Browser enabled wireless communication system having encoded parameters for transmission

• US 7,519,688 B2
• Filed: 05/28/2004
• Issued: 04/14/2009
• Est. Priority Date: 11/30/2001
• Status: Active Grant

• Current Assignee: Harman Becker Automotive Systems GmbH (Samsung Electronics Co. Ltd.)
• Original Assignee: Harman Becker Automotive Systems GmbH (Samsung Electronics Co. Ltd.)
• Inventors: Lappe, Dirk, Volker, Kuz, Koeppen, Jan, Behrens, Ralph
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): AMPAGOOMIAN, DAVID S
• Application Number:
  US10/497,422
• Publication Number:
  US 20050091377A1
• Time in Patent Office: 1,782 Days
• Field of Search: 709/217, 709/219, 709/230, 709/237, 709/227
• US Class Current: 709/219
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A wireless communication system allows mobile users to access a resource from a content server. The wireless communication system includes a browser that allows mobile users to access resources through a wireless application protocol (WAP) compliant server. The (WAP) compliant server connects the browser to a content server. This connection allows resources to be passed between the browser and the (WAP) compliant server. The browser is further configured to transmit a request that includes an address for a resource, a protocol to be used, and one or more textual parameters encoded into a binary data packet. The wireless communication method includes generating a request for a resource; translating a textual portion of that request into binary data at the browser; transmitting the request to a wireless gateway; and converting the request into a format that is compatible with a protocol used by a receiving network.

Claims

1. A communication system having a browser capability, comprising:

a wireless application protocol (WAP) compliant server; and

a client communicating with the WAP compliant server utilizing a WAP protocol and adapted to transmit to the WAP compliant server a uniform resource locator (URL) request having attached parameters for requesting an offered service,

where upon transmission, the attached parameters comprise a binary data packet encoded for transmission and the binary data packet comprises;

a service identification code for identifying a requested service;

a device identification length and a device identifier for identifying a serial number of the client;

a vehicle identification number for identifying a vehicle associated with the client;

a password for logging in the requested service; and

additional data required for the requested service, the additional data varying based on the requested service;

where the server responds to the URL request by sending a response data packet, the response data packet comprising successive bits arranged one after another as follows;

the service identification code (Service ID) for identifying the requested service;

the length of the device identifier of the client;

the device identifier of the client;

bits further reserved for future applications;

a number of data packets transmitted by the WAP compliant server; and

a packet number of each data packet within the number of data packets transmitted by the WAP compliant server; and

a session identification code for further identifying a session and having a variable length where the session identification code is generated and determined by the WAP compliant server upon first request.

2. The communication system according to claim 1 where the attached parameters are converted into a notation specific to the URL request based on browser restrictions.

3. The communication system according to claim 1 where the URL request is not more than 256 characters long.

4. The communication system according to claim 1 where the attached parameters comprise a session identification code for a handshake process with the WAP complaint server and the WAP compliant server identifies the client making the URL request based on the session identification code.

5. The communication system according to claim 1 where the WAP compliant server performs a push transmission of another binary data packet in response to the URL request from the client.

6. The communication system according to claim 5 where the offered service comprises querying the client'"'"'s current position and the WAP compliant server pushes a query of the client'"'"'s current position and sends data based on the position passed on after a log-in by a user.

7. The communication system according to claim 1 where the data packets from the WAP compliant server comprises a one data format.

8. The communication system according to claim 1 where the service identification code has a specified bit length and the WAP compliant server decodes remaining data contained in the data packets based on the service identification code.

9. The communication system according to claim 1 where the offered service comprises searching a destination in the client'"'"'s vicinity and in response to the URL request, the client receives navigation data corresponding to the destination in the client'"'"'s vicinity once a search is complete.

10. The communication system according to claim 1 where the client comprises a navigation system resident to a vehicle radio or a vehicle navigation system.

11. The communication system according to claim 1 where the client comprises an Internet compliant hand-held wireless device.

12. The communication system according to claim 1, where the client comprises a terminal or part of the terminal within a vehicle'"'"'s communication system.

13. The communication system according to claim 1, where the WAP compliant server transmits to the client the data packets in a Multipurpose Internet Mail Extension (MIME) format.

14. The communication system according to claim 1 where the services identification code has a predetermined bit length.

15. A method for use with a communication system having browser capability and comprising a WAP compliant server and a client communicating with a WAP protocol, comprising:

receiving from the client a URL request having attached parameters for requesting an offered service where the attached parameters comprise a binary data packet encoded for transmission and the binary data packet comprises;

a service identification code (service-ID) for identifying a requested service;

a device identification length and a device identifier for identifying a serial number of the client

a vehicle identification number for identifying a vehicle associated with the client;

a password for logging in the requested service;

a session identification code (session-ID) for identifying a session; and

additional data required for the requested service, the additional data varying based on the requested service;

enabling a handshake procedure based on the session-ID and identifying the client making the URL request, thereby beginning the session with the identified client;

recognizing the service-ID and decoding remaining data in the URL request based on the service-ID;

forming at the WAP compliant server a response data packet that comprise;

the service identification code (Service ID) for identifying the requested service;

the length of the device identifier of the client;

the device identifier of the client;

bits further reserved for future applications;

a number of data packets transmitted by the WAP compliant server;

a packet number of each data packet within the number of data packets transmitted by the WAP compliant server; and

the session identification code for further identifying the session and having a variable length where the session identification code is generated and determined by the WAP compliant server upon first request; and

where forming the response data packet at WAP compliant server comprises arranging successive bits one after another in the above order; and

transmitting the response data packets to the client.

16. The method according to claim 15, further comprising:

transmitting to the client the response data packets in a Multipurpose Internet Mail Extension (MIME) format