IP Library Granted Patent US 12,225,510
Granted Patent B2
US 12,225,510 · App. 18/498,878 · Granted Feb 11, 2025

Resource pool configuration method, resource pool using method, configuration device, and terminal

Inventors: Siqi Liu (Chang'an Dongguan, CN); Zichao Ji (Chang'an Dongguan, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W72/044H04L27/2605H04W24/08H04W56/001H04W72/543
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,225,510
App. No.
18/498,878
Granted
Feb 11, 2025
Kind
B2
Abstract

The present disclosure provide a resource pool configuration method, a resource pool using method, a configuration device, and a terminal. The resource pool obtaining method is applied to a terminal, including: obtaining a first resource pool in at least one of the following manners: obtaining the predefined first resource pool; obtaining the preconfigured first resource pool; or obtaining the configured first resource pool.

Claims (78)

1. A resource pool obtaining method, comprising:

obtaining, by a terminal, a first resource pool in at least one of the following manners: obtaining a predefined first resource pool; obtaining a preconfigured first resource pool; or obtaining a configured first resource pool;

wherein a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total beam number, or a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total synchronization signal block number.

2. The resource pool obtaining method according to claim 1 , wherein at least two of the predefined first resource pool, the preconfigured first resource pool, or the configured first resource pool are compatible, and being compatible comprises at least one of the following:

frequency domain resources are same, time domain resources are same, a frequency domain resource range of one is comprised in a frequency domain resource range of the other, and a time domain resource range of one is comprised in a time domain resource range of the other.

3. The resource pool obtaining method according to claim 1 , further comprising:

obtaining a reconfigured first resource pool, wherein the reconfigured first resource pool is the same as or compatible with at least one of the following: the predefined first resource pool, the preconfigured first resource pool, or the configured first resource pool.

4. The resource pool obtaining method according to claim 1 , further comprising:

monitoring the first resource pool according to a monitoring procedure.

5. The resource pool obtaining method according to claim 4 , wherein the monitoring the first resource pool according to a monitoring procedure comprises at least one of the following:

monitoring the first resource pool in a first time window;

monitoring the first resource pool according to a first periodicity;

monitoring the first resource pool when a corresponding transmission configuration or a corresponding transmission mode is used; or

monitoring the first resource pool when transmission of another resource pool meets a corresponding condition.

6. The resource pool obtaining method according to claim 5 , wherein the corresponding transmission configuration or the corresponding transmission mode comprises at least one of the following:

when broadcasting is needed;

when beam sweeping is needed;

when connection fails;

when a resource pool is reconfigured;

when a resource pool is added;

when a resource pool is released;

when quasi-co-location (QCL) information cannot be obtained; or

when a synchronization source that meets a requirement cannot be found.

7. The resource pool obtaining method according to claim 5 , wherein the corresponding condition comprises at least one of the following:

a bit error rate is higher than a threshold;

a block error rate is higher than a threshold;

a false alarm rate exceeds a threshold;

beam failure recovery;

connection failure recovery; or

connection re-establishment.

8. The resource pool obtaining method according to claim 4 , wherein the monitoring a first resource pool comprises at least one of the following:

performing synchronization in the first resource pool;

performing measurement in the first resource pool;

performing transmission in the first resource pool; or

sensing in the first resource pool.

9. A communications device, comprising: a memory, a processor, and a computer program that is stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, causes the communications device to implement:

obtaining a first resource pool in at least one of the following manners: obtaining a predefined first resource pool; obtaining a preconfigured first resource pool; or obtaining a configured first resource pool;

wherein a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total beam number, or a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total synchronization signal block number.

10. The communications device according to claim 9 , wherein at least two of the predefined first resource pool, the preconfigured first resource pool, or the configured first resource pool are compatible, and being compatible comprises at least one of the following:

frequency domain resources are same, time domain resources are same, a frequency domain resource range of one is comprised in a frequency domain resource range of the other, or a time domain resource range of one is comprised in a time domain resource range of the other.

11. The communications device according to claim 9 , wherein the computer program, when executed by the processor, causes the communications device to further implement:

obtaining a reconfigured first resource pool, wherein the reconfigured first resource pool is the same as or compatible with at least one of the following: the predefined first resource pool, the preconfigured first resource pool, or the configured first resource pool.

12. The communications device according to claim 9 , wherein the computer program, when executed by the processor, causes the communications device to further implement:

monitoring the first resource pool according to a monitoring procedure.

13. The communications device according to claim 12 , wherein the monitoring the first resource pool according to a monitoring procedure comprises at least one of the following:

monitoring the first resource pool in a first time window;

monitoring the first resource pool according to a first periodicity;

monitoring the first resource pool when a corresponding transmission configuration or a corresponding transmission mode is used; or

monitoring the first resource pool when transmission of another resource pool meets a corresponding condition.

14. The communications device according to claim 13 , wherein the corresponding transmission configuration or the corresponding transmission mode comprises at least one of the following:

when broadcasting is needed;

when beam sweeping is needed;

when connection fails;

when a resource pool is reconfigured;

when a resource pool is added;

when a resource pool is released;

when quasi-co-location (QCL) information cannot be obtained; or

when a synchronization source that meets a requirement cannot be found.

15. The communications device according to claim 13 , wherein the corresponding condition comprises at least one of the following:

a bit error rate is higher than a threshold;

a block error rate is higher than a threshold;

a false alarm rate exceeds a threshold;

beam failure recovery;

connection failure recovery; or

connection re-establishment.

16. The communications device according to claim 12 , wherein the monitoring a first resource pool comprises at least one of the following:

performing synchronization in the first resource pool;

performing measurement in the first resource pool;

performing transmission in the first resource pool; or

sensing in the first resource pool.

17. A communications device, comprising: a memory, a processor, and a computer program that is stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, causes the communications device to implement:

configuring a first resource pool of a terminal;

wherein a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total beam number, or a granularity of a time domain and/or frequency domain resource of the first resource pool is a multiple of a total synchronization signal block number.

18. The communications device according to claim 17 , wherein at least two of a predefined first resource pool, a preconfigured first resource pool, or a configured first resource pool are compatible, and being compatible comprises at least one of the following:

frequency domain resources are same, time domain resources are same, a frequency domain resource range of one is comprised in a frequency domain resource range of the other, or a time domain resource range of one is comprised in a time domain resource range of the other.

19. The communications device according to claim 17 , wherein the computer program, when executed by the processor, causes the communications device to further implement:

reconfiguring the first resource pool of the terminal, wherein the reconfigured first resource pool and the configured first resource pool are the same or compatible.

20. A non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the resource pool obtaining method according to claim 1 .

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 1, 2023
From: LIU, SIQI; JI, ZICHAO
To: VIVO MOBILE COMMUNICATION CO.,LTD.
Reel/Frame 065428/0143 →
Priority Claims (1)
CN 201811126468.X · Sep 26, 2018 · national
Continuity (3)
Continuation 17214601 · Mar 26, 2021
Continuation PCTCN2019102515 · Aug 26, 2019
Related Publication 20240064710A1 · Feb 22, 2024
References Cited (41)
US 11601955B2 · Dinan · 2023 [cited by applicant]
US 20170041902A1 · Sheng · 2017 [cited by applicant]
US 20170215203A1 · Lee et al. · 2017 [cited by applicant]
US 20170303240A1 · Basu Mallick et al. · 2017 [cited by applicant]
US 20180020365A1 · Xiong et al. · 2018 [cited by applicant]
US 20180098331A1 · Zhao et al. · 2018 [cited by applicant]
US 20180160418A1 · Luo et al. · 2018 [cited by applicant]
US 20210044956A1 · Kim · 2021 [cited by applicant]
US 20230180264A1 · Kim · 2023 [cited by examiner]
CN 104936187A · 2015 [cited by applicant]
CN 105813204A · 2016 [cited by applicant]
CN 106211332A · 2016 [cited by applicant]
CN 107113803A · 2017 [cited by applicant]
CN 107211470A · 2017 [cited by applicant]
CN 108141847A · 2018 [cited by applicant]
CN 108400837A · 2018 [cited by applicant]
EP 3275268A1 · 2018 [cited by applicant]
WO 2016153548A1 · 2016 [cited by applicant]
WO 2016163106A1 · 2016 [cited by applicant]
Samsung., “Specification impact in case of TDD Pcell for TDD-FDD CA,” 3GPP TSG RAN WG1 #76, R1-140364, pp. 1-2, (Feb. 10-14, 2014). [cited by applicant]
Sony., “D2D Communication Resource Scheduling,” 3GPP TSG-RAN WG1 Meeting #76, R1-140589, (Feb. 10-14, 2014). [cited by applicant]
Sony., “D2D Resource Pool and Scheduling Assignments,” 3GPP TSG-RAN WG1 Meeting #76bis, R1-141571, (Mar. 31-Apr. 4, 2014). [cited by applicant]
Alcatel-Lucent Shanghai Bell, et al., “Resource allocation for D2D broadcast communication,” 3GPP TSG RAN WG1 Meeting #77, R1-142055, pp. 1-7, (May 19-13, 2014). [cited by applicant]
Qualcomm Incorporated, et al., “Introduction of ProSe,” 3GPP TSG-RAN WG2 #86, R2-142750, (May 19-23, 2014). [cited by applicant]
Intel Corporation., “On Remaining Details of Resource Pool Configuration for D2D Communication,” 3GPP TSG RAN WG1 Meeting #78bis, R1-143763, pp. 1-7, (Oct. 6-10, 2014). [cited by applicant]
Intel Corporation., “Remaining details of D2D discovery resource allocation,” 3GPP TSG RAN WG1 Meeting #78bis, R1-143766, pp. 1-8, (Oct. 6-10, 2014). [cited by applicant]
CATT., “Missing Packet due to Half-duplex in PC5,” 3GPP TSG RAN WG2 Meeting #90, R2-152247, pp. 1-4, (May 25-29, 2015). [cited by applicant]
Nokia, et al., “On resource pool design,” 3GPP TSG RAN WG1 Meeting #84bis, R1-162541, (Apr. 11-15, 2016). [cited by applicant]
Samsung., “Remaining issues related to Tx resource selection and pool usage,” 3GPP TSG-RAN WG2 Meeting #95bis, R2-166658, pp. 1-5, (Oct. 10-14, 2016). [cited by applicant]
Intel Corporation., “Design Options for eNB-Controlled and Relay UE-Assisted Resource Allocation,” 3GPP TSG RAN WG1 Meeting #90, R1-1712519, pp. 1-7, (Aug. 21-25, 2017). [cited by applicant]
Panasonic., “Discussion on supporting unicast, groupcast and broadcast via NR sidelink,” 3GPP TSG RAN WG1 Meeting #94, R1-1808646, pp. 1-3, (Aug. 20-24, 2018). [cited by applicant]
NTT Docomo, Inc., “Resource allocation mechanism,” 3GPP TSG RAN WG1 Meeting #94, R1-1809159, pp. 1-7, (Aug. 20-24, 2018). [cited by applicant]
Ericsson., “On coexistence aspects of NR V2X,” 3GPP TSG-RAN WG1 Meeting #94, R1-1809313, (Aug. 20-24, 2018). [cited by applicant]
ITL., “Discussion on NR V2X Synchronization mechanism,” 3GPP TSG-RAN WG1 Meeting #94, R1-1809475, pp. 1-4, (Aug. 20-24, 2018). [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority dated Nov. 27, 2019 as received in Application No. PCT/CN2019/102515. [cited by applicant]
CN Office Action dated Sep. 2, 2021 as received in Application No. 201811126468.X. [cited by applicant]
Extended European Search Report dated Oct. 28, 2021 as received in Application No. 19864058.3. [cited by applicant]
JP First Office Action dated May 31, 2022 as received in Application No. 2021-517375. [cited by applicant]
JP Second Office Action dated Oct. 11, 2022 as received in Application No. 2021-517375. [cited by applicant]
US Office Action dated Mar. 21, 2023 as received in U.S. Appl. No. 17/214,601. [cited by applicant]
First Office Action for U.S. Appl. No. 18/498,888 dated Aug. 8, 2024, 21 Pages. [cited by applicant]