EKTEL Weblog

Short Message Service Center (SMSC)

The SMSC is mostly integrated with the IW/GMSC, that is, it has the functions of IW/GMSC to connect the SC with PLMN. Here, the GMSC receives short messages from the SMSC, requests routing information from the HLR, and forwards the short messages to the VMSC/SGSN of the mobile stations, while IWMSC receives short messages from PLMN and sends them to the receiving SMSC.

Mobile Base Station Transceiver(BTS) Configuration

Introduction •BTS configuration is determined by the traffic volume and the traffic distribution. •BTS configuration is associated with the number of the TRXs and the antenna system. •BTS can be omni directional •BTS can be sectored. •Number of TRXs can vary from site to site and that number determines the BTS configuration of that site. [...]

Interface of BTS with BSC(Base Station controller) and MS(Mobile Station)

Allocation of Entropies for Tri-Partite System

Allocation of Entropy for Tri-Partite System composed of quantum states with the following density matrices: Qa = , Qb = and Qc = forms a convex cone. The composite system ingredients were varied to obtain set of entropic values. For example, system A is in 10%, system B is in 40% and system C is [...]

Allocation of Entropy for Bipartite Quantum System

The allocation of Entropy of a Bipartite system has been proved to form a Convex cone. This can be found in the IEEE paper authored by Nicholas Pippenger. Here I am taking two bipartite system as: 1. Mixture of |0> and |1> 2. Mixture of |0> and |+> In each case of the bipartite system [...]

3D graph of allocation of Entropy for Bipartite System

Microwave Radio Installation and Commissioning

In Mobile Network, microwave radio are used to transfer data between BTS sites, between BTS and BSC or MSC. There are both advantages and disadvantages of using Microwave Radio links. Microwave radio communication is normally used for sites which are located in rural areas where site accessibility is difficult. It is because the cost of [...]

SMSC SMPP Server

Posted by admin on January 6th, 2012

SMPP(Short Message Peer to Peer) is a standardized protocol that handles the communication between SMSC and other SMS entities. It is an interface between the SMSC and NON-PLMN SMEs ( Short Message Entity). Typically it specifies the interface used between the SMSC and ESME ( External Short Message Entity) systems. This SMPP protocol may be implemented over a variety of underlying communications protocols X.25 or TCP/IP over internet or leased line by pluging in the IP cables into the SMPP server and opening the correct SMPP port.

The diagram below shows how ESME is connected to the SMSC via the SMPP server (SMPP gateway).

Fig: ESME to SMSC Interconnection (click to enlarge)

The SMPP Agent (process) is responsible for maintaining the communication link with the ESME, accomplishing the conversion of the SMPP standard message and the internal message of the SMSC ( Short Message Service Centre ) system, and providing the external short message entity (ESME) with the open interface to access the SMSC system. The current version of SMPP protocol is 3.4 (SMPP3.4).

As explained in the communication between ESME and SMSC servers post, there are two transmission modes between ESME and SMSC servers, namely-

Transmitter Mode
Receiver Mode

The following diagram explains the role of SMPP server during the connection establishment and release between the ESME server and SMS server

Transmission Mode:

Fig: Role of SMPP server during transmission mode(click to enlarge)

In the figure,

•Steps (1) to (4): ESME is bound with SMSC in transmitter mode, so that short messages can be sent to SMSC;

•Steps (5) to (8): ESME submits short messages to SMSC;

•Steps (9) to (10): ESME sends link detection messages to SMPP AGENT.

•Steps (11) to (14): Disconnect the link between ESME and SMSC.

Receiver Mode:

Fig: Role of SMPP server in Receiver Mode(Click to Enlarge)

In the figure:

•Steps (1) to (4): ESME is bound with SMSC in Receiver mode and is ready to receive short messages from SMSC;

•Steps (5) to (8): SMSC distributes a short message to ESME.

•Steps (9) to (12): Disconnect the link between ESME and SMSC.

The SMPP server and/or SMPP gateway is usually used in cluster mode, meaning that it has two same processor(active and standby) such that when one is down the other will be automatically turned on. Thus it has two IP address for each server processor and one floating IP for identification as single SMPP server and/or SMPP gateway. The server may run on Windows servers or linux servers. SMPP client is required on the ESME server side if there is need of SMS server. To connect to the ESME server to SMPP server the SMPP port number, username, password and SMS shortcode are required.

SMS Messages between ESME Server and SMSC Server

Posted by admin on January 6th, 2012

ESME(External Short Message Entity) is the name given to SMS Server(s) or SMS provider external to the SMS service provider network. Usually ESME server are owned by private business companies or government organizations that use SMS messaging service to provide various sms application such as Mobile Commerce(advertising), Mobile Banking by Banks, Email gateway (where email is send to sms gateway), notification applications, directory services, telemetry, vehicle tracking, cell broadcast etc. On the other hand, the SMSC server/ SMS server are usually owned by telecommunication or mobile operators (owning to the fact of SMSC cost and operation cost). Both Entities are known as SMS provider but the telecommunication company or mobile operators are usually the sms gateway provider. SMS Short Codes or just short codes are given to ESME owners by the SMSC owners for identification purpose and connection between the ESME and SMSC servers. Multiple ESME servers can be connected to SMSC via SMS gateway. SMS gateway of SMSC is also the gateway for sending international SMS. The interconnection of SMSC with MSC and HLR is shown in this SMSC post. The status of the connections between the multiple ESME servers and SMSC can be viewed at the SMSC location. The connection between the ESME servers and SMSC server is such that, ESME server is connected TCP/IP or X.25 network (internet or leased line). The TCP/IP or X.25 network is connected to the SMPP server and then SMPP server is connected to the SMSC server. This is illustrated in figure below.

Method of the ESME to access the SMSC

Fig: ESME and SMSC Communication

Interworking between the SMSC and ESMEs are categorised as:

Messages from ESMEs to the SMSC
Messages from SMSC to ESMEs

Transmission mode between ESME and SMSC

There are two transmission mode between ESMS and SMSC

Transmitter Mode
Receiver Mode

1. Transmitter Mode

In transmitter binding mode, the ESME binds with the SMSC as a transmitter. When the binding is successful, the ESME can initiate messages to the SMSC. For example, the ESME can transmit to the SMSC submit_sm, query_sm, cancel_sm, replace_sm, enquire_link and other messages.

2. Receiver Mode

In this mode, the ESME binds with the SMSC as a receiver. When the binding is successful, the ESME can receive messages initiated by the SMSC. SMSC can send a deliver_sm message to ESME.

Message Types

Fig: Messages between ESME and SMSC

Major Operation between ESME and SMSC

The major operation between ESME and SMSC are:

Bind operation
Unbind operation
Submit_SM operation
Deliver_SM operation

Bind operation is carried out to connect ESME server and SMSC server. Unbind Operation is carried out to release connection between ESEM server and SMSC server. Submit_SM and Deliver_SM are operation carried out to send and deliver short message between ESME and SMSC server. There are two types of bind operation:

Bind_Transmitter
Bind_Receiver

All these operation process is explained below with figure.

The figure below illustrates the process of bind_transmitter operation between ESME and SMSC servers.

Fig: Bind_Transmitter (Bind Process between ESME and SMSC servers)

The figure below illustrates the process of bind_receiver operation between ESME and SMSC servers.

Fig: Bind_Receiver Process between ESME and SMSC

The figure below illustrates the communication process between ESME server and SMSC server for transmitting and receiving Short Messages

Fig: Short Message transfer between ESME and SMSC

Thus mobile user sends sms to ESME and is then send to by that ESME to the SMSC server and the bill is generated by counting the number of SMS send or received. The SMS count for each ESME account is identfied by the SMS short code given at the time of interconnection of the ESME and SMSC. The amount per SMS is subject to business policy between the two SMS service provider.

Color Ring Back Tones (CRBT) System Architecture

Posted by admin on December 20th, 2011

Ring back tones or color ring back tones(crbt) is a value added service in which if the called party has crbt then the calling party will hear song when the called party number is dialed. RBT(Ring Back Tone) or CRBT(Color Ring Back Tones) are becoming increasingly popular.

The figure illustrates the RBT call flow

Fig: Ring Back Tone Call Flow

Explanation: Sub A call to sub B

1.A connect to MSC A.

2.MSC A send IAM to MSC B.

3.MSC B check information about Sub B in HLR B.

4.HLR response to MSC B that sub B is active and use CRBT Service.

5.MSC B send ACM to MSC A

6.MSC B send IAM to CRBT system

7.CRBT System check information in CRBT system and send ACM to MSC B.

8.After that, CRBT System send ANM to MSC B

9.From this time, CRBT System will play song and sub A can listen song.

10.In this time, MSC B is paging Sub B.

11.If Sub accept this call, Sub A and B will conversation, MSC B send REL to CRBT System.

12.After that, CRBT send RLC to MSC B for finish connection with CRBT System

CRBT Architecture

Fig: CRBT System Architecture

Explanation:

1.MSC send IAM to SS7/Voice-IP Interface(SII).

2.SII convert IAM to base in IP and send to data process system (DPS).

3.This DPS will sent request check information of Subs in database.

4.Database will response the song of subs to DPS.

5.DPS will send to SII the song of subs.

6.SII will load song from files server and play song to calling subs.

7.When MSC send REL to SII, SII will clear channel.

Mobile Network Parameters and Number Planning and Coding Plan

Posted by admin on December 20th, 2011

This article explains the mobile network number system, its planning and coding

1. Network Parameters

1.1 Mobile Subscriber ISDN Number (MSISDN)

An MSISDN is the number that a calling dials to call a user in a digital PLMN cellular mobile communications network. The number format is as follows:

CC + NDC + SN

CC: country code, for example, 86 for China.

NDC: Mobile service access number, for example, 130 ~ 139 for China

SN: Comprise of HLR identification number(H0H1H2H3) and subscriber number in each HLR(ABCD).

1.2 International Mobile Subscriber Identity (IMSI)

The IMSI is the unique number used to identify a mobile subscriber in the digital PLMN. It is comprised 15 numbers. The number format is as follows:

MCC+MNC+MSIN

MCC: Mobile Country Code

MNC: Mobile Network Code

MSIN: Mobile subscriber identification number Here, MSIN contain H1H2H3H0?and the H1H2H3H0 is the same as H0H1H2H3 in the MSISDN. The IMSI is used in all signaling of the GSM mobile communications network and stored in the HLR, VLR, and SIM card.

1.3 Mobile Station Roaming Number (MSRN)

The MSRN is a temporary number allocated by the VLR, as required by the HLR, to a mobile subscriber being called to enable rerouting by the network. Once the connection is completed, this number is freed for use by another subscriber.

In the China Mobile network, its structure is 8613900M1M2M3ABC or 861374X M1M3M3ABC.

"M1M2M3" is the number of the MSC.

1.4 Handover Number (HON)

The HON is a temporary number allocated by the target MSC/VLR to a mobile subscriber to enable routing during an inter-office handover. As a part of an MSRN, this number can be used only when a mobile subscriber performs an inter-office handover. It can be freed for use by another subscriber once the connection is completed.

1.5 Location Area Identity

The LAI is used to identify location areas. Its number structure is MCC+MNC+LAC.

Herein, the MCC and MNC are the same as the MCC and MNC of the IMSI.

LAC (Location Area Code) uniquely identifies each location area in the digital PLMN in China. It is a two-byte hexadecimal BCD code expressed as L1L2L3L4 (in the range of 0000 ~ FFFF; it can define 65,536 different location areas).

1.6 MSC/VLR Number

The MSC/VLR number is used in the No.7 signaling information, representing a number of the MSC. The structure of an MSC/VLR number in the GSM mobile communications network in China is 8613900M1M2M3. Herein, the allocation scheme for M1M2 is the same as that for H1H2.

1.7 HLR Number

The HLR number is used in the No.7 signaling information, representing a number of the HLR. The structure of the HLR number in the GSM mobile communications network in China is an MSISDN with an all-zero subscriber number.

2. Coding Plan

2.1 E.164 Coding Format

MSISDN and other numbers are coded in the E.164 format, which is CC+NDC+SN. Mobile phone numbers, MSC, HLR, and other numbers are coded in the E.164 format.

2.2 E.212 Coding Format

The IMSI is coded in the E.212 format: MCC+MNC+MSIN.

2.3 E.214 Coding Format

The E.214 coding format is comprised of the CC and NDC in the E.164 coding format and the MSIN in the E.212 format. Its structure is as follows:

CC+NDC+MSIN

Short Message Service Center (SMSC)

Posted by admin on December 20th, 2011

Short Message Service Center (SMSC) is the central text messaging server in the telecommunication network which provides usually the functions such as Storing, transferring and resending short text messages, Monitoring junk short messages, Virtual SC functions and provides a unified access platform for various ESME. SMSC server are expensive and are usually owned by Telecommunication Operator and/or Mobile Operator. Text messaging has become very popular and this article describes SMSC server in terms of where it is located within the core telecommunication network, SMSC hardware architecture and SMSC software architecture. Mobile marketing, sending text message to staffs by companies are some of the best used example of SMS uses. Any company/organization may be given private SMS short code which they can use for their own business such as sending text message to its employees, or using it for color tunes(CRBT) or marketing products/services through mobile (mobile marketing). The company which want this SMS feature has to apply for short code to the Telecommunication/Mobile Operator, and after it is approved the Company is given short code. The SMS short code is used for interconnection between Telecommunication/ Mobile Operator SMSC server and the Company's server. This is explained in details below.

To understand how SMSC works, one needs to understand where it is located in PLMN. The figure below illustrates this:

Fig: Short Message Service Center (SMSC)

Where:

BSS: Base Station Sub-System

MSC: Mobile services Switching Center

VLR : Visitor Location Register

HLR : Home Location Register

OMC : Operation and Maintenance Center

SGSN: Serving GPRS Support Note

GGSN: Gateway GPRS Support Note

AUC : Authentication Centre

EIR: Equipment Identification Register

PSPDN: Public Switched Data Network

PLMN: Public Land and Mobile Network

The SM-SC (Short Message Center) exists as an independent network element in PLMN, and occupies one signaling point in the SS7 network. In PLMN, it is connected to MSC, HLR, and SGSN via the SS7 network as shown in above picture.

The functions of short message gateway are located inside the SC entity to connect PLMN via the standard MAP signaling

Architecture of single SMSC

A single SMSC usually consists of two major parts: SC and the External Short Message Entity (ESME). The former integrates both IW/GMSC and the short message service processing center with an internal interface in between. Between ESME and SC, the SMPP protocol interface is adopted. Standard SS7 links are employed for communications between the SC and the PLMN using a standard service interface in compliance with MAP protocol standards. The structure of the system is shown in the figure below:

Fig: SMSC Architecture

The SC comprises the service processing module, the Operation & Maintenance Module (OMM), the Billing Module (BM), SMPP agent module (SMEA module), junk short message monitoring module, and short message query module. Multi-level modularized design is adopted inside each of the modules. Short message entities (SMEs) are value added service platforms like the information station, manual station and automatic station.

Hardware Architecture

Fig: SMSC Hardware Architecture

The SC consists of the IW/GMSC, service processing module, OMM, BM, SMEA, junk short message monitoring module and short query module. Each module inside adopts multi-level modularized design. Various components are connected via the Fast Ethernet (FE) and communicate through TCP/IP. Dual networks are used to ensure the reliability of connections.

The functional structure of these modules is described briefly as follows:

1. IW/GMSC module

Comprised of one or multiple modules to process the SS7 signaling, it is the interface between the SC and such functional entities as HLR/AUC, MSC/VLR and SGSN. The hardware is based on the ZXJ10 switching platform and the number of modules can be configured flexibly according to practical requirements.

2. Service processing module

The service processing module is comprised of one or multiple service processing sub-modules in the mode of multi-module load sharing. Each module adopts the structure of dual-system server plus disk array as well as the Cluster technology to enhance the reliability of the system.

The service processing module is the short message service processing center. It is responsible for receiving the short messages submitted by SME and MS, storing and forwarding short messages, and attempting to forward again the short messages failed in forwarding. A high-performance industrial server is used. This module exchanges information with other network functional entities through the IW/GMSC.

The service processing module consists of the service processing server and the database system.

3. Database module

To gain higher short message processing capability, the DB module can be separated from the service processing module so that an independent service DB module can be used to conduct operations such as storage and query of short messages.

4. O&M module

The operation and maintenance module consists of OMM Server, and the Agent station and the maintenance station connected to the OMM server. The Agent station and the maintenance station provide the man-machine operation platform. Operators can find out the running state of the system, detect and remove faults via the maintenance console, and manage users via the Agent. In addition, the operator can also implement remote services handling, operation and maintenance via routers.

5. SMPP Agent module

The SMPP Agent module provides the standard external SMPP protocol interface for the SC and implements the function of conversion between internal messages and standard messages. Each ESME accesses the SC just via this module.

6. Charging module

The billing module is responsible for generating short message charging bills. For facilitating the charging settlement by operators, the SMSC system will generate three kinds of bills, that is, MO, MT and ACK bills.

The BM adopts Cluster technology and shared disk array mode, is connected to the SC via DDN/X.25 network, and complies with FTP/FTAM protocol.

7. Junk SM monitoring module

The junk SM monitoring module is designed in client/server structure to separate its monitoring and management functions. The server monitors and collects the suspected short messages, while the client provides the function for the system administrator to query, analyze and handle the suspected short messages and suspected subscribers, thus implementing the centralized monitoring of multiple SCs.

The rack-mounted universal server is used as server of the junk SM monitoring module, which consists of the analysis agent module and the management server module.

8. SM query module

The SM query module is designed in a client/server structure. The server receives the SMSC-originated short messages and sets up index information for them. Also, as the module to process query requests from the client, the server searches the short message index database for short message flags of calling and called subscribers and further for the detailed information of short messages.

The rack-mounted universal server and disk array equipment are used for the server of the SM query module.

Software Architecture of SMSC

Fig: SMSC Software Architecture

Functions of these modules are described as follows:

1. Operation support module

The operation support module, located in the real time operating system, provides the development platform and the unified operation interface for the upper layer service so that the upper layer need not care about the specific structure of the lower layer hardware platform and the operating system.

2. SS7 module

For receiving and transmitting SS7 signaling, the SS7 module (that is, the IW/GMSC part) exchanges information with the service processing module, supports OMM, and provides the SMSC system with the signaling transfer function.

3. SMPP access module

The SMPP Agent module is responsible for the communication between the SC and ESMEs, converts SMPP standard messages into internal messages and vice versa, provides open interfaces for ESMEs to access the SC system, and provides TCP/IP based and X.25 based access modes.

4. Database module

The database module in the IW/GMSC is for loading and accessing the system configuration information in the SMSC system.

The database module in the service processing module stores basic subscriber information, subscriber service information, short message information and SC configuration information in the system, providing the data management function and the loading of various configuration information.

The SMSC system adopts the memory database technology that greatly reduces the times of operating the physical database and immensely improves the processing capability of the system.

5. Service processing module

The service processing module is the core component of the whole SMSC system. It is for MAP access processing, SMPP access processing, and short message service processing.

MAP access is used to exchange signaling between the SC and the GSM network, providing a short message receiving and transmitting channel for MSs.

SMPP access is used to connect ESMEs and SC, providing manual and auto stations with a channel for receiving and transmitting short messages.

Short message service processing refers to such functions as receiving, storing, forwarding short messages and repeated attempts to forward short messages.

6. O&M module

The SMSC system provides such operation and maintenance functions as subscriber data management, short message data management, system configuration, system monitoring, authority management, fault management, diagnosis test, subscriber equipment tracing, signaling tracing, security management, file management, clock management, service observation, version management, operation log and performance statistics. It also provides an interface with the Operation and Maintenance Center (OMC) for the whole GSM network system.

7. Junk SM monitoring module

To prevent some mobile subscribers from sending illegal advertising short messages and spreading retroactive information via the short message service system, the junk SM monitoring module monitors the frequency and keywords of mobile short messages. It provides the function of adding the suspected subscribers in the blacklist, so that they are restricted from sending short messages.

8. SM query module

As a complement to the short message probe module, the SM query module provides new functions such as querying and deleting short messages according to calling subscribers and called subscribers, based on the original function of querying the destination subscriber information.

Mobile Base Station Transceiver(BTS) Configuration

Posted by admin on December 17th, 2011

Introduction

•BTS configuration is determined by the traffic volume and the traffic distribution.

•BTS configuration is associated with the number of the TRXs and the antenna system.

•BTS can be omni directional

•BTS can be sectored.

•Number of TRXs can vary from site to site and that number determines the BTS configuration of that site.

2. BTS Cell Configuration:

BTS supports the following cell configurations

- Omni cell

- One sector cell

- Two sectors cell

- Three sectors cell

•BTS configuration is presented as S1/1/1 where S means sector

•Above configuration shows that the BTS is sectored.

•It has 3 sectors and each sector has 1 TRX.

•S2/3/2 means BTS has 3 sectors.

•First sector has 2 TRXs, second sector has 3 TRXs and third sector has 2 TRXs

•BTS configuration can be S2 where the BTS is sectored with only one sector having only two TRXs.

•BTS configuration can be S3/3 where the BTS has two sectors with each sectors of 3 TRXs.

•Omnidirectinal BTS is presented as O2 where the BTS has only 2 TRX.

•Similarly O4 means the BTS is omnidirectional with 4 TRXs.

•O1 means omnidirectional BTS with only one TRX.

•Supports the omni directional and directional coverage

•Combination of two cabinets to form one group

• Combination of three cabinets to form a group.

One single cabinet supports upto 12 TRXs in the full configuration

•Use as few as possible cabinets for cell configurations

•All TRXs of a cell are configured in the same cabinet

•TRXs are configured in the basic cabinet in preference and the number of TRXs in the basic cabinet is not less than that in any extension cabinet

3. Configuration Principle:

•In full configuration, the BTS configuration will be O36 or S12/12/12.

•The Transmit power will be 40W or 80W.

•For 40W the maximum configuration is S12/12/12 or O36

•But for 80W BTS, additional modules called power amplifier (PA) are required so the capacity of the BTS decreases and BTS maximum configuration will be S6/6/6 or O18.

BTS Hardware Configuration

Fig: BTS hardware configuration

Interface of BTS with BSC(Base Station controller) and MS(Mobile Station)

Fig: Interface of BTS with BSC and MS

Modules of a BTS

The main modules of a BTS are as follows:

CMM:Controller & Maintenance Module
TRM:Transceiver Module
AEM:Antenna Equipment Module
FCM:Fan Control Module
PDM:Power Distribute Module

TRM (Transceiver Module)

It has 3 parts:

TPU:Transceiver Process Unit
RCU:Radio Carrier Unit
PAU:Power Amplifier Unit

AEM (Antenna Equipment Module)

Its components are:

CDU/DCDU/ECDU:Combiner Distribution Unit
CEU:Combiner Extension Unit

CMM module funtions are:

•BS interface functions

•Providing various clocks needed by BS

•Operation & maintenance function of BTS

•Equipment alarm collection

• Active/standby hot backup

TRM Module

Fig: Transceiver Module of a BTS

AEM Module

Fig: Antenna Equipment Module (AEM)

CDU(Combiner Distribution Unit)

Fig: Combiner Distribution Unit

How might a quantum computer work?

Posted by admin on December 8th, 2011

A computer, whether classical or quantum mechanical, is a physical system, and computing is achieved through physical processes. The fundamental difference between a classical and a quantum computer is that the former, as a classical system, obeys the laws of classical physics, whereas the latter makes extensive use of quantum laws. Quite generally, computation is a physical evolution process: the system starts from a certain initial state and ends up in a final state that represents the result of the computation. In the case of quantum computers, the evolution is known to be a unitary transformation. Hence, to make a computation on a quantum computer means to realize a specific unitary transformation. This is certainly no trivial task. Fortunately, we can benefit from the fact that any unitary transformation can be built up from rotations that bring single qubits into superposition states , and elementary unitary transformations, so-called quantum gates (the analogues of gates in classical computers) that act on two qubits. Hence a quantum algorithm is specified by a sequence of rotations and gates, and the experimentalist’s task is to realize this sequence of operations.
Among the quantum gates the so-called controlled-NOT gate (or C-NOT gate)
is of special importance, since it was shown that any unitary transformation can be decomposed into rotations on a single qubit and controlled-NOT gates acting on two qubits, a control and a target qubit. A controlled-NOT gate has the following properties:

it leaves the target qubit t unchanged, when the control qubit c is
set to 0

|0>c |0>t --> |0>c |0>t , |0>c |1>t --> |0>c |1>t ,

and it causes a flip of the target qubit, when the control qubit is set to 1

|1>c |0>t --> |1>c |1>t , |1>c |1>t --> |1>c |0>t

To realize a controlled-NOT gate, one needs a physical mechanism that couples any target qubit to any control qubit. Cirac and Zoller (1995) found a suitable mechanism to be given by Coulomb repulsion, in their proposal of a quantum computer that is made up of cold ions stored in a linear Paul trap. This concept proved to be attractive for experimentalists. In fact, many of the techniques for preparing and manipulating quantum states of trapped ions have already been developed in the field of precision spectroscopy, and it has been shown that entanglement between two trapped ions was produced and quantum teleportation was realized in a three-ion system. Hence the trapped ion scheme is indeed prospective. So, to get a realistic idea of how a quantum computer might work, as a physical system, we can have a closer look at the Cirac–Zoller proposal. Dealing with ions, the two states of a qubit, |0> and |1>, are realized by two long lived energy levels.Working with alkaline earth ions, one may choose the state |0> as a sub-level of the S12 ground state, and the state |1> as a sub-level of the excited D52 state. Those two states are coupled through a quadrupole transition. So the excited state is metastable. Nevertheless, with the help of lasers optical transitions between the two states can be induced. A second important point is that by utilizing the quantum jump technique, level occupations can be reliably read out. With a properly tuned strong laser, resonance fluorescence can be excited exclusively between the ground state |0> and a suitable higher level, whereas no such possibility exists for the excited state |1>. So the occurrence of a fluorescence signal indicates that the qubit is in the state |0>, whereas the absence of such a signal tells us that the state |1> is occupied. In fact, this is the kind of measurement that enables one to read out the result of a computation.

CRBT configuration files

Posted by admin on November 29th, 2011

The CRBT system is connected to the IN (Intelligent Network). There are two main configuration files for CRBT system. One is the PPS and the other is HLR information files. Whenever a new number range is defined for user purpose in the market. It is first defined in HLR and IN. After that, if CRBT service is to be provided for that number range then it also needs to be specified in the CRBT configuration files(IMP files). Therefore the prefix of that number is added in the PPS file and HLR file.

Allocation of Entropies for Tri-Partite System

Posted by admin on November 16th, 2011

Allocation of Entropy for Tri-Partite System composed of quantum states with the following density matrices:

Qa = $\begin{pmatrix} 3/4� & 0 \\ 0� & 1/4 \end{pmatrix}$ , Qb = $\begin{pmatrix} 9/10� & 0 \\ 0� & 1/10 \end{pmatrix}$ and Qc = $\begin{pmatrix} 1/2� & 1/4 \\ 1/4� & 1/2 \end{pmatrix}$

forms a convex cone. The composite system ingredients were varied to obtain set of entropic values. For example, system A is in 10%, system B is in 40% and system C is in 50% of the mixture. The calculated values of entropies were plotted in Matlab and plotted in 3D to obtain 3D pictorial view of the allocation of entropies. This is shown below:

Another view:

Fig: Allocation of Entropy for Tripartite System

Another View:

Allocation of Entropies for Tri-Partite System as Convex Cone

Allocation of Entropy for Bipartite Quantum System

Posted by admin on November 16th, 2011

The allocation of Entropy of a Bipartite system has been proved to form a Convex cone. This can be found in the IEEE paper authored by Nicholas Pippenger. Here I am taking two bipartite system as:

1. Mixture of |0> and |1>

2. Mixture of |0> and |+>

In each case of the bipartite system case, the percentage of the two states are varied and entropy calculated. The entropies were then plotted in Matlab to obtain the following 3D view of the allocation of Entropy.

fig: Allocation of Entropy for Bipartite Quantum Systems

fig: allocation of Entropies of a two Bipartite System, the blue color plot is for the |0> and |+> mixed system, the green color plot is for |0> and |1> mixed system(click on the picture to enlarge)

The following plot is for the |0> and |+> mixed bipartite system:

fig: Allocation of Entropy for |0> and |+> bipartite system in 3D

Another view:

In this figure, the red part at the top is the area of maximum entropy for the bipartite system, while the blue at the bottom represents the minimum entropy of the composite system. Any two points inside the area satisfies the convex function criteria as well as the convex cone criteria. Hence the allocation of entropy is a Convex Cone.

Fig: 3D graph of allocation of Entropy for Bipartite System

Short Message Service Center (SMSC)

Mobile Base Station Transceiver(BTS) Configuration

Allocation of Entropies for Tri-Partite System

Allocation of Entropy for Bipartite Quantum System

Microwave Radio Installation and Commissioning

SMSC SMPP Server

SMS Messages between ESME Server and SMSC Server

Color Ring Back Tones (CRBT) System Architecture

Mobile Network Parameters and Number Planning and Coding Plan

1. Network Parameters

1.1 Mobile Subscriber ISDN Number (MSISDN)

1.2 International Mobile Subscriber Identity (IMSI)

1.3 Mobile Station Roaming Number (MSRN)

1.4 Handover Number (HON)

1.5 Location Area Identity

1.6 MSC/VLR Number

1.7 HLR Number

2. Coding Plan

2.1 E.164 Coding Format

2.2 E.212 Coding Format

2.3 E.214 Coding Format

Short Message Service Center (SMSC)

Mobile Base Station Transceiver(BTS) Configuration

How might a quantum computer work?

CRBT configuration files

Allocation of Entropies for Tri-Partite System

Allocation of Entropy for Bipartite Quantum System

Recent Posts

Meta

Reports

Telecommunication Network Information Useful Links

Archives