WO2002080512A1 - Procede d'administration de demandes de contacts, utilisant des recommandations, par des abonnes agrees demandant un contact - Google Patents

Procede d'administration de demandes de contacts, utilisant des recommandations, par des abonnes agrees demandant un contact Download PDF

Info

Publication number
WO2002080512A1
WO2002080512A1 PCT/FI2002/000274 FI0200274W WO02080512A1 WO 2002080512 A1 WO2002080512 A1 WO 2002080512A1 FI 0200274 W FI0200274 W FI 0200274W WO 02080512 A1 WO02080512 A1 WO 02080512A1
Authority
WO
WIPO (PCT)
Prior art keywords
crp
vip
contact
shield
recommendation
Prior art date
Application number
PCT/FI2002/000274
Other languages
English (en)
Inventor
Arto Juhola
Original Assignee
Elisa Communications Oyj
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 Elisa Communications Oyj filed Critical Elisa Communications Oyj
Publication of WO2002080512A1 publication Critical patent/WO2002080512A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • H04L51/21—Monitoring or handling of messages
    • H04L51/212—Monitoring or handling of messages using filtering or selective blocking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it

Definitions

  • a method for controlling contact requests is related in general to communications and more particularly to address handling in a way specified in the preamble of claim 1.
  • Telephone services make use of unlisted phone numbers which can be changed e.g. at three-month intervals in order to screen out harassers and other unwanted persons.
  • a drawback of this method is, however, that wanted potential contacts will be thwarted in cases where the contact-requesting party (CRP later on) is not known from before and uninformed of the contact details such as e.g. the address and/or phone number.
  • CCP contact-requesting party
  • all wanted persons have to update their address books unnecessarily often, making communication laborious and yet uncertain.
  • An object of the invention is to eliminate the problems of the prior art in restricting the passage of contact requests and/or messages coming via communications networks to wanted persons or similar parties only or direct certain contact requests to appropriate targets such as secretaries, for example.
  • the objects of the invention are achieved by managing lists compiled through the co-operation of multiple persons and/or entities, said lists including names and/or addresses of contact-requesting parties, where a name may refer, in addition to a person, also to a SW or other entity and/or process.
  • a method according to the invention is characterized in that communication between at least two parties, intended to take place in a communications network based on electromagnetic phenomena and utilizing digital technology, is controlled in a manner specified in the characterizing part of claim 1.
  • a system according to the invention is characterized in that which is specified in the characterizing part of claim 23.
  • a method according to an embodiment of the invention can be used to prevent these CRPs from contacting the VIP.
  • the VIP is thus shielded against trivial contact requests that would only result in a waste of time or otherwise negatively affect the VIP's interests.
  • Such a shield is accomplished by managing, jointly by a plurality of so-called entities, a so- called list, which may be part of a database, comprising so-called contact-requesting parties (CRP).
  • CRP contact-requesting parties
  • the CRPs are categorized.
  • the classes used in the categorization of CRPs are hereinafter called CRP types.
  • each CRP type there is associated a number of attributes the values of which can be defined for CRP instances belonging to a given CRP type.
  • the CRP types describe the data stored on the list for a CRP of that type.
  • a CRP instance is a collection of attribute values stored on the list for an individual member of a CRP type.
  • the attribute values of instances of CRP types (meaning, if not otherwise stated, records of a catalog in a list) specify e.g. the identity, ID, of the CRP and/or a network address which may serve as the list index, the CRP type on which the CRP instance is based, the identity, ID, of the AGENT that recommended the CRP and/or a network address thereof, the ID of the AGENT that recommended the AGENT in question, and other factors to be considered in forming the accepting or rejecting decision for the contact request.
  • Such other factors may include, for example, allowed and/or disallowed contacting methods, allowed and/or disallowed contacting times, allowed and/or disallowed physical locations of the CRP, and allowed and/or disallowed network locations as far as they can be determined, allowed number of contact requests and/or message per unit time, the authentication method required, e.g. in accordance with the time of day (say, weak during the day, stronger at night, call-back).
  • Some necessary background information of a contact request or message can be determined direct from the contact request or message. It is also possible to use indirect methods and/or combine information obtained from different sources such as network and other databases or from the calendar or clock of the shield system described, and other such sources which are obvious to a person skilled in the art.
  • Data gathered from the contact request are compared to attribute values stored for the CRP instance, and the contact request directed to the VIP is either accepted or rejected.
  • the shield system described can include in the message itself some related information without disturbing the end user's applications.
  • Such information may be e.g. message properties (if not already included in the message), filtering rules, as well as information about the maker of the CRP instance (AGENT) and recommender chain for the AGENT in question.
  • An AGENT may be authorized to recommend another CRP as AGENT, who in turn may receive similar authorization etc.
  • a contact request/message cannot be altered without disturbing end user applications, it is just delivered to the VIP or rejected.
  • the VIP can get message specific information from the shield system by means of a suitable auxiliary application; e.g. when a normal phone call arrives, the VIP can ask for the data of the last available phone contact request on his/her workstation. There may be one or more associated attributes.
  • Properties of a shield according to an embodiment of the invention only allow certain CRPs to get in contact with the VIP. Thus all parties not allowed access to the VIP through the shield are considered potential HARASSERs.
  • a recommender which is a party approved by the VIP, which recommender has the right to modify the shield of the VIP so that the CRP can pass through the shield and communicate with the VIP.
  • Such a party, which has the right to modify the shield is called an AGENT.
  • a recommender sends to a so-called entity, which maintains the shield, a message concerning the modification of the properties of the shield so that the CRP, who is being recommended, can get through to the VIP when requesting a contact with the VIP.
  • An AGENT'S message containing a recommendation is called a letter of recommendation regardless of its physical nature.
  • a letter of recommendation can be used so as to create in a catalog maintained for keeping up a shield, a CRP instance representing a desired CRP type and to set values for its attributes as defined in the CRP type. Furthermore, a letter of recommendation can be used so as to change the attribute values of an existing CRP instance within the scope of the AGENT's authorization. In that case, the attribute representing the rights required for changing the shield is associated with the CRP.
  • a CRP which is neither a HARAS SER nor an AGENT is called a PAL.
  • a PAL has the right to get in contact with the VIP but no right to change the shield properties and, therefore, no right to create or remove CRP instances in a catalog nor modify their attribute values.
  • a record can be kept of at least AGENTs and PALs the contact information of whom are included in a so-called list which is managed in order to maintain the VIP shield.
  • information defined in the CRP type is entered on a list/catalog which is maintained in order to keep up the shield.
  • the definition of an individual piece of information in the CRP type is called an attribute.
  • An attribute is usually not given any default value in the CRP type unless the value is a constant.
  • the CRP type definitions apply to every CRP of that type, and information according to the appropriate CRP type attributes shall be saved for each CRP. These data are stored in a catalog of the list, and they are called the attribute values of CRP instances. Which attributes are used for which CRP type is determined on the basis of the needs of the VIP using the list as well as the software utilizing the attributes.
  • the VIP list management can be distributed among a plurality of AGENTs.
  • An AGENT may also delegate the management rights.
  • the AGENT type differs from the PAL/HARAS SER types in that a PAL/HARAS SER requires a contact with the VIP whereas an AGENT primarily communicates with the shield.
  • One and the same person or entity may function in the roles of multiple CRP types, even at the same time, unless it should result in an irreconcilable conflict.
  • a CRP and/or the message thereof may also be directed to another party specified in the VIP shield, say, to an entity serving as a so-called secretary.
  • the invention has embodiments for seeking a wanted party specified by certain attributes, e.g. a VIP seeking a second VIP by contacting a third VIP. Then it is at the discretion of the first VIP whether he/she transfers the management and/or attribute associations of his/her lists in conjunction with the inquiry. These rights can be conveyed using a certain message and appropriate data transfer entities.
  • certain attributes e.g. a VIP seeking a second VIP by contacting a third VIP.
  • Fig. 1 shows an example of the method according to an embodiment of the invention
  • Fig. 2 shows an exemplary diagram of the association right level hierarchy
  • Fig. 3 shows a classification of entities
  • Fig. 4 shows a letter of recommendation
  • Fig. 5 shows a message
  • Fig. 6 shows an example of the transfer of association right
  • Fig. 7 shows an example of message space
  • Fig. 8 shows an exemplary diagram of a list.
  • a VIP is a so-called entity which/who, as a target of contact requests, utilizes a shield according to an embodiment of the invention maintained by means of a so- called list which is managed by a plurality of so-called AGENTs and/or so-called entities.
  • the list contains entries of CRPs and/or attributes associated with them.
  • an entity refers to a person, such as a secretary or some other assistant, for example, and, as an extension thereto, also a software algorithm.
  • a typical entity could be e.g. a network daemon.
  • a classification of entities is illustrated in Fig. 3.
  • a CRP means, in addition to what was mentioned above, also any party or entity which can send a contact request to the VIP or the shield of the VIP.
  • CRPs are advantageously categorized into three CRP types according to VIP interests: PAL, HARAS SER, and AGENT.
  • a PAL is a desired CRP who does not take part in the management of the VIP shield.
  • a CRP is meant the CRP type of which is PAL.
  • An AGENT is a CRP which has got a right to participate in the management of the properties of the shield and the CRP type of which is AGENT. All CRPs that have no right to get in contact with the VIP are, by default, potential HARASSERs, unwanted CRPs.
  • a HARASSER is a CRP who is not a PAL nor an AGENT (nor the VIP himself).
  • the VIP or an entity authorized by the VIP has the right to add to a list used in the management of the shield also entities which have not yet made a contact request but which are likely and/or expected to do so. In that case the party making the list entry is authorized by the VIP to associate attributes with the CRP. Such a procedure may be advantageous e.g. when updating a list containing information about certain acquaintances of a human VIP.
  • An AGENT is a CRP which/who has a right to send an acceptable "letter of recommendation" to an entity managing the VIP shield.
  • the letter of recommendation contains the necessary information for making an entry in order to change the properties of the shield so that an entry is made on a list used for the management of the shield for changing a potential HARASSER into a PAL, the net effect being that the AGENT has recommended this CRP to contact the VIP.
  • AGENTs are included on a list to keep up the shield. Also the rights representing the authorizations of the AGENTs, as indicated by so-called attributes, are included on a list.
  • PALs and/or their attributes are entered on a list which is managed by entities.
  • a list means a collection of contact data relating to the VIP shield or the like, such as a catalog, also a database, containing information relating to the access to the VIP arranged in an order which is advantageous from the point of view of data retrieval. Most advantageously the lists make up databases so that it is possible to view attributes indicating CRP properties, for example. Most advantageously lists according to the invention are hierarchic and managed by a plurality of entities. A list may also be distributed, e.g. in certain parts of a data network. A database which, applied in some manner, can be used as a list within the scope of the invention, is considered a list.
  • a VIP can be drawn up a list of CRPs according to type, thus producing a PAL list and an AGENT list. If necessary, a list of HARASSERs may also be drawn up (so- called HARASSER list), specifying parties that have requested contact or are otherwise known to be HARASSERs. In accordance with an embodiment of the invention, these lists may also contain references to other lists of the VIP and/or other lists which contain direct and/or indirect information about PALs, AGENTs and so-called attributes associated therewith.
  • Attributes are descriptive qualifiers that can be used to express relevant properties of CRPs.
  • the attributes make up a means of classifying objects related to certain messages into categories which are significant from the point of view of the VIP's interests, making it easier to manage the lists and/or databases of a shield managed by a plurality of entities.
  • the attributes may be associated in a restrictive and/or permissive manner with the rights of the message, its sender and/or portion of the message, also the propagation rights of the message, as well as to other attributes and/or groups formed by them.
  • attributes are CRP contact information, CRP code and CRP type.
  • attributes can be used to indicate the recommender, i.e. via whom the CRP is contacting, whether the matter is personal, business, a warning, work offer or any other piece of information belonging to a classification defined by the user and/or user organization, a combination of the above or any other piece of information relating to the VIP or CRP.
  • the number of contact requests, number or responses and/or the occurrence of a certain other attribute in the communication may also function as an attribute in a manner determined by the preferences of the user and/or operator.
  • a title or corresponding character combination in a contact request is also considered an attribute.
  • an arbitrarily defined portion of a contact request and/or letter of recommendation may be defined as an attribute.
  • a VIP may create new attributes in addition to existing ones, according to need, in order to indicate and/or classify PALs and/or their access conditions and/or message properties.
  • ATTRI lists lists of attributes
  • corresponding CRPs whereby it will be easier to direct an unknown CRP to an appropriate address.
  • the attributes may form a hierarchy so that attributes will become more specific, moving from a certain general topic and/or property towards a more clearly defined property determined by the attribute, when observing the hierarchy of said attributes in depth.
  • these ATTRI lists are obtained by applying in an appropriate manner the properties of a database, for example.
  • a message and/or the CRP associated therewith is classified, and the contact request is directed e.g. to a response entity which automatically generates a polite response.
  • Automatic response generation is advantageously used for a CRP the communication with which requires a certain standard communications format.
  • the address information and/or associated attributes are in plain language, and in another embodiment of the invention, they are in code, and in yet another embodiment, they are encrypted in a manner determined by the VIP.
  • the coding is most advantageously realized by adding to the data a character sequence where the characters and their quantity can be determined by the user.
  • the relation between the character sequence and the encoded data is readable to any party handling said data. In encryption, this relation is concealed so that only certain parties handling the data can receive the data in an intelligible form.
  • An advantage of the encryption approach is a certain kind of transparency with regard to attribute-searching entities so that shortcuts can be arranged for the immediate circle of the VIP or other parties, including authorities, considered eligible by the VIP.
  • the association of attributes involves a so-called association right, which refers to an authorization by a first person of a second person to change the shield of the first person in such a manner that a third person can get through the shield to the first person.
  • the association right may also include the right to associate certain attributes with other attributes, a message, an entity conveying the latter and/or the sender of the message, and to applicable parts of the shield and/or the database used to maintain it.
  • the association right may have hier- archie levels in relation to the nature of the attributes themselves, as described in conjunction with Fig. 2.
  • the association right may also belong to an entity other than a person.
  • preferred embodiments of the invention include user authentication in order to verify the true identity of the CRP.
  • the VIP may be authenticated for the CRP.
  • identity means any such information, defined by the user as reliable, which is uniquely, as defined by the security level, associated with a certain VIP and/or CRP.
  • authentication is carried out based on the principle of public and secret keys.
  • the authentication of the VIP may be based on the IETF PGP method.
  • user authentication is based on the Personal Telecommunications Number (PTN) service, or the Universal Personal Telecommunications (UPT) service which is an extension to the former. It is also possible to use GSM SIM-based authentication.
  • PTN/UPT authentication is a certain independence of the terminal used, so that for a mobile VIP the PTN/UPT authentication is particularly advantageous in the method according to an embodiment of the invention.
  • An example of simple authentication is call-back or similar contact made to an address or such given by the CRP.
  • FIG. 1 illustrates the operating principle of a method according to an embodiment of the invention.
  • a VIP 101 is an entity protected from senders 107 of junk mail behind a shield 102 which is a sort of access list managed by a plurality of entities.
  • the shield 102 comprises a portion which includes, in the form of database 103, for example, the desired contact-requesting parties (CRP) and, at the same time, the undesired ones.
  • the shield 102 includes a database part 104 specifying, based on certain lists, for instance, the parties entitled to change the properties of the shield 102, e.g. as regards penetration of a message.
  • the VIP 101 gives a CRP 105, which is an entity, the right to act as an agent for the VIP 101.
  • the agent 105 perceives a CRP 106 whom it knows to be a desired CRP from the point of view of the VIP 101, it sends a message 115 to the CRP 106, urging the latter to contact the VIP 101.
  • the agent 105 sends 113 a 'letter of recommendation' on the basis of which a channel is opened in the shield 102, through which the CRP 106 can contact 110, 111 the VIP 101 independent of the agent 105.
  • an entry can be made in the shield and/or a database used in its management, on the basis of which the CRP 106 is able to penetrate the shield.
  • This entry can be made by some specialized entity and/or a multifunction entity.
  • the shield 102 and/or an entity managing the shield Based on a contact request 113 and/or associated factors the shield 102 and/or an entity managing the shield identifies the agent 105 as the agent 105 and also recognizes that it has the right to change, by means of the letter of recommendation, the rights in the database 104 so that the CRP 106 can get through 1 11 and in contact with the VIP 101.
  • the right may also be limited to a certain time period or it may be disabled for a certain time period.
  • the right may also be restricted according to geographical location, connection means and/or contacting address, or a combination of the above, even in a case where the moment of sending of the message or a given location may be assumed to be of special significance, as regards the contents of the message, to the VIP and/or an object and/or entity operating under the VIP.
  • the entity 105 which acts as an AGENT for the VIP 101, and the recommended CRP 106 are horizontal acquaintances of the VIP 101.
  • the AGENT 105 also belongs to a group in depth, which group also includes the recommended CRP 106.
  • these AGENTs belong to a group in depth as far as the transfer or rights is concerned.
  • at least some of the CRPs serving as AGENTs are in contact with the VIP 101 so that these make up a horizontal group of acquaintances of the VIP 101.
  • Fig. 2 shows an example of categorization of association rights according to their probable numbers of users. Referring to the rectangles drawn in Fig. 2, the number of probable users is in proportion to the area of the rectangle. However, the invention is not limited to the numbers according to the example depicted.
  • the highest association right 201 is unlimited. Innermost, or highest, in the hierarchy are those few selected people who have an unlimited association right 201. Typically in some embodiments of the invention an unlimited association right belongs to the VIP himself, his personal secretary or an equivalent entity.
  • the entities that have an association right 202 which is in some way limited, say certain AGENTs. The limitation may also apply to altering the AGENT rights of the AGENT itself, for example.
  • the party using the highest association right has the right to recommend any CRP to contact the VIP and also to give, at his discretion, the CRP in question the same or narrower rights than he himself has.
  • the highest association right includes the right to associate attributes with an object and/or thing which is essential from the point of view of the delivery of the message of the CRP and which exists in a communications system with preconditions relating to the completion of communication; i.e. a letter of recommendation, message, address, part of any of the above, its geographical location, contents and/or manner of sending.
  • the unlimited association right includes the right to change association rights, advantageously not, however, the association rights of the VIP from whom said right was obtained either directly or indirectly.
  • a limited association right 202 differs from the unlimited one in that there the authorization is limited in some way, say, to +8 hierarchy levels forward in depth.
  • the limitation may also concern the time, place, size, and duration of the transmission and/or reception of the message, as well as the sender and/or receiver of the message, and the right to change the association right.
  • the limitation may also relate to the attachment of attributes to the message and/or its sender. In some embodiments of the invention, limitations are combinations of the above.
  • the narrowest association right 203 is one which does not have other rights than that of forwarding the message, without attaching properties and/or attributes to the message or its sender.
  • Fig. 2 shows by way of example a three-level division of rights. However, the invention is not restricted to any certain division of association rights, but coarser and finer divisions are possible.
  • the association right it may be advantageous to restrict the association right. It may also be advantageous to restrict the passage of a message even if the sender of the message were a PAL and/or an AGENT.
  • the nature of a limitation concerning the association right and/or passage of a message is bound to time in an embodiment of the invention. In an example, the limitation applies to a person of a horizontal hierarchy level on the first week day of the month at 20:00:01 to 22:30:25, but to another exemplary person until the end of year 2000. In another embodiment of the invention the limitation is bound to the geographical location, service provider, or some other factor indicating location, electrical and/or physical location, e.g. a hierarchy level from the sender onwards.
  • the basis of the limitation concerning the association right and/or message penetration is bound to an appearance of an attribute associated with the contents of the message.
  • the contents of a subject field which is in English, are examined for four-letter words starting with the letter f, and the sender of the message is denied his existing association right, either temporarily, permanently or for that particular message, if such a word is found and it further contains the letters c and k, for example.
  • the right of the person to change association rights may also be altered.
  • Fig. 3 illustrates a hierarchy which classifies entities related to embodiments of the invention, which entities belong to the scope of the entity concept either as CRPs, VIPs, secretaries, and/or some other parties.
  • an entity 320 may be a person 321, group 330, and/or an algorithm 341, such as e.g. a daemon operating in some part of a data network.
  • a device 432 in a data network may also be an entity.
  • a person 321 may be a natural person 322, such as an individual human being, or an artificial, i.e. legal, person 323, such as an operator, organization, company or such.
  • a natural person may be e.g. a secretary 324 or a VIP 325 in the narrow meaning of the term.
  • a group 330 may be a homogeneous group 331 or heterogeneous group 332.
  • the members of a homogeneous group 331 belong substantially to the same species.
  • a heterogeneous group 332 includes at least one member which is of a substantially different species than at least one other member of the group.
  • a heterogeneous group 332 may comprise both natural 322 and legal 323 persons, algorithms 341 and other entities 320 and/or other groups 330 which have structures of their own.
  • the entities may serve as CRPs and VIPs and also as secretaries and/or agents to another entities. Functionally, an entity may be available to a VIP either directly or indirectly as well as by way of a right conveyed by another entity (say, VIP, AGENT).
  • entities can be classified on the basis of the function of the entity or on the basis of the object of the function of the entity.
  • the function of an entity may be limited to a certain narrow field of operation.
  • an entity may function e.g. in order to produce a message with a certain content and, moreover, so that different entities can produce their special messages according to target groups.
  • Another example in an embodiment of the invention is the use of an entity to detect an attribute of a certain kind in a message.
  • An entity may also be specialized in processing letters of recommendation, for example. Entities may also be specialized in controlling other entities and/or their association rights. Certain entities may specialize in generating messages relating to contact requests from CRPs.
  • the messages generated by an entity contain various responses which are substantially categorized into requests, announcements and invitations.
  • the responses are based on attributes and in another embodiment of the invention they are based on attribute hierarchy.
  • Tones of requests depend on the CRP attributes, varying from polite requests asking the CRP to attempt a contact later at a more convenient time to more pressing requests to stop harassment under a penalty of an appropriate sanction, such as reporting the harasser to the authorities, for example.
  • requests are also regarded as attributes.
  • Announcements are notices to the PALs of the VIP, concerning e.g. the availability of the VIP or related matters, such as contact information and/or changes therein. Announcements may also include other information deemed relevant by the VIP.
  • invitations are e.g. invitations to make contact, sent to another VIP when the latter is in a position of a CRP, or used when the VIP himself wants to contact some other VIP and/or AGENT.
  • Fig. 4 shows a structural diagram of a message, i.e. a letter of recommendation, for setting an attribute to be associated with a CRP, which attribute allows communication with the VIP through the shield 102.
  • the letter of recommendation advanta- geously comprises at least a field 401 which indicates the authentic sender of the message, field 402, which indicates the object of recommendation, and field 403, which indicates that the message is a letter of recommendation for opening the shield 102 for communication from the party, say CRP 106, indicated by field 402.
  • a message which is a letter of recommendation, advantageously further comprises a field 404, on the basis of which the entity processing the messages at the location of the shield 102 knows which actions should be directed to the shield 102 and or CRP 106 and the contact request 110 thereof, and/or in which form the contact request should be delivered 111 to the VIP 101.
  • Said actions may be indicated e.g. with special attributes which are checked by entities manag- ing the shield and/or the traffic through it.
  • An embodiment of the invention involves a special part attached to the letter of recommendation, containing information on attributes associated for changing the shield properties so that the CRP indicated in the message can get through the shield in order to communicate with the VIP.
  • Said CRP may be a certain named CRP with a certain address.
  • a letter of recommendation may also concern a group of named CRPs. It is also possible use certain attributes to define a group of unnamed CRPs where the group meets conditions defined by certain attributes so that the letter of recommendation applies anonymously to the members of said group. According to an embodiment of the invention, the letter of recommendation may also be used to recommend that the right of communication is canceled for a given CRP and/or restricted according to a temporal or geographical property and/or content-related property of the message.
  • Fig. 5 shows the structure of a message 500 according to an embodiment of the invention.
  • the message is constructed of several parts, fields (501, 502, 503, 504, 505, 506, 507).
  • the message comprises at least the address 501, subject 502, and the message body 504.
  • the message may contain a part indicating the route 503, especially in applications where contact is requested to a party that has an attribute defining a certain property.
  • the message may contain a field for the author 505 of the message, author's right of distributing the message 506 and/or a qualifier indicating the validity of the message 507, which qualifier may be bound to time, place and/or address or a combination thereof, as was described earlier. All fields need not be readable to those handling the message.
  • a message according to an embodiment of the invention includes a field which may contain certain information about a letter of recommendation and/or even a copy of it.
  • a field may also indicate whether the message is an ordinary message to a CRP or a letter of recommendation to an entity managing the shield 102.
  • an AGENT with appropriate authoriza- tion and/or an entity managing the shield of the VIP can get to the field containing information about the letter of recommendation.
  • Fig. 6 shows an example of the transfer of association rights in relation to the controlling of contact requests directed to a VIP.
  • a VIP 607 has given full rights to a CRP serving as a secretary S2 606, including the right to pass on rights to other parties at his/her/its discretion.
  • the secretary S2 606 has passed on a right to a secretary SI 605, who thus has an authorization from S2 606 to associate a CRP and/or a message of the CRP with CRP types HARASSER, AGENT and/or PAL and to make entries concerning the CRP on respective lists.
  • the VIP 607 has given an agent Ag3 603 the same right as the secretary S2 606 has, as regards contact requests coming through that agent.
  • the rights of the agent Ag3 603 are limited so that he/she/it can pass on his/her/its rights to an agent Ag2 602 operating one level in depth below him/her/it, and the association right alone to an agent Agl 601 operating two levels in depth below him/her/it.
  • This example is not to be understood so as to restrict the transfer of the association right relating to the invention.
  • Fig. 7 illustrates a message space defined by the mutual properties of the association right, CRP and the message.
  • the block depicted has got dimensions defined by mutually independent aspects, determining, on the basis of message contents 704b, message-sending CRP 704c and CRP types 704a, a classification of messages sent by a circle of acquaintances of a certain VIP and, at the same time, that of the circle of acquaintances itself, said acquaintances being enti- ties.
  • This example illustrating the classification of message space is presented using a 3-dimensional example. However, said classification can also be based on more dimensions which, in an analog manner, are mutually independent. Obvious additional dimensions in such embodiments of the invention are e.g. classifications based on the subject matter, time and/or place.
  • Fig. 8 shows an example of a list 800 according to an embodiment of the invention.
  • the list may have two parts, namely, a data part 801 comprising information relating to contact requests from CRPs, and a specifying part 802.
  • the list may also be a distributed list, in which case one part of the list is located separately from another part of the list. It is obvious to a person skilled in the art that there may be more fields as regards both quantity and contents.
  • the data part 801 tells of the contact- requesting parties at least their names and/or addresses associated with the names.
  • the CRP type preferably in the form of an attribute indicating the CRP type, of a CRP entered in the data part 801 of a list 800 according to an embodiment of the invention is also stored in the data part 801.
  • Fig. 8 shows a data part 801 including fields 807, 808, and 809 for, respectively, a HARAS SER-type CRP (H), AGENT-type CRP (Ag), and a PAL- type CRP (P).
  • H HARAS SER-type CRP
  • Ag AGENT-type CRP
  • P PAL- type CRP
  • the invention does not limit the quality or quantity of attributes associated with CRPs in the data part of the list. Nor does the invention impose any restriction as to whether the list is used as a blocking list or as a permissive list regarding contact requests.
  • the specifying part 802 of the list 800 includes the following fields indicating the CRP type: identifier 811 for a HARASSER H, identifier 813 for an AGENT Ag, and an identifier 814 for a PAL P.
  • the specifying part 802 includes fields 821, 823, 824 specifying, respectively, the actions directed to a HARASSER H, actions directed to and/or allowed for an AGENT Ag, and the actions directed to and/or allowed for a PAL.
  • the specifying part further includes fields 831, 833 and/or 834 for indicating, respectively, which part of the CRP's message contains the attribute defining the CRP as H, Ag, and/or P.
  • the specifying part includes fields 841, 843 and 844 specifying the attributes which define the CRP as H, Ag and/or P, respectively.
  • a portion of a list 800 can be attached to a message 500 to become part thereof. In that case it is highly advantageous to attach to the message the specifying part 802 of the list 800 and/or a certain field thereof, to help entities in handling the message along its way.
  • the invention relates to electronic communications, e.g. in various telephone, e-mail, GSM and/or WAP systems as well as via the Internet, where the contact-requesting party has got a data communication means for making a contact request and the target of the contact request has got a second data communication means for accepting or rejecting the contact request at his will.
  • magnetic, optic, fiber-optic and other communication systems in which a message is trans- ferred between at least two communication means according to a principle based on electromagnetic phenomena, are considered electronic systems.
  • the user interface in the communication means for utilizing the method may be text-based, visual and/or acoustic.
  • Text-based' is not confined solely to text produced using alphabetic characters, but a text-based text may have an altogether different form in which it is produced and/or processed.
  • text may be presented in a binary bit string in a digital network, for instance.
  • Text may also comprise text produced from speech with speech recognition means.
  • the text in that case has a presentable content and/or meaning which can be expressed in text.
  • attributes can also be associated with a spoken and/or another kind of acoustic message.
  • an advantageous embodiment of the invention can be used for automatic evaluation of telephone answering machine messages in order to filter out harassers.
  • ads and/or inappropriate portions thereof, which waste storage capacity can be filtered out in e-mail by means of pattern recognition means.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Signal Processing (AREA)
  • Strategic Management (AREA)
  • Operations Research (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Data Mining & Analysis (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Storage Device Security (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne l'administration de demandes de contact réalisée au moyen d'un écran dans un réseau de transfert de données dans le domaine des communications électroniques. L'utilisation d'attributs, associés à des demandes de contacts, permet de ranger les abonnés demandeurs de contacts en catégories de correspondants, d'agents et d'inconnus, ces derniers étant considérés comme harceleurs. Chaque abonné demandeur de contact doit posséder un garant autorisé par le propriétaire de l'écran de façon que, sur la base d'une lettre de recommandation provenant d'un garant, un accès soit réalisé sur au moins une liste de l'écran afin d'accepter la demande de contact provenant d'un abonné demandeur de contact.
PCT/FI2002/000274 2001-03-30 2002-03-28 Procede d'administration de demandes de contacts, utilisant des recommandations, par des abonnes agrees demandant un contact WO2002080512A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20010662 2001-03-30
FI20010662A FI111779B (fi) 2001-03-30 2001-03-30 Menetelmä yhteydenottojen hallitsemiseksi

Publications (1)

Publication Number Publication Date
WO2002080512A1 true WO2002080512A1 (fr) 2002-10-10

Family

ID=8560879

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2002/000274 WO2002080512A1 (fr) 2001-03-30 2002-03-28 Procede d'administration de demandes de contacts, utilisant des recommandations, par des abonnes agrees demandant un contact

Country Status (2)

Country Link
FI (1) FI111779B (fr)
WO (1) WO2002080512A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004077710A2 (fr) 2003-02-27 2004-09-10 Businger, Peter, A. Filtrage et classement de communications par ordre de priorite au moyen de communications anterieures
WO2011131228A1 (fr) * 2010-04-20 2011-10-27 Deutsche Telekom Ag Procédé et système pour la formation d'un réseau pour une communication par courrier électronique sans spam

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999004344A1 (fr) * 1997-07-18 1999-01-28 Net Exchange, Inc. Dispositif et procede permettant de mettre en oeuvre un courrier electronique centre autour du correspondant
WO2000054491A1 (fr) * 1999-03-09 2000-09-14 Don Novak Procede de filtrage et de localisation d'utilisateurs d'un reseau telephonique
GB2350747A (en) * 1999-04-09 2000-12-06 Ibm Hindering undesired transmission or receipt of electronic messages

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999004344A1 (fr) * 1997-07-18 1999-01-28 Net Exchange, Inc. Dispositif et procede permettant de mettre en oeuvre un courrier electronique centre autour du correspondant
WO2000054491A1 (fr) * 1999-03-09 2000-09-14 Don Novak Procede de filtrage et de localisation d'utilisateurs d'un reseau telephonique
GB2350747A (en) * 1999-04-09 2000-12-06 Ibm Hindering undesired transmission or receipt of electronic messages

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004077710A2 (fr) 2003-02-27 2004-09-10 Businger, Peter, A. Filtrage et classement de communications par ordre de priorite au moyen de communications anterieures
EP1606718A2 (fr) * 2003-02-27 2005-12-21 Businger, Peter A. Filtrage et classement de communications par ordre de priorite au moyen de communications anterieures
EP1606718A4 (fr) * 2003-02-27 2009-03-25 Businger Peter A Filtrage et classement de communications par ordre de priorite au moyen de communications anterieures
WO2011131228A1 (fr) * 2010-04-20 2011-10-27 Deutsche Telekom Ag Procédé et système pour la formation d'un réseau pour une communication par courrier électronique sans spam

Also Published As

Publication number Publication date
FI111779B (fi) 2003-09-15
FI20010662A (fi) 2002-10-01

Similar Documents

Publication Publication Date Title
US9798777B2 (en) Authorization and authentication based on an individual's social network
US7516182B2 (en) Practical techniques for reducing unsolicited electronic messages by identifying sender's addresses
US8234371B2 (en) Federated challenge credit system
Hall How to avoid unwanted email
US10354229B2 (en) Method and system for centralized contact management
US20080196092A1 (en) Method and system for reducing the proliferation of electronic messages
WO2004013796A1 (fr) Techniques pratiques pour diminuer des messages electroniques non sollicites par identification des adresses de l'expediteur
US11689660B2 (en) Methods and systems for detecting disinformation and blocking robotic calls
US8239921B2 (en) System and method of retrieving a service contact identifier
WO2002080512A1 (fr) Procede d'administration de demandes de contacts, utilisant des recommandations, par des abonnes agrees demandant un contact
US20080177846A1 (en) Method for Providing E-Mail Spam Rejection Employing User Controlled and Service Provider Controlled Access Lists
WO2007101149A2 (fr) Procédé destiné à entraîner le rejet de courrier électronique poubelle au moyen d'une liste d'accès contrôlée par l'utilisateur et le fournisseur d'accès

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