An on-demand service system can arrange for an on-demand service to be provided for a requesting user by a service provider. In some examples, the on-demand service system can provide information relevant to the requesting user to the service provider for purposes of assisting the service provider in performing the on-demand service.
Examples described herein provide for a system that can automatically configure an indication device (or a display device) for use with an on-demand service. As referred to herein, an indication device is a device that is capable of providing illumination, displaying content, and/or outputting audio, and that can be positioned or fastened, for example, on or within a vehicle operated by a service provider (e.g., a transport service provider, a delivery provider, etc.). Such an indication device can be positioned to be easily visible to a user or positioned proximate to a particular entry or door of the vehicle to indicate to the user where to enter. The system can use information specified or configured by a user of an on-demand service to cause the indication device to dynamically adjust the output for a predefined duration of time. Examples of features that can be configured by a user include a color(s), a pattern(s), an illumination sequence(s), text, visual content, video, and/or audio. In this manner, when the service provider approaches a user for purposes of providing the on-demand service, the indication device can be dynamically configured and personalized in a manner specified and recognizable by the user, thereby informing the user which vehicle has been assigned to the user to provide the on-demand service.
According to some examples, a transport personalization system can be a part of or be in communication with the on-demand service system. In one example, the on-demand service system can arrange a transport service for a user by receiving a request for transport from the user's device, selecting a driver from a plurality of available drivers to perform the transport service for that user, sending an invitation to the selected driver's device, and receiving an acceptance of the invitation by the selected driver. The on-demand service system can associate an identifier of the user and an identifier of the driver with an entry for that transport service. Once the on-demand service system arranges the transport service for the user and the driver, the transport personalization system can access a user database to determine whether that user has specified an output configuration for an indication device (e.g., determine whether the user has personalized at least one aspect of the transport service). For example, the transport personalization system can determine if the user has specified an output configuration in the user's account. If the user has specified an output configuration, the transport personalization system can identify data corresponding to the output configuration and transmit the data to the driver device of the driver that is to provide the transport service for the user. In the case where the driver is in possession of and uses an indication device, the data can enable the driver device to control the indication device using the data, such as during at least a duration of the transport service (e.g., while the transport service is in progress for that user). In such an example, once the transport service is completed for the user, the driver device can be instructed or caused to no longer control the indication device using the user's output configuration.
As described herein, the output configuration for an indication device can specify the manner in which the indication device is to output or emit light or content. Depending on implementation, the output configuration can specify one or more colors of light to be outputted by the indication device, one or more patterns in which light is to be outputted by the indication device, and/or one or more sequences of illumination in which light is to be outputted by the indication device, so that different portions of the indication device can be illuminated at different times. A user can access the user's account via a portal on the user's computing device, such as through use of a webpage or a designated client service application in communication with the on-demand service system and/or the transport personalization system, in order to configure the output configuration.
Still further, in some examples, the on-demand service system and/or the transport personalization system (collectively referred to herein as the system), can monitor the transport service to determine the state of the transport service. In some examples, the transport service can be in progress for a user from the time the selected driver accepts an invitation to perform the transport service or from the time the selected driver begins to travel from a position in which the selected driver accepted the invitation until the transport service has been completed by the driver (e.g., the driver has dropped off the user at the user's destination). The system can monitor the transport service using information received from the driver device (e.g., periodically or intermittently from driver user input), such as from a driver service application operating on the driver device, and/or information about the transport service (e.g., the pickup location and/or the destination location specified by the user). Depending on implementation, the system can transmit the data corresponding to the output configuration to the driver device during the progress of the transport service, but before the driver arrives at the pickup location specified by the user in the user's request for the transport service.
In some variations, the indication device (also referred to herein as a lighting or illumination device) can have different housing shapes or features to be fixed to a vehicle. For example, an indication device can include a body, a power source or power input port to receive power from a power source, a communication interface, and a base. Depending on implementation, the body can be formed of a translucent, semi-transparent, or transparent material that can be at least partially illuminated by a light source. As an addition or an alternative, the body can include or be formed as a display device that can output content (e.g., a flat panel display). In either examples, the body can be shaped to have at least one surface that is substantially flat and can have dimensions in which its length is substantially larger (e.g., two or more times larger) than both its height and its width, and/or its height is substantially larger (e.g., two or more times larger) than its width (e.g., the body can be in the shape of a blade). The body can provide illumination and/or output content that is customized based on the user-specified output configuration information.
The body can also be coupled to a base that extends at least partially along the length of the body. The base can include one or more fastening mechanisms or structures to enable the indication device to be coupled or fastened (e.g., either permanently or temporarily) to a vehicle. In one example, the base can also house one or more components of the indication device, such as a communication interface, a light source, a power source or a port for the power source, a light or display controller, wires or connection components, etc. The communication interface can enable the indication device to communicate (e.g., wirelessly or via a wire or cable) with the driver device to receive configuration data.
In another example, the indication device can have a body that has a length, a width, and a height, with its length being substantially greater (e.g., two or more times larger) than its width and its height, but its width being greater than its height. The body can have a first façade or surface that extends along the length and the width of the body. The body can also house one or more light sources to illuminate at least a portion of the first façade. The indication device can include a base that is coupled to the body and that extends along at least a portion of the length of the body and at least a portion of the width of the body. The indication device can also include one or more fastening mechanisms to enable the illumination device to adhere to a surface such that the first façade of the body faces the surface. Such a surface can be an interior surface of a window of a vehicle or a windshield. The indication device can communicate with the driver's device using a communication interface (e.g., wireless and/or a wire/cable) so that the controller device can receive data from the driver's device in order to control the one or more light sources. In this manner, when the driver's device receives the data corresponding to a user's output configuration, the driver's device can provide control signals to the indication device to control the manner in which the indication device outputs or emits light.
As used herein, a client device, a driver device, and/or a computing device refer to devices corresponding to desktop computers, cellular devices or smartphones, personal digital assistants (PDAs), laptop computers, tablet devices, television (IP Television), etc., that can provide network connectivity and processing resources for communicating with a notification system and/or a dispatch system over a network. A driver device can also correspond to other devices of a transit object, such as an in-vehicle computing system, or custom hardware, etc. The client device and/or the driver device can also each operate a designated service application that is configured to communicate with the on-demand service system and/or the transport personalization system. Still further, while some examples described herein relate to transport services, the systems describe herein can be used to provide other on-demand services, such as a food truck service, a delivery service, an entertainment service, etc.
One or more examples described herein provide that methods, techniques, and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically, as used herein, means through the use of code or computer-executable instructions. These instructions can be stored in one or more memory resources of the computing device. A programmatically performed step may or may not be automatic.
One or more examples described herein can be implemented using programmatic modules, engines, or components. A programmatic module, engine, or component can include a program, a sub-routine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.
Some examples described herein can generally require the use of computing devices, including processing and memory resources. Examples described herein may be implemented, in whole or in part, on computing devices such as servers, desktop computers, cellular or smartphones, personal digital assistants (e.g., PDAs), laptop computers, printers, network equipments (e.g., routers) and tablet devices. Memory, processing, and network resources may all be used in connection with the establishment, use, or performance of any example described herein (including with the performance of any method or with the implementation of any system).
Furthermore, one or more examples described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with figures below provide examples of processing resources and computer-readable mediums on which instructions for implementing examples can be carried and/or executed. In particular, the numerous machines shown with examples include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on smartphones, multifunctional devices or tablets), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices, such as cell phones) are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums. Additionally, examples may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.
In one example, the system 100 can include a personalization management 110, a client device interface 120, a driver device interface 130, and a client database 140. The system 100 can be a part of or communicate with an on-demand service system and/or can include other components or databases, such as a configuration database, which are not illustrated in
Depending on implementation, one or more components of the system 100 can be implemented on a computing device, such as a server, laptop, PC, etc., or on multiple computing devices that can communicate with the client devices 150 and the driver devices 160 over one or more networks. In some examples, a computing device can operate or execute an application to perform one or more of the processes described by the various components of the system 100. The system 100 can also be implemented through other computer systems in alternative architectures (e.g., peer-to-peer networks, etc.).
The system 100 can communicate, over one or more networks via a network interface (e.g., wirelessly or using a wire), with the client devices 150 (e.g., mobile computing devices operated by clients or users/customers) and the driver devices 160 (e.g., mobile computing devices operated by drivers) using a client device interface 120 and a driver device interface 130, respectively. The client and driver device interfaces 120, 130 can enable and manage communications between the system 100 and each of the client and driver devices 150, 160. In some examples, each of the client devices 150 and the driver devices 160 can individually operate a designated service application 151, 161, respectively, that interfaces with the respective device interfaces 120, 130 to communicate with system 100. According to some examples, the applications can include or use an application programming interface (API), such as an externally facing API, to communicate data with the device interfaces 120, 130. The externally facing API can provide access to system 100 via secure access channels over the network through any number of methods, such as web-based forms, programmatic access via restful APIs, Simple Object Access Protocol (SOAP), remote procedure call (RPC), scripting access, etc.
As described herein, the system 100 can be a part of or communicate with an on-demand service system, such as a dispatch system of the on-demand service system (not shown in
As illustrated in
According to some examples, the personalization management 110 can receive the transport information 111 of the arranged transport service from the dispatch system when the transport service is arranged for a user and a driver. The transport information 111 can include (i) an identifier (ID) corresponding to the arranged transport service, (ii) an identifier of the user and/or the client device 150 receiving the transport service, (iii) an identifier of the driver and/or the driver device 160 providing the transport service, and/or (iv) status information about the driver with respect to the transport service. Depending on implementation, the personalization management 110 can receive the transport information 111 in response to the transport service being initially arranged by the dispatch system. The personalization management 110 can determine when and whether to transmit configuration information specified by the user for an indication device 170 to the driver. The personalization management 110 can also receive the status information of the driver (e.g., periodically or in response to changes to the driver's status information) during a duration from when the transport service is arranged until completion of the transport service.
When the personalization management 110 receives the transport information 111, the personalization management 110 can use the user ID to access the client database 140. The client database 140 can store a plurality of client profiles 141 (or client accounts) for each user that has an account with the on-demand service system. A client profile 141 can include (or be associated with) a user identifier, contact information, payment/billing information, device and/or the service application 151 information (e.g., version information), user preferences, historical information about previous transport services provided for the user, etc. The user preferences can be configured by the user and can include indication (or sign) preferences, such as color, text, pattern, illumination sequence, media content, etc., related to the output of an indication device.
The personalization management 110 can perform a lookup of the client profile 141 (e.g., using the user's ID or user's device ID) and determine if the user has specified an output configuration for an indication device. If the user has specified (e.g., in the user preferences) the output configuration, the personalization management 110 can determine and/or retrieve the configuration data 145 corresponding to the specified configuration for that user. In one example, the personalization management 110 can receive information about the output configuration from the client profile 141 and retrieve the configuration data 145 from a configuration database. On the other hand, if the personalization management 110 determines that the user has not specified an output configuration, the personalization management 110 can transmit a message or a prompt (e.g., an in-application message displayed by the service application 151 or a text message) to the user's client device 150 informing the user that the user can configure one or more indication preferences. If the user operates the service application 151 and provides indication preferences, the personalization management 110 can receive the user's preferences and store the preferences with the user's profile 141 in the client database 140. If the user does not provide indication preferences, however, the personalization management 110 can store or maintain default indication preferences in the user's profile 141. In some examples, the personalization management 110 can perform these steps after the transport service has been arranged but before the driver has arrived at the pick up location and/or before the driver has initiated the transport service.
The personalization management 110 can transmit the user's configuration data 145 corresponding to the user's indication preferences (or default configuration data if the user has not specified indication preferences) to the driver device 160. For example, the personalization management 110 can determine the driver that is to provide the transport service by identifying the driver's ID from the transport information 111. Depending on implementation, if there is no configuration data 145 for indication preferences specified by the user, the personalization management 110 can transmit default configuration data to the driver device 160 or transmit a message (without sending default configuration data) indicating to the driver's service application 161 operating on the driver device 160 that the driver's own configuration data or default configuration data is to be used for controlling the indication device 170.
The driver device 160 can run the service application 161 for purposes of communicating with the on-demand service system (and/or the system 100). For example, the driver can operate the service application 161 when the driver is ready or available to provide transport services. The service application 161 can also enable the driver device 160 to communicate with the indication device 170 using the communication interfaces of the driver device 160 and the indication device 170. In one example, the driver device 160 and the indication device 170 can communicate with each other using a Bluetooth protocol or using another short range wireless technology protocol. In another example, the driver device 160 and the indication device 170 can communicate with each other over a wire or cable. The service application 161 can receive the configuration data 145 from the system 100 and control the indication device 170 using the configuration data 145 via one or more control signals over the communication interfaces of the driver device 160 and the indication device 170. In one example, the indication device 170 can include a device controller that provides control signals to the light source or display of the indication device 170 based on the configuration data 145.
The service application 161 can also receive invitations for transport services from the on-demand service system and provide location information and/or status information of the driver to the on-demand service system. The service application 161 can interface with components of the driver device 160, such as the global positioning system (GPS) component of the driver device 160 to determine a current position or location of the driver device 160. In one example, after (and before) the driver accepts the invitation to provide the transport service for the user via interaction with the service application 161, the driver device 160 can periodically transmit GPS location data points to the on-demand service system (and/or the system 100).
According to an example, the on-demand service system can determine different states of the transport service or the driver by using information received from the service application 161. As referred to herein, a state of the transport service or a state of the driver can refer to the current condition of the driver when providing transport service. A driver can be in one of a plurality of different states that include, for example: (i) unavailable (e.g., off duty), (ii) available (e.g., on duty) but not yet providing transport service, (iii) en route to the pickup location of the user after accepting an invitation for transport service, (iv) arriving at the pickup location (e.g., the driver is approaching the pickup location), (v) on trip (e.g., the user has entered the vehicle, the transport service has begun), or (vi) completed trip (e.g., the driver has completed the transport service by dropping off the user at the user's destination location). The state information used by the on-demand service system to keep track of the driver, determine whether it can select the driver for a transport service, determine how long and how far the driver has driven the user for purposes of determining the fare, etc. Depending on examples, the driver operating the driver device 160 (and in possession of the indication device 170) can indicate what state the driver is currently in by providing input to the service application 161 (e.g., input that the driver has accepted the invitation, that the driver is approaching the user, that the driver has completed the transport service, etc.). The service application 161 can provide state information to the on-demand service system.
In another example, the on-demand service system can use location information from the driver's device 160 and/or the transport information 111 to automatically determine the driver's state or the state of the transport service. For example, the on-demand service system can determine that the driver is en route to the pickup location in response to receiving the acceptance of the invitation from the driver device 160 and/or in response to determining that the driver has changed positions (from GPS data of the driver device 160) since the acceptance. In another example, the on-demand service system can programmatically determine that the driver is arriving at the pickup location or has reached the pickup location by comparing the location data of the driver with the specified pickup location of the user (e.g., if the driver's position is within a predetermined distance of the user's current location or the pickup location). Still further, similarly, the on-demand service system can programmatically determine that the driver has completed the transport service by comparing the location data of the driver with the specified destination location of the user, if provided. Accordingly, in variations, the on-demand service system can provide the state information to the service application 161 and/or the service application 161 can provide the state information to the on-demand service system. In this manner, in either examples, the service application 161 and the system 100 can recognize the state of the transport service or the driver.
According to some examples, based on the state of the transport service or the driver, the system 100 and/or the service application 161 can control the operation of the indication device 170. As described herein, the system 100 can provide the configuration data 145 for the particular user to the selected driver's device 160 for use during the specific transport service. In this manner, when that driver completes the transport service, he or she can receive another invitation for transport service for another user, and receive, if any, the configuration data 145 for the other user during the progress of another transport service. During the progress of the transport service, the service application 161 can use the state information to control the indication device 170 to output different colors, content, patterns, etc., based on the state of the transport service or the driver. In other words, based on the indicated state (e.g., arriving now or on trip), the service application 161 can tailor the output of the indication device 170.
For example, the configuration data 145 of the user preference can specify that a blue color to be outputted by the indication device 170. When the driver accepts a transport request and is en route to the pick up location of the user for the transport service, the service application 161 can cause the indication device 170 to output a default color or be turned off to conserve power because the user will not yet see the vehicle or the indication device 170. At a time when the driver is approaching the pickup location, the driver can input on the service application 161 that the driver is close to the user's pickup location or the service application 161 and/or the on-demand service system can determine that the driver's current location is within a predetermined distance of the pickup location of the user. The state of the transport service can correspond to the driver “arriving now.” When the service application 161 determines that the transport service is to change states from “en route” to “arriving now,” for example, the service application 161 can trigger or control the indication device to output the user's specified color, e.g., blue, (and/or other preferred output content, patterns, or sequences) so that the user can see which vehicle is approaching and will provide the service for the user. The service application 161 can also control the indication device to output the user's specified display/output preferences in a specific configuration that is based on the transport state.
As an addition or an alternative, the system 100 can receive information about the transport state from the service application 161 and the personalization management 110 can use the configuration data 145 of the user preference to control the indication device 170 based on the transport state (e.g., as opposed to the service application 161 controlling the indication device 170). For example, the indication device 170 can include network resources to be in communication with system 100 over one or more networks (and/or via the driver device 160). In such an example, the system 100 can control the output of the indication device 170 without input provided by the driver operating the driver device 160.
In this manner, by enabling the user to provide user-specified preferences for the indication device 170, the system 100 can provide the user with a personalized on-demand service experience. In addition, in some situations, such as during darkness or when the user is at a crowded street corner or area (e.g., an airport) and waiting for the vehicle, the personalized experience can indicate to the user which vehicle is the user's vehicle for purposes of the transport service. The indication device 170 can show the user's specified color, content, pattern, etc., so that in a group of vehicles, the user can easily determine which vehicle to enter. Still further, the indication device 170 can also display or include features, such as a trademark or name, associated with the on-demand service provider, thereby providing brand recognition for the on-demand service provider.
As an addition or an alternative, the indication device 170 can also include other components or sensors, such as a GPS receiver and/or an inertial measurement unit (INU). These components or sensors can be used to periodically determine real-time conditions of the vehicle while the indication device 170 is powered on and in operation. The indication device 170 can provide to the driver device 160, via one or more communication interfaces, data determined from the components or sensors (referred to herein as indication device information 131). The service application 161 can store the indication device information 131 in a memory resource and/or concurrently provide the indication device information 131 to the on-demand service system and/or the system 100. The indication device information 131 can be used by the on-demand service system to complement or supplement data corresponding to a transport service or to determine, with higher accuracy, the bearing, the movement, the direction of movement, etc. of the driver's vehicle (before, after, or during transport service).
In some examples, the body 205 can be shaped to have an overall length, L, that is substantially greater than the overall height, H, and the overall width, W (see
In the examples described in
Referring to
Another example of the indication device 230 is illustrated in
Another benefit for shaping the body 205 to have the exemplary dimensions is to reduce the amount of material (e.g., plastic, glass, etc.) necessary for manufacturing the indication device 200, while maintaining a large surface area for purposes of maximizing lighting. Still further, reducing the overall size and weight of the indication device 200 can enable a service provider to easily and quickly fasten or remove the indication device 200 from the vehicle (e.g., the driver can do it by himself or herself). This can be important as a driver can quickly fasten the indication device 200 to the roof of his vehicle, for example, when the driver is electing to go on-duty (e.g., be available to provide transport services), and similarly, quickly remove the indication device 200 when the driver will go off-duty.
Referring back to
In another example, in
In one example, the indication device can be illuminated in a default color (e.g., white) while the driver is providing transport or driving to pick up a user (e.g., the indication device is in a “neutral state”). When the driver indicates “arriving now,” the indication device can fade to the user's specified color (e.g., the indication device is in the “arrival state”). In addition, from this instance in time, as the driver waits for the user to enter the vehicle, the illumination can pulse or periodically fade in and fade out between the user's specified color and the default color (e.g., slowly transition from white to yellow for 2 seconds, maintain the yellow color for 0.5 seconds, and then transition back to white for 2 seconds, etc.). While the driver waits, he or she has not indicated that the transport service has yet begun. During this time, the indication device can provide pulsating or transitioning illumination, as discussed (e.g., the indication device is in the “transition state”). After the user enters the vehicle, the indication device can be illuminated back to the default color or maintained in the user's specified color (e.g., the indication device is in a “transport state”). When the transport service is completed and the driver arrives at the user's destination, the driver can indicate on his or her device, “trip ended,” and the indication device can again perform a transitioning illumination operation or output the user's specified color for a duration of time as the user exits, such as 10 seconds (e.g., the indication device is in a “goodbye state”). In this manner, the indication device can provide the user with a personalized experience that gives the user the appearance of a transport service that is specifically tailored for that user.
Referring to
The base 291 of the indication device 290 can be shaped to extend along at least a portion of the length of the body 293 and at least a portion of the width of the body 293. In one example, the base 291 can have a greater length (and/or width) than the body 293, such as illustrated in
Each of the fastening mechanisms 295, 297 can also include an attachment mechanism(s) to couple to respective first end and second end portions of the base 291 (see
In some examples, at least one or more of the base 291, the body 293, or the fastening mechanisms 295, 297 can include or house one or more electrical components (e.g., light source(s), device controller circuitry, ports/interfaces, wires, electrical contacts, etc.). For example, as illustrated in
As an addition or an alternative, different fastening mechanisms can be used to attach the indication device 290 to a vehicle. For example, in
In another example, referring to
The indication device 290 can also be shaped in different ways, depending on variations. For example, the façade 294 of the indication device 290 can be substantially flat or can have a slight curve along its length, such as illustrated in
Depending on implementation, the indication device 290 can have a variety of different light sources and/or different arrangements for the light source(s). In one example, the indication device 290 can be backlit using different light-producing devices, can include an array of light elements, such as bulbs, light-emitting diodes (LEDs), light-emitting electrochemical cells (LECs), and/or can include a display device, such as a touch-sensitive display device, a LED display, an liquid crystal display (LCD) device, etc. Based on power and/or control signals received from a computing device, such as the driver's device, the indication device 290 can be illuminated in a particular manner. In another example, the indication device 290 can be pre-programmed to illuminate in a particular manner when the indication device 290 is turned on, without being connected to or without communicating with the driver's device or the transport personalization system of
For example,
Referring to
In another example, in
Methodology
Referring to
If the user has specified an output configuration, the transport personalization system can retrieve or determine the output configuration from the user's profile (360) and provide data corresponding to the output configuration to the driver's device (370). For example, the transport personalization system can determine the driver's identifier that is to provide the transport for the user from the arranged transport service information and identify the driver's device. If the user has not specified an output configuration, on the other hand, the transport personalization system can provide a message (e.g., an in-app message) to the user's device prompting the user to provide an output configuration for the indication device (330).
The prompt can indicate to the user that the user may specify the output configuration if the user would like. The user can interact with the in-app message (e.g., that is displayed by the designated service application) in order to access the different configuration(s) that can be selected by the user. If the user inputs the output configuration (340), the transport personalization system can receive and determine the output configuration (360) and store the output configuration with the user's profile for future use. The transport personalization system can then transmit the output configuration to the appropriate driver device (370).
If the user chooses not to input or select an output configuration, the transport personalization system can determine that the default output configuration is to be used by the driver (350). In that case, the transport personalization system can transmit the default output configuration to the driver device (370). As an alternative, the transport personalization system does not transmit any output configuration to the driver device, and the driver device automatically uses the default output configuration. The driver's device can use the output configuration to adjust the illumination and/or display of the indication device for purposes of providing personalized transport services for the user (e.g., by providing control signals from the driver's device to the indication device using a communication interface).
As an addition or an alternative, the system and/or the driver service application can determine the output configuration used to control the indication devices (e.g., without user control or preference). For example, the output configuration can be based on the current state of the transport service without taking into consideration user-specified colors, patterns, or sequences of illumination. The driver service application can store the output configuration data with predetermined transport service/driver status information so that the driver service application can control the indication device when it detects a certain state of the transport service or driver. In other examples where the system determines the state, the system can transmit predetermined output configuration data to the driver device corresponding to the detected state in order to cause the driver's device to control the indication device accordingly.
Still further, in some examples, the indication device can include memory that store pre-programmed data that controls the manner in which the indication device illuminates its façade or blade-like surfaces. The indication device may receive state information from the driver device and the device controller of the indication device can control the illumination based on the received state information. In another example, a connection between the indication device and the driver's device may not be necessary as the indication device can illuminate in a specified pre-programmed manner when the indicating device is turned on (such that the illumination is not based on user-specified preferences or the state of the transport service).
User Interface
In
When the user selects the feature 413 to adjust or select the color, the user interface 420 of
Although not illustrated in
Hardware Diagram
In one implementation, the computer system 500 includes processing resources 510, a main memory 220, a read-only memory (ROM) 530, a storage device 540, and a communication interface 550. The computer system 500 includes at least one processor 510 for processing information and a main memory 520, such as a random access memory (RAM) or other dynamic storage device, for storing information and instructions to be executed by the processor 510. The main memory 520 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 510. The computer system 500 may also include the ROM 530 or other static storage device for storing static information and instructions for the processor 510. The storage device 540, such as a solid-state device, a magnetic disk, or an optical disk, is provided for storing information and instructions. For example, the storage device 540 can correspond to a computer-readable medium that stores sign (output configuration) instructions 542 for performing operations discussed with respect to
The communication interface 550 can enable the computer system 500 to communicate with one or more networks 580 (e.g., cellular network) through use of the network link (wireless and/or using a wire). Using the network link, the computer system 500 can communicate with a plurality of devices, such as the mobile computing devices of the clients and service providers. According to some examples, the computer system 500 can receive configuration information 552 from a client device when the user provides a selection or configures the output configuration for an indication device via the network link. The processor 510 can associate the configuration information 552 with the user's profile and store the configuration information in the storage device 540, for example, and provide the configuration information to the driver's device if a transport service is arranged for that user. If a transport service is arranged for the user and a driver, the processor 510 can identify the user's configuration information 552 from memory, for example, and transmit the configuration information 552 to the specific driver's device. The driver's device can use the configuration information to control the illumination or display of the indication device in possession of the driver.
The computer system 500 can also include a display device 560, such as a cathode ray tube (CRT), an LCD monitor, or a television set, for example, for displaying graphics and information to a user. An input mechanism 570, such as a keyboard that includes alphanumeric keys and other keys, can be coupled to the computer system 500 for communicating information and command selections to the processor 510. Other non-limiting, illustrative examples of input mechanisms 570 include a mouse, a trackball, touch-sensitive screen, or cursor direction keys for communicating direction information and command selections to the processor 510 and for controlling cursor movement on the display 560.
Examples described herein are related to the use of the computer system 500 for implementing the techniques described herein. According to one example, those techniques are performed by the computer system 500 in response to the processor 510 executing one or more sequences of one or more instructions contained in the main memory 520, such as the sign instructions 542. Such instructions may be read into the main memory 520 from another machine-readable medium, such as the storage device 540. Execution of the sequences of instructions contained in the main memory 520 causes the processor 510 to perform the process steps described herein. In alternative implementations, hard-wired circuitry may be used in place of or in combination with software instructions to implement examples described herein. Thus, the examples described are not limited to any specific combination of hardware circuitry and software.
The processor 610 is configured with software and/or other logic to perform one or more processes, steps and other functions described with implementations, such as described by
The processor 610 can provide a variety of content to the display 630 by executing instructions and/or applications that are stored in the memory resources 620. One or more user interfaces 615 can be provided by the processor 610, such as a user interface for the service application. A user, for example, can operate a mobile computing device (such as the mobile computing device 600) to operate a client service application. The GPS component 670 can determine location information, such as the current location information 665 of the computing device 600. The user can make a transport request using the location information 665, as a pick up location, for example, and provide the transport request to the on-demand service system via the communication sub-systems 640. The user can also operate a user interface 615 provided as part of the service application in order to input output configuration preferences of the user. The configuration information 645 can be provided to the on-demand service system and stored with the user's profile.
In another example, for a driver device, the memory resources 620 can store data corresponding to the driver service application. The GPS component 670 can determine location information, such as the current location information 665 of the computing device 600, and the operation of the driver service application can cause the location information 665 to be periodically determined and communicated to the on-demand service system (and/or the transport personalization system) via the communication sub-systems 640. In addition, for a driver device, the driver service application can receive the configuration information 645 (for a user that the driver is to provide transports service for) from the on-demand service system (and/or the transport personalization system) and based on the configuration information 645, control an indication device (not shown in
The power source 740 provides power to the components of the indication device 700. The power source 740 can be an internal power source, such as a battery, and/or an external power source (e.g., provided by a power source of the vehicle of the driver in possession of the indication device 700 or the driver's device). The light source 730 can be one or more individual light sources, an electroluminescence (EL) element(s), and/or a display device, as described with
In some examples, the indication device 700 can receive control data 725 via the communication interface 720 from a wirelessly connected (or connected via wire) driver device (not shown in
It is contemplated for examples described herein to extend to individual elements and concepts described herein, independently of other concepts, ideas or system, as well as for examples to include combinations of elements recited anywhere in this application. Although examples are described in detail herein with reference to the accompanying drawings, it is to be understood that the concepts are not limited to those precise examples. Accordingly, it is intended that the scope of the concepts be defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described either individually or as part of an example can be combined with other individually described features, or parts of other examples, even if the other features and examples make no mentioned of the particular feature. Thus, the absence of describing combinations should not preclude having rights to such combinations.
This application is a continuation of U.S. patent application Ser. No. 16/253,936, filed Jan. 22, 2019, titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND TRANSPORT SERVICE, which is a continuation of U.S. patent application Ser. No. 15/902,787, filed Feb. 22, 2018, now U.S. Pat. No. 10,239,444 issued Mar. 26, 2019 titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND TRANSPORT SERVICE, which is a continuation of U.S. patent application Ser. No. 15/615,678, filed Jun. 6, 2017, now U.S. Pat. No. 9,937,857, issued Apr. 10, 2018, titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND TRANSPORT SERVICE, which is a continuation of U.S. patent application Ser. No. 15/342,072, filed Nov. 2, 2016, now U.S. Pat. No. 9,718,397 issued Aug. 1, 2017, titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND TRANSPORT SERVICE, which is a continuation of U.S. patent application Ser. No. 14/604,573, filed Jan. 23, 2015, now U.S. Pat. No. 9,536,271 issued Jan. 3, 2017, titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND TRANSPORT SERVICE, which claims benefit of priority to U.S. Provisional Patent Application No. 61/994,722, filed May 16, 2014, titled USER-CONFIGURABLE INDICATION DEVICE FOR USE WITH AN ON-DEMAND SERVICE; the aforementioned priority applications being hereby incorporated by reference in their respective entirety.
Number | Name | Date | Kind |
---|---|---|---|
4550304 | Saitta | Oct 1985 | A |
5168451 | Bolger | Dec 1992 | A |
5212645 | Wildes et al. | May 1993 | A |
5604676 | Penzias | Feb 1997 | A |
5945919 | Trask | Aug 1999 | A |
6028537 | Suman | Feb 2000 | A |
6212393 | Suarez | Apr 2001 | B1 |
6356838 | Paul | Mar 2002 | B1 |
6618593 | Drutman | Sep 2003 | B1 |
6756913 | Ayed | Jun 2004 | B1 |
6874037 | Abram | Mar 2005 | B1 |
6925381 | Adamczyk | Aug 2005 | B2 |
6950745 | Agnew | Sep 2005 | B2 |
6989765 | Gueziec | Jan 2006 | B2 |
7062376 | Oesterling | Jun 2006 | B2 |
7080019 | Hurzeler | Jul 2006 | B1 |
7610145 | Kantarjiev | Oct 2009 | B2 |
7822426 | Wuersch | Oct 2010 | B1 |
8140256 | dos-Santos | Mar 2012 | B1 |
8285571 | Demirdjian | Oct 2012 | B2 |
8362894 | Shah | Jan 2013 | B2 |
8489119 | Fraccaroli | Jul 2013 | B1 |
8554608 | O'Connor | Oct 2013 | B1 |
8646194 | Podd | Feb 2014 | B2 |
8799038 | Chen et al. | Aug 2014 | B2 |
8909256 | Fraccaroli | Dec 2014 | B2 |
9483744 | Ford | Nov 2016 | B2 |
9488484 | Ford | Nov 2016 | B2 |
9552559 | Ford | Jan 2017 | B2 |
9558469 | Ford | Jan 2017 | B2 |
9569740 | Ford | Feb 2017 | B2 |
9599481 | Ford | Mar 2017 | B2 |
9671239 | Ford | Jun 2017 | B2 |
9689694 | Ford | Jun 2017 | B2 |
9715667 | Ford | Jul 2017 | B2 |
9892637 | Demisse | Feb 2018 | B2 |
9965960 | McDavitt-Van Fleet | May 2018 | B1 |
20010037174 | Dickerson | Nov 2001 | A1 |
20010056363 | Gantz | Dec 2001 | A1 |
20020125839 | Yen | Sep 2002 | A1 |
20020143587 | Champernown | Oct 2002 | A1 |
20030030666 | Najmi | Feb 2003 | A1 |
20040024789 | Ditcharo et al. | Feb 2004 | A1 |
20040049424 | Murray | Mar 2004 | A1 |
20040107110 | Gottlieb et al. | Jun 2004 | A1 |
20050153707 | Ledyard | Jul 2005 | A1 |
20050227704 | Ferra | Oct 2005 | A1 |
20060004590 | Khoo | Jan 2006 | A1 |
20060034201 | Umeda et al. | Feb 2006 | A1 |
20060059023 | Mashinsky | Mar 2006 | A1 |
20060200306 | Adamcyzk | Sep 2006 | A1 |
20060224437 | Gupta | Oct 2006 | A1 |
20060242154 | Rawat | Oct 2006 | A1 |
20070150375 | Yang | Jun 2007 | A1 |
20070183156 | Shan | Aug 2007 | A1 |
20070224939 | Jung | Sep 2007 | A1 |
20070255627 | Hallowell | Nov 2007 | A1 |
20070265974 | Chang | Nov 2007 | A1 |
20070276595 | Lewinson | Nov 2007 | A1 |
20070279241 | Jung | Dec 2007 | A1 |
20080055049 | Weill | Mar 2008 | A1 |
20080091342 | Assael | Apr 2008 | A1 |
20080114629 | Pavlov | May 2008 | A1 |
20080195428 | O'Sullivan | Aug 2008 | A1 |
20080228854 | Grimault et al. | Sep 2008 | A1 |
20080270204 | Poykko | Oct 2008 | A1 |
20080277183 | Huang | Nov 2008 | A1 |
20080298058 | Kan et al. | Dec 2008 | A1 |
20090049119 | Marcinkiewicz et al. | Feb 2009 | A1 |
20090143965 | Chang et al. | Jun 2009 | A1 |
20090176508 | Lubeck et al. | Jul 2009 | A1 |
20090192851 | Bishop | Jul 2009 | A1 |
20090216600 | Hill | Aug 2009 | A1 |
20090281844 | Probst | Nov 2009 | A1 |
20090313077 | Wheeler, IV | Dec 2009 | A1 |
20090326991 | Wei | Dec 2009 | A1 |
20100042549 | Adamczyk | Feb 2010 | A1 |
20100198428 | Sultan et al. | Aug 2010 | A1 |
20100205017 | Sichelman et al. | Aug 2010 | A1 |
20100207812 | Demirdjian | Aug 2010 | A1 |
20100260350 | Chutorash | Oct 2010 | A1 |
20100280852 | Huang | Nov 2010 | A1 |
20100292914 | Vepsalainen | Nov 2010 | A1 |
20100332133 | Harris | Dec 2010 | A1 |
20110000747 | Wu | Jan 2011 | A1 |
20110009098 | Kong | Jan 2011 | A1 |
20110099040 | Felt et al. | Apr 2011 | A1 |
20110102165 | Rahamim | May 2011 | A1 |
20110118981 | Chamlou | May 2011 | A1 |
20110145089 | Khunger et al. | Jun 2011 | A1 |
20110153629 | Lehmann et al. | Jun 2011 | A1 |
20110161227 | Santo, Jr. | Jun 2011 | A1 |
20110225269 | Yap et al. | Sep 2011 | A1 |
20110258623 | Wagner | Oct 2011 | A1 |
20110301985 | Camp | Dec 2011 | A1 |
20110301997 | Gale et al. | Dec 2011 | A1 |
20110320230 | Podgurny | Dec 2011 | A1 |
20120041675 | Juliver | Feb 2012 | A1 |
20120059693 | Colodny et al. | Mar 2012 | A1 |
20120078672 | Mohebbi | Mar 2012 | A1 |
20120092194 | Crucs | Apr 2012 | A1 |
20120131170 | Spat | May 2012 | A1 |
20120137256 | Lalancette | May 2012 | A1 |
20120171963 | Tsfaty | Jul 2012 | A1 |
20120203599 | Choi | Aug 2012 | A1 |
20120232943 | Myr | Sep 2012 | A1 |
20130024249 | Zohar | Jan 2013 | A1 |
20130024308 | Ramaswamy | Jan 2013 | A1 |
20130054139 | Bodin | Feb 2013 | A1 |
20130054281 | Thakkar | Feb 2013 | A1 |
20130073327 | Edelberg | Mar 2013 | A1 |
20130074111 | Hyde et al. | Mar 2013 | A1 |
20130090963 | Sharma | Apr 2013 | A1 |
20130102333 | Dam | Apr 2013 | A1 |
20130132140 | Amin | May 2013 | A1 |
20130144831 | Atlas | Jun 2013 | A1 |
20130150004 | Rosen | Jun 2013 | A1 |
20130171930 | Anand | Jul 2013 | A1 |
20130179205 | Slinin | Jul 2013 | A1 |
20130290200 | Singhal | Oct 2013 | A1 |
20130295963 | Sen | Nov 2013 | A1 |
20130316727 | Edge | Nov 2013 | A1 |
20130332527 | Du | Dec 2013 | A1 |
20140011522 | Lin | Jan 2014 | A1 |
20140051465 | Ruys et al. | Feb 2014 | A1 |
20140067488 | James | Mar 2014 | A1 |
20140081764 | James | Mar 2014 | A1 |
20140082069 | Varoglu et al. | Mar 2014 | A1 |
20140087697 | Johnston et al. | Mar 2014 | A1 |
20140129135 | Holden et al. | May 2014 | A1 |
20140129951 | Amin | May 2014 | A1 |
20140130387 | Podd | May 2014 | A1 |
20140149544 | Le Nerriec | May 2014 | A1 |
20140156556 | Lavian | Jun 2014 | A1 |
20140164559 | Demeniuk | Jun 2014 | A1 |
20140172727 | Abhyanker | Jun 2014 | A1 |
20140223787 | Richmond | Aug 2014 | A1 |
20150032484 | Mermelstein | Jan 2015 | A1 |
20150046080 | Wesselius et al. | Feb 2015 | A1 |
20150127439 | Campos De Figueiredo Faceira | May 2015 | A1 |
20150154810 | Tew | Jun 2015 | A1 |
20150161554 | Sweeney | Jun 2015 | A1 |
20150161564 | Sweeney | Jun 2015 | A1 |
20150161752 | Barreto | Jun 2015 | A1 |
20150195133 | Sheets | Jul 2015 | A1 |
20150204684 | Rostamian | Jul 2015 | A1 |
20150228000 | Bijor | Aug 2015 | A1 |
20150248689 | Paul | Sep 2015 | A1 |
20150262430 | Farrelly | Sep 2015 | A1 |
20150279217 | Chen | Oct 2015 | A1 |
20150310868 | Mallik | Oct 2015 | A1 |
20150317568 | Grasso | Nov 2015 | A1 |
20150323327 | Ford | Nov 2015 | A1 |
20150323329 | Ford | Nov 2015 | A1 |
20150323330 | Ford | Nov 2015 | A1 |
20150323331 | Ford | Nov 2015 | A1 |
20150324334 | Ford | Nov 2015 | A1 |
20150324717 | Lord | Nov 2015 | A1 |
20150324734 | Ford | Nov 2015 | A1 |
20150324945 | Lord et al. | Nov 2015 | A1 |
20150325158 | Ford | Nov 2015 | A1 |
20150332425 | Kalanick | Nov 2015 | A1 |
20150339923 | Konig | Nov 2015 | A1 |
20150345743 | Trincia | Dec 2015 | A1 |
20150345951 | Dutta | Dec 2015 | A1 |
20150356803 | Ellis | Dec 2015 | A1 |
20160019728 | Petrie | Jan 2016 | A1 |
20160026935 | Botea | Jan 2016 | A1 |
20160027306 | Lambert | Jan 2016 | A1 |
20160034828 | Sarawgi | Feb 2016 | A1 |
20160034845 | Hiyama | Feb 2016 | A1 |
20160042303 | Medina | Feb 2016 | A1 |
20160117610 | Ikeda | Apr 2016 | A1 |
20160132792 | Rosnow | May 2016 | A1 |
20160138928 | Guo | May 2016 | A1 |
20160180346 | Cheng | Jun 2016 | A1 |
20160198319 | Huang | Jul 2016 | A1 |
20160300318 | Godil | Oct 2016 | A1 |
20160334232 | Zhuang | Nov 2016 | A1 |
20160356615 | Arata | Dec 2016 | A1 |
20160364678 | Cao | Dec 2016 | A1 |
20160364824 | Bryant | Dec 2016 | A1 |
20160377445 | Rodoni | Dec 2016 | A1 |
20160378303 | Crilley | Dec 2016 | A1 |
20170011324 | Truong | Jan 2017 | A1 |
20170017374 | Herz | Jan 2017 | A1 |
20170038948 | Le Cun | Feb 2017 | A1 |
20170072844 | Kalanick | Mar 2017 | A1 |
20170126810 | Kentley | May 2017 | A1 |
20170138749 | Pan | May 2017 | A1 |
20170186126 | Marco | Jun 2017 | A1 |
20170193404 | Yoo | Jul 2017 | A1 |
20170213160 | Yerli | Jul 2017 | A1 |
20170267166 | Kalanick | Sep 2017 | A1 |
20170300848 | Shoval | Oct 2017 | A1 |
20180003843 | Hori et al. | Jan 2018 | A1 |
20180091603 | Nickels | Mar 2018 | A1 |
20180101925 | Brinig | Apr 2018 | A1 |
20180102017 | Brinig | Apr 2018 | A1 |
20180178717 | Kalanick | Jun 2018 | A1 |
20180180426 | Pan | Jun 2018 | A1 |
20180198535 | Cirit | Jul 2018 | A1 |
20180232789 | Bijor | Aug 2018 | A1 |
20190035202 | Brinig | Jan 2019 | A1 |
20190051174 | Haque | Feb 2019 | A1 |
20190087754 | Farrelly | Mar 2019 | A1 |
20190095849 | Sweeney | Mar 2019 | A1 |
20190109910 | Sweeney | Apr 2019 | A1 |
20190120636 | Le Cun | Apr 2019 | A1 |
20190152382 | Kalanick | May 2019 | A1 |
20190221069 | Brinig | Jul 2019 | A1 |
20190320043 | Goldstein | Oct 2019 | A1 |
20190327003 | Cirit | Oct 2019 | A1 |
20200145503 | Sweeney | May 2020 | A1 |
20200173979 | Nickels | Jun 2020 | A1 |
20200258344 | Brinig | Aug 2020 | A1 |
20200374650 | Jung | Nov 2020 | A1 |
20210256794 | Brinig | Aug 2021 | A1 |
20210262810 | Le Cun | Aug 2021 | A1 |
Number | Date | Country |
---|---|---|
2889853 | May 2014 | CA |
201918124 | Aug 2011 | CN |
202213529 | May 2012 | CN |
102934393 | Feb 2013 | CN |
104885386 | Sep 2015 | CN |
105871903 | Aug 2016 | CN |
109120497 | Jan 2019 | CN |
2473831 | Mar 2011 | GB |
1992027220 | May 1990 | JP |
2000082199 | Mar 2000 | JP |
2004-302941 | Oct 2004 | JP |
2004-362271 | Dec 2004 | JP |
3934985 | Jun 2007 | JP |
2012088925 | May 2012 | JP |
2014-130552 | Jun 2014 | JP |
2004-073639 | May 2015 | JP |
6218057 | Oct 2017 | JP |
10-2010-0053717 | May 2010 | KR |
10-2012-0090480 | Aug 2012 | KR |
10-1013-08531 | Sep 2013 | KR |
10-2014-0124137 | Oct 2014 | KR |
10-2015-0045962 | Apr 2015 | KR |
WO 1999044186 | Feb 1999 | WO |
WO 1999044186 | Sep 1999 | WO |
WO 2005013588 | Feb 2005 | WO |
WO 2011067741 | Jun 2011 | WO |
WO-20110069170 | Jun 2011 | WO |
WO 2014106617 | Jul 2014 | WO |
WO-2018128781 | Jul 2018 | WO |
Entry |
---|
Hai Yang et al. “Equilibria of bilateral taxi-customer searching and meeting on networks”, Transportation Research Part B., 2010, vol. 44, pp. 1067-1083. |
International Search Report in PCT/US2015/034831 dated Sep. 24, 2015. |
International Search Report in PCT/US2015/043654 dated Nov. 26, 2015. |
International Search report in PCT/US2016/016858 dated May 19, 2016. |
IPRP in PCT/US2014/069602 dated Jun. 23, 2016. |
Alfred Round, et al.: Future Ride: Adapting New Technologies to Paratransit in the United States, UC Transportation Center Berkeley, CA, UCTC No. 306 (1996). |
Kikuchi, et al., “Advanced Traveler Aid Systems for Public Transportation”, US Department of Transportation, Sep. 1994. |
Fu, et al., “On-Line and Off-Line Routing and Scheduling of Dial-a-Ride Paratransit Vehicles”, Computer-Aided Civil and Infrastructure Engineering 14 (1999). |
International Search Report and Written Opinion issued in PCT/US2016/062344 dated Jan. 31, 2017. |
Extended Search Report issued in EP 14869805.3 dated May 10, 2017. |
Extended Search Report issued in EP 15826507.1 dated Nov. 10, 2017. |
International Search Report in PCT/US2017/053065 datedDec. 13, 2017. |
Written Opinion issued in SG 11201700669R dated Dec. 5, 2017. |
Robert Kuhlthau and Ira D. Jacobson, The Development of a Model for Predicting Passenger Acceptance of Short Haul Air Transportation Systems, NASA, Sep. 1977. |
Xing Wang, Optimizing Ride Matches for Dynamic Ride Sharing Systems, GIT, May 2013. |
International Search Report issued in PCT/US2017/053065 dated Dec. 13, 2017. |
First Examination Report in EP 14869806.3 dated May 4, 2018. |
Aloizio P. Silva, A Mobile Location-Based Vehicle Fleet Management Service Application, 0-7803-78482/03 2003, IEEE. |
Andersson, Magnus, Peer-to-Peer Service Sharing Platforms: Driving Share and Share Alike on a Mass-Scale, Thirty Fourth International Conference on Information Systems, Milan 2013, pp. 1-15 (2013). |
First Office Action in CN 2014800731753 dated Feb. 3, 2019. |
Examination Reported in AU 2017342747 dated Apr. 8, 2019. |
Office Action in EP 15826501.7 dated May 14, 2019. |
EESR in EP 17859424.8 dated Aug. 5, 2019. |
ISR and Written Opinion in PCT/US2018/055256 dated Jan. 30, 2019. |
How to request multiple Uber vehicles, Aug. 15, 2013 (https://www.wikihow.com/ Request-Multiple-Uber-Vehicles. |
How to book two cabs at the same time in Uber, Jun. 30, 2017 (https://fastandclean.org/ book-two-cabs-time-uber). |
Is it possible to order 2 Ubers at the same time, Jul. 13, 2015 (https://web.archive.org/web/20150801000000*/https://android. Stackexchange.com/questions/114027/is-it- possible-to-order-2-ubers-at-the-same-time. |
Written Opinion in PCT/US2018/055256 dated Jul. 19, 2019. |
Examination Report No. 1 in AU 2014362392 dated Sep. 10, 2019. |
Examination Report No. 1 in AU 2014362378 dated Sep. 18, 2019. |
Exam Report No. 2 in AU 2017/342747 dated Aug. 27, 2019. |
Second Office Action dated Sep. 27, 2019 in CN 2014800731753. |
Exam Report No. 1 in AU 2015296265 dated Apr. 21, 2020. |
Office Action in JP 2018-524399 dated Apr. 8, 2020. |
Office Action in BR 1120170017768 dated May 6, 2020. |
Exam Report No. 2 in AU 2014362378 dated May 7, 2020. |
Exam Report No. 2 in AU 2015296265 dated Aug. 13, 2020. |
Summons to attend oral hearing in EP 17859424.8 dated Dec. 7, 2020. |
Office Action in IN 201647042936 dated Dec. 23, 2020. |
Office Action in JP 2019-91274 dated Sep. 2, 2020. |
Exam Report No. 2 in AU 2019200957 dated Sep. 4, 2020. |
Notice of Allowance in AU 2019200957 dated Feb. 18, 2021. |
Decision in EP 17859424.8 dated Aug. 4, 2021. |
Number | Date | Country | |
---|---|---|---|
20200269750 A1 | Aug 2020 | US |
Number | Date | Country | |
---|---|---|---|
61994722 | May 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16253936 | Jan 2019 | US |
Child | 15930276 | US | |
Parent | 15902787 | Feb 2018 | US |
Child | 16253936 | US | |
Parent | 15615678 | Jun 2017 | US |
Child | 15902787 | US | |
Parent | 15342072 | Nov 2016 | US |
Child | 15615678 | US | |
Parent | 14604573 | Jan 2015 | US |
Child | 15342072 | US |