Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
27 Cards in this Set
- Front
- Back
|
1
|
For a newly deployed Plug-n-Play AP (eNB), AP (eNB) is powered up and launches DHCP by sending DHCP Discover.
|
|
|
2
|
External DHCP returns AP (eNB) Physical IP Address (IPsec tunnel outer IP address), and External (Public) primary and secondary DNS server IP addresses in DHCP responses. AP (eNB) shall have its Start up SeGW FQDN and EMS FQDN pre-provisioned in the factory (written in the EEPROM)
|
|
|
3
|
AP (eNB) sends DNS query to External DNS server to resolve Start up SeGW IP address from SeGW FQDN.
|
|
|
4
|
AP (eNB) initiates IPsec tunnel setup with Start up SeGW. Internal DHCP provides to SeGW the AP (eNB) IPsec tunnel static inner IP address and IKEv2 messages return the Internal DNS server IP address.
|
|
|
5
|
AP (eNB) sends DNS query to Internal DNS server to resolve EMS IP addresses from EMS FQDN.
|
|
|
6
|
AP (eNB) sends "Hello" messages to the list of candidate EMS IP addresses. AP (eNB) sends "Hello" messages to default port of 162.
|
|
|
7
|
Upon receiving a "Hello" message from AP (eNB), EMS determines if it is the Managing EMS for this AP (eNB) by comparing the AP (eNB) identity information (serial number) in the "Hello" message with the operator provisioned information in OAMInterface.provisionedEnbidentifier.
|
|
|
8
|
If there is a match, EMS registers itself as the Managing EMS by setting its active and standby EMS IP addresses and ports in emsActive AddressTable.
|
|
|
8a
|
AP (eNB) continues to send "Hello" messages forever. But each "Hello" message has an amount of time that the AP (eNB) has been sending "Hello" messages without a response. Non-managing SAMs read the "Hello" message and if the time exceeds a threshold, they raise an Orphan AP (eNB) alarm.
|
|
|
9
|
Managing EMS sends heartbeat to AP (eNB)
|
|
|
10
|
AP (eNB) sends heartbeat response to the Managing EMS.
|
|
|
11
|
AP (eNB) sends OAM Link Opened messages to all EMS IP addresses to which it had sent "Hello" messages
|
|
|
12
|
OAM link with IPsec is established. AP (eNB) is managed by EMS. AP (eNB) and Managing EMS begin Link Monitoring.
|
|
|
13
|
EMS downloads and activates the AP (eNB) target SW version according to the self-configuration policy
|
|
|
14
|
EMS automatically configures the AP (eNB) DB using pre-provisioned configuration according to the self configuration policy.
|
|
|
15
|
AP (eNB) resets and configures itself according to the AP (eNB) configuration
|
|
|
16
|
The Serving SeGW IP address will be provisioned by the EMS then AP (eNB) sets up the IPsec tunnel with the Serving SeGW (SeGW redirection)
|
|
|
17a
|
checks the GPS reported location vs operator-defined location. If there is a match, proceed to step 18. Match=expected lat, long within 10m of actual GPS lat, long. If there is a mismatch (or no GPS reported location, i.e., no GPS), AP (eNB) raises an alarm, includes serial # and GPS reported location info in the alarm, and sends the alarm to EMS.
|
|
|
17b
|
EMS forwards alarm to NetCool
|
|
|
17c
|
Manual intervention required to correct pre-provisioned profile
|
|
|
17d
|
corrected profile is imported to EMS
|
|
|
17e
|
The configuration is pushed to the AP (eNB) from EMS
|
|
|
17f
|
If IPsec is down - requires site visit
|
|
|
18
|
If CMS info is provisioned, AP (eNB) will perform certificate enrollment to obtain the operator certificate. AP (eNB) resets and sets up the IPsec tunnels using the operator certificate
|
|
|
19
|
AP (eNB) updates EMS - Ready for Service
|
|
|
20
|
EMS unlocks AP (eNB)
|
|
|
21
|
AP (eNB) ready for production service
|
