CN110351003B

CN110351003B - Method and communication device for determining size of transmission block

Info

Publication number: CN110351003B
Application number: CN201810299445.2A
Authority: CN
Inventors: 王婷; 郭英昊; 王轶
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-04-04
Filing date: 2018-04-04
Publication date: 2021-12-28
Anticipated expiration: 2038-04-04
Also published as: WO2019192442A1; CN110351003A

Abstract

The invention provides a method and a communication device for determining the size of a transmission block. The application provides a method for determining TBS, comprising: the communication device determines a TBS table to be used from N candidate TBS tables, wherein the TBS table is used for determining TBS corresponding to transmitted or received data, and N is an integer greater than or equal to 2; and the communication device determines the TBS corresponding to the data according to the used TBS table. By the flexible TBS value searching mode, the communication device can flexibly determine the used TBS table according to the service requirement or the indication, and the transmission efficiency of the communication system is improved.

Description

Method and communication device for determining size of transmission block

Technical Field

The present application relates to the field of communications, and in particular, to a method and a communication apparatus for determining a transport block size in the field of communications.

Background

Data is transmitted between the network equipment and the terminal equipment through an air interface. For example, for a scenario in which the terminal device transmits data to the network device, before the data is transmitted through the antenna, the physical layer of the terminal device performs processing according to a specified format, where the processing may include: scrambling, modulation, layer mapping, precoding, resource mapping, and signal generation, among others.

The data may correspond to a Transport Block (TB) in the physical layer. The Transport Block Size (TBS) needs to be determined during processing.

However, in the process of determining the TBS, the prior art does not consider special requirements of services, such as Enhanced Voice Service (EVS) of the New Radio (NR) technology of the 5th Generation (5G), which results in wasted transmission resources and reduced transmission efficiency of the communication system.

Disclosure of Invention

The present application, in conjunction with various embodiments, provides a method, a communication device, and a system for determining a TBS size to improve system transmission efficiency.

It should be understood that, in the present application, "and/or" describes an association relationship of associated objects, it means that there may be three relationships, for example, "a, and/or, B", may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In a first aspect, an embodiment of the present application provides a method for determining a TBS size, including: the communication device determines a TBS table to be used from N candidate TBS tables, wherein the TBS table is used for determining TBS corresponding to transmitted or received data, and N is an integer greater than or equal to 2; and the communication device determines the TBS corresponding to the data according to the used TBS table. The TBS table considered for special services is designed by the TBS value searching mode, so that the communication device can flexibly determine the TBS table to be used according to service requirements or instructions, and the transmission efficiency of the communication system is improved.

In one possible implementation, a communication apparatus determining a TBS table to use from among N candidate TBS tables includes: and the communication device determines the used TBS table from the N candidate TBS tables according to the service type of the data. The used TBS table is selected according to the service type, so that the flexibility of the technical scheme is embodied, and the used TBS table is more targeted. The efficiency of the communication system is improved.

In a possible implementation manner, the communication apparatus is a terminal device, or is located in the terminal device; the communication device determines a TBS table to use from among N candidate TBS tables, and comprises: the communication device determines the used TBS table from the N TBS tables according to the instruction of the base station.

Optionally, the indication of the base station may include signaling sent by the base station to the terminal device.

Optionally, the indication of the base station may include characteristic information of control information sent by the base station to the terminal device, where the control information is used to schedule the data. The characteristic information of the control information comprises one or more of the following information: and the cyclic redundancy code of the control information checks the radio network temporary identifier RNTI scrambled by the CRC, the format of the control information, the type of the search space of the control information and the detection period of the control information. The indication mode can also be called as an implicit indication mode, and the signaling overhead of the base station can be saved.

In one possible implementation, at least one of the candidate TBS tables includes one or more of the following TBS values: 544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324.

These values are obtained for the voice service, so that the transmission efficiency of the voice service can be effectively improved.

In a possible implementation manner, the number of TBS tables used is one, or more.

In a second aspect, an embodiment of the present application provides another method for determining a TBS, including: the communication device determines the number of temporary information bits of the transmitted or received data; the communication device searches TBS corresponding to the data in a TBS table according to the number of bits of the temporary information; wherein the TBS table includes at least one of the following TBS values: 544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324.

These values are obtained for voice traffic, and therefore, the efficiency of voice traffic transmission can be improved. For example, when the TBS of the data to be transmitted is the same as the TBS in the table calculated according to the resource allocation, the most efficient resource utilization can be achieved, and the waste of the number of bits due to the padding bits during data transmission is avoided.

In a third aspect, an embodiment of the present application provides a communication device, including a processor and a memory, where the memory is used to store a program, and the processor calls the program stored in the memory to execute the following steps: determining a TBS table to be used from N candidate TBS tables, wherein the TBS table is used for determining a TBS corresponding to transmitted or received data, and N is an integer greater than or equal to 2; and determining the TBS corresponding to the data according to the used TBS table.

In one implementation, the communication device may be a terminal device or a network device.

In a possible implementation manner, the determining a TBS table to use from among the N candidate TBS tables includes: and determining the used TBS table from the N candidate TBS tables according to the service type of the data.

In a possible implementation manner, the communication apparatus further includes a communication interface, and the communication apparatus is a terminal device or is located in the terminal device; the TBS table determined to be used from among the N candidate TBS tables includes: and determining the used TBS table from the N candidate TBS tables according to the instruction of the base station.

In a fourth aspect, an embodiment of the present application provides a communication device, including a processor and a memory, where the memory is used to store a program, and the processor calls the program stored in the memory to execute the following steps: determining the number of temporary information bits of data to be transmitted or received; searching TBS corresponding to the data in a TBS table according to the bit number of the temporary information; wherein the TBS table includes at least one of the following TBS values: 544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324.

In a fifth aspect, an embodiment of the present application provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method of any one of the first to second aspects.

In a sixth aspect, an embodiment of the present application provides a chip system, including: a processor configured to enable a communication device to implement the method of any of the first to second aspects.

Drawings

FIG. 1 is a schematic diagram of a general hardware architecture of a handset;

FIG. 2 is a general hardware architecture of a base station;

fig. 3 is a flow chart of a method of determining TBS;

fig. 4 is a diagram of a TBS table;

FIG. 5 is a schematic diagram of a protocol stack model of a communication system;

FIG. 6 is a schematic block diagram of a communication device;

FIG. 7 is a schematic block diagram of another communication device;

fig. 8 is a hardware configuration diagram of a communication apparatus.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The embodiment of the present application may be applied to, but not limited to, a 5G mobile communication NR system, and may also be applied to a Long Term Evolution (LTE) system, for example, a long term evolution-advanced (LTE-a) system, an enhanced long term evolution-advanced (LTE) system, and other communication systems, and may also be extended to related cellular systems such as wireless fidelity (WiFi), global microwave access (wimax), and third generation partnership project (3 GPP), or may also be applied to future communication systems, and is not limited in particular.

The terminal device referred to in the embodiments of the present application may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.

Taking the terminal device as a mobile phone as an example, a general hardware architecture of the mobile phone is explained. As shown in fig. 1, the cellular phone 11 may include: radio Frequency (RF) circuitry 110, memory 120, other input devices 130, display screen 140, sensors 150, audio circuitry 160, I/O subsystem 170, processor 180, and power supply 190. Those skilled in the art will appreciate that the configuration of the handset shown in the figures is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, some components may be separated, or a different arrangement of components may be used. Those skilled in the art will appreciate that the display screen 140 belongs to a User Interface (UI), and the display screen 140 may include a display panel 141 and a touch panel 142. Although not shown, the mobile phone may further include a camera, a bluetooth module, and other functional modules or devices, which are not described herein again.

Further, processor 180 is coupled to RF circuitry 110, memory 120, audio circuitry 160, I/O subsystem 170, and power supply 190, respectively. The I/O subsystem 170 is connected to other input devices 130, the display screen 140, and the sensors 150, respectively. The RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for receiving downlink information from a base station and then sending the downlink information to the processor 180 for processing. The memory 120 may be used to store software programs and modules. The processor 180 executes various functional applications and data processing of the mobile phone, for example, methods and functions of the terminal device in the embodiments of the present application, by executing the software programs and modules stored in the memory 120. Other input devices 130 may be used to receive entered numeric or character information and generate key signal inputs relating to user settings and function controls of the handset. The display screen 140 may be used to display information input by or provided to the user and various menus of the handset, and may also accept user input. The sensor 150 may be a light sensor, a motion sensor, or other sensor. Audio circuitry 160 may provide an audio interface between the user and the handset. The I/O subsystem 170 is used to control input and output peripherals, which may include other device input controllers, sensor controllers, and display controllers. The processor 180 is a control center of the mobile phone 11, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone 11 and processes data by operating or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby performing overall monitoring of the mobile phone. A power supply 190 (e.g., a battery) is used to supply power to the above components, and preferably, the power supply may be logically connected to the processor 180 via a power management system, so that functions of managing charging, discharging, and power consumption are implemented via the power management system.

The network device in the embodiments of the present application may be a base station in various forms (such as a macro base station, a micro base station (also referred to as a small station)), a relay station, an access point, or the like, or may refer to a device in an access network that communicates with a wireless terminal over an air interface through one or more sectors. When the network device is a base station, the base station may be configured to convert a received air frame into an Internet Protocol (IP) packet, and serve as a router between the wireless terminal and the rest of the access network, where the rest of the access network may include an IP network. The base station may also be used to coordinate management of attributes for the air interface. In communication systems using different radio access technologies, names of devices having a base station function may be different, for example, a base station in a global system for mobile communication (GSM) or Code Division Multiple Access (CDMA) system is called a base station (BTS), a base station in a Wideband Code Division Multiple Access (WCDMA) system is called a node B (node B), a base station in an LTE system is called an evolved node B (eNB), a base station in an NR system is called a universal base station (gbb), and the like. The embodiment of the present application is not limited to this.

Further, a general hardware architecture of the base station is explained. As shown in fig. 2, the base station 12 may include an indoor Baseband processing Unit (BBU) 1201 and a Remote Radio Unit (RRU) 1202, the RRU1202 is connected to an antenna feed system (i.e., an antenna) 1203, the BBU 1201 and the RRU1202 may be detached or combined for use as needed, when the BBU 1201 and the RRU1202 are detached for use, the BBU 1201 and the RRU1202 are connected to each other through an optical fiber, and the RRU1202 and the antenna 1203 are connected to each other through a coaxial cable.

Some terms referred to in the embodiments of the present application are explained below.

A slot (slot), which is a unit of a resource for transmitting data in a time domain, generally includes one or more symbols and/or chips, and each symbol and/or chip may have the same or different transmission directions (states). The transmission direction may be uplink or downlink, or may be an uncertain (unknown) state or a flexible (flexible) state, and in these two states, the terminal device may not perform the transceiving processing but may be used for the internal processing of the terminal device. The time slot may be a time unit, which is used to represent a granularity in a time domain, and optionally, the time unit may also refer to other time units such as a subframe, a radio frame, a symbol, and the like, which is not limited in this application.

The TBS table may be used to select a TBS corresponding to data to be transmitted or data to be received. Specifically, the predefined may be predefined by a protocol, such as table 5.1.3.2-2 in section 5.1.3.2 of the third generation partnership project (3 GPP) Technical Specification (TS) 38.214 version 15.0.0 (v15.0.0). In this table, each TBS may be labeled with an index number.

The communication device may be a network device, a terminal device, or a chip located in the network device or the terminal device.

The number of temporary information bits, which may also be referred to as an intermediate number of information bits (intermediate number of information bits), refers to an intermediate amount obtained by temporary calculation in the process of determining the TBS corresponding to data transmission. Further, the TBS corresponding to the data to be transmitted/received may be obtained by looking up the TBS table according to the number of bits of the temporary information.

It should be noted that, unless otherwise specified, the numbers referred to in this application have units of bits (bits). Alternatively, in the embodiment of the present application, 8bits may be equivalent to 1 byte (byte), or 8bits may be equivalent to 1 octet (octet).

As an example of the following data TBS determination, in the prior art, the TBS determination step may include:

the method comprises the following steps: determining a number N of Resource Elements (REs) occupied by data_RE。

A Physical Resource Block (PRB) is a unit for characterizing resources, and may refer to a granularity in a frequency domain, for example, one PRB may include N1 subcarriers, for example, N1 ═ 12, or may refer to a granularity in a time-frequency domain, for example, one PRB may include M symbols, N2 subcarriers, and so on. Wherein N1, N2, M can be positive integers.

The physical resource block may also be referred to as a Resource Block (RB), a Virtual Resource Block (VRB), or the like, which is not limited in this application.

Firstly, the number N 'of REs of a Physical Downlink Shared Channel (PDSCH) allocated in one RB is determined according to formula (1)'_RE。

Wherein,

indicates the number of subcarriers of one PRB in the frequency domain,

indicates the number of symbols scheduled in a slot,

the number of REs occupied by demodulation reference signals (DMRSs) in one PRB in the slot may include, for example, overhead of a Code Division Multiplexing (CDM) group indicated in Downlink Control Information (DCI).

Representing overhead configured with the higher layer parameter Xoh-PDSCH, the overhead value may be 6,12, or 18 REs. If it is notIf the high-layer parameter Xoh-PDSCH is not configured, the value of Xoh-PDSCH is 0.

Secondly, calculating N according to the formula (2)_RE。

N_RE＝min(156,N'_RE)*n_PRBEquation (2);

wherein n is_PRBIs the number of PRBs allocated for the data. Min () represents taking the minimum of the two.

Step two: calculating the number of temporary information bits N according to equation (3)_info。

N_info＝N_RE*R*Q_mυ, equation (3).

Wherein, R represents a code rate, and may be determined by a Modulation Coding Scheme (MCS) indication (the MCS indication may include a modulation scheme and a code rate). Q_mIndicating the modulation scheme. And upsilon represents the number of layers of data mapping, and can be determined by the layer number indication information in the DCI or can be predefined.

Step three: judgment of N_infoWhether less than (or equal to) the first threshold value. For example, the first threshold may be one of 3824, 3848, and 8848, or other values, but the embodiment of the present application is not limited thereto.

If N is present_infoLess than (or equal to) the first threshold, the TBS is determined via branch 1. Otherwise, TBS is determined via branch 2.

Branch 1:

the TBS value is obtained by looking up a predefined TBS table in the protocol.

If calculated N_infoIf the TBS value is A, the TBS value is found by looking up a table to obtain a value which is greater than or equal to A and is closest to A.

Of course, it is also possible to pair N by equation (4) before looking up the table_infoQuantizing to obtain quantized temporary information bit number N'_infoAnd then look up a predefined table to obtain the TBS value.

Wherein

Indicating a rounding down.

As a specific example, assume that N 'is calculated'_infoAnd the TBS is found to be 368 according to the table 5.1.3.2-2 as 360.

And branch 2:

n 'is obtained through calculation of formula (5)'_info

Wherein,

round functions mean rounding up or rounding down.

If R is less than or equal to a second threshold value, e.g., 1/4, the TBS value may be calculated by equation (6),

wherein,

indicating rounding up.

Otherwise, if N'_infoGreater than or equal to a third threshold, e.g., 8424, the TBS value may be calculated by equation (7),

wherein,

if neither of the above conditions is satisfied, the TBS value can be calculated by equation (8).

On the other hand, the development of communication technology puts higher demands on various services including voice services. For example, voice traffic goes from narrowband communication to wideband communication to ultra wideband communication and full-bandwidth communication, enhancing intelligibility. For example, the speech coding scheme that can be used by the speech service in NR is EVS, and for the same speech frame, the transmission block sent by the EVS over the air interface is much smaller than the transmission block sent by other speech coding schemes over the air interface, which improves the transmission efficiency.

At the higher layer, the size of a packet is also calculated before the data flows to the physical layer, and may be referred to as a Media Access Control (MAC) Protocol Data Unit (PDU). The MAC PDU value is closely related to the TBS determined at the physical layer, that is, the design of the TBS value in the above-mentioned TBS table needs to consider the MAC PDU value to improve the transmission efficiency of the communication system.

Alternatively, the MAC PDU value may also be referred to as TBS in higher layers.

However, the TBS values in the TBS table mentioned above do not include TBS values suitable for special services such as voice services, for example, if the current table is used to determine the TBS value at the EVS, the transmission resource waste is inevitably caused, and the transmission efficiency and the performance of the communication system are reduced.

The embodiment of the application provides a flexible TBS value searching mode, and a TBS table considered for a special service is designed, so that a communication device can flexibly determine the TBS table to be used according to service requirements or instructions, and the transmission efficiency of a communication system is improved.

Example one

Fig. 3 provides a flow chart of a method of determining TBS. The method can be applied to the processing flow of data transmission and can also be applied to the processing flow of data reception. The method comprises the following steps:

301. the communication device determines a TBS table to be used from N candidate TBS tables, wherein the TBS table is used for determining TBS corresponding to transmitted or received data, and N is an integer greater than or equal to 2;

302. and the communication device selects the TBS corresponding to the data according to the used TBS table.

Here, the communication device is taken as a terminal device, and the terminal device has data to be transmitted as an example. Of course, as described above, the communication device may also be a network device, or the technical solution of the embodiment of the present application may also be applied to a data receiving processing flow, and a person skilled in the art can understand how to apply the technical solution to these scenarios by reading the technical solution of the present application, and the embodiment of the present application is not described again.

As mentioned above, only one TBS table is defined in the prior art, and the TBS values in the TBS table do not take into account the requirements of the special service. In the embodiment of the present application, N TBS tables are defined as candidate tables of the TBS table used by the communication apparatus. The N tables may include a TBS table in the prior art, that is, a table without considering special service requirements, and may further include a new TBS table, where a TBS value in the new TBS table includes a TBS value designed for a special service such as a voice service. The number of the new TBS tables may be 1 or more. When the number of the new TBS tables is 1, the N value is 2, and when the number of the new TBS tables is multiple, the N value is an integer greater than 2.

The following description will be given by taking the new TBS table as one table, that is, N is 2. And assume that the prior art TBS table is table 1 and the new TBS table is table 2.

As an implementation manner, in 301, the terminal device may determine, according to the service type of the data to be transmitted, a TBS table to be used from among 2 TBS tables candidate. For example, when the service type is a non-voice service such as a mobile bandwidth service, the TBS table in table 1 is selected as a used TBS table, and for example, when the service type is a voice service, the TBS table in table 2 is selected, or the TBS tables in table 1 and table 2 are selected as used TBS tables.

The TBS table used is determined according to the actual service type, so that the flexibility of the technical scheme is increased.

As another implementation manner, the terminal device in 301 may determine the TBS table to be used from among the 2 TBS tables candidates according to an instruction of the network device. The indication here may be a display indication or an implicit indication. The indication of the display indicates, for example, the TBS table used by the network device to the terminal device through signaling. The signaling may be higher layer signaling or physical layer signaling, and may be broadcast signaling or dedicated signaling (e.g., cell-level or UE-level signaling). The implicit indication may be based on the DCI characteristics of the scheduling data, with different DCI characteristics corresponding to different selection results. The DCI may be characterized by at least one of a Cyclic Redundancy Check (CRC) scrambled Radio Network Temporary Identity (RNTI), a DCI format, a characteristic of a search space, a detection period of a control channel, and a period of data transmission. The RNTI may include a cell radio network temporary identity (C-RNTI), a Temporary Cell (TC) -RNTI (TC-RNTI), a Configured Scheduling-RNTI (CS-RNTI), System Information (SI) -RNTI (SI-RNTI), a Random Access (RA) -RNTI (RA-RNTI), or a Paging (P) -RNTI (P-RNTI). The DCI format may be DCI format0_0, DCI format0_1, DCI format1_0, DCI format1_ 1, or the like. The feature of the search space may be at least one of an aggregation level, a candidate number, a search space format, and the like, and may also refer to a common search space or a UE-specific search space. The period of data transmission may be that data is transmitted or scheduled every 1 slot, or data is transmitted or scheduled every N slots, etc.

This is merely an example. For example, when the format of the DCI transmitted by the network device is DCI format0_0, it is equivalent to implicitly instructing the terminal device to determine the TBS table to use as table 1. When the format of the DCI transmitted by the network device is DCIformat0_1, it is equivalent to implicitly instructing the terminal device to determine the TBS table to use as table 2. When the format of the DCI transmitted by the network device is DCI format1_0, it is equivalent to implicitly instructing the terminal device to determine that the used TBS tables are table 1 and table 2. Other ways of implicitly indicating can be referred to this example.

Optionally, the correspondence between the format of the DCI and the table may be as shown above, or may be other similar correspondences, which is not limited in this application.

Optionally, the TBS values in table 1 and table 2 may not overlap at all, or may partially overlap.

Here, in an example 302, how the terminal device selects a TBS corresponding to data according to the used TBS table and the temporary information bit number of the data. Assume that the TBS values in table 1 and table 2 are shown in fig. 4.

The implementation mode is as follows:

according to 301, the table selected by the terminal device is table 1. If the temporary information bit number of the data obtained by starting the calculation according to the embodiment is 180, since the TBS value that is greater than the temporary information bit number and closest to the temporary information bit number in the table needs to be selected, the TBS value of the finally selected data is 184.

The implementation mode two is as follows:

according to 301, the table selected by the terminal device is table 2. If the temporary information bit number of the data obtained by starting the calculation according to the embodiment is 180, since the TBS value that is greater than the temporary information bit number and closest to the temporary information bit number in the table needs to be selected, the TBS value of the finally selected data is 192.

The implementation mode is three:

according to 301, the tables selected by the terminal device are table 1 and table 2. If the temporary information bit number of the data obtained by starting to calculate according to the embodiment is 180, the TBS value which is greater than the temporary information bit number and closest to the temporary information bit number in the table needs to be selected, so that the table 1 is searched, and the obtained TBS value is 184; looking up table 2, the TBS value obtained is 192. Then the smaller of the TBS values of the finally selected data is 184. If the bit number of the temporary information is 230, looking up the table 1, and obtaining a TBS value of 240; looking up table 2, the TBS value obtained is 232. Then the smaller of the TBS values of the finally selected data is 232.

The embodiment of the application provides a flexible TBS value searching mode, and the TBS table is designed aiming at the TBS table considered by special service, so that a communication device can flexibly determine the used TBS table according to service requirements or instructions, and the transmission efficiency of a communication system is improved.

Example two

The second embodiment provides a mode and a TBS table for determining TBS values related to special services in the table. The present embodiment may be based on the foregoing embodiments, and may also be independent of the foregoing embodiments.

The following discussion takes the special service as the voice service as an example.

As mentioned above, the determination of the TBS value in the TBS table is closely related to the data packet size at the higher layer, i.e. the MAC PDU value, so that, most directly, we can calculate the MAC PDU value corresponding to the data at the time of data transmission first and use at least one of these values as the value in the TBS table. For example, the TBS table may be a new TBS table designed specifically for the voice service (e.g., as a value of table 2 in an embodiment), or the TBS table may include TBS values of the voice service based on an existing TBS table, that is, the TBS values of the voice service may be added to the existing TBS table to form a more complete TBS table.

To calculate the MAC PDU value of the data of the voice service, a protocol model of the communication system needs to be briefly introduced. As shown in fig. 5, the protocol stack model of the communication system may include, from top to bottom, a real-time transport protocol (RTP) layer, a User Datagram Protocol (UDP) layer, an Internet Protocol (IP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer.

Optionally, for the NR system, a Service Data Adaptation Protocol (SDAP) layer may be further added between the IP layer and the PDCP layer to form an 8-layer model. For example, if the core network of LTE is accessed by the communication device, the SDAP layer is not available, and the data transmission may not need to consider the size of the SDAP header. The core network of the NR to which the communication device accesses may include the SDAP layer, and the data transmission may need to consider the size of the SDAP header.

Based on this, for voice traffic, its MAC PDU can be determined by equation (9) before transmission to the higher layer, i.e., the Physical (PHY) layer.

MAC PDU ═ real-time transport protocol (RTP) payload (payload) size + robust header compression (RoHC) header (header) size + layer 2(layer2, L2) header size, equation (9).

Where the RoHC header size may take different values for the speech frame and the silence insertion indicator (SID) frame, for example, it may take 2 bytes (16 bits), 3 bytes (24 bits), 6 bytes (48 bits) or other values, respectively. The L2header size may include the size of the MAC/RLC/PDCP header, or may also include other additional information bits that may be used to indicate or handle small changes, such as short buffer status report (short BSR), Power Headroom Report (PHR), etc.

Regarding the voice service, the EVS may specifically include the following modes corresponding to different coding modes and code rates respectively: primary primary, primary SID, primary2.8, primary7.2, primary8, primary9.6, primary13.2, primary16.4, primary24.4, primary32, primary48, primary64, primary96, primary128, adaptive multi-rate (AMR) Wideband (WB) Interoperation (IO) SID, AMR-WB IO 6.6, AMR-WB IO 8.85, AMR-WB IO 12.65, AMR-WB IO14.25, AMR-WB IO 15.85, AMR-WB IO 18.25, AMR-WB 19.85, AMR-WB IO 23.05, WB-IO 23.85, etc.

The AMR service may specifically include the following modes corresponding to different coding modes and code rates, respectively: AMR SID, AMR4.75, AMR5.15, AMR5.9, AMR6.7, AMR7.4, AMR7.95, AMR10.2, AMR12.2, AMR-WB SID, AMR-WB 6.6, AMR-WB8.85, AMR-WB12.65, AMR-WB14.25, AMR-WB15.85, AMR-WB18.25, AMR-WB 19.85, AMR-WB23.05, AMR-WB23.85, and the like.

The mode of the voice service may refer to coding (codec), coding mode (codec mode), bit rate (bits), coding rate (codec rate), or simply mode (mode), and the present application is not limited to this.

Several modes are selected from the above as examples and explained below:

table 1 below is a MAC PDU value calculated according to formula (9), and table 2 is 3GPP ts38.214v15.0.0 table 5.1.3.2-2.

	PTP payload	RoHC header	L2header	MAC PDU
					primary	48	24	40	112
AMR-WB IO SID	56	24	40	120
					primary7.2	144	24	40	208
AMR-WB IO 12.65	256	24	40	320
					primary 13.2	264	24	40	328
primary16.4	328	24	40	392
					AMR-WB IO 23.85	480	24	40	544
primary 24.4	488	24	40	552
					primary 64	1280	24	40	1344

TABLE 1

Index	TBS	Index	TBS	Index	TBS	Index	TBS
									1	24	31	336	61	1288	91	3624
2	32	32	352	62	1320	92	3752
								3	40	33	368	63	1352	93	3824
4	48	34	384	64	1416
								5	56	35	408	65	1480
6	64	36	432	66	1544
								7	72	37	456	67	1608
8	80	38	480	68	1672
								9	88	39	504	69	1736
10	96	40	528	70	1800
								11	104	41	552	71	1864
12	112	42	576	72	1928
								13	120	43	608	73	2024
14	128	44	640	74	2088
								15	136	45	672	75	2152
16	144	46	704	76	2216
								17	152	47	736	77	2280
18	160	48	768	78	2408
								19	168	49	808	79	2472
20	176	50	848	80	2536
								21	184	51	888	81	2600
22	192	52	928	82	2664
								23	208	53	984	83	2728
24	224	54	1032	84	2792
								25	240	55	1064	85	2856
26	256	56	1128	86	2976
								27	272	57	1160	87	3104
28	288	58	1192	88	3240
								29	304	59	1224	89	3368
30	320	60	1256	90	3496

TABLE 2

By comparing table 1 and table 2, it can be seen that the data in the last column of table 1, using the underlined data, is not in the TBS values of table 2, and therefore a TBS table can be designed, which can include these values: 328. 392, 544 and 1344.

Optionally, at least one of these values may be added to a new TBS table designed specifically for voice services to form table 3, or directly added to table 4 as in existing table 2.

For example, table 3 may be:

Index	TBS
			1	328
2	392
		3	544
4	1344

TABLE 3

For another example, table 4 may be (where underlined values are new values added according to table 1, and the new values are added in an ascending order together with the values in the existing table to form table 4):

Index	TBS	Index	TBS	Index	TBS	Index	TBS
									1	24	31	328	61	1192	91	3104
2	32	32	336	62	1224	92	3240
								3	40	33	352	63	1256	93	3368
4	48	34	368	64	1288	94	3496
								5	56	35	384	65	1320	95	3642
6	64	36	392	66	1344	96	3752
								7	72	37	408	67	1352	97	3824
8	80	38	432	68	1416
								9	88	39	456	69	1480
10	96	40	480	70	1544
								11	104	41	504	71	1608
12	112	42	528	72	1672
								13	120	43	544	73	1736
14	128	44	552	74	1800
								15	136	45	576	75	1864
16	144	46	608	76	1928
								17	152	47	640	77	2024
18	160	48	672	78	2088
								19	168	49	704	79	2152
20	176	50	736	80	2216
								21	184	51	768	81	2280
22	192	52	808	82	2408
								23	208	53	848	83	2472
24	224	54	888	84	2536
								25	240	55	928	85	2600
26	256	56	984	86	2664
								27	272	57	1032	87	2728
28	288	58	1064	88	2792
								29	304	59	1128	89	2856
30	320	60	1160	90	2976

TABLE 4

In table 1, the ROHC header size is 24 as an example, and it should be noted that the ROHC header size may have other values. Similarly, the L2header size may have other values. The size of the RTP payload can also have different RTP payload formats, and different RTP payload formats can have different values for voice services in the same mode.

Several possible RTP payload formats are as follows:

format1 (otherwise known as case 1): bandwidth-efficient mode (bandwidth-effective mode)

Format 2 (otherwise known as case 2): 8 byte alignment mode (octet-aligned mode)

Format 3 (otherwise known as case 3): load size under protection of compression format (compact formatted payload sizes)

Format 4 (otherwise known as case 4): coder-full format with out CMR byte under Coder Mode Request (CMR) byte

Format 5 (otherwise known as case 5): CMR byte lower header Full format (header-Full format with CMR byte)

The values in table 1 are values obtained based on case 1. For example, the size of the RTP payload may also be obtained in other formats.

Tables 5 and 6 show possible values of RTP payload size under different voice service modes and different RTP payload formats:

TABLE 5

TABLE 6

Based on the above discussion, each traffic mode will obtain different values of MAC PDU, i.e. RTP payload size, ROHC header size and L2header size will affect the values of MAC PDU.

Optionally, when calculating the MAC PDU size, in addition to considering the RTP payload size, the RoHC header size, and the L2header, it is also possible to consider the value of an additional (additional) header according to the actual situation of data transmission. Thus, each specific service will also get a different value of the MAC PDU, i.e. the size of the additional header will affect the value of the MAC PDU.

Based on this, for voice traffic, its MAC PDU can be determined by equation (10) before being transmitted to a higher layer, i.e., a Physical (PHY) layer.

MAC PDU ═ RTP payload size + RoHC header size + L2header size + additional header size, equation (10).

The additional header may also be referred to as an additional bit. It can be either independent of the L2header as given by equation (10) or can be calculated as part of the L2header, which is equivalent to the other extra information bits in the aforementioned L2header, and since the additional header is already calculated as part of the L2header, the MAC PDU can be determined by equation (9). Of course, this part of the header may also be named as other bits, which is not limited in this application.

Alternatively, as previously described, each specific service may also obtain a different value for the MAC PDU if the SDAP header size is considered.

Based on this, for voice traffic, its MAC PDU may be determined by equation (11) or equation (12) before being transmitted to a higher layer, i.e., to a Physical (PHY) layer.

MAC PDU equals RTP payload size + SDAP header size + RoHC header size + L2header size, equation (11).

MAC PDU ═ RTP payload size + SDAP header size + RoHC header size + L2header size + additional header size, equation (12).

If the values of the MAC PDU calculated by the above formulas are not in the TBS values of table 2, the TBS table can be designed in the same manner as described above. For example, at least one of these values may be taken as the value in table 3, or added to table 2 to form a new table 4.

For the above mentioned various factors affecting the MAC PDU value, such as at least one of RTP payload size, ROHC header size, L2header size, additional header size, and SDAP header size, further illustration is made:

alternatively, the following examples may be taken as independent embodiments, or may be combined with other examples or embodiments, and the present application is not limited thereto.

As an implementation, the ROHC header size is 24, and the L2header size is 48, where the L2header may be other additional information bits including a 16-bit PDCP header, an 8-bit MAC header, and 24 bits. The specific MAC PDU for each voice service may be as described in at least one item of table 7. Other service types are similarly available and are not described in detail.

TABLE 7

By comparing table 7 with table 2, it can be seen that the data in the last column of table 7, using the underlined data, is not in the TBS values of table 2, and therefore a TBS table can be designed, which can include these values: 216, 328, 400, and 560.

Alternatively, at least one of these values may be added to a new TBS table specifically designed for voice traffic to form a table similar to table 3, or directly added to a table similar to table 4 as in existing table 2.

As another implementation manner, the ROHC header size is 24, and the L2header size is 24, where the L2header may include a 16-bit PDCP header and an 8-bit MAC header. The specific MAC PDU for each voice service may be as described in at least one item of table 8. Other service types are similarly available and are not described in detail.

TABLE 8

By comparing table 8 with table 2, it can be seen that the data in the last column of table 8, using the underlined data, is not in the TBS values of table 2, and therefore a TBS table can be designed, which can include these values: 312, 376, 536, and 1328.

As another implementation, the ROHC header size is 24, and the L2header size is 64, where the L2header may be other additional information bits including a 16-bit PDCP header, an 8-bit RLC header, a 16-bit MAC header, and 24 bits. The specific MAC PDU for each voice service may be as described in at least one item of table 9. Other service types are similarly available and are not described in detail.

TABLE 9

By comparing table 9 with table 2, it can be seen that in the data in the last column of table 9, the data underlined is not in the TBS values of table 2, and therefore, a TBS table can be designed, which can include these values: 232, 344, 416, 568, and 1368.

As described above, the RTP payload size may be based on different RTP payload formats, and different RTP payload formats may have different values for voice services in the same mode.

For the 5 formats described above, the ROHC header size is 24, and the L2header size is 64, where the L2header may be other additional information bits including a 16-bit PDCP header, an 8-bit RLC header, a 16-bit MAC header, and 24 bits. The specific MAC PDU for each voice service may be as described in at least one of tables 10 to 14. Other service types are similarly available and are not described in detail.

Watch 10

TABLE 11

TABLE 12

Watch 13

TABLE 14

By comparing tables 10 to 14 with table 2, it can be seen that the data in the last column of tables 10 to 14, the underlined data is not included in the TBS values of table 2, and therefore a TBS table can be designed, which can include these values: 344,216,200,280,232,584,360,232,568 and 592.

Considering the influence factors on the MAC PDU value, for example, at least one of the RTP payload size, the ROHC header size, the L2header size, the optional header size, and the SDAP header size may have other values, and the MAC PDU value may be other values.

For example, values of the ROHC header size may include 24,48, 32, 16, 40, or other values; the L2header size may include 16,24, 20, 26, 28, 34, 32, 38, 40, 46, 44, 52, 48, 54, 56, 62, 60, 64, 68, or other values, wherein the MAC header size may include 0, 8, 16,24, or other values, the RLC header size may be 0, 8, 16,24, 32, 40, or other values, and the PDCP header size may be 0, 8, 24, 16, 32, 40, or other values; the additional header size may include 0, 16,24, 32, or other values; the SDAP header size may be 0, 8, or 16, or some other value. With these possible values, one skilled in the art can also obtain more values of MAC PDU in combination with any one of equations (9) to (12). For example, the following values can also be obtained: 1328. 44, 92, 100, 108, 156, 164, 172, 180, 188, 196, 236, 244, 264, 300, 308, 316, 324, 532, 540, 548, 560, and the like. The specific calculation method for obtaining these values is not described in detail in this application.

In combination with at least one implementation manner in this embodiment, if the TBS value is presented in a table, the communication apparatus may obtain the TBS value of the data in the following manner:

the communication device determines the number of temporary information bits of the transmitted or received data;

the communication device searches a TBS corresponding to the data in a TBS table according to the number of bits of the temporary information, wherein the TBS table includes at least one of the following TBS values:

328. 392, 544, 1344, 216, 400, 560, 312, 376, 536, 232, 344, 416, 568, 1368, 216,200,280, 584,360,232, 592, 1328, 44, 92, 100, 108, 156, 164, 172, 180, 188, 196, 236, 244, 264, 300, 308, 316, 324, 532, 540, 548 and 560.

According to the embodiment of the application, the existing TBS table is updated according to the special requirements of special services, such as voice services, so that the transmission efficiency and the performance of a communication system are improved.

EXAMPLE III

Embodiment three provides a mode and a TBS table for determining TBS values related to special services in the table. The present embodiment may be based on the first embodiment, or may be independent of the first embodiment.

The third embodiment also takes the special service as the voice service as an example for detailed discussion. It should be noted that, in this embodiment, the manner of calculating the MAC PDU value of the data of the voice service obtains the TBS value different from that in the existing 3GPP ts38.214v15.0.0 table 5.1.3.2-2, and when the TBS is presented by using only one table, the communication device obtains the TBS value of the transmitted or received data, which is consistent with the second embodiment and is not described herein again. Different from the second embodiment, when selecting the TBS value added to the existing table 5.1.3.2-2, this embodiment needs to comprehensively consider possible adjacent values, and ensure that two adjacent TBS values in the TBS table cannot be too close to each other, so that it is possible to avoid the processing complexity of the communication device from increasing due to too many TBS values of the updated table, and avoid too much modification to the existing 3GPP protocol.

For example, assume that the values obtained according to example two that may be added to the existing table are: 328. 392, 544, 1344, 232, 344, 416, 568, 1368, 312, 376, 1328.

Wherein, 328 is closer to TBS value 320 corresponding to index value 30 in table 5.1.3.2-2 (see table 2 in example two), the two values can be adjusted, 324 is added to the TBS value of existing table 5.1.3.2-2, and for original table 5.1.3.2-2, the original TBS value 328 is deleted.

Similarly, because 544 is closer to TBS 528 for index 40 in table 5.1.3.2-2 (see table 2 in example two), the two values can be adjusted by adding 536 to the TBS of the prior table 5.1.3.2-2 and deleting 528 from the prior table 5.1.3.2-2.

Similarly, because the TBS value 1320 corresponding to index 62 is closer in 1328 to table 5.1.3.2-2 (see table 2 in example two), the two values can be adjusted by adding 1324 to the TBS value of existing table 5.1.3.2-2 and deleting 1328 from the original TBS value of original table 5.1.3.2-2.

The calculation method for adjusting the TBS value may be an average value of two considered values, or may be other operations, which is not limited in the present application. If the calculated number is non-integer, then rounding up or rounding down may be further considered to obtain an integer value.

The TBS value thus finally added to the existing Table 5.1.3.2-2 may be: 392. 1344, 232, 344, 416, 568, 1368, 312, 376, 324, 536, 1324.

Optionally, at least one of these values may be added to a new TBS table designed for voice services to form another table. At this time, the value adjusted together with the value possibly added to the existing table, for example, at least one of 320, 528, 1320, etc., in the existing table may still be retained in the existing table without being deleted, and may of course be deleted from the existing table.

As an implementation manner, unlike the first embodiment, if the TBS value is presented in a table manner, then the TBS value of the data can be obtained for this embodiment in the following manner:

392，1344，232，344，416，568，1368，312，376，324，536，1324。

as an implementation manner, whether to adjust the TBS value obtained in the second embodiment may be determined by setting a threshold.

That is, if the difference between the obtained TBS value and a TBS value in the existing table 5.1.3.2-2 is smaller than (or equal to) a threshold, the TBS value obtained by the third embodiment is adjusted and added to the table 5.1.3.2-2 for updating. I.e., the last updated table, is such that the difference between two TBS values adjacent to the index number is less than (or equal to) the threshold.

The optional threshold value may be 0, 8, or 16, or other values. The specific values are not limited in this application.

Optionally, the threshold may be notified to the terminal by the base station, or may be predefined by a protocol, which is not limited in this application.

It should also be understood that the above description is intended to assist those skilled in the art in better understanding the embodiments of the present application and is not intended to limit the scope of the embodiments of the present application. It will be apparent to those skilled in the art from the above description that various equivalent modifications or changes may be made, and such modifications or changes also fall within the scope of the embodiments of the present application.

It should also be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic thereof, and should not constitute any limitation to the implementation process of the embodiments of the present application.

The method for sending the measurement report according to the embodiment of the present application is described in detail above with reference to fig. 1 to 5, and the communication apparatus according to the embodiment of the present application is described in detail below with reference to fig. 6 to 8. The communication apparatus embodiments correspond to the method embodiments and similar descriptions may refer to the method embodiments.

Example four

Fig. 6 is a schematic block diagram of a communication device according to an embodiment of the present application. It is to be understood that the communication device 600 shown in fig. 6 may be used to perform the relevant steps performed by the communication device of one embodiment to another. The communication device 600 includes: a first determination unit 601 and a second determination unit 602.

First determining section 601 determines a TBS table to be used for determining a TBS corresponding to data to be transmitted or received from among N candidate TBS tables, where N is an integer equal to or greater than 2.

A second determining unit 602, configured to determine a TBS corresponding to the data according to the used TBS table.

The first determining unit 601 may specifically be configured to:

and determining the used TBS table from the N candidate TBS tables according to the service type of the data.

Optionally, when the communication apparatus is a terminal device or is located in the terminal device, the first determining unit 601 may be specifically configured to:

and determining the used TBS table from the N candidate TBS tables according to the instruction of the base station.

Optionally, the indication of the base station is a signaling sent by the base station to the terminal device.

Optionally, the indication of the base station is feature information of control information sent by the base station to the terminal device, where the control information is used to schedule the data.

Optionally, the feature information of the control information includes one or more of the following information:

and the cyclic redundancy code of the control information checks the radio network temporary identifier RNTI scrambled by the CRC, the format of the control information, the type of the search space of the control information and the detection period of the control information.

Optionally, at least one of the candidate TBS tables includes one or more of the following TBS values:

544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324.

Optionally, the number of TBS tables used is one, or multiple.

Optionally, a difference between TBS values included in at least one of the candidate TBS tables is less than or equal to a preset threshold.

The embodiment of the application provides a flexible TBS value searching mode, and a TBS table specially considered for a special service is newly added on the premise of not changing the existing predefined TBS table, so that a communication device can flexibly determine the TBS table to be used according to service requirements or instructions, and the transmission efficiency of a communication system is improved.

Fig. 7 is a schematic block diagram of a communication device according to an embodiment of the present application. It is understood that the communication device 700 shown in fig. 7 can be used to perform the relevant steps performed by the communication device of one embodiment to another. The communication apparatus 700 includes: a determination unit 701 and a lookup unit 702.

A determining unit 701, configured to determine a temporary information bit number of data to be transmitted or received;

a searching unit 702, configured to search, according to the number of bits of the temporary information, a TBS corresponding to the data in a TBS table;

wherein the TBS table includes at least one of the following TBS values:

It should be noted that the above division of the units of the communication device 600 and the communication device 700 is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity or may be physically separated. And these units can be implemented entirely in software, invoked by a processing element; or may be implemented entirely in hardware; and part of the units can be realized in the form of calling by a processing element through software, and part of the units can be realized in the form of hardware. For example, the sending unit may be a processing element that is set up separately, or may be implemented by being integrated in a chip of the network device, or may be stored in a memory of the network device in the form of a program, and the function of the sending unit may be called and executed by a processing element of the network device. The other units are implemented similarly. In addition, all or part of the units can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, the steps of the method or the units above may be implemented by hardware integrated logic circuits in a processor element or instructions in software.

The above units may be one or more integrated circuits configured to implement the above methods, for example: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when the above units are implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling programs. As another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

EXAMPLE five

Fig. 8 is a schematic diagram of a hardware structure of a communication device 800 according to an embodiment of the present disclosure. The communication device 800 includes at least one processor 801, a communication bus 802, and at least one communication interface 804, and may also include a memory 803.

The processor 801 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication bus 802 may include a path that conveys information between the aforementioned components.

The communication interface 804 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 803 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), 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. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 803 is used for storing application program codes for executing the scheme of the application, and the processor 801 controls the execution. The processor 801 is configured to execute the application program codes stored in the memory 803, so as to implement the steps performed by the terminal device or the network device in embodiments 1 to 6 of the present application.

As one implementation, the processor 801 may include one or more CPUs.

As one implementation, the communication device 800 may include multiple processors. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The communication device 800 may also include an output device and an input device, as one implementation. The output device communicates with the processor 801 and may display information in a variety of ways. For example, the output device may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device is in communication with the processor 801 and may accept user input in a variety of ways. For example, the input device may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

In addition, as described above, the communication device 800 provided in the embodiment of the present application may be a chip, or a terminal device, or a network device, or a device having a similar structure in fig. 8. The embodiment of the present application does not limit the type of the communication apparatus 800.

The memory 803 may be located outside the communication device 800, for example, an off-chip memory.

In addition, the present application provides a chip system, where the chip system includes a processor, and is configured to support a communication device to implement the method for sending a measurement report according to the foregoing embodiments, for example, to determine a symbol of a demodulation reference signal used for transmitting a shared channel. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the communication device. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

It should be noted that, in the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or can comprise one or more data storage devices, such as a server, a data center, etc., that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of determining a transport block size, TBS, the method comprising:

the communication device determines a used TBS table from N TBS tables of candidates according to an instruction of a base station, wherein the TBS table is used for determining a TBS corresponding to transmitted or received data, N is an integer greater than or equal to 2, the TBS tables of the candidates comprise at least one TBS table corresponding to a special service and one TBS table not corresponding to the special service, the communication device is a terminal device or is positioned in the terminal device, and the special service is a voice service;

the communication device determines the TBS corresponding to the data according to the used TBS table;

wherein the indication of the base station comprises: the characteristic information of the control information sent by the base station, the control information being used for scheduling the data, the characteristic information of the control information including one or more of the following information: and the cyclic redundancy code of the control information checks the radio network temporary identifier RNTI scrambled by the CRC, the format of the control information, the type of the search space of the control information and the detection period of the control information.

2. The method of claim 1, wherein the indication of the base station is: and the base station sends signaling to the terminal equipment.

3. The method of claim 1 or 2, wherein at least one of the TBS table candidates comprises one or more of the following TBS values:

4. The method of claim 1 or 2, wherein the number of TBS tables used is one or more.

5. The method of claim 4, wherein a difference between TBS values included in at least one of the candidate TBS tables is less than or equal to a predetermined threshold.

6. A communication apparatus, wherein the communication apparatus is a terminal device or is located in the terminal device, and the communication apparatus comprises: a processor, a memory,

the memory is used for storing the program,

the processor is used for calling the program stored in the memory and executing the following steps:

determining a TBS table to be used from N candidate TBS tables according to an indication of a base station, wherein the TBS table is used for determining a TBS corresponding to transmitted or received data, N is an integer greater than or equal to 2, and the candidate TBS tables comprise at least one TBS table corresponding to a special service and one TBS table not corresponding to the special service;

determining a TBS corresponding to the data according to the used TBS table, wherein the special service is a voice service;

7. The communications apparatus of claim 6, wherein the indication of the base station is: and the base station sends signaling to the terminal equipment.

8. The communications apparatus of claim 6 or 7, wherein at least one of the candidate TBS tables includes one or more of the following TBS values:

9. The communication apparatus according to claim 6 or 7, wherein the used TBS table has one or more TBS tables.

10. The communications apparatus of claim 9, wherein a difference between TBS values included in at least one of the TBS candidate tables is less than or equal to a predetermined threshold.

11. A method of determining a transport block size, TBS, the method comprising:

the communication device searches a TBS corresponding to the data in a used TBS table according to the number of the temporary information bits, wherein the used TBS table is determined from N candidate TBS tables according to the indication of a base station, N is an integer greater than or equal to 2, the candidate TBS tables comprise at least one TBS table corresponding to a special service and one TBS table not corresponding to the special service, and the special service is a voice service; the TBS table used includes at least one of the following TBS values: 544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324;

12. A communication apparatus, wherein the communication apparatus is a terminal device or is located in the terminal device, and the communication apparatus comprises: a processor, a memory,

the memory is used for storing the program,

determining the number of temporary information bits of data to be transmitted or received;

according to the bit number of the temporary information, searching a TBS corresponding to the data in a used TBS table, wherein the used TBS table is determined from N candidate TBS tables according to the indication of a base station, N is an integer greater than or equal to 2, the candidate TBS table comprises at least one TBS table corresponding to a special service and one TBS table not corresponding to the special service, and the special service is a voice service; the TBS table used includes at least one of the following TBS values: 544. 1344, 216, 400, 560, 312, 1328, 232, 416, 1368, 200, 360, 592, 324, and 1324;