This section provides a description of the IPNE feature.
IPNE (IP Network Enabler) is a MINE client component running on various network nodes within operator's network (P-GW, GGSN, HA, or HNBGW), to collect and distribute session/network information to MINE servers. The MINE cloud service provides a central portal for wireless operators and partners to share and exchange session and network information to realize intelligent services.
The information is shared between the MINE server and IPNE service in the form of XML data. The core object in the IPNE service is the XMPP protocol engine. There is one XMPP protocol engine instance for each configured MINE server peer. The engine implements the XMPP protocol using FSM.
All information that is shared is derived from the context at that instance in time. An IPNE service level scheduler is also implemented to rate-control the feed and notification activities on all the handles to avoid overload which would affect call processing and data path performance.
Relationships to Other Features
This section describes how the IPNE service is related to other features.
One of the following GW services must be configured on the StarOS before IPNE can be configured:
Refer to the GGSN Administration Guide, the HA Administration Guide, the HNBGW Administration Guide and the P-GW Administration Guide for configuration procedures.
The MINE cloud service provides a central portal for wireless operators and partners to share and exchange session/network information to realize intelligent services. A MINE client component is running on various network nodes within operator's network, e.g. PGW, HA, to collect and distribute session/network information to MINE servers. The client is IPNE.
The IPNE client runs on the StarOS as a configurable service. The Enhanced Charging Service (ECS) component interacts with the IPNE client in order to fulfill the defined requirements.
For best IPNE performance, the ECS component should provide the following functionality:
- Flow information parameters
should be provided by ECS to IPNE:
- Tuple information
- User Agent
- Application protocol
- Flow creation time
NBR information parameters should be provided by ECS to IPNE:
- NAT-IP address
- Start Port
- End Port
ECS should provide the above parameters for all active flows in a response corresponding to the query from the MINE server indexed on the subscriber's call id.
For the subscription that is installed by the IPNE client on a subscriber's call id, ECS should send a notification message to the IPNE client whenever a subscribed trigger is detected.