WO2010105667A1

WO2010105667A1 - Configuring the transmission of periodic feedback information on a physical uplink shared channel (pusch)

Info

Publication number: WO2010105667A1
Application number: PCT/EP2009/053134
Authority: WO
Inventors: Esa Tiirola; Timo Lunttila; Kari Pajukoski; Kari Hooli; Matti Kiiski
Original assignee: Nokia Siemens Networks Oy
Priority date: 2009-03-17
Filing date: 2009-03-17
Publication date: 2010-09-23
Also published as: EP2409438A1; ES2905351T3; US20120002568A1; JP2012520645A; EP2409438B1; CN102356580B; KR101440134B1; US11729770B2; KR20140023419A; JP5452705B2; KR20110135407A; CN102356580A

Abstract

In order to facilitate sending of different kinds of channel feedback information, a periodic information transmission in a shared uplink channel is configured, PUSCH, and required resources are allocated for the transmission.

Description

CONFIGURING THE TRANSMISSION OF PERIODIC FEEDBACK INFORMATION ON A PHYSICAL

UPLINK SHARED CHANNEL (PUSCH)

FIELD

[0001] The invention relates to the field of teSecom munications and, particularly, to transmitting periodic information. BACKGROUND

[0002] The following description of background art may include insights, discoveries, understandings or disclosures, or associations together with disclosures not known to the relevant art prior to the present invention but provided by the invention. Some such contributions of the invention may be specifically pointed out below, whereas other such contributions of the invention will be apparent from their context.

[0003] The evolvement of communications technologies and different services increase user needs to obtain over a wireless connection same broadband services that are obtained via a fixed connection. To fulfil both mo- bility requirements and increasing speed requirements, currently a solution called long term evolution release 8, below called LTE, has been specified in 3GPP (Third Generation Partnership Project). LTE is a packet-only wideband radio access with flat architecture that provides higher data speeds and reduced packet latency. [0004] LTE air interface between user equipment (UE) and a base station, also called evolved node B (eNB), is based on an orthogonal frequency-division multiple access (OFDMA) in a downlink and a single-carrier frequency-division multiple access (SC-FDMA) in an uplink that efficiently supports multi-antenna technologies (MlMO). Further, in LTE a carrier bandwidth of up to 20 MHz is split into resource blocks (or physical resource blocks) with which a transmission between user equipment and a base station is scheduled on a shared channel. The shared channel may be formed by allocating resource blocks in different places of the frequency domain. The user equipment measures, using cell-specific or antenna-specific reference signals, downlink channel quality in a predetermined way and transmits downlink channel state information feedback, called CSI, on the uplink to the base station. When the base station performs the downlink scheduling, the base station preferably takes also into account received CSIs.

[0005] In LTE, CSI is sent either on a control channel called PUCCH (physical uplink control channel) in a periodic report having maximum size of 1 1 bits for feedback or on a user traffic shared channel called PUSCH (physical uplink shared channel) in an aperiodic report in which the feedback may be bigger but which can be sent only if the base station triggers the sending by specifically requesting the report by sending an uplink grant to the user equipment. The periodic report may be sent multiplexed on user data on the user traffic shared channel, when user equipment is scheduled, but the maximum size remains the same.

[0006] However, the capabilities of LTE will also evolve towards next generations systems, such as 4G systems, and it is evident that when the features of the air interface increases, the content of CSI will increase and thereby the amount and size of CSI needed and transmitted from the user equipment to the base station will increase, and the periodic and aperiodic reporting of LTE cannot be used as such.

SUMMARY [0007] The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention, it is not intended to identify key/critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.

[0008] An aspect of some embodiments is to provide a periodic information transmission in a shared uplink channel.

[0009] Various aspects of the invention comprise methods, appara- tuses, a system and a computer program product, as defined in the independent claims. Further embodiments of the invention are disclosed in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In the following different embodiments will be described in greater detail with reference to the attached drawings, in which

Figure 1 shows simplified architecture of a radio access network and schematic diagrams of an apparatuses according to an embodiment;

Figures 2, 3 and 4 are information exchange diagrams illustrating exemplary information exchanges according to embodiments; Figure 5 is a flow chart illustrating resource allocations according to an embodiment;

Figure 6 illustrates an exemplary use case according to an embodiment; and

Figure 7 shows an example of a block wise spreading according to an embodiment.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

[0011] Exemplary embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Although the specification may refer to "an", "one", or "some" embodiments) in several locations, this does not necessarily mean that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.

[0012] Embodiments of present invention are applicable to any user terminal (i.e. user equipment), base station, corresponding component, corre- sponding apparatus, and/or to any communication system or any combination of different communication systems having a shared (i.e. a non-dedicated) channel wherefrom resources may be allocated dynamically or semi- persistently. The communication system may be a wireless communication system or a communication system utilizing both fixed networks and wireless networks. The protocols used and the specifications of communication systems, and apparatuses, especially in wireless communication, develop rapidly. Such development may require extra changes to an embodiment. Therefore, all words and expressions should be interpreted broadly and are intended to illustrate, not to restrict, the embodiment. [0013] In the following, different embodiments will be described using, as an example of an access architecture to which the embodiments may be applied, a radio access architecture based on LTE Advanced, LTE-A, that is based on OFDMA in a downlink and a single-carrier frequency-division multiple access SC-FDMA in an uplink, without restricting the embodiments to such an architecture, however. [0014] A general architecture of LTE-A, or more precisely a radio access network 100 implementing LTE-A, is illustrated in Figure 1. Figure 1 is a simplified architecture only showing user equipment 110 configured to be in a wireless connection on communication channels 101 (only one shown in Figure 1 ) in a cell with a base station 120 providing the cell, both apparatuses having some elements and functional entities, all being logical units whose implementation may differ from what is shown. It is apparent to a person skilled in the art that the radio access of LTE-A comprises in practise many base stations serving many user equipment, and one user equipment may use multiple cells, and the radio access of LTE-A may comprise other apparatuses, such as physical layer relay nodes.

[0015] The user equipment 110 Illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with user equipment may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station. The user equipment 110 refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SlM), including, but not limited to, the following types of devices: mobile phone, smartphone, persona! digital assistant (PDA), handset, laptop computer. The user equipment 110 (or a layer 3 relay node) is configured to perform one or more of user equipment functionalities described below with an embodiment, and it may be configured to perform functionalities from different embodiments. For this purpose, the user equipment (or the layer 3 relay node) comprises a feedback unit 111 for providing functionality to form and transmit feedback information according to one or more of the embodiments described below. Further, the apparatus comprises a receiving unit 112 for receiving different inputs, control information, user data and messages, for example, and a sending unit 113 for sending different outputs, control informa- tion, user data and messages, for example.

[0016] The base station, or advanced evolved node B, 120 is a computing device configured to control the radio resources, and connected to a communication system (not shown in Figure 1 ) thereby providing the user equipment 110 a connection to the communication system, in other words, in the illustrated embodiment, all radio-related functionalities of the communication system are located in the base station which, for example, configures con- nection parameters and controls the user equipment measurement reporting. The base station 120 is configured to perform one or more of base station functionalities described below with an embodiment, and it may be configured to perform functionalities from different embodiments. For this purpose, the base station comprises a configuration unit 121 for providing functionality to configure transmission of feedback information according to one or more of the embodiments described below, and a resource allocator unit 124 for allocating resources for the feedback information according to one or more of the embodiments described below. The resource aflocator unit 124 may be integrated with the configuration unit, or with a physical uplink shared channel scheduler (not shown in Figure 1 ). Further, the apparatus comprises a receiving unit 122 for receiving different inputs, control information, user data and messages, for example, and a sending unit 123 for sending different outputs, control information, user data and messages, for example. [0017] In embodiments, in which a common (more centralized) radio resource management and/or scheduling is applied, the configuration unit may locate in another network entity/node than the resource allocator unit, the other network entity taking care of configurations of several cells or base stations or relays. Depending on the implementation, the network entity may further com- prise, at least for some ceils (or base stations or relays), the resource allocator or some functionality of the resource allocator unit. However, in the following it is assumed that the functionalities locate in the same base station without restricting the embodiment to such a solution.

[0018] Although the apparatuses, i.e. the user equipment and the base station, have been depicted as one entity, different units, and processors and memory (not shown in Figure 1 ) may be implemented in one or more physical or logical entities. The units may be software and/or software- hardware and/or firmware components (recorded indelibly on a medium such as read-only-memory or embodied in hard-wired computer circuitry). [0019] The apparatuses may generally include a processor (not shown in Figure 1 ), controfler, control unit, micro-controiler, or the like connected to a memory and to various interfaces of the apparatus. Generally the processor is a central processing unit, but the processor may be an additional operation processor. The feedback unit 11 1 , the configuration unit 121 and/or the resource allocation unit 124 may be configured as a computer or a processor, or a microprocessor, such as a single-chip computer element, or as a chipset, including at least a memory for providing storage area used for arithmetic operation and an operation processor for executing the arithmetic operation. The feedback unit 111 , the configuration unit 121 and/or the resource allocation unit 124 may comprise one or more computer processors, application- specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD)₁ programmable logic devices (PLD), field- programmable gate arrays (FPGA), and/or other hardware components that have been programmed in such a way to carry out one or more functions of one or more embodiments. [0020] The receiving units and the transmitting units each provides an interface in an apparatus, the interface including a transmitter and/or a receiver or a corresponding means for receiving and/or transmitting information, such as data, content, control information, messages and performing necessary functions so that user data, content, control fnformation, messages can be received and/or transmitted. The receiving and sending units may comprise a set of antennas, the number of which is not limited to any particular number.

[0021] The apparatuses may generally include volatile and/or nonvolatile memory (not shown in Figure 1) and typically store content, data, or the like. For example, the memory may store computer program code such as software applications (for example for the emergency location continuity unit) or operating systems, information, data, content, or the like for the processor to perform steps associated with operation of the apparatus in accordance with embodiments. The memory may be, for example, random access memory, a hard drive, or other fixed data memory or storage device. Further, the memory, or part of it, may be removable memory detachably connected to the apparatus.

[0022] It should be appreciated that the apparatus may comprise other units used in or for information transmission. However, they are irrelevant to the actual invention and, therefore, they need not to be discussed in more detail here.

[0023] In an embodiment, the user equipment is configured to utilize a single user multiple input multiple output (SU-MIMO) transmission on the communication channel 101 with the base station 120. in SU-MIMO, the antenna arrangement comprises a set of antennas or an antenna array config- ured to form more than one transmission streams. The transmission streams may be obtained using several antennas, antenna beams or suitably coding. [0024] In another embodiment, a multi-user multiple input multiple output (MU-MIMO) is utilized in the radio access network 100. In MU-MIMO, multiple users in a ceil are utilizing the same transmission resources.

[0025] In another embodiment, a coordinated multi-point (CoMP) is utilized in the radio access network 100. CoMP, applied in an uplink transmission direction, implies the reception of the transmission of user equipment at multiple, geographically separated points. In CoMP, the management and scheduling of radio resources may be taken care of by a common radio resource scheduler that may locate in a "management node" separate from base stations, or the common radio resource scheduler may locate in one base stations but the network may contain also base stations not having a radio resource scheduler.

[0026] Below different embodiments are disclosed using feedback information as an example of a control information, and data as an example of all other information. Further, in Figures 2, 3 and 4, the use of shared channel (PUSCH) is illustrated with dashed line, and the use of a control channel (a physical downlink control channel (PDCCH) and/or a physical uplink control channel (PUCCH), if used) is illustrated with continuous (non-dashed) line.

[0027] Figure 2 illustrates information exchange according to an embodiment. In the embodiment it is assumed for the sake of clarity that the user equipment, UE, supports periodic feedback on PUSCH, and accepts configurations the user equipment receives from the base station, and that periodic feedback configuration and resource allocation is performed semi- persistently via a higher layer signalling, the illustrated example of which is a radio resource control (RRC) signalling, it should be appreciated that any other higher layer signalling may be used.

[0028] Figure 2 starts in a situation in which the base station detects a need for feedback information from the user equipment that supports periodic feedback on PUSCH. For example, the base station notices that there will be user data to be sent on downlink to the user equipment. Therefore the base station determines, in point 2-1 , what feedback information is needed, then determines, in point 2-1 , the amount of resources needed for conveying the needed feedback information, allocates, in point 2-1 , resource blocks from the shared uplink user traffic channel PUSCH, and forms, in point 2-1 , a configura- tion for a periodic feedback on PUSCH, and sends the configuration in message 2-2. A resource block refers herein to a minimum unit that can be allo- cated. The message 2-2 may be an "RRC connection set up" that contains different radio recourse configurations, including the configuration for a periodic feedback on PUSCH. The configuration for a periodic feedback on PUSCH is a semi-persistent configuration and may contain parameters/fields described in Table 1. it should be appreciated that although the table 1 has a number for each parameter, the numbers are not part of the configuration, they are added to facilitate and clarify the description. Further, it should be appreciated that tabie 1 is only an example, and other parameters/fields may be sent in a configuration and some of the parameters described in table 1 may be left out.

Table 1:

[0029] New parameters for a PUSCH configuration, when compared to LTE release 8, are parameters 1 , 2, 4, 6, and 10-14. Parameters 1 and 2 are based on corresponding parameters relating to PUCCH configuration in LTE release 8, and they may be combined into one field. Further, parameters 3, 5, and 7-9, although corresponding to PUSCH parameters in LTE release 8, may be amended. For example, in the above parameter 8 does not indicate a signal redundancy version since HARQ (hybrid automatic response request) is not used with feedback information in the described embodiment. Further, a resource block assignment (parameter 5), modification and coding scheme (parameter 8), and cyclic shift allocation (parameter 9) may use the principles defined for LTE release 8, but they may take into account new features introduced in LTE-advanced, such as a clustered resource assignment principle.

[0030] The parameters 1 to 4 indicate that the configuration relates to periodic reporting and describe what information is needed in reports and what the periodicity is. For example, a periodicity with value 1 may indicate that the resource is allocated in each sub-frame (i.e. as a continuous one), a periodicity with value 2 may indicate that the resource is allocated from every second sub-frame, etc. However, it should be appreciated that any other periodicity definition may be used. The content of a feedback information report is con- figured by the parameters 3 and 4. The feedback information may contain, for example, a channel quality indicator CQi, precoding matrix indicator PMI, rank indicator Ri, quantized complex channel impulse or frequency response, and/or component carrier aggregation-specific information. CQI corresponds preferably to a transport block size/modulation and coding scheme (TBS/MCS) the user equipment is able to support on the assigned sub-band, it should be appreciated that the content of the feedback information is not limited in any way; it may be anything determined useful. Further, the feedback information may be absolute values or delta values, i.e. represented as relative to some information. [0031] The parameters 5 to 12 assign the allocated resources for the feedback information transmission. Sub-resource assignment, i.e. sub- channelization within the allocated physical resource is supported in LTE-A, and therefore the configuration contains the new parameter 6. The parameter 6 defines sub-channelization on the allocated resource, thereby making an allocation granularity (i.e. one resource block offers more resources than feedback information typically contains) less coarse. For example, the parameter 6 may indicate a code division multiplexing/frequency division multiplexing (CDM/FDM) sub-channel to be used. The new parameter 7 defines how long the resources are allocated. There is no restriction on how long the resources may be allocated; they may be allocated infinite, for one shot, for certain time period, for certain amount of transmissions, etc. In order to provide a possibility to increase frequency diversity, the new parameter 8 defines whether or not (and if yes, how) PUSCH hopping is utilized. Since LTE-A supports multi- antenna transmissions also on uplink, uplink transmission mode needs to be configured by the new parameter 11. The parameter 12 may be used to indicate whether or not acknowledgments and negative acknowledgement are sent in the periodic information the configuration relates to. It should be appreciated that the presence or absence of the parameter 12 may indicate the same. [0032] The parameters 13 and 14 relate to enhancing the coverage of the feedback information. With the parameter 13 it may be defined whether or not to apply sub-frame (or sub-slot) repetition for the entire PUSCH, including cyclic redundance check information (CRC). Further, orthogonal cover codes may be applied over repeated sub-frames. Parameter 14 enables transmission of multiple sub-reports of a single feedback information report in consecutive sub-frames. A sub-report may be self-decodable or non-self- decodable, and each sub-report may contain feedback information on one component carrier or one cell, when the coordinated multi-point is applied. (A component carrier or a ceil defines what is measured/reported, i.e. in practise how many bits one report contains.) [0033] In response to the above configuration in message 2-2, the user equipment stores the configuration in point 2-3, acknowledges the configuration in message 2-4, and starts to apply the periodic feedback on PUSCH in point 2-5. More precisely, the user equipment initializes its periodicity counter in the feedback unit to correspond to the received configuration, col- lects the feedback information requested, and sends periodically feedback information 2-6 on PUSCH without any specific request.

[0034] After a while the base station wants to modify the configuration. It may, for example, modify the content of the reports or reallocate resources, and therefore the base station, after modifying the content of the con- figuration, sends, in message 2-7, such as "RRC connection reconfiguration" or "RRC connection configuration", the modified configuration, i.e. in the illustrated example the parameters disclosed in table 1 but at least one of them having a different value compared to a value sent in message 2-2.

[0035] The user equipment updates, in point 2-8, the configuration, acknowledges the reconfiguration by sending message 2-9 (which may be "RRC connection reconfiguration completed") and continues collecting and sending the feedback information 2-6' according to the modified configuration in point 2-5'.

[0036] When the base station determines that it does not any more need the periodic feedback information, the base station sends message 2-10, such as "RRC connection release" and releases allocated resources (not shown in Figure). After that the user equipment deletes the configuration from its memory and stops sending the feedback information on PUSCH. Thus, in the illustrated example the duration (parameter 7) has a value "infinite". How- ever, also some other event than the duration value configured in message 2-2 expiring, or the release command, may cause that the user equipment stops sending the periodic feedback information on PUSCH. An example of such an event is that the user equipment enters a power saving state (DXR, discontinuous reception).

[0037] Thus, sufficiently accurate feedback information is sent over PUSCH without "UL grant" as long as the feedback information is needed. This reduces the downlink overhead.

[0038] Figure 3 illustrates information exchange according to another embodiment. In the embodiment it is assumed that a base station, eNB, requests that a layer 3 relay node transmits periodic data on PUSCH. In the example illustrated in Figure 3, it is further assumed for the sake of clarity that the layer 3 relay node supports periodic information on PUSCH, and accepts configurations the layer 3 relay node receives from the base station. Further, in the embodiment it is assumed that configuration for periodic information is performed semi-persistently via a higher layer signalling, the illustrated example of which is a radio resource control (RRC) signalling. It should be appreciated that any other higher layer signalling may be used. In the embodiment, the physical resources are allocated dynamically by a PUSCH scheduler, and the allocation information is sent over physical downlink control channel.

[0039] Figure 3 starts in an exemplary situation in which the base station, eNB, determines that it needs to schedule the layer 3 relay node, L3 relay, supporting periodic information on PUSCH in order to obtain uplink data via the layer 3 relay node. Therefore the base station determines, in point 3-1 , the amount of resources needed for conveying the data, allocates, in point 3-1 , resource blocks from the shared uplink user traffic channel PUSCH, and forms, in point 3-1 , a configuration for a periodic information on PUSCH, and sends the configuration in message 3-2. The message 3-2 may be a message as described above, including the configuration for periodic information on PUSCH. The configuration for a periodic feedback on PUSCH is a semi-persistent configuration and may contain parameters/fields described in Table 1 above. However, in the embodiment illustrated in Figure 3, the configuration does not contain parameters defining feedback information to be reported, i.e. parameters 3 and 4 are omitted, since the periodic reports are used for data transfer. Further, ACK/NAK-parameter 12 may be omitted in the example. In another embodiment of the invention, the parameters 3 and 4 are used to define the data to be sent in reports.

[0040] In response to the above configuration in message 3-2, the layer 3 relay node stores the configuration in point 3-3, acknowledges the configuration in message 3-4, and starts to apply the periodic information on PUSCH in point 3-5 according to a channelling configured by the configuration in message 3-2 when sending {point 3-5) periodic data 3-6 as long as the du- ration in the configuration message indicates, or a new resource reservation is received, or a new configuration message is received, or the connection is not disabled. However, these are not illustrated in Figure 3. More precisely, the layer 3 relay node initializes its periodicity counter in the feedback unit to correspond the received configuration, and sends periodically data 3-6 on PUSCH without any specific request.

[0041] It should be appreciated that user equipment may as well be configured to send data as described above with Figure 3 and the layer 3 relay node. In that case periodic feedback information may be configured with a separate message, for example, as described above with Figure 2. [0042] Figure 4 illustrates information exchange according to a further embodiment, in the embodiment it is assumed that a base station, eNB, requests that periodic feedback is transmitted concurrently on PUCCH and PUSCH. in the example illustrated in Figure 4, it is further assumed for the sake of clarity that the user equipment, UE, supports periodic feedback on PUSCH, and accepts configurations the user equipment receives from the base station. Further, in the embodiment it is assumed that periodic feedback configuration and resource allocation is performed semi-persistently via a higher layer signalling, the illustrated example of which is a radio resource control (RRC) signalling. It should be appreciated that any other higher layer sig- nailing may be used and/or resource allocation may be performed dynamically. [0043] Figure 4 starts in the same situation as Figure 2, i.e. the base station detects a need for feedback information from the user equipment supporting periodic feedback on PUSCH. Therefore the base station determines, in point 4-1 , what feedback information is needed, then determines, in point 4-1 , what information is to be sent on PUCCH and what on PUSCH. Then the base station determines, in point 4-2, the amount of resources (symbol and power, for example,) needed for conveying the feedback information to be sent on PUSCH and resources (if any) needed on PUCCH, and forms, in point 4-2, a configuration for a periodic information on PUSCH, and a configu- ration for a periodic ACK/NAK on PUCCH, and sends the configurations in message 4-3. The configuration for a periodic feedback on PUSCH may con- tain parameters/fields described in Table 1 above. However, in the embodiment illustrated in Figure 4, the configuration for a periodic feedback on PUSCH indicates that no ACK/NAK is sent on the periodic feedback on PUSCH. [0044] In response to the above configurations in message 4-3, the user equipment stores the configurations in point 4-4, and acknowledges the configurations in message 4-5. The user equipment also performs, in point 4-6, the periodic feedback by collecting feedback information according to the configurations and sending periodic ACK/NAK 4-7 on PUCCH and other periodic feedback information 4-8 on PUSCH according to the corresponding configurations as long as the corresponding connection is not disabled, or reconfigured (not shown in Figure 4).

[0045] In another embodiment, based on the one described with Figure 4, the user equipment multiplexes ACK/NAK information with the other feedback information, i.e. like channel state information is multiplexed with user data in LTE release 8.

[0046] In another embodiment, the base station is further configured to select, on the basis of the needed feedback information, the most efficient way to obtain feedback information. In other words, the base station deter- mines whether to use periodic feedback on a control channel (multiplexed with uplink user data if the user equipment is scheduled), or aperiodic feedback information on a shared channel, or periodic feedback information on pre- assigned resources on the shared channel.

[0047] In another embodiment of the invention, the base station configures periodic feedback on control channel (PUCCH)₁ aperiodic feedback and periodic feedback on the shared channel (PUSCH), and indicates in the configuration which one of the periodic reporting to use with a specific feedback information. Another implementation of the embodiment is that the user equipment selects which periodic reporting to use, aperiodic is used only on specific request, in the embodiment, the user equipment may perform the selections report by report,

[0048] Figure 5 is a flow chart illustrating scheduling according to an embodiment, in which a base station, or more precisely the resource allocating unit, is configured to allocate resources reserved for periodic information on PUSCH to dynamically scheduled user equipment and to semi-persistent user equipment. [0049] The base station is going to schedule, in step 501 , user equipment so that the user equipment uses resources received for periodic information on PUSCH. However, no appropriate configuration exist (step 502), and the base station defines, in step 503, a basic configuration of peri- odic information on PUSCH. The basic configuration defines at least a period to be used, allocated resources from the PUSCH (using a resource block granularity), a sub-channelization (the used cover code, for example) and the lifetime (duration) of the configuration.

[0050] Then the base station decides (step 504), whether or not to use dynamic allocation. The decision may be based on user equipment capabilities, amount and/or type of the information to be transmitted, etc. For example, LTE release 8 user equipment do not support semi-persistent periodic information on PUSCH, but if allocated dynamically, they can be allocated to use the same resources. [0051] If the dynamic allocation is to be applied, the basic configuration is sent, in step 505, in a higher layer signalling, either in a user equipment- specific signalling or in a cell-specific signalling. The base station also allocates a sub-channel from the resources allocated in step 506, the allocation including, if the user equipment supports, assigning additional cover codes, etc. Then the sub-channel information is sent, in step 507, in an uplink grant, as many times as required to transmit the information for which resources are allocated (or as long as the resources reserved to the basic configuration are allocated.)

[0052] If the semi-persistent allocation is to be applied, the base station defines, in step 508, rest of the configuration, including the sub-channel configuration, and sends, in step 509, the configuration in a higher layer user equipment-specific signalling.

[0053] When another user equipment is to be scheduled, the base station starts again in step 501 . If a configuration exists, has enough resources available, and the configuration is an appropriate one (step 502), the base station proceeds to step 504 to determine whether or not dynamic allocation is to be applied.

[0054] in another embodiment of the invention dynamic allocation is always applied. [0055] in a further embodiment, if a basic configuration exists but if it is not suitable, the basic configuration is reconfigured. [0056] Figure 6 illustrates an exemplary use case how a cover code (i.e. a block level spreading code) can be utilized between different cells according to an embodiment when the coordinated multi-point is applied in uplink. In the illustrated example it is assumed that five code channels/one time slot are available within the allocated (assigned) PUSCH frequency resource. Following interference avoidance strategies between the cells may be used to manage the channel resources by means of co-ordinatedly allocating orthogonal code resources between cells: a) a full cover code reuse between different cells (1 user/cell/resource), b) a partial cover code reuse between different cells (inter-cell interference coordination, ICIC)₁ c) a reuse-1 (all cover code resources are in use in different cells), d) a full cover code reuse between different cells, variable band- width allocation between the cells (1 user/celf/resource).

[0057] An advantage of the cover code reuse between the cells is that a low-complexity, low-delay multi-ceil reception is enabled since there is no need to an advanced interference cancelling of multi-cell receivers, and thereby the additional delay caused by it is avoided. [0058] Figure 7 shows an example of a block wise spreading according to an embodiment, in which the block wise spreading is applied to periodic data sent on PUSCH. The block wise spreading increases the multiplexing capacity by a spreading factor (SF) used. As can be seen from Figure 7, the block wise spreading of the resources received for the periodic data on PUSCH (periodic PUSCH) resembles a block wise spreading according to PUCCH format 1/1 a/1 b. In the latter, however, only one symbol is sent, whereas in the embodiment, the amount of sent symbols, including data symbols and reference signal (RS) symbols, is bigger. For example, the amount of data symbols is 12 times the amount of allocated physical resource blocks. [0059] The block wise spreading illustrated in Figure 7 may be performed over one time slot and/or sub-frame, exciuding the reference signal (RS) blocks, regardless of the amount of data blocks in a time slot/sub-frame. Further, the symbol-rate (i.e. the size of the information sent periodically on PUSCH) may be adjusted by modifying the length of the block coding. The length may be modified by modifying the spreading factor used. For example, the spreading factor (i.e. the length of the block-spreading code) may be part of a sub-frame, the spreading factor may be shorter than the number of sub- frames, an additional cover code may be allocated to user equipment providing smaller periodic information, and if there are several TTIs in the transmission, a sub-frame repetition for the entire data blocks including CRC may be applied, and orthogonal cover codes may be applied over the repeated sub-frames.

[0060] In an example illustrating the use of a variable spreading factor and an additional cover code, and thereby the possibility to trade-off the processing gain provided by a channel coding (i.e. a symbol rate) and an interference suppression provided by an orthogonal channelization, which provides an optimized capacity/coverage for the ColviP feedback, in the example, two or more user equipment are transmitting feedback information on PUSCH, user equipment 1 transmitting two data blocks per slot, and the other user equipment are each sending only one data block per slot. If the spreading is performed within a sub-frame and the spreading factor is 6, it is possible to multi- plex the 6 user equipment. However, resources reserved for each user equipment are the same, although half of the resources reserved would have been sufficient for user equipment 2 to 6. Instead, if a spreading factor 3 is used, user equipment 1 may be assigned a cover code #1 , and the user equipment 1 can send one data block (UE1-1) in the beginning (denoted with A) of the sub- frame and the other data block (UE1-2) in the end (denoted with B) of the sub- frame. However, since the other user equipment send only one data block, the same block code will be repeated in the beginning of the sub-frame and in the end of the sub-frame, and an additional block cover can be added on the repetition (i.e. the block coding is two-level block coding). Therefore user equip- ment 2 may be assigned a cover code #2, and an additional cover code #1 , so that half of the data block UE2-1 is sent in the beginning of the sub-frame, half in the end. in the illustrated example user equipment 3 is also assigned the cover code #2, but an additional cover code #2, user equipment 4 is assigned a cover code #3, and the additional cover code #1 , and user equipment 5 is assigned the cover code #3 and the additional cover code #2. The additional cover code may be included in a weighting coefficient, or it may be a separate operation, for example. Thus, 5 user equipments are multiplexed, and the size of the feedback information is for user equipment 1 twice the size for other user equipment. Indexes wθ, w1 , etc., are orthogonal cover code elements with which a repeated data block is multiplied.

[0061] It should be appreciated that additional cover code may be applied over a slot/subframe, although in the example the additional cover code is applied within a slot.

[0062] Orthogonal sub-channels are provided with orthogonal reference signals which may be arranged by means of cyclic shift separation inside a reference signal block. Alternatively, a block level spreading over consecutive reference signal blocks may be utilized. It is also possible to combine cyclic shift separation and block level spreading. Further, it may be sufficient to provide low cross-correlation reference signals (instead of orthogonal reference signals) for different orthogonal sub-channeis. [0063] As regards presence of a sounding reference signal, SRS, periodic information on PUSCH and block spreading, the base station may allocate resources so that bandwidths allocated to periodic information on PUSCH and bandwidths allocated for SRS are not overlapping, in another embodiment, the bandwidths may overlap and the block-wise spreading of the periodic information on PUSCH is configured to enable puncturing of the last PUSCH symbol. This may be achieved by configuring different spreading factors for the sub-frames with and without the possibility to convey SRS. Another alternative is provide user equipment transmitting SRS with information on frequency/time resources occupied by the periodic information on PUSCH so that the user equipment is able to truncate or drop SRSs overlapping with the periodic information on PUSCH.

[0064] If user equipment A has been configured to transmit both the periodic information on PUSCH and SRS on the same sub-frame, simultaneous transmission of them may be denied, and preferably SRS is dropped. This implementation has an advantage that it does not increase cubic metric of the transmitted signal, An alternative implementation is that simultaneous transmission of periodic information on PUSCH and SRS is allowed, at the expense of increased cubic metric.

[0065] In an embodiment, where the periodic information on PUSCH is used with the component carrier aggregation, a coding of a rank indicator corresponding to multiple component carriers and other channel state information corresponding to the multiple component carriers depends on an implementation: they, or at least one of them, may be separately or jointly coded. [0066] In an embodiment, where the periodic information on

PUSCH is used with the coordinated multi-point, coding of a rank indicator cor- responding to multiple cells and other channel state information corresponding to the multiple cells depends on an implementation: they, or at least one of them, may be separately or jointly coded.

[0067] It should be appreciated that channelization is not affected by the implemented coding method (joint or separate).

[0068] The steps/points, messages, information exchange and related functions described above in Figures 2 to 7 are in no absolute chronological order, and some of the steps/points or functions may be performed and/or messages sent simultaneously or in an order differing from the given one. Other functions can also be executed between the points or functions or within the steps/points and other messages sent between the illustrated messages. Some of the functions or the steps/points or part of the steps/points can also be left out or replaced by a corresponding function or step/point or part of the step/point. Further, functions, steps/points and/or messages described with different embodiments may be combined to obtain further embodiments. The messages are only exemplary and may even comprise several separate messages for transmitting the same information. In addition, the messages may also contain other information. Depending on the network technologies involved, other entities may take part to the messaging than those described above.

[0069] it should be appreciated that the above described scheme for periodic information (reporting) on PUSCH may be considered as having a new, configurable and scalable sub-channel on a physical uplink shared channel, the configuration comprising one or more parameters/parameter sets de- fining what is to be sent on periodic reports (i.e. the content of a report, the report covering transmission of any kind of information), and/or one or more parameters/parameter sets defining when a report is sent, and/or one or more parameters/parameter sets defining what transmission format is to be used, and/or one or more parameters/parameter sets defining what air interface re- source to use. Another alternative is to divide the parameters into two subgroups; parameters configuring the physical sub-channel, and parameters relating to a content of reports to be sent over the sub-channel. In an embodiment one or more parameters required to configure the physical sub-channel are mandatory, but the parameters relating to the content are optional. Refer- ring to table 1 , parameters configuring the physical sub-channel may include parameters 1 , 5, 6, 7, 9, 10, 8 (if hopping is supported), 11 (if multi-antenna user equipment), 12 (if simultaneous ACK/NAK is supported), and 13 (if TTI bundling/repetition is supported), rest of the parameters (i.e. parameters 2, 3, 4, and 14) relate to the content, and especially to the content of control information, and may be omitted if the configuration is made for other data than controi information.

[0070] When the sub-channel is configured semi-persistently, it may be considered as a dedicated channel or a dedicated resource (both in frequency and time).

[0071] The techniques described herein may be implemented by various means so that an apparatus implementing one or more functions of a corresponding user equipment or base station described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of a corresponding apparatus described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software, implementation can be through modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in any suitable, processor/computer-readable data storage medium(s) or memory unit(s) or article(s) of manufacture and executed by one or more processors/computers. The data storage medium or the memory unit may be implemented within the processor/computer or external to the processor/computer, in which case it can be communicatively coupled to the processor/computer via various means as is known in the art.

[0072] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The invention and its embodiments are not limited to the examples de- scribed above but may vary within the scope of the claims.

Claims

1. A method comprising: configuring a periodic information transmission to be sent on a physical uplink shared channel; determining the amount of resources needed for a transmission; reserving resources for the periodic information transmission from the physical uplink shared channel; and sending information on the reserved resources to an apparatus performing the reporting.

2. A method as claimed in claim 1 , wherein the configuring includes reserving the resources, and adding information on them to a configuration, and the method further comprises performing the configuring with an upper layer signalling so that the configuration and the resource reservation are semi-persistent.

3. A method as claimed in claim 1 , wherein the method further comprises performing the configuring with an upper layer signalling and reserving the resources dynamically by a scheduler of the physical uplink shared channel.

4. A method as claimed in claim 1 , 2 or 3, wherein the configuring further comprises defining at least one of periodicity, offset, reporting mode, indication of cells, indication of component carriers, subject to be reported, sub-channelization, hopping information, modulation and coding scheme, cyclic shift, uplink transmission mode, transmission time interval, report splitting and duration of the configuration.

5. A method as claimed in claim 4, wherein the sub-channelization is defined by the means of block level spreading indicating a code division multiplexing and/or a frequency division multiplexing.

6. A method as claimed in claim 4 or 5, wherein orthogonal subchannels are provided with low cross-correlation reference signals or with or- thogonal reference signals arranged by at least one of means of cyclic shift separation inside a reference signal block, a block level spreading over consecutive reference signal, or as a combination of cyclic shift separation and block level spreading.

7. A method as claimed in any of the preceding claims, the method further comprising allocating co-ordinated Iy orthogonal code resources be- tween cells.

8. A method as claimed in any of the preceding claims, the method further comprising reconfiguring the periodic information transmission.

9. A method as claimed in any of the preceding claims, wherein the information transmission is channel state information.

10. A method as claimed in any of the preceding claims, wherein the physical uplink shared channel is intended for user traffic.

11. A method comprising: receiving a configuration for information transmission on a physical uplink shared channel, and an indication of the resources allocated for the transmission; detecting that the configuration contains a parameter indicating that periodic transmissions are requested; and sending periodically information according to the configuration on the allocated resources on the physical uplink shared channel.

12. A method as claimed in claim 11 , wherein the method further comprises receiving the indication of the resources as part of the configuration; and receiving the configuration in a higher layer signalling.

13. A method as claimed in claim11 or 12,, wherein the information transmission is channel state information, and the method further comprises performing channel state measurements according to the configuration.

14. An apparatus comprising means for implementing a method as claimed in any of claims 1 to 10.

15. An apparatus as claimed in claim 14, wherein the apparatus is a base station.

16. An apparatus comprising means for implementing a method as claimed in claim 11 , 12 or 13.

17. An apparatus as claimed in claim 16, wherein the apparatus is user equipment or a relay node.

18. An apparatus as claimed in claim 14, 15, 16, or 17, wherein the apparatus is configured to support single user multiple input multiple output, multi-user multiple input multiple output, and/or coordinated multi-point.

19. A system comprising a base station as claimed in claim 14, 15 or 18 and user equipment or a layer 3 relay as claimed in claim 16, 17 or 18.

20. A computer program product comprising computer program code, wherein execution of the program code in an apparatus causes the apparatus to carry out a method according to any of claims 1 to 13.