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 .
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-8, 10-14, and 16-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Hu (Publication number: US 2019/0357043).
Consider Claim 1, Hu shows a method (see figures 2 and 3), comprising:
(a) Receiving a subnet parameter allocation request message sent by a first gateway (see figure 5; and paragraphs 98-102); (After a Bluetooth gateway detects the Bluetooth device's broadcast data packets, it reports the product ID and MAC address to the cloud).
(b) Allocating, based on the subnet parameter allocation request message, different first parameters and a same second parameter to a plurality of first subdevices belonging to different categories (see figure 5; and paragraphs 98-102); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
(c) Sending a first subnet parameter comprising a first parameter of the different first parameters and the same second parameter to the first gateway (see figure 5; and paragraphs 100-104); (The cloud sends the first authentication information and the server random number to the Bluetooth gateway. The Bluetooth gateway forwards the first authentication information to the Bluetooth device. The Bluetooth device generates second authentication information, e.g., AES-CMAC applied to (Random2∥AuthValue2) from its built-in three-tuple information (Product ID2, MAC2, Secret Key2) and a device random number).
Consider Claim 10, Hu shows a method (see figures 2 and 3), comprising:
(a) When network configuration is performed on a first subdevice, allocating different first parameters and a same second parameter to a plurality of first subdevices belonging to different categories (see figure 5; and paragraphs 98-102); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
(b) Sending a first subnet parameter comprising a first parameter of the different first parameters and the same second parameter to the first subdevice (see figure 5; and paragraphs 100-104); (The cloud sends the first authentication information and the server random number to the Bluetooth gateway. The Bluetooth gateway forwards the first authentication information to the Bluetooth device. The Bluetooth device generates second authentication information, e.g., AES-CMAC applied to (Random2∥AuthValue2) from its built-in three-tuple information (Product ID2, MAC2, Secret Key2) and a device random number).
Consider Claim 17, Hu shows an apparatus, comprising one or more processors and one or more memories, wherein the one or more memories store one or more computer programs, the one or more computer programs comprise instructions, and when the instructions are executed by the one or more processors (see figure 5; and paragraphs 115-117), cause the apparatus to:
(a) Receive a subnet parameter allocation request message sent by a first gateway; allocate, based on the subnet parameter allocation request message, different first parameters and a same second parameter to a plurality of first subdevices belonging to different categories (see figure 5; and paragraphs 98-102); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
(b) Send a first subnet parameter comprising a first parameter of the different first parameters and the same second parameter to the first gateway (see figure 5; and paragraphs 100-104); (The cloud sends the first authentication information and the server random number to the Bluetooth gateway. The Bluetooth gateway forwards the first authentication information to the Bluetooth device. The Bluetooth device generates second authentication information, e.g., AES-CMAC applied to (Random2∥AuthValue2) from its built-in three-tuple information (Product ID2, MAC2, Secret Key2) and a device random number).
Consider Claims 2 and 18, HU shows allocating, based on the subnet parameter allocation request message, the different first parameters and the same second parameter to the plurality of first subdevices belonging to the different categories comprises: generating the first parameter and the same second parameter based on the subnet parameter allocation request message (see figure 5; and paragraphs 98-102); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
Consider Claims 3 and 19, Hu shows allocating, based on the subnet parameter allocation request message, the different first parameters and the same second parameter to the plurality of first subdevices belonging to the different categories comprises: obtaining the first parameter and the same second parameter from a pre-stored subnet parameter (see figure 5; and paragraphs 116-120); (Receiving module 60a receives device identification information of a to-be-authenticated Bluetooth device that requests access to a Bluetooth mesh network (as reported by a destination Bluetooth gateway). The destination Bluetooth gateway is a Bluetooth gateway that detects a to-be-authenticated Bluetooth device in the Bluetooth mesh network).
Consider Claims 4 and 20, Hu shows that before receiving the subnet parameter allocation request message sent by the first gateway, the method further comprises: receiving the first parameter and the same second parameter that are sent by a first application (see figure 5; and paragraphs 96-98); (After a Bluetooth device is plugged in, it broadcasts data packets. These data packets may include the product ID and MAC address built into the Bluetooth device. After a Bluetooth gateway detects the Bluetooth device's broadcast data packets, it reports the product ID and MAC address to the cloud).
Consider Claim 5, Hu shows that the first parameter comprises an application layer data key, and the same second parameter comprises a network layer data key; or the first parameter comprises the application layer data key and a multicast address, and the same second parameter comprises the network layer data key; or the first parameter is empty, and the same second parameter comprises the application layer data key and the network layer data key (see figure 5; and paragraphs 98-104); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
Consider Claim 6, Hu shows sending a subnet parameter update message to the first gateway; and after completing identity authentication with a first subdevice of the plurality of first subdevices, sending an updated second subnet parameter to the first gateway (see figure 5; and paragraphs 108-112); (The cloud subjects the Bluetooth device to authentication based on the device random number, the second authentication information, and the three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
Consider Claim 7, Hu shows sending the subnet parameter update message to the first gateway comprises: periodically sending the subnet parameter update message to the first gateway (see figure 5; and paragraphs 118-122).
Consider Claim 8, Hu shows a subnet parameter update request message sent by the first gateway; and after completing identity authentication with a first subdevice of the first plurality of subdevices based on the subnet parameter update request message, sending an updated second subnet parameter to the first gateway (see figure 5; and paragraphs 116-120); (Receiving module 60a receives device identification information of a to-be-authenticated Bluetooth device that requests access to a Bluetooth mesh network (as reported by a destination Bluetooth gateway). The destination Bluetooth gateway is a Bluetooth gateway that detects a to-be-authenticated Bluetooth device in the Bluetooth mesh network).
Consider Claim 11, Hu shows that before allocating the different first parameters and the same second parameter to the plurality of first subdevices belonging to the different categories, the method further comprises: receiving the first parameter and the same second parameter that are sent by a first application (see figure 5; and paragraphs 98-102); (The cloud uses the product ID and MAC address reported by the Bluetooth gateway as a basis to determine the Bluetooth device's three-tuple information (Product ID1, MAC1, Secret Key1) maintained in the cloud).
Consider Claims 12 and 13, Hu shows sending a subnet parameter update message to the first subdevice; and after completing identity authentication with the first subdevice, sending an updated second subnet parameter to the first subdevice; wherein sending the subnet parameter update message to the first subdevice comprises: periodically sending the subnet parameter update message to the first subdevice (see figure 5; and paragraphs 118-122).
Consider Claim 14, Hu shows receiving a subnet parameter update request message sent by the first subdevice; and after completing identity authentication with the first subdevice, sending an updated second subnet parameter to the first subdevice (see figure 5; and paragraphs 116-120); (Receiving module 60a receives device identification information of a to-be-authenticated Bluetooth device that requests access to a Bluetooth mesh network (as reported by a destination Bluetooth gateway). The destination Bluetooth gateway is a Bluetooth gateway that detects a to-be-authenticated Bluetooth device in the Bluetooth mesh network).
Consider Claim 16, Hu shows that the first parameter comprises an application layer data key, and the same second parameter comprises a network layer data key; or the first parameter comprises the application layer data key and a multicast address, and the same second parameter comprises the network layer data key; or the first parameter is empty, and the same second parameter comprises the application layer data key and the network layer data key (see figure 5; and paragraphs 100-104); (The cloud sends the first authentication information and the server random number to the Bluetooth gateway. The Bluetooth gateway forwards the first authentication information to the Bluetooth device. The Bluetooth device generates second authentication information, e.g., AES-CMAC applied to (Random2∥AuthValue2) from its built-in three-tuple information (Product ID2, MAC2, Secret Key2) and a device random number).
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.
Claims 9 and 15 are rejected under 35 U.S.C. 103 as being unpatentable over Hu (Publication number: US 2019/0357043) in view of an official notice taken by the USPTO.
Consider Claims 9 and 15, Hu does not specifically show sending, to the first gateway, a message for deregistering the first subnet parameter. However, the USPTO takes official notice that it is well known and expected in the art to deregister a subnet parameter in order to release network resources.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MICHAEL A FARAGALLA whose telephone number is (571)270-1107. The examiner can normally be reached Mon-Fri 8:00-5:00.
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, Matthew Eason can be reached at 571-270-7230. 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.
/MICHAEL A FARAGALLA/Primary Examiner, Art Unit 2624 09/09/2026
Prosecution Insights