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 § 103
In the 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 (i.e., changing from AIA to pre-AIA ) 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 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.
The factual inquiries 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-2, 9-10, 24-25, 28-29, 32-33, 47 are rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014).
Regarding claim 1 (Currently Amended), Han discloses an apparatus for wireless communication (fig. 2, a schematic diagram of a message transmission process according to a PTP version of a sending port set by a network side device, sections 0055-0056), comprising: memory (fig. 9, processor 901 that is coupled to a memory 902, section 0137); and at least one processor coupled to the memory (fig. 9, processor with memory, section 0137) and configured to: transmit (fig. 9, transceiver 903 coupled to processor 901 and memory 902, section 0137), to a first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), a first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) comprising capability information (see, follow up, delay request, and delay response message in a first PTP message that can indicate capacity, section 0062) indicating that the apparatus (fig. 2, a schematic diagram of a message transmission process according to a PTP version of a sending port set by a network side device, sections 0055-0056) is capable of operating as a precision time protocol (PTP) grand master clock (see, PTP message field can include a grandmaster clock quality field, sections 0094-0097; noted, state of the sending port is a master clock, section 0101); receive, from the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), a second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) comprising one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) after transmission of the first message (see, the second PTP message compared to the previous PTP message based on version where a previous lower PTP version cannot be compatible with a new higher PTP version and new higher PTP version can be compatible with the previous lower PTP version implying the aftermath of a previous PTP message, section 0076); generate, based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a followup (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) received from the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), a first PTP message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) including first time information (see, the first PTP message contains time synchronization, section 0061-0062), wherein the first PTP message comprises an Announce message; and transmit, to one or more downstream devices in communication with the apparatus, the generated first PTP message including the first time information (see, the first PTP message contains time synchronization, section 0061-0062), wherein the first device is distinct from the one or more downstream devices.
Han discloses all the claim limitations as set forth above but fails to explicitly disclose: transmit, to one or more downstream devices in communication with the apparatus, the generated first PTP message including the first time information, wherein the first device is distinct from the one or more downstream devices.
However Zheng from a similar field of endeavor discloses: transmit, to one or more downstream devices in communication with the apparatus (see, when a conventional PTP device switches to a new slave port, there is a possibility that a re-convergence may occur (i.e., a new synchronization tree may be formed), and as a result all downstream PTP devices are affected, section 0075 Zheng; noted, stepsRemoved values of the receiving and transmitting PTP port where stepsRemoved refers to the number of boundary clock hops away the respective PTP clock is from the GM, section 0033 Zheng), the generated first PTP message (see, network device includes message generator for generating and sending PTP timing messages, section 0045 Zheng) including the first time information, wherein the first device is distinct (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng) from the one or more downstream devices (see, when a conventional PTP device switches to a new slave port, there is a possibility that a re-convergence may occur (i.e., a new synchronization tree may be formed), and as a result all downstream PTP devices are affected, section 0075 Zheng; noted, stepsRemoved values of the receiving and transmitting PTP port where stepsRemoved refers to the number of boundary clock hops away the respective PTP clock is from the GM, section 0033 Zheng).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the apparatus of Han with the unique PTP identities as taught by Zheng. The motivation would have been to reduce sync time in a precision time protocol (PTP) network.
The combination of Han and Zheng discloses all the claim limitations as set forth above but fails to explicitly disclose: a first PTP message including first time information, wherein the first PTP message comprises an Announce message; and transmit, to one or more downstream devices in communication with the apparatus, the generated first PTP message including the first time information, wherein the first device is distinct from the one or more downstream devices.
However Wang ‘476 from a similar field of endeavor discloses: a first PTP message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0095 Wang ‘476) including first time information (see, generate a time synchronization message according to the request message received by the receiving module, section 0047 Wang ‘476), wherein the first PTP message comprises an Announce message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0096 Wang ‘476); and transmit, to one or more downstream devices in communication with the apparatus, the generated first PTP message including the first time information, wherein the first device is distinct from the one or more downstream devices.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han and Zheng with the Announce message as taught by Wang ‘476. The motivation would have been to improve time synchronization with respect to messages.
Regarding claim 2 (Previously Presented), Han discloses the apparatus of claim 1, wherein the at least one processor is further configured to: receive, from the first device, an activation message (fig. 7, the PTP Announce message to select a device such as to assume if it is a master clock, sections 0108-0110) to enable the at least one processor to be configured to transmit (fig. 9, processor 901 is configured to execute the program stored in the memory 902 and control the transceiver to send a first PTP message that uses the PTP version of the sending port through the sending port, section 0137) PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) to the one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015), wherein, to generate the first PTP message (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), the at least one processor is configured to generate the first PTP message (see, after the network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061) further based on the activation message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) (see, the PTP Announce message that allows the network side device to determine the state of the sending port as a master or slave clock, section 0104).
Regarding claim 9 (Original), Han discloses the apparatus of claim 1, wherein the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a followup (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) includes PTP version-type information (see, PTP version used by the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064).
Regarding claim 10 (Original), Han discloses the apparatus of claim 1, wherein the capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) includes PTP version-type information (see, PTP version used by the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064; noted, that the port can send and receive information, section 0087).
Regarding claim 24 (Previously Presented), Han discloses the apparatus of claim 1, further comprising a transceiver coupled to the at least one processor (fig. 9, a network side device 900, including: a processor 901, a memory 902, and a transceiver 903, section 0136) , wherein the at least one processor is further configured to: transmit, via the transceiver, the first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061): receive, via the transceiver, the second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064): and transmit via the transceiver, the first PTP message, wherein the first message is distinct from the first PTP message.
Han discloses all the claim limitations as set forth above but fails to explicitly disclose: wherein the first message is distinct from the first PTP message.
However Zheng from a similar field of endeavor discloses: wherein the first message is distinct from the first PTP message (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the apparatus of Han with the unique PTP identities as taught by Zheng. The motivation would have been to reduce sync time in a precision time protocol (PTP) network.
Regarding claim 25 (Currently Amended), Han discloses a method of wireless communication at a first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), comprising: transmitting, to a second device, a first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) comprising capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) indicating that the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061) is capable of operating as a precision time protocol (PTP) grand master clock (see, PTP message field can include a grandmaster clock quality field, sections, 0094-0097); receiving, from the second device, a second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) comprising one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) after transmission of the first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061); generating, based on the one or more PTP parameters received from the second device (see, PTP message can send a delay response (Delay_Resp) message following a delay request (Delay_Req) message, section 006), a first PTP message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) including time information (see, the first PTP message contains time synchronization, section 0061-0062), wherein the first PTP message comprises an Announce message; and transmitting, to one or more downstream devices in communication with the first device, the generated first PTP message (see, sending the first PTP message through the sending port, section 0061) including the time information (see, the first PTP message contains time synchronization, section 0061-0062) to one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015) in communication with the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), wherein the second device is distinct from the one or more downstream devices.
Han discloses all the claim limitations as set forth above but fails to explicitly disclose: transmitting, to one or more downstream devices in communication with the first device, the generated first PTP message (see, sending the first PTP message through the sending port, section 0061) including the time information (see, the first PTP message contains time synchronization, section 0061-0062) to one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015) in communication with the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), wherein the second device is distinct from the one or more downstream devices.
However Zheng from a similar field of endeavor discloses: transmitting, to one or more downstream devices in communication with the first device (see, when a conventional PTP device switches to a new slave port, there is a possibility that a re-convergence may occur (i.e., a new synchronization tree may be formed), and as a result all downstream PTP devices are affected, section 0075 Zheng; noted, stepsRemoved values of the receiving and transmitting PTP port where stepsRemoved refers to the number of boundary clock hops away the respective PTP clock is from the GM, section 0033 Zheng), the generated first PTP message (see, network device includes message generator for generating and sending PTP timing messages, section 0045 Zheng) including the time information to one or more downstream devices in communication with the first device, wherein the second device is distinct from the one or more downstream devices (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the method of Han with the unique PTP identities as taught by Zheng. The motivation would have been to reduce sync time in a precision time protocol (PTP) network.
The combination of Han and Zheng discloses all the claim limitations as set forth above but fails to explicitly disclose: a first PTP message including time information, wherein the first PTP message comprises an Announce message; and transmitting, to one or more downstream devices in communication with the first device, the generated first PTP message including the time information to one or more downstream devices in communication with the first device, wherein the second device is distinct from the one or more downstream devices.
However Wang ‘476 from a similar field of endeavor discloses: a first PTP message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0095 Wang ‘476) including first time information (see, generate a time synchronization message according to the request message received by the receiving module, section 0047 Wang ‘476), wherein the first PTP message comprises an Announce message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0096 Wang ‘476); and transmitting, to one or more downstream devices in communication with the first device, the generated first PTP message including the time information to one or more downstream devices in communication with the first device, wherein the second device is distinct from the one or more downstream devices.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han and Zheng with the Announce message as taught by Wang ‘476. The motivation would have been to improve time synchronization with respect to messages.
Regarding claim 28 (Currently Amended), Han discloses an apparatus for wireless communication (fig. 2, a schematic diagram of a message transmission process according to a PTP version of a sending port set by a network side device, sections 0055-0056), comprising: memory (fig. 9, processor with memory, section 0137); and at least one processor coupled to the memory (fig. 9, processor with memory, section 0137) and configured to: receive, from a first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), a first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) comprising capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) indicating that the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061) is capable of operating as a precision time protocol (PTP) grand master clock (see, PTP message field can include a grandmaster clock quality field, sections, 0094-0097); transmit, based on the received capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061), a second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) comprising one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) to the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061); and transmit, to the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), an activation message (fig. 7, the PTP Announce message to select a device such as to assume if it is a master clock, sections 0108-0110) to enable the first device to transmit, based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) to one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015) in communication with the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), wherein the apparatus is distinct from the one or more downstream devices, the PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) including time information (see, PTP message can be sent through the sending port, section 0061; noted, the port can send and receive information, section 0087; noted, the PTP message includes time synchronization and delay information, section 0061) based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), the PTP messages comprising an Announce message.
Han discloses all the claim limitations as set forth above but fails to explicitly disclose: wherein the apparatus is distinct from the one or more downstream devices, the PTP messages including time information (see, PTP message can be sent through the sending port, section 0061; noted, the port can send and receive information, section 0087; noted, the PTP message includes time synchronization and delay information, section 0061) based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), the PTP messages comprising an Announce message.
However Zheng from a similar field of endeavor discloses: wherein the apparatus is distinct from the one or more downstream devices (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng), the PTP messages including time information based on the one or more PTP parameters, the PTP messages comprising an Announce message.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the apparatus of Han with the unique PTP identities as taught by Zheng. The motivation would have been to reduce sync time in a precision time protocol (PTP) network.
The combination of Han and Zheng discloses all the claim limitations as set forth above but fails to explicitly disclose: the PTP messages comprising an Announce message.
However Wang ‘476 from a similar field of endeavor discloses: the PTP messages (see, generate a time synchronization message according to the request message received by the receiving module, section 0047 Wang ‘476)comprising an Announce message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0096 Wang ‘476).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han and Zheng with the Announce message as taught by Wang ‘476. The motivation would have been to improve time synchronization with respect to messages.
Regarding claim 29 (Previously Presented), Han discloses the apparatus of claim 28, further comprising a transceiver coupled to the at least one processor (fig. 9, a network side device 900, including: a processor 901, a memory 902, and a transceiver 903, section 0136), wherein, to transmit the second message comprising the one or more PTP parameters to the first device (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), the at least one processor are further configured to: transmit, via the transceiver, the second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) comprising one or more updated PTP parameters to the first device (see, the transceiver to send a first PTP message that uses the PTP version of the sending port through the sending port, section 0137).
Regarding claim 32 (Original), Han discloses the apparatus of claim 28, wherein the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a followup (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) includes PTP version-type information (see, PTP version used by the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064).
Regarding claim 33 (Original), Han discloses the apparatus of claim 28, wherein the capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) includes PTP version-type information (see, PTP version used by the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064; noted, that the port can send and receive information, section 0087).
Regarding claim 47 (Currently Amended), Han discloses a method of wireless communication at a first device, comprising: receiving, from a second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148), a first message (see, the generation of the first PTP message based on the PTP version of the sending port from a network side device, section 0061) comprising capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061) indicating that the second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148) is capable of operating as a precision time protocol (PTP) grand master clock (see, PTP message field can include a grandmaster clock quality field, sections, 0094-0097); transmitting, based on the received capability information (see, message fields that include fields such as synchronization domain number (domain Number) field, a PTP version (version PTP) field, a grandmaster clock quality (grandmaster clock quality) field, a PTP profile Specific 1 field, and a PTP profile Specific 2 field which can indicate different capabilities of the PTP message, sections 0093-0094; noted, the network side device can support different PTP version to support compatibility between different devices on higher/lower PTP versions, sections 0059-0061), a second message (see, the second PTP message received by the identified receiving port corresponding to the sending port is determined as the PTP version of the sending port, section 0064) comprising one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062) to the second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148); and transmitting, to the second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148), an activation message (fig. 7, the PTP Announce message to select a device such as to assume if it is a master clock, sections 0108-0110) to enable the second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148) to transmit, based on the transmitted one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) to one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015) in communication with the second device (see, the use of setting the state of the sending port of a second device to master to send a second PTP message to a receiving port of a first device after a first message, sections 0143-148) wherein the first device is distinct from the one or more downstream devices, the PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) including time information (see, PTP message can be sent through the sending port, section 0061; noted, the port can send and receive information, section 0087; noted, the PTP message includes time synchronization and delay information, section 0061) based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), the PTP messages comprising an Announce message.
Han discloses all the claim limitations as set forth above but fails to explicitly disclose: wherein the first device is distinct from the one or more downstream devices, the PTP messages including time information (see, PTP message can be sent through the sending port, section 0061; noted, the port can send and receive information, section 0087; noted, the PTP message includes time synchronization and delay information, section 0061) based on the one or more PTP parameters (see, PTP message includes at least one of the following: a PTP announce (Announce) message, a synchronization (Sync) message, a follow-up (Follow_Up) message, a delay request (Delay_Req) message, and a delay response (Delay_Resp) message, section 0062), the PTP messages comprising an Announce message.
However Zheng from a similar field of endeavor discloses: wherein the first device is distinct from the one or more downstream devices (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng), the PTP messages including time information based on the one or more PTP parameters, the PTP messages comprising an Announce message.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the method of Han with the unique PTP identities as taught by Zheng. The motivation would have been to reduce sync time in a precision time protocol (PTP) network.
The combination of Han and Zheng discloses all the claim limitations as set forth above but fails to explicitly disclose: the PTP messages comprising an Announce message.
However Wang ‘476 from a similar field of endeavor discloses: the PTP messages (see, generate a time synchronization message according to the request message received by the receiving module, section 0047 Wang ‘476)comprising an Announce message (see, PTP configuration indication information and recognition information of the terminal may be framed to generate an announce message, section 0096 Wang ‘476).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han and Zheng with the Announce message as taught by Wang ‘476. The motivation would have been to improve time synchronization with respect to messages.
Claim 3 is rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014), and in further view of Aweya et al. US 20200021378 A1 (Domestic Priority July 16, 2018).
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 3 (Previously Presented), the apparatus of claim 1, wherein the memory and the at least one processor are further configured to: receive, from the first device, one or more updated PTP parameters, wherein at least one parameter of the one or more updated PTP parameters is distinct from the one or more PTP parameters (see, portIdentity of the receiving and transmitting PTP port where portIdentity is a unique value/identifier that is assigned to each PTP port in the PTP domain and comprises the clockIdentity and a portNumber where clockIdentity uniquely identifies the PTP clock, and the portNumber is unique within that PTP clock, sections 0033-0034 Zheng); generate, based on the one or more updated PTP parameters received from the first device, a second PTP message including second time information; and transmit the second PTP message including the second time information to the one or more downstream devices.
However Aweya from a similar field of endeavor discloses: the apparatus of claim 1, wherein the memory and the at least one processor are further configured to: receive, from the first device, one or more updated PTP parameters (see, event messages Sync and Delay_Resp messages in the PTP message that update the PTP message, sections 0009-0010 Aweya), wherein at least one parameter of the one or more updated PTP parameters is distinct from the one or more PTP parameters; generate, based on the one or more updated PTP parameters received from the first device (see, event messages including Follow_Up and Delay-Resp can be used to update time information, section 0010), a second PTP message (see, the sending of a further timing message (PTP Follow_Up message) after a first timing message (PTP Sync message), section 0057 Aweya) including second time information (see, timing message includes timing information, sections 0085-0089; noted, the further timing message also known as a PTP Follow_Up message indicates a second information, section 0091 Aweya); and transmit the second PTP message (see, synchronization message exchanges that includes multiple sending and receiving of PTP event messages, section 0012) including the second time information (see, timing message includes timing information, sections 0085-0089; noted, the further timing message also known as a PTP Follow_Up message indicates a second information, section 0091 Aweya) to the one or more downstream devices (see, transparent clocks information downstream devices of events such as delays, section 0015; noted, transparent clocks act invisibly to the grand master, section 0014 Aweya).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the updated PTP parameters as taught by Aweya. The motivation would have been to provide retransmission.
Claims 4 and 30 rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014), and in further view of Yahagi et al. US 20060116152 A1 (Foreign Priority January 10, 2003).
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 4 (Previously Presented), the apparatus of claim 1, wherein the at least one processor is further configured to: receive, from the first device (fig. 7, the PTP Announce message to select a device such as to assume if it is a master clock, sections 0108-0110), a deactivation message to stop a transmission (see, a Delay_Req message for a PTP message, to request a delay from slave to master, section 0062) of PTP messages (see, the transmission of multiple PTP messages between ports, sections 0089-0090) to the one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015); and refrain from transmitting PTP messages (see, a Delay_Req message for a PTP message, to request a delay from slave to master, section 0062; noted, the transmission of multiple PTP messages between ports, sections 0089-0090) to the one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015) based on the deactivation message.
However Yahagi from a similar field of endeavor discloses: a deactivation message (fig. 17, the base station control device 301 sends a PtP channel transmission stop message for canceling the PtP channel 3 to the base station 201, sections 0098-0112 Yahagi; noted, the downlink transmission power of the PtP channel used for distributing the content to the user terminals , section 0068 Yahagi) to stop a transmission of PTP messages to the one or more downstream devices; and refrain from transmitting PTP messages to the one or more downstream devices based on the deactivation message (fig. 17, the base station control device 301 sends a PtP channel transmission stop message for canceling the PtP channel 3 to the base station 201, sections 0098-0112 Yahagi; noted, the downlink transmission power of the PtP channel used for distributing the content to the user terminals , section 0068 Yahagi).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the PTP stop message as taught by Yahagi. The motivation would have been to stop a device.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 30 (Previously Presented), the apparatus of claim 28, wherein the at least one processor is further configured to: transmit, to the first device, a deactivation message (see, a Delay_Req message for a PTP message, to request a delay from slave to master, section 0062) to stop the first device (fig. 7, the PTP Announce message to select a device such as to assume if it is a master clock, sections 0108-0110) from transmitting PTP messages (fig. 9, processor 901 is configured to execute the program stored in the memory 902 and control the transceiver to send a first PTP message that uses the PTP version of the sending port through the sending port, section 0137; noted, the transmission of multiple PTP messages between ports, sections 0089-0090) to the one or more downstream devices (see, receiving port corresponding to the sending port for devices where the sending port can be a master or slave, sections 0010-0015).
However Yahagi from a similar field of endeavor discloses: a deactivation message (fig. 17, the base station control device 301 sends a PtP channel transmission stop message for canceling the PtP channel 3 to the base station 201, sections 0098-0112 Yahagi; noted, the downlink transmission power of the PtP channel used for distributing the content to the user terminals, section 0068 Yahagi) to stop the first device from transmitting PTP messages to the one or more downstream devices.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the PTP stop message as taught by Yahagi. The motivation would have been to stop a device.
Claim 5 is rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014), and in further view of Saches et al. US 20200259896 A1 (Domestic Priority February 13, 2019).
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 5 (Currently Amended), the apparatus of claim 1, wherein, to generate, based on the one or more PTP parameters, the first PTP message including the first time information (see, a network side device determines the PTP version of the sending port, it can generate the first PTP message that uses the PTP version of the sending port, section 0061), the at least one processor is configured to: generate the first time information based on an absolute timing of radio frames based on a 5G system (5GS) clock, wherein the one or more PTP parameters comprises the absolute timing of radio frames, wherein the first time information comprises the absolute timing of radio frames.
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein, to generate , based on the one or more PTP parameters, the first PTP message including the first time information, the at least one processor is configured to: generate the first time information (see, the use of timing information to improve scheduling of radio resources, section 0773 Saches) based on an absolute timing of radio frames (see, 802.1Qbv standard ensures frames arrive at the 5GS from the TSN network with minimum jitter, section 0773 Saches) based on a 5G system (5GS) clock (see, 5GS transmits frames based on TSN traffic, section 0773 Saches), wherein the one or more PTP parameters comprises the absolute timing of radio frames, wherein the first time information comprises the absolute timing of radio frames.
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the timing information as taught by Saches. The motivation would have been to transmit frames based on a 5G system.
The combination of Han, Zheng, and Wang ‘476, and Saches discloses all the claim limitations as set forth above but fails to explicitly disclose: wherein the one or more PTP parameters comprises the absolute timing of radio frames, wherein the first time information comprises the absolute timing of radio frames.
However Wang ‘778 from a similar field of endeavor discloses: wherein the one or more PTP parameters comprises the absolute timing of radio frames (see, 5G internal system clock can be made available to UE with signaling of time information related to absolute timing of radio frames using System information Block (SIB)/Radio Resource Control (RRC) based methods, section 0045 Wang ‘778; noted, timing information as generalized Precision Time Protocol (gPTP) messages, including the information on the incoming sync message timestamping, section 0046 Wang ‘778), wherein the first time information comprises the absolute timing of radio frames (see, 5G internal system clock can be made available to UE with signaling of time information related to absolute timing of radio frames using System information Block (SIB)/Radio Resource Control (RRC) based methods, section 0045 Wang ‘778).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476, and Saches with the absolute timing of radio frames as taught by Wang ‘778. The motivation would have been to enable 5G system support for conveying time synchronization.
Claims 6- 8, 11-13, 19, 31, 34-35, and 41 are rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014), and in further view of Saches et al. US 20200259896 A1 (Domestic Priority February 13, 2019).
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 6 (Previously Presented), the apparatus of claim 1, wherein, to transmit the first PTP message, the at least one processor is configured to broadcast the first PTP message to the one or more downstream devices.
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein, to transmit the first PTP message, the at least one processor is configured to broadcast (see, the broadcast of message to the UE related to time domain where the UE will only select the time domains from the broadcasted time signal information that it requires for a PTP domain, section 2341 Saches) the first PTP message (see, UE acts as master clock to the TSN end stations using the (g)PTP protocol for use of PTP message exchange as performed in the TSN network, section 1106 Saches) to the one or more downstream devices (see, grandmaster (GM) is a node that transmits timing information to all other nodes in a master-slave architecture which indicates from a grandmaster downstream to slaves, section 2309 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the broadcast of messages as taught by Saches. The motivation would have been to provide broadcasting conditions.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 7 (Previously Presented), the apparatus of claim 1, wherein, to transmit the first PTP message, the at least one processor is configured to multicast the first PTP message to the one or more downstream devices.
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein, to transmit the first PTP message (see, UE acts as master clock to the TSN end stations using the (g)PTP protocol for use of PTP message exchange as performed in the TSN network, section 1106 Saches), the at least one processor is configured to multicast (see, multicast as dedicated RRC or SIB signaling next to the time signal transmission or as part of the time signaling in RRC or SIB messages of an outgoing PTP message, section 2354 Saches) the first PTP message (see, UE acts as master clock to the TSN end stations using the (g)PTP protocol for use of PTP message exchange as performed in the TSN network, section 1106 Saches) to the one or more downstream devices (grandmaster (GM) is a node that transmits timing information to all other nodes in a master-slave architecture, section 1512 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the multicast of messages as taught by Saches. The motivation would have been to provide multicasting conditions.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 8 (Previously Presented), the apparatus of claim 1, wherein to transmit the first PTP message, the at least one processor is configured to unicast the first PTP message to the one or more downstream devices.
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein to transmit the first PTP message, the at least one processor is configured to unicast (see, unicast as dedicated RRC or SIB signaling next to the time signal transmission or as part of the time signaling in RRC or SIB messages of an outgoing PTP message, section 2354 Saches) the first PTP message (see, UE acts as master clock to the TSN end stations using the (g)PTP protocol for use of PTP message exchange as performed in the TSN network, section 1106 Saches) to the one or more downstream devices (grandmaster (GM) is a node that transmits timing information to all other nodes in a master-slave architecture, section 1512 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the unicast of messages as taught by Saches. The motivation would have been to provide unicasting conditions.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 11 (Original), the apparatus of claim 10, wherein the PTP version-type information includes one of generalized PTP (gPTP)/IEEE 802. IAS, PTP over IEEE 802.3/Ethernet, PTP over user datagram protocol (UDP) over Internet protocol version 4 (IPv4), and PTP over UDP over IPv6.
However Saches from a similar field of endeavor discloses: the apparatus of claim 10, wherein the PTP version-type information includes one of generalized PTP (gPTP)/IEEE 802. IAS, PTP over IEEE 802.3/Ethernet (see, time synchronization is based on the exchange of packets containing time information as defined in IEEE 802.1AS-rev, section 0745; noted, the 5G system shall support clock synchronization defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet, section 0754 Saches), PTP over user datagram protocol (UDP) over Internet protocol version 4 (IPv4) (see, an Internet Protocol (IP) is used as for transporting the gPTP frames, section 2391 Saches), and PTP over UDP over IPv6 (see, an Internet Protocol (IP) is used as for transporting the gPTP frames, section 2391 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the PTP version as taught by Saches. The motivation would have been to include internet version of PTP.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 12 (Original), the apparatus of claim 1, wherein the apparatus comprises a device-side (DS) time sensitive networking (TSN) translator (DS-TT), and the first device comprises a user equipment (UE).
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein the apparatus comprises a device-side (DS) time sensitive networking (TSN) translator (DS-TT) (see, 5G device connected to a TSN network, section 0761 Saches; noted, the receiving entity in the 5GC can translate the requested TSN stream requirements to QoS requirements for the UE that is connected to the TSN sensor, section 1254 Saches), and the first device comprises a user equipment (UE) (see, a TSN domain can link between two devices starting with a first UE, section 0759 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the TSN network as taught by Saches. The motivation would have been to provide translation between device and TSN.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 13 (Original), the apparatus of claim 12, wherein the one or more downstream devices includes a device coupled to the apparatus via an Ethernet port.
However Saches from a similar field of endeavor discloses: the apparatus of claim 12, wherein the one or more downstream devices includes a device coupled to the apparatus via an Ethernet port (see, time synchronization is based on the exchange of packets containing time information as defined in IEEE 802.1AS-rev, section 0745; noted, the 5G system shall support clock synchronization defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet, section 0754 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the Ethernet as taught by Saches. The motivation would have been to include internet version of PTP.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: the apparatus of claim 1, Regarding claim 19 (Original), wherein the apparatus comprises a user equipment (UE), and the first device comprises a base station.
However Saches from a similar field of endeavor discloses: the apparatus of claim 1, wherein the apparatus comprises a user equipment (UE) (fig. 165, radio network node 12 is configured to receive from the UE 10 data on a radio resource, sections 1626-1629; noted, fig. 195, network node 1300 may be referred as a base station, section 1879 Saches), and the first device comprises a base station (fig. 165, radio network node 12 is configured to receive from the UE 10 data on a radio resource, sections 1626-1629; noted, fig. 195, network node 1300 may be referred as a base station, section 1879 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the UE and base station as taught by Saches. The motivation would have been to provide network specification.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 31 (Original), the apparatus of claim 28, wherein the time information is related to an absolute timing of radio frames based on a 5G system (5GS) clock.
However Saches from a similar field of endeavor discloses: the apparatus of claim 28, wherein the time information (see, the use of timing information to improve scheduling of radio resources, section 0773 Saches) is related to an absolute timing of radio frames (see, 802.1Qbv standard ensures frames arrive at the 5GS from the TSN network with minimum jitter, section 0773 Saches) based on a 5G system (5GS) clock (see, 5GS transmits frames based on TSN traffic, section 0773 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the timing information as taught by Saches. The motivation would have been to transmit frames based on a 5G system.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 34 (Original), the apparatus of claim 33, wherein the PTP version-type information includes one of generalized PTP (gPTP)/IEEE 802. IAS, PTP over IEEE 802.3/Ethernet, PTP over user datagram protocol (UDP) over Internet protocol version 4 (IPv4), and PTP over UDP over IPv6.
However Saches from a similar field of endeavor discloses: the apparatus of claim 33, wherein the PTP version-type information includes one of generalized PTP (gPTP)/IEEE 802. IAS, PTP over IEEE 802.3/Ethernet (see, time synchronization is based on the exchange of packets containing time information as defined in IEEE 802.1AS-rev, section 0745; noted, the 5G system shall support clock synchronization defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet, section 0754 Saches), PTP over user datagram protocol (UDP) over Internet protocol version 4 (IPv4) (see, an Internet Protocol (IP) is used as for transporting the gPTP frames, section 2391 Saches, see, UDP/TCP/IP in section 1116, or PTP messages using UDP/IP), and PTP over UDP over IPv6 (see, an Internet Protocol (IP) is used as for transporting the gPTP frames, section 2391 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the PTP version as taught by Saches. The motivation would have been to include internet version of PTP.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 35 (Original), the apparatus of claim 28, wherein the apparatus comprises a user equipment (UE), and the first device comprises a device-side (DS) time sensitive networking (TSN) translator (DS-TT).
However Saches from a similar field of endeavor discloses: the apparatus of claim 28, wherein the apparatus comprises a user equipment (UE) (see, a TSN domain can link between two devices starting with a first UE, section 0759 Saches), and the first device comprises a device-side (DS) time sensitive networking (TSN) translator (DS-TT) (see, 5G device connected to a TSN network, section 0761 Saches; noted, the receiving entity in the 5GC can translate the requested TSN stream requirements to QoS requirements for the UE that is connected to the TSN sensor, section 1254 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the TSN network as taught by Saches. The motivation would have been to provide translation between device and TSN.
The combination of Han, Zheng, and Wang ‘476 discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 41 (Original), the apparatus of claim 28, wherein the apparatus comprises a base station, and the first device comprises a user equipment (UE).
However Saches from a similar field of endeavor discloses: the apparatus of claim 28, wherein the apparatus comprises a base station (fig. 165, radio network node 12 is configured to receive from the UE 10 data on a radio resource, sections 1626-1629; noted, fig. 195, network node 1300 may be referred as a base station, section 1879 Saches), and the first device comprises a user equipment (UE) (fig. 165, radio network node 12 is configured to receive from the UE 10 data on a radio resource, sections 1626-1629; noted, fig. 195, network node 1300 may be referred as a base station, section 1879 Saches).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476 with the UE and base station as taught by Saches. The motivation would have been to provide network specification.
Claims are rejected under 35 U.S.C. 103 as being unpatentable over Han et al. US 20210243283 A1 (Foreign Priority June 5, 2018) in view of Zheng et al. US 20150318941 A1 (Domestic Priority May 5, 2014), and in further view of Wang et al. US 20180205476 A1 (Foreign Priority July 16, 2014), and in further view of Saches et al. US 20200259896 A1 (Domestic Priority February 13, 2019) as applied claim 12 and 35 above, and in further view of Roberts et al. US 20140226984 A1 (Domestic Priority November 10, 2009).
The combination of Han, Zheng, and Wang ‘476, and Saches discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 14 (Previously Presented), the apparatus of claim 12, wherein, to transmit the first message comprising the capability information, the at least one processor is configured to; transmit the capability information in an uplink port management information container.
However Roberts from a similar field of endeavor discloses: the apparatus of claim 12, wherein, to transmit the first message comprising the capability information (see, PTP message with synchronization information, section 0025 Roberts), the at least one processor is configured to; transmit the capability information (see, the packets containing information within time stamp correction field, section 0037 Roberts; noted, correction fields are used by timing protocol packets such as PTP packets to use transient network elements by measuring them and applying them to said packets to be carried, sections 0027-0028 Roberts) in an uplink port management information container (see, upstream direction of a PTP packet, section 0037 Roberts; noted, a link connected to the port receiving a PTP event message, section 0042 Roberts) comprising the first message (see, an initial PTP message associated with a PTP packet, section 0063 Roberts).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476, and Saches with the transmission of PTP packets as taught by Roberts. The motivation would have been to provide containers for transmission.
The combination of Han, Zheng, and Wang ‘476, and Saches discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 15 (Original), the apparatus of claim 14, wherein, to receive the second message comprising the one or more PTP parameters, the memory and the at least one processor is configured to receive the one or more PTP parameters in a downlink port management information container.
However Roberts from a similar field of endeavor discloses: the apparatus of claim 14, wherein, to receive the second message comprising the one or more PTP parameters (see, PTP message with synchronization information, section 0025 Roberts), the at least one processor is configured to receive the one or more PTP parameters (see, the packets containing information within time stamp correction field, section 0037 Roberts; noted, correction fields are used by timing protocol packets such as PTP packets to use transient network elements by measuring them and applying them to said packets to be carried, sections 0027-0028 Roberts) in a downlink port management information container (see, downstream direction of a PTP packet, section 0037 Roberts; noted, a link connected to the port receiving a PTP event message, section 0042 Roberts) comprising the second message (see, a next PTP message associated with a second PTP packet, section 0065 Roberts).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476, and Saches with the transmission of PTP packets as taught by Roberts. The motivation would have been to provide containers for transmission.
The combination of Han, Zheng, and Wang ‘476, and Saches discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 36 (Previously Presented), the apparatus of claim 35, wherein, to transmit the first message comprising the capability information, the at least one processor is configured to; receive an uplink port management information container comprising the first message.
However Roberts from a similar field of endeavor discloses: the apparatus of claim 35, wherein, to transmit the first message comprising the capability information (see, PTP message with synchronization information, section 0025 Roberts) (see, the packets containing information within time stamp correction field, section 0037 Roberts; noted, correction fields are used by timing protocol packets such as PTP packets to use transient network elements by measuring them and applying them to said packets to be carried, sections 0027-0028 Roberts), the at least one processor is configured to; receive an uplink port management information container (see, upstream direction of a PTP packet, section 0037 Roberts; noted, a link connected to the port receiving a PTP event message, section 0042 Roberts) comprising the first message (see, an initial PTP message associated with a PTP packet, section 0063 Roberts).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476, and Saches with the transmission of PTP packets as taught by Roberts. The motivation would have been to provide containers for transmission.
The combination of Han, Zheng, and Wang ‘476, and Saches discloses all the claim limitations as set forth above but fails to explicitly disclose: Regarding claim 37 (Original), the apparatus of claim 36, wherein, to receive the second message comprising the one or more PTP parameters, the at least one processor is configured to transmit the one or more PTP parameters in a downlink port management information container comprising the second message.
However Roberts from a similar field of endeavor discloses: the apparatus of claim 36, wherein, to receive the second message comprising the one or more PTP parameters (see, PTP message with synchronization information, section 0025 Roberts), the at least one processor is configured to transmit the one or more PTP parameters (see, the packets containing information within time stamp correction field, section 0037 Roberts) in a downlink port management information container (see, downstream direction of a PTP packet, section 0037 Roberts; noted, a link connected to the port receiving a PTP event message, section 0042 Roberts) comprising the second message (see, a next PTP message associated with a second PTP packet, section 0065 Roberts).
In view of the above, it would have been obvious before the effective filling date of the claim invention to a person having ordinary skill in the art of which the claimed invention pertains to modify the combination of Han, Zheng, and Wang ‘476, and Saches with the transmission of PTP packets as taught by Roberts. The motivation would have been to provide containers for transmission.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PATRICK YIPAO PEI whose telephone number is (703)756-1890. The examiner can normally be reached Monday - Friday 9:30 AM to 5:30 PM ET.
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, Kwang Yao can be reached at (571) 272-3182. 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.
/PATRICK YIPAO PEI/Examiner, Art Unit 2473
/KWANG B YAO/Supervisory Patent Examiner, Art Unit 2473
Prosecution Insights