Patent Application
20250217773
Various embodiments described herein provide for systems, methods, techniques, instruction sequences, and devices that facilitate the generation and management of communication workflows using tacit workflows.
In the realm of digital communication, systems often grapple with the management and generation of workflows that automate interactions based on user activities and scheduled events. A primary challenge in this field is the effective processing of these user actions and events to ensure users are guided through the appropriate steps of communication workflows. Additionally, maintaining an accurate record of users' progress and status within these workflows presents a complex task, requiring precise coordination and tracking.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. Some embodiments are illustrated by way of examples, and not limitations, in the accompanying figures.
The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the present disclosure. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments. It will be evident, however, to one skilled in the art that the present inventive subject matter can be practiced without these specific details.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present subject matter. Thus, the appearances of the phrase “in one embodiment” or “in an embodiment” appearing in various places throughout the specification are not necessarily all referring to the same embodiment.
For purposes of explanation, specific configurations, and details are set forth in order to provide a thorough understanding of the present subject matter. However, it will be apparent to one of ordinary skill in the art that embodiments of the subject matter described can be practiced without the specific details presented herein, or in various combinations, as described herein. Furthermore, well-known features can be omitted or simplified in order not to obscure the described embodiments. Various embodiments may be given throughout this description. These are merely descriptions of specific embodiments. The scope or meaning of the claims is not limited to the embodiments given.
Various embodiments include systems, methods, and non-transitory computer-readable media that facilitate generating and managing communication workflows using tacit workflows. Specifically, communication workflows refer to sequences of interactions and/or communication designed to engage with users. Various embodiments address the challenges of automating communications based on user actions and scheduled events, ensuring that users are directed through the correct steps of a communication workflow and that their progress is accurately tracked.
In various embodiments, a communication workflow can be configured by users (e.g., customer-defined workflows) through a user interface on a device or automatically generated by the system (e.g., tacit workflows) based on predefined settings (e.g., campaign setting). Communication workflows are part of a larger structure referred to as a journey, as a journey can include multiple communication workflows that run concurrently. Each step within a communication workflow is associated with specific actions and conditions. When these conditions are met, the corresponding actions are triggered.
In various embodiments, a journey can include one or more tacit workflows and one or more customer-defined workflows. Tacit workflows run concurrently with customer-defined workflows within a given journey but remain invisible to the user. They are automatically generated by the system based on predefined settings, such as campaign settings, to realize the tacit behavior associated with a customer-defined workflow in the same journey. An example of a tacit workflow is an exit flow. In a scenario involving an abandoned shopping cart, the exit flow for an item is generated (or initiated or activated) when the item is added to a shopping cart. The exit workflow is simultaneously generated to ensure an item in a shopping cart is purchased within a set timeframe while the main workflow is waiting for the timeout duration to elapse. If the item is purchased within a set timeframe, such as 7 days, the event of the purchase triggers an exit from the associated customer-defined workflow, regardless of the user's current position in the customer-defined workflow. This illustrates how tacit workflows can influence the behavior of the journey without direct user interaction.
In various embodiments, customers can create customer-defined workflows using an editor, such as the What You See Is What You Get (WYSIWYG) editor. This editor allows the creation of flows through a visual interface that includes nodes and edges, representing different steps and the transitions between them. Unlike tacit workflows, customer-defined workflows are visible to the user and can be customized directly according to the user's needs.
Various embodiments allow a user to be in one step of the customer-defined workflow at any given epoch. However, for effective tracking and management of the overarching workflow (e.g., a journey), a user can be involved in multiple steps within the associated tacit workflows. This dual engagement in both customer-defined and tacit workflows ensures that the system can react to exceptional scenarios within the journey, such as a rescheduled appointment or an abandoned cart, without requiring manual intervention from the user.
In various embodiments, a tacit workflow can be generated (or activated) to handle the case when an appointment is rescheduled. This workflow reacts to detection of a rescheduling event. This rescheduling event both resets the state of the customer-defined workflow within the same journey and becomes the input of the customer-defined workflow going forward. So if an appointment is rescheduled from April 30th to May 5th, the underlying plumbing (e.g., timers) for April 29th (1 day before April 30th) is discarded (or torn down) before restarting the flow for May 5th with similar resources set up for a May 4th email.
In various embodiments, the runtime is able to apply the same event to multiple steps in the event processing loop. In the rescheduling use case, if the rescheduling event is determined to be the same as the scheduling event except for the change of the duration to remind before an appointment, the event may be applied from the reset workflow into the customer-defined workflow, capturing the updated duration (d1aseconds) and using that in the customer-defined workflow as if it were the event initiating it at the time of the generation (or initiation).
In various embodiments, the system is able to call out to external systems (e.g., a Reference Data Service) and augment the context passed and updated between steps in a communication workflow. In a use case as illustrated in
Overall, various embodiments provide a robust framework for managing communication workflows in a way that automates responses to user actions and scheduled events, tracks user progress through various steps, and reacts to exceptional scenarios within a journey. Various embodiments streamline the interaction process, making it more efficient and responsive to the dynamic nature of user engagement.
Various embodiments include systems, methods, and non-transitory computer-readable media that facilitate generating and managing communication workflows using event filters. Specifically, communication workflows refer to sequences of interactions and/or communication designed to engage with users. A communication workflow can include one or more steps configured by a user via a user interface of a device. A journey can include one or more workflows. Each step of a communication workflow can be associated with one or more actions and one or more conditions that trigger the one or more actions. A communication workflow can be associated with metadata that is used to reference another step within the workflow, or reference one or more steps in another workflow. Various embodiments provide user-friendly interfaces to design and manage flows of interactions across various communication channels, such as SMS messages, voice calls, email, etc. Under this approach, users can automate interactions through predefined communication workflows to set up automated responses, reminders, and/or notifications based on user behavior and/or triggers. Further, various embodiments provide customized communication based on user actions and/or preferences to enhance the user experience, leading to higher conversion rates for various goals, including sales, user sign-ups, etc.
In various embodiments, an event filter filters incoming messages based on definitions of communication workflows and relays the qualified messages (also referred to as events or qualified events) to the corresponding state machines for downstream processing. Specifically, a data management system detects one or more events. Each event can include (or be associated with) a state object that indicates a state of a user and/or a state of an action associated with a user. The data management system uses one or more event filters to map the one or more events to one or more communication workflows based on the content of the one or more events. A journey can include one or more communication workflows. The mapping of the one or more events includes determining that the content of the one or more events satisfies the definitions of the journeys. In various embodiments, the data management system identifies a state machine associated with a journey. A state machine can refer to a computational model that represents different states of complex systems and/or communication processes and the transitions between those states based on certain events or conditions. A state machine can change (or transition) from one state to another in response to inputs. State machines can help manage communication workflows and provide a structured way to design, implement, and manage complex workflows by defining the possible states, the conditions triggering state transitions, and the actions to be taken in each state. For example, a state machine can be used to model various states (e.g., initiating call, ringing, connected, on hold, ended) of a call when building a phone call application using the example data system 100 described herein. Each of these states can be associated with actions, triggers, and conditions that determine how the call progresses from one state to another. Such a progression determination can be made based on user input, time limits, or events triggered by the data system described herein.
In various embodiments, the data management system uses a state machine to process an event (e.g., a filtered event) based on the associated state object in accordance with one or more steps defined for a journey. Filtered events can be saved in a log of events (e.g., Kafka topic) with a predetermined retention period (e.g., 24 hours).
In various embodiments, a single event (e.g., a filtered event) can be mapped to a plurality of journeys. The data management system can use one or more state machines to process one or more steps defined for each of the plurality of journeys.
In various embodiments, each step in a journey can be associated with metadata that is used to reference another step within the journey or a step in another journey. A state machine can be used to model a plurality of states associated with a user, a system, a communication workflow, etc.
In various embodiments, a journey can include one or more steps sequentially arranged in a logical order. A journey can allow a user to trigger an operation associated with a step of the journey once an operation associated with a previous step of the journey has been triggered. In various embodiments, a journey (also referred to as a communication workflow) can be configured and managed by a user via a user interface of a device.
In various embodiments, an event can be a system-generated event or a user-triggered event. In various embodiments, the data management system determines a current step in a journey that matches a user-triggered event. The data management system identifies a subsequent step from the journey based on the current step and uses a state machine to initiate an operation associated with the subsequent step based on the satisfaction of one or more conditions of the current step. The satisfaction of one or more conditions of the current step dictates how an entity progresses from the current step to the subsequent step. For example, a user-trigger event is detected and determined that the event is related to an action, such as a user abandoning a shopping cart. The data management system uses an event filter to map the event to a journey associated with the user. In accordance with the steps defined for the journey, the system determines the user's current step (e.g., checkout started) and one or more conditions to trigger a subsequent step. In this example, the user abandoning a shopping cart can be a condition to trigger a subsequent step (e.g., awaiting payments). Based on the determination, the data management system uses a state machine that handles the journey to initiate one or more actions associated with the subsequent step. An example of such an action can be transmitting one or more follow-up messages to the user with relevant product information.
In various embodiments, the data management system detects an event (e.g., a filtered event) associated with an entity (e.g., a user). Upon determining, based on the content of the event, that the event does not map to any definition (or any state machine) of a journey associated with the entity, the data management system generates a state machine based on the event. The generated state machine can model each step in the journey associated with the entity and handle one or more journeys to be configured by the entity. The handling of a journey can include initiating an operation associated with each step based on the current state of the entity.
In various embodiments, in order to map an event to a journey based on the content of the event, the data management system can use a software library to match a plurality of rules against the content of the event. The plurality of rules can be user-defined rules. The software library allows users to build applications that match a number of rules against events at a high processing speed (e.g., several hundred thousand events per second). Both events and rules can be JavaScript Object Notation (JSON) objects, but rules can additionally be expressed through an inbuilt query language that describes custom matching patterns.
A profile's (e.g., user profile) trip through a journey shall clearly define where a user is in a journey. At no point should a “profile and epoch” pair be simultaneously in multiple places (e.g., steps) in a given journey, or in a user-defined part of a given journey. In other words, each user can have one journey state (per user-defined concurrency criteria, for example), and each journey state can have one epoch at a time (for a given concurrency key). Epoch can be represented by an epoch object created upon entering a journey, and maintained until a user is deemed to have exited from the journey.
In various embodiments, upon determining that an event is mapped to a journey, the data management system places an entity (e.g., a user) in a current step in the journey based on a state object of the event (or a state object of the journey). The data management system evaluates one or more factors to determine that the entity is not simultaneously placed in another step of the journey. One or more factors can correspond to one or more of, without limitation, the evaluation of memberships, setting of evaluation windows, setting of priorities, existing entities, moving of profiles, and support analytics.
In various embodiments, in response to determining that the entity (e.g., user) is not simultaneously placed in another step of the journey, the data management system uses a state machine to process the event based on an operation associated with a step subsequent to the current step in the journey.
In various embodiments, the data management system updates a profile associated with a user based on the processing of the event.
In various embodiments, the data management system determines an event does not map to any journey associated with an entity (e.g., a user). Based on the determination, the data management system discards the event and/or passes the event to another system and/or component for processing.
In various embodiments, the data management system identifies one or more attributes (e.g., event properties) of an event (e.g., filtered event). Upon identifying a journey associated with the event, the data management system stores the one or more attributes of the event in the journey. Attributes of an event can include contextual data associated with the user profile, such as journey identifier, step identifier, timestamp data, etc.
Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the appended drawings. The present disclosure may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein.
The server system 108 provides server-side functionality via the network 106 to the client software application 104. While certain functions of the data system 100 are described herein as being performed by the data management system 122 on the server system 108.
It will be appreciated that the location of certain functionality within the server system 108 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the server system 108, but to later migrate this technology and functionality to the client software application 104.
The server system 108 supports various services and operations that are provided to the client software application 104 by the data management system 122. Such operations include transmitting data from the data management system 122 to the client software application 104, receiving data from the client software application 104 to the system 122, and the system 122 processing data generated by the client software application 104. Data exchanges within the data system 100 may be invoked and controlled through operations of software component environments available via one or more endpoints, or functions available via one or more user interfaces of the client software application 104, which may include web-based user interfaces provided by the server system 108 for presentation at the client device 102.
With respect to the server system 108, each of an Application Program Interface (API) server 110 and a web server 112 is coupled to an application server 116, which hosts the data management system 122. The application server 116 is communicatively coupled to a database server 118, which facilitates access to a database 120 that stores data associated with the application server 116, including data that may be generated or used by the data management system 122.
The API server 110 receives and transmits data (e.g., API calls, commands, requests, responses, and authentication data) between the client device 102 and the application server 116. Specifically, the API server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the client software application 104 in order to invoke the functionality of the application server 116. The API server 110 exposes various functions supported by the application server 116 including, without limitation: user registration; login functionality; data object operations (e.g., generating, storing, retrieving, encrypting, decrypting, transferring, access rights, licensing, etc.); and user communications.
Through one or more web-based interfaces (e.g., web-based user interfaces), the web server 112 can support various functionality of the data management system 122 of the application server 116.
The application server 116 hosts a number of applications and subsystems, including the data management system 122, which supports various functions and services with respect to various embodiments described herein. The application server 116 is communicatively coupled to a database server 118, which facilitates access to database(s) 120 that stores data associated with the data management system 122.
The event detecting component 210 is configured to detect one or more events associated with one or more entities (e.g., users). An event can include (or be associated with) a state object that indicates a state of a user and/or a state of an action associated with a user. An event can be a system-generated event or a user-triggered event.
The event mapping component 220 is configured to map one or more events to one or more communication workflows based on the content of the one or more events. A journey can include one or more workflows. The mapping of the one or more events includes determining that the content of the one or more events satisfies the definitions of the journeys.
The state machine identifying component 230 is configured to identify one or more state machines associated with one or more journeys. A state machine can refer to a computational model that represents different states of complex systems and/or communication processes and the transitions between those states based on certain events or conditions.
The workflow generating component 240 is configured to generate one or more communication workflows (e.g., customer-defined workflows, tacit workflows). A tacit workflow can be generated based on settings (e.g., campaign settings) associated with a journey or a customer-defined workflow in a journey.
The workflow processing component 250 is configured to use state machines to process one or more tacit workflows based on settings (e.g., campaign settings) associated with a journey or a customer-defined workflow in a journey. The workflow processing component 250 is configured to use state machines to process one or more customer-defined workflows based on definitions of one or more journeys.
In various embodiments, the customer-defined workflow runs concurrently with the tacit workflow within the journey. A customer-defined workflow is configured by a customer associated with the entity or by the entity associated with the event. A tacit workflow is automatically generated by the system based on one or more settings (e.g., campaign) associated with the customer-defined workflow in the journey.
In various embodiments, a detected event can include contextual data that can be referenced by (and/or passed between) one or more steps in the customer-defined workflow and by one or more steps in the tacit workflow. Examples of contextual data include an item identifier, a timer identifier, an appointment identifier, and a time duration to remind before an appointment. In various embodiments, contextual data can be augmented via a call out to external systems (e.g., a Reference Data Service).
In various embodiments, upon (or in response to) determining that the content of an event satisfies a definition of a journey, a processor maps the event to the customer-defined workflow in the journey.
In various embodiments, a processor generates a tacit workflow based on contextual data (e.g., item identifier, timer identifier, appointment identifier, and duration to remind before an appointment) included in a detected event.
In various embodiments, a processor determines that the event does not correspond to a rescheduling event. In response to determining that the event is not the rescheduling event, a processor generates a tacit workflow (e.g., an exit workflow) in the journey based on one or more settings (e.g., campaign) associated with the customer-defined workflow in the journey.
In various embodiments, a processor identifies one or more state machines associated with one or more journeys. A state machine can refer to a computational model that represents different states of complex systems and/or communication processes and the transitions between those states based on certain events or conditions. State machines can help manage communication workflows and provide a structured way to design, implement, and manage complex workflows by defining the possible states, the conditions triggering state transitions, and the actions to be taken in each state.
In various embodiments, a processor uses one or more state machines to process one or more communication workflows (e.g., customer-defined workflow, exit workflow, reset workflow) based on one or more detected events described herein.
Though not illustrated, method 300 can include an operation where a graphical user interface can be displayed (or caused to be displayed) by the hardware processor. For instance, the operation can cause a client device (e.g., the client device 102 communicatively coupled to the data management system 122) to display the graphical user interface. This operation for displaying the graphical user interface can be separate from operations 302 through 308 or, alternatively, form part of one or more of operations 302 through 308.
Though not illustrated, method 400 can include an operation where a graphical user interface can be displayed (or caused to be displayed) by the hardware processor. For instance, the operation can cause a client device (e.g., the client device 102 communicatively coupled to the data management system 122) to display the graphical user interface. This operation for displaying the graphical user interface can be separate from operations 402 through 410 or, alternatively, form part of one or more of operations 402 through 410.
Though not illustrated, method 500 can include an operation where a graphical user interface can be displayed (or caused to be displayed) by the hardware processor. For instance, the operation can cause a client device (e.g., the client device 102 communicatively coupled to the data management system 122) to display the graphical user interface. This operation for displaying the graphical user interface can be separate from operations 502 through 508 or, alternatively, form part of one or more of operations 502 through 508.
In various embodiments, a user can define the conditions and/or events that trigger transitions that cause progression from one state to another handled by a state machine. For example, if a user is transitioned from a “pending” state to a “sending” state, a condition can be the user triggering the sending action. If there are time-dependent transitions (e.g., waiting for a response), timeouts may be configured to handle cases where the expected event fails to occur within a specified timeframe.
In various embodiments, the conditions and/or events can be determined based on the content of filtered events described herein. Filtered events can correspond to actions taken by users (e.g., user-triggered events) or by the system(s) (e.g., system-generated events).
In various embodiments, upon determining, based on the content of the event, that the event does not map to any definition of a journey associated with the entity, the processor generates a state machine based on the event. The generated state machine can model each step in one or more journeys to be configured by the entity and handle transitions from one step to another. The transitions can be handled by initiating one or more operations associated with a subsequent step based on the entity's current state.
Though not illustrated, method 600 can include an operation where a graphical user interface can be displayed (or caused to be displayed) by the hardware processor. For instance, the operation can cause a client device (e.g., the client device 102 communicatively coupled to the data management system 122) to display the graphical user interface. This operation for displaying the graphical user interface can be separate from operations 602 through 606 or, alternatively, form part of one or more of operations 602 through 606.
Though not illustrated, method 700 can include an operation where a graphical user interface can be displayed (or caused to be displayed) by the hardware processor. For instance, the operation can cause a client device (e.g., the client device 102 communicatively coupled to the data management system 122) to display the graphical user interface. This operation for displaying the graphical user interface can be separate from operations 702 through 712 or, alternatively, form part of one or more of operations 702 through 712.
In various embodiments, customers can create customer-defined workflows using an editor, such as the What You See Is What You Get (WYSIWYG) editor. This editor allows the creation of flows through a visual interface that includes nodes and edges, representing different steps and the transitions between them. Unlike tacit workflows, customer-defined workflows are visible to the user and can be customized directly according to the user's needs.
Various embodiments allow a user to be in one step of the customer-defined workflow at any given epoch. However, for effective tracking and management of the overarching workflow (e.g., a journey), a user can be involved in multiple steps within the associated tacit workflows. This dual engagement in both customer-defined and tacit workflows ensures that the system can react to exceptional scenarios within the journey, such as a rescheduled appointment or an abandoned cart, without requiring manual intervention from the user.
As shown, a step, such as step 808 (Wait 7 days), is able to reference data points (e.g., contextual data, such as the 7-day timer) from another step (e.g., step 810) in the workflow. The data management system (e.g., the data management system 122, 200 manages the persistence of referenced data points, obviating the need of namespacing similarly named data from different steps.
In various embodiments, contextual data is stable for the duration of the workflow. Data can be explicitly mutated as step definitions call for it (Added Item to Cart in this case).
Workflows can have multiple timelines internally. In this case, the customer defined a timeline (on the left) using a WYSIWYG canvas to describe the sequence of events and actions to take on them (send a coupon after 7 days of inactivity in the cart). In parallel, we can create one or more concurrent workflows (e.g., tacit workflows) that realize the tacit behavior of the workflow. In the abandoned cart use case, the exit workflow and the customer-defined workflow are simultaneously generated (or activated) to ensure that if the item is purchased while the exit workflow is waiting for the timeout duration to elapse, regardless of which step the user is in at any point in time, the customer-defined workflow is terminated (or exited).
The customer-defined workflow 902, the reset workflow 904, and the exit workflow 906 are processed concurrently (or in parallel). An exit from the exit workflow 906 causes the termination of the customer-defined workflow 902.
In various embodiments, a rescheduling event both resets the state of the customer-defined workflow 902 and becomes the input of the customer-defined workflow going forward. For example, if an appointment is rescheduled from April 30th to May 5th, the underlying plumbing (e.g., timers) for April 29th (1 day before April 30th) is discarded (or torn down) before restarting the flow for May 5th with similar resources set up for a May 4th email.
In various embodiments, the runtime is able to apply the same event to multiple steps in the event processing loop. In the rescheduling use case, if the rescheduling event is determined to be the same as the scheduling event except for the change of the duration to remind before an appointment, the event may be applied from the reset workflow into the customer-defined workflow, capturing the updated duration (d1aseconds) and using that in the customer-defined workflow as if it was the event initiating it afresh.
In various embodiments, the system is able to call out to external systems (e.g., a Reference Data Service 908) and augment the contextual data passed between steps in a workflow. As shown in
Enter a new journey: If the match (or mapping) is on the entry step for a journey and no epoch is generated, the data management system can create an epoch for the journey based on the event data (e.g., the data content of the event).
Transition to new steps in a journey the user has already entered: If the match (or mapping) is on non-entry steps for a journey, and the epoch for the journey has the matching step as one of the next steps (e.g., subsequent steps), the data management system can apply the event data to the epoch on the journey.
No valid transitions: The event is ignored, discarded, or passed to another system if neither of the above checks succeeds.
Data store 1010 can be a low-latency key-value store that stores various data described herein, including event, epoch, and profile data.
In various embodiments, in order to map an event to a journey based on the content of the event, the data management system can use a software library (e.g., event ruler 1106) to match a plurality of rules against the content of the event. The plurality of rules can be user-defined rules. The event ruler 1106 can be a component or an external tool used by the event filter 1102 to perform the relevant operations described herein. The event ruler 1106 allows users to build applications that match a number of rules against events at a high processing speed. Both events and rules can be JSON objects. Rules can additionally be expressed through an inbuilt query language that describes custom matching patterns.
In the example architecture of
The operating system 1214 may manage hardware resources and provide common services. The operating system 1214 may include, for example, a kernel 1228, services 1230, and drivers 1232. The kernel 1228 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1228 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1230 may provide other common services for the other software layers. The drivers 1232 may be responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1232 may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.
The libraries 1216 may provide a common infrastructure that may be utilized by the applications 1220 and/or other components and/or layers. The libraries 1216 typically provide functionality that allows other software modules to perform tasks in an easier fashion than by interfacing directly with the underlying operating system 1214 functionality (e.g., kernel 1228, services 1230, or drivers 1232). The libraries 1216 may include system libraries 1234 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 1216 may include API libraries 1236 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1216 may also include a wide variety of other libraries 1238 to provide many other APIs to the applications 1220 and other software components/modules.
The frameworks 1218 (also sometimes referred to as middleware) may provide a higher-level common infrastructure that may be utilized by the applications 1220 or other software components/modules. For example, the frameworks 1218 may provide various graphical user interface functions, high-level resource management, high-level location services, and so forth. The frameworks 1218 may provide a broad spectrum of other APIs that may be utilized by the applications 1220 and/or other software components/modules, some of which may be specific to a particular operating system or platform.
The applications 1220 include built-in applications 1240 and/or third-party applications 1242. Examples of representative built-in applications 1240 may include, but are not limited to, a home application, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, or a game application.
The third-party applications 1242 may include any of the built-in applications 1240, as well as a broad assortment of other applications. In a specific example, the third-party applications 1242 (e.g., an application developed using the Android™ or iOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as iOS™, Android™, or other mobile operating systems. In this example, the third-party application 1242 may invoke the API calls 1224 provided by the mobile operating system, such as the operating system 1214, to facilitate the functionality described herein.
The applications 1220 may utilize built-in operating system functions (e.g., kernel 1228, services 1230, or drivers 1232), libraries (e.g., system libraries 1234, API libraries 1236, and other libraries 1238), or frameworks/middleware 1218 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems, interactions with a user may occur through a presentation layer, such as the presentation layer 1244. In these systems, the application/module “logic” can be separated from the aspects of the application/module that interact with the user.
Some software architectures utilize virtual machines. In the example of
The machine 1300 may include processors 1310, memory 1330, and I/O components 1350, which may be configured to communicate with each other such as via a bus 1302. In an embodiment, the processors 1310 (e.g., a hardware processor, such as a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1312 and a processor 1314 that may execute the instructions 1316. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although
The memory 1330 may include a main memory 1332, a static memory 1334, and a storage unit 1336 including machine-readable medium 1338, each accessible to the processors 1310 such as via the bus 1302. The main memory 1332, the static memory 1334, and the storage unit 1336 store the instructions 1316 embodying any one or more of the methodologies or functions described herein. The instructions 1316 may also reside, completely or partially, within the main memory 1332, within the static memory 1334, within the storage unit 1336, within at least one of the processors 1310 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1300.
The I/O components 1350 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1350 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1350 may include many other components that are not shown in
In further embodiments, the I/O components 1350 may include biometric components 1356, motion components 1358, environmental components 1360, or position components 1362, among a wide array of other components. The motion components 1358 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components 1360 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1362 may include location sensor components (e.g., a Global Positioning System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The I/O components 1350 may include communication components 1364 operable to couple the machine 1300 to a network 1380 or devices 1370 via a coupling 1382 and a coupling 1372, respectively. For example, the communication components 1364 may include a network interface component or another suitable device to interface with the network 1380. In further examples, the communication components 1364 may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1370 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).
Moreover, the communication components 1364 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1364 may include radio frequency identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as
Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1364, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.
Certain embodiments are described herein as including logic or a number of components, modules, elements, or mechanisms. Such modules can constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A “hardware module” is a tangible unit capable of performing certain operations and can be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) are configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In various embodiments, a hardware module is implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module can include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module can be a special-purpose processor, such as a field-programmable gate array (FPGA) or an ASIC. A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module can include software encompassed within a general-purpose processor or other programmable processor. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) can be driven by cost and time considerations.
Accordingly, the phrase “module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where a hardware module comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware modules) at different times. Software can accordingly configure a particular processor or processors, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules can be regarded as being communicatively coupled. Where multiple hardware modules exist contemporaneously, communications can be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between or among such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module performs an operation and stores the output of that operation in a memory device to which it is communicatively coupled. A further hardware module can then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules can also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein can be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented module” refers to a hardware module implemented using one or more processors.
Similarly, the methods described herein can be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method can be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines 1300 including processors 1310), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). In certain embodiments, for example, a client device may relay or operate in communication with cloud computing systems and may access circuit design information in a cloud environment.
The performance of certain of the operations may be distributed among the processors, not only residing within a single machine 1300, but deployed across a number of machines 1300. In some example embodiments, the processors 1310 or processor-implemented modules are located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented modules are distributed across a number of geographic locations.
The various memories (i.e., 1330, 1332, 1334, and/or the memory of the processor(s) 1310) and/or the storage unit 1336 may store one or more sets of instructions 1316 and data structures (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions 1316), when executed by the processor(s) 1310, cause various operations to implement the disclosed embodiments.
As used herein, the terms “machine-storage medium,” “device-storage medium,” and “computer-storage medium” mean the same thing and may be used interchangeably. The terms refer to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions 1316 and/or data. The terms shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium” discussed below.
In various embodiments, one or more portions of the network 1380 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a LAN, a wireless LAN (WLAN), a WAN, a wireless WAN (WWAN), a metropolitan-area network (MAN), the Internet, a portion of the Internet, a portion of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, the network 1380 or a portion of the network 1380 may include a wireless or cellular network, and the coupling 1382 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular or wireless coupling. In this example, the coupling 1382 may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long-Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.
The instructions may be transmitted or received over the network using a transmission medium via a network interface device (e.g., a network interface component included in the communication components) and utilizing any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions may be transmitted or received using a transmission medium via the coupling (e.g., a peer-to-peer coupling) to the devices 1370. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure. The terms “transmission medium” and “signal medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by the machine, and include digital or analog communications signals or other intangible media to facilitate communication of such software. Hence, the terms “transmission medium” and “signal medium” shall be taken to include any form of modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
The terms “machine-readable medium,” “computer-readable medium,” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure. The terms are defined to include both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. For instance, an embodiment described herein can be implemented using a non-transitory medium (e.g., a non-transitory computer-readable medium).
Throughout this specification, plural instances may implement resources, components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. The terms “a” or “an” should be read as meaning “at least one,” “one or more,” or the like. The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to,” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
It will be understood that changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure.
This patent application is a continuation-in-part of U.S. patent application Ser. No. 18/400,924, filed on Dec. 29, 2023, which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18400924 | Dec 2023 | US |
| Child | 18758820 | US |
