Methods, systems, and computer readable media for validating a redirect address in a diameter message

• US 10,237,721 B2
• Filed: 01/17/2017
• Issued: 03/19/2019
• Est. Priority Date: 01/17/2017
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gupta, Nitin, Mahalank, Shashikiran Bhalachandra, Aravamudhan, Venkatesh
• Primary Examiner(s): Htun, San
• Application Number:
  US15/408,155
• Publication Number:
  US 20180205698A1
• Time in Patent Office: 791 Days
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 2101/622 Layer-2 addresses, e.g. medium access control [MAC] addresses
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04M 15/64 On-line charging system [OCS]
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04M 17/02 Coin-freed or check-freed systems , e.g. mobile- or card-operated phones, public telephones or booths
• CPC Class Codes: H04M 17/20 with provision for recharging the prepaid account or card, or for credit establishment
• CPC Class Codes: H04M 17/204 on-line recharging, e.g. cashless
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/205 Transfer to or from user equipment or user record carrier

Abstract

Methods, systems, and computer readable media for validating a redirect address in a Diameter message are disclosed. One method occurs at a Diameter node, e.g., a Diameter routing agent (DRA) node, a packet data network (PDN) gateway, a policy and charging enforcement function (PCEF) node, or a Diameter edge agent (DEA) node. The method includes receiving a message containing a redirect address that appears to be associated with a top-up server for facilitating a subscriber to recharge or top-up an account balance. The method also includes determining whether the redirect address is valid by querying, using a subscriber related identifier, a data structure containing one or more addresses. The method further includes performing at least one action based on the determining.

Claims

1. A method for validating a redirect address in a Diameter message, the method comprising:

at a Diameter routing agent node;

receiving a Diameter credit control message containing an attribute value pair (AVP), wherein the AVP includes a redirect address that appears to be associated with a top-up server for facilitating a subscriber to recharge or top-up an account balance, wherein the AVP includes a final unit indication AVP, a final unit action AVP, a redirect-server AVP, a redirect-address-type AVP, or a redirect-server-address AVP, and wherein the Diameter credit control message includes a Diameter credit control answer (CCA) message, a Diameter CCA initial (CCA-I) message, or a Diameter CCA update (CCA-U) message;

determining whether the redirect address is valid by querying, using a subscriber related identifier, a data structure containing one or more redirect addresses; and

performing at least one action based on the determining, wherein performing the at least one action includes determining that the redirect address is invalid, and, in response to determining that the redirect address is invalid, preventing the invalid redirect address from being received by a user device by modifying the Diameter credit control message to replace the invalid redirect address with a valid redirect address and sending the Diameter credit control message to a packet data network (PDN) gateway or by discarding the Diameter credit control message without sending the Diameter credit control message to the PDN gateway.

2. The method of claim 1 wherein determining whether the redirect address is valid includes determining that the redirect address is valid by matching the redirect address with an address in the data structure, wherein the one or more redirect addresses in the data structure are valid redirect addresses.

3. The method of claim 1 wherein determining whether the redirect address is valid includes determining that the redirect address is invalid by matching the redirect address with an address in the data structure, wherein the one or more redirect addresses in the data structure are known invalid redirect addresses.

4. The method of claim 1 wherein the subscriber related identifier includes a network identifier, a mobile country code (MCC), a mobile network code (MNC), a location area code (LAC), a network identifier, a cell global identifier (CGI), a base station identifier (BSID), an access node identifier, a cell identity (CI), a service area code (SAC), a routing area identity (RAI), a routing area code (RAC), a tracking area identity (TAI), a tracking area code (TAC), an eUTRAN CGI (EGCI), a user device identifier, an international mobile station equipment identity (IMEI), a phone number, or an international mobile subscriber identity (IMSI).

5. The method of claim 1 wherein the Diameter credit control message originates from an online charging server (OCS), a charging server, or a policy and charging rules function (PCRF).

6. The method of claim 1 wherein the redirect address includes an Internet protocol (IP) version 4 address, an IP version 6 address, a uniform resource locator (URL), or a session initiation protocol (SIP) uniform resource identifier (URI).

7. A system for validating a redirect address in a Diameter message, the system comprising:

a Diameter routing agent node comprising;

at least one processor;

at least one communications interface; and

a memory,

wherein the Diameter routing agent node is configured for;

receiving, using the at least one communications interface, a Diameter credit control message containing an attribute value pair (AVP), wherein the AVP includes a redirect address that appears to be associated with a top-up server for facilitating a subscriber to recharge or top-up an account balance, wherein the AVP includes a final unit indication AVP, a final unit action AVP, a redirect-server AVP, a redirect-address-type AVP, or a redirect-server-address AVP, and wherein the Diameter credit control message includes a Diameter credit control answer (CCA) message, a Diameter CCA initial (CCA-I) message, or a Diameter CCA update (CCA-U) message;

determining whether the redirect address is valid by querying, using a subscriber related identifier, a data structure containing one or more redirect addresses; and

performing at least one action based on the determining, wherein performing the at least one action includes determining that the redirect address is invalid, and, in response to determining that the redirect address is invalid, preventing the invalid redirect address from being received by a user device by modifying the Diameter credit control message to replace the invalid redirect address with a valid redirect address and sending the Diameter credit control message to a packet data network (PDN) gateway or by discarding the Diameter credit control message without sending the Diameter credit control message to the PDN gateway.

8. The system of claim 7 wherein determining whether the redirect address is valid includes determining that the redirect address is valid by matching the redirect address with an address in the data structure, wherein the one or more redirect addresses in the data structure are valid redirect addresses.

9. The system of claim 7 wherein determining whether the redirect address is valid includes determining that the redirect address is invalid by matching the redirect address with an address in the data structure, wherein the one or more redirect addresses in the data structure are known invalid redirect addresses.

10. The system of claim 7 wherein the subscriber related identifier includes a network identifier, a mobile country code (MCC), a mobile network code (MNC), a location area code (LAC), a network identifier, a cell global identifier (CGI), a base station identifier (BSID), an access node identifier, a cell identity (CI), a service area code (SAC), a routing area identity (RAI), a routing area code (RAC), a tracking area identity (TAI), a tracking area code (TAC), an eUTRAN CGI (EGCI), a user device identifier, an international mobile station equipment identity (IMEI), a phone number, or an international mobile subscriber identity (IMSI).

11. The system of claim 7 wherein the Diameter credit control message originates from an online charging server (OCS), a charging server, or a policy and charging rules function (PCRF).

12. The system of claim 7 wherein the redirect address includes an Internet protocol (IP) version 4 address, an IP version 6 address, a uniform resource locator (URL), or a session initiation protocol (SIP) uniform resource identifier (URI).

13. A non-transitory computer readable medium comprising computer executable instructions embodied in the non-transitory computer readable medium that when executed by at least one processor of at least one computer cause the at least one computer to perform steps comprising:

at a Diameter routing agent node;

receiving a Diameter credit control message containing an attribute value pair (AVP), wherein the AVP includes a redirect address that appears to be associated with a top-up server for facilitating a subscriber to recharge or top-up an account balance, wherein the AVP includes a final unit indication AVP, a final unit action AVP, a redirect-server AVP, a redirect-address-type AVP, or a redirect-server-address AVP, and wherein the Diameter credit control message includes a Diameter credit control answer (CCA) message, a Diameter CCA initial (CCA-I) message, or a Diameter CCA update (CCA-U) message;

determining whether the redirect address is valid by querying, using a subscriber related identifier, a data structure containing one or more redirect addresses; and

performing at least one action based on the determining, wherein performing the at least one action includes determining that the redirect address is invalid, and, in response to determining that the redirect address is invalid, preventing the invalid redirect address from being received by a user device by modifying the Diameter credit control message to replace the invalid redirect address with a valid redirect address and sending the Diameter credit control message to a packet data network (PDN) gateway or by discarding the Diameter credit control message without sending the Diameter credit control message to the PDN gateway.