IP Library Granted Patent US 12,634,686
Granted Patent B2
US 12,634,686 · App. 16/827,492 · Granted May 19, 2026

Diameter multifold message

Inventors: Manisha Sameer Gambhir Parekh (Pune, IN); Shivani Mehrotra (Pune, IN)
Assignee: Parallel Wireless, Inc.
H04W12/06
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,634,686
App. No.
16/827,492
Granted
May 19, 2026
Kind
B2
Abstract

Systems, methods and computer software are disclosed for providing a Diameter multifold message. In one embodiment a method is disclosed, comprising: providing a multifold-command Attribute Value Pair (AVP), the multifold-command AVP including an AVP code, a set of VMP flags, an AVP length and a vendor ID; including the AVP in a Capabilities Exchange Request (CER) command for a Diameter stack supporting multiplexing of commands in one message; and using the AVP to combine messages from multiple applications running on a single Diameter node and multiple commands from a single application.

Claims (39)

1 . A method for providing a Diameter multifold message, comprising:

providing a multifold-command Attribute Value Pair (AVP), the multifold-command AVP including an AVP code, a set of VMP flags, an AVP length and a vendor ID;

including the multifold-command AVP in a Capabilities Exchange Request (CER) command for a Diameter stack to determine support for multiplexing of commands in one message;

using the multifold-command AVP to combine multiple Diameter messages, from at least one of: multiple applications running on a first node supporting a Diameter protocol, and multiple commands from a single application, into a single Diameter multifold message communicated between the first node and a peer node supporting the Diameter protocol; and

performing a check to ensure that a combined length of the multiple Diameter messages to be published in the single Diameter multifold message does not exceed space available in an existing packet buffer.

2 . The method of claim 1 wherein:

the first node is a core network node or a RAN node; and

the peer node is a core network node or a RAN node.

3 . The method of claim 1 wherein the set of VMP flags includes a vendor-specific (V) bit indicating whether an optional vendor ID field is present.

4 . The method of claim 3 wherein the set of VMP flags includes a mandatory (M) bit indicating whether support of the multifold-command AVP is required.

5 . The method of claim 4 wherein the set of VMP flags includes a P bit indicating a need for encryption for end-to-end security.

6 . The method of claim 5 wherein when providing a multifold-command AVP, the V bit is set, the M bit is not set, and the P bit may be set or not set.

7 . The method of claim 1 further comprising when a peer node supports multiplexing commands, receiving from the peer node a Capabilities Exchange Answer (CEA) command including the multifold-command AVP.

8 . The method of claim 1 further comprising batch processing the combined multiple Diameter messages.

9 . A non-transitory computer-readable medium containing instructions for providing a Diameter multifold message which, when executed, cause a system to perform steps comprising:

providing a multifold-command Attribute Value Pair (AVP), the multifold-command AVP including an AVP code, a set of VMP flags, an AVP length and a vendor ID;

including the multi fold-command AVP in a Capabilities Exchange Request (CER) command for a Diameter stack to determine support for multiplexing of commands in one message;

using the multifold-command AVP to combine multiple Diameter messages, from at least one of: multiple applications running on a first node supporting a Diameter protocol and multiple commands from a single application, into a single Diameter multifold message communicated between the first node and a peer node supporting the Diameter protocol; and

performing a check to ensure that a combined length of the multiple Diameter messages to be published in the single Diameter multifold message does not exceed space available in an existing packet buffer.

10 . The computer-readable medium of claim 9 wherein:

the first node is a core network node or a radio access network (RAN) node; and

the peer node is a core network node or a RAN node.

11 . The computer-readable medium of claim 9 wherein the set of VMP flags includes a vendor-specific (V) bit indicating whether an optional vendor ID field is present.

12 . The computer-readable medium of claim 11 wherein the set of VMP flags includes a mandatory (M) bit indicating whether support of the multifold-command AVP is required.

13 . The computer-readable medium of claim 12 wherein the set of VMP flags includes a P bit indicating a need for encryption for end-to-end security.

14 . The computer-readable medium of claim 13 wherein instructions for providing a multifold-command AVP includes instructions for providing the multifold-command AVP in which the V bit is set, the M bit is not set, and the P bit may be set or not set.

15 . The computer-readable medium of claim 9 further comprising instructions, which when executed, cause the system to perform the step of, when a peer node supports multiplexing commands, receiving from the peer node a Capabilities Exchange Answer (CEA) command including the multifold-command AVP.

16 . The computer-readable medium of claim 9 further comprising instructions, which when executed, cause the system to perform the step of batch processing the combined multiple Diameter messages.

17 . A system for providing a Diameter multifold message, comprising:

a first core network or radio access network (RAN) node, including a processor coupled to a memory, and configured to couple to

a second core network or RAN node;

wherein the first core network or RAN node provides a multifold-command Attribute Value Pair (AVP), the multifold-command AVP including an AVP code, a set of VMP flags, an AVP length and a vendor ID, the multifold-command AVP included in a Capabilities Exchange Request (CER) command for a Diameter stack to determine support for multiplexing of commands in one message;

wherein the first core network or RAN node and the second core network or RAN node use the determined multiplexing support to combine Diameter messages, from at least one of multiple applications running on the first core network or RAN node and multiple commands from a single application, into a single Diameter multifold message communicated between the first core network or RAN node and the second core network or RAN node; and

wherein the first core network or RAN node performs a check to ensure that a combined length of the multiple Diameter messages to be published in the single Diameter multifold message does not exceed space available in an existing packet buffer.

18 . The system of claim 17 wherein:

the first core network or RAN node is a core network node; and

the second core network or RAN node is a RAN node.

19 . The system of claim 17 wherein the set of VMP flags includes a vendor-specific (V) bit indicating whether an optional vendor ID field is present, a mandatory (M) bit indicating whether support of the multifold-command AVP is required, and a P bit indicating a need for encryption for end-to-end security, and wherein a multifold-command AVP is provided in which the V bit is set, the M bit is not set, and the P bit may be set or not set.

20 . The system of claim 17 wherein the combined multiple Diameter messages are batch processed.

Assignments (2)
RELEASE OF SECURITY INTEREST Recorded Jul 12, 2022
From: VENTURE LENDING & LEASING IX, INC.; WTI FUND X, INC.
To: PARALLEL WIRELESS, INC.
Reel/Frame 060900/0022 →
SECURITY INTEREST Recorded Mar 1, 2022
From: PARALLEL WIRELESS, INC.
To: VENTURE LENDING & LEASING IX, INC.; WTI FUND X, INC.
Reel/Frame 059279/0851 →
Continuity (2)
Provisional Application 62822647 · Mar 22, 2019
Related Publication 20200304996A1 · Sep 24, 2020
References Cited (14)
US 9654553B2 · Mann · 2017 [cited by applicant]
US 20060171365A1 · Borella · 2006 [cited by examiner]
US 20110173332A1 · Li · 2011 [cited by applicant]
US 20130328429A1 · Enomoto · 2013 [cited by examiner]
US 20200204961A1 · Diwahar · 2020 [cited by examiner]
US 20210051235A1 · Cai · 2021 [cited by examiner]
Magnus Olsson, Shabnam Sultana, Catherine Mulligan, “Diameter Protocol”, EPC and 4G Packet Networks Driving the Mobile Broadband Revolution Book ⋅ Second Edition ⋅ 2013. [cited by examiner]
Cellusys, “Diameter Base Protocol:pocket-guide”, Mar. 10, 2019. [cited by examiner]
Ernon, “Diameter Extensible Authentication Protocol (EAP) Application”, 2005 (Year: 2005). [cited by examiner]
Diameter, “Diameter Protocol Explained” (Year: 2011). [cited by examiner]
Jones “Diameter Group Signaling draft-ietf-dime-group-signaling-01.txt”, further in view of (Year: 2013). [cited by examiner]
Fajardo “Diameter Base Protocol draft-ietf-dime-rfc3588bis-34.txt”. (Year: 2012). [cited by examiner]
Hannes Tschofenig; Sebastien Decugis; Jean Mahoney; Jouni Korhonen, “Diameter End-to-End Communication,” in Diameter: New Generation AAA Protocol—Design, Practice, and Applications , Wiley, 2019, pp. 61-80. (Year: 2019). [cited by examiner]
A. Hussein, I. H. Elhajj, A. Chehab and A. Kayssi, “Securing Diameter: Comparing TLS, DTLS, and IPSec,” 2016 IEEE International Multidisciplinary Conference on Engineering Technology (IMCET), Beirut, Lebanon, 2016, pp. … [cited by examiner]