Manual

General Feture description
•
IPNE client is a service running within the SMGR context PGW service or HNBGW service
•
Any external service that wants to interact with IPNE should call IPNE API to create an IPNE handle
for each session. All subsequent interaction between external service and IPNE will go through this
handle, for example:
◦
IPNE will call back HNBGW session through this handle to collect any session information when
a query is received from MINE server
◦
HNBGW session will submit a feed through this handle if any changes occur in the parameters
dynamically
•
The core object in IPNE service is the XMPP protocol engine, XMPP protocol is implemented using
FSM . For every configured MINE server peer, there is one XMPP protocol engine instance.
IPNE Requirements
•
Only one IPNE service should be associated to HNBGW service at one time
•
IPNE service is allowed to associated/disassociated HNBGW
•
HNBGW should provide the following mandatory session information to IPNE client:
◦
HNB Identity
◦
HNB Location Information
◦
PLMN ID
◦
Cell ID
◦
LAC
◦
RAC
◦
SAC
◦
UE Identity at UE registration
•
HNBGW may provide the following optional information to IPNE client:
◦
CSG ID
◦
Service Area for Broadcast
◦
HNB Cell Access Mode
•
HNBGW should also send the information stated above to MINE server at the time of HNB/UE
registration
•
HNBGW should provide IPNE Client with session information for MINE server query for a specific
call ID identifying a specific subscriber in the system
•
HNBGW should maintain a subscription status from MINE server for a specific call-id. Whenever
HNBGW detects a change in the subscription parameters, it should notify IPNE client with the changed
value. IPNE client should then notify MINE server
HNB-GW Administration Guide, StarOS Release 19
27
HNB Gateway in Wireless Network
IPNE services enhancement