Apparatus and methods for operation of a wireless communication system

Apparatus and method for coordinating wireless communication systemTechnical field

[0001] The present invention relates to an apparatus and method for coordinating a wireless communication system.

Background technique

[0002] In the function of modern society, obtaining information is an important element. Improvements in information flow have enhanced people's ability to interact with other people and their ability to respond to changing needs.

Summary of the invention

[0003] In one aspect of the present invention, a method is provided, including:

[0004] determining the private status of information obtained on the mobile wireless device, the information being at least partially stored on the mobile wireless device;

[0005] Based on the private state and the identity verification corresponding to the private state, the data in the mobile wireless device is synchronized with the wireless server, the data is associated with the information, and the mobile wireless device registers with the wireless server and Be able to register with one or more other wireless servers, the mobile wireless device can integrate multiple strategies, each strategy from a separate service, so that the integration of the strategy includes specifying the main service, the strategy of the main service compared to other services The strategy is priority.

[0006] In another aspect of the present invention, a method is provided, including:

[0007] determining the private status of information obtained on the wireless device, the information being at least partially stored on the mobile wireless device;

[0008] Based on the private state and the identity verification corresponding to the private state, the data in the wireless server is automatically synchronized with the mobile wireless device, the mobile wireless device is registered with the wireless server, and the mobile wireless device can register with one or More other wireless server registrations.

Description of the drawings

[0009] The embodiments of the present invention are shown in the drawings by way of example and not limitation, in the drawings:

[0010] FIG. 1 illustrates features of an embodiment of an architecture for operation of a wireless entity that uses a wireless infrastructure to deliver information content.

[0011] FIG. 2A illustrates features of an embodiment of the architecture of a wireless system including a wireless server.

[0012] FIG. 2B depicts an embodiment of a wireless architecture, which illustrates the relationship between a mobile wireless client and multiple wireless servers.

[0013] FIG. 3 illustrates features of an embodiment of a mobile wireless client associated with multiple wireless servers in a shared group arrangement;

[0014] FIG. 4 shows features of an embodiment of a method for establishing wireless server capabilities on an electronic system to provide a staging area for wireless communication on the electronic system.

[0015] FIG. 5 shows features of an embodiment of a method for synchronizing wireless entities based on a shared basis.

[0016] FIG. 6 shows features of an embodiment of a method for browsing a wireless server from a mobile wireless device.

CN 101448317 Β

[0017] FIG. 7 shows a feature of an embodiment of a method of selecting content from a wireless server and providing content to the mobile wireless device based on a command from a mobile wireless device.

[0018] FIG. 8A shows features of an embodiment of a method that includes a mobile wireless device accessing and controlling an application executable on a wireless server.

[0019] FIG. 8B shows a feature of an embodiment of a method that includes a wireless server executing an application residing on the wireless server under the control of a command set from a mobile wireless client.

[0020] FIG. 9 shows features of an embodiment of an arrangement in which a home-based wireless server is connected to a home personal monitoring device, wherein the home-based wireless server is communicatively connected to a mobile wireless client.

[0021] FIGS. 10A, 10B, and 10C show an embodiment of a system and method in which a mobile wireless client is used with more than one wireless server.

[0022] FIGS. 11A and 11B show an embodiment of a system and method for routing email messages with external domains directly between mobile wireless clients.

[0023] FIG. 12 shows an embodiment of a method for managing mobile wireless clients.

[0024] FIG. 13 shows an alternative embodiment of a method of managing mobile wireless clients.

[0025] FIG. 14 illustrates features of an embodiment of a wireless system that can be employed in the architecture of FIG. 1 or FIG. 2.

[0026] FIG. 15 illustrates features of an embodiment of an information content management subsystem.

[0027] FIG. 16 illustrates features of an embodiment of a wireless mobile device.

[0028] FIG. 17 features of an embodiment of a user map.

[0029] FIG. 18 illustrates features of an embodiment of a content retainer.

[0030] FIG. 19 illustrates features of an embodiment of a content holder.

[0031] FIG. 20 illustrates features of an embodiment of appointment data.

[0032] FIG. 21 illustrates features of an embodiment of memo data.

[0033] FIG. 22 illustrates features of an embodiment of an address book entry.

[0034] FIG. 23 illustrates features of an embodiment of a recurrence table.

[0035] FIG. 24 illustrates features of an embodiment of a synchronization table.

[0036] FIG. 25 illustrates features of an embodiment of a content holder table.

[0037] FIG. 26 illustrates features of an embodiment of a user configuration table.

[0038] FIG. 27 illustrates features of an embodiment of a method of presenting information content.

[0039] FIG. 28 illustrates features of an embodiment of a method of synchronizing information content.

[0040] FIG. 29 illustrates features of an embodiment of a method for adding users to a wireless server.

[0041] FIG. 30 illustrates features of an embodiment of a method for deleting a user from a wireless server.

[0042] FIG. 31 illustrates features of an embodiment of a method of distributing information content.

[0043] FIG. 32 illustrates features of an embodiment of a method of processing information content.

[0044] FIG. 33 illustrates features of an embodiment of a method of processing information content.

[0045] FIG. 34 illustrates features of an embodiment of a method for deleting shared information content.

[0046] FIG. 35 illustrates features of an embodiment of a method for deleting shared information content.

Detailed ways

[0047] The following detailed description refers to the accompanying drawings, wherein the accompanying drawings schematically illustrate the details and details that can implement the present invention.

CN 101448317 Β

Examples. These embodiments are described in sufficient detail to enable those skilled in the art to implement the embodiments of the present invention. Other embodiments can be utilized, and structural, logical, and electrical changes can be made without departing from the subject matter of the present invention. The various embodiments disclosed herein are not necessarily mutually exclusive, and some embodiments may be combined with one or more other embodiments to form new embodiments. Therefore, the following detailed description should not be regarded as having a limiting meaning.

[0048] FIG. 1 illustrates an embodiment of an architecture for operation of a wireless entity that uses a wireless infrastructure to deliver information content. The example architecture includes a group coordinator (or group coordinator) 105, and the group coordinator 105 provides various services to a group 110 of mobile wireless devices. The mobile wireless device may include, but is not limited to: mobile phones, portable computers, personal digital assistants (PDAs), and other devices that users can conveniently carry and provide wireless communication. Mobile phones include wireless communication devices and are commonly referred to as cellular phones. Mobile phones can include a wide range of communication devices, from portable phones with limited functions beyond voice communication to portable phones that can provide personal computer functions. Here, a personal computer (PC) refers to a computing device that has an operating system (OS) that allows individuals with little or no knowledge of the underlying hardware and software to operate the PC to control the personal computer, without the need for a typical authoring computer The program can operate the PC by the individual who operates the computer. The portable computer may include a portable personal computer (PC). An example of a portable PC is a laptop or notebook computer, which typically has a display screen, keyboard, underlying hardware and software, and display pointing devices, all of which are integrated in a housing that can be carried by an individual. Some PDAs can be regarded as a type of portable computer.

[0049] The group coordinator 105 includes tools for managing the operation of the mobile wireless device group 110 under a common criterion or a set of common criteria (instrumentality) _oThe group coordinator 105 controls the distribution of information in the group 110. In some instances, this information is shared among one or more mobile wireless devices in the group 110. In some instances, this information may be shared among less than all mobile wireless devices in the group 110. The private state can be used to maintain and adjust the privacy of information related to the members of the group 110 and entities outside the group 110. The tool can be implemented in hardware implementation, software implementation, and a combination of hardware and software implementations. Some parts of the tool can be described in terms of algorithms and symbolic representations of data bit operations in machine memory. Here, and generally, the algorithm is conceived as a self-consistent sequence of steps leading to the desired result. These steps are steps that require physical operations and physical quantities. Usually, although not necessary, these quantities use electrical or magnetic signals that can be stored, transferred, combined, compared, and calculated. The tool can be operated to process, estimate, calculate, determine, display, and/or perform other activities related to the processing of a machine such as a computer system or similar electronic computing equipment, which will be represented as a computer system's registers and The data of the physical (electronic) quantity in the memory is calculated and converted into other data similarly expressed as the physical quantity in the computer system memory or register or other such information storage, transmission or display device. This tool can provide personalization capabilities, providing Access to other content or its combination. The tool can use distributed applications, combine two or more applications to achieve output transfer between applications with different numbers and types of software-based components, hardware to provide services from multiple different sources, the tool can be used in various Implementation on a variety of platforms, such as servers and content management systems. The tool can include or be used for subprogram codes, code libraries, application programming interfaces such as the use of Java EETM>Simple DirectMedia LayerTM (SDL) and DirectXTM interpreters, combinations thereof, or other such electronic-based functions. access.

[0050] The group coordinator 105 can access the information source 115 using the interconnection communication facility 120. The information source 115 may include a variety of sources that provide information content in various formats. The information source 115 may include information content in an open format with no restrictions on which entities can access the information content. The information source 115 may include information content in an open format that requires an entity to register to access the information content without further restrictions. The information source 115 may include information content that can be accessed based on a subscription to the information content. The information source 115 may include accessibility under private conditions managed by the corresponding information source 115

CN 101448317 Β

The content of the information asked.

[0051] Information content may include, but is not limited to: photos, documents, music, videos, audio transmissions, emails, messages, telephone communications, personalization data, calculation data, operation data, and combinations thereof. Personalized data may include, but is not limited to: a person's personal calendar entries, notes, contacts (name, address, phone number, email address, etc.), memos, and other data that is private to a person. This information content can be provided in various electronic formats. Such electronic formats may include file formats with extensions, including but not limited to: doc, dot, wpd, txt, xls, pdf, ppt, jpg, jpeg, png>bmp>gif>html>htm> zip, tif, tiff, wmf, mp3 and wavo

[0052] The interconnected communication facility 120 may include one or more that allows data to be transferred between the group coordinator 105, the mobile wireless device group 110, the information source 115, and other communication entities accessible in conjunction with the interconnected communication facility 120 Communications network. The interconnection communication facility 120 may be configured as a local area network, a wide area network, or a combination thereof. In addition, the interconnection communication facility 120 may be configured to include a private network. One or more transmission media may be used to implement the interconnected communication facility 120. Such transmission media may include one or more optical fibers, twisted pairs, cables, or wireless media. In one embodiment, the group coordinator 105 and the members of the wireless device group 100 can communicate directly without using the interconnection communication facility 120. The interconnected communication facility 120 allows the group coordinator 105 and the members of the group 110 to communicate in a wireless infrastructure that includes not sharing mobile wireless device common criteria or sets of common criteria with members of the group coordinator 105 and group 110, However, mobile wireless devices that use the same wireless infrastructure or at least part of the same wireless infrastructure.

[0053] In one embodiment, the group coordinator 105 and the members of the mobile wireless device group 110 have inherent relations (intrinsic relationshaip), so that the group coordinator 105 mostly operates based on the inherent relations with the group 110. This inherent relationship can be used to define a sharing group. A sharing group is two or more entities that share information, where these entities have a trusting relationship. The trust relationship can be directed to and controlled by an entity in the group. The group coordinator 105 may be implemented as software integrated into the machine, which provides simplified operation of the machines around the core of the group 110. The group 110 can be defined by a group of people who have public relations that can be implemented in the group coordinator 105. The group of people can range from one to thousands. For the mobile wireless device group 110, the inherent relationship can be generated through the common use of the group coordinator 105, where the group 105 shares information among group members based on the unique identifier of the user group 110, and the user group 110 is the group coordinator 105 One of the users. By installing the unique identifier of each member in the storage medium of the group coordinator 105, this relationship can be initiated to create a shared group.

[0054] In one embodiment, the communication between the mobile wireless device group 110 and the group coordinator 105 may be performed on a secure communication channel. The secure communication channel may be associated with a unique identification that establishes a group relationship of the wireless mobile device with respect to the shared group of the group coordinator 105. In some embodiments, the group coordinator 105 may be implemented as group software that can be installed on an existing machine with a controller such as one or more processors and a machine for storing instructions for the group software Readable medium. In some embodiments, the group coordinator 105 may be implemented as a system with hardware and software that perform functions for the shared group defined by the group coordinator 105 and the mobile wireless device group 110. In various embodiments, a simplified user interface (UI) may be provided to execute and operate the group software of the group coordinator 105. [0055] FIG. 2A illustrates features of an embodiment of an architecture for a wireless system including a wireless server 205. A wireless server is a server configuration that communicates with entities through a channel established by entities in a wireless network. Multiple wireless servers can be located at corresponding nodes in the wireless network. Multiple wireless servers can be located in a single node in the communication network. The wireless server can be used to implement services from network providers. The network provider provides users with access to the communication network and typically provides access to information services associated with the provided access to the communication network.

CN 101448317 Β

The wireless server 205 may be associated with multiple network providers according to the network provider services that the registered users of the wireless server 205 have signed an agreement with. The wireless server 205 can establish a client-server relationship with various systems and devices, including the mobile wireless client 210 and the web-based client 215. The wireless server 205 may be configured as a group coordinator for the mobile wireless client 210. In one embodiment, the wireless server 205 serves as a hierarchical area for distributing information content to one or more mobile wireless clients of the shared group of the wireless server 205. The wireless server 205 can communicate with mobile wireless clients through a secure wireless channel. For security, encrypted data can be used to provide the secure channel. In one embodiment, Advanced Encryption Standard (AES) may be used to encrypt data.

[0056] In various embodiments, the wireless server 205 may be configured as a set of interoperating instructions. When the set of interoperating instructions is processed by a controller such as a processor, the set of interoperating instructions will prompt Perform functions related to interactions within one or more wireless clients 210 and/or one or more web-based clients 215. The wireless server 205 can be used for one or more functional parts, such as the controller 222, router 224, distributor 226, database 228, mobile data system (MDS) 230, accessory service 232, policy service 234, synchronization service 236, message broker 238 and email proxy service 240. The email proxy service 240 provides a mechanism for the wireless server 205 to access the mail account group 241 outside the wireless server 205. The group 241 includes two or more mail accounts, such as an Internet Message Access Protocol (IMAP) mail account 243, a Post Office Protocol (POP) system account 245, a Google mail account 247, or other mail accounts 249.

[0057] In one embodiment, the wireless server 205 includes a sharing agent 207, and the sharing agent 207 is configured to, in response to the determination of the private status of the information, control the transfer from the wireless server 205 to the mobile wireless client based on a shared basis. The distribution of information from the terminal 210 or other entities. The shared agent 207 can control one or more databases 228, mobile data system 230, attachment service 232, policy service 234, synchronization service 236, message agent 238, and email agent service 240. The sharing agent 207 may be distributed among the mobile data system 230, the accessory service 232, the policy service 234, the synchronization service 236, the message agent 238, and the email agent service 240 or constructed within one of these wireless service tools.

[0058] The wireless server 205 and the mobile wireless client 210 may operate as a sharing group, and the sharing group has secure communication and secure sharing through the wireless server 205. The wireless server 205 includes a list of identifiers that uniquely identify each mobile wireless client 210 belonging to a user and also a user of the wireless server 205. The establishment of a unique identifier in the wireless server 205 and each corresponding mobile wireless client 210 can define a trust relationship to the shared group. The identity of each mobile wireless client can be associated with its Secure Remote Password (SRP) key. When connecting to a wireless network, the SRP key can be used for authentication. The SRP key provides a unique identifier for the wireless server 205, and can also indicate the use of a secure channel. The SRP key can be used to register the wireless server 205 and determine that the wireless server 205 has a unique relationship with the wireless client, so as to communicate with the network infrastructure. The SRP key also allows the wireless client to identify the wireless server 205 on the direct plug-in channel and the insecure Wi-Fi channel. According to the security needs of the situation, the SRP key can be implemented in any acceptable way. Such implementations can range from simple combinations such as current data and time to the use of complex cryptographic algorithms. The simple implementation can be used in environments that do not have strict safety requirements. When security concerns are high, complex cryptographic algorithms can be used. The use of SRP keys can achieve a combination of various security measures.

[0059] A shared group can have multiple levels of private status. Private states may include, but are not limited to, states owned by users associated with one mobile wireless client 210, states shared between two or more mobile wireless clients 210 that are less than all mobile wireless clients 210, Shared state among all mobile wireless clients 210, and

CN 101448317 Β

In addition to being shared among all mobile wireless clients 210, the state is shared or accessed by entities outside the group of mobile wireless clients 210. The status shared or accessed by entities outside of the mobile wireless client 210 group may include the accessibility permitted for specified entities to access.

[0060] The sharing agent of the wireless server 205 may be operated to make the information content available to the mobile wireless client 210. Such information content may include one or more audio, video, text, or a combination thereof. An agent is a software entity that is a collection of machine-executable instructions that can be executed with a certain degree of autonomy in order to complete tasks on behalf of its user's machine. Typically, an agent is defined by its behavior and can perform its functions based on the criteria contained in its instruction set. Typically, it is not necessary to directly execute the proxy code as required, and the proxy code operates continuously based on its instructions to perform one or more activities. The capabilities associated with the agent include, but are not limited to: task selection, prioritization, purpose-oriented behavior, decision making without human intervention, and integration with other components in the form of communication and coordination. Typically, the agent analyzes the context of the activity and reacts appropriately to it, the activity being the activity in which the agent operates. The sharing agent can perform activation and perform its functions based on the occurrence of an event or the settings in the wireless server. For example, the reception of a specified type of data in the wireless server 205 can initiate the activity of the sharing agent to distribute the data based on the stored criteria. Another example includes the selection of a feature by the user of the wireless server 205, resulting in a change in the setting, which is an event that initiates the activity of the shared agent.

[0061] The wireless server 205 can be implemented in various configurations. The wireless server 205 may be configured in a hardware configuration, the hardware configuration including a machine-readable medium having machine-readable instructions for performing functions to implement communication operations between the wireless server 205 and the mobile wireless client 210. Such a hardware configuration may include an integrated structure set up in a manner similar to a desktop computer. Other hardware configurations can be used for the wireless server 205. The wireless server 205 may be configured as group software that can be installed on the machine. In one embodiment, the wireless server 205 is configured on a personal computer to provide private information, information generated on the personal computer, and shared information to one or more mobile wireless clients 210 in a wireless manner. A system incorporating the wireless server 205 may operate as a group-oriented system, and such a system has limited management associated with the operation of the wireless server 205. The system may include a user interface to manage the wireless server 205 based on a set of management parameters, where the set is managed by guides and lists generated by instructions. The wizard is a collection of execution instructions, which asks the user for input to guide the user through the steps to complete the task.

[0062] Various features of the wireless server 205 (some of which are illustrated in FIG. 2) may be implemented by hardware, software, and/or a combination thereof. These features can be configured to operate as a proxy for the wireless server 205. In various embodiments, multiple features can be combined in a single agent to manipulate these features.

[0063] The controller 222 may be used to manage the database 228, the router 224, and the distributor 226, and to adjust the operations of the MDS service 230, the accessory service 232, the policy service 234, the message service 238, and the synchronization service 236. The router 224 is used to route the communication content to the entity. The router 224 is operated to control communication to mobile wireless clients selected from the mobile wireless clients 210. Such communication can be provided using a format selected from the following: email message, instant message communication, paging message, text communication, telephone call, or other formats. The distributor 226 may be used to control the implementation of services on the wireless server 205. Based on the obtained permission to use the wireless server 205 or a specific service in the wireless server 205, the allocator 226 may synchronize access to the service based on the permitted time period and the time when the permission is obtained.

[0064] The database 228 may store maintained, processed, and transmitted information. The database 228 may be configured as a distributed database within the wireless server 205. The database 228 can be queried and manipulated using structured query language (SQL). Other query and storage mechanisms can be implemented. The database 228 may include information stored in a memory external to the wireless server 205 that is accessible when SQL is applied. The database 228 may include users with the wireless mobile wireless client 205

The associated information includes the user ID of each mobile wireless client. Each user identification can be associated with the user's wireless service account. The database 228 may be constructed such that the table includes the correspondence between the content and the folder associated with the content, the private status of the content, and the correspondence between the private status and authorized users of the content. Information content may include, but is not limited to: calendar data, address book, message board, task monitor, photo data, music data, video data, text data, user settings, preferences, usage data, or a combination thereof.

[0065] The MDS 230 can operate together with the sharing agent 207, and in response to the determination of the private status of the information, control the distribution of information from the database 228 based on the sharing basis. The information may include the following: one or more interactive calendars, address books, message boards, task monitors, or other information content. The MDS 230 may include a resource agent configured to make information content collected from a source outside the system available to the mobile wireless client 210. In one embodiment, the MDS 230 may work with a video agent that is configured to access a video program source external to the wireless server 205, and make the video content from the video program source available to everyone authorized to access the video content. Two mobile wireless clients 210 are available. The video content can be routed through the wireless server 205. The wireless server 205 may include a folder associated with the storage of video content in a memory accessible by the wireless server 205. Optionally, the wireless server 205 may set a path for directly transferring the video content from the video program source to each authorized mobile wireless client 210. The wireless server 205 may include an interface for accessing video program sources via a wired network, an optical fiber network, and a wireless network.

[0066] The MDS 230 can coordinate the retrieval and display of information content with the accessory service 232. The accessory service 232 can manage the browser inside the wireless server 205 to browse the media files stored on the wireless server. The browser can be controlled through a user interface integrated in the wireless server 205, or operated under the guidance of a browser in the mobile wireless client 210. The browser can be used to select a media file by a user of one of the wireless server 205 or the mobile wireless client 210. A transfer agent can be used to send the selected media file to the mobile wireless client corresponding to the browsing activity. The transfer may be in response to receiving a selection indicator from the associated mobile wireless client. When performing a browsing activity on behalf of a mobile wireless client, the wireless server 205 may provide the associated mobile wireless client with a representation of each media file accessed in the browsing activity, so as to provide an option for selecting one or more multimedia files. basis. The representation of each media file can be implemented as a thumbnail of each media file.

[0067] The policy service 234 may be configured as a flow control agent that restricts the information flow of each mobile wireless client 210 in response to a communication policy. Such an agent may be referred to as a server policy agent SPA. The communication strategy includes a set of rules that regulates the use of voice communication services on multiple mobile wireless clients. The communication strategy may also include operating instructions for adjusting the use of the network outside the system. For example, the communication strategy can adjust the flow of information from each mobile wireless client 210 to entities on the Internet. Such a communication strategy can be set as a set of strategies, and the strategies in the set can be applied to one or more mobile wireless clients 210. This strategy can adjust email message flow, instant message communication flow, paging message flow, text communication flow, and/or telephone call flow.

[0068] The synchronization service 236 includes a synchronization engine for automatically copying information to each mobile wireless client 210 authorized to access the information. In one embodiment, the information can be automatically transferred to the shared folder controlled by the database 228 according to the distribution of the information. The shared folder can be classified by the type of its content or the identity of the entity allowed to access the content. The authorized entity may be one or more mobile wireless clients 210, and optionally, may include other authorized entities. In one embodiment, the wireless server 205 is operated to automatically provide the data to the wireless server outside the system through the synchronization service 236 once the data is transferred to the shared folder, where the identified shared folder is associated with the user ID , The user identification is associated with at least one mobile wireless client 210. This data can include but is not limited to: personal calendar

CN 101448317 Β

Data, photo data, music data, video data, text data, or a combination thereof.

[0069] The message agent 238 includes an email agent for supporting the email service of the mobile wireless client 210 associated with the user identification. The email service includes coordinating sending and receiving emails from each email domain corresponding to the user identification. Using the configuration of the group-oriented wireless server 205, the message agent 238 can be used to control all emails associated with the mobile wireless client 210. The operation of the message agent 238 can be coordinated with the email agent service 240 to collect emails from the mail domain group 241 outside the wireless server 205, where the recipient of each collected email corresponds to the user ID, so The user ID is one of the group users of the wireless server 205. E-mails can be collected using a protocol, which is the protocol under which the host e-mail domain runs. Such a protocol can be a standard protocol or a proprietary protocol (proprietary protocol)_oPrivate email domains can use this private protocol. The message agent 238 and/or the email agent 240 may be configured to route email messages corresponding to one or more mobile wireless clients without processing through the email domain identified in the electronic message. After the e-mail is routed to the corresponding mobile wireless client, the e-mail message can be processed through the identified one or more e-mail domains. Logging can be used to record such processing in order to ignore the activity of preprocessing email messages in the email domain.

[0070] In one embodiment, the wireless server may coordinate a backup procedure with one or more mobile wireless clients 210. The wireless server 205 may store configuration data in a memory inside the wireless server 205, where the configuration data provides information for configuring and/or operating the wireless server 205. In order to provide a backup to restore the configuration of the wireless server 205, the wireless server 205 may automatically provide configuration data to one or more mobile wireless clients 210. Using the configuration data stored in more than one mobile wireless client 210, a reconfiguration strategy can be used to restore the configuration to the wireless server 210. The reconfiguration strategy can provide various features for providing configuration data to the wireless server 210. The features can include a sequencing process for providing configuration data and/or levels, which identify Which mobile wireless client 210 controls the resupply of the configuration data. The mobile wireless client 210 running as a backup of the wireless server 205 may be a handheld mobile wireless client or a client set as a wireless portable computer. The backup process may be associated with a user ID of the mobile wireless client, and the user ID indicates that the mobile wireless client belongs to the sharing group of the wireless server 205. In one embodiment, external The server stores configuration data, where the external server is associated with one or more sharing groups of the wireless server 205. For a system that incorporates a wireless server as a part of the system, in addition to the configuration data of the wireless server 205, the configuration data of the system can be automatically stored in the shared group of the wireless server 205, or with the wireless server 205 in the shared group. At least one client is associated with an external system.

[0071] In one embodiment, the machine-readable medium stores instructions, and when the machine executes the instructions, the instructions cause the machine to operate as a wireless server. As a wireless server, the instructions cause the machine to communicate with multiple mobile wireless clients, manage the information in the database for the wireless server (including storing information associated with the user of the mobile wireless client), and respond to private information The status is determined, based on the sharing basis, and the information is distributed from the database. The information associated with the user may include a unique user identification for each mobile wireless client. Using a unique identifier established only in the wireless server and each corresponding mobile wireless client, the wireless server and the mobile wireless client define a trust sharing group. In one embodiment, the managed information may include one or more of the following: interactive calendar, address book, message board, task monitor, photo data, music data, video data, text data, or a combination thereof.

[0072] In one embodiment, the instructions to cause the machine to operate as a wireless server may include one or more instructions for controlling communication to the mobile wireless clients of the shared group. Communication control can include controlling the format, permission

CN 101448317 Β

Allow communication in a format selected from the following: email message, instant message communication, paging message, text communication, or phone call. In one embodiment, the instructions for making the machine operate as a wireless server may include one or more control instructions for controlling the strategy of managing the information flow from the members of the sharing group.

[0073] In one embodiment, the instructions for making the machine operate as a wireless server include instructions for collecting emails in the wireless server from one or more mail domains outside the wireless server, and instructions for supporting and user identification The e-mail service instructions of the associated mobile wireless client, and each instruction collects e-mails corresponding to a user ID. The instructions may include one or more instructions for routing email messages between one or more mobile wireless clients without processing through the email domain identified in the email message.

[0074] In one embodiment, the instructions for operating the machine as a wireless server may include one or more instructions for making information content collected from sources outside the system available to mobile wireless clients. In order to make the information available to the mobile wireless, one or more instructions are provided for automatically copying the information from the wireless server to each mobile wireless client authorized to access the information. The type of information that can be accessed by the mobile wireless client may be provided by one or more instructions for sending to the mobile wireless client a representation of each media file that the mobile wireless client is authorized to access stored on the wireless server. The thumbnail of each media file can be used for such a representation. In one embodiment, the instructions for operating the machine as a wireless server may include one or more instructions for accessing a video program source outside the system, and for enabling video content from the video program source to be authorized to access This video content is available to every mobile wireless client. The video content can be routed through the machine where the wireless server commands are located. In one embodiment, the instructions for causing the machine to operate as a wireless server may include one or more instructions for automatically providing data in the identified shared folder associated with the wireless server to the external server. These identified shared folders can be associated with a user identification, and the user identification is associated with at least one mobile wireless client.

[0075] In one embodiment, the instructions for making the machine operate as a wireless server may include one or more instructions. These instructions are used to store configuration data for the configuration of a specified wireless server, and automatically transmit data to an external wireless server based on the occurrence of a specified event. The device provides this configuration data. The external wireless device is associated with a user identification, and the user identification is associated with at least one mobile wireless client. One or more instructions may provide for the retrieval of configuration data from the appropriate mobile wireless client. In addition, as described herein according to FIGS. 1 and 2, various functions of the wireless server can be implemented as instructions on a machine-readable medium. Various instructions may include establishing secure communication and secure sharing, where the wireless server uses a secure form of identification for each mobile wireless client.

[0076] FIG. 2B depicts an embodiment of a wireless architecture, which illustrates the relationship between a mobile wireless client and multiple wireless servers. The wireless server 205-1 acts as a group of mobile wireless clients 210-1, 210-2, ... The main wireless server of the 210-N provides the group with wireless services similar to those discussed for the wireless server 205 of FIG. 2A. The members of the group may each belong to another group associated with another wireless server, where such wireless server is a secondary wireless server. For example, wireless servers 205-2.205-3 and 205-4 are configured to groups 207, 208, and 209, respectively. The group 207 includes mobile wireless clients 211-1, 211-2, and 211-3. Group 208 includes mobile wireless clients 212-1.212-2.212-3 and 212-4. Group 209 includes mobile wireless clients 213-1 and 213-2. The mobile wireless client 210-N may also belong to the group 207, in which case the wireless server 205-2 is the secondary wireless server of the mobile wireless client 210-N. The mobile wireless client 210-2 may also belong to the group 208. In this case, the wireless server 205-3 is a secondary wireless server of the mobile wireless client 210-2. The mobile wireless client 210-1 may also belong to the group 209, in which case the wireless server 205-4 is the secondary wireless server of the mobile wireless client 210-1. In one embodiment, the mobile wireless client is assigned to a primary wireless server as a group member and as a

CN 101448317 Β

Group members are assigned to multiple secondary wireless servers.

[0077] In one embodiment, the functions of the mobile wireless client, one primary wireless server, and one or more secondary wireless servers can be controlled by the wireless server's policy, where the primary wireless server's policy governs the secondary wireless server. The strategy of the server. Assigning the primary wireless server may include negotiation. In the negotiation, in response to being assigned to a specific wireless server group, the user of the mobile wireless client agrees to use the specific wireless server as its primary wireless server. Since some wireless servers are identified as secondary, such negotiation may result in the termination of some service features provided by these servers. Due to the conflict between wireless servers, the mobile wireless client can be restricted in terms of the number of secondary wireless servers to which the mobile wireless client belongs.

[0078] FIG. 3 illustrates the features of an embodiment of a mobile wireless device 310. The mobile wireless device 310 is also referred to herein as a user equipment or UE. It can operate with more than one server, or can provide services to more than one network provider. Or a combination of server and provider to register. A UE that can be registered with more than one server or network provider may be referred to as a multi-mode wireless device, a multi-mode wireless client, and/or a multi-mode UE. Optionally, a UE that has the ability to register with multiple servers, server networks, and/or providers or connect to them at the same time may also be referred to as a multi-registration or multi-connection UE.

[0079] As shown in FIGS. 1 and 2, in the architecture, the mobile wireless device 310 can be used as a client. The mobile wireless device 310 includes a controller 322, a memory 328 communicatively connected with the controller 322, and a management system 320 operating together with the controller 322. The memory 328 may include a secure digital (SD) card. The memory 328 may be directly connected to the controller 322 and connected to the internal communication bus. The controller 322 may be implemented as one or more processors. The management system 320 is configured to manage a mobile wireless device 310, which can operate as a multi-mode wireless client with respect to each of a plurality of wireless servers. The mobile wireless device 310 is configured to share information between wireless servers, where the sharing of information is based on a user identity common to the mobile wireless device and multiple wireless servers. The shared information may include user-generated data, as well as information obtained from sources other than the mobile wireless device 310 and the wireless server. In one embodiment, the mobile wireless device 310 may be a member of a shared group of each wireless server.

[0080] The mobile wireless device 310 may be set as a simple communication device or a communication device with a large number of features beyond voice communication. Since the controller 322, the memory 328, and the management system 320 provide the underlying foundation, the mobile wireless device 310 may include a speaker 330, a display 331, a keyboard 333, a presentation control 335, a power interface 337, or a combination thereof. The presentation control 335 may include a control for guiding the visual presentation on the display, a control for adjusting the volume of the speaker 330, and a control for enhancing audio, visual use, and management of the mobile wireless device 310 that may be operated by the user. The mobile wireless device 310 may include a camera 339, a headset interface 34 for a headset, a USB interface 343, other interfaces 345, or other options accessible to the user. A graphical user interface for the display 311 may be provided for displaying the icon 337 to provide a quick presentation to the user. The mobile wireless device 310 may include other capabilities that are not directly visible to the user, such as Bluetooth capabilities, access to Wi-Fi networks, and various other capabilities. The mobile wireless device 310 may be configured as a handheld mobile wireless device, a portable wireless computer, or a combination thereof.

[0081] In one embodiment, the mobile wireless device 310 is configured as a member of a shared group that owns at least one wireless server. The management system 320 operates to manage and adjust the activities of the mobile wireless device 310 and the sharing group. The management system 320 may include an email agent 321, a policy agent 323, a synchronization agent 325, a browsing agent 327, and a positioning system 329. The email agent 321 manages the reception and transmission of emails of the mobile wireless device, and is configured to manage its emails through at least one wireless server. A secure channel with a wireless server can be used to transfer emails via a wireless server. The secure channel may be associated with the unique identifier of the mobile wireless device 310. Similarly, the wireless server defines the group relationship between the two entities to maintain the identifier.

CN 101448317 Β

Π/page 37

[0082] The policy agent 323 controls the flow of information and the progress of the interaction with the wireless server based on settings or rules or instructions. Such an agent in a mobile wireless device may be referred to as a UE policy agent UEPAo. Although the mobile wireless device 310 may register (register) with one or more wireless servers in an information and control sharing mode, the mobile wireless device 310 and each of these The wireless server has its own respective policy agent. UEPA is a separate entity from SPA. In one embodiment, the information flow policy in the mobile wireless device 310 may be based on the identification of the wireless server, the wireless server is part of a sharing group, and the mobile wireless device 310 is a member of the sharing group. If the mobile wireless device 310 is a client of multiple wireless servers, and for these wireless servers, the mobile wireless device 310 and each wireless server are in a shared group, the policy agent 323 determines that it is used to operate between multiple wireless servers and to communicate with each other. A control command for multiple wireless servers to operate individually. The policy agent 323 can apply various criteria. A set of criteria may depend on the wireless service to which the mobile wireless device 310 subscribes. Another set of criteria may depend on the group relationship of each wireless server. The sharing relationship with the wireless server may involve secret information, which may restrict the manner in which the mobile wireless device 310 operates and controls the data flow between the shared groups to which it belongs. The policy agent 323 may include selecting a wireless service Compared with other wireless servers, the server serves as a strategy to dominate the wireless server. The dominant or primary wireless server is identified, and the priority of the rule set can be determined according to the selection of the dominant wireless server.

[0083] If there is no overriding rule for selecting the primary wireless server, the positioning system 329 can be used in combination with the policy agent 323 to establish the used policy based on the relative position of the mobile wireless device 310. The positioning system 329 can be used to determine the location of the mobile wireless device relative to each wireless server. Based on the relative position, the wireless server that is considered to be the closest to the mobile wireless device 310 can be selected as the main wireless server. The positioning system 329 may include the use of a global positioning system (GPS) in the mobile wireless device 310. In one embodiment, the management system 325 may use the positioning system 329 to determine whether the mobile wireless device 310 is only within the local area network of one wireless server. The local area network may be a Wi-Fi network. Determining the closest wireless server in a local area network such as a Wi-Fi network can be used to determine the signal strength associated with each wireless server. In one embodiment, a secure control channel from the mobile wireless device 310 to the wireless server can be used to determine whether the mobile wireless device is within the Wi-Fi network associated with the wireless server.

[0084] The synchronization agent 325 may be used to automatically interact with wireless servers that are identified as members of the shared group of the mobile wireless device 310. Once a communication is received from the wireless server: the communication indicates that the wireless server has information associated with the identifier, and the identifier is associated with the mobile wireless device 310, once the information is downloaded from the wireless device, the synchronization agent 325 This information can be automatically stored in the memory 328. The synchronization agent 325 may also update the table to identify the download information with respect to the assigned folder, the information source, and/or the private status of the information. The synchronization agent 325 may also upload the information to the wireless server based on the relative status of the wireless server with respect to the information. As the information is assigned to the folder, the synchronization agent 325 uploads the information to the wireless server, which is the wireless server identified in the mobile wireless device 310 as authorized to automatically receive the information. The transfer from the mobile wireless device 310 to one or more wireless servers in response to the synchronization agent 325 may be performed through a secure channel established by the mobile wireless device 310. The information that can be uploaded automatically includes, but is not limited to: personal calendar content, photo content, music content, video content, text content, or a combination thereof.

[0085] The browser agent 327 provides the ability to browse folders in the mobile wireless device 310 to select files in the mobile wireless device 310, view content on the display 331 or listen via the speaker 330 or other suitable listening device The content. The browsing agent 327 may provide the ability to browse folders in the wireless server, and the mobile wireless device 310 is in a sharing relationship with the wireless server. The browsing agent 327 can control from the mobile wireless device 310 to no

CN 101448317 Β

The command of the line server is generated, and the command is used to browse the folder of the wireless server that the mobile wireless device 310 is authorized to access. Such commands include selection of information content to be downloaded from the wireless server to the mobile wireless device 310. In one embodiment, the mobile wireless device 310 receives thumbnail content representing the file being browsed in the wireless server. In response to the selection of the thumbnail through the graphical user interface of the mobile wireless device 310±, the information content can be downloaded from the wireless server to the mobile wireless device 310. The downloaded information content may include personal calendar data, photo data, music data, video data, text data, or a combination thereof. When transferring files from the wireless server to the mobile wireless device 310 in response to the selection activity of the browsing agent 327, the synchronization agent 325 may be used in combination. The transfer of information content from the wireless server to the mobile wireless device 310 may be performed on a secure channel established by the mobile wireless device 310.

[0086] In one embodiment, the mobile wireless device 310 may operate in conjunction with a wireless server to serve as a backup for the wireless server. The memory 328 may be used to store configuration data of the wireless server. Based on a scheduling basis, or on an event-driven basis, the mobile wireless device 310 receives configuration data from the wireless server. The configuration data may be received as data that overwrites the configuration data in the memory 328. The configuration data may be received as an increment or change of configuration, where the changed data overwrites the corresponding portion of the configuration data in the memory 328. According to the request of the wireless server, the configuration data can be uploaded to the wireless server.

[0087] In one embodiment, the machine-readable medium stores instructions, which when the mobile wireless device executes the instructions, cause the mobile wireless device to operate as a client of multiple wireless servers. The mobile wireless device may be a handheld wireless device. The mobile wireless device may be a portable wireless computer. In one embodiment, the instructions cause the mobile wireless device to operate as a multi-mode wireless client for each wireless server and share information with these wireless servers. Information can be shared based on the user identification common to the mobile wireless device and the wireless server. This instruction can effectively configure mobile wireless devices in multiple sharing groups, and a sharing group is for each wireless server that has a sharing relationship with the mobile wireless device. The user identification information can continue to be used to establish secure communication and protected sharing between mobile wireless devices and wireless servers in a sharing group arrangement. The shared information can include user-generated data.

[0088] In one embodiment, the instructions for operating the mobile wireless device as a multi-mode wireless client may include instructions for adjusting the functions of the mobile wireless according to a stored strategy. The strategy may depend on which wireless server is adopted as the primary or dominant wireless server relative to other wireless servers. In one embodiment, the main wireless server can be selected by determining the location of the mobile wireless device corresponding to other wireless servers through application instructions. The instructions for determining the location can be used with GPS systems in mobile wireless devices. The instruction can lead to determine that the mobile wireless device is in the local area network of a wireless server. The local area network may be a Wi-Fi network. One or more instructions can be used to use the secure control channel to determine whether the mobile wireless device is in the Wi-Fi network.

[0089] In one embodiment, the instructions for operating the mobile wireless device as a multi-mode wireless client may include instructions for controlling the flow of information. The instructions for adjusting the information flow may include, but are not limited to: instructions for managing the reception and transmission of e-mails through at least one wireless server in a sharing group with the mobile wireless device, and instructions for using the mobile wireless device on the mobile wireless device. The browser is used to browse files on a wireless server in a sharing group with the mobile wireless device, and instructions for synchronizing the information content stream from the wireless server in a sharing group with the mobile wireless device to the mobile wireless , Instructions for synchronizing the information content flow from the mobile wireless to the wireless server in a sharing group with the mobile wireless device. The information content may include, but is not limited to: calendar data, photo data, music data, video data, text data, or a combination thereof.

[0090] In one embodiment, the instructions for operating the mobile wireless device as a multi-mode wireless client may include instructions for working in a backup process in conjunction with one or more wireless servers. The instruction can guide the move

CN 101448317 Β

Mobile wireless automatically stores the configuration data from the wireless server, and records the data storage and its associated wireless server records in a log record. The configuration data can provide information to the system to establish the system as a wireless server. The instruction can guide the mobile wireless device to transmit configuration data to the appropriate wireless server according to the request of the wireless server.

[0091] In addition, the various functions of the mobile wireless device described herein according to FIGS. 1, 2 and 3 may be implemented as instructions on a machine-readable medium in the mobile wireless device. Various instructions may include using a secure form of identification associated with the mobile wireless device to establish secure communication and secure sharing with the wireless server, the mobile wireless device and the wireless server being in different sharing groups.

[0092] FIG. 4 shows a feature of an embodiment of a method for establishing a wireless server capability on an electronic system to provide a platform for wireless communication on the electronic system. At 410, the storage of data on the mobile wireless device is controlled. The data may include instructions for installing a software program on the electronic system to provide the electronic system with the function of a wireless server. The installation instruction may include an instruction to install the software in stages based on the response received from the electronic system during the installation sequence. The installation instructions may be organized with instructions from the mobile wireless device to initiate the installation, and the installation is completed through a network such as the Internet. The installation instruction may be organized with an instruction to initiate the installation from the mobile wireless device, and the installation is completed by downloading at least a minimum part of the program to make the electronic system operate as a wireless server. Mobile wireless devices can provide a complete version of the wireless service software during the download process. Before providing mobile wireless devices commercially, at factory manufacturing or other process points, one or more installation process options may be provided for the mobile wireless device. The mobile wireless device provided with the wireless server installation capability may be a handheld wireless device. The mobile wireless device provided with the wireless server installation capability may be a portable wireless device.

[0093] At 420, download at least a portion of the data from the mobile wireless device to the electronic system. The download for establishing the wireless server function can start from the connection of the mobile wireless device with the electronic system, and the connection uses a physical connection medium that can be connected to an interface on the mobile wireless device and can be connected to a compatible interface on the electronic system. The interfaces on the electronic system of the mobile wireless device may all be USB interfaces. Other media can be used to physically connect mobile wireless devices and electronic systems, including but not limited to: optical fiber media or other cable media. A converter that provides the connection of two different types of interfaces can be used to achieve the compatibility of the interface between the electronic system and the mobile wireless device. The graphical user interface on the display of the mobile wireless device can be used to provide installation guidance. A graphical user interface on the display of the electronic device can be used to provide installation guidance. After the graphical user interface on the display of the mobile wireless device guides the execution of the initial installation, the graphical user interface on the display of the electronic device can be used to provide installation guidance.

[0094] After the initial delivery of the instructions, the sequence of instructions is provided on the display of the electronic system to guide the user through the installation process. You can use the wizard installation tool to perform this sorting. In one embodiment, the installation is provided in an automated manner, where only limited input by the user is required. The user may be asked to accept or reject the license agreement. A response indicating a rejection may lead to the termination of the installation of the wireless server software. This termination can lead to the termination of further software downloads. If the software has already been downloaded, such termination can cause the installation of the software to be terminated as an executable entity. The installation instructions may include providing protection to prevent the downloaded software from being installed without conveying acceptance of the license agreement. Indicates that the accepted response leads to further processing of the installation of the wireless server software. The further processing may include downloading further data from the mobile wireless device and completing the installation. The further processing may include downloading further data from the Internet or similar networks and completing the installation. The additional information provided by the user collected during the installation step may include: name, email address, and country. The user may be required to provide his secure remote password (SRP) key. Optionally, during the installation process, one or more of these personal data items can be automatically downloaded from the wireless mobile device.

CN 101448317 Β

[0095] As the wireless server is installed on the electronic system to serve as the group coordinator of the wireless mobile device that initiates the installation process, the SRP key can be automatically downloaded from the associated mobile wireless device. Optionally, the SRP key can be evaluated during the security process with another system. The downloading of the mobile wireless device, user and security information can be performed using the physical connection of the mobile wireless device and the electronic system. The downloaded SRP can be controlled through instructions in the mobile wireless device or using instructions downloaded from the mobile wireless device to provide interactive processing of the SRP downloaded and stored on the electronic device. In addition, the name, email address, and country can also be automatically installed from the associated mobile wireless device. Through the installed wireless server, it is possible to manage and guide the group of the installed wireless server and the activated mobile wireless to join other mobile wireless devices to form a larger trust sharing group. The Wi-Fi capabilities of the installed wireless server can be used to add mobile wireless devices to the shared group of installed wireless servers.

[0096] Through the network connection of the electronic system incorporating the installed wireless server, or through the installed mobile wireless device or other authorized mobile wireless devices in the shared group of the wireless server, the wireless server can be automatically updated . Updates can be provided on the wireless server, so that users can guide when updates occur, including allowing automatic updates. Periodic re-licensing can be realized, in which permission rejection is followed by automatic shutdown of the wireless server. In addition, the refusal of the automatic update of the wireless server can be followed by the automatic shutdown of the wireless server. The shutdown event may be based on whether the automatic update has a key characteristic above a certain threshold level.

[0097] The installed software program includes a machine-executable execution set, which can be operated to be stored on an electronic system, so that the controller of the electronic system can execute these instructions to perform functions in the electronic system. In addition, the electronic system is operated as a wireless server. The controller on the electronic system can be implemented as one or more processors. The installed wireless server may include the configuration and functions of the wireless server discussed in FIGS. 1-3. The mobile wireless device performing the installation may include the configuration and functions of the mobile wireless device discussed in FIG. 3. The installed wireless service can be set as a group coordinator, the group coordinator provides a platform for sharing information with mobile wireless devices, the SRP information of the mobile wireless device stored in the wireless server as a trusted mobile wireless device Group members. The operable agents of the wireless server can include all the functions of the agents and services discussed in Figure 2, although these agents can be combined or constructed with different command settings.

[0098] FIG. 5 shows features of an embodiment of a method for synchronizing wireless entities based on a shared basis. Based on the private state and the identity verification corresponding to the private state, the information obtained in the wireless entity can be synchronized between the wireless entities. The information undergoing the synchronization process includes but is not limited to: personal calendar data, photo data, music data, video data, message data, and combinations thereof. The wireless entity may include a wireless server and a collection of mobile wireless clients of the wireless server, which together form a shared group. In one embodiment, the mobile wireless clients of the group are configured to browse files in the wireless server. In one embodiment, the wireless server is configured to provide a view of its file content to mobile wireless clients in a group authorized to view the file content of the wireless server.

[0099] At 510, the private state of the obtained and at least partially stored information is determined. The private status of the information can be determined before and/or during the partial storage of the information. In one embodiment, the information is obtained from a wireless server, which is a member of a shared group that includes one or more wireless mobiles. Devices, these wireless mobile devices are the wireless clients of the wireless server. The wireless server initiates and guides the synchronization process for the obtained information. Using the graphical user interface, the user of the wireless server can assign attributes to the acquired information, which creates the private status of the information. This information can be marked as private to the wireless server. This information can be marked as private to the user associated with one wireless mobile device of the group. This information can be marked as shared by multiple but not all users associated with the group, which is a limited private state, where each of the multiple users is related to one wireless mobile device of the group

CN 101448317 Β

United. This information can be marked as shared by all members of the group, where each user is associated with one wireless mobile device of the group. This information can be marked as shared by all members of the group and entities outside the group. The relationship with the wireless mobile devices of the group can be implemented as mapping the SRP key and user name to the wireless mobile devices in the wireless server. The marking of the attributes by the wireless server can be done by assigning information to the folder and associating the identity of the information, the private indicator, and the name of the user with the private status or other identities in one or more tables. Other procedures can be used to provide mobile wireless devices for the private state of information. Optionally, the information may have a predetermined private status with an identified authorized user, so that the wireless server receives the information and automatically allocates the information to its predetermined folder. The predetermined private status may be based on the type of information or the specific identity of the information obtained.

[0100] In one embodiment, the information is obtained in a mobile wireless device that is a member of a shared group including a wireless server. The mobile wireless device can initiate and guide the synchronization process for the obtained information. The shared group can include other mobile wireless devices. Using the graphical user interface on the mobile wireless device, the user of the mobile wireless device can assign attributes to the obtained information, which attributes produce the private status of the information. This information can be marked as private to the user associated with the wireless mobile device from which the information was obtained. This information can be marked as shared by multiple but not all users of the group, which is a limited private state, where each of the multiple users is associated with one wireless mobile device of the group. This information can be marked as shared by all members of the group, where each user is associated with one wireless mobile device of the group. This information can be marked as shared by all members of the group and entities outside the group. The relationship with the wireless mobile devices of the group can be realized by viewing the group member list stored in the mobile wireless device that obtained the information, or by viewing the group member list accessible from the wireless server. The attribute marking by the wireless server can be done by assigning information to the folder and associating the identity of the information, the private indicator, and the name of the user with the private status or other identification in one or more tables. Other procedures can be used to make information private Provide other mobile wireless devices in the group. Optionally, the information may have a predetermined private status with an identified authorized user, so that the mobile wireless device receives the information and automatically allocates the information to its predetermined folder. The predetermined private status may be based on the type of information or the specific identity of the information obtained. In one embodiment, a mobile wireless device can obtain information content, and a wireless server that shares a group state with the mobile wireless device can establish a private state for the information content.

[0101] At 520, based on the private state and the identity verification corresponding to the private state, the data associated with the information is synchronized with the wireless entity. In one embodiment, when the information obtained in the wireless server is moved to the synchronization folder, the wireless server automatically downloads the information to the mobile wireless device identified in the table as being authorized to automatically receive the information. A synchronization folder is a type of folder whose contents are designated to undergo a synchronization process. These synchronization tables provide private status and authentication for automatic downloads. A synchronization folder can be created for each group member, so that the received information associated with each folder can be automatically downloaded to the associated group member. The download by the wireless server can be based on the status of the storage facility on the target mobile wireless device. If the mobile wireless device does not have a suitable storage medium such as an SD card or other storage medium, or if the storage medium of the mobile wireless device has insufficient capacity, the download is not performed and the mobile wireless device is notified that the capacity is insufficient.

[0102] A capacity limit can be set in the wireless server. Therefore, if the size of the information to be downloaded is larger than the capacity limit, the wireless server does not send the information on the wireless channel. For file content exceeding the capacity limit, when the wireless server determines that a physical connection such as a USB connection has been established, or when a mobile wireless device accesses the Wi-Fi network of the wireless server, it can be automatically downloaded. If such a USB or Wi-Fi transmission is lost during the transfer process, the process can be aborted, and once the transmission is re-established, the process can be restarted. In addition, according to mobile wireless devices

Or other status in the wireless server to adjust the synchronization of the content. For example, if the battery capacity drops below a specified amount, you can suspend content synchronization. In one embodiment, if the battery life falls below 20% of its full power, content synchronization is suspended, and if the battery life exceeds 25% of its full power, it can continue.

[0103] The wireless server can download information to the mobile wireless device via Wi-Fi capabilities, wired cables, carrier-based networks, or a combination thereof. While the wireless server is in the process of synchronization, the mobile wireless device can display the synchronization process from the wireless server on its screen. The mobile wireless device that receives the information can assign the information to one of its folders, where the folder can be a synchronized folder on the mobile wireless device. The mobile wireless device can store the information content received during the synchronization process from the wireless server in the secure digital storage of the mobile wireless device.

[0104] In an embodiment, the wireless server downloads the synchronization indicator to the mobile wireless device in the synchronization process with the mobile wireless device sharing the group. The synchronization indicator indicates that the wireless server has obtained the information that the mobile wireless device is identified as a shared member. In the future, the identification information can be downloaded to the mobile wireless server. In response to the information being moved into a folder accessible by the wireless server, the wireless service can automatically download the indicator. The folder may be located on a system outside the system where the wireless server is located, and the wireless server is authorized to read information from the external storage medium.

[0105] In one embodiment, the information obtained in the mobile wireless device can be moved to a wireless server in a shared group of which the mobile wireless device is a member. The mobile wireless device may be configured to automatically upload the information to the wireless server when the information obtained in the mobile wireless device is moved to the synchronization folder of the mobile wireless device. The content in the mobile wireless device can be uploaded to and stored in the wireless server to provide a backup of the content. The content is not limited to a specific type of content, but can be any content on a mobile wireless device. Mobile wireless devices can upload information to wireless servers via Wi-Fi capabilities, wired cables, carrier-based networks, or a combination thereof. In one embodiment, the mobile wireless device can monitor its operating state, and adjust the synchronization process with the wireless server based on the determined state. For example, if the battery capacity of the mobile wireless device drops below a specified amount, content synchronization can be suspended. In one embodiment, if the battery life falls below 20% of its full power, content synchronization is suspended, and if the battery life exceeds 25% of its full power, it can continue.

[0106] FIG. 6 shows features of an embodiment of a method for browsing a wireless server from a mobile wireless device. At 610, the browser in the mobile wireless device is started to control the browsing of the file directory in the wireless server. The mobile wireless and the wireless server belong to a common sharing group. The user of the mobile wireless device can view the files in the file directory of the wireless server by using the graphical user interface of the mobile wireless device. At 620, a signal is generated to the wireless server to select a file in the file directory of the wireless server. The mobile wireless device may generate a signal to the wireless server to indicate that the file is to be downloaded to the storage in the mobile wireless device, and that the file will be sent as an email attachment or the attachment server of the wireless server will be used to view the file. The information content that can be browsed by mobile wireless devices includes but is not limited to: personal calendar content, photo content, music content, video content, message content, and combinations thereof. Browsing activities can include browsing files with indicators selected from these indicators, but not limited to: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3, and wavo

[0107] FIG. 7 shows a feature of an embodiment of a method of selecting content from a wireless server and providing content to the mobile wireless device based on a command from a mobile wireless device. At 710, a signal is received from the mobile wireless device, and the signal is a browser signal for browsing the directory of the wireless server. The mobile wireless and the wireless server belong to a common sharing group. At 720, in response to a browse command from the mobile wireless device, browse files in the directory. The browse command may include a selection command for selecting a file used by the mobile wireless device.

CN 101448317 Β

[0108] At 730, the content of the file selected from the directory is provided to the mobile wireless device. By downloading the file as the data to be stored on the mobile wireless device, by sending the file as an email attachment, or by using the attachment server of the wireless server to provide viewing of the file, the selected file can be sent from the wireless server to the mobile Wireless equipment. The browsed information content may include, but is not limited to: personal calendar content, photo content, music content, video content, message content, and combinations thereof. The browsing activity may include browsing files with indicators selected from these indicators, but not including: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3, and wav.

[0109] FIG. 8A shows features of an embodiment of a method that includes a mobile wireless device accessing and controlling an application executable on a wireless server. In various embodiments, the application may be different from the application used to maintain and control the wireless communication link between the mobile wireless device and the wireless server. At 810, an application executable on the wireless server is accessed from the mobile wireless device. As a member of the sharing group of the wireless server, the mobile wireless device has authorization to access the application. The authorization can be associated with the SRP key of the mobile wireless device that is also stored on the wireless server. Mobile wireless devices can access various types of applications on the wireless server. For example, a data processing application that uses a lot of memory to perform complex calculations ("data crunching) can be accessed to run it on a server instead of on a mobile wireless device. The application can reside in a wireless server. In one implementation In an example, the application resides virtually on a wireless server. The virtual residency occurs when the wireless server can access an application stored on another server. In one embodiment, the access is used for control and/or An application that monitors the functions of a facility. For facilities, the application can control and/or monitor one or more of heating management, lighting management, water management, physical security, and web camera management. It can be accessed for control and/or monitoring and main Application of the functions of different facilities.

[0110] In one embodiment, the mobile wireless device receives data about the application from the wireless server. The received data can be used to display a graphical user interface on the mobile wireless device, which can be operated as a command to launch the application. Optionally, the data of the graphical user interface for controlling and/or managing the application can be stored in the mobile wireless device. The graphical user interface of the mobile wireless device may be a mirror image of the graphical user interface of the wireless server for controlling and/or managing applications through user interaction. The graphical user interface of the mobile wireless device may have a simplified set of features that is the same as the graphical user interface of the wireless server for controlling and/or managing applications through user interaction. According to the activation of the command in the mobile wireless device, the underlying processing of the application guided by the command is executed on the wireless server.

[0111] At 820, a command is sent from the mobile wireless device to the wireless server to execute the features of the application. This feature may be different from the feature used to maintain and control the wireless communication link between the mobile wireless device and the wireless server. The mobile wireless device can receive the result of the feature execution in the wireless server. Can provide a complete analysis including various graphs and flowcharts for the calculation results. The operating status of the facility can be provided for the results from the monitoring application, including the current value of the status, the history of the status, and the trend analysis of the status. For the video camera application, the result received in the mobile wireless device may be a video of the activity monitored by the video camera. For example, a video of a storage facility can be provided to monitor the safety of the storage facility. The video of the child's living area may allow parents to monitor the activities of the child and the person who cares for the child.

[0112] In one embodiment, a private state can be generated in the mobile wireless device and attached to the result generated by the wireless server executing the application through an operation. The private status can be transmitted to the wireless server to set the accessibility of the result to other members of the sharing group and other entities that can access the wireless server.

[0113] FIG. 8B shows a feature of an embodiment of a method that includes a wireless server executing an application residing on the wireless server under the control of a set of commands from a mobile wireless client. In various embodiments, the application can

CN 101448317 Β

It is different from the application used to maintain and control the wireless communication link between the mobile wireless device and the wireless server. The mobile wireless and the wireless server belong to a common sharing group. At 910, the wireless server receives a signal from the mobile wireless client of the wireless server. In the wireless server, the mobile wireless client is identified as a sharing group member of the wireless server and an authorized user of an application accessible by the wireless server. Once the signal corresponding to the application accessible by the wireless server is received, the wireless server can send data to the mobile wireless device for display on the graphical user interface of the mobile wireless device.

[0114] At 920, in response to receiving the signal, execute an application in the wireless server, wherein the execution is performed by the wireless server under the control of the mobile wireless client. This application may be different from the application used to maintain and control the wireless communication link between the mobile wireless device and the wireless server. The applications executed by the wireless server can be stored on the wireless server, or stored in an external system accessible by the wireless server. The wireless server can execute data processing applications. The wireless server may execute applications for controlling and/or monitoring the functions of the facility. The operations of the controlled and/or monitored facility may include one or more of heating management, lighting management, water management, physical security, and management. The application can be executed by the wireless server to control and/or monitor the operating parameters of a facility different from the main facility.

[0115] The result of executing the application can be transmitted to the mobile wireless device as a simple result or with various levels of analysis and presentation results.

[0116] The private status can be attached to the result of the wireless server. The private state may be provided by a mobile wireless device that controls and/or directs the wireless server to execute and/or process applications. The private state can be updated in the database of the wireless server, and the private state involves the mobile wireless client performing control, other mobile wireless clients of the wireless server sharing members with the wireless server, and other entities accessing the wireless server.

[0117] In various embodiments, a secure connection from the home wireless server to the UE can be used to implement the ability to run home control or home monitoring programs. Various devices, such as but not limited to cameras, baby sound detection devices, other baby monitors, personal devices, personal programs, and other personal monitoring devices can be connected to a home-based wireless server, which is used by, for example, a network provider Its available network to control access to the UE. Similarly, this allows private monitoring of small businesses, including remote and secure access to inventory control charts, production charts, monitoring inventory areas and warehouses for loss control, ensuring that non-duty personnel at public counters are not threatened, and monitoring solutions Similar situations that are responsible for monitoring. Various devices can be configured to provide output that can be monitored by the UE through a home-based wireless server. Such output is safe without the use of a third party and/or without making the output publicly available, such as in the Internet type Broadcast on the facility. Such a setting allows individual UE users and wireless servers to avoid being forced to use third-party monitoring services to obtain such personal monitoring. In addition, by not making the monitored output accessible on the public Internet, this arrangement allows individual users to maintain the privacy of their homes, businesses, and personal lives. The output from the monitoring device can be provided for the security monitoring of the home and/or enterprise, and such output is provided as encrypted data.

[0118] FIG. 9 shows features of an embodiment of an arrangement in which a home-based wireless server 970 is connected to a home personal monitoring device 980, wherein the home-based wireless server 970 communicates with a mobile wireless client 850 connection. The various components of the home personal monitoring device 980 can be distributed throughout the home. Each component can be configured to perform different personal monitoring functions. The home personal monitoring device 980 may include, but is not limited to: cameras, baby sound detection devices, other baby monitors, personal devices, personal programs, and other personal monitoring devices. The components of the home personal monitoring device 980 can be connected to the home wireless server via a direct connection or a local area network. The direct connection or local area network can be a wired connection, a wireless connection, or a combination of wired and wireless connections. The local area network can be a secure or insecure home Wi-Fi network.

CN 101448317 Β

The home-based wireless server 970 is operated to connect with the UE 850 through the network 860. The network 860 can be any operable connection, including the use of private local networks and/or commercial providers. The home-based wireless server 970 may also be operated to connect with other UEs that are associated with members of the family where the home-based wireless server 970 is located, where these other UEs are registered with the home-based wireless server 970 Wireless client. The home-based wireless server 970, the UE 850, and other wireless clients of the home-based wireless server 970 can be configured according to the wireless server and multi-mode mobile wireless device embodiments discussed herein.

[0119] The UE 850 may operate as discussed for FIG. 8A, where the application includes the control and management of the home personal monitoring device 980. By using UE 850 to control monitoring, individuals can monitor and control the home environment while traveling away from home. Through the secure channel of the home-based wireless server 970 locally connected to the monitoring device 980 located in the individual's home, the individual can maintain private control of the monitoring signals sent from the home.

[0120] The home-based wireless server 970 may operate as discussed with respect to FIG. 8B, where the application includes the control and management of the home personal monitoring device 980. The home-based wireless server 970 may accept control and commands from the UE, which is a UE registered with the home-based wireless server 970 or a subset of registered UEs. Among them, the registration may include the corresponding relationship between a given UE and the family. Under the control of the UE 850, the home-based wireless server 970 provides a signal to the monitoring device 980 to obtain monitoring information. The monitoring information may include data, audio, video, image, or a combination thereof. The home-based wireless server 970 locally connected to the monitoring device 980 located in the personal home has private control over the home and the monitoring of the activities in the home. The secure channel provides a mechanism. At any time, the information obtained by the home-based wireless server 970 is provided to the UE 850 under the control of the UE 850, without the need to use a third party that is not registered with the home-based wireless server 970 to manage Monitor events. Similarly, Figure 9 is equally applicable to small business applications and home-based applications. The difference lies in which remote programs are monitored or operated. For example, a small business owner may want to use the same capabilities, types of monitors and equipment to monitor inventory levels, small production lines, storage areas Domains, current retail activities, and counter areas, and get the same benefits as the above-mentioned home owners.

[0121] Referring now to FIG. 10A, FIG. 10A shows an example of a system and method that uses a mobile wireless client with more than one wireless server. According to an example embodiment, a first wireless server 1002 is provided , It can communicate with multiple mobile wireless clients, such as mobile wireless client 1004. For example, as described elsewhere herein, the first wireless server includes configuration data associated with at least one of a plurality of mobile wireless clients supported by the wireless server 1002 (for example, client 1004), and is operable on the server The database is configured to store information associated with users of mobile wireless clients, including the user identification of each mobile wireless client. The wireless server 1002 also includes a program configured to control the distribution of information from the first database to one or more of the plurality of mobile wireless clients.

[0122] The wireless server 1002 also stores or maintains at least one policy 1006, which is associated with a mobile wireless client, such as the client 1004. The policy 1006 can be used to manage the permitted operating mode of the client 1004, and to establish various operating parameters, such as what type of Internet is allowed to the wireless client or the type or duration of telephone calls that can be made using the client 1004 . Other uses of the policy 1006 include allowing or prohibiting the user of the mobile wireless client to enable or prohibit specific features of the client 1004, such as password protection operations.

[0123] As shown in FIG. 10B, the policy 1006 may include various policy information, including but not limited to: the author of the policy 1022, the identity 1024 of any server authorized to update or modify the policy 1006, or the individual permission or setting of the policy ( Such as setting 1026, 1028 and 1030). For example, as described here, the policy 1006 can also authorize 1026 the wireless client 1004 to work with other wireless servers (such as the server 1010 in FIG.

CN 101448317 Β

Provide wireless e-mail or calendar and other server functions. The policy 1006 may also specify one or more other policy settings 1028 to 1030.

[0124] The wireless server 1002 also includes a policy service 1008, which allows a user of the wireless server 1002 to specify a policy 1006 for one or more mobile wireless clients, especially the client 1004 in the example of FIG. 10A. If allowed, The service 1008 also provides that the policy 1006 can be downloaded to the wireless client 1004. Such downloading can be guided or controlled by the policy download or modification program 1005 on the wireless client 1004.

[0125] According to an example embodiment shown in FIG. 10C, for example, in a manufacturing plant or after being initialized, the mobile wireless client 1004 may be initially loaded 1032 with an "initial" policy, such as a policy set by the manufacturing plant. For example, the policy may allow it to be replaced by a user-specified policy. For example, the policy described by the user is loaded 1034 from the first wireless server 1002 to the mobile wireless client 1004 ±. Typically, this may be determined by the UE's UEPA deal with. For example, the policy loaded by the server 1002 may stipulate that no other wireless server (such as the server 1010) can replace or modify the policy loaded by the server 1002 in whole or in part, thereby preventing the policy from being other than the server 1002. The server changes. Therefore, any attempt 1036 to load another strategy results in a mobile wireless client 1004 (or alternatively, The server attempting to modify the policy) checks the policy currently loaded on the wireless client to determine 1038 whether the policy can be changed or replaced. If so, you can make 1040 new strategies or changes to strategies, such as personal settings. If the server requires that the policy cannot be changed, prevent 1042 the policy from being replaced or modified. Accordingly, at this point, the policy establishes that one server (such as server 1002) is the primary server that controls the permissions and changes of all policies, while other servers 1010 are secondary servers, and secondary servers cannot rewrite the policies set by primary server 1002. , Unless the policy set by the server 1002 allows this.

[0126] In an embodiment, the wireless server 1002 includes a flag or field stored on the wireless server 1002, indicating whether the UEPA on the registered UE (such as the UE 1004) can modify the policy of the wireless server 1002 in the UE 1004. This flag or field can be called a policy modification flag, or, if the context is clear, it can be simply called a modification flag. In some embodiments, the modification flag may be a single bit with a value of T or F (1 or 0). Optionally, the modification flag can be more complicated, and can be implemented to indicate under what circumstances the strategy can be modified. Examples of more complex modification flags include the identities of other servers that are allowed to rewrite the server's policy, while not allowing other servers to rewrite the server's policy. As defined by the server's SPA and the UE's UEPA, any combination of strategies is possible, but some are more likely than others. For example, the SPA of the wireless server 1002 may have a policy that is logically true, that is, "T" or is defined as meaning to allow any UEPA configuration, which can be used in a good environment. Optionally, SPA can have such a strategy, that is, "F" or not is defined as meaning that UEPA cannot modify any strategy. In one embodiment, "F" or No may also indicate that any implementation of the configuration of UEPA is not allowed.

[0127] Therefore, according to an embodiment, the first wireless server 1002 (such as a company or enterprise server) may establish a policy to be loaded on the wireless client 1004, which may allow the client 1004 to interact with the server 1010. Working with other wireless servers, the server 1010 may be set up for family members or other groups associated with the user of the client 1004. This authorization may include permitting the server 1004 to synchronize with other email services or domains such as users' private or non-commercial email addresses, or to provide other services such as calendars between users of the server 1010.

[0128] Each wireless server, such as the wireless servers 1002 and 1010 operating together with the UE 1004, has its own SPA, and the UE 1004 is in a multi-registration mode with the wireless servers 1002 and 1010. The SPA of each server may have different strategies for different UEs registered with the server, even if these different UEs share information. In order to achieve

CN 101448317 Β

For different sets of policies for different UEs, SPAs can be implemented as SPA groups in the server, where each SPA is assigned to a direct subset of different UEs. These subsets may consist of one UE.

[0129] In a configuration of an SPA, the SPA may have a policy of not controlling the UE 1004. Therefore, any activity related to the UE 1004 is allowed. In some embodiments, there may be one or more servers that do not have a SPA (typically, existing servers are like this), which usually means that there is no modification flag. The server can provide modification flags without SPA, but these are currently considered to be a few examples. In some embodiments, UEPA can be set to identify the identity of the server or the provider, and apply a pre-planned set of modification rules in the UE, so no flag is required. By default, the UEPA of the UE connected to the server/provider without any modification flag or any pre-planned modification rule can be provided. This default action can be set by the UE provider, or selected by the user in some embodiments. In one embodiment, when there is no modification flag and no pre-planned modification rule set corresponding to the server or provider, UEPA is set to interpret the no modification flag condition as one of "T" or "F". "T" means that the UEPA will allow the policy modification of the server/provider's policy, and the server/provider will have a lower priority than other servers/providers. "F" means that the servers/providers policy cannot be modified, and it can be compared with other servers/providers. Compared with the provider, the server/provider has a higher priority. In a higher security environment, since servers/providers without modification flags or pre-planned modification rules will be considered as higher-risk connections, the default value is considered "T". Any server whose setting security is higher than the nominal value without modification flag (and thus may not have SPA) cannot be the main server of the UE. That is to say, in a high-security environment, the main or dominant server should always keep the software settings up-to-date, should have SPA, and should have a modification flag. If the user connects to a server that has no modification flag (and typically no SPA), it can be assumed that this is a secondary server with unknown security (untrusted). In this case, the UEPA that assigns the modified value should use the default value "T" as the modified value for the untrusted server, which means that the policy of the untrusted server is assumed to be modifiable according to the policies of other more trusted servers.

[0130] In one embodiment, the UE (such as UE 1004) is registered in multiple wireless servers (such as wireless servers 1002 and 1010). Although the UE 1004 is not limited to register with two wireless servers, the UEPA of the UE 1004 is from Each SPA of the wireless servers 1002 and 1010 receives policy information. Multiple wireless servers, such as the SPAs of wireless servers 1002 and 1010, can have a hierarchical order in which SPA provides a strategy that is completely implemented by UEPA. The hierarchy can be realized as a simple advantage, in which one SPA strategy is implemented, and other SPA strategies are not used at all. For example, if the user of the UE is a registered member of a company server and a home-based server, and the company server is designated as the dominant server and has a policy of not sharing information with registered members of the company server, it may not be implemented in the UE Different shared state policies are allocated to UEs of different members of the home-based server. Optionally, non-shared information can be limited to information obtained through the company server, so that for information other than the information obtained through the company server, the part of the non-dominant server strategy that allocates different shared states can be realized. Hierarchy can be implemented as a subset, that is, a SPA can be designated as dominating, and other SPA strategies can be implemented, or any part of other SPA strategies can be implemented. The strategy or part of it is a subset of the strategy that governs the SPA and does not interfere with the strategy that governs the SPA. The strategies implemented in the subset setting are logically unified with each other. For example, if the dominating SPA shows international calls to a set of countries, and the non-dominating SPA restricts international calls to half of the same set of countries, then the non-dominating SPA policy is a subset of the dominating SPA policy. If the strategy is not logically decomposable, the strategy conflicts. For example, the SPA of the company server allows the UE to use unlimited minutes, while the SPA of the home-based server may set the limited number of minutes for the UE to use, which is used to associate two different accounts to two different Strategies, so these strategies are not logically decomposable. For the case where members who register the company server as the dominant server are not allowed to share any information through their UE, the non-dominant server allows sharing

CN 101448317 Β

The strategy will not be logically consistent with the strategy governing the server.

[0131] In one embodiment, by checking the modification flags controlled by each SPA with multiple servers, UEPA can evaluate the policies provided by the SPA of multiple servers. When establishing a connection with the UE, or when other strategies establish a process with the UEPA, each SPA can respond to a request from the UEPA and send its associated modification flag status. If the modification flag from an SPA is set to "No" or "F", the policy cannot be modified. UEPA must determine whether the policy associated with the SPA can be made from the UEPA owned and connected to the UE. The information of other SPAs is the same. For example, if the UE is logged to two servers, for a UE that designates one server as the dominant server, the modification flags of these two servers are both set to "F", then the nonconformity with the policy of the dominant server will be ignored. The strategy that governs the server. If all the policies of the non-dominating server conflict with the policies of the dominating server, UEPA can guide a process for the UE user, which allows the UE user to re-evaluate the user's selection of the server to which the UE is registered. If no policy is set to dominate, and the SPA policy received by UEPA conflicts with the existing SPA policy (logically not decomposable), the default action of UEPA may not allow the received policy and/or hang up and include and present. There are connections and/ Or a connection made by a UE registered with an inconsistent SPA policy. If for the UE, one server sets its modification flag to "T", and the other server's modification flag is set to "F", then since both SPAs allow UEPA to follow the unmodifiable policy, the two SPAs can still be satisfied. The logical requirements of the server.

[0132] In one embodiment, the wireless server may be configured to have multiple registered UE groups as separate groups from the wireless server. In addition, on the wireless server, the UE may not be registered as a member of any group, but may be registered as a member of one group or multiple groups. The SPA may send multiple policy sets to the UE based on the group registered by the UE with the server. As mentioned above, UEPA of UE can be decomposed into different strategies. Optionally, SPA can resolve conflicts between policies of different groups, and send a set of resolved policies to UEPA for each group registered by the UE.

[0133] In an embodiment, the UEPA of the UE may be configured to provide a logical interface for each server connected to the UE, so that the logical interface works as if only one server is connected. For such a configuration, the default state of UEPA is to keep each connection independent, so that there is no information sharing between the server and/or connection. However, UEPA can direct the display of a split screen on the UE, showing multiple independent connections on the screen. Using such a split screen, UE users can manage different connections. UEs registered with and/or connected to multiple servers and/or providers may have UEPA configured such that no sharing occurs between services. In one embodiment, no SPA strategy can surpass no sharing strategy. For example, one server may be a company server and the other server may be a personal server, such as a server located in a home, and the number of registrations of the personal server is the number of registrations of the company's server. Information shared with members of company servers is not allowed to be shared with members of personal servers. If the second member registered with the personal server also registers with the company server, the information associated with the company server shared between the two members who are both the company server and the personal server is sent through the logical interface associated with the company server provide. In one implementation In the example, the UEPA of the UE may have such a policy that a specific predefined group or a set of servers and/or providers can provide SPA policies used in operations between the specified groups, but these groups are not in the pre-defined group. No sharing occurs between any other servers and/or providers in the definition group. Each predefined group can be a group of servers.

[0134] Referring now to FIG. 11A, a first exemplary embodiment of a system and method is illustrated for routing email messages with external domains directly between mobile wireless clients. As shown in FIG. 11A, the first wireless server 1102 and a plurality of mobile wireless clients 1104-1 and 1104-2 can operate communicatively. In an example embodiment, the wireless server 1102 may include a database configured to store information associated with the user of the mobile wireless client, including the user identification of each mobile wireless client 1104-1 and 1104-2 E-mail proxy

CN 101448317 Β

1110, which includes one or more email agents managed by external email servers 1108-1 and 1108-2, used to collect emails from one or more external email domains and send them to one or more external emails Domain to send emails. According to one embodiment, these external email domains may include email domains such as Microsoft Hotma^ and Google Gma^®. In another embodiment, the external email domain may include corporate or other corporate mail systems, such as Microsoft Exchange ®, IBMs Domino @, and Novells GroupWise ®_o

[0135] According to one embodiment, each email corresponds to a user identification. The email proxy 1110 supports the email service of the mobile wireless client 1104 associated with the user identification. The email service includes coordinating the sending and receiving of emails from each email domain corresponding to the user identification. The email proxy 1110 is further configured to include a direct routing function 1112 to route email messages between one or more mobile wireless clients without first processing of email messages via external mail domains identified in the email message . Accordingly, according to an exemplary embodiment, the email message can be transmitted without first processing by the external email server.

[0136] Therefore, as shown in FIG. 11B, the method according to an example embodiment requires sending a 1122 email message from the first wireless client, where the email message comes from the first user or entity. The destination of the email is a second user or entity that also has an external email domain that is the same as or different from the external email domain of the first user or entity. The e-mail is received 1124 at the wireless server 1102, for example, the e-mail is received into the e-mail proxy 1110, for example, using the direct routing function 1112, the e-mail message is directly routed or sent 1126 to the second mobile wireless client 1104-2 , Without having to process the e-mail message first through one or more external e-mail domains identified as the sender or receiver of the e-mail message. Accordingly, since there is no need to be sent to and routed through external email servers (such as 1108-1 and 1108-2) first, the email message may be delivered to the recipient faster. In an alternative embodiment, the external email servers are also updated 1128 so that the email records in these servers show that directly routed emails have been sent or received. Accordingly, the external email server maintains synchronization with any email directly routed by the wireless server 1102. In one embodiment, for example, through the email proxy 1110, after the email is routed first, the external email server is directed to synchronize the email. In another embodiment, after or at the same time that the message is directly routed between mobile wireless clients, the external server may be instructed to synchronize the email.

[0137] According to an example embodiment, the email domain outside the wireless server 1102 may include an email domain based on the Post Office Protocol (POP), an email domain based on the Internet Message Access Protocol (IMAP), and an email based on POP and IMAP. Domains, or email domains based on other server architectures such as Microsoft Exchange, IBM's Domino® and Nov 11's GroupWise®.

[0138] According to yet another example embodiment, the direct routing of e-mails can be applied to other electronic communications such as instant messaging, where it is the instant messaging server that replaces the external e-mail server and domain, and the In contrast to the domain, direct routing is used to route instant messages directly between mobile wireless clients.

[0139] FIG. 12 shows an embodiment of a method for managing mobile wireless clients. The wireless server provides a simplified user interface for managing mobile wireless clients. In one embodiment, the wireless server displays one or more management scenarios for at least one mobile wireless client among the plurality of mobile wireless clients. The user of the wireless server selects the management scenario. In response to the selection of one or more management scenarios, the mobile wireless client automatically determines one or more management parameters for the mobile wireless client.

[0140] At 1210, the mobile wireless server may present one or more management scenarios for the mobile device to the user. Then, the wireless server receives a selection of at least one management scene from the user. At 1220, there is no need for

CN 101448317 Β

In addition, the wireless server identifies one or more management parameters to implement the selected management scenario. The management parameter can be operated to configure the mobile device for a specific management scenario.

[0141] The management scenario includes conditions or required changes to the wireless device, and the changes include changes to configuration data on the wireless device to implement such changes. For example, management scenarios include, but are not limited to: setting passwords, forgetting passwords, misplacement of mobile devices, losing mobile devices, and managing operation modes of wireless devices.

[0142] FIG. 13 shows an embodiment of a method for selectively managing mobile wireless clients. At 1310, the wireless server receives the required operation mode of the mobile wireless client. At 1320, the wireless server may use the required operating mode to determine one or more management parameters to configure the mobile wireless client for the required operating mode.

[0143] The operation mode of the wireless device may include, but is not limited to: turning off phone functions, controlling website access, restricting international phone calls, restricting phone calls to designated area codes, turning off short message service (SMS) messages, turning off multimedia messaging services ( MMS), turn off the use of the web browser, block the download of specific content (such as games), and log or monitor different types of use on the mobile device.

[0144] In one embodiment, the wireless server may transmit management parameters from the wireless server to the mobile wireless client, and use the management parameters to configure the mobile wireless client for the required operation mode. The management parameters can be determined without human intervention.

[0145] In one embodiment, the wireless server or mobile wireless client may display management scenarios or operation modes on a simplified user interface. The simplified user interface displays fewer management parameters than all the management parameters available for the configuration of the wireless server. As an alternative, the simplified user interface may display one or more management scenarios or operating modes instead of displaying management parameters. For example, if the management scenario used on the system for user authentication includes the need for a password, the management parameters used to implement the management scenario may include the following:

[0146] Parameters requiring password (true/false)

[0147] Maximum password validity period parameter (number of days)

[0148] Maximum password length parameter (number of characters)

[0149] Password Mode Check

[0150] Prohibited Password

[0151] Although in this example, five parameters are included to implement a management scenario requiring a password, the simplified user interface may not display any of these management parameters, or the user interface may display less than all these management parameters. parameter. As an alternative to displaying some or all of the management parameters, the user interface may display a high-level or abstract description of the management parameters used to implement the password policy. For example, the user interface can provide the user with the question "Do you need to change your password?" as an option. This question is an example of a management scenario.

[0152] FIG. 14 illustrates a system 1400 that can be employed in the architecture 100 and/or the architecture 200 (see FIG. 1 or FIG. 2). For example, a collaboration tool 1402 and an agent 1412 may be used in the wireless server 205 (see FIG. 2). The information content may be stored on the information content management subsystem 1408 of the collaboration tool 1402.

[0153] The information content management subsystem 1408 may receive and/or provide information related to information content from users through the web console user interface 1404 and/or from external applications through the external interface 1406. The external interface 1406 may use an API and/or a scrapping program of an external application to obtain this information.

[0154] The information content management subsystem 1408 can use the synchronization table 1410 and the agent 1412 to provide information content to the wireless mobile device 1414 and/or receive information content from the wireless mobile device 1414. The agent 1412 may enable communication between the wireless mobile device 1414 and the collaboration tool 1402. The wireless device 1414 may be a wireless device group 110 (see FIG.

CN 101448317 Β

1) Membership.

[0155] The synchronization table 1410 can synchronize the wireless mobile device 1414 with the wireless server 205. The synchronization table 1410 may be maintained on the wireless server 205.

[0156] FIG. 15 illustrates features of an embodiment of an information content management subsystem 1408 that may be employed in the system 1400 or other systems.

[0157] The information content management subsystem 1408 may include an information content access module 1502, an information content display module 1504, an information content providing module 1506, an entry module 1508, an identification module 1510, a recording module 1512, a response receiver module 1514, and a synchronization update module 1516, disassociation module 1518, distribution determination module 1520, synchronization access module 1522, transfer status determination module 1524, notification module 1526, content holder update module 1528, synchronization modification module 1530, deletion module 1532, and/or content data modification module 1534 . Other modules can also be used.

[0158] The information content access module 1502 accesses (eg receives) private information content associated with a single user and/or shared information associated with a single user and at least one other user. The information content can be received from one or more information sources 115 (see FIG. 1).

[0159] The information content display module 1504 displays private information content and shared information content for a single user on the same user interface. The same user interface may include (by way of example) the web console user interface 1404 and/or the user interface of the wireless mobile device 1414±.

[0160] The information content providing module 1506 transmits or delivers shared information content (for example, information content received from one or more information sources) and/or private information content to a mobile wireless device 1414 associated with the user. The provided information content can be resynchronized with the mobile wireless device 1414.

[0161] The entry module 1508 adds and/or deletes entries in the user configuration table of the user.

[0162] The identification module 1510 identifies private information content and/or shared information content associated with the user.

[0163] The recording module 1512 adds a synchronization record of shared information content and/or private information content to the synchronization table, and/or removes a synchronization record of shared information content and/or private information content from the synchronization table.

[0164] The response receiver module 1514 receives an update response from the mobile wireless device 1414.

[0165] The synchronization update module 1516 updates the synchronization table based on the received response, and/or updates the provided information content based on the private status.

[0166] The disassociation module 1518 disassociates the private content holder (for example, a folder or a content table) associated with the user.

[0167] The distribution determination module 1520 determines to distribute the information content to one or more mobile wireless devices 114 based on the private status of the information content.

[0168] The synchronization access module 1522 accesses one or more synchronization records associated with the information content based on the determination of distribution.

[0169] The delivery status determination module 1524 determines the delivery status of the information content associated with one or more synchronization records.

[0170] The notification module 1526 sends a notification about information content to the user, and/or receives a notification of deleting information content (for example, sharing information content).

[0171] The content holder update module 1528 updates the content holder (for example, a folder or a content table) of the content type to include information content. The content holder can track the private status of the information content.

[0172] The synchronization modification module 1530 modifies the synchronization table for one or more users to reflect the shared information content

CN 101448317 Β

delete.

[0173] The deletion module 1532 provides a deletion request for the shared information content to the user's mobile wireless device 1414, and/or receives a deletion response from the user's mobile wireless device 1414.

[0174] The content data modification module 1534 modifies the content data structure of the content type to remove information content. [0175] FIG. 16 illustrates an example wireless mobile device 1414 that may be employed in the system 1400 or other systems.

[0176] The wireless mobile device 1414 may include an information content receiver module 1602, a content data structure update module 1604, an information display module 1606, a response providing module 1608, a deletion request receiver module 1610, and/or an omission module 1612. Other modules can also be used.

[0177] The information content receiver module 1602 receives information content of one content type from the wireless server 205 (see FIG. 2).

[0178] The content data structure updates module 1604 of the content data structure of the content type to include and/or remove the information content.

[0179] The information display module 1606 displays the information associated with the information content on the user interface of the mobile wireless client 114.

[0180] The response providing module 1608 provides an update response to the wireless server 205 and/or provides a delete response to the wireless server 205.

[0181] The deletion request receiver module 1610 receives a deletion request for a shared information content of a content type from the wireless server 205.

[0182] The omission module 1612 omits the shared information content from the display associated with the content data result on the user interface.

[0183] FIG. 17 illustrates a user map 1700 according to an example embodiment. The user map 1700 may be adopted in the information content management subsystem 1408, or in the system 1400 or other systems.

[0184] The user map 1700 may maintain a mapping between the number of users and the content holders (eg, folders or content tables) associated with the users. The content holder may hold the information content received from the user or otherwise received.

[0185] The user may be associated with more than one content holder. For example, the user may be associated with one or more private content holders and/or one or more public content holders. The content holder can be identified by more than one user. For example, the content holder may be associated with multiple users of the shared content holder.

[0186] The user map 1700 may include a user identifier header 1702, a content holder identifier header 1704 and/or a license header 1706, and a plurality of mapping records 1708-1722. The mapping records 1708-1722 may include a header (Header) The corresponding field. Other headers and/or records can also be used.

[0187] The user identifier header 1702 relates to a user identifier to distinguish a user from other users, and a specific user is associated with the user identifier. In the mapping records 1708-1722, a specific user identifier may be included multiple times to reflect that the specific user identifier is associated with multiple content holders.

[0188] The content holder identifier header 1704 relates to the content holder identifier of the content holder to which a specific user is associated. In the mapping records 1708-1722, a specific content holder identifier may be included multiple times to reflect that the specific content holder identifier is associated with multiple users.

[0189] The license header 1706 relates to the license that the user has for the content holder. Available permissions may include, for example, read access, write access, modify access, and/or all access. The permission can enable the associated user to have a specific access permission to the information content held by the content holder.

CN 101448317 Β

[0190] FIG. 18 illustrates a content holder 1800 according to an example embodiment. The content holder 1800 can be used in the information content management subsystem 1408, or used in the system 1400 or other systems.

[0191] The content holder 1800 may be in the form of multiple folders 1802-1810, each folder holding one or more appointments 1812-1820 or other information content. The number of folders 1802-180 is shown only as an example, and a larger or smaller number of folders of the same and/or different content types may also be used. In an example embodiment, one of the folders 1802-1810 may only include information content of a single content type, while multiple folders are used to represent more than one content type.

[0192] The shared content folder 1802 may include two shared content subfolders 1804 and 1806. The two shared information content subfolders 1804 and 1806 can inherit some attributes of the shared information content folder 1802 on which they are based (for example, being associated with a user of a specific folder). The two shared content subfolders 1804.1806 may enable users to be associated with only a subset of appointments or other content in the parent shared content folder 1802. The private folder 1814 may be divided into one or more sub-folders 1810 for organization or other purposes.

[0193] FIG. 19 illustrates a content holder 1900 according to an example embodiment. The content holder can be used in the information content management subsystem 1408, or used in the system 1400 or other systems.

[0194] The content holder 1900 may be in the form of multiple content tables 1902, 1904, and each content table holds one or more conventions 1906.1-1906.n, 190&1-1908.n or other information content. The number of content tables 1902 and 1904 are shown as examples only, and a larger or smaller number of folders of the same and/or different content types may also be used. In an example embodiment, one of the content tables 1902 and 1904 may only include information content of a single content type, while multiple content tables are used to represent more than one content type.

[0195] FIG. 20 illustrates appointment data 2000 according to an example embodiment. The appointment data 2000 can be used in the information content management subsystem 1408, or used in the system 1400 or other systems. The appointment data 2000 can be used for calendar or other purposes.

[0196] The appointment data 2000 may include an entry identifier field 2002, a date field 2004, a subject field 2006, a start time field 2008, a duration field 2010, a time zone field 2012, a reminder time field 2014, an event name field 2016, and an event body field 2018 , Event location field 202, content holder identifier field 2022, owner identifier 2024, and/or shared field 2026. Other fields can also be used.

[0197] The entry identifier field 2002 stores a value (for example, an index value) for the appointment data 2000, and is used to distinguish the specific appointment data 2000 (for example, an appointment) from other information content in the content holder. For example, the content holder may include a plurality of appointment data 2000, each appointment data being identified by an entry identifier.

[0198] The date field 2004 stores the date when the appointment occurred. The subject field 2006 stores the agreed subject. The start time field 2008 stores the agreed start time. The duration field 2010 stores the agreed duration. The time zone field 2012 stores the agreed time zone. The reminder time field 2014 stores an optional time at which reminders are to be sent to one or more users associated with the appointment.

[0199] The event name field 2016 stores an agreed name. The event body field 2018 stores the agreed body. The event location field 202 stores the agreed event location. The content holder identifier field 2022 indicates the content holder associated with the information content.

[0200] The owner identifier 2024 identifies the agreed user identifier or creator. The shared field 2026 indicates whether the agreement is a shared agreement or a private agreement.

[0201] FIG. 21 illustrates memo data 2100 according to an example embodiment. Memo data 2100 can be in the letter

The information content management subsystem 1408 may be used in the system 1400 or other systems. The memo data 2100 can be used for memo collection or other purposes.

[0202] The memo data 2100 may include an entry identifier field 2102, an entry date field 2104, a subject field 2106, a memo name field 2108, a memo body field 2120, a content holder identifier field 2112, an owner identifier field 2114, a shared field 2116 and/or completion field 2118. Other fields can also be used.

[0203] The entry identifier field 2102 stores a value (for example, an index value) for the information content, and is used to distinguish specific memo data 2100 (for example, a memo) from other information contents in the content holder.

[0204] The entry date field 2104 stores the date value when the memo was created. The subject field 2106 stores the subject of the memo. The memo name field 2108 stores the name of the memo. The memo body field 2120 stores the body of the memo.

[0205] The content holder identifier field 2112 indicates the content holder associated with the memo data 2100. The owner identifier field 2114 identifies the user identifier or creator of the memo. The shared field 2116 indicates whether the memo is a shared memo or a private memo. The completion field 2118 indicates whether the task or other information described in the memo has been completed.

[0206] FIG. 22 illustrates address book data 2200 according to an example embodiment. The address book data 2200 can be used in the information content management subsystem 1408, or used in the system 1400 or other systems. The address book data 2200 can be used for an address book or other purposes.

[0207] The address book data 2200 may include an entry identifier field 2202, a last modified date 2204 field, a full name field 2206, a postal address field 2208, an email address field 2210, a telephone number field 2212, a fax number field 2214, and a comment field 2216 , Content holder identifier field 2218, owner identifier field 2220, and/or shared field 2222.

[0208] The entry identifier field 2202 stores a value (for example, an index value) for the address book data 2200, and is used to distinguish the specific address book data 2200 (for example, an address book entry) from other information content in the content holder.

[0209] The last modified date 2204 field stores the date value of the last modification of the address book entry. The full name field 2206 stores the full name of the user of the address book entry. The postal address field 2208 stores the postal address of the address book entry. The email address field 2210 stores the email address of the address book entry. The phone number field 2212 stores the phone number of the address book entry. The fax number field 2214 stores the fax number of the address book entry. The comment field 2216 stores a comment for the address book entry.

[0210] The content holder identifier field 2218 identifies the content holder associated with the address book entry. The owner identifier field 2220 identifies the user identifier and/or creator of the address book entry. The shared field 2222 indicates whether the address book entry is a shared address book entry or a private address book entry.

[0211] FIG. 23 illustrates an example repetition table 2300 according to an example embodiment. The example repetition table 2300 may be adopted in the information content management subsystem 1408, or in the system 1400 or other systems. The example repetition table 2300 may be associated with the information content (for example, an appointment) to indicate multiple occurrences of the information content (for example, the information content in the holder).

[0212] The repeating table 2300 may include multiple headers 2304-2318 associated with the fields 2320-2334 for each entry in the repeating table 2300. Although the example repeating table 2300 is shown as including fields with fields 2320-2334 A single repetition, however, a larger number of repetitions can be included in the example repetition table 2300.

[0213] The fields 2320-2334 include a repeat identifier field 2320, a repeat interval field 2322, a repeat frequency field 2324, a repeat end field 2326, a repeat month field 2328, a repeat week start field 2330, a repeat day of the week field 2332, and/or Repeat the day of the month field 2334. Other fields can also be used.

CN 101448317 Β

[0214] The repetition identifier field 2320 receives a value (for example, an index value) for repetition, which is used to distinguish a specific repetition from other repetitions in the repetition table 2300.

[0215] The repetition interval field 2322 receives a value indicating the interval between occurrences (eg, scheduled occurrences). The repetition frequency field 2324 receives a value indicating the frequency of occurrence. The repeated termination field 2326 receives a value indicating the date on which the termination occurred.

[0216] The repeated month field 2328 receives a value indicating the month of the year in which it occurred. The repeated week start field 2330 receives a value indicating the week of the year in which the occurrence starts. The repeated day of the week field 2332 receives a value indicating the day of the week that occurs. The day of the repeating month field 2334 receives a value indicating the month of the year in which it occurs.

[0217] FIG. 24 does not notice an exemplary synchronization table 1410 according to an exemplary embodiment. The synchronization table 1410 may be adopted in the system 1400 or other systems.

[0218] The synchronization table 1410 may include a plurality of headers 2402-2418 associated with the fields 2420-2336 for each entry in the synchronization table 1410. The fields 2420-2336 may include a table identifier field 2420, a synchronization identifier field 2422, user identifier field 2424, reference identifier 2426, delivery status field 2428, content type field 2430, revision field 2432, sequence field 2434, and/or status field 2436. Other headers and/or fields can also be used.

[0219] The table identifier field 2420 receives a value (for example, an index value) for distinguishing a specific synchronization record from other synchronization records in the synchronization table 1410.

[0220] The synchronization identifier field 2422 receives a value indicating an entry identifier for information content of one content type. The user identifier field 2424 receives a value indicating the user who is the user associated with the synchronization record in the user map 1700. The reference identifier 2426 receives the reference value.

[0221] The delivery status field 2428 receives a value indicating the delivery status of the information content delivered to the mobile wireless device 1414. For example, the value may be "4", the substantially associated information content is new and will be delivered to the wireless mobile device 1414, and "8" indicates that the associated information content is updated and will be delivered to the wireless mobile device 1414. The mobile device 1414, or "16" indicates that the associated information content is to be deleted from the mobile wireless device 1414.

[0222] The content type field 2430 receives a value indicating the content type of the information content. The revision field 2432 receives values that can be used to resolve conflicts and/or concurrent updates on the mobile wireless device 1414. The sequence field 2434 receives values that can be used to resolve conflicts and/or concurrent updates on the mobile wireless device 1414. The status field 2436 receives a value indicating the processing status of the content management subsystem 1402.

[0223] FIG. 25 illustrates a content holder table 2500 according to an example embodiment. The content holder table 2500 can be used in the information content management subsystem 1408, or used in the system 1400 or other systems. The content holder table 25000 may be associated with a content holder (such as a folder or a content table) to identify the name and content type of the associated content holder.

[0224] The content holder table 2500 may include a plurality of table headers 2502-2506, and a plurality of records 2508-2516 with fields corresponding to the table header 2502-25-6. The table header 2502-2506 may include a content holder The identifier header 2502, the content holder name field 2504, and/or the content content type field 2506. Other headers and/or fields can also be used.

[0225] The field associated with the content holder identifier header 2502 receives a value (for example, an index value) for distinguishing a specific content holder from other content holders. The field associated with the content holder name header 2504 receives the name of the content holder. The field associated with the content type header 2506 receives a value indicating the content type of the content holder.

[0226] FIG. 26 illustrates a user configuration table 2600 according to an example embodiment. The content holder table 2600 can be

CN 101448317 Β

Adopted in 1412, or in system 1400 or other systems. The user configuration table 2600 may be associated with a user having a specific mobile wireless device 1414.

[0227] The user configuration table 2600 may include a plurality of headers 2602, 2604 and a plurality of entries 2606-2620 with fields corresponding to the headers 2602, 2604. The headers 2602, 2604 may include a user identifier header 2602 and / Or the device identifier header 2604. Other fields and/or headers can also be used.

[0228] The field associated with the user identifier header 2602 receives a value (for example, an index value) for distinguishing a specific user from other users. The field associated with the device identifier header 2604 indicates the value (eg, unique value) of the wireless mobile device 1414 associated with this particular user.

[0229] FIG. 27 illustrates a method 2700 for presenting information content according to an example embodiment. The method 2700 may be executed by the wireless mobile device 1414, executed by the content management subsystem 1408, or executed by other devices.

[0230] At block 2702, the method associates private information content with a single user. Except for the single user, the private information content is not available to other users. At block 2704, the shared information content associated with the single user and at least one other user is accessed. By way of example, the shared and/or private information content may include: calendar data, address book, message board, task monitor, photo data, music data, video data, text data, or a combination thereof. Other types of shared information content can also be used.

[0231] At block 2706, on the same user interface, private information content and shared information content are displayed for the single user. For example, the same user interface can be used on the mobile wireless device 1414±ο

[0232] FIG. 28 illustrates a method 2800 for synchronizing information content according to an example embodiment. The method 2800 may be executed by the agent 1412, executed by the content management subsystem 1408, or executed by other devices.

[0233] At block 2802, the user's shared information content is received from one or more information sources 115. By way of example, the information source 115 may include a web console interface 1404, a user interface of the mobile wireless device 1414, and/or an external interface 1406. Other information sources 115 may also be used.

[0234] The shared information content may include: calendar data, address book, message board, task monitor, photo data, music data, video data, text data, or a combination thereof. The shared information content may include new information content or modified information. information.

[0235] At block 2804, the shared information content received from one or more information sources 115 is transmitted to a mobile wireless device 1414 associated with the user. The shared information content can be transmitted to a second mobile wireless device associated with the second user 1414

[0236] FIG. 29 illustrates a method 2900 for adding users to the wireless server 205 according to an example embodiment. The method 2900 may be executed by the information content management subsystem 1408, or executed by other devices.

[0237] At block 2902, an entry is added to the user configuration table 2600 of the user.

[0238] At block 2904, the private information content associated with the user is identified.

[0239] At block 2906, a synchronization record for the private information content is added to the synchronization table 1410 of the user.

[0240] At block 2908, the private information content may be delivered to the mobile wireless device 1414 of the user.

[0241] At block 2910, the shared information content associated with the user is identified.

[0242] At block 2912, a synchronization record for the shared information content is added to the synchronization table 1410 of the user.

[0243] At block 2914, the shared information content may be delivered to the user's mobile wireless device 1414.

[0244] At block 2916, an update response may be received from the mobile wireless device 1414.

[0245] At block 2918, based on the received update response, the synchronization table 1410 of the user may be updated.

CN 101448317 Β

[0246] In an example embodiment, the operations performed in blocks 2910, 2912, 2914 may precede the operations performed in blocks 2904, 2906, 2908.

[0247] FIG. 30 illustrates a method 3000 for deleting a user from the wireless server 205 according to an example embodiment. The method 3000 may be executed by the information content management subsystem 1408, or executed by other devices.

[0248] At block 3002, one or more synchronization records are removed from the synchronization table 1410 of the user.

[0249] At block 3004, the entry in the user configuration table 2600 for the user is removed. The user configuration table 2600 may include one or more entries. Each of the one or more entries may define an association between another user and the mobile wireless device 1414.

[0250] In block 3006, the private content holder associated with the user is disassociated. The private content holder may include private folders or private tables. Other private content holders can also be used.

[0251] FIG. 31 illustrates a method 3100 for distribution of information content according to an example embodiment. The method 3100 may be executed by the content management subsystem 1408, executed by the agent 1412, or executed by other devices.

[0252] At block 3102, the information content is accessed. The information content can have a private status.

[0253] In an exemplary embodiment, during the operation of block 3102, a modification request for the information content may be received through a user interface (for example, a web console user interface 1404), and the information content may be modified according to the modification request; One or more synchronization records associated with the information content can be modified.

[0254] At block 3104, based on the private status, it is determined to distribute the information content to one or more mobile wireless devices 1414.

[0255] At block 3106, based on the determination of the distribution, one or more synchronization records associated with the information content are accessed.

[0256] At block 3106, the delivery status of the information content associated with the one or more synchronization records is determined.

[0257] At block 3108, based on the determination of the transfer status, the information content is transferred to one or more mobile wireless devices 1414.

[0258] FIG. 32 illustrates a method 3200 for processing information content according to an example embodiment. The method 3200 may be executed by the information content management subsystem 1408, executed by the agent 1412, or executed by other devices.

[0259] At block 3202, information content of a content type is received. The information content can have a private status. This information content can be received by the mobile wireless device 1414, by a user interface on a different computing system, or by other devices.

[0260] At block 3204, based on the privacy status of the information content, update the synchronization table 1410 of one or more users identifying the mobile wireless client 210 (see FIG. 2) to be provided with the information content. By way of example, The updating may include adding an entry to the synchronization table 1410 of the user who will be provided with the information content and/or modifying an entry in the synchronization table 1410 of the user who will be provided with the information content.

[0261] In an example embodiment, when the information content originates from the user's wireless mobile device 1414, the user of the mobile device 1414 may not receive the information content. Excluding the retransmission of the information content to the source wireless mobile device 1414 can reduce the bandwidth and/or prevent the source wireless mobile device 1414 from performing unnecessary data processing.

[0262] At decision block 3206, a determination can be made whether to deliver the information content. If the determination is made to deliver the information content, then at block 3208, the information content is delivered to the mobile wireless device 1414 of one or more users. The provided information can be synchronized with the mobile wireless device 1414. If the determination made at decision block 3206 is not to transmit the information content, then the method 3200 may continue to decision block 3210.

[0263] At decision block 3210, a determination can be made whether to send a notification. If the decision is to send a notification, you can

CN 101448317 Β

To send a notification about the content of the information to one or more users. If the determination made at decision block 3210 is not to send a notification, then the method 3200 may continue to decision block 3214.

[0264] At decision block 3214, a determination may be made whether to update the content holder (eg, a folder or a table of contents). If the determination is made to update the content table, the content holder of the content type can be updated to include the information content. The content holder can track the private status of the information content. If the determination made at decision block 3214 is not to update the content holder, or the operation is completed at block 3216, the method 3200 terminates.

[0265] In an example embodiment, updating the content table may include adding information content to the content table (eg, content tables 1902, 1904), or modifying existing information content of the content table. For example, modifying the existing information content may include determining whether the user associated with the received information content is the owner of the existing information content, and modifying the existing information content based on the determination.

[0266] In an example embodiment, the operations in decision blocks 3206, 3210, 3214 may occur in any order and/or simultaneously.

[0267] FIG. 33 illustrates a method 3300 for processing information content according to an example embodiment. The method 3300 may be performed by the wireless device 1414 or performed by other devices.

[0268] At block 3302, information content of a content type is received from the wireless server 205. By way of example, the information content may include calendar items, memo items, contact items, task items, message board items, and/or address book items. Other information content can also be used.

[0269] At block 3204, the content data structure of the content type is updated to include the information content. The content data structure can have the private status of the information content. The content data structure can be a folder, a content table, or a different structure.

[0270] At block 3306, an update response may be provided to the wireless server 205.

[0271] At block 3308, information related to the information content is displayed on the user interface of the mobile wireless device 1414.

[0272] FIG. 34 illustrates a method 3400 for deleting shared information content according to an example embodiment. The method 3100 may be executed by the information content management subsystem 1408, or executed by other devices.

[0273] At block 3402, a notification to delete shared information content of a content type is received. The shared information content can be associated with multiple users.

[0274] At block 3404, the synchronization table 1410 of these users is modified to reflect the deletion of the shared information content.

[0275] In an exemplary embodiment, the transmission status of the synchronization record of the synchronization table 1410 of the user is modified to reflect the deletion of the shared information content.

[0276] At block 3406, the mobile wireless device 1414 of one or more users is provided with a delete request for the shared information content.

[0277] At block 3408, the response may be deleted from the user's mobile wireless device 1414.

[0278] At block 3410, the content data structure of the content type may be modified to remove the information content.

[0279] FIG. 35 illustrates a method 3500 for deleting shared information content according to an example embodiment. The method 3500 may be executed by the information content management subsystem 1408, or executed by other devices.

[0280] At block 3502, a delete request for shared information content of a content type is received from the wireless server 205.

[0281] At block 3504, the content data structure of the content type is updated to remove the information content.

[0282] At block 3506, a delete response may be provided to the wireless server 205.

[0283] At block 3508, the shared information content may be omitted from the information associated with the content data structure on the user interface.

CN 101448317 Β

[0284] The various embodiments or combinations of embodiments of the apparatus and method for a wireless server described herein may be implemented in a hardware implementation manner, a software implementation manner, and a hardware and software combination implementation manner. These implementations may include a machine-readable medium with machine-executable instructions, such as a computer-readable medium with computer-readable instructions, for operating a wireless server in a group relationship with one or more mobile wireless clients, such that based on The private state associated with the information distributes the information in the group. The communication and information sharing between the wireless server and the group can be performed on the basis of security. The machine-readable medium is not limited to any kind of medium.

[0285] The various embodiments or combinations of embodiments of the apparatus and method for a mobile wireless device described herein can be implemented in a hardware implementation manner, a software implementation manner, and a hardware and software combination implementation manner. These implementations may include a machine-readable medium having machine-executable instructions, such as a computer-readable medium having computer-readable instructions, for operating the mobile wireless device as a client of multiple wireless servers in a multi-mode setting. The mobile wireless device may be configured to be in a group relationship with the wireless server, so that the mobile wireless device interacts with the wireless server to receive and send the information based on the private state associated with the information. The communication between the mobile wireless device and each wireless server in the associated group can be performed on the basis of security. The machine-readable medium is not limited to any kind of medium.

[0286] According to an embodiment of a further invention, there is provided:

[0287] 1& One method, including:

[0288] establishing communication from a mobile wireless device to a wireless server, where the mobile wireless device is a registered wireless client of the wireless server;

[0289] determining whether a strategy for a wireless mobile device associated with another wireless server is primary relative to controlling the flow of information from the mobile wireless device;

[0290] Start the browser in the mobile wireless device for controlling the browsing of the file directory in the wireless server; and

[0291] A signal is generated to the wireless server to select files in the file directory.

[0292] 19. The method according to 18, wherein establishing communication from the mobile wireless device to the wireless server includes establishing communication from the mobile wireless device to the wireless server, so that substantially all of the communication between the mobile wireless device and the wireless server The communication is automatically performed on the secure communication channel between the mobile wireless device and the wireless server.

[0293] 20. The method according to 18, wherein the method includes generating a signal to the wireless server to download the selected content to the mobile wireless device to store the selected content on the mobile wireless device file.

[0294] 21. The method according to 18, wherein the method includes generating a signal to the wireless server to send the selected file as an email attachment.

[0295] 22. The method of 18, wherein the method includes generating a signal to the wireless server to use an accessory server of the wireless server to view the selected file.

[0296] 23. The method according to 18, wherein controlling the browsing of the file directory in the wireless server includes browsing files with format indicators selected from the following: doc, xls, pdf, ppt, jpg, png , Bmp, gif, mp3 and wav.

[0297] 24. A method, including:

[0298] Establish communication with a mobile wireless device in the wireless server, and the mobile wireless device is a registered wireless client of the wireless server;

[0299] Receive a signal from the wireless server, the signal is a browser signal, used to browse the directory of the wireless server;

[0300] In response to a browse command including a selection command from the wireless mobile wireless device, browse files in the directory; and

CN 101448317 Β

[0301] The content of the file selected from the directory is provided.

[0302] 25. The method according to 24, wherein establishing communication with the mobile wireless device in the wireless server includes establishing communication with the mobile wireless device in the wireless server, so that the mobile wireless device and the wireless server basically communicate with each other. All communications above are automatically performed on the secure communication channel between the mobile wireless device and the wireless server.

[0303] 26. The method of 24, wherein the method includes determining a strategy for controlling the flow of information to the mobile wireless device that can register with one or more other wireless servers.

[0304] 27. The method of 24, wherein providing the content of the file selected from the directory includes downloading the selected file to the mobile wireless device to store the selected file on the mobile wireless device.

[0305] 2& The method according to 24, wherein providing the content of the file selected from the directory includes sending the selected file as an email attachment.

[0306] 29. The method of 24, wherein providing the content of the file selected from the directory includes using an accessory server of the wireless server to view the selected file.

[0307] 30. The method according to 24, wherein browsing files in the file directory includes browsing files with format indicators selected from the following: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3 and way.

[0308] 45. A machine-readable medium storing instructions, when the instructions are executed on a machine, the machine is prompted to perform operations, the operations including:

[0309] establishing communication from a mobile wireless device to a wireless server, where the mobile wireless device is a registered wireless client of the wireless server;

[0310] determining whether a strategy for a wireless mobile device associated with another wireless server is primary relative to controlling the flow of information from the mobile wireless device;

[0311] Starting the browser in the mobile wireless device for controlling the browsing of the file directory in the wireless server; and

[0312] Generate a signal to the wireless server to select files in the file directory.

[0313] 46. The machine-readable medium of 45, wherein establishing communication from the mobile wireless device to the wireless server includes establishing communication from the mobile wireless device to the wireless server, such that the mobile wireless device and the wireless server are Basically all communication is carried out on the secure communication channel between the mobile wireless device and the wireless server.

[0314] 47. The machine-readable medium of 45, wherein the instructions include generating a signal to the wireless server to download the selected content to the mobile wireless device for storage on the mobile wireless device The selected file.

[0315] 4& The machine-readable medium according to 45, wherein the instructions include generating a signal to the wireless server to send the selected file as an email attachment.

[0316] 49. The machine-readable medium of 45, wherein the instructions include generating a signal to the wireless server to use an accessory server of the wireless server to view the selected file.

[0317] 50. The machine-readable medium according to 45, wherein controlling the browsing of the file directory in the wireless server includes browsing files with format indicators selected from the following: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3 and wav ο

[0318] 51. A machine-readable medium storing instructions, when the instructions are executed on a machine, prompt the machine to perform operations, the operations including:

[0319] Establish communication with a mobile wireless device in the wireless server, and the mobile wireless device is a registered wireless client of the wireless server;

CN 101448317 Β

[0320] Receive a signal from the wireless server, the signal is a browser signal, used to browse the directory of the wireless server;

[0321] In response to a browse command including a selection command from the wireless mobile wireless device, browse the files in the directory; and

[0322] Provide the content of the file selected from the directory.

[0323] 52. The machine-readable medium of 51, wherein establishing communication with the mobile wireless device in the wireless server includes establishing communication with the mobile wireless device in the wireless server, so that the mobile wireless device and the wireless server Basically all communication between the mobile wireless device and the wireless server is carried out on the secure communication channel.

[0324] 53. The machine-readable medium of 51, wherein the instructions include determining a strategy for controlling the flow of information to the mobile wireless device that can register with one or more other wireless servers .

[0325] 54. The machine-readable medium of 51, wherein providing the content of the file selected from the directory includes downloading the selected file to the mobile wireless device to store the selected file on the mobile wireless device file.

[0326] 55. The machine-readable medium of 51, wherein providing the content of the file selected from the directory includes sending the selected file as an email attachment.

[0327] 56. The machine-readable medium of 51, wherein providing the content of the file selected from the directory includes using an accessory server of the wireless server to view the selected file.

[0328] 57. The machine-readable medium according to 51, wherein browsing files in the file directory includes browsing files with format indicators selected from the following: doc, xls, pdf, ppt, jpg, png, bmp , Gif, mp3 and wav.

[0329] 5&-a mobile wireless device, including:

[0330] Controller;

[0331] An identifier, which is unique and provides the ability to establish a registered client relationship with the wireless server;

[0332] The policy agent is used to determine whether a policy for a wireless mobile device associated with another wireless server is the primary one relative to controlling the flow of information from the mobile wireless device;

[0333] In response to the machine-readable medium of the controller, the machine-readable medium stores and retrieves data, the data including instructions for guiding browsing activities of files in the wireless server.

[0334] 59. The mobile wireless device according to 58, wherein the mobile wireless device includes a communication control for establishing communication with a wireless server so that substantially all of the communication between the mobile wireless device and the wireless server The communication is performed on a secure communication channel between the mobile wireless device and the wireless server.

[0335] 60. The mobile wireless device according to 58, wherein the instructions include instructions for uploading information content in the mobile wireless device to a wireless server.

[0336] 61. The mobile wireless device according to 60, wherein the instructions include instructions for uploading information content in the mobile wireless device to a wireless server, and the uploading is based on the It is done automatically by loading information content in the synchronization folder uploaded by the server.

[0337] 62. The mobile wireless device according to 61, wherein the synchronization folder designated to be automatically uploaded to the wireless server includes a synchronization folder specifically associated with a wireless server among the plurality of wireless servers.

[0338] 63. The mobile wireless device of 58, wherein the mobile wireless device includes a display that is operated to display a presentation of the availability of new information content on the wireless server.

[0339] 64. The mobile wireless device of 58, wherein the mobile wireless device includes a display that is operated to display the presentation of the information content that is automatically downloaded from the wireless server.

CN 101448317 Β

[0340] 65. The mobile wireless device according to 58, wherein the file includes a file having a format indicator selected from the following: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3, and wav.

[0341] 66. A wireless server, comprising:

[0342] Controller;

[0343] A data storage area, running together with the controller, the data storage area including one or more identifiers for uniquely establishing a registration relationship with one or more mobile wireless clients, the one or more mobile The wireless clients correspond to their respective identifiers, and the one or more mobile wireless clients are identified as belonging to a group;

[0344] In response to a machine-readable medium of the controller, the machine-readable medium stores and retrieves data including instructions for browsing files in the wireless server based on commands from mobile wireless clients belonging to the group; And a [0345] interface, through which information is transmitted to the mobile wireless client.

[0346] 67. The wireless server according to 66, wherein the wireless server includes a communication control for establishing communication with a mobile wireless client, so that substantially all communication between the wireless server and the mobile wireless client is On the secure communication channel between the wireless server and the mobile wireless client.

[0347] 6& The wireless server according to 66, wherein the wireless server includes a policy service for determining a policy for controlling the flow of information to a mobile wireless device, which can transmit information to one or more other wireless devices. Server registration.

[0348] 69. The wireless server according to 66, wherein the instructions include one or more instructions for downloading information content to mobile wireless.

[0349] 70. The wireless server according to 66, wherein the server includes folders corresponding to one or more corresponding mobile wireless clients based on private or shared designation.

[0350] 71. The wireless server according to 70, wherein the designation to be shared includes designating to identify two or more mobile wireless clients, each having an identifier, and the number of the two or more mobile wireless clients Less than all one or more corresponding mobile wireless clients whose identifiers are stored in the wireless server.

[0351] 72. The wireless server according to 66, wherein the instructions include one or more instructions for automatically downloading data to the mobile wireless client, and the downloading is based on a folder accessible on the wireless server The storage of information content in the folder, the folder is associated with the wireless client.

[0352] 73. The wireless server according to 72, wherein the data includes information content.

[0353] 74. The wireless server according to 72, wherein the data includes a presentation of the availability of information content accessible by the wireless server.

[0354] 75. The wireless server shown in 66, wherein the file includes a file having a format indicator selected from the following: doc, xls, pdf, ppt, jpg, png, bmp, gif, mp3, and wav .

[0355] 76. A wireless server, comprising:

[0356] Controller;

[0357] A data storage area, running together with the controller, the data storage area including one or more identifiers for uniquely establishing a registration relationship with one or more mobile wireless clients, the one or more mobile The wireless clients correspond to their respective identifiers, and the one or more mobile wireless clients are identified as belonging to a group;

[0358] In response to the machine-readable medium of the controller, the machine-readable medium stores and retrieves data, the data including instructions for automatically downloading the data to the mobile wireless client, the downloading is based on the accessibility of the wireless server Storage of the information content in the folder of which is associated with the wireless client; and

CN 101448317 Β

[0359] An interface, through which information is transmitted to the mobile wireless client.

[0360] 77. The wireless server according to 76, wherein the wireless server includes a communication control for establishing communication with a mobile wireless client, so that substantially all communication between the wireless server and the mobile wireless client is in the wireless On the secure communication channel between the server and the mobile wireless client.

[0361] 7& The wireless server according to 76, wherein the wireless server includes a policy service for determining a policy for controlling the flow of information to a mobile wireless device, which can transmit information to one or more other wireless devices. Server registration.

[0362] 79. The wireless server according to 76, wherein, corresponding to the mobile wireless clients belonging to the group, a folder is configured and designated as private or shared.

[0363] 80. The wireless server of 79, wherein the designation as shared can be attributed to less than all mobile wireless clients whose identifiers are stored in the wireless server.

[0364] 81. The wireless server according to 76, wherein the data includes information content.

[0365] 82. The wireless server according to 76, wherein the data includes a presentation or representation of the availability of information content accessible by the wireless server

[0366] Although specific embodiments are illustrated and described herein, those skilled in the art should understand that any arrangement suitable for achieving the same purpose can be substituted for the specific embodiments shown. It should be understood that the above description is intended for illustration rather than limitation, and the wording or terminology used here is for the purpose of description rather than limitation. By studying the above description, the combination of the above-mentioned embodiments and other embodiments will be obvious to those skilled in the art.

CN 101448317 Β