DESC:Form 2
The Patent Act 1970
(39 of 1970)
AND
Patent Rules 2003
Complete Specification
(Sec 10 and Rule 13)

Title: Method, System and Apparatus for interconnecting sellers and buyers
Applicant(s) Name Nationality Address
Nusecond Technologies Private Limited India

No. 562/640, 3rd Floor, Janardhana Towers, Bilekahalli, Bannerghatta Main Road, Bangalore-560076, Karnataka, India.

The following specification particularly describes the invention and manner in which it is to be performed

DESCRIPTION
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate generally interconnected computer system and more specifically to method, system and apparatus for interconnecting sellers and buyers.
RELATED ART
[0002] Local retailers and multi-brand sellers have traditional showrooms and commercial outlets providing a major channel for consumers. These outlets provide small, mid and large scale product brands, goods etc., and catering needs of people. Further, the retail websites provides a platform to the consumers to purchase the products, goods over internet.
[0003] Even though, the emergence of retail websites/online purchase websites has been appreciated, the local/neighborhood retailers are staying away in the online market. Also, the penetration and market of online purchases remains limited for local and regional retailers. The local and regional market faces a barrier which is mainly due to the discount demands by online purchasers who wishes to enhance their consumer base, IT complexity, investment of huge capital and lack of systematic product cataloging with inventory management. In the consumer front, the ease of purchasing with the physical feel of the product is reducing eventually.
[0004] There is a need for a system that efficiently connecting local consumer and regional retailers to ease transaction of buying and selling products offered by the regional retailers to the consumers.
SUMMARY
[0005] According to one aspect, a system for interconnecting set of first terminal devices and set of second terminal devices for engaging in sale and purchase transaction of a product comprises, a first profile collector, a second profile collector, an offer collector, a strategy engine, a deal engine, a product selector, an intent recorder and an intent bridge. In an embodiment, the first profile collector collects set of first profiles from a first terminal devices and attributing the first set of profiles to activity of purchase. The second profile collector collects set of second profiles from a second terminal devices and attributing the second set of profile to activity of sale. The offer collector collects first offer value and second offer value from the second terminal devices for the product. The strategy engine which determines first price from first offer value and determining a second price based on a number of transactions performed over a first time period. The deal engine displays the first price against the product and also displays the second price when first price is not selected. The product selector displays multiple selection parameters enabling selection of the product when first set of parameters are selected. The intent recorder which records selection of second set of parameters which are part of the first set of parameters and the intent bridge shares the second set of parameter with multiple external devices.
BRIEF DESCRIPTION OF DRAWINGS
[0006] FIG. 1 is block diagram of an example system in an embodiment.
[0007] FIG. 2 is a block diagram of an example interconnecting server.
[0008] FIG. 3 illustrates the example user interface presented on the second terminal device 110 by the second profile collection engine for collecting the second profile data.
[0009] FIG. 4 illustrates example user interface enabling collection of information.
[0010] FIG. 5 is an example user interface presented on the second terminal device by the offer collector for collecting offers as part of the second input data.
[0011] FIG. 6 is an example user interface presented on the second terminal devices by the deal & sale manager as part of second information and second input data.
[0012] FIG. 7 is a block diagram illustrating the manner in which interconnecting server presents and collects the data on the second terminal devices in an embodiment.
[0013] FIG. 8 illustrates the example user interface presented on the first terminal device by the profile collection engine for collecting the first profile data.
[0014] FIG. 9-13 illustrates the manner in which the selection manager enables selection and monitors the selections in one embodiment.
[0015] FIG. 14 is an example user interface presented on the first terminal devices for collecting bargain inputs in an embodiment.
[0016] FIG. 15 is an example user interface presented on the first terminal devices by the deal & purchase manager as part of first information and first input data.
[0017] FIG. 16 is a block diagram illustrating an example processing in one embodiment.
[0018] FIG. 17 is a block diagram illustrating the manner in which the deal strategy engine enables participation plurality of second terminal devices in one embodiment.
[0019] FIG. 18 illustrates example aggregated bargains received from first terminal devices.
DETAILED DESCRIPTION OF THE PREFERRED EXAMPLES
[0020] FIG. 1 is block diagram of an example system in an embodiment. The block diagram, shown comprising first terminal devices 105, second terminal devices 110, service providing devices 115, communication networks (120, 125 and 130), an interconnecting server 135 and a data storage 140.
[0021] First terminal devices 105 receive first input data through I/O interface (provided on each first terminal device like, mouse, keyboard, touch screen etc.,) and send first input data to the interconnecting server 135 through the communication network 120. First terminal devices 105 may receive preprocessed information content from the interconnecting server 135 and display on a display screen of the first terminal device 105 to collect the first input data suitably. First input data may comprise first profile data, first selections, first options, first location, first queries etc. the first input data is indexed to a first index value. The first index value is listed under buying, receiving, consuming, owning interest etc.
[0022] First options may comprise the information that determines the action to be performed on the interconnecting server 135. For example, the first options may comprise buy, bid, wait, store, save, deal, bargain an any other option generally required by a consumer or sought by consumer in expectation of a benefit from a purchase. First type of queries may comprise information to obtain desired data from the interconnecting server 135. The first type of query may be configured to extract the data such as availability of product, pricing, time of delivery, product status, offers, location of availability and sourcing agency.
[0023] Second terminal devices 110 receive second input data through I/O interface (provided on each second terminal device like, mouse, keyboard, touch screen etc.,) and send second input data to the interconnecting server 135 through the communication network 125. Second terminal devices 110 may receive preprocessed information content from the interconnecting server 135 and display on a display screen of the second terminal device 110 to collect the second input data suitably. Second input data may comprise second profile data, stock data, second selections, second location, second options, second queries etc. The second input data is indexed to second index value. The second index value is associated to selling, sourcing, make available, delivering interest etc. Thus, the first input data (index values) and the second input data (index values) are distinctive in the purposes, usage and handling.
[0024] Second profile data may comprise seller, agent, retailer information such as name, address, contact no, geographical information, area of coverage, seller identification parameters, payment details. In an embodiment, the second profile data is also referred to as Retailer’s Product Profile (RPP). In that, the retailer offer the product of many brands/makes/types for sale also at the local store within the indicated geographical location. Stock data comprises list of products, quantity, price, and other information indicating the status of stock. Second selections may comprise selections relating to products/goods list, stock list, offers, coverage information, area of delivery, price, time of delivery, status and other selections indicating the salability of a product. Second options may comprise the information that determines the action to be performed on the interconnecting server 135. For example, the second options may comprise sell, bid, wait, deliver, save, deal, offers. Second type of queries may comprise set of parameters required to obtain desired data from the interconnecting server 135. The second type of query may be configured to extract the data such as list of bids, list of orders, deals, sales, payments, dynamic pricing, delivery details, and order status.
[0025] Service providing devices 115 are connected to the interconnecting server 135 through the communication network 130. Service providing devices 115 are configured to act as a gateway to avail/render various services like to print, to pay, to make secured communications, to authenticate, information distribution and sharing, selective searching, and payment transactions.
[0026] Data storage 140 stores the first input data, second input data, results and other processed information received from the interconnecting server 135 in a suitable format and tables. The data storage 140 is dynamically indexed and structured to identify and retrieve the requested data by the first and second terminal devices and interconnecting server 135.
[0027] The interconnecting server 135 receive first input data and second input data and process them dynamically enabling efficient interconnection between first and second terminal devices. The manner in which the interconnecting server 135 operates to connect first terminal devices 105 and second terminal devices 110 is further described below.
[0028] FIG. 2 is a block diagram of an example interconnecting server 135. The block diagram is shown comprising bargain collector 215, first profile collection engine 205, product selection manager 210, deal & purchase manager 220, intent manager 230, bargain aggregator 235, dynamic bargain creator 240, deal strategy engine 245, dynamic offer creator 250, offer aggregator 255, offer collector 290, product collection manager 285, Intent bridge 260, second profile collection engine 280, deal & sale manager 295. Each component is further described below.
[0029] The first profile collection engine 205, product selection manager 210, bargain collector 215 and deal & purchase manager 220 together operate to present first information on the first terminal devices 105 (display of the first information on the display device/screen) and collect first input data from the first terminal devices 105.
[0030] The second profile collection engine 280, the product collection manager 285, offer collector 290, and deal & sale manager 295 together operate to present second information on the second terminal devices 110 (display of the second information on the display screen) and collect second input data from the second terminal devices 110. The first information, second information, first input data and second input data enable interaction and meaningful interconnection between the first terminal devices 105 and second terminal devices 110. For example the interaction and interconnect may enable trading of products, buying, selling, etc.,
[0031] The manner in which the information is presented on the second terminal device 110 for suitably collecting the second input data is further described below.
[0032] The second profile collection engine 280 collects second profile data. Second profile data may comprise identity of a seller, agent, retailer information such as name, address, contact no, geographical information, area of coverage, seller identification parameters, and payment details.
[0033] FIG. 3 illustrates the example user interface presented on the second terminal device 110 by the second profile collection engine 280 for collecting the second profile data. As shown there, second profile collection engine 280 captures and receives the data entered in fields 301A-301N. The field 301A collects the profile information, field 301B collects location information and the field 301C collects coverage area for example. The coverage area may be centered to the location entered in the field 301B.
[0034] The product collection manager 285, records, collects, and dynamically manages the product/item information and stock details. The product information may comprise data relating to a product or set of products, product parameters, product categories, price parameters, availability information, quantity in stock, product specification and other information related to one or more products. Manner in which the product collection manager 285 may present user interface and collect information is further described with one example below.
[0035] FIG. 4 illustrates example user interface enabling collection of information. As shown there, each field 401A-401N provides name of the product or product identifier. The field 401A-N may be selected from a pre-populated set of names/identifier (wherein such pre-population may be based on the second profile data or from the information available in the data storage 140). Fields 402A-402N captures a number value representing the availability or in stock volume corresponding to the products. Fields 403A-403N captures the price (retail price) of the corresponding product. Fields 404A-404N captures the delivery time corresponding to each product. Fields 405A-405N captures the geographical coverage area for delivery/pickup. Fields 406A-406N may capture pictures and other media content representing/corresponding to a product. Fields 407A-407N may capture other information related to corresponding product.
[0036] The product collection manager 285 may index product/item information and stock details collected through fields 401-407 against corresponding profiles, geographical location coverage area etc.
[0037] Offer collector 290 collects information related to offers or benefits associated with each product and the second profile information. For example, offer collector 290 may prompt each second terminal device 110 seeking benefits associated with products collected through product collection manager 285. The offer collector 290 may store the collected offers in relation to the product(s) and the second profile. The offers may further related to a time tag. The time tag may represent validity of the offer so collected with respect to a time of consideration. The manner in which is the offer collector 290 may collect the offers in one embodiment is described in further detail below.
[0038] FIG. 5 is an example user interface presented on the second terminal device 110 by the offer collector 290 for collecting offers as part of the second input data. As shown there, field 501 presents a product identifier. The product identifier may represent product name or number received by the product collection manager 285. The field 502 collects a static value (or string) representing a first offer. The first offer may be a static value applicable for relatively longer period of time (for example six months to a year) or may depend on an occurrence of an event. The field 503 captures the second offer that may be applicable for a relatively lesser period of time for example one month starting from a known time point. The field 504 captures the third offer that may be applicable on when prerequisite conditions are met. For example, the field 504 may capture an offer value that is applicable when a number of deals forwarded by the deal & sale manager 295 exceed a threshold number within a fixed period of time. The field 505 presents information related to a proposal, prospect and input for bid. The field 505 may provide information dynamically (push technique) on the second terminal device 110 specifically seeking a data input on field 506. The field 506 collects data in response to the information presented on the field 505. For example the field 506 may collect fourth offer in response to projected number of orders/deals presented on field 505. The fourth offer may be valid on occurrence of event presented on field 505. For example, the field 506 may collect bid inputs. The field 507 may collect other offers. The field 508 collects comments/conditions for other offers on field 507. The field 505 and field 506 may dynamically change and engage number of the second terminal on a protocol for confirmation and authentication of data presented on the field 505 and 506. The offer collected in the fields 501-507 may represent benefits in forms of another product in the stock or benefits in various forms like, coupons, waiver of charges, discounts, and percentage of reductions from the maximum retail price for example.
[0039] The deal & sale manager 295 provides and exchanges information related to start of event, end of event, progress of event etc., “to and from” the second terminal devices 110 and interconnecting server 135. For example, the event may correspond to sale in that, the deal & sale manger 295 may exchange information related to confirmation of sale, confirmation of delivery, confirmation of payment, close of deal etc. The manner in the deal & sale manager 295 may exchange information is described below in further detail.
[0040] FIG. 6 is an example user interface presented on the second terminal devices 110 by the deal & sale manager 295 as part of second information and second input data. As shown there the user interface 600 comprises deal/sale field 601A-601N, first text field 602A-602N, second text field 603A-603N, value field 604N-604N, first acknowledge field 605A-605N, delivery confirmation field 606A-606N, payment confirmation field 607A-607N and deal close field 608A-608N.
[0041] The deal/sale field 601A-601N present a unique identity number associated with triggering of an event. The event may correspond to a deal agreement requiring a set of actions to be performed on the second terminal devices 110. For example, the set of actions may be providing information/digital document as proof of execution deal agreement. The number of such triggers corresponding to a particular second profile may represent the number of deals or orders to the corresponding second profile.
[0042] First text field 602A-602N presents the unique identifier identifying a product associated with the respective deal in the field 601. For example, the first text field 602A-602N may provide information comprising the product name, make, model, variant, etc.
[0043] Second text field 603A-603N presents the information associated with other entity engaged in the deal agreement. For example, the second text field 603A-603N may represent a name, address, contact number, and other information of an entity to which the product is sold or to be delivered.
[0044] Value field 604N-604N may indicate the value corresponding to the deal. The value may represent the sale price, receivable price, deal price, collectable price etc., associated with corresponding deal.
[0045] First acknowledge field 605A-605N collects the acknowledgement information representing the initiation of the set of action corresponding to the respective deal on field 601 at the second terminal device 110.
[0046] Delivery confirmation field 606A-606N collects the information representing a completion of an action as part of the set of actions at the second terminal device 110. For example, the information may comprise proof of delivery, proof of reception of a product in good condition, proof of dispatch of the product etc.
[0047] Payment confirmation field 607A-607N collects the information representing a reception of consideration corresponding to a deal. For example, the consideration may represent receipt of the payment represented in the field 604.
[0048] Deal close field 608A-608N may present information representing close of the respective deal indicative of successful execution of set of actions associated with the deal agreement.
[0049] The second profile collection engine 280, product collection manager 285, offer collector 290, and deal & sale manager 295 may operate in conjunction with bargain aggregator 235, dynamic bargain creator 240, deal strategy engine 245, and dynamic offer creator 250. Further, fields in FIG. 3-6 may be presented independently, combined, and selectively combined in one or more user interface (hereafter referred to us second user interface) for ease of presentation and collection of data.
[0050] The manner in which the data may be collected from second terminal devices 110 is further described below.
[0051] FIG. 7 is a block diagram illustrating the manner in which interconnecting server 135 presents and collects the data on the second terminal devices 110 in an embodiment.
[0052] In block 710, the interconnecting server 135 receives a login request from second terminal device 110 and enables access. The login request may contain the username and password, which are authenticated by the interconnecting server 135 in any known way.
[0053] In block 720, interconnecting server 135 sends second user interface to the second terminal devices 110. Upon successful authentication of the user, the interconnecting server 135 forwards the second user interface in a suitable format for display.
[0054] In block 730, the interconnecting server 135 may check for existing product details in the data storage 140 corresponding to the user name. In one embodiment, the interconnecting server 135 may collect the product details from different sources, through other devices at the back end and prepare them for the suitable display on the second terminal devices 110 as part of the second user interface. Such presentation of data may ease the data entry and collection on the second terminal devices 110. Alternatively, interconnecting server 135 may present already collected data for any update or modification.
[0055] In block 740, the interconnecting server 135 receives information from the second terminal devices 110. The information may contain product details such as product name, stock details, offer details, geographical information, and other metadata. The second input is suitably stored in the data storage 140.
[0056] In block 750, the interconnecting server 135 generates information for presentation on the second user interface. The information may be generated based on the data received through first terminal devices 105 and other second terminal devices 110, etc. For example the interconnecting server 135 may prepare data comprising number of orders, enquiries, orders pending, expected price etc. collected from one or more first terminal devices 105. The interconnecting server 135 may push such data to second terminal devices 110 using suitable push techniques.
[0057] In block 760, the interconnecting server 135 receives dynamic data from second terminal devices 110. In one embodiment, the second dynamic data (as collected from field 505 in FIG. 5) may represent response to the first dynamic data (as presented on field 504 in FIG. 5). For example, the second dynamic data may comprise offer price in response to indicated first quantum of order in the first field.
[0058] Continuing further with respect to FIG. 2, the manner in which first profile collection engine 205, product selection manager 210, the bargain collector 215 and deal & purchase manager 220 operate in combination with bargain aggregator 235, dynamic bargain creator 240, deal strategy engine 245, and dynamic offer creator engine 250 is further described below. In one embodiment blocks 205, 210, 215, and 220 operate to present information on the first terminal device 105 for suitably collecting the first input data.
[0059] The first profile collection engine 205 collects first profile data. First profile data may comprise information such as name, address, contact no, geographical information, payment details.
[0060] FIG. 8 illustrates the example user interface presented on the first terminal device 105 by the profile collection engine 205 for collecting the first profile data. As shown there, the data entered on the fields 801A-801N is captured and received at the profile collection engine 205. The fields 801A-801N may collect name, address, contact no, geographical information, payment details and other details as part of the first profile. In an embodiment, the first profile data is also referred to as Customer’s Product Profile (CPP).
[0061] The product selection manager 210 records, collects, and dynamically manages the first type of selections on first terminal devices 105. First type of selections may comprise selections relating to a product(s), product parameters, product categories, price parameters, availability information, and other selections enabling drilling down to a desired product or item. The product selection manager 210 may enable selection of products, group of products or items on the first terminal devices 105 by way of presenting user interface on the first terminal device 105. For example, the product selection manager 210 may present a set of items based on the first profile data or may present a menu of items in pre-determined arrangement enabling selection and drill down to a particular item. FIG. 9-13 illustrates the manner in which the product selection manager 210 enables selection and monitors the selections in one embodiment.
[0062] FIG. 9 illustrates an example menu presented on first terminal devices 105 enabling sequential selection and drill down in one embodiment. As shown, the menu 901 comprises first level of selection (departments) 910, second level of selection (categories) 920, and third level of selection (products) 930 and fourth level of selection (parameters) 940, for example.
[0063] The first level of selections 910 represents a title that may suitably describe and broadly classifies set of products/items in the database. The department may describe the use and application of the items there by enables first level of selections. For example, the department 910 may comprise electronics, home appliances, artwork, jewellery etc.
[0064] The categories 920 represents a title that sub-classifies set of products in the database thereby enable drilling down to second level of selections within the department 910. For example, the category 920 may comprise (corresponding to department – electronics) camera, television, computer, accessories etc.
[0065] The products 930 represents a title or name that identify set of products in the database and enable drilling down to third level of selections within the category 920. For example, the product 930 may comprise digital SLRs, point & shoot, mirror less, camcorders, camera lenses, etc.
[0066] The parameter 940 represents a title that indicates varying qualities, features, specification of the products in the database. The parameter 940 enables drilling down to fourth level of selections within the product 930. For example, the parameter 940 may comprise, weight, product dimensions, memory slots available, display technology, screen size, display type etc.
[0067] Item space 950 displays set of items complying with the level of selection. Item space 950 comprise item 1 to ‘n’, complied with the level of selection. As shown there, each item is indexed with corresponding values for example, item 1, item 2, item 3 etc. The item description is enabled whenever an item is selected.
[0068] In addition to the departments, categories, products and parameters, the menu 901 may further comprise titles that may suitably describe other selection such as availability 960, sellers 970, and geographical location 980, offers 990 etc. The availability 960 indicates stock status of product as registered in the database (for example, as non-available and available items).
[0069] The sellers 970 represents a title that indicate list of names of the supplier as register in the database and associated with the items. For example, the seller list may comprise trading names, trademark, seller identifier etc.
[0070] The geographical location 980 indicates geographical coverage area associated to each supplier/second profile in the data storage 140. The geographical coverage area in the database may indicate the operational area of the supplier for corresponding item or set of items. The geographical location 980 may be represented by locality names popularly identified. For example, Jayanagar, Basavangudi, Redbank, Long Beach, Downtown area etc.
[0071] The offers 990 indicate the discounts or other benefits indexed against item, set of items, sellers etc., in the data storage 140. For example, the offer may comprise numbers or items. In case of numbers, the number may represent percentage like 10%, 20%, 30% etc.
[0072] In one embodiment, the menu 901 may comprise set of entries that are matched to the first profile. For example, the menu 901 may comprise only the list of products that are marked available within the preferred geographical location 980 entered as part of the first profile. Alternatively, the list of products in the menu may comprise only the set of products that are matched to one or more parameters in the first profile. As a result, the product selection on the first terminal device 105 need not drill through all the products in the database.
[0073] In one embodiment, the interconnecting server 135 in general, intent manager 230 in particular tracks and records every level of selections made on the first user terminal device 105 and stores the records as intent in the data storage 140. The intent manager 230 operates in combination with the product selection manager 210 to track selection at the first terminal device 105 at each step or at regular interval and stores in the data storage 140 as intent. The manner in which the selections are recorded and stored as intents is further described below.
[0074] FIG. 10 is a flowchart illustrating the manner in which the selections are recorded in an embodiment.
[0075] In block 1005, interconnecting server 135 receives a login request from first terminal devices 105 and enables access to the data storage 140. The login request contains the username and password, which are authenticated by the interconnecting server 135. Interconnecting server 135 may authenticate user through any known techniques, through service providing devices, gateways etc.
[0076] In block 1010, interconnecting server 135 sends menu 801 to first terminal devices 105. Upon successful authentication of the user, the interconnecting server 135 forwards the menu in a suitable format for display.
[0077] In block 1015, interconnecting server 135 receives first level of selection made on the first user terminal device 105. The selection may be captured through the input device by way of mouse clicks, keyboard input, etc., on one or more of the first level of selections.
[0078] In block 1020, interconnecting server 135 stores first level of selection with other metadata in the data storage 140. The metadata include time of capture, session id, other web page status details, title of selection etc.
[0079] In block 1025, interconnecting server 135 receives next selection. The next selections are captured through the first terminal devices 105. The next selection may be either within first selection or outside first selection. The next selection is saved in relation to first selection by appropriate indexing or linking in the data storage 140.
[0080] In block 1030, interconnecting server 135 may store next selection with other metadata in the data storage 140. The metadata include time of capture, session id, other web page details etc. In addition to the metadata, the relation with other selection made prior to next selection, time elapsed between the selections etc is also stored in the data storage 140.
[0081] In block 1035, the interconnecting server 135 checks whether it is a final item/selection/or termination of connection. The interconnecting server 135 may check the data storage 140 and determine the remaining number of selections for an item or availability of further selections. The control is transferred to block 1040, at least when no availability of selections is indicated from the data storage 140, the communication from first user is terminated, session expires, etc. The control is transferred to block 1025, when the data storage 140 retrieves at least one level of selection for that item.
[0082] In block 1040, the interconnecting server 135 may store the selection in the data storage 140 as intent. For example, the set of selection, relative time delay in selections, to and forth selection pattern may be stored against an intent ID as history. Further, interconnecting server 135 may initiate action/procedure/other tasks for the selected item. One example task may be a purchase procedure. The purchase procedure is further described in sections below.
[0083] FIG. 11 illustrates the example user intent (selections) recorded in the interconnecting server 135. As shown there, the intent 1110 (highlighted with grey) comprises, department 1, category 1, parameters 2, 4, 5, 7, 8 and 9. The intent 1110 may be recorded in one previous session, or the through multiple session prior to the current login.
[0084] In one embodiment, interconnecting server 135 provides the intent of the user in the previous sessions as part of the menu 901. The intent 1110 may represent full navigation made to the desired product or partial navigation made to desired product. The manner in which the intent 1110 is provided to the user device is further described below.
[0085] FIG. 12 is a flowchart illustrating the manner in which the intents 1110 are retrieved in an embodiment.
[0086] In block 1210, interconnecting server 135 receives a login request from first user terminal devices 105 and enables access. The login request may contain the username and password, which are authenticated by the interconnecting server 135.
[0087] In block 1220, interconnecting server 135 checks existence of intent (selection) history from previous sessions in the data storage 140 for the same account/first profile (user ID and Password). If the intent history is available then the control is transferred to block 1230, otherwise the control is transferred to block 1240.
[0088] In block 1230, interconnecting server 135 presents the menu comprising intent history. In one embodiment, the interconnecting server 135 may populate the selections from the intent captured in the immediate previous session. In an alternative embodiment, the interconnecting server 135 may simulate the selection hierarchy indicating to and forth navigation as made in the previous session. Further, the interconnecting server 135 lists all previous recorded intents with the session id, date and time of capture, title of selection, etc., as a drop down menu.
[0089] In block 1240, interconnecting server 135 displays menu without the intent history on the first terminal device 105. The interconnecting server 135 sends a menu 201 to the user, when no recorded selection history is available in the data storage 140.
[0090] In block 1250, interconnecting server 135 receives a request for desired intent from the intent history. In one embodiment, the user may choose the desired intent from the intent history list.
[0091] In block 1260, the interconnecting server 135 presents desired intent from the history on the first terminal device 105.
[0092] In block 1270, the interconnecting server 135 enables further selection on the first terminal device 105. The further selections/navigations may be made from the previous intent. The interconnecting server 135 initiates purchase procedure for the selected item. The manner in which the intent from the intent history is presented on the first terminal device 105 is described in further detail below.
[0093] FIG. 13 illustrates the manner in which the menu selections are automatically populated for selected intent in one embodiment. As shown there, screen 1310 is menu presented on the first terminal device 105 upon login to the interconnecting server 135. The list of intent 1320 is presented for selection on first terminal device 105. The selection from the list of intent 1320 is captured on the interconnecting server 135. The screen 1330 comprising the populated selection 1340 corresponding to selected intent (in this example 1110) is presented on the first terminal device 105. In an alternative embodiment, the screen 1330 with the populated selection 1340 may be presented directly. In such cases, the population of selections may be made based on the intent captured in the previous session.
[0094] In one embodiment, the interconnecting server 135 allows other service devices and second terminal devices 110 to access the list of intent 1320 stored in the data storage 140. The intent bridge 260 may facilitate access to the list of intent 1320 stored in the data storage 140. Alternatively, intent bridge 260 may locally/separately store the list of intent 1320 for access to the other devices. Accordingly, the service providing devices and the second terminal devices 110 may send messages to the first terminal device 105 based on the list of intent 1320. In another embodiment, the interconnecting server 135 provides the intent to second terminal device 110 and presents the messages from the second terminal devices 110 on to the first terminal devices 105. Wherein the message may be generated in accordance with the intent captured at any given time. Thus, interconnecting server 135 enables bringing retailer’s advertisement campaign to consumer having corresponding intent.
[0095] The navigation to desired product may be further carried out from the populated selection 1340. The product selection manager 210 enable selection of a product from the list of product in a hierarchical set of selection or may enable product selection based on the user profile interest. Once a final product is detected to be selected (no further selections are available on the product selection, the product selection manager 210 may pass the control to at least one of deal & purchase manager 220, bargain collector 215 and other blocks. In one embodiment, deal & purchase manager 220 presents a first price against the selected product and enable selection of a purchase event and a bargain event.
[0096] Continuing further with reference to FIG. 2, the manner in which the interconnecting server 135 enable further interactions between the first terminal devices 105 and second terminal devices 110 is further described below.
[0097] Bargain collector 215 collects first set of bargain inputs corresponding to a selected product(s). The bargain inputs may represent an integer or a string representing a value. Bargain collector 215 may presents a bargain information on the first terminal devices 105 and correspondingly collect the bargain inputs for a selected one or more products. The bargain information may comprise a bargain value, set of bargain values providing options for selection, time validity, and start time for each bargain value presented, location information and other compliance details for a bargain selection or selected bargain. The manner in which the bargain collector 215 may present bargain information and collect the bargain is further described below.
[0098] FIG. 14 is an example user interface presented on the first terminal devices 105 for providing bargain information and collecting bargain inputs in an embodiment. As shown there, the interface comprises product identity field 1401A-1401N, deal identity field 1402A-1402N, first bargain information field 1403A-1403N, second bargain information field 1404A-1404N, time field 1405, geographical information field 1406, bargain input fields 1407A-1407N and 1408A-1408N. Each field is described below in further detail.
[0099] The product identity fields 1401A-1401N presents information of one or more products. selected at the product selection manager 210 and associated/linked or in the uploaded list of one or more retailer/ second profile.
[00100] Deal identity field 1402A-1402N represents one or more options or set of actions initiated with reference to a product (through the deal & purchase manager 220 described in sections below)
[00101] First bargain information field 1403A-1403N presents the type of bargains. For example, the type of bargain may comprise the price bargain, quantity bargain, benefits bargain, service bargain, compliments bargain, payment bargains etc.
[00102] Second bargain information field 1404A-1404N presents the bargain value corresponding to the product. For example bargain value may represent second price that is less than the first price. Alternatively, the bargain value may represent other benefits. The other benefits may comprise, free delivery, supporting accessory, gift coupons vouchers etc.,
[00103] Time field 1405 may represent the validity of a bargain, start time and end time (time window) for applicability the bargain value.
[00104] Geographical information field 1406 represents the geographical information over which the bargain is applicable.
[00105] Proposal input fields 1407A-1407N receives proposal value corresponding to the respective products. Alternatively the input field’s1407A-1407N may receive a value indicative of a limit.
[00106] Field 1408A-1408N may receive a string, item description etc. the string may represent a product in exchange to the corresponding products in the fields 1401A-1401N. The bargain inputs thus collected on number of first terminal devices 105 corresponding to number of first profile is received at the bargain aggregator 235.
[00107] The field 1409 may receive input indicative of acceptance of one of the bargain value presented against the corresponding product. The acceptance indication is passed on to the deal & purchase manager 220.
[00108] Deal & purchase manager 220 exchanges information related to start of event, end of event, progress of event etc., “to and from” the first terminal devices 105 and interconnecting server 135. For example, the event may correspond to purchase in that, the deal & purchase manger 220 may exchange information related to confirmation of purchase, confirmation of receipt of product, confirmation of payment, close of deal etc. The manner in the deal & purchase manager 220 may exchange information is described below in further detail.
[00109] FIG. 15 is an example user interface presented on the first terminal devices 105 by the deal & purchase manager 220 as part of first information and first input data. As shown there the user interface 1500 comprises deal/purchase field 1501A-1501N, first text field 1502A-1502N, second text field 1503A-1503N, value field 1504N-1504N, first acknowledge field 1505A-1505N, product receipt field 1506A-1506N, payment confirmation field 1507A-1507N, bargain option field 1508 and deal close fields 1509A-1509N.
[00110] The deal/purchase field 1501A-1501N present a unique identity number associated with triggering of an event. The event may correspond to a deal agreement requiring a set of actions to be performed on the second terminal devices 110. For example, the set of actions may be providing information/digital document as proof of execution deal agreement.
[00111] First text field 1502A-1502N presents the unique identifier identifying a product associated with the respective deal in the field 601. For example, the first text field 1502A-1502N may provide information comprising the product name, make, model, variant, etc.
[00112] Second text field 1503A-1503N presents the information associated with other entity engaged in the deal agreement. For example, the second text field 1503A-1503N may represent a name, address, contact number, and other information of an entity from which the product is sold or delivered from or the agreement of delivery of a product is entered.
[00113] Value field 1504N-1504N may indicate the value corresponding to the deal. The value may represent the sale price, receivable price, deal price, collectable price etc., associated with corresponding deal.
[00114] First acknowledge field 1505A-1505N collects the acknowledgement information representing the initiation of the set of action corresponding to the respective deal on field 1501 at the first terminal device 105.
[00115] Product receipt field 1506A-1506N collects the information representing a completion of an action as part of the set of actions at the first terminal device 105. For example, the information may comprise proof of receipt, proof of reception of a product in good condition, etc.
[00116] Payment confirmation field 1507A-1507N collects the information representing a payment corresponding to a deal. For example, the information comprises, various information needed for online payment. Alternatively, the input may comprise proof of receipt of the payment made.
[00117] Deal close fields 1509A-1509N may present information representing close of the respective deal indicative of successful execution of set of actions associated with the deal agreement. In one embodiment, the interconnecting server 135 checks the data at the bargain option field 1508 before closing the deal. If the data input at the bargain option field 1508 indicate further action, the deal is not closed.
[00118] Bargain option field (bargain event) 1508 receives input indicating performance of preferred set of action prior to and subsequent to the deal close. The preferred set of action may comprise at least one of, wait for pre-specified time, check for a bargain value, execute an action when the bargain value is within a range indicated at the proposal field, execute benefit over time, return benefit over a time period etc. Bargain option field 1508 passes control to bargain collector 215 and withholds the completion of deal close until selection is indicated. The bargain option field 1508 may be enabled based on the data entered on the payment confirmation field. Alternatively, the bargain option field 1508 may be enabled on partial payment or acceptance of purchase or confirmation of deferred deal close. In one embodiment, the bargain option field 1508 is enabled to a set of first profiles with desired history of transaction. Additional field (not shown) may receive an interest to purchase at a pre-specified price and benefit condition without entering to a purchase deal.
[00119] The first profile collection engine 205, the product selection manager 210, bargain collector 215, and deal & purchase manager 220 may operate in conjunction with bargain aggregator 235, dynamic bargain creator 240, deal strategy engine 245, and dynamic offer creator 250. Further, fields in FIG. 9-14 may be presented independently, combined, and selectively combined in one or more user interface (hereafter referred to as second user interface) for ease of presentation and collection of data. The manner in which the interconnecting server 135 operates to present the relevant information on the first terminal devices 105 and second terminal devices 110 for effective interconnect is further described below.
[00120] Continuing further with reference to FIG. 2, the manner in which first input data and second input data are processed by the interconnecting server 135 is further described below.
[00121] Bargain aggregator 235 collects the bargain inputs from set (plurality) of first terminal devices 105 and provides the collected inputs to the strategy engine for further processing. The bargain aggregator 235 may maintain connectivity with first terminal device 105 and receive any updates made to the bargain input on the first terminal device 105 during the processing. The processing period may be set to a day, week, months based on the conditions set forth in the bargain input. The aggregated bargain input may be arranged and indexed corresponding to product, price, geographical location, retailer/second profile, first profile and other parameters so collected as part of the first input data. The aggregated data may be dynamically changed/updated as and when new bargain data is collected corresponding to same reference index or product from the first terminal device 105.
[00122] Offer aggregator 255 collects the offer data from set of second terminal devices 110 and aggregates such data over period of time. For example, the aggregation may be for a day, week, months based on the conditions set forth in the offer data. The aggregated offer data may be arranged and indexed corresponding to product, price, geographical location, retailer/second profile, first profile and other parameters so collected as part of the second input data. The aggregated data is provided to the strategy engine for further processing. In one embodiment, offer aggregator 255 may maintain communication with one or more second terminal devices 110 dynamically collect offers from the second user interface.
[00123] Dynamic bargain creator 240 generates second price value (one or more) for a selected product when the bargain mode is selected. The second price is presented on each first profile/first terminal device 105. The set of proposed second price is generated based on number of parameters like the offers collected from the second profile/second terminal devices 110, first profile, number of deals and other parameters described in section below.
[00124] Dynamic offer creator 250 generates a dynamic number representing a projected number of deals within a time period. The dynamic number is presented on the second terminal devices 110 as information for receiving offers. The dynamic offer creator 250 may create the dynamic number based on number of bargain mode selection, purchase trend, first profile data, the earlier offers collected from the second terminal devices 110, geographical information, type of delivery and other parameters present in the first input data and second input data. The dynamic offer creator 250 may create dynamic number representing an order at different instant of time based on the number of bargain mode selections collected at a given point in time for example. In one embodiment, the dynamic number representing the proposed number of order is created for one or more product, for one or more applicable retailer.
[00125] Deal Strategy engine 245 processes first input data, second input data, and other prior processing results to establish communication/transaction between first profile and second profile. The manner in which the deal strategy engine process data is further described below.
[00126] FIG. 16 is a block diagram illustrating an example processing in one embodiment. In block 1610, the deal strategy engine 245 enables selection of product on the first terminal device 105 by first profile. The selection of the product may be made through product selection manager 210 as described in the sections above. In block 1620, the deal strategy engine 245 presents the first price associated to the selected product and enable selection of first price or bargain option through the first user interface. In block 1630, the deal strategy engine 245 checks if the presented first price is selected on the first terminal device 105. In block 1640, the deal strategy engine 245 initiates the purchase through the deal & purchase manager 220. In block 1650, the deal strategy engine 245 checks if the bargain option is selected on the first terminal device 105. In block 1660, the deal strategy engine 245 determines the second price. In block 1670, the deal strategy engine 245 presents the determined second price on first terminal device 105 on the first user interface. In block 1680, the deal strategy engine 245 checks if the second price is selected on the first terminal device 105. If the second price is determined t be selected, the engine passes the control to deal & purchase manager 220 for completing the deal activity. In block 1690, the deal strategy engine passes a pre-specified time or checks for other relevant activity upon which the second price is recomputed and represented. The action in blocks is repeated for pre-specified time (a bargain window). The manner in which the second price is computed is further described below.
[00127] The second price is determined based on number of parameters. In one embodiment, the second price is represented with a relation:
[00128] P2 = f( Vo, Nd, TFp, Dk)
Wherein the term f represents function of, Vo represents the Volumetric benefit provided by the second profile (collected through offer collector 290), Nd represents Number of deals completed over a time period, TFp represents the number of successful transaction by first profile (or percentage of successful deal transaction over initiated transaction) and D represents an income value at the server accumulated over period of time while managing the communication and interconnection between the first terminal devices 105 and second terminal devices 110.
[00129] FIG. 17 is a block diagram illustrating the manner in which the deal strategy engine 245 enables participation plurality of second terminal devices 110 in one embodiment. In block 1710, the deal strategy engine 245 determines a projected number of orders that may be targeted more than one second profiles. In block 1720, the deal strategy engine 245 opens communication with the determined set of second profiles on corresponding second terminal devices 110. In block 1730, the deal strategy engine 245 presents the projected number of orders on the set of second terminal devices (for example on filed 505). In the block 1740, the deal strategy engine 245 collects the offer response from the second terminal devices 110 corresponding to presented number of orders (for example from field 506). In block 1750, the deal strategy engine 245 allocates the projected number of orders to one or more second profile based on the offer response received.
[00130] The manner in which the deal engine computes projected number of orders is further described below.
[00131] FIG. 18 illustrates example aggregated bargains received from first terminal devices 105. As shown there the total 34 bargain options are collected and aggregated by the bargain aggregator 235. The first coverage area 1810 is shown comprising 13 bargain requests (or 13 bargain requests are associated with coverage area 1810). Similarly, 21 bargain requests are associated with coverage area 1820 and 17 bargain requests are associated with respect to the coverage area 1830. The Deal strategy engine 245 may assigns each bargain request to corresponding geographical location 1820-1830 and compute the number of bargain in each geographical location.
[00132] Deal strategy engine 245 also determines and identifies the retailer profile (second profile) matching with the parameters of the bargain request (in this case, product and geographical information) and send the list of the retailer and corresponding number of bargain request to the dynamic offer creator 250. Alternatively, the deal strategy engine 245 may present number of deals in the corresponding geographical area as offered deal to the corresponding set of retailer falling within the geographical area. For example, the deal strategy engine 245 sends value 21 as potential deal to collect dynamic sale offer from one of the second terminal device 110 (or corresponding second profile). Similarly, deal strategy engine 245 may send value 13 and 17 respectively to corresponding other second terminal devices 110 (say terminal devices of first and third retailer) to collect the dynamic offer corresponding to a product or deal in progress.
[00133] The collected offer response against the proposed number of deals/orders is compared and the deal is made between the retailer and the buyer matching the least/best offer proposal.
[00134] As may be appreciated the server enable user (consumer) of the first terminal devices 105 enjoys a single stop online shopping experience with additional bargaining power. The user (retailer) of the second terminal devices 110 get the power of an online store and get to connect to more consumers without any hassles and heavy technology investment. The interconnecting server 135 will enable up sell and cross sell thereby increasing retailers revenue and consumer base retaining loyalty. The interconnecting server 135 provides retailers a platform to compete with B2C online ecommerce as a fair market.
[00135] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-discussed embodiments, but should be defined only in accordance with the following claims and their equivalents.

CLAIMS
I/We Claim,
1. A system for interconnecting set of first terminal devices and set of second terminal devices for engaging in sale and purchase transaction of a product comprising;
a first profile collector configured to collect a set of first profiles from a first terminal devices and attributing the first set of profiles to activity of purchase;
a second profile collector configured to collect set of second profiles from a second terminal devices and attributing the second set of profile to activity of sale;
an offer collector configured to collect first offer value and second offer value from the second terminal devices for the product;
a strategy engine configured to determine a first price from first offer value and determining a second price based on a number of transactions performed over a first time period; and
a deal engine configured to display the first price against the product and display the second price when first price is not selected.
2. The system of claim 1, further comprising;
a product selector configured display multiple selection parameters enabling selection of the product when a first set of parameters are selected;
an intent recorder configured to record selection of second set of parameters that are part of the first set of parameters; and
an intent bridge configured to share the second set of parameter with multiple external devices,
wherein the a message from a second terminal devices relevant to the second set of parameters is presented on the first terminal device.
3. The system of claim 2, wherein the product selector is further configured to display the second set of parameters in a second session of communication with the product selector when the second set of parameter is selected in a first session of communication with the product selector prior to the second session.
4. The system of claim 1, further comprising an offer collector configured to display projected number of orders on a set of second terminal devices associated with the corresponding set of second profiles that are within first geographical area and collect a response offer value to the projected number of orders and the deal engine is further configured to establish sale transaction with the second profile responding with low response offer value.
5. The system of claim 4, wherein the strategy engine is further configured to determine second price based on a second offer having a dependency to a order volume within a time period.
6. The system of claim 5, wherein strategy engine is further configured to generate a second price based on relation:
P2 = f( Vo, Nd, TFp, Dk), wherein P2 representing the second price, term f represents function of, Vo represents the Volumetric benefit provided by the second profile (collected through offer collector), Nd represents Number of deals completed over a time period, TFp represents the number of successful transaction by first profile (or percentage of successful deal transaction over initiated transaction) and Dk represents an income value at the server accumulated over period of time while managing the communication and interconnection between the first terminal devices and second terminal devices.
7. The system of claim 6, further comprising a bargain collector configured to collect a exchange product information, wherein the strategy engine determine one of the first price and the second price based on the exchange product information.
8. The system of claim 7, wherein a geographical region of operation of each second terminal device overlap with other.
9. The system of claim 8, wherein the strategy engine is further configured to present the second price only when a set of parameters in the first profile matches to a preset values.
10. A method, system and apparatus comprising one or more features as described in one more paragraphs of this specification.

Date: 09-11-2015 Signature………………………

ABSTRACT
According to one aspect, a system for interconnecting set of first terminal devices and set of second terminal devices for engaging in sale and purchase transaction of a product comprises, a first profile collector which collects set of first profiles from a first terminal devices and attributing the first set of profiles to activity of purchase, a second profile collector which collects set of second profiles from a second terminal devices and attributing the second set of profile to activity of sale, an offer collector which collects first offer value and second offer value from the second terminal devices for the product, a strategy engine which determines first price from first offer value and determining a second price based on a number of transactions performed over a first time period and a deal engine which displays the first price against the product and also display the second price when first price is not selected.
,CLAIMS:CLAIMS
I/We Claim,
1. A system for interconnecting set of first terminal devices and set of second terminal devices for engaging in sale and purchase transaction of a product comprising;
a first profile collector configured to collect a set of first profiles from a first terminal devices and attributing the first set of profiles to activity of purchase;
a second profile collector configured to collect set of second profiles from a second terminal devices and attributing the second set of profile to activity of sale;
an offer collector configured to collect first offer value and second offer value from the second terminal devices for the product;
a strategy engine configured to determine a first price from first offer value and determining a second price based on a number of transactions performed over a first time period; and
a deal engine configured to display the first price against the product and display the second price when first price is not selected.
2. The system of claim 1, further comprising;
a product selector configured display multiple selection parameters enabling selection of the product when a first set of parameters are selected;
an intent recorder configured to record selection of second set of parameters that are part of the first set of parameters; and
an intent bridge configured to share the second set of parameter with multiple external devices,
wherein the a message from a second terminal devices relevant to the second set of parameters is presented on the first terminal device.
3. The system of claim 2, wherein the product selector is further configured to display the second set of parameters in a second session of communication with the product selector when the second set of parameter is selected in a first session of communication with the product selector prior to the second session.
4. The system of claim 1, further comprising an offer collector configured to display projected number of orders on a set of second terminal devices associated with the corresponding set of second profiles that are within first geographical area and collect a response offer value to the projected number of orders and the deal engine is further configured to establish sale transaction with the second profile responding with low response offer value.
5. The system of claim 4, wherein the strategy engine is further configured to determine second price based on a second offer having a dependency to a order volume within a time period.
6. The system of claim 5, wherein strategy engine is further configured to generate a second price based on relation:
P2 = f( Vo, Nd, TFp, Dk), wherein P2 representing the second price, term f represents function of, Vo represents the Volumetric benefit provided by the second profile (collected through offer collector), Nd represents Number of deals completed over a time period, TFp represents the number of successful transaction by first profile (or percentage of successful deal transaction over initiated transaction) and Dk represents an income value at the server accumulated over period of time while managing the communication and interconnection between the first terminal devices and second terminal devices.
7. The system of claim 6, further comprising a bargain collector configured to collect a exchange product information, wherein the strategy engine determine one of the first price and the second price based on the exchange product information.
8. The system of claim 7, wherein a geographical region of operation of each second terminal device overlap with other.
9. The system of claim 8, wherein the strategy engine is further configured to present the second price only when a set of parameters in the first profile matches to a preset values.
10. A method, system and apparatus comprising one or more features as described in one more paragraphs of this specification.

Date: 09-11-2015 Signature………………………