Downlink data receiving method, downlink data sending method, and device
Patent Information
- Authority / Receiving Office
- MY · MY
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-04-07
- Publication Date
- 2026-07-20
AI Technical Summary
In LTE technology, MBS services do not support HARQ transmission, which results in data that has been repeatedly sent unable to be combined and decoded, reducing the decoding success rate and increasing the packet loss rate.
By introducing the Hybrid Automatic Repeat Request (HARQ) process in terminals and network equipment, the HARQ process of the MBS service is acquired and processed to receive and send downlink data, and the combined decoding of the data is achieved.
It improves the decoding success rate and transmission reliability of MBS services, and solves the problem that data cannot be combined and decoded when MBS services are repeatedly sent.
Abstract
Description
Downlink data receiving method, downlink data sending method and device
[0001] Cross-reference to Related Applications
[0002] This application claims priority to Chinese Patent Application No. 202010266874.7, filed on April 7, 2020 in China, the contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD
[0003] Embodiments of the present application relate to the field of communication technology, in particular to a downlink data receiving method, a downlink data sending method and a device. BACKGROUND
[0004] In the existing long term evolution (LTE) technology, the Multicast and Broadcast Service (MBS) service only supports 1-time sending, and therefore does not support Hybrid Automatic Repeat Request (HARQ) transmission, which results in that the data repeatedly sent multiple times cannot be combined and decoded when the MBS service is repeatedly sent, and thus the decoding success rate is reduced and the packet loss rate is increased.
[0005] SUMMARY
[0006] An object of embodiments of the present application is to provide a downlink data receiving method, a downlink data sending method and a device to solve the problem that the MBS service does not support HARQ transmission.
[0007] In a first aspect, embodiments of the present application provide a downlink data receiving method applied to a terminal, comprising:
[0008] obtaining a Hybrid Automatic Repeat Request (HARQ) process of a broadcast multicast service (MBS) service;
[0009] receiving downlink data of the MBS service according to the HARQ process.
[0010] In a second aspect, embodiments of the present application further provide a downlink data sending method applied to a network device, comprising:
[0011] obtaining a HARQ process of a MBS service;
[0012] sending downlink data of the MBS service according to the HARQ process.
[0013] In a third aspect, embodiments of the present application further provide a terminal, comprising:
[0014] a first obtaining module configured to obtain a HARQ process of a MBS service;
[0015] The first receiving module is configured to receive the downlink data of the MBS service according to the HARQ process.
[0016] In a fourth aspect, an embodiment of the present application provides a network device, comprising:
[0017] The second obtaining module is configured to obtain the HARQ process of the MBS service.
[0018] The first sending module is configured to send the downlink data of the MBS service according to the HARQ process.
[0019] In a fifth aspect, an embodiment of the present application provides a communication device, comprising a processor, a memory, and a program stored in the memory and executable in the processor, wherein the program, when executed by the processor, implements the steps of the downlink data receiving method according to the first aspect, or the steps of the downlink data sending method according to the second aspect.
[0020] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the steps of the downlink data receiving method according to the first aspect, or the steps of the downlink data sending method according to the second aspect.
[0021] In the embodiment of the present application, the specific MBS service can be transmitted and retransmitted through the corresponding HARQ process, so that the terminal can combine and decode the data repeatedly transmitted by the network side for multiple times, thereby improving the decoding success rate and improving the transmission reliability of the specific MBS service. BRIEF DESCRIPTION OF DRAWINGS
[0022] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description. The drawings are included only to illustrate preferred embodiments and do not therefore need to be considered limiting of the application. Likewise, like reference numerals refer to like elements throughout the several views. In the drawings:
[0023] FIG. 1 is a schematic diagram of an architecture of a wireless communication system according to an embodiment of the present application;
[0024] FIG. 2 is a flowchart of a downlink data receiving method according to an embodiment of the present application;
[0025] FIG. 3 is a flowchart of a downlink data sending method according to an embodiment of the present application;
[0026] FIG. 4 is a schematic diagram of a terminal according to an embodiment of the present application;
[0027] FIG. 5 is a schematic diagram of a network device according to an embodiment of the present application;
[0028] FIG. 6 is a schematic diagram of a communication device according to an embodiment of the application. DETAILED DESCRIPTION
[0029] In order to facilitate understanding of the embodiments of the application, the following two technical points are introduced as follows:
[0030] (1) Multimedia Broadcast and Multicast Service (MBMS) or Multicast Broadcast Service (MBS) introduction:
[0031] In the LTE system, the MBMS service can be sent in the following two ways:
[0032] MBMS / MBS sending method 1: sent through the physical multicast channel (PMCH) physical channel in the MBMS single frequency network (MBSFN) subframe. Among them, the control information is sent through the system information (such as SIB13) and the broadcast control channel (MCCH), and the data is sent through the broadcast traffic channel (MTCH).
[0033] MBMS / MBS sending method 2: sent through the physical downlink control channel (PDSCH) channel scheduled by the physical downlink control channel (PDCCH). Among them, the control information is sent through the system information (such as SIB20) and the single cell broadcast control channel (SC-MCCH), and the data is sent through the single cell broadcast traffic channel (SC-MTCH). Among them, the SC-MCCH is sent through the PDSCH scheduled by the PDCCH with the single cell radio network temporary identity (SC-RNTI), and the SC-MTCH is sent through the PDSCH scheduled by the PDCCH with the G-RNTI.
[0034] (2) Bandwidth Part (BWP) Introduction:
[0035] For a specific cell, the network side can configure up to four BWPs corresponding to different working frequency information. The network side can indicate the activated BWP through Downlink Control Information (DCI) signaling. For a specific cell, the terminal can only have one activated BWP at the same time.
[0036] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.
[0037] The term "comprising" and any variation thereof in the specification and claims of the present application is intended to cover not exclusively including, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can 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 means at least one of the connected objects, for example, A and / or B, means including single A, single B, and three cases of A and B.
[0038] In the embodiments of the present application, the words such as "exemplary" or "for example" are used to represent as an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words such as "exemplary" or "for example" are intended to present the relevant concept in a specific manner.
[0039] The technology described herein is not applicable to a Long Time Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used for various 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.
[0040] The terms "system" and "network" are frequently used interchangeably. A CDMA system can implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. UTRA includes Wideband-CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system can implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). LTE and LTE-A are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.
[0041] Embodiments of the present application provide a downlink data receiving method, a downlink data sending method and equipment, which can be applied to a wireless communication system. Referring to FIG. 1, a schematic diagram of an architecture of a wireless communication system according to an embodiment of the present application is shown. As shown in FIG. 1, the wireless communication system can include a network equipment 10, a network equipment 11 and a terminal 12, which can be denoted as UE 12. The terminal 12 can communicate (transmit signaling or data) with the network equipment 10 and the network equipment 11. In actual application, the connections between the above-mentioned equipments can be wireless connections. In order to represent the connection relationship between the equipments intuitively, solid lines are used in FIG. 1.
[0042] The network device 10 and the network device 11 provided by the embodiment of the present application can be a base station, which can be a commonly used base station, an evolved node base station (eNB), a network device in a 5G system (for example, a next generation node base station (gNB) or a transmission and reception point (TRP)), or the like.
[0043] The terminal 12 provided by the embodiment of the present application can be a mobile phone, a tablet computer, a notebook computer, an Ultra-Mobile Personal Computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device, or a vehicle-mounted device, or the like.
[0044] Referring to FIG. 2, the embodiment of the present application provides a downlink data receiving method, and the execution subject of the method can be a terminal, which includes the following steps 201 and 202.
[0045] Step 201: Obtain a HARQ process of an MBS service.
[0046] It can be understood that the MBS service refers to a partial MBS service or a specific MBS service, that is, the HARQ process can be used for transmission of the partial or specific MBS service, such as an MBS service corresponding to a specific cell, an MBS service corresponding to a specific transmission node, or an MBS service in a specific frequency range, or the like.
[0047] Step 202: Receive downlink data of the MBS service according to the HARQ process.
[0048] Exemplarily, when the network side retransmits the transmission of the downlink data of the MBS service, the UE combines and decodes the retransmission data of the MBS service and the data of the MBS service received before according to the HARQ process. For example, the G-RNTI-1 PDCCH schedules the initial transmission of HARQ-1, and the C-RNTI PDCCH schedules the retransmission of HARQ-1, and then the UE combines and decodes the data of the initial transmission and the retransmission data.
[0049] In the embodiments of the present application, part or specific MBS services can be received through specific HARQ processes, so that the terminal can combine and decode the data repeatedly sent by the network side multiple times, improve the decoding success rate, and thus improve the transmission reliability of part or specific MBS services.
[0050] In some embodiments, the method further comprises receiving indication information indicating that the terminal sends or does not send HARQ feedback information according to the reception of the downlink data of the MBS service.
[0051] In some embodiments, in step 202, the transmission configuration of the downlink data of the MBS service is obtained; and the downlink data of the MBS service is received according to the HARQ process and the transmission configuration.
[0052] Optionally, the transmission configuration of the downlink data of the MBS service comprises a plurality of transmission positions in one downlink data transmission period of the MBS service.
[0053] For example, each of the plurality of transmission positions corresponds to the transmission of respective new data; or each of the plurality of transmission positions corresponds to the transmission of the same data.
[0054] Optionally, the HARQ transmission version of each transmission position is determined by a protocol or configured by the network side, for example, when each of the plurality of transmission positions corresponds to the transmission of the same data, the HARQ transmission versions of the plurality of transmission positions are the same or different.
[0055] In the embodiments of the present application, the transmission configuration of the downlink data of the MBS service comprises a retransmission mode of the HARQ process of the MBS service or unicast service.
[0056] Optionally, the retransmission mode of the HARQ process comprises any one of the following:
[0057] (1) retransmission through a scheduling transmission mode corresponding to the MBS service or unicast service;
[0058] (2) retransmission through another scheduling transmission mode different from the initial transmission scheduling transmission mode of the MBS service.
[0059] For example, the initial transmission of the MBS service is sent through a "multicast scheduling transmission mode", and the retransmission is sent through a "unicast scheduling transmission mode", both of which use the same HARQ process, but the "scheduling transmission mode" is different.
[0060] Optionally, the scheduling transmission mode corresponding to the MBS or unicast service comprises at least one of the following:
[0061] (1) the MBS service dynamic scheduling transmission mode;
[0062] (2) the unicast service dynamic scheduling transmission mode;
[0063] (3) the MBS service semi-persistent scheduling transmission mode;
[0064] (4) the unicast service semi-persistent scheduling transmission mode.
[0065] Optionally, in the case of the other scheduling transmission mode different from the MBS service initial transmission scheduling transmission mode, the identifier of the retransmission corresponding scheduling transmission mode is indicated by the network side.
[0066] In some embodiments, in step 202, the downlink data of the MBS service is received, including:
[0067] The downlink data of the MBS service is received according to the downlink data receiving rule.
[0068] Optionally, the downlink data receiving rule includes one or more of the following:
[0069] (1) the priority corresponding to the scheduling transmission mode;
[0070] The priority corresponding to the scheduling transmission mode corresponding to the unicast service is higher than the priority corresponding to the scheduling transmission mode corresponding to the multicast service.
[0071] (2) the priority corresponding to the logical channel;
[0072] For example, the logical channel priority of the unicast service is higher than the logical channel priority of the multicast service, and the UE preferentially receives the multicast service; for another example, the logical channel priority of the multicast service-1 is higher than the logical channel priority of the multicast service-2, and the UE preferentially receives the multicast service-1.
[0073] (3) the priority corresponding to the service identifier.
[0074] Optionally, the service identifier includes at least one of the following: the identifier of a specific MBS service and the identifier of a unicast service.
[0075] Optionally, the downlink data receiving rule is configured by the network side, agreed by the protocol, or determined by the terminal.
[0076] For example, the terminal determines the downlink data receiving rule according to the reception interest of the service. Illustratively, the reception interest of the UE for the TMGI-1 service is higher than that for the TMGI-2 service. Or, the reception interest of the UE for the MBS service is higher than that for the unicast service.
[0077] In some embodiments, in step 201, the HARQ process of the MBS service is acquired, including:
[0078] The HARQ configuration information corresponding to the MBS service is acquired, including one or more of the following:
[0079] (1) The number of HARQ processes available to the MBS service;
[0080] Optionally, the configuration mode of the MBS available HARQ process number includes any one of the following: a starting HARQ process number and the number of available HARQ processes; an ending HARQ process number and the number of available HARQ processes; an explicitly indicated HARQ process number; a starting HARQ process number and an ending HARQ process number.
[0081] It can be understood that the HARQ configuration information can be used for part or specific MBS service.
[0082] Optionally, the starting HARQ process number and the ending HARQ process number are configured by the network side or agreed by the protocol.
[0083] (2) The HARQ process number available to the MBS service.
[0084] In some embodiments, the HARQ configuration information of the MBS service includes any one of the following:
[0085] (1) The HARQ configuration information of a specific MBS service;
[0086] It can be understood that the HARQ configuration information of each MBS service can be independent.
[0087] (2) The HARQ configuration information of the MBS service corresponding to a specific cell;
[0088] (3) The HARQ configuration information of the MBS service corresponding to a specific transmission node;
[0089] (4) The HARQ configuration information of the MBS service corresponding to a specific frequency range.
[0090] Optionally, the HARQ configuration information has a corresponding relationship with one or more MBS services, and the corresponding relationship is configured by the network side or agreed by the protocol.
[0091] In some embodiments, the HARQ process pool to which the HARQ process available to the MBS service belongs is the same as the HARQ process pool to which the HARQ process available to the unicast service belongs;
[0092] Further, the HARQ process available for the MBS service cannot be used for initial transmission of the unicast service.
[0093] In some embodiments, the HARQ process pool to which the HARQ process available for the MBS service belongs is different from the HARQ process pool to which the HARQ process available for the unicast service belongs.
[0094] In the embodiments of the present application, the MBS service can be transmitted and retransmitted through a specific HARQ process, thereby improving the transmission reliability of the MBS service.
[0095] Referring to FIG. 3, the embodiments of the present application further provide a method for transmitting downlink data, and the execution subject of the method is a network device, which specifically includes steps 301 and 302.
[0096] Step 301: Obtain a HARQ process of an MBS service.
[0097] It can be understood that the MBS service refers to a part of MBS services or a specific MBS service, that is, the HARQ process can be used for a part of or a specific MBS service.
[0098] Step 302: Transmit downlink data of the MBS service according to the HARQ process.
[0099] Optionally, the transmission configuration of the downlink data of the MBS service is obtained, and the downlink data of the MBS service is transmitted according to the HARQ process and the transmission configuration.
[0100] In some embodiments, the method further includes transmitting indication information indicating whether the terminal transmits or does not transmit the HARQ feedback information according to the reception of the downlink data of the MBS service.
[0101] In the embodiments of the present application, the MBS service can be transmitted and retransmitted through a specific HARQ process, thereby improving the transmission reliability of the MBS service.
[0102] In order to facilitate understanding of the embodiments of the present application, the following examples are introduced.
[0103] Step 1: The network side configures or agrees on the MBS service reception corresponding HARQ configuration information.
[0104] Step 2: According to the HARQ configuration information, the UE receives the downlink data of the corresponding MBS service and transmits the corresponding feedback information.
[0105] Optionally, the "MBS service reception corresponding HARQ configuration information" can indicate the indication information of whether the HARQ feedback needs to be transmitted.
[0106] For example, the network indicates that the UE needs to send HARQ feedback information for the reception of the PDSCH corresponding to the MBS service-1.
[0107] Optionally, the configuration manner of the "HARQ configuration information" includes any one of the following:
[0108] (1) The HARQ configuration information corresponding to the reception of the MBS service corresponding to a specific cell;
[0109] For example, the HARQ configuration information corresponding to the reception of the MBS service corresponding to cell-1.
[0110] (2) The HARQ configuration information corresponding to the reception of the MBS service corresponding to a specific transmission node;
[0111] For example, the HARQ configuration information corresponding to the reception of the MBS service corresponding to transmission node-1.
[0112] (3) The HARQ configuration information corresponding to the reception of the MBS service corresponding to a specific frequency range;
[0113] For example, the HARQ configuration information corresponding to the reception of the MBS service corresponding to BWP-1.
[0114] In addition, for the HARQ configuration information corresponding to the reception of the MBS service corresponding to a specific cell (or a specific transmission node; or a specific frequency range), further, the network side configures or the protocol agrees that one or more MBS services correspond to the HARQ configuration information corresponding to the reception of the MBS service.
[0115] For example, the HARQ configuration information corresponding to the reception of the MBS service corresponding to Temporary Mobile Group Identity (TMGI)-1.
[0116] Wherein, the "identification of the specific cell" includes any combination of one or more of the following:
[0117] (1) Cell group identification;
[0118] For example, Master Cell Group (MCG) or Secondary Cell Group (SCG) identification.
[0119] (2) Cell type identification;
[0120] For example, a Primary Cell (PCell), a Secondary Cell (SCell), a Primary Secondary Cell (PSCell), or a special Cell (SpCell).
[0121] (3) Serving cell identification;
[0122] For example, Serving cell-1.
[0123] (4) SCell identification;
[0124] For example, SCell-1.
[0125] (5) Physical Cell Identifier (PCI) identification;
[0126] For example, PCI-1.
[0127] The "identification of the specific transmission node" includes any combination of one or more of the following:
[0128] (1) Transmission Point (TRP) identification;
[0129] For example, TRP-1.
[0130] (2) Physical Cell Identifier identification;
[0131] For example, PCI-1.
[0132] (3) Reference signal identification;
[0133] For example, Synchronous Signal Block (SSB)-1, and / or Channel State Information-Reference Signal (CSI-RS)-1.
[0134] (4) Port number identification corresponding to the reference signal;
[0135] For example, port_1.
[0136] (5) Resource location identification of the control channel;
[0137] For example, a control resource set (CORESET) identification of a physical downlink control channel (PDCCH), and / or a search space identification.
[0138] (6) a reference signal identification of the control channel;
[0139] For example, a synchronization signal block (SSB) identification, and / or a channel state information-reference signal (CSI-RS) identification.
[0140] (7) a port number identification corresponding to the reference signal of the control channel;
[0141] For example, port_1.
[0142] The “identification of the specific frequency range” includes any combination of one or more of the following:
[0143] (1) a bandwidth part (BWP) identification;
[0144] For example, BWP-1.
[0145] (2) a frequency point;
[0146] For example, an absolute radio frequency channel number (ARFCN)-1.
[0147] (3) a bandwidth;
[0148] For example, 20MHz.
[0149] (4) a frequency start position;
[0150] For example, an absolute radio frequency channel number start position (ARFCN-start).
[0151] (5) a frequency end position;
[0152] For example, an absolute radio frequency channel number end position (ARFCN-end).
[0153] (6) a physical resource block (PRB) identification;
[0154] For example, PRB-1.
[0155] (7) a physical resource block number identification;
[0156] For example, 10 PRBs.
[0157] wherein the "identity of the specific MBS service" comprises one or more of the following in any combination:
[0158] (1) an MBS service information identity;
[0159] For example, TMGI-1.
[0160] (2) an MBS service logical channel identity;
[0161] For example, Multicast Traffic Channel (MTCH)-1.
[0162] (3) an MBS bearer identity;
[0163] For example, Data Radio Bearer (DRB)-1, or MBMS Point to Multipoint Radio Bearer (MRB)-1.
[0164] (4) an MBS data flow identity;
[0165] For example, Quality of Service (QoS) flow-1.
[0166] (5) an MBS session identity;
[0167] For example, PDU Session-1.
[0168] (6) an MBS service area identity;
[0169] For example, Service Area Identity (SAI);
[0170] (7) an MBS service transmission area identity;
[0171] For example, MBSFN-1, a list of cells transmitting the MBS service, an identity of an area in which the MBS service is transmitted (e.g., MBS area 1).
[0172] (8) an MBS service scheduling information identity;
[0173] For example, Group Radio Network Temporary Identifier (G-RNTI)-1, an MBS service TMGI-1 transmitted by a PDSCH scheduled by a PDCCH identified by the G-RNTI-1.
[0174] (9) Data channel identifier of the MBS service;
[0175] For example, for the configuration 1 of the semi-persistent PDSCH, the MBS service TMGI-1 is transmitted by the downlink semi-persistent scheduling (SPS).
[0176] The "HARQ configuration information" includes one or more of the following in any combination:
[0177] (1) The number of HARQ processes available for the MBS;
[0178] For example, 4 HARQ processes.
[0179] (2) The HARQ process number available for the MBS;
[0180] For example, HARQ processes numbered 0-3.
[0181] The relationship between the "HARQ process available for the MBS" and the "HARQ process available for the unicast service" includes any of the following:
[0182] Relationship 1: The "HARQ process available for the MBS" and the "HARQ process available for the unicast service" share the same HARQ process pool.
[0183] For example, the total number of HARQ processes of the UE is "0-15" (a total of 16), the "HARQ process available for the MBS" is "0-7", and the "HARQ process available for the unicast service" is "8-15".
[0184] Additionally, for relationship 1, the network side configures or the protocol agrees that the HARQ process of the MBS cannot be used for the initial transmission of the unicast service. For example, the new data transmission of the unicast service PDSCH scheduled by the cell radio network temporary identifier (C-RNTI) PDCCH cannot use the HARQ process of the MBS.
[0185] Relationship 2: The "HARQ process available for the MBS" and the "HARQ process available for the unicast service" use independent HARQ process pools.
[0186] For example, the MBS service of the UE has 8 HARQ processes (for example, HARQ process numbers "0-7") dedicated to the MBS, and 16 HARQ processes (for example, HARQ process numbers "0-15") dedicated to the unicast service.
[0187] The "unicast service available HARQ process" corresponds to the "unicast service identifier", which includes at least one of the following:
[0188] (1) The scheduling information identifier of the unicast service;
[0189] For example, the cell radio network temporary identity (C-RNTI)-1, that is, the unicast service DRB-1 sent by the PDCCH scheduling PDSCH identified by the C-RNTI-1 of the UE.
[0190] (2) The data channel identifier of the unicast service;
[0191] For example, the configuration 1 of the semi-persistent PDSCH, which sends the unicast service DRB-1 through the downlink SPS.
[0192] (3) The unicast service bearer type identifier;
[0193] For example, DRB-1.
[0194] (4) The unicast service logical channel identifier;
[0195] For example, DTCH-1.
[0196] (5) The unicast bearer identifier;
[0197] For example, DRB-1.
[0198] (6) The unicast data flow identifier;
[0199] For example, QoS flow-1.
[0200] (7) The unicast session identifier;
[0201] For example, PDU Session-1.
[0202] The configuration method of the "MBS available HARQ process number" includes any one of the following:
[0203] (1) The starting HARQ process number and the number of available HARQ processes;
[0204] For example, the total number of HARQ processes is 16, the "starting HARQ process" is 5, and the "number of available HARQ processes" is 5, then the "MBS available HARQ process number" is "5-9".
[0205] (2) The explicitly indicated HARQ process number;
[0206] For example, the available HARQ processes are "0, 2, 4, and 6".
[0207] (3) the start HARQ process number and the end HARQ process number;
[0208] For example, the total number of HARQ processes is 16, the start HARQ process is 5, and the end HARQ process number is 9. The "MBS available HARQ process number" is "5-9", and there are 5 HARQ processes in total.
[0209] The "start HARQ process number" or "end HARQ process number" is configured by the network or agreed by the protocol. For example, the protocol agrees to start from number "0", or the network configures to start from number "5".
[0210] In addition, when the MBS service is sent through a semi-persistent data channel, the HARQ process number corresponds to a specific time position.
[0211] For example, the start HARQ process is 5, the number of available HARQ processes is 5, the system frame number (SFN) of the semi-persistent PDSCH (such as SPS PDSCH) is 1, and the slot number is 1. The HARQ process corresponding to the semi-persistent PDSCH is 5, and the HARQ process corresponding to the next semi-persistent PDSCH is 6.
[0212] In addition, when the MBS service is sent through a semi-persistent data channel, the network side configures or agrees by the protocol that there are multiple sending positions in one data sending period.
[0213] For example, the network side configures the MBS service to be sent through a semi-persistent data channel with a period of 10 milliseconds (ms), and there are 2 sending positions in each period.
[0214] The network side configures or agrees by the protocol that the sending mode of the "multiple sending positions in one data sending period" includes any of the following:
[0215] (1) Each sending position corresponds to the transmission of new data;
[0216] For example, the network side configures the MBS service to be sent through a semi-persistent data channel with a period of 10 ms, and there are 2 sending positions in each period. Sending position 1 uses HARQ process 1 to send new data, and sending position 2 uses HARQ process 2 to send new data.
[0217] (2) Each sending position corresponds to the transmission of the same data (including new transmission and retransmission);
[0218] For example, the network side configures the MBS service to be transmitted through a semi-persistent data channel with a period of 10 ms, and there are 2 transmission positions in each period. Transmission position 1 transmits new data using HARQ process 1, and transmission position 2 transmits retransmission data using HARQ process 1.
[0219] When the multiple transmission positions in one data transmission period use the transmission of the same data for each transmission position, the network side configures or the protocol agrees on the HARQ transmission version of the multiple transmission positions.
[0220] For example, the network side configures the MBS service to be transmitted through a semi-persistent data channel with a period of 10 ms, and there are 2 transmission positions in each period. Transmission position 1 transmits new data using HARQ process 1 with a redundancy version (RV) of 0, and transmission position 2 transmits retransmission data using HARQ process 1 with an RV of 2.
[0221] In addition, the network side configures or the protocol agrees that the retransmission mode of the HARQ process of the specific service includes any of the following:
[0222] (1) Retransmission through a specific service corresponding scheduling transmission mode.
[0223] For example, the initial transmission of HARQ process-1 of the MBS service scheduled by G-RNTI-1 PDCCH is retransmitted through the PDSCH scheduled by G-RNTI-1 PDCCH.
[0224] For example, the initial transmission of HARQ process-1 of the MBS service transmitted through the MBS semi-persistent PDSCH is retransmitted through the PDSCH scheduled by G-RNTI-1 PDCCH or the MBS semi-persistent PDSCH.
[0225] (2) Retransmission through different service scheduling transmission mode.
[0226] For example, the initial transmission of HARQ process-1 of the MBS service scheduled by G-RNTI-1 PDCCH is retransmitted through the PDSCH scheduled by C-RNTI-1 PDCCH.
[0227] For example, the initial transmission of HARQ process-1 of the MBS service transmitted through the MBS semi-persistent PDSCH is retransmitted through the PDSCH scheduled by C-RNTI-1 PDCCH or the MBS semi-persistent PDSCH.
[0228] The "specific service corresponding scheduling transmission mode" includes at least one of the following:
[0229] (1) The transmission of specific MBS service dynamic scheduling;
[0230] For example, the MBS service-1 is transmitted by the PDSCH scheduled by the G-RNTI-1 PDCCH.
[0231] (2) The transmission of specific unicast service dynamic scheduling;
[0232] For example, the unicast service is transmitted by the PDSCH scheduled by the C-RNTI or the Configured Scheduling RNTI (CS-RNTI) PDCCH.
[0233] (3) The transmission of specific MBS service semi-persistent scheduling;
[0234] For example, the MBS service-1 is transmitted by the PDSCH of SPS-1.
[0235] (4) The transmission of specific unicast service semi-persistent scheduling;
[0236] For example, the unicast service is transmitted by the PDSCH of SPS-2.
[0237] In addition, for the retransmission by different service scheduling transmission mode, the network side indicates the service identifier corresponding to the retransmission. The "service identifier" includes any one of the following:
[0238] (1) "The identifier of specific MBS service"
[0239] (2) "The identifier of unicast service".
[0240] The scenario of "indicating the service identifier corresponding to the retransmission" can be configured by the network or agreed by the protocol, that is, the unicast service allows the initial transmission of the unicast service to use the HARQ process of the MBS.
[0241] Optionally, when the network side retransmits the transmission of the downlink data of the MBS, the UE combines and decodes the retransmission data of the MBS service and the data of the MBS service received before according to the retransmission indication information of the network side.
[0242] For example, the G-RNTI-1 PDCCH schedules the initial transmission of HARQ-1, and the C-RNTI PDCCH schedules the retransmission of HARQ-1, and the UE combines and decodes the data of the initial transmission and the retransmission data.
[0243] Additionally, if the UE cannot simultaneously receive the downlink data of the MBS (such as the PDSCH scheduled by the G-RNTI-1 PDCCH) and the downlink data of the unicast (such as the PDSCH scheduled by the C-RNTI PDCCH), or cannot simultaneously receive the downlink data of multiple MBS (such as the PDSCH scheduled by the G-RNTI-1 PDCCH and the PDSCH scheduled by the G-RNTI-2 PDCCH), the UE selects to receive the corresponding downlink data according to the following downlink data receiving rules:
[0244] Rule 1: Receive the downlink data according to the priority order configured by the network or agreed by the protocol;
[0245] Rule 2: Receive the downlink data according to the priority order indicated by the UE;
[0246] Rule 3: Receive the downlink data according to the priority order of the UE's interest in receiving services;
[0247] For example, the UE's interest in receiving the TMGI-1 service is higher than the TMGI-2 service; or the UE's interest in receiving the MBS service is higher than the unicast service.
[0248] For Rule 1, the priority order includes any of the following:
[0249] (1) The unicast service scheduling transmission mode (or the multicast service scheduling transmission mode) is preferred;
[0250] For example, the PDSCH scheduled by the C-RNTI PDCCH is preferred to the PDSCH scheduled by the G-RNTI PDCCH.
[0251] (2) The order of the logical channel priority is used to determine the priority order of reception.
[0252] For example, if the logical channel priority of the unicast is higher than the logical channel priority of the multicast, the UE preferentially receives the multicast; or for example, if the logical channel priority of the multicast service-1 is higher than the logical channel priority of the multicast service-2, the UE preferentially receives the multicast service-1.
[0253] For Rule 2, the "UE indicated priority order" information includes any of the following:
[0254] (1) The unicast service scheduling transmission mode (or the multicast service scheduling transmission mode) is preferred;
[0255] For example, the PDSCH scheduled by the C-RNTI PDCCH is preferred to the PDSCH scheduled by the G-RNTI PDCCH.
[0256] (2) The indicated service identifier corresponds to the priority order;
[0257] For example, the priority of the logical channel 1 is higher than the priority of the logical channel 2; for another example, the priority of the TMGI-1 is higher than the priority of the TMGI-2.
[0258] The service identifier includes at least one of the following:
[0259] (1) an identifier of a specific MBS service;
[0260] (2) an identifier of a unicast service.
[0261] In the embodiments of the present application, the MBS service can be transmitted and retransmitted through a specific HARQ process, thereby improving the transmission reliability of the MBS service.
[0262] Referring to FIG. 4, the embodiments of the present application further provide a terminal 400, which comprises:
[0263] A first obtaining module 401 is configured to obtain a HARQ process of an MBS service.
[0264] A first receiving module 402 is configured to receive downlink data of the MBS service according to the HARQ process.
[0265] In some embodiments, the terminal 400 further comprises a second receiving module configured to receive indication information, wherein the indication information indicates whether the terminal transmits or does not transmit HARQ feedback information according to the reception of the downlink data of the MBS service.
[0266] In some embodiments, the first receiving module 402 is further configured to obtain a transmission configuration of the downlink data of the MBS service; and receive the downlink data of the MBS service according to the HARQ process and the transmission configuration.
[0267] In some embodiments, the transmission configuration of the downlink data of the MBS service comprises:
[0268] The MBS service comprises a plurality of transmission positions in one downlink data transmission period.
[0269] In some embodiments, each of the plurality of transmission positions corresponds to the transmission of respective new data; or each of the plurality of transmission positions corresponds to the transmission of the same data.
[0270] In some embodiments, the HARQ transmission version of each transmission position is determined by a protocol or configured by a network side, such as when each of the plurality of transmission positions corresponds to the transmission of the same data, the HARQ transmission versions of the plurality of transmission positions are the same or different.
[0271] In some embodiments, the sending configuration of the downlink data of the MBS service comprises: a retransmission mode of a HARQ process of the MBS service.
[0272] In some embodiments, the retransmission mode comprises any one of the following:
[0273] (1) retransmission by a scheduling and sending mode corresponding to the MBS service or a unicast service;
[0274] (2) retransmission by another scheduling and sending mode different from the initial transmission scheduling and sending mode of the MBS service.
[0275] In some embodiments, the scheduling and sending mode corresponding to the MBS service comprises at least one of the following:
[0276] (1) dynamic scheduling and sending mode of the MBS service;
[0277] (2) semi-persistent scheduling and sending mode of the MBS service;
[0278] The scheduling and sending mode corresponding to the unicast service comprises at least one of the following:
[0279] (1) dynamic scheduling and sending mode of the unicast service;
[0280] (2) semi-persistent scheduling and sending mode of the unicast service.
[0281] In some embodiments, in the case of the other scheduling and sending mode different from the initial transmission scheduling and sending mode of the MBS service, the identity of the scheduling and sending mode corresponding to the retransmission is indicated by the network side.
[0282] In some embodiments, receiving the downlink data of the MBS service comprises:
[0283] receiving the downlink data of the MBS service according to a downlink data receiving rule.
[0284] In some embodiments, the downlink data receiving rule comprises one or more of the following:
[0285] (1) priority corresponding to a scheduling and sending mode;
[0286] (2) priority corresponding to a logical channel;
[0287] (3) priority corresponding to a service identity.
[0288] In some embodiments, the downlink data receiving rule is configured by the network side, agreed by a protocol, or determined by the terminal.
[0289] In some embodiments, the HARQ process for acquiring the MBS service comprises:
[0290] The HARQ configuration information corresponding to the MBS service acquisition comprises one or more of the following:
[0291] (1) the number of HARQ processes available for the MBS service;
[0292] (2) the HARQ process number available for the MBS service.
[0293] In some embodiments, the configuration of the HARQ process number available for the MBS service comprises any of the following:
[0294] (1) the starting HARQ process number and the number of available HARQ processes;
[0295] (2) the ending HARQ process number and the number of available HARQ processes; explicitly indicated HARQ process number;
[0296] (3) the starting HARQ process number and the ending HARQ process number.
[0297] In some embodiments, the starting HARQ process number and the ending HARQ process number are configured by the network side or agreed by the protocol.
[0298] In some embodiments, the HARQ configuration information of the MBS service comprises any of the following:
[0299] (1) the HARQ configuration information of a specific MBS service;
[0300] (2) the HARQ configuration information of the MBS service corresponding to a specific cell;
[0301] (3) the HARQ configuration information of the MBS service corresponding to a specific transmission node;
[0302] (4) the HARQ configuration information of the MBS service corresponding to a specific frequency range.
[0303] In some embodiments, the HARQ configuration information has a corresponding relationship with one or more MBS services, and the corresponding relationship is configured by the network side or agreed by the protocol.
[0304] In some embodiments, the HARQ process pool to which the HARQ process available for the MBS service belongs is the same as the HARQ process pool to which the HARQ process available for the unicast service belongs.
[0305] Or,
[0306] The HARQ process pool to which the HARQ process available for the MBS service belongs is different from the HARQ process pool to which the HARQ process available for the unicast service belongs.
[0307] In some embodiments, in the case that the HARQ process pool to which the HARQ process available for the MBS service belongs is the same as the HARQ process pool to which the HARQ process available for the unicast service belongs, the HARQ process available for the MBS service cannot be used for the initial transmission of the unicast service.
[0308] The terminal provided by the embodiment of the application can execute the method embodiment shown in FIG. 2, and has similar implementation principles and technical effects, which will not be repeated here.
[0309] Referring to FIG. 5, the embodiment of the application further provides a network device 500, which comprises:
[0310] The second acquisition module 501 is configured to acquire the HARQ process of the MBS service.
[0311] The first sending module 502 is configured to send the downlink data of the MBS service according to the HARQ process.
[0312] In some embodiments, the network device 500 further comprises:
[0313] The second sending module is configured to send the indication information, and the indication information indicates that the terminal sends or does not send the HARQ feedback information according to the reception of the downlink data of the MBS service.
[0314] In some embodiments, the first sending module 501 is further configured to acquire the sending configuration of the downlink data of the MBS service, and send the downlink data of the MBS service according to the HARQ process and the sending configuration.
[0315] The network device provided by the embodiment of the application can execute the method embodiment shown in FIG. 3, and has similar implementation principles and technical effects, which will not be repeated here.
[0316] Referring to FIG. 6, FIG. 6 is a structure diagram of a communication device to which the embodiment of the application is applied, as shown in FIG. 6, the communication device 600 comprises a processor 601, a transceiver 602, a memory 603 and a bus interface, wherein:
[0317] In an embodiment of the application, the communication device 600 further comprises a computer program stored in the memory 603 and executable on the processor 601, and the computer program is executed by the processor 601 to implement the steps in the embodiment shown in FIG. 2 or FIG. 3.
[0318] In Figure 6, the bus architecture can include any number of interconnected buses and bridges, specifically, various circuit links between the processor(s) 601 and the memory represented by the memory 603. The bus architecture can also link various other circuitry such as peripheral devices, voltage stabilizers, and power management circuitry, which are well known in the art, and therefore, are not further described herein. The bus interface provides an interface. The transceiver 602 can be a plurality of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatuses over a transmission medium. It is understood that the transceiver 602 is an optional component.
[0319] The processor 601 is responsible for managing the bus architecture and general processing, and the memory 603 can store data used by the processor 601 in executing operations.
[0320] The communication device provided by the embodiments of the present application can execute the method embodiments shown in Figures 2 or 3, and the implementation principles and technical effects are similar, and thus are not described here again.
[0321] The steps of the methods or algorithms described in connection with the present disclosure can be implemented in hardware, or be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a read-only light disk, or any other form of storage medium well 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 an integral part of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). In addition, the ASIC can be located in the core network interface device. Of course, the processor and the storage medium can also exist as discrete components in the core network interface device.
[0322] Those skilled in the art should understand that, in one or more examples described above, the functions described in the specification of the present application can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. The computer readable medium includes computer storage media and communication media including any medium that facilitates the transfer of computer program from one place to another.
[0323] The above detailed description describes the purpose, technical solutions and beneficial effects of the present application. It should be understood that the above description is only a specific embodiment of the present application and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.
[0324] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the embodiments of the present application can be in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present application can be in the form of a computer program product implemented on one or more computer usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
[0325] The embodiments of the present application are described with reference to flowcharts and / or block diagrams according to the methods, devices (systems) and computer program products of the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general purpose computer, a special purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.
[0326] These computer program instructions can also be stored in a computer readable storage medium which can guide the computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer readable storage medium produce a product including instruction means, which implements the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.
[0327] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable devices to generate a computer-implemented process, so that the instructions executed on the computer or other programmable devices provide steps for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.
[0328] Obviously, various modifications and changes can be made to the embodiments of the present application without departing from the spirit and scope of the present application. Accordingly, it is intended that the present application embrace all such modifications and changes as fall within the scope of the appended claims and their equivalents.
Claims
1. A method for receiving downlink data of a multicast and broadcast service (MBS), applied to a terminal, comprising: obtaining a hybrid automatic repeat request (HARQ) process of the MBS; and receiving downlink data of the MBS according to the HARQ process. 2.The method of claim 1, further comprising: receiving indication information indicating whether the terminal sends or does not send HARQ feedback information according to reception of the downlink data of the MBS. The receiving of the downlink data of the MBS according to the HARQ process comprises: obtaining a transmission configuration of the downlink data of the MBS; and receiving the downlink data of the MBS according to the HARQ process and the transmission configuration. The transmission configuration of the downlink data of the MBS comprises: a plurality of transmission positions in a transmission period of the downlink data of the MBS. Each of the plurality of transmission positions corresponds to transmission of respective new data.
3. The method of claim 1, wherein, Alternatively, each of the plurality of transmission positions corresponds to transmission of the same data. A HARQ transmission version of each transmission position is determined by a protocol or configured by a network side. The transmission configuration of the downlink data of the MBS comprises: a retransmission mode of the HARQ process of the MBS.
4. The method of claim 3, wherein, The retransmission mode comprises any one of: retransmission by a scheduling transmission mode corresponding to the MBS or a unicast service; and retransmission by another scheduling transmission mode different from a scheduling transmission mode of initial transmission of the MBS. The scheduling transmission mode corresponding to the MBS comprises at least one of: a dynamic scheduling transmission mode of the MBS; and a semi-persistent scheduling transmission mode of the MBS.
5. The method of claim 4, wherein, The scheduling transmission mode corresponding to the unicast service comprises at least one of: a dynamic scheduling transmission mode of the unicast service; and a semi-persistent scheduling transmission mode of the unicast service. In the case of the other scheduling transmission mode different from the scheduling transmission mode of the initial transmission of the MBS, an identifier of the scheduling transmission mode corresponding to the retransmission is indicated by the network side. The receiving of the downlink data of the MBS comprises: receiving the downlink data of the MBS according to a downlink data reception rule.
6. The method of claim 5, wherein, The downlink data reception rule comprises one or more of: a priority corresponding to a scheduling transmission mode; a priority corresponding to a logical channel; and a priority corresponding to a service identifier.
7. The method of claim 3, wherein, The downlink data reception rule is configured by the network side, determined by a protocol, or determined by the terminal.
8. The method of claim 7, wherein, The obtaining of the HARQ process of the MBS comprises: obtaining HARQ configuration information corresponding to reception of the MBS, the HARQ configuration information comprising one or more of: a number of available HARQ processes of the MBS; and HARQ process numbers available to the MBS. The configuration mode of the HARQ process numbers available to the MBS comprises any one of: a start HARQ process number and a number of available HARQ processes; an end HARQ process number and a number of available HARQ processes; explicitly indicated HARQ process numbers; a start HARQ process number and an end HARQ process number. 9. The method of claim 8, wherein, 10. The method of claim 8, wherein, 11. The method of claim 1, wherein, 12. The method of claim 11, wherein, 13. The method of claim 11, wherein, 14. The method of claim 1, wherein, 15. The method of claim 14, wherein, 16. The method of claim 14, wherein, The start HARQ process number and the end HARQ process number are configured by a network side or agreed by a protocol.
17. The method of claim 14, wherein, The HARQ configuration information of the MBS service includes any one of the following: HARQ configuration information of a specific MBS service; HARQ configuration information of an MBS service corresponding to a specific cell; HARQ configuration information of an MBS service corresponding to a specific transmission node; HARQ configuration information of an MBS service corresponding to a specific frequency range.
18. The method of claim 14, wherein, The HARQ configuration information has a corresponding relationship with one or more MBS services, and the corresponding relationship is configured by a network side or agreed by a protocol.
19. The method of claim 14, wherein, The HARQ process pool to which the HARQ process available for the MBS service is the same as the HARQ process pool to which the HARQ process available for the unicast service; Or, The HARQ process pool to which the HARQ process available for the MBS service is different from the HARQ process pool to which the HARQ process available for the unicast service.
20. The method of claim 19, wherein, In the case where the HARQ process pool to which the HARQ process available for the MBS service is the same as the HARQ process pool to which the HARQ process available for the unicast service, the HARQ process available for the MBS service cannot be used for initial transmission of the unicast service.
21. A method for sending downlink data, applied to a network device, comprising: obtaining a HARQ process of an MBS service; sending downlink data of the MBS service according to the HARQ process.
22. The method of claim 21, further comprising: sending indication information indicating whether the terminal sends or does not send HARQ feedback information according to reception of the downlink data of the MBS service.
23. The method of claim 21, wherein, The sending downlink data of the MBS service according to the HARQ process comprises: obtaining a sending configuration of the downlink data of the MBS service; sending downlink data of the MBS service according to the HARQ process and the sending configuration.
24. A terminal, comprising: a first obtaining module configured to obtain a HARQ process of an MBS service; a first receiving module configured to receive downlink data of the MBS service according to the HARQ process.
25. The terminal of claim 24, further comprising: a second receiving module configured to receive indication information indicating whether the terminal sends or does not send HARQ feedback information according to reception of the downlink data of the MBS service.
26. The terminal of claim 24, wherein, The first receiving module is further configured to: obtain a sending configuration of the downlink data of the MBS service; receive downlink data of the MBS service according to the HARQ process and the sending configuration.
27. The terminal of claim 26, wherein, The sending configuration of the downlink data of the MBS service comprises: a plurality of sending positions included in one downlink data sending period of the MBS service.
28. The terminal of claim 27, wherein, Each of the plurality of sending positions corresponds to transmission of respective new data; or Each of the plurality of sending positions corresponds to transmission of the same data.
29. The terminal of claim 28, wherein, A HARQ sending version of each sending position is agreed by a protocol or configured by a network side.
30. The terminal of claim 26, wherein, The sending configuration of the downlink data of the MBS service comprises a retransmission mode of the HARQ process of the MBS service.
31. The terminal of claim 30, wherein, The retransmission mode includes any one of the following: retransmitting through a scheduling and sending mode corresponding to the MBS service or the unicast service; retransmitting through another scheduling and sending mode different from the initial transmission scheduling and sending mode of the MBS service.
32. The terminal of claim 31, wherein, The scheduling and sending mode corresponding to the MBS service includes at least one of the following: The dynamic scheduling and sending mode of the MBS service; The semi-persistent scheduling and sending mode of the MBS service; The scheduling and sending mode corresponding to the unicast service includes at least one of the following: The dynamic scheduling and sending mode of the unicast service; The semi-persistent scheduling and sending mode of the unicast service.
33. The terminal of claim 31, wherein, In the case of the other scheduling and sending mode different from the initial transmission scheduling and sending mode of the MBS service, the identifier of the scheduling and sending mode corresponding to the retransmission is indicated by the network side.
34. The terminal of claim 24, wherein, Receiving downlink data of the MBS service includes: Receiving downlink data of the MBS service according to the downlink data receiving rule.
35. The terminal of claim 34, wherein, The downlink data receiving rule includes one or more of the following: The priority corresponding to the scheduling and sending mode; The priority corresponding to the logical channel; The priority corresponding to the service identifier.
36. The terminal of claim 34, wherein, The downlink data receiving rule is configured by the network side, agreed by the protocol, or determined by the terminal.
37. The terminal of claim 24, wherein, The HARQ process of the MBS service includes: Obtaining HARQ configuration information corresponding to the reception of the MBS service, the HARQ configuration information including one or more of the following: The number of available HARQ processes of the MBS service; The HARQ process number available to the MBS service.
38. The terminal of claim 37, wherein, The configuration mode of the MBS available HARQ process number includes any one of the following: Starting HARQ process number and available HARQ process number; End HARQ process number and available HARQ process number; explicitly indicated HARQ process number; Starting HARQ process number and end HARQ process number.
39. The terminal of claim 37, wherein, The starting HARQ process number and the end HARQ process number are configured by the network side or agreed by the protocol.
40. The terminal of claim 37, wherein, The HARQ configuration information of the MBS service includes any one of the following: The HARQ configuration information of a specific MBS service; The HARQ configuration information of the MBS service corresponding to a specific cell; The HARQ configuration information of the MBS service corresponding to a specific transmission node; The HARQ configuration information of the MBS service corresponding to a specific frequency range.
41. The terminal of claim 37, wherein, The HARQ configuration information has a corresponding relationship with one or more MBS services, and the corresponding relationship is configured by the network side or agreed by the protocol.
42. The terminal of claim 37, wherein, The HARQ process pool to which the HARQ process available to the MBS service belongs is the same as the HARQ process pool to which the HARQ process available to the unicast service belongs; Or, The HARQ process pool to which the HARQ process available to the MBS service belongs is different from the HARQ process pool to which the HARQ process available to the unicast service belongs.
43. The terminal of claim 42, wherein, In the case that the HARQ process pool to which the HARQ process available to the MBS service belongs is the same as the HARQ process pool to which the HARQ process available to the unicast service belongs, the HARQ process available to the MBS service cannot be used for the initial transmission of the unicast service.
44. A network device, comprising: a second obtaining module, configured to obtain a HARQ process of the MBS service; a first sending module, configured to send downlink data of the MBS service according to the HARQ process.
45. The network device of claim 44, further comprising: a second sending module, configured to send indication information, the indication information indicating whether the terminal sends or does not send HARQ feedback information according to downlink data reception of the MBS service.
46. The network device of claim 44, wherein, The first sending module is further configured to: obtain a sending configuration of the downlink data of the MBS service; and send the downlink data of the MBS service according to the HARQ process and the sending configuration.
47. A communication device comprising: a processor, a memory, and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the downlink data reception method according to any one of claims 1 to 20; or the steps of the downlink data sending method according to any one of claims 21 to 23.
48. A computer-readable storage medium, having stored thereon a computer program, the computer program, when executed by a processor, implementing the steps of the downlink data reception method according to any one of claims 1 to 20; or the steps of the downlink data sending method according to any one of claims 21 to 23.