Patent Application 18172888 - METHOD APPARATUS AND COMPUTER PROGRAM - Rejection

Patent Application 18172888 - METHOD APPARATUS AND COMPUTER PROGRAM

Title: METHOD, APPARATUS AND COMPUTER PROGRAM

Application Information

• Invention Title: METHOD, APPARATUS AND COMPUTER PROGRAM
• Application Number: 18172888
• Submission Date: 2025-05-14T00:00:00.000Z
• Effective Filing Date: 2023-02-22T00:00:00.000Z
• Filing Date: 2023-02-22T00:00:00.000Z
• National Class: 370
• National Sub-Class: 331000
• Examiner Employee Number: 82139
• Art Unit: 2642
• Tech Center: 2600

Rejection Summary

• 102 Rejections: 1
• 103 Rejections: 4

Cited Patents

No patents were cited in this rejection.

Office Action Text

    DETAILED ACTION
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
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 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.

Claims 1, 7-15, and 19 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Xu et al, US 20230413139 A1, hereinafter “Xu.”
Consider claim 1. Xu discloses:
a user equipment -reads on wireless device- (1502, fig. 15A; see paragraph [0048]: As used throughout, the term “wireless device” may comprise one or more of: a mobile device, a fixed (e.g., non-mobile) device for which wireless communication is configured or usable, a computing device, a node, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. As non-limiting examples, a wireless device may comprise, for example: a telephone, a cellular phone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a hotspot, a cellular repeater, a vehicle road side unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE), a user terminal (UT), etc.), an access terminal (AT), a mobile station, a handset, a wireless transmit and receive unit (WTRU), a wireless communication device, and/or any combination thereof), comprising: 
at least one processor (See fig. 15A and paragraph [0191]: The processing system 1508 and/or the processing system 1518 may comprise one or more controllers and/or one or more processors…); and 
at least one memory (See fig. 15A and paragraph [0190]: The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively…) storing instructions (See fig. 15A and paragraph [0190]: … Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518, respectively, to carry out one or more of the functionalities (e.g., one or more functionalities described herein and other functionalities of general computers, processors, memories, and/or other peripherals)…) that, when executed with the at least one processor, cause the user equipment at least to: 
receive, from a source cell entity (See paragraph [0205]; FIG. 18 shows an example of an inter cell mobility procedure. A wireless device 1810 may receive, via a source cell, one or more RRC messages 1860 from a source base station 1830…), a physical downlink control channel command -reads on PDCCH order- (See paragraph [0004]: A wireless device may need to maintain communications with a plurality of cells (e.g., a source cell, a neighboring cell, a target cell, etc.). The wireless device may be configured for intercell mobility to maintain communications, for example, if moving from the source cell to a target cell. Latency may be reduced by sharing parameters of a target cell with a wireless device before the wireless device initiates a procedure to communicate with the target cell (e.g., for L1/L2-centric intercell mobility). An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device. The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure…); and
based on the physical downlink control channel command, initiate a random access procedure to one or more target cells (See paragraph [0004]: … An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device. The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure. A target cell for a random-access procedure may be selected based on power levels of the available random-access resources. The wireless device may perform a random-access procedure to connect to the target cell after receiving, and/or after acknowledging receipt, of the DCI using the received preamble and random-access resources).	
 Consider claim 7. Xu teaches claim 1, and further discloses wherein the physical downlink control channel command comprises an indication that the user equipment is to perform contention based random access to the one or more target cells, and wherein initiating the random access procedure comprises performing contention based random access (see paragraphs [0151] and [0159]: FIG. 13A shows an example four-step random access procedure. The four-step random access procedure may comprise a four-step contention-based random access procedure…     The wireless device may send/transmit the third message (e.g., Msg 3 1313), for example, based on (e.g., after or in response to) a successful reception of the second message (e.g., Msg 2 1312) (e.g., using resources identified in the Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in the contention-based random access procedure…).
Consider claim 8. Xu teaches claim 1, and further discloses wherein the physical downlink control channel command comprises at least one of: target cell information or information identifying a plurality of target cells (see paragraph [0221]: Intercell mobility latency may be decreased, for example, based on a wireless device receiving, from a source cell, one or more RRC messages comprising configuration parameters. The configuration parameters may comprise TCI states for a plurality of target cells, a preamble, and/or random access procedure…).	
Consider claim 9. Xu teaches claim 8, and further discloses wherein the physical downlink control channel command comprises target cell information of the one or more target cells, and the target cell information indicates one or more of: 
target cell identity information (See paragraph [0004]: … An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device…); and 
target cell frequency information (See fig. 18 and paragraph [0205]: …The source base station 1830 may send (e.g., transmit) a HO request message 1866 to the target base station 1840. The HO request message 1866 may comprise an RRC container with necessary information to prepare the handover at side of the target base station 1840. The necessary information may comprise one or more of: a target cell identity (ID), a C-RNTI of the wireless device 1710 in the source base station, RRM configuration comprising wireless device inactive time, basic AS-configuration comprising antenna configuration information (e.g., antenna Info) and downlink carrier frequency…).
Consider claim 10. Xu teaches claim 8, and further discloses selecting the one or more target cells from the plurality of target cells in response to receiving the physical downlink control channel command (see paragraphs [0004], [0225], and [0226]: A wireless device may need to maintain communications with a plurality of cells (e.g., a source cell, a neighboring cell, a target cell, etc.). The wireless device may be configured for intercell mobility to maintain communications, for example, if moving from the source cell to a target cell. Latency may be reduced by sharing parameters of a target cell with a wireless device before the wireless device initiates a procedure to communicate with the target cell (e.g., for L1/L2-centric intercell mobility). An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device. The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure. A target cell for a random-access procedure may be selected based on power levels of the available random-access resources. The wireless device may perform a random-access procedure to connect to the target cell after receiving, and/or after acknowledging receipt, of the DCI using the received preamble and random-access resources…     As described herein, a mobility procedure based on low layers signaling may be enhanced, for example, if a source cell shares reference signals of a plurality of second cells with a wireless device, and the wireless device selects a target cell from the plurality of second cells after acknowledging receipt of the reference signals and based on the reference signal received power levels. A wireless device may receive, via a first cell, configuration parameters of a second cell. The configuration parameters may indicate a plurality of reference signals associated with preambles of the second cell…     As described herein, a mobility procedure may be enhanced, for example, if a source cell shares reference signals of a plurality of second cells with a wireless device, and the wireless device selects a target cell, based on the reference signal received power levels, from the plurality of second cells after receipt of the reference signals...).
Claim 11 discloses a source cell entity to operate with the user equipment of claim 1; therefore, similar rejection rationale applies.	
Consider claim 12. Xu teaches claim 11, and further discloses wherein the mobility request comprises user equipment context information (see paragraph [0088] An RRC connection may be established for the wireless device. For example, this may be during an RRC connected state. During the RRC connected state (e.g., during the RRC connected 602), the wireless device may have an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNBs 160 or ng-eNB s 162 shown in FIG. 1B, the base station 220 shown in FIG. 2A and FIG. 2B, or any other base stations). The base station with which the wireless device is connected (e.g., has established an RRC connection) may have the RRC context for the wireless device. The RRC context, which may be referred to as a wireless device context (e.g., the UE context), may comprise parameters for communication between the wireless device and the base station. These parameters may comprise, for example, one or more of: AS contexts; radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, a signaling radio bearer, a logical channel, a QoS flow, and/or a PDU session); security information; and/or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information). During the RRC connected state (e.g., the RRC connected 602), mobility of the wireless device may be managed/controlled by an RAN (e.g., the RAN 104 or the NG RAN 154). The wireless device may measure received signal levels (e.g., reference signal levels, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals sent from a serving cell and neighboring cells. The wireless device may report these measurements to a serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device may request a handover to a cell of one of the neighboring base stations, for example, based on the reported measurements. The RRC state may transition from the RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., the RRC idle 606) via a connection release procedure 608. The RRC state may transition from the RRC connected state (e.g., RRC connected 602) to the RRC inactive state (e.g., RRC inactive 604) via a connection inactivation procedure 610), and wherein the confirmation of the mobility request comprises confirmation of user equipment context transfer including dedicated preamble identifier for use in the physical downlink control channel command, and wherein the physical downlink control channel command comprises the dedicated preamble identifier (see paragraph [0004]: … The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure).
	Consider claim 13. Xu teaches claim 12, and further discloses wherein the confirmation of the mobility request comprises a first dedicated preamble for use in the physical downlink control channel command and a second dedicated preamble for use in a physical downlink shared channel command (See paragraph [0004]: … The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure…     See paragraph [0082]: …The set of physical channels and physical control channels (e.g., that may be defined by an NR configuration or any other configuration) may comprise one or more of the following channels. A physical broadcast channel (PBCH) may comprise/carry the MIB from the BCH. A physical downlink shared channel (PDSCH) may comprise/carry downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH…).
Consider claim 14. Xu teaches claim 13; and Xu and further discloses determining to use the first dedicated preamble based on one or more requirements associated with the user equipment; and in response to determining to use the first dedicated preamble, send, to the user equipment, the physical downlink control channel command (See paragraph [0206]: … The necessary information to access the target base station 1840 may comprise one or more of: the target cell ID, the new C-RNTI, the target base station security algorithm identifiers for selected security algorithms, a set of dedicated RACH resources).
Consider claim 15. Xu teaches claim 14; and Xu and further discloses wherein the one or more requirements associated with the user equipment comprise at least one quality of service requirement and/or at least one quality of experience requirement (See paragraph [0068]: FIG. 3 shows an example of protocol layers. The protocol layers may comprise, for example, protocol layers of the NR user plane protocol stack. One or more services may be provided between protocol layers. SDAPs (e.g., SDAPS 215 and 225 shown in FIG. 2A and FIG. 3) may perform Quality of Service (QoS) flow handling. A wireless device (e.g., the wireless devices 106, 156A, 156B, and 210) may receive services through/via a PDU session, which may be a logical connection between the wireless device and a DN. The PDU session may have one or more QoS flows 310. A UPF (e.g., the UPF 158B) of a CN may map IP packets to the one or more QoS flows of the PDU session, for example, based on one or more QoS requirements (e.g., in terms of delay, data rate, error rate, and/or any other quality/service requirement). The SDAPs 215 and 225 may perform mapping/de-mapping between the one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping/de-mapping between the one or more QoS flows 310 and the radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and the radio bearers 320 via reflective mapping and/or control signaling received from the base station 220. For reflective mapping, the SDAP 225 of the base station 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be monitored/detected/identified/indicated/observed by the SDAP 215 of the wireless device 210 to determine the mapping/de-mapping between the one or more QoS flows 310 and the radio bearers 320).
	Claim 19 discloses a target cell entity to operate with the user equipment of claim 1 and the source cell entity of claim 11; therefore, similar rejection rationale applies.
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 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 set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claim 9 is rejected under 35 U.S.C. 103(a) as being unpatentable over Xu et al, US 20230413139 A1, hereinafter “Xu,” in view of Geng et al., US 20220167235 A1, hereinafter “Geng.”
Consider claim 9. Xu teaches claim 8, and further discloses wherein the physical downlink control channel command comprises target cell information of the one or more target cells, and the target cell information indicates one or more of: 
target cell identity information (See paragraph [0004]: … An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device…); and 
target cell frequency information (See fig. 18 and paragraph [0205]: …The source base station 1830 may send (e.g., transmit) a HO request message 1866 to the target base station 1840. The HO request message 1866 may comprise an RRC container with necessary information to prepare the handover at side of the target base station 1840. The necessary information may comprise one or more of: a target cell identity (ID), a C-RNTI of the wireless device 1710 in the source base station, RRM configuration comprising wireless device inactive time, basic AS-configuration comprising antenna configuration information (e.g., antenna Info) and downlink carrier frequency…).
But Xu is silent regarding wherein the physical downlink control channel command comprises target cell information of the one or more target cells, and the target cell information indicates one or more of:
an absolute radio frequency channel number of the target cell; an absolute frequency point A of the target cell; and/or an absolute frequency of synchronization signal block of the target cell.
Geng, however, in related art, suggests wherein the physical downlink control channel command comprises target cell information of the one or more target cells, and the target cell information indicates one or more of: an absolute radio frequency channel number of the target cell, an absolute frequency point A of the target cell, or an absolute frequency of synchronization signal block of the target cell (see paragraph [0142]: An original base station sends configuration information of a CHO to a terminal device when source link quality is relatively good. The configuration information of the conditional handover may include a handover triggering condition and information about one or more candidate cells. Specifically, the information about the one or more candidate cells may include a PCI of a candidate cell and frequency information corresponding to the candidate cell. The frequency information corresponding to the candidate cell may include one or more of the following an absolute frequency of a synchronization signal block SSB, an absolute frequency location (for example, absoluteFrequencyPointA) of a reference resource module (common RBo), a frequency bandwidth list (for example, frequencyBandList), and a subcarrier spacing (SCS)-specific carrier list (for example, scs-SpecificCarrierList). After receiving the configuration information of the conditional handover, the UE determines, based on the configuration information, whether each candidate cell meets the handover triggering condition, and uses a candidate cell that meets the handover triggering condition as a target cell. After determining the target cell, the UE initiates a random access procedure to the target cell. After random access is completed, the UE sends an RRC message (for example, an RRC reconfiguration complete message) to a base station (namely, a target base station) to which the target cell belongs, to notify the target base station of completion of the conditional handover).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention, to consider Geng’s teachings in relation to the claimed invention, thus providing means for avoiding failure and improving handover in a term evolution (LTE) system or a new radio (NR) system, as suggested by Geng (see paragraph [0004]).
Claims 2, 16, and 17 are rejected under 35 U.S.C. 103(a) as being unpatentable over Xu et al, US 20230413139 A1, hereinafter “Xu,” in view of Shrestha et al., US 20230403538 A1, hereinafter “Shrestha.”
Consider claim 2. Xu teaches claim 1, but is silent regarding wherein the physical downlink control channel command comprises integrity information, and wherein the instructions, when executed with the at least one processor cause the user equipment to perform an integrity check of the command based on the integrity information and initiate the random access procedure based on a result of the integrity check.
Shrestha, in related art, suggests wherein the physical downlink control channel command comprises integrity information (see paragraph [0018]: Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a downlink control information (DCI) over a physical downlink control channel (PDCCH), the DCI scheduling a physical downlink shared channel (PDSCH), the DCI including a group radio network temporary identifier (G-RNTI) or a system information radio network temporary identifier (SI-RNTI) for the integrity information and where receiving the first control signaling indicating the configuration associated with the target network node in the non-terrestrial network may be based on the DCI), and wherein the instructions, when executed with the at least one processor cause the user equipment to perform an integrity check of the command based on the integrity information and initiate the random access procedure based on a result of the integrity check (see paragraph [0031]: Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing an integrity check of the first UE-group configuration to obtain the trust status of the first UE-group configuration and where performing the connection operation may be based on the integrity check of the first UE-group configuration).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention, to consider Shrestha’s teachings in relation to the claimed invention, thus providing means to obtain the trust status of the UE-group configuration, as discussed by Shrestha (see paragraph [0134]).
Consider claim 16. Xu teaches claim 11, but is silent regarding wherein the physical downlink control channel command comprises integrity information.
Shrestha, in related art, suggests wherein the physical downlink control channel command comprises integrity information (see paragraph [0018]: Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a downlink control information (DCI) over a physical downlink control channel (PDCCH), the DCI scheduling a physical downlink shared channel (PDSCH), the DCI including a group radio network temporary identifier (G-RNTI) or a system information radio network temporary identifier (SI-RNTI) for the integrity information and where receiving the first control signaling indicating the configuration associated with the target network node in the non-terrestrial network may be based on the DCI).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention, to consider Shrestha’s teachings in relation to the claimed invention, thus providing means to obtain the trust status of the UE-group configuration, as discussed by Shrestha (see paragraph [0134]).
Consider claim 17. Xu in view of Shrestha teaches claim 16; and Xu further suggests wherein the physical downlink control channel command comprises target cell information of the one or more target cells, and the target cell information indicates one or more of: 
target cell identity information (See paragraph [0004]: … An identifier (e.g., a physical cell identifier (PCI)) may be included in downlink control information (DCI) to indicate a target cell for the wireless device…); and 
target cell frequency information (See fig. 18 and paragraph [0205]: …The source base station 1830 may send (e.g., transmit) a HO request message 1866 to the target base station 1840. The HO request message 1866 may comprise an RRC container with necessary information to prepare the handover at side of the target base station 1840. The necessary information may comprise one or more of: a target cell identity (ID), a C-RNTI of the wireless device 1710 in the source base station, RRM configuration comprising wireless device inactive time, basic AS-configuration comprising antenna configuration information (e.g., antenna Info) and downlink carrier frequency…).
Claims 3-6 and 20 are rejected under 35 U.S.C. 103(a) as being unpatentable over Xu et al, US 20230413139 A1, hereinafter “Xu,” in view Park et al., US 12156083 B2, hereinafter “Park.”
Consider claim 3. Xu teaches claim 1, but is silent regarding sending, to a target cell entity providing at least one of the one or more target cells, a random access channel request; and receive, from the target cell entity, a random access channel response comprising information indicating an uplink and/or downlink resource grant.
Park, in related art, suggests sending, to a target cell entity providing at least one of the one or more target cells, a random access channel request; and receive, from the target cell entity, a random access channel response comprising information indicating an uplink and/or downlink resource grant (See column 40 lines 64-67 through column 41 lines 1-2: The electronic device of claim 1, wherein the at least one processor is further configured to transmit a random access channel (RACH) request message to a target cell, as at least a portion of an operation for performing the conditional handover to the target cell to which the conditional handover is determined to be performed).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention, to consider Park’s teachings in relation to the claimed invention, thus providing means to avoid delay when a UE performs a handover according to satisfaction of a handover execution condition during an ultra-low latency service, as suggested by Park (see column 1 lines 54-67 through column 2 lines 1-7).
Consider claims 4 and 20. Xu in view of Park teaches claims 3 and 19; and Xu further suggests wherein the physical downlink control channel command comprises a first dedicated preamble identifier, and wherein the random access channel request comprises a first dedicated preamble corresponding to the first dedicated preamble identifier (see paragraph [0004]: … The DCI may schedule a transmission using a physical downlink control channel (PDCCH) order that may include the identifier (e.g., a PCI), a preamble, and/or random-access resources that a wireless device may use to connect to an indicated target cell using a random-access procedure).
Consider claim 5. Xu in view of Park teaches claim 3; and Xu further suggests sending a radio resource control request to the target cell entity based on the indicated uplink resource grant (see paragraph [0150]: A network (e.g., an NR network comprising a gNB and/or an ng-eNB) and/or the wireless device may initiate/start/perform a random access procedure. A wireless device in an RRC idle (e.g., an RRC_IDLE) state and/or an RRC inactive (e.g., an RRC_INACTIVE) state may initiate/perform the random access procedure to request a connection setup to a network…).
Consider claim 6. Xu in view of Park teaches claim 5; and Xu further suggests wherein the radio resource control request comprises one of: a re-establishment request; a resume request; a handover request; or a redirection request (see fig. 18 and paragraph [0205]: …The HO request message 1866 may comprise an RRC container with necessary information to prepare the handover at side of the target base station 1840…).
Claim 18 is rejected under 35 U.S.C. 103(a) as being unpatentable over Xu et al, US 20230413139 A1, hereinafter “Xu,” in view of Cirik et al., US 12069582 B2, hereinafter ”Cirik.” 
Consider claim 18. Xu teaches claim 11, but is silent regarding sending, to the at least one of the one or more target cell entities, information indicating that the physical downlink control channel command has been sent to the user equipment.
Cirik, in related art, suggests sending, to the at least one of the one or more target cell entities, information indicating that the physical downlink control channel command has been sent to the user equipment (see column 21 lines 22-31: The SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention, to consider Cirik’s teachings in relation to the claimed invention, thus providing means to implement an enhanced procedure for calculating/determining a transmission power for a random-access preamble transmission via a second cell when a wireless device receives a PDCCH order, via a first cell, indicating a random-access procedure for the second cell that is different from the first cell, as discussed by Cirik (see column 40 lines 43-48).
Pertinent Prior Art
The following references, although not relied upon, are considered to be pertinent prior art since they disclose subject matter related to the invention claimed by the present application, i.e., selecting a random access procedure type in a wireless system.
US 12294897 B2		US 20250142629 A1	US 12244456 B2
US 12041502 B2		US 20240171260 A1	US 20240057192 A1US 20230413281 A1		US 20230363005 A1	US 20230362986 A1
US 20230254836 A1	US 20230224916 A1	US 10856201 B2
US 20230217448 A1	US 20230156857 A1	US 11653393 B2
US 20230138737 A1	US 20230048364 A1	US 20220394577 A1
US 11412422 B2		US 11265774 B2		US 11172513 B2
US 20210136641 A1		
Conclusion
Any response to this Office Action should be faxed to (571) 273-8300 or mailed to:
Commissioner for Patents
P.O. Box 1450
		Alexandria, VA 22313-1450
Hand-delivered responses should be brought to 
Customer Service Window
Randolph Building
401 Dulany Street
Alexandria, VA 22314                                                                                                                                                                           
Any inquiry concerning this communication or earlier communications from the Examiner should be directed to Amancio González, whose telephone number is (571) 270-1106. The Examiner can normally be reached on Monday-Thursday from 8:00am to 5:00pm.    
If attempts to reach the Examiner by telephone are unsuccessful, the Examiner’s supervisor, Rafael Perez-Gutierrez, can be reached at (571) 272-7915. The fax phone number for the organization where this application or proceeding is assigned is (571) 273-8300.             
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only.  For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free) or 703-305-3028.
Any inquiry of a general nature or relating to the status of this application or proceeding should be directed to the receptionist/customer service whose telephone number is (571) 272-2600.

/AMANCIO GONZALEZ/
Primary Examiner, Art Unit 2642
May 8, 2025