IP Library › Granted Patent US 12,150,203
Granted Patent B2
US 12,150,203 · App. 18/359,439 · Granted Nov 19, 2024

Communication method and related product

Inventors: Yada Huang (Shanghai, CN); Yuanping Zhu (Shanghai, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W76/40H04W4/06
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,150,203
App. No.
18/359,439
Granted
Nov 19, 2024
Kind
B2
Abstract

Embodiments of the present invention disclose a communication method and a related product. A method implemented on an access network side includes: sending, by an access network device, indication information to user equipment, where the indication information is used to indicate a manner of receiving multicast service data, and the receiving manner includes a unicast manner and/or a multicast manner; and sending, by the access network device, the multicast service data in the unicast manner and/or the multicast manner indicated by the indication information.

Claims (59)

1. A communication method for access network device, comprising:

sending indication information to user equipment, wherein the indication information indicates a receiving manner of multicast service data, and the receiving manner comprises a unicast manner, a multicast manner or a hybrid manner, and the hybrid manner comprises the unicast manner and the multicast manner;

if the indication information indicates that the receiving manner of the multicast service data is the unicast manner, sending multicast service data to a unicast radio link control (RLC) entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the unicast manner;

if the indication information indicates that the receiving manner of the multicast service data is the multicast manner, sending multicast service data to a multicast radio link control (RLC) entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the multicast manner;

if the indication information indicates that the receiving manner of the multicast service data is the hybrid manner, sending multicast service data to a multicast radio link control (RLC) entity and a unicast RLC entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the unicast manner and the multicast manner, sending, in the unicast manner, multicast service data that has been sent in the multicast manner and needs to be retransmitted.

2. The method according to claim 1 , wherein the receiving manner is the hybrid manner, and the multicast service data is sent in the multicast manner and the unicast manner, the method further comprises:

determining the multicast service data that needs to be retransmitted in one of the following ways:

a way of transmitting negative acknowledgement (NACK) through a physical layer feedback channel, an RLC status report, or a PDCP status report.

3. The method according to claim 2 , wherein the RLC status report indicates a sequence number (SN) of the multicast service data that needs to be retransmitted; or the PDCP status report indicates a SN of the multicast service data that needs to be retransmitted.

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

sending configuration information to the user equipment, wherein the configuration information is used to receive the multicast service data,

wherein the configuration information comprises:

at least one of configuration information of a multicast bearer, multicast session information corresponding to the multicast bearer, logical channel information of the multicast bearer, or multicast scheduling identifier information.

5. The method according to claim 4 , wherein the configuration information of the multicast bearer comprises a mapping relationship between a PDCP layer and a RLC layer of the multicast bearer, and the mapping relationship is one of the following: the PDCP layer of the multicast bearer is mapped to an RLC layer in the unicast manner, or the PDCP layer of the multicast bearer is mapped to an RLC layer in the multicast manner, and the PDCP layer of the multicast bearer is mapped to the RLC layer in the unicast manner and the RLC layer in the multicast manner.

6. The method according to claim 1 , receiving multicast service information from a core network device, wherein the multicast service information comprises identifier information of the user equipment and identifier information of a multicast service.

7. The method according to claim 1 , wherein

the sending multicast service data to a unicast radio link control (RLC) entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the unicast manner comprises:

sending the multicast service data to the unicast RLC entity through the multicast PDCP layer, and sending, by the unicast RLC entity, the multicast service data to a unicast media access control (MAC) entity, and sending, by the unicast MAC entity, the multicast service data in the unicast manner;

the sending multicast service data to a multicast radio link control (RLC) entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the multicast manner comprises:

sending the multicast service data to the multicast RLC entity in the access network device through the multicast PDCP layer, sending, by the multicast RLC entity, the multicast service data to a multicast media access control (MAC) entity, and sending, by the multicast MAC entity, the multicast service data in the multicast manner; and

the sending multicast service data to a multicast radio link control (RLC) entity and a unicast RLC entity in the access network device through a multicast data convergence protocol (PDCP) layer, and sending the multicast service data in the unicast manner and the multicast manner comprises:

sending the multicast service data to the multicast RLC entity and the unicast RLC entity in the access network device through the multicast PDCP layer, sending, by the unicast RLC entity, the multicast service data to a unicast media access control (MAC) entity, and sending, by the unicast MAC entity, the multicast service data in the unicast manner, sending, by the multicast RLC entity, the multicast service data to the multicast MAC entity, and sending, by the multicast MAC entity, the multicast service data in the multicast manner.

8. The method according to claim 7 , wherein the multicast RLC entity corresponds to a non-acknowledgement (UM) manner, and the unicast RLC entity corresponds to an acknowledgement (AM) manner or the non-acknowledgement (UM) manner.

9. The method according to claim 1 , further comprising copying the multicast service data at the PDCP layer, and storing the multicast service data.

10. The method according to claim 1 , wherein

the sending the multicast service data in the unicast manner comprises: sending a unicast scheduling signaling by using a user equipment identifier (C-RNTI), wherein the unicast scheduling signaling indicates time-frequency resources of the multicast service data; and

the sending the multicast service data in the multicast manner comprises: sending a multicast scheduling signaling by using a group wireless network temporary identifier (G-RNTI), wherein the multicast scheduling signaling indicates time-frequency resources of the multicast service data.

11. A communication apparatus, comprising:

at least one processor; and

a non-transitory computer-readable medium including computer-executable instructions that, when executed by the at least one processor, cause the apparatus to carry out operations including:

receiving indication information sent by an access network device, wherein the indication information indicates a receiving manner of multicast service data, and the receiving manner comprises a unicast manner, a multicast manner or a hybrid manner, and the hybrid manner comprises the unicast manner and the multicast manner; and

if the indication information indicates that the receiving manner of the multicast service data is the unicast manner, receiving multicast service data in the unicast manner;

if the indication information indicates that the receiving manner of the multicast service data is the multicast manner, receiving the multicast service data in the multicast manner;

if the indication information indicates that the receiving manner of the multicast service data is the hybrid manner, receiving the multicast service data in the unicast manner and the multicast manner, and receiving in the unicast manner, multicast service data that has been sent in the multicast manner and needs to be retransmitted.

12. The apparatus according to claim 11 , wherein the multicast service data that needs to be retransmitted is determined in one of the following ways:

a way of transmitting negative acknowledgement (NACK) through a physical layer feedback channel, an RLC status report, or a PDCP status report.

13. The apparatus according to claim 12 , wherein the RLC status report indicates a sequence number (SN) of the multicast service data that needs to be retransmitted; or the PDCP status report indicates a SN of the multicast service data that needs to be retransmitted.

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

receiving configuration information from the access network device, wherein the configuration information is used to receive the multicast service data,

wherein the configuration information comprises:

at least one of configuration information of a multicast bearer, multicast session information corresponding to the multicast bearer, logical channel information of the multicast bearer, or multicast scheduling identifier information.

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

wherein the configuration information of the multicast bearer comprises a mapping relationship between a PDCP layer and a RLC layer of the multicast bearer, and the mapping relationship is one of the following: the PDCP layer of the multicast bearer is mapped to an RLC layer in the unicast manner, or the PDCP layer of the multicast bearer is mapped to an RLC layer in the multicast manner, or the PDCP layer of the multicast bearer is mapped to the RLC layer in the unicast manner and the RLC layer in the multicast manner.

16. The apparatus according to claim 11 , wherein

the receiving multicast service data in the unicast manner comprises:

receiving, from a unicast MAC entity, the multicast service data in the unicast manner;

the receiving the multicast service data in the multicast manner comprises:

receiving, from a multicast MAC entity, the multicast service data in the multicast manner; and

the receiving the multicast service data in the unicast manner and the multicast manner, and receiving in the unicast manner, multicast service data that has been sent in the multicast manner and needs to be retransmitted comprises:

receiving, from the unicast MAC entity, the multicast service data in the unicast manner, and receiving, from the multicast MAC entity, the multicast service data in the multicast manner.

17. The apparatus according to claim 15 , wherein the RLC layer in the multicast manner corresponds to a non-acknowledgement (UM) manner, and the RLC layer in the unicast manner corresponds to an acknowledgement (AM) manner or the non-acknowledgement (UM) manner.

18. The apparatus according to claim 11 , wherein

the receiving the multicast service data in the unicast manner comprises: receiving a unicast scheduling signaling by using a user equipment identifier (C-RNTI), wherein the unicast scheduling signaling indicates time-frequency resources of the multicast service data; and

the receiving the multicast service data in the multicast manner comprises: receiving a multicast scheduling signaling by using a group wireless network temporary identifier (G-RNTI), wherein the multicast scheduling signaling indicates time-frequency resources of the multicast service data.

19. The apparatus according to claim 11 , wherein the operations further comprise:

performing packet loss detection at a PDCP layer, to obtain receiving status information.

20. The apparatus according to claim 11 , wherein the operations further comprise at least one of the following:

transmitting at least one of the following: negative acknowledgement (NACK) through a physical layer feedback channel, an RLC status report, or a PDCP status report; or

sending the received multicast service data to a PDCP layer.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2024
From: HUANG, YADA; ZHU, YUANPING
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 067562/0054 →
Priority Claims (1)
CN 201711453932.1 · Dec 28, 2017 · national
Continuity (4)
Continuation 17569120 · Jan 5, 2022
Continuation 16909891 · Jun 23, 2020
Continuation PCTCN2018124928 · Dec 28, 2018
Related Publication 20240098844A1 · Mar 21, 2024