The document outlines an induction training for new network operations and maintenance staff. It includes details like: - The training will last 3 days and cover topics like NGN protocols and H.248 call flow scenarios. - Sessions will use methods like presentations, demonstrations, and question/answer to ensure understanding. - Participants are expected to follow rules like silencing phones and focusing on the content.

1. Date- 14/09/2015
Prepared By: Yonas Feleke
PSTN, FLNGN and IGW-Advanced support supervisor
Induction Training for Network O&M new Staffs

2. P_002
Date
(DD/MM/YYYY)
Version Prepared by Remark
14/09/2015 V2 Yonas Feleke
DOCUMENT CONTROL

3. Morning class
08:30-12:30 A.M
Afternoon class
13:30-17:00 P.M
Coffee Break:
Morning: 10:30 AM - 10:45 AM
Afternoon: 3:00 PM - 3:15 PM
TRAINING TIME-BUDGET
Training Duration: 03 days

4.  Describe NGN working principle
 Describe NGN protocols
 Describe H.248 call flow scenarios
 Know Subscriber Configuration steps
 Understand the Subscriber Number Allocation( Hundred group and
zone concepts)
 Know the DAS Configuration
OBJECTIVE OF THE TRAINING

5.  Top-down content presentation
 Conceptual briefings on milestone areas
 Illustrative diagrams
 Demonstrative simulations if any
 White board drawings if necessary
 Interaction (Q&A)
o A sound, friendly & conducive learning environment setup
 Site visit for real equipment view
 Closing remarks
TRAINING METHODOLOGY

6.  Put Cell phones in Silent mode or
 No side talk
 Punctuality (e.g. mornings & after coffee break)
 Politeness/Courtesy
 Concentration/Focus
 Enthusiasm/Passion
 Sharing know how
 …
GROUND RULES FOR TRAINING SUCCESS
(LEARNING CLIMAX)

7. CH-1: Introduction to NGN
CH-2: H.248 protocol stack
CH-3: H.248 subscriber configuration and service problem
troubleshooting
Dashboard | October 27, 2014
P_007
PRESENTATION RUNNING ORDER

8. Introduction to FL NGN Network
8
Day 1 Morning

9. NGN STANDARD ARCHITECTURE
9
Service APPS
Control Softswitch
Core
Access
TG AG BGW
Intelligent
terminals
OA
M
Supporting
platform
SG
NMS
Billing
Softswitch
IP Network
PSTN/P
HS
Broadband
Access
Other
NGN
IAD
IPPhone
IP VT
HLR
BAC-
N

10. ZXSS10
SS1b
Adaptation
processing
between accessing
protocols.
Resource
control
Call Control
Processing
Interconnection
Service Interface
&Interoperation Provisioning
Accomplishing basic call
processing and enhanced
call processing.
Application
System
Support
Protocol
Adaptation

11. ZTE NGN ARCHITECTURE
11
Access
ZXSS10
IAD series
Broadband
Access
Core
Control
Service
ZXMSG
5200
ZXMSG7200
ZXMSG9000
ZXSS10 SS1 ZXSS10 SS1
ZXUP10 APP Router Server
IAD Manager ZXSS10
NMS
Core Packet Network
PSTN
/ISDN
SS7
Network
PBX
Private
Network
ZXSS10
BGW
Soft-
Phone
SHLR
Video
phone

12.  SS：SoftSwitch-- core of NGN network.
 Call control processing
 Protocol Adaptation
 Service Interface Provisioning
 Application System Support
 SG：Signaling Gateway
 Accomplishing signaling translation from PSTN to
IP
 TG：Trunk Gateway
 Accomplishing voice translation from PSTN to IP
ELEMENT OF NGN
12

13.  MSAG：Multi-Service Access Gateway
 Accessing subscribers
 IAD：Integrated Access Gateway
 Accessing subscribers
 BGW：Broadband Gateway
 Inter-connect public network and private network
 SHLR: Smart Home Location Register
 Storing subscribers data
 Application Server
 Provide API (Application Programming Interface)
for different service
ELEMENT OF NGN
13

14. Call control
protocol
Transportation
control protocol
Media control
protocol
Service
application
protocol
• ISUP, TUP over
IP;
• Q.931;
• BICC;
• SIP-T;
• H.323
• TCP, UDP;
• SCTP;
• TCAP/SCCP/M
3UA
• H.248;
• SIP;
• MGCP
• INAP(CS2);
LDAP; RADIUS
• OAM protocol
• SNMP
• LAN protocol
• IEEE802.3,
IEEE 802.3u;
TCP/IP protocol
suite
ZXSS10 SS1B PROTOCOL SUPPORT CAPABILITY

17. SS10 Operating Principle

18. FN

19. Card Slot Position
J
REAR
1
L
r
N
I
C
N
I
C
T
I
C
S
S
N
I
CARD NO 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
J
FRONT
1
i
r
S
S
C
S
S
C
S
P
C
1
S
P
C
2
S
S
N
S
S
N

20. SS1B Communication Bus Diagram
IP Network Interface
Hot Swap Control Bus and 485 Bus
o
E

21.  ZXSS10 Hardware description
DAY 1 AFTERNOON

22. BOARD FUNCTION DESCRIPTION
■ SSC: SYSTEM CONTRL CARD (CPU 800/7410)
■ ESC: An enhanced version of SSC, Enhanced SSC (ESC)
is designed to improve the overall processing capability of
ZXSS10 SS1b
■ SSN: SYSTEM SWITCHING NETWOTK
■ SPC: SYSTEM PROTOCOL CARD
■ ESPC: an enhanced version of SPC
■ NIC: NETWORK INTERFACE CARD
■ SSNI: SYSTEM SWITCHING NETWORK INTERFACE
■ TIC: TRANSPORTATION INTERFACE CARD

23. SSC Board: Control and Monitor
■ Hardware
• CPU(MPC7410, MPC750), RAM
• IDE,
• Ethernet Interface,
• Power supply,
• Serial bus(RS-485/RS- 232)
• Board status: online/offline/reset
■ Function
• Monitor the hardware and software status of other boards.
• Control other board in the shelf.
• File backup (Software version, CLI script, etc. )
• SC active-reserve switch.

24. ESC: An enhanced version of SSC
■ Has powerful processing capability and large-size memory; It shares
part of protocol processing tasks.
■ Provides external interfaces that are necessary for the system.
■ Monitors and controls the working status of other boards within the
system; Provides a hot plugging function.
■ Provides ports for communication with two SSNs.
■ Provides active/standby control and communication signals;
■ Provides interfaces and status signals relating to power detection, and
provides information about slot numbers and shelf numbers.

25. SSN board: Ethernet switching network
■ Hardware
• CPU, RAM, Switching Chip
• 24 100M Ethernet interface.
• 13 for SPCs
• 2 for SCs
• 6 for NICs
• others for DB server, shelf cascade.
■ Function
• Provide Ethernet switching platform

26. NIC Network Interface Card
■ Hardware
• CPU, RAM
• 2 Ethernet Interface 1 for inner Ethernet network, 1 for
• outer IP network
■ Function
• Distribute the Protocol and other packet among SPCs.

27. SPC: System Protocol Card
■ Hardware
• CPU, RAM
• 1 10Base-T Ethernet Interface
■ Function
• Protocol and Call processing.

28. ESPC: As an enhanced version of SPC
■ Has powerful processing performance and large-size
memory; Shares part of protocol processing tasks.
■ Provides ports for communication with other boards.
■ Provides SC-controlled auxiliary communication channels.

29. SS1B shelf cascading
■ CSN: CASCADE SWITCHING NETWORK
■ CSNI: CASCADE SWITCHING NETWORK INTERFACE
■ GNIC: GIGABIT NETWORK INTERFACE CARD

30. SS1B shelf cascading
■ CSN board
• Inserted in Slot 7 and Slot 8 of the main shelf
• Provide 24*FE + 4 *GE, layer-2 Ethernet switching
• Work in the active/standby mode
■ CSNI board
• Provides Ethernet connection for CSN board
■ GNIC board
Provides 1 GE and 4 FE ports used to connect to the
external network

31. Master shelf Card Slot Position
J
REAR
i
L
r
C
S
N
I
G
N
I
C
G
N
I
C
N
I
C
N
I
C
T
I
C
S
S
N
I
CARD NO 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
k
FRONT
i
i
r
S
S
C
S
S
C
S
P
C
1
S
P
C
2
C
S
N
C
S
N
S
S
N
S
S
N

34. SPC Software Architecture
Database
Call & Service subsystem
Billing
/OAM
Vieun interface
Etc.
MGC
P
H248 H323 SIP SIP-T SS7
SIGT
RAN
DSS1
Support subsystem
Hardware

35. ■ SC/SPC/NIC/SSN Software
OS: VxWorks
■ Database Software
OS:SUN Solaris, Oracle
■ OAM Software
OS: SUN Solaris/WinNT/Windows2000

39. SUMMARY
■ Powerful capacity
■ High reliability
■ Flexible configuration

40.  H.248 protocol
DAY 2 MORNING
40

41. 41
H.248 PROTOCOL

42. 42

43. 43

44. 44

45. 45

46. 46

47. 47

48. 48

49. 49
Concepts of H.248 protocol

50. 50

51. 51

52. 52

53. 53

54. 54

55. 55

56. 56

57. 57

58. 58

59. 59

60. 60

61. 61

62. 62

63. 63

64. 64

65. 65

66. 66

67. 67

68. 68

69. 69
Call Flow Scenario

70. 70

71. 71

72. 72

73. 73

74. 74

75. 75

76. 76

77. 77

78. 78

79. 79

80. 80

81. 81

82. 82

83. 83

84. 84

85. 85

86.  H.248 subscriber configuration
DAY 3 MORNING

87.  ADD Zone
 ADD Node
 Allocating Subscriber Number
 Default Template Configuration
 TID Name Configuration
 DAS Configuration
CONTENTS

88.  Node：Represent a Device
 Zone：A set of gateway nodes with the same properties
CONCEPT

89. The nodes with different equipment types cannot
exist in the same gateway cluster. In the SS
system, SPC data area and hundred groups are
allocated in the unit of gateway cluster. Before
addition of IAD equipment, the gateway cluster
where this IAD equipment resides should be
configured.
Right Click SS Configure Management
IAD GATEWAY CLUSTER CONFIGURATION

90. IAD GATEWAY CLUSTER CONFIGURATION

91. IAD Zone ID=6
Area Code=755
IAD GATEWAY CLUSTER CONFIGURATION

92.  The SPC of SS control equipment processes
calls & protocols based on the gateway cluster.
After a gateway cluster is added, we need to
allocate an SPC for it.
 Right Click SS Configure Management
Globe Configuration SS Data Configuration
Shelf Configuration Right Click SPC Card
Data Area Capacity Configuration Click “Add”
CONFIGURATION OF DATA AREA CAPACITY

93. CONFIGURATION OF DATA AREA CAPACITY

94. CONFIGURATION OF DATA AREA CAPACITY

95. We must allocate services, protocols and authentication
of users in the zone (gateway cluster) to the SPC board
for processing.
ZONE TO CARD CONFIGURATION

96.  Right Click SS and Select Command Line Terminal
REBOOT THE SPC CARD

97.  Command: 1211:3, 14,”YYYYMMDD”
REBOOT THE SPC CARD

98.  Double Click on the zone to which a node is added to enter the zone
IAD NODE CONFIGURATION

99. IAD NODE CONFIGURATION
Node ID=23
IAD IP=192.168.1.9
Local Port=2944
Peer Port=2944
Zone ID=6

100. Device Property
IAD NODE CONFIGURATION

101.  5004：1
SHOW NODE STATE

102.  Local Office User Configuration
1. Local Office Code
IAD USER CONFIGURATION
Click Add and Select Add Local Office Code

103.  ADD Local Office Code
 ADD Hundred Set
ADD LOCAL OFFICE CODE
 Office Code:8426
 Local Office Use…4
 8426XXXX

104.  Local Office User Configuration
User Configuration Local Office User Configuration
Click “Add”
IAD USER CONFIGURATION

105.  Here we have to specify the default property template and packet
template ID for different terminal types.
 Enter in to the Zone and Select Default Attribute Configuration
TID DEFAULT ATTRIBUTE CONFIGURATION

106.  TID Name is the terminal ID in the H.248 protocol, used
for identifying the physical termination point (user circuit)
and the logic termination point (RTP Port).
CONFIGURATION OF THE TID NAME

107.  Select “Add” then “Add TID Name”
CONFIGURATION OF THE TID NAME
User Circuit

108.  RTP Port
CONFIGURATION OF THE TID NAME

109. SHOW TID NAME

110. DAY 3 AFTERNOON

111.  DAS is used to find the
Destination
DAS CONFIGURATION

112.  Add Local
Office Code
DAS CONFIGURATION

113. DAS CONFIGURATION

114. DAS CONFIGURATION

115. DAS CONFIGURATION

116.  H248 subscriber problem troubleshooting based on live problems on
the network TT
TROUBLESHOOTING
11
6