. . In WIN. SMP. SCP. 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. VPN service. SDP. IN can create and realized all kinds of new services such as PPS. SCEP. SMAP. WEBSMAP are belong to IN layer. WEBSMAP. etc. SMP. which communicated by TCP/IP protocols. CMP. PPT. As a high layer service network of switching network.FEP. SCEP. SDP. and it is the combination of the existing network (switch & transmission layer) and the intelligent network (intelligent network layer). their communication system is SS7. .SSP/IP. SMAP. the whole system included SCP. SSP/IP entities are in switch & transmission layer. while the traditional exchange only performs the basic call connection functions. The full name of IN is Intelligent Network. FEP. SMP. SCP is the most important supporting equipment in the service operation. SCP. SMP is the management center of IN. IP. SMAP. and undertakes the function of service management and operating system. providing the switching function. MSC is the core of the whole mobile communication system. SDP. The logical network architecture of TELLIN IN system is shown in this slide. TELLIN-IN system: Huawei has developed a whole set of IN product including SSP. HLR is used to store the important static data of all the registered mobile subscribers controlled by this HLR. It implements the service control function (SCF) and part of service data function (SDF) and accepts the control by SMS. 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. CMP and SCEP – TELLIN IN system. It exercises the IN services controlling and processing function in the whole IN system. . It forms a subscriber's information management network together with CMP and SMAP (SMS). SMP. Web Server . A Case for TELLIN-WIN solution (physical WIN structure) Main physical entities are included SCP. Report Server.OAM Server and I2000 Server. I2000 client (PC) and Report client (PC) . Routers. SMAP(PC) and SAU (USAU) Other physical entities are firewalls. . 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 USAU: Universal Signaling Access Unit SCP: Service Control Point SMAP: Service Manage Agent Point MSC: Mobile Switching Center SSP: Service Switching Point GFEP: General Front End Processor SMSC: Short Message Service Center HLR: Home Location Register OAM: Operations. Administration and Maintenance FTP: File Transfer Protocol RBI: Recorded Bill Interface . 7. 8. The VMP forwards MML commands to the VCP to trigger the VCP service logic. After authenticating and recharging the number to be recharged. After successful recharge. 2. VMP Server sends MML commands to the VMP. 3. the SCP/IN returns the result to the VCP. The operator enters the password (or card number + password) of a recharge card and the number to be recharged through the VMAP interface. 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. 4. the VCP sends a recharge request to the SCP/IN that the recharged number belongs to based on the recharged number. If yes. . The SMSC sends message to user A. 5. the VCP sends the recharge result notification message to the SMSC through the GFEP. The processing flow of manual recharge is as follows: 1. User A goes to the customer service centre for recharge. The VCP queries whether the resources and status of the recharge card are legal based on the recharge information. see the MML interface specification that is released together with the UVC software version. The third-party application can access the VMP via the MML command provided by the VMP to implement the recharge card management function. The UVC provides the GFEP for diameter/web service protocol conversion. For the details of MML interfaces. The USAU is required because the SS7 mode is used. . . the SCP/IN returns response to the recharge request to the VCP. The VCP communicates with the SCP/IN through EXECUTE protocol. The SCP/IN authenticates the account to be recharged. and then sends the recharge request to the SCP/IN to which the account to be recharged belongs. Then. 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 VCP deducts resources and validity period from the recharge card and returns the recharge result to the VMP. and then adds recharge resources and resource validity period to it. The VCP queries the status of the recharge card. . 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 VMP communicates with the VCP through RCOMM protocol. The VCP sends a TC-END message to the SCP/IN to end the conversation between them. unlocks the recharge card. The authentication request contains the recharged number. The UVC updates the status and resource information of the recharge card. and then sends a recharging confirmation response message to the SCP/IN. The UVC authenticates the recharge card. calling number. The SCP/IN recharges the user (add funds. If the recharge card status is normal. and then returns the basic information about the recharge card to the SRS. validity period. Message exchange during the recharging based on SCP/IN access: The SCP/IN sends a card authentication request to the UVC. . and brand information. and password of a recharge card. resources and additional validity period to the user’s account) and then sends a card set request message to the UVC. including the recharge resource. the UVC locks the recharge card. and then returns the basic information about the recharge card to the SRS. the UVC locks the recharge card. and password of a recharge card. The UVC authenticates the recharge card. validity period. calling number. including the recharge resource. and brand information. The SRS/Third party sends a recharge request to the CCBS/Other Charging system. Then the SRS/Third party sends a card reset request to the UVC. The CCBS/Other Charging system returns a message indicating that the recharge is successful. The UVC sends the status of the recharge card to be used. If the recharge card status is normal. . The authentication request contains the recharged number. The SRS/IPCC/Third party notifies the subscriber of the recharge result. Message exchange during the card authentication and reset: The SRS/IPCC/Third party sends a card authentication request to the UVC. and brand information. Then the SRS/Third party sends a card reset request to the UVC. The authentication request contains the recharged number. including the recharge resource. the UVC locks the recharge card. The SRS/IPCC/Third party notifies the subscriber of the recharge result. If the recharge card status is normal. The CCBS/Other Charging system returns a message indicating that the recharge is successful. and password of a recharge card. validity period. The UVC sends the status of the recharge card to be used. . The SRS/Third party sends a recharge request to the CCBS/Other Charging system. The UVC authenticates the recharge card. and then returns the basic information about the recharge card to the SRS. calling number. 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 UVC sends the message for confirming to add money. the UVC locks the recharge card. the UVC prompts the subscriber to enter the password of the recharge card. the UVC sends the message for adding money to the OCS/CCBS/Other charging system. The UVC prompts the subscriber to select a language type. . the UVC analyzes the recharged number. The UVC plays a voice to prompt the subscriber to enter the recharged number. and then the UVC checks the status of the recharge card. After the subscriber enters the recharged number. Message exchange during the recharging based on UVC IVR access A subscriber triggers the UVC IVR flow by dialing an access code. After analyzing the recharged number. If the status of the recharge card is normal. If the OCS system returns a message normally. The subscriber enters the password of the recharge card. After the subscriber selects the language type. . If the recharge card status is normal. The recharge request contains the password of a recharge card and the recharged number. The recharge request contains the password of a recharge card and the recharged number. Message exchange during the recharging based on UVC USSD Access: A subscriber sends a USSD recharge request. If the OCS system returns a message normally. the UVC sends the message for confirming to add money. The MSC/HLR/USSD Server sends the recharge request to the UVC. the UVC locks the recharge card. The UVC notifies the subscriber of the recharge result. The UVC analyzes the recharged number and authenticates the recharge card. The UVC sends the message for adding money to the OCS/CCBS/Other charging system. If the recharge card status is normal. Message exchange during the recharging based on UVC SMS access: The SMSC sends a recharge request to the UVC. . the UVC locks the recharge card. The UVC sends the message for adding money to the OCS/CCBS/Other charging system. the UVC sends the message for confirming to add money. If the OCS system returns a message normally. The UVC analyzes the recharged number and authenticates the recharge card. The SMSC notifies the subscriber of the recharge result. The recharge request contains the password of a recharge card and the recharged number.
Report "0IB401101 UVC System Introduction ISSUE1.00"