Oeb9fa131 Usn9810 System Overview Issue1.00

USN9810 System Overview
Confidential Information of Huawei. No Spreading Without Permission





 The LTE/SAE network is designed for high-speed mobile packet data services. In the SAE
network, the network structure is greatly simplified.
 Compared with the architecture described in earlier versions, the SAE architecture is
optimized in the following aspects:
 The LTE base stations are directly connected to the EPS core network. The
previously independent BSC/RNC functions are integrated into the eNodeB.
 The PS domain is restructured as follows:
 The control plane and user plane of the SGSN are separated. The signaling
function of the SGSN is implemented by the MME and the forwarding
function of the SGSN is implemented by the serving gateway (S-GW).
 The GGSN function is implemented by the PDN gateway (P-GW).
 The S-GW and P-GW may be implemented in one physical node.
 The SAE network can access the non-3GPP networks such as CDMA2000 High
Rate Packet Data (HRPD) network. Thus, the interworking of various radio access
technologies is realized.
 LTE: Long Term Evolution
 SAE: System Architecture Evolution
 EPC: Evolved Packet Core
 MME: mobility management entity

 PCRF: policy control and charging rules function

 HSGW: HRPD serving gateway
 PDSN: packet data service node
 GERAN: GSM/EDGE Radio Access Network
 UTRAN: UMTS Terrestrial Radio Access Network
 E-UTRAN: Evolved UMTS Terrestrial Radio Access Network (LTE)





 High rate
The high-speed serial data link and switched structure are used. Thus, the data
exchange bandwidth intra-subrack can reach 2.5 Tbit/s.
 High reliability
All boards and subboards are hot swappable. In addition, redundancy is implemented
on all key components, such as power supply, fan, management module, and
board of each type. Thus, the reliability of the system reaches 99.999%.
 High expansion capability
The USN supports addition of interfaces on the ATCA board and cascading between
subracks through the interface board within a subrack.
 Well management
The standard management bus is used, which can manage any part in the system.

 Cross-hardware platform
A uniform interface of the hardware platform is provided, which implements the operation
of upper-layer applications on different hardware platforms. Thus, the hardware
management is independent of the hardware platform.
 Cross-operating system
Different interfaces of the operating system at the lower layer are shielded. Instead, a
uniform virtual operating system application programming interface (VOS API) is provided
for upper-layer applications.
 Easy maintenance
The implementation mechanisms of the functions such as operation and maintenance,
alarm management, performance measurement, call and signaling tracing, data backup,
board switchover, and online loading are provided for upper-layer applications.


 The cabinet provides an area where components are placed together and connected to
each other. It also protects the components from pollution and damage, and represents
the product image.
 USN9810 adopts N68E-22 cabinets.
 The subrack provides the following functions:

- Using a backplane to combine various boards inserted in the subrack to be an
independent unit
- Protecting boards from damage and providing power for the boards and fan assembly
- Providing heat rejection paths for the system
 USN9810 adopts T8280 subracks, which contain the following parts:

- Boards and board filler panels
- Fan assembly
- Power entry modules

 In PS11.0, EVUs are added to process CHRs. A USN9810 supports a maximum of four
EVUs.

 Based on sevice requirements, subracks configured are divided into two types:
- Basic subrack: mandatory. Basic subracks are configured in the cabinet with full service
processing abilities and provide external interfaces.
- Service subrack: optional based on number of users. Service subracks are used
together with basic subracks to process services.
The OMU board is configured in the basic subrack. In the basic subrack, the back
board of the SWU board is the TMI board. In the service subrack, the back board of
the SWU board is the TSI board.
One basic subrack is configured in each USN9810 and fixed in subrack 0 of the first
rack. Service subracks are configured optionally based on the number of users. During
the subrack configuration, you must configure boards from bottom to top.
 In PS11.0, EVUs are added to process CHRs. A USN9810 supports a maximum of four
EVUs.

 Host Software
The host software runs on different boards. It implements functions such as signaling access and processing, service control, and resource management. In response to specific
commands, the host software also performs the following operations such as data management, device management, alarm management, performance statistics, and signaling
trace on the host in cooperation with the BAM software.
The host software adopts a hierarchical and modular design. From bottom to top, its components are the operating system, middleware, and various applications.
 Operating System
The operating system of the host software is Linux. This is a real-time operating system.
 Middleware
The middleware technology, distributed object-oriented programmable real-time architecture (DOPRA), is applied to the operating system and applications of the USN9810. Thus,
the upper-layer service software is irrelevant to the lower-layer operating system.
The middleware facilitates the migration of software functions between different platforms. Thus, new and stable product versions are released quickly as the service software is
rarely changed.
 Applications
The application is the functional part of USN9810 software. Loaded with different applications, boards can provide different functions. The USN9810 applications can be classified
into the following types:
Signaling bearer software: implements the access of broadband and narrowband signaling and processing of the lower-layer protocols.
Service processing software: performs signaling processing, session management, mobility management, and resource management.
Database software: manages device data and dynamic subscriber data.
System support software: implements system management and device interconnection.
OM software: receives the operation commands from the OMU and reports the command results to the OMU.
 BAM Software
The BAM software runs on the OMU, OMS (Operation and Maintenance System), and WebUI. Along with the host software, it provides the man-machine interface, which enables
the maintenance personnel to implement the following functions: data management, device management, alarm management, performance statistics and signaling trace.
The BAM software adopts the client/server model. It consists of the OMU server software, OMS software, and WebUI software. The OMU server software is installed on the OMU.
The OMS software and WebUI software is installed on the client, namely, a PC.
 OMU Server Software
The OMU server software runs on the OMU board. As a combination of the communication server and the database server, the OMU server software forwards OM commands
from different workstations to the host and sends responses or command results to the corresponding workstations. The OMU server software serves as the essential unit of the
operation, administration and maintenance (OAM) software.
The OMU server software runs on the Linux operating system and uses Oracle as the database platform. It provides functions of the terminal OAM software through multiple
parallel service processes, such as maintenance process, data management process, alarm process, and performance statistical process.
 OMS Software
The OMS software runs on a workstation. Serving as a client, the OMS software is connected to the OMU, serving as a server, in client/server mode. The OMS software provides
MML-based graphical terminals. A workstation can be located locally or remotely. For example, a remote workstation can be connected to the OMU server through a wide area
network (WAN) in dial-up mode.
In addition, you can perform the following maintenance functions on a workstation: data maintenance, device management, alarm management, performance statistics, call trace,
and signaling trace.
WebUI Software
The WebUI software is namely the Web client. You can use the Web browser, such as IE browser, to perform performance management and traffic statistics. In addition, the Web
browser can also be used during upgrade.






 Gb is the interface between the SGSN and the GSM BSS. Gb uses the statistical
multiplexing technology to transmit GPRS data and signaling between the SGSN and the
GSM BSS/MS.
 Gb supports functions such as flow control of downlink data, GPRS suspend and restore,
automatic cell configuration, and resource sharing in the entire system.

 Iu is the interface between the RNC and the SGSN. IP packets and signaling between the
RNC and the SGSN, and between the user equipment (UE) and the SGSN are transmitted
through the Iu. Iu supports resource sharing in the entire system.

 Definition
S1 is the interface between the eNodeB and the core network (CN) of the EPC system.
Signaling switching and service transmission between the UE and the CN are performed
through the S1. S1-MME is the control interface between the eNodeB and the MME. The
S1-MME provides reliable signaling transmission on the wireless networks.
 S1 application protocol (S1-AP) contains multiple elementary procedures (EPs). One EP is
generated when there is one interaction between the eNodeB and EPC. One EP contains
one initialization message and one response message. The S1-MME interface defines two
types of EPs:
- Response message: Indicates successful EP or failed EP.
- No response message: Response messages are not required.
 Response types of EP with response messages:
- Success: There is a definite signaling indicating success of the EP. With receipt of the
response message, the EP ends successfully.
- Failure:
There is a definite signaling indicating failure of the EP.
No response message is received due to timeout of the timer.
 Success and failure: A signaling message indicates different results, including successful
requests and failed requests.


 Definition
- S6a is the interface between the MME and the HSS of the EPC system. Subscription data
management and authentication-related functions are provided through the S6a. In the
roaming scenario, the MME connects to the HSS through the S6a.
 The protocol layers are described as follows:
- Diameter: supports the subscription and authentication data transmitted between the
MME and the HSS. Based on the Diameter, users can be authorized to access the EPS
network.
- SCTP: ensures the transmission of signaling messages between the MME and the HSS.

 Definition
- The SGSN and GPRS support node (GSN) are interconnected through the Gn/Gp interface.
GPRS is short for general packet radio service.
 Note:
- When functioning as an MME, the USN9810 can communicate with an SGSN through
a Gn interface. In this case, the MME serves as an SGSN.
- The GTP-C version is GTPv1.
- The GTP-U version is GTPv1.

 Definition
-- S10 is the interface between MMEs of the EPC system. Signaling over S10 is used to
forward context information and handover signaling when the MME handover is
performed.
 Note:
-- GPRS Tunneling Protocol for the control plane (GTP C) provides the tunnel for signaling
messages between the MME and the SGSN.
-- The GTP-C version is GTPv2.

 Definition
-- S11 is the interface between the MME and the S-GW of the EPC system. S11 is used to
create transmission bearers between the MME and S-GW, update and delete request
and response messages. In addition, the S-GW informs the MME of UE paging through
the S11 when UE is in the ECM-IDLE state.
 Note:
-- GPRS Tunneling Protocol for the control plane (GTP C) provides the tunnel for signaling
messages between the MME and the S-GW.
-- The GTP-C version is GTPv2.




 Authentication
− The authentication function is used in subscriber identification and authentication and
synchronization of the encryption key. This function checks the validity of a subscriber's service
requests to ensure that only legal subscribers can use network services. The authentication
procedure and EMM-related procedures are correlated. The authentication of subscriber identity
modules (SIMs) is unidirectional, and the authentication of user service identity modules (USIMs)
is bi-directional. A subscriber can authenticate the network to ensure the security of the
network.
 UE Identity Confidentiality
- The UE identity confidentiality is implemented through P-TMSI/GUTI allocation. The P-TMSI/GUTI
is used to provide a unique temporary UE identity in the EPS. This identity does not reveal the
permanent UE identity.
 NAS Signaling Encryption and Integrity Protection
- NAS signaling encryption and integrity protection can provide encryption and integrity
protection for the NAS signaling, and thus improving the system security. Currently, NAS
signaling encryption algorithms supported by the USN9810 are as follows:
EPC: AES, SNOW 3G (encryption and integrity)
GSM: GEA-1, GEA-2, GEA-3 (encryption)
UMTS: UEA1 and UEA2 (encryption), UIA1 and UIA2 (integrity)
 Identity Request
- Subscribers must provide a variety of identities (IMSI, IMEI, and IMEISV) so that the network can
identify their authentic identities.

 Definition
- Subscriber data management refers to the procedure for inserting, deleting, and
modifying subscriber data in USN9810.
- Subscriber data includes subscription data in the HLR/HSS and dynamic data generated
during subscriber access to the network.
- Subscriber data is the basis for the SGSN/MME to control UE access and provide services.
 Subscriber data involved in the subscriber data management feature refers to the
following data:
- Subscriber data stored in the HLR/HSS, including the IMSI/MSISDN, EPC subscription
information, ODB, charging information, and roaming restriction information.
- Dynamic data generated during the EPC network accessing procedure and the
activation bearer procedure, including location information, IP address assigned by the
session for the UE, S-GW/P-GW/GGSN IP address, QoS resource used by the UE, and
APN.



 S-CDR: Records the relevant information of the PDP context in the SGSN.
 M-CDR: Records the relevant information of the mobility.
 S-SMO-CDR: Records the information of mobile originated SMS.
 S-SMT-CDR: Records the information of the mobile terminated SMS.
 LCS-MT-CDR: Records the CDR information of the mobile terminated location service.
 LCS-MO-CDR: Records the CDR information of mobile originated location service.
 LCS-NI-CDR: Records the CDR information of network originated service.

 SGSN supports processing of PS SMSs. PS SMSs refer to services provided by SGSN through PS for mobile subscribers to receive or send short
messages. PS SMSs include the short message mobile originated (SMMO), short message mobile terminated (SMMT), and short message alert
(SM alert).
SMSs can be carried over CS or PS networks. MSs with GPRS attached or MSs with GPRS attached and IMSI unattached receive or send SMSs in
the PS domain. MSs with GPRS attached and IMSI attached can receive and send SMSs in the PS and CS domains. PS SMSs of class B MSs are
processed only when the voice service ends, that is, the switching between the voice service and PS SMSs is performed through the suspend
and restore procedure.
 SMMO: The GSM/UMTS system forwards short messages sent from MSs to the SMC. Meanwhile, GSM/UMTS provides the results of
sending short messages: success or failure.
 SMMT: The GSM/UMTS system forwards short messages sent from the SC to MSs. Meanwhile, GSM/UMTS and provides the results of sending
short messages: success or failure. If short messages fail to be sent, a subsequent transmission strategy is required.
 SM alerts include:
SMC After the result that short messages are received successfully is sent, the MS alerts the SMC.
The points of the system ready for receiving short messages include mobile subscriber reachable, memory available, and the information that
the SMC is informed of the mobile subscriber reachable and memory available. After the faults such as subscriber unreachable and memory
overflow are rectified, the SGSN instructs the HLR to be ready for receiving short messages. After the HLR receives the information that the
system is ready for receiving short messages, the HLR checks the subscriber flag bit, and sends the notification to the SMC with the sending
failure results. In this way, the SMC can re-initiate the SMMT.
 Short message charging

After the MS sends a message through the SGSN, the SGSN generates a S-SMO-CDR for the charging of the message. After the MS receives a
message through the SGSN, the SGSN generates a S-SMT-CDR for the charging of the message. The S-SMO-CDR and S-SMT-CDR includes the
following contents:
- Identity of short message sender
- Subscriber location
- Number of short message receiver
- Short message center address
- SGSN number
- Time of sending short messages from SGSN to MS
- Time of receiving short messages from MS to SGSN


The circuit switched fallback in evolved packet system (CS fallback) is a CS fallback mechanism
complying with 3GPP TS23.272 (a protocol). This mechanism ensures subscriber registration
on the evolved packet system (EPS) network and the traditional CS network at the same time.
When a subscriber initiates a voice call, the EPS instructs the subscriber to fall back on the CS
network. Then the subscriber re-initiates the voice call.

Single radio voice call continuity (SRVCC): When voice services on the LTE network switch to
the GSM/UMTS network, the SRVSS solution provided by USN9810 can ensure the seamless
switching.


The QoS mechanisms on control plane are as follows:

 Access control
The access control is implemented based on the subscription data, device resources, local policy, and policy decision function
(PDF). This ensures sufficient resources for services.
When the subscriber activates the PDP context, the SGSN negotiates the QoS with the MS. If the negotiation fails, the SGSN
denies the MS access.
 QoS negotiation
The MS sends a context activation request with the requested QoS to the SGSN. The SGSN negotiates with the MS based on
the QoS information and its configuration, and returns a context activation response with the negotiated QoS to the MS.
The QoS mechanisms on user plane are as follows:
 Traffic classification
The traffic classification is an important mechanism. Only after traffics are classified, the system can adopt class-based policies.
Identification refers to the identification of IP priority levels or DSCP bits of IP packets. Classification refers to the classification
of data traffics by multiple priority levels and service types. For example, the packet can be classified into eight types at
maximum if identified by the first three bits of the type of service (ToS), namely the IP priority level. The packet can be
classified into 64 types at maximum if identified by differentiated services code point (DSCP).
The network administrator can specify the packet classification policy. The policy includes information such as the IP priority
or DSCP bits of the IP packet, the experimental bits of the multiprotocol label switching (MPLS) packet, input interface, source
address, target address, MAC address, IP protocol, and port numbers of application programs. The classification results are
not limited. They can be traffics defined by a quintuple group (source address, source port number, protocol number, target
address, and target port number) or all packets transmitted to certain network segments.
After packets are classified, the system adopts the class-based QoS mechanisms and performs congestion management, traffic
monitor, and traffic shaping.

 Congestion control
Congestion management
For a network unit, when the receiving rate is higher than the sending rate on the outbound interface, the congestion occurs.
Congestion management provides a resource allocation policy to determine the process sequence of packet forwarding during the congestion.
Congestion management includes the queue setup, packet classification, packet allocation to queues, and queue scheduling. The queue
scheduling is used to address specific problems and has specific impact on the network performance. At present, the queue scheduling includes
mechanisms such as the first in first out queuing (FIFO), priority queue (PQ), custom queue (CQ), weighted fair queuing (WFQ), and class-based
weighted fair queuing (CBWFQ).
Congestion prevention
Congestion prevention refers to a traffic control mechanism for addressing network overload by adjusting the network traffic. It enables the
system to monitor the using condition of network resources (queuing and memory cache) and discard packets when the congestion becomes
worse.
It is more profound than the source traffic control because more service traffic loads of the router are involved. When the router discards packets,
the source traffic control (such as the TCP traffic control) is required to adjust the network load. Congestion prevention is implemented by
discarding packets. The SGSN meets diversified application needs by adopting multiple congestion prevention mechanisms such as the tail drop,
random early detection (RED), and weighted random early detection (WRED).
 Traffic monitor by committed access rate (CAR)
CAR is a QoS mechanism on user plane used to limit the traffic rate. The device traffic must be measured for the implementation of this function.
 QoS queue management
The QoS queue management is a QoS mechanism on user plane. The subscriber data packets are allocated to corresponding QoS queues based
on their QoS types. The SGSN provides multiple queue scheduling mechanisms such as FIFO, PQ, CQ, WFQ, and CBWFQ, performs queue
scheduling, and determines the transmission sequence of packets.
QoS mapping: DSCP remapping/mapping between the 3GPP QoS and DSCP/mapping between the DSCP and ATM QoS/mapping between the
R97/98 and R99 QoS attribute/conversion from the R5/99 to R7 QoS attribute/
 Traffic shaping (TS)
Traffic shaping mechanism is used on the user plane. It can limit the traffic of certain connection of certain network and balance the packet
transmission rate. It is an active measure for adjusting the traffic output rate.



 Switchover when a UE moves from an LTE network to a UMTS network

1. The UE sends a RAU request to the GnGp SGSN.
2. The GnGp SGSN obtains the context from the MME.
3. If the context does not contain security parameters, the operation will be implemented in safe
mode.
4. The GnGp SGSN requests the GGSN to update the context.
5. The HLR/HSS cancels the location information in the MME and updates the location
information on the GnGp SGSN.
6. The GnGp SGSN receives the RAU request from the UE. The UE completes the RAU procedure
of switching over from the LTE to the UMTS network.
7. The MME requests the S-GW to delete the original bearer. If there is S1 connection before the
RAU procedure, the connection is released.
 Switchover when a UE moves from a UMTS network to an LTE network
1. The UE sends the TAU request to the MME through eNodeB.
mode.
4. The MME send a bearer setup request to the S-GW. The S-GW creates the context and sends
the updated bearer setup request to the P-GW.
5. The HLR/HSS cancels the location information in the MME and updates the location information
on the GnGp SGSN.
6. If any Iu connection exists before the TAU procedure, the connection is released.
7. The MME receives the TAU request from the UE. The UE completes the TAU procedure of
switching over from the UMTS to the LTE network.

 Switchover when a UE moves from an LTE network to a GSM network

1. The UE sends a RAU request to the GnGp SGSN.
mode.
6. The GnGp SGSN receives the RAU request from the UE. The UE completes the RAU procedure
of switching over from the LTE to the UMTS network.
7. The MME requests the S-GW to delete the original bearer. If there is S1 connection before the
RAU procedure, the connection is released.
 Switchover when a UE moves from a GSM network to an LTE network
1. The UE sends the TAU request to the MME through eNodeB.
mode.
4. The MME send a bearer setup request to the S-GW. The S-GW creates the context and sends
the updated bearer setup request to the P-GW.
6. If any Iu connection exists before the TAU, this connection is released.
7. The MME receives the TAU request from the UE. The UE completes the TAU procedure of
switching over from the UMTS to the LTE network.

 Handover from an LTE network to a UMTS network

1. The eNodeB sends a handover request to the MME. The MME sends a header relocation request to the GnGp SGSN.
2. The GnGp SGSN requests the target RNC to set up wireless resource and sends a relocation response to the MME.
3. If there is no direct link from the eNodeB to the target RNC, the MME requests the S-GW to set up a non-direct link.
4. The MME sends a handover command to the UE through eNodeB.
5. Data forwarding by eNodeB: If there is direct link, the eNodeB forwards the data to the target RNC directly. If there is no
direct link, the eNodeB forwards the data to the target RNC through the S-GW.
6. The UE completes the handover and sends a RRC reconfiguration completion message to the RNC.
7. The GnGp SGSN notifies the MME of the relocation completion. The MME responds to the relocation completion.
9. The MME requests the S-GW to delete sessions and the eNodeB to release resources.
 Handover from a UMTS network to an LTE network
1. When a UE moves from the UMTS network to the overlapping area of the LTE and UMTS networks, the RNC send a
handover request to the GnGp SGSN. The GnGp SGSN sends a relocation request to the MME.
2. The MME requests the eNodeB to prepare wireless resource and requests the S-GW to set up sessions. The eNodeB and
S-GW returns response after resources are prepared.
3. If there is no direct link between the eNodeB and the target RNC, the MME requests the S-GW to set up a non-direct link.
4. The MME sends a request to the GnGp SGSN for confirmation on the resource preparation. The GnGp SGSN sends a
relocation command to the RNC.
5. Data forwarding by the RNC: If there is direct link. The RNC forwards the data to the eNodeB directly. If there is no direct
link, the target RNC forwards the data to the eNodeB through the S-GW.
6. The RNC instructs the UE to hand over to eNodeB. The UE completes the handover and sends a confirmation message to
the MME. The MME notifies the GnGP SGSN of the relocation completion.
7. The MME notifies the S-GW/P-GW of the handover completion and requests for updating the bearer. If the PCRF is
deployed, the P-GW reports the RAT change event to the PCRF for decision.
8. The GnGp SGSN requests the RNC to release the original wireless resources. The RNC returns a response to the GnGp
SGSN after the release.

 The HLR/HSS must support different IMSI accounts with the same MSISND for the multi-
IMSI feature.

 MVNO refers to the mobile virtual network operators that use the network resources
authorized by the mobile network operator (MNO) to provide services (including services of
MNO and MVNO), and maintain the authorized network resources.
 MVNO enables multiple operators invest on the sharing network, or rent other
operator’s network, to lower the investment and risk.
 The MVNOs depends on the MNO differently. The network resource authorized by the
MNO can be RAN, partial CN and the whole CN.

 Limitation:
 The direct tunnel solution cannot be adopted in the following scenarios:
 Roaming subscribers use the CAMEL service.
 The GGSN only supports the GTP V0.
 Any one of the RNC, SGSN, or GGSN does not support direct tunnel.
 Operators deploy the MBMS application whose billing policy requires the SGSN to
reduce the S-CDR traffic.
 The 2G scenario.

 The SIGTRAN protocol stack enables an IP network to transfer the signals of a traditional
switched circuit network (SCN), supports inter-layer standard primitive interface of the SCN
signaling protocol, ensures the SCN signaling can be applied without changing, uses the
standard IP transmission protocol as the transmission layer, and meets the special
transmission requirement of SCN signaling by improving its own functions.




 The S-GW Pool is covered by multiple S-GWs. Subscribers in an S-GW Pool are served by
multiple S-GWs.
 In the GGSN/P-GW Pool, multiple P-GWs work as the gateways of a APN and serve for this
APN in load sharing or backup mode.


The USN9810 provides redundancy backup in three levels, namely, NE, board, and interface, to ensure the reliability of the system and avoid single
point failure.
 NE-level redundancy
Based on the MME Pool feature, multiple MMEs in the Pool area share loads.
The USN9810 can choose more than two S-GWs/P-GWs for packet services. If one S-GW/P-GW is faulty, the USN9810 can choose the other S-
GW/P-GW to provide services. The S-GWs/P-GWs can be chosen in turn or work in active and standby mode.
The USN9810 can connect to multiple CGs and specify the relationship with these CGs. In load sharing mode, the USN9810 generates CDRs and
sends to multiple CGs for load sharing. In the active and standby mode, the USN9810 sends CDRs to the standby CG when the active CG is
faulty.
 Board-level redundancy
In the USN9810, all important units work in 1 + 1 backup mode. When the active unit is faulty, the standby unit continues to provide services.
 Interface-level
The USN9810 provides multiple types of interfaces: FE/GE interface. These interfaces work in active and standby mode to prevent single point
failure and ensure network security.
The operation and maintenance (OAM) is the management and maintenance protocol defined by the ITU-T for the asynchronous transfer mode
(ATM) network.
The OAM performs the following functions:
1. Performance monitor: The network maintenance and management entity monitors multiple performance specifications that relate to the
network operation continually and periodically.
2. Fault detection: The network maintenance and management entity detects the existing and possible faults and provides report about the
maintenance information and alarms.
3. Network protection: The network maintenance and management entity isolates the entire network to prevent failure occurs on devices and
ensure the normal running of the entire network.
4. Management information transmission: The network maintenance and management entity obtains information during transmission and
notifies other entities of the information for timely transmission to the controlled device.
5. Fault location: The network maintenance and management entity locates the faulty device for timely and correct rectification.
The OAM functions of the ATM network can be classified into five levels. Each level has related OAM information traffic (defined as F1 to F5). The
F5 function is implemented on the virtual connective channel (VCC).







Oeb9fa131 Usn9810 System Overview Issue1.00

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Oeb9fa131 Usn9810 System Overview Issue1.00

Transféré par

Droits d'auteur :

Formats disponibles

USN9810 System Overview

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 PCRF: policy control and charging rules function

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 USN9810 adopts N68E-22 cabinets.

 The subrack provides the following functions:

 USN9810 adopts T8280 subracks, which contain the following parts:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Short message charging

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

The QoS mechanisms on control plane are as follows:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Switchover when a UE moves from an LTE network to a UMTS network

Confidential Information of Huawei. No Spreading Without Permission

 Switchover when a UE moves from an LTE network to a GSM network

Confidential Information of Huawei. No Spreading Without Permission

 Handover from an LTE network to a UMTS network

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission