DETAILED ACTION
This action is responsive to claims filed on 22 April 2026. Claims 1, 3-5, 9, 11-14, 16, 18, 21, 24, and 39 are pending examination.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
Applicant's arguments filed on 22 April 2026 have been fully considered but they are not persuasive.
Applicant has amended claim 1 to recite wherein in case that the preset information comprises the scheduling signaling of the Uu interface received from the network-side device, or comprises the scheduling signaling of the sidelink interface received through the Uu interface, the preset content comprises 1-bit indication information carried in the scheduling signaling, wherein the 1-bit indication information is used for identifying whether the scheduling signaling is for the relay UE or the remote UE through a value of the 1-bit indication information. The examiner finds that Bag teaches this limitation.
Applicant’s specification explains that the indication information may include either an N-bit indication identifying whether the present information is related to the relay UE or the remote UE, or alternatively a UE identity that is an identity of the relay UE or the remote UE (Spec., [0048]-[0049]). Therefore, under the broadest reasonable interpretation, the claimed identifying information is not limited to only a dedicated 1-bit indication field. Bag teaches scheduling signaling associated with a remote UE through the use of the remote-RNTI. Specifically, the relay UE monitors the remote-RNTI and, the DCI is scrambled with the remote-RNTI so that the relay UE identifies that the received scheduling information is associated with the remote UE (Bag, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]). Bag further discloses transmitting scheduling information, resource allocation information, and sidelink control information associated with the remote UE through the use of the remote-RNTI (Bag, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]). Therefore, the remote-RNTI identifies whether the communicated scheduling information is associated with the relay UE or the remote UE.
Accordingly, the examiner finds that Bag teaches the amended limitation under the broadest reasonable interpretation. Therefore, the rejection of claims 1, 3-5, 9, 11-14, 16, 18, 21, 24, and 39 under U.S.C 102 (a)(1) is maintained.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1, 3-5, 9, 11-14, 16, 18, 21, 24, and 39 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Baghel et al. (US 20180324848 A1) (hereinafter Bag).
Regarding claim 1 and 24, Bag teaches an information transmission method (Bag, see fig. 5 ) / a relay UE (Bag, see fig. 3):
performing communication of preset information with a network-side device, wherein the preset information indicates through a preset content whether the preset information is related to the relay UE or to a remote UE served by the relay UE (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: [0091] FIG. 7 is a flowchart 700 of a method of resource allocation at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 702, the method may receive, on a downlink channel from a network entity, at least one indication including resource allocation information for at least one of the relay UE or a remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to receive, on a downlink channel from a network entity (e.g., base station 462), at least one indication including resource allocation information for at least one of the relay UE 464 or a remote UE 466. At block 704, the method may transmit, on a sidelink channel to the remote UE, the resource allocation information of remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to transmit, on a sidelink channel 430, the resource allocation information to the remote UE 466. [0096] In some aspects, although not shown, the method 700 may determine a first timing advance information, and transmit the first timing advance information to the remote UE 466. Further, in some aspects, determining the first timing advance information may include receiving, from a network entity, a second timing advance information for use in transmissions between the relay UE 464 and the network entity (e.g., base station 462), and setting the first timing advance information equal to the second timing advance information.);
a memory, a transceiver, and a processor (Bag, fig. 3, [0046]-[0053]);
a transceiver is configured to transmit and receive data under a control of the processor (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: [0113] The processing system 1214 may be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium.); and
the processor is configured to read the computer program in the memory to perform the following step (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: See above for paragraph [0113].):
wherein the preset information comprises at least one of the following:
a Scheduling Request (SR) (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag teaches that the remote UE send a scheduling request to the relay UE for sidelink communication. [0105] In some aspects, the resource grant may correspond to an allocation of resources by the relay UE 464 on a sidelink interface for communication between the remote UE 466 and the relay UE 464. In some aspects, the scheduling request may be transmitted according to a code-division multiplexing scheme. In some aspects, receiving the scheduling indication may include receiving SCI including an indication of an upcoming scheduling indication transmission, the indication being different from the scheduling indication and receiving the scheduling indication corresponding to a MAC CE within a data portion of a sidelink transmission from the relay UE 464.);
a scheduling signaling of a Uu interface sent by the network-side device (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the base station transmits downlink scheduling signaling over the Uu interface to the relay UE for resource allocation and scheduling. [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink.);
a Sidelink Buffer Status Reporting Medium Access Control Control Element (Sidelink BSRMAC CE) (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the BSR MAC CE carries buffer status information from the remote UE to the relay UE for scheduling purpose. [0083] For the remote UE 466 linked to the relay 464, the BSR may be similar to an RTS of the relay UE. For example, the BSR may be transmitted as a MAC CE over the sidelink, the remote UE 466 may generate BSR (e.g., for sidelink buffer) and include the BSR as part of the “DATA” transmitted to the relay UE 464. However, the relay UE 464 may extract this part of DATA and discern the contents represented by the BSR message and adjust the scheduling decisions accordingly. To provide the relay UE 464 an indication that there is a BSR MAC CE in the DATA portion of the transmission, the SCI (L1 Signaling) transmitted preceding the data may include a flag to indicate such.);
a scheduling signaling of a sidelink interface transmitted through a Uu interface (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the relay UE receives scheduling information over the Uu interface and then forwards the scheduling of the sidelink resources to the remote UE.[0074] In another example, the eNB such as base station 462 may allocate bulk resources to the relay UE 464, and the relay UE 464 then sub-allocates and forwards the resources to the remote UE 466 in a transparent manner. For example, the base station 462 may transmit an initial resource allocation in accordance with a semi-persistent scheduling (SPS) configuration to the relay UE 464 for both the relay UE 464 and the remote UE 466 resources. The relay UE 464 may then sub-allocate resources from the SPS resources to the remote UE 466. In one instance, the relay UE 464 may allocate one resource at a time. In another instance, as a sub-SPS process, the relay UE 464 may first be informed of the periodicity and then transmit according to n′+X using DCI or a MAC CE.); or
a sidelink interface configured grant confirmation message transmitted through a Uu interface (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the relay UE determines the remote UE based on the RNTI and transmits the sidelink grant to the remote UE over the sidelink interface. [0086] In some aspects, the message may include an index including one or more index values each associated with one of the RNTI of the remote UE 466 and one or more additional RNTIs of one or more distinct remote UEs. For example, the index may be a listing of a plurality of distinct index values each associated with an RNTI of a different remote UE. Although not shown, the method 500 may further determine an index value associated with the remote UE 466, identify/determine the RNTI of the remote UE 466 based on the index value, and determine the sidelink grant for the remote UE 466 based on the RNTI of the remote UE 466. In some aspects, the sidelink grant may be transmitted to the remote UE 466 on the sidelink channel 430 in accordance with a determination of the RNTI based on the index value.);
wherein in case that the preset information comprises the scheduling signaling of the Uu interface received from the network-side device, or comprises the scheduling signaling of the sidelink interface received through the Uu interface, the preset content comprises 1-bit indication information carried in the scheduling signaling, wherein the 1-bit indication information is used for identifying whether the scheduling signaling is for the relay UE or the remote UE through a value of the 1-bit indication information (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: As discussed above, Applicant’s specification (spec. 48-49) explains that the identifying information is not limited to a dedicated 1-bit field and may instead comprise a UE identity. Bag discloses that the scheduling information includes identifying information used by the relay UE to determine which UE the scheduling grant is intended for (see paragraph 62-64). [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink. [0080] For a mode 1 UE, the remote UE 466 may rely on the eNB to allocate PC5 sidelink resource dynamically. For a mode 2 UE, the remote UE 466 may read SIB 21 or use pre-configured sidelink resource to transmit its data over PC5 interface. However, for a UE that is neither in mode 1 nor in mode 2, the UE may be in a third mode where the eNB may not directly be involved in remote resource assignment over sidelink. From the remote UE 466 perspective, the sidelink resources may be assigned by the relay UE 464. In this case, scheduling requests may be transmitted on the sidelink between the remote UE 466 and relay UE 464. [0081] For example, the D2D UEs may perform synchronous resource allocation for SR (or RTS). Unlike asynchronous on-demand RTS operation, the resource to send SR may be short and periodic. The resource may be used to support code-division multiplexing (CDM) such that multiple remote UEs including remote UE 466 can transmit in the resource at the same time. The relay UE 464 may discern the transmitter(s) or distinct remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit of information may be transmitted by each remote UE as a request for relay-allocated resource to be used for sidelink operation.).
Regarding claim 3, blank teaches an information transmission method according to claim 1:
wherein when the preset information comprises the SR, the preset content comprises at least one of the following (Bag, fig. 2c-2D, fig. 9, [0045], [0054]-[0084], [0103]-[0106]: See above for paragraph [0103].):
SR resources used by the SR, wherein different SR resources are configured corresponding to the relay UE and the remote UE; or
SR carrying indication information, wherein the indication information is configured to indicate whether the preset information is intended for the relay UE or the remote UE (Bag, fig. 7, [0091]-[0102], [0103]-[0106]: [0091] FIG. 7 is a flowchart 700 of a method of resource allocation at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 702, the method may receive, on a downlink channel from a network entity, at least one indication including resource allocation information for at least one of the relay UE or a remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to receive, on a downlink channel from a network entity (e.g., base station 462), at least one indication including resource allocation information for at least one of the relay UE 464 or a remote UE 466. At block 704, the method may transmit, on a sidelink channel to the remote UE, the resource allocation information of remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to transmit, on a sidelink channel 430, the resource allocation information to the remote UE 466.), or
the indication information is configured to indicate a UE identity for which the preset information is intended.
Regarding claim 4, Bag teaches an information transmission method according to claim 3:
wherein different SR resources are configured for different remote UEs (Bag, fig. 4, [0054]-[0084]: [0063] In the case where a single RNTI may be determined and forwarded to a corresponding remote UE 466, the relay UE 464 may obtain the single RNTI associated with the remote UE 466 for determining the sidelink grant allocated by the base station 462 for the remote UE 466. The relay UE 464 may perform such procedure for each distinct RNTI associated with different remote UEs. As such, in either case, the relay UE 464 receives an indication including one or more RNTIs of remote UEs 466, and based on the indication, the relay UE 464 may decode PDCCH from the base station 462 to obtain the grant, and passes the grant onto the remote UE 466. [0081] For example, the D2D UEs may perform synchronous resource allocation for SR (or RTS). Unlike asynchronous on-demand RTS operation, the resource to send SR may be short and periodic. The resource may be used to support code-division multiplexing (CDM) such that multiple remote UEs including remote UE 466 can transmit in the resource at the same time. The relay UE 464 may discern the transmitter(s) or distinct remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit of information may be transmitted by each remote UE as a request for relay-allocated resource to be used for sidelink operation.).
Regarding claim 5, Bag teaches an information transmission method according to claim 1:
wherein a triggering condition of the SR comprises one or more of the following:
the relay UE receives the SR sent by the remote UE through the sidelink interface (Bag, fig. 4, [0054]-[0084], [0103]-[0109]: [0105] In some aspects, the resource grant may correspond to an allocation of resources by the relay UE 464 on a sidelink interface for communication between the remote UE 466 and the relay UE 464. In some aspects, the scheduling request may be transmitted according to a code-division multiplexing scheme. In some aspects, receiving the scheduling indication may include receiving SCI including an indication of an upcoming scheduling indication transmission, the indication being different from the scheduling indication and receiving the scheduling indication corresponding to a MAC CE within a data portion of a sidelink transmission from the relay UE 464.);
wherein the SR sent by the remote UE is sent through a dedicated control channel of the sidelink interface;
the relay UE receives the Sidelink BSR MAC CE message sent by the remote UE through the sidelink interface;
the relay UE receives resource allocation mode configuration information for the remote UE sidelink interface, and the resource allocation mode configuration information indicates that the remote UE uses a network-scheduled resource allocation mode on the sidelink interface; or
the relay UE receives a preset instruction sent by the remote UE, the preset instruction is configured to instruct the relay UE to send an SR;
wherein the preset instruction is through at least one of a sidelink interface radio resource control (PC5-RRC) signaling, a sidelink interface Sidelink MAC CE information and sidelink interface Sidelink control information (SCI).
Regarding claim 9, Bag teaches an information transmission method according to claim 1:
wherein when the preset information comprises the scheduling signaling of the sidelink interface transmitted through the Uu interface, after the relay device receives the scheduling signaling of the sidelink interface transmitted through the Uu interface, when the scheduling signaling of the sidelink interface is for the remote UE served by the relay UE, the method further comprises (Bag, [0085]-[0100]: See above for paragraph [0085].):
using at least one of the following methods to forward the received scheduling signaling to the remote UE through the sidelink interface (Bag, fig. 4, [0054]-[0084]: [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink.):
using sidelink interface SCI (Bag, fig. 4, [0054]-[0084]: [0076] Further, to address the timing variance, the remote UE 466 may apply a timing advance to sidelink transmissions. In one example, the relay UE 464 may inform the remote UE 466 of the timing advance to apply. The timing advance may be derived in at least two manners. First, the relay UE 464 may inform the remote UE 466 of the timing advance of the relay UE 464. Such information may be sent as MAC CE or SCI. Second, the relay UE 464 may inform the remote UE 466 of the timing advance. For example, the timing advance may be the relay UE's own TA in addition to a correction (e.g., correction may be within the autonomous correction limit. Further, the timing advance of the relay UE's 464 timing advance in addition to the correction (e.g., correction may be within some limits configured by the eNB). Additionally, the correction may be based on any sidelink transmission from the remote UE 466 and the relay UE 464.);
using a high-level signaling of sidelink interface;
wherein the SCI comprises at least one of the following:
an identity of the relay UE (Bag, fig. 4, [0054]-[0084]: [0056] In an aspect related to the RNTI component 412 at the UE 464 and the RNTI reception component 422 at the remote UE 466, one or more radio network temporary identifier (RNTIs) for D2D based bi-directional relating may be implemented. In some aspects, an RNTI is a physical layer identifier of the UE allocated by a base station (e.g., eNB). Specifically, a D2D relaying may provide efficiency in power and resource utilization. For instance, a remote UE such the remote UE 466 (e.g., smartwatch) may have limited batteries and/or power supply. When the remote UE 466 is communicating with the base station 462, the remote UE 466 may transmit at higher power (e.g., as opposed to communicating with the relay UE 464 on a sidelink). As such, when communicating with the relay UE such as the relay UE 464, the remote UE 466 may consume lower power for transmission and receptions. Hence, relaying assists with conserving power at the remote UE 466. Also, from a resource utilization point of view, the remote UE 466 may reuse at least some of the same resources between the relay UE 464 and the remote UE 466 by the base station 462, thereby increasing system capacity.);
an identity of the remote UE; or
resources for sending a remote UE sidelink interface data and/or control information forwarded by the relay UE, which is allocated by the network-side device.
Regarding claim 11, Bag teaches an information transmission method according to claim 1:
wherein when the preset information comprises the Sidelink BSR MAC CE sent to the network-side device, the preset content comprises at least one of the following (Bag, fig. 4, [0054]-[0084]: [0073] The relay UE 464 may relay the DCI to the remote UE 466. In one instance, the DCI may be sent as sidelink control information (SCI) without any associated data. In another instance, the DCI may be sent as a MAC control element and part of sidelink link shared channel (SL-SCH) data. Additionally, a time ‘X’ after which the allocation applies may be determined such that n′+X=n+T, where n′ is the subframe on which the DCI is relayed to the remote UE 466.):
buffer status information of the relay UE sidelink interface and buffer status information of the remote UE sidelink interface are reported using different Sidelink BSR MAC CEs, and the reported Sidelink BSR MAC CE payload or Sidelink BSR MAC CE sub-header carries a UE identity corresponding to the buffer status information (Bag, fig. 4, [0046]-[0053], [0054]-[0084], [0103]-[0106]: [0078] In an aspect related to the scheduling determination component 416 at the relay UE 464 and the scheduling component 426 at the remote UE 466, scheduling requests (SRs) and buffer status reports (BSRs) on PC5 sidelink interface between the remote UE 466 and the relay UE 464 may be provided. [0106] In some aspects, the scheduling request may be transmitted on a periodic resource. Further, for instance, the periodic resource may be allocated when the remote UE links to the relay UE. In some aspects, the method may further transmit, on the at least one sidelink channel 430, SCI including a flag indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, and transmit, on the at least one sidelink channel 430, a buffer status report as a MAC CE within the data portion.);
buffer status information of the relay UE sidelink interface and buffer status information of the remote UE sidelink interface are reported using the same Sidelink BSR MAC CE, and the Sidelink BSR MAC CE carries a UE identity corresponding to the buffer status information.
Regarding claim 12, Bag teaches an information transmission method according to claim 1:
wherein when the preset information comprises the Sidelink BSR MAC CE sent to the network-side device, the method further comprises (Bag, fig. 4, [0054]-[0084]: See above for paragraph [0073]):
obtaining a sidelink BSR sent by the remote UE through the sidelink interface with the relay UE (Bag, fig. 4, [0054]-[0084]: [0083] For the remote UE 466 linked to the relay 464, the BSR may be similar to an RTS of the relay UE. For example, the BSR may be transmitted as a MAC CE over the sidelink, the remote UE 466 may generate BSR (e.g., for sidelink buffer) and include the BSR as part of the “DATA” transmitted to the relay UE 464. However, the relay UE 464 may extract this part of DATA and discern the contents represented by the BSR message and adjust the scheduling decisions accordingly. To provide the relay UE 464 an indication that there is a BSR MAC CE in the DATA portion of the transmission, the SCI (L1 Signaling) transmitted preceding the data may include a flag to indicate such.);
according to the sidelink BSR, sending the SR to the network-side device through the Uu interface (Bag, fig. 4, [0054]-[0084]: [0081] For example, the D2D UEs may perform synchronous resource allocation for SR (or RTS). Unlike asynchronous on-demand RTS operation, the resource to send SR may be short and periodic. The resource may be used to support code-division multiplexing (CDM) such that multiple remote UEs including remote UE 466 can transmit in the resource at the same time. The relay UE 464 may discern the transmitter(s) or distinct remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit of information may be transmitted by each remote UE as a request for relay-allocated resource to be used for sidelink operation.); and
after obtaining uplink resources sent by the network-side device, sending the Sidelink BSR MAC CE to the network-side device, and indicating through the preset content whether the Sidelink BSR MAC CE is related to the relay UE or to the remote UE served by the relay UE (Bag, fig. 4, [0054]-[0084]: [0083] For the remote UE 466 linked to the relay 464, the BSR may be similar to an RTS of the relay UE. For example, the BSR may be transmitted as a MAC CE over the sidelink, the remote UE 466 may generate BSR (e.g., for sidelink buffer) and include the BSR as part of the “DATA” transmitted to the relay UE 464. However, the relay UE 464 may extract this part of DATA and discern the contents represented by the BSR message and adjust the scheduling decisions accordingly. To provide the relay UE 464 an indication that there is a BSR MAC CE in the DATA portion of the transmission, the SCI (L1 Signaling) transmitted preceding the data may include a flag to indicate such.).
Regarding claim 13, Bag teaches an information transmission method according to claim 1:
wherein when the preset information comprises the sidelink interface configured grant confirmation message transmitted through the Uu interface, the sidelink interface configured grant confirmation message is sent to the network-side device through a sidelink configured grant confirmation MAC CE (Bag, fig. 4, [0046]-[0053], [0054]-[0084], [0103]-[0106]);
wherein the sidelink interface configured grant confirmation MAC CE comprises indication information for indicating whether the sidelink interface configured grant confirmation message is related to the relay UE or to the remote UE served by the relay UE (Bag, fig. 4, [0046]-[0053], [0054]-[0084], [0103]-[0106]: [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink.);
wherein the indication information comprises at least one of the following:
N-bit indication information, wherein a value of the N-bit indication information is used to identify whether the preset information is related to the relay UE or the remote UE (Bag, fig. 4, [0046]-[0053], [0054]-[0084], [0103]-[0106]: [0081] For example, the D2D UEs may perform synchronous resource allocation for SR (or RTS). Unlike asynchronous on-demand RTS operation, the resource to send SR may be short and periodic. The resource may be used to support code-division multiplexing (CDM) such that multiple remote UEs including remote UE 466 can transmit in the resource at the same time. The relay UE 464 may discern the transmitter(s) or distinct remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit of information may be transmitted by each remote UE as a request for relay-allocated resource to be used for sidelink operation.);
wherein N is an integer greater than or equal to 1; or
a UE identity, which is an identity of the relay UE or an identity of the remote UE.
Regarding claim 14, Bag teaches an information transmission method according to claim 1:
wherein when the preset information comprises a sidelink interface configured grant confirmation message transmitted through the Uu interface, the relay UE forwards an end-to-end RRC signaling between the remote UE and the network-side device, the end-to-end RRC signaling is configured to carry the configured grant confirmation message for the remote device (Bag, fig. 3, [0046]-[0053], [0054]-[0084]: [0046] FIG. 3 is a block diagram of an eNB 310 in communication with a UE 350 in an access network. The UE 350 may include at least one of a relay component 410 configured to relay information from the eNB 310 to a remote UE and/or from the remote UE to the eNB 310, or a communication component 420 configured to facilitate sidelink communication with another UE. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.).
Regarding claim 16, Bag teaches an information transmission method performed by a network- side device and comprising:
performing communication of preset information with a relay UE, wherein the preset information indicates through a preset content whether the preset information is related to the relay UE or to a remote UE served by the relay UE (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: [0091] FIG. 7 is a flowchart 700 of a method of resource allocation at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 702, the method may receive, on a downlink channel from a network entity, at least one indication including resource allocation information for at least one of the relay UE or a remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to receive, on a downlink channel from a network entity (e.g., base station 462), at least one indication including resource allocation information for at least one of the relay UE 464 or a remote UE 466. At block 704, the method may transmit, on a sidelink channel to the remote UE, the resource allocation information of remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to transmit, on a sidelink channel 430, the resource allocation information to the remote UE 466. [0096] In some aspects, although not shown, the method 700 may determine a first timing advance information, and transmit the first timing advance information to the remote UE 466. Further, in some aspects, determining the first timing advance information may include receiving, from a network entity, a second timing advance information for use in transmissions between the relay UE 464 and the network entity (e.g., base station 462), and setting the first timing advance information equal to the second timing advance information.);
wherein the preset information comprises at least one of the following:
a Scheduling Request (SR) (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag teaches that the remote UE send a scheduling request to the relay UE for sidelink communication. [0105] In some aspects, the resource grant may correspond to an allocation of resources by the relay UE 464 on a sidelink interface for communication between the remote UE 466 and the relay UE 464. In some aspects, the scheduling request may be transmitted according to a code-division multiplexing scheme. In some aspects, receiving the scheduling indication may include receiving SCI including an indication of an upcoming scheduling indication transmission, the indication being different from the scheduling indication and receiving the scheduling indication corresponding to a MAC CE within a data portion of a sidelink transmission from the relay UE 464.);
a scheduling signaling of a Uu interface sent by the network-side device (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the base station transmits downlink scheduling signaling over the Uu interface to the relay UE for resource allocation and scheduling. [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink.);
a Sidelink Buffer Status Reporting Medium Access Control Control Element (Sidelink BSRMAC CE) (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the BSR MAC CE carries buffer status information from the remote UE to the relay UE for scheduling purpose. [0083] For the remote UE 466 linked to the relay 464, the BSR may be similar to an RTS of the relay UE. For example, the BSR may be transmitted as a MAC CE over the sidelink, the remote UE 466 may generate BSR (e.g., for sidelink buffer) and include the BSR as part of the “DATA” transmitted to the relay UE 464. However, the relay UE 464 may extract this part of DATA and discern the contents represented by the BSR message and adjust the scheduling decisions accordingly. To provide the relay UE 464 an indication that there is a BSR MAC CE in the DATA portion of the transmission, the SCI (L1 Signaling) transmitted preceding the data may include a flag to indicate such.);
a scheduling signaling of a sidelink interface transmitted through a Uu interface (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the relay UE receives scheduling information over the Uu interface and then forwards the scheduling of the sidelink resources to the remote UE.[0074] In another example, the eNB such as base station 462 may allocate bulk resources to the relay UE 464, and the relay UE 464 then sub-allocates and forwards the resources to the remote UE 466 in a transparent manner. For example, the base station 462 may transmit an initial resource allocation in accordance with a semi-persistent scheduling (SPS) configuration to the relay UE 464 for both the relay UE 464 and the remote UE 466 resources. The relay UE 464 may then sub-allocate resources from the SPS resources to the remote UE 466. In one instance, the relay UE 464 may allocate one resource at a time. In another instance, as a sub-SPS process, the relay UE 464 may first be informed of the periodicity and then transmit according to n′+X using DCI or a MAC CE.); or
a sidelink interface configured grant confirmation message transmitted through a Uu interface (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: Bag discloses that the relay UE determines the remote UE based on the RNTI and transmits the sidelink grant to the remote UE over the sidelink interface. [0086] In some aspects, the message may include an index including one or more index values each associated with one of the RNTI of the remote UE 466 and one or more additional RNTIs of one or more distinct remote UEs. For example, the index may be a listing of a plurality of distinct index values each associated with an RNTI of a different remote UE. Although not shown, the method 500 may further determine an index value associated with the remote UE 466, identify/determine the RNTI of the remote UE 466 based on the index value, and determine the sidelink grant for the remote UE 466 based on the RNTI of the remote UE 466. In some aspects, the sidelink grant may be transmitted to the remote UE 466 on the sidelink channel 430 in accordance with a determination of the RNTI based on the index value.);
wherein in case that the preset information comprises the scheduling signaling of the Uu interface received from the network-side device, or comprises the scheduling signaling of the sidelink interface received through the Uu interface, the preset content comprises 1-bit indication information carried in the scheduling signaling, wherein the 1-bit indication information is used for identifying whether the scheduling signaling is for the relay UE or the remote UE through a value of the 1-bit indication information (Bag, fig. 1, fig. 11-14, [0034]-[0042], [0054]-[0084], [0085]-[0119], [0120]-[0125]: As discussed above, Applicant’s specification (spec. 48-49) explains that the identifying information is not limited to a dedicated 1-bit field and may instead comprise a UE identity. Bag discloses that the scheduling information includes identifying information used by the relay UE to determine which UE the scheduling grant is intended for (see paragraph 62-64). [0061] The relay UE 464 may receive the one or more RNTIs, which may include an RNTI of the relay UE 464 and an RNTI of the remote UE 466. The UE 464 may perform scheduling of resources for the remote UE 466 based on the base stations 462 command. Specifically, for the RNTI of the UE relay 464, the relay UE 464 may decode the physical downlink control channel (PDCCH) to determine whether there a downlink and/or uplink grant has been allocated by the base station 462. Similarly, for the RNTI of the remote UE 466, the relay UE 464 may decode the PDCCH to determine whether a grant of sidelink resources has been allocated for the remote UE 466. Based on determining that a grant of sidelink resources has been provided for the remote UE 466, the relay UE 464 may forward the grant or associated RNTI to the remote UE 466 to facilitate bi-directional communication on the sidelink. [0080] For a mode 1 UE, the remote UE 466 may rely on the eNB to allocate PC5 sidelink resource dynamically. For a mode 2 UE, the remote UE 466 may read SIB 21 or use pre-configured sidelink resource to transmit its data over PC5 interface. However, for a UE that is neither in mode 1 nor in mode 2, the UE may be in a third mode where the eNB may not directly be involved in remote resource assignment over sidelink. From the remote UE 466 perspective, the sidelink resources may be assigned by the relay UE 464. In this case, scheduling requests may be transmitted on the sidelink between the remote UE 466 and relay UE 464. [0081] For example, the D2D UEs may perform synchronous resource allocation for SR (or RTS). Unlike asynchronous on-demand RTS operation, the resource to send SR may be short and periodic. The resource may be used to support code-division multiplexing (CDM) such that multiple remote UEs including remote UE 466 can transmit in the resource at the same time. The relay UE 464 may discern the transmitter(s) or distinct remote UEs by identifying different code(s) used in the CDM scheme. In this SR, 1-bit of information may be transmitted by each remote UE as a request for relay-allocated resource to be used for sidelink operation.).
Regarding claim 18, Bag teaches the information transmission according to claim 16:
wherein when the preset information comprises the SR, the preset content comprises at least one of the following UE (Bag, fig. 2c-2D, fig. 9, [0045], [0054]-[0084], [0103]-[0106]: See above for paragraph [0103].):
SR resources used by the SR, wherein different SR resources are configured corresponding to the relay UE and the remote; or
SR carrying indication information, wherein the indication information is configured to indicate whether the preset information is intended for the relay UE or the remote UE (Bag, fig. 7, [0091]-[0102], [0103]-[0106]: [0091] FIG. 7 is a flowchart 700 of a method of resource allocation at a relay UE. The method may be performed by a UE (e.g., UE 464). At block 702, the method may receive, on a downlink channel from a network entity, at least one indication including resource allocation information for at least one of the relay UE or a remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to receive, on a downlink channel from a network entity (e.g., base station 462), at least one indication including resource allocation information for at least one of the relay UE 464 or a remote UE 466. At block 704, the method may transmit, on a sidelink channel to the remote UE, the resource allocation information of remote UE. For example, as described herein, the relay UE 464 and/or the relay component 410 may execute the resource allocation component 414 to transmit, on a sidelink channel 430, the resource allocation information to the remote UE 466.), or
the indication information is configured to indicate a UE identity for which the preset information is intended.
Regarding claim 21, Bag teaches the information transmission according to claim 16:
wherein when the preset information comprises the Sidelink BSR MAC CE sent to the network-side device, the preset content comprises at least one of the following (Bag, [0085]-[0100]: See above for paragraph [0085].):
buffer status information of the relay UE sidelink interface and buffer status information of the remote UE sidelink interface are reported using different Sidelink BSR MAC CEs, and the reported Sidelink BSR MAC CE payload or Sidelink BSR MAC CE sub-header carries a UE identity corresponding to the buffer status information (Bag, fig. 4, [0046]-[0053], [0054]-[0084], [0103]-[0106]: [0078] In an aspect related to the scheduling determination component 416 at the relay UE 464 and the scheduling component 426 at the remote UE 466, scheduling requests (SRs) and buffer status reports (BSRs) on PC5 sidelink interface between the remote UE 466 and the relay UE 464 may be provided. [0106] In some aspects, the scheduling request may be transmitted on a periodic resource. Further, for instance, the periodic resource may be allocated when the remote UE links to the relay UE. In some aspects, the method may further transmit, on the at least one sidelink channel 430, SCI including a flag indicating an upcoming transmission of a buffer status report within a data portion of the upcoming transmission, and transmit, on the at least one sidelink channel 430, a buffer status report as a MAC CE within the data portion.);
buffer status information of the relay UE sidelink interface and buffer status information of the remote UE sidelink interface are reported using the same Sidelink BSR MAC CE, and the Sidelink BSR MAC CE carries a UE identity corresponding to the buffer status information; or
when the preset information comprises the sidelink interface configured grant confirmation message transmitted through the Uu interface, the sidelink interface configured grant confirmation message is obtained through a sidelink configured grant confirmation MAC CE;
wherein the sidelink interface configured grant confirmation MAC CE comprises indication information for indicating whether the sidelink interface configured grant confirmation message is related to the relay UE or to the remote UE served by the relay UE; or
when the preset information comprises a sidelink interface configured grant confirmation message transmitted through the Uu interface, the relay UE forwards an end-to-end RRC signaling between the remote UE and the network-side device, the end-to-end RRC signaling is configured to carry the configured grant confirmation message for the remote device.
Regarding claim 39, Bag teaches a network-side device, comprising:
a memory, a transceiver, and a processor (Bag, fig. 3, [0046]-[0053]);
wherein a memory is configured to store a computer program (Bag, fig. 12, [0112]-[0117]: [0113] The processing system 1214 may be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1210 receives a signal from the one or more antennas 1220, extracts information from the received signal, and provides the extracted information to the processing system 1214, specifically the reception component 1104 In addition, the transceiver 1210 receives information from the processing system 1214, specifically the transmission component 1106, and based on the received information, generates a signal to be applied to the one or more antennas 1220. The processing system 1214 includes a processor 1204 coupled to a computer-readable medium/memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1206 may also be used for storing data that is manipulated by the processor 1204 when executing software. The processing system 1214 further includes at least one of the components 1104, 1106, 412, 414, and 416. The components may be software components running in the processor 1204, resident/stored in the computer readable medium/memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.);
a transceiver is configured to transmit and receive data under a control of the processor (Bag, fig. 12, [0112]-[0117]: [0113] The processing system 1214 may be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1210 receives a signal from the one or more antennas 1220, extracts information from the received signal, and provides the extracted information to the processing system 1214, specifically the reception component 1104 In addition, the transceiver 1210 receives information from the processing system 1214, specifically the transmission component 1106, and based on the received information, generates a signal to be applied to the one or more antennas 1220. The processing system 1214 includes a processor 1204 coupled to a computer-readable medium/memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described supra for any particular apparatus. The computer-readable medium/memory 1206 may also be used for storing data that is manipulated by the processor 1204 when executing software. The processing system 1214 further includes at least one of the components 1104, 1106, 412, 414, and 416. The components may be software components running in the processor 1204, resident/stored in the computer readable medium/memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.); and
the processor is configured to read the computer program in the memory to perform the information transmission method according to claim 16 (Bag, fig. 12, [0112]-[0117]: See above for paragraph [0113].).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Roy et al. (US 20200196387 A1) discloses wireless communication device operating as a network relay device for a remote device in a radio access network. Roy further discloses receiving and decoding a control indication signal from the remote device to determine a time allocation for future sidelink data transmissions.
Lee et al. (US 20180054755 A1) discloses performing buffer status reporting (BSR) for data relayed from a remote user equipment over a sidelink communication link.
Faurie et al. (US 20160338095 A1) discloses transmitting a scheduling request based on sidelink control information indicating a future sidelink data transmission from a remote user equipment.
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Francesca Lima Santos whose telephone number is (571)272-6521. The examiner can normally be reached Monday thru Friday 7:30am-5pm, 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, Marcus R Smith can be reached at (571) 270-1096. 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.
/FRANCESCA LIMA SANTOS/ Examiner, Art Unit 2468
/MARCUS SMITH/Supervisory Patent Examiner, Art Unit 2468
Prosecution Insights