WO2024007291A1 - 调度资源的方法和通信装置 - Google Patents

调度资源的方法和通信装置 Download PDF

Info

Publication number
WO2024007291A1
WO2024007291A1 PCT/CN2022/104584 CN2022104584W WO2024007291A1 WO 2024007291 A1 WO2024007291 A1 WO 2024007291A1 CN 2022104584 W CN2022104584 W CN 2022104584W WO 2024007291 A1 WO2024007291 A1 WO 2024007291A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
buffer status
sent
compression
type
Prior art date
Application number
PCT/CN2022/104584
Other languages
English (en)
French (fr)
Inventor
唐子涵
马梦瑶
李佳徽
顾佳琦
颜敏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2022/104584 priority Critical patent/WO2024007291A1/zh
Publication of WO2024007291A1 publication Critical patent/WO2024007291A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • the embodiments of the present application relate to the field of wireless communication technology, and more specifically, to a method and communication device for scheduling resources.
  • layer 1 also known as the physical layer (PHY)
  • PHY physical layer
  • Layer 2 that is, the media access control layer (media access control, MAC)
  • MAC media access control
  • all operations at the physical layer and MAC layer assume that the data to be transmitted from the upper layer itself has no redundancy, or ignore the redundancy and only consider how to combat channel transmission errors. Therefore, only Use channel coding (CC).
  • CC channel coding
  • the data to be transmitted at the physical layer may have a certain degree of redundancy.
  • the compression algorithm of the application layer fails to fully utilize the redundancy in the data for compression, or the upper layer data is not compressed, and the air interface may
  • the generated raw data such as channel state information (CSI), positioning, imaging, environment reconstruction and other sensing data generated by the new sensing function of the air interface.
  • CSI channel state information
  • the physical layer uses a coding mode that separates compression and channel coding for data to be transmitted, or a coding mode that combines compression and channel coding, better transmission performance can be achieved than using only channel coding.
  • the existing communication protocols of cellular systems do not support the above coding mode of the physical layer. If the above coding mode is introduced in the physical layer, it will cause uplink resource scheduling problems, such as uplink resource mismatch.
  • This application provides a method for scheduling resources, which can support the physical layer to adopt a coding mode in which compression and channel coding are separated, or a coding mode in which compression and channel coding are combined, without causing uplink resource scheduling problems.
  • the first aspect provides a method for scheduling resources, which can be applied to the sending end of wireless communication and can also be applied to the chip or chip system of the sending end.
  • the sending end may refer to the sending end of data transmission.
  • the following description takes the sending end as the terminal device as an example.
  • the method includes:
  • the terminal device sends a buffer status report to the network device, and the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device;
  • the terminal device sends compressed information of the uplink data to be sent to the network device.
  • the compression information indicates compression parameters related to physical layer processing of the uplink data to be sent.
  • the physical layer processing includes first encoding the transport block TB, and the first encoding is compression and A coding mode in which channel coding is separated, or the physical layer processing includes performing second coding on multiple sub-TBs obtained according to the TB, and the second coding is a coding mode in which compression and channel coding are combined;
  • the terminal device receives resource scheduling information from the network device.
  • the resource scheduling information is used to instruct the network device to allocate air interface resources for the uplink data to be sent.
  • the air interface resources are determined based on the data volume and compression parameters of the uplink data to be sent.
  • the terminal device sends a buffer status report to the network device to report the amount of uplink data to be sent.
  • the terminal device also sends compressed information of the uplink data to be sent to the network device.
  • the compressed information Indicates compression parameters related to physical layer processing of the uplink data to be sent.
  • the physical layer processing may include a coding mode in which TB is compressed or channel coding is separated (a coding mode of SSCC), or the physical layer processing may include a coding mode in which a plurality of sub-TBs obtained according to the TB are respectively compressed and channel coded jointly (JSCC). encoding mode).
  • the network device schedules air interface resources for the uplink data to be sent by the terminal device based on the data volume and compression information of the uplink data to be sent. This can solve the problem of introducing a coding mode that separates compression and channel coding at the physical layer, or a coding mode that combines compression and channel coding. The problem of uplink resource mismatch will then arise.
  • the method further includes:
  • the terminal device sends the first uplink data on the air interface resource.
  • the first uplink data is obtained by first encoding the first transmission block TB at the physical layer, or the first uplink data is obtained by performing the first encoding on the first TB at the physical layer. Multiple sub-TBs are obtained by performing second encoding respectively, and the first TB is obtained by data grouping the uplink data to be sent according to the compression parameters.
  • the resource scheduling information includes resource indication information and modulation and coding strategy MCS information
  • the method further includes:
  • the terminal device determines the packet length based on the resource indication information and MCS information
  • the terminal device performs data packetization on the uplink data to be sent according to the packet length and compression parameters, and obtains the first TB, where the estimated compressed length of the uplink data to be sent contained in the first TB is less than or equal to the packet length;
  • the terminal device performs the physical layer processing on the first TB to obtain the first uplink data.
  • This implementation introduces the SSCC or JSCC coding mode into the physical layer, providing a feasible physical layer processing mechanism.
  • a resource scheduling method which can be applied to the receiving end of wireless communication and can also be applied to the chip or chip system of the receiving end.
  • the receiving end may refer to the receiving end of data transmission.
  • the following description takes the receiving end as a network device as an example. The method includes:
  • the network device receives a buffer status report from the terminal device.
  • the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device;
  • the network device receives compressed information of the uplink data to be sent from the terminal device.
  • the compression information indicates compression parameters related to physical layer processing of the uplink data to be sent.
  • the physical layer processing includes first encoding the transport block TB, and the first encoding is A coding mode in which compression and channel coding are separated, or the physical layer processing includes performing second coding on multiple sub-TBs obtained according to the TB, and the second coding is a coding mode in which compression and channel coding are combined;
  • the network device sends resource scheduling information to the terminal device.
  • the resource scheduling information is used to instruct the network device to allocate air interface resources for the uplink data to be sent.
  • the air interface resources are determined based on the data volume and compression parameters of the uplink data to be sent.
  • the method also includes:
  • the network device receives the first uplink data from the terminal device on the air interface resource.
  • the first uplink data is obtained by the first encoding of the first transmission block TB by the physical layer of the terminal device, or the first uplink data is obtained by the terminal device.
  • the physical layer performs second encoding on the plurality of sub-TBs obtained according to the first TB, and the first TB is obtained by data grouping the uplink data to be sent according to the compression parameters.
  • the compression parameter is a compression ratio
  • the compression ratio is the ratio of the estimated post-compression length and the pre-compression length of the uplink data to be sent;
  • the compression parameter is the estimated compressed length of the uplink data to be sent.
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a first type of buffer status report
  • the first type of buffer status report is used for Indicates the amount of raw data to be sent
  • the first type of buffer status report includes the logical channel group identification LCG ID field and the buffer status field.
  • the LCG ID field has multiple different values. The multiple different values correspond to different native data types.
  • the buffer status field Used to indicate the amount of data to be sent of the native data type corresponding to the LCG ID field.
  • a corresponding type of buffer status report is designed for the physical layer native data type, which is used to report the physical layer native data.
  • the buffer status report of the first type includes a compression information field, and the compression information field carries compression information of the data to be sent of the native data type corresponding to the LCG ID field.
  • the buffer status report for the physical layer native data type may also include the compression information of the physical layer native data, providing an implementable mechanism for the UE to report the compression information of the physical layer native data.
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a second type of buffer status report
  • the second type of buffer status report is used for Indicates the amount of raw data to be sent
  • the second type of buffer status report is an extension of the short buffer status report or long buffer status report of the media access control MAC layer.
  • the second type of buffer status report contains the logical channel group identifier LCG ID field and buffer District status field, where,
  • the LCG ID field includes x bits, and the buffer status field is one.
  • the x bits have y different values.
  • p values respectively correspond to different native data types.
  • the q values respectively correspond to different logical channel types.
  • the buffer status field indicates the native data type or logical channel type corresponding to the first value to be sent.
  • the LCG ID field includes z bits. k bits among the z bits satisfy the bit mapping relationship with the k native data types. r bits among the z bits satisfy the bit mapping relationship with the r logical channel types. The z bits satisfy the bit mapping relationship. Each bit in has a second value or a third value. When the j-th bit among the z bits is the second value, the native data type or logical channel type corresponding to the j-th bit is selected.
  • the extended BSR can be reused for reporting native data of the physical layer, which can save the introduction of buffer status reporting bands for native data of the physical layer. bit overhead.
  • the buffer status report of the second type also includes a compressed information field.
  • the compression information field carries the compression information of the data to be sent of the native data type or logical channel type corresponding to the first value;
  • the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry w bits of the corresponding native data type or logical channel type of data to be sent. Compress information.
  • the expanded BSR can also include compression information, providing an implementable mechanism for the UE to report compression information of physical layer native data.
  • a third aspect provides a communication device, which has the function of implementing the method in the first aspect or any possible implementation of the first aspect.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above functions.
  • a fourth aspect provides a communication device having the function of implementing the method in the second aspect or any possible implementation of the second aspect.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the above functions.
  • a communication device including a processor and a memory.
  • a transceiver may also be included.
  • the memory is used to store computer programs
  • the processor is used to call and run the computer programs stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the first aspect or any possible implementation of the first aspect.
  • a communication device including a processor and a memory.
  • a transceiver may also be included.
  • the memory is used to store computer programs
  • the processor is used to call and run the computer programs stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the second aspect or any possible implementation of the second aspect.
  • a communication device including a processor and a communication interface, the communication interface being used to receive data and/or information, and transmit the received data and/or information to the processor; the processing The processor processes the data and/or information; and, the communication interface is also used to output the data and/or information processed by the processor, so that the communication device performs the first aspect, or the first aspect method in any possible implementation.
  • a communication device including a processor and a communication interface, the processor processes data and/or information to be sent; the communication interface is used to output data and/or information processed by the processor, So that the communication device performs the method in the second aspect, or any possible implementation manner of the second aspect.
  • a communication device including at least one processor coupled to at least one memory, and the at least one processor is configured to execute a computer program or instructions stored in the at least one memory to The communication device is caused to perform the method in the first aspect, or any possible implementation of the first aspect.
  • a communication device including at least one processor coupled to at least one memory, and the at least one processor is configured to execute a computer program or instructions stored in the at least one memory to The communication device is caused to perform the method in the second aspect, or any possible implementation manner of the second aspect.
  • a computer-readable storage medium is provided.
  • Computer instructions are stored in the computer-readable storage medium.
  • the computer instructions are run on a computer, the first aspect, or the second aspect, or these aspects are achieved.
  • the method in any possible implementation is executed.
  • a twelfth aspect provides a computer program product, the computer program product comprising computer program code, when the computer program code is run on a computer, the first aspect, or the second aspect, or these aspects Methods in any possible implementation of either aspect are executed.
  • a thirteenth aspect provides a wireless communication system, including the communication device according to the third aspect and the communication device according to the fourth aspect.
  • Figure 1 is a schematic diagram of the uplink resource application, scheduling and data transmission process in a cellular system.
  • Figure 2 is a schematic diagram of the relationship between uplink resource scheduling and coding and modulation.
  • Figure 3 is a schematic diagram of the relationship between uplink resource scheduling and coding modulation when the physical layer of a cellular system adopts SSCC.
  • Figure 4 is a schematic diagram of uplink resource allocation after SSCC or JSCC is introduced into the physical layer.
  • FIG. 5 is a schematic architecture diagram of a communication system according to the resource scheduling method provided by this application.
  • Figure 6 is a schematic flow chart of the resource scheduling method provided by this application.
  • Figure 7 is a schematic diagram of counting the sparsity of the uplink data to be sent in the buffer by PB and estimating the compression ratio.
  • Figure 8 is a schematic diagram of using an 8-bit quantization compression ratio and adding it to the short BSR or long BSR for reporting.
  • Figure 9 is a schematic structural diagram of a BSR for native data types.
  • Figure 10 is a schematic diagram of the terminal device packetizing data according to the packet length and compression ratio.
  • Figure 11 is a schematic block diagram of a communication device provided by this application.
  • Figure 12 is a schematic structural diagram of a communication device provided by this application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems, such as the 5th generation (5G) system or new radio (NR) system, long term evolution (LTE) system, long term evolution Advanced technology (long term evolution-advanced, LTE-A) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. It can also be applied to future communication systems, such as the sixth generation mobile communication system. In addition, it can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, and machine-type communication (machine type).
  • 5G 5th generation
  • NR new radio
  • LTE long term evolution
  • LTE-A long term evolution Advanced technology
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • future communication systems such as the sixth generation mobile communication system.
  • D2D device-to-device
  • V2X vehicle-to
  • MTC mobile communications
  • IoT Internet of things
  • WiFi wireless-fidelity
  • WIMAX worldwide interoperability for microwave access
  • 3gpp third generation partner program
  • the communication system applicable to this application may include one or more transmitting ends, and one or more receiving ends.
  • one of the sending end and the receiving end may be a terminal device, and the other may be a network device.
  • the cache status report can be (buffer status report, BSR) in 5G
  • the physical uplink shared channel can be (physical uplink shared channel, PUSCH) in 5G.
  • the terminal equipment may also be called user equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, mobile terminal (mobile terminal, MT), remote station, remote terminal, Mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • UE user equipment
  • access terminal subscriber unit
  • user station mobile station
  • mobile station mobile station
  • mobile terminal mobile terminal
  • remote station remote terminal
  • Mobile device user terminal
  • terminal wireless communication device
  • user agent or user device may be a device that provides voice and/or data connectivity to users, and may be used to connect people, things, and machines, such as handheld devices and vehicle-mounted devices with wireless connection functions.
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), tablet computer (pad), notebook computer, handheld computer, mobile Internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc.
  • the UE may be used to act as a base station.
  • a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc.
  • the device used to implement the function of the terminal may be a terminal, or may be a device capable of supporting the terminal to implement the function, such as a chip system or a chip, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the network device may be a device with wireless transceiver functions.
  • the network device may be a device that provides wireless communication function services. It is usually located on the network side, including but not limited to the fifth generation (5th generation, 5G) communication system.
  • gNodeB, gNB next generation base station
  • network equipment may include centralized unit (CU) nodes, or include distributed unit (DU) nodes, or RAN equipment including CU nodes and DU nodes, or include control plane CU nodes.
  • CU centralized unit
  • DU distributed unit
  • RAN equipment including CU nodes and DU nodes, or include control plane CU nodes.
  • user plane CU nodes, as well as RAN equipment of DU nodes, or the network equipment can also be wireless controllers, relay stations, vehicle equipment and wearable devices in the cloud radio access network (cloud radio access network, CRAN) scenario.
  • the base station may be a macro base station, a micro base station, a relay node, a donor node, or a combination thereof.
  • a base station may also refer to a communication module, modem or chip used in the aforementioned equipment or devices.
  • the base station can also be a mobile switching center and equipment that performs base station functions in D2D, V2X, and M2M communications, network-side equipment in 6G networks, equipment that performs base station functions in future communication systems, etc.
  • the base station can support networks with the same or different access technologies without limitation.
  • the device used to implement the function of the network device may be a network device, or may be a device that can support the network device to implement the function, such as a chip system or a chip, and the device may be installed in the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of uplink resource application, scheduling and data transmission processes in a cellular system.
  • the base station schedules uplink resources for the UE based on the UE's buffer status report and power headroom and other information.
  • the BSR is mainly used to tell the base station the amount of data to be transmitted in each logical channel buffer of the UE, so that the base station can decide how many air interface resources to schedule for the UE based on this information.
  • the resource scheduling of the base station is informed to the UE by sending downlink control information (DCI) on the downlink control channel, for example, DCI format 0 (abbreviated as DCI 0).
  • DCI downlink control information
  • the fields related to resource scheduling in DCI 0 are mainly resource indication and MCS indication.
  • the resource indication is used to indicate the time-frequency resource for sending uplink data
  • the MCS indication is used to indicate what channel coding rate is used on the time-frequency resource. and modulation order.
  • Figure 2 is a schematic diagram of the relationship between uplink resource scheduling, coding, and modulation.
  • the resource indication and the MCS indication jointly determine the size of the UE's physical layer transport block (TB) (that is, the code block before channel coding), the code rate of the channel coding, and the code block size after channel coding. .
  • the channel-encoded code blocks are modulated and mapped to corresponding air interface resources for transmission.
  • the unit of data transmission in the physical layer is a transport block (TB). If the TB itself still has a certain degree of redundancy, a coding mode that separates compression and channel coding, or a coding that combines compression and channel coding, is introduced in the physical layer. mode, the redundancy of the data to be transmitted in the physical layer can be used to further improve data transmission performance.
  • the physical layer of the cellular system does not support the coding mode that separates compression and channel coding, nor does it support the coding mode that combines compression and channel coding.
  • the protocol layer for example, the signaling process of resource scheduling
  • source coding is usually also understood as compression. Therefore, the industry usually calls the coding mode that separates compression and channel coding (separate source and channel coding (SSCC)), and refers to compression and channel coding.
  • the coding mode of joint coding is called joint source and channel coding (JSCC). Therefore, SSCC coding in the following refers to the coding mode in which compression and channel coding are separated, and JSCC refers to the coding mode in which compression and channel coding are combined.
  • Figure 3 is a schematic diagram of the relationship between uplink resource scheduling and coding modulation when the physical layer of the cellular system adopts SSCC.
  • the resource indication and MCS indication in the downlink control information of the base station jointly determine the TB size (length L in Figure 3), coding modulation and resource mapping (resource size). It can be seen that resource indication and MCS indication are essential for successful decoding at the receiving end.
  • SSCC is introduced in the physical layer
  • the data must first be compressed (lossy or lossless), and the TB of length L scheduled by the base station is compressed into a new TB of length L'.
  • a CRC can be added after the new TB. (such as CRC') or padding. Without loss of generality, padding is usually filled with 0s before channel coding.
  • the base station When scheduling uplink resources, the base station needs to refer to the BSR and other information reported by the UE to decide how many air interface resources to allocate to the UE.
  • the main consideration is channel error protection. If data compression is introduced at the physical layer, and the BSR sent by the UE only reports the amount of data to be sent before compression, the base station does not know the amount of data after compression, and the uplink resources scheduled by the base station will be wasted, as shown in the figure As shown in 4, Figure 4 is a schematic diagram of uplink resource allocation after SSCC or JSCC is introduced into the physical layer.
  • the UE Before receiving the scheduling information from the network side (specifically, it may refer to the resource indication and the MCS indication), it does not know what size of data to compress, that is, the UE does not know the size of L.
  • JSCC uses the redundancy of the data to be sent to simultaneously compress and channel the data to be sent, it can essentially be considered to use a puncturing mode that is different from channel coding and based on the redundancy of the data to be sent. Higher channel coding bit rate. Equivalently, it can also be considered that the redundancy of the information source is used to reduce the consumption of air interface resources while maintaining the same error protection effect. Therefore, it can be seen as a data compression before channel coding. Therefore, using JSCC in the physical layer will cause uplink resource allocation problems and the uplink resource allocation problems caused by introducing SSCC in the physical layer. the same.
  • this application provides a resource scheduling method, aiming to solve the uplink resource mismatch caused by the introduction of SSCC or JSCC in the physical layer (for example, the size of the air interface resources allocated by the network side for uplink data is larger than the size actually sent by the UE). air interface resources required for uplink data).
  • the physical layer not only considers channel error protection, but also uses the redundancy of the data to be sent in the physical layer, and uses a coding mode in which compression and channel coding are separated for the data, or a combination of compression and channel coding. encoding mode.
  • FIG. 5 is a schematic architecture diagram of a communication system suitable for the resource scheduling method provided by this application.
  • the resource scheduling method provided by this application is mainly applicable to the scenario of uplink data transmission between network equipment and terminal equipment, and can also be applied to data transmission between terminal equipment, that is, sidelink ,SL) data transmission, this application does not limit this. Therefore, the sending end in this article may refer to the terminal in uplink data transmission, or may refer to the sending terminal in sidelink data transmission. Similarly, the receiving end may refer to a network device in uplink data transmission or a receiving terminal in sidelink data transmission. The following uses uplink data transmission as an example to describe the technical solution of this application.
  • the terminal device reports a buffer status report to the network device, and the buffer status report is used to indicate the amount of uplink data to be sent.
  • the terminal device sends compression information of the uplink data to be sent to the network device, and the compression information indicates compression parameters related to physical layer processing of the uplink data to be sent.
  • the network device schedules air interface resources for the uplink data to be sent by the terminal device based on the data volume and compression parameters of the uplink data to be sent, which can avoid the mismatch of air interface resources scheduled by the network device after introducing SSCC or JSCC into the physical layer of the terminal device.
  • the terminal device in the embodiment of the present application can be the terminal device 120 or 130 as shown in Figure 5, and the network device can be the network device 110 as shown in Figure 5. What is shown in Figure 5 is only an example.
  • the communication system may also include other communication devices, such as more terminal devices, or more network devices, without limitation.
  • Figure 6 is a schematic flow chart of a resource scheduling method provided by this application.
  • the terminal device sends a buffer status report to the network device.
  • the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device.
  • the uplink data to be sent here may refer to data from the application layer, or may be native data of the physical layer, without limitation.
  • the following will provide a detailed introduction to the buffer status report of the physical layer native data reported by the terminal device to the network side.
  • the terminal device sends compression information of the uplink data to be sent to the network device, where the compression information indicates compression parameters related to physical layer processing of the uplink data to be sent.
  • physical layer processing may include:
  • the plurality of sub-TBs obtained according to the TB are respectively subjected to second coding, and the second coding is a coding mode combining compression and channel coding.
  • Network devices receive buffer status reports from end devices, as well as compression information.
  • the network device sends resource scheduling information to the terminal device.
  • the resource scheduling information is used to instruct the network device to allocate air interface resources for the uplink data to be sent by the terminal device.
  • the air interface resources are determined based on the uplink data to be sent and compression parameters of the terminal device. of.
  • the terminal device receives resource scheduling information from the network device.
  • the physical layer of the terminal device introduces a coding mode that separates compression and channel coding, or a coding mode that combines compression and channel coding.
  • the terminal device reports a buffer status report of the uplink data to be sent to the network device.
  • the compression information of the uplink data to be sent will be reported.
  • the compression information is the compression ratio (that is, the estimated compression ratio) estimated by the terminal device based on the uplink data to be sent before sending the buffer status report, or it can also be estimated.
  • the compressed size of the uplink data to be sent (that is, the estimated compressed length).
  • the terminal device sends compressed information of the uplink data to be sent to the network device, which can assist the network device in scheduling the uplink resources to avoid the network device not knowing the compression information related to the physical layer processing of the terminal device.
  • Sending uplink data schedules air interface resources, resulting in a mismatch between the scheduled air interface resources and the amount of actually sent uplink data.
  • the method 600 may also include step 640.
  • the terminal device sends the first uplink data on the air interface resource.
  • the network device receives the first uplink data from the terminal device.
  • the first uplink data is obtained by performing the first encoding on the first TB by the physical layer of the terminal device, or the first TB is obtained by performing the second encoding on multiple sub-TBs obtained according to the first TB.
  • the first TB is obtained by the physical layer of the terminal device performing data packetization on the uplink data to be sent according to the compression parameters.
  • the terminal device can estimate the compression ratio of the uplink data to be sent through a variety of different implementations, and only some examples are given below.
  • the radio link control (RLC) and packet data convergence protocol (PDCP) of the terminal device need to Add the following process to estimate the compression ratio:
  • the packet sparsity of the data in the buffer of each logical channel (group) is counted, and then the compression ratio of the uplink data to be sent is estimated based on the sparsity.
  • the uplink data to be sent in the buffer is divided into several preprocessing blocks (PB) of size N s , and then sparsity statistics are performed on these PBs.
  • Figure 7 is a schematic diagram of counting the sparsity of the uplink data to be sent in the buffer by PB and estimating the compression ratio. After the sparsity of each PB is statistically obtained, the compressed length of the uplink data to be sent in the buffer of the logical channel (group) is estimated based on the sparsity (also called estimated compressed length in the text).
  • the pre-compression length of the uplink data to be sent in the buffer is L bits
  • the TB is divided into K PBs according to the length N s
  • the sparsity of the i-th PB is recorded as S i (0 ⁇ S i ⁇ 1)
  • the compressed length of the sent uplink data is estimated to be
  • the above way of estimating the compression ratio is only an example.
  • Another feasible calculation method is: randomly select several segments from the uplink data to be sent in the buffer. Usually the length of the selected data is much smaller than the total amount of data (that is, the data length L), and then use a data compression algorithm. Compress the selected data, and count the length before and after compression of the selected data to obtain an estimate of the compression ratio.
  • the compression algorithm used in this calculation method may be online arithmetic code, Lempel-Ziv algorithm, etc., without limitation. It should be noted that the compression algorithm should be consistent with the compression algorithm used by the physical layer of the terminal device for data compression.
  • terminal devices sending compressed information to network devices.
  • the terminal device can quantify the compression ratio and report the quantified information.
  • the terminal device quantizes the compression ratio of each logical channel (group) into several levels, and uses fixed x bits to represent the quantized compression ratio information.
  • the quantized compression ratio information can be reported to the network along with the BSR. side.
  • the quantized compression ratio information and BSR can be reported through the medium access control-control element (MAC CE).
  • MAC CE medium access control-control element
  • the compression ratio can be quantized to one of 256 levels, and then 8 bits are used to indicate the quantization level.
  • the quantization level can be added to the short BSR (short BSR) or long BSR (long BSR) for reporting, that is, the compression information in this application can be reported by extending the short BSR or long BSR, as follows Introduction in Figure 8.
  • FIG 8 is a schematic diagram of using an 8-bit quantization compression ratio and adding it to the short BSR or long BSR for reporting.
  • Short BSR is usually suitable for reporting only the cache status of one logical channel group or one type of native data.
  • the short BSR includes LCG ID and buffer status fields.
  • the LCG ID uses 3 bits to identify the number of a logical channel group, and the following 5 bits are the buffer status field, which is used to indicate the amount of data in the buffer corresponding to the logical channel group.
  • Long BSR can be suitable for reporting the cache status of multiple logical channel groups or multiple types of native data at the same time.
  • LCG1 ⁇ LCG8 form an 8-bit bitmap, and the 8 bits are divided into corresponding 8 different logical Channel group type.
  • the value of a certain bit in the 8 bits is 0, which means that the logical channel group corresponding to this bit is not selected.
  • the value is 1, which means that the logical channel group corresponding to this bit is selected.
  • the data amount of the buffer corresponding to the selected logical channel group is attached to the subsequent buffer status (buffer status) field in the same order as the bitmap.
  • the data amount of the buffer of each selected logical channel is determined by 8 bits. instruct.
  • the uplink data to be sent by the terminal device may be native data of the physical layer.
  • BSRs for different native data types can be added.
  • the physical layer native data may include positioning data, reconstructed environment data, sensory imaging data, etc., and may also be other types of physical layer native data, without limitation.
  • the first type of BSR may include a logical channel group identification LCG ID field and a buffer status field, where the LCG ID field has (or corresponds to) multiple different values, and the multiple different values correspond to different native data types. ;
  • the buffer status field is used to indicate the amount of data in the buffer. It should be understood that when the value of the LCG ID field corresponds to a certain native data type, the buffer status field indicates the amount of data to be sent of the native data of the native data type.
  • the first type of BSR may include an LCG ID field, a buffer status field, and a compression information field.
  • the first type of BSR also includes a compression information field for indicating compression information (eg, compression ratio) of the native data to be sent.
  • the compression information field is used to indicate the amount of data to be sent of the native data type corresponding to the LCG ID field.
  • the LCG ID field of the first type of BSR corresponds to different native data types.
  • the LCG ID field of the first type of BSR includes 4 bits. When the value of the 4 bits is 0000, it indicates the positioning data type corresponding to the first type of BSR; accordingly, the buffer status field is used to Indicates the data amount of the physical layer native positioning data to be sent; if a compression information field is also included, the compression information field is used to indicate the compression information of the physical layer native positioning data to be sent.
  • the buffer status field is used to indicate the data amount of the physical layer native perceptual imaging data to be sent; if it is also A compression information field is included, and the compression information field is used to indicate the compression information of the physical layer native sensing imaging data to be sent.
  • the BSR used to report physical layer native data can multiplex a short BSR or multiplex a long BSR, but the short BSR or multiplex long BSR needs to be expanded.
  • the extended BSR is called the second type BSR.
  • the LCG ID field of the short BSR or long BSR can be extended to support more LCG IDs, and the extra LCG IDs are used to correspond to different native data types.
  • the LCG ID field and buffer status field of the short BSR or long BSR are extended.
  • the extended BSR i.e., the second type of BSR
  • the LCG ID field and the buffer status field includes the LCG ID field and the buffer status field.
  • the short BSR is expanded to obtain the expanded BSR.
  • the extended BSR includes an LCG ID field and a buffer status field.
  • the LCG ID field includes x bits
  • the x bits have (or correspond to) y values
  • p values among the y values correspond to different native data types
  • q among the y values Each value corresponds to a different logical channel type.
  • the buffer status field is used to indicate the amount of data to be sent of the native data type or logical channel type corresponding to the first value.
  • p+q ⁇ y,x,y,p and q are all integers.
  • p+q ⁇ y it means that the y values include reserved values.
  • y 2x .
  • the long BSR is expanded to obtain the expanded BSR.
  • the extended BSR includes the LCG ID field and buffer status field.
  • the LCG ID field includes z bits, k bits among the z bits satisfy the bit mapping relationship with k native data types, and r bits among the z bits satisfy the bit mapping relationship with the r logical channel types.
  • Each bit among the z bits has a second value or a third value. When a certain bit among the z bits has a second value, it means that the native data type or logical channel type corresponding to the bit is selected. When this bit takes the third value, it means that the native data type or logical channel type corresponding to this bit is not selected.
  • w bits among the z bits are the second value
  • there are w buffer status fields in the extended BSR and the w buffer status fields are respectively used to indicate the native data corresponding to the w bits.
  • the second value is 1, and the third value is 0, and is not limited to other values.
  • the second type of BSR also contains a compression information field.
  • the expanded BSR contains a compressed information field.
  • the expanded BSR includes an LCG ID field, a buffer status field and a compressed information field.
  • the compression information field carries the compression information of the data to be sent of the native data type or logical channel type corresponding to the first value.
  • the extended BSR includes the LCG ID field, and the LCG ID field contains z bits.
  • w bits among the z bits are the second value, it means that the native data type and/or logical channel type corresponding to the w bits is selected.
  • the extended BSR includes w buffer status fields. and w compressed information fields.
  • the w buffer status fields are respectively used to indicate the data volume of the native data type and/or the logical channel type corresponding to the w bits
  • the w compression information fields respectively carry the w bits corresponding to the data amount. Compressed information of data to be sent of native data type or logical channel type.
  • Figure 9 is a schematic structural diagram of a BSR for native data types.
  • the LCG ID field is increased by 1 bit, extending from the original 3 bits to 4 bits. Therefore, the LCG ID field can indicate 8 LCG IDs from the original, and the extended In order to indicate 16 LCG IDs, 8 more LCG IDs can be indicated. The additional 8 LCG IDs can respectively correspond to 8 native data types.
  • the buffer status field is increased by 1 bit, extending from the original 5 bits to 6 bits.
  • the expanded BSR also includes a compression information field. Taking the compression information as the compression ratio CR as an example, the compression information field may be a CR field. For example, the CR field contains 6 bits. As can be seen, in this example, the total length of the short BSR is extended to 16 bits.
  • the extended BSR is an example of the above-mentioned second type of BSR.
  • the LCG ID field of the extended BSR includes a total of 16 bits, of which 8 bits correspond to different logical channel types.
  • the additional 8 bits and 8 native data types meet the requirements of bitmap. Relationship, each bit corresponds to a native data type.
  • the expanded BSR also includes the selected The amount of data to be sent of the native data type or logical channel type.
  • the expanded BSR also includes compression information of the selected native data type or logical channel type of data to be sent. Therefore, in this design, if w bits among the z bits contained in the LCG ID field are 1, then the expanded BSR includes w buffer status fields, which are used to report the corresponding w bits. The amount of data to be sent of native data type and/or logical channel type.
  • the expanded BSR also includes w compression information fields, which respectively carry the compression information of the native data type and/or logical channel type corresponding to the w bits of data to be sent.
  • the buffer status field and/or the CR field each contain 8 bits, which are not limited.
  • the above provides a detailed description of the terminal device's estimation of the compression ratio of the uplink data to be sent, and the specific implementation of BSR for the terminal device to report native data to the network device.
  • the terminal device sends the first uplink data to the network device. Specifically, the terminal device sends the first uplink data to the network device on the physical uplink shared channel.
  • the physical uplink shared channel can be (physical uplink shared channel, PUSCH).
  • the terminal device multiplexes the first uplink data and UCI to the PUSCH for sending.
  • UCI uplink control information
  • the first uplink data is obtained by first encoding the first TB by the physical layer of the terminal device, or by performing second encoding on multiple sub-TBs obtained according to the first TB, and the first TB is the terminal
  • the physical layer of the device packs the uplink data to be sent according to the compression parameters.
  • the resource scheduling information includes the resource indication and the MCS indication.
  • the terminal device calculates the packet length (TB size) based on the resource indication and MCS indication.
  • the calculation method of the packet length can refer to the specific implementation of determining TBS (TB size) in NR.
  • the terminal device packetizes the uplink data to be sent according to the packet length and compression parameters to obtain the first TB.
  • the terminal device estimates the compressed length of the uplink data to be sent based on the compression parameters until the estimated compressed length fills the packet length, at which time the first TB is obtained. In some cases, the uplink data to be sent is not enough to fill the packet length.
  • the estimated compressed length of the uplink data to be sent contained in the first TB is less than or equal to the group packet length.
  • the first encoding may be performed on the first TB, or multiple sub-TBs may be obtained based on the first TB, and then the plurality of sub-TBs may be subjected to second encoding respectively, without limitation.
  • the terminal device when packaging, specifically packages the RLC PDUs in the buffer of each logical channel group.
  • each RLC PDU is packaged.
  • the RLC PDU and raw data in the buffer of the logical channel group are packaged to obtain the first TB.
  • FIG 10 is a schematic diagram of a terminal device packetizing data according to the packet length and compression ratio.
  • the RLC layer segments/reassembles the RLC SDU corresponding to each logical channel group to match the MAC SDU size allocated by the MAC layer. After segmentation/reassembly, the RLC SDU is encapsulated with an RLC header and submitted as an RLC PDU. to the MAC layer.
  • the MAC layer plays a scheduling role and is responsible for allocating the physical resources corresponding to this transmission to several logical channel groups. The length of the RLC PDU of each logical channel group can be different.
  • RLC PDU is called MAC SDU at the MAC layer.
  • MAC SDUs are multiplexed into one MAC PDU and sent out through the physical layer channel.
  • One MAC PDU can carry data from multiple different logical channel groups.
  • MAC PDU is called TB.
  • One TB is used to carry one MAC PDU, and the size of the TB is determined by the number of physical resources allocated to the TB and the MCS.
  • the packet length is denoted as T.
  • the terminal device estimates the compressed length of the uplink data to be sent based on the compression ratio until the estimated compressed length fills T, as shown in Figure 10 S 1 +S 2 +S 3 +S 4 ⁇ T, at this time, obtains the first TB.
  • subsequent operations may be to compress the first TB at the physical layer, and then perform channel coding, rate matching, modulation, and resource mapping on the compressed TB.
  • the subsequent operation can also be to perform JSCC processing on the first TB at the physical layer.
  • preprocessing process is roughly as follows: preset 2 Q sparsity ranges, and then divide the first TB into B PBs according to a fixed length. For example, each PB The length is N s . Then multiple PBs are combined according to the sparsity. For example, PBs with sparsity in the same sparsity range are combined into a sub-TB, and 2 Q sub-TBs are obtained from this combination.
  • a control information sub-TB is created, and the control information sub-TB is used to indicate information about the sparsity of each of the B PBs.
  • the control information sub-TB may indicate the index of the sparsity range corresponding to the sparsity of each of the B PBs.
  • the length of the control information sub-TB is B ⁇ Q bits, and both B and Q are positive integers. It can be seen that a total of 2 Q sub-TBs and one control information sub-TB are obtained according to the first TB, that is, the multiple sub-TBs obtained according to the first TB described in this article. Then, perform JSCC on the multiple sub-TBs.
  • each of the plurality of sub-TBs is independently subjected to the second encoding, that is, each sub-TB is independently processed using a coding mode that combines compression and channel coding.
  • the compression rate of the control information sub-TB is 1.
  • the resource multiplexing of different sub-TBs can be determined on the network side and the terminal side according to fixed rules.
  • UCI can include one or more of the following types: hybrid automatic repeat request acknowledgment (HARQ-ACK), channel state information (channel state information) ,CSI).
  • HARQ-ACK hybrid automatic repeat request acknowledgment
  • channel state information channel state information
  • CSI may include CSI part 1 and CSI part 2.
  • Figure 11 is a schematic block diagram of a communication device provided by this application.
  • the communication device 1000 includes a processing unit 1100 , a receiving unit 1200 and a sending unit 1300 .
  • the communication device 1000 may correspond to the terminal device in the embodiment of the present application.
  • each unit of the communication device 1000 is used to implement the following functions:
  • the first coding is a coding mode in which compression and channel coding are separated, or the physical layer processing includes performing second coding on multiple sub-TBs obtained according to the TB, and the second coding is compression and channel coding. Coding patterns for coding unions;
  • the receiving unit 1200 is configured to receive resource scheduling information from the network device.
  • the resource scheduling information is used to instruct the network device to allocate air interface resources for the uplink data to be sent.
  • the air interface resources are allocated according to the The amount of uplink data to be sent is determined by the compression parameters.
  • the sending unit 1300 is also used to:
  • the first uplink data is sent on the air interface resource, and the first uplink data is obtained by performing the first encoding on the first transport block TB by the physical layer of the communication device, or the first uplink data is
  • the physical layer of the communication device is obtained by performing the second encoding on a plurality of sub-TBs obtained according to the first TB, which is obtained by data grouping the uplink data to be sent according to the compression parameters. of.
  • the compression parameter is a compression ratio, which is the ratio of the estimated post-compression length and the pre-compression length of the uplink data to be sent; or,
  • the compression parameter is the estimated compressed length of the uplink data to be sent.
  • the resource scheduling information includes resource indication information and modulation and coding strategy MCS information
  • the processing unit 1100 is used to:
  • the packet length and the compression parameter perform data packetization on the uplink data to be sent to obtain the first TB, wherein the estimated compressed length of the uplink data to be sent contained in the first TB Less than or equal to the packet length;
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a first type of buffer status report
  • the first type of buffer status report is used To indicate the data amount of the raw data to be sent
  • the first type of buffer status report includes a logical channel group identification LCG ID field and a buffer status field.
  • the LCG ID field has multiple different values, and the multiple different values respectively correspond to different native data types.
  • the buffer status field is used to indicate the amount of data to be sent of the native data type corresponding to the LCG ID field.
  • the first type of buffer status report includes a compression information field, and the compression information field carries the compression of the data to be sent of the native data type corresponding to the LCG ID field. information.
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a second type of buffer status report.
  • the second type of buffer status report is used To indicate the data amount of the raw data to be sent;
  • the second type of buffer status report is an extension of the short buffer status report or the long buffer status report of the media access control MAC layer, and the second type of buffer status report includes a logical channel group identifier LCG ID field and buffer status field, where,
  • the LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, and p values among the y values correspond to different native data respectively. type, q values among the y values respectively correspond to different logical channel types.
  • the LCG ID field includes z bits, k bits among the z bits and k native data types satisfy a bit mapping relationship, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. relationship, each bit among the z bits has a second value or a third value, and when the j-th bit among the z bits is the second value, the j-th bit The corresponding native data type or logical channel type is selected. When the j-th bit among the z bits is the third value, the native data type or logical channel type corresponding to the j-th bit is not selected.
  • the second type of buffer status report also includes a compression information field.
  • the compression information field carries the compression information of the data to be sent of the native data type or logical channel type corresponding to the first value;
  • the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the native data types corresponding to the w bits or The compressed information of the data to be sent of the logical channel type.
  • the communication device 1000 may correspond to the network device in the embodiment of the present application.
  • each unit of the communication device 1000 is used to implement the following functions:
  • Receiving unit 1200 used for:
  • the compression information indicating compression parameters related to physical layer processing of the uplink data to be sent, where the physical layer processing includes processing a transport block
  • the TB performs first coding, and the first coding is a coding mode in which compression and channel coding are separated.
  • the physical layer processing includes performing second coding on multiple sub-TBs obtained according to the TB, and the second coding is compression. Coding mode combined with channel coding;
  • the sending unit 1300 is configured to send resource scheduling information to the terminal device.
  • the resource scheduling information is used to instruct the communication device to allocate air interface resources for the uplink data to be sent.
  • the air interface resources are allocated according to the uplink data to be sent.
  • the amount of uplink data is determined by the compression parameters.
  • the sending unit 1300 is also used to:
  • the first uplink data is obtained by performing the first encoding on the first transmission block TB by the physical layer of the terminal device, or, The first uplink data is obtained by the physical layer of the terminal device performing the second encoding on multiple sub-TBs obtained according to the first TB.
  • the first TB is obtained by encoding the to-be-sent data according to the compression parameters.
  • the uplink data is obtained through data grouping.
  • the compression parameter is a compression ratio, which is the ratio of the estimated post-compression length and the pre-compression length of the uplink data to be sent; or,
  • the compression parameter is the estimated compressed length of the uplink data to be sent.
  • the resource scheduling information includes resource indication information and modulation and coding strategy MCS information.
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a first type of buffer status report
  • the first type of buffer status report is used To indicate the data amount of the raw data to be sent
  • the first type of buffer status report includes a logical channel group identification LCG ID field and a buffer status field.
  • the LCG ID field has multiple different values, and the multiple different values respectively correspond to different native data types. .
  • the first type of buffer status report includes a compression information field
  • the compression information field carries the compression information of the data to be sent of the native data type corresponding to the LCG ID field.
  • the uplink data to be sent is native data of the physical layer
  • the buffer status report is a second type of buffer status report.
  • the second type of buffer status report is used To indicate the data amount of the raw data to be sent;
  • the second type of buffer status report is an extension of the short buffer status report or the long buffer status report of the media access control MAC layer, and the second type of buffer status report includes a logical channel group identifier LCG ID field and buffer status field, where,
  • the LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, and p values among the y values correspond to different native data types respectively. , q values among the y values respectively correspond to different logical channel types.
  • the LCG ID field includes z bits, k bits among the z bits and k native data types satisfy a bit mapping relationship, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. relationship, each bit among the z bits has a second value or a third value, and when the j-th bit among the z bits is the second value, the j-th bit The corresponding native data type or logical channel type is selected. When the j-th bit among the z bits is the third value, the native data type or logical channel type corresponding to the j-th bit is not selected.
  • the second type of buffer status report also includes a compression information field.
  • the compression information field carries the compression information of the data to be sent of the native data type or logical channel type corresponding to the first value;
  • the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the native data types corresponding to the w bits or The compressed information of the data to be sent of the logical channel type.
  • the receiving unit 1200 and the sending unit 1300 can also be integrated into a transceiver unit or an input and output unit, having both receiving and sending functions, which is not limited here.
  • the processing unit 1100 is configured to perform processing and/or operations implemented internally by the terminal device in addition to actions of sending and receiving.
  • the receiving unit 1200 is configured to perform the receiving action of the terminal device, and the sending unit 1300 is configured to perform the sending action of the terminal device.
  • the sending unit 1300 performs the sending action in steps 610 and 620 ; the receiving unit 1200 performs the receiving action in step 630 .
  • the processing unit 1100 performs the following processing in each method embodiment: determining the grouping length according to the resource indication and the MCS indication; performing grouping according to the grouping length and compression information to obtain the first TB, etc.
  • the processing unit 1100 is configured to perform processing and/or operations implemented internally by the network device in addition to actions of sending and receiving.
  • the receiving unit 1200 is configured to perform the receiving action of the network device, and the sending unit 1300 is configured to perform the sending action of the network device.
  • the receiving unit 1200 performs the receiving actions in steps 610 and 620 .
  • the receiving unit 1200 performs the action received in step 640.
  • the sending unit 1300 performs the sending action in step 630.
  • the processing unit 1100 performs the following processing in each method embodiment: determining the air interface resources to be scheduled according to the data volume and compression information of the uplink data to be sent by the terminal device in the received buffer status report.
  • Figure 12 is a schematic structural diagram of a communication device provided by this application.
  • the communication device 10 includes: one or more processors 11 , one or more memories 12 and one or more communication interfaces 13 .
  • the processor 11 is used to control the communication interface 13 to send and receive signals
  • the memory 12 is used to store a computer program
  • the processor 11 is used to call and run the computer program from the memory 12, so that the communication device 10 executes the method described in the embodiments of the present application. Processing performed by end devices or network devices.
  • the processor 11 may have the function of the processing unit 1100 shown in FIG. 11
  • the communication interface 13 may have the function of the receiving unit 1200 and/or the sending unit 1300 .
  • the processor 11 may be used to perform processing or operations performed internally by the communication device
  • the communication interface 13 may be used to perform operations of sending and/or receiving of the communication device.
  • the communication device 10 may be a terminal device in the method embodiment.
  • the communication interface 13 may be a transceiver of the terminal device.
  • a transceiver may include a receiver and/or a transmitter.
  • the processor 11 may be a baseband device of the terminal device, and the communication interface 13 may be a radio frequency device.
  • the communication device 10 may be a chip (or chip system) installed in the terminal device.
  • communication interface 13 may be an interface circuit or an input/output interface.
  • the communication device 10 may be a network device in the method embodiment.
  • the communication interface 13 may be a transceiver of the network device.
  • a transceiver may include a receiver and/or a transmitter.
  • the processor 11 may be a baseband device of a network device, and the communication interface 13 may be a radio frequency device.
  • the communication device 10 may be a chip (or chip system) installed in a network device.
  • communication interface 13 may be an interface circuit or an input/output interface.
  • the dotted box behind the device indicates that there can be more than one device.
  • the memory and the processor in the above device embodiments may be physically independent units, or the memory may be integrated with the processor, which is not limited herein.
  • the present application also provides a computer-readable storage medium.
  • Computer instructions are stored in the computer-readable storage medium. When the computer instructions are run on the computer, the operations performed by the terminal device in each method embodiment of the present application are performed. and/or processing is performed.
  • This application also provides a computer-readable storage medium.
  • Computer instructions are stored in the computer-readable storage medium. When the computer instructions are run on the computer, the operations performed by the network device in each method embodiment of the application are caused and/or or processing is performed.
  • this application also provides a computer program product.
  • the computer program product includes computer program code or instructions.
  • the operations and/or operations performed by the terminal device in each method embodiment of the application are performed. or processing is performed.
  • the computer program product includes computer program code or instructions.
  • the operations and/or processes performed by the network device in each method embodiment of the application are performed. be executed.
  • the present application also provides a chip.
  • the chip includes a processor.
  • a memory used to store a computer program is provided independently of the chip.
  • the processor is used to execute the computer program stored in the memory, so that a device equipped with the chip executes Operations and/or processes performed by the terminal device in any method embodiment.
  • the chip may also include a communication interface.
  • the communication interface may be an input/output interface, or an interface circuit, etc.
  • the chip may further include the memory.
  • the application also provides a chip.
  • the chip includes a processor.
  • a memory used to store computer programs is provided independently of the chip.
  • the processor is used to execute the computer program stored in the memory, so that the device installed with the chip executes any Operations and/or processes performed by network devices in method embodiments.
  • the chip may also include a communication interface.
  • the communication interface may be an input/output interface, or an interface circuit, etc.
  • the chip may further include the memory.
  • processors there may be one or more processors, one or more memories, and one or more memories.
  • this application also provides a communication device (for example, it can be a chip or a chip system), including a processor and a communication interface.
  • a communication device for example, it can be a chip or a chip system
  • the communication device The interface is used to receive data and/or information to be processed, and the processor processes the data and/or information.
  • the communication interface is also used to send (or output) data and/or information processed by the processor.
  • This application also provides a communication device (for example, it can be a chip or a chip system), including a processor and a communication interface.
  • a communication device for example, it can be a chip or a chip system
  • the communication interface is The processor is used to receive data and/or information to be processed; the processor processes the data and/or information; and the communication interface is used to send (or output) the data and/or information processed by the processor.
  • the present application also provides a communication device, including at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instructions stored in the at least one memory,
  • the communication device is caused to perform the operations and/or processing performed by the terminal device in any method embodiment.
  • the present application also provides a communication device, including at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instructions stored in the at least one memory, so that the The communication device performs operations and/or processes performed by the network device in any method embodiment.
  • this application also provides a wireless communication system, including the terminal device and network device in the method embodiment of this application.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. three conditions. Among them, the number of A is not limited, it can be one or more than one, and the number of B is not limited, it can be one or more than one.
  • first, second, etc. are only for the convenience of distinguishing different objects, and should not constitute any limitation on the present application. For example, distinguish different buffer status reports, different values, etc.
  • first and second do not necessarily mean that the described objects are necessarily different.
  • first value and the second value only differentiate and describe two values.
  • the first value and the second value may be the same or different, and are not limited.
  • the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), application specific integrated circuit (application specific integrated circuit) circuit, ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

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

Abstract

本申请提供一种调度资源的方法和通信装置，可以适用于上行数据传输中。终端设备向网络设备发送缓冲区状态报告，以上报待发送上行数据的数据量，同时，终端设备还向网络设备发送该待发送上行数据的压缩信息，该压缩信息指示了与该待发送上行数据的物理层处理相关的压缩参数。该物理层处理可以包括对TB进行压缩和信道编码分离的编码模式，或者，物理层处理包括对根据TB获得的多个子TB分别进行压缩和信道编码联合的编码模式。网络设备根据待发送上行数据的数据量和压缩信息，为终端设备的待发送上行数据调度空口资源，可以解决在物理层引入压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式之后带来的上行资源失配的问题。

Description

调度资源的方法和通信装置 技术领域
本申请实施例涉及无线通信技术领域，更具体地，涉及一种调度资源的方法和通信装置。
背景技术
在蜂窝系统中，层1，也即物理层(physical,PHY)，主要负责数据的信道编码、调制和资源映射，层2，也即，媒体接入控制层(media access control,MAC)，主要负责数据组包和资源调度。在目前的蜂窝系统中，物理层和MAC层的所有操作都是假设从上层下来的待传输数据本身是没有冗余的，或者忽略里面的冗余，而仅考虑如何对抗信道传输差错，因此仅使用信道编码(channel coding,CC)。但是，在实际使用中，物理层的待传输数据可能具有一定的冗余度，例如，应用层的压缩算法未能充分利用数据中的冗余进行压缩，或者上层数据未经过压缩，以及空口可能产生的原生数据，如信道状态信息(channel state information,CSI)、定位、成像、环境重构等由于空口新增感知功能所生成的感知数据。而如果在物理层对待传输数据采用压缩和信道编码分离的编码模式，或者进行压缩和信道编码联合的编码模式，相对于仅仅使用信道编码能够获得更好的传输性能。
但是，现有的蜂窝系统的通信协议并不支持物理层的上述编码模式。如果在物理层引入上述编码模式，将会带来上行资源调度上的问题，例如上行资源失配。
发明内容
本申请提供一种调度资源的方法，可以支持物理层采用压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式，而不会带来上行资源调度的问题。
第一方面，提供了一种调度资源的方法，可以应用于无线通信的发送端，也可以应用在发送端的芯片或芯片系统上。这里，发送端可以是指数据传输的发送端。下面以发送端为终端设备为例进行说明。该方法包括：
终端设备向网络设备发送缓冲区状态报告，缓冲区状态报告用于指示终端设备的待发送上行数据的数据量；
终端设备向网络设备发送待发送上行数据的压缩信息，压缩信息指示与待发送上行数据的物理层处理相关的压缩参数，物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，物理层处理包括对根据TB获得的多个子TB分别进行第二编码，第二编码为压缩和信道编码联合的编码模式；
终端设备接收来自于网络设备的资源调度信息，资源调度信息用于指示网络设备为待发送上行数据分配的空口资源，空口资源是根据待发送上行数据的数据量和压缩参数确定的。
在本申请的技术方案中，终端设备向网络设备发送缓冲区状态报告，以上报待发送上 行数据的数据量，同时，终端设备还向网络设备发送该待发送上行数据的压缩信息，该压缩信息指示了与该待发送上行数据的物理层处理相关的压缩参数。该物理层处理可以包括对TB进行压缩或信道编码分离的编码模式(SSCC的编码模式)，或者，物理层处理包括对根据TB获得的多个子TB分别进行压缩和信道编码联合的编码模式(JSCC的编码模式)。网络设备根据待发送上行数据的数据量和压缩信息，为终端设备的待发送上行数据调度空口资源，可以解决在物理层引入压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式之后带来的上行资源失配的问题。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
终端设备在空口资源上发送第一上行数据，第一上行数据是在物理层对第一传输块TB进行第一编码获得的，或者，第一上行数据是在物理层对根据第一TB获得的多个子TB分别进行第二编码获得的，第一TB是根据压缩参数对待发送上行数据进行数据组包获得的。
结合第一方面，在第一方面的某些实现方式中，资源调度信息包括资源指示信息和调制与编码策略MCS信息，该方法还包括：
终端设备根据资源指示信息和MCS信息，确定组包长度；
终端设备根据组包长度和压缩参数，对待发送上行数据进行数据组包，获得第一TB，其中，第一TB中包含的待发送上行数据的估计压缩后长度小于或等于组包长度；
终端设备对第一TB进行所述物理层处理，获得第一上行数据。
该实现方式为物理层引入SSCC或JSCC的编码模式，提供了可行的物理层处理机制。
第二方面，提供了一种调度资源的方法，可以应用于无线通信的接收端，也可以应用在接收端的芯片或芯片系统上。接收端可以是指数据传输的接收端。下面以接收端为网络设备为例进行说明。该方法包括：
网络设备接收来自于终端设备的缓冲区状态报告，缓冲区状态报告用于指示终端设备的待发送上行数据的数据量；
网络设备接收来自于终端设备的待发送上行数据的压缩信息，压缩信息指示与待发送上行数据的物理层处理相关的压缩参数，物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，物理层处理包括对根据TB获得的多个子TB分别进行第二编码，第二编码为压缩和信道编码联合的编码模式；
网络设备向终端设备发送资源调度信息，资源调度信息用于指示网络设备为待发送上行数据分配的空口资源，空口资源是根据待发送上行数据的数据量和压缩参数确定的。
第二方面的有益技术效果，可以参见第一方面的说明，不予赘述。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备在空口资源上接收来自于终端设备的第一上行数据，第一上行数据是终端设备的物理层对第一传输块TB进行第一编码获得的，或者，第一上行数据是终端设备的物理层对根据第一TB获得的多个子TB分别进行第二编码获得的，第一TB是根据压缩参数对待发送上行数据进行数据组包获得的。
在第一方面或第二方面的某些实现方式中，压缩参数为压缩比，压缩比为待发送上行数据的估计压缩后长度和压缩前长度的比值；或者，
压缩参数为待发送上行数据的估计压缩后长度。
在第一方面或第二方面的某些实现方式中，待发送上行数据为物理层的原生数据，缓冲区状态报告为第一类型的缓冲区状态报告，第一类型的缓冲区状态报告用于指示待发送的原生数据的数据量；
第一类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，LCG ID字段具有多个不同取值，该多个不同取值分别对应不同的原生数据类型，缓冲区状态字段用于指示LCG ID字段所对应的原生数据类型的待发送数据的数据量。
在该实现方式中，针对物理层原生数据类型，设计相应类型的缓冲区状态报告，用于物理层原生数据的上报。
在第一方面或第二方面的某些实现方式中，第一类型的缓冲区状态报告包含压缩信息字段，压缩信息字段携带LCG ID字段所对应的原生数据类型的待发送数据的压缩信息。
在该实现方式中，在针对物理层原生数据类型的缓冲区状态报告中，还可以包括该物理层原生数据的压缩信息，为UE上报物理层原生数据的压缩信息提供了可实现的机制。
在第一方面或第二方面的某些实现方式中，待发送上行数据为物理层的原生数据，缓冲区状态报告为第二类型的缓冲区状态报告，第二类型的缓冲区状态报告用于指示待发送的原生数据的数据量；
第二类型的缓冲区状态报告是对媒体接入控制MAC层的短缓冲区状态报告或长缓冲区状态报告扩展得到的，第二类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，
LCG ID字段包括x个比特，缓冲区状态字段为一个，x个比特具有y个不同的取值，y个取值中的p个取值分别对应不同的原生数据类型，y个取值中的q个取值分别对应不同的逻辑信道类型，当LCG ID字段为y个取值中的第一取值时，缓冲区状态字段指示第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量，p+q≤y,y＝2 x,x,y,p和q均为整数；
或者，
LCG ID字段包括z个比特，z个比特中的k个比特与k个原生数据类型满足比特映射关系，z个比特中的r个比特与r个逻辑信道类型满足比特映射关系，该z个比特中的每个比特具有第二取值或第三取值，当z个比特中的第j个比特为第二取值时，第j个比特对应的原生数据类型或逻辑信道类型被选中，当z个比特中的第j个比特为第三取值时，第j个比特对应的原生数据类型或逻辑信道类型未被选中；若z个比特中的w个比特为第二取值，缓冲区状态字段有w个，该w个缓冲区状态字段分别用于指示和该w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，z＝k+r,1≤j≤z,1≤w≤z,z,k,r,j和w均为正整数。
在该实现方式中，通过对MAC层的短BSR或长BSR进行扩展，可以复用扩展后的BSR，用于物理层原生数据的上报，可以节省引入针对物理层原生数据的缓冲区状态报告带来的比特开销。
在第一方面或第二方面的某些实现方式中，若缓冲状态字段为一个，第二类型的缓冲区状态报告还包括一个压缩信息字段，当x个比特为y个取值中的第一取值时，压缩信息字段携带第一取值对应的原生数据类型或逻辑信道类型的待发送数据的压缩信息；
若缓冲状态字段为w个，第二类型的缓冲区状态报告还包括w个压缩信息字段，w 个压缩信息字段分别携带w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的压缩信息。
在该实现方式中，扩展后的BSR中还可以包括压缩信息，为UE上报物理层原生数据的压缩信息提供了可实现的机制。
第三方面，提供一种通信装置，所述通信装置具有实现第一方面或第一方面的任一可能的实现方式中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第四方面，提供一种通信装置，所述通信装置具有实现第二方面或第二方面的任一可能的实现方式中的方法的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第五方面，提供一种通信装置，包括处理器和存储器。可选地，还可以包括收发器。其中，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，并控制收发器收发信号，以使通信装置执行如第一方面或第一方面的任一可能的实现方式中的方法。
第六方面，提供一种通信装置，包括处理器和存储器。可选地，还可以包括收发器。其中，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，并控制收发器收发信号，以使通信装置执行如第二方面或第二方面的任一可能的实现方式中的方法。
第七方面，提供一种通信装置，包括处理器和通信接口，所述通信接口用于接收数据和/或信息，并将接收到的数据和/或信息传输至所述处理器；所述处理器处理所述数据和/或信息；以及，所述通信接口还用于输出经所述处理器处理之后的数据和/或信息，以使所述通信装置执行如第一方面，或第一方面的任一可能的实现方式中的方法。
第八方面，提供一种通信装置，包括处理器和通信接口，所述处理器处理待发送的数据和/或信息；所述通信接口用于输出经处理器处理之后的数据和/或信息，以使得所述通信装置执行如第二方面，或第二方面的任一可能的实现方式中的方法。
可选地，上述第五方面至第八方面中，处理器可以为一个或多个，存储器可以为一个或多个。可选地，收发器可以为一个或多个。
第九方面，提供一种通信装置，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所述通信装置执行如第一方面，或第一方面的任一可能的实现方式中的方法。
第十方面，提供一种通信装置，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所述通信装置执行如第二方面，或第二方面的任一可能的实现方式中的方法。
第十一方面，提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机指令，当计算机指令在计算机上运行时，使得如第一方面，或第二方面，或这些方面的任一可能的实现方式中的方法被执行。
第十二方面，提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得如第一方面，或第二方面，或这些方面中的任一方面的任一可能的实现方式中的方法被执行。
第十三方面，提供一种无线通信系统，包括如第三方面所述的通信装置以及如第四方面所述的通信装置。
附图说明
图1为蜂窝系统中上行资源申请、调度和数据传输流程示意图。
图2为上行资源调度和编码调制的关系的示意图。
图3为蜂窝系统的物理层采用SSCC的情况下上行资源调度和编码调制的关系的示意图。
图4为物理层引入SSCC或JSCC之后上行资源分配的示意图。
图5为本申请提供的调度资源的方法的通信系统的示意性架构图。
图6为本申请提供的调度资源的方法的示意性流程图。
图7为对缓冲区中的待发送上行数据分PB统计稀疏度并估计压缩比的示意图。
图8为采用8比特量化压缩比并添加到短BSR或长BSR进行上报的示意图。
图9为针对原生数据类型的BSR的示意性结构图。
图10为终端设备根据组包长度和压缩比进行数据组包的示意图。
图11为本申请提供的通信装置的示意性框图。
图12为本申请提供的通信装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，第五代(the 5th generation,5G)系统或新无线(new radio,NR)系统、长期演进(long term evolution,LTE)系统、长期演进高级技术(long term evolution-advanced，LTE-A)系统、LTE频分双工(frequency division duplex,FDD)系统、LTE时分双工(time division duplex,TDD)系统等。还可以应用于未来的通信系统，例如第六代移动通信系统。此外，还可以应用于设备到设备(device to device,D2D)通信，车辆外联(vehicle-to-everything,V2X)通信，机器到机器(machine to machine,M2M)通信，机器类型通信(machine type communication,MTC)，以及物联网(internet of things,IoT)通信系统或者其它通信系统，等。此外，还可以扩展到类似的无线通信系统中，如无线保真(wireless-fidelity,WiFi)，全球微波互联接入(worldwide interoperability for microwave access,WIMAX)，以及第三代合作伙伴计划(3rd generation partnership project,3gpp)相关的通信系统等，不作限定。
适用于本申请的通信系统，可以包括一个或多个发送端，以及，一个或多个接收端。可选地，发送端和接收端中的一个可以为终端设备，另一个可以为网络设备。
本文部分实施例以5G系统为例介绍具体的方案细节。可以理解的是，当该方案用于其它通信系统时，例如，LTE系统，或者未来的通信系统，方案中的各消息、信道或信息等可以替换为其它通信系统中能够实现相应功能的消息、信道或信息等，本申请对此不作限定。例如，缓存状态报告在5G中可以为(buffer status report,BSR)，物理上行共享信道在5G中可以为(physical uplink shared channel,PUSCH)。
示例性地，终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户 单元、用户站、移动站、移动台、移动终端(mobile terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请实施例中的终端设备可以是指向用户提供语音和/或数据连通性的设备，可以用于连接人、物和机，例如具有无线连接功能的手持式设备、车载设备等。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(pad)、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。可选地，UE可以用于充当基站。例如，UE可以充当调度实体，其在V2X或D2D等中的UE之间提供侧行链路信号。
本申请实施例中，用于实现终端的功能的装置可以是终端，也可以是能够支持终端实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
示例性地，网络设备可以是具有无线收发功能的设备，该网络设备可以是提供无线通信功能服务的设备，通常位于网络侧，包括但不限于第五代(5th generation，5G)通信系统中的下一代基站(gNodeB,gNB)、第六代(6th generation,6G)移动通信系统中的基站、未来移动通信系统中的基站或无线保真(wireless fidelity,WiFi)系统中的接入节点，长期演进(long term evolution,LTE)系统中的演进型节点B(evolved node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(node B,NB)、基站控制器(base station controller,BSC)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU)，传输接收点(transmission reception point,TRP)、发射点(transmitting point,TP)、基站收发台(base transceiver station,BTS)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit,CU)节点，或包括分布单元(distributed unit,DU)节点，或包括CU节点和DU节点的RAN设备，或包括控制面CU节点和用户面CU节点，以及DU节点的RAN设备，或者，网络设备还可以为云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器、中继站、车载设备以及可穿戴设备等。此外，基站可以是宏基站、微基站、中继节点、施主节点，或其组合。基站还可以指用于设置于前述设备或装置内的通信模块、调制解调器或芯片。基站还可以是移动交换中心以及D2D、V2X、M2M通信中承担基站功能的设备、6G网络中的网络侧设备、未来的通信系统中承担基站功能的设备等。基站可以支持相同或不同接入技术的网络，不作限定。
本申请实施例中，用于实现网络设备的功能的装置可以是网络设备，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在网络设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
在现有的蜂窝系统中，物理层(physical,PHY)和MAC层的操作都是假设从上层下来的待传输数据本身没有冗余，或者忽略掉其中的冗余，而只考虑如何对抗信道传输差错，基本流程如图1所示。
参见图1，图1为蜂窝系统中上行资源申请、调度和数据传输流程示意图。如图1，基站根据UE的缓冲区状态报告和功率余量等信息，为UE调度上行资源。其中，BSR主 要用于告诉基站该UE的各逻辑信道缓冲区中的待传输数据的数据量，可以使得基站能够根据该信息决定给UE调度多少空口资源。基站的资源调度是通过在下行控制信道上下发下行控制信息(downlink control information,DCI)，例如，DCI格式0(简记为DCI 0)，来告知UE。DCI 0中关于资源调度的字段主要是资源指示和MCS指示，其中，资源指示用于指示发送上行数据的时频资源，MCS指示用于指示在该时频资源上使用什么样的信道编码码率和调制阶数。参见图2，图2为上行资源调度和编码、调制的关系的示意图。如图2，资源指示和MCS指示共同决定了UE的物理层传输块(transport block,TB)(也即信道编码前的码块)的大小、信道编码的码率和信道编码后的码块大小。信道编码后的码块经过调制，被映射到相应的空口资源上进行发送。
已知物理层传输数据的单元为传输块(transport block,TB)，如果TB本身仍然有一定的冗余度，在物理层引入压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式，可以利用物理层待传输数据的冗余度来进一步提升数据传输性能。而蜂窝系统的物理层并不支持压缩和信道编码分离的编码模式，也不支持压缩和信道编码联合的编码模式，并且，协议层面(例如，资源调度的信令流程)也不支持物理层该功能的实现。
需要说明的是，信源编码通常也理解为压缩，因此，业界通常也将压缩和信道编码分离的编码模式称为分离信源和信道编码(separate source and channel coding,SSCC)，将压缩和信道编码联合的编码模式称为联合信源信道编码(joint source and channel coding,JSCC)。因此，下文中的SSCC编码即是指压缩和信道编码分离的编码模式，JSCC即是指压缩和信道编码联合的编码模式。
在物理层引入SSCC或JSCC，可以提升数据传输性能，但是由于现有的蜂窝系统协议层面支持在物理层采用SSCC或JSCC，同时也会带来上行资源调度失配的问题。
参见图3，图3为蜂窝系统的物理层采用SSCC的情况下上行资源调度和编码调制的关系的示意图。上文已经介绍过，基站的下行控制信息中的资源指示和MCS指示共同决定了TB size(如图3中的长度L)、编码调制以及资源映射(资源大小)。可见，资源指示和MCS指示对于接收端成功解码是必不可少的。在物理层引入SSCC之后，首先要对数据进行压缩(有损或无损)，将基站调度的长度为L的TB压缩为长度为L′的新TB，可选地，该新TB后面可以添加CRC(如CRC′)或填充(padding)，不失一般性地，填充通常是用0来填充，然后再进行信道编码。
基站在调度上行资源时需要参考UE上报的BSR等信息来决定给UE分配多少空口资源，主要考虑的是信道差错保护。如果在物理层引入了数据压缩，而UE发送的BSR如果仅上报待发送数据在压缩前的数据量，则基站不知道压缩后的数据量的多少，基站调度的上行资源会造成浪费，如图4所示，图4为物理层引入SSCC或JSCC之后上行资源分配的示意图。但是，如果UE发送的BSR上报压缩后的数据量的大小L′，则需要UE提前对待发送上行数据进行压缩，又会造成组包延时，而且在实现上也面临较大的困难，因为UE在接收到网络侧的调度信息(具体可以是指资源指示和MCS指示)之前，并不知道对多大尺寸的数据进行压缩，也即UE不知道L的大小。
类似地，如果在物理层引入JSCC，也会带来类似的上行资源分配的问题。因为，JSCC是利用待发送数据的冗余度，对该待发送数据同时进行压缩和信道编码，本质上可以认为是利用不同于信道编码的打孔模式、根据待发送数据的冗余度，采用更高的信道编码码率。 等价地，也可认为是利用信源的冗余度，在同样差错保护效果的前提下减少了空口资源的消耗。因此整体上也可以看作是在信道编码之前先进行了一次数据压缩，因此在物理层使用JSCC，对上行资源分配所造成的问题和在物理层引入SSCC所带来的上行资源分配的问题是一样的。
为此，本申请提供一种调度资源的方法，旨在解决物理层引入SSCC或JSCC之后带来的上行资源失配(例如，网络侧为上行数据分配的空口资源的大小，大于UE实际发送的上行数据所需求的空口资源)的问题。
也即，在本申请中，物理层不仅考虑信道差错保护，还利用物理层的待发送数据的冗余度，在物理层对数据采用压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式。
参见图5，图5为适用于本申请提供的调度资源的方法的通信系统的示意性架构图。如图5，本申请提供的调度资源的方法主要适用于网络设备和终端设备之间的上行数据传输的场景，也可适用于终端设备之间的数据传输，也即，侧行链路(sidelink,SL)的数据传输，本申请对此不作限定。因此，本文中的发送端可以是指上行数据传输中的终端，也可以是指侧行链路数据传输中的发送终端。类似地，接收端可以是指上行数据传输中的网络设备或者侧行链路数据传输中的接收终端。下文以上行数据传输为例，对本申请的技术方案进行说明。
在本申请的技术方案中，终端设备在向网络设备上报缓冲区状态报告，缓冲区状态报告用于指示待发送上行数据的数据量。同时，终端设备向网络设备发送该待发送上行数据的压缩信息，压缩信息指示与该待发送上行数据的物理层处理相关的压缩参数。网络设备根据该待发送上行数据的数据量和压缩参数，为终端设备的待发送上行数据调度空口资源，可以避免在终端设备的物理层引入SSCC或JSCC之后而导致网络设备调度的空口资源失配的问题。
本申请实施例中的终端设备可以如图5中所示的终端设备120或130，网络设备可以如图5中所示的网络设备110。图5中所示仅是作为示例，该通信系统中还可以包括其它的通信设备，例如，更多的终端设备，或者更多的网络设备等，不作限定。
参见图6，图6为本申请提供的调度资源的方法的示意性流程图。
610、终端设备向网络设备发送缓冲区状态报告，缓冲区状态报告用于指示终端设备的待发送上行数据的数据量。
可选地，这里的待发送上行数据可以是指来自于应用层的数据，或者也可以是物理层原生数据，不作限定。下文会对终端设备向网络侧上报物理层原生数据的缓冲区状态报告作详细介绍。
620、终端设备向网络设备发送待发送上行数据的压缩信息，该压缩信息指示与待发送上行数据的物理层处理相关的压缩参数。
可选地，物理层处理可以包括：
对TB进行第一编码，第一编码压缩和信道编码分离的编码模式；或者，
对根据TB获得的多个子TB分别进行第二编码，第二编码为压缩和信道编码联合的编码模式。
网络设备接收来自于终端设备的缓冲区状态报告，以及压缩信息。
630、网络设备向终端设备发送资源调度信息，资源调度信息用于指示网络设备为终端设备的待发送上行数据分配的空口资源，所述空口资源是根据终端设备的待发送上行数据和压缩参数确定的。
终端设备接收来自于网络设备的资源调度信息。
在本申请的技术方案中，终端设备的物理层引入了压缩和信道编码分离的编码模式，或者压缩和信道编码联合的编码模式，终端设备向网络设备上报待发送上行数据的缓冲区状态报告，同时会上报待发送上行数据的压缩信息，该压缩信息是终端设备在发送缓冲区状态报告之前，根据待发送上行数据估计确定的压缩比(即，估计压缩比)，或者，也可以是估计的待发送上行数据的压缩后大小(即，估计压缩后长度)。下文会介绍终端设备估计压缩比的一些实现方式。终端设备向网络设备发送待发送上行数据的压缩信息，可以辅助网络设备进行上行资源的调度，以避免网络设备在不知道终端设备的物理层处理相关的压缩信息的情况下，为终端设备的待发送上行数据调度空口资源，导致所调度的空口资源与实际发送的上行数据的数据量失配的问题。
进一步地，方法600还可以包括步骤640。
640、终端设备在所述空口资源上发送第一上行数据。网络设备接收来自于终端设备的第一上行数据。
其中，第一上行数据是终端设备的物理层对第一TB进行上述第一编码获得的，或者，第一TB是对根据第一TB获得的多个子TB分别进行第二编码获得的。其中，第一TB是终端设备的物理层根据压缩参数对待发送上行数据进行数据组包获得的。
可选地，终端设备可以通过多种不同实现来估计待发送上行数据的压缩比，下面仅给出一些示例。
在一个示例中，终端设备的无线链路控制(radio link control,RLC)和分组数据汇聚协议(packet data convergence protocol,PDCP)在统计每个逻辑信道(组)的缓冲区的数据量时，需要增加如下估计压缩比的过程：
统计每个逻辑信道(组)的缓冲区的数据的分组稀疏度，然后根据稀疏度估算待发送上行数据的压缩比。具体地，将缓冲区中待发送上行数据切分为大小为N s的若干个预处理块(processing block,PB)，然后对这些PB进行稀疏度统计。如图7所示，图7为对缓冲区中的待发送上行数据分PB统计稀疏度并估计压缩比的示意图。统计获得每个PB的稀疏度之后，根据稀疏度估计该逻辑信道(组)的缓冲区中的待发送上行数据的压缩后长度(文本中也称为估计压缩后长度)。
示例性地，在估计待发送上行数据的压缩后长度时，可以采用如下计算方式：
在一种计算方式中，假设缓冲区中的待发送上行数据的压缩前长度为L比特，按照长度N s，将TB划分为K个PB，将其中第i个PB的稀疏度记作S i(0≤S i≤1)，对应的熵为H i，其中，H i＝-S ilog(S i)-(1-S i)log(1-S i)，则该缓冲区中待发送上行数据的压缩后长度估计为
Figure PCTCN2022104584-appb-000001
在另一种计算方式中，设置一系列稀疏度的范围区间，统计每个PB的稀疏度所在的范围区间的右端点值，记作S′ i，对应的熵记作H′ i，则该缓冲区中待发送上行数据的压缩后长度的估计为
Figure PCTCN2022104584-appb-000002
在估计出待发送上行数据的压缩后长度之后，结合压缩前长度，就可以计算获得压缩 比。应理解，压缩比可以是指逻辑信道的缓冲区中待发送上行数据的估计压缩后长度和压缩前长度的比值，记作CR，在上述第一种计算方式中，CR＝S/L；或者，在上述第二种计算方式中，CR＝S′/L。此外，压缩比的估计也可以参考过往的历史信息。
上述估计压缩比的方式仅是作为示例。再一种可行的计算方式为：从缓冲区中的待发送上行数据中随机选取若干段，通常所选取的数据的长度远小于总的数据量(也即数据长度L)，然后使用数据压缩算法对选出来的数据进行压缩，并统计选出来的数据的压缩前长度和压缩后长度，从而获得压缩比的估计。示例性地，该计算方式中采用的压缩算法可以是在线的算术码，或者伦佩尔-齐夫(Lempel-Ziv)算法等，不作限定。需要注意的是，该压缩算法应该和终端设备的物理层在进行数据压缩时使用的压缩算法保持一致。
下面再给出终端设备向网络设备发送压缩信息的一些示例。
以终端设备向网络设备发送压缩比为例，可选地，终端设备可以对压缩比进行量化，并上报量化后的信息。
例如，终端设备将各逻辑信道(组)的压缩比量化为若干个等级，并使用固定的x个比特来表示量化后的压缩比信息，该量化后的压缩比信息可以随BSR一起上报给网络侧。例如，量化后的压缩比信息和BSR可以通过媒体接入控制-控制元素(medium access control-control element,MAC CE)进行上报。例如，可以将压缩比量化为256个等级中的一个，然后用8比特来指示量化等级。作为一个示例，量化等级可以添加到短BSR(short BSR)或长BSR(long BSR)中进行上报，也即，本申请中的压缩信息可以通过对短BSR或长BSR进行扩展来上报，如下面图8中的介绍。
参见图8，图8为采用8比特量化压缩比并添加到短BSR或长BSR进行上报的示意图。短BSR通常适用于只上报一个逻辑信道组或一种类型的原生数据的缓存状态。短BSR包括LCG ID和缓冲区状态字段。其中的LCG ID使用3比特来标识一个逻辑信道组的编号，后面的5比特为缓冲区状态字段，用于表示该逻辑信道组对应的缓冲区的数据量。长BSR可以适用于同时上报多个逻辑信道组或多个类型的原生数据的缓存状态，其中的LCG1～LCG8组成一个8比特的比特映射(bitmap)，该8比特分为对应8个不同的逻辑信道组类型，该8比特中的某个比特的值为0，表示该比特对应的逻辑信道组未被选中，其值为1表示该比特对应的逻辑信道组被选中。被选中的逻辑信道组对应的缓冲区的数据量按照与bitmap相同的顺序附在后面的缓存状态(buffer status)字段中，每个被选中的逻辑信道的缓冲区的数据量大小由8比特来指示。
可选地，本申请中终端设备的待发送上行数据可以为物理层的原生数据。
可选地，针对物理层原生数据的上报，可以增加针对不同原生数据类型的BSR。
示例性地，物理层原生数据可以包括定位数据、重构环境数据和感知成像数据等，还可以是物理层其它类型的原生数据，不作限定。
下面介绍本申请提供的终端设备向网络设备上报物理层的原生数据的几种实现方式，仅作为示例进行说明。
实现方式(1)
示例性地，在一种实现方式中，可以重新定义一种类型的BSR，为了和上文的MAC层的短BSR以及长BSR区分，在本文中称为第一类型的BSR。第一类型的BSR可以包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，LCG ID字段具有(或者说， 对应)多个不同取值，该多个不同取值对应不同的原生数据类型；缓冲区状态字段用于指示缓冲区的数据量。应理解，当LCG ID字段的取值对应某个原生数据类型时，缓冲区状态字段则指示该原生数据类型的原生数据的待发送的数据量。
实现方式(2)
示例性地，在另一种实现方式中，第一类型的BSR可以包括LCG ID字段、缓冲区状态字段和压缩信息字段。相比于上一种实现方式，在该实现方式中，第一类型的BSR还包括压缩信息字段，用于指示待发送原生数据的压缩信息(例如，压缩比)。具体地，压缩信息字段用于指示LCG ID字段所对应的原生数据类型的待发送数据的数据量。
在这两种实现方式中，第一类型的BSR的LCG ID字段的不同取值，分别对应不同的原生数据类型。示例性地，第一类型的BSR的LCG ID字段包括4个比特，当该4个比特的取值为0000时，表示第一类型的BSR对应定位数据类型；相应地，缓冲区状态字段用于指示待发送的物理层原生定位数据的数据量；如果还包括压缩信息字段，则压缩信息字段用于指示待发送的物理层原生定位数据的压缩信息。当该4个比特的取值为00001时，表示该第一类型的BSR对应感知成像数据类型；相应地，缓冲区状态字段用于指示待发送的物理层原生感知成像数据的数据量；如果还包括压缩信息字段，则压缩信息字段用于指示待发送的物理层原生感知成像数据的压缩信息。
实现方式(3)
示例性地，在一种实现方式中，用于上报物理层原生数据的BSR可以复用短BSR或者复用长BSR，但是需要对短BSR或者复用长BSR进行扩展。为了描述上的方便，将扩展后的BSR称为第二类型的BSR。
具体地，可以对短BSR或者长BSR的LCG ID字段进行扩展，以支持更多的LCG ID，多出来的LCG ID用于对应不同的原生数据类型。
示例性地，对短BSR或者长BSR的LCG ID字段以及缓冲区状态字段进行扩展。在该实现方式中，扩展后的BSR(即，第二类型的BSR)包括LCG ID字段和缓冲区状态字段。
在一个示例中，对短BSR进行扩展，获得扩展后的BSR。该扩展后的BSR包括一个LCG ID字段和一个缓冲区状态字段。其中，LCG ID字段包括x个比特，x个比特具有(或者说，对应)y个取值，y个取值中的p个取值分别对应不同的原生数据类型，y个取值中的q个取值分别对应不同的逻辑信道类型。当LCG ID字段为y个取值中的第一取值时，缓冲区状态字段用于指示第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量。其中，p+q≤y,x,y,p和q均为整数。当p+q<y时，表示y个取值中包括预留取值。示例性地，y＝2 x。
在另一个示例中，对长BSR进行扩展，获得扩展后的BSR。该扩展后的BSR包括LCG ID字段和缓冲区状态字段。其中，LCG ID字段包括z个比特，z个比特中的k个比特与k个原生数据类型满足比特映射关系，z个比特中的r个比特与r个逻辑信道类型满足比特映射关系。该z个比特中的每个比特具有第二取值或第三取值，当z个比特中的某个比特为第二取值，表示该比特对应的原生数据类型或逻辑信道类型被选中，当该比特为第三取值，表示该比特对应的原生数据类型或逻辑信道类型未被选中。若z个比特中有w个比特为第二取值，则该扩展后的BSR中的缓冲区状态字段为w个，该w个缓冲区状态 字段分别用于指示和该w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，z＝k+r,1≤w≤z,z,k，w和r均为正整数。示例性地，第二取值为1，第三取值为0，不限定为其它取值。
实现方式(4)
可选地，第二类型的BSR还包含压缩信息字段。
如果是对短BSR进行扩展，获得扩展后的BSR，则该扩展后的BSR包含一个压缩信息字段。结合上述实现方式(3)可知，在此设计中，扩展后的BSR包括一个LCG ID字段、一个缓冲区状态字段和一个压缩信息字段。其中，当LCG ID字段的x个比特为所述y个取值中的第一取值时，压缩信息字段携带第一取值对应的原生数据类型或逻辑信道类型的待发送数据的压缩信息。
如果是对长BSR进行扩展，获得扩展后的BSR，则该扩展后的BSR中的压缩信息字段的个数是动态变化的。结合上述实现方式(3)可知，在此设计中，扩展后的BSR包括LCG ID字段，LCG ID字段包含z个比特。当该z个比特中的w个比特为第二取值时，表示该w个比特对应的原生数据类型和/或逻辑信道类型被选中，此时，扩展后的BSR包括w个缓冲区状态字段以及w个压缩信息字段。其中，w个缓冲区状态字段分别用于指示该w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，w个压缩信息字段分别携带该w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的压缩信息。
下面结合图9对上述实现方式(4)进行示例说明。如图9，图9为针对原生数据类型的BSR的示意性结构图。
例如，如图9的(a)，以扩展短BSR为例，将LCG ID字段增加1比特，从原来的3比特扩展为4比特，由此LCG ID字段从原来可指示8个LCG ID，扩展为可以指示16个LCG ID，可以多指示8个LCG ID，这多出来的8个LCG ID可以分别对应8个原生数据类型。同时，将缓冲区状态(buffer status)字段增加1比特，从原来的5比特扩展为6比特。可选地，扩展后的BSR还包括压缩信息字段。以压缩信息为压缩比CR为例，该压缩信息字段可以为CR字段，示例性地，CR字段包含6比特。可以看出，在该示例中，短BSR的总长度被扩展至16比特。该扩展后的BSR为上述第二类型的BSR的一个示例。
再以长BSR为例，如图9的(b)，可以直接在原来的LCG ID字段再增加8个比特，从原来的8比特扩展为16比特。应理解，扩展后的BSR的LCG ID字段共包括16个比特，其中有8个比特分别对应不同的逻辑信道类型，另外新增的8个比特与8种原生数据类型满足比特映射(bitmap)的关系，每个比特对应一个原生数据类型。可选地，当LCG ID字段的16个比特中的某个比特为1时，表示该比特对应的原生数据类型或逻辑信道类型为被选中，此时，扩展后的BSR中还包括被选中的原生数据类型或逻辑信道类型的待发送数据的数据量，可选地，扩展后的BSR中还包括该被选中的原生数据类型或逻辑信道类型的待发送数据的压缩信息。因此，在该设计中，若LCG ID字段所包含的z个比特中，有w个比特为1，则扩展后的BSR中包括w个缓冲区状态字段，分别用于上报该w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量。可选地，扩展后的BSR还包括w个压缩信息字段，分别携带该w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的压缩信息。示例性地，在图9的(b)中，缓冲区状态字段和/或CR字段 各自包含8比特，不作限定。
以上对终端设备估计待发送上行数据的压缩比，以及终端设备向网络设备上报原生数据的BSR的具体实现作了详细说明。
在步骤640中，终端设备向网络设备发送第一上行数据。具体地，终端设备在物理上行共享信道上向网络设备发送第一上行数据。以NR为例，物理上行共享信道可以为(physical uplink shared channel,PUSCH)。
可选地，如果还存在上行链路控制信息(uplink control information,UCI)需要发送，则终端设备将第一上行数据和UCI复用到PUSCH进行发送。
上文已经介绍过，第一上行数据是终端设备的物理层对第一TB进行第一编码获得，或者对根据第一TB获得的多个子TB分别进行第二编码获得，而第一TB是终端设备的物理层根据压缩参数对待发送上行数据进行数据组包获得的。
具体地，终端设备在接收到来自于网络设备的资源调度信息之后，资源调度信息中包括资源指示和MCS指示。终端设备根据资源指示和MCS指示，计算组包长度(TB size)。示例性地，组包长度的计算方法，可以参考NR中确定TBS(TB size)的具体实现。确定组包长度之后，终端设备根据组包长度和压缩参数，对待发送上行数据进行数据组包，获得第一TB。在组包时，终端设备根据压缩参数估计待发送上行数据的压缩后长度，直到估计的压缩后长度填充完组包长度为止，此时得到第一TB。在一些情况下，待发送上行数据不足以填充完组包长度。因此，第一TB中包含的待发送上行数据的估计压缩后长度小于或等于组包长度。获得第一TB之后，后续可以对第一TB进行所述第一编码，或者根据第一TB获得多个子TB，然后再对该多个子TB分别进行第二编码，不作限定。可选地，上述实施例中，终端设备在组包时，具体是对各逻辑信道组的缓冲区中的RLC PDU进行组包，可选地，如果还存在待发送的原生数据，则将各逻辑信道组的缓冲区中的RLC PDU和原生数据进行组包，获得第一TB。
参见图10，图10为终端设备根据组包长度和压缩比进行数据组包的示意图。应理解，RLC层将每个逻辑信道组对应的RLC SDU进行分段/重组，以匹配MAC层为其分配的MAC SDU size，RLC SDU经过分段/重组之后加上RLC头封装为RLC PDU递交到MAC层。MAC层起调度作用，负责将本次传输所对应的物理资源分配给若干个逻辑信道组，每个逻辑信道组的RLC PDU的长度可以不同。RLC PDU在MAC层被称为MAC SDU，若干个MAC SDU复用到一个MAC PDU内，通过物理层信道发送出去。一个MAC PDU可以承载多个不同逻辑信道组的数据。MAC PDU对于物理层而言，称为TB。一个TB用于承载一个MAC PDU，TB的大小由分配给该TB的物理资源数和MCS决定。如图10，将组包长度记作T。在进行数据组包时，终端设备根据压缩比估计待发送上行数据的压缩后长度，直至估计的压缩后长度填充满T为止，如图10中的S 1+S 2+S 3+S 4≤T，此时，获得第一TB。
在获得第一TB之后，后续操作可以是在物理层对第一TB进行压缩，再对压缩后的TB进行信道编码、速率匹配、调制和资源映射。
或者，后续操作也可以是在物理层对第一TB进行JSCC处理。首先对第第一TB进行预处理，预处理过程大致为：预先设定2 Q个稀疏度范围，然后按照固定的长度，将第一TB划分为B个PB，示例性地，每个PB的长度为N s。然后将多个PB按照稀疏度进行 组合，例如，将稀疏度位于同一个稀疏度范围的PB组成一个子TB，由此组合得到2 Q个子TB。此外，创建一个控制信息子TB，该控制信息子TB用于指示该B个PB各自的稀疏度的信息。例如，如果预先设定的2 Q个稀疏度范围分别对应一个索引，示例性地，控制信息子TB可以指示B个PB各自的稀疏度所对应的稀疏度范围的索引。进一步地，由于每个PB需要Q个比特来指示其稀疏度范围，共有B个PB，因此，控制信息子TB的长度为B·Q个比特，B和Q均为正整数。可知，根据第一TB共得到2 Q个子TB和一个控制信息子TB，即本文中所述的根据第一TB获得的多个子TB。然后，对该多个子TB进行JSCC。应理解，该多个子TB中的各个子TB是独立进行第二编码的，也即每个子TB单独采用压缩和信道编码联合的编码模式进行处理。特别地，在对该多个子TB进行JSCC过程中，控制信息子TB的压缩率为1。其中，不同子TB的资源复用可根据固定规则在网络侧和终端侧确定下来。
终端设备将上行数据和UCI复用到PUSCH发送时，UCI可以包括如下一个或多个类型：混合自动重传请求-确认(hybrid automatic repeat request acknowledgement,HARQ-ACK)、信道状态信息(channel state information,CSI)。可选地，CSI可以包括CSI part 1和CSI part 2。
以上对本申请提供的调度资源的方法进行了详细说明，下面介绍本申请提供的通信装置。
参见图11，图11为本申请提供的通信装置的示意性框图。如图11，通信装置1000包括处理单元1100、接收单元1200和发送单元1300。
可选地，通信装置1000可以对应本申请实施例中的终端设备。
此时，通信装置1000的各单元用于实现如下功能：
发送单元1300，用于：
向网络设备发送缓冲区状态报告，所述缓冲区状态报告用于指示所述通信装置的待发送上行数据的数据量；
以及，向所述网络设备发送所述待发送上行数据的压缩信息，所述压缩信息指示与所述待发送上行数据的物理层处理相关的压缩参数，所述物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，所述物理层处理包括对根据所述TB获得的多个子TB分别进行第二编码，所述第二编码为压缩和信道编码联合的编码模式；
接收单元1200，用于接收来自于所述网络设备的资源调度信息，所述资源调度信息用于指示所述网络设备为所述待发送上行数据分配的空口资源，所述空口资源是根据所述待发送上行数据的数据量和所述压缩参数确定的。
可选地，在一个实施例中，所述发送单元1300，还用于：
在所述空口资源上发送第一上行数据，所述第一上行数据是所述通信装置的物理层对第一传输块TB进行所述第一编码获得的，或者，所述第一上行数据是所述通信装置的物理层对根据第一TB获得的多个子TB分别进行所述第二编码获得的，所述第一TB是根据所述压缩参数对所述待发送上行数据进行数据组包获得的。
可选地，在一个实施例中，所述压缩参数为压缩比，所述压缩比为所述待发送上行数据的估计压缩后长度和压缩前长度的比值；或者，
所述压缩参数为所述待发送上行数据的估计压缩后长度。
可选地，在一个实施例中，所述资源调度信息包括资源指示信息和调制与编码策略MCS信息，所述处理单元1100，用于：
根据所述资源指示信息和所述MCS信息，确定组包长度；
根据所述组包长度和所述压缩参数，对所述待发送上行数据进行数据组包，获得所述第一TB，其中，所述第一TB中包含的待发送上行数据的估计压缩后长度小于或等于所述组包长度；
对所述第一TB进行所述物理层处理，获得所述第一上行数据。
可选地，在一个实施例中，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第一类型的缓冲区状态报告，所述第一类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
所述第一类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，所述LCG ID字段具有多个不同取值，所述多个不同取值分别对应不同的原生数据类型，所述缓冲区状态字段用于指示所述LCG ID字段所对应的原生数据类型的待发送数据的数据量。
可选地，在一个实施例中，所述第一类型的缓冲区状态报告包含压缩信息字段，所述压缩信息字段携带所述LCG ID字段所对应的原生数据类型的待发送数据的所述压缩信息。
可选地，在一个实施例中，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第二类型的缓冲区状态报告，所述第二类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
所述第二类型的缓冲区状态报告是对媒体接入控制MAC层的短缓冲区状态报告或长缓冲区状态报告扩展得到的，所述第二类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，
所述LCG ID字段包括x个比特，所述缓冲区状态字段为一个，所述x个比特具有y个不同的取值，所述y个取值中的p个取值分别对应不同的原生数据类型，所述y个取值中的q个取值分别对应不同的逻辑信道类型，当所述LCG ID字段为所述y个取值中的第一取值时，所述缓冲区状态字段用于指示所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量，p+q≤y,y＝2 x,x,y,p和q均为整数；
或者，
所述LCG ID字段包括z个比特，所述z个比特中的k个比特与k个原生数据类型满足比特映射关系，所述z个比特中的r个比特与r个逻辑信道类型满足比特映射关系，所述z个比特中的每个比特具有第二取值或第三取值，当所述z个比特中的第j个比特为所述第二取值时，所述第j个比特对应的原生数据类型或逻辑信道类型被选中，当所述z个比特中的第j个比特为所述第三取值时，所述第j个比特对应的原生数据类型或逻辑信道类型未被选中；若所述z个比特中的w个比特为所述第二取值，所述缓冲区状态字段有w个，所述w个缓冲区状态字段分别用于指示和所述w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，z＝k+r,1≤j≤z,1≤w≤z,z,k,r,j和w均为正整数。
可选地，在一个实施例中，若所述缓冲状态字段为一个，所述第二类型的缓冲区状态报告还包括一个压缩信息字段，当所述x个比特为所述y个取值中的第一取值时，所述压 缩信息字段携带所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息；
若所述缓冲状态字段为w个，所述第二类型的缓冲区状态报告还包括w个压缩信息字段，所述w个压缩信息字段分别携带所述w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息。
可选地，通信装置1000可以对应本申请实施例中的网络设备。
此时，通信装置1000的各单元用于实现如下功能：
接收单元1200，用于：
接收来自于终端设备的缓冲区状态报告，所述缓冲区状态报告用于指示所述终端设备的待发送上行数据的数据量；
以及，接收来自于所述终端设备的所述待发送上行数据的压缩信息，所述压缩信息指示与所述待发送上行数据的物理层处理相关的压缩参数，所述物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，所述物理层处理包括对根据所述TB获得的多个子TB分别进行第二编码，所述第二编码为压缩和信道编码联合的编码模式；
发送单元1300，用于向所述终端设备发送资源调度信息，所述资源调度信息用于指示所述通信装置为所述待发送上行数据分配的空口资源，所述空口资源是根据所述待发送上行数据的数据量和所述压缩参数确定的。
可选地，在一个实施例中，所述发送单元1300，还用于：
在所述空口资源上接收来自于所述终端设备的第一上行数据，所述第一上行数据是所述终端设备的物理层对第一传输块TB进行所述第一编码获得的，或者，所述第一上行数据是所述终端设备的物理层对根据第一TB获得的多个子TB分别进行所述第二编码获得的，所述第一TB是根据所述压缩参数对所述待发送上行数据进行数据组包获得的。
可选地，在一个实施例中，所述压缩参数为压缩比，所述压缩比为所述待发送上行数据的估计压缩后长度和压缩前长度的比值；或者，
所述压缩参数为所述待发送上行数据的估计压缩后长度。
可选地，在一个实施例中，所述资源调度信息包括资源指示信息和调制与编码策略MCS信息。
可选地，在一个实施例中，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第一类型的缓冲区状态报告，所述第一类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
所述第一类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，所述LCG ID字段具有多个不同取值，所述多个不同取值分别对应不同的原生数据类型。
可选地，在一个实施例中，所述第一类型的缓冲区状态报告包含压缩信息字段，所述压缩信息字段携带LCG ID字段所对应的原生数据类型的待发送数据的所述压缩信息。
可选地，在一个实施例中，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第二类型的缓冲区状态报告，所述第二类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
所述第二类型的缓冲区状态报告是对媒体接入控制MAC层的短缓冲区状态报告或长 缓冲区状态报告扩展得到的，所述第二类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，
所述LCG ID字段包括x个比特，所述缓冲区状态字段为一个，所述x个比特具有y个不同取值，所述y个取值中的p个取值分别对应不同的原生数据类型，所述y个取值中的q个取值分别对应不同的逻辑信道类型，当所述LCG ID字段为所述y个取值中的第一取值时，所述缓冲区状态字段用于指示所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量，p+q≤y,y＝2 x，x,y,p和q均为整数；
或者，
所述LCG ID字段包括z个比特，所述z个比特中的k个比特与k个原生数据类型满足比特映射关系，所述z个比特中的r个比特与r个逻辑信道类型满足比特映射关系，所述z个比特中的每个比特具有第二取值或第三取值，当所述z个比特中的第j个比特为所述第二取值时，所述第j个比特对应的原生数据类型或逻辑信道类型被选中，当所述z个比特中的第j个比特为所述第三取值时，所述第j个比特对应的原生数据类型或逻辑信道类型未被选中；若所述z个比特中的w个比特为所述第二取值，所述缓冲区状态字段有w个，所述w个缓冲区状态字段分别用于指示和所述w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，z＝k+r,1≤j≤z,1≤w≤z,z,k,r,j和w均为正整数。
可选地，在一个实施例中，若所述缓冲状态字段为一个，所述第二类型的缓冲区状态报告还包括一个压缩信息字段，当所述x个比特为所述y个取值中的第一取值时，所述压缩信息字段携带所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息；
若所述缓冲状态字段为w个，所述第二类型的缓冲区状态报告还包括w个压缩信息字段，所述w个压缩信息字段分别携带所述w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息。
在以上各实现方式中，接收单元1200和发送单元1300也可以集成为一个收发单元或者一个输入输出单元，同时具备接收和发送的功能，这里不作限定。
在通信装置1000对应终端设备的各实施例中，处理单元1100用于执行除了发送和接收的动作之外由终端设备内部实现的处理和/或操作。接收单元1200用于执行终端设备的接收的动作，发送单元1300用于执行终端设备的发送的动作。
例如，在图6中，发送单元1300执行步骤610、步骤620中的发送的动作；接收单元1200执行步骤630中接收的动作。此外，处理单元1100执行各方法实施例中的如下处理：根据资源指示和MCS指示确定组包长度；根据组包长度和压缩信息进行组包，获得第一TB，等。
在通信装置1000对应网络设备的各实施例中，处理单元1100用于执行除了发送和接收的动作之外由网络设备内部实现的处理和/或操作。接收单元1200用于执行网络设备的接收的动作，发送单元1300用于执行网络设备的发送的动作。
例如，在图6中，接收单元1200执行步骤610和步骤620中的接收的动作。可选地，接收单元1200执行步骤640中接收的动作。发送单元1300执行步骤630中的发送的动作。此外，处理单元1100执行各方法实施例中的如下处理：根据接收到的缓冲区状态报告中的终端设备的待发送上行数据的数据量和压缩信息，确定所要调度的空口资源等。
参见图12，图12为本申请提供的通信装置的示意性结构图。如图12，通信装置10包括：一个或多个处理器11，一个或多个存储器12以及一个或多个通信接口13。处理器11用于控制通信接口13收发信号，存储器12用于存储计算机程序，处理器11用于从存储器12中调用并运行该计算机程序，以使得通信装置10执行本申请各方法实施例中由终端设备或网络设备执行的处理。
例如，处理器11可以具有图11中所示的处理单元1100的功能，通信接口13可以具有接收单元1200和/或发送单元1300的功能。具体地，处理器11可以用于执行由通信装置内部执行的处理或操作，通信接口13用于执行通信装置的发送和/或接收的操作。
在一种实现方式中，通信装置10可以为方法实施例中的终端设备。在这种实现方式中，通信接口13可以为终端设备的收发器。收发器可以包括接收器和/或发射器。可选地，处理器11可以为终端设备的基带装置，通信接口13可以为射频装置。
在另一种实现中，通信装置10可以为安装在终端设备中的芯片(或芯片系统)。在这种实现方式中，通信接口13可以为接口电路或者输入/输出接口。
在一种实现方式中，通信装置10可以为方法实施例中的网络设备。在这种实现方式中，通信接口13可以为网络设备的收发器。收发器可以包括接收器和/或发射器。可选地，处理器11可以为网络设备的基带装置，通信接口13可以为射频装置。
在另一种实现中，通信装置10可以为安装在网络设备中的芯片(或芯片系统)。在这种实现方式中，通信接口13可以为接口电路或者输入/输出接口。
其中，图12中器件(例如，处理器、存储器或通信接口)后面的虚线框表示该器件可以为一个以上。
可选地，上述各装置实施例中的存储器与处理器可以是物理上相互独立的单元，或者，存储器也可以和处理器集成在一起，本文不作限定。
此外，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机指令，当计算机指令在计算机上运行时，使得本申请各方法实施例中由终端设备执行的操作和/或处理被执行。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机指令，当计算机指令在计算机上运行时，使得本申请各方法实施例中由网络设备执行的操作和/或处理被执行。
此外，本申请还提供一种计算机程序产品，计算机程序产品包括计算机程序代码或指令，当计算机程序代码或指令在计算机上运行时，使得本申请各方法实施例中由终端设备执行的操作和/或处理被执行。
本申请还提供一种计算机程序产品，计算机程序产品包括计算机程序代码或指令，当计算机程序代码或指令在计算机上运行时，使得本申请各方法实施例中由网络设备执行的操作和/或处理被执行。
此外，本申请还提供一种芯片，所述芯片包括处理器，用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，使得安装有所述芯片的装置执行任意一个方法实施例中由终端设备执行的操作和/或处理。
进一步地，所述芯片还可以包括通信接口。所述通信接口可以是输入/输出接口，也可以为接口电路等。进一步地，所述芯片还可以包括所述存储器。
本申请还提供一种芯片，所述芯片包括处理器，用于存储计算机程序的存储器独立于芯片而设置，处理器用于执行存储器中存储的计算机程序，使得安装有所述芯片的装置执行任意一个方法实施例中由网络设备执行的操作和/或处理。
进一步地，所述芯片还可以包括通信接口。所述通信接口可以是输入/输出接口，也可以为接口电路等。进一步地，所述芯片还可以包括所述存储器。
可选地，上述处理器可以为一个或多个，所述存储器可以为一个或多个，所述存储器可以为一个或多个。
此外，本申请还提供一种通信装置(例如，可以为芯片或芯片系统)，包括处理器和通信接口，根据前述任意一个方法实施例中由终端设备执行的操作和/或处理，所述通信接口用于接收待处理的数据和/或信息，所述处理器处理所述数据和/或信息。可选地，通信接口还用于发送(或称为输出)处理器处理后的数据和/或信息。
本申请还提供一种通信装置(例如，可以为芯片或芯片系统)，包括处理器和通信接口，根据前述任意一个方法实施例中由网络设备执行的操作和/或处理，所述通信接口用于接收待处理的数据和/或信息；所述处理器处理所述数据和/或信息；所述通信接口用于发送(或称为输出)处理器处理后的数据和/或信息。
此外，本申请还提供一种通信装置，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，使得所述通信装置执行任意一个方法实施例中由终端设备执行的操作和/或处理。
本申请还提供一种通信装置，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，使得所述通信装置执行任意一个方法实施例中由网络设备执行的操作和/或处理。
此外，本申请还提供一种无线通信系统，包括本申请方法实施例中的终端设备和网络设备。
需要说明的是，“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。其中，A的数量并不限定，可以为一个，也可以为多于一个，B的数量也不限定，可以为一个，也可以为多于一个。
此外，在上述实施例中，第一、第二等仅为便于区分不同对象，而不应对本申请构成任何限定。例如，区分不同的缓冲区状态报告、不同的取值等。此外应理解，“第一”和“第二”并不表示所描述的对象一定不同。例如，第一取值和第二取值仅仅区分描述两个取值，第一取值和第二取值可以相同，也可以不同，不作限定。
本申请实施例中提及的处理器可以是中央处理单元(central processing unit,CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory,ROM)、 可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DRRAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (20)

  1. 一种调度资源的方法，其特征在于，包括：
    终端设备向网络设备发送缓冲区状态报告，所述缓冲区状态报告用于指示所述终端设备的待发送上行数据的数据量；
    所述终端设备向所述网络设备发送所述待发送上行数据的压缩信息，所述压缩信息指示与所述待发送上行数据的物理层处理相关的压缩参数，所述物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，所述物理层处理包括对根据所述TB获得的多个子TB分别进行第二编码，所述第二编码为压缩和信道编码联合的编码模式；
    所述终端设备接收来自于所述网络设备的资源调度信息，所述资源调度信息用于指示所述网络设备为所述待发送上行数据分配的空口资源，所述空口资源是根据所述待发送上行数据的数据量和所述压缩参数确定的。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备在所述空口资源上发送第一上行数据，所述第一上行数据是所述终端设备的物理层对第一传输块TB进行所述第一编码获得的，或者，所述第一上行数据是所述终端设备的物理层对根据所述第一TB获得的多个子TB分别进行所述第二编码获得的，所述第一TB是根据所述压缩参数对所述待发送上行数据进行数据组包获得的。
  3. 如权利要求1或2所述的方法，其特征在于，所述压缩参数为压缩比，所述压缩比为所述待发送上行数据的估计压缩后长度和压缩前长度的比值；或者，
    所述压缩参数为所述待发送上行数据的估计压缩后长度。
  4. 如权利要求2或3所述的方法，其特征在于，所述资源调度信息包括资源指示信息和调制与编码策略MCS信息，所述方法还包括：
    所述终端设备根据所述资源指示信息和所述MCS信息，确定组包长度；
    所述终端设备根据所述组包长度和所述压缩参数，对所述待发送上行数据进行数据组包，获得所述第一TB，其中，所述第一TB中包含的待发送上行数据的估计压缩后长度小于或等于所述组包长度；
    所述终端设备对所述第一TB进行所述物理层处理，获得所述第一上行数据。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第一类型的缓冲区状态报告，所述第一类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
    所述第一类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，所述LCG ID字段具有多个不同取值，所述多个不同取值分别对应不同的原生数据类型，所述缓冲区状态字段用于指示所述LCG ID字段所对应的原生数据类型的待发送数据的数据量。
  6. 如权利要求5所述的方法，其特征在于，所述第一类型的缓冲区状态报告包含压缩信息字段，所述压缩信息字段携带所述LCG ID字段所对应的原生数据类型的待发送数据的所述压缩信息。
  7. 如权利要求1至4中任一项所述的方法，其特征在于，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第二类型的缓冲区状态报告，所述第二类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
    所述第二类型的缓冲区状态报告是对媒体接入控制MAC层的短缓冲区状态报告或长缓冲区状态报告扩展得到的，所述第二类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，
    所述LCG ID字段包括x个比特，所述缓冲区状态字段为一个，所述x个比特具有y个不同的取值，所述y个取值中的p个取值分别对应不同的原生数据类型，所述y个不同的取值中的q个取值分别对应不同的逻辑信道类型，当所述LCG ID字段为所述y个取值中的第一取值时，所述缓冲区状态字段用于指示所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量，p+q≤y,y＝2 x,x,y,p和q均为整数；
    或者，
    所述LCG ID字段包括z个比特，所述z个比特中的k个比特与k个原生数据类型满足比特映射关系，所述z个比特中的r个比特与r个逻辑信道类型满足比特映射关系，所述z个比特中的每个比特具有第二取值或第三取值，当所述z个比特中的第j个比特为所述第二取值时，所述第j个比特对应的原生数据类型或逻辑信道类型被选中，当所述z个比特中的第j个比特为所述第三取值时，所述第j个比特对应的原生数据类型或逻辑信道类型未被选中；若所述z个比特中的w个比特为所述第二取值，所述缓冲区状态字段有w个，所述w个缓冲区状态字段分别用于指示和所述w个比特对应的原生数据类型和/或逻辑信道类型的待发送数据的数据量，z＝k+r,1≤j≤z,1≤w≤z,z,k,r,j和w均为正整数。
  8. 如权利要求7所述的方法，其特征在于，若所述缓冲状态字段为一个，所述第二类型的缓冲区状态报告还包括一个压缩信息字段，当所述x个比特为所述y个取值中的第一取值时，所述压缩信息字段携带所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息；
    若所述缓冲状态字段为w个，所述第二类型的缓冲区状态报告还包括w个压缩信息字段，所述w个压缩信息字段分别携带所述w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息。
  9. 一种调度资源的方法，其特征在于，包括：
    网络设备接收来自于终端设备的缓冲区状态报告，所述缓冲区状态报告用于指示所述终端设备的待发送上行数据的数据量；
    所述网络设备接收来自于所述终端设备的所述待发送上行数据的压缩信息，所述压缩信息指示与所述待发送上行数据的物理层处理相关的压缩参数，所述物理层处理包括对传输块TB进行第一编码，第一编码为压缩和信道编码分离的编码模式，或者，所述物理层处理包括对根据所述TB获得的多个子TB分别进行第二编码，所述第二编码为压缩和信道编码联合的编码模式；
    所述网络设备向所述终端设备发送资源调度信息，所述资源调度信息用于指示所述网络设备为所述待发送上行数据分配的空口资源，所述空口资源是根据所述待发送上行数据的数据量和所述压缩参数确定的。
  10. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述网络设备在所述空口资源上接收来自于所述终端设备的第一上行数据，所述第一上行数据是所述终端设备的物理层对第一传输块TB进行所述第一编码获得的，或者，所述第一上行数据是所述终端设备的物理层对根据第一TB获得的多个子TB分别进行所述第二编码获得的，所述第一TB是根据所述压缩参数对所述待发送上行数据进行数据组包获得的。
  11. 如权利要求9或10所述的方法，其特征在于，所述压缩参数为压缩比，所述压缩比为所述待发送上行数据的估计压缩后长度和压缩前长度的比值；或者，
    所述压缩参数为所述待发送上行数据的估计压缩后长度。
  12. 如权利要求9至11中任一项所述的方法，其特征在于，所述资源调度信息包括资源指示信息和调制与编码策略MCS信息。
  13. 如权利要求9至11中任一项所述的方法，其特征在于，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第一类型的缓冲区状态报告，所述第一类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
    所述第一类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，所述LCG ID字段具有多个不同取值，所述多个不同取值分别对应不同的原生数据类型，所述缓冲区状态字段用于指示所述LCG ID字段所对应的原生数据类型的待发送数据的数据量。
  14. 如权利要求13所述的方法，其特征在于，所述第一类型的缓冲区状态报告包含压缩信息字段，所述压缩信息字段携带所述LCG ID字段所对应的原生数据类型的待发送数据的所述压缩信息。
  15. 如权利要求9至11中任一项所述的方法，其特征在于，所述待发送上行数据为物理层的原生数据，所述缓冲区状态报告为第二类型的缓冲区状态报告，所述第二类型的缓冲区状态报告用于指示待发送的所述原生数据的数据量；
    所述第二类型的缓冲区状态报告是对媒体接入控制MAC层的短缓冲区状态报告或长缓冲区状态报告扩展得到的，所述第二类型的缓冲区状态报告包含逻辑信道组标识LCG ID字段和缓冲区状态字段，其中，
    所述LCG ID字段包括x个比特，所述缓冲区状态字段为一个，所述x个比特具有y个不同的取值，所述y个取值中的p个取值分别对应不同的原生数据类型，所述y个取值中的q个取值分别对应不同的逻辑信道类型，当所述LCG ID字段为所述y个取值中的第一取值时，所述缓冲区状态字段用于指示所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的数据量，p+q≤y,y＝2 x，x,y,p和q均为整数；
    或者，
    所述LCG ID字段包括z个比特，所述z个比特中的k个比特与k个原生数据类型满足比特映射关系，所述z个比特中的r个比特与r个逻辑信道类型满足比特映射关系，所述z个比特中的每个比特具有第二取值或第三取值，当所述z个比特中的第j个比特为所述第二取值时，所述第j个比特对应的原生数据类型或逻辑信道类型被选中，当所述z个比特中的第j个比特为所述第三取值时，所述第j个比特对应的原生数据类型或逻辑信道类型未被选中；若所述z个比特中的w个比特为所述第二取值，所述缓冲区状态字段有w个，所述w个缓冲区状态字段分别用于指示和所述w个比特对应的原生数据类型和/或逻 辑信道类型的待发送数据的数据量，z＝k+r,1≤j≤z,1≤w≤z,z,k,r,j和w均为正整数。
  16. 如权利要求15所述的方法，其特征在于，若所述缓冲状态字段为一个，所述第二类型的缓冲区状态报告还包括一个压缩信息字段，当所述x个比特为所述y个取值中的第一取值时，所述压缩信息字段携带所述第一取值对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息；
    若所述缓冲状态字段为w个，所述第二类型的缓冲区状态报告还包括w个压缩信息字段，所述w个压缩信息字段分别携带所述w个比特各自所对应的原生数据类型或逻辑信道类型的待发送数据的所述压缩信息。
  17. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所述通信装置执行如权利要求1-8中任一项所述的方法，或者如权利要求9-16中任一项所述的方法。
  18. 一种芯片，其特征在于，包括处理器和通信接口，所述通信接口用于接收数据和/或信息，并将接收到的数据和/或信息传输至所述处理器，所述处理器处理所述数据和/或信息，以执行如权利要求1-8中任一项所述的方法，或者如权利要求9-16中任一项所述的方法。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机指令，当计算机指令在计算机上运行时，使得如权利要求1-8中任一项所述的方法，或如权利要求9-16中任一项所述的方法被实现。
  20. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得如权利要求1-8中任一项所述的方法，或如权利要求9-16中任一项所述的方法被实现。
PCT/CN2022/104584 2022-07-08 2022-07-08 调度资源的方法和通信装置 WO2024007291A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/104584 WO2024007291A1 (zh) 2022-07-08 2022-07-08 调度资源的方法和通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/104584 WO2024007291A1 (zh) 2022-07-08 2022-07-08 调度资源的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2024007291A1 true WO2024007291A1 (zh) 2024-01-11

Family

ID=89454583

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/104584 WO2024007291A1 (zh) 2022-07-08 2022-07-08 调度资源的方法和通信装置

Country Status (1)

Country Link
WO (1) WO2024007291A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090296637A1 (en) * 2007-08-12 2009-12-03 Patrick Fischer Wireless device and method of transmitting uplink data and buffer status reports in a wireless communications system
CN111711967A (zh) * 2014-11-14 2020-09-25 高通股份有限公司 用于eDCS的缓存器状态报告
CN113472480A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 一种传输处理方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090296637A1 (en) * 2007-08-12 2009-12-03 Patrick Fischer Wireless device and method of transmitting uplink data and buffer status reports in a wireless communications system
CN111711967A (zh) * 2014-11-14 2020-09-25 高通股份有限公司 用于eDCS的缓存器状态报告
CN113472480A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 一种传输处理方法及设备

Similar Documents

Publication Publication Date Title
US10999890B2 (en) Data processing method, apparatus, and system
US11445404B2 (en) Method and apparatus for wireless communication in wireless communication system
US11296841B2 (en) Communications method and apparatus
WO2019213924A1 (zh) 通信方法、通信装置和系统
US20190215901A1 (en) Data transmission method, device and system
EP3968555A1 (en) Downlink control information sending method and apparatus, and readable storage medium
CN113114411B (zh) 数据传输方法和设备
US20230139754A1 (en) Coding method and apparatus
US20200296620A1 (en) Method for transmitting data, terminal device and network device
WO2024007291A1 (zh) 调度资源的方法和通信装置
TWI826994B (zh) 一種實體層控制資訊的傳輸方法和裝置
WO2022021021A1 (zh) 无线通信方法、终端设备和网络设备
CN114902637B (zh) 一种数据传输方法及装置
WO2024007292A1 (zh) 发送数据和接收数据的方法以及通信装置
WO2023051417A1 (zh) 一种通信方法及装置
US20240129068A1 (en) Communication method and apparatus
WO2024140241A1 (zh) 数据传输方法和装置
EP4443781A1 (en) Communication method and device
WO2021169517A1 (zh) 通信方法及装置
WO2022152272A1 (zh) 上行控制信息uci传输方法和装置
WO2024168869A1 (en) Wireless communication method and related devices
WO2024208024A1 (zh) 通信方法和通信装置
CN115915253A (zh) 一种通信方法及装置
WO2024165436A1 (en) Methods, communications devices, and infrastructure equipment
WO2020224781A1 (en) Data allocation in cellular communication

Legal Events

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

Ref document number: 22949874

Country of ref document: EP

Kind code of ref document: A1