Skip to main content

Mobile telephony explained



With the invention and expansion of mobile telephony, mobile devices such as smartphones and tablets offer more than just making calls, it has become quite usual to surf the internet, make video calls and download photos, music and videos and so much more. People want to use their devices anywhere and everywhere. From the user with the simplest ‘mulika mwizi’ to the one with the most sophisticated of gadgets, a voice call; the mustard seed of cellular services can be made. To many the transmission path of mobile communications appears as a rather simple radio signal transmission from one mobile equipment to another. In reality however, speech and data will pass through a number of intermediate stations before reaching the called party.
The transmission path of mobile communications spans the distance from the mobile phone to the base station of the radio cell in which the caller is located. From there, the information must be transmitted, at times over great distances, to the radio cell in which the called party is located. This is done by the use of mobile switching centres (MSCs).
The mobile phone base station receives the radio signal of a mobile phone – and the information to be transmitted – with its receiving antenna. It relays this signal, via a traditional cable connection or a microwave link, to the MSC. The MSC routes calls and handles the entire connection, including ringing through to the end connection, carrying out services such as call forwarding, call waiting or conference calls. Additionally, it registers the billing data. It (the MSC) will either hand the call over to the traditional fixed network or to another MSC that will transmit the call to the base station closest to the called party. It is from here that it can reach the mobile phone.
The transmission of data between the base stations and the MSCs uses either cable connections or microwave links. Microwave links will send and receive signals on frequencies in the GigaHertz range via circular parabolic antennas. Signals are sent in the microwave range between 2 GHz and 60 GHz. Microwave links always require a direct line-of-sight(LOS) connection and will not transmit in case of an obstacle such as a skyscraper or a  hill. It is the reason as to why they are often installed on rooftops together with transceiver stations. The microwave radio relays receive and amplify the microwave signals and retransmit them to the next relay. Maximum distances here depend on the frequency. The higher the frequency, the less the distance of transmission covered.
The transmission path of the information changes depending on the location of the caller and the called party. Whenever a subscriber moves from one radio cell to another during a call, the system will automatically switch over (handover) to the adjacent radio cell and terminate the connection to the old cell without the mobile phone user noticing anything. The transmission quality is the deciding factor in the decision whether the handover will occur or not. If changing the radio cell will improve the transmission quality, a handover to the next cell will take place.



Comments

Popular posts from this blog

OBIEE 11g Error "Selected item is not of valid selection type" In Agent When Select Dashboard Page For Content

OBIEE 11g Error"Selected item is not of valid selection type" This error applies to OBIEE - version 11.1.1.7.0 and later . When you try to choose a dashboard page for delivery content in an agent, it constantly fails with the error message " Selected item is not of valid selection type ”.  Solution: This error may happen, when there is an added extra space after the end of the name of the dashboard page. For example, instead of "PAGE", it is "PAGE   "  It may happen with a space at the beginning of the name also. Removal of the extra space by renaming the dashboard page will correct the error.

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server This guide explains how to set your own predefined JVM memory arguments for the JDeveloper WebLogic container at startup for the integrated WebLogic server.   This will help avoid java.lang.OutOfMemoryError s experienced on heavy java processes and also improve on the integrated JDeveloper WebLogic server’s performance overall. Steps Locate the file: setDomainEnv.cmd which should be at: [JDeveloper Working Directory]\jdeveloper\system.xxx.xx.xx\DefaultDomain\bin                                 i.             Note: [JDeveloper Working Directory] will be "C:\Documents and Settings\<username>\Application...

Oracle BI Scheduler Error: [nqSError:76015]

Oracle BI Scheduler Error: [nqSError:76015]. The active Oracle BI Scheduler instance in the cluster could not be determined This solution applies to Oracle Business Intelligence Server Enterprise Edition - Version 11.1.1.7 and later The above error appears when a user is unable to save and edit an iBOT/Agent job This is because the data source details are incorrect and not matching with the data connection from tnsnames.ora file To resolve the error, 1.        Log in to Enterprise Manager 2.        Navigate to coreapplication 3.        Open the Deployment tab and navigate to scheduler 4.        Lock and Edit configuration 5.        Copy connection details from tnsnames.ora file NB Don’t include the TNS alias, only copy the connection string after the equal (=) sign. Spaces are OK: For example: (DESCRIPTION=(ADDRES...