Sign In to Follow Application
View All Documents & Correspondence

Shared Space For Communicating Information

Abstract: ABSTRACT SHARED SPACE FOR COMMUNICATING INFORMATION Embodiments provide a shared space for communicating information. In an embodiment a number of users associated with a computing environment can use a shared space to communicate information with one another. Each computing device of the computing environment can include a shared space appHcation. The shared space application includes a number of interactive tools that can be used to persist various communications between associated computing devices of a computing environment.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
22 May 2009
Publication Number
34/2009
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2019-09-12
Renewal Date

Applicants

MICROSOFT CORPORATION
ONE MICROSOFT WAY, REDMOND, WASHINGTON 98052-6399

Inventors

1. SANCHEZ, RUSSELL
C/O MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND, WA 98052-6399
2. COLANDO,CHRISTIAN
C/O MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND, WA 98052-6399
3. OHTA, SEIYA
C/O MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND, WA 98052-6399

Specification

BACKGROUND 10001) People try to communicate and stay connected using a number of communication methods, such as: postal mail, phones, digital photos, whiteboards, e-mail, and instant messaging (IM) applications. However, each technique has associated limitations and can result in an unsatisfactory experience for the user. For example, instant messages, networked digital picture frames, and e-mail can be untimely and constrain the amount of information that can be communicated. Some communication methods, like phone and IM communications, can be intrusive by forcing a party to respond in real-time. Passive communication methods, like email, and postal mail communications allow for delayed responses, but are typically less intrusive since a party can wait to respond. However, passive methods can be impersonal and deficient in emotional expressiveness because they impose a turn taking statement/reply/statement/reply communications structure (e.g. e-mail and instant messaging). [0002] Other communication methods lack fidelity, variety of expressiveness, or are limited to providing information in temporary sessions (e.g. instant messaging, virtual whiteboards). Once the session ends, the information is lost. For example, whiteboards are often used as a medium to communicate spontaneous handwritten ideas and concepts. However, information displayed on the whiteboard is not ideal for remote interaction and collaboration. It can be difficult for remote users to read and focus upon relevant portions of a whiteboard, due in part to the limitations associated with video teleconferencing equipment. For example, ink strokes written on a whiteboard can be hard to see, and cannot be erased or edited by remote users. Thus, real-time multi-user physical whiteboard collaboration is limited and generally an unsatisfactory experience for the remote participant. SUMMARY |0003] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter. [0004] Embodiments provide a "shared space" for communicating information. The shared space can be configured to allow a number of users to communicate by using the shared space. In an embodiment, a shared space application is configured to provide a persistent space that can be shared for interaction by two or more users. A user can have a number of separate spaces to share and communicate with other individuals and/or groups. In various embodiments, the shared space can be interacted with and populated using a flexible aggregation of simple communication tools for sharing and communicating a variety of information. The communication tools and the shared space provide users with a persistent means to naturally and conveniently interact and communicate. [0005] These and other features and advantages will be apparent from a reading of the foliowing detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of the invention as claimed. BRIEF DESCRIPTION OF THE DRAWINGS [0006] FIGURE 1 is a block diagram of a computing environment. |0007| FIGURE 2 is a block diagram of a computing environment. [0008) FIGURE 3 is a block diagram of a shared space architecture. [0009] FIGURE 4 is a flowchart illustrating using a shared space. (0010] FIGURES 5A-5K illustrate a user interface for interacting with a shared space. [0011| FIGURE 6 is a block diagram illustrating a computing environment for implementation of various embodiments described herein. DETAILED DESCRIPTION [00121 Embodiments provide a shared spaced, wherein a number of users can use the shared space to communicate information. The shared space can be configured to allow a number of users to communicate by using the shared space. In an embodiment a shared space application is configured to provide a persistent space that can be shared and used by two or more users to communicate using various tools. A display of a computing device can be used to present a shared space to users who are using the shared space application to share such a space. The users can use the various tools provided by the shared space application to interact with the shared space in real-time or at their convenience. [0013] In one embodiment, a plurality of shared spaces can be presented on one or more displays, thereby allowing a user to concurrently interact with various individuals and/or groups. That is, a user can have separate spaces to keep in touch and communicate with different individuals and/or groups. In various embodiments, the shared space can be populated using a flexible aggregation of simple communication tools that allow for the sharing of a variety of information. For example, the communication tools can be used by a user to populate a shared space with imagery, text, audio, handwritten drawings and words (e.g. digital ink), and/or other data. The communication tools are configured to afford natural and convenient communication and interaction, [0014] In an embodiment, a shared space is persistent and remains available to an associated participant at all times, even when a participant is not using the space and/or signed in (e.g. offline). A user can invite one or more participants to share one or more spaces, A participant of a shared space can add to, delete from, and/or otherwise modify the space. Thereafter, all participants of the shared space see or will see the same result of the interaction. The shared space application is configured to allow a participant to save content to a private scrapbook, since the nature of the shared space can be highly transitory. Moreover, the shared space application is configured to use shared and private data, but is not so limited. In one embodiment, the shared space application is further configured to enable a "live connection." The live connection enables a number of participants to engage in live audio and/or video communication using the shared space application. [0015] FIGURE 1 is a block diagram of a computing environment 100, under an embodiment. The computing environment 100 can be described as a network of components wherein the associated components are communicatively coupled in such a manner to provide an operational fiinctionality. A number of computing devices 102-106 are in communication with one another to provide a network of computing devices. The number if computing devices 102-106 also can be in communication with a serving computing device 107. Each computing device 102-107 includes networking and security components configured to provide communication functionality between the computing devices 102-107. The computing devices 102-106 can include desktop computers, laptop computers, tablet computers, handheld devices, and other communication devices. |0016| As shown in FIGURE 1, each computing device 102-106 includes a shared space application 108-112, described further below. The serving computing device 107 includes a space manager component 114, but is not so limited. The space manager component 114 can be configured and operated to manage aspects of one or more shared spaces, but is not so limited. For example, the space manager component 114 can maintain a read-write master data file that is associated with a shared space. In an embodiment, each shared space application 108-112 and the space manager component 114 comprise software applications that execute in conjunction with processors of computing devices 102-107. As described below, each shared space application 108-112 is configured to provide a persistent space to a number of users that are associated with the shared space, In order to streamline the discussion below, the computing device 102 and associated shared space application 108 are referred to when describing the functionality and use of the shared space appUcation. [0017] As described below, a user can use the computing device 102 and associated shared space application 108 to communicate and interact with other users of a shared space. The shared space can be described as a persistent canvas or interactive window that can be used by two or more users to communicate in a variety of ways. That is, the shared space application 108 is configured to persist user interactions, including various expressions, for an associated shared space. Correspondingly, the user interactions are seen by all users associated with the shared space, regardless of their physical location. In various embodiments, anything that is created, placed, or otherwise located (ink, video files, audio files, text, pictures, etc.) in a shared space is persisted in the shared space until deleted or otherwise modified. [00181 A user can use the shared space application 108 to interact with a number of separate spaces and/or users. For example, a user can use the shared space application 108 to create a number of shared spaces which enable the user to keep in touch with various individuals and/or groups. A user's interaction with a shared space is termed an expression. The shared space application 108 is configured to persist an expression in the shared space until the expression is deleted or otherwise modified by a user associated with the shared space. For example, if a user draws a picture or posts a photo in a shared space, the items remain in the shared space, even if they are covered by other items. |0019] The shared space application 108 can be installed on the computing device 102. For example, the shared space application 108 can be installed as part of an operating system (OS) installation process. As described above, a user can use the shared space application 108 to communicate v«th one or more users or participants of a shared space. Additionally, the communication of a shared space can be provided to a number of associated computing devices. The communication of a shared space to a plurality of computing devices makes collaboration and interaction a pleasurable experience, even for users in remote locations. Thus, the shared space application 108 provides a convenient medium for communicative interaction to businesses, families, friends and others, |0020| For example, the communication of a shared space can be provided to a number of ultra-mobile computing devices and associated users communicating over a network, such as the Internet. In one embodiment, the communication of the shared space is provided over the Internet using an online file storage service. In another embodiment, the communication of the shared space is provided to a number of computing devices using a peer-to-peer service, such as a peer-to-peer synchronization service for example. (0021) The communication of the shared space can be provided to the computing devices 102-107 of a computing network, such as wireless local area network (WLAN), local area network (LAN), wide-area network (WAN), combinations thereof, and/or some other type of computing and/or communication network. In one embodiment, the computing environment 100 is a distributed computer network that allows one or more computing devices, communication devices, databases, etc., to communicate according to a desired implementation. |0022I The components of the computing environment 100 can be communicatively coupled to one another using wired, wireless, combii\ations of wired and wireless, and other communication techniques. The communication of a shared space can also include combinations of various communication methods. Other embodiments that communicate a shared space include file/folder sharing methodologies and/or synchronization schemes. For example, a file/folder sharing program such as FOLDERSHARE can be used to communicate a shared space and the associated displayed content. [0023] In an embodiment, a shared space application 108 is configured to operate on, persist, and/or display the content(s) of a master file, such as a read-only copy of a master file for example. The master file can be updated when the shared space is modified or otherwise changed. That is, the shared space application uses the master file to track and maintain changes to the shared space. In one embodiment, a master file is associated with each shared space. Each computing device 102-106 can use the master file to display the content(s) of the shared space, including recent changes and modifications to the shared space. (00241 In one embodiment, each computing device 102-106 is associated with a peer-to-peer network and uses a master file that is associated with a shared space. When a computing device 102-106 associated with a shared space is cormected and online, the master data file changes state fi-om a read-only state to a read-write state. Thereafter, the local master data files are synchronized in real-time as additions, delefions, and other changes are made to the associated shared space. When a computing device disconnects (e.g. the user is offline), the local master data file is reconfigured to read-only. Thereafter, the next time a user logs in to a shared space and the shared space application 108 cormects to the read-write master file, the read-write master file is copied over (e.g. replaces) the local read-only master file so that the master file is updated with all the additions and changes that occuned while the user was disconnected. (00251 Accordingly, as updates to the shared space occur, each master file is updated and/or synchronized with the other associated master files for the shared space. Thus, the shared space application 108 operates to ensure that users who are currently in commimication (e.g. connected and/or signed on) with one another see the same information. The shared space application 108 is configured to modify the master file and communication of the shared space is provided by using the master file when a user is in communication with another participant and associated master file. For example, the communication of the shared space can be provided when a user has network connectivity to an associated master file through an online storage service and/or directly to other associated computing devices (e.g. peer-to-peer). [00261 As described above, the shared space application 108 can be configured to maintain a read-only copy of a latest version the master file in local storage of an associated computing device. If a user is offline, the shared space application 108 does not provide access to the read-only master file. However, the user can view the read-only copy of the master file, but cannot make changes to the master file. As described below, the user can also save one or more expressions stored in the read-only master file to a scrapbook. If another user changes the master file associated with a shared space while a user is offline, the offline user will not see the changes until they log back in to the associated shared space. Thus, a user must be logged into a shared space so that the shared space application 108 can access and use the read-write master file to update the shared space with any changes since the user has been offline. [00271 As an example, suppose user A and user B have a shared space. User A is online. When user A opens the shared space, the shared space application accesses the master file. As one example, the shared space application can access the master file from a virtual hard drive. Then, user A adds a picture to the shared space. The shared space application adds the picture to the master file and the local read-only file of user A. User B is offline, and opens the shared space, which shows that user B is offline. User B carmot see the picture that user A just added. Thereafter, user B goes online, such as be connecting to the Internet. Once user B goes online, the shared space application accesses and reads the master file, and updates the local read-only file on user B's machine. Now user B sees the picture added by user A to the shared space. [0028| In one embodiment, the read-write master file is stored and maintained on the serving computing device 107. Thus, a user associated with a shared space needs to have network coimectivity and be online to make changes to the shared space and associated read- write master file. In other embodiments, the master file can be stored and maintained using a web service, on a peer machine, and/or on the user's computing device. The master file can then be copied to all participants associated with a shared space when they are communicating. In an alternative embodiment, a user can make additions and/or changes to their local file at any time. Thereafter, when each participant re-connects to a shared space (e.g. logs in) or to another participant (e.g. peer-to-peer), a synchronization operates to aggregate all off-line changes made by each participant so that each participant "sees" the same space. [0029| FIGURE 2 is a block diagram of a computing environment 200, under an embodiment. The computing environment 200 includes a computing device 202 in communication with a serving computing device 204. The components of the computing environment 200 can be communicatively coupled to one another using wired, wireless, combinations of wired and wireless, and other communication and networking techniques. While one computing device 202 and one serving computing device 204 are shown, other embodiments can include a plurality of such computing and serving computing devices. In one embodiment, a shared space can be created and defined between at least two users using two computing devices, such as ultra-mobile computing devices for example. [00301 As shown in FIGURE 2, the computing device 202 includes a shared space application 206. The shared space application 206 is configured to provide a persistent space that can be shared for interaction by a number of users. According to this embodiment, the shared space application 206 includes a number of associated components that are used to maintain a space. The shared space application 206 includes, but is not limited to: a launch component 208; an authenticating component 210; a contacts component 212; a canvas dispatch component 214; a media recorder component 216; a fi-ame capture component 218; a history/scrapbook manager component 220; a space manager component 222; a content object creator component 224; data synchronizer component 226; a file creator component 228; a response/request handler component 230; and, a space canvas component 232. In alternative embodiments, the functionality and operation of the various components can be combined to provide fewer components and/or a desired implementation. [0031| The launch component 208 can be configured as a user interface and operated to provide user authentication, space selection, and/or participant selection. The authenficating component 210 can be configured and operated as an authenticating service, such as a PASSPORT service for example. The contacts component 212 can be configured and operated to locate and/or maintain a user contact list. For example, the contacts component 212 can be configured to connect to a MSN service to expose a user's MSN contact list as participants for shared spaces. The canvas dispatch component 214 can be configured and operated to create a new space canvas and display objects in a space.' The media recorder component 216 can be configured and operated to record audio, images, video, and other objects/expressions. For example the media recorder component 216 can use a local camera, microphone, and/or other components to record images, audio and video as expressions in a space. (0032) With continuing reference to FIGURE 2, the frame capture component 218 can be configLired and operated to capture "snapshot" images of a space for the history and/or scrapbook. The history/scrapbook manager component 220 can be configured and operated to manage a chronological collection of "snapshots" of a space and to provide the user a mechanism to review and/or store selected expressions in a private local repository referred to as a scrapbook. The history/scrapbook manager component 220 can record every event occurring in a space. Accordingly, a user does not have to continually use save operations, which allow for a more informal interaction with the space. The space manager component 222 can be configured and operated to manage aspects of a space. For example, the space manager component 222 can be configured and operated to manage a local copy of a master file. The content object creator component 224 can be configured and operated to manage objects and other expressions in a space. For example, the content object creator component 224 can be configured and operated to manage images, ink, text, and/or other user expressions. (0033| The data synchronizer component 226 can be configured and operated to synchronize data files between a user computing device 202 and a serving computing device 204. For example, the data synchronizer component 226 can be configured and operated to synchronize master data files between the user computing device 202 and serving computing device. The file creator component 228 can be configured and operated to manage shared space data files, including, but not limited to: creating, opening, and saving shared space data files. The response/request handler component 230 can be configtu-ed and operated to manage communication between computing devices. For example, the response/request handler component 230 can be configured and operated to manage communication between the computing device 202 and the serving computing device 204. The space canvas component 232 can be configured and operated as a user interface to enable user interaction with a space. [0034] In accordance with this embodiment, the serving computing device 204 includes a number of shared space components. As shown in FIGURE 2, the serving computing device 204 includes, but is not limited to: a data synchronizer component 234; a response/request handler component 236; and, a space manager component 238. The data synchronizer component 234 can be configured and operated to synchronize data files between the serving computing device 202 and one or more user computing devices. For example, data synchronizer component 234 can be configured and operated to synchronize master data files between the serving computing device 204 and user computing device 202. The response/request handler component 236 can be configured and operated to manage communication between the serving computing device and one or more other computing devices, including other serving computing devices. The space manager component 238 can be configured and operated to manage aspects of a space. For example, the space manager component 238 can be configured and operated to manage a read-write master copy of a master file. Other embodiments are available. [0035| The shared space application 206 is configured to use and provide various objects in a shared space. In one embodiment, the shared space application 206 uses and provides: participant indicators (e.g. icon, digital image, etc.) that represent other users who are sharing a space; expressions in the space (e.g. ink, text, photos, video, live connections, etc); and, a number of interactive tools. For example, an icon (e.g. default person/group icon) or a digital image can be used to represent an individual or group that is sharing a space. A digital image or photo can be imported or dropped using the contacts component 212 along with a name associated with individual or group name. The contacts component 212 can be configured to propagate name/photo updates/changes to the shared space application 206. An individual participant indicator can include an indication of a participant status or state (e.g. present, occupied, not present, etc). A group participant indicator can also include a count of participants in each state (4 of 12 present, etc). When a user taps a participant indicator, a live cormection is established (e.g. audio and/or video depending on available device hardware and service features), as described below. |0036] Expressions include any participant created item in a space including ink, images, text, video, live connections, etc. For example, a participant can use a tablet pen to draw a picture or write some text. The user can also use a finger and a touchscreen to ink in a space for example. In an embodiment, an expression can include three states: normal, focus, and magnify, but is not so limited. In the normal expression state, new expressions appear on top of old expressions (except for live connections which always appear on top). Previously kept live connections can be represented by a live connection indicator, such as a live connection icon for example. Text expressions can be scrolled by touching in the text area and dragging up/down, Giving focus to an expression (or group of expressions) in a shared space operates to display a marquee around the item. |0037| Table 1 below lists a number of expressions and how each expression receives focus. Table I Expression Gets focus when tanped from... Ink Select Tool Image Select Tool Video Select Tool Audio (music) Select Tool Text Select Tool Text Tool Live Connection Icon Select Tool Group of Expressions Select Tool [00381 In the focus state, individual expressions (individual select) or group of expressions (group select) can have focus. When an expression (or group of expressions) has focus, it is temporarily displayed on top of other expressions, including a surrounding marquee, magnify button, and move grip. Losing focus returns the expression (or group) to its former position in view order. A user can drag the marquee to move (e.g. drag from center, or move grip), resize the expression (e.g. drag from edges and comers), and rotate (e.g. drag move grip or rotation handle). 10039] In one embodiment, any change to an expression (e.g. move, resize, rotate) operates to move the changed expression to the top of view order. Changing focus to an expression without making any changes to the expression operates to return the expression to its former position in view order. The user can clear focus by tapping a blank area of a shared space or selecting another expression. Expressions that are pasted to a shared space are automatically given focus. 10040] A user can tap the magnify button which operates to change the expression view to the magnify state. In the magnify state, the expression is magnified to encompass a substantial portion of a display (tools remain visible). An expression cannot be moved. resized, or rotated in the magnify state. A user can tap the close button which operates to return the expression to the focus state. |004l| Table 2 below lists a number of contextual controls and information associated with various expressions. Table 2 Expression Controls Info TMeta-datal Ink Close Save copy in Scrapbook Delete Timestamp Author (>2 Participants only) Image Close Save copy in Scrapbook Delete Crop (Tool) Timestamp Author (>2 Participants only) Size Location (if recorded) Video Close Save copy in Scrapbook Delete Crop Timestamp Author (>2 Participants only) Size Location (if recorded) Audio (music) Close Save copy in Scrapbook Delete Crop Timestamp Author (>2 Participants only) Size Text Close Save copy in Scrapbook Delete Timestamp (sub-statements within Expression) Author (sub-statements within Expression) Live Connection Close Save copy in Scrapbook Delete Play Stop Pause Rewind Fast Forward Participant(s) Timestamp Size Duration Current position in recording Group of Expressions Close Save copy in Scrapbook Delete Aggregate Size |0042) The tools of the shared space application are configured to facilitate the sharing of photos, video, audio, ink, text, and other user expressions. The tools can be used to create, select, modify and save expressions. In one embodiment, the tools are provided via the space canvas component 232 and are configured as a number of buttons (e.g. touchscreen buttons, tablet buttons, icons, etc.). The button types include, but are not limited to: a toolset tray button: expands/collapses toolset tray; a toolset button that selects a tool and then collapses the toolset tray; a tool button that activates control (for modal burtons) or expands/collapses a palette (for palettes); and a palette button that selects item/mode/choice from a palette and closes the palette. The appearance of a tool button can change to reflect current paiette selection. 10043) Table 3 below lists each toolset, tools, and palettes, under an embodiment. Table 3 Toolset Tool Palette Ink Pen (default) Magnify pen Ink thickness Tliickness Palette Ink color Color Palette Stroke Eraser Get stuff from... My Pictures (default) My Videos My Music Scrapbook History Text Text (default) Style Style Palette Size Size Palette Color Color Palette Font Font Palette Select Individual select (default) Group select (bounded Expressions) Copy Paste Undo Scrapbook [0044] The shared space application 206 and associated tools allow a participant to interact with a space and locate expressions wherever desired in the space. Moreover, space participants are free to interact with a space ai their convenience. There is no rigid communication requirement or protocol {e.g. User 1 communication followed by User 2 communication followed by User 3 communication, etc.), [0045] As described above, the shared space application 206 is configured to provide a live connection between participants of a shared space. In an embodiment, a live connection is configured to behave as an expression with a few exceptions, A live connection can be used to engage in (and store) live audio/video conversation (e.g. like a video conference), or to record a message for another participant (e.g. like voicemail or videomail). In either case, the methods and controls are the same. When a live connection is opened by tapping a participant icon, the user is prompted to select a type of Uve connection. The type of live connection depends on a type of service subscription. [0046] Table 4 below lists the subscription types for live connections of an embodiment. Table 4 Subscription Type Live Connection with a Participant Live Connection with Group or muUiple P^uticipants Basic Audio Video Record audio and leave as a message in shared space. Record video and leave as a message in shared space. Premium Audio Video Combined audio. Separate video stream for each participant. 10047] The live connection is configured to provide local ("me") and remote ("you") views. In a Group live connection, there is a "you" view for each member of the group. While a live connection is open, a number of controls and information is provided. Duration information is provided to show the duration (e.g. minute:seconds) of a live connection. A mute button is provided (for both audio and video) which operates to mute a device microphone and camera so that others cannot hear or see you. A close button, which when t^ped, operates to prompt the user to select either "Cancel", "Keep" or "Erase". Selecting cancel returns to the live connection as if the close button had not been tapped. Selecting keep places the live connection in the associated space, and is represemed by a live connection icon. Selecting erase discards a buffered live connection. 10048] The shared space application 206 is also configured to provide a scrapbook using the history/scrapbook manager component 220. The scrapbook provides a convenient private storage for expressions and space snapshots. The scrapbook can be opened by tapping a scrapbook tool. The scrapbook is configured to provide multiple views (e.g. list, icon, thumbnail, etc.) and grouping/sorting (e.g. by participant, by date, by expression type, by location, etc). The scrapbook also includes a search/filter tool for locating expressions and other items in the scrapbook. 10049] Any expression or space snapshot can be stored in the scrapbook. The scrapbook includes a "Save Space" button which operates to save a snapshot copy of a current space into the scrapbook in image form. Contents of the scrapbook are stored in a folder named "My Scrapbook" in the operating filesystem, "My Scrapbook" is a peer to "My Pictures", "My Notebook", and "My Music". The "My Scrapbook" folder can be created when the Shared Space application is installed. Expressions in scrapbook have the same three states (Normal, Focus, Magnity) and all the same respective controls and behaviors as they do in a space except the following controls are changed/added; Move, Resize, Rotate are not available; "Save copy to Scrapbook" is replaced with "Copy to Space"; "Prinf button prints an expression or a space snapshot. [0050] The "Get Stuff toolset is configured to provide a convenient way to browse and import items from the operating file system into a space. The "Get Stuff" toolset can be used to browse and import items from various folders, such as My Pictures, My Videos and My Music for example. Tapping the "My

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 2868-CHENP-2009 FORM-3 23-11-2009.pdf 2009-11-23
1 2868-CHENP-2009-RELEVANT DOCUMENTS [15-09-2023(online)].pdf 2023-09-15
2 2868-CHENP-2009 FORM-18 20-10-2010.pdf 2010-10-20
2 2868-CHENP-2009-RELEVANT DOCUMENTS [26-09-2022(online)].pdf 2022-09-26
3 2868-CHENP-2009-RELEVANT DOCUMENTS [22-09-2021(online)].pdf 2021-09-22
3 2868-chenp-2009 form-5.pdf 2011-09-04
4 2868-CHENP-2009-RELEVANT DOCUMENTS [27-03-2020(online)].pdf 2020-03-27
4 2868-chenp-2009 form-3.pdf 2011-09-04
5 2868-CHENP-2009-IntimationOfGrant12-09-2019.pdf 2019-09-12
5 2868-chenp-2009 form-1.pdf 2011-09-04
6 2868-CHENP-2009-PatentCertificate12-09-2019.pdf 2019-09-12
6 2868-chenp-2009 drawings.pdf 2011-09-04
7 Abstract_Granted 320288_12-09-2019.pdf 2019-09-12
7 2868-chenp-2009 description(complete).pdf 2011-09-04
8 Claims_Granted 320288_12-09-2019.pdf 2019-09-12
8 2868-chenp-2009 correspondance others.pdf 2011-09-04
9 2868-chenp-2009 claims.pdf 2011-09-04
9 Description_Granted 320288_12-09-2019.pdf 2019-09-12
10 2868-chenp-2009 abstract.pdf 2011-09-04
10 Drawings_Granted 320288_12-09-2019.pdf 2019-09-12
11 2867-chenp-2009 form-5.pdf 2011-09-04
11 Marked up Claims_Granted 320288_12-09-2019.pdf 2019-09-12
12 2867-chenp-2009 form-3.pdf 2011-09-04
12 2868-CHENP-2009-Written submissions and relevant documents (MANDATORY) [22-08-2019(online)].pdf 2019-08-22
13 2867-chenp-2009 form-1.pdf 2011-09-04
13 2868-CHENP-2009-FORM 3 [21-08-2019(online)].pdf 2019-08-21
14 2867-chenp-2009 drawings.pdf 2011-09-04
14 2868-CHENP-2009-PETITION UNDER RULE 137 [21-08-2019(online)].pdf 2019-08-21
15 2867-chenp-2009 description(complete).pdf 2011-09-04
15 2868-CHENP-2009-HearingNoticeLetter07-08-2019.pdf 2019-08-07
16 2867-chenp-2009 correspondance others.pdf 2011-09-04
16 2868-CHENP-2009-Correspondence to notify the Controller (Mandatory) [23-07-2019(online)].pdf 2019-07-23
17 2868-CHENP-2009-ABSTRACT [21-08-2017(online)].pdf 2017-08-21
17 2867-chenp-2009 claims.pdf 2011-09-04
18 2867-chenp-2009 abstract.pdf 2011-09-04
18 2868-CHENP-2009-CLAIMS [21-08-2017(online)].pdf 2017-08-21
19 2868-CHENP-2009 FORM-6 26-02-2015.pdf 2015-02-26
19 2868-CHENP-2009-COMPLETE SPECIFICATION [21-08-2017(online)].pdf 2017-08-21
20 2868-CHENP-2009-CORRESPONDENCE [21-08-2017(online)].pdf 2017-08-21
20 MTL-GPOA - JAYA.pdf 2015-03-13
21 2868-CHENP-2009-FER_SER_REPLY [21-08-2017(online)].pdf 2017-08-21
21 MS to MTL Assignment.pdf 2015-03-13
22 2868-CHENP-2009-OTHERS [21-08-2017(online)].pdf 2017-08-21
22 FORM-6-1201-1300(JAYA).9.pdf 2015-03-13
23 2868-CHENP-2009-FER.pdf 2017-02-27
24 FORM-6-1201-1300(JAYA).9.pdf 2015-03-13
24 2868-CHENP-2009-OTHERS [21-08-2017(online)].pdf 2017-08-21
25 MS to MTL Assignment.pdf 2015-03-13
25 2868-CHENP-2009-FER_SER_REPLY [21-08-2017(online)].pdf 2017-08-21
26 2868-CHENP-2009-CORRESPONDENCE [21-08-2017(online)].pdf 2017-08-21
26 MTL-GPOA - JAYA.pdf 2015-03-13
27 2868-CHENP-2009 FORM-6 26-02-2015.pdf 2015-02-26
27 2868-CHENP-2009-COMPLETE SPECIFICATION [21-08-2017(online)].pdf 2017-08-21
28 2867-chenp-2009 abstract.pdf 2011-09-04
28 2868-CHENP-2009-CLAIMS [21-08-2017(online)].pdf 2017-08-21
29 2867-chenp-2009 claims.pdf 2011-09-04
29 2868-CHENP-2009-ABSTRACT [21-08-2017(online)].pdf 2017-08-21
30 2867-chenp-2009 correspondance others.pdf 2011-09-04
30 2868-CHENP-2009-Correspondence to notify the Controller (Mandatory) [23-07-2019(online)].pdf 2019-07-23
31 2867-chenp-2009 description(complete).pdf 2011-09-04
31 2868-CHENP-2009-HearingNoticeLetter07-08-2019.pdf 2019-08-07
32 2867-chenp-2009 drawings.pdf 2011-09-04
32 2868-CHENP-2009-PETITION UNDER RULE 137 [21-08-2019(online)].pdf 2019-08-21
33 2867-chenp-2009 form-1.pdf 2011-09-04
33 2868-CHENP-2009-FORM 3 [21-08-2019(online)].pdf 2019-08-21
34 2867-chenp-2009 form-3.pdf 2011-09-04
34 2868-CHENP-2009-Written submissions and relevant documents (MANDATORY) [22-08-2019(online)].pdf 2019-08-22
35 2867-chenp-2009 form-5.pdf 2011-09-04
35 Marked up Claims_Granted 320288_12-09-2019.pdf 2019-09-12
36 Drawings_Granted 320288_12-09-2019.pdf 2019-09-12
36 2868-chenp-2009 abstract.pdf 2011-09-04
37 2868-chenp-2009 claims.pdf 2011-09-04
37 Description_Granted 320288_12-09-2019.pdf 2019-09-12
38 2868-chenp-2009 correspondance others.pdf 2011-09-04
38 Claims_Granted 320288_12-09-2019.pdf 2019-09-12
39 2868-chenp-2009 description(complete).pdf 2011-09-04
39 Abstract_Granted 320288_12-09-2019.pdf 2019-09-12
40 2868-chenp-2009 drawings.pdf 2011-09-04
40 2868-CHENP-2009-PatentCertificate12-09-2019.pdf 2019-09-12
41 2868-chenp-2009 form-1.pdf 2011-09-04
41 2868-CHENP-2009-IntimationOfGrant12-09-2019.pdf 2019-09-12
42 2868-CHENP-2009-RELEVANT DOCUMENTS [27-03-2020(online)].pdf 2020-03-27
42 2868-chenp-2009 form-3.pdf 2011-09-04
43 2868-CHENP-2009-RELEVANT DOCUMENTS [22-09-2021(online)].pdf 2021-09-22
43 2868-chenp-2009 form-5.pdf 2011-09-04
44 2868-CHENP-2009-RELEVANT DOCUMENTS [26-09-2022(online)].pdf 2022-09-26
44 2868-CHENP-2009 FORM-18 20-10-2010.pdf 2010-10-20
45 2868-CHENP-2009-RELEVANT DOCUMENTS [15-09-2023(online)].pdf 2023-09-15
45 2868-CHENP-2009 FORM-3 23-11-2009.pdf 2009-11-23
46 2868-CHENP-2009-FORM-27 [10-09-2025(online)].pdf 2025-09-10

Search Strategy

1 searchstrategy_23-02-2017.pdf

ERegister / Renewals

3rd: 13 Nov 2019

From 30/10/2009 - To 30/10/2010

4th: 13 Nov 2019

From 30/10/2010 - To 30/10/2011

5th: 13 Nov 2019

From 30/10/2011 - To 30/10/2012

6th: 13 Nov 2019

From 30/10/2012 - To 30/10/2013

7th: 13 Nov 2019

From 30/10/2013 - To 30/10/2014

8th: 13 Nov 2019

From 30/10/2014 - To 30/10/2015

9th: 13 Nov 2019

From 30/10/2015 - To 30/10/2016

10th: 13 Nov 2019

From 30/10/2016 - To 30/10/2017

11th: 13 Nov 2019

From 30/10/2017 - To 30/10/2018

12th: 13 Nov 2019

From 30/10/2018 - To 30/10/2019

13th: 13 Nov 2019

From 30/10/2019 - To 30/10/2020

14th: 13 Nov 2019

From 30/10/2020 - To 30/10/2021

15th: 08 Sep 2021

From 30/10/2021 - To 30/10/2022

16th: 13 Sep 2022

From 30/10/2022 - To 30/10/2023

17th: 25 Oct 2023

From 30/10/2023 - To 30/10/2024