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 .
DETAILED ACTION
Claims 1-20 received on 1/29/2024 have been examined, of which claims 1, 17 and 20 are independent.
Claim Objections
Claims 7, 10, 20 are objected to because of the following informalities:
Claim 7 recites in preamble “a second terminal device”, which appears to refer same second terminal device limitation in claim 1. For proper antecedent basis in the claim, the examiner suggests to amend claim 7 limitation as “[[a]] the second terminal device”.
Claim 10 recites “the network device” (preamble, line 2), which appears to have lack of antecedent basis in the claim. The examiner suggests to amend the limitation as “[[the]] a network device”.
Claim 20 recites “the SL” in acquiring limitation, which has lack of antecedent basis in the claim. The examiner suggests to amend the limitation as “[[the SL]] a sidelink (SL)”.
Appropriate correction is required.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 2, 20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor, or for pre-AIA the applicant regards as the invention.
Claim 2 recites in the third limitation, “the configuration information being targeted at a receiving resource pool used by the first terminal device and/or the second terminal device, wherein the configuration information corresponding to the receiving resource pool is common for the plurality of terminal devices, or the configuration information corresponding to the transmitting resource pool is dedicated for the first terminal device and/or the second terminal device”. It is unclear, how the configuration information targeted at receiving resource pool further specify transmitting resource pool being dedicated. Further, limitation “the configuration information corresponding to the transmitting resource pool is dedicated for the first terminal device and/or the second terminal device” is also recited in the second limitation. To overcome the issue, the examiner suggests to amend the above limitation as “the configuration information being targeted at a receiving resource pool used by the first terminal device and/or the second terminal device, wherein the configuration information corresponding to the receiving resource pool is common for the plurality of terminal devices, or the configuration information corresponding to the receiving resource pool is dedicated for the first terminal device and/or the second terminal device”.
Claim 20 recites limitations of acquiring “and” performing “or” transmitting. It is unclear if acquiring limitation is optional for transmitting limitation or not – if the limitations are to be read as “acquiring and performing” or “transmitting”, or to be read as “acquiring and performing” or “acquiring and transmitting”. In view of claims 1 and 17, the examiner assumes the interpretation as implementing first method of “acquiring and performing” or second method of “transmitting”.
Claim Rejections - 35 USC § 102
(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.
Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Chen et al. (WO 2019061194).
Regarding claim 1, Chen teaches a duplication transmission method for a sidelink (SL) (para 92-96: for eV2X sidelink communication, the BS based SL RB configuration mechanism), performed by a first terminal device (UE 810, fig 8), comprising:
acquiring configuration information, wherein the configuration information is configured to configure a duplication transmission for the SL (step 1, fig 8; para 92: the BS 820 may configure the PC5 RB with appropriate PC5 QoS parameters to UE 810 together with PC5 data duplication/split configuration to UE 810); and
performing a SL transmission process with a second terminal device based on the configuration information (para 96: upon receiving the PC5 RB configuration with the data duplication/data split relevant info, the Tx UE 810 may configure the PC5 RB together with the PDCP entity, RLC entities and logical channels correspondingly, and then transmit on PC5 based on the data duplication/split configuration; para 95-96: unicast V2X SL communication with SL Rx UE 810 and TX UE 810).
Regarding claim 17, Chen teaches a duplication transmission method for a sidelink (SL) (para 92-96: for eV2X sidelink communication, the BS based SL RB configuration mechanism), performed by a network device (BS 820, fig 8), comprising:
transmitting configuration information to at least one terminal device (step 1, fig 8), wherein the configuration information is configured to configure a duplication transmission for the SL (step 1, fig 8; para 92: the BS 820 may configure the PC5 RB with appropriate PC5 QoS parameters to UE 810 together with PC5 data duplication/split configuration to UE 810).
Regarding claim 20, Chen teaches a device (BS 500, fig 5), comprising:
a processor (processor 504, fig 5); and
a memory (memory 506, fig 5), storing a computer program (para 70: the processor 504, the memory 506 work similarly to the processor 304, the memory 306; para 48: the processor 304 typically performs logical and arithmetic operations based on program instructions stored within the memory 306);
wherein the processor is configured to execute the computer program (para 70, 48) to implement:
transmitting configuration information to at least one terminal device, wherein the configuration information is configured to configure a duplication transmission for the SL (step 1, fig 8; para 92: the BS 820 may configure the PC5 RB with appropriate PC5 QoS parameters to UE 810 together with PC5 data duplication/split configuration to UE 810).
Regarding claim 2, Chen further teaches wherein the configuration information conforms to at least one case of: the configuration information being targeted at the first terminal device (para 96: for the unicast V2X SL communication, the BS may have knowledge of the UE pairs that perform unicast V2X SL communication, the BS 820 may also send the PC5 RB configuration with PC5 data duplication/split information to SL Rx UE 810, besides the above mentioned information, the source UE ID corresponding to the Rx PC5 RB is also included).
Regarding claim 3, Chen further teaches wherein the configuration information comprises configuration information corresponding to a duplication transmission employing 2 radio link control (RLC) entities (para 87: two RLC entities and logical channels established for the PC5 RB with data duplication/data spit; para 93-95: multiple RLC configuration included in the PC5 RB configuration).
Regarding claim 4, Chen further teaches wherein the configuration information comprises at least one of primary path information (para 94: Data duplication/split primary path indication indicates which path/leg (RLC entity/LCH) to be used when PDCP data duplication/split is deactivated， which could be identified by LCID), indication information of whether the duplication transmission is activated (para 94: PC5 data duplication indication indicates whether the SL RB to enable/support PC5 data duplication).
Regarding claim 5, Chen further teaches wherein the configuration information comprises at least one of an identity of the first terminal device and/or the second terminal device and an RB identity (para 96: the BS 820 may also send the PC5 RB configuration with PC5 data duplication/split information to SL Rx UE 810, besides the above mentioned information, the source UE ID corresponding to the Rx PC5 RB is also included).
Regarding claim 6, Chen further teaches wherein the configuration information comprises an enable identity of a split transmission (para 94: PC5 RB configuration and PC5 data duplication/split configuration includes PC5 data split indication indicates whether the SL RB to enable/support PC5 data split, data split primary path indication (in terms of LCID)).
Regarding claim 7, Chen further teaches wherein the performing a SL transmission process with a second terminal device based on the configuration information (para 96: upon receiving the PC5 RB configuration with the data duplication/data split relevant info, the Tx UE 810 may configure the PC5 RB together with the PDCP entity, RLC entities and logical channels correspondingly, and then transmit on PC5 based on the data duplication/split configuration; para 95-96: unicast V2X SL communication with SL Rx UE 810 and TX UE 810), comprises:
determining whether to perform the duplication transmission for the SL based on the configuration information (para 94: configuration including PC5 data duplication indication indicates whether the SL RB to enable/support PC5 data duplication; para 92-96, UE 810 configures and transmits on PC5 (sidelink));
determining whether to perform a duplication transmission for an DRB and/or a SRB based on the configuration information (para 40: in fig 2a, for a given data radio bearer (DRB) or signaling radio bearer (SRB) that supports data duplication or data split, there are one PDCP entity 220, two or more radio link control (RLC) entities 231, 232, 233, and two or more logical channels associated with it; para 93-94: the PC5 RB configuration information may include the PC5 RBs that should be set up/released/updated, for each PC5 RB, whether data duplication or data split should be supported is indicated, the PC5 RB is used for SL transmission and or reception is also indicated, the PC5 RB may contain the PDCP, RLC and logical channel configurations, multiple RLC and logical channel configurations may be included, corresponding to the multiple legs of a PC5 RB/PDCP);
determining an RLC entity of performing the duplication transmission based on the configuration information (para 94: data duplication/split primary path indication indicates which path/leg (RLC entity/LCH) to be used); and
determining RLC entities to which data and a data duplicate in the duplication transmission are transmitted, respectively, based on the configuration information (para 87: the maximum number of RLC entities and logical channels to be established may be set as default value or preconfigured or configured by the BS, the system may only allow the data duplication/data split of two legs, two RLC entities and logical channels shall be established for the PC5 RB with data duplication/data split; para 94: multiple RLC configuration).
Regarding claim 8, Chen further teaches
determining whether to perform a split transmission for the SL in a case of the duplication transmission for the SL being not configured (para 105: the UE 1010 may be pre-configured or configured by BS 1020 with a data split threshold, if the data arrived at a PC5 RB is higher than the data split threshold， more carriers should be used for this PC5 RB’s sidelink data scheduling and transmission, thus the data split should be activated to support the data transmission over more carriers; here, the data split is configured, the data duplication is not configured); and
performing a data split transmission through a primary path and a secondary path in a case of determining to perform the split transmission for the SL (para 105: the data split should be activated to support the data transmission over more carriers, additional RLC entity/logical channel may also be established to support the data split operation; para 40: for the PDCP data split, the PDCP entity 220 may deliver the PDCP PDUs to different RLC entities 231, 232, 233 according to pre-configured data split ratio or data split rules).
Regarding claim 9, Chen further teaches performing a single RLC entity transmission in a case of the duplication transmission for the SL being not configured (para 101-102: only one RLC entity and logical channel are established when the PC5 RB that supports data duplication/data split is configured to set up, only one RLC entity and logical channel is used initially until the data duplication/data split is activated by UE or BS).
Regarding claim 10, Chen further teaches wherein the configuration information is configured or pre-configured by the network device (step 1, fig 8; para 92: the BS 820 may configure the PC5 RB with appropriate PC5 QoS parameters to UE 810 together with PC5 data duplication/split configuration to UE 810);
wherein the network device is configured to transmit the configuration information to the first terminal device and the second terminal device, respectively (para 95-96: the PC5 RB configuration with the data duplication/data split relevant info is received by the Tx UE 810, and for the unicast V2X SL communication, the BS 820 may also send the PC5 RB configuration with PC5 data duplication/split information to SL Rx UE 810).
Regarding claim 11, Chen further teaches wherein the configuration information is configured by a target terminal device (fig 9, para 97: Tx UE 910 may send its data duplication/data split relevant configuration to Rx UE 920 via broadcast or dedicated PC5 signaling), and the target terminal device is the first terminal device (TX UE 910, fig 9);
wherein the configuration information is transmitted to the second terminal device through a direct communication interface (fig 9, para 97: Tx UE 910 may send its data duplication/data split relevant configuration to Rx UE 920 via broadcast or dedicated PC5 signaling).
Regarding claim 12, Chen further teaches wherein the configuration information comprises all configuration parameters required to perform the SL transmission process (para 94 describes all the parameters for PC5 RB configuration; para 95: upon receiving the PC5 RB configuration with the data duplication/data split relevant info, the Tx UE 810 may configure the PC5 RB together with the PDCP entity, RLC entities and logical channels correspondingly， and then transmit on PC5 based on the data duplication/split configuration).
Regarding claim 13, Chen further teaches acquiring a first activating signaling (fig 11-12, signaling of PC5 data duplication/split activation/deactivation command), wherein the first activating signaling is configured to indicate to activate the duplication transmission for the SL (para 106: the activation/deactivation command may be delivered through RRC signaling or MAC CE or PDCP control PDU, it may contain a bitmap or list, each bit or entry indicates the PC5 RB which data duplication/data split should be activated or deactivated).
Regarding claim 14, Chen further teaches wherein signaling is configured or pre-configured by a network device (para 106: in fig 11, BS 1120 may send the activation/deactivation command to the Tx UE 1110), and
the signaling comprises the first activating signaling (para 106: in fig 11, BS 1120 may send the activation/deactivation command to the Tx UE 1110, the activation/deactivation command may contain a bitmap or list, each bit or entry indicates the PC5 RB which data duplication/data split should be activated or deactivated).
Regarding claim 15, Chen further teaches wherein the network device is configured to transmit the signaling to the first terminal device and the second terminal device, respectively (para 106: in fig 11, BS 1120 may send the activation/deactivation command to the Tx UE 1110, for the unicast SL communication, if the BS knows which UE pair is performing unicast SL communication, the BS may also send the activation/deactivation command to Rx UE).
Regarding claim 16, Chen further teaches wherein signaling is configured by a target terminal device (para 107: in fig 12, the Tx UE 1210 may send the activation/deactivation command to the Rx UE 1220), the signaling comprises the first activating signaling (para 107: the activation/deactivation command may be delivered through RRC signaling or MAC CE or PDCP control PDU, it may contain a bitmap or list, each bit or entry indicates the PC5 RB which data duplication/data split should be activated or deactivated), and the target terminal device is the first terminal device (TX UE 1210, fig 12);
wherein the signaling is transmitted to the second terminal device through a direct communication interface (para 107: in fig 12, the Tx UE 1210 may send the activation/deactivation command to the Rx UE 1220, the activation/deactivation command may be delivered through RRC signaling or MAC CE or PDCP control PDU).
Regarding claim 18, Chen further teaches transmitting second indicating information to the at least one terminal device (fig 10 – PC5 data duplication/data split activation/deactivation configuration from eNB 1020 to UE1 1010), wherein the second indication information is configured to indicate whether the terminal device is allowed to determine to activate or de-activate the duplication transmission for the SL by itself (para 105: the Tx UE may autonomously initiate the activation/deactivation of data duplication/data split, as shown in FIG. 10, the autonomous activation/deactivation may be based on the dynamic change of data flow, for the data split, the UE 1010 may be pre-configured or configured by BS 1020 with a data split threshold, if the data arrived at a PC5 RB is higher than the data split threshold, more carriers should be used for this PC5 RB’s sidelink data scheduling and transmission, thus the data split should be activated to support the data transmission over more carriers).
Regarding claim 19, Chen further teaches
receiving assistance information transmitted by the at least one terminal device (fig 8; para 95: UE1 810 may send PC5 RB configuration request/PC5 data duplication/split request to BS 820);
performing determining an activated and/or de-activated duplication transmission of the SL (para 93-95: the BS 820 may configure the PC5 RB with appropriate PC5 QoS parameters to UE 810 together with PC5 data duplication/split configuration to UE 810, configuration parameters including PC5 data duplication indication indicates whether the SL RB to enable/support PC5 data duplication).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
-Wang et al. (US 20190215685): Para 32: the present disclosure discloses systems and methods for configuring, activating, and deactivating PC5 CA for the purpose of data split or data duplication.
- Kousaridas et al. (WO 2021089136): para 140: in accordance with an embodiment, the ECU 1308 of the source vehicle 1302 is configured to select a duplication mode or a split mode to communicate a plurality of data packets to the target vehicle 1304 via the cellular communication path 1316 and the sidelink communication path 1318.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to RINA C PANCHOLI whose telephone number is (571)272-2679. The examiner can normally be reached M-F 7:30am-4pm.
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, Chirag Shah can be reached on 571-272-3144. 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.
/RINA C PANCHOLI/Primary Examiner, Art Unit 2477 1/7/2026