# MSS

Top Previous Next

The MSS application entities include MSC, VLR, HLR, AUC, PPS, SMSC, EIR, VSS, AAS, SMEG, OPPS, MRFC, iPALIM, iRLS and MHC. Any alarm will be displayed in red text. The basic status of application entity is listed in the following table.

Basic Status | Descriptions
Basic status | Basic status of the application entity. Any failure will bring alarm.
Dual server mode | Status of SYNC main server which is responsible for performing automatically data sync every 30 minutes via multicasting the sync data to the slave server. The 0 server is default main server
Refresh time | The status page refreshes itself every 10 seconds
License | Certified maximum subscriber capacity of this application server.
Users | The number of subscribers registered in this application server.
Serial number | The read-only UltraWAVE system serial number of Altobridge controls.

| Mobile Switching Center (MSC)

The MSC entity is integrated in the MSS. This server is responsible for call control, processing and PSTN access for the UltraWAVE system.

| Visitor Location Register (VLR)

The VLR entity is integrated in the MSS. The VLR stores information for all subscribers who enter the present coverage area. It also registers mobile subscriber identity, location identity and service parameters for the subscribers. It allocates Mobile Subscriber Roaming Numbers (MSRN) for terminating calls to subscribers located in its area.

| Home Location Register (HLR)

The HLR entity is integrated in the MSS. The HLR is a database used for storage and management of subscriber information. The HLR stores permanent subscriber data including a subscriber's service profile, location information and activity status. When a mobile user buys a subscription from the service provider, the user is registered in the HLR.

The basic functions of the HLR includes:

•Storage of the subscriber database

•Provisioning of data for the VLR

•Subscriber data query and modification via EMS GUI

•Periodic database update queries for VLR update

The information stored in the HLR includes the following:

•Subscription information

•Location information enabling the charging and routing of calls towards the MSC where the Mobile Station (MS) is registered, for example the MS Roaming Number, the VLR Number, the MSC Number and the Local MS Identity.

•Telecommunication and bearer services subscription information

•Service restrictions - roaming limitations

•Parameters attached to supplementary services

| Authentication Center (AUC)

The optional AUC entity is integrated in the MSS. The AUC server provides authentication and encryption parameters that verify the MS user's identity and guarantee the confidentiality of each call.

The basic functions of the AUC include:

•Authentication service provisioning management

•Data encryption, security and access protection

•Generation of security triplets for the MS

•Cooperation with the HLR

•Subscriber data query and modification via EMS GUI

| Pre-Paid System (PPS)

The optional PPS entity provides a solution for the mobile prepaid service. The PPS contains three operational modules: Accounting, Prepaid and Tariff.

The Accounting module is responsible for storing subscriber information. The information stored includes:

•Account balance

•Validity

•Service status

•Tariff ID and tariff area ID

•Real-time charge calculation

•Tariff query

•Call duration calculation

•Recharging subscriber accounts

The Prepaid module stores the information of the recharge cards and processes account recharge. The Tariff module stores the tariff sheets and processes tariff queries for each call.

The PPS is also capable of performing the following functions:

•Subscriber authentication

•Real time call debiting

•Dual server load sharing redundancy

•User data storage, searching and modification

•Dual server data synchronization, backup and restoration

•Web page-based provisioning interface

•User data and recharge card import

•Tariff table and multiple rate schedules

•Multi-lingual audio announcements

| Short Message Service Center (SMSC)

The optional SMSC entity provides the mechanism of delivering short messages over mobile networks. It is a store and forward way of transmitting messages to and from mobiles. The text message from the sending mobile is stored in a SMSC which then forwards it to the destination mobile. In the case that the recipient is not available the short message is stored and can be sent at a later time.

Each short message is less than 160 characters (Latin alphabets) or 70 characters (Chinese or Arabic). The SMS is sent using signaling channels only. The messages can be transferred simultaneously with the voice/data/fax service over a GSM network.

The SMSC performs the following basic functions:

•MS originated SMS to MS

•Prepaid account balance query

•Short Messages

•Storage, query and statistics of SMS

•Support Short Message Peer-to-Peer (SMPP)

| Equipment Identity Register (EIR)

The optional EIR entity is a database that contains information on the identity of mobile equipment to prevent calls from stolen, unauthorized or defective mobile stations. Each mobile station is uniquely identified by its IMEI (International Mobile Equipment Identity), and it is this identity which may be checked against the EIR to check the validity of the handset. A white list number is a legal IMEI that can pass the EIR verification.

| Voice Mail System (VMS)

The optional IP VMS entity is a value added peripheral of the UltraWAVE system. The VMS provides voice mail service to the calling party when the called party is busy, no answer, not reachable or switched off. When a new voice message is received, the VMS notifies the host by a short message. Subscribers can receive and retrieve their messages and maintain their mailboxes (set greetings, language and password) at any time from anywhere. The VMS functions along with the SMSC to provide message indication.

A single high-capacity VMS can support up to 100K subscribers. The VMS stores voices and syntax of 5 languages to support different countries without modifying software or recording new voice. The subscriber may select one of the five languages as the greeting language.

| Audio Announcement System (AAS)

The AAS entity provides multi-lingual audio announcements for unattainable call and prepaid service. This can be done over 60 channels to notify subscribers their call status or prepaid account information. The announcement can be recorded and the playback can be flexibly configured to meet the specific requirements. The AAS is connected to the MSC using BICC interfaces over virtual connections.

| SMS Email Gateway (SMEG)

The SMS Email Gateway (SMEG) entity is a software application that provides bi-directional SMS to email support, allowing email messages to be sent to SMS recipients, and vice versa. The SMEG software may reside in the UltraWAVE EMS server or run on a standalone server.

The UltraWAVE Gateway relays short messages and internet email messages between the UltraWAVE Short Message Center (SMSC) and the host email server. It links to the host email server and short message center via SMTP and SMPP respectively. UltraWAVE Gateway routes email messages and short messages between them with appropriate format conversion.

| Open-Prepaid-Roaming Public- Private System (OPPS)

The UltraWAVE Open-Prepaid-Roaming Public-Private System (OPPS) entity is a combination of two systems: the Open-to-all Prepaid Roaming System (OPR) and the Intelligent MAP-D Multiplexer System (IMDX).

•The OPR System enables the existing UltraWAVE Prepaid System to provide temporary services to any visiting GSM users; even they are from PLMN without local roaming agreement in place. The OPR doesn’t require GSM visitors to change their SIM cards. OPR provides prepaid services to the visitors with their home SIM cards.

•The IMDX System enables the R9 System to provide “private” communication services. The IMDX provides private, hybrid and public user services to the GSM subscribers. Operator may restrict private users to make/receive calls to/from private users only and public users to make/receive calls to/from public users only; while Hybrid users can make/receive calls from both private and public users. IMDX allows the operator to use the existing R9 System to provide GSM services to employee users as a private communication tool for their daily works.

| Multimedia Resource Function Controller (MRFC)

The Multimedia Resource Function Controller (MRFC) and the Multimedia Resource Function Processor (MRFP) handle the bearer-related services. The MRFC and the MRFP are deployed in logical pairs and provide bearer functions for sessions. The MRFC acts as an interpreter in the user plane while the MRFP performs the actual operations.

The MRFC controls such things as conferencing, announcements to a user, or bearer transcoding. As an aside, transcoding is the term that defines the conversion from one form of codec to another. The MRFC receives the SIP signaling from the SIP server and uses the Media Gateway Control Protocol instructions to control the MRFP.

The MRFP does all of the work on the user-plane and provides the resources that are requested by the MGCP instructions, which were issued by the MRFC. Some of these functions are listed below:

•Mixing of the incoming media streams that multiple parties would have created as part of a conferencing service.

•Sourcing of the media stream that would be used as an announcement message for a user. The tone that sounds at the start of an instant message is an example of an announcement message that could come from the MRFP. The MRFP also sends along the stream if some processing is required.

| IP Private A-Link Intelligent Multiplexer (iPALIM)

IP Private A-link Intelligent Multiplexer (iPALIM) is an application server of the UltraWAVE soft switch system to connect the local Inter-Reach Office (IRO) network to Public Mobile Network (PLMN) via A-interface. It allows the IRO to perform as a self-contained GSM system or a virtual BSC of the PLMN, depending on the desired service and user type. iPALIM monitors the messages originated by a subscriber to determine his user type, and selects the optimal way to route the call.

iPALIM provides two types of services - private service and public service.

•iPALIM routes calls of private users to the local MSC for local switching within the IRO network. The private users may also make calls to local PSTN or PBX if it is attainable.

•For public users, iPALIM routes calls to the PLMN MSC, bypassing the IRO soft-switch. iPALIM makes IRO appears as a BSC to the PLMN MSC. iPALIM is transparent to the user and to the IRO MSC. Moving into and out of the IRO is seamless to the public user.

| Intelligent RTP Local Switching Controller (iRLS)

Intelligent RTP Local Switching (iRLS) function is a software application for helping the operators achieves significant saving in the transmission bandwidth between the core network and the rural/remote areas.

In standard GSM architecture, calls are routing to the MSC even if the calling and the called parties are in the same BSC zone. iRLS enables the system to route calls locally whenever the calling and called parties are in the same BSS zone; hence saving the backhaul transmission bandwidth. iRLS only controls the routing of the call traffic, the call signaling is still under the control of the host MSC.

| Multisite HLR Coordinator (MHC)

Multisite HLR Coordinator (MHC) supports distributed HLR across UltraWAVE R4S nodes of a mesh network through HLR data replication and synchronization. Automatic replication and synchronization of HLR data across multiple UltraWAVE R4S node sites enable subscribers to register to the Mesh UltraWAVE R4S GSM network at any nodes ‘locally’. MHC must attaches to a UltraWAVE R4S HLR - the ‘host’ HLR of the coordinator. The principal duty of MHC is to cooperate with other meshed MHC to synchronize the HLR data among the UltraWAVE R4S nodes in a mesh network. In order to synchronize the HLR among the nodes of a Mesh UltraWAVE R4S network, a MHC will broadcast the alterations of its host HLR to other MHC and will update its host HLR according to the alterations received from other MHC. MHC supports dual system architecture of UltraWAVE R4S HLR. Each HLR of a dual HLR system will has one MHC attached.

1.2.2.2