WO2022021410A1 - Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau - Google Patents

Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau Download PDF

Info

Publication number
WO2022021410A1
WO2022021410A1 PCT/CN2020/106387 CN2020106387W WO2022021410A1 WO 2022021410 A1 WO2022021410 A1 WO 2022021410A1 CN 2020106387 W CN2020106387 W CN 2020106387W WO 2022021410 A1 WO2022021410 A1 WO 2022021410A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbs service
harq process
service data
terminal device
indication information
Prior art date
Application number
PCT/CN2020/106387
Other languages
English (en)
Chinese (zh)
Inventor
王淑坤
石聪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/106387 priority Critical patent/WO2022021410A1/fr
Priority to CN202310507829.XA priority patent/CN116566551A/zh
Priority to CN202080101107.9A priority patent/CN115668829A/zh
Publication of WO2022021410A1 publication Critical patent/WO2022021410A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a method and apparatus for transmitting a Multimedia Broadcast Service (MBS) service, a terminal device, and a network device.
  • MMS Multimedia Broadcast Service
  • New Radio New Radio, NR
  • higher requirements are put forward for the reliability of the MBS service, and the terminal equipment is required to give feedback on the reception of the MBS service.
  • the current feedback mechanism has the following problems: if a MBS service data is received by multiple users, only one user receives the data incorrectly, and multicast retransmission of the MBS service data is redundant for other users and consumes electricity of. Therefore, how to perform efficient retransmission is a problem that needs to be solved.
  • Embodiments of the present application provide an MBS service transmission method and apparatus, terminal equipment, and network equipment.
  • the terminal device receives the first MBS service data sent by the network device in a multicast manner
  • NACK negative acknowledgement
  • the terminal device receives retransmission data of the first MBS service data sent by the network device in a unicast manner.
  • 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 network device sends the first MBS service data in a multicast manner
  • the network device sends the retransmission data of the first MBS service data to the terminal device in a unicast manner.
  • the MBS service transmission apparatus provided by the embodiment of the present application is applied to terminal equipment, and the apparatus includes:
  • a receiving unit configured to receive the first MBS service data sent by the network device in a multicast manner
  • a sending unit configured to send first NACK information to the network device, where the first NACK information is used to instruct the terminal device to receive an error in the first MBS service data;
  • 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.
  • the MBS service transmission apparatus provided by the embodiment of the present application is applied to terminal equipment, and the apparatus includes:
  • 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 MBS service transmission apparatus provided by the embodiment of the present application is applied to network equipment, and the apparatus includes:
  • a sending unit configured to send the first MBS service data in a multicast manner
  • a receiving unit configured to receive first NACK information sent by a terminal device, where the first NACK information is used to instruct the terminal device to receive an error in the first MBS service data;
  • the sending unit is further configured to send the retransmission data of the first MBS service data to the terminal device in a unicast manner.
  • the terminal device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the above-mentioned MBS service transmission method.
  • the network device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the above-mentioned MBS service transmission method.
  • the chip provided by the embodiment of the present application is used to implement the above-mentioned MBS service transmission method.
  • the chip includes: a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned MBS service transmission method.
  • the computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program enables a computer to execute the above-mentioned MBS service transmission method.
  • the computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned MBS service transmission method.
  • the computer program provided by the embodiment of the present application when running on a computer, enables the computer to execute the above-mentioned MBS service transmission method.
  • the network device after receiving the first NACK information sent by a terminal device, can confirm that the terminal device receives the first MBS service data in error, and retransmit the first NACK information to the terminal device through unicast.
  • the MBS service data avoids redundant reception of the first MBS service data by other terminal devices, and achieves the purpose of energy saving and efficient feedback.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the transmission of MBS services provided by an embodiment of the present application in a multicast mode and a unicast mode;
  • FIG. 3 is a schematic flowchart 1 of an MBS service transmission method provided by an embodiment of the present application.
  • FIG. 4 is a second schematic flowchart of a method for transmitting an MBS service provided by an embodiment of the present application
  • FIG. 5 is a schematic flowchart 3 of an MBS service transmission method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram 1 of simultaneously delivering MBS service data in a multicast mode and a unicast mode according to an embodiment of the present application;
  • FIG. 7 is a schematic diagram 2 of simultaneously delivering MBS service data in a multicast mode and a unicast mode according to an embodiment of the present application;
  • FIG. 8 is a schematic diagram 1 of the structure and composition of an MBS service transmission apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram 2 of the structure and composition of an MBS service transmission device provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram 3 of the structure and composition of the MBS service transmission device provided by the embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication systems or future communication systems etc.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area.
  • the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the
  • the network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system.
  • the communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 .
  • Terminal includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit a communication signal; and/or an Internet of Things (IoT) device.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal” or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communication capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • a terminal may refer to an access terminal, user equipment (UE), subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .
  • the 5G communication system or the 5G network may also be referred to as a new radio (New Radio, NR) system or an NR network.
  • New Radio NR
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of terminals. This embodiment of the present application This is not limited.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • 5G 3rd Generation Partnership Project
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC Massive Machine-Type Communications
  • eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly.
  • eMBB since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios.
  • Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety assurance, etc.
  • Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of the module.
  • MBMS is a technology that transmits data from a data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize the broadcast of multimedia services at higher rates (such as 256kbps). and multicast.
  • 3GPP clearly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.
  • eMBMS evolved MBMS
  • SFN Single Frequency Network
  • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
  • MBSFN uses a uniform frequency to send service data in all cells at the same time, but To ensure synchronization between cells. In this way, the overall signal-to-noise ratio distribution of the cell can be greatly improved, and the spectral efficiency will also be greatly improved accordingly.
  • eMBMS implements service broadcast and multicast based on IP multicast protocol.
  • MBMS has only a broadcast bearer mode and no multicast bearer mode.
  • the reception of the MBMS service is applicable to the terminal equipment in the idle state or the connected state.
  • SC-PTM Single Cell Point To Multiploint
  • SC-MCCH Single Cell Multicast Control Channel
  • SC-MTCH Single Cell Multicast Transport Channel
  • SC-MCCH and SC-MTCH are mapped to downlink shared channel (Downlink-Shared Channel, DL-SCH), further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), wherein, SC - MCCH and SC-MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.
  • SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operations.
  • Hybrid Automatic Repeat reQuest Hybrid Automatic Repeat reQuest
  • MBMS introduces a new system information block (System Information Block, SIB) type, namely SIB20.
  • SIB System Information Block
  • the configuration information of the SC-MCCH includes the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and information such as the radio frame and subframe in which the SC-MCCH is scheduled.
  • SFN represents the system frame number of the radio frame
  • mcch-RepetitionPeriod represents the repetition period of SC-MCCH
  • mcch-Offset represents SC-MCCH offset.
  • the SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH).
  • PDCCH Physical Downlink Control Channel
  • RNTI Radio Network Tempory Identity
  • SC-RNTI Single Cell RNTI
  • the fixed value of SC-RNTI is FFFC.
  • a new RNTI is introduced, that is, a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of the SC-MCCH, optionally, the SC
  • the fixed value of -N-RNTI is FFFB; further, one of the 8 bits (bits) of DCI 1C can be used to indicate the change notification.
  • the configuration information of the SC-PTM is based on the SC-MCCH configured by the SIB20, and then the SC-MCCH configures the SC-MTCH, and the SC-MTCH is used to transmit service data.
  • the SC-MCCH only transmits one message (ie, SCPTMConfiguration), which is used to configure the configuration information of the SC-PTM.
  • the configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session identifier (session id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM service information of neighboring cells, etc.
  • TMGI Temporary Mobile Group Identity
  • session id session identifier
  • group RNTI Group RNTI, G-RNTI
  • discontinuous reception discontinuous Reception
  • DRX discontinuous Reception
  • Downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
  • the downstream SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.
  • SC-PTM business continuity adopts the concept of MBMS business continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode.
  • SIB15 namely "SIB15+MBMSInterestIndication" mode.
  • the service continuity of terminal equipment in idle state is based on the concept of frequency priority.
  • a new SIB (called the first SIB) is defined, and the first SIB includes the configuration information of the first MCCH.
  • the first MCCH is the control channel of the MBMS service.
  • An SIB is used to configure the configuration information of the control channel of the NR MBMS.
  • the control channel of the NR MBMS may also be called the NR MCCH (that is, the first MCCH).
  • the first MCCH is used to carry the first signaling, and the embodiment of this application does not limit the name of the first signaling.
  • the first signaling is signaling A
  • the first signaling includes at least one first MTCH.
  • the first MTCH is a service channel (also called a data channel or a transmission channel) of the MBMS service
  • the first MTCH is used to transmit MBMS service data (such as NR MBMS service data).
  • the first MCCH is used to configure the configuration information of the traffic channel of the NR MBMS.
  • the traffic channel of the NR MBMS may also be called the NR MTCH (that is, the first MTCH).
  • the first signaling is used to configure a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel.
  • the service information corresponding to the service channel such as TMGI, session id and other identification information for identifying services.
  • the scheduling information corresponding to the traffic channel for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, such as G-RNTI, DRX configuration information, and the like.
  • the transmissions of the first MCCH and the first MTCH are both scheduled based on the PDCCH.
  • the RNTI used for scheduling the PDCCH of the first MCCH uses a network-wide unique identifier, that is, a fixed value.
  • the RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.
  • this embodiment of the present application does not limit the naming of the first SIB, the first MCCH, and the first MTCH.
  • the first SIB may also be abbreviated as SIB
  • the first MCCH may also be abbreviated as MCCH
  • the first MTCH may also be abbreviated as MTCH.
  • M PDCCHs for scheduling MTCH through MCCH (ie MTCH 1 PDCCH, MTCH 2 PDCCH, ..., MTCH M PDCCH), wherein the DCI carried by MTCH n PDCCH schedules the PDSCH used for transmitting MTCH n (ie MTCH n PDSCH), 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, wherein MCCH and MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.
  • MBMS services in the above solution include but are not limited to multicast services and multicast services.
  • the embodiments of the present application are described by taking the MBS service as an example, and the description of "MBS service” may also be replaced with "multicast service” or “multicast service” or "MBMS service”.
  • the same cell needs to deliver the MBS service in the multicast mode, and may also transmit the MBS service in the unicast mode for a specific user.
  • the user transmits the MBS service in a unicast manner.
  • the base station sends the MBS service to each user in unicast mode. For example, when there are few users receiving MBS service in the cell, the unicast mode is used. Sending MBS service to each user can effectively improve service transmission efficiency.
  • a shared GTP tunnel (Shared GTP tunnel) may be used between the 5G core network (5G Core network, 5GC) and the gNB.
  • the transmission of the MBS service that is, the MBS service in the unicast mode or the MBS service in the multicast mode, all share the GTP tunnel.
  • the gNB delivers MBS services to a multicast group in a multicast (multicast) manner, and delivers MBS services to a certain UE in a unicast (unicast) manner (UE3 is taken as an example in FIG. 2 ).
  • the multicast group includes one or more UEs (in FIG. 2 , the multicast group includes UE1 and UE2 as an example).
  • the current feedback mechanism has the following problems: if a MBS service data is received by multiple users, only one user receives the data incorrectly, and multicast retransmission of the MBS service data is redundant for other users and consumes electricity of. For example, if there are 10 users receiving an MBS service data, and only one user receives the wrong data, if the MBS service data is retransmitted in a multicast mode, it is redundant and expensive for the other 9 users. electrical. Therefore, how to perform efficient retransmission is a problem that needs to be solved.
  • FIG. 3 is a schematic flowchart 1 of an MBS service transmission method provided by an embodiment of the present application. As shown in FIG. 3 , the MBS service transmission method includes the following steps:
  • Step 301 The terminal device receives the first MBS service data sent by the network device in a multicast manner.
  • the network device sends the first MBS service data in a multicast manner, and correspondingly, the terminal device receives the first MBS service data sent by the network device in a multicast manner.
  • the network device may be a base station, such as a gNB.
  • the network device sends first configuration information to the terminal device, and accordingly, the terminal device receives the first configuration information sent by the network device, where the first configuration information includes at least one of the following one:
  • first indication information where 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 indication information is used to instruct the terminal device to receive retransmission data of the MBS service data in a unicast manner
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in the multicast mode shares the HARQ process with the MBS service data transmitted in the unicast mode;
  • the fourth indication information is used to indicate whether the HARQ process identification corresponding to the MBS service and the HARQ process identification corresponding to the unicast service use the same numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the network device sends second configuration information to the terminal device, and accordingly, the terminal device receives the second configuration information sent by the network device, the second configuration information
  • M is a positive integer.
  • the HARQ process number of each HARQ process in the M HARQ processes is configured by the second configuration information; or, the HARQ process number of each HARQ process in the M HARQ processes is determined by the Calculated by the terminal equipment.
  • Step 302 The terminal device sends first NACK information to the network device, where the first NACK information is used to indicate that the terminal device receives the first MBS service data in error.
  • the terminal device if the terminal device receives the first MBS service data in error, the terminal device sends the first NACK information to the network device, and accordingly, the network device receives the first NACK information sent by the terminal device, The first NACK information is used to indicate that an error occurs when the terminal device receives the first MBS service data.
  • Step 303 The terminal device receives the retransmission data of the first MBS service data sent by the network device in a unicast manner.
  • the network device 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 accordingly, The terminal device receives retransmission data of the first MBS service data sent by the network device in a unicast manner.
  • the first MBS service data transmitted in a multicast manner is scheduled by a first DCI, and the first DCI carries a first HARQ process number; the first MBS service data transmitted in a unicast manner The retransmitted data is scheduled through the second DCI, and the second DCI carries the first HARQ process ID.
  • the first HARQ process number is used to identify the first HARQ process, that is, the first MBS service data transmitted in the multicast mode and the retransmission data of the first MBS service data transmitted in the unicast mode share the first HARQ process.
  • the first HARQ process number is used to identify the first HARQ process, that is, the first MBS service data transmitted in the multicast mode and the retransmission data of the first MBS service data transmitted in the unicast mode share the first HARQ process.
  • the terminal device performs soft combining of the received first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number.
  • the terminal device softly combines the MBS service data corresponding to the same HARQ process (that is, the first HARQ process) at the physical layer, because the first MBS service data in unicast mode and the first MBS service data in multicast mode
  • the retransmission data of the service data corresponds to the same HARQ process (ie, the first HARQ process). Therefore, the terminal device performs soft combining of the received first MBS service data and the retransmission data of the first MBS service data.
  • the network device sends the second MBS service data in a multicast manner, and accordingly, the terminal device receives the 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, where the third DCI carries the first HARQ process number.
  • the second MBS service data and the first MBS service data are different data.
  • the first HARQ process ID is used to identify the first HARQ process, that is, the second MBS service data transmitted in the multicast mode and the retransmission data of the first MBS service data transmitted in the unicast mode also share the first HARQ process.
  • HARQ process there are the following two embodiments.
  • the terminal device In the case that the terminal device receives the retransmission data of the first MBS service data in error, and also receives the second MBS service data in error, the terminal device sends the second NACK information to the network device, and the corresponding The network device receives the second NACK information sent by the terminal device, and the second NACK information is used to indicate that the terminal device receives the second MBS service data in error; The network device sends the retransmission data of the second MBS service data, and correspondingly, the terminal device receives the retransmission data of the second MBS service data sent by the network device in a unicast manner.
  • the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, where the fourth DCI carries the first HARQ process number.
  • the terminal device when the terminal device receives the retransmission data of the first MBS service data in error, and also receives the second MBS service data in error, the terminal device ignores the retransmission of the first MBS service data.
  • the HARQ feedback of the retransmitted data or the terminal device assumes that the retransmitted data of the first MBS service data is correctly received and thus does not perform HARQ feedback on it.
  • the terminal device sends second NACK information to the network device, where the second NACK information is used to indicate that there is an error in receiving the second MBS service data by the terminal device, and the terminal device receives the information sent by the network device in a unicast manner. Retransmission data of the second MBS service data.
  • the first MBS service data transmitted in the multicast mode is scheduled by the first DCI, and the first DCI carries the first HARQ process number; the retransmission data of the first MBS service data transmitted in the unicast mode is scheduled by the first DCI.
  • Second DCI scheduling where the second DCI carries the first HARQ process ID. Further, the first DCI and/or the second DCI also carry a first sequence number, where the first sequence number is used to identify the first MBS service data.
  • retransmission data of the first MBS service data transmitted in a unicast manner is scheduled by a fifth DCI, where the fifth DCI carries the first HARQ process number and the first sequence number.
  • the first HARQ process number is used to identify the first HARQ process, that is, the first MBS service data transmitted in a multicast manner, the retransmission data of the first MBS service data transmitted in a unicast manner, and subsequent The data retransmitted again all share the first HARQ process.
  • the second MBS service data transmitted in a multicast manner is scheduled by a third DCI, where the third DCI carries the first HARQ process number and a second sequence number, and the second sequence number is used to identify the first HARQ process number.
  • Two MBS service data; wherein, the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, and the fourth DCI carries the first HARQ process number and the second sequence number .
  • the first HARQ process number is used to identify the first HARQ process, that is, the second MBS service data transmitted in a multicast manner and the retransmission data of the second MBS service data transmitted in a unicast manner share the first HARQ process.
  • the first HARQ process number is used to identify the first HARQ process, that is, the second MBS service data transmitted in a multicast manner and the retransmission data of the second MBS service data transmitted in a unicast manner share the first HARQ process.
  • the prerequisite for soft combining is to perform soft combining on the MBS service data in the same HARQ process.
  • the first MBS service data and the second MBS service data need to be distinguished, and the first MBS service data and the second MBS service data can be distinguished by the serial number.
  • the first MBS service data passes through The first sequence number is identified, and the second MBS service data is identified by the second sequence number.
  • the terminal device retransmits the received retransmission data of the first MBS service data and the first MBS service data again Perform soft combining of data; the terminal device performs soft combining 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. merge.
  • the MAC entity on the base station side copies each MAC PDU (that is, one TB data or one MBS service data) to one PHY entity, and the original MAC PDU is sent to another PHY entity.
  • One of the two PHY entities transmits the MBS service data in a multicast manner, and the other PHY entity transmits the MBS service data in a unicast manner.
  • the base station sends MBS service data through multicast, and the MBS service data is scheduled through DCI scrambled by G-RNTI, and the DCI carries the HARQ process identifier k.
  • the UE fails to receive the MBS service data, and feeds back NACK information to the base station. 3.
  • the base station retransmits the MBS service data in a unicast manner, and the retransmitted MBS service data is scheduled by the DCI scrambled by the C-RNTI, and the DCI carries the HARQ process identifier k.
  • the UE enters the RRC connected state to receive the MBS service, and the network device configures the UE with at least one of the following indication information:
  • the first indication information is used to indicate whether the UE can receive MBS service data in a multicast manner and MBS service data in a unicast manner at the same time;
  • the second indication information is used to instruct the UE to receive retransmission data of the MBS service data in a unicast manner, where the MBS service data refers to the MBS service data that has not been correctly received before;
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in the multicast mode shares the HARQ process with the MBS service data transmitted in the unicast mode;
  • 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 numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the UE is allowed to feed back the HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the UE determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the UE receives the MBS service data in the multicast mode, and the HARQ feedback of the MBS service data is NACK.
  • the network device sends the retransmission data of the MBS service data in a unicast manner for the user who feeds back the NACK.
  • the network device takes out or copies a copy of the MBS service data corresponding to the NACK feedback in the memory of the multicast mode, and performs scheduling and repeated transmission according to unicast.
  • the UE receives the retransmission data of the MBS service data according to the unicast mode, and the UE transmits the DCI according to the HARQ process identifier in the multicast DCI (ie the G-RNTI scrambled DCI) and the unicast DCI (ie the C-RNTI scrambled DCI).
  • the HARQ process identifier in the DCI is determined, and the unicast transmission corresponds to the repeated transmission of the multicast transmission, so that the MBS service data in the multicast mode and the retransmission data in the unicast mode can be softly combined, thereby improving the decoding success rate.
  • the network device can configure the number of multicast HARQ processes. Further, the network device may also configure the HARQ process identifier of each HARQ process, or the UE may calculate the HARQ process identifier of the multicast HARQ process according to certain rules (eg, according to some scheduling information).
  • the network device can stay for a period of time before sending new MBS service data, or directly send new MBS service data after receiving HARQ feedback (without waiting for successful retransmission).
  • the period of time may be a length of a period of time specified by the protocol.
  • the UE feeds back NACK after receiving an error in the MBS service data through multicast.
  • the HARQ process identifier of the MBS service data is identifier 1, and then the UE only receives the MBS service data corresponding to the identifier 1 through unicast. , and softly combine the received MBS service data (that is, the retransmission data of the MBS service data with the error before) and the MBS service data with the error before, and decode the softly combined data.
  • FIG. 5 is a schematic flow diagram 3 of an MBS service transmission method provided by an embodiment of the present application. As shown in FIG. 5 , the MBS service transmission method includes the following steps:
  • 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.
  • the network device may simultaneously send the first MBS service data in a multicast manner and send the first MBS service data to a specific terminal device in a unicast manner.
  • the network device may be a base station, such as a gNB.
  • the network device sends first configuration information to the terminal device, and accordingly, the terminal device receives the first configuration information sent by the network device, where the first configuration information includes at least one of the following one:
  • first indication information where 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 indication information is used to instruct the terminal device to receive retransmission data of the MBS service data in a unicast manner
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in the multicast mode shares the HARQ process with the MBS service data transmitted in the unicast mode;
  • 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 numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the first MBS service data transmitted in a multicast manner is scheduled by a first DCI, and the first DCI carries a first HARQ process number; the first MBS service data transmitted in a unicast manner Through the second DCI scheduling, the second DCI carries the second HARQ process number.
  • the terminal device determines a first HARQ process based on the first HARQ process number and the G-RNTI that scrambled the first DCI, and determines the first HARQ process based on the second HARQ process number and the C-RNTI that scrambled the first DCI
  • the RNTI determines the second HARQ process; if the first HARQ process and the second HARQ process have an associated relationship, the terminal device will use the first MBS service data received through the first HARQ process and the The first MBS service data received by the second HARQ process is soft combined.
  • the HARQ process ID corresponding to the MBS service in the multicast mode and the HARQ process ID corresponding to the MBS service in the unicast mode use the same number space, and there may be a HARQ process ID in the multicast mode and the HARQ process ID in the unicast mode.
  • one HARQ process can be uniquely determined by combining the RNTI with the HARQ process identifier.
  • the terminal device determines a first HARQ process based on the first HARQ process number, and determines 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 performs soft combining of the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process.
  • the HARQ process identifier corresponding to the MBS service in the multicast mode and the HARQ process identifier corresponding to the MBS service in the unicast mode use independent numbering spaces, and the independent numbering space can ensure the numbering space in the multicast mode and the numbering space in the unicast mode.
  • a HARQ process can be uniquely determined directly according to the HARQ process identifier.
  • FIG. 6 shows that the SDAP entity replicates the MBS service data and transmits it through two channels, one of which is delivered by multicast, and the other delivered by unicast.
  • Figure 7 shows that the PDCP entity replicates the MBS service data and transmits it through two channels, one of which is delivered by multicast, and the other delivered by unicast.
  • the network device may configure some indication information to the UE, for example, one indication information is used to indicate that the UE can receive the unicast MBS service and the multicast MBS service at the same time. For example, an indication information is used to indicate that the UE does not need to feed back the HARQ feedback corresponding to the multicast mode. For example, an indication message is used to indicate that new MBS service data is delivered in unicast mode instead of retransmission data.
  • the HARQ processes configured on the network side for unicast and multicast are independent, or the HARQ processes configured on the network side for unicast and multicast are shared.
  • the UE receives the MBS service data in the multicast mode with an error, and successfully receives the MBS service data in the unicast mode, and softly combines the MBS service data in the multicast mode and the MBS service data in the unicast mode at the physical layer, thereby Improve decoding efficiency.
  • the prerequisite for soft combining is that the MBS service data in the multicast mode and the MBS service data in the unicast mode are the same MBS service data.
  • whether the MBS service data in the multicast mode and the MBS service data in the unicast mode are the same MBS service data may be determined according to the HARQ process number.
  • whether the MBS service data in the multicast mode and the MBS service data in the unicast mode are the same MBS service data can be determined through the HARQ process number and the RNTI.
  • FIG. 8 is a schematic structural diagram 1 of an MBS service transmission apparatus provided by an embodiment of the present application, which is applied to a terminal device.
  • the MBS service transmission apparatus includes:
  • a receiving unit 801 configured to receive first MBS service data sent by a network device in a multicast manner
  • a sending unit 802 configured to send first NACK information to the network device, where the first NACK information is used to instruct the terminal device to receive the first MBS service data in error;
  • 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.
  • the receiving unit 801 is further configured to receive first configuration information sent by the network device, where the first configuration information includes at least one of the following:
  • first indication information where 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 indication information is used to instruct the terminal device to receive retransmission data of the MBS service data in a unicast manner
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in a multicast manner and the MBS service data transmitted in a unicast manner share a hybrid automatic repeat request 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 numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the first MBS service data transmitted in a multicast manner is scheduled by first downlink control information DCI, and the first DCI carries a first HARQ process number;
  • the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled by a second DCI, and the second DCI carries the first HARQ process number.
  • the device further includes:
  • a processing unit (not shown in the figure), configured to perform soft combining of the received first MBS service data and the retransmission data of the first MBS service data based on the first HARQ process number.
  • the receiving unit 801 is further configured to receive second MBS service data sent by the network device in a multicast manner, and the second MBS service data transmitted in a multicast manner passes through a third DCI scheduling, the third DCI carries the first HARQ process number;
  • the sending unit 802 is further configured to send the first MBS service data to the network device when the receiving unit receives an error in the retransmission data of the first MBS service data and also receives an error in the second MBS service data.
  • Two NACK information, the second NACK information is used to indicate that the terminal device receives an error in the second MBS service data;
  • 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.
  • the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, and the fourth DCI carries the first HARQ process number.
  • the first DCI and/or the second DCI further carry a first sequence number, and the first sequence number is used to identify the first MBS service data.
  • the receiving unit 801 is further configured to receive second MBS service data sent by the network device in a multicast manner, and the second MBS service data transmitted in a multicast manner passes through a third DCI scheduling, the third DCI carries the first HARQ process number and a second sequence number, where the second sequence number is used to identify the second MBS service data;
  • the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, and the fourth DCI carries the first HARQ process number and the second sequence number.
  • the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled by a fifth DCI, and the fifth DCI carries the first HARQ process number and the first sequence No.
  • the device further includes:
  • a processing unit configured to perform the received 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.
  • Soft combining based on the first HARQ process number and the second sequence number, soft combining the received second MBS service data and the retransmission data of the second MBS service data.
  • the receiving unit 801 is further configured to receive second configuration information sent by the network device, where the second configuration information is used to determine that there are M HARQ processes in the transmission corresponding to the multicast mode, and M is a positive integer.
  • the HARQ process number of each HARQ process in the M HARQ processes is configured through the second configuration information; or,
  • the HARQ process number of each HARQ process in the M HARQ processes is calculated by the terminal device.
  • FIG. 9 is a schematic diagram 2 of the structure and composition of an MBS service transmission apparatus provided by an embodiment of the present application, which is applied to terminal equipment.
  • the MBS service transmission apparatus includes:
  • the receiving unit 901 is configured to receive first MBS service data sent by a network device in a multicast manner and the first MBS service data sent in a unicast manner.
  • the receiving unit 901 is further configured to receive first configuration information sent by the network device, where the first configuration information includes at least one of the following:
  • first indication information where 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 indication information is used to instruct the terminal device to receive retransmission data of the MBS service data in a unicast manner
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in the multicast mode shares the HARQ process with the MBS service data transmitted in the unicast mode;
  • 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 numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the first MBS service data transmitted in a multicast manner is scheduled by a first DCI, and the first DCI carries a first HARQ process number;
  • the first MBS service data transmitted in a unicast manner is scheduled through a second DCI, where the second DCI carries a second HARQ process number.
  • the device further includes:
  • a processing unit 902 configured to determine a first HARQ process based on the first HARQ process number and the G-RNTI that scrambled the first DCI, and determine a first HARQ process based on the second HARQ process number and the G-RNTI that scrambled the first DCI;
  • the C-RNTI determines the second HARQ process; 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 The first MBS service data received by the second HARQ process is soft combined.
  • the HARQ process identifier corresponding to the MBS service in the multicast mode and the HARQ process identifier corresponding to the MBS service in the unicast mode use the same numbering space.
  • the device further includes:
  • a processing unit 902 configured to determine a first HARQ process based on the first HARQ process number, and determine a second HARQ process based on the second HARQ process number; if the first HARQ process and the second HARQ process have If the association relationship is established, the first MBS service data received through the first HARQ process and the first MBS service data received through the second HARQ process are softly combined.
  • the HARQ process identifier corresponding to the MBS service in the multicast mode and the HARQ process identifier corresponding to the MBS service in the unicast mode use independent numbering spaces.
  • FIG. 10 is a schematic diagram 3 of the structure and composition of the MBS service transmission apparatus provided by the embodiment of the present application, which is applied to network equipment.
  • the MBS service transmission apparatus includes:
  • a sending unit 1001 configured to send the first MBS service data in a multicast manner
  • a receiving unit 1002 configured to receive first NACK information sent by a terminal device, where the first NACK information is used to indicate that an error occurs when the terminal device receives the first MBS service data;
  • the sending unit 1001 is further configured to send the retransmission data of the first MBS service data to the terminal device in a unicast manner.
  • the sending unit 1001 is further configured to send first configuration information to the terminal device, where the first configuration information includes at least one of the following:
  • first indication information where 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 indication information is used to instruct the terminal device to receive retransmission data of the MBS service data in a unicast manner
  • third indication information where the third indication information is used to indicate that the MBS service data transmitted in the multicast mode shares the HARQ process with the MBS service data transmitted in the unicast mode;
  • 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 numbering space or an independent numbering space;
  • the fifth indication information is used to indicate whether the terminal device is allowed to feed back HARQ feedback information corresponding to the MBS service data in the multicast mode;
  • sixth indication information is used to indicate whether the terminal device determines the HARQ process based on the HARQ process identifier, or determines the HARQ process based on the HARQ process identifier and the RNTI.
  • the first MBS service data transmitted in a multicast manner is scheduled by a first DCI, and the first DCI carries a first HARQ process number;
  • the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled by a second DCI, and the second DCI carries the first HARQ process number.
  • the sending unit 1001 is further configured to send the second MBS service data in a multicast manner, and 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;
  • the receiving unit 1002 is further configured to receive the second NACK information sent by the terminal device, where the second NACK information is used to instruct the terminal device to receive the second MBS service data error;
  • the sending unit 1001 is further configured to send the retransmission data of the second MBS service data to the network device in a unicast manner.
  • the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, and the fourth DCI carries the first HARQ process number.
  • the first DCI and/or the second DCI further carry a first sequence number, and the first sequence number is used to identify the first MBS service data.
  • the sending unit 1001 is further configured to send the second MBS service data in a multicast manner, and 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 and a second sequence number, where the second sequence number is used to identify the second MBS service data;
  • the retransmission data of the second MBS service data transmitted in a unicast manner is scheduled by a fourth DCI, and the fourth DCI carries the first HARQ process number and the second sequence number.
  • the retransmission data of the first MBS service data transmitted in a unicast manner is scheduled by a fifth DCI, and the fifth DCI carries the first HARQ process number and the first sequence No.
  • the sending unit 1001 is further configured to send second configuration information to the terminal device, where the second configuration information is used to determine that there are M HARQ processes in the transmission corresponding to the multicast mode, where M is: positive integer.
  • the HARQ process number of each HARQ process in the M HARQ processes is configured through the second configuration information; or,
  • the HARQ process number of each HARQ process in the M HARQ processes is calculated by the terminal device.
  • FIG. 11 is a schematic structural diagram of a communication device 1100 provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 1100 shown in FIG. 11 includes a processor 1110, and the processor 1110 can call and run a computer program from a memory to implement the methods in the embodiments of the present application.
  • the communication device 1100 may further include a memory 1120 .
  • the processor 1110 may call and run a computer program from the memory 1120 to implement the methods in the embodiments of the present application.
  • the memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.
  • the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the processor 1110 may control the transceiver 1130 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 1130 may include a transmitter and a receiver.
  • the transceiver 1130 may further include an antenna, and the number of the antenna may be one or more.
  • the communication device 1100 may specifically be a network device in this embodiment of the present application, and the communication device 1100 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 1100 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 1100 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and will not be repeated here.
  • FIG. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 1200 shown in FIG. 12 includes a processor 1210, and the processor 1210 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 1200 may further include a memory 1220 .
  • the processor 1210 may call and run a computer program from the memory 1220 to implement the methods in the embodiments of the present application.
  • the memory 1220 may be a separate device independent of the processor 1210, or may be integrated in the processor 1210.
  • the chip 1200 may further include an input interface 1230 .
  • the processor 1210 may control the input interface 1230 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 1200 may further include an output interface 1240 .
  • the processor 1210 may control the output interface 1240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • FIG. 13 is a schematic block diagram of a communication system 1300 provided by an embodiment of the present application. As shown in FIG. 13 , the communication system 1300 includes a terminal device 1310 and a network device 1320 .
  • the terminal device 1310 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 1320 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program runs on the computer, the computer executes the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de transmission de service MBS, ainsi qu'un dispositif terminal et un dispositif réseau Le procédé comprend les étapes suivantes : un dispositif terminal reçoit des premières données de service MBS envoyées par un dispositif réseau en multidiffusion ; le dispositif terminal envoie des premières informations d'accusé de réception négatif (NACK) au dispositif réseau, les premières informations NACK servant à indiquer qu'une erreur s'est produite lors de la réception des premières données de service MBS par le dispositif terminal ; le dispositif terminal reçoit les données retransmises des premières données de service MBS envoyées par le dispositif réseau en monodiffusion.
PCT/CN2020/106387 2020-07-31 2020-07-31 Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau WO2022021410A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2020/106387 WO2022021410A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau
CN202310507829.XA CN116566551A (zh) 2020-07-31 2020-07-31 一种mbs业务传输方法及装置、终端设备、网络设备
CN202080101107.9A CN115668829A (zh) 2020-07-31 2020-07-31 一种mbs业务传输方法及装置、终端设备、网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/106387 WO2022021410A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau

Publications (1)

Publication Number Publication Date
WO2022021410A1 true WO2022021410A1 (fr) 2022-02-03

Family

ID=80036992

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/106387 WO2022021410A1 (fr) 2020-07-31 2020-07-31 Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau

Country Status (2)

Country Link
CN (2) CN115668829A (fr)
WO (1) WO2022021410A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007148138A1 (fr) * 2006-06-23 2007-12-27 Siemens Aktiengesellschaft Retransmission de paquets
CN101771939A (zh) * 2008-12-30 2010-07-07 中兴通讯股份有限公司 单播业务控制信息的发送方法和装置
CN102067499B (zh) * 2008-08-22 2013-12-25 上海贝尔股份有限公司 利用单播链路来实现harq重传的方法和系统
CN104105072A (zh) * 2014-07-30 2014-10-15 宇龙计算机通信科技(深圳)有限公司 混合多播方法和混合多播系统
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品
CN110381538A (zh) * 2019-06-21 2019-10-25 上海交通大学 广播网络和蜂窝网络协同传输方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007148138A1 (fr) * 2006-06-23 2007-12-27 Siemens Aktiengesellschaft Retransmission de paquets
CN102067499B (zh) * 2008-08-22 2013-12-25 上海贝尔股份有限公司 利用单播链路来实现harq重传的方法和系统
CN101771939A (zh) * 2008-12-30 2010-07-07 中兴通讯股份有限公司 单播业务控制信息的发送方法和装置
CN104105072A (zh) * 2014-07-30 2014-10-15 宇龙计算机通信科技(深圳)有限公司 混合多播方法和混合多播系统
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品
CN110381538A (zh) * 2019-06-21 2019-10-25 上海交通大学 广播网络和蜂窝网络协同传输方法及系统

Also Published As

Publication number Publication date
CN116566551A (zh) 2023-08-08
CN115668829A (zh) 2023-01-31

Similar Documents

Publication Publication Date Title
WO2021056152A1 (fr) Appareil et procédé de configuration d'informations, dispositif terminal et dispositif réseau
US11949598B2 (en) Window adjustment method and apparatus, network device, terminal device
WO2021134298A1 (fr) Procédé et dispositif d'indication de ressources et appareil de communication
CN113678500B (zh) 一种反馈资源配置方法及通信方法、装置、通信设备
WO2021051320A1 (fr) Procédé et appareil de transmission de données de service, dispositif de réseau et dispositif terminal
WO2022006849A1 (fr) Procédé et appareil de gestion d'état tci de service mbs et dispositif terminal
WO2022155978A1 (fr) Procédé et appareil de configuration de service mbs, dispositif terminal et dispositif de réseau
WO2022120837A1 (fr) Procédé et appareil de planification semi-persistante pour un service mbs, dispositif terminal et dispositif réseau
WO2022141545A1 (fr) Procédé et appareil de transmission de planification de mcch, et dispositif terminal
WO2022141088A1 (fr) Procédé et appareil d'émission de service mbs et dispositif terminal
WO2022021410A1 (fr) Procédé et appareil de transmission de service mbs, dispositif terminal et dispositif réseau
WO2021051321A1 (fr) Procédé et appareil de transmission de données de service et dispositif terminal
WO2021051322A1 (fr) Procédé et appareil de configuration de bwp, dispositif terminal et dispositif de réseau
WO2022087990A1 (fr) Procédé et appareil de retransmission de service de multidiffusion, dispositif de terminal et dispositif de réseau
WO2022198415A1 (fr) Procédé et appareil pour améliorer la fiabilité d'un mbs, dispositif terminal et dispositif de réseau
WO2022006888A1 (fr) Procédé et appareil de réception de service mbs et dispositif terminal
WO2022165720A1 (fr) Procédé et appareil pour améliorer la fiabilité d'un service mbs, dispositif de terminal et dispositif de réseau
WO2023097665A1 (fr) Procédé et appareil de réception de données, et dispositif terminal
WO2023097601A1 (fr) Procédé et appareil d'exploitation de temporisateur drx, et dispositif terminal
WO2023102898A1 (fr) Procédé et appareil de détermination de mode de retransmission, et procédé et appareil de commande de temporisateur
WO2022006882A1 (fr) Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal
WO2023102833A1 (fr) Procédé et appareil d'indication d'état de rétroaction, dispositif terminal, et dispositif de réseau
WO2023097613A1 (fr) Procédé et appareil de détermination d'informations, et dispositif terminal
WO2022120749A1 (fr) Procédé et appareil de planification de services de multidiffusion, dispositif terminal et dispositif de réseau
WO2022056859A1 (fr) Procédé et appareil de commande de progression de transmission de mbs et dispositif de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20947048

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20947048

Country of ref document: EP

Kind code of ref document: A1