CN116114195A

CN116114195A - Retransmission method and device for multicast service, terminal equipment and network equipment

Info

Publication number: CN116114195A
Application number: CN202080105070.7A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-10-29
Filing date: 2020-10-29
Publication date: 2023-05-12
Also published as: WO2022087990A1

Abstract

The embodiment of the application provides a retransmission method and device of multicast service, terminal equipment and network equipment, wherein the method comprises the following steps: the method comprises the steps that a terminal device generates an RLC status report aiming at multicast service data reception, and sends the RLC status report to a network device, wherein the RLC status report is used for the network device to determine RLC PDU needing retransmission; and the terminal equipment receives the RLC PDU retransmitted by the network equipment in a unicast mode.

Description

Retransmission method and device for multicast service, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a retransmission method and device of multicast service, terminal equipment and network equipment.

Background

In a New Radio (NR) system, a higher demand is put forward for reliability of a multicast service, and a terminal device is required to feed back reception of the multicast service. However, the current feedback mechanism has the following problems: if there are multiple users receiving a piece of multicast service data, only one user receives errors, and multicast retransmission of the multicast service data is redundant and electricity-consuming for other users. How to perform efficient retransmission is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a retransmission method and device of multicast service, terminal equipment and network equipment.

The retransmission method of the multicast service provided by the embodiment of the application comprises the following steps:

the terminal equipment generates a radio link control (Radio Link Control, RLC) status report for multicast service data reception, and sends the RLC status report to the network equipment, wherein the RLC status report is used for determining a radio link control packet data unit (Radio Link Control Packet Data Unit, RLC PDU) which needs to be retransmitted by the network equipment;

and the terminal equipment receives the RLC PDU retransmitted by the network equipment in a unicast mode.

the network equipment receives an RLC status report sent by the terminal equipment, wherein the RLC status report is generated by the terminal equipment and used for receiving multicast service data, and the RLC status report is used for determining RLC PDU (protocol data unit) needing to be retransmitted by the network equipment;

and the network equipment retransmits the RLC PDU to the terminal equipment in a unicast mode.

The retransmission apparatus for multicast service provided in the embodiment of the present application is applied to a terminal device, and the apparatus includes:

A generating unit, configured to generate an RLC status report for multicast service data reception;

a sending unit, configured to send the RLC status report to a network device, where the RLC status report is used for determining, by the network device, an RLC PDU that needs to be retransmitted;

and the receiving unit is used for receiving the RLC PDU retransmitted by the network equipment in a unicast mode.

The retransmission apparatus for multicast service provided in the embodiment of the present application is applied to a network device, and the apparatus includes:

a receiving unit, configured to receive an RLC status report sent by a terminal device, where the RLC status report is an RLC status report generated by the terminal device and used for determining, by the network device, an RLC PDU that needs to be retransmitted;

and the sending unit is used for retransmitting the RLC PDU to the terminal equipment in a unicast mode.

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the retransmission method of the multicast service.

The network device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the retransmission method of the multicast service.

The chip provided by the embodiment of the application is used for realizing the retransmission method of the multicast service.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory, so that the device provided with the chip executes the retransmission method of the multicast service.

The computer readable storage medium provided in the embodiments of the present application is configured to store a computer program, where the computer program causes a computer to execute the above-mentioned method for retransmitting a multicast service.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the method for retransmitting the multicast service.

The computer program provided in the embodiments of the present application, when running on a computer, causes the computer to execute the above-mentioned retransmission method of the multicast service.

According to the technical scheme, the terminal equipment feeds back the RLC status report to the network equipment, so that the network equipment can determine the RLC PDU needing to be retransmitted according to the RLC status report and retransmit the RLC PDU to the terminal equipment in a unicast mode, redundant receiving of other terminal equipment on the RLC PDU is avoided, the purposes of energy saving and efficient feedback are achieved, and the reliability of multicast service receiving is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application;

fig. 2 is a flow chart of a retransmission method of a multicast service according to an embodiment of the present application;

fig. 3 is a schematic diagram of a protocol stack of a terminal device and a network device provided in an embodiment of the present application;

fig. 4 is a second protocol stack schematic diagram of a terminal device and a network device provided in an embodiment of the present application;

fig. 5 is a schematic structural diagram of a retransmission apparatus for multicast service according to an embodiment of the present application;

fig. 6 is a schematic diagram ii of a structural composition of a retransmission apparatus for multicast service according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG. 8 is a schematic block diagram of a chip of an embodiment of the present application;

fig. 9 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), systems, 5G communication systems, future communication systems, or the like.

Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in the LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system, etc.

The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. "terminal" as used herein includes, but is not limited to, connection via wireline, such as via public-switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminals arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.

Alternatively, direct to Device (D2D) communication may be performed between the terminals 120.

Alternatively, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within a coverage area, which is not limited in this embodiment.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, where the network device 110 and the terminal 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of tight coupling (tight interworking) between LTE and NR is proposed.

MBMS

MBMS is a technology for transmitting data from one data source to a plurality of terminal equipments through a shared network resource, which can effectively utilize the network resource while providing a multimedia service, and realize broadcasting and multicasting of a multimedia service of a higher rate (e.g., 256 kbps).

Due to the low MBMS spectrum efficiency, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In LTE, 3GPP has therefore explicitly proposed to enhance the support capability for the downlink high speed MBMS service and to determine the design requirements for the physical layer and the air interface.

The 3gpp R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. a multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MBSFN), wherein the MBSFN uses a unified frequency to simultaneously transmit traffic data in all cells, but synchronization between the cells is guaranteed. The method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocols.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to terminal devices in an idle state or a connected state.

A single cell point-to-multipoint (Single Cell Point To Multiploint, SC-PTM) concept is introduced in 3gpp r13, SC-PTM being based on the MBMS network architecture.

MBMS introduces new logical channels including Single Cell multicast control channel (SC-MCCH) and Single Cell multicast transport channel (SC-MTCH) and Single Cell-Multicast Transport Channel. The SC-MCCH and SC-MTCH are mapped onto a Downlink-Shared Channel (DL-SCH), and further, the DL-SCH is mapped onto a physical Downlink Shared Channel (Physical Downlink Shared Channel, PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a physical Channel. The SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operation.

MBMS introduces a new system information block (System Information Block, SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, the radio frame and subframe for scheduling the SC-MCCH and other information. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m=0, where SFN represents a system frame number of the boundary, and m is a modification period (i.e., SC-MCCH-modification period) of the SC-MCCH configured in SIB20. 2) The radio frame of the scheduling SC-MCCH meets the following conditions: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents the system frame number of the radio frame, MCCH-repetition period represents the repetition period of the SC-MCCH, and MCCH-Offset represents the Offset of the SC-MCCH. 3) The subframes of the scheduling SC-MCCH are indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a physical downlink control channel (Physical Downlink Control Channel, PDCCH). In one aspect, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), i.e., single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling the SC-MCCH, optionally with the SC-RNTI fixed value FFFC. On the other hand, a new RNTI, i.e., a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change notification of the SC-MCCH, optionally, the SC-N-RNTI is fixed to a value of FFFB; further, the change notification may be indicated with one bit of 8 bits (bits) of DCI 1C. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., scptm configuration) for configuring configuration information of the SC-PTM. The configuration information of the SC-PTM comprises: temporary mobile Group identity (Temporary Mobile Group Identity, TMGI), session identity (session id), group RNTI (G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information, SC-PTM service information of neighbor cells, and the like. Note that SC-PTM in R13 does not support the robust header compression (Robust Header Compression, ROHC) function.

The downlink discontinuous reception of the SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-scheduling cycle, and SC-MTCH-scheduling offset.

When [ (SFN 10) +subframe number ] module (SC-MTCH-scheduling cycle) =sc-MTCH-scheduling offset is satisfied, a timer ondurationtimerscpm is started;

when receiving downlink PDCCH scheduling, starting a timer drx-InactivityTimerSCPTM;

the downstream SC-PTM service is received only when the timer onduration timerscpm or drx-incaactyitimerscpm is running.

The SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely a mode of SIB15 and MBMSInterestindication. The traffic continuity of the terminal device in idle state is based on the concept of frequency priority.

It should be noted that, the MBMS service in the above scheme includes, but is not limited to, a multicast service and a multicast service. The embodiments of the present application are described by taking the multicast service as an example, and the description of the "multicast service" may be replaced by the "MBS service" or the "multicast service" or the "MBMS service".

In NR, RLC AM mode is with a feedback mechanism. The data receiving end feeds back whether the receiving state of the RLC PDU is correct or incorrect through the RLC status report, if the receiving state is correct, the RLC status report indicates that the feedback information of the SN corresponding to the RLC PDU is ACK information, and if the receiving state is incorrect, the RLC status report indicates that the feedback information of the SN corresponding to the RLC PDU is NACK information, and it should be noted that the RLC status report may indicate the feedback information of the SN corresponding to one or more RLC PDUs. The data transmitting end can repeatedly transmit the RLC PDU corresponding to the SN number with the feedback information being NACK information according to the RLC status report.

In the NR system, the multicast service needs to be received in the RRC connected state, and a higher demand is put forward for reliability of the multicast service, and a terminal device is required to feed back the reception of the multicast service. How to ensure the reliability of multicast service without redundant retransmission in multicast mode, and reducing the influence on the terminal equipment which has received correct data is a problem to be solved. For this reason, the following technical solutions of the embodiments of the present application are proposed.

Fig. 2 is a flow chart of a retransmission method of a multicast service according to an embodiment of the present application, as shown in fig. 2, where the retransmission method of the multicast service includes the following steps:

step 201: the terminal equipment generates an RLC status report aiming at multicast service data reception, the RLC status report is sent to the network equipment, the network equipment receives the RLC status report sent by the terminal equipment, and the RLC status report is used for the network equipment to determine the RLC PDU needing to be retransmitted.

In the embodiment of the present application, the terminal device has a first RLC entity and a fourth RLC entity, where the first RLC entity belongs to a PTM RLC entity, and the fourth RLC entity belongs to a PTP RLC entity.

In the embodiment of the application, the network device may be a base station, such as a gNB. The network device has a second RLC entity and a third RLC entity, wherein the second RLC entity belongs to a PTM RLC entity and the third RLC entity belongs to a PTP RLC entity.

The PTM RLC entity refers to an RLC entity that performs data reception and/or transmission by multicast. The PTP RLC entity refers to an RLC entity that performs data reception and/or transmission by unicast. For the case of data reception and/or transmission by multicast, the scheduling information of the data is scrambled by G-RNTI. For the case of data reception and/or transmission by unicast, the scheduling information of the data is scrambled by the C-RNTI.

In this embodiment of the present application, the RLC status report is an RLC status report generated by the terminal device and used for receiving multicast service data. Before the terminal device generates the RLC status report for multicast service data reception, the method further includes:

the second RLC entity of the network equipment sends multicast service data to the first RLC entity of the terminal equipment, and the first RLC entity of the terminal equipment receives the multicast service data sent by the second RLC entity of the network equipment, wherein the scheduling information of the multicast service data is scrambled through a G-RNTI.

Here, since the first RLC entity and the second RLC entity belong to a PTM RLC entity, the terminal device receives multicast service data sent by the network device in a multicast manner.

In the embodiment of the application, the terminal equipment generates the RLC status report for receiving the multicast service data based on the receiving condition of the multicast service data. Here, the receiving condition of the multicast service data may be that the multicast service data is received correctly or that the multicast service data is received incorrectly, if the multicast service data is received correctly, the feedback information of the SN corresponding to the multicast service data is indicated by the RLC status report as ACK information, and if the multicast service data is received incorrectly, the feedback information of the SN corresponding to the multicast service data is indicated by the RLC status report as NACK information. It should be noted that, feedback information of SN corresponding to one or more multicast service data may be indicated in the RLC status report.

In the embodiment of the present application, the terminal device sends the RLC status report to the network device, which may be implemented in the following manner.

Mode one: the RLC status report is sent to a second RLC entity of the network device.

The method comprises the steps that a first RLC entity of terminal equipment generates an RLC status report for multicast service data reception, the RLC status report is sent to a second RLC entity of network equipment, and the second RLC entity of the network equipment receives the RLC status report sent by the first RLC entity of the terminal equipment.

Here, the RLC status report is an RLC status report for multicast service data reception generated by the first RLC entity of the terminal apparatus.

Here, although the first RLC entity and the second RLC entity belong to a PTM RLC entity, the terminal device reports its RLC status report to the network device in a unicast manner. That is, the scheduling information corresponding to the RLC status report is scrambled by the C-RNTI.

In this embodiment of the present application, the RLC status report is used for sending, by the second RLC entity of the network device, an RLC PDU corresponding to at least one SN to a third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the RLC status report, and the third RLC entity belongs to a PTP RLC entity.

Specifically, the second RLC entity of the network device determines SN corresponding to NACK feedback information based on the RLC status report, obtains at least one SN, and sends RLC PDU corresponding to at least one SN to the third RLC entity of the network device. Then, the following step 202 is performed.

In this embodiment of the present application, the network device sends first configuration information to the terminal device, where the terminal device receives the first configuration information sent by the network device, where the first configuration information is used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception; the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode. Further optionally, the first configuration information includes second indication information, where the second indication information is used to indicate that the bearer corresponding to the first RLC entity is only used for downlink data reception.

Here, the AM mode represents an acknowledged mode, and for the AM mode, since it has ARQ capability, if a data receiving end (e.g., a terminal device) erroneously receives an RLC PDU, a data transmitting end (e.g., a network device) is informed to retransmit the RLC PDU, where SN is included in the RLC PDU.

Mode two: the RLC status report is sent to a third RLC entity of the network device.

The method comprises the steps that a first RLC entity of terminal equipment generates an RLC status report for multicast service data reception, and the RLC status report is sent to a fourth RLC entity of the terminal equipment; the fourth RLC entity of the terminal device sends the RLC status report to a third RLC entity of the network device. And the third RLC entity of the network equipment receives the RLC status report sent by the fourth RLC entity of the terminal equipment.

Here, the RLC status report is an RLC status report for multicast service data reception generated by the first RLC entity of the terminal apparatus, and the RLC status report is transmitted by the first RLC entity of the terminal apparatus to the fourth RLC entity of the terminal apparatus.

Here, the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities. The terminal device reports the RLC status report to the network device in a unicast mode. That is, the scheduling information corresponding to the RLC status report is scrambled by the C-RNTI.

In this embodiment of the present application, after receiving an RLC status report sent by a fourth RLC entity of the terminal device, a third RLC entity of the network device sends first indication information or the RLC status report to a second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report; the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report; wherein the second RLC entity belongs to a PTM RLC entity.

Specifically, the second RLC entity of the network device determines SN corresponding to NACK feedback information based on the first indication information or the RLC status report, obtains at least one SN, and sends RLC PDU corresponding to at least one SN to the third RLC entity of the network device. Then, the following step 202 is performed.

In this embodiment of the present application, the network device sends first configuration information to the terminal device, where the terminal device receives the first configuration information sent by the network device, where the first configuration information is used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception; the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode. Further optionally, the first configuration information includes second indication information, where the second indication information is used to indicate that the bearer corresponding to the first RLC entity is only used for downlink data reception.

Here, the AM mode represents an acknowledged mode. UM mode represents unacknowledged mode. For UM mode, no retransmission protocol is used.

Step 202: and the network equipment retransmits the RLC PDU to the terminal equipment in a unicast mode, and the terminal equipment receives the RLC PDU retransmitted by the network equipment in the unicast mode.

In this embodiment of the present application, after the above steps, the third RLC entity of the network device receives RLC PDUs corresponding to at least one SN sent by the second RLC entity of the network device, where the RLC PDUs are RLC PDUs that need to be retransmitted to the terminal device, for this purpose,

the third RLC entity of the network device sends the RLC PDU corresponding to the at least one SN to the fourth RLC entity of the terminal device, the fourth RLC entity of the terminal device receives the RLC PDU corresponding to the at least one SN sent by the third RLC entity of the network device, and sends the RLC PDU corresponding to the at least one SN to the first RLC entity of the terminal device (i.e., the RLC PDU corresponding to the at least one SN is sent by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device).

Further, in an alternative manner, the first RLC entity of the terminal device adjusts the reception window based on the received RLC PDU corresponding to the at least one SN.

According to the technical scheme, the network equipment retransmits the RLC PDU to the terminal equipment, and the RLC PDU is retransmitted to the PTP RLC entity of the terminal equipment through the PTP RLC entity of the network equipment, so that the retransmission of the multicast service data in a unicast mode is realized, and the influence on other terminal equipment which has correctly received the multicast service data is avoided. Optionally, before the multicast service data is retransmitted in the unicast mode, the multicast service data may also be retransmitted in the multicast mode, where the number of retransmissions in the multicast mode needs to be limited, specifically, if the number of retransmissions in the multicast mode exceeds a specified threshold, the multicast service data is transmitted in the unicast mode instead.

Wherein, the retransmission of the multicast service data by using the multicast mode means: the PTM RLC entity of the network device retransmits the RLC PDU to the PTM RLC entity of the terminal device. For specific details of transmitting the multicast service data in the unicast manner, reference may be made to the description of the foregoing scheme, i.e. the PTP RLC entity of the network device retransmits the RLC PDU to the PTP RLC entity of the terminal device.

It should be noted that, for the terminal device, if the PTM RLC entity of the terminal device sends the RLC status report to the PTM RLC entity of the network device (i.e., mode one in the above scheme), the PTM RLC entity of the terminal device sends the RLC status report to the MAC entity first, and the MAC entity multiplexes the RLC status report with other information in the MAC layer, and associates the RLC status report with the RLC ID of the PTM RLC entity of the terminal device. If the PTP RLC entity of the terminal device sends the RLC status report to the PTP RLC entity of the network device (i.e., mode two in the above scheme), the PTP RLC entity of the terminal device sends the RLC status report to the MAC entity first, and the MAC entity multiplexes the RLC status report with other information in the MAC layer and associates the RLC status report with the RLC ID of the PTP RLC entity of the terminal device.

In this embodiment, the network device determines, based on the RLC status report reported by the terminal device, the RLC PDU that needs to be retransmitted to the terminal device, where the RLC PDU retransmitted to the terminal device is an RLC PDU that is not received correctly (i.e., received incorrectly) by the terminal device. The network device may also acquire information (e.g., SN of RLC PDU requiring retransmission) related to RLC PDU requiring retransmission from other devices (e.g., other terminal devices), and determine RLC PDU requiring retransmission according to the information.

The following illustrates the technical solution of the embodiments of the present application in conjunction with specific application examples.

Application example one

Referring to fig. 3, a PTM RLC entity of a terminal device has an AM mode, a PTP RLC entity of a terminal device has an AM mode, a PTM RLC entity of a network device has an AM mode, and a PTP RLC entity of a network device has an AM mode.

The terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring multicast received protocol stack configuration and unicast received protocol stack configuration. In the protocol stack configuration of multicast reception, a PTM RLC entity of the terminal device has an AM mode. Optionally, the first configuration information includes second indication information, where the second indication information is used to indicate that a bearer corresponding to the PTM RLC entity of the terminal device is only used for downlink data reception.

And the terminal equipment receives the multicast service data through the G-RNTI. Specifically, referring to fig. 3, the PTM RLC entity of the terminal device receives multicast service data sent by the PTM RLC entity of the network device. If the reporting of the RLC status report is triggered, the PTM RLC entity of the terminal equipment generates the RLC status report and submits the RLC status report to the MAC entity, and then the RLC status report is sent to the network equipment through the PHY entity. After receiving the RLC status report, the PTM RLC entity of the network device sends RLC PDU corresponding to SN corresponding to NACK information indicated by the RLC status report to the PTP RLC entity of the network device, and triggers retransmission of the RLC PDU. The PTP RLC entity of the terminal equipment receives the RLC PDU retransmitted by the PTP RLC entity of the network equipment, and sends the RLC PDU to the PTM RLC entity of the terminal equipment. The PTM RLC entity of the terminal equipment adjusts the receiving window based on the received RLC PDU.

Application example two

Referring to fig. 4, a PTM RLC entity of a terminal device has an AM mode or a UM mode, a PTP RLC entity of a terminal device has an AM mode, a PTM RLC entity of a network device has an AM mode or a UM mode, and a PTP RLC entity of a network device has an AM mode.

The terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring multicast received protocol stack configuration and unicast received protocol stack configuration. In the protocol stack configuration of multicast reception, the PTM RLC entity of the terminal device has an AM mode or UM mode. Optionally, the first configuration information includes second indication information, where the second indication information is used to indicate that a bearer corresponding to the PTM RLC entity of the terminal device is only used for downlink data reception.

And the terminal equipment receives the multicast service data through the G-RNTI. Specifically, referring to fig. 3, the PTM RLC entity of the terminal device receives multicast service data sent by the PTM RLC entity of the network device. If the report of the RLC status report is triggered, the PTM RLC entity of the terminal equipment generates the RLC status report and sends the RLC status report to the PTP RLC entity of the terminal equipment, and the PTP RLC entity of the terminal equipment submits the RLC status report to the MAC entity and then sends the RLC status report to the network equipment through the PHY entity. After receiving the RLC status report, the PTP RLC entity of the network device forwards the first indication information or the status report to the PTM RLC entity of the network device. The PTM RLC entity of the network equipment adjusts an RLC sending window based on the RLC status reports or the first indication information of all users in the multicast group, and sends the RLC PDU corresponding to the SN corresponding to the NACK information to the PTP RLC entity of the network equipment, and triggers retransmission of the RLC PDU. The PTP RLC entity of the terminal equipment receives the RLC PDU retransmitted by the PTP RLC entity of the network equipment, and sends the RLC PDU to the PTM RLC entity of the terminal equipment. The PTM RLC entity of the terminal equipment adjusts the receiving window based on the received RLC PDU.

Fig. 5 is a schematic structural diagram of a retransmission apparatus for multicast service provided in an embodiment of the present application, which is applied to a terminal device, as shown in fig. 5, where the retransmission apparatus for multicast service includes:

A generating unit 501, configured to generate an RLC status report for multicast service data reception;

a sending unit 502, configured to send the RLC status report to a network device, where the RLC status report is used for determining, by the network device, RLC PDUs that need to be retransmitted;

a receiving unit 503, configured to receive RLC PDUs retransmitted by the network device in a unicast manner.

In an alternative manner, the terminal device has a first RLC entity;

the generating unit 501 is configured to generate, by using a first RLC entity of the terminal device, an RLC status report for multicast service data reception;

the sending unit 502 is configured to send, by using a first RLC entity of the terminal device, the RLC status report to a second RLC entity of a network device;

wherein the first RLC entity and the second RLC entity belong to a PTM RLC entity.

In an optional manner, the RLC status report is used for the second RLC entity of the network device to send an RLC PDU corresponding to at least one SN to a third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the RLC status report, and the third RLC entity belongs to a PTP RLC entity.

In an alternative manner, the terminal device further has a fourth RLC entity;

the receiving unit 503 is configured to receive, by using a fourth RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN sent by a third RLC entity of the network device;

the sending unit 502 is further configured to send, to the first RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN through a fourth RLC entity of the terminal device, where the fourth RLC entity belongs to a PTP RLC entity;

the apparatus further comprises: an adjustment unit (not shown in the figure) is configured to adjust, by the first RLC entity of the terminal device, the reception window based on the received RLC PDU corresponding to the at least one SN.

In an optional manner, the receiving unit 503 is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a protocol stack configuration of multicast reception and/or a protocol stack configuration of unicast reception;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.

In an alternative manner, the terminal device has a first RLC entity and a fourth RLC entity;

the sending unit 502 is configured to send, by the first RLC entity of the terminal device, the RLC status report to a fourth RLC entity of the terminal device; and transmitting the RLC status report to a third RLC entity of the network device by a fourth RLC entity of the terminal device;

wherein the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities.

In an optional manner, the third RLC entity of the network device sends first indication information or the RLC status report to the second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report;

the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report;

Wherein the second RLC entity belongs to a PTM RLC entity.

In an optional manner, the receiving unit 503 is further configured to receive, by using a fourth RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN sent by a third RLC entity of the network device, and send the RLC PDU corresponding to the at least one SN to a first RLC entity of the terminal device;

the apparatus further comprises: and the adjusting unit is used for adjusting the receiving window based on the received RLC PDU corresponding to the at least one SN through the first RLC entity of the terminal equipment.

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.

In an alternative manner, the first configuration information includes second indication information, where the second indication information is used to indicate that the bearer corresponding to the first RLC entity is only used for downlink data reception.

In an alternative manner, the terminal device has a first RLC entity;

the receiving unit 503 is further configured to receive, by using a first RLC entity of the terminal device, multicast service data sent by a second RLC entity of the network device, where scheduling information of the multicast service data is scrambled by a G-RNTI, and the first RLC entity and the second RLC entity belong to a PTM RLC entity.

It should be understood by those skilled in the art that the description of the retransmission apparatus for multicast service according to the embodiments of the present application may be understood with reference to the description of the retransmission method for multicast service according to the embodiments of the present application.

Fig. 6 is a schematic diagram ii of a structural composition of a retransmission apparatus for multicast service provided in an embodiment of the present application, which is applied to a network device, as shown in fig. 6, where the retransmission apparatus for multicast service includes:

a receiving unit 601, configured to receive an RLC status report sent by a terminal device, where the RLC status report is an RLC status report generated by the terminal device and used for determining, by the network device, an RLC PDU that needs to be retransmitted;

a sending unit 602, configured to retransmit RLC PDUs to the terminal device in a unicast manner.

In an alternative manner, the RLC status report is an RLC status report for multicast service data reception generated by a first RLC entity of the terminal apparatus;

the receiving unit 601 is configured to receive, by using a second RLC entity of the network device, an RLC status report sent by a first RLC entity of the terminal device;

In an optional manner, the sending unit 602 is configured to send, to a fourth RLC entity of the terminal device, the RLC PDU corresponding to the at least one SN through a third RLC entity of the network device, where the RLC PDU corresponding to the at least one SN is sent by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device, and the fourth RLC entity belongs to a PTP RLC entity.

In an optional manner, the sending unit 602 is further configured to send first configuration information to the terminal device, where the first configuration information is used to determine a protocol stack configuration of multicast reception and/or a protocol stack configuration of unicast reception;

In an alternative manner, the RLC status report is an RLC status report generated by the first RLC entity of the terminal device for receiving multicast service data, where the RLC status report is sent by the first RLC entity of the terminal device to the fourth RLC entity of the terminal device;

the receiving unit 601 is configured to receive, by using a third RLC entity of the network device, the RLC status report sent by a fourth RLC entity of the terminal device;

In an optional manner, the sending unit 602 is further configured to send, by the third RLC entity of the network device, first indication information or the RLC status report to the second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report;

wherein the second RLC entity belongs to a PTM RLC entity.

In an alternative manner, the sending unit 602 is configured to send, by the third RLC entity of the network device, the RLC PDU corresponding to the at least one SN to the fourth RLC entity of the terminal device, where the RLC PDU corresponding to the at least one SN is sent by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device.

In an alternative manner, the sending unit 602 is further configured to send, by using a second RLC entity of the network device, multicast service data to a first RLC entity of the terminal device, where scheduling information of the multicast service data is scrambled by using a G-RNTI, and the first RLC entity and the second RLC entity belong to a PTM RLC entity.

Fig. 7 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 700 shown in fig. 7 includes a processor 710, where the processor 710 may call and execute a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 7, the communication device 700 may further comprise a memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the methods in embodiments of the present application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, as shown in fig. 7, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices.

Among other things, transceiver 730 may include a transmitter and a receiver. Transceiver 730 may further include antennas, the number of which may be one or more.

Optionally, the communication device 700 may be specifically a network device in the embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 700 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 700 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 8 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 800 shown in fig. 8 includes a processor 810, and the processor 810 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 8, chip 800 may also include memory 820. Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application.

Wherein the memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.

Optionally, the chip 800 may also include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 9, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of retransmitting multicast traffic, the method comprising:

the method comprises the steps that a terminal device generates a Radio Link Control (RLC) status report aiming at multicast service data reception, and sends the RLC status report to a network device, wherein the RLC status report is used for determining a radio link control packet data unit (RLC PDU) needing to be retransmitted by the network device;

and the terminal equipment receives the RLC PDU retransmitted by the network equipment in a unicast mode.
The method of claim 1, wherein the terminal device generates an RLC status report for multicast service data reception, and sends the RLC status report to a network device, comprising:

a first RLC entity of terminal equipment generates an RLC status report for multicast service data reception, and sends the RLC status report to a second RLC entity of network equipment;

wherein the first RLC entity and the second RLC entity belong to a point-to-multipoint PTM RLC entity.
The method of claim 2, wherein the RLC status report is for a second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to a third RLC entity of the network device, the at least one SN being an SN corresponding to NACK feedback information indicated by the RLC status report, the third RLC entity belonging to a peer-to-peer PTP RLC entity.
The method of claim 3, wherein the terminal device receiving RLC PDUs retransmitted by the network device in a unicast manner, comprises:

a fourth RLC entity of the terminal equipment receives the RLC PDU corresponding to the at least one SN sent by a third RLC entity of the network equipment, and sends the RLC PDU corresponding to the at least one SN to a first RLC entity of the terminal equipment, wherein the fourth RLC entity belongs to a PTP RLC entity;

the method further comprises the steps of: and the first RLC entity of the terminal equipment adjusts the receiving window based on the received RLC PDU corresponding to the at least one SN.
The method of any of claims 2 to 4, wherein the method further comprises:

the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for determining multicast received protocol stack configuration and/or unicast received protocol stack configuration;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The method of claim 1, wherein the terminal device generates an RLC status report for multicast service data reception, sends the RLC status report to a network device, the RLC status report being for RLC PDUs that the network device determines need for retransmission, comprising:

the method comprises the steps that a first RLC entity of terminal equipment generates an RLC status report for multicast service data reception, and the RLC status report is sent to a fourth RLC entity of the terminal equipment;

the fourth RLC entity of the terminal device sends the RLC status report to a third RLC entity of the network device;

wherein the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities.
The method of claim 6, wherein the method further comprises:

the third RLC entity of the network device sends first indication information or the RLC status report to the second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report;

the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report;

Wherein the second RLC entity belongs to a PTM RLC entity.
The method of claim 7, wherein the terminal device receiving RLC PDUs retransmitted by the network device in a unicast manner, comprises:

the fourth RLC entity of the terminal device receives the RLC PDU corresponding to the at least one SN sent by the third RLC entity of the network device, and sends the RLC PDU corresponding to the at least one SN to the first RLC entity of the terminal device;

the method further comprises the steps of: and the first RLC entity of the terminal equipment adjusts the receiving window based on the received RLC PDU corresponding to the at least one SN.
The method of any of claims 6 to 8, wherein the method further comprises:

the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for determining multicast received protocol stack configuration and/or unicast received protocol stack configuration;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The method of claim 5 or 9, wherein the first configuration information includes second indication information, the second indication information being used to indicate that a bearer corresponding to the first RLC entity is only used for downlink data reception.
The method according to any of claims 1 to 10, wherein before the terminal device generates an RLC status report for multicast service data reception, the method further comprises:

and the first RLC entity of the terminal equipment receives the multicast service data sent by the second RLC entity of the network equipment, wherein the scheduling information of the multicast service data is scrambled by G-RNTI, and the first RLC entity and the second RLC entity belong to a PTM RLC entity.
A method of retransmitting multicast traffic, the method comprising:

the network equipment receives an RLC status report sent by the terminal equipment, wherein the RLC status report is generated by the terminal equipment and used for receiving multicast service data, and the RLC status report is used for determining RLC PDU (protocol data unit) needing to be retransmitted by the network equipment;

and the network equipment retransmits the RLC PDU to the terminal equipment in a unicast mode.
The method of claim 12, wherein the RLC status report is an RLC status report for multicast service data reception generated by a first RLC entity of the terminal apparatus;

The network device receives an RLC status report sent by a terminal device, including:

the second RLC entity of the network equipment receives an RLC status report sent by the first RLC entity of the terminal equipment;

wherein the first RLC entity and the second RLC entity belong to a PTM RLC entity.
The method of claim 13, wherein the RLC status report is for a second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to a third RLC entity of the network device, the at least one SN being an SN corresponding to NACK feedback information indicated by the RLC status report, the third RLC entity belonging to a PTP RLC entity.
The method of claim 14, wherein the network device retransmitting RLC PDUs to the terminal device in a unicast manner, comprising:

the third RLC entity of the network device sends RLC PDUs corresponding to the at least one SN to a fourth RLC entity of the terminal device, where the RLC PDUs corresponding to the at least one SN are sent by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device, and the fourth RLC entity belongs to a PTP RLC entity.
The method of any of claims 13 to 15, wherein the method further comprises:

The network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for determining multicast received protocol stack configuration and/or unicast received protocol stack configuration;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The method of claim 12, wherein the RLC status report is an RLC status report generated by a first RLC entity of the terminal device for reception of multicast service data, the RLC status report being sent by the first RLC entity of the terminal device to a fourth RLC entity of the terminal device;

the network device receives an RLC status report sent by a terminal device, including:

the third RLC entity of the network equipment receives the RLC status report sent by the fourth RLC entity of the terminal equipment;

wherein the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities.
The method of claim 17, wherein the method further comprises:

The third RLC entity of the network device sends first indication information or the RLC status report to the second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report;

the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report;

wherein the second RLC entity belongs to a PTM RLC entity.
The method of claim 18, wherein the network device retransmitting RLC PDUs to the terminal device in a unicast manner, comprising:

and the third RLC entity of the network equipment sends the RLC PDU corresponding to the at least one SN to the fourth RLC entity of the terminal equipment, and the fourth RLC entity of the terminal equipment sends the RLC PDU corresponding to the at least one SN to the first RLC entity of the terminal equipment.
The method of any of claims 17 to 19, wherein the method further comprises:

The network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for determining multicast received protocol stack configuration and/or unicast received protocol stack configuration;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The method of claim 16 or 20, wherein the first configuration information includes second indication information, the second indication information being used to indicate that a bearer corresponding to the first RLC entity is only used for downlink data reception.
The method according to any of claims 12 to 21, wherein before the network device receives the RLC status report sent by the terminal device, the method further comprises:

and the second RLC entity of the network equipment sends multicast service data to the first RLC entity of the terminal equipment, wherein the scheduling information of the multicast service data is scrambled by G-RNTI, and the first RLC entity and the second RLC entity belong to a PTM RLC entity.
A retransmission apparatus of a multicast service, applied to a terminal device, the apparatus comprising:

A generating unit, configured to generate an RLC status report for multicast service data reception;

a sending unit, configured to send the RLC status report to a network device, where the RLC status report is used for determining, by the network device, an RLC PDU that needs to be retransmitted;

and the receiving unit is used for receiving the RLC PDU retransmitted by the network equipment in a unicast mode.
The apparatus of claim 23, wherein the terminal device has a first RLC entity;

the generating unit is configured to generate, by using a first RLC entity of the terminal device, an RLC status report for multicast service data reception;

the sending unit is configured to send, by using a first RLC entity of the terminal device, the RLC status report to a second RLC entity of a network device;

wherein the first RLC entity and the second RLC entity belong to a PTM RLC entity.
The apparatus of claim 24, wherein the RLC status report is for a second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to a third RLC entity of the network device, the at least one SN being an SN corresponding to NACK feedback information indicated by the RLC status report, the third RLC entity belonging to a PTP RLC entity.
The apparatus of claim 25, wherein the terminal device further has a fourth RLC entity;

the receiving unit is configured to receive, by using a fourth RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN sent by a third RLC entity of the network device;

the sending unit is further configured to send, to the first RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN through a fourth RLC entity of the terminal device, where the fourth RLC entity belongs to a PTP RLC entity;

the apparatus further comprises: and the adjusting unit is used for adjusting the receiving window based on the received RLC PDU corresponding to the at least one SN through the first RLC entity of the terminal equipment.
The apparatus according to any one of claims 24 to 26, wherein the receiving unit is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The apparatus of claim 23, wherein the terminal device has a first RLC entity and a fourth RLC entity;

the generating unit is configured to generate, by using a first RLC entity of the terminal device, an RLC status report for multicast service data reception;

the sending unit is configured to send, by using a first RLC entity of the terminal device, the RLC status report to a fourth RLC entity of the terminal device; and transmitting the RLC status report to a third RLC entity of the network device by a fourth RLC entity of the terminal device;

wherein the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities.
The apparatus of claim 28, wherein a third RLC entity of the network device sends first indication information indicating an SN corresponding to NACK feedback information and/or an SN corresponding to ACK information, or the RLC status report, to a second RLC entity of the network device, the first indication information being determined based on the RLC status report;

the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report;

Wherein the second RLC entity belongs to a PTM RLC entity.
The apparatus of claim 29, wherein,

the receiving unit is further configured to receive, by using a fourth RLC entity of the terminal device, an RLC PDU corresponding to the at least one SN sent by a third RLC entity of the network device, and send the RLC PDU corresponding to the at least one SN to a first RLC entity of the terminal device;

the apparatus further comprises: and the adjusting unit is used for adjusting the receiving window based on the received RLC PDU corresponding to the at least one SN through the first RLC entity of the terminal equipment.
The apparatus according to any one of claims 28 to 30, wherein the receiving unit is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The apparatus of claim 27 or 31, wherein the first configuration information comprises second indication information, the second indication information being used to indicate that a bearer corresponding to the first RLC entity is only used for downlink data reception.
The apparatus of any of claims 23 to 32, wherein the terminal device has a first RLC entity;

the receiving unit is further configured to receive, by using a first RLC entity of the terminal device, multicast service data sent by a second RLC entity of the network device, where scheduling information of the multicast service data is scrambled by using a G-RNTI, and the first RLC entity and the second RLC entity belong to a PTM RLC entity.
A retransmission apparatus of multicast traffic applied to a network device, the apparatus comprising:

a receiving unit, configured to receive an RLC status report sent by a terminal device, where the RLC status report is an RLC status report generated by the terminal device and used for determining, by the network device, an RLC PDU that needs to be retransmitted;

and the sending unit is used for retransmitting the RLC PDU to the terminal equipment in a unicast mode.
The apparatus of claim 34, wherein the RLC status report is an RLC status report for multicast service data reception generated by a first RLC entity of the terminal device;

the receiving unit is configured to receive, by using a second RLC entity of the network device, an RLC status report sent by a first RLC entity of the terminal device;

Wherein the first RLC entity and the second RLC entity belong to a PTM RLC entity.
The apparatus of claim 35, wherein the RLC status report is for a second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to a third RLC entity of the network device, the at least one SN being an SN corresponding to NACK feedback information indicated by the RLC status report, the third RLC entity belonging to a PTP RLC entity.
The apparatus of claim 36, wherein the means for transmitting, by the third RLC entity of the network device, the RLC PDU corresponding to the at least one SN to a fourth RLC entity of the terminal device, the RLC PDU corresponding to the at least one SN being transmitted by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device, the fourth RLC entity belonging to a PTP RLC entity.
The apparatus according to any of claims 35 to 37, wherein the sending unit is further configured to send first configuration information to the terminal device, the first configuration information being used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The apparatus of claim 34, wherein the RLC status report is an RLC status report generated by a first RLC entity of the terminal device for reception of multicast service data, the RLC status report being sent by the first RLC entity of the terminal device to a fourth RLC entity of the terminal device;

the receiving unit is configured to receive, by using a third RLC entity of the network device, the RLC status report sent by a fourth RLC entity of the terminal device;

wherein the first RLC entity belongs to a PTM RLC entity, and the third RLC entity and the fourth RLC entity belong to PTP RLC entities.
The apparatus of claim 39, wherein the sending unit is further configured to send, by a third RLC entity of the network device, first indication information or the RLC status report to a second RLC entity of the network device, where the first indication information is used to indicate SN corresponding to NACK feedback information and/or SN corresponding to ACK information, and the first indication information is determined based on the RLC status report;

the first indication information or the RLC status report is used for the second RLC entity of the network device to send RLC PDUs corresponding to at least one SN to the third RLC entity of the network device, where the at least one SN is an SN corresponding to NACK feedback information indicated by the first indication information or the RLC status report;

Wherein the second RLC entity belongs to a PTM RLC entity.
The apparatus of claim 40, wherein the transmitting unit is configured to transmit, by the third RLC entity of the network device, the RLC PDU corresponding to the at least one SN to the fourth RLC entity of the terminal device, the RLC PDU corresponding to the at least one SN being transmitted by the fourth RLC entity of the terminal device to the first RLC entity of the terminal device.
The apparatus according to any of claims 39 to 41, wherein the sending unit is further configured to send first configuration information to the terminal device, the first configuration information being used to determine a protocol stack configuration for multicast reception and/or a protocol stack configuration for unicast reception;

the protocol stack of the multicast reception is configured to determine that a mode of a first RLC entity of the terminal device is an AM mode or an UM mode; the unicast received protocol stack is configured to determine that a mode of a fourth RLC entity of the terminal device is an AM mode.
The apparatus of claim 38 or 42, wherein the first configuration information comprises second indication information, the second indication information being used to indicate that a bearer corresponding to the first RLC entity is only used for downlink data reception.
The apparatus of any one of claims 34 to 43, wherein the sending unit is further configured to send multicast service data to a first RLC entity of the terminal device through a second RLC entity of the network device, wherein scheduling information of the multicast service data is scrambled through a G-RNTI, the first RLC entity and the second RLC entity belonging to a PTM RLC entity.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 11.
A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 12 to 22.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 11.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 12 to 22.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 11.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 12 to 22.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 11.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 12 to 22.
A computer program which causes a computer to perform the method of any one of claims 1 to 11.
A computer program which causes a computer to perform the method of any of claims 12 to 22.