IP Library › Granted Patent US 12,238,714
Granted Patent B2
US 12,238,714 · App. 18/487,332 · Granted Feb 25, 2025

Information determination method and device, and storage medium

Inventors: Jing Shi (Shenzhen, CN); Peng Hao (Shenzhen, CN); Yu Ngok Li (Shenzhen, CN); Xianghui Han (Shenzhen, CN); Xingguang Wei (Shenzhen, CN)
Assignee: ZTE Corporation
H04W72/1273H04W72/0446H04W72/23H04W72/569H04W76/11H04W76/27
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,238,714
App. No.
18/487,332
Granted
Feb 25, 2025
Kind
B2
Abstract

Provided are an information determination method and device and a storage medium. The information determination method includes determining a time domain resource allocation (TDRA) table with a physical downlink control channel (PDCCH) related symbol served as a reference point of a start length indicator value (SLIV).

Claims (30)

1. An information determination method, comprising:

determining, when a first downlink control information (DCI) format and a second DCI format are used for scheduling traffic channel and responsive to a collision in a time domain, a first priority corresponding to the first DCI format higher than a second priority corresponding to the second DCI format to schedule the traffic channel; and

performing subsequent operations in accordance with the first priority corresponding to the first DCI format and the second priority corresponding to the second DCI format,

wherein when the first priority of a new DCI format corresponding to the first DCI format indicates a high priority and a low priority, the second priority of an original DCI format corresponding to the second DCI format is determined to be the low priority.

2. The method of claim 1 , wherein the second DCI format is for non-fallback DCI.

3. The method of claim 1 , wherein determining further comprises determining a lowest priority corresponding to the first DCI format to be equal to the second priority corresponding to the second DCI format.

4. The method of claim 1 , wherein when the second DCI format is used by an ultra-reliable low latency communication (URLLC), the first DCI format is used by an enhanced mobile broadband (eMBB), and

wherein when the second DCI format is used by the eMBB, the first DCI format is used by the URLLC.

5. The method of claim 4 , wherein the URLLC reuses a same or different DCI format as a DCI format used by the eMBB.

6. The method of claim 1 , wherein when a URLLC uses a new DCI format, the first DCI format includes the new DCI format and the second DCI format includes an original DCI format different from the new DCI format.

7. A device comprising:

at least one processor and a memory, the at least one processor is configured to:

determine, when a first downlink control information (DCI) format and a second DCI format are used for scheduling traffic channel and responsive to a collision in a time domain, a first priority corresponding to the first DCI format higher than a second priority corresponding to the second DCI format to schedule the traffic channel; and

perform subsequent operations in accordance with the first priority corresponding to the first DCI format and the second priority corresponding to the second DCI format,

wherein when the first priority of a new DCI format corresponding to the first DCI format indicates a high priority and a low priority, the second priority of an original DCI format corresponding to the second DCI format is determined to be the low priority.

8. The device of claim 7 , wherein the second DCI format is for non-fallback DCI.

9. The device of claim 7 , wherein the at least one processor is further configured to determine a lowest priority corresponding to the first DCI format to be equal to the second priority corresponding to the second DCI format.

10. The device of claim 7 , wherein when the second DCI format is used by an ultra-reliable low latency communication (URLLC), the first DCI format is used by an enhanced mobile broadband (eMBB), and

wherein when the second DCI format is used by the eMBB, the first DCI format is used by the URLLC.

11. The device of claim 10 , wherein the URLLC reuses a same or different DCI format as a DCI format used by the eMBB.

12. The device of claim 7 , wherein when a URLLC uses a new DCI format, the first DCI format includes the new DCI format and the second DCI format includes an original DCI format different from the new DCI format.

13. A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to:

determine, when a first downlink control information (DCI) format and a second DCI format are used for scheduling traffic channel and responsive to a collision in a time domain, a first priority corresponding to the first DCI format higher than a second priority corresponding to the second DCI format to schedule the traffic channel; and

perform subsequent operations in accordance with the first priority corresponding to the first DCI format and the second priority corresponding to the second DCI format,

wherein when the first priority of a new DCI format corresponding to the first DCI format indicates a high priority and a low priority, the second priority of an original DCI format corresponding to the second DCI format is determined to be the low priority.

14. The non-transitory computer readable medium of claim 13 , wherein the second DCI format is for non-fallback DCI.

15. The non-transitory computer readable medium of claim 13 , wherein the instructions further cause the at least one processor to determine a lowest priority corresponding to the first DCI format to be equal to the second priority corresponding to the second DCI format.

16. The non-transitory computer readable medium of claim 14 , wherein when the second DCI format is used by an ultra-reliable low latency communication (URLLC), the first DCI format is used by an enhanced mobile broadband (eMBB), and

wherein when the second DCI format is used by the eMBB, the first DCI format is used by the URLLC.

17. The non-transitory computer readable medium of claim 14 , wherein when a URLLC uses a new DCI format, the first DCI format includes the new DCI format and the second DCI format includes an original DCI format different from the new DCI format.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2023
From: SHI, JING; HAO, PENG; LI, YU NGOK; HAN, XIANGHUI; WEI, XINGGUANG
To: ZTE CORPORATION
Reel/Frame 065231/0712 →
Priority Claims (1)
CN 201910754997.2 · Aug 15, 2019 · national
Continuity (3)
Continuation 17158861 · Jan 26, 2021
Continuation PCTCN2020108091 · Aug 10, 2020
Related Publication 20240163873A1 · May 16, 2024
References Cited (50)
US 10939382B2 · Zhou · 2021 [cited by examiner]
US 11297674B2 · He · 2022 [cited by examiner]
US 11457434B2 · Ying · 2022 [cited by examiner]
US 20140119269A1 · Guan et al. · 2014 [cited by applicant]
US 20150327226A1 · Cheng et al. · 2015 [cited by applicant]
US 20180199229A1 · Lee et al. · 2018 [cited by applicant]
US 20190082431A1 · Yi et al. · 2019 [cited by applicant]
US 20190149365A1 · Chatterjee et al. · 2019 [cited by applicant]
US 20190165846A1 · Kim et al. · 2019 [cited by applicant]
US 20190174466A1 · Zhang et al. · 2019 [cited by applicant]
US 20190182807A1 · Panteleev · 2019 [cited by examiner]
US 20190223084A1 · John Wilson et al. · 2019 [cited by applicant]
US 20190274032A1 · Chatterjee · 2019 [cited by examiner]
US 20190363843A1 · Gordaychik · 2019 [cited by examiner]
US 20200022144A1 · Papasakellariou · 2020 [cited by examiner]
US 20210385826A1 · Moon · 2021 [cited by examiner]
US 20220158788A1 · Horiuchi · 2022 [cited by examiner]
US 20220216972A1 · Takeda · 2022 [cited by examiner]
US 20220321278A1 · Yoshioka · 2022 [cited by examiner]
CN 109475000A · 2019 [cited by applicant]
CN 110138525A · 2019 [cited by applicant]
CN 110536448A · 2019 [cited by applicant]
EP 2317681B1 · 2011 [cited by applicant]
EP 3811699B1 · 2023 [cited by examiner]
KR 1020190027705A · 2019 [cited by applicant]
WO WO2019093865A1 · 2019 [cited by applicant]
WO WO2019137274A1 · 2019 [cited by applicant]
WO WO2019144932A1 · 2019 [cited by applicant]
First EP Office Action on EP AppIn No. 20852512.1, dated Dec. 21, 2023 (8 pages). [cited by applicant]
OPPO, “PDCCH enhancement for URLLC,” 3GPP TSG RAN WG1 #96bis, R1-1904042, Xi'an, China, Apr. 2, 2019 (6 pages). [cited by applicant]
CATT, “On PDSCH and PUSCH resource allocation” 3GPP TSG RAN WG1 Meeting AH 1801, R1-1800257, Jan. 26, 2018, Vancouver, Canada (23 pages). [cited by applicant]
CATT: “On PDSCH and PUSCH resource allocation” 3GPP TSG RAN WG1 Meeting AH 1801; R1-1800257; Jan. 26, 2018; Vancouver, Canada (22 pages). [cited by applicant]
Ericsson: “Benefits of Enhanced PDCCH Monitoring Capability for URLLC” 3GPP TSG-RAN WG1 Meeting #97; R1-1906109; May 17, 2019; Reno, Nevada (9 pages). [cited by applicant]
Ericsson: “Summary of 7.3.3.1 (resource allocation)” TSG-RAN WG1 AdHoc 1801; R1-1801011; Jan. 26, 2018; Vancouver, Canada (14 pages). [cited by applicant]
Extended European Search Report for EP Appl. No. 20852512.1, dated Nov. 11, 2021 (11 pages). [cited by applicant]
First Office Action for CN Appl. No. 2021102370249, dated Jul. 29, 2022 (with English translation, 14 pages). [cited by applicant]
First Office Action for JP Appl. No. 2021-510309, dated Mar. 24, 2022 (with English translation, 8 pages). [cited by applicant]
Huawei “Feature lead summary of HARW enhancements for NR-U” 3GPP TSG RAN WG1 Meeting #97, R1-1907652, May 17, 2019, Reno, USA (24 pages). [cited by applicant]
Huawei et al.: “Remaining issues on DCI contents and formats” R1-1803707; 3GPP TSG RAN WG1 Meeting #92bis; Apr. 20, 2018; Sanya, China (9 pages). [cited by applicant]
International Search Report and Written Opinion for PCT Appl. No. PCT/CN2020/108091 mailed Oct. 29, 2020 (with English translation, 12 pages). [cited by applicant]
Nokia et al.: “Summary of contributions on PUSCH enhancements for NR eURLLC (AI 7.2.6.3)” R1-1907695; 3GPP TSG-RAN WG1 Meeting #97; May 17, 2019; Reno, Nevada (27 pages). [cited by applicant]
Notice of Allowance on U.S. Appl. No. 17/158,861 Dtd Aug. 23, 2023. [cited by applicant]
Wilus Inc.: “On DCI enhancement for NR URLLC” 3GPP TSG RAN WG1 #97; R1-1907384; May 17, 2019; Reno, USA (3 pages). [cited by applicant]
ZTE: “On PDCCH enhancements for NR URLLC” 3GPP TSG RAN WG1 #98bis; R1-1910100; Oct. 20, 2019; Chongqing, China (15 pages). [cited by applicant]
Ericsson, “PDCCH Enhancements for NR URLLC”, 3GPP TSG-RAN WG1 Meeting #97, Tdoc R1-1906091, May 17, 2019, Reno, Nevada, US (13 pages). [cited by applicant]
ETSI TS 138 213 V15.6.0 (Jul. 2019), Technical Specification, “5G; NR; Physical layer procedures for control (3GPP TS 38.213 version 15.6.0 Release 15)” (110 pages). [cited by applicant]
Huawei, “CR to 38.212 capturing the Jan. 18 ad-hoc and RAN1#92 meeting agreements”, 3GPP TSG RAN WG1 Meeting #92, R1-1803553, Mar. 1, 2018, Athens (100 pages). [cited by applicant]
Nokia et al., “Summary of Tuesday offline discussion on PUSCH enhancements for NR eURLLC (AI 7.2.6.3)”, 3GPP TSG-RAN WG1 Meeting #97, R1-1907766, May 17, 2019, Reno, Nevada (27 pages). [cited by applicant]
Nokia, “Corrections to 38.214 including alignment of terminology across specifications”, 3GPP TSG RAN WG1 #97, R1-1907867, May 17, 2019, Reno, Nevada, U.S.A. (39 pages). [cited by applicant]
Office Action for KR Appl. No. 10-2021-7005438, dated Apr. 22, 2024 (with English translation, 8 pages). [cited by applicant]