Prosecution Insights
Last updated: April 19, 2026
Application No. 18/580,621

WIRELESS TELECOMMUNICATIONS SYSTEM AND METHOD

Non-Final OA §102§103
Filed
Jan 19, 2024
Examiner
IQBAL, KHAWAR
Art Unit
2643
Tech Center
2600 — Communications
Assignee
Sony Group Corporation
OA Round
1 (Non-Final)
73%
Grant Probability
Favorable
1-2
OA Rounds
3y 6m
To Grant
99%
With Interview

Examiner Intelligence

Grants 73% — above average
73%
Career Allow Rate
466 granted / 639 resolved
+10.9% vs TC avg
Strong +29% interview lift
Without
With
+28.8%
Interview Lift
resolved cases with interview
Typical timeline
3y 6m
Avg Prosecution
34 currently pending
Career history
673
Total Applications
across all art units

Statute-Specific Performance

§101
3.2%
-36.8% vs TC avg
§103
52.9%
+12.9% vs TC avg
§102
30.8%
-9.2% vs TC avg
§112
5.4%
-34.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 639 resolved cases

Office Action

§102 §103
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)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claim(s) 1-6 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by SHRESTHA et al (20220046486). Regarding claim 1, SHRESTHA et al discloses, an infrastructure equipment (504A, 504B, fig. 5) for providing a wireless interface to a communications node (506, fig. 5) in a wireless communications network, the infrastructure equipment configured to support a wireless backhaul configuration for the communications node, wherein in the wireless backhaul configuration the communications node is configured to provide a wireless backhaul between one or more communications devices (502a, 502b, 502N, fig. 5) and the infrastructure equipment, the infrastructure equipment comprising (abstract, fig. 4-11): a transmitter configured to transmit, via a wireless access interface, signals to the communications node (506, fig. 5) (¶ 0067-0068, FIG. 5 is an example communication flow 500 between a group of UEs and a base station that communicates via a satellite. As illustrated in FIG. 5, a group of UEs 502 including one or more UEs 502A, 502B, and 502N are in communication 510 with a base station 504A via a satellite 506. The UEs 502A-502N may have an RRC connection with the base station 504A, for example. In some aspects, communication 510 between the base station 504A and the UEs in the group of UEs 502 may be exchanged via the satellite 506. The communication 510 may include data, control, etc. The communication 510 may include downlink communication and/or uplink communication); a receiver configured to receive, via the wireless access interface, signals from the communications node (¶ 0067-0068, FIG. 5 is an example communication flow 500 between a group of UEs and a base station that communicates via a satellite. As illustrated in FIG. 5, a group of UEs 502 including one or more UEs 502A, 502B, and 502N are in communication 510 with a base station 504A via a satellite 506. The UEs 502A-502N may have an RRC connection with the base station 504A, for example. In some aspects, communication 510 between the base station 504A and the UEs in the group of UEs 502 may be exchanged via the satellite 506. The communication 510 may include data, control, etc. The communication 510 may include downlink communication and/or uplink communication); and a controller configured to determine to handover the communications node (504A, fig. 5) to the other infrastructure equipment (504B, fig. 5) (¶ 0069-0070, the base station 504A may determine, at 518, to initiate a group handover for the group of UEs 502. The determination may be based on any of a variety of triggering events. For example, the base station 504A may determine to initiate the group handover based on measurement-based triggering where cell quality for the group of UEs 502 has exceeded or fallen below a configured threshold.); wherein the controller is further configured to operate with the transmitter and receiver to: transmit, to the other infrastructure equipment (504B, fig. 5), one or more handover requests including first node configuration information for the communications node and first device configuration information for each of the one or more communications devices (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); receive, from the other infrastructure equipment (504B, fig. 5), one or more handover request acknowledgements (¶ 0070-0071, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); determine second device configuration information based on the one or more handover request acknowledgements, wherein the second device configuration information for a first communications device of the one or more communications devices is different to the first device configuration information for the first communications device (¶ 0070-0071, Signaling radio bearer 1 (SRB1) information may provide a UE specific configuration, and UE specific integrity protection and ciphering of the RRC message may be applied for the SRB1 information for each individual UE in the group. An SRB-x, such as SRB 3 or SRB 4, may include group specific configuration information and may be protected with security information that is known to each of the UEs in the group. For example, access stratum (AS) security information may be transmitted to the group of UEs 502, and the signaling radio bearer information may be sent to the group of UEs with integrity protection and ciphering based on the AS security information for the group of UEs. A common group AS key may be provided to each UE in the group of UEs 502 upon joining of the group. In some aspects, the common group AS key may be derived using a set of cell specific or group specific parameters. For the group handover, the base station may transmit an RRC message that includes a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration messages may include delta RRC configuration for each UE based on the particular UE's current configuration.); transmit, via the communications node and to the first communications device, the second device configuration information for the first communications device (¶ 0071-0072, the base station 504A may transmit the group handover message 524 comprising multiple RRC messages to the group of UEs 502. The multiple RRC messages may be multiplexed at medium access control (MAC) using one or more same or different logical channel identifiers (LCIDs). Each UE in the group of UEs 502 may attempt to decode all of the RRC messages in the multiplexed RRC messages (such as in SRB1). In some aspects, each UE may utilize a current SRB1 configuration and AS security profile for the particular UE to attempt to decode the multiple RRC messages. A UE in the group of UEs may decode a single RRC message from the multiplexed RRC messages based on the UE's AS security profile, e.g., one RRC message will pass the integrity protection check for the UE). Regarding claim 2, SHRESTHA et al discloses, a first handover request including the first node configuration information, and a second handover request for each of the one or more communications devices including first device configuration information for the respective one or more communications devices (¶ 0066, 0070-0071, 0101, Signaling radio bearer 1 (SRB1) information may provide a UE specific configuration, and UE specific integrity protection and ciphering of the RRC message may be applied for the SRB1 information for each individual UE in the group. An SRB-x, such as SRB 3 or SRB 4, may include group specific configuration information and may be protected with security information that is known to each of the UEs in the group. For example, access stratum (AS) security information may be transmitted to the group of UEs 502, and the signaling radio bearer information may be sent to the group of UEs with integrity protection and ciphering based on the AS security information for the group of UEs. A common group AS key may be provided to each UE in the group of UEs 502 upon joining of the group. In some aspects, the common group AS key may be derived using a set of cell specific or group specific parameters. For the group handover, the base station may transmit an RRC message that includes a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration messages may include delta RRC configuration for each UE based on the particular UE's current configuration and The baseband unit 804 may further include means for transmitting a group handover request for the group of UEs to a target base station. The baseband unit 804 may further include means for receiving a group handover acknowledgment from the target base station). Regarding claim 3, SHRESTHA et al discloses, wherein one or more handover request acknowledgements include a first handover request acknowledgement for each of the one or more of communications devices (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station). Regarding claim 4, SHRESTHA et al discloses, wherein the one or more handover request acknowledgements further comprise a second handover request acknowledgement including the second node configuration information (¶ 0070-0071, 0101, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the baseband unit 804 may further include means for transmitting a group handover request for the group of UEs to a target base station. The baseband unit 804 may further include means for receiving a group handover acknowledgment from the target base station). Regarding claim 5, SHRESTHA et al discloses, wherein the one or more handover request acknowledgements include the second device configuration information (¶ 0066, 0070-0071, 0101, Signaling radio bearer 1 (SRB1) information may provide a UE specific configuration, and UE specific integrity protection and ciphering of the RRC message may be applied for the SRB1 information for each individual UE in the group. An SRB-x, such as SRB 3 or SRB 4, may include group specific configuration information and may be protected with security information that is known to each of the UEs in the group. For example, access stratum (AS) security information may be transmitted to the group of UEs 502, and the signaling radio bearer information may be sent to the group of UEs with integrity protection and ciphering based on the AS security information for the group of UEs. A common group AS key may be provided to each UE in the group of UEs 502 upon joining of the group. In some aspects, the common group AS key may be derived using a set of cell specific or group specific parameters. For the group handover, the base station may transmit an RRC message that includes a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration messages may include delta RRC configuration for each UE based on the particular UE's current configuration and The baseband unit 804 may further include means for transmitting a group handover request for the group of UEs to a target base station. The baseband unit 804 may further include means for receiving a group handover acknowledgment from the target base station). Regarding claim 6, SHRESTHA et al discloses, wherein the first node configuration includes one or more of channel configuration information, backhaul configuration information, and address configuration information (¶ 0066, 0070-0071, 0101, Signaling radio bearer 1 (SRB1) information may provide a UE specific configuration, and UE specific integrity protection and ciphering of the RRC message may be applied for the SRB1 information for each individual UE in the group. An SRB-x, such as SRB 3 or SRB 4, may include group specific configuration information and may be protected with security information that is known to each of the UEs in the group. For example, access stratum (AS) security information may be transmitted to the group of UEs 502, and the signaling radio bearer information may be sent to the group of UEs with integrity protection and ciphering based on the AS security information for the group of UEs. A common group AS key may be provided to each UE in the group of UEs 502 upon joining of the group. In some aspects, the common group AS key may be derived using a set of cell specific or group specific parameters. For the group handover, the base station may transmit an RRC message that includes a list of RRC reconfiguration messages for multiple UEs. The RRC reconfiguration messages may include delta RRC configuration for each UE based on the particular UE's current configuration and The baseband unit 804 may further include means for transmitting a group handover request for the group of UEs to a target base station. The baseband unit 804 may further include means for receiving a group handover acknowledgment from the target base station). 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. 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. Claim(s) 7-15, 18, 21-22 are rejected under 35 U.S.C. 103 as being unpatentable over SHRESTHA et al (20220046486) in view of Park et al (20240064595). Regarding claims 7, 9, 14, SHRESTHA et al discloses, in ¶ 0031, 0042-0043, 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function AMF 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. SHRESTHA et al does not specifically disclose the infrastructure equipment configured to support a wireless backhaul configuration for a communications node. In the same field of endeavor, Park et al discloses, the infrastructure equipment configured to support a wireless backhaul configuration for a communications node, (¶ 0318, 0434, 0468…, support an access node to receive backhaul link information of neighboring cells and/or neighboring access nodes and may support to determine whether to perform a handover of a wireless device based on the backhaul link information of neighboring cells and/or the neighboring access nodes, based on backhaul link information of neighboring cells and/or neighboring access nodes, an access node may decide a handover of a wireless device depending on service requirements of the wireless device). Therefore, before the effective filing date of the claim invention, it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify the device of SHRESTHA et al by specifically adding feature in order to enhance system performance to the BS can determine whether to transmit the control signal, service performs a handover to a new cell served by an access node with a backhaul link in response to the determination, thus reducing power consumption of the BS in an effective manner. The method allows the BS to transmit control signals to the wireless devices in an efficient manner, thus improving user experience in an easy manner as taught by Park et al. Regarding claims 8, 10, 13, SHRESTHA et al discloses, in ¶ 0031, 0042-0043, 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function AMF 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. SHRESTHA et al does not specifically disclose determining that the other infrastructure equipment will not support the wireless backhaul configuration for the communications node. In the same field of endeavor, Park et al discloses, determining that the other infrastructure equipment will not support the wireless backhaul configuration for the communications node (¶ 0318, 0434-0436, 0447…, FIG. 36, if the first cell does not supports/meets at least one of the service requirements e.g., URLLC service of the wireless device and/or requirements for the device type). Therefore, before the effective filing date of the claim invention, it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify the device of SHRESTHA et al by specifically adding feature in order to enhance system performance to the BS can determine whether to transmit the control signal, service performs a handover to a new cell served by an access node with a backhaul link in response to the determination, thus reducing power consumption of the BS in an effective manner. The method allows the BS to transmit control signals to the wireless devices in an efficient manner, thus improving user experience in an easy manner as taught by Park et al. Regarding claim 9, SHRESTHA et al discloses, in ¶ 0031, 0042-0043, 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function AMF 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. SHRESTHA et al does not specifically disclose the infrastructure equipment configured to support a wireless backhaul configuration for a communications node. In the same field of endeavor, Park et al discloses, the infrastructure equipment configured to support a wireless backhaul configuration for a communications node, (¶ 0318, 0434, 0468…, support an access node to receive backhaul link information of neighboring cells and/or neighboring access nodes and may support to determine whether to perform a handover of a wireless device based on the backhaul link information of neighboring cells and/or the neighboring access nodes, based on backhaul link information of neighboring cells and/or neighboring access nodes, an access node may decide a handover of a wireless device depending on service requirements of the wireless device). Therefore, before the effective filing date of the claim invention, it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify the device of SHRESTHA et al by specifically adding feature in order to enhance system performance to the BS can determine whether to transmit the control signal, service performs a handover to a new cell served by an access node with a backhaul link in response to the determination, thus reducing power consumption of the BS in an effective manner. The method allows the BS to transmit control signals to the wireless devices in an efficient manner, thus improving user experience in an easy manner as taught by Park et al. Regarding claim 11, SHRESTHA et al discloses, wherein the indication is included in a message received by the infrastructure equipment, from the other infrastructure equipment, prior to transmitting the one or more handover requests (see claims 1 and 7, further, ¶ 0031, 0042-0043, 0071-0073, (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station; the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.). Regarding claim 11, SHRESTHA et al discloses, wherein the indication is included in a message received by the infrastructure equipment, from the other infrastructure equipment, prior to transmitting the one or more handover requests (see claims 1 and 7, further, ¶ 0031, 0042-0043, 0071-0073, (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station; the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.). Regarding claim 15, SHRESTHA et al discloses, wherein the second device configuration information for the first communications device indicates that the first communications device is to connect directly to the other infrastructure equipment (see claim 1 and 8, further, ¶ 0041, 0104, to connect to the target base station, in some aspects, the UE decodes one RRC message in the multiplexed RRC messages that is directed to the UE.). Regarding claim 18, SHRESTHA et al discloses, an infrastructure equipment for providing a wireless interface to a communications node in a wireless communications network, the infrastructure equipment comprising (abstract, fig. 1-9): a transmitter configured to transmit, via a wireless access interface, signals to the communications node and to another infrastructure equipment (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); a receiver configured to receive, via the wireless access interface, signals from the communications node and the other infrastructure equipment (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); and a controller is further configured to operate with the transmitter and receiver to: receive, from the other infrastructure equipment, one or more handover requests including first node configuration information for the communications node and first device configuration information for each of the one or more communications devices (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); transmit, to the other infrastructure equipment, one or more handover request acknowledgements, wherein the one or more handover request acknowledgements enable the other infrastructure equipment to determine second device configuration information based on the one or more handover request acknowledgements, wherein the second device configuration information for a first communications device of the one or more communications devices is different to the first device configuration information for the first communications device (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); SHRESTHA et al discloses, in ¶ 0031, 0042-0043, 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function AMF 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. SHRESTHA et al does not specifically disclose the infrastructure equipment configured to support a wireless backhaul configuration for a communications node. In the same field of endeavor, Park et al discloses, the infrastructure equipment configured to support a wireless backhaul configuration for a communications node, wherein in the wireless backhaul configuration communications node is configured to provide a wireless backhaul between one or more communications devices and the infrastructure equipment (¶ 0318, 0434, 0468…, support an access node to receive backhaul link information of neighboring cells and/or neighboring access nodes and may support to determine whether to perform a handover of a wireless device based on the backhaul link information of neighboring cells and/or the neighboring access nodes, based on backhaul link information of neighboring cells and/or neighboring access nodes, an access node may decide a handover of a wireless device depending on service requirements of the wireless device). Therefore, before the effective filing date of the claim invention, it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify the device of SHRESTHA et al by specifically adding feature in order to enhance system performance to the BS can determine whether to transmit the control signal, service performs a handover to a new cell served by an access node with a backhaul link in response to the determination, thus reducing power consumption of the BS in an effective manner. The method allows the BS to transmit control signals to the wireless devices in an efficient manner, thus improving user experience in an easy manner as taught by Park et al. Regarding claim 21, SHRESTHA et al discloses, a device, the device configured to: receive, from an infrastructure equipment for providing a wireless interface to a communications node in a wireless communications network (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station); transmit, to another infrastructure equipment and based on the indication, a signal indicating (¶ 0070-0071, after the base station 504A determines, at 518, to handover the group of UEs 502, the base station 504A may transmit a handover request 520 to the base station 504B and receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station). SHRESTHA et al discloses, in ¶ 0031, 0042-0043, 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. The core network 190 may include an Access and Mobility Management Function AMF 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 e.g., X2 interface. The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless. SHRESTHA et al does not specifically disclose the infrastructure equipment configured to support a wireless backhaul configuration for a communications node. In the same field of endeavor, Park et al discloses, the infrastructure equipment configured to support a wireless backhaul configuration for a communications node, wherein in the wireless backhaul configuration communications node is configured to provide a wireless backhaul between one or more communications devices and the infrastructure equipment (¶ 0318, 0434, 0468…, support an access node to receive backhaul link information of neighboring cells and/or neighboring access nodes and may support to determine whether to perform a handover of a wireless device based on the backhaul link information of neighboring cells and/or the neighboring access nodes, based on backhaul link information of neighboring cells and/or neighboring access nodes, an access node may decide a handover of a wireless device depending on service requirements of the wireless device). Therefore, before the effective filing date of the claim invention, it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify the device of SHRESTHA et al by specifically adding feature in order to enhance system performance to the BS can determine whether to transmit the control signal, service performs a handover to a new cell served by an access node with a backhaul link in response to the determination, thus reducing power consumption of the BS in an effective manner. The method allows the BS to transmit control signals to the wireless devices in an efficient manner, thus improving user experience in an easy manner as taught by Park et al. Regarding claim 22, SHRESTHA et al discloses, wherein the device is a communications device of the one or more communications devices, or wherein the device is the communications node (see claim 21 further, ¶ 0070-0073, receive a handover acknowledgment 522 from the base station 504B. Then the base station 504A may transmit one or more group handover messages 524 to the group of UEs 502. Each UE in the group of UEs processes the group handover message 524, as illustrated at 525, in order to determine that the UE is being handed over to a target base station and the base stations 102 may communicate directly or indirectly e.g., through the EPC 160 or core network 190 with each other over third backhaul links 134 e.g., X2 interface.). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to KHAWAR IQBAL whose telephone number is (571)272-7909. The examiner can normally be reached M-F. 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, Jinsong Hu can be reached at 5712723965. 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. /KHAWAR IQBAL/ Primary Examiner, Art Unit 2643
Read full office action

Prosecution Timeline

Jan 19, 2024
Application Filed
Jan 27, 2026
Non-Final Rejection — §102, §103
Mar 26, 2026
Interview Requested
Apr 01, 2026
Applicant Interview (Telephonic)
Apr 02, 2026
Examiner Interview Summary

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12597354
SYSTEMS AND METHODS FOR IDENTIFYING A VEHICLE ASSET PAIRING
2y 5m to grant Granted Apr 07, 2026
Patent 12587826
Roaming for UE of a NPN
2y 5m to grant Granted Mar 24, 2026
Patent 12580881
METHODS AND SYSTEMS FOR DELAYING MESSAGE NOTIFICATIONS
2y 5m to grant Granted Mar 17, 2026
Patent 12568373
FEDERATED MULTI-ACCESS EDGE COMPUTING AVAILABILITY NOTIFICATIONS
2y 5m to grant Granted Mar 03, 2026
Patent 12563386
METHOD AND APPARATUS FOR SECURITY REALIZATION OF CONNECTIONS OVER HETEROGENEOUS ACCESS NETWORKS
2y 5m to grant Granted Feb 24, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

1-2
Expected OA Rounds
73%
Grant Probability
99%
With Interview (+28.8%)
3y 6m
Median Time to Grant
Low
PTA Risk
Based on 639 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month