WO2007036143A1 - Procede et systeme pour emettre des informations de presence - Google Patents

Procede et systeme pour emettre des informations de presence Download PDF

Info

Publication number
WO2007036143A1
WO2007036143A1 PCT/CN2006/002519 CN2006002519W WO2007036143A1 WO 2007036143 A1 WO2007036143 A1 WO 2007036143A1 CN 2006002519 W CN2006002519 W CN 2006002519W WO 2007036143 A1 WO2007036143 A1 WO 2007036143A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
information
presentation
delegation
server
Prior art date
Application number
PCT/CN2006/002519
Other languages
English (en)
French (fr)
Inventor
Linyi Tian
Yang Zhao
Qian Sun
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to CN200680012244.5A priority Critical patent/CN101160846A/zh
Priority to EP06791108A priority patent/EP1873976B1/en
Publication of WO2007036143A1 publication Critical patent/WO2007036143A1/zh
Priority to US11/936,918 priority patent/US8201241B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227Filtering policies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102Entity profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/54Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Definitions

  • the present invention relates to a method and system for publishing presence information, and more particularly to a method and system for publishing presence information with a delegation mechanism.
  • Presence Service is a communication service that collects and publishes presence information. It may be that many people want to get presence information for presenting business users, who may include the user's family, friends, or strangers, and many of the presentation information is user privacy.
  • the presentation service enables users to utilize various terminals, break through space and time constraints, find chat partners, query partner status information, etc., and realize instant text and multimedia information exchange. Through the presence server, the presentation and management of the user state is completed.
  • the presentation information it is possible to know whether the other party is online, what is being done (such as meeting, eating, etc.), mood, client capabilities, hobbies, etc., and the user can send Invite to other users to share media content such as ring tones, pictures, files, etc.
  • FIG. 1 depicts a system architecture for implementing a presence service in the prior art, including a presence client or application server (Application Server) 103, a presence server (Presence Server) 102, a watcher client (Watcher) 101, and a presentation XDMS (Presence).
  • the presentation client or application server (Application Server) 103 is a presentation information source, and when the presentation information changes, actively sends a PUBLISH release message to the presentation server 102, and publishes the presentation. information.
  • the presentity client and the viewer client 101 may be mobile terminals, such as a mobile phone, a PDA (PDA), an intelligent terminal (such as a digital set top box), or the like, or may be a fixed terminal.
  • the above functions on the mobile terminal may also be applied to the fixed terminal.
  • the terminal there is also a session initialization protocol.
  • SIP Session Initiation Protocol
  • the presence client or the application server 103 has an application for publishing a message, and the user can select the published information to be published, and then confirm the presentation client or application.
  • the server 103 sends all the messages including the user identifier and the like to the presence server 102. .
  • the presence server 102 is responsible for receiving the SUBSCRIBE subscription message of the Observing Client 101. Determining the result of the subscription according to the subscription authorization rule preset by the subscribed presentity client; receiving the PUBLISH release message of the presentity client, according to some rules originally set by the presentity client or the application server 103/observing client 101 ( Including content composition, authorization, and filtering, processing is performed, and the presence information is finally released to the viewer client 101 through the NOTIFY notification.
  • the observing client 101 subscribes to the presence information of the presence client or application server 103 and receives the notification message from the presence server 102.
  • the presentation XDMS 104 saves the authorization list of the presentity client or application server 103 (such as a subscription authorization list, a content authorization list, a delegation authorization list, etc.), a group list, etc., and other devices such as presentation information synthesis and distribution devices may pass protocols such as ML.
  • Document Configuration and Access Protocol (XCAP) direct access to the rendering XDMS 104, or a series of information, such as subscription authorization rules, content authorization rules, delegated authorization lists, etc., can be obtained from the authorization list in the presentation DMS 104 through a dedicated information access unit; If desired, those skilled in the art can set the presentation XDMS 104 directly to the presence server 102, or both can be set up as separate service units for access through a particular communication protocol.
  • the aforementioned SUBSCRIBE and PUBLISH are all SIP messages.
  • the SIP header of the PUBLISH message contains the identifier of the presentity client, and the message body contains the XML document, which is the presentation information of the presentity client.
  • the subscription and release messages are not limited to the SIP message format, and are SIP messages in the IP Multimedia Subsystem (IMS) network. For other networks (such as ICQMSN applications in IP networks), they may not be SIP messages.
  • IMS IP Multimedia Subsystem
  • the presentation server 102 includes a presence information synthesizing and distributing device 105, and the presence information synthesizing and distributing device 105 is the most important device. FIG.
  • the presentation information synthesizing unit 211 is configured to synthesize the newly released presentation information and the presentation information saved in the server;
  • the content authorization rule checking unit 212 Used to filter out the information that is not allowed to be published according to the rules set by the presentity client (which information is allowed to be published for a certain observing client);
  • the observing body filtering unit 213 is used to follow the rules set by the observing body (if not wishing) Receiving information about a certain client client), filtering out information that is not desired to be received (for example, the observer only wants the user to change from shutdown to power-on notification, and other presentation information will be filtered out);
  • the partial notification processing unit 214 observes Client client 101
  • the SUBSCRIBE is configured to subscribe to the rules (for example, only the presence information related to the location
  • FIG. 3 shows the flow chart of the existing system interaction. The specific process is as follows:
  • the presentity client A first has to make some settings in the rendering XDMS (such as subscription authorization rules (which users are allowed to subscribe), content authorization rules (which information is allowed to be published), etc., the rendering server can obtain these rules through the XCAP protocol, or If the presence server subscribes to the change notifications for these rules, the presentation DMS notifies the presence server when these rules change.
  • the Subscription Authorization Rule and the Content Authorization Rule are guaranteed to be presented in an XML file.
  • XML includes three important elements ⁇ Condition>, ⁇ Action>, ⁇ Transformation>.
  • ⁇ Condition> indicates the condition of the match
  • ⁇ Acti 0 n> indicates the result of the match, (allow, deny, friendly rejection, wait for confirmation)
  • the combination of ⁇ Condition> and ⁇ eight ( ⁇ 011> corresponds to the subscription authorization rule for processing the subscription request of the observer client according to the rules set by the presentity client;
  • ⁇ Tran S formati 0n > corresponding content authorization rule, for Rules for presenting client settings (for a watch client) What information Xu release), will not allow the release of information to filter out;
  • the presence server matches according to the subscription authorization rule in the presentation XDMS, and if it matches, allows the subscription; and saves the subscription relationship at the same time;
  • the presentity client A issues (PUBLISH) information to the presence server;
  • the presence server sends a notification of the presence information to the observer B according to a series of rules (NOTIFY) o
  • the XDMS is separated from the rendering server, various rules are saved on the rendering XDMS, the rendering client uses the XCAP protocol through the Aggregation Proxy, or the application server directly uses the XCAP protocol, or the user passes the human-computer interaction interface (such as web pages) to present XDMS settings and modify various rules; in the prior art, the presentation of XDMS can also be presented Now the server is merged, and various rules are saved in the presence server.
  • the publisher of the presentation information must be the presentation client itself, which is always less flexible and has a poor user experience.
  • the presentation information distribution method is called a non-delegation distribution method; if the other person or the device can be entrusted to publish the presentation information instead of the user, the above-mentioned deficiencies can be solved, for example, when the user A wants to log in to the game server to play the game, the presentation state is "play". "game”, the corresponding presentation information may include: game server name, game hall name, game name, etc.; user A wants the game server to be able to delegate the presentation information so that his friends can see his status and log in to The same game server plays games with him. User A does not need to manually publish the presentation information; if a company CEO is about to meet, he asks the secretary to set his status to "Meeting". The secretary uses some software to post the presentation information of the CEO to the presence server. Obviously, the commission is used. The mechanism can improve the user experience.
  • the publisher who presents the information must be the presentity client itself, and the prior art system cannot complete the presence information service with the delegation mechanism, so that when the user uses an application, the other device cannot be trusted.
  • the entity publishes its presence information, and requires the user to log in to another program to publish the presentation information.
  • the user experience is poor and inflexible.
  • the presence information of the service is not clear to the user.
  • the content of the presented information is limited, making the business display information poor.
  • the present invention provides a method and system for distributing presence information with a delegation mechanism, which makes the distribution of presentation information more flexible and rich, and can improve the user experience.
  • the present invention provides a method for publishing presence information, including: a delegated presentity client or application server sends a publish message of the presentity client to the presence server;
  • the presence server determines that the received message is a delegation
  • the message is processed according to the delegation authorization rule
  • the presence server determines that the received message is a non-delegation issue
  • the message is processed according to a non-delegation issue mode
  • the presence server sends the presence information obtained after processing the above message to pre-subscribe to the presentation letter. Observing the client.
  • the delegation authorization rule includes entrusting the issuance of an authorization rule, and the presentation server determines, according to the entrusted release authorization rule, what entrustment manner is used for the release message.
  • the delegation authorization rule further includes a delegation content authorization rule
  • the trusted content authorization rule includes a combination of one or more of a personal entrusted authorization rule, a general entrusted authorization rule, and a default rule.
  • the delegation authorization rule includes a delegation filtering rule
  • the rendering server filters the content of the presentation information to be published according to the delegation filtering rule.
  • the presence server determines that the received message is a delegated release, including:
  • the presence server determines that the message is a commissioned release
  • the presence server determines that the message is a commissioned publication according to the field.
  • the message received according to the processing of the delegation authorization rule includes: determining whether the received message needs to wait for the client to confirm, and if it is necessary to wait for the confirmation, the presentation server performs a process of waiting for confirmation.
  • the message received according to the processing of the delegation authorization rule includes determining whether the received message needs to be rejected, and if so, the presence server refuses to publish the message.
  • the entrusted release authorization rule has a validity period, a time period, and/or a number of times of publishing the message, and the presence server allows the message when the message to be published is within the set validity period, time period, and/or number of times. release.
  • the present invention also provides a system for publishing presence information, including a presence client, a presentation server, a presentation XML file management system, and a delegated presence client or application server;
  • the delegated presentity client or application server sends a publish message of the presentity client to the presence server;
  • the presence server processes the received message issued by the delegation according to the delegation authorization rule, or processes the received message that is not authorized to be distributed according to the non-delegation publishing mode, and sends the presence information obtained after processing the message to the observed client who subscribes to the presentation information.
  • the entrusted authorization rule The body is set in the rendering server or the presentation ML file management system.
  • the presence server includes a presence information synthesis and distribution device, a delegation check and a processing device, wherein:
  • the entrusting inspection and processing device is configured to check whether the published message received from the delegated presentity client or the application server is a delegated release, and if it is a delegated release, the published message is processed according to the delegation authorization rule, and then the obtained presentation is performed.
  • the information is sent to the presentation information synthesizing and distributing device; if it is for non-delegation publishing, the publishing message is directly sent to the presentation information synthesizing and distributing device;
  • the information synthesizing and distributing device is configured to process the received message according to the setting rule and output the message to the observing client. .
  • the entrusting check and processing device is further configured to filter the content to be distributed according to the entrusted filtering rule, and send the message to be distributed to the presence information synthesizing and distributing device, where the entrusted filtering rule is presented by the presentity in the XML Set in the file management system. Further, the entrusted checking and processing device is further configured to wait for the entrusting party to confirm and then send the information to the presence information synthesizing and distributing device when the received message needs to be acknowledged by the entrusting party.
  • the entrusted checking and processing device is further configured to reject the publishing when the received posting message needs to be rejected.
  • the entrusted checking and processing device is further configured to: when the received message is within a set validity period, a time period, and/or a number of times, send the message to the presence information synthesizing and distributing device.
  • the presence server includes:
  • Delegate an authorization processing device configured to receive a publishing message sent by the trusted presentity client or the application server, and send the message that is issued in a trusted manner and allowed to be published to the presentation information synthesizing and distributing device;
  • the presentation information synthesizing and distributing device receives the presentation message sent by the entrusted release authorization processing device, processes the presentation message according to the setting rule, and outputs the presentation message to the observing client.
  • the entrusted release authorization processing device is further configured to wait for the entrusting party to confirm and then send the notification message to the presence information synthesizing and distributing device when the received posting message needs to wait for confirmation by the entrusting party.
  • the entrusted release authorization processing device is further configured to receive the release cancellation When the content needs to be rejected, it refuses to publish.
  • the presentation information synthesizing and distributing device is further configured to filter the received input information according to the entrusted filtering rule, and output the information that is allowed to be published, where the entrusted filtering rule is set in the presenting XDMS or the rendering server. in.
  • the present invention further provides a presentation server, including a presentation information synthesis and distribution device, and further comprising:
  • the entrusting check and processing device is configured to check whether the published message received from the delegated presentity client or the application server is a trusted publishing mode, and if it is a trusted publishing mode, the published message is processed according to the delegation authorization rule, and then the obtained message is obtained.
  • the presentation information is sent to the presentation information synthesizing and publishing device; if it is the non-delegation publishing method, the posting message is directly sent to the presentation information synthesizing and distributing device.
  • the entrusted checking and processing device is further configured to filter the content to be distributed according to the entrusted filtering rule, and send the message to be distributed to the presence information synthesizing and distributing device.
  • the entrusted checking and processing device is further configured to wait for the entrusting party to confirm and then send the information to the presence information synthesizing and distributing device when the received posting message needs to wait for confirmation by the entrusting party.
  • the entrusted checking and processing device is further configured to reject the publishing when the received posting message needs to be rejected.
  • the entrusted checking and processing device is further configured to: when the received posting message is received within the set validity period, time period, and/or number of times, send the message to the presence information synthesizing and distributing device.
  • the present invention also provides another presentation server, including a presentation information synthesizing and distributing device, and further comprising:
  • the authorization processing device is commissioned to receive the posting message sent by the delegated presentity client or the application server, and the message issued for the delegation mode and allowed to be published is sent to the presence information synthesizing and distributing device.
  • the delegating and issuing authorization processing device is further configured to wait for the entrusting party to confirm and then send the information to the presence information synthesizing and distributing device when the received posting message needs to be confirmed by the entrusting party. Further, the entrusted release authorization processing device is further configured to refuse to issue when the received release message needs to be rejected for publication.
  • the presentation information synthesizing and distributing device is further configured to filter the received input information according to the entrusted filtering rule, and output the information that is allowed to be published, where the entrusted filtering rule is set in the rendering XDMS or in the rendering server. .
  • the present invention further provides a presentation information synthesizing and distributing apparatus, including at least one of a viewer filtering unit, a content authorization rule checking unit, and a partial notification processing unit, and a presentation information synthesizing unit and a presentation information issuing unit, further comprising: a content authorization processing unit, configured to process the received input information according to the entrusted content authorization rule, and output the content that allows the entrusted publishing content; the message output by the presentation information synthesizing unit passes the entrusted content authorization processing unit, and the observation body After processing, at least one of the three units of the filtering unit, the content authorization rule checking unit, and the partial notification processing unit is output to the presentation information issuing unit.
  • a presentation information synthesizing and distributing apparatus including at least one of a viewer filtering unit, a content authorization rule checking unit, and a partial notification processing unit, and a presentation information synthesizing unit and a presentation information issuing unit, further comprising: a content authorization processing unit, configured to process the received input information according
  • the apparatus further includes: a request filtering processing unit, configured to filter the received input information according to the trusted filtering rule, and output the content that is allowed to be released after filtering; and the message output by the presenting information synthesizing unit passes the trusted content
  • the authorization processing unit, the delegation filtering processing unit, and the observing body filtering unit, the content authorization rule checking unit, and the partial notification processing unit are processed by at least one of the three units, and output to the presentation information issuing unit.
  • the above technical solution of the present invention can realize the requirement that the user entrusts other people or other application servers to publish the presence information; the presentation information can be published in the process of the user using the application, and does not need to log in to the dedicated presentation information publishing terminal, so that the presentation is performed.
  • the release of information is more flexible, reducing the number and frequency of users manually publishing presence information, and enhancing the user experience; users do not need to know a certain business very well, and do not need to remember which complex presentation information the business has; the service can provide human-machine
  • the interactive interface displays the presentation information to the user for selection, which reduces the difficulty for the user to publish and configure the presentation information. It is of great significance for business promotion, and the business content based on the presentation information is also richer, and can attract users to use the information related to the presentation information. .
  • 1 is a system structure for implementing a presence service in the prior art
  • FIG. 2 is a structural diagram of a device for synthesizing and presenting information in the prior art
  • 3 is a flow chart of an existing system interaction
  • 4 is a structural diagram of a system for implementing a presence service according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of a subscription and a release according to Embodiment 1 of the present invention.
  • FIG. 6 is a detailed system structure diagram of implementing a presence service in Embodiment 1 of the present invention.
  • FIG. 7 is a flowchart of executing a delegation authority and a delegation authority authorization rule according to Embodiment 1 of the present invention.
  • FIG. 8 is a structural diagram of a system for implementing a presence service in a second embodiment of the present invention.
  • FIG. 9 is a detailed system structural diagram of implementing a presence service in a second embodiment of the present invention.
  • the improved system includes a presentity client A 403, a delegated presentity client B or application server C 404, a presence server 102, a watch client 101, and a presence XDMS 104, wherein the presence server 102 includes a delegate check and process
  • the presentity client A 403 performs some settings in advance on the presentation XDMS 104 (eg, subscription authorization rules (which users are allowed to subscribe), content authorization rules (what information is allowed to be published), and delegation authorization rules (whether or not the delegation is allowed, what content is allowed to be posted, etc.) ));
  • the observing client 101 requests the presence server 102 to subscribe (SUBSCRIBE) to present the presentation information of the client A;
  • the presence server 102 matches according to the subscription authorization rule, if it matches, allows the subscription; and simultaneously sends the subscription information to the presentation XDMS 104 for information preservation, and saves the subscription relationship;
  • the presentity client A403 delegates the delegated presence client B or the application server C404 to publish (PUBLISH) presence information to the presence server 102; for example: the CEO delegates the secretary, the user uses a certain service (such as logging into the game server), or Click the button to trigger the commission release process;
  • the delegated presentity client B or application server C404 issues the presence information to the delegation check and processing device 405 of the presence server 102, and the entrusted inspection and processing device 405 performs the following operations - a) checking whether it is a delegated release mode;
  • step f) If it is a non-delegation publishing method, proceed to step f) ; if it is a delegation mode, enter the step C) ;
  • the presentation information synthesizing and distributing device 105 can perform processing using an existing functional unit (refer to FIG. 6, the presentation information synthesizing and distributing device 105 adopts an existing functional unit, including the presence information synthesizing unit 211, the content authorization rule checking unit 212, the observation body filtering unit 213, the partial notification processing unit 214, and the presence information issuing unit 215);
  • the presence information synthesizing and distributing device 105 sends a notification (NOTIFY) to the observing client 101.
  • the above-mentioned entrusted inspection and processing device 405 may obtain the rules for the various rules, or the presence server 102 may obtain these rules through the XCAP protocol, or if the presence server 102 subscribes to the change notifications of the rules, when the rules change, the XDMS 104 is presented.
  • the presentation server 102 may be notified; it may also be that the entrusted inspection and processing device 405 itself presents the XDMS 104 acquisition through the XCAP protocol; a public module may also be provided in the presence server 102 for specifically obtaining rules from the presentation XDMS 104 and providing Other units may be used; the above various rules may be directly stored in the presence server 102; those skilled in the art should understand that each device or unit in the present invention can obtain the corresponding rules in the above manner; Both the published presence information and the existing presence information in the presence server apply "delegation content authorization rules", "filter conditions", and then synthesize.
  • the application server includes a game server or a server having similar functions, and also includes an instant message server (such as an ICQ/MSN server).
  • the user fills in a message to be published in the game server, or only fills in the user identifier, and the game server Automatically transmitting the user identification and corresponding game-related presence information to a predetermined presence server, if the presence server is not unique, It can be sent by the user inputting the relevant identifier of the presence server.
  • the delegation method can be combined with the prior art, and the entrusted inspection process is used to judge which method to perform processing for the entrustment inspection.
  • the device receives the presence information release message, first checks whether it is a delegate release, if it is a non-delegation mode, it processes according to the existing process, and if it is a delegation mode, obtains the delegation authorization rule from the presentation XDMS 104 (including the delegation authority authorization rule ( Whether to allow delegates to publish), delegate content authorization rules (allowing content to be delegated), and delegate filtering rules (which will be published if the filter criteria are met, others will be discarded).
  • the delegate filter rules can also be included in the delegate content authorization rules. In the case, it is determined flexibly according to the actual situation), and the presentation information is issued according to the entrusted authorization rule.
  • Method 1 Receive the user identifier of the message publisher and the user identifier of the owner of the presentation information, and then compare, if the matching is consistent, the non-delegation mode, if not, the delegation mode.
  • Method 2 a field indicating the publication of the delegation, such as a "Delegation" field, may be added to the posting message (message header or message body).
  • the message is placed in the information sent when the message is posted. It can be anywhere, as long as the presence server can detect the message according to a pre-defined protocol, such as in the published presence information, and the sub-segments can be set to any of the fields.
  • the entrusted inspection and processing device 405 After receiving the release message, the entrusted inspection and processing device 405 obtains the entrusted release authorization rule from the presentation XDMS 104, and performs matching according to the entrusted release authorization rule;
  • step 3 Check if the sender (the entrusted party) has a match in the prohibition list, and if so, refuse to publish; otherwise, proceed to step 3);
  • the index delegates the result corresponding to the matching item in the authorization rule, and if the result is not allowed, proceeds to step 6), and if the result is allowed, the matching item is performed in the delegation content authorization rule.
  • the corresponding processing rule personal entrusted content authorization rule or general entrusted content authorization rule
  • the process of confirming the execution may be to select a delegation content authorization rule, such as a general entrusted content authorization rule or a personal entrusted content authorization rule, or may be directly selected. Published content options, you can also reject);
  • the matching record table includes personal identity matching. According to the specific identity of the individual (Identity), for example, to personal Zhang San, Li Si) and universal identity matching (meaning not specific to the individual, you can use a public identity to match the judgment, such as *@163.
  • the entrusted content authorization rule includes a personal entrusted content authorization rule and a general entrusted content authorization rule, and the personal entrusted content authorization rule corresponds to the personal identification, and the universal entrusted content authorization rule corresponds to the universal identification; in these rules, the corresponding rules can be formulated.
  • [email protected] helps Li Si to send the message
  • the matching identifier is personal identification
  • the corresponding rule is allowed
  • the personal identification [email protected] is matched in the delegation content, and the matching result is "*@163 .com”
  • the corresponding rule is to allow location information to be published;
  • the release time and the number of times can be limited in the entrusted release authorization rule, such as the validity period is 8:00 ⁇ 18:00 every day, the number of times is specified 100 times, the subscription is invalid after 100 times, no longer published, need to re-subscribe, or renew subscription, etc. Wait.
  • the structure and corresponding flow of the presentity client of the present invention are described below - an additional delegation processing module added in the presentity client of the present invention, and the presentity client executes the following processing flow;
  • the release message indicates the delegate release method, such as adding a delegate release field in the release message header;
  • the posting message may not add a field, but the user identifier of the sender and the user identifier of the owner of the presentation information may be used by the presence server, or a field indicating the non-delegation mode may be added.
  • the system of this embodiment includes a presentity client A 403, a delegated presentity client B or an application server C 404, a presence server 102, a viewer client 101, and a presence XDMS 104, wherein the presence server 102 includes a delegation authority
  • the trusted content authorization processing unit 702 is located in the existing presentation information synthesis.
  • the trusted content authorization processing device 702 in the present invention is not limited to the position in the embodiment. It may be any position between the presentation information synthesizing unit 211 and the presentation information publishing unit 215; the specific subscription and distribution process of this embodiment is as follows:
  • the presentity client A 403 performs some settings in advance on the presentation XDMS 104 (eg, subscription authorization rules (which users are allowed to subscribe), content authorization rules (what information is allowed to be published), delegation authorization rules, etc.); 2)
  • the viewer client 101 requests the presence server 102 to subscribe to (SUBSCRIBE) the presence information of the client client A;
  • the presence server 102 matches according to the subscription authorization rule, if it matches, allows the subscription; and saves the subscription relationship at the same time;
  • the presentity client A403 delegates the presence client B or the application server C404 to publish (PUBLISH) presence information to the presentation server 102;
  • the presentity client B or the application server C404 issues the presence information to the delegated distribution authorization processing device 701 of the presence server 102, and the delegation authority processing device 701 performs the following operations: a) checking whether it is a trusted distribution mode;
  • step d If it is a non-delegation release method, proceed to step d); if it is a delegation mode, proceed to step c);
  • Each unit in the presentation information synthesizing and distributing device 105 performs the following process: the presentation information synthesizing unit 211 is configured to synthesize the newly released presentation information and the presentation information saved in the server;
  • the content authorization rule checking unit 212 is configured to filter the information that is not allowed to be published according to the rule set by the presentity client (what information is allowed to be posted for a certain observing client);
  • the delegation content authorization processing unit 702 determines which content is allowed to be posted according to the Delegation Content Authorization Rule.
  • the observation body filtering unit 213 is configured to filter out information that is not desired to be received according to a rule set by the observation body (which information is not desired to receive a certain presentation client) (for example, the observation body only wants the user to change from the shutdown to the startup notification, Other presentation information will be filtered out);
  • the partial notification processing unit 214 filters the information that is not in the subscription scope according to the rules set by the observer client 101 when SUBSCRIBE subscribes (for example, only receiving presence information related to the user location);
  • the presentation information issuing unit 215 is configured to notify the observed client information 101 of the processed presence information NOTIFY; 7) The presentation information issuing unit 215 transmits a notification (NOTIFY) to the observer client 101.
  • the presence information synthesizing and distributing device 105 further includes a request filtering processing unit that publishes only the content that meets the filtering condition according to the delegation filter.
  • the processing procedure of the delegation content authorization processing unit 702 in this embodiment may be located at any position between the presentation information synthesizing unit 211 and the presentation information issuing unit 215, and the processing of the process may be flexibly set.
  • the delegation content authorization processing unit and the delegation filtering processing unit may be distributed at any position between the presentation information synthesizing unit 211 and the presentation information distribution unit 215, and the processing order of the delegation content authorization processing unit and the delegation filtering processing unit may also be adjusted, each The combination can be based on specific needs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Description

一种发布呈现信息的方法和*** 技术领域
本发明涉及一种发布呈现信息的方法和***, 尤其涉及一种具有委托机 制的发布呈现信息的方法和***。
背景技术
目前, 呈现业务的应用越来越广泛, 呈现业务 (Presence Service) 是一 种搜集和发布呈现信息(presence information)的通信业务。可能许多人希望 获取呈现业务用户的呈现信息, 这些人可能包括用户的家人、 朋友, 也可能 包含陌生人, 而很多呈现信息都是用户隐私。 呈现业务使用户可以利用各种 终端, 突破空间与时间的限制, 寻找聊天伙伴、 査询伙伴的状态信息等, 实 现即时的文本与多媒体信息交流。 通过呈现服务器(Presence Server)完成用 户状态的呈现与管理, 根据呈现信息, 可以知道对方是否在线、 正在干什么 (如开会、 吃饭等)、 心情、 客户端能力、 爱好等等信息, 用户可以通过发送 邀请给其它用户, 进行铃声、 图片、 文件等媒体内容共享。
图 1描述了现有技术中实现呈现业务的***结构, 包括呈现体客户端或 者应用服务器(Application Server) 103、 呈现服务器(Presence Server) 102、 观察体客户端 (Watcher) 101和呈现 XDMS (Presence XML Document Management System, 呈现 XML文件管理***) 104; 呈现体客户端或者应用 服务器(Application Server) 103为呈现信息源, 当其呈现信息发生改变时, 主动向呈现服务器 102发送 PUBLISH发布消息, 发布呈现信息。
呈现体客户端与观察体客户端 101可以是移动终端, 如手机、 PDA (掌上 电脑)、 智能终端(例如数字机顶盒)等, 也可以是固定终端, 移动终端上的 上述功能同样可以运用于固定终端中, 目前也出现了具有会话初始化协议
(Session Initiation Protocol, SIP) 功能的固定终端; 呈现体客户端或者应用 服务器 103上有一个用于发布消息的应用程序, 用户可以通过选择发布需要 发布的信息, 确认后, 呈现体客户端或者应用服务器 103将所有消息包括用 户标识符等一并发送到呈现服务器 102。 .
呈现服务器 102负责接收观察体客户端 101的 SUBSCRIBE订阅消息, 根据被订阅的呈现体客户端预先设置的订阅授权规则来判断订阅的结果; 接 收呈现体客户端的 PUBLISH发布消息, 按照呈现体客户端或者应用服务器 103/观察体客户端 101原先设置的一些规则 (包括内容合成、 授权和过滤) 进行处理, 最终通过 NOTIFY通知将呈现信息发布给观察体客户端 101。
观察体客户端 101订阅呈现体客户端或者应用服务器 103的呈现信息, 并接收来自呈现服务器 102的通知消息。
呈现 XDMS 104保存呈现体客户端或者应用服务器 103的授权列表(如 订阅授权列表、 内容授权列表、委托授权列表等)、群组列表等, 其它装置如 呈现信息合成和发布装置可以通过协议如 ML文档配置和访问协议 (XCAP) 直接访问呈现 XDMS104, 也可以通过专用的信息访问单元从呈现 DMS104 中的授权列表中获取一系列的信息, 如订阅授权规则, 内容授权规则、 委托 授权列表等; 当然如果需要, 本领域技术人员可以将呈现 XDMS104直接设 置到呈现服务器 102中, 也可以将两者设置成独立的服务单元, 通过特定的 通信协议进行访问。
上述的 SUBSCRIBE和 PUBLISH等均为 SIP消息。 PUBLISH消息的 SIP 消息头中包含呈现体客户端的标识, 消息体中包含 XML文档, 为呈现体客 户端的呈现信息。订阅和发布消息并不局限于 SIP消息格式, 在 IP多媒体系 统(IP Multimedia Subsystem, IMS) 网络中是 SIP消息; 对于其他网络 (例 如 IP网络中的 ICQMSN应用), 可以不为 SIP消息, 为自定义的消息格式。 呈现服务器 102包括呈现信息合成和发布装置 105, 呈现信息合成和发布装 置 105是最重要的一个装置, 图 2描述了它的结构, 它包括依次连接的呈现 信息合成单元 211、 内容授权规则检查单元 212、 观察体过滤单元 213、 部分 通知处理单元 214和呈现信息发布单元 215; 呈现信息合成单元 211用于将 新发布的呈现信息和服务器中保存的呈现信息进行合成处理; 内容授权规则 检查单元 212用于按照呈现体客户端设置的规则 (对于某个观察体客户端允 许发布哪些信息),将不允许发布的信息过滤掉;观察体过滤单元 213用于按 照观察体设置的规则(如不希望接收某个呈现体客户端的哪些信息),将不希 望接收的信息过滤掉 (比如观察体仅希望用户从关机变为开机时通知, 其他 呈现信息将被过滤掉); 部分通知处理单元 214按照观察体客户端 101 在 SUBSCRIBE订阅时设置的规则 (比如只接收用户位置相关的呈现信息), 将 不属于订阅范围的信息过滤掉; 呈现信息发布单元 215用于将处理后的呈现 信息 NOTIFY通知给观察体客户端 101。上述内容授权规则检查单元 212、观 察体过滤单元 213、 部分通知处理单元 214的先后连接关系可以根据实际需 要设定。
图 3为现有***交互流程图, 具体流程如下:
1 )呈现体客户端 A首先要在呈现 XDMS进行一些设置 (例如订阅授权 规则(允许哪些用户订阅)、 内容授权规则(允许发布哪些信息)等, 呈现服 务器可以通过 XCAP协议来获得这些规则, 或者如果呈现服务器订阅了这些 规则的改变通知, 当这些规则发生改变时, 呈现 DMS会通知呈现服务器。 订阅授权规则 (Subscription Authorization Rule)和内容授权规则 (Content Authorization Rule ) 保呈现一个 XML文件中, 此 XML包括 3个重要的元素 <Condition>、 <Action>、 <Transformation>。 <Condition>表示匹酉己的条件, <Acti0n>表示匹配的结果, (允许、拒绝、友好拒绝、等待确认), <Condition> 和<八(^011>的组合对应订阅授权规则, 用于按照呈现体客户端设置的规则处 理观察体客户端的订阅请求; <TranSformati0n>对应内容授权规则, 用于按照 呈现体客户端设置的规则(对于某个观察体客户端允许发布哪些信息), 将不 允许发布的信息过滤掉;
2)观察体 B向呈现服务器请求订阅 (SUBSCRIBE)呈现体客户端 A的 呈现信息;
3)呈现服务器根据呈现 XDMS中的订阅授权规则匹配, 如果匹配, 允 许订阅; 同时保存此订阅关系;
4) 呈现体客户端 A向呈现服务器发布 (PUBLISH)信息;
5)呈现服务器根据一系列的规则处理后向观察体 B发送呈现信息的通知 (NOTIFY) o
上述方案中呈现 XDMS与呈现服务器分离,各种规则保存在呈现 XDMS 上, 呈现体客户端通过聚合代理(Aggregation Proxy)使用 XCAP协议, 或 者应用服务器直接使用 XCAP协议, 或者用户通过人机交互界面 (如网页) 去呈现 XDMS设置和修改各种规则; 现有技术中, 呈现 XDMS也可以和呈 现服务器合并, 各种规则保存在呈现服务器中; 在上述的现有技术中, 呈现 信息的发布者必须是呈现体客户端本身, 始终不太灵活, 用户体验也差, 我 们将上述现有的呈现信息发布方式称之为非委托发布方式; 如果能够委托他 人或者设备代替其本人发布呈现信息, 就能解决上述不足, 例如: 用户 A希 望登陆到游戏服务器玩游戏时, 其呈现状态为 "玩游戏", 对应的呈现信息可 以包括: 游戏服务器名、 游戏大厅名称、 游戏名称等; 用户 A希望游戏服务 器能够委托其发布呈现信息, 这样他的朋友就可以看到他的状态, 也能够登 陆到相同的游戏服务器和他一起玩游戏。 用户 A就不需要自己手工去发布呈 现信息; 再如某公司老总即将开会, 其要求秘书将其状态设置为 "开会", 秘 书使用某种软件向呈现服务器发布老总的呈现信息; 显然, 利用委托机制可 以很好地提升用户体验。
但是在现有技术中, 呈现信息的发布者必须是呈现体客户端本身, 现有 技术中的***是无法完成具有委托机制的呈现信息服务的, 这样当用户使用 某种应用时, 无法委托其他实体发布其呈现信息, 需要用户自己登陆另外一 个程序发布呈现信息, 用户体验差, 不灵活, 用户使用某些业务时, 由于对 于业务不熟悉, 此业务具备哪些呈现信息, 用户不清楚, 这样就限制了呈现 信息的内容, 使得业务展现信息贫乏。
发明内容
针对上述现有技术中存在的问题, 本发明提供了一种具有委托机制的发 布呈现信息的方法和***, 使呈现信息的发布变得更加灵活, 丰富, 能很好 的提升用户体验。
为此, 本发明提供一种发布呈现信息的方法, 包括- 受委托的呈现体客户端或应用服务器将呈现体客户端的发布消息发送给 呈现服务器;
当呈现服务器判定接收到的消息为委托发布时, 按照委托授权规则处理 所述消息;
当呈现服务器判定接收到的消息为非委托发布时, 按照非委托发布方式 处理所述消息;
呈现服务器将处理上述消息后得到的呈现信息发送给预先订阅该呈现信 息的观察体客户端。
进一步地, 所述委托授权规则包括委托发布授权规则, 所述呈现服务器 依所述委托发布授权规则判断该发布消息采用何种委托方式处理。
更进一步地, 所述委托授权规则还包括委托内容授权规则, 所述委托内 容授权规则包括个人委托授权规则、 通用委托授权规则和默认规则中的一个 或几个的组合。
再进一步地, 所述委托授权规则包括委托过滤规则, 所述呈现服务器根 据委托过滤规则过滤要发布的呈现信息内容。
进一步地, 呈现服务器判定接收到消息为委托发布包括:
当发布者的用户标识与呈现信息拥有者的用户标识一致时, 呈现服务器 判定所述消息为委托发布; 或者
当所述的消息中设置了表明为委托发布方式的字段时, 呈现服务器根据 该字段判定所述消息为委托发布。
进一步地, 所述根据委托授权规则的处理接收到的消息包括: 判断接收 到的消息是否需要等待委托方确认, 如果需要等待确认, 则呈现服务器进行 等待确认的处理。
进一步地, 所述根据委托授权规则的处理接收到的消息包括判断接收到 的消息是否需要拒绝, 如果是, 则呈现服务器拒绝发布该消息。
更迸一步地, 所述委托发布授权规则中有发布消息的有效期、 时间周期 和 /或次数, 当待发布的消息在设定的有效期、 时间周期和 /或次数内时, 呈现 服务器允许该消息发布。
此外, 本发明还提供一种发布呈现信息的***, 包括呈现体客户端、 呈 现服务器、 呈现 XML文件管理***, 和受委托的呈现体客户端或应用服务 器;
所述的受委托的呈现体客户端或应用服务器将呈现体客户端的发布消息 发送给呈现服务器;
所述的呈现服务器按照委托授权规则处理委托发布的接收消息, 或者按 照非委托发布方式处理未委托发布的接收消息, 并将处理上述消息后得到的 呈现信息发送给订阅该呈现信息的观察体客户端; 所述的委托授权规则由呈 现体在呈现服务器或者呈现 ML文件管理***中设置。
进一步地, 所述的呈现服务器包括呈现信息合成和发布装置、 委托检査 和处理装置, 其中:
委托检查和处理装置, 用于检査从受委托的呈现体客户端或应用服务器 接收的发布消息是否为委托发布, 如果为委托发布, 根据委托授权规则对发 布消息进行处理, 然后将获得的呈现信息发送给呈现信息合成和发布装置; 如果为非委托发布, 直接将发布消息发送给呈现信息合成和发布装置;
呈现信息合成和发布装置, 用于将接收到的消息按照设定规则进行处理 后输出给观察体客户端。。
更进一步地, 所述委托检查和处理装置, 还用于根据委托过滤规则过滤 要发布的内容, 将要发布的消息发送给呈现信息合成和发布装置, 所述的委 托过滤规则由呈现体在呈现 XML文件管理***中设置。 ' 更进一步地, 所述委托检査和处理装置, 还用于当接收到的消息需要等 待委托方的确认时, 等待委托方确认后再发送给呈现信息合成和发布装置。
更进一步地, 所述委托检查和处理装置, 还用于当接收到的发布消息需 要拒绝发布时, 拒绝发布。
更进一步地, 所述委托检査和处理装置, 还用于当接收到的消息在设定 的有效期、 时间周期和 /或次数内时, 将该消息发送给呈现信息合成和发布装 置。
进一步地, 所述的呈现服务器包括:
委托发布授权处理装置, 用于接收受委托的呈现体客户端或应用服务器 发送的发布消息, 将为委托方式发布且允许发布的消息发送给呈现信息合成 和发布装置;
呈现信息合成和发布装置, 接收到委托发布授权处理装置发送的呈现消 息后, 对所述的呈现消息按照设定规则进行处理后输出给观察体客户端。
更进一步地, 所述的委托发布授权处理装置, 还用于当接收到的发布消 息需要等待委托方的确认时, 等待委托方确认后再发送给呈现信息合成和发 布装置。
更进一步地, 所述的委托发布授权处理装置, 还用于当接收到的发布消 息需要拒绝发布时, 拒绝发布。
更进一步地, 所述的呈现信息合成和发布装置, 还用于将接收到的输入 信息根据委托过滤规则进行过滤, 输出允许发布的信息, 所述的委托过滤规 则设置在呈现 XDMS中或者呈现服务器中。
除上述发布呈现信息的方法和***之外,本发明还提供一种呈现服务器, 包括呈现信息合成和发布装置, 还包括:
委托检査和处理装置, 用于检查从受委托的呈现体客户端或应用服务器 接收的发布消息是否为委托发布方式, 如果为委托发布方式, 根据委托授权 规则对发布消息进行处理, 然后将获得的呈现信息发送给呈现信息合成和发 布装置; 如果为非委托发布方式, 直接将发布消息发送给呈现信息合成和发 布装置。
进一步地, 所述委托检查和处理装置, 还用于根据委托过滤规则过滤要 发布的内容, 将要发布的消息发送给呈现信息合成和发布装置。
进一步地, 所述委托检查和处理装置, 还用于当接收到的发布消息是否 需要等待委托方的确认时, 等待委托方确认后再发送给呈现信息合成和发布 装置。 '
进一步地, 所述委托检査和处理装置, 还用于当接收到的发布消息需要 拒绝发布时, 拒绝发布。
进一步地, 所述委托检査和处理装置, 还用于当接收到发布消息在设定 的有效期、 时间周期和 /或次数内时, 将该消息发送给呈现信息合成和发布装 置。
本发明还提供另一种呈现服务器, 包括呈现信息合成和发布装置, 还包 括:
委托发布授权处理装置, 接收受委托的呈现体客户端或应用服务器发送 的发布消息, 将为委托方式发布且允许发布的消息发送给呈现信息合成和发 布装置。
进一步地, 所述的委托发布授权处理装置, 还用于当接收到的发布消息 需姜等待委托方的确认时, 等待委托方确认后再发送给呈现信息合成和发布 装置。 进一步地, 所述的委托发布授权处理装置, 还用于当接收到的发布消息 需要拒绝发布时, 拒绝发布。
进一步地, 所述的呈现信息合成和发布装置, 还用于将接收到的输入信 息根据委托过滤规则进行过滤, 输出允许发布的信息, 所述的委托过滤规则 设置在呈现 XDMS中或者呈现服务器中。
另外, 本发明又提供一种呈现信息合成和发布装置, 包括观察体过滤单 元、 内容授权规则检查单元和部分通知处理单元中至少一个, 以及呈现信息 合成单元、 呈现信息发布单元, 还包括: 委托内容授权处理单元, 用于将接 收到的输入信息根据委托内容授权规则进行处理, 将允许委托发布内容的内 容输出; 所述的呈现信息合成单元输出的消息经过委托内容授权处理单元, 以及观察体过滤单元、 内容授权规则检查单元和部分通知处理单元三个单元 中至少一个单元处理后, 输出至呈现信息发布单元。 进一步地, 该装置还包 括- 委托过滤处理单元, 用于将接收到的输入信息根据委托过滤规则进行过 滤, 将过滤后允许发布的内容输出; 所述的呈现信息合成单元输出的消息经 过委托内容授权处理单元、 委托过滤处理单元, 以及观察体过滤单元、 内容 授权规则检査单元和部分通知处理单元三个单元中至少一个单元处理后, 输 出至呈现信息发布单元。
采用本发明的上述技术方案, 能够实现用户委托其他人或其他应用服务 器发布呈现信息的需求; 能够在用户使用应用的过程中发布呈现信息, 不需 要登陆到专门的呈现信息发布终端上, 使呈现信息的发布更加灵活, 减少了 用户手工发布呈现信息的次数和频率, 增强用户体验; 用户不需要对某个业 务非常了解, 不需要记住业务具备哪些复杂的呈现信息; 该业务可以提供人 机交互界面, 将其呈现信息显示给用户进行选择, 降低了用户发布和配置呈 现信息的难度, 对于业务推广具有重要意义, 基于呈现信息的业务内容也更 加丰富, 可以吸引用户使用呈现信息相关的业务。
附图说明
图 1为现有技术中实现呈现业务的***结构;
图 2为现有技术中呈现信息合成和发布装置的结构图;
图 3为现有***交互流程图; 图 4为本发明实施例一中实现呈现业务的***结构图;
图 5为本发明实施例一的订阅与发布流程图;
图 6为本发明实施例一中实现呈现业务的详细***结构图;
图 7为本发明实施例一的执行委托发布授权规则和委托内容授权规则的 流程图;
图 8为本发明第二实施例中实现呈现业务的***结构图;
图 9为本发明第二实施例中实现呈现业务的详细***结构图。
具体实施方式
下面结合附图对本发明做进一步的说明。
实施例一
参考图 4, 改进后的***包括呈现体客户端 A403、 受委托的呈现体客户 端 B或者应用服务器 C404、 呈现服务器 102、 观察体客户端 101和呈现 XDMS104, 其中呈现服务器 102包括委托检查和处理装置 405、 呈现信息合 成和发布装置 105, 参考图 5, 具体的订阅和发布流程如下:
1 )呈现体客户端 A403预先在呈现 XDMS104进行一些设置(例如订阅 授权规则(允许哪些用户订阅)、 内容授权规则(允许发布哪些信息)和委托 授权规则 (是否允许委托、 允许委托发布哪些内容等));
2)观察体客户端 101向呈现服务器 102请求订阅 (SUBSCRIBE) 呈现 体客户端 A的呈现信息;
3)呈现服务器 102根据订阅授权规则匹配, 如果匹配, 允许订阅; 同时 将该订阅信息发送到呈现 XDMS104中进行信息保存, 同时保存此订阅关系;
4)呈现体客户端 A403委托受委托的呈现体客户端 B或者应用服务器 C404向呈现服务器 102发布 (PUBLISH) 呈现信息; 例如: 老总委托秘书、 用户使用某种业务(如登陆游戏服务器), 或者点击按钮触发委托发布流程;
5)受委托的呈现体客户端 B或者应用服务器 C404向呈现服务器 102的 委托检査和处理装置 405发布呈现信息, 委托检查和处理装置 405进行如下 操作- a)检查是否为委托发布方式;
b )如果为非委托发布方式, 则进入步骤 f) ; 如果为委托方式, 进入步骤 C ) ;
c)根据委托发布授权规则 (Delegation Publishment Authorization Rule), 判 断是否允许委托发布;
d)根据委托内容授权规则 (Delegation Content Authorization Rule),判断允 许委托发布哪些内容;
e) 根据委托过滤规则 (Delegation Filter), 将不符合过滤条件的内容过滤 掉;
f)然后将呈现消息发送给呈现信息合成和发布装置;
6)呈现信息合成和发布装置 105可以采用现有的功能单元进行处理(参 考图 6, 呈现信息合成和发布装置 105采用现有的功能单元, 包括呈现信息 合成单元 211、 内容授权规则检査单元 212、 观察体过滤单元 213、 部分通知 处理单元 214和呈现信息发布单元 215);
7 ) 呈现信息合成和发布装置 105 向观察体客户端 101 发送通知 (NOTIFY)。
该实施例中, 委托检査和处理装置 405的各种功能均为可选项。
上述委托检查和处理装置 405对于各种规则的获取, 可以是呈现服务器 102通过 XCAP协议来获得这些规则, 或者如果呈现服务器 102订阅了这些 规则的改变通知, 则当这些规则发生改变时, 呈现 XDMS104会通知呈现服 务器 102; 也可以是委托检查和处理装置 405自己通过 XCAP协议去呈现 XDMS104获取;还可以在呈现服务器 102中设置一个公用的模块,专门用于 从呈现 XDMS104上获取规则, 并提供给其它单元使用; 还可以是上述各种 规则直接存储在呈现服务器 102中; 本领域技术人员应该明白, 本发明中各 个装置或者单元获取相应的规则都可以采用上述方式; 本实施例中需要对新 发布的呈现信息和呈现服务器中现有呈现信息均应用 "委托内容授权规则"、 "过滤条件", 然后再进行合成。
本实施例中, 应用服务器包括游戏服务器或具有相似功能的服务器, 也 包括即时消息服务器(如 ICQ/MSN服务器), 用户在游戏服务器中填写需要 发布的消息, 也可以只填写用户标识, 游戏服务器自动将用户标识以及相应 的与游戏相关的呈现信息发送到预定的呈现服务器,如果呈现服务器不唯一, 可以通过用户输入呈现服务器的相关标识进行发送。
上述实施例中描述了以委托方式发布呈现信息的流程,在呈现服务器 102 中, 可以将委托方式与现有技术相结合, 通过委托检查流程进行判断依据哪 种方式进行处理, 用于委托检査的装置接收到呈现信息发布消息, 首先检查 是否为委托发布, 如果为非委托方式, 则按照现有流程处理, 如果是委托方 式, 则从呈现 XDMS104上获取委托授权规则 (包括委托发布授权规则 (是 否允许委托发布)、委托内容授权规则(允许委托发布哪些内容)和委托过滤 规则(符合过滤条件的将被发布, 其它将被丢弃), 当然, 委托过滤规则也可 以被包含在委托内容授权规则中, 根据实际情况灵活确定), 根据委托授权规 则发布呈现信息。
关于检查是否为委托发布, 可以采取下列方式:
方法一、 接收消息发布者的用户标识与呈现信息拥有者的用户标识,然 后进行比较, 如果匹配一致, 则为非委托方式, 如果不一致, 则为委托方式。
方法二、 可以在发布消息(消息头或消息体) 中增加表明为委托发布的 字段, 如 "Delegation"字段, 当然, 本领域技术人员能明白, 这个消息放在 发布消息时发送的信息中的任何一处均可以, 只要呈现服务器能够根据预先 设定的协议检测到该消息即可, 例如放在发布的呈现信息中, 而且子段可以 设定为任何一种字段。
下面对执行委托发布授权规则和委托内容授权规则的流程作一个详细的 说明, 参考图 7, 具体流程如下:
1 )委托检查和处理装置 405接收到发布消息后, 从呈现 XDMS104上获取 委托发布授权规则, 根据委托发布授权规则进行匹配;
2)检查发送方(受委托方)在禁止列表中是否有匹配项, 如果有, 则拒 绝发布; 否则, 进入步骤 3 );
3 )检査不在禁止列表中的发送方在委托发布授权规则中是否还有相应的 匹配项, 如果否, 应用呈现服务器的默认策略 (如可以是拒绝或发布所有消 息); 如果是, 进入步骤 4);
4)检查是否存在多个匹配项, 如果是, 按照选择规则(如优先级)进行 选取; 5)根据获得的匹配项,索引委托发布授权规则中与该匹配项对应的结果, 如果结果不为允许, 进入步骤 6), 如果结果为允许, 则将该匹配项在委托内 容授权规则中进行再次匹配, 根据再次匹配获得的匹配项, 索引相应的处理 规则 (个人委托内容授权规则或通用委托内容授权规则)迸行处理;
6)如果结果为拒绝, 则拒绝发布;
7)如果结果为需要确认, 则执行确认的处理流程(让委托人进行选择, 可以是选择委托内容授权规则, 如通用委托内容授权规则或某个个人委托内 容授权规则, 也可以是直接选取可以发布的内容选项, 还可以拒绝);
对于各种规则的制定, 可以根据个人的需求, 灵活掌握, 上面例举的规 则的判断是利用匹配与各个规则相关联的消息字段或标识进行的。
上述本发明涉及到的各个操作步骤及各种规则的制定, 本领域技术人员 根据现有掌握的编程手段就能轻易实施。
为有助于理解, 下面列举几个具体的委托发布授权规则和委托内容授权 规则的例子, 首先要匹配委托发布授权规则, 包括查找禁止列表和匹配记录 表, 匹配记录表包括个人身份匹配(指按照具体的个人的身份(Identity)来 匹配, 例如具体到个人张三、 李四)和通用身份匹配 (指不具体到个人, 可 以采用一个具有公共特性的标识进行匹配判断, 例如 *@163.com), 根据查找 的结果进行相应的处理, 如果没有查找到匹配的标识, 采用呈现服务器默认 策略处理; 如在禁止列表中查找到匹配标识, 则拒绝发布; 如查找结果对应 的规则为拒绝, 则拒绝发布, 如查找结果对应的规则为允许, 则将该允许对 应的标识在委托内容授权规则中进行匹配, 应用匹配结果所对应的委托内容 授权规则进行处理; 如查找结果对应的规则为确认, 则进行等待确认的处理; 委托内容授权规则包括个人委托内容授权规则和通用委托内容授权规则, 个 人委托内容授权规则与个人标识相对应, 通用委托内容授权规则与通用标识 相对应; 在这些规则中可以制定符合相应规则的信息发布内容或发布范围; 下面举例说明, 假设呈现体为用户李四, 用户李四的相关规则文件如下所示-
1、 禁止列表: [email protected]
2、 匹配记录表 受委托人标识 结果 优先级
zhangsan@ 163.com 允许 1
*@163.com 拒绝 2
3、 委托内容授权规则:
受委托人标识 位置信息 游戏信息
[email protected] 拒绝 允许
*@163.com 允许 拒绝 参照上面的禁止列表、 发布授权规则和内容授权规则, 例举几个用户发 布消息的实例:
1、 如果是 [email protected]帮助李四发送信息, 由于在禁止列表中而被 拒绝;
2、 如果是 [email protected]帮助李四发送信息, 查找发布授权规则的 时候, 个人和通用均有, 匹配结果为个人的优先级高, 且对应规则为允许; 则将个人的标识 "[email protected]"在内容授权规则中进行匹配, 匹配的 结果为釆用 "[email protected]"对应的委托内容授权规则, 允许发布游戏 信息 (在这里采用精度匹配方式, 如果在委托内容授权规则中没有 [email protected]标识, 则采用标识 "*@163.com"对应的规则进行处理, 即只允许发位置信息);
3、 如果是 [email protected]帮助李四发送信息, 查找发布授权规则的 时候, 匹配结果为通用标识, 规则对应为拒绝, 则拒绝发送;
4、 如果是 [email protected]帮助李四发送信息, 匹配标识为个人标识, 对应规则为允许; 将该个人标识 [email protected]在委托内容中进行匹配, 匹配的结果为 " *@163.com", 对应的规则为允许发布位置信息;
5、 如果是 [email protected]帮助李四发送信息, 由于在委托发布授权 规则中 (禁止列表和匹配记录表)没有匹配的标识, 根据呈现服务器的默认 策略, 可以为拒绝或者确认;
6、如果是 [email protected]帮助李四发送信息, 有匹配的标识, 但是该 标识对应的规则为确认, 则进行确认的处理过程。
而且还可以在委托发布授权规则中限定发布时间和次数, 如有效期为每 天 8:00〜18:00, 次数指定 100次, 100次以后订阅无效, 不再发布, 需要重新 订阅, 或者续费订阅等等。
针对本发明的方法,下面描述本发明的呈现体客户端的结构和相应流程- 本发明的呈现体客户端中增加的委托发布处理模块, 呈现体客户端执行 如下处理流程;
1 )询问呈现信息发布实体是否采用委托发布;
2)如果是委托发布, 发布消息中指明为委托发布方式, 如在发布消息头 中增加委托发布字段;
3 )如果为委托发布, 发布消息中可以不添加字段, 而是采用发送发布者 的用户标识与呈现信息拥有者的用户标识, 由呈现服务器进行判断, 也可以 添加表示非委托发布方式的字段。
实施例二
参考图 8, 本实施例的***包括呈现体客户端 A403、 受委托的呈现体客 户端 B或者应用服务器 C404、 呈现服务器 102、 观察体客户端 101和呈现 XDMS104, 其中呈现服务器 102包括委托发布授权处理装置 701、 呈现信息 合成和发布装置 105, 其中呈现信息合成和发布装置 105包括委托内容授权 处理单元 702, 本实施例中 (参考图 9), 委托内容授权处理单元 702位于现 有呈现信息合成和发布装置 105中的内容授权规则检査单元 212和观察体过 滤单元 213之间; 当然, 本领域技术人员应该明白, 本发明中的委托内容授 权处理装置 702并不限于本实施例中的位置, 可以是呈现信息合成单元 211 和呈现信息发布单元 215之间的任意位置; 本实施例具体的订阅和发布流程 如下:
1 )呈现体客户端 A403预先在呈现 XDMS104进行一些设置 (例如订阅 授权规则 (允许哪些用户订阅)、 内容授权规则 (允许发布哪些信息)、 委托 授权规则等); 2)观察体客户端 101向呈现服务器 102请求订阅 (SUBSCRIBE)呈现 体客户端 A的呈现信息;
3)呈现服务器 102根据订阅授权规则匹配, 如果匹配, 允许订阅; 同时 保存此订阅关系;
4)呈现体客户端 A403委托呈现体客户端 B或者应用服务器 C404向呈 现服务器 102发布 (PUBLISH)呈现信息;
5 )呈现体客户端 B或者应用服务器 C404向呈现服务器 102的委托发布 授权处理装置 701发布呈现信息,委托发布授权处理装置 701进行如下操作: a)检査是否为委托发布方式;
b)如果为非委托发布方式, 则进入步骤 d); 如果为委托方式, 进入步 骤 c);
c)根据呈现 XDMS104中的委托发布授权规则 (Delegation Publishment Authorization Rule), 判断是否允许委托发布;
d)将呈现信息发送给呈现信息合成和发布装置 105;
6)呈现信息合成和发布装置 105中的各个单元进行如下流程处理: 呈现信息合成单元 211用于将新发布的呈现信息和服务器中保存的呈现 信息进行合成处理;
内容授权规则检查单元 212用于按照呈现体客户端设置的规则 (对于某 个观察体客户端允许发布哪些信息), 将不允许发布的信息过滤掉;
委托内容授权处理单元 702根据委托内容授权规则 (Delegation Content Authorization Rule), 判断允许委托发布哪些内容;
观察体过滤单元 213用于按照观察体设置的规则 (不希望接收某个呈现 体客户端的哪些信息), 将不希望接收的信息过滤掉(比如观察体仅希望用户 从关机变为开机时通知, 其他呈现信息将被过滤掉);
部分通知处理单元 214按照观察体客户端 101在 SUBSCRIBE订阅时设 置的规则(比如只接收用户位置相关的呈现信息), 将不属于订阅范围的信息 过滤掉;
呈现信息发布单元 215用于将处理后的呈现信息 NOTIFY通知给观察体 客户端 101 ; 7)呈现信息发布单元 215向观察体客户端 101发送通知 (NOTIFY)。 针对该实施例的一种改进方案, 所述呈现信息合成和发布装置 105还包 括委托过滤处理单元, 根据委托过滤条件 (Delegation Filter), 仅发布符合过滤 条件的内容。
本领域技术人员应该明白, 本实施例中委托内容授权处理单元 702的处 理过程可以位于呈现信息合成单元 211和呈现信息发布单元 215之间的任何 一个位置处, 流程的处理先后可以灵活设置。 委托内容授权处理单元和委托 过滤处理单元可以分散在呈现信息合成单元 211和呈现信息发布单元 215之 间的任何一个位置处, 而且委托内容授权处理单元与委托过滤处理单元处理 顺序也可以调整, 各种组合可以依据具体的需求而定。
以上所述仅是本发明的优选实施方式, 应当指出, 对于本技术领域的普 通技术人员来说, 在不脱离本发明原理的前提下, 还可以作出若干改进和润 饰, 这些改进和润饰也应视为本发明的保护范围。

Claims

权 利 要 求 书
1.一种发布呈现信息的方法, 包括:
受委托的呈现体客户端或应用服务器将呈现体客户端的发布消息发送给 呈现服务器;
当呈现服务器判定接收到的消息为委托发布时, 按照委托授权规则处理 所述消息;
当呈现服务器判定接收到的消息为非委托发布时, 按照非委托发布方式 处理所述消息;
呈现服务器将处理上述消息后得到的呈现信息发送给预先订阅该呈现信 息的观察体客户端。
2.根据权利要求 1所述的发布呈现信息的方法, 其特征在于, 所述委托 授权规则包括委托发布授权规则, 所述呈现服务器依所述委托发布授权规则 判断该发布消息采用何种委托方式处理。
3. 根据权利要求 2所述的发布呈现信息的方法, 其特征在于, 所述委托 授权规则还包括委托内容授权规则, 所述委托内容授权规则包括个人委托授 权规则、 通用委托授权规则和默认规则中的一个或几个的组合。
4.根据权利要求 3所述的发布呈现信息的方法, 其特征在于, 所述委托 授权规则包括委 ft过滤规则, 所述呈现服务器根据委托过滤规则过滤要发布 的呈现信息内容。
5.根据权利要求 1至 4中任一项的发布呈现信息的方法, 其特征在于, 呈现服务器判定接收到消息为委托发布包括:
当发布者的用户标识与呈现信息拥有者的用户标识一致时, 呈现服务器 判定所述消息为委托发布; 或者
当所述的消息中设置了表明为委托发布方式的字段时, 呈现服务器根据 该字段判定所述消息为委托发布。
6.根据权利要求 1至 4中任一项的发布呈现信息的方法, 其特征在于, 所述根据委托授权规则的处理接收到的消息包括: 判断接收到的消息是否需 要等待委托方确认,如果需要等待确认,则呈现服务器进行等待确认的处理。
7.根据权利要求 1至 4中任一项的发布呈现信息的方法, 其特征在于, 所述根据委托授权规则的处理接收到的消息包括判断接收到的消息是否需要 拒绝, 如果是, 则呈现服务器拒绝发布该消息。
8.根据权利要求 2至 4中任一项的发布呈现信息的方法, 其特征在于, 所述委托发布授权规则中有发布消息的有效期、 时间周期和 /或次数, 当待发 布的消息在设定的有效期、 时间周期和 /或次数内时, 呈现服务器允许该消息 发布
9. 一种发布呈现信息的***, 包括呈现体客户端、 呈现服务器、 呈现 XML文件管理***, 其特征在于, 该***还包括: 受委托的呈现体客户端或 应用服务器;
所述的受委托的呈现体客户端或应用服务器将呈现体客户端的发布消息 发送给呈现服务器;
所述的呈现服务器按照委托授权规则处理委托发布的接收消息, 或者按 照非委托发布方式处理未委托发布的接收消息, 并将处理上述消息后得到的 呈现信息发送给订阅该呈现信息的观察体客户端; 所述的委托授权规则由呈 现体在呈现服务器或者呈现 XML文件管理***中设置。
10.根据权利要求 9所述的***, 其特征在于, 所述的呈现服务器包括 呈现信息合成和发布装置、 委托检査和处理装置, 其中:
委托检查和处理装置, 用于检查从受委托的呈现体客户端或应用服务器 接收的发布消息是否为委托发布, 如果为委托发布, 根据委托授权规则对发 布消息进行处理, 然后将获得的呈现信息发送给呈现信息合成和发布装置; 如果为非委托发布, 直接将发布消息发送给呈现信息合成和发布装置;
呈现信息合成和发布装置, 用于将接收到的消息按照设定规则进行处理 后输出给观察体客户端。
11.根据权利要求 10所述的***, 其特征在于, 所述委托检查和处理装 置, 还用于根据委托过滤规则过滤要发布的内容, 将要发布的消息发送给呈 现信息合成和发布装置, 所述的委托过滤规则由 现体在呈现 XML文件管 理***中设置。
12.根据权利要求 10所述的***, 其特征在于, 所述委托检査和处理装 置, 还用于当接收到的消息需要等待委托方的确认时, 等待委托方确认后再 发送给呈现信息合成和发布装置。
13.根据权利要求 10所述的***, 其特征在于, 所述委托检查和处理装 置, 还用于当接收到的发布消息需要拒绝发布时, 拒绝发布。
14.根据权利要求 10所述的***, 其特征在于, 所述委托检查和处理装 置, 还用于当接收到的消息在设定的有效期、 时间周期和 /或次数内时, 将该 消息发送给呈现信息合成和发布装置。
15.根据权利要求 9所述的***, 其特征在于, 所述的呈现服务器包括: 委托发布授权处理装置, 用于接收受委托的呈现体客户端或应用服务器 发送的发布消息, 将为委托方式发布且允许发布的消息发送给呈现信息合成 和发布装置;
呈现信息合成和发布装置, 接收到委托发布授权处理装置发送的呈现消 息后, 对所述的呈现消息按照设定规则进行处理后输出给观察体客户端。
16.根据权利要求 15所述的***, 其特征在于, 所述的委托发布授权处 理装置, 还用于当接收到的发布消息需要等待委托方的确认时, 等待委托方 确认后再发送给呈现信息合成和发布装置。
17.根据权利要求 15所述的***, 其特征在于, 所述的委托发布授权处 理装置, 还用于当接收到的发布消息需要拒绝发布时, 拒绝发布。
18.根据权利要求 15所述的***, 其特征在于, 所述的呈现信息合成和 发布装置, 还用于将接收到的输入信息根据委托过滤规则进行过滤, 输出允 许发布的信息,所述的委托过滤规则设置在呈现 XDMS中或者呈现服务器中。
19. 一种呈现服务器, 包括呈现信息合成和发布装置, 其特征在于, 该 呈现服务器还包括:
委托检查和处理装置, 用于检查从受委托的呈现体客户端或应用服务器 接收的发布消息是否为委托发布方式, 如果为委托发布方式, 根据委托授权 规则对发布消息进行处理, 然后将获得的呈现信息发送给呈现信息合成和发 布装置; 如果为非委托发布方式, 直接将发布消息发送给呈现信息合成和发 布装置。
20.根据权利要求 19所述的呈现服务器, 其特征在于, 所述委托检查和 处理装置, 还用于根据委托过滤规则过滤要发布的内容, 将要发布的消息发 送给呈现信息合成和发布装置。
21.根据权利要求 19所述的呈现服务器, 其特征在于, 所述委托检査和 处理装置, 还用于当接收到的发布消息是否需要等待委托方的确认时, 等待 委托方确认后再发送给呈现信息合成和发布装置。
22.根据权利要求 19所述的呈现服务器, 其特征在于, 所述委托检查和 处理装置, 还用于当接收到的发布消息需要拒绝发布时, 拒绝发布。
23.根据权利要求 19所述的***, 其特征在于, 所述委托检查和处理装 置, 还用于当接收到发布消息在设定的有效期、 时间周期和 /或次数内时, 将 该消息发送给呈现信息合成和发布装置。
24. —种呈现服务器, 包括呈现信息合成和发布装置, 其特征在于, 该 呈现服务器还包括:
委托发布授权处理装置, 接收受委托的呈现体客户端或应用服务器发送 的发布消息, 将为委托方式发布且允许发布的消息发送给呈现信息合成和发 布装置。
25.根据权利要求 24所述的呈现服务器, 其特征在于, 所述的委托发布 授权处理装置, 还用于当接收到的发布消息需要等待委托方的确认时, 等待 委托方确认后再发送给呈现信息合成和发布装置。
26.根据权利要求 24或 25所述的呈现服务器, 其特征在于, 所述的委 托发布授权处理装置, 还用于当接收到的发布消息需要拒绝发布时, 拒绝发 布。
27.根据权利要求 24所述的呈现服务器, 其特征在于, 所述的呈现信息 合成和发布装置, 还用于将接收到的输入信息根据委托过滤规则进行过滤, 输出允许发布的信息,所述的委托过滤规则设置在呈现 XDMS中或者呈现服 务器中。
28. 一种呈现信息合成和发布装置, 包括观察体过滤单元、 内容授权规 则检查单元和部分通知处理单元中至少一个, 以及呈现信息合成单元、 呈现 信息发布单元, 其特征在于, 该装置还包括:
委托内容授权处理单元, 用于将接收到的输入信息根据委托内容授权规 则进行处理, 将允许委托发布内容的内容输出;
所述的呈现信息合成单元输出的消息经过委托内容授权处理单元, 以及 观察体过滤单元、 内容授权规则检査单元和部分通知处理单元三个单元中至 少一个单元处理后, 输出至呈现信息发布单元。
29. 根据权利要求 28所述的呈现信息合成和发布装置, 其特征在于, 该 装置还包括:
委托过滤处理单元, 用于将接收到的输入信息根据委托过滤规则进行过 滤, 将过滤后允许发布的内容输出;
所述的呈现信息合成单元输出的消息经过委托内容授权处理单元、 委托 过滤处理单元, 以及观察体过滤单元、 内容授权规则检查单元和部分通知处 理单元三个单元中至少一个单元处理后, 输出至呈现信息发布单元。
PCT/CN2006/002519 2005-09-30 2006-09-25 Procede et systeme pour emettre des informations de presence WO2007036143A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN200680012244.5A CN101160846A (zh) 2005-09-30 2006-09-25 一种发布呈现信息的方法和***
EP06791108A EP1873976B1 (en) 2005-09-30 2006-09-25 A method and servers of issueing the presence information
US11/936,918 US8201241B2 (en) 2005-09-30 2007-11-08 Method and system for publishing presence information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510112504.3 2005-09-30
CN200510112504.3A CN1863172B (zh) 2005-09-30 2005-09-30 一种发布呈现信息的方法和***

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/936,918 Continuation US8201241B2 (en) 2005-09-30 2007-11-08 Method and system for publishing presence information

Publications (1)

Publication Number Publication Date
WO2007036143A1 true WO2007036143A1 (fr) 2007-04-05

Family

ID=37390501

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002519 WO2007036143A1 (fr) 2005-09-30 2006-09-25 Procede et systeme pour emettre des informations de presence

Country Status (4)

Country Link
US (1) US8201241B2 (zh)
EP (1) EP1873976B1 (zh)
CN (2) CN1863172B (zh)
WO (1) WO2007036143A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2071806A1 (en) * 2007-06-05 2009-06-17 Huawei Technologies Co., Ltd. Receiving/transmitting agent method of session initiation protocol message and corresponding processor
CN105227636A (zh) * 2008-02-14 2016-01-06 诺基亚公司 用于实施发布处理的***和方法

Families Citing this family (152)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8554868B2 (en) 2007-01-05 2013-10-08 Yahoo! Inc. Simultaneous sharing communication interface
KR101492627B1 (ko) * 2008-01-28 2015-02-16 삼성전자주식회사 위임 프레즌스 구독을 위한 시스템 및 방법
ATE531183T1 (de) * 2008-02-08 2011-11-15 Ericsson Telefon Ab L M Verfahren und vorrichtung zur autorisierung der bereitstellung von mit einer presentity eines präsenzdienstes assoziiertem indirected content
CN101946480B (zh) * 2008-02-12 2013-08-21 爱立信电话股份有限公司 观察方信息通知中的特定于观察方信息
US20090299985A1 (en) * 2008-05-27 2009-12-03 Telefonaktiebolaget Lm Ericsson (Publ) Network Based Address Book with Optional Storage of Data
JP4445559B2 (ja) * 2008-05-30 2010-04-07 株式会社東芝 プレゼンスサービス提供システムとそのサーバユニット
WO2010043017A1 (en) * 2008-10-16 2010-04-22 Research In Motion Limited Scheduling policy and quality of service through the presence access layer
US20110289195A1 (en) * 2009-02-06 2011-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Method and server for accessing and providing presence information in a communications network
WO2010093295A1 (en) * 2009-02-13 2010-08-19 Telefonaktiebolaget Lm Ericsson (Publ) A method and an arrangement for handling resource data
US8266226B2 (en) 2009-06-26 2012-09-11 International Business Machines Corporation System and method to enhance user presence management to enable the federation of rich media sessions
US9357026B2 (en) 2010-03-03 2016-05-31 Telefonaktiebolaget Lm Ericsson (Publ) Presentity authorization of buddy subscription in a communication system
WO2011140709A1 (zh) * 2010-05-12 2011-11-17 阿尔卡特朗讯 为呈现信息订阅用户过滤其订阅的呈现信息的方法和装置
CN102437968A (zh) * 2010-09-29 2012-05-02 腾讯科技(深圳)有限公司 一种代言消息发布的方法和装置
US9886727B2 (en) 2010-11-11 2018-02-06 Ikorongo Technology, LLC Automatic check-ins and status updates
US8548855B2 (en) 2010-11-11 2013-10-01 Teaneck Enterprises, Llc User generated ADS based on check-ins
CN102480514A (zh) * 2010-11-30 2012-05-30 北京千橡网景科技发展有限公司 提供呈现服务的方法、呈现服务器、web服务器及其处理方法
US9131343B2 (en) 2011-03-31 2015-09-08 Teaneck Enterprises, Llc System and method for automated proximity-based social check-ins
WO2013008238A1 (en) 2011-07-12 2013-01-17 Mobli Technologies 2010 Ltd. Methods and systems of providing visual content editing functions
CN102958009B (zh) * 2011-08-26 2017-09-08 中兴通讯股份有限公司 增强现实信息的传输方法和移动增强现实服务器
CN103034654B (zh) * 2011-10-10 2016-06-15 中国电信股份有限公司 社会化动态消息呈现控制方法及***
US8972357B2 (en) 2012-02-24 2015-03-03 Placed, Inc. System and method for data collection to validate location data
US11734712B2 (en) 2012-02-24 2023-08-22 Foursquare Labs, Inc. Attributing in-store visits to media consumption based on data collected from user devices
WO2013166588A1 (en) 2012-05-08 2013-11-14 Bitstrips Inc. System and method for adaptable avatars
US9628950B1 (en) 2014-01-12 2017-04-18 Investment Asset Holdings Llc Location-based messaging
US9537811B2 (en) 2014-10-02 2017-01-03 Snap Inc. Ephemeral gallery of ephemeral messages
US9396354B1 (en) 2014-05-28 2016-07-19 Snapchat, Inc. Apparatus and method for automated privacy protection in distributed images
IL239238B (en) 2014-06-05 2022-04-01 Mobli Tech 2010 Ltd Automatic enrichment of advertising with the help of social network trends
US9113301B1 (en) 2014-06-13 2015-08-18 Snapchat, Inc. Geo-location based event gallery
US9225897B1 (en) 2014-07-07 2015-12-29 Snapchat, Inc. Apparatus and method for supplying content aware photo filters
US10423983B2 (en) 2014-09-16 2019-09-24 Snap Inc. Determining targeting information based on a predictive targeting model
US10824654B2 (en) 2014-09-18 2020-11-03 Snap Inc. Geolocation-based pictographs
US11216869B2 (en) 2014-09-23 2022-01-04 Snap Inc. User interface to augment an image using geolocation
US10284508B1 (en) 2014-10-02 2019-05-07 Snap Inc. Ephemeral gallery of ephemeral messages with opt-in permanence
US9015285B1 (en) 2014-11-12 2015-04-21 Snapchat, Inc. User interface for accessing media at a geographic location
CN104468760A (zh) * 2014-11-28 2015-03-25 小米科技有限责任公司 提醒消息推送方法及装置
US9385983B1 (en) 2014-12-19 2016-07-05 Snapchat, Inc. Gallery of messages from individuals with a shared interest
US10311916B2 (en) 2014-12-19 2019-06-04 Snap Inc. Gallery of videos set to an audio time line
US9754355B2 (en) 2015-01-09 2017-09-05 Snap Inc. Object recognition based photo filters
US11388226B1 (en) 2015-01-13 2022-07-12 Snap Inc. Guided personal identity based actions
US10133705B1 (en) 2015-01-19 2018-11-20 Snap Inc. Multichannel system
US9521515B2 (en) 2015-01-26 2016-12-13 Mobli Technologies 2010 Ltd. Content request by location
US10223397B1 (en) 2015-03-13 2019-03-05 Snap Inc. Social graph based co-location of network users
EP3941000B1 (en) 2015-03-18 2024-02-14 Snap Inc. Geo-fence authorization provisioning
US9692967B1 (en) 2015-03-23 2017-06-27 Snap Inc. Systems and methods for reducing boot time and power consumption in camera systems
US9881094B2 (en) 2015-05-05 2018-01-30 Snap Inc. Systems and methods for automated local story generation and curation
US10135949B1 (en) 2015-05-05 2018-11-20 Snap Inc. Systems and methods for story and sub-story navigation
US10993069B2 (en) 2015-07-16 2021-04-27 Snap Inc. Dynamically adaptive media content delivery
US10817898B2 (en) 2015-08-13 2020-10-27 Placed, Llc Determining exposures to content presented by physical objects
CN105162783B (zh) * 2015-08-31 2018-09-04 小米科技有限责任公司 操作权限控制方法和装置
US9652896B1 (en) 2015-10-30 2017-05-16 Snap Inc. Image based tracking in augmented reality systems
US9984499B1 (en) 2015-11-30 2018-05-29 Snap Inc. Image and point cloud based tracking and in augmented reality systems
US10474321B2 (en) 2015-11-30 2019-11-12 Snap Inc. Network resource location linking and visual content sharing
US10356017B2 (en) * 2015-12-14 2019-07-16 T-Mobile Usa, Inc. Configurable use of local presence authorization policy
US10354425B2 (en) 2015-12-18 2019-07-16 Snap Inc. Method and system for providing context relevant media augmentation
US10285001B2 (en) 2016-02-26 2019-05-07 Snap Inc. Generation, curation, and presentation of media collections
US11023514B2 (en) 2016-02-26 2021-06-01 Snap Inc. Methods and systems for generation, curation, and presentation of media collections
US10679389B2 (en) 2016-02-26 2020-06-09 Snap Inc. Methods and systems for generation, curation, and presentation of media collections
US10339365B2 (en) 2016-03-31 2019-07-02 Snap Inc. Automated avatar generation
US10805696B1 (en) 2016-06-20 2020-10-13 Pipbin, Inc. System for recording and targeting tagged content of user interest
US11201981B1 (en) 2016-06-20 2021-12-14 Pipbin, Inc. System for notification of user accessibility of curated location-dependent content in an augmented estate
US10638256B1 (en) 2016-06-20 2020-04-28 Pipbin, Inc. System for distribution and display of mobile targeted augmented reality content
US11876941B1 (en) 2016-06-20 2024-01-16 Pipbin, Inc. Clickable augmented reality content manager, system, and network
US11044393B1 (en) 2016-06-20 2021-06-22 Pipbin, Inc. System for curation and display of location-dependent augmented reality content in an augmented estate system
US11785161B1 (en) 2016-06-20 2023-10-10 Pipbin, Inc. System for user accessibility of tagged curated augmented reality content
US10334134B1 (en) 2016-06-20 2019-06-25 Maximillian John Suiter Augmented real estate with location and chattel tagging system and apparatus for virtual diary, scrapbooking, game play, messaging, canvasing, advertising and social interaction
US10430838B1 (en) 2016-06-28 2019-10-01 Snap Inc. Methods and systems for generation, curation, and presentation of media collections with automated advertising
US9681265B1 (en) 2016-06-28 2017-06-13 Snap Inc. System to track engagement of media items
US10733255B1 (en) 2016-06-30 2020-08-04 Snap Inc. Systems and methods for content navigation with automated curation
US10855632B2 (en) 2016-07-19 2020-12-01 Snap Inc. Displaying customized electronic messaging graphics
WO2018045076A1 (en) 2016-08-30 2018-03-08 C3D Augmented Reality Solutions Ltd Systems and methods for simultaneous localization and mapping
US10432559B2 (en) 2016-10-24 2019-10-01 Snap Inc. Generating and displaying customized avatars in electronic messages
WO2018085848A1 (en) 2016-11-07 2018-05-11 Snap Inc. Selective identification and order of image modifiers
US10203855B2 (en) 2016-12-09 2019-02-12 Snap Inc. Customized user-controlled media overlays
US11616745B2 (en) 2017-01-09 2023-03-28 Snap Inc. Contextual generation and selection of customized media content
US10454857B1 (en) 2017-01-23 2019-10-22 Snap Inc. Customized digital avatar accessories
US10915911B2 (en) 2017-02-03 2021-02-09 Snap Inc. System to determine a price-schedule to distribute media content
US11250075B1 (en) 2017-02-17 2022-02-15 Snap Inc. Searching social media content
US10319149B1 (en) 2017-02-17 2019-06-11 Snap Inc. Augmented reality anamorphosis system
US10074381B1 (en) 2017-02-20 2018-09-11 Snap Inc. Augmented reality speech balloon system
US10565795B2 (en) 2017-03-06 2020-02-18 Snap Inc. Virtual vision system
US10523625B1 (en) 2017-03-09 2019-12-31 Snap Inc. Restricted group content collection
US10582277B2 (en) 2017-03-27 2020-03-03 Snap Inc. Generating a stitched data stream
US10581782B2 (en) 2017-03-27 2020-03-03 Snap Inc. Generating a stitched data stream
US11170393B1 (en) 2017-04-11 2021-11-09 Snap Inc. System to calculate an engagement score of location based media content
US10387730B1 (en) 2017-04-20 2019-08-20 Snap Inc. Augmented reality typography personalization system
US11409407B2 (en) 2017-04-27 2022-08-09 Snap Inc. Map-based graphical user interface indicating geospatial activity metrics
US10212541B1 (en) 2017-04-27 2019-02-19 Snap Inc. Selective location-based identity communication
US11893647B2 (en) 2017-04-27 2024-02-06 Snap Inc. Location-based virtual avatars
US10467147B1 (en) 2017-04-28 2019-11-05 Snap Inc. Precaching unlockable data elements
US10803120B1 (en) 2017-05-31 2020-10-13 Snap Inc. Geolocation based playlists
US11475254B1 (en) 2017-09-08 2022-10-18 Snap Inc. Multimodal entity identification
US10740974B1 (en) 2017-09-15 2020-08-11 Snap Inc. Augmented reality system
US10499191B1 (en) 2017-10-09 2019-12-03 Snap Inc. Context sensitive presentation of content
US10573043B2 (en) 2017-10-30 2020-02-25 Snap Inc. Mobile-based cartographic control of display content
US11265273B1 (en) 2017-12-01 2022-03-01 Snap, Inc. Dynamic media overlay with smart widget
US11017173B1 (en) 2017-12-22 2021-05-25 Snap Inc. Named entity recognition visual context and caption data
US10678818B2 (en) 2018-01-03 2020-06-09 Snap Inc. Tag distribution visualization system
US11507614B1 (en) 2018-02-13 2022-11-22 Snap Inc. Icon based tagging
US10885136B1 (en) 2018-02-28 2021-01-05 Snap Inc. Audience filtering system
US10979752B1 (en) 2018-02-28 2021-04-13 Snap Inc. Generating media content items based on location information
US10327096B1 (en) 2018-03-06 2019-06-18 Snap Inc. Geo-fence selection system
CN111886058B (zh) 2018-03-14 2024-06-18 斯纳普公司 基于位置信息生成可收集项
US11163941B1 (en) 2018-03-30 2021-11-02 Snap Inc. Annotating a collection of media content items
US10219111B1 (en) 2018-04-18 2019-02-26 Snap Inc. Visitation tracking system
US10896197B1 (en) 2018-05-22 2021-01-19 Snap Inc. Event detection system
US10679393B2 (en) 2018-07-24 2020-06-09 Snap Inc. Conditional modification of augmented reality object
US10997760B2 (en) 2018-08-31 2021-05-04 Snap Inc. Augmented reality anthropomorphization system
US10698583B2 (en) 2018-09-28 2020-06-30 Snap Inc. Collaborative achievement interface
US10778623B1 (en) 2018-10-31 2020-09-15 Snap Inc. Messaging and gaming applications communication platform
US10939236B1 (en) 2018-11-30 2021-03-02 Snap Inc. Position service to determine relative position to map features
US11199957B1 (en) 2018-11-30 2021-12-14 Snap Inc. Generating customized avatars based on location information
US11032670B1 (en) 2019-01-14 2021-06-08 Snap Inc. Destination sharing in location sharing system
US10939246B1 (en) 2019-01-16 2021-03-02 Snap Inc. Location-based context information sharing in a messaging system
US11294936B1 (en) 2019-01-30 2022-04-05 Snap Inc. Adaptive spatial density based clustering
US11972529B2 (en) 2019-02-01 2024-04-30 Snap Inc. Augmented reality system
US10936066B1 (en) 2019-02-13 2021-03-02 Snap Inc. Sleep detection in a location sharing system
US10838599B2 (en) 2019-02-25 2020-11-17 Snap Inc. Custom media overlay system
US10964082B2 (en) 2019-02-26 2021-03-30 Snap Inc. Avatar based on weather
US10852918B1 (en) 2019-03-08 2020-12-01 Snap Inc. Contextual information in chat
US11868414B1 (en) 2019-03-14 2024-01-09 Snap Inc. Graph-based prediction for contact suggestion in a location sharing system
US11852554B1 (en) 2019-03-21 2023-12-26 Snap Inc. Barometer calibration in a location sharing system
US11249614B2 (en) 2019-03-28 2022-02-15 Snap Inc. Generating personalized map interface with enhanced icons
US10810782B1 (en) 2019-04-01 2020-10-20 Snap Inc. Semantic texture mapping system
US10582453B1 (en) 2019-05-30 2020-03-03 Snap Inc. Wearable device location systems architecture
US10560898B1 (en) 2019-05-30 2020-02-11 Snap Inc. Wearable device location systems
US11405347B1 (en) * 2019-05-31 2022-08-02 Meta Platforms, Inc. Systems and methods for providing game-related content
US10893385B1 (en) 2019-06-07 2021-01-12 Snap Inc. Detection of a physical collision between two client devices in a location sharing system
US11307747B2 (en) 2019-07-11 2022-04-19 Snap Inc. Edge gesture interface with smart interactions
US11821742B2 (en) 2019-09-26 2023-11-21 Snap Inc. Travel based notifications
US11218838B2 (en) 2019-10-31 2022-01-04 Snap Inc. Focused map-based context information surfacing
US11429618B2 (en) 2019-12-30 2022-08-30 Snap Inc. Surfacing augmented reality objects
US11128715B1 (en) 2019-12-30 2021-09-21 Snap Inc. Physical friend proximity in chat
US11169658B2 (en) 2019-12-31 2021-11-09 Snap Inc. Combined map icon with action indicator
US11343323B2 (en) 2019-12-31 2022-05-24 Snap Inc. Augmented reality objects registry
US11228551B1 (en) 2020-02-12 2022-01-18 Snap Inc. Multiple gateway message exchange
US11516167B2 (en) 2020-03-05 2022-11-29 Snap Inc. Storing data based on device location
US11619501B2 (en) 2020-03-11 2023-04-04 Snap Inc. Avatar based on trip
US10956743B1 (en) 2020-03-27 2021-03-23 Snap Inc. Shared augmented reality system
US11430091B2 (en) 2020-03-27 2022-08-30 Snap Inc. Location mapping for large scale augmented-reality
US11290851B2 (en) 2020-06-15 2022-03-29 Snap Inc. Location sharing using offline and online objects
US11503432B2 (en) 2020-06-15 2022-11-15 Snap Inc. Scalable real-time location sharing framework
US11314776B2 (en) 2020-06-15 2022-04-26 Snap Inc. Location sharing using friend list versions
US11483267B2 (en) 2020-06-15 2022-10-25 Snap Inc. Location sharing using different rate-limited links
US11308327B2 (en) 2020-06-29 2022-04-19 Snap Inc. Providing travel-based augmented reality content with a captured image
US11349797B2 (en) 2020-08-31 2022-05-31 Snap Inc. Co-location connection service
US11606756B2 (en) 2021-03-29 2023-03-14 Snap Inc. Scheduling requests for location data
US11645324B2 (en) 2021-03-31 2023-05-09 Snap Inc. Location-based timeline media content system
US12026362B2 (en) 2021-05-19 2024-07-02 Snap Inc. Video editing application for mobile devices
US11829834B2 (en) 2021-10-29 2023-11-28 Snap Inc. Extended QR code
US12001750B2 (en) 2022-04-20 2024-06-04 Snap Inc. Location-based shared augmented reality experience system
US12020384B2 (en) 2022-06-21 2024-06-25 Snap Inc. Integrating augmented reality experiences with other components
US12020386B2 (en) 2022-06-23 2024-06-25 Snap Inc. Applying pregenerated virtual experiences in new location

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030229687A1 (en) * 2002-06-11 2003-12-11 Fujitsu Limited Presence administration method and device
WO2004021730A1 (en) * 2002-08-28 2004-03-11 Motorola, Inc. Method for authorizing location based services
US20040193920A1 (en) * 2003-03-25 2004-09-30 Krisztian Kiss Service provisioning in a communication system
US20050102389A1 (en) * 2002-08-12 2005-05-12 Mitsubishi Chemical Corporation Role-based presence enabled service for communication system
CN1625737A (zh) * 2001-12-12 2005-06-08 Ut斯达康有限公司 在互联网协议网络中提供即时业务的***与方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030023623A1 (en) * 2001-03-14 2003-01-30 Horvitz Eric J. Schema-based service for identity-based access to presence data
WO2004034719A1 (en) * 2002-10-09 2004-04-22 Nokia Corporation A communication system
US7836126B2 (en) * 2004-08-04 2010-11-16 Sap Ag Business presence system and method
KR101326403B1 (ko) * 2006-04-28 2013-11-20 삼성전자주식회사 위임 오퍼레이션 수행을 위한 시스템 및 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1625737A (zh) * 2001-12-12 2005-06-08 Ut斯达康有限公司 在互联网协议网络中提供即时业务的***与方法
US20030229687A1 (en) * 2002-06-11 2003-12-11 Fujitsu Limited Presence administration method and device
US20050102389A1 (en) * 2002-08-12 2005-05-12 Mitsubishi Chemical Corporation Role-based presence enabled service for communication system
WO2004021730A1 (en) * 2002-08-28 2004-03-11 Motorola, Inc. Method for authorizing location based services
US20040193920A1 (en) * 2003-03-25 2004-09-30 Krisztian Kiss Service provisioning in a communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1873976A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2071806A1 (en) * 2007-06-05 2009-06-17 Huawei Technologies Co., Ltd. Receiving/transmitting agent method of session initiation protocol message and corresponding processor
EP2071806A4 (en) * 2007-06-05 2009-11-11 Huawei Tech Co Ltd RECEIVE / SENDER AGENT PROCEDURE FOR MEETING INTRODUCTION PROTOCOL MESSAGE AND CORRESPONDING PROCESSOR
CN105227636A (zh) * 2008-02-14 2016-01-06 诺基亚公司 用于实施发布处理的***和方法

Also Published As

Publication number Publication date
CN101160846A (zh) 2008-04-09
CN1863172B (zh) 2010-08-25
EP1873976B1 (en) 2012-06-06
CN1863172A (zh) 2006-11-15
US20080092233A1 (en) 2008-04-17
EP1873976A1 (en) 2008-01-02
EP1873976A4 (en) 2008-08-13
US8201241B2 (en) 2012-06-12

Similar Documents

Publication Publication Date Title
WO2007036143A1 (fr) Procede et systeme pour emettre des informations de presence
WO2007036144A1 (fr) Procede et systeme pour s&#39;abonner aux informations de presence
JP5303536B2 (ja) プレゼンス技術を用いたアプリケーション情報およびコマンドの送信
JP5049438B2 (ja) 存在管理システム及び方法
JP4668503B2 (ja) 存在管理システム、コンピュータ・プログラム、多重アクセス通信ネットワーク及び方法
JP5416877B2 (ja) 存在管理システム、多重アクセスネットワーク及び処理方法
RU2477014C2 (ru) Способ группового оповещения в службе обмена сообщениями на основе протокола инициации сеанса связи &#34;sip&#34;
EP1968263A1 (en) A method and system for querying user information, and search agent, client and server
WO2007051384A1 (fr) Méthode de notification d’information de présence et système correspondant
EP1802074A1 (en) Common interest community service via presence messaging
JP2008539504A (ja) 協調的招待システムおよび方法
EP1559240B1 (en) System and method for add-on services, secondary authentication, authorization and/or secure communication for dialog based protocols and systems
US20080005119A1 (en) Remotely updating a user status on a presence server
WO2007053998A1 (fr) Méthode, système, serveur et unité pour définir des informations de configuration de corps de présence
JP2010500840A (ja) プレゼンス属性に基づくプレゼンス通知システム及び方法
JP2008538637A (ja) サーバレスピアツーピアネットワークへの参加者を招待するためのアプリケーションプログラミングインターフェース
CN101268454A (zh) 与无服务器在场协同的***和方法
TW200920059A (en) Active profile selection
KR20080008331A (ko) 서버 없는 피어-투-피어 시스템에서의 존재 모니터링
WO2009074037A1 (fr) Procédé, dispositif et système de communication instantanée
WO2007076673A1 (fr) Procede, systeme et dispositif permettant de partager des informations de presence
WO2014042968A1 (en) Establishing a communication session in heterogeneous systems
EP2764675A1 (en) System for contact subscription invitations in a cross-domain converged address book system
JP2006244100A (ja) プレゼンス情報配布システム
JP4427957B2 (ja) プレゼンスシステム及びそれに用いるプレゼンス通知先制御方法並びにそのプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 200680012244.5

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2006791108

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11936918

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 2006791108

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 11936918

Country of ref document: US