1 <?xml version="1.0" encoding="UTF-8"?>
4 Copyright © 2013 František Kučera (frantovo.cz)
6 Permission is granted to copy, distribute and/or modify this document
7 under the terms of the GNU Free Documentation License, Version 1.3
8 published by the Free Software Foundation;
9 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
10 A copy of the license is included in the section entitled "GNU
11 Free Documentation License".
13 You should have received a copy of the GNU Free Documentation License
14 along with this program. If not, see <http://www.gnu.org/licenses/>.
16 <dictionary xmlns="https://telco.frantovo.cz/xmlns/dictionary">
18 <id>fca6b6ec-34dd-4cb2-83a3-d1b8ceccb296</id>
21 <tag id="acision" name="Acision" description="comes from Acision or is specific for this company"/>
22 <tag id="ericsson" name="Ericsson" description="comes from Ericsson or is specific for this company"/>
23 <tag id="nsn" name="Nokia Siemens Networks" description="comes from Nokia Siemens Networks or is specific for this company"/>
25 <tag id="charging" name="Charging" description="charging, billing"/>
26 <tag id="messaging" name="Messaging" description="sending messages, receiving messages (SMS, MMS etc.)"/>
28 <tag id="computer" name="Computer" description="general IS/ICT term"/>
29 <tag id="general" name="General" description="general term"/>
30 <tag id="finance" name="Finance" description="financial term"/>
32 <tag id="java" name="Java" description="Java and other JVM languages"/>
33 <tag id="xml" name="XML" description="eXtensible Markup Language"/>
34 <tag id="database" name="Database" description="SQL/Relational and other DBMS"/>
35 <tag id="security" name="Security" description="security and cryptography"/>
36 <tag id="protocol" name="Protocol" description="communication protocol"/>
40 <term abbreviation="MVNO" completeForm="mobile virtual network operator" language="en"/>
41 <term abbreviation="MOLO" completeForm="mobile other licensed operator" language="en"/><!-- in the United Kingdom -->
42 <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>
45 <term abbreviation="MVNE" completeForm="mobile virtual network enabler" language="en"/>
46 <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>
49 <term abbreviation="" completeForm="hot billing" language="en"/>
50 <term abbreviation="" completeForm="late billing" language="en"/>
51 <term abbreviation="" completeForm="latebiller" language="en"/>
52 <explanation language="en">
54 a technique used in charging;
55 for pre-paid subscribers the standard way to charge services is online
56 – 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;
57 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;
58 this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.)
59 and can be done at the billing gateway or directly at system like SMSC
65 <term abbreviation="SMS" completeForm="short message service" language="en"/>
66 <explanation language="en">
68 a service or particular short text message sent from or to a mobile phone;
69 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;
70 the number „160“ is iconic for SMS
76 <term abbreviation="" completeForm="octet" language="en"/>
77 <term abbreviation="" completeForm="byte" language="en"/>
78 <explanation language="en">
80 a unit of digital information;
81 byte (almost always) consists of 8 bits, which means 256 possible values (2^8);
82 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)
88 <term abbreviation="" completeForm="octet string" language="en"/>
89 <term abbreviation="" completeForm="OctetString" language="en"/>
90 <explanation language="en">
92 a basic data type in ASN.1, LDAP and other protocols;
93 just a byte array – an ordered sequence of zero or more octets;
94 can contain human readable text (in any character encoding) or any binary data;
95 the most generic data type
100 <term abbreviation="MMS" completeForm="multimedia messaging service" language="en"/>
101 <explanation language="en">
103 a service or particular multimedia message sent from or to a mobile phone;
104 in contrast to SMS, supports not only text but also pictures, videos, sounds…
105 thus subscriber can take a photo by his mobile phone and easily send it to a friend;
106 other use case is AOMT messaging e.g. news with pictures or some premium content;
107 MMS requires special infrastructure including MMSC deployed by the operator
113 <term abbreviation="DMS" completeForm="donors message service" language="en"/>
114 <term abbreviation="DMS" completeForm="dárcovská SMS" language="cs"/>
115 <explanation language="en">
117 specific kind of MOAT short message which is used to donate money to charity or some organization;
118 the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS
124 <term abbreviation="EMS" completeForm="enhanced messaging service" language="en"/>
125 <explanation language="en">
127 an application-level extension to SMS;
128 adds some new features like formatted text, pictures or sounds
129 but works with existing networks (unlike MMS which requires new infrastructure)
135 <term abbreviation="SMIL" completeForm="synchronized multimedia integration language" language="en"/>
136 <explanation language="en">
138 a markup language for describing multimedia presentations;
139 describes timing, layout, animations etc.
146 <term abbreviation="SVG" completeForm="scalable vector graphics" language="en"/>
147 <explanation language="en"><text>an XML-based file format for vector graphics</text></explanation>
152 <term abbreviation="IM" completeForm="instant messaging" language="en"/>
153 <term abbreviation="OTT" completeForm="over the top" language="en"/>
154 <explanation language="en">
156 a kind of electronic communication between two persons or a group chat;
157 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;
158 compared to SMS, IM messages are cheap – typically free of charge;
159 important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.;
160 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;
161 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
168 <term abbreviation="IMS" completeForm="IP Multimedia Subsystem" language="en"/>
169 <explanation language="en"><text></text></explanation>
173 <term abbreviation="RCS" completeForm="Rich Communication Suite" language="en"/>
174 <term abbreviation="RCSE" completeForm="" language="en"/>
175 <term abbreviation="RCSx" completeForm="" language="en"/>
176 <term abbreviation="" completeForm="Joyn" language="en"/>
177 <explanation language="en"><text></text></explanation>
181 <term abbreviation="XMPP" completeForm="extensible messaging and presence protocol" language="en"/>
182 <term abbreviation="" completeForm="jabber" language="en"/><!-- original name -->
183 <explanation language="en">
185 a communication protocol for messaging based on XML;
186 used for transferring
188 presence information (statuses like: online, busy, away etc.),
189 contact list (called roster here) management,
190 signaling of VoIP and video, file transfers etc.;
191 can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction)
192 or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide)
201 <term abbreviation="" completeForm="roster" language="en"/>
202 <explanation language="en"><text>a contact list; term used by Jabber/XMPP</text>
208 <term abbreviation="IMAP4" completeForm="Internet message access protocol version 4" language="en"/>
209 <term abbreviation="IMAP" completeForm="Internet message access protocol" language="en"/>
210 <explanation language="en">
212 a text-based client-server protocol for accessing e-mail mailbox;
214 multiple hierarchical folders (inbox, sent, drafts… or user defined),
215 marging messages with tags/flags,
216 notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages),
217 full-text search and other features;
218 messages usually stays at server storage after reading which allows using multiple client programs/devices;
219 is more complex than POP3 protocol;
220 uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS)
228 <term abbreviation="POP3" completeForm="post office protocol version 3" language="en"/>
229 <term abbreviation="POP" completeForm="post office protocol" language="en"/>
230 <explanation language="en">
232 a text-based client-server protocol for accessing e-mail mailbox;
233 messages are usually deleted from server after reading and are stored only on the client side;
234 nowadays the more advanced IMAP4 protocol is often used instead of POP3;
235 uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS)
243 <term abbreviation="SMTP" completeForm="simple mail transfer protocol" language="en"/>
244 <term abbreviation="ESMTP" completeForm="Extended SMTP" language="en"/>
245 <explanation language="en">
247 a text-based client-server protocol for sending e-mail messages
248 uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409);
249 is defined in RFC 5321
257 <term abbreviation="LMTP" completeForm="local mail transfer protocol" language="en"/>
258 <explanation language="en">
260 a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue);
261 uses TCP/IP but must not use port 25 (SMTP);
262 is defined in RFC 2033
270 <term abbreviation="MUA" completeForm="mail user agent" language="en"/>
271 <explanation language="en">
273 an e-mail client – a software used for managing user's e-mail;
274 because the MUA (like most client software) runs only when user needs it,
275 the messages from the Internet are received by a remote MTA over the SMTP protocol,
276 then delivered using an MDA into user's remote mailbox,
277 from which they are obtained by the MUA using POP3 or IMAP4 protocols;
278 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;
279 examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes
286 <term abbreviation="MTA" completeForm="message transfer agent" language="en"/>
287 <term abbreviation="MTA" completeForm="mail transfer agent" language="en"/>
288 <term abbreviation="MX" completeForm=" mail exchanger" language="en"/>
289 <explanation language="en">
291 a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving);
292 messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP);
293 examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James
300 <term abbreviation="MSA" completeForm="message submission agent" language="en"/>
301 <explanation language="en">
303 a software component dedicated to receive e-mails from MUA;
304 cooperates with MTA or is often integrated in MTA as one of its features;
305 uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25)
312 <term abbreviation="MDA" completeForm="message delivery agent" language="en"/>
313 <term abbreviation="LDA" completeForm="local delivery agent" language="en"/>
314 <explanation language="en">
316 a software component that receives e-mail from the MTA and stores them in the recipient's mailbox;
317 the MDA can also apply Sieve filters on processed messages;
318 examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop
325 <term abbreviation="MRA" completeForm="message retrieval agent" language="en"/>
326 <explanation language="en">
328 a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol)
329 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.;
330 implements pull (not push) approach: fetches messages periodically (or on user's demand)
331 instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does);
332 examples of MRA: fetchmail, getmail
339 <term abbreviation="" completeForm="sieve" language="en"/>
340 <explanation language="en">
342 a standardized language for describing e-mail filters;
343 the MDA can apply system-wide or user-defined filters on incoming messages;
344 a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“
345 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“;
346 filters are executed on the server where MDA resides,
347 so they are independent of the MUA currently used by the user
348 and works even if the user is offline (useful for OOTO messages when the user is on vacation)
355 <term abbreviation="OOTO" completeForm="out of the office" language="en"/>
356 <explanation language="en">
358 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;
359 in case of e-mail it can be easily configured as a Sieve filter
366 <term abbreviation="MIME" completeForm="multipurpose Internet mail extensions" language="en"/>
367 <explanation language="en">
369 an Internet standard for extended e-mail format which supports
370 international character sets for body parts,
371 international characters in message headers,
372 attachements of various types,
374 MIME message itself is a human-readable text starting with header section and having one or more body parts;
375 binary or non-ASCII values are encoded in several ways described by the MIME's RFCs;
376 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
383 <term abbreviation="SAP" completeForm="sms application protocol" language="en"/>
384 <explanation language="en"><text></text></explanation>
389 <term abbreviation="SPID" completeForm="service provider ID" language="en"/>
390 <explanation language="en"><text></text></explanation>
393 <term abbreviation="UTF-8" completeForm="unicode transformation format 8-bit" language="en"/>
394 <explanation language="en">
396 an character encoding that can represent every character in the Unicode character set;
397 is multibyte and variable-width encoding which means that one character can be represented by one or more bytes
398 (i.e. character length of the text does not have to be equal to byte lenght of the data),
399 in case of UTF-8 it is from 1 byte up to 6 bytes per character;
400 is backward compatible with ASCII – one-byte characters in UTF-8 are encoded in same way as in ACSII;
401 nowadays is widely used: on web, in e-mail, in operating systems (file names), in XML files etc.
406 <term abbreviation="UCS-2" completeForm="universal character set 2-byte" language="en"/>
407 <explanation language="en">
409 an multibyte but fixed-length (2 byte) character encoding;
410 sometimes is used for SMS when international characters are needed – such single message has only 70 characters instead of 160 (7-bit encoding);
411 for general use it was superseded by UTF-16 (in Unicode 2.0 in 1996)
417 <term abbreviation="UTF-16" completeForm="unicode transformation format 16-bit" language="en"/>
418 <explanation language="en">
420 an multibyte and variable-width encoding for Unicode codepoints from 0 to 0x10FFFF;
421 successor of UCS-2 encoding (for range 0-0xFFFF they have same values)
427 <term abbreviation="SMPP" completeForm="short message peer-to-peer" language="en"/>
428 <explanation language="en">
430 open and industry standard protocol for transferring SMS messages among service centers (SC), applications (ESME) and routing entities (RE);
431 was designed by the Aldiscon company (later Logica CMG and later Acision);
432 binary PDUs are transported over TCP/IP or X.25 connection
440 <term abbreviation="NMS" completeForm="network management system" language="en"/>
441 <explanation language="en"><text></text></explanation>
445 <term abbreviation="SNMP" completeForm="simple network management protocol" language="en"/>
446 <explanation language="en"><text></text></explanation>
450 <term abbreviation="MIB" completeForm="management information base" language="en"/>
451 <explanation language="en"><text></text></explanation>
455 <term abbreviation="OID" completeForm="object identifier" language="en"/>
456 <explanation language="en"><text></text></explanation>
460 <term abbreviation="SPBP" completeForm="SMS prepaid billing protocol" language="en"/>
461 <explanation language="en"><text></text></explanation>
468 <term abbreviation="RTPP" completeForm="Real Time Payment Protocol" language="en"/>
469 <explanation language="en"><text></text></explanation>
475 <term abbreviation="BIP" completeForm="billing interface protocol" language="en"/>
476 <explanation language="en"><text></text></explanation>
481 <term abbreviation="LTE" completeForm="Long Term Evolution" language="en"/>
482 <explanation language="en"><text></text></explanation>
485 <term abbreviation="VoLTE" completeForm="Voice over LTE" language="en"/>
486 <explanation language="en"><text></text></explanation>
489 <term abbreviation="FTTH" completeForm=" fiber to the home" language="en"/>
490 <explanation language="en"><text></text></explanation>
493 <term abbreviation="CIC" completeForm="Carrier Identification Code" language="en"/>
494 <explanation language="en"><text></text></explanation>
497 <term abbreviation="" completeForm="E.164" language="en"/>
498 <explanation language="en">
500 an ITU-T recommendation;
501 full title: The international public telecommunication numbering plan;
502 defines the numbering plan of the PSTN and general format of international phone numbers
507 <term abbreviation="MSISDN" completeForm="mobile subscriber integrated services digital network number" language="en"/>
508 <term abbreviation="MSISDN" completeForm="mobile subscriber ISDN number" language="en"/>
509 <term abbreviation="MSISDN" completeForm="mobile station international ISDN number" language="en"/>
510 <explanation language="en">
512 a globally unique indentifier of a subscription in a GSM or a UMTS network;
513 follows numbering plan defined by E.164 – international phone number
518 <term abbreviation="IMEI" completeForm="international mobile station equipment identity" language="en"/>
519 <explanation language="en">
521 a number used to identify GSM, UMTS, LTE, iDEN or satelite mobile phones;
522 it identifies the device not the subscribtion (like IMSI or MSISDN);
523 on most phones can be displayed by typing *#06#
528 <term abbreviation="IMSI" completeForm="international mobile subscriber identity" language="en"/>
529 <explanation language="en">
531 a globally unique identifier stored on the SIM card used in GSM, UMTS and LTE networks;
532 a 64 bit value usually presented as 15 digit number;
533 consists of MCC (country code), MNC (network code) and MSIN (subscription ID)
538 <term abbreviation="MCC" completeForm="mobile country code" language="en"/>
539 <explanation language="en">
541 a unique numeric identifier of a country;
543 often used in tuple with MNC;
549 https://en.wikipedia.org/wiki/Mobile_country_code
550 http://wammu.eu/tools/countries/
551 http://wammu.eu/tools/networks/
554 <term abbreviation="MNC" completeForm="mobile network code" language="en"/>
555 <explanation language="en">
557 a unique numeric identifier of a mobile network (carrier);
559 often used in tuple with MCC
564 <term abbreviation="MSIN" completeForm="mobile subscription identification number" language="en"/>
565 <term abbreviation="MIN" completeForm="mobile identification number" language="en"/>
566 <explanation language="en">
573 <term abbreviation="Ki" completeForm="" language="en"/>
574 <explanation language="en"><text></text></explanation>
577 <term abbreviation="SIM" completeForm="subscriber identification module" language="en"/>
578 <term abbreviation="SIM" completeForm="subscriber identity module" language="en"/>
579 <explanation language="en">
581 a smartcard which contains IMSI, ke and cryptographic functions;
582 is used to identify and authenticate subscribers in mobile phone networks
587 <term abbreviation="ICCID" completeForm="integrated circuit card identifier" language="en"/>
588 <!-- https://en.wikipedia.org/wiki/Subscriber_identity_module#ICCID -->
589 <explanation language="en"><text></text></explanation>
592 <term abbreviation="GT" completeForm="global title" language="en"/>
593 <explanation language="en"><text></text></explanation>
596 <term abbreviation="SCCP" completeForm="signalling connection control part" language="en"/>
597 <explanation language="en"><text></text></explanation>
600 <term abbreviation="MWC" completeForm="Mobile World Congress" language="en"/>
601 <explanation language="en"><text></text></explanation>
604 <term abbreviation="ITU" completeForm="International Telecommunication Union" language="en"/>
605 <explanation language="en"><text></text></explanation>
608 <term abbreviation="3GPP" completeForm="3rd Generation Partnership Project" language="en"/>
609 <term abbreviation="TGPP" completeForm="Third Generation Partnership Project" language="en"/><!-- used as an identifier if can not start with number -->
610 <explanation language="en"><text></text></explanation>
613 <term abbreviation="ASN.1" completeForm="abstract syntax notation one" language="en"/>
614 <explanation language="en"><text></text></explanation>
617 <term abbreviation="" completeForm="X.400" language="en"/>
618 <explanation language="en"><text></text></explanation>
621 <term abbreviation="" completeForm="X.500" language="en"/>
622 <explanation language="en"><text></text></explanation>
625 <term abbreviation="" completeForm="X.509" language="en"/>
626 <explanation language="en"><text></text></explanation>
631 <term abbreviation="BER" completeForm="basic encoding rules" language="en"/>
632 <explanation language="en"><text></text></explanation>
636 <term abbreviation="DER" completeForm="distinguished encoding rules" language="en"/>
637 <explanation language="en"><text></text></explanation>
641 <term abbreviation="CER" completeForm="canonical encoding rules" language="en"/>
642 <explanation language="en"><text></text></explanation>
646 <term abbreviation="PER" completeForm="packed encoding rules" language="en"/>
647 <explanation language="en"><text></text></explanation>
651 <term abbreviation="XER" completeForm="XML Encoding Rules" language="en"/>
652 <explanation language="en"><text></text></explanation>
657 <term abbreviation="EMV" completeForm="Europay, MasterCard and Visa" language="en"/>
658 <explanation language="en"><text></text></explanation>
663 <term abbreviation="AVP" completeForm="attribute-value pair" language="en"/>
664 <explanation language="en"><text></text></explanation>
668 <term abbreviation="TLV" completeForm="type-length-value" language="en"/>
669 <explanation language="en"><text></text></explanation>
673 <term abbreviation="PDU" completeForm="protocol data unit" language="en"/>
674 <explanation language="en"><text></text></explanation>
678 <term abbreviation="MM1" completeForm="" language="en"/>
679 <explanation language="en">
681 an MMS protocol used between a Mobile Station and an MMSC;
682 is based on WAP and SMS
689 <term abbreviation="MM7" completeForm="" language="en"/>
690 <explanation language="en">
692 an MMS protocol used between an MMSC and VASP;
693 is based on SOAP, HTTP and MIME
700 <term abbreviation="AAA" completeForm="authentication, authorization and accounting" language="en"/>
701 <explanation language="en"><text></text></explanation>
706 <term abbreviation="" completeForm="Diameter" language="en"/>
707 <explanation language="en">
709 an AAA protocol and a successor of the RADIUS protocol;
710 consists of the base protocol and many „Diameter Applications“ (protocols based on Diameter)
712 Diameter Credit-Control Application,
713 Diameter Session Initiation Protocol Application or
714 Diameter Extensible Authentication Protocol Application
722 <term abbreviation="RADIUS" completeForm="remote access dial in user service" language="en"/>
723 <explanation language="en">
725 an AAA protocol and the predecessor of the Diameter protocol;
732 <term abbreviation="SCAP" completeForm="service charging application protocol" language="en"/>
733 <term abbreviation="SCAPv2" completeForm="service charging application protocol version 2" language="en"/>
734 <term abbreviation="" completeForm="Draft 8" language="en"/>
735 <term abbreviation="" completeForm="Draft-8" language="en"/>
736 <explanation language="en"><text></text></explanation>
742 <term abbreviation="DCC" completeForm="Diameter credit control" language="en"/>
743 <explanation language="en"><text></text></explanation>
747 <term abbreviation="DAAC" completeForm="Diameter accounting and authorization control" language="en"/>
748 <explanation language="en"><text></text></explanation>
752 <term abbreviation="SPI" completeForm="service parameter info" language="en"/>
753 <explanation language="en"><text></text></explanation>
757 <term abbreviation="" completeForm="result code" language="en"/>
758 <explanation language="en">
760 a number which represents the result of an operation in the Diameter protocol;
761 codes are divided into several groups:
762 1xxx – Informational,
764 3xxx – Protocol errors,
765 4xxx – Transient failures,
766 5xxx – Permanent failure;
767 for example 2001 means success, 2002 limited success, 3001 unsupported command or 5001 unsupported AVP
772 <term abbreviation="CCR" completeForm="Credit-Control-Request" language="en"/>
773 <explanation language="en"><text></text></explanation>
777 <term abbreviation="CCA" completeForm="Credit-Control-Answer" language="en"/>
778 <explanation language="en"><text></text></explanation>
782 <term abbreviation="CCN" completeForm="Charging Control Node" language="en"/>
783 <explanation language="en"><text></text></explanation>
787 <term abbreviation="IN" completeForm="Intelligent Network" language="en"/>
788 <explanation language="en"><text></text></explanation>
793 <term abbreviation="BS" completeForm="billing system" language="en"/>
794 <explanation language="en"><text></text></explanation>
798 <term abbreviation="CTF" completeForm="Charging Trigger Function" language="en"/>
799 <explanation language="en">
801 one of two peers involved in charging process;
802 CTF decides how to charge particular subscriber for specific service;
803 issues requests to the OCF
809 <term abbreviation="OCF" completeForm="Online Charging Function" language="en"/>
810 <explanation language="en">
812 one of two peers involved in charging process;
813 accepts requests from CTF and performs actual charging
814 based on the message type, service logic, user's profile or other circumstances
820 <term abbreviation="" completeForm="charged party" language="en"/>
821 <!-- A, B, AB, - RTPP/MMSC -->
822 <explanation language="en">
824 the party (sender or recipient) who is charged for the service (e.g. SMS);
825 MOMT messages (or other traffic) are typically charged to the sender (A);
826 AOMT messages (like weather forecast or news) are typically charged to the recipient (B);
827 some messages can be free of charge and some can be charged to both party (AB)
833 <term abbreviation="" completeForm="subscriber" language="en"/>
834 <explanation language="en">
836 a subscriber of a mobile network, a customer of a telco operator
837 (but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator)
842 <term abbreviation="" completeForm="SMS gateway" language="en"/>
843 <term abbreviation="RE" completeForm="routing entity" language="en"/>
844 <explanation language="en">
846 a software component located between the SMSC (or other service centre) and ESME (applications);
847 passes messages in both directions,
848 uses SMPP and other messaging protocols,
849 does routing of messages, their transformations, conversions or other operations
854 <term abbreviation="" completeForm="pre-paid" language="en"/>
855 <explanation language="en">
857 a kind of subscription where the subscriber pays in advance
858 and his services are charged (usually immediately, online) from his pre-paid balance
864 <term abbreviation="" completeForm="post-paid" language="en"/>
865 <explanation language="en">
867 a kind of subscription where the subscriber pays later than he uses the services (usually monthly);
868 compared to pre-paid, batch processing of CDR files and offline processing is common here
874 <term abbreviation="CDR" completeForm="call detail record" language="en"/>
875 <term abbreviation="SDR" completeForm="service detail record" language="en"/>
876 <explanation language="en">
878 kind of log file in machine-readable format (ASN.1, XML, CSV etc.)
879 which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection;
880 CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage;
881 they must be handled carefully because they contain private information (who calls or texts who);
882 always respect subscriber's privacy!
888 <term abbreviation="SDR" completeForm="software-defined radio" language="en"/>
889 <explanation language="en">
891 a radio communication system that has important parts (filters, modulators, demodulators…) implemented as computer software instead of hardware components;
892 examples: Universal Software Radio Peripheral (USRP), GNU Radio (software)
897 <term abbreviation="MO" completeForm="mobile originated" language="en"/>
898 <explanation language="en">
900 traffic which comes from a cell phone resp. mobile network,
901 e.g. an SMS sent from your Handy
907 <term abbreviation="MT" completeForm="mobile terminated" language="en"/>
908 <explanation language="en">
910 traffic which comes to a cell phone resp. mobile network,
917 <term abbreviation="AO" completeForm="application originated" language="en"/>
918 <explanation language="en">
920 traffic which comes from an application i.e. not from the mobile network/phone,
921 e.g. some weather forecast messages generated by an SPA
927 <term abbreviation="AT" completeForm="application terminated" language="en"/>
928 <explanation language="en">
930 traffic which comes to an application i.e. not to the mobile network/phone,
931 e.g. message sent to an application in order to subscribe the service or to send your vote
937 <term abbreviation="MOMT" completeForm="mobile originated → mobile terminated" language="en"/>
938 <explanation language="en"><text>e.g. when Bob texts Alice from his phone to her phone</text></explanation>
942 <term abbreviation="MOAT" completeForm="mobile originated → application terminated" language="en"/>
943 <explanation language="en"><text>e.g. if Bob subscribes a weather forecast service by sending a message from his phone</text></explanation>
947 <term abbreviation="AOMT" completeForm="application originated → mobile terminated" language="en"/>
948 <explanation language="en"><text>e.g. if Alice receives to her phone a news message which she has previously subscribed</text></explanation>
952 <term abbreviation="AOAT" completeForm="application originated → application terminated" language="en"/>
953 <explanation language="en">
955 if two applications communicates over an SMS gateway and there are no cell phones involved;
956 this is pretty rare, but somewhere you can meet such configuration
962 <term abbreviation="" completeForm="Handy" language="de"/>
963 <explanation language="en"><text>a cell phone</text></explanation>
966 <term abbreviation="" completeForm="billing" language="en"/>
967 <term abbreviation="" completeForm="charging" language="en"/>
968 <explanation language="en"><text></text></explanation>
972 <term abbreviation="IEC" completeForm="immediate event charging" language="en"/>
973 <explanation language="en"><text></text></explanation>
977 <term abbreviation="ECUR" completeForm="event charging with unit reservation" language="en"/>
978 <explanation language="en"><text></text></explanation>
982 <term abbreviation="SCUR" completeForm="session charging with unit reservation" language="en"/>
983 <explanation language="en"><text></text></explanation>
987 <term abbreviation="COI" completeForm="community of interest" language="en"/>
988 <explanation language="en"><text></text></explanation>
991 <term abbreviation="" completeForm="aliasing" language="en"/>
992 <term abbreviation="" completeForm="de-aliasing" language="en"/>
993 <term abbreviation="" completeForm="dealiasing" language="en"/>
994 <term abbreviation="" completeForm="hashing" language="en"/>
995 <explanation language="en">
997 when a subscriber communicates with an application (MOAT/AOMT messaging)
998 he might not want expose his identity (MSISDN or IMSI);
999 the aliasing feature (sometimes called hashing) deployed on an SMS gateway enables this communication and rewrites the subscriber's ID to some generated ID;
1000 the application can then send a response on a message without knowing subscriber's identity (on the gateway the ID is translated back to real ID – de-aliasing);
1002 subscribers can vote in some survey,
1003 everyone will have one vote,
1004 but the owner of the survey will not know the opinion of particular subscibers
1005 because of missing their real IDs
1009 <tag>messaging</tag>
1012 <term abbreviation="" completeForm="provisioning" language="en"/>
1013 <explanation language="en"><text></text></explanation>
1017 <term abbreviation="CP" completeForm="content provider" language="en"/>
1018 <explanation language="en"><text></text></explanation>
1021 <term abbreviation="" completeForm="short code" language="en"/>
1022 <term abbreviation="" completeForm="short number" language="en"/>
1023 <explanation language="en">
1025 a special kind of phone number which has few digits (e.g. four);
1026 ESME usually has assigned a short number
1027 thus subscriber can do MOAT messaging without remembering/typing long phone numbers;
1028 texting or calling to/from this numbers might be charged with an extra rate
1029 (the subscriber pays not only for the telco service but also for the VAS provided)
1032 <tag>messaging</tag>
1035 <term abbreviation="VASP" completeForm="value-added service provider" language="en"/>
1036 <explanation language="en">
1038 a provider who operates an ESME (application)
1041 <tag>messaging</tag>
1044 <term abbreviation="ESME" completeForm="external short message entity" language="en"/>
1045 <term abbreviation="" completeForm="application" language="en"/>
1046 <term abbreviation="LA" completeForm="large account" language="en"/>
1047 <term abbreviation="VAS" completeForm="value-added service" language="en"/>
1048 <term abbreviation="SPA" completeForm="service provider application" language="en"/>
1049 <term abbreviation="AIM" completeForm="application interface module" language="en"/>
1051 LA vs. AIM „Use AIM instead of LA (AIM is an MCO term, LA is a V5 term).“
1053 ESME = any application which can either
1054 recieve or send or both is an ESME (also known as VAS or SPA or LA)
1055 LA Large Account (also known as ESME or SPA or VAS)
1056 SPA Service Provider Application (also known as ESME or VAS or LA)
1057 VAS Value Added Service (also known as ESME or SPA or LA)
1059 <explanation language="en">
1061 an application a software component which sends and receives messages (SMS, MMS, e-mail…) and is connected over IP (not directly attached to mobile network) and protocol like SMPP;
1062 often is operated by different company than telco operator – a VASP;
1065 <tag>messaging</tag>
1068 <term abbreviation="NEP" completeForm="network end point" language="en"/>
1069 <explanation language="en">
1071 an end-point in RE where SC is connected
1074 <tag>messaging</tag>
1077 <term abbreviation="AEP" completeForm="application end point" language="en"/>
1078 <explanation language="en">
1080 an end-point in RE where SPA is connected
1083 <tag>messaging</tag>
1086 <term abbreviation="SPDB" completeForm="service provider database" language="en"/>
1087 <explanation language="en"><text></text></explanation>
1090 <term abbreviation="MCO" completeForm="Message Controller" language="en"/>
1091 <!-- bridge mezi TCP/IP a SS7 ? -->
1092 <explanation language="en"><text></text></explanation>
1094 <tag>messaging</tag>
1097 <term abbreviation="SME" completeForm="short message entity" language="en"/>
1098 <explanation language="en">
1100 e.g. a mobile handset
1104 <tag>messaging</tag>
1107 <term abbreviation="GSM" completeForm="Global System for Mobile communications" language="en"/>
1108 <term abbreviation="GSM" completeForm="Groupe Spécial Mobile" language="fr"/>
1109 <explanation language="en"><text></text></explanation>
1112 <term abbreviation="GSMA" completeForm="GSM Association" language="en"/>
1113 <explanation language="en"><text></text></explanation>
1116 <term abbreviation="CDMA" completeForm="code division multiple access" language="en"/>
1117 <explanation language="en"><text></text></explanation>
1120 <term abbreviation="TDMA" completeForm="time division multiple access" language="en"/>
1121 <explanation language="en"><text></text></explanation>
1124 <term abbreviation="UMTS" completeForm="universal mobile telecommunications system" language="en"/>
1125 <explanation language="en"><text></text></explanation>
1128 <term abbreviation="SS7" completeForm="signalling system no. 7" language="en"/>
1129 <explanation language="en"><text></text></explanation>
1132 <term abbreviation="SIGTRAN" completeForm="SIGnaling TRAnsport" language="en"/>
1133 <explanation language="en"><text></text></explanation>
1136 <term abbreviation="3G" completeForm="third generation" language="en"/>
1137 <explanation language="en"><text></text></explanation>
1140 <term abbreviation="4G" completeForm="fourth generation" language="en"/>
1141 <explanation language="en"><text></text></explanation>
1144 <term abbreviation="" completeForm="Baby Bell" language="en"/>
1145 <!-- https://en.wikipedia.org/wiki/Regional_Bell_Operating_Company -->
1146 <explanation language="en"><text></text></explanation>
1149 <term abbreviation="EAIF" completeForm="external application interface" language="en"/>
1150 <explanation language="en"><text>Nokia's protocol for sending and receiving MMS, is based on HTTP and transferres binary content.</text></explanation>
1152 <tag>messaging</tag>
1156 <term abbreviation="UCP" completeForm="universal computer protocol" language="en"/>
1157 <explanation language="en">
1159 an SMS messaging protocol developed by CMG (later Acision)
1160 as interface for ESME to SMSC;
1161 an extended variant of it is called EMI
1165 <tag>messaging</tag>
1169 <term abbreviation="EMI" completeForm="external machine interface" language="en"/>
1170 <explanation language="en"><text>an extension of UCP</text></explanation>
1172 <tag>messaging</tag>
1176 <term abbreviation="CIMD" completeForm="computer interface to message distribution" language="en"/>
1177 <explanation language="en">
1179 a proprietary SMS messaging protocol developed by Nokia
1180 for connecting to their SMSC
1184 <tag>messaging</tag>
1188 <term abbreviation="URLP" completeForm="URL encoded message protocol" language="en"/>
1189 <explanation language="en">
1191 a simple protocol that can be used between AAG and SPA for transmitting messages;
1192 uses HTTP GET method and encodes data in the URL or in HTTP response body
1196 <tag>messaging</tag>
1200 <term abbreviation="SMAP" completeForm="short message application protocol" language="en"/>
1201 <explanation language="en"><text></text></explanation>
1202 <tag>messaging</tag>
1207 <term abbreviation="PSA" completeForm="" language="en"/>
1208 <explanation language="en"><text></text></explanation>
1212 <term abbreviation="PAP" completeForm="push access protocol" language="en"/>
1213 <explanation language="en"><text></text></explanation>
1217 <term abbreviation="SC" completeForm="service center" language="en"/>
1218 <term abbreviation="MC" completeForm="message centre" language="en"/>
1219 <explanation language="en">
1221 a component in telecommunication network;
1222 SMSC for SMS or MMSC for MMS messages
1225 <tag>messaging</tag>
1228 <term abbreviation="SMSC" completeForm="SMS service center" language="en"/>
1229 <term abbreviation="SMS-SC" completeForm="Short Message Service - Service Centre" language="en"/>
1230 <explanation language="en">
1232 a component in telecommunication network dedicated to store, forward, convert and deliver SMS messages;
1233 is connected to the SS7 network on one side and to routing entities (RE) using SMPP on the other side;
1234 is able to process MOMT messaging and also MOAT or AOMT messaging (using RE)
1235 Example of SMSC: SMSCv5
1238 <tag>messaging</tag>
1241 <term abbreviation="SMSCv5" completeForm="SMS service center version 5" language="en"/>
1242 <term abbreviation="v5" completeForm="" language="en"/><!-- jargon -->
1243 <explanation language="en">
1245 an implementation of SMSC from Acision;
1246 runs on an OpenVMS system
1250 <tag>messaging</tag>
1253 <term abbreviation="MMSC" completeForm="Multimedia Messaging Service Centre" language="en"/>
1254 <term abbreviation="MMSC" completeForm="MMS Service Centre" language="en"/>
1255 <term abbreviation="" completeForm="MMS store and forward server" language="en"/>
1256 <explanation language="en">
1258 a kind of SC dedicated to processing multimedia messages;
1259 the messaging is more comlex process than in case of SMS:
1260 MO MMS message is received (in similar format to MIME e-mail) by the MMSC and stored,
1261 then SC determines if the recipient is capable to receive MMS,
1262 if yes, the message is put at a server with HTTP interface and the recipient gets special SMS containing the URL and downloads it over WAP,
1263 if recipient is not capable he gets plain text SMS with URL and have to use computer and www browser
1266 <tag>messaging</tag>
1269 <term abbreviation="BMSC" completeForm="Broadband Messaging Service Centre" language="en"/>
1270 <term abbreviation="" completeForm="Fusion" language="en"/>
1271 <explanation language="en">
1273 a consolidated messaging platform announced by the Acision company in 2013;
1274 integrates RSC, SMS, MMS and voice mail
1278 <tag>messaging</tag>
1281 <term abbreviation="IWG" completeForm="inter-working gateway" language="en"/>
1282 <explanation language="en"><text></text></explanation>
1283 <tag>messaging</tag>
1286 <term abbreviation="WAP" completeForm="wireless application protocol" language="en"/>
1287 <explanation language="en"><text></text></explanation>
1291 <term abbreviation="OTA" completeForm="over-the-air" language="en"/>
1292 <explanation language="en"><text></text></explanation>
1295 <term abbreviation="FOTA" completeForm="firmware over the air" language="en"/>
1296 <explanation language="en"><text></text></explanation>
1299 <term abbreviation="DRM" completeForm="digital restrictions management" language="en"/>
1300 <term abbreviation="DRM" completeForm="digital rights management" language="en"/>
1301 <explanation language="en"><text></text></explanation>
1305 <term abbreviation="SyncML" completeForm="synchronization markup language" language="en"/>
1306 <explanation language="en"><text></text></explanation>
1310 <term abbreviation="VoIP" completeForm="voice over IP" language="en"/>
1311 <explanation language="en">
1313 delivering voice communication (or other multimedia sessions like video) over the Internet Protocol (IP) instead of traditional telco networks;
1314 there are open and standard protocols for signaling: SIP and XMPP and open protocols for the payload (audio/video) like RTP;
1315 VoIP is nowadays widely used inside companies where often shares same ethernet network with computers (can be separeted by VLANs)
1316 and also in households espetially for cheap overseas calls;
1317 as VoIP phone can be used a computer with appropriate software or a cell phone or dedicated hardware phone;
1318 there are also gateways that enable connecting old analog phones to the VoIP network
1323 <term abbreviation="SIP" completeForm="session initiation protocol" language="en"/>
1324 <explanation language="en">
1326 an open signalling protocol for initiation of VoIP calls (audio, video or possibly other media sessions);
1327 has similar format of headers and request/response model as HTTP;
1328 transported over UDP or TCP (for TLS encryption) or SCTP;
1329 for the media payload is typically used RTP protocol
1335 <term abbreviation="RTP" completeForm="real-time transport protocol" language="en"/>
1336 <explanation language="en">
1338 a standardized packet format for delivering audio and video over IP;
1339 can transfer audio or video streams for telephony or television streams;
1340 is used heavily in VoIP in combination with SIP;
1341 can be secured with SRTP/ZRTP to avoid wiretrapping
1347 <term abbreviation="SRTP" completeForm="secure RTP" language="en"/>
1348 <explanation language="en"><text></text></explanation>
1353 <term abbreviation="ZRTP" completeForm="Zimmermann RTP" language="en"/>
1354 <explanation language="en"><text></text></explanation>
1359 <term abbreviation="" completeForm="throttling" language="en"/>
1360 <explanation language="en">
1362 limiting the flow rate;
1363 e.g. short messages per second
1366 <tag>messaging</tag>
1369 <term abbreviation="" completeForm="keep alive" language="en"/>
1370 <term abbreviation="" completeForm="keep-alive" language="en"/>
1371 <explanation language="en">
1373 a packet or message or command without useful content
1374 which is sent in order to avoid closing the connection (time out) and to check, it is still working;
1375 in HTTP this term means persistent connection
1381 <term abbreviation="" completeForm="inroaming" language="en"/>
1382 <explanation language="en"><text>roaming of subscribers from other operator in your network</text></explanation>
1385 <term abbreviation="" completeForm="outroaming" language="en"/>
1386 <explanation language="en"><text>roaming of your subscribers in other operator's network</text></explanation>
1389 <term abbreviation="TON" completeForm="type of number" language="en"/>
1390 <explanation language="en">
1392 (0x00) Unknown type of number;
1393 (0x01) International number;
1394 (0x02) National number;
1395 (0x03) Network specific number;
1396 (0x04) Subscriber number, dedicated access, short code;
1397 (0x05) Alphanumeric, in 7-bit GSM alphabet;
1398 (0x06) Abbreviated number
1403 <term abbreviation="NPI" completeForm="numbering plan indicator" language="en"/>
1404 <explanation language="en">
1406 a number which indicates the numbering plan of a telephone number;
1408 (0x00) Unknown numbering plan;
1409 (0x01) ISDN/telephone numbering plan – E.164/E.163;
1411 (0x03) Data numbering plan – X.121;
1412 (0x04) Telex numbering plan – F.96;
1413 (0x05) Service Centre Specific plan;
1414 (0x06) Land mobile numbering plan – E.212;
1415 (0x07) ISDN/mobile numbering plan – E.214;
1416 <!-- only 0-7 defined in the ITU standard Q.713 ? -->
1417 (0x08) National numbering plan;
1418 (0x09) Private numbering plan;
1419 (0x0A) ERMES numbering plan – ETSI DE/PS 3 01-3;
1420 (0x0D) Binary Internet addres – IP;
1421 (0x0E) Alphanumeric Internet address
1426 <term abbreviation="PID" completeForm="protocol identifier" language="en"/>
1427 <explanation language="en">
1429 one octet of information which describes the protocol resp. type of telematic device;
1430 0 means implicit (plain MOMT messages);
1431 other values are described in 3GPP TS 03.40
1436 <term abbreviation="PID" completeForm="process identifier" language="en"/>
1437 <explanation language="en">
1439 identifier of an process (running program) in an operating system;
1440 PID 1 is usually assigned to the init process (the first process which starts other ones)
1446 <term abbreviation="" completeForm="Blue box" language="en"/>
1447 <term abbreviation="" completeForm="BlueBox" language="en"/>
1448 <explanation language="en"><text></text></explanation>
1451 Orange box https://en.wikipedia.org/wiki/Orange_box
1452 Vermilion box https://en.wikipedia.org/wiki/Vermilion_box
1453 Magenta box https://en.wikipedia.org/wiki/Magenta_box
1456 <term abbreviation="" completeForm="Orange box" language="en"/>
1457 <term abbreviation="" completeForm="OrangeBox" language="en"/>
1458 <explanation language="en"><text></text></explanation>
1461 <term abbreviation="" completeForm="Vermilion box" language="en"/>
1462 <term abbreviation="" completeForm="VermilionBox" language="en"/>
1463 <explanation language="en"><text></text></explanation>
1466 <term abbreviation="" completeForm="Magenta box" language="en"/>
1467 <term abbreviation="" completeForm="MagentaBox" language="en"/>
1468 <explanation language="en"><text></text></explanation>
1471 <term abbreviation="" completeForm="hack" language="en"/>
1472 <term abbreviation="" completeForm="hacking" language="en"/>
1473 <term abbreviation="" completeForm="hacker" language="en"/>
1474 <explanation language="en">
1476 hacker is an interrogative person interested in internal principles of things;
1477 often it is a software developer or a system administrator but hacking is also possible outside the digital world;
1478 hacking is the activity of these people – usually
1479 improving a software by adding new features
1480 or discovering secrets in existing software or hardware systems
1481 or running extraordinary configurations or combinations of components;
1482 hack is the product of their work – e.g. improved computer program or piece of hardware;
1483 <!-- hack can mean also the insctructions how to do it; -->
1484 don't confuse with „cracker“
1487 RMS - https://www.gnu.org/philosophy/rms-hack.html
1488 „someone who enjoys playful cleverness, especially in programming but other media are also possible“
1490 ESR - http://www.catb.org/~esr/jargon/html/H/hacker.html
1491 [originally, someone who makes furniture with an axe]
1492 1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary. RFC1392, the Internet Users' Glossary, usefully amplifies this as: A person who delights in having an intimate understanding of the internal workings of a system, computers and computer networks in particular.
1493 2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming.
1494 3. A person capable of appreciating hack value.
1495 4. A person who is good at programming quickly.
1496 5. An expert at a particular program, or one who frequently does work using it or on it; as in ‘a Unix hacker’. (Definitions 1 through 5 are correlated, and people who fit them congregate.)
1497 6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example.
1498 7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations.
1499 8. [deprecated] A malicious meddler who tries to discover sensitive information by poking around. Hence password hacker, network hacker. The correct term for this sense is cracker.
1500 The term ‘hacker’ also tends to connote membership in the global community defined by the net (see the network. For discussion of some of the basics of this culture, see the How To Become A Hacker FAQ. It also implies that the person described is seen to subscribe to some version of the hacker ethic (see hacker ethic).
1501 It is better to be described as a hacker by others than to describe oneself that way. Hackers consider themselves something of an elite (a meritocracy based on ability), though one to which new members are gladly welcome. There is thus a certain ego satisfaction to be had in identifying yourself as a hacker (but if you claim to be one and are not, you'll quickly be labeled bogus). See also geek, wannabee.
1502 This term seems to have been first adopted as a badge in the 1960s by the hacker culture surrounding TMRC and the MIT AI Lab. We have a report that it was used in a sense close to this entry's by teenage radio hams and electronics tinkerers in the mid-1950s.
1504 RFC 1392 - https://tools.ietf.org/html/rfc1392
1505 A person who delights in having an intimate understanding of the
1506 internal workings of a system, computers and computer networks in
1507 particular. The term is often misused in a pejorative context,
1508 where "cracker" would be the correct term. See also: cracker.
1515 <term abbreviation="" completeForm="crack" language="en"/>
1516 <term abbreviation="" completeForm="cracking" language="en"/>
1517 <term abbreviation="" completeForm="cracker" language="en"/>
1518 <explanation language="en">
1520 someone who breaks the security protections in order to get unauthorized access to a computer system;
1521 they often misuse their skills to steal private data, destroy systems or steal money;
1522 don't confuse with „hacker“
1529 <term abbreviation="" completeForm="phreak" language="en"/>
1530 <term abbreviation="" completeForm="phreaking" language="en"/>
1531 <term abbreviation="" completeForm="phreaker" language="en"/>
1532 <explanation language="en">
1534 a hacker interested in phone systems or telecommunications in general;
1535 sometimes they can become cracker if they don't only experiment but misuse telephone networks excessively (fraud);
1536 the term is a portmanteau of the words „phone“ and „freak“
1542 <term abbreviation="AAGP" completeForm="Acision Application Gateway Provisioning" language="en"/>
1543 <term abbreviation="GAS" completeForm="Generic application server" language="en"/>
1544 <term abbreviation="CPS" completeForm="Central provisioning system" language="en"/>
1545 <explanation language="en">
1547 a software component developed by the Acision company;
1548 a provisioning tool for AAG and other products of this company;
1549 can be used as generic provisioning tool for any product provided that particular connector exists;
1550 has web GUI and several APIs
1554 <tag>messaging</tag>
1557 <term abbreviation="AAG" completeForm="Acision Application Gateway" language="en"/>
1558 <term abbreviation="OMG" completeForm="Open Messaging Gateway" language="en"/>
1559 <explanation language="en">
1561 a software component developed by the Acision company;
1562 typical use case is: a messaging gateway between SMSC and applications (ESME)
1566 <tag>messaging</tag>
1569 <term abbreviation="GBG" completeForm="General Billing Gateway" language="en"/>
1570 <term abbreviation="AFG" completeForm="Acision Flexible Gateway" language="en"/>
1571 <term abbreviation="TGC" completeForm="Test Gateway Component" language="en"/>
1572 <term abbreviation="UGC" completeForm="Universal Gateway Component" language="en"/>
1573 <explanation language="en">
1575 a software component developed by the Acision company;
1576 works as a messaging gateway and can interconnect systems talking many various messaging protocols;
1577 is highly configurable and can translate and transform messages in many formats;
1578 original purpose was doing a gateway for billing messages comming from e.g. SMSC to some billing system
1582 <tag>messaging</tag>
1585 <term abbreviation="UGC" completeForm="user generated content" language="en"/>
1586 <explanation language="en">
1588 content in various media formats (text, pictures, video, sound…)
1589 which is created by users (or subscribers);
1590 e.g. photos taken by mobile and sent over MMS, e-mail or web to some server which displays them to other users
1596 <term abbreviation="VCS" completeForm="version control system" language="en"/>
1597 <term abbreviation="RCS" completeForm="revision control system" language="en"/>
1598 <explanation language="en">
1600 a software tool used for management of changes in documents;
1601 often is used for managing source code and other artifacts (like documentation or analytic models) created during software development;
1602 VCS tracks versions of particular files or changesets, branches, tags (named revisions);
1603 examples of traditional centralized VCS: SCCS, RCS, CVS or SVN (quite modern but centralized);
1604 nowadays are very popular decentralized systems (DVCS)
1610 <term abbreviation="DVCS" completeForm="distributed version control system" language="en"/>
1611 <term abbreviation="DRCS" completeForm="distributed revision control system" language="en"/>
1612 <explanation language="en">
1614 kind of version control system which allows not only workflow with one central server
1615 but also decentralized workflows where changesets are pushed or pulled between particular nodes;
1616 each node has typically full repository clone with all the history (commits, branches, tags);
1617 this facilitates offline work –
1618 developer can do commits or work with branches and tags even if he is offline –
1619 and after going online,
1620 he pushed his work to other developers
1621 or to the central repository
1622 or his work is pulled by others;
1623 other advantage is easy backup – just clone the repository and then do push/pull from the working one;
1624 Examples of DVCS: Mercurial (Hg), Git, Bazaar (bzr), Monotone (mtn), Fossil, GNU arch, Darcs, DCVS or SVK
1630 <term abbreviation="SCM" completeForm="software configuration management" language="en"/>
1631 <explanation language="en"><text></text></explanation>
1635 <term abbreviation="hg" completeForm="mercurial" language="en"/>
1636 <explanation language="en"><text>a distributed version control system</text></explanation>
1640 <term abbreviation="cvs" completeForm="Concurrent Versions System" language="en"/>
1641 <explanation language="en"><text>a centralized version control system</text></explanation>
1645 <term abbreviation="svn" completeForm="Subversion" language="en"/>
1646 <explanation language="en"><text>a centralized version control system</text></explanation>
1650 <term abbreviation="bzr" completeForm="Bazaar" language="en"/>
1651 <explanation language="en"><text>a distributed version control system</text></explanation>
1655 <term abbreviation="" completeForm="git" language="en"/>
1656 <explanation language="en"><text>a distributed version control system</text></explanation>
1660 <term abbreviation="XML" completeForm="eXtensible markup language" language="en"/>
1661 <explanation language="en"><text></text></explanation>
1666 <term abbreviation="xmlns" completeForm="XML name space" language="en"/>
1667 <explanation language="en"><text></text></explanation>
1672 <term abbreviation="DTD" completeForm="document type definition" language="en"/>
1673 <explanation language="en">
1675 a schema language for XML;
1676 used to describe the format based on XML
1677 and perform validations of XML documents
1684 <term abbreviation="XSD" completeForm="XML schema definition" language="en"/>
1685 <explanation language="en">
1687 a schema language for XML;
1688 used to describe the format based on XML
1689 and perform validations of XML documents
1690 XSD itself is written in XML;
1691 is more powerful than DTD
1698 <term abbreviation="" completeForm="Schematron" language="en"/>
1699 <explanation language="en">
1701 a validation language;
1702 can describe formats based on XML like XSD or DTD does, but has entirely different approach;
1703 Schematron is rule-based – defines assertions which must be met to have valid document;
1704 this rules are transformed into XSL template which is executed during validation;
1705 Schematron can be also combined with XSD
1706 – XSD schemas (which are more declarative and more clearly represents the desired structure of the document for humans)
1707 are enriched with Schematron assertions that adds more complex rules (that cannot be easily expressed in pure XSD)
1714 <term abbreviation="XSLT" completeForm="Extensible Stylesheet Language Transformations" language="en"/>
1715 <term abbreviation="XSL" completeForm="Extensible Stylesheet Language" language="en"/>
1716 <explanation language="en">
1718 a transformation language for XML;
1719 can be used e.g. for
1720 conversion from one XML format to another one,
1721 for generating (plain) text or HTML,
1722 for user friendly visualisation of XML data (XHTML or SVG output),
1723 or for validations (raise error message on invalid input, see also Schematron);
1724 XSL templates are also written in XML
1731 <term abbreviation="" completeForm="XQuery" language="en"/>
1732 <explanation language="en">
1734 functional programming language for processing XML and other data
1741 <term abbreviation="XPath" completeForm="XML Path Language" language="en"/>
1742 <explanation language="en">
1744 a query language for selecting XML nodes;
1745 an XPath expression can also compute values and call XPath functions
1752 <term abbreviation="" completeForm="Ant" language="en"/>
1753 <explanation language="en">
1755 a tool for automating software build processes;
1756 does similar job like GNU Make, but is written in and for Java;
1757 equivalent for the Makefile is here build.xml which describes particular tasks and their dependencies;
1758 there is lot of tasks distributed with Apache Ant e.g.
1759 compilation of Java code,
1761 running XSLT transformations,
1762 packing JARs and other archives,
1763 copying and moving files
1764 or calling system commands;
1765 and user can also write own tasks in Java
1772 <term abbreviation="mvn" completeForm="Maven" language="en"/>
1773 <explanation language="en">
1775 a tool for automating software build processes;
1776 compared to Ant, Maven is much more declarative instead of procedural and is strongly focused on resolving dependencies on modules, components, libraries;
1777 dependencies (libraries) of a project are automatically downloaded from a repository;
1778 projects in Maven are described by a POM file
1785 <term abbreviation="POM" completeForm="Project Object Model" language="en"/>
1786 <explanation language="en">
1788 an XML configuration file which describes one Maven project;
1789 contains project metadata like name, owner, version, dependencies
1790 and phases of its build process
1797 <term abbreviation="" completeForm="Java" language="en"/>
1798 <explanation language="en">
1800 an object-oriented programming language designed by James Gosling at Sun Microsystems;
1801 Java source code is compiled into byte code (.class files) which can be executed in JVM on many architectures and operating systems;
1802 Java is completely free software, there is OpenJDK and standard library distributed under GNU GPL license;
1803 there is also GNU Classpath – an independent and free software implementation of the standard library;
1804 Java is popular and well established enterprise-grade software platform
1811 <term abbreviation="JVM" completeForm="Java virtual machine" language="en"/>
1812 <explanation language="en">
1814 a runtime environment for running Java byte code;
1815 there is lot of programming languages that can be compiled into the bytecode and executed in JVM e.g.
1816 Clojure (a Lisp dialect),
1817 Scala (OOP and functional language),
1818 Groovy (a scripting language),
1819 Jython (an implementation of Python),
1821 or Rhino (JavaScript)
1828 <term abbreviation="JavaDoc" completeForm="Java documentation" language="en"/>
1829 <explanation language="en">
1831 documentation of Java source code (classes, enumerations, interfaces, packages);
1832 describes API and software's internals;
1833 is useful for developers, not too much for end-users
1840 <term abbreviation="" completeForm="Erlang" language="en"/>
1841 <explanation language="en">
1843 a functional programming language developed in Ericsson;
1844 influenced by Prolog and SmallTalk languages;
1845 Erlang implementation is a free software
1851 <term abbreviation="RegEx" completeForm="Regular Expression" language="en"/>
1852 <term abbreviation="RegExp" completeForm="Regular Expression" language="en"/>
1853 <term abbreviation="RE" completeForm="Regular Expression" language="en"/>
1854 <explanation language="en">
1856 an expression (sequence of characters) which forms a pattern that can be used for string matching –
1857 finding occurrences of the pattern in the text or evaluating whether the whole text matches the pattern;
1858 Example: regular expression (a|b)cde\d+ matches strings acde123 or bcde0 but not cde1 or acdex
1864 <term abbreviation="PCRE" completeForm=" Perl Compatible Regular Expressions" language="en"/>
1865 <explanation language="en">
1867 a C library for regular expressions compatible with Perl's RegEx dialect
1868 or this dialect itself
1874 <term abbreviation="Perl" completeForm="Practical Extraction and Reporting Language" language="en"/>
1875 <explanation language="en">
1877 an interpreted dynamic programming language;
1878 popular in UNIX environment for scripting and text processing;
1879 Perl syntax allows very effective and elegant notation especially while working with regular expressions, but sometimes it is hard to read;
1880 its implementation is free software
1886 <term abbreviation="POSIX" completeForm="Portable Operating System Interface" language="en"/>
1887 <explanation language="en">
1889 a family of standards for maintaining compatibility between operating systems;
1890 defines API, command line shells and utility interfaces
1891 and thus brings compatibility amog many variants of unix and unix-like operating systems;
1892 the name POSIX was suggested by Richard Stallman (the standards was formerly known as IEEE-IX);
1893 there are standards for e.g. process creation and control, signals, pipes, message passing, shared memory or semaphores;
1894 Examples of fully or mostly POSIX-compliant systems: AIX, IRIS, Solaris, OS X, GNU/Linux, BeOS (Haiku) or several BSD variants
1900 <term abbreviation="" completeForm="UNIX" language="en"/>
1901 <term abbreviation="Unics" completeForm="UNiplexed Information and Computing Service" language="en"/>
1902 <explanation language="en">
1904 a multitasking and multi-user operating system developed in 1969 by a group of AT&T hackers at Bell Labs;
1905 has influenced many other operating systems (now called UNIX-like OS) and established distinctive UNIX culture and philosophy;
1906 nowadays we have completely free software implementation called GNU (resp. GNU/Linux where Linux is operating system kernel or GNU/Hurd);
1907 UNIX and UNIX-like operating systems runs on many mission-critical servers and are also used on personal computers or even mobile phones and small devices like routers or firewalls;
1908 GNU/Linux runs on 95,2 % (and other 3,4 % are Unices too) of world's supercomputers with 97,4 % performance share (top500.org, June 2013 statistics)
1914 <term abbreviation="" completeForm="GNU/Linux" language="en"/>
1915 <term abbreviation="" completeForm="Linux" language="en"/>
1916 <explanation language="en">
1918 the GNU operating system with Linux kernel;
1924 <term abbreviation="GNU" completeForm="GNU's Not Unix!" language="en"/>
1925 <explanation language="en">
1927 a Unix-like operating system that is free software and is upward-compatible with Unix;
1928 the GNU Project was initially announced in September 1983 by Richard Stallman;
1929 nowadays is mostly used in combination with Linux kernel and called GNU/Linux
1935 <term abbreviation="GNU GPL" completeForm="GNU General Public License" language="en"/>
1936 <term abbreviation="GPL" completeForm="General Public License" language="en"/>
1937 <explanation language="en">
1939 a free software and copyleft license which is used by many free software packages
1945 <term abbreviation="GNU FDL" completeForm="GNU Free Documentation License" language="en"/>
1946 <term abbreviation="FDL" completeForm="Free Documentation License" language="en"/>
1947 <explanation language="en">
1949 whereas GNU GPL is free and copyleft license for software,
1950 the GNU FDL is similar license designed for documentaion – books, articles, drawings etc.
1956 <term abbreviation="FS" completeForm="free software" language="en"/>
1957 <explanation language="en">
1959 a category of software which respects user's freedoms – user of such software has the four essential freedoms:
1960 0) The freedom to run the program, for any purpose.
1961 1) The freedom to study how the program works, and change it so it does your computing as you wish. Access to the source code is a precondition for this.
1962 2) The freedom to redistribute copies so you can help your neighbor.
1963 3) The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.;
1964 the term „Free software“ was defined by Richard Stallman
1970 <term abbreviation="OSS" completeForm="open source software" language="en"/>
1971 <explanation language="en">
1973 a category of software similar to Free software;
1974 the term „open source software“ was defined by Open Source Initiative;
1975 its definition contains ten requirements like free redistribution, available source code or allowing derived works;
1976 almost every open source license is also a free software license and vice versa;
1977 but there is different philosophical background – the free software movement has user's freedom as the main priority
1983 <term abbreviation="FSF" completeForm="Free Software Foundation" language="en"/>
1984 <explanation language="en">
1986 a non-profit organization founded by Richard Stallman on 4 October 1985 to support the free software movement;
1987 has developed the GNU operating system,
1988 issued licenses like GPL or FDL,
1989 maintains the Free Software Definition,
1990 does political campaigns and other activities related to user's freedoms;
1996 <term abbreviation="OSI" completeForm="Open Source Initiative" language="en"/>
1997 <explanation language="en">
1999 an organization dedicated to promoting open-source software;
2000 was founded in February 1998, by Bruce Perens and Eric S. Raymond;
2006 <term abbreviation="EFF" completeForm="Electronic Frontier Foundation" language="en"/>
2007 <explanation language="en">
2009 a non-profit organization focused on protecting user's freedoms and privacy in mostly digital world;
2010 fights against censorship and spying, criticises software patents
2011 and promotes – among others – free speech, privacy, e-voting and network neutrality
2017 <term abbreviation="OpenVMS" completeForm="Open Virtual Memory System" language="en"/>
2018 <term abbreviation="VMS" completeForm="Virtual Memory System" language="en"/><!-- informally -->
2019 <explanation language="en">
2021 an operating system for VAX, Alpha and Itanium-based computers
2027 <term abbreviation="VMS" completeForm="voice mail system" language="en"/><!-- informally -->
2028 <explanation language="en"><text></text></explanation>
2031 <term abbreviation="LDAP" completeForm="Lightweight Directory Access Protocol" language="en"/>
2032 <explanation language="en">
2034 a binary protocol for accessing directories (specialized databases);
2035 LDAP databases are usually optimalized for reading operations with rare write operations;
2036 provides a tree-oriented view on data which is different from relational one in RDBMS;
2037 despite that some LDAP servers use relational database as its backend
2045 <term abbreviation="GAL" completeForm="global address list" language="en"/>
2046 <explanation language="en">
2048 The Global Address List is a term used in groupware software
2049 and means the shared address book which contains usually all people of given organization (company, school etc.).
2050 This address book is accessed over the computer network using LDAP protocol, CardDAV or other electronic way (it is not a printed book).
2051 The GAL is usually read-only for users – only administrators adds or updates the items.
2052 Users can search it, lookup other people (employees, students, members etc.)
2053 and obtain information about them like e-mail address, phone number, work position, office location and others.
2054 The common usage of GAL is
2055 if the user is writing an e-mail,
2056 knows recipient's name,
2057 but don't know his e-mail address
2058 – the groupware or e-mail client (e.g. SOGo, Zimbra or Thunderbird) can lookup the e-mail address in the GAL while user is writing only a part of the recipient's name.
2064 <term abbreviation="" completeForm="white pages" language="en"/>
2065 <explanation language="en">
2067 a method of looking up in a directory;
2068 we know a person's name or MSISDN and we are fetching particular record from LDAP or other database;
2069 so it is similar to using the white pages (not yellow) of a telephone directory (a thick paperback book)
2075 <term abbreviation="" completeForm="yellow pages" language="en"/>
2076 <explanation language="en">
2078 a method of looking up in a directory;
2079 we know just some criteria of desired object and we are fetching a list of records from LDAP or other database;
2080 for example we can search for a PostScript printer in second floor or subscribers with particular tariff;
2081 so it is similar to using the yellow pages (not white) of a telephone directory (a thick paperback book)
2087 <term abbreviation="SQL" completeForm="structured query language" language="en"/>
2088 <term abbreviation="SEQUEL" completeForm="structured english query language" language="en"/>
2089 <explanation language="en">
2098 <term abbreviation="noSQL" completeForm="Not SQL" language="en"/>
2099 <explanation language="en"><text></text></explanation>
2104 <term abbreviation="RDBMS" completeForm="relational database management system" language="en"/>
2105 <term abbreviation="DBMS" completeForm="database management system" language="en"/>
2106 <term abbreviation="SŘDB" completeForm="systém řízení báze dat" language="cs"/>
2107 <explanation language="en"><text></text></explanation>
2112 <term abbreviation="ODBC" completeForm="open database connectivity" language="en"/>
2113 <explanation language="en">
2115 an industry standard that provides API for accessing a DBMS;
2116 in late 80s several vendors (mostly from the Unix and database communities) established the SQL Access Group (SAG)
2117 and then specified the Call Level Interface (CLI). ODBC, which is based on CLI, was published in early 90s;
2118 ODBC is available on many operating systems and there are at least two free software implementations: unixODBC and iODBC;
2119 in particular, it is an API consisting of C functions (see the files sql.h and sqlext.h e.g. in unixODBC or iODBC)
2126 <term abbreviation="JDBC" completeForm="java database connectivity" language="en"/>
2127 <explanation language="en">
2129 a standard Java API for accessing relational (SQL) databases
2137 <term abbreviation="" completeForm="data source" language="en"/>
2138 <explanation language="en">
2140 a set of parameters (like server name, user name, password etc.) needed for connecting to a database;
2141 a configuration (e.g. in a file) or then its instantiation (an object) in a running program from which particular database connections can be obtained;
2142 see also DSN, connection string
2149 <term abbreviation="DSN" completeForm="data source name" language="en"/>
2150 <explanation language="en">
2152 the name of a preconfigured data source
2153 – when connecting, we need to know only the DSN –
2154 all parameters (like server name, user name, password etc.) can be then looked-up in the configuration;
2155 see also data source, connection string
2162 <term abbreviation="" completeForm="connection string" language="en"/>
2163 <explanation language="en">
2165 a text string consisting of serialized parameters needed for connecting
2166 – we can specify all parameters ad-hoc in the connection string without creating any permanent configuration;
2167 a connection string can also refer to an already defined DSN and add or override its parameters
2168 see also DSN, data source
2175 <term abbreviation="AS" completeForm="application server" language="en"/>
2176 <explanation language="en"><text></text></explanation>
2181 <term abbreviation="" completeForm="JBoss" language="en"/>
2182 <explanation language="en"><text>an application server</text></explanation>
2187 <term abbreviation="" completeForm="GlassFish" language="en"/>
2188 <explanation language="en"><text>an application server</text></explanation>
2193 <term abbreviation="WSDL" completeForm="web services description language" language="en"/>
2194 <explanation language="en"><text></text></explanation>
2199 <term abbreviation="WADL" completeForm="web application description language" language="en"/>
2200 <explanation language="en"><text></text></explanation>
2205 <term abbreviation="SOAP" completeForm="simple object access protocol" language="en"/>
2206 <term abbreviation="SOAP" completeForm="SOA Protocol" language="en"/>
2207 <explanation language="en"><text></text></explanation>
2213 <term abbreviation="REST" completeForm="representational state transfer" language="en"/>
2214 <explanation language="en"><text></text></explanation>
2218 <term abbreviation="EJB" completeForm="Enterprise JavaBeans" language="en"/>
2219 <explanation language="en"><text></text></explanation>
2224 <term abbreviation="CORBA" completeForm="common object request broker architecture" language="en"/>
2225 <explanation language="en"><text></text></explanation>
2229 <term abbreviation="IDL" completeForm="interface definition language" language="en"/>
2230 <explanation language="en"><text></text></explanation>
2234 <term abbreviation="IIOP" completeForm="Internet InterORB Protocol" language="en"/>
2235 <term abbreviation="GIOP" completeForm="General Inter-ORB Protocol" language="en"/>
2236 <explanation language="en"><text></text></explanation>
2241 <term abbreviation="RMI" completeForm="Remote Method Invocation" language="en"/>
2242 <explanation language="en"><text></text></explanation>
2248 <term abbreviation="JAR" completeForm="Java ARchive" language="en"/>
2249 <explanation language="en">
2251 an archive format in which compiled Java classes, metadata and other resources are distributed;
2252 is based on the ZIP format and files have .jar extension;
2253 basic JAR files are used for desktop applications and Java libraries;
2254 there are also EAR and WAR for enterprise and web applications
2261 <term abbreviation="EAR" completeForm="Enterprise ARchive" language="en"/>
2262 <explanation language="en">
2264 a kind of JAR file in which an enterprise application is distributed/deployed
2271 <term abbreviation="WAR" completeForm="Web ARchive" language="en"/>
2272 <explanation language="en">
2274 a kind of JAR file in which a web application is distributed/deployed
2281 <term abbreviation="RAR" completeForm="Resource Adapter aRchive" language="en"/>
2282 <explanation language="en"><text></text></explanation>
2287 <term abbreviation="AJP" completeForm="Apache JServ Protocol" language="en"/>
2288 <explanation language="en"><text></text></explanation>
2294 <term abbreviation="HTTP" completeForm="hypertext transfer protocol" language="en"/>
2295 <term abbreviation="HTTPS" completeForm="hypertext transfer protocol secure" language="en"/>
2296 <explanation language="en"><text></text></explanation>
2301 <term abbreviation="SSL" completeForm="secure socket layer" language="en"/>
2302 <term abbreviation="TLS" completeForm="transport layer security" language="en"/>
2303 <explanation language="en"><text></text></explanation>
2309 <term abbreviation="DTLS" completeForm="datagram transport layer security" language="en"/>
2310 <explanation language="en"><text></text></explanation>
2315 <term abbreviation="BASH" completeForm="Bourne Again Shell" language="en"/>
2316 <explanation language="en"><text></text></explanation>
2320 <term abbreviation="SH" completeForm="shell" language="en"/>
2321 <explanation language="en"><text></text></explanation>
2325 <term abbreviation="SSH" completeForm="secure shell" language="en"/>
2326 <term abbreviation="" completeForm="OpenSSH" language="en"/>
2327 <explanation language="en"><text></text></explanation>
2333 <term abbreviation="SCP" completeForm="secure copy" language="en"/>
2334 <explanation language="en"><text></text></explanation>
2339 <term abbreviation="SFTP" completeForm="SSH file transfer protocol" language="en"/>
2340 <explanation language="en"><text></text></explanation>
2346 <term abbreviation="FTP" completeForm="file transfer protocol" language="en"/>
2347 <term abbreviation="FTPS" completeForm="file transfer protocol secure" language="en"/>
2348 <explanation language="en"><text></text></explanation>
2353 <term abbreviation="PGP" completeForm="Pretty Good Privacy" language="en"/>
2354 <term abbreviation="GPG" completeForm="GNU Privacy Guard" language="en"/>
2355 <term abbreviation="GnuPG" completeForm="GNU Privacy Guard" language="en"/>
2356 <term abbreviation="OpenPGP" completeForm="Open Pretty Good Privacy" language="en"/>
2357 <explanation language="en"><text></text></explanation>
2362 <term abbreviation="DSA" completeForm="digital signature algorithm" language="en"/>
2363 <explanation language="en"><text></text></explanation>
2368 <term abbreviation="RSA" completeForm="Ron Rivest, Adi Shamir and Leonard Adleman" language="en"/>
2369 <explanation language="en"><text></text></explanation>
2374 <term abbreviation="EC" completeForm="elliptic curve" language="en"/>
2375 <term abbreviation="ECC" completeForm="elliptic curve cryptography" language="en"/>
2376 <explanation language="en"><text></text></explanation>
2381 <term abbreviation="AES" completeForm="Advanced Encryption Standard" language="en"/>
2382 <term abbreviation="AES-128" completeForm="Advanced Encryption Standard 128-bit" language="en"/>
2383 <term abbreviation="AES-192" completeForm="Advanced Encryption Standard 192-bit" language="en"/>
2384 <term abbreviation="AES-256" completeForm="Advanced Encryption Standard 256-bit" language="en"/>
2385 <explanation language="en"><text></text></explanation>
2390 <term abbreviation="" completeForm="Camellia" language="en"/>
2391 <explanation language="en"><text></text></explanation>
2396 <term abbreviation="SHA" completeForm="secure hash algorithm" language="en"/>
2397 <term abbreviation="SHA-1" completeForm="secure hash algorithm 160-bit" language="en"/>
2398 <term abbreviation="SHA-2" completeForm="" language="en"/>
2399 <term abbreviation="SHA-3" completeForm="" language="en"/>
2400 <term abbreviation="SHA-256" completeForm="secure hash algorithm 256-bit" language="en"/>
2401 <term abbreviation="SHA-512" completeForm="secure hash algorithm 512-bit" language="en"/>
2402 <explanation language="en"><text></text></explanation>
2407 <term abbreviation="MD4" completeForm="message-digest algorithm 4" language="en"/>
2408 <explanation language="en"><text></text></explanation>
2413 <term abbreviation="MD5" completeForm="message-digest algorithm 5" language="en"/>
2414 <explanation language="en"><text></text></explanation>
2419 <term abbreviation="" completeForm="ethernet" language="en"/>
2420 <explanation language="en"><text></text></explanation>
2425 <term abbreviation="LAN" completeForm="local area network" language="en"/>
2426 <explanation language="en"><text></text></explanation>
2430 <term abbreviation="WAN" completeForm="wide area network" language="en"/>
2431 <explanation language="en"><text></text></explanation>
2435 <term abbreviation="WLAN" completeForm="wireless local area network" language="en"/>
2436 <explanation language="en"><text></text></explanation>
2440 <term abbreviation="VLAN" completeForm="virtual local area network" language="en"/>
2441 <explanation language="en"><text></text></explanation>
2446 <term abbreviation="IP" completeForm="Internet Protocol" language="en"/>
2447 <term abbreviation="IPv4" completeForm="Internet Protocol version 4" language="en"/>
2448 <term abbreviation="IPv6" completeForm="Internet Protocol version 6" language="en"/>
2449 <term abbreviation="" completeForm="IP address" language="en"/>
2450 <explanation language="en"><text></text></explanation>
2455 <term abbreviation="FQDN" completeForm="fully qualified domain name" language="en"/>
2456 <term abbreviation="" completeForm="absolute domain name" language="en"/>
2457 <explanation language="en">
2459 a domain name like „some-machine.example.com“ which completely specifies the location in the DNS hierarchy including the TLD;
2460 compared to „some-machine“ which is not FQDN – is not globally unambiguous and will be resolved differently in different contexts
2466 <term abbreviation="MAC" completeForm="media access control" language="en"/>
2467 <explanation language="en">
2469 a data communication protocol, a sublayer of the layer 2 in OSI model (data link layer);
2470 a MAC address is a unique identifier of an network interface – used for IEEE 802 networks including Ethernet;
2471 they are assigned by the manufacturer of the card and stored in the hardware (can be often changed by the software);
2472 there are three numbering namespaces: MAC-48, EUI-48 and EUI-64;
2473 the address has 6 or 8 bytes and they are usually written in HEX, octets separated by : (a colon)
2479 <term abbreviation="TCP" completeForm="transmission control protocol" language="en"/>
2480 <explanation language="en"><text></text></explanation>
2485 <term abbreviation="UDP" completeForm="user datagram protocol" language="en"/>
2486 <explanation language="en"><text></text></explanation>
2491 <term abbreviation="SCTP" completeForm="stream control transmission protocol" language="en"/>
2492 <explanation language="en"><text></text></explanation>
2496 <term abbreviation="QoS" completeForm="quality of service" language="en"/>
2497 <explanation language="en"><text></text></explanation>
2501 <term abbreviation="FUP" completeForm="fair usage policy" language="en"/>
2502 <explanation language="en">
2504 a set of rules that should avoid excessive usage of a service by one user to the detriment of other user's comfort;
2505 example: „You can download 10 GB at full speed every month. If you exceed this limit the speed of your connection will descend to 64 kb/s“
2510 <term abbreviation="API" completeForm="application programming interface" language="en"/>
2511 <explanation language="en">
2513 specifies interaction between software components;
2514 adds an abstraction layer which divides calling code and called code
2515 and enables multiple implementations of such API (or SPI) like multiple databases (database drivers), file systems, remote services etc.
2516 examples of API: POSIX, OpenGL, JDBC, JMS or JMX
2522 <term abbreviation="SPI" completeForm="service provider interface" language="en"/>
2523 <explanation language="en">
2525 a kind of API to be implemented by third party;
2526 can be installed as plugin/addon/extension and used by the application over standard interface;
2527 examples of SPI: JDBC, JNDI or JAXP
2534 <term abbreviation="JMX" completeForm="Java management extensions" language="en"/>
2535 <term abbreviation="MBean" completeForm="managed bean" language="en"/>
2536 <explanation language="en">
2538 a Java technology for monitoring and managing applications or devices;
2540 managed objects (MBeans) can emit events, can be asked for values (e.g. counters) or an action (method) can be called on them;
2541 this native Java technology can be also adapted/translated to other protocols like SNMP or WS/SOAP and integrated with the non-Java world;
2542 thanks to this abstraction, the managed object can implement only simple Java interface and don't have to deal with other protocols (which is job of generic adaptors)
2549 <term abbreviation="JMS" completeForm="Java message service" language="en"/>
2550 <explanation language="en">
2552 a Java API for message-oriented middleware (MOM);
2553 allows JEE components to create, send, receive and read messages;
2554 supports both point-to-point and publish-subscribe messaging models;
2555 can be adapted/translated to many other protocols like SMTP, AMQP, XMPP or SOAP;
2556 is defined in JSR 914;
2557 examples of JMS implementations: Apache ActiveMQ, OpenJMS, HornetQ
2562 <tag>messaging</tag>
2565 <term abbreviation="MOM" completeForm="message-oriented middleware" language="en"/>
2566 <explanation language="en">
2568 a software (or even hardware) infrastructure for sending and receiving messages;
2569 can also offer routing and transformation features;
2570 for Java the MOM API is standardized as JMS
2574 <tag>messaging</tag>
2577 <term abbreviation="AMQP" completeForm="advanced message queuing protocol" language="en"/>
2578 <explanation language="en">
2580 an open and standard binary protocol for message-oriented middleware (MOM);
2581 is vendor and platform independent;
2582 whereas JMS defines programming API and is Java specific, the AMQP defines the wire-level protocol;
2583 so JMS (or other language/platform specific API) can be used inside the system and AMQP can be used for interconnection of systems in heterogenous environment;
2584 example of implementation: Apache ActiveMQ
2588 <tag>messaging</tag>
2591 <term abbreviation="" completeForm="wire-level protocol" language="en"/>
2592 <explanation language="en">
2594 the format of data sent over the network as stream of bytes;
2595 an application layer protocol
2601 <term abbreviation="JCA" completeForm="Java connector architecture" language="en"/>
2602 <explanation language="en">
2604 a Java EE technology for connecting application servers (AS) and enterprise information systems (EIS);
2605 is similar to JDBC (which is used for connecting to databases) but is much more generic
2606 and allows connecting any (often legacy) system using a specific connector
2613 <term abbreviation="EIS" completeForm="enterprise information system" language="en"/>
2614 <explanation language="en">
2616 an enterprise-class software system;
2617 typically high quality and critical service, large volumes of data, robust, supporting business processes
2623 <term abbreviation="OSGi" completeForm="Open Services Gateway initiative" language="en"/>
2624 <explanation language="en">
2626 a framework and module system for Java;
2627 allows applications with modular architecture composed from components
2628 that can be loaded, started, stopped, updated or uninstalled without restarting the JVM and the application;
2629 examples of OSGi implementations: Apache Felix, Equinox and Knopflerfish
2636 <term abbreviation="VPN" completeForm="virtual private network" language="en"/>
2637 <explanation language="en"><text></text></explanation>
2642 <term abbreviation="P2P" completeForm="peer to peer" language="en"/>
2643 <explanation language="en"><text></text></explanation>
2647 <term abbreviation="DNS" completeForm="domain name system" language="en"/>
2648 <explanation language="en"><text></text></explanation>
2653 <term abbreviation="ENUM" completeForm="E.164 number mapping" language="en"/>
2654 <explanation language="en"><text></text></explanation>
2657 <term abbreviation="NAPTR" completeForm="naming authority pointer resource records" language="en"/>
2658 <explanation language="en"><text></text></explanation>
2661 <term abbreviation="SPID" completeForm="service profile identifier" language="en"/>
2662 <explanation language="en"><text></text></explanation>
2665 <term abbreviation="DN" completeForm="distinguished name" language="en"/>
2666 <explanation language="en"><text></text></explanation>
2670 <term abbreviation="CN" completeForm="common name" language="en"/>
2671 <explanation language="en"><text></text></explanation>
2675 <term abbreviation="SN" completeForm="surname" language="en"/>
2676 <explanation language="en"><text></text></explanation>
2680 <term abbreviation="DC" completeForm="domain component" language="en"/>
2681 <explanation language="en"><text></text></explanation>
2685 <term abbreviation="CR" completeForm="change request" language="en"/>
2686 <explanation language="en">
2688 a request for changing a software – new features or modification of existing ones;
2689 when one or more CRs are developed, they are delivered as new version of software product;
2690 CR is requested by the customer (mobile network operator) and is delivered by the development team;
2691 CR consists of one or more DT which are assigned to particular developers
2697 <term abbreviation="DT" completeForm="development ticket" language="en"/>
2698 <explanation language="en">
2700 a task assigned to a software developer;
2701 one or more DTs together usually forms a CR;
2702 it is also possible to have an internal DT which is not linked to any CR (e.g. some refactoring or fixes or maintenence which was not requested by the customer);
2703 each commit in the versioning system should be linked to a DT
2709 <term abbreviation="TT" completeForm="trouble ticket" language="en"/>
2710 <explanation language="en">
2712 a request for fixing something in the production;
2713 requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development)
2719 <term abbreviation="SRS" completeForm="System Requirement Specification" language="en"/>
2720 <explanation language="en">
2722 requirements on a software product or its particular change;
2723 is written from the system's point of view
2729 <term abbreviation="URS" completeForm="User Requirement Specification" language="en"/>
2730 <explanation language="en">
2732 requirements on a software product or its particular change;
2733 is written from the user's point of view
2739 <term abbreviation="" completeForm="engineering build" language="en"/>
2740 <explanation language="en">
2742 a build of a software product which was not done according to regular procedure and processes;
2743 might be used only for testing on site or during development – not in production;
2744 such software is often delivered as a tar.gz or JAR, WAR etc. file to be patched into existing installation, not as regular package (RPM, DEB etc.) as production version
2750 <term abbreviation="" completeForm="monkey patching" language="en"/>
2751 <explanation language="en"><text></text></explanation>
2754 <term abbreviation="GMT" completeForm="Greenwich mean time" language="en"/>
2755 <explanation language="en"><text></text></explanation>
2759 <term abbreviation="UTC" completeForm="coordinated universal time" language="en"/>
2760 <explanation language="en"><text></text></explanation>
2764 <term abbreviation="TZ" completeForm="timezone" language="en"/>
2765 <term abbreviation="TZ" completeForm="time-zone" language="en"/>
2766 <term abbreviation="TZ" completeForm="time zone" language="en"/>
2767 <explanation language="en"><text></text></explanation>
2771 <term abbreviation="IETF" completeForm="Internet Engineering Task Force" language="en"/>
2772 <explanation language="en"><text></text></explanation>
2776 <term abbreviation="RFC" completeForm="request for comments" language="en"/>
2777 <explanation language="en"><text></text></explanation>
2781 <term abbreviation="" completeForm="vendor lock-in" language="en"/>
2782 <term abbreviation="" completeForm="vendor-lock-in" language="en"/>
2783 <term abbreviation="" completeForm="vendor lock in" language="en"/>
2784 <explanation language="en"><text></text></explanation>
2788 <term abbreviation="UT" completeForm="unit test" language="en"/>
2789 <explanation language="en"><text></text></explanation>
2793 <term abbreviation="AT" completeForm="acceptance testing" language="en"/>
2794 <term abbreviation="UAT" completeForm="user acceptance testing" language="en"/>
2795 <explanation language="en"><text></text></explanation>
2799 <term abbreviation="" completeForm="code coverage" language="en"/>
2800 <explanation language="en"><text></text></explanation>
2804 <term abbreviation="" completeForm="jUnit" language="en"/>
2805 <explanation language="en"><text></text></explanation>
2810 <term abbreviation="" completeForm="TestNG" language="en"/>
2811 <explanation language="en"><text></text></explanation>
2816 <term abbreviation="" completeForm="tcpdump" language="en"/>
2817 <term abbreviation="" completeForm="tshark" language="en"/>
2818 <term abbreviation="" completeForm="wireshark" language="en"/>
2819 <explanation language="en"><text></text></explanation>
2824 <term abbreviation="" completeForm="Asterisk" language="en"/>
2825 <explanation language="en"><text></text></explanation>
2828 <term abbreviation="OTR" completeForm="off-the-record messaging" language="en"/>
2829 <explanation language="en"><text></text></explanation>
2832 <tag>messaging</tag>
2836 <term abbreviation="CLI" completeForm="command-line interface" language="en"/>
2837 <explanation language="en"><text></text></explanation>
2841 <term abbreviation="TUI" completeForm="text user interface" language="en"/>
2842 <explanation language="en"><text></text></explanation>
2846 <term abbreviation="GUI" completeForm="graphical user interface" language="en"/>
2847 <explanation language="en"><text></text></explanation>
2851 <term abbreviation="UI" completeForm="user interface" language="en"/>
2852 <explanation language="en"><text></text></explanation>
2856 <term abbreviation="EOL" completeForm="end of line" language="en"/>
2857 <explanation language="en"><text></text></explanation>
2861 <term abbreviation="COB" completeForm="close of business" language="en"/>
2862 <!-- e.g. you have until COB today to show us why you should not be disconnected -->
2863 <explanation language="en"><text></text></explanation>
2867 <term abbreviation="SCCB" completeForm="software configuration control board" language="en"/>
2868 <explanation language="en"><text></text></explanation>
2872 <term abbreviation="SCCB" completeForm="site configuration control board" language="en"/>
2873 <explanation language="en"><text></text></explanation>
2877 <term abbreviation="RBDL" completeForm="rule based decision logic" language="en"/>
2878 <explanation language="en"><text></text></explanation>
2883 <term abbreviation="" completeForm="OpenMoko" language="en"/>
2884 <term abbreviation="" completeForm="FreeRunner" language="en"/>
2885 <explanation language="en">
2887 an open hardware GSM phone
2892 <term abbreviation="" completeForm="OpenBSC" language="en"/>
2894 <explanation language="en"><text></text></explanation>
2897 <term abbreviation="BSC" completeForm="base station controller" language="en"/>
2898 <explanation language="en"><text></text></explanation>
2901 <term abbreviation="BTS" completeForm="base transceiver station" language="en"/>
2902 <explanation language="en"><text></text></explanation>
2905 <term abbreviation="MSC" completeForm="mobile switching center" language="en"/>
2906 <explanation language="en"><text></text></explanation>
2909 <term abbreviation="HLR" completeForm="home location register" language="en"/>
2910 <explanation language="en"><text></text></explanation>
2913 <term abbreviation="AuC" completeForm="authentication center" language="en"/>
2914 <explanation language="en"><text></text></explanation>
2917 <term abbreviation="VLR" completeForm="visitor location register" language="en"/>
2918 <explanation language="en"><text></text></explanation>
2921 <term abbreviation="EIR" completeForm="equipment identity register" language="en"/>
2922 <explanation language="en"><text></text></explanation>
2925 <term abbreviation="FXO" completeForm="foreign exchange office" language="en"/>
2926 <explanation language="en">
2928 the FXO interface is typically the plug on the phone (or modem)
2929 which receives the POTS service;
2930 should be connected to an FXS interface (not to another FXO interface)
2935 <term abbreviation="FXS" completeForm="foreign exchange station" language="en"/>
2936 <explanation language="en">
2938 the FXS interface is typically the plug on the wall
2939 which delivers the POTS service from telephone company to the subscriber;
2941 supplies battery power,
2944 should be connected to an FXO interface (not to another FXS interface)
2949 <term abbreviation="PBX" completeForm="private branch exchange" language="en"/>
2950 <explanation language="en">
2952 a kind of telephone exchange used in some office or company for its own purposes;
2953 provides FSX interface for connected phones;
2954 can have FXO interface for connecting to PSTN (for calling outside the company);
2955 nowadays are often deployed digital VoIP PBXes based on free software like Asterisk;
2956 such telephony can be pure IP based with no POTS or can have some FSX or FXO interfaces
2961 <term abbreviation="PLMN" completeForm="public land mobile network" language="en"/>
2962 <explanation language="en">
2964 a network established for providing mobile telecommunications services to the public;
2965 e.g. GSM or UMTS networks operated by various carriers;
2966 particular PLMNs are identified by MCC and MNC codes
2971 <term abbreviation="PSTN" completeForm="public switched telephone network" language="en"/>
2972 <explanation language="en">
2974 the worldwide public telephony network consisting of networks of particular carriers;
2975 the network is developed according to ITU-T standards and recommendations
2976 and uses uniform system of telephone numbers based on ITU-T recommendation E.164
2977 which provides a single global address space for telephone numbers
2982 <term abbreviation="POTS" completeForm="plain old telephone service" language="en"/>
2983 <explanation language="en">
2985 traditional wired telephony based on analog signals
2986 (contrary to ISDN which is digital)
2991 <term abbreviation="CID" completeForm="caller ID" language="en"/>
2992 <term abbreviation="CLIP" completeForm="calling line identification presentation" language="en"/>
2993 <term abbreviation="CLID" completeForm="calling line identification" language="en"/>
2994 <term abbreviation="CNID" completeForm="calling number identification" language="en"/>
2995 <term abbreviation="CND" completeForm="calling number delivery" language="en"/>
2996 <explanation language="en">
2998 a service that delivers caller's phone number to the called party's device during ringing;
2999 so the called party knows who is calling before answering the phone;
3000 this service is common in digital networks like VoIP, GSM or ISDN but can be provided also on analog POTS networks
3005 <term abbreviation="DTMF" completeForm="dual-tone multi-frequency signaling" language="en"/>
3006 <explanation language="en"><text></text></explanation>
3009 <term abbreviation="AGC" completeForm="auto gain control" language="en"/>
3010 <explanation language="en"><text></text></explanation>
3013 <term abbreviation="AEC" completeForm="auto echo cancellation" language="en"/>
3014 <explanation language="en"><text></text></explanation>
3017 <term abbreviation="VAD" completeForm="voice activity detection" language="en"/>
3018 <explanation language="en"><text></text></explanation>
3021 <term abbreviation="CNG" completeForm="comfort noise generation" language="en"/>
3022 <explanation language="en"><text></text></explanation>
3025 <term abbreviation="" completeForm="streamlining" language="en"/>
3026 <explanation language="en"><text>delivering better product faster with smaller teams of less-experienced engineers</text></explanation>
3027 <!-- Internal: if you dont understand, just ignore it :-) -->
3030 <term abbreviation="" completeForm="relevant company" language="en"/>
3031 <explanation language="en"><text>a company which is not going to bankrupt</text></explanation>
3032 <!-- Internal: if you dont understand, just ignore it :-) -->
3035 <term abbreviation="DAO" completeForm="data access object" language="en"/>
3036 <explanation language="en"><text></text></explanation>
3040 <term abbreviation="DTO" completeForm="data transfer object" language="en"/>
3041 <explanation language="en"><text></text></explanation>
3045 <term abbreviation="GSoC" completeForm="Google Summer of Code" language="en"/>
3046 <explanation language="en"><text>an annual program (since 2005) for students working on tasks for free software (open-source) projects</text></explanation>
3050 <term abbreviation="TBD" completeForm="to be done" language="en"/>
3051 <term abbreviation="TODO" completeForm="to do" language="en"/>
3052 <explanation language="en"><text>Something that should or will be done later. Used as comments in draft version of documents or in software source code.</text></explanation>
3056 <term abbreviation="FIXME" completeForm="fix me" language="en"/>
3057 <explanation language="en"><text>Something that should be fixed. Similar to TODO but describes rather some problem (bug) than feature request.</text></explanation>
3061 <term abbreviation="WIP" completeForm="work in progress" language="en"/>
3062 <explanation language="en"><text>It is not finished yet but it is in more advanced state than TODO. Someone is working on this task.</text></explanation>
3066 <term abbreviation="etc" completeForm="et cetera" language="la"/>
3067 <explanation language="en"><text>and so forth, and the rest</text></explanation>
3071 <term abbreviation="e.g" completeForm="exempli gratia" language="la"/>
3072 <explanation language="en"><text>for instance, for example</text></explanation>
3076 <term abbreviation="i.e." completeForm="id est" language="la"/>
3077 <explanation language="en"><text>in other words, that is</text></explanation>
3081 <term abbreviation="i.a." completeForm="inter alia" language="la"/>
3082 <explanation language="en"><text>among other things</text></explanation>
3086 <term abbreviation="N.B." completeForm="nota bene" language="la"/>
3087 <explanation language="en"><text>note well, note</text></explanation>
3091 <term abbreviation="per cent." completeForm="per centum" language="la"/>
3092 <explanation language="en"><text>percent, for each one hundred</text></explanation>
3096 <term abbreviation="p.a." completeForm="per annum" language="la"/>
3097 <explanation language="en"><text>annually</text></explanation>
3101 <term abbreviation="cca" completeForm="circa" language="la"/>
3102 <explanation language="en"><text>approximately</text></explanation>
3106 <term abbreviation="c.v." completeForm="curriculum vitae" language="la"/>
3107 <term abbreviation="CV" completeForm="curriculum vitae" language="la"/>
3108 <explanation language="en"><text>a document summarizing your relevant job experience and education</text></explanation>
3112 <term abbreviation="et al." completeForm="et alii" language="la"/>
3113 <explanation language="en"><text>and others, and co-workers</text></explanation>
3117 <term abbreviation="P.S." completeForm="post scriptum" language="la"/>
3118 <explanation language="en"><text>after what has been written; used at the end of the letters/messages for additions</text></explanation>
3122 <term abbreviation="Q.E.D." completeForm="quod erat demonstrandum" language="la"/>
3123 <explanation language="en"><text>which was to be demonstrated</text></explanation>
3127 <term abbreviation="R.I.P." completeForm="requiescat in pace" language="la"/>
3128 <explanation language="en"><text>rest in peace</text></explanation>
3132 <term abbreviation="vs." completeForm="versus" language="la"/>
3133 <explanation language="en"><text>against</text></explanation>