DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statement filed 09/06/2023 fails to comply with the provisions of 37 CFR 1.97, 1.98 and MPEP § 609 because International Search Report and Written Opinion issued in PCT/CN2020/092710, dated August 6, 2020, is not provided in English. It has been placed in the application file, but the information referred to therein has not been considered as to the merits. Applicant is advised that the date of any re-submission of any item of information contained in this information disclosure statement or the submission of any missing element(s) will be the date of submission for purposes of determining compliance with the requirements based on the time of filing the statement, including all certification requirements for statements under 37 CFR 1.97(e). See MPEP § 609.05(a).
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1 – 20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1 - 20 of U.S. Patent No. 11,784,915 in view of Nainar et al. (Pub. No.: US 2019/0372877; hereinafter Nainar).
Claim 1 of U.S. Patent No. 11,784,915 discloses all the claimed features of claim 1 of Application No. 18/461,597 except for the claimed features of: regarding claim 1, the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device.
Regarding claim 1, Nainar discloses the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device (see Fig. 1, routers R3 and R4 are downstream to router R2).
It would have been obvious to one ordinary skilled in the art before the effective filing date of the claimed invention to modify the invention of U.S. Patent No. 11,784,915, and have the features, as taught by Nainar, where a network controller may analyze the packet replication information to generate, if necessary, one or more controls that alter a configuration of one or more network elements in the network to improve performance of the network, as discussed by Nainar (para. 0039).
Claim 9 of U.S. Patent No. 11,784,915 discloses all the claimed features of claim 9 of Application No. 18/461,597 except for the claimed features of: regarding claim 9, the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device.
Regarding claim 9, Nainar discloses the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device (see Fig. 1, routers R3 and R4 are downstream to router R2).
It would have been obvious to one ordinary skilled in the art before the effective filing date of the claimed invention to modify the invention of U.S. Patent No. 11,784,915, and have the features, as taught by Nainar, where a network controller may analyze the packet replication information to generate, if necessary, one or more controls that alter a configuration of one or more network elements in the network to improve performance of the network, as discussed by Nainar (para. 0039).
Claim 17 of U.S. Patent No. 11,784,915 discloses all the claimed features of claim 17 of Application No. 18/461,597 except for the claimed features of: regarding claim 17, the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device.
Regarding claim 17, Nainar discloses the second network device being a downstream device of the first network device, and the third network device being a downstream device of the first network device (see Fig. 1, routers R3 and R4 are downstream to router R2).
It would have been obvious to one ordinary skilled in the art before the effective filing date of the claimed invention to modify the invention of U.S. Patent No. 11,784,915, and have the features, as taught by Nainar, where a network controller may analyze the packet replication information to generate, if necessary, one or more controls that alter a configuration of one or more network elements in the network to improve performance of the network, as discussed by Nainar (para. 0039).
The mappings of the conflicting claims are shown in the table below.
Claims from Application No. 18/461,597
Claims from U.S. Patent No. 11,784,915
1. A multicast packet processing method, comprising: obtaining, by a first network device, a packet comprising a payload; obtaining, by the first network device, a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier, identifying a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device, the second network device being a downstream device of the first network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the third network device being a downstream device of the first network device, the first in-situ flow information telemetry information indicates performing in-situ flow information telemetry; and sending, by the first network device, the first multicast packet to the second network device via the first forwarding path, and sending the second multicast packet to the third network device via the second forwarding path.
2. The method according to claim 1, wherein the obtaining, by the first network device, a first multicast packet and a second multicast packet based on the packet comprises: obtaining, by the first network device, the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information, the first level information identifies a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier, identifying a multicast data flow to which the first multicast packet belongs; and obtaining, by the first network device, the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information, identifying a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier, identifying a flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
3. The method according to claim 2, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
4. The method according to claim 2, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information identifying a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a downstream device of the fourth network device, the third level information comprises a third multicast flow identifier identifying a flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
5. The method according to claim 1, wherein the obtaining, by the first network device, a first multicast packet and a second multicast packet based on the packet specifically comprises: obtaining, by the first network device, the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first series information and a first multicast flow identifier, the first series information identifies obtaining the first multicast packet and the second multicast packet based on the packet, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and obtaining, by the first network device, the second multi-level flow identifier, wherein the second multi-level flow identifier comprises the first series information and a second multicast flow identifier identifying a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
6. The method according to claim 5, wherein the first multi-level flow identifier and the second multi-level flow identifier further comprise a first device identifier identifying the first network device.
7. The method according to claim 5, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises second series information and a third multicast flow identifier, and the third multicast flow identifier identifies a multicast data flow to which the third multicast packet belongs; and the obtaining, by the first network device, a first multicast packet and a second multicast packet based on the packet further comprises: obtaining, by the first network device, the first series information based on the second series information of the third multi-level flow identifier of the packet.
8. The method according to claim 1, further comprising: sending, by the first network device, a first message and a second message to a network management device, wherein the first message carries the first multi-level flow identifier of the first multicast packet and first information, the first information is determined by the first network device based on the first in-situ flow information telemetry information in the first multicast packet, the second message carries the second multi-level flow identifier of the second multicast packet and second information, and the second information is determined by the first network device based on the first in-situ flow information telemetry information in the second multicast packet.
9. A first network device comprising: at least one processor; a memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the first network device to: obtain a packet comprising a payload; obtain a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier identifying a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device, the second network device being a downstream device of the first network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the third network device being a downstream device of the first network device, the first in-situ flow information telemetry information indicates performing in-situ flow information telemetry; and send the first multicast packet to the second network device via the first forwarding path, and send the second multicast packet to the third network device via the second forwarding path.
10. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, further cause the first network device to: obtain the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information identifying a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier identifying a multicast data flow to which the first multicast packet belongs; and obtain the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information identifying a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier identifying a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
11. The first network device according to claim 10, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
12. The first network device according to claim 10, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information identifying a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a downstream device of the fourth network device, the third level information comprises a third multicast flow identifier identifying a multicast data flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
13. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, cause the first network device to: obtain the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first series information and a first multicast flow identifier, the first series information identifies obtaining the first multicast packet and the second multicast packet based on the packet, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and obtain the second multi-level flow identifier, wherein the second multi-level flow identifier comprises the first series information and a second multicast flow identifier identifying a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
14. The first network device according to claim 13, wherein the first multi-level flow identifier and the second multi-level flow identifier further comprise a first device identifier identifying the first network device.
15. The first network device according to claim 13, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises second series information and a third multicast flow identifier, and the third multicast flow identifier identifies a multicast data flow to which the third multicast packet belongs; and wherein the obtaining of the first multicast packet and the second multicast packet based on the packet further comprises: obtaining the first series information based on the second series information of the third multi-level flow identifier of the packet.
16. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, further cause the first network device to: send a first message and a second message to a network management device, wherein the first message carries the first multi-level flow identifier of the first multicast packet and first information, the first information is determined based on the first in-situ flow information telemetry information in the first multicast packet, the second message carries the second multi-level flow identifier of the second multicast packet and second information, and the second information is determined based on the first in-situ flow information telemetry information in the second multicast packet.
17. A non-transitory storage medium storing information comprising instructions that, when executed by at least one processor, control the at least one processor to perform operations comprising: obtaining a packet comprising a payload; obtaining a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier identifying a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device, the second network device being a downstream device of the first network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the third network device being a downstream device of the first network device, the first in-situ flow information telemetry information indicates performing in-situ flow information telemetry; and sending the first multicast packet to the second network device via the first forwarding path, and sending the second multicast packet to the third network device via the second forwarding path.
18. The non-transitory storage medium according to claim 17, wherein the obtaining a first multicast packet and a second multicast packet based on the packet comprises: obtaining the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information identifying a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier identifying a multicast data flow to which the first multicast packet belongs; and obtaining the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information identifying a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier identifying a flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
19. The non-transitory storage medium according to claim 18, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
20. The non-transitory storage medium according to claim 18, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information identifying a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a downstream device of the fourth network device, the third level information comprises a third multicast flow identifier identifying a flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
1. A multicast packet processing method, comprising: obtaining, by a first network device, a packet comprising a payload; generating, by the first network device, a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier, the first multi-level flow identifier identifies a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the first in-situ flow information telemetry information indicates the second network device to perform in-situ flow information telemetry on a flow to which the first multicast packet comprising the first multi-level flow identifier belongs, the first in-situ flow information telemetry information indicates the third network device to perform in-situ flow information telemetry on a flow to which the second multicast packet comprising the second multi-level flow identifier belongs, and the second network device and the third network device are next-hop network devices of the first network device; and sending, by the first network device, the first multicast packet to the second network device through the first forwarding path, and sending the second multicast packet to the third network device through the second forwarding path.
2. The method according to claim 1, wherein the generating, by the first network device, a first multicast packet and a second multicast packet based on the packet comprises: generating, by the first network device, the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information, the first level information identifies a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and generating, by the first network device, the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information, the second level information identifies a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier, the second multicast flow identifier identifies a flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
3. The method according to claim 2, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
4. The method according to claim 2, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information, the third level information identifies a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a next-hop network device of the fourth network device, the third level information comprises a third multicast flow identifier, the third multicast flow identifier identifies a flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
5. The method according to claim 1, wherein the generating, by the first network device, a first multicast packet and a second multicast packet based on the packet specifically comprises: generating, by the first network device, the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first series information and a first multicast flow identifier, the first series information identifies that the first network device generates the first multicast packet and the second multicast packet based on the packet, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and generating, by the first network device, the second multi-level flow identifier, wherein the second multi-level flow identifier comprises the first series information and a second multicast flow identifier, the second multicast flow identifier identifies a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
6. The method according to claim 5, wherein the first multi-level flow identifier and the second multi-level flow identifier further comprise a first device identifier identifying the first network device.
7. The method according to claim 5, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises second series information and a third multicast flow identifier, and the third multicast flow identifier identifies a multicast data flow to which the third multicast packet belongs; and the generating, by the first network device, a first multicast packet and a second multicast packet based on the packet further comprises: generating, by the first network device, the first series information based on the second series information of the third multi-level flow identifier of the packet.
8. The method according to claim 1, further comprising: sending, by the first network device, a first message and a second message to a network management device, wherein the first message carries the first multi-level flow identifier of the first multicast packet and first information, the first information is determined by the first network device based on the first in-situ flow information telemetry information in the first multicast packet, the second message carries the second multi-level flow identifier of the second multicast packet and second information, and the second information is determined by the first network device based on the first in-situ flow information telemetry information in the second multicast packet.
9. A first network device, wherein the first network device comprises: at least on processor; a memory coupled to the one processor and storing instructions that, when executed by the at least one processor, cause the first network device to: obtain a packet comprising a payload; generate a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier, the first multi-level flow identifier identifies a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the first in-situ flow information telemetry information indicates the second network device to perform in-situ flow information telemetry on a flow to which the first multicast packet comprising the first multi-level flow identifier belongs, the first in-situ flow information telemetry information indicates the third network device to perform in-situ flow information telemetry on a flow to which the second multicast packet comprising the second multi-level flow identifier belongs, and the second network device and the third network device are next-hop network devices of the first network device; and send the first multicast packet to the second network device through the first forwarding path, and send the second multicast packet to the third network device through the second forwarding path.
10. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, further cause the first network device to: generate the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information, the first level information identifies a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and generate the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information, the second level information identifies a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier, the second multicast flow identifier identifies a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
11. The first network device according to claim 10, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
12. The first network device according to claim 10, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information, the third level information identifies a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a next-hop network device of the fourth network device, the third level information comprises a third multicast flow identifier, the third multicast flow identifier identifies a multicast data flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
13. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, cause the first network device to: generate the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first series information and a first multicast flow identifier, the first series information identifies that the first network device generates the first multicast packet and the second multicast packet based on the packet, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and generate the second multi-level flow identifier, wherein the second multi-level flow identifier comprises the first series information and a second multicast flow identifier, the second multicast flow identifier identifies a multicast data flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
14. The first network device according to claim 13, wherein the first multi-level flow identifier and the second multi-level flow identifier further comprise a first device identifier identifying the first network device.
15. The first network device according to claim 13, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises second series information and a third multicast flow identifier, and the third multicast flow identifier identifies a multicast data flow to which the third multicast packet belongs; and wherein the generation of the first multicast packet and the second multicast packet based on the packet further comprises: generating the first series information based on the second series information of the third multi-level flow identifier of the packet.
16. The first network device according to claim 9, wherein the instructions, when executed by the at least one processor, further cause the first network device to: send a first message and a second message to a network management device, wherein the first message carries the first multi-level flow identifier of the first multicast packet and first information, the first information is determined by the first network device based on the first in-situ flow information telemetry information in the first multicast packet, the second message carries the second multi-level flow identifier of the second multicast packet and second information, and the second information is determined by the first network device based on the first in-situ flow information telemetry information in the second multicast packet.
17. A non-transitory storage medium storing information comprising instructions that, when executed by at least one processor, control the at least one processor to perform operations comprising: obtaining a packet comprising a payload; generating a first multicast packet and a second multicast packet based on the packet, wherein the first multicast packet comprises a first multicast packet header and the payload, the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier, the first multi-level flow identifier identifies a first forwarding path of the payload, the first forwarding path comprises a path from a first network device to a second network device, the second multicast packet comprises a second multicast packet header and the payload, the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device to a third network device, the first in-situ flow information telemetry information indicates the second network device to perform in-situ flow information telemetry on a flow to which the first multicast packet comprising the first multi-level flow identifier belongs, the first in-situ flow information telemetry information indicates the third network device to perform in-situ flow information telemetry on a flow to which the second multicast packet comprising the second multi-level flow identifier belongs, and the second network device and the third network device are next-hop network devices of the first network device; and sending the first multicast packet to the second network device through the first forwarding path, and sending the second multicast packet to the third network device through the second forwarding path.
18. The non-transitory storage medium according to claim 17, wherein the generating a first multicast packet and a second multicast packet based on the packet comprises: generating the first multi-level flow identifier, wherein the first multi-level flow identifier comprises first level information, the first level information identifies a path that corresponds to the payload and that is from the first network device to the second network device, the first level information comprises a first multicast flow identifier, and the first multicast flow identifier identifies a multicast data flow to which the first multicast packet belongs; and generating the second multi-level flow identifier, wherein the second multi-level flow identifier comprises second level information, the second level information identifies a path that corresponds to the payload and that is from the first network device to the third network device, the second level information comprises a second multicast flow identifier, the second multicast flow identifier identifies a flow to which the second multicast packet belongs, and the second multicast flow identifier is different from the first multicast flow identifier.
19. The non-transitory storage medium according to claim 18, wherein the first level information and the second level information further comprise a first device identifier identifying the first network device.
20. The non-transitory storage medium according to claim 18, wherein the packet is a third multicast packet, the third multicast packet comprises a third multicast packet header and the payload, the third multicast packet header comprises the first in-situ flow information telemetry information and a third multi-level flow identifier, the third multi-level flow identifier comprises third level information, the third level information identifies a path that corresponds to the payload and that is from a fourth network device to a fifth network device, the fifth network device is a next-hop network device of the fourth network device, the third level information comprises a third multicast flow identifier, the third multicast flow identifier identifies a flow to which the third multicast packet belongs, and the first multi-level flow identifier and the second multi-level flow identifier each further comprises the third level information.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
Claims 1, 9 and 17 are rejected under 35 U.S.C. 112(a) failing to comply with the written description requirement. The Specification dated 09/06/2023 discloses the first network device generates a first multicast packet and a second multicast packet based on the packet (para. 0005). Figure 3 shows multicast replication is performed on the data packet on an egress interface of the head node 31 (for example: first network device). A first data packet and a second data packet that are generated through replication respectively flow out through egress interfaces B and C of the head node 31. The Specification does not describe “obtaining, by the first network device, a first multicast packet and a second multicast packet based on the packet” as recited in claim 1. Claims 9 and 17 contain the similar subject matter as claim 1 and they are rejected for the same reasons.
Allowable Subject Matter
According to a prior art search based on the claimed features, Nainar et al. (Pub. No.: US 2019/0372877) disclose in-situ OAM for multicast path and to apply the In-Situ OAM techniques in the multicast data path and unicast paths that involve packet replication as well. For example, In-Situ OAM telemetry data collection can be useful for collecting complete path information from a headend to each leaf node, and for performance measurements from headend to leaf node(s). Presented herein are techniques to extend the applicability of In-Situ OAM for multicast data paths or other unicast data paths that involve a packet replication operation (para. 0011). For multicast traffic, a packet comes in on one interface of a network device but it is replicated and goes out on multiple interfaces of the network device, if that network device is a replicator. It is desirable to be able to identify the exact set of nodes that the particular multicast node travels, with additional details about the underlay network and overlay network. Any replicating node will replicate the IOAM data, include itself as a replicator and add additional path information. Capturing the data at any leaf node can be helpful to understand the exact path and the replication nodes along the path (para. 0012).
Jeuk et al. (Pub. No.: US 2019/0306056) disclose “In-situ” Operations, Administration, and Maintenance (OAM) refers to the concept of directly encoding telemetry information within the data packet as the packets traverse the network or telemetry domain. Mechanisms which add tracing or other types of telemetry information to the regular data traffic, sometimes also referred to as “in-band” OAM, can complement active, probe-based mechanisms such as ping or traceroute, which are sometimes considered as “out-of-band” because the messages are transported independently from regular data traffic. In relation to “active” or “passive” OAM, “in-situ” OAM can be considered a hybrid OAM type. While no extra packets are sent, in-situ OAM (iOAM) adds information to the packets and therefore cannot be considered passive (para. 0003).
The cited prior arts, taken alone or in combination, do not disclose the claimed features of “…the first multicast packet header comprises first in-situ flow information telemetry information and a first multi-level flow identifier, the first multi-level flow identifier identifies a first forwarding path of the payload, the first forwarding path comprises a path from the first network device to a second network device…the second multicast packet header comprises a second multi-level flow identifier and the first in-situ flow information telemetry information, the second multi-level flow identifier identifies a second forwarding path of the payload, the second forwarding path comprises a path from the first network device” as recited in claims 1, 9 and 17 when considering each claim individually as a whole.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Anh Ngoc M Nguyen whose telephone number is (571) 270-5139. The examiner can normally be reached on Monday to Friday, from 7:30 am to 4:00 pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kwang Bin Yao can be reached on ((571) 272-3182. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice .
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/ANH NGOC M NGUYEN/Primary Examiner, Art Unit 2473