Signaling for repetition

Abstract

There is a method performed by a wireless device WD. The method includes a WD receiving a control message, the control message including an indication of an index value. The method further includes the WD obtaining a parameter set from time domain resource allocation (TDRA) configuration information using the index value, the parameter set including an aggregation factor.

Description

Technical Field

[0001] The present disclosure relates to repeated signaling in a communication network. Background Art

[0002] Generally, all terms used herein, unless clearly given and / or different meanings are implied from the context in which it is used, will be interpreted according to their common meanings in the relevant technical field. Unless otherwise clearly stated, all references to one / an / the element, equipment, assembly, parts, step, etc. will be openly interpreted as referring to at least one instance of the element, equipment, assembly, parts, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless the steps are clearly described as after or before another step and / or the implicit steps must be after or before another step. In any appropriate case, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. From the following description, other purposes, features and advantages of the attached embodiments will be apparent. From the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0003] In 5G New Radio (NR) Release 15, timeslot aggregation is supported for both downlink (DL) and uplink (UL) transmissions, which is beneficial for enhancing coverage and improving reliability. With timeslot aggregation, physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) transmissions can be repeated in multiple timeslots when the radio resource control (RRC) parameters for timeslot aggregation are configured. The corresponding RRC parameters are called pdsch-AggregationFactor, pusch-AggregationFactor, repK of PDSCH, PUSCH based on grant, and PUSCH without grant, respectively. The following table lists the relevant information elements (IEs) from TS 38.331 to illustrate the use of these parameters.

[0004] Table 1 When a user equipment (UE) is scheduled for PDSCH transmission in a given timeslot by DL assignment or DL ​​semi-persistent scheduling (SPS), if the aggregation factor is configured to have a value greater than 1, the signaled resource allocation for PDSCH is used for the number of consecutive timeslots. In this case, the PDSCH is repeated with different redundancy versions in those timeslots used for transmission of the corresponding transport block. The same procedure applies to the UL, where the UE is scheduled for PUSCH transmission in a timeslot by UL assignment or without grant and is configured for timeslot aggregation. In this case, the UE uses different redundancy versions for transmission of the corresponding TB, using the signaled resource allocation in multiple timeslots given by the aggregation factor.

[0005] In NR Rel-1 5, the time domain resource allocation (TDRA) information for PDSCH transmission in a time slot includes information that allows the UE to determine the time slot (also known as K0) in which it is expected to receive PDSCH, the starting symbol in the time slot for PDSCH reception, and the length or duration (also known as SLIV) of the PDSCH reception. The UE is also provided with a mapping type for determining the location of the demodulation reference signal (DMRS). In NR, there are designated TDRA tables consisting of different combinations of K0, SLIV, etc. The UE can be signaled an index to a row in the table that provides information about the K0 and SLIV to be used for reception.

[0006] A similar process applies for PUSCH transmissions, where the timeslot intended for PUSCH transmission is obtained from a field in the UL allocation given by K2. SLIV information is similarly provided by the UL assignment and / or configuration as for DL ​​reception and mapping type.

[0007] TDRA is a time domain resource allocation for the first time instant of PDSCH reception or PUSCH transmission. As described above, if the UE is configured with an aggregation factor, the transmission in the time slot is repeated in multiple time slots based on the aggregation factor.

[0008] The following table lists the relevant information elements (IEs) from TS 38.331 to illustrate the use of these parameters.

[0009] Table 2 Table 3 Table 4 Table 5 In addition to the RRC configuration of time domain resource allocation for PDSCH and PUSCH, several default TDRA tables are defined for PDSCH and PUSCH respectively. The default tables may be used when PDSCH reception or PUSCH transmission is required before RRC connection, such as during initial access.

[0010] In LTE, a UE can be configured with different repetition factors or slot aggregations. However, the UE is dynamically indicated with the repetition factor or slot aggregation factor using a field in the downlink control information (DCI). The number of slots can be configured from the set {2, 4, 8}.

[0011] In LTE Rel-14, a PUSCH enhancement feature was introduced, in which the use of PUSCH repetitions is dynamically configured (via DCI), and the number of repetitions that can be used is extended from 4 to the set {1, 2, 4, 8, 16, 32}.

[0012] There are currently certain challenges. Semi-static signaling of the number of transmissions configured by RRC, such as the slot aggregation factor, applies to all transmissions and therefore makes it impossible to apply different numbers of repetitions to different transmissions with different reliability and latency requirements.

[0013] Additionally, an explicit field in the DCI, as used in LTE to signal the number of repetitions, makes the DCI payload larger. This has the effect of making PDCCH transmissions less reliable when using the same aggregation level. As a result, the gNB may need to use a larger aggregation level, which makes the risk of PDCCH blocking greater and uses more radio resources. Such a field in the DCI also applies to all possible resource allocations, and some combinations are less likely to be used since other combinations achieve similar total transmission lengths. For example, a 7-symbol transmission consisting of two transmissions in total may be scheduled using one 14-symbol transmission. Summary of the invention

[0014] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. According to some aspects of the present disclosure, with respect to the default TDRA table, the current TDRA table is extended to also include a column for the number of repetitions and / or a column for the DMRS configuration. According to some aspects of the present disclosure, for a non-default TDRA configuration, the aggregation factor is made part of the TDRA configuration so that the DCI index of the TDRA table also obtains information about the aggregation factor.

[0015] Various embodiments are presented herein that address one or more of the issues disclosed herein.

[0016] According to one embodiment, a method for repeated signaling performed by a wireless device is provided. The method includes the step of receiving a control message, the control message including an indication of an index value. The method further includes the step of obtaining a parameter set from a time domain resource allocation (TDRA) configuration information using the index value, the parameter set including an aggregation factor. In some embodiments, a wireless device for repeated signaling is provided, and the wireless device includes a processing circuit configured to perform the method.

[0017] According to another embodiment, a method for repeated signaling performed by a base station is provided. The method includes the step of generating a configuration message, the message including time domain resource allocation (TDRA) configuration information, the TDRA configuration information including an aggregation factor. The method also includes the step of transmitting the configuration message to a wireless device. In some embodiments, a base station for repeated signaling is provided, and the base station includes a processing circuit configured to perform the method.

[0018] Certain embodiments may provide one or more of the following technical advantages. By extending the TDRA table, no additional DCI fields are introduced, thereby keeping the DCI payload small. Only relevant combinations of time domain resources and repetition factors will be configured. As an example, a combination of 7-symbol transmission and repetition factor two will not be configured. In addition, by extending the TDRA table with a specific DMRS configuration for each duration and repetition factor, the DMRS configuration can be tuned to the exact transmission length and quantity, thereby reducing DMRS overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate various embodiments.

[0020] Figure 1 is an example of repeated signaling according to some embodiments.

[0021] Figure 2 is a wireless network according to some embodiments.

[0022] Figure 3 is a user equipment according to some embodiments.

[0023] Figure 4 is a schematic block diagram illustrating a virtualization environment according to some embodiments.

[0024] Figure 5 is a communication system according to some embodiments.

[0025] Figure 6 Example implementations of user equipment, base stations, and host computers are shown in accordance with some embodiments.

[0026] Figure 7is a flow chart illustrating a method implemented in a communication system according to some embodiments.

[0027] Figure 8 is a flow chart illustrating a method implemented in a communication system according to some embodiments.

[0028] Fig. 9 is a flow chart illustrating a method implemented in a communication system according to some embodiments.

[0029] Fig.10 is a flow chart illustrating a method implemented in a communication system according to some embodiments.

[0030] Fig.11 is a flow diagram for repeated signaling according to some embodiments.

[0031] Fig.12 is a flow diagram for repeated signaling according to some embodiments.

[0032] Fig.13 is a schematic block diagram of an apparatus according to some embodiments.

[0033] Fig.14 is a schematic block diagram of an apparatus according to some embodiments.

[0034] Fig.15 Long alignment delays due to transmission restrictions across slot boundaries are shown in accordance with some embodiments.

[0035] Fig.16 Slot aggregation when applied to repetition of short transmissions according to some embodiments is shown.

[0036] Fig.17 A double-repetition PUSCH transmission is shown according to some embodiments.

[0037] Fig.18 Blocking probability is shown as a function of number of UEs, DCI size and CORESET size according to some embodiments.

[0038] Fig.19 The downlink data latency for one retransmission according to some embodiments is shown.

[0039] Fig. 20 Uplink data latency with configuration grant and one retransmission is shown in accordance with some embodiments. DETAILED DESCRIPTION

[0040] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the appendix.

[0041] In one non-limiting embodiment, the TDRA table is extended to include a column containing an aggregation factor. This aggregation factor works similarly to the slot aggregation factor in current NR, i.e., repeating transmissions in the same symbol and frequency resources in different slots.

[0042] In one non-limiting embodiment, the aggregation factor indicates the number of transmissions that will be repeated back-to-back. For example, a transmission occupying symbols 0 and 1 with an aggregation factor of four will be transmitted four times in the same time slot in symbols 0-1, 2-3, 4-5, and 6-7. The same frequency resources may be used for repeated back-to-back transmissions. If frequency hopping is enabled, the frequency resources used for each repeated transmission follow the frequency allocation as a result of the frequency hopping.

[0043] In one non-limiting embodiment, there is an additional field that indicates whether slot aggregation is used or back-to-back repetitions are performed.

[0044] In one non-limiting embodiment, time slot aggregation is used for one set of transmission durations and back-to-back is used for repetition for another set of transmission durations. For example, if the duration L<=7, then back-to-back repetitions may be performed, otherwise time slot aggregation is used. In this case, the indicated repetition factor may indicate back-to-back repetitions (L<=7) and additionally indicate the number of repetition time slots.

[0045] In one non-limiting embodiment, if Type A scheduling is used, the repetition is performed using slot aggregation, and if Type B scheduling is used, the repetition is performed using back-to-back.

[0046] In one non-limiting embodiment, if Type B scheduling is used, the repetition is performed using slot aggregation, and if Type A scheduling is used, the repetition is performed using back-to-back.

[0047] In one non-limiting embodiment, if back-to-back repetitions would result in some transmissions at least partially occupying different time slots than the first transmission, the transmissions occupying different time slots are discarded, ie, not transmitted.

[0048] In one non-limiting embodiment, if a transmission in a back-to-back repetition that covers two time slots is not discarded but shortened so that it does not cover two time slots. In some such embodiments, a selection is made to transmit the shortened transmission before or after the time slot based on the number of symbols before or after the time slot. For example, if the length of the shortened transmission before the time slot is greater than the length of the shortened transmission after the time slot, then the shortened transmission is sent before the time slot, otherwise the shortened transmission is sent after the time slot.

[0049] In one non-limiting example, the resource allocation is repeated back-to-back as often as possible within a time slot without crossing time slot boundaries. In (one or more) subsequent time slots, the same process is applied until the resource allocation is repeated as frequently as indicated. The repetition factor may indicate the number of separate repetitions or the number of time slots over which the resource allocation should be repeated.

[0050] In one non-limiting embodiment, if back-to-back repetitions would result in a transmission occupying two time slots, then the particular transmission occupying two time slots is discarded. Other transmissions are not discarded.

[0051] In one non-limiting embodiment, the TDRA table is extended to include a field containing a DMRS presence configuration. This field indicates in which aggregate transmission the DMRS is present.

[0052] In another embodiment, the DMRS presence configuration field indicates the number of DMRS present in the total aggregate transmission. How the DMRS exist follows specific rules, for example, the first DMRS exists in the first repetition and the remaining DMRS are evenly distributed across the repetitions. If, according to some of the above embodiments, a DMRS exists in a discarded transmission, the DMRS can be moved to exist in the next repetition. Instead of configuring the total number of DMRS, the maximum duration between two DMRSs is configured (measured in absolute time or symbols or samples). Another alternative is to reuse the dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB configurations that specify the number of additional DMRSs per time slot.

[0053] In another embodiment, the DMRS preference configuration field indicates the presence or absence of a DMRS that follows a mapping type in a repetition. In a first example, the entry for the presence of DMRS indicates that the DMRS exists in the first repetition in frequency hopping after the mapping type of the PUSCH or PDSCH, respectively. However, in subsequent repetitions of frequency hopping, the DMRS does not exist, and the corresponding RE is used for data transmission. In the absence of frequency hopping, the DMRS exists in the first repetition after the corresponding mapping type, and it does not exist in subsequent repetitions. In another example, the number of bits can be increased to the number of repetitions to indicate whether the DMRS exists for each repetition based on the mapping type. This can be extended to apply the presence indicator to half repetitions or quarter repetitions, etc. In a non-limiting embodiment, the TDRA table is extended to include a field containing a redundant version sequence. The redundant version sequence indicates which transmission uses which redundant version, and if the length of the redundant version sequence is shorter than the number of repetitions, it is repeated in a cyclic manner.

[0054] In one non-limiting embodiment, the redundancy version is selected from (0,0,0,0), (0,3,0,3), or (0,2,3,1).

[0055] In one non-limiting embodiment, the TDRA table is extended to include a field containing a frequency hopping indication. The frequency hopping indication indicates in which transmission frequency hopping is performed. Alternatively, this field - when set - indicates that every other repetition is frequency hopped, while the remaining repetitions use the frequency allocation indicated in the DCI. In the case of back-to-back repetitions extending over multiple slots, the frequency hopping pattern can be reset at the slot boundaries.

[0056] In a non-limiting embodiment, the extensions to the TDRA table are optional parameters that may not be configured. If they are not configured, the legacy Rel 15 behavior is followed. If they are configured, the behavior is based on other embodiments in the present disclosure.

[0057] In a non-limiting embodiment, the extensions to the TDRA table are optional parameters that may not be configured. Whether configured or not, implicit indicators are used for different repetition-based transmissions. For example, if they are configured, back-to-back repetitions are indicated, where the aggregation factor is used to determine the number of repeated back-to-back transmissions. If they are not configured, other types of repetition-based transmissions that do not require an aggregation factor are indicated.

[0058] Reference now Figure 1 , provides an example of repeated signaling. Figure 1In the example shown, the UE is configured with a TDRA table having an entry 110 where back-to-back transmissions of total length L occur in two slots, where no transmission occurs on a slot boundary 120. The UE is also configured with a UL configured grant 130 with period P of configuration type 2. If the UE receives an activation DCI for a configured grant indicating a non-back-to-back transmission of length L and a configured granted transmission opportunity determined by period P, which transmission opportunity matches an entry for a back-to-back transmission on a slot boundary, the UE uses back-to-back transmissions on the slot boundary. Thus, the UE uses non-back-to-back transmissions for configured transmission occurrences that do not cross a slot boundary, but uses back-to-back transmissions for occurrences that cross a slot boundary, such as Figure 1 as shown in .

[0059] According to some embodiments, it may also be beneficial to send multiple repetitions of the PDCCH. Then, if the UE misses the first PDCCH transmission, it still has a chance to decode the remaining PDSCH repetitions if it is able to successfully decode the second PDCCH transmission. Then, it needs to know that the second PDCCH only schedules a smaller number of repetitions.

[0060] In one embodiment, another column M is added to the TDRA table. Then, instead of defining the number of repeated transmissions as L, it is defined as: L-(n modM), where n is the slot index and M specifies the maximum number of PDCCH transmissions supported. For example, an M column of one bit will give the option M=1 or M=2. If M=2, a PDCCH on an even-numbered slot will schedule L consecutive slots; and a PDCCH on an odd-numbered slot will schedule L-1 consecutive slots.

[0061] Take L=4 repetitions as an example: if the scheduler transmits DCI in slot 0, it is repeated in slots 0, 1, 2, 3, and the scheduler has the possibility to repeat DCI in slot 1; then indicate slots 1, 2, 3. The cost of adding M columns is that the sequence of M repeated slots can only start on a slot that satisfies n mod M=0, which will increase latency.

[0062] As in the previous embodiment, PDCCH repetitions may be performed back-to-back with Type B scheduling. n may then specify the index of the Type B schedule (or the symbol index within the slot divided by the length of the Type B schedule).

[0063] Enhanced default TDRA table. In some embodiments, it is assumed that the TDRA configuration is laid out in a table format. In this case, adding a new field (e.g., aggregation factor) means adding a new column to the TDRA table for that field. This is shown in the table below, where two new fields (aggregation factor, DMRS presence configuration) are added to the default PDSCH TDRA table for normal CP.

[0064] Table 6: Enhanced 38.214 v15.2.0, Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation for normal CP A In other embodiments, TDRA for both PDSCH and PUSCH is provided via RRC signaling. Therefore, adding a new field means extending the RRC configuration to include the new field. This is illustrated below for PDSCH and PUSCH TDRA configurations respectively.

[0065] As an example, three fields are added to PDSCH-TimeDomainResourceAllocation and PUSCH-TimeDomainResourceAllocation as described in the following table.

[0066] Table 7 In another example, the DMRSPresenceConfig field is a bitmap whose length is equal to the aggregation factor, where 1 means that DMRS is present in the corresponding data transmission and 0 means that DMRS is not present. For example, when the aggregation factor is equal to n4, the bitmap "1010" means that DMRS is present in the first and third transmissions, and DMRS is not present in the second and fourth transmissions.

[0067] In another example, the DMRSPresenceConfig field is a bitmap of length equal to the maximum aggregation factor, where 1 means that DMRS is present in the corresponding data transmission and 0 means that DMRS is not present. Any bits at positions greater than the aggregation factor are ignored.

[0068] In a non-limiting embodiment, the present invention is implemented using a "segmentation factor" or "partition indicator" instead of AggregationFactor. In such an embodiment, the "segmentation factor" may indicate that a longer transmission defined by start S and length L should be split into two or more repetitions. For example, it may indicate that a repetition should be, for example, 2-OS long.

[0069] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 2 For simplicity, Figure 2 The wireless network of FIG. 2 depicts only network 206, network nodes 260 and 260b, and WD 210, 210b, and 210c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. In the illustrated components, network node 260 and wireless device (WD) 210 are described with additional details. The wireless network may provide communication and other types of services to one or more wireless devices, so that the wireless device can access and / or use services provided by or via the wireless network.

[0070] A wireless network may include, and / or interface with, any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-IoT), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0071] Network 206 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0072] The network node 260 and WD 210 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations and / or any other components or systems that may facilitate or participate in data and / or signal communications via wired or wireless connections.

[0073] As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly to a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and then may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Still other examples of network nodes include multi-standard radio (MSR) equipment (such as an 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, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable and / or provide a wireless device with access to a wireless network or to provide a certain service to a wireless device that has access to a wireless network.

[0074] exist Figure 2 In the embodiment, the network node 260 includes a processing circuit 270, a device readable medium 280, an interface 290, an auxiliary device 284, a power supply 286, a power circuit 287, and an antenna 262. Figure 2The network node 260 illustrated in the example wireless network of can represent a device including the illustrated combination of hardware components, but other embodiments can include network nodes with different combinations of components. It is to be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, although the components of the network node 260 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node can include multiple different physical components that make up the single illustrated component (for example, the device readable medium 280 can include multiple separate hard drives and multiple RAM modules).

[0075] Similarly, the network node 260 may be composed of multiple physically separated components (e.g., NodeB components and RNC components or BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 260 includes multiple individual components (e.g., BTS and BSC components), one or more of the individual components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single individual network node in some instances. In some embodiments, the network node 260 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device readable storage media 280 for different RATs), and some components may be reused (e.g., RATs may share the same antenna 262). The network node 260 may also include multiple groups of various components shown for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 260. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 260 .

[0076] The processing circuitry 270 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. Such operations performed by the processing circuitry 270 may include processing information obtained by the processing circuitry 270, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making determinations as a result of the processing.

[0077] The processing circuitry 270 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide network node 260 functionality, either alone or in conjunction with other network node 260 components, such as device readable medium 280. For example, the processing circuitry 270 may execute instructions stored in the device readable medium 280 or in a memory within the processing circuitry 270. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 770 may include a system on a chip (SOC).

[0078] In some embodiments, processing circuitry 270 may include one or more of radio frequency (RF) transceiver circuitry 272 and baseband processing circuitry 274. In some embodiments, radio frequency (RF) transceiver circuitry 272 and baseband processing circuitry 274 may be on separate chips (or chipsets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuitry 272 and baseband processing circuitry 274 may be on the same chip or chipset, board, or unit.

[0079] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 270 executing instructions stored in a memory or device-readable medium 280 within the processing circuit 270. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 270 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuit 270 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 270 alone or other components of the network node 260, but are enjoyed by the network node 260 as a whole, and / or generally by end users and wireless networks.

[0080] Device readable medium 280 may include any form of volatile or non-volatile computer readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or computer executable memory devices that store information, data, and / or instructions that can be used by processing circuit 270. Device readable medium 280 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions that can be executed by processing circuit 270 and utilized by network node 260. Device readable medium 280 may be used to store any calculations performed by processing circuit 270 and / or any data received via interface 290. In some embodiments, processing circuit 270 and device readable medium 280 may be considered integrated.

[0081] Interface 290 is used in wired or wireless communication of signaling and / or data between network node 260, network 206 and / or WD 210. As shown, interface 290 includes (one or more) ports / (one or more) terminals 294, for example, to send data to network 206 and receive data from the network through a wired connection. Interface 290 also includes radio front-end circuit 292, which can be coupled to antenna 262, or is part of the antenna in some embodiments. Radio front-end circuit 292 includes filter 298 and amplifier 296. Radio front-end circuit 292 can be connected to antenna 262 and processing circuit 270. Radio front-end circuit can be configured to adjust the signal transmitted between antenna 262 and processing circuit 270. Radio front-end circuit 292 can receive digital data to be sent to other network nodes or WD via wireless connection. Radio front-end circuit 292 can use a combination of filter 298 and / or amplifier 296 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna 262. Similarly, when data is received, antenna 262 may collect radio signals, which are then converted into digital data by radio front end circuitry 292. The digital data may be passed to processing circuitry 270. In other embodiments, the interface may include different components and / or different combinations of components.

[0082] In some alternative embodiments, the network node 260 may not include a separate radio front end circuit 292, and instead, the processing circuit 270 may include the radio front end circuit and may be connected to the antenna 262 without the separate radio front end circuit 292. Similarly, in some embodiments, all or some of the RF transceiver circuit 272 may be considered part of the interface 290. In still other embodiments, the interface 290 may include one or more ports or terminals 294, the radio front end circuit 292, and the RF transceiver circuit 272 as part of a radio unit (not shown), and the interface 290 may communicate with the baseband processing circuit 274, which is part of the digital unit (not shown).

[0083] Antenna 262 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 262 may be coupled to radio front-end circuit 290 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 262 may include one or more omnidirectional, sector or flat panel antennas operable to transmit / receive, for example, radio signals between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 262 may be separate from network node 260 and may be connected to network node 260 via an interface or port.

[0084] Antenna 262, interface 290 and / or processing circuit 270 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 262, interface 290 and / or processing circuit 270 can be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data and / or signal can be transmitted to a wireless device, another network node and / or any other network equipment.

[0085] The power circuit 287 may include or be coupled to a power management circuit, and is configured to supply power for performing the functionality described herein to the components of the network node 260. The power circuit 287 may receive power from the power supply 286. The power supply 286 and / or the power circuit 287 may be configured to provide power to the various components of the network node 260 in a form suitable for the respective components (e.g., with the voltage and current levels required for each respective component). The power supply 286 may be included in the power circuit 287 and / or the network node 260, or outside thereof. For example, the network node 260 may be connected to an external power source (e.g., an electrical socket) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit 287. As another example, the power supply 286 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit 287. If the external power source fails, the battery may provide a backup power source. Other types of power sources, such as photovoltaic devices, may also be used.

[0086] Alternative embodiments of network node 260 may include, in addition to Figure 2 , which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 260 may include a user interface device to allow information to be input into the network node 260 and to allow information to be output from the network node 260. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 260.

[0087] As used herein, a wireless device (WD) refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other wireless device. Unless otherwise noted, the term WD may be used interchangeably with a user equipment (UE) herein. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air to transmit and / or receive wireless signals. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD 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 the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, rechargeable devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted equipment (LMEs), smart devices, wireless customer premises equipment (CPEs), wireless terminal devices installed in vehicles, etc. WDs can support device-to-device (D2D) communications, such as by implementing the (3GPP) standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as D2D communication devices. As another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the WD may be a UE that implements 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 appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. The WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0088] As shown, wireless device 210 includes antenna 211, interface 214, processing circuit 220, device readable medium 230, user interface device 232, auxiliary device 234, power supply 236 and power circuit 237. WD 210 can include multiple groups of one or more illustrated components for different wireless technologies supported by WD 210, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMax or Bluetooth wireless technology, just to mention a few. These wireless technologies can be integrated into chips or chipsets that are the same or different from other components in WD 710.

[0089] Antenna 211 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 214. In some alternative embodiments, antenna 211 may be separated from WD 210 and may be connected to WD 210 via an interface or port. Antenna 211, interface 214, and / or processing circuit 220 may be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, radio front-end circuitry and / or antenna 211 may be considered as an interface.

[0090] As shown, the interface 214 includes a radio front-end circuit 212 and an antenna 211. The radio front-end circuit 212 includes one or more filters 218 and an amplifier 216. The radio front-end circuit 214 is connected to the antenna 211 and the processing circuit 220, and is configured to adjust the signal transmitted between the antenna 211 and the processing circuit 220. The radio front-end circuit 212 can be coupled to the antenna 211, or as a part thereof. In some embodiments, the WD 210 may not include a separate radio front-end circuit 212; on the contrary, the processing circuit 220 may include a radio front-end circuit and may be connected to the antenna 211. Similarly, in some embodiments, some or all of the RF transceiver circuit 222 may be considered as part of the interface 214. The radio front-end circuit 212 may receive digital data to be sent out to other network nodes or WDs via a wireless connection. The radio front-end circuit 212 may use a combination of filters 218 and / or amplifiers 216 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 211. Similarly, when data is received, antenna 211 may collect radio signals, which are then converted into digital data by radio front end circuit 712. The digital data may be passed to processing circuit 220. In other embodiments, the interface may include different components and / or different combinations of components.

[0091] The processing circuit 220 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, a combination of one or more of the resources, or a combination of hardware, software, and / or encoded logic operable to provide WD210 functionality, either alone or in combination with other WD210 components (such as device readable medium 730). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 220 may execute instructions stored in the device readable medium 230 or in a memory within the processing circuit 220 to provide the functionality disclosed herein.

[0092] As shown, the processing circuit 220 includes one or more of the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 220 of the WD 210 may include a SOC. In some embodiments, the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 224 and the application processing circuit 226 may be combined into one chip or chipset, and the RF transceiver circuit 222 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 222 and the baseband processing circuit 224 may be on the same chip or chipset, and the application processing circuit 226 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 222, the baseband processing circuit 224, and the application processing circuit 226 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 222 may be part of interface 214. RF transceiver circuitry 222 may condition RF signals for processing circuitry 220.

[0093] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by a processing circuit 220 executing instructions stored on a device-readable medium 230, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 220 without the need to execute instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit 220 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 220 alone or other components of the WD 210, but are enjoyed by the WD 210 as a whole, and / or are generally enjoyed by end users and wireless networks.

[0094] Processing circuit 220 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. Such operations performed by processing circuit 220 may include processing information obtained by processing circuit 220, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 210, and / or performing one or more operations based on the obtained information or the converted information and making determinations as a result of the processing.

[0095] Device-readable medium 230 is operable to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by processing circuit 220. Device-readable medium 230 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by processing circuit 220. In some embodiments, processing circuit 220 and device-readable medium 230 may be considered integrated.

[0096] The user interface device 232 can provide a component that allows a human user to interact with the WD 210. Such interaction can be in a variety of forms, such as visual, auditory, tactile, etc. The user interface device 232 can operate to generate output to the user and allow the user to provide input to the WD 210. The type of interaction can vary according to the type of user interface device 232 installed in the WD 210. For example, if the WD 710 is a smart phone, the interaction can be carried out via a touch screen; if the WD 210 is a smart meter, the interaction can be carried out through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 232 can include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 232 is configured to allow information to be input into the WD 210, and is connected to the processing circuit 220 to allow the processing circuit 220 to process the input information. The user interface device 232 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device 232 is further configured to allow information to be output from the WD 210 and to allow the processing circuit 220 to output information from the WD 210. The user interface device 232 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 232, the WD 210 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0097] Auxiliary device 234 is operable to provide more specific functionality not typically performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and type of components of auxiliary device 734 may vary depending on the embodiment and / or scenario.

[0098] In some embodiments, the power source 236 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical socket), a photovoltaic device, or a power battery. The WD 210 may further include a power circuit 237 for delivering power from the power source 236 to various parts of the WD 210, which need to be powered from the power source 236 to implement any functionality described or indicated herein. In some embodiments, the power circuit 237 may include a power management circuit. The power circuit 237 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 210 may be connected to an external power source (such as an electrical socket) via an input circuit or interface (such as a power cable). In some embodiments, the power circuit 237 may also be operable to deliver power from an external power source to the power source 236. For example, this may be used for charging the power source 236. The power circuit 237 may perform any formatting, conversion, or other modifications to the power from the power source 236 so that the power is suitable for the corresponding components of the WD 210 to which the power is supplied.

[0099] Figure 3 An embodiment of a UE in accordance with various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but that may not be associated with, or that may not initially be associated with, a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but that may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 300 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 3 The UE 300 illustrated in FIG. 1 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 3 It is a UE, but the components discussed in this article are also applicable to WD, and vice versa.

[0100] exist Figure 3In the embodiment, UE 300 includes processing circuit 301, which is operably coupled to input / output interface 305, radio frequency (RF) interface 309, network connection interface 311, memory 315 including random access memory (RAM) 317, read-only memory (ROM) 319 and storage medium 321, communication subsystem 331, power supply 333 and / or any other components or any combination thereof. Storage medium 321 includes operating system 323, application 325 and data 327. In other embodiments, storage medium 321 may include other similar types of information. Some UEs may utilize Figure 3 All components shown in the UE may be used, or only a subset of the components may be utilized. The level of integration between components may vary from one UE to another. In addition, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0101] exist Figure 3 , processing circuit 301 may be configured to process computer instructions and data. Processing circuit 301 may be configured to implement any sequential state machine that operates to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together with appropriate software; or any combination of the above. For example, processing circuit 301 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0102] In the depicted embodiment, the input / output interface 305 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 300 may be configured to use an output device via the input / output interface 305. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to the UE 300 and output from the UE. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 300 may be configured to use an input device via the input / output interface 305 to allow a user to capture information into the UE 300. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0103] exist Figure 3 In the embodiment of the present invention, the RF interface 309 can be configured to provide a communication interface to the RF components (such as transmitters, receivers and antennas). The network connection interface 311 can be configured to provide a communication interface to the network 343a. The network 343a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 343a can include a Wi-Fi network. The network connection interface 311 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 311 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

[0104] RAM 317 can be configured to interface with processing circuit 801 via bus 302 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications and device drivers. ROM 319 can be configured to provide computer instructions or data to processing circuit 301. For example, ROM 319 can be configured to store unchanged low-level system code or data of basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup or receiving keystrokes from a keyboard. Storage medium 321 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium 321 can be configured to include operating system 323, application 325 (such as a web browser application, widget or gadget engine or another application) and data file 327. The storage medium 321 may store any of various operating systems or combinations of operating systems for use by the UE 300 .

[0105] The storage medium 321 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM) synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory or any combination thereof. The storage medium 321 may allow the UE 300 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article such as utilizing a communication system may be tangibly embodied in the storage medium 321, which may include a device-readable medium.

[0106] exist Figure 3In the embodiment, the processing circuit 801 can be configured to communicate with the network 343b using the communication subsystem 331. The network 343a and the network 343b can be the same one or more networks or different one or more networks. The communication subsystem 331 can be configured to include one or more transceivers for communicating with the network 343b. For example, the communication subsystem 331 can be configured to include one or more transceivers for communicating with the network 343b according to one or more communication protocols (such as IEEE 802, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.) and one or more remote transceivers of another device (such as another WD, UE or base station of a radio access network (RAN)) capable of wireless communication. Each transceiver can include a transmitter 333 and / or a receiver 335 to respectively implement the transmitter or receiver functionality (e.g., frequency allocation, etc.) applicable to the RAN link. In addition, the transmitter 333 and the receiver 335 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

[0107] In the illustrated embodiment, the communication functions of the communication subsystem 331 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function, or any combination thereof. For example, the communication subsystem 331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 343b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 343b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 313 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 300.

[0108] The features, benefits and / or functions described herein may be implemented in one of the components of UE 300, or may be divided across multiple components of UE 300. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 331 may be configured to include any component described herein. In addition, the processing circuit 301 may be configured to communicate with any such component via the bus 302. In another example, any such component may be represented by program instructions stored in a memory, which, when executed by the processing circuit 301, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between the processing circuit 301 and the communication subsystem 331. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0109] Figure 4 400 is a schematic block diagram of a virtualized environment, wherein the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least some functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0110] In some embodiments, some or all of the functionality described herein may be implemented as virtual components performed by one or more virtual machines implemented in one or more virtual environments 400 hosted by one or more of the hardware nodes 430. Additionally, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0111] These functions may be implemented by one or more applications 420 (alternatively they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 420 run in a virtualized environment 400 that provides hardware 430 including processing circuitry 460 and memory 490. The memory 490 includes instructions 495 executable by the processing circuitry 460, whereby the applications 420 may operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0112] The virtualized environment 400 includes a general or special purpose network hardware device 430, which includes a collection of one or more processors or processing circuits 460, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuit, including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 490-1, which may be a non-permanent memory for temporarily storing software or instructions 495 executed by the processing circuit 460. Each hardware device may include one or more network interface controllers (NICs) 470, also known as network interface cards, which include physical network interfaces 480. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 490-2 in which instructions and / or software 495 executable by the processing circuit 460 are stored. The software 495 may include any type of software, including software for instantiating one or more virtualization layers 450 (also known as hypervisors), software for executing virtual machines 440, and software that allows them to perform the functions, features, and / or benefits described in conjunction with some of the embodiments described herein.

[0113] The virtual machine 440 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 450 or hypervisor. Different embodiments of the instance of the virtual appliance 420 can be implemented on one or more of the virtual machines 440, and the implementation can be performed in different ways.

[0114] During operation, processing circuitry 460 executes software 495 to instantiate a hypervisor or virtualization layer 450, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 450 may present to virtual machines 440 a virtual operating platform that appears to be networked hardware.

[0115] like Figure 4 As shown, hardware 430 can be an independent network node with common or specific components. Hardware 430 can include antenna 4225, and some functions can be implemented via virtualization. Alternatively, hardware 430 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 4100, which also oversees the life cycle management of application 420, among other things.

[0116] Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and customer premises equipment.

[0117] In the context of NFV, a virtual machine 440 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 440 and the portion of the hardware 430 on which it executes, whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines 440, forms a separate virtual network element (VNE).

[0118] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 440 atop the hardware networking infrastructure 430 and corresponds to Figure 4 Application 420.

[0119] In some embodiments, one or more radio units 4200, each including one or more transmitters 4220 and one or more receivers 4210, may be coupled to one or more antennas 4225. The radio units 4200 may communicate directly with the hardware nodes 430 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.

[0120] In some embodiments, some signaling may be accomplished using a control system 4230 , which may alternatively be used for communications between the hardware node 430 and the radio unit 4200 .

[0121] refer to Figure 5 , shows a communication system according to an embodiment. Figure 5 A telecommunication network connected to a host computer via an intermediate network according to an embodiment is shown. The communication system shown includes a telecommunication network 510, such as a 3GPP type cellular network, which includes an access network 511 (such as a radio access network) and a core network 514. The access network 511 includes a plurality of base stations 512a, 512b, 512c, such as NB, eNB, gNB or other types of wireless access points, each defining a corresponding coverage area 513a, 513b, 513c. Each base station 512a, 512b, 512c can be connected to the core network 514 via a wired or wireless connection 515. A first UE 591 located in the coverage area 513c is configured to be wirelessly connected to or paged by the corresponding base station 512c. A second UE 592 in the coverage area 513a can be wirelessly connected to the corresponding base station 512a. Although multiple UEs 591, 592 are illustrated in this example, the disclosed embodiments are equally applicable to situations where a unique UE is in the coverage area or a unique UE is connected to the corresponding base station 1012.

[0122] The telecommunications network 510 itself is connected to a host computer 530, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 530 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 521 and 522 between the telecommunications network 510 and the host computer 530 may extend directly from the core network 514 to the host computer 530, or may be via an optional intermediate network 520. The intermediate network 520 may be one or more of a combination of public, private, or managed networks; the intermediate network 520 (if any) may be a backbone network or the Internet; in particular, the intermediate network 520 may include two or more subnets (not shown).

[0123] Figure 5 The communication system as a whole enables connectivity between the connected UEs 591, 592 and the host computer 530. The connectivity can be described as an over-the-top (OTT) connection 550. The host computer 530 and the connected UEs 591, 592 are configured to use the access network 511, the core network 514, any intermediate networks 520, and possible additional infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 550. The OTT connection 550 can be transparent in the sense that the participating communication devices through which the OTT connection 550 passes are unaware of the routing of uplink and downlink communications. For example, the base station 512 may not be informed or need not be informed of the past routing of incoming downlink communications, which have data originating from the host computer 530 to be forwarded (e.g., switched) to the connected UE 591. Similarly, the base station 512 does not need to know the future routing of outgoing uplink communications originating from the UE 591 toward the host computer 530.

[0124] According to the embodiment, reference will now be made to Figure 6 Example implementations of the UE, base station, and host computer discussed in the previous paragraphs are described. Figure 6A host computer that communicates with a user device via a base station through a partial wireless connection according to an embodiment is shown. In the communication system 600, the host computer 610 includes hardware 615, which includes a communication interface 616, which is configured to establish and maintain a wired or wireless connection of an interface with different communication devices of the communication system 600. The host computer 610 further includes a processing circuit 618, which may have storage and / or processing capabilities. In particular, the processing circuit 618 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 610 further includes software 611, which is stored in or accessible to the host computer 610 and can be executed by the processing circuit 618. The software 611 includes a host application 612. The host application 612 is operable to provide services to remote users, such as UE 630 connected via an OTT connection 650 terminated at UE 630 and the host computer 610. When providing services to remote users, the host application 612 can provide user data transmitted using the OTT connection 650.

[0125] The communication system 600 further includes a base station 620, which is provided in the telecommunication system and includes hardware 625, enabling it to communicate with the host computer 610 and the UE 630. The hardware 625 may include a communication interface 626 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 600, and for establishing and maintaining a connection with the base station 620 in the coverage area ( Figure 6 The communication interface 626 may be configured to facilitate a connection 660 to the host computer 610. The connection 660 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Figure 6 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 625 of the base station 620 further includes processing circuitry 628, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 620 further has software 621 stored internally or accessible via an external connection.

[0126] The communication system 600 further includes the UE 630 already mentioned. Its hardware 635 may include a radio interface 637, which is configured to establish and maintain a wireless connection 670 with a base station serving the coverage area where the UE 630 is currently located. The hardware 635 of the UE 630 further includes a processing circuit 638, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 630 further includes software 631, which is stored in the UE 630 or can be accessed by it, and can be executed by the processing circuit 638. The software 631 includes a client application 632. The client application 632 is operable to provide services to human or non-human users via the UE 630 under the support of the host computer 610. In the host computer 610, the executing host application 612 can communicate with the executing client application 632 via an OTT connection 650 terminated at the UE 630 and the host computer 610. In providing services to users, client application 632 may receive request data from host application 612 and provide user data in response to the request data. OTT connection 650 may transfer both request data and user data. Client application 632 may interact with the user to generate the user data it provides.

[0127] Notice, Figure 6 The host computer 610, base station 620 and UE 630 shown may be similar to or identical to Figure 5 The host computer 530, one of the base stations 512a, 512b, 512c and one of the UEs 591, 592. That is, the internal workings of these entities can be as follows Figure 6 shown, and independently, the surrounding network topology can be Figure 5 network topology.

[0128] exist Figure 6 In FIG. 6 , an OTT connection 650 has been abstractly drawn to illustrate communications between a host computer 610 and a UE 630 via a base station 620, without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 630, or hidden from the service provider operating the host computer 610, or hidden from both. While the OTT connection 650 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0129] The wireless connection 670 between the UE 630 and the base station 620 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of the OTT service provided to the UE 630 using the OTT connection 650, wherein the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments can improve latency and reliability, and thereby provide benefits such as reduced usage latency, relaxed restrictions on file size, better responsiveness, etc.

[0130] For the purpose of monitoring data rate, latency and other factors improved by one or more embodiments, a measurement process may be provided. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host computer 610 and the UE 630 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 650 may be implemented in the software 611 and hardware 615 of the host computer 610 or in the software 631 and hardware 635 of the UE 630 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 650 passes; the sensor may participate in the measurement process by providing the value of the monitored quantity exemplified above or providing the value of other physical quantities from which the software 611, 631 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 650 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 620 and may be unknown or imperceptible to the base station 620. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling, facilitating host computer 610 measurements of throughput, propagation time, latency, etc. The measurements may be accomplished by software 611 and 631 causing messages (particularly empty or "dummy" messages) to be transmitted using OTT connection 650 while it monitors propagation time, errors, etc.

[0131] Figure 7 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be a reference Figure 5 and 6 To simplify this disclosure, only the Figure 7. In step 710, the host computer provides user data. In sub-step 711 of step 710 (which may be optional), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. In step 730 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0132] Figure 8 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be a reference Figure 5 and 6 To simplify this disclosure, only the Figure 8 . In step 810 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 820, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission can be delivered via a base station. In step 830 (which may be optional), the UE receives the user data carried in the transmission.

[0133] Fig. 9 is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be a reference Figure 5 and 6 To simplify this disclosure, only the Fig. 9 . In step 910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 920, the UE provides user data. In sub-step 921 of step 920 (which may be optional), the UE provides user data by executing a client application. In sub-step 911 of step 910 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step 930 (which may be optional), the UE initiates transmission of user data to the host computer. In step 940 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0134] Fig.10is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be a reference Figure 5 and 6 To simplify this disclosure, only the Fig.10 In step 1010 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1020 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0135] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include several of these functional units. These functional units may be implemented via processing circuits and other digital hardware, and the processing circuits may include one or more microprocessors or microcontrollers, and the digital hardware may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function.

[0136] Fig.11 is a flow chart for repeating signaling according to some embodiments. In some embodiments, Fig.11 Method 1100 may be performed by a wireless device or UE for repeated signaling. In step 1102, the WD receives a control message including an indication of an index value. For example, in some embodiments, the control message is downlink control information (DCI) transmitted on a physical downlink control channel (PDCCH), a configuration message transmitted on a radio resource control (RRC), or a combination of a DCI transmitted on the PDCCH and a configuration message transmitted on the RRC. In step 1104, the WD obtains a parameter set from the TDRA configuration information using the index value, the parameter set including an aggregation factor. For example, as described above, the TDRA configuration information may include a default TDRA table as described above or a TDRA configuration configured via the RRC.

[0137] Fig.12is a flow chart for repeating signaling according to some embodiments. In some embodiments, Fig.12 The method 1200 may be performed by a base station for repeated signaling. In step 1202, the base station generates a configuration message, the message including TDRA configuration information, the TDRA configuration including an aggregation factor. In step 1204, the base station sends the configuration message to the wireless device.

[0138] Figure 13-14 A wireless network (eg, Figure 2 Schematic block diagram of apparatus 1300, 1400 in a wireless network (shown in FIG. 1 ). The apparatus may be in a wireless device or a network node (e.g., Figure 2 The apparatus 1300, 1400 may be operable to perform the reference Fig.11 and Fig.12 The example methods described herein and possibly any other processes or methods disclosed herein. It should also be understood that Fig.11 and Fig.12 The method is not necessarily performed only by the devices 1300, 1400. At least some operations of the method may be performed by one or more other entities.

[0139] The virtual device 1300, 1400 may include a processing circuit, which may include one or more microprocessors or microcontrollers and digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more techniques described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the receiving unit 1302, the configuration unit 1304, the control unit 1406, the transmission unit 1408 and / or any other suitable unit of the device 1300, 1400 to perform corresponding functions.

[0140] like Fig.13 As shown in , the device 1300 includes: a receiving unit 1302 configured to receive a control message, the control message including an indication of an index value; and a configuration unit 1304 configured to obtain a parameter set from TDRA configuration information using the index value, the parameter set including an aggregation factor.

[0141] like Fig.14As shown, the apparatus 1400 includes a control unit 1406 configured to generate a configuration message, the message including time domain resource allocation (TDRA) configuration information, the TDRA configuration information including an aggregation factor; and a transmitting unit 1408 configured to transmit the configuration message to a wireless device.

[0142] The term "unit" has a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0143] Example Embodiments Example Group A Embodiment - UE A1. A method for repeated signaling performed by a wireless device, the method comprising at least one of the following steps: receiving a control message, the control message comprising an indication of an index value; and using the index value to obtain a parameter set from time domain resource allocation (TDRA) configuration information, the parameter set comprising an aggregation factor.

[0144] A2. A method according to embodiment 1, wherein the TDRA configuration information is arranged in a table having multiple rows, and the step of obtaining the parameter set includes at least one of the following: identifying the row in the table corresponding to the index value; and obtaining the parameter set from the identified row in the table.

[0145] A3. According to the method of any one of the preceding embodiments, the TDRA configuration information includes a physical uplink shared channel (PUSCH) TDRA configuration, and the parameter set further includes a time slot offset, a start symbol, an allocation length, and a PUSCH mapping type.

[0146] A4. A method according to any one of embodiments 1-2, wherein the TDRA configuration information includes a physical uplink shared channel (PUSCH) TDRA configuration, and the parameter set also includes a time slot offset, a start and length indicator variable, and a PUSCH mapping type.

[0147] A5. A method according to any of the preceding embodiments, wherein the parameter set further comprises an indication of at least one of time slot aggregation or back-to-back repetition of transmissions using an aggregation factor.

[0148] A6. The method of embodiment 5, wherein the indication of using at least one of slot aggregation or back-to-back repetition specifies using slot aggregation for the first set of transmission durations and using back-to-back for the second set of transmission durations.

[0149] A7. The method of embodiment 5, wherein the indication of using at least one of slot aggregation or back-to-back repetition further specifies using slot aggregation for the first type of scheduling and back-to-back for the second type of scheduling.

[0150] A8. The method according to any one of embodiments 5-7 also includes at least one of the following: determining that using back-to-back repetition for the aggregation factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as a result of the determination, determining not to transmit at least one transmission that at least partially occupies the second time slot.

[0151] A9. The method according to any one of embodiments 5-7 also includes at least one of the following: determining that using back-to-back repetition for the aggregation factor will cause the first transmission to occupy the first time slot and the second transmission to at least partially occupy a second time slot different from the first time slot; as a result of the determination, shortening the second transmission so that the second transmission no longer at least partially occupies the second time slot.

[0152] A10. The method according to any of the preceding embodiments further comprises: transmitting a message using a parameter set obtained from the TDRA configuration information.

[0153] A11. A method according to any of the preceding embodiments, wherein the aggregation factor indicates the number of single repetitions, the method further comprising at least one of the following: determining that back-to-back repetitions according to the number of single repetitions result in a transmission occupying two time slots; and determining not to transmit a transmission occupying two time slots.

[0154] A12. A method according to any one of the preceding embodiments, wherein the TDRA configuration information includes a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set further includes a time slot offset, a start symbol, an allocation length, and a PDSCH mapping type.

[0155] A13. A method according to any one of embodiments 1-11, wherein the TDRA configuration information is a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set also includes a time slot offset, a start and length indicator variable, and a PDSCH mapping type.

[0156] A14. The method according to any one of the preceding embodiments further includes: receiving a message according to a parameter set obtained from the TDRA configuration information.

[0157] A15. A method according to any one of the aforementioned embodiments, wherein the clustering factor indicates the number of time slots in which resource allocation should be repeated, and the method further includes: for each time slot in the number of time slots, repeating the resource allocation back-to-back as frequently as possible without crossing the boundary of the time slot.

[0158] A15-1. The method according to claim 15, wherein the resource allocation is frequency domain resource allocation.

[0159] A16. The method according to any one of the aforementioned embodiments further includes at least one of the following: determining that back-to-back repetition with an aggregation factor will cause a first transmission to occupy a first time slot, and at least one transmission to at least partially occupy a second time slot different from the first time slot; as a result of the determination, determining not to receive at least one transmission that at least partially occupies the second time slot.

[0160] A17. The method according to any one of the preceding embodiments further includes at least one of the following: determining that back-to-back repetition with an aggregation factor will result in a first transmission occupying a first time slot and a second transmission at least partially occupying a second time slot different from the first time slot; as a result of the determination, receiving a shortened second transmission so that the shortened second transmission no longer at least partially occupies the second time slot.

[0161] A18. A method according to any one of the preceding embodiments, wherein the aggregation factor indicates the number of single repetitions, and the method further comprises the following steps: determining that back-to-back repetitions according to the number of single repetitions result in a transmission occupying two time slots; and determining not to receive a transmission occupying two time slots.

[0162] A19. A method according to any one of the preceding embodiments, wherein the parameter set further includes: a demodulation reference signal (DMRS) presence configuration, wherein the DMRS presence configuration indicates in which of the aggregate transmissions the DMRS exists.

[0163] A20. The method according to embodiment 19, wherein the DMRS presence configuration further indicates the number of DMRSs present in a group of aggregated transmissions.

[0164] A21. A method according to any one of embodiments 1-19, wherein the DMRS presence configuration further indicates the presence or absence of a DMRS following a mapping type in the repetition.

[0165] A22. A method according to any one of the preceding embodiments, wherein the parameter set also includes a redundant version sequence.

[0166] A23. A method according to any one of the preceding embodiments, wherein the parameter set also includes a frequency hopping indication.

[0167] A24. A method according to any one of the preceding embodiments, wherein the control message is: (i) downlink control information (DCI) transmitted on a physical downlink control channel (PDCCH); (ii) a configuration message transmitted on a radio resource control (RRC); or (iii) a combination of DCI transmitted on PDCCH and a configuration message transmitted on RRC.

[0168] A25. The method according to any one of the preceding embodiments, wherein the aggregation factor is an optional parameter, further comprising: determining that the aggregation factor is not configured in the TDRA configuration information.

[0169] A26. A method according to any one of the preceding embodiments, wherein the set of parameters also includes an indication of the maximum number (M) of supported physical downlink control channel (PDCCH) transmissions, and also includes: determining the number of repeated transmissions by calculating L-(n modM), where L is the allocation length and n is the time slot index value.

[0170] A27. A method according to any of the preceding embodiments, wherein the aggregation factor is a split factor or a partition indicator, which indicates that the transmission defined by the start S and the length L is to be divided into two or more repetitions.

[0171] Group B Example - Base Station B1. A method for repeated signaling performed by a base station, the method comprising at least one of the following steps: generating a control message, the control message comprising time domain resource allocation (TDRA) configuration information, the TDRA configuration information comprising an aggregation factor; and transmitting the configuration message to a wireless device.

[0172] B2. According to the method of embodiment 1, the TDRA configuration information includes a physical uplink shared channel (PUSCH) TDRA configuration, and the TDRA configuration information further includes a time slot offset, a start symbol, an allocation length, and a PUSCH mapping type.

[0173] B3. The method of embodiment 1, wherein the TDRA configuration information includes a physical uplink shared channel (PUSCH) TDRA configuration, and the parameter set further includes a time slot offset, a start and length indicator variable, and a PUSCH mapping type.

[0174] B4. The method according to any of the preceding embodiments, wherein the TDRA configuration information further includes an indication for the wireless device to send transmissions to the base station using at least one of time slot aggregation or back-to-back repetition according to an aggregation factor.

[0175] B5. The method of embodiment 4, wherein the indication of using at least one of slot aggregation or back-to-back repetition specifies using slot aggregation for the first set of transmission durations and using back-to-back for the second set of transmission durations.

[0176] B6. The method of embodiment 5, wherein the indication of using at least one of slot aggregation or back-to-back repetition further specifies to the wireless device that slot aggregation is used for the first type of scheduling and back-to-back is used for the second type of scheduling.

[0177] B7. The method according to any of the preceding embodiments further comprises: receiving a message transmitted from a wireless device according to the TDRA configuration information.

[0178] B7-1. The method according to any one of the aforementioned embodiments further includes: at least one of the following: determining that using back-to-back repetition for the aggregation factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as a result of the determination, determining not to receive at least one transmission that at least partially occupies the second time slot.

[0179] B7-2. The method according to any one of the aforementioned embodiments further includes at least one of the following: determining that using back-to-back repetition for the aggregation factor will cause the first transmission to occupy a first time slot and the second transmission to at least partially occupy a second time slot different from the first time slot; as a result of the determination, receiving a shortened second transmission so that the second transmission no longer at least partially occupies the second time slot.

[0180] B7-3. A method according to any of the preceding embodiments, wherein the aggregation factor indicates the number of single repetitions, the method further comprising at least one of the following: determining that back-to-back repetitions according to the number of single repetitions result in a transmission occupying two time slots; and determining not to transmit a transmission occupying two time slots.

[0181] B8. A method according to any one of the preceding embodiments, wherein the TDRA configuration information includes a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set further includes a time slot offset, a start symbol, an allocation length, and a PDSCH mapping type.

[0182] B9. A method according to any one of embodiments 1-7, wherein the TDRA configuration information is a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set also includes a time slot offset, a start and length indicator variable, and a PDSCH mapping type.

[0183] B10. The method according to any one of the aforementioned embodiments further includes at least one of the following: determining that using back-to-back repetition with an aggregation factor will result in a first transmission occupying a first time slot and a second transmission at least partially occupying a second time slot different from the first time slot; as a result of the determination, determining not to receive at least one transmission that at least partially occupies the second time slot.

[0184] B11. The method according to any one of the aforementioned embodiments further includes at least one of the following: determining that back-to-back repetition with an aggregation factor will cause the first transmission to occupy a first time slot and the second transmission to at least partially occupy a second time slot different from the first time slot; as a result of the determination, shortening the second transmission so that the shortened second transmission no longer at least partially occupies the second time slot.

[0185] B12. The method according to any one of the preceding embodiments further includes at least one of the following: transmitting a message according to TDRA configuration information.

[0186] B13. A method according to any one of the preceding embodiments, wherein the aggregation factor indicates the number of single repetitions, and the method further comprises the following steps: determining, based on the number of single repetitions, that back-to-back repetitions result in a transmission occupying two time slots; and determining not to receive a transmission occupying two time slots.

[0187] B14. A method according to any one of the preceding embodiments, wherein the clustering factor indicates the number of time slots in which resource allocation should be repeated, and the method further comprises: for each time slot in the number of time slots, repeating the resource allocation back-to-back as frequently as possible without crossing the boundaries of the time slots.

[0188] B14-1. The method according to claim 1, wherein the resource allocation is frequency domain resource allocation.

[0189] B15. The method according to any one of the preceding embodiments, wherein the TDRA configuration information further includes: a DMRS presence configuration, wherein the DMRS presence configuration indicates in which of the aggregate transmissions the DMRS exists.

[0190] B16. A method according to embodiment 15, wherein the DMRS presence configuration further indicates: (i) the number of DMRSs present in a group of aggregate transmissions, or (ii) the presence or absence of DMRSs following a mapping type in a repetition.

[0191] B17. A method according to any one of embodiments 15-16, wherein the DMRS presence configuration includes a bitmap having a length equal to an aggregation factor.

[0192] B18. A method according to any one of the preceding embodiments, wherein the parameter set also includes a redundant version sequence.

[0193] B19. A method according to any one of the preceding embodiments, wherein the parameter set also includes a frequency hopping indication.

[0194] B20. A method according to any one of the preceding embodiments, wherein the configuration message is: (i) downlink control information (DCI) transmitted on a physical downlink control channel (PDCCH); (ii) a configuration message transmitted on a radio resource control (RRC); or (iii) a combination of a DCI transmitted on the PDCCH and a configuration message transmitted on the RRC.

[0195] B21. A method according to any of the preceding embodiments, wherein the clustering factor is an optional parameter.

[0196] B22. A method according to any one of the preceding embodiments, wherein the TDRA configuration further includes an indication of the maximum number (M) of supported physical downlink control channel (PDCCH) transmissions, wherein the number of repeated transmissions is calculated based on L-(n mod M), where L is the allocation length and n is the time slot index value.

[0197] B23. A method according to any of the preceding embodiments, wherein the aggregation factor is a split factor or a partition indicator, which indicates that the transmission defined by the start S and the length L is to be divided into two or more repetitions.

[0198] Group C Example C1. A wireless device for repeated signaling, the wireless device comprising: a processing circuit configured to perform any steps of any one of the embodiments in Group A.

[0199] C2. A base station for repeated signaling, the base station comprising: a processing circuit configured to perform any steps of any embodiment of any Group B embodiments.

[0200] C3. A user equipment for repeated signaling, the UE comprising: an antenna configured to transmit and receive wireless signals; and a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust the signal transmitted between the antenna and the processing circuit; the processing circuit is configured to perform any step of any one of the embodiments in Group A; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to supply power to the UE.

[0201] abbreviation At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage should be preferred. If listed multiple times below, the first listing should take precedence over (one or more) subsequent listings.

[0202] lx RTT CDMA2000 lx Radio Transmission Technology 3GPP Third Generation Partnership Project 5G fifth generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC carrier component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR channel impulse response CP cyclic prefix CPICH common pilot channel CPICH Ec / NoCPICH Received energy per chip divided by the power density in the frequency band CQI channel quality information C-RNTICell RNTI CSI channel state information DCCH dedicated control channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell ID (positioning method) E-SMLC Evolution - Service Mobile Location Center ECGI Evolved CGI eNB E-UTRAN Node B ePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Service Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS needs further study GERAN GSM EDGE Radio Access Network Base stations in gNB NR GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed ​​Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long Term Evolution MAC Media Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFNABS MBSFN Almost Blank Subframes MDT Minimization of Drive Test MTB Master Information Block MME mobility management entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Power Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid ARQ Indicator Channel PLMN Public Land Mobile Network PMI precoder matrix indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS primary synchronization signal PUCCH Physical uplink control channel PUSCH Physical uplink shared channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSCP received signal code power RSRP reference symbol received power or reference signal received power RSRQ reference signal received quality or reference symbol received quality RSSI received signal strength indicator RSTD reference signal time difference SCH synchronization channel SCell secondary cell SDU service data unit SFN system frame number SGW serving gateway SI system information SIB system information block SNR signal-to-noise ratio SON self-optimizing network SS synchronization signal SSS secondary synchronization signal TDD time division duplex TDOA time difference of arrival TOA time of arrival TSS tertiary synchronization signal TTI transmission time interval UE user equipment UL uplink UMTS universal mobile telecommunications system USIM universal subscriber identity module UTDOA uplink time difference of arrival UTRA universal terrestrial radio access UTRAN universal terrestrial radio access network WCDMA wide CDMA WLAN wide area network The following includes an appendix derived from the provisional text. appendix Enhancements to uplink and downlink physical channels for NR URLLC Introduction At the RAN Plenary meeting in June 2018, the eURLLC study project

[00415] was approved. The purpose of the study project is to study the reliability and latency performance supported by NR Rel 15 and identify further enhancements if needed to achieve these requirements. The study project will, for example, study methods to further improve reliability and reduce latency for different use cases (such as factory automation, transportation industry, and power distribution) that have different requirements that may be more stringent than those considered in Rel-15. For example, some use cases considered in Rel-16 may require 1-10 -6Level 1 reliability and RAN latency of 0.5 to 1 ms. On the first layer enhancements, during the RAN1#94 meeting in Gothenburg

[00415] , the following agreements were made: Agreement: Further evaluate potential PDCCH enhancements for NR Rel-16 URLLC. Further evaluate PDCCH reliability. Further evaluate PDCCH blocking. Company describes resource utilization. Complexity should be considered. Enhanced latency should be considered.

[0203] Agreement: Further study on how to enable more than one PUCCH for HARQ-ACK transmission within a timeslot.

[0204] Agreement: Further study whether / how to implement enhanced reporting procedures / feedback for HARQ-ACK. Enhanced HARQ-ACK multiplexing on PUSCH and PUCCH. Finer indication for HARQ feedback timing, such as symbol level, half-slot, etc. Note: This may involve more than one PUCCH for HARQ-ACK tx within a slot. Other implementations are not excluded.

[0205] Agreement: Study the need for enhanced CSI reporting / measurement mechanisms. For example, DMRS-based CSI; A-CSI on PUCCH; triggered by DL assignment; enhanced CSI reporting mode. Other methods are not excluded.

[0206] discuss In the following, we discuss different enhancements to the physical channels including PUSCH, PDCCH and PUCCH in terms of latency and reliability. In order to achieve true high reliability and low latency for URLLC, aspects such as processing timeline and UE capabilities may also need to be addressed.

[0207] Enhancements on PUSCH reliability In Rel-16, different relevant use cases of eURLLC SI can be considered to have potentially different reliability requirements. In some use cases, for example, as mentioned in [1], -6 It is worth noting that techniques for enhancing reliability can be implemented at different layers in the protocol stack. Requirements 1-10 -6 Total transmission reliability does not necessarily mean that all solutions must come from the physical layer. For example, NR supports higher layer reliability enhancements in the form of PDCP duplication. With PDCP duplication, the reliability requirements on the physical layer can be relaxed.

[0208] In NR Rel.15, the corresponding 10 -5New CQI table for CQI reporting with BLER target. The present invention aims to support URLLC DL transmissions with high reliability requirements. In addition, new MCS tables supporting new MCS entries with low spectral efficiency values ​​are introduced to support very robust PDSCH and PUSCH transmissions. These PHY reliability enhancements made in NR Rel.15 can be considered sufficient for eURLLC.

[0209] Latency In terms of latency, NR Rel.15 supports data transmission with a duration shorter than the time slot. PDSCH / PUSCH mapping type B allows transmission to start in any symbol in the time slot, which makes it preferable from the perspective of latency. For PDSCH mapping type B, transmission durations of 2, 4, and 7 symbols are supported, while for PUSCH mapping type B, all symbol durations up to 14 symbols are supported. These features act as key elements to achieve the low-latency transmission required for URLLC.

[0210] However, there are still some limitations in scheduling flexibility in NR Rel.15 to fully realize ultra-low latency transmission. One example is the limitation on scheduling across slot boundaries. For URLLC services with strict delay budgets, it is very desirable that data be sent as quickly as possible. For example, it may happen that UL data for UL transmission is ready to be transmitted in a symbol that is too close to the slot boundary (after a certain processing time at the UE). Because NR Rel.15 does not allow transmission across slot boundaries, the UE must wait until the start of the next slot to be transmitted. This may result in increased delays that exceed the allowed budget.

[0211] See example Fig.15 is a diagram illustrating high alignment delay when data with 7-symbol duration arrives too close to a slot boundary. In the case of 7-symbol transmission, assuming data arrives uniformly, this alignment delay will occur in 50% of UL transmissions. This problem is particularly severe for UL transmissions where the UE is power limited, since increasing bandwidth does not help improve performance.

[0212] An alternative to waiting until the next timeslot is to schedule multiple transmissions with shorter durations so that the transmission can have already started in the current timeslot. Although NR Rel.15 supports timeslot aggregation, where a transmission can be repeated over multiple timeslots, there is a limitation that the TB repetitions in the following timeslots need to have the same resource allocation as the transmission in the first timeslot. Therefore, short transmissions (less than 14 symbols) repeated over multiple timeslots will have time gaps between them. For example, see the illustration for minislot aggregation, when a 4os minislot allocation is repeated in each timeslot forming a 10os time gap between transmissions.

[0213] In order to support true ultra-low latency transmission for eURLLC in Rel.16, it is proposed to support PUSCH scheduling across slot boundaries. This can take the form of having long transmissions that cross slot boundaries or other different scheduling flexibility to allow low latency transmissions across slot boundaries without excessive delay. We further study the impact of this enhancement on alignment delay in our paper

[00415] Scheme 1: NR Rel.16 for eURLLC supports more flexible PUSCH scheduling across slot boundaries. One possible solution to support PUSCH transmissions across slot boundaries is to use two PUSCH transmissions (see Fig.17 ). That is, the UE may expect to receive an UL grant or a configured UL grant that allocates resources across a time slot boundary in the time domain. The UE then interprets that the PUSCH transmission is split into two PUSCH transmissions. For example, Fig.17 As shown at the top of FIG. , UL data having a duration of N symbols is configured or scheduled to span time slots. Fig.17 As shown at the bottom of the , UL data is divided into two repetitions. The first PUSCH starts at the configured or allocated start symbol and ends at the end of the current time slot. The second PUSCH starts at the beginning of the subsequent time slot and ends at the symbol corresponding to the original configured or scheduled length.

[0214] A simple signaling approach may be based on implicit signaling, for example, by allowing a direct indicator of the start symbol (S) and the allocation length (L) in the time domain resource allocation to result in S+L>14, in which case the first PUSCH starts at the configured or scheduled start symbol and lasts until the end of the first time slot, and the second PUSCH starts immediately in the subsequent time slot until the end of the scheduled symbol. The MSC determination may be based on the number of resource elements used for the first and second PUSCH, respectively, where the same TBS may be used for both segments of the PUSCH transmission. The RV may follow some configured RV sequence.

[0215] Another approach discussed is based on mini-slot repetition. For mini-slot repetition, several factors should be considered. First, from a performance point of view, splitting the PUSCH into two PUSCHs has an advantage over repetition-based solutions due to improved coding gain in one segment. Second, the DMRS overhead in each repetition creates unnecessary extra overhead. Therefore, additional mechanisms should be considered to reduce the DMRS overhead. Third, the repetition-based solution cannot guarantee that the symbols around the slot boundaries are fully used for PUSCH transmission to reduce latency. Depending on the data arrival and the allocated PUSCH resources, the repetition factor should be adjusted dynamically. Since in Rel-15, slot aggregation is RRC configured, the introduction of this feature means that dynamic repetition should be supported in Rel-16 to make this feature meaningful.

[0216] In addition, reliability can be improved by frequency hopping. However, it should be considered whether frequency hopping results in a fragmented spectrum, thereby affecting the overall system performance. Therefore, frequency hopping should be dynamically enabled or disabled. In addition, if frequency hopping is enabled, it can be performed based on existing inter-slot and intra-slot frequency hopping. However, in some cases, it may not be desirable to have hopping positions in an asymmetric manner relative to the PUSCH allocation. In this case, a frequency hopping pattern may be considered, in which the hopping position is based on intra-slot frequency hopping with any one of a certain regular repetition, for example, a time slot with a greater number of symbols.

[0217] Based on the above discussion, we propose the following: Solution 2: Consider the following alternatives for PUSCH scheduling across slot boundaries: Alt 1) A method based on two PUSCH transmissions across slot boundaries based on implicit signaling by using the starting symbol (S) and allocation length (L) in time domain resource allocation and S+L>14.

[0218] The first PUSCH transmission starts at symbol S and lasts until the end of the slot.

[0219] The second PUSCH transmission starts at the beginning of the next slot including the remaining symbols.

[0220] The same or configured RV for two PUSCHs is for further study (FFS).

[0221] Alt 2) Method based on micro-slot repetition Support dynamic repetition Supports dynamic frequency hopping.

[0222] How to reduce DMRS overhead, FFS Investigate whether Alt 2 is beneficial in terms of performance and signaling overhead compared to Alt 1.

[0223] Enhancements on PDCCH During RAN1#94, several possibilities for PDCCH enhancement were discussed.

[0224] The companies agreed to further study PDCCH enhancements and consider different aspects, namely blocking, reliability and complexity

[00415] . In this section, we discuss the limitations on the number of blind decoding and CCEs used for URLLC, as well as the aspects of PDCCH blocking and possible improvements using compact DCI formats with smaller DCI sizes than fallback DCI.

[0225] Blind decoding and CCE number limitation are due to the latency (0.5-1ms) and reliability (1-10ms) mentioned in eURLLC SID [1]. -6 ), it is important to support PDSCH / PUSCH mapping Type B. In order to realize the full latency benefits of Type B scheduling, it is necessary to have multiple PDCCH monitoring opportunities within a timeslot. For example, to obtain the full benefit of 2 OFDM symbol transmission, it is preferable to have PDCCH monitoring every 2 OFDM symbols. The restrictions in Rel.15 on the total number of CCEs and blind decodings for channel estimation in a timeslot strongly constrain the scheduling options for these kinds of configurations, even when limiting the number of candidates in the search space. In this section, we provide views on how this restriction should be relaxed for NR URLLC Rel.16.

[0226] In LTE, the number of blind decodes increases with the introduction of sTTI. This is due to the new sTTI structure, where 2 or 3 OS subslots (corresponding to 6 monitoring opportunities within a subframe) and 7 OS slots (corresponding to 2 monitoring opportunities within a subframe) are supported. The baseline for one component carrier in LTE is 44 blind decodes per 1ms subframe, of which 12 are used for CSS and 32 for USS. For sTTI, there can be 24 additional BDs with 1 slot sTTI, and 36 additional BDs with 2 / 3 OS sTTIs. Therefore, the total number of blind decodes per 1ms subframe in LTE increases, as summarized in the following table.

[0227] Based on the analysis in the accompanying document

[00415] , a PDCCH monitoring period of at least less than 5 symbols is necessary to meet the LMS delay target. PDCCH monitoring periodicity means, for example, that the PDCCH may start at symbols 0, 5, and 10 in a slot, resulting in 3 monitoring opportunities in the slot.

[0228] Table 8: Number of blind decodings for LTE with sTTI Observation 1: To support URLLC with a latency requirement of 1 ms, more than three PDCCH monitoring opportunities are needed per slot.

[0229] If AL=16 is required, these three monitoring opportunities occupy 48 of the 56 allowed CCEs for channel estimation in Rel. 15, severely limiting both USS and CSS for scheduling URLLC services.

[0230] The above observations are merely the minimum number of monitoring opportunities required to support at least a single transmission of a 15kHz SCS that meets the URLLC latency requirements. As mentioned earlier, the number of monitoring opportunities for NR in a time slot can in principle be flexible, i.e., any number from every 1 to 14os. As can be seen in

[00415] , allowing more PDCCH monitoring opportunities per time slot allows URLLC services to be scheduled using retransmission opportunities, which results in more efficient resource usage.

[0231] Instead of specifying multiple new UE capability levels, it is proposed to specify one additional level supporting PDCCH blind decoding, for which the number is doubled compared to Rel.15.

[0232] For this additional level of support, instead of simply defining it on a per-slot basis, it makes more sense to consider how the BD / CCE are distributed in the slots for mini-slot operation. One possible option is to define a BD / CCE limit for each half of the slot. For the first half of the slot, it is natural to assume the same number as in the other cases. For the second half of the slot, assuming that the UE has completed PDCCH processing in the first half of the slot, the UE should have the same PDCCH processing capability in the second half of the slot. Therefore, it is reasonable to assume the same number as in the first slot.

[0233] Based on the above analysis, a corresponding increase in BD restrictions is proposed: Table 9: Number of blind decodings for Rel.15 and recommended values ​​for Rel.16.

[0234] Similarly, a corresponding increase in the CCE limit is proposed: Table 10: CCE limits for Rel.15 and recommended values ​​for Rel.16.

[0235] For example, for 120kHz SCS, the existing limit is 32 CCEs per timeslot, and there can be at most two AL16 candidates per timeslot, which may be very limiting for URLLC which requires at least two monitoring opportunities in a timeslot. The proposed value will allow more flexible PDCCH scheduling and reduce the blocking probability. As an alternative solution to Tables 2 and 3, introducing restrictions on each sliding window can be considered, where the size of the sliding window and the number of blind decoding or CCEs per window can be further discussed. For NR URLLC Rel.16, refer to Fig.16 , the following number of blind decodings and CCEs for channel estimation can be considered.

[0236] Proposal 3: For NR Rel.16 considering URLLC, for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of PDCCH blind decodings for the PDCCH monitoring occasions with the first symbol in the first half slot is {44, 36, 22, 20}, and for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of PDCCH blind decodings for the first symbol in the second half slot is {44, 36, 22, 20}.

[0237] Proposal 4: For NR Rel.16 considering URLLC, for SCS {15kHz, 30kHz, 60kHz, SCS}, the number of CCEs for channel estimation of (one or more) PDCCH monitoring opportunities for the (one or more) first symbols in the first half of the time slot is {56, 56, 48, 32}, and for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of (one or more) PDCCH monitoring opportunities for the (one or more) first symbols in the second half of the time slot is {56, 56, 48, 32}.

[0238] PDCCH blocking High PDCCH reliability is crucial to meet URLLC reliability requirements. The NR PDCCH design addresses this aspect with support for AL16. However, there are still some concerns about PDCCH resource usage. Namely, if there are multiple UEs scheduled simultaneously and some of them require high AL, the available control resources may not be sufficient to schedule all UEs and PDCCH blocking starts to occur.

[0239] In our companion paper [5], the PDCCH blocking probability is evaluated for the macro scenario. The DL geometry is derived and used together with the PDCCH link level results to obtain the PDCCH reliability target 10 -5We observe that the blocking probability generally depends on several parameters, such as the number of UEs, CORESET size, DCI size, and traffic model. Figure 4 From the results shown, it can be seen that it makes more sense to use a larger CORESET size to reduce the blocking probability.

[0240] Using smaller DCI sizes, such as compact DCI, can reduce the blocking probability, but only to a small extent. Moreover, the introduction of compact DCI has other consequences, such as increased blind decoding complexity at the UE and reduced data scheduling flexibility. All these aspects must be taken into account. If the goal is to increase the blocking probability to a level relevant for URLLC, relying on compact DCI may not be the right approach. Fig.18 The blocking probability is shown as a function of the number of UEs, DCI size and CORESET size.

[0241] Proposal 5: Considering the additional complexity of introducing a new DCI format, consider the trade-off between PDCCH blocking reduction and PDSCH scheduling flexibility by using compact DCI.

[0242] Enhancements to UE processing timeline DL data transmission timeline Fig.19 The UL data transmission timeline is shown in Fig. 20 For PUSCH via a configured UL grant, the delay components are shown in the following table: Table 11 T UE,Proc It is an important latency component to be improved. In Release 15, UE processing time capabilities #1 and #2 have been defined, where capability #1 is defined as SCS of 15 / 30 / 60 / 120kHz, and capability #2 is defined as SCS of 15 / 30 / 60kHz. The evaluation results in

[00415] show that the more aggressive capability #2 is still insufficient for the 1ms latency constraint. For eURLLC, delays less than 1ms (e.g. 0.5ms) need to be studied. In order to meet the latency requirements, we recommend defining capability 3 in Release 16.

[0243] Table 12: UE processing time capability #3 Proposal 6: Define more aggressive UE processing time capability #3 for Release 16.

[0244] Proposal 7: For 15 / 30 / 60 / 120kHz SCS, UE processing time capability #3 is 2.5 / 2.5 / 5 / 10OS.

[0245] Although N1 gives the minimum number of OFDM symbols from the end of the PDSCH to the start of the HARQ-ACK transmission on the PUCCH, the actual transmission time of the HARQ-ACK is also limited by the timing allowed within the time slot. In Release 15, each time slot supports at most one PUCCH transmission including HARQ-ACK. This will increase the alignment time for sending HARQ-ACK. In order to reduce DL data latency, it is necessary to increase the number of PUCCH opportunities for HARQ-ACK transmission in the time slot, especially when supporting eMBB and URLLC service multiplexing.

[0246] Proposal 8: Support at least two PUCCH transmissions for HARQ-ACK in a slot of Rel-16.

[0247] For T DL,align , which is significantly affected by the PDCCH period. The worst case T DL,align =Equal to the PDCCH periodicity. In Rel-15, the PDCCH periodicity is subject to several constraints, including: (a) blind decoding restrictions, (b) #CCE restrictions, and (c) DCI size. In order to provide a shorter PDCCH periodicity for eURLLC, it is necessary to add blind decoding restrictions and #CC# restrictions in Rel-16. This will be discussed in Section 2.2.2.

[0248] UCI Transmission Enhancements For UEs running hybrid services with eMBB and URLLC, the reliability requirements on UCI transmitted on PUSCH may be significantly different from those for PUSCH data. The reliability requirements for UCI may be higher than those for PUSCH data, for example when HARQ-ACK for DL ​​URLLC data is transmitted simultaneously with eMBB data, or, lower, for example when CQI reports for eMBB are transmitted simultaneously with URLLC data. In cases where the requirements for UCI are lower than for PUSCH data, it may be desirable to discard some or all of the UCI.

[0249] Observation 2: For UEs supporting both eMBB and URLLC, the reliability requirements for UCI and ETL data may differ significantly. Either UCI or PUSCH data may require higher reliability. The resource division between UCI and PUSCH data is controlled by a beta factor for the various UCIs. The minimum value of the beta factor defined in Rel.15 is 1.0. This value may not be low enough when URLLC data is considered together with eMBB UCI.

[0250] Proposal 9: Consider increasing the range of the beta factor in Rel. 16 to include values ​​less than 1.0 (including as low as 0.0), allowing HARQ-ACK / CSI bits to be dropped from UCI.

[0251] In our accompanying paper

[00415] , it is observed that when UCI is transmitted on PUCCH, the reliability requirements may also differ significantly if the UCI is related to eMBB or eTLLC. In particular, HARQ-ACK related to eMBB does not need to be as reliable as HARQ-ACK involving URLLC. In our paper, it is observed that for PUCCH formats 0 and 1, suitable methods for controlling reliability are limited to the selection of number of symbols and / or power adjustment. It is also observed that NR Rel-15 does not support the use of power control to quickly adjust reliability. In some cases, using symbol number selection to adjust reliability may not be sufficient in mixed service scenarios. Therefore, we propose: Proposal 10: Consider enhancing PUCCH power control to achieve a larger power difference between PUCCH transmissions associated with eMBB and PUCCH transmissions associated with URLLC: (1) new TPC tables allowing larger power adjustment steps, and / or (2) dynamically indicating the power setting indicated using DCI (e.g., P0, closed-loop index) in conclusion In this section, we discuss potential L1 enhancements for NR operations of URLLC services supported in Release 16. Based on the discussion, we make the following observations and proposals: Observation 1 To support URLLC with a latency requirement of 1 ms, more than three PDCCH monitoring opportunities are needed per slot.

[0252] Observation 2 For UEs supporting both eMBB and URLLC, the reliability requirements for UCI and UL data may differ significantly. Either UCI or PUSCH data may require higher reliability.

[0253] Proposal 1: NR Rel.16 for eURLLC supports more flexible PUSCH scheduling across slot boundaries.

[0254] Proposal 2 considers the following alternatives for PUSCH scheduling across slot boundaries: Alt 1) A method based on two PUSCH transmissions across slot boundaries, which is based on implicit signaling, achieved by using the start symbol (S) and allocation length (L) in the time domain and resource allocation S+L>14. The first PUSCH transmission starts from symbol S and continues until the end of the slot. The second PUSCH transmission starts at the beginning of the next slot including the remaining symbols. Regarding the same or configured RV for two PUSCHs, FFS. Alt 2) A method based on mini-slot repetition. Support for dynamic repetition. Support for dynamic frequency hopping. Regarding how to reduce DMRS overhead, FFS. Study whether Alt 2 is beneficial in terms of performance and signal strength overhead compared to Alt 1.

[0255] Proposal 3 For NR Rel.16 considering URLLC, for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of PDCCH blind decodings for (one or more) PDCCH monitoring opportunities of (one or more) first symbols in the first half of the time slot is {44, 36, 22, 20}, and for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of PDCCH blind decodings for (one or more) first symbols in the second half of the time slot is {44, 36, 22, 20}.

[0256] Proposal 4 For NR Rel.16 considering URLLC, for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of CCEs for channel estimation of (one or more) PDCCH monitoring opportunities of (one or more) first symbols in the first half of the time slot is {56, 56, 48, 32}, and for SCS {15kHz, 30kHz, 60kHz, 120kHz}, the number of CCEs for channel estimation of (one or more) PDCCH monitoring opportunities of (one or more) first symbols in the second half of the time slot is {56, 56, 48, 32}.

[0257] Proposal 5 Considering the additional complexity of introducing a new DCI format, a trade-off between PDCCH blocking reduction and PDSCH scheduling flexibility is considered when using compact DCI.

[0258] Proposal 6 defines a more aggressive UE processing time capability #3 for Release 16.

[0259] Proposal 7 For 15 / 30 / 60 / 120kHz SCS, UE processing time capability #3 is 2.5 / 2.5 / 5 / 10OS.

[0260] Proposal 8 supports at least two PUCCH transmissions for HARQ-ACK in a slot of Rel-16.

[0261] Proposal 9 considers increasing the range of the beta factor in Rel. 16 to include values ​​less than 1.0 (including as low as 0.0), thereby allowing HARQ-ACK / CSI bits to be dropped from the UCI.

[0262] Proposal 10 considers enhancing PUCCH power control to achieve a larger power difference between PUCCH transmissions related to eMBB and PUCCH transmissions related to URLLC: new TPC tables allow larger power adjustment steps and / or dynamic indication of power settings using DCI indications (e.g. P0, closed-loop index).

[0263] References. [1] RP-181477 New SID for Physical Layer Enhancements for NR URLLC, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell. [2] RAN1#94 Chairman’s Notes. [3] R-1811112 Study on Aligned Delay for URLLC Latency, Ericsson, October 2018. [4] R-1810177Rel-15 Latency Evaluation for URLLC, Ericsson, October 2018. [5] R1-1811109 Performance Evaluation of PDCCH for URLLC, Ericsson, October 2018. [6] Rl-1811111 Enhancements to Uplink Power Control for NR URLLC, Ericsson, October 2018.

[0264] Although various embodiments are described herein, it should be understood that they are provided by way of example only and not by way of limitation. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments. Moreover, unless otherwise noted herein or clearly contradictory to the context, the present disclosure encompasses any combination of the above elements in all possible variations thereof.

[0265] In addition, although the processes described above and shown in the accompanying drawings are shown as a sequence of steps, this is done for illustrative purposes only. Therefore, it is expected that some steps may be added, some steps may be omitted, the order of the steps may be rearranged, and some steps may be performed in parallel. Similarly, the phrase "received from..." should be interpreted as covering "received directly from..." or "received indirectly from...". That is, the first entity receives the message from the second entity even in the case where the third entity receives the message transmitted by the second entity and then forwards the message to the first entity.

Claims

1. A method (1100) for repeating signaling performed by a user equipment UE (210, 300, 592, 630, 1300), the method comprising: receiving (1102) from a base station a configuration message transmitted via radio resource control RRC signaling and downlink control information DCI transmitted on a physical downlink control channel PDCCH, the configuration message comprising time domain resource allocation TDRA configuration information, and the DCI comprising an indication of an index value; as well as A parameter set is obtained (1104) from the TDRA configuration information using the index value, the parameter set including a repetition factor.

2. The method according to claim 1, wherein: The TDRA configuration information includes at least one of a physical uplink shared channel (PUSCH) TDRA configuration or a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set further includes a time slot offset, a mapping type, and at least one of: (i) a start symbol and an allocation length, or (ii) a start and length indicator variable.

3. The method according to claim 1, wherein: The parameter set also includes an indication to use at least one of back-to-back repetition or slot aggregation of transmissions according to the aggregation factor.

4. The method according to claim 1, further comprising: determining that using back-to-back repetitions with the repetition factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as well as, As a result of said determining: said at least one transmission at least partially occupying said second time slot is divided into a plurality of transmissions, each transmission occupying only one time slot.

5. The method according to claim 1, further comprising: determining that using back-to-back repetitions with the repetition factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as well as, As a result of the determination: (i) it is determined that the at least one transmission that at least partially occupies the second time slot is not received, (ii) a shortened transmission of the at least one transmission that at least partially occupies the second time slot is received, so that the shortened transmission no longer at least partially occupies the second time slot, or (iii) a split transmission of the at least one transmission that at least partially occupies the second time slot is received, so that the split transmission includes multiple transmissions, each transmission occupying only one time slot.

6. The method according to claim 1, wherein: The repetition factor indicates at least one of the number of single repetitions or the number of time slots that a resource allocation should be repeated.

7. The method according to claim 1, wherein: The aggregation factor is a split factor or partition indicator that indicates that the transmission defined by the start S and length L should be divided into two or more repetitions.

8. A method (1200) for repeating signaling performed by a base station (260, 420, 430, 512, 620, 1300), the method comprising: generating (1202) a configuration message for transmission via radio resource control RRC signaling and downlink control information DCI for transmission on a physical downlink control channel PDCCH, the configuration message comprising time domain resource allocation TDRA configuration information, the TDRA configuration information comprising a repetition factor, and the DCI comprising an indication of an index value; and The configuration message is transmitted (1204) to a user equipment UE via RRC signaling and the DCI is transmitted (1204) on the PDCCH.

9. The method according to claim 8, wherein: The TDRA configuration information includes at least one of a physical uplink shared channel (PUSCH) TDRA configuration or a physical downlink shared channel (PDSCH) TDRA configuration, and the parameter set further includes a time slot offset, a mapping type, and at least one of: (i) a start symbol and an allocation length, or (ii) a start and length indicator variable.

10. The method according to claim 8, wherein: The TDRA configuration information further includes an indication for the UE to use at least one of back-to-back repetition or timeslot aggregation of transmissions according to the repetition factor.

11. The method according to claim 8, further comprising: determining that using back-to-back repetitions with the repetition factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as well as, As a result of said determining: receiving a split transmission of said at least one transmission at least partially occupying said second time slot, such that said split transmission comprises a plurality of transmissions, each transmission occupying only one time slot.

12. The method according to claim 8, further comprising: determining that using back-to-back repetitions with the repetition factor will result in a first transmission occupying a first time slot and at least one transmission at least partially occupying a second time slot different from the first time slot; as well as, As a result of the determination: (i) it is determined not to transmit the at least one transmission that at least partially occupies the second time slot, (ii) the at least one transmission that at least partially occupies the second time slot is shortened so that it no longer at least partially occupies the second time slot, or (iii) the at least one transmission that at least partially occupies the second time slot is divided into multiple transmissions, each transmission occupying only one time slot.

13. The method according to claim 8, wherein: The repetition factor indicates the number of single repetitions or the number of time slots that a resource allocation should be repeated.

14. The method according to claim 8, wherein: The aggregation factor is a split factor or partition indicator that indicates that the transmission defined by the start S and length L should be divided into two or more repetitions.

15. A tangible, non-transitory, device-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform the method of any one of claims 1-7.

16. A tangible, non-transitory, device-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform the method of claims 8-14.

17. A user equipment UE (210, 300, 592, 630, 1300) for repeated signaling, wherein the UE is adapted to perform the method according to any one of claims 1-7.

18. A base station (260, 420, 430, 512, 620, 1300) for repeated signaling, comprising a processing circuit and a memory, wherein The base station is adapted to perform the method according to any one of claims 8-14.

Images