TW200404449A - System and method for implementing virtual mobile messaging services - Google Patents

Abstract

According to one embodiment, a wireless mobile messaging system architecture includes a virtual mobile messaging service (VMMS) client, a virtual mobile messaging system (VMMS) component, and a middleware server component. The VMMS client is adapted to run on a Java-enabled mobile device, the client including a user interface and a lightweight object request broker (ORB), wherein the user interface enables input of a client request to a messaging server. The VMMS component includes an enterprise Java beans (EJB) component and a mobile messaging server agent, wherein the EJB component is configured to operate on the Java application server to handle the client request to the messaging server via the mobile messaging server agent, and the mobile messaging server agent is configured to interface with the messaging server. Lastly, the middleware server component is adapted to support distributed object-oriented connectivity from the Java-enabled mobile device to the EJB component on the Java application server, the middleware component including a gateway server adapted to support transparent access from the Java-enabled mobile device to the EJB component on the Java application server, and wherein the lightweight ORB enables communication between the client on the Java-enabled mobile device and the middleware server component on the Java application server.

Description

200404449 Π) 发明 Description of the invention [Technical field to which the invention belongs] This disclosure relates to mobile communication services, and more particularly to a system and method for performing a virtual mobile messaging service. [Previous technology] Although mobile phones were originally developed for voice telecommunications, recent technological innovations (wireless communication technology, Internet technology, and especially hardware integration technology) have positioned it as an important information tool. For example, some of the latest mobile phone models are already capable of executing Java (Java) applications. With this Java-enabled mobile phone, you can develop and use various types of JavaTM applications, such as games (events, adventures, etc.), 'entertainment programs (karaoke), and business applications (stock information, online trading, etc.) ). However, the hardware resources of such mobile phones are very limited. In order to develop high-performance and useful applications that can run on such mobile platforms, and to make up for resource constraints, close collaboration between mobile devices and server-side applications is required over the Internet. The ability to communicate is very important for this kind of mobile Java application. Therefore, to increase the appeal of mobile Java applications on platforms that use wireless connectivity, communication is the main key point. At present, there are some influences that act on some kind of tug-of-war and form the radio market. Each of these influences is fairly clear and cannot disappear immediately. The first influence includes the demand for more advanced wireless services and applications that enhance and improve people's lives and work at home and work -6-(2) (2) 200404449. The second impact includes delays in the implementation of truly useful new mobile applications and services due to competing technology platforms and communication formats that cannot communicate with each other. Several issues in the radio market are affected by these influences and affect delivery providers, handset suppliers, and companies, both of which are the same but presented in different ways. One of these issues is the need for new services and sources of income. Deliverers are looking for service ideas and technologies that can increase average unit revenue (APRU) from their corporate customers. Such applications usually do not exist and are generally difficult to deploy. Companies are looking for more effective ways to increase employee productivity through smarter technology applications. Another issue includes the need for more efficient use of available bandwidth. Bandwidth is currently at or near maximum productivity, and using next-generation bandwidth is still a dream. Another issue is the need for standardized software and applications. There is significant technical confusion in the market, leading to uncertainty and increasing the cost of delivery. This confusion has led to short-lived technologies for senders and companies, making them more frustrated in making large-scale investments. Another problem is the need for "anywhere" and "easy" access to company data. Employees are increasingly mobile and need access to company information where they are and when they need it. PCs (personal computers) are not always available and wireless devices must be able to communicate with corporate applications including email and group software. Another problem is the need for more cost-effective devices. Device manufacturers want longevity, a consistent user interface, and cost-effective technology standardization. Therefore, it is hoped to provide an innovation to overcome the above technical problems and (3) (3) 200404449 a cost-effective solution for the internal structure of the computer. SUMMARY OF THE INVENTION According to one embodiment, a wireless mobile message system structure includes a virtual mobile message service (VMMS) user, a virtual mobile message system (VMMS) component, and a mediator server component. VMMS users are used to operate on Java-enabled mobile devices. The users include a user interface and a lightweight object request arbitration interface (0 R B). The user interface enables input of user requests to the message server. The VMM S component includes an enterprise Java bean (EJB) component and a mobile message server agent. The EJB component is configured to operate on a Java application server to process user requests to the message server through the mobile message server agent. And the mobile messaging server agent is configured to interface with the messaging server. Finally, the mediator server component is used to support distributed object-oriented connectivity from Java-enabled mobile devices to EJB components on the Java application server. The mediator component includes support for transparent storage from Java-enabled mobile devices. A gateway server that takes EJB components on a Java application server, and a lightweight ORB that enables users on Java-enabled mobile devices and mediator server components on a Java application server Can communicate with each other. [Embodiment] Referring now to FIG. 1, according to an exemplary embodiment, a software structure for executing a wireless mobile information system 10 includes a B 1 ue Grid T M server software (4) (4) 200404449 body 1 2. Virtual Mobile Messaging Service EJBs 1 4. Java Native Interface (JNI) or JaWin DLL (Dynamic Link Function Library) 1 6. ActiveX DLL or Agent 1 for mail server 8 and wireless mobile user application package software 20. The installation of the wireless mobile messaging system 10 on the application server 22 includes subordinate virtual mobile messaging services accessing EJB 14 and registering DLLs for the corresponding mail messaging server 18. The web application server 22 also includes a database configured to store user profile information 24 'with object database connectivity (OdBC) or java database connectivity (JDBC) 26 database name for system data sources For the database. The web application server 22 can be configured to support the use of servlets related to the user web browser 30 and the PC user Java applet browser 32] SP (Java Server Web Page) 2 7 and EJB (Enterprise Java Bean) 2 8. The web application server 22 additionally includes the infrastructure 34 (JNDI (Java Naming and Directory Interface), JMS (Java Messaging Service), ...) when needed for specific implementations. In the following, various functions of the virtual mobile messaging service (VMMS) application disclosed in this disclosure are briefly explained. The VMMS application includes one or more goals: reduce the memory requirements of VMMS user midlets (mobile information device applets) to support 2.5 G phones (less than 30 K bytes level); support MIDP handsets; provide comprehensive mail services Functions (such as mail, calendar, tasks, notes, and contacts); and support for common mail servers (such as MS Exchange, Note, and POP3) 〇 The VMMS operating environment of this disclosure can be configured to support access to (5 ) (5) 200404449 Various mobile messaging server systems, such as Microsoft Exchange, IBM Lotus Domino, Novell GroupWise, or any other mail system that supports the standard POP3 / IMAP4 and SMTP protocols. The VMMS operating environment also uses a relational database management system (RDBMS) that supports SQL and JDBC / ORBC, a J2EETM-enabled application server, a servlet-based environment, an EJB environment, JAVA / Win32 (JAWIN), and the BlueGrid Java communication mediator. J2EE means the JavaTM 2 platform, Enterprise Edition (Enterprise Edition), and includes an environment for developing and deploying enterprise applications. JAWIN means the cooperation between the Java and the contacted components through Microsoft's Component Object Model (COM) or through the Win32 Dynamic Link Function Library (DLL). Turning now to FIG. 2 (VMMS physical plan), a block diagram of a virtual mobile information system (VMMS) structure 40 and its external independent components according to another embodiment of the present disclosure will be discussed. As a user server application, the component data flow solution has two main components in the virtual mobile messaging system (VMMS) 40, including VMMS user 42 and VMMS server 41. VMMS user is a lightweight user who handles user interface (UI) 46 . The VMMS server is a gateway server that enables mobile user applications to directly access the desired mail server 48. Figure 3 (VMMS software configuration layer) is a component diagram 50 of the vmMS application, including both the user 42 and server 44 of the VMMS 40 and their external independent software components. (6) 200404449 Regarding the VMMS software configuration layer 50 of Fig. 3, the data flow of the VMMS application is completed by using a composite protocol and format. The following table shows the protocols and formats used to transfer data from one component to another in a VMMS application according to one embodiment.

Protocol data format VMMS user BlueGrid Servlet HTTP / HTTPS string byte array VMMS EJB RMI / II0P string JAWIN DLL JNI DLL J ava object VCMM ActiveX C function library call C object (VB DLL) mail server CD0 C 0 Μ Object (Exchange) VMMS Data Stream Protocol and Format

User Components According to an embodiment, the VMMS user application 42 is downloaded and executed from a J2METM MIDP profile device. In another embodiment, a J2ME / CLDC profile is used. Regarding the J2ME / CLDC profile, due to the limited resources of J2ME / CLDC mobile devices, especially 2.5G phones, the V M M S user application 4 2 size must be less than 30 K bytes. J 2 ME stands for Java 2 Platform, Micro Edition, and includes a small set of specifications and technologies related to Java. j2ME covers a very wide range of -11-(7) (7) 200404449 devices, from wireless paging and mobile phones to frequency converters and car navigation systems. The user application 4 2 contains two main components. The mobile user component 46 is a Java-based application that runs on a mobile device to handle the user interface and can communicate with the BlueGrid server 5 2 through the BlueGrid-ORB 54. B 1 u e G1 · i d-0 R B 5 4 The user component is a mobile J a v a communication medium, which is used to handle the application HTTP / HTTPS which communicates with the BlueGrid server 52. HyperFile Transfer Protocol (HTTP) is an Internet protocol used to retrieve hyperfile objects from remote hosts. The HTTP message contains a request from the user to the server and a response from the server to the user. In addition, Secure Sockets Layer (SSL) is a protocol for transmitting private files over the Internet. Operate SSL by using public keys to encrypt the data transmitted through the SSL connection. Therefore, the HTTPS message contains a request from the user to the server and a response from the server to the user that require an SSL connection. Server component A VMMS server component is executed on the application server 44. Their main function is to provide access to / from the VMS user 42 to the desired mail service 48. It has three main server components. The first component includes a B 1 ue G1 · id server 5 2 which executes as a ser ν 1 et program 5 6 (Figure 2) and provides a gateway between BlueGrid-ORB user 54 and enterprise Java bean (EJB) 58器 Features. Therefore, the BlueGrid server 52 enables J2ME / CLDC applications of the mobile device 60 to access the EJB component 58. The VMMS EJB component 58 processes user requests. That is, the EJB component 58 receives a user request from the B 1 u e G r d s er v 1 e t program 5 6 in a string format. (8) 200404449 B 1 u e G r i d s er v 1 e t program 5 6 converts the string request into a j a v a object and sends the request object to J N I (J a v a native interface) 1 6 (picture)

JaWin DLL. JaWin DLL passes the request to VMMS ActiveX 18 (Figure 1). J a W i n D L L converts the received J a v a object into a c object and calls VMMS CLIENT ActiveX 18 through the C function (Figure 1). VMMS CLIENT ActiveX] 8 Send a request to the mail server

Server 48 (for example, MS Exchange Server 62). VMMS

CLIENT ActiveX 1 8 converts the received C object into a D 0 M object and sends a request object to the mail server 4 8. Multi-user support VMMS 50 includes a user server architecture application operating in a J2EE environment. V M M S 50 will support multi-user interaction, as its operating environment and its D L L are supported for composite concatenation. Multiple users can access VMMS 50 at the same time. Localization Issues In one embodiment, the user interface (UI) 46 is written for J2ME MIDP profiles and supports English. The user interface (UI) can also be configured to support other languages and profiles. Security Considerations According to another embodiment, many aspects of the VMMS User Server Application 50 product are required. Select MIDP profile version and -13- (9) (9) 00404449

The Java version supports SSL. In addition, VMMS is configured to support the HTTPS protocol. Referring again to FIG. 2, the WEB application server 44 includes any suitable web application server, such as but not limited to: BEA WebLogica application server; IBM WebSphered application server;

Java§ 2 platform, Enterprise Edition server; Oracle 9iS application server; Su η M i c ι 〇 s s s t e m s i P 1 a η e 13 application server; or other appropriate server.

The mail server 48 may include any suitable mail server, such as but not limited to: Micro softs Exchange server 62; IB MS

Lotus DominoS mail server 64; Novell Group Wisea 06; mail server system 68 that supports POP3 / SMTP; and mail server system that supports IMAP / SMTP. According to an embodiment, a wireless mobile platform and a mobile message structure are operated as follows. A wireless device such as a telephone handset or PDA 60 contains two code sets. The first code set is wireless mobile user 42 and the second code set is software unique to each application that must be run on the wireless device. Wireless mobile users are software that enables communication with BlueGrid servers and outperforms messaging server applications such as ExchangeTM. The wireless mobile user 42 is very small 'and requires about 2-8K class of device memory. In one embodiment, the ' wireless mobile user 42 is programmed into the device chip set of the respective wireless device. In another embodiment, the wireless mobile user 42 is downloaded into the device's memory of the wireless device by a deliverer or mobile device manufacturer, for example, from a website or via a broadcast supply program. -14- (10) (10) | 04004449 One of the advantages of the wireless mobile user 42 of the VMMS structure 40 is its simplicity. The wireless mobile platform classifies most of the 2ME processing into the BlneGrid server 12 (Figure 1), instead of wireless devices that need limited memory and processor speeds to assume the full capabilities of j2ME. Focus on the unique features of each wireless device. As such, this provides performance, maintainability, and cost effectiveness to wireless device manufacturers and their customers. According to an embodiment, the wireless mobile user 42 includes an object request arbitration interface (ORB) 54. The wireless mobile user's (ORB) 54 communicates with the B 1 ue G rid Ο RB executed on the B 1 ue G rid server 5 2. The wireless mobile user ORB 54 again uses pre-configuration to operate and is already on the wireless mobile device 60. Appear and operate MIDP (Mobile Information Device Profile) and Java KVM (Sun Microsystems Java Virtual Machine) software. In addition, at the top of wireless mobile users is software specific to each application running on the wireless mobile device (discussed further below). Regarding wireless mobile messaging according to an embodiment of the present disclosure, a wireless mobile messaging application residing on a wireless device or telephone handset 60 includes a GUI 46 and a conversation. The GUI 46 and conversation are necessary to retrieve or develop and send information such as e-mail, calendar information, and so on. The wireless UI and conversation of the wireless mobile messaging application requires approximately 2 5 κ level of device memory on the wireless device, which is significantly lower than the browser-based application and much lower than the browser itself. In addition, the wireless mobile messaging application can browse a variety of remote, broadcast menus. Send and receive information faster and use less network bandwidth by using a variety of remote, broadcast menus. Wireless mobile messaging software on wireless mobile devices is also implemented in -15- (11) (11) 00404449 binary mode, which requires much less data translation than a browser-based system. BUeGrid servlet 56 A communication point dedicated to the wireless user software of the wireless mobile device 60. The BlueGrid servlet 56 includes an ORB that communicates with the user ORB 54 of the wireless mobile device 60 and the Java Virtual Machine (JVM) software 70 (Figure 3). The JVM software 70 is the core jav & software required by the jav server. The B 1 u e G1 · i d s e 1 · v 1 e t program 5 6 runs on any web application server and resides on top of the respective web application server operating system 72. In one embodiment, the BlueGrid servlet 56 process is used for limited processing capacity on wireless devices, which is related to the (Java 2 mobile environment). Note that the J2 ME specifications are very robust. Regarding conventional wireless devices with limited processing capacity, for example, placing all J2ME-required codes on a telephone handset has proven to be impossible at times, and it is too strenuous for the manufacturer of the telephone handset. Regarding the wireless mobile architecture model of the present disclosure, most of the J2ME processing is moved to the BlueGrid servlet program 56. Therefore, it is better to let the users 42 of mobile wireless devices load as lightly as possible. In addition, with regard to the wireless mobile platform of this embodiment, the wireless mobile platform 4 includes an E J B background processing program (14, 5 8) that is configured to communicate with a corresponding server-based messaging application 48. In one embodiment, the EJ B background processing program 58 communicates with the ActiveX application 74 residing on the respective messaging application server platform 48. The ActiveX component 74 includes APIs for moving data between the messaging application 48, b 1 u e G r d mediator 5 2, and finally the wireless device 60. Because many -16- (12) (12) # 0404449

Microsoft applications and other messaging applications cannot communicate directly with Java and use ActiveX instead, so EJB code 58 is configured to translate Java to ActiveX. Therefore, EJB code makes communication with specific applications more natural. In an example where ActiveX is not required, according to one embodiment, the wireless mobile architecture includes an application specific agent 76 configured to run on a server platform of a messaging application. In another embodiment, the single agent 74 may be configured to act as a gateway agent dedicated to more than one message server, as indicated by the dashed square box in FIG. 2. In addition to the agent 74 residing on the server of the messaging application, the wireless mobile structure includes XML to EJB software. The XML-to-EJB software retrieves the XML data from the wireless mobile device and places it in the format required by the software. The EJB software provides a Java front end to messaging applications (such as Exchange 62) related to the ActiveX components or agents mentioned above. Instead, the XML to EJB software takes the EJB data and transforms it into the appropriate XML data. According to another embodiment, the wireless mobile message structure provides function expansion performance, flexibility, and ease. For example, the wireless mobile message structure can be used to implement wireless mobile messaging applications, such as E X c h a n g e 6 2, No ots TM 64, GroupWise TM 66, and POP3 68. Because the wireless mobile message structure is server-powered, it can provide a complete set of messaging functions. For example, messaging functions can include reading, framing, replying, answering everything, and forwarding. Messaging features can also include company address lookups, cut and paste into address fields, eliminating the need to type email addresses. In addition to -17- (13) (13) M0404449, although the messaging function may include access to the local address book of the wireless device, this additional messaging function needs to be completed through device-specific corrections and additionally including security considerations. The wireless mobile message structure can also provide calendar functions. Calendar features include, for example, browsing and scheduling appointments, to-do items, and forms with other users of the server-based or web messaging application. The wireless mobile messaging architecture leverages the network and application servers run by messaging applications. With regard to the wireless mobile architecture of the present disclosure, additional mobile device security features can be provided. Such security features may include, for example, suspension of the communication period so that mobile devices that are left behind and unnoticed cannot download emails and browse calendars on the Internet. In addition, email and other information cannot be retained once the mobile device is turned off, so if a mobile device is lost or stolen, it prevents any unauthorized access to that information. The wireless mobile architecture of the present disclosure facilitates performance characteristics, which may include, for example, the use of light-load client devices that minimize network traffic to enable fast response times across the network and support large enterprise users or offenders. Capabilities, and messaging applications that connect directly to the underlying web server. Wireless mobile architecture additionally provides usability features including, for example, direct connection without synchronization, no synchronization issues, mail, always-used address book, and no need for any SyncML (SyncML is used to synchronize devices and applications on the network The emerging XML-based standard.) Wireless mobile architecture eliminates information synchronization across management devices. Mobile Messages for Wireless Devices • 18- (14) 0404449 Structures The GUI more closely represents the typical communication period of the underlying server messaging application, making the GUI easy to learn and use. Another usability feature includes a simple cut-and-paste for address book registration inserted in the e-mail address line, and full-color functions such as color graphics for monthly calendar viewing when available on the handset. Unlike other wireless email systems, the wireless mobile messaging system according to an embodiment of the present disclosure provides a secure, direct connection to a server-based messaging application system, such as a corporate system. No synchronization is required between the user's mobile phone handset or wireless device and the user's PC. Moreover, no synchronization software is required on the user's PC. For mobile devices with an address book, synchronization is well-suited for writing an address book from a tied PC or wireless portal, but not for e-mail. In addition, the synchronization is based on the premise that the synchronization element is maintained on the telephone handset that will cause security problems if the handset is lost or stolen. The synchronization also requires the handset driver software. And gain many of its benefits. Finally, the synchronization communication period is usually interrupted prematurely, leaving the mobile device in an ambiguous state. The user does not know which email is synchronized and which is not synchronized. This may cause duplicate or missed emails on mobile devices. The wireless mobile architecture according to the present disclosure does not encounter any of these synchronization problems, and therefore provides the full functionality of the respective server-based messaging applications without synchronization problems. Some wireless company email access products require software redirection on the PC of the user. Redirection software adds company information technology (IT) jobs -19- (15) 0404449 Another complexity and configuration issue for personnel. However, the wireless mobile architecture of the present disclosure does not require such redirection software on the user's PC. Wireless mobile infrastructure software resides on the user GUI and / or on the wireless mobile infrastructure application server. Therefore, depending on the specific implementation, the software can be neatly managed by the company's IT staff or service provider. In addition, end users do not need to worry about whether the PC is on or off, or whether software is loaded or not. Moreover, the end user does not have to worry about whether he / she redirects email to the wireless device or not. In addition to the above, please note that browser-based wireless messaging systems have their own problems. For example, all menus are host-based. That is, the end-user selection must go to the web server and take effect before retrieving the first email or calendar from the server-based messaging application. In contrast, the mobile information user residing on the wireless device of the wireless mobile architecture of the present disclosure handles all internal menus on the mobile device. Mobile messaging users only send the last command to the email host (no web server in the middle), allowing users to do more or add extra recurring costs to the network. Therefore, the wireless mobile messaging platform of the present disclosure provides advantages not found in other wireless technologies. These advantages are to provide solutions to major problems that are difficult for wireless deliverers, device manufacturers, and enterprises, and to provide wireless solution providers with a "real" wireless Internet solution, which will soon be very satisfactory And the very secure Internet provides experience to their buyers and mobile users. Other advantages of incorporating wireless mobile structures into wireless service technology bases -20-on a (16) (16) 200404449 include: using advanced wireless network capabilities; providing next-generation wireless applications such as video calls and voice command operations And features of the basic software and structure; the establishment of global standards to make it easier to enter the global market; and the ability to provide new and useful revenue-generating wireless Internet and mobile business services to offenders while installing And the need to maintain very expensive network infrastructure. According to another embodiment, the wireless mobile messaging application software configuration layer includes the following components. The mobile message user interface is set on the mobile device or the handset to manage the display of messages. In particular, the handset includes a Java capable device with KVM / MIDP and BlueGrid ORB. The Blue Grid gateway component is set on the web application server to manage and process all requests from mobile devices and is configured to interface with the BlueGrid server. A Java-to-message service utility software or agent (e.g., Java-to-MS Exchange) converts a Java request into a corresponding message server's message service response request. The utility software also interprets Java and messaging service paging. In one embodiment, Java-to-message service utility software is implemented in the form of RPC (Remote Procedure Call). Finally, the message server services and stores messages and other information. For example, an exemplary messaging server includes any data center or server running a standard MS Exchange, and no modification is needed to the required MS Exchange. In addition, according to an embodiment of the present disclosure, a mobile message user is established to support a corresponding message server. For example, including access to one or more Microsoft Exgege server 62, LotusTM Domi 11 oTM server 64, GroupWiseTM server 66, and mobile POP3 mail server-21-(17) (17) 100404449 server 6 8 In a set of wireless mobile messaging software products, corresponding mobile messaging users are set. The mobile messaging users each include a wireless Exchange mobile messaging user, a wireless Nokia mobile messaging user, a Grup u Mobile messaging user, and a mobile mail server messaging user. In one embodiment, the wireless mobile application package software including the corresponding mobile message user may be delivered to the appropriate web application server installed on it via CD ROM or via a web / FTP computer website. Referring now to FIGS. 4 and 5, FIG. 4 illustrates an embodiment of a user interface (UI) 46 processing flow. The UI resides on a mobile device 60 for implementing a mail service according to an embodiment of the present disclosure. FIG. 5 is an exemplary screen shot on a mobile device corresponding to the UI processing flow of FIG. 4. FIG. Feature Analysis To illustrate an example of feature analysis, the process starts with the login sequence on the login screens (the login screens and input passwords in Figures 5a and 5b, respectively). In response to loading the VMMS user midlet on the mobile device, the login screen is displayed on the device display. The login screen includes asking the device user to enter a username or password. That is, the mobile device user is requested to enter his / her username and password to log in to the mail server. In response to receiving the requested username and password input, VMMS m 1 d 1 e 1 sends a login request to a mail server (such as an Exchange server). In response to receiving a login request, the Exchange mail server will execute the user during the period The ID is transferred back to the VMMS user. The user ID will be 0 or an integer greater than 0 (success). V M M S users will use this ID as proof of future requests from users at (18) (18) 100404449. During service request processing, the user server communication is ongoing, ie, the "Processing" screen, Figure 5c (Processing Screen) will be displayed on the mobile device display screen. Mobile device users can cancel by selecting and / or pressing Button to cancel the current processing .. In response to a successful login, the VMMS user requests the next screen, for example, the default screen showing the current data (Figure 5d). The mail server retrieves the user characteristics and returns to the previous request The requested folder. If the last requested request is invalid, the mail server switches back to the displayed folder requested screen. According to a conventional embodiment, in order to provide a UI (user interface) configuration that supports mobile device users , Each user will have his / her own user profile, which is stored in the server database of the wireless mobile message server structure. The user's profile characteristics are set during user positioning processing. For example The configuration features can include one or more: Folder Request, Buffer Size 'Domain, ExchangeFolder (in the example of the MS Exchange mail server) M ai 1F etch Lmit, Memory Size, and Send A] ert. F ο 1 der Request corresponds to the last packet requested by the user. BufferSize means the maximum allowed in the content field. Number of bit groups. D 〇mai η means the user's domain. EX change F ο 1 der refers to the user's MS Exchange directory. MailFetchLim it defines the maximum number of messages that can be returned from the mail server. Memory Size means The available memory on the user ’s device determines the maximum number of items that can be transferred back to the user within a given time. Finally, Send Alert gives the user ’s appointment on the handset or phone • 23- (19) (19) 200404449 handset and Ability to send email alert notifications. Folders 槪 Wants: Folders 槪 If it is the first-time user's settings screen. Folders 槪 Want to show a list of available folders belonging to the registered user. The names attached to the folders are in the folders The total number of available items. The folder is required, Figure 5d, (Folder screen) shows that the registered user folder currently contains 6 mails, 2 appointments, 2 contacts, No notes. In the exemplary folder screen of Figure 5d, the total number of messages is only an arbitrary day, for example, as the current date setting. The total number of appointments is only an arbitrary day, for example, as the current date setting. Contact The total number of people and notes are pre-existing items in their respective categories. Similarly, work items include work for any day. The select date button enables users to select different dates. Similarly, choosing Back allows the user to return to a previous screen, such as the login screen. Mail / request list The header of the mail / request screen will show the selected date and show how many messages existed on that date based on the time of receipt. The mails are listed in chronological order: put most recent first. For each mail entry, only the subject of the mail is displayed 'and its content is truncated to fit the line on the screen. Hide all other relevant information from the user. In one embodiment, all messages received on the selected date are retrieved and displayed. In other embodiments of the old wireless mobile message structure, the 'AppFetchLimit' number of recent mail back. If the number of messages on the selected date is greater than the number of MailFetchLimit, -24- (20) (20) 200404449, the application will switch back to the entire list to replace the number of MailFetchLimit. However, the size of the number of returned mail items must be smaller than the memory size available to the user (M e m y S i z e characteristic). VMMS users in turn provide user navigation. The user pilot starts by moving the cursor on the mobile device display to the desired message to mark it as the selected message. The user next selects the ENTER button (such as the green phone icon on a mobile device) to display details of the highlighted mail item. For example, other options illustrated in Figure 5f include selecting the desired MENU button to: create new message; delete selected message; reply to selected message; reply to all selected message; forward selected message; search message; And roll out the application. In one embodiment, VMMs users can be configured to display which messages have been read. Furthermore, in another embodiment, the VMMS user may be configured to distinguish between read and unread mail. In addition, VMMS users can be configured with mobile device users having the ability to filter (search) messages based on date, subject, and sender. Mail details list (Figure 5g-mail details screen) In one embodiment, the mail details page displays the following fields: Subject, From (Sender Name), To, Copy Cc, and Content. The field was not copied blindly. Each display field has two components, the header and the content. The content field is limited to the number of bytes of the "BufferSize" property. In the ~ embodiment, VMMS users only support TEXT for the mail detail screen. In another embodiment, the VMMS user is configured to support EXT and HTML in the mail detail list. (21) (21) 200404449 Create mail: When a user requests a new mail, the VMMS user fetches a sample board for the new mail from the VMMS server via a packet agreement and displays a template for the user's input. The VMMS server then creates a template. You can add or change template fields on the server side. The new template will then be dynamically displayed appropriately on the V MM S user. A new email template can include five (5) fields that are displayed: Subject, To, Copy Cc, Blind Copy, and Content. For each field in the template, there are field headers, content, and hidden field attribute types that tell VMMS users how to display and verify user input. For example, the defined attributes include: TEXT Any- string; TEXT Email A ddress-an email address that must have "@" and "·" characters in the string; TEXT Numeric- numeric field; TEXT Phone- phone Number format string; TEXT URL-HTTP URL format string; TEXT Password- will display the string instead of typing characters; TEXT Time-time format string such as: hh: mm; TEXT Date-date format character Strings such as: yyyy / mm / dd. Various steps can be implemented to edit the contents of the field, where the steps will vary depending on the needs of a particular handset vendor. For example, steps may include: using the up and / or down arrows to select an edit field; pressing the enter button to enter an edit mode; typing a content string; pressing the ENTER button to exit the edit mode; and selecting SAVE Button to switch to edit field content mode. -26- (22) (22) 200404449 According to an embodiment, the VMMS user needs the user type in the TEX Ί E m a i 1 A d d r e s s field or enter all email addresses here. In another embodiment, the VMMS user enables the user to open the Contact form, select the desired address, copy and paste the copied address into the TEXT Email Address field. When compiling a new email, the user selects the SEND button to send it. Delete mail = In one embodiment of the present disclosure, by updating the command after each delete request, the VMMS user enables the user to delete one mail at a time. In another embodiment, the VMM S user provides a plurality of mail deletion features. Reply / Reply to all emails: According to the request, the V MM user retrieves the replies / responses from the V MM server. Replying / responding to all messages is similar to creating a message template. In one embodiment, three fields are displayed: copy carbon copy, blind copy, and response content. Once the desired editing is completed, the user can press the REPLY button to request a reply (or a reply to all) to the selected message. Forwarding mail: VMMS user retrieves the forwarding template from the VMMS server. Forwarding a template is similar to creating a mail template. In one embodiment, four fields are displayed: to, copy to copy, blind copy, and new content. Once the required -27- (23) (23) 200404449 fields are entered to complete forwarding the selected mail, the user can select the REPLY button. Search Mail: VMMS users retrieve search templates from VMMS servers. Searching for templates is similar to creating email templates. In one embodiment, three fields are displayed: Subject, Date Received, and From (Sender). Based on the received search request, the VMMS server will logically AND search for all non-blank search fields in the search algorithm (blank search fields will be ignored) and return to the mailing list that meets the selected criteria. Appointment summary list (Figure 5h-Appointment summary screen): The header shows the selected date and how many appointments are in the selected date. Appointments will be listed in chronological order: the earliest appointments come first. For each meeting, only the subject of the appointment is displayed and its content is truncated to fit one (1) line on the screen. Hide all other relevant data from the user. The user navigation is as follows: move the cursor to the desired message to mark it as the selected appointment. Select the ENTER button (for example, a green phone icon or similar function key) to display the details of the highlighting appointment item. Select the Μ EN U (Menu) button to: create a new appointment; delete the selected appointment; update the selected appointment; search for the appointment; and exit the app. In one embodiment, the VMMS user provides the user with the ability to filter (search) appointments based on date, subject, and location. -28- (24). (24) .200404449 List of appointment details (Figure 5i-Dating details screen)-The details of the appointment include the following fields: subject, start time, end time, location, and content. Each display field has two components, the header and the content. The content field is limited to the < B u f f r r S i z e > byte. Creating a new appointment: Similar to creating a mail template, a VMS user retrieves a new appointment template from a VMS server. In one embodiment, five columns are displayed: the main φ title, start time, end time, location, and content. When the editing of the appointment data is finished, the user selects the SAVE button to save the new appointment. In one embodiment, the VMMS user is configured to enable the user to select from the Contact table to select available appointment time slots and notify attendees. Deleting appointments: Deleting appointments deletes appointments in a similar way to deleting messages. Update appointments: Similar to creating an email template, a VMS user retrieves an updated appointment template from a VMS server. In one embodiment, five columns are displayed: the subject, start time, end time, location, and content. These fields will be written using previously stored data. The user can modify the contents of these fields and press the Update button to send an update request to the VMMS server. -29- (25) (25) 200404449 Searching for appointments: Similar to creating an email template, a VMS user retrieves a search appointment template from a VMS server. In one embodiment, three fields are displayed: the subject, the date of the appointment, and the location. See Search Mail for more details on search algorithms. The V MM S server returns the appointment summary meeting the selection criteria. Appointment alert notification: In one embodiment, the VMS user supports sending an upcoming appointment alert to the user's mobile device or mobile phone. Contacts list (Figure 5 j _Contacts list) The header shows how many contacts this user has. List contacts in alphabetical order. For each contact, only the contact's first and last names are displayed, the contents of which are rounded down to fit one (1) line on the screen. Hide all other relevant data from the user. The user navigation bar includes: moving the cursor to the desired message to identify it as the selected contact. Select the ENTER button to display the details of the highlighted contact item. Select the menu button to: create a new contact; delete the selected contact; update the selected contact; search for the contact; and exit the application. In one embodiment, the VM MS user gives the user the ability to filter (search) contacts based on name and email address. Contact details list (Figure 5k_Contact details screen) -30- (26) (26) 200404449 The details of the contact include the following fields: first name, last name, middle name, work address, work city, State of work, home address, home city, home state, work phone, home phone, and email. Creating a new contact is similar to creating a jlL mail message board. A user of V Μ M S retrieves a template of a new contact from a VS M S server. In one embodiment, 12 fields are displayed: first name of the first name, last name, middle name, work address, work city, work state, home address, home city, home state, work phone, Home phone and email. When finishing editing the contact information, the user selects the SAVE button to save the new contact to the server. Deleting a contact Deleting a contact deletes a contact in a similar way to deleting an email. Updating a contact Similar to creating an email template, a V MM user retrieves an updated contact template from a v MM server. In an embodiment, 12 fields are displayed: first word of the first name, last name, middle name, work address, work city, work state, home address, home city, home state, work phone, Home phone and email. These fields are written using previously stored data. -31-(27) 200404449 Searching for contacts Similar to creating a mail template, V M M S retrieves the search template. In one embodiment, there are name and email. See section Searching for mail. The V MM S server returns the standard-compliant notes 槪 to the list (Figure 51-Notes 槪 to the screen header to show how many notes this user has and to round down to fit one (1) line of other relevant data on the screen. Use The Navigator column includes: Mail to mark it as the selected note. Select to display the details of the highlighted note item. Select to: Create a new note; Delete the selected note; Application. Note details list: Note details only include one (1 ) Create a new note in the field: Similar to creating a mail template, V MS puts a new pen template. In one embodiment: content. When you finish editing the contact ’s SAVE button to save a new note. The user from the VMMS server Two (2) fields are displayed: More contact details to the search algorithm. Act.) Exist. Display note contents and. Hide all from the user Move the highlight cursor to the desired ENTER button MENU button Update the selected note; or switch out: Contents. When the user only displays one (1) column of content from the VMMS server, the user selects (28) 200404449 Delete note: Delete note Delete the note in a similar way to deleting an email. Update notes: Similar to the Jian 1 mail template ’V Μ M S user updates the contact template from the V Μ S server. In one embodiment, only one (1) field is displayed: content. Write to this field with previously saved data. In addition to the features described above, work and appointments can also be performed in a manner similar to the features described above. According to one embodiment, VMMS users fully use the BlueGrid ™ user server architecture, Java EJB, Microsoft Exchange ™, and Lotus Domino 0, POP3 mail features. This embodiment provides the performance, flexibility, and ease of function expansion. Users have direct access to e-mail, appointments, contacts, and other features available in general mail services, and in addition, can be instant. According to another embodiment of the wireless mobile messaging service of the present disclosure, a packet protocol 'detail packet and a desired packet are defined for two types of packets. Details packet includes version, packet field delimiter, packet type, item ID, header, status, total number of fields, and field details. The version includes any string that indicates the version of the packet. The packet field delimiter 値 includes an integer 分成 (two bytes) divided into two parts. The first group of bits is used to identify the correction flag (bit type) and the second group of bits is used to list the packet ID type. Amendment flags can include one or more of the summary, new, update, delete, forward, reply, reply -33- (29) (29) 200404449 _ all, check, and others. The packet ID type may include one or more ID types listed in folders, calendars, emails, notes, contacts, tasks, monthly calendars, mail folders, default profiles, or others. Item IDs can include strings containing unique details of objects 1 d, such as mail, contacts, and so on. The header includes a string displayed by the user device. The status includes a "success" or "failure" message. The total number of fields and field details each include the number of subsequent field records and their format. The field detail format can include the field type, field name, and field string.槪 The packet to be included includes the version, packet field delimiter 値, packet type 値, item ID, header, status, total number of packets, and detail packets. The version, packet field delimiter, packet type, item ID, header, and status are similar to a detail packet. The total number of packets means the number of subsequent packets. Details The packet depends on the flag, which can be a detail or a packet. Now briefly discuss the user's rollback packet. E J B always returns to the user in string format array, version, packet type (modified flag + packet type), item Id, header, status, total number of items, and first item, second item, etc. If the total number of items is zero (0), the string array ends, otherwise the string continues to be the number of items in the total number of items. Regarding the user's turn-back packet, the content of the project is based on the packet type and the flag. If the flag is not to be set, then each item contains a fully qualified packet. If the packet type is a folder request, the packet of the item is 槪 wanted packet. Or if the packet type is a calendar, the project packet is a detail packet. For example, in one embodiment, the user sends the following packets to the server: default request, folder request, mail request, calendar request, contact -34-(30) (30) 200404449 person request, notes Essentials, email folder essentials, and email details. The server responds with the same packet request and appropriate results. With the calendar, contacts, and notes, the S ’details are sent back to the packet to be packaged. Some specific examples are mentioned below. Regarding the folder request, the server returns a list of all the required packets including all the mails, calendars, contacts, and notes with a total of item details packets set to zero (0). Regarding the mail, the server's request will return the packet type equal to the mail folder and the item packet will contain a zero (0) field. Therefore, in order to display the contents of the mail, the user must request a mail for each mail Id. For mail details, the server will switch back to the desired packet with one (!) Packet in the project. Encapsulated packet will be a message detail packet with appropriate fields. The following is an exemplary example of a packet processing flow according to an embodiment of the present disclosure, wherein the mail server includes a Microsoft Exchange mail server. In response to the user's login, using the username / password, the server performs a lookup of the user id from the database. Then the server looks up the realm / E x c h a n g e folder from the database, and uses the user ID to perform a login to the Exchange server. If successful, the server retrieves the buffer size setting of the last valid valid wanted packet and its contents. The server then returns the right or wrong to the user. The server responds to a user submitting a request to send a preset response. If the last requested packet is invalid, the server will return the folder from Exchange to the user. In addition, the server saves the folder as the default packet. Otherwise, the server performs one of the following; from mail to Exchange request, or from Exchange to Calendar request, or -35- (31) (31) 200404449

Exchange revert notes, or revert contacts from Exchange. In response to the user's request to send a folder, the server returns the folder 槪 to be packaged. In response to the user submitting a mail request, the server returns the mail folder to request a packet. In response to the user sending and sending the calendar packet, the server returns the calendar to request the packet. In response to the template, users can request templates such as emails, calendars, contacts, or notes. However, the user request needs to send an appropriate packet with the NEW (new) flag set in the package software type field, the item Id =,, 0 ,, and the total number of items = 0. In response, the server responds with the appropriate detail packet and the succinct NEW flag. The packet will be encapsulated in an email with the total number of 1 items and the details of the packet itself. According to an embodiment of the present disclosure, the wireless mobile platform provides one or more of the following advantages to wireless deliverers, device manufacturers, enterprises, and wireless solution providers: using standard-based technology, high performance, thousands of Design app availability, proven technology and adjustability, reduce device memory requirements, and pooling of different devices. Standard-Based Technology ’The wireless mobile platform is based on JAVA and enjoys all the advantages of j A v A including sound standards and long life. Regarding high performance, the light-load client server model reduces network conversations between wireless devices and applications, and provides improved response time to users and better use of the network bandwidth of the sender. With regard to server-based messaging applications, there are literally thousands of applications that can be transferred to the Java-based environment and provide many available applications for the needs of almost any deliverer and enterprise. Regarding (32) (32) 200404449 Proven Technology and Adjustability One embodiment of the present disclosure uses the Java platform (J2EE / J2ME user / server environment) and the BlueGrid mobile Java communication mediator technology. Regarding mobile device memory 'the user-server model of this embodiment requires a relatively small amount of device memory' so that the device is not only less expensive to produce, but also more unique at the same price point. Finally, with regard to the collection of devices, [AV A is an equalizer ', which enables the PDA and the handset to be integrated by providing the same look and feel to the user. A deliverer deploying the wireless mobile platform of the present disclosure may receive one or more benefits. Such benefits include competitive advantages and new sources of income. Incorporating the wireless mobile platform of this disclosure into an existing application web server provides a true mobile computing solution that cannot be easily replicated by deliverers and corporate competitors. For example, the combination of a wireless mobile platform and an existing wireless platform provides the rapid development of web services for mobile commercial (m-conimerce) portals, enabling deliverers or businesses to quickly expand portal services to offtakers or mobile users. Even faster, this last product advantage provides mobile access to company data. Regarding new revenue sources, the wireless mobile platform disclosed in this disclosure provides accelerated new revenue through the rapid introduction of useful new mobile applications and services, such as reducing the time to market for new wireless solutions and reducing overall development costs. Ability to grow. Wireless mobile platform solutions provide a major opportunity to give true wireless applications and content to all virtualized wireless devices, thereby substantially increasing market share. Wireless mobile platform solutions include advanced mobile communication mediators, such as -37- (33) (33) 200404449 If support for BlueGrid, which is easy to develop and adjustable, etc., make J2ME CLDC (connected limited device configuration) and j2EE can be Cooperation. Therefore, the sender or enterprise can develop an adjustable and highly trusted application with minimal development cost and maximum reduction time to market and switch back to all wireless designated devices that are virtualized. The wireless mobile platform also includes application packages that support mobile messaging for businesses. Application packages include applications that give mobile users access to not only e-mail, but also calendars, contacts, notes, and tasks. Because the wireless mobile platform is implemented with Blue Grid user-server wireless media technology, the application package allows users to enjoy all the features and benefits of their respective applications on the handset or PD. Applications can include, for example, Microsoft Exchange, Lotus Domino, and others. The wireless mobile platform makes it possible to have the features and benefits of the respective application on the handset or PDA without a browser. As a result, wireless mobile platforms can ensure consistency, performance, and the ability to quickly upgrade without changing the handset or PDA. Unlike other solutions that can only access email, the wireless mobile platform of this embodiment can also access appointments, contacts, and anything in their respective message server applications (for example, Microsoft Exchange or Lotus Domino). Get the features. Such access using the wireless mobile platform of this embodiment is instantaneous and provides a truly pleasant wireless Internet experience. According to an embodiment, the wireless mobile messaging package of the software application includes Exchange mobile messaging users, Notea mobile messaging users, -38- (34) (34) 200404449

Group Wise mobile messaging users and mobile instant messaging users. The wireless mobile platform of this disclosure in turn uses a light-load client approach. As a result, mobile messaging user software residing on mobile devices consumes very little application memory on such devices. Mobile devices include, for example, mobile phones, PDA's, and packaged PC's. In addition, each user is supported by a server component residing on a web application server, which is included in the software's wireless mobile messaging package. Utilizing the disclosed wireless mobile platform structure, applications and content can be centralized and automatically kept up to date without user intervention. Because both content and applications are server-based, you can access content and applications anytime, anywhere, regardless of mobile device and network. Internet access wireless Internet access independent of the device or network is the basic price of the wireless mobile platform disclosed herein. Therefore, the wireless mobile platform can be built to execute on various wireless networks such as GSM, CDMA, TDMA, and i-mode with MIDP protocol and DOJA (Japanese version of MIDP) in particular. In addition, if a business or delivery company maintains websites, applications, and Internet content fully protected in one or more application servers in its data center, the business or delivery company can choose the wireless user device's desired choice, When it is a mobile phone or PDA, and can maintain reliable voice and data connections and communications between different networks and platforms. The wireless mobile platform of the present disclosure utilizes the same freedom and unlimited voice communication access to provide mobile users who want to use text messages on their mobile devices. The disclosed wireless mobile platform is an innovative wireless solution, which can provide access to applications and content without being subject to location or wireless mobile control. Wireless mobile platforms and mobile messaging structures provide true wireless aggregation. Features include access to the same current information regardless of device. Data becomes truly portable. According to an embodiment, the wireless mobile platform structure is based on a Java J2ME CLDC MIDP profile and provides portability between various devices. As discussed in this article, the wireless mobile messaging of the wireless mobile messaging platform is a Jav a "user-server" application running on a BiueGrid communication mediator and a J2EE / EJB environment. The wireless mobile messaging method enables mobile devices to access not only email but also calendars, contacts, notes, and tasks from their corresponding messaging servers or servers. The "Java" user-heavy application can easily access all the features and benefits of mail server applications such as Microsoft Exchange, Lotus Domino, and many others, and becomes available on a telephone handset or PDA. Although The above only describes some exemplary embodiments, but those skilled in the art will immediately understand that many modifications can be made in the exemplary embodiments as long as the innovation principles and advantages of the embodiments disclosed herein are not substantially violated. Therefore, All such amendments are intended to be included within the scope of the disclosed embodiments as defined in the following patent application scopes. In the patent application scope, the institutional-plus-function clauses are used to cover the structure described in this document to perform the detailed functions It is not only the structural equivalent but also the same structure. [Brief description of the figure] Figure 1 is a wireless mobile message structure according to an embodiment of the present disclosure.-40- • α: £ α. (36) 200404449 Block Figures; Figure 2 is a block diagram of a wireless mobile message structure according to another embodiment of the present disclosure; Figure 3 is a wireless mobile message structure according to another embodiment of the present disclosure Block diagram of the software configuration layer of the message structure; Figure 4 is a processing flow of various modules of the user interface and a flowchart of the user interface in a wireless mobile message structure according to an embodiment of the present disclosure; Exemplary display screen diagrams of various display screens on a mobile device operating with a wireless mobile message structure according to an embodiment of the present disclosure. ~ Main components comparison table 10 Wireless mobile message system 12 BlueGridTM server software

14 Virtual Mobile Messaging Service Enterprise Java Bean Interface 16 Java Native Interface 18 Mail Server ActiveX Dynamic Link Function Library 18 Mail Server Agent 2 0 Wireless Mobile User Application Package Software 22 Web Application Server 2 4 Database 26 Objects Database Connectivity 26 Java Database Connectivity-41-(37) servlet program Java server web page enterprise Java bean interface user web browser personal computer user Java applet browser infrastructure virtual mobile messaging system virtual mobile messaging system User Virtual Mobile Message System Server User Interface Graphic User Interface Mail Service Virtual Mobile Message System Software Configuration Layer BlueGrid Server

BlueGrid-Object Request Arbitration Interface User BlueGrid servlet Enterprise Java Bean Interface Wireless Device Phone Handset

Microsoft ^ Exchange Server IBMa Lotus Dominoa Mail Server Novell Group Wisea Mail Server System Supporting POP3 / SMTP Java Virtual Machine Software Web Application Server Operating System-42- (38) 200404449 7 4 ActiveX Application 7 6 Application Designation Agent

-43-

Claims (1)

(1) (1) 200404449 Patent application scope 1 · A wireless mobile messaging system structure, including: A virtual mobile messaging service (VMMS) user for execution on a mobile device that can use java, the user includes User interface and lightweight object request arbitration interface (ORB), the user interface is used to enable input of user requests to the message server; Virtual Mobile Message System (V MS) component, the V MS component includes the Java Bean (EJB) component and mobile message server agent, wherein the EJB component is configured to operate on a Java application server to process user requests to the message server via the mobile message server agent. The mobile message server agent is Configured to interface with the message server; and a mediator server component for supporting distributed object-oriented connectivity from Java-enabled mobile devices to EJB components on the Java application server, the mediator server component includes Gateway for transparent access to EJB components on Java application servers from Java-enabled mobile devices Server, and wherein the lightweight ORB enable communication between a user may use the Java rows and actuating means mediator servo assembly on the Java application server. 2. The structure according to item 1 of the patent application scope, wherein the EJB is configured to receive user requests from the mediator server in a string format. 3. The structure according to item 2 of the scope of patent application, wherein the mediator server includes a servlet program, which is used to convert a request in string format into a Java object and to send the converted Java request object -44 -^ 4 ^ (2) (2) 200404449 to mobile message server agent. 4. The structure according to item 3 of the scope of patent application, wherein the mobile message server user includes the ActiveX component of the VMMS user, and the servlet program sends a request in the form of a Java object to the JaWin DLL (JaWin dynamic link) through the Java Native Interface (JNI) Function library). In addition, JaWin DLL converts the received Java objects into C objects and calls the VMMS user ActiveX component through the C function. 5. The structure according to item 1 of the scope of patent application, wherein the message server includes a mail server. 6. The structure according to item 5 of the scope of patent application, wherein the mail server includes a server selected from Microsoft ^ Exchanges server, IBMS Lotusa omi oa server, Novella GroupWiseS server, mail server system supporting POP3 / SMTP And at least one of a mail server system that supports IMAP / SMTP. 7 · Structure according to item 1 of the scope of patent application, where the mobile message server agent includes an ActiveX component. 8. According to the structure of the scope of patent application item 7, where the user request is in the form of C object, and the VMMS user ActiveX component will convert the received C object into a D OM (Document Object Model) object and will be converted into a DOM object The request was sent to the message server. 9. According to the structure of the first patent application, VMMS users use HTTP (Hyper File Transfer Protocol) as the communication protocol, and the gateway server is implemented in the servlet program environment on the application server. The server has a servlet program -45- (3) (3) 200404449 as a gateway to translate the HTTP protocol into the TCP / IP (Transmission Control Protocol / Internet Protocol) protocol. 1 〇 According to the structure of the scope of the first patent application, the user uses a TCP / IP socket as his communication channel. 11. The structure according to item 1 of the scope of patent application, wherein the user interface includes a J 2 Μ Ε ΜID P profile. 12. According to the structure of item 11 of the scope of patent application, in addition, the MIDP profile file version and the Java version of the J2 ME MIDP profile file support SSL (Secure Socket Layer). 13. The structure according to item 1 of the patent application scope, wherein the VMMS component is configured to support the HTTPS (Secure Hyper File Transfer Protocol) protocol. 1 4 · Structure according to item 1 of the scope of patent application, in which the VMS user includes software that can be executed on a mobile device that can use Java, and the software requires device memory at the level of 2-8 Kbytes. 15. The structure according to item 14 of the scope of patent application, in which the VMM S user software is burned into a device chipset that can use a Jav a mobile device. 16. The structure according to item 14 of the scope of patent application, in which the VMM S user software can be downloaded from the website or via a broadcast supply program to the device memory of a Java mobile device. 17 • The structure according to item 14 of the scope of patent application, which includes a graphical user interface (GUI) configured to be viewed through a plurality of remote, broadcast menus of respective message servers. 1 8. According to the structure of item 14 of the scope of patent application, in addition, -46- (4) (4) 200404449 VMMS user software is configured to execute in binary mode. 19. A method for implementing a wireless mobile message system structure, comprising: providing a virtual mobile message service (VMMS) user to run on a Java-enabled mobile device, the user including a user interface and a lightweight object request arbitration interface ( ORB), the user interface is used to enable the input of user requests to the message server; provide a virtual mobile messaging system (VMMS) component via the enterprise Java Bean (E) B component and the mobile message server agent, including the EJB The component is configured to operate on a Java application server to process user requests to the message server via a mobile message server agent, the mobile message server agent is configured to interface with the message server, and a mediator server Components are used to support distributed object-oriented connectivity to Java application servers from Java-enabled mobile devices. The mediator server component includes components for self-use: iava's mobile devices support transparent access to Java Gateway server for EJB components on the application server, and Level 0 RB so that the user may enable communication between the mobile device and the mediator Java server components on java application server. 20. The method according to item 19 of the scope of patent application, further comprising configuring the EIB to receive user requests from the mediator server in a string format. 2 1 · The method according to item 20 of the scope of the patent application, where the provided I-body server benefits include converting a string format request into a Java object via the serv 1 et program and sending the converted java request object to the action -47- dl-Λ I (5) (5) 200404449 message server agent. 2 2. The method according to item 2 of the scope of the patent application, wherein the mobile message server agent program includes an Active X component and its serv 1 et program through the J ava native interface (: [n 1). The request is sent to Ja W in DLL. In addition, jawin DLL converts the received Ja ava object into C object and calls the MV MS user A ctive X component through the c function. 2 3 · The method according to item i 9 of the scope of patent application, wherein the message server includes a mail server. 2 4 · The method according to item 23 of the scope of patent application, wherein the mail server includes a server selected from Microsoft ^ Exchanged server, IBMS Lotusa Dominoa server, Novella Group Wisea server, mail server system supporting POP3 / SMTP, and support At least one of IMAp / SMTP mail server systems. 25 · The method according to item 19 of the scope of patent application, wherein the mobile message server agent includes an ActiveX component. 26. The method according to item 25 of the scope of patent application, wherein the user request is in the form of a C object, and further includes converting the received C object into a DO object through the v Μ MS user Active X component, and via VMM S The user's ActiveX component sends a request in the form of a DOM object to the message server. 27. The method according to item 19 of the scope of patent application, additionally including the use of HTTP as a communication protocol dedicated to VMMS users, and the implementation of the server server in the serv 1 et program environment on the application server -48 -(6) (6) 200404449 server, the gateway server has a servlet program acting as a gateway to translate the HTTP protocol into the TCP / IP protocol. 28 • The method according to item 19 of the scope of patent application, which additionally includes the use of a TCP / IP socket as a user-specific communication channel. 29. The method according to item 19 of the scope of patent application, wherein the user interface includes a J2 ME MIDP profile. 3 〇 · The method according to item 29 of the scope of the patent application, additionally including the MIDP profile file version and the Java version of the J2ME MIDP profile file supports SSL ° 3 1 · According to the method of scope of patent application item 19, it also includes The VMMS component is configured to support the HTTPS protocol. 32. The method according to item 19 of the scope of patent application, wherein the provided VMMS user includes software running on a Java-enabled mobile device, and the software requires device memory of a level between 2 and 8 Kbytes. 3 3 • The method according to item 32 of the scope of patent application, which additionally includes burning the VMMS user software into a device chipset that can use Java mobile devices. 34. The method according to item 32 of the scope of patent application, further comprising downloading VMMS user software from a website or via a broadcast supply program to device memory that can use a Java mobile device. 35. The method according to item 32 of the patent application scope, wherein the VMMS user software includes a graphical user interface (GUI) configured to be viewed through a plurality of remote, broadcast menus of respective message servers. 3 6 · The method according to item 32 of the scope of patent application, further comprising -49- ii; Λ Λ (7) 200404449 VMMS user software is configured to execute in binary mode. -50-