Wireless communication method, user equipment and base station

Abstract

A user equipment (UE) performs a wireless communication method. A set of transmit / receive points (TRPs) transmit a first uplink schedule and a second uplink schedule to the UE. The UE receives a first uplink schedule and a second uplink schedule, performs a first uplink transmission using the first uplink schedule, and performs a second uplink transmission using the second uplink schedule. The first uplink transmission and the second uplink transmission are simultaneously transmitted via a plurality of transmit panels.

Description

Background Art 1. Technical field

[0001] The present application relates to the field of communication systems, and in particular to a wireless communication method, user equipment and base station. 2. Related technologies

[0002] Wireless communication systems, such as third-generation (3G) mobile phone standards and technologies are well known. Such 3G standards and technologies have been developed by the Third Generation Partnership Project (3GPP). The third generation of wireless communications has been generally developed to support macrocell mobile phone communications. Communication systems and networks have been developed in the direction of broadband and mobile systems. In a cellular wireless communication system, a user equipment (UE) is connected to a radio access network (RAN) via a wireless link. The RAN includes a group of base stations (BS), which provide wireless links to UEs in cells covered by the base stations, and an interface to a core network (CN), which provides overall network control. As will be understood, the RAN and CN each perform corresponding functions related to the overall network. The 3rd Generation Partnership Project has developed the so-called Long Term Evolution (LTE) system, the Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), for mobile access networks, in which one or more macro cells are supported by base stations called Evolved Node B (eNodeB or eNB). Recently, LTE is evolving further to the so-called 5G or NR (New Radio) system, in which one or more cells are supported by base stations called Next Generation Node B (gNB).

[0003] In LTE and NR, multiple transmission / reception points (TRP) allow base stations to use multiple transmit / receive antenna panels. This feature is also commonly referred to as multiple input multiple output (MIMO). Multiple TRP configurations can be applied to both downlink (base station to user equipment) and uplink (user equipment to base station) transmissions, thereby achieving two-way enhancements in the system. Technical issues

[0004] The current uplink transmission scheme in a multi-TRP system based on multiple downlink control information (DCI) has a disadvantage in that the UE cannot send multiple uplink transmissions to different TRPs simultaneously. This limitation leads to low utilization of time-frequency resources, thereby compromising the system efficiency of the multi-TRP system. Summary of the invention

[0005] The purpose of this application is to propose a user equipment, a base station and a wireless communication method.

[0006] In a first aspect, an embodiment of the present application provides a wireless communication method that can be executed in a UE, the method comprising: receiving a first uplink scheduling and a second uplink scheduling; using the first uplink scheduling to perform a first uplink transmission, and using the second uplink scheduling to perform a second uplink transmission, wherein the first uplink transmission and the second uplink transmission are sent simultaneously via multiple transmitting panels.

[0007] In a second aspect, an embodiment of the present application provides a wireless communication method performed by a group of base stations, the method comprising: receiving a first uplink transmission on a wireless resource scheduled by a first uplink scheduling by a first TRP of the base station; receiving a second uplink transmission on a wireless resource scheduled by a second uplink scheduling by a second TRP of the base station.

[0008] In a third aspect, an embodiment of the present application provides a UE, which includes a processor, and the processor is configured to call and run a computer program stored in a memory so that a device equipped with the processor executes the disclosed method.

[0009] In a fourth aspect, an embodiment of the present application provides a base station, which includes a processor, and the processor is configured to call and run a computer program stored in a memory so that a device equipped with the processor executes the disclosed method.

[0010] The disclosed method can be programmed as computer executable instructions stored in a non-transitory computer readable medium. When loaded into a computer, the non-transitory computer readable medium directs the processor of the computer to perform the disclosed method.

[0011] The non-transitory computer readable medium may include at least one item from the group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an EPROM, an electrically erasable programmable read-only memory, and a flash memory.

[0012] The disclosed method may be programmed as a computer program product which enables a computer to perform the disclosed method.

[0013] The disclosed method may be programmed as a computer program that causes a computer to perform the disclosed method. Beneficial Effects

[0014] The disclosed method enables a UE with multiple transmit panels to send more than one PUSCH transmission simultaneously, thereby enabling improvement of uplink peak throughput.

[0015] At least some embodiments of the disclosed method solve the technical problem by enabling multiple uplink transmissions to be sent simultaneously to different TRPs in a multi-TRP system. The benefits of this solution include:

[0016] Improved system efficiency: By allowing uplink transmissions to be sent to different TRPs simultaneously, the solution improves the utilization of time-frequency resources. This enables resources to be allocated more efficiently, thereby increasing overall system capacity and improving performance.

[0017] Increased throughput: The ability to send multiple uplink transmissions simultaneously enables higher throughput for the UE. The UE is able to transmit data to different TRPs simultaneously, thereby increasing data transfer rates and improving user experience.

[0018] Improved resource utilization: By removing the limitation of a single uplink transmission, the solution optimizes the utilization of available resources. This ensures that time and frequency resources are allocated efficiently and reduces resource waste, thereby using network resources more efficiently and economically.

[0019] Enhanced coverage and connectivity: Uplink transmissions sent to multiple TRPs simultaneously can improve coverage and connectivity. The UE can transmit to different TRPs simultaneously, which helps reduce coverage gaps and improves signal reception at the base station. This benefit is particularly important in scenarios where certain areas may have weak signal conditions.

[0020] Improved spectral efficiency: Efficient use of time and frequency resources by sending uplink transmissions simultaneously results in improved spectral efficiency. This means more data can be transmitted within the same bandwidth, thereby increasing the overall capacity of the system and accommodating more users.

[0021] In summary, this solution enables uplink transmissions to be sent to different TRPs simultaneously, addressing current limitations and improving system efficiency in multi-TRP systems. This solution enhances resource utilization, throughput, coverage, and connectivity while reducing latency, ultimately achieving a more efficient and powerful wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application or related technologies, the following figures to be described in the embodiments are briefly introduced. Obviously, the drawings are only some embodiments of the present application, and ordinary technicians in this field can obtain other drawings based on these drawings without any prerequisites.

[0023] Figure 1 shows a schematic diagram of a telecommunications system;

[0024] Figure 2 A schematic diagram of a UE and a base station is shown;

[0025] Figure 3 A schematic diagram illustrating an embodiment of a wireless communication method;

[0026] Figure 4 A schematic diagram showing another example of non-coherent joint transmission based on multiple TRPs;

[0027] Figure 5 A schematic diagram showing another example of multi-TRP transmission;

[0028] Figure 6 A schematic diagram of a system for wireless communication according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0029] The following describes the embodiments of the present application in detail with reference to the accompanying drawings, using technical issues, structural features, and achieved purposes and effects. Specifically, the terms in the embodiments of the present application are only used to describe the purpose of a specific embodiment, and are not intended to limit the present application.

[0030] The following is a list of abbreviations used in this manual: Table 1 3GPP <![CDATA[3rd Generation Partnership Project (3 rd Generation Partnership Project)]]> 5G <![CDATA[Fifth Generation (5 th Generation)]]> NR New Radio gNB Next generation NodeB DL Downlink UL Uplink PUSCH Physical Uplink Shared Channel PUCCH Physical Uplink Control Channel PDSCH Physical Downlink Shared Channel PDCCH Physical Downlink Control Channel SRS Sounding Reference Signal RS Reference Signal CORESET Control Resource Set DCI Downlink control information TRP Transmission / reception point RRC Radio Resource Control HARQ Hybrid Automatic Repeat Request NW Network TCI Transmission Configuration Indicator Tx Transmission Rx Receive QCL Quasi Co-Location

[0031] The present application provides a solution for a UE to send multiple PUSCHs simultaneously.

[0032] refer to Figure 1 A telecommunication system including UE 10a, UE 10b, a base station (BS) 20a and a network entity device 30 executes the method disclosed in the embodiment of the present application. Figure 1For illustration and not limitation, and the system may include more UE, BS and CN entities. The connections between devices and device components are shown as lines and arrows in the figure. UE 10a may include a processor 11a, a memory 12a and a transceiver 13a. UE 10b may include a processor 11b, a memory 12b and a transceiver 13b. Base station 20a may include a processor 21a, a memory 22a and a transceiver 23a. Network entity device 30 may include a processor 31, a memory 32 and a transceiver 33. Each of processors 11a, 11b, 21a and 31 may be configured to implement the functions, processes and / or methods proposed in this specification. The wireless interface protocol layer may be implemented in processors 11a, 11b, 21a and 31. Each of memories 12a, 12b, 22a and 32 operatively stores various programs and information to operate the connected processors. Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled to a connected processor to send and / or receive wireless signals or wired signals. The UE 10a can communicate with the UE 10b or other UEs. The base station 20a can be one of the eNB, gNB, or other types of wireless nodes, and can configure wireless resources for the UE 10a and the UE 10b.

[0033] Each of the processors 11a, 11b, 21a and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. Each of the memories 12a, 12b, 22a and 32 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other storage devices. Each of the transceivers 13a, 13b, 23a and 33 may include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When the embodiment is implemented in software, the techniques described herein may be implemented using modules, processes, functions, entities, etc. that perform the functions described herein. These modules may be stored in a memory and executed by a processor. The memory may be implemented inside or outside the processor, and the modules in the memory may be communicatively coupled to the processor via various means known in the art.

[0034] The network entity device 30 may be a node in the CN. The CN may include an LTE CN or a 5G Core (5G Core, 5GC), and the 5GC includes a User Plane Function (UPF), a Session Management Function (SMF), an Access and Mobility Management Function (AMF), a Unified Data Management (UDM), a Policy Control Function (PCF), a Control Plane (CP) / User Plane (UP) Separation (CP / UPSeparation, CUPS), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF) and a Network Exposure Function (NEF).

[0035] Examples of UE in the specification may include one of UE 10a and UE 10b. Examples of base stations in the specification may include base station 20a. Figures 2 to 3 For example, an embodiment of UE 10 includes one of UE 10a or UE 10b, and an embodiment of gNB 20 includes base station 20a. Although UE 10 and gNB 20 are described in detail as examples in the specification, the disclosed method can be applied to other UEs and / or other base stations. UL transmission of control signals or data can be a transmission operation from UE to base station. DL transmission of control signals or data can be a transmission operation from base station to UE.

[0036] exist Figure 2 In the embodiment, UE 10 has multiple panels, including panels 14-1, 14-2, ..., and 14-n. Variable n is a positive integer. The transceiver of UE 10 is connected to the panels. Each panel may include one or more antennas or one or more antenna arrays. gNB 20 has multiple TRPs, including TRPs 15-1, 15-2, ..., and 15-m. Variable m is a positive integer. The transceiver of gNB 10 is connected to these TRPs. Each TRP may include one or more antennas or one or more antenna arrays.

[0037] exist Figure 3 In the embodiment, UE 10 and gNB 20 perform an embodiment of a wireless communication method.

[0038] The gNB 20 sends a first uplink scheduling 110 and a second uplink scheduling 111 to the UE 10 (S12). The UE 10 receives the first uplink scheduling 110 and the second uplink scheduling 111 (S13), and sends an uplink transmission according to the first uplink scheduling 110 and the second uplink scheduling 111.

[0039] Specifically, the UE 10 performs a first uplink transmission 114 using a first uplink scheduling 110 and performs a second uplink transmission 115 using a second uplink scheduling 111, wherein the first uplink transmission 114 and the second uplink transmission 115 are simultaneously transmitted via a plurality of transmission panels (S15).

[0040] The first TRP of gNB 20 receives the first uplink transmission 114 on the radio resources scheduled by the first uplink scheduling 110, and the second TRP of gNB 20 receives the second uplink transmission 115 on the radio resources scheduled by the second uplink scheduling 111. The first TRP is abbreviated as TRP 1, and the second TRP is abbreviated as TRP 2. Examples of the first TRP include TRP 14-1, and examples of the second TRP include TRP 14-2.

[0041] In some embodiments, the first uplink transmission 114 is a first PUSCH transmission, and the second uplink transmission 115 is a second PUSCH transmission. The first PUSCH transmission and the second PUSCH transmission completely overlap or partially overlap in the time domain, and completely overlap, partially overlap, or do not overlap in the frequency domain. The first PUSCH transmission is a codebook-based or non-codebook-based transmission, and the second PUSCH transmission is a codebook-based or non-codebook-based transmission.

[0042] In some embodiments, the first uplink scheduling 110 includes a first SRS resource set configured for a first PUSCH transmission, and the second uplink scheduling 111 includes a second SRS resource set configured for a second PUSCH transmission. Each SRS resource set may have an identifier (ID) or index, such as SRS-ResourceSet, SRS-ResourceSetId, SRS-PosResource-r16, SRS-PosResourceSetId-r16, SRS-Resource, or SRS-ResourceId. The first SRS resource set is configured with a parameter "Use" set to be codebook-based or non-codebook-based. The second SRS resource set is configured with a parameter "Use" set to be codebook-based or non-codebook-based. The first SRS resource set is associated with a first CORESETPoolIndex value, and the second SRS resource set is associated with a second CORESETPoolIndex value.

[0043] In some embodiments, the first uplink scheduling 110 includes a first joint TCI state or a first UL TCI state, and the first joint TCI state or the first UL TCI state is a first uplink transmission 114 configuration associated with a first CORESETPoolIndex value. The second uplink scheduling 111 includes a second joint TCI state or a second UL TCI state, and the second joint TCI state or the second UL TCI state is a second uplink transmission 115 configuration associated with a second CORESETPoolIndex value. The first joint TCI state or the first UL TCI state is applied to the first SRS resource set. The second joint TCI state or the second UL TCI state is applied to the second SRS resource set. The configuration of the SRS resource set can be included in the parameters or information elements (IE) in the DL control signal, such as SRS-Resource, SRS-PosResource and SRS-Config. The configuration of the joint TCI state or the UL TCI state can be included in the parameters or IEs in the DL control signal, such as srs-TCI-State.

[0044] In some embodiments, for a Type 1 PUSCH transmission with a configured grant, the SRS resource indicator indicates a first SRS resource set or a second SRS resource set, and a joint TCI state or an uplink TCI state is indicated as being applied to the indicated SRS resource set.

[0045] In some embodiments, the first uplink scheduling 110 is specified by a first DCI, which is transmitted via a first part of a PDCCH, and the second uplink scheduling 111 is specified by a second DCI, which is transmitted via a second part of a PDCCH. The first part of the PDCCH is associated with a first TRP (such as TRP 15-1), and the second part of the PDCCH is associated with a second TRP (such as TRP 15-2). For example, the first part of the PDCCH is referred to as a first PDCCH, which can be transmitted by one TRP (such as TRP 15-1). The second part of the PDCCH is referred to as a second PDCCH, which can be transmitted by the same TRP or another TRP (such as TRP 15-2).

[0046] The first part of the PDCCH is located in a first CORESET having a first CORESETPoolIndex value, and the second part of the PDCCH is located in a second CORESET having a second CORESETPoolIndex value.

[0047] In some embodiments, for a Type 2 PUSCH transmission with a configured grant: ■ If a DCI format is in the PDCCH in the CORESET associated with the first CORESETPoolIndex value, then a Type 2 PUSCH transmission with a configured grant triggered by that DCI format is also associated with the first CORESETPoolIndex value; ■ If a DCI format is in the PDCCH in a CORESET associated with the second CORESETPoolIndex value, then the Type 2 PUSCH transmission with the configured grant triggered by this DCI format is also associated with the second CORESETPoolIndex value.

[0048] For Type 2 PUSCH transmissions with configured grants: ■ If the UE 10 receives a DCI format in a PDCCH in a CORESET associated with a first CORESETPoolIndex value, the UE 10 assumes that a Type 2 PUSCH transmission with a configured grant triggered by this DCI format is also associated with the first CORESETPoolIndex value; ■ If the UE 10 receives a DCI format in a PDCCH in a CORESET associated with a second CORESETPoolIndex value, the UE 10 assumes that a Type 2 PUSCH transmission with a configured grant triggered by this DCI format is also associated with the second CORESETPoolIndex value.

[0049] In some embodiments, for a type 2 PUSCH transmission with configuration authorization, an SRS resource set is indicated based on the association between the CORESETPoolIndex value and the PDCCH in which the received DCI format is located. The DCI format triggers the type 2 PUSCH transmission with configuration authorization and schedules the SRS resource set for the type 2 PUSCH transmission with configuration authorization.

[0050] In some embodiments, for type 2 PUSCH transmission with configuration authorization, the UE determines an SRS resource set based on the association between the CORESETPoolIndex value and the PDCCH where the received DCI format is located, and the DCI format triggers the type 2 PUSCH transmission with configuration authorization, and schedules the SRS resource set for the type 2 PUSCH transmission with configuration authorization.

[0051] The NR system introduces non-coherent joint transmission based on multiple TRPs. Multiple TRPs are connected through a backhaul link for coordination. The backhaul link can be an ideal or non-ideal backhaul. In the case of an ideal backhaul, the TRPs are able to exchange dynamic PDSCH scheduling information with short delays. Therefore, different TRPs are able to coordinate PDSCH transmissions for each individual PDSCH transmission. On the other hand, in the case of a non-ideal backhaul, there is a significant delay in the information exchange between TRPs. Therefore, the coordination between TRPs can only be semi-static or static.

[0052] In non-coherent joint transmission, different TRPs use different PDCCHs to independently schedule PDSCH transmissions. Each TRP can send a single DCI to schedule one PDSCH transmission. PDSCHs from different TRPs can be scheduled in the same or different time slots. Two different PDSCH transmissions from different TRPs can fully overlap or partially overlap in PDSCH resource allocation.

[0053] To support non-coherent joint transmission based on multiple TRPs, the UE is requested to receive PDCCH from multiple TRPs, and subsequently receive PDSCH sent from multiple TRPs. For each PDSCH transmission, the UE can provide feedback to the network in the form of Hybrid Automatic Repeat Request-Acknowledgment (HARQ-ACK) information. In multi-TRP transmission, the UE can provide HARQ-ACK information for each PDSCH transmission to the TRP that sends the PDSCH. The UE can also provide HARQ-ACK information for PDSCH transmissions sent from any TRP to a specific TRP.

[0054] Figure 4 An example of non-coherent joint transmission based on multiple TRPs is shown. In this scenario, the UE receives PDSCH transmission based on non-coherent joint transmission from two TRPs: TRP 1 and TRP 2. Figure 4 As shown, TRP 1 sends a single DCI to schedule PDSCH 1 transmission to the UE, and TRP 2 sends a separate DCI to schedule PDSCH 2 transmission to the UE. On the UE side, the UE receives and decodes the DCI from both TRPs. Based on the DCI from TRP 1, the UE receives and decodes PDSCH 1, and based on the DCI from TRP 2, the UE receives and decodes PDSCH 2.

[0055] exist Figure 4In the example shown, the UE reports HARQ-ACK for PDSCH 1 to TRP 1 and HARQ-ACK for PDSCH 2 to TRP 2. TRP 1 and TRP 2 use different CORESETs and search spaces to send DCI, which is used to schedule PDSCH transmissions sent to the UE. Therefore, the network (NW) can configure multiple CORESETs and search spaces. Each TRP can be associated with one or more CORESETs and associated search spaces. With this configuration, the TRP will use the associated CORESET to send DCI to the UE, and the DCI is used to schedule PDSCH transmissions sent to the UE. The UE can be requested to decode the DCI in the CORESET associated with the TRP to obtain PDSCH scheduling information.

[0056] Figure 5 Another example of multi-TRP transmission is shown. In this scenario, the UE receives PDSCH transmission based on non-coherent joint transmission from two TRPs: TRP 1 and TRP 2. Figure 5 As shown, TRP 1 sends a single DCI to schedule PDSCH 1 transmission to the UE, and TRP 2 sends a single DCI to schedule PDSCH 2 transmission to the UE. On the UE side, the UE receives and decodes the DCI from both TRPs. Based on the DCI from TRP 1, the UE receives and decodes PDSCH 1. Based on the DCI from TRP 2, the UE receives and decodes PDSCH 2. Figure 5 In the example shown, the UE reports HARQ-ACK for both PDSCH 1 and PDSCH 2 to TRP 1. By relaying the HARQ-ACK via the ideal backhaul connecting TRP 1 and TRP 2, both TRP 1 and TRP 2 receive the HARQ-ACK. This is consistent with Figure 4 The HARQ-ACK reporting in the example shown is different. It is important to note that Figure 5 The example shown requires an ideal backhaul between TRP1 and TRP 2, while Figure 4 The example shown can be deployed in scenarios where the backhaul between TRP 1 and TRP 2 is ideal or non-ideal.

[0057] The current uplink transmission scheme in a multi-TRP system based on multi-DCI has a disadvantage in that the UE cannot send multiple uplink transmissions to different TRPs simultaneously. This limitation leads to poor utilization of time-frequency resources, thereby compromising the system efficiency of the multi-TRP system.

[0058] In one embodiment, the gNB can be configured to schedule the UE so that the UE sends two PUSCHs that are fully overlapped or partially overlapped in the time domain, and fully overlapped, partially overlapped, or non-overlapped in the frequency domain. The gNB sends two separate DCIs to schedule the two PUSCHs that are fully overlapped or partially overlapped in the time domain, and fully overlapped, partially overlapped, or non-overlapped in the frequency domain. In other words, the gNB can send a first DCI to schedule a first PUSCH and a second DCI to schedule a second PUSCH. The first PUSCH and the second PUSCH can fully overlap or partially overlap in the time domain, and fully overlap, partially overlap, or non-overlapped in the frequency domain.

[0059] The gNB can configure two SRS resource sets for PUSCH transmission. For example, the gNB can configure a first SRS resource set for codebook-based or non-codebook-based PUSCH transmission (referred to as a first PUSCH transmission), and the gNB can configure a second SRS resource set for codebook-based or non-codebook-based PUSCH transmission (referred to as a second PUSCH transmission). The first PUSCH transmission can be associated with the first SRS resource set, and the second PUSCH transmission can be associated with the second SRS resource set.

[0060] The PDCCH can be classified and divided into two parts: the first part of the PDCCH is associated with the first TRP (e.g., TRP 1), and the second part of the PDCCH is associated with the second TRP (e.g., TRP 2). The first DCI can be transmitted in the first part of any PDCCH, and the second DCI can be transmitted in the second part of any PDCCH.

[0061] In one method, the gNB can provide a configuration of multiple CORESETs for PDCCH transmission, where each CORESET can be associated with a higher layer parameter called CORESETPoolIndex, which can be set to 0 or 1. The gNB can send a first DCI in a PDCCH associated with a CORESET linked to CORESETPoolIndex set to 0 to schedule a first PUSCH. Similarly, the gNB can send a second DCI in a PDCCH associated with a CORESET linked to CORESETPoolIndex set to 1 to schedule a second PUSCH. It is important to note that the first PUSCH and the second PUSCH can fully overlap or partially overlap in the time domain, and fully overlap, partially overlap, or non-overlap in the frequency domain.

[0062] The gNB can configure the first SRS resource set to the parameter "Use" set to codebook-based or non-codebook-based. Additionally, the gNB can configure the second SRS resource set to the same parameter "Use" set to codebook-based or non-codebook-based. The first SRS resource set can be associated with CORESETPoolIndex with a value of 0, and the second SRS resource set can be associated with CORESETPoolIndex with a value of 1.

[0063] The gNB can indicate a first joint TCI state or a first UL TCI state for UL transmissions associated with a first TRP. In other words, the first joint TCI state or the first UL TCI state is a UL transmission configuration associated with CORESETPoolIndex set to 0. Similarly, the gNB can indicate a second joint TCI state or a second UL TCI state for UL transmissions associated with a second TRP, wherein the UL transmissions are associated with CORESETPoolIndex set to 1. In other words, the second joint TCI state or the second UL TCI state is a UL transmission configuration associated with CORESETPoolIndex set to 1.

[0064] The UE can be instructed to apply a first joint TCI state or a first UL TCI state to PUSCH transmissions associated with a first TRP, i.e., UL transmissions associated with CORESETPoolIndex set to 0. Similarly, the UE can be instructed to apply a second joint TCI state or a second UL TCI state to PUSCH transmissions associated with a second TRP, i.e., UL transmissions associated with CORESETPoolIndex set to 1. The gNB can instruct the UE using a configuration or indication in a downlink control signal.

[0065] In addition, the UE can be instructed to apply the first joint TCI state or the first UL TCI state to the SRS resources in the first SRS resource set. Similarly, the UE can be instructed to apply the second joint TCI state or the second UL TCI state to the SRS resources in the second SRS resource set. That is, when transmitting SRS on the SRS resources in the first SRS resource set, the UE applies the parameters of the first joint TCI state or the first UL TCI state to transmit the SRS. Similarly, when transmitting SRS on the SRS resources in the second SRS resource set, the UE applies the parameters of the second joint TCI state or the second UL TCI state to transmit the SRS. The gNB can instruct the UE using the configuration or indication in the downlink control signal.

[0066] A first DCI sent in a PDCCH associated with CORESETPoolIndex set to 0 schedules transmission of a first PUSCH. In the first DCI, a bit field Sounding Reference Signal Resource Indicator (SRI) indicates one or more SRS resources in a first SRS resource set. A second DCI sent in a PDCCH associated with CORESETPoolIndex set to 1 schedules transmission of a second PUSCH. In the second DCI, a bit field SRI indicates one or more SRS resources in a second SRS resource set.

[0067] In one example, an SRS resource indicator (SRI) field within the DCI can provide an indication of whether the SRS resource indicated by the SRI field is from the first SRS resource set or from the second SRS resource set.

[0068] For example, if the PUSCH transmission associated with the first SRS resource set and the second SRS resource set is not configured to follow the indicated unified TCI state, the DCI field "SRS resource indicator" can indicate whether the SRS resource indicated by the SRI field is from the first SRS resource set or the second SRS resource set.

[0069] If the first PUSCH and the second PUSCH partially overlap or completely overlap in the time domain, the UE will expect the first DCI and the second DCI to indicate different SRS resource sets.

[0070] The TCI status is defined in Technical Specification (TS) 38.214.

[0071] PUSCH resource allocation can be semi-statically configured by higher layer parameters through RRC signaling. A PUSCH transmission corresponds to a configuration grant.

[0072] In an embodiment of the disclosed method, the UE can be configured with a type 1 PUSCH transmission with a configured grant. A type 1 PUSCH transmission with a configured grant is a PUSCH transmission with a configured grant type 1 defined using a 3GPP related standard, such as TS 38.321.

[0073] In an example where a higher layer parameter (e.g., RRC signaling) provides a configuration for a type 1 PUSCH transmission with a configuration grant, the UE can be provided with an SRS resource indicator indicating a first SRS resource set or a second SRS resource set. The term "indicated SRS resource set" refers to a first SRS resource set or a second SRS resource set that has been designated or indicated.

[0074] For Type 1 PUSCH transmissions with a configured grant, the UE can be indicated which of the indicated joint TCI states or UL TCI states to use. The term "indicated joint TCI state or UL TCI state" refers to a first joint TCI state or UL TCI state or a second joint TCI state or UL TCI state that has been specified or indicated for or associated with an indicated SRS resource set.

[0075] In one example, for a type 1 PUSCH transmission with a configured grant, the UE can be provided with an SRS resource indicator indicating a first SRS resource set or a second SRS resource set. The UE can be requested to apply a joint TCI state or a UL TCI state to the PUSCH transmission, wherein the joint TCI state or the UL TCI state is indicated to apply to the indicated SRS resource set.

[0076] In one example, for a Type 1 PUSCH transmission with a configured grant, the UE can be provided with an association that associates a joint TCI state or UL TCI state with one of a first SRS resource set or a second SRS resource set. When the first SRS resource set and the second SRS resource set are associated with the same joint TCI state or UL TCI state, the UE can be requested to assume that the PUSCH is associated with one of the first SRS resource set or the second SRS resource set.

[0077] In one example, for a Type 1 PUSCH transmission with a configured grant, the UE can be provided with an association that associates a joint TCI state or UL TCI state with a CORESETPoolIndex having a value of 0 or 1, or that associates the PUSCH transmission with a CORESETPoolIndex having a value of 0 or 1. For example, a first Type 1 PUSCH transmission with a configured grant can be associated with CORESETPoolIndex = 0. For example, a second Type 1 PUSCH transmission with a configured grant can be associated with CORESETPoolIndex = 1. When performing a Type 1 PUSCH transmission with a configured grant associated with a CORESETPoolIndex value, the UE can be requested to apply an indicated joint TCI state or UL TCI state, wherein the indicated joint TCI state or UL TCI state is associated with the CORESETPoolIndex value of the PUSCH transmission.

[0078] In an embodiment of the disclosed method, a UE can be configured with a type 2 PUSCH transmission with a configured grant, wherein resource allocation follows higher layer configuration in RRC and an UL grant received in DCI. A type 2 PUSCH transmission with a configured grant is a PUSCH transmission with a configured grant type 2 defined using 3GPP related standards, such as TS 38.321.

[0079] A Type 2 PUSCH transmission with a configured grant is triggered by a UL grant received in a DCI format such as DCI format 0_1 ​​or 0_2. For such a PUSCH transmission, the UE can be requested to assume that the PUSCH transmission is associated with a CORESETPoolIndex value associated with the CORESET of the PDCCH in which the DCI carrying the UL grant was received. For example, if the UE receives a DCI format in a PDCCH in a CORESET associated with CORESETPoolIndex=0, the UE can assume that a Type 2 PUSCH transmission with a configured grant triggered by this DCI format is also associated with CORESETPoolIndex=0. For example, if the UE receives a DCI format in a PDCCH in a CORESET associated with CORESETPoolIndex=1, the UE can assume that a Type 2 PUSCH transmission with a configured grant triggered by this DCI format is also associated with CORESETPoolIndex=1.

[0080] For a Type 2 PUSCH transmission with a configured grant, the UE can be requested to determine the corresponding SRS resource set from the first SRS resource set and the second SRS resource set according to one or more of the following alternatives: ■Alternative solution 1: The corresponding DCI format can indicate one SRS resource set through the DCI bit field "SRS resource set indicator". ■Alternative 2: The UE can determine an SRS resource set based on the association between the CORESETPoolIndex value and the PDCCH in which the received DCI format is located. The DCI format triggers a Type 2 PUSCH transmission with a configured grant and schedules an SRS resource set for the Type 2 PUSCH transmission with a configured grant. ■ Alternative 3: The UE can determine an SRS resource set according to the indicated joint TCI state or UL TCI state applied to the PUSCH transmission.

[0081] The disclosed method enables a UE with multiple transmit panels to send more than one PUSCH transmission simultaneously, thereby enabling improvement of uplink peak throughput.

[0082] FIG12 is a block diagram of an exemplary system 700 for wireless communication according to an embodiment of the present application. The embodiments described herein can be implemented into the system using any appropriately configured hardware and / or software. FIG12 shows a system 700, which includes a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage device 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780 coupled to each other as shown.

[0083] The processing unit 730 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (such as graphics processors and application processors). The processor may be coupled to a memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on the system.

[0084] The baseband circuit 720 may include circuits, such as but not limited to one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuit may handle various wireless control functions, wherein the various wireless control functions are used to implement communication with one or more wireless networks via RF circuits. The wireless control functions may include but are not limited to signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuit may provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuit may support communication with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other wireless metropolitan area networks (Wireless Metropolitan Area Network, WMAN), wireless local area network (Wireless Local Area Network, WLAN), wireless personal area network (Wireless Personal Area Network, WPAN). An embodiment in which the baseband circuit is configured to support wireless communication of more than one wireless protocol may be referred to as a multi-mode baseband circuit. In various embodiments, the baseband circuit 720 may include circuits that operate using signals that are strictly considered not to be in the baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry that operates with signals having an intermediate frequency that is between the baseband frequency and the radio frequency.

[0085] RF circuit 710 can implement communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the RF circuit 710 can include circuits that operate using signals that are not strictly considered to be in radio frequency. For example, in some embodiments, the RF circuit can include circuits that operate using signals with intermediate frequencies, which are between baseband frequency and radio frequency.

[0086] In various embodiments, the transmitter circuit, control circuit, or receiver circuit discussed above with respect to the UE, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuit, baseband circuit, and / or processing unit. As used herein, "circuitry" may refer to, may be part of, or may include an ASIC, electronic circuit, processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinatorial logic circuits, and / or other suitable hardware components that provide the described functionality. In some embodiments, electronic device circuits may be implemented in one or more software or firmware modules, or the functionality associated with the circuits may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuit, processing unit, and / or memory / storage device may be implemented together on a System-On-Chip (SOC).

[0087] Memory / storage device 740 can be used to load and store data and / or instructions, such as data and / or instructions for the system. Memory / storage device for an embodiment may include any combination of suitable volatile memory (such as dynamic random access memory (DRAM)) and / or non-volatile memory (such as flash memory). In various embodiments, I / O interface 780 may include one or more user interfaces designed to realize the interaction between the user and the system and / or a peripheral component interface designed to realize the interaction between the peripheral component and the system. The user interface may include but is not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. The peripheral component interface may include but is not limited to a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power interface.

[0088] In various embodiments, sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of or interact with a baseband circuit and / or RF circuit to communicate with components of a positioning network (e.g., a global positioning system (GPS) satellite). In various embodiments, display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smart phone, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as computer programs. The computer program may be stored in a storage medium, such as a non-transient storage medium.

[0089] The embodiments of the present application are a combination of technologies / processes that can be adopted in the 3GPP specifications to create a final product.

[0090] It is understood by those of ordinary skill in the art that each of the units, algorithms, and steps described and disclosed in the embodiments of the present application is implemented using electronic hardware or a combination of software and electronic hardware for a computer. Whether the function is run in hardware or in software depends on the conditions of the application and the design requirements of the technical solution. Those of ordinary skill in the art can use different ways to implement the functions of each specific application, and such implementation should not exceed the scope of the present application. It is understood by those of ordinary skill in the art that since the working processes of the above-mentioned systems, devices, and units are basically the same, reference can be made to the working processes of the systems, devices, and units in the above-mentioned embodiments. For ease of description and simplicity, these working processes will not be described in detail.

[0091] It is understood that the disclosed systems, devices and methods in the embodiments of the present application can be implemented in other ways. The above embodiments are exemplary only. The division of units is based only on logical functions, and there are other divisions in the implementation. Multiple units or components can be combined or integrated into another system. It is also possible to omit or skip some features. On the other hand, the mutual coupling, direct coupling or communication coupling shown or discussed is operated indirectly or communicatively in the form of electrical, mechanical or other types through some ports, devices or units.

[0092] The units used to explain the separation components are physically separated or not physically separated. The units used for display are physical units or not physical units, that is, located in one place or distributed on multiple network units. Some units or all units are used according to the purpose of the embodiment. In addition, each functional unit of each embodiment can be integrated into one processing unit, or can be integrated into one processing unit with two or more units, and the processing units are physically independent.

[0093] If the software functional unit is implemented, used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solution proposed in the present application can be substantially or partially implemented in the form of a software product. Alternatively, a part of the technical solution that is beneficial to traditional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium, which includes multiple commands for a computing device (such as a personal computer, a server or a network device) to run all or some of the steps disclosed by the embodiments of the present application. The storage medium includes a USB disk, a mobile hard disk, a ROM, a RAM, a floppy disk or other types of media capable of storing program code.

[0094] The disclosed method enables a UE with multiple transmit panels to send more than one PUSCH transmission simultaneously, thereby improving uplink peak throughput.

[0095] At least some embodiments of the disclosed method solve the technical problem by enabling multiple uplink transmissions to be sent simultaneously to different TRPs in a multi-TRP system. The benefits of this solution include:

[0096] Improved system efficiency: By allowing uplink transmissions to different TRPs simultaneously, the solution improves the utilization of time-frequency resources. This enables resources to be allocated more efficiently, thereby increasing overall system capacity and improving performance.

[0097] Increased throughput: The ability to send multiple uplink transmissions simultaneously enables higher throughput for the UE. The UE is able to transmit data to different TRPs simultaneously, thereby increasing data rates and improving user experience.

[0098] Improved resource utilization: By removing the limitation of a single uplink transmission, the solution optimizes the utilization of available resources. This solution ensures that time and frequency resources are allocated efficiently and reduces resource waste, thereby using network resources more efficiently and economically.

[0099] Enhanced coverage and connectivity: Uplink transmission to multiple TRPs simultaneously can improve coverage and connectivity. The UE is able to transmit to different TRPs simultaneously, which helps reduce coverage gaps and improves signal reception at the base station. This benefit is particularly important in scenarios where certain areas may have weak signal conditions.

[0100] Improved spectral efficiency: The efficient use of time and frequency resources achieved by sending uplinks simultaneously improves spectral efficiency. This means that more data can be transmitted in the same bandwidth, thereby increasing the total capacity of the system and accommodating more users.

[0101] In summary, this solution enables uplinks to be sent to different TRPs simultaneously, solving current limitations and improving system efficiency in multi-TRP systems. This solution enhances resource utilization, throughput, coverage, and connectivity while reducing latency, ultimately achieving a more efficient and powerful wireless communication system.

[0102] While the present application has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the application is not limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A wireless communication method performed by a user equipment UE, characterized in that: The method comprises: Receiving a first uplink scheduling and a second uplink scheduling; A first uplink transmission is performed using the first uplink scheduling, and a second uplink transmission is performed using the second uplink scheduling, wherein the first uplink transmission and the second uplink transmission are sent simultaneously via a plurality of transmission panels.

2. The method according to claim 1, characterized in that: The first uplink transmission is a first physical uplink shared channel PUSCH transmission, and the second uplink transmission is a second PUSCH transmission.

3. The method according to claim 2, characterized in that The first PUSCH transmission and the second PUSCH transmission completely overlap or partially overlap in the time domain, and completely overlap, partially overlap, or do not overlap in the frequency domain.

4. The method according to claim 2, characterized in that: The first PUSCH transmission is codebook-based or non-codebook-based transmission, and the second PUSCH transmission is codebook-based or non-codebook-based transmission.

5. The method according to claim 3, characterized in that: The first uplink scheduling includes a first sounding reference signal SRS resource set configured for the first PUSCH transmission, and the second uplink scheduling includes a second SRS resource set configured for the second PUSCH transmission.

6. The method according to claim 5, characterized in that The first SRS resource set is configured with a parameter “use” set to be based on a codebook or based on a non-codebook; the second SRS resource set is configured with a parameter “use” set to be based on a codebook or based on a non-codebook.

7. The method according to claim 5, characterized in that The first SRS resource set is associated with a first CORESETPoolIndex value, and the second SRS resource set is associated with a second CORESETPoolIndex value.

8. The method according to claim 5, characterized in that The first uplink scheduling includes a first joint transmission configuration indicator TCI state or a first UL TCI state, where the first joint TCI state or the first UL TCI state is the first uplink transmission configuration associated with a first CORESETPoolIndex value; The second uplink scheduling includes a second joint TCI state or a second UL TCI state, and the second joint TCI state or the second UL TCI state is the second uplink transmission configuration associated with a second CORESETPoolIndex value.

9. The method according to claim 8, characterized in that The first joint TCI state or the first UL TCI state is applied to the first SRS resource set; The second joint TCI state or the second UL TCI state is applied to the second SRS resource set.

10. The method according to claim 8, characterized in that The first joint TCI state or the first UL TCI state is applied to the first uplink transmission; The second joint TCI state or the second UL TCI state is applied to the second uplink transmission.

11. The method according to claim 8, characterized in that For a type 1 PUSCH transmission with a configured grant, the SRS resource indicator indicates the first SRS resource set or the second SRS resource set; A joint TCI state or a UL TCI state is indicated as being applicable to the indicated SRS resource set.

12. The method according to claim 1, characterized in that The first uplink scheduling is specified by first downlink control information DCI, and the first DCI is transmitted through the first part of a physical downlink control channel PDCCH; The second uplink scheduling is specified by a second DCI, and the second DCI is transmitted through the second part of the PDCCH.

13. The method according to claim 12, characterized in that The first part of the PDCCH is associated with a first transmission / reception point TRP, and the second part of the PDCCH is associated with a second TRP.

14. The method according to claim 12, characterized in that The first part of the PDCCH is located in a first control resource set CORESET with a first CORESETPoolIndex value, and the second part of the PDCCH is located in a second CORESET with a second CORESETPoolIndex value.

15. The method according to claim 14, characterized in that for a Type 2 PUSCH transmission with a configured grant, if the UE receives a DCI format in a PDCCH in a CORESET associated with the first CORESETPoolIndex value, the UE assumes that the Type 2 PUSCH transmission with the configured grant triggered by the DCI format is also associated with the first CORESETPoolIndex value; If the UE receives a DCI format in the PDCCH in the CORESET associated with the second CORESETPoolIndex value, the UE assumes that the Type 2 PUSCH transmission with the configured grant triggered by the DCI format is also associated with the second CORESETPoolIndex value.

16. The method according to claim 14, characterized in that For type 2 PUSCH transmission with configuration authorization, the UE determines an SRS resource set based on the association between the CORESETPoolIndex value and the PDCCH where the received DCI format is located. The DCI format triggers the type 2 PUSCH transmission with configuration authorization, and schedules the SRS resource set for the type 2 PUSCH transmission with configuration authorization.

17. A user equipment UE, characterized in that: The UE includes: A processor, wherein the processor is configured to call and run a computer program stored in a memory, so that a device equipped with the processor executes the method according to any one of claims 1 to 16.

18. A chip, characterized in that: The chip comprises: A processor, wherein the processor is configured to call and run a computer program stored in a memory so as to enable a device equipped with the chip to perform a method according to any one of claims 1 to 16.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which causes a computer to execute the method according to any one of claims 1 to 16.

20. A computer program product, characterized in that The computer program product comprises a computer program, which causes a computer to execute the method according to any one of claims 1 to 16.

21. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 16.

22. A wireless communication method performed by a base station, characterized in that: The method comprises: Sending a first uplink scheduling and a second uplink scheduling; Receiving, by a first transmitting / receiving point TRP of the base station, a first uplink transmission on the radio resources scheduled by the first uplink scheduling; The second TRP of the base station receives the second uplink transmission on the wireless resources scheduled by the second uplink scheduling.

23. The method according to claim 22, characterized in that The first uplink transmission is a first physical uplink shared channel PUSCH transmission, and the second uplink transmission is a second PUSCH transmission.

24. The method according to claim 23, characterized in that The first PUSCH transmission and the second PUSCH transmission completely overlap or partially overlap in the time domain, and completely overlap, partially overlap, or do not overlap in the frequency domain.

25. The method according to claim 23, characterized in that The first PUSCH transmission is codebook-based or non-codebook-based transmission, and the second PUSCH transmission is codebook-based or non-codebook-based transmission.

26. The method according to claim 24, characterized in that The first uplink scheduling includes a first sounding reference signal SRS resource set configured for the first PUSCH transmission, and the second uplink scheduling includes a second SRS resource set configured for the second PUSCH transmission.

27. The method according to claim 26, characterized in that The first SRS resource set is configured with a parameter "Use" set to be codebook-based or non-codebook-based; The second SRS resource set is configured with a parameter “Use” set to codebook-based or non-codebook-based.

28. The method according to claim 26, characterized in that The first SRS resource set is associated with a first CORESETPoolIndex value, and the second SRS resource set is associated with a second CORESETPoolIndex value.

29. The method according to claim 26, characterized in that The first uplink scheduling includes a first joint transmission configuration indicator TCI state or a first UL TCI state, where the first joint TCI state or the first UL TCI state is the first uplink transmission configuration associated with a first CORESETPoolIndex value; The second uplink scheduling includes a second joint TCI state or a second UL TCI state, and the second joint TCI state or the second UL TCI state is the second uplink transmission configuration associated with a second CORESETPoolIndex value.

30. The method according to claim 29, characterized in that The first joint TCI state or the first ULTCI state is applied to the first SRS resource set; The second joint TCI state or the second UL TCI state is applied to the second SRS resource set.

31. The method according to claim 29, characterized in that The first combined TCI state or the first UL TCI state is applied to the first uplink transmission; The second joint TCI state or the second UL TCI state is applied to the second uplink transmission.

32. The method according to claim 29, characterized in that For a type 1 PUSCH transmission with a configured grant, the SRS resource indicator indicates the first SRS resource set or the second SRS resource set; A joint TCI state or a UL TCI state is indicated as being applicable to the indicated SRS resource set.

33. The method according to claim 22, characterized in that The first uplink scheduling is specified by first downlink control information DCI, and the first DCI is transmitted through the first part of a physical downlink control channel PDCCH; The second uplink scheduling is specified by a second DCI, and the second DCI is transmitted through the second part of the PDCCH.

34. The method according to claim 33, characterized in that The first part of the PDCCH is associated with a first transmission / reception point TRP, and the second part of the PDCCH is associated with a second TRP.

35. The method according to claim 33, characterized in that The first part of the PDCCH is located in a first control resource set CORESET with a first CORESETPoolIndex value, and the second part of the PDCCH is located in a second CORESET with a second CORESETPoolIndex value.

36. The method according to claim 35, characterized in that for a Type 2 PUSCH transmission with a configured grant, if a DCI format is in a PDCCH in a CORESET associated with the first CORESETPoolIndex value, then the Type 2 PUSCH transmission with the configured grant triggered by the DCI format is also associated with the first CORESETPoolIndex value; If a DCI format is in the PDCCH in the CORESET associated with the second CORESETPoolIndex value, then the Type 2 PUSCH transmission with the configured grant triggered by the DCI format is also associated with the second CORESETPoolIndex value.

37. The method according to claim 35, characterized in that For type 2 PUSCH transmission with configuration authorization, an SRS resource set is indicated based on the association between the CORESETPoolIndex value and the PDCCH where the received DCI format is located. The DCI format triggers the type 2 PUSCH transmission with configuration authorization and schedules the SRS resource set for the type 2 PUSCH transmission with configuration authorization.

38. A user equipment UE, characterized in that: The UE includes: A processor, wherein the processor is configured to call and run a computer program stored in a memory so that a device equipped with the processor executes the method according to any one of claims 22 to 37.

39. A chip, characterized in that: The chip comprises: A processor, wherein the processor is configured to call and run a computer program stored in a memory so as to enable a device equipped with the chip to perform a method as claimed in any one of claims 22 to 37.

40. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which causes a computer to execute the method according to any one of claims 22 to 37.

41. A computer program product, characterized in that The computer program product comprises a computer program, which causes a computer to execute the method according to any one of claims 22 to 37.

42. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 22 to 37.

Images