IP Library Granted Patent US 12,363,601
Granted Patent B2
US 12,363,601 · App. 17/704,362 · Granted Jul 15, 2025

Communication method and apparatus

Inventors: Shuigen Yang (Shanghai, CN); Feng Han (Shanghai, CN); Yinghao Jin (Boulogne Billancourt, FR); Wei Tan (Shanghai, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W36/06H04W36/0064H04W36/13
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,363,601
App. No.
17/704,362
Granted
Jul 15, 2025
Kind
B2
Abstract

The disclosure provides communication methods and apparatuses. One example method includes receiving, by a first network device, a first message from a second network device, where the first message includes network slice configuration information. The network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1. In response to the received first message, the first network device sends a second message to the second network device.

Claims (81)

1. A communication method comprises:

receiving, by a first network device, a first message from a second network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises:

first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and

second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and

sending, by the first network device, a second message to the second network device, wherein the second message is in response to the first message.

2. The method according to claim 1 , wherein:

the first message is a handover request message;

the first message is a UE context setup request message or a UE context modification request message;

the first message is a bearer context setup request message or a bearer context modification request message;

the first message is a secondary node addition request message or a secondary node modification request message; or

the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message.

3. The method according to claim 1 , wherein:

the second message is a handover request acknowledge message;

the second message is a UE context setup response message or a UE context modification response message;

the second message is a bearer context setup response message or a bearer context modification response message;

the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or

the second message is a PDU session resource setup response message or an initial context setup response message.

4. The method according to claim 1 , wherein the second message indicates that the first network device rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n.

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

sending, by the first network device, rejection information to the second network device, wherein the rejection information indicates that a reason why the first network device rejects the configuration requirements of maximum data rates provided by m network slices is that the first network device does not support the maximum data rates provided by the m network slices for the terminal device.

6. A communication method comprises:

sending, by a second network device, a first message to a first network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises:

first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and

second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and

receiving a second message from the first network device, wherein the second message is in response to the first message.

7. The method according to claim 6 , wherein:

the first message is a handover request message;

the first message is a UE context setup request message or a UE context modification request message;

the first message is a bearer context setup request message or a bearer context modification request message;

the first message is a secondary node addition request message or a secondary node modification request message; or

the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message.

8. The method according to claim 6 , wherein:

the second message is a handover request acknowledge message;

the second message is a UE context setup response message or a UE context modification response message;

the second message is a bearer context setup response message or a bearer context modification response message;

the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or

the second message is a PDU session resource setup response message or an initial context setup response message.

9. The method according to claim 6 , wherein the second message indicates that the first network device rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n.

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

receiving, by the second network device, rejection information from the first network device, wherein the rejection information indicates that a reason why the first network device rejects the configuration requirements of maximum data rates provided by m network slices is that the first network device does not support the maximum data rates provided by m network slices for the terminal device.

11. A communication apparatus, comprising at least one processor; and

one or more memories are coupled to the at least one processor and storing programming instructions for execution by the at least one processor to perform operations comprising:

receiving a first message from a network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises:

first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and

second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and

sending a second message to the network device, wherein the second message is in response to the first message.

12. The communication apparatus according to claim 11 , wherein:

the first message is a handover request message;

the first message is a UE context setup request message or a UE context modification request message;

the first message is a bearer context setup request message or a bearer context modification request message;

the first message is a secondary node addition request message or a secondary node modification request message; or

the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message.

13. The communication apparatus according to claim 11 , wherein:

the second message is a handover request acknowledge message;

the second message is a UE context setup response message or a UE context modification response message;

the second message is a bearer context setup response message or a bearer context modification response message;

the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or

the second message is a PDU session resource setup response message or an initial context setup response message.

14. The communication apparatus according to claim 11 , wherein the second message indicates that the communication apparatus rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n.

15. The communication apparatus according to claim 14 , wherein the operations further comprise:

sending rejection information to the network device, wherein the rejection information indicates that a reason why the communication apparatus rejects the configuration requirements of maximum data rates provided by m network slices is that the communication apparatus does not support the maximum data rates provided by m network slices for the terminal device.

16. A non-transitory computer-readable storage medium storing one or more programming instructions executable by at least one processor to cause a first network device to perform operations comprising:

receiving a first message from a second network device, wherein the first message comprises network slice configuration information, the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for a terminal device, and n is an integer greater than or equal to 1, wherein the network slice configuration information comprises:

first indication information that indicates an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, wherein the uplink data flow comprises at least one of an uplink non-guaranteed bit rate quality of service (non-GBR QoS) flow or an uplink guaranteed bit rate quality of service (GBR QoS) flow of the terminal device; and

second indication information that indicates an aggregate bit rate provided by each of the n network slices for a downlink data flow of the terminal device, wherein the downlink data flow comprises at least one of a downlink non-GBR QoS flow or a downlink GBR QoS flow; and

sending a second message to the second network device, wherein the second message is in response to the first message.

17. The non-transitory computer-readable storage medium according to claim 16 , wherein:

the first message is a handover request message;

the first message is a UE context setup request message or a UE context modification request message;

the first message is a bearer context setup request message or a bearer context modification request message;

the first message is a secondary node addition request message or a secondary node modification request message; or

the first message is a protocol data unit (PDU) session resource setup request message or an initial context setup request message.

18. The non-transitory computer-readable storage medium according to claim 16 , wherein:

the second message is a handover request acknowledge message;

the second message is a UE context setup response message or a UE context modification response message;

the second message is a bearer context setup response message or a bearer context modification response message;

the second message is a secondary node addition request acknowledge message or a secondary node modification request acknowledge message; or

the second message is a PDU session resource setup response message or an initial context setup response message.

19. The non-transitory computer-readable storage medium according to claim 16 , wherein the second message indicates that the first network device rejects configuration requirements of maximum data rates provided by m network slices for the terminal device, and m is an integer greater than or equal to 0 and less than or equal to n.

20. The non-transitory computer-readable storage medium according to claim 19 , wherein the operations further comprise:

sending, by the first network device, rejection information to the second network device, wherein the rejection information indicates that a reason why the first network device rejects the configuration requirements of maximum data rates provided by m network slices is that the first network device does not support the maximum data rates provided by m network slices for the terminal device.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2025
From: YANG, SHUIGEN; HAN, FENG; JIN, YINGHAO
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071159/0761 →
EMPLOYMENT AGREEMENT Recorded May 19, 2025
From: TAN, WEI
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071297/0277 →
Priority Claims (1)
CN 201910919493.1 · Sep 26, 2019 · national
Continuity (2)
Continuation PCTCN2020115328 · Sep 15, 2020
Related Publication 20220217593A1 · Jul 7, 2022
References Cited (30)
US 20180324645A1 · Park et al. · 2018 [cited by applicant]
US 20180352483A1 · Youn · 2018 [cited by examiner]
US 20190159027A1 · Kuge et al. · 2019 [cited by applicant]
US 20220116816A1 · Liang · 2022 [cited by examiner]
CN 107770794A · 2018 [cited by applicant]
CN 108366365A · 2018 [cited by applicant]
CN 108668381A · 2018 [cited by applicant]
CN 109151924A · 2019 [cited by applicant]
CN 109257827A · 2019 [cited by applicant]
CN 109392038A · 2019 [cited by applicant]
CN 109792657A · 2019 [cited by applicant]
CN 110226337A · 2019 [cited by applicant]
EP 3634036A1 · 2020 [cited by applicant]
WO 2018228126A1 · 2018 [cited by applicant]
WO 2019007486A1 · 2019 [cited by applicant]
Huawei, Intra-system, “Intra-RAT mobility in RRC_Connected,” 3GPP TSG-RAN WG3 Meeting #95bis R3-171253, Spokane, USA, Apr. 3-7, 2017, 4 pages. [cited by applicant]
Extended European Search Report in European AppIn No. 20869389.5, dated Oct. 12, 2022, 13 pages. [cited by applicant]
3GPP TS 23.501 V16.2.0 (Sep. 2019), “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16),” Sep. 2019, 389 page… [cited by applicant]
3GPP TS 38.413 V15.4.0 (Jul. 2019), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 15),” Jul. 2019, 328 pages. [cited by applicant]
Ericsson, “Core Network type restriction on “EPC” in 5GS subscription data,” 3GPP TSG-SA WG2 Meeting #128bis, S2-187799, Sophia Antipolis, France, Aug. 20-24, 2018, 4 pages. [cited by applicant]
Huawei, HiSilicon, “Procedures for Small Data Rate Control,” 3GPP TSG-SA WG2 Meeting #133, S2-1905610, Reno, USA, May 13-17, 2019, 33 pages. [cited by applicant]
Huawei, HiSilicon, “Procedures for Small Data Rate Control,” 3GPP TSG-SA WG2 Meeting #133, S2-1906050, Reno, USA, May 13-17, 2019, 33 pages. [cited by applicant]
Nokia et al., “New WID Study on Enhancement of Network Slicing Phase 2,” 3GPP TSG|WG-SA WG2 Meeting #134, S2-1908583, Sapporo, Japan, Jun. 24-28, 2019, 3 pages. [cited by applicant]
Nokia et al., “RDI handling for data forwarding at handover,” 3GPP TSG-RAN WG2 Meeting #104, R2-1816412, Spokane, USA, Nov. 12-16, 2018, 4 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201910919493.1 on Aug. 3, 2021, 26 pages (with English translation). [cited by applicant]
PCT International Search Report and Written Opinion issued in International Application No. PCT/CN2020/115328 on Aug. 27, 2020, 17 pages (with English translation). [cited by applicant]
Qualcomm Incorporated et al., “Handling of S-NSSAI and PDU session ID during mobility between EPS and 5GS,” 3GPP TSG-CT WG1 Meeting #108, C1-180696, Gothenburg, Sweden, Jan. 22-26, 2018, 12 pages. [cited by applicant]
Huawei et al., “Proposed corrections to 38.300 mainly on RRC_Inactive state,” 3GPP TSG-RAN WG2#99, R2-1709833, Berlin, Germany, Aug. 21-25, 2017, 12 pages. [cited by applicant]
Huawei et al., “QoS Parameters,” 3GPP TSG-RAN WG2 Meeting #98, R2-1704976, Hangzhou, China, May 15-19, 2017, 3 pages. [cited by applicant]
Office Action in Korean Appin. No. 10-2022-7013975, mailed on Sep. 23, 2024, 13 pages (with English translation). [cited by applicant]