Resource scheduling method and communication device

Abstract

The invention provides a resource scheduling method and a communication device, which can be applied to uplink data transmission. In the embodiment of the invention, the terminal equipment sends a buffer status report to the network equipment to report the data volume of uplink data to be sent, and meanwhile, the terminal equipment also sends compression information of the uplink data to be sent to the network equipment, and the compression information indicates a compression parameter related to physical layer processing of the uplink data to be sent. The physical layer processing may include a coding mode in which compression and channel coding are separated on the TB, or the physical layer processing may include a coding mode in which compression and channel coding are combined on a plurality of sub-TBs obtained according to the TB, respectively. In the embodiment of the invention, the network equipment schedules the air interface resource for the uplink data to be sent of the terminal equipment according to the data volume and the compression information of the uplink data to be sent, so that the problem of uplink resource mismatch caused by introduction of a compression and channel coding separated coding mode or a compression and channel coding combined coding mode in a physical layer can be solved.

Description

Method and communication device for scheduling resources Technical Field

[0001] Embodiments of the present application relate to the field of wireless communication technologies, and more specifically, to a method and communication device for scheduling resources. Background Art

[0002] In cellular systems, Layer 1, the physical layer (PHY), is primarily responsible for data channel coding, modulation, and resource mapping. Layer 2, the media access control (MAC), is primarily responsible for data packetization and resource scheduling. In current cellular systems, all operations in the PHY and MAC layers assume that the transmitted data from upper layers is inherently free of redundancy, or ignore any inherent redundancy, focusing solely on mitigating channel transmission errors. Consequently, only channel coding (CC) is employed. However, in practice, the transmitted data at the physical layer may contain some redundancy. For example, application layer compression algorithms fail to fully exploit redundancy in the data, or upper layer data is uncompressed. Furthermore, raw data generated by the air interface may include channel state information (CSI), positioning, imaging, and environmental reconstruction, as well as sensory data generated by new air interface sensing functions. However, using separate or combined compression and channel coding schemes for transmitted data at the physical layer can achieve better transmission performance than using channel coding alone.

[0003] However, the existing cellular system communication protocol does not support the above coding mode at the physical layer. If the above coding mode is introduced at the physical layer, it will cause problems in uplink resource scheduling, such as uplink resource mismatch.

[0004] Summary of the Invention

[0005] The present application provides a method for scheduling resources, which can support the physical layer to adopt a coding mode that separates compression and channel coding, or a coding mode that combines compression and channel coding, without causing problems in uplink resource scheduling.

[0006] In a first aspect, a method for scheduling resources is provided. The method can be applied to a transmitting end of wireless communication or to a chip or chip system at the transmitting end. Here, the transmitting end may refer to a transmitting end of data transmission. The following description uses a terminal device as an example. The method includes:

[0007] The terminal device sends a buffer status report to the network device, where the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device;

[0008] The terminal device sends compression information of 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, where the physical layer processing includes performing a first encoding on a transport block TB, where the first encoding is a coding mode in which compression and channel coding are separated, or where the physical layer processing includes performing a second encoding on each of a plurality of sub-TBs obtained from the TB, where the second encoding is a coding mode in which compression and channel coding are combined;

[0009] The terminal device receives resource scheduling information from the network device. The resource scheduling information is used to indicate the air interface resources allocated by the network device 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.

[0010] In the technical solution of the present application, the terminal device sends a buffer status report to the network device to report the data volume of the uplink data to be sent. At the same time, the terminal device also sends compression information of the uplink data to be sent to the network device, and the compression information indicates the compression parameters related to the physical layer processing of the uplink data to be sent. The physical layer processing may include a coding mode that compresses or separates the channel coding of the TB (the coding mode of SSCC), or the physical layer processing includes a coding mode that compresses and combines the channel coding of multiple sub-TBs obtained according to the TB (the coding mode of JSCC). 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, which can solve the problem of uplink resource mismatch caused by the introduction of a coding mode that separates compression and channel coding, or a coding mode that combines compression and channel coding, at the physical layer.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:

[0012] The terminal device sends first uplink data on the air interface resource. The first uplink data is obtained by performing a first encoding on the first transmission block TB at the physical layer, or the first uplink data is obtained by performing a second encoding on multiple sub-TBs obtained according to the first TB at the physical layer. The first TB is obtained by packetizing the uplink data to be sent according to the compression parameters.

[0013] In conjunction with the first aspect, in certain implementations of the first aspect, the resource scheduling information includes resource indication information and modulation and coding strategy (MCS) information, and the method further includes:

[0014] The terminal device determines the packet length based on the resource indication information and MCS information;

[0015] The terminal device performs data packetization on the uplink data to be sent according to the packetization length and the compression parameter to obtain a first TB, wherein the estimated compressed length of the uplink data to be sent contained in the first TB is less than or equal to the packetization length;

[0016] The terminal device performs the physical layer processing on the first TB to obtain the first uplink data.

[0017] This implementation introduces the SSCC or JSCC coding mode into the physical layer, providing a feasible physical layer processing mechanism.

[0018] In a second aspect, a method for scheduling resources is provided. The method can be applied to a receiving end of wireless communication or to a chip or chip system at the receiving end. The receiving end can refer to a receiving end of data transmission. The following description uses a network device as an example. The method includes:

[0019] The network device receives a buffer status report from the terminal device, where the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device;

[0020] The network device receives compression information of uplink data to be sent from the terminal device, where the compression information indicates a compression parameter related to physical layer processing of the uplink data to be sent, where the physical layer processing includes performing a first encoding on a transport block TB, where the first encoding is a coding mode in which compression and channel coding are separated, or where the physical layer processing includes performing a second encoding on each of a plurality of sub-TBs obtained from the TB, where the second encoding is a coding mode in which compression and channel coding are combined;

[0021] The network device sends resource scheduling information to the terminal device. The resource scheduling information is used to indicate the air interface resources allocated by the network device for the uplink data to be sent. The air interface resources are determined according to the data volume and compression parameters of the uplink data to be sent.

[0022] The beneficial technical effects of the second aspect can be found in the description of the first aspect and will not be elaborated on here.

[0023] In conjunction with the second aspect, in certain implementations of the second aspect, the method further includes:

[0024] The network device receives the first uplink data from the terminal device on the air interface resources. The first uplink data is obtained by the physical layer of the terminal device performing a first encoding on the first transmission block TB, or the first uplink data is obtained by the physical layer of the terminal device performing a second encoding on multiple sub-TBs obtained based on the first TB. The first TB is obtained by packetizing the uplink data to be sent according to the compression parameters.

[0025] In certain implementations of the first aspect or the second aspect, the compression parameter is a compression ratio, which is a ratio of an estimated compressed length of the uplink data to be sent to a length before compression; or

[0026] The compression parameter is the estimated compressed length of the uplink data to be sent.

[0027] In certain implementations of the first aspect or the second aspect, the uplink data to be sent is native data of the physical layer, and the buffer status report is a first type of buffer status report, where the first type of buffer status report is used to indicate a data volume of the native data to be sent;

[0028] The first type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field. The LCG ID field has 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 to be sent of the native data type corresponding to the LCG ID field.

[0029] In this implementation, a corresponding type of buffer status report is designed for the physical layer native data type, which is used for reporting the physical layer native data.

[0030] In certain implementations of the first aspect or the second aspect, the first type of buffer status report includes a compression information field, where the compression information field carries compression information of the to-be-sent data of the native data type corresponding to the LCG ID field.

[0031] In this implementation, the buffer status report for the physical layer native data type may also include compression information of the physical layer native data, providing a feasible mechanism for the UE to report the compression information of the physical layer native data.

[0032] In certain implementations of the first aspect or the second aspect, the uplink data to be sent is native data of the physical layer, and the buffer status report is a second type of buffer status report, where the second type of buffer status report is used to indicate a data volume of the native data to be sent;

[0033] The second type of buffer status report is obtained by extending the short buffer status report or the long buffer status report of the media access control MAC layer. The second type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field, wherein:

[0034] The LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, p of the y values ​​correspond to different native data types, and q of the y values ​​correspond to different logical channel types. When the LCG ID field is the first value among the y values, the buffer status field indicates the amount of data to be sent of the native data type or logical channel type corresponding to the first value, p + q ≤ y, y = 2 x ,x,y,p and q are all integers;

[0035] or,

[0036] The LCG ID field includes z bits, k bits among the z bits satisfy a bit mapping relationship with k native data types, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. Each of the z bits 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. 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. If w bits among the z bits are the second value, there are w buffer status fields, and the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, z=k+r, 1≤j≤z, 1≤w≤z, z, k, r, j and w are all positive integers.

[0037] In this implementation, by extending the short BSR or long BSR of the MAC layer, the extended BSR can be reused for reporting physical layer native data, which can save the bit overhead caused by introducing buffer status reports for physical layer native data.

[0038] In certain implementations of the first or second aspects, if the buffer status field is one, the second type of buffer status report further includes a compression information field, and when the x bits are a first value among y values, the compression information field carries compression information of the to-be-transmitted data of the native data type or logical channel type corresponding to the first value;

[0039] If there are w buffer status fields, the second type of buffer status report further includes w compression information fields, where the w compression information fields respectively carry compression information of the to-be-sent data of the native data type or logical channel type corresponding to each of the w bits.

[0040] In this implementation, the extended BSR may further include compression information, providing a feasible mechanism for the UE to report compression information of physical layer native data.

[0041] In a third aspect, a communication device is provided, wherein the communication device has the function of implementing the method of the first aspect or any possible implementation of the first aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0042] In a fourth aspect, a communication device is provided, wherein the communication device has the function of implementing the method of the second aspect or any possible implementation of the second aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

[0043] In a fifth aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the first aspect or any possible implementation of the first aspect.

[0044] In a sixth aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory and control the transceiver to transmit and receive signals, so that the communication device performs the method according to the second aspect or any possible implementation of the second aspect.

[0045] In the seventh aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor; 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 executes the method as in the first aspect, or any possible implementation of the first aspect.

[0046] In an eighth aspect, a communication device is provided, comprising a processor and a communication interface, wherein 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 executes the method as in the second aspect, or any possible implementation of the second aspect.

[0047] Optionally, in the fifth to eighth aspects above, there may be one or more processors, one or more memories, and one or more transceivers.

[0048] In a ninth aspect, a communication device is provided, comprising at least one processor coupled to at least one memory, wherein the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the communication device performs the method as in the first aspect, or any possible implementation of the first aspect.

[0049] In the tenth aspect, a communication device is provided, comprising at least one processor coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the communication device performs the method as in the second aspect, or any possible implementation of the second aspect.

[0050] In the eleventh aspect, a computer-readable storage medium is provided, in which computer instructions are stored. When the computer instructions are run on a computer, the method in the first aspect, or the second aspect, or any possible implementation of these aspects is executed.

[0051] In the twelfth aspect, a computer program product is provided, which includes a computer program code, and when the computer program code is run on a computer, the method in the first aspect, or the second aspect, or any possible implementation of any of these aspects is executed.

[0052] In a thirteenth aspect, a wireless communication system is provided, comprising the communication device as described in the third aspect and the communication device as described in the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic diagram of the uplink resource application, scheduling and data transmission process in a cellular system.

[0054] FIG2 is a schematic diagram showing the relationship between uplink resource scheduling and coding modulation.

[0055] FIG3 is a schematic diagram showing the relationship between uplink resource scheduling and coding modulation when the physical layer of a cellular system adopts SSCC.

[0056] FIG4 is a schematic diagram of uplink resource allocation after SSCC or JSCC is introduced into the physical layer.

[0057] FIG5 is a schematic architecture diagram of a communication system for the resource scheduling method provided in this application.

[0058] FIG6 is a schematic flowchart of the method for scheduling resources provided in this application.

[0059] FIG7 is a schematic diagram of calculating the sparsity of uplink data to be sent in the buffer by PB and estimating the compression ratio.

[0060] FIG8 is a schematic diagram of using an 8-bit quantization compression ratio and adding it to a short BSR or a long BSR for reporting.

[0061] FIG9 is a schematic structural diagram of a BSR for native data types.

[0062] FIG10 is a schematic diagram of data packetization by a terminal device according to packet length and compression ratio.

[0063] FIG11 is a schematic block diagram of a communication device provided in this application.

[0064] FIG12 is a schematic structural diagram of the communication device provided in this application. DETAILED DESCRIPTION

[0065] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0066] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as the 5th generation (5G) system or the new radio (NR) system, the long term evolution (LTE) system, the long term evolution-advanced (LTE-A) system, the LTE frequency division duplex (FDD) system, the 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, machine type communication (MTC), and the Internet of Things (IoT) communication system or other communication systems, etc. In addition, the present invention can also be extended to similar wireless communication systems, such as wireless-fidelity (WiFi), worldwide interoperability for microwave access (WIMAX), and communication systems related to the 3rd Generation Partnership Project (3GPP), without limitation.

[0067] The communication system applicable to the present application may include one or more transmitting ends and one or more receiving ends. Optionally, one of the transmitting end and the receiving end may be a terminal device, and the other may be a network device.

[0068] Some embodiments of this document use the 5G system as an example to introduce specific solution details. It is understandable that when this solution is used in other communication systems, such as the LTE system, or future communication systems, the various messages, channels, or information in the solution can be replaced with messages, channels, or information that can achieve corresponding functions in other communication systems, and this application does not limit this. For example, the buffer status report in 5G can be (buffer status report, BSR), and the physical uplink shared channel in 5G can be (physical uplink shared channel, PUSCH).

[0069] For example, a terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc.

[0070] In the embodiments of the present application, the device for implementing the function of the terminal can be the terminal, or it can be a device that can support the terminal to implement the function, such as a chip system or chip, which can be installed in the terminal. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0071] Exemplarily, the network device may be a device with wireless transceiver functions, and the network device may be a device that provides wireless communication function services, usually located on the network side, including but not limited to the next generation base station (gNodeB, gNB) in the fifth generation (5G) communication system, the base station in the sixth generation (6G) mobile communication system, the base station in the future mobile communication system or the access node in the wireless fidelity (WiFi) system, the evolved node B (eNB) in the long term evolution (LTE) system, the radio network controller (RNC), the node B (NB), the base station controller (BSC), the home base station (for example, home evolved NodeB, or home Node B, HNB), the base band unit (BBU), the transmission reception point (TRP), the transmitting point (TP), the base transceiver station (BTS), etc. In a network structure, the network equipment may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a RAN device including a control plane CU node and a user plane CU node, and a DU node, or the network equipment may also be a wireless controller, a relay station, a vehicle-mounted device, and a wearable device in a cloud radio access network (CRAN) scenario. In addition, the base station may be a macro base station, a micro base station, a relay node, a donor node, or a combination thereof. The base station may also refer to a communication module, a modem, or a chip for being set in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, a device that performs the base station function in future communication systems, etc. The base station can support networks with the same or different access technologies without limitation.

[0072] In the embodiments of the present application, the device for implementing the function of the network device can be the network device, or it can be a device that can support the network device to implement the function, such as a chip system or chip, which can be installed in the network device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0073] In existing cellular systems, the physical (PHY) and MAC layer operations assume that the data being transmitted from the upper layer has no redundancy, or ignore any redundancy, and only consider how to combat channel transmission errors. The basic process is shown in Figure 1.

[0074] Refer to Figure 1, which is a schematic diagram of the uplink resource application, scheduling and data transmission process in a cellular system. As shown in Figure 1, the base station schedules uplink resources for the UE based on information such as the UE's buffer status report and power headroom. Among them, 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 base station's resource scheduling is done by sending downlink control information (DCI) on the downlink control channel, for example, DCI format 0 (abbreviated as DCI 0), to inform the UE. The fields related to resource scheduling in DCI 0 are mainly resource indication and MCS indication, among which the resource indication is used to indicate the time-frequency resource for sending uplink data, and the MCS indication is used to indicate what channel coding rate and modulation order to use on the time-frequency resource. Refer to Figure 2, which is a schematic diagram of the relationship between uplink resource scheduling, coding, and modulation. As shown in Figure 2, the resource indicator and the MCS indicator jointly determine the size of the UE's physical layer transport block (TB) (i.e., the code block before channel coding), the channel coding code rate, and the size of the code block after channel coding. The code block after channel coding is modulated and mapped to the corresponding air interface resources for transmission.

[0075] It's known that the unit of data transmission at the physical layer is the transport block (TB). If a TB itself still has a certain degree of redundancy, introducing a separate coding mode for compression and channel coding, or a combined coding mode for compression and channel coding, at the physical layer can further improve data transmission performance by leveraging the redundancy of the physical layer data to be transmitted. However, the physical layer of cellular systems does not support separate or combined coding modes for compression and channel coding, and the protocol layer (for example, the signaling process for resource scheduling) does not support the implementation of this function at the physical layer.

[0076] It should be noted that source coding is often also understood as compression. Therefore, the industry generally refers to the coding mode that separates compression and channel coding as separate source and channel coding (SSCC), and the coding mode that combines compression and channel coding as joint source and channel coding (JSCC). Therefore, SSCC coding below refers to the coding mode that separates compression and channel coding, and JSCC refers to the coding mode that combines compression and channel coding.

[0077] Introducing SSCC or JSCC at the physical layer can improve data transmission performance. However, since the existing cellular system protocol layer supports the use of SSCC or JSCC at the physical layer, it also brings the problem of uplink resource scheduling mismatch.

[0078] Refer to Figure 3, which is a schematic diagram of the relationship between uplink resource scheduling and coding modulation when the physical layer of a cellular system adopts SSCC. As mentioned above, the resource indicator and MCS indicator in the downlink control information of the base station jointly determine the TB size (such as the length L in Figure 3), coding modulation, and resource mapping (resource size). It can be seen that the resource indicator and MCS indicator are indispensable for successful decoding at the receiving end. After the physical layer introduces SSCC, the data must first be compressed (lossy or lossless) to compress the TB of length L scheduled by the base station into a new TB of length L'. Optionally, a CRC (such as CRC') or padding can be added to the new TB. Without loss of generality, the padding is usually filled with 0s before channel coding is performed.

[0079] When scheduling uplink resources, the base station needs to refer to information such as the BSR reported by the UE to determine how much air interface resources to allocate to the UE, primarily considering 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 transmitted before compression, the base station does not know the amount of compressed data, resulting in waste of uplink resources scheduled by the base station. Figure 4 shows a schematic diagram of uplink resource allocation after the introduction of SSCC or JSCC at the physical layer. However, if the BSR sent by the UE reports the size L′ of the compressed data, the UE must compress the uplink data to be transmitted in advance, which will cause packet assembly delays and pose significant implementation difficulties. This is because the UE does not know the data size to be compressed before receiving scheduling information (specifically, resource indication and MCS indication) from the network. In other words, the UE does not know the size of L.

[0080] Similarly, if JSCC is introduced at the physical layer, similar uplink resource allocation problems will arise. This is because JSCC utilizes the redundancy of the data to be sent to simultaneously compress and channel-code the data to be sent. In essence, it can be considered to be using a puncturing pattern different from the channel coding and adopting a higher channel coding rate based on the redundancy of the data to be sent. Equivalently, it can also be considered to be utilizing the redundancy of the signal source to reduce the consumption of air interface resources while maintaining the same error protection effect. Therefore, it can be considered as a data compression before channel coding. Therefore, the problems caused by using JSCC at the physical layer for uplink resource allocation are the same as those caused by introducing SSCC at the physical layer.

[0081] To this end, the present application provides a method for scheduling resources, which aims to solve the problem of uplink resource mismatch caused by the introduction of SSCC or JSCC at the physical layer (for example, the size of the air interface resources allocated by the network side for uplink data is greater than the air interface resources required for the uplink data actually sent by the UE).

[0082] That is, in this application, the physical layer not only considers channel error protection, but also utilizes the redundancy of the data to be sent in the physical layer, and adopts a coding mode that separates compression and channel coding, or a coding mode that combines compression and channel coding, for the data in the physical layer.

[0083] Refer to Figure 5, which is a schematic architecture diagram of a communication system applicable to the method for scheduling resources provided in the present application. As shown in Figure 5, the method for scheduling resources provided in the present application is mainly applicable to the scenario of uplink data transmission between a network device and a terminal device, and can also be applicable to data transmission between terminal devices, that is, sidelink (SL) data transmission, which is not limited in the present application. Therefore, the transmitting end in this article may refer to a terminal in uplink data transmission, or may refer to a transmitting 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 describes the technical solution of the present application by taking uplink data transmission as an example.

[0084] In the technical solution of the present application, a terminal device reports a buffer status report to a network device, where the buffer status report indicates the amount of uplink data to be transmitted. Simultaneously, the terminal device sends compression information about the uplink data to the network device, where the compression information indicates compression parameters related to physical layer processing of the uplink data to be transmitted. Based on the amount of uplink data to be transmitted and the compression parameters, the network device schedules air interface resources for the uplink data to be transmitted by the terminal device. This avoids the problem of mismatched air interface resources scheduled by the network device after the introduction of SSCC or JSCC at the physical layer of the terminal device.

[0085] The terminal device in the embodiment of the present application may be the terminal device 120 or 130 shown in Figure 5, and the network device may be the network device 110 shown in Figure 5. Figure 5 is merely an example, and the communication system may further include other communication devices, for example, more terminal devices, or more network devices, etc., without limitation.

[0086] See FIG6 , which is a schematic flowchart of the method for scheduling resources provided in this application.

[0087] 610. 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.

[0088] Optionally, the uplink data to be sent here may refer to data from the application layer, or may also be physical layer native data, without limitation. The following will describe in detail the buffer status report of the terminal device reporting physical layer native data to the network side.

[0089] 620. 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.

[0090] Optionally, physical layer processing may include:

[0091] Performing a first encoding on the TB, a coding mode in which the first coding compression and channel coding are separated; or,

[0092] Second coding is performed on each of the multiple sub-TBs obtained according to the TB. The second coding is a coding mode combining compression and channel coding.

[0093] The network device receives the buffer status report and compression information from the terminal device.

[0094] 630. The network device sends resource scheduling information to the terminal device. The resource scheduling information is used to indicate the air interface resources allocated by the network device to the uplink data to be sent by the terminal device. The air interface resources are determined according to the uplink data to be sent by the terminal device and compression parameters.

[0095] The terminal device receives resource scheduling information from the network device.

[0096] In the technical solution of the present application, 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, and at the same time reports the compression information of the uplink data to be sent. The compression information is the compression ratio (i.e., 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 the estimated compressed size of the uplink data to be sent (i.e., the estimated compressed length). Some implementation methods of the terminal device estimating the compression ratio will be introduced below. The terminal device sends the compressed information of the uplink data to be sent to the network device, which can assist the network device in scheduling uplink resources, so as to avoid the network device scheduling air interface resources for the uplink data to be sent of the terminal device without knowing the compression information related to the physical layer processing of the terminal device, resulting in a mismatch between the scheduled air interface resources and the amount of uplink data actually sent.

[0097] Furthermore, method 600 may further include step 640 .

[0098] 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.

[0099] The first uplink data is obtained by the physical layer of the terminal device performing the first encoding on the first TB, or the first TB is obtained by performing the second encoding on multiple sub-TBs obtained based on 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 transmitted according to the compression parameter.

[0100] Optionally, the terminal device may estimate the compression ratio of the uplink data to be sent through a variety of different implementations, of which only some examples are given below.

[0101] In one example, when counting the amount of data in the buffer of each logical channel (group), the radio link control (RLC) and packet data convergence protocol (PDCP) of the terminal device need to add the following compression ratio estimation process:

[0102] The grouping 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. Specifically, the uplink data to be sent in the buffer is divided into N blocks of size. sSeveral preprocessing blocks (PBs) are then processed, and sparsity statistics are performed on these PBs. Figure 7 shows a schematic diagram of calculating 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 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 referred to as the estimated compressed length in this text).

[0103] For example, when estimating the compressed length of uplink data to be sent, the following calculation method may be used:

[0104] In one calculation method, assuming that the length of the uplink data to be sent in the buffer before compression is L bits, according to the length N s , divide TB into K PBs, and record the sparsity of the i-th PB as S i (0≤S i ≤1), the corresponding entropy is H i , where H i =-S i log(S i )-(1-S i )log(1-S i ), the compressed length of the uplink data to be sent in the buffer is estimated to be

[0105] In another calculation method, a series of sparsity range intervals are set, and the right endpoint value of the range interval where the sparsity of each PB is located is counted, which is recorded as S′ i , the corresponding entropy is denoted as H′ i , then the estimated compressed length of the uplink data to be sent in the buffer is

[0106] After estimating the compressed length of the uplink data to be sent, the compression ratio can be calculated in combination with the pre-compression length. It should be understood that the compression ratio refers to the ratio of the estimated compressed length of the uplink data to be sent in the logical channel buffer to the pre-compression length, denoted as CR. In the first calculation method described above, CR = S / L; or in the second calculation method described above, CR = S' / L. Furthermore, the compression ratio can also be estimated based on historical information.

[0107] The above-mentioned method of estimating the compression ratio is only used as 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 the data compression algorithm to compress the selected data, and count the length of the selected data before compression and the length after compression, so as to obtain an estimate of the compression ratio. Exemplarily, the compression algorithm used in this calculation method can be an online arithmetic code, or a 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 when performing data compression.

[0108] The following are some examples of a terminal device sending compressed information to a network device.

[0109] Taking the example of a terminal device sending a compression ratio to a network device, the terminal device may optionally quantify the compression ratio and report the quantized information.

[0110] For example, the terminal device quantizes the compression ratio of each logical channel (group) into several levels, and uses a fixed x bits to represent the quantized compression ratio information, and the quantized compression ratio information can be reported to the network side together with the BSR. For example, the quantized compression ratio information and the BSR can be reported through the medium access control-control element (MAC CE). For example, the compression ratio can be quantized into one of 256 levels, and then 8 bits are used to indicate the quantization level. As an example, the quantization level can be added to the short BSR (short BSR) or the long BSR (long BSR) for reporting, that is, the compression information in this application can be reported by extending the short BSR or the long BSR, as described in Figure 8 below.

[0111] See Figure 8, which illustrates the use of 8-bit quantization of the compression ratio and its addition to a short or long BSR for reporting. A short BSR is typically used to report the buffer status of only one logical channel group or one type of native data. The short BSR includes an LCG ID and a buffer status field. The LCG ID uses 3 bits to identify a logical channel group, followed by a 5-bit buffer status field, which indicates the data volume in the buffer corresponding to that logical channel group. A long BSR can be used to simultaneously report the buffer status of multiple logical channel groups or multiple types of native data. LCG1 through LCG8 form an 8-bit bitmap corresponding to eight different logical channel group types. A bit value of 0 indicates that the corresponding logical channel group is not selected, while a bit value of 1 indicates that the corresponding logical channel group is selected. The data volume in the buffer corresponding to the selected logical channel group is appended to the buffer status field in the same order as the bitmap. The data volume in the buffer of each selected logical channel group is indicated by 8 bits.

[0112] Optionally, the uplink data to be sent by the terminal device in the present application may be native data of the physical layer.

[0113] Optionally, for reporting of physical layer native data, BSRs for different native data types may be added.

[0114] Exemplarily, the physical layer native data may include positioning data, reconstructed environment data, perception imaging data, etc., and may also be other types of physical layer native data, without limitation.

[0115] The following introduces several implementation methods of the terminal device provided in this application reporting physical layer native data to the network device, which are only used as examples.

[0116] Implementation (1)

[0117] For example, in one implementation, a new type of BSR can be defined. To distinguish it from the short and long BSRs at the MAC layer described above, this type of BSR is referred to herein as a first type of BSR. The first type of BSR can include a logical channel group identifier (LCG ID) field and a buffer status field. The LCG ID field has (or corresponds to) multiple different values ​​corresponding 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 native data of that native data type to be sent.

[0118] Implementation (2)

[0119] For example, in another implementation, the first type BSR may include an LCG ID field, a buffer status field, and a compression information field. Compared to the previous implementation, in this implementation, the first type BSR also includes a compression information field for indicating compression information (e.g., compression ratio) of the native data to be transmitted. Specifically, the compression information field is used to indicate the amount of data to be transmitted for the native data type corresponding to the LCG ID field.

[0120] In these two implementations, different values ​​of the LCG ID field of the first type of BSR correspond to different native data types. Exemplarily, the LCG ID field of the first type of BSR includes 4 bits. When the value of the 4 bits is 0000, it indicates that the first type of BSR corresponds to the positioning data type; accordingly, the buffer status field is used to indicate the data volume of the physical layer native positioning data to be sent; if the 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. When the value of the 4 bits is 00001, it indicates that the first type of BSR corresponds to the perceptual imaging data type; accordingly, the buffer status field is used to indicate the data volume of the physical layer native perceptual imaging data to be sent; if the compression information field is also included, the compression information field is used to indicate the compression information of the physical layer native perceptual imaging data to be sent.

[0121] Implementation (3)

[0122] For example, in one implementation, the BSR for reporting physical layer native data can reuse a short BSR or a long BSR, but the short BSR or the long BSR needs to be extended. For ease of description, the extended BSR is referred to as a second type of BSR.

[0123] Specifically, the LCG ID field of the short BSR or long BSR may be expanded to support more LCG IDs, and the extra LCG IDs are used to correspond to different native data types.

[0124] Exemplarily, the LCG ID field and the buffer status field of the short BSR or long BSR are extended. In this implementation, the extended BSR (ie, the second type of BSR) includes the LCG ID field and the buffer status field.

[0125] In one example, the short BSR is extended to obtain an extended BSR. The extended BSR includes an LCG ID field and a buffer status field. Among them, the LCG ID field includes x bits, and the x bits have (or correspond to) y values. p of the y values respectively correspond to different native data types, and q of the y values respectively correspond to different logical channel types. When the LCG ID field is the first value among the y values, the buffer status field is used to indicate the data volume of the data to be transmitted of the native data type or logical channel type corresponding to the first value. Among them, p + q ≤ y, and x, y, p, and q are all integers. When p + q < y, it means that there are reserved values among the y values. Exemplarily, y = 2 x .

[0126] In another example, the long BSR is extended to obtain an extended BSR. The extended BSR includes an LCG ID field and a buffer status field. Among them, the LCG ID field includes z bits. k of the z bits have a bit mapping relationship with k native data types, and r of the z bits have a bit mapping relationship with r logical channel types. Each of the z bits has a second value or a third value. When a certain bit among the z bits is the second value, it means that the native data type or logical channel type corresponding to this bit is selected. When this bit is the third value, it means that the native data type or logical channel type corresponding to this bit is not selected. If w of the z bits are the second value, then there are w buffer status fields in the extended BSR. The w buffer status fields are respectively used to indicate the data volume of the data to be transmitted of the native data type and / or logical channel type corresponding to the w bits. z = k + r, 1 ≤ w ≤ z, and z, k, w, and r are all positive integers. Exemplarily, the second value is 1, and the third value is 0, and it is not limited to other values.

[0127] Implementation method (4)

[0128] Optionally, the second type of BSR also includes a compression information field.

[0129] If the short BSR is extended to obtain an extended BSR, then the extended BSR includes a compression information field. Combining with the above implementation method (3), it can be seen that in this design, the extended BSR includes an LCG ID field, a buffer status field, and a compression information field. Among them, when the x bits of the LCG ID field are the first value among the y values, the compression information field carries the compression information of the data to be transmitted of the native data type or logical channel type corresponding to the first value.

[0130] If the long BSR is extended to obtain an extended BSR, the number of compressed information fields in the extended BSR changes dynamically. In combination with the above implementation method (3), it can be seen that in this design, the extended BSR includes an LCG ID field, and the LCG ID field contains z bits. When w bits of the z bits are the second value, it means that the native data type and / or logical channel type corresponding to the w bits are selected. At this time, the extended BSR includes w buffer status fields and w compressed information fields. Among them, the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, and the w compressed information fields respectively carry the compressed information of the data to be sent of the native data type or logical channel type corresponding to the w bits.

[0131] The above implementation (4) is described below with reference to Figure 9. Figure 9 is a schematic structural diagram of a BSR for native data types.

[0132] For example, as shown in FIG9 (a), taking the extended short BSR as an example, the LCG ID field is increased by 1 bit, from the original 3 bits to 4 bits, so that the LCG ID field can indicate 16 LCG IDs instead of the original 8 LCG IDs, and can indicate 8 more LCG IDs. These 8 additional LCG IDs can correspond to 8 native data types respectively. At the same time, the buffer status field is increased by 1 bit, from the original 5 bits to 6 bits. Optionally, the extended BSR also includes a compression information field. Taking the compression information as the compression ratio CR as an example, the compression information field can be a CR field. Exemplarily, the CR field contains 6 bits. It can be seen that in this example, the total length of the short BSR is extended to 16 bits. This extended BSR is an example of the second type of BSR mentioned above.

[0133] Taking the long BSR as an example, as shown in FIG9(b), 8 more bits can be directly added to the original LCG ID field, extending it from the original 8 bits to 16 bits. It should be understood that the LCG ID field of the extended BSR includes a total of 16 bits, of which 8 bits correspond to different logical channel types respectively. The additional 8 bits satisfy a bitmap relationship with the 8 native data types, and each bit corresponds to a native data type. Optionally, when a bit among the 16 bits of the LCG ID field is 1, it indicates that the native data type or logical channel type corresponding to the bit is selected. At this time, the extended BSR also includes the data volume of the selected native data type or logical channel type to be sent. Optionally, the extended BSR also includes compression information of the data to be sent of the selected native data type or logical channel type. Therefore, in this design, if w bits among the z bits included in the LCG ID field are 1, the extended BSR includes w buffer status fields, which are respectively used to report the data volume of the native data type and / or logical channel type to be sent corresponding to the w bits. Optionally, the extended BSR further includes w compression information fields, each carrying compression information of the to-be-transmitted data of the native data type and / or logical channel type corresponding to the w bits. For example, in FIG9(b), the buffer status field and / or the CR field each contain 8 bits, without limitation.

[0134] The above describes in detail the specific implementation of the terminal device estimating the compression ratio of the uplink data to be sent and the BSR of the terminal device reporting the original data to the network device.

[0135] In step 640, 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 a physical uplink shared channel (PUSCH). Taking NR as an example, the physical uplink shared channel may be PUSCH.

[0136] Optionally, if there is uplink control information (UCI) that needs to be sent, the terminal device multiplexes the first uplink data and UCI into the PUSCH for transmission.

[0137] As mentioned above, the first uplink data is obtained by the physical layer of the terminal device performing the first encoding on the first TB, or performing the second encoding on multiple sub-TBs obtained based on the first TB, and 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.

[0138] Specifically, after the terminal device receives the resource scheduling information from the network device, the resource scheduling information includes a resource indication and an MCS indication. The terminal device calculates the packet length (TB size) based on the resource indication and the MCS indication. Exemplarily, the method for calculating the packet length can refer to the specific implementation of determining TBS (TB size) in NR. After determining the packet length, the terminal device performs data packetization on the uplink data to be sent based on the packet length and the compression parameter to obtain the first TB. When packetizing, the terminal device estimates the compressed length of the uplink data to be sent based on the compression parameter 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 sufficient to fill the packet length. Therefore, 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. After obtaining the first TB, the first encoding can be performed on the first TB, or multiple sub-TBs can be obtained based on the first TB, and then the multiple sub-TBs can be respectively performed the second encoding, without limitation. Optionally, in the above embodiment, when packetizing, the terminal device specifically packetizes the RLC PDU in the buffer of each logical channel group. Optionally, if there is native data to be sent, the RLC PDU and native data in the buffer of each logical channel group are packetized to obtain the first TB.

[0139] Refer to Figure 10, which is a schematic diagram of a terminal device packetizing data based on packet length and compression ratio. It should be understood that 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 delivered to the MAC layer as an RLC PDU. The MAC layer performs scheduling, allocating the physical resources corresponding to the current transmission to several logical channel groups. The length of the RLC PDU for each logical channel group can be different. The RLC PDU is called a MAC SDU at the MAC layer. Several MAC SDUs are multiplexed into a single MAC PDU and transmitted via a physical layer channel. A single MAC PDU can carry data from multiple different logical channel groups. For the physical layer, a MAC PDU is called a TB. A TB is used to carry a single MAC PDU, and the size of the TB is determined by the number of physical resources allocated to the TB and the MCS. As shown in Figure 10, the packet length is denoted as T. When packetizing data, 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 S1+S2+S3+S4≤T in Figure 10. At this time, the first TB is obtained.

[0140] After obtaining 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.

[0141] Alternatively, the subsequent operation may be to perform JSCC processing on the first TB at the physical layer. First, pre-process the first TB. The pre-processing process is roughly as follows: pre-set 2 Q Sparsity range, then divide the first TB into B PBs according to a fixed length. For example, the length of each PB is N s Then multiple PBs are combined according to sparsity. For example, PBs with the same sparsity range are combined into a sub-TB, and 2 Q In addition, a control information sub-TB is created, which is used to indicate the sparsity information of each of the B PBs. For example, if the preset 2 Q Each sparsity range corresponds to an index. For example, the control information sub-TB can indicate the index of the sparsity range corresponding to the sparsity of each of the B PBs. Furthermore, since each PB requires Q bits to indicate its sparsity range, and there are B PBs in total, the length of the control information sub-TB is B·Q bits, where B and Q are both positive integers. It can be seen that according to the first TB, a total of 2 Q Sub-TBs and a control information sub-TB, i.e., the multiple sub-TBs obtained according to the first TB described in this document. JSCC is then performed on the multiple sub-TBs. It should be understood that each of the multiple sub-TBs is independently second-coded, that is, each sub-TB is processed using a combined compression and channel coding mode. In particular, during the JSCC process for the multiple sub-TBs, the compression rate of the control information sub-TB is 1. The resource reuse of different sub-TBs can be determined on the network side and the terminal side according to fixed rules.

[0142] When a terminal device multiplexes uplink data and UCI onto the PUSCH for transmission, the UCI may include one or more of the following types: hybrid automatic repeat request acknowledgement (HARQ-ACK) and channel state information (CSI). Optionally, the CSI may include CSI part 1 and CSI part 2.

[0143] The resource scheduling method provided by the present application is described in detail above. The communication device provided by the present application is introduced below.

[0144] 11 is a schematic block diagram of a communication device provided in this application. As shown in FIG11 , the communication device 1000 includes a processing unit 1100 , a receiving unit 1200 , and a sending unit 1300 .

[0145] Optionally, the communication device 1000 may correspond to the terminal device in the embodiment of the present application.

[0146] At this time, each unit of the communication device 1000 is used to implement the following functions:

[0147] The sending unit 1300 is configured to:

[0148] Sending a buffer status report to a network device, wherein the buffer status report is used to indicate the amount of uplink data to be sent by the communication device;

[0149] and, sending compression information of the uplink data to be sent to the network device, where the compression information indicates a compression parameter related to physical layer processing of the uplink data to be sent, where the physical layer processing includes performing a first encoding on a transport block (TB), where the first encoding is a coding mode in which compression and channel coding are separated, or where the physical layer processing includes performing a second encoding on each of a plurality of sub-TBs obtained according to the TB, where the second encoding is a coding mode in which compression and channel coding are combined;

[0150] The receiving unit 1200 is used to receive resource scheduling information from the network device, where the resource scheduling information is used to indicate the air interface resources allocated by the network device for the uplink data to be sent, and the air interface resources are determined based on the data volume of the uplink data to be sent and the compression parameters.

[0151] Optionally, in one embodiment, the sending unit 1300 is further configured to:

[0152] First uplink data is sent on the air interface resource, where the first uplink data is obtained by the physical layer of the communication device performing the first encoding on the first transmission block TB, or the first uplink data is obtained by the physical layer of the communication device performing the second encoding on multiple sub-TBs obtained according to the first TB, and the first TB is obtained by packetizing the uplink data to be sent according to the compression parameter.

[0153] Optionally, in one embodiment, the compression parameter is a compression ratio, and the compression ratio is a ratio of an estimated compressed length of the uplink data to be sent to a length before compression; or,

[0154] The compression parameter is the estimated compressed length of the uplink data to be sent.

[0155] Optionally, in one embodiment, the resource scheduling information includes resource indication information and modulation and coding strategy (MCS) information, and the processing unit 1100 is configured to:

[0156] Determining a packet length according to the resource indication information and the MCS information;

[0157] Packetizing the uplink data to be sent according to the packetization length and the compression parameter to obtain the first TB, wherein an estimated compressed length of the uplink data to be sent contained in the first TB is less than or equal to the packetization length;

[0158] Perform the physical layer processing on the first TB to obtain the first uplink data.

[0159] Optionally, in one embodiment, the uplink data to be sent is native data of a physical layer, and the buffer status report is a first type of buffer status report, where the first type of buffer status report is used to indicate a data volume of the native data to be sent;

[0160] The first type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field, the LCG ID field has multiple different values, and the multiple different values ​​correspond to different native data types respectively. 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.

[0161] Optionally, in one embodiment, the first type of buffer status report includes a compression information field, and the compression information field carries the compression information of the to-be-sent data of the native data type corresponding to the LCG ID field.

[0162] Optionally, in one embodiment, the uplink data to be sent is native data of a physical layer, and the buffer status report is a second type of buffer status report, where the second type of buffer status report is used to indicate a data volume of the native data to be sent;

[0163] The second type of buffer status report is obtained by extending 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 a buffer status field, wherein:

[0164] The LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, p of the y values ​​correspond to different native data types, and q of the y values ​​correspond to different logical channel types. When the LCG ID field is the first of the y values, 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, y=2 x ,x,y,p and q are all integers;

[0165] or,

[0166] The LCG ID field includes z bits, k bits among the z bits satisfy a bit mapping relationship with k native data types, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. Each of the z bits 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; 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. If w bits among the z bits are the second value, there are w buffer status fields, and the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, z=k+r, 1≤j≤z, 1≤w≤z, and z, k, r, j and w are all positive integers.

[0167] Optionally, in one embodiment, if the buffer status field is one, the second type of buffer status report further includes a compression information field, and when the x bits are a first value among the y values, the compression information field carries the compression information of the to-be-sent data of the native data type or logical channel type corresponding to the first value;

[0168] If there are w buffer status fields, the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the compressed information of the data to be sent of the native data type or logical channel type corresponding to each of the w bits.

[0169] Optionally, the communication device 1000 may correspond to the network device in the embodiment of the present application.

[0170] At this time, each unit of the communication device 1000 is used to implement the following functions:

[0171] The receiving unit 1200 is configured to:

[0172] receiving a buffer status report from a terminal device, the buffer status report being used to indicate an amount of uplink data to be sent by the terminal device;

[0173] and receiving compression information of the uplink data to be sent from the terminal device, the compression information indicating a compression parameter related to physical layer processing of the uplink data to be sent, the physical layer processing including performing a first encoding on a transport block TB, the first encoding being a coding mode in which compression and channel coding are separated, or the physical layer processing including performing a second encoding on each of a plurality of sub-TBs obtained according to the TB, the second encoding being a coding mode in which compression and channel coding are combined;

[0174] The sending unit 1300 is used to send resource scheduling information to the terminal device, where the resource scheduling information is used to indicate the air interface resources allocated by the communication device for the uplink data to be sent, and the air interface resources are determined based on the data volume of the uplink data to be sent and the compression parameters.

[0175] Optionally, in one embodiment, the sending unit 1300 is further configured to:

[0176] The first uplink data is received from the terminal device on the air interface resource, where the first uplink data is obtained by the physical layer of the terminal device performing the first encoding on the first transmission block TB, 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, and the first TB is obtained by packetizing the uplink data to be sent according to the compression parameter.

[0177] Optionally, in one embodiment, the compression parameter is a compression ratio, and the compression ratio is a ratio of an estimated compressed length of the uplink data to be sent to a length before compression; or,

[0178] The compression parameter is the estimated compressed length of the uplink data to be sent.

[0179] Optionally, in one embodiment, the resource scheduling information includes resource indication information and modulation and coding strategy (MCS) information.

[0180] Optionally, in one embodiment, the uplink data to be sent is native data of a physical layer, and the buffer status report is a first type of buffer status report, where the first type of buffer status report is used to indicate a data volume of the native data to be sent;

[0181] The first type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field. The LCG ID field has multiple different values, and the multiple different values ​​correspond to different native data types respectively.

[0182] Optionally, in one embodiment, the first type of buffer status report includes a compression information field, and the compression information field carries the compression information of the to-be-sent data of the native data type corresponding to the LCG ID field.

[0183] Optionally, in one embodiment, the uplink data to be sent is native data of a physical layer, and the buffer status report is a second type of buffer status report, where the second type of buffer status report is used to indicate a data volume of the native data to be sent;

[0184] The second type of buffer status report is obtained by extending 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 a buffer status field, wherein:

[0185] The LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, p of the y values ​​correspond to different native data types, and q of the y values ​​correspond to different logical channel types. When the LCG ID field is the first of the y values, 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, y=2 x , x, y, p and q are all integers;

[0186] or,

[0187] The LCG ID field includes z bits, k bits among the z bits satisfy a bit mapping relationship with k native data types, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. Each of the z bits 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; 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. If w bits among the z bits are the second value, there are w buffer status fields, and the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, z=k+r, 1≤j≤z, 1≤w≤z, and z, k, r, j and w are all positive integers.

[0188] Optionally, in one embodiment, if the buffer status field is one, the second type of buffer status report further includes a compression information field, and when the x bits are a first value among the y values, the compression information field carries the compression information of the to-be-sent data of the native data type or logical channel type corresponding to the first value;

[0189] If there are w buffer status fields, the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the compressed information of the data to be sent of the native data type or logical channel type corresponding to each of the w bits.

[0190] In the above implementations, the receiving unit 1200 and the sending unit 1300 may also be integrated into a transceiver unit or an input / output unit, which has both receiving and sending functions, and is not limited here.

[0191] In various embodiments of the communication apparatus 1000 corresponding to a terminal device, the processing unit 1100 is configured to perform processing and / or operations implemented within the terminal device in addition to the sending and receiving operations. The receiving unit 1200 is configured to perform the receiving operation of the terminal device, and the sending unit 1300 is configured to perform the sending operation of the terminal device.

[0192] For example, in Figure 6, the sending unit 1300 performs the sending actions in steps 610 and 620, and the receiving unit 1200 performs the receiving action in step 630. Furthermore, the processing unit 1100 performs the following processing in each method embodiment: determining the packet length based on the resource indication and the MCS indication; performing packetization based on the packet length and compression information to obtain the first TB, etc.

[0193] In various embodiments where the communication apparatus 1000 corresponds to a network device, the processing unit 1100 is configured to execute processing and / or operations implemented within the network device in addition to the sending and receiving operations. The receiving unit 1200 is configured to execute the receiving operation of the network device, and the sending unit 1300 is configured to execute the sending operation of the network device.

[0194] For example, in Figure 6, the receiving unit 1200 performs the receiving actions in steps 610 and 620. Optionally, the receiving unit 1200 performs the receiving action in step 640. The sending unit 1300 performs the sending action in step 630. In addition, the processing unit 1100 performs the following processing in each method embodiment: determining the air interface resources to be scheduled based on the data volume and compression information of the uplink data to be sent by the terminal device in the received buffer status report.

[0195] See Figure 12, which is a schematic diagram of the communication device provided in this application. As shown in Figure 12, 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, and the memory 12 is used to store a computer program. The processor 11 is used to call and execute the computer program from the memory 12 to enable the communication device 10 to perform the processing performed by the terminal device or network device in the various method embodiments of this application.

[0196] For example, the processor 11 may have the functionality of the processing unit 1100 shown in FIG11 , and the communication interface 13 may have the functionality of the receiving unit 1200 and / or the sending unit 1300. Specifically, the processor 11 may be configured to execute processing or operations performed internally by the communication device, and the communication interface 13 may be configured to execute sending and / or receiving operations of the communication device.

[0197] In one implementation, the communication device 10 may be the terminal device in the method embodiment. In this implementation, the communication interface 13 may be a transceiver of the terminal device. A transceiver may include a receiver and / or a transmitter. Alternatively, the processor 11 may be a baseband device of the terminal device, and the communication interface 13 may be a radio frequency device.

[0198] In another implementation, the communication device 10 may be a chip (or chip system) installed in a terminal device. In this implementation, the communication interface 13 may be an interface circuit or an input / output interface.

[0199] In one implementation, the communication device 10 may be the network device described in the method embodiment. In this implementation, the communication interface 13 may be a transceiver of the network device. A transceiver may include a receiver and / or a transmitter. Alternatively, the processor 11 may be a baseband device of the network device, and the communication interface 13 may be a radio frequency device.

[0200] In another implementation, the communication device 10 may be a chip (or chip system) installed in a network device. In this implementation, the communication interface 13 may be an interface circuit or an input / output interface.

[0201] In FIG12 , the dotted box behind a device (eg, a processor, a memory, or a communication interface) indicates that there may be more than one device.

[0202] Optionally, the memory and processor in the above-mentioned device embodiments may be physically independent units, or the memory and the processor may be integrated together, which is not limited herein.

[0203] In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are run on a computer, the operations and / or processing performed by the terminal device in each method embodiment of the present application are executed.

[0204] The present application also provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the operations and / or processing performed by the network device in each method embodiment of the present application are executed.

[0205] In addition, the present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processing performed by the terminal device in the various method embodiments of the present application are executed.

[0206] The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processing performed by the network device in the various method embodiments of the present application are executed.

[0207] In addition, the present application also provides a chip, which includes a processor, a memory for storing computer programs is set independently of the chip, and the processor is used to execute the computer program stored in the memory, so that the device equipped with the chip performs the operations and / or processing performed by the terminal device in any method embodiment.

[0208] Furthermore, the chip may further include a communication interface. The communication interface may be an input / output interface, or an interface circuit, etc. Furthermore, the chip may further include the memory.

[0209] The present application also provides a chip, which includes a processor, a memory for storing computer programs set independently of the chip, and the processor is used to execute the computer program stored in the memory, so that a device equipped with the chip performs the operations and / or processing performed by the network device in any method embodiment.

[0210] Furthermore, the chip may further include a communication interface. The communication interface may be an input / output interface, or an interface circuit, etc. Furthermore, the chip may further include the memory.

[0211] Optionally, the processor may be one or more, the memory may be one or more, or the memory may be one or more.

[0212] In addition, the present application also provides a communication device (for example, a chip or a chip system), including a processor and a communication interface, wherein according to the operation and / or processing performed by the terminal device in any of the aforementioned method embodiments, the communication interface is used to receive data and / or information to be processed, and the processor processes the data and / or information. Optionally, the communication interface is also used to send (or output) the data and / or information processed by the processor.

[0213] The present application also provides a communication device (for example, a chip or a chip system), including a processor and a communication interface. According to the operations and / or processing performed by the network device in any of the aforementioned method embodiments, the communication interface 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.

[0214] In addition, the present application also provides a communication device, comprising at least one processor, wherein 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 instruction stored in the at least one memory, so that the communication device performs the operations and / or processing performed by the terminal device in any one method embodiment.

[0215] The present application also provides a communication device, comprising at least one processor, wherein 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 instruction stored in the at least one memory, so that the communication device performs the operations and / or processing performed by the network device in any one of the method embodiments.

[0216] In addition, the present application also provides a wireless communication system, including the terminal device and network device in the method embodiment of the present application.

[0217] It should be noted that "and / or" describes the association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The number of A is not limited and can be one or more. The number of B is also not limited and can be one or more.

[0218] Furthermore, in the above embodiments, the terms "first," "second," and so on are merely used to distinguish different objects and should not constitute any limitation on this application. For example, different buffer status reports, different values, and so on are used to distinguish each other. Furthermore, it should be understood that "first" and "second" do not necessarily indicate that the objects described are different. For example, the terms "first value" and "second value" merely distinguish and describe two values; the first value and the second value may be the same or different, without limitation.

[0219] The processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0220] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DRRAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0222] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0223] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0225] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0226] If 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. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, 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 and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0227] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for scheduling resources, characterized in that: include: The terminal device sends a buffer status report to the network device, where the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device; The terminal device sends compression information of the uplink data to be sent to the network device, where the compression information indicates a compression parameter related to physical layer processing of the uplink data to be sent, where the physical layer processing includes performing a first encoding on a transport block TB, where the first encoding is a coding mode in which compression and channel coding are separated, or the physical layer processing includes performing a second encoding on each of a plurality of sub-TBs obtained according to the TB, where the second encoding is a coding mode in which compression and channel coding are combined; The terminal device receives resource scheduling information from the network device, where the resource scheduling information is used to indicate the air interface resources allocated by the network device for the uplink data to be sent, and the air interface resources are determined based on the data volume of the uplink data to be sent and the compression parameters.

2. The method according to claim 1, wherein The method further comprises: The terminal device sends first uplink data on the air interface resource, and the first uplink data is obtained by the physical layer of the terminal device performing the first encoding on the first transmission block TB, 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, and the first TB is obtained by packetizing the uplink data to be sent according to the compression parameter.

3. The method according to claim 1 or 2, wherein: The compression parameter is a compression ratio, which is a ratio of an estimated length of the uplink data to be sent after compression to an estimated length before compression; or The compression parameter is the estimated compressed length of the uplink data to be sent.

4. The method according to claim 2 or 3, wherein: The resource scheduling information includes resource indication information and modulation and coding strategy (MCS) information, and the method further includes: The terminal device determines the packet length according to the resource indication information and the MCS information; The terminal device performs data packetization on the uplink data to be sent according to the packetization length and the compression parameter to obtain the first TB, wherein the estimated compressed length of the uplink data to be sent contained in the first TB is less than or equal to the packetization length; The terminal device performs the physical layer processing on the first TB to obtain the first uplink data.

5. The method according to any one of claims 1 to 4, characterized in that The uplink data to be sent is native data of the physical layer, and the buffer status report is a first type of buffer status report, where the first type of buffer status report is used to indicate a data amount of the native data to be sent; The first type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field, the LCG ID field has multiple different values, and the multiple different values ​​correspond to different native data types respectively. 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.

6. The method according to claim 5, wherein The first type of buffer status report includes a compression information field, where the compression information field carries the compression information of the to-be-sent data of the native data type corresponding to the LCG ID field.

7. The method according to any one of claims 1 to 4, characterized in that The uplink data to be sent is native data of the physical layer, and the buffer status report is a second type of buffer status report, where the second type of buffer status report is used to indicate a data amount of the native data to be sent; The second type of buffer status report is obtained by extending 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 a buffer status field, wherein: The LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, p of the y values ​​correspond to different native data types, and q of the y different values ​​correspond to different logical channel types. When the LCG ID field is the first of the y values, 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, y=2 x ,x,y,p and q are all integers; or, The LCG ID field includes z bits, k bits among the z bits satisfy a bit mapping relationship with k native data types, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. Each of the z bits 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; 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. If w bits among the z bits are the second value, there are w buffer status fields, and the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, z=k+r, 1≤j≤z, 1≤w≤z, and z, k, r, j and w are all positive integers.

8. The method according to claim 7, wherein If there is one buffer status field, the second type of buffer status report further includes a compression information field, and when the x bits are a first value among the y values, the compression information field carries the compression information of the to-be-sent data of the native data type or logical channel type corresponding to the first value; If there are w buffer status fields, the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the compressed information of the data to be sent of the native data type or logical channel type corresponding to each of the w bits.

9. A method for scheduling resources, characterized in that: include: The network device receives a buffer status report from the terminal device, where the buffer status report is used to indicate the amount of uplink data to be sent by the terminal device; The network device receives, from the terminal device, compression information of the uplink data to be sent, the compression information indicating a compression parameter related to physical layer processing of the uplink data to be sent, the physical layer processing including performing a first encoding on a transport block (TB), the first encoding being a coding mode in which compression and channel coding are separated, or the physical layer processing including performing a second encoding on each of a plurality of sub-TBs obtained according to the TB, the second encoding being a coding mode in which compression and channel coding are combined; The network device sends resource scheduling information to the terminal device, where the resource scheduling information is used to indicate the air interface resources allocated by the network device for the uplink data to be sent, and the air interface resources are determined based on the data volume of the uplink data to be sent and the compression parameters.

10. The method according to claim 9, wherein The method further comprises: The network device receives the first uplink data from the terminal device on the air interface resource, where the first uplink data is obtained by the physical layer of the terminal device performing the first encoding on the first transmission block TB, or the first uplink data is obtained by the physical layer of the terminal device performing the second encoding on multiple sub-TBs obtained based on the first TB, where the first TB is obtained by packetizing the uplink data to be sent according to the compression parameter.

11. The method according to claim 9 or 10, wherein: The compression parameter is a compression ratio, which is a ratio of an estimated length of the uplink data to be sent after compression to an estimated length before compression; or The compression parameter is the estimated compressed length of the uplink data to be sent.

12. The method according to any one of claims 9 to 11, characterized in that The resource scheduling information includes resource indication information and modulation and coding strategy (MCS) information.

13. The method according to any one of claims 9 to 11, characterized in that The uplink data to be sent is native data of the physical layer, and the buffer status report is a first type of buffer status report, where the first type of buffer status report is used to indicate a data amount of the native data to be sent; The first type of buffer status report includes a logical channel group identifier LCG ID field and a buffer status field, the LCG ID field has multiple different values, and the multiple different values ​​correspond to different native data types respectively. 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.

14. The method according to claim 13, wherein The first type of buffer status report includes a compression information field, where the compression information field carries the compression information of the to-be-sent data of the native data type corresponding to the LCG ID field.

15. The method according to any one of claims 9 to 11, characterized in that The uplink data to be sent is native data of the physical layer, and the buffer status report is a second type of buffer status report, where the second type of buffer status report is used to indicate a data amount of the native data to be sent; The second type of buffer status report is obtained by extending 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 a buffer status field, wherein: The LCG ID field includes x bits, the buffer status field is one, the x bits have y different values, p of the y values ​​correspond to different native data types, and q of the y values ​​correspond to different logical channel types. When the LCG ID field is the first of the y values, 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, y=2 x , x, y, p and q are all integers; or, The LCG ID field includes z bits, k bits among the z bits satisfy a bit mapping relationship with k native data types, and r bits among the z bits satisfy a bit mapping relationship with r logical channel types. Each of the z bits 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; 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. If w bits among the z bits are the second value, there are w buffer status fields, and the w buffer status fields are respectively used to indicate the amount of data to be sent of the native data type and / or logical channel type corresponding to the w bits, z=k+r, 1≤j≤z, 1≤w≤z, and z, k, r, j and w are all positive integers.

16. The method according to claim 15, wherein If there is one buffer status field, the second type of buffer status report further includes a compression information field, and when the x bits are a first value among the y values, the compression information field carries the compression information of the to-be-sent data of the native data type or logical channel type corresponding to the first value; If there are w buffer status fields, the second type of buffer status report also includes w compressed information fields, and the w compressed information fields respectively carry the compressed information of the data to be sent of the native data type or logical channel type corresponding to each of the w bits.

17. A communication device, characterized in that: The communication device comprises at least one processor coupled to at least one memory, wherein the at least one processor is configured to execute a computer program or instruction stored in the at least one memory, so as to enable the communication device to perform the method according to any one of claims 1 to 8, or the method according to any one of claims 9 to 16.

18. A chip, characterized in that: The method comprises a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information to execute the method according to any one of claims 1 to 8, or the method according to any one of claims 9 to 16.

19. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, which, when executed on a computer, enable the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 16 to be implemented.

20. A computer program product, characterized in that The computer program product comprises a computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 16 is implemented.

Images