AU2004203177B2 - Communication System for Mobile Devices - Google Patents

Description

COMMUNICATION SYSTEM FOR MOBILE DEVICES BACKGROUND OF THE INVENITON TECHNICAL FIELD The present invention relates to a communication system and more particularly to a communication system suitable for use in an information distribution system providing information from at least one server apparatus to a plurality of user terminals via a network.

BACKGROUND

ART

The Internet provides content providers with an environment capable of delivering content to users around the world directly and at a low cost. In addition, the Internet provides users an environment that allows content from around the world to be enabled for use in a standard user interface. As development, provision and use of content providing services that make use of the Internet become more prevalent, the vast amount of content for available on the Internet increases daily. As a result, the ease of access to the Internet has become an important consideration in the development of content distribution services.

With the increasing popularity of the Internet, transparent system architectures employing Internet technologies in LANs (Local Area Networks) have become commonplace. One basic constituent of many "Internet technologies" is the communication protocol, specifically TCP/IP (Transmission Control Protocol Internet Protocol). In fact, a large number of networks currently employ the TCP/IP.

Data communications according to TCP/IP are based on an OSI layer model (OSI Reference Model). The OSI reference model is a seven layer model used to model data relayed between a transmitter and a receiver. On the transmission side, data is relayed by sequentially adding headers for each layer to actual data from a higher layer to form packets. The packets are transmitted to the reception side. At the reception side, the transmitted packets are processed sequentially from the lowest layer (physical layer) to the highest layer. During processing in each layer, packets supplied from a lower layer are separated into data and a header corresponding to that layer. The content of the header is analyzed, and the data is handed to a next higher layer.

An example of the packet structure obtained by the processing in each layer on the transmission side shall be explained with reference to Figs. 12-14. In this example, the transmission side and reception side are connected one-to-one using a PPP (Point-to-Point Protocol), as in general dial-up connections.

Fig. 12 shows the structure of an example TCP segment which is a packet that has undergone processing in the fourth layer (transport layer). The TCP segment is composed of a TCP header and data. The TCP header is composed of a basic header (20 bytes) and an optional header. The basic header includes information such as a source port number, destination port number, sequence number, acknowledgment number, code bits and window size. Additionally, the data is composed of actual data and a header added by processing at an upper layer equal to or higher than the fifth layer (session layer).

Fig. 13 shows the structure of an example IP datagram which is a packet that has undergone processing in the third layer (network layer). This IP datagram is composed of an IP header and data. The IP header is composed of a basic header (20 bytes) and an optional header. The basic header includes information such as a source IP address, a destination IP address, a service type, a packet length, and a protocol number. Additionally, the data is composed of actual data and a header added by processing on a layer equal to or higher than the fourth layer (transport layer) such as TCP, UDP (User Datagram Protocol) or ICMP (Internet Control Message Protocol).

Fig. 14 shows the structure of an example PPP frame which is a packet that has undergone processing in the second layer (data link layer). The numbers in parentheses in Fig. 14 are given in units of bytes. The illustrated PPP frame consists of a PPP header (5 bytes), data, and a PPP footer (3 or 5 bytes).

The PPP header includes a flag, an address, a control, and a packet protocol identifier such as LCP (Link Control Protocol), IPCP (Internet Protocol Control Protocol), IP or IPX (Internetwork Packet Exchange). In addition, the data includes actual data and a header (including the above-mentioned TCP header and IP header) added by processing at least one layer equal to or higher than the third layer (network layer). The PPP footer includes an FCS (Frame Check Sequence) and a flag. The MTU indicated in Fig. 14 refers to the maximum transmission unit.

As described above, on the transmission side, the actual data to be transmitted is processed by procedures corresponding to each layer in the OSI layer model from the highest layer to the lowest layer. As such, a header corresponding to the processing of each layer is sequentially added to the actual data.

Fig. 7 illustrates an example packet 7A that has undergone all of the processes on the transmission side and is ready to be transmitted. As shown in Fig. 7, the packet 7A has a header composed of a 5-byte PPP header, a IP header and a 20-byte TCP header. The header therefore includes a total of bytes that are added at the beginning of the application data (if it is assumed that there are no optional headers). In addition, a 3- or 5-byte footer is added at the end of the application data. The size of the application data is, for example, 500 bytes and can be expanded to a maximum of 1460 bytes.

The operating sequence for performing packet communications according to TCP/IP shall now be explained with reference to the example process flow diagram of Fig. At S1, an LCP set up request message requesting set up of the LCP is sent from the data transmission side to the data reception side, or from the data reception side to the data transmission side. An acknowledgment response message (LCP Set Up Ack) corresponding to the LCP set up request is then sent from the party receiving the LCP set up request message to the other side at S2.

At S3, a Challenge Message to perform identification at the other side is subsequently sent from the data reception side. Upon receipt of the challenge message on the data transmission side, a response message is sent out at S4.

At S5, a Success Message to indicate that the identification on the other side has succeeded is then sent out from the data reception side to the data transmission side.

Once this sequence of operations is complete, an IPCP set up request message is sent from the data reception side to the data transmission side at S6.

In addition, an IPCP set up request message is sent from the data transmission side to the data reception side at S7. At S8, an IPCP set up request message or a negative response message (Nak) is sent from the data reception side to the data transmission side. Upon receiving the IPCP set up request message, an acknowledgment response message (IPCP Set Up Ack) is sent from the data transmission side at S9.

At S10, an IPCP set up request message is then sent from the data transmission side to the data reception side. Upon receiving the IPCP set up request message, an acknowledgment response message is sent from the data reception side at S11. In this way, a PPP link is established between the data transmission side and the data reception side.

At S12, an IP TCP Request message requesting establishment of an IP data link and establishment of a TCP connection is then sent from the data transmission side to the data reception side. Upon receipt of the IP TCP request message, an IP TCP acknowledgment response message is sent from the data reception side at S13. At S14, the data transmission side receives the IP TCP acknowledgement response message and sends out a reply IP TCP acknowledgment response message indicating that the IP TCP acknowledgment response message has been received. In this way, a TCP connection is established between the data transmission side and the data reception side. The transmission and reception of actual data in the form of packet data is then initiated.

Packet data is first transmitted from the data transmission side by means of HTTP (HyperText Transfer Protocol) at S15. At S16, the data reception side receives the packet data and sends out an acknowledgment response message.

Then, depending upon the size of the data being transmitted the number of packets needed), the operations of steps S15 and S16 are repeatedly performed until the transmission of the packet data is completed.

At S17, a transmit finish message indicating that the transmission of the packet data has been completed is sent out from the data transmission side. The data reception side, upon receiving the transmit finish message, sends out an acknowledgment transmit finish message at S18. At S19, a reception complete message indicating that the reception of data has been completed is sent out from the data reception side. Upon receipt of the reception complete message, the data transmission side sends out an acknowledgment reception complete message at In this way, the TCP session is terminated. At S21, to disconnect the PPP link, a Termination Request message requesting termination of the PPP link is sent out from the data transmission side. Upon receiving the termination request message, an acknowledgment termination request message is sent from the data reception side at S22. In this way, the PPP link is first disconnected. Upon disconnection of the PPP link, the channel is disconnected at S23 and the overall operation is completed.

In recent years, mobile communications have spread widely, and mobile data communications using mobile terminals is increasing in popularity. In the field of mobile data communications, it has become possible for a mobile user to access the Internet using a mobile terminal. Accordingly, provision for userfriendly Internet access services for mobile users is desired. Providing such mobile Internet access services using packet communications according to TCP/IP as described above, however, creates undesirable performance and operability issues.

With TCP/IP, as described above, the. header of a packet is added sequentially by each layer and encapsulated. As a result, the overall header size becomes large. The header size is particularly large in comparison to the data when the actual data size is small. For example, when transferring about 500 bytes of data during mobile communications, the header size is about ten percent of the data size. Among the information contained in the header there are also fields which are left unused.

The number of signals exchanged between the data transmission side and reception side using TCP/IP is also relatively large in the operating sequences during establishment of connections prior to actually transmitting data. In the example shown in Fig. 15, a total of 14 steps from step S1 to S14 are performed.

Consequently, as the number of users accessing the network increases, network traffic increases dramatically and the data transfer rates may drop. In addition, since the mobile user is charged for the operations (steps S1-S14) prior to data transmission and reception, the economic burden on the mobile user may also become large.

Although these processes also occur 'in connections to the Internet via fixed networks, they are especially burdensome in mobile communication where data transmission capability bandwidth) is relatively low in comparison to communication via fixed networks.. In addition, since TCP/IP is relatively complex, mobile terminals with computing capability to rapidly process TCP/IP may be larger, heavier, and more expensive. Currently, mobile terminals with rapid processing capability (such as a personal digital assistant (PDA, etc.) simply include a portable computer and are therefore received well only in small markets.

In contrast, mobile stations that are used for voice communication are designed with portability, operability and ease of use. The form and price of mobile stations for voice communication are believed to already be well-received in a broad market due to their general usefulness and high degree of popularity.

As mentioned above, various types of content capable of meeting the needs of various users already exists on the Internet. Due to the steady increase in the amount of content, devices that are already operated by various users, such as mobile stations for voice communication, are desired as devices for accessing the Internet. Thus, services for accessing the Internet using mobile stations for voice communication that have the capability to rapidly process TCP/IP will be well-received in a wide market. Even without taking into consideration the problem of data transmission capability in mobile communications.

One might also consider having the content providing side develop content that is customized to the data processing power of mobile stations for voice communication, and/or the data transmission capability of mobile communications. The development of this type of customized content may place a heavy burden of the content providing side. Accordingly, it is predicted that only a small amount of content with uses that are restricted to mobile stations for voice communication as compared to the content of the Internet will be available to the user.

From the above description, it is believed that the foundation of mobile data distribution is in the combination of mobile stations with voice communication with the Internet. In order to achieve this combination, it is necessary to develop efficient communication technologies which enable mobile users to effortlessly use content from the Internet using mobile stations with voice communication.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems, and has the object of providing a communication method, terminal device and relay apparatus capable of efficiently performing data communications even when the data processing capability and transmission capability are not high such as in mobile stations.

In accordance with a first aspect of the present invention there is provided a method for relaying application data between a terminal which belongs to a local, private network and one or more content provider servers which belong to a public network, including the steps of: establishing a packet communication link, between the terminal and the local, private network, that implements packet communications between the terminal and the local, private network; establishing, over the packet communication link, one or more logical communication connections between the terminal and the local, private network in order to communicate the application data between the terminal and the one or more content provider servers; and while relaying the application data between the terminal and the one or more content provider servers, conducting, at the network, communication protocol conversions on the application data to be sent to the terminal and received therefrom.

According to a second aspect of the present invention there is provided a relay apparatus for relaying application data between a terminal and one or more content provider servers, including at least first and second communication protocol stacks that implement different communication protocols for communication with the terminal and the one or more content provider servers and relay the application data between the terminal and the one or more content provider servers while conducting communication protocol conversions on the application data relayed between them, the first communication protocol stack including: packet communication link layers that establish a packet communication link, between the terminal and the relay apparatus, that implements packet communications between the terminal and the relay apparatus; and a transport layer, located over the packet communication link layers, that establishes, over the packet communication link, one or more logical communication connections between the terminal and the relay apparatus in order to communicate the application data between the terminal and the one or more content provider servers.

According to a third aspect of the present invention there is provided a terminal that exchanges application data with one or more content provider servers via a local, private network, said terminal including a communication protocol stack that implements a first communication protocol, the communication protocol stack including: packet communication link layers that establish a packet communication link, between the terminal and the local, private network, that implements packet communications between the terminal and the local, private network; and a transport layer, located on the packet communication link layers, that establishes, over the packet communication link, one or more logical communication connections between the terminal and the local, private network in order to communicate the application data between the terminal and the one or more content provider servers, the application data being transmitted, between the network and the one or more content provider servers, using a second communication protocol that differs from the first communication protocol.

According to preferred embodiments of the present invention there is employed a simplified protocol to perform data communications between a server apparatus and a user terminal. The simplified protocol makes the header size smaller and thus reduces the amount of data transferred. In addition, the simplified protocol reduces the number of transmitted messages (signals) when a channel connection is established. These preferred embodiments thereby reduces communication traffic and resulting overhead and also improves the response of data communications. Therefore, they enable smooth and speedy downloading of Internet content with devices having the data processing capabilities of a mobile device and through wireless communication channels having relatively low data transmission capacity.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram showing the structure of an example communication system according to an embodiment of the present invention.

Fig. 2 is a block diagram showing an example protocol structure of the same communication system illustrated in Fig. 1.

Fig. 3 is a block diagram showing another example protocol structure of the communication system illustrated in Fig. 1.

Fig. 4 is a flow diagram showing an example operating sequence prior to packet communications in the communication system illustrated in Fig. 1.

Fig. 5 is a flow diagram showing an example operating sequence during packet communications in the communication system illustrated in Fig. 1.

Fig. 6 is a flow diagram showing an example operating sequence after packet communications in the communication system illustrated in Fig. 1.

Fig. 7 is a table comparing the structure of a packet transmitted in TCP/IP communications and the structure of a packet transmitted according to a simplified protocol T6.

Fig. 8 is a table showing the structure of an example packet transmitted in a connection set up request.

Fig. 9 is a table showing the structure of an example packet transmitted in acknowledgment response to a connection set up request of Fig. 8.

Fig. 10 are tables showing the structure of example packets transmitted during data transmission and reception, showing the structure of a packet containing actual data and showing the structure of a packet transmitted in acknowledgment response when the packet containing actual data has been transmitted.

Fig. 11 is a diagram showing an example of the outward appearance of a mobile station contained in the same communication system of Fig. 1 and showing a screen of an information display portion when the mobile station is providing the user with information.

Fig. 12 is a table showing the format of an example TCP segment.

Fig. 13 is a table showing the format of an example IP datagram.

Fig. 14 is a table showing the format of an example PPP frame.

Fig. 15 is a flow diagram showing an example operating sequence for the case in which data communications are performed using TCP/IP.

Fig. 16 is a block diagram showing the structure of another example communication system.

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention shall be described in detail with reference to the attached drawings.

1. Structure of Embodiment 1.1. System Structure Fig. 1 shows the structure of a communication network system of the present embodiment. The communication network system comprises at least one MS (Mobile Station) 1, at least one BS (Base Station) 2, at least one PPM (Packet Processing Module) 3 and at least one GWS (GateWay Server) 5. At least one CPS (Content Provider Server) 8 is connected to GWS 5 via the Internet 6 or a dedicated line 7. In addition, at least one M-SCP (Mobile Service Control Point) 9 is connected with the GWS 5. BS 2, PPM 3, GWS 5, M-SCP 9 and the interconnecting communication paths form a mobile packet communication network MS 1 is a terminal device which utilizes packet communication services of the mobile packet communication network 10. In addition to wirelessly communicating with the mobile packet communication network 10 shown in Fig.

1, the MS 1 may also wirelessly communicate with a mobile telephone network (not shown). The MS 1 may therefore also be capable of receiving mobile telephone service.

Fig. 11 shows an example of the outward appearance of the MS 1 and example screens displayed on the MS 1. The MS 1 may include an audio input/output portion (not shown) for the user to perform audio communications. In addition, the MS 1 may include a radio portion for performing wireless radio communications with BS 2 (Fig. Further, the MS 1 may include an information display portion 1 a. The information display portion 1 a may include a liquid crystal panel or the like.

An operating portion 1 b may also be included in the MS 1 for performing information input operations such as number entry or character input. The MS 1 also includes an internal microcomputer for controlling these portions.

Additionally, the MS 1 contains software that may be generally referred to as a browser for viewing document data. The browser is software for displaying a dialog screen based on data in a content format such as HTML data format. The data (hereafter referred to as HTML data) may be supplied from the CPS 8. The CPS 8 may be operated by a content providing business to communicate content over the mobile packet communication network The MS 1 may display for the user various types of information on the information display portion l a utilizing the above-mentioned browser. An example information display portion la can display 8 (characters) x 6 (lines) of information. In other examples, it is possible to have more than 8 characters horizontally and more than 6 lines vertically, depending on the area of the information display portion 1 a and the character size.

During operation, the MS 1 may perform a variety of functions and/or provide a variety of data. For example, when the user pushes an "information" key on the operating portion 1 b, an initial screen 11A may provide the user with information relating to a weather forecast. The initial screen 11A is displayed on the information display portion 1 a. By operating a jog dial key 1 c, the user can select from a weather forecast menu of in the initial screen 11A. If, for example, the user selects a screen 11 B showing today's weather is displayed in the information display portion la.

If the user selects then a screen 11C showing a weekly weather forecast is displayed on the information display portion la. If the user selects then a weather message submenu screen 110 is displayed. The weather message submenu screen 11D may be used to select information such as a rainfall alarm or a quick weather report. Furthermore, if the user selects then a world weather forecast screen 11E is displayed. Text-based information may therefore be displayed on the information display portion l a under control of the browser. The text-based information may be presented in a form that is easy for the user of the MS 1 to see and control.

In Fig. 1, the BS 2 may be positioned according to a wireless radio zone.

The wireless radio zone provides a communication area, such as a geographic area with a determined radius such as about 500 meters. A BS 2 may perform radio communications with one or more MS 1 that are present in the wireless radio zone. In the mobile packet communication network 10, a plurality of the BS 2 may be geographically positioned to form a plurality of wireless radio zones.

The PPM 3 is a computer-based system that may operate in a packet subscriber switching station. The PPM 3 is capable of accommodating a plurality of BS 2. the PPM 3 may receive packet switching requests from the MS 1 via the BS 2. In addition, the PPM 3 may relay packet switching within the mobile packet communication network The GWS 5 is a computer-based system that may operate with a mobile packet gateway switching station. The GWS 5 may interconnect the mobile packet communication network 10 with another network such as the Internet 6.

As shall be explained later, the GWS 5 may also maintain a wireless communication path (a radio-oriented interval) between the MS 1 and the GWS In addition, a wireline communication path (a wire-oriented interval or landline communication path) may be maintained by the GWS 5 between the GWS 5 and the CPS 8. Accordingly, the GWS 5 operates as a relay between the MS 1 and the CPS 8. Additionally, a plurality of the GWS 5 may form a server group. A proxy server may also be included in the server group. Further, the GWS 5 may perform various types of control to enable packet communications between the MS 1 and CPS 8 by absorbing differences between the MS 1 and CPS 8.

Enabling packet communications involves translation between a first communication protocol and a second communication protocol. The first communication protocol is a simplified protocol hereafter referred to as "simplified protocol TL" or The simplified protocol TL is used in wireless communication paths within wireless communication networks (radio-oriented interval). The second communication protocol is used in wireline communication paths within wireline (or landline) networks (wire-oriented interval) and is hereafter referred to as "TCP/IP protocol".

The CPS 8 is a server-based system that may be operated by a content provider business. The CPS 8 may supply the GWS 5 with content. The content may be provided to the users of the MS 1 in a content format such as HTML data format. The content may be provided via the Internet 6 or a dedicated line 7. In addition, the GWS 5 may include a server for the mobile packet communication network 10 to provide content to the MS 1.

The M-SCP 9 may manage subscriber information and perform processing relating to packet registration. When packet communication begins, packet registration may be performed by the M-SCP 9. When packet communication ends, packet deregistration may be performed by the M-SCP 9. Billing information for the packet communications may be recorded in the PPM 3 and the GWS 5. The billing information may be transferred at a predetermined timing to a billing center such as a call toll accounting center (not shown).

1.2. Protocol Structure In the above-described communication system, the devices employ protocol structures in order to perform data communications between the MS 1 and the CPS 8.

Figs. 2 and 3 express schematically example protocol structures of the present embodiment based on an OSI layer model. Fig. 2 shows a protocol structure for a case where information is received from the CPS 8 by the mobile station MS 1. Fig. 3 shows a protocol structure for a case where information is received from the CPS 8 by an external device 11, such as a portable information terminal or car navigation device that is coupled with the MS 1.

In the example protocol structures shown in Figs. 2 and 3, the left side of the GWS 5, i.e. the PPM 3 and MS 1 (and external device 11) are in a wireless communication path or in the radio-oriented data communication interval. In a wireless communication path, a radio communication protocol and the simplified protocol TL of the present embodiment are used. On the other hand, the right side of the GWS 5, i.e. up to the CPS 8 is a wireline communication path or wireoriented communication interval. In the wireline communication path, the generalpurpose protocol TCP/IP (second communication protocol) is used.

The example protocol structure shown in Figs. 2 and 3 shall now be described in sequence from the bottom layers to a top layer based on the OSI layer model.

1.2.1. First Layer (Physical Layer) In Figs. 2 and 3, L1 indicates a physical layer protocol. In the physical layer protocol of the wireline communication path (wire-oriented interval), the frequencies used, transmission power, modulation method, access method and other wireline-related communication parameters are defined. The wirelinerelated communication parameters are defined in order to ensure that the transmission of bit sequences is performed using communication lines composed of physical media such as dedicated lines, public telephone lines or ISDN.

On the other hand, in the physical layer protocol of the wireless communication path (radio-oriented interval), the packet communication channels are defined on the basis of the channel structure of the mobile packet communication network 10 (Fig. such as a personal digital assistant (PDC) system. The arrangement/structure of physical channels for packet communication, the signal coding method and signal transmission method for transmitting signals using the physical channels for packet communication are defined.

1.2.2. Second Layer (Data Link Layer) In Figs. 2 and 3, L2 indicates a data link layer protocol. In the data link layer protocol of the wireline communication path (wire-oriented interval), the procedures and interfaces for performing transparent and highly reliable data transmissions between nodes are defined. The procedures and interfaces may be defined using bit sequence transmission functions provided in the physical layer. Data links are established using PPP as the protocol of this data link layer.

On the other hand, in the data link layer protocol of the wireless communication path (radio-oriented interval), LAPDM (Link Access Procedure for Digital Mobile channel) is used between the MS 1 and PPM 3. The LAPDM is used for physical control channels and physical communication channels with functions added to perform packet communications efficiently so as to enable use on physical channels for packet communications. Furthermore, in the case of Fig.

3, an LAPB (Link Access Procedure Balanced) is used between the MS 1 and the external device 11.

1.2.3. Third Layer (Network Layer) The network layer protocol in the wireless communication path (wireoriented interval) is composed of an IP (Internet Protocol). This IP performs routing and supplies HTML data transmitted from the CPS 8 to the GWS 5 via the Internet 6. Additionally, in the wireless communication path (radio-oriented interval), PMAP (Packet Mobile Application Part) may be used between the PPM 3 and GWS 5. The PMAP is defined as a message format for transmitting and receiving user packets between nodes in a PDC-P network.

The network layer protocol for communications between the MS 1 and the PPM 3 may be composed of RT (Radio frequency Transmission management), MM (Mobility Management) and CC (Call Control). Here, RT performs functions relating to management of radio resources (including management of physical channels for packet communications). In addition, such functions as selection of radio zones and setting, maintenance, switching and disconnection of radio channels are performed by RT. MM performs functions relating to mobile station MS 1 movement support. The functions include position registration and identification. CC performs functions relating to channel call connection control.

Such functions include setting, maintenance and release of calls. The detailed operations of these network layer protocol functions are described in "Digital Car Telephone System Standards RCR STD-27F". These functions work cooperatively to perform such control as simultaneous standby control, communication initiation control, packet transfer control, channel switching control, periodic registration control and communication termination control.

1.2.4. Fourth Layer (Transport Layer) The transport layer protocol of the wireline communication path (wireoriented interval) is composed of TCP. The transport layer protocol is for supplying HTML data transmitted from the CPS 8 to the GWS 5 via the Internet 6.

The transport layer protocol is also for communications between the MS 1 and GWS 5 over the wireless communication path (radio-oriented interval). The transport layer protocol over the wireless communication path is composed of the simplified protocol TL. The TL provides a connection-type service for performing highly reliable end-to-end communications that make communications by virtual circuits possible. As a result, higher level applications can provide dialog-type services as if a physical point-to-point link has been established with a communication partner (this is known as a "logical connection"). The TL can set up a plurality of logical connections simultaneously. The communication protocol of the mobile packet communication network 10 (Fig. 1) is composed in such a way that the TL directly resides on the bearer of the mobile packet communication network 1.2.5. Fifth Layer (Session Layer) Over the wireline communication path (wire-oriented interval), HTTP may be used for browser display. In addition, SMTP may be used for electronic mail distribution. HTTP and SMTP may be used on the session layer and presentation layer between the GWS 5 and CPS 8. Between the MS 1 and GWS communications may be performed using HTTP by means of a virtual circuit that is explained later. In addition, in the application layer, data communications are performed between the MS 1 operating a browser and the CPS 8 possessing data of various formats such as plain text, HTML, GIF, and the like.

1.2.6. Sixth Layer (Presentation Layer) The sixth layer may include HTTP as an Internet work-dedicated protocol between the MS 1 and the GWS 5. Between the GWS 5 and CPS 8, the sixth layer may include HTTP/SMTP protocols.

1.2.7. Seventh Layer (Application Layer) The application layer of the MS 1 is composed of a browser having the function of Internet browsing software. The application layer of he CPS 8 includes data such as plain text, HTML, GIF, and the like. As previously discussed, the CPS 8 operates as a server to provide the user of the MS 1 with various content.

2. Operation of the Embodiment The overall operating sequence of a communication system including the wireline communication path (wire-oriented interval) and wireless communication path (radio-oriented interval) employing a protocol structure of this type shall be explained for the case of performing packet communications. In the following description, the structures of the packets exchanged in the wireless communication path (radio-oriented intervals) shall be referred to as the occasion demands. In addition, it should be understood that each of the packets are transmitted in the form of a signal that are each messages.

2.1. Operating Sequence for Packet Registration When a user presses the "information" key in MS 1, the operating sequence for packet registration shown in Fig. 4 is executed. At S100, a packet communication registration request is issued from the MS 1 side toward the PPM 3 in the form of a meassage (or signal). Upon receiving the registration request, the PPM 3 sends the GWS 5 a message requesting readout of packet origination information at S101. The packet origination information indicates whether or not the packet originator is a packet subscriber. The packet origination information readout request message is transmitted through the GWS 5 to the M-SCP 9.

The M-SCP 9 searches for subscriber information corresponding to an originator ID included in the packet origination information readout. request message to determine whether or not the user of MS 1 is a packet service subscriber, and sends out a packet origination information readout response message at S103. At S104, the packet origination information readout response message is transmitted through the GWS 5 to the PPM 3. Upon receiving the packet origination information readout response message, the PPM 3 sends the MS 1 a packet identification request message at S105. At S106, a packet identification response meassge in response to the packet identification request message is returned from the MS 1 to the PPM 3.

A packet communication registration request message requesting registration of packet communications is transmitted from the PPM 3 through the GWS 5 to the M-SCP 9 at S107 and S108. At S109, the M-SCP 9 performs registration for initiating packet communication between the MS 1 and the wireless communication system, and returns a packet communication registration response message to the GWS 5. The packet communication registration request message is transmitted from the GWS 5 to the PPM 3 at S110.

Upon receiving the packet communication registration response message, the PPM 3 sends a channel connection request message requesting channel connection to the GWS 5 at S111. At S112, The GWS 5 receives the channel connection request message and sends a channel connection request message to the CPS 8. The CPS 8 returns a channel connection response message at S113. Upon receiving the channel connection response message, the GWS sends the PPM 3 a channel connection request message at S114. At S115, the PPM 3 sends the MS 1 a packet communication registration response message.

2.2. Operating Sequence during Packet Communications When the sequence of packet communication registration procedures ends, an initial screen such as the example shown in the previously discussed Fig. 11 is shown in the information display portion 1 a of MS 1. The user may then operate the jog dial key 1c and select a menu number from the initial screen.

Packet communications may then commence to display the content of the homepage at the URL linked to that menu number on the information display portion 1 a.

Fig. 5 shows an example operating sequence during packet communications.

At S200, the MS 1 sends out a first packet (TL-OpenReq packet). The first packet includes a connection setup request message (Open Request), the URL of the homepage which is to be accessed, and an HTTP-Get method, The HTTP- Get method is requesting transfer of the data required to display the content of the homepage on the information display portion 1 a of the MS 1.

Fig. 8 shows the structure of an example TL-OpenReq packet sent when requesting connection setup in the example of Fig. 5. In this packet, the field identified as "message type" includes information indicating that the message type is an "Open Request" message. The field identified as "data" contains data for the HTTP-Get method including the above-mentioned URL. The "logical number" field contains identification numbers for identifying the end-to-end connection established between the MS 1 and the GWS 5. The simplified protocol TL in the wireless communication path (radio-oriented interval) enables a plurality of simultaneous logical connections. Each logical connection is indicated in the field identified as "logical number". This logical number field is set on the mobile station side MS 1.

The fields identified as "communication parameters" contain the data length and the amount of data that the MS 1 can receive in one packet. In addition, information such as timer values for the case where retransmission is to be performed may be included in the communication parameters fields. The MS 1 may store information relating to its own capabilities in the communication parameter fields of the transfer packet to be sent to the wireline network side.

As shown in Fig. 5, the TL-OpenReq packet may be sent through the PPM 3 to the GWS 5 at S201. The GWS 5 returns a packet containing an acknowledgment response message (TL-OpenAck) to the MS1 through the PPM 3 (S203, S205). More specifically, on the wireline network side, a logical connection setup request message is received. The communication parameter information for the MS 1 side is analyzed. The communication parameters are determined and sent out, together with the acknowledgment response message (Open Acknowledge).

With the simplified protocol TL, the capabilities (the above-mentioned communication parameter values) of the MS 1 and the GWS 5 (the partner sides) are negotiated before setting up the logical connection and prior to data exchange. Thus, resources are used efficiently, and capacity control is performed by traffic gradients. A logical connection is then established between the MS 1 and the GWS 5 by means of these operations, and the exchange of packet data is completed.

Fig. 9 shows the structure of an example TL-OpenAck packet sent as an acknowledgement response to a connection setup request message in the example of Fig. 5. In the TL-OpenAck packet, the field identified as the "message type" contains information indicating that it is an "Open Acknowledge" message.

The field identified as "logical number" contains logical numbers designated at the time of the connection setup request.

Referring again to Fig. 5, the TL-OpenAck packet is transferred to the mobile station side MS 1 at S205.

On the other hand, the following exchange occurs between the GWS (which has received the TL-OpenReq packet) and the CPS 8 based on the normal TCP operating sequence. At S206, in order to establish a connection between the GWS 5 and the CPS 8, a segment to which a SYN flag has been set is sent from the GWS 5 to the CPS 8. As an acknowledgment response to indicate that the segment has been received, a segment with a SYN flag and an ACK flag is returned from the CPS 8 to the GWS 5 at S207. At S208, a segment having an ACK flag is sent from the GWS 5 to the CPS 8. A connection is established between the GWS 5 and the CPS 8 by means of a Three Way Handshake procedure that is part of the TCP.

At S209, an HTTP-Get segment containing the URL of the target homepage (obtained from MS 1 in step S201) is transmitted from the GWS 5 to the CPS 8. The CPS 8 returns an acknowledgment response message indicating that the HTTP-Get segment has been received by the GWS 5 at S210. At S211, an HTTP-Res segment containing data from the homepage of CPS 8 as designated by the URL is transmitted from the CPS 8 to the GWS 5. A segment with an ACK flag indicating that the HTTP-Res segment has been received is returned from the CPS 8 at S212.

When data transfer by the HTTP-Res segment ends, the connection termination process is performed. At S213, a segment set up with a FIN flag is sent from the CPS 8 to the GWS 5. The GWS 5 returns an acknowledgment response segment indicating that the segment has been received at S214. At this time, a similar connection termination process is performed from the GWS at S215 and S216.

By means of this sequence composed of S206-S216, data from the homepage of the CPS 8 is supplied to the GWS 5. A packet (TL-DATA packet) containing data from the homepage of the CPS 8 previously supplied to the GWS is transferred to the PPM 3 at S217. In Fig. 10, an example TL-DATA packet is indicated as packet 10A, and its structure is shown. In packet 10A, the field identified as the "message type" contains information indicating that the message type is a "Data" message. The fields identified as "data" includes the data from the homepage of the CPS 8.

Referring again to Fig. 5, the TL-DATA packet transferred to the PPM 3 is then transferred to the MS 1 at S219. As a result, data from the homepage selected by the user is transferred to the MS 1. The content corresponding to the menu number selected from the initial screen 11A (Fig. 11) by the user is displayed on the information display portion 1 a.

The MS 1 returns an acknowledgment response packet (TL-DATA Ack) to the PPM 3 indicating that the TL-DATA packet has been received at S220. In Fig. 10, the TL-DATA Ack packet is shown as packet 10B, and its structure is shown. In packet 10B, the field identified as "message type" includes information indicating that the message type is "Data Acknowledge".

Referring again to Fig. 5, the TL-DATA packet returned to the PPM 3 is transferred to the GWS 5 at S221.

The above-explained example is one where data transfer ends after a single packet transferred from the CPS 8 to the MS 1. In actual practice, the sequences between the PPM 3 and GWS 5 (S217, S221) and the sequences between the MS 1 and PPM 3 (S219, S220) are repeatedly performed in accordance with the amount of data supplied from the CPS 8. That is, if the amount of data supplied from the CPS 8 is 3 times the maximum amount of data capable of being received in one packet on the MS 1 side, then the data is divided and transferred to the MS 1 side in 3 packets. The processes of steps S217, S218, S221 and S222, and steps S219 and S220 are performed 3 times.

2.3. Operating Sequence at Packet Communication Termination Fig. 6 shows an example of the operating process at the time of packet communication termination. First, a message requesting deregistration from packet communications is transmitted from the MS 1, through the PPM 3 and GWS 5 to the M-SCP 9 at S300, S301 and S302. At S303, the M-SCP 9 deregisters MS 1 from packet communications, and sends a packet communication deregistration response message. The packet communication deregistration response message is transmitted via the GWS 5 and PPM 3 to the MS 1 at S304 and S305. At S306, the MS 1 sends the PPM 3 a response message acknowledging receipt of the packet communications deregistration response message.

The PPM 3 sends the GWS 5 a message requesting disconnection of the channel at S307. At S308, the GWS 5 sends the CPS 8 the channel disconnection request message. Upon receiving the channel disconnection request message, the CPS 8 sends the GWS 5 a channel disconnection response message at S309. At S310, the GWS 5 sends the PPM 3 a channel disconnection response message, thus ending the process performed at packet communications termination.

3. Effects of the Embodiment By comparing the conventional sequence using PPP, IP and TCP (shown in Fig. 15) with the sequence using TL between the MS 1 and GWS 5 (shown in Fig. it is possible to largely reduce (to about 1/3) the number of messages (signals) exchanged between the transmitting side and the receiving side. As a result, data communications may be smoothly performed even if the hardware performance (CPU processing power, memory capacity, etc.) of the MS 1 are relatively low.

Additionally, as shown in Fig. 7, the structure of the packet 7B transferred with the protocol TL is considerably simplified. That is, in communications by the simplified protocol TL, each packet is composed of a header of approximately bytes (called the TL header) and application data 500 bytes, expandable to a maximum of about 1400 bytes). Consequently, the header size is largely reduced (to about 1/5) in comparison to convention packets 7A using TCP/IP. As a result, the amount of transferred data is reduced and the communication time and bandwidth requirements are lowered.

4. Examples of Modifications The present invention is not restricted to the above-described embodiment, and various modifications such as the examples given below are possible.

Data communications downstream with respect to the network have been previously described from the viewpoint of the user of a mobile station MS 1 receiving data distributions from a CP server, CPS 8. It is also possible to transfer data according to the previously described simplified protocol TL in data communications upstream. That is, data communications by TL are possible in cases where electronic mail is to be transmitted to a partner terminal connected to the internet.

The previously described simplified protocol TL is one example of a simplified protocol. Any protocol that does not have a relatively high number of messages, as in conventional TCP/IP, may be connected to the communication partner by a virtual circuit at the transport layer level, and allow for connectiontype communications.

The structure of the packets and content of the information elements described in the present embodiment are only examples. Therefore these structures and content may be of any type which allows the header size to be made smaller, and enables smooth data communications between the user terminal MS 1 and the relay apparatus CPS 8.

The format of the data distributed from the CP server does not need to be HTML. Other formats may be employed. For example, if the distributed information is only text data, then it does not have to be a data format which uses browser-compatible tags such as HTML.

The GWS 5 can be composed of a plurality of devices, to spread the load and traffic on the GWS 5. For example, as shown in Fig. 16, it can be separated into an M-PGW (Mobile Message-Packet Gateway Module) 11 and a GWS 13. In this example, the GWS 13 performs relay processes between the mobile packet communications network 10 and external communication paths. The M-PGW 12 performs other processes. In addition, it is possible to provide a plurality of M- PGW 11 and connect each M-PGW 11 to the GWS 13, so as to spread the load and traffic on each M-PGW.

While the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention as set forth in the claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Comprises/comprising and grammatical variations thereof when used in this specification are to be taken to specify the presence of stated features, integers, steps or components or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

Claims (34)

1. A method for relaying application data between a terminal which belongs to a local, private network and one or more content provider servers which belong to a public network, including the steps of: establishing a packet communication link, between the terminal and the local, private network, that implements packet communications between the terminal and the local, private network; establishing, over the packet communication link, one or more logical communication connections between the terminal and the local, private network in order to communicate the application data between the terminal and the one or more content provider servers; and while relaying the application data between the terminal and the one or more content provider servers, conducting, at the network, communication protocol conversions on the application data to be sent to the terminal and received therefrom.

2. The method according to claim 1, wherein establishing the packet communication link includes registering the terminal, at the local, private network, for packet communication between the terminal and the local, private network.

3. The method according to claim 2, wherein registering the terminal includes authenticating the terminal using subscriber information in a registration request.

4. The method according to claim 3, wherein authenticating the terminal includes searching a subscriber database, in the local, private network, for the subscriber information.

The method according to claim 3 or 4, wherein the subscriber information associated with the terminal includes an originator ID uniquely assigned to the terminal by the local, private network.

6. The method according to any one of claims 2 to 5, wherein establishing the packet communication link further includes registering the packet communication.

7. The method according to any one of the preceding claims, wherein the packet communication link includes at least one wireless portion therein and performs control and management of wireless communications.

8. The method according to claim 7, wherein the terminal is a wireless mobile terminal.

9. The method according to claim 8, wherein the packet communication link performs mobility management of the terminal.

The method according to any one of the preceding claims, wherein establishing one or more logical communication connections includes receiving a connection setup request from the terminal and returning an acknowledgement to the terminal.

11. The method according to any one of the preceding claims, wherein the one or more logical communication connections ensures delivery of the application data between the terminal and the local, private network.

12. The method according to any one of the preceding claims, wherein a header is added to the application data to implement a logical communication connection between the terminal and the local, private network, wherein the header includes a logical number that identifies the logical communication connection.

13. The method according to any one of the preceding claims, wherein the one or more content provider servers are data sources located outside the local, private network.

14. The method according to claim 13, wherein the one or more content provider servers are connected to the local, private network over a public data communication network.

The method according to any one of the preceding claims, wherein TCP/IP is implemented in communications between the local, private network and the one or more content provider servers.

16. A relay apparatus for relaying application data between a terminal and one or more content provider servers, including at least first and second communication protocol stacks that implement different communication protocols for communication with the terminal and the one or more content provider servers and relay the application data between the terminal and the one or more content provider servers while conducting communication protocol conversions on the application data relayed between them, the first communication protocol stack including: packet communication link layers that establish a packet communication link, between the terminal and the relay apparatus, that implements packet communications between the terminal and the relay apparatus; and a transport layer, located over the packet communication link layers, that establishes, over the packet communication link, one or more logical communication connections between the terminal and the relay apparatus in order to communicate the application data between the terminal and the one or more content provider servers.

17. The relay apparatus according to claim 16, wherein the packet communication link includes at least one wireless portion therein and performs control and management of wireless communications.

18. The relay apparatus according to claim 17, wherein the terminal is a wireless mobile terminal.

19. The relay apparatus according to claim 18, wherein that packet communication link performs mobility management of the terminal.

The relay apparatus according to any one of claims 16 to 19, wherein the one or more logical communication connections ensures delivery of application data between the terminal and the relay apparatus.

21. The relay apparatus according to any one of claims 16 to 20, wherein the transport layer adds a header to the application data to implement a logical communication connection between the terminal and the relay apparatus, wherein the header includes a logical number that identifies the logical communication connection.

22. The relay apparatus according to any one of claims 16 to 21, wherein the relay apparatus communicates with the one or more content provider servers over a public data communication network.

23. The relay apparatus according to any one of claims 16 to 22, wherein the second communication protocol stack implements TCP/IP in communications between the relay apparatus and the one or more content provider servers.

24. A terminal that exchanges application data with one or more content provider servers via a local, private network, said terminal including a communication protocol stack that implements a first communication protocol, the communication protocol stack including: packet communication link layers that establish a packet communication link, between the terminal and the local, private network, that implements packet communications between the terminal and the local, private network; and a transport layer, located on the packet communication link layers, that establishes, over the packet communication link, one or more logical communication connections between the terminal and the local, private network in order to communicate the application data between the terminal and the one or more content provider servers, the application data being transmitted, between the network and the one or more content provider servers, using a second communication protocol that differs from the first communication protocol.

The terminal according to claim 24, wherein the terminal sends a registration request to the local, private network to initiate establishing the packet communication link.

26. The terminal according to claim 24 or 25, wherein the packet communication link includes at least one wireless portion therein and performs control and management of wireless communications.

27. The terminal according to claim 26, wherein the terminal is a wireless mobile terminal.

28. The terminal according to claim 27, wherein the packet communication link performs mobility management of the terminal.

29. The terminal according to any one of claims 24 to 28, wherein the terminal sends to the local, private network a connection setup request to initiate establishing the one or more logical communication connections.

The terminal according to any one of claims 24 to 29, wherein the one or more logical communication connections ensures delivery of application data between the terminal and the local, private network.

31. The terminal according to any one of claims 24 to 30, wherein the transport layer adds a header to the application data to implement a logical communication connection between the terminal and the local, private network, wherein the header includes a logical number that identifies the logical communication connection.

32. The terminal according to any one of claims 24 to 31, wherein the one or more content provider servers are data sources located outside the local, private network.

33. The terminal according to claim 32, wherein the one or more content provider servers are connected to the local, private network over a public data communication network.

34. The terminal according to any one of claims 24 to 33, wherein the second communication protocol implements TCP/IP in communications between the local, private network and the one or more content provider servers. DATED this 5th day of August 2004 NTT DOCOMO, INC WATERMARK PATENT TRADE MARK ATTORNEYS 290 BURWOOD ROAD HAWTHORN VICTORIA 3122 AUSTRALIA RCS/CAG/SH