Patent Grant
12093283
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention generally relates to sharing data among business partners, and more particularly to sharing data in supply chain partners via a multi-tenant database service.
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.
In conventional supply chain operation, the different business partners communicate via e-mail, fax, or phone call. One of the business partners may run a particular application on its own database system to which the other entities log onto and enter data by hand. The different business partners also enter data into their own database systems. This process is cumbersome, time-consuming, and tends to cause inaccuracies.
Accordingly, it is desirable to provide systems and methods that allow companies to easily share information, e.g. in a supply chain.
In accordance with embodiments, there are provided mechanisms and methods for sharing product data among business partners in a supply chain via a multi-tenant database service. These mechanisms and methods for sharing product data or other information can enable business partners to receive real-time and automatic updates to an order, an offer, product, or other object or part of a supply chain. A tenant (also called a subscriber or organization) of the multi-tenant database system can store data specific to that tenant in the multi-tenant data base system. Data associated with a product can be shared between different subscribers, who are or potentially will become business partners. The ability of embodiments to share data can enable partners to share deals and create new business opportunities. Embodiments can allow organizations to effectively prepare and educate employees, partners, and users around new features in each product release.
In an embodiment and by way of example, a method of sharing product data involved in a supply chain among a plurality of subscribers to an on-demand database is provided. Data related to a product is received from a first of the subscribers. From the data, a product object is created in a section of the on-demand data base that is accessibly restricted to the first subscriber. A request to share the product object is communicated to one or more second subscribers. An acceptance of a second subscriber is received. Data associated with the product object is received in a section of the on-demand data base that is reserved for the second subscriber. Changes made to the product object are synchronized between the two subscribers.
In another embodiment and by way of example, a system that implements the method of sharing product data involved in a supply chain among a plurality of subscribers to an on-demand database is provided. The system includes one or more processors which send, receive and store data associated with a product object in an on demand database after a request is sent from a first subscriber to a second subscriber. The request is accepted by the second subscriber before the shared product object data is stored in the on-demand database in a location accessible by both the first and second subscriber. In addition, the shared product object data is synchronized between the two subscribers.
In another embodiment and by way of example, a computer program product stored on a tangible computer readable medium storing a plurality of instructions for controlling one or more processors of an on-demand database system to perform an operation for sharing product data in a supply chain among a plurality of subscribers is provided. The computer program product includes instructions to receive a data related to a product by a first subscriber, communicate a request to share the product object with one or more second subscribers, accept an invitation form the second subscriber, store data associated with the shared product object on the on demand database and synchronous the data between the two subscribers.
Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
While the present invention is described with reference to an embodiment in which techniques for methods and systems for sharing information in a supply chain are implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the present invention is not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.
Any of the above embodiments may be used alone or together with one another in any combination. Inventions encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments of the invention may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments of the invention do not necessarily address any of these deficiencies. In other words, different embodiments of the invention may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.
In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.
Embodiments of the present invention can provide business collaboration both within and across organizations. Users can share leads, opportunities, cases and other information with their business partners and get real-time updates on the shared data. Embodiments may use proprietary connectivity or standards based connectivity (e.g. XML, W3C)
Various embodiments can enable a user of a database system to share opportunity products on opportunities, define templates that ease the process of connecting with companies, allow users to share the same record with multiple partners, and add certain API functions that will allow users to create custom rules to forward and stop sharing records with connections.
Systems and methods are provided for sharing information in a supply chain. These techniques for sharing information in a supply chain can enable embodiments to provide efficiently and accurately communicate information about one or more business transactions among multiple businesses.
As used herein, the term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server (e.g. running an application process) may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers.
Next, mechanisms and methods for providing controlling access to custom objects in a database system will be described with reference to example embodiments.
Environment 10 is an environment in which an on-demand database service exists. User system 12 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 12 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in
An on-demand database service, such as system 16, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 16” and “system 16” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 16 may include an application platform 18 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12, or third party application developers accessing the on-demand database service via user systems 12.
The users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 12 to interact with system 16, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.
Network 14 is any network or combination of networks of devices that communicate with one another. For example, network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that the present invention might use are not so limited, although TCP/IP is a frequently implemented protocol.
User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 16. Such an HTTP server might be implemented as the sole network interface between system 16 and network 14, but other techniques might be used as well or instead. In some implementations, the interface between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
In one embodiment, system 16, shown in
One arrangement for elements of system 16 is shown in
Several elements in the system shown in
According to one embodiment, each user system 12 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 16 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 17, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments of the present invention can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).
According to one embodiment, each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16. As such, system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
User system 12, network 14, system 16, tenant data storage 22, and system data storage 24 were discussed above in
Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 104 managed by tenant management process 110 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Provisional Patent Application 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEM FOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, by Craig Weissman, filed Oct. 4, 2006, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manages retrieving application metadata 116 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
Each application server 100 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23, via a different network connection. For example, one application server 1001 might be coupled via the network 14 (e.g., the Internet), another application server 100N-1 might be coupled via a direct network link, and another application server 100N might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 100 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.
In certain embodiments, each application server 100 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 100. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 100 and the user systems 12 to distribute requests to the application servers 100. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 100. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 100, and three requests from different users could hit the same application server 100. In this manner, system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant-specific data, system 16 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.
In certain embodiments, user systems 12 (which may be client systems) communicate with application servers 100 to request and update system-level and tenant-level data from system 16 that may require sending one or more queries to tenant data storage 22 and/or system data storage 24. System 16 (e.g., an application server 100 in system 16) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 24 may generate query plans to access the requested data from the database.
A table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc.
In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system.
In step 201, a user may set up their database in order to establish a connection with a contact, or partner. Initial set-up may include enabling sharing capabilities, establishing tenancy within the database and inviting a contact to create a connection. A user may communicate with the a contact in order to create such a connection through an email invitation in the form of a survey. A connection is created between a user and a contact when the contact acknowledges use of the database and, in some embodiments, their permissions to share data with other partners in database.
In step 202, the user may invite a connection to share data objects within their database. The user may customize templates in order to create an invitation. The customization may also include selected fields relating to that object which are wing to be shared with a connection. The invitation templates may be applied to multiple connections or individually customized per each connection. The connection needs to accept the invitation prior to sharing the data offered.
When the invitation is accepted, the structure of how an object and fields related to that shared object is defined within the connection's database. For example, the object is mapped to an object and the fields are mapped to corresponding fields in that object. The connection will then have an object and fields within their database matching those shared by the user. If new fields are added at a later point, this structure is updated in the connection's system. Accordingly, when the record is shared with a connection, the record is correctly mapped to a connections' database based on the object mapping.
In step 203, the user may share data with a connection. The shared data records may be modified after they are shared. In addition, new records may be shared with a connection upon invitation and by a user publishing and subscribing to additional records which are available for sharing. The data shared may be in die form of object data, such as products, opportunities, leads, etc. In the case of the aforementioned objects, the shared data record is made available to partners within a supply chain allowing for an improved business relationship and development.
The aforementioned method for sharing data between data base users is discussed in further detail in the following sections.
In some embodiments, in order to begin a sharing process between different tenants of a multi-tenant database, an initial connection can be established. In one embodiment, the connection may only be established if both tenants are both subscribers to a same database system (e.g., system 16).
In step 301, a user of the first organization establishes a user account and logs into the system. The user may be an administrator or another user of the system that has access to that particular tenant's information, dependent on the permissions established by the administrator. Such permission are discussed in more detail in the permissions section of the disclosure.
Within a database of an embodiment, many users may be allowed to access records within one tenant location. For instance, a salesclerk in a retail location may have access to the retail owner's account within the database. However, the owner may only wish the salesclerk to have specific privileges, or permissions within the system. In one embodiment, in order to establish a connection with a partner organization, the user has administrative privileges. In addition, in order to modify email templates and settings within the system, the user also has these administrative privileges. Accordingly, such privileges, or permissions can be established for each type of user profile in a tenancy in order for certain records to be viewed and for modifications to those records to be made.
In step 302, the user determines whether a connection with a business partner is possible. In one embodiment, the user requests the database system to send an e-mail to the business partner. The e-mail can require a response that is used to determine whether the business partner is a subscriber.
The user can customize the e-mail through an e-mail template, such as with a company logo or slogan. An end user that is using the template can further tailor the e-mail to the specific partner. The electronic message may include a welcome message and explanation as to the purpose of the email, as well as fields, radio buttons and other data elements for the receiving party to select as part of the response. For example, the fields provided may ask whether the receiving party utilized the database and what types of permissions they have to within their organization. The customized email may then be sent to the contact at a partner organization.
Essentially, the e-mail provides a survey of the companies available on the database to the user. The survey information is collected when the receiving party provides answers to the questions provided. The information provided may then be automatically stored within the database in records relating to the user's partners, which have been entered into the database previously. Accordingly, if a partner responds to the email survey providing they are a tenant within the database, such information is noted in the user's database under that particular partner's record as a part of the partner's contact information. In addition, the administrative privileges, or permissions allowed to party receiving the email is also noted in the partner's record.
Once the survey is complete, the partner contacted may submit 405 the information through the click of a button. The information is automatically received by the user of the database and entered into the partner's contact record within their database. As shown in
Referring back to
To enable the setting 303, the user can enter into the set-up menu of the database. Such enablement may only be done by users having administrative privileges. Because the enablement is irreversible in some embodiments, a warning, or similar precautionary message may be provided to the user when such a selection is made. The user can then select enablement and save the settings.
Next, the user can initialize a sharing connection between the partner having tenancy in the database. The database additionally has email templates for this purpose. In some embodiments, these templates may only be customized and sent by an administrative user. The templates may include initial invitation emails to establish a connection with a partner organization, or acceptance, rejection or deactivation emails for use once a connection is established.
The customizable template may also include a message from the user of the system, along with a URL in the body of the email. The URL is provided in order for the receiving party, or partner organization, to easily accept the invitation and establish a connection with the user. At this point, a connection is established between the two partner organizations and sharing may begin.
Referring again to
In step 305, the administrator may add a connections tab to the page layouts of the profiles having the “manage connections” permissions. In the database, the user can build applications in order to customize screen views within their account. As will be discussed further in the API access section, customized applications and instructions may be created by the user as well. However, a standard application and standard tab label is provided in the database and may be selected for connections. Adding this tab allows users to see contact information of the database connections, communicate with those connections, and share records with those connections.
In step 306, the user may then create a template in order to invite a connection to share certain objects. In one embodiment, step 306 can be performed during step 202 of method 200. The actions defining how and what about an object is shared may be automated for connections. In one embodiment, the automation may be performed using templates. Templates allow a user to pre-define publish object and field rules as well as assign active templates to one or more connections. This feature can simplify and streamline the process of setting up connections and allow users to easily connect with thousands of their business partners without any hindrance.
Invitation templates allow users to create pre defined templates organized by partner type. In one embodiment, connections using the template automatically inherit all the published objects and field rules. For large scale implementations, templates ease the administration of connections and allow users to change the sharing rules with connections with the click of a button.
In one aspect, templates are a sub-tab in the connections main tab so as to show the association with “Connections”. In another aspect, only administrators and users with the Manage Connections user profile can create, edit and view templates.
Users can define the name of the template, activate the template, and identify the objects and fields that are published when this template is associated to an invitation or existing connection (active or sent).
In one embodiment, the assigning of a template to a New/Existing connection is as follows. The assigning allows an administrator (admin) or user with Manage Connections permission to associate the template to either a new invitation or existing connection (active or sent). The above can be done via the ‘Invite to Connect’ mass invite action on the Contacts tab, ‘New’ invite action on the Connections tab and by editing an active or sent invitation and changing the template association (lookup field to the Templates object). In one aspect, only active templates can be associated to a connection. Though if a template is deactivated, there will be no impact on connections using this template.
In another embodiment, when the template is applied to a connection then the template's “Publish” object and field rules are applied to the connection. New objects/fields may be automatically added to the Publish definition of the connection. If the objects and fields already exist in the connection, then no update should take place on these objects/fields (no unpub/pub). If an object/field exists on the connection that doesn't exist on the template, then the object/field will be unpublished automatically. A notification message may be sent when an object/field is added or removed from the connection.
An updated template may be applied to all connections using the template. For example, imagine a template is being used by one or more connections. If the template is edited by changing either the Published Object or Field definition, the user should have the ability to apply the changes to all the connections using the template. Again, similar rules as described above may apply. In one aspect, a special button on each template Apply to Connections' performs this action of applying an updated template.
In one embodiment, templates are packagable so that the user can export the templates and associated Publish object and field definitions and publish the same on the service platform. The packaged templates should also be available for download by users. When the package is downloaded, all the associated objects (which may be done just for custom objects) and fields are also created in the organization downloading the package.
Accordingly,
In an exemplary embodiment, a vendor can have 3 partner tiers, Platinum, Gold and Bronze partners. The channel manager (CM) may want to share Leads, Opportunities, MDF's and Orders with the platinum tier; share Leads and Opportunities with Gold; and share only Leads with Bronze. Using templates, the CM can define right to the field level the sharing rules by partner by associating the right template to the connections (i.e. Platinum template to platinum partners). Additionally, if the CM wants to add an object or field to one of the templates, the ability exists at automatically update all the connections with the change with the click of a button.
Referring back to the method in
Once the invitation is accepted, the shared records are mapped to records in the recipients account and may be viewed. The user, or sender of the invitation, may view the shared data in the connection details of the partner with whom the connection is established.
Finally, as shown in
In step 701, data related to a product is received at an on-demand data base system from a first of the subscribers, e.g. a tenant in a multi-tenant database. A subscriber may be a one organization of a company, with another subscriber being another organization within the same company.
In step 702, a product object is created from the data and stored in a section of the database reserved for the user, or first subscriber. A product object is a database object that can include information related to a product that a business entity, for example, makes, sells, or uses. Typical fields of the object include a SKU #, a price, and a description. In one embodiment, the product object is created in a section of the on-demand database that is accessibly restricted to the first subscriber. For example, a section may be part of a table to which users of anther subscriber cannot read, write, or change data stored in that section.
In step 703, a request to share the product object with one or more second subscribers is received from the user, or first subscriber and communicated to the second subscribers, or connections of the user. The request may be made as a default operation based on properties of the product object. In one aspect, the request may be made as a one-click option.
In step 704, an acceptance of a second subscriber is received. The acceptance of the second subscriber may also be automated based on rules specified by the second subscriber. For example, the second subscriber may allow an automatic acceptance from a particular first party, and potentially one associated with a particular deal or opportunity, which may have already been shared.
In step 705, data associated with the product object is stored in a section of the on-demand data base that is reserved for the second subscriber. In this manner, employees of the second subscriber may have access to the product object created by the first subscriber in a manner consistent with a product object of the second subscriber. In one embodiment, the data is a copy of the product object, with the data being linked. In another embodiment, there may be one copy of the product object with pointers to the data being stored at the second subscriber.
In step 706, changes made to the product object are synchronized between the two subscribers. For example, if the first subscriber is a vendor and the second subscriber is a supplier, the first subscriber can change the number of products ordered by changing the product object. The number of products ordered as seen by the second subscriber is automatically updated.
Although method 700 is described for sharing a product object, embodiments can also provide sharing any other type of object or other information in a supply chain.
In another embodiment, only certain fields are shared and may be modified at any time. The user selects to “edit” 803 a specific object in order to change the fields provided for that object. As shown in
In another embodiment, the user may select (subscribe) to objects shared by a connection. As shown in
Referring back to
In some embodiments, the subscribed objects may require certain fields to be shared. Accordingly, these fields may be not be modifiable and provided as standard fields for that subscribed object.
The ability to update and map fields within connections may also allow for flexible process integration between connections by picklist value mapping. For example, one field of an object for a first tenant may be a picklist that has multiple values (e.g. 1-10). This field may also correspond to a picklist for the corresponding object of the other tenant. However, the picklist values may be different (e.g. 1-5). A mapping can be created to map the one set of picklist values to the other picklist values. As shown in
Products can be shared either as a member of the parent record (e.g. Account), individually or en-masse using a ‘Forward to Connections’ link on the Products list view. Accordingly, the products may be forwarded multiple connections and share thousands of records with those connections. Again, when a product or parent record is shared all selected child records are also forwarded to those connections. In one embodiment, limitations on the amount of child records forwarded may be required.
In one aspect, only a record may be shared or forwarded. In another embodiment, a record related to shared parent may be also be forwarded. Accordingly, a record and related child records may be forwarded together. In order to forward a record, the user is provided with a related list of available connections to which a record may be sent. Only objects published to and subscribed by at least one connection are made available within the related lists. In addition, objects such as tasks, attachments, and opportunity products may be shared when forwarding an opportunity to a connection. In order to forward the records, the user needs to own the record, i.e. the user may not forward all shared records unless having permissions to do so. Administrators may forward all records. The user may customize which parent and child records to forward, dependent on the connection with whom they are shared.
Alternatively, the user may elect to individually share related records, of a shared parent record. In this embodiment, the user opens the shared parent record details and forwards the record via the “Manage Connections” link, which was previously described. Forwarding these records may only be done through users with connections permissions and for records owned by the user. In one embodiment, on the related list, if the parent is not shared, the ‘Manage Connections’ link is not shown.
Furthermore, a record related to shared parent and shared related child records may be forwarded as long as the parent record has been accepted. When any related child record is shared, the record is automatically related to the parent record within the connection's records. If a relationship cannot be established between a shared child record within a partner, or recipient's account, the recipient may need to manually accept the record and provide a parent record name.
In some embodiments, the user may wish to manually accept parent records. In such embodiments, the user may chose to create a customized list view of the shared parent records by applying filters to the records received from connections. Accordingly, when records are shared, they arrive in a the user's inbox in a list view specified by the user. This customization may only be performed if an object has been subscribed to by at least one connection of the user. As described previously, if an auto accept is selected for the shared objects with a connection, the shared objects, or records related thereto will not be shown to the user.
In a further embodiment, the user may assign rules to the shared records upon acceptance of that record. This may be particularly useful when a new lead record is shared and the user wants to assign that lead to a particular record within their account, or another user within their organization. The assignment rules may be established and automatically provided, or manually chosen by the user when the lead is accepted.
In another embodiment, if a user manually accepts an opportunity from a connection, the user may chose to assign the opportunity to a related record within their database or a new or existing account or opportunity.
In a further embodiment, when an account is shared from a partner, may chose to create a new account or link the new account to an existing account. Further, the user may also assign the account to a contact within their organization.
In another embodiment, if a new contact is shared, the user may manually assign that contact to an existing account within their database, create a new account and assign the contact to a user within the organization. The option to assign a contact is only available if the contact is not associated with an existing account, i.e. it is not a child record.
Accordingly, in the instance when a user manually accepts a parent record, different fields may be made available during acceptance, dependent on the type of parent record shared. If the user chooses to manually accept a parent record, then record may be assigned to a specific records existing on the database.
In a further embodiment, the user may also share attachments associated with a product object with one or more connections. These attachments are stored similar to a child record and may be forwarded and/or published when other object related fields and/or data is modified and updated.
In order for a user to have increased visibility of the records shared, the page layout may be customized to provide an external related lists link, which shows details of the records shared.
In an alternative embodiment, the object may be forwarded and shared with a new connection if the owner of that connection is changed 1004.
Another modification that may be desirable in the related lists section is the addition of both a received and a sent connection column. The user may simply select “edit properties” of the related lists, and add fields to this section. By adding these two additional fields, the user may be able to quickly view the connection whom sent a record of an object (“received connection name”) as well as forward a record to one or more connections (“sent connection name”). This allows a user to share any related record within a shared object as well as individual tasks and opportunity products. The user does not have to update and/or share an entire object in order for a particular record to be forwarded to a partner. Additionally, the user may easily view who is responsible for sharing a particular record when more than one record is available regarding a particular object shared.
In an exemplary embodiment, when sharing a product, a ‘Product from Connections’ view can include the following fields: Connection Name, Sent Date, Product Name, Product Code, Product Family and Parent Record Name. In one aspect, the Parent Record Name is set if the Product is shared as a child of another record and is populated with the name of the parent record including type of object (e.g. Account: Acme). This may occur when an entire parent (e.g. an account) is shared, with the product object being shared as a child of the parent object.
The system first tries to insert the product and relate it to the shared parent record, however in some circumstances it may not be possible to commit this relationship at which time the product record will be visible in this view.
In one embodiment, the user may create multiple views using the criteria above and assign the same views to multiple internal users using role assignments. In another embodiment, if a product is shared by the user to a partner (e.g. a subscriber to which an object is shared), the connection owner in the partners organization receives an email notification.
If a product is shared as a parent, then the partner may accept the product using the ‘Products from Connections’ view described above. In one aspect, a requirement may be to either create a new product or link to an existing product. In another aspect, there may be no ‘Owner’ assignment requirements since products may not have an owner.
In one embodiment, product reports can be created using custom report types (CRT's). Using these reports users can see which products have been shared and updated by a connection. These reports can be run on specific data in fields such as accounts and contacts, opportunities, funds, etc. For example, a report may be run on a “Connections with Accounts” under the “Accounts and Contacts” data type. The report types may be additionally customized by the user, dependent on the customized objects within the user's account.
In another embodiment, validation rules can apply to Products as well. Users can use “Received Connection Name/ID” along with “Current User Alias contains pnet” to ignore validation rules when the product is shared with a connection. A user can use “Received Connection Name” and “Current User contains pnet” to run workflow rules. “Received Connection Name” and “Sent Connection Name” are available to create filter list views to show all products shared with one or more connections.
Finally, a user may wish to share a product catalog with a connection. In this embodiment, the product catalog may be manually accepted as a parent record, with assignment fields generated specifically for product catalog. If the catalog is a child record of an account, no acceptance is required by the user. If shared, a product catalog may include standard fields such as quantity schedules and revenue schedules.
In one embodiment, if “Quantity Schedules” (a field of the product object) are enabled and a customer is subscribing to the “Quantity Schedule” fields, then the user should ensure that all fields are subscribed to the same quantity schedule fields. For example, a partner's “Number of Quantity Installments” can be mapped to the user's “Number of Quantity Installments.” Other fields that are affected include Quantity Installment Period, Quantity Installment Period & Quantity Scheduling Enabled, which may be mapped as well.
In another embodiment, if “Revenue Schedules” are enabled and the user is subscribing to the “Revenue Schedule” fields then the user should ensure all fields are subscribed to the same revenue schedule fields. For example, a partner's “Number of Revenue Installments” can be mapped to the user's “Number of Revenue Installments.” Other fields affected include Revenue Installment Period, Revenue Schedule Type & Revenue Scheduling Enabled.
As an example of implementation, hi-tech hardware vendors can share their product SKU's with resellers and distributors who in-turn can have the latest and greatest information when registering a deal for a new prospect. Enabling these features allows vendors and partners to have real-time, in-sync product information while at the same time allow partners to register opportunities with the right product SKU's attached.
Also, users can share formula and roll-up summary fields with connections. With the availability of this feature, embodiments support all the major standard and custom field types. For example, a reseller may be selling products from multiple vendors on the same opportunity and only show the applicable amount to each vendor. Using RSF (roll-up summary) the reseller could share the right amount with each vendor based on the product sold.
In one embodiment in Error Logging, if an insert (accept) or update fails either due to system down, validation failure or uniqueness constraint then the following is logged in the Connection audit: Object (id if available) & Message. A task/email may be created for the “connection owner” for the target organization with the audit details in the subject.
In one embodiment, if the error takes place while accepting a record using the UI the user is given a message: ‘Failed to Accept one or more records since Validation or Uniqueness constraint was not met: check the connection audit trail for more details.
Similar to sharing product objects, other types of objects may be shared between connections. These objects may be related.
In some embodiments, data related to a product object and an opportunity can be shared. An opportunity is a business opportunity (e.g. a deal) between two or more subscribers of the on-demand database service.
Opportunity Products are similar to Detail objects but in this case are related to both Opportunities (master) as well as the Product object. In one embodiment, the quantity is a required field to be shared (e.g. published and subscribed).
Opportunity Products can be shared either as a member of the parent opportunity or individually using the “Manage Connections” link on the Connection Sent column. In either case, the opportunity product may be automatically associated to the parent opportunity in the target organization (e.g. the second subscriber). In one embodiment, the opportunity product is not shared on its own.
In one embodiment, the following rules are adhered to when sharing an opportunity product. The Opportunity is shared with the target connection(s), e.g. the second subscriber. Opportunity product is published and subscribed to the target organization. The related product is also be shared with the same target organization. The price book on the target organization's opportunity has the product to which the opportunity product is related to. If one or more of the requirements above is not met, the opportunity product is not be shared with the target organization.
In another embodiment, there is no manual acceptance required for Opportunity Products. The records are automatically associated to the parent opportunity. In other words, the acceptance is automatic, for example, as set or hardwired by code.
In addition, opportunity product reports can be created using CRT's as discussed previously. Additionally, the “Opportunity with Products” and “Opportunity with Products and Schedules” reports should be modified to include the “Connection” table so that the user can see all opportunity products shared with one or more connections.
Validation Rules apply to Opportunity Products as well. A user can use “Received Connection Name/ID” along with “Current User Alias contains pnet” to ignore validation rules when the opportunity product is shared with a connection. A user can use “Received Connection Name” and “Current User Alias contains pnet” to run workflow rules. In one embodiment, there are no list views for Opportunity Products.
An object may be shared from one subscriber to many second subscribers by selecting a link on that product object detail page. For example, the product object may be an account, a lead, an opportunity or other object recited in the disclosure. Accordingly, a vendor can share the same opportunity downstream with an ISV partner, reseller, distributor and upstream with the supplier. While the downstream partners are working together to close the deal, the supplier has real-time information on product requirements, close dates and stage enabling the supplier to source the right parts at the right time. One to many (1:Many) will enable a host of use cases including consulting companies bidding for the same project (e.g. EDS and IBM), and user master use cases.
Another example is where a new deal where the CM needs to collaborate with the local reseller as well as the consulting partner to close a deal with a user. At the same time, the CM may want to provide visibility upstream to the supplier who needs to be aware of when the opportunity will close so that the supplier can make the requisite orders and ensure the shipping company is notified of the new user. All this real-time automatic co-ordination is now possible with 1:Many. For example, a vendor can share with a Distributor, Supplier, Reseller, and a Solution Provider.
Therefore, the advantages of having database connections is that real-time updates and data can be communication between users, such as vendors, resellers, manufacturers and other agencies. Each user may have access to shared records from other partners in the business supply chain. In addition, embodiments can allow a user to share the same record with multiple business partners at the same time. This feature can be key to collaborative selling. As described above, these records are automatically kept in synch and may even be audited, if desired by the user of an account. Accordingly, users can keep track of the changed record as well as easily receive and send updates to/from multiple partners regarding that record in a timely manner and without additional communication steps required.
In one embodiment, related items may be shared when a record is forwarded after being assigned to a queue containing connections as members. For example, the record may be a mass lead, case or a custom object and may be sent to a queue when no partner connection is established. Accordingly, the record is made available to the next member of the queue. To this end, a setup option may enable sharing the related record when a record is forwarded due to queue assignment. This can apply to all connections and all types of objects that queues support. If the above is set, then anytime a record is forwarded due to queue assignment all the related records that are published to the other organizations should also be forwarded after the parent record has been accepted.
In one embodiment, users can write Apex (or other application code) and automatically share/stop sharing records based on changes to one or more fields on a record. For example, for an API Forward, the user can forward a record as a parent, forward a parent and child records the user has access to, and forward a child that is linked to a shared parent.
For an API Method, the following function interface may be used: forwardToConnection(Id, Map <Child Object Names>, Parent Record. ID). In one embodiment, only Id is required, with everything else being optional. In one aspect, if the child is supplied, then this acts as a deep share of parent with children. In another aspect, if the parent record Id is supplied, this acts as deep share of child with parent also shared (this will support 2 levels of sharing).
For API Stop Sharing, the following function interface may be used: API Method: stopSharingWithConnection (Id, Inbound Connection Id, Map <Outbound Connection ids>). In one embodiment, only Id is required. In one aspect, if this is supplied while the others are empty then both inbound and outbound are disconnected. In another aspect, if one or other (inbound and/or outbound) is supplied then only that connection is disconnected (i.e. inbound or outbound
In one embodiment, users can write intelligent rules when the sharing status on a record changes (e.g. Lead has been converted by partner organization—automatically convert lead into opportunity and share that opportunity back with the partner). External Sharing Related list may be made api available.
Accordingly, an administrator can auto-share any record. For example, based on specific criteria the administrator can automatically share an account and associated opportunities, contacts and tasks with multiple partners. Using an Apex trigger or even the excel connector/data loader the admin can make this happen.
Also, in one embodiment, users can use Apex triggers, custom code or other options including the excel connector and data loader to automatically share records with one or more connections. The new API methods can also be used to stop sharing with one or more connections. A benefit of this feature is two fold: users can define custom criteria to share/top share records and partners can build applications triggering s2s functionality and make this available on the AppExchange.
It should be understood that embodiments of the present invention as described above can be implemented in the form of control logic using hardware and/or using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software
Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium for storage and/or transmission, suitable media include random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. The computer readable medium may be any combination of such storage or transmission devices.
Such programs may also be encoded and transmitted using carrier signals adapted for transmission via wired, optical, and/or wireless networks conforming to a variety of protocols, including the Internet. As such, a computer readable medium according to an embodiment of the present invention may be created using a data signal encoded with such programs. Computer readable media encoded with the program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer readable medium may reside on or within a single computer program product (e.g. a hard drive or an entire computer system), and may be present on or within different computer program products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.
The above description of exemplary embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form described, and many modifications and variations are possible in light of the teaching above. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated.
The present application is a continuation of U.S. application Ser. No. 16/786,357, entitled “SHARING DATA IN A DATA STORAGE SYSTEM,” filed Feb. 10, 2020 (now U.S. Pat. No. 11,494,410), which is a continuation of U.S. application Ser. No. 15/069,236, entitled “SHARING INFORMATION IN A MULTI-TENANT DATABASE SYSTEM,” filed Mar. 14, 2016 (now U.S. Pat. No. 10,558,685), which is a continuation of U.S. application Ser. No. 12/693,374, entitled “Methods and Systems for Sharing Information in a Supply Chain.” filed Jan. 25, 2010 (now U.S. Pat. No. 9,286,364), which claims priority to from and is a non-provisional application of U.S. Provisional Appl. No. 61/146,968, entitled “Methods and Systems for Sharing Product Data among tenants of an on-demand database,” filed Jan. 23, 2009; the disclosures of each of the above-referenced applications are incorporated by reference herein in their entireties. This application is related to commonly owned U.S. patent application Ser. No. 12/145,325 entitled “Method and System For Sharing Data Between Subscribers of a Multi-Tenant Database Service” by Doshi et. al., filed Jun. 24, 2008, and provisional U.S. Patent Application No. 61/096,289 entitled “Automating Sharing Data Between Subscribers Of A Multi-Tenant Database Service” by Doshi et. al., filed Sep. 11, 2008, the disclosures of which are incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5577188 | Zhu | Nov 1996 | A |
| 5608872 | Schwartz et al. | Mar 1997 | A |
| 5649104 | Carleton et al. | Jul 1997 | A |
| 5715450 | Ambrose et al. | Feb 1998 | A |
| 5761419 | Schwartz et al. | Jun 1998 | A |
| 5819038 | Carleton et al. | Oct 1998 | A |
| 5821937 | Tonelli et al. | Oct 1998 | A |
| 5831610 | Tonelli et al. | Nov 1998 | A |
| 5873096 | Lim et al. | Feb 1999 | A |
| 5918159 | Fomukong et al. | Jun 1999 | A |
| 5963953 | Cram et al. | Oct 1999 | A |
| 6092083 | Brodersen et al. | Jul 2000 | A |
| 6161149 | Achacoso et al. | Dec 2000 | A |
| 6169534 | Raffel et al. | Jan 2001 | B1 |
| 6178425 | Brodersen et al. | Jan 2001 | B1 |
| 6189011 | Lim et al. | Feb 2001 | B1 |
| 6216135 | Brodersen et al. | Apr 2001 | B1 |
| 6233617 | Rothwein et al. | May 2001 | B1 |
| 6266669 | Brodersen et al. | Jul 2001 | B1 |
| 6295530 | Ritchie et al. | Sep 2001 | B1 |
| 6324568 | Diec | Nov 2001 | B1 |
| 6324693 | Brodersen et al. | Nov 2001 | B1 |
| 6336137 | Lee et al. | Jan 2002 | B1 |
| D454139 | Feldcamp | Mar 2002 | S |
| 6367077 | Brodersen et al. | Apr 2002 | B1 |
| 6393605 | Loomans | May 2002 | B1 |
| 6405220 | Brodersen et al. | Jun 2002 | B1 |
| 6434550 | Warner et al. | Aug 2002 | B1 |
| 6446089 | Brodersen et al. | Sep 2002 | B1 |
| 6535909 | Rust | Mar 2003 | B1 |
| 6549908 | Loomans | Apr 2003 | B1 |
| 6553563 | Ambrose et al. | Apr 2003 | B2 |
| 6560461 | Fomukong et al. | May 2003 | B1 |
| 6574635 | Stauber et al. | Jun 2003 | B2 |
| 6577726 | Huang et al. | Jun 2003 | B1 |
| 6601087 | Zhu et al. | Jul 2003 | B1 |
| 6604117 | Lim et al. | Aug 2003 | B2 |
| 6604128 | Diec | Aug 2003 | B2 |
| 6609150 | Lee et al. | Aug 2003 | B2 |
| 6621834 | Scherpbier et al. | Sep 2003 | B1 |
| 6654032 | Zhu et al. | Nov 2003 | B1 |
| 6665648 | Brodersen et al. | Dec 2003 | B2 |
| 6665655 | Warner et al. | Dec 2003 | B1 |
| 6684438 | Brodersen et al. | Feb 2004 | B2 |
| 6711565 | Subramaniam et al. | Mar 2004 | B1 |
| 6724399 | Katchour et al. | Apr 2004 | B1 |
| 6728702 | Subramaniam et al. | Apr 2004 | B1 |
| 6728960 | Loomans | Apr 2004 | B1 |
| 6732095 | Warshavsky et al. | May 2004 | B1 |
| 6732100 | Brodersen et al. | May 2004 | B1 |
| 6732111 | Brodersen et al. | May 2004 | B2 |
| 6754681 | Brodersen et al. | Jun 2004 | B2 |
| 6763351 | Subramaniam et al. | Jul 2004 | B1 |
| 6763501 | Zhu et al. | Jul 2004 | B1 |
| 6768904 | Kim | Jul 2004 | B2 |
| 6772229 | Achacoso et al. | Aug 2004 | B1 |
| 6782383 | Subramaniam et al. | Aug 2004 | B2 |
| 6804330 | Jones et al. | Oct 2004 | B1 |
| 6826565 | Ritchie et al. | Nov 2004 | B2 |
| 6826582 | Chatterjee et al. | Nov 2004 | B1 |
| 6826745 | Coker et al. | Nov 2004 | B2 |
| 6829655 | Huang et al. | Dec 2004 | B1 |
| 6842748 | Warner et al. | Jan 2005 | B1 |
| 6850895 | Brodersen et al. | Feb 2005 | B2 |
| 6850949 | Warner et al. | Feb 2005 | B2 |
| 7047276 | Liu et al. | May 2006 | B2 |
| 7062502 | Kesler | Jun 2006 | B1 |
| 7069231 | Cinarkaya et al. | Jun 2006 | B1 |
| 7181758 | Chan | Feb 2007 | B1 |
| 7209929 | Dominguez, Jr. et al. | Apr 2007 | B2 |
| 7221942 | Jung et al. | May 2007 | B2 |
| 7289976 | Kihneman et al. | Oct 2007 | B2 |
| 7340411 | Cook | Mar 2008 | B2 |
| 7356482 | Frankland et al. | Apr 2008 | B2 |
| 7373108 | Vidaillac | May 2008 | B2 |
| 7401094 | Kesler | Jul 2008 | B1 |
| 7412455 | Dillon | Aug 2008 | B2 |
| 7508789 | Chan | Mar 2009 | B2 |
| 7590564 | Ward et al. | Sep 2009 | B1 |
| 7620655 | Larsson et al. | Nov 2009 | B2 |
| 7630986 | Herz et al. | Dec 2009 | B1 |
| 7664861 | Guntupalli et al. | Feb 2010 | B2 |
| 7698160 | Beaven et al. | Apr 2010 | B2 |
| 7707222 | Manno | Apr 2010 | B2 |
| 7779039 | Weissman et al. | Aug 2010 | B2 |
| 7933871 | LaToza | Apr 2011 | B2 |
| 7991790 | Barker | Aug 2011 | B2 |
| 8015495 | Achacoso et al. | Sep 2011 | B2 |
| 8082301 | Ahlgren et al. | Dec 2011 | B2 |
| 8095413 | Beaven | Jan 2012 | B1 |
| 8095594 | Beaven et al. | Jan 2012 | B2 |
| 8275836 | Beaven et al. | Sep 2012 | B2 |
| 8307119 | Rochelle | Nov 2012 | B2 |
| 8453052 | Newman | May 2013 | B1 |
| 8457545 | Chan | Jun 2013 | B2 |
| 8484111 | Frankland et al. | Jul 2013 | B2 |
| 20010044791 | Richter et al. | Nov 2001 | A1 |
| 20020022986 | Coker et al. | Feb 2002 | A1 |
| 20020029161 | Brodersen et al. | Mar 2002 | A1 |
| 20020029376 | Ambrose et al. | Mar 2002 | A1 |
| 20020035577 | Brodersen et al. | Mar 2002 | A1 |
| 20020042264 | Kim | Apr 2002 | A1 |
| 20020042843 | Diec | Apr 2002 | A1 |
| 20020072951 | Lee et al. | Jun 2002 | A1 |
| 20020082892 | Raffel et al. | Jun 2002 | A1 |
| 20020129352 | Brodersen et al. | Sep 2002 | A1 |
| 20020140731 | Subramaniam et al. | Oct 2002 | A1 |
| 20020143997 | Huang et al. | Oct 2002 | A1 |
| 20020162090 | Parnell et al. | Oct 2002 | A1 |
| 20020165742 | Robins | Nov 2002 | A1 |
| 20030004971 | Gong et al. | Jan 2003 | A1 |
| 20030018705 | Chen et al. | Jan 2003 | A1 |
| 20030018830 | Chen et al. | Jan 2003 | A1 |
| 20030055880 | Liu et al. | Mar 2003 | A1 |
| 20030066031 | Laane | Apr 2003 | A1 |
| 20030066032 | Ramachandran et al. | Apr 2003 | A1 |
| 20030069936 | Warner et al. | Apr 2003 | A1 |
| 20030070000 | Coker et al. | Apr 2003 | A1 |
| 20030070004 | Mukundan et al. | Apr 2003 | A1 |
| 20030070005 | Mukundan et al. | Apr 2003 | A1 |
| 20030074418 | Coker | Apr 2003 | A1 |
| 20030120675 | Stauber et al. | Jun 2003 | A1 |
| 20030151633 | George et al. | Aug 2003 | A1 |
| 20030159136 | Huang et al. | Aug 2003 | A1 |
| 20030187921 | Diec | Oct 2003 | A1 |
| 20030189600 | Gune et al. | Oct 2003 | A1 |
| 20030204427 | Gune et al. | Oct 2003 | A1 |
| 20030206192 | Chen et al. | Nov 2003 | A1 |
| 20030225730 | Warner et al. | Dec 2003 | A1 |
| 20030233404 | Hopkins | Dec 2003 | A1 |
| 20040001092 | Rothwein et al. | Jan 2004 | A1 |
| 20040010489 | Rio | Jan 2004 | A1 |
| 20040015981 | Coker et al. | Jan 2004 | A1 |
| 20040027388 | Berg et al. | Feb 2004 | A1 |
| 20040128001 | Levin et al. | Jul 2004 | A1 |
| 20040186860 | Lee et al. | Sep 2004 | A1 |
| 20040193510 | Catahan, Jr. et al. | Sep 2004 | A1 |
| 20040199489 | Barnes-Leon et al. | Oct 2004 | A1 |
| 20040199536 | Barnes-Leon et al. | Oct 2004 | A1 |
| 20040199543 | Braud et al. | Oct 2004 | A1 |
| 20040230676 | Spivack | Nov 2004 | A1 |
| 20040249854 | Barnes-Leon et al. | Dec 2004 | A1 |
| 20040260534 | Pak et al. | Dec 2004 | A1 |
| 20040260659 | Chan et al. | Dec 2004 | A1 |
| 20040268299 | Lei et al. | Dec 2004 | A1 |
| 20050015466 | Tripp | Jan 2005 | A1 |
| 20050050555 | Exley et al. | Mar 2005 | A1 |
| 20050065925 | Weissman et al. | Mar 2005 | A1 |
| 20050091098 | Brodersen et al. | Apr 2005 | A1 |
| 20050132221 | Marcjan | Jun 2005 | A1 |
| 20050198085 | Blakey et al. | Sep 2005 | A1 |
| 20050210500 | Stone | Sep 2005 | A1 |
| 20050215252 | Jung et al. | Sep 2005 | A1 |
| 20050223022 | Weissman et al. | Oct 2005 | A1 |
| 20050283478 | Choi et al. | Dec 2005 | A1 |
| 20060021019 | Hinton et al. | Jan 2006 | A1 |
| 20060168043 | Eisenberger et al. | Jul 2006 | A1 |
| 20060206834 | Fisher et al. | Sep 2006 | A1 |
| 20070168958 | Huang et al. | Jul 2007 | A1 |
| 20080244184 | Lewis et al. | Oct 2008 | A1 |
| 20080249972 | Dillon | Oct 2008 | A1 |
| 20080292080 | Quon et al. | Nov 2008 | A1 |
| 20090043689 | Yang | Feb 2009 | A1 |
| 20090063415 | Chatfield et al. | Mar 2009 | A1 |
| 20090100342 | Jakobson | Apr 2009 | A1 |
| 20090138808 | Moromisato | May 2009 | A1 |
| 20090177744 | Marlow et al. | Jul 2009 | A1 |
| 20090192845 | Gudipaty | Jul 2009 | A1 |
| 20090327244 | Rizal | Dec 2009 | A1 |
| 20110218958 | Warshavsky et al. | Sep 2011 | A1 |
| 20110247051 | Bulumulla et al. | Oct 2011 | A1 |
| 20120042218 | Cinarkaya et al. | Feb 2012 | A1 |
| 20130218948 | Jakobson | Aug 2013 | A1 |
| 20130218949 | Jakobson | Aug 2013 | A1 |
| 20130218966 | Jakobson | Aug 2013 | A1 |
| 20130247216 | Cinarkaya et al. | Sep 2013 | A1 |
| 20140359537 | Jackobson et al. | Dec 2014 | A1 |
| 20150006289 | Jackobson et al. | Jan 2015 | A1 |
| 20150007050 | Jackobson et al. | Jan 2015 | A1 |
| 20150095162 | Jackobson et al. | Apr 2015 | A1 |
| 20150142596 | Jackobson et al. | May 2015 | A1 |
| 20150172563 | Jackobson et al. | Jun 2015 | A1 |
| Entry |
|---|
| Office Action in U.S. Appl. No. 12/693,374 mailed Apr. 27, 2012, 28 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Nov. 7, 2012, 30 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Mar. 1, 2013, 34 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Oct. 28, 2013, 47 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Apr. 24, 2014, 34 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Dec. 19, 2014, 29 pages. |
| Office Action in U.S. Appl. No. 12/693,374 mailed Apr. 9, 2015, 29 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230185826 A1 | Jun 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61146968 | Jan 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16786357 | Feb 2020 | US |
| Child | 18053301 | US | |
| Parent | 15069236 | Mar 2016 | US |
| Child | 16786357 | US | |
| Parent | 12693374 | Jan 2010 | US |
| Child | 15069236 | US |
