EP2789122B1 - Apparatus and method for inviting subscription to contact information - Google Patents

Apparatus and method for inviting subscription to contact information Download PDF

Info

Publication number
EP2789122B1
EP2789122B1 EP12855762.6A EP12855762A EP2789122B1 EP 2789122 B1 EP2789122 B1 EP 2789122B1 EP 12855762 A EP12855762 A EP 12855762A EP 2789122 B1 EP2789122 B1 EP 2789122B1
Authority
EP
European Patent Office
Prior art keywords
contact
request
client
cab
information
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.)
Active
Application number
EP12855762.6A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2789122A4 (en
EP2789122A1 (en
Inventor
Gyu-Bong Oh
Wuk Kim
Kyung-Tak Lee
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics 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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP2789122A1 publication Critical patent/EP2789122A1/en
Publication of EP2789122A4 publication Critical patent/EP2789122A4/en
Application granted granted Critical
Publication of EP2789122B1 publication Critical patent/EP2789122B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4594—Address books, i.e. directories containing contact information about correspondents
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present invention relates generally to a Converged Address Book (CAB) service, and more particularly, to an apparatus and a method for inviting subscription to contact information based on a converged address book service.
  • CAB Converged Address Book
  • a converged Address Book (CAB) service refers to an address book service based on a single network which stores address information usable by various terminals of a user, allows the information to be accessible by any device anytime and anywhere, and synchronizes the address information.
  • Such a converged address book service corresponds to a service provided for a purpose of improving a user experience for the address book and a function of the address book by storing a single network address book in a network.
  • Main functions of the converged address book service may include an address book synchronization, contact subscription, contact share, contact search, an external address book import from a non-CAB system and the like.
  • the contact subscription function is performed though a method in which an originating side invites a receiving side to subscribe to contact information of the originating side.
  • the method is implemented in a type of directly transmitting information on a subscription request subject to the receiving side and storing the information, and then transmitting a contact status information as illustrated in FIG. 1 .
  • a CAB client A 10 stores a subscription invitation request in a CAB server 20 in step 1
  • the CAB server 20 performs a series of operations in order to invite a user B of a CAB client B 60 to subscribe to contact information of the CAB client A 10.
  • all contact information of the CAB client A 10 is transferred to a CAB server 50 including the CAB client B 60 in step 4 regardless of whether the CAB client B 60 accepts the subscription or not.
  • the subscription is accepted in step 5
  • information on the subscription request subject that is, the entire received contact information and the subscription invitation are stored in step 6, and the user B of the CAB client B 60 recognizes that the user A invites the user B to subscribe to the contact information of the user A in step 7.
  • the subscription is not accepted in step 5
  • the received all contact information is not stored.
  • the Change Request "CAB 1.1 AD Contact invitation flows" dated 25 March 2010 by GYUBONG OH ET AL discloses a system in which a first user can invite a second user to subscribe to all his published contact information.
  • the system comprises two CAB clients, two CAB servers and two CAB XDMS (belonging respectively to the inviting user and to the invited user).
  • the two CAB servers communicate directly without using any proxy/relay or interminate device.
  • the contact information can be referenced by using a URI in order to avoid transmission of big amount of data within the signaling.
  • the document "Clarification on XDM Forward from CAB Server” dated 4 November 2011 by SAMSUNG ELECTRONICS discloses a system in which a first user can share a part of his contact information (by using a filter value) with a second user.
  • the system comprises a XDMC client (belonging to the first user) and two CAB XDMS (belonging respectively to the first user and to the invited user).
  • No CAB servers are disclosed in the system.
  • the contact information can be shared between the two CAB XDMS.
  • the contact information is referenced by using a URI in order to avoid transmission of big amount of data within the signaling.
  • the CAB client A 10 invites the CAB client B 60 to subscribe to contact information of the user A
  • entire contact information of the user A is transmitted in step 4. Accordingly, even though the user A desires to share only a part of contact information of the user A with the user B, there is no method capable of supporting it. Further, since actual contact information is transmitted to the CAB server 50 of the user B from the CAB server 20 of the user A regardless of whether the CAB client B 60 has accepted or rejected the subscription invitation, an efficiency is deteriorated in that a processing capacity is inefficiently used and an unnecessary storage space within the CAB server and the CAB XDMS is used.
  • the present invention provides an apparatus and a method for efficiently inviting the subscription to contact information.
  • the present invention provides an apparatus and a method for inviting the selective subscription to only a part of the contact information.
  • a method of inviting a subscription to contact information in a converged address book server includes receiving a subscription invitation request of particular contact information of a first client from the first client; and determining whether a condition for allowing the subscription to the particular contact information is included in the subscription invitation request, and transmitting a subscription request containing address information by which the condition and the particular contact information can be received to a second client when the condition is included.
  • a converged address book XML Document Management Server for inviting a subscription to contact information.
  • the converged address book XDMS includes a converged address book feature handler application usage for, when receiving a subscription invitation request of particular contact information of a first client from the first client, notifying a converged address book server of a contact share request containing a condition of allowing a subscription to the particular contact information; and a personal contact card application usage for storing particular contact information filtered by the condition by the converged address book server and forwarding a subscription request containing address information by which the particular contact information can be received to a second client.
  • the originating side can make a request for subscribing only a desired part of all contact information, and the receiving side can selectively receive only contact information of a desired client.
  • the receiving side can selectively receive only contact information of a desired client.
  • address information on contact information instead of actual contact information, it is possible to increase a transmission efficiency and also increase a storage efficiency of the CAB server and the CAB XDMS.
  • CAB Converged Address Book
  • OMA Open Mobile Alliance
  • the present invention proposes a method of efficiently performing a contact information subscription invitation. Accordingly, the present invention includes a process in which, when a first client makes a request for a subscription invitation of a particular contact information of the first client, a CAB server determines whether a condition allowing the subscription of the particular contact information is included and transmits a subscription request containing the condition and address information of the particular contact information to a second client.
  • a communication service at a high speed in a communication system supporting various types of communication services without a waste of resources, power, or memories.
  • a CAB service system includes a converged address book (hereinafter, referred to as a "CAB") client 100, a CAB server 110, a CAB XML document management server (hereinafter, referred to as a "CAB XDMS) 120, and a non-CAB system 130.
  • CAB converged address book
  • CAB server 110 a CAB server 110
  • CAB XDMS CAB XML document management server
  • the CAB client 100 communicates with the CAB server 110 on a terminal, and serves to authenticate a CAB user, synchronize Personal Contact Card (hereinafter, referred to as a "PCC") information and a converged address book stored in a network storage space, and transmit requirements of the CAB user, for example, a address subscription, address search, address share, interaction with a conventional address book, or management of user preference to the CAB server 110.
  • PCC Personal Contact Card
  • the CAB client 100 refers to a terminal of the user A, and serves to transmit a contact share request for recommending the user B to subscribe to contact information of the user A according to a request of the user A.
  • the contact share request contains a filter value as a condition for allowing a part of a contact view in personal information (PCC).
  • PCC personal information
  • the contact share request refers to a request for subscribing to a part of the contact information of the user A by the user B, and particularly, may contain a filter value to inform what the part of the contact information requested to be subscribed to is.
  • the contact information contains at least one of an address book, business card information, and personal information (PCC), and the contact view refers to, for example, making some information such as the personal information including as a name, a phone number, and an e-mail address be one group according to a need of the user. That is, the contact view means selectively extracting a part of all contact information to be shared and then forming the extracted information as a subset.
  • PCC personal information
  • the CAB server 110 is a main component of the network in the CAB structure, and serves to receive a request of the CAB user from the CAB client 100 and process the request. As main functions, the CAB server 110 serves to mutually authenticate the CAB client, store a CAB address, synchronize address information, receive an address information update from the address subscription function and reflect the address information update in the address book.
  • the CAB server 110 performs an operation for a network management of reflecting an address subscription/share/conversion, a user preference/policy and the like. Further, the CAB server 110 has an interworking function (IWF) of interworking with a conventional address book system or exposing an interface to an external enabler.
  • IWF interworking function
  • the CAB server 110 receives a contact information share request containing a filter value for allowing a selective subscription to the contact information from the CAB client 100. Then, the CAB server 110 generates address information by which particular contact information of the CAB client 100 selected according to the filter value is received. The request containing the newly generated address information is transferred to the CAB server (for example, XDMS 140) including the user B through the CAB server (for example, XDMS 130) including the user A. As described above, the CAB server 110 serves to newly generate the address information by which the contact information may be received, that is, URL information, instead of actual contact information in order to reduce transmission loads and to provide the URL information.
  • the CAB server 110 serves to newly generate the address information by which the contact information may be received, that is, URL information, instead of actual contact information in order to reduce transmission loads and to provide the URL information.
  • the CAB XDMS 120 for managing data of the user includes a CAB Address Book Application (CAB AB App) usage for storing the converged address book and a contact status for distinguishing between a conventional user and the CAB user, a CAB User Preference Application (CAB UP App) usage for storing user preference, a CAB Personal Contact Card Application (CAB PCC App) usage for storing personal contact card information, and a CAB Feature Handler Application (CAB FH App) usage for managing a CAB service request and response.
  • CAB AB App CAB Address Book Application
  • CAB UP App CAB User Preference Application
  • CAB PCC App CAB Personal Contact Card Application
  • CAB FH App CAB Feature Handler Application
  • the CAB XDMS 120 includes an XDMC for accessing various application usage functions, an SIP/IP core network for a message routing with entities of an external domain, a PUSH enabler for transferring a notification message of non-SIP terminals and the like.
  • a new schema for making a contact share request containing a standardized invitation message is defined within the CAB feature handler app. usage.
  • the CAB server 110 gives the receiver a right for the subscription to the personal profile information for the corresponding contact share request, transmits the corresponding contact share request to a receiving side, and processes the contact share request containing the corresponding personal profile information subscription invitation according to the user preference for the subscription request of another person set by the receiver, that is, acceptance, rejection, and confirmation, which finally proposes a method of inviting the receiver to subscribe to the contact information in a form of the contact status information.
  • the user preference confirmation refers to a setting to inform the receiver of the subscription request of another person and ask whether to accept the subscription request.
  • FIG. 3 illustrates an example of a contact information subscription invitation method through XML document delivery.
  • the CAB client A 100 transmits the contact share request to the CAB feature handler app. usage within the CAB XDMS 130 in step 300.
  • an XML Configuration Access Protocol (XCAP) request is used for the contact share request.
  • the contact share request contains a standardized invitation message for inviting a receiver, for example, XUI: sip:[email protected] to subscribe the contact information for a particular contact view among the personal information (PCC) and a selective filter value for allowing to subscribe to only a part of the contact view.
  • PCC personal information
  • the standardized invitation message can be automatically generated by a server having received the contact information subscription invitation message of the receiver.
  • the CAB XDMS 130 In response to the request, the CAB XDMS 130 notifies of the contact share request in step 305. To this end, the CAB feature handler app. usage within the CAB XDMS 130 informs a contact share function 105 within the CAB server 110 of a document change of the CAB feature handler, that is, document update information in response to the contact share request.
  • the CAB server 110 updates an access permission document of the receiver in step 310. Specifically, the access permission document is updated in the PCC app. usage within the CAB XDMS 120 based on the document update information in response to the contact share request obtained in step 605 in order to allow the subscription of the receiver according to the contact information subscription invitation of an originator. At this time, filter information contained for limiting the subscription to the contact information is also reflected to the access permission document. This corresponds to a process of authenticating the receiver, for example, user B to subscribe to the contact information of the originator, for example, user A in advance.
  • the CAB server 110 may receive a plurality of different subscription permission requests from contact information of a plurality of receivers of the user A, and serve to manage the subscription permission requests, that is, creation, update, deletion and the like for the plurality of subscription permission requests for the user A.
  • the CAB server 110 forwards the request in step 315.
  • the CAB server 110 In order to forward the request, the CAB server 110 generates and uses an XDCP forward request.
  • the XDCP forward request contains a standardized message for the contact information subscription invitation and a filter value for allowing to subscribe to only a part of the contact view.
  • the CAB server 110 generates URL information by which particular contact information can be actually received, inserts the generated URL information into the forward request, and transmits the forward request.
  • HTTP POST instead of a conventional "SIP MESSAGE
  • only information by which contact information is received can be transmitted instead of actual contact information, and also partial contact information can be provided through a filter value.
  • the XDCP forward request is transmitted to the PCC app. usage within the CAB XDMS 120.
  • the CAB XDMS 120 generates a new contact view by applying the filter for allowing to subscribe to only a part of a particular contact view designated for a subscription invitation by the originator, that is, user A, and then stores the generated new contact view in a temporary storage space or a separate document storage space within the PCC app. usage.
  • the CAB XDMS 120 forwards a remote request containing a URI value for the document and the standardized message for the contact information subscription invitation in step 320.
  • the CAB XDMS 120 may generate the URI value so that only the particular contact view can be shown to a particular receiver by applying the filter from all contact information.
  • an XDCP forward remote request is used for the remote request.
  • the XDCP forward remote request is transmitted to the CAB XDMS 130 including the receiving side, that is, the user B. Then, the PCC app. usage of the CAB XDMS 130 processes the remote request based on the received XDCP forward remote request in step 325. That is, the CAB XDMS 130 performs a preference confirmation for address book document delivery of the user B.
  • the preference for the address book document delivery may include settings such as acceptance, rejection, confirmation and the like.
  • the acceptance means to directly store the received document without asking the user B when the user B receives a subscription request from another person, the rejection means not to accept the subscription request of another person, and the confirmation means to inform the user B of the subscription request of another person, receive a response (for example, acceptance or rejection) to the subscription request from the user B, and process the response.
  • the CAB XDMS(130) fetches a document to be used for the contact information subscription invitation from a server storing the document by using the URI value of the document received from the user A, and stores the document as a temporary document, for example, in a type of ContactlnvitationPCC.xml
  • the CAB server 140 of the receiving side is informed of the temporary document from the PCC app. usage of the CAB XDMS 130 in step 330. Specifically, the CAB server 140 is informed of a contact invitation document containing "ContactSharePCC.xml" corresponding to the temporary document and a "note” element as a document change or informed of a contact invitation document containing "ContactInvitationPCC.xml” and the "note” element as a document change.
  • the CAB server 140 stores a contact entry in step 335.
  • An example of the contact entry includes an address, and address share data is converted according to an address book format and then added to an Address Book document (AB document) within the AB app. usage of the XDMS 130. Further, an address type is displayed as a contact status, an update type ( ⁇ updated>) is displayed as an entry status, and the ⁇ note> element corresponding to the standardized message (or expression) for the contract information subscription invitation transmitted from the originator is displayed, with reference to the contact invitation document in step 330.
  • the CAB server 140 transmits a server notification message containing the document change generated in the AB app. usage to synchronize the address book of the CAB client B 150 in step 340. Accordingly, the user B of the CAB client B 150 can view the contact information of which subscription is allowed by the user A through the synchronization of the address book.
  • FIG. 4 illustrates contact information share in an originating side in detail.
  • step 400 is the same as step 300 of FIG. 3 .
  • the contact share request contains a result report of the share request, and the standardized message for the contact information subscription invitation which is the 'contact subscription invitation" is contained in the "note" element within the share request.
  • the message for the contact share request is illustrated in FIG. 5 .
  • the standardized message which is the "contact subscription invitation" in the "note” element serves as an indication indicating that the contact share request is a request for sharing the contact for the contact information subscription invitation of the originator in the originating side and the receiving side.
  • the receiver XUI: sip:[email protected]
  • a filter value for allowing only a partial value of the corresponding document is set to subscribe to or read the contact information.
  • step 405 the CAB feature handler app. usage of the CAB XDMS 120 stores the XCAP request and transmits a response message (200 OK) to the CAB client A 100.
  • the CAB feature handler app usage informs the contact share function 105 within the CAB server 110 of the document change of the CAB feature handler, that is, document update information for the corresponding share request.
  • the contact share function 105 may obtain change information within the CAB feature handler by actively identifying whether the contact share request message is stored, separately from the CAB feature handler app. usage informing the change information.
  • step 410 the contact share function 105 transmits a response message (200 OK) to the CAB feature handler app. usage in step 415.
  • step 420 is the same as step 310 of FIG. 3 .
  • the contact share function 105 updates an access permission document based on filter information included within the document update information for the contact share request obtained in step 410 to limit the subscription to the receiver information and the contact information by using an XDM agent in order to allow the subscription of the receiver according to the contact information subscription invitation of the originator within the corresponding PCC app. usage.
  • FIG. 6 illustrates an example of an access permission document for allowing the subscription of the receiver according to the contact information subscription invitation within the PCC app. usage.
  • "allow-retrieve” which is a document rule of the personal information (PCC) in the contact information of the originator (XUI: sip:[email protected]) means that the receiver can subscribe to or read entire contact information of the originator.
  • the access permission document based on filter information (invite-include) included in the document update information for the contact share request obtained in step 410 to limit the subscription to the receiver (XUI: sip:[email protected]) information and the contact information, subscription or reading is allowed when the receiver finally accepts the contact information subscription invitation only for a name, a contact, and a career (career-history) among the personal information of the originator and attempts to subscribe to the contact information of the originator.
  • filter information invite-include
  • the contact information subscription invitation only for a name, a contact, and a career (career-history) among the personal information of the originator and attempts to subscribe to the contact information of the originator.
  • the contact share function 105 receives a response message (200 OK) from the PCC app. usage in step 425 and then generates and transmits the XDCP forward request to share the contact information with the corresponding PCC app. usage by using the XDM agent in step 430. At this time, the filter information for allowing to subscribe to only a partial value of the contact view obtained in step 410 is included. Further, the standardized message (or expression) for the contact information subscription invitation which is the "contact subscription invitation" is included in the "note” element within the XDCP forward request.
  • the XDCP forward request generated by the contact share function 105 is illustrated in FIG. 7 .
  • the PCC app. usage first identifies whether a contact share delivery report for contact share of the originator is made in step 435. Subsequently, for notification of a delivery result to the originator, related information is updated by inserting the "note" element into a delivery notification list ( ⁇ delivery-notification-list>) element of a forward notification list ( ⁇ forward-notification-list>) element within a forward notification list (hereinafter, referred to as an "FNL") app. usage of a List XDMS and setting a delivery status value of the corresponding receiver as "pending". In response to the update, the PCC app. usage receives a response message (200 OK) from the List XDMS 125 in step 440.
  • the PCC app. usage identifies that the receiver is a user of another domain based on the XDCP forward request, applies the filter for allowing to subscribe to only the partial value of the particular contact view designated for the subscription invitation by the originator, and then stores the contact view in a temporary storage space or a separate document storage space within the PCC app. usage.
  • an XDCP forward remote request containing a URI value for the document and a standardized message for a personal information subscription invitation to a receiving side in step 445.
  • the XDCP forward remote request generated by the PCC app. usage of an originating side is illustrated in FIG. 8 .
  • the PCC app. usage receives a response message (200 OK) for a delivery result from networks 127 &129 of the receiving side in step 450.
  • the PCC app. usage generates a response message (200 OK) for the XDCP forward request from the response message (200 OK) for the delivery result in step 455.
  • the contact share function 105 stores a forwarding result in step 460. That is, the contact share function 105 stores the delivery result in the CAB feature handler app. usage, and the CAB feature handler app. usage transmits the response message (200 OK) to the contact share function 105 in step 465.
  • step 470 the PCC app. usage receives a contact share delivery report from the networks 127&129 of the receiving side.
  • the PCC app. usage transmits a response message (200 OK) to the networks 127&129 of the receiving side in step 475.
  • the PCC app. usage updates a forward notification list in step 480. Specifically, for notification of a delivery result to the receiver, related information is updated by setting a delivery status value of the corresponding receiver as "delivered" in a delivery notification list ( ⁇ delivery-notification-list>) element of a forward notification list ( ⁇ forward-notification-list>) element within the forward notification list (hereinafter, referred to as an "FNL") of the List XDMS.
  • the PCC app. usage receives a response message (200 OK) form the List XDMS 125 in step 485.
  • step 490 the XDM agent within the CAB server 120 is informed of a result of the delivery report and updates a delivery status of the corresponding contact share request within the CAB FH app. usage in step 190.
  • FIG. 9 illustrates in detail a method of inviting to subscribe to personal information when user preference for XML document delivery of the receiver is set as 'accept'.
  • the PCC app usage including the CAB client B 150 receives the XDCP forward remote request from the networks 127&129 of the originating side in step 900. Then, the PCC app. usage identifies whether the receiver within the XDCP forward remote request is in a corresponding domain and then transmits a response message (200 OK) to the PCC app. usage including the CAB client A 100 in step 905.
  • usage of the CAB XDMS 130 identifies preference of the CAB client B 150 for the XDCP forward remote request from the AB forward preference within the AB app. usage in step 910.
  • the AB forward preference includes the following cases, and a case where the CAB client B 150 receives (accepts) an XDM resource received from the CAB client A 100 is described herein.
  • the XDM resource transmitted from the originating side is automatically stored in a corresponding XDM server in step 915.
  • the preference corresponds to the confirmation the XDM resource transmitted from the originating side is informed to the receiver and then a result thereof is waited for.
  • the preference corresponds to the rejection the XDM resource transmitted from the originating side is not stored in the corresponding XDM server and is rejected.
  • steps after step 920 are not performed.
  • the PCC app since the URI of the document included in the XDCP forward remote request, that is, the filter value set by the originator to allow to subscribe to only the partial value of the particular contact view designated by the originator for the subscription invitation is applied, the PCC app. usage of the receiving side fetches an XDM resource from the PCC app. usage of the originating side by using the URI of the document stored in the temporary storage space within the PCC. app. usage of the originating side or the separate storage space.
  • the XDM resource may be stored in a document form of "ContactSharePCC.xml", or stored in a new document form of "ContactInvitationPCC.xml” after the standardized message (or expression) for the personal information subscription invitation which is the "contact subscription invitation" in the "note” element included in the XDCP forward remote request.
  • the CAB server 140 is informed of a temporary document from the PCC app. usage of the receiving side in step 920. Specifically, the CAB server 140 is informed of "ContactSharePCC.xml" and a contact invitation document containing the "note” element as a document change, or informed of "ContactInvitationPCC.xml” and a contact invitation document containing the "note” element as a document change. Further, according to a system implementation, the contact invitation document may not be included by separately generating the contact invitation document containing the "note” element, but may be included within a notification request message (SIP NOTIFY) in a new header form.
  • SIP NOTIFY notification request message
  • the CAB server 140 is informed of the document change in a form of the "ContactSharePCC.xml" and the contact invitation document.
  • the CAB server 140 may actively obtain information corresponding to document change information within the PCC app. usage in the receiving side separately from being informed of the information from the PCC app. usage in the receiving side.
  • the CAB server 140 transmits a response message (200 OK) to the PCC app. usage in step 925, and then updates an address book in step 930. Specifically, the CAB server 140 converts contact information share data to an AB format, and then adds the converted contact information share data to an AB document within the AB app. usage. And then, the CAB server 140 displays an address type below as a contact status, an update type ( ⁇ updated>) as an entry status, and the ⁇ note> element corresponding to the standardized message (or expression) for the personal information subscription invitation transmitted from the originator, with reference to the contact invitation document or a "note" related header included in the notification request message.
  • FIG. 10 shows the contact status added for the contact information subscription invitation in addition to the contact share data within the AB document.
  • the AB app. usage transmits a response message (200 OK) to the CAB server 140 in step 935.
  • the PCC app. usage adds a ⁇ request-notification-list> element to a forward notification list of the List XDMS 132 to notify the receiver of a detailed matter of the received XDCP forward remote request in step 940.
  • the "note” element which is the standardized message (or expression) for the contact information subscription invitation is also stored in the contact information share request.
  • the ⁇ request-notification-list> element including the "note” element within the forward notification list of the List XDMS 132 is illustrated in FIG. 11 .
  • the receiver may identify information on an originator (XUI: sip:[email protected]) and the standardized message (or expression) for the contact information subscription invitation through the corresponding request notification list.
  • originator XUI: sip:[email protected]
  • change information of the corresponding request notification list of the List XDMS 132 can be notified to the receiver or the receiver can actively identify the corresponding request notification list of the List XDMS 132 to obtain the change information of the corresponding request notification list of the List XDMS 132.
  • step 945 the List XDMS 132 transmits a response message (200 OK) to the PCC app. usage.
  • the CAB XDMS 130 generates a contact share delivery report and transmits the contact share delivery report to the networks 127&129 of the originating side in step 950.
  • the CAB XDMS 130 receives a response message (200 OK) from the networks 127&129 of the originating side in step 955.
  • the CAB server 140 transmits a server notification message including the document change generated in the AB app. usage to synchronize the address book of the CAB client B 150 to the CAB client B 150 in step 960.
  • a contact information subscription process in a later time is performed according to a general procedure.
  • a contact information subscription result is informed according to a setting of allowing the subscription or the reading when the receiver (XUI: sip:[email protected]) accepts the contact information subscription invitation and finally attempts to subscribe to the contact information of the originator only for a name, a contact (comm-addr), and a career (career-history) through the preset access permission within the PCC app.
  • usage of the originator that is, a filter ID corresponding to "invite-include” in step 420 of FIG. 4
  • the contact information is updated according to the user preference.
  • the contact share is completed by adding the received AB document to the AB app. usage, setting a contact status as "temporary”, synchronizing the address of the CAB client B 150, directly expressing a confirmation intention by the receiver, and removing the "temporary" status.
  • the present invention implements a personal information subscription invitation method by transmitting the contact share request to the CAB server through the CAB FH app. usage.
  • the above embodiments may be modified within an allowable range of a general XDM document management function implementation in a converged address book system where the contact share request is transmitted to the CAB XDMS in a form of XDM document delivery through a direct interface for an XDM document delivery request/response between the CAB client and the CAB XDMS, but an overall operation and method are the same within the scope of the present invention.
  • the present invention implements a method of inviting a contact information subscription between different domain users
  • the method of inviting the contact information subscription between different domain users may be implement with some modifications in a contact information subscription invitation between the same domain users within an allowable range of a general XDM document management function implementation in a CAB server and a CAB XMDS within the same domain but an overall operation and method are the same within the scope of the present invention.
  • the originating side can make a request for subscribing only a desired part of all contact information, and the receiving side can selectively receive only contact information of a desired client.
  • the receiving side can selectively receive only contact information of a desired client.
  • address information on contact information instead of actual contact information, it is possible to increase a transmission efficiency and also increase a storage efficiency of the CAB server and the CAB XDMS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Databases & Information Systems (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Data Mining & Analysis (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
EP12855762.6A 2011-12-08 2012-12-07 Apparatus and method for inviting subscription to contact information Active EP2789122B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020110131358A KR101922985B1 (ko) 2011-12-08 2011-12-08 연락처 정보의 구독을 초대하는 장치 및 방법
PCT/KR2012/010638 WO2013085342A1 (en) 2011-12-08 2012-12-07 Apparatus and method for inviting subscription to contact information

Publications (3)

Publication Number Publication Date
EP2789122A1 EP2789122A1 (en) 2014-10-15
EP2789122A4 EP2789122A4 (en) 2015-08-12
EP2789122B1 true EP2789122B1 (en) 2018-03-07

Family

ID=48574620

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12855762.6A Active EP2789122B1 (en) 2011-12-08 2012-12-07 Apparatus and method for inviting subscription to contact information

Country Status (6)

Country Link
US (1) US10795963B2 (zh)
EP (1) EP2789122B1 (zh)
JP (1) JP6254530B2 (zh)
KR (1) KR101922985B1 (zh)
CN (1) CN103988468B (zh)
WO (1) WO2013085342A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9591056B2 (en) * 2013-01-29 2017-03-07 Facebook, Inc. Techniques for contact exporting
US10476758B2 (en) * 2013-07-11 2019-11-12 Google Llc Systems and methods for providing notifications of changes in a cloud-based file system
WO2015041469A1 (en) 2013-09-18 2015-03-26 Samsung Electronics Co., Ltd. A method and system for integrating content viewing and communication in immersive social centre session
KR20150059662A (ko) * 2013-11-22 2015-06-02 삼성전자주식회사 소셜 서비스 제공 시스템에서 관계 설정 방법 및 장치
CN104519057B (zh) 2014-12-12 2018-06-19 小米科技有限责任公司 资格授予方法、资格获取方法及装置
CN108366106B (zh) * 2018-01-31 2020-11-17 维沃移动通信有限公司 通信信息的更新方法、管理方法、修改方法和相关设备

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1442411A4 (en) 2001-09-30 2006-02-01 Realcontacts Ltd CONNECTING SERVICE
US7474741B2 (en) * 2003-01-20 2009-01-06 Avaya Inc. Messaging advise in presence-aware networks
US20100088105A1 (en) 2003-10-23 2010-04-08 Feldhahn Jeffrey M Method and system for updating electronic business cards
CN1998224A (zh) * 2004-05-12 2007-07-11 富盛旺公司 高级联络识别***
US8116444B2 (en) * 2006-02-01 2012-02-14 At&T Intellectual Property, L.P. System and method of publishing contact information
US20090100099A1 (en) 2007-08-08 2009-04-16 Buckwalter Alan M Method and apparatus for providing and offering an exchange database
CN101426017B (zh) * 2007-11-01 2012-06-27 华为技术有限公司 一种地址簿的处理方法和***
SG157990A1 (en) 2008-07-04 2010-01-29 3Rd Brand Pte Ltd System and method for facilitating the growth of a mobile community
CA2736755C (en) 2008-09-17 2015-04-28 Research In Motion Limited System and method for access and communication between a converged network-based address book system and a user device
RU2504115C2 (ru) * 2008-09-30 2014-01-10 Нокиа Корпорейшн Способ и устройство для управления контактами адресной книги
KR20100061254A (ko) * 2008-11-28 2010-06-07 삼성전자주식회사 통신 이력 제공 방법
CN102576361A (zh) * 2009-02-05 2012-07-11 捷讯研究有限公司 用于在基于网络的地址簿***中集中多个联系人信息源的***和方法
US20100325208A1 (en) * 2009-06-19 2010-12-23 Suresh Chitturi Methods and apparatus to forward documents in a communication network
WO2011011422A2 (en) * 2009-07-20 2011-01-27 Research In Motion Limited Methods and apparatus to use a network repository as a proxy to exchange converged address book service requests and responses
US8640204B2 (en) * 2009-08-28 2014-01-28 Broadcom Corporation Wireless device for group access and management
CA2773120A1 (en) * 2009-09-04 2011-03-10 Research In Motion Limited Methods and apparatus to subscribe for change notifications in a document management system
WO2011047050A2 (en) * 2009-10-15 2011-04-21 Reseach In Motion Limited Methods and apparatus to exchange converged address book events among multiple network domains
CN102075644B (zh) * 2009-11-23 2014-04-09 中兴通讯股份有限公司 融合地址簿中联系视图的实现方法与***
US20110145270A1 (en) * 2009-12-14 2011-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Service personas for address books
CN101771691B (zh) * 2009-12-29 2014-03-12 北京邮电大学 融合用户信息的***及用户信息的感知、融合和决策方法
EP2539835A4 (en) * 2010-02-22 2015-06-03 Nokia Corp METHOD AND APPARATUS FOR PROVIDING A RESEARCH TOOL IN ASSOCIATION WITH MANAGING AN ADDRESS BOOK
KR101712199B1 (ko) * 2010-03-02 2017-03-03 삼성전자주식회사 메시징 서비스와 소셜 네트워크 서비스 간의 상호 연동을 통한 연락처 제공 장치 및 방법
CA2798583A1 (en) * 2010-05-07 2011-11-10 Telefonica, S.A. System and method for synchronizing the profile of a user in social networks and the user's personal contact card (pcc)
US20110295988A1 (en) * 2010-05-28 2011-12-01 Le Jouan Herve Managing data on computer and telecommunications networks
KR20130012199A (ko) * 2011-06-28 2013-02-01 삼성전자주식회사 메시징 서비스와 타 서비스 간의 상호 연동을 통한 연락처 제공 방법 및 장치
US20130091287A1 (en) * 2011-10-05 2013-04-11 Suresh Chitturi System for contact subscription invitations in a cross-domain converged address book system
US9113283B2 (en) * 2012-04-03 2015-08-18 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (M2M) context
KR101906413B1 (ko) * 2012-08-02 2018-10-11 삼성전자주식회사 통신 시스템에서 개인 정보를 갱신하는 방법 및 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN103988468B (zh) 2018-06-29
WO2013085342A1 (en) 2013-06-13
CN103988468A (zh) 2014-08-13
EP2789122A4 (en) 2015-08-12
KR101922985B1 (ko) 2018-11-29
EP2789122A1 (en) 2014-10-15
US10795963B2 (en) 2020-10-06
US20140344215A1 (en) 2014-11-20
KR20130082561A (ko) 2013-07-22
JP6254530B2 (ja) 2017-12-27
JP2015502613A (ja) 2015-01-22

Similar Documents

Publication Publication Date Title
EP2789122B1 (en) Apparatus and method for inviting subscription to contact information
KR101635906B1 (ko) 통신 이력 제공 방법
US8788694B2 (en) Content update from a server to a client terminal in a dynamic content delivery (DCD) system
EP2055023B1 (en) Method of securing privacy in automatic answer mode of push-to service
US20140012813A1 (en) Method and apparatus for synchronizing personal information
CN103119911A (zh) 用于同步社交网络的用户配置文件和用户的个人联系卡（pcc）的方法和***
CN102138315A (zh) 在ims用户中的服务共享
CN105812229A (zh) 一种终端通信方法、***及相关装置
EP2847931B1 (en) Method and apparatus for updating personal information in communication system
CN102007784A (zh) 用于与非融合因特网协议消息服务互配的融合因特网协议消息服务提供***和方法
CN102308557A (zh) 用于在通信网络中访问和提供存在信息的方法和服务器
US20140143675A1 (en) Method and apparatus for providing contact information through interworking between messaging service and another service
US9692796B2 (en) Apparatus and method for setting disposition with respect to document share
CN108476203A (zh) 本地呈现授权策略的可配置使用
KR20110074244A (ko) 통신 시스템에서 인스턴트 메시징 클라이언트 간 데이터 동기화 장치 및 방법
CN101800759B (zh) 一种邀请订阅的实现***及方法
EP2891270B1 (en) Method and apparatus for updating personal information in communication system
EP2874069A1 (en) Method and apparatus for managing personal information in communication system
KR101691235B1 (ko) 통합 주소록 서비스 기반의 주소 상태를 제공하기 위한 장치 및 방법
WO2008100019A1 (en) Method for providing cpm service using device profile
CN101374161A (zh) 网络地址簿的实现方法和网络地址簿服务器

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140606

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20150710

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/12 20060101ALI20150706BHEP

Ipc: G06Q 50/30 20120101ALI20150706BHEP

Ipc: G06Q 10/10 20120101ALI20150706BHEP

Ipc: H04L 29/06 20060101ALI20150706BHEP

Ipc: H04L 12/16 20060101AFI20150706BHEP

17Q First examination report despatched

Effective date: 20160314

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170926

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 977670

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180315

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012043865

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180607

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 977670

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180307

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180608

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012043865

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180709

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

26N No opposition filed

Effective date: 20181210

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20181207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181207

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181207

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180307

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180307

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20121207

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180707

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20231121

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231120

Year of fee payment: 12