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 .
Response to Amendment
This office action is in reply to Applicant’s Response dated 04/21/2026. Claims 1, 14, 15 and 28 were amended. Claims 8 and 22 were canceled. Claims 1-7, 9-21 and 23-28 remain pending in the application.
Rejections under 35 USC § 112 no longer applies, the rejection is withdrawn as a result of amendment made on the claims.
Response to Arguments
To teach the amended independent claims, new reference Gaskill et al. (US 4897835 A), Gaskill hereinafter in combination with existing Xu is now used.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
In event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claims 1, 14, 15 and 28 are rejected under 35 U.S.C. 103 as being unpatentable over Xu ( U.S. PGPUB 2025/0031191), Xu hereinafter, in view of Gaskill et al. (US 4897835 A), Gaskill hereinafter.
Regarding claims 1 and 15, Xu teaches a network device for wireless communications, the network device comprising: (fig. 13 and fig. 14 and paragraph 0133 - FIG. 13 shows a wireless audio data transmission device 1300 according to one embodiment of the present invention. The wireless audio data transmission device 1300 can be used as a master device. The master device communicates wirelessly with N slave devices in consecutive isochronous intervals based on N communication links, respectively. The N slave devices comprise one or more audio input slave devices and one or more audio output slave devices. N is an integer greater than or equal to two.)
at least one memory; and (fig. 16)
at least one processor coupled to the at least one memory and configured to: (fig. 16)
output, for transmission to a plurality of wireless communication devices, a message (fig. 1, fig.2, fig. 10, fig. 11(a) and fig. 11(b) and paragraphs 0039 to 0041 and 0081 discloses output for transmission to devices - … the master device periodically transmits a synchronization control data packet based on a periodic advertising channel in the bidirectional advertising communication time slot and receives a synchronization control response packet fed back by a candidate slave device which is one of the slave devices requesting access. ...)
receive, on one or more available channel subframes of the plurality of available channel from one or more wireless communication devices of the plurality of wireless communication devices, an initiation request message requesting synchronization with the network device; (fig. 1, fig.2, fig. 10, fig. 11(a) and fig. 11(b) and paragraph 0125 discloses receiving initiation request message - … After the slave device transmits the AIS access request, it continues to receive the AUX_SYNC_CTR PDU transmitted by the master device ...)
output, for transmission on the one or more available channel subframes to the one or more wireless communication devices, an initiation response message confirming the synchronization with the network device; and(fig. 1, fig.2, fig. 10, fig. 11(a) and fig. 11(b) and paragraph 0125 discloses initiation confirmation message - … After the slave device transmits the AIS access request, it continues to receive the AUX_SYNC_CTR PDU transmitted by the master device ...)
establish a synchronized connection with the one or more wireless communication devices on the one or more available channel subframes (paragraphs 0082 to 0088 discloses synchronized connection - … master device further transmits a link access permit command based on the synchronization control data packet for permitting the candidate slave device to establish a communication link with the master device. …)
Yet, Xu does not expressly teach a bit mask indicating plurality of available channel subframes; and channel subframes selected from the plurality of available channel subframes indicated in the bit mask from one or more wireless communication devices.
However, in the analogous art, Gaskill explicitly discloses comprising a bit mask indicating plurality of available channel subframes; (column 23 line 53 to 67 - (95) ... The remaining or upper 6-bits of field 608 are ordinarily used to identify to the receiver one or more subframes, depending on how many of the bits are masked by the receiver. These 6-bits also match a corresponding portion of the individual receiver's address and, for a receiver that normally turns on once each frame, corresponds to subframe number. If one bit of the upper 6-bits is masked, the subframe number, as interpreted by the receiver, recurs every 32nd subframe. If two bits are masked, the subframe number recurs every 16th subframe, so the individual receiver turns on twice each frame. When a group message is transmitted, field 608 contains the subframe number and time slot number in which the message is transmitted.)
channel subframes selected from the plurality of available channel subframes indicated in the bit mask from one or more wireless communication devices (column 23 line 53 to 67 and column 36 line 13 to line 19 - (95) ... The remaining or upper 6-bits of field 608 are ordinarily used to identify to the receiver one or more subframes, depending on how many of the bits are masked by the receiver. These 6-bits also match a corresponding portion of the individual receiver's address and, for a receiver that normally turns on once each frame, corresponds to subframe number. If one bit of the upper 6-bits is masked, the subframe number, as interpreted by the receiver, recurs every 32nd subframe. If two bits are masked, the subframe number recurs every 16th subframe, so the individual receiver turns on twice each frame. When a group message is transmitted, field 608 contains the subframe number and time slot number in which the message is transmitted. ... (173) FIG. 18 is a diagram of a transmitted frame that illustrates the time offset, with subframes 0-31 indicated on the vertical axis and time slots 0-500 of the 1027 total slots indicated on the horizontal axis. The 32 subframes result from a masking of the most significant bit of the subframe identification number as discussed in Section 3.2. ).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filling date of the claimed invention to combine Xu’s Wireless audio data transmission method and related device to include Gaskill’s use of bit masking to address receiver and transmitter subframes to achieve individual synchronization to each device.
Regarding claims 14 and 28, Xu in view of Gaskill teaches claims 1 and 15.
Xu further teaches wherein each wireless communication device of the plurality of wireless communication devices is configured to communicate according to a low energy wireless protocol (paragraphs 0145 to 0152 discloses BLE devices - [0150]… The baseband data and protocol processor also executes the BLE Audio-related BLE protocol and the AIG protocol, processes the AISD PDUs received by the BLE RF transceiver module, and transmits them to the audio processing unit. … ). BLE is Bluetooth Low Energy.
Claims 2-7, 9-13, 16-21 and 23- 27 are rejected under 35 U.S.C. 103 as being unpatentable over Xu ( U.S. PGPUB 2025/0031191), Xu hereinafter, in view of Gaskill, and further view of Woolley Bluetooth Core Specification Version 5.4 Technical overview, Woolley hereinafter.
Regarding Claims 2 and 16, Xu in view of Gaskill teaches claim 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the at least one processor is configured to output the message for transmission within a periodic advertisement with response (PAwR) train.
However, in the analogous art, Woolley explicitly discloses wherein the at least one processor is configured to output the message for transmission within a periodic advertisement with response (PAwR) train (Section 1.2.3.4.4 - Synchronization The LE Set Periodic Sync Subevent command is a new command that the Observer uses to instruct its Controller to synchronize its scanning schedule with one or more PAwR subevents belonging to a particular PAwR advertising train.).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filling date of the claimed invention to combine Xu’s Wireless audio data transmission method and related device to include Woolley’s Bluetooth Core Specification Version 5.4 Technical overview to get advantages associated with Bluetooth.
Regarding Claims 3 and 17, Xu in view of Gaskill and further in view of Woolley teaches claims 2 and 16.
Woolley further teaches wherein the message further comprises data associated with the PAwR train (Section 1.2.3.3.1 - ... Having acquired the event timing information described in (1) and the subevents information in (2), the Observer has a complete description of the timing parameters and structure of the events and subevents of the PAwR advertising train. But it is only when it has the information in (3) that it can schedule its scanning such that it receives only those packets that are expected to contain data of relevance and can schedule the transmission of response packets. ). The information in 3 is the data associated with the PAWR train.
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claim 3 and 17.
Regarding Claims 4 and 18, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the at least one processor is configured to output the message for transmission on a legacy channel.
However, in the analogous art, Woolley explicitly discloses wherein the at least one processor is configured to output the message for transmission on a legacy channel (Sections 1.1.5 and 1.1.5.1 - Legacy Advertising When performing legacy advertising, identical copies of legacy advertising packets are transmitted on up to three primary advertising channels, ).
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claim 4 and 18.
Regarding Claims 5 and 19, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the message is an extended advertising packet.
However, in the analogous art, Woolley explicitly discloses wherein the message is an extended advertising packet (Section 1.1.5.2 Extended Advertising … The LE Advertising Broadcast (ADVB) logical transport incorporates two advertising modes: legacy advertising and one of two ways of performing extended advertising. Both legacy advertising and the form of extended advertising associated with the ADVB logical transport involve irregular scheduling of events. ...)
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 5 and 19.
Regarding Claims 6 and 20, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the initiation request message is a camping initiation message, and wherein the initiation response message is a camping confirmation message.
However, in the analogous art, Woolley explicitly discloses wherein the initiation request message is a camping initiation message, and wherein the initiation response message is a camping confirmation message (Section 1.1.4 - … A Peripheral can accept a request to establish a connection sent by a Central. … The terms Central and Peripheral are used when the context relates to establishing connections. … and section 1.2.1 - … Observers can establish the periodic transmission schedule used by the Broadcaster from AUX_ADV_IND PDUs or by using the Periodic Advertising Sync Transfer (PAST) procedure. ... The PAwR Broadcaster may use a transmission time slot to send a connection request (AUX_CONNECT_REQ) to a specific device and establish an LE-ACL connection with it. PADVB does not have this capability. ... )
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 6 and 20.
Regarding Claims 7 and 21, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the initiation request message comprises wireless communication device identification information and cryptographic information.
However, in the analogous art, Woolley explicitly discloses wherein the initiation request message comprises wireless communication device identification information and cryptographic information (Section 2.1.3 - The intended recipient(s) of encrypted data must somehow be provided with the associated key material so that received data can be decrypted. ... and Section 2.2.2 - ... The Encrypted Data Key Material characteristic contains a 24-octet value which is made up of a 16-octet session key and an 8-octet IV value. A GATT client can read this value over an encrypted and authenticated ACL connection only; therefore, the advertising device and all devices intended to be recipients of encrypted advertising data must have been paired. ...).
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 7 and 21.
Regarding Claims 9 and 23, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein, to establish the synchronized connection, the at least one processor is configured to establish a generate attribute profile (GATT) connection.
However, in the analogous art, Woolley explicitly discloses wherein, to establish the synchronized connection, the at least one processor is configured to establish a generate attribute profile (GATT) connection (Section 3, 3.1 to 3.2.2 – The whole of section 3 discloses details of GATT)
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 9 and 23.
Regarding Claims 10 and 24, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the at least one processor is configured to receive, from a network entity, a command to start onboarding at least one of the plurality of wireless communication devices.
However, in the analogous art, Woolley explicitly discloses wherein the at least one processor is configured to receive, from a network entity, a command to start onboarding at least one of the plurality of wireless communication devices (Section 1.2.3.4.1 - Periodic Advertising Configuration Version 2 of the LE Set Periodic Advertising Parameters command adds parameters Num_Subevents, Subevent_Interval, Response_Slot_Delay, Response_Slot_Spacing, and Num_Response_ Slots. These parameters are required when configuring the Controller for periodic advertising with responses.)
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 10 and 23.
Regarding Claims 11 and 25, Xu in view of Gaskill and further in view of Woolley teaches claims 10 and 24.
Woolley further teaches wherein the network entity is a management entity (ME) (Section 1.2.4.2.2 - Figure 9 shows the transmission of PDUs that occur when the AP issues a command addressed to several shelf labels, each of which is a member of ESL group #1. This is followed by transmitting a single command addressed to a single device that belongs to ESL group #2.). The command by AP to several shelf labels shows it as a management entity.
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 11 and 25.
Regarding Claims 12 and 26, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein the at least one processor is configured to receive, from a network entity, a command to stop onboarding the one or more wireless communication devices.
However, in the analogous art, Woolley explicitly discloses wherein the at least one processor is configured to receive, from a network entity, a command to stop onboarding the one or more wireless communication devices (Section 1.2.3.4.1 - Periodic Advertising Configuration Version 2 of the LE Set Periodic Advertising Parameters command adds parameters Num_ Subevents, Subevent_Interval, Response_Slot_Delay, Response_Slot_Spacing, and Num_Response_ Slots. These parameters are required when configuring the Controller for periodic advertising with responses.)
The motivation regarding to the obviousness of claim 2 and 16 is also applied to claims 12 and 26.
Regarding Claims 13 and 27, Xu in view of Gaskill teaches claims 1 and 15.
Yet, Xu in view of Gaskill does not expressly teach wherein network device is an access point (AP).
However, in the analogous art, Woolley explicitly discloses wherein network device is an access point (AP). (Section 1.2.4 - The PAwR Broadcaster, known as an Access Point (AP) in the ESL profile specification, configures electronic shelf label devices by writing to various GATT characteristics over an LE ACL connection.)
The motivation regarding to the obviousness of claims 2 and 16 is also applied to claims 13 and 27.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LAWRENCE AYODELE OLUBODUN whose telephone number is (571)270-5462. The examiner can normally be reached 8.00am - 5pm.
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, Nicholas A. Jensen can be reached at 571-270-5443. 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.
/A.L.O./Examiner, Art Unit 2472
/ANDREW W CHRISS/Primary Examiner, Art Unit 2472