Communication method and communication apparatus
By determining the transport block and coding block buffer sizes for the multicast service channel and employing rate matching technology, the problem of large MBMS data buffer usage was solved, thereby improving the processing capability and receiving performance of terminal equipment.
Patent Information
- Application Number
- PCT/CN2026/093235
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-27
- Publication Date
- 2026-11-12
AI Technical Summary
In LTE cellular communication systems, MBMS data is transmitted using full coded blocks, resulting in a large buffer footprint. Existing technologies struggle to effectively reduce the coded block size of multicast service channels.
By receiving the first information, the buffer size corresponding to the transport block and coding block of the multicast service channel is determined. Rate matching technology is used to reduce the coding block size and reduce the buffer size.
It enables the determination of the multicast service channel coding block size and the optimization of the buffer amount, thereby improving the processing capability and receiving performance of terminal equipment.
Smart Images

Figure CN2026093235_12112026_PF_FP_ABST
Abstract
Description
A communication method and apparatus
[0001] Cross-references to related applications
[0002] This application claims priority to Chinese Patent Application No. 202510599763.0, filed on May 9, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of wireless communication technology, and in particular to a communication method and apparatus. Background Technology
[0004] To effectively utilize mobile network resources, the 3rd Generation Partnership Project (3GPP) proposed Multimedia Broadcast Multicast Service (MBMS), which aims to enable the broadcast and multicast of multimedia content through point-to-multipoint transmission. MBMS allows for network resource sharing, helping to improve the utilization rate of network resources (such as air interface resources).
[0005] In Long Term Evolution (LTE) cellular communication systems, MBMS can be implemented through either MBMS-unicast hybrid cells or dedicated MBMS cells. In MBMS-unicast hybrid cells, MBMS shares frequency resources with non-MBMS cells. In dedicated MBMS cells, MBMS has its own dedicated frequency resources. Multiple MBMS cells can form a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) area. Within the same MBSFN area, base stations broadcast the same MBMS transport block (or MBMS data). The MBMS transport block (or simply transport block) can be transmitted via a multicast traffic channel (MTCH) using the MBSFN method. The basic scheduling unit in LTE cellular communication systems is the transmission time interval (TTI), which can be a subframe or a time slot. When a transport block (TB) is transmitted at the physical layer, it is mapped onto a physical multicast channel (PMCH), and the PMCH is transmitted only within an MBSFN subframe. An MBSFN subframe can be a complete subframe or a portion of orthogonal frequency division multiplexing (OFDM) symbols within a subframe.
[0006] Currently, MBMS data uses full buffer rate matching (or full coded block transmission), which results in large coded blocks and a large amount of buffer space required. Summary of the Invention
[0007] This application provides a communication method and apparatus to reduce the size of the coding block of a multicast service channel, thereby reducing the amount of buffer space occupied.
[0008] Firstly, a communication method is provided, which can be applied to a second communication device. The second communication device can be a terminal device (e.g., a UE), or a module applied to the terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a system-on-chip (SoC) or system-in-a-package (SIP) chip containing a modem core), a chip system, or a processor, etc.), or a logical node, logical module, or software capable of implementing all or part of the terminal device's functions, or a combination of hardware and software. The method includes: receiving first information; determining, based on the first information, the buffer size corresponding to a transport block of a multicast service channel; determining, based on the buffer size corresponding to a transport block of the multicast service channel, the buffer size corresponding to a coding block of the multicast service channel; and receiving the multicast service channel based on the buffer size corresponding to a coding block of the multicast service channel.
[0009] The above implementation, for multicast services, determines the buffer size corresponding to the coding block of the multicast service channel. When transmitting the multicast service channel, rate matching can be performed based on the buffer size corresponding to the coding block. Similarly, at the receiving end, rate matching can be performed based on the buffer size corresponding to the coding block. Compared to the traditional multicast service data processing that uses full buffer rate matching, the above implementation can reduce the size of the coding block, thereby reducing the amount of buffer space required.
[0010] In one possible implementation, the first information includes terminal device type information or the buffer size corresponding to a transport block of the multicast service channel.
[0011] In one possible implementation, the terminal device type information contained in the first information sent by the network to multiple terminal devices used to receive the multicast service channel is the same.
[0012] Based on the above implementation, the first communication device can send first information to multiple second communication devices that receive multicast service channels. The first information sent by the first communication device to different second communication devices contains the same terminal device type information. That is, although the types of terminal devices receiving multicast service channels may vary, the terminal device type information sent by the network device to these terminal devices is the same. This ensures that the "total number of soft channel bits" determined by these terminal devices is the same, thereby determining the same buffer size for a transport block and the same buffer size for a coding block of the multicast service channel. This ensures that the terminal side and the network side have a consistent understanding of the transport block (or coding block) size, guaranteeing correct reception of the multicast service channel by the terminal side.
[0013] In one possible implementation, determining the buffer size corresponding to a transport block of the multicast service channel based on the first information includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; and determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits.
[0014] In one possible implementation, determining the buffer size corresponding to a transport block of the multicast service channel based on the first information includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits and at least one of a first scaling factor and the number of carriers; wherein the first scaling factor is greater than 0 and less than or equal to 1, and the number of carriers is the number of carriers used to carry the multicast service channel.
[0015] In one possible implementation, the buffer size corresponding to a transport block of the multicast service channel satisfies the following formula:
[0016] in, The buffer size corresponding to one transport block of the multicast service channel. The number of soft channel bits corresponding to the terminal device type information, where β is the first scaling factor. The number of carriers; This indicates rounding down, where x is a real number.
[0017] In one possible implementation, the first information further includes at least one of the first scaling factor and the number of carriers.
[0018] In one possible implementation, a transport block of the multicast service channel is transmitted over multiple non-contiguous time units in the time domain; determining the buffer size corresponding to a transport block of the multicast service channel based on the first information includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits and the time interval; wherein the time interval indicates the interval between two adjacent time units in the multiple non-contiguous time units.
[0019] In one possible implementation, the buffer size corresponding to a transport block of the multicast service channel satisfies the following formula:
[0020] in, The buffer size corresponding to one transport block of the multicast service channel. M represents the number of soft channel bits corresponding to the terminal device type information, and M represents the time interval. This indicates rounding down, where x is a real number.
[0021] In one possible implementation, the buffer size corresponding to a transport block of the multicast service channel satisfies the following formula:
[0022] in, The buffer size corresponding to one transport block of the multicast service channel. The number of soft channel bits corresponding to the terminal device type information, M is the time interval, and β is the first scaling factor. The number of carriers; This indicates rounding down, where x is a real number.
[0023] In one possible implementation, the buffer size corresponding to a transport block of the multicast service channel satisfies the following formula:
[0024] in, The buffer size corresponding to one transport block of the multicast service channel. The number of soft channel bits corresponding to the terminal device type information, M is the time interval, and β is the first scaling factor; This indicates rounding down, where x is a real number.
[0025] In one possible implementation, a transport block of the multicast service channel is transmitted over multiple non-contiguous time units in the time domain; the first information includes the number of time units and time interval information, wherein the number of time units indicates the number of the multiple non-contiguous time units, and the time interval information indicates the interval between two adjacent time units in the multiple non-contiguous time units.
[0026] One possible implementation further includes: determining a first value as one of a plurality of maximum bit counts for a transport block of the multicast service channel based on the terminal device type information, wherein the first value is used to determine the maximum bit count for a transport block of the multicast service channel.
[0027] In one possible implementation, the first value is the maximum or minimum value among the plurality of maximum bit numbers, or the first value is determined based on the configuration information of the network device.
[0028] One possible implementation further includes: receiving second information; and determining the buffer size corresponding to a transport block of the downlink shared channel based on the second information.
[0029] In the above implementation, when the first communication device schedules the downlink shared channel and the multicast service channel, the first communication device can send second information to the second communication device so that the second communication device can determine the buffer size corresponding to the transport block of the downlink shared channel, so as to receive the downlink shared channel and the multicast service channel as much as possible.
[0030] In one possible implementation, the buffer size corresponding to a transport block of the downlink shared channel satisfies the following formula:
[0031] Where, N IR N is the buffer size corresponding to one transport block of the downlink shared channel; soft The number of soft channel bits determined based on the type of terminal device; K C The total cache size is related to the type of terminal device; K MIMO Related to the transmission mode of the downlink shared channel, its value is 1 or 2; M DL_HARQ M represents the maximum number of downlink hybrid automatic repeat request processes on the downlink shared channel. limit It is a fixed value; α is related to the transmission time interval of the downlink shared channel, and can take values of 1, 0.5, or 1 / 6, etc. The function `min()` rounds down to the nearest integer, where x is a real number; `min()` takes the minimum value.
[0032] In the above implementation, the buffer size corresponding to a transport block of the downlink shared channel can be reduced by a second proportional factor based on the value calculated by the existing method, so as to appropriately reduce the buffer size corresponding to a transport block of the downlink shared channel, thereby reducing the buffer size corresponding to a coding block of the downlink shared channel, so as to enable the downlink shared channel and the multicast service channel to share the processing capabilities of the terminal equipment as much as possible.
[0033] In one possible implementation, the buffer size corresponding to a transport block of the downlink shared channel satisfies the following formula:
[0034] Where, N IR N is the buffer size corresponding to one transport block of the downlink shared channel; soft The number of soft channel bits is determined based on the type of terminal device; K represents the number of soft channel bits corresponding to the terminal type information sent by the network device. C The total cache size is related to the type of terminal device; K MIMO Related to the transmission mode of the downlink shared channel, its value is 1 or 2; M DL_HARQ M represents the maximum number of downlink hybrid automatic repeat request processes on the downlink shared channel. limit It is a fixed value; α is related to the transmission time interval of the downlink shared channel, and can take values of 1, 0.5, or 1 / 6, etc. The function `min()` rounds down to the nearest integer, where x is a real number; `min()` takes the minimum value.
[0035] In the above implementation, the buffer size corresponding to a transport block of the downlink shared channel can be determined by adjusting the value calculated using the existing method, through a first proportionality factor β. The second scaling factor is also adjusted downward to appropriately reduce the buffer size corresponding to a transport block of the downlink shared channel, thereby reducing the buffer size corresponding to a coding block of the downlink shared channel, so as to enable the downlink shared channel and the multicast service channel to share the processing capabilities of the terminal equipment as much as possible.
[0036] In one possible implementation, the second information includes first indication information and / or a second scaling factor; wherein the first indication information indicates the number of soft channel bits shared by the multicast service channel and the downlink shared channel, the number of soft channel bits being determined based on the type of terminal device, and the second scaling factor is greater than 0 and less than or equal to 1.
[0037] One possible implementation further includes: sending a second indication message, the second indication message indicating that the terminal device expects to receive the downlink shared channel and the multicast service channel simultaneously; or sending a third indication message, the third indication message indicating priority to receive the multicast service channel; or sending terminal device capability information, the terminal device capability information indicating that the terminal device supports determining the buffer size corresponding to a transport block of the downlink shared channel based on network configuration information.
[0038] One possible implementation further includes: determining to receive the multicast service channel, or receive the downlink shared channel, or preferentially receive the downlink shared channel, or abandon receiving the multicast service channel when one of the following conditions is met: if the multicast service channel and the downlink shared channel scheduled by the network side exceed the processing capacity of the terminal device within a scheduling time interval; or, when the terminal device is operating in multi-carrier aggregation mode, if the multicast service channel and the downlink shared channel scheduled by the network side exceed the processing capacity of the terminal within a scheduling time interval; or, if the multicast service channel and the downlink shared channel scheduled by the network side exceed the number of soft channel bits corresponding to the type of terminal device.
[0039] In one possible implementation, a transport block of the multicast service channel is transmitted in multiple non-continuous time units in the time domain.
[0040] The above implementation method can realize the interleaved transmission of transport blocks of multicast service channels in the time domain, thereby improving the reception performance of terminal equipment for multicast MBMS service channels.
[0041] In one possible implementation, receiving the multicast service channel according to the buffer size corresponding to a coding block of the multicast service channel includes: performing derate matching according to the buffer size corresponding to a coding block of the multicast service channel.
[0042] Secondly, a communication method is provided, applied to a first communication device. The first communication device can be a network device, such as an access network device (e.g., a base station). The method can be executed by the access network device, or by a module applied to the access network device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the access network device's functions, or it can be implemented through a combination of hardware and software. The method includes: sending first information, the first information being used to determine the buffer size corresponding to a transport block of a multicast service channel; determining the buffer size corresponding to a transport block of the multicast service channel; determining the buffer size corresponding to a coding block of the multicast service channel based on the buffer size corresponding to the transport block of the multicast service channel; and sending the multicast service channel based on the buffer size corresponding to the coding block of the multicast service channel.
[0043] One possible implementation further includes sending second information, which is used to determine the buffer size corresponding to a transport block of the downlink shared channel.
[0044] In one possible implementation, the second information includes first indication information and / or a second scaling factor; wherein the first indication information indicates the number of soft channel bits shared by the multicast service channel and the downlink shared channel, the number of soft channel bits being determined based on the type of terminal device, and the second scaling factor is greater than 0 and less than or equal to 1.
[0045] One possible implementation further includes: receiving second indication information, the second indication information indicating that the terminal device expects to simultaneously receive the downlink shared channel and the multicast service channel; or, receiving third indication information, the third indication information indicating priority to receive the multicast service channel; or, receiving terminal device capability information, the terminal device capability information indicating that the terminal device supports determining the buffer size corresponding to a transport block of the downlink shared channel based on network configuration information.
[0046] In one possible implementation, the first information includes terminal device type information or the buffer size corresponding to a transport block of the multicast service channel.
[0047] In one possible implementation, determining the buffer size corresponding to a transport block of the multicast service channel includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; and determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits.
[0048] In one possible implementation, determining the buffer size corresponding to a transport block of the multicast service channel based on the first information includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits and at least one of a first scaling factor and the number of carriers; wherein the first scaling factor is greater than 0 and less than or equal to 1, and the number of carriers is the number of carriers used to carry the multicast service channel.
[0049] In one possible implementation, the first information further includes at least one of the first scaling factor and the number of carriers.
[0050] In one possible implementation, a transport block of the multicast service channel is transmitted over multiple non-contiguous time units in the time domain; determining the buffer size corresponding to a transport block of the multicast service channel includes: determining the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information; determining the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits and the time interval; wherein the time interval indicates the interval between two adjacent time units in the multiple non-contiguous time units.
[0051] In one possible implementation, a transport block of the multicast service channel is transmitted over multiple non-contiguous time units in the time domain; the first information includes the number of time units and time interval information, wherein the number of time units indicates the number of the multiple non-contiguous time units, and the time interval information indicates the interval between two adjacent time units in the multiple non-contiguous time units.
[0052] One possible implementation further includes: determining a first value as one of a plurality of maximum bit counts for a transport block of the multicast service channel based on the terminal device type information, wherein the first value is used to determine the maximum bit count for a transport block of the multicast service channel.
[0053] In one possible implementation, the first value is the maximum or minimum value among the plurality of maximum bit numbers, or the first value is determined based on the configuration information of the network device.
[0054] In one possible implementation, a transport block of the multicast service channel is transmitted in multiple non-continuous time units in the time domain.
[0055] In one possible implementation, sending the multicast service channel according to the buffer size corresponding to a coding block of the multicast service channel includes: performing rate matching according to the buffer size corresponding to a coding block of the multicast service channel.
[0056] Thirdly, a communication device is provided, the communication device including a unit or module for performing the method of any one of the first aspects, or including a unit or module for performing the method of any one of the second aspects.
[0057] Fourthly, a communication device is provided, comprising: one or more processors configured to perform the method described in any one of the first aspects, or to perform the method described in any one of the second aspects.
[0058] Fifthly, a readable storage medium is provided, the readable storage medium storing a program or instructions that, when executed on a communication device, cause the communication device to perform the method described in any one of the first aspects, or to perform the method described in any one of the second aspects.
[0059] A sixth aspect provides a chip system including a processor for supporting a computer device in implementing the method described in any one of the first aspects above, or in implementing the method described in any one of the second aspects above.
[0060] In a seventh aspect, a program product is provided, the program product comprising a program; when the program is run on a computer, the computer performs the method described in any one of the first aspects above, or performs the method described in any one of the second aspects above.
[0061] Eighthly, a communication system is provided, comprising a first communication device and a second communication device, wherein the second communication device is configured to implement the method described in any one of the first aspects, and the first communication device is configured to implement the method described in any one of the second aspects. Attached Figure Description
[0062] Figure 1 is a schematic diagram of an MBSFN region provided in an embodiment of this application;
[0063] Figure 2 is a schematic diagram of a transport block processing flow in an embodiment of this application;
[0064] Figure 3 is a schematic diagram of an E-MBMS system architecture provided in an embodiment of this application;
[0065] Figure 4 is a schematic diagram of the user plane protocol stack in an E-MBMS system architecture provided in an embodiment of this application;
[0066] Figure 5 is a schematic diagram of the control plane protocol stack in an E-MBMS system architecture provided in an embodiment of this application;
[0067] Figure 6 is a schematic diagram of the control plane protocol structure of an M2 interface provided in an embodiment of this application;
[0068] Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application;
[0069] Figure 8 is a schematic diagram of a time-domain interleaving scheme for a multicast service channel transport block in an embodiment of this application;
[0070] Figure 9 is a schematic diagram of the rate matching process of a Turbo-coded transmission channel in an embodiment of this application;
[0071] Figure 10 is a schematic diagram of the communication process in a scenario where a multicast service channel and a downlink shared channel can share the number of soft channel bits, as provided in an embodiment of this application.
[0072] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0073] Figure 12 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation
[0074] Before introducing the technical solutions provided in this application, some of the terms used in this application will be explained in order to facilitate understanding by those skilled in the art.
[0075] (1) MBMS
[0076] MBMS is an important feature introduced by 3GPP in cellular communication-based systems, designed to enable the broadcasting and multicasting of multimedia content through point-to-multipoint transmission.
[0077] MBMS is a point-to-multipoint transmission service that allows network resources to be shared among multiple users, making it particularly suitable for large-scale multimedia broadcasting and multicast needs. For example, MBMS can be applied to mobile TV, advertising and promotional scenarios, and emergency notification scenarios. Specifically, in mobile TV scenarios, users can receive TV programs and enjoy multimedia content on their mobile phones via MBMS; in advertising and promotional scenarios, operators can use MBMS for large-scale advertising and promotional pushes; and in emergency notification scenarios, MBMS can quickly push information to a large number of users in emergency situations, such as disaster warnings.
[0078] (2) MBMS transmission mode
[0079] MBMS can be transmitted via MBSFN. Its frequency resources can be shared with non-MBMS services, known as MBMS / unicast hybrid cells, or dedicated frequency resources for MBMS, known as MBMS dedicated cells. Its frequency resources can be resources corresponding to one or several carriers.
[0080] An MBSFN area can include multiple cells, as shown in Figure 1. These multiple cells can be managed by one or more access network devices. For example, these multiple cells can include reserved cells and cells participating in MBMS data transmission (or participating in MBSFN transmission). Reserved cells are cells that do not participate in MBMS data transmission. Of course, reserved cells can limit their transmission power to allow transmission of other services. MBSFN transmission refers to a synchronous playback transmission method, which is achieved by transmitting from at least one cell at the same time with the same waveform.
[0081] As shown in Figure 1, an MBMS service area can include one or more MBSFN areas. Each cell that joins in transmitting MBMS data is configured with a point-to-multipoint radio resource, and all users registered for MBMS can simultaneously receive the same transmitted signal. Using MBSFN transmission for multi-cell broadcast / multicast requires tight synchronization between cells and time alignment of signals from different cells.
[0082] It is understood that cells participating in MBMS data transmission within the same MBSFN area achieve time synchronization, and these cells also use the same resources (such as time-domain resources, frequency-domain resources, etc.). It should be understood that cells participating in MBMS data transmission within the same MBSFN area send (or transmit) the same data.
[0083] (3) MBMS related channels
[0084] The logical channels used for MBMS transmission are divided into the multicast control channel (MCCH) and the multicast traffic channel (MTCH). Both MCCH and MTCH are mapped onto the multicast channel (MCH), and the MCH is further mapped onto the physical multicast channel (PMCH).
[0085] The MCCH is a point-to-multipoint downlink channel used by the network to transmit MBMS-related control information to terminal devices, as well as to calculate (counting) information for MBMS service interest. One MCCH can correspond to one or more MTCHs, and only terminal devices capable of receiving MBMS services can use that MCCH.
[0086] The MTCH is a point-to-multipoint downlink channel used by the network to transmit MBMS service data to terminal devices. Only terminal devices capable of receiving MBMS services can use the MTCH. The configuration information of the MTCH is indicated by its corresponding MCCH. The network uses the MCCH to indicate the MTCH to the terminal devices, thereby enabling the terminal devices to receive the MBMS services carried on the MTCH.
[0087] (4) Time-domain and frequency-domain resources of MBSFN
[0088] The physical channel used for MBSFN transmission is PMCH. PMCH is only transmitted within the MBSFN area. An MBSFN area can be a complete MBSFN subframe or a portion of orthogonal frequency division multiplexing (OFDM) symbols within an MBSFN. It should be noted that, in the embodiments of this application, an OFDM symbol can also be simply referred to as a symbol.
[0089] System information or other unicast data may also be transmitted on the PMCH, and the resource blocks used to transmit this information use a normal cyclic prefix. Therefore, in the time domain, the subframes contained within a radio frame can be divided into MBSFN subframes and non-MBSFN subframes.
[0090] A radio frame has a duration of 10 milliseconds and contains 10 subframes, each with a duration of 1 millisecond. Each subframe can be further divided into multiple slots, such as two slots, and each slot can include at least one symbol. During transmission, the physical layer maps each symbol to a corresponding resource element (RE). A physical resource block (PRB) is defined as a [missing information - likely a time-domain variable]... A series of consecutive symbols and continuous in the frequency domain. Number of subcarriers. Among them, the resource blocks used to transmit MBMS use an extended cyclic prefix.
[0091] The number and location of MBSFN subframes within a radio frame are configured by the network, for example, through system information, and this configuration information can be carried by the MCCH. When a terminal device needs to receive multiple MTCHs, the MCCH can carry control information for multiple MTCHs, such as the modulation scheme and code rate used. This configuration information can be sent to base stations within the MBSFN area by logical units such as the Multi-cell / multicast coordination entity (MCE) in the system architecture.
[0092] At the physical layer, the processing procedure for transport blocks of unicast channels and transport blocks of multicast channels (such as MCH or PMCH) can be as shown in Figure 2, including: adding cyclic redundancy check (CRC) to TB; segmenting the transport block into coded blocks and adding CRC to each coded block; performing channel coding; performing rate matching; and concatenating code blocks.
[0093] Currently, for unicast data, limited buffer rate matching (LBRM) is used for rate matching because the total buffer size of the terminal device is fixed. Various possibilities exist during unicast scheduling, such as the terminal device being configured to receive data on multiple carriers, data being spatially layered on each carrier, and the terminal device needing to buffer multiple transport blocks for parallel reception. Therefore, under a specific configuration, the buffer size that can be used for a transport block during unicast transmission needs to be determined based on the total buffer size of the terminal device, thereby determining the buffer size that can be used for each coded block. For broadcast / multicast data, however, full buffer rate matching is used, transmitting the entire coded block, which consumes a larger amount of buffer space.
[0094] In order to control the amount of buffer required to receive broadcast / multicast data and reduce the size of the encoded blocks for broadcast / multicast transmission, this application provides a communication method and an apparatus for implementing the method.
[0095] The embodiments of this application will now be described in detail with reference to the accompanying drawings.
[0096] The following describes the communication system architecture to which the communication method provided in this application is applicable. It should be noted that this description is for the convenience of those skilled in the art and does not constitute a limitation on the scope of protection claimed in this application.
[0097] The communication scheme provided in 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, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) mobile communication systems or new radio access technology (NR), satellite communication systems, etc. Among them, the 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking. The technical solution provided in this application can also be applied to future evolving communication systems. The satellite communication system can be a satellite communication system integrated with the 4th Generation (4G) mobile communication system, the 5G mobile communication system, or future communication systems, such as a non-terrestrial network (NTN), etc. NTN communication systems can be, for example, satellite communication systems, or can include unmanned aerial vehicles, high altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit the scope of such systems.
[0098] In a communication system, one network element can send signals to or receive signals from another network element. These signals can include information, signaling, or data. The term "network element" can also be replaced by entities, network entities, devices, communication equipment, communication modules, nodes, communication nodes, etc.
[0099] Figure 3 illustrates an exemplary schematic diagram of an evolved multimedia broadcast multicast service (E-MBMS) system architecture applicable to embodiments of this application. As shown in Figure 3, the E-MBMS system architecture may include a mobility management entity (MME), a multi-cell / multicast coordination entity (MCE), a multimedia broadcast service gateway (MBMS gateway, MBMS GW), and access network equipment (such as an evolved NodeB, eNodeB).
[0100] The MME is responsible for mobility management in the control plane, user context and mobility state management, and assigning temporary user identities.
[0101] The MCE is responsible for allocating time-domain and frequency-domain resources for the E-MBMS and determining the modulation scheme and effective code rate of the radio channel. The MCE can be a standalone entity or implemented as a logical entity in the access network equipment.
[0102] Understandably, the MCE is primarily used for MBMS scheduling, such as selecting appropriate resources (including parameters like frequency and time) for MBSFN transmission, which means ensuring that access network devices send MBMS data on suitable resources (such as MBSFN subframes). For multiple MBMS, the MCE needs to coordinate the transmission of its corresponding multiple MBSFNs, including the size of the MBSFN area and the use of radio resources, in order to use resources rationally and efficiently.
[0103] For example, configuration information related to the MCCH can be sent by the MCE to the access network device through the M2 interface. When the terminal device enters the MBSFN cell, it can read messages from the broadcast control channel (BCCH) and MCCH to obtain the MBMS configuration information in the target cell, and then receive the required MBMS (or MBMS data) on the MTCH.
[0104] The MBMS Gateway (GW) is responsible for handling MBMS distribution and control, and consists of control plane and user plane functions. The control plane processes MBMS session control signaling through the MME, transmitting MBMS session control signaling (such as session start and session stop) to the access network equipment. The user plane transmits data to the access network equipment via broadcast / multicast in the form of Internet Protocol (IP) multicast streams.
[0105] Access network equipment is a device that connects terminal devices to a wireless network. It can also be called an access network apparatus, wireless access network equipment, (R)AN entity, network device, access node, (R)AN node, or (R)AN device, etc. For example, access network equipment can provide network access functionality to authorized users in a specific area and can determine different quality transmission tunnels to transmit user data based on user level, service requirements, etc. Access network equipment can manage its own resources, utilize them rationally, provide access services to terminal devices on demand, and is responsible for forwarding control signals and user data between terminal devices and core network equipment.
[0106] For example, access network equipment can include, but is not limited to: eNodeB (eNB), access point (AP), access point (AP) in a wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP), next generation node B (gNB) in a 5G network, transmitting point (TP), transmission reception point (TRP), home base station (e.g., home evolved NodeB, or home Node B, HNB), macro base station, micro base station (also known as small station), relay station, satellite station, base band unit (BBU), and other access network equipment in communication systems evolved after 5G. Access network equipment can also be other equipment with access network equipment functions, such as gNB, TRP, or TP in a 5G system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system. Furthermore, access network equipment can also be equipment that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), Internet of Things (IoT), machine-to-machine (M2M) communication, or other communication systems. It can also include centralized units (CU) and distributed units (DU) in cloud radio access network (C-RAN) systems, and access network equipment in non-terrestrial network (NTN) communication systems, and can be deployed on high-altitude platforms or satellites. This application does not specifically limit this. For example, in a satellite communication system, the access network equipment can be a satellite or base station equipment mounted on a satellite.
[0107] For example, in some possible network architectures, access network devices can be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs), etc. CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). In this network architecture, signaling generated by the CU can be sent to the terminal device via the DU, or signaling generated by the terminal device can be sent to the CU via the DU. The DU can directly pass the signaling through protocol layer encapsulation without parsing it to the terminal device or CU. In this network architecture, the CU is classified as a device on the radio access network side; alternatively, the CU can also be classified as a device on the core network side, and this application does not impose any limitations on this. For example, the functions of the Packet Data Convergence Protocol (PDCP) layer and above are located in the CU, while the functions of protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer and the Medium Access Control (MAC) layer) are located in the DU. It is understood that the above division of the processing functions of the CU and DU according to protocol layers is merely an example, and other methods can also be used. For instance, the functions of protocol layers above the RLC layer are located in the CU, and the functions of protocol layers below the RLC layer are located in the DU. Alternatively, the CU or DU can be divided into those with functions involving more protocol layers, or even those with partial processing functions involving specific protocol layers.
[0108] It is understood that CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.
[0109] In this embodiment, the access network device can adopt a CU-DU separation architecture, which can also be called a distributed deployment architecture, or a CU-DU-RU separation architecture. For example, the access network device can logically include one CU and one or more DUs. Each DU can be connected to the CU through an F1 interface, and information exchange between different DUs can be completed based on the forwarding of the CU. The CU and DU can be physically set together or physically separated, without limitation. The CU can support the functions of the radio resource control (RRC) layer protocol, PDCP protocol, and service data adaptation protocol (SDAP) protocol; the DU can support the RLC layer protocol, MAC layer protocol, and some or all physical (PHY) layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant 3GPP technical specifications. For another example, the access network device can logically include a CU, DU, and RU. The CU and DU can be physically set together or physically separated, without limitation. The CU (Core Unit) supports RRC, PDCP, and SDAP layer protocols; the DU (Distributed Unit) supports RLC and MAC layer protocols, and some PHY layer protocols; the RU (Remote Root Unit) supports some or all PHY layer protocols. For example, the DU is primarily responsible for higher-level protocol functions such as data encryption and integrity protection, while the RU is primarily responsible for transmitting and receiving radio frequency signals. In this CU-DU-RU separation architecture, the interface between the DU and RU can be called fronthaul, the interface between the CU and DU can be called midhaul, and the interface between the CU and the core network can be called backhaul.
[0110] A terminal device is a device that provides voice or data connectivity to a user. It can also be an Internet of Things (IoT) device, and is also referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. This application does not limit the specific technology or device form used in the terminal device embodiments.
[0111] In the embodiments of this application, the terminal device can be fixed in location or mobile, and this application does not limit the location. For example, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted, or it can be deployed on water (such as a ship) or in the air (such as on an airplane, balloon or satellite).
[0112] It is understood that access network devices and terminal devices can communicate using licensed spectrum, unlicensed spectrum, or both simultaneously. Access network devices and terminal devices can communicate using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. This application does not limit the spectrum resources used between access network devices and terminal devices.
[0113] The interfaces in the E-MBMS system architecture are described below.
[0114] M1 Interface: This is the interface between the MBMS-GW and the access network equipment. It should be understood that the M1 interface is a user plane (UP) interface and can use IP multicast transmission to transmit MBMS data.
[0115] M2 interface: This is the interface between the MCE and the access network equipment. It should be understood that the M2 interface is a control plane (CP) interface and can use point-to-point (PTP) transmission.
[0116] M3 Interface: This is the interface between the MME and MCE. It should be understood that the M3 interface belongs to the control plane (CP) interface and is used to transmit session control signaling. It can use PTP transmission mode.
[0117] In this embodiment, the functions of the access network device (such as a base station) can be executed by modules (such as chips) within the access network device, or by a control subsystem containing base station functions. This control subsystem containing base station functions can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can be executed by modules (such as chips or modems) within the terminal device, or by a device containing terminal functions.
[0118] It should be noted that the communication system and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0119] In the E-MBMS system architecture shown in Figure 3 above, communication between multiple devices follows a certain protocol stack structure. The protocol stack under the E-MBMS system architecture can include a user plane protocol stack and a control plane protocol stack. Figure 4 is a schematic diagram of the user plane protocol stack in an E-MBMS system architecture provided by an embodiment of this application. Figure 4 uses the UE as the terminal device and the eNB as the access network device as an example. As shown in Figure 4, the user plane protocol stack between the UE and the eNB can include protocol layers such as the RLC layer, MAC layer, or PHY layer. For example, the RLC layer and MAC layer perform functions such as data segmentation and encapsulation.
[0120] The user plane protocol stack between the broadcast multicast service center (BM-SC) and the eNB can include a data synchronization protocol (SYNC) layer. This SYNC layer, defined above the transport network layer (TNL), supports content synchronization mechanisms and carries information enabling the eNB to recognize the timing of radio frame transmissions and detect packet loss.
[0121] The BM-SC is responsible for providing functions such as user management, session transmission, service claims, security management, and content synchronization. For content providers, the BM-SC is the MBMS content distribution entry point. For the bearer network, the BM-SC is responsible for authorization, initiating broadcast / multicast services, scheduling, and content transmission. For example, the MBMS packets provided by the BM-SC can be sent to the UE via the MBMS GW and eNB.
[0122] It is understandable that the BM-SC belongs to the service layer network element and serves as the entry point for content providers. It provides services aggregation and transmission, user authorization (key generation and transmission), MBMS bearer establishment and initiation, session control initiation, and also enables synchronization between the BM-SC and the eNB. The MBMS GW, as a node between the BM-SC and the eNB, is the network access gateway, responsible for handling user data-related messages and session-related signaling.
[0123] Figure 5 is a schematic diagram of the control plane protocol stack in an E-MBMS system architecture provided in an embodiment of this application. Figure 5 uses the UE as the terminal device and the eNB as the access network device as an example. As shown in Figure 5, the control plane protocol stack between the UE and the eNB may include protocol layers such as the RRC layer, RLC layer, MAC layer, or PHY layer. For example, the RRC layer mainly performs functions such as broadcasting, paging, RRC connection management, radio bearer management, mobility management, key management, UE measurement reporting and control, MBMS control, non-access stratum (NAS) message direct transmission, and quality of service (QoS) management. The relevant functions of the RLC layer and MAC layer can be referred to the description above, and will not be repeated here.
[0124] The control plane protocol stack between the MCE and eNB can include the M2 application protocol (M2AP). The control plane protocol stack between the MCE and MME can include the M3 application protocol (M3AP). For example, the control plane protocol structure of the M2 interface can be seen in Figure 6. As shown in Figure 6, M2AP can include the Stream Control Transmission Protocol (SCTP), IP protocol, data link layer protocol, and PHY layer protocol, etc.
[0125] The M2 interface signaling process includes the MBMS scheduling information process, which enables the MCE to update the MCCH information. Typically, the MCE triggers the MBMS scheduling information process before MBMS user data transmission or when user plane data transmission ends. The MBMS scheduling information process allows the MCE to update the MCH scheduling information.
[0126] The specific implementation of the communication method in the embodiments of this application will be described in detail below with reference to the accompanying drawings. It is understood that the embodiments of this application use a first communication device and a second communication device as examples of the execution subjects in the interactive illustration, but this application does not limit the execution subjects in the interactive illustration. For example, the first communication device can be a network device, such as an access network device (e.g., a base station), and the second communication device can be a terminal device (e.g., a UE). The method executed by the access network device in this application can also be executed by a module applied to the access network device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the access network device functions, or it can also be implemented through a combination of hardware and software. Similarly, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the terminal device functions, or it can also be implemented through a combination of hardware and software.
[0127] Figure 7 illustrates a flowchart of a communication method provided in an embodiment of this application. This method is applicable to the E-MBMS system architecture shown in Figure 3. As shown in Figure 7, the method includes:
[0128] Step 701: The first communication device sends the first information. Correspondingly, the second communication device receives the first information.
[0129] In one possible implementation, the first piece of information is system information, also known as configuration information. This configuration information can be carried by the MCCH. This configuration information can be sent by the MCE in the system architecture to the access network devices within the MBSFN area, and then by the access network devices to the terminal devices. If the MCE is implemented as a logical entity within the access network devices, the configuration information is sent by the access network devices to the terminal devices.
[0130] The first information can be used to determine the buffer size corresponding to a transport block of a multicast service channel, or in other words, to determine the buffer size of a coding block of a multicast service channel.
[0131] The multicast service channel refers to the MTCH, corresponding to the logical channel MCH, or the PMCH at the physical layer. The PMCH is the channel on the physical layer mapped from the MCH. The MCH can include the MCCH and / or the MTCH; the MCCH carries control information for the MBMS service, and the MTCH carries data for the MBMS service.
[0132] In one possible implementation, the first information may include the soft buffer size corresponding to a transport block of the multicast service channel. This allows the second communication device to directly use the... Determine the buffer size corresponding to a coding block of the multicast service channel.
[0133] It is understandable that the first piece of information includes the buffer size corresponding to a transport block of the multicast service channel. Specifically, it could refer to the following As part of the first information, it is sent to the second communication device; or, it may refer to the first information or an indication information (or parameter) in the first information used to indicate the buffer size corresponding to a transport block of the multicast service channel. For example, the buffer size corresponding to a transport block of a multicast service channel. There are multiple possible values, each distinguished by a number. The first information may include one of these numbers to indicate the buffer size corresponding to the transport block. The meanings of phrases such as "the first information contains" or "the first information includes" in the following text can be understood in the same way as explained above.
[0134] In another possible implementation, the first information includes terminal device type information, which enables the second communication device to obtain the corresponding number of soft channel bits based on the terminal device type information, and then determine the buffer size corresponding to a transport block of the multicast service channel based on the number of soft channel bits.
[0135] Taking the second communication device as an example, the terminal device's wireless access capability and ability to receive multicast service channels can be reflected by the terminal device type. The terminal device can query the downlink physical parameters corresponding to the terminal device type based on the terminal device type information sent by the network device, thereby obtaining the expected number of soft channel bits.
[0136] For example, the downlink physical parameters corresponding to the terminal device type can be shown in Table 1.
[0137] Table 1: Downlink Physical Parameters Corresponding to Terminal Device Types
[0138] In Table 1, the first column indicates the UE category of the terminal device's network access capability; the second column indicates the total number of bits in the largest transport block (TB) that can be transmitted within each transmission time interval (TTI). The value of this column can be referenced to the maximum number of DL-SCH transport block bits received within a TTI; the third column indicates the maximum number of bits in a transport block within a TTI. The value of this column can be referenced to the maximum number of bits of a DL-SCH transport block received within a TTI; the fourth column indicates the total number of soft channel bits, which reflects the terminal device's hardware storage resources; and the last column indicates the maximum number of supported layers for spatial multiplexing in DL, reflecting the spatial multiplexing capability, which is generally strongly correlated with the number of antennas or antenna ports of the terminal device.
[0139] Taking the terminal device type information sent by the network device as an example to indicate "Type 5" in Table 1, the terminal device can obtain the corresponding "total number of soft channel bits" by querying Table 1 based on the terminal device type information, which has a value of 3667200.
[0140] It is understood that Table 1 above is only one possible example, and this application does not limit the correspondence between terminal device type and downlink physical parameters.
[0141] The first communication device can send first information to multiple second communication devices that receive multicast service channels. The first information sent by the first communication device to different second communication devices contains identical terminal device type information. That is, although the types of terminal devices receiving multicast service channels may vary, the terminal device type information sent by the network device to these terminal devices is identical. This ensures that the "total number of soft channel bits" determined by these terminal devices is the same, resulting in identical buffer sizes for a transport block and a coding block of the multicast service channel. This guarantees consistent understanding of the transport block (or coding block) size between the terminal side and the network side, ensuring correct reception of the multicast service channel by the terminal side.
[0142] In one possible implementation, in addition to including terminal device type information, the first information may further include at least one of a first scaling factor and a carrier number, as a basis for determining the buffer size corresponding to a transport block of the multicast service channel. The first scaling factor is a real number greater than 0 and less than or equal to 1, for example, a value of 0.5. The value of the first scaling factor can be a fixed value, in which case it can be pre-configured. The first scaling factor can also be configured by the network side; in this case, the first scaling factor can be configured to the second communication device through the first information. The carrier number is the number of carriers used to carry the multicast service channel. This carrier can be dedicated to carrying the multicast service channel, that is, the carrier can be a dedicated carrier for the multicast service channel. In this embodiment, the first scaling factor can be expressed as β, and the carrier number can be expressed as... Of course, other representation methods can also be used, and this application does not restrict them.
[0143] In some embodiments of this application, in order to improve the reception performance of the multicast service channel, the transport blocks of the multicast service channel can be interleaved in the time domain. That is, one transport block of the multicast service channel can be transmitted in multiple non-contiguous time units in the time domain, thereby obtaining time domain diversity gain. The time unit can be a subframe or a time slot, etc., and this application does not limit the scope.
[0144] In one time-domain interleaving scheme, the number of the plurality of non-contiguous time units can be represented as N (N is an integer greater than 1), and the interval between any two adjacent time units is M (M is an integer greater than or equal to 1) time units. That is, in this time-domain interleaving scheme, the interleaving length is N and the interleaving depth is M.
[0145] The time interval between two adjacent time units may or may not include the preceding time unit. In other words, the time interval between two adjacent time units can be identified by the difference between their unit numbers, or by subtracting one from the difference. For example, a time-domain interleaving scheme is as follows: Subframe 1 (transmitting TB0), Subframe 2 (transmitting TB1), Subframe 3 (transmitting TB2), Subframe 4 (transmitting TB3), Subframe 5 (transmitting TB0), Subframe 6 (transmitting TB1), Subframe 7 (transmitting TB2), Subframe 8 (transmitting TB3), and so on. The multiple non-contiguous subframes of TB0 include subframe 1, subframe 5, and so on. The time interval between two adjacent subframes can be considered as 3 subframes (i.e., there are 3 subframes between subframe 1 and subframe 5, namely subframe 2, subframe 3 and subframe 4, which does not include subframe 1 and subframe 5), or it can be considered as 4 subframes (i.e., there are 4 subframes between subframe 1 and subframe 5, namely subframe 1, subframe 2, subframe 3 and subframe 4, which includes subframe 1).
[0146] Taking a time unit as a subframe as an example, Figure 8 illustrates a schematic diagram of a time-domain interleaving scheme for transport blocks in a multicast service channel. As shown in Figure 8, in this time-domain interleaving scheme, identical redundant versions of m transport blocks (TBs) are distributed across m subframes. The n redundant versions of a TB are transmitted in non-contiguous subframes, with an interval of m between adjacent subframes.
[0147] Based on the time-domain interleaving scheme shown in Figure 8, taking an interleaving length of n=4 and an interleaving depth of m=4 as an example, in the 16 MBSFN subframes in the time domain, MBSFN subframe 1 is used to transmit TB0, MBSFN subframe 2 is used to transmit TB1, MBSFN subframe 3 is used to transmit TB2, MBSFN subframe 4 is used to transmit TB3, MBSFN subframe 5 is used to transmit TB0, MBSFN subframe 6 is used to transmit TB1, MBSFN subframe 7 is used to transmit TB2, MBSFN subframe 8 is used to transmit TB3, MBSFN subframe 9 is used to transmit TB0, MBSFN subframe 10 is used to transmit TB1, MBSFN subframe 11 is used to transmit TB2, MBSFN subframe 12 is used to transmit TB3, MBSFN subframe 13 is used to transmit TB0, MBSFN subframe 14 is used to transmit TB1, MBSFN subframe 15 is used to transmit TB2, and MBSFN subframe 16 is used to transmit TB3.
[0148] Optionally, MBSFN subframes 1, 5, 9, and 13 can be used to transmit different redundant versions of the same TB. For example, MBSFN subframe 1 is used to transmit new data packets for TB0, while MBSFN subframes 5, 9, and 13 are used to transmit retransmitted data packets of different redundant versions of TB0.
[0149] A first communication device (e.g., a network device) can send time-domain interleaving parameters (e.g., at least one of interleaving length and interleaving depth) to a second communication device (e.g., a terminal device). For example, the time-domain interleaving parameters can be sent to the terminal device via first information, that is, the first information may include the number of time units (interleaving length) and time interval information (interleaving depth), wherein the "number of time units" indicates the number of multiple non-contiguous time units, and the "time interval information" indicates the interval between two adjacent time units among the multiple non-contiguous time units.
[0150] It is understood that the first piece of information can be sent through one message or multiple messages. For example, terminal type information can be sent through one radio resource control (RRC) message, and time-domain interleaving parameters can be sent through another RRC message; this application does not impose any restrictions.
[0151] In one possible implementation, the first communication device may further send at least one of the modulation and coding scheme (MCS) index and transport block size (TBS) index used by the multicast service channel to the second communication device, so that the second communication device can determine the corresponding MCS based on the MCS index, and determine the number of bits of the transport block transmitted within one TTI based on the TBS index and the number of PRBs used by the multicast service channel. For example, the MCS may be quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM), wherein QAM may include 16QAM, 64QAM, or 256QAM, which is not limited in this application.
[0152] Optionally, the first information may include at least one of the MCS index and TBS index used by the multicast service channel. The first information may be sent through one message or through multiple messages. For example, the first communication device may send terminal device type information through one message and send at least one of the MCS index and TBS index through another message.
[0153] Step 702: The second communication device determines the buffer size corresponding to a transport block of the multicast service channel based on the first information.
[0154] In one possible implementation, the second communication device can determine the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information. For example, the second communication device can query the number of soft bits corresponding to the terminal device type based on the terminal device type information contained in the first information (as shown in Table 1) to obtain the number of soft bits corresponding to the terminal device type information. Then, the buffer size corresponding to a transport block of the multicast service channel can be determined based on the number of soft channel bits. For example, the number of soft information bits can be determined as the buffer size corresponding to a transport block of the multicast service channel.
[0155] In another possible implementation, the second communication device can determine the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information. For example, the second communication device can query the number of soft bits corresponding to the terminal device type based on the terminal device type information contained in the first information (as shown in Table 1), thereby obtaining the number of soft bits corresponding to the terminal device type information; then, based on the number of soft channel bits, and according to the first scaling factor β and the number of carriers... At least one of the following determines the buffer size corresponding to a transport block of a multicast service channel.
[0156] Optional, the first scaling factor β and / or the number of carriers It can be carried in the first information and sent to the second communication device, or it can be configured or pre-configured to the second communication device in other ways, which is not limited in this application.
[0157] For example, the buffer size corresponding to a transport block of a multicast service channel. Satisfy the following formula (1):
[0158] For example, the buffer size corresponding to a transport block of a multicast service channel. The following formula (2) must be satisfied:
[0159] Another example is the buffer size corresponding to a transport block of a multicast service channel. The following formula (3) must be satisfied:
[0160] In the above formulas (1), (2), and (3), The buffer size corresponding to one transport block of a multicast service channel. The number of soft channel bits corresponding to the terminal device type information, where β is the first scaling factor. For the number of carriers; This indicates rounding down, where x is a real number. Rounding down means rounding a real number down to the nearest integer that does not exceed it.
[0161] In another possible implementation, when a transport block of a multicast service channel is interleaved in the time domain (i.e., transmitted in multiple non-contiguous time units), the second communication device can determine the number of soft channel bits corresponding to the terminal device type information based on the terminal device type information. For example, the second communication device can query the number of soft bits corresponding to the terminal device type based on the terminal device type information contained in the first information (as shown in Table 1) to obtain the number of soft bits corresponding to the terminal device type information. Then, based on the number of soft channel bits and the interleaving depth of the transport block in the time domain, the buffer size corresponding to a transport block of the multicast service channel is determined.
[0162] Interleaving depth is the time interval, used to indicate the interval between two adjacent time units in a multicast service channel's transport block across multiple non-contiguous time units.
[0163] Optionally, the interleaving depth (time interval) can be carried in the first information and sent to the second communication device, or it can be configured to the second communication device in other ways, which is not limited in this application.
[0164] For example, the buffer size corresponding to a transport block of a multicast service channel. The following formula (4) must be satisfied:
[0165] For example, based on formula (4), the first scaling factor β can also be used to determine the buffer size corresponding to a transport block of a multicast service channel. The basis for this is, for example, the buffer size corresponding to a transport block of a multicast service channel. The following formula (5) must be satisfied:
[0166] As another example, based on formula (4), the number of carriers can also be increased. The buffer size corresponding to a transport block for determining a multicast service channel. The basis for this is, for example, the buffer size corresponding to a transport block of a multicast service channel. The following formula (6) must be satisfied:
[0167] As another example, based on formula (4), the first scaling factor β and the number of carriers can also be combined. The buffer size corresponding to a transport block for determining a multicast service channel. The basis for this is, for example, the buffer size corresponding to a transport block of a multicast service channel. The following formula (7) must be satisfied:
[0168] In the above formulas (4), (5), (6), and (7), The buffer size corresponding to one transport block of a multicast service channel. Where M is the number of soft channel bits corresponding to the terminal device type information, M is the time interval (or interleaving depth), and β is the first scaling factor. For the number of carriers; This indicates rounding down, where x is a real number.
[0169] It is understood that the above formulas (1) to (7) are only examples of several ways to determine the buffer size corresponding to the transport block. Based on this, the schemes obtained by modifying some algorithms (e.g., changing the rounding down to other rounding methods) or adding some other parameters are all within the protection scope of this application.
[0170] In one possible implementation, the second communication device can determine the maximum number of bits in a transport block of the multicast service channel based on the terminal device type information contained (or indicated) in the first information. For example, the second communication device can query the "maximum number of bits in a transport block within a TTI" (as shown in Table 1) corresponding to the terminal device type based on the terminal device type information, thereby obtaining the maximum number of bits in a transport block corresponding to the terminal device type information. When scheduling the multicast service channel, the first communication device can determine the maximum number of bits allowed to be scheduled for a transport block based on this parameter. When using a time-domain interleaving scheme, the number of bits in a transport block of the multicast service channel can be expressed as N'' = round(N′*N). Where N′ is the number of bits in a transport block sent within a TTI, and the second communication device can determine the number of bits N′ in a transport block sent within a TTI based on the TBS index and the number of PRBs used by the multicast service channel; N is the time-domain interleaving length; round() represents rounding to the nearest integer. N'' is less than the maximum number of bits in a transport block corresponding to the terminal device type information. In other words, if round(N′*N) is greater than the "maximum number of bits in a transport block within a TTI" corresponding to the terminal device type information, then the "maximum number of bits in a transport block within a TTI" corresponding to the terminal device type information is used as the maximum number of bits that the first communication device can schedule for a transport block.
[0171] In some cases, there are multiple values for the maximum number of bits in a transport block of a multicast service channel corresponding to the terminal device type information. For example, in Table 1, the "maximum number of bits in a transport block within a TTI" for "Type 6" has the following two values: 149776 (4 transport layers, 64QAM) and 75376 (2 transport layers, 64QAM). In this case, the second communication device can determine a first value based on the terminal device type information, choosing one of the multiple maximum number of bits in a transport block of the multicast service channel. The first value is used to determine the maximum number of bits in a transport block of the multicast service channel. Optionally, the first value can be the maximum or minimum value among the multiple maximum number of bits, or it can be determined based on the network device's configuration information. For example, the network device can specify the maximum or minimum value among the multiple maximum number of bits through configuration information.
[0172] For example, taking "Type 6" in Table 1 and its corresponding "maximum number of bits in a transport block within a TTI" as an example, in one possible way, the second communication device can, according to the protocol, determine the minimum value between 149776 and 75376 as the maximum number of bits in a transport block by default; in another possible way, the second communication device can, according to the protocol, determine the maximum value between 149776 and 75376 as the maximum number of bits in a transport block by default; in yet another possible implementation, the second communication device can, according to the configuration information sent by the first communication device, determine the minimum or maximum value between 149776 and 75376 as the maximum number of bits in a transport block.
[0173] Step 703: The second communication device determines the buffer size corresponding to a coding block of the multicast service channel based on the buffer size corresponding to a transport block of the multicast service channel.
[0174] In one possible implementation, the buffer size corresponding to a coding block of a multicast service channel satisfies the following formula (8):
[0175] in, The buffer size corresponding to one coding block of a multicast service channel. C is the buffer size corresponding to one transport block of a multicast service channel. B This refers to the number of coded blocks determined after the transport block is segmented into code blocks. This represents the total number of bits output after the coded block is channel-coded; min(x,y) means rounding down, where x is a real number; min(x,y) means taking the minimum value between x and y.
[0176] It is understood that the above formula (8) is only an example of determining the cache size corresponding to the coded block. Any scheme obtained by modifying the algorithm or adding other parameters based on this formula is within the scope of protection of this application.
[0177] Step 704: The first communication device transmits the multicast service channel. Correspondingly, the second communication device receives the multicast service channel according to the buffer size corresponding to a coding block of the multicast service channel.
[0178] After processing the multicast service data (including rate matching), the first communication device transmits the multicast service data through the multicast service channel. The data processing procedures of the first and second communication devices are essentially the same. That is, the first and second communication devices can determine the buffer size corresponding to a transport block and the buffer size corresponding to a coding block of the multicast service channel using the same method and based on the same parameters. This ensures that the buffer sizes determined by the first and second communication devices for the transport block and the coding block are the same, thereby guaranteeing correct reception of the multicast service channel.
[0179] During the transmission of the multicast channel, the first communication device can perform rate matching based on the buffer size corresponding to a coding block of the multicast service channel, and the second communication device can perform de-rate matching based on the buffer size corresponding to a coding block of the multicast service channel.
[0180] Rate matching refers to the process of retransmitting or puncturing bits on a transmission channel to match the carrying capacity of the physical channel, achieving the bit rate required by the transmission format during channel mapping. Punching involves removing the current bit and shifting the subsequent bits forward by one position, essentially removing bits from the bit sequence according to a specific pattern. Repetition involves inserting the current bit once between the current bit and the following bit.
[0181] For multicast service channels, Turbo coding can be used for channel coding. Turbo coding performs transmission channel rate matching on a block-by-block basis, including bit collection, interleaving, and circular buffer generation. Through these operations, the system can flexibly adjust the transmission rate according to channel conditions to ensure efficient data transmission. When using Turbo coding, the transmission block for the multicast service channel uses turbo coding with a code rate of 1 / 3, meaning the encoder input consists of K bits. II 1 bit, encoder output is 3K IIThe number of bits, that is, the total number of bits output after the coded block is channel-coded. Then, 3K II After matching the LBRM with a limited cache rate, each coded block is determined to be... 1 bit, then this A number of bits are involved in subsequent modulation and mapped to the RE at the physical layer.
[0182] For example, Figure 9 illustrates a rate matching process for a Turbo-coded transmission channel. This involves determining the buffer size corresponding to a coding block of a multicast service channel. Then, rate matching can be performed according to the process shown in Figure 9.
[0183] As shown in Figure 9, for a length of K II bit sequence and After interleaving the sub-blocks separately, three blocks of length K are obtained. II bit sequence and Next, for 3 lengths of K II bit sequence and Bit collection was performed, resulting in a length of 3K. II bit sequence w k Then, based on the cache size corresponding to a coding block... For a length of 3K II bit sequence w k Rate matching (i.e., bit selection and puncturing) is performed to obtain a length of 3K. II A bit sequence of a coded block
[0184] During rate matching, if This indicates that the buffer size corresponding to a single coded block cannot buffer the total number of bits of the coded block after channel coding. In this case, the number of bits that can be cached in a coded block is The corresponding part can therefore be determined based on the number of bits that can be cached. Loop from The corresponding data is extracted for transmission.
[0185] For example, based on the above data processing procedure, in a scenario where the transport blocks of a multicast service channel are transmitted using time-domain interleaving, if the total number of bits of the interleaved transport block that can be transmitted within one subframe is G, then it is determined that: Among them, Q mThis indicates the modulation order. For example, if the modulation scheme is QPSK, then Q... m =2; if the modulation scheme is 16QAM, then Q m =4; if the modulation scheme is 256QAM, then Q m =6; if the modulation scheme is 256QAM, then Q m =8.
[0186] Then, γ is determined according to G′: γ = G′mod C. Where C is the total number of coded blocks corresponding to a transport block, and mod is the modulo operator.
[0187] Finally, for the C coded blocks corresponding to a transport block, if the number of bits in the r-th coded block output by the rate matching module is E, then for the first (C-γ-1) coded blocks of these C coded blocks, E = Q. m ×floor(G′ / C), from the (C-γ)th coded block to the last coded block, E = Q m ×ceiling(G′ / C). Here, floor() represents the floor function, and ceiling represents the floor function.
[0188] Once the number of bits E of a coding block is determined, the rate matching process is as follows: for a block of size E... A soft buffer is used to determine a starting pointer, and E bits are read starting from the bit corresponding to that starting pointer. The starting pointer can be set to... in The number of rows in the matrix determined by the sub-block interleaver in the rate matching of the Turbo-coded transport channel; n takes values of 0, 1, 2, 3, 4, ..., N, where N is the interleaving length.
[0189] Rate matching dematching is the process of recovering the original coded bits from received data that has undergone rate matching. Rate matching involves selectively repeating or deleting coded bits to adapt to different transmission requirements and channel conditions. Rate matching dematching is the inverse operation of this process, aiming to recover the original sequence of coded bits.
[0190] For example, the rate matching resolution process may include: the receiver receiving the signal transmitted through the multicast service channel after a series of processing steps such as rate matching and modulation mapping; and the receiver performing a reverse operation on the received data according to rate matching related parameters. If the transmitter repeated some bits during rate matching, the receiver removes these repeated bits; if the transmitter performed a deletion operation during rate matching, the receiver restores the deleted bits according to a certain algorithm. The rate matching related parameters may include the first information in the embodiments of this application, and may also include other information, such as a repetition factor and a deletion mode.
[0191] After rate matching is achieved, the receiver obtains the sequence of coded bits transmitted through the channel. Next, the receiver can send these coded bits to a decoder for decoding. The decoder can utilize the parity-check matrix of the Turbo code and an iterative decoding algorithm to perform decoding based on the received coded bits and channel statistics.
[0192] According to the process shown in Figure 7 above, the buffer size corresponding to the coding block of the multicast service channel is determined for multicast services. When transmitting the multicast service channel, rate matching can be performed based on the buffer size corresponding to the coding block of the multicast service channel. Correspondingly, at the receiving end, rate matching can be de-matched based on the buffer size corresponding to the coding block of the multicast service channel. That is, limited buffer rate matching is implemented for broadcast / multicast data. Compared with the traditional multicast service data processing process, which uses full buffer rate matching, the above implementation method provided by the embodiments of this application can reduce the size of the coding block, thereby reducing the amount of buffer space occupied.
[0193] In addition, the use of time-domain interleaving for the transmission blocks of the multicast service channel in the above process can effectively improve the reception performance of the terminal equipment for broadcast / multicast data.
[0194] In some embodiments of this application, the multicast service channel used for broadcast / multicast and the downlink shared channel (e.g., DL-SCH) used for unicast can share the same number of soft channel bits. This number of soft channel bits refers to the number of soft channel bits corresponding to the type of terminal device. In other words, for a given terminal device, this number of soft channel bits reflects the hardware storage resources of the terminal device, or in other words, reflects the data processing capability (e.g., data receiving capability) of the terminal device.
[0195] In this context, the multicast service channel and the downlink shared channel can share the number of soft channel bits. This can be understood as the multicast service channel and the downlink shared channel sharing the data receiving capability of the terminal device, or in other words, multicast and unicast can share the data receiving capability of the terminal device. In other words, the terminal device can receive data through the multicast service channel, the downlink shared channel, or both, based on its data receiving capability (which can be reflected by the number of soft channel bits).
[0196] In a scenario where the first communication device schedules both a downlink shared channel (i.e., schedules unicast data transmission) and a multicast service channel (i.e., schedules broadcast / multicast data transmission), if the downlink shared channel and multicast service channel scheduled by the network side exceed the processing capacity of the second communication device, the choice of which channel to receive depends on the implementation of the second communication device. In other words, the second communication device can decide for itself which channel to receive between the downlink shared channel and the multicast service channel.
[0197] In this case, the downlink shared channel and multicast service channel scheduled by the network side exceed the processing capacity of the second communication device. This can be understood as follows: the downlink shared channel and multicast service channel exceed the number of soft information bits corresponding to the device type of the second communication device; or it can be understood as: the sum of the buffer size corresponding to one transport block of the downlink shared channel and the buffer size corresponding to one transport block of the multicast service channel exceeds the number of soft information bits corresponding to the device type of the second communication device. In this situation, the downlink shared channel and multicast service channel cannot share the number of soft information bits corresponding to the device type of the second communication device. Therefore, the second communication device can decide whether to receive the multicast service channel or the downlink shared channel.
[0198] The method for determining the buffer size corresponding to a coding block of a multicast service channel can be found in the relevant content of the embodiments of this application. The method for determining the buffer size corresponding to a coding block of a downlink shared channel is not limited in this application.
[0199] For example, the following is a process for determining the buffer size corresponding to a coding block of a downlink shared channel:
[0200] First, determine the buffer size corresponding to one transport block of the downlink shared channel. For example, the buffer size N corresponding to one transport block of the downlink shared channel. IR The following formula (9) must be satisfied:
[0201] Where, N soft This refers to the number of soft channel bits corresponding to the type of terminal equipment; α is related to the transmission time interval of the downlink shared channel, and its value can be 1, 0.5, or 1 / 6, etc.; K MIMO It can be either 2 or 1, and its value depends on the transmission mode; M DL_HARQ It is the largest number of downlink hybrid automatic repeat request (HARQ) processes; M limit It is a fixed value, taking the value 8; K C It is related to the total cache size, as well as whether certain modulation schemes or the maximum number of spatial tiers are configured.
[0202] For example, K C The possible values for are:
[0203] If N soft =35982720 or 47431680, then K C =5.
[0204] If N soft =303562752, then K C =32.
[0205] If N soft =14616576, then: if the terminal device is configured by altCQI-Table-r12 by a higher layer, then K C =3 / 2, otherwise, K C =2.
[0206] If N soft =19488768, then: if the terminal device is configured by a higher layer using altCQI-Table-1024QAM-r15, then K C =8 / 5; If the terminal device is configured by a higher layer using altCQI-Table-r12, then K C =2; otherwise, K C =8 / 3.
[0207] If N soft =7308288, and the terminal device is configured by a higher layer using altCQI-Table-r12, then: if the terminal device can support a maximum of two spatial layers for the downlink cell in the transmission mode configured for the terminal device, or if the maximum number of layers indicated by the maxLayersMIMO-r10 field does not exceed two, then K C =3; otherwise, K C =3 / 2.
[0208] If N soft =7308288, and the terminal device is configured by a higher layer using altCQI-Table-1024QAM-r15, then: if the terminal device can support up to two spatial layers for the downlink cell in the transmission mode configured for the terminal device, or if the maximum number of layers indicated by the maxLayersMIMO-r10 field does not exceed two, then K C =12 / 5, otherwise, K C =6 / 5.
[0209] If N soft=3654144, and the terminal device can support a maximum of two spatial layers for the downlink cell, or if the maximum number of layers indicated by the maxLayersMIMO-r10 field does not exceed two layers, then K C =2, otherwise, K C =1.
[0210] Then, based on the buffer size N corresponding to a transport block IR Determine the buffer size N corresponding to a coding block of the downlink shared channel. cb For example, the buffer size N corresponding to a coding block of a downlink shared channel. cb The following formula (10) must be satisfied:
[0211] Where C is the number of coded blocks determined by the total number of bits in a transport block, and K... w This represents the total number of bits output after a coding block is channel-coded.
[0212] In one possible implementation, the second communication device may, under certain conditions, receive the downlink shared channel and abandon receiving the multicast service channel; or, receive the multicast service channel and abandon receiving the downlink shared channel. Optionally, the second communication device may prioritize receiving the downlink shared channel or abandon receiving the multicast service channel, and then resume receiving the multicast service channel when the multicast service channel and the downlink shared channel can share the number of soft channel bits.
[0213] For example, the above conditions can be one of the following:
[0214] a) During a scheduling time interval, the multicast service channel and downlink shared channel scheduled by the first communication device exceeded the processing capacity of the second communication device.
[0215] b) When the second communication device is operating in multi-carrier aggregation mode, if the multicast service channel and downlink shared channel scheduled by the first communication device exceed the processing capacity of the terminal within a scheduling time interval;
[0216] c) If the number of soft channel bits scheduled by the first communication device for the multicast service channel and the downlink shared channel exceeds the number of soft channel bits corresponding to the type of terminal device.
[0217] In some embodiments of this application, when the first communication device schedules both a downlink shared channel (i.e., schedules unicast data transmission) and a multicast service channel (i.e., schedules broadcast / multicast data transmission), the first communication device can send a parameter for determining the buffer size corresponding to the transport block of the downlink shared channel to the second communication device. This allows the second communication device to determine the buffer size corresponding to the coding block of the downlink shared channel based on the parameter, thereby maximizing the reception of both the downlink shared channel and the multicast service channel. A detailed implementation can be found in the flowchart shown in Figure 10.
[0218] The communication process in a scenario where the multicast service channel and the downlink shared channel can share the number of soft channel bits is described below with reference to Figure 10. It is understood that the embodiments of this application use the first and second communication devices as examples of the execution entities for the interactive illustration, but this application does not limit the execution entities for the interactive illustration. For example, the first communication device can be a network device, such as an access network device (e.g., a base station), and the second communication device can be a terminal device (e.g., a UE). The method executed by the access network device in this application can also be executed by a module applied to the access network device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or can be implemented by a logical node, logical module, or software that can implement all or part of the access network device functions, or it can be implemented through a combination of hardware and software. The method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or can be implemented by a logic node, logic module, or software that can implement all or part of the functions of the terminal device, or can be implemented by a combination of hardware and software.
[0219] As shown in Figure 10, the process may include the following steps:
[0220] Step 1001: The second communication device sends third information to the first communication device. Correspondingly, the first communication device receives the third information.
[0221] The third information is used to indicate the willingness or ability of the second communication device to receive downlink shared channels and multicast service channels, so that the first communication device can send the second information to the second communication device according to the third information.
[0222] For example, third-party information may include one or more of the following:
[0223] a) Second indication information: used to indicate that the second communication device expects to receive both the downlink shared channel and the multicast service channel simultaneously;
[0224] b) Third indication information: used to instruct the second communication device to prioritize receiving the multicast service channel;
[0225] c) Terminal device capability information. This terminal device capability information is used to indicate that the second communication device supports determining the buffer size corresponding to a transport block of the downlink shared channel based on the network configuration information.
[0226] Step 1002: The first communication device sends second information to the second communication device. Correspondingly, the second communication device receives the second information.
[0227] The second information is used to trigger the second communication device to determine the buffer size corresponding to a transport block of the downlink shared channel, or the second information is used to determine the buffer size corresponding to a transport block of the downlink shared channel.
[0228] In one possible implementation, the second information may include first indication information. The first indication information is used to indicate the number of soft channel bits shared by the multicast service channel and the downlink shared channel. That is, the first indication information can trigger the second communication device to determine the buffer size corresponding to a transport block of the downlink shared channel.
[0229] In another possible implementation, the second information may include a second scaling factor. The second scaling factor is a real number greater than 0 and less than or equal to 1. The value of the second scaling factor can be a fixed value; in this case, the second scaling factor can be pre-configured. Alternatively, the second scaling factor can be configured by the network side; in this case, the second scaling factor can be configured to the second communication device through the second information.
[0230] In another possible implementation, the second information may include the first indication information and the second scaling factor.
[0231] Step 1003: The second communication device determines the buffer size corresponding to a transport block of the downlink shared channel based on the second information.
[0232] In one possible implementation, the buffer size corresponding to a transport block of the downlink shared channel satisfies the following formula (11):
[0233] Where, N IR N is the buffer size corresponding to one transport block of the downlink shared channel; soft The number of soft channel bits determined based on the type of terminal device; K C Related to the total cache size (which is determined based on the terminal setting type); K MIMO Related to the transmission mode of the downlink shared channel, its value is 1 or 2; M DL_HARQM represents the maximum number of HARQ processes for the downlink shared channel. limit It is a fixed value; α is related to the transmission time interval of the downlink shared channel, and can take values of 1, 0.5, or 1 / 6, etc. `min()` indicates rounding down, where x is a real number; `min()` indicates taking the minimum value. For the values of the relevant parameters, please refer to the relevant content throughout the text.
[0234] According to the above formula (11), the buffer size corresponding to a transport block of the downlink shared channel can be reduced by the second proportional factor based on the value calculated by formula (9) to appropriately reduce the buffer size corresponding to a transport block of the downlink shared channel, thereby reducing the buffer size corresponding to a coding block of the downlink shared channel, so as to make the downlink shared channel and the multicast service channel share the processing capabilities of the terminal equipment as much as possible.
[0235] In another possible implementation, the buffer size corresponding to a transport block of the downlink shared channel satisfies the following formula (12):
[0236] Where β is the first scaling factor. This represents the number of soft channel bits corresponding to the terminal device type information. Other parameters can be explained using formula (11).
[0237] According to the above formula (12), it can be seen that the buffer size corresponding to a transport block of the downlink shared channel can be determined based on the value calculated by formula (9), by using the first proportional factor β. The second scaling factor is also adjusted downward to appropriately reduce the buffer size corresponding to a transport block of the downlink shared channel, thereby reducing the buffer size corresponding to a coding block of the downlink shared channel, so as to enable the downlink shared channel and the multicast service channel to share the processing capabilities of the terminal equipment as much as possible.
[0238] It is understood that the above formulas (11) to (12) are only examples of several ways to determine the buffer size corresponding to the transport block. Any scheme obtained by modifying the algorithm (e.g., changing the rounding down to other rounding methods) or adding other parameters based on these are all within the scope of protection of this application.
[0239] After determining the buffer size corresponding to a coding block of the downlink shared channel, if the downlink shared channel and multicast service channel scheduled by the network side do not exceed the processing capacity of the second communication device, then the second communication device can receive the downlink shared channel and multicast service channel. If the downlink shared channel and multicast service channel scheduled by the network side exceed the processing capacity of the second communication device, then the second communication device can decide on its own whether to receive the downlink shared channel or the multicast service channel. For example, the second communication device can prioritize receiving the downlink shared channel or abandon receiving the multicast service channel, and resume receiving the multicast service channel when the multicast service channel and the downlink shared channel can share the number of soft channel bits.
[0240] In the process shown in Figure 10 above, step 1001 is an optional step (indicated by a dashed line in the figure). That is to say, the first communication device can send second information to the second communication device based on the third information sent by the second communication device, or the first communication device can decide on its own to send second information to the second communication device.
[0241] For example, after receiving the second instruction information sent by the second communication device, the first communication device determines, based on the second instruction information, that the second communication device expects to simultaneously receive the downlink shared channel and the multicast service channel, and therefore the first communication device sends the second information to the second communication device.
[0242] For another example, after receiving the third instruction information sent by the second communication device, the first communication device determines, based on the third instruction information, that the second communication device has priority to receive the multicast service channel, and therefore the first communication device sends the second information to the second communication device.
[0243] For another example, after receiving terminal device capability information sent by the second communication device, the first communication device determines, based on the terminal device capability information, that the second communication device supports determining the buffer size corresponding to a transport block of the downlink shared channel according to the network configuration information. Therefore, the first communication device sends second information to the second communication device.
[0244] For another example, when the first communication device schedules the downlink shared channel and the multicast service channel, it can send the second information to the terminal device that receives the downlink shared channel and the multicast service channel.
[0245] Furthermore, it is understood that the processes shown in Figure 10 and Figure 7 can be combined. For example, the second communication device can receive the multicast service channel based on the process shown in Figure 7. When the first communication device schedules both downlink shared channel transmission and multicast service channel transmission for one or more second communication devices, the first communication device can send second information to the second communication devices to reduce the buffer size corresponding to the coding block of the downlink shared channel, thereby receiving as much downlink shared channel and multicast service channel as possible.
[0246] According to the process shown in Figure 10 above, when the first communication device schedules the downlink shared channel and the multicast service channel, the first communication device can send second information to the second communication device so that the second communication device can determine the buffer size corresponding to the transport block of the downlink shared channel in order to receive the downlink shared channel and the multicast service channel as much as possible.
[0247] It is understood that, in order to achieve the functions in the above embodiments, the first communication device and the second communication device include hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
[0248] Figures 11 and 12 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first or second communication device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. The communication device can be a terminal device or an access network device, or it can be a module in the terminal device or access network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or it can be a logical node, logical module, or software that can implement all or part of the functions of the terminal device or access network device.
[0249] The communication device 1100 shown in Figure 11 includes a transceiver unit 1120 (or a communication module, for sending and receiving data). Optionally, the communication device 1100 shown in Figure 11 may further include a processing unit 1110 (or a processing module). The communication device 1100 can be used to implement the functions of the first or second communication device in the method embodiments shown in Figure 7 or Figure 10. For example, the transceiver unit 1120 can perform the receiving and sending actions performed by the first or second communication device in the method embodiments described above. The processing unit 1110 can perform other actions besides the sending and receiving actions performed by the first or second communication device in the method embodiments described above.
[0250] When the communication device 1100 is used to implement the function of the second communication device in the method embodiment shown in FIG7 above: the transceiver unit 1120 is used to receive first information; the processing unit 1110 is used to determine the buffer size corresponding to a transport block of the multicast service channel according to the first information; determine the buffer size corresponding to a coding block of the multicast service channel according to the buffer size corresponding to a transport block of the multicast service channel; and receive the multicast service channel through the transceiver unit 1120 according to the buffer size corresponding to a coding block of the multicast service channel.
[0251] When the communication device 1100 is used to implement the function of the first communication device in the method embodiment shown in FIG7 above: the processing unit 1110 is used to send first information through the transceiver unit 1120, the first information being used to determine the buffer size corresponding to a transport block of the multicast service channel; the processing unit 1110 is also used to determine the buffer size corresponding to a transport block of the multicast service channel; based on the buffer size corresponding to a transport block of the multicast service channel, determine the buffer size corresponding to a coding block of the multicast service channel; based on the buffer size corresponding to a coding block of the multicast service channel, send the multicast service channel through the transceiver unit 1120.
[0252] For a more detailed description of the processing unit 1110 and the transceiver unit 1120, please refer to the relevant description in the method embodiment shown in Figure 7 above, which will not be repeated here.
[0253] It should be understood that the transceiver unit 1120 in the embodiments of this application can be implemented by an interface circuit or interface circuit-related circuit components, and the processing unit 1110 can be implemented by a processor or processor-related circuit components.
[0254] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.
[0255] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it 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 all or part 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, or a server, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0256] The communication device 1200 shown in Figure 12 includes at least one processor 1210 and interface circuitry 1220. The at least one processor 1210 and interface circuitry 1220 may be coupled to each other. It is understood that interface circuitry 1220 may be a transceiver or an input / output interface. Optionally, the communication device 1200 may also include a memory 1230. Memory 1230 is used to store instructions executed by at least one processor 1210, or to store input data required for at least one processor 1210 to execute instructions, or to store data generated after at least one processor 1210 executes instructions.
[0257] When the communication device 1200 is used to implement the method embodiment shown in FIG7, at least one processor 1210 is used to implement the function of the processing unit 1110, and the interface circuit 1220 is used to implement the function of the transceiver unit 1120.
[0258] For example, consider a first communication device as a base station and a second communication device as a UE. When the aforementioned communication device is a chip applied to the UE, the UE chip implements the functions corresponding to the UE in the above method embodiments. For instance, when the UE chip receives information from the base station, it can be understood that the information is first received by other modules in the UE (such as a radio frequency module or antenna), and then sent to the UE chip by these modules. When the UE chip sends information to the base station, it can be understood that the information is first sent to other modules in the UE (such as a radio frequency module or antenna), and then sent to the base station by these modules.
[0259] When the aforementioned communication device is a chip applied to a base station, the base station chip implements the functions corresponding to the base station in the above method embodiments. For example, when the base station chip receives information from the UE, it can be understood that the information is first received by other modules in the base station (such as an RF module or antenna), and then sent to the base station chip by these modules. When the base station chip sends information to the UE, it can be understood that the information is sent down to other modules in the base station (such as an RF module or antenna), and then sent to the UE by these modules.
[0260] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be terminal devices or access network devices, or modules within those devices. Information transmission and reception can be between a terminal device and an access network device, such as between a UE and a base station. Information transmission and reception can also be between two base stations, such as between a CU and a DU. Furthermore, information transmission and reception can be between different modules within a single device, such as between a UE chip and other UE modules, or between a base station chip and other modules within that base station.
[0261] Based on the same concept, embodiments of this application also provide a possible communication system. This communication system may include one or more of a first communication device or a second communication device. The first communication device can be used to implement the technical solutions related to the first communication device in the above embodiments. The second communication device can be used to implement the technical solutions related to the second communication device in the above embodiments.
[0262] Based on the same concept, this application also provides a computer program product, which includes a computer program or instructions that, when run on a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.
[0263] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.
[0264] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
[0265] Based on the same concept, embodiments of this application also provide a chip, which may include at least one processor and may also include a memory (or the chip may be coupled to the memory), wherein the at least one processor executes program instructions in the memory to cause the chip to perform the methods provided in the above embodiments. Here, "coupling" refers to two components being directly or indirectly connected to each other, such as coupling referring to an electrical connection between two components.
[0266] Based on the same concept, embodiments of this application also provide a chip system, which includes at least one processor for supporting a computer device in implementing the functions involved in the first or second communication device in the above embodiments. In one possible implementation, the chip system further includes a memory for storing necessary programs and data of the computer device. The chip system may be composed of chips or may include chips and other discrete components.
[0267] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.
[0268] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a communication device. Of course, the processor and storage medium can also exist as discrete components in the communication device.
[0269] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program is a set of instructions that directs each step of an action of an electronic computer or other device with message processing capabilities. It is typically written in a programming language and runs on a target architecture. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be volatile or non-volatile, or it can include both types of storage media.
[0270] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0271] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" 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, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.
[0272] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.
Claims
1. A communication method, characterized in that, include: Receive the first message; Based on the first information, determine the buffer size corresponding to a transport block of the multicast service channel; The buffer size corresponding to a coding block of the multicast service channel is determined based on the buffer size corresponding to a transport block of the multicast service channel. The multicast service channel is received according to the buffer size corresponding to a coding block of the multicast service channel.
2. The method as described in claim 1, characterized in that, The first information includes terminal device type information or the buffer size corresponding to a transport block of the multicast service channel.
3. The method as described in claim 2, characterized in that, Determining the buffer size corresponding to a transport block of a multicast service channel based on the first information includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal device type information; The buffer size corresponding to one transport block of the multicast service channel is determined based on the number of soft channel bits.
4. The method as described in claim 2, characterized in that, Determining the buffer size corresponding to a transport block of a multicast service channel based on the first information includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal device type information; The buffer size corresponding to a transport block of the multicast service channel is determined based on the number of soft channel bits and at least one of a first scaling factor and the number of carriers; wherein the first scaling factor is greater than 0 and less than or equal to 1, and the number of carriers is the number of carriers used to carry the multicast service channel.
5. The method as described in claim 4, characterized in that, The first information also includes at least one of the first scaling factor and the number of carriers.
6. The method according to any one of claims 2-5, characterized in that, One transport block of the multicast service channel is transmitted on multiple non-continuous time units in the time domain; Determining the buffer size corresponding to a transport block of a multicast service channel based on the first information includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal type information; The buffer size corresponding to a transport block of the multicast service channel is determined based on the number of soft channel bits and the time interval; wherein the time interval indicates the interval between two adjacent time units in the plurality of non-contiguous time units.
7. The method according to any one of claims 1-6, characterized in that, One transport block of the multicast service channel is transmitted on multiple non-continuous time units in the time domain; The first information includes the number of time units and time interval information. The number of time units indicates the number of the plurality of non-contiguous time units, and the time interval information indicates the interval between two adjacent time units in the plurality of non-contiguous time units.
8. The method according to any one of claims 2-6, characterized in that, Also includes: Based on the terminal device type information, the first value is determined to be one of the multiple maximum bit counts of a transport block of the multicast service channel, and the first value is used to determine the maximum bit count of a transport block of the multicast service channel.
9. The method as described in claim 8, characterized in that, The first value is the maximum or minimum value among the plurality of maximum bit counts, or the first value is determined based on the configuration information of the network device.
10. The method according to any one of claims 1-9, characterized in that, Also includes: Receive the second message; Based on the second information, determine the buffer size corresponding to a transport block of the downlink shared channel.
11. The method as described in claim 10, characterized in that, The second information includes a first indication information and / or a second scaling factor; wherein the first indication information indicates the number of soft channel bits shared by the multicast service channel and the downlink shared channel, the number of soft channel bits being determined based on the type of terminal device, and the second scaling factor is greater than 0 and less than or equal to 1.
12. The method according to any one of claims 10-11, characterized in that, Also includes: Send a second indication message, which indicates that the terminal device expects to simultaneously receive the downlink shared channel and the multicast service channel; or... Send a third indication message, which indicates that the multicast service channel should be received preferentially; or... Send terminal device capability information, which indicates that the terminal device supports determining the buffer size corresponding to a transport block of the downlink shared channel based on network configuration information.
13. The method according to any one of claims 1-12, characterized in that, Also includes: The decision to receive the multicast service channel, or the downlink shared channel, or to prioritize receiving the downlink shared channel, or to forgo receiving the multicast service channel, is made when one of the following conditions is met: If, within a scheduling time interval, the multicast service channel and the downlink shared channel scheduled by the network side exceed the processing capacity of the terminal device; or... When the terminal device is operating in multi-carrier aggregation mode, if the multicast service channel and the downlink shared channel scheduled by the network side exceed the processing capacity of the terminal within a scheduling time interval; or, If the number of soft channel bits corresponding to the type of terminal device is exceeded by the multicast service channel and the downlink shared channel scheduled by the network side.
14. The method according to any one of claims 1-13, characterized in that, A transport block of the multicast service channel is transmitted in multiple non-continuous time units in the time domain.
15. The method according to any one of claims 1-14, characterized in that, Receiving the multicast service channel according to the buffer size corresponding to a coding block of the multicast service channel includes: De-rate matching is performed based on the buffer size corresponding to a coding block of the multicast service channel.
16. A communication method, characterized in that, include: Send first information, which is used to determine the buffer size corresponding to a transport block of a multicast service channel; Determine the buffer size corresponding to a transport block of the multicast service channel; The buffer size corresponding to a coding block of the multicast service channel is determined based on the buffer size corresponding to a transport block of the multicast service channel. The multicast service channel is sent according to the buffer size corresponding to a coding block of the multicast service channel.
17. The method as described in claim 16, characterized in that, Also includes: Send a second message, which is used to determine the buffer size corresponding to a transport block of the downlink shared channel.
18. The method as described in claim 17, characterized in that, The second information includes a first indication information and / or a second scaling factor; wherein the first indication information indicates the number of soft channel bits shared by the multicast service channel and the downlink shared channel, the number of soft channel bits being determined based on the type of terminal device, and the second scaling factor is greater than 0 and less than or equal to 1.
19. The method according to any one of claims 17-18, characterized in that, Also includes: Receive a second indication message, which indicates that the terminal device expects to simultaneously receive the downlink shared channel and the multicast service channel; or... Receive a third indication message, which indicates that the multicast service channel should be received preferentially; or, The terminal device receives terminal device capability information, which indicates that the terminal device supports determining the buffer size corresponding to a transport block of the downlink shared channel based on network configuration information.
20. The method according to any one of claims 16-19, characterized in that, The first information includes terminal device type information or the buffer size corresponding to a transport block of the multicast service channel.
21. The method as described in claim 20, characterized in that, Determining the buffer size corresponding to a transport block of a multicast service channel includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal device type information; The buffer size corresponding to one transport block of the multicast service channel is determined based on the number of soft channel bits.
22. The method as described in claim 20, characterized in that, Determining the buffer size corresponding to a transport block of a multicast service channel based on the first information includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal device type information; The buffer size corresponding to a transport block of the multicast service channel is determined based on the number of soft channel bits and at least one of a first scaling factor and the number of carriers; wherein the first scaling factor is greater than 0 and less than or equal to 1, and the number of carriers is the number of carriers used to carry the multicast service channel.
23. The method as described in claim 22, characterized in that, The first information also includes at least one of the first scaling factor and the number of carriers.
24. The method according to any one of claims 20-23, characterized in that, One transport block of the multicast service channel is transmitted on multiple non-continuous time units in the time domain; Determining the buffer size corresponding to a transport block of a multicast service channel includes: Based on the terminal device type information, determine the number of soft channel bits corresponding to the terminal type information; The buffer size corresponding to a transport block of the multicast service channel is determined based on the number of soft channel bits and the time interval; wherein the time interval indicates the interval between two adjacent time units in the plurality of non-contiguous time units.
25. The method according to any one of claims 16-24, characterized in that, One transport block of the multicast service channel is transmitted on multiple non-continuous time units in the time domain; The first information includes the number of time units and time interval information. The number of time units indicates the number of the plurality of non-contiguous time units, and the time interval information indicates the interval between two adjacent time units in the plurality of non-contiguous time units.
26. The method according to any one of claims 20-25, characterized in that, Also includes: Based on the terminal device type information, the first value is determined to be one of the multiple maximum bit counts of a transport block of the multicast service channel, and the first value is used to determine the maximum bit count of a transport block of the multicast service channel.
27. The method as described in claim 26, characterized in that, The first value is the maximum or minimum value among the plurality of maximum bit counts, or the first value is determined based on the configuration information of the network device.
28. The method according to any one of claims 16-27, characterized in that, A transport block of the multicast service channel is transmitted in multiple non-continuous time units in the time domain.
29. The method according to any one of claims 16-28, characterized in that, Sending the multicast service channel according to the buffer size corresponding to a coding block of the multicast service channel includes: Rate matching is performed based on the buffer size corresponding to a coding block of the multicast service channel.
30. A communication device, characterized in that, include: One or more processors are configured to perform the method as described in any one of claims 1-15, or to perform the method as described in any one of claims 16-29.
31. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed on the communication device, cause the communication device to perform the method as described in any one of claims 1-15, or the method as described in any one of claims 16-29.
32. A chip system, characterized in that, Includes a processor for supporting a computer device in implementing the method as claimed in any one of claims 1-15, or in implementing the method as claimed in any one of claims 16-29.
