Source: https://patents.google.com/patent/US7917124B2/en
Timestamp: 2019-11-22 21:25:12
Document Index: 371885181

Matched Legal Cases: ['Application No. 05425656', 'Application No. 2006220390', 'Application No. 2006236096', 'Application No. 2006236099', 'Application No. 2006233229', 'Application No. 2006220388', 'Application No. 2006220390', 'Application No. 2', 'Application No. 200610139284', 'Application No. 200619149468', 'Application No. 2006', 'Application No. 200619149468', 'Application No. 05425657', 'Application No. 05425656', 'Application No. 05425765', 'Application No. 05425764', 'Application No. 05425824', 'Application No. 05425821', 'Application No. 05425612', 'Application No. 05425657', 'Application No. 1469', 'Application No. 1490', 'Application No. 1722', 'Application No. 2006']

US7917124B2 - Third party access gateway for telecommunications services - Google Patents
Third party access gateway for telecommunications services Download PDF
US7917124B2
US7917124B2 US11/314,577 US31457705A US7917124B2 US 7917124 B2 US7917124 B2 US 7917124B2 US 31457705 A US31457705 A US 31457705A US 7917124 B2 US7917124 B2 US 7917124B2
US11/314,577
US20070067385A1 (en
Nicola Ionfrida
2005-09-20 Priority to EP05425656 priority Critical
2005-09-20 Priority to EP05425656.5 priority
2005-09-20 Priority to ITMI20051741 priority patent/ITMI20051741A1/en
2005-09-20 Priority to ITMI2005A1741 priority
2005-09-20 Priority to ITMI2005A001741 priority
2005-09-20 Priority to EP05425656.5A priority patent/EP1764971B1/en
2005-12-13 Application filed by Accenture Global Services Ltd filed Critical Accenture Global Services Ltd
2006-05-18 Assigned to ACCENTURE S.P.A reassignment ACCENTURE S.P.A ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: D'ANGELO, GIOVANNI, DONNA, MARCO, IONFRIDA, NICOLA
2006-08-02 Assigned to ACCENTURE GLOBAL SERVICES GMBH reassignment ACCENTURE GLOBAL SERVICES GMBH ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ACCENTURE S.P.A.
2007-03-22 Publication of US20070067385A1 publication Critical patent/US20070067385A1/en
2011-03-29 Publication of US7917124B2 publication Critical patent/US7917124B2/en
A telecommunications architecture exposes telecommunications services to third parties through a secure access gateway. The third parties may be other telecommunications service providers who employ the services to support their own products and services. The access gateway provides a secure, standardized, and controlled access platform for the exposed services, and addresses the technical problems associated with such access. In addition to providing technical solutions for efficient and secure access to exposed services, the architecture also provides an additional revenue channel for existing telecommunication service providers.
This application claims the priority benefit of EPO Application No. 05425656.5 filed Sep. 20, 2005, and Italian Application No. Ml2005A001741 filed Sep. 20, 2005, both of which are incorporated herein by reference in their entirety.
Establishing enhanced telecommunications service provider architectures for third party access poses significant technical challenges. As examples, there is a technical challenge in providing an architecture which provides secure and controlled access to internal functionality. Another technical challenge lies in providing a database data model architecture which efficiently flexibly supports independent authorization criteria for multiple different types of service requesters. The service requesters may vary widely, from individual end-users to company applications which issue service requests.
The elements illustrated in the Figures interoperate as explained in more detail below. Before setting forth the detailed explanation, however, it is noted that all of the discussion below, regardless of the particular implementation being described, is exemplary in nature, rather than limiting. For example, although selected aspects, features, or components of the implementations are depicted as being stored in memories, all or part of systems and methods consistent with the third party access gateway and its underlying components may be stored on, distributed across, or read from other machine-readable media, for example, secondary storage devices such as hard disks, floppy disks, and CD-ROMs; a signal received from a network; or other forms of ROM or RAM either currently known or later developed.
The products and services, and their exposed underlying functionalities, may vary between implementations. As examples, the telecommunications architecture 100 may expose SMS messaging services (to deliver and charge for an SMS message), Multimedia Messaging System (MMS) messaging services (to deliver and charge for an MMS message), and SIP services (to setup a SIP call and charge for the call). As additional examples, the telecommunications architecture 100 may expose Charge services (to request to bill a charge against an account), Internet Protocol Television (IPTV) services (to request delivery of television programming), User Status services (to request a current user status, such as ‘online’, ‘offline’, ‘busy’, or ‘away’), and user authentication services (e.g., to request verification of whether a mobile user exists and whether the mobile user has the credentials to purchase a desired service, such as IPTV service). Other functionalities may be provided in addition or as alternatives. Furthermore, the telecommunications architecture 100 and may also provide access to communication network services (e.g., Internet browsing services) through the third party access gateway 110.
TABLE 1 Company Attribute Name Attribute Description Type COMPANY_ID Unique Identifier of the Company Integer MASTERPARTYID AlphaNumeric descriptor of the String Company COMPANY_NAME Company Name String VAT_CODE Company Vat Code String FISCAL_CODE Company Fiscal Code String STATUS_ID Identifier of Company status (e.g., Integer activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 2 End User Attribute Name Attribute Description Type ENDUSER_ID Unique Identifier of the EndUser Integer MSISDN_ID Identifier of user MSISDN Integer SERVICE_PARTY_ID AlphaNumeric descriptor of the String EndUser COMPANY_ID Identifier of the Company Integer STATUS_ID Identifier of EndUser status (e.g., Integer activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 3 MSISDN Attribute Name Attribute Description Type MSISDN_ID Unique Identifier of the MSISDN Integer MSISDN MSISDN value String STATUS_ID Identifier of MSISDN status (e.g., Integer activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 4 Status Attribute Name Attribute Description Type STATUS_ID Unique Identifier of the Status Integer STATUS_NAME Name of the Status: String Activated Deactivated Suspended Idle STATUS_DESCRIPTION Description of the Status String CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 5 End user cross application Attribute Name Attribute Description Type ENDUSER_ID Unique Identifier of the EndUser Integer APPLICATION_ID Unique Identifier of the Application Integer CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 6 Company Application Attribute Name Attribute Description Type APPLICATION_ID Unique Identifier of the Integer Application APPLICATION_NAME The name of the String Application APPLICATION_DESCRIPTION The description of the String Application URL The home URL of the String Application COMPANY_ID Identifier of the Company Integer MSITE_URL_CATALOGUE The URL of Application String catalogue CERTIFICATE_ID Identifier of Application Integer certificate PROXY_HOST IP of proxy server String PROXY_PORT Port of proxy server String STATUS_ID Identifier of Application Integer status (e.g. activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 7 Installed Services Attribute Name Attribute Description Type INSTALLEDSERVICE_ID Unique Identifier of the Integer Installed Service APPLICATION_ID Identifier of the Application Integer SERVICE_ID Identifier of the subscribed Integer Service STATUS_ID Identifier of Installed Service Integer status (e.g., activated, deactivated) CREATIONDATE Creation Date Date ENDDATE Service Ending Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 8 Installed Attributes Attribute Name Attribute Description Type INSTALLEDATTRIBUTE_ID Unique Identifier of the Integer Installed Attribute ATTRIBUTE_ID Identifier of the Attribute Integer ATTRIBUTE_VALUE Name of the Attribute Integer INSTALLEDSERVICE_ID Identifier of the Installed Service STATUS_ID Identifier of Installed Integer Attribute status (e.g., activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 9 Service Attribute Attribute Name Attribute Description Type ATTRIBUTE_ID Unique Identifier of the Integer Attribute SERVICE_ID Identifier of the Service String ATTRIBUTE_NAME The name of the attribute String ATTRIBUTE_DEFAULT_VALUE The attribute default String value ATTRIBUTE_DESCRIPTION The description of the String attribute STATUS_ID Identifier of Service Integer Attribute status (e.g., activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
TABLE 10 Service Catalog Attribute Name Attribute Description Type SERVICE_ID Unique Identifier of the Integer Service SERVICE_NAME The name of the Service String SERVICE_DESCRIPTION The description of the String Service STATUS_ID Identifier of Service Catalog Integer status (e.g., activated, deactivated) CREATIONDATE Creation Date Date LASTMODIFIEDDATE Last Modified Date Date
As an example, the profiling database 228 may define an exposed SMS service. To that end, the service catalog may establish a new record with a Service_Name set to “Send SMS”. The service attribute table may then set an Attribute_Name of “Threshold”, with an Attribute_Default_Value of “100” (i.e., 100 SMS messages per month). The Attribute_Description optionally may be set to a text string which describes the Threshold. The Service Attribute table may also define a Recurring Charge attribute with an Attribute_Default_Value of $1,000 (i.e., access to the exposed service costs $1,000 per month). An associated Attribute_Description may provide a text string which describes the recurring charge.
A third party company may negotiate with the telecommunications service provider to have access to the exposed SMS message service. The terms and conditions of the access will depending on the negotiation and are supported by the data model in the profiling database 228. The profiling database 228 will establish a company record for the company, and establish a company application record linked. to the company. The installed services table may then establish an installed service record for the company application which specifies the “Send SMS” service defined in the service catalog. The default values provided in the service attribute table may be set specifically for the company in the installed attributes table. For example, the installed attributes table may define a Threshold of 10,000 SMS messages per month, and a Recurring Charge of $5,000 per month.
TABLE 11 Log Table Attribute Name Attribute Description Type OBJECT_ID Unique Identifier of the Integer Table row DATETIME The date of the event String MSISDN The MSISDN String SERVICE_PARTY_ID The Service Party ID String TRANSACTION_ID The event transaction ID String MODULE_IDENTIFIER The third party access gateway String module identifier ACTION The point where the log has String been taken ELAPSED_TIME The time elapsed in each action Integer APPLICATION_NAME The name of the Application String COMPANY_NAME The name of the Company String APPLICATION_URL The home application URL String REQUESTED_URL The requested URL String ERROR_CODE The error code String
TABLE 12 Company Attribute Name Attribute Description Type OBJECT_ID Unique Identifier of the Integer Table row DATETIME The date of the event String TRANSACTION_ID The event transaction ID String MODULE_IDENTIFIER The third party access gateway String module identifier APPLICATION_NAME The name of the Application String COMPANY_NAME The name of the Company String BRICK_NAME The Name of a wrapper applied String to the request ACTION The point where the log has String been taken MSISDN_QUANTITY The quantity of MSISDN sent String ERROR_CODE The error code String TRANSACTION_RESULT The transaction result String MESSAGE_VOLUME_KB The amount of data transferred Integer ARTICLE_ID The article ID for payment String transactions ASSET_CREATION_DATE The creation date of the asset Date requested ARTICLE_PRICE The article price String CURRENCY The article currency String ARTICLE_PRICE_BAND The article price band String INVOICE_TEXT The invoice text String ASSET_QUANTITY The number of assets Integer requested
As noted above, the exposed service interface 412 may wrap the request to a standard form for the service broker 116. FIG. 10 shows an example of a wrapped SMS message 1000. The SMS wrapper 414 maps the transaction identifier field 902 to the transaction identifier field 1002, adds a transaction label field 1004 which may specify the message type (e.g., “SMSDELIVERY” for SMS messages); and maps the message type field 904 to the service type field 1006, while dropping the SMS version field 906. Similarly, the SMS wrapper 414 maps the addressing fields 910-914 to the To Address field 1010, CC Address field 1012, and BCC address field 1014, and also maps the service code field 916 to the service identifier field 1016.
Table 13 shows an example implementation of a wrapped XML SMS request message with field values derived from the request message shown in FIG. 9. The wrapped message adds a label field (set to “SMSDELIVERY” for SMS messages).
TABLE 13 <?xml version=“1.0” encoding=“ISO-8859-1” ?> <TSOheader TSOID=“12345” TSOlabel=“SMSDELIVERY” /> <TSOattributes> <attribute name=“SERVICE_TYPE” value=“SMS” /> <attribute name=“SENDERADDRESS” value=“M-Site” /> <attribute name=“SERVICEID” value=“55555” /> <attribute name=“STARTDATE” value=“05/05/2004” /> <attribute name=“ENDDATE” value=“10/05/2004” /> <attribute name=“PRIORITY” value=“High” /> <attribute name=“SUBJECT” value=“Message” /> <attribute name=“ACCOUNTID” value=“77777” /> <attribute name=“MESSAGE_BODY” value=“This is the SMS message.” /> <attribute name=“CHARGE_FLAG” value=“1” /> <list name=“TO_ADDRESSEE” value=“3”> <attribute name=“1” value=“+39xxxx” /> <attribute name=“2” value=“+39xxxx” /> <attribute name=“3” value=“+39xxxx” /> </list> <list name=“CC_ADDRESSEE” value=“4”> <attribute name=“1” value=“+39xxxx” /> <attribute name=“2” value=“+39xxxx” /> <attribute name=“3” value=“+39xxxx” /> <attribute name=“4” value=“+39xxxx” /> </list> <list name=“BCC_ADDRESSEE” value=“3”> <attribute name=“1” value=“+39xxxx” /> <attribute name=“2” value=“+39xxxx” /> <attribute name=“3” value=“+39xxxx” /> </list> </TSOattributes> </TSO_DATA>
TABLE 14 <?xml version=“1.0” encoding=“ISO-8859-1” ?> <TSOheader TSOID=“12345” TSOlabel=“SMSDELIVERY” /> <TSOresult> <statusCode>0</statusCode> <errorCode></errorCode> <errorDescription></errorDescription> </TSOresult> </TSO_DATA>
The SMS wrapper 414 maps information from the response 1100 to the wrapped response 1200, including a transaction identifier field 1202, status field 1204, error code field 1206, and error description field 1208. The wrapped response 1200 also adds a message type field 1210 (e.g., set to “<SMS>” or another value expected by the requesting application), and an SMS version field 1221 which reports the applicable SMS version to the requesting application. The transaction label field 1104 may be dropped.
FIG. 13 shows a mapping from an MMS exposed service request 1302 to a wrapped MMS service request 1304. The TSOLABEL may be set to “MMSDelivery” or any other identifier. An application may issue the MMS service request to deliver multimedia content to any specified recipient. FIG. 14 shows a mapping from an MMS exposed service response 1402 to a wrapped MMS service response 1404.
FIG. 15 shows a mapping from an SIP exposed service request 1502 to a wrapped SIP service request 1504. The TSOLABEL may be set to “SIPCall” or any other identifier. A requesting application may initiate a SIP request to establish a communication channel between a sender and a receiver specified in the SIP request 1502. FIG. 16 shows a mapping from a SIP exposed service response 1602 to a wrapped SIP service response 1604. The TSOLABEL field may be dropped.
FIG. 17 shows a mapping from a Status exposed service request 1702 to a wrapped Status service request 1704. The TSOLABEL may be set to “GetUserStatus” or any other identifier. A requesting application may issue the Status request to check the status of one or more users listed in the status request 1702. The Status request 1702 may further include provider identifiers to request status with respect to specific service providers. FIG. 18 shows a mapping from a Status response 1802 to a wrapped Status service response 1804.
FIG. 19 shows a mapping from an Authentication exposed service request 1902 to a wrapped Authentication service request 1904. The TSOLABEL may be set to “Authentication” or any other identifier. A requesting application may issue the authentication request 1902 in order to ask for authentication of an MSISDN with respect to a particular service and provider. FIG. 20 shows a mapping from a Status exposed service response 2002 to a wrapped Status service response 2004. The response may include a wide range of status information, such as service status (e.g., “ok”, or “disconnected”), customer type (e.g., “commercial” or “residential”), identification information for the customer's service plan, SIM module, wireless device type, capability to send or receive MMS, UMTS, or GPRS messages, the access channel (e.g., “mobile” or “landline”), or any other status information available for the MSISDN.
FIG. 21 shows a mapping from a Charge exposed service request 2102 to a wrapped Charge service request 2104. The TSOLABEL may be set to “Charge” or any other identifier. A requesting application may initiate a charge request to request billing for a communication session with the specified begin and end date between two endpoints (e.g., between a sender URI and a receiver URI) and handled by the a service provider specified in the Charge request 2102. FIG. 22 shows a mapping from a Charge exposed service response 2202 to a wrapped Charge service response 2204. The TSOLABEL field may be dropped in the response.
Table 15 shows an example of a WSDL definition for an exposed service. In particular, Table 15 shows an example WSDL Charge service descriptor which may define input and output messages and the message format for an exposed service. The Charge service descriptor defines a <port> (“ChargeAdapterFrontEnd”) through which the Charge service requests and responses are sent as defined by the input and output messages. Furthermore, the Charge service descriptor defines the message form and content for the input and output messages (“submitReqRequest”, and “submitReqResponse”, respectively). A SOAP binding is also defined, as is the location to which the Charge exposed service requests are sent (via the “location” specifier).
TABLE 15 <?xml version=“1.0” encoding=“UTF-8”?> <wsdl:definitions targetNamespace=“http://[address]” xmlns=“http://schemas.xmlsoap.org/wsdl/” xmlns:apachesoap=“http://xml.apache.org/xml-soap” xmlns:impl=“http://[address]” xmlns:intf=“http://[address]” xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/” xmlns:tns2=“http://[address]” xmlns:tns3=“http://[address]” xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/” xmlns:wsdlsoap=“http://schemas.xmlsoap.org/wsdl/soap/” xmlns:xsd=“http://www.w3.org/2001/XMLSchema”> <wsdl:types> <schema targetNamespace=“http://[address]” xmlns=“http://www.w3.org/2001/XMLSchema”> <import namespace=“http://schemas.xmlsoap.org/soap/encoding/”/> <complexType name=“WrappedRequest”> <sequence> <element name=“certId” nillable=“true” type=“xsd:int”/> <element name=“transactionId” nillable=“true” type=“xsd:string”/> </sequence> </complexType> <complexType name=“Status”> <sequence> <element name=“details” nillable=“true” type=“xsd:string”/> <element name=“statusCode” type=“xsd:int”/> <element name=“statusText” nillable=“true” type=“xsd:string”/> </sequence> </complexType> <complexType name=“WrappedResponse”> <sequence> <element name=“status” nillable=“true” type=“tns3:Status”/> <element name=“transactionId” nillable=“true” type=“xsd:string”/> </sequence> </complexType> </schema> <schema targetNamespace=“http://[address]” xmlns=“http://www.w3.org/2001/XMLSchema”> <import namespace=“http://schemas.xmlsoap.org/soap/encoding/”/> <complexType name=“ChargeWrappedRequest”> <complexContent> <extension base=“tns3:WrappedRequest”> <sequence> <element name=“accountID” nillable=“true” type=“xsd:string”/> <element name=“endDate” nillable=“true” type=“xsd:dateTime”/> <element name=“serviceID” nillable=“true” type=“xsd:string”/> <element name=“startDate” nillable=“true” type=“xsd:dateTime”/> </sequence> </extension> </complexContent> </complexType> <complexType name=“ChargeWrappedResponse”> <complexContent> <extension base=“tns3:WrappedResponse”> <sequence/> </extension> </complexContent> </complexType> </schema> </wsdl:types> <wsdl:message name=“submitReqRequest”> <wsdl:part name=“chargeWrappedRequest” type=“tns2:ChargeWrappedRequest”/> </wsdl:message> <wsdl:message name=“submitReqResponse”> <wsdl:part name=“submitReqReturn” type=“tns2:ChargeWrapped Response”/> </wsdl:message> <wsdl:portType name=“ChargeAdapterFrontEnd”> <wsdl:operation name=“submitReq” parameterOrder=“chargeWrappedRequest”> <wsdl:input message=“intf:submitReqRequest” name=“submitReqRequest”/> <wsdl:output message=“intf:submitReqResponse” name=“submitReqResponse”/> </wsdl:operation> </wsdl:portType> <wsdl:binding name=“ChargeAdapterFrontEndSoapBinding” type=“intf:ChargeAdapterFrontEnd”> <wsdlsoap:binding style=“rpc” transport=“http://schemas.xmlsoap.org/soap/http”/> <wsdl:operation name=“submitReq”> <wsdlsoap:operation soapAction=“”/> <wsdl:input name=“submitReqRequest”> <wsdlsoap:body encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/” namespace=“http://[address]” use=“encoded”/> </wsdl:input> <wsdl:output name=“submitReqResponse”> <wsdlsoap:body encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/” namespace=“http://[address]” use=“encoded”/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name=“ChargeAdapterFrontEndService”> <wsdl:port binding=“intf:ChargeAdapterFrontEndSoapBinding” name=“ChargeAdapterFrontEnd”> <wsdlsoap:address location=“http://localhost:8080/serverfinto/services/SdcCharge”/> </wsdl:port> </wsdl:service> </wsdl:definitions>
US11/314,577 2005-09-20 2005-12-13 Third party access gateway for telecommunications services Active 2027-01-22 US7917124B2 (en)
ITMI20051741 ITMI20051741A1 (en) 2005-09-20 2005-09-20 Access door to third parties for telecommunications services
ITMI2005A1741 2005-09-20
ITMI2005A001741 2005-09-20
EP05425656.5A EP1764971B1 (en) 2005-09-20 2005-09-20 Third party access gateway for telecommunications services
EP05425656 2005-09-20
EP05425656.5 2005-09-20
US20070067385A1 US20070067385A1 (en) 2007-03-22
US7917124B2 true US7917124B2 (en) 2011-03-29
ID=37885470
US11/314,577 Active 2027-01-22 US7917124B2 (en) 2005-09-20 2005-12-13 Third party access gateway for telecommunications services
US (1) US7917124B2 (en)
JP (1) JP4526526B2 (en)
AU (1) AU2006220388B2 (en)
CA (1) CA2559647C (en)
HK (1) HK1102042A1 (en)
EP2648364A2 (en) 2012-03-07 2013-10-09 Accenture Global Services Limited Communication collaboration
US9967203B2 (en) * 2016-08-08 2018-05-08 Satori Worldwide, Llc Access control for message channels in a messaging system
ITMI20051742A1 (en) * 2005-09-20 2007-03-21 Accenture Global Services Gmbh Architecture authentication and authorization for an access door
JP2008097510A (en) * 2006-10-16 2008-04-24 Konica Minolta Business Technologies Inc Network system, service retrieving method and image forming apparatus
TWI366384B (en) * 2007-03-30 2012-06-11 Ibm Sms wrapper/dewrapper and mobile devices embedded with the sms wrapper/dewrapper
ES2310123B1 (en) * 2007-05-07 2009-11-05 Vodafone España, S.A. Remote access from an extension of a web browser to the information of a mobile terminal.
ES2333633B1 (en) * 2007-05-07 2011-02-10 Vodafone España, S.A. Access from a remote terminal to the information of a mobile terminal.
CN101056208B (en) * 2007-05-31 2010-06-02 华为技术有限公司 Service tracking method, network device, O&M controller, and service request device
CN101990183B (en) * 2009-07-31 2013-10-02 国际商业机器公司 Method, device and system for protecting user information
EP2572498A4 (en) * 2010-05-18 2013-10-02 Certicall Llc Certified communications system and method
US8358745B2 (en) 2011-02-09 2013-01-22 Certicall, Llc Recording identity data to enable on demand services in a communications system
US8457601B2 (en) 2011-02-09 2013-06-04 Certicall, Llc Key responsive record, navigation and marking controls for communications system
CN103634365A (en) * 2012-08-29 2014-03-12 中兴通讯股份有限公司 Third party application platform in wireless access network and communication method thereof
US9854066B1 (en) 2013-02-05 2017-12-26 Amdocs Software Systems Limited System, method, and computer program for customizing a response to a request
WO2015191603A1 (en) * 2014-06-09 2015-12-17 Exosite LLC Gateway-facilitated communications for resource-constrained devices
JPH11219340A (en) 1998-02-04 1999-08-10 Mitsubishi Electric Corp Device and system for authentication management
EP0980175A2 (en) 1998-08-10 2000-02-16 Robert Bosch Gmbh Method for displaying data of called subscribers
EP1052841A2 (en) 1999-05-12 2000-11-15 Motorola Ireland Limited System and method for billing in a radio telecommunications network
JP2001224000A (en) 2000-02-07 2001-08-17 Matsushita Electric Ind Co Ltd Multi-spots tv conference system
US20020156874A1 (en) 2001-04-20 2002-10-24 Suorsa Raymond E. Automated provisioning of computing networks according to customer accounts using a network database data model
US20030065777A1 (en) 2001-10-03 2003-04-03 Nokia Corporation System and method for controlling access to downloadable resources
JP2004070733A (en) 2002-08-07 2004-03-04 Ntt Docomo Inc Authentication system, authentication method, authentication program, and computer-readable storage medium
US20040133486A1 (en) 2001-02-19 2004-07-08 Outi Markki Control of billing in a communications system
US20040153404A1 (en) 2003-01-31 2004-08-05 Joern Rischmueller Convergent invoicing system and method
JP2004260240A (en) 2003-02-24 2004-09-16 Nec Corp Mobile phone
JP2004266310A (en) 2003-01-14 2004-09-24 Matsushita Electric Ind Co Ltd Service and address management method in wlan interconnetion
JP2004297138A (en) 2003-03-25 2004-10-21 Ntt Docomo Inc Authentication system and communication terminal
WO2004102396A1 (en) 2003-05-14 2004-11-25 Fujitsu Limited Delay storage device and delaying method
JP2004362061A (en) 2003-06-02 2004-12-24 Ddi Pocket Inc Terminal identification system, method and program
JP2005004248A (en) 2003-06-09 2005-01-06 Kddi Corp Communication terminal, system and method for authentication
JP2005039317A (en) 2003-07-15 2005-02-10 Kddi Corp Network relaying system, relaying apparatus, and user terminal
US20050037752A1 (en) 2003-08-12 2005-02-17 Arvie Kwan Telecommunications subscriber profile management system
JP2005510328A (en) 2001-12-05 2005-04-21 アセプティカ インコーポレイテッド Antimicrobial system and method
US20050091370A1 (en) 2003-06-06 2005-04-28 Siemens Aktiengesellschaft Method for monitoring data transmissions
US20050149724A1 (en) 2003-12-30 2005-07-07 Nokia Inc. System and method for authenticating a terminal based upon a position of the terminal within an organization
US20050160135A1 (en) 2004-01-15 2005-07-21 Atsushiro Yokoro Method and system for managing programs for distributed processing systems
US20050165930A1 (en) 2003-12-19 2005-07-28 Whitman Raymond Jr. Resource assignment in a distributed environment
US20050223064A1 (en) 2004-04-01 2005-10-06 Robert Salerno Method and system for electronic message retraction
US20060047709A1 (en) 2001-09-05 2006-03-02 Belin Sven J Technology independent information management
US20060101474A1 (en) 2004-11-08 2006-05-11 Bruce Magown System, method and apparatus for an extensible distributed enterprise integration platform
US7140025B1 (en) 1999-11-16 2006-11-21 Mci, Llc Method and apparatus for providing a real-time message routing communications manager
US20070240046A1 (en) 2001-11-20 2007-10-11 Heung-Wah Yan Method and apparatus for controlling view navigation in workflow systems
US20080077680A1 (en) 2006-08-31 2008-03-27 Accenture SAS (Dellarole) Service provisioning and activation engines for system
DE69711179D1 (en) * 1996-05-28 2002-04-25 Lonza Ag Visp Wood preservatives
AU2003294304B2 (en) * 2002-11-18 2010-04-15 Liquidware Labs, Inc. Systems and apparatuses using identification data in network communication
2005-12-13 US US11/314,577 patent/US7917124B2/en active Active
2006-09-13 CA CA 2559647 patent/CA2559647C/en active Active
2006-09-19 AU AU2006220388A patent/AU2006220388B2/en active Active
2006-09-20 JP JP2006284334A patent/JP4526526B2/en active Active
2007-09-10 HK HK07109812A patent/HK1102042A1/en unknown
US7222088B2 (en) 2000-11-02 2007-05-22 Hitachi, Ltd. Service system
JP2003060714A (en) 2001-05-09 2003-02-28 Docomo Communications Laboratories Usa Inc Method for providing customized service
US20050228906A1 (en) 2003-05-14 2005-10-13 Fujitsu Limited Delay storage device and delay treating method
JP2005202631A (en) 2004-01-15 2005-07-28 Hitachi Ltd Constitution method of processing request queue for program component, registration method and execution control method for program component, registaration program and execution control program for program component, and application server
Anonymous, "3GPP; Technical Specification Group Services and System Aspects; Presence Service; Architecture and Functional Description," 3GPP TS 23.141 V6.0.0, Oct. 2002, 31 pages.
Australian First Examination Report dated Jan. 3, 2008 for co-pending Australian Patent Application No. 2006220390.
Australian Official Report, mailed Dec. 12, 2007, for co-pending Australian Patent Application No. 2006236096.
Australian Official Report, mailed Dec. 17, 2007, for co-pending Australian Patent Application No. 2006236099.
Australian Official Report, mailed Jan. 31, 2008, for co-pending Australian Patent Application No. 2006233229.
Australian Official Report, mailed Oct. 26, 2007, for co-pending Australian Patent Application No. 2006220388.
Australian Second Examination Report dated Aug. 31, 2009 for co-pending Australian Patent Application No. 2006220390.
Canadian Office Action, dated Aug. 4, 2010, for co-pending Canadian Patent Application No. 2,559,647, 5 pages.
Chinese First Office Action dated Jul. 8, 2004, for co-pending Chinese Patent Application No. 200610139284.8.
Chinese Office Action, mailed Mar. 13, 2009, for co-pending Chinese Patent Application No. 200619149468.2.
Dr. Bert Dempsey and Dr. Matthew Lucas, "IPDR Update: Standards Effort Moves From Usage to Provisioning", pp. 44-48, TelOSSource Magazine, Apr. 2000.
Droms, "Dynamic Host Configuration Protocol," Oct. 2003, available from http://www.ietf.org/rfc/rfc1541.txt, 40 pages.
English translation of Japanese Office Action, Dispatch Date Jan. 25, 2010, 2 pgs.
English translation of Japanese Official Action dated Apr. 6, 2009 for co-pending Japanese Patent Application No. 2006-319265.
English Translation of the Chinese Office Action, mailed Mar. 13, 2009, for co-pending Chinese Patent Application No. 200619149468.2.
EPO Examination Report, dated May 10, 2006, EP Pat. App. No. 05425824.9.
EPO Examination Report, dated May 19, 2006, EP Pat. App. No. 05425821.5.
European Patent Office Extended Search Report dated Mar. 14, 2006 for co-pending European Patent Office Application No. 05425657.
European Patent Office Search Report dated Feb. 14, 2006 for co-pending European Patent Office Application No. 05425656.5.
European Patent Office Search Report dated Jan. 2, 2006 for co-pending European Patent Office Application No. 05425765.
European Patent Office Search Report dated May 10, 2006 for co-pending European Patent Office Application No. 05425764.7.
European Patent Office Search Report dated May 10, 2006 for co-pending European Patent Office Application No. 05425824.9.
European Patent Office Search Report dated May 12, 2006 for co-pending European Patent Office Application No. 05425821.5.
European Patent Office Search Report dated Nov. 10, 2005 for co-pending European Patent Office Application No. 05425612.
Extended European Search Report, dated Oct. 8, 2010, for co-pending European Patent Application No. 05425657.3, 4 pages.
Indian Examination Report, dated Sep. 29, 2008, Indian Pat. App. No. 1722/MUM/2006.
Indian First Examination Report dated Oct. 17, 2008 for co-pending Indian Patent Application No. 1469/MUM/2006.
Indian First Examination Report dated Sep. 11, 2008 for co-pending Indian Patent Application No. 1490/MUM/2006.
Indian First Examination Report dated Sep. 29, 2008 for co-pending Indian Patent Application No. 1722/MUM/2006.
Japanese Final Official Action dated Apr. 6, 2009 for co-pending Japanese Patent Application No. 2006-319265.
Japanese Office Action for JP-2006-284333, Dispatch Date Jun. 28, 2010, with English translation, 30 pgs.
Japanese Office Action, Dispatch Date Jan. 25, 2010, 3 pgs.
Livingston et al., "Remote Authentication Dial in User Service (Radius)," Radius Working Group, Internet-Draft, Feb. 2000, 80 pages.
Michel L.F. Grech et al., "Delivering Searmless Services in Open Networks Using Intelligent Service Mediaton", pp. 186-202, Bell Labs Technical Journal, Jul.-Sep. 2000.
Nokia "Parameters in Subscriber Certificate and Subscriber Profile Supporting Operator Control and Service Differentiation", 4pp., 3GPP TSG SA WG 3 Security, Feb. 25-28, 2003, Sophia Antipolis, France.
Notice of Allowance, mailed Nov. 12, 2009, for commonly owned U.S. Appl. No. 11/314,576.
Office Action, mailed Apr. 2, 2009, for commonly owned U.S. Appl. No. 11/314,576.
Office Action, mailed Apr. 28, 2009, for commonly owned U.S. Appl. No. 11/400,249.
Office Action, mailed Aug. 20, 2010, for commonly owned U.S. Appl. No. 11/313,497.
Office Action, mailed Dec. 18, 2009, for commonly owned U.S. Appl. No. 11/313,441.
Office Action, mailed Jan. 23, 2009, for commonly owned U.S. Appl. No. 11/313,463.
Office Action, mailed Jun. 2, 2009, for commonly owned U.S. Appl. No. 11/313,441.
Office Action, mailed Jun. 22, 2010, for commonly owned U.S. Appl. No. 11/313,497.
Office Action, mailed Jun. 23, 2010, for commonly owned U.S. Appl. No. 11/585,612.
Office Action, mailed Nov. 13, 2009, for commonly owned U.S. Appl. No. 11/400,249.
Office Action, mailed Nov. 9, 2009, for commonly owned U.S. Appl. No. 11/313,497.
Opencon, "White Paper on Billing for the New Public Network", pp. 1-5, OpenCon Systems, Inc., www.opencon.com, 2000.
Silver et al., "Unified Network Presence Management," White Paper Nortel Networks, 2000, 6 pages.
Sun Microsystems, Chapter 8, Authentication Options, Sun Java System Access Manager 6 2005Q1 Adminstration Guide, Sun Microsystems, pp. 1-25, Mar. 2005.
The Parlay Group, Inc., The Parlay Goup: Web Services Working Group, "Parlay Web Services Application Deployment Infrastructure", pp. 1-21, Version 1.0, Oct. 31, 2002.
The prosecution history of commonly owned U.S. Appl. No. 11/399,780 shown in the attached Patent Application Retrieval file wrapper document list, including each substantive office action and applicant response, if any, printed Jan. 5, 2010.
The prosecution history of U.S. Appl. No. 11/313,441 shown in the attached Patent Application Retrieval file wrapper document list, printed Nov. 13, 2008.
The prosecution history of U.S. Appl. No. 11/313,496 shown in the attached Patent Application Retrieval file wrapper document list, printed Nov. 13, 2008, including each substantive Office Action.
The prosecution history of U.S. Appl. No. 11/313,497 shown in the attached Patent Application Retrieval file wrapper document list, printed Nov. 13, 2008.
The prosecution history of U.S. Appl. No. 11/314,576 shown in the attached Patent Application Retrieval file wrapper document list, printed Nov. 13, 2008.
The prosecution history of U.S. Appl. No. 11/585,612 shown in the attached Patent Application Information Retrieval file wrapper document list, printed Nov. 3, 2010, including each substantive office action.
The prosecution history of U.S. Appl. No.11/313,463 shown in the attached Patent Application Retrieval file wrapper document list, printed Nov. 13, 2008.
Translation of Japanese Examination Report, dated Sep. 16, 2008, Japanese Pat. App. No. 2006-319265.
US10389674B2 (en) 2015-10-09 2019-08-20 Satori Worldwide, Llc Systems and methods for storing and transferring message data
US10382574B2 (en) 2016-09-23 2019-08-13 Satori Worldwide, Llc Systems and methods for providing messages to multiple subscribers
CA2559647A1 (en) 2007-03-20
CA2559647C (en) 2012-07-10
HK1102042A1 (en) 2011-08-05
JP4526526B2 (en) 2010-08-18
JP2007089200A (en) 2007-04-05
AU2006220388B2 (en) 2009-01-08
US20070067385A1 (en) 2007-03-22
AU2006220388A1 (en) 2007-04-05
US7912067B2 (en) 2011-03-22 Clearinghouse server for internet telephony and multimedia communications
US9197599B1 (en) 2015-11-24 Integrated business system for web based telecommunications management
US9805090B1 (en) 2017-10-31 System and method for processing database queries
US9479908B2 (en) 2016-10-25 Short message service protocol gateway
Owner name: ACCENTURE S.P.A, ITALY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:D'ANGELO, GIOVANNI;DONNA, MARCO;IONFRIDA, NICOLA;REEL/FRAME:017638/0602