Patent Application
20180321807
This application claims priority to and the benefit of Indian Patent Application No. 201711016025, entitled “SYSTEM AND METHODS FOR TAILORED CONTENT PROVISION”, filed May 6, 2017, which is herein incorporated by reference in its entirety.
The present disclosure relates in general to systems, methods, and apparatuses for visualization features of a graphical-user-interface (GUI). More specifically, the present disclosure is related to systems and methods for generating and/or rendering content recommendations based upon observed interaction with guided tours and other documents facilitated by a remote instance for subsequent visualization at a client device.
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
Computer resources hosted in distributed computing (e.g., cloud-computing) environments may be disparately located with different resources potentially having their own functions, properties, and/or permissions. Such resources may include hardware resources (e.g. computing devices, switches, etc.) and software resources (e.g. database applications). These resources may be used to collect and store data at various times related to a variety of measurable properties, including network, hardware, or database performance properties measured at different times. As systems for collecting data become more readily available and the costs for storage hardware continue to decrease, the amount of data that these computer resources are capable of collecting is increasing. For instance, in addition to collecting raw data more frequently, metadata associated with the time in which the raw data has been generated or acquired may also be stored for a given data set.
Although the capabilities of computer resources for collecting and storing more data continues to expand, the vast amount of collected data has resulted in more-complex GUIs that provide a significant number of interactive objects. In particular, the magnitude of available data (and corresponding interactive GUI objects) may result in difficulties in understanding what each of the various objects represents, how they are intended to be interacted with, etc. While, documents, such as images and videos may demonstrate functions of the interactive objects, as the GUIs expand, it may be difficult to find particular relevant demonstrations.
A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.
Information Technology (IT) networks may include a number of computing devices, server systems, databases, and the like that generate, collect, and store information. Graphical-user-interfaces may provide interactive objects, which enable usage of this data. As GUIs become increasingly complex, it may be more difficult to discern certain characteristics of the GUIs' interactive objects.
With this in mind, an IT system may include a guided tour designer (GTD) that enables creation of a guided tour of certain features of a graphical-user-interface (GUI). The guided tour may provide insight into various interactive objects presented by the GUI, resulting in a clearer understanding of GUI and its interactive objects.
Guided tours and other documents (e.g., click-through demonstrations, images, and/or videos may be generated to illustrate certain features of the GUIs. However, to avoid inundation with a multitude of demonstrative content, a system may monitor interaction with the instance GUIs, to discern a focus of the interaction. For example, particular portions of the GUIs may be associated with meta-data. Interaction with these particular portions may be associated with the meta-data, and a focus of the interaction may be determined based upon the distribution of the meta-data. The discerned focus may be used to derive subsequent content recommendations/provision.
As will be discussed in more detail below, interactions may be weighted, proportioning a more significant portion of the distribution to certain sets of interactions over other interactions. This enables increased focus accuracy, resulting in better content recommendations/provision.
Various refinements of the features noted above may exist in relation to various aspects of the present disclosure. Further features may also be incorporated in these various aspects as well. These refinements and additional features may exist individually or in any combination. For instance, various features discussed below in relation to one or more of the illustrated embodiments may be incorporated into any of the above-described aspects of the present disclosure alone or in any combination. The brief summary presented above is intended only to familiarize the reader with certain aspects and contexts of embodiments of the present disclosure without limitation to the claimed subject matter.
The description herein makes reference to the accompanying drawings, wherein like reference numerals refer to like parts throughout the several views.
One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and enterprise-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
The following discussion relates to generation and presentation of guided tours and document views in an Information Technology (IT) monitoring and/or reporting system. However, this is not meant to limit the current techniques to IT systems. Indeed, the current techniques may be useful in a number of different contexts. For example the current techniques may be applied to Human Resources (HR) systems or any system that may benefit from guided tours and/or rendered document views.
Keeping this in mind, the discussion now turns to an Information Technology (IT)-centered example. IT devices are increasingly important in an electronics-driven world in which various electronics devices are interconnected within a distributed context. As more functions are performed by services using some form of distributed computing, the complexity of IT network management increases. As management complexities increase, GUIs for completing the complex management may increase. Further, when documents are retrieved via download, data inundation may result in significant depletion on client device storage resources. Further, document downloads may reduce data security by allowing local data manipulation of documents.
By way of introduction to the present concepts and to provide context for the examples discussed herein,
The cloud service 104 may include any suitable number of computing devices (e.g., computers) in one or more locations that are connected together using one or more networks. For instance, the cloud service 104 may include various computers acting as servers in datacenters at one or more geographic locations where the computers communicate using network and/or Internet connections. The communication channel 106 may include any suitable communication mechanism for electronic communication between the client 102 and the cloud service 104. The communication channel 106 may incorporate local area networks (LANs), wide area networks (WANs), virtual private networks (VPNs), cellular networks (e.g., long term evolution networks), and/or other network types for transferring data between the client 102 and the cloud service 104. For example, the communication channel 106 may include an Internet connection when the client 102 is not on a local network common with the cloud service 104. Additionally or alternatively, the communication channel 106 may include network connection sections when the client and the cloud service 104 are on different networks or entirely using network connections when the client 102 and the cloud service 104 share a common network. Although only a single client 102 is shown connected to the cloud service 104, it should be noted that cloud service 104 may connect to multiple clients (e.g., tens, hundreds, or thousands of clients).
Through the cloud service 104, the client 102 may connect to various devices with various functionality, such as gateways, routers, load balancers, databases, application servers running application programs on one or more nodes, or other devices that may be accessed via the cloud service 104. For example, the client 102 may connect to an application server 107 and/or one or more databases 108 via the cloud service 104. The application server 107 may include any computing system, such as a desktop computer, laptop computer, server computer, and/or any other computing device capable of providing functionality from an application program to the client 102. The application server 107 may include one or more application nodes running application programs whose functionality is provided to the client via the cloud service 104. The application nodes may be implemented using processing threads, virtual machine instantiations, or other computing features of the application server 107. Moreover, the application nodes may store, evaluate, or retrieve data from the databases 108 and/or a database server.
The databases 108 may contain a series of tables containing information about assets and enterprise services controlled by a client 102 and the configurations of these assets and services. The assets and services include configuration items (CIs) 110 that may be computers, other devices on a network 112 (or group of networks), software contracts and/or licenses, or enterprise services. The CIs 110 may include hardware resources (such as server computing devices, client computing devices, processors, memory, storage devices, networking devices, or power supplies); software resources (such as instructions executable by the hardware resources including application software or firmware); virtual resources (such as virtual machines or virtual storage devices); and/or storage constructs (such as data files, data directories, or storage models). As such, the CIs 110 may include a combination of physical resources or virtual resources. For example, the illustrated embodiment of the CIs 110 includes printers 114, routers/switches 116, load balancers 118, virtual systems 120, storage devices 122, and/or other connected devices 124. The other connected devices 124 may include clusters of connected computing devices or functions such as data centers, computer rooms, databases, or other suitable devices. Additionally or alternatively, the connected devices 124 may include facility-controlling devices having aspects that are accessible via network communication, such as heating, ventilation, and air conditioning (HVAC) units, fuel tanks, power equipment, and the like. The databases 108 may include information related to CIs 110, attributes (e.g., roles, characteristics of elements, etc.) associated with the CIs 110, and/or relationships between the CIs 110.
In some embodiments, the databases 108 may include a configuration management database (CMDB) that may store the data concerning CIs 110 mentioned above along with data related to various IT assets that may be present within the network 112. In addition to the databases 108, the cloud service 104 may include one or more other database servers. The database servers are configured to store, manage, or otherwise provide data for delivering services to the client 102 over the communication channel 106. The database server may include one or more additional databases that are accessible by the application server 107, the client 102, and/or other devices external to the additional databases. By way of example, the additional databases may include a relational database and/or a time series database. The additional databases may be implemented and/or managed using any suitable implementations, such as a relational database management system (RDBMS), a time series database management system, an object database, an extensible markup language (XML) database, a configuration management database (CMDB), a management information base (MIB), one or more flat files, and/or or other suitable non-transient storage structures. In some embodiments, more than a single database server may be utilized. Furthermore, in some embodiments, the cloud service 104 may have access to one or more databases external to the cloud service 104 entirely.
In the depicted topology, access to the CIs 110 from the cloud service 104 is enabled via a management, instrumentation, and discovery (MID) server 126 via an External Communications Channel (ECC) Queue 128. The MID server 126 may include an application program (e.g., Java application) that runs as a service (e.g., Windows service or UNIX daemon) that facilitates communication and movement of data between the cloud service 104 and external applications, data sources, and/or services. The MID service 126 may be executed using a computing device (e.g., server or computer) on the network 112 that communicates with the cloud service 104. As discussed below, the MID server 126 may periodically or intermittently use discovery probes to determine information on devices connected to the network 112 and return the probe results back to the cloud service 104. In the illustrated embodiment, the MID server 126 is located inside the network 112 thereby alleviating the use of a firewall in communication between the CIs 110 and the MID server 126. However, in some embodiments, a secure tunnel may be generated between a MID server 126 running in the cloud service 104 that communicates with a border gateway device of the network 112.
The ECC queue 128 may be a database table that is typically queried, updated, and inserted into by other systems. Each record in the ECC queue 128 is a message from an instance in the cloud service 104 to a system (e.g., MID server 126) external to the cloud service 104 that connects to the cloud service 104 or a specific instance 130 running in the cloud service 104 or a message to the instance from the external system. The fields of an ECC queue 128 record include various data about the external system or the message in the record.
Although the system 100 is described as having the application servers 107, the databases 108, the ECC queue 128, the MID server 126, and the like, it should be noted that the embodiments disclosed herein are not limited to the components described as being part of the system 100. Indeed, the components depicted in
Further, it should be noted that server systems described herein may communicate with each other via a number of suitable communication protocols, such as via wired communication networks, wireless communication networks, and the like. In the same manner, the client 102 may communicate with a number of server systems via a suitable communication network without interfacing its communication via the cloud service 104.
In addition, other methods for populating the databases 108 may include directly importing the CIs or other entries from an external source, manual import by users entering CIs o or other entries via a user interface, and the like. Moreover, although the details discussed above are provided with reference to the CMDB, it should be understood that the embodiments described herein should not be limited to being performed with the CMDB. Instead, the present systems and techniques described herein may be implemented with any suitable database.
Additionally, the system 100 may include demonstration services 132, which may present content (e.g., guided tours, videos, click-through demonstrations, etc.) which may be useful to illustrate certain features/functions of portions of GUIs of the system 100. As will be discussed in more detail below, the demonstration services 132 may provide interactivity monitoring that may discern a likely interest focus based upon interactivity with the demonstration services 132. The interest focus may be used to identify future content recommendations and/or future content to present to a user.
Interactivity analysis services 138 may monitor for interaction between the client 102 and content, such as demonstrations provided by the demonstration services 134 and/or digital content (e.g., videos, images, etc.) provided by the digital content provision services 136. As will be discussed in more detail below, the interactivity analysis services 138 may identify content that may be relevant based upon interaction between the client 102 and the content. The interactions and/or the identified content may be stored in the data store 140, such that, when desirable, new content and/or content recommendations may be provided to the client 102, based upon the interactions.
The interactor may also be classified as a particular type of interactor (block 154). For example, the interactor may be classified as a potential new customer, a potential partner, a current customer, and/or a current partner. For example, partners may include users that design add-ons or other third-party features for the system 100, whereas customers may include users that take advantage of services of the system 100.
Additionally or alternatively, the classification of the interactor may be based upon a role of the interactor. For example, a technical support role and. a network administrator role may be responsible for vastly different tasks. By classifying the interactor via a role, additional useful information pertaining to relevant content may be gleaned. In one embodiment, information for making such a classification may be acquired via a GUI poll and associated with the user profile. In some embodiments, the classification may be inferred based upon interactions or other available information. For example, if an interactor typically interacts with digital content related to a network administrator's role, the system 100 may infer that the interactor holds a network administrator role. Further, in some embodiments, an access permissions role may be used to classify the interactor based upon a role.
Additionally, a particular instance that is accessed may provide information useful for classification. For example, if a developer instance is accessed, such access may suggest that the interactor is a developer and/or tester rather than a high-level manager, such as Chief Executive Officer. Accordingly, based upon characteristics of particular access criteria, certain role inferences may be made.
In some embodiments, classification of the interactor may be determined based at least in part upon a speed of interaction with content. For example, if an interactor progresses at a fast pace through a click-through demonstration (e.g., above a pre-determined threshold speed), this may indicate that the interactor is familiar with at least portions of the feature being demonstrated. However, when an interactor progress slowly (e.g., below a pre-determined threshold speed), this may indicate that the interactor is likely unfamiliar with at least portions of the feature being demonstrated.
The process 150 continues by identifying interactions of the interactor and determining associated meta-data related to the interactions (block 156). For example, the interactivity analysis services 138 may identify interactions, by the interactor, with specific portions of a demonstration of a GUI, specific video, text documents, or images.
Machine-readable meta-data may be associated with the specific portions of a demonstration of a GUI, specific videos, text documents, and/or images, which may provide an indication of particular topics of the specific portions of a demonstration of a GUI, specific videos, text documents, and/or images. Accordingly, by interpreting the meta-data associated with the interacted-with content, the interactivity analysis services 138 may discern possible focus areas of interest.
Characteristics of the interactions may illustrate more likely interest than other characteristics. Accordingly, in some embodiments, the focus areas of interest (e.g., discerned based upon the meta-data associated with the interacted-with content) may be weighted (block 158). For example, consuming content in its entirety may indicate more interest than merely consuming a portion of content. Further, interacting with content for a longer period of time may indicate more interest than interacting with content for a shorter period of time. Repeated consumption of content may indicate more interest than merely consuming content once. Interactive searching of content (e.g., using a keyword search to find interacted-with content) may indicate more interest than merely browsing and interacting with content. Sharing content may indicate more interest than merely consuming content. Further, requesting communication (e.g., via a “Contact Us” link) and/or providing feedback after consuming content may indicate more interest than simply consuming content.
Based upon the difference in likelihood of interest based upon these interaction characteristics, the interactions and/or metadata may be weighted, resulting in a distribution of meta-data accounting for the various characteristics of the interactions and their potential for indicating interest.
Relevant content for subsequent presentation and/or recommendation may be identified based upon the weighted interaction and/or metadata and/or based upon the interactor classification (block 160). For example, in some embodiments, the relevant content may be identified based upon a metadata from the interactions that has the highest weighted distribution. Further in some embodiments, the magnitude of the weighted distribution may be used in conjunction with the interactor classification. For example, if the weighted metadata suggests two focus areas of interest, one associated with a network administrator role and one associated with a developer role, a classification of the interactor based upon role may indicate which of the two focus areas is more relevant. In another example, if a single focus area is present, but content for the focus area includes beginner content and advanced content, a classification based upon the interactor's experience level with a product may determine whether the beginner content or the advanced content should be recommended/presented.
Once the relevant content is identified, the relevant content may be presented and/or recommended (block 162). For example, in some embodiments, new content offerings may be provided directly to the interactor, e.g., via a GUI presented at the client 102. In some embodiments, an email may be provided to the interactor (e.g., as discerned from the interactor's user profile), indicating particular content that the interactor may be interested in.
In some embodiments, a sales representative or other entity may receive a progressive profile, indicating basic information, such as a user name, address, telephone number, etc. associated with the interactor's user profile. Further, the relevant content and/or focus areas may be provided. In addition, an indication of the interactor's interactions may be provided to the sales representative. This may enable the sales representative to follow up with the interactor, providing, via phone or other communications mechanism, information pertaining to the focus areas, the relevant content recommendations, etc.
To perform one or more of the operations described herein, the client 102, the application servicer 107, the MID server 126, the demonstration services 130, and other server or computing system described herein may include one or more of the computer components depicted in
As illustrated, the computing device 200 may include various hardware components. For example, the device includes one or more processors 202, one or more busses 204, memory 206, input structures 208, a power source 210, a network interface 212, a user interface 214, and/or other computer components useful in performing the functions described herein.
The one or more processors 202 may include processors capable of performing instructions stored in the memory 206. For example, the one or more processors may include microprocessors, system on a chips (SoCs), or any other suitable circuitry for performing functions by executing instructions stored in the memory 206. Additionally or alternatively, the one or more processors 202 may include application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and/or other devices designed to perform some or all of the functions discussed herein without calling instructions from the memory 206. Moreover, the functions of the one or more processors 202 may be distributed across multiple processors in a single physical device or in multiple processors in more than one physical device. The one or more processors 202 may also include specialized processors, such as a graphics processing unit (GPU).
The one or more busses 204 includes suitable electrical channels to provide data and/or power between the various components of the computing device. For example, the one or more busses 204 may include a power bus from the power source 210 to the various components of the computing device. Additionally, in some embodiments, the one or more busses 204 may include a dedicated bus among the one or more processors 202 and/or the memory 206.
The memory 206 may include any tangible, non-transitory, and computer-readable storage media. For example, the memory 206 may include volatile memory, non-volatile memory, or any combination thereof. For instance, the memory 206 may include read-only memory (ROM), randomly accessible memory (RAM), disk drives, solid state drives, external flash memory, or any combination thereof. Although shown as a single block in
The input structures 208 provide structures to input data and/or commands to the one or more processor 202. For example, the input structures 208 include a positional input device, such as a mouse, touchpad, touchscreen, and/or the like. The input structures 208 may also include a manual input, such as a keyboard and the like. These input structures 208 may be used to input data and/or commands to the one or more processors 202 via the one or more busses 204. The input structures 208 may alternative or additionally include other input devices. For example, the input structures 208 may include sensors or detectors that monitor the computing device 200 or an environment around the computing device 200. For example, a computing device 200 can contain a geospatial device, such as a global positioning system (GPS) location unit. The input structures 208 may also monitor operating conditions (e.g., temperatures) of various components of the computing device 200, such as the one or more processors 202.
The power source 210 can be any suitable source for power of the various components of the computing device 200. For example, the power source 210 may include line power and/or a battery source to provide power to the various components of the computing device 200 via the one or more busses 204.
The network interface 212 is also coupled to the processor 202 via the one or more busses 204. The network interface 212 includes one or more transceivers capable of communicating with other devices over one or more networks (e.g., the communication channel 106). The network interface may provide a wired network interface, such as Ethernet, or a wireless network interface, such an 802.11, Bluetooth, cellular (e.g., LTE), or other wireless connections. Moreover, the computing device 200 may communicate with other devices via the network interface 212 using one or more network protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP), power line communication (PLC), Wi-Fi, infrared, and/or other suitable protocols.
A user interface 214 may include a display that is configured to display images transferred to it from the one or more processors 202. The display may include a liquid crystal display (LCD), a cathode-ray tube (CRT), a light emitting diode (LED) display, an organic light emitting diode display (OLED), or other suitable display. In addition and/or alternative to the display, the user interface 214 may include other devices for interfacing with a user. For example, the user interface 214 may include lights (e.g., LEDs), speakers, and the like.
With the foregoing in mind, the discussion now turns to various content where interaction monitoring may be used to identify focus areas of interest, such that future relevant content recommendations may be discerned. Further, the suggested content may be content of similar types as the content monitored for interactivity.
Turning first to a discussion of guided tours,
The process 300 begins by polling for a request to generate a guided tour (decision block 302). If a request to generate a guided tour is not detected, the system may continue to poll for such a request.
In the GUI 400, a sidebar 402 includes an option 404 for creating a tour via a guided tour designer. In additional and/or alternative embodiments, an option 404 for creating a tour may be provided elsewhere, such as in the top bar 406, in the main body 408, etc. Upon selection of the option 404 (e.g., via the pointer 410), the request for generation of the guided tour may be generated and/or detected.
Returning to
Further, the prompt 502 includes an Application Page Name field 506, which is used to input a particular page of a GUI that the guided tour will take place on. As will be discussed in more detail below, the guided tour, when being generated and/or played, will render the page and its interactive objects such that callouts can be associated and/or played back on the interactive objects. For example, in the illustrated embodiment, the guided tour “DDay03” is associated with the incident.do page (e.g., of the IT application mentioned above).
Additionally, the roles section 508 enables the selection of particular roles that the guided tour will be available for. Available roles box 510 may provide a listing of all available role types, such as a task editor, an inventory administrator, a role delegator, etc. When at least one role is selected (e.g., by moving a role from box 510 into selected roles box 512), the guided tour will be available for the selected roles. In some embodiments, if no roles are selected (e.g., by transferring the roles into the selected roles box 512) the guided tour may be available for all roles. In alternative embodiments, when no role is selected, the guided tour is not available for any role. Once the input of the guided tour characteristics is complete (e.g., as indicated by selecting the Create button 514), the process 300 of
Returning to
Additionally, a guided tour menu 616 is presented in the GUI 600, which may facilitate generation of the guided tour. For example, the guided tour menu 616 may provide a callout menu 618 with one or more callouts that may be associated with one or more of the interactive objects 604. For example, in the current embodiment, a top callout 620, a bottom callout 622, a right callout 624, and a left callout 626 are provided.
Returning to
Returning to
Additionally, a trigger prompt 806 may be used to gather a trigger input that determines when a subsequent callout instance will be presented. For example, in
Upon completion of providing input to the callout instance characteristics prompt 802 (e.g., by selecting the “Save” button 808, the characteristics may be saved for the callout instance. Returning to
Returning to
After creation of the callout instances, it may be desirable to edit one of the callout instances. In certain embodiments, hovering over one of the indications in the guided tour menu 616, may alter a corresponding indication in the page view 1324. For example, in the current embodiment, hovering over indication 1306 causes indication 1308 to enlarge, change color, or otherwise be altered (e.g., being surrounded by dashed line 1326). Conversely, hovering over an indicator in the page view 1324 (e.g., indication 1308) may, in some embodiments cause a visual alteration of a corresponding indication in the guided tour menu 616 (e.g., indication 1306). Selection of any of the indications may indicate a request to edit the corresponding callout instance. Accordingly, in some embodiments, upon selection of an indication, a callout instance characteristic edit prompt may be provided.
Returning to
Upon selection of the next button 1606, the second callout association 1610 is presented. For example
Upon selection of the next button 1614, the third callout association 1616 is presented. For example
Upon selection of the next button 1620, the fourth callout 1622 association is presented. For example
Upon selection of the next button 1626, the fifth callout association 1628 is presented. For example
Upon selection of the next button 1636, the sixth callout association 1638 is presented. For example
Once the guided tour is created, it may be automatically added to an embedded help dialog.
As mentioned above, other interactions with digital content may be monitored to determine relevant digital content/focus areas.
Video interaction may also be used for focus area/relevant content determination.
Demonstration application interaction may also be used for focus area/relevant content determination.
Returning to
Returning to
Using the above-described techniques, content provision/recommendation may be facilitated GUI interaction, resulting in significant improvement in customer satisfaction and support. Further, interactive objects of application pages may be easily and efficiently featured for demonstration and/or embedded help purposes.
The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.
The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).
| Number | Date | Country | Kind |
|---|---|---|---|
| 201711016025 | May 2017 | IN | national |
