# US 11,451,637 B2 · Method for migration of session accounting to a different stateful accounting peer > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,451,637 B2 - Document ID: US11451637B2 - Status: Granted - Kind: B2 - Application number: 16/766,452 - Filed: 2017-12-02 - Published: 2021-02-04 - Granted: 2022-09-20 - Earliest claimed: 2017-12-02 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Natarajan Venkataraman; Parag Narayanrao Pote - Web page: https://patentgrep.com/patent/US11451637B2 ## CPC - H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling} - H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)} - H04L 63/0892: {by using authentication-authorization-accounting [AAA] servers or protocols} - H04L 65/1069: Session establishment or de-establishment - H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms - H04L 67/143: Termination or inactivation of sessions, e.g. event-controlled end of session - H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding - H04L 67/148: Migration or transfer of sessions - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method for migrating a subscriber session from a first authentication, authorization and accounting (AAA) accounting peer to a second AAA accounting peer, where the first AAA accounting peer is stateful. The method includes receiving an accounting start packet from an AAA client application, forwarding the accounting start packet to the first AAA accounting peer, receiving an accounting update or accounting stop packet from the AAA client application; and sending an accounting start packet from the AAA client application to the second AAA accounting peer, in response to a connection failure with the first AAA accounting peer. ## Claims ### Claim 1 A method for migrating a subscriber session from a first authentication, authorization and accounting (AAA) accounting peer to a second AAA accounting peer, where the first AAA accounting peer is stateful, the method comprising: receiving an accounting start packet from an AAA client application; forwarding the accounting start packet to the first AAA accounting peer; receiving an accounting update or accounting stop packet from the AAA client application; selecting the second AAA accounting peer from the available accounting peers, in response to determination of a connection failure with the first AAA accounting peer; determining whether the received packet is the accounting update packet or the accounting stop packet; re-marking or re-labeling the accounting update packet, from the AAA client application, as an accounting start packet; and sending the re-marked or re-labeled accounting start packet from the AAA client application to the second AAA accounting peer. ### Claim 2 (depends on 1) The method of claim 1, further comprising: sending the accounting stop packet from the AAA client application to the second AAA accounting peer in response to receiving the accounting stop packet. ### Claim 3 (depends on 2) The method of claim 2, wherein the accounting start packet is a copy of the accounting stop packet received from the AAA client application. ### Claim 4 (depends on 1) The method of claim 1, further comprising: determining whether the first AAA accounting peer is available in response to receiving the accounting update or accounting stop packet. ### Claim 5 (depends on 1) The method of claim 1, wherein an AAA protocol utilized by the first AAA accounting peer, second AAA accounting peer, AAA protocol stack and AAA client application is Diameter. ### Claim 6 A network device configured to execute a plurality of virtual machines, the virtual machines configured to support network function virtualization (NFV), the plurality of virtual machines to support a method for migrating a subscriber session from a first authentication, authorization and accounting (AAA) accounting peer to a second AAA accounting peer, where the first AAA accounting peer is stateful, the network device comprising: a non-transitory computer readable medium having stored therein a AAA client; and a processor coupled to the non-transitory computer readable medium configured to execute a virtual machine from the plurality of virtual machine, the virtual machine to execute the AAA client, the AAA client configured to receive an accounting start packet from an AAA client application, to forward the accounting start packet to the first AAA accounting peer, to receive an accounting update or accounting stop packet from the AAA client application, to select the second AAA accounting peer from the available accounting peers, in response to determination of a connection failure with the first AAA accounting peer, to determine whether the received packet is the accounting update packet or the accounting stop packet, to re-mark or re-label the accounting update packet, from the AAA client application, as an accounting start packet; and to send the re-marked or re-labeled accounting start packet from the AAA client application to the second AAA accounting peer. ### Claim 7 (depends on 6) The network device of claim 6, wherein the AAA client is further configured to send the accounting stop packet from the AAA client application to the second AAA accounting peer in response to receiving the accounting stop packet. ### Claim 8 (depends on 6) The network device of claim 6, wherein the accounting start packet is a copy of the accounting stop packet received from the AAA client application. ### Claim 9 (depends on 8) The network device of claim 8, wherein the AAA client is further configured to determine whether the first AAA accounting peer is available in response to receiving the accounting update or accounting stop packet. ### Claim 10 (depends on 6) The network device of claim 6, wherein an AAA protocol utilized by the first AAA accounting peer, second AAA accounting peer, AAA protocol stack and AAA client application is Diameter. ### Claim 11 A computing device configured to execute a method for migrating a subscriber session from a first authentication, authorization and accounting (AAA) accounting peer to a second AAA accounting peer, where the first AAA accounting peer is stateful, the computing device comprising: a non-transitory computer readable medium having stored therein a AAA client; and a processor coupled to the non-transitory computer readable medium configured to execute the AAA client, the AAA client configured to receive an accounting start packet from an AAA client application, to forward the accounting start packet to the first AAA accounting peer, to receive an accounting update or accounting stop packet from the AAA client application, to select the second AAA accounting peer from the available accounting peers, in response to determination of a connection failure with the first AAA accounting peer, to determine whether the received packet is the accounting update packet or the accounting stop packet, to re-mark or re-label the accounting update packet, from the AAA client application, as an accounting start packet; and to send the re-marked or re-labeled accounting start packet from the AAA client application to the second AAA accounting peer. ### Claim 12 (depends on 11) The computing device of claim 11, wherein the AAA client is further configured to send the accounting stop packet from the AAA client application to the second AAA accounting peer in response to receiving the accounting stop packet. ### Claim 13 (depends on 12) The computing device of claim 12, wherein the accounting start packet is a copy of the accounting stop packet received from the AAA client application. ### Claim 14 (depends on 11) The computing device of claim 11, wherein the AAA client is further configured to determine whether the first AAA accounting peer is available in response to receiving the accounting update or accounting stop packet. ### Claim 15 (depends on 11) The computing device of claim 11, wherein an AAA protocol utilized by the first AAA accounting peer, second AAA accounting peer, AAA protocol stack and AAA client application is Diameter. ### Claim 16 A control plane device in a network including a plurality of data plane devices, the control plane device in communication with the plurality of data plane devices and configured to implement a method for migrating a subscriber session from a first authentication, authorization and accounting (AAA) accounting peer to a second AAA accounting peer, where the first AAA accounting peer is stateful, the control plane device comprising: a non-transitory computer readable medium having stored therein a AAA client; and a processor coupled to the non-transitory computer readable medium configured to execute the AAA client, the AAA client configured to receive an accounting start packet from an AAA client application, to forward the accounting start packet to the first AAA accounting peer, to receive an accounting update or accounting stop packet from the AAA client application, to select the second AAA accounting peer from the available accounting peers, in response to determination of a connection failure with the first AAA accounting peer, to determine whether the received packet is the accounting update packet or the accounting stop packet, to re-mark or re-label the accounting update packet, from the AAA client application, as an accounting start packet; and to send the re-marked or re-labeled accounting start packet from the AAA client application to the second AAA accounting peer. ### Claim 17 (depends on 16) The control plane device of claim 16, wherein the AAA client is further configured to send the accounting stop packet from the AAA client application to the second AAA accounting peer in response to receiving the accounting stop packet. ### Claim 18 (depends on 17) The control plane device of claim 17, wherein the accounting start packet is a copy of the accounting stop packet received from the AAA client application. ### Claim 19 (depends on 16) The control plane device of claim 16, wherein the AAA client is further configured to determine whether the first AAA accounting peer is available in response to receiving the accounting update or accounting stop packet. ### Claim 20 (depends on 16) The control plane device of claim 16, wherein an AAA protocol utilized by the first AAA accounting peer, second AAA accounting peer, AAA protocol stack and AAA client application is Diameter.