# US 2015/0148003 A1 · Adaptive Request Processing Service For Charging Requests

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

- Number: US 2015/0148003 A1
- Document ID: US20150148003A1
- Status: Published application
- Kind: A1
- Application number: 14/199,457
- Filed: 2014-03-06
- Published: 2015-05-28
- Earliest claimed: 2013-11-25
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporaton
- Inventors: Louis Thomas Piro, JR.; Jens Kaemmerer
- Web page: https://patentgrep.com/patent/US20150148003A1

## CPC

- G06Q 30/04: Billing or invoicing
- H04M 15/43: {Billing software details}
- H04M 15/70: {Administration or customization aspects; Counter-checking correct charges}
- H04M 15/725: {by the operator}
- 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
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

The present disclosure provides a method, non-transitory computer readable storage medium, and apparatus that implement an adaptable payload object model. In one embodiment, a payload object is generated using a payload specification that defines a plurality of payload attributes, where the payload object includes the plurality of payload attributes. The plurality of payload attributes of the payload object are populated with message attribute values that are extracted from an incoming message. The plurality of payload attributes of the payload object is validated. In one embodiment, an outgoing message is built that includes the payload object and is forwarded to a destination, such as a subscriber or a charging engine.

## Claims

### Claim 1

A method comprising:
generating a payload object, wherein
the payload object is generated using a message builder associated with a payload specification,
the payload specification defines a plurality of payload attributes, and
the payload object comprises the plurality of payload attributes;
populating the plurality of payload attributes with message attribute values, wherein
the message attribute values are extracted from an incoming message; and
validating the plurality of payload attributes of the payload object.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
building an outgoing message that comprises the payload object; and
forwarding the outgoing message to a destination, wherein
the destination comprises one of a subscriber and a charging engine.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
identifying a message type of the incoming message;
determining service product and event information from the incoming message; and
instantiating the message builder, based on the message type and service product and event information, wherein
the payload specification is retrieved from a repository of payload specifications.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
searching the repository for the payload specification, wherein
the payload specification is associated with the message type, and
the payload specification comprises information that matches the service product and event information.

### Claim 5 (depends on 1)

The method of claim 1, wherein the populating comprises
identifying a message attribute associated with a first payload attribute of the plurality of payload attributes;
extracting a value of the message attribute from the incoming message; and
setting the first payload attribute with the value.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
determining whether a first data type of the value matches a second data type of the first payload attribute, wherein
the first payload attribute is set with the value in response to a determination that the first data type matches the second data type.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
discarding the payload object in response to a determination that at least one payload attribute of the plurality of payload attributes is invalid, wherein
the at least one payload attribute is invalid in response to determining at least one of:
a data type of an extracted message attribute value associated with the at least one payload attribute violates the payload specification, and
the at least one payload attribute is a required payload attribute that is populated with an empty value.

### Claim 8

A non-transitory computer readable storage medium configured to store program instructions that, when executed on a processor, are configured to cause the processor to perform a method comprising:
generating a payload object, wherein
the payload object is generated using a message builder associated with a payload specification,
the payload specification defines a plurality of payload attributes, and
the payload object comprises the plurality of payload attributes;
populating the plurality of payload attributes with message attribute values, wherein
the message attribute values are extracted from an incoming message; and
validating the plurality of payload attributes of the payload object.

### Claim 9 (depends on 8)

The non-transitory computer readable storage medium of claim 8, wherein the method further comprises:
building an outgoing message that comprises the payload object; and
forwarding the outgoing message to a destination, wherein
the destination comprises one of a subscriber and a charging engine.

### Claim 10 (depends on 8)

The non-transitory computer readable storage medium of claim 8, wherein the method further comprises:
identifying a message type of the incoming message;
determining service product and event information from the incoming message; and
instantiating the message builder, based on the message type and service product and event information, wherein
the payload specification is retrieved from a repository of payload specifications.

### Claim 11 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the method further comprises:
searching the repository for the payload specification, wherein
the payload specification is associated with the message type, and
the payload specification comprises information that matches the service product and event information.

### Claim 12 (depends on 8)

The non-transitory computer readable storage medium of claim 8, wherein the populating comprises
identifying a message attribute associated with a first payload attribute of the plurality of payload attributes;
extracting a value of the message attribute from the incoming message; and
setting the first payload attribute with the value.

### Claim 13 (depends on 12)

The non-transitory computer readable storage medium of claim 12, wherein the method further comprises:
determining whether a first data type of the value matches a second data type of the first payload attribute, wherein
the first payload attribute is set with the value in response to a determination that the first data type matches the second data type.

### Claim 14 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the method further comprises:
discarding the payload object in response to a determination that at least one payload attribute of the plurality of payload attributes is invalid, wherein
the at least one payload attribute is invalid in response to determining at least one of:
a data type of an extracted message attribute value associated with the at least one payload attribute violates the payload specification, and
the at least one payload attribute that is populated with an empty value violates the payload specification.

### Claim 15

An apparatus comprising:
a processor; and
a memory coupled to the processor and configured to store instructions executable by the processor, the instructions configured to implement
a payload object generation module configured to generate a payload object, wherein
the payload object is generated using a message builder associated with a payload specification,
the payload specification defines a plurality of payload attributes, and
the payload object comprises the plurality of payload attributes;
a payload attribute population module configured to populate the plurality of payload attributes with message attribute values, wherein
the message attribute values are extracted from an incoming message; and
a payload build module configured to validate the plurality of payload attributes of the payload object.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the payload build module is further configured to
build an outgoing message that comprises the payload object, and
forward the outgoing message to a destination, wherein
the destination comprises one of a subscriber and a charging engine.

### Claim 17 (depends on 15)

The apparatus of claim 15, wherein the payload object generation module is further configured to
identify a message type of the incoming message;
determine service product and event information from the incoming message; and
instantiate the message builder, based on the message type and service product and event information, wherein
the payload specification is retrieved from a repository of payload specifications.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein the payload object generation module is further configured to
search the repository for the payload specification, wherein
the payload specification is associated with the message type, and
the payload specification comprises information that matches the service product and event information.

### Claim 19 (depends on 15)

The apparatus of claim 15, wherein the payload attribute population module is further configured to
identify a message attribute associated with a first payload attribute of the plurality of payload attributes;
extract a value of the message attribute from the incoming message; and
set the first payload attribute with the value.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the payload attribute population module is further configured to
determine whether a first data type of the value matches a second data type of the first payload attribute, wherein
the first payload attribute is set with the value in response to a determination that the first data type matches the second data type.
