Adjusting attributes for an on-demand service system based on real-time information

A system and method for dynamically adjusting attributes for a network service is described. A computing system can determine a change that is to be implemented to an attribute of the network service. For each of a plurality of computing devices, the computing system can receive information associated with that computing device from a designated application operating on that computing device. The designated application is associated with the network service. The computing system automatically implements the change to at least one but not all of the plurality of computing devices based on the information received from each of the plurality of computing devices.

BACKGROUND OF THE INVENTION

An on-demand service system can arrange for a service to be provided to a user by a service provider. In some examples, the user and the service provider can individually operate a computing device that communicates with the on-demand service system. For example, the user and the service provider each operates a designated application that communicates with the service system on the user's device or the service provider's device, respectively.

DETAILED DESCRIPTION

Examples described herein provide for a system that enables a user (e.g., an administrative user) of the system to add, delete, edit, and/or switch on or off a feature(s) related to an attribute(s) of a network service. The system can also provisionally switch on or off a feature related to an attribute, such as turning on or off a feature for a set (or percentage) of users and/or computing devices. According to an example, an on-demand service system (that, at least in part, implements the network service) can communicate with a feature provider system in order to determine a change that is to be implemented to an attribute of the network service. The on-demand service system can use information received from client devices, service provider devices (e.g., driver devices), and/or current configuration information associated with the on-demand service system in order to automatically implement the change to the attribute of the network service.

As described herein, an attribute can correspond to a characteristic of the network service, such as, for example, a designated client application associated with the network service (e.g., operated on a client device to communicate with the on-demand service system), a designated service provider application associated with the network service (e.g., operated on a service provider device to communicate with the on-demand service system), a dispatch process utilized by the on-demand service system, a price determination process utilized by the on-demand service system, other processes utilized by the on-demand service system related to providing on-demand services, etc. A feature can be an aspect of an attribute that can be added, removed, adjusted, etc., such as a user interface of a designated application, text or graphics of the designated application, selectable features of the designated application, components used to implement the dispatch process or the price determination process, rules or policies for other processes used by the on-demand service system, etc., for implementing the network service.

Each of the on-demand service system and the feature provider system can be implemented on one or more computing systems or devices. According to examples, the on-demand service system and the feature provider system can be implemented on different computing systems or on the same computing system. In one example, the on-demand service system can communicate with a feature provider system periodically and/or in response to receiving a user input (or using a push or pull protocol via a persistent connection). The on-demand service system can check for updates or changes that are to be made to one or more attributes. Depending on examples, the on-demand service system can access a configuration database to determine whether a change is to be made to an attribute (e.g., toggle on or off a user interface feature of the designated application for certain devices) or receive, via push or pull protocol, instructions about a change that is to be made to an attribute. If the on-demand service system determines that a change is to be made, the next time client devices and/or service provider devices communicate with the on-demand service system, the on-demand service system can implement the change to one or more of the client devices and/or service provider devices based on information received from the devices and based on configuration data from configuration file(s).

In some examples, the on-demand service system can implement a change to an internal process that is utilized and/or performed by the on-demand service system for purposes of arranging on-demand services. As described herein, arranging a service can correspond to selecting a service provider to perform the service for a requesting user. In one example, a configuration file, which corresponds to a particular feature or an attribute, can instruct the on-demand service system to adjust a dispatch (or driver selection) mechanism or process in a particular geographic region (e.g., increase or decrease a dispatch radius for selecting drivers as compared to a previous dispatch radius). As another example, a configuration file can be used to perform a test operation for the on-demand service system (e.g., A/B testing). The configuration file can instruct the on-demand service system to select drivers by distance for drivers that are in one geographic region and select drivers by estimated time of arrival for drivers that are in another geographic region.

As used herein, a client device, a service provider 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 the system over a network. A driver device can also correspond to other devices of a transit object, such as custom hardware or on-board vehicle computers, etc. The client device and/or the driver device can also operate each an application configured to communicate with the system (e.g., a designated application).

Although examples of the network service described herein relate to an on-demand transport service, the on-demand service system can also enable other location-based on-demand services to be arranged between individuals using the computing devices described. For example, the on-demand service system can provide a delivery service (e.g., food delivery, messenger service, or product shipping), a food service (e.g., food trucks), or an entertainment service (e.g., mariachi band, string quartet), and a service provider, such as a driver, food provider, band, etc., can be selected by the on-demand service system to provide the service for a user.

Some embodiments described herein can generally require the use of computing devices, including processing and memory resources. For example, one or more embodiments 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, digital picture frames, network equipment (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 embodiment described herein (including with the performance of any method or with the implementation of any system).

System Description

FIG. 1illustrates an example system to dynamically adjust an attribute(s) for a network system using real-time information. An on-demand service system can communicate with a feature provider system, which notifies or instructs the on-demand service system as to which features of attributes should be toggled on or off (or provisionally turned on or off). For example, the feature provider system can provide a user interface to enable a user (e.g., an administrative user of the feature provider system and/or the on-demand service system) to cause the system to toggle on or off features for certain devices or for certain processes performed by the on-demand service system based on real-time conditions, such as time of day, device or application information, device location, current dispatch state information, etc. In this manner, the on-demand service system and the feature provider system can combine to dynamically implement changes to attributes of the on-demand service system with specific granularity.

According to an example, a system100includes an on-demand service system110(also referred to as the on-demand system110) and a feature provider system140. The on-demand system110includes a feature control component120, a feature interface130, a client interface133, a driver interface135, a user interface database127, and a business logic190, and the feature provider system140includes a feature management component150(which provides a feature interface160), a service interface155, and a configuration database165. A plurality of client devices170and a plurality of driver devices180can also communicate with the system100over one or more networks. The components of the system100can combine to dynamically adjust an attribute for the on-demand system110based on real-time (or close to real-time) information received from the client devices170and/or the driver devices180, and/or current configuration information associated with the on-demand system110. Logic can be implemented with various applications (e.g., software) and/or with hardware of a computer system that implements the system100.

Depending on implementation, one or more components of the system100can be implemented on network side resources, such as on one or more servers. The system100can also be implemented through other computer systems in alternative architectures (e.g., peer-to-peer networks, etc.). As an addition or an alternative, some or all of the components of the system100can be implemented on client devices, such as through applications that operate on the client devices170and/or the driver devices180. For example, a client application, such as a designated service application, can execute to perform one or more of the processes described by the various components of the system100. The system100can communicate over a network, via a network interface (e.g., wirelessly or using a wireline), to communicate with the one or more client devices170and the one or more driver devices180.

The system100can communicate, over one or more networks, with client devices170and driver devices180using a client interface133and a driver interface135, respectively. The device interfaces133,135can manage communications between the system100and remote computing devices. The client devices170and driver devices180can individually operate a designated service application that can interface with the device interfaces133,135to communicate with the system100. 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 interfaces133,135. The externally facing API can provide access to the system100via 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.

In some examples, the feature control component120of the on-demand system110can communicate, via the feature interface130and the service interface155, with the feature provider system140. The feature interface130and the service interface155can enable the on-demand system110and the feature provider system140to communicate with each other and exchange data. For example, the feature interface130and the service interface155can implement a protocol, such as a push protocol or pull protocol, which enables the feature control component120to check for updates about what changes need to be made since the last communication. For example, a push protocol can enable the feature provider system140to push information about updates to the on-demand system110through a persistent connection (e.g., web sockets, SPDY, transmission control protocol, etc.). The feature control component120can use the interfaces130,155to communicate with the feature provider system140periodically (e.g., every five seconds, seven seconds, etc.) and/or in response to receiving a user input that instructs the feature control component120to ping or message the feature provider system140for data. By communicating with the feature provider system140, the feature control component120can determine whether there is a change that is to be implemented to an attribute of the on-demand system110.

According to an example, the configuration database165can store a plurality of configuration files for a plurality of features that each corresponds to an attribute of the on-demand system110. As described herein a configuration file refers to configuration data that is stored in a file, in memory, or other data structure or store. The configuration database165can be updated and maintained by the feature management component150based on user input. In some examples, a user (e.g., an administrator) of the system100can access and interact with a user interface161provided by the feature interface160of the feature management component150to create, delete, edit, and/or toggle on or off features of different attributes of the on-demand system110(by providing user input163). For example, the user interface161can provide a plurality of options to enable the user to create, delete, edit, and/or toggle on or off features. The options can be extensible so that options can be added or removed for creating a configuration file.

For a particular feature of an attribute, for example, the user can create a configuration file by providing configuration data167via user input163, including (i) providing a name or identifier, (ii) specifying a type of feature, (iii) providing a value for that feature, such as a price, value, or threshold number that pertains to the feature (e.g., a distance for a dispatch radius, a total number of devices to receive a particular user interface feature, etc.), (iv) specifying a geographic region for that feature (e.g., by accessing or referencing a geofence database that stores a plurality of geofences that each define a geographic region), (v) specifying a time or time interval (e.g., when the feature should be toggled on or off, or how long the feature should be toggled on or off if based on a schedule), (vi) specifying a device or device type (e.g., by brand or operating system used by the device), (vii) specifying an application version, (viii) specifying a user or set of users, (ix) specifying a percentage of users to expose a feature to (e.g., 20% of users see feature A, while 80% of the users see features B on the user interface of the designated client application), and/or (x) providing other information for the configuration file.

The feature interface160can receive the user inputs163and the feature management component150can create and store the configuration file with corresponding configuration data167based on the user inputs163. The configuration data167stored with a configuration file can instruct the feature control component120to implement a corresponding feature to only those devices170,180and/or to only those components of the on-demand system110that satisfy the conditions specified by the configuration file when the configuration file is toggled on. In one example, a configuration file can be toggled on or off for a set of client devices or driver devices at a particular time of day (e.g., at 8 am) or manually by the administrative user.

In addition, the feature management component150can enable the administrative user to toggle on or off the features via the user input163. For example, each of the configuration files in the configuration database165can include a value (e.g., an active value) that indicates whether the corresponding feature is toggled on or off (e.g., is the feature active?). A “true” or “yes” value indicates that the feature is active or on while a “false” or “no” value indicates that the feature is inactive or off. The administrative user can schedule a particular feature to be automatically turned on or off or manually adjust the active value in order to turn on or off a particular feature.

According to some examples, the feature control component120can periodically communicate with the feature provider system140to determine which features are toggled on or off. Depending on implementation, in one example, when the feature control component120pings or messages the feature provider service140, the feature management component150can provide an update to the feature control component120indicating which changes (if any) have been made since the last communication. The feature management component150can keep track of a timestamp of the last communication between the feature control component120and the feature management component140and which features were toggled on or off at that time, and perform a comparison at the subsequent communication to determine which features changed states. For example, as compared to the previous time the on-demand system110communicated with the feature provider system140, a new feature123may have been added as a configuration file or an existing feature121may have been turned on or off (or deleted). The feature control component120can receive, from the feature management150, the identifiers of the configuration files that have changed states from the previous time and access the configuration database165to determine the configuration data167for those configuration files.

As an addition or an alternative, the feature control component120can access the configuration database165to determine which features are toggled on or off. For example, the feature control component120can maintain its own configuration database125that indicates the current state of the attributes of the on-demand system110(e.g., which features are on or off). The configuration database125can indicate which configuration files are currently active (e.g., have features that are toggled on) and/or which configuration files are currently inactive. When the feature control component120communicates with the feature provider system140, the feature control component120can read the active values of the configuration files from the configuration database165to determine which features are toggled on or toggled off at the present time. The feature control component120can perform a compare operation with configuration information from the configuration database125and the configuration information read from the configuration database165to determine which changes (if any) have been made since the last time the feature control component120accessed the configuration database165.

For example, if a previously toggled-off feature (or non-existing feature) is now toggled-on (or created and toggled-on) at the time the feature control component120communicates with the feature provider system140, the feature control component120determines that a change is to be implemented. Similarly, if a previously toggled-on feature is now toggled-off (or deleted) at the time the feature control component120communicates with the feature provider system140, the feature control component120also determines that a change is to be implemented. The feature control component120can determine the identifiers of the configuration files that have changed states from the comparison and access the configuration database165to determine the configuration data167for those configuration files. Depending on either implementation, by determining that a change is to be implemented to an attribute of the on-demand system100, the feature control component120can identify the configuration file, and use the corresponding configuration data167and real-time information to perform the implementation process.

The on-demand system110can receive real-time client information171associated with the client devices170and real-time driver information181associated with the driver devices180. For example, when a designated client application and/or a designated driver application is being run on a client device170and/or a driver device180, respectively, the feature control component120can receive client information171and/or driver information181from the respective designated application periodically and/or in response to receiving user input on those devices170,180. According to examples, the information171,181received from the devices170,180includes at least one of (i) a current location of a respective computing device, (ii) a device type of the respective computing device, (iii) a user identifier associated with the respective computing device, or (iv) a version information for the designated application operating on the respective computing device, or other information associated with the designated application or the respective computing device.

When the feature control component120determines that a change to a feature is to be made, the feature control component120can use (i) the corresponding configuration data167, (ii) the client information171and/or driver information181, and (iii) other known information (such as current time or date) to automatically implement the change to the designated application on the appropriate devices. For example, the designated applications can communicate with the on-demand system110using a protocol in which client information171and/or device information181is transmitted (e.g., a ping) to the on-demand system110and the on-demand system110provides a response. In some examples described, the on-demand system110can provide a response that corresponds to a client application control signal173or a driver application control signal183that causes the respective designated service applications to implement a corresponding change.

In some examples, the feature control component120can also access a user interface database127that stores different user interface features, selectable features, texts, graphics, etc., for the designated client application and designated driver application. A configuration file can correspond to a user interface feature that is to be turned on or off (e.g., added or removed from a user interface of a designated application on the client device170or the driver device180). In such an example, the feature control component120can use the configuration data167of that configuration file to determine which user interface feature to add or remove by accessing the user interface database127and identifying the appropriate user interface data129. Although the user interface database127is shown to be a part of the on-demand service system110, depending on implementation, the user interface database127can be a part of the feature provider system140or the dispatch system (not shown inFIG. 1) and can be updated by inputs provided by a user of system100.

According to another example, the feature control component120can determine that a change is to be implemented to a process utilized or performed by the on-demand service system (as opposed to a feature on the designated service applications). A configuration file that has been toggled on, for example, can correspond to a feature in which the dispatch system of the on-demand system110uses, for a particular city or metropolitan area, an additional factor when making a driver selection as compared to a previous (or default) driver selection mechanism in which fewer factors are used. In such an example, the feature control component120can determine the configuration data167corresponding to that configuration file, determine current dispatch system configuration information (e.g., received from the dispatch system), and automatically implement the change to the dispatch system using the configuration data167and the current dispatch system configuration information. The feature control component120can provide a control signal corresponding to the change to the dispatch system.

Although the dispatch system is not illustrated inFIG. 1, the on-demand system110can include the dispatch system and/or be in communication with the dispatch system. The dispatch system can receive requests for transport services from users, select drivers for the users to perform the transport services, provide pricing for the transport services, and perform payment transactions for the transport services.

As an example, a configuration file can instruct the feature control component120to increase a maximum time a driver has to accept a transport request for only those drivers that are currently in a particular geographic region (e.g., in San Francisco, Calif.) from a default time (e.g., ten seconds) to a new time (e.g., twenty seconds). Initially, for example, the configuration file can be toggled off. When the user (via the feature interface160) toggles the configuration file on, at a next time the feature control component120pings the feature provider service140(and/or or accesses the configuration database165), the feature control component120can determine that the feature has been turned on and determine that a change is to be implemented to that feature.

The feature control component120can receive driver information181from the driver devices180and identify those drivers that are in the geographic region indicated by the configuration file. The feature control component120can then automatically implement the change to the feature to those driver devices180that are in the specified geographic region by transmitting a driver application control183signal corresponding to the change to the designated driver applications on the driver devices180. In addition, the feature control component120can also implement the change to the feature to the dispatch system so that the dispatch system is informed of the increased acceptance time. In this manner, the increased acceptance time feature for drivers that are located in San Francisco, Calif. (as specified by the San Francisco geofence, for example) can be implemented on their respective driver devices180whereas the increased acceptance time feature for drivers that are located elsewhere are not implemented on their respective driver devices180.

As an addition or an alternative, in some examples, the on-demand system110can be implemented on one server or computing device (or one set of servers) while the feature provider system140can be implemented on another server or computing device (or another set of servers). In other examples, although two separate systems110,140are shown inFIG. 1, the feature provider system140can be included with the on-demand system110as a single system and/or in a single server or computing device. Still further, in another example, multiple on-demand systems110and/or multiple feature provider systems140can be used to implement system100.

For example, multiple systems can communicate with the feature provider system140via the service interface155and the respective systems' feature interface130in order to determine and/or implement changes to attributes of the network service. In another example, the business logic190of the on-demand system110can instruct the feature control component120to control one or more other systems of the network service. The business logic190can be configured with one or more rules or parameters, for example, to instruct the feature control component120to implement the appropriate change to a feature of another system of the network service.

According to some examples, the on-demand system110can represent a plurality of systems and platforms. For example, the on-demand system110can be running on any operating system (e.g., Windows, Linux, etc.) and running any language platform (e.g., Java, Node, Python, etc.). In one implementation, the feature control component120can use grammar language to describe the configuration from the configuration database165in order for the feature control component120to work consistently across a plurality of systems and platforms.

Methodology

FIG. 2illustrates an example method for adjusting one or more attributes for a network service using real-time information. A method such as described by an example ofFIG. 2can be implemented using, for example, components described with an embodiment ofFIG. 1. Accordingly, references made to elements ofFIG. 1are for purposes of illustrating a suitable element or component for performing a step or sub-step being described.

Referring toFIG. 2, an on-demand system110can communicate with a feature provider system140(210). Depending on implementation, the on-demand system100can communicate with the feature provider system140periodically, in response to user input (received at the on-demand system110or the feature provider system140), and/or as part of a scheduled push or pull protocol using a persistent connection. The feature provider system140can include a configuration database165that stores a plurality of configuration files for a plurality of features associated with the network service. The configuration files can be turned on or off based on user input or based on a set schedule, so that the corresponding features of attributes can be indicated to be changed.

The on-demand system110can communicate with the feature provider system140to determine whether there is a change that is to be implemented to an attribute of the network service (220). For example, at time t=t1, the feature control component120can determine which features have been turned on or off as compared to a previous time, t=t0(e.g., the previous time the on-demand system110communicated with the feature provider system140). If no change is to be made to an attribute, the feature control component120does not implement a change. The feature control component120can communicate with the feature provider system140at the next instance in time. On the other hand, if the feature control component120determines that one or more changes is to be implemented to an attribute, the feature control component120can identify the one or more configuration files that have been toggled on or off (or created or deleted) and that instructs the one or more changes that are to be made to the attribute.

For example, a configuration file can instruct the feature control component120to use a vehicle selection interface that has four vehicle type options (as opposed to three options) for the designated client applications on client devices170that are in a particular geographic region (e.g., Los Angeles, Calif.). Previously, at time t=t0, the configuration file may have been toggled off. After the configuration file is toggled on, at time t=t1, when the feature control component120communicates with the feature provider system140, the feature control component120can determine that a change is to be implemented to a designated client application. The feature control component120can identify the configuration file from the configuration database165and determine the corresponding configuration data167.

The on-demand system110can receive information from the client devices170and/or the driver devices180(230). For example, the client devices170and/or the driver devices180can individually operate a designated service application that communicates with the on-demand system110. Depending on implementation, the on-demand system110can receive information initially when a respective user or driver launches or opens the respective designated service application and/or periodically afterwards. The devices170,180can send information including (i) a current location of a respective computing device (232), (ii) a device type of the respective computing device (234), (iii) a user identifier associated with the respective computing device, such as a user identifier of the client or customer or the user identifier of the driver (236), and/or (iv) a version information for the designated application operating on the respective computing device (238).

The feature control component120can implement the change to one or more of the client devices170and/or the driver devices180and/or to different other aspects of the on-demand service system based on the received information and the configuration data167corresponding to the changed to the attribute (240). Referring back to the example, the configuration data167of the configuration file can instruct the feature control component120to use a vehicle selection interface that has four choices (as opposed to three choices) for the designated client applications on client devices170that are in the particular geographic region. The feature control component120can use the received application and/or application version information to determine which devices operate the client application and also determine which devices are currently located in the geographic region. The feature control component120can then implement the change to only those devices that satisfy the conditions specified in the configuration file. In one example, the feature control component120can access a user interface database127to determine the user interface data129of the vehicle selection interface that has four choices (as opposed to three choices) so that the user interface data129can be transmitted to the identified devices as part of or along with client application control173. The client application control173can cause the designated client applications to implement the corresponding change.

Depending on implementation, a variety of different changes can be implemented to an attribute(s) of the on-demand system110. In one example, a particular application user interface feature can be turned on or off (e.g., added, removed, exchanged) on the client application and/or driver application (242). This can include changing selectable features, providing different text, changing graphics (e.g., instead of an image of an automobile moving on a map, such as on a default view of a vehicle type, display an image of a trolley or a kitten or a football), changing colors or configurations of the application, etc. In some examples, certain applications can also be changed by pushing an application upgrade for applications of certain versions (244). For example, if a set of drivers use application version 2.5, but version 2.3 (e.g., the older version) is working better with less glitches, toggling a feature to cause the older version to be used (for a period of time while version 2.5 is being modified or fixed) can cause the feature control component120to determine which drivers are operating the application with version 2.5. The feature control component120can then automatically implement the change to those set of drivers to push the upgrade to the version 2.3.

In another example, the feature control component120can implement a change to a system component or process (246). A feature can correspond to a rule or policy used for dispatching drivers, determining pricing, processing payment, etc., that is performed by the dispatch system and/or the on-demand system110. Such rules or policies can be dynamically adjusted by the feature control component120. Still further, other examples include turning on or off a service, thereby causing a change to user interface features of the designated service applications as well as to components or features of the dispatch system and/or the on-demand system110(248). For example, a service can correspond to sharing a fare between multiple users for a transport service. The fare sharing service can be enabled for only those users that are administrators of the system (as opposed to other customers who are not administrators) (e.g., for purposes of testing before public release). A corresponding user interface feature (e.g., a menu option) to use the fare sharing service can be toggled on for client applications stored on devices belonging to only administrators. In addition, the feature control component120can enable the fare sharing service to be performed by the on-demand system110for only those administrators.

In another example, as another use case scenario, transport services can be subject to different rules or regulations based on different countries or geographic regions. The configuration files can cause different rules or regulations to be implemented for different users based on whether the user is a client or a driver, and based on the current location of the users. For example, clients in a certain state or region can have a user interface feature that is toggled on for their client applications that enable a client to notify the on-demand system110if the driver appears to be under the influence. Other clients in other regions may not have the same user interface feature toggled on.

Use Case Examples

For purpose of illustration, a number of use case examples are described below. In one example, an entity that provides the network service can offer a promotion or a special service for users in a geographic region. This promotion or special service can be available for a duration of time or permanently until turned off by an administrative user of the entity. For example, a transport service arrangement system can typically offer a set of vehicle types that a user can select when making a transport request for a transport service. An administrative user can create a special service that can be requested by users in a given geographic region during a specified duration of time (e.g., for a month, for a week, or ending on a particular date and/or time, etc.). The special service can correspond to a specific vehicle type that was previously unavailable in that geographic region or a delivery service of food (or kittens, for example, in connection with a partnership with an animal shelter) to a specified location.

When the configuration file for the special service is toggled on, for example, at the feature provider system140, the on-demand system110can determine that a change is to be implemented to an attribute (e.g., the client application and/or the dispatch system) of the network service. The on-demand system110can determine which client applications on which client device170are to be changed so that the user interface feature corresponding to the special service, for example, are to be included and/or displayed by those client applications. The on-demand system100can receive client information171from the client devices170, determine (based on the geofence associated with the geographic region specified in the configuration file) which of those client devices170are in the geofence of that geographic region, and cause the client applications on those client devices170to implement the change to the user interface. In one example, the change can correspond to displaying an option to select the special service (e.g., a new selectable feature) that was previously not available on the user interface of the client application. As an addition or an alternative, the change can correspond to displaying graphic images corresponding to the special service (e.g., images of kittens or ice cream cones, etc.) in place of default images of automobiles associated with default transport services. In such an example, these images would replace the images of automobiles that would otherwise been displayed on a map user interface to show the close to real-time locations of those automobiles. In this manner, the client devices170that are in the geographic region may display other transport service offerings as compared to client devices170that are not in that geographic region, thereby changing the attribute for the network service for certain groups of users.

If the configuration file specifies a duration of time (e.g., three days) in which the special service is made available to client devices in the geographic region, when the duration of time elapses, the feature control component120can again implement a change to the attribute to cause the attribute to revert back to the previous state. In this example, after the duration of the special service ends, the feature control component120can cause the new selectable feature for the special service to be removed from the user interface of the client application and the default feature(s) to be present and/or cause the graphic images corresponding to the special service to be removed from the map user interface of the client application.

In another example, a configuration file, when toggled on, can cause the client applications associated with a specific group of users to display different user interface features than client applications associated with another group of users. The group of users can be identified by user identifiers, application identifiers, email domain names, mobile device identification numbers, etc. The group of users may also be identified by flagging the users' accounts as belonging to a particular organization or being an employee of the entity that offers the network service.

Still further, in another use case example, the on-demand system110can determine that a change is to be implemented to a driver selection process performed by the on-demand system110(and/or the dispatch system). The on-demand system100can determine which set of rules (that specify the manner in which a driver selection process is to be performed) is to apply to a particular geographic region and/or to drivers and users in that region. For example, a configuration file can specify that when the dispatch system receives a request for a transport service from a user operating a client device170in that region (or receives a request that specifies a pickup location in that region), the dispatch system is to identify available drivers that are within a predetermined distance (e.g., three miles) from the location of the client device170(or the specified pickup location). The dispatch system would not implement this change to other regions, so that when the dispatch system receives a request for a transport service from a user operating a client device170in another geographic region (or receives a request that specifies a pickup location in another geographic region), the dispatch system can continue to identify available drivers that are within the previously specified distance (e.g., five miles) from the location of the client device170(or the specified pickup location).

In another example, a configuration file can specify that the dispatch system is to select a driver from a set of available drivers to provide the transport service for a user by determining the driver being closest to the pickup location of the user (e.g., having the shortest distance as compared to other available drivers) when performing the driver selection process for the user. Alternatively, a configuration file can specify that the dispatch system is to select a driver from a set of available drivers to provide the transport service for a user by determining the driver having the shortest estimated travel time to the pickup location of the user when performing the driver selection process for the user.

Hardware Diagrams

FIG. 3is a block diagram that illustrates a computer system upon which examples described herein may be implemented. For example, in the context ofFIG. 1, the system100may be implemented using one or more computer systems such as described byFIG. 3. The system100may also be implemented using a combination of multiple computer systems as described byFIG. 3.

In one implementation, a computer system300includes processing resources310, a main memory320, a read-only memory (ROM)330, a storage device340, and a communication interface350. The computer system300includes at least one processor310for processing information and the main memory320, such as a random access memory (RAM) or other dynamic storage device, for storing information and instructions to be executed by the processor310. The main memory320may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor310. The computer system300may also include the ROM330or other static storage device for storing static information and instructions for the processor310. The storage device340, such as a solid-state device, a magnetic disk, or an optical disk, is provided for storing information and instructions. For example, the storage device340can correspond to a computer-readable medium that stores feature management and feature control instructions for performing operations discussed with respect toFIGS. 1 through 2. In another example, the storage device340can store configuration data and user interface data, such as discussed with respect toFIGS. 1 through 2.

The communication interface350can enable the computer system300to communicate with one or more networks380(e.g., cellular network) through use of the network link (wireless and/or using a wire). Using the network link, the computer system300can communicate with a plurality of devices, such as the mobile computing devices of the clients and service providers. According to some examples, the computer system300can determine a change to be implemented to an attribute of the on-demand service system. The computer system300can also receive client and/or driver information352from the client and driver devices, respectively via the network link. The processor310can use the client and/or driver information352received from the devices (as well as other information) to determine which device(s) to implement the change to. The processor310can transmit, via the communication interface350over the network380, application controls354to the respective devices that have been identified as requiring the change. The application controls354, for example, can cause changes to be implemented to a designated service application on a client device(s) and/or a driver device(s).

The computer system300can also include a display device360, 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 mechanism370, such as a keyboard that includes alphanumeric keys and other keys, can be coupled to the computer system300for communicating information and command selections to the processor310. Other non-limiting, illustrative examples of input mechanisms370include a mouse, a trackball, touch-sensitive screen, or cursor direction keys for communicating direction information and command selections to the processor310and for controlling cursor movement on the display360.

Examples described herein are related to the use of the computer system300for implementing the techniques described herein. According to one example, those techniques are performed by the computer system300in response to the processor310executing one or more sequences of one or more instructions contained in the main memory320, such as feature management and feature control instructions. Such instructions may be read into the main memory320from another machine-readable medium, such as the storage device340. Execution of the sequences of instructions contained in the main memory320causes the processor310to 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.

FIG. 4is a block diagram that illustrates a mobile computing device upon which examples described herein may be implemented. In one example, a mobile computing device400may correspond to a mobile computing device, such as a cellular device that is capable of telephony, messaging, and data services. The mobile computing device400can correspond to a client device or a driver device. Examples of such devices include smartphones, handsets or tablet devices for cellular carriers. The mobile computing device400includes a processor410, memory resources420, a display device430(e.g., such as a touch-sensitive display device), one or more communication sub-systems440(including wireless communication sub-systems), input mechanisms450(e.g., an input mechanism can include or be part of the touch-sensitive display device), and one or more location detection mechanisms (e.g., GPS component)460. In one example, at least one of the communication sub-systems440sends and receives cellular data over data channels and voice channels.

The processor410is configured with software and/or other logic to perform one or more processes, steps and other functions described with implementations, such as described byFIGS. 1 through 2, and elsewhere in the application. The processor410is configured, with instructions and data stored in the memory resources420, to operate a designated service application as described inFIGS. 1 through 2. For example, instructions for operating the designated service application in order to display user interfaces415can be stored in the memory resources420of the mobile computing device400.

A client or service provider, for example, can operate a respective mobile computing device (such as the mobile computing device400) to operate the designated client or service provider application, respectively. The GPS component460can determine location information, such as the current location information465of the computing device400. The location information465can be wirelessly transmitted to the on-demand service system via the communication sub-systems440periodically and/or as part of a status message. For example, information about the mobile computing device400, which can include location information465, a device type, a user identifier associated with the device400, and/or a version information for the designated service application, can be transmitted periodically to the on-demand service system. In addition, a service provider can provide status messages (not shown inFIG. 4) to the on-demand service system to indicate, for example, that he or she is available to provide services (e.g., is on duty) or that he or she has completed a service and is idle.

The on-demand service system can receive the information from the mobile computing device400and when the system determines that change is to be implemented to an attribute of the on-demand service system, such as to the designated service application stored on the mobile computing device400, the system can transmit the application control445, via the communication sub-systems440, to the mobile computing device400. The processor410can process the application control445, which can cause a change to be implemented to the designated service application (e.g., turn on or off a user interface feature of the service application, provide a user with another option that was not previously available before the change, etc.).

For example, the processor410can provide a variety of content to the display430by executing instructions and/or applications that are stored in the memory resources420. One or more user interfaces415can be provided by the processor410, such as a user interface for the service application. The change can be implemented to a user interface415. WhileFIG. 4is illustrated for a mobile computing device, one or more examples may be implemented on other types of devices, including full-functional computers, such as laptops and desktops (e.g., PC).

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.