NETWORK DEVICE, TERMINAL DEVICE, AND METHODS THEREIN

Abstract

The present disclosure provides a method (100) in a network device, the method (100) including determining (s110) a configuration for a terminal device for transmitting a transmission block (TB), the configuration indicating at least a transmission mode in which a single TB is allowed to be transmitted over two or more slots, transmitting (s120) the configuration to the terminal device, and receiving (s130) the TB transmitted from the terminal device according to the configuration.

Description

[Technical field]

[0001] The present disclosure relates to wireless communications, and more particularly to a network device, a terminal device, and methods therein for transmission block transmission across multiple slots. [Background technology]

[0002] In NR Rel-15 and 16, the transport block (TB) size is determined by the resource element (RE) resources, which has a certain number of physical resource blocks (PRBs) and a number of OFDM symbols up to 14, i.e., up to one slot in the time domain. To reach a certain UL data rate, multiple PRBs in a slot are usually allocated for TB transmission.

[0003] However, increasing the resources in the frequency domain leads to a lower power density of the signal transmitted on each OFDM symbol, assuming that the UE has a total power limitation, and therefore to a worse channel estimation accuracy. Therefore, an option to improve the performance of PUSCH transmission is to increase the resources in the time domain, e.g., repetition in the time domain.

[0004] Furthermore, in order to reduce cyclic redundancy check (CRC) overhead and reduce coding rate in addition to increasing time domain resources, a transport block size (TBS) of a physical uplink shared data channel (PUSCH) transmission may be determined according to multiple slots, and different versions of a coded sample may be mapped to different slots for a PUSCH transmission spanning multiple slots. Summary of the Invention

[0005] An object of the present disclosure is to provide a network device, a terminal device, and a method therein that enable TB transmission across multiple slots.

[0006] According to a first aspect of the present disclosure, a method in a network device is provided, which may include determining a configuration for a terminal device for transmitting a transmission block (TB), the configuration indicating at least a transmission mode in which a single TB is allowed to be transmitted over two or more slots, transmitting the configuration to the terminal device, and receiving the TB transmitted from the terminal device according to the configuration.

[0007] In one embodiment, the configuration indicates a type A TBoMS (TB over Multiple Slots) transmission, where a symbol in the same position in each of a certain number of slots is configured to transmit a TB.

[0008] In one embodiment, the configuration includes parameters S, L, and N when a Type A TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot, L indicates the number of adjacent symbols in each slot, and N indicates the number of slots.

[0009] In one embodiment, a group of N slots starting from a first slot is used by the terminal device when transmitting the TB, each slot of the group has at least L adjacent available symbols starting from the symbol indicated by S, and the L adjacent available symbols starting from the symbol indicated by S in each slot of the group are used by the terminal device when transmitting the TB.

[0010] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and available symbols in slots prior to the last slot of the group that are not included in the group and have at least X1 adjacent available symbols starting from the symbol indicated by S are used by the terminal device when transmitting the TB.

[0011] In one embodiment, the available symbols starting from the symbol indicated by S in a slot prior to the last slot of the group that is not included in the group and has X1 or more adjacent available symbols are a symbol-by-symbol repetition of the symbols in that particular slot of the group.

[0012] In one embodiment, the configuration indicates a Type B TBoMS transmission, and the number of symbols across two or more slots is set for transmitting the TB.

[0013] In one embodiment, the Type-B TBoMS transmission comprises at least one of a slot-based Type-B TBoMS transmission and a symbol-based Type-B TBoMS transmission.

[0014] In one embodiment, the configuration includes parameters S and N when slot-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and N indicates the number of slots.

[0015] In one embodiment, the configuration includes parameters S and L when symbol-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and L indicates the number of symbols.

[0016] In one embodiment, the setting is: - intra-slot frequency hopping, - Inter-slot frequency hopping, or - Inter-bundle frequency hopping The signal further indicates the supported frequency hopping, including one or more of:

[0017] In one embodiment, the slots used in transmitting TBs form a predefined number of bundles, each bundle using the same frequency hopping.

[0018] In one embodiment, the configuration further indicates whether frequency hopping is applied for any of the slots used in transmitting TBs with fewer than a predetermined number of adjacent available symbols.

[0019] In one embodiment, if the configuration indicates that frequency hopping is disabled, the terminal device uses the same set of physical resource blocks (PRBs) across N slots, and if the configuration indicates that frequency hopping is enabled, the number of PRBs is the same across N slots.

[0020] In one embodiment, the parameter N is: - N is signaled by a new Downlink Control Information (DCI) field; - N is added to the Time Domain Resource Allocation (TDRA) table and jointly coded with the TDRA field in the DCI, or - N is configured in Radio Resource Control (RRC) The embodiment is indicated by one or more of:

[0021] In one embodiment, the transmission of the TB is scheduled with a dynamic or configured grant.

[0022] In one embodiment, when a dynamic SFI is not configured, the RRC / DCI configures or pre-determines whether a semi-static flexible symbol in a slot configured for transmitting a TB is an available symbol.

[0023] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, and available symbols of slots among the K-1 slots following the first slot that have fewer than X1 adjacent available symbols are not used by the terminal device when transmitting the TB.

[0024] In one embodiment, a group of N slots starting from a first slot are used by a terminal device in transmitting a TB, and each slot in the group other than the first slot has at least 14 available symbols.

[0025] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of contiguous available symbols in each slot, where a group of N slots starting from the first slot are used by the terminal device when transmitting the TB, and each slot of the group other than the first slot has at least X1 contiguous available symbols.

[0026] In one embodiment, available symbols out of the L symbols starting with the symbol indicated by S are used by the terminal device in transmitting TB.

[0027] In one embodiment, the configuration further includes a parameter X1 indicating the minimum number of available symbols in each slot, such that a slot covered by L symbols with fewer than X1 available symbols is not used when transmitting a TB.

[0028] In one embodiment, the L available symbols starting with the symbol indicated by S are used by the terminal device in transmitting TB.

[0029] In one embodiment, the configuration further includes a parameter X1 indicating the minimum number of available symbols in each slot, such that a slot covered by the L available symbols with fewer than X1 available symbols is not counted towards the L available symbols and is not used in transmitting the TB.

[0030] In one embodiment, the available symbols in slots after the first slot that are not used in transmitting the TB are a symbol-by-symbol repetition of the symbols in the particular slot that are used in transmitting the TB.

[0031] In one embodiment, the configuration further includes a physical uplink shared data channel (PUSCH) mapping type.

[0032] In one embodiment, the PUSCH mapping type comprises at least a PUSCH mapping type A and a PUSCH mapping type B, where the PUSCH mapping type A or the PUSCH mapping type B is configured for a Type A TBoMS transmission.

[0033] In one embodiment, when Type A TBoMS transmission is indicated in the configuration, the terminal device uses PUSCH mapping Type B for slots having fewer than L adjacent available symbols used in transmitting the TB.

[0034] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and a slot used in transmitting a TB has at least four available symbols, the terminal device uses PUSCH mapping Type A to transmit the TB, and the demodulation reference signal (DMRS) position in each slot is defined with respect to parameter S defined in PUSCH mapping Type A.

[0035] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and N slots starting from the first slot are used in transmitting a TB, regardless of whether any of the N slots has L available symbols, the terminal device uses PUSCH mapping Type A for slots having fewer than four adjacent available symbols used in transmitting a TB, and the terminal device uses a separately configured DMRS configuration.

[0036] In one embodiment, a PUSCH mapping type B is configured for Type-B TBoMS transmission, and the demodulation reference signal (DMRS) position in each slot depends on the number of adjacent available symbols in the slot.

[0037] In one embodiment, the parameter L defined in the PUSCH mapping Type B for symbol-based Type-B TBoMS transmission is greater than 14 for normal cyclic prefix (CP) or greater than 12 for extended CP.

[0038] In one embodiment, when a dynamic slot format indication (SFI) is set and a TB transmission is scheduled with a dynamic grant, the dynamic downlink symbol in the slot configured for transmitting the TB is considered an unavailable symbol.

[0039] In one embodiment, when a dynamic SFI is configured and a transmission of a TB is scheduled with a configured grant, an RRC / DCI is configured or predetermined as to whether a semi-static flexible symbol in a slot configured for transmitting the TB is an available symbol.

[0040] In one embodiment, a single cyclic redundancy check (CRC) is transmitted for the TB.

[0041] According to a second aspect of the present disclosure, there is provided a network device. The terminal device may include a transceiver, a processor, and a memory. The memory includes instructions executable by the processor, such that the network device is operable to perform the method according to the first aspect above.

[0042] According to a third aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer program instructions which, when executed by a processor in a network device, cause the network device to perform a method according to the first aspect above.

[0043] According to a fourth aspect of the present disclosure, a method in a terminal device is provided, which may include: obtaining a configuration for transmitting a transmission block (TB) from a network device, the configuration indicating at least a transmission mode in which a single TB is allowed to be transmitted over two or more slots; determining resources for transmitting the TB according to the configuration; and transmitting the TB to the network device over the determined resources.

[0044] In one embodiment, the configuration indicates a Type A TB over multiple slots (TBoMS) transmission, where a symbol in the same position in each of a certain number of slots is configured to transmit a TB.

[0045] In one embodiment, the configuration includes parameters S, L, and N when a Type A TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the slot, L indicates the number of adjacent symbols in each slot, and N indicates the number of slots.

[0046] In one embodiment, a group of N slots starting from a first slot is used by the terminal device when transmitting the TB, each slot of the group has at least L adjacent available symbols starting from the symbol indicated by S, and the L adjacent available symbols starting from the symbol indicated by S in each slot of the group are used by the terminal device when transmitting the TB.

[0047] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and available symbols in slots prior to the last slot of the group that are not included in the group and have at least X1 adjacent available symbols starting from the symbol indicated by S are used by the terminal device when transmitting the TB.

[0048] In one embodiment, the available symbols starting from the symbol indicated by S in a slot prior to the last slot of the group that is not included in the group and has X1 or more adjacent available symbols are a symbol-by-symbol repetition of the symbols in that particular slot of the group.

[0049] In one embodiment, the configuration indicates a Type B TBoMS transmission, and the number of symbols across two or more slots is set for transmitting the TB.

[0050] In one embodiment, the Type-B TBoMS transmission comprises at least one of a slot-based Type-B TBoMS transmission and a symbol-based Type-B TBoMS transmission.

[0051] In one embodiment, the configuration includes parameters S and N when slot-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and N indicates the number of slots.

[0052] In one embodiment, the configuration includes parameters S and L when symbol-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and L indicates the number of symbols.

[0053] In one embodiment, the setting is: - intra-slot frequency hopping, - Inter-slot frequency hopping, or - Inter-bundle frequency hopping The signal further indicates the supported frequency hopping, including one or more of:

[0054] In one embodiment, the slots used in transmitting TBs form a predefined number of bundles, each bundle using the same frequency hopping.

[0055] In one embodiment, the configuration further indicates whether frequency hopping is applied for any of the slots used in transmitting TBs with fewer than a predetermined number of adjacent available symbols.

[0056] In one embodiment, if the configuration indicates that frequency hopping is disabled, the terminal device uses the same set of physical resource blocks (PRBs) across N slots, and if the configuration indicates that frequency hopping is enabled, the number of PRBs is the same across N slots.

[0057] In one embodiment, the parameter N is: - N is signaled by a new Downlink Control Information (DCI) field; - N is added to the Time Domain Resource Allocation (TDRA) table and jointly coded with the TDRA field in the DCI, or - N is configured in Radio Resource Control (RRC) The embodiment is indicated by one or more of:

[0058] In one embodiment, the transmission of the TB is scheduled with a dynamic or configured grant.

[0059] In one embodiment, when a dynamic SFI is configured and a transmission of a TB is scheduled with a configured grant, an RRC / DCI is configured or predetermined as to whether a semi-static flexible symbol in a slot configured for transmitting the TB is an available symbol.

[0060] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, and available symbols of slots among the K-1 slots following the first slot that have fewer than X1 adjacent available symbols are not used by the terminal device when transmitting the TB.

[0061] In one embodiment, a group of N slots starting from a first slot are used by a terminal device in transmitting a TB, and each slot in the group other than the first slot has at least 14 available symbols.

[0062] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of contiguous available symbols in each slot, where a group of N slots starting from the first slot are used by the terminal device when transmitting the TB, and each slot of the group other than the first slot has at least X1 contiguous available symbols.

[0063] In one embodiment, available symbols out of the L symbols starting with the symbol indicated by S are used by the terminal device in transmitting TB.

[0064] In one embodiment, the configuration further includes a parameter X1 indicating the minimum number of available symbols in each slot, such that a slot covered by L symbols with fewer than X1 available symbols is not used when transmitting a TB.

[0065] In one embodiment, the L available symbols starting with the symbol indicated by S are used by the terminal device in transmitting TB.

[0066] In one embodiment, the configuration further includes a parameter X1 indicating the minimum number of available symbols in each slot, such that a slot covered by the L available symbols with fewer than X1 available symbols is not counted towards the L available symbols and is not used in transmitting the TB.

[0067] In one embodiment, the available symbols in slots after the first slot that are not used in transmitting the TB are a symbol-by-symbol repetition of the symbols in the particular slot that are used in transmitting the TB.

[0068] In one embodiment, the configuration further includes a physical uplink shared data channel (PUSCH) mapping type.

[0069] In one embodiment, the PUSCH mapping type comprises at least a PUSCH mapping type A and a PUSCH mapping type B, where the PUSCH mapping type A or the PUSCH mapping type B is configured for a Type A TBoMS transmission.

[0070] In one embodiment, when Type A TBoMS transmission is indicated in the configuration, the terminal device uses PUSCH mapping Type B for slots having fewer than L adjacent available symbols used in transmitting the TB.

[0071] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and a slot used in transmitting a TB has at least four available symbols, the terminal device uses PUSCH mapping Type A to transmit the TB, and the demodulation reference signal (DMRS) position in each slot is defined with respect to parameter S defined in PUSCH mapping Type A.

[0072] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and N slots starting from the first slot are used in transmitting a TB, regardless of whether any of the N slots has L available symbols, the terminal device uses PUSCH mapping Type A for slots having fewer than four adjacent available symbols used in transmitting a TB, and the terminal device uses a separately configured DMRS configuration.

[0073] In one embodiment, a PUSCH mapping type B is configured for Type-B TBoMS transmission, and the demodulation reference signal (DMRS) position in each slot depends on the number of adjacent available symbols in the slot.

[0074] In one embodiment, the parameter L defined in the PUSCH mapping Type B for symbol-based Type-B TBoMS transmission is greater than 14 for normal cyclic prefix (CP) or greater than 12 for extended CP.

[0075] In one embodiment, when a dynamic slot format indication (SFI) is set and a TB transmission is scheduled with a dynamic grant, the dynamic downlink symbol in the slot configured for transmitting the TB is considered an unavailable symbol.

[0076] In one embodiment, when a dynamic SFI is not configured, the RRC / DCI configures or pre-determines whether a semi-static flexible symbol in a slot configured for transmitting a TB is an available symbol.

[0077] In one embodiment, a single cyclic redundancy check (CRC) is transmitted for the TB.

[0078] According to a fifth aspect of the present disclosure, there is provided a terminal device. The terminal device may include a transceiver, a processor, and a memory. The memory includes instructions executable by the processor, such that the terminal device is operable to perform the method according to the fourth aspect above.

[0079] According to a sixth aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer program instructions which, when executed by a processor in a terminal device, cause the terminal device to perform a method according to the fourth aspect above.

[0080] In an embodiment of the present disclosure, a single TB can be transmitted across multiple slots, thus enhancing the performance of PUSCH transmission.

[0081] The above and other objects, features and advantages will become more apparent from the following description of the embodiments with reference to the drawings. [Brief description of the drawings]

[0082] [Figure 1] 1 is a flowchart illustrating a method in a network device according to one embodiment of the present disclosure. [Diagram 2] 1 is a flowchart illustrating a method in a terminal device according to one embodiment of the present disclosure. [Diagram 3] FIG. 2 is a block diagram of a network device according to another embodiment of the present disclosure. [Figure 4]FIG. 2 is a block diagram of a network device according to another embodiment of the present disclosure. [Diagram 5] FIG. 2 is a block diagram of a terminal device according to one embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram of a terminal device according to another embodiment of the present disclosure. [Figure 7] FIG. 2 illustrates an example of a Type A multi-slot TB transmission according to one embodiment of the present disclosure. [Figure 8] FIG. 13 illustrates another example of Type A multi-slot TB transmission according to one embodiment of the present disclosure. [Figure 9] FIG. 2 illustrates an example of slot-based Type B multi-slot TB transmission according to one embodiment of the present disclosure. [Figure 10] FIG. 1 illustrates a schematic diagram of a communications network connected to a host computer via an intermediate network. [Figure 11] FIG. 1 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection. [Figure 12] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 13] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 14] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 15] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0083] As used herein, the term "wireless communication network" refers to a network conforming to any suitable communication standard, such as NR, LTE-Advanced (LTE-A), LTE, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), etc. Furthermore, communications between terminal devices and network devices in a wireless communication network may be performed in accordance with any suitable generation of communications protocols, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 1G (first generation), 2G (second generation), 2.5G, 2.75G, 3G (third generation), 4G (fourth generation), 4.5G, 5G (fifth generation) communications protocols, wireless local area network (WLAN) standards, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth, and / or Zigbee standards, and / or any other protocols either currently known or to be developed in the future.

[0084] The term "network node" or "network device" refers to a device in a wireless communication network through which a terminal device accesses and receives services from the wireless communication network. A network node or network device refers to a base station (BS), an access point (AP), or any other suitable device in a wireless communication network. A BS may be, for example, a Node B (Node B or NB), an evolved Node B (eNode B or eNB), or a gNB, a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as femto, pico, etc. Yet further examples of a network device may include an MSR radio equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node. More generally, however, a network device may represent any suitable device (or group of devices) capable of, set up, configured, and / or operable to enable and / or provide terminal device access to a wireless communication network or to provide some service to terminal devices that have accessed the wireless communication network.

[0085] The term "terminal device" refers to any end device capable of accessing and receiving services from a wireless communication network. By way of example and not limitation, a terminal device refers to a mobile terminal, a user equipment (UE), or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smartphone, a voice over IP (VoIP) phone, a wireless local loop telephone, a tablet, a personal digital assistant (PDA), a wearable terminal device, a vehicle mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), and the like. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured for communication according to one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As used herein, "user equipment" or "UE" does not necessarily have a "user" in the sense of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For example, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from a wireless communication network. Instead, a UE may represent a device that is intended for sale to or operation by a human user, but may not be initially associated with a particular human user.

[0086] The terminal device may support device-to-device (D2D) communication, for example by implementing the 3GPP standard for sidelink communication, in which case it may be referred to as a D2D communication device.

[0087] As yet another example, in an Internet of Things (IOT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another terminal device and / or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may be referred to as a machine-type communication (MTC) device in the 3GPP context. As one particular example, the terminal device may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal electrical appliances, e.g., personal wearables such as refrigerators, televisions, clocks, etc. In other scenarios, the terminal device may represent a vehicle or other equipment capable of monitoring and / or reporting on its operating status, or other functions related to its operation.

[0088] As used herein, downlink transmission refers to transmission from a network device to a terminal device, and uplink transmission refers to transmission in the opposite direction.

[0089] References herein to "one embodiment," "an embodiment," "exemplary embodiment," and the like indicate that the embodiment being described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, it is submitted that when a particular feature, structure, or characteristic is described with respect to an embodiment, it is within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic with respect to other embodiments, whether or not explicitly described.

[0090] Terms such as "first" and "second" may be used herein to describe various elements, but it will be understood that these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0091] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly dictates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including" as used herein specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0092] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0093] 1.1 PUSCH Repetition in NR Rel-15 and Rel-16 1.1.1 NR Rel-15 Slot aggregation for the Physical Downlink Shared Data Channel (PUSCH) was supported in Rel-15 and renamed to PUSCH repetition type A in Rel-16. The name "PUSCH repetition type A" is used even when there is only a single repetition, i.e., no slot aggregation. In Rel.15, PUSCH transmissions that overlap with downlink (DL) symbols are not transmitted. > DCI Granted Multi-slot Transmission (PDSCH / PUSCH) vs. Semi-Static DL / UL Allocation If the semi-static DL / UL allocation configuration of a slot has no directional conflict with the allocated symbols of a scheduled PDSCH / PUSCH, the PDSCH / PUSCH in that slot is received / transmitted. If the semi-static DL / UL allocation configuration of a slot has a directional collision with the allocated symbols of a scheduled PDSCH / PUSCH, then the PDSCH / PUSCH transmission in that slot is not received / transmitted, i.e. the effective repetition number is reduced.

[0094] In Rel.15, the number of repetitions is semi-statically set by the RRC parameter pusch-AggregationFactor. At most 8 repetitions are supported. pusch-AggregationFactor ENUMERATED{n2,n4,n8}

[0095] 1.1.2 NR Rel-16 A new repetition format PUSCH repetition type B is supported in Rel-16, which allows successive repetitions of a PUSCH transmission. The biggest difference between the two types is that PUSCH repetition type A only allows a single repetition in each slot, with each repetition occupying the same positioned symbol. Using this format with a PUSCH length shorter than 14 would result in gaps between repetitions, increasing the overall latency. Another change compared to Rel.15 is how the repetition number is signaled. In Rel.15, the repetition number is semi-statically configured, while in Rel.16, the repetition number can be dynamically indicated in the DCI. This applies to both dynamic grants and configured grant type 2.

[0096] In NR R16, the invalid symbols for PUSCH repetition type B include reserved uplink (UL) resources. The invalid symbol pattern indicator field is set in the scheduling DCI. Segmentation is done around the symbols indicated as DL by the semi-static TDD pattern and the invalid symbols.

[0097] If dynamic indication of TDD patterns through DCI format 2_0 (ie, SFI) is configured, the segmentation behavior is different for dynamic grants and configured grants.

[0098] In case of dynamic grant, the UE only sees scheduling DCI and segments around the semi-static DL symbols and reserved symbols dictated by the pattern.

[0099] For configured grants, segmentation is based on semi-static DL symbols and patterns for reserved resources, but some actual repetitions are dropped based on receipt of an SFI. If the UE receives an SFI, it drops actual repetitions that overlap with dynamically indicated DL or flexible symbols. If the UE does not receive an SFI that covers an actual repetition, it drops the repetition if any of the symbols in the repetition are semi-static flexible symbols.

[0100] The signaling of the repetition number is shown below.

[0101] From 3GPP TS38.214 v.16.2.0: For PUSCH repetition type A, when transmitting a PUSCH scheduled by DCI format 0_1 ​​or 0_2 in a PDCCH with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, the number of repetitions K is - if numberofrepetitions is present in the resource allocation table, the number of repetitions K is equal to numberofrepetitions, - otherwise, if pusch-AggregationFactor is configured in the UE, the number of repetitions K is equal to pusch-AggregationFactor; - Else, K=1 is determined as:

[0102] Format DCI0_1 in 3GPP TS38.212 V16.1.0: Time domain resource allocation – 0, 1, 2, 3, 4, 5, or 6 bits - 0, 1, 2, 3 or 4 bits as specified in 3GPP TS 38.214 clause 6.1.2.1 if the higher layer parameter USCH-TimeDomainResourceAllocationList-ForDCIformat0_1 is not set and if the higher layer parameter pusch-TimeDomainAllocationList is set. The bit width for this field is The time-domain allocation list (TIFF0007676559000001.tif) is determined as 8170 bits, where I is the number of entries in the upper layer parameter pusch-TimeDomainAllocationList or pusch-TimeDomainAllocationList-r16. - 0, 1, 2, 3, 4, 5 or 6 bits as specified in clause 6.1.2.1 of 3GPP TS 38.214 if the higher layer parameter PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 is set. The bit width for this field is TIFF0007676559000002.tif6170 bits, where I is the number of entries in the higher layer parameter PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1. - Otherwise, the bit width for this field is The size of the default table is determined as TIFF0007676559000003.tif6170 bits, where I is the number of entries in the default table.

[0103] From 3GPP TS38.331 V16.1.0 PUSCH-Config information element JPEG0007676559000004.jpg31170PUSCH - Time Domain Resource Allocation Information Element JPEG0007676559000005.jpg127170JPEG0007676559000006.jpg15170

[0104] 1.2 TDRA In PUSCH transmission, the time domain resource allocation (TDRA) is determined by K2, the start symbol S, the number of consecutive symbols L, and the mapping type. K2 indicates which slot is used for PUSCH transmission. S indicates the start symbol for PUSCH transmission in the scheduling slot, and L indicates the length of the consecutive symbols for PUSCH transmission. The mapping type indicates different combinations of S and L for PUSCH.

[0105] Specifically, it is assumed that the UE transmits PUSCH in the slot TIFF0007676559000007.tif11170, where n is the slot with scheduling DCI, and u PUSCH and u PDCCH are the sub - carrier spacing settings for PUSCH and PDCCH. There are two ways to represent S and L. In the first way, S and L are represented separately. In the second way, S and L are combined and represented by SLIV using the following formula. When (L - 1) ≤ 7, SLIV = 14(L - 1)+S In other cases, SLIV = 14(14 - L + 1)+(14 - 1 - S) where 0 < L ≤ 14 - S. The mapping type rules are shown in the following table. TIFF0007676559000008.tif103170

[0106] 1.2.1 Method of Indicating Parameters in TDRA There are three cases for scheduling PUSCH transmissions, including UL grant in DCI, configured grant type 1, and configured type 2. They use different ways to indicate parameters in TDRA.

[0107] A group of parameters indicates the values ​​of K2, SLIV and mapping type at the same time, and the group of parameters constitutes a TDRA list in the RRC signaling or a default PUSCH TDRA table. The time domain resource allocation in the DCI field or timeDomainAllocation in the RRC then indicates an index of the TDRA list or a row of the default PUSCH TDRA table.

[0108] 1) When a PUSCH transmission(s) is scheduled by an UL grant in the DCI, the UE determines which PUSCH TDRA configuration to use based on the RNTI and the PDCCH search space. The following table shows the relationship between them. Table 6.1.2.1.1-1: Applicable PUSCH time domain resource allocations TIFF0007676559000009.tif125170

[0109] 1.1) When default A is applied, the TDRA list is shown in the table below for normal CP and extended CP. Table 6.1.2.1.1-2: Default PUSCH time domain resource allocation for normal CP A TIFF0007676559000010.tif100170 Table 6.1.2.1.1-3: Default PUSCH time domain resource allocation for extended CP A TIFF0007676559000011.tif100170, where j is determined by the PUSCH numerology shown in the table below. Table 6.1.2.1.1-4: Provision for the value j TIFF0007676559000012.tif29170

[0110] In the default table A for normal CP and extended CP, there are 16 rows indicating different TDRA parameters. If the PUSCH is scheduled by DCI format 0_0, the time domain resource allocation value m (comprising 4 bits) in the DCI field indicates row index m+1 of the default table. If the PUSCH is scheduled by DCI format 0_1 ​​and no higher layer parameters are configured, the time domain resource allocation value m (comprising 4 bits) in the DCI field indicates row index m+1 of the default table.

[0111] 1.2) If pusch-configCommon applies, it contains pusch-TimeDomainAllocationList as shown below. JPEG0007676559000013.jpg57170

[0112] The pusch-TimeDomainAllocationList contains the group TDRA parameters as shown below. JPEG0007676559000014.jpg47170

[0113] The value of the time domain resource allocation field in DCI0_1 then points to an element in the list, with a value of 0 referring to the first element in the list, a value of 1 referring to the second element in the list, and so on.

[0114] 1.3) If pusch-config applies, it contains a pusch-TimeDomainAllocationList as shown below. JPEG0007676559000015.jpg191170

[0115] The pusch-TimeDomainAllocationList contains the group TDRA parameters as shown below. JPEG0007676559000016.jpg48170

[0116] The value of the time domain resource allocation field in DCI0_1 then points to an element in the list, with a value of 0 referring to the first element in the list, a value of 1 referring to the second element in the list, and so on.

[0117] 2) When PUSCH transmission(s) are scheduled by configured grant type 1, the selection of default table A, or pusch-TimeDomainAllocationList provided by pusch-ConfigCommon, or pusch-TimeDomainAllocationList provided by pusch-Config follows the rules for UE-specific search space in Table 6.1.2.1.1-1. Also, timeDomainAllocation in configuredGrantConfig provides a value m indicating index m+1 for default table A or pusch-TimeDomainAllocationList. JPEG0007676559000017.jpg221170

[0118] 3) When PUSCH transmission(s) is scheduled with configured grant type 2, resource allocation follows higher layer configuration according to 3GPP TS38.321 and UL grant received on DCI.

[0119] 1.2.2 PUSCH repetition type A For PUSCH repetition type A, when transmitting a PUSCH scheduled by DCI format 0_1 ​​or 0_2 in a PDCCH with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, the number of repetitions K is - if numberofrepetitions is present in the resource allocation table, the number of repetitions K is equal to numberofrepetitions, - otherwise, if pusch-AggregationFactor is configured in the UE, the number of repetitions K is equal to pusch-AggregationFactor; - Else, K=1 is determined as:

[0120] For PUSCH repetition type A, the same symbol allocation is applied over K consecutive slots, for K>1, and PUSCH is restricted to a single transmission layer. The UE shall repeat TB over K consecutive slots and apply the same symbol allocation in each slot.

[0121] DM-RS Location for Intra-Slot Frequency Hopping From 3GPP TS38.211 V16.0.0 Table 6.4.1.1.3-6: PUSCH DM-RS positions within a slot for single symbol DM-RS and intra-slot frequency hopping enabled TIFF0007676559000018.tif6170. TIFF0007676559000019.tif67170

[0122] 2. TBoMs Configuration In the following, the term "TBoMS" stands for "TB over multiple slots" or "TB processing over multiple slots." The expression "covered" by a certain number of symbols or slots refers to slots that are considered unavailable slots when counting symbols or slots and are therefore ignored when counting, but that range from the first symbol to the last symbol of said number of symbols or from the first slot to the last slot of said number of slots.

[0123] 1 is a flowchart illustrating a method 100 according to one embodiment of the present disclosure. The method 100 may be implemented in a network device, for example, a gNB.

[0124] In step s110, the network device determines a configuration for the terminal device for transmitting TBs, the configuration indicating at least a transmission mode in which a single TB is allowed to be transmitted over more than one slot.

[0125] In step s120, the network device transmits the configuration to the terminal device.

[0126] Then, in step s130, the network device receives the TB sent from the terminal device according to the setting.

[0127] In one embodiment, the configuration indicates a Type A multi-slot TB transmission, in which a symbol in the same position in each of a certain number of slots is configured to transmit a TB.

[0128] In one embodiment, the configuration indicates a Type B multi-slot TB transmission, in which the number of symbols across two or more slots is configured to transmit a TB.

[0129] In one embodiment, the Type-B TBoMS transmission comprises at least one of a slot-based Type-B TBoMS transmission and a symbol-based Type-B TBoMS transmission.

[0130] The network device sets the transmission mode for transmitting the TB to the terminal device. For example, the terminal device may be set to type A TBoMS transmission, slot-based type B TBoMS transmission, or symbol-based type B TBoMS transmission.

[0131] In one embodiment, the configuration includes parameters S, L, and N when a Type A TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the slot, L indicates the number of adjacent symbols in each slot, and N indicates the number of slots.

[0132] In one embodiment, the configuration includes parameters S and N when slot-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and N indicates the number of slots.

[0133] In one embodiment, the configuration includes parameters S and L when symbol-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and L indicates the number of symbols.

[0134] The network device configures the terminal device with resource allocation, for example parameters to be used in TBoMS transmission.

[0135] In one embodiment, available symbols among the configured symbols are used by the terminal device when transmitting the TB, i.e., if slot-based Type-B TBoMS transmission or Type-A multi-slot transmission is configured by the network device, the terminal device drops unavailable symbols and uses available symbols among the configured symbols when transmitting the TB.

[0136] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and a slot among the N slots starting from the first slot that has fewer than X1 adjacent available symbols starting from the symbol indicated by S is not used by the terminal device when transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where a slot among the N slots that has fewer than X1 adjacent available symbols starting from the symbol indicated by S is considered as an unavailable slot. The available slots among the N slots are used by the terminal device when transmitting the TB. In this case, at most N slots are used by the terminal device when transmitting the TB.

[0137] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, and a slot among the N-1 slots following the first slot that has fewer than X1 adjacent available symbols is not used by the terminal device when transmitting the TB. That is, when slot-based Type-B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where slots other than the first slot among the N slots that have fewer than X1 adjacent available symbols starting from the symbol indicated by S are considered as unavailable slots. Available symbols of available slots among the N slots are used by the terminal device when transmitting the TB.

[0138] In one embodiment, a group of N slots starting from the first slot is used by the terminal device in transmitting the TB, and each slot of the group has at least L adjacent available symbols starting from the symbol indicated by S. In that case, the L adjacent available symbols starting from the symbol indicated by S in each slot of the group are used by the terminal device in transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where in counting the N slots, slots having less than L adjacent symbols starting from the symbol indicated by S are not counted. The counted N slots are used by the terminal device in transmitting the TB. In particular, the L adjacent available symbols starting from the symbol indicated by S in each slot of the counted N slots are used by the terminal device in transmitting the TB.

[0139] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and available symbols in slots before the last slot of the group that are not included in the group and have X1 or more adjacent available symbols starting from the symbol indicated by S are used by the terminal device when transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where slots that have less than X1 adjacent available symbols starting from the symbol indicated by S are not counted when counting the N slots. The counted N slots are used by the terminal device when transmitting the TB. In particular, the terminal device uses L adjacent available symbols starting from the symbol indicated by S in slots among the counted K slots if the slot has at least L adjacent available symbols starting from the symbol indicated by S, and uses all adjacent available symbols starting from the symbol indicated by S in slots among the counted K slots if the slot has L or less adjacent available symbols starting from the symbol indicated by S.

[0140] In one embodiment, a group of N slots starting from the first slot is used by the terminal device in transmitting the TB, and each slot of the group other than the first slot has at least 14 available symbols. That is, when a slot-based Type-B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where slots other than the first slot that have less than 14 available symbols are not counted in counting the N slots. The available symbols of the counted N slots are used by the terminal device in transmitting the TB.

[0141] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, and a group of N slots starting from the first slot are used by the terminal device in transmitting the TB, and each slot of the group other than the first slot has X1 or more adjacent available symbols. That is, when the slot-based Type B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where in counting the N slots, slots other than the first slot that have fewer than X1 adjacent available symbols are not counted. The available symbols of the counted N slots are used by the terminal device in transmitting the TB.

[0142] In one embodiment, the available symbols starting from the symbol indicated by S in slots prior to the last slot of the group that are not included in the group and have X1 or more adjacent available symbols are symbol-by-symbol repetitions of the symbol in a particular slot of the group, i.e., when a slot-based Type-B TBoMS transmission or Type-A multi-slot transmission is configured by the network device, a slot that is considered as an unavailable slot when counting the N slots carries a symbol repetition of the symbol of the particular slot among the N counted slots.

[0143] In one embodiment, available symbols among the L symbols starting from the symbol indicated by S are used by the terminal device in transmitting TB, i.e., when symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L symbols from the first symbol indicated by S and uses available symbols among the L symbols in transmitting TB.

[0144] In one embodiment, L available symbols starting from the symbol indicated by S are used by the terminal device in transmitting TB, i.e., when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L available symbols from the symbol indicated by S and uses the counted L available symbols in transmitting TB.

[0145] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of available symbols in each slot, and a slot covered by L symbols with fewer than X1 available symbols is not used in transmitting the TB. That is, when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L symbols from the first symbol indicated by S, and a slot with fewer than X1 available symbols covered by L symbols is considered an unavailable slot, and the symbols of the unavailable slot are not used in transmitting the TB. In this case, the terminal device uses at most L symbols in transmitting the TB.

[0146] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of available symbols in each slot, and a slot covered by the L available symbols with fewer than X1 available symbols is not counted for the L available symbols and is not used in transmitting the TB. That is, when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L available symbols from the symbols indicated by S, and a slot with fewer than X1 available symbols is not counted in counting the available symbols and is considered as an unavailable slot. That is, a symbol of an unavailable slot is not counted in counting the L available symbols and is not used in transmitting the TB. The terminal device uses the counted L available symbols in transmitting the TB.

[0147] In one embodiment, the available symbols in the slots after the first slot that are not used in transmitting the TB are symbol-by-symbol repetitions of the symbols in the particular slot used in transmitting the TB, i.e., when symbol-based Type B TBoMS transmission is configured by the network device, the slots not used in transmitting the TB carry symbol repetitions of the symbols in the particular slot not used in transmitting the TB.

[0148] In one embodiment, the configuration further includes a physical uplink shared data channel (PUSCH) mapping type.

[0149] In one embodiment, the PUSCH mapping type comprises at least a PUSCH mapping type A and a PUSCH mapping type B, where the PUSCH mapping type A or the PUSCH mapping type B is configured for a Type A TBoMS transmission.

[0150] In one embodiment, when Type A TBoMS transmission is indicated in the configuration, the terminal device uses PUSCH mapping Type B for slots having fewer than L adjacent available symbols used in transmitting the TB.

[0151] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and a slot used in transmitting a TB has at least four available symbols, the terminal device uses PUSCH mapping Type A to transmit the TB, and the demodulation reference signal (DMRS) position in each slot is defined with respect to parameter S defined in PUSCH mapping Type A.

[0152] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and N slots starting from the first slot are used in transmitting a TB, regardless of whether a slot among the N slots has L available symbols, the terminal device uses PUSCH mapping Type A for slots having fewer than four adjacent available symbols used in transmitting a TB, and the terminal device uses a separately configured DMRS configuration.

[0153] In one embodiment, a PUSCH mapping type B is configured for Type-B TBoMS transmission, and the demodulation reference signal (DMRS) position in each slot depends on the number of adjacent available symbols in the slot.

[0154] In one embodiment, the parameter L defined in the PUSCH mapping Type B for symbol-based Type-B TBoMS transmission is greater than 14 for normal cyclic prefix (CP) or greater than 12 for extended CP.

[0155] In one embodiment, the setting is: - intra-slot frequency hopping, - Inter-slot frequency hopping, or - Inter-bundle frequency hopping The signal further indicates the supported frequency hopping, including one or more of:

[0156] In one embodiment, the slots used in transmitting TBs form a predefined number of bundles, each bundle using the same frequency hopping.

[0157] In one embodiment, the configuration further indicates whether frequency hopping is applied for any of the slots used in transmitting TBs with fewer than a predetermined number of adjacent available symbols.

[0158] In one embodiment, if the configuration indicates that frequency hopping is disabled, the terminal device uses the same set of physical resource blocks (PRBs) across N slots, and if the configuration indicates that frequency hopping is enabled, the number of PRBs is the same across N slots.

[0159] In one embodiment, when a Type A TBoMS transmission or a slot-based Type B TBoMS transmission is configured by a network device, the parameter N is: - N is signaled by a new Downlink Control Information (DCI) field; - N is added to the Time Domain Resource Allocation (TDRA) table and jointly coded with the TDRA field in the DCI, or - N is configured in Radio Resource Control (RRC) The embodiment is indicated by one or more of:

[0160] In one embodiment, the transmission of the TB is scheduled with a dynamic or configured grant.

[0161] In one embodiment, when a dynamic slot format indication (SFI) is set and a TB transmission is scheduled with a dynamic grant, the dynamic downlink symbol in the slot configured for transmitting the TB is considered an unavailable symbol.

[0162] In one embodiment, when a dynamic SFI is configured and a transmission of a TB is scheduled with a configured grant, an RRC / DCI is configured or predetermined as to whether a semi-static flexible symbol in a slot configured for transmitting the TB is an available symbol.

[0163] In one embodiment, when a dynamic SFI is not configured, the RRC / DCI configures or pre-determines whether a semi-static flexible symbol in a slot configured for transmitting a TB is an available symbol.

[0164] In one embodiment, a single cyclic redundancy check (CRC) is transmitted for the TB.

[0165] 2 is a flowchart illustrating a method 200 according to one embodiment of the present disclosure. The method 200 may be implemented in a terminal device, for example, a UE.

[0166] In step s210, the terminal device obtains a configuration for transmitting TBs from a network device, the configuration indicating at least a transmission mode in which a single TB can be transmitted over two or more slots.

[0167] The terminal device then determines resources for transmitting the TB according to the configuration in step s220, and transmits the TB to the network device over the determined resources in step s230.

[0168] In one embodiment, the configuration indicates a Type A TBoMS transmission, in which a symbol in the same position in each of a certain number of slots is configured to transmit a TB.

[0169] In one embodiment, the configuration indicates a Type B TBoMS transmission, in which a number of symbols across two or more slots is configured for transmitting a TB.

[0170] In one embodiment, the Type-B TBoMS transmission comprises at least one of a slot-based Type-B TBoMS transmission and a symbol-based Type-B TBoMS transmission.

[0171] The network device sets the transmission mode for transmitting the TB to the terminal device. For example, the terminal device may be set to type A TBoMS transmission, slot-based type B TBoMS transmission, or symbol-based type B TBoMS transmission.

[0172] In one embodiment, the configuration includes parameters S, L, and N when a Type A TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the slot, L indicates the number of adjacent symbols in each slot, and N indicates the number of slots.

[0173] In one embodiment, the configuration includes parameters S and N when slot-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and N indicates the number of slots.

[0174] In one embodiment, the configuration includes parameters S and L when symbol-based Type B TBoMS transmission is indicated in the configuration, where S indicates the starting symbol for the start of the first slot and L indicates the number of symbols.

[0175] The network device configures the terminal device with resource allocation, for example parameters to be used in TBoMS transmission.

[0176] In one embodiment, available symbols among the configured symbols are used by the terminal device when transmitting the TB, i.e., if slot-based Type-B TBoMS transmission or Type-A multi-slot transmission is configured by the network device, the terminal device drops unavailable symbols and uses available symbols among the configured symbols when transmitting the TB.

[0177] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and a slot among the N slots starting from the first slot that has fewer than X1 adjacent available symbols starting from the symbol indicated by S is not used by the terminal device when transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where a slot among the N slots that has fewer than X1 adjacent available symbols starting from the symbol indicated by S is considered as an unavailable slot. The available slots among the N slots are used by the terminal device when transmitting the TB. In this case, at most N slots are used by the terminal device when transmitting the TB.

[0178] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, and a slot among the N-1 slots following the first slot that has fewer than X1 adjacent available symbols is not used by the terminal device when transmitting the TB. That is, when the slot-based Type-B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where a slot other than the first slot among the N slots that has fewer than X1 adjacent available symbols is considered as an unavailable slot. The available symbols of the available slots among the N slots are used by the terminal device when transmitting the TB.

[0179] In one embodiment, a group of N slots starting from the first slot is used by the terminal device in transmitting the TB, and each slot of the group has at least L adjacent available symbols starting from the symbol indicated by S. In that case, the L adjacent available symbols starting from the symbol indicated by S in each slot of the group are used by the terminal device in transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where in counting the N slots, slots having less than L adjacent symbols starting from the symbol indicated by S are not counted. The counted N slots are used by the terminal device in transmitting the TB. In particular, the L adjacent available symbols starting from the symbol indicated by S in each slot of the counted N slots are used by the terminal device in transmitting the TB.

[0180] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols starting from the symbol indicated by S in each slot, and available symbols in slots before the last slot of the group that are not included in the group and have X1 or more adjacent available symbols starting from the symbol indicated by S are used by the terminal device when transmitting the TB. That is, when the Type A TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where slots that have less than X1 adjacent available symbols starting from the symbol indicated by S are not counted when counting the N slots. The counted N slots are used by the terminal device when transmitting the TB. In particular, the terminal device uses L adjacent available symbols starting from the symbol indicated by S in slots among the counted K slots if the slot has at least L adjacent available symbols starting from the symbol indicated by S, and uses all adjacent available symbols starting from the symbol indicated by S in slots among the counted K slots if the slot has L or less adjacent available symbols starting from the symbol indicated by S.

[0181] In one embodiment, a group of N slots starting from the first slot is used by the terminal device in transmitting the TB, and each slot of the group other than the first slot has at least 14 available symbols. That is, when a slot-based Type-B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where slots other than the first slot that have less than 14 available symbols are not counted in counting the N slots. The available symbols of the counted N slots are used by the terminal device in transmitting the TB.

[0182] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of adjacent available symbols in each slot, where each slot in the group of N slots starting from the first slot, other than the first slot, has X1 or more adjacent available symbols. That is, when slot-based Type-B TBoMS transmission is configured by the network device, the terminal device counts N slots from the first slot, where in counting the N slots, slots other than the first slot that have fewer than X1 adjacent available symbols are not counted. The available symbols of the counted N slots are used by the terminal device in transmitting the TB.

[0183] In one embodiment, the available symbols starting from the symbol indicated by S in slots prior to the last slot of the group that are not included in the group and have X1 or more adjacent available symbols are symbol-by-symbol repetitions of the symbol in a particular slot of the group, i.e., when a slot-based Type-B TBoMS transmission or Type-A multi-slot transmission is configured by the network device, a slot that is considered as an unavailable slot when counting the N slots carries a symbol repetition of the symbol of the particular slot among the N counted slots.

[0184] In one embodiment, available symbols among the L symbols starting from the symbol indicated by S are used by the terminal device in transmitting TB, i.e., when symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L symbols from the first symbol indicated by S and uses available symbols among the L symbols in transmitting TB.

[0185] In one embodiment, L available symbols starting from the symbol indicated by S are used by the terminal device in transmitting TB, i.e., when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L available symbols from the symbol indicated by S and uses the counted L available symbols in transmitting TB.

[0186] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of available symbols in each slot, and a slot covered by L symbols with fewer than X1 available symbols is not used in transmitting the TB. That is, when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L symbols from the first symbol indicated by S, and a slot with fewer than X1 available symbols covered by L symbols is considered an unavailable slot, and the symbols of the unavailable slot are not used in transmitting the TB. In this case, the terminal device uses at most L symbols in transmitting the TB.

[0187] In one embodiment, the configuration further includes a parameter X1 indicating a minimum number of available symbols in each slot, and a slot covered by the L available symbols with fewer than X1 available symbols is not counted for the L available symbols and is not used in transmitting the TB. That is, when the symbol-based Type B TBoMS transmission is configured by the network device and the parameter L is set, the terminal device counts L available symbols from the symbols indicated by S, and a slot with fewer than X1 available symbols is not counted in counting the available symbols and is considered as an unavailable slot. That is, a symbol of an unavailable slot is not counted in counting the L available symbols and is not used in transmitting the TB. The terminal device uses the counted L available symbols in transmitting the TB.

[0188] In one embodiment, the available symbols in the slots after the first slot that are not used in transmitting the TB are symbol-by-symbol repetitions of the symbols in the particular slot used in transmitting the TB, i.e., when symbol-based Type B TBoMS transmission is configured by the network device, the slots not used in transmitting the TB carry symbol repetitions of the symbols in the particular slot not used in transmitting the TB.

[0189] In one embodiment, the configuration further includes a physical uplink shared data channel (PUSCH) mapping type.

[0190] In one embodiment, the PUSCH mapping type comprises at least a PUSCH mapping type A and a PUSCH mapping type B, where the PUSCH mapping type A or the PUSCH mapping type B is configured for a Type A TBoMS transmission.

[0191] In one embodiment, when Type A TBoMS transmission is indicated in the configuration, the terminal device uses PUSCH mapping Type B for slots having fewer than L adjacent available symbols used in transmitting the TB.

[0192] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and a slot used in transmitting a TB has at least four available symbols, the terminal device uses PUSCH mapping Type A to transmit the TB, and the demodulation reference signal (DMRS) position in each slot is defined with respect to parameter S defined in PUSCH mapping Type A.

[0193] In one embodiment, when Type A TBoMS transmission is indicated in the configuration and N slots starting from the first slot are used in transmitting a TB, regardless of whether a slot among the N slots has L available symbols, the terminal device uses PUSCH mapping Type A for slots having fewer than four adjacent available symbols used in transmitting a TB, and the terminal device uses a separately configured DMRS configuration.

[0194] In one embodiment, a PUSCH mapping type B is configured for Type-B TBoMS transmission, and the demodulation reference signal (DMRS) position in each slot depends on the number of adjacent available symbols in the slot.

[0195] In one embodiment, the parameter L defined in the PUSCH mapping Type B for symbol-based Type-B TBoMS transmission is greater than 14 for normal cyclic prefix (CP) or greater than 12 for extended CP.

[0196] In one embodiment, the setting is: - intra-slot frequency hopping, - Inter-slot frequency hopping, or - Inter-bundle frequency hopping The signal further indicates the supported frequency hopping, including one or more of:

[0197] In one embodiment, the slots used in transmitting TBs form a predefined number of bundles, each bundle using the same frequency hopping.

[0198] In one embodiment, the configuration further indicates whether frequency hopping is applied for any of the slots used in transmitting TBs with fewer than a predetermined number of adjacent available symbols.

[0199] In one embodiment, if the configuration indicates that frequency hopping is disabled, the terminal device uses the same set of physical resource blocks (PRBs) across N slots, and if the configuration indicates that frequency hopping is enabled, the number of PRBs is the same across N slots.

[0200] In one embodiment, when a Type A TBoMS transmission or a slot-based Type B TBoMS transmission is configured by a network device, the parameter N is: - N is signaled by a new Downlink Control Information (DCI) field; - N is added to the Time Domain Resource Allocation (TDRA) table and jointly coded with the TDRA field in the DCI, or - N is configured in Radio Resource Control (RRC) The embodiment is indicated by one or more of:

[0201] In one embodiment, the transmission of the TB is scheduled with a dynamic or configured grant.

[0202] In one embodiment, when a dynamic slot format indication (SFI) is set and a TB transmission is scheduled with a dynamic grant, the dynamic downlink symbol in the slot configured for transmitting the TB is considered an unavailable symbol.

[0203] In one embodiment, when a dynamic SFI is configured and a transmission of a TB is scheduled with a configured grant, an RRC / DCI is configured or predetermined as to whether a semi-static flexible symbol in a slot configured for transmitting the TB is an available symbol.

[0204] In one embodiment, when a dynamic SFI is not configured, the RRC / DCI configures or pre-determines whether a semi-static flexible symbol in a slot configured for transmitting a TB is an available symbol.

[0205] In one embodiment, a single cyclic redundancy check (CRC) is transmitted for the TB.

[0206] Corresponding to the above described method 100, a network device is provided. Figure 3 is a block diagram of a network device 300 according to one embodiment of the present disclosure.

[0207] As shown in FIG. 3, the network device 300 includes a determining unit 310 configured to determine a setting for the terminal device for transmitting a TB.

[0208] The network device 300 further includes a sending unit 320 configured to send the configuration.

[0209] The network device 300 may further include a receiving unit 330 configured to receive the TB transmitted from the terminal device according to the configuration.

[0210] The determining unit 310, the sending unit 320 and the receiving unit 330 of the network device 300 may be configured to perform the actions described with respect to FIG. 1 to implement the functionality of the network device.

[0211] The units 310-330 may be implemented as a pure hardware solution or as a combination of software and hardware, for example by a processor or microprocessor and sufficient software and memory for storage of the software, a programmable logic device (PLD), or one or more of the other electronic components or processing circuits described above and shown, for example, in FIG. 1, configured to perform the actions.

[0212] FIG. 4 is a block diagram of a network device 400 according to another embodiment of the present disclosure.

[0213] The network device 400 includes a transceiver 410, a processor 420, and a memory 430. The memory 430 includes instructions executable by the processor 420 such that the network device 400 is operable to perform actions of procedures, for example, as previously described in conjunction with FIG.

[0214] In one embodiment, the memory 430 includes instructions executable by the processor 420 such that the network device 400 is operable to determine settings for a terminal device for transmitting TBs, transmit the settings to the terminal device, and receive TBs transmitted from the terminal device in accordance with the settings.

[0215] Corresponding to the above-described method 200, a terminal device is provided. Figure 5 is a block diagram of a terminal device 500 according to one embodiment of the present disclosure.

[0216] As shown in FIG. 5, the terminal device 500 includes an obtaining unit 510 configured to obtain a setting for transmitting a TB from a network device.

[0217] The terminal device 500 may further include a determining unit 520 configured to determine a resource for transmitting the TB according to the configuration.

[0218] The terminal device 500 may further include a transmitting unit 530 configured to transmit the TB to the network device over the determined resources.

[0219] The obtaining unit 510, the determining unit 520 and the sending unit 530 of the terminal device 500 may be configured to perform the actions described with respect to FIG. 2 to implement the functions of the terminal device.

[0220] The units 510-530 may be implemented as a pure hardware solution or as a combination of software and hardware, for example by a processor or microprocessor and sufficient software and memory for storage of the software, a programmable logic device (PLD), or one or more of the other electronic components or processing circuits described above and shown, for example, in FIG. 2, configured to perform the actions.

[0221] FIG. 6 is a block diagram of a terminal device 600 according to another embodiment of the present disclosure.

[0222] The terminal device 600 includes a transceiver 610, a processor 620, and a memory 630. The memory 630 includes instructions executable by the processor 620 such that the terminal device 600 is operable to perform actions of procedures, for example, as previously described in conjunction with FIG.

[0223] In one embodiment, the memory 630 includes instructions executable by the processor 620 such that the terminal device 600 is operable to obtain a configuration for transmitting a TB from a network device, determine resources for transmitting the TB according to the configuration, and transmit the TB to the network device over the determined resources.

[0224] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer-readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory, and a hard drive. The computer program product includes a computer program. The computer program includes code / computer-readable instructions that, when executed by the processor 420, cause the network device 400 to perform actions of a procedure, e.g., previously described with reference to FIG. 1, or code / computer-readable instructions that, when executed by the processor 620, cause the terminal device 600 to perform actions of a procedure, e.g., previously described with reference to FIG. 2.

[0225] The computer program product may be configured as computer program code structured in computer program modules, which may essentially implement the actions of the flows shown in FIG.

[0226] The processor may be a single CPU (Central Processing Unit), but may also comprise two or more processing units. For example, the processor may include a general-purpose microprocessor, an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor such as an application specific integrated circuit (ASIC). The processor may also comprise an on-board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a random access memory (RAM), a read only memory (ROM), or an EEPROM, and the computer program modules described above may be distributed on different computer program products in the form of memories in alternative embodiments.

[0227] The present disclosure is not limited to the above embodiments, and may further include the following embodiments.

[0228] 3.1 Overview PUSCH coverage has been identified as one of the coverage bottlenecks. In NR Rel-15 / 16, one UL TB is limited to UL symbols in a slot. To support high data rates, multiple PRBs in a slot form a TB, and multiple PRBs share the UE transmit power. Transport Block (TB) processing across multiple slots, i.e., TBoMS, has been proposed as a candidate solution for PUSCH coverage extension. TBoMS extends the TB across slot boundaries to increase the power spectral density and reduce the code rate by reducing the CRC overhead in some slots of the TB. The mechanism of TBoMS and related signaling are described below.

[0229] The TBoMS transmission may be based on a dynamic grant and / or a configured grant. We use the terms "DG-based TBoMS transmission" and "CG-based TBoMS transmission", respectively.

[0230] Here, dynamic grants refer to grants provided by L1 signaling or MAC layer, e.g., random access response, configured grants refer to grants provided by RRC and / or at least partly by DCI to activate configured grants, similar to CG type 1 and CG type 2, respectively, as specified in NR releases R15 and R16.

[0231] In embodiment 1, TBoMS transmission may be scheduled by dynamic grant and / or configured grant for PUSCH transmission.

[0232] In some TDD UL / DL configurations, there are a small number of adjacent UL slots in a radio frame. To exploit the time diversity of TBoMS, the slots of TB do not need to be adjacent.

[0233] In embodiment 2, the multiple slots and symbols of a TB may be contiguous or non-contiguous within a radio frame or across frame boundaries.

[0234] In embodiment 3, when frequency hopping is disabled, the UE uses the same set of PRBs across multiple slots of the TB. When frequency hopping is enabled, the number of PRBs is the same across multiple slots of the TB.

[0235] Some examples of unavailable symbols are DL symbols, UL symbols in slots not scheduled for the UE, semi-static flexible symbols that are later configured as DL symbols by dynamic SFI, UCI on higher priority PUCCH, and RRC / DCI configured invalid symbols. Invalid symbol patterns are supported for Rel-16 PUSCH repetition type B, and invalid symbol patterns can also be configured for TBoMS transmissions.

[0236] There may be several types of TBoMS transmission with different methods for allocation of the number of UL symbols in multiple slots for TB. In this invention, the term "Type A TBoMS transmission" is used for a type of TBoMS transmitted using the same UL symbol in each of multiple slots, and another term "Type B TBoMS transmission" is used for a type of TBoMS transmitted on multiple slots that allows available UL symbols across the slots. Time domain resource allocation may be slot-based for both types, i.e., UL resources in a certain number of slots are allocated for TB. For Type B TBoMS transmission, symbol-based resource allocation, i.e., resource allocation based on the number of symbols, is also applicable.

[0237] Embodiment 4, Type A TBoMS transmission uses the same UL symbol in each slot of multiple slots of a TB.

[0238] In a sub-embodiment of embodiment 4, the UE needs to be configured with S, L and N for Type A TBoMS transmission, where S and L are the starting symbol relative to the start of a slot and the number of consecutive symbols in a slot in the set of multiple slots of a TB, respectively, and N is the number of slots of a TB.

[0239] Embodiment 5, Type B TBoMS transmission uses all available UL symbols in multiple slots of TB.

[0240] In a sub-embodiment of embodiment 5, one resource allocation for Type-B TBoMS transmission may be slot-based, whereby the UE uses all available UL symbols in N slots of TB. The UE needs to be configured with S and N for slot-based Type-B TBoMS transmission. S is the starting symbol in the first slot of the multiple slots for TB. N is the number of slots of TB. L is predetermined as 14 and does not need to be explicitly configured.

[0241] The S, L and N definitions for Type A TBoMS transmissions and slotted-based Type B TBoMS transmissions can be found in Table 3.5-1.

[0242] A TDD network configures a semi-static TDD pattern via RRC signaling and dynamic slot format via DCI format 2_0 with SFI.

[0243] In embodiment 6, one or more of the following methods may be applied for TBoMS transmission with respect to semi-static flexible symbols and transmission contention with dynamic SFI. - If dynamic SFI is not set, □ For UEs scheduled with dynamic or configured grants, it may be RRC / DCI configured or predetermined whether semi-static flexible symbols are available. For example, for a UE with a dynamic grant, semi-static flexible symbols are available. - If a dynamic SFI is set, □ A UE with a dynamic grant may consider dynamic DL symbols as unavailable. □ A UE with a configured grant processes the TBoMS transmission as if there was no dynamic SFI. If some of the symbols scheduled by the configured grant are indicated as DL by the dynamic SFI, the UE cancels the transmission in either the CBG or the slot or the conflicting symbol.

[0244] Embodiment 7, the UE capability for transmission across multiple slots for TB may be one or more of the following: Whether frequency hopping is applied across slots Whether the power allocation is the same across slots · Whether the slots are contiguous or how large the gap is between two of the slots in a set of multiple slots. Phase coherency across multiple slots Type A or Type B, slot-based or symbol-based, option 1 and option 2

[0245] In a sub-embodiment of embodiment 7, one or more of the above capabilities may depend on one or more of the other above capabilities.

[0246] 3.2 Type-A TBoMS transmission and slot-based Type-B TBoMS transmission For both Type-A TBoMS transmission and slot-based Type-B TBoMS transmission, two options may be applied with respect to N as a physical slot or an available slot.

[0247] In embodiment 1, for both Type A TBoMS transmission and slot-based Type B TBoMS transmission, if N slots are configured for TBoMS transmission and TBoMS starts from slot n, one or more of the following methods may be used to determine the number of slots to be used for TB. - Option 1, TB ends in slot n+K-1. - Option 2: If a slot has only a portion of the L scheduled symbols available for the UE, the slot is not counted. Only slots where all L scheduled symbols are available are counted until N slots are found. - NOTE: L is not set for slot-based Type B TBoMS transmission. In Option 2 for slot-based Type B TBoMS transmission, for multiple slots other than the first slot, L = 14. For the first slot, L = 14-S. - For both options 1 and 2, □ If only a portion of the L scheduled symbols in a slot from the first slot to the last slot are available for TB, it can be set or predetermined in the specifications whether the UL symbol in that slot can be used or not. ■ The UE may be RRC / DCI configured or predefined with X1, i.e., the minimum number of adjacent UL symbols among the L scheduled symbols in a slot that may be used for TB. Slots with fewer than X1 UL symbols are not used for TB. If X1=1, all UL symbols (fewer than L in number) in a slot may be used. If X1=L, slots with fewer than L adjacent symbols are not used. If X1 is not configured, a default value may be predefined, e.g., X1=L. ■ If the UE is configured to use UL symbols in slots with fewer than L adjacent symbols for TBoMS transmission, one or more of the following ways may be configured. UL symbols in a slot carry new information bits and are counted in the TBS determination. UL symbols in a slot are symbol-by-symbol repetitions of the same symbol in the previous or subsequent or particular slot, e.g., the first slot. That is, the transmission in the slot uses the same Redundancy Version (RV) as that slot. These UL symbols are not counted in the TBS determination.

[0248] An example of option 1 of Type A TBoMS transmission is shown in Figure 7. In the upper part of the figure, each slot from slot n to slot n+N-1 has at least L adjacent available symbols, and the UE uses the same L symbols in each of the N slots. The lower part of the figure shows that there are fewer than L adjacent available UL symbols in slot n+1. If X1=1, the UL symbol in slot n+1 may be used for TB. The UE is configured to transmit the same bit as in the same symbol in the previous slot. In option 1, the TB consists of at most L*N UL symbols.

[0249] An example of option 2 for Type A TBoMS transmission is shown in Figure 8. In slot n+1, there are fewer than L adjacent available UL symbols, and slot n+1 is not counted as an available slot. If X1=1, the UL symbol in slot n+1 can be used for TB, but slot n+1 is not counted as an available UL symbol. The UE is configured to transmit the same bit in the symbol of slot n+1 as in the same symbol in the previous slot. The last available slot is postponed until slot n+K. In option 2, the TB consists of at least L*N UL symbols.

[0250] In TDD configuration DDDSUDDDSU, the UE is scheduled with TBoMS transmission starting from the first UL slot in a radio frame. For slot-based Type B TBoMS transmission option 1 and K=6, the TBoMS transmission will traverse six slots, i.e., UDDDSU. For option 2 and K=2, the TB also spans UDDDSU until two UL slots are found, as shown in Figure 9. There are four UL symbols in the special slot. If X1>4, the UL symbols in the special slot are not used.

[0251] 3.3 Symbol-based Type-B TBoMS Transmission Resource allocation for Type-B TBoMS transmissions can be slot-based or symbol-based. Slot or symbol is the time domain scheduling granularity. The slot-based option has a TB that ends at a slot boundary, while the symbol-based option means that the gNB schedules a certain number of symbols across multiple slots for a TB. The symbol-based option can have a TB end in the middle of a slot. The slot-based option is configured with N slots, either physical slots or available slots. The symbol-based option uses L symbols, either physical symbols or available symbols.

[0252] Embodiment 1, a symbol-based Type-B TBoMS transmission spans L symbols in multiple slots of a TB.

[0253] Here, L symbols is the total number of UL symbols across the slots scheduled for TB transmission.

[0254] In one sub-embodiment of embodiment 1, for symbol-based resource allocation, the UE needs to be configured with S and L for symbol-based Type B TBoMS transmission. S is the starting symbol in the first slot of multiple slots for TB. L is the number of symbols for TBoMS. N is not configured. One or more of the following methods may be used to determine the symbol to be used for TB. - Option 1, TB spans L symbols and ends after symbol S+L-1. - Option 2, the TB ends after the Lth available UL symbol.

[0255] The S and L definitions for symbol-based Type B TBoMS transmissions can also be found in Table 3.5-1.

[0256] In another sub-embodiment of embodiment 1, in symbol-based Option 1 and Option 2, if a slot has less than 14 available UL symbols, the UE may be RRC / DCI configured or predefined with X1, i.e., the minimum number of contiguous UL symbols in a slot to be used. If X1 is not configured, a default value may be predetermined, e.g., 14. If the UE is configured to use the [X1,14) UL symbol in slots for TBoMS other than the first slot, one or more of the following ways may be configured: □ UL symbols in a slot carry new information bits and are counted in the TBS decision. These symbols are counted as available symbols for option 2. □ UL symbols in a slot are symbol-by-symbol repetitions of the same symbol in the previous or subsequent or particular slot, e.g., the first slot. That is, the transmission in the slot uses the same RV as that slot. These UL symbols are not counted in the TBS determination. These symbols are counted as unavailable symbols for option 2.

[0257] 3.4 PUSCH mapping types In Rel-15 / 16, PUSCH mapping type A or B is configured for PUSCH transmission in a slot with respect to valid S and L combinations, DM-RS positions in a slot with intra-slot frequency hopping enabled, etc. PUSCH mapping type A has at least 4 UL symbols in a slot. Also, PUSCH mapping type A or B needs to be configured for TBoMS transmission.

[0258] Embodiment 1, Type A For TBoMS transmission, either PUSCH mapping type A or B can be configured. All available scheduled L symbols in the TB slots should conform to the configured PUSCH mapping type.

[0259] In a sub-embodiment of embodiment 1, when the UE is configured to carry new information in fewer than L UL symbols in a slot for TBoMS, one or more ways may be applied. - A slot may use a corresponding number of symbols of type B regardless of the number of UL symbols in the slot. - If a slot has at least 4 adjacent UL symbols, the slot still uses PUSCH mapping type A, except that the reference point for the PUSCH length and the DMRS position(s) are defined with respect to the start of the scheduled PUSCH resource in the slot. If a slot has less than four adjacent UL symbols, the DMRS configuration may be configured or predefined separately, e.g., the slot has no DMRS in it.

[0260] Embodiment 2, Type B For TBoMS transmission, PUSCH mapping type B may be configured. The DMRS position in each of multiple slots of a TB depends on the number of adjacent UL symbols in the slot.

[0261] In a sub-embodiment of embodiment 2, the effective L for PUSCH mapping Type B for symbol-based Type-B TBoMS transmission may be greater than 14 for normal CP and greater than 12 for extended CP.

[0262] Embodiment 3, frequency hopping is supported for TBoMS and may include one or more of the following options: - Intra-slot frequency hopping - Inter-slot frequency hopping - Inter-bundle frequency hopping. □ Several slots of a TB can form a bundle and use the same hop.

[0263] For example, if two bundles are configured for a TB spanning eight slots, the first four slots will use one hop and the last four slots will use another hop.

[0264] In a sub-embodiment of embodiment 3, whether frequency hopping is applied for PUSCH transmission in slots with less than a certain number of symbols may be configured or predefined.

[0265] In one example, PUSCH transmission in a slot with at least a minimum number of OFDM symbols is required for intra-slot frequency hopping, otherwise intra-slot frequency hopping is not enabled, to avoid hops with too short length.

[0266] In another example, if PUSCH mapping type A is configured for TBoMS, slots with fewer than four adjacent UL symbols are not needed for intra-slot frequency hopping.

[0267] 3.5 Signaling on Time Domain Resources of TBoMS Transmission In the first embodiment, for TBoMS transmission, the UE may be configured with one or more of the following parameters by RRC / DCI signaling: - TBoMS transmission type, Type A or Type B - Resource Allocation Options □ Type A TBoMS transmission, option 1 or option 2 ■ Starting symbols in multiple slots, number of adjacent UL symbols in a slot, number of slots for TB transmission □ Type B TBoMS transmission, ■ Slot-based, option 1 or option 2 Starting symbol in the first slot, number of slots for TB transmission ■ Symbol-based, option 1 or option 2 Starting symbol in the first slot, the number of symbols for TB transmission

[0268] Type-A TBoMS transmission and slot-based Type-B TBoMS transmission, options 1 and 2 are defined in embodiment 1 in section 3.2. Symbol-based Type-B TBoMS transmission, options 1 and 2 are defined in embodiment 1 in section 3.3.

[0269] The parameters to be set for each type of TBoMS transmission and the corresponding setting method can be summarized in Table 3.5-1. S and L have different meanings in different types of TBoMS transmission and the setting method can be reused in Rel-15 / 16. N for Type A TBoMS transmission and slot-based Type B TBoMS transmission needs to be set. Table 3.5-1 TBoMS transmission parameter specifications and setting methods TIFF0007676559000020.tif61170

[0270] In one sub-embodiment of embodiment 1, the number of slots of the TBoMS, N, may be indicated in one or more of the following ways. Alternative 1:N can be signaled by a new DCI field Alternative 2:N may be added to the TDRA table and jointly coded with the TDRA field in the DCI. Alternative 3: N may be RRC configured. This may be used for configured grant type 1.

[0271] An example of alternative 2 is given below.

[0272] PUSCH-Time Domain Resource Allocation Information Element JPEG0007676559000021.jpg135170

[0273] In another sub-embodiment of embodiment 1, a valid L for a symbol-based Type-B TBoMS may be in the range of {1, ..., maximum symbol of TBoMS}, where the maximum symbol of TBoMS may be greater than 14 for normal CP and greater than 12 for extended CP, as shown in Table 3.5-2. Table 3.5-2 Valid S and L Combinations TIFF0007676559000022.tif103170

[0274] 3.6 PUSCH Repetition Extends to TBoMS Transmission Rel-15 / 16 PUSCH repetition allows for multi-slot transmission of a single transport block, where different redundancy versions (RVs) of the PUSCH are transmitted in different slots. The multi-slot transport block transmission contemplated by the present invention differs from Rel-15 / 16 PUSCH transmission in that the transport block size is determined based on multiple slots, but the Rel-15 / 16 repetition TBS is calculated assuming that the entire transport block is carried in each slot. The benefit of determining the TBS of the TBoMS from all slots occupied by the TB is that the TBS grows with the number of slots, thus allowing larger transmissions for a given code rate with multi-slot transmission without reducing reliability, and at the same time avoiding the extra overhead of a CRC check in each slot, since there is only one CRC check per TB.

[0275] Rel-15 / 16 repetition includes a wide set of mechanisms for determining which time domain resources are used. These include how to determine the resources allocated to each repetition, the total number of repetitions, and which slots are omitted and / or which symbols are disabled. TBoMS transmission also requires a mechanism for determining the time domain resources. Therefore, one way to reduce the complexity in UEs that already support PUSCH repetition is to construct the TBoMS transmission by combining the PUSCH repetition time domain resource determination mechanism with a multi-slot transport block construction method.

[0276] As explained above, in rel-15 / 16, the transport block size is Determined according to TIFF0007676559000023.tif8170, where: TIFF0007676559000024.tif7170 is the number of symbols of PUSCH allocation in a slot. This implies that TBS is proportional to the number of symbols in a slot and that TBS cannot be increased by increasing the number of slots. However, If TIFF0007676559000025.tif7170 is redefined as the number of symbols of PUSCH allocation in all slots in which a given transport block is carried, TBoMS can grow with the number of slots. Furthermore, since a TB may not be completely contained within a single slot of a TBoMS transmission, and since a CRC check of the entire TB requires the UE to receive the entire TB, a single CRC is added to the TB, which is used after receiving the entire TB. Since TBoMS transmissions are generally motivated by the need for increased coverage of low data rates, it follows that only one TB may be transmitted in a TBoMS transmission, and adding a CRC for each slot of a multi-slot transmission made for Rel-15 / 16 PUSCH repetition may increase overhead without improving net performance. Thus, in some embodiments, a single CRC check is transmitted in a TBoMS transmission.

[0277] In some embodiments, the mapping of PUSCH modulation symbols to REs depends directly on the number of coded bits for the transport block carried by the PUSCH. For example, 3GPP TS38.211 V16.3.0, section 6.1.3.6 states: TIFF0007676559000026.tif 7170 modulation symbols TIFF0007676559000027.tif7170 is mapped to resource elements on antenna port p, where: TIFF0007676559000028.tif8170 is the number of modulation symbols per layer, TIFF0007676559000029.tif8170, where: TIFF0007676559000030.tif7170 is the number of coded bits in the transport block carried in PUSCH codeword q, and Qm is the number of coded bits per modulation symbol, where Qm is the number of symbols in the PUSCH allocation in all slots in which a given transport block is carried. By redefining TIFF0007676559000031.tif7170, the mapping of PUSCH modulation symbols to REs does not need to be changed when the TBS for TBoMS transmission is determined.

[0278] In one embodiment, the TBoMS transmission determines the time domain resource allocation (TDRA) according to Rel-15 / 16 PUSCH repetition type A as specified in 3GPP TS38.214 V16.3.0. The starting symbol S and the number of consecutive symbols L in each slot are calculated as described in Section 6.1.2.1 for repetition type A. In an embodiment, a portion of the TB is carried in each slot, unlike Rel-15 and Rel-16 PUSCH repetition type A, where the entire TB is encoded in each slot. Since only a portion of the TB is carried, the number of symbols L is the total number of symbols occupied by the TB in all of the slots in which the TB is carried. TIFF0007676559000032.tif7170. Also, since S and L are the same for each slot with this use of PUSCH repetition type A TDRA, the total number of symbols occupied by the PUSCH in this case is TIFF0007676559000033.tif7170. Furthermore, in one such embodiment, slots for TBoMS are omitted in the same manner as for PUSCH repetition type A, in accordance with the requirements of clause 11.1 of 3GPP TS38.213.

[0279] In one embodiment, the TBoMS transmission determines the time domain resource allocation (TDRA) according to Rel-15 / 16 PUSCH repetition type B as specified in 3GPP TS38.214 V16.3.0. In this embodiment, the TBoMS comprises K segments, each of which is contiguous and L symbols long. Then, the maximum total number of symbols occupied by the PUSCH when all segments are transmitted with L symbols is TIFF0007676559000034.tif7170. The starting symbol S, the number of consecutive symbols L, and the starting and ending slots for each segment are calculated as described in section 6.1.2.1 for repetition type B, where the starting and ending slots for the nth segment are calculated in the same manner as for the nth nominal repetition of PUSCH repetition type B. In some embodiments, the UE determines the invalid symbols for TBoMS transmission according to the procedure used for PUSCH repetition type B given in 3GPP TS38.214 V16.3.0, section 6.1.2.1. In some embodiments, the UE determines the potentially valid symbols for TBoMS transmission and which segments of the multi-slot transmission are to be transmitted according to the procedure used for PUSCH repetition type B given in 3GPP TS38.214 V16.3.0, section 6.1.2.1, and the segment to be transmitted, which may be labeled "actual segment", is identified according to the method used to determine the actual transmission. In some embodiments, the actual segment is omitted according to the conditions in 3GPP TS38.213 V16.3.0, clause 11.1.

[0280] In a more general embodiment, the UE determines the size of the transport block according to the number of symbols to be occupied by the PUSCH carrying the transport block, where the number of symbols is the number of OFDM symbols occupied by the PUSCH, where the PUSCH occupies multiple slots. The UE determines the symbols to be occupied by the PUSCH according to a PUSCH repetition procedure. In some embodiments, the UE determines whether to transmit a PUSCH in a slot according to a PUSCH repetition procedure. The UE then encodes the transport block with an error correction code to form a coded transport block and transmits the coded transport block in the PUSCH in the symbols to be occupied in the multiple slots. In some embodiments, the PUSCH repetition procedure is one of PUSCH repetition type A or type B as specified in 3GPP TS38.214 V16.3.0. In some embodiments, the number of symbols is The image is determined as TIFF0007676559000035.tif7170, where: TIFF0007676559000036.tif7170 is the number of consecutive OFDM symbols occupied by the PUSCH, and K is one of the number of repetitions determined according to the PUSCH repetition procedure and the number of slots that the PUSCH is set to occupy.

[0281] Referring to Fig. 10, according to one embodiment, a communication system includes a communication network 2510, such as a 3GPP type cellular network, comprising an access network 2511, such as a wireless access network, and a core network 2514. The access network 2511 comprises a number of base stations 2512a, 2512b, 2512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2513a, 2513b, 2513c. Each base station 2512a, 2512b, 2512c can be connected to the core network 2514 via a wired or wireless connection 2515. A first UE 2591 located in the coverage area 2513c is configured to wirelessly connect to the corresponding base station 2512c or to be paged by the corresponding base station 2512c. A second UE 2592 in the coverage area 2513a can be wirelessly connected to the corresponding base station 2512a. Although multiple UEs 2591, 2592 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in a coverage area or where only one UE is connected to a corresponding base station 2512.

[0282] The communication network 2510 is itself connected to a host computer 2530, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 2530 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. The connections 2521 and 2522 between the communication network 2510 and the host computer 2530 may extend directly from the core network 2514 to the host computer 2530, or may proceed through an optional intermediate network 2520. The intermediate network 2520 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 2520 may be a backbone network or the Internet, if any, and in particular the intermediate network 2520 may comprise two or more sub-networks (not shown).

[0283] The communication system of FIG. 10 as a whole enables connectivity between connected UEs 2591, 2592 and a host computer 2530. The connectivity may be described as an over-the-top (OTT) connection 2550. The host computer 2530 and connected UEs 2591, 2592 are configured to communicate data and / or signaling via the OTT connection 2550 using the access network 2511, the core network 2514, any intermediate networks 2520 and possible further infrastructure (not shown) as intermediaries. The OTT connection 2550 may be transparent in the sense that the participating communication devices through which the OTT connection 2550 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 2512 may not be or need not be informed of the past routing of incoming downlink communications involving data originating from the host computer 2530 to be forwarded (e.g., handed over) to the connected UE 2591. Similarly, the base station 2512 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 2591 and destined for the host computer 2530 .

[0284] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 11. In the communication system 2600, the host computer 2610 comprises hardware 2615 including a communication interface 2616 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 2600. The host computer 2610 further comprises a processing circuit 2618, which may have storage and / or processing capabilities. In particular, the processing circuit 2618 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 2610 further comprises software 2611, which is stored in or accessible by the host computer 2610 and is executable by the processing circuit 2618. The software 2611 includes a host application 2612. The host application 2612 may be operable to provide services to a remote user, such as a UE 2630 connecting via an OTT connection 2650 that terminates at the UE 2630 and the host computer 2610. In providing services to the remote user, the host application 2612 may provide user data that is transmitted using the OTT connection 2650.

[0285] The communication system 2600 further includes a base station 2620 provided in the communication system, the base station 2620 comprising hardware 2625 enabling the base station 2620 to communicate with the host computer 2610 and the UE 2630. The hardware 2625 may include a communication interface 2626 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 2600, as well as a wireless interface 2627 for setting up and maintaining at least a wireless connection 2670 with a UE 2630 located in a coverage area (not shown in FIG. 11 ) served by the base station 2620. The communication interface 2626 may be configured to facilitate a connection 2660 to the host computer 2610. The connection 2660 may be direct or alternatively the connection 2660 may pass through a core network (not shown in FIG. 11 ) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 2625 of the base station 2620 further includes processing circuitry 2628, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 2620 further has software 2621 stored internally or accessible via an external connection.

[0286] The communication system 2600 further includes the UE 2630 already mentioned. The hardware 2635 of the UE 2630 may include a wireless interface 2637 configured to set up and maintain a wireless connection 2670 with a base station serving a coverage area in which the UE 2630 is currently located. The hardware 2635 of the UE 2630 further includes a processing circuit 2638, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 2630 further includes software 2631 stored in or accessible by the UE 2630 and executable by the processing circuit 2638. The software 2631 includes a client application 2632. The client application 2632, with the support of the host computer 2610, may be operable to provide services to a human or non-human user via the UE 2630. At the host computer 2610, a running host application 2612 may communicate with a running client application 2632 via an OTT connection 2650 that terminates at the UE 2630 and the host computer 2610. In providing services to a user, the client application 2632 may receive request data from the host application 2612 and provide user data in response to the request data. The OTT connection 2650 may transfer both the request data and the user data. The client application 2632 may interact with the user to generate the user data that the client application 2632 provides.

[0287] It should be noted that the host computer 2610, base station 2620 and UE 2630 shown in Figure 11 may be similar or equivalent to the host computer 2530, one of the base stations 2512a, 2512b, 2512c, and one of the UEs 2591, 2592, respectively, of Figure 10. That is, the inner workings of these entities may be as shown in Figure 11, and separately, the surrounding network topology may be that of Figure 10.

[0288] 11, the OTT connection 2650 is depicted abstractly to show communication between the host computer 2610 and the UE 2630 via the base station 2620, without explicit reference to intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 2630 or from the service provider operating the host computer 2610, or both. While the OTT connection 2650 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0289] The wireless connection 2670 between the UE 2630 and the base station 2620 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2630 using the OTT connection 2650 of which the wireless connection 2670 forms the last segment. More precisely, the teachings of these embodiments may improve radio resource utilization, thereby providing benefits such as reduced user latency.

[0290] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 2650 between the host computer 2610 and the UE 2630 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 2650 may be implemented in the software 2611 and hardware 2615 of the host computer 2610 or in the software 2631 and hardware 2635 of the UE 2630, or both. In an embodiment, sensors (not shown) may be deployed in or in association with the communication devices through which the OTT connection 2650 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 2611, 2631 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2650 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 2620, and the reconfiguration may be unknown or imperceptible to the base station 2620. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 2610 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 2611 and 2631 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2650 while the software 2611 and 2631 monitors propagation times, errors, etc.

[0291] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 12 are included in this section. In step 2710, the host computer provides user data. In sub-step 2711 of step 2710 (which may be optional), the host computer provides the user data by executing a host application. In step 2720, the host computer initiates a transmission carrying the user data to the UE. In step 2730 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 2740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0292] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 13 are included in this section. In step 2810 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2820, the host computer initiates a transmission carrying the user data to the UE. The transmission may go through a base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 2830 (which may be optional), the UE receives the user data carried in the transmission.

[0293] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 14 are included in this section. In step 2910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2920, the UE provides user data. In sub-step 2921 (which may be optional) of step 2920, the UE provides the user data by executing a client application. In sub-step 2911 (which may be optional) of step 2910, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 2930 (which may be optional). In method step 2940, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0294] FIG. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 15 are included in this section. In step 3010 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 3020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0295] The present disclosure has been described above with reference to the embodiments of the present disclosure. It should be understood that various modifications, alterations and additions may be made by those skilled in the art without departing from the spirit and scope of the present disclosure. Therefore, the scope of the present disclosure is not limited to the above specific embodiments, but is defined only by the appended claims.

Claims

1. A method (100) in a network device, comprising: determining (s110) a configuration for a terminal device for transmitting a transmission block (TB), the configuration indicating at least a transmission mode in which a single TB is transmittable over two or more slots; transmitting (s120) said configuration to said terminal device; receiving (s130) the TB transmitted from the terminal device according to the setting; Including, The method (100), wherein when a Type A TB over multiple slots (TBoMS) transmission is indicated in the configuration, the configuration includes parameters S, L, and N, a group of N slots starting with a first slot are used by the terminal device in transmitting the TB, each slot of the group has at least L contiguous available symbols starting with a symbol indicated by S, and L contiguous available symbols starting with a symbol indicated by S in each slot of the group are used by the terminal device in transmitting the TB.

2. 2. The method of claim 1, wherein the configuration further includes a parameter X1 indicating a minimum number of contiguous available symbols starting from the symbol indicated by S in each slot, and an available symbol in any slot prior to the last slot of the group that is not included in the group and has X1 or more contiguous available symbols starting from the symbol indicated by S is used by the terminal device in transmitting the TB.

3. 3. The method of claim 2, wherein the available symbols starting from the symbol indicated by S in any slot prior to the last slot of the group that is not included in the group and has X or more adjacent available symbols is a symbol-by-symbol repetition of the symbols in a particular slot of the group.

4. The parameter N is - N is signaled by a new Downlink Control Information (DCI) field; - N is added to the Time Domain Resource Allocation (TDRA) table and jointly coded with the TDRA field in the DCI, or - N is configured in the radio resource control (RRC) The method of claim 1 , wherein the method is instructed by one or more of:

5. The method of claim 1 , wherein the transmission of the TB is scheduled with a dynamic grant or a configured grant.

6. 2. The method of claim 1, wherein when a dynamic SFI is not configured, whether a semi-static flexible symbol in any slot configured for transmitting the TB is an available symbol is configured or predetermined by RRC / DCI.

7. A method (200) in a terminal device, comprising: Obtaining (s210) a configuration for transmitting a transmission block (TB) from a network device, the configuration indicating at least a transmission mode in which a single TB can be transmitted over two or more slots; determining (s220) resources for transmitting said TB according to said configuration; transmitting (s230) the TB to the network device over the determined resources; and Including, The method (200), wherein when a Type A TB over multiple slots (TBoMS) transmission is indicated in the configuration, the configuration includes parameters S, L, and N, a group of N slots starting from a first slot are used by the terminal device in transmitting the TB, each slot of the group has at least L contiguous available symbols starting from a symbol indicated by S, and L contiguous available symbols starting from the symbol indicated by S in each slot of the group are used by the terminal device in transmitting the TB.

8. A network device comprising a transceiver, a processor and a memory, the memory comprising instructions executable by the processor, whereby the network device is operable to perform a method according to any one of claims 1 to 6.

9. A terminal device comprising a transceiver, a processor and a memory, said memory comprising instructions executable by said processor, whereby said terminal device is operable to perform the method of claim 7.

Images