Global Worldwide Office in Orlando Florida - US. Branch Office in Anaheim California - US.
Rabu, 23 Juli 2008
MM7
MM7 is used to transfer MMS from MMSC (Multimedia Messaging Service Center) to MMS VAS applications and to transfer MMS from MMS VAS applications to MMSC. It is based on SOAP messages with attachments using an HTTP transport layer.
Glosary Telco
WAP 1.2 G/W(Wireless Application Protocol 1.2 G/W) WAP-HTTP 프로토콜 변환 게이트웨이
WAP 2.0 G/W(Wireless Application Protocol 2.0 G/W) xHTML Basic을 지원하는 게이트웨이
PMS(Portal Management System) 유무선 인터넷 포탈관리 시스템
CMS(Contents Management System) 모바일 Contents 관리 시스템
MDS(Multimedia Download Server) 멀티미디어 Contents 다운로드 서버
MOG(Mobile Office Gateway) 모바일 그룹웨어 서비스
MZS(Mobile Zone System) 지역기반 맞춤형 무선인터넷 서비스
SCP(Service Control Point) 지능망 서비스 제어 시스템
IP(Intelligent Peripheral) 특수자원 관리 시스템
SMP(Service Management Point) 지능망 서비스 관리 시스템
SCE(Service Creation Environment) 지능망 서비스 생성 환경
OSA/Parlay G/W(Open Service Access Parlay Gateway) 개방형 망 자원 연동 시스템
SMSC(Short Message Service Center) 문자 메시지 전송 시스템
CBSC(Cell Broadcast Service Center) 동일지역 단말에 대한 데이터 전송 시스템
GMLC(Gateway Mobile Location Center) IMT-2000용 단말 위치정보 제공 시스템
MPC(Mobile Positioning Center) 2G용 단말 위치정보 제공 시스템
PPS(Pre-paid Service) 선불카드 서비스
VPN(Virtual Private Network) 가상 사설 망 서비스
CDMA(Code Division Multiple Access) 코드분할 다중 접속방식, 2세대 북미 이동통신 방식
GSM(Global Standard for Mobile Telecommunication) 2세대 유럽형 이동전화 방식
IMT-2000 = 3G (International Mobile Telecommunications-2000) 차세대 이동통신 시스템
MSC(Mobile Switching Center) 교환기
HLR(Home Location Registry) 가입자 위치 등록기
IWF(Inter Working Function) 망 연동 장치
WIN (Wireless Intelligent Network standard) 북미 무선 지능 망 규격
CAP(CAMEL Application Protocol) 유럽형 무선 지능 망 규격
SGSN(Serving GPRS Support Node) Packet 데이터 교환장치
GGSN(Gateway GPRS Support Node) Packet 데이터 관문장치
MAP(Mobile Application Protocol) Mobile 응용 프로토콜
RBT(Ring Back Tone) 특성화된 통화 연결음 제공 서비스
WAP 2.0 G/W(Wireless Application Protocol 2.0 G/W) xHTML Basic을 지원하는 게이트웨이
PMS(Portal Management System) 유무선 인터넷 포탈관리 시스템
CMS(Contents Management System) 모바일 Contents 관리 시스템
MDS(Multimedia Download Server) 멀티미디어 Contents 다운로드 서버
MOG(Mobile Office Gateway) 모바일 그룹웨어 서비스
MZS(Mobile Zone System) 지역기반 맞춤형 무선인터넷 서비스
SCP(Service Control Point) 지능망 서비스 제어 시스템
IP(Intelligent Peripheral) 특수자원 관리 시스템
SMP(Service Management Point) 지능망 서비스 관리 시스템
SCE(Service Creation Environment) 지능망 서비스 생성 환경
OSA/Parlay G/W(Open Service Access Parlay Gateway) 개방형 망 자원 연동 시스템
SMSC(Short Message Service Center) 문자 메시지 전송 시스템
CBSC(Cell Broadcast Service Center) 동일지역 단말에 대한 데이터 전송 시스템
GMLC(Gateway Mobile Location Center) IMT-2000용 단말 위치정보 제공 시스템
MPC(Mobile Positioning Center) 2G용 단말 위치정보 제공 시스템
PPS(Pre-paid Service) 선불카드 서비스
VPN(Virtual Private Network) 가상 사설 망 서비스
CDMA(Code Division Multiple Access) 코드분할 다중 접속방식, 2세대 북미 이동통신 방식
GSM(Global Standard for Mobile Telecommunication) 2세대 유럽형 이동전화 방식
IMT-2000 = 3G (International Mobile Telecommunications-2000) 차세대 이동통신 시스템
MSC(Mobile Switching Center) 교환기
HLR(Home Location Registry) 가입자 위치 등록기
IWF(Inter Working Function) 망 연동 장치
WIN (Wireless Intelligent Network standard) 북미 무선 지능 망 규격
CAP(CAMEL Application Protocol) 유럽형 무선 지능 망 규격
SGSN(Serving GPRS Support Node) Packet 데이터 교환장치
GGSN(Gateway GPRS Support Node) Packet 데이터 관문장치
MAP(Mobile Application Protocol) Mobile 응용 프로토콜
RBT(Ring Back Tone) 특성화된 통화 연결음 제공 서비스
CMS
Content management system
From Wikipedia, the free encyclopedia
A content management system (CMS) is computer software used to create, edit, manage, and publish content in a consistently organized fashion.[1] CMSs are frequently used for storing, controlling, versioning, and publishing industry-specific documentation such as news articles, operators' manuals, technical manuals, sales guides, and marketing brochures. CMS tools have the ability to efficiently publish all forms of content to their respective online locations without involving technical resources. CMS is becoming increasingly relevant to both large and small businesses as content continues to grow exponentially and search engines struggle to spider that content online. [2] The content managed may include computer files, image media, audio files, electronic documents, and Web content.
A CMS may support the following features:
identification of all key users and their content management roles;
the ability to assign roles and responsibilities to different content categories or types;
definition of workflow tasks for collaborative creation, often coupled with event messaging so that content managers are alerted to changes in content (For example, a content creator submits a story, which is published only after the copy editor revises it and the editor-in-chief approves it.);
the ability to track and manage multiple versions of a single instance of content;
the ability to publish the content to a repository to support access to the content (Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval.);
separation of content's semantic layer from its layout (For example, the CMS may automatically set the color, fonts, or emphasis of text.).
From Wikipedia, the free encyclopedia
A content management system (CMS) is computer software used to create, edit, manage, and publish content in a consistently organized fashion.[1] CMSs are frequently used for storing, controlling, versioning, and publishing industry-specific documentation such as news articles, operators' manuals, technical manuals, sales guides, and marketing brochures. CMS tools have the ability to efficiently publish all forms of content to their respective online locations without involving technical resources. CMS is becoming increasingly relevant to both large and small businesses as content continues to grow exponentially and search engines struggle to spider that content online. [2] The content managed may include computer files, image media, audio files, electronic documents, and Web content.
A CMS may support the following features:
identification of all key users and their content management roles;
the ability to assign roles and responsibilities to different content categories or types;
definition of workflow tasks for collaborative creation, often coupled with event messaging so that content managers are alerted to changes in content (For example, a content creator submits a story, which is published only after the copy editor revises it and the editor-in-chief approves it.);
the ability to track and manage multiple versions of a single instance of content;
the ability to publish the content to a repository to support access to the content (Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval.);
separation of content's semantic layer from its layout (For example, the CMS may automatically set the color, fonts, or emphasis of text.).
Short message peer-to-peer protocol (SMPP)
Short message peer-to-peer protocol
From Wikipedia, the free encyclopedia
The short message peer-to-peer protocol (SMPP) is a telecommunications industry protocol for exchanging SMS messages between SMS peer entities such as short message service centres. It is often used to allow third parties (e.g. value-added service providers like news organisations) to submit messages, often in bulk.
SMPP was originally designed by Aldiscon, a small Irish company that was later acquired by Logica (now split off and known as Acision). In 1999, LogicaCMG formally handed over SMPP to the SMPP Developers Forum, later renamed as The SMS Forum and now disbanded. The SMPP protocol specifications are still available through the website which also carries a notice stating that it will be taken down at the end of 2007.
The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer 4 (TCP session or X.25 SVC3) connections. PDUs are binary encoded for efficiency.
The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which adds transceiver support (single connections that can send and receive messages). Data exchange may be synchronous, where each peer must wait for a response for each PDU being sent, and asynchronous, where multiple requests can be issued in one go and acknowledged in a skew order by the other peer. The latest version of SMPP is v5.0.
From Wikipedia, the free encyclopedia
The short message peer-to-peer protocol (SMPP) is a telecommunications industry protocol for exchanging SMS messages between SMS peer entities such as short message service centres. It is often used to allow third parties (e.g. value-added service providers like news organisations) to submit messages, often in bulk.
SMPP was originally designed by Aldiscon, a small Irish company that was later acquired by Logica (now split off and known as Acision). In 1999, LogicaCMG formally handed over SMPP to the SMPP Developers Forum, later renamed as The SMS Forum and now disbanded. The SMPP protocol specifications are still available through the website which also carries a notice stating that it will be taken down at the end of 2007.
The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer 4 (TCP session or X.25 SVC3) connections. PDUs are binary encoded for efficiency.
The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which adds transceiver support (single connections that can send and receive messages). Data exchange may be synchronous, where each peer must wait for a response for each PDU being sent, and asynchronous, where multiple requests can be issued in one go and acknowledged in a skew order by the other peer. The latest version of SMPP is v5.0.
Interactive voice response
Interactive voice response
From Wikipedia, the free encyclopedia
In telephony, interactive voice response, or IVR, is a phone technology that allows a computer to detect voice and touch tones using a normal phone call. The IVR system can respond with pre-recorded or dynamically generated audio to further direct callers on how to proceed. IVR systems can be used to control almost any function where the interface can be broken down into a series of simple menu choices. Once constructed IVR systems generally scale well to handle large call volumes.
Contents[hide]
1 Example usage
2 Typical uses
2.1 Voice Activated Diallers
2.2 Entertainment and information
2.3 Anonymous Access
2.4 Clinical Trials
3 Technologies used
4 Criticism
5 See also
6 References
7 External links
[edit] Example usage
A caller dials a telephone number that is answered by an IVR system. The IVR system executes an application which is tied to the number dialed DNIS (Dialed Number Identification Service). As part of the application, prerecorded audio files or dynamically generated Text to Speech (TTS) audio explain the options available to the caller. The caller is given the choice to select options using DTMF tones or spoken words. Speech recognition is normally used to carry out more complex transactions and simplifies the application menu structure.
[edit] Typical uses
IVR systems are typically used to service high call volumes, reduce cost and improve the customer experience. Examples of typical IVR applications are: telephone banking, televoting, and credit card transactions. Large companies use IVR services to extend the business hours of operation.
Call centers use IVR systems to identify and segment callers. The ability to identify customers allows the ability to tailor services according to the customer profile. It also allows the option of choosing automated services. Information can be fed to the caller allowing choices such as: wait in the queue, choose an automated service, or request a callback. (At a suitable time and telephone number) The use of CTI(Computer Telephone Integration) will allow the IVR system to look up the CLI (Calling Line ID) on a network database and identify the caller. This is currently accurate for about 80% of inbound calls. In the cases where CLI is withheld or unavailable, the caller can be asked to identify themselves by other methods such as a PIN or password. The use of DNIS will ensure that the correct application and language is executed by the IVR system.
From Wikipedia, the free encyclopedia
In telephony, interactive voice response, or IVR, is a phone technology that allows a computer to detect voice and touch tones using a normal phone call. The IVR system can respond with pre-recorded or dynamically generated audio to further direct callers on how to proceed. IVR systems can be used to control almost any function where the interface can be broken down into a series of simple menu choices. Once constructed IVR systems generally scale well to handle large call volumes.
Contents[hide]
1 Example usage
2 Typical uses
2.1 Voice Activated Diallers
2.2 Entertainment and information
2.3 Anonymous Access
2.4 Clinical Trials
3 Technologies used
4 Criticism
5 See also
6 References
7 External links
[edit] Example usage
A caller dials a telephone number that is answered by an IVR system. The IVR system executes an application which is tied to the number dialed DNIS (Dialed Number Identification Service). As part of the application, prerecorded audio files or dynamically generated Text to Speech (TTS) audio explain the options available to the caller. The caller is given the choice to select options using DTMF tones or spoken words. Speech recognition is normally used to carry out more complex transactions and simplifies the application menu structure.
[edit] Typical uses
IVR systems are typically used to service high call volumes, reduce cost and improve the customer experience. Examples of typical IVR applications are: telephone banking, televoting, and credit card transactions. Large companies use IVR services to extend the business hours of operation.
Call centers use IVR systems to identify and segment callers. The ability to identify customers allows the ability to tailor services according to the customer profile. It also allows the option of choosing automated services. Information can be fed to the caller allowing choices such as: wait in the queue, choose an automated service, or request a callback. (At a suitable time and telephone number) The use of CTI(Computer Telephone Integration) will allow the IVR system to look up the CLI (Calling Line ID) on a network database and identify the caller. This is currently accurate for about 80% of inbound calls. In the cases where CLI is withheld or unavailable, the caller can be asked to identify themselves by other methods such as a PIN or password. The use of DNIS will ensure that the correct application and language is executed by the IVR system.
Selasa, 15 Juli 2008
Provisioning
Provisioning
From Wikipedia, the free encyclopedia
For other uses, see Provisioning (disambiguation).
In voice telecommunication, provisioning means to provide telecommunications services to a user or customer, including transmission, wiring, and equipment. In NS/EP telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability. Source: US Federal Standard 1037C
In a modern signal infrastructure employing information technology at all levels, there is no distinction possible between telecommunications services and "higher level" infrastructure. Accordingly provisioning configures any required systems, provides users with access to data and technology resources, and refers to all enterprise-level information resource management involved.
From a management perspective, it is typically managed by a CIO, and necessarily involves human resources and IT departments cooperating to:
give users access to data repositories or grant authorization to systems, networks applications and databases based on a unique user identity, and
appropriate for their use hardware resources, such as computers, mobile phones and pagers.
As its most central responsibility, the provisioning process monitors access rights and privileges to ensure the security of an enterprise's resources and user privacy. As a secondary responsibility, it ensures compliance and minimizes the vulnerability of systems to penetration and abuse. As a tertiary responsibliity, it tries to reduce the amount of custom configuration using boot image control and other methods that radically reduce the number of different configurations involved.
"Provisioning" often appears in the context of virtualization, orchestration, utility computing and open configuration concepts and projects. For instance, the OASIS Provisioning Services Technical Committee (PSTC) defines an XML-based framework for exchanging user, resource, and service provisioning information, e.g. SPML (Service Provisioning Markup Language) for "managing the provisioning and allocation of identity information and system resources within and between organizations".
Once provisioned, the process of SysOpping ensures that services are maintained to the expected standards. Provisioning thus refers only to the setup or startup part of the service operation, and SysOpping to the ongoing responsibility.
Contents[hide]
1 Server provisioning
2 User provisioning
3 Mobile subscriber provisioning
4 Mobile content provisioning
5 External links
//
[edit] Server provisioning
Selecting a server from a pool of available servers; loading the appropriate software (operating system, device drivers, middleware, and applications); appropriately customizing and configuring the system, software to create or change a boot image for this server, and change its parameters, e.g. IP address, IP gateway, to find associated network and storage resources - sometimes separated as resource provisioning - audit the system, i.e. ensuring OVAL compliance to limit vulnerability or ensure compliance or install patches, then finally starting the server and its newly-loaded software. This makes the system ready for operation. Typically an internet service provider (ISP) or Network Operations Center will perform these tasks to a well-defined set of parameters, e.g. a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a virtual dedicated host.
There are many software products available to automate the provisioning of servers, from vendors such as BladeLogic, Cassatt, IBM Tivoli IBM Tivoli, HP and OpenQRM.
In short, server provisioning is defining server configuration based on organizational requirements. A hardware/software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) will depend purely on utilizations like ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.
Service used by most larger scale centers in part to avoid this. Additional resource provisioning may be done per service.
[edit] User provisioning
User provisioning refers to the creation, maintenance and deactivation of user objects and user attributes, as they exist in one or more systems, directories or applications, in response to automated or interactive business processes. User provisioning software may include one or more of the following processes: change propagation, self service workflow, consolidated user administration, delegated user administration, and federated change control. User objects may represent employees, contractors, vendors, partners, customers or other recipients of a service. Services may include electronic mail, inclusion in a published user directory, access to a database, access to a network or mainframe, etc. User provisioning is a type of identity management software, particularly useful within organizations, where users may be represented by multiple objects on multiple systems.
[edit] Mobile subscriber provisioning
This refers to the setting up of new services, such as GPRS, MMS and Instant Messaging for an existing subscriber of a mobile phone network, and any gateways to standard Internet chat or mail services. The network operator typically sends these settings to the subscriber's handset using SMS or WAP as mobile operating systems accept.
From Wikipedia, the free encyclopedia
For other uses, see Provisioning (disambiguation).
In voice telecommunication, provisioning means to provide telecommunications services to a user or customer, including transmission, wiring, and equipment. In NS/EP telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability. Source: US Federal Standard 1037C
In a modern signal infrastructure employing information technology at all levels, there is no distinction possible between telecommunications services and "higher level" infrastructure. Accordingly provisioning configures any required systems, provides users with access to data and technology resources, and refers to all enterprise-level information resource management involved.
From a management perspective, it is typically managed by a CIO, and necessarily involves human resources and IT departments cooperating to:
give users access to data repositories or grant authorization to systems, networks applications and databases based on a unique user identity, and
appropriate for their use hardware resources, such as computers, mobile phones and pagers.
As its most central responsibility, the provisioning process monitors access rights and privileges to ensure the security of an enterprise's resources and user privacy. As a secondary responsibility, it ensures compliance and minimizes the vulnerability of systems to penetration and abuse. As a tertiary responsibliity, it tries to reduce the amount of custom configuration using boot image control and other methods that radically reduce the number of different configurations involved.
"Provisioning" often appears in the context of virtualization, orchestration, utility computing and open configuration concepts and projects. For instance, the OASIS Provisioning Services Technical Committee (PSTC) defines an XML-based framework for exchanging user, resource, and service provisioning information, e.g. SPML (Service Provisioning Markup Language) for "managing the provisioning and allocation of identity information and system resources within and between organizations".
Once provisioned, the process of SysOpping ensures that services are maintained to the expected standards. Provisioning thus refers only to the setup or startup part of the service operation, and SysOpping to the ongoing responsibility.
Contents[hide]
1 Server provisioning
2 User provisioning
3 Mobile subscriber provisioning
4 Mobile content provisioning
5 External links
//
[edit] Server provisioning
Selecting a server from a pool of available servers; loading the appropriate software (operating system, device drivers, middleware, and applications); appropriately customizing and configuring the system, software to create or change a boot image for this server, and change its parameters, e.g. IP address, IP gateway, to find associated network and storage resources - sometimes separated as resource provisioning - audit the system, i.e. ensuring OVAL compliance to limit vulnerability or ensure compliance or install patches, then finally starting the server and its newly-loaded software. This makes the system ready for operation. Typically an internet service provider (ISP) or Network Operations Center will perform these tasks to a well-defined set of parameters, e.g. a boot image that the organization has approved and which uses software it has license to. Many instances of such a boot image create a virtual dedicated host.
There are many software products available to automate the provisioning of servers, from vendors such as BladeLogic, Cassatt, IBM Tivoli IBM Tivoli, HP and OpenQRM.
In short, server provisioning is defining server configuration based on organizational requirements. A hardware/software component (e.g. single/dual processor, RAM, HDD, RAID controller, a number of LAN cards, applications, OS, etc.) will depend purely on utilizations like ISP, virtualization, NOS, or voice processing. Server redundancy depends on the availability of servers in the organization. Critical applications have less downtime when using cluster servers, RAID, or a mirroring system.
Service used by most larger scale centers in part to avoid this. Additional resource provisioning may be done per service.
[edit] User provisioning
User provisioning refers to the creation, maintenance and deactivation of user objects and user attributes, as they exist in one or more systems, directories or applications, in response to automated or interactive business processes. User provisioning software may include one or more of the following processes: change propagation, self service workflow, consolidated user administration, delegated user administration, and federated change control. User objects may represent employees, contractors, vendors, partners, customers or other recipients of a service. Services may include electronic mail, inclusion in a published user directory, access to a database, access to a network or mainframe, etc. User provisioning is a type of identity management software, particularly useful within organizations, where users may be represented by multiple objects on multiple systems.
[edit] Mobile subscriber provisioning
This refers to the setting up of new services, such as GPRS, MMS and Instant Messaging for an existing subscriber of a mobile phone network, and any gateways to standard Internet chat or mail services. The network operator typically sends these settings to the subscriber's handset using SMS or WAP as mobile operating systems accept.
Customer Care and Billing Provider in China
Amdocs Completes Acquisition of Longshine, A Leading Customer Care and Billing Provider in China
August 4, 2005, St. Louis, Missouri - Amdocs (NYSE: DOX), the leading provider of software and services to enable integrated customer management and the intentional customer experience, announced today the completion of the acquisition of Longshine Information Technology Company Ltd., a privately-held, leading vendor of customer care and billing software in China. Amdocs acquired Longshine’s outstanding shares for approximately US $30 million in cash with the possibility of additional cash consideration to be paid later based on the achievement of certain performance metrics. This acquisition expands Amdocs’ global presence and marks its entry into mainland China.“We are pleased with this acquisition and what the combination means for Amdocs. The fast growing China market represents a tremendous potential opportunity,” said Eli Gelman, executive vice president of Amdocs Management Limited. “Amdocs combined offering will enable service providers in China to effectively deal with the rapidly evolving market needs, increasing competition and the associated growing complexity.” The former Longshine will operate as a business unit in China within Amdocs and will be led by the founder and CEO, Mr. Zhangjun XU. Amdocs intends to continue to sell Longshine’s software products and services in China. In parallel, Amdocs will continue offering the Amdocs 6 portfolio of products and accompanying services to the Chinese market. Longshine has been providing billing, customer care, business intelligence and settlement systems, as well as associated integration and implementation services, since 1996, with a primary focus on the telecommunications sector in China, in addition to the utility industry. Today, it counts three out of China’s four largest communications service providers and two power grid companies among its customers. Headquartered in Beijing, Longshine is present in more than 15 provinces across China and serves more than 120 million subscribers. It has been successful in attracting skilled professionals experienced in the delivery of customer care and billing systems, and has close to 800 employees.About AmdocsAmdocs combines innovative software and services with deep business knowledge to accelerate implementation of an integrated customer management strategy by the world’s leading service providers. By delivering a comprehensive portfolio of software and services that spans the customer lifecycle – target, sell, deliver, bill and support – Amdocs enables service companies to deliver an intentional customer experience, which results in stronger, more profitable customer relationships. Service providers also benefit from a rapid return on investment, lower total cost of ownership and improved operational efficiencies. A global company with the revenue of approximately $1.8 billion in fiscal 2004, Amdocs employs over 10,000 IT professionals and serves customers in 40 countries around the world. For more information, visit Amdocs at www.amdocs.com.
August 4, 2005, St. Louis, Missouri - Amdocs (NYSE: DOX), the leading provider of software and services to enable integrated customer management and the intentional customer experience, announced today the completion of the acquisition of Longshine Information Technology Company Ltd., a privately-held, leading vendor of customer care and billing software in China. Amdocs acquired Longshine’s outstanding shares for approximately US $30 million in cash with the possibility of additional cash consideration to be paid later based on the achievement of certain performance metrics. This acquisition expands Amdocs’ global presence and marks its entry into mainland China.“We are pleased with this acquisition and what the combination means for Amdocs. The fast growing China market represents a tremendous potential opportunity,” said Eli Gelman, executive vice president of Amdocs Management Limited. “Amdocs combined offering will enable service providers in China to effectively deal with the rapidly evolving market needs, increasing competition and the associated growing complexity.” The former Longshine will operate as a business unit in China within Amdocs and will be led by the founder and CEO, Mr. Zhangjun XU. Amdocs intends to continue to sell Longshine’s software products and services in China. In parallel, Amdocs will continue offering the Amdocs 6 portfolio of products and accompanying services to the Chinese market. Longshine has been providing billing, customer care, business intelligence and settlement systems, as well as associated integration and implementation services, since 1996, with a primary focus on the telecommunications sector in China, in addition to the utility industry. Today, it counts three out of China’s four largest communications service providers and two power grid companies among its customers. Headquartered in Beijing, Longshine is present in more than 15 provinces across China and serves more than 120 million subscribers. It has been successful in attracting skilled professionals experienced in the delivery of customer care and billing systems, and has close to 800 employees.About AmdocsAmdocs combines innovative software and services with deep business knowledge to accelerate implementation of an integrated customer management strategy by the world’s leading service providers. By delivering a comprehensive portfolio of software and services that spans the customer lifecycle – target, sell, deliver, bill and support – Amdocs enables service companies to deliver an intentional customer experience, which results in stronger, more profitable customer relationships. Service providers also benefit from a rapid return on investment, lower total cost of ownership and improved operational efficiencies. A global company with the revenue of approximately $1.8 billion in fiscal 2004, Amdocs employs over 10,000 IT professionals and serves customers in 40 countries around the world. For more information, visit Amdocs at www.amdocs.com.
Convergent Charging Solution at Telkomsel
Siemens and Convergys Implement Convergent Charging Solution at Telkomsel
September 27, 2005, Cincinnati, Ohio - Indonesia's premier cellular and wireless network operator Telkomsel has gone live with the first phase of Siemens' (NYSE: SI) market-leading, real-time, convergent charging solution, charge@once, that features Infinys [tm] Rating software from Convergys Corporation (NYSE: CVG). Telkomsel obtained the advanced solution to deliver the first-ever, truly convergent pre- and post-paid rating and billing of individual customer segments regardless of payment options. The solution currently supports more than 21 million subscribers.With the initial implementation by Siemens and Convergys now completed, Telkomsel is using the convergent charging solution to support its geographically complex business that spans over 13,000 islands. The solution satisfied Telkomsel's rigorous IT, engineering, and network requirements. It is now supporting an operation that has more than 54 percent of the mobile market in Indonesia and provides network coverage to more than 90 percent of the country's population, including corporate and private customers.The architecturally advanced solution, featuring Infinys as the embedded rater on Siemens' Charging, enables Telkomsel to explore the full range of convergent pre- and post-paid capabilities. These include real-time checking of credit limits, flexible charge and packages adjustment, as well as the use of bonus schemes and hybrid offers that help enhance customer loyalty and average revenue per user across all subscribers and service types."The success of this project reaffirms our decision to partner with Siemens and Convergys," said Arman Hazairin, Vice President Information and Technology Telkomsel. "We operate in an increasingly competitive market, so it is imperative that we can innovate around products and differentiate our offerings from those of competitors. The charge@once solution enables this, supports our drive to become even more customer-focused, and provides a platform for developing new revenue streams and achieving long-term growth.""Completing the first phase of the implementation, supporting the complete customer base with a comprehensive real-time solution, and providing maximum charging flexibility at Telkomsel are major milestones for the Siemens convergent charging system, charge@once, featuring online rating from Infinys," said Volker Ziegler, President of Applications and Solutions at Siemens COM. "Together with Convergys, we are demonstrating the real-world viability of our solution in a market where similar projects involving other suppliers have not yet been successful. Upon completion, the OPEX-effective solution will place Telkomsel in a unique position, enabling it to respond more quickly to changing market conditions, alter prices, and create discounts or promotions with an ease and alacrity hitherto unattainable.""Telkomsel is already seeing the benefits of a solution that effectively joins the high availability and scalability needed to support a tier-one operation with the real-time functionality and flexibility required to drive a customer-focused business," said Dave Dougherty, President and Chief Operating Officer of Convergys. "This project showcases both the capabilities of the world's first truly commercially operational online charging solution and the benefits of the close working relationship between Convergys and Siemens."Operators' needs for convergent online charging systems are increasing alongside the ever-expanding range of new multimedia data services for the online environment. The ability to handle both pre-paid and post-paid transactions in real time is critical if customers and providers are to quickly check usage limits and status of account balances in real time. This capability, provided by the Siemens and Convergys solution, allows customers to make informed decisions about their usage and expenditures while enabling operators to better manage their risk of revenue exposure. The solution also permits operators to constantly expand the existing charging structures and map new business and billing models in the charging system, which were once restricted to the post-paid offline environment.About TelkomselTelkomsel is the leading operator of cellular telecommunications services in Indonesia by market share. By the end of June 2005, Telkomsel had more than 21 million customers, which represented of around 54 percent market share in the telecommunication industry. Telkomsel provides GSM cellular services in Indonesia, through its own nationwide dual band 900/1800 MHz GSM network, and internationally, has 219 roaming operator partners in 135 countries (June 2005). Telkomsel's operations in Indonesia have grown substantially since the commercial launch of its post-paid services on 26 May 1995. In November 1997, Telkomsel became the first cellular telecommunications operator in Asia to introduce rechargeable GSM pre-paid services, a solution with Siemens. Telkomsel has the largest network coverage of any of the cellular operators in Indonesia, providing network coverage to over 90% of Indonesia's population and is the only operator in Indonesia that covers all of the country's provinces, cities, and regencies ("kabupaten"). The company currently offers GSM Dual Band (900 & 1800), GPRS, Wi-Fi, and EDGE Technology and has a successful 3G trial. For more information, see www.telkomsel.comAbout Siemens CommunicationsSiemens Communications is one of the largest players in the global telecommunications industry. Siemens is the only provider in the market hat offers its customers a full-range portfolio, from end-user equipment to complex network infrastructures for enterprises and carriers as well as related services. Siemens Communications is the world's innovation leader in convergent technologies, products and services for wireless, fixed and enterprise networks. It is the largest Group within Siemens and operates in more than 160 countries around the world. In fiscal 2004 (year-end September 30), its 60,000-strong workforce posted sales of approximately 18 billion Euros. For more information, see http://www.siemens.com/communicationsAbout ConvergysConvergys Corporation (NYSE: CVG) is a global leader in providing customer care, human resources, and billing services. Convergys combines specialized knowledge and expertise with solid execution to deliver outsourced solutions, consulting services, and software support. Clients in more than 60 countries speaking nearly 30 languages depend on Convergys to manage the increasing complexity and cost of caring for customers and employees. Convergys serves the world's leading companies in many industries including communications, financial services, technology, and consumer products. Convergys is a member of the S&P 500 and a Fortune Most Admired Company. Headquartered in Cincinnati, Ohio, Convergys has more than 62,000 employees in 68 customer contact centers, three data centers, and other facilities in the United States, Canada, Latin America, Europe, the Middle East, and Asia. For more information visit www.convergys.com (Infinys is a trademark and Convergys and the Convergys logo are registered trademarks of Convergys Corporation.).
September 27, 2005, Cincinnati, Ohio - Indonesia's premier cellular and wireless network operator Telkomsel has gone live with the first phase of Siemens' (NYSE: SI) market-leading, real-time, convergent charging solution, charge@once, that features Infinys [tm] Rating software from Convergys Corporation (NYSE: CVG). Telkomsel obtained the advanced solution to deliver the first-ever, truly convergent pre- and post-paid rating and billing of individual customer segments regardless of payment options. The solution currently supports more than 21 million subscribers.With the initial implementation by Siemens and Convergys now completed, Telkomsel is using the convergent charging solution to support its geographically complex business that spans over 13,000 islands. The solution satisfied Telkomsel's rigorous IT, engineering, and network requirements. It is now supporting an operation that has more than 54 percent of the mobile market in Indonesia and provides network coverage to more than 90 percent of the country's population, including corporate and private customers.The architecturally advanced solution, featuring Infinys as the embedded rater on Siemens' Charging, enables Telkomsel to explore the full range of convergent pre- and post-paid capabilities. These include real-time checking of credit limits, flexible charge and packages adjustment, as well as the use of bonus schemes and hybrid offers that help enhance customer loyalty and average revenue per user across all subscribers and service types."The success of this project reaffirms our decision to partner with Siemens and Convergys," said Arman Hazairin, Vice President Information and Technology Telkomsel. "We operate in an increasingly competitive market, so it is imperative that we can innovate around products and differentiate our offerings from those of competitors. The charge@once solution enables this, supports our drive to become even more customer-focused, and provides a platform for developing new revenue streams and achieving long-term growth.""Completing the first phase of the implementation, supporting the complete customer base with a comprehensive real-time solution, and providing maximum charging flexibility at Telkomsel are major milestones for the Siemens convergent charging system, charge@once, featuring online rating from Infinys," said Volker Ziegler, President of Applications and Solutions at Siemens COM. "Together with Convergys, we are demonstrating the real-world viability of our solution in a market where similar projects involving other suppliers have not yet been successful. Upon completion, the OPEX-effective solution will place Telkomsel in a unique position, enabling it to respond more quickly to changing market conditions, alter prices, and create discounts or promotions with an ease and alacrity hitherto unattainable.""Telkomsel is already seeing the benefits of a solution that effectively joins the high availability and scalability needed to support a tier-one operation with the real-time functionality and flexibility required to drive a customer-focused business," said Dave Dougherty, President and Chief Operating Officer of Convergys. "This project showcases both the capabilities of the world's first truly commercially operational online charging solution and the benefits of the close working relationship between Convergys and Siemens."Operators' needs for convergent online charging systems are increasing alongside the ever-expanding range of new multimedia data services for the online environment. The ability to handle both pre-paid and post-paid transactions in real time is critical if customers and providers are to quickly check usage limits and status of account balances in real time. This capability, provided by the Siemens and Convergys solution, allows customers to make informed decisions about their usage and expenditures while enabling operators to better manage their risk of revenue exposure. The solution also permits operators to constantly expand the existing charging structures and map new business and billing models in the charging system, which were once restricted to the post-paid offline environment.About TelkomselTelkomsel is the leading operator of cellular telecommunications services in Indonesia by market share. By the end of June 2005, Telkomsel had more than 21 million customers, which represented of around 54 percent market share in the telecommunication industry. Telkomsel provides GSM cellular services in Indonesia, through its own nationwide dual band 900/1800 MHz GSM network, and internationally, has 219 roaming operator partners in 135 countries (June 2005). Telkomsel's operations in Indonesia have grown substantially since the commercial launch of its post-paid services on 26 May 1995. In November 1997, Telkomsel became the first cellular telecommunications operator in Asia to introduce rechargeable GSM pre-paid services, a solution with Siemens. Telkomsel has the largest network coverage of any of the cellular operators in Indonesia, providing network coverage to over 90% of Indonesia's population and is the only operator in Indonesia that covers all of the country's provinces, cities, and regencies ("kabupaten"). The company currently offers GSM Dual Band (900 & 1800), GPRS, Wi-Fi, and EDGE Technology and has a successful 3G trial. For more information, see www.telkomsel.comAbout Siemens CommunicationsSiemens Communications is one of the largest players in the global telecommunications industry. Siemens is the only provider in the market hat offers its customers a full-range portfolio, from end-user equipment to complex network infrastructures for enterprises and carriers as well as related services. Siemens Communications is the world's innovation leader in convergent technologies, products and services for wireless, fixed and enterprise networks. It is the largest Group within Siemens and operates in more than 160 countries around the world. In fiscal 2004 (year-end September 30), its 60,000-strong workforce posted sales of approximately 18 billion Euros. For more information, see http://www.siemens.com/communicationsAbout ConvergysConvergys Corporation (NYSE: CVG) is a global leader in providing customer care, human resources, and billing services. Convergys combines specialized knowledge and expertise with solid execution to deliver outsourced solutions, consulting services, and software support. Clients in more than 60 countries speaking nearly 30 languages depend on Convergys to manage the increasing complexity and cost of caring for customers and employees. Convergys serves the world's leading companies in many industries including communications, financial services, technology, and consumer products. Convergys is a member of the S&P 500 and a Fortune Most Admired Company. Headquartered in Cincinnati, Ohio, Convergys has more than 62,000 employees in 68 customer contact centers, three data centers, and other facilities in the United States, Canada, Latin America, Europe, the Middle East, and Asia. For more information visit www.convergys.com (Infinys is a trademark and Convergys and the Convergys logo are registered trademarks of Convergys Corporation.).
ETL
Extract, transform, load
From Wikipedia, the free encyclopedia
Extract, Transform, and Load (ETL) is a process in data warehousing that involves
extracting data from outside sources,
transforming it to fit business needs (which can include quality levels), and ultimately
loading it into the end target, i.e. the data warehouse.
ETL is important, as it is the way data actually gets loaded into the warehouse. This article assumes that data is always loaded into a data warehouse, whereas the term ETL can in fact refer to a process that loads any database. ETL can also be used for the integration with legacy systems. Usually ETL implementations store an audit trail on positive and negative process runs. In almost all designs, this audit trail is not at the level of granularity which would allow to reproduce the ETL's result if the raw data were not available.
Extract
The first part of an ETL process is to extract the data from the source systems. Most data warehousing projects consolidate data from different source systems. Each separate system may also use a different data organization / format. Common data source formats are relational databases and flat files, but may include non-relational database structures such as IMS or other data structures such as VSAM or ISAM. Extraction converts the data into a format for transformation processing.
An intrinsic part of the extraction is the parsing of extracted data, resulting in a check if the data meets an expected pattern or structure. If not, the data is rejected entirely.
[edit] Transform
The transform stage applies a series of rules or functions to the extracted data from the source to derive the data to be loaded to the end target. Some data sources will require very little or even no manipulation of data. In other cases, one or more of the following transformations types to meet the business and technical needs of the end target may be required:
Selecting only certain columns to load (or selecting null columns not to load)
Translating coded values (e.g., if the source system stores 1 for male and 2 for female, but the warehouse stores M for male and F for female), this is called automated data cleansing; no manual cleansing occurs during ETL
Encoding free-form values (e.g., mapping "Male" to "1" and "Mr" to M)
Deriving a new calculated value (e.g., sale_amount = qty * unit_price)
Joining together data from multiple sources (e.g., lookup, merge, etc.)
Summarizing multiple rows of data (e.g., total sales for each store, and for each region)
Generating surrogate key values
Transposing or pivoting (turning multiple columns into multiple rows or vice versa)
Splitting a column into multiple columns (e.g., putting a comma-separated list specified as a string in one column as individual values in different columns)
Applying any form of simple or complex data validation; if failed, a full, partial or no rejection of the data, and thus no, partial or all the data is handed over to the next step, depending on the rule design and exception handling. Most of the above transformations itself might result in an exception, e.g. when a code-translation parses an unknown code in the extracted data.
[edit] Load
The load phase loads the data into the end target, usually being the data warehouse (DW). Depending on the requirements of the organization, this process ranges widely. Some data warehouses might weekly overwrite existing information with cumulative, updated data, while other DW (or even other parts of the same DW) might add new data in a historized form, e.g. hourly. The timing and scope to replace or append are strategic design choices dependent on the time available and the business needs. More complex systems can maintain a history and audit trail of all changes to the data loaded in the DW.
As the load phase interacts with a database, the constraints defined in the database schema as well as in triggers activated upon data load apply (e.g. uniqueness, referential integrity, mandatory fields), which also contribute to the overall data quality performance of the ETL process.
From Wikipedia, the free encyclopedia
Extract, Transform, and Load (ETL) is a process in data warehousing that involves
extracting data from outside sources,
transforming it to fit business needs (which can include quality levels), and ultimately
loading it into the end target, i.e. the data warehouse.
ETL is important, as it is the way data actually gets loaded into the warehouse. This article assumes that data is always loaded into a data warehouse, whereas the term ETL can in fact refer to a process that loads any database. ETL can also be used for the integration with legacy systems. Usually ETL implementations store an audit trail on positive and negative process runs. In almost all designs, this audit trail is not at the level of granularity which would allow to reproduce the ETL's result if the raw data were not available.
Extract
The first part of an ETL process is to extract the data from the source systems. Most data warehousing projects consolidate data from different source systems. Each separate system may also use a different data organization / format. Common data source formats are relational databases and flat files, but may include non-relational database structures such as IMS or other data structures such as VSAM or ISAM. Extraction converts the data into a format for transformation processing.
An intrinsic part of the extraction is the parsing of extracted data, resulting in a check if the data meets an expected pattern or structure. If not, the data is rejected entirely.
[edit] Transform
The transform stage applies a series of rules or functions to the extracted data from the source to derive the data to be loaded to the end target. Some data sources will require very little or even no manipulation of data. In other cases, one or more of the following transformations types to meet the business and technical needs of the end target may be required:
Selecting only certain columns to load (or selecting null columns not to load)
Translating coded values (e.g., if the source system stores 1 for male and 2 for female, but the warehouse stores M for male and F for female), this is called automated data cleansing; no manual cleansing occurs during ETL
Encoding free-form values (e.g., mapping "Male" to "1" and "Mr" to M)
Deriving a new calculated value (e.g., sale_amount = qty * unit_price)
Joining together data from multiple sources (e.g., lookup, merge, etc.)
Summarizing multiple rows of data (e.g., total sales for each store, and for each region)
Generating surrogate key values
Transposing or pivoting (turning multiple columns into multiple rows or vice versa)
Splitting a column into multiple columns (e.g., putting a comma-separated list specified as a string in one column as individual values in different columns)
Applying any form of simple or complex data validation; if failed, a full, partial or no rejection of the data, and thus no, partial or all the data is handed over to the next step, depending on the rule design and exception handling. Most of the above transformations itself might result in an exception, e.g. when a code-translation parses an unknown code in the extracted data.
[edit] Load
The load phase loads the data into the end target, usually being the data warehouse (DW). Depending on the requirements of the organization, this process ranges widely. Some data warehouses might weekly overwrite existing information with cumulative, updated data, while other DW (or even other parts of the same DW) might add new data in a historized form, e.g. hourly. The timing and scope to replace or append are strategic design choices dependent on the time available and the business needs. More complex systems can maintain a history and audit trail of all changes to the data loaded in the DW.
As the load phase interacts with a database, the constraints defined in the database schema as well as in triggers activated upon data load apply (e.g. uniqueness, referential integrity, mandatory fields), which also contribute to the overall data quality performance of the ETL process.
Minggu, 06 Juli 2008
Telkomsel Pilih LTE
Telkomsel Pilih LTE Karena Wimax Lemah Standarisasi
Bandung (ANTARA News) - Operator seluler, PT Telkomsel, memilih akan menggunakan teknologi LTE (long term evolution) untuk mengembangkan jaringan GSM (global system for mobile communication) ketimbang Wimax yang tengah dikembangkan pemerintah."Oleh Telkom group, Telkomsel tidak akan masuk menggunakan teknologi Wimax. Roadmap ke depan, Telkomsel akan menggunakan teknologi LTE," kata Direktur Perencanaan dan Pengembangan Telkomsel Syraif Syarial Ahmad di Bogor akhir pekan ini.Sementara Vice President Teknologi Planning and Bussiness Incubations Telkomsel Joseph Garo mengatakan, Telkomsel memutuskan menggunakan teknologi LTE karena melihat ada beberapa kelebihan dibandingkan dengan Wimax.Menurut Joseph, Wimax mempunyai kelemahan pada standarisasi yang tidak terlalu matang baik pada perangkat terminal, infrastruktur maupun frekuensi yang digunakan."Layanan akan lebih efisien kalau semua perangkat standar, otomatis infastruktur lebih efisien, maka volume yang tersedia akan lebih besar sehingga biaya akan lebih rendah," jelas dia."Hal ini akan berdampak pada terhambatnya pengembangan perangkat. Sedangkan LTE hanya mengembangkan teknologi GSM sebelumnya yaitu 3G sehingga tidak menambah perangkat-perangkat lain," sambung Joseph.Joseph frekuensi WCDMA lebih rendah dibandingkan frekuensi GSM sehingga jangkuan akan lebih luas dalam satu wilayah BTS, sehingga nantinya investasi akan lebih efisien.Karena hanya mengembangkan teknologi 3G GSM, maka investasi untuk menggunakan teknologi LTE tiga kali lebih murah dibandingkan investasi untuk menggunakan teknologi Wimax.Bila memang menggunakan teknologi Wimax, kata Joseph, Telkomsel hanya akan menggunakan untuk jaringan pelengkap (backhaul / complementary acces) Joseph mengatakan teknologi Wimax lebih cocok digunakan untuk koneksi telekomunikasi di perusahaan kecil seperti penyedia jasa internet (ISP) atau untuk penggunaan internal sebuah perusahaan.Langkah pertama yang dilakukan oleh Telkomsel untuk menggunakan menggunakan teknologi LTE adalah menambah jumlah frekuensi minimum 10 Megahertz, dan untuk mengoptimalkan teknologi tersebut, Telkomsel harus menambah 10 Megahertz lagi."Kalau tidak mendapatkan frekuensi tambahan, maka Telkomsel akan menggunakan frekuensi GSM yang telah ada melalui proses refarming," terang Joseph."Refarming" merupakan proses mengubah frekuensi GSM menjadi frekuensi Wide Band CDMA (WCDMA) dengan cara mengubah seluruh infrastruktur telekomunikasi mulai dari BTS dan sebagainya.Joseph frekuensi WCDMA lebih rendah dibandingkan frekuensi GSM sehingga jangkuan akan lebih luas dalam satu wilayah BTS, sehingga nantinya investasi akan lebih efisien.Joseph mengatakan Telkomsel akan melakukan uji coba refarming teknologi GSM ke teknologi WCDMA di Jakarta pada pertengahan tahun ini."Biaya untuk refarming akan diambilkan dari R & D (riset dan pengembangan) yang masuk pada biaya operasional," katanya.Syarif Syarial Ahmad memperkirakan teknologi WCDMA ini dapat dioperasikan oleh Telkomsel sekitar tahun 2010.(*)
Bandung (ANTARA News) - Operator seluler, PT Telkomsel, memilih akan menggunakan teknologi LTE (long term evolution) untuk mengembangkan jaringan GSM (global system for mobile communication) ketimbang Wimax yang tengah dikembangkan pemerintah."Oleh Telkom group, Telkomsel tidak akan masuk menggunakan teknologi Wimax. Roadmap ke depan, Telkomsel akan menggunakan teknologi LTE," kata Direktur Perencanaan dan Pengembangan Telkomsel Syraif Syarial Ahmad di Bogor akhir pekan ini.Sementara Vice President Teknologi Planning and Bussiness Incubations Telkomsel Joseph Garo mengatakan, Telkomsel memutuskan menggunakan teknologi LTE karena melihat ada beberapa kelebihan dibandingkan dengan Wimax.Menurut Joseph, Wimax mempunyai kelemahan pada standarisasi yang tidak terlalu matang baik pada perangkat terminal, infrastruktur maupun frekuensi yang digunakan."Layanan akan lebih efisien kalau semua perangkat standar, otomatis infastruktur lebih efisien, maka volume yang tersedia akan lebih besar sehingga biaya akan lebih rendah," jelas dia."Hal ini akan berdampak pada terhambatnya pengembangan perangkat. Sedangkan LTE hanya mengembangkan teknologi GSM sebelumnya yaitu 3G sehingga tidak menambah perangkat-perangkat lain," sambung Joseph.Joseph frekuensi WCDMA lebih rendah dibandingkan frekuensi GSM sehingga jangkuan akan lebih luas dalam satu wilayah BTS, sehingga nantinya investasi akan lebih efisien.Karena hanya mengembangkan teknologi 3G GSM, maka investasi untuk menggunakan teknologi LTE tiga kali lebih murah dibandingkan investasi untuk menggunakan teknologi Wimax.Bila memang menggunakan teknologi Wimax, kata Joseph, Telkomsel hanya akan menggunakan untuk jaringan pelengkap (backhaul / complementary acces) Joseph mengatakan teknologi Wimax lebih cocok digunakan untuk koneksi telekomunikasi di perusahaan kecil seperti penyedia jasa internet (ISP) atau untuk penggunaan internal sebuah perusahaan.Langkah pertama yang dilakukan oleh Telkomsel untuk menggunakan menggunakan teknologi LTE adalah menambah jumlah frekuensi minimum 10 Megahertz, dan untuk mengoptimalkan teknologi tersebut, Telkomsel harus menambah 10 Megahertz lagi."Kalau tidak mendapatkan frekuensi tambahan, maka Telkomsel akan menggunakan frekuensi GSM yang telah ada melalui proses refarming," terang Joseph."Refarming" merupakan proses mengubah frekuensi GSM menjadi frekuensi Wide Band CDMA (WCDMA) dengan cara mengubah seluruh infrastruktur telekomunikasi mulai dari BTS dan sebagainya.Joseph frekuensi WCDMA lebih rendah dibandingkan frekuensi GSM sehingga jangkuan akan lebih luas dalam satu wilayah BTS, sehingga nantinya investasi akan lebih efisien.Joseph mengatakan Telkomsel akan melakukan uji coba refarming teknologi GSM ke teknologi WCDMA di Jakarta pada pertengahan tahun ini."Biaya untuk refarming akan diambilkan dari R & D (riset dan pengembangan) yang masuk pada biaya operasional," katanya.Syarif Syarial Ahmad memperkirakan teknologi WCDMA ini dapat dioperasikan oleh Telkomsel sekitar tahun 2010.(*)
Minggu, 15 Juni 2008
Intelligent Network Application Part (INAP)
Intelligent Network Application Part (INAP)
Intelligent Network Application Part (INAP) is the signaling protocol used in Intelligent Networking. Developed by the International Telecommunications Union (ITU), IN is recognized as a global standard. Within the International Telecommunications Union, a total functionality of the IN has been defined and implemented in digestible segments called capability sets. The first version to be released was Capability Set 1 (CS-1). Currently CS-2 is defined and available. The CAMEL Application Part (CAP) is a derivative of INAP and enables the use of INAP in mobile GSM networks.
INAP is a signaling protocol between a service switching point (SSP), network media resources (intelligent peripherals), and a centralized network database called a service control point (SCP). The SCP consists of operator or 3rd party derived service logic programs and data.
Service Switching Point (SSP) is a physical entity in the Intelligent Network that provides the switching functionality. SSP the point of subscription for the service user, and is responsible for detecting special conditions during call processing that cause a query for instructions to be issued to the SCP.
The SSP contains Detection Capability to detect requests for IN services. It also contains capabilities to communicate with other physical entities containing SCF, such as SCP, and to respond to instructions from the other physical entities. Functionally, an SSP contains a Call Control Function, a Service Switching Function, and, if the SSP is a local exchange, a Call Control Agent Function. It also may optionally contain Service Control Function, and/or a Specialized Resource Function, and/or a Service Data Function. The SSP may provide IN services to users connected to subtending Network Access Points.
The SSP is usually provided by the traditional switch manufacturers. These switches are programmable and they can be implemented using multipurpose processors. The main difference of SSP from an ordinary switch is in the software where the service control of IN is separated from the basic call control.
Service Control Point (SCP) validates and authenticates information from the service user, processing requests from the SSP and issuing responses.The SCP stores the service provider instructions and data that direct switch processing and provide call control. At predefined points during processing an incoming or outgoing call, the switch suspends what it is doing, packages up information it has regarding the processing of the call, and queries the SCP for further instruction. The SCP executes user-defined programs that analyze the current state of the call and the information received from the switch. The programs can then modify or create the call data that is sent back to the switch. The switch then analyzes the information received from the SCP and follows the provided instruction to further process the call.
Functionally, an SCP contains Service Control Function (SCF) and optionally also Service Data Function (SDF). The SCF is implemented in Service Logic Programs (SLP). The SCP is connected to SSPs by a signalling network. Multiple SCPs may contain the same SLPs and data to improve service reliability and to facilitate load sharing between SCPs. In case of external Service Data Point (SDP) the SCF can access data through a signalling network. The SDP may be in the same network as the SCP, or in another network. The SCP can be connected to SSPs, and optionally to IPs, through the signalling network. The SCP can also be connected to an IP via an SSP relay function. The SCP comprises the SCP node, the SCP platform, and applications. The node performs functions common to applications, or independent of any application; it provides all functions for handling service-related, administrative, and network messages. These functions include message discrimination, distribution, routing, and network management and testing. For example, when the SCP node receives a service-related message, it distributes the incoming message to the proper application. In turn, the application issues a response message to the node, which routes it to the appropriate network elements. The SCP node gathers data on all incoming and outgoing messages to assist in network administration and cost allocation. This data is collected at the node, and transmitted to an administrative system for processing.
Intelligent Peripheral (IP) provides resources such as customized and concatenated voice announcements, voice recognition, and Dual Tone Multi-Frequencies (DTMF) digit collection, and contains switching matrix to connect users to these resources. The IP supports flexible information interactions between a user and the network. Functionally, the IP contains the Special Resource Function. The IP may directly connect to one or more SSPs, and/or may connect to the signalling network.
Service Management Point (SMP) performs service management control, service provision control, and service deployment control. Examples of functions it can perform are database administration, network surveillance and testing, network traffic management, and network data collection. Functionally, the SMP contains the Service Management Function and, optionally, the Service Management Access Function and the Service Creation Environment
Function. The SMP can access all other Physical Entities.
Conceptual model of the Intelligent Network :
The IN standards present a conceptual model of the Intelligent Network that model and abstract the IN functionality in four planes:
The Service Plane (SP): This plane is of primary interest to service users and providers. It describes services and service features from a user perspective, and is not concerned with how the services are implemented within the network.
The Global Functional Plane (GFP): The GFP is of primary interest to the service designer. It describes units of functionality, known as service independent building blocks (SIBs) and it is not concerned with how the functionality is distributed in the network. Services and service features can be realised in the service plane by combining SIBs in the GFP.
The Distributed Functional Plane (DFP): This plane is of primary interest to network providers and designers. It defines the functional architecture of an IN-structured network in terms of network functionality, known as functional entities (FEs). SIBs in the GFP are realised in the DFP by a sequence of functional entity actions (FEAs) and their resulting information flows.
The Physical Plane (PP): Real view of the physical network.The PP is of primary interest to equipment providers. It describes the physical architecture for an IN-structured network in terms of physical entities (PEs) and the interfaces between them. The functional entities from the DFP are realised by physical entities in the physical plane.
Services that can be defined with INAP include:
Single number service: one number reaches a local number associated with the service
Personal access service: provide end user management of incoming calls
Disaster recovery service: define backup call destinations in case of disaster
Do not disturb service: call forward
Virtual private network short digit extension dialing service
Advantages created by the IN architecture:
extensive use of information processing techniques;
efficient use of network resources;
modularization of network functions;
integrated service creation and implementation by means of reusable standard network functions;
flexible allocation of network functions to physical entities;
portability of network functions among physical entities;
standardised communication between network functions via service independent interfaces;
customer control over their specific service attributes;
standardised management of service logic.
References:
SS7 Discussion Forum
http://www.item.ntnu.no/fag/ttm4130/stottelitteratur/IN.pdf
http://www.doc.ic.ac.uk/~nd/surprise_97/journal/vol4/vra/
Intelligent Network Application Part (INAP) is the signaling protocol used in Intelligent Networking. Developed by the International Telecommunications Union (ITU), IN is recognized as a global standard. Within the International Telecommunications Union, a total functionality of the IN has been defined and implemented in digestible segments called capability sets. The first version to be released was Capability Set 1 (CS-1). Currently CS-2 is defined and available. The CAMEL Application Part (CAP) is a derivative of INAP and enables the use of INAP in mobile GSM networks.
INAP is a signaling protocol between a service switching point (SSP), network media resources (intelligent peripherals), and a centralized network database called a service control point (SCP). The SCP consists of operator or 3rd party derived service logic programs and data.
Service Switching Point (SSP) is a physical entity in the Intelligent Network that provides the switching functionality. SSP the point of subscription for the service user, and is responsible for detecting special conditions during call processing that cause a query for instructions to be issued to the SCP.
The SSP contains Detection Capability to detect requests for IN services. It also contains capabilities to communicate with other physical entities containing SCF, such as SCP, and to respond to instructions from the other physical entities. Functionally, an SSP contains a Call Control Function, a Service Switching Function, and, if the SSP is a local exchange, a Call Control Agent Function. It also may optionally contain Service Control Function, and/or a Specialized Resource Function, and/or a Service Data Function. The SSP may provide IN services to users connected to subtending Network Access Points.
The SSP is usually provided by the traditional switch manufacturers. These switches are programmable and they can be implemented using multipurpose processors. The main difference of SSP from an ordinary switch is in the software where the service control of IN is separated from the basic call control.
Service Control Point (SCP) validates and authenticates information from the service user, processing requests from the SSP and issuing responses.The SCP stores the service provider instructions and data that direct switch processing and provide call control. At predefined points during processing an incoming or outgoing call, the switch suspends what it is doing, packages up information it has regarding the processing of the call, and queries the SCP for further instruction. The SCP executes user-defined programs that analyze the current state of the call and the information received from the switch. The programs can then modify or create the call data that is sent back to the switch. The switch then analyzes the information received from the SCP and follows the provided instruction to further process the call.
Functionally, an SCP contains Service Control Function (SCF) and optionally also Service Data Function (SDF). The SCF is implemented in Service Logic Programs (SLP). The SCP is connected to SSPs by a signalling network. Multiple SCPs may contain the same SLPs and data to improve service reliability and to facilitate load sharing between SCPs. In case of external Service Data Point (SDP) the SCF can access data through a signalling network. The SDP may be in the same network as the SCP, or in another network. The SCP can be connected to SSPs, and optionally to IPs, through the signalling network. The SCP can also be connected to an IP via an SSP relay function. The SCP comprises the SCP node, the SCP platform, and applications. The node performs functions common to applications, or independent of any application; it provides all functions for handling service-related, administrative, and network messages. These functions include message discrimination, distribution, routing, and network management and testing. For example, when the SCP node receives a service-related message, it distributes the incoming message to the proper application. In turn, the application issues a response message to the node, which routes it to the appropriate network elements. The SCP node gathers data on all incoming and outgoing messages to assist in network administration and cost allocation. This data is collected at the node, and transmitted to an administrative system for processing.
Intelligent Peripheral (IP) provides resources such as customized and concatenated voice announcements, voice recognition, and Dual Tone Multi-Frequencies (DTMF) digit collection, and contains switching matrix to connect users to these resources. The IP supports flexible information interactions between a user and the network. Functionally, the IP contains the Special Resource Function. The IP may directly connect to one or more SSPs, and/or may connect to the signalling network.
Service Management Point (SMP) performs service management control, service provision control, and service deployment control. Examples of functions it can perform are database administration, network surveillance and testing, network traffic management, and network data collection. Functionally, the SMP contains the Service Management Function and, optionally, the Service Management Access Function and the Service Creation Environment
Function. The SMP can access all other Physical Entities.
Conceptual model of the Intelligent Network :
The IN standards present a conceptual model of the Intelligent Network that model and abstract the IN functionality in four planes:
The Service Plane (SP): This plane is of primary interest to service users and providers. It describes services and service features from a user perspective, and is not concerned with how the services are implemented within the network.
The Global Functional Plane (GFP): The GFP is of primary interest to the service designer. It describes units of functionality, known as service independent building blocks (SIBs) and it is not concerned with how the functionality is distributed in the network. Services and service features can be realised in the service plane by combining SIBs in the GFP.
The Distributed Functional Plane (DFP): This plane is of primary interest to network providers and designers. It defines the functional architecture of an IN-structured network in terms of network functionality, known as functional entities (FEs). SIBs in the GFP are realised in the DFP by a sequence of functional entity actions (FEAs) and their resulting information flows.
The Physical Plane (PP): Real view of the physical network.The PP is of primary interest to equipment providers. It describes the physical architecture for an IN-structured network in terms of physical entities (PEs) and the interfaces between them. The functional entities from the DFP are realised by physical entities in the physical plane.
Services that can be defined with INAP include:
Single number service: one number reaches a local number associated with the service
Personal access service: provide end user management of incoming calls
Disaster recovery service: define backup call destinations in case of disaster
Do not disturb service: call forward
Virtual private network short digit extension dialing service
Advantages created by the IN architecture:
extensive use of information processing techniques;
efficient use of network resources;
modularization of network functions;
integrated service creation and implementation by means of reusable standard network functions;
flexible allocation of network functions to physical entities;
portability of network functions among physical entities;
standardised communication between network functions via service independent interfaces;
customer control over their specific service attributes;
standardised management of service logic.
References:
SS7 Discussion Forum
http://www.item.ntnu.no/fag/ttm4130/stottelitteratur/IN.pdf
http://www.doc.ic.ac.uk/~nd/surprise_97/journal/vol4/vra/
Signalling
•INAP: Intelligent Network Application Part •CAMEL: Customized Application for Mobile
GSM uses SS7 signalling for call control, mobility management, short messages and value-added services.
GSM uses SS7 signalling for call control, mobility management, short messages and value-added services.
•MTP1-3: Message Transfer Part
•SCCP: Signalling Connection Control Part
•TCAP: Transaction Capabilities Application Part
•MAP: Mobile Application Part
•BSSAP: Base Station Subsystem Application Part
•
Enhanced Logic
Intelligent Network (IN) Concept
The intelligent network concept: intelligence is taken out of exchanges and placed in computer nodes that are distributed throughout the network.
Intelligence => access to various databases
This provides the network operator with the means to develop and control services more efficiently. New capabilities can be rapidly introduced into the network. Once introduced, services are easily customized to meet individual customer's needs.
IN service subscriber and customer
In a typical IN service scenario, the network operator or a 3rd party service provider implements the service for one or several subscribers, after which customers can use the service.
Service subscriber = company offering the service (e.g. the 0800 number that anybody can call)
Customers = those who use the service (e.g. those who call the 0800 number)
Confusion possible:
IN service subscriber ¹ PSTN subscriber
IN services
A large number of IN services can be implemented by combining different “building blocks”:
- Called number translation (at SCP)
- Routing decision based on calling number, time, date, called user busy, called user alerting timeout, network load ...
- Announcements (from IP) or user notification (<= ISDN user signalling)
- DTMF number reception (at IP) and analysis (at SCP)
- Customised charging (at exchanges)
4G & IN
4G – Akhir dari Kejayaan Intelligent Network.
http://dasteld3ilkomuns.wordpress.com/
1G, 2G, 2.5G, 3G dan terakhir 4G merupakan generasi teknologi yang digunakan pada infrastruktur selular. Pada hari ini, Indonesia baru memasuki tahapan teknologi 2.5G. Secara sederhana dapat di identikan teknologi 1G adalah telepon analog / PSTN yang menggunakan selular. Teknologi 2G, 2.5G dan 3G merupakan ISDN di selular.
Intelligent Network (IN) secara sederhana merupakan inti dari infrastruktur telekomunikasi yang di operasikan oleh banyak operator telekomunikasi di Indonesia pada saat ini. Khususnya di dunia selular banyak bertumpu pada protokol SS7/IS-41/GSM MAP intelligent nodes.Teknik yang hampir sama juga berlaku untuk operator non-selular, seperti Telkom, Indosat & Satelindo.
Servis suara di 3G pada dasarnya sama dengan servis suara di ISDN. Handset digital selular pada dasarnya sebuah handset ISDN. Sialnya, ISDN pada kenyataannya tidak berhasil dengan baik untuk mendeploy servis suara yang baru maupun integrasi data / suara. Kita cukup beruntung dengan adanya 3G ternyata membuka kesempatan untuk uji coba teknologi Internet seperti Session Initiation Protocol (SIP) maupun menggunaan IP v6 (saat ini semua ISP komersial di Indonesia menggunakan IP v4 yang lebih tua). Ujicoba untuk integrasi SIP & IP v6 ke dalam 3G di lakukan dalam inisiatif 3GPP
http://dasteld3ilkomuns.wordpress.com/
1G, 2G, 2.5G, 3G dan terakhir 4G merupakan generasi teknologi yang digunakan pada infrastruktur selular. Pada hari ini, Indonesia baru memasuki tahapan teknologi 2.5G. Secara sederhana dapat di identikan teknologi 1G adalah telepon analog / PSTN yang menggunakan selular. Teknologi 2G, 2.5G dan 3G merupakan ISDN di selular.
Intelligent Network (IN) secara sederhana merupakan inti dari infrastruktur telekomunikasi yang di operasikan oleh banyak operator telekomunikasi di Indonesia pada saat ini. Khususnya di dunia selular banyak bertumpu pada protokol SS7/IS-41/GSM MAP intelligent nodes.Teknik yang hampir sama juga berlaku untuk operator non-selular, seperti Telkom, Indosat & Satelindo.
Servis suara di 3G pada dasarnya sama dengan servis suara di ISDN. Handset digital selular pada dasarnya sebuah handset ISDN. Sialnya, ISDN pada kenyataannya tidak berhasil dengan baik untuk mendeploy servis suara yang baru maupun integrasi data / suara. Kita cukup beruntung dengan adanya 3G ternyata membuka kesempatan untuk uji coba teknologi Internet seperti Session Initiation Protocol (SIP) maupun menggunaan IP v6 (saat ini semua ISP komersial di Indonesia menggunakan IP v4 yang lebih tua). Ujicoba untuk integrasi SIP & IP v6 ke dalam 3G di lakukan dalam inisiatif 3GPP
GSM 1800
GSM 1800: Frekuensi Besar, Jangkauan Sempit
http://dasteld3ilkomuns.wordpress.com/
Teknologi ponsel terus berkembang dari waktu ke waktu. Akan tetapi, bukan berarti yang terbaru adalah yang terhebat. Setiap jenis ada kekurangan dan kelebihan masing-masing.
Teknologi telepon selular di Indonesia saat ini telah berkembang begitu pesatnya. Jangan heran kalau minat konsumen pun makin meningkat. Ujung-ujungnya pengguna telepon selular pada tahun ini diduga akan bertambah dua kali lipat dibandingkan dengan tahun lalu.
Jenis telepon selular yang pertama kali masuk di Indonesia adalah jenis NMT (nordic mobile telephone). Jenis selular ini menggunakan frekuensi 450 mHz, tetapi khusus di Indonesia digunakan frekuensi 470 mHz. Daerah jangkauan NMT dapat mencapai 60 kilometer, sehingga memungkinkan NMT digunakan di daerah-daerah terpencil yang jauh dari pusat kota. Namun jenis selular pertama ini mempunyai kekurangan, yaitu bentuknya yang relatif besar sehingga membuat NMT kurang efektif dan efisien untuk dibawa bepergian.
Menyusul berkembangnya teknologi NMT, muncul pula teknologi baru selular yaitu AMPS (advance mobile phone system). Sistem AMPS menggunakan frekuensi 800 mHz dan daya jangkaunya sekitar 1,5 km sampai 2 km. Karena bentuknya yang ringan dan dapat dibawa dengan mudah, maka teknologi AMPS menjadi pilihan baru dalam berkomunikasi. Bahkan teknologi yang berasal dari Amerika Serikat ini pernah menjadi primadona dunia informasi dunia pada 1980-an sampai menjelang 1990-an.
Setelah berkembangnya AMPS, muncul pula sebuah teknologi selular digital CDMA (code division multiple access). CDMA adalah teknologi yang dikembangkan oleh militer Amerika Serikat pada 1989 dan mulai dioperasikan pada 1995. Teknologi CDMA dapat menggunakan frekuensi yang selama ini dipakai oleh AMPS yaitu 800 mHz. Cuma, CDMA juga dapat memakai frekuensi 1.700 mHz. Karena menggunakan teknologi yang sama, maka sistem AMPS yang analog akan dapat dengan sederhana bermigrasi ke sistem CDMA yang digital.
Pada saat yang hampir bersamaan dengan munculnya CDMA, teknologi GSM (global system for mobile communication) diperkenalkan. Dengan digunakannya sistem GSM yang digital, teknologi NMT atau AMPS yang analog praktis tidak dapat digunakan. Bagi para pengguna kedua sistem itu, hal ini sangat merugikan karena mereka telanjur memakai ponsel lama yang harganya relatif mahal. Hal ini menyebabkan banyak dari mereka enggan berpindah ke teknologi GSM. Namun setelah para operator GSM terlihat sangat serius dengan bisnisnya, maka mereka berlomba-lomba mencicipi teknologi baru tersebut. Hasilnya, saat ini sistem GSM-lah yang paling banyak digunakan di Indonesia untuk masalah ponsel.
Teknologi GSM yang kita pakai saat ini menggunakan frekuensi 900 mHz dengan daya jangkau 1,5 km sampai 2 km saja. Akan tetapi, daya jangkau itu dapat diperluas dengan menggunakan antena payung yang tinggi (umbrella). Dengan penggunaan antena payung, jarak jangkau GSM dapat mencapai 35 km.
Sebenarnya, ditinggalkannya sistem NMT dan AMPS bukan karena keduanya tidak dapat digunakan lagi, tetapi lebih karena kedua sistem itu sudah ketinggalan zaman–terutama NMT yang memang kurang nyaman untuk dibawa ke mana-mana. NMT dan AMPS di satu pihak masih mentransmisikan suara dengan cara analog, sedangkan CDMA dan GSM di pihak lain menggunakan teknologi digital yang menghasilkan kualitas suara yang jauh lebih baik. Oleh karena itu, AMPS dan NMT sering disebut sebagai selular generasi pertama, sedangkan GSM dan CDMA disebut sebagai selular generasi kedua.
http://dasteld3ilkomuns.wordpress.com/
Teknologi ponsel terus berkembang dari waktu ke waktu. Akan tetapi, bukan berarti yang terbaru adalah yang terhebat. Setiap jenis ada kekurangan dan kelebihan masing-masing.
Teknologi telepon selular di Indonesia saat ini telah berkembang begitu pesatnya. Jangan heran kalau minat konsumen pun makin meningkat. Ujung-ujungnya pengguna telepon selular pada tahun ini diduga akan bertambah dua kali lipat dibandingkan dengan tahun lalu.
Jenis telepon selular yang pertama kali masuk di Indonesia adalah jenis NMT (nordic mobile telephone). Jenis selular ini menggunakan frekuensi 450 mHz, tetapi khusus di Indonesia digunakan frekuensi 470 mHz. Daerah jangkauan NMT dapat mencapai 60 kilometer, sehingga memungkinkan NMT digunakan di daerah-daerah terpencil yang jauh dari pusat kota. Namun jenis selular pertama ini mempunyai kekurangan, yaitu bentuknya yang relatif besar sehingga membuat NMT kurang efektif dan efisien untuk dibawa bepergian.
Menyusul berkembangnya teknologi NMT, muncul pula teknologi baru selular yaitu AMPS (advance mobile phone system). Sistem AMPS menggunakan frekuensi 800 mHz dan daya jangkaunya sekitar 1,5 km sampai 2 km. Karena bentuknya yang ringan dan dapat dibawa dengan mudah, maka teknologi AMPS menjadi pilihan baru dalam berkomunikasi. Bahkan teknologi yang berasal dari Amerika Serikat ini pernah menjadi primadona dunia informasi dunia pada 1980-an sampai menjelang 1990-an.
Setelah berkembangnya AMPS, muncul pula sebuah teknologi selular digital CDMA (code division multiple access). CDMA adalah teknologi yang dikembangkan oleh militer Amerika Serikat pada 1989 dan mulai dioperasikan pada 1995. Teknologi CDMA dapat menggunakan frekuensi yang selama ini dipakai oleh AMPS yaitu 800 mHz. Cuma, CDMA juga dapat memakai frekuensi 1.700 mHz. Karena menggunakan teknologi yang sama, maka sistem AMPS yang analog akan dapat dengan sederhana bermigrasi ke sistem CDMA yang digital.
Pada saat yang hampir bersamaan dengan munculnya CDMA, teknologi GSM (global system for mobile communication) diperkenalkan. Dengan digunakannya sistem GSM yang digital, teknologi NMT atau AMPS yang analog praktis tidak dapat digunakan. Bagi para pengguna kedua sistem itu, hal ini sangat merugikan karena mereka telanjur memakai ponsel lama yang harganya relatif mahal. Hal ini menyebabkan banyak dari mereka enggan berpindah ke teknologi GSM. Namun setelah para operator GSM terlihat sangat serius dengan bisnisnya, maka mereka berlomba-lomba mencicipi teknologi baru tersebut. Hasilnya, saat ini sistem GSM-lah yang paling banyak digunakan di Indonesia untuk masalah ponsel.
Teknologi GSM yang kita pakai saat ini menggunakan frekuensi 900 mHz dengan daya jangkau 1,5 km sampai 2 km saja. Akan tetapi, daya jangkau itu dapat diperluas dengan menggunakan antena payung yang tinggi (umbrella). Dengan penggunaan antena payung, jarak jangkau GSM dapat mencapai 35 km.
Sebenarnya, ditinggalkannya sistem NMT dan AMPS bukan karena keduanya tidak dapat digunakan lagi, tetapi lebih karena kedua sistem itu sudah ketinggalan zaman–terutama NMT yang memang kurang nyaman untuk dibawa ke mana-mana. NMT dan AMPS di satu pihak masih mentransmisikan suara dengan cara analog, sedangkan CDMA dan GSM di pihak lain menggunakan teknologi digital yang menghasilkan kualitas suara yang jauh lebih baik. Oleh karena itu, AMPS dan NMT sering disebut sebagai selular generasi pertama, sedangkan GSM dan CDMA disebut sebagai selular generasi kedua.
Selasa, 10 Juni 2008
IM-SSF an architectural framework
IP Multimedia Subsystem
The IP Multimedia Subsystem (IMS) is an architectural framework for delivering internet protocol (IP) multimedia to mobile users. It was originally designed by the wireless standards body 3rd Generation Partnership Project (3GPP), and is part of the vision for evolving mobile networks beyond GSM. Its original formulation (3GPP R5) represented an approach to delivering "Internet services" over GPRS. This vision was later updated by 3GPP, 3GPP2 and TISPAN by requiring support of networks other than GPRS, such as Wireless LAN, CDMA2000 and fixed line.
To ease the integration with the Internet, IMS as far as possible uses IETF (i.e. Internet) protocols such as Session Initiation Protocol (SIP). According to the 3GPP[1], IMS is not intended to standardise applications itself but to aid the access of multimedia and voice applications across wireless and wireline terminals, i.e. aid a form of fixed mobile convergence (FMC). This is done by having a horizontal control layer that isolates the access network from the service layer. Services need not have their own control functions, as the control layer is a common horizontal layer.
Alternative and overlapping technologies for access and provision of services across wired and wireless networks depend on the actual requirements, and include combinations of Generic Access Network, soft switches and "naked" SIP. This makes the business use of IMS less appealing. It is easier to sell services than to sell the virtues of "integrated services". But, services for IMS have not been prolific.
Since IMS was conceived years ago, it is becoming increasingly easier to access content and contacts using mechanisms outside the control of traditional wireless/fixed operators, and so those operators are likely to reconsider their strategies[2]. Although it is expected that eventually IP will be available on all mobile phones and operators, it is not clear how much of the 3GPP/3GPP2/TISPAN IMS as it exists today will be deployed. "Early IMS" might be used in IMS implementations that do not yet support all "Full IMS" requirements, although it's not clearly defined what differences there might be (IPv4 support instead of IPv6 is often mentioned).
The IP Multimedia Subsystem (IMS) is an architectural framework for delivering internet protocol (IP) multimedia to mobile users. It was originally designed by the wireless standards body 3rd Generation Partnership Project (3GPP), and is part of the vision for evolving mobile networks beyond GSM. Its original formulation (3GPP R5) represented an approach to delivering "Internet services" over GPRS. This vision was later updated by 3GPP, 3GPP2 and TISPAN by requiring support of networks other than GPRS, such as Wireless LAN, CDMA2000 and fixed line.
To ease the integration with the Internet, IMS as far as possible uses IETF (i.e. Internet) protocols such as Session Initiation Protocol (SIP). According to the 3GPP[1], IMS is not intended to standardise applications itself but to aid the access of multimedia and voice applications across wireless and wireline terminals, i.e. aid a form of fixed mobile convergence (FMC). This is done by having a horizontal control layer that isolates the access network from the service layer. Services need not have their own control functions, as the control layer is a common horizontal layer.
Alternative and overlapping technologies for access and provision of services across wired and wireless networks depend on the actual requirements, and include combinations of Generic Access Network, soft switches and "naked" SIP. This makes the business use of IMS less appealing. It is easier to sell services than to sell the virtues of "integrated services". But, services for IMS have not been prolific.
Since IMS was conceived years ago, it is becoming increasingly easier to access content and contacts using mechanisms outside the control of traditional wireless/fixed operators, and so those operators are likely to reconsider their strategies[2]. Although it is expected that eventually IP will be available on all mobile phones and operators, it is not clear how much of the 3GPP/3GPP2/TISPAN IMS as it exists today will be deployed. "Early IMS" might be used in IMS implementations that do not yet support all "Full IMS" requirements, although it's not clearly defined what differences there might be (IPv4 support instead of IPv6 is often mentioned).
Signalling Connection Control Part (SCCP)
Signalling Connection Control Part
SS7 protocol suite
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The Signalling Connection Control Part (SCCP) is a transport layer protocol which provides extended routing, flow control, segmentation, connection-orientation, and error correction facilities in Signaling System 7 telecommunications networks. SCCP relies on the services of MTP for basic routing and error detection.
Contents[hide]
1 Published specification
2 Routing facilities beyond MTP-3
3 Classes of service
3.1 Class 0: Basic connectionless
3.2 Class 1: Sequenced connectionless
3.3 Class 2: Basic connection-oriented
3.4 Class 3: Flow control connection oriented
4 Transport over IP Networks
5 References
6 External links
//
[edit] Published specification
The base SCCP specification is defined by the ITU-T, in recommendations Q.711 to Q.714, with additional information to implementors provided by Q.715 and Q.716. There are, however, regional variations defined by local standards bodies. In the United States, ANSI publishes its modifications to Q.713 as ANSI T1.112 or JT-Q.711 to JT-Q.714, whilst in Europe ETSI publishes ETSI EN 300 009, which documents its modifications to the ITU-T specification.
[edit] Routing facilities beyond MTP-3
Although MTP-3 provides routing capabilities based upon the Point Code, SCCP allows routing using a Point Code and Subsystem number or a Global Title.
A Point Code is used to address a particular node on the network, whilst a Subsystem number addresses a specific application available on that node. SCCP employs a process called Global Title Translation (which is similar to DNS resolution in IP networks) in order to determine Point Codes from Global Titles so as to instruct MTP-3 on where to route messages.
SCCP messages contain parameters which describe the type of addressing used, and how the message should be routed:
Address Indicator
Subsystem indicator: The address includes a Subsystem Number
Point Code indicator: The address includes a Point Code
Global title indicator
No Global Title
Global Title includes Translation Type (TT), Numbering Plan Indiciator (NPI) and Type of Number (TON)
Global Title includes Translation Type only
Routing indicator
Route using Global Title only
Route using Point Code/Subsystem number
Address Indicator Coding
Address Indicator coded as national (the Address Indicator is treated as international if not specified)
[edit] Classes of service
SCCP provides 5 classes of service to its applications:
Class 0: Basic connectionless
Class 1: Sequenced connectionless
Class 2: Basic connection-oriented
Class 3: Flow control connection oriented
Class 4: Error recovery and flow control connection oriented
The connectionless protocol classes provide the capabilities needed to transfer one Network Service Data Unit (NSDU) in the "data" field of an XUDT, LUDT or UDT message. When one connectionless message is not sufficient to convey the user data contained in one NSDU, a segmenting/reassembly function for protocol classes 0 and 1 is provided. In this case, the SCCP at the originating node or in a relay node provides segmentation of the information into multiple segments prior to transfer in the "data" field of XUDT (or as a network option LUDT) messages. At the destination node, the NSDU is reassembled.
The connection-oriented protocol classes (protocol classes 2 and 3) provide the means to set up signalling connections in order to exchange a number of related NSDUs. The connection-oriented protocol classes also provide a segmenting and reassembling capability. If an NSDU is longer than 255 octets, it is split into multiple segments at the originating node, prior to transfer in the "data" field of DT messages. Each segment is less than or equal to 255 octets. At the destination node, the NSDU is reassembled.[1]
[edit] Class 0: Basic connectionless
The SCCP Class 0 service is the most basic of SCCP transports. Network Service Data Units passed by higher layers to the SCCP in the originating node are delivered by the SCCP to higher layers in the destination node. They are transferred independently of each other. Therefore, they may be delivered to the SCCP user out-of-sequence. Thus, this protocol class corresponds to a pure connectionless network service. As a connectionless protocol, no transport-level dialog is established between the sender and the receiver.
[edit] Class 1: Sequenced connectionless
SCCP Class 1 builds on the capabilities of Class 0, with the addition of a sequence control parameter in the NSDU which allows the SCCP User to instruct the SCCP that a given stream of messages should be delivered in sequence. Therefore, Protocol Class 1 corresponds to an enhanced connectionless service with in-sequence delivery.
[edit] Class 2: Basic connection-oriented
SCCP Class 2 provides the facilities of Class 1, but also allows for an entity to establish a two-way dialog with another entity using SCCP.
[edit] Class 3: Flow control connection oriented
Class 3 service builds upon Class 2, but also allows for expedited (urgent) messages to be sent and received, and for errors in sequencing (segment re-assembly) to be detected and for SCCP to restart a connection should this occur.
[edit] Transport over IP Networks
In the SIGTRAN suite of protocols, there are two primary methods of transporting SCCP applications across Internet Protocol networks: SCCP can be transported directly using the MTP level 3 User Adaptation protocol (M3UA), a protocol which provides support for users of MTP-3—including SCCP. Alternatively, SCCP applications can operate over the SCCP User Adaptation protocol (SUA) which is a form of modified SCCP designed specifically for use in IP networking.
SS7 protocol suite
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The Signalling Connection Control Part (SCCP) is a transport layer protocol which provides extended routing, flow control, segmentation, connection-orientation, and error correction facilities in Signaling System 7 telecommunications networks. SCCP relies on the services of MTP for basic routing and error detection.
Contents[hide]
1 Published specification
2 Routing facilities beyond MTP-3
3 Classes of service
3.1 Class 0: Basic connectionless
3.2 Class 1: Sequenced connectionless
3.3 Class 2: Basic connection-oriented
3.4 Class 3: Flow control connection oriented
4 Transport over IP Networks
5 References
6 External links
//
[edit] Published specification
The base SCCP specification is defined by the ITU-T, in recommendations Q.711 to Q.714, with additional information to implementors provided by Q.715 and Q.716. There are, however, regional variations defined by local standards bodies. In the United States, ANSI publishes its modifications to Q.713 as ANSI T1.112 or JT-Q.711 to JT-Q.714, whilst in Europe ETSI publishes ETSI EN 300 009, which documents its modifications to the ITU-T specification.
[edit] Routing facilities beyond MTP-3
Although MTP-3 provides routing capabilities based upon the Point Code, SCCP allows routing using a Point Code and Subsystem number or a Global Title.
A Point Code is used to address a particular node on the network, whilst a Subsystem number addresses a specific application available on that node. SCCP employs a process called Global Title Translation (which is similar to DNS resolution in IP networks) in order to determine Point Codes from Global Titles so as to instruct MTP-3 on where to route messages.
SCCP messages contain parameters which describe the type of addressing used, and how the message should be routed:
Address Indicator
Subsystem indicator: The address includes a Subsystem Number
Point Code indicator: The address includes a Point Code
Global title indicator
No Global Title
Global Title includes Translation Type (TT), Numbering Plan Indiciator (NPI) and Type of Number (TON)
Global Title includes Translation Type only
Routing indicator
Route using Global Title only
Route using Point Code/Subsystem number
Address Indicator Coding
Address Indicator coded as national (the Address Indicator is treated as international if not specified)
[edit] Classes of service
SCCP provides 5 classes of service to its applications:
Class 0: Basic connectionless
Class 1: Sequenced connectionless
Class 2: Basic connection-oriented
Class 3: Flow control connection oriented
Class 4: Error recovery and flow control connection oriented
The connectionless protocol classes provide the capabilities needed to transfer one Network Service Data Unit (NSDU) in the "data" field of an XUDT, LUDT or UDT message. When one connectionless message is not sufficient to convey the user data contained in one NSDU, a segmenting/reassembly function for protocol classes 0 and 1 is provided. In this case, the SCCP at the originating node or in a relay node provides segmentation of the information into multiple segments prior to transfer in the "data" field of XUDT (or as a network option LUDT) messages. At the destination node, the NSDU is reassembled.
The connection-oriented protocol classes (protocol classes 2 and 3) provide the means to set up signalling connections in order to exchange a number of related NSDUs. The connection-oriented protocol classes also provide a segmenting and reassembling capability. If an NSDU is longer than 255 octets, it is split into multiple segments at the originating node, prior to transfer in the "data" field of DT messages. Each segment is less than or equal to 255 octets. At the destination node, the NSDU is reassembled.[1]
[edit] Class 0: Basic connectionless
The SCCP Class 0 service is the most basic of SCCP transports. Network Service Data Units passed by higher layers to the SCCP in the originating node are delivered by the SCCP to higher layers in the destination node. They are transferred independently of each other. Therefore, they may be delivered to the SCCP user out-of-sequence. Thus, this protocol class corresponds to a pure connectionless network service. As a connectionless protocol, no transport-level dialog is established between the sender and the receiver.
[edit] Class 1: Sequenced connectionless
SCCP Class 1 builds on the capabilities of Class 0, with the addition of a sequence control parameter in the NSDU which allows the SCCP User to instruct the SCCP that a given stream of messages should be delivered in sequence. Therefore, Protocol Class 1 corresponds to an enhanced connectionless service with in-sequence delivery.
[edit] Class 2: Basic connection-oriented
SCCP Class 2 provides the facilities of Class 1, but also allows for an entity to establish a two-way dialog with another entity using SCCP.
[edit] Class 3: Flow control connection oriented
Class 3 service builds upon Class 2, but also allows for expedited (urgent) messages to be sent and received, and for errors in sequencing (segment re-assembly) to be detected and for SCCP to restart a connection should this occur.
[edit] Transport over IP Networks
In the SIGTRAN suite of protocols, there are two primary methods of transporting SCCP applications across Internet Protocol networks: SCCP can be transported directly using the MTP level 3 User Adaptation protocol (M3UA), a protocol which provides support for users of MTP-3—including SCCP. Alternatively, SCCP applications can operate over the SCCP User Adaptation protocol (SUA) which is a form of modified SCCP designed specifically for use in IP networking.
Camel Application Part (CAP)
Camel Application Part
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Please help improve this article or section by expanding it.Further information might be found on the talk page or at requests for expansion. (January 2007)
SS7 protocol suite
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The CAMEL Application Part (CAP) is a signalling protocol used in the Intelligent Network (IN) architecture. CAP is a Remote Operations Service Element (ROSE) user protocol, and as such is layered on top of the Transaction Capabilities Application Part (TCAP) of the SS#7 protocol suite. CAP is based on a subset of the ETSI Core and allows for the implementation of carrier-grade, value added services such as unified messaging, prepaid, fraud control and Freephone in both the GSM voice and GPRS data networks. CAMEL is a means of adding intelligent applications to mobile (rather than fixed) networks. It builds upon established practices in the fixed line telephony business that are generally classed under the heading of (Intelligent Network Application Part) or INAP CS-2 protocol.[1]
[edit] Protocol specification
The CAMEL Application Part (CAP) portable software provides mechanisms to support operator services beyond the standard GSM services for subscribers roaming within or outside the Home PLMN (HPLMN). The CAP product extends the IN framework to GSM/3G networks for implementing IN-based services within GSM/3G networks.
CAMEL is used when the subscriber is roaming between networks, allowing the home network to monitor and control calls made by the subscriber. CAMEL provides services such as prepaid roaming services, fraud control, special numbers (e.g., 123 for voicemail that works everywhere) and closed user groups (e.g., office extension numbers that work everywhere).
As with CAMEL, CAP has been defined in 4 phases, each of which has an accompanying specification that builds upon the previous phase. Each CAP phase provides the message set and procedures needed to support the corresponding CAMEL phase requirements, as defined in 3GPP TS 22.078 (service aspects) and 3GPP TS 23.078 (technical realization).
The definition of the protocol may be considered to be split into 3 sections:
the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol, defined within the prose of the specification;
the definition of the operations transferred between entities, defined using Abstract Syntax Notation One (ASN.1);
the definition of the actions taken at each entity, defined by means of state transition diagrams.
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Please help improve this article or section by expanding it.Further information might be found on the talk page or at requests for expansion. (January 2007)
SS7 protocol suite
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The CAMEL Application Part (CAP) is a signalling protocol used in the Intelligent Network (IN) architecture. CAP is a Remote Operations Service Element (ROSE) user protocol, and as such is layered on top of the Transaction Capabilities Application Part (TCAP) of the SS#7 protocol suite. CAP is based on a subset of the ETSI Core and allows for the implementation of carrier-grade, value added services such as unified messaging, prepaid, fraud control and Freephone in both the GSM voice and GPRS data networks. CAMEL is a means of adding intelligent applications to mobile (rather than fixed) networks. It builds upon established practices in the fixed line telephony business that are generally classed under the heading of (Intelligent Network Application Part) or INAP CS-2 protocol.[1]
[edit] Protocol specification
The CAMEL Application Part (CAP) portable software provides mechanisms to support operator services beyond the standard GSM services for subscribers roaming within or outside the Home PLMN (HPLMN). The CAP product extends the IN framework to GSM/3G networks for implementing IN-based services within GSM/3G networks.
CAMEL is used when the subscriber is roaming between networks, allowing the home network to monitor and control calls made by the subscriber. CAMEL provides services such as prepaid roaming services, fraud control, special numbers (e.g., 123 for voicemail that works everywhere) and closed user groups (e.g., office extension numbers that work everywhere).
As with CAMEL, CAP has been defined in 4 phases, each of which has an accompanying specification that builds upon the previous phase. Each CAP phase provides the message set and procedures needed to support the corresponding CAMEL phase requirements, as defined in 3GPP TS 22.078 (service aspects) and 3GPP TS 23.078 (technical realization).
The definition of the protocol may be considered to be split into 3 sections:
the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol, defined within the prose of the specification;
the definition of the operations transferred between entities, defined using Abstract Syntax Notation One (ASN.1);
the definition of the actions taken at each entity, defined by means of state transition diagrams.
Transaction Capabilities Application Part (TCAP)
Transaction Capabilities Application Part
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
Transaction Capabilities Application Part, from ITU-T recommendations Q.771-Q.775 or ANSI T1.114 is a protocol for Signalling System 7 networks. Its primary purpose is to facilitate multiple concurrent dialogs between the same sub-systems on the same machines, using Transaction IDs to differentiate these, similar to the way TCP ports facilitate multiplexing connections between the same IP addresses on the Internet.
TCAP is used to transport INAP in Intelligent Networks and MAP in mobile phone networks.
TCAP messages are sent over the wire between machines. TCAP primitives are sent between the application and the local TCAP stack, all TCAP messages are primitives but there are primitives that are not messages, i.e. some are only transferred inside the local machine. A TCAP primitive is made up of one or more TCAP components.
A TCAP primitive may be one of the following types:
Unidirectional
A single primitive with no subsequent primitives. Sometimes referred to as a Notice.
Begin
Start a dialog, further primitives will follow.
Continue
Send a subsequent primitive on an existing dialog, further primitives will follow.
End
The last primitive on an existing dialog, Close an existing dialog.
Abort
An error has caused the dialog to close.
Cancel
The invoke timer has expired without a response being received (this is a primitive but not a message)
A Begin primitive has an, up to 4 bytes, Originating Transaction ID, Continues also have a Destination Transaction ID, Ends and Aborts only have a Destination Transaction ID. Each primitive have both optional component and dialogue portions. Component portion for the unidirecitonal primitive is mandatory.
The dialogue portion carries dialogue or unidialogue control PDUs. For MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives. Following primitives are defined for the dialogue PDU:
AARQ
Dialogue request. For MAP and INAP, AARQ is sent in the Begin primitive with the Invoke component in general, with the application context of MAP/INAP operation's package.
AARE
Dialogue response. Sent in response to AARQ in either Continue or End primitives.
ABRT
Dialogue abort.
Each TCAP component may be one of the following types:
Invoke
A new operation is being requested, this may or may not solicit a response
Return Result Last
A final response to an Invoke
Return Result Not Last
A response to an Invoke, further responses will be sent
Return Error
An error occurred
Reject
Component is rejected for some reason like duplicate invocation, unrecognized linked id, unrecognized operation or mistyped argument
Invoke components have a signed 7 bit InvokeID which is present in all the other components to identify which invoke they relate to.
TCAP can be regarded as light weight implementation of the OSI defined ROSE, Remote Operations Services Element protocol
[edit] Transaction ID
The transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog. When machine A starts a TCAP dialog with another machine B, the machine A sends a Begin message to machine B. This Begin message contains an Originating Transaction ID, which is the Transaction ID reference for A. When the machine B replies to A with a Continue message it includes A's Transaction ID as the Destination Transaction ID. Furthermore B includes its own Transaction ID as the Originating Transaction ID.
As the TCAP dialog goes on each Continue message includes the Transaction ID of the destination machine as the Destination Transaction ID and the Transaction ID of the originating machine as the Originating Transaction ID. When any of the machines wants to close the dialog it sends an End message or an Abort message to the other machine. This message contains the Destination Transaction ID only.
[edit] Invoke ID
Invoke ID is a TCAP reference for a specific TCAP operation.
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
Transaction Capabilities Application Part, from ITU-T recommendations Q.771-Q.775 or ANSI T1.114 is a protocol for Signalling System 7 networks. Its primary purpose is to facilitate multiple concurrent dialogs between the same sub-systems on the same machines, using Transaction IDs to differentiate these, similar to the way TCP ports facilitate multiplexing connections between the same IP addresses on the Internet.
TCAP is used to transport INAP in Intelligent Networks and MAP in mobile phone networks.
TCAP messages are sent over the wire between machines. TCAP primitives are sent between the application and the local TCAP stack, all TCAP messages are primitives but there are primitives that are not messages, i.e. some are only transferred inside the local machine. A TCAP primitive is made up of one or more TCAP components.
A TCAP primitive may be one of the following types:
Unidirectional
A single primitive with no subsequent primitives. Sometimes referred to as a Notice.
Begin
Start a dialog, further primitives will follow.
Continue
Send a subsequent primitive on an existing dialog, further primitives will follow.
End
The last primitive on an existing dialog, Close an existing dialog.
Abort
An error has caused the dialog to close.
Cancel
The invoke timer has expired without a response being received (this is a primitive but not a message)
A Begin primitive has an, up to 4 bytes, Originating Transaction ID, Continues also have a Destination Transaction ID, Ends and Aborts only have a Destination Transaction ID. Each primitive have both optional component and dialogue portions. Component portion for the unidirecitonal primitive is mandatory.
The dialogue portion carries dialogue or unidialogue control PDUs. For MAP and INAP, dialogue PDU is used which performs establishment and release of dialogues for the application context provided in the primitives. Following primitives are defined for the dialogue PDU:
AARQ
Dialogue request. For MAP and INAP, AARQ is sent in the Begin primitive with the Invoke component in general, with the application context of MAP/INAP operation's package.
AARE
Dialogue response. Sent in response to AARQ in either Continue or End primitives.
ABRT
Dialogue abort.
Each TCAP component may be one of the following types:
Invoke
A new operation is being requested, this may or may not solicit a response
Return Result Last
A final response to an Invoke
Return Result Not Last
A response to an Invoke, further responses will be sent
Return Error
An error occurred
Reject
Component is rejected for some reason like duplicate invocation, unrecognized linked id, unrecognized operation or mistyped argument
Invoke components have a signed 7 bit InvokeID which is present in all the other components to identify which invoke they relate to.
TCAP can be regarded as light weight implementation of the OSI defined ROSE, Remote Operations Services Element protocol
[edit] Transaction ID
The transaction ID is a TCAP reference for a set of TCAP operations that are performed within a single dialog. When machine A starts a TCAP dialog with another machine B, the machine A sends a Begin message to machine B. This Begin message contains an Originating Transaction ID, which is the Transaction ID reference for A. When the machine B replies to A with a Continue message it includes A's Transaction ID as the Destination Transaction ID. Furthermore B includes its own Transaction ID as the Originating Transaction ID.
As the TCAP dialog goes on each Continue message includes the Transaction ID of the destination machine as the Destination Transaction ID and the Transaction ID of the originating machine as the Originating Transaction ID. When any of the machines wants to close the dialog it sends an End message or an Abort message to the other machine. This message contains the Destination Transaction ID only.
[edit] Invoke ID
Invoke ID is a TCAP reference for a specific TCAP operation.
The Mobile Application Part (MAP)
Mobile Application Part
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The Mobile Application Part (MAP) is a SS7 protocol which provides an application layer for the various nodes in GSM and UMTS mobile core networks and GPRS core networks to communicate with each other in order to provide services to mobile phone users. The Mobile Application Part is the application-layer protocol used to access the Home Location Register, Visitor Location Register, Mobile Switching Center, Equipment Identity Register, Authentication Centre, Short message service center and Serving GPRS Support Node.
Layer
Protocols
Application
INAP, MAP, IS-41...
TCAP, CAP, ISUP, ...
Transport
SCCP
Network
MTP Level 3
Data link
MTP Level 2
...
Physical
MTP Level 1
...
The Mobile Application Part (MAP) is a SS7 protocol which provides an application layer for the various nodes in GSM and UMTS mobile core networks and GPRS core networks to communicate with each other in order to provide services to mobile phone users. The Mobile Application Part is the application-layer protocol used to access the Home Location Register, Visitor Location Register, Mobile Switching Center, Equipment Identity Register, Authentication Centre, Short message service center and Serving GPRS Support Node.
Langganan:
Postingan (Atom)