IP Library Granted Patent US 12,262,380
Granted Patent B2
US 12,262,380 · App. 17/605,894 · Granted Mar 25, 2025

Communications method and device

Inventors: Chuting Yao (Beijing, CN); Yanzhao He (Shenzhen, CN); Yiru Kuang (Beijing, CN); Haibo Xu (Beijing, CN); Jian Wang (Beijing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04W72/20
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,262,380
App. No.
17/605,894
Granted
Mar 25, 2025
Kind
B2
Abstract

A method includes: determining, by a terminal device, that assistance information of the terminal device can be sent to a first network device through a signaling radio bearer (SRB) 3, wherein the terminal device is connected to at least two network devices, and the first network device is a secondary network device in the at least two network devices; and sending, by the terminal device, the assistance information to the first network device through the SRB3, wherein the assistance information is used to indicate a configuration expected by the terminal device or service information of the terminal device.

Claims (76)

1. A method, applied for a terminal device, comprising:

receiving first configuration information from a first network device or a second network device, wherein the first configuration information comprises first time information;

determining based on the first configuration information that the terminal device is allowed to send assistance information of the terminal device to the first network device through a signaling radio bearer 3 (SRB3) within a time range corresponding to the first time information, wherein the terminal device is connected to at least two network devices, and the first network device is a secondary network device in the at least two network devices, the second network device is a master network device in the at least two network devices; and

sending the assistance information to the first network device through the SRB3, wherein the assistance information indicates a configuration expected by the terminal device or service information of the terminal device, wherein the assistance information comprises one or any combination of the following:

a quantity of secondary cells corresponding to the terminal device;

a quantity of antenna ports of the terminal device;

a bandwidth of each secondary cell corresponding to the terminal device;

a connected-discontinuous reception (C-DRX) configuration or parameter expected by the terminal device;

an application type of the terminal device;

a size of a data packet transmitted by the terminal device;

a scheduling mode expected by the terminal device;

a search space expected by the terminal device;

a scheduling format expected by the terminal device; or

a slot format expected by the terminal device.

2. The method according to claim 1 , wherein the method further comprises:

determining, by the terminal device based on the first time information, that the terminal device is not allowed to send any further assistance information to the first network device within a time range corresponding to the first time information after sending the assistance information to the first network device.

3. The method according to claim 2 , wherein the first configuration information further comprises information about at least one parameter corresponding to the assistance information, and the method further comprises:

determining that a value of the at least one parameter is allowed to be sent to the first network device through the SRB3.

4. The method according to claim 2 , wherein the assistance information is information related to the first network device.

5. The method according to claim 4 , further comprising:

sending capability information of the terminal device to the second network device, wherein the capability information comprises:

first sub-capability information corresponding to the first network device, wherein the first sub-capability information is transparently transmitted to the first network device using the second network device;

second sub-capability information corresponding to the second network device; and

third sub-capability information corresponding to the first network device and the second network device.

6. A method applied for a first network device, comprising:

sending first configuration information to a terminal device, wherein the first configuration information comprises first time information, the first configuration information indicates that the terminal device is allowed to send assistance information of the terminal device to the first network device through a signaling radio bearer 3 (SRB3) within a time range corresponding to the first time information; and

receiving the assistance information of the terminal device, wherein the assistance information indicates a configuration expected by the terminal device or service information of the terminal device, the terminal device is connected to at least two network devices, and the first network device is a secondary network device in the at least two network devices, wherein the assistance information comprises one or any combination of the following:

a quantity of secondary cells corresponding to the terminal device;

a quantity of antenna ports of the terminal device;

a bandwidth of each secondary cell corresponding to the terminal device;

a connected-discontinuous reception (C-DRX) configuration or parameter expected by the terminal device;

an application type of the terminal device;

a size of a data packet transmitted by the terminal device;

a scheduling mode expected by the terminal device;

a search space expected by the terminal device;

a scheduling format expected by the terminal device; or

a slot format expected by the terminal device.

7. The method according to claim 6 , wherein receiving the assistance information of the terminal device comprises:

receiving the assistance information from the terminal device through the SRB3; or

receiving the assistance information from a second network device, wherein the second network device is a master network device in the at least two network devices.

8. The method according to claim 7 , wherein the assistance information is information related to the first network device.

9. The method according to claim 8 , wherein the first configuration information further indicates that:

the terminal device is not allowed to send any further assistance information to the first network device within the first time after sending the assistance information to the first network device.

10. The method according to claim 9 , wherein the first configuration information further comprises information about at least one parameter corresponding to the assistance information, and the information about the at least one parameter indicates to the terminal device to send a value of the at least one parameter when sending the assistance information of the terminal device to the first network device.

11. The method according to claim 10 , further comprising:

receiving capability information of the terminal device from the second network device, wherein the second network device is the master network device in the at least two network devices, and the capability information of the terminal device comprises:

first sub-capability information corresponding to the first network device; and

third sub-capability information corresponding to the first network device and the second network device.

12. The method according to claim 10 , further comprising:

receiving a request message from the second network device, wherein the request message requests the first network device to serve as a secondary network device of the second network device, and the second network device is the master network device in the at least two network devices;

sending a response message to the second network device, wherein the response message indicates that the first network device agrees that the first network device will serve as the secondary network device of the second network device; and

receiving second configuration information from the second network device, wherein the second configuration information configures the first network device as the secondary network device of the second network device.

13. The method according to claim 6 , wherein the assistance information is power saving assistance information, and the power saving assistance information indicates terminal device power saving.

14. A terminal device, comprising:

at least one processor; and

a memory coupled to the at least one processor and configured to store programming instructions that, when executed by the at least one processor, cause the terminal device to:

receiving first configuration information from a first network device or a second network device, wherein the first configuration information comprises first time information;

determine that assistance information of the terminal device is allowed to be sent to the first network device through a signaling radio bearer 3 (SRB3) within a time range corresponding to the first time information, wherein the terminal device is connected to at least two network devices, and the first network device is a secondary network device in the at least two network devices, the second network device is a master network device in the at least two network devices; and

send the assistance information to the first network device through the SRB3, wherein the assistance information indicates a configuration expected by the terminal device or service information of the terminal device, wherein the assistance information comprises one or any combination of the following:

a quantity of secondary cells corresponding to the terminal device;

a quantity of antenna ports of the terminal device;

a bandwidth of each secondary cell corresponding to the terminal device;

a connected-discontinuous reception (C-DRX) configuration or parameter expected by the terminal device;

an application type of the terminal device;

a size of a data packet transmitted by the terminal device;

a scheduling mode expected by the terminal device;

a search space expected by the terminal device;

a scheduling format expected by the terminal device; or

a slot format expected by the terminal device.

15. The terminal device according to claim 14 , wherein determining that assistance information of the terminal device is allowed to be sent to the first network device through the SRB3 comprises:

receiving the first configuration information from the first network device or a second network device; and

determining that the terminal device is allowed to send the assistance information to the first network device through the SRB3 based on the first configuration information, wherein the second network device is the master network device in the at least two network devices.

16. The terminal device according to claim 15 , wherein the first configuration information further comprises first time information, and the programming instructions, when executed by the at least one processor, further cause the terminal device to:

determine that the terminal device is not allowed to send any further assistance information to the first network device within a time range corresponding to the first time information after sending the assistance information to the first network device based on the first time information.

17. The terminal device according to claim 16 , wherein the first configuration information further comprises information about at least one parameter corresponding to the assistance information, and the programming instructions, when executed by the at least one processor, further cause the terminal device to:

determine that a value of the at least one parameter is allowed to be sent to the first network device through the SRB3.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2022
From: YAO, CHUTING; HE, YANZHAO; KUANG, YIRU; XU, HAIBO; WANG, JIAN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 061255/0115 →
Priority Claims (1)
CN 201910327423.7 · Apr 23, 2019 · national
Continuity (1)
Related Publication 20220124697A1 · Apr 21, 2022
References Cited (36)
US 10785817B2 · Palat · 2020 [cited by examiner]
US 20150373523A1 · Jeong · 2015 [cited by examiner]
US 20170196008A1 · Wang · 2017 [cited by examiner]
US 20170230917A1 · Ouchi · 2017 [cited by examiner]
US 20190053292A1 · Ali · 2019 [cited by examiner]
US 20200008113A1 · Chen · 2020 [cited by examiner]
US 20210067299A1 · Wu · 2021 [cited by examiner]
US 20220014953A1 · Teyeb · 2022 [cited by examiner]
US 20220132615A1 · Sharma · 2022 [cited by examiner]
CN 105101472A · 2015 [cited by applicant]
CN 109246824A · 2019 [cited by applicant]
CN 109246833A · 2019 [cited by applicant]
CN 113826431A · 2021 [cited by applicant]
EP 3897058A1 · 2021 [cited by applicant]
WO 2015199319A1 · 2015 [cited by applicant]
WO 2018056623A1 · 2018 [cited by applicant]
WO 2018130115A1 · 2018 [cited by applicant]
WO 2019059673A1 · 2019 [cited by applicant]
Apple, “Enhancement on SCell Activation and Deactivation”, 3GPP TSG-RAN WG2 Meeting #105bis, R2-1903609, Ki'an, China, Apr. 8-12, 2019, 4 pages. [cited by applicant]
Huawei et al., “37.340 Draft CR for addressing overheating issue in EN-DC scenario-Option 2”, 3GPP TSG-RAN2 Meeting #107bis, R2-1913693, Chongqing, China, Oct. 14-18, 2019, 7 pages. [cited by applicant]
Vivo, “Discussion on the IDC report of NR frequency in EN-DC”, 3GPP TSG-RAN WG2 Meeting #102, R2-1807634, revision of R2-1804601, Busan, Korea, May 21-25, 2018, 7 pages. [cited by applicant]
Huawei et al., “UE reporting assistance information to gNB”, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, R1-1901243, Taipei, Jan. 21-25, 2019, 5 pages. [cited by applicant]
3GPP TS 37.340 V15.5.0 (Mar. 2019), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Releas… [cited by applicant]
Vivo, “Consideration on RAN1 recommendation for power saving study”, 3GPP TSG RAN WG1 Meeting #96bis, R1-1904106, Xi'an, China, Apr. 8-12, 2019, 7 pages. [cited by applicant]
Qualcomm Inc., “UE Assistance Information for power saving”, 3GPP TSG-RAN WG2 Meeting #105bis, R2-1903053, Xi'an, China, Apr. 8-12, 2019, 3 pages. [cited by applicant]
Huawei et al., “Discussion on TA group management”, 3GPP TSG-RAN WG2 Meeting #74, R2-113285, Barcelona, Spain, May 9-13, 2011, 4 pages. [cited by applicant]
Nokia et al., “Assistance information for NR overheating”, 3GPP TSG-RAN WG2 Meeting #104, R2-1816537, Spokane, WA, US, Nov. 12-16, 2018, 3 pages. [cited by applicant]
Intel Corp., “Discussion on non-TM10 Homogenous Network CRS-IM RX”, 3GPP TSG RAN4 Meeting #76, R4-154142, Beijing, China, Aug. 24-28, 2015, 6 pages. [cited by applicant]
Nokia et al., “Assistance information for NR overheating”, 3GPP TSG-RAN WG2 Meeting #104, R2-1816537, Spokane, WA, USA, Nov. 12-16, 2018, 3 pages. [cited by applicant]
3GPP TS 38.331 V15.5.1 (Apr. 2019), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15), 491 pages. [cited by applicant]
Ericsson, “Extension of overheating indication parameters”, 3GPP TSG-RAN WG2 #104, R2-1817930, Spokane, WA, US, Nov. 12-16, 2018, 2 pages. [cited by applicant]
Huawei et al., “Coordination for overheating in MR-DC scenario”, 3GPP TSG-RAN2 Meeting#105bis, R2-1904936, (Revision of R2-1901681), Xi'an, China, Apr. 8-12, 2019, 3 pages. [cited by applicant]
Qualcomm Inc., “Extending LTE Overheating mechanism to NR”, 3GPP TSG-RAN WG2 #101, R2-1803617, Athens, Greece, Feb. 26-Mar. 2, 2018, 4 pages. [cited by applicant]
Huawei et al., “UE reporting assistance information to gNB”, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, R1-1901243, Jan. 21-25, 2019, 5 Pages, Taipei. [cited by applicant]
Vivo., “UE assistant information”, 3GPP TSG RAN WG1 #96bis, R1-1904120, Apr. 8-12, 2019, 3 Pages, Xi'an, China. [cited by applicant]
Huawei et al., “CR on UE overheating support for NGEN-DC”, 3GPP TSG-RAN2 Meeting#105, R2-1901680, Feb. 25-Mar. 1, 2019, 5 Pages, Athens, Greece. [cited by applicant]