EP2936340B1 - Auto-achèvement à l'aide d'entités reliées atomiquement amenées à persister - Google Patents

Auto-achèvement à l'aide d'entités reliées atomiquement amenées à persister Download PDF

Info

Publication number
EP2936340B1
EP2936340B1 EP13829057.2A EP13829057A EP2936340B1 EP 2936340 B1 EP2936340 B1 EP 2936340B1 EP 13829057 A EP13829057 A EP 13829057A EP 2936340 B1 EP2936340 B1 EP 2936340B1
Authority
EP
European Patent Office
Prior art keywords
entity
user interface
linked
input
auto
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
EP13829057.2A
Other languages
German (de)
English (en)
Other versions
EP2936340A2 (fr
Inventor
Kieran K. GUPTA
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.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Technology Licensing LLC
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 Microsoft Technology Licensing LLC filed Critical Microsoft Technology Licensing LLC
Publication of EP2936340A2 publication Critical patent/EP2936340A2/fr
Application granted granted Critical
Publication of EP2936340B1 publication Critical patent/EP2936340B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/20—Natural language analysis
    • G06F40/274—Converting codes to words; Guess-ahead of partial word inputs

Definitions

  • Embodiments are provided for persisting atomically linked entities when utilizing an auto-complete mechanism.
  • a computing device may be utilized to receive an input in a user interface. The computing device may then display an auto-complete suggestion list in response to receiving the input in the user interface. A selection of an entity may then be received from the auto-complete suggestion list. The selected entity may then be atomically linked to program code defining an action. The atomically linked entity may then be inserted in the user interface. The atomically linked entity may then be persisted among the input received within the user interface. The input is modifiable and the atomically linked entity is unmodifiable within the user interface.
  • Embodiments are provided for persisting atomically linked entities when utilizing an auto-complete mechanism.
  • a computing device may be utilized to receive an input in a user interface. The computing device may then display an auto-complete suggestion list in response to receiving the input in the user interface. A selection of an entity may then be received from the auto-complete suggestion list. The selected entity may then be atomically linked to program code defining an action. The atomically linked entity may then be inserted in the user interface. The atomically linked entity may then be persisted among the input received within the user interface. The input is modifiable and the atomically linked entity is unmodifiable within the user interface.
  • FIGURE 1 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with an embodiment.
  • the computing device may comprise a general purpose desktop, laptop, handheld, tablet, or other type of computer capable of executing one or more application programs.
  • the user interface may include an input area (e.g., a text box) for receiving an input 20 from a user via keyboard 60.
  • the keyboard 60 may comprise a touchscreen or physical keyboard for entering text or graphic characters (e.g., emoticons, etc.) into the input area.
  • the input 20 may also be received via voice, gestures or other means known by those skilled in the art for inputting data.
  • the input area may be utilized for composing a message to one or more users for posting (via post command 70) to a social networking site.
  • the input area may further include invocation character 30 which, in accordance with an embodiment, may comprise a predetermined special character (e.g., a "@" symbol) which may be utilized to invoke an auto-complete suggestion list 50.
  • the invocation character 30 may comprise any number of predetermined special characters for invoking the auto-complete suggestion list 50.
  • a predetermined special character may not be required and the auto-complete suggestion list 50 may be invoked by typing one or more initial characters of an entity name (e.g., the first few letters of a user's social networking account name).
  • a cursor 40 is also provided for allowing a user to enter additional input following the selection of an entity from the auto-complete suggestion list 50.
  • the auto-complete suggestion list 50 may be utilized to select an entity (e.g., a user's name or term) for insertion into the input area as a special or "atomic" entity.
  • an atomic entity as defined herein, is an entity that is linked to special code (e.g., program code) that has a specific meaning. Once an atomic entity has been inserted into the input area, the link is persisted even while a user continues to type a message. Once an entity is atomically linked, a user may only either use the entire term or delete the entire term. However, the user is prevented from modifying any portion of the atomic entity.
  • the auto-complete suggestion list 50 may be populated from a database of finite entities (e.g., user names) each of which is linked to data (e.g., account data) which may be utilized for accessing information about an entity directly from within a message.
  • finite entities e.g., user names
  • data e.g., account data
  • the selection of an atomic entity linked to a user within a social networking post may cause the display of that user's social network profile information.
  • an atomic entity may be linked to a tracking number which, when selected within a message, may direct a user to package tracking information.
  • atomic entities may also be linked to other types of data.
  • the message posts described herein may comprise "rich" posts which are text posts having content as part of the post. Examples of rich posts may include, without limitation, tags or hash tags which are linked to other content related to text contained within a post.
  • the user interface on the computing device screen display 10 may be generated by an integrated web application platform for providing intranet portals, document and file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence.
  • An illustrative integrated web application platform is the SHAREPOINT web application platform developed by MICROSOFT CORPORATION of Redmond, Washington. It should be understood, however, that other web application platforms from other manufacturers may also be utilized without departing from the scope of the embodiments described herein.
  • FIGURE 2 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with another embodiment.
  • the input area shows additional text input added to the input 20 (from the keyboard 60) following the invocation character 30.
  • the auto-complete suggestion list 50 automatically filters the entities based on matching characters in the additional text input.
  • the alphabetical listing of entities is filtered from entities starting with the character "A” (as shown in FIGURE 1 ) to entities starting with the character "Jo” (e.g., "John Smith”).
  • FIGURE 3 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with another embodiment.
  • the input area shows the insertion of an entity 80 (i.e., "John Smith") within the input 20 which was selected (e.g., via touch or input from the keyboard 50) from the auto-complete suggestion list shown in FIGURE 2 .
  • the auto-complete suggestion list is no longer visible following the insertion of the entity 80 (alternatively referred to herein as the "atomic entity 80").
  • the auto-complete suggestion list may be automatically hidden upon the insertion of an entity from the auto-complete suggestion list.
  • the auto-complete suggestion list may also be hidden in response to a user entered termination character (e.g., a period, question mark, exclamation point, etc.).
  • a user entered termination character e.g., a period, question mark, exclamation point, etc.
  • the entity 80 is linked to special code and the length and starting position of the entity in the input 20 is maintained.
  • the entity 80 is atomically linked (i.e., the entity may only be used as a whole or deleted as a whole but may not be partially modified).
  • FIGURE 4 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with another embodiment.
  • the input area shows the selection of the atomic entity 80 (i.e., "John Smith") within the input 20.
  • the entire atomic entity 80 e.g., via touch or input from the keyboard 60
  • the highlighting of the entire atomic entity 80 may be utilized to visually convey that a user is prohibited from adding additional text or removing specific characters from the atomic entity 80.
  • FIGURE 5 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with the invention.
  • the input area shows the deletion of the atomic entity 80 (show in FIGURE 4 ) from the input 20 in response to a user editing action.
  • the atomic entity 80 may be deleted when a user, via the keyboard 60, backspaces or attempts to enter a new character after the atomic entity 80 has been selected.
  • the atomic entity 80 is enforced by prohibiting the modification of part of entity (which would in turn break any associated link).
  • the auto-complete suggestion list 80 is automatically invoked so that a user may select another entity for insertion into the input 20.
  • FIGURE 6 is a computing device screen display 10 of a user interface for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with another embodiment.
  • the input area shows multiple atomic entities (i.e., the atomic entities 80 and 85) which have been inserted among the input 20 with the atomic entity 85 being shown as selected by a user (e.g., highlighted).
  • the links for multiple unique entities may be independently persisted to special (e.g., program) code appropriately and their atomic nature may be separately maintained so that a user is prohibited from modifying any of a number of displayed atomic entities.
  • FIGURE 7 is a flow diagram illustrating a routine illustrating a routine 700 for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with an embodiment.
  • routines for persisting atomically linked entities when utilizing an auto-complete mechanism, in accordance with an embodiment.
  • the logical operations of various embodiments of the present invention are implemented (1) as a sequence of computer implemented acts or program modules running on a computing device or system, and/or (2) as interconnected machine logical circuits or circuit modules within the computing device or system.
  • the implementation is a matter of choice dependent on the performance requirements of the computing device or system implementing the invention.
  • the logical operations illustrated in FIGURES 7-8 and making up the various embodiments described herein are referred to variously as operations, structural devices, acts or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logical, and any combination thereof without deviating from the scope of the present invention as recited within the claims set
  • the routine 700 begins at operation 705, where an application executing on a computing device receives an input in a user interface.
  • a messaging application may receive text or graphics (e.g., emoticons, etc.) for posting a message to another user on a social networking website.
  • the routine 700 continues to operation 710, where the application executing on the computing device may display an auto-complete suggestion list of selectable entities in response to receiving the input in the user interface.
  • the auto-complete suggestion list may be displayed automatically in response to receiving a predetermined character (e.g., a "@" symbol) among received text in the user interface.
  • the auto-complete suggestion list may be displayed automatically in response to the first few characters of an entity (e.g., a user name) being received in the user interface. It should be understood that after the auto-complete suggestion list has been displayed, the list may be dynamically filtered by the application as additional characters corresponding to known entities are input into the user interface.
  • routine 700 continues to operation 715, where the application executing on the computing device may receive a selection of an entity from the auto-complete suggestion list.
  • routine 700 continues to operation 720, where the application executing on the computing device may link the selected entity to program code defining an action. For example, the application may link the selected entity to program code for initiating a message post to a user identified by the selected entity.
  • the routine 700 continues to operation 725, where the application executing on the computing device may insert the linked entity in the user interface among the received input.
  • the inserted linked entity is atomic. That is, the atomic entity may only be either used as a whole or deleted as a whole. Thus, a user is prevented from modifying any portion of the atomic entity.
  • routine 700 continues to operation 730, where the application executing on the computing device may persist the linked entity among the input received within the user interface. As discussed above, any portion of the input outside of the atomic entity may be modified, however, the atomic entity itself is unmodifiable within the user interface. From operation 730, the routine 700 then ends.
  • the operations 700-730 may also be applied to multiple atomic entities.
  • one or more different entities may also be selected in response to subsequent input being received in the user interface.
  • the one or more different entities may further be linked to program code defining an action (e.g., for initiating a message post) and inserted as atomic entities in a user interface.
  • each of the different atomic entities may be independently persisted such that each of the atomic entities is unmodifiable while any surrounding input (e.g., text) may be modified by a user.
  • FIGURE 8 is a flow diagram illustrating a routine illustrating a routine 800 for persisting atomically linked entities when utilizing an auto-complete mechanism.
  • the routine 800 begins at operation 805, where an application executing on a computing device receives an editing action on a linked entity.
  • the editing action may comprise a backspace or an attempt to enter a new character within an atomic entity.
  • the application may be configured to dynamically compute a character position upon receiving an editing action to determine whether or not the editing action is directed towards an atomic entity.
  • the application may further be configured to highlight an atomic entity upon detecting the movement of a cursor over the entity.
  • routine 800 continues to operation 810, where the application executing on the computing device may delete the linked entity in response to receiving the editing action.
  • the application may enforce an atomic entity by prohibiting the modification of part of entity (which would in turn break any associated link).
  • routine 800 continues to operation 815, where the application executing on the computing device redisplays the auto-complete suggestion list in response to the deletion of the atomic entity at operation 810. From operation 815, the routine 800 then ends.
  • FIGURE 9 is a block diagram illustrating example physical components of a computing device 900 with which various embodiments may be practiced.
  • the computing device 900 may include at least one processing unit 902 and a system memory 904.
  • system memory 904 may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or any combination.
  • System memory 904 may include an operating system 905, application 907 and database 920.
  • Operating system 905, for example may be suitable for controlling computing device 900's operation and, in accordance with an embodiment, may comprise the iOS and OS operating systems from APPLE INC.
  • the application 907 may be utilized for persisting atomically linked entities when utilizing an auto-complete mechanism.
  • the application 907 may comprise an integrated web application platform for providing intranet portals, document and file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence.
  • the database 920 may be utilized to store finite entities (e.g., user names) each of which is linked to data (e.g., account data) which may be utilized for accessing information about an entity directly from within a message.
  • finite entities e.g., user names
  • data e.g., account data
  • the computing device 900 may have additional features or functionality.
  • the computing device 900 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, solid state storage devices ("SSD”), flash memory or tape.
  • additional storage is illustrated in FIGURE 9 by a removable storage 909 and a non-removable storage 910.
  • program modules may be provided which include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types.
  • various embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
  • Various embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote memory storage devices.
  • various embodiments may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors.
  • various embodiments may be practiced via a system-on-a-chip ("SOC") where each or many of the components illustrated in FIGURE 9 may be integrated onto a single integrated circuit.
  • SOC system-on-a-chip
  • Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which are integrated (or "burned") onto the chip substrate as a single integrated circuit.
  • the functionality, described herein may operate via application-specific logic integrated with other components of the computing device/system 900 on the single integrated circuit (chip).
  • Embodiments may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies.
  • embodiments may be practiced within a general purpose computer or in any other circuits or systems.
  • Various embodiments may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
  • the computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
  • Computer readable media may include computer storage media.
  • Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
  • the system memory 904, removable storage 909, and non-removable storage 910 are all computer storage media examples (i.e., memory storage.)
  • Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by the computing device 900. Any such computer storage media may be part of the computing device 900.
  • the computing device 900 may also have input device(s) 912 such as a keyboard, a mouse, a pen, a sound input device (e.g., a microphone) for receiving a voice input, a touch input device for receiving gestures, etc.
  • input device(s) 912 such as a keyboard, a mouse, a pen, a sound input device (e.g., a microphone) for receiving a voice input, a touch input device for receiving gestures, etc.
  • Output device(s) 914 such as a display, speakers, a printer, etc. may also be included.
  • the aforementioned devices are examples and others may be used.
  • Computer readable media may also include communication media.
  • Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
  • modulated data signal may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal.
  • communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
  • RF radio frequency
  • FIGURES 10A and 10B illustrate a suitable mobile computing environment, for example, a mobile computing device 1050 which may include, without limitation, a smartphone, a tablet personal computer, a laptop computer, and the like, with which various embodiments may be practiced.
  • a mobile computing device 1050 which may include, without limitation, a smartphone, a tablet personal computer, a laptop computer, and the like, with which various embodiments may be practiced.
  • FIG. 10A an example mobile computing device 1050 for implementing the embodiments is illustrated.
  • mobile computing device 1050 is a handheld computer having both input elements and output elements.
  • Input elements may include touch screen display 1025 and input buttons 1010 that allow the user to enter information into mobile computing device 1050.
  • Mobile computing device 1050 may also incorporate an optional side input element 1020 allowing further user input.
  • Optional side input element 1020 may be a rotary switch, a button, or any other type of manual input element.
  • mobile computing device 1050 may incorporate more or less input elements.
  • display 1025 may not be a touch screen in some embodiments.
  • the mobile computing device is a portable telephone system, such as a cellular phone having display 1025 and input buttons 1010.
  • Mobile computing device 1050 may also include an optional keypad 1005.
  • Optional keypad 1005 may be a physical keypad or a "soft" keypad generated on the touch screen display.
  • Mobile computing device 1050 incorporates output elements, such as display 1025, which can display a graphical user interface (GUI). Other output elements include speaker 1030 and LED 1080. Additionally, mobile computing device 1050 may incorporate a vibration module (not shown), which causes mobile computing device 1050 to vibrate to notify the user of an event. In yet another embodiment, mobile computing device 1050 may incorporate a headphone jack (not shown) for providing another means of providing output signals.
  • output elements such as display 1025, which can display a graphical user interface (GUI).
  • GUI graphical user interface
  • Other output elements include speaker 1030 and LED 1080.
  • mobile computing device 1050 may incorporate a vibration module (not shown), which causes mobile computing device 1050 to vibrate to notify the user of an event. In yet another embodiment, mobile computing device 1050 may incorporate a headphone jack (not shown) for providing another means of providing output signals.
  • any computer system having a plurality of environment sensors, a plurality of output elements to provide notifications to a user and a plurality of notification event types may incorporate the various embodiments described herein.
  • FIG. 10B is a block diagram illustrating components of a mobile computing device used in one embodiment, such as the mobile computing device 1050 shown in FIG. 10A .
  • mobile computing device 1050 can incorporate a system 1002 to implement some embodiments.
  • system 1002 can be used in implementing a "smart phone" that can run one or more applications similar to those of a desktop or notebook computer.
  • the system 1002 is integrated as a computing device, such as an integrated personal digital assistant (PDA) and wireless phone.
  • PDA personal digital assistant
  • One or more applications 1067 and a database 1095 may be loaded into memory 1062 and run on or in association with an operating system 1064.
  • the system 1002 also includes non-volatile storage 1068 within memory the 1062.
  • Non-volatile storage 1068 may be used to store persistent information that should not be lost if system 1002 is powered down.
  • the one or more applications 1067 may be utilized for persisting atomically linked entities when utilizing an auto-complete mechanism.
  • the one or more applications 1067 may use and store information in the database 1095 and in the non-volatile storage 1068.
  • the one or more applications 1067 may comprise an integrated web application platform for providing intranet portals, document and file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence.
  • the database 1095 may be utilized to store finite entities (e.g., user names) each of which is linked to data (e.g., account data) which may be utilized for accessing information about an entity directly from within a message.
  • finite entities e.g., user names
  • data e.g., account data
  • a synchronization application (not shown) also resides on system 1002 and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage 1068 synchronized with corresponding information stored at the host computer.
  • other applications may also be loaded into the memory 1062 and run on the mobile computing device 1050.
  • the system 1002 has a power supply 1070, which may be implemented as one or more batteries.
  • the power supply 1070 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.
  • the system 1002 may also include a radio 1072 (i.e., radio interface layer) that performs the function of transmitting and receiving radio frequency communications.
  • the radio 1072 facilitates wireless connectivity between the system 1002 and the "outside world," via a communications carrier or service provider. Transmissions to and from the radio 1072 are conducted under control of OS 1064. In other words, communications received by the radio 1072 may be disseminated to the applications 1067 via OS 1064, and vice versa.
  • the radio 1072 allows the system 1002 to communicate with other computing devices, such as over a network.
  • the radio 1072 is one example of communication media.
  • the embodiment of the system 1002 is shown with two types of notification output devices: the LED 1080 that can be used to provide visual notifications and an audio interface 1074 that can be used with speaker 1030 to provide audio notifications. These devices may be directly coupled to the power supply 1070 so that when activated, they remain on for a duration dictated by the notification mechanism even though processor 1060 and other components might shut down for conserving battery power.
  • the LED 1080 may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device.
  • the audio interface 1074 is used to provide audible signals to and receive audible signals from the user.
  • the audio interface 1074 may also be coupled to a microphone (not shown) to receive audible input, such as to facilitate a telephone conversation.
  • the microphone may also serve as an audio sensor to facilitate control of notifications.
  • the system 1002 may further include a video interface 1076 that enables an operation of on-board camera 1040 to record still images, video streams, and the like.
  • a mobile computing device implementing the system 1002 may have additional features or functionality.
  • the device may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape.
  • additional storage is illustrated in FIG. 10B by storage 1068.
  • Data/information generated or captured by the mobile computing device 1050 and stored via the system 1002 may be stored locally on the mobile computing device 1050, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio 1072 or via a wired connection between the mobile computing device 1050 and a separate computing device associated with the mobile computing device 1050, for example, a server computer in a distributed computing network such as the Internet.
  • a server computer in a distributed computing network such as the Internet.
  • data/information may be accessed via the mobile computing device 1050 via the radio 1072 or via a distributed computing network.
  • data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Computer Interaction (AREA)
  • User Interface Of Digital Computer (AREA)
  • Document Processing Apparatus (AREA)
  • Information Transfer Between Computers (AREA)
  • Machine Translation (AREA)
  • Input From Keyboards Or The Like (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Facsimiles In General (AREA)
  • Telephone Function (AREA)

Claims (11)

  1. Procédé mis en œuvre par un ordinateur pour faire persister des entités reliées atomiquement lors de l'utilisation d'un mécanisme d'autocomplétion, comprenant :
    la réception, par un dispositif informatique, d'une entrée dans une interface utilisateur ;
    l'affichage, par le dispositif informatique, d'une liste de suggestions d'autocomplétion en réponse à la réception de l'entrée dans l'interface utilisateur ;
    la réception, par le dispositif informatique, de la sélection d'une entité provenant de la liste de suggestions d'autocomplétion ;
    la liaison, par le dispositif informatique, de l'entité sélectionnée à un code de programme définissant une action ;
    l'insertion, par le dispositif informatique, de l'entité reliée dans l'interface utilisateur, l'entité reliée étant atomique ; et
    la persistance, par le dispositif informatique, de l'entité reliée parmi l'entrée reçue dans l'interface utilisateur, l'entrée étant modifiable et l'entité reliée n'étant pas modifiable dans l'interface utilisateur ;
    caractérisé en ce que le procédé comprend en outre :
    la réception d'une action d'édition sur l'entité reliée dans l'interface utilisateur ;
    la suppression de l'entité reliée en réponse à la réception de l'action d'édition ; et
    le réaffichage de la liste de suggestions d'autocomplétion.
  2. Procédé selon la revendication 1, comprenant en outre :
    la réception d'une sélection d'au moins une entité différente provenant de la liste de suggestions d'autocomplétion en réponse à la réception d'une entrée subséquente dans l'interface utilisateur ;
    la liaison de ladite au moins une entité différente sélectionnée avec le code de programme définissant une action ;
    l'insertion de ladite au moins une entité différente reliée dans l'interface utilisateur, ladite au moins une entité différente reliée étant atomique ; et
    la persistance indépendante de ladite au moins une entité différente reliée et de l'entité reliée parmi l'entrée et l'entrée subséquente reçues dans l'interface utilisateur, ladite au moins une entité différente reliée n'étant pas modifiable dans l'interface utilisateur.
  3. Procédé selon la revendication 1, dans lequel la réception, par un dispositif informatique, d'une entrée dans une interface utilisateur comprend la réception d'un ou plusieurs graphiques ou caractères textuels dans l'interface utilisateur.
  4. Procédé selon la revendication 1, dans lequel la réception, par un dispositif informatique, d'une entrée dans une interface utilisateur comprend la réception d'une entrée utilisateur dans une application de messagerie pour envoyer un message à un autre utilisateur.
  5. Procédé selon la revendication 1, dans lequel l'affichage, par le dispositif informatique, d'une liste de suggestions d'autocomplétion en réponse à la réception de l'entrée dans l'interface utilisateur comprend l'affichage de la liste de suggestions d'autocomplétion en réponse à la réception d'un caractère prédéterminé dans l'interface utilisateur.
  6. Procédé selon la revendication 1, dans lequel l'affichage, par le dispositif informatique, d'une liste de suggestions d'autocomplétion en réponse à la réception de l'entrée dans l'interface utilisateur comprend le filtrage dynamique de la liste de suggestions d'autocomplétion alors qu'un ou plusieurs caractères comprenant l'entrée sont reçus dans l'interface utilisateur.
  7. Procédé selon la revendication 1, dans lequel la liaison, par le dispositif informatique, de l'entité sélectionnée à un code de programme définissant une action comprend la liaison de l'entité sélectionnée à un code de programme pour initier l'envoi d'un message à un utilisateur identifié par l'entité sélectionnée.
  8. Dispositif informatique pour faire persister des entités reliées atomiquement lors de l'utilisation d'un mécanisme d'autocomplétion, comprenant :
    une mémoire pour le stockage d'un code de programme exécutable ; et
    un processeur couplé fonctionnellement à la mémoire, le processeur répondant à des instructions exécutables par un ordinateur contenues dans le code de programme et étant fonctionnel pour :
    la réception d'une entrée dans l'interface utilisateur ;
    l'affichage d'une liste de suggestions d'autocomplétion en réponse à la réception de l'entrée dans l'interface utilisateur ;
    la réception de la sélection d'une entité provenant de la liste de suggestions d'autocomplétion ;
    la liaison de l'entité sélectionnée à un code de programme définissant une action ;
    l'insertion de l'entité reliée dans l'interface utilisateur, l'entité reliée étant atomique ;
    la persistance de l'entité reliée parmi l'entrée reçue dans l'interface utilisateur, l'entrée étant modifiable et l'entité reliée n'étant pas modifiable dans l'interface utilisateur ;
    caractérisé en ce qu'il est en outre fonctionnel pour :
    la réception d'une action d'édition sur l'entité reliée dans l'interface utilisateur ;
    la suppression de l'entité reliée en réponse à la réception de l'action d'édition ; et
    le réaffichage de la liste de suggestions d'autocomplétion.
  9. Support de stockage lisible par un ordinateur et comportant des instructions exécutables par un ordinateur qui, lorsqu'elles sont exécutées par un dispositif informatique, commandent au dispositif informatique de mettre en œuvre un procédé pour faire persister des entités reliées atomiquement lors de l'utilisation d'un mécanisme d'autocomplétion, le procédé comprenant :
    la réception d'une entrée dans l'interface utilisateur d'une application de messagerie pour envoyer des messages à un ou plusieurs utilisateurs ;
    l'affichage d'une liste de suggestions d'autocomplétion en réponse à la réception de l'entrée dans l'interface utilisateur ;
    la réception de la sélection d'une entité provenant de la liste de suggestions d'autocomplétion ;
    la liaison atomique de l'entité sélectionnée à un code de programme définissant une action ;
    l'insertion de l'entité reliée dans l'interface utilisateur ;
    la persistance de l'entité reliée parmi l'entrée reçue dans l'interface utilisateur, l'entrée étant modifiable et l'entité reliée n'étant pas modifiable dans l'interface utilisateur ;
    caractérisé en ce qu'il comprend en outre :
    la réception d'une action d'édition sur l'entité reliée dans l'interface utilisateur ;
    la suppression de l'entité reliée en réponse à la réception de l'action d'édition ; et
    le réaffichage de la liste de suggestions d'autocomplétion.
  10. Support de stockage lisible par un ordinateur selon la revendication 9, dans lequel la liste de suggestions d'autocomplétion est filtrée dynamiquement alors que l'entrée est reçue dans l'interface utilisateur.
  11. Support de stockage lisible par un ordinateur selon la revendication 9 ou 10, dans lequel le procédé comprend en outre :
    la réception d'une sélection d'au moins une entité différente provenant de la liste de suggestions d'autocomplétion en réponse à la réception d'une entrée subséquente dans l'interface utilisateur ;
    la liaison de ladite au moins une entité différente sélectionnée avec le code de programme définissant une action ;
    l'insertion de ladite au moins une entité différente reliée dans l'interface utilisateur, ladite au moins une entité différente reliée étant atomique ; et
    la persistance indépendante de ladite au moins une entité différente reliée et de l'entité reliée parmi l'entrée et l'entrée subséquente reçues dans l'interface utilisateur, ladite au moins une entité différente reliée n'étant pas modifiable dans l'interface utilisateur.
EP13829057.2A 2012-12-20 2013-12-19 Auto-achèvement à l'aide d'entités reliées atomiquement amenées à persister Active EP2936340B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/722,200 US9836179B2 (en) 2012-12-20 2012-12-20 Auto-complete with persisted atomically linked entities
PCT/US2013/076562 WO2014100414A2 (fr) 2012-12-20 2013-12-19 Auto-achèvement à l'aide d'entités reliées atomiquement amenées à persister

Publications (2)

Publication Number Publication Date
EP2936340A2 EP2936340A2 (fr) 2015-10-28
EP2936340B1 true EP2936340B1 (fr) 2019-12-04

Family

ID=50097811

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13829057.2A Active EP2936340B1 (fr) 2012-12-20 2013-12-19 Auto-achèvement à l'aide d'entités reliées atomiquement amenées à persister

Country Status (8)

Country Link
US (2) US9836179B2 (fr)
EP (1) EP2936340B1 (fr)
JP (2) JP6320420B2 (fr)
KR (1) KR102143258B1 (fr)
CN (2) CN110096700B (fr)
AR (1) AR094186A1 (fr)
TW (1) TW201433967A (fr)
WO (1) WO2014100414A2 (fr)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9836179B2 (en) 2012-12-20 2017-12-05 Microsoft Technology Licensing, Llc Auto-complete with persisted atomically linked entities
US9619046B2 (en) * 2013-02-27 2017-04-11 Facebook, Inc. Determining phrase objects based on received user input context information
US9313284B2 (en) 2013-03-14 2016-04-12 International Business Machines Corporation Smart posting with data analytics and semantic analysis to improve a message posted to a social media service
US10684752B2 (en) * 2013-04-12 2020-06-16 Salesforce.Com, Inc. Computer implemented methods and apparatus for responding to actionable text patterns in a feed item
US20150006632A1 (en) * 2013-06-27 2015-01-01 Google Inc. Determining additional information for an intended action of a user
US9860338B2 (en) * 2014-12-30 2018-01-02 Facebook, Inc. Systems, methods, and apparatus for relationship mapping
US9965569B2 (en) 2015-03-13 2018-05-08 Microsoft Technology Licensing, Llc Truncated autosuggest on a touchscreen computing device
US9929990B2 (en) * 2015-04-28 2018-03-27 Dropbox, Inc. Inserting content into an application from an online synchronized content management system
US20170083211A1 (en) * 2015-09-21 2017-03-23 Microsoft Technology Licensing, Llc Focused attention in documents and communications
US10049149B2 (en) 2015-09-29 2018-08-14 Oath Inc. Computerized system and method for search query auto-completion
US10380190B2 (en) 2015-11-18 2019-08-13 International Business Machines Corporation Optimized autocompletion of search field
US10909146B2 (en) 2015-12-07 2021-02-02 Microsoft Technology Licensing, Llc Providing automated hashtag suggestions to categorize communication
US10749986B2 (en) 2016-04-11 2020-08-18 Samsung Electronics Co., Ltd. Platform for interaction via commands and entities
US10452638B2 (en) 2016-12-14 2019-10-22 International Business Machines Corporation Atomically moving data elements between or within linked data structures having no support for atomic moves
US10749978B2 (en) * 2017-04-07 2020-08-18 Accenture Global Solutions Limited Tags for automatic cloud resource provisioning
US11153284B2 (en) * 2018-11-07 2021-10-19 Citrix Systems, Inc. Systems and methods for transparent SaaS data encryption and tokenization
JP6725943B2 (ja) * 2019-04-03 2020-07-22 Ｌｉｎｅ株式会社 表示方法およびプログラム
JP6966157B2 (ja) * 2019-04-03 2021-11-10 Ｌｉｎｅ株式会社 表示方法およびプログラム
CN110162758A (zh) * 2019-05-21 2019-08-23 北京字节跳动网络技术有限公司 在线文档插入信息方法及装置
CN113407092A (zh) * 2021-06-17 2021-09-17 北京达佳互联信息技术有限公司 一种文本框信息处理方法、装置、电子设备及存储介质

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS63121971A (ja) 1986-11-11 1988-05-26 Fujitsu Ltd オブジエクト選択範囲再変換処理方式
JPH09190436A (ja) * 1996-01-12 1997-07-22 Toshiba Corp 情報処理装置及び範囲指定方法
US20060288297A1 (en) * 1999-08-12 2006-12-21 Robert Haitani System, method and technique for enabling users to interact and edit address fields of messaging applications
US8510668B1 (en) * 2000-04-03 2013-08-13 Google Inc. Indicating potential focus in a user interface
US6629793B1 (en) * 2002-04-26 2003-10-07 Westie Intellectual Properties Limited Partnership Emoticon keyboard
US7346660B2 (en) * 2003-02-21 2008-03-18 Hewlett-Packard Development Company, L.P. Method and system for managing and retrieving data
US7188316B2 (en) * 2003-03-24 2007-03-06 Microsoft Corporation System and method for viewing and editing multi-value properties
US20040234315A1 (en) * 2003-05-20 2004-11-25 Colwell Steven Lee Method and computer-readable medium for faster data entry
US7451397B2 (en) * 2004-12-15 2008-11-11 Microsoft Corporation System and method for automatically completing spreadsheet formulas
US9286935B1 (en) * 2007-01-29 2016-03-15 Start Project, LLC Simplified data entry
JP2008250708A (ja) * 2007-03-30 2008-10-16 Sanyo Electric Co Ltd 入力文字列予測装置および入力文字列予測プログラム
JP2007193849A (ja) 2007-04-25 2007-08-02 Microsoft Corp かな漢字変換システムおよび方法
US20090089690A1 (en) 2007-09-28 2009-04-02 Yahoo! Inc. System and method for improved tag entry for a content item
JP2009190436A (ja) 2008-02-12 2009-08-27 Toyota Motor Corp 車両の制御装置
US9098479B2 (en) * 2008-02-15 2015-08-04 Edyt Inc. Methods and apparatus for improved navigation among controlled terms in one or more user documents
US10867123B2 (en) 2009-11-09 2020-12-15 Microsoft Technology Licensing, Llc Social browsing
US20090271374A1 (en) 2008-04-29 2009-10-29 Microsoft Corporation Social network powered query refinement and recommendations
US8294680B2 (en) * 2009-03-27 2012-10-23 Sony Mobile Communications Ab System and method for touch-based text entry
US8230336B2 (en) 2009-04-22 2012-07-24 Microsoft Corporation Efficient discovery, display, and autocompletion of links to wiki resources
US20110004692A1 (en) * 2009-07-01 2011-01-06 Tom Occhino Gathering Information about Connections in a Social Networking Service
US20110041177A1 (en) * 2009-08-14 2011-02-17 Microsoft Corporation Context-sensitive input user interface
US9317116B2 (en) * 2009-09-09 2016-04-19 Immersion Corporation Systems and methods for haptically-enhanced text interfaces
JP2011138305A (ja) 2009-12-28 2011-07-14 Fujitsu Ltd 文字入力装置、文字入力方法及びそのプログラム
JP5471457B2 (ja) * 2010-01-07 2014-04-16 富士通モバイルコミュニケーションズ株式会社 情報処理装置
US8782556B2 (en) * 2010-02-12 2014-07-15 Microsoft Corporation User-centric soft keyboard predictive technologies
US20110209040A1 (en) * 2010-02-24 2011-08-25 Microsoft Corporation Explicit and non-explicit links in document
US8704783B2 (en) * 2010-03-24 2014-04-22 Microsoft Corporation Easy word selection and selection ahead of finger
US8782080B2 (en) * 2010-04-19 2014-07-15 Facebook, Inc. Detecting social graph elements for structured search queries
US20120110493A1 (en) 2010-10-27 2012-05-03 Honda Motor Co., Ltd. Text entry using a steering wheel in a vehicle
AU2012211130B2 (en) * 2011-01-27 2015-11-26 Google Llc Content access control in social network
US9519476B2 (en) 2011-03-29 2016-12-13 Hewlett Packard Enterprise Development Lp Methods, apparatus and articles of manufacture to autocomplete application lifecycle management entities
US9141707B2 (en) * 2012-07-19 2015-09-22 Facebook, Inc. Context-based object retrieval in a social networking system
US9424249B1 (en) * 2012-09-18 2016-08-23 Amazon Technologies, Inc. Encoding text units
US9836179B2 (en) 2012-12-20 2017-12-05 Microsoft Technology Licensing, Llc Auto-complete with persisted atomically linked entities

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US9836179B2 (en) 2017-12-05
JP6320420B2 (ja) 2018-05-09
US20180150160A1 (en) 2018-05-31
CN110096700B (zh) 2023-07-04
US20140181692A1 (en) 2014-06-26
US11455069B2 (en) 2022-09-27
CN105051722A (zh) 2015-11-11
EP2936340A2 (fr) 2015-10-28
KR102143258B1 (ko) 2020-08-10
JP6514388B2 (ja) 2019-05-15
WO2014100414A2 (fr) 2014-06-26
KR20150100679A (ko) 2015-09-02
WO2014100414A3 (fr) 2014-08-14
JP2018129076A (ja) 2018-08-16
AR094186A1 (es) 2015-07-15
CN105051722B (zh) 2019-05-03
TW201433967A (zh) 2014-09-01
CN110096700A (zh) 2019-08-06
JP2016503207A (ja) 2016-02-01

Similar Documents

Publication Publication Date Title
US11455069B2 (en) Auto-complete with persisted atomically linked entities
US8756500B2 (en) Dynamic content feed filtering
KR102122104B1 (ko) 웹 애플리케이션에서의 협업 통신 기법
US10394440B2 (en) Drag and drop always sum formulas
US10565301B2 (en) Stateful editing of rich content using a basic text box
US9696810B2 (en) Managing ink content in structured formats
US20150074127A1 (en) Creating Visualizations from Data in Electronic Documents

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: 20150617

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190705

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013063686

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0017270000

Ipc: G06F0040200000

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1210279

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191215

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013063686

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191204

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: 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: 20191204

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: 20191204

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: 20191204

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: 20200304

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: 20200305

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: 20200304

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: 20191204

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

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: 20191204

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: 20191204

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: 20191204

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

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: 20191204

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: 20191204

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: 20191204

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: 20200429

Ref country code: NL

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: 20191204

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: 20191204

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191231

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: 20191204

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: 20200404

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: 20191204

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013063686

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1210279

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191204

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: 20191204

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: LU

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

Effective date: 20191219

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: 20191204

Ref country code: IE

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

Effective date: 20191219

26N No opposition filed

Effective date: 20200907

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

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: 20191204

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: 20191204

Ref country code: CH

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

Effective date: 20191231

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: 20191204

Ref country code: BE

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

Effective date: 20191231

Ref country code: LI

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

Effective date: 20191231

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

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: 20191204

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: 20191204

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191204

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: 20131219

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: 20191204

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191204

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230505

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

Ref country code: GB

Payment date: 20231121

Year of fee payment: 11

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

Ref country code: FR

Payment date: 20231122

Year of fee payment: 11

Ref country code: DE

Payment date: 20231121

Year of fee payment: 11