A method and apparatus for transmitting an MBS service, a terminal device, and a network device

Abstract

The embodiment of the application provides a kind of MBS service transmission method and device, terminal equipment, network equipment, which comprises: terminal equipment receives the first MBS service data that network equipment sends according to multicast mode;The terminal equipment sends the first negative acknowledgement NACK information to the network equipment, and the first NACK information is used to indicate that the terminal equipment receives the first MBS service data error;The terminal equipment receives the retransmission data of the first MBS service data that the network equipment sends according to unicast mode.

Description

[0001] This application is a divisional application of PCT International Patent Application No. PCT / CN2020 / 106387, filed on July 31, 2020, entitled "MBS Service Transmission Method and Device, Terminal Device, and Network Device", which entered the Chinese national phase as Chinese Patent Application No. 202080101107.9. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of mobile communication technology, and in particular to a multimedia multicast service (MBS) service transmission method and device, terminal device, and network device. BACKGROUND

[0003] In a new radio (NR) system, higher requirements are proposed for the reliability of MBS services, and the terminal device needs to feed back the reception of the MBS service. However, the current feedback mechanism has the following problems: if there are multiple users receiving one MBS service data, only one user receives an error, and multicast retransmission of the MBS service data is redundant and power-consuming for other users. Therefore, how to perform efficient retransmission is a problem to be solved. SUMMARY

[0004] Embodiments of the present application provide a MBS service transmission method and device, terminal device, and network device.

[0005] The MBS service transmission method provided by the embodiments of the present application comprises:

[0006] The terminal device receives first MBS service data sent by the network device in a multicast manner.

[0007] The terminal device sends first negative acknowledgement (NACK) information to the network device, and the first NACK information is used to indicate that the terminal device receives the first MBS service data incorrectly.

[0008] The terminal device receives retransmission data of the first MBS service data sent by the network device in a unicast manner.

[0009] The MBS service transmission method provided by the embodiments of the present application comprises:

[0010] The terminal device receives first MBS service data sent by the network device in a multicast manner and the first MBS service data sent by the network device in a unicast manner.

[0011] The MBS service transmission method provided by the embodiments of the present application comprises:

[0012] The network device sends the first MBS service data via multicast.

[0013] The network device receives a first NACK message sent by the terminal device, the first NACK message being used to indicate that the terminal device has encountered an error in receiving the first MBS service data.

[0014] The network device sends the retransmission data of the first MBS service data to the terminal device in a unicast manner.

[0015] The MBS service transmission device provided in this application embodiment is applied to a terminal device, and the device includes:

[0016] The receiving unit is used to receive the first MBS service data sent by the network device in a multicast manner.

[0017] The sending unit is configured to send a first NACK message to the network device, wherein the first NACK message is used to indicate that the terminal device has encountered an error in receiving the first MBS service data;

[0018] The receiving unit is further configured to receive retransmission data of the first MBS service data sent by the network device in a unicast manner.

[0019] The MBS service transmission device provided in this application embodiment is applied to a terminal device, and the device includes:

[0020] The receiving unit is used to receive the first MBS service data sent by the network device in a multicast manner and the first MBS service data sent in a unicast manner.

[0021] The MBS service transmission device provided in this application embodiment is applied to a network device, and the device includes:

[0022] The transmitting unit is used to transmit the first MBS service data in a multicast manner.

[0023] The receiving unit is configured to receive a first NACK message sent by the terminal device, wherein the first NACK message is used to indicate that the terminal device has encountered an error in receiving the first MBS service data.

[0024] The sending unit is further configured to send retransmission data of the first MBS service data to the terminal device in a unicast manner.

[0025] The terminal device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the MBS service transmission method described above.

[0026] The network device provided in this application includes a processor and a memory. The memory stores computer programs, and the processor calls and runs the computer programs stored in the memory to execute the MBS service transmission method described above.

[0027] The chip provided in this application embodiment is used to implement the MBS service transmission method described above.

[0028] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the MBS service transmission method described above.

[0029] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the MBS service transmission method described above.

[0030] The computer program product provided in this application includes computer program instructions that cause a computer to execute the MBS service transmission method described above.

[0031] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the MBS service transmission method described above.

[0032] In the technical solution of this application embodiment, after the network device receives the first NACK information sent by a terminal device, it can confirm that the terminal device has made a mistake in receiving the first MBS service data. The network device then retransmits the first MBS service data to the terminal device via unicast, thereby avoiding redundant reception of the first MBS service data by other terminal devices and achieving the purpose of energy saving and efficient feedback. Attached Figure Description

[0033] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0034] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application;

[0035] Figure 2 This is a schematic diagram illustrating the transmission of MBS services according to multicast and unicast methods provided in the embodiments of this application;

[0036] Figure 3 This is a flowchart illustrating the MBS service transmission method provided in the embodiments of this application. Figure 1 ;

[0037] Figure 4 This is a flowchart illustrating the MBS service transmission method provided in the embodiments of this application.Figure 2 ;

[0038] Figure 5 This is a flowchart illustrating the MBS service transmission method provided in the embodiments of this application. Figure 3 ;

[0039] Figure 6 This is a schematic diagram of the simultaneous delivery of MBS service data in multicast and unicast modes provided in the embodiments of this application. Figure 1 ;

[0040] Figure 7 This is a schematic diagram of the simultaneous delivery of MBS service data in multicast and unicast modes provided in the embodiments of this application. Figure 2 ;

[0041] Figure 8 This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 1 ;

[0042] Figure 9 This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 2 ;

[0043] Figure 10 This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 3 ;

[0044] Figure 11 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0045] Figure 12 This is a schematic structural diagram of the chip according to an embodiment of this application;

[0046] Figure 13 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0048] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5G communication systems, or future communication systems.

[0049] For example, the communication system 100 used in the embodiments of this application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area. Optionally, the network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future communication system, etc.

[0050] The communication system 100 also includes at least one terminal 120 located within the coverage area of ​​network device 110. As used herein, "terminal" includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and / or another terminal. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. A terminal can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in future PLMNs, etc.

[0051] Optionally, the terminals 120 can communicate directly with each other via Device to Device (D2D).

[0052] Alternatively, 5G communication systems or 5G networks may also be referred to as New Radio (NR) systems or NR networks.

[0053] Figure 1 An exemplary network device and two terminals are shown. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area. This application embodiment does not limit this.

[0054] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0055] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.

[0056] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0057] To facilitate understanding of the technical solutions in the embodiments of this application, the technical solutions related to the embodiments of this application will be described below.

[0058] With people's pursuit of speed, latency, high-speed mobility, and energy efficiency, and the increasing diversity and complexity of business in future life, the third-generation partnership program (3GPP) is therefore being developed. rd The Generation Partnership Project (3GPP) international standards organization has begun developing 5G. The main application scenarios for 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0059] On the one hand, eMBB still aims to provide users with multimedia content, services, and data, and its demand is growing rapidly. On the other hand, because eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made; a detailed analysis based on the specific deployment scenario is necessary. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include high connection density, small data volume, latency-insensitive services, low module cost, and long service life.

[0060] In the early stages of NR deployment, complete NR coverage was difficult to achieve, so typical network coverage consisted of wide-area LTE coverage and isolated NR coverage. Furthermore, a large amount of LTE deployment was below 6 GHz, leaving very little spectrum available for 5G below 6 GHz. Therefore, NR had to explore spectrum applications above 6 GHz, but high-frequency band coverage was limited and signal fading was rapid. Simultaneously, to protect mobile operators' initial investments in LTE, a tight interworking mode between LTE and NR was proposed.

[0061] MBMS

[0062] MBMS is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and achieve high-speed (e.g., 256kbps) broadcast and multicast of multimedia services.

[0063] Because MBMS has low spectral efficiency, it is insufficient to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed enhancing support for downlink high-speed MBMS services and defined the design requirements for the physical layer and air interface.

[0064] 3GPP Release 9 introduced evolved MBMS (eMBMS) into LTE. eMBMS introduced the concept of a Single Frequency Network (SFN), specifically a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to transmit service data simultaneously in all cells, while ensuring synchronization between cells. This approach can significantly improve the overall signal-to-noise ratio distribution of cells, and spectrum efficiency will also be greatly improved accordingly. eMBMS implements service broadcasting and multicasting based on the IP multicast protocol.

[0065] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS only has a broadcast bearer mode, not a multicast bearer mode. Furthermore, MBMS service reception is applicable to terminal devices in either idle or connected states.

[0066] The concept of Single Cell Point To Multiploint (SC-PTM) was introduced in 3GPP R13. SC-PTM is based on the MBMS network architecture.

[0067] MBMS introduces new logical channels, including the Single Cell-Multicast Control Channel (SC-MCCH) and the Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to the Downlink-Shared Channel (DL-SCH), which is further mapped to the Physical Downlink-Shared Channel (PDSCH). SC-MCCH and SC-MTCH are logical channels, DL-SCH is a transport channel, and PDSCH is a physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat Request (HARQ) operation.

[0068] MBMS introduces a new System Information Block (SIB) type, namely SIB20. Specifically, SIB20 is used to transmit SC-MCCH configuration information, and there is only one SC-MCCH per cell. The SC-MCCH configuration information includes: the SC-MCCH modification period, the SC-MCCH repetition period, and the radio frames and subframes used to schedule the SC-MCCH. Further, 1) the boundary of the SC-MCCH modification period satisfies SFN mod m = 0, where SFN represents the system frame number of the boundary, and m is the SC-MCCH modification period (i.e., sc-mcch-ModificationPeriod) configured in SIB20. 2) the radio frames used to schedule the SC-MCCH satisfy: SFN mod mcch-RepetitionPeriod = mcch-Offset, where SFN represents the system frame number of the radio frame, mcch-RepetitionPeriod represents the SC-MCCH repetition period, and mcch-Offset represents the SC-MCCH offset. 3) Subframes for scheduling SC-MCCH are indicated by sc-mcch-Subframe.

[0069] SC-MCCH is scheduled via the Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), namely the Single Cell RNTI (SC-RNTI), is introduced to identify the PDCCH used for scheduling SC-MCCH (e.g., SC-MCCHPDCCH). Optionally, the SC-RNTI is fixed at FFFC. On the other hand, a new RNTI, the Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify the PDCCH used to indicate changes to SC-MCCH (e.g., notification PDCCH). Optionally, the SC-N-RNTI is fixed at FFFB. Furthermore, one bit from the eight bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then the SC-MCCH configures the SC-MTCH, which is used to transmit service data.

[0070] Specifically, the SC-MCCH transmits only one message (SCPTMConfiguration), which is used to configure the SC-PTM configuration information. The SC-PTM configuration information includes: Temporary Mobile Group Identity (TMGI), session ID, Group RNTI (G-RNTI), Discontinuous Reception (DRX) configuration information, and SC-PTM service information from neighboring cells. It should be noted that the SC-PTM in Release 13 does not support Robust Header Compression (ROHC).

[0071] Downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

[0072] When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, start timer onDurationTimerSCPTM;

[0073] When a downlink PDCCH schedule is received, the timer drx-InactivityTimerSCPTM is started;

[0074] Downlink SC-PTM traffic is only received when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

[0075] SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely the "SIB15+MBMSInterestIndication" method. Service continuity of idle terminal equipment is based on the concept of frequency priority.

[0076] In the technical solution of this application embodiment, a new SIB (referred to as the first SIB) is defined. The first SIB includes the configuration information of the first MCCH. Here, the first MCCH is the control channel of MBMS service. In other words, the first SIB is used to configure the configuration information of the control channel of NRMBMS. Optionally, the control channel of NR MBMS can also be called NR MCCH (i.e., the first MCCH).

[0077] Furthermore, the first MCCH is used to carry the first signaling. In this embodiment, the name of the first signaling is not limited; for example, the first signaling may be signaling A. The first signaling includes configuration information for at least one first MTCH. Here, the first MTCH is the service channel (also called the data channel or transport channel) of the MBMS service, and it is used to transmit MBMS service data (such as NR MBMS service data). In other words, the first MCCH is used to configure the configuration information of the NR MBMS service channel. Optionally, the NR MBMS service channel can also be called the NR MTCH (i.e., the first MTCH).

[0078] Specifically, the first signaling is used to configure the NR MBMS service channel, the service information corresponding to the service channel, and the scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel may include identification information such as TMGI, session ID, etc., that identifies the service. The scheduling information corresponding to the service channel may include, for example, the RNTI used when the MBMS service data corresponding to the service channel is scheduled, such as G-RNTI, DRX configuration information, etc.

[0079] It should be noted that the transmission of the first MCCH and the first MTCH is based on PDCCH scheduling. The RNTI used by the PDCCH for scheduling the first MCCH uses a globally unique identifier, i.e., a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

[0080] It should be noted that the naming of the first SIB, the first MCCH, and the first MTCH is not limited in this application embodiment. For ease of description, the first SIB can also be abbreviated as SIB, the first MCCH can also be abbreviated as MCCH, and the first MTCH can also be abbreviated as MTCH. The PDCCH (i.e., MCCHPDCCH) used for scheduling MCCH and the PDCCH are notified through the SIB. The DCI carried by the MCCH PDCCH is used to schedule the PDSCH (i.e., MCCH PDSCH) used for transmitting MCCH. Further, M PDCCHs (i.e., MTCH 1PDCCH, MTCH 2PDCCH, ..., MTCH MPDCCH) used for scheduling MTCH are configured through the MCCH. The DCI carried by the MTCH n PDCCH is used to schedule the PDSCH (i.e., MTCH n PDSCH) used for transmitting MTCH n, where n is an integer greater than or equal to 1 and less than or equal to M. MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH. MCCH and MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.

[0081] It should be noted that the MBMS service in the above scheme includes, but is not limited to, multicast and multi-cast services. This application uses MBS service as an example for illustration, and the description of "MBS service" can also be replaced with "multicast service," "multicast service," or "MBMS service."

[0082] In NR MBS services, in addition to multicast MBS services within the same cell, the base station may also transmit the MBS service to a specific user via unicast, for example, if that user has a poor channel. Within a cell, several users may simultaneously receive the same MBS service, but the base station transmits the MBS service to each user via unicast. For example, if there are few users receiving MBS services in the cell, using unicast to transmit the MBS service to each user can effectively improve service transmission efficiency.

[0083] Reference Figure 2For a specific MBS (Mobile Broadcast Service) packet data unit (PDU) session, a shared GTP tunnel may be used between the 5G core network (5GC) and the gNB to transmit the MBS service. This means that both unicast and multicast MBS services share this GTP tunnel. The gNB distributes MBS services to a multicast group via multicast and to a specific UE via unicast. Figure 2 (Taking UE3 as an example). The multicast group includes one or more UEs (...). Figure 2 (Taking a multicast group including UE1 and UE2 as an example).

[0084] In NR systems, higher reliability requirements are placed on MBS services, necessitating feedback from terminal devices regarding MBS service reception. However, current feedback mechanisms suffer from the following issues: if multiple users are receiving MBS service data, and only one user experiences a reception error, multicast retransmission of that MBS service data is redundant and power-intensive for the other users. For example, if 10 users are receiving MBS service data, and only one user experiences a reception error, multicast retransmission of that MBS service data would be redundant and power-intensive for the other 9 users. Therefore, efficient retransmission is a problem that needs to be solved.

[0085] Figure 3 This is a flowchart illustrating the MBS service transmission method provided in the embodiments of this application. Figure 1 ,like Figure 3 As shown, the MBS service transmission method includes the following steps:

[0086] Step 301: The terminal device receives the first MBS service data sent by the network device in a multicast manner.

[0087] In this embodiment, the network device transmits first MBS service data via multicast, and correspondingly, the terminal device receives the first MBS service data transmitted by the network device via multicast. Here, the network device may be a base station, such as a gNB.

[0088] In this embodiment of the application, the network device sends first configuration information to the terminal device, and correspondingly, the terminal device receives the first configuration information sent by the network device. The first configuration information includes at least one of the following:

[0089] The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode.

[0090] The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner.

[0091] The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process.

[0092] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0093] The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0094] The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0095] In this embodiment, optionally, the network device sends second configuration information to the terminal device, and correspondingly, the terminal device receives the second configuration information sent by the network device. The second configuration information is used to determine that the transmission corresponding to the multicast mode has M HARQ processes, where M is a positive integer. Further, optionally, the HARQ process number of each of the M HARQ processes is configured using the second configuration information; or, the HARQ process number of each of the M HARQ processes is calculated by the terminal device.

[0096] Step 302: The terminal device sends a first NACK message to the network device. The first NACK message is used to indicate that the terminal device has encountered an error in receiving the first MBS service data.

[0097] In this embodiment of the application, if the terminal device fails to receive the first MBS service data, the terminal device sends a first NACK message to the network device. Correspondingly, the network device receives the first NACK message sent by the terminal device. The first NACK message is used to indicate that the terminal device has failed to receive the first MBS service data.

[0098] Step 303: The terminal device receives the retransmission data of the first MBS service data sent by the network device in unicast mode.

[0099] In this embodiment of the application, after the network device receives the first NACK information sent by the terminal device, the network device sends the retransmission data of the first MBS service data to the terminal device in a unicast manner, and correspondingly, the terminal device receives the retransmission data of the first MBS service data sent by the network device in a unicast manner.

[0100] In this embodiment, the first MBS service data transmitted in a multicast manner is scheduled through a first DCI, the first DCI carrying a first HARQ process number; the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled through a second DCI, the second DCI carrying the first HARQ process number.

[0101] Here, the first HARQ process number is used to identify the first HARQ process. That is, the first MBS service data transmitted in multicast mode and the retransmission data of the first MBS service data transmitted in unicast mode share the first HARQ process.

[0102] In this embodiment, the terminal device performs soft merging of the received first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number. It should be noted that the terminal device performs soft merging of MBS service data corresponding to the same HARQ process (i.e., the first HARQ process) at the physical layer. Since the retransmission data of the unicast first MBS service data and the multicast first MBS service data correspond to the same HARQ process (i.e., the first HARQ process), the terminal device performs soft merging of the received first MBS service data and the retransmission data of the first MBS service data.

[0103] Furthermore, in an optional embodiment of this application, the network device transmits the second MBS service data via multicast. Correspondingly, the terminal device receives the second MBS service data transmitted by the network device via multicast. The second MBS service data transmitted via multicast is scheduled through a third DCI, which carries the first HARQ process number. Here, the second MBS service data is different from the first MBS service data.

[0104] Here, the first HARQ process number is used to identify the first HARQ process. That is, the retransmission data of the second MBS service data transmitted in multicast mode and the retransmission data of the first MBS service data transmitted in unicast mode also share the first HARQ process. For this situation, there are the following two implementation schemes.

[0105] Option A):

[0106] If the terminal device encounters an error in receiving retransmitted data of the first MBS service data and also encounters an error in receiving the second MBS service data, the terminal device sends a second NACK message to the network device. Correspondingly, the network device receives the second NACK message sent by the terminal device. The second NACK message indicates that the terminal device has encountered an error in receiving the second MBS service data. The network device then sends retransmitted data of the second MBS service data to the terminal device via unicast. Correspondingly, the terminal device receives the retransmitted data of the second MBS service data sent by the network device via unicast.

[0107] Here, the retransmission data of the second MBS service data transmitted in unicast mode is scheduled through the fourth DCI, which carries the first HARQ process number.

[0108] In other words, if the terminal device encounters an error in receiving retransmitted data of the first MBS service data and also encounters an error in receiving the second MBS service data, the terminal device ignores the HARQ feedback for the retransmitted data of the first MBS service data, or the terminal device assumes that the retransmitted data of the first MBS service data was received correctly and therefore does not provide HARQ feedback. The terminal device sends a second NACK message to the network device, which indicates that the terminal device encountered an error in receiving the second MBS service data, and the terminal device receives the retransmitted data of the second MBS service data sent by the network device in a unicast manner.

[0109] Option B:

[0110] The first MBS service data transmitted via multicast is scheduled through a first DCI, which carries a first HARQ process number; retransmission data of the first MBS service data transmitted via unicast is scheduled through a second DCI, which carries the first HARQ process number. Furthermore, the first DCI and / or the second DCI also carry a first sequence number, which is used to identify the first MBS service data.

[0111] In addition, the retransmission data of the first MBS service data transmitted in unicast mode is scheduled through the fifth DCI, which carries the first HARQ process number and the first sequence number.

[0112] Here, the first HARQ process number is used to identify the first HARQ process. That is to say, the first MBS service data transmitted in multicast mode, the retransmission data of the first MBS service data transmitted in unicast mode, and the subsequent retransmission data all share the first HARQ process.

[0113] The second MBS service data transmitted in a multicast manner is scheduled through a third DCI, which carries the first HARQ process number and the second sequence number, the second sequence number being used to identify the second MBS service data; wherein, the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled through a fourth DCI, which carries the first HARQ process number and the second sequence number.

[0114] Here, the first HARQ process number is used to identify the first HARQ process. That is, the second MBS service data transmitted in multicast mode and the retransmission data of the second MBS service data transmitted in unicast mode share the first HARQ process.

[0115] Since the first MBS service data and its retransmission data share the first HARQ process with the second MBS service data and its retransmission data, and since the prerequisite for soft merging is to perform soft merging on MBS service data on the same HARQ process, in order to correctly implement soft merging, it is necessary to distinguish between the first MBS service data and the second MBS service data. The first MBS service data and the second MBS service data can be distinguished by sequence numbers. Specifically, the first MBS service data is identified by a first sequence number, and the second MBS service data is identified by a second sequence number.

[0116] Based on this, the terminal device performs soft merging of the retransmission data of the first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number and the first sequence number; the terminal device performs soft merging of the received second MBS service data and the retransmission data of the second MBS service data based on the first HARQ process number and the second sequence number.

[0117] Reference Figure 4The base station's MAC entity copies each MAC PDU (i.e., one TB of data or one MBS service data) to one PHY entity, and the original MAC PDU to the other PHY entity. One of the two PHY entities sends the MBS service data via multicast, and the other sends it via unicast. 1. The base station sends the MBS service data via multicast. This MBS service data is scheduled using a DCI scrambled with G-RNTI, and the DCI carries the HARQ process identifier k. 2. If the UE fails to receive the MBS service data, it sends a NACK message to the base station. 3. The base station retransmits the MBS service data via unicast. This retransmitted MBS service data is scheduled using a DCI scrambled with C-RNTI, and the DCI carries the HARQ process identifier k.

[0118] The technical solutions of the embodiments of this application are illustrated below with specific application examples.

[0119] 1. When a UE enters the RRC connected state to receive MBS services, the network device is configured to provide the UE with at least one of the following indications:

[0120] The first indication information is used to indicate whether the UE can simultaneously receive MBS service data in multicast mode and MBS service data in unicast mode.

[0121] The second instruction information is used to instruct the UE to receive the retransmitted MBS service data in a unicast manner. The MBS service data refers to the MBS service data that was not previously received correctly.

[0122] The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process.

[0123] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0124] The fifth indication information is used to indicate whether the UE is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0125] The sixth indication information is used to indicate whether the UE determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0126] 2. The UE receives MBS service data in multicast mode, and the HARQ feedback of this MBS service data is NACK.

[0127] 3. The network device retransmits the MBS service data for users who respond with NACK via unicast. Here, the network device retrieves or copies the MBS service data corresponding to the NACK response from memory in multicast mode, and schedules and retransmits it via unicast.

[0128] 4. The UE receives the retransmitted MBS service data in unicast mode. The UE determines that the unicast transmission corresponds to the repeated transmission of the multicast transmission based on the HARQ process identifier in the multicast DCI (i.e., the DCI scrambled by G-RNTI) and the HARQ process identifier in the unicast transmission DCI (i.e., the DCI scrambled by C-RNTI). This allows for soft merging of the multicast MBS service data and the unicast retransmitted data, thereby improving the decoding success rate.

[0129] 5. Assuming there are M HARQ processes in multicast transmission, where M is a positive integer, the network device can configure the number of multicast HARQ processes. Furthermore, the network device can also configure the HARQ process identifier for each HARQ process, or the UE can calculate the HARQ process identifier for the multicast HARQ process based on certain rules (e.g., scheduling information).

[0130] 6. For the HARQ process containing MBS service data that has received a NACK, the network device can pause for a period of time before sending new MBS service data, or send new MBS service data directly after receiving HARQ feedback (without waiting for successful retransmission). Here, the period of time can be a time period length specified in the protocol.

[0131] 7. For the UE, after receiving MBS service data via multicast and encountering an error, the UE sends back a NACK. The HARQ process identifier of the MBS service data is identifier 1. Then, the UE only receives the MBS service data corresponding to identifier 1 via unicast and performs soft merging of the received MBS service data (i.e., the retransmission data of the previously erroneous MBS service data) with the previously erroneous MBS service data. The soft-merged data is then decoded.

[0132] 8. 1) For the UE, if two MBS service data packets fail to be received correctly in succession, and the HARQ process identifiers associated with these two MBS service data packets are the same, then the UE assumes that the first MBS service data packet that was not received correctly was received correctly, i.e., it abandons the first MBS service data packet. It only sends a NACK feedback for the second MBS service data packet and receives the retransmission data of the second MBS service data packet. Or, 2) If two MBS service data packets fail to be received correctly in succession, and the HARQ process identifiers associated with these two MBS service data packets are the same, then two sequence numbers are needed to distinguish between these two MBS service data packets, so that the UE can simultaneously receive the retransmission data of these two MBS service data packets.

[0133] Figure 5 This is a flowchart illustrating the MBS service transmission method provided in the embodiments of this application. Figure 3 ,like Figure 5 As shown, the MBS service transmission method includes the following steps:

[0134] Step 501: The terminal device receives the first MBS service data sent by the network device in a multicast manner and the first MBS service data sent in a unicast manner.

[0135] In this embodiment, the network device can simultaneously send the first MBS service data via multicast and via unicast to a specific terminal device. Here, the network device can be a base station, such as a gNB.

[0136] In this embodiment of the application, the network device sends first configuration information to the terminal device, and correspondingly, the terminal device receives the first configuration information sent by the network device. The first configuration information includes at least one of the following:

[0137] The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode.

[0138] The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner.

[0139] The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process.

[0140] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0141] The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0142] The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0143] In this embodiment of the application, the first MBS service data transmitted in a multicast manner is scheduled through a first DCI, the first DCI carrying a first HARQ process number; the first MBS service data transmitted in a unicast manner is scheduled through a second DCI, the second DCI carrying a second HARQ process number.

[0144] 1) When the HARQ process identifier for multicast MBS services and the HARQ process identifier for unicast MBS services use the same number space,

[0145] The terminal device determines a first HARQ process based on the first HARQ process number and the G-RNTI scrambling the first DCI, and determines a second HARQ process based on the second HARQ process number and the C-RNTI scrambling the first DCI; if the first HARQ process and the second HARQ process are associated, the terminal device will perform soft merging of the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process.

[0146] Here, the HARQ process identifiers for multicast MBS services and unicast MBS services use the same number space. It is possible that the HARQ process identifiers for multicast and unicast services may be the same. In this case, a HARQ process can be uniquely identified by combining the RNTI with the HARQ process identifier.

[0147] 2) When the HARQ process identifiers for multicast MBS services and unicast MBS services use separate numbering spaces,

[0148] The terminal device determines a first HARQ process based on the first HARQ process number and a second HARQ process based on the second HARQ process number; if the first HARQ process and the second HARQ process are associated, the terminal device will perform soft merging of the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process.

[0149] Here, the HARQ process identifiers for multicast MBS services and unicast MBS services use independent numbering spaces. The independent numbering spaces ensure that there is no overlap between the numbering spaces for multicast and unicast services. In other words, a HARQ process can be uniquely identified directly based on the HARQ process identifier.

[0150] Reference Figure 6 and Figure 7 ,in, Figure 6 The SDAP entity replicates MBS service data and transmits it through two paths: one via multicast and the other via unicast. Figure 7 The PDCP entity replicates MBS service data and transmits it through two channels: one channel is distributed via multicast and the other via unicast.

[0151] Network devices can be configured to provide indications to the UE. For example, one indication might indicate that the UE can simultaneously receive both unicast and multicast MBS services. Another indication might indicate that the UE does not need to provide HARQ feedback for multicast services. Yet another indication might indicate that the unicast service is transmitting new MBS data, not retransmitted data.

[0152] In this embodiment, the network-side HARQ processes for unicast and multicast are either independent or shared.

[0153] In one example, the UE encounters an error receiving multicast MBS service data but successfully receives unicast MBS service data. In this case, the multicast and unicast MBS service data are soft-merged at the physical layer to improve decoding efficiency. Here, the prerequisite for soft merging is that the multicast and unicast MBS service data are the same MBS service data. Optionally, the HARQ process number can be used to determine whether the multicast and unicast MBS service data are the same MBS service data. Alternatively, the HARQ process number and RNTI can be used to determine whether the multicast and unicast MBS service data are the same MBS service data.

[0154] Figure 8 This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 1 Applied to terminal devices, such as Figure 8 As shown, the MBS service transmission device includes:

[0155] The receiving unit 801 is used to receive the first MBS service data sent by the network device in a multicast manner;

[0156] Sending unit 802 is used to send a first NACK message to the network device, the first NACK message being used to indicate that the terminal device has encountered an error in receiving the first MBS service data;

[0157] The receiving unit 801 is further configured to receive retransmission data of the first MBS service data sent by the network device in a unicast manner.

[0158] In an alternative embodiment, the receiving unit 801 is further configured to receive first configuration information sent by the network device, the first configuration information including at least one of the following:

[0159] The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode.

[0160] The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner.

[0161] The third indication information is used to indicate that MBS service data transmitted in multicast mode and MBS service data transmitted in unicast mode share the Hybrid Automatic Repeat Request (HARQ) process.

[0162] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0163] The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0164] The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0165] In an alternative mode, the first MBS service data transmitted in a multicast manner is scheduled by a first downlink control information (DCI), the first DCI carrying a first HARQ process number;

[0166] The retransmission data of the first MBS service data transmitted in unicast mode is scheduled by the second DCI, which carries the first HARQ process number.

[0167] In an alternative embodiment, the device further includes:

[0168] The processing unit (not shown in the figure) is used to perform soft merging of the received first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number.

[0169] In an optional configuration, the receiving unit 801 is further configured to receive second MBS service data sent by the network device in a multicast manner, wherein the second MBS service data transmitted in a multicast manner is scheduled through a third DCI, and the third DCI carries the first HARQ process number.

[0170] The sending unit 802 is further configured to send a second NACK message to the network device when the receiving unit encounters an error in retransmitting the first MBS service data and also encounters an error in receiving the second MBS service data. The second NACK message is used to indicate that the terminal device has encountered an error in receiving the second MBS service data.

[0171] The receiving unit 801 is further configured to receive retransmission data of the second MBS service data sent by the network device in a unicast manner.

[0172] In an alternative approach, retransmission data of the second MBS service data transmitted in a unicast manner is scheduled through a fourth DCI, which carries the first HARQ process number.

[0173] In an alternative embodiment, the first DCI and / or the second DCI also carry a first sequence number, which is used to identify the first MBS service data.

[0174] In an optional embodiment, the receiving unit 801 is further configured to receive second MBS service data sent by the network device in a multicast manner. The second MBS service data transmitted in a multicast manner is scheduled through a third DCI. The third DCI carries the first HARQ process number and the second sequence number, and the second sequence number is used to identify the second MBS service data.

[0175] The retransmission data of the second MBS service data transmitted in unicast mode is scheduled by the fourth DCI, which carries the first HARQ process number and the second sequence number.

[0176] In an alternative approach, the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled through a fifth DCI, which carries the first HARQ process number and the first sequence number.

[0177] In an alternative embodiment, the device further includes:

[0178] The processing unit is configured to perform soft merging of the retransmission data of the first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number and the first sequence number; and to perform soft merging of the received second MBS service data and the retransmission data of the second MBS service data based on the first HARQ process number and the second sequence number.

[0179] In an optional configuration, the receiving unit 801 is further configured to receive second configuration information sent by the network device, the second configuration information being used to determine that the transmission corresponding to the multicast mode has M HARQ processes, where M is a positive integer.

[0180] In one optional approach, the HARQ process number of each of the M HARQ processes is configured using the second configuration information; or,

[0181] The HARQ process number of each of the M HARQ processes is calculated by the terminal device.

[0182] Those skilled in the art should understand that the description of the MBS service transmission device in the embodiments of this application can be understood with reference to the description of the MBS service transmission method in the embodiments of this application.

[0183] Figure 9This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 2 Applied to terminal devices, such as Figure 9 As shown, the MBS service transmission device includes:

[0184] The receiving unit 901 is used to receive the first MBS service data sent by the network device in a multicast manner and the first MBS service data sent in a unicast manner.

[0185] In an alternative embodiment, the receiving unit 901 is further configured to receive first configuration information sent by the network device, the first configuration information including at least one of the following:

[0186] The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode.

[0187] The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner.

[0188] The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process.

[0189] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0190] The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0191] The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0192] In an alternative approach, the first MBS service data transmitted via multicast is scheduled through a first DCI, the first DCI carrying a first HARQ process number;

[0193] The first MBS service data transmitted in unicast mode is scheduled by the second DCI, which carries the second HARQ process number.

[0194] In an alternative embodiment, the device further includes:

[0195] Processing unit 902 is configured to determine a first HARQ process based on the first HARQ process number and the G-RNTI scrambling the first DCI, and to determine a second HARQ process based on the second HARQ process number and the C-RNTI scrambling the first DCI; if the first HARQ process and the second HARQ process are associated, then the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process are soft-merged.

[0196] In one optional mode, the HARQ process identifier for the multicast MBS service and the HARQ process identifier for the unicast MBS service use the same numbering space.

[0197] In an alternative embodiment, the device further includes:

[0198] Processing unit 902 is configured to determine a first HARQ process based on the first HARQ process number and a second HARQ process based on the second HARQ process number; if the first HARQ process and the second HARQ process are associated, the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process are soft-merged.

[0199] In one optional approach, the HARQ process identifiers for multicast MBS services and unicast MBS services use separate numbering spaces.

[0200] Those skilled in the art should understand that the description of the MBS service transmission device in the embodiments of this application can be understood with reference to the description of the MBS service transmission method in the embodiments of this application.

[0201] Figure 10 This is a schematic diagram of the structural composition of the MBS service transmission device provided in the embodiments of this application. Figure 3 Applied to network devices, such as Figure 10 As shown, the MBS service transmission device includes:

[0202] The transmitting unit 1001 is used to transmit the first MBS service data in a multicast manner;

[0203] The receiving unit 1002 is configured to receive a first NACK message sent by the terminal device, wherein the first NACK message is used to indicate that the terminal device has encountered an error in receiving the first MBS service data.

[0204] The sending unit 1001 is further configured to send retransmission data of the first MBS service data to the terminal device in a unicast manner.

[0205] In an optional embodiment, the sending unit 1001 is further configured to send first configuration information to the terminal device, the first configuration information including at least one of the following:

[0206] The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode.

[0207] The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner.

[0208] The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process.

[0209] The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space.

[0210] The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode;

[0211] The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

[0212] In an alternative approach, the first MBS service data transmitted via multicast is scheduled through a first DCI, the first DCI carrying a first HARQ process number;

[0213] The retransmission data of the first MBS service data transmitted in unicast mode is scheduled by the second DCI, which carries the first HARQ process number.

[0214] In an optional configuration, the sending unit 1001 is further configured to send second MBS service data in a multicast manner, wherein the second MBS service data transmitted in a multicast manner is scheduled by a third DCI, and the third DCI carries the first HARQ process number.

[0215] The receiving unit 1002 is further configured to receive a second NACK information sent by the terminal device, the second NACK information being used to indicate that the terminal device has encountered an error in receiving the second MBS service data;

[0216] The sending unit 1001 is further configured to send retransmission data of the second MBS service data to the network device in a unicast manner.

[0217] In an alternative approach, retransmission data of the second MBS service data transmitted in a unicast manner is scheduled through a fourth DCI, which carries the first HARQ process number.

[0218] In an alternative embodiment, the first DCI and / or the second DCI also carry a first sequence number, which is used to identify the first MBS service data.

[0219] In an optional configuration, the sending unit 1001 is further configured to send second MBS service data in a multicast manner. The second MBS service data transmitted in a multicast manner is scheduled by a third DCI. The third DCI carries the first HARQ process number and the second sequence number, and the second sequence number is used to identify the second MBS service data.

[0220] The retransmission data of the second MBS service data transmitted in unicast mode is scheduled by the fourth DCI, which carries the first HARQ process number and the second sequence number.

[0221] In an alternative approach, the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled through a fifth DCI, which carries the first HARQ process number and the first sequence number.

[0222] In an optional configuration, the sending unit 1001 is further configured to send second configuration information to the terminal device, the second configuration information being used to determine that the transmission corresponding to the multicast mode has M HARQ processes, where M is a positive integer.

[0223] In one optional approach, the HARQ process number of each of the M HARQ processes is configured using the second configuration information; or,

[0224] The HARQ process number of each of the M HARQ processes is calculated by the terminal device.

[0225] Those skilled in the art should understand that the description of the MBS service transmission device in the embodiments of this application can be understood with reference to the description of the MBS service transmission method in the embodiments of this application.

[0226] Figure 11 This is a schematic structural diagram of a communication device 1100 provided in an embodiment of this application. This communication device can be a terminal device or a network device. Figure 11 The communication device 1100 shown includes a processor 1110, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0227] Optionally, such as Figure 11 As shown, the communication device 1100 may further include a memory 1120. The processor 1110 can retrieve and run computer programs from the memory 1120 to implement the methods described in this embodiment.

[0228] The memory 1120 can be a separate device independent of the processor 1110, or it can be integrated into the processor 1110.

[0229] Optionally, such as Figure 11 As shown, the communication device 1100 may also include a transceiver 1130. The processor 1110 can control the transceiver 1130 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0230] The transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include an antenna, and the number of antennas may be one or more.

[0231] Optionally, the communication device 1100 may specifically be a network device in the embodiments of this application, and the communication device 1100 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0232] Optionally, the communication device 1100 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 1100 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0233] Figure 12 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 12 The chip 1200 shown includes a processor 1210, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0234] Optionally, such as Figure 12As shown, chip 1200 may further include memory 1220. Processor 1210 can retrieve and run computer programs from memory 1220 to implement the methods described in this embodiment.

[0235] The memory 1220 can be a separate device independent of the processor 1210, or it can be integrated into the processor 1210.

[0236] Optionally, the chip 1200 may also include an input interface 1230. The processor 1210 can control the input interface 1230 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0237] Optionally, the chip 1200 may also include an output interface 1240. The processor 1210 can control the output interface 1240 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0238] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0239] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0240] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0241] Figure 13 This is a schematic block diagram of a communication system 1300 provided in an embodiment of this application. Figure 13 As shown, the communication system 1300 includes a terminal device 1310 and a network device 1320.

[0242] The terminal device 1310 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1320 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, these will not be elaborated here.

[0243] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0244] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0245] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0246] This application also provides a computer-readable storage medium for storing computer programs.

[0247] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0248] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0249] This application also provides a computer program product, including computer program instructions.

[0250] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0251] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0252] This application also provides a computer program.

[0253] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0254] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0255] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0256] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0258] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0259] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0260] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0261] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for transmitting Multimedia Multicast Service (MBS) traffic, the method comprising: The terminal device receives the first MBS service data sent by the network device in a multicast manner and the first MBS service data sent in a unicast manner; The first MBS service data transmitted in a multicast manner is scheduled by the first DCI, and the first DCI carries the first HARQ process number. The first MBS service data transmitted in unicast mode is scheduled by the second DCI, and the second DCI carries the second HARQ process number; The terminal device determines the first HARQ process based on the first HARQ process number and the G-RNTI scrambling the first DCI, and determines the second HARQ process based on the second HARQ process number and the C-RNTI scrambling the second DCI. If the first HARQ process and the second HARQ process are associated, the terminal device will perform soft merging of the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process.

2. The method according to claim 1, wherein, The method further includes: The terminal device receives first configuration information sent by the network device, the first configuration information including at least one of the following: The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode. The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner. The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process. The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space. The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode; The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

3. The method according to claim 1, wherein, The HARQ process identifier for multicast MBS services and the HARQ process identifier for unicast MBS services use the same number space.

4. An MBS service transmission apparatus, applied to a terminal device, the apparatus comprising: The receiving unit is configured to receive the first MBS service data sent by the network device in a multicast manner and the first MBS service data sent in a unicast manner. The first MBS service data transmitted in a multicast manner is scheduled by the first DCI, and the first DCI carries the first HARQ process number. The first MBS service data transmitted in unicast mode is scheduled by the second DCI, and the second DCI carries the second HARQ process number; The processing unit is configured to determine a first HARQ process based on the first HARQ process number and the G-RNTI scrambling the first DCI, and to determine a second HARQ process based on the second HARQ process number and the C-RNTI scrambling the second DCI; if the first HARQ process and the second HARQ process are associated, then the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process are soft-merged.

5. The apparatus according to claim 4, wherein, The receiving unit is further configured to receive first configuration information sent by the network device, wherein the first configuration information includes at least one of the following: The first indication information is used to indicate whether the terminal device simultaneously receives MBS service data in multicast mode and MBS service data in unicast mode. The second instruction information is used to instruct the terminal device to receive the retransmission data of MBS service data in a unicast manner. The third indication information is used to indicate that MBS service data transmitted in a multicast manner and MBS service data transmitted in a unicast manner share the HARQ process. The fourth indication information is used to indicate whether the HARQ process identifier corresponding to the MBS service and the HARQ process identifier corresponding to the unicast service use the same number space or an independent number space. The fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to MBS service data in multicast mode; The sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier or based on the HARQ process identifier and RNTI.

6. The apparatus according to claim 4, wherein, The HARQ process identifier for multicast MBS services and the HARQ process identifier for unicast MBS services use the same number space.

7. A terminal device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 3.

8. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 3.

9. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as described in any one of claims 1 to 3.

Images