WO2001086854A2

WO2001086854A2 - Method and system for data file management within a telecommunication system

Info

Publication number: WO2001086854A2
Application number: PCT/SE2001/000976
Authority: WO
Inventors: Babak Zahiraldinni
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2000-05-11
Filing date: 2001-05-04
Publication date: 2001-11-15
Also published as: WO2001086854A3; AU5690701A

Abstract

A method and system for providing a data file operation service within a telecommunication system (100) that allows for transporting data files, e.g. patches, presentations and multimedia files, between FTP sites (134, 132) and workstations (125) without having to upload or download the data files to a communication unit. The system includes the communication unit (105) which communicates with a real workstation (125) which in turn communicates with a data file site (132) through an Intranet or Internet (130). The communication unit (105) performs an emulator routine which operates to instruct the real workstation (125) to perform at least one of a plurality of operations on at least one data file associated with the data file site (132), in which the data file is buffered at the real workstation (125) when needed for transfer type operations.

Description

METHOD AND SYSTEM FOR DATA FILE MANAGEMENT WITHIN A TELECOMMUNICATION SYSTEM

BACKGROUND OF THE INVENTION Technical Field of the Invention

The present invention relates to telecommunications and, more particularly, to data file management within a telecommunication system. Description of Related Art

One of the most popular uses of computers today is for the communication of information. Computer systems are often connected to other computer systems using servers to form a computer network. When networked together, communication between the separate computer systems is possible. This communication can include, for example, the transfer of large amounts of data electronically.

Users can access these servers through several different communication media. A very common communications medium used in the home environment is the public switched telephone network (PSTN). For instance, a user can connect their computer to a phone line via a modem, and then place a phone call to another computer similarly connected to the PSTN. A common communication medium in most business environments is typically a Local Area Network (LAN) connection. In a LAN, the communicating computers are typically interconnected with a twisted pair of wires to form a network. Other communication media include a Wide Area Network connection (WAN), or a wireless (cellular) connection. Advances in cellular telecommunications technology now allow users to access servers using a radio interface. Because wireline connections are no longer required, hand-held computer- like devices can access server functions without restricting the user's mobility. Each communication medium offers a unique set of advantages and disadvantages making each communication medium more suitable for certain data communication uses and less suitable for other data communication uses.

When a user-to-server connection is established, any information to be transmitted must be formatted in a manner suitable for transmission. Additionally, information regarding various transmission parameters, such as the speed, ready to send signals, and ready to receive signals, must also be formatted and transmitted. Furthermore, the format of the information, as well as the convention for communicating the transmission parameters, must be known to the user or server receiving the transmission. The foregoing is accomplished using what is known in the art as a protocol. A protocol is a specific set of rules, procedures or conventions relating to the format and timing of data transmission. By establishing a common protocol between the user and server, information can be transmitted in a reliable manner understandable to both the user and the server. Exemplary protocols are briefly discussed below.

The File Transfer Protocol (FTP) allows computers to exchange, upload, and download data files. Simple Mail Transport Protocol (SMTP) provides a method for exchanging electronic mail (E-mail). One of the most popular protocols is the Hypertext Transfer Protocol (HTTP) which is used by a browser, such as the Netscape Navigator™ or the Microsoft Internet Explorer™, to browse pages on the World Wide

Web (WWW). Data sites which use applications like FTP, SMTP and HTTP transfer large amounts of data and require data links which offer a high bandwidth. Such transfers require computer-like devices which can accommodate the large amounts of data transferred between links. A recent development to improve data site communications with wireless users is the Wireless Application Protocol (WAP). In accordance with WAP, the wireless user accesses the Internet via a WAP gateway. The WAP gateway receives data communications over the Internet in HTTP format, translates the data communications to WAP format, and forwards the translated data communications in WAP format to the wireless user through the cellular network. Likewise, the WAP gateway receives data communications from the wireless user in WAP format, translates the data communications to HTTP format, and forwards the translated data communications to the Internet.

However, such WAP based systems not only require cellular capabilities but also require additional computer-like equipment and software to be added to existing cellular telephone networks and cellular phones to perform the above-described data communications. Additionally, WAP based phones are restricted by their own buffer media for receiving and transmitting data file communications. Further, WAP based phones are dependent on their own connection and speed rate to the Internet which, despite recent improvements in the mobile nets, can not be compared with the current speed rate in the fixed nets.

Similarly, Hybrid phones function as computer-like devices or microprocessor- controlled electronic devices in the cellular environment. These phones can perform some of the same functions as the WAP based phones, however, they also experience the same encumbrances as the above-described WAP based phones. Thus, there is a need for a method and system capable of improving file transfer within a telecommunication system.

BRIEF DESCRIPTION OF THE INVENTION

The present invention overcomes the foregoing and other problems by providing a method and system capable of supporting a data file service that in addition to other services allows a user of a communication unit to effectively transport data files between data sites, such as FTP sites and workstations, without having to download the data files into the communication unit. Such a service would be very useful to key people in urgent situations who do not have access to a computer or computer-like communication device with a fast Internet connection. And, such a service would also be more effective than the conventional technology used in existing WAP or hybrid phones because little needs to be actually downloaded to the communication unit (e.g., mobile station, digital PSTN phone) other than the confirmation of the execution or non-execution of commands.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the method and system of the present invention may be obtained by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein: FIGURE 1A is a block diagram of a wireless telecommunication system wherein the present invention can be practiced; FIGURE IB is a block diagram of a land-based telecommunication system wherein the present invention can be practiced;

FIGURE 2 is a flow diagram illustrating the basic steps of a preferred method of the present invention; FIGURES 3 A-3D illustrate a flow diagram of an exemplary data file service in accordance with the present invention;

FIGURES 4A-4B illustrate a flow diagram of an exemplary data file service operable within a wireless telecommunication system in accordance with the present invention; FIGURE 5 is an illustration of an SMS gateway in the messaging protocol utilized thereby between a mobile station and a mobile switching center;

FIGURE 6 illustrates the use of a CDPD for transferring packet data; and

FIGURE 7 illustrates the functionality of CDPD within the network layers.

DETAILED DESCRIPTION hi the following description, for purposes of explanation and not limitation, specific details are set forth in order to provide a thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known methods, devices, logical code, etc. are omitted so as not to obscure the description of the present invention with unnecessary detail.

A preferred embodiment of the present invention and its advantages are best understood by referring to FIGURES 1 A-4B of the drawings, wherein like numerals represent like parts. Basically, the present invention includes a method and system capable of supporting a data file operation service that in addition to other services allows a user of a communication unit to effectively transport data files between data sites without having to download the data files into the communication unit. One embodiment of the present invention is directed to using a standard mobile station as a remote control device to carry out certain FTP operations. Referring to FIGURE 1 A, there is illustrated a block diagram of a wireless telecommunications system 100 configured in accordance with the present invention. The wireless telecommunications system 100 includes a communication device such as mobile station 105 (including cellular phone, mobile phone) which can establish a connection with at least one base station (BS) 115 and vice versa. The wireless telecommunications system 100 includes at least one mobile switching center (MSC) 120 that is in communication with the BS 115. The BS 115 is the physical equipment that provides radio coverage to a particular geographical portion of an area served by the MSC 120. The MSC 120 is also connected to a real workstation 125 which may be located within (as shown) or remote to the MSC 120. The real workstation 125 is a powerful computer equipped with certain necessary applications like FTP-server, Mail-server, and with the applications particularly needed for this invention.

The mobile station 105 can establish a connection to a remote data file site 132 through, for example, an Intranet or Internet 130 for which the mobile station user has access. The data file site 132 can be an FTP site, or any server/workstation that is running in a net accessible to the user of the mobile station 105. This connection procedure is performed by the mobile station 105 using an emulator 107 which enables commands to be initiated at the mobile station 105 but executed by the real workstation 125. Preferably, the emulator 107 can be used for entering commands (mostly FTP commands) for receiving results. Responsive to the emulator 107, the real workstation 125 establishes a connection with the data file site 132. After the real workstation 125 establishes the desired connection, the mobile station user can view a list of data files associated with the data file site 132. The list is displayable on a display 106 associated with the mobile station 105. The emulator 107 enables the real workstation 125 to execute commands (e.g., transfer, rename, help and delete) on selected data file(s) associated with the data file site 132 without downloading the data file(s) into the mobile station 105. For transfer type operations (e.g.,put-the-file, mail- the-file), the selected data file(s) are not downloaded to the mobile station 105, but instead are buffered at the real workstation 125 prior to transferring the buffered data file(s) to a new data file site 134. The new data file site 134 is connected to the

Internet 130 during the full course of an FTP transfer to get the file. For non-transfer type operations (e.g., rename, delete), the emulator 107 allows the mobile station user to select at least one of the non-transfer type operations that can be performed by the real workstation 125 on selected data fιle(s) stored at data file site 132 without downloading the selected data fϊle(s) to the real workstation 125 or mobile station 105. A more detailed discussion about the different data file operations is provided below with respect to FIGURES 3A-4B.

Referring to FIGURE IB, there is illustrated a land-based telecommunication system 190 configured in accordance with the present invention. It should be understood that the land-based telecommunication system 190 can be combined with the wireless telecommunications system 100 but has been shown and described as separate systems for the sake of clarity.

The land-based telecommunication system 190 includes a digital station phone 135 including a digital display 136 and an emulator 107. The digital station phone 135 can establish a connection to a remote data file site 132 through, for example, a PSTN 140 and an Intranet or Internet 130 for which the digital station user is a member or subscriber. The data file site 132 can be an FTP site, or any server/workstation that is running in a net accessible to the digital station user. This connection procedure is performed by the digital station phone 135 using the emulator 107 which enables commands to be initiated at the digital station phone 135 but executed by the real workstation 125. The real workstation 125 may be located within

(as shown) or remote to the PSTN 140. Preferably, the emulator 107 can be used for entering commands (mostly FTP commands) and for receiving results. Responsive to the emulator 107, the real workstation 125 establishes a connection with the data file site 132. After the real workstation 125 establishes the desired connection, the digital station user can view a list of data files associated with the data file site 132. The list is displayable on a display 136 associated with the digital station phone 135. The emulator 107 enables the real workstation 125 to execute commands (e.g., transfer, rename, help and delete) on selected data file(s) associated with the data file site 132 without downloading the data file(s) into the digital station phone 135. For transfer type operations (e.g., put-the-file, mail-the-file), the selected data fϊle(s) are not downloaded to the digital station phone 135 but instead are buffered at the real workstation 125 prior to transferring the buffered data file(s) to a new data file site 134. The new data file site 134 is connected to the Internet 130 during the full course of an FTP transfer to get the file. For non-transfer type operations (e.g., rename, delete), the emulator 107 allows the digital station user to select at least one of the non- transfer type operations that can be performed by the real workstation 125 on selected data file(s) stored at the data file site 132 without downloading the selected data file(s) to the real workstation 125 or digital station phone 135. Again, a more detailed discussion about the different data file operations is provided below with respect to FIGURES 3A-4B. Referring to FIGURE 2, there is a flow diagram illustrating the basic steps of a preferred method 200 of the present invention. Basically, the process begins at step 202 by establishing a communication link between a communication unit (e.g., mobile station 105 and digital station phone 135) and a remote data file site 132 through a real workstation 125. The communications can be initiated by a user operating a communication unit 105 and 135. For example, the user can initiate the process by depressing a function key on the communication unit 105 and 135. The function key can be one key or a combination of keys. In addition, the process may also be initiated by voice activation.

After successfully establishing the communications link, an emulator 107 within the communication unit 105 and 135 operates at step 204 to enable commands

(non-transfer type commands and transfer type commands) initiated by the user at the communications unit and executed by the real workstation 125. At step 206 which is associated with non-transfer type commands (e.g., rename, delete), the real workstation 125 can execute these commands on selected data file(s) stored at data file site 132 without downloading the selected data file(s) to the real workstation 125 or communication unit 105 and 135. At steps 208 and 210 which are associated with transfer type commands (e.g., put-the-file, mail-the-file), the selected data file(s) are not downloaded to the communication unit 105 and 135 but instead are buffered at the real work station 125 prior to transferring the buffered data file(s) to a new data file site 134. Alternatively, the digital station user may transfer the buffered data file(s) in an attachment of an email sent from the real workstation 125 to another user. Referring to FIGURES 3A-3D, there is illustrated a flow diagram of an exemplary data file service in accordance with the present invention. This exemplary data file operation can be performed within a wireless telecommunication system and/or a land-based telecommunication system. Specifically referring to FIGURE 3 A, a data file secession begins at step 302 by depressing a key or a combination of keys on a communication unit 105 or 135. The data file secession may also begin by voice activation. After initiation of the data file secession, a predefined process at step 304 requests a user of the communication unit 105 or 135 to provide the name or identity of a data file site 132 they want to communicate with and, subsequently at step 306, the user enters the identity of the data file site 132 using the communication unit 105 or 135. The data file site 132 can be an FTP site or any server/workstation that is running in a net accessible to the communication unit 105 or 135. The identity of the data file site 132 is the (or "is the same as the" IP) address/name of the workstation or the FTP site. At step 308 (optional), the predefined process may request a user to provide a user name for log-in purposes. In response to the user name request, the user can enter at step 310 their user name using the communication unit 105 or 135. Subsequently, the entered user name and identity of the data file site 132 are sent to a real workstation 125 through the MSC 120 or PSTN 140. The MSC 120 and PSTN 140 utilize this information to obtain, for example, user subscriptions, user control data and user billing data. The real workstation 125 can be a conventional workstation or hardware and software located in close geographical proximity to or within the MSC 120 or PSTN 140.

Thereafter, a determination is made at step 312 as to whether the requested data file site 132 is an anonymous site which may be accessed without a password. If the data file site 132 is not an anonymous site, then the predefined process at step 314 requests the user to input a password. Following the password request, the user enters at step 316 their password into the communication unit 105 or 135 which is used by the real workstation 125 to access the data file site 132. If the data file site 132 is an anonymous site, the real workstation 125 may identify the user to the data file site 135 by sending the e-mail address of the user to the data file site 132. At step 318, the real workstation 125 obtains and sends a list of files associated with the data file site 132 through the MSC 120 or PSTN 140 to the communications unit 105 or 135. The list of files can be displayed on the display 106 or 136 of the communication unit 105 or 135 such that the user can scroll through the list and select one or more files. Continuing to FIGURE 3B, the user can mark at step 320 the desired or requested file(s), for example, by depressing a key or a combination of keys on the communications unit 105 or 135. Next at step 322, the real workstation 125 sends a list to the communications unit 105 or 135 which enables the user to select a particular data file operation (e.g., transfer operation or non-transfer operation) that they desire to have performed in or with the marked file(s). For example, the choice of data file operations can include transfer (step 324), rename (step 336), delete (step 340), or other types of operations (step 344) that are known in the art. The user can select a particular data file operation, for example, by scrolling to the desired displayed operation and depressing a key. More than one data file operation may be chosen for each marked file.

The communication unit 105 or 135 each include an emulator 107 that enables the execution of non-transfer type operations (see steps 336, 340 and 344) on the marked data file(s) without downloading the marked file(s) from the data file site 132 to the real workstation 125 or the communication unit 105 or 135. If the rename selection is chosen at step 336, then the user at step 332 by way of the real workstation

125 can rename the marked data file(s) in the data file site 132. And, if the delete selection is chosen at step 340, then the user at step 342 by way of the real workstation 125 can delete the marked data file(s) in the data file site 132. Moreover, if the other operation selection is chosen at step 344, then the user by way of the real workstation 125 can select at step 346 whether or not they want to communicate with another data file site. If yes, the predefined process begins again back at step 302 (FIGURE 3 A) and, if no, the predefined process is completed at step 380 (FIGURE 3D).

If the transfer type operation is chosen at step 324, then at step 325 the marked file(s) are downloaded and buffered at the real workstation 125 instead of being downloaded and buffered at the communication unit 105 or 135 as they are in conventional systems. At step 326, the user can then select the particular type of transfer operation they want performed on the marked file(s) buffered at the real workstation 125. The transfer operations can include, for example, a put-the-file operation (step 328) or a mail-the-file operation (step 332). The selection can be entered at the communication unit 105 or 135 in a variety of ways including depressing keys and voice activation. If the user elects the put-the-file operation (step 328), then the user is requested at step 330 to indicate the name or IP -address of a new data file site or workstation that is going to receive the marked file(s). Otherwise, if the user elects the mail-the-file operation (step 332), then the user is requested at step 334 to insert the desired e-mail address or to select it from the address book (the e-mail address of another recipient of a desired destination).

Referring to FIGURE 3C, the predefined process at step 348 (following step 330 in FIGURE 3B) request the user of the communication unit 105 or 135 to provide the name or identity of a new data file site 134 to which they want to transfer the marked file(s). Subsequently at step 350, the user enters the identity of the data file site 132 using the communication unit 105 or 135. The identity of the new data file site 134 is the same as the IP-address/name of the new workstation or FTP site.

At step 352 (optional), the predefined process may request a user to provide a user name for log-in purposes. In response to the user name request, the user can enter at step 354 their user name using the communication unit 105 or 135. Subsequently, the entered user name and identity of the new data file site 134 are sent to the real workstation 125 through the MSC 120 or PSTN 140. The MSC 120 and PSTN 140 utilizes this information to obtain, for example, user subscriptions, user control data and user billing data.

Thereafter, a determination is made at step 356 as to whether the new data file site 134 is an anonymous site which may be accessed without a password. If the new data file site 134 is not an anonymous site, then the predefined process at step 362 requests the user to input a password. Following the password request, the user enters at step 364 their password into the communication unit 105 or 135 which is used by the real workstation 125 to access the new data file site 134. If the new data file site 134 is an anonymous site or the user has entered the password at step 364, then a list of the files associated with the new data site 134 are sent at step 358 to the communication unit 105 or 135. The list of files is displayed on the display 106 or 136 of the communication unit 105 or 135 such that the user can scroll through the list and select the position within the new data file site 134 where the marked fιle(s) are to be transferred during step 359. At step 360, the transfer of the marked data file(s) to the new data site 134 is confirmed. At step 366, the user is sent a receipt confirming the transfer from the real workstation 125 to the new data file site 314. Thereafter, the put-the-file operation is directed towards the finish process at step 380.

Still referring to FIGURE 3C, the user is queried at step 368 (following step 334 in FIGURE 3B) as to whether a message is to be added to the e-mail. If yes, the user can insert the message at step 370 through the communication unit 105 or 135.

After the user has inserted the message or has chosen not to add a message, the marked file(s) are mailed at step 372 as an attachment to the e-mail. In a preferred embodiment, this part of the file transfer procedure can be handled by a mail server which is associated with the real workstation 125. After the e-mail is sent, the user is sent at step 374 a receipt confirming the transfer. Thereafter, the e-mail transfer operation is directed towards the finish process at step 380.

Referring to FIGURE 3D, the exemplary finish process is illustrated which begins at step 380 by asking the user if they have finished this secession of data file services. The user may choose to begin a new data file service in which case the predefined process would go back to step 302 (FIGURE 3A). Alternatively, at step 38 the user may choose to simply terminate the current data file service.

It should be understood that the aforementioned procedure shown in FIGURES 3A-3D is only one example of how the data file service of the present invention can be implemented. Additional steps which could be added to the aforementioned procedure include fault handling and/or authentication. In addition, it should be understood that the user in the aforementioned procedure can include a mobile station user or a digital station user.

Referring to FIGURES 4A-4B, there is illustrated a signal flow diagram of an exemplary data file service operable within a wireless telecommunications system in accordance with the present invention. Although this exemplary data file operation is described as being performed within a wireless telecommunication system, it could also be performed within a land-bases telecommunication system or a combination of the two systems.

Specifically referring to FIGURE 4A, initially, the mobile station or MS part 105 sends a request at step 1 to a base station or BS part 115 requesting a data file service. The BS part 115 in turn sends a control request to a MSC or Switch part 120.

In response, the Switch part 120 sends a reply request at step 2 to the MS part 105 through the BS part 115. The reply request queries the MS part 105 for a name of a data file site 132 or for an IP address if the user subscribes to the data file service, otherwise, the user is sent a fault message from the Switch part 120. The user submits at step 3 the host name or IP address which can be selected from an address book within the MS part 105. The MS part 105 sends the entered information to the BS part 115 and the BS part 115 sends a connection request to the Switch part 120. Next, the Switching part 120 signals an associated Server part 425 (e.g., real workstation 125 of FIGURES 1A and IB) to open communications with requested data file site 132. The Server part 425 may be located within or remote to the Switching part 120.

The Server part 425 in turn sends at step 4 a request to the Switch part 120 for a user name and/or password if the requested data file site 132 is not an anonymous site. The Switch part 120 forwards the request to the BS part 115 which forwards the request to the MS part 105. The user responds by entering at step 5 the requested user name and/or password and sending this information to the Server part 425 through the

BS part 115 and the Switch part 120. Upon receipt of a valid user name and/or password, the Server part 425 establishes the connection through the Intranet or Internet 130 to the requested data file site 132 and a reply result is sent at step 6 to the MS part 105. Next, the user selects at step 7 a command from a list of available commands and then the selected command is sent at step 8 to the Server part 425. The list of commands may include, for example, transfer, rename, help and delete or other file operations known in the art. Except for transfer type commands, the selected commands are executed by the Server part 425 without downloading the marked data fιle(s) from the data file site 132. For transfer type commands (e.g., put-the-file and mail-the-file), the marked data fιle(s) are first buffered at the Server part 425. And, then the buffered data file(s) are transferred by the Server part 425 to a new data file site 134 or another user without downloading the marked data file(s) to the MS part 105.

Now referring to FIGURE 4B, upon receipt of the selected command, the Server part 425 causes the command to be executed at step 9 on the marked data file(s) and sends at step 10 the result back to the MS part 105. If needed, the execution of transfer type commands at step 9 can include downloading the marked data file(s) to the Server part 425 which then executes the transfer type commands. Or if needed, the execution of non-transfer type commands at step 9 (as shown) can be performed by the Server part 425 which executes the non-transfer type commands at the data files site 13. The above-described steps 7-10 may be repeated again at step 11 so as to execute more commands.

For transfer type commands, the user can choose at step 12 to e-mail or put the marked data file(s) to a new data file site 134 or another user. For a put selection, steps 3 to 11 are repeated at step 13 for the new data file site 134. After steps 3 to 11 have been completed and the marked data file(s) have been transferred to the new data file site 134, the user is then informed at step 17 by the Server part 425 as to whether the transfer was or was not successful. In addition, the Server part 425 requests at step 17 whether the user would like to continue with other data file operations or exit from the session. If the user wants to exit the session, then a request is sent at step 18 to the Server part 425 which operates to delete files (if any) that are temporarily buffered within the Server part 425. If the user wants to continue the session, then the process is started again at step 1.

A request to e-mail the marked data file(s) requires the user to enter a destination address which is received and checked at step 14 by the Server part 425. Next, the Server part 425 sends at step 15 the result to the MS part 105 and asks the user to enter a short message (if desired) to the e-mail. The Server part 425 sends the short message, with the data file attached, to the recipient's e-mail address and gives the MS part 105 the confirmation. Subsequently, the Server part 425 requests at step 17 whether the user would like to continue with other data file operations or exit from the session. If the user wants to exit the session, then a request is sent at step 18 to the

Server part 425 which operates to delete files (if any) that are temporarily buffered within the Server part 425. If the user wants to continue the session, then the process is started again at step 1.

The communications between the mobile station part 105 and the switch part

120 described in FIGURES 4A and 4B maybe carried out using a number of different communication protocols. The communication protocols may utilize a circuit switched short message service (SMS) protocol or alternatively, may utilize a packet switched CDPD protocol.

Circuit switch communications (SMS) may utilize the R-data channel for transmission of messages between the MS part 105 and the server part 425. SPACH and RACH messaging may be used on a TDMA air interface between the MS part 105 and the server part 425 on the R-DATA channel. The SPACH messaging protocol is used for downlinking messages coming from the server part 425 via the base station part 115 through the switch part 120. The RACH messaging protocol is used for sending messages from the mobile station part 105 to the server part 425 through the base station part 115 and switch part 120. This structure illustrates an SMS messaging protocol enabling the communication of messages of up to 200 octets. This provides for a greater probability that a received message packet is correctly decoded even under server channel impairment. FIGURE 5 illustrates the usage of an SMS gateway for sending commands between the MS part 105 and the server part 425. The signaling protocol between the base station and MSC of FIGURES 4A and

4B may also be implemented within a packet data transmission protocol using existing systems such as CDPD, EDGE, WCDMA, GPRS, etc. FIGURE 6 illustrates an example of an implementation of how the CDPD protocol can be used to transfer packet data (for instance for a list of files from an FTP site) within this invention. FIGURE 7 illustrates the functionality of CDPD within the network layers.

It should be understood that there are many technical fields in which the present invention may be used. For instance, the technology can be used for sending urgent patches, instructions and presentations as desired by key persons who are not at work or do not have access to a computer with fast internet connection. In addition, the technology can also be adapted for all of the services where files are downloaded or uploaded by means of a mobile phone. For instance, this technique can be modified and used like "Sky Melody" in 3G phones. The "Sky Melody" feature, which is now very popular in Japan, enables one to download their favorite melodies from the Internet and play them on their handset. This is a complete digital feature with data packet transfer. But this can be used as well in a 2G phone by using the present invention. One can actually get their melody file from the Internet. The file will be converted from a data format to speech (voice/sound) format and sent to the MSC. The voice/second signals may then be played as an audio signal at the MS.

Although preferred embodiments of the method and system of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it will be understood that the present invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit and scope of the present invention as set forth and defined by the following claims.

Claims

WHAT IS CLAIMED IS:

1. A method for providing a data file management service within a telecommunication system, said method comprising the steps of: establishing a connection to a real workstation through a communication unit, said real workstation capable of communicating with a data file site; and performing an emulator routine within said communication unit, wherein said emulator routine enables commands initiated at said communication unit to be executed by said real workstation and said data file site without downloading a data file to said communication unit.

2. The method of Claim 1, further including the step of transmitting to said communication unit a data file list indicating data files associated with said data file site, said data file list is displayable on said communications unit for viewing and operation selection by a user.

3. The method of Claim 1 , further including the step of buffering, at said real workstation, a selected file in response to said emulator routine instructing said real workstation to perform a transfer type of operation.

4. The method of Claim 1, further including the steps of selecting a transfer type of operation, and identifying a new data file site.

5. The method of Claim 4, wherein said transfer type includes transporting at least one data file using an e-mail message.

6. The method of Claim 1, wherein said real workstation communicates with said data file site through at least one of an Intranet system and an internet system.

7. The method of Claim 1 further including the step of determining whether said user can access said data file site.

8. The method of Claim 7, wherein said step of determining whether said user can access said data file site further includes the step of requesting a password from said user.

9. The method of Claim 1, wherein said communication unit comprises a mobile phone, said mobile phone establishing said connection to said real workstation through a cellular telephone network.

10. The method of Claim 9, wherein said cellular telephone network comprises a mobile switching center, wherein said mobile switching center is com ected to said real workstation.

11. The method of Claim 1, wherein said data file site includes a file transfer protocol (FTP) site.

12. The method of Claim 1, wherein said communication unit comprises a digital stationary phone, said digital stationary phone establishing a connection with said real workstation through a public switched telephone network.

13. A system for providing a data file management service within a telecommunications system, the system comprising: a first workstation; a second workstation, wherein said first workstation communicates with said second workstation; and a communication unit communicating with said first workstation and performing an emulator routine, wherein said emulator routine operates to instruct said first workstation to perform at least one of a first type and a second type of operation on at least one data file associated with said second workstation.

14. The system of Claim 13, wherein said first workstation is capable of buffering said at least one data file in response to said emulator routine instructing said first workstation to perform said second type of operation, said second type of operation is performed at said first workstation without downloading said at least one data file to said communication unit.

15. The system of Claim 13, wherein said first workstation is capable of transmitting a data file list indicating data files associated with said second workstation to said communication unit, said data file list is formatted to be displayable on said communications unit for viewing and operation selection by a communications unit subscriber.

16. The system of Claim 13, wherein said second type of operation includes transfer operations.

17. The system of Claim 13, wherein said first workstation, for transfer operations, is capable of operating to receive a transfer type selection and a transfer destination identifier from said communications unit.

18. The system of Claim 13 , wherein said transfer type selection includes at least one of transmitting said data file using a file transfer protocol and attaching said at least one data file to an electronic message.

19. The system of Claim 13 , wherein said first workstation communicates with said second workstation through at least one of an Intranet system and an internet system.

20. The system of Claim 13, wherein said first workstation determines whether said communications unit subscribes to said data file management services.

21. The system of Claim 13 , wherein said first workstation further operates to request a password from said communications unit.

22. The system of Claim 13, wherein said second workstation is identified by at least one of an IP address and a name.

23. The system of Claim 13 , wherein said communication unit comprises a mobile phone, said mobile phone communicating with said first workstation through a cellular telephone network.

24. The system of Claim 23, wherein said cellular telephone network comprises a mobile switching center, wherein said mobile switching center is connected to said first workstation.

25. The system of Claim 13 , wherein said data file site includes file transfer protocol (FTP) site.

26. A method for providing data file services within a cellular telecommunication system, the method comprising the steps of: establishing a connection to a data file site through a mobile station, wherein said cellular telecommunication system is connectable to a workstation and said workstation is connectable with said data file site through at least one of an Intranet system and an internet system; instructing said workstation to transmit a list of data files associated with said data file site to said mobile station; selecting at least one transfer type of operation to be performed on at least one data file of said data file list; and for selection of said transfer type of operation: transmitting said at least one data file to said workstation; and buffering, at said workstation, said at least one data file, wherein said transfer type of operation is performed between said workstation and a desired e-mail address without downloading said at least one data file to said mobile station.

27. The method of Claim 26, wherein said data file site includes a file transfer protocol (FTP) site.

28. The method of Claim 26, wherein said transfer type of operation includes attaching said at least one data file to an electronic message which is transmitted to said desired e-mail address.

29. The method of Claim 26, wherein said mobile station includes an emulator routine operating to perform said steps of instructing and selecting.