# US 2020/0401714 A1 · Method and system for natively accessing enterprise data according to an identified view context

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0401714 A1
- Document ID: US20200401714A1
- Status: Published application
- Kind: A1
- Application number: 16/444,970
- Filed: 2019-06-18
- Published: 2020-12-24
- Earliest claimed: 2019-06-18
- Assignees: ADP, Inc.
- Applicants: Adp, LLC
- Inventors: Eitan Klein; Dan Bar-Lev; Richard Noad; Norman Azoulay; Robert Shewan
- Web page: https://patentgrep.com/patent/US20200401714A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- H04L 63/0281: {Proxies}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06Q 10/105: Human resources
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A method, apparatus, and computer program product for validating a structured data object. A computer system receives a request to access enterprise data within a human resources database. The request is received from a consuming service within an authentication context of the user. The computer system determines a view context for the human resources (HR) database by applying a business rule to the authentication context. The business rule comprises a set of data nodes that are composed into a structured data object according to a domain specific language. The computer system creates a data view of the human resources database according to the view context determined by the business rule. The computer system provides the data view to the consuming service. The consuming service natively accesses the enterprise data through the data view.

## Claims

### Claim 1

A computer-implemented method for natively accessing enterprise data according to an identified view context, the method comprising:
receiving a request to access enterprise data within a human resources database, wherein the request is received from a consuming service within an authentication context of a user;
determining a view context for the human resources (HR) database by applying a business rule to the authentication context, wherein the business rule comprises a set of data nodes that are composed into a structured data object according to a domain specific language;
creating a data view of the human resources database according to the view context determined by the business rule; and
providing the data view to the consuming service, where in the enterprise data is natively accessed through the data view.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising:
maintaining the authentication context within a lightweight directory access protocol (LDAP) interface in communication with the (HR) database, wherein the LDAP interface serves as a proxy for requests between the consuming service and the HR database, wherein the LDAP interface serves as a system of record data source.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the LDAP interface maintains the authentication context on an on-demand basis.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein receiving the request to access enterprise data further comprises:
receiving an HTTP request to access the enterprise data at a RESTful API between the consuming service and the HR database, wherein the authentication context is indicated in the HTTP request.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein creating the data view further comprises:
generating a data seeding window according to the authentication context, wherein the data seeding window enables assignment of the correct data view for the consuming service according to a native data context of the consuming service.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein determining the view context further comprises:
identifying the authentication context from the request;
determining a persona of the user within an organization based on the authentication context;
determining the view context based on the persona of the user; and
redirecting the request to the data view according to session data.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein receiving the request further comprises:
locking the data views;
refreshing the data views; and
unlocking the data views.

### Claim 8 (depends on 7)

The computer-implemented method of claim 7, wherein the data view is a first data view, and wherein refreshing the data views further comprises:
creating a second data view of the human resources database according to the view context determined by the business rule; and
setting a pointer to the session data to indicate the second data view.

### Claim 9 (depends on 6)

The computer-implemented method of claim 6, further comprising:
mapping the authentication context from the request to an employee identifier of within an organization;
interpreting the set of data nodes within a context of the employee identifier to determine the persona of the user; and
interpreting the set of data nodes within a context of the persona of the user to determine the view context for the user that is allowed by the business rule.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein interpreting the set of data nodes further comprises:
identifying rules and properties for the business rule, wherein the rules and properties are indicated within the plurality of linked data nodes; and
wherein creating the data view further comprises:
creating the data view according to the rules and properties indicated within the plurality of linked data nodes.

### Claim 11 (depends on 9)

The computer-implemented method of claim 9, wherein interpreting the set of data nodes forms a syntax tree, the method further comprising:
entering the syntax tree and the requested enterprise data into an abstract syntax tree interpreter, wherein a compiler operation to generate computer code for implementing the business rule is avoided, and wherein executing the abstract syntax tree interpreter produces a result without using executable code to achieve the result.

### Claim 12

A computer system comprising:
a hardware processor; and
a lightweight directory access protocol (LDAP) service in communication with the hardware processor, wherein the LDAP service:
receives a request to access enterprise data within a human resources database, wherein the request is received from a consuming service within an authentication context of a user;
determines a view context for the human resources (HR) database by applying a business rule to the authentication context, wherein the business rule comprises a set of data nodes that are composed into a structured data object according to a domain specific language;
creates a data view of the human resources database according to the view context determined by the business rule; and
provides the data view to the consuming service, where in the enterprise data is natively accessed through the data view.

### Claim 13 (depends on 12)

The computer system of claim 12, wherein the LDAP service further:
maintains the authentication context within a lightweight directory access protocol (LDAP) interface in communication with the (HR) database, wherein the LDAP interface serves as a proxy for requests between the consuming service and the HR database, wherein the LDAP interface serves as a system of record data source.

### Claim 14 (depends on 13)

The computer system of claim 13, wherein the LDAP interface maintains the authentication context on an on-demand basis.

### Claim 15 (depends on 12)

The computer system of claim 12, wherein, in receiving the request to access enterprise data, the LDAP service further:
receives an HTTP request to access the enterprise data at a RESTful API between the consuming service and the HR database, wherein the authentication context is indicated in the HTTP request.

### Claim 16 (depends on 12)

The computer system claim 12, wherein in creating the data view, the LDAP service further:
generates a data seeding window according to the authentication context, wherein the data seeding window enables assignment of the correct data view for the consuming service according to a native data context of the consuming service.

### Claim 17 (depends on 12)

The computer system of claim 12, wherein in determining the view context, the LDAP service further:
identifies the authentication context from the request;
determines a persona of the user within an organization based on the authentication context;
determines the view context based on the persona of the user; and
redirects the request to the data view according to session data.

### Claim 18 (depends on 17)

The computer system of claim 17, wherein in receiving the request, the LDAP service further:
locks the data views;
refreshes the data views; and
unlocks the data views.

### Claim 19 (depends on 18)

The computer system of claim 18, wherein the data view is a first data view, and wherein in refreshing the data views, the LDAP service further:
creates a second data view of the human resources database according to the view context determined by the business rule; and
sets a pointer to the session data to indicate the second data view.

### Claim 20 (depends on 18)

The computer system of claim 18, wherein the LDAP service further:
maps the authentication context from the request to an employee identifier of within an organization;
interprets the set of data nodes within a context of the employee identifier to determine the persona of the user; and
interprets the set of data nodes within a context of the persona of the user to determine the view context for the user that is allowed by the business rule.

### Claim 21 (depends on 20)

The computer system of claim 20, wherein in interpreting the set of data nodes, the LDAP service further:
identifies rules and properties for the business rule, wherein the rules and properties are indicated within the plurality of linked data nodes; and
wherein in creating the data view, the LDAP service further:
creates the data view according to the rules and properties indicated within the plurality of linked data nodes.

### Claim 22 (depends on 20)

The computer system of claim 20, wherein interpreting the set of data nodes forms a syntax tree, the LDAP service further:
integers the syntax tree and the requested enterprise data into an abstract syntax tree interpreter, wherein a compiler operation to generate computer code for implementing the business rule is avoided, and wherein executing the abstract syntax tree interpreter produces a result without using executable code to achieve the result.

### Claim 23

A computer program product for natively accessing enterprise data according to an identified view context, the computer program product comprising:
a non-transitory computer readable storage medium;
program code, stored on the computer readable storage medium, for receiving a request to access enterprise data within a human resources database, wherein the request is received from a consuming service within an authentication context of a user;
program code, stored on the computer readable storage medium, for determining a view context for the human resources (HR) database by applying a business rule to the authentication context, wherein the business rule comprises a set of data nodes that are composed into a structured data object according to a domain specific language;
program code, stored on the computer readable storage medium, for creating a data view of the human resources database according to the view context determined by the business rule; and
program code, stored on the computer readable storage medium, for providing the data view to the consuming service, where in the enterprise data is natively accessed through the data view.

### Claim 24 (depends on 23)

The computer program product of claim 23, further comprising:
program code, stored on the computer readable storage medium, for maintaining the authentication context within a lightweight directory access protocol (LDAP) interface in communication with the (HR) database, wherein the LDAP interface serves as a proxy for requests between the consuming service and the HR database, wherein the LDAP interface serves as a system of record data source.

### Claim 25 (depends on 24)

The computer program product of claim 24, wherein the LDAP interface maintains the authentication context on an on-demand basis.

### Claim 26 (depends on 23)

The computer program product of claim 23, wherein the program code for receiving the request to access enterprise data further comprises:
program code, stored on the computer readable storage medium, for receiving an HTTP request to access the enterprise data at a RESTful API between the consuming service and the HR database, wherein the authentication context is indicated in the HTTP request.

### Claim 27 (depends on 23)

The computer program product of claim 23, wherein the program code for creating the data view further comprises:
program code, stored on the computer readable storage medium, for generating a data seeding window according to the authentication context, wherein the data seeding window enables assignment of the correct data view for the consuming service according to a native data context of the consuming service.

### Claim 28 (depends on 23)

The computer program product of claim 23, wherein the program code for determining the view context further comprises:
program code, stored on the computer readable storage medium, for identifying the authentication context from the request;
program code, stored on the computer readable storage medium, for determining a persona of the user within an organization based on the authentication context;
program code, stored on the computer readable storage medium, for determining the view context based on the persona of the user; and
program code, stored on the computer readable storage medium, for redirecting the request to the data view according to session data.

### Claim 29 (depends on 28)

The computer program product of claim 28, wherein the program code for receiving the request further comprises:
program code, stored on the computer readable storage medium, for locking the data views;
program code, stored on the computer readable storage medium, for refreshing the data views; and
program code, stored on the computer readable storage medium, for unlocking the data views.

### Claim 30 (depends on 29)

The computer program product of claim 29, wherein the data view is a first data view, and wherein the program code for refreshing the data views further comprises:
program code, stored on the computer readable storage medium, for creating a second data view of the human resources database according to the view context determined by the business rule; and
program code, stored on the computer readable storage medium, for setting a pointer to the session data to indicate the second data view.

### Claim 31 (depends on 28)

The computer program product of claim 28, further comprising:
program code, stored on the computer readable storage medium, for mapping the authentication context from the request to an employee identifier of within an organization;
program code, stored on the computer readable storage medium, for Interpreting the set of data nodes within a context of the employee identifier to determine the persona of the user; and
program code, stored on the computer readable storage medium, for Interpreting the set of data nodes within a context of the persona of the user to determine the view context for the user that is allowed by the business rule.

### Claim 32 (depends on 31)

The computer program product of claim 31, wherein the program code for interpreting the set of data nodes further comprises:
program code, stored on the computer readable storage medium, for identifying rules and properties for the business rule, wherein the rules and properties are indicated within the plurality of linked data nodes; and
wherein program code for creating the data view further comprises:
program code, stored on the computer readable storage medium, for creating the data view according to the rules and properties indicated within the plurality of linked data nodes.

### Claim 33 (depends on 31)

The computer program product of claim 31, wherein interpreting the set of data nodes forms a syntax tree, the computer program product further comprising:
program code, stored on the computer readable storage medium, for entering the syntax tree and the requested enterprise data into an abstract syntax tree interpreter, wherein a compiler operation to generate computer code for implementing the business rule is avoided, and wherein executing the abstract syntax tree interpreter produces a result without using executable code to achieve the result.