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 (IDS) submitted on October 21, 2025 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement id being considered by the examiner.
Priority
Acknowledgment is made of applicant’s claim for foreign priority under 35 U.S.C. 119 (a)-(d). The certified copies have been filed in parent Korean Applications No. 10-2022-0077879, 10-2022-0080070, and 10-2022-0082005 filed on June 24, 2022, June 29, 2022, and July 4, 2022, respectively.
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-15 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims of the Applicant’s U.S. Patent Serial No. 12490313, as reasoned below. Although the claims at issue are not identical, they are not patentably distinct from each other because of the following comparison and reasoning
(a) Claim 1 of the Instant Application is rejected in view of Claims 1, 3, 4, 5 and 6 of U.S. 12490313;
(b) Claim 2 of the Instant Application is rejected in view of Claim 2 of U.S. 12490313;
(c) Claim 3 of the Instant Application is rejected in view of Claim 3 of U.S. 12490313;
(d) Claim 4 of the Instant Application is rejected in view of Claim 4 of U.S. 12490313;
(e) Claim 5 of the Instant Application is rejected in view of Claim 5 of U.S. 12490313;
(f) Claim 6 of the Instant Application is rejected in view of Claim 7 of U.S. 12490313;
(g) Claim 7 of the Instant Application is rejected in view of Claim 8 of U.S. 12490313;
(h) Claim 8 of the Instant Application is rejected in view of Claim 9 of U.S. 12490313;
(i) Claim 9 of the Instant Application is rejected in view of Claim 10 of U.S. 12490313;
(j) Claim 10 of the Instant Application is rejected in view of Claim 11 of U.S. 12490313;
(k) Claim 11 of the Instant Application is rejected in view of Claims 12, 13, 15, 16 and 17 of U.S. 12490313;
(l) Claim 12 of the Instant Application is rejected in view of Claim 13 of U.S. 12490313;
(m) Claim 13 of the Instant Application is rejected in view of Claim 14 of U.S. 12490313;
(n) Claim 14 of the Instant Application is rejected in view of Claim 15 of U.S. 12490313;
(o) Claim 15 of the Instant Application is rejected in view of Claim 16 of U.S. 12490313;
(p) Claim 16 of the Instant Application is rejected in view of Claim 18 of U.S. 12490313;
(q) Claim 17 of the Instant Application is rejected in view of Claim 19 of U.S. 12490313;
(r) Claim 18 of the Instant Application is rejected in view of Claim 20 of U.S. 12490313;
(s) Claim 19 of the Instant Application is rejected in view of Claim 21 of U.S. 12490313;
(t) Claim 20 of the Instant Application is rejected in view of Claim 22 of U.S. 12490313;
U.S. Patent 12490313
Instant Application
Claim 1.
A multi-link device (MLD) comprising a plurality of stations (STAs) operating on a plurality of links, wherein a processor is configured to: receive a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element including at least one neighbor AP information field related to the at least one other AP, wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield, ii) a TBTT information length subfield, and iii) a TBTT information set field including one or more TBTT information fields…
Claim 3.
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is ignored when a value of the TBTT information length subfield is equal to or less than a first threshold value…
Claim 4.
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a first threshold value…
Claim 5.
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a second threshold value…
Claim 6.
The MLD of claim 1, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a third threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) the TBTT information type subfield is set to ‘1’ and ii) a value of the TBTT information length subfield is greater than the third threshold value.
Claim 1.
A multi-link device (MLD) comprising a plurality of stations (STAs) operating on a plurality of links, wherein a processor is configured to: receive a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element including at least one neighbor AP information field related to the at least one other AP, wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield, ii) a TBTT information length subfield, and iii) a TBTT information set field including one or more TBTT information fields,
wherein, when the TBTT information field type subfield is set to ‘0’, the processor is configured to perform one of the following steps, based on the TBTT information length subfield:
(i) ignore each of the one or more TBTT information fields;
(ii) process a number of octets of each of the one or more TBTT information fields up to a first threshold value;
or (iii) process a number of octets of each of the one or more TBTT information fields up to a second threshold value,
and wherein, when the TBTT information field type subfield is set to ‘1’, and based on a value of the TBTT information length subfield being greater than a third threshold value, the processor is configured to process a number of octets of each of the one or more TBTT information fields up to the third threshold value and ignore remaining octets of each of the one or more TBTT information fields above the third threshold value.
Claim 2
The MLD of claim 1, wherein the TBTT information field type subfield is used together with the TBTT information length subfield to identify a format of the one or more TBTT information fields.
Claim 2
The MLD of claim 1, wherein the TBTT information field type subfield is used together with the TBTT information length subfield to identify a format of the one or more TBTT information fields.
Claim 3
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is ignored when a value of the TBTT information length subfield is equal to or less than a first threshold value.
Claim 3
The MLD of claim 1, wherein, when the TBTT information field type subfield is set to '0', the processor is configured to ignore each of the one or more TBTT information fields when a value of the TBTT information length subfield is equal to or less than the first threshold value.
Claim 4
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a first threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) a value of the TBTT information length subfield is greater than the first threshold value…
Claim 4
The MLD of claim 1, wherein, when the TBTT information field type subfield is set to '0', the processor is configured to process a number of octets of each of the one or more TBTT information fields up to the first threshold value and to ignore remaining octets of each of the one or more TBTT information fields when a value of the TBTT information length subfield is greater than the first threshold value.
Claim 5
The MLD of claim 1, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a second threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) a value of the TBTT information length subfield is greater than the second threshold value…
Claim 5
The MLD of claim 1, wherein, when the TBTT information field type subfield is set to '0', the processor is configured to process a number of octets of each of the one or more TBTT information fields up to the second threshold value and to ignore remaining octets of each of the one or more TBTT information fields when a value of the TBTT information length subfield is greater than the second threshold value.
Claim 7
The MLD of claim 6, wherein the third threshold value is ‘3’.
Claim 6
The MLD of claim 1, wherein the third threshold value is '3'.
Claim 8
The MLD of claim 1, wherein each of the one or more TBTT information fields includes an MLD parameters subfield when i) the TBTT information type subfield is set to ‘1’ and ii) a value of the TBTT information length subfield is set to a specific value.
Claim 7
The MLD of claim 1, wherein each of the one or more TBTT information fields includes an MLD parameters subfield when i) the TBTT information field type subfield is set to '1' and ii) a value of the TBTT information length subfield is set to a specific value.
Claim 9
The MLD of claim 1, wherein each of the one or more TBTT information fields includes a neighbor AP TBTT offset subfield, and wherein the neighbor AP TBTT offset subfield indicates an offset between a TBTT for the AP to transmit a beacon frame and a TBTT for the at least one other AP to transmit a beacon frame.
Claim 8
The MLD of claim 1, wherein each of the one or more TBTT information fields includes a neighbor AP TBTT offset subfield, and wherein the neighbor AP TBTT offset subfield indicates an offset between a TBTT for the AP to transmit a beacon frame and a TBTT for the at least one other AP to transmit a beacon frame.
Claim 10
The MLD of claim 9, wherein an offset value indicated by the neighbor AP TBTT offset subfield is set to a value excluding a predetermined value related to Unknown.
Claim 9
The MLD of claim 8, wherein an offset value indicated by the neighbor AP TBTT offset subfield is set to a value excluding a predetermined value related to Unknown.
Claim 11
The MLD of claim 10, wherein the predetermined value is “255”.
Claim 10
The MLD of claim 9, wherein the predetermined value is "255".
Claim 12
A method performed by a multi-link device (MLD) comprising a plurality of stations (STAs) operating on a plurality of links in a wireless communication system, the method comprising: receiving a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element including at least one neighbor AP information field related to the at least one other AP, wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield, ii) a TBTT information length subfield, and iii) a TBTT information set field including one or more TBTT information fields…
Claim 13
The method of claim 11, wherein, when the TBTT information field type subfield is set to '0', the method comprises ignoring each of the one or more TBTT information field…
Claim 15.
The method of claim 12, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a first threshold value…
Claim 16.
The method of claim 12, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a second threshold value…
Claim 17.
The method of claim 12, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a third threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) the TBTT information type subfield is set to ‘1’ and ii) a value of the TBTT information length subfield is greater than the third threshold value.
Claim 11
A method performed by a multi-link device (MLD) comprising a plurality of stations (STAs) operating on a plurality of links in a wireless communication system, the method comprising: receiving a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element including at least one neighbor AP information field related to the at least one other AP, and wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield, ii) a TBTT information length subfield, and iii) a TBTT information set field including one or more TBTT information fields;
when the TBTT information field type subfield is set to ‘0’, and based on the TBTT information length subfield, performing one of the following steps:
(i) ignoring each of the one or more TBTT information fields;
(ii) processing a number of octets of each of the one or more TBTT information fields up to a first threshold value;
or (iii) processing a number of octets of each of the one or more TBTT information fields up to a second threshold value,
and when the TBTT information field type subfield is set to ‘1’, and based on a value of the TBTT information length subfield being greater than a third threshold value, processing a number of octets of each of the one or more TBTT information fields up to the third threshold value and ignoring remaining octets of each of the one or more TBTT information fields above the third threshold value.
Claim 13
The method of claim 12, wherein the TBTT information field type subfield is used together with the TBTT information length subfield to identify a format of the one or more TBTT information fields.
Claim 12
The method of claim 11, wherein the TBTT information field type subfield is used together with the TBTT information length subfield to identify a format of the one or more TBTT information fields.
Claim 14
The method of claim 12, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is ignored when a value of the TBTT information length subfield is equal to or less than a first threshold value.
Claim 13
The method of claim 11, wherein, when the TBTT information field type subfield is set to '0', the method comprises ignoring each of the one or more TBTT information fields when a value of the TBTT information length subfield is equal to or less than the first threshold value.
Claim 15
The method of claim 12, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a first threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) a value of the TBTT information length subfield is greater than a first threshold value…
Claim 14
The method of claim 11, wherein, when the TBTT information field type subfield is set to '0', the method comprises processing each of the one or more TBTT information fields up to a number of octets corresponding to the first threshold value, and ignoring remaining octets of each of the one or more TBTT information fields when i) a value of the TBTT information length subfield is greater than the first threshold value.
Claim 16
The method of claim 12, when the TBTT information type subfield is set to ‘0’, wherein each of the one or more TBTT information fields is processed up to octets corresponding to a second threshold value, and remaining octets of each of the one or more TBTT information fields are ignored when i) a value of the TBTT information length subfield is greater than the second threshold value…
Claim 15
The method of claim 11, wherein, when the TBTT information field type subfield is set to '0', the method comprises processing each of the one or more TBTT information fields up to a number of octets corresponding to the second threshold value, and ignoring remaining octets of each of the one or more TBTT information fields when i) a value of the TBTT information length subfield is greater than the second threshold value.
Claim 18
The method of claim 17, wherein the third threshold value is ‘3’.
Claim 16
The method of claim 11, wherein the third threshold value is '3'.
Claim 19
The method of claim 12, wherein each of the above one or more TBTT information fields includes an MLD parameters subfield when i) the TBTT information type subfield is set to ‘1’ and ii) a value of the TBTT information length subfield is set to a specific value.
Claim 17
The method of claim 11, wherein each of the one or more TBTT information fields includes an MLD parameters subfield when i) the TBTT information field type subfield is set to '1' and ii) a value of the TBTT information length subfield is set to a specific value.
Claim 20
The method of claim 12, wherein each of the one or more TBTT information fields includes a neighbor AP TBTT offset subfield, and wherein the neighbor AP TBTT offset subfield indicates an offset between a TBTT for the AP to transmit a beacon frame and a TBTT for the at least one other AP to transmit a beacon frame.
Claim 18
The method of claim 11, wherein each of the one or more TBTT information fields includes a neighbor AP TBTT offset subfield, and wherein the neighbor AP TBTT offset subfield indicates an offset between a TBTT for the AP to transmit a beacon frame and a TBTT for the at least one other AP to transmit a beacon frame.
Claim 21
The method of claim 20, wherein an offset value indicated by the neighbor AP TBTT offset subfield is set to a value excluding a predetermined value related to Unknown.
Claim 19
The method of claim 18, wherein an offset value indicated by the neighbor AP TBTT offset subfield is set to a value excluding a predetermined value related to Unknown.
Claim 22
The method of claim 21, wherein the predetermined value is “255”.
Claim 20
The method of claim 19, wherein the predetermined value is "255".
Instant Application is taught by the claims of the US Patent 12490313.
Instant Application independent claim 1 recites a multi-link device (MLD), comprising a plurality of stations (STAs) operating on a plurality of links, receiving a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element including at least one neighbor AP information field related to the at least one other AP, wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield, ii) a TBTT information length subfield, and iii) a TBTT information set field including one or more TBTT information fields. The US Patent recites each of these elements in its claim 1. Further, Instant Application claim 1 recites when the TBTT information field type subfield is set to ‘0’, then based on the TBTT information length subfield, one or more of the following actions are performed: each of the one or more TBTT information fields are ignored (which is recited in claim 3 of the US Patent), a number of octets of each of the one or more TBTT information fields are processed up to a first threshold value (which is recited in claim 4 of the US Patent), and/or a number of octets of each of the one or more TBTT information fields are processed up to a second threshold value (which is recited in claim 5 of the US Patent). Further, claim 1 of Instant Application recites when the TBTT information field type subfield is set to ‘1’, and based on a value of the TBTT information length subfield being greater than a third threshold value, a number of octets of each of the one or more TBTT information fields are processed up to the third threshold value and ignore remaining octets of each of the one or more TBTT information fields above the third threshold value (which is recited in claim 6 of the US Patent).
Dependent claims 2-10 are mirrored in claims 2-5 and 7-11 of the US Patent.
Independent claim 11 of the Instant Application is directed to a method that performs operations which are functionally similar to those performed by the device(s) of claim 1. Therefore, the reasoning used in the examination of claim 1 applies to claim 11.
Claims 12-22 of the US Patent are functionally similar to its claims 1-11, respectively. Therefore, similar reasoning may be applied to claims 12-16 and 18-22 teaching the claims 12-22 of the Instant Application, as seen in the table above.
Allowable Subject Matter
Claims 1-20 are objected to as containing allowable subject matter, and would be allowable if the double patenting rejection is overcome.
The following is a statement of reasons for the indication of allowable subject matter:
Regarding independent Claim 1, directed to a multi-link device (MLD) comprising a plurality of stations (STAs) operating on a plurality of links, and independent Claim 11, directed to a method performed by a MLD, comprising operations that are functionally similar to those performed by the MLD of claim 1:
Prior art of record discloses receiving a management frame from an access point (AP) in an AP MLD comprising the AP and at least one other AP, wherein the management frame includes a reduced neighbor report (RNR) element, including at least one neighbor AP information field related to the at least one AP. Such teachings may be seen in Patil et al, U.S. Patent Application Publication No. 20230053972 (hereinafter Patil: e.g., ¶ [0052], A single AP 102 and an associated set of STAs 104 may be referred to as a basic service set (BSS), which is managed by the respective AP 102; e.g., ¶ [0089] [0090], In the example of FIG. 7A, the NSTR softAP MLD transmits, on only the primary link, a first frame that includes the complete profile of the primary link and indicates the complete profile of the non-primary link… In some implementations, the primary link may be configured as a complete BSS, and the non-primary link may be configured as a pseudo-BSS that shares one or more capabilities and operation parameters with the primary link; e.g., ¶ [0091], The first frame may be any suitable frame that can carry or indicate the complete profiles of both the primary and non-primary links; e.g., ¶ [0159], FIG. 10A shows an example management frame 1000A usable for wireless communications that supports NSTR softAP MLDs; e.g., ¶ [0161], FIG. 10B shows another example management frame usable for multi-link communications with an NSTR softAP MLD [non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device] according to some implementations; e.g., ¶ [0163], FIG. 11A shows an example RNR Element 1100 usable for multi-link communications according to some implementations. In some implementations, the RNR element 1100 may be an example implementation of the RNR Element 1020 of the example management frames 1000A and 1000B described with reference to FIGS. 10A and 10B, respectively; e.g., ¶ [0093], The body of the first frame may also include a Reduced Neighbor Report (RNR) Element carrying a Neighbor AP Information field associated with the non-primary link. The Neighbor AP Information field may carry a target beacon transmission time (TBTT) Information field consisting of a basic service set identification (BSSID) and one or more MLD parameters of the non-primary link),
Patil, above, further discloses wherein each of the at least one neighbor AP information field includes i) a target beacon transmission time (TBTT) information field type subfield (e.g., ¶ [0093], Neighbor AP Information field may carry a target beacon transmission time (TBTT) Information field; e.g., FIG. 11A, B; ¶ [0167], FIG. 11B shows an example TBTT Information Header 1120 according to some implementations. In some instances, the TBTT Information Header 1120 may be an example implementation of the TBTT Information Header 1111 of FIG. 11A. As shown, the TBTT Information Header 1120 includes a TBTT Information Field Type subfield 1121), ii) a TBTT information length subfield (e.g., FIG. 11A, B; ¶ [0167], BTT Information Header 1120 includes… a TBTT Information Length subfield 112), and iii) a TBTT information set field including one or more TBTT information fields (e.g., FIG. 11A, ¶ [0165], the Neighbor AP Information field 1106 includes… TBTT Information Set field 1114), and processing each of the one or more TBTT information fields (e.g., ¶ [0096], The STA receives the first frame transmitted by the NSTR softAP MLD on the primary link, and may parse the first frame to obtain the complete profiles of the primary and non-primary links [For implementations in which the STA is a multi-radio device having STR capabilities]), wherein a length of each of the one or more TBTT information subfields is indicated by the TBTT information length subfield (e.g., ¶ [0168], The TBTT Information Length subfield 1125 indicates the length of each TBTT Information field included in the TBTT Information Set field of the Neighbor AP Information field), one or more TBTT information subfields varying in a number of octets (e.g.,¶ [0093], The body of the first frame may also include a Reduced Neighbor Report (RNR) Element carrying a Neighbor AP Information field [which] may carry a target beacon transmission time (TBTT) Information field consisting of a basic service set identification (BSSID) and one or more MLD parameters… TBTT Information field associated with the non-primary link consists of a 6-octet BSSID field and a 3-octet MLD parameters field, and has a length of 9 octets [i.e., establishing that each field and subfield are associated with an octet length]), and that the TBTT information field type subfield and the TBTT information length subfield are included in a corresponding neighboring AP information field among the at least one neighboring AP information field (e.g., FIG. 11B, ¶ [0167], TBTT Information Header 1120 includes a TBTT Information Field Type subfield 1121, a Filtered Neighbor AP subfield 1122, a reserved subfield 1123, a TBTT Information Count subfield 1124, and a TBTT Information Length subfield 1125. The TBTT Information Field Type subfield 1121 carries a value indicating the type or format of the TBTT Information field. In some implementations, the value of the TBTT Information Field Type subfield 1121 may be set to 1 or a reserved value to indicate that the TBTT Information field is of a new type or format associated with an NSTR device).
Patil further discloses informative details, depending on values for TBTT information field type and TBTT information length subfield, and to ignore one or more TBTT information fields under certain circumstances (e.g., ¶ [0094] In some implementations, the Neighbor AP Information field may include a TBTT Information Field Type set to a value indicating that the Neighbor AP Information field carries only information associated with the non-primary link. In some instances, the Neighbor AP Information field may be of a new or undefined type, and the TBTT Information Field Type may be set to 1 or a reserved value to indicate the new or undefined type of TBTT Information field. In this way, a receiving STA may determine that the first frame is transmitted from the first AP of the NSTR softAP MLD by parsing the TBTT Information Field Type in the Neighbor AP Information field associated with the non-primary link. In some instances, non-legacy devices may be aware of the new type of TBTT Information field disclosed herein, and may thus obtain the complete profiles of both the primary and non-primary links from the first frame. Conversely, legacy devices may not understand the new type of TBTT Information field disclosed herein, and may thus ignore the TBTT Information field in the Neighbor AP Information field associated with the non-primary link. In this way, aspects of the subject matter disclosed herein may preclude at least some legacy devices from discovering the non-primary link based on information received on the primary link).
Prior art of record discloses wherein each of the one or more TBTT information subfields vary in a number of octets based on a combination of a type of a corresponding STA among the plurality of STAs, or the TBTT information field type subfield and the TBTT information length subfield included in a corresponding neighboring AP information field among the at least one neighboring AP information field. Such teachings may be seen in Lu et al, U.S. Patent Application Publication No. 20220386301 (e.g., FIG. 2, ¶ [0023], TBTT Information Length subfield is set to 9 (e.g., 9 octets) [this citation establishes that a subfield value may be associated with number of octets for the subfield]; e.g., ¶ [0024], the Neighbor AP Information field may include the TBTT Information Field with a specific length value to indicate that the reported AP is affiliated with an NSTR AP MLD and operating on the non-primary link of the NSTR link pair. For instance, the TBTT Information Length subfield may be set to a specific or predefined value (e.g., 3, 25), and the TBTT Information Field Type subfield may be set to 0; e.g., ¶ [0025], When the TBTT Information Length subfield is set to the specific value (e.g., 25 in one example), the TBTT Information Field content may contain the following information: the BSSID subfield and the MLD parameters subfield. The TBTT Information Field content may not include the Neighbor AP TBTT Offset subfield. The TBTT Information Field contents may be of a total length of 9 octets when the Length subfield is set to 25, which means the TBTT Information Length subfield value is mapped to a specific TBTT Information field content) [i.e., the citations suggest that at least the one or more TBTT information subfields may vary in a number of octets, and the TBTT information field type subfield and the TBTT information length subfield, with their associated subfield sizes, are included in a neighboring AP information field]).
Prior art of record discloses wherein, when the TBTT information field type subfield is set to ‘0’, and based on the value of the TBTT information length subfield… a number of octets of each of the one or more TBTT information fields are processed up to a first threshold value or a second threshold value. Such teachings may be seen in Huang, U.S. Patent Application Publication No. 20250063530 A1 (e.g., FIGS. 3C, 3D, ¶ [0062] Table 1: If the TBTT Information Field Type subfield is 0, the TBTT Information Length subfield indicates the length and contents of each TBTT Information field described in FIG. 3D; and is interpreted as shown in Table 1. For example, when the TBTT Information Length subfield value is 15, each TBTT Information field comprises a 1-octet Neighbor AP TBTT Offset subfield [i.e., a first threshold for number of octets for this information field], a 6-octet BSSID subfield [i.e., a second threshold for number of octets for this information field], a 4-octet Short SSID subfield, 1-octet BSS Parameters subfield, and a 3-octet MLD Parameters subfield). Patil further discloses wherein, when the TBTT information field type subfield is set to ‘1’, and based on a value of the TBTT information length subfield, each TBTT Information field comprises a 3-octet MLD Parameters subfield [i.e., a third threshold value for an information subfield] (e.g., ¶ [0062] Table 1).
Other prior art of record which discloses informative details, depending on values for TBTT information field type and TBTT information length subfield, may be seen in:
Gan et al, U.S. Patent Application Publication No. 20200280909 A1 (e.g., ¶ [0121] The TBTT Information Field Type subfield is set to 1 to indicate the AP reported in the Neighbor AP Information field is a member of a multiple BSSID set (i.e., operated by an AP with dot11MultiBSSIDActivated set to true), in this case, the setting Transmitted BSSID subfield is the same as Multiple BSSID subfield of 1 value; e.g., ¶ [0137] The TBTT Information Field Type subfield is 2 bits in length and identifies, together with the TBTT Information Length subfield, the format of the TBTT Information field. It is set to 0. (11ai) Values 1, 2, and 3 are reserved);
Chitrakar et al, U.S. Patent Application Publication No. 20230232315 A1 (e.g., ¶ [0142] In an example, a Reduced Neighbor Report element 3000 as shown in FIG. 30 may be used to provide information of multiple APs or VAPs. In this case, Reduced Neighbor Report element 3000 provides information for a VAP-2 1010 in FIG. 10A, and is affiliated with AP MLD2 1004, indicating in TBTT Information set field 3002 the BSSID of VAP-2 and indicating Short-SSID of VAP-2 as “32-CRC(Guest)”. Two fields are also added to the TBTT Information set field 3002. The new added fields 3004 and 3006 indicate respectively the AP MLD MAC address and the Link ID with which this AP (VAP-2) is affiliated with. The “TBBT Information Field Type” sub-field 3008 by itself or together with the “TBTT Information Length” subfield 3010 of the RNR element indicates the presence of additional the MLD Information. For example, if “TBBT Information Field Type” is set to a value other than 0, it indicates that the TBTT Information Set carries the MLD information. E.g. if set to 1, the Link ID field is carried, and if it is set to 2, both Link ID and MLD MAC Address are carried. Alternatively, if the “TBTT Information Length” is set to 13, the Link ID field is carried, and if it is set to 18, the MLD MAC Address is carried, and if set to 19, both Link ID and MLD MAC Address are carried); and
Park et al, U.S. Patent Application Publication No. 20150208330 A1 (e.g., ¶ [0224] The TBTT information field type 1950 may define a structure of a TBTT information field by a length of 2 bits. When the TBTT information field type 1950 is 0, it may indicate presence of informative neighbor AP information. The informative neighbor AP information may be information assisting the STA to perform AP discovery. When the TBTT information field type 1950 is 1, it may indicate presence of the redirect neighbor AP information (or neighbor AP). The redirect neighbor AP information (or a neighbor AP) may be used by the STA to switch an AP that performs a scanning procedure to a different AP. When the TBTT information field type 1950 is 1 and a channel and a band of an AP that has transmitted the reduced neighbor report element is a current operating channel and a current operating band, a different AP may be used by the STA to switch an AP to a different AP of the current operating channel, an AP of a channel from the current operating channel, or a different AP of a band different from the current operating band. In short, the value 1 of the TBTT information field type 1950 can be used by the STA to switch to the channel, the band, or the neighbor AP as specified in the neighbor AP information field).
Prior art of record fails to disclose individually or in combination or render obvious the limitations regarding wherein, when the TBTT information field type subfield is set to ‘1’, and based on a value of the TBTT information length subfield being greater than a third threshold value, the processor is configured to process a number of octets of each of the one or more TBTT information fields up to the third threshold value and ignore remaining octets of each of the one or more TBTT information fields above the third threshold value.
Claims 2-10, dependent from claim 1, and Claims 12-20, dependent from claim 10, are also objected.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. References considered relevant to this application are listed in the attached "Notice of References Cited” (PTO-892).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to VLADISLAV Y AGUREYEV whose telephone number is (571)272-0549. The examiner can normally be reached Monday--Friday (9-5).
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.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Sujoy Kundu can be reached at (571) 272-8586. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/VLADISLAV Y AGUREYEV/Examiner, Art Unit 2471