[go: up one dir, main page]

WO2002093445A1 - Messagerie interactive - Google Patents

Messagerie interactive Download PDF

Info

Publication number
WO2002093445A1
WO2002093445A1 PCT/SE2002/000925 SE0200925W WO02093445A1 WO 2002093445 A1 WO2002093445 A1 WO 2002093445A1 SE 0200925 W SE0200925 W SE 0200925W WO 02093445 A1 WO02093445 A1 WO 02093445A1
Authority
WO
WIPO (PCT)
Prior art keywords
context
user
parameter
users
parameters
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/SE2002/000925
Other languages
English (en)
Inventor
Jan Gabrielsson
Lori Robertsson
Per-Olof Nerbrant
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2002093445A1 publication Critical patent/WO2002093445A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication

Definitions

  • the present invention is related to a method for generating and distributing specialized information to users and to a network in which specialized information is 5 distributed to users of the network.
  • Any person usually is member of at least one group of people.
  • the membership can be characterised in various ways, e.g. as a relationship between family members, common interests, or as a relation between professionals.
  • Prior art systems and methods fail to disclose presentation of at least part of a personal context to dedicated persons. Further, a limitation of known systems, that use context information, is the use of static rules to affect the communication mode between two parties. 5 Although the cited patent application WO 00/18166 discloses an arrangement whereby direct user control influences a further refined selection of contextually determined interaction modalities and communication media, the application fails to describe how said user control may be implemented.
  • a further object of the invention is to provide a system for analysis of user defined contextual information, the system taking automatic actions in response to specific rules being fulfilled.
  • Still another object is to provide a system and method for user control of contextual 5 information and inference rules governing automatic actions related to communication between group members.
  • Context is defined to be a set o of parameters having values.
  • a context can also be assigned a technical subsystem, e.g. a refrigerator.
  • a refrigerator may, e.g., have a temperature and a shopping list.
  • the context can be provided to other users via a shared area comprising a compilation of the monitored parameters of each user.
  • Each user has the ability to define her/his own context and decide how it should be shared or interpreted by the other users 5 within the group by means of a dynamic set of rules. More generally, a user may define conditions affecting the presentation of the user context to other persons. The conditions may include personal access rights, dependency of time, location or fulfilment of certain conditions as specified by rules.
  • Each individual user within this group is allowed to specify events that are 0 connected to his/her own context or the contexts of other users and the context of subsystems that can trigger actions within the system. This is achieved by defining rules that are executed by a rule engine and depend upon the conditions of the parameters that have been designated within the context of each user.
  • Each individual user can also define parameters for virtual objects that have an 5 associated meaning to her/his own context such as a car.
  • a virtual object of this type has or is associated with a set of parameters representing a subsystem context. These parameters, however, only receive a meaning when certain conditions are fulfilled, e.g. that a user occupies a car as a driver and then the location of the car, and traffic conditions are examples of parameters associated with the car and receive a meaning at occupation of the car.
  • the particular car in this example, is bound to the car object defined by the user.
  • the system as described herein has a structure allowing a context to be dependent on other contexts.
  • Virtual objects are used that have an associated meaning to the contexts and that are associated with a set of parameters which can represent a subsystem context.
  • Each user context is dynamically dependent on other user contexts and of the status of virtual objects. For example, while a user is working in the office a user context might be defined in terms of location of equipment such as printers, displays, projectors, PCs, status of colleagues.
  • the virtual object represented by a car is not an active component of the context. However, while the car is occupied it becomes an active part of the context whereas the previous active components representing office equipment become inactivated. Further, occupation of the car at e.g.
  • the inclusion of the child context into the drivers context might be in dependence of the child replying to a question, resulting from the evaluation of a rule, whether or not the child wants to be picked up by the car driver.
  • This kind of interaction might be described in terms of messages: the rules engine launches an action resulting in a message for an identified person who responds to the message.
  • Other messages carry sensor values that are pushed into a user's part of the context database.
  • a parameter might have properties and might be associated with information, e.g. a message.
  • information e.g. a message.
  • the question to a child whether it wishes to be picked up or not could be extended from a simple Yes/No question to include a message suggesting a meeting place.
  • Fig. 2 is a block diagram of basic steps performed by a rule engine
  • FIG. 3 is a block diagram illustrating the basic blocks and functions of a context service
  • - Fig. 4 is diagram illustrating sensors, parameters and actions for part systems of a rule engine associated with two users
  • o - Fig. 5 is a flowchart illustrating steps performed by rule engine
  • - Fig. 6 is a picture illustrating the fields of a context database.
  • a network for providing information is schematically illustrated in Fig. 1.
  • the network comprises a plurality of sensors 1 collecting data, sensors being taken in a s general sense as devices, physical or logical, indicating some varying condition or state.
  • the sensors can be monitored for changes or themselves indicate or signal a change of a condition.
  • Each sensor defines one or more parameters available for building rules, the parameters including e.g. an output signal or a state of the sensor that can be accessed on request.
  • Some sensors 1 can also operate as actuators.
  • An example thereof is an electric o lock that could be momtored for its status, i.e. whether it is locked or unlocked, but also be remotely controlled to lock or unlock.
  • Some sensors can include only the on/off state of conditions manually set by a user.
  • a user 3 in the network has a set of the sensors 1 associated with her/him.
  • Some sensors can be global, accessible to all users, such as sensors providing information on 5 the weather or the traffic situation, or they can be restricted to be only associated with a single user or a group of users.
  • Sensors can be connected to or included in devices carried by the user or to devices owned by the user but not carried around, such as a car or a home. Some of these devices can be considered "shared" amongst some of the users of the network. For instance, the sensors located in a private home can be associated with 0 all the members of the family living in the home.
  • the sensors 1 may relate to measurements, e.g. of temperature, time, location, heart beat of a person, and thus provide measured values as parameters.
  • Other sensors are related to virtual objects or events or states, e.g. sensing that a person has occupied a particular car as the driver thereof.
  • the network further comprises a logical unit 5, also called a rule and context manager, as will be described below, that collects, interprets, evaluates and modifies context information of users, i.e. the parameters from or comprised in the sensors, and, based on a rule engine 6 comprised therein, see Fig. 3, triggers actions when a specific rule is fulfilled.
  • the rule and context manager 5 monitors the parameters of the sensors 1 and when a change is detected it stores the new values and evaluates, in the rule engine, associated rules to form adapted context information. Also new values of derived or virtual parameters can be formed using rules evaluated in the rule engine 6. Thus, when such rules that are found to be fulfilled the new derived parameter values can trigger 5 associated actions.
  • Fig. 4 distributed parts E: A and E:B of the rule engine 6 are illustrated, the parts E:A and E:B belonging to users A and B respectively and e.g. executed in mobile user devices, as will be described below.
  • the sensors 1 having labels SI - S4 provide parameter values designated PI , P2, P5 and P6 respectively.
  • the value of parameter PI o provided by sensor SI is pushed into, i.e. is automatically transmitted to, the part system E:A that is associated with user A, whereas the value of the parameter P2 provided by sensor S2 is pulled on request by the part rule engine E:A, i.e. the value of the parameter P2 is obtained by polling or interrogating the sensor S2.
  • the sensors S3 and S4 provide values of parameters P5 and P6 which are delivered on s request to the part system E:B of user B and are directly or automatically provided to the same part system E:A, respectively.
  • the parameter indicated at P8 has a value that is manually set by the user B.
  • first rules of the respective user as indicated at 8 are executed and are applied to the parameters PI , P2, P3 and to the parameters P5, P6, P8.
  • the rule of user A results in the setting of the o virtual parameter P4 that can operate the actuator Al.
  • the parameter P3 used by the first rule of user A in the part rule engine E:A associated with the user A is a shared parameter that is pushed by the part rule engine E:B associated with the other user B.
  • a shared parameter is defined to be a parameter that is pushed to at least one other user than the user with which the parameter is primarily associated.
  • the rule of user B results 5 in the setting of the virtual parameter P7.
  • Actions can be utilised to update the user's context information that is then automatically processed to be shared with other users within a group.
  • the virtual parameter P7 set by the rule engine of user B can be such a parameter that e.g. can be displayed to other users.
  • the parameter P7 can have an 0 associated action, e.g. as defined by an executive file that when the parameter is set is executed in one of the devices of the system.
  • the execution of action files can be considered to be performed in an action handler unit that can be a logic unit assigned to execute actions and physically being any of the devices of the system suitable for this kind of work.
  • An action can use the values of parameters of the rule with which the 5 action is associated and other values computed from the parameters.
  • Such an executable action file can then for instance generate an electronic message being sent to a selected user or to a user group, at a specific time or several specific times, the type of message such as SMS or voice message.
  • the contents of or the text inside such a message can be dependent on the parameter values, i.e. on the context of the user considered and also on the shared contexts of other users.
  • the message can contain information on the current place where the considered user is currently located such "I am driving the car” or "I am at home", the underlined word being set in the execution of the action.
  • the rule and context manager unit 5 may find a rule, associated with the context of a particular user that is almost fulfilled but for at least one ambiguous parameter.
  • An ambiguous parameter is defined as a parameter the value of which is currently unknown.
  • the rule engine 6 is designed to have the capability of resolving this and other types of conflicts, if specified by special rules. For example, the rule engine may decide to launch o a request for the value of an ambiguous parameter.
  • the request for a parameter value may, e.g., be directed to the person 3 having said context.
  • the system may contain information of persons, devices or entities, which may provide the requested value.
  • the rule and context manager may then launch successive requests to said persons, devices or entities until a value is received or it may launch parallel s requests to said persons, devices or entities.
  • data may be provided to the rule and context manager 5 and the rule engine 6 thereof in regard of the way in which it is to react to ambiguous parameters.
  • the system may be instructed only to prompt a user for ambiguous parameters in the case where there is a change within the o system that changes other parameters within the same rule.
  • the system may be required not to prompt a named person for the ambiguous parameter. In this case, the system may request another person or other entity for the value or the parameter is left with no defined value at all.
  • the rule engine 6 is further designed so that each user 3 has a personal rules area in s the list 21 of all personal rules, see Fig. 3, allowing personalization of rules and creation of new rules.
  • the rule engine 6 and/or the context manager 11 or parts thereof may further be more or less decentralised and then e.g. at least said personal rules area can be located at a preferred device or entity capable of executing the rules.
  • a distributed rule device or entity must be capable of communicating with the appropriate 0 database of compiled contexts, see items 13 and 17 of Fig. 3 and the description below.
  • an aggregation of parameters can be defined to create new parameters.
  • one or more sensors/parameters can be aggregated to form a joint sensor 7 creating a new "virtual" parameter.
  • the aggregation can be carried out by the rule engine 6 evaluating formulae involving two or more parameters and 5 setting the value of a new virtual parameter equal to the result of the evaluation. This is also illustrated in Fig. 4, compare the parameter P4.
  • the user 3 can assign properties to the parameters in different ways so that they behave according to the requirements of the respective user. For example, parameters can be set to control the rule engine 6 to question the user 3 at the times when a value is needed or at predetermined time intervals. Further, parameters can be defined to be polled by the system, e.g. so that a logical function accesses the value of a sensor that is continuously measuring the parameter. Other parameters can be blocked from the "shared view”. Further, parameters can be connected to an aggregated value of
  • Fig. 1 is also illustrated that the user's 3 own context as well as his/hers view of the other users contexts can be visually represented on an awareness area, typically a display 9', e.g. at a personal mobile device 9. Results of events and notifications may also be represented on the same mobile device.
  • Another way of sharing contexts could be o to have parameters connected or provided to heat/audio or tactile actuators that the user can sense. An example can include that when the body temperature of a person's child reaches a certain threshold the wristwatch of the person starts to vibrate.
  • the awareness area can also make the user aware of the contexts of persons that the user has defined as belonging to various groups, e.g. family members.
  • the awareness area comprises a s plurality of views selectable on a user terminal, e.g. a mobile telephone 9.
  • the current context of a user 3 is submitted to the rule and context manager 5, which can use these data to control the information for presentation on the user awareness area.
  • the data can also affect the types of modes of communication that the user can use in the current context. For example, in the meeting case mentioned above, the data may instruct the rule engine 6 not to allow any oral communication with the user.
  • Fig. 3 the basic functions of the rule and context manager 5 are illustrated and in 5 particular the interaction between a context manager unit 11 and the rule engine 6.
  • sensors associated with two users A and B provide context information to the context manager 11.
  • Contexts compiled from the users A and B are stored in a context database 13, each user A, B having a personal context area 13 A, 13B within the database.
  • the compilation of context information is controlled by a context 0 control unit 15 that is part of the rule engine 6.
  • the context control unit can request the context manager 11 to ask a specified person, device or sensor for the value of a certain parameter.
  • a context distributor 16, also controlled by or part of the rule engine 6, processes the contexts of the users, i.e. the contents of the database 13, to form "shared" context 5 information stored in a shared context information database 17 that contains personal areas 17A, 17B and is further distributed for presentation on awareness areas of other users than that user which "owns" the considered context information, such as at the displays of the mobile terminals of the users B and A, respectively.
  • the context distributor 17 further includes functionality for pushing shared parameters to the areas 21 A, 21B for personal rules which have indicated a need for these parameters. Referring to Fig. 4, the parameter P3 is an example thereof.
  • a separate part 21 of the rule engine 6 implements the personal rules so that the personal rules 21 A belonging to user A can use the unprocessed context 13 A of user A and the context information, i.e. the processed
  • the whole or parts of the rule engine 6 and the context manager 11 can be decentralised or distributed as indicated above, and e.g. the personal part of the rule engine 6 for user A and/or B may be distributed.
  • the personal rules associated with user A may be implemented in a mobile device 9 belonging to user A.
  • the context of a first member of a group may be in conflict with the context of a second member of the group, e.g. in relation to the communication media that are allowed.
  • a first group member may be driving a car and then a message for a second party can only be created as a verbal message.
  • the message may be rerouted for transcoding from an oral format to a text format by the change of an associated parameter value, the value changed by the rule engine 6.
  • an oral message created at that terminal may be rerouted to an entity or device that performs transcoding to text and further delivery to the intended recipient.
  • Fig. 2 the main different steps performed by the rule and context unit 5 are illustrated.
  • the parameters are collected, as shown in a first block 25.
  • the parameters collected can be classified in different categories depending on the way in which they are perceived within the system.
  • a parameter can belong to one or many of the following categories: 5 - Periodically polled parameters, such as the quantity obtained from a temperature sensor. This is useful for parameters that can be read without disturbing users or demanding too many resources within the system or has some other cost that makes it inconvenient to perform excessive readings.
  • Some sensors/parameters only report to the rule and context 0 unit 5 when a change has occurred. Sensors could be configured to only report changes greater then a predetermined threshold. Typically a GPS parameter would only change when the object has moved a predetermined distance or to a specific place.
  • a parameter which is hard to automatically measure or over which a user wants a total control may be manually set by the user owning the 5 parameter.
  • Rules are usually evaluated on demand, see the block 27, e.g. when a change occurs in the network that may affect a rule or typically when a parameter gets a new value. Rules that are prevented from being fulfilled due to an ambiguous parameter value may, if the owner of the parameter has allowed it, ask the owner or any other named person or specified device for the current value of parameter to determine whether the rule can be fulfilled and hence the associated action can be carried out. This may be the case of manually set parameters. Parameters can generally be associated with a time 5 stamp and an expiration time period so that they are undefined after the expiration period.
  • Events are associated with changed parameter values, i.e. changed contexts. Events are related to rules in that fulfilled rules may change parameter values and, thus, create new events. Events, i.e. changed parameter values, may trigger actions in devices that use parameters for device control, e.g. locking a door. Events can also be defined to set 0 the value of another parameter, i.e. to create a new event. This is the way in which a rule can aggregate the value of one or more parameters to form a new virtual parameter.
  • Each record contains the data of one parameter and can e.g. have the following fields:
  • a step 55 is executed in which it is determined whether an action should be started for a change of this parameter X and then executing the action if there is such an action.
  • a next step 57 the value of the parameter is pushed to the rule engine parts of other users which require this parameter according to the specification for this parameter.
  • a loop is started for each rule involving the parameter.
  • step 65 it is determined in a step 65 whether the rule A is resolvable, i.e. whether the result of the rule can be decided, and whether the result of the rule is true. If it cannot be resolved or the result is not true the next rule is processed and if there is no more rule the loop is ended in a step ⁇ o 67, and a new event is awaited in the start step 51.
  • a step 69 is executed in which a target or virtual parameter T is set, e.g. by some calculation, if this has been defined for the rule, compare parameter P4 of Fig. 4.
  • the setting or changing of the value of the virtual is parameter can T generate a new event, as indicated in the next block 71.
  • the next rule is processed if there is one and if there is no more rule the loop is ended in a step 67, and a new event is awaited in the start step 51.
  • step 75 is executed in which a loop is started for each polled parameter Z.
  • a step 77 the parameter is polled for its value. Thereafter, in a step 79 it is decided whether the value of the parameter Z has changed from its previous value. If the value has not changed, the next parameter is polled in the case where there is one and if it no more such parameter, the loop is ended in a step 81 and a new event is awaited in the start step 51. If it was decided in the step 79 that the value of the parameter has
  • a rule has the following general properties: First, it is possible to evaluate the rule, i.e. to find whether a composite condition a true, and second, the rule is capable of making algebraic calculations. The rule based calculation is generally performed if the
  • a rule is evaluated to have the value TRUE.
  • a rule can have the general format: 1. A condition starting the evaluation of the rule, e.g. "parameter No. 1 changing value” or "parameter No. T equal to 10.30". In the latter example parameter No. T is assumed to be the current time.
  • the function can have the values TRUE and FALSE.
  • a simple example of a logical function is "parameter No. 1 AND parameter No. 2" in which it is assumed that the parameters Nos. 1 and 2 are logical parameters and which has the meaning that an action will be taken in the case where the two parameters both are true.
  • the actions are generally defined by a file that is to be executed in a predetermined one of the devices of the system.
  • the file can include algebraic or logical operations on parameter values, setting or changing the same or other parameter values and can when executed generate an electronic message.
  • rules which govern the processing of parameter values whether they are to be made available to other users. They can have the following general format for each other user to which the parameter value or some other value derived therefrom should be presented:
  • the network as described herein allows the users within a defined group to automatically share their contexts with each other as a supplement to existing forms of communication - e.g. telephony and messaging.
  • the users can combine information about their contexts with actions such as notification, messaging, and/or actions that are performed to a user's environment, e.g. devices, objects.
  • the network as described herein provides the users within a group with automatic information about their contexts without requiring other users to request such information. It allows each user to establish her/his own parameters and to flexibly create new parameters that can also trigger actions towards objects within their environment or towards other users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Computer Hardware Design (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

Dans la présente invention, lorsque des informations, telles que des messages, sont distribuées à une pluralité d'utilisateurs (3) et à des dispositifs (9) associés à des utilisateurs, des contextes personnels sont formés pour les utilisateurs. Le contexte personnel d'un utilisateur est évalué et adapté dans un gestionnaire de règles et de contextes pour être distribué de façon sélective à d'autres utilisateurs. Le contexte personnel adapté peut être présenté sur les écrans des dispositifs associés aux autres utilisateurs. Le gestionnaire central (5) comprend un moteur de règles permettant d'appliquer des règles personnelles pour adapter le contexte personnel et appliquer des règles aux contextes personnels pour régler des paramètres. La modification de la valeur d'un paramètre permet de déclencher une action externe servant à générer et à transmettre un message électronique, par exemple. La présente invention permet de distribuer des informations de contexte selon de multiples possibilités et de déclencher des actions à l'aide de règles évaluant les contextes d'une pluralité d'utilisateurs.
PCT/SE2002/000925 2001-05-15 2002-05-15 Messagerie interactive Ceased WO2002093445A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE0101708A SE0101708D0 (sv) 2001-05-15 2001-05-15 Interactive messaging
SE0101708-6 2001-05-15

Publications (1)

Publication Number Publication Date
WO2002093445A1 true WO2002093445A1 (fr) 2002-11-21

Family

ID=20284118

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2002/000925 Ceased WO2002093445A1 (fr) 2001-05-15 2002-05-15 Messagerie interactive

Country Status (2)

Country Link
SE (1) SE0101708D0 (fr)
WO (1) WO2002093445A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7689562B2 (en) 2006-02-27 2010-03-30 Sap Ag Access control system, a rule engine adaptor, a rule-based enforcement platform and a method for performing access control
CN115499395A (zh) * 2018-09-29 2022-12-20 创新先进技术有限公司 社交方法、装置及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5440620A (en) * 1992-08-28 1995-08-08 At&T Corp. Telecommunications system subscriber profile updating
WO1999033293A1 (fr) * 1997-12-23 1999-07-01 Global Mobility Systems, Inc. Systeme et procede de commande d'informations personnelles et de transmission d'informations a destination et en provenance d'un dispositif de telecommunication
WO2000018166A1 (fr) * 1998-09-21 2000-03-30 Telefonaktiebolaget Lm Ericsson Traitement d'appels personnalise dans un systeme de communication
WO2000022800A1 (fr) * 1998-10-15 2000-04-20 At Mobile.Com Corporation Systeme et procede permettant de gerer des listes d'appels de numeros telephoniques personnels ainsi que les capacites d'appel
US6311055B1 (en) * 1997-10-02 2001-10-30 Ericsson Inc System and method for providing restrictions on mobile-originated calls

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5440620A (en) * 1992-08-28 1995-08-08 At&T Corp. Telecommunications system subscriber profile updating
US6311055B1 (en) * 1997-10-02 2001-10-30 Ericsson Inc System and method for providing restrictions on mobile-originated calls
WO1999033293A1 (fr) * 1997-12-23 1999-07-01 Global Mobility Systems, Inc. Systeme et procede de commande d'informations personnelles et de transmission d'informations a destination et en provenance d'un dispositif de telecommunication
WO2000018166A1 (fr) * 1998-09-21 2000-03-30 Telefonaktiebolaget Lm Ericsson Traitement d'appels personnalise dans un systeme de communication
WO2000022800A1 (fr) * 1998-10-15 2000-04-20 At Mobile.Com Corporation Systeme et procede permettant de gerer des listes d'appels de numeros telephoniques personnels ainsi que les capacites d'appel

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7689562B2 (en) 2006-02-27 2010-03-30 Sap Ag Access control system, a rule engine adaptor, a rule-based enforcement platform and a method for performing access control
CN115499395A (zh) * 2018-09-29 2022-12-20 创新先进技术有限公司 社交方法、装置及设备
CN115499395B (zh) * 2018-09-29 2024-01-16 创新先进技术有限公司 社交方法、装置及设备

Also Published As

Publication number Publication date
SE0101708D0 (sv) 2001-05-15

Similar Documents

Publication Publication Date Title
US7225229B1 (en) Automated pushing of computer user's context data to clients
US7444594B2 (en) Mediating conflicts in computer user's context data
US7231439B1 (en) Dynamically swapping modules for determining a computer user's context
US8677248B2 (en) Requesting computer user's context data
US6812937B1 (en) Supplying enhanced computer user's context data
US7062715B2 (en) Supplying notifications related to supply and consumption of user context data
Tsai et al. Who's viewed you? The impact of feedback in a mobile location-sharing application
US9372555B2 (en) Managing interactions between computer users' context models
US8181113B2 (en) Mediating conflicts in computer users context data
US7464153B1 (en) Generating and supplying user context data
US7080322B2 (en) Thematic response to a computer user's context, such as by a wearable personal computer
US7107539B2 (en) Thematic response to a computer user's context, such as by a wearable personal computer
US7055101B2 (en) Thematic response to a computer user's context, such as by a wearable personal computer
US20100299319A1 (en) Method, apparatus, and architecture for automated interaction between subscribers and entities
US20060004680A1 (en) Contextual responses based on automated learning techniques
US8677254B2 (en) Discerning and displaying relationships between avatars
JP2015531909A (ja) 情報ターゲティングシステムおよび方法
JP2011175674A (ja) 目標アクティビティに関する進んだ情報収集のための、システム、方法、及びマニュファクチャーのアーティクル
EP2480965A2 (fr) Modèle informatique d'événements multi-niveau
US7660872B2 (en) Managing location information for a group of users
WO2002093445A1 (fr) Messagerie interactive
de Almeida et al. Using ontologies in context-aware applications
JP2021033955A (ja) Ｓｎｓシステム、ｓｎｓサーバ、情報処理方法、ｓｎｓ提供方法、プログラム
Jones et al. Flexible collaborative support: An architecture and application
Kollikowski The taxonomy of local services: a systematic literature review

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP