Abstract:
A framework and method for managing business data transactions resides outside individual business systems and allows creation of a policy for classification of each data element for all data schema in transit between processes. The framework allows identification of data sets by document type and endpoint, so that individual data elements of a schema can be validated, and edited or deleted if necessary, during their transit between endpoints, such as between trading partners. Because the policy is built and enforced outside the individual endpoint business systems, expensive customizations within each transactional system are avoided.

Description:
BACKGROUND 
       [0001]    The rapid growth of electronic business support tools has increased the efficiency and responsiveness of business both on a local level and globally. Enterprise resource planning (ERP) systems, business automation tools, customer relationship management (CRM) tools, warehouse and inventory management systems, business-to-business (B2B) and business to consumer (B2C) auctions are all examples of categories of electronic business tools. Hundreds, if not thousands, of implementations of these tools are commercially available along with ‘homegrown’ versions of these and other tools. Message-based systems and queue-based systems, web services, as well as direct feeds, can be used to connect these tools to each other for information sharing and integration of tasks. 
         [0002]    The actual integration of these tools can be a significant effort, both in initial setup and in maintenance, as endpoint tools change versions or are replaced. The endpoints for data-based transactions can be internal to an enterprise, such as between a sales order processing system and a manufacturing planning system. Other endpoints can be between internal and external entities, such as a corporate purchasing system and a supplier sales order processing system. The information available to a given system is likely to be well beyond the needs of an individual transaction. For example, the corporate purchasing system is likely to have access to corporate sales information, competitive pricing, supplier contract status, overseas vendors, and more. However, a purchase order sent to the supplier sales order processing system may need little more than a part number, quantity, ship-to address, and volume purchase agreement reference. Care must be taken when developing the interfaces between systems that all the required data and none of the additional data are present when a data-based transaction leaves the sphere of control of the sending system, be it an internal boundary or an inter-enterprise boundary. 
         [0003]    XML, or extended markup language, and the associated XSD, or XML schema definition, have brought marked improvements to inter-process collaboration by creating self-defining documents that are not bound to rigorous bit-level formatting conventions. However, XML does little or nothing to prevent transmission of unneeded, unwanted, or privileged information between business data endpoints. 
       SUMMARY 
       [0004]    A business framework for validating and amending data of electronic transactions between specified endpoints is based on a policy engine that extracts data field information from XML documents and creates a data policy document. The policy may be created via a user interface for setting requirements for each data element in a schema, such as to include or exclude, or to place limits on the data of a given schema element. A given policy may correspond to business documents having a given schema that are in transit between defined endpoints. Because a given schema defines a particular document type, the policy is defined by document type and the source and destination endpoints. The endpoints may be one-to-one or one-to-many, depending on the document type and the business requirement. 
         [0005]    The policy may be applied to both inbound and outbound data. When data is inbound, it may be validated as coming from an approved source endpoint and may be further validated as containing data required by the policy before being relayed to the destination endpoint. Outbound data may be validated as being directed to an approved destination endpoint and may be screened to ensure that it contains only data permitted for release to that endpoint. Should non-permitted data be found, it may be removed from the outbound data. 
         [0006]    The policy engine may present a simple tool for creation and maintenance of business data policies that can be created or updated without making changes to either endpoint system. Endpoints can be changed, added, or removed as trading partners and internal support teams change relationships. Thus, identical transactions between internal and external support teams or trading partners may be generated by a business application, but the actual data sent may be tailored by the policy engine according to destination in conjunction with a corresponding policy rather than by expensive customizations to the business application. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0007]      FIG. 1  is a simplified and representative network; 
           [0008]      FIG. 2  is a simplified and representative block diagram of a computer suitable to implement an embodiment of the business document data policy; 
           [0009]      FIG. 3  is a method of developing a business document data policy; 
           [0010]      FIG. 4  illustrates the method of  FIG. 3 ; 
           [0011]      FIG. 5  is a further illustration of the method of  FIG. 3 ; 
           [0012]      FIG. 6  is a method of applying a business document data policy to incoming data; 
           [0013]      FIG. 7  is an illustration of the method of  FIG. 6 ; 
           [0014]      FIG. 8  is a method of applying a business document data policy to outgoing data; and 
           [0015]      FIG. 9  is an illustration of the method of  FIG. 8 . 
       
    
    
     DETAILED DESCRIPTION 
       [0016]    Although the following text sets forth a detailed description of numerous different embodiments, it should be understood that the legal scope of the description is defined by the words of the claims set forth at the end of this disclosure. The detailed description is to be construed as exemplary only and does not describe every possible embodiment since describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments could be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims. 
         [0017]    It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘______’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this patent is referred to in this patent in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term by limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based on the application of 35 U.S.C. § 112, sixth paragraph. 
         [0018]    Much of the inventive functionality and many of the inventive principles are best implemented with or in software programs or instructions and integrated circuits (ICs) such as application specific ICs. It is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation. Therefore, in the interest of brevity and minimization of any risk of obscuring the principles and concepts in accordance to the present invention, further discussion of such software and ICs, if any, will be limited to the essentials with respect to the principles and concepts of the preferred embodiments. 
         [0019]      FIG. 1  illustrates a network environment  10  that may be used to in transacting electronic business. A network cloud  15  may support a wide area network connections, such as the Internet. A network  20  coupled to the network cloud  15  may connect an individual computer  22  that may be, for example, an electronic business transaction endpoint. Another network  24  may be coupled to the network cloud  15  and to a local area network  28  via a network interface  26 . The network interface  26  may be a proxy server and may incorporate a firewall or other network security device. In another embodiment, the network interface  26  may be a simple data modem. Coupled to the local area network  28  may be a variety of individual subnets  30  coupled to a server  32  a personal computer  34  and an application server  36 . The server  32  may also host business applications. In the description below, any of the computers  22 ,  32 ,  34 ,  36  may be valid endpoints for business data transactions. In this exemplary embodiment, transactions between computer&#39;s  30  to  34  and  36  may be considered internal transactions or transactions between computer  22  and any other computer would be considered an external transaction. Boundaries between computers or systems may be defined at the process level, the computer level or the network level. Setting a boundary for a given business data transaction may depend on the nature of the transaction and the relationship between the source and destination endpoints, as discussed in more detail below. 
         [0020]      FIG. 2  illustrates a computing device in the form of a computer  110  that may host one or more of the embodiments of the current disclosure and is discussed in detail to provide a context for subsequent discussions. 
         [0021]    Components of the computer  110  may include, but are not limited to a processing unit  120 , a system memory  130 , and a system bus  121  that couples various system components including the system memory to the processing unit  120 . The system bus  121  may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. 
         [0022]    The computer  110  typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer  110  and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer  110 . Combinations of the any of the above should also be included within the scope of computer readable media. 
         [0023]    The system memory  130  includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM)  131  and random access memory (RAM)  132 . A basic input/output system  133  (BIOS), containing the basic routines that help to transfer information between elements within computer  110 , such as during start-up, is typically stored in ROM  131 . RAM  132  typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit  120 . By way of example, and not limitation,  FIG. 2  illustrates operating system  134 , application programs  135 , other program modules  136 , and program data  137 . 
         [0024]    The computer  110  may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,  FIG. 2  illustrates a hard disk drive  140  that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive  151  that reads from or writes to a removable, nonvolatile magnetic disk  152 , and an optical disk drive  155  that reads from or writes to a removable, nonvolatile optical disk  156  such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive  141  is typically connected to the system bus  121  through a non-removable memory interface such as interface  140 , and magnetic disk drive  151  and optical disk drive  155  are typically connected to the system bus  121  by a removable memory interface, such as interface  150 . 
         [0025]    The drives and their associated computer storage media discussed above and illustrated in  FIG. 2 , provide storage of computer readable instructions, data structures, program modules and other data for the computer  110 . In  FIG. 2 , for example, hard disk drive  141  is illustrated as storing operating system  144 , application programs  145 , other program modules  146 , and program data  147 . Note that these components can either be the same as or different from operating system  134 , application programs  135 , other program modules  136 , and program data  137 . Operating system  144 , application programs  145 , other program modules  146 , and program data  147  are given different numbers here to illustrate that, at a minimum, they are different copies. 
         [0026]    The computer  110  may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer  180 . The remote computer  180  may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer  110 , although only a memory storage device  181  has been illustrated in  FIG. 2 . The logical connections depicted in  FIG. 2  include a local area network (LAN)  171  and a wide area network (WAN)  173 , but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. 
         [0027]    When used in a LAN networking environment, the computer  110  is connected to the LAN  171  through a network interface or adapter  170 . When used in a WAN networking environment, the computer  110  typically includes a modem  172  (telephone, cable, DSL, etc.) or other means for establishing communications over the WAN  173 , such as the Internet. The modem  172 , which may be internal or external, may be connected to the system bus  121 , the network interface  170 , or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer  110 , or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,  FIG. 2  illustrates remote application programs  185  as residing on memory device  181 . Such remote application programs may include business systems involved in electronic business transactions as are discussed in more detail below. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. 
         [0028]    Referring to  FIG. 3 , a method  300  of developing a business application data policy is discussed and described. At block  302 , a business document, such as an XML schema, may be analyzed for document definition, that is, the type of document by structure and origin. The document schema may be representative, or may be an actual document from a live or simulated business transaction. Referring briefly to  FIG. 4 , a representative document schema  402  is shown. The document schema  402  has various identifying information and definitions, as well as data elements identified by name. Returning to  FIG. 3 , at block  304  a data policy engine, such as data policy engine  404  of  FIG. 4 , may begin to identify data elements from the document schema  402 . The process may continue at block  306  where it may be determined if additional elements of the document schema  402  are present. If so, processing may continue by following the ‘yes’ branch from block  306  to block  308  for the next data element to be processed. When all the data elements of the document schema  402  have been identified, the ‘no’ branch from block  306  may be followed to block  310  and a data model may be built representing the business document.  FIG. 4  illustrates an inferred XML structure  406  shown in a tree representation based on the original document schema  402 . 
         [0029]    At block  312 , rules for each data element may be determined. This may be accomplished through a variety of mechanisms, for example, in one embodiment a table may be presented via a user interface supported by the data policy engine  404  and a user may simply select one or more characteristics for each data element.  FIG. 4  illustrates such an exemplary table  410  with one row for each inferred data element by group. The row for Field  1   412  is shown as being enabled and required. The row for Field  2   416  is shown as being enabled but not required. The rows for Field  3   418  and the SubGroup  420  are shown as not being enabled and are therefore also not required. 
         [0030]    Table 1, below, illustrates a similar table having further data classifications that may be representative of other embodiments of the business data policy. In this example, a Range column has been added, as well as a Restricted column. For Field  1 , the range has been restricted to any number of alpha characters, while Field  2  is shown as being restricted to values of red, green, or blue. Other columns, ranges, or restrictions may be used depending on the particular API and associated endpoints. 
         [0000]    
       
         
               
               
               
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
               
                 XPath - 
                   
                   
                   
                   
               
               
                 endpoint1:endpoint2 
                 Enabled 
                 Required 
                 Range 
                 Restricted 
               
               
                   
               
             
             
               
                 /Document/Group 1/ 
                 Yes 
                 Yes 
                 [a–z; A–Z]* 
                 No 
               
               
                 Field 1 
               
               
                 /Document/Group 1/ 
                 Yes 
                 No 
                 No 
                 Red|Green| 
               
               
                 Field 2 
                   
                   
                   
                 Blue 
               
               
                 /Document/Group 2/ 
                 No 
                 — 
                 — 
                 — 
               
               
                 Field 3 
               
               
                 /Document/Group 1/ 
                 No 
                 — 
                 — 
                 — 
               
               
                 SubGroup 
               
               
                   
               
             
          
         
       
     
         [0031]    Another mechanism for capturing rules related to a particular may be used, for example, a inference engine may look at similar policies and seed data classifications from equivalent or similar data fields, endpoints, or both. 
         [0032]    At block  314 , endpoint data may be added to identify which data paths are applicable for the given policy rules. Each policy rule set may apply to one or more document type/endpoint group. Referring now briefly to  FIG. 5 , the table  504  built at block  312  of  FIG. 3 , with endpoint data  505  and individual Field rows  506 ,  508 ,  510 ,  512  may be used by the data policy engine  514  to create a data policy schema  516  from the document schema  502 . Note that even though the document schema  502  specifies that Field  1  is optional (minOccurs=“0”), because the policy rules at row  506  require Field  1 , the data policy schema  516  reflects that Field  1  is a required element (minOccurs=“1”). Because the Field  3  and the SubGroup elements are not enabled, the individual Field  3  and SubGroup elements are not shown in the data policy schema  516 . Further, because Group  2  now has no elements, it has also been removed from the data policy schema  516 . 
         [0033]    When this data policy schema  516  is subsequently applied to a document, those elements associated with Group  2 , if present, may be removed or the document may simply be rejected. Also, if Field  1  is not present in the document, the document may be rejected and not further processed or passed to its destination endpoint. 
         [0034]    Returning to  FIG. 3 , at block  316 , the data policy schema developed at block  314 , for example, data policy schema  516  of  FIG. 5 , may be stored for subsequent use in processing business documents in transit between end points. This general process may be repeated for each endpoint pair and document type for which data validation and processing is desired. Each data policy schema may be identified by endpoint pair and document type when being stored. Depending on the network architecture and a particular business implementation, the various data policy schema may be stored together, or may be stored separately according to various criteria, such as, network topology or use of a one set of policy schema for inbound data and another set of policy schema for outbound data. 
         [0035]      FIG. 6  is a method  600  of applying a business application data policy to incoming data. At block  602 , serialized data or an XML document may be received from either external endpoints or internal endpoints. Referring briefly to  FIG. 7 , representative external endpoints  702  may be connected by a network cloud  704  to an integration framework  708  that may incorporate one or more processes executing a business application policy engine. Internal endpoints  706  may be directly connected to the integration framework  708 . Data crossing the boundary of the integration framework  708  may be subject to validation or qualification by the data policy engine. 
         [0036]    At block  604  of  FIG. 6 , serialized data may need to be de-serialized before further processing is done. At block  606  the document type, for example a particular XML schema, may be determined by examining information in the document. Additionally, endpoint information may be explicitly extracted from data in the document, or may be concluded by network information available with the document, for example, Internet protocol (IP) addresses in a transport header. When the appropriate document type and endpoint information has been determined, an appropriate data policy schema may be selected at block  608 . 
         [0037]    At block  610 , the data policy schema selected may be used to validate that the particular document type is appropriate for use between the identified endpoints. If allowed, processing may continue at block  612 . The data may be validated to determine that all required elements are present and that the contents meet defined criteria. Optionally, elements that are not enabled (i.e. authorized) may be removed. When all the data elements have been validated or edited, at block  614 , the document may be transmitted to its destination endpoint, as depicted in  FIG. 7  by document  710 . If the document type/endpoints are not allowed or required data elements are not present or not valid in the document itself, the received document may be discarded and, optionally, an error message sent to the source endpoint, the destination endpoint, or both. 
         [0038]      FIG. 8  is a method  800  of applying a business application data policy to outgoing data. At block  802 , a schema or other appropriately formatted business data may be received for transmission to an endpoint. Referring briefly to  FIG. 9 , business data  902  may be generated in a business application and forwarded for transmission. In some embodiments, the business data  902  may be generated internal to the integration framework  904  or may be received via a network (not depicted). In one embodiment, the business data  902  is generated by a well-known internal source, so that the internal endpoint information is readily available. Returning to  FIG. 8 , at block  804 , the internal endpoint information may be known, and the document type and destination endpoint may be extracted from the data received at block  802 . At block  806 , an appropriate policy schema, such as data policy schema  906  shown in  FIG. 9 , may be retrieved, using keys corresponding to source endpoint, destination endpoint, and the document type. 
         [0039]    At block  810  of  FIG. 8 , the data policy schema may be used to validate that the document type and specific document are valid for transmission between the source endpoint and the requested destination endpoint. If the endpoint pair is not valid for that document type, the business data  902  may be discarded and, optionally, an error message sent to the source process/endpoint. 
         [0040]    If the endpoints anddocument type are valid, processing may continue at block  812  to verify that each data element conforms to the requirements of the data policy, that is, that each data element required is present and has appropriate values. Further checks may be made to determine if disabled data elements appear. If present, disabled data elements may be removed. However, if required elements are not present or do not conform to required types or values, the yes branch from block  812  may be taken to block  818  and the schema discarded. Optionally, an error message returned to the source endpoint, the destination endpoint, or both. 
         [0041]    If the data elements are valid and correct and if only disabled elements are present, the no branch from block  812  may be taken to block  814 . Any disabled elements may be removed and, at block  816 , the data may be serialized and sent to the destination endpoint across the boundary of the integration framework  904 . As shown in  FIG. 9 , document  908  may be sent to an external endpoint  912 , or an internal endpoint  910 . 
         [0042]    The use of an integration framework, such as an existing integration framework or a specialized one for this purpose, allows a data policy engine to be used to create, maintain and enforce data policies for data in transit between entities. Such entities may be highly friendly, as in related internal business tools, or may have adversarial overtones, such as customer/supplier business integration. The ability to screen and qualify data as it passes an incoming boundary to determine that the required data is present and the ability to screen data as it passes an outbound boundary to determine that only appropriate data is present gives business integration managers a new and powerful tool for managing relationships. Further, because a data manager does not have to constantly customize each business tool as new endpoints are added or changed, costly, and potentially risky, modifications to business critical systems can be avoided. 
         [0043]    By placing the data policy engine at critical boundaries between business units and between internal and external trading partner systems, security can be enforced at appropriate points in the network and not applied blindly to all data in transit, avoiding superfluous data handling when no validation or screening is required. Thus, both business managers and data managers benefit from the application of the data policy enforcement provided by the tools and methods described above. 
         [0044]    Although the forgoing text sets forth a detailed description of numerous different embodiments of the invention, it should be understood that the scope of the invention is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possibly embodiment of the invention because describing every possible embodiment would be impractical, if not impossible. Numerous alternative embodiments could be implemented, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims defining the invention. 
         [0045]    Thus, many modifications and variations may be made in the techniques and structures described and illustrated herein without departing from the spirit and scope of the present invention. Accordingly, it should be understood that the methods and apparatus described herein are illustrative only and are not limiting upon the scope of the invention.