Transmission method, device, equipment and readable storage medium

Abstract

An embodiment of the present application provides a transmission method, apparatus, device and readable storage medium, the method comprising: the MAC layer of the transmitting end sends MBMS data through a scheduling function and / or a multiplexing function; if the MAC layer of the transmitting end receives a NACK sent by the MAC layer of the receiving end, the MAC layer of the transmitting end retransmits the MBMS data to the HARQ function of the MAC layer of the receiving end through a HARQ function.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and specifically to a transmission method, apparatus, device, and readable storage medium. Background Art

[0002] Based on the Multimedia Broadcast Multicast Service (MBMS) solution defined in the fourth generation mobile communication technology (4G) standard, the technical trend of the MBMS solution is currently being discussed in the fifth generation mobile communication technology (5G) standard. Among them, how to define the MBMS data feedback and retransmission process is an urgent problem to be solved. Summary of the invention

[0003] The embodiments of the present application provide a transmission method, apparatus, device and readable storage medium to solve the problem of how to perform MBMS data feedback and retransmission.

[0004] In a first aspect, a transmission method is provided, comprising:

[0005] The MAC layer of the transmitting end sends MBMS data through a scheduling function and / or a multiplexing function;

[0006] If the MAC layer of the transmitting end receives the NACK sent by the MAC layer of the receiving end, the MAC layer of the transmitting end retransmits the MBMS data to the HARQ function of the MAC layer of the receiving end through the HARQ function.

[0007] Optionally, after the MAC layer of the transmitting end sends the MBMS data through a scheduling function and / or a multiplexing function, the method further includes:

[0008] The MAC layer of the transmitting end receives the ACK sent by the MAC layer of the receiving end through the HARQ function.

[0009] Optionally, after the MAC layer of the transmitting end sends the MBMS data through a scheduling function and / or a multiplexing function, the method further includes:

[0010] The MAC layer of the transmitting end sends the MBMS data to the HARQ function of the MAC layer of the transmitting end.

[0011] Optionally, a scheduling function and / or a multiplexing function of the MAC layer of the transmitting end directly sends the MBMS data to a HARQ function of the MAC layer of the transmitting end;

[0012] or,

[0013] The scheduling function and / or multiplexing function of the MAC layer of the transmitting end caches the MBMS data, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache.

[0014] Optionally, the HARQ function of the MAC layer of the transmitting end reads the MBMS data from a cache, including:

[0015] The HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer periodically according to the PTM transmission mode;

[0016] or,

[0017] The HARQ function of the MAC layer of the transmitting end receives the notification message, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer according to the notification message.

[0018] Optionally, the PTM transmission mode is configured through RRC signaling when establishing or reconfiguring HARQ.

[0019] Optionally, the cache is provided with a discard timer, and if the timer times out, the cache will be cleared;

[0020] or,

[0021] Each HARQ function of the MAC layer of the transmitting end can only access the corresponding cache;

[0022] or,

[0023] Multiple HARQ functions of the MAC layer of the transmitting end can access the same buffer.

[0024] Optionally, the method further comprises:

[0025] The SDAP layer of the transmitting end maps the MBMS data to be sent to different lower layers for sending, and the lower layers include one or more of the following: PDCP layer, RLC layer and MAC layer.

[0026] Optionally, the method further comprises:

[0027] The SDAP layer of the sending end establishes or reconfigures the QoS Flow carrying the MBMS data to be sent;

[0028] The SDAP layer of the sending end selects the DRB of the lower layer;

[0029] The SDAP layer of the sending end maps the QoS Flow carrying the MBMS data to be sent to the DRB.

[0030] Optionally, the QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB.

[0031] Optionally, the multiple QoS Flows carrying the MBMS data to be sent are mapped to one of the DRBs.

[0032] Optionally, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0033] Optionally, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0034] Optionally, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0035] or,

[0036] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0037] or,

[0038] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0039] Optionally, the PDCP layer of the transmitting end directly sends the MBMS data to a lower layer of the PDCP layer.

[0040] Optionally, the RLC layer of the transmitting end sends MBMS data in a non-confirmation mode.

[0041] In a second aspect, a transmission method is provided, including:

[0042] The MAC layer of the transmitting end receives the MBMS data through a scheduling function and / or a multiplexing function;

[0043] If the MBMS data is received in error, the MAC layer of the transmitting end sends a NACK through a HARQ function;

[0044] The MAC layer of the transmitting end receives the MBMS data retransmitted by the MAC layer of the transmitting end through the HARQ function through the HARQ function.

[0045] Optionally, the method further comprises:

[0046] If the MBMS data is received correctly, the MAC layer of the transmitting end sends ACK through the HARQ function.

[0047] Optionally, the method further comprises:

[0048] The SDAP layer of the receiving end establishes or reconfigures the QoS Flow that carries the MBMS data;

[0049] The SDAP layer of the receiving end selects a DRB of a lower layer, wherein the lower layer includes one or more of the following: a PDCP layer, an RLC layer, and a MAC layer;

[0050] The SDAP layer of the receiving end maps the QoS Flow carrying the MBMS data to the DRB.

[0051] Optionally, the QoS Flow carrying MBMS data is mapped one-to-one with the DRB.

[0052] Optionally, the multiple QoS Flows carrying MBMS data are mapped to one DRB.

[0053] Optionally, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0054] Optionally, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0055] Optionally, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0056] or,

[0057] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0058] or,

[0059] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0060] In a third aspect, a transmission device is provided, comprising:

[0061] A sending module, used for the MAC layer of the sending end to send MBMS data through a scheduling function and / or a multiplexing function;

[0062] The retransmission module is used for retransmitting the MBMS data to the HARQ function of the MAC layer of the receiving end through the HARQ function if the MAC layer of the transmitting end receives the NACK sent by the MAC layer of the receiving end.

[0063] In a fourth aspect, a transmission device is provided, comprising:

[0064] A receiving module, used for the MAC layer of the transmitting end to receive MBMS data through a scheduling function and / or a multiplexing function;

[0065] A sending module, configured to cause the MAC layer of the sending end to send a NACK through a HARQ function if the MBMS data is received incorrectly;

[0066] The receiving module is also used for the MAC layer of the transmitting end to receive the MBMS data retransmitted by the MAC layer of the transmitting end through the HARQ function through the HARQ function.

[0067] In a fifth aspect, a communication device is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect or the second aspect.

[0068] In a sixth aspect, a readable storage medium is provided, on which a program is stored. When the program is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0069] In an embodiment of the present application, by defining the HARQ function of the MAC layer (such as the Adjoint HARQ function) and the SDAP function, it is possible to implement feedback and retransmission through the Adjoint HARQ at the MAC layer without performing ARQ feedback processing at the RLC layer, thereby reducing the RRC signaling overhead, avoiding the overhead of establishing a new RLC function body on the network side and the terminal side and the added system complexity, and realizing fast, efficient and retransmission guaranteed MBMS data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0071] Figure 1 is a schematic diagram of a multicast / broadcast architecture with RLC split bearer;

[0072] Figure 2is a schematic diagram of logical channel aggregation mode 1 (UM PTM+AM PTP);

[0073] Figure 3 is a schematic diagram of logical channel aggregation mode 2 (AM PTM+AM PTP);

[0074] Figure 4 It is one of the schematic diagrams of the downlink layer 2 structure;

[0075] Figure 5 This is the second schematic diagram of the downlink layer 2 structure;

[0076] Figure 6 is a schematic diagram of a model of two unconfirmed mode peer entities;

[0077] Figure 7 A schematic diagram of a wireless communication system applicable to the embodiment of the present application

[0078] Figure 8 It is one of the schematic diagrams of the transmission method provided in the embodiment of the present application;

[0079] Fig. 9 This is the second schematic diagram of the transmission method provided in the embodiment of the present application;

[0080] Fig.10 It is a functional diagram of the overall MBMS solution provided by the embodiment of the present application;

[0081] Fig.11 is a schematic diagram of a SDAP data PDU format without an SDAP header provided in an embodiment of the present application;

[0082] Fig.12 This is one of the schematic diagrams of the DL SDAP PDU format carrying MBMS data provided by the embodiment of the present application;

[0083] Fig.13 This is the second schematic diagram of the DL SDAP PDU format carrying MBMS data provided by the embodiment of the present application;

[0084] Fig.14 It is one of the schematic diagrams of the transmission device provided in the embodiment of the present application;

[0085] Fig.15 This is the second schematic diagram of the transmission device provided in the embodiment of the present application;

[0086] Fig.16 is a schematic diagram of a terminal provided in an embodiment of the present application;

[0087] Fig.17 It is a schematic diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0088] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0089] The term "comprise" and any variation thereof in the specification and claims of the present application are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, such as A and / or B, means that A alone, B alone, and A and B exist in three cases.

[0090] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0091] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. However, the following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0092] In order to facilitate understanding of the embodiments of the present application, the following technical points are first introduced below:

[0093] The Multimedia Broadcast Multicast Service (MBMS) service includes multicast mode and broadcast mode. The multicast mode requires users to sign up for the corresponding multicast group, activate the service, and generate corresponding billing information. In the data transmission phase of the broadcast mode service and the multicast mode service, the MBMS service has two modes for transmitting information between the network and the terminal: point to multipoint (PTM) mode and point to point (PTP) mode.

[0094] The so-called PTP mode refers to establishing a point-to-point bearer for each terminal (such as User Equipment (UE)) in the cell, such as establishing an end-to-end transmission channel for UE transmitting MBMS data;

[0095] The so-called PTM mode means that a common transmission channel is established in the cell to provide services for all UEs.

[0096] In the related technologies, multicast / broadcast technology enhancement solutions are studied, and the focus issues mainly include the flexible conversion between PTP and PTM.

[0097] Regarding the enhancement of multicast / broadcast technology, the current conference discussion mainly focuses on the separation of Radio Link Control (RLC), such as Figure 1 As shown, the sending end Packet Data Convergence Protocol (PDCP) is used as an anchor point, and the RLC bearer separation executes the PTP and PTM processes respectively; through logical channel aggregation, the UE only needs one RLC receiving entity.

[0098] At the same time, regarding the aggregation of logical channels, there are currently two possible implementation methods discussed:

[0099] (1) Unacknowledged Mode (UM) PTM + Acknowledged Mode (AM) PTP, Figure 2 shown.

[0100] PTM only supports UM mode, that is, when multicast data is transmitted for the first time, PTM or PTP can be flexibly selected. UE feeds back RLC status report through UL dedicated traffic channel (Dedicated Traffic Channel, DTCH). AM RLC control data is retransmitted through multicast.

[0101] (2)AM PTM+AM PTP, Figure 3 Shown

[0102] Both PTM and PTP support AM mode. Specifically, the RLC status report fed back by the UE through the UL DTCH is shared between the two RLC entities, and the network can flexibly choose to perform unicast retransmission through the DTCH or perform multicast retransmission through the multicast traffic channel (MTCH).

[0103] In the relevant protocols of 5G, the Multimedia Broadcast Multicast Service (MBMS) is not defined. The defined Service Data Adaptation Protocol (SDAP) has the following functions: The main services and functions of SDAP include:

[0104] - Mapping between Quality of Service (QoS) flows and data radio bearers;

[0105] - Marking of QoS Flow ID (QFI) in DL and UL packets.

[0106] If MBMS is reintroduced in the fifth generation of mobile communication technology (5G), the SDAP function needs to be redefined. Figure 4 .

[0107] In the relevant protocols of the fourth generation mobile communication technology (4G), MBMS has independent scheduling and resource allocation methods, and does not have Hybrid Automatic Repeat reQuest (HARQ), that is, there is no air interface feedback, see Figure 5 .

[0108] Among the related protocols, only UM RLC supports MBMS's Multicast Traffic Channel (MTCH) / Multicast Control Channel (MCCH), but the sending window length is 0, which means that no sorting is required and the message is completed as soon as it is sent:

[0109] The receiving UM RLC entity uses this constant to define the SN of those UM mode transmitted protocol data units (UMD PDUs) that can be received without causing the receive window to be advanced. When a 5-bit SN is configured, UM_Window_Size = 16; when a 10-bit SN is configured, UM_Window_Size = 512; when a receiving UM RLC entity is configured for MCCH, MTCH or STCH, UM_Window_Size = 0, see Figure 6 .

[0110] In the relevant protocols, the reception of MBMS is defined:

[0111] MCH transmissions may occur in subframes configured by upper layers for MCCH or MTCH transmissions. For each such subframe, upper layers indicate whether signaling MCS or data MCS is applicable. Transmission of the MCH occurs in a set of subframes defined by the Physical Multicast Channel Configuration (PMCH-Config). The MCH Scheduling Information MAC Control element is included in the first subframe allocated to the MCH within the MCH scheduling period to indicate the location of each MTCH and the unused subframes on the MCH. If the MCCH is not present, the UE shall assume that the first scheduled MTCH starts immediately after the MCCH or MCH Scheduling Information MAC Control element and that other scheduled MTCHs start immediately after the previous MTCH in the subframe earliest at which the previous MTCH stopped. When the UE needs to receive the MCH, the UE shall:

[0112] -Try to decode TB on MCH;

[0113] - If the TB on the MCH is decoded successfully:

[0114] - Demultiplexes MAC PDU and passes MAC SDU to upper layer.

[0115] Combined with the forms of MBMS that have been defined in the current standards, they can be summarized into two types:

[0116] 1. In 4G, MBMS is directly broadcasted by the base station - through the RLC UM mode of 0 window, using the radio resource mode configured by the Radio Resource Control (RRC) for scheduling and sending. In addition, the Medium Access Control (MAC) layer does not have HARQ, and does not require air interface reception feedback.

[0117] 2. In 5G, the current plan is to introduce PTM transmission in the RLC layer and implement MBMS reception feedback through PTP feedback.

[0118] Based on the technical trends of the MBMS solutions already defined in the 4G standard and the MBMS solutions being discussed in the 5G standard, the MBMS defined in the 5G standard will have feedback and retransmission capabilities. Figure 2 and Figure 3 As shown in FIG. 1 , the introduction of the ARQ (Automatic Repeat-reQuest) function in the RLC layer complicates the processing mechanism of MBMS. Each RLC entity that carries MBMS transmission needs to be configured with an RLC AM entity for feedback processing. Although in order to reduce the complexity of the UE side implementation, Figure 2and Figure 3 The solution emphasizes that only one RLC AM entity for receiving MBMS data is established on the UE side. However, in essence, it is necessary to establish RLC entities for MBMS transmission on the network side and the terminal side through RRC signaling, establish a functional entity of RLC AM / UM PTM+AM PTP combination on the network side, and establish an RLC AM PTP functional entity on the terminal side. At the same time, in order to ensure the effectiveness of ARQ operation, the network side also needs to synchronize the sequence number (SN) of the RLC data packet sent between the RLC AM / UM PTM functional entity and the AM PTP functional entities of different users.

[0119] See also Figure 7 , showing a block diagram of a wireless communication system applicable to the embodiment of the present application. The wireless communication system includes a terminal 71 and a network side device 72. Among them, the terminal 71 can also be called a terminal device or a user terminal (UserEquipment, UE), and the terminal 71 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (Vehicle User Equipment, VUE), a pedestrian terminal (Pedestrian User Equipment, PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 71 is not limited in the embodiment of the present application.

[0120] The network side device 72 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a TRP or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0121] See also Figure 8 , an embodiment of the present application provides a transmission method, and the specific steps include: step 801 and step 802.

[0122] Step 801: The MAC layer of the transmitting end sends MBMS data through a scheduling function and / or a multiplexing function;

[0123] Step 802: If the MAC layer of the transmitting end (for example, through the HARQ function) receives a negative acknowledgment (NACK) sent by the MAC layer of the receiving end (for example, through the HARQ function), the MAC layer of the transmitting end retransmits the MBMS data to the HARQ function of the MAC layer of the receiving end through the HARQ function.

[0124] The HARQ function in this article may also be referred to as a HARQ functional entity, a HARQ-related function or a process.

[0125] The above-mentioned HARQ-related functions include one or more of the following: HARQ process function, HARQ process reception and transmission feedback process function, different HARQ mode functions, different HARQ process mode functions, etc.

[0126] It can be understood that the following description is made by taking the HARQ function as an accompanying HARQ function as an example.

[0127] The accompanying HARQ function is specifically used to complete the PTP type transmission of MBMS service data (corresponding to the MCH channel). Figure 4 MBMS Scheduling and / or Multiplex functions are responsible for PTM type transmission, and HARQ is responsible for corresponding PTP reception and transmission.

[0128] When sending: PTM scheduling (MBMS Scheduling) and / or multiplexing (Multiplex) is broadcasted. For a UE, if its MBMS data is received correctly, it will feedback ACK or nothing through the accompanying HARQ function; if its MBMS data is received incorrectly, it will NACK through the accompanying HARQ, and then retransmit and send through the accompanying HARQ, and the process ends directly. The "end of the process" corresponds to three situations: one is successful transmission after one transmission; the second is unsuccessful, reaching the maximum number of transmissions, until failure and discarding; the third is multiple transmissions but not reaching the maximum number of transmissions, and finally successful transmission.

[0129] When receiving: the UE uses the accompanying HARQ function to receive and receive ACK / NACK feedback.

[0130] The accompanying HARQ function may be a newly added function within an existing HARQ function, including one of the following: a scheduling function, data transmission and feedback function for MBMS is added to the existing HARQ function, and a newly defined HARQ process for MBMS is defined.

[0131] The companion HARQ function can also be a newly added function body parallel to the existing HARQ function. When the user needs to transmit MBMS data, a new companion HARQ function is added (newly established or reconfigured). The companion HARQ function has a scheduling function for MBMS data transmission, a data multiplexing function, a HARQ process, and a corresponding transmission-feedback control function.

[0132] In one embodiment of the present application, after the MAC layer of the transmitting end sends the MBMS data through the scheduling function and / or the multiplexing function, the method further includes:

[0133] The MAC layer of the transmitting end (for example, through the accompanying HARQ function) receives an acknowledgment (ACK) sent by the MAC layer of the receiving end (for example, through the accompanying HARQ function).

[0134] In one embodiment of the present application, after the MAC layer of the transmitting end sends the MBMS data through the scheduling function and / or the multiplexing function, the method further includes:

[0135] The MAC layer of the transmitting end sends the MBMS data to an accompanying HARQ function of the MAC layer of the transmitting end.

[0136] In one embodiment of the present application, the scheduling function and / or multiplexing function of the MAC layer of the transmitting end does not buffer the MBMS data, and directly sends the MBMS data to the accompanying HARQ function of the MAC layer of the transmitting end;

[0137] or,

[0138] The scheduling function and / or multiplexing function of the MAC layer of the transmitting end caches the MBMS data, and the accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache.

[0139] In one implementation of the present application, the accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache, including:

[0140] The accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer at a timing according to the PTM transmission mode;

[0141] or,

[0142] The HARQ function of the MAC layer of the transmitting end receives the notification message, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer according to the notification message.

[0143] In one implementation of the present application, the transmission mode of the PTM is configured through RRC signaling when establishing or reconfiguring the accompanying HARQ.

[0144] In one embodiment of the present application, the cache is provided with a discard timer, and if the timer times out, the cache will be cleared;

[0145] or,

[0146] Each companion HARQ function of the MAC layer of the transmitting end can only access the corresponding cache;

[0147] or,

[0148] Multiple companion HARQ functions of the MAC layer of the transmitting end can access the same buffer.

[0149] In one embodiment of the present application, the method further includes:

[0150] The SDAP layer of the transmitting end maps the MBMS data to be transmitted to different lower layers for transmission, and the lower layers include one or more of the following: a Packet Data Convergence Protocol (PDCP) layer, an RLC layer, and a MAC layer.

[0151] In one embodiment of the present application, the method further includes:

[0152] The SDAP layer of the sending end establishes or reconfigures the QoS Flow carrying the MBMS data to be sent;

[0153] The SDAP layer of the transmitting end selects a lower layer data radio bearer (DRB);

[0154] The SDAP layer of the sending end maps the QoS Flow carrying the MBMS data to be sent to the DRB.

[0155] In one implementation of the present application, the QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB.

[0156] In one implementation of the present application, the multiple QoS Flows carrying the MBMS data to be sent are mapped to one DRB.

[0157] In one implementation of the present application, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0158] In one embodiment of the present application, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0159] In one implementation of the present application, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0160] or,

[0161] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0162] or,

[0163] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0164] In one implementation of the present application, the PDCP layer of the transmitting end directly sends the MBMS data to a lower layer of the PDCP layer.

[0165] In one implementation of the present application, the RLC layer of the transmitting end transmits MBMS data in a non-acknowledgement mode.

[0166] In the embodiment of the present application, when the MAC layer solves PTM and PTP transmission (sending and receiving), the delay is short and the control overhead is low. For the precise transmission (sending and receiving) of each UE, the transmission (sending and receiving) and feedback are accompanied by HARQ, and the system overhead of transmitting ACK / NACK is the lowest. Only new functions need to be defined at the SDAP layer and the MAC layer, and the system overhead is small. SDAP flexibly selects low-level channels, has no RRC signaling overhead, and can perform broadcast transmission (sending and receiving) on ​​demand.

[0167] See also Fig. 9 , an embodiment of the present application provides a transmission method, and the specific steps include: step 901 and step 902.

[0168] Step 901: The MAC layer of the transmitting end receives MBMS data through a scheduling function and / or a multiplexing function;

[0169] Step 902: If the MBMS data is received incorrectly, the MAC layer of the transmitting end sends a NACK through an accompanying HARQ function;

[0170] Step 903: The MAC layer of the transmitting end receives the MBMS data retransmitted by the MAC layer of the transmitting end through the accompanying HARQ function.

[0171] In one embodiment of the present application, the method further includes:

[0172] If the MBMS data is received correctly, the MAC layer of the transmitting end sends ACK by accompanying the HARQ function.

[0173] In one embodiment of the present application, the method further includes:

[0174] The SDAP layer of the receiving end establishes or reconfigures the QoS Flow that carries the MBMS data;

[0175] The SDAP layer of the receiving end selects a DRB of a lower layer, wherein the lower layer includes one or more of the following: a PDCP layer, an RLC layer, and a MAC layer;

[0176] The SDAP layer of the receiving end maps the QoS Flow carrying the MBMS data to the DRB.

[0177] In one implementation of the present application, the QoS Flow carrying MBMS data is mapped one-to-one with the DRB.

[0178] In one implementation of the present application, the multiple QoS Flows carrying MBMS data are mapped to one DRB.

[0179] In one implementation of the present application, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0180] In one embodiment of the present application, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0181] In one implementation of the present application, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0182] or,

[0183] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0184] or,

[0185] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0186] In the embodiment of the present application, when the MAC layer solves PTM and PTP transmission (sending and receiving), the delay is short and the control overhead is low. For the precise transmission (sending and receiving) of each UE, the transmission (sending and receiving) and feedback are accompanied by HARQ, and the system overhead of transmitting ACK / NACK is the lowest. Only new functions need to be defined at the SDAP layer and the MAC layer, and the system overhead is small. SDAP flexibly selects low-level channels, has no RRC signaling overhead, and can perform broadcast transmission (sending and receiving) on ​​demand.

[0187] See also Fig.10 , add the function definition for MBMS transmission in L2 (layer 2). The functions of "Qos flow", "PDU Distribution for Adjoint HARQ", and "Adjoint HARQ" are new functions. The functions of "Segm.", "MBMS Scheduling", and "Multiplexing" are newly added to the 5G system and are borrowed from the 4G system (the innovation may be problematic).

[0188] 1. About SDAP layer

[0189] MBMS data can be sent on different PDCP-RLC-MAC low-layer channels through SDAP layer mapping, such as Fig.10As shown. Different PDCP-RLC-MAC low-layer channels can be channels of the same or different cells. On the network side, it can be on the same base station or on different base stations; it can be on the same CU / DU of the same base station or on different CU / DUs, or on the same CU but different DUs. On the terminal side, data received from the PDCP-RLC-MAC low-layer channels of different or the same cells is delivered to the SDAP layer.

[0190] Because the L2 function supporting MBMS service is not defined in the 5G system, the transmission of MBMS service data is realized by defining new functions of SDAP and MAC layers.

[0191] For QoS Flows carrying MBMS service data points:

[0192] 1. Receive RRC signaling configuration and establish / reconfigure / delete QoS Flow that carries MBMS data.

[0193] 2. Select the low-level DRB bearer. Select the low-level DRB bearer based on the RRC signaling configuration, self-monitoring, or system operation requirements.

[0194] 3. Map the QoS flow carrying MBMS data to the DRB. (Mapping between a QoS flow and a data radio bearer)

[0195] 3.1. The QoS Flow carrying MBMS data is mapped one-to-one with the DRB. The reflective mapping function is not supported. At the same time, multiple QoS Flows are not supported to be mapped to one DRB at the same time. QFI is not carried in the uplink and downlink data packets (not marketing QoS flow ID (QFI) in both DL and UL packets.)

[0196] The SDAP PDU format without SDAP header defined in the current protocol can meet the above data transmission requirements and can also be used Fig.11 The SDAP PDU is sent in the defined PDU format. The SDAP PDU contains only a data field and does not contain any SDAP header.

[0197] 3.2. The QoS Flow carrying MBMS data and DRB are mapped many-to-one. The reflective mapping function is not supported.

[0198] See also Fig.12, indicating the downlink (DL) SDAP PDU format carrying MBMS data.

[0199] in,

[0200] (a) R field (Reserved Field): 1 bit in length, set to 0. The receiving end ignores this field after receiving the PDU.

[0201] (b) QFI Field: The length is less than or equal to 6 bits. The length of QFI is not necessarily 6 bits as defined in the protocol, but can be 4 bits, 2 bits, or even 1 bit. QFI is the ID of the QoS Flow mapped to the same Data Radio Bearer (DRB).

[0202] 3.3. One-to-many mapping between QoS Flow and DRB carrying MBMS data (e.g. Fig.10 As shown, one SDAP functional entity is mapped to different PDCP-RLC-MAC lower layer channels). The reflective mapping function is not supported.

[0203] Can be used Fig.12 Or without SDAP PDU header (such as Fig.11 The SDAP PDU format is sent as shown in FIG.

[0204] Alternatively, the SDAP PDU format carrying the Duplication Resolution Flag (DRF) may also be used, see Fig.13 . To solve the problem of how to identify and discard duplicate MBMS data packets (Packets) in multi-channel reception.

[0205] in,

[0206] (a) R field (Reserved Field): 1 bit in length, set to 0. The receiving end ignores this field after receiving the PDU.

[0207] (b) QFI Field: The length is less than or equal to 6 bits. The length of QFI is not necessarily 6 bits as defined in the protocol. It can be 4 bits, 2 bits, or even 1 bit. QFI is the ID of the QoS Flow mapped to the same DRB (Data Radio Bearer).

[0208] The R and QFI fields are optional fields and may or may not be carried. They are configured through RRC signaling or can be determined by the fields carried in the PDU.

[0209] If you make your own judgment, you need to carry the O field.

[0210] (c) O field: optional field. Indicates whether QFI is carried. For example, 0: QFI is not carried; 1: QFI is carried. Located in the first byte of SDAP PDU. If QFI is present, it is in the same byte as QFI; if QFI is not present, it is in the same byte as DRF.

[0211] (d) Duplication Resolution Flag (DRF) field: used to determine whether the PDU has been received. A common definition is the sequence number (SN) sent by the data packet, with a length of an integer multiple of a whole byte, such as 8 bits, 16 bits, 24 bits (n*8, n is an integer), or 7 bits, 15 bits, 23 bits or other n*8-1 bits (n is an integer). The initial value is 0. Each time a PDU is sent, DRF is increased by 1, and then cyclically added.

[0212] After receiving a PDU, the receiver determines whether the DRF of the PDU has been received. If it has been received, the PDU is discarded, otherwise it is submitted to the upper layer after processing.

[0213] 2. About PDCP layer:

[0214] Transparent transmission of the PDCP protocol function layer means that the MBMS data packet is processed in the PDCP layer and directly delivered to the upper layer of PDCP or sent to the lower layer of PDCP.

[0215] 3. About RLC layer:

[0216] It has segmentation function when sending and reassembly function when receiving.

[0217] The RLC layer uses the unacknowledged mode (UM) to receive and send MBMS data, and does not use the AM (Acknowledged Mode) mode and ARQ process.

[0218] When using RLC UM, you can close both the send and receive windows, set their lengths to 0, or not configure them.

[0219] 4. About MAC layer:

[0220] Two new functions are defined:

[0221] 1. Adjoint HARQ function;

[0222] The accompanying HARQ function is specifically used to complete the PTP type transmission of MBMS service data (corresponding to the MCH channel). Fig.10 MBMS Scheduling and / or Multiplex functions are responsible for PTM type transmission, and HARQ is responsible for corresponding PTP reception and transmission.

[0223] When sending: PTM scheduling (MBMS Scheduling) and / or multiplexing (Multiplex) is broadcasted. For a UE, if its MBMS data is received correctly, it will feedback ACK through the accompanying HARQ or nothing; if its MBMS data is received incorrectly, it will NACK through the accompanying HARQ, and then retransmit and send through the accompanying HARQ until the end of the process. The "end of the process" corresponds to three situations: one is successful transmission after one transmission; the second is unsuccessful, reaching the maximum number of transmissions, until failure and discarding; the third is multiple transmissions but not reaching the maximum number of transmissions, and finally successful transmission.

[0224] When receiving: UE uses the accompanying HARQ to provide reception ACK / NACK feedback.

[0225] 2.MBMS MAC PDU distribution to accompanying HARQ function;

[0226] During transmission: after each PTM scheduling (MBMS Scheduling) and / or multiplexing (Multiplex) body is broadcast and sent, the MAC PDU sent this time is distributed to the accompanying HARQ function body of each UE in a timely manner.

[0227] The distribution method may be that the PTM scheduling (MBMS Scheduling) and / or multiplexing (Multiplex) function body does not cache but directly distributes to the companion HARQ of each UE; or it may be a temporary cache, and each companion HARQ sends a request to the PTM scheduling (MBMS Scheduling) and / or multiplexing (Multiplex) function body if retransmission is required, sets a discard timer (Discard Timer), and clears the cache when it times out. It may also be possible to set a shared cache, and each companion HARQ can access the cache. When the PTM sends a data packet, it sends a notification message to each companion HARQ. After receiving the notification message, the companion HARQ reads the data packet from the shared cache; or the companion HARQ reads the data from the cache regularly according to the transmission mode of the PTM (cycle length, cycle start point, transmission start subframe, etc.). In this case, the transmission mode of the PTM needs to be notified to each companion HARQ. Because the transmission mode of the PTM is configured by RRC signaling, when the companion HARQ is established or reconfigured, the mode of the PTM can be configured by RRC signaling.

[0228] When receiving: only the accompanying HARQ function (PTP function) is required, and the PTM function is not required.

[0229] See also Fig.14 , an embodiment of the present application provides a transmission device, applied to a transmitting end, the device 1400 includes:

[0230] A sending module 1401, configured for the MAC layer of the sending end to send MBMS data through a scheduling function and / or a multiplexing function;

[0231] The retransmission module 1402 is configured to retransmit the MBMS data to the accompanying HARQ function of the MAC layer of the receiving end through the accompanying HARQ function if the MAC layer of the transmitting end receives the NACK sent by the MAC layer of the receiving end.

[0232] In the embodiment of the present application, the device 1400 further includes:

[0233] The receiving module is used for the MAC layer of the transmitting end to receive the ACK sent by the MAC layer of the receiving end through the accompanying HARQ function.

[0234] In the embodiment of the present application, the sending module 1401 is also used for the MAC layer of the sending end to send the MBMS data to the accompanying HARQ function of the MAC layer of the sending end.

[0235] In the embodiment of the present application, the sending module 1401 is also used for the scheduling function and / or multiplexing function of the MAC layer of the sending end to directly send the MBMS data to the accompanying HARQ function of the MAC layer of the sending end;

[0236] or,

[0237] The scheduling function and / or multiplexing function of the MAC layer of the transmitting end caches the MBMS data, and the accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache.

[0238] In the embodiment of the present application, the accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache, including:

[0239] The accompanying HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer at a timing according to the PTM transmission mode;

[0240] or,

[0241] The HARQ function of the MAC layer of the transmitting end receives the notification message, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer according to the notification message.

[0242] In an embodiment of the present application, the transmission mode of the PTM is configured through RRC signaling when establishing or reconfiguring the accompanying HARQ.

[0243] In an embodiment of the present application, the cache is provided with a discard timer, and if the timer times out, the cache will be cleared;

[0244] or,

[0245] Each companion HARQ function of the MAC layer of the transmitting end can only access the corresponding cache;

[0246] or,

[0247] Multiple companion HARQ functions of the MAC layer of the transmitting end can access the same buffer.

[0248] In the embodiment of the present application, the sending module 1401 is also used for the SDAP layer of the sending end to map the MBMS data to be sent to different lower layers for sending, and the lower layers include one or more of the following: PDCP layer, RLC layer and MAC layer.

[0249] In the embodiment of the present application, the device 1400 further includes:

[0250] A mapping module is used for the SDAP layer of the sending end to establish or reconfigure the QoS Flow carrying the MBMS data to be sent; the SDAP layer of the sending end selects the DRB of the lower layer; the SDAP layer of the sending end maps the QoS Flow carrying the MBMS data to be sent to the DRB.

[0251] In the embodiment of the present application, the QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB.

[0252] In the embodiment of the present application, the multiple QoS Flows carrying the MBMS data to be sent are mapped to one DRB.

[0253] In the embodiment of the present application, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0254] In the embodiment of the present application, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0255] In the embodiment of the present application, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0256] or,

[0257] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0258] or,

[0259] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0260] In the embodiment of the present application, the sending module 1401 is also used for the PDCP layer of the sending end to directly send the MBMS data to the lower layer of the PDCP layer.

[0261] In the embodiment of the present application, the sending module 1401 is also used for the RLC layer of the sending end to send MBMS data through a non-confirmation mode.

[0262] See also Fig.15 , the embodiment of the present application further provides a transmission device, the device 1500 comprising:

[0263] Receiving module 1501, used for the MAC layer of the transmitting end to receive MBMS data through scheduling function and / or multiplexing function;

[0264] The sending module 1502 is configured to send a NACK by the MAC layer of the sending end through an accompanying HARQ function if the MBMS data is received incorrectly;

[0265] The receiving module 1501 is further configured to receive, by the MAC layer of the transmitting end, the MBMS data retransmitted by the MAC layer of the transmitting end through the accompanying HARQ function.

[0266] In the embodiment of the present application, the sending module 1502 is further configured to, if the MBMS data is received correctly, cause the MAC layer of the sending end to send an ACK through an accompanying HARQ function.

[0267] In the embodiment of the present application, the device 1500 further includes:

[0268] A mapping module is used for the SDAP layer of the receiving end to establish or reconfigure the QoS Flow carrying MBMS data; the SDAP layer of the receiving end selects a DRB of a lower layer, and the lower layer includes one or more of the following: a PDCP layer, an RLC layer, and a MAC layer; the SDAP layer of the receiving end maps the QoS Flow carrying MBMS data to the DRB.

[0269] In the embodiment of the present application, the QoS Flow carrying MBMS data is mapped one-to-one with the DRB.

[0270] In the embodiment of the present application, the multiple QoS Flows carrying MBMS data are mapped to one DRB.

[0271] In the embodiment of the present application, the downlink SDAP PDU format carrying MBMS data includes: a first field indicating an identifier of a QoS Flow mapped to the same DRB.

[0272] In the embodiment of the present application, the QoS Flow carrying the MBMS data to be sent is mapped to multiple DRBs.

[0273] In the embodiment of the present application, the downlink SDAP PDU format carrying MBMS data includes: a second field indicating an identifier of a QoS Flow mapped to the same DRB;

[0274] or,

[0275] The downlink SDAP PDU format carrying MBMS data does not include an SDAP PDU header;

[0276] or,

[0277] The downlink SDAP PDU format carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

[0278] The device provided in the embodiment of the present application can achieve Fig. 9 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0279] Fig.16 To implement a hardware structure diagram of a terminal in an embodiment of the present application, the terminal 1600 includes but is not limited to: a radio frequency unit 1601, a network module 1602, an audio output unit 1603, an input unit 1604, a sensor 1605, a display unit 1606, a user input unit 1607, an interface unit 1608, a memory 1609, and a processor 1610 and other components.

[0280] Those skilled in the art will appreciate that the terminal 1600 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1610 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.16 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0281] It should be understood that in the embodiment of the present application, the input unit 1604 may include a graphics processor (Graphics Processing Unit, GPU) 16041 and a microphone 16042, and the graphics processor 16041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1606 may include a display panel 16061, and the display panel 16061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1607 includes a touch panel 16071 and other input devices 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include two parts: a touch detection device and a touch controller. Other input devices 16072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0282] In the embodiment of the present application, the radio frequency unit 1601 receives downlink data from the network side device and sends it to the processor 1610 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 1601 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0283] The memory 1609 can be used to store software programs or instructions and various data. The memory 1609 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1609 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0284] The processor 1610 may include one or more processing units; optionally, the processor 810 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1610.

[0285] The terminal provided in the embodiment of the present application can achieve Figure 8 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0286] See also Fig.17 , Fig.17 is a structural diagram of a network side device applied in an embodiment of the present invention, such as Fig.17 As shown, the network side device 1700 includes: a processor 1701, a transceiver 1702, a memory 1703 and a bus interface, wherein:

[0287] In one embodiment of the present invention, the network side device 1700 further includes: a program stored in the memory 903 and executable on the processor 1701, and when the program is executed by the processor 1701, the following is implemented: Fig. 9 Steps of the illustrated embodiment.

[0288] exist Fig.17 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1701 and memory represented by memory 1703. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1702 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0289] The processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1703 can store data used by the processor 1701 when performing operations.

[0290] The network side device provided in the embodiment of the present application can achieve Fig. 9 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0291] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the above Figure 8 or Fig. 9 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0292] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0293] The steps of the method or algorithm described in conjunction with the contents disclosed in this application can be implemented in hardware or by executing software instructions in a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, mobile hard disks, read-only optical disks, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be carried in an ASIC. In addition, the ASIC can be carried in a core network interface device. Of course, the processor and the storage medium can also exist in the core network interface device as discrete components.

[0294] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0295] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation methods of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

[0296] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application may adopt the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0297] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0298] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1A function specified in one or more boxes.

[0299] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0300] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A transmission method, characterized in that: include: The media access control MAC layer of the transmitting end sends the multimedia broadcast multicast service MBMS data through a scheduling function and / or a multiplexing function, wherein the scheduling function and / or the multiplexing function are used for point-to-multipoint PTM type transmission; If the MAC layer of the transmitting end receives a negative acknowledgment NACK sent by the MAC layer of the receiving end, the MAC layer of the transmitting end retransmits the MBMS data to the HARQ function of the MAC layer of the receiving end through a hybrid automatic repeat request HARQ function, where the HARQ function is an accompanying HARQ function, and the accompanying HARQ function is used for point-to-point PTP type transmission of MBMS data; The method further comprises: The service data adaptation protocol SDAP layer of the sending end establishes or reconfigures a quality of service QoS flow Flow that carries the MBMS data to be sent; The SDAP layer of the transmitting end selects a data radio bearer DRB at a lower layer; The SDAP layer of the transmitting end maps one or more QoS Flows carrying the MBMS data to be sent to the DRB; The QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB, or the multiple QoS Flows carrying the MBMS data to be sent are mapped with one DRB, or the one QoS Flow carrying the MBMS data to be sent is mapped with multiple DRBs.

2. The method according to claim 1, characterized in that After the MAC layer of the transmitting end sends the MBMS data through the scheduling function and / or the multiplexing function, the method further includes: The MAC layer of the transmitting end receives the ACK sent by the MAC layer of the receiving end.

3. The method according to claim 1, characterized in that: After the MAC layer of the transmitting end sends the MBMS data through the scheduling function and / or the multiplexing function, the method further includes: The scheduling function and / or multiplexing function of the MAC layer of the transmitting end sends the MBMS data to the HARQ function of the MAC layer of the transmitting end.

4. The method according to claim 3, characterized in that The scheduling function and / or multiplexing function of the MAC layer of the transmitting end directly sends the MBMS data to the HARQ function of the MAC layer of the transmitting end; or, The scheduling function and / or multiplexing function of the MAC layer of the transmitting end caches the MBMS data, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache.

5. The method according to claim 4, characterized in that The HARQ function of the MAC layer of the transmitting end reads the MBMS data from the cache, including: The HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer periodically according to the point-to-multipoint PTM transmission mode; or, The HARQ function of the MAC layer of the transmitting end receives the notification message, and the HARQ function of the MAC layer of the transmitting end reads the MBMS data from the buffer according to the notification message.

6. The method according to claim 5, characterized in that The PTM transmission mode is configured through radio resource control RRC signaling when establishing or reconfiguring HARQ.

7. The method according to claim 4, characterized in that The cache is provided with a discard timer, and if the timer times out, the cache will be cleared; or, Each HARQ function of the MAC layer of the transmitting end can only access the corresponding cache; or, Multiple HARQ functions of the MAC layer of the transmitting end can access the same buffer.

8. The method according to claim 1, characterized in that The method further comprises: The SDAP layer of the transmitting end maps the MBMS data to be sent to different lower layers for sending, and the lower layers include one or more of the following: PDCP layer, radio link control RLC layer and MAC layer.

9. The method according to claim 1, characterized in that In the case where the QoS Flows carrying the MBMS data to be sent are mapped to one DRB, The format of the downlink SDAP protocol data unit PDU carrying MBMS data includes: a first field indicating the identifier of the QoS Flow mapped to the same DRB.

10. The method according to claim 1, characterized in that In the case where the QoS Flow carrying the MBMS data to be sent is mapped to a plurality of the DRBs, The format of the downlink SDAP PDU carrying MBMS data includes: a second field indicating the identifier of the QoSFlow mapped to the same DRB; or, The downlink SDAP PDU format carrying MBMS data does not include the SDAP PDU header; or, The format of the downlink SDAP PDU carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

11. The method according to claim 1, characterized in that: The PDCP layer of the transmitting end directly sends the MBMS data to the lower layer of the PDCP layer.

12. The method according to claim 1, characterized in that The RLC layer of the transmitting end transmits MBMS data in a non-confirmation mode.

13. A transmission method, characterized in that: include: The MAC layer of the receiving end receives the MBMS data through a scheduling function and / or a multiplexing function, wherein the scheduling function and / or the multiplexing function is used for point-to-multipoint PTM type transmission; If the MBMS data is received in error, the MAC layer of the receiving end sends a NACK through a HARQ function; The MAC layer of the receiving end receives the MBMS data retransmitted by the MAC layer of the transmitting end through the HARQ function through the HARQ function, wherein the HARQ function is an accompanying HARQ function, and the accompanying HARQ function is used for point-to-point PTP type transmission of MBMS data; The method further comprises: The service data adaptation protocol SDAP layer of the receiving end establishes or reconfigures the QoS Flow that carries the MBMS data; The SDAP layer of the receiving end selects a DRB of a lower layer, wherein the lower layer includes one or more of the following: a PDCP layer, an RLC layer, and a MAC layer; The SDAP layer of the receiving end maps one or more QoS Flows carrying MBMS data to the DRB; The QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB, or the multiple QoS Flows carrying the MBMS data to be sent are mapped with one DRB, or the one QoS Flow carrying the MBMS data to be sent is mapped with multiple DRBs.

14. The method according to claim 13, characterized in that The method further comprises: If the MBMS data is received correctly, the MAC layer of the transmitting end sends ACK through the HARQ function.

15. The method according to claim 13, characterized in that In the case where the multiple QoS Flows carrying the MBMS data to be sent are mapped to one DRB, the downlink SDAP PDU format carrying the MBMS data includes: a first field indicating an identifier of the QoS Flow mapped to the same DRB.

16. The method according to claim 13, characterized in that In the case where the QoS Flow carrying the MBMS data to be sent is mapped to a plurality of the DRBs, The format of the downlink SDAP PDU carrying MBMS data includes: a second field indicating the identifier of the QoSFlow mapped to the same DRB; or, The downlink SDAP PDU format carrying MBMS data does not include the SDAP PDU header; or, The format of the downlink SDAP PDU carrying MBMS data includes: a third field for the receiving end to determine whether the downlink SDAP PDU has been received.

17. A transmission device, characterized in that: include: A sending module, used for the MAC layer of the sending end to send MBMS data through a scheduling function and / or a multiplexing function, wherein the scheduling function and / or the multiplexing function is used for point-to-multipoint PTM type transmission; a retransmission module, configured to retransmit the MBMS data to the HARQ function of the MAC layer of the receiving end through a HARQ function if the MAC layer of the transmitting end receives a NACK sent by the MAC layer of the receiving end, wherein the HARQ function is an accompanying HARQ function, and the accompanying HARQ function is used for point-to-point PTP type transmission of MBMS data; The device also includes: A mapping module, used for the service data adaptation protocol SDAP layer of the sending end to establish or reconfigure the quality of service QoS flow Flow carrying the MBMS data to be sent; The SDAP layer of the transmitting end selects a data radio bearer DRB at a lower layer; The SDAP layer of the transmitting end maps one or more QoS Flows carrying the MBMS data to be sent to the DRB; The QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB, or the multiple QoS Flows carrying the MBMS data to be sent are mapped with one DRB, or the one QoS Flow carrying the MBMS data to be sent is mapped with multiple DRBs.

18. A transmission device, characterized in that: include: A receiving module, used for the MAC layer of the receiving end to receive MBMS data through a scheduling function and / or a multiplexing function, wherein the scheduling function and / or the multiplexing function is used for point-to-multipoint PTM type transmission; A sending module, configured to cause the MAC layer of the receiving end to send a NACK through a HARQ function if the MBMS data is received incorrectly; The receiving module is further configured for the MAC layer of the receiving end to receive the MBMS data retransmitted by the MAC layer of the transmitting end through the HARQ function through the HARQ function, wherein the HARQ function is an accompanying HARQ function, and the accompanying HARQ function is used for point-to-point PTP type transmission of MBMS data; The device also includes: A mapping module, used for the service data adaptation protocol SDAP layer of the receiving end to establish or reconfigure the QoS Flow carrying MBMS data; The SDAP layer of the receiving end selects a DRB of a lower layer, wherein the lower layer includes one or more of the following: a PDCP layer, an RLC layer, and a MAC layer; The SDAP layer of the receiving end maps one or more QoS Flows carrying MBMS data to the DRB; The QoS Flow carrying the MBMS data to be sent is mapped one-to-one with the DRB, or the multiple QoS Flows carrying the MBMS data to be sent are mapped with one DRB, or the one QoS Flow carrying the MBMS data to be sent is mapped with multiple DRBs.

19. A communication device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program implements the steps of the method according to any one of claims 1 to 16 when executed by the processor.

20. A readable storage medium, characterized in that: The readable storage medium stores a program, and when the program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

Images