Source: http://www.google.com/patents/US7979519?dq=6,247,130
Timestamp: 2014-10-23 21:32:31
Document Index: 694085161

Matched Legal Cases: ['art 226', 'art 228', 'art 228', 'art 228', 'art 54', 'art 212', 'art 210', 'art 212', 'art 212', 'art 214', 'art 214', 'art 210', 'art 224', 'art 224', 'art 224', 'art 210', 'art 224', 'art 210', 'art 226', 'art 226', 'art 226', 'art 226', 'art 234', 'art 234', 'art 210', 'art 210', 'art 226', 'art 234', 'art 226', 'art 226', 'art 236', 'art 236', 'art 220', 'art 236', 'art 226', 'art 236', 'art 226', 'art 226', 'art 236', 'art 236', 'art 220', 'art 210', 'art 210', 'art 220', 'art 220', 'art 236', 'art 226', 'art 226']

Patent US7979519 - System for providing information between different protocol environments ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsThe service providing system uses cooperation managers both in SIP and Web systems to process information of the SIP and HTTP protocols with SOAP/CORBA and the like as a communication protocol that can be handled in common. The service providing system thereby facilitates cooperation between the SIP...http://www.google.com/patents/US7979519?utm_source=gb-gplus-sharePatent US7979519 - System for providing information between different protocol environments cooperative with each other and a method thereforAdvanced Patent SearchPublication numberUS7979519 B2Publication typeGrantApplication numberUS 10/959,586Publication dateJul 12, 2011Filing dateOct 7, 2004Priority dateOct 9, 2003Also published asCN1606311A, CN100571257C, US20050091362Publication number10959586, 959586, US 7979519 B2, US 7979519B2, US-B2-7979519, US7979519 B2, US7979519B2InventorsYoshiaki Shigeta, Shinya ItoOriginal AssigneeOki Electric Industry Co., Ltd.Export CitationBiBTeX, EndNote, RefManPatent Citations (21), Non-Patent Citations (3), Referenced by (39), Classifications (21), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetSystem for providing information between different protocol environments cooperative with each other and a method thereforUS 7979519 B2Abstract The service providing system uses cooperation managers both in SIP and Web systems to process information of the SIP and HTTP protocols with SOAP/CORBA and the like as a communication protocol that can be handled in common. The service providing system thereby facilitates cooperation between the SIP and Web systems through the SPAP/CORBA network, thereby accomplishing information transfer on a real time basis.
CROSS-REFERENCES TO RELATED APPLICATIONS This application is related to U.S. application Ser. No. 10/959,580 filed on Oct. 7, 2004 and to U.S. application Ser. No. 10/921,343 filed on Aug. 19, 2004.
SUMMARY OF THE INVENTION It is an object of the present invention to eliminate the disadvantages in the prior art, and to provide an information providing system capable of making applications built on environments different in protocol cooperate with each other to operate applications on a real time basis.
DESCRIPTION OF THE PREFERRED EMBODIMENTS In the following, preferred embodiments of an information providing system in accordance with the invention will be described in more detail in reference with the accompanying drawings. Referring first to FIG. 1, an illustrative embodiment of an information providing system in accordance with the invention solves the problem of extensibility of applications involved by using a conventional HTTP-SIP conversion gateway or by an access made by a client itself to SIP and web servers, as well as uses a configuration and a method capable of building flexible cooperation between the SIP and Web applications to enable a client to use the services of both SIP and Web applications by simply accessing either to the SIP or Web environment. Description will be omitted on portions not directly relevant to the invention. In the following description, signals are denoted with reference numerals of respective connections on which they appear.
For example, a browser 68 issues at time T130 a request for execution of �service generation� (Service Generation Request Signal: Gen.REQ.). Here, the requested information includes requesting information, such as retrieving information, message information to be transmitted, as well as user information. The user information includes information concerning contracts, such as user's names, addresses, ages, etc., and those used for certification or authentication at the time of using information systems. In general, this request is issued using a GUI (Graphical User Interface) provided by the Web server 32 displayed on the Web browser 68. A service generation request signal is sent out to the Web server 32/Web-AP server 36.
The Web server 32/Web-AP server 36, based on the �service generation request� thus supplied, uses the component AP interface 78 in the proxy UA management part 226 on the Web side to supply at time T132 a start up signal (Launching) 302 to the proxy UA generation accessing function part 228 in order to start up the proxy UA generation accessing function part 228. The proxy UA generation accessing function part 228 supplies at time T134 a start-up signal (Launching) 304 to the cooperation management section 66 to start it.
The cooperation management section 66, in order to transmit information to the proxy UA management part 54 in the SIP system 12, converts the �service generation request� data to match with a communication protocol possible to be commonly used, for example, SOAP or CORBA and communicates with the cooperation management section 54 on the SIP system 12 side present in a separate domain on the network 16. The cooperation management section 66 communicates at time T136 with the cooperation management section 54 to transmit the �service generation request� (Gen. REQ.) issued from the Web browser 68.
The cooperation management section 54 supplies at time T138 a start up signal (Launching) 308 containing the �service generating request� to the proxy UA generating function part 212 of the proxy UA management part 210 to start up the proxy UA generating function part 212, whereby a proxy UA is generated. The proxy UA generating function part 212 starts up the proxy UA registering function part 214 (not shown). The proxy UA registering function part 214 registers at time T140 the service proxy UA in the SIP database 20 managed by the SIP-AP server 22 or the SIP server 18 (Registration 310). With this registration, the Web browser 68 can provide certification for use of the systems.
After the registration, the proxy UA management part 210, when retrieval information is contained in the information included in �service generation request�, not shown in the figure, starts up the proxy UA information retrieving function part 224. The proxy UA information retrieving function part 224 instructs a retrieving process (Search 312 at T142) for the retrieving information to the SIP database 20. The SIP database 20 executes the retrieving process according to the supplied retrieving information. The SIP database 20 transmits at time T144 the retrieved result to the proxy UA information retrieving function part 224 of the proxy management part 210 as a response signal (Response). The retrieved result is URI information (Uniform Resource Identifier) generated in the SIP protocol.
The proxy UA information retrieving function part 224 receives the retrieved result and generates a start up signal (Launching) 316 containing the retrieved result (Generated SIP-URI Information) to deliver it to the cooperation management section 54. The cooperation management section 54 is started up by the start-up signal 316 and answers the retrieved result (Generated SIP-URI Information) to the proxy UA management section 66. For this, the cooperation management part 210 uses SOAP or CORBA to communicate with the cooperation management section 66. When the cooperation management section 54 uses, for example, SOAP, the retrieving information supplied based on the HTTP protocol is delivered at time T148 as a response signal (Response), a SOAP response, to the cooperation management section 66 through the network 16. The cooperation management section 66 receives the supplied retrieving information and transmits at time T150 the result of �service generation request� to the proxy UA management part 226 (Response 320).
Subsequently, the proxy UA management part 226 receives the result of the received �service generation request� and sends it out as the executed result of the component application interface 56 back to the Web server 32 or the Web-AP server 36 at time T152 (Response 322). The executed result is the data of user information obtained from the retrieval on the afore-described SIP database.
The Web server 32 or the Web-AP server 36 processes the retried result of the user information, i.e. The generated SIP-URI information into a form available to be displayed by the Web client. In this case, it is processed into data in the SIP-URI form. The Web server 32 or the Web-AP server 36 delivers at time T154 the said data as the service SIP-URI 324 to the Web browser 68. The Web browser 68 displays at time T156 the result of �service generation request� on the monitor.
The Web browser 68 issues at time T160 an execution request for �service presence setting� to the Web server 32/Web-AP server 36. This execution request means to specify SIP-URI, which includes user information as well. The user information includes, as described above, the users' names, addresses and age concerning contracts and information for certification or authentication in use of systems. The information of the service presence setting request includes, for example, �standby for execution�, �in processing�, �termination�, etc., as the content representing the service status. The request is generally executed using GUI supplied form the Web server 32 displayed on the Web browser 68.
The Web server 32/Web-AP server 36 supplies at time T162 a start up signal (Launching) 332 generated based on �service presence setting request� (Set_REQ) 330 to the proxy UA management part 226. The proxy UA management part 226 uses the component AP interface 78 based on the �service presence setting request� (Set_REQ) 330 contained in a start up signal (Launching) 332 to start up the presence setting accessing function part 234, whereby the presence setting accessing function part 234 supplies at time T164 a start up signal (Launching) 334 to the cooperation management section 66 and starts up.
The cooperation management section 66, in order to transmit information to the proxy UA management part 210, uses SOAP or CORBA to communicate at time T166 with the cooperation management section 54 present within another domain on the network 16. By means of that communication, the cooperation management section 54 receives the �service presence setting request� (Set_REQ) 336 issued from the Web browser 68.
The proxy UA management part 210 supplies at time T176 a start up signal (Launching) 348 containing the retrieved result to the cooperation management section 54 to start it up. The cooperation management section 54 uses SOAP or CORBA to communicate (Response 350) at time T178 with the cooperation management section 66. The cooperation management section 66 supplies at time T180 a response signal (Response) 352 to the proxy UA management part 226. The response signal 352 contains the result of �presence setting request� and is transmitted as the result of NG (no good) when the setting fails. The presence setting accessing function part 234 of the proxy UA management part 226 receives the response signal 352 as the result of �service presence setting request�.
The proxy UA management part 226 supplies at time T182 the executed result of the component AP interface 78 to the Web server 32/Web-AP server 36 (Response 354). The executed result represents the data of user information obtained by retrieval in the SIP database 20. The Web server 32/Web-AP server 36 converts the executed result into a displayable form. For such a form, there is, for example, a SIP-URI form. The Web sever 32/Web-AP server 36 supplies at time T184 the result of �service presence setting request, i.e., the service presence 356, to the Web browser 68 to display it.
The Web browser 68 issues at time T190 an execution request for �message transmission� (Send_REQ.) 360 to the Web server 32/Web-AP server 36. The user information and GUI are the same as those described in the previous description for operations. The Web server 32/Web-AP server 36 generates a start up signal (Launching) 362 based on the received �message transmission request� (Send_REQ.) and uses the component AP interface 78 to start up the message transmission accessing function part 236.
The message transmission accessing function part 236 starts up at time T194 the cooperation management section 66 (Launching 364). The cooperation management section 66 uses SOAP or CORBA to communicate at time T196 with the cooperation management section 54 present in the separate domain on the network 16. The cooperation management section 54 receives �message transmission request� (Send_REQ.) 366. The cooperation management section 54 starts up at time T198 the message transmitting function part 220 (Launching 368).
The cooperation management section 54 uses either SOAP or CORBA in sending out a response of the transmission result to communicate with the cooperation management section 66 (Response 374). The cooperation management section 66 receives the result of �message transmission request� issued from the Web browser 68. The cooperation management section 66 transmits at time T206 it to the message transmission accessing function part 236 of the proxy UA management part 226 (Response 376).
The message transmission accessing function part 236 receives the supplied result of �message transmission request� and delivers it as the executed result of the component AP interface 78 to the Web server 32/Web-AP server 36 at time T208 (Response 378). The Web server 32/Web-AP server 36 processes the result of the message transmission request into a displayable form, for example into a SIP-URI form. The Web server 32/Web-AP server 36 supplies at time T210 a response signal (Response 380) to the Web browser 68. The Web browser 68 displays the result of �message transmission request� on the monitor.
The operation procedure starts firstly in such a manner that the FTP client 394 issues at time T300 a request �file transfer request� to the FTP server 392/FTP-AP server 396 through the text display screen (FT_REQ. 410). The FTP server 392/FTP-AP server 396 executes at time T300 file transfer based on the received �file transfer request�. Thereafter, the FTP server 392/FTP-AP server 396 reads out the SIP-URI of a receiver to whom the message is to be directed and the content of the message to be transmitted from the content of the transferred file. The FTP server 392/FTP-AP server 396 generates a start up signal (Launching) 412 containing the read-out SIP-URI and content of the transmitted message to send it out at time T302 to the proxy UA management part 226. The proxy UA management part 226 uses the interface function of the component AP interface 78 to supply the start up signal 412 to the message transmission accessing function part 236 to start up the message transmission accessing function part 236.
The cooperation management section 54 receives the supplied request signal (FT_REQ.) 416 representative of a �file transfer request�. The cooperation management section 54 generates a start up signal (Launching) 418 for the message transmission function part 220 in the proxy UA management part 210 based on the received request signal 416. The cooperation management section 54 delivers at time T308 the start up signal 418 to the proxy UA management part 210.
The message transmission function part 220 receives a response to the received message information 420 from the SIP soft-phone 46 as the result of the message transmission, although not specifically shown. The message transmission function part 220 delivers at time T312 for the cooperation management section 52 a start up signal (Launching) 422 containing a response to the received signal. The cooperation management section 52 starts up on receiving the start up signal 422. The cooperation management section 54, in order to transmit the transmission result to the different FTP system 390 through the network 16, uses either SOAP or CORBA to send out at time T314 to the cooperation management section 66 a signal (Response) 424 which has been processed into the form processable with a protocol selected by the transmission result. The cooperation management 66 transmits at time T316 the result of �file transfer request� (Response) 426 to the message transmission accessing function part 236 of the proxy UA management part 226.
The proxy UA management part 226 receives the result of �file transfer request�. The message transmission accessing function 236 supplies at time T318 the received result as the execution result of the component AP interface 78 to the FTP server 392/FTP-AP server 396 (Response 428). The FTP server 392/FTP-AP server 396 supplied with the result processes the result of the message transmission request into a displayable form, for example into a SIP-URI form. The FTP server 392/TP-AP server 396 delivers at time T320 the result of the processed message transmission request (Response) 430 to the FTP client 406. The FTP client 406 displays the result of �file transfer request� in the form of codes.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6308203 *Oct 9, 1998Oct 23, 2001Sony CorporationInformation processing apparatus, information processing method, and transmitting mediumUS6567661 *Mar 7, 2001May 20, 2003Hewlett-Packard CompanyDistributed telemetry method and systemUS6934756 *Mar 21, 2002Aug 23, 2005International Business Machines CorporationConversational networking via transport, coding and control conversational protocolsUS7028306 *Dec 4, 2001Apr 11, 2006International Business Machines CorporationSystems and methods for implementing modular DOM (Document Object Model)-based multi-modal browsersUS7085814 *Nov 2, 2000Aug 1, 2006Microsoft CorporationData driven remote device control model with general programming interface-to-network messaging adapterUS7254614 *Nov 20, 2001Aug 7, 2007Nokia CorporationWeb services push gatewayUS7480915 *Oct 3, 2002Jan 20, 2009Nokia CorporationWV-IMS relay and interoperability methodsUS7487199 *Jul 23, 2003Feb 3, 2009Motorola, Inc.Method and apparatus for maintaining SIP contact addressesUS7496672 *Nov 20, 2003Feb 24, 2009Nortel Networks LimitedMethod and apparatus for a SIP client managerUS7702726 *Apr 10, 2002Apr 20, 20103Com CorporationSystem and methods for providing presence services in IP networkUS20020108128 *Sep 12, 2001Aug 8, 2002Todd LashMethod, apparatus, and system for overlapping enhancement controlUS20020131395 *Dec 19, 2001Sep 19, 2002Chenghui WangSession initiation protocol (SIP) user agent in a serving GPRS support node (SGSN)US20020147818 *Dec 5, 2001Oct 10, 2002Michael WengrovitzSession initiation protocol routing using voice cookiesUS20020184373 *Mar 21, 2002Dec 5, 2002International Business Machines CorporationConversational networking via transport, coding and control conversational protocolsUS20030079020 *Oct 23, 2001Apr 24, 2003Christophe GourraudMethod, system and service provider for IP media program transfer-and-viewing-on-demandUS20030187992 *Nov 26, 2002Oct 2, 2003Steenfeldt Rico WerniService triggering frameworkUS20040121765 *Jul 23, 2003Jun 24, 2004Idnani Ajaykumar R.Method and apparatus for maintaining sip contact addresses using event subscriptionUS20050021626 *May 22, 2003Jan 27, 2005Cisco Technology, Inc.Peer-to-peer dynamic web page sharingUS20050044233 *Jul 14, 2004Feb 24, 2005International Business Machines CorporationRemote servlets collaborationUS20060095508 *Oct 12, 2005May 4, 2006Sony CorporationInformation processing apparatus, information processing method, and transmitting mediumUS20080140789 *Aug 6, 2007Jun 12, 2008Nokia CorporationWeb services push gateway* Cited by examinerNon-Patent CitationsReference1Internet Engineering Task Force (IETF) Network Working Group; "SIP: Session Initiation Protocol, Request for Comments: 3261," Jun. 2002.2Javar Community Process; "JSR 116: SIP Servlet API," http://jcp.org/en/jsr/detail?id=116; Dec. 17, 2004; pp. 1-4.3Osamu Nakazawa et al.; "Service Providing System Allowing Flexible Cooperation Between Application Exploiting Different Protocols," U.S. Appl. No. 10/921,343, filed Aug. 19, 2004.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8332272 *Dec 27, 2011Dec 11, 2012Blaze Mobile, Inc.Single tap transactions using an NFC enabled mobile deviceUS8352323 *Nov 30, 2007Jan 8, 2013Blaze Mobile, Inc.Conducting an online payment transaction using an NFC enabled mobile communication deviceUS8583494 *Dec 7, 2012Nov 12, 2013Blaze Mobile, Inc.Processing payments at a management server with user selected payment methodUS8589237 *Dec 7, 2012Nov 19, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS8620754 *Jan 7, 2013Dec 31, 2013Blaze Mobile, Inc.Remote transaction processing using authentication informationUS8630905 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a secure elementUS8630906 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a point-of-sale terminalUS8688526 *Dec 7, 2012Apr 1, 2014Michelle FisherFinancial transaction processing with digital artifacts using a mobile communications deviceUS8693995Dec 13, 2007Apr 8, 2014Michelle FisherCustomized mobile applications for special interest groupsUS8694380 *Jan 7, 2013Apr 8, 2014Michelle FisherRemote transaction processing using a default payment method and couponsUS8725575 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment mechanismsUS8725576 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment methods using authenticationUS8725577 *Aug 29, 2013May 13, 2014Michelle FisherPersonalized mobile banking transactionsUS8751313 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a mobile applicationUS8751314 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a serverUS8751315 *Dec 5, 2012Jun 10, 2014Michelle FisherUsing a mobile device as a point of sale terminalUS8799085 *Nov 19, 2012Aug 5, 2014Michelle FisherRedeeming coupons using NFCUS8805726 *Dec 10, 2012Aug 12, 2014Michelle FisherOnline shopping using NFC and a mobile deviceUS8818870 *Dec 7, 2012Aug 26, 2014Michelle FisherUsing a secure element coupled to a mobile device as a POS terminal for processing mag stripe transactionsUS20090144161 *Nov 30, 2007Jun 4, 2009Mobile Candy Dish, Inc.Method and system for conducting an online payment transaction using a mobile communication deviceUS20120150601 *Dec 27, 2011Jun 14, 2012Blaze Mobile, Inc.Single tap transactions using an nfc enabled mobile deviceUS20130073373 *Nov 19, 2012Mar 21, 2013Blaze Mobile, Inc.Single tap transactions using a point-of-sale terminalUS20130080228 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using a user selected cardUS20130080229 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using user selected couponsUS20130080230 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using both user selected payment method and user selected couponsUS20130080231 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile applicationUS20130080232 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile deviceUS20130080233 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a secure elementUS20130080240 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a serverUS20130080241 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Redeeming coupons using nfcUS20130097032 *Dec 11, 2012Apr 18, 2013Blaze Mobile, Inc.Utilizing shopping lists for nfc transactionsUS20130097036 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a mobile device as a point of sale terminalUS20130097040 *Dec 7, 2012Apr 18, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS20130097041 *Dec 11, 2012Apr 18, 2013Blaze Mobile, Inc.Online shopping using a cloud-based mobile walletUS20130097083 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing nfc transactionsUS20130103512 *Dec 11, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a secure elementUS20130103517 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing mag stripe transactionsUS20130103588 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Processing payments at a management server with a user selected payment methodUS20130124351 *Dec 5, 2012May 16, 2013Blaze Mobile, Inc.Using an nfc enabled mobile device as a pos terminal* Cited by examinerClassifications U.S. Classification709/223, 709/224, 370/349, 709/225, 709/228International ClassificationG06F15/173, H04L29/08, H04L29/02, H04L29/06Cooperative ClassificationH04L67/2823, H04L69/329, H04L67/02, H04L69/08, H04L67/28, H04W80/10, H04W48/17, H04W80/04European ClassificationH04L29/08N27F, H04L29/08N1, H04L29/08N27, H04L29/08A7Legal EventsDateCodeEventDescriptionOct 7, 2004ASAssignmentOwner name: OKI ELECTRIC INDUSTRY CO., LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHIGETA, YOSHIAKI;ITO, SHINYA;REEL/FRAME:015881/0532;SIGNING DATES FROM 20040922 TO 20040924Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHIGETA, YOSHIAKI;ITO, SHINYA;SIGNING DATES FROM 20040922 TO 20040924;REEL/FRAME:015881/0532RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google