franta-hg@1: franta-hg@1: franta-hg@0: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@5: franta-hg@11: franta-hg@27: franta-hg@10: franta-hg@5: franta-hg@5: franta-hg@12: franta-hg@10: franta-hg@10: franta-hg@10: franta-hg@10: franta-hg@37: franta-hg@5: franta-hg@5: franta-hg@0: franta-hg@15: franta-hg@28: franta-hg@28: a provider which does not have own wireless network infrastructure; but does marketing and sets the prices for subscribers franta-hg@0: franta-hg@0: franta-hg@41: franta-hg@41: a company that provides technical services to MVNO thus MVNO can focus on marketing, pricing, brand and customer care franta-hg@41: franta-hg@41: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@28: franta-hg@28: franta-hg@33: a technique used in charging; franta-hg@28: for pre-paid subscribers the standard way to charge services is online franta-hg@30: – 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; franta-hg@30: 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; franta-hg@30: this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.) franta-hg@30: and can be done at the billing gateway or directly at system like SMSC franta-hg@28: franta-hg@28: franta-hg@30: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@26: franta-hg@26: franta-hg@26: a service or particular short text message sent from or to a mobile phone; franta-hg@26: 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; franta-hg@26: the number „160“ is iconic for SMS franta-hg@26: franta-hg@26: franta-hg@27: messaging franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: franta-hg@26: a unit of digital information; franta-hg@26: byte (almost always) consists of 8 bits, which means 256 possible values (2^8); franta-hg@26: 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) franta-hg@26: franta-hg@26: franta-hg@27: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@63: franta-hg@63: franta-hg@63: a service or particular multimedia message sent from or to a mobile phone; franta-hg@63: in contrast to SMS, supports not only text but also pictures, videos, sounds… franta-hg@63: thus subscriber can take a photo by his mobile phone and easily send it to a friend; franta-hg@63: other use case is AOMT messaging e.g. news with pictures or some premium content; franta-hg@63: MMS requires special infrastructure including MMSC deployed by the operator franta-hg@63: franta-hg@63: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@30: franta-hg@30: franta-hg@30: specific kind of MOAT short message which is used to donate money to charity or some organization; franta-hg@30: the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS franta-hg@30: franta-hg@30: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@62: franta-hg@62: franta-hg@62: an application-level extension to SMS; franta-hg@62: adds some new features like formatted text, pictures or sounds franta-hg@62: but works with existing networks (unlike MMS which requires new infrastructure) franta-hg@62: franta-hg@62: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@63: franta-hg@63: franta-hg@63: a markup language for describing multimedia presentations; franta-hg@63: describes timing, layout, animations etc. franta-hg@63: franta-hg@63: franta-hg@12: computer franta-hg@12: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@28: an XML-based file format for vector graphics franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@33: franta-hg@33: franta-hg@33: franta-hg@33: a kind of electronic communication between two persons or a group chat; franta-hg@33: 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; franta-hg@33: compared to SMS, IM messages are cheap – typically free of charge; franta-hg@33: important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.; franta-hg@50: 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; franta-hg@33: 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 franta-hg@33: franta-hg@33: franta-hg@9: computer franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@38: franta-hg@38: franta-hg@38: messaging franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: franta-hg@38: messaging franta-hg@38: franta-hg@38: franta-hg@34: franta-hg@50: franta-hg@50: franta-hg@50: franta-hg@50: a communication protocol for messaging based on XML; franta-hg@50: used for transferring franta-hg@50: IM messages, franta-hg@50: presence information (statuses like: online, busy, away etc.), franta-hg@50: contact list (called roster here) management, franta-hg@50: singaling of VoIP and video, file transfers etc.; franta-hg@50: can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction) franta-hg@50: or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide) franta-hg@50: franta-hg@50: franta-hg@34: computer franta-hg@34: xml franta-hg@34: messaging franta-hg@37: protocol franta-hg@34: franta-hg@34: franta-hg@50: franta-hg@50: a contact list; term used by Jabber/XMPP franta-hg@50: franta-hg@50: computer franta-hg@50: messaging franta-hg@50: franta-hg@50: franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for accessing e-mail mailbox; franta-hg@28: supports franta-hg@28: multiple hierarchical folders (inbox, sent, drafts… or user defined), franta-hg@28: marging messages with tags/flags, franta-hg@28: notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages), franta-hg@28: full-text search and other features; franta-hg@28: messages usually stays at server storage after reading which allows using multiple client programs/devices; franta-hg@28: is more complex than POP3 protocol; franta-hg@28: uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS) franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for accessing e-mail mailbox; franta-hg@28: messages are usually deleted from server after reading and are stored only on the client side; franta-hg@28: nowadays the more advanced IMAP4 protocol is often used instead of POP3; franta-hg@28: uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS) franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@42: franta-hg@28: franta-hg@28: franta-hg@28: a text-based client-server protocol for sending e-mail messages franta-hg@43: uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409); franta-hg@43: is defined in RFC 5321 franta-hg@28: franta-hg@28: franta-hg@9: computer franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@42: franta-hg@42: franta-hg@42: franta-hg@42: a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue); franta-hg@42: uses TCP/IP but must not use port 25 (SMTP); franta-hg@42: is defined in RFC 2033 franta-hg@42: franta-hg@42: franta-hg@42: computer franta-hg@42: messaging franta-hg@42: protocol franta-hg@42: franta-hg@42: franta-hg@12: franta-hg@40: franta-hg@40: franta-hg@40: an e-mail client – a software used for managing user's e-mail; franta-hg@40: because the MUA (like most client software) runs only when user needs it, franta-hg@40: the messages from the Internet are received by a remote MTA over the SMTP protocol, franta-hg@40: then delivered using an MDA into user's remote mailbox, franta-hg@40: from which they are obtained by the MUA using POP3 or IMAP4 protocols; franta-hg@40: 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; franta-hg@40: examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes franta-hg@40: franta-hg@40: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@49: franta-hg@49: franta-hg@42: franta-hg@42: franta-hg@42: franta-hg@44: a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving); franta-hg@44: messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP); franta-hg@44: examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James franta-hg@42: franta-hg@42: franta-hg@9: computer franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@49: franta-hg@45: franta-hg@45: franta-hg@45: a software component dedicated to receive e-mails from MUA; franta-hg@45: cooperates with MTA or is often integrated in MTA as one of its features; franta-hg@45: uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25) franta-hg@45: franta-hg@45: franta-hg@40: computer franta-hg@40: messaging franta-hg@40: franta-hg@40: franta-hg@49: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: a software component that receives e-mail from the MTA and stores them in the recipient's mailbox; franta-hg@46: the MDA can also apply Sieve filters on processed messages; franta-hg@46: examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop franta-hg@46: franta-hg@46: franta-hg@46: computer franta-hg@46: messaging franta-hg@46: franta-hg@46: franta-hg@49: franta-hg@48: franta-hg@48: franta-hg@48: a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol) franta-hg@48: 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.; franta-hg@48: implements pull (not push) approach: fetches messages periodically (or on user's demand) franta-hg@48: instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does); franta-hg@48: examples of MRA: fetchmail, getmail franta-hg@48: franta-hg@48: franta-hg@48: computer franta-hg@48: messaging franta-hg@48: franta-hg@48: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: a standardized language for describing e-mail filters; franta-hg@46: the MDA can apply system-wide or user-defined filters on incoming messages; franta-hg@47: a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“ franta-hg@47: 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“; franta-hg@46: filters are executed on the server where MDA resides, franta-hg@47: so they are independent of the MUA currently used by the user franta-hg@46: and works even if the user is offline (useful for OOTO messages when the user is on vacation) franta-hg@46: franta-hg@46: franta-hg@46: computer franta-hg@46: messaging franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@46: franta-hg@48: 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; franta-hg@46: in case of e-mail it can be easily configured as a Sieve filter franta-hg@46: franta-hg@46: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@84: franta-hg@84: franta-hg@84: an Internet standard for extended e-mail format which supports franta-hg@84: international character sets for body parts, franta-hg@84: international characters in message headers, franta-hg@84: attachements of various types, franta-hg@84: multipart messages; franta-hg@84: MIME message itself is a human-readable text starting with header section and having one or more body parts; franta-hg@84: binary or non-ASCII values are encoded in several ways described by the MIME's RFCs; franta-hg@84: 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 franta-hg@84: franta-hg@84: franta-hg@12: computer franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@85: franta-hg@85: franta-hg@85: an character encoding that can represent every character in the Unicode character set; franta-hg@85: is multibyte and variable-width encoding which means that one character can be represented by one or more bytes franta-hg@85: (i.e. character length of the text does not have to be equal to byte lenght of the data), franta-hg@85: in case of UTF-8 it is from 1 byte up to 6 bytes per character; franta-hg@85: is backward compatible with ASCII – one-byte characters in UTF-8 are encoded in same way as in ACSII; franta-hg@85: nowadays is widely used: on web, in e-mail, in operating systems (file names), in XML files etc. franta-hg@85: franta-hg@85: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@86: franta-hg@86: franta-hg@86: an multibyte but fixed-length (2 byte) character encoding; franta-hg@88: sometimes is used for SMS when international characters are needed – such single message has only 70 characters instead of 160 (7-bit encoding); franta-hg@86: for general use it was superseded by UTF-16 (in Unicode 2.0 in 1996) franta-hg@86: franta-hg@86: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@86: franta-hg@86: franta-hg@86: franta-hg@86: an multibyte and variable-width encoding for Unicode codepoints from 0 to 0x10FFFF; franta-hg@86: successor of UCS-2 encoding (for range 0-0xFFFF they have same values) franta-hg@86: franta-hg@86: franta-hg@86: computer franta-hg@86: franta-hg@86: franta-hg@12: franta-hg@89: franta-hg@89: franta-hg@89: open and industry standard protocol for transferring SMS messages among service centers (SC), applications (ESME) and routing entities (RE); franta-hg@89: was designed by the Aldiscon company (later Logica CMG and later Acision); franta-hg@89: binary PDUs are transported over TCP/IP or X.25 connection franta-hg@89: franta-hg@89: franta-hg@27: messaging franta-hg@37: protocol franta-hg@89: acision franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@87: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@11: charging franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@11: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@117: franta-hg@117: franta-hg@117: an ITU-T recommendation; franta-hg@117: full title: The international public telecommunication numbering plan; franta-hg@117: defines the numbering plan of the PSTN and general format of international phone numbers franta-hg@117: franta-hg@117: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@118: franta-hg@118: franta-hg@119: a globally unique indentifier of a subscription in a GSM or a UMTS network; franta-hg@118: follows numbering plan defined by E.164 – international phone number franta-hg@118: franta-hg@118: franta-hg@11: franta-hg@11: franta-hg@122: franta-hg@122: franta-hg@122: franta-hg@122: a number used to identify GSM, UMTS, LTE, iDEN or satelite mobile phones; franta-hg@122: it identifies the device not the subscribtion (like IMSI or MSISDN); franta-hg@122: on most phones can be displayed by typing *#06# franta-hg@122: franta-hg@122: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@119: franta-hg@119: franta-hg@119: a globally unique identifier stored on the SIM card used in GSM, UMTS and LTE networks; franta-hg@119: a 64 bit value usually presented as 15 digit number; franta-hg@119: consists of MCC (country code), MNC (network code) and MSIN (subscription ID) franta-hg@119: franta-hg@119: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@119: franta-hg@119: franta-hg@119: a unique numeric identifier of a country; franta-hg@119: a part of IMSI; franta-hg@119: often used in tuple with MNC; franta-hg@119: franta-hg@119: franta-hg@12: franta-hg@119: franta-hg@12: franta-hg@12: franta-hg@119: franta-hg@119: franta-hg@119: a unique numeric identifier of a mobile network (carrier); franta-hg@119: a part of IMSI; franta-hg@119: often used in tuple with MCC franta-hg@119: franta-hg@119: franta-hg@12: franta-hg@12: franta-hg@16: franta-hg@16: franta-hg@120: franta-hg@120: franta-hg@120: a part of IMSI franta-hg@120: franta-hg@120: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@121: franta-hg@121: franta-hg@121: franta-hg@121: franta-hg@121: a smartcard which contains IMSI, ke and cryptographic functions; franta-hg@121: is used to identify and authenticate subscribers in mobile phone networks franta-hg@121: franta-hg@121: franta-hg@11: franta-hg@11: franta-hg@123: franta-hg@123: franta-hg@123: franta-hg@123: franta-hg@123: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@19: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: finance franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@124: franta-hg@124: franta-hg@124: an MMS protocol used between a Mobile Station and an MMSC; franta-hg@124: is based on WAP and SMS franta-hg@124: franta-hg@124: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@124: franta-hg@124: franta-hg@124: an MMS protocol used between an MMSC and VASP; franta-hg@124: is based on SOAP, HTTP and MIME franta-hg@124: franta-hg@124: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@125: franta-hg@125: franta-hg@125: an AAA protocol and a successor of the RADIUS protocol; franta-hg@125: consists of the base protocol and many „Diameter Applications“ (protocols based on Diameter) franta-hg@125: e.g. franta-hg@125: Diameter Credit-Control Application, franta-hg@125: Diameter Session Initiation Protocol Application or franta-hg@125: Diameter Extensible Authentication Protocol Application franta-hg@125: franta-hg@125: franta-hg@10: security franta-hg@10: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@126: franta-hg@126: franta-hg@126: franta-hg@126: an AAA protocol and the predecessor of the Diameter protocol; franta-hg@126: franta-hg@126: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@6: ericsson franta-hg@10: charging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@126: franta-hg@126: franta-hg@126: a number which represents the result of an operation in the Diameter protocol; franta-hg@126: codes are divided into several groups: franta-hg@126: 1xxx – Informational, franta-hg@126: 2xxx – Success, franta-hg@126: 3xxx – Protocol errors, franta-hg@126: 4xxx – Transient failures, franta-hg@126: 5xxx – Permanent failure; franta-hg@126: for example 2001 means success, 2002 limited success, 3001 unsupported command or 5001 unsupported AVP franta-hg@126: franta-hg@126: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: nsn franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: charging franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@127: franta-hg@127: franta-hg@127: one of two peers involved in charging process; franta-hg@127: CTF decides how to charge particular subscriber for specific service; franta-hg@127: issues requests to the OCF franta-hg@127: franta-hg@127: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@127: franta-hg@127: franta-hg@127: one of two peers involved in charging process; franta-hg@127: accepts requests from CTF and performs actual charging franta-hg@127: based on the message type, service logic, user's profile or other circumstances franta-hg@127: franta-hg@127: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@35: franta-hg@35: franta-hg@35: franta-hg@35: the party (sender or recipient) who is charged for the service (e.g. SMS); franta-hg@35: MOMT messages (or other traffic) are typically charged to the sender (A); franta-hg@35: AOMT messages (like weather forecast or news) are typically charged to the recipient (B); franta-hg@35: some messages can be free of charge and some can be charged to both party (AB) franta-hg@35: franta-hg@35: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@36: franta-hg@36: franta-hg@38: a subscriber of a mobile network, a customer of a telco operator franta-hg@38: (but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator) franta-hg@36: franta-hg@36: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@89: franta-hg@127: franta-hg@127: franta-hg@127: a software component located between the SMSC (or other service centre) and ESME (applications); franta-hg@127: passes messages in both directions, franta-hg@127: uses SMPP and other messaging protocols, franta-hg@127: does routing of messages, their transformations, conversions or other operations franta-hg@127: franta-hg@127: franta-hg@0: franta-hg@0: franta-hg@24: franta-hg@127: franta-hg@127: franta-hg@127: a kind of subscription where the subscriber pays in advance franta-hg@127: and his services are charged (usually immediately, online) from his pre-paid balance franta-hg@127: franta-hg@127: franta-hg@24: charging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@127: franta-hg@127: franta-hg@127: a kind of subscription where the subscriber pays later than he uses the services (usually monthly); franta-hg@127: compared to pre-paid, batch processing of CDR files and offline processing is common here franta-hg@127: franta-hg@127: franta-hg@24: charging franta-hg@24: franta-hg@24: franta-hg@12: franta-hg@12: franta-hg@24: franta-hg@24: franta-hg@24: kind of log file in machine-readable format (ASN.1, XML, CSV etc.) franta-hg@24: which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection; franta-hg@24: CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage; franta-hg@24: they must be handled carefully because they contain private information (who calls or texts who); franta-hg@24: always respect subscriber's privacy! franta-hg@24: franta-hg@24: franta-hg@24: charging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@65: franta-hg@65: franta-hg@65: traffic which comes from a cell phone resp. mobile network, franta-hg@65: e.g. an SMS sent from your Handy franta-hg@65: franta-hg@65: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@65: franta-hg@65: franta-hg@65: traffic which comes to a cell phone resp. mobile network, franta-hg@65: e.g. a received SMS franta-hg@65: franta-hg@65: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@65: franta-hg@65: franta-hg@65: traffic which comes from an application i.e. not from the mobile network/phone, franta-hg@65: e.g. some weather forecast messages generated by an SPA franta-hg@65: franta-hg@65: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@65: franta-hg@65: franta-hg@65: traffic which comes to an application i.e. not to the mobile network/phone, franta-hg@65: e.g. message sent to an application in order to subscribe the service or to send your vote franta-hg@65: franta-hg@65: franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. when Bob texts Alice from his phone to her phone franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. if Bob subscribes a weather forecast service by sending a message from his phone franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: e.g. if Alice receives to her phone a news message which she has previously subscribed franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@65: franta-hg@65: franta-hg@65: if two applications communicates over an SMS gateway and there are no cell phones involved; franta-hg@65: this is pretty rare, but somewhere you can meet such configuration franta-hg@65: franta-hg@65: franta-hg@27: messaging franta-hg@24: franta-hg@24: franta-hg@24: franta-hg@24: a cell phone franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: charging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@64: franta-hg@64: franta-hg@64: when a subscriber communicates with an application (MOAT/AOMT messaging) franta-hg@64: he might not want expose his identity (MSISDN or IMSI); franta-hg@64: the aliasing feature (sometimes called hashing) deployed on an SMS gateway enables this communication and rewrites the subscriber's ID to some generated ID; franta-hg@64: 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); franta-hg@64: use case: franta-hg@64: subscribers can vote in some survey, franta-hg@64: everyone will have one vote, franta-hg@64: but the owner of the survey will not know the opinion of particular subscibers franta-hg@64: because of missing their real IDs franta-hg@64: franta-hg@64: franta-hg@10: security franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@10: franta-hg@128: franta-hg@128: franta-hg@128: franta-hg@128: a special kind of phone number which has few digits (e.g. four); franta-hg@128: ESME usually has assigned a short number franta-hg@128: thus subscriber can do MOAT messaging without remembering/typing long phone numbers; franta-hg@128: texting or calling to/from this numbers might be charged with an extra rate franta-hg@128: (the subscriber pays not only for the telco service but also for the VAS provided) franta-hg@128: franta-hg@128: franta-hg@27: messaging franta-hg@10: franta-hg@10: franta-hg@12: franta-hg@36: franta-hg@36: franta-hg@36: a provider who operates an ESME (application) franta-hg@36: franta-hg@36: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@36: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@36: franta-hg@36: franta-hg@36: 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; franta-hg@36: often is operated by different company than telco operator – a VASP; franta-hg@36: franta-hg@36: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@129: franta-hg@129: franta-hg@129: an end-point in RE where SC is connected franta-hg@129: franta-hg@129: franta-hg@129: messaging franta-hg@129: franta-hg@129: franta-hg@129: franta-hg@129: franta-hg@129: franta-hg@129: an end-point in RE where SPA is connected franta-hg@129: franta-hg@129: franta-hg@27: messaging franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@6: franta-hg@6: franta-hg@6: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: Nokia's protocol for sending and receiving MMS, is based on HTTP and transferres binary content. franta-hg@12: nsn franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: an extension of UCP franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: nsn franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: A simple protocol that can be used between AAG and SPA for transmitting messages. Uses HTTP GET method and encodes data in the URL or in HTTP response body franta-hg@12: acision franta-hg@27: messaging franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@96: franta-hg@90: franta-hg@90: franta-hg@90: a component in telecommunication network; franta-hg@90: SMSC for SMS or MMSC for MMS messages franta-hg@90: franta-hg@90: franta-hg@27: messaging franta-hg@10: franta-hg@10: franta-hg@12: franta-hg@91: franta-hg@91: franta-hg@91: franta-hg@91: a component in telecommunication network dedicated to store, forward, convert and deliver SMS messages; franta-hg@91: is connected to the SS7 network on one side and to routing entities (RE) using SMPP on the other side; franta-hg@91: is able to process MOMT messaging and also MOAT or AOMT messaging (using RE) franta-hg@91: Example of SMSC: SMSCv5 franta-hg@91: franta-hg@91: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@91: franta-hg@91: franta-hg@91: franta-hg@91: an implementation of SMSC from Acision; franta-hg@91: runs on an OpenVMS system franta-hg@91: franta-hg@91: franta-hg@6: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@92: franta-hg@92: franta-hg@92: franta-hg@92: franta-hg@92: franta-hg@92: a kind of SC dedicated to processing multimedia messages; franta-hg@92: the messaging is more comlex process than in case of SMS: franta-hg@92: MO MMS message is received (in similar format to MIME e-mail) by the MMSC and stored, franta-hg@92: then SC determines if the recipient is capable to receive MMS, franta-hg@92: 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, franta-hg@92: if recipient is not capable he gets plain text SMS with URL and have to use computer and www browser franta-hg@92: franta-hg@92: franta-hg@87: messaging franta-hg@87: franta-hg@87: franta-hg@87: franta-hg@87: franta-hg@93: franta-hg@93: franta-hg@93: a consolidated messaging platform announced by the Acision company in 2013; franta-hg@93: integrates RSC, SMS, MMS and voice mail franta-hg@93: franta-hg@93: franta-hg@87: acision franta-hg@87: messaging franta-hg@87: franta-hg@87: franta-hg@12: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@95: franta-hg@95: franta-hg@95: franta-hg@95: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@94: franta-hg@94: franta-hg@94: delivering voice communication (or other multimedia sessions like video) over the Internet Protocol (IP) instead of traditional telco networks; franta-hg@94: there are open and standard protocols for signaling: SIP and XMPP and open protocols for the payload (audio/video) like RTP; franta-hg@94: VoIP is nowadays widely used inside companies where often shares same ethernet network with computers (can be separeted by VLANs) franta-hg@94: and also in households espetially for cheap overseas calls; franta-hg@94: as VoIP phone can be used a computer with appropriate software or a cell phone or dedicated hardware phone; franta-hg@94: there are also gateways that enable connecting old analog phones to the VoIP network franta-hg@94: franta-hg@94: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@38: roaming of subscribers from other operator in your network franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@38: roaming of your subscribers in other operator's network franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@39: franta-hg@39: franta-hg@39: (0x00) Unknown type of number; franta-hg@39: (0x01) International number; franta-hg@39: (0x02) National number; franta-hg@39: (0x03) Network specific number; franta-hg@39: (0x04) Subscriber number, dedicated access, short code; franta-hg@39: (0x05) Alphanumeric, in 7-bit GSM alphabet; franta-hg@39: (0x06) Abbreviated number franta-hg@39: franta-hg@39: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@39: franta-hg@39: franta-hg@39: a number which indicates the numbering plan of a telephone number; franta-hg@39: values: franta-hg@39: (0x00) Unknown numbering plan; franta-hg@39: (0x01) ISDN/telephone numbering plan – E.164/E.163; franta-hg@39: (0x02) Generic; franta-hg@39: (0x03) Data numbering plan – X.121; franta-hg@39: (0x04) Telex numbering plan – F.96; franta-hg@39: (0x05) Service Centre Specific plan; franta-hg@39: (0x06) Land mobile numbering plan – E.212; franta-hg@39: (0x07) ISDN/mobile numbering plan – E.214; franta-hg@39: franta-hg@39: (0x08) National numbering plan; franta-hg@39: (0x09) Private numbering plan; franta-hg@39: (0x0A) ERMES numbering plan – ETSI DE/PS 3 01-3; franta-hg@39: (0x0D) Binary Internet addres – IP; franta-hg@39: (0x0E) Alphanumeric Internet address franta-hg@39: franta-hg@39: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@97: franta-hg@97: franta-hg@97: one octet of information which describes the protocol resp. type of telematic device; franta-hg@97: 0 means implicit (plain MOMT messages); franta-hg@97: other values are described in 3GPP TS 03.40 franta-hg@97: franta-hg@97: franta-hg@0: franta-hg@0: franta-hg@98: franta-hg@98: franta-hg@98: franta-hg@98: identifier of an process (running program) in an operating system; franta-hg@99: PID 1 is usually assigned to the init process (the first process which starts other ones) franta-hg@98: franta-hg@98: franta-hg@98: computer franta-hg@98: franta-hg@98: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@108: franta-hg@108: franta-hg@108: hacker is an interrogative person interested in internal principles of things; franta-hg@108: often it is a software developer or a system administrator but hacking is also possible outside the digital world; franta-hg@108: hacking is the activity of these people – usually franta-hg@108: improving a software by adding new features franta-hg@108: or discovering secrets in existing software or hardware systems franta-hg@108: or running extraordinary configurations or combinations of components; franta-hg@108: hack is the product of their work – e.g. improved computer program or piece of hardware; franta-hg@108: franta-hg@108: don't confuse with „cracker“ franta-hg@108: franta-hg@108: franta-hg@108: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@109: franta-hg@109: franta-hg@109: someone who breaks the security protections in order to get unauthorized access to a computer system; franta-hg@109: they often misuse their skills to steal private data, destroy systems or steal money; franta-hg@109: don't confuse with „hacker“ franta-hg@109: franta-hg@109: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@110: franta-hg@110: franta-hg@110: a hacker interested in phone systems or telecommunications in general; franta-hg@110: sometimes they can become cracker if they don't only experiment but misuse telephone networks excessively (fraud); franta-hg@110: the term is a portmanteau of the words „phone“ and „freak“ franta-hg@110: franta-hg@110: franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@106: franta-hg@106: franta-hg@107: a software component developed by the Acision company; franta-hg@106: a provisioning tool for AAG and other products of this company; franta-hg@106: can be used as generic provisioning tool for any product provided that particular connector exists; franta-hg@106: has web GUI and several APIs franta-hg@106: franta-hg@106: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@107: franta-hg@107: franta-hg@107: a software component developed by the Acision company; franta-hg@107: typical use case is: a messaging gateway between SMSC and applications (ESME) franta-hg@107: franta-hg@107: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@105: franta-hg@105: franta-hg@107: a software component developed by the Acision company; franta-hg@105: works as a messaging gateway and can interconnect systems talking many various messaging protocols; franta-hg@105: is highly configurable and can translate and transform messages in many formats; franta-hg@105: original purpose was doing a gateway for billing messages comming from e.g. SMSC to some billing system franta-hg@105: franta-hg@105: franta-hg@9: acision franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@104: franta-hg@104: franta-hg@104: content in various media formats (text, pictures, video, sound…) franta-hg@104: which is created by users (or subscribers); franta-hg@104: e.g. photos taken by mobile and sent over MMS, e-mail or web to some server which displays them to other users franta-hg@104: franta-hg@104: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@101: franta-hg@103: franta-hg@103: franta-hg@103: a software tool used for management of changes in documents; franta-hg@103: often is used for managing source code and other artifacts (like documentation or analytic models) created during software development; franta-hg@103: VCS tracks versions of particular files or changesets, branches, tags (named revisions); franta-hg@103: examples of traditional centralized VCS: SCCS, RCS, CVS or SVN (quite modern but centralized); franta-hg@103: nowadays are very popular decentralized systems (DVCS) franta-hg@103: franta-hg@103: franta-hg@101: computer franta-hg@101: franta-hg@101: franta-hg@101: franta-hg@101: franta-hg@102: franta-hg@102: franta-hg@102: kind of version control system which allows not only workflow with one central server franta-hg@102: but also decentralized workflows where changesets are pushed or pulled between particular nodes; franta-hg@102: each node has typically full repository clone with all the history (commits, branches, tags); franta-hg@102: this facilitates offline work – franta-hg@102: developer can do commits or work with branches and tags even if he is offline – franta-hg@102: and after going online, franta-hg@102: he pushed his work to other developers franta-hg@102: or to the central repository franta-hg@102: or his work is pulled by others; franta-hg@102: other advantage is easy backup – just clone the repository and then do push/pull from the working one; franta-hg@102: Examples of DVCS: Mercurial (Hg), Git, Bazaar (bzr), Monotone (mtn), Fossil, GNU arch, Darcs, DCVS or SVK franta-hg@102: franta-hg@102: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@101: a distributed version control system franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@101: a centralized version control system franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@101: a centralized version control system franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@101: a distributed version control system franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@101: a distributed version control system franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@19: franta-hg@19: franta-hg@19: computer franta-hg@19: xml franta-hg@19: franta-hg@19: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@100: franta-hg@100: franta-hg@100: franta-hg@100: a validation language; franta-hg@100: can describe formats based on XML like XSD or DTD does, but has entirely different approach; franta-hg@100: Schematron is rule-based – defines assertions which must be met to have valid document; franta-hg@100: this rules are transformed into XSL template which is executed during validation; franta-hg@100: Schematron can be also combined with XSD franta-hg@100: – XSD schemas (which are more declarative and more clearly represents the desired structure of the document for humans) franta-hg@100: are enriched with Schematron assertions that adds more complex rules (that cannot be easily expressed in pure XSD) franta-hg@100: franta-hg@100: franta-hg@100: computer franta-hg@100: xml franta-hg@100: franta-hg@100: franta-hg@12: franta-hg@19: franta-hg@100: franta-hg@100: franta-hg@100: a transformation language for XML; franta-hg@100: can be used e.g. for franta-hg@100: conversion from one XML format to another one, franta-hg@100: for generating (plain) text or HTML, franta-hg@100: for user friendly visualisation of XML data (XHTML or SVG output), franta-hg@100: or for validations (raise error message on invalid input, see also Schematron); franta-hg@100: XSL templates are also written in XML franta-hg@100: franta-hg@100: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@67: franta-hg@67: franta-hg@67: a tool for automating software build processes; franta-hg@67: does similar job like GNU Make, but is written in and for Java; franta-hg@67: equivalent for the Makefile is here build.xml which describes particular tasks and their dependencies; franta-hg@68: there is lot of tasks distributed with Apache Ant e.g. franta-hg@68: compilation of Java code, franta-hg@68: unit testing, franta-hg@68: running XSLT transformations, franta-hg@68: packing JARs and other archives, franta-hg@68: copying and moving files franta-hg@68: or calling system commands; franta-hg@67: and user can also write own tasks in Java franta-hg@67: franta-hg@67: franta-hg@12: computer franta-hg@12: java franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@68: franta-hg@68: franta-hg@68: a tool for automating software build processes; franta-hg@68: compared to Ant, Maven is much more declarative instead of procedural and is strongly focused on resolving dependencies on modules, components, libraries; franta-hg@68: dependencies (libraries) of a project are automatically downloaded from a repository; franta-hg@68: projects in Maven are described by a POM file franta-hg@68: franta-hg@68: franta-hg@68: computer franta-hg@68: java franta-hg@68: franta-hg@68: franta-hg@68: franta-hg@68: franta-hg@68: franta-hg@68: an XML configuration file which describes one Maven project; franta-hg@68: contains project metadata like name, owner, version, dependencies franta-hg@68: and phases of its build process franta-hg@68: franta-hg@68: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@69: franta-hg@69: franta-hg@69: an object-oriented programming language designed by James Gosling at Sun Microsystems; franta-hg@69: Java source code is compiled into byte code (.class files) which can be executed in JVM on many architectures and operating systems; franta-hg@69: Java is completely free software, there is OpenJDK and standard library distributed under GNU GPL license; franta-hg@69: there is also GNU Classpath – an independent and free software implementation of the standard library; franta-hg@69: Java is popular and well established enterprise-grade software platform franta-hg@69: franta-hg@69: franta-hg@69: computer franta-hg@69: java franta-hg@69: franta-hg@69: franta-hg@69: franta-hg@69: franta-hg@69: franta-hg@69: a runtime environment for running Java byte code; franta-hg@69: there is lot of programming languages that can be compiled into the bytecode and executed in JVM e.g. franta-hg@69: Clojure (a Lisp dialect), franta-hg@69: Scala (OOP and functional language), franta-hg@69: Groovy (a scripting language), franta-hg@69: Jython (an implementation of Python), franta-hg@69: JRuby franta-hg@69: or Rhino (JavaScript) franta-hg@69: franta-hg@69: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@19: franta-hg@70: franta-hg@70: franta-hg@70: documentation of Java source code (classes, enumerations, interfaces, packages); franta-hg@70: describes API and software's internals; franta-hg@70: is useful for developers, not too much for end-users franta-hg@70: franta-hg@70: franta-hg@19: computer franta-hg@19: java franta-hg@19: franta-hg@19: franta-hg@0: franta-hg@71: franta-hg@71: franta-hg@71: a functional programming language developed in Ericsson; franta-hg@71: influenced by Prolog and SmallTalk languages; franta-hg@71: Erlang implementation is a free software franta-hg@71: franta-hg@71: franta-hg@9: ericsson franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@72: franta-hg@72: franta-hg@72: an expression (sequence of characters) which forms a pattern that can be used for string matching – franta-hg@72: finding occurrences of the pattern in the text or evaluating whether the whole text matches the pattern; franta-hg@72: Example: regular expression (a|b)cde\d+ matches strings acde123 or bcde0 but not cde1 or acdex franta-hg@72: franta-hg@72: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@72: franta-hg@72: franta-hg@72: a C library for regular expressions compatible with Perl's RegEx dialect franta-hg@72: or this dialect itself franta-hg@72: franta-hg@72: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@73: franta-hg@73: franta-hg@73: franta-hg@73: an interpreted dynamic programming language; franta-hg@73: popular in UNIX environment for scripting and text processing; franta-hg@73: Perl syntax allows very effective and elegant notation especially while working with regular expressions, but sometimes it is hard to read; franta-hg@73: its implementation is free software franta-hg@73: franta-hg@73: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@74: franta-hg@74: franta-hg@74: a family of standards for maintaining compatibility between operating systems; franta-hg@74: defines API, command line shells and utility interfaces franta-hg@74: and thus brings compatibility amog many variants of unix and unix-like operating systems; franta-hg@74: the name POSIX was suggested by Richard Stallman (the standards was formerly known as IEEE-IX); franta-hg@74: there are standards for e.g. process creation and control, signals, pipes, message passing, shared memory or semaphores; franta-hg@74: Examples of fully or mostly POSIX-compliant systems: AIX, IRIS, Solaris, OS X, GNU/Linux, BeOS (Haiku) or several BSD variants franta-hg@74: franta-hg@74: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@75: franta-hg@75: franta-hg@75: a multitasking and multi-user operating system developed in 1969 by a group of AT&T hackers at Bell Labs; franta-hg@75: has influenced many other operating systems (now called UNIX-like OS) and established distinctive UNIX culture and philosophy; franta-hg@75: nowadays we have completely free software implementation called GNU (resp. GNU/Linux where Linux is operating system kernel or GNU/Hurd); franta-hg@75: 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; franta-hg@75: 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) franta-hg@75: franta-hg@75: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@76: franta-hg@76: franta-hg@76: the GNU operating system with Linux kernel franta-hg@76: franta-hg@76: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@78: franta-hg@79: franta-hg@79: franta-hg@79: a Unix-like operating system that is free software and is upward-compatible with Unix; franta-hg@79: the GNU Project was initially announced in September 1983 by Richard Stallman; franta-hg@79: nowadays is mostly used in combination with Linux kernel and called GNU/Linux franta-hg@79: franta-hg@79: franta-hg@78: computer franta-hg@78: franta-hg@78: franta-hg@78: franta-hg@78: franta-hg@79: franta-hg@79: franta-hg@79: a free software and copyleft license which is used by many free software packages franta-hg@79: franta-hg@79: franta-hg@78: computer franta-hg@78: franta-hg@78: franta-hg@78: franta-hg@78: franta-hg@79: franta-hg@79: franta-hg@79: whereas GNU GPL is free and copyleft license for software, franta-hg@79: the GNU FDL is similar license designed for documentaion – books, articles, drawings etc. franta-hg@79: franta-hg@79: franta-hg@78: computer franta-hg@78: franta-hg@78: franta-hg@77: franta-hg@79: franta-hg@79: franta-hg@79: a category of software which respects user's freedoms – user of such software has the four essential freedoms: franta-hg@79: 0) The freedom to run the program, for any purpose. franta-hg@79: 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. franta-hg@79: 2) The freedom to redistribute copies so you can help your neighbor. franta-hg@79: 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.; franta-hg@79: the term „Free software“ was defined by Richard Stallman franta-hg@79: franta-hg@79: franta-hg@77: computer franta-hg@77: franta-hg@77: franta-hg@77: franta-hg@80: franta-hg@80: franta-hg@80: a category of software similar to Free software; franta-hg@80: the term „open source software“ was defined by Open Source Initiative; franta-hg@80: its definition contains ten requirements like free redistribution, available source code or allowing derived works; franta-hg@80: almost every open source license is also a free software license and vice versa; franta-hg@80: but there is different philosophical background – the free software movement has user's freedom as the main priority franta-hg@80: franta-hg@80: franta-hg@77: computer franta-hg@77: franta-hg@77: franta-hg@77: franta-hg@81: franta-hg@81: franta-hg@81: a non-profit organization founded by Richard Stallman on 4 October 1985 to support the free software movement; franta-hg@81: has developed the GNU operating system, franta-hg@81: issued licenses like GPL or FDL, franta-hg@81: maintains the Free Software Definition, franta-hg@81: does political campaigns and other activities related to user's freedoms; franta-hg@81: franta-hg@81: franta-hg@77: computer franta-hg@77: franta-hg@77: franta-hg@77: franta-hg@82: franta-hg@82: franta-hg@82: an organization dedicated to promoting open-source software; franta-hg@82: was founded in February 1998, by Bruce Perens and Eric S. Raymond; franta-hg@82: franta-hg@82: franta-hg@77: computer franta-hg@77: franta-hg@77: franta-hg@77: franta-hg@83: franta-hg@83: franta-hg@83: a non-profit organization focused on protecting user's freedoms and privacy in mostly digital world; franta-hg@83: fights against censorship and spying, criticises software patents franta-hg@83: and promotes – among others – free speech, privacy, e-voting and network neutrality franta-hg@83: franta-hg@83: franta-hg@77: computer franta-hg@77: franta-hg@77: franta-hg@76: franta-hg@76: franta-hg@76: franta-hg@76: franta-hg@76: an operating system for VAX, Alpha and Itanium-based computers franta-hg@76: franta-hg@76: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@28: franta-hg@28: franta-hg@28: computer franta-hg@28: franta-hg@28: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: java franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: xml franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: xml franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@37: protocol franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@11: franta-hg@37: security franta-hg@37: protocol franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: security franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@53: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@61: franta-hg@61: franta-hg@61: franta-hg@61: a domain name like „some-machine.example.com“ which completely specifies the location in the DNS hierarchy including the TLD; franta-hg@61: compared to „some-machine“ which is not FQDN – is not globally unambiguous and will be resolved differently in different contexts franta-hg@61: franta-hg@61: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@60: franta-hg@60: franta-hg@60: a data communication protocol, a sublayer of the layer 2 in OSI model (data link layer); franta-hg@60: a MAC address is a unique identifier of an network interface – used for IEEE 802 networks including Ethernet; franta-hg@60: they are assigned by the manufacturer of the card and stored in the hardware (can be often changed by the software); franta-hg@60: there are three numbering namespaces: MAC-48, EUI-48 and EUI-64; franta-hg@60: the address has 6 or 8 bytes and they are usually written in HEX, octets separated by : (a colon) franta-hg@60: franta-hg@60: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@15: franta-hg@59: franta-hg@59: franta-hg@59: a set of rules that should avoid excessive usage of a service by one user to the detriment of other user's comfort; franta-hg@59: 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“ franta-hg@59: franta-hg@59: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@58: franta-hg@58: franta-hg@58: specifies interaction between software components; franta-hg@58: adds an abstraction layer which divides calling code and called code franta-hg@58: and enables multiple implementations of such API (or SPI) like multiple databases (database drivers), file systems, remote services etc. franta-hg@58: examples of API: POSIX, OpenGL, JDBC, JMS or JMX franta-hg@58: franta-hg@58: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@58: franta-hg@58: franta-hg@58: a kind of API to be implemented by third party; franta-hg@58: can be installed as plugin/addon/extension and used by the application over standard interface; franta-hg@58: examples of SPI: JDBC, JNDI or JAXP franta-hg@58: franta-hg@58: franta-hg@9: computer franta-hg@58: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@51: franta-hg@52: franta-hg@52: franta-hg@51: a Java technology for monitoring and managing applications or devices; franta-hg@51: similar to SNMP; franta-hg@51: managed objects (MBeans) can emit events, can be asked for values (e.g. counters) or an action (method) can be called on them; franta-hg@51: this native Java technology can be also adapted/translated to other protocols like SNMP or WS/SOAP and integrated with the non-Java world; franta-hg@51: 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) franta-hg@52: franta-hg@52: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@51: franta-hg@52: franta-hg@53: a Java API for message-oriented middleware (MOM); franta-hg@52: allows JEE components to create, send, receive and read messages; franta-hg@52: supports both point-to-point and publish-subscribe messaging models; franta-hg@53: can be adapted/translated to many other protocols like SMTP, AMQP, XMPP or SOAP; franta-hg@52: is defined in JSR 914; franta-hg@52: examples of JMS implementations: Apache ActiveMQ, OpenJMS, HornetQ franta-hg@52: franta-hg@51: franta-hg@9: computer franta-hg@10: java franta-hg@27: messaging franta-hg@0: franta-hg@0: franta-hg@52: franta-hg@52: franta-hg@52: franta-hg@52: a software (or even hardware) infrastructure for sending and receiving messages; franta-hg@52: can also offer routing and transformation features; franta-hg@52: for Java the MOM API is standardized as JMS franta-hg@52: franta-hg@52: franta-hg@52: computer franta-hg@52: messaging franta-hg@52: franta-hg@52: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: an open and standard binary protocol for message-oriented middleware (MOM); franta-hg@53: is vendor and platform independent; franta-hg@53: whereas JMS defines programming API and is Java specific, the AMQP defines the wire-level protocol; franta-hg@53: 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; franta-hg@53: example of implementation: Apache ActiveMQ franta-hg@53: franta-hg@53: franta-hg@53: computer franta-hg@53: messaging franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: franta-hg@53: the format of data sent over the network as stream of bytes; franta-hg@53: an application layer protocol franta-hg@53: franta-hg@53: franta-hg@53: computer franta-hg@53: franta-hg@53: franta-hg@12: franta-hg@54: franta-hg@54: franta-hg@54: a Java EE technology for connecting application servers (AS) and enterprise information systems (EIS); franta-hg@54: is similar to JDBC (which is used for connecting to databases) but is much more generic franta-hg@54: and allows connecting any (often legacy) system using a specific connector franta-hg@54: franta-hg@54: franta-hg@54: computer franta-hg@54: java franta-hg@54: franta-hg@54: franta-hg@54: franta-hg@55: franta-hg@55: franta-hg@55: an enterprise-class software system; franta-hg@55: typically high quality and critical service, large volumes of data, robust, supporting business processes franta-hg@55: franta-hg@55: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@52: franta-hg@56: franta-hg@56: franta-hg@56: a framework and module system for Java; franta-hg@56: allows applications with modular architecture composed from components franta-hg@56: that can be loaded, started, stopped, updated or uninstalled without restarting the JVM and the application; franta-hg@56: examples of OSGi implementations: Apache Felix, Equinox and Knopflerfish franta-hg@56: franta-hg@56: franta-hg@52: computer franta-hg@52: java franta-hg@52: franta-hg@52: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a request for changing a software – new features or modification of existing ones; franta-hg@30: when one or more CRs are developed, they are delivered as new version of software product; franta-hg@30: CR is requested by the customer (mobile network operator) and is delivered by the development team; franta-hg@30: CR consists of one or more DT which are assigned to particular developers franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a task assigned to a software developer; franta-hg@30: one or more DTs together usually forms a CR; franta-hg@30: 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); franta-hg@30: each commit in the versioning system should be linked to a DT franta-hg@30: franta-hg@30: franta-hg@30: computer franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: franta-hg@30: a request for fixing something in the production; franta-hg@30: requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development) franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: requirements on a software product or its particular change; franta-hg@30: is written from the system's point of view franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@30: franta-hg@30: franta-hg@30: requirements on a software product or its particular change; franta-hg@30: is written from the user's point of view franta-hg@30: franta-hg@30: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@11: franta-hg@30: franta-hg@30: franta-hg@30: a build of a software product which was not done according to regular procedure and processes; franta-hg@30: might be used only for testing on site or during development – not in production; franta-hg@30: 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 franta-hg@30: franta-hg@30: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: java franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@10: security franta-hg@27: messaging franta-hg@37: protocol franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@12: franta-hg@12: computer franta-hg@12: franta-hg@12: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@9: general franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: computer franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@9: acision franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@0: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@113: franta-hg@113: franta-hg@113: the FXO interface is typically the plug on the phone (or modem) franta-hg@113: which receives the POTS service; franta-hg@113: should be connected to an FXS interface (not to another FXO interface) franta-hg@113: franta-hg@113: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@113: franta-hg@113: franta-hg@113: the FXS interface is typically the plug on the wall franta-hg@113: which delivers the POTS service from telephone company to the subscriber; franta-hg@115: this interface franta-hg@115: supplies battery power, franta-hg@115: ringing voltage franta-hg@115: and dial tone; franta-hg@113: should be connected to an FXO interface (not to another FXS interface) franta-hg@113: franta-hg@113: franta-hg@0: franta-hg@0: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: a kind of telephone exchange used in some office or company for its own purposes; franta-hg@114: provides FSX interface for connected phones; franta-hg@114: can have FXO interface for connecting to PTSN (for calling outside the company); franta-hg@114: nowadays are often deployed digital VoIP PBXes based on free software like Asterisk; franta-hg@114: such telephony can be pure IP based with no POTS or can have some FSX or FXO interfaces franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: the worldwide public telephony network consisting of networks of particular carriers; franta-hg@114: the network is developed according to ITU-T standards and recommendations franta-hg@114: and uses uniform system of telephone numbers based on ITU-T recommendation E.164 franta-hg@114: which provides a single global address space for telephone numbers franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@114: franta-hg@12: franta-hg@112: franta-hg@112: franta-hg@112: traditional wired telephony based on analog signals franta-hg@112: (contrary to ISDN which is digital) franta-hg@112: franta-hg@112: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@116: franta-hg@116: franta-hg@116: franta-hg@116: franta-hg@116: franta-hg@116: franta-hg@116: a service that delivers caller's phone number to the called party's device during ringing; franta-hg@116: so the called party knows who is calling before answering the phone; franta-hg@116: this service is common in digital networks like VoIP, GSM or ISDN but can be provided also on analog POTS networks franta-hg@116: franta-hg@116: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@0: franta-hg@12: franta-hg@4: franta-hg@0: franta-hg@7: franta-hg@22: franta-hg@22: delivering better product faster with smaller teams of less-experienced engineers franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@112: a company which is not going to bankrupt franta-hg@22: franta-hg@22: franta-hg@22: franta-hg@12: franta-hg@11: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@11: franta-hg@11: computer franta-hg@11: franta-hg@11: franta-hg@12: franta-hg@12: franta-hg@11: Something that should or will be done later. Used as comments in draft version of documents or in software source code. franta-hg@11: franta-hg@11: franta-hg@7: franta-hg@7: and so forth, and the rest franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: for instance, for example franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: in other words, that is franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: among other things franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: note well, note franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: percent, for each one hundred franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: annually franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: approximately franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: a document summarizing your relevant job experience and education franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: and others, and co-workers franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: after what has been written; used at the end of the letters/messages for additions franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: which was to be demonstrated franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: rest in peace franta-hg@8: general franta-hg@7: franta-hg@7: franta-hg@7: franta-hg@7: against franta-hg@8: general franta-hg@7: franta-hg@0: