Systems, methods, and non-transitory computer readable media for transmission mode switching
By introducing transformed precoding configuration and dynamic switching technology in wireless communication systems, the coverage problem caused by high frequency bands in traditional systems is solved, and wider coverage and higher network capabilities are achieved.
Patent Information
- Application Number
- CN202280095006.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-02
- Publication Date
- 2024-11-29
AI Technical Summary
In traditional wireless communication systems, high frequency bands lead to large propagation losses, resulting in small cell coverage radius, and the uplink waveform configuration is semi-static and cannot be switched dynamically, affecting the service quality of edge users.
By introducing a transformed precoding configuration in the wireless communication system, it supports dynamic switching between DFT-s-OFDM and CP-OFDM waveforms, and uses RRC signaling configuration and DCI format to indicate transformed precoding to realize dynamics of uplink transmission parameters. Switch to adapt to coverage needs.
It improves the coverage range and network capabilities of wireless communication systems, enhances the service quality of edge users, and flexibly matches coverage and capability requirements.
Smart Images

Figure CN119054401A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems, methods, and non-transitory computer-readable media for transmission mode switching. Background Art
[0002] Although wireless communication services cover more and more applications, traditional wireless communication services do not match the communication frequency band. For some systems, the frequency band is relatively high relative to the service, resulting in greater propagation loss. At the same power, the cell coverage radius is smaller. Summary of the invention
[0003] The example embodiments disclosed herein are intended to solve problems related to one or more of the problems presented in the prior art, and to provide additional features, which will become apparent when combined with the following figures and by reference to the following detailed description. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it will be understood that these embodiments are presented only as examples and are not restrictive, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure.
[0004] Some deployments of the present disclosure relate to systems, apparatuses, methods, and non-transitory computer-readable media for indicating a transform precoding configuration, including: receiving at least one of a first indication or a second indication from a network (e.g., a base station (BS)) by a user equipment (UE). At least one of the first indication and the second indication indicates a transmission parameter for uplink transmission. The second indication is used to indicate a relationship between the transmission parameter and the first indication, and the transmission parameter includes the transform precoding configuration. The UE sends an uplink transmission to the network using the transmission parameter indicated by at least one of the first indication or the second indication.
[0005] Some deployments of the present disclosure relate to systems, apparatuses, methods, and non-transitory computer-readable media for indicating a transform precoding configuration, including: a network sends at least one of a first indication or a second indication to a UE, at least one of the first indication or the second indication indicating a transmission parameter for an uplink transmission. The second indication is used to indicate a relationship between the transmission parameter and the first indication, and the transmission parameter includes the transform precoding configuration. The network receives an uplink transmission from the UE using the transmission parameter indicated by at least one of the first indication or the second indication.
[0006] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Various example implementations of the present solution are described in detail below with reference to the following figures or drawings. These drawings are provided for illustrative purposes only and depict only example implementations of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0008] Figure 1 An example cellular communication network is shown in accordance with some deployments.
[0009] Figure 2 Block diagrams of example base stations and example user equipment are shown in accordance with some deployments.
[0010] Figure 3 is a table showing an example relationship between Radio Resource Control (RRC) parameters or fields and the applicable Physical Uplink Shared Channel (PUSCH) according to some deployments.
[0011] Figure 4 is a flow chart illustrating an example method for indicating a transform precoding configuration according to various deployments.
[0012] Figure 5 is a diagram illustrating time domain restrictions for dynamic switching of uplink transmission parameters (eg, transform precoding configurations) according to various deployments.
[0013] Figure 6 is a diagram illustrating time domain restrictions for dynamic switching of uplink transmission parameters (eg, transform precoding configurations) according to various deployments. DETAILED DESCRIPTION
[0014] Various example implementations of the present solution are described below with reference to the accompanying drawings to enable those of ordinary skill in the art to make and use the present solution. As will be apparent to those of ordinary skill in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example implementations and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be redeployed while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.
[0015] Mobile communication systems can be systematically networked on carrier frequencies higher than those used in 2G, 3G, and 4G systems. Some systems utilize frequency bands such as 3 GHz to 6 GHz and 6 GHz to 100 GHz. In these systems, the frequency bands are relatively high relative to the services, resulting in large propagation losses. At the same power, the cell coverage radius is relatively small. In order to achieve a wider range of communication systems (including but not limited to 2G, 3G, and 4G), some deployments in this article involve enhancing coverage of uplink channels (such as physical uplink shared channels (PUSCH), and physical uplink control channels (Physical Uplink Control Channel, PUCCH), etc.).
[0016] In some embodiments, two waveforms are supported in the uplink, Discrete Fourier Transform (DFT) spread Orthogonal Frequency Division Multiplexing (OFDM) (DFT spread OFDM, DFT-s-OFDM) and Cyclic Prefix (CP) OFDM (CP-OFDM). DFT-s-OFDM supports single-layer transmission, while CP-OFDM supports multi-layer uplink transmission. When the UE is at the edge of the cell, the DFT-s-OFDM waveform provides high-quality coverage due to power efficiency. However, the network semi-statically configures the waveform for uplink transmission, which means that if the DFT-s-OFDM waveform is configured, a UE that supports multiple transmit antennas only supports single-layer transmission. Therefore, the network configures the CP-OFDM waveform for uplink transmission to utilize uplink multiple input multiple output (MIMO) transmission. Currently, the waveform used in the uplink is configured via Radio Resource Control (RRC) signaling and cannot be switched dynamically, which makes it difficult for cell-edge UEs to switch to the DFT-s-OFDM waveform. Some deployments involve implementing dynamic switching between different waveforms for uplink transmissions.
[0017] Figure 1 An example wireless communication network and / or system 100 is shown in which the techniques disclosed herein may be implemented in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a NarrowBand Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes a BS 102 and a UE 104 that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. In Figure 1 1, BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating on its allocated bandwidth to provide adequate wireless coverage to its intended users.
[0018] For example, BS 102 may operate on an allocated channel transmission bandwidth to provide adequate coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may also be divided into subframes 120 / 127, which may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as "communication nodes" that may generally practice non-limiting examples of the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communications.
[0019] Figure 2 A block diagram of an example wireless communication system 200 for sending and receiving wireless communication signals (e.g., OFDM (Orthogonal Frequency Division Multiplexing) / OFDMA (Orthogonal Frequency Division Multiple Access) signals) according to some embodiments of the present solution is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, the system 200 may be used in a wireless communication environment (such as, for example, a wireless communication environment such as described above). Figure 1 Communicate (eg, send and receive) data symbols in a wireless communication environment 100).
[0020] The system 200 generally includes a BS 202 and a UE 204. The BS 202 includes a base station (BS) transceiver module 210 (hereinafter also referred to as: BS transceiver 210, transceiver 210), a BS antenna 212 (hereinafter also referred to as: antenna 212 or downlink antenna 212), a BS processor module 214 (hereinafter also referred to as: processor module 214), a BS memory module 216 (hereinafter also referred to as: memory module 216), and a network communication module 218, each module coupled and interconnected to each other via a data communication bus 220 as needed. The UE 204 includes a UE (user equipment) transceiver module 230 (also referred to as UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as: antenna 232 or uplink antenna 232), a UE memory module 234 (hereinafter also referred to as: memory module 234), and a UE processor module 236 (hereinafter also referred to as: processor module 236), each module coupled and interconnected to each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via communication channel 250 , which may be any wireless channel or other medium suitable for data transmission as described herein.
[0021] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2 . It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether this function is implemented as hardware, firmware, or software may depend on the specific application and the design constraints imposed on the entire system. Personnel familiar with the concept described herein can implement this function in an appropriate manner for each specific application, but this implementation decision should not be interpreted as limiting the scope of the present disclosure.
[0022] According to some embodiments, the UE transceiver 230 may be referred to herein as an uplink transceiver 230 including a Radio Frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time division duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time so that the uplink receiver circuit is coupled to the uplink antenna 232 so as to receive transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. In some embodiments, there is tight time synchronization with a minimum guard time between changes in both duplex directions.
[0023] The UE transceiver 230 and the BS transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna deployment 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the BS transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and related protocols. Instead, the UE transceiver 230 and the BS transceiver 210 can be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).
[0024] According to various embodiments, BS202 can be, for example, an evolved node B (eNB), a serving eNB, a target eNB, a femtocell or a microcell. In some embodiments, UE 204 can be various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 214 and 236 can be implemented or realized using a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or a combination of any other such configurations.
[0025] Further, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly in hardware, in firmware, in software modules executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to 210 and 230, respectively, so that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.
[0026] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the BS 202, which implement bidirectional communication between the BS transceiver 210 and other network components and communication nodes configured to communicate with the BS 202. For example, the network communication module 218 can be configured to support the Internet or WiMAX (World Interoperability for Microwave Access) business. In a typical deployment, but without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the BS transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured to", "configured to" and various variations thereof used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted and / or deployed to perform a specified operation or function.
[0027] Some deployments described herein involve configuring or indicating dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) for uplink transmission (e.g., PUSCH) scheduled by a Random Access Response (RAR) uplink (UL) grant or a downlink control information (DCI) format 0-0 with a cyclic redundancy check (CRC) scrambled by a Temporary Cell Radio Network Temporary Identifier (TC-RNTI). In addition, time domain requirements associated with PUSCH using different transmission parameters (e.g., transform precoding configuration) may be defined. Thus, dynamic switching and selection of uplink transmission parameters (e.g., transform precoding configuration) may be supported to flexibly match coverage enhancement requirements and improve network capabilities.
[0028] In some examples, the codeword of CP-OFDM has two inputs, while the codeword of DFT-s-OFDM has one input.Regarding whether transform precoding is performed before precoding, there is transform precoding under DFT-s-OFDM, while no transform precoding is used in conjunction with CP-OFDM.
[0029] In some examples, given that CP-OFDM does not utilize transform precoding, in response to the UE receiving RRC signaling including an indication corresponding to transform precoding being set to disabled (e.g., RRC parameter transformPrecoder is set to disabled), the UE transmits PUSCH transmission to the network (e.g., BS) using CP-OFDM. On the other hand, in response to the UE receiving RRC signaling including an indication corresponding to transform precoding being set to enabled (e.g., RRC parameter transformPrecoder is set to enabled), the UE transmits PUSCH transmission to the network (e.g., BS) using DFT-s-OFDM.
[0030] Figure 3300 is a table showing an example relationship between RRC parameters or fields and applicable PUSCH according to some deployments. As shown in Table 300, the network may (e.g., by the BS) configure four RRC parameters, each corresponding to a transform precoding, to indicate transmission parameters (e.g., transform precoding configuration) for different types of PUSCH. For example, the parameter msg3-transformPrecoder applies to 1) PUSCH scheduled by a random access response (RAR) UL grant, or PUSCH scheduled by a fallback RAR UL grant, or PUSCH scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI; 2) if msgA-TransformPrecoder is not configured, it is MsgAPUSCH; 3) PUSCH transmission scheduled by the following items: DCI format 0-0 with a CRC scrambled by CS-RNTI with New Data Indicator (NDI) = 1, DCI format 0-0 with a CRC scrambled by C-RNTI, or DCI format 0-0 with a CRC scrambled by Modulation Coding Scheme Cell RNTI (MCS-C-RNTI) or DCI format 0-0 with a CRC scrambled by semi-persistent channel state information (Channel State Information). 1) DCI format 0-0 with CRC scrambled by Semi-Persistent Channel State Information RNTI (SP-CSI-RNTI); or 4) if transformPrecoder in configuredGrantConfig is not configured, it is a configured granted PUSCH transmission. The parameter msgA-TransformPrecoder applies to MsgA PUSCH. The parameter transformPrecoder in pusch-Config applies to PUSCH transmissions scheduled by the following DCI formats except DCI formats 0-0, and DCI formats with CRC scrambled by CS-RNTI, DCI formats with CRC scrambled by C-RNTI, or DCI formats with CRC scrambled by MCS-C-RNTI, or DCI formats with CRC scrambled by SP-CSI-RNTI with NDI=1. The parameter transformPrecoder in configuredGrantConfig applies to configured granted PUSCH transmissions.
[0031] Figure 4is a flow chart illustrating an example method 400 for performing transmission parameter (eg, changing precoding configuration) switching according to various deployments. Figures 1 to 4 , the method 400 may be performed by a network and a UE 104 / 204. As used herein, a network refers to a network entity other than a UE 104 / 204 (eg, a BS 102 / 202).
[0032] In some deployments, the network (e.g., BS) sends a first indication to the UE, the first indication being used to indicate transmission parameters (e.g., transform precoding configuration or transmission waveform configuration) for sending uplink transmission. The UE receives the first indication from the network, the first indication being used to indicate transmission parameters (e.g., transform precoding configuration or transmission waveform configuration) for sending uplink transmission. In some examples, the waveform includes one of: a waveform supporting single-layer transmission (e.g., DFT-s-OFDM) or a waveform supporting multi-layer transmission (e.g., CP-OFDM). In some deployments, the UE sends an uplink transmission to the network using the transmission parameters in response to receiving the first indication. In response to the first indication, the network receives the uplink transmission using the transmission parameters.
[0033] In some deployments, the network (e.g., BS) indicates to the UE or configures the UE for dynamic switching of uplink transmission parameters (e.g., transform precoding configuration). In some examples, the network may use RRC signaling to indicate or configure the dynamic switching of uplink transmission parameters (e.g., transform precoding configuration). For example, the network sends a second indication and the UE receives the second indication, the second indication being used to indicate the dynamic switching of the transmission parameter (e.g., transform precoding configuration).
[0034] In some examples, a parameter or field (e.g., msg3-transformPrecoder) for an indication of transform precoding includes three states. Specifically, a new value is provided that indicates whether transform precoding is enabled depending on a dynamic indication. Therefore, the transform precoding indication includes three values corresponding to three states, which include: enabling transform precoding, disabling transform precoding, and transform precoding configuration depending on a dynamic indication. Another parameter or field (e.g., msgA-TransformPrecoder, transformPrecoder in pusch-Config, and transformPrecoder in configuredGrantConfig) for another type of transform precoding indication may similarly include a value corresponding to a state, where the transform precoding configuration depends on a dynamic indication (e.g., a first indication). Therefore, the second indication is RRC signaling. The second indication is set to one of the following: a first value indicating enabling transform precoding, a second value indicating disabling transform precoding, or a third value indicating enabling or disabling transform precoding based on the first indication.
[0035] In some examples, in an example where there is no second indication (e.g., corresponding to enabling transform precoding based on the first indication / dynamic switching), any of the states of enabling transform precoding or disabling transform precoding can be defined as a default state. For example, if there is no parameter or field corresponding to the transform precoding indication, the UE can determine whether transform precoding is enabled or disabled based on the dynamic indication (e.g., the first indication). Therefore, the transform precoding indication is a parameter in the RRC signaling. If there is no transform precoding indication, transform precoding is enabled or disabled based on the first indication (e.g., the dynamic indication).
[0036] In some examples, a new RRC parameter or field may be defined to have the following structure:
[0037] dynamicTransformPrecoder (dynamic transform precoder) ENUMERATED (enumeration) {true} (1)
[0038] The presence of a new RRC parameter or field indicates that transform precoding is enabled or disabled according to a dynamic indication (e.g., a first indication). The absence of a new RRC parameter or field indicates that the UE determines whether transform precoding is enabled or disabled according to the RRC configuration, for example, via one of msg3-transformPrecoder, msgA-transformPrecoder, and transformPrecoder. Therefore, in some examples, the second indication is RRC signaling. The presence of the second indication indicates that transform precoding is enabled or disabled based on the first indication (e.g., dynamic switching). The absence of the second indication indicates that transform precoding is enabled or disabled based on at least another parameter in the RRC signaling (e.g., any one of the existing RRC signaling, msg3-transformPrecoder, msgA-transformPrecoder, and transformPrecoder).
[0039] In some examples, legacy UEs or UEs that do not support dynamic switching of transform precoding configurations may omit new RRC parameters or fields. The UE may determine the transform precoding configuration or waveform for uplink transmission based on the RRC configuration, for example, via any one of msg3-transformPrecoder, msgA-transformPrecoder, and transformPrecoder.
[0040] In some deployments, the network (e.g., BS) indicates to the UE or configures the UE for dynamic switching of uplink waveform or transform precoding configuration. The network can use the DCI format to provide waveform indication or transform precoding configuration for uplink scheduling. For example, the first indication transmitted in box 410 and box 420 includes a transform precoding indication field of DCI format 0_0. Specifically, DCI format 0-0 includes a 1-bit transform precoding indication field to indicate whether switching is required (e.g., 0 indicates no switching, and 1 indicates switching) or which waveform or transform precoding configuration to use (e.g., 0 indicates that the first waveform is to be used (e.g., enabling transform precoding), and 1 indicates that the second waveform is to be used (e.g., disabling transform precoding)).
[0041] In some deployments, a transform precoding indication field is introduced or exists in DIC format 0_0 in response to determining one or more of the following: 1) the UE has the ability to dynamically switch uplink transmission parameters (for example, between CP-OFDM and DFT-s-OFDM, enabling or disabling transform precoding); 2) the number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding; 3) the number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding by more than 1 bit; or 4) if there is an uplink / supplementary uplink indication field in DCI format 0_0, the number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding by more than 1 bit, and if there is no uplink / supplementary uplink indication field in DCI format 0_0, the number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0.
[0042] In some examples, the transform precoding indication field, if present, is located in the last bit of DCI format 0_0 after the bit(s) of DCI format 0_0 is filled. In some examples, the transform precoding indication field, if present, is located in the second to last bit after the bit(s) of DCI format 0_0 is filled. In some examples, if the uplink / supplementary uplink indication field does not exist in DCI format 0_0, the transform precoding indication field, if present, is located in the last bit of DCI format 0_0 after the bit(s) of DCI format 0_0 is filled. In some examples, if the uplink / supplementary uplink indication field exists in DCI format 0_0, the transform precoding indication field, if present, is located in the second to last bit of DCI format 0_0 after the bit(s) of DCI format 0_0 is filled.
[0043] In some deployments, the first indication includes a transform precoding indication field, and in response to determining that the transmission parameter is indicated by the first indication according to the second indication, the DCI format for scheduling uplink transmission includes a transform precoding indication field. In some examples, if the number of bits of DCI format 1_0 before filling is only 1 bit more than the number of bits of DCI format 0_0 before filling, the extra bit of DCI format 1_0 can be used as an uplink / supplementary uplink indicator. In some deployments, the extra bit of DCI format 1_0 can be used as a transform precoding indication field. In some deployments, the extra bit of DCI format 1_0 can be used as an uplink / supplementary uplink indicator or a transform precoding indicator according to the RRC configuration.
[0044] For example, if the cell has two uplink carriers and the UE does not have the ability to dynamically switch uplink transmission parameters (e.g., transform precoding), the additional bit of DCI format 1_0 is used as an uplink / supplementary uplink indicator. In some examples, if the cell does not have two uplink carriers and the UE has the ability to dynamically switch uplink transmission parameters (e.g., transform precoding), the additional bit of DCI format 1_0 is used as a transform precoding indicator. In some examples, if the UE has the ability to dynamically switch uplink transmission parameters (e.g., transform precoding), the additional bit of DCI format 1_0 is used as a transform precoding indicator. In some examples where the above conditions cannot be met, the network does not provide any uplink transmission parameter dynamic switching indication, or the indication field is 0 bits. Then, the uplink transmission parameters (e.g., transform precoding) can be determined based on the RRC configuration or predefined uplink transmission parameters.
[0045] For DCI format 0_1, if the transform precoding configuration of the uplink transmission is determined depending on a dynamic indication configured by RRC signaling, the size of DCI format 0_1 is determined by assuming that transform precoding is disabled via RRC signaling. In other words, the size of the DCI format including the transform precoding indication field is determined based on the size of the same DCI format when transform precoding is disabled via RRC signaling. In some examples, the size of the DCI format including the transform precoding indication field is the same as the size of the same DCI format when transform precoding is disabled via RRC signaling. In some examples, the size of the DCI format including the transform precoding indication field is 1 bit larger than the size of the same DCI format when transform precoding is disabled via RRC signaling.
[0046] Similarly, for DCI format 0_2, if the transform precoding configuration of the uplink transmission is determined depending on a dynamic indication configured by RRC signaling, the size of DCI format 0_2 is determined by assuming that transform precoding is disabled via RRC signaling. In other words, the UE receives a second indication via RRC, the second indication being used to indicate dynamic switching of the transform precoding configuration, and the size of DCI format 0_2 is determined based on enabling transform precoding via RRC.
[0047] More specifically, in some deployments, the size of each field in DCI format 0_1 / 0_2 is the same regardless of whether the transform precoding configuration for uplink transmission is dynamically determined or transform precoding is disabled via RRC signaling. In other deployments, the total size of DCI format 0_1 / 0_2 is aligned between the case where the transform precoding configuration for uplink transmission is dynamically determined and the case where transform precoding is disabled via RRC signaling. For fields whose size is related to whether transform precoding is enabled or disabled, the size of such fields may be different between the case where the transform precoding configuration for uplink transmission is dynamically determined and the case where transform precoding is disabled via RRC signaling. The size of these fields may be determined based on the transform precoding indication field. If transform precoding is disabled based on the transform precoding indication field, padding bits will be added.
[0048] Some deployments involve configuring or indicating dynamic switching of a transform precoding configuration for a PUSCH scheduled by a random access response (RAR) uplink grant. In some examples where an uplink transmission (e.g., PUSCH) is scheduled by a RAR UL grant (the uplink transmission may also be referred to as msg.3PUSCH), the transform precoding configuration may be dynamically indicated.
[0049] In some deployments, the UE is configured with specific PRACH (Physical Random Access Channel) resources (e.g., RACH (Random Access Channel) timing, preamble index) corresponding to msg.3PUSCH with transform precoding enabled (e.g., with DFT-s-OFDM waveform). When the UE initiates a random access procedure using one of these specific PRACH resources, transform precoding will be enabled for subsequent msg.3PUSCH (e.g., using DFT-s-OFDM waveform).
[0050] On the other hand, the UE is configured with specific PRACH resources (e.g., RACH opportunity, preamble index) corresponding to msg.3PUSCH with disabled transform precoding (e.g., with CP-OFDM waveform). When the UE initiates a random access procedure using one of these specific PRACH resources, transform precoding will be disabled for subsequent msg.3PUSCH (e.g., using CP-OFDM waveform).
[0051] Thus, in some examples, the uplink transmission in method 400 is scheduled by an RAR uplink grant. The second indication includes a configuration of resources for a random access procedure corresponding to a transmission parameter of the uplink transmission. The UE initiates a random access procedure using the resources for the random access procedure. After initiating the random access procedure, an uplink transmission using the transmission parameter is sent.
[0052] In some deployments, a Reference Signal Received Power (RSRP) threshold may be defined. For example, in response to determining that an RSRP measurement result based on a synchronization signal / physical broadcast channel (SS / PBCH Block, SSB) block is lower than an RSRP threshold, the UE may use a PRACH resource corresponding to msg.3PUSCH with transform precoding enabled (e.g., with a DFT-s-OFDM waveform). Otherwise, in response to the UE selecting a PRACH resource other than a specific PRACH resource, a transmission parameter (e.g., whether transform precoding is enabled) may be determined based on an RRC configuration (e.g., msg3-transformPrecoder).
[0053] In some deployments, the UE is configured with specific PRACH resources (e.g., RACH timing, preamble index) corresponding to msg.3 PUSCH repetition or PRACH repetition. When the UE initiates a random access procedure using one of these specific PRACH resources, transform precoding will be enabled for subsequent msg.3 PUSCH (e.g., using DFT-s-OFDM waveform).
[0054] In some deployments, the UE is configured with specific PRACH resources (e.g., RACH timing, preamble index) corresponding to msg.3PUSCH repetitions. When the UE initiates a random access procedure using one of these specific PRACH resources and the base station repeatedly indicates msg.3PUSCH transmissions, transform precoding will be enabled for subsequent msg.3PUSCH (e.g., using DFT-s-OFDM waveform).
[0055] Thus, in some examples, the uplink transmission in method 400 is scheduled by a RAR uplink grant. The second indication includes a configuration of resources for a random access procedure corresponding to at least one repetition of the uplink transmission or at least one repetition of a preamble of the random access procedure. The UE initiates the random access procedure using the resources for the random access procedure. After initiating the random access procedure, an uplink transmission enabling transform precoding is sent.
[0056] Otherwise, in response to the UE selecting a PRACH resource other than a specific PRACH resource, a transmission parameter (e.g., whether transform precoding is enabled) is determined according to an RRC configuration (e.g., msg3-transformPrecoder). Alternatively, after initiating a random access procedure, an uplink transmission with transform precoding disabled is sent.
[0057] In some deployments, the UE is configured with specific PRACH resources (e.g., RACH timing, preamble index) corresponding to the dynamic switching of the transmission parameters of the msg.3PUSCH. When the UE uses one of these specific PRACH resources to initiate a random access procedure, the subsequent msg.3PUSCH is transmitted using the transmission parameters indicated in the RAR uplink grant. Therefore, in some examples, the uplink transmission in method 400 is scheduled by the RAR uplink grant. The second indication includes a configuration of resources for the random access procedure corresponding to enabling or disabling transform precoding for uplink transmission. The random access procedure is initiated using the resources for the random access procedure. The transform precoding configuration of the uplink transmission after the random access procedure is initiated is indicated in the first indication. In some examples, the transform precoding configuration is introduced in the time domain resource allocation (TDRA) table as a column, and the TDRA field in the RAR uplink grant will be used to indicate the time domain resource allocation and transform precoding configuration for msg.3PUSCH transmission. In some embodiments, the N most significant bits (MSB) or the least significant bits (LSB) of a specific field in the RAR UL grant may be used to indicate the transform precoding configuration for msg.3 PUSCH. The specific field may be one of the following: a modulation coding scheme (MCS) field, a TDRA field, or a transmission power control (TPC) field, etc.
[0058] In some deployments where the UE repeatedly transmits PRACH, transform precoding may be enabled (e.g., using a DFT-s-OFDM waveform) for subsequent msg.3PUSCH. Otherwise, if the UE does not repeatedly transmit PRACH, the transform precoding configuration for msg.3PUSCH transmission is determined according to the RRC configuration (e.g., msg3-transformPrecoder). In some deployments, after initiating a random access procedure, an uplink transmission with transform precoding disabled is sent. In some examples, uplink transmissions are scheduled by RAR uplink grants, and if the UE repeatedly transmits a preamble for a random access procedure, transform precoding is enabled for uplink transmissions.
[0059] In some deployments, the transform precoding configuration of the PUSCH scheduled by the RAR UL grant is the same as the transform precoding configuration of the PUSCH scheduled by the latest DCI (e.g., the most recent DCI immediately preceding the RAR UL grant). In some examples, the uplink transmission is scheduled by the RAR uplink grant and uses the same transform precoding configuration as the transform precoding configuration of the uplink transmission scheduled by the most recent DCI.
[0060] In some deployments, the transformed precoding configuration of a PUSCH scheduled by a RAR UL grant or DCI format 0_0 is the same as the transformed precoding configuration of a PUSCH scheduled by the latest DCI with DCI format 0_1 or 0_2.
[0061] In some deployments, the transform precoding configuration of the configuration granting the PUSCH is the same as the transform precoding configuration of the PUSCH scheduled by the latest DCI before the configuration granting the PUSCH. In some examples, the latest DCI has DCI format 0_1 or 0_2. In some examples, the latest DCI can be any one of DCI formats 0_0, 0_1, or 0_2.
[0062] Some deployments involve configuring or indicating dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) for PUSCH scheduled by DCI format 0-0 with CRC scrambled by TC-RNTI (e.g., transform precoding configuration). In some deployments, the transform precoding configuration for PUSCH scheduled by DCI format 0-0 with CRC scrambled by TC-RNTI is the same as the transform precoding configuration for the initial transmission of msg.3PUSCH scheduled by RAR UL grant. In some deployments, the transform precoding configuration for PUSCH scheduled by DCI format 0-0 with CRC scrambled by TC-RNTI follows the transform precoding configuration for PUSCH scheduled by DCI format 0-0 with CRC scrambled by C-RNTI. In some deployments, the transform precoding configuration for PUSCH scheduled by DCI format 0-0 with CRC scrambled by TC-RNTI follows the configuration of msg3-transformPrecoder.
[0063] Figure 5 is a diagram illustrating time domain constraints for dynamic switching of uplink transmission parameters according to various deployments. Figure 5 In the example in which the UE reports its ability to support dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) or the dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) is configured via RRC signaling, a timeline 530 with a longer time period is determined. In the example in which the UE does not support dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) or the dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) is not configured via RRC signaling, a timeline with a shorter time period will be used. The timeline is defined as the time length between the PDCCH 510 carrying the uplink grant and the PUSCH 520. In other words, the UE receives an uplink grant from the network for scheduling uplink transmission. The length of time between the uplink grant and the uplink transmission is determined based on whether the UE supports dynamic switching of the changing precoding configuration.
[0064] In some deployments, two timelines between an uplink grant 510 and a corresponding PUSCH 520 may be defined. If the PUSCH 520 is indicated to use uplink transmission parameters (e.g., transform precoding configuration) that are different from the uplink transmission parameters of the latest PUSCH (not shown) (which is the PUSCH immediately before the PUSCH 520), the timeline with a longer time length is adopted. Otherwise, if the PUSCH 520 is indicated to use uplink transmission parameters (e.g., transform precoding configuration) that are the same as the uplink transmission parameters of the latest PUSCH, the other timeline with a shorter time length is adopted. In other words, the UE receives an uplink grant from the network for scheduling uplink transmission. The time length between the uplink grant and the uplink transmission is determined based on whether the uplink grant indicates the use of the same transform precoding configuration as the transform precoding configuration of the latest uplink transmission.
[0065] Figure 6 is a diagram illustrating time domain constraints for dynamic switching of uplink transmission parameters (eg, transform precoding configurations) according to various deployments. Figure 6 , the vertical dimension represents the frequency domain, and the horizontal dimension represents the time domain. The time-frequency resources 600 are shown as blocks, each of which may correspond to a time slot. An uplink grant for a PUSCH 620 is received in a PDCCH 610. An uplink grant for a PUSCH 625 is received in a PDCCH 615. In some deployments, if two PUSCHs 620 and 625 are indicated to correspond to different transmission parameters (e.g., transform precoding configurations), a time domain gap 630 of N symbols between the PUSCH 620 and the PUSCH 625 is required. In other words, if two PUSCHs 620 and 625 with different transmission parameters (e.g., transform precoding configurations) are scheduled for the UE, the UE does not expect the gap 630 between the two PUSCHs 620 and 625 to be less than a predefined threshold, where the predefined threshold is N symbols. That is, the UE receives a first uplink grant from the network for scheduling a first uplink transmission. The UE receives a second uplink grant from the network for scheduling a second uplink transmission. The second uplink transmission is indicated as corresponding to a transform precoding configuration different from the transform precoding configuration of the first uplink transmission. A gap between the first uplink transmission and the second uplink transmission is greater than a threshold.
[0066] Therefore, the configuration and indication of dynamic switching of uplink transmission parameters (e.g., transform precoding configuration) of PUSCH scheduled by RAR UL grant or DCI format 0-0 with CRC scrambled by TC-RNTI can be implemented. In addition, time domain requirements related to PUSCH using different transmission parameters (e.g., transform precoding configuration) can be defined. The deployment disclosed in this article can effectively support dynamic switching and selection of uplink transmission parameters (e.g., transform precoding configuration) and flexibly match the needs of coverage enhancement and capability improvement.
[0067] Although various embodiments of the present solution have been described above, it should be understood that these embodiments are presented only as examples and not as limitations. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, those of ordinary skill in the art will understand that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as those of ordinary skill in the art will understand, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.
[0068] It should also be understood that any reference to elements using names such as "first", "second", etc. in this article does not generally limit the number or order of these elements. Instead, these names can be used as a convenient means of distinguishing between two or more elements or instances of elements in this article. Therefore, the reference to the first and second elements does not mean that only two elements can be used or that the first element must precede the second element in some way.
[0069] In addition, those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols such as may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.
[0070] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes in conjunction with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.
[0071] Further, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components and circuits described herein may be implemented in or performed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, modules and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or a combination of any other suitable configurations that perform the functions described herein.
[0072] If these functions are implemented in software, they can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any medium that can enable a computer program or code to be transferred from one location to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to store the required program code in the form of instructions or data structures and any other medium that can be accessed by a computer.
[0073] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various modules are described as separate modules; however, as is clear to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs associated functions according to an embodiment of the present solution.
[0074] In addition, memory or other storage devices and communication components can be used in the implementation of the present solution. It should be understood that, for the purpose of clarity, the above description describes the implementation of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions between different functional units, processing logic elements or domains can be used without detracting from the present solution. For example, functions shown as being performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Therefore, references to specific functional units are only references to suitable means for providing the described functions, rather than indicating a strict logical or physical structure or organization.
[0075] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the widest scope consistent with the new features and principles disclosed herein as described in the following claims.
Claims
1. A wireless communication method, comprising: Receiving, by a wireless communication device, at least one of a first indication or a second indication from a network, wherein at least one of the first indication or the second indication indicates a transmission parameter for uplink transmission, wherein the second indication is used to indicate a relationship between the transmission parameter and the first indication, and the transmission parameter includes a transform precoding configuration; and The uplink transmission is sent, by the wireless communication device, to the network using the transmission parameters indicated by at least one of the first indication or the second indication.
2. The method according to claim 1, wherein: The second indication is a radio resource control (RRC) signaling; The second indication is set to one of the following: a first value indicating enabling transform precoding, a second value indicating disabling the transform precoding, or a third value indicating enabling or disabling the transform precoding based on the first indication.
3. The method according to claim 1, wherein: The second indication is in radio resource control (RRC) signaling; The presence of the second indication indicates enabling or disabling of transform precoding based on the first indication; The absence of the second indication indicates that the transform precoding is enabled or disabled based on at least another parameter in the RRC signaling.
4. The method according to claim 1, wherein: The first indication includes a transform precoding indication field in a downlink control information (DCI) format 0_0.
5. The method according to claim 4, wherein: In response to determining at least one of the following, the transform precoding indication field is present in DCI format 0_0: The wireless communication device has the capability of dynamically switching uplink transmission parameters; The number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding; or The number of bits of DCI format 1_0 before padding is greater than the number of bits of DCI format 0_0 before padding by more than 1 bit.
6. The method according to claim 4, wherein: The transform precoding indication field is located at one of the following locations: the last bit of the DCI format 0_0 after padding the bits of the DCI format 0_0; the second to last bit of the DCI format 0_0 after the bits of the DCI format 0_0 are filled; If the uplink / supplemental uplink indication field does not exist, filling the last bit of the DCI format 0_0 after the bit of the DCI format 0_0; or If the uplink / supplemental uplink indication field exists, the second to last bit of the DCI format 0_0 after the bit of the DCI format 0_0 is filled.
7. The method according to claim 1, wherein: The first indication includes a transform precoding indication field, and in response to determining according to the second indication that the transmission parameter is indicated by the first indication, a downlink control information DCI format for scheduling the uplink transmission includes the transform precoding indication field.
8. The method according to claim 7, wherein: The size of the DCI format including the transform precoding indication field is determined based on the size of the same DCI format in a case where transform precoding is disabled via RRC signaling.
9. The method according to claim 8, wherein: The size of the DCI format including the transform precoding indication field is the same as the size of the same DCI format in a case where the transform precoding is disabled via radio resource control (RRC) signaling; or The size of the DCI format including the transform precoding indication field is 1 bit larger than the size of the same DCI format in a case where the transform precoding is disabled via RRC signaling.
10. The method according to claim 1, further comprising: The uplink transmission is scheduled via a random access response (RAR) uplink grant; The second indication comprises a configuration of resources for a random access procedure corresponding to a transmission parameter of the uplink transmission; initiating the random access procedure using the resources for the random access procedure; and After initiating the random access procedure, the uplink transmission is sent using the transmission parameters.
11. The method according to claim 1, wherein: The uplink transmission is scheduled via a random access response (RAR) uplink grant; The second indication comprises a configuration of resources for the random access procedure corresponding to at least one repetition of the uplink transmission or at least one repetition of a preamble of the random access procedure; initiating the random access procedure using the resources for the random access procedure; and After initiating the random access procedure, the uplink transmission enabling transform precoding is sent.
12. The method of claim 1, wherein: The uplink transmission is scheduled via a random access response (RAR) uplink grant; The second indication includes a configuration of resources for a random access procedure corresponding to enabling or disabling transform precoding for the uplink transmission; initiating the random access procedure using the resources for the random access procedure; and The transformed precoding configuration of the uplink transmission after initiating the random access procedure is indicated in the first indication.
13. The method according to claim 12, wherein: The transform precoding configuration is indicated in a column in a time domain resource allocation (TDRA) table of the RAR uplink grant; or The transform precoding configuration is indicated in a field of the RAR uplink grant.
14. The method according to claim 1, wherein: The uplink transmission is scheduled via a random access response (RAR) uplink grant; and If the wireless communication device repeatedly transmits a preamble for a random access procedure, transform precoding is enabled for the uplink transmission.
15. The method according to claim 1, wherein: The uplink transmission is scheduled via a random access response (RAR) uplink grant; and The same transform precoding configuration as that of the uplink transmission scheduled by the latest downlink control information (DCI) is used.
16. The method according to claim 1, wherein: The uplink transmission is scheduled by downlink control information (DCI) format 0-0 with a cyclic redundancy check (CRC) scrambled by a temporary cell (TC)-radio network temporary identifier (RNTI); The transform precoding configuration is one of: a transformed precoding configuration for an initial transmission of said uplink transmission scheduled by a random access response (RAR) uplink grant; a transformed precoding configuration for uplink transmissions scheduled by DCI format 0-0 with a CRC scrambled by a cell-RNTI (C-RNTI); or The transform precoding configuration is determined according to the configuration of msg3-transformPrecoder.
17. The method according to claim 1, further comprising: An uplink grant for scheduling the uplink transmission is received by the wireless communication device from the network, wherein a time length between the uplink grant and the uplink transmission is determined based on whether the wireless communication device supports dynamic switching of a change precoding configuration.
18. The method of claim 1, further comprising: An uplink grant for scheduling the uplink transmission is received by the wireless communication device from the network, wherein a time length between the uplink grant and the uplink transmission is determined based on whether the uplink grant indicates the use of a transform precoding configuration that is the same as a transform precoding configuration of a most recent uplink transmission.
19. The method of claim 1, further comprising: Receiving, by the wireless communication device, a first uplink grant from the network for scheduling a first uplink transmission; as well as receiving, by the wireless communication device, a second uplink grant from the network for scheduling a second uplink transmission, the second uplink transmission being indicated as corresponding to a transform precoding configuration different from the transform precoding configuration of the first uplink transmission, The gap between the first uplink transmission and the second uplink transmission is greater than a threshold.
20. A wireless communication device comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 1.
21. A computer program product, comprising a computer-readable program medium, on which codes are stored, which, when executed by at least one processor, cause the at least one processor to implement the method according to claim 1.
22. A wireless communication method, comprising: The network sends at least one of a first indication or a second indication to the wireless communication device, wherein at least one of the first indication or the second indication indicates a transmission parameter for uplink transmission, wherein the second indication is used to indicate a relationship between the transmission parameter and the first indication, and the transmission parameter includes a transform precoding configuration; and The uplink transmission from the wireless communication device is received by the network using the transmission parameters indicated by at least one of the first indication or the second indication.
23. A wireless communication device comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 1.
24. A computer program product, comprising a computer-readable program medium on which codes are stored, which, when executed by at least one processor, cause the at least one processor to implement the method according to claim 1.
