The full name of IN is Intelligent Network, and it is the combination of the existing network (switch & transmission layer)

and the intelligent network (intelligent network layer). As a high layer service network of switching network, IN can create and realized all kinds of new services such as PPS, PPT, VPN service. Intelligent Network implementation independence allows network operators to allocate functionality and resources within their networks and to efficiently manage their networks Wireless Intelligent Network performs the intelligent processing with the support of signaling system (SS7) network and large centralized database, while the traditional exchange only performs the basic call connection functions. In WIN, the whole system included SCP, SMP, CMP, SCEP,SSP/IP, SDP,FEP, SMAP, WEBSMAP, etc. SCP, SMP, SCEP, SDP, FEP, SMAP, WEBSMAP are belong to IN layer, which communicated by TCP/IP protocols, SSP/IP entities are in switch &

transmission layer, their communication system is SS7.

TELLIN-IN system: Huawei has developed a whole set of IN product including SSP, IP, SCP, SDP, SMP, SMAP, CMP and SCEP TELLIN IN system. The logical network architecture of TELLIN IN system is shown in this slide.

MSC is the core of the whole mobile communication system, providing the switching function. HLR is used to store the important static data of all the registered mobile subscribers controlled by this HLR, it stores and provides the information of the area where the mobile subscriber is roaming so that the routing information of the called party can be obtained for the call connection. SMP is the management center of IN. It forms a subscriber's information management network together with CMP and SMAP (SMS), and undertakes the function of service management and operating system.

SCP is the most important supporting equipment in the service operation. It exercises the IN services controlling and processing function in the whole IN system. It implements the service control function (SCF) and part of service data function (SDF) and accepts the control by SMS.

A Case for TELLIN-WIN solution (physical WIN structure) Main physical entities are included SCP, SMP, Report Server, Web Server ,OAM Server and I2000 Server, SMAP(PC) and SAU (USAU)

Other physical entities are firewalls, Routers, I2000 client (PC) and Report client (PC)

The functional entities that the HUAWEI UVC products provide include:

VMAP Server: Voucher Management Agent Point Server USSD: Unstructured Supplementary Service Data

VMP: Voucher Management Point

SMSC: Short Message Service Center

The processing flow of manual recharge is as follows: 1. User A goes to the customer service centre for recharge. The operator enters the password (or card number + password) of a recharge card and the number to be recharged through the VMAP interface. 2. VMP Server sends MML commands to the VMP. 3. The VMP forwards MML commands to the VCP to trigger the VCP service logic. 4. The VCP queries whether the resources and status of the recharge card are legal based on the recharge information. If yes, the VCP sends a recharge request to the SCP/IN that the recharged number belongs to based on the recharged number. 5. After authenticating and recharging the number to be recharged, the SCP/IN returns the result to the VCP. 6. The VCP returns the recharge result to VMP Server through which the returned result is parsed into HTML and displayed on the VMP recharge interface. 7. After successful recharge, the VCP sends the recharge result notification message to the SMSC through the GFEP. 8. The SMSC sends message to user A.

The third-party application can access the VMP via the MML command provided by the VMP to implement the recharge card management function. For the details of MML interfaces, see the MML interface specification that is released together with the UVC software version. The UVC provides the GFEP for diameter/web service protocol conversion. The USAU is required because the SS7 mode is used.

There are two networking modes for the UVC:

The VMP communicates with the VCP through RCOMM protocol that is also adopted between the VCP and the SCP/IN.

The VMP communicates with the VCP through RCOMM protocol. The VCP communicates with the SCP/IN through EXECUTE protocol.

The following description takes the second networking mode as an example to introduce the signaling flow of VMP manual recharge:

The VMP sends a recharge request to the VCP. The VCP queries the status of the recharge card, and then sends the recharge request to the SCP/IN to which the account to be recharged belongs.

The SCP/IN authenticates the account to be recharged, and then adds recharge resources and resource validity period to it. Then, the SCP/IN returns response to the recharge request to the VCP. The VCP sends a TC-END message to the SCP/IN to end the conversation between them. The VCP deducts resources and validity period from the recharge card and returns the recharge result to the VMP.

Message exchange during the recharging based on SCP/IN access:

The SCP/IN sends a card authentication request to the UVC. The authentication request contains the recharged number, calling number, and password of a recharge card. The UVC authenticates the recharge card. If the recharge card status is normal, the UVC locks the recharge card, and then returns the basic information about the recharge card to the SRS, including the recharge resource, validity period, and brand information. The SCP/IN recharges the user (add funds, resources and additional validity period to the users account) and then sends a card set request message to the UVC.

The UVC updates the status and resource information of the recharge card, unlocks the recharge card, and then sends a recharging confirmation response message to the SCP/IN.

Message exchange during the card authentication and reset:

The SRS/IPCC/Third party sends a card authentication request to the UVC. The authentication request contains the recharged number, calling number, and password of a recharge card. The UVC authenticates the recharge card. If the recharge card status is normal, the UVC locks the recharge card, and then returns the basic information about the recharge card to the SRS, including the recharge resource, validity period, and brand information. The SRS/Third party sends a recharge request to the CCBS/Other Charging system. The CCBS/Other Charging system returns a message indicating that the recharge is successful. Then the SRS/Third party sends a card reset request to the UVC. The UVC sends the status of the recharge card to be used.

The SRS/IPCC/Third party notifies the subscriber of the recharge result.

Message exchange during the recharging based on IPCC/SRS/Third party access:

The SRS/IPCC/Third party sends a card authentication request to the UVC. The authentication request contains the recharged number, calling number, and password of a recharge card. The UVC authenticates the recharge card. If the recharge card status is normal, the UVC locks the recharge card, and then returns the basic information about the recharge card to the SRS, including the recharge resource, validity period, and brand information. The SRS/Third party sends a recharge request to the CCBS/Other Charging system. The CCBS/Other Charging system returns a message indicating that the recharge is successful. Then the SRS/Third party sends a card reset request to the UVC. The UVC sends the status of the recharge card to be used.

The SRS/IPCC/Third party notifies the subscriber of the recharge result.

Message exchange during the recharging based on UVC IVR access

A subscriber triggers the UVC IVR flow by dialing an access code. The UVC prompts the subscriber to select a language type.

After the subscriber selects the language type, the UVC prompts the subscriber to enter the password of the recharge card.
The subscriber enters the password of the recharge card, and then the UVC checks the status of the recharge card. If the status of the recharge card is normal, the UVC locks the recharge card. The UVC plays a voice to prompt the subscriber to enter the recharged number. After the subscriber enters the recharged number, the UVC analyzes the recharged number.

After analyzing the recharged number, the UVC sends the message for adding money to the OCS/CCBS/Other charging system. If the OCS system returns a message normally, the UVC sends the message for confirming to add money.

Message exchange during the recharging based on UVC USSD Access:

A subscriber sends a USSD recharge request. The recharge request contains the password of a recharge card and the recharged number.

The MSC/HLR/USSD Server sends the recharge request to the UVC. The recharge request contains the password of a recharge card and the recharged number.
The UVC analyzes the recharged number and authenticates the recharge card. If the recharge card status is normal, the UVC locks the recharge card. The UVC sends the message for adding money to the OCS/CCBS/Other charging system. If the OCS system returns a message normally, the UVC sends the message for confirming to add money.

The UVC notifies the subscriber of the recharge result.

Message exchange during the recharging based on UVC SMS access:

The SMSC sends a recharge request to the UVC. The recharge request contains the password of a recharge card and the recharged number.

The UVC analyzes the recharged number and authenticates the recharge card. If the recharge card status is normal, the UVC locks the recharge card.
The UVC sends the message for adding money to the OCS/CCBS/Other charging system. If the OCS system returns a message normally, the UVC sends the message for confirming to add money. The SMSC notifies the subscriber of the recharge result.