Claims:
CLAIMS
What is claimed is:
1. A method comprising:
executing, through at least one server, a computing platform engine; and
executing, through a data processing device communicatively coupled to the at least one server through a computer network, a component of the computing platform engine, characterized in that the computing platform engine:
ingests information associated with an account of a customer represented through the data processing device across a plurality of products offered by an entity associated with the at least one server and packs the ingested information into a single data store;
addresses an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the plurality of products directly through the single data store instead of fetching the subset of the ingested information from a plurality of data sources associated with the product, and
in response to the inquiry,
additionally fetches relevant contextual information associated with the account from the single data store based on analyzing at least one of: the inquiry and the subset of the ingested information,
determines whether the account originating the inquiry also participates in another product of the plurality of products, and
provides auxiliary information accessible through the computing platform engine component on the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product, the auxiliary information pertaining to the another product.
2. The method of claim 1, comprising the data processing device being one of: at least one other server and at least one client device.
3. The method of claim 1, comprising the computing platform engine ingesting the information associated with the account of the customer across the plurality of products through at least one experience Application Programming Interface (API).
4. The method of claim 1, comprising the computing platform engine enabling visualization of at least one of: the subset of the ingested information, the relevant contextual information and the auxiliary information through the computing platform engine component on the data processing device.
5. The method of claim 1, comprising distributedly executing the computing platform engine across a plurality of servers as the at least one server.
6. A server comprising:
a memory; and
a processor communicatively coupled to the memory,. characterized in that the processor executes instructions associated with a computing platform engine to:
ingest information associated with an account of a customer represented through a data processing device across a plurality of products offered by an entity associated with the server and pack the ingested information into a single data store, the data processing device communicatively coupled to the server through a computer network;
address an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the plurality of products directly through the single data store instead of fetching the subset of the ingested information from a plurality of data sources associated with the product, and
in response to the inquiry,
additionally fetch relevant contextual information associated with the account from the single data store based on analyzing at least one of: the inquiry and the subset of the ingested information,
determine whether the account originating the inquiry also participates in another product of the plurality of products, and
provide auxiliary information accessible through the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product, the auxiliary information pertaining to the another product.
7. The server of claim 6, wherein the processor executes instructions associated with the computing platform engine ingesting the information associated with the account of the customer across the plurality of products through at least one experience API.
8. The server of claim 6, wherein the processor executes instructions associated with the computing platform engine to enable visualization of at least one of: the subset of the ingested information, the relevant contextual information and the auxiliary information through the data processing device.
9. A system comprising:
at least one server executing a computing platform engine; and
a data processing device communicatively coupled to the at least one server through a computer network executing a component of the computing platform engine, characterized in that the computing platform engine:
ingests information associated with an account of a customer represented through the data processing device across a plurality of products offered by an entity associated with the at least one server and packs the ingested information into a single data store;
addresses an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the plurality of products directly through the single data store instead of fetching the subset of the ingested information from a plurality of data sources associated with the product, and
in response to the inquiry,
additionally fetches relevant contextual information associated with the account from the single data store based on analyzing at least one of: the inquiry and the subset of the ingested information,
determines whether the account originating the inquiry also participates in another product of the plurality of products, and
provides auxiliary information accessible through the computing platform engine component on the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product, the auxiliary information pertaining to the another product.
10. The system of claim 9, wherein the computing platform engine ingests the information associated with the account of the customer across the plurality of products through at least one experience API.
, Description:
CONTEXTUAL ADDRESSING OF AN INQUIRY FROM AN ACCOUNT PARTICIPATING IN A NUMBER OF PRODUCTS

FIELD OF TECHNOLOGY
[0001] This disclosure relates generally to transactional computing systems and, more particularly, to contextual addressing of an inquiry from an account participating in a number of products.

BACKGROUND
[0002] A customer of a banking institution may have one or more account(s) with the banking institution. Each account may be associated with one or more product(s) offered by the banking institution. The customer may be provided a capability to query each product associated with an account thereof through a web portal and/or an application executing on a data processing device thereof provided by the banking institution. However, the set of queries may not result in valuable data insights derivable by the customer.

SUMMARY
[0003] Disclosed are a method, a server and/or a system of contextual addressing of an inquiry from an account participating in a number of products.
[0004] In one aspect, a method includes executing, through one or more server(s), a computing platform engine, and executing, through a data processing device communicatively coupled to the one or more server(s) through a computer network, a component of the computing platform engine. The computing platform engine ingests information associated with an account of a customer represented through the data processing device across a number of products offered by an entity associated with the one or more server(s) and packs the ingested information into a single data store, and addresses an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the number of products directly through the single data store instead of fetching the subset of the ingested information from a number of data sources associated with the product.
[0005] In response to the inquiry, the computing platform engine additionally fetches relevant contextual information associated with the account from the single data store based on analyzing the inquiry and/or the subset of the ingested information, determines whether the account originating the inquiry also participates in another product of the number of products, and provides auxiliary information accessible through the computing platform engine component on the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product. The auxiliary information pertains to the another product.
[0006] In another aspect, a server includes a memory and a processor communicatively coupled to the memory. The processor executes instructions associated with a computing platform engine to ingest information associated with an account of a customer represented through a data processing device across a number of products offered by an entity associated with the server and pack the ingested information into a single data store. The data processing device is communicatively coupled to the server through a computer network. The processor also executes instructions associated with the computing platform engine to address an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the number of products directly through the single data store instead of fetching the subset of the ingested information from a number of data sources associated with the product.
[0007] Further, in response to the inquiry, the processor executes instructions associated with the computing platform engine to additionally fetch relevant contextual information associated with the account from the single data store based on analyzing the inquiry and/or the subset of the ingested information, determine whether the account originating the inquiry also participates in another product of the number of products, and provide auxiliary information accessible through the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product. The auxiliary information pertains to the another product.
[0008] In yet another aspect, a system includes one or more server(s) executing a computing platform engine; and a data processing device communicatively coupled to the one or more server(s) through a computer network executing a component of the computing platform engine. The computing platform engine ingests information associated with an account of a customer represented through the data processing device across a number of products offered by an entity associated with the one or more server(s) and packs the ingested information into a single data store; and addresses an inquiry from the account via the data processing device for a subset of the ingested information associated with a product of the number of products directly through the single data store instead of fetching the subset of the ingested information from a number of data sources associated with the product.
[0009] In response to the inquiry, the computing platform engine additionally fetches relevant contextual information associated with the account from the single data store based on analyzing the inquiry and/or the subset of the ingested information, determines whether the account originating the inquiry also participates in another product of the number of products, and provides auxiliary information accessible through the computing platform engine component on the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product. The auxiliary information pertains to the another product.
[0010] Other features will be apparent from the accompanying drawings and from the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The embodiments of this invention are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
[0012] Figure 1 is a schematic view of a computing system, according to one or more embodiments.
[0013] Figure 2 is a schematic view of a computing platform engine executing on a server of the computing system of Figure 1, according to one or more embodiments.
[0014] Figure 3 is a schematic view of an example inquiry initiated by an authorised user at a client device of the computing system of Figure 1.
[0015] Figure 4 is a process flow diagram detailing the operations involved in contextual addressing of an inquiry from an account participating in a number of products, according to one or more embodiments.
[0016] Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION
[0017] Example embodiments, as described below, may be used to provide a method, a server and/or a system of contextual addressing of an inquiry from an account participating in a number of products. Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments.
[0018] Figure 1 shows a computing system 100 (e.g., a distributed computing system), according to one or more embodiments. In one or more embodiments, computing system 100 may include a number of servers 1021-N communicatively coupled to one another through a computer network 104 (e.g., a Wide Area Network (WAN), a Local Area Network (LAN) and/or a short range network (e.g., WiFi®, Bluetooth®)). Other forms of computer network 104 are within the scope of the exemplary embodiments discussed herein. In one or more embodiments, computing system 100 may also include a number of client devices 1061-M communicatively coupled to the number of servers 1021-N through computer network 104. As implied above, computer network 104 may, in some embodiments, encompass a wide variety of computer networks.
[0019] In one or more embodiments, computing system 100 may be a traditional computing system with data centers, a cloud based computing system or a hybrid computing system. In one or more embodiments, computing system 100 may provide one or more computing environment(s) through a computing platform 150 thereof. Computing platform 150, as discussed herein, may encompass hardware, software, operating systems, applications including browsers and/or virtualized environments (e.g., virtual machines representing operating systems, virtual storage). Figure 1 shows a computing platform engine 170 (e.g., a comprehensive engine enabling capabilities and functionalities provided through computing platform 150) executing on a server 1021 and components (e.g., computing platform engine components 1702-N; computing platform engine components 1761-M) executing on other servers 1022-N and client devices 1061-M. Examples of client devices 1061-M may include but are not limited to desktop computers, laptops, notebooks, smart devices and mobile phones. Other client devices 1061-M including thin clients are within the scope of the exemplary embodiments discussed herein. Each client device 1061-M may represent a type of a channel for accessing capabilities provided through computing platform engine 170.
[0020] Each server 1021-N discussed above may be a standalone server or a network of servers configured to operate in conjunction with one another and capable of handling large sets of data. “Processor,” as used herein, may also refer to a number of processors configured to operate in conjunction with one another. In one or more embodiments, each server 1021-N may include a processor 1721-N communicatively coupled to a memory 1741-N. Figure 1 shows computing platform engine 170 stored in memory 1741; computing platform engine 170 may be executable through processor 1721. Similarly, computing platform engine components 1702-N and computing platform engine components 1762-M may be stored in corresponding memories to be executed on processors associated therewith.
[0021] Figure 1 also shows data sources 1901-R within computing system 100. In one or more embodiments, data sources 1901-R may include but are not limited to mainframes, Relative Database Management Systems (RDBMS), NoSQL databases, feeds, files, legacy systems, Software-as-a-Service (SaaS), a Management Information System (MIS) and an entitlement data server. In one or more embodiments, data sources 1901-R may be local to one or more servers 1021-N, local to one or more client devices 1061-M and/or external to both the one or more servers 1021-N and the one or more client devices 1061-M. An example data source 1901-R may include account information of authorised users 1921-M; each authorised user 1921-M may be at a client device 1061-M of computing system 100. It should be noted that client device 1061-M (e.g., a common computing resource) may be shared by multiple users and that one authorised user 1921-M per client device 1061-M discussed above is merely for illustrative purposes.
[0022] Other forms of information within data sources 1901-R are within the scope of the exemplary embodiments discussed herein. In one or more embodiments, one authorised user 1921-M may differ from another authorised user 1921-M in terms of roles within an entity or outside thereof. For example, one or more servers 1021-N may be associated with an example entity of a banking institution, and one or more client devices 1061-M may be associated with one or more authorised users 1921-M (e.g., customers of the banking institution, banking personnel). One or more other servers 1021-N may be associated with another example entity of a software service provider associated with computing platform engine 170. One or more other client devices 1061-M may also be associated with one or more other authorised users 1921-M (e.g., sales, pre-sales, testing and/or development team personnel associated with the another example entity of the software service provider).
[0023] Figure 2 shows computing platform engine 170, according to one or more embodiments. In one or more embodiments, computing platform engine 170 may be integrated with example products 2601-P of an entity 220. In one example, entity 220 may be a subscriber of capabilities provided through computing platform 150. In another example, entity 220 may be a financial technology product development company associated with server 1021 and executing computing platform engine 170 thereon. In one or more embodiments, one or more client device(s) 1061-M and/or one or more other server(s) 1022-N may be associated with a customer 250 (e.g., a banking institution, a customer of the banking institution, official staff of the banking institution) of entity 220. In some cases, computing platform engine 170 may be implemented on server 1021 associated with customer 250.
[0024] For example, one or more products 2601-P may help customer 250 optimize liquidity thereof. However, data associated with the aforementioned one or more products 2601-P may be extensive and may become overwhelming for an authorised user 1921-M at a client device 1061-M representing customer 250. Further, additional data from domains pertaining to other product(s) 2601-P may be unavailable to said authorised user 1921-M. In the case of authorised user 1921-M being a strategist on behalf of customer 250, the unavailability of the additional data may hamper decision making thereof. Also, costs in terms of fees, penalties and charges may be incurred by customer 250 in the course of developing insights with respect to a range of useful products 2601-P thereto. While customer 250 (or entity 220 on behalf of customer 250) may have an online portal through which management of products 2601-P is possible, no insights into efficacy of products 2601-P may be derivable
[0025] Further, authorised user 1921-M on behalf of customer 250 may be overwhelmed by domain complexity with respect to products 2601-P and may find experience therewith slow and/or fraught with complexity. Exemplary embodiments discussed herein solve the abovementioned problems through providing an ability to combine data from multiple product domain(s) quickly (e.g., in less than a second) and present said combined data in an intuitive way to authorised user 1921-M acting on behalf of customer 250. Also, exemplary embodiments may provide authorised user 1921-M with contextual data to help decision making on behalf of customer 250 while reducing cognitive load thereon. Concepts discussed herein may be applicable across many areas spanned by product(s) 2601-P (e.g., corporate banking products) where data may be deep and complex and may have the potential to influence decision making.
[0026] Unlike many applications that keep data tightly linked to a specific topic/product context, exemplary embodiments discussed herein may combine a single data store through intelligent inquiries to break down traditional silos and create a richer and more natural understanding of related data and product contexts. Referring back to Figure 2, computing platform engine 170 may include Application Programming Interfaces (APIs) 2021-K including experience APIs 2041-L. In one or more embodiments, computing platform 150/computing platform engine 170 may be architected in a way that enables the aforementioned experience APIs 2041-L to gather data spanning multiple product domains. Figure 2 shows experience APIs 2041-L gathering data 206 from multiple products 2601-P, according to one or more embodiments.
[0027] In one or more embodiments, computing platform engine 170 may ingest (e.g., through experience APIs 2041-L) data 206 from multiple sources (e.g., data sources 1901-R) associated with multiple products 2601-P and pack said ingested data 206 into a single data store 208 (e.g., in memory 1741 or as a standalone new data source (not shown)). In one or more embodiments, when authorised user 1921-M submits an inquiry 210 for information associated with a product 2601-P, said inquiry 210 may be satisfied directly through data 206 packed into the single data store 208 instead of leveraging one or more data sources 1901-R. In one or more embodiments, the satisfaction of inquiry 210 may be accompanied by the incorporation of associated information 212 (e.g., in data 206) indirectly/tangentially relevant thereto (e.g., automatically, based on analysis of inquiry 210 and/or the requested information) to provide a significantly contextual experience to authorised user 1921-M.
[0028] Figure 3 shows an example inquiry 210 initiated by authorised user 1921-M at a client device 1061-M thereof via computing platform engine component 1761-M. Here, authorised user 1921-M may perform an account balance inquiry as example inquiry 210. In response to inquiry 210, computing platform engine 170 (e.g., based on execution of an appropriate banking engine) may leverage account information 302 (e.g., stored in the single data store 208) pertaining to an account 3041-Q of a number of accounts 3041-Q of authorised user 1921-M with entity 220 associated with computing platform engine 170 and fetch the requested information 306 (e.g., available account balance) along with other relevant information 308 (e.g., cleared balance, date/time of last activity); the fetching of relevant information 308 may be automatic and/or based on computing platform engine 170 analyzing inquiry 210 and/or requested information 306. The aforementioned requested information 306 and relevant information 308 may come from the single data store 208.
[0029] In one or more embodiments, the number of accounts 3041-Q of authorised user 1921-M may be distributed across multiple products 2601-P of entity 220. In one or more embodiments, based on ingesting account information 302 from multiple data sources (e.g., data sources 1901-R) associated with the multiple products 2601-P and packing account information 302 into the single data store 208, computing platform engine 170 may enable minimizing data volume within computing platform 150 and a frequency of inquires on core processing engines thereon.
[0030] In one or more embodiments, computing platform engine 170 may additionally determine whether account 3041-Q originating inquiry 210 associated with a specific product 2601-P participates in any other product 2601-P associated with entity 220; this may also be done in response to inquiry 210. In one or more embodiments, if yes, authorised user 1921-M may be provided auxiliary information 310 (e.g., from the single data store 208) in addition to requested information 306 and relevant information 308 from the single data store 208; again, this may be done in response to inquiry 210. Here, auxiliary information 310 may be a link to navigate directly to instruments associated with other products 2601-P in which account 3041-Q originating inquiry 210 participates. In traditional implementations, analogous auxiliary information 310 may be available only through specific product inquiries. Here, multiple inquiries associated with multiple products may be initiated on multiple data sources in parallel and the results collated. Exemplary embodiments may solve efficiency related problems associated therewith through accessing the single data store 208.
[0031] As shown in Figure 3, in one or more embodiments, computing platform engine 170 may include a data visualization engine 320 to enable visualization of complex data (e.g., requested information 306, relevant information 308 and/or auxiliary information 310) via computing platform engine component 1761-M on client device 1061-M of authorised user 1921-M. For example, the aforementioned visualization may be enhanced through hover-over analytics and Key Performance Indicators (KPIs). These elements may also incorporate appropriate navigation links.
[0032] It should be noted that analogous authorised users may also be associated with servers 1022-N executing computing platform engine components 1702-N. All of the abovementioned discussion may also be applicable thereto. Further, as indicated above, computing platform engine 170 may be distributedly executed across one or more servers 1021-N. All reasonable variations are within the scope of the exemplary embodiments discussed herein.
[0033] Figure 4 shows a process flow diagram detailing the operations involved in contextual addressing of an inquiry (e.g., inquiry 210) from an account (e.g., account 3041-Q) participating in a number of products (e.g., more than one of products 2601-P), according to one or more embodiments. In one or more embodiments, operation 402 may involve executing, through one or more server(s) (e.g., server 1021), a computing platform engine (e.g., computing platform engine 170). In one or more embodiments, operation 404 may involve executing, through a data processing device (e.g., client device 1061-M) communicatively coupled to the one or more server(s) through a computer network (e.g., computer network 104), a component (e.g., computing platform engine component 1761-M) of the computing platform engine.
[0034] In one or more embodiments, the computing platform engine may ingest information (e.g., data 206) associated with the account (e.g., of customer 250) represented through the data processing device across the number of products offered by an entity (e.g., entity 220) associated with the one or more server(s) and pack the ingested information into a single data store (e.g., data store 208). In one or more embodiments, the computing platform engine may addresses the inquiry from the account via the data processing device for a subset of the ingested information (e.g., requested information 306) associated with a product of the number of products directly through the single data store instead of fetching the subset of the ingested information from a number of data sources (e.g., data sources 1901-R) associated with the product.
[0035] In one or more embodiments, in response to the inquiry, the computing platform engine may additionally fetch relevant contextual information (e.g., relevant information 308) associated with the account from the single data store based on analyzing the inquiry and/or the subset of the ingested information, may determine whether the account originating the inquiry also participates in another product of the number of products, and may provide auxiliary information (e.g., auxiliary information 310) accessible through the computing platform engine component on the data processing device from the single data store in addition to the subset of the ingested information and the relevant contextual information based on the determination of the additional participation of the account in the another product. In one or more embodiments, the auxiliary information may pertain to the another product.
[0036] It may be appreciated that the various systems, methods, and apparatus disclosed herein may be embodied in a non-transitory machine-readable medium (e.g., a hard disk, a Compact Disc (CD), a Digital Video Disc (DVD), a Blu-ray disc®) and/or a machine-accessible medium compatible with a data processing system (e.g., computing system 100, servers 1021-N), and/or may be performed in any order.
[0037] The structures and modules in the figures may be shown as distinct and communicating with only a few specific structures and not others. The structures may be merged with each other, may perform overlapping functions, and may communicate with other structures not shown to be connected in the figures.
[0038] Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.