IP Library › Granted Patent US 12,712,948
Granted Patent B2
US 12,712,948 · App. 18/776,510 · Granted Aug 18, 2026

Application service behavior management using request context

Inventors: Masoud Aghadavoodi Jolfaei (Wiesloch, DE); Frederick Dufour (Heidelberg, DE)
Assignee: SAP SE
H04L67/51G06F16/2455H04L41/084H04L67/133
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,712,948
App. No.
18/776,510
Filed
Jul 18, 2024
Granted
Aug 18, 2026
Kind
B2
Art Unit
2449
USPC
709/223
Abstract

Techniques for managing application service behavior using request context are disclosed. In some embodiments, a computer system performs a method comprising: detecting a request sent by a service of an application, the service being one of a plurality of services included in a microservice architecture of the application, the request including a service type data that identifies the application and a service identification data that identifies the service; determining a behavior configuration for the request based on the service type data and the service identification data; and executing the service or another service of the plurality of services based on the determined behavior configuration.

Claims (35)

1 . A system comprising:

at least one hardware processor; and

a non-transitory computer-readable medium storing executable instructions that, when executed, cause the at least one hardware processor to perform operations comprising:

detecting a request sent by a first service of an application, the first service being one of a plurality of services included in a microservice architecture of the application, the request including a service type data that identifies the application and a service identification data that identifies the first service;

determining a behavior configuration for the request based on the service type data and the service identification data, the behavior configuration comprising a configuration of a priority level for executing the first service or a second service of the plurality of services, and a configuration for the executing of the first service or the second service using a workload class identification, the workload class identification being configured to be used in allocating one or more computing resources for the executing of the first service or the second service; and

executing the first service or the second service based on the determined behavior configuration.

2 . The system of claim 1 , wherein the behavior configuration further comprises a configuration of a log level and a feature flag for the executing of the first service or the second service.

3 . The system of claim 1 , wherein the behavior configuration further comprises a configuration for running a database query with a statement hash and a hint, the statement hash comprising a hash of a query statement of the database query, and the hint being configured to instruct a database engine on how to execute the database query.

4 . The system of claim 1 , wherein the request comprises a byte array structure in which values of properties of the request are encoded.

5 . The system of claim 4 , wherein the properties of the request encoded in the byte array structure include one or more of a hard coded value used to determine a beginning of the request, a version of a format of the request, a length of the byte array structure, one or more trace flags, an initiator system identification, an initiator component identification, a type of the request, and a user identification.

6 . The system of claim 4 , wherein the properties of the request encoded in the byte array structure include one or more of a unique identifier of the request, a client number, a component type, a root context identification, a connection identification, a connection counter, a variable part counter, a variable part offset, and a hard coded value used to determine an end of the request.

7 . The system of claim 1 , wherein the determining the behavior configuration comprises:

accessing a behavior management catalog stored in a database, the behavior management catalog comprising a plurality of behavior configurations including the behavior configuration; and

identifying the behavior configuration from the plurality of behavior configurations in the behavior management catalog using the service type data and the service identification data.

8 . The system of claim 7 , wherein the behavior management catalog is accessed using a representational state transfer (REST) application programming interface (API).

9 . A non-transitory machine-readable storage medium tangibly embodying a set of instructions that, when executed by at least one hardware processor, causes the at least one processor to perform operations comprising:

detecting a request sent by a first service of an application, the first service being one of a plurality of services included in a microservice architecture of the application, the request including a service type data that identifies the application and a service identification data that identifies the first service;

determining a behavior configuration for the request based on the service type data and the service identification data, the behavior configuration comprising a configuration of a priority level for executing the first service or a second service of the plurality of services, and a configuration for the executing of the first service or the second service using a workload class identification, the workload class identification being configured to be used in allocating one or more computing resources for the executing of the first service or the second service; and

executing the first service or the second service based on the determined behavior configuration.

10 . The non-transitory machine-readable storage medium of claim 9 , wherein the behavior configuration further comprises a configuration of a log level and a feature flag for the executing of the first service or the second service.

11 . The non-transitory machine-readable storage medium of claim 9 , wherein the behavior configuration further comprises a configuration for running a database query with a statement hash and a hint, the statement hash comprising a hash of a query statement of the database query, and the hint being configured to instruct a database engine on how to execute the database query.

12 . The non-transitory machine-readable storage medium of claim 9 , wherein the request comprises a byte array structure in which values of properties of the request are encoded.

13 . The non-transitory machine-readable storage medium of claim 12 , wherein the properties of the request encoded in the byte array structure include one or more of a hard coded value used to determine a beginning of the request, a version of a format of the request, a length of the byte array structure, one or more trace flags, an initiator system identification, an initiator component identification, a type of the request, and a user identification.

14 . A computer-implemented method performed by a computer system comprising a memory and at least one hardware processor, the computer-implemented method comprising:

detecting a request sent by a first service of an application, the first service being one of a plurality of services included in a microservice architecture of the application, the request including a service type data that identifies the application and a service identification data that identifies the first service;

determining a behavior configuration for the request based on the service type data and the service identification data, the behavior configuration comprising a configuration of a priority level for executing the first service or a second service of the plurality of services, and a configuration for the executing of the first service or the second service using a workload class identification, the workload class identification being configured to be used in allocating one or more computing resources for the executing of the first service or the second service; and

executing the first service or the second service based on the determined behavior configuration.

15 . The computer-implemented method of claim 14 , wherein the behavior configuration further comprises a configuration of a log level and a feature flag for the executing of the first service or the second service.

16 . The computer-implemented method of claim 14 , wherein the behavior configuration further comprises a configuration for running a database query with a statement hash and a hint, the statement hash comprising a hash of a query statement of the database query, and the hint being configured to instruct a database engine on how to execute the database query.

17 . The computer-implemented method of claim 14 , wherein the request comprises a byte array structure in which values of properties of the request are encoded.

18 . The computer-implemented method of claim 17 , wherein the properties of the request encoded in the byte array structure include one or more of a hard coded value used to determine a beginning of the request, a version of a format of the request, a length of the byte array structure, one or more trace flags, an initiator system identification, an initiator component identification, a type of the request, and a user identification.

19 . The computer-implemented method of claim 17 , wherein the properties of the request encoded in the byte array structure include one or more of a unique identifier of the request, a client number, a component type, a root context identification, a connection identification, a connection counter, a variable part counter, a variable part offset, and a hard coded value used to determine an end of the request.

20 . The computer-implemented method of claim 14 , wherein the determining the behavior configuration comprises:

accessing a behavior management catalog stored in a database, the behavior management catalog comprising a plurality of behavior configurations including the behavior configuration; and

identifying the behavior configuration from the plurality of behavior configurations in the behavior management catalog using the service type data and the service identification data.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2026
From: AGHADAVOODI JOLFAEI, MASOUD; DUFOUR, FREDERICK
To: SAP SE
Reel/Frame 075323/0821 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 19, 2024
From: JOLFAEI, MASOUD AGHADAVOODI; DUFOUR, FREDERICK
To: SAP SE
Reel/Frame 068030/0620 →
Continuity (2)
Continuation 17830752 · Jun 2, 2022
Related Publication 20240372924A1 · Nov 7, 2024
References Cited (21)
US 11252025B2 · A et al. · 2022 [cited by applicant]
US 20050256931A1 · Follmeg · 2005 [cited by examiner]
US 20160112475A1 · Lawson et al. · 2016 [cited by applicant]
US 20180285416A1 · Bestfleisch · 2018 [cited by applicant]
US 20180302283A1 · Vyas et al. · 2018 [cited by applicant]
US 20190327324A1 · Buffone · 2019 [cited by examiner]
US 20200366752A1 · White · 2020 [cited by applicant]
US 20210258212A1 · Uke et al. · 2021 [cited by applicant]
US 20210311756A1 · Bhosle et al. · 2021 [cited by applicant]
US 20210373924A1 · Sivaraman · 2021 [cited by examiner]
US 20220150113A1 · A et al. · 2022 [cited by applicant]
US 20220342718A1 · Iqbal et al. · 2022 [cited by applicant]
US 20230281038A1 · Shah · 2023 [cited by examiner]
US 20230396687A1 · Aghadavoodi Jolfaei et al. · 2023 [cited by applicant]
CN 112379948A · 2021 [cited by examiner]
“U.S. Appl. No. 17/830,752, Examiner Interview Summary mailed Feb. 20, 2024”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 17/830,752, Non Final Office Action mailed Jan. 30, 2024”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 17/830,752, Notice of Allowance mailed Jun. 20, 2024”, 18 pgs. [cited by applicant]
“U.S. Appl. No. 17/830,752, Response filed Feb. 26, 2024 to Non Final Office Action mailed Jan. 30, 2024”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/830,752, Response filed Nov. 6, 2023 to Restriction Requirement mailed Sep. 11, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/830,752, Restriction Requirement mailed Sep. 11, 2023”, 7 pgs. [cited by applicant]