GMSC

The Gateway Mobile Switching Centre (GMSC) is a special kind of MSC that is used to route calls outside the
mobile network. Whenever a call for a mobile subscriber comes from outside the mobile network, or the subscriber
wants to make a call to somebody outside the mobile network the call is routed through the GMSC.
In practice, the GMSC is just a function that can be part of a MSC.

A Mobile Station Roaming Number (MSRN) is an E.164 defined telephone number used to route telephone calls
in a mobile network from a GMSC (Gateway Mobile Switching Centre) to the target MSC (see Network Switching
Subsystem). It can also be defined as a directory number temporarily assigned to a mobile for a mobile terminated
call. A MSRN is assigned for every mobile terminated call, not only the calls where the terminating MS lives on a
different MSC than the originating MS. Although this seems unnecessary since many vendors' VLR's are integrated
with the MSC, the GSM specification indicates that the MSC and VLR (Visitor Location Register) do not need to
reside on the same switch. They are considered two different nodes as they have their own routing addresses.
i.e.the MSRN is one of the returned parameters into SRI_Response message. In particular the MSRN is used into
an MNP scenario (in this case it can be modified as 'RgN + MSISDN').
Another temporary address that hides the identity of a subscriber. The VLR generates this address on request from
the MSC,and the address is also stored in the HLR. MSRN contains the current visitor country code(VCC), the
visitor national destination code (VNDC), the identification of the current MSC together with the subscriber number.
If we have all the MSC working as a GMSC like the latest technologies so what would be the states of the MSRN ?
we can use it only for test to route the calls to a specific MSC otherwise we don't need it to use it.
The Mobile Subscriber Roaming Number (MSRN) is a temporarily telephone number assigned to a mobile station
which roams into another numbering area. (This is usually another country). This number is needed by the home
network to forward incoming calls for the mobile station to the network it visits. It is stored in the Home Location
Register (HLR).
This number can be assigned by the visited network upon initial registration, or it can be assigned on a per call
basis. In the latter case the number has to be requested by the home network (HLR) for each incoming call before it
can forward the call to the visiting network.

When an MS roams to another MSC service area, the MSC will allocate a temporary roaming number for routing. The
roaming number format is the same with the MSISDN format of the visited area. When the MS leaves the area, VLR and
HLR will delete the roaming number so that the number can be re-allocated to other MS.
Example of MSRN allocation process: local call subscriber can send MSISDN to GSMC and HLR through PSTN. HLR
requests the visited MSC/VLR to allocate a temporary roaming number and sends this number to HLR after allocating.
HLR sends to MSC such relevant parameter of the MS as IMSI, at the same time informs GMSC of the roaming number
of the MS, then GMSC can select route, and complete the task: local call subscriber ->GMSC->MSC-> MS connection.
MSRN adopts E.164 numbering plan.

With 2G
o With GPRS (General Packet Radio Service), you have a theoretical transfer speed
of max. 50 Kbps.
o With EDGE (Enhanced Data Rates for GSM Evolution), you have a theoretical
transfer speed of max. 250 Kbps.
With 3G or UMTS (Universal Mobile Telecommunications System), you have a theoretical
transfer speed of max. 384 Kbps.
With 3G+
o With HSDPA (High-Speed Downlink Packet Access), you have a theoretical transfer
speed of max. 7.2 Mbps.
o With HSPA+ (High-Speed Packet Access +), you have a theoretical transfer speed
of max. 42 Mbps.
With 4G or LTE (Long Term Evolution), you have a theoretical transfer speed
of max. 129 Mbps.


Higher hierarchical levels[edit]
As is the case with level 1 of the plesiochronous digital hierarchy (2 Mbit/s), the higher levels of multiplexing are
carried out bit by bit (unlike the multiplexing of 64 kbit/s channels in a 2 Mbit/s signal, which is byte by byte), thus
making it impossible to identify the lower level frames inside a higher level frame. Recovering the tributary frames
requires the signal to be fully demultiplexed.
The higher hierarchical levels (8,448, 34,368, and 139,264 Mbit/s, etc.; referred to as 8, 34, and 140 Mbit/s for
simplicity) are obtained by multiplexing four lower level frames within a frame whose nominal transmission rate is
more than four times that of the lower level (see Table 3), in order to leave room for the permitted variations in rate
(justification bits), as well as the corresponding FAS, alarm, and spare bits.
E2: multiplexing level 2: 8 Mbit/s[edit]
The 8 Mbit/s frame structure is defined in the ITU-T Rec. G.742. The frame is divided into four groups:
Group I contains the FAS, with sequence "1111010000"; the A-bit (remote alarm); the S-bit (spare); and 200 T-
bits (tributary) transporting data.
Groups II and III contain a block of four J-bits (justification control) and 208 T-bits transporting data.
Group IV contains a block of four J-bits, a block of R-bits (justification opportunity), one per tributary, and 204 T-
bits. To check whether R-bits have been used, the J-bits are analyzed in each of the groups II, III, and IV (there
are three per tributary). Ideally the R-bit does not carry useful information on 42.4% of the occasions. In other
words, this percentage is the probability of justification or the insertion of stuffing bits.
E3: multiplexing level 3: 34 Mbit/s[edit]
The structure of this frame is described in the ITU-T Rec. G.751 (see Figure 20). As in the previous case, the frame
is divided into four groups:
Group I contains the FAS, with sequence "1111010000"; the A-bit (remote alarm); the S-bit (spare); and 372 T-
bits (tributary) transporting data.
Groups II and III contain a block of four J-bits (justification control) and 380 T-bits transporting data.
Group IV contains a block of four J-bits, a block of R-bits (justification opportunity) one per tributary, and 376 T-
bits. To check whether R-bits have been used, the J-bits are analyzed in each of the groups II, III, and IV (there
are three per tributary). Ideally the R-bit does not carry useful information on 43.6% of the occasions.
E4: multiplexing level 4: 140 Mbit/s[edit]
The structure of this frame is described in the ITU-T Rec. G.751 (see Figure 20). In this case, the frame is divided
into six groups:
Group I contains the FAS, with sequence "111110100000"; the A-bit (remote alarm); the S-bit (spare); and 472
T-bits (tributary) transporting data.
Groups II, III, IV, and V contain a block of four J-bits (justification control) and 484 T-bits transporting data.
Group VI contains a block of four J-bits, a block of R-bits (justification opportunity), one per tributary, and 376 T-
bits. To check whether R-bits have been used, the J-bits are analyzed in each of the groups II, III, IV, V, and VI
(there are five per tributary). Ideally the R-bit does not carry useful information on 41.9% of the occasions.
The PDH hierarchy, with four levels from 2 to 140 Mbit/s. Higher rates are not standard.
Level Standard Rate Size Frame/s Code Amplitude Attenuation
E1 G.704/732 2.048 Mbit/s 50 ppm 256 bits 8,000 HDB3 2.37-3.00 V 6 dB
E2 G.742 8.448 Mbit/s 30 ppm 848 bits 9,962.2 HDB3 2.37 V 6 dB
E3 G.751 34.368 Mbit/s 20 ppm 1536 bits 22,375.0 HDB3 1.00 V 12 dB
E4 G.751 139.264 Mbit/s 15 ppm 2928 bits 47,562.8 CMI 1.00 V 12 dB

OCS
As the network is leaning towards convergence and the telecom services are rapidly developing, the
operator's business model gradually shifts from communications-centric to service-centric. The
operators, while reaping handsome profits from the ever-increasing cornucopia of offerings, are
pressured to come up with a new charging platform that supports various charging modes (e.g.,
content-based charging and volume-based charging), and provide real-time control of chargeable
services.
The traditional offline charging system which only collects charging information after a service is
rendered is unable to prevent the huge revenue loss caused by service overdraft. Intelligent Network
(IN), which provides online charging capabilities, features poor market adaptability, though it is
popular in the telecoms industry.
In the traditional IN-based system, prepaid users can't enjoy the same service packages and tariff
plans as the postpaid users can due to the technical limitations. However, they also demand for the
same services that the postpaid users have. As the current charging system falls far short of the new
charging requirement, operators need to find a solution that gives them a greater pricing flexibility
which naturally gives birth to the Online Charging System (OCS).
Traditional IN system
Before looking into the advantages of the OCS, the article will first look at the traditional charging
mode and its inherent defects.
In the prepaid charging mode, the IN system performs real-time charging. The IN-based prepaid
system authenticates the user's identity and checks the account balance before giving authorization
to use the relative service; immediately deducts related fees from the user account; and terminates
the service upon expiration of the user's account balance. Therefore, the IN-based prepaid charging
is actually a type of online real-time processing. The IN-based prepaid charging mode features
excellent real-time revenue control, but lacks the flexibility to support more complex tariff plans and
service bundles. It is hard for a carrier to frequently change the tariff policies with the IN platform.
Advantages of OCS
The OCS is to provide unified online charging functions separated from all network elements (NEs)
such as service control point (SCP), short message service center (SMSC), and multimedia message
service center (MMSC). It has the following advantages:
# Support the prepaid services development
The prepaid services are popular among mobile users as it is a low-risk option. As the online
charging system gives prepaid users the access to more services, it will undoubtedly facilitate the
development of prepaid services.
# Enable effective risk mitigation
The mobile services run a greater risk for revenue leakage than the fixed ones. With the
development of high-value, high-risk, and high-credit-limit services, guaranteeing that operators are
paid for the services delivered is critical. The OCS enables real-time traffic monitoring so as to help
operators to effectively reduce the possibility of revenue leakage.
# An effective way to attract customers
Since the charging is independent of the service control, it is possible for the prepaid subscribers to
enjoy the services that already exist for the postpaid subscribers. The OCS allows prepaid users to
have high credit limit and gain access to high-risk but attractive services (e.g., international
roaming), helping operators develop their markets.
# Convergent billing platform, lowering CAPEX and OPEX
When new tariff packages or service bundles are launched, it is necessary to upgrade the traditional
IN SCP that is integrated with a billing engine. The OCS, as the basis of convergent billing platform,
only requires small investment at the initial stage, enabling operators to dramatically reduce the
capital expenditure (CAPEX) and operation expenditure (OPEX).
# Improve customer loyalty
The new generation of charging solution is a great marketing tool that can help operators attract
customers with its flexible service bundling and pricing capabilities, enhancing customers' loyalty.
# Provide opportunities to optimize network structure
The IN-based prepaid solution doesn't have a well-optimized network structure which requires large
investments. It also can't expedite the offering of services and meet the challenges of the market. In
addition, it is also defective in terms of stability, for example, in the IN mode, the call will not be
connected if the SCP breaks down. The OCS can avoid such a problem by switching to the hot billing
mode as they share information such as customer and service profiles.
# Meet industrial development trend
The OCS solution is compliant with the 3GPP standard. It represents the inevitable trend of the
telecoms network, making it a necessary choice for operators.
# Python script
With the memory database technology, and the basic operating system that supports the task
distribution function and the telecom-level information communication system (ICS), ZTE's OCS-
based convergent billing system can analyze and execute 500,000 command lines per second with
the IBM P550 (4x1.65CPU) cluster.
As the traditional IN-based prepaid solution lacks the flexibility to support different business models
and payment plans, operators can't offer prepaid users with the same services that the postpaid
users enjoy. To maximize the potential of the enormous prepaid market, operators need to shift
from the legacy systems to the online charging system in order to provide enhanced charging
capabilities for today's advanced services, as well as of the future's