TITLE

SECURE SERVICE NETWORK

TECHNICAL FIELD

The present invention relates to a secure electronic information exchange network using a service infrastructure with a participant gateway that provides private bilateral security between participants. Authentication, authorization and encryption are administered through single participant gateways, and optionally, a global gateway, that processus] unique participant identifiers associated with a participant and/or a domain. BACKGROUND ART

Current drawbacks of the Internet include, inter alia, the lack of quality of service, rouge user attacks (hackers), the absence of standards for global authentication and authorization, the lack of service level enforcement and tools for governance, the lack of standard application implementation and reporting, and the lack of assured delivery and status reporting. There is thus a need for a network solution that provides the benefits of the Internet such as flexibility, dynamics, and end user controllability, without the foregoing drawbacks.

There is a further need to establish a common service infrastructure that supports a higher level of commonality on a standard IP network focused on addressing shortfalls in the current Internet model so that secure and reliable connectivity (one to one; one to many; many to one; many to many) can be accomplished in a cost effective and unrestrictive fashion.

Although many individual technologies exist, such as VPNs, firewalls, authentication, and encryption protocols, ostensibly to provide security, no solution is sufficiently adaptable to provide a secure service network offering that addresses current Internet shortcomings. The secure service network environment provided by the invention supports information sharing in a convenient manner not currently available. DISCLOSURE OF INVENTION

The secure service network (SSN) of the present invention provides a solution and process framework that rapidly and simply establishes trusted, authorized, private and encrypted connections among a diverse group of participants on new or existing IP based network infrastructure. The invention represents a shared multi function

service network (SMFSN) and service infrastructure capable of supporting a broad range of secure and private activities on any private or public IP infrastructure. The invention provides a SMFSN by leveraging or adding a service layer on top of an existing or new IP network infrastructure to provide a secure implementation of services across trusted and un-trusted network connections.

The service layer includes, as needed, full encryption, authentication, authorization and participant privacy. Advantages include low cost, low complexity, flexibility, user friendliness and controllability; secure service over a common network infrastructure results in a lower cost of ownership for all users. Users include the data provider, the data requestor and the network provider. An infrastructure establishes a secure service network that includes full authorization and authentication support, which can be enforced at either the enterprise or local level, thereby delivering control of access to data and services to the owner of the data and/or to a central governance body.

Network security comprises encryption, privacy, authentication, service access authorization, local service access control, and privilege revocation. The invention supports all forms of network relationships and real time, batch, inquire, and update functions, quality of service prioritization, and enterprise and end point managed security. Value oriented service offerings in a technical design provide for simplified expansion of the service offerings.

The invention offers transition from fixed point to point application specific EDI solutions to a shared secure service network with services for customers, suppliers, and or partners on a common infrastructure. The architecture includes a common framework for business infrastructure and reporting, governance, audit, security, and billing. The invention offers the benefit of real time sharing of information between and among participants, in which the owner of the information maintains unique capabilities and control over the information, the consumer of the information draws upon the information directly related to information value, and the deliverer of the Information receives value added functionality at a lower cost.

Multiple service definitions are supported across any number of service domains; user domains are defined in a manner to restrict knowledge of participants to a given domain of users. A domain establishes a community of users with common trust relationships; a user is provided the capability to protect the privacy of

W participants without requiring a separate dedicated network. As a result, a participant can define an infinite number of domains. Users may be aware of domain members but may not be aware of the services that each member can access unless the provider of the services shares this information. In this manner, a service provider on the network can publish a service for one or many users in a given domain.

Domains can be comprised of parent child relationships such that some services and participants can be in global domains - while others are in subsets of a global domain. Domains support the business development of contractual relationships for a set of users and any number of services. For example, in a domain of participants only, defined as part of a domain access service for that domain, services are then only available to domain members that are defined in an access control list (ACL). One domain can not see participants or services for other domains; ACLs are typically used to authorize a participant's access to a service within a domain. BRIEF DESCRIPTION OF DRAWINGS

The invention is described more fully in the following description of the preferred embodiment, considered in view of the drawings in which:

Figure 1A, Figure 1B and Figure 1C show the general infrastructure of an SSN including secure service gateways (SSGs) intermediate the participants in the network.

Figure 2 is chart showing SSN information exchange and transaction functions and interactions in embodiment of the invention suitable for a financial institution.

Figure 3 is a diagram of a SSN showing security and service gateways (or nodes) and sub level networks.

Figure 4 is an example of a defined relationship in a SSN implementation.

Figure 5 is a diagram of an example of a financial services SSN linked in a invention.

Figure 6 shows interactions between and among SSN user and service domains.

Figure 7k shows the SSN supporting a hybrid governance model providing local data access controls with global enforcement. (In the bold connections shown at 190, the secure virtual service network connections that are established on a peer to peer basis; clear channel or open connections are shown by the dashed lines 191.)

Figure 7B shows an alternate SSN supporting a strong local or distributed governance model with central fail safe enforcement.

Figure 7C shows another example of a SSN supporting a strong central governance and enforcement model with central service access control and global enforcement.

Figure 8 shows a logical representation of network or communication interfaces to the SSG or the Global Secure Service Gateway (GSSG) which administers the network, reflecting at least one SSN interface, one participant internal interface, and one out of band interface, isolated from the SSN network interface. The out of band interface is used for security and administration activities in support of the SSN.

Figure 9A, Figure 9B and Figure 9C depict sample domain and ACL tree hierarchies that can be implemented as part of authentication and/or authorization protocols in the SSN.

Figure 10 depicts a bilateral connection at 190 between participants in a secure virtual service network connection that is established in an SSN implementation.

Figure 11 depicts, in the bold connections shown at 190, the secure virtual service network connections that are established on a peer to peer basis over a physical IP infrastructure by the SSN. The secure connection is SSG to SSG independent of physical path. In one embodiment, the secure connection is established only following the successful negotiation of mutual authentication between SSGs using digital certificates signed by the certificate authority.

Figure 12 shows an embodiment of the invention in which a personal transceiver cell phone with an SSG operates in a secure GSSG administered network, allowing point of sale secure payments initiated by the transceiver, securely administered through GSSG administered SSGs at all network participant nodes with virtual secure network connections. Interconnections in the network to debit/credit, payment, exchange, management and settlement functions at a merchant's commercial bank are provided. A SMFSN is enabled where all activity on the network is isolated and discrete from all other traffic as defined by a service. This allows multiple payment types, products, services, applications, users, and functions to be run one the same physical network connection but maintains discrete isolation for security, privacy, billing, SLA, and compliance needs for all traffic. This also allows infinite functions to run in isolation across a converged network without changes to the

underlying transport. The result is a secure multi function network capability independent of carrier provider, or carrier type (wired or wireless) including the ability to traverse private and public networks including the Internet with absolute security, audit ability, and end to end compliance reporting.

Figure 13 shows an alternate configuration of architecture interconnections showing the relationships between and among the user's retail interconnections and the merchants' network connections to the merchants' bank[s] whereby any retail payment type or transaction is captured, converted, monitored, securely managed, and settled.

Figure 14 shows a further alternative in which a user of a cell phone transceiver initiates a POS transaction accessing a checking account, and biometric identification and authorization security measures are implemented through media interconnected with the user's cell phone. All network transactions are discrete, isolated, and specific to the participants of the transaction as defined by a service (which can be an application, web service or business function on a traditional network) on the SSN or SMFSN network of the invention.

Figure 15A and Figure 15B depict the secure network architecture implemented in the invention. The SSN is a network implementation that creates and manages a Virtual Secure Service network topology on any mix of physical networks. In this manner the SSN secures the exchange of digital information between parties in a trusted, reliable, and manageable manner across any network or combination or network elements. In addition all devices, application or web services running on the network inherit a based security model that allows for the creation of a secure multi function network over a shared physical network connection.

In a typical SSN, GSSGs administer one to one, one to many, etc., network interconnections through administered SSGs at user's access points. All administration services enforce the same security for all SSN services assuring protection and privacy of all participants. Multiple governance models are supported as defined in our prior applications. The invention uniquely provides the ability to securely manage network service from a wide range of providers down to an individual device such as the cell phone. In this manner, the network facilitates the presentment and access to market communities from a wireless or portable payment device independent of the provider of the device. For example, the end user may select from

a list of payment types and payment providers at the point of presentment, allowing the user to shop for the best payment and settlement mechanism from a wide range of providers to meet the needs of a given transaction. The functions described can all be accomplished over the same physical network connection while maintaining absolute security for each and every transaction type and service down to the specific transaction and service by provider. Additionally, the SSN allows merchants to provide multiple security functions and payment types to any endpoint on the network. In this manner, the merchants or merchant financial providers provide absolutely secured services.

Figure 16 illustrates SSN management between different networks.

Figure 17 shows an example of real time monitoring available in the net settlement architecture optionally implemented at the site of a debit/credit/payment recording or collection facility. Real time net settlement (NSS) is a settlement solution that provides a real-time view of balances and payments exchanges between members of a community.

Figure 18 shows the payments management center (PMC), an enterprise payments repository, optionally implemented at the site of a debit/credit/payment recording, collection facility, or as a service on the network, that delivers a total view of payments and provides real time tracking of all payment and payments type across all LOBs or service providers.

Figure 19 illustrates the functions of the payments exchange network. The payments exchange (eP ^x ) is a payments exchange solution that processes, clears, and routes all payments on a single, straight-through platform. This can be operated by a participant on the network as a service bureau or as a service on the network for other payment and payee providers allowing the creation of aggregated services by combining multiple services into an composite service while maintaining all of the elements of security previously identified.

Figure 20 Illustrates the Log Record detail for a transaction on SSN. Specifically the information captured for each and every transaction is reflected. Universal Identifiers (UIDs), request UID, originator UID, and correlation UID are logged, and, additional information such as elapsed time, date/time, response Code, participants, layer 3 mapping, and message sizes are tracked and captured for all

traffic on SSN. The information is specific to a service and specific participants which allows privacy and an end to end audit specific to each participant on the SSN.

Figure 21 illustrates a provisioning process window from the SSN management console for services on the network, reflecting the ability for a wide range of services, service types, service providers and service requesters to be provisioned and managed across any combination of physical networks.

Figure 22 shows an example of bill presentment and payment architecture using the invention.

Figure 23 illustrates an end to end payments solution provided by the invention. BEST MODES FOR CARRYING OUT THE INVENTION

The invention provides a secure service network in which at least two participants having a relationship are connected to the network via secure service gateways and share information, data, payments, images, and the like located at one or more service providers within one or more service domains where a mutual trust relationship is established. Access to information is determined using trust relationships for high level domain partitioning and access control for low level authorization; in one embodiment, the trust relationships are established within or between and/or among domains upon the establishment of a root certificate of authority (CA), that signs one or more intermediate CAs, which in turns signs one or more subordinate CAs. This hierarchy supports one to one, one to many, and many to many participant domains and service definitions.

The invention establishes a secure virtual service network (VSN) connection over any IP backbone which allows the sharing of information via services for a given service provider and requestor or domain of participants. The duration of the connection is user configurable and may range from indefinitely to the life of a given service request and its associated response. In an embodiment of the SSN, for a connection to be established, the requestor and service provider authenticate each other via a mutual SSL negotiation; if the authentication fails a connection will not be established. Once authentication is verified and a connection is established, authorization is enforced for that specific request based on data in the SSG, GSSG, or a combination of the two. Alternately, in establishing a SSN connection, the requestor and service provider authenticate and authorize each other as part of a mutual SSL negotiation. The service is then executed.

In one embodiment, authorization is determined by first determining that a requestor is listed in a global access control list (ACL) and then determining that the requestor is listed in a local ACL, which may only further restrict the global access listing. Information is shared in real time, single transmission, bulk file or batch data transfer and may include verification, identity authentication, image exchange, network based image archiving. Network participants may typically include corporations, government entities, healthcare providers, manufacturers, retailers, utilities and their respective customers or clients.

For example, a financial services embodiment is depicted in Figure 1A wherein participants in an SSN include banks 4 and 7, clearing house 5, merchants 6, archive 1 and information exchange 2 and service provider 3. Figure 1B depicts a secure service network stack and messaging architecture employing a standard web services protocol stack based on XML messages using SOAP over an HTTP transport. The services infrastructure includes message protocol stack, message specification, content, processing model, routing, exception handling, and integrated security and management functions providing management for XML, SOAP, HTTP/S, and TCP/IP. Figure 1C depicts responsibilities of the secure service gateway which is logically portioned into subsystems: management services, logging (transaction event), security (authentication, encryption, authorization), request processor, service invoker, service implementation, resource adapter, and data access.

In Figure 2 an instance of SSN or a domain on a global SSN ₁ IP connection 200, is used in an example where an institution's internal functions and data 210 are linked by the SSN to outside markets 220 as services and service domains through SSGs 10. Inside the bank nodes 210 include branch, call center, ATM, web bank, and treasury services, providing one or more of check verification, account verification, identity verification, loan services, sufficient funds, cash services, remote check capture, net settlement, ACH, wire, and guarantee funds. A SSN secure service gateway SSG 10 allows an institution to generate revenue from these assets by exposing existing and new business functions as pay for services to outside consumers 220, such as bank to bank, bank to corporate customer, bank to retail customer, bank to small business, bank to government, bank to others, etc. Secure, scalable, reliable and flexible digital information exchanges are created for markets

such as corporations, correspondent banks, small business, net settlement, large banks, small banks, the Federal Reserve, etc.

More particularly, in the general embodiment shown in Figure 3, SSGs 300a, 300b, 300c ... 30On comprise a security proxy 360a, 360b, 360c ... 36On and a services interface 350a, 350b, 350c ... 35On allowing authentication and/or encryption providing authorization to services 370a, 370b, 370c ... 37On. A log of all activities for a given SSG between service providers and service requestors is maintained at each SSG. A participant on the SSN 330 may be a requestor, a service provider, or both through their SSG. Each SSG provides a request processor, a service invoker, a service implementation, a resource adapter, a data access layer and a security layer as functional elements. A message processed in the SSG includes at least (1) a unique name identifier assigned by a SSN to the services interface, (2) a request universal identifier that uniquely identifies a request from the SSG, and (3) a unique identifier for the participant originating the request. A policy between a requesting participant and a participant providing information may optionally determine a requesting participant's access to the provider's SSG and resulting service and data.

In a financial systems embodiment, services such as check verification, account verification, identity verification, loan services, sufficient funds, cash services, remote check capture, net settlement, ACH, wire, and funds guarantee services are securely provided. A service on the SSN (1) confirms in real time, the existence of an account the instrument is drawn upon; (2) determines account status and owner; and (3) optionally, on one side, authorizes the transfer of the amount of the instrument for a subset of participants; and, (4) transfers and archives one or more image for clearing and settlement, thus achieving payment.

The global secure service gateway (GSSG) 380 interconnected in the SSN 300 of Figure 3 includes, in addition to a global service proxy, (1) a directory of services available on the network, (2) a system-of-record to create and store information regarding participant connectivity; (3) a compilation of service statistics; (4) means for payment and verification; (5) means for document and or image exchange; (6) means for identity authentication; (7) a transaction audit and logging function; and (8) an activity billing function linked to the network. Within the SSN 330, a service domain may comprise an infinite set of services and participants providing information securely over an IP infrastructure to participants having a defined one to one, one to

many, or many to many relationship. Administration and/or support functions, such as audit, record tracking and reporting, are part of the services infrastructure layer implemented by the SSG of a participant and one or more GSSGs in real time or for a given period of time.

As shown in Figure 3, a SSN 330 includes SSGs 300a ... 30On at each participant's interface with the SSN and a GSSG 380, one or more service domains each with one or more services 370a ... 37On, coupled with security, administration and support functions to provide information sharing, including information owned, information used, and information delivered. The characteristics of information shared in the system is not limited and may be transferred in real time as a single transmission, in a bulk file transfer, or batch data transfer. In brief, the SSN is a network comprising two or more participants with one of the participants offering at least one service. Participants communicate with other participants, such as a group of participants communicating with a set of service providers and or requestors. Connectivity to the network of the architecture is established via the SSG located at each participant.

Ellipses 410a ... 41On in Figure 4, represent parties, such as one or more participants providing a service ("provider") 420a ... 42On that have a shared trust relationship with a participant requesting a service 430 ("requestor") that participates in the network. Multiple requestors such as 430 may be participants in the network. A requestor 430 may also be a provider such as 420a ... 42On and vice versa. A provider 420 offers a service that is a business function to one or more requestors 430. As depicted by security umbrella 410, requestors must be explicitly authorized to access services; authorization can be managed locally and or centrally. The business function remains invisible to all other participants except to those that are authenticated and authorized to use the provider's service in the network. A participant optionally publishes the participant's public services offered in the domain of participants. A participant optionally publishes services specific to one or more requestors and/or domains. The participant restricts requestor access to services based upon a relationship, such as the security umbrella 410a ... 41On between the participant and the requestor in the domain. As shown in Figure 4, any participant service provider 420a ... 42On creates a secured unique relationship 410a ... 41On

with one or more requestor 430. Participant service provider 420a is unaware of other providers 42On unless agreed to by the relationship it has with requestor 430.

In the example of Figure 4, requestor A 430 can have a unique relationship with services provider A 420a and also have a unique relationship with service provider B 42On. Neither service provider is aware of the other unless agreed to by the relationship they have with the requestor; any service provider can have a unique relationship with one or more requestors, allowing services to be flexible, protecting unique relationships and cost models. For example, to service requestor A, service provider A may provide compartmented information, operational alerts and real time data feeds. Service provider B may, for example, provide terrorist list verification, social security number verification, OFAC list, alerts, and other services. Sample requestors and providers in a government application include the FBI, local governments, Department of Homeland Security, DOE, NAS, INS, state authorities, and the like.

In a general outline, SSN functions include service creation and domain administration through WDSL and objects, the distribution of WSDL and a family of infrastructure services, maintenance of a master ACL and ACL distribution, records of service runtime and domain administration, PKI certificate management, mutual SSL certificate authentication between requestor and provider, a certificate revocation list service (CRL), message validation, XML schema support, administration of master and local ACL roles and privileges, and JCA based system-of-record integration.

SSN administration includes (1) service level reporting: administration services for local and global reporting, SLA enforcement, usage and billing functions, dispute resolution, real time status, utilization, and planning; (2) performance monitoring such as end to end audit, Hop level data for each major component, SNMP integration, JMX, proxy IDs to legacy systems for audit; and (3) security reporting and administration, including security proxy log roll up, certificate authority and key generation and distribution, certificate revocation list service (CRL). In the SSN administration, activity by gateway and domain includes service implementation, security proxy, management of all requests and responses, and ACL enforcement and response time by component. Global activity includes roll up of activity from each SSG and GSSG, and end to end reporting and billing.

The SSN GSSG administration includes discovery service participant enrollment and look-up, management of system-of-record connectivity and service statistics such as payment item verification, document/image exchange and identity authentication, transaction audit logging and activity billing.

SSN network security is provided by encryption and includes (1) network access and user authentication by mutual authentication, PKI infrastructure, and private key distribution; (2) service access authorization involving local and/or central ACL enforcement; (The data owner maintains complete control over access.) and (3) certificate revocation (CRL). The SSN also provides a pluggable framework to support XML certificates, DES, etc.

In one embodiment, adding a service through SSN governance, the parties agree on a standardized message. The message is defined by XML schema; WSDL is used to define the SOAP object to be exchanged; WSDL schema is distributed to the participants. Additionally, a JAVA object to be deployed in the reference platform is distributed. In the WSDL, authorization ACL information is distributed; the participant is responsible for approving who can access what service; the participant then loads the approved ACL in the security proxy. Management of the security proxy may be outsourced and/or performed remotely, consistent with requirements of a particular SSN implementation.

In the SSN shown in Figure 5, the SSN leverages additional security provided at the network IP level by devices, such as routers 51 , switches 52 and firewalls 53 (as shown by the legend accompanying the drawing) and other VPN devices, including combinations of hardware and software. The present invention centralizes the administration of various security devices and integrates policies across a network. The invention comprises role based security and control in a shared multi function services network. Role-based security enforces authentication and authorization filters based on a participant's role, activity, and function in the SSN. The network includes one or more interconnected SSGs in the SSN. The SSGs, or integration nodes, comprise a security layer and a service interface at each network connection point. In Figure 5, each SSG 555 is further connected to the participant's system of record (SOR) 510, 512 and 514.

The SSG connects each participant to the network via an SSG that is logically partitioned into subsystems or layers. The subsystems comprise links, where the

SSG infrastructure creates a log of each event and management services for all actions interacting with an SSG. This includes the SSG side as well as the integration side of the SSG into a participant's private network. The layers comprise security, request processor, service invoker, service implementation, resource adapter, data access, and HTTP/SSL proxy.

Security at the SSG includes authentication, encryption and/or authorization. In one embodiment, ACL security is provided through one or more of Lightweight Directory Access Protocol (LDAP) over a SSL, SOAP using Hypertext Transfer Protocol (HTTP) exchanged over an SSL encrypted and mutually authenticated session (HTTPS), SOAP over HTTP, Java Remote Method Invocation (RMI), Internet Inter-ORB Protocol (HOP), Java Database Connectivity (JDBC), and the like. The security layer performs an authorization look up in a directory before a participant is allowed access to the network and further access through a second participant's internal firewall to a second participant's SSG. The security infrastructure supports ID and directory management through PKI, digital certificates, and ACLs using Open DAP, LDAP and/or SSL and Open SSL.

The request processor of the SSG authenticates the connecting participant and verifies that the participant is authorized to perform the given request. If verification succeeds, then the request processor locates a service associated with the specified URL, and allows the participant access to that service. The service invoker of the SSG leverages defined classes of participant authorization and access so that requestor access to data filtering is controlled. Hierarchal classes are configured to determine the processing chain. The resource adapter connects each node to the participant side of a network. The data access component of the SSG provides access to databases in the network upon authorization.

The service implementation function of the SSG handles events from the participant's offered service while tracing support functions. A provider can establish a shared trust relationship with a requestor of the provider in the network. Requestors may also be providers and vice versa. The provider offers information or provides a transactional or business function to one or more requestor; requestors must be explicitly authorized to access services. The invention supports multiple governance models for secure communication and administration. The information or transactional or business function remains invisible except to those requestors that

are authenticated and authorized to use the service in a domain on the SSN. The security portion of the SSGs and GSSGs establish a common infrastructure for security that is completely transparent to a service implementation on the network. This approach allows for consistent security while allowing the end participant to maintain complete control over the creation, definition, and secure distribution of a service to any and all participants. In Figure 3, the network includes one or more GSSGs 380 connected to one or more SSGs 300a ... 30On. The GSSG 380 provides effective network management for the participants by prioritizing functional applications and creates a secure legacy integration layer for legacy data. The GSSG comprises service creation, service runtime, message validation, and a Java Connector Architecture (JCA) based system-of-record interface. These functions include: (1) a directory of services to retrieve network service-related resource descriptions and to enroll participants and perform look-ups; (2) a system-of-record to create and store information regarding connectivity; (3) the compilation of service statistics, such as service status/notification, confirmation and completion statistics, trouble status notification, closure statistics and complaint status; (4) means for payment and verification; (5) means for document and/or image exchange; (6) means for identity authentication; (7) a transaction audit logging function; and (8) an activity billing function.

The SSN is a peer to peer secure service infrastructure that through implementation and administrative process supports a wide range of governance models. Examples include a strong central governance model as well as a distributed model, or a mix of both. This allows the benefits of full peer to peer network operation without relinquishing individual security control to a central governance authority and is accomplished via the unique SSN design and the fact that all services are layered on top of a distinct security infrastructure for service implementation. Security is thus part of the base infrastructure and therefore may be stated to be part of the network. The SSN (1) provides a common and consistent implementation that can be monitored and managed both centrally and locally; (2) supports an enterprise security framework without the requirement for the end user to proxy security for their data to some third party; (3) supports additional security at the service implementation layer if necessary; (4) removes the need for security in the application or service layer, reducing chances for error in development; and (5) provides a common

implementation and enforcement that supports local as well as enterprise reporting and administration. Security is not required or unique to each service definition; security is incorporated in the overall service infrastructure and therefore becomes part of the network definition for all services instead of a individual service by individual service function.

Three of the many governance and administration models that the SSN can support are described below. The ability to support a wide range of governance and administration models by configurations and permutations of security characteristics in the SSG and GSSG is achieved.

EXAMPLE I

Hybrid governance: Local service and data access control with global enforcement is shown in Figure 7A. Participant nodes including service providers A 70 and service provider B 71 , with service modules 700a and 700b, respectively connected through security proxy 710a and security proxy 710ba are under the control of the local node and user. At the GSSG level 75, correspondent security proxies 720a and 720b, and GSSG 380 including security module 730, with services utilities, master ACL and certificate infrastructure 740 are under central control and enforcement. This arrangement gives absolute local data access control to the service provider participant A 70 and service provider participant B 71 (Ae. local ACL management and enforcement) independent of the central body. In the bold connections shown at 190 between 710a and 720a, between 710b and 720b, between 720a and 720b, between 720a and 730, and between 720b and 730, secure virtual service network connections are established on a peer to peer basis. Clear channel or open connections are shown by the dashed lines 191 between 700a and 710a and between 700b and 710b. New services and domains can not be added without central provisioning. This ensures consistency and adherence to a loose overall governance model. To enforce this, there is a central check for authorization with an option local check. The local check assures that the central authority has not provided access to services that the local service provider does not also agree can be accessed by a specific user or user domain. This means that a check of local ACL and central ACL must be validated for a service to be used. This hybrid approach results in significant flexibility at the local level while enforcing standard implementation patterns and compliance with the infrastructure at the global level.

EXAMPLE Il

Strong local or distributed governance with central fail safe enforcement and local data access control with total local ACL enforcement is shown in Figure 7B. Provider A 70 and provider B 71 are under local control. In this model, there is no central ACL enforcement; authorization is completely managed by the end participant. However, prior to authorization there must be mutual authentication which is controlled by the GSSG via certificate management. As such global control can still be enforced through certificate privileges and certificate revocation as well as domain definitions. As in Example I, A and B functions, services implementation, 700a and 700b, and security proxy local ACL control, 720a and 720b, are under the control of the local node and security proxy central ACL control 730 and GSSG 740 are under central control by GSSG 380; however, there is no corresponding proxy for A and B at the GSSG level 75. Secure 190 and clear channel 191 interconnections are shown by the respective lines. As a result, local users can publish services to the network without being provisioned in the central ACL assuming the domain exists. Domain enforcement and authentication are still managed centrally; thus, rouge users can be disabled if abuse is observed.

EXAMPLE III

Strong central governance and enforcement with central service access control with global enforcement is shown in Figure 7C. A 70 and B 71 services implementation, 700a and 700b, are under the control of the local node and user; security proxy 730 and central ACL control and other services 740 at level 75 are maintained at GSSG 380. Security proxy 730 and GSSG 740 are under central control. Secure 190 and clear channel 191 interconnections are shown by the respective lines. This embodiment provides little or no control to the end user except for the ability to create a new service and request provisioning from a central authority and assumes that authentication and authorization are managed and enforced centrally. Local security proxies are under central management and control. Local users can submit service and domains to a central authority for provisioning on the network.

The GSSG includes security proxy service, and infrastructure functions and performs management and operations of the network such as the deployment service, support and billing. GSSG management features comprise participant enrollment and

look-up, system-of-record connectivity, service statistics, transaction audit logging, activity billing, payment item verification, and document and image exchange. GSSG administration comprises service level reporting performance monitoring, open source based operating architecture, Java Management Extensions (JMX), Java management, and audit / logging management, n an embodiment, the GSSG performs an end to end audit comprising Hop level data for each major component, simple network management protocol (SNMP) for the integration of the exchange of information, Java management extensions (JMX), and proxy IDs to legacy systems for auditing, logging, tracing, and tracking.

The present invention creates any number of participant service domains. In an embodiment, the network comprises multiple private service domains which allow a participant to supply unique services to specified markets, customers, suppliers, and classes or groups of participants. The architecture implements an infinite set of service domains securely over any IP infrastructure while providing diversified uses across a multitude of industries. The service domains support unique private relationships to include one to one, one to many, and many to many between and among participants. Relationships can be business to business, business to consumer, and consumer to consumer. Participants are aware only of participants in a specific service domain to which they are a member. Non-domain members cannot see other domains or domain traffic. End points can only see and interact with participants in a defined domain.

A service domain comprises one or multiple services. The SSN comprises means to add a service. In one embodiment of SSN governance, the parties connected in the network agree on a standardized message. The message is defined by XML schema. WSDL is used to define the SOAP object to be exchanged. WSDL and the schema are distributed to the participants. A Java object to be deployed in the SSG is distributed with the WSDL and schema.

In the example shown in Figure 3, participants are linked to the SSN network 330 through SSGs 300a, 300b, 300c ... 30On as nodes 30, 31 , 31, 33 ... in the network. The number of nodes connected to a network is not limited. Each SSG may optionally be linked to other networks either within or without the system. Each node optionally can support one or more sub nodes such as 310 established on an intranet or other private network. Internal sub nodes or subnets, such as those related to

human resources, legal, accounting, finance and the like, may similarly require security adapted to subnet functionality. Participants may be service providers and/or service consumers, and may act both as participants on the network and members of one or more service domains. The participants may be similar or mixed markets and use the same or different applications all acting privately and securely on a common IP network infrastructure. A participant using the system may not necessarily be a human, since automated procedures and processing may be adapted in embodiments.

The architecture creates and protects IP packets in the network by defining a method of specifying the traffic to be protected, how that traffic is protected, and to whom the traffic is sent. Services messages are defined using WSDL. Message content typing is specified in an external XML schema definition with its own namespace. The schema definition is imported into the WSDL service definition. Message content is literal XML. XML content is schema based and therefore adaptable to many dialects. The service implementation supports the concepts of self describing interfaces where the SSG can be interrogated by a machine and acted upon easily without human intervention. Services optionally include one or more attachments in a manner consistent with World Wide Web Consortium's SOAP Messages with Attachments (SwA) specification. Such a practice allows compliance with the Web Services Interoperability Organization's basic profile recommendations.

All request and response messages contain at least three identifiers: (1) the unique name identifier assigned by the SSN to the SSG, such as created by the program DIGI-FI™, a product of Synoran LLC, Columbus, Ohio; (2) a request universal identifier (RqUID) that uniquely identifies a request from a SSG; and (3) a point of origination universal identifier (PoUID) that represents a unique identifier for the originator of the request within a participant's internal network domain that is attached to a SSG which is attached to a domain on a SSN. When these three identifiers are contained in a message, they uniquely identify a request and response pair in the network. The existence of this information is also used for reporting, administration, security, billing, audit, attack tracking, failed attempts and the like across the entire SSN. Information logged and reported from each SSG can be rolled up and reported on at the GSSG. This allows for a global view of activities while maintaining privacy for all participants.

The services infrastructure comprises a message protocol stack, a message specification, content, a processing model, means for routing and exception handling, and at least one integrated security and management function. The protocol stack comprises messaging architecture employing a standard web services implementation. Messaging architecture employs a standard web services protocol stack based on XML messages in SOAP over an HTTP transport. Each participant's family of services is defined and created using WDSL and objects. In one embodiment authorization is left to each participant where the participant is a service provider on the SSN. In this case, the participant is responsible for approving who can access their individual services. This allows for each participant individually to control access to services without requiring a rigid service definition and implementation process that has to be agreed to by all participants. The embodiment allows each participant to create, develop and deploy a service independent of other participants on the network. In addition, each service provider is allowed to define domains and participant access to services the provider offers. Each participant then loads the approved ACL in its SSG; management of the SSG can be controlled in- house or outsourced.

In one implementation, sessions during information sharing are managed with PKI certificates where a mutual SSL authentication is accomplished between a requestor and a participant service provider. The architecture provides for revocation of certificates through a CRL implementation. Hierarchical certificate management and ACL management is supported to allow flexible service and domain definitions on the same network. Thus, the invention provides true multi function services on a common network infrastructure. There may be multiple domains, services and participants all on the same IP backbone. Messages are validated using XML schema support. In one implementation, master and/or local ACLs define participant's roles and or privileges. Enforcement can be based on the local, the master or a mix of ACL validation. Validation is accomplished via a confirmation that a given service requestor is allowed to access that service via defined privileges in one or more ACLs. The invention provides the ability to provide local ACL enforcement and control without introducing security risks to the other participants on the network.

The SSG and GSSG provide an integration layer to allow rapid integration to new or existing systems. This includes integration via common standards like JCA,

Java Message Service (JMS), MQ, External Call Interface (ECI), Remote Method Invocation (RMI), JDBC, application program interface (API) and the like. Sample services include, but are not limited to: verification, identity authentication, image exchange, network based image archiving and retrieval, and remote image capture. Verification allows validation of information in real time, information and image processing, and insures reduced telecommunication costs, image compliance and quality assurance. The network provides for the exchanges of multiple types of images, which streamlines many processes.

To meet the need for privacy, the architecture supports literal data exchange as well as interpreted data exchange. For example, a check verification service may include a detailed look up of the account, the account owner, available funds, etc. However, due to privacy needs, the reply on the network may or may not include this detail. The reply may provide only a yes or no, a score, a level of confidence, etc. The architecture described herein thus protects the privacy of the account owner and meets the needs of privacy laws in some industries, but still conveys the critical information needed for the requestor to make a decision. In addition, a service can be defined for a given set of activities and the interpretation of that service can be specific to the requestor and/or provider or the unique relationship of the participants.

Data and processing flow can be context specific where context definition is beyond the data in the message. It can be done in terms of the relationship between the provider and requestor and can be structured to fit the relationship to a domain and a given role in a domain or set of domains. The ability to define a service that is exposed to a community of users in the SSN that can be acted on differently from both a data and processing flow perspective is unique to the architecture. For example, a request from requestor A (a Bank) for a service provided by provider B may be interpreted differently in terms of data to provide a processing flow that differs from the same service request from requestor C (for example, a different bank or a car dealer) to provider B. This feature allows a service interpretation for a given request to be context specific where context requires more than the data in the request.

The invention can be dependent on a relationship defined in at least two dimensions by using the domain option as well as the role option in the security layer of the SSN. This allows the processing chain on the service provider side to be flexible and requestor specific in responding to a request. It also allows the service

fulfillment to be specific to the risk or cost associated with a specific service activity by leveraging other statistical data that allows for further interpretation of the data in the service or the relationship defined by the implementation and fulfillment of a service from a specific requestor.

Identity authentication contributes value in a wide range of environments by establishing a participant's identity on the SSN and a service on the SSN where a requestor can request an identity service. A service request can be made to confirm an identity based on data available to a community of participants on an SSN. This allows a participant to validate an identity based on data available from all service providers on an SSN or in a given SSN domain. An example could include verification of customer information against information on file at a customer's bank, the federal government, a state's bureau of motor vehicles, court records, etc. Once a participant or individual is authenticated, a rule can be enforced for that participant. This rule involves authorizing rights and privileges for a given request -- typically involving limiting access to secure areas and or private information based on the rights of each participant in the network. Authenticating a participant's identity ensures qualification for access to a service and ensures a participant's privacy. A participant using the system for identity management authenticates the information in real time from one or many locations on the network that contain identity information. The architecture optionally creates new repositories for identity verification. Under the authentication function of the present invention, an XML record is utilized; the XML record is sufficiently flexible to handle a variety of network based identity solutions, including driver's license information, biometric capture, and data sharing. Upon connecting to the invention, a participant configures policies. Each participant in an SSN has a defined relationship with the SSN that can be unique to a domain, groups of domains, individual services, or groups of services.

Service domains are partitioned into domain hierarchies with inherited trust relationships. Domain partitioning is flexible. In one embodiment, trust relationships are determined via a hierarchy of certificate authorities (CA). To establish trust relationships, the network first creates a trusted root CA. Trust relationships in domains are determined by partitioning and using intermediate CAs, each of which is signed by the designated root CA. Each participant's digital certificate originating from its domain is signed by the intermediate CA. Access control is enforced via a

hierarchy of service ACLs. Domain participants must be trusted with signed CAs to gain access to information in the SSN. All requestors must be authorized by the ACL, which may be applied to multiple services and multiple providers. Example IV describes the interactions of participants and service domains.

EXAMPLE IV

As shown in Figure 6, in domain 610, provider 650 has a trusted relationship and offers one or more service to requestor 640 and requestor 670. In domain 630, provider 660 has a trusted relationship with and offers one or more service to requestor 670. In domain 620, provider 650 has a trusted relationship with and offers one or more service to requestor 660, which may be a different or the same service(s) offered to requestor 640 or requestor 670. Trust relationships among the participants are determined via a hierarchy of CAs. A root CA is created that signs all participant's certificates. In this example, an intermediate CA is created for domain 610, which is signed by the root CA. Domain 610 intermediate CA signs CAs for participants 640, 650, and 670. The trusted relationship between provider 650 and requestor 640 and requestor 670 is established via the participant domain 610 and intermediate root CAs. Similarly, the intermediate CA for domain 630 is signed by the root CA for that domain. Domain 630 intermediate CA signs CAs for participants 670 and 660. The trust relationship between provider 660 and requestor 670 for one or more service is established via the participant domain 630 intermediate and root CAs for that domain.

In domain 620, a domain 620 intermediate CA, signed by root CA signs CAs for participants 650 and 660. The trusted relationship between provider 650 and requestor 660 for one or more service, which may differ from service(s) offered to requestor 640 and or requestor 670, is established via the participants, domain 620, and intermediate and root CAs for that domain. Access among the participants is determined by ACLs. The root CA signs all participants' certificates.

In domain 610, provider 650 determines the authenticity of a requestor 640 or 670 by comparing the requestor to an ACL for the service for which provider 650 and requestor 640 and requestor 670 have a relationship. In this example, requestor 640 and requestor 670 are listed on the ACL for the service requested.

In domain 630, provider 660 determines the authenticity of a requestor by comparing the requestor to an ACL for a particular service. Requestor 670 is listed on the ACL for a particular service, while participant 640 is not. In domain 620, provider

650 determines the authenticity of a requestor by comparing the requestor to an ACL for a service different from the service offered to requestor 670; requestor 660 is listed on the ACL for the different service; participant 670 is not.

The SSN provides flexibility by combining trust and access control and uses trust relationships for high level domain partitioning and access control for low level partitioning. Access is managed in the invention through a combination of global and local controls. This provides the benefits of peer to peer network solutions without compromising security and governance. Global access is defined through business relationships and determined via service ACLs. With reference to the SSN shown in Figure 3, global or central ACLs are stored in the GSSG 380 managed by the system. Local access is defined by providers in each business relationship and determined via service ACLs stored in each participant's SSG 300a ... 30On in security modules 360a ... 36On and managed locally and/or centrally depending on the desired governance model. Authorization is global, then local or any combination of the two. Requestors must be listed in the global ACL maintained in the GSSG 380 and the local ACLs maintained in SSGs 300a ... 30On shown in modules 360a ... 36On, to gain access to a provider's services 370a ... 37On through interfaces 350a ... 35On. A local ACL may optionally further restrict a global access listing in the GSSG and as a result provide the local service provider with absolute control of access to its services and data.

The invention is useful for multiple markets for applications, such as financial services, government, including homeland defense, national security, military theater, healthcare, manufacturing, retail, multiple B-to-B and B-to-C communities, business firms, large corporations with complex corporate structures, small businesses, suppliers, consumers, and the like. In an embodiment, the invention can be implemented for a single end user as a self-contained appliance such as a modem like interface to a network connection. Typically, the participant is a supplier selling services on a network based on an IP infrastructure. With the growing concerns about security and identity fraud, a SSN can be implemented at the single computer user for secure exchange of information on a one to one, one to many, or many to many basis.

The supplier optionally provides organizational management to deliver sales, deployment and operational support. The supplier is optionally a commodity information or financial services supplier. In an embodiment, a supplier uses the architecture to implement SSNs in specified industries. The supplier's service

optionally generates click revenue where end users pay by the use of each service. The service drives demand for the commodity and in turn increases volume and revenue for the supplier. Alternately, a supplier may generate revenue based on consumption, through a base fee plus a consumption charge, a flat fee, an in-kind service exchange, and the like.

The ability to allow participants to define, build and deploy services in a secure manner but with complete freedom of business functionality is a benefit of the SSN, allowing a participant to easily introduce new services and user communities to support a rapid low cost expansion of business relationships. Service requestors can gain access to data on a use basis without the need for a large up front cost or investment. As such, the SSN enables a unique business model that has the flexibility of the Internet without specific drawbacks of prior art security and reliability deficiencies.

In a financial services embodiment depicted in Figure 1A and Figure 2, participants include all types of financial institutions, merchants, consumers, compliance entities, and the like. Figure 1A depicts the exchange of sensitive financial information in an SSN through intermediate SSGs 10 at each participant. Information is exchanged between nodes connected to the SSN, such as service providers shown as image archive 1 , information exchange 2 and others 3, individual banks 4 and 7, clearing house 5, and merchant 6. "Bank" as used herein includes all types of financial institutions and financial service, payment providers; generally, any firm or institution initiating or participating in a financial transaction or payment process. Interactions include bank to bank; bank to a corporate customer; bank to a retail customer; bank to a small business; bank to a governmental entity; bank to others; and the like. Information shared may include check image, image replacement documents (IRDs) and MICR data in batch or real time mode.

In Figure 2, an SSN or a domain on a global SSN 200 is used for financial services where an institution's inside functions 210 and operations divisions 211 are linked to outside markets 220 by being exposed as services and service domains within SSN. As shown in Figure 2, outside market participants 220 include corporations, correspondent banks, small business, net settlement providers, large banks, small banks, and government entities, such as the Federal Reserve, the FBI, etc. To access services, the service provider must enable access by requestor or

requestor domain. This allows the requestor to gain access to new data sources with very little investment or no up front cost and it allows a service provider to expose new services that are unique differentiators in the market. Such services can be exposed and billed on an as used basis through reporting and administration available at the SSG and GSSG.

The SSG exposes the pre-existing business functions, for example, as shown in 210, of a participant as "pay for" services to outside consumers in categories, for example, identified at 220. Inside business functions of a participant, such as the bank depicted in Figure 2, include but are not limited to check verification, account verification, identity verification, loan services, sufficient funds, cash services, remote check capture, net settlement, ACH, wire, and guarantee funds. As mentioned previously, a service does not have to return literal data for each request; an interpretation or variation of that data will protect customer privacy. In addition, the processing chain on the service provider side can be varied for the same service without changing the service from the perspective of the requestor. This provides a flexibility to support various billing and servicing models. An example may be a check verification service where a request is made to verify a check; the service provider may execute a different processing chain internally depending on the requestor and the amount of the check. In this fashion, the service provider has the ability to link the amount of processing determined, for example, by expense or level of effort that the provider is willing to incur with the risk or value of the transaction. This is unique to the invention in the context of a SSN.

As an example, a low value check may require data only concerning the length of time the customer has been with the bank and data that the account is in good standing. One the other hand, for a high value check, the service provider may additionally verify that there are sufficient funds in the account to cover the check. Optionally, the service provider could even hold those funds. The ability to do this without changing the service implementation from the requestor's perspective is a powerful and unique function achieved by the SSN. Cost and value of a service provided may be individually tailored to risk tolerance.

Figure 5 depicts a SSN financial services domain implementation. Participants, Bank A 501 and Bank B 502 and net settlement service provider 503, and a GSSG 555 provided with security proxy 506 and service interface 507 with management

W services module 508 are connected in an SSN domain by SSGs 555 form the SSN. A SSG may optionally have a sub net such as with bank branches 520 which may optionally be accessed by a payment teller 521 or accessory 522, as depicted for Bank A in Figure 5. The sub net may be an intranet or a single source. Each participant is protected by a firewall in the connection in addition to the security layer provided by SSN. Each SSG, intermediate the participant in the SSN, comprises a security proxy and a service interface at each network connection point. Each SSG in the SSN domain is further connected to the participant's system of record: for Bank A, payment enterprise server 510; for Bank B, system of record server 512, and for net settlement provider, net settlement server 514.

Bank A and Bank B securely share information which may optionally be obtained through sub-nodes to (1 ) verify an account, the identity of the check writer, and whether the account contains sufficient funds through payment teller; and (2) perform loan services, cash service; remote financial instrument capture, and the like. The net settlement provider depicted in Figure 5 may be broadly defined as a treasury service. Bank A 500a and Bank B 500b interact with the treasury service from to effect electronic funds transfer, such as net settlement, payment and clearing, ACH transfers, wire transfers, and funds guarantee. ACH transfers may include direct deposit of payroll, social security, government benefits, tax refunds, direct payment of consumer bills such as mortgages, loans, utility bills, insurance premiums, business- to-business payments, e-checks, e-commerce payments, federal, state and local tax payments, and the like.

Using suitable variations of the bilateral trusted relationship security options, banks may verify financial instruments and a customer's identity, guarantee payments, and participate in Check 21 , a law that facilitates check truncation by creating a secure substitute negotiable instrument, (IRD), thereby permitting banks to truncate original checks and process check information electronically. A participant using the system to verify a negotiable instrument, such as a check, (1) confirms, in real time, the existence of an account the instrument is drawn upon; (2) determines account owner and status; (3) optionally authorizes the transfer of the amount of the instrument for a subset of participants, such as "on-we" processing where banks mutually agreed to truncate financial instruments at the collecting bank. A participant

using the system for Check 21 processing, transfers images of the financial instrument for clearing and settlement.

Check fraud should be reduced by eliminating the time lag between check presentment, clearing and settlement. Thus, SSN services of the invention provide a unique and flexible mechanism to support straight through processing in financial services, providing significant business value to corporate customers by allowing a financial institution to offer services for remote check capture with real or near real time settlement and clearing. SSN provides the financial institution a low cost flexible, private, and secure mechanism to deliver this functionality to a wide range of customers. Traditional approaches of the prior art, in contrast, require a check specific network or a point to point dedicated network. SSN provides a peer to peer SSN that can perform a wide variety of functions that are exposed as services on the network.

Services in a financial embodiment include verification, identity authentication, truncated check image exchange, network based image archiving, and the like. Transaction verification allows validation of transaction information in real-time, such as (1) the ability to link demand deposit account (DDA) account information to teller and retail environments, (2) the ability to present commercial paper at tellers and retail points of presentment, and (3) the ability to streamline merchant / teller participation. In the financial embodiment, the SSN provides for the exchanges of multiple types of images, streamlining merchant participation in the truncation process; authentication prevents fraudulent payment transactions and identity theft while limiting access to secure areas and or private information.

In an embodiment where the participant is a governmental entity, the architecture is useful for: (1) compliance with national security specifications for homeland security, such as support for Regional Alliances for Infrastructure and Network Security (RAINS) and the Open Specification for Information Sharing (OSIS) as well as other emerging specifications through a family of secure web services that are easily integrated into existing legacy systems; (2) military uses, such as command and control and intelligence gathering, assessment, and dissemination; (3) sensitive compartmented information sharing and exchanges, such as intelligence and special operations; (4) local and regional government information uploads and sharing,

including law enforcement and the Department of Homeland Security; and other government information and services.

Healthcare uses include: (1) patient safety, optionally adapted to biometrics, including patient verification and procedure and process verification; (2) device monitoring and remote monitoring; (3) substantiation of a controlled substance supply chain; (4) billing, payment, settlement, clearing, and facilitating insurance claims and payments; (5) access to patient records; (6) remote healthcare; and (7) image exchange.

Insurance industry uses may include: (1) claims reporting and updating, for use by customers, contractors, underwriters, etc.; (2) billing, payment, settlement and clearing; and (3) compliance issues.

In retail applications, the architecture is useful for: (1) point of presentment capture and end to end electronic check processing; (2) acquirer services, including providing a single source solution for delivering merchant credit and debit card services such as a comprehensive authorization network for credit cards, debit cards and checks; (3) electronic data capture incorporating the capabilities of the retailer's authorization architecture combined with software, to enable an entire transmission to be electronically captured and value-added information to be transmitted; (4) Internet payment and processing services; (5) an accounting system to allow the retailer to record activities; (6) exception processing, including sales draft retrieval and charge back resolution; (7) fraud monitoring; (8) customized value added applications for retailers such as restaurants, lodging and direct marketers; and (9) identity verification.

Utilities, such as electricity, telephone, natural gas, and cable providers may use the architecture, inter alia, for: (1) local and regional information sharing between and among distribution facilities, generation facilities, suppliers, trading partners, consumers, and government regulators; (2) security; and (3) compliance.

Thus, the present invention optimally provides a secure transaction network for a defined space, such as a metropolitan area using a layered mechanism over existing infrastructure. In a metropolitan financial network, the SSN can provide transaction verification, identity authentication, image exchange, correspondent processing, "on-we" clearing, and settlement. An embodiment of a metropolitan transaction network comprises one or more service providers linked in an SSN to a

SSG, to a GSSG, and to one or more of the participant's customers either via the customer's SSG or SSGs at each customer site. Each connection to the network is via an SSG comprising services, administration, and security functions. The GSSG further comprises a directory of the services in the network and a total SSN roll up point for those activities that an implementer may want to manage through central governance. The customer may be a single SSG or multiple SSGs further connected in a SSN or SSN domain.

There are many implementations of the SSG, ranging from large clustered hardware environments to an individual user through software or with a similarly configured appliance like hardware device. For large high throughput applications, clustered servers are used to deliver scalability and redundancy. For the individual appliance, the user may install SSG software on an SSG device as a card in a PC or server or as an add on box similar to a personal broad band router for DSL or cable broadband connectivity. As technology matures, miniaturization to a single chip implementation may occur in hardware embodiments. The base implementation supports SSN network interface(s) as well as internal user owned network interface(s). In addition to these SSN interfaces, several out of band communications options are supported for remote administration and security management and reporting for interfaces such as USB, Firewire, Ethernet, Gigabit Ethernet, and wireless.

EXAMPLE V

SSG 10 is shown in Figure 8 interconnected with a participant's internal network 801 and business functions 810. The SSG includes the participant's interface 802, service implementation 803, and security proxy controller and SSN network interface 804. Out of band communications controller 805 for use with other options 840 and administration module for logging and reporting 806 are included in the SSG. The SSG is optionally sized to suit the network and the participant. A low cost gateway is a POS single function endpoint to transact on the SSN comprising one CPU or appliance footprint with a reference platform technology stack. A small gateway for corporate access with full functionality is, for example, a two CPU footprint. An example of a medium gateway with significant throughput and high availability / failover is a six CPU footprint. A GSSG will likely require full high availability / failover archive components and extended storage. For example, a

GSSG with large volume and high availability / failover is a 10 CPU footprint. Extended storage is required when substantial financial transaction histories and data are involved.

The architecture audits, tracks and reports, and is adaptable to private or public networks for any type of secure information exchange. The architecture comprises logging and reporting functions to support probing, authorization failures, request parameters, and the like. The reporting function includes both local and enterprise reporting; local reporting is performed at SSG; enterprise reporting occurs at any of the one or more GSSGs. Reporting supports determination of usage for billing purposes, requirements for service level agreements and governance, provides evidence in billing and dispute resolution, and the like. Reports are creatable in real time or over periods of time. Reports are useful for participant utilization and planning. The architecture provides for security reporting comprising a security log roll up, certificate of authority and key generation and distribution, and CRLs.

Participant service usage is logged and reported based on each request and service provided. SSG and GSSG administrators can view transaction histories, errors, usage and other reports regarding the status and state of the SSN. Reports provide an end to end view of all the services involved in the integration, including those behind a participant's firewall. The architecture's reporting feature allows node and GSSG administrators to view and understand errors across the entire SSN. The architecture creates logs of activities by gateway and domain, service implementation, and security layer. Logs of the system include but are not limited to all requests and responses, all ACL enforcement, response time by component, global activities, such as roll up of activity from each SSG and GSSG, end to end reporting, and billing. Other functions include quality of service (QOS) support for determining throughput based upon transmission rates, check images, real time payments, digital documents, fraud data, shared services, and the like.

The physical and logical design of the SSN, SSG and GSSG is layered to provide both flexibility and enhanced security. All major security functions are performed at the security layer; as a result, the security infrastructure is inherently part of any service implementation on the network. In so doing, one has the ability to physically isolate portions of the architecture for enhanced security. For example, the security may be located in a DMZ while the service implementation is located on the

internal trusted side of a user's internal network. Multiple security layers can be used in a chain to provide both local and central control points in the SSN implementation. Each of the layers can be physically located on one hardware platform or segmented across many. This provides for a level of fail over and isolation to enhance performance and security and supports implementation patterns ranging from a single small appliance to a large server farm. The ability to support IP based firewalls between major layers and components of the infrastructure allows for ease of integration to current networks as well as supporting additional security on top of the base service implementation security infrastructure. Components of the SSN include: 1) Secure Service Gateway (SSG). The SSG is the on ramp to the SSN and establishes the embedded security for all services running over the SSN. 2) Global Secure Service Gateway (GSSG) SSN Management Facility. The GSSG is an SSG with the systems of record, management facility, provisioning, and domain model for an overall SSN implementation. 3) The Services Repository is an element of the Management Facility. SSN Services Repository resides on the GSSG or in the SSN network and is the repository for all services created and provisioned by participants on the network. 4) The PKI Infrastructure includes the SSN Certificate Authority (CA) housed and managed by the GSSG for an instance of SSN and enforces CA Lifecycle, Access Control List (ACL) and Certificate Revoke List (CRL) management. An external CA can be substituted as needed. 5) The SSN Management Console (Domain Model) is an SSN Component residing on the GSSG that includes the overall data tier and management facility for an SSN implementation. The SSN Management Console provides the management screens for provisioning and reporting on an SSN implementation, including pricing, reporting, provisioning, and service relationships. 6) The Web Services SDK allows participants to create their own services. The SDK creates all of the component stubs including a test harness allowing the user to create and test new services as they desire. 7) Operational Reporting from an SSN implementation includes the configuration screens and reporting options as well as an operational data base. Operational Reporting also includes enterprise infrastructure services used to gather information from network participants and typically resides on the GSSG. 8) Pre-Built Services (Business, Infrastructure and Management) comprise families of pre built services for the SSN including Management Services, Infrastructure Services, and Business Services.

W

With reference to Figure 9A, a template for examples of typical tree hierarchies also illustrated in Figure 9B and Figure 9C, the y-axis column 90 arranges users in general vertical categories of company 901 , location of business 902, product 903, customer 904 and user 905. In turn, each vertical axis participant within the category is assigned narrower (or more specific) characteristics arranged in an x-axis branch (horizontal) 90, such as Bank A 907 in the company category where retail 908, commercial 909, small business 910, and operations 912 are also shown in the horizontal layer. The product hierarchy 903 includes accounts for checking 913, CDs 914, loans 915, and credit card 916. The customer hierarchy 904 includes categories of household 917, company 918 and individual 919. In the user category 905, an individual 920 is shown.

Selected secure communications within and between hierarchical participants are shown in bold lines; unselected participants are in dashed blocks. In the sublevels, access may be finely tuned to an individual or locality, or any other individual or group of participants otherwise within the hierarchy as shown by the vertical arrows through the hierarchal levels Figure 9B and Figure 9C. Although a horizontal vertical hierarchy is shown in Figure 9A, Figure 9B and Figure 9C, the representation is illustrative only, as any hierarchy or matrix of authorization and security levels may be defined in a SSN of the invention.

The SSG overall architecture supports in and out of band key distribution and management, and is adaptable to any PKI infrastructure where the ability to manage and distribute the private (secret) keys associated with the use of digital certificates is critical. Figure 10 and Figure 11 depict, in the bold connections shown at 190, the virtual secure service network connections that are established peer to peer over a physical IP infrastructure by the SSN. The secure connection is participant SSG to participant SSG independent of physical path. In almost every case, out of band distribution and management will be preferred for security reasons. Forms of distribution include: (1) distribution via secure web communication authentication and download, accomplished out of band of the SSN infrastructure by a log on to a secure web site where an additional credential is used to validate the download of a new private key; (2) via physical media; (3) telephone, cable or wireless home modem connection, authentication and download; or (4) distribution in band as part of a service on the SSN.

In an embodiment, every SSN service is first defined in standard Web Service Description Language (WSDL). SSN WSDL service definitions use XML Schema to describe message content. In general, any SSN service can be described completely by a series of XML files: (1) XML schema description of input and output messages; (2) WSDL binding describing service details; or (3) WSDL service endpoint description. The use of XML allows services to leverage a self describing data context permitting the architecture to machine interpret interfaces and services across the SSN. The security around each service is implemented in a separate layer of the SSG; however, security may be placed in a service if conditions so require.

Authorization can be managed centrally as well as locally. A local ACL can be more restrictive than the global ACL but can never enable privileges that are not in the global ACL for that requestor or service provider, unless the governance disables global ACL enforcement. This assures that all users are loosely governed by an overall governance authority but does not require that a user or data provider on the network trust the security that restricts access to their data to a third party. This unique feature, that supports loose governance, with absolute security, is an enabler unique to the SSN. Security is increased while the complexity of adding new services is reduced. Users can publish services at their discretion without the total agreement or consensus from all users or even a subset of users.

In another embodiment, authentication is managed via a secure public key infrastructure (PKI) that includes digital certificates. All users on the network have a certificate that is signed by a certificate definition in the master certificate authority. The master certificate authority includes a hierarchy that supports multiple domains for one or more signing authorities. As such, service domains can be established for any group of users deemed necessary. Only users defined as part of that service domain can connect with each other. Once connected, the combination of the mutual authentication and user roles as defined in the ACL for that requestor and provider enforce what a requestor can see and what a provider will service. For a given request, the requestor and provider must belong to a common domain as defined by a GSSG and/or SSG. To validate this bilateral association, the certificate for each participant (service requestor and service provider) must be signed by the master certificate authority for that domain. When this is true, then a mutual authenticated secure session is established.

Once the bilateral trust verification is complete, the provider authorizes against a local and/or master ACL to confirm the requestor is authorized to request that service. In one embodiment, the SSN certificate authority (CA) creates signed member certificates, and may revoke a member certificate at any time using a certificate revocation list (CRL). This functionality is managed by the GSSG and enforced at the GSSG and/or local SSG levels. Full SSL encryption is supported for all communications on the SSN. Other encryption approaches can be implemented through a plugable framework. In services requiring audit and nonrepudiation, multiple levels of logging are supported across all elements of the SSN, including all distributed SSGs and one or more GSSG.

The SSN allows a service provider to offer a service that may be comprised of data or functions from itself as well as services from other service providers with which it has a relationship. In this fashion, a service provide can provide a service offering that is an aggregation of services and/or data it has access to and/or consumes from other providers. In this manner, a service provider may become a service requestor as the result of a request it receives for a service that it provides. As a requestor it can provide access to services that the original requestor does not have access to or knowledge of. Aggregation is supported internal to one domain as well as across any domains that the service provider is a member of. As a result, a service provider can provide a broad range of services even if the provider only brokers data from other service providers. The ability to do this in a secure manner that requires no additional authentication or authorization from the original service requestor is unique to the SSN. In this manner, the SSN provides a level of transitive authentication and authorization that is not available today.

The SSN provides authentication and authorization in a manner that is anonymous to the end requestor. This allows a service provider to broker other services without revealing to the original requestor his sources or business relationships. Full audit and logging for aggregation services are provided via the PoUID that is part of the core SSN. The PoUID identifies the point of origination of the original request and can be used to tie the logs together for all resulting requests to arrive at an end to end audit for the activity.

EXAMPLE Vl

As noted, the invention integrates authentication and authorization functions in a transaction payment system across the board with a comprehensive embedded security administration function that supports multiple governance models. The architecture includes switch and verification means, users, services and multiple layers of security for allowing user sign on, encryption, authentication, authorization, activity non repudiation, SLA management, consumption based billing, session access, transaction processing of data and image files with quality comparisons and security at all levels from capture to settlement, check processing. A quality assurance algorithm may be included at every or any stage of financial transaction processing from capture through settlement, and a secure service network with unique audit and point of origin identifiers administered by service gateways across a broad community of users is independent of the physical network transport provider.

The present embodiment fills a need in providing access to funds, and the processing of purchase and payment transactions integrating a wireless network transceiver, or in an example, a personal cell phone with the above architecture and a SMFSN as an interface for wireless, mobile and secure transaction processing across any physical IP network independent of carrier transport.

In examples shown in Figure 12, Figure 13 and Figure 14, functionality in a transceiver device such as a cell phone, smart phone, or other telephone network transceiver, is provided to select, aggregate, initiate, process and effect secure transactions at a point of sale (POS) site. The transceiver is interconnected through SMFSN through SSG to a network managed by a GSSG where a community of payment services is available to the device. The transceiver is equipped with an SSG; SSGs at the user sites are also administered by the GSSG for the network in which the phone user and merchant are members. For clarity in the drawing figures, the administration interconnections between the GSSG and the user sites, e.g., point of sale terminals, ATMs, transceiver users, etc., are not always shown, but are, however, implied in the overall GSSG / SSG security protocol. Connectivity can be peer to peer or hub and spoke depending on the governance model implemented. Mutual and multi-factor authentication is provided as a default function of the network with optional PKI certificates that also support service authorization. As an example of a payment service, the user of the device is identified as an account holder having a unique identifier, numerical address, phone number or equivalent. Additional security

measures in the phone, such as a PIN, biometrics, secret phrase, digital certificate may be integrated in the system.

The invention allows the availability of a wide range of secure payment services from one or more communities of providers over any physical network infrastructure wherein a transceiver is interconnected by an individual user with a variety of service providers (funds sources) at a point of sale through a secure shared multi function service network (SSN) interconnecting the transceiver, a funds source associated with the transceiver and the point of sale, and an SSN implementation for managing the security of the interconnections between and among the transceiver, funds source and point of sale. From a user perspective, multiple transaction types over a secure multi function service network using a transceiver system are effected. A cell phone, smart phone, or other network transceiver capable of an interconnection effected by an individual user with a funds source at a point of sale initiates the transaction. A secure service network interconnects the transceiver, a funds source associated with the transceiver and the point of sale, and a global secure service gateway managing provisioning and service interconnections between and among the transceiver, funds source and point of sale.

Authentication and authorization mechanisms are provided as a function of the service network to insure secure verification within the network of the user of the transceiver as the true user of the transceiver and the true owner of the funds source. The user can enter a debit or credit with respect to the point of sale from or to the funds source over the secure network. The network includes mutual authentication and multi-factor authentication as a function of any service or application attached to and effecting a connection over the network. Biometric user identification may be incorporated. The funds source may be interconnected with a payments network to allow debit, credit, payment and settlement of funds accessed by a user from the funds source which may be a cash account or a credit account.

In the example, a signal initiated by a button, touch screen, biometric reader, or combination, activates a Virtual Service Connection (VSC). A PIN or other form of additional personal identification known only to the user may be required as a condition of log on (1) to the secure network and (2) to an interconnection over the secure network to a POS location to effect a transaction. The SSN shown in Figure 2A and Figure 2B is software (or hardware equivalent) that enables the creation of a

Secure Shared Multi Function Service Network and network community of services over any physical network infrastructure. The SSN is comprised of secure gateways (SSGs) that are the on-ramps to the SSN and a network management facility (GSSG) that enables reporting, policy, compliance, billing, and privacy management across an SSN VSC topology. The combination of functions and the GSSG and SSG allows for implementations to support multiple governance models. SSN works with web services (HTTP, SOAP, WSDL) using the WS-I specification, native HTTP applications (web browser applications), and legacy applications and protocols (through integration or tunneling). In addition, SSN supports many additional protocols focused on network convergence and multi media services. These include SIP or IAX for VOIP, UDP, and many others defined under the traditional TCP standards for protocol support above layer 2 and 3 in a traditional OSI network model. The SSN is adapted, in various configurations, to use the ubiquitous mobile cell phone to effect secure payment transactions at various points of sale. An example of a SSN implementation is illustrated in Figure 16. Members 682 and 681 , each equipped with SSGs, are interconnected in a network 690, in a connection managed by GSSG 680. GSSG 680 in turn is interconnected with network service provider 685 to administer the one to one, or one to many, or many to many, secure network connections and to provide event analysis: logging analysis, event tracing, billing analysis, and SLA analysis. Processor administration station 684 provides topology management: service repository management, network organization management, service implementation management, access control list management, end user management, security proxy management, and access control list services. Service module 683 provides PKI and Certificate of Authentication management: as a third party to mediate PKI, sign security proxy requests, revoke certificates, and provide certificate revocation lists. Secure service network member 682, through the network accesses secure service network member 681 , connecting through SSGs at both sides. An authentication service may be used on the network to facilitate a higher level of user authentication than what is provided by the base SSG or application connected to the network. In this manner, user authentication can be linked to credential repositories stored internal to a service provider on the network where access is controlled by the provider or an agent of the provider.

Member 682 provides a request for authentication, logging, and integration to enterprise systems available at member 681. In one governance model, the request is processed at GSSG 680 and the SSN components 685, 684 and 683 whereupon, upon receipt of access approval, member 681 reciprocally provides authentication service, local and/or central authorization, logging, and integration to enterprise systems allowing member 682 secure one to one access through the administered SSGs to the requested business service implementation. This may be accomplished for each and every service provider on the SSN such that a market community is available to the user of the POS and wireless device for real time payment decisions that include method selection and method validation. In the network, services provided may be singular to a provider or an aggregate combination of services by multiple providers over the SSN implementation. Elements of security necessary to effect and support a transaction or activity on the network from the transceiver are provided at a base level as a function of the network; and the base level elements of security on the network may include mutual authentication, authorization, payload encryption, transport independent encryption, privacy, end to end audit, and non- repudiation for compliance reporting.

The payload for a transaction may be encrypted independent of the transport and the payment may be specific to the participants of the transaction; data stored is encrypted at rest and accessed only by one or more of participants to the transaction. A transaction UID that is unique to each transaction effected by the network is created and managed as a function of the network. In a variation, a correlation UID that is specific to a series of service events on the network establishes transitive trust as a function of the network and the ability to track and recreate the events of a muti- service transaction are captured and maintained in a file specific to the transaction to allow the reconstruction of the events associated with a transaction. End to end non- repudiation of a transaction is uniquely provided in the system. An origination UID can be populated by the transceiver, user, or application connected to the SSN such that end to end logging and transitive authentication can be supported, tracked and enforced; the UID is created and managed as a function of the network. Additional elements of security in support of either further authorization or further authentication on the network for a given service or function can be created and managed as a function of the network; examples are WS-S, SAML, XML certificates, OLDAP, Active

Directory, LDAP, and other credential related means. The secure multi function service network is provided as a web service; a web application can be accessed as the service used through the transceiver. The service definition on the network links between web services from one or more providers and applications from one or more providers on an implementation of the SSN to effect an aggregated service on the network.

Secure payment transactions are effected using a transceiver cell phone, smart phone, or other transceiver capable of an interconnection effected by an individual user with a funds source at a point of sale. A secure service network interconnects the transceiver, a funds source associated with the transceiver and the point of sale. A global secure service gateway manages the security of the interconnections between and among the transceiver, funds source and point of sale. Upon authentication and authorization, the user of the transceiver is securely verified as the true user of the transceiver and owner of the funds source. The user can enter a debit or credit with respect to the point of sale from or to the funds source over the secure network; in the SSN network, the user is verified as the true owner of a checking account. A biometric user identification may be adapted intrinsically in the transceiver. The user funds source, a retail bank, or credit card system, may be interconnected with a payments network that allows at least one of the debit, credit, payment and settlement of funds accessed by a user from the funds source. Thus, a multi function network for point of sale transactions is administered by a GSSG with access points securely maintained at local, individual SSGs.

Using a cell phone, smart phone, or other wired or wireless transceiver capable of an interconnection, multiple transaction types over a secure multi function service network using a transceiver system can be made. A payment originator (merchant) at a point of sale initiates the transaction with the user. The SSN interconnects the transceiver, a funds source associated with the transceiver and the point of sale, and a GSSG manages provisioning and service interconnections of SSGs between and among the transceiver, funds source and point of sale.

EXAMPLE VII

As shown in Figure 12 and Figure 13, a wireless device, cell phone, smart phone, or equivalent transceiver medium capable of wireless network communications is shown. The transceiver unit is interconnectable with an integrated processor

including a SSG capable of SSN receiving and storing information, and optionally providing tracking, accounting and other financial functions. Through a SSN, which may be configured in many alternative interconnections managed by a GSSG, as shown in Figure 15 and Figure 16, the transceiver device may be loaded with a predetermined amount of currency from the customer's retail bank. An network interconnection between the cell phone and a point of sale, such as a grocery store, a mall merchant, an ATM, or other site (POS sites) allowing a monetary transaction is made through the transceiver to the POS through SSN over an SSN created VSC specific to that service and the participants of the transaction.

The SSGs at the POS sites and the cell phone assure that the merchant effects a secure connection to the customer's cell phone, and that through the SSN, the funds are charged to the phone, or alternatively, through the cell phone physical network, in real time, to the cell phone user's bank cash or credit account (also members of the SSN and SSN service providers), can be debited to the merchant's account. Alternatively, the secure interconnection of the phone, or other transceiver, allows real time transactions to be conducted without a reserve of user funds charged to the telephone. For example, a purchase can be made and the debit owing can be transmitted through the secure network to the cell phone holder's retail bank, where a cash or credit account may be debited in the amount of a purchase. Thereupon, the merchant's account at the merchant bank is credited with the purchase amount.

Utilizing the SSN, communications are secure, authentication is mutual and multi-factor, and authorization at the phone may be effected by entering a coded PIN number, known only to the account holder of the phone, in the phone keyboard or other human interface on the phone that is validated locally or externally as a service over SSN where the credential validation is a service on the network that may or may not be specific to the cell phone provider or service provider. As used herein, "point of sale" may be any interconnectable SSN site with the cell phone, wireless device, computer, self service terminal, vending machine, wherein funds may be debited or credited to the user's account, an account held by a participant on the SSN, or at an account held by a non-participant on the network where account access is accomplished out of band of an SSN implementation.

Figure 13 shows an alternative interconnection of retail and merchant networks useful for processing checks in the system. In the drawing figures, it is evident that a

user in the SSN may be interconnected in one or more GSSG administered networks. Users and POS providers may also be interconnected in one or more SSNs: for example, an SSN interconnecting a merchant bank with retail banks, a customer SSN interconnecting account holders with retail banks, and SSN merchant networks, such as Visa ^® , and others. As an alternative, separate SSNs may require separate SSGs administered by a GSSG for each network in which the participant is a member.

Upon processing the user debit or credit, the SSN may simultaneously interconnect with the merchant bank and the transaction is processed with respect to the merchant account through commercial bank facilities. Typical of such facilities are net settlement, payment management, and/or payment exchange systems accessed and implemented through a merchant bank network utilizing the NSS, PMC and eP ^x systems as shown in Figure 17, Figure 18 and Figure 19. These systems may also be provided as services on an SSN implementation where participants can access these service or aggregate these services to effect a transaction. NSS, PMC and eP ^x are products of Synoran LLC, Columbus, Ohio.

EXAMPLE VIII

In Figure 13, the network SSG is configured to interconnect directly with the cell phone user's retail bank. Additional SSN security measures may be implemented at the transceiver level, such as biometric voice, fingerprint and ocular reading, before a network connection is effected. Simultaneously with user activation, the merchant connects through the SSN network to the user and the merchant's bank, whereupon a transaction may be effected. Upon entry of a transaction, identifying the amount, payor, payee, payor's bank, payee's bank, transaction information is transmitted debiting the user's debit or credit account, and crediting the merchant's account. Processing the payment information through eP ^x , PMC and/or NSS at the merchant bank allows real time monitoring and settlement on behalf of the bank associated with the user and the merchant, as well as the merchant's account at the merchant bank with regard to other banks and customers of the merchant. While ePx, PMC, and NSS are shown in the figure, applications with like functionality may be included in the implementation. In this manner, the participants are not required to use ePx, PMC, NSS to effect the transaction because SSN allows defining a service on the network that is independent of the application that my ultimately full fill that service. The service

provider determines the processing flow for any service the provider offers on the network.

EXAMPLE IX

In Figure 14, security measures are implemented at the cell phone level, such as biometric voice, fingerprint and ocular reading, before a network connection is effected. As in preceding examples, upon user activation through the SSN network, the user connects to the merchant, the merchant connects to the user and to the merchant's bank, whereupon a transaction may be authorized and effected. In this example, identification and authorization is securely accomplished, logged, and verified in a checking account transaction, independently of a user's direct access to funds or debit facility at a user's bank.

EXAMPLE X

Figure 22 illustrates architecture of the invention adapted to a secure bill presentment and payment application in which settlement and payment is effected between and among consumer payors and merchant payees that are members of banking and payment domains.

EXAMPLE Xl

The end to end payments solution shown in Figure 23 illustrates the overall adaptability of the SSN. The SSN networked based services are identified in Figure 23 wherein the SSN solution is represented by SSG A, SSG B, and the Global SSG. The example shows an example of two participant banks and a third party service provider that offers net settlement and check image archive services. Variations of this example are enabled by the SSN such as corporate financial service processing, treasury management services and the brokering of services across industries.

+++

Having thus described the invention in detail, those skilled in the art will appreciate that, given the present disclosure, modifications may be made to the invention without departing from the spirit of the inventive concept herein described. Therefore, it is not intended that the scope of the invention be limited to the specific and preferred embodiments illustrations as described. Rather, it is intended that the scope of the invention be determined by the appended claims.

>» • <«