# US 12,182,008 B2 · Labelling web traffic routing to support software testing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,182,008 B2 - Document ID: US12182008B2 - Status: Granted - Kind: B2 - Application number: 18/065,683 - Filed: 2022-12-14 - Published: 2024-06-20 - Granted: 2024-12-31 - Earliest claimed: 2022-12-14 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Sri Harsha Varada; Pavan Kumar Penugonda; Akash U. Dhoot; Pavan K Manda; Thomas Chang - Web page: https://patentgrep.com/patent/US12182008B2 ## CPC - G06F 11/3688: {for test execution, e.g. scheduling of test suites} - G06F 8/60: Software deployment - G06F 11/3668: Testing of software - G06F 11/3692: {for test results analysis} - G06F 11/3698: Environments for analysis, debugging or testing of software - G06F 11/323: {Visualisation of programs or trace data} - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - 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) ## Abstract Computer technology for: (i) determining which version of a software service to use depending upon whether the user requesting the service is a beta tester, and (ii) if the user status of the user requesting a software service is beta tester then: (a) that user will have the newer, testing-phase version of the software service used to fulfill the software service request, and (b) the user will be given an opportunity to provide feedback on the effectiveness and/or performance of the service to effect the beta testing of the new version of the software service under test. ## Claims ### Claim 1 A computer-implemented method (CIM) for performing beta testing of a first software service whose functionality is offered as a service to a plurality of requesters over a communication network, the CIM comprising: identifying the plurality of requesters for the first software service, wherein each requester is associated with a device that operates an application associated with the first software service; for each requester of the plurality of requesters, automatically assigning a beta tester status to the requester for the first software service, wherein the beta tester status comprises a beta tester level; receiving a first request, over the communication network and from a first requester of the plurality of the plurality of requesters, to use the first software service, with the request including an indication of the first requester's beta tester level; determining, by a set of machine logic rules and based, at least in part, upon the first requester's beta tester level, that the first software service will be served by a beta testing version of the first software instead of a production version of the first software service that is out of beta testing; and routing, based on the determining, by the first software service and in response to the first request, the beta testing version of the first software to a first device of the first requester that is using the application. ### Claim 2 (depends on 1) The CIM of claim 1 further comprising: responsive to the routing of the first request, performing, by the beta testing version of the first software service hosted on the first device for the first requester to obtain output data; and outputting, over the communication network and to the first requester, the output. ### Claim 3 (depends on 2) The CIM of claim 2: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 4 (depends on 1) The CIM of claim 1: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 5 (depends on 1) The CIM of claim 1 wherein: the first software service is a microservice; and the beta testing version hosted by the first device is implemented in a first container. ### Claim 6 (depends on 1) The CIM of claim 1 wherein the first request includes a predefined behavior user label to indicate the beta tester status assigned to the first requester. ### Claim 7 (depends on 1) The CIM of claim 1, wherein the beta tester level for each requester of the plurality of requesters is based a number of instances of feedback given by the requester. ### Claim 8 A computer program product (CPP) for performing beta testing on a first software service whose functionality is offered as a service to a plurality of requesters over a communication network, the CPP comprising: a set of storage device(s); and computer code stored collectively in the set of storage device(s), with the computer code including data and instructions to cause a processor(s) set to perform at least the following operations: identifying the plurality of requesters for the first software service, wherein each requester is associated with a device that operates an application associated with the first software service; for each requester of the plurality of requesters, automatically assigning a beta tester status to the requester for the first software service, wherein the beta tester status comprises a beta tester level; receiving a first request, over the communication network and from a first requester of the plurality of the plurality of requesters, to use the first software service, with the request including an indication of the first requester's beta tester level; determining, by a set of machine logic rules and based, at least in part, upon the first requester's beta tester level, that the first software service will be served by a beta testing version of the first software instead of a production version of the first software service that is out of beta testing; and routing, based on the determining, by the first software service and in response to the first request, the beta testing version of the first software to a first device of the first requester that is using the application. ### Claim 9 (depends on 8) The CPP of claim 8 wherein the computer code further includes instructions for causing the processor(s) set to perform the following operation(s): responsive to the routing of the first request, performing, by the beta testing version of the first software service hosted on the first device for the first requester to obtain output data; and outputting, over the communication network and to the first requester, the output. ### Claim 10 (depends on 9) The CPP of claim 9: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 11 (depends on 8) The CPP of claim 8: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 12 (depends on 8) The CPP of claim 8 wherein: the first software service is a microservice; and the beta testing version hosted by the first device is implemented in a first container. ### Claim 13 (depends on 8) The CPP of claim 8 wherein the first request includes a predefined behavior user label to indicate the beta tester status assigned to the first requester. ### Claim 14 A computer system (CS) for performing beta testing on a first software service whose functionality is offered as a service to a plurality of requesters over a communication network, the CS comprising: a processor(s) set; a set of storage device(s); and computer code stored collectively in the set of storage device(s), with the computer code including data and instructions to cause the processor(s) set to perform at least the following operations: identifying the plurality of requesters for the first software service, wherein each requester is associated with a device that operates an application associated with the first software service; for each requester of the plurality of requesters, automatically assigning a beta tester status to the requester for the first software service, wherein the beta tester status comprises a beta tester level; receiving a first request, over the communication network and from a first requester of the plurality of the plurality of requesters, to use the first software service, with the request including an indication of the first requester's beta tester level; determining, by a set of machine logic rules and based, at least in part, upon the first requester's beta tester level, that the first software service will be served by a beta testing version of the first software instead of a production version of the first software service that is out of beta testing; and routing, based on the determining, by the first software service and in response to the first request, the beta testing version of the first software to a first device of the first requester that is using the application. ### Claim 15 (depends on 14) The CS of claim 14 wherein the computer code further includes instructions for causing the processor(s) set to perform the following operation(s): responsive to the routing of the first request, performing, by the beta testing version of the first software service hosted on the first device for the first requester to obtain output data; and outputting, over the communication network and to the first requester, the output. ### Claim 16 (depends on 15) The CS of claim 15: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 17 (depends on 14) The CS of claim 14: receiving feedback data from the first requester with the feedback data including an indication of an assessment of the performance of the first software service by the beta testing version. ### Claim 18 (depends on 14) The CS of claim 14 wherein: the first software service is a microservice; and the beta testing version hosted by the first device is implemented in a first container. ### Claim 19 (depends on 14) The CS of claim 14 wherein the first request includes a predefined behavior user label to indicate the beta tester status assigned to the first requester.