Source: https://patents.google.com/patent/US8112103B2/en
Timestamp: 2018-10-23 08:09:46
Document Index: 789423193

Matched Legal Cases: ['application No. 2005200193', 'Application No. 200510083716', 'application No. 05000834', 'application No. 2005200193', 'application No. 2005', 'application No. 2005200193', 'application No. 2005', 'application No. 2005100866', 'application No. 2005', 'application No. 2005', 'application No. 2005', 'application No. 2005', 'application No. 05000834', 'application No. 05000834', 'application No. 10', 'application No. 2005', 'application No. 20052000193', 'application No. 2005', 'application No. 2005', 'application No. 2005100866', 'application No. 2005100866', 'application No. 05000834', 'application No. 2005', 'application No. 2005', 'Application No. 094101240']

US8112103B2 - Methods and systems for mobile device messaging - Google Patents
US8112103B2
US8112103B2 US10759642 US75964204A US8112103B2 US 8112103 B2 US8112103 B2 US 8112103B2 US 10759642 US10759642 US 10759642 US 75964204 A US75964204 A US 75964204A US 8112103 B2 US8112103 B2 US 8112103B2
US10759642
US20050164721A1 (en )
Kuang-Chao Eric Yeh
The web service 310 includes a Web Service Description Language (WSDL) file 335 defining a web service module 350. That is, the WSDL file 335 may include an XML or other description of the services provided by the web service module 350. An exemplary WSDL file is listed below in Table 1.
<definitions xmlns:http=“http://schemas.xmlsoap.org/wsdl/http/”
xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/” xmlns:s=“http://www.w3.org/2001/XMLSchema”
xmlns:s0=“urn:Microsoft.Office.OMMS.OMMWS” xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/”
xmlns:tm=“http://microsoft.com/wsdl/mime/textMatching/” xmlns:mime=“http://schemas.xmlsoap.org/wsdl/mime/”
targetNamespace=“urn:Microsoft.Office.OMMS.OMMWS” xmlns=“http://schemas.xmlsoap.org/wsdl/”>
<s:schema elementFormDefault=“qualified” targetNamespace=“urn:Microsoft.Office.OMMS.OMMWS”>
<s:element name=“sendXml”>
<s:element minOccurs=“0” maxOccurs=“1” name=“SMSData” type=“s:string” />
<s:element name=“sendXmlResponse”>
<s:element minOccurs=“0” maxOccurs=“1” name=“sendXmlResult” type=“s:string” />
<message name=“sendXmlSoapIn”>
<part name=“parameters” element=“s0:sendXml” />
<message name=“sendXmlSoapOut”>
<part name=“parameters” element=“s0:sendXmlResponse” />
<portType name=“OMMWebServiceSoap”>
<operation name=“sendXml”>
<documentation>This method handles the request from Microsoft Office Mobile Message Add-
in.</documentation>
<input message=“s0:sendXmlSoapIn” />
<output message=“s0:sendXmlSoapOut” />
<binding name=“OMMWebServiceSoap” type=“s0:OMMWebServiceSoap”>
<soap:binding transport=“http://schemas.xmlsoap.org/soap/http” style=“document” />
<soap:operation soapAction=“urn:Microsoft.Office.OMMS.OMMWS/sendXml” style=“document” />
<service name=“OMMWebService”>
<documentation>Microsoft Office Mobile Message Web Service.</documentation>
<port name=“OMMWebServiceSoap” binding=“s0:OMMWebServiceSoap”>
<soap:address location=“http://localhost/OMMWS/OMMWebService.asmx” />
FIG. 4 illustrates an exemplary format for a message from a client system or mobile device to a web service according to an embodiment of the present invention. This example illustrates one possible format for a short message. However, depending upon the exact implementation, the format may vary. For example, additional elements may be included, the elements may be in a different order or some illustrated elements may be omitted. This message format may be defined as an XML schema or in another similar manner. Table 2 is an exemplary XML schema for defining a message format as illustrated in FIG. 4.
<xs:schema targetNamespace=“urn:Microsoft.Office.OMMS.SMSData” elementFormDefault=“qualified”
xmlns=“urn:Microsoft.Office.OMMS.SMSData” xmlns:mstns=“urn:Microsoft.Office.OMMS.SMSData”
<xs:element name=“SMSData”>
<xs:element name=“Carrier” type=“xs:string” minOccurs=“1” maxOccurs=“1” />
<xs:element name=“Id” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
<xs:element name=“Password” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
<xs:element name=“ToMobile” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
<xs:element name=“Message” type=“xs:string” minOccurs=“1” maxOccurs=“unbounded” />
<xs:element name=“MsgType” type=“xs:string” minOccurs=“1” maxOccurs=“1” />
<xs:element name=“Scheduled” type=“xs:time” minOccurs=“0” maxOccurs=“1” />
<xs:element name=“MMS” minOccurs=“0” maxOccurs=“1”>
<xs:extension base=“xs:boolean”>
<xs:attribute name=“format” type=“xs:string” default=“text” use=“optional” />
The message format illustrated in FIG. 4 includes a service provider element 405, a sender's ID element 410, a password element 415, a destination element 420, a message field 425, a message type element 430, a schedule element 435, and a message format element 440.
FIG. 5 illustrates an exemplary format for a response from a web service to a client system or mobile device according to an embodiment of the present invention. This example illustrates one possible format for a response to a short message. However, depending upon the exact implementation, the format may vary. For example, additional elements may be included, the elements may be in a different order or some illustrated elements may be omitted. This response format may be defined as an XML schema or in another similar manner. Table 3 is an exemplary XML schema for defining a response format as illustrated in FIG. 5.
<xs:schema targetNamespace=“urn:Microsoft.Office.OMMS.Response” elementFormDefault=“qualified”
xmlns=“urn:Microsoft.Office.OMMS.Response” xmlns:mstns=“urn:Microsoft.Office.OMMS.Response”
xmlns:xs=“http://www.w3.org/2001/XMLSchema” id=“Response”>
<xs:element name=“Result” minOccurs=“1” maxOccurs=“unbounded”>
<xs:element name=“ToMobile” minOccurs=“0” maxOccurs=“1”>
<xs:element name=“Count” type=“xs:string” minOccurs=“0”
<xs:element name=“RetCode” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
<xs:element name=“ErrCause” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
<xs:element name=“Message” type=“xs:string” maxOccurs=“1” minOccurs=“1” />
The error cause element 525, identified by the “ErrCause” name in Table 3, may contain an indication of the component that is the cause of an error. For example, if the user's password in the original short message was invalid, the error cause element 525 can indicate the Client as the cause of the error. In another example, if the SMSC of the service provider returns a response to the web service indicating failure of the delivery of the message, the error cause element 525 may indicate the SMSC as the cause.
If a determination is made at query operation 625 that the message should be allowed, send operation 630, at the scheduled time or immediately if no scheduled time is indicated, sends the short message to the SMSC of the destination mobile device's service provider for delivery to the mobile device. Generate operation 635 then generates response such as an XML file following the schema listed in Table 3 above indicating success or failure of the message along with appropriate return codes, error codes, and error messages and sends the response to the client system.
Finally, optional notification operation 915 notifies the user of the success or failure of the message queued based on the response data. This operation is optional since, in some cases, a notification may not be desired. For example, if the message was successfully placed into the transmission queue of the SMSC, no notification may be given. In other cases, all responses may prompt notification of the user. The notification may be in the form of opening a window or other user interface element to inform the user of the success of failure of the message. The notification may include return codes, error codes, and/or error messages from the response.
receiving, at a web service client, a request from a user to send content to a mobile device;
collecting, from an originating system of the user, information including content data to be sent to the mobile device;
generating two or more short messages encapsulating the content data, the short message formatted to be readable by a web service and the content data formatted to be readable by the mobile device;
sending the two or more short messages to the web service for delivery to the mobile device; and
receiving a response readable by the originating system that indicates a status of delivery of the two or more short messages, wherein said response has a first result element and a second result element, and further wherein each said result element has one or more child elements representing details of said result element, wherein,
the first result element further comprises:
a first child count element of the first result element, wherein the first child count element indicates a number of the two or more short messages delivered successfully;
and wherein the second result element further comprises:
a second child count element of the second result element, wherein the second child count element indicates a number of the two or more short messages unsuccessfully delivered;
a recipient element, wherein the recipient element is included when a recipient is associated with an error that caused the unsuccessful delivery of the two or more short messages;
an error cause element comprising an indication of the cause of the error that resulted in unsuccessful delivery of the short messages unsuccessfully delivered; and
a message element that contains a message describing the error;
parsing the received response into individual elements; and
notifying the web service client of the success or failure of the two or more messages based on the individual elements from the parsed received response.
receiving the two or more short messages at a web service;
6. The method of claim 1, wherein generating one of the two or more short messages further comprises:
7. The method of claim 1, wherein generating the two or more short messages comprises generating an eXtensible Mark-up Language (XML) file including the content data contained in a Short Message Service (SMS) message.
8. The method of claim 1, wherein generating the two or more short messages comprises generating an eXtensible Mark-up Language (XML) file including the content data contained in a Multimedia Message Service (MMS) message.
9. The method of claim 1, wherein sending the two or more short messages to the web service comprises sending the two or more short messages using the Simple Object Access Protocol (SOAP).
10. A method for mobile device messaging over a web service comprising:
receiving two or more short messages from a web service client, the two or more short messages formatted to be readable by a web service and containing content data formatted to be readable by a mobile device, wherein the content data was specified by a user request to be sent from an originating system of the user to the mobile device;
determining whether a sender of the two or more short messages is authentic and authorized to send the two or more short messages;
if the sender of the two or more short messages are authentic and authorized to send the two or more short messages, sending the content data to the mobile device;
generating a response readable by the web service client and indicating a status of delivery of the two or more short messages, wherein said response has a first result element an a second result element, and further wherein each said result element has one or more child elements representing details of said result element, wherein,
a second child count element of the second result element indicates a number of the two or more short messages unsuccessfully delivered;
a message element that contains a message describing the error; and
11. The method of claim 10, wherein the two or more short messages comprises an eXtensible Mark-up Language (XML) file including the content data contained in a Short Message Service (SMS) message.
12. The method of claim 10, wherein the two or more short messages comprises an eXtensible Mark-up Language (XML) file including the content data contained in a Multimedia Message Service (MMS) message.
13. A system for mobile device messaging over a web service comprising:
a memory coupled with and readable by the processor and containing instructions that, when executed by the processor, cause the processor to:
receive, at a web service client, a request from a user to send content to a mobile device;
collect, from an originating system of the user, information including content data to be sent to the mobile device;
generate two or more short messages encapsulating the content data, the two or more short messages formatted to be readable by a web service and the content data formatted to be readable by the mobile device;
send the two or more short messages to a web service for delivery to the mobile device;
receive a response readable by the originating system that indicates a status of delivery of the two or more short messages, wherein said response has a first result element and a second result element, and further wherein each said result element has one or more child elements representing details of said result element, wherein,
second child count element of the second result element, wherein the second child count element indicates a number of the two or more short messages unsuccessfully delivered;
14. The system of claim 13, wherein collecting information to be sent to the mobile device further comprises collecting sender information, the sender information comprising a sender identification and a sender password.
15. The system of claim 13, wherein collecting information to be sent to the mobile device further comprises collecting destination information, the destination information comprising a service provider and a cellular telephone number of a destination mobile device.
16. The system of claim 13, wherein collecting information to be sent to the mobile device further comprises collecting delivery information, the delivery information comprising a time and date for the web service to send the content data to the mobile device.
17. The system of claim 13, wherein generating one of the two or more short messages further comprises:
18. The system of claim 13, wherein generating the two or more short messages comprises generating an eXtensible Mark-up Language (XML) file including the content data contained in a Short Message Service (SMS) message.
19. The system of claim 13, wherein generating the two or more short messages comprises generating an eXtensible Mark-up Language (XML) file including the content data contained in a Multimedia Message Service (MMS) message.
20. The system of claim 13, wherein sending the two or more short messages to the web service comprises sending the two or more short messages using the Simple Object Access Protocol (SOAP).
21. A system for mobile device messaging over a web service comprising:
receive two or more short messages from a web service client, the two or more short messages formatted to be readable by a web service and containing content data formatted to be readable by a mobile device, wherein the content data was specified by a user request to be sent from an originating system of the user to the mobile device;
determine whether a sender of the two or more short messages are authentic and authorized to send the two or more short messages, and if the sender of the two or more short messages are authentic and authorized to send the two or more short messages, send the content data to the mobile device;
generate a response readable by the web service client that indicates a status of delivery of the two or more short messages, wherein said response has a first result element and a second result element, and further wherein each said result element has one or more child elements representing details of said result element, wherein,
and wherein the second result element further comprising:
send the response to the web service client.
22. The system of claim 21, wherein the two or more short messages comprises an eXtensible Mark-up Language (XML) file including the content data contained in a Short Message Service (SMS) message.
23. The system of claim 21, wherein the two or more short messages comprises an eXtensible Mark-up Language (XML) file including the content data contained in a Multimedia Message Service (MMS) message.
US10759642 2004-01-16 2004-01-16 Methods and systems for mobile device messaging Active 2027-02-23 US8112103B2 (en)
US10759642 US8112103B2 (en) 2004-01-16 2004-01-16 Methods and systems for mobile device messaging
CA 2493180 CA2493180C (en) 2004-01-16 2005-01-14 Methods and systems for mobile device messaging
RU2005100866A RU2395114C2 (en) 2004-01-16 2005-01-14 Methods and systems of messages exchange with mobile devices
CN 200510083716 CN1716922B (en) 2004-01-16 2005-01-17 Method and system for mobile device messaging
KR20050004116A KR20050075732A (en) 2004-01-16 2005-01-17 Methods and systems for mobile device messaging
EP20050000834 EP1555837A3 (en) 2004-01-16 2005-01-17 Methods and systems for mobile device messaging
JP2005009690A JP4878757B2 (en) 2004-01-16 2005-01-17 Mobile device messaging method and system
JP2011185029A JP2011254540A (en) 2004-01-16 2011-08-26 Methods and systems for mobile device messaging
US20050164721A1 true US20050164721A1 (en) 2005-07-28
US8112103B2 true US8112103B2 (en) 2012-02-07
US10759642 Active 2027-02-23 US8112103B2 (en) 2004-01-16 2004-01-16 Methods and systems for mobile device messaging
US20160065510A1 (en) * 2005-06-29 2016-03-03 Mark Carlson Schema-based dynamic parse/build engine for parsing multi-format messages
CN105141506B (en) * 2015-08-26 2018-06-29 小米科技有限责任公司 A communication message processing method and apparatus
JP2001508958A (en) 1996-11-20 2001-07-03 インターナショナル モービル サテライト オーガニゼイション High margin notification method and apparatus
KR20010056233A (en) 1999-12-14 2001-07-04 이계철 Apparatus of processing short message services for integrated message service
JP2001525642A (en) 1997-12-01 2001-12-11 ソネラ ユルキネン オサケユキチュア Short message transmission system and method
EP1168766A2 (en) 2000-06-23 2002-01-02 Comverse Network Systems, Ltd. Web development and deployment using SMS and USSD
WO2003001819A2 (en) 2001-06-25 2003-01-03 Empower Interactive Group Limited Message transmission system and method
US20030058815A1 (en) 2001-09-26 2003-03-27 Shen Alan W. Communicating multi-part messages between cellular devices using a standardized interface
CN1444378A (en) 2002-03-11 2003-09-24 联想(北京)有限公司 Ultra-long short message sending method
EP1361763A1 (en) 2001-02-15 2003-11-12 Vodafone Group PLC System for interconnecting a remote server with a short message server centre (smsc) via the internet
WO2003096720A2 (en) 2002-05-13 2003-11-20 Orange France System and method for managing access to a protected digital content transmitted to a mobile terminal
WO2004006596A1 (en) 2002-07-09 2004-01-15 Qualcomm Incorporated Method and apparatus for conveying reports for sms messages in wireless communication systems
JP2001188743A (en) 1999-10-08 2001-07-10 Phone.Com Japan Kk Method and device for supplying internet contents to radio equipment based on sms
CN1343055A (en) 2000-06-23 2002-04-03 孔沃斯网络系统有限公司 Network development and dispatch using SMS and USSD
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System *UMTS); Multimedia Messaging Service *MMS); Functional description; State 2 (3GPP TS 23.140 version 4.10.0 Release 4)" European Telecommunications Standards Institute (ETSI), ETSI TS 123 10 V4.10.0 (Jun. 2003), XP-002381874, Jun. 30, 2003, pp. 1-79.
"iSMS: An integration platform for short message service and IP networks," by Rao, H.C.-H.; Chang, D.-F.; Lin, Y.-B., IEEE Network v 15 n 2 Mar./Apr. 2001, p. 48-55.
"On-line service adaptation for mobile and fixed terminal devices," by Korva, Jr.; Plomp, Jr.; Maatta, P.; Metso, M., Mobile Data Management, Second International Conference, MDM 2001. Proceedings (Lecture Notes in Computer Science vol. 1987), p. 252-9.
"OPC-SMS: a wireless gateway to OPC-based data sources," by V. Kapsalis; S. Koubias; G. Papadopoulos, Computer Standards & Interfaces 24 (2002) 437-451.
"System integration of WAP and SMS for home network system," by Wu, Chi-Hsiang; Jan, Rong-Hong, Computer Networks v 42 n 4 Jul. 15, 2003, p. 493-502.
"The Mobile Internet," by Emmerson, B., BYTE (International Edition) vo. 23, No. 5, p. IS40/15-19.
"Wireless data: new choices and challenges," by Borthick, S., Business Communications Review, vo. 30, No. 12, p. 28-38. (Any missing pages are advertisements.).
Australian Examiner's first report on patent application No. 2005200193, mailed Dec. 17, 2009, 2 pgs.
Chinese Notice of Allowance in Application No. 200510083716.3, mailed Jun. 3, 2011, 3 pgs.
European Search Report for application No. 05000834.1 2412, mailed on Jun. 7, 2006 (4 pages).
Examiner's Report No. 2 on Australian application No. 2005200193, mailed on Jul. 2, 2010 (6 pages).
Grant of Patent from the South African Patent Office for South African application No. 2005/0376, mailed on Jul. 19, 2007 (1 page).
Japanese Notice of Allowance in Application 2005009690, mailed Nov. 22, 2011, 6 pgs.
Korean Final Notice of Preliminary Rejection in Application 10-2005-4116, mailed Nov. 11, 2011 , 4 pgs. (in foreign language).
Notice of Acceptance for Australian application No. 2005200193, mailed on Oct. 15, 2010 (3 pages).
Notice of Allowance from the Mexican Patent Office for Mexican application No. 2005/000670, mailed on Apr. 21, 2010 (2 pages).
Notice of Allowance from the Patent Office of the Russian Federation for Russian application No. 2005100866/09, mailed on Feb. 1, 2010 (7 pages).
Notice of Final Rejection from the Japanese Patent Office for Japanese application No. 2005-09690, mailed on Apr. 26, 2011 (3 pages).
Notice of First Office Action from Chinese Patent Office for Chinese application No. 2005/0083716.3, mailed on Mar. 13, 2009 (35 pages).
Notice of Rejection from the Japanese Patent Office for Japanese application No. 2005-009690, mailed on Aug. 24, 2010 (4 pages).
Notice of the Second Office Action from Chinese Patent Office for Chinese application No. 2005/0083716.3, mailed on Mar. 25, 2011 (6 pages).
Office Action from the Malaysian Patent Office for Malaysian application No. PI20050159, mailed on Mar. 31, 2010 (3 pages).
Official Communication from the European Patent Office, First Examination Report for European application No. 05000834.1 2412, mailed on Mar. 1, 2007 (3 pages).
Official Communication from the European Patent Office, Second Examination Report for European application No. 05000834.1 2412, mailed on Jun. 9, 2011 (5 pages).
Preliminary Rejection from the Korean Patent Office for Korean application No. 10-2005-4116, mailed on May 9, 2011, (4 pages).
Response of Office Action from the Mexican Patent Office for Mexican application No. 2005/000670, mailed on Sep. 14, 2009 (17 pages).
Response to Examiner's First Report on Australian application No. 20052000193, mailed on Sep. 23, 2010 (8 pages).
Response to Notice of First Office Action from Chinese Patent Office for Chinese application No. 2005/0083716.3, mailed on Jul. 13, 2009 (18 pages).
Response to Office Action from the Malaysian Patent Office for Malaysian application No. PI20050159, mailed on Jun. 30, 2010 (3 pages).
Response to Office Action from the Mexican Patent Office for Mexican application No. 2005/000670, mailed Apr. 2, 2010 (20 pages).
Response to Official Action from the Patent Office of the Russian Federation for Russian application No. 2005100866/09, mailed on May 26, 2009 (5 pages).
Response to Official Action from the Patent Office of the Russian Federation for Russian application No. 2005100866/09, mailed on Nov. 30, 2009 (15 pages).
Response to Official Communication from the European Patent Office First Examination Report for European application No. 05000834.1 2412, mailed on Sep. 11, 2007 (13 pages).
Response to the Notice of Rejection from the Japanese Patent Office for Japanese application No. 2005-009690, mailed on Dec. 24, 2010 (9 pages).
Response to the Second Office Action from the Chinese Patent Office for Chinese application No. 2005/0083716.3, mailed on Apr. 25, 2011 (7 pages).
Russian Second Office Action in Application 2005100866, mailed Feb. 26, 2009, 8 pgs.
Search Report for Taiwan Invention Patent Application No. 094101240, Date of Research: Aug. 11, 2011, Received by Merchant & Gould, P.C. on Oct. 21, 2011, 1 page.
US9756001B2 (en) * 2005-06-29 2017-09-05 Visa U.S.A. Schema-based dynamic parse/build engine for parsing multi-format messages
JP2011254540A (en) 2011-12-15 application
EP1555837A2 (en) 2005-07-20 application
US20050164721A1 (en) 2005-07-28 application
CA2493180A1 (en) 2005-07-16 application
CN1716922A (en) 2006-01-04 application
RU2395114C2 (en) 2010-07-20 grant
CN1716922B (en) 2011-10-19 grant
JP4878757B2 (en) 2012-02-15 grant
CA2493180C (en) 2013-12-17 grant
JP2005202972A (en) 2005-07-28 application
KR20050075732A (en) 2005-07-21 application
EP1555837A3 (en) 2006-07-05 application
RU2005100866A (en) 2006-06-20 application
US20050027741A1 (en) 2005-02-03 Method and system for alert delivery architecture
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YEH, KUANG-CHAO ERIC;LIN, LYNN;SHIH, GEORGE;REEL/FRAME:014921/0745