<?xml version="1.0" encoding="UTF-8"?>

<!--

Free Telco Dictionary

Copyright © 2013 František Kučera (frantovo.cz)

Permission is granted to copy, distribute and/or modify this document

under the terms of the GNU Free Documentation License, Version 1.3

or any later version published by the Free Software Foundation;

with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.

A copy of the license is included in the section entitled "GNU

Free Documentation License".

You should have received a copy of the GNU Free Documentation License

along with this program.  If not, see <http://www.gnu.org/licenses/>.

-->

<dictionary xmlns="https://telco.frantovo.cz/xmlns/dictionary">

	<tags>

		<tag id="acision" name="Acision" description="comes from Acision or is specific for this company"/>

		<tag id="ericsson" name="Ericsson" description="comes from Ericsson or is specific for this company"/>

		<tag id="nsn" name="Nokia Siemens Networks" description="comes from Nokia Siemens Networks or is specific for this company"/>

		<tag id="charging" name="Charging" description="charging, billing"/>

		<tag id="messaging" name="Messaging" description="sending messages, receiving messages (SMS, MMS etc.)"/>

		<tag id="computer" name="Computer" description="general IS/ICT term"/>

		<tag id="general" name="General" description="general term"/>

		<tag id="finance" name="Finance" description="financial term"/>

		<tag id="java" name="Java" description="Java and other JVM languages"/>

		<tag id="xml" name="XML" description="eXtensible Markup Language"/>

		<tag id="security" name="Security" description="security and cryptography"/>

		<tag id="protocol" name="Protocol" description="communication protocol"/>

	</tags>

	<concept>

		<term abbreviation="MVNO" completeForm="mobile virtual network operator" language="en"/>

		<term abbreviation="MOLO" completeForm="mobile other licensed operator" language="en"/><!-- in the United Kingdom -->

		<explanation language="en"><text>a provider which does not have own wireless network infrastructure; but does marketing and sets the prices for subscribers</text></explanation>

	</concept>

	<concept>

		<term abbreviation="MVNE" completeForm="mobile virtual network enabler" language="en"/>

		<explanation language="en"><text>a company that provides technical services to MVNO thus MVNO can focus on marketing, pricing, brand and customer care</text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="hot billing" language="en"/>

		<term abbreviation="" completeForm="late billing" language="en"/>

		<term abbreviation="" completeForm="latebiller" language="en"/>

		<explanation language="en">

			<text>

				a technique used in charging;

				for pre-paid subscribers the standard way to charge services is online

				– subscriber's balance is checked in the billing system and if sufficient, the service (e.g. sending a SMS) is provided, otherwise the service is denied;

				if the billing system is not currently available (so we can't say if the subscriber's balance is high enough), we can provide the service anyway and try to charge it later;

				this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.)

				and can be done at the billing gateway or directly at system like SMSC

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="SMS" completeForm="short message service" language="en"/>

		<explanation language="en">

			<text>

				a service or particular short text message sent from or to a mobile phone;

				length of the content in one message is 140 bytes (octets), the number of characters depends on encoding, if 7-bit one is used, it is well known 160 characters;

				the number „160“ is iconic for SMS

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="octet" language="en"/>

		<term abbreviation="" completeForm="byte" language="en"/>

		<explanation language="en">

			<text>

				a unit of digital information;

				byte (almost always) consists of 8 bits, which means 256 possible values (2^8);

				octet is a synonym for 8-bit byte which accents that we really mean the 8-bit byte (and not e.g. the 7-bit one)

			</text>

		</explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="octet string" language="en"/>

		<term abbreviation="" completeForm="OctetString" language="en"/>

		<explanation language="en">

			<text>

				a basic data type in ASN.1, LDAP and other protocols;

				just a byte array – an ordered sequence of zero or more octets;

				can contain human readable text (in any character encoding) or any binary data;

				the most generic data type

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="MMS" completeForm="multimedia messaging service" language="en"/>

		<explanation language="en">

			<text>

				a service or particular multimedia message sent from or to a mobile phone;

				in contrast to SMS, supports not only text but also pictures, videos, sounds…

				thus subscriber can take a photo by his mobile phone and easily send it to a friend;

				other use case is AOMT messaging e.g. news with pictures or some premium content;

				MMS requires special infrastructure including MMSC deployed by the operator

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="DMS" completeForm="donors message service" language="en"/>

		<term abbreviation="DMS" completeForm="dárcovská SMS" language="cs"/>

		<explanation language="en">

			<text>

				specific kind of MOAT short message which is used to donate money to charity or some organization;

				the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="EMS" completeForm="enhanced messaging service" language="en"/>

		<explanation language="en">

			<text>

				an application-level extension to SMS;

				adds some new features like formatted text, pictures or sounds

				but works with existing networks (unlike MMS which requires new infrastructure)

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="SMIL" completeForm="synchronized multimedia integration language" language="en"/>

		<explanation language="en">

			<text>

				a markup language for describing multimedia presentations;

				describes timing, layout, animations etc.

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>xml</tag>

	</concept>

	<concept>

		<term abbreviation="SVG" completeForm="scalable vector graphics" language="en"/>

		<explanation language="en"><text>an XML-based file format for vector graphics</text></explanation>

		<tag>computer</tag>

		<tag>xml</tag>

	</concept>

	<concept>

		<term abbreviation="IM" completeForm="instant messaging" language="en"/>

		<term abbreviation="OTT" completeForm="over the top" language="en"/>

		<explanation language="en">

			<text>

				a kind of electronic communication between two persons or a group chat;

				compared to e-mail, IM messages are short (few words, sentence) and the other side is expected (depending on his/her online status) to read and respond it immediately;

				compared to SMS, IM messages are cheap – typically free of charge;

				important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.;

				IM is rooted in the computer world but nowadays it is often used also on mobile phones as an alternative to (expensive) SMS – in such case it is called OTT and requires mobile Internet connectivity;

				IM messages are usually transferred over an TCP/IP protocol – good example is Jabber/XMPP which is free and open protocol for IM and presence based on XML

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="IMS" completeForm="IP Multimedia Subsystem" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="RCS" completeForm="Rich Communication Suite" language="en"/>

		<term abbreviation="RCSE" completeForm="" language="en"/>

		<term abbreviation="RCSx" completeForm="" language="en"/>

		<term abbreviation="" completeForm="Joyn" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="XMPP" completeForm="extensible messaging and presence protocol" language="en"/>

		<term abbreviation="" completeForm="jabber" language="en"/><!-- original name -->

		<explanation language="en">

			<text>

				a communication protocol for messaging based on XML;

				used for transferring

					IM messages,

					presence information (statuses like: online, busy, away etc.),

					contact list (called roster here) management,

					singaling of VoIP and video, file transfers etc.;

				can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction)

				or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide)

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>xml</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="roster" language="en"/>

		<explanation language="en"><text>a contact list; term used by Jabber/XMPP</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="IMAP4" completeForm="Internet message access protocol version 4" language="en"/>

		<term abbreviation="IMAP" completeForm="Internet message access protocol" language="en"/>

		<explanation language="en">

			<text>

				a text-based client-server protocol for accessing e-mail mailbox;

				supports

					multiple hierarchical folders (inbox, sent, drafts… or user defined),

					marging messages with tags/flags,

					notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages),

					full-text search and other features;

				messages usually stays at server storage after reading which allows using multiple client programs/devices;

				is more complex than POP3 protocol;

				uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS)

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="POP3" completeForm="post office protocol version 3" language="en"/>

		<term abbreviation="POP" completeForm="post office protocol" language="en"/>

		<explanation language="en">

			<text>

				a text-based client-server protocol for accessing e-mail mailbox;

				messages are usually deleted from server after reading and are stored only on the client side;

				nowadays the more advanced IMAP4 protocol is often used instead of POP3;

				uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS)

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="SMTP" completeForm="simple mail transfer protocol" language="en"/>

		<term abbreviation="ESMTP" completeForm="Extended SMTP" language="en"/>

		<explanation language="en">

			<text>

				a text-based client-server protocol for sending e-mail messages

				uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409);

				is defined in RFC 5321

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="LMTP" completeForm="local mail transfer protocol" language="en"/>

		<explanation language="en">

			<text>

				a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue);

				uses TCP/IP but must not use port 25 (SMTP);

				is defined in RFC 2033

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="MUA" completeForm="mail user agent" language="en"/>

		<explanation language="en">

			<text>

				an e-mail client – a software used for managing user's e-mail;

				because the MUA (like most client software) runs only when user needs it,

					the messages from the Internet are received by a remote MTA over the SMTP protocol,

					then delivered using an MDA into user's remote mailbox,

					from which they are obtained by the MUA using POP3 or IMAP4 protocols;

				when sending an e-mail, the MUA composes the message in RFC 5322 format and then submits it using the SMTP protocol to a MTA or MSA server;

				examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MTA" completeForm="message transfer agent" language="en"/>

		<term abbreviation="MTA" completeForm="mail transfer agent" language="en"/>

		<term abbreviation="MX" completeForm=" mail exchanger" language="en"/>

		<explanation language="en">

			<text>

				a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving);

				messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP);

				examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MSA" completeForm="message submission agent" language="en"/>

		<explanation language="en">

			<text>

				a software component dedicated to receive e-mails from MUA;

				cooperates with MTA or is often integrated in MTA as one of its features;

				uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25)

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MDA" completeForm="message delivery agent" language="en"/>

		<term abbreviation="LDA" completeForm="local delivery agent" language="en"/>

		<explanation language="en">

			<text>

				a software component that receives e-mail from the MTA and stores them in the recipient's mailbox;

				the MDA can also apply Sieve filters on processed messages;

				examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MRA" completeForm="message retrieval agent" language="en"/>

		<explanation language="en">

			<text>

				a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol)

				and then passes them to the MDA for local storage, or over SMTP to an MTA, or directly delivers it to the mailbox, or prints to standard output etc.;

				implements pull (not push) approach: fetches messages periodically (or on user's demand)

				instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does);

				examples of MRA: fetchmail, getmail

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="sieve" language="en"/>

		<explanation language="en">

			<text>

				a standardized language for describing e-mail filters;

				the MDA can apply system-wide or user-defined filters on incoming messages;

				a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“

				and actions that will be done with the message like „file into folder X“ or „add flag/label X“ or „redirect message to some.address@example.com“ or „discard message“;

				filters are executed on the server where MDA resides,

				so they are independent of the MUA currently used by the user

				and works even if the user is offline (useful for OOTO messages when the user is on vacation)

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="OOTO" completeForm="out of the office" language="en"/>

		<explanation language="en">

			<text>

				an automatic response on a message (e-mail, SMS etc.) which is sent when the recipient is for example on vacation and can't respond immediately;

				in case of e-mail it can be easily configured as a Sieve filter

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MIME" completeForm="multipurpose Internet mail extensions" language="en"/>

		<explanation language="en">

			<text>

				an Internet standard for extended e-mail format which supports

					international character sets for body parts,

					international characters in message headers,

					attachements of various types,

					multipart messages;

				MIME message itself is a human-readable text starting with header section and having one or more body parts;

				binary or non-ASCII values are encoded in several ways described by the MIME's RFCs;

				the content types defined by MIME is used also outside of e-mail – for indicating format of the content in HTTP, databases or operating systems

			</text>

		</explanation>

		<tag>computer</tag>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="SAP" completeForm="sms application protocol" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="SPID" completeForm="service provider ID" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="UTF-8" completeForm="unicode transformation format 8-bit" language="en"/>

		<explanation language="en">

			<text>

				an character encoding that can represent every character in the Unicode character set;

				is multibyte and variable-width encoding which means that one character can be represented by one or more bytes

				(i.e. character length of the text does not have to be equal to byte lenght of the data),

				in case of UTF-8 it is from 1 byte up to 6 bytes per character;

				is backward compatible with ASCII – one-byte characters in UTF-8 are encoded in same way as in ACSII;

				nowadays is widely used: on web, in e-mail, in operating systems (file names), in XML files etc.

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="UCS-2" completeForm="universal character set 2-byte" language="en"/>

		<explanation language="en">

			<text>

				an multibyte but fixed-length (2 byte) character encoding;

				sometimes is used for SMS when international characters are needed – such single message has only 70 characters instead of 160 (7-bit encoding);

				for general use it was superseded by UTF-16 (in Unicode 2.0 in 1996)

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="UTF-16" completeForm="unicode transformation format 16-bit" language="en"/>

		<explanation language="en">

			<text>

				an multibyte and variable-width encoding for Unicode codepoints from 0 to 0x10FFFF;

				successor of UCS-2 encoding (for range 0-0xFFFF they have same values)

			</text>

		</explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="SMPP" completeForm="short message peer-to-peer" language="en"/>

		<explanation language="en">

			<text>

				open and industry standard protocol for transferring SMS messages among service centers (SC), applications (ESME) and routing entities (RE);

				was designed by the Aldiscon company (later Logica CMG and later Acision);

				binary PDUs are transported over TCP/IP or X.25 connection

			</text>

		</explanation>

		<tag>messaging</tag>

		<tag>protocol</tag>

		<tag>acision</tag>

	</concept>

	<concept>

		<term abbreviation="NMS" completeForm="network management system" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="SNMP" completeForm="simple network management protocol" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="MIB" completeForm="management information base" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="OID" completeForm="object identifier" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="SPBP" completeForm="SMS prepaid billing protocol" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

		<tag>acision</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="RTPP" completeForm="Real Time Payment Protocol" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="BIP" completeForm="billing interface protocol" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="LTE" completeForm="Long Term Evolution" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="VoLTE" completeForm="Voice over LTE" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="FTTH" completeForm=" fiber to the home" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="CIC" completeForm="Carrier Identification Code" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="E.164" language="en"/>

		<explanation language="en">

			<text>

				an ITU-T recommendation;

				full title: The international public telecommunication numbering plan;

				defines the numbering plan of the PSTN and general format of international phone numbers

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="MSISDN" completeForm="mobile subscriber integrated services digital network number" language="en"/>

		<term abbreviation="MSISDN" completeForm="mobile subscriber ISDN number" language="en"/>

		<term abbreviation="MSISDN" completeForm="mobile station international ISDN number" language="en"/>

		<explanation language="en">

			<text>

				a globally unique indentifier of a subscription in a GSM or a UMTS network;

				follows numbering plan defined by E.164 – international phone number

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="IMEI" completeForm="international mobile station equipment identity" language="en"/>

		<explanation language="en">

			<text>

				a number used to identify GSM, UMTS, LTE, iDEN or satelite mobile phones;

				it identifies the device not the subscribtion (like IMSI or MSISDN);

				on most phones can be displayed by typing *#06#

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="IMSI" completeForm="international mobile subscriber identity" language="en"/>

		<explanation language="en">

			<text>

				a globally unique identifier stored on the SIM card used in GSM, UMTS and LTE networks;

				a 64 bit value usually presented as 15 digit number;

				consists of MCC (country code), MNC (network code) and MSIN (subscription ID)

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="MCC" completeForm="mobile country code" language="en"/>

		<explanation language="en">

			<text>

				a unique numeric identifier of a country;

				a part of IMSI;

				often used in tuple with MNC;

			</text>

		</explanation>

	</concept>

	<!--

		Lists of MCC/MNC:

		https://en.wikipedia.org/wiki/Mobile_country_code

		http://wammu.eu/tools/countries/

		http://wammu.eu/tools/networks/

	-->

	<concept>

		<term abbreviation="MNC" completeForm="mobile network code" language="en"/>

		<explanation language="en">

			<text>

				a unique numeric identifier of a mobile network (carrier);

				a part of IMSI;

				often used in tuple with MCC

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="MSIN" completeForm="mobile subscription identification number" language="en"/>

		<term abbreviation="MIN" completeForm="mobile identification number" language="en"/>

		<explanation language="en">

			<text>

				a part of IMSI

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="Ki" completeForm="" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="SIM" completeForm="subscriber identification module" language="en"/>

		<term abbreviation="SIM" completeForm="subscriber identity module" language="en"/>

		<explanation language="en">

			<text>

				a smartcard which contains IMSI, ke and cryptographic functions;

				is used to identify and authenticate subscribers in mobile phone networks

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="ICCID" completeForm="integrated circuit card identifier" language="en"/>

		<!-- https://en.wikipedia.org/wiki/Subscriber_identity_module#ICCID -->

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="GT" completeForm="global title" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="SCCP" completeForm="signalling connection control part" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="MWC" completeForm="Mobile World Congress" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="ITU" completeForm="International Telecommunication Union" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="3GPP" completeForm="3rd Generation Partnership Project" language="en"/>

		<term abbreviation="TGPP" completeForm="Third Generation Partnership Project" language="en"/><!-- used as an identifier if can not start with number -->

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="ASN.1" completeForm="abstract syntax notation one" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="X.400" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="X.500" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="X.509" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

		<tag>security</tag>

	</concept>

	<concept>

		<term abbreviation="BER" completeForm="basic encoding rules" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="DER" completeForm="distinguished encoding rules" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="CER" completeForm="canonical encoding rules" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="PER" completeForm="packed encoding rules" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="XER" completeForm="XML Encoding Rules" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

		<tag>xml</tag>

	</concept>

	<concept>

		<term abbreviation="EMV" completeForm="Europay, MasterCard and Visa" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>finance</tag>

	</concept>

	<concept>

		<term abbreviation="AVP" completeForm="attribute-value pair" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="TLV" completeForm="type-length-value" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="PDU" completeForm="protocol data unit" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

	</concept>

	<concept>

		<term abbreviation="MM1" completeForm="" language="en"/>

		<explanation language="en">

			<text>

				an MMS protocol used between a Mobile Station and an MMSC;

				is based on WAP and SMS

			</text>

		</explanation>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="MM7" completeForm="" language="en"/>

		<explanation language="en">

			<text>

				an MMS protocol used between an MMSC and VASP;

				is based on SOAP, HTTP and MIME

			</text>

		</explanation>

		<tag>messaging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="AAA" completeForm="authentication, authorization and accounting" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>computer</tag>

		<tag>security</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="Diameter" language="en"/>

		<explanation language="en">

			<text>

				an AAA protocol and a successor of the RADIUS protocol;

				consists of the base protocol and many „Diameter Applications“ (protocols based on Diameter)

				e.g.

					Diameter Credit-Control Application,

					Diameter Session Initiation Protocol Application or

					Diameter Extensible Authentication Protocol Application

			</text>

		</explanation>

		<tag>security</tag>

		<tag>charging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="RADIUS" completeForm="remote access dial in user service" language="en"/>

		<explanation language="en">

			<text>

				an AAA protocol and the predecessor of the Diameter protocol;

			</text>

		</explanation>

		<tag>security</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="SCAP" completeForm="service charging application protocol" language="en"/>

		<term abbreviation="SCAPv2" completeForm="service charging application protocol version 2" language="en"/>

		<term abbreviation="" completeForm="Draft 8" language="en"/>

		<term abbreviation="" completeForm="Draft-8" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>ericsson</tag>

		<tag>charging</tag>

		<tag>protocol</tag>

	</concept>

	<concept>

		<term abbreviation="DCC" completeForm="Diameter credit control" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="DAAC" completeForm="Diameter accounting and authorization control" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="SPI" completeForm="service parameter info" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="result code" language="en"/>

		<explanation language="en">

			<text>

				a number which represents the result of an operation in the Diameter protocol;

				codes are divided into several groups:

					1xxx – Informational,

					2xxx – Success,

					3xxx – Protocol errors,

					4xxx – Transient failures,

					5xxx – Permanent failure;

				for example 2001 means success, 2002 limited success, 3001 unsupported command or 5001 unsupported AVP

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="CCR" completeForm="Credit-Control-Request" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="CCA" completeForm="Credit-Control-Answer" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="CCN" completeForm="Charging Control Node" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="IN" completeForm="Intelligent Network" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>nsn</tag>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="BS" completeForm="billing system" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="CTF" completeForm="Charging Trigger Function" language="en"/>

		<explanation language="en">

			<text>

				one of two peers involved in charging process;

				CTF decides how to charge particular subscriber for specific service;

				issues requests to the OCF

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="OCF" completeForm="Online Charging Function" language="en"/>

		<explanation language="en">

			<text>

				one of two peers involved in charging process;

				accepts requests from CTF and performs actual charging

				based on the message type, service logic, user's profile or other circumstances

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="charged party" language="en"/>

		<!-- A, B, AB, - RTPP/MMSC -->

		<explanation language="en">

			<text>

				the party (sender or recipient) who is charged for the service (e.g. SMS);

				MOMT messages (or other traffic) are typically charged to the sender (A);

				AOMT messages (like weather forecast or news) are typically charged to the recipient (B);

				some messages can be free of charge and some can be charged to both party (AB)

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="subscriber" language="en"/>

		<explanation language="en">

			<text>

				a subscriber of a mobile network, a customer of a telco operator

				(but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator)

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="SMS gateway" language="en"/>

		<term abbreviation="RE" completeForm="routing entity" language="en"/>

		<explanation language="en">

			<text>

				a software component located between the SMSC (or other service centre) and ESME (applications);

				passes messages in both directions,

				uses SMPP and other messaging protocols,

				does routing of messages, their transformations, conversions or other operations

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="pre-paid" language="en"/>

		<explanation language="en">

			<text>

				a kind of subscription where the subscriber pays in advance

				and his services are charged (usually immediately, online) from his pre-paid balance

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="post-paid" language="en"/>

		<explanation language="en">

			<text>

				a kind of subscription where the subscriber pays later than he uses the services (usually monthly);

				compared to pre-paid, batch processing of CDR files and offline processing is common here

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="CDR" completeForm="call detail record" language="en"/>

		<term abbreviation="SDR" completeForm="service detail record" language="en"/>

		<explanation language="en">

			<text>

				kind of log file in machine-readable format (ASN.1, XML, CSV etc.)

				which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection;

				CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage;

				they must be handled carefully because they contain private information (who calls or texts who);

				always respect subscriber's privacy!

			</text>

		</explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="SDR" completeForm="software-defined radio" language="en"/>

		<explanation language="en">

			<text>

				a radio communication system that has important parts (filters, modulators, demodulators…) implemented as computer software instead of hardware components;

				examples: Universal Software Radio Peripheral (USRP), GNU Radio (software)

			</text>

		</explanation>

	</concept>

	<concept>

		<term abbreviation="MO" completeForm="mobile originated" language="en"/>

		<explanation language="en">

			<text>

				traffic which comes from a cell phone resp. mobile network,

				e.g. an SMS sent from your Handy

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MT" completeForm="mobile terminated" language="en"/>

		<explanation language="en">

			<text>

				traffic which comes to a cell phone resp. mobile network,

				e.g. a received SMS

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="AO" completeForm="application originated" language="en"/>

		<explanation language="en">

			<text>

				traffic which comes from an application i.e. not from the mobile network/phone,

				e.g. some weather forecast messages generated by an SPA

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="AT" completeForm="application terminated" language="en"/>

		<explanation language="en">

			<text>

				traffic which comes to an application i.e. not to the mobile network/phone,

				e.g. message sent to an application in order to subscribe the service or to send your vote

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MOMT" completeForm="mobile originated → mobile terminated" language="en"/>

		<explanation language="en"><text>e.g. when Bob texts Alice from his phone to her phone</text></explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="MOAT" completeForm="mobile originated → application terminated" language="en"/>

		<explanation language="en"><text>e.g. if Bob subscribes a weather forecast service by sending a message from his phone</text></explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="AOMT" completeForm="application originated → mobile terminated" language="en"/>

		<explanation language="en"><text>e.g. if Alice receives to her phone a news message which she has previously subscribed</text></explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="AOAT" completeForm="application originated → application terminated" language="en"/>

		<explanation language="en">

			<text>

				if two applications communicates over an SMS gateway and there are no cell phones involved;

				this is pretty rare, but somewhere you can meet such configuration

			</text>

		</explanation>

		<tag>messaging</tag>

	</concept>

	<concept>

		<term abbreviation="" completeForm="Handy" language="de"/>

		<explanation language="en"><text>a cell phone</text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="billing" language="en"/>

		<term abbreviation="" completeForm="charging" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="IEC" completeForm="immediate event charging" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="ECUR" completeForm="event charging with unit reservation" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="SCUR" completeForm="session charging with unit reservation" language="en"/>

		<explanation language="en"><text></text></explanation>

		<tag>charging</tag>

	</concept>

	<concept>

		<term abbreviation="COI" completeForm="community of interest" language="en"/>

		<explanation language="en"><text></text></explanation>

	</concept>

	<concept>

		<term abbreviation="" completeForm="aliasing" language="en"/>

		<term abbreviation="" completeForm="de-aliasing" language="en"/>

		<term abbreviation="" completeForm="dealiasing" language="en"/>

		<term abbreviation="" completeForm="hashing" language="en"/>

		<explanation language="en">

			<text>