CN114071372A

CN114071372A - Multicast broadcast service MBS transmission method, terminal and network equipment

Info

Publication number: CN114071372A
Application number: CN202010789109.3A
Authority: CN
Inventors: 谌丽; 张大钧
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2022-02-18
Anticipated expiration: 2040-08-07
Also published as: CN114071372B

Abstract

The invention provides a multicast broadcast service MBS transmission method, a terminal and network equipment, wherein the method comprises the following steps: and sending first feedback information to the network equipment through the layer 2 entity of unicast transmission, wherein the first feedback information is used for indicating the receiving condition of the terminal on the multicast broadcast data packet. The invention can solve the problem that the transmission reliability of the MBS service can not be ensured because the terminal can not effectively feed back and require the network equipment to retransmit when the network equipment transmits the multicast broadcast data packet to the terminal at present.

Description

Multicast broadcast service MBS transmission method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a multicast broadcast service MBS transmission method, a terminal, and a network device.

Background

Multicast Broadcast Multimedia Service (MBMS) services have long existed in The 3rd Generation Mobile Communications, 3G, fourth Generation Mobile Communications technology (4G) technologies. Fig. 1 is an MBMS transmission architecture based on multimedia Broadcast multicast service Single Frequency network mbsfn (multimedia Broadcast multicast service Single Frequency network) in Long Term Evolution (LTE).

Services that need to be broadcast multicast transmitted are mapped into a broadcast multicast channel for transmission to multiple terminals. As shown in fig. 2, which is a downlink Channel map in fig. 4G, a Multicast Control Channel (MCCH) and a Single Cell Multicast Control Channel (SC-MCCH) are Multicast broadcast Control channels, and a Multicast Traffic Channel (MTCH) and a Single Cell Multicast Traffic Channel (SC-MTCH) are Multicast broadcast Traffic channels, and these channels are used for transmitting Multicast broadcast Traffic data; a Dedicated Control Channel (DCCH) and a Dedicated Traffic Channel (DTCH) for a base station to perform dedicated signaling and data transmission to a single terminal; a Physical Control Channel (PCCH) for transmitting a paging message; a Broadcast Control Channel (BCCH) for broadcasting common information to the terminals by the base station; common Control Channel (CCCH) for transmitting control information required for link connection in a call connection phase; a Multicast Channel (MCH) for supporting MBMS; a Paging Channel (PCH) for transmitting information on the PCCH logical Channel; a Broadcast Channel (BCH) for transmitting information on the BCCH logical channel; a Downlink Shared Channel (DL-SCH), a transport Channel for transmitting Downlink data in LTE.

Due to the demand of Broadcast-Multicast Services, the fifth Generation mobile communication technology (5th-Generation, 5G) will introduce MBMS Services, and in 5G, it is called Multicast and Broadcast Services (MBS). The 5G does not need to introduce an MBSFN framework, and each cell independently sends MBS service. The MBS service transmits a Multicast Radio Bearer (MRB) through a Multicast broadcast channel, the base station transmits a plurality of terminals simultaneously, and when a single terminal fails to receive, effective feedback cannot be performed and network equipment is required to perform retransmission, so that the transmission reliability of the MBS service cannot be guaranteed.

Disclosure of Invention

The invention provides a multicast broadcast service MBS transmission method, a terminal and network equipment, which solve the problem that the transmission reliability of MBS service can not be ensured because the terminal can not effectively feed back and the network equipment is required to retransmit when the network equipment transmits a multicast broadcast data packet to the terminal at present.

To achieve the above object, an embodiment of the present invention is implemented by:

in a first aspect, an embodiment of the present invention provides a method for transmitting a multicast broadcast service MBS, including:

and sending first feedback information to the network equipment through the layer 2 entity of unicast transmission, wherein the first feedback information is used for indicating the receiving condition of the terminal on the multicast broadcast data packet.

Optionally, the method further comprises:

and sending second feedback information to the network equipment through the layer 2 entity of unicast transmission, wherein the second feedback information is used for indicating the receiving condition of a terminal on a downlink unicast data packet corresponding to the layer 2 entity of unicast transmission, and the first feedback information carries a type identifier.

Optionally, the sending, by the layer 2 entity in unicast transmission, the first feedback information to the network device includes:

the Radio Link Control (RLC) entity transmits an RLC status report of a multicast broadcast data packet to network equipment through a unicast transmission radio link;

alternatively, the first and second electrodes may be,

and sending a PDCP status report of the multicast broadcast data packet to the network equipment through the packet data convergence protocol PDCP entity of the unicast transmission.

Optionally, a control protocol data unit type CPT field in the RLC status report is set to a first preset value, where the first preset value is used to indicate that the RLC status report is an RLC status report of a multicast broadcast packet;

alternatively, the first and second electrodes may be,

and setting a Protocol Data Unit (PDU) type field in the PDCP status report to be a second preset value, wherein the second preset value is used for indicating that the PDCP status report is a PDCP status report of a multicast broadcast data packet.

Optionally, after the layer 2 entity transmitting the first feedback information to the network device through unicast transmission, the method further includes:

receiving a first data packet transmitted by the network device, wherein the first data packet is a retransmission data packet of the multicast broadcast data packet which is not successfully received and indicated by the first feedback information.

Optionally, the receiving the first data packet transmitted by the network device includes:

receiving the first data packet transmitted by the network equipment through a layer 2 entity of multicast transmission;

alternatively, the first and second electrodes may be,

receiving the first data packet transmitted by the network device through a layer 2 entity of unicast transmission.

In a second aspect, an embodiment of the present application further provides a terminal, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, the processor implementing the steps when executing the program of:

Optionally, the processor, when executing the program, implements the following steps:

alternatively, the first and second electrodes may be,

after first feedback information is sent to a network device through a layer 2 entity of unicast transmission, a first data packet transmitted by the network device is received, wherein the first data packet is a retransmission data packet of a multicast broadcast data packet which is not successfully received and indicated by the first feedback information.

alternatively, the first and second electrodes may be,

In a third aspect, an embodiment of the present invention further provides a terminal, including:

a sending module, configured to send first feedback information to a network device through a layer 2 entity in unicast transmission, where the first feedback information is used to indicate a receiving condition of a terminal for a multicast broadcast data packet.

In a fourth aspect, an embodiment of the present invention further provides a readable storage medium, on which a program is stored, where the program is executed by a processor to implement the steps of the MBS transmission method according to the first aspect.

In a fifth aspect, an embodiment of the present invention further provides a method for transmitting a multicast broadcast service MBS, including:

and receiving first feedback information sent by a terminal through a layer 2 entity of unicast transmission, wherein the first feedback information is used for indicating the receiving condition of the terminal on the multicast broadcast data packet.

Optionally, after receiving the first feedback information sent by the terminal through the layer 2 entity in unicast transmission, the method further includes:

and transmitting a first data packet to the terminal according to the first feedback information, wherein the first data packet is a retransmission data packet of a multicast broadcast data packet which is indicated by the first feedback information and is not successfully received by the terminal.

Optionally, the transmitting the first data packet to the terminal includes:

transmitting the first data packet to the terminal through a layer 2 entity of multicast transmission;

alternatively, the first and second electrodes may be,

and transmitting the first data packet to the terminal through a layer 2 entity of unicast transmission.

Optionally, when the first data packet is transmitted to the terminal through a layer 2 entity of unicast transmission, and a second data packet of unicast is also transmitted to the terminal through the layer 2 entity of unicast transmission, the first data packet carries identification information, where the identification information is used to indicate that the first data packet is a retransmission data packet of a multicast broadcast data packet.

Optionally, in a case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, the transmitting the first data packet to the terminal includes:

if receiving an RLC status report of a multicast broadcast data packet sent by a Radio Link Control (RLC) entity through unicast transmission by a terminal, determining an unsuccessfully received PDCP PDU according to an unsuccessfully received RLC Protocol Data Unit (PDU) indicated by the RLC status report, and transmitting the PDCP PDU to the terminal through a unicast or multicast layer 2 entity;

alternatively, the first and second electrodes may be,

in the case that multicast transmission and unicast transmission correspond to different PDCP entities, the transmitting the first data packet to the terminal by the layer 2 entity of unicast transmission includes:

if receiving a PDCP status report of a multicast broadcast data packet sent by a PDCP entity of unicast transmission by a terminal, converting the MRB PDCP PDU into a PDCP service data unit SDU according to the unsuccessfully received multicast broadcast radio bearer MRB PDCP PDU indicated by the PDCP status report, and converting the PDCP SDU into a data radio bearer DRB PDCP PDU according to a layer 2 entity rule of unicast transmission and transmitting the data radio bearer DRB PDCP PDU to the terminal.

In a sixth aspect, an embodiment of the present invention further provides a network device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, the processor implementing the steps when executing the program of:

alternatively, the first and second electrodes may be,

Optionally, in a case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, the processor when executing the program implements the following steps:

alternatively, the first and second electrodes may be,

in the case that the multicast transmission and the unicast transmission correspond to different PDCP entities, the processor, when executing the program, implements the following steps:

In a seventh aspect, an embodiment of the present invention further provides a network device, including:

the receiving module is configured to receive first feedback information sent by a terminal through a layer 2 entity in unicast transmission, where the first feedback information is used to indicate a receiving condition of a multicast broadcast packet by the terminal.

In an eighth aspect, an embodiment of the present invention further provides a readable storage medium, on which a program is stored, where the program is executed by a processor to implement the steps of the MBS transmission method according to the fifth aspect.

The technical scheme of the invention has the beneficial effects that: the terminal feeds back the receiving condition of the multicast broadcast data packet to the network equipment through the layer 2 entity of unicast transmission, and the problem that the transmission reliability of the MBS service cannot be ensured because the terminal cannot effectively feed back and the network equipment is required to retransmit when the multicast broadcast data packet is transmitted to the terminal by the network equipment at present is solved.

Drawings

Fig. 1 shows a schematic diagram of an MBSFN-based MBMS transmission architecture in LTE;

fig. 2 shows a schematic diagram of downlink channel mapping in 4G;

fig. 3 shows a MBS service transmission diagram according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a protocol stack architecture of an access network air interface user plane according to an embodiment of the present invention;

fig. 5 is a flowchart illustrating an MBS transmission method at a terminal side according to an embodiment of the present invention;

FIG. 6a is a diagram illustrating an RLC status report format with an SN length of 12 bits according to an embodiment of the present invention;

FIG. 6b is a diagram illustrating an RLC status report format with an SN length of 18 bits according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a PDCP status report format according to an embodiment of the present invention;

fig. 8 shows one of the configuration block diagrams of a terminal of the embodiment of the present invention;

fig. 9 shows a second block diagram of the terminal according to the embodiment of the present invention;

fig. 10 is a flowchart illustrating an MBS transmission method on a network device side according to an embodiment of the present invention;

fig. 11 is a second schematic diagram of a protocol stack architecture of an access network air interface user plane according to an embodiment of the present invention;

fig. 12 is a third schematic diagram of a protocol stack architecture of an access network air interface user plane according to an embodiment of the present invention;

fig. 13 is a fourth schematic diagram illustrating a protocol stack architecture of an access network air interface user plane according to an embodiment of the present invention;

fig. 14 is a fifth schematic diagram illustrating a protocol stack architecture of an access network air interface user plane according to an embodiment of the present invention;

FIG. 15 is a block diagram of a network device according to an embodiment of the present invention;

fig. 16 shows a second block diagram of the network device according to the embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the full understanding of the embodiments of the present invention. Thus, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In addition, the terms "system" and "network" are often used interchangeably herein.

In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

In the embodiment of the present invention, the access network may be an access network including a Macro Base Station (Macro Base Station), a micro Base Station (Pico Base Station), a Node B (3G mobile Station), an enhanced Base Station (eNB), a 5G mobile Base Station (gNB), a Home enhanced Base Station (Femto eNB or Home eNode B or Home eNB or HeNB), a relay Station, an access point, an RRU (Remote Radio Unit, Remote Radio module), an RRH (Remote Radio Head), and the like. The user terminal may be a mobile phone (or handset), or other device capable of sending or receiving wireless signals, including user Equipment, a Personal Digital Assistant (PDA), a wireless modem, a wireless communicator, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a CPE (Customer Premise Equipment) or a mobile smart hotspot capable of converting mobile signals into WiFi signals, a smart appliance, or other devices capable of autonomously communicating with a mobile communication network without human operation, and so on.

In the 5G system, MBS service is also introduced due to the requirement of broadcast multicast service, and each cell in the 5G system independently sends MBS service, as shown in fig. 3, a schematic diagram of MBS service transmission is given.

As shown in fig. 4, in the 5G system, data mapping is performed by a stream (flow) method. The core network is responsible for mapping Internet Protocol (IP) flow to Quality of Service (QoS) flow, and the access network is responsible for mapping QoS flow to Radio Bearer (RB). As shown in fig. 4, a Service Data Application Protocol (SDAP) layer is responsible for mapping QoS Flow to RB, where one QoS Flow can only be mapped to one RB, the QoS Flow is identified by a QoS Flow identification number (QoS Flow ID, QFI) and further mapped to a logical channel, and Data organization and scheduling transmission are performed based on the logical channel priority in a Media Access Control (MAC) layer.

A Packet Data Convergence Protocol (PDCP) entity and a Radio Link Control (RLC) entity corresponding to one RB at a transmitting end and a receiving end are respectively referred to as a peer PDCP entity and a peer RLC entity. For an RB configured as an RLC Acknowledged Mode (AM) (the RLC entity corresponding to the RB is bidirectional in transceiving), the PDCP entity of the receiving end may send feedback, i.e., a PDCP status report, to the peer PDCP entity of the transmitting end, reflecting a receiving condition of a PDCP Protocol Data Unit (PDU); the RLC entity at the receiving end may send an Automatic Repeat request (ARQ) feedback, i.e., an RLC status report, to the peer RLC entity at the transmitting end, to reflect the receiving condition of the RLC PDU.

Specifically, the embodiment of the present invention provides a method for transmitting a multicast broadcast service MBS, which solves the problem that when a network device transmits a multicast broadcast data packet to a terminal at present, the terminal cannot perform effective feedback and the network device is required to perform retransmission, so that the transmission reliability of the MBS cannot be guaranteed.

As shown in fig. 5, an embodiment of the present invention provides a method for transmitting a multicast broadcast service MBS, which specifically includes the following steps:

step 51: and sending first feedback information to the network equipment through the layer 2 entity of unicast transmission, wherein the first feedback information is used for indicating the receiving condition of the terminal on the multicast broadcast data packet.

Optionally, the receiving condition of the multicast broadcast packet may include a receiving condition of a multicast broadcast packet transmitted by the network device in a multicast manner, and may also include a multicast broadcast packet transmitted by the network device in a unicast manner.

Optionally, the receiving condition of the multicast broadcast packet by the terminal may include: the identification information of the multicast broadcast data packet received by the terminal, and/or the identification information of the multicast broadcast data packet not received by the terminal.

In the embodiment, the terminal feeds back the receiving condition of the multicast broadcast data packet to the network equipment through the layer 2 entity of unicast transmission, so that the problem that the transmission reliability of the MBS service cannot be guaranteed because the terminal cannot effectively feed back and the network equipment is required to retransmit when the network equipment transmits the multicast broadcast data packet to the terminal at present is solved.

Alternatively, the network device may refer to a base station or a node with a base station function in an Integrated Access and Backhaul (IAB) or Relay (Relay) system.

Optionally, the step of sending the first feedback information to the network device through the layer 2 entity of unicast transmission may specifically include:

and sending the RLC status report of the multicast broadcast data packet to the network equipment through the RLC entity of the unicast transmission.

Specifically, the RLC status report of the multicast broadcast packet is fed back by the unicast uplink RLC entity, that is, the terminal uses the unicast RLC entity, and sends the condition that the terminal receives the multicast broadcast packet to the network device in the uplink direction, that is, the terminal uses the unicast RLC entity and sends the RLC status report of the downlink RLC entity corresponding to the multicast broadcast packet to the network device.

Optionally, before the terminal sends the RLC status report of the multicast broadcast packet to the network device through the RLC entity for unicast transmission, the network device configures, for the terminal, a unicast uplink RLC entity corresponding to the downlink RLC sending entity of the multicast broadcast packet, and is used to send the RLC status report of the multicast broadcast packet.

For example: the network device maps the QoS flow of the MBS service to an MRB and a Data Radio Bearer (DRB) respectively, and the MRB and the DRB respectively correspond to a set of PDCP entity and RLC entity. The network equipment sends MRB data packets on a PDCP/RLC entity corresponding to the MRB in a multicast mode; and the network equipment receives the RLC status report sent by the terminal through the RLC entity of the DRB.

For another example: the network equipment maps the QoS flow of the MBS service to the MRBs respectively, the MRBs correspond to a PDCP entity, the PDCP entity corresponds to RLC1 and RLC2, RLC1 adopts multicast transmission, and RLC2 adopts unicast transmission. The network equipment sends MRB data packets on PDCP/RLC1 entities corresponding to MRBs in a multicast mode; and the network equipment receives the RLC status report sent by the terminal through the RLC2 entity.

Optionally, the RLC status report may include RLC Sequence Number (SN) information of MRB RLC PDUs successfully received and/or unsuccessfully received by the terminal.

Optionally, the step of sending the first feedback information to the network device through the layer 2 entity of unicast transmission may further include:

and sending the PDCP status report of the multicast broadcast data packet to the network equipment through the PDCP entity of the unicast transmission.

Specifically, the terminal feeds back the PDCP status report of the multicast broadcast packet through the unicast uplink PDCP entity, that is, the terminal uses the unicast PDCP entity, and sends the condition that the terminal receives the multicast broadcast packet to the network device in the uplink direction, that is, the terminal uses the unicast PDCP entity, and sends the PDCP status report of the downlink PDCP entity corresponding to the multicast broadcast packet to the network device.

Optionally, before the terminal sends the PDCP status report of the multicast broadcast packet to the network device through the unicast PDCP entity, the network device configures, for the terminal, a unicast uplink transmission PDCP entity corresponding to the multicast broadcast packet sending PDCP entity, so as to send the PDCP status report of the multicast broadcast packet.

For example: the network equipment maps the QoS flow of the MBS service to the MRB and the DRB respectively, and the MRB and the DRB respectively correspond to a set of PDCP entity and RLC entity. The network equipment sends MRB data packets on a PDCP/RLC entity corresponding to the MRB in a multicast mode; and the network equipment receives the PDCP status report sent by the terminal through the RLC/PDCP entity of the DRB.

For another example: the network equipment maps the QoS flow of the MBS service to the MRBs respectively, the MRBs correspond to a PDCP entity, the PDCP entity corresponds to RLC1 and RLC2, RLC1 adopts multicast transmission, and RLC2 adopts unicast transmission. The network equipment sends MRB data packets on PDCP/RLC1 entities corresponding to MRBs in a multicast mode; and the network equipment receives the PDCP status report sent by the terminal through the RLC2/PDCP entity.

Optionally, the PDCP status report may include PDCP SN information of MRB PDCP PDUs that the terminal successfully received and/or did not successfully receive.

Optionally, the method may further include: and sending second feedback information to the network equipment through the layer 2 entity of unicast transmission, wherein the second feedback information is used for indicating the receiving condition of a downlink unicast data packet corresponding to the layer 2 entity of unicast transmission by the terminal, and the first feedback information carries a type identifier which is used for indicating that the first feedback information is the feedback information of the receiving condition of the multicast broadcast data packet by the terminal.

For example: when the layer 2 entity of the unicast transmission sends, to the network device, first feedback information for indicating a receiving condition of the multicast broadcast packet by the terminal, the layer 2 entity of the unicast transmission is further configured to send, to the network device, second feedback information for indicating a receiving condition of a downlink unicast packet corresponding to the layer 2 entity of the unicast transmission by the terminal, where in this case, an identifier may be added to the first feedback information to indicate that the first feedback information is feedback information for indicating a receiving condition of the multicast broadcast packet by the terminal.

Optionally, in a case that the first feedback information includes an RLC status report of a multicast broadcast data packet, the RLC status report carries a status report type identifier to indicate that the RLC status report is an RLC status report of a corresponding multicast broadcast data packet.

Optionally, a Control protocol data unit Type (CPT) field in the RLC status report is set to a first preset value, where the first preset value is used to indicate that the RLC status report is an RLC status report of a multicast broadcast packet.

Specifically, the terminal (or called as a receiving end) needs to feed back the RLC status report of the multicast channel through the unicast channel, that is, the RLC status report fed back by the terminal is not the RLC status report of the peer entity on the network equipment side, but is the status report of another RLC entity (e.g., the RLC entity for multicast transmission). Therefore, new design is required to distinguish the RLC status report of the peer RLC entity of the network device (or called sending end).

The specific design is as follows:

using RLC control PDU for feedback, the multiplexing RLC status report format is as shown in fig. 6a and 6b, and the RLC status report formats with SN length of 12 bits (bit) and 18 bits in fig. 6a and 6b respectively; in the CPT field, a specific value (e.g. 001) is used to indicate that the current RLC control PDU is an RLC status report for the multicast channel, not an RLC status report of the peer RLC entity of the transmitting end.

Optionally, when the first feedback information includes a PDCP status report of a multicast broadcast packet, the PDCP status report of the multicast broadcast packet carries a status report type identifier, so as to indicate that the PDCP status report is a PDCP status report of a corresponding multicast broadcast packet.

Optionally, a protocol data unit Type (PDU Type) field in the PDCP status report is set to a second preset value, where the second preset value is used to indicate that the PDCP status report is a PDCP status report of a multicast broadcast packet.

Specifically, the terminal (or called as a receiving end) feeds back the PDCP status report of the multicast channel through the unicast channel, that is, the PDCP layer and the RLC layer corresponding to the unicast channel of the terminal feed back the PDCP status report of the peer PDCP entity on the network device side. Therefore, a new design is needed to distinguish the PDCP status report of the peer PDCP entity of the network device (or called the sending end).

The specific design is as follows:

using the PDCP control PDU for feedback, multiplexing the PDCP status report in the format as shown in fig. 7, using a specific value (e.g., 011) in the PDU Type field to indicate that the current PDCP control PDU is the PDCP status report for the MRB PDCP entity, not the PDCP status report of the peer PDCP entity at the transmitting end.

Optionally, after the step of sending the first feedback information to the network device by the layer 2 entity in unicast transmission, the method may further specifically include:

In this embodiment, after the terminal feeds back the reception condition of the multicast broadcast data packet to the network device through the layer 2 entity of unicast transmission, the network device may resend the retransmission data packet of the multicast broadcast data packet that is unsuccessfully received and fed back by the terminal to the terminal, so as to ensure the transmission reliability of the MBS service.

Optionally, the step of receiving the first data packet transmitted by the network device may specifically include:

receiving the first data packet transmitted by the network equipment through a layer 2 entity of multicast transmission; or, receiving the first data packet transmitted by the network device through a layer 2 entity of unicast transmission.

Optionally, when receiving the first data packet transmitted by the network device through the layer 2 entity of unicast transmission, if the network device further transmits a unicast data packet through the layer 2 entity of unicast transmission, the first data packet may carry identification information, where the identification information is used to indicate that the first data packet is a retransmission data packet of an unsuccessfully received multicast broadcast data packet retransmitted by the network device.

The above embodiments describe the MBS transmission method of the present invention, and the following embodiments further describe the corresponding terminals with reference to the accompanying drawings.

Specifically, as shown in fig. 8, an embodiment of the present invention further provides a terminal 800, including:

a first sending module 810, configured to send, by a layer 2 entity in unicast transmission, first feedback information to a network device, where the first feedback information is used to indicate a reception situation of a terminal on a multicast broadcast packet.

Optionally, the terminal 800 further includes:

a second sending module, configured to send second feedback information to the network device through the layer 2 entity in unicast transmission, where the second feedback information is used to indicate, to the terminal, a reception condition of a downlink unicast data packet corresponding to the layer 2 entity in unicast transmission, and the first feedback information carries a type identifier.

Optionally, the first sending module 810 comprises:

a first sending unit, configured to send an RLC status report of a multicast broadcast packet to a network device through an RLC entity controlled by a unicast radio link;

alternatively, the first and second electrodes may be,

and a second sending unit, configured to send a PDCP status report of the multicast broadcast packet to the network device through a packet data convergence protocol PDCP entity in unicast transmission.

alternatively, the first and second electrodes may be,

Optionally, the terminal 800 further includes:

a receiving module, configured to receive a first data packet transmitted by a network device after layer 2 entity of unicast transmission sends first feedback information to the network device, where the first data packet is a retransmission data packet of a multicast broadcast data packet that is indicated by the first feedback information and is not successfully received.

Optionally, the receiving module includes:

a first receiving unit, configured to receive the first data packet transmitted by the network device through a layer 2 entity in multicast transmission;

alternatively, the first and second electrodes may be,

a second receiving unit, configured to receive the first data packet transmitted by the network device through a layer 2 entity in unicast transmission.

The terminal embodiment of the invention is corresponding to the method embodiment, all implementation means in the method embodiment are applicable to the terminal embodiment, and the same technical effect can be achieved.

In the embodiment, the terminal 800 feeds back the receiving condition of the multicast broadcast data packet to the network device through the layer 2 entity of unicast transmission, so as to solve the problem that the transmission reliability of the MBS service cannot be guaranteed because the terminal cannot effectively feed back and the network device is required to retransmit when the network device transmits the multicast broadcast data packet to the terminal at present.

As shown in fig. 9, this embodiment further provides a terminal, including: a processor 91; and a memory 93 connected to the processor 91 through a bus interface 92, the memory 93 storing programs and data used by the processor 91 in performing operations, and a transceiver 94 connected to the bus interface 92 for receiving and transmitting data under the control of the processor 91. When the processor 91 calls and executes the programs and data stored in the memory 93, the following processes are performed.

Optionally, the processor 91 executes the program to implement the following steps:

alternatively, the first and second electrodes may be,

It should be noted that in fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 91 and various circuits of memory represented by memory 93 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 94 may be a number of elements including a transmitter and a transceiver providing a means for communicating with various other apparatus over a transmission medium. For different terminals, the user interface 95 may also be an interface capable of interfacing with a desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 91 is responsible for managing the bus architecture and general processing, and the memory 93 may store data used by the processor 41 in performing operations.

The above terminal embodiment of the present invention is corresponding to the above method embodiment, and all implementation means in the above method embodiment are applicable to the terminal embodiment, and can achieve the same technical effect, and are not described herein again.

Those skilled in the art will appreciate that all or part of the steps for implementing the above embodiments may be performed by hardware, or may be instructed to be performed by associated hardware by a computer program that includes instructions for performing some or all of the steps of the above methods; and the computer program may be stored in a readable storage medium, which may be any form of storage medium.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the MBS transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

The MBS transmission method according to the embodiment of the present invention is introduced from the terminal side, and the MBS transmission at the network device side will be further described with reference to the drawings.

As shown in fig. 10, an embodiment of the present invention provides a method for transmitting a multicast broadcast service MBS, which specifically includes the following steps:

step 101: and receiving first feedback information sent by a terminal through a layer 2 entity of unicast transmission, wherein the first feedback information is used for indicating the receiving condition of the terminal on the multicast broadcast data packet.

Optionally, the receiving condition of the multicast broadcast packet may include a receiving condition of a multicast broadcast packet transmitted to the terminal by the network device in a multicast manner, and may also include a multicast broadcast packet transmitted to the terminal by the network device in a unicast manner.

In the embodiment, the network device can receive the multicast broadcast data packet from the terminal through the layer 2 entity receiving terminal of unicast transmission, thereby solving the problem that the transmission reliability of the MBS service cannot be guaranteed because the terminal cannot effectively feed back and the network device is required to retransmit when the multicast broadcast data packet is transmitted to the terminal by the network device at present.

Alternatively, the network device may refer to a base station or a node having a function of a base station in an IAB or Relay system.

Optionally, the step of receiving the first feedback information sent by the terminal through the layer 2 entity in unicast transmission may specifically include:

and receiving the RLC status report of the multicast broadcast data packet sent by the terminal through the RLC entity of the unicast transmission.

Specifically, the network device may receive an RLC status report of a multicast broadcast packet fed back by the terminal through the unicast uplink RLC entity, that is, the terminal uses the unicast RLC entity, and sends a situation that the terminal receives the multicast broadcast packet to the network device in the uplink direction, that is, the terminal uses the unicast RLC entity, and sends an RLC status report of a downlink RLC entity corresponding to the multicast broadcast packet to the network device.

Optionally, before receiving the RLC status report of the multicast broadcast packet sent by the terminal through the unicast-transmitted RLC entity, the network device configures, for the terminal, a unicast uplink RLC entity corresponding to the downlink-transmitting RLC entity of the multicast broadcast packet, and is configured to send the RLC status report of the multicast broadcast packet.

For example: the network equipment maps the QoS flow of the MBS service to the MRB and the DRB respectively, and the MRB and the DRB respectively correspond to a set of PDCP entity and RLC entity. The network equipment sends MRB data packets on a PDCP/RLC entity corresponding to the MRB in a multicast mode; and the network equipment receives the RLC status report sent by the terminal through the RLC entity of the DRB.

Optionally, the RLC status report may include RLC SN information of MRB RLC PDUs successfully received and/or unsuccessfully received by the terminal.

and receiving the PDCP state report of the multicast broadcast data packet sent by the PDCP entity of unicast transmission by the terminal.

Specifically, the receiving terminal sends the situation that the terminal receives the multicast broadcast data packet to the network device through the PDCP status report of the multicast broadcast data packet fed back by the unicast uplink PDCP entity, that is, the terminal uses the unicast PDCP entity, and in the uplink direction, the receiving terminal sends the PDCP status report of the downlink PDCP entity corresponding to the multicast broadcast data packet to the network device by using the unicast PDCP entity.

Optionally, before receiving the PDCP status report of the multicast broadcast packet sent by the terminal through the PDCP entity for unicast transmission, the network device configures, for the terminal, a unicast uplink transmission PDCP entity corresponding to the PDCP entity for sending the multicast broadcast packet, so as to send the PDCP status report of the multicast broadcast packet.

Optionally, the method may further include:

and receiving second feedback information sent by the terminal through the layer 2 entity of unicast transmission, wherein the second feedback information is used for indicating the receiving condition of a downlink unicast data packet corresponding to the layer 2 entity of unicast transmission by the terminal, and the first feedback information carries a type identifier.

For example: when receiving first feedback information, which is sent by a terminal through the layer 2 entity of unicast transmission and used for indicating the receiving condition of the terminal for the multicast broadcast data packet, the layer 2 entity of unicast transmission is also used for receiving second feedback information, which is sent by the terminal and used for indicating the receiving condition of the terminal for the downlink unicast data packet corresponding to the layer 2 entity of unicast transmission, in this case, an identifier may be added to the first feedback information to indicate that the first feedback information is feedback information for indicating the receiving condition of the terminal for the multicast broadcast data packet.

Optionally, the CPT field in the RLC status report is set to a first preset value, where the first preset value is used to indicate that the RLC status report is an RLC status report of a multicast broadcast packet.

Optionally, the PDU type field in the PDCP status report is set to a second preset value, where the second preset value is used to indicate that the PDCP status report is a PDCP status report of a multicast broadcast packet.

Optionally, after the step of receiving the first feedback information sent by the terminal through the layer 2 entity in unicast transmission, the method may further include:

In this embodiment, after receiving the receiving condition of the multicast broadcast data packet fed back by the terminal through the layer 2 entity of unicast transmission, the network device may resend the unsuccessfully received multicast broadcast data packet fed back by the terminal to the terminal, so as to ensure the transmission reliability of the MBS service.

Optionally, the step of transmitting the first data packet to the terminal may specifically include:

transmitting the first data packet to the terminal through a layer 2 entity of multicast transmission; or transmitting the first data packet to the terminal through a layer 2 entity of unicast transmission.

optionally, in a case that multicast transmission and unicast transmission correspond to different PDCP entities, the transmitting, by a layer 2 entity of unicast transmission, the first data packet to the terminal includes:

The following describes the interaction process between the network device and the terminal in the MBS transmission method with reference to specific embodiments:

the first embodiment is as follows:

taking the network equipment as a sending end and the terminal as a receiving end as an example, the terminal transmits a PDCP status report of a multicast channel through a unicast channel; wherein, the multicast and unicast channels for transmitting MBS service correspond to different PDCP entities.

As shown in fig. 11, the network device maps the QoS flow of the MBS service to the MRB and the DRB, where the MRB and the DRB respectively correspond to a set of PDCP entity/RLC entity.

Sending end (network equipment side)

And the network equipment transmits the MRB data packet on the PDCP/RLC entity corresponding to the MRB in a multicast mode.

The network equipment receives a PDCP status report sent by the terminal through a RLC/PDCP entity of the DRB, wherein the PDCP status report comprises PDCP SN information of MRB PDCP PDUs successfully received and/or unsuccessfully received by the terminal.

Optionally, the PDCP entity of the DRB interacts with the PDCP entity of the MRB to determine the MRB PDCP PDUs that the terminal did not successfully receive.

Optionally, the network device may use a multicast mode to resend the MRB PDCP PDUs that the terminal did not successfully receive through the PDCP/RLC of the MRB; or, the network device may re-send the MRB PDCP PDUs that the terminal did not successfully receive through the PDCP/RLC of the DRB in a unicast manner.

Optionally, the network device uses a unicast mode to resend the MRB PDCP PDU that the terminal did not successfully receive through the PDCP/RLC of the DRB, and may:

restoring the MRB PDCP PDU into a PDCP SDU, and converting the PDCP SDU into a DRB PDCP PDU for transmission according to the rule of the DRB PDCP; or directly transmitting the MRB PDCP PDU which is not successfully received by the terminal on the unicast channel, and if the unicast channel is transmitting the DRB PDCP PDU at the same time, adding an identifier in the PDCP PDU, such as: and indicating that the PDCP PDU is an MRB PDCP PDU by using an R bit in the existing PDCP data PDU.

Receiving end (terminal side):

the terminal receives layer 2 configuration of the network equipment for MBS service, determines MRB corresponding to MBS service and corresponding PDCP, RLC entity configuration, and corresponding DRB and corresponding PDCP, RLC entity configuration.

The terminal receives the MRB PDCP PDU transmitted in the multicast mode, determines the unsuccessfully received MRB PDCP PDU (also called gap), and generates an MRB PDCP status report.

Optionally, the PDCP entity of the MRB interacts with the PDCP entity of the DRB to request the DRB PDCP entity to transmit the MRB PDCP status report instead.

The terminal transmits the PDCP status report of the MRB through the PDCP/RLC entity of the DRB.

Optionally, the terminal may receive an MRB PDCP PDU that the terminal did not successfully receive and is retransmitted by the PDCP/RLC entity of the MRB in a multicast manner by the network device; or, the terminal may receive the MRB PDCP PDU that the network device has not successfully received and retransmitted by the PDCP/RLC entity of the DRB in a unicast manner. The specific organization method of the PDCP PDU corresponds to the description of the network device side, and is not described herein again.

Example two:

as shown in fig. 12, the network device serves as a sending end, and the terminal serves as a receiving end, for example, the terminal transmits a PDCP status report of the multicast channel through the unicast channel; wherein, the multicast and unicast channel for transmitting MBS service corresponds to a PDCP entity.

Transmitting end (network device side):

the network equipment maps the QoS flow of the MBS service to the MRBs respectively, the MRBs correspond to a PDCP entity, the PDCP entity corresponds to RLC1 and RLC2, RLC1 adopts multicast transmission, and RLC2 adopts unicast transmission.

The network equipment sends MRB data packets on PDCP/RLC1 entities corresponding to the MRB in a multicast mode.

The network equipment receives a PDCP status report sent by the terminal through the RLC2/PDCP entity, wherein the PDCP status report comprises PDCP SN information of MRB PDCP PDUs successfully received and/or unsuccessfully received by the terminal.

Optionally, the network device may re-send, in a multicast manner, the MRB PDCP PDUs which the terminal did not successfully receive, through the RLC 1; or, the network device may retransmit the MRB PDCP PDUs that the terminal did not successfully receive on the multicast channel through the RLC2 in a unicast manner.

Receiving end (terminal side):

the terminal receiving network side determines the configuration of the PDCP entity, the RLC1 of multicast transmission and the RLC2 entity of unicast transmission corresponding to the MBS service for the layer 2 configuration of the MBS service.

The terminal transmits a PDCP status report of the MRB through the RLC2 entity of the unicast transmission.

Optionally, the terminal may receive the MRB PDCP PDUs which are retransmitted by the network device in a multicast manner and unsuccessfully received by the terminal through the RLC 1; or, the terminal may receive the MRB PDCP PDUs which are retransmitted by the network device in a unicast manner and unsuccessfully received by the terminal through the RLC 2.

Example three:

as shown in fig. 13, the network device serves as a sending end, and the terminal serves as a receiving end, for example, the terminal transmits an RLC status report of a multicast channel through a unicast channel; wherein, the multicast and unicast channels for transmitting MBS service correspond to different PDCP entities.

Transmitting end (network device side):

the network equipment maps the QoS flow of the MBS service to the MRB and the DRB respectively, and the MRB and the DRB respectively correspond to a set of PDCP entity/RLC entity.

The network equipment receives an RLC status report sent by the terminal through an RLC entity of the DRB, wherein the RLC status report comprises RLC SN information of MRB RLC PDUs successfully received and/or unsuccessfully received by the terminal.

Optionally, the RLC entity of the DRB interacts with the RLC entity of the MRB to determine the MRB RLC PDU that the terminal did not successfully receive.

Optionally, the network device may use a multicast mode to resend, through the RLC of the MRB, the MRB RLC PDU that the terminal did not successfully receive; or, the network device may retransmit the MRB RLC PDU that the terminal did not successfully receive, through the RLC of the DRB in a unicast manner.

Optionally, the network device uses a unicast mode, and resending, through the RLC of the DRB, the MRB RLC PDU that the terminal did not successfully receive may be:

the network device directly transmits MRB RLC PDUs which are not successfully received by the terminal on the unicast channel, and if the unicast channel is transmitting DRB RLC PDUs at the same time, an identifier needs to be added to the RLC PDUs, for example: and using the R bit or adding a bit in the RLC PDU to indicate that the RLC PDU is the MRB RLC PDU.

Receiving end (terminal side):

the terminal receiving network side determines the MRB corresponding to the MBS service and the corresponding PDCP and RLC entity configuration, and the corresponding DRB and the corresponding PDCP and RLC entity configuration for the layer 2 configuration of the MBS service.

The terminal receives the MRB PDCP PDU transmitted by the multicast mode, determines the unsuccessfully received MRB RLC PDU (also called gap), and generates an MRB RLC status report.

Optionally, the RLC entity of the MRB interacts with the RLC entity of the DRB, requesting the DRB RLC entity to instead transmit the MRB RLC status report.

The terminal transmits an RLC status report of the MRB through the RLC of the DRB.

Optionally, the terminal may receive an MRB RLC PDU that is retransmitted by the network device through the RLC of the MRB and that is not successfully received by the terminal in a multicast manner; or, the terminal may receive the MRB RLC PDU that is retransmitted by the network device through the RLC of the DRB and that is not successfully received by the terminal in a unicast manner.

Example four:

as shown in fig. 14, a network device is taken as a sending end, and a terminal is taken as a receiving end as an example, and the terminal transmits an RLC status report of a multicast channel through a unicast channel; wherein, the multicast and unicast channel for transmitting MBS service corresponds to a PDCP entity.

Transmitting end (network device side):

The network equipment receives an RLC status report sent by the terminal through an RLC2 entity, wherein the RLC status report comprises RLC SN information of MRB RLC PDUs successfully received and/or unsuccessfully received by the terminal.

Optionally, the RLC2 entity interacts with the RLC1 entity to determine the MRB RLC PDUs which the terminal did not successfully receive.

Optionally, the network device may use a multicast mode to resend the MRB RLC PDU that the terminal did not successfully receive through the RLC 1; or, the network device may retransmit, in a unicast manner, the MRB RLC PDU that the terminal did not successfully receive on the multicast channel through the RLC 2; or, the network device side deduces unsuccessfully received RLC SDUs, i.e. PDCP PDUs, from the unsuccessfully received RLC PDUs through RLC1 or RLC2, and notifies the PDCP layer of retransmitting the unsuccessfully received PDCP PDUs. Specifically, the network device may retransmit the unsuccessfully received PDCP PDUs through the RLC1 in a multicast manner, or retransmit the unsuccessfully received PDCP PDUs through the RLC2 in a unicast manner.

Receiving end (terminal side):

The terminal receives the MRB RLC PDUs transmitted in a multicast mode on the RLC1, determines the unsuccessfully received MRB RLC PDUs (also called gap), and generates an RLC status report of the RLC1 entity.

Optionally, the RLC1 entity interacts with the RLC2 entity, requesting the RLC2 entity to instead transmit an RLC status report.

The terminal transmits an RLC status report through the RLC 2.

Optionally, the terminal may receive an MRB RLC PDU which is retransmitted by the network device in a multicast manner and unsuccessfully received by the terminal through the RLC 1; or, the terminal may receive the MRB RLC PDU that is retransmitted by the network device in a unicast manner and unsuccessfully received by the terminal through the RLC 2; or, the terminal may receive the MRB PDCP PDUs which are retransmitted by the network device through the RLC1 and unsuccessfully received by the terminal in a multicast manner, or the MRB PDCP PDUs which are retransmitted by the network device through the RLC2 and unsuccessfully received by the terminal in a unicast manner.

The above embodiments describe the MBS transmission method of the present invention, and the following embodiments further describe corresponding network devices with reference to the accompanying drawings.

As shown in fig. 15, an embodiment of the present invention further provides a network device 1500, including:

a receiving module 1510, configured to receive first feedback information sent by a terminal through a layer 2 entity in unicast transmission, where the first feedback information is used to indicate a receiving situation of a multicast broadcast packet by the terminal.

Optionally, the network device 1500 further includes:

a sending module, configured to, after receiving first feedback information sent by a terminal through a layer 2 entity in unicast transmission, transmit a first data packet to the terminal according to the first feedback information, where the first data packet is a retransmission data packet of a multicast broadcast data packet that is indicated by the first feedback information and that is not successfully received by the terminal.

Optionally, the sending module includes:

a first sending unit, configured to transmit the first data packet to the terminal through a layer 2 entity of multicast transmission;

alternatively, the first and second electrodes may be,

a second sending unit, configured to transmit the first data packet to the terminal through a layer 2 entity in unicast transmission.

Optionally, in a case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, the sending module further includes:

a third sending unit, configured to determine, if the receiving terminal controls an RLC status report of a multicast broadcast packet sent by an RLC entity through a radio link transmitted by unicast, an unsuccessfully received PDCP PDU according to an unsuccessfully received RLC protocol data unit PDU indicated by the RLC status report, and transmit the PDCP PDU to the terminal through a layer 2 entity of unicast or multicast;

optionally, in a case that the multicast transmission and the unicast transmission correspond to different PDCP entities, the second sending unit is specifically configured to:

The embodiment of the network device of the invention is corresponding to the embodiment of the method, all the implementation means in the embodiment of the method are suitable for the embodiment of the network device, and the same technical effect can be achieved.

In the network device 1500 in this embodiment, the receiving terminal uses the layer 2 entity of unicast transmission to feed back the receiving condition of the multicast broadcast data packet to the network device, which solves the problem that when the network device transmits the multicast broadcast data packet to the terminal at present, the terminal cannot perform effective feedback and the network device is required to perform retransmission, which results in that the transmission reliability of the MBS service cannot be guaranteed.

In order to better achieve the above object, as shown in fig. 16, a fourth embodiment of the present invention further provides a network device, including: a processor 1600; a memory 1620 coupled to the processor 1600 via a bus interface, and a transceiver 1610 coupled to the processor 1600 via a bus interface; the memory 1620 is used for storing programs and data used by the processor in performing operations; transmitting data information or pilot through the transceiver 1610, and receiving an uplink control channel through the transceiver 1610; when the processor 1600 calls and executes the programs and data stored in the memory 1620, the following functions are implemented.

Optionally, the processor 1600, when executing the program, implements the following steps:

alternatively, the first and second electrodes may be,

Optionally, in a case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, when the processor 1600 executes the program, the following steps are implemented:

alternatively, the first and second electrodes may be,

in the case that the multicast transmission and the unicast transmission correspond to different PDCP entities, the processor 1600 when executing the program implements the following steps:

A transceiver 1610 for receiving and transmitting data under the control of the processor 1600.

In fig. 16, among other things, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by the processor 1600 and various circuits of the memory represented by the memory 1620 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1610 can be a plurality of elements including a transmitter and a transceiver providing a means for communicating with various other apparatus over a transmission medium. The processor 1600 is responsible for managing the bus architecture and general processing, and the memory 1620 may store data used by the processor 1600 in performing operations.

The embodiment of the network device of the present invention corresponds to the embodiment of the method, and all implementation means in the embodiment of the method are applicable to the embodiment of the network device, and can achieve the same technical effect, which is not described herein again.

Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for transmitting multicast broadcast service MBS is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 1, wherein the sending the first feedback information to the network device via the layer 2 entity of the unicast transmission comprises:

alternatively, the first and second electrodes may be,

4. The method of claim 3,

a control protocol data unit (CPT) field in the RLC status report is set to be a first preset value, and the first preset value is used for indicating that the RLC status report is an RLC status report of a multicast broadcast data packet;

alternatively, the first and second electrodes may be,

5. The method of claim 1, wherein after the layer 2 entity transmitting the first feedback information to the network device via unicast transmission, the method further comprises:

6. The method of claim 5, wherein receiving the first packet transmitted by the network device comprises:

alternatively, the first and second electrodes may be,

7. A terminal, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the processor when executing the program performs the steps of:

8. The terminal of claim 7, wherein the processor, when executing the program, performs the steps of:

9. The terminal of claim 7, wherein the processor, when executing the program, performs the steps of:

alternatively, the first and second electrodes may be,

10. The terminal of claim 9,

alternatively, the first and second electrodes may be,

11. The terminal of claim 7, wherein the processor, when executing the program, performs the steps of:

12. The terminal of claim 11, wherein the processor, when executing the program, performs the steps of:

alternatively, the first and second electrodes may be,

13. A terminal, comprising:

14. A method for transmitting multicast broadcast service MBS is characterized by comprising the following steps:

15. The method of claim 14, wherein after receiving the first feedback information sent by the terminal through the layer 2 entity of the unicast transmission, the method further comprises:

16. The method of claim 15, wherein transmitting the first packet to the terminal comprises:

alternatively, the first and second electrodes may be,

17. The method of claim 16, wherein when the first data packet is transmitted to the terminal through a layer 2 entity for unicast transmission, and when a second data packet for unicast transmission is also transmitted to the terminal through the layer 2 entity for unicast transmission, the first data packet carries identification information, and the identification information is used to indicate that the first data packet is a retransmission data packet of a multicast broadcast data packet.

18. The method of claim 16, wherein in the case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, the transmitting the first packet to the terminal comprises:

alternatively, the first and second electrodes may be,

19. A network device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the processor when executing the program performs the steps of:

20. The network device of claim 19, wherein the processor when executing the program performs the steps of:

21. The network device of claim 20, wherein the processor when executing the program performs the steps of:

alternatively, the first and second electrodes may be,

22. The network device according to claim 21, wherein when the first data packet is transmitted to the terminal through a layer 2 entity for unicast transmission, and when a second data packet for unicast transmission is also transmitted to the terminal through the layer 2 entity for unicast transmission, the first data packet carries identification information, where the identification information is used to indicate that the first data packet is a retransmission data packet of a multicast broadcast data packet.

23. The network device of claim 21, wherein in the case that the multicast transmission and the unicast transmission correspond to one packet data convergence protocol PDCP entity, the processor when executing the program performs the following steps:

alternatively, the first and second electrodes may be,

24. A network device, comprising:

25. A readable storage medium, on which a program is stored, which when executed by a processor performs the steps of the multicast broadcast service MBS transmission method according to any of claims 1 to 6 and 14 to 18.