Selection of time domain resource allocation table
By sharing multiple time domain resource allocation tables between wireless devices and network nodes, and using information in DCI to select appropriate table entries, the problem of limited time domain resource allocation tables in NR is solved, and a more flexible time domain is achieved Improvement of resource scheduling and communication efficiency.
Patent Information
- Application Number
- CN202210610052.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-11-17
- Filing Date
- 2018-11-16
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2038-11-16
AI Technical Summary
New radio (NR) is too limited when using a single time domain resource allocation table in downlink control information (DCI), limiting scheduling flexibility. Increasing the resource allocation table size will increase the number of bits of DCI, which is not conducive to communication efficiency. .
Wireless devices and network nodes determine one of the multiple time domain resource allocation tables through the received information, and use the time domain resource allocation field in DCI to select appropriate table entries to achieve flexible allocation of time domain resources without explicit addition. The number of bits of DCI.
Without increasing the number of DCI bits, the scheduling flexibility of time domain resources is improved, and the flexibility and efficiency of wireless communication is enhanced.
Smart Images

Figure CN114978460B_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese patent application with application number 201880074123.6. The application date of the original application is November 16, 2018, the priority date is November 17, 2017, the date of entering the Chinese national phase is May 15, 2020, and the name of the invention is "Selection of time domain resource allocation table". Technical Field
[0002] Certain embodiments of the present disclosure relate generally to wireless communications and, more particularly, to selection of a time domain resource allocation table. Background Art
[0003] New Radio (NR) will support a bit field in the Downlink Control Information (DCI) to select the time domain resource allocation for the Physical Uplink Shared Channel (PUSCH) and Physical Downlink Shared Channel (PDSCH) from pre-configured entries in a table. Each entry in the table specifies the starting Orthogonal Frequency Division Multiplexing (OFDM) symbol of the allocation and the OFDM symbol length. Note that the starting OFDM symbol can be expressed relative to the scheduled Physical Downlink Control Channel (PDCCH) / Control Channel Resource Set (CORESET) symbol, or can be expressed in terms of an absolute OFDM symbol number within a slot or subframe. Summary of the invention
[0004] There are certain challenges. Although NR is very flexible, for example because it supports different ways of how to distribute system information and supports both slot-based and non-slot-based transmissions, the use of a single time domain resource allocation table is very limited and can restrict scheduling in many cases. One possible solution is to increase the resource allocation table size, thereby enabling more time domain resource allocations. However, the disadvantage of this solution is that it increases the downlink control information (DCI) size, since more bits are needed to select the appropriate resource allocation.
[0005] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. According to certain embodiments, a wireless device (e.g., a user equipment UE) is configured with multiple time domain resource allocation tables. Which table to use is implicitly derived from other information available at both the network node (e.g., gNB) and the wireless device. Examples of this other information may be a radio network temporary identifier (RNTI), information contained in the DCI, which DCI format has been used for scheduling, which CORSET / search space has been used for scheduling, whether the transmission is slot-based or non-slot-based, information related to carrier aggregation, information related to bandwidth parts, slot formats, and / or information indicating parameter sets (e.g., cyclic prefix, OFDM subcarrier spacing, etc.). According to certain embodiments, if the time domain resource allocation is used for scheduling of system information (e.g., remaining minimum system information (RMSI)), the manner in which the system information is distributed (non-slot-based transmission versus slot-based transmission) determines which table to use. According to certain embodiments, a wireless device configured with multiple time domain resource allocation tables derives which table to use from information available at the wireless device and selects an entry from the table based on an explicit bit field in the DCI, which may be referred to as a time domain resource allocation field.
[0006] According to certain embodiments, a wireless device includes a memory and a processing circuit. The memory is operable to store instructions, and the processing circuit is operable to execute the instructions, whereby the wireless device is operable to determine one of a plurality of time domain resource allocation tables based on first information received from a network node. Based on the determined time domain resource allocation table of the plurality of time domain resource allocation tables and second information received from the network node, the wireless device is operable to determine a time domain resource allocated to the wireless device for sending or receiving a wireless signal. The second information is different from the first information.
[0007] According to certain embodiments, a method performed by a wireless device includes determining a time domain resource allocation table from a plurality of time domain resource allocation tables based on first information received from a network node. The method also includes determining a time domain resource allocated to the wireless device for transmitting or receiving a wireless signal based on the determined time domain resource allocation table from the plurality of time domain resource allocation tables and second information received from the network node. The second information is different from the first information.
[0008] According to some embodiments, the computer program includes instructions that, when executed by at least one processor of the wireless device, cause the wireless device to determine one of a plurality of time domain resource allocation tables based on first information received from a network node, and determine a time domain resource allocated to the wireless device for sending or receiving a wireless signal based on the determined time domain resource allocation table in the plurality of time domain resource allocation tables and second information received from the network node. The second information is different from the first information. In some embodiments, the carrier containing the computer program is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.
[0009] According to certain embodiments, the wireless device is operable to determine one of a plurality of time domain resource allocation tables based on first information received from a network node. Based on the determined time domain resource allocation table of the plurality of time domain resource allocation tables and second information received from the network node, the wireless device is operable to determine time domain resources allocated to the wireless device for sending or receiving wireless signals. The second information is different from the first information.
[0010] The wireless device, the method executed by the wireless device and / or the computer program described above may each include one or more additional features, such as any one or more of the following features:
[0011] In some embodiments, the second information comprises a time domain resource allocation field received in a DCI.
[0012] In some embodiments, one of the plurality of time domain resource allocation tables determined based on the first information includes a plurality of entries, and the second information indicates which entry of the plurality of entries is to be used to determine the time domain resources allocated to the wireless device.
[0013] In some embodiments, the time domain resource allocation table includes different combinations of starting OFDM symbol positions and OFDM symbol durations for time domain resource allocation.
[0014] In some embodiments, the plurality of time domain resource allocation tables are related to time domain resource allocation for PUSCH or for PDSCH.
[0015] In some embodiments, the plurality of time domain resource allocation tables include at least one of a predefined table with default values for time domain resource allocation and an RRC configuration table. That is, the plurality of time domain resource allocation tables include a predefined table with default values for time domain resource allocation and / or an RRC configuration table.
[0016] In some embodiments, the first information comprises a Radio Network Temporary Identifier (RNTI).
[0017] In some embodiments, the first information includes information indicating a search space related to a control channel used to schedule wireless signals.
[0018] In some embodiments, the first information includes information related to a CORESET used to schedule the wireless signal.
[0019] In some embodiments, the first information includes information related to the bandwidth portion.
[0020] In some embodiments, the first information includes information indicating a time slot format.
[0021] In some embodiments, the first information includes a cyclic prefix, an OFDM subcarrier spacing, or other information indicating a parameter set.
[0022] In some embodiments, wireless signals are transmitted or received using the determined time domain resources.
[0023] According to some embodiments, a network node includes a memory and a processing circuit. The memory is operable to store instructions, and the processing circuit is operable to execute the instructions, whereby the network node is operable to determine a time domain resource to be allocated to a wireless device for sending or receiving a wireless signal. The network node is also operable to send first information and second information to the wireless device, wherein the wireless device determines one of a plurality of time domain resource allocation tables according to the first information, and the wireless device determines the time domain resource based on the determined time domain resource allocation table in the plurality of time domain resource allocation tables and the second information. The second information is different from the first information.
[0024] According to certain embodiments, a method performed by a network node includes determining a time domain resource to be allocated to a wireless device for transmitting or receiving a wireless signal. The method also includes sending first information and second information to the wireless device, wherein the wireless device determines one of a plurality of time domain resource allocation tables based on the first information, and the wireless device determines the time domain resource based on the determined time domain resource allocation table in the plurality of time domain resource allocation tables and the second information. The second information is different from the first information.
[0025] According to some embodiments, the computer program includes instructions that, when executed by at least one processor of a network node, cause the network node to determine a time domain resource to be allocated to a wireless device for sending or receiving a wireless signal. The instructions also cause the network node to send first information and second information to the wireless device, wherein the wireless device determines one of a plurality of time domain resource allocation tables according to the first information, and the wireless device determines the time domain resource based on the determined time domain resource allocation table in the plurality of time domain resource allocation tables and the second information. The second information is different from the first information. In some embodiments, the carrier containing the computer program is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.
[0026] According to certain embodiments, a network node is operable to determine a time domain resource to be allocated to a wireless device for transmitting or receiving a wireless signal. The network node is further operable to send first information and second information to the wireless device, wherein the wireless device determines one of a plurality of time domain resource allocation tables according to the first information, and the wireless device determines the time domain resource based on the determined one of the plurality of time domain resource allocation tables and the second information. The second information is different from the first information.
[0027] The above network node, the method executed by the network node and / or the computer program may each include one or more additional features, such as any one or more of the following features:
[0028] In some embodiments, the second information comprises a time domain resource allocation field sent in a DCI.
[0029] In some embodiments, a time domain resource allocation table of the plurality of time domain resource allocation tables comprises a plurality of entries. The second information indicates which entry of the plurality of entries the wireless device should use to determine the time domain resource.
[0030] In some embodiments, the time domain resource allocation table includes different combinations of starting OFDM symbol positions and OFDM symbol durations for time domain resource allocation.
[0031] In some embodiments, the plurality of time domain resource allocation tables are related to time domain resource allocation for PUSCH or for PDSCH.
[0032] In some embodiments, the plurality of time domain resource allocation tables comprises a predefined table and / or an RRC configuration table having default values for time domain resource allocation.
[0033] In some embodiments, the first information includes a RNTI.
[0034] In some embodiments, the first information includes information indicating a search space related to a control channel used to schedule wireless signals.
[0035] In some embodiments, the first information includes information related to a CORESET used to schedule the wireless signal.
[0036] In some embodiments, the first information includes information related to the bandwidth portion.
[0037] In some embodiments, the first information includes information indicating a time slot format.
[0038] In some embodiments, the first information includes a cyclic prefix, an OFDM subcarrier spacing, or other information indicating a parameter set.
[0039] In some embodiments, the allocated time domain resources are used to send or receive wireless signals.
[0040] Various embodiments are proposed herein to solve one or more of the problems disclosed herein. Certain embodiments may provide one or more of the following technical advantages. Certain embodiments allow for more flexible scheduling of time domain resources without increasing the number of DCI bits. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 Examples of multiple time-domain resource allocation tables according to certain embodiments are shown.
[0042] Figure 2 An example of a method for use in a wireless device according to some embodiments is shown.
[0043] Figure 3 An example of a method for use in a wireless device according to some embodiments is shown.
[0044] Figure 4 An example of a method for use in a network node according to some embodiments is shown.
[0045] Figure 5 A schematic block diagram is shown of an apparatus in a wireless network according to some embodiments.
[0046] Figure 6 An example of a wireless network in accordance with some embodiments is shown.
[0047] Figure 7 An example of a user equipment according to some embodiments is shown.
[0048] Figure 8 An example of a virtualized environment is shown in accordance with some embodiments.
[0049] Fig. 9 An example of a telecommunications network connected to a host computer via an intermediary network is shown in accordance with some embodiments.
[0050] Fig.10 An example of a host computer communicating with a user device via a base station over a partially wireless connection is shown in accordance with some embodiments.
[0051] Fig.11 An example of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.
[0052] Fig.12 An example of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.
[0053] Fig.13An example of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.
[0054] Fig.14 An example of a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown. DETAILED DESCRIPTION
[0055] Generally, unless clearly given and / or implied different meanings in the context of using the term, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless clearly stated, all references to one / an / the element, equipment, assembly, parts, step, etc. should be publicly interpreted as referring to at least one instance of the element, device, assembly, parts, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.
[0056] 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 merely as examples to convey the scope of the subject matter to those skilled in the art. Additional information can also be found in Appendix A and Appendix B.
[0057] Figure 1 A wireless device configured with multiple (two in the example) time domain resource allocation tables is shown. Examples of time domain resource allocation tables include a predefined table with default values for time domain resource allocation, a table configured using RRC signaling, and a combination of a predefined table and an RRC configuration table. The time domain resource allocation table indicates the allocation of time domain resources (such as time domain resources of a PUSCH or PDSCH) for sending or receiving wireless signals. In some embodiments, the time domain resource allocation table indicates the allocation of time domain resources with respect to OFDM symbols. For example, Figure 1It is shown that the time domain resource allocation table includes different combinations of starting OFDM symbol positions and durations in OFDM symbols used for time domain resource allocation. It can be seen that the time domain resource allocation table includes multiple entries, and different table entries can differ in at least one of the OFDM start symbol and / or the scheduled OFDM symbol duration. Any two parameters selected from the start symbol, the stop symbol and the symbol duration (e.g., the start symbol and the stop symbol, the start symbol and the duration, or the stop symbol and the duration) can be used to indicate the OFDM symbol. The start symbol can be absolute relative to the time slot boundary or relative to the scheduled DCI / CORESET. Different tables can also have different definitions regarding the start (or end) OFDM symbol. For example, some tables can use the absolute OFDM symbol number of the time slot to indicate the start (or end) OFDM symbol, while other tables can indicate the start (or end) symbol relative to the PDCCH / CORESET symbol used to schedule PDSCH / PUSCH. Absolute numbering can be useful for time slot-based transmission or type A transmission, while relative numbering can be preferred by non-time slot-based transmission or type B transmission. In principle, different tables can have different numbers of entries; however, Figure 1 In the examples shown, it is assumed that the number of entries in each table is the same.
[0058] The wireless device determines which time domain resource allocation table to use based on first information received from a network node, such as a base station. The wireless device determines the time domain resources allocated to the wireless device based on the time domain resource allocation table determined according to the first information and based on second information received from the network node. The second information is different from the first information. In some embodiments, the second information indicates which entry of the determined table is to be used to determine the time domain resources allocated to the wireless device. For example, the second information may include a time domain resource allocation field, such as a bit field, received in a DCI. Figure 1 In the example shown, each table includes four entries, so that a time domain resource allocation field including a two-bit wide bit field can be used to select one of the four entries in the table (e.g., "00" selects the first entry, "01" selects the second entry, "10" selects the third entry, and "11" selects the fourth entry).
[0059] As described above, the wireless device determines the table based on the first information. The first information includes information other than the time domain resource allocation field received in the DCI. Examples of this other information may be a radio network temporary identifier (RNTI), information contained in the DCI, which DCI format has been used for scheduling, which CORSET / search space has been used for scheduling, whether the transmission is slot-based or non-slot-based, information related to carrier aggregation, information related to bandwidth parts, slot formats, and / or information indicating parameter sets (e.g., cyclic prefix, OFDM subcarrier spacing, etc.), as further described below.
[0060] In some embodiments, the first information may be another field in the DCI that has been signaled for another purpose (i.e., a field other than the time domain resource allocation field). For example, if the DCI includes a bit for distinguishing between type A scheduling and type B scheduling, the bit may be used to select Figure 1 One of the two tables in . Another example can be a bit used to distinguish between slot-based transmissions and non-slot-based transmissions. Slot-B scheduling, non-slot-based transmissions, and mini-slots are transmissions that are usually short in duration. Slot-based transmissions usually have a transmission length in the order of slots. Therefore, it makes sense to use two different time domain resource allocation tables based on the Type A / Type B or non-slot-based transmission / slot-based transmission distinguisher bit.
[0061] If multi-slot scheduling is dynamically indicated in the DCI using a multi-slot indicator bit, this bit can be used as the first information to distinguish the time domain resource allocation table to be used for single-slot and multi-slot (time slot aggregation) transmission. In these two cases, the resource allocation is obviously different. In addition to the symbol information, the multi-slot time domain resource allocation can also contain time slot information. Here, if the multi-slot indicator bit is set to achieve more time domain resource allocation, the time domain resource allocation field received in the DCI can be a larger bit field. If multi-slot scheduling is not indicated via the multi-slot indicator bit in the DCI, but is indicated in any other way, the same principle applies.
[0062] Certain embodiments of the present disclosure use a DCI format (e.g., a conventional DCI or a fallback DCI) as the first information for selecting a time domain resource allocation table. For example, for NR, the use of two different DCI variants has been discussed in 3GPP. The first variant is a conventional DCI that can be used for all types of signaling or configuration required. The size and format of this conventional DCI varies depending on the usage (i.e., depending on the actual RRC configuration), similar to the LTE DCI format to some extent. The second variant is a fallback DCI with a fixed and predefined size. During RRC reconfiguration, when there may be a period of configuration uncertainty (during which it is valuable to make the fixed-size DCI known to both the network and the UE), a fixed-size fallback DCI is generally required to limit the impact of configuration uncertainty on wireless communication. The problem of configuration uncertainty occurs when the network does not know when the UE applies the RRC reconfiguration. For example, the UE may have to list the information, or multiple retransmissions may be required before the RRC command reaches the UE. Therefore, there is a period when the UE may have applied the new configuration but the network does not know the new configuration, and vice versa. Therefore, during this period, a communication method that both parties are "always" aware of is needed, and this need is met by using a non-configurable fallback DCI.
[0063] The wireless device may be configured with multiple control channel resource sets (CORESETs), and each CORESET may contain one or more search spaces. The CORESETs and / or search spaces that have been used for scheduling transmissions may be used as first information for determining a time domain resource allocation table.
[0064] The DCI contains a downlink / uplink (DL / UL) indicator bit, which indicates whether the transmission is DL or UL. Due to the difference in frame structure and different processing times between DL allocation reception → DL data reception and UL grant reception → UL data transmission, different time domain resource allocations may be required for DL and UL. Therefore, the DL / UL indicator bit can be used as the first information for determining the time domain resource allocation table.
[0065] In the case of carrier aggregation, the wireless device is configured with multiple carriers. Different carriers may have different sets of parameters and different requirements for coexistence with Long Term Evolution (LTE), and are set up with different DL / UL configurations. Then, it makes sense to support different time domain resource allocations for different carriers. Therefore, depending on the scheduled carrier, a time domain resource allocation table is selected (i.e., the scheduled carrier can be used as the first information for determining the time domain resource allocation table). If cross-carrier scheduling is not applied (i.e., the PDCCH is sent on the same carrier as the PDSCH or on a carrier associated with the PUSCH carrier), the carrier on which the scheduled DCI is sent determines the time domain resource allocation table. If cross-carrier scheduling is used (i.e., the PDCCH is sent on another carrier as the PDSCH or on a carrier associated with the PUSCH carrier), the information in the DCI or how the DCI is sent indicates the PDSCH / PUSCH carrier. For example, a carrier indicator field (CIF) pointing to the PDSCH / PUSCH carrier can be included in the DCI. Different offsets on how the search space is located in the CORESET can also be used to indicate the PDSCH / PUSCH carrier. Based on the identified carrier, a time domain resource allocation table is selected.
[0066] In LTE and NR, different Radio Network Temporary Identifiers (RNTIs) may be used to schedule transmissions. As the name suggests, an RNTI is an identification number that identifies a specific radio channel and sometimes a specific UE. Some examples are:
[0067] -C-RNTI: used for cell-level scheduling. C-RNTI is a unique UE ID used as an identifier of the RRC connection and used for scheduling.
[0068] -RA-RNTI used in the random access procedure.
[0069] -SI-RNTI: an identifier of the system information in the downlink.
[0070] -P-RNTI: an identifier for paging and system information change notification in the downlink.
[0071] For example, it is conceivable to use different RNTIs to schedule slot-based transmissions and non-slot-based transmissions. Therefore, different RNTIs can be mapped to different time domain resource allocations, and the wireless device (depending on which RNTI it detects) selects a time domain resource allocation table. Therefore, the RNTI can be used as the first information for determining the time domain resource allocation table.
[0072] NR supports different parameter sets, such as OFDM subcarrier spacing and / or cyclic prefix. Different parameter sets (including cyclic prefix) can be used to optimize transmission with respect to latency or to use the parameter set alone for the current radio conditions of the terminal. Different parameter sets can be mapped to different time domain resource allocations, and the wireless device selects the correct time domain resource allocation table based on the transmitted parameter set. In NR, different bandwidth parts (BWPs) will be used for different parameter sets. Therefore, different BWPs may use different time domain resource allocation tables. For example, if the DCI contains a BWP indicator field, this can be used as the first information to determine the time domain resource allocation table.
[0073] Yet another possibility is to use the slot format as the first information for determining the time domain resource allocation table. For example, the wireless device may determine which table to use based on the slot format determined by the wireless device. The slot format may be determined based on the slot in which the PDSCH is received (or the PUSCH is sent). Alternatively, in the case of multi-slot transmission, the slot format may be determined based on the format applicable to the first slot from which the PDSCH is received (or the PUSCH is sent). The slot format may be determined by the wireless device via high-layer signaling and / or L1 signaling (e.g., a slot format indicator received in a DCI or group-common PDCCH), and indicates at least one or more downlink / uplink / unknown symbols within the slot.
[0074] In initial access, the remaining minimum system information (RMSI) can be sent according to slot-based transmission and non-slot-based transmission. The master information block (MIB) on the physical broadcast channel (PBCH) contains information about how to distribute the RMSI. Depending on how the RMSI is sent, different time domain resource allocation tables can be used to maximize the scheduling flexibility of the RMSI. Therefore, the information about how to send the RMSI can be used as the first information for determining the time domain resource allocation table.
[0075] Figure 2A flow chart of a method for selecting a time domain resource allocation table and a time domain resource allocation entry within a table in a wireless device is shown. First, the method includes selecting a time domain resource allocation table. In some embodiments, the method includes selecting one of a plurality of time domain resource allocation tables, for example based on information available to a network node and a wireless device, without the network node having to send a DCI that explicitly indicates which time domain resource allocation table the wireless device should select. Secondly, the method includes determining a time domain resource allocation entry within the selected table. For example, from the perspective of the network node, the network node determines a time domain resource allocation entry and explicitly signals the entry in a time domain resource allocation field of the DCI. From the perspective of the wireless device, the wireless device determines a time domain resource allocation entry within the selected table based on the time domain resource allocation field in the DCI received from the network node.
[0076] Furthermore, the table discussed above may be configured according to a set of possible time domain resource allocations. An example of a set of time domain resource allocations is given in Table 1 below.
[0077] Table 1 - Possible time domain resource allocation (taken from the specification)
[0078]
[0079]
[0080] In Table 1, the multi-slot schedule has been included directly in the table as a separate column. It is found under the "Applicable Slots (L2 Slots)" column. In other embodiments, the multi-slot schedule may be indicated in other ways. In some embodiments, the four entries of Table 1 may be configured to construct Figure 1 Table A (for example, in Figure 1 In the example shown, table A has four entries. The signaling for this may be in system information or in wireless device-specific signaling via radio resource control (RRC). A similar method may be performed for table B, etc.
[0081] Then, a table is selected based on the first information (e.g., RNTI), information contained in the DCI, which DCI format has been used for scheduling, which CORSET / search space has been used for scheduling, whether the transmission is slot-based or non-slot-based, information related to carrier aggregation, information related to bandwidth parts, slot formats, and / or information indicating parameter sets (e.g., cyclic prefix, OFDM subcarrier spacing, etc.). The time domain resource allocation field in the DCI will indicate the entry in the selected table. It is further observed that although Table 1 is described for PDSCH, a similar table can be constructed for PUSCH. As previously described, different tables (Table A, Table B, ...) can be configured for different CORESET / search spaces / ..., and each Table A, B, ... is configured with a row from Table 1.
[0082] Specific to initial access, some entries of Table 1 may be hard-coded directly in the specification for scheduling exemplary system information, paging, random access response and message 3 during random access. If there are no default values, additional signaling may be required in the MIB / PBCH to configure the default time domain resource allocation. These values may also be the default values used by the wireless device unless configured with a new time domain resource allocation table.
[0083] 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 a plurality of these functional units. These functional units may be implemented via processing circuits (which may include one or more microprocessors or microcontrollers) and other digital hardware (which 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 memory, 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 executing 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.
[0084] Figure 3A method according to a particular embodiment is depicted. In some embodiments, the method may be performed by a wireless device such as a UE. The method begins at step 30, where one of a plurality of time domain resource allocation tables is determined based on first information received from a network node. The method continues to step 32, where time domain resources allocated to the wireless device for sending or receiving wireless signals are determined based on the determined time domain resource allocation table from the plurality of time domain resource allocation tables and second information different from the first information received from the network node. Examples of the first information (i.e., information from which the wireless device can determine the time domain resource allocation table) and the second information (i.e., information from which the wireless device can determine the time domain resource) include, but are not limited to, the above description of Figure 1-2 and the examples described in the following Group A embodiments. In some embodiments, the method further comprises: at step 34, using the determined time domain resources to send or receive a wireless signal.
[0085] Figure 4 A method according to a particular embodiment is depicted. In some embodiments, the method may be performed by a network node such as a base station. The method begins at step 40, determining a time domain resource allocated to a wireless device for transmitting or receiving a wireless signal. For example, in some embodiments, the network node determines the time domain resource allocation based on an identified table and other information (e.g., current scheduling requirements). The network node may then select an entry from the table corresponding to the determined time domain resource allocation. In addition, the network node may determine second information for indicating the selected entry to the wireless device. The method proceeds to step 42, sending first information and second information to the wireless device, wherein the wireless device determines one of a plurality of time domain resource allocation tables based on the first information, and the wireless device determines the time domain resource based on the determined time domain resource allocation table from the plurality of time domain resource allocation tables and the second information. The second information is different from the first information. Examples of the first information (i.e., information from which the wireless device can determine the time domain resource allocation table when sent to the wireless device) and the second information (i.e., information from which the wireless device can determine the time domain resource when sent to the wireless device) include, but are not limited to, the above description of Figure 1-2 and the examples described in the following Group B embodiments. In some embodiments, the method further comprises: at step 44, using the allocated time domain resources to send or receive wireless signals.
[0086] about Figure 3 and Figure 4 In the example, in some embodiments, the first information includes one or more of the following:
[0087] a. Information contained in downlink control information (DCI) from the network and signaled to the wireless device for purposes other than determining time domain resources;
[0088] b. Information indicating which DCI format has been used for scheduling (eg, a normal DCI format or a fallback DCI format);
[0089] c. Information indicating which CORSET / search space has been used for scheduling;
[0090] d. Information indicating whether the transmission is slot-based or non-slot-based;
[0091] e. Information related to carrier aggregation;
[0092] f. Information related to the bandwidth part;
[0093] g. Information indicating the time slot format;
[0094] h. Information indicating whether the transmission is a single slot or multiple slots;
[0095] i. Configuration of the downlink / uplink indicator received in the DCI;
[0096] j. Radio Network Temporary Identifier (RNTI); and / or
[0097] k. Information indicating a parameter set (eg, OFDM subcarrier spacing and / or cyclic prefix).
[0098] The second information includes a time domain resource allocation field within the downlink control information that allows the wireless device / UE to determine which entry within a determined table of the plurality of tables to use in order to determine the allocated time domain resources.
[0099] Figure 5 A wireless network (e.g., Figure 6 The schematic block diagram of an apparatus 50 in a wireless network (shown in FIG. 1 ) is shown. The apparatus may be in a wireless device or a network node (e.g., Figure 6 The apparatus 50 is implemented in the wireless device 110 or the network node 160 shown in FIG. Figure 3 or Figure 4 The exemplary methods described herein and any other processes or methods that may be disclosed herein. It should also be understood that Figure 3 and Figure 4 The method is not necessarily performed only by the apparatus 50. At least some operations of the method may be performed by one or more other entities.
[0100] The virtual device 50 may include processing circuits (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuits 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, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some embodiments, the processing circuits may be used to enable the configuration information unit 52, the time resource determination unit 54, the communication unit 56, and any other suitable units of the device 50 to perform corresponding functions according to one or more embodiments of the present disclosure.
[0101] like Figure 5 As shown, the apparatus 50 includes a configuration information unit 52, a time resource determination unit 54, and a communication unit 56. In some embodiments, the configuration information unit 52 is configured to determine the first information and the second information. For example, when used in a network node, the configuration information unit 52 determines the first information and the second information to be sent to the wireless device, wherein the wireless device determines one of a plurality of tables according to the first information, and the wireless device (based on one of the plurality of tables determined according to the first information) determines the allocated time domain resources according to the second information. When used in the wireless device, the configuration information unit 52 determines the first and second information received from the network node. The time resource determination unit 54 determines the time resources allocated to the wireless device for sending or receiving wireless signals. When used in the network node, the time resource determination unit 54 can allocate time domain resources, and can indicate the allocated time domain resources to the configuration information unit 52 of the network node, so that the configuration information unit 52 can determine the first information and the second information to be sent to the wireless device (e.g., the first and second information corresponding to the allocated time domain resources). When used in a wireless device, the time resource determination unit 54 may receive the first and second information from the network node (e.g., via the configuration information unit 52 of the wireless device), and may use the first and second information to determine the time domain resources that the network node has allocated for sending or receiving wireless signals. The communication unit 56 sends or receives wireless signals according to the allocated time domain resources determined by the time resource determination unit 54.
[0102] The term "unit" may have its 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 various tasks, processes, calculations, output and / or display functions, etc., such as those described herein.
[0103] In some embodiments, a computer program, a computer program product, or a computer-readable storage medium includes instructions that, when executed on a computer, perform any of the embodiments disclosed herein. In a further example, the instructions are carried on a signal or carrier and can be executed on a computer, where, when executed, any of the embodiments disclosed herein are performed.
[0104] Example
[0105] Group A Embodiment
[0106] 1. A method performed by a wireless device, the method comprising:
[0107] - determining a table of a plurality of tables based on first information received from a network node (eg a base station),
[0108] - Determining time domain resources allocated to the wireless device for sending or receiving wireless signals based on a table determined from the plurality of tables and second information received from the network node, the second information being different from or not the first information.
[0109] 2. The method according to the aforementioned embodiment, wherein the multiple tables are time domain resource allocation tables.
[0110] 3. The method according to any one of the preceding embodiments further includes using the determined time domain resources to send or receive a wireless signal.
[0111] 4. The method according to any one of the preceding embodiments, wherein the second information is a time domain resource allocation field received in downlink control information.
[0112] 5. The method according to any one of the preceding embodiments, wherein the first information includes one or more of the following:
[0113] a. Information contained in downlink control information (DCI) from the network and signaled to the wireless device for another purpose besides determining time domain resources;
[0114] b. Information indicating which DCI format has been used for scheduling (eg, a normal DCI format or a fallback DCI format);
[0115] c. Information indicating which CORSET / search space has been used for scheduling;
[0116] d. Information indicating whether the transmission is slot-based or non-slot-based;
[0117] e. Information related to carrier aggregation;
[0118] f. Information related to the bandwidth part;
[0119] g. Information indicating the time slot format;
[0120] h. Information indicating whether the transmission is a single slot or multiple slots;
[0121] i. Configuration of the downlink / uplink indicator received in the DCI;
[0122] j. Radio Network Temporary Identifier (RNTI); and / or
[0123] k. Information indicating a parameter set (eg, OFDM subcarrier spacing and / or cyclic prefix).
[0124] 6. A method performed by a wireless device, the method comprising:
[0125] - using a selected table from a plurality of tables to determine time domain resources that the network has allocated to the wireless device for transmitting or receiving wireless signals.
[0126] 7. The method according to the preceding embodiment further comprises: determining the selected table based on information other than the time domain resource allocation field received in the downlink control information from the network.
[0127] 8. The method of any of the preceding embodiments, further comprising: selecting the selected table at the wireless device based on information available to both the network and the wireless device.
[0128] 9. The method of example embodiment 6, wherein the information used to select the selected table includes one or more of the following:
[0129] - Information contained in downlink control information (DCI) from the network and signaled to the wireless device for another purpose besides identifying the selected time domain resource allocation;
[0130] - Which DCI format has been used for scheduling (e.g., normal DCI format or fallback DCI format);
[0131] - Which CORSET / search space has been used for scheduling;
[0132] - Whether the transmission is slot-based or non-slot-based;
[0133] -Information related to carrier aggregation;
[0134] - Information related to bandwidth components;
[0135] -Time slot format;
[0136] - Whether the transmission is single-slot or multi-slot;
[0137] - Configuration of downlink / uplink indicators received in DCI;
[0138] - Radio Network Temporary Identifier (RNTI); and / or
[0139] - Parameter set (e.g. OFDM subcarrier spacing and / or cyclic prefix).
[0140] 10. The method of any of the preceding embodiments, wherein when time domain resource allocation is used to schedule system information, the selected table is based on whether the system information is distributed according to a slot-based transmission or a non-slot-based transmission.
[0141] 11. The method according to any one of the preceding embodiments further comprises: determining a selected entry among a plurality of entries in the selected table, the selected entry indicating a time domain resource that the network has allocated to the wireless device for sending or receiving wireless signals.
[0142] 12. The method of the preceding embodiment, wherein the selected entry is determined based on an explicit indication received from a network.
[0143] 13. The method according to the preceding embodiment, wherein the explicit indication is received via a time domain resource allocation bit field received in downlink control information from the network.
[0144] 14. The method of any one of the preceding embodiments, wherein the selected entry indicates at least two of a start symbol, a stop symbol, and a symbol duration for transmitting or receiving a wireless signal.
[0145] 15. The method according to any one of the preceding embodiments further comprises: sending a wireless signal on a physical uplink shared channel (PUSCH) using the allocated time domain resources.
[0146] 16. The method according to any one of the preceding embodiments further comprises: receiving a wireless signal on a physical downlink shared channel (PDSCH) using the allocated time domain resources.
[0147] 17. The method of any preceding embodiment, wherein:
[0148] - a first table of the plurality of tables indicates the starting or ending OFDM symbol as an absolute OFDM symbol number relative to a slot boundary, and
[0149] - A second table among the plurality of tables indicates a start or end OFDM symbol with respect to a PDCCH / CORESET symbol for scheduling a PDSCH / PUSCH.
[0150] 18. The method of any of the preceding embodiments, wherein a first table of the plurality of tables includes a different number of entries than a second table of the plurality of tables.
[0151] 19. The method of any of the preceding embodiments, wherein each of the plurality of tables comprises the same number of entries.
[0152] 20. The method according to any one of the preceding embodiments, further comprising:
[0153] - provide user data; and
[0154] - Forwarding user data to a host computer via transmission to a network node.
[0155] Group B Example
[0156] 21. A method performed by a base station, the method comprising:
[0157] -determining a time domain resource to be allocated to the wireless device for transmitting or receiving a wireless signal, and
[0158] - sending first information and second information to the wireless device, wherein the wireless device determines one of the plurality of tables based on the first information. The wireless device determines the allocated time domain resources based on one of the plurality of tables and the second information, the second information being different from or not the first information.
[0159] 22. The method according to the preceding embodiment, wherein the plurality of tables are time domain resource allocation tables.
[0160] 23. The method according to any one of the preceding embodiments further comprises using the determined time domain resources to send or receive wireless signals.
[0161] 24. The method according to any one of the preceding embodiments, wherein the second information is a time domain resource allocation field sent in downlink control information.
[0162] 25. The method according to any one of the preceding embodiments, wherein the first information includes one or more of the following:
[0163] a. Information contained in downlink control information (DCI) signaled from a base station to a wireless device for another purpose other than determining time domain resources;
[0164] b. Information indicating which DCI format has been used for scheduling (eg, a normal DCI format or a fallback DCI format);
[0165] c. Information indicating which CORSET / search space has been used for scheduling;
[0166] d. Information indicating whether the transmission is slot-based or non-slot-based;
[0167] e. Information related to carrier aggregation;
[0168] f. Information related to the bandwidth part;
[0169] g. Information indicating the time slot format;
[0170] h. Information indicating whether the transmission is a single slot or multiple slots;
[0171] i. Configuration of the downlink / uplink indicator received in the DCI;
[0172] j. Radio Network Temporary Identifier (RNTI); and / or
[0173] k. Information indicating a parameter set (eg, OFDM subcarrier spacing and / or cyclic prefix).
[0174] 26. A method performed by a network node (e.g., a base station), the method comprising:
[0175] - determining one of the plurality of tables that the wireless device is using to determine the time domain resources that the network node is allocating to the wireless device for transmitting or receiving wireless signals;
[0176] - sending information indicating one of a plurality of entries in the determined table of the plurality of tables to the wireless device, the selected entry indicating a time domain resource that has been allocated to the wireless device for transmitting or receiving wireless signals.
[0177] 27. The method of any preceding embodiment, wherein a table of the plurality of tables is determined based on information available to both the network node and the wireless device.
[0178] 28. The method of example embodiment 26, wherein the information used to determine which table (i.e., one of the plurality of tables) the wireless device is using comprises:
[0179] - information contained in downlink control information (DCI) signaled by the network to the wireless device for another purpose than identifying the selected time domain resource allocation;
[0180] - Which DCI format has been used for scheduling (e.g., normal DCI format or fallback DCI format);
[0181] - Which CORSET / search space has been used for scheduling;
[0182] - Whether the transmission is slot-based or non-slot-based;
[0183] -Information related to carrier aggregation;
[0184] - Information related to bandwidth components;
[0185] -Time slot format;
[0186] - Whether the transmission is single slot or multi-slot;
[0187] - Configuration of downlink / uplink indicators received in DCI;
[0188] - Radio Network Temporary Identifier (RNTI); and / or
[0189] - Parameter set (e.g. OFDM subcarrier spacing and / or cyclic prefix).
[0190] 29. A method according to any one of the preceding embodiments, wherein, when time domain resource allocation is used to schedule system information, one of the multiple tables is determined based on whether the system information is distributed according to a time slot based transmission or a non-time slot based transmission.
[0191] 30. The method of the preceding embodiment, wherein information indicating one of the plurality of entries is explicitly sent.
[0192] 31. The method of the preceding embodiment, wherein the information indicating one of the plurality of entries is transmitted via a time domain resource allocation bit field in downlink control information transmitted to the wireless device.
[0193] 32. The method of any of the preceding embodiments, wherein an entry in the plurality of entries indicates at least two of a start symbol, a stop symbol, and a symbol duration for transmitting or receiving a wireless signal.
[0194] 33. The method according to any of the preceding embodiments further comprises receiving a wireless signal on a physical uplink shared channel (PUSCH) using the allocated time domain resources.
[0195] 34. The method according to any one of the preceding embodiments further comprises sending a wireless signal on a physical downlink shared channel (PDSCH) using the allocated time domain resources.
[0196] 35. The method of any one of the preceding embodiments, wherein:
[0197] - a first table of the plurality of tables indicates the starting or ending OFDM symbol as an absolute OFDM symbol number relative to a slot boundary, and
[0198] - A second table among the plurality of tables indicates a start or end OFDM symbol relative to a PDCCH / CORESET symbol for scheduling a PDSCH / PUSCH.
[0199] 36. The method of any of the preceding embodiments, wherein a first table of the plurality of tables comprises a different number of entries than a second table of the plurality of tables.
[0200] 37. A method according to any of the preceding embodiments, wherein each table in the plurality of tables includes the same number of entries.
[0201] 38. The method according to any one of the preceding embodiments, further comprising:
[0202] - Access user data; and
[0203] -Forward user data to a host computer or wireless device.
[0204] 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 6 For simplicity, Figure 6 The wireless network of FIG. 1 depicts only network 106, network nodes 160 and 160b, and WD 110, 110b, and 110c. 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 (e.g., a landline, a service provider, or any other network node or terminal device). In the components shown, network node 160 and wireless device (WD) 110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by the wireless network or services provided via the wireless network.
[0205] 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), 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.
[0206] The network 106 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 communications between devices.
[0207] The network node 160 and the WD 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, 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 the communication of data and / or signals via wired or wireless connections.
[0208] 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 with 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 node Bs (gNBs)). Base stations can be classified based on the amount of coverage provided by the base stations (or in other words, their transmit power levels), and then they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can 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 also 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). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs. 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 a wireless device to access a wireless network and / or to provide a wireless device with access to a wireless network or to provide a wireless device that has accessed a wireless network with some service.
[0209] exist Figure 6 In the embodiment, the network node 160 includes a processing circuit 170, a device readable medium 180, an interface 190, an auxiliary device 184, a power supply 186, a power supply circuit 187, and an antenna 162. Figure 6The network node 160 shown in the example wireless network of can represent a device including a combination of hardware components illustrated, but other embodiments can include network nodes with different combinations of components. It should 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. In addition, although the components of the network node 160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up the single illustrated component (for example, the device readable medium 180 may include multiple separate hard drives and multiple RAM modules).
[0210] Similarly, the network node 160 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 some cases where the network node 160 includes multiple separated components (e.g., BTS and BSC components), one or more separated components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In this case, each unique NodeB and RNC pair may be considered as a single separated network node in some cases. In some embodiments, the network node 160 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be duplicated (e.g., separate device readable media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by RATs). The network node 160 may also include multiple groups of various example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into the network node 160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 160 .
[0211] The processing circuit 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by the network node. These operations performed by the processing circuit 170 may include, for example, processing information acquired by the processing circuit 170 by converting the acquired information into other information, comparing the acquired information or the converted information with information stored in the network node, and / or performing one or more operations based on the acquired information or the converted information; and making determinations as a result of the processing.
[0212] The processing circuit 170 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 one or more of hardware, software, and / or encoded logic operable to provide network node 160 functionality, either alone or in conjunction with other network node 160 components (e.g., device readable medium 180). For example, the processing circuit 170 may execute instructions stored in the device readable medium 180 or in a memory within the processing circuit 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 170 may include a system on a chip (SOC).
[0213] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.
[0214] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 170 executing instructions stored on a device-readable medium 180 or a memory within the processing circuit 170. In alternative embodiments, some or all of the functions may be provided by the processing circuit 170 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of those embodiments, the processing circuit 170 may be configured to perform the described functions regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuit 170 alone or other components of the network node 160, but are enjoyed by the network node 160 as a whole and / or generally by end users and wireless networks.
[0215] Device readable medium 180 may include any form of volatile or non-volatile computer readable memory, including but not limited to permanent memory, 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 any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuit 170. Device readable medium 180 may store any suitable instructions, data, or information (including one or more of 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 170 and utilized by network node 160. Device readable medium 180 may be used to store any computations performed by processing circuit 170 and / or any data received via interface 190. In some embodiments, processing circuit 170 and device readable medium 180 may be considered integrated.
[0216] Interface 190 is used in wired or wireless communication of signaling and / or data between network node 160, network 106 and / or WD 110. As shown, interface 190 includes port / terminal 194 to send data to network 106 and receive data from network 106, for example, through wired connection. Interface 190 also includes radio front-end circuit 192 that can be coupled to antenna 162 or as a part of antenna 162 in some embodiments. Radio front-end circuit 192 includes filter 198 and amplifier 196. Radio front-end circuit 192 can be connected to antenna 162 and processing circuit 170. Radio front-end circuit 192 can be configured to adjust the signal communicated between antenna 162 and processing circuit 170. Radio front-end circuit 192 can receive digital data that will be sent to other network nodes or WD through wireless connection. Radio front-end circuit 192 can use the combination of filter 198 and / or amplifier 196 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted through antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals, which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.
[0217] In some alternative embodiments, the network node 160 may not include a separate radio front end circuit 192, and instead, the processing circuit 170 may include the radio front end circuit and may be connected to the antenna 162 without the separate radio front end circuit 192. Similarly, in some embodiments, all or some of the RF transceiver circuit 172 may be considered part of the interface 190. In other embodiments, the interface 190 may include one or more ports or terminals 194, the radio front end circuit 192, and the RF transceiver circuit 172 as part of a wireless unit (not shown), and the interface 190 may communicate with the baseband processing circuit 174 as part of a digital unit (not shown).
[0218] Antenna 162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuit 192 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separated from network node 160 and may be connected to network node 160 via an interface or port.
[0219] Antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any receiving operation and / or certain acquisition 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 device. Similarly, antenna 162, interface 190 and / or processing circuit 170 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.
[0220] The power circuit 187 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 160 to perform the functions described herein. The power circuit 187 may receive power from the power supply 186. The power supply 186 and / or the power circuit 187 may be configured to provide power to the various components of the network node 160 in a form suitable for the various components (e.g., at the voltage and current level required by each corresponding component). The power supply 186 may be included in the power circuit 187 and / or the network node 160 or extended to the power circuit 187 and / or the network node 160. For example, the network node 160 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (such as a cable), whereby the external power source provides power to the power circuit 187. As another example, the power supply 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated in the power circuit 187. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.
[0221] Alternative embodiments of network node 160 may include Figure 6 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of a network node, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 160 may include a user interface device to allow information to be input into network node 160 and to allow information to be output from network node 160. This may allow a user to perform diagnostics, maintenance, repair, and other management functions of network node 160.
[0222] As used herein, a wireless device (WD) refers to a device that can, is configured to, is arranged to and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. 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 send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event or in response to a request from a network, a WD may be designed to send information to the network on a predetermined schedule. 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, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop built-in devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WDs can support device-to-device (D2D) communications (e.g., by implementing 3GPP standards for secondary link 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 measurements and sends the results of such monitoring and / or measurements to another WD and / or a network node. In this case, a WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As an example, a 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 cases, a 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. A 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, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
[0223] As shown, wireless device 110 includes antenna 111, interface 114, processing circuit 120, device readable medium 130, user interface device 132, auxiliary device 134, power supply 136 and power supply circuit 137. WD 110 may include multiple groups of components for one or more of the different wireless technologies supported by WD 110 (such as GSM, WCDMA, LTE, NR, Wi-Fi, WiMAX or Bluetooth wireless technology, to name a few). These wireless technologies can be integrated into the same or different chips or chipsets as other components in WD 110.
[0224] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 114. In some alternative embodiments, antenna 111 may be separated from WD 110 and may be connected to WD 110 via an interface or port. Antenna 111, interface 114 and / or processing circuit 120 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 111 may be considered as an interface.
[0225] As shown, the interface 114 includes a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 includes one or more filters 118 and an amplifier 116. The radio front-end circuit 112 is connected to the antenna 111 and the processing circuit 120, and is configured to adjust the signal transmitted between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to the antenna 111 or as part of the antenna 111. In some embodiments, the WD 110 may not include a separate radio front-end circuit 112; instead, the processing circuit 120 may include a radio front-end circuit and may be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered as part of the interface 114. The radio front-end circuit 112 may receive digital data sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be sent via the antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals, which are then converted into digital data by radio front end circuit 112. The digital data may be passed to processing circuit 120. In other embodiments, the interface may include different components and / or different combinations of components.
[0226] The processing circuit 120 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 hardware, software, and / or a combination of one or more of a combination of coded logic operable to provide WD 110 functionality alone or in combination with other WD 110 components (such as device readable medium 130,). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 120 may execute instructions stored in the device readable medium 130 or in a memory within the processing circuit 120 to provide functionality disclosed herein.
[0227] As shown, the processing circuit 120 includes one or more of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of the WD 110 may include a SOC. In some embodiments, the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 124 and the application processing circuit 126 may be combined into one chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In yet another alternative embodiment, part or all of the RF transceiver circuit 122 and the baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 122 may be part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.
[0228] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by the processing circuit 120 executing instructions stored on a device-readable medium 130, which may be a computer-readable storage device medium in some embodiments. In alternative embodiments, some or all of the functions may be provided by the processing circuit 120 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 120 may be configured to perform the described functions regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits 120 or other components of the WD 110, but may also be enjoyed by the WD 110 as a whole and / or generally by end users and wireless networks.
[0229] Processing circuit 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by processing circuit 120 may include, for example, processing information acquired by processing circuit 120 by converting the acquired information into other information, comparing the acquired information or the converted information with information stored by WD 110, and / or performing one or more operations based on the acquired information or the converted information; and making determinations as a result of the processing.
[0230] Device readable medium 130 may be 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 120. Device readable medium 130 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 storage device that stores information, data, and / or instructions that may be used by processing circuit 120. In some embodiments, processing circuit 120 and device readable medium 130 may be considered integrated.
[0231] The user interface device 132 can provide a component that allows a human user to interact with the WD 110. This interaction can have multiple forms such as visual, auditory, tactile, etc. The user interface device 132 is operable to generate output to the user and allow the user to provide input to the WD 110. The type of interaction may vary depending on the type of user interface device 132 installed in the WD 110. For example, if the WD 110 is a smart phone, the interaction can be via a touch screen; if the WD 110 is a smart meter, the interaction can be performed 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 132 may include input interfaces, devices and circuits and output interfaces, devices and circuits. The user interface device 132 is configured to allow information to be input to the WD 110, and is connected to the processing circuit 120 to allow the processing circuit 120 to process the input information. The user interface device 132 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 circuit. The user interface device 132 is also configured to allow information to be output from the WD 110 and to allow the processing circuit 120 to output information from the WD 110. The user interface device 132 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 132, the WD 110 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.
[0232] Auxiliary device 134 is operable to provide more specific functionality that a WD may not normally perform. This may include specialized sensors for taking measurements for various purposes, interfaces for additional communication types such as wired communications, etc. The inclusion and types of components of auxiliary device 134 may vary depending on the embodiment and / or scenario.
[0233] In some embodiments, the power source 136 may be in the form of a battery or battery pack. Other types of power sources such as an external power source (e.g., a power outlet), a photovoltaic device, or a power battery may also be used. The WD 110 may also include a power circuit 137 for transmitting power from the power source 136 to various components of the WD 110 that require power from the power source 136 to perform any functions described or indicated herein. In some embodiments, the power circuit 137 may include a power management circuit. The power circuit 137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 110 may be connected to an external power source (such as a power outlet) via an input circuit or interface (e.g., a power cable). In some embodiments, the power circuit 137 may also be operable to transfer power from an external power source to the power source 136. This may be used, for example, to charge the power source 136. The power circuit 137 may perform any formatting, conversion, or other modification of the power from the power source 136 to make the power suitable for the corresponding components of the WD 110 to which it is powered.
[0234] Figure 7 One embodiment of a UE according to various aspects described herein is shown. 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. Instead, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a specific 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 may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 200 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 7 As shown, UE 200 is an example of a WD configured to communicate according to 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. Therefore, although Figure 7 It is UE, but the components discussed in this article are also applicable to WD and vice versa.
[0235] exist Figure 7In the embodiment, UE 200 includes a processing circuit 201 operably coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connection interface 211, a memory 215 including a random access memory (RAM) 217, a read-only memory (ROM) 219, and a storage medium 221, a communication subsystem 231, a power supply 213, and / or any other components or any combination thereof. The storage medium 221 includes an operating system 223, an application 225, and data 227. In other embodiments, the storage medium 221 may include other similar types of information. Some UEs may utilize Figure 7 All components shown, or only a subset of these components. The level of integration between components may vary from one UE to another UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0236] exist Figure 7 In the embodiment of the present invention, the processing circuit 201 can be configured to process computer instructions and data. The processing circuit 201 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in the form of discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 201 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.
[0237] In the depicted embodiment, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 200 or to provide output from the UE 200. 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 200 may be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device may include a touch-sensitive display or a 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 steering wheel, 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 the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
[0238] exist Figure 7 In the embodiment of the present invention, the RF interface 209 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface 211 can be configured to provide a communication interface to the network 243a. The network 243a can cover 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 243a can include a Wi-Fi network. The network connection interface 211 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 (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 211 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately.
[0239] RAM 217 can be configured to interface with processing circuit 201 via bus 202 to provide storage or buffering of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuit 201. For example, ROM 219 can be configured to store unchanged low-level system code or data for basic system functions (such as basic input and output (I / O), startup, or receiving keystrokes from a keyboard) stored in non-volatile memory. Storage medium 221 can be configured to include a memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), a disk, an optical disk, a floppy disk, a hard disk, a removable cassette, or a flash drive. In one example, storage medium 221 can be configured to include an operating system 223, an application 225 such as a web browser application, a widget or a gadget engine, or another application, and a data file 227. The storage medium 221 may store any one of various operating systems or a combination of operating systems for use by the UE 200 .
[0240] The storage medium 221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy 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), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory (e.g., a subscriber identity module (SIM) or a removable user identity (RUIM) module), other memory, or any combination thereof. The storage medium 221 may allow the UE 200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 221, which may include a device-readable medium.
[0241] exist Figure 7In the embodiment of the present invention, the processing circuit 201 may be configured to communicate with the network 243b using the communication subsystem 231. The network 243a and the network 243b may be the same one or more networks or different one or more networks. The communication subsystem 231 may be configured to include one or more transceivers for communicating with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE, or a base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 233 and / or a receiver 235 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 233 and the receiver 235 of each transceiver may share circuit components, software, or firmware, or may alternatively be implemented separately.
[0242] In the illustrated embodiment, the communication functions of the communication subsystem 231 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 location), another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may cover 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 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.
[0243] The features, benefits and / or functions described herein may be implemented in one of the components of UE 200, or may be divided between multiple components of UE 200. 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 231 may be configured to include any component described herein. In addition, the processing circuit 201 may be configured to communicate with any such component via bus 202. In another example, any such component may be represented by a program instruction stored in a memory, which performs the corresponding function described herein when executed by the processing circuit 201. In another example, the function of any such component may be divided between the processing circuit 201 and the communication subsystem 231. 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.
[0244] Appendix A
[0245] In the following, further example embodiments related to the NR resource allocation design problem, and more specifically time domain resource allocation, are discussed.
[0246] Time allocation
[0247] In the 3GPP RAN1#90bis meeting, the following agreement was reached:
[0248] agreement:
[0249] For both slots and mini-slots, the scheduling DCI may provide an index into a UE-specific table giving the OFDM symbol used for PDSCH (or PUSCH) transmission
[0250] oAssigned starting OFDM symbol and OFDM symbol length
[0251] oFor Further Study (FFS): one or more tables
[0252] o FFS: includes slots for multi-slot / multi-mini-slot scheduling or slot indexes for cross-slot scheduling
[0253] o FFS: If SFI supports non-contiguous allocations, you may need to revisit
[0254] At least for RMSI scheduling
[0255] oAt least one table entry needs to be fixed in the specification
[0256] Regarding whether one or more tables should be specified, it is believed that multiple tables can provide greater flexibility in scheduling. However, in order to limit the DCI message size for selecting a table, the number of tables can be limited to two. The table entries in the two tables can be different in starting OFDM symbols and / or duration. The selection of the table can be based on other fields in the DCI message, such as using type A scheduling or using type B scheduling, or signaling scheduling based on slot-based transmission or based on mini-slot-based transmission fields.
[0257] Proposal 3-1: To provide greater flexibility in time domain resource allocation, two tables with different starting OFDM symbols and OFDM symbol durations are specified.
[0258] For NR, data transmission may occupy (almost) all OFDM symbols in a slot, or in case of mini-slot transmission, only some OFDM symbols. These possibilities can be handled in a unified way by including information about the PUSCH and PDSCH start and end positions in the DCI. In order to limit the DCI overhead while providing some flexibility, one possibility is to have, for example, 3 bits in the DCI pointing to different combinations of start and end positions.
[0259] The combination should also be aligned with the OFDM symbol positions given by the SFI (Slot Format Indicator) in the group-common PDCCH (e.g., the combination shown in [1]). For DL, the reference to the start and end positions should be relative to the first OFDM symbol of the PDCCH carrying the corresponding DCI. Some starting positions can be -ve values to accommodate the case where the PDSCH starts before the symbol in which the PDCCH coreset is configured. In order to limit UE buffering requirements, only limited -ve values should be allowed (e.g., only -2, -1).
[0260] In case of slot aggregation / repetition, data may also span multiple slots. To handle slot aggregation, the UE uses the same time resource allocation in the slots where the transmission is repeated.
[0261] Proposal 3-2: When slot aggregation / repetition is applied, the UE adopts the same time resource allocation in the slots where transmission is repeated.
[0262] In order to have higher efficiency in the DCI message, it is possible to make a bit field in the DCI message depend on which CORESET the DCI is sent according to. This is to allow more appropriate options for the configuration of the start and stop OFDM symbols for PDSCH and PUSCH.
[0263] Proposal 3-3: The bit fields in the DCI message indicating the start and end OFDM symbols within a timeslot are configured separately per CORESET.
[0264] Furthermore, in some cases, for both UL and DL, it may be necessary to define in which time slot the transmission of PUSCH or PDSCH should occur. Such information may be a separate bit field or jointly encoded with the start and end positions. However, it should be noted here that in order to be able to support fairly long UL time slot cycles, approximately 4 bits may be required to support these cases. Similar requirements do not strictly exist for DL, since in DL, DCI messages may be provided in each DL time slot, so for DL, the information may be jointly encoded with the position information within the time slot, or a single bit may be introduced to indicate scheduling in the next preceding time slot.
[0265] Proposal 3-4
[0266] For PUSCH transmission, a bit field of up to 4 bits is introduced in the DCI message to indicate in which UL time slot the PUSCH is transmitted
[0267] • For PDSCH, the indication in which DL slot the PDSCH is transmitted is jointly encoded with the position information within the slot, or a single bit may be introduced to indicate scheduling in the next preceding slot.
[0268] Appendix B
[0269] Now refer to Figure 8-14 Some additional embodiments contemplated herein are described more fully. Figure 8 300 is a schematic block diagram illustrating a virtualized environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may 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 a portion of a function 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).
[0270] 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 300 hosted by one or more hardware nodes 330. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), then the network nodes may be fully virtualized.
[0271] These functions may be implemented by one or more applications 320 (alternatively referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement certain features, functions, and / or benefits of some embodiments disclosed herein. The applications 320 run in a virtualized environment 300 that provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360, whereby the applications 320 are operable to provide one or more features, benefits, and / or functions disclosed herein.
[0272] The virtualized environment 300 includes a general or special purpose network hardware device 330 (which includes a set of one or more processors or processing circuits 360), which may be commercial off-the-shelf (COTS) processors, dedicated 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 390-1 that may be a non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuit 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also known as network interface cards) that include a physical network interface 380. Each hardware device may also include a non-transitory persistent machine-readable storage medium 390-2 in which software 395 and / or instructions executable by the processing circuit 360 are stored. The software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also known as hypervisors), software for executing virtual machines 340, and software that allows it to perform the functions, features, and / or benefits described in connection with some embodiments described herein.
[0273] The virtual machines 340 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of the virtual device 320 may be implemented on one or more virtual machines 340 and may be implemented in different ways.
[0274] During operation, processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present to virtual machines 340 a virtual operating platform that appears to be networked hardware.
[0275] like Figure 8 As shown, hardware 330 can be an independent network node with general or specialized components. Hardware 330 can include antenna 3225 and can implement some functions via virtualization. Alternatively, hardware 330 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)) in which many hardware nodes work together and are managed via management and orchestration (MANO) 3100 that oversees the lifecycle management of application 320, in particular.
[0276] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to consolidate many network device types into industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and client devices.
[0277] In the context of NFV, a virtual machine 340 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtualized machine. Each virtual machine 340 and the portion of the hardware 330 on which it executes (whether dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 340) form a separate virtual network element (VNE).
[0278] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions in one or more virtual machines 340 running on top of the hardware network infrastructure 330 and interacting with the Figure 8 Corresponding to application 320 in.
[0279] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware nodes 330 via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.
[0280] In some embodiments, some signaling may be accomplished using a control system 3230 that may alternatively be used for communications between the hardware node 330 and the radio unit 3200 .
[0281] refer to Fig. 9According to an embodiment, a communication system includes a telecommunication network 410 such as a 3GPP type cellular network, which includes an access network 411 such as a radio access network and a core network 414. The access network 411 includes a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c may be connected to the core network 414 via a wired or wireless connection 415. A first UE 491 located in a coverage area 413C is configured to be wirelessly connected to or paged by a corresponding base station 412C. A second UE 492 in a coverage area 413a may be wirelessly connected to a corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments are equally applicable to situations where a sole UE is in a coverage area or a sole UE is connected to a corresponding base station 412.
[0282] The telecommunications network 410 itself is connected to a host computer 430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 430 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 421 and 422 between the telecommunications network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430 or may be made via an optional intermediate network 420. The intermediate network 420 may be a combination of one or more of a public, private, or managed network; the intermediate network 420 (if any) may be a backbone network or the Internet; in particular, the intermediate network 420 may include two or more sub-networks (not shown).
[0283] Fig. 9The communication system as a whole implements a connection between the connected UE 491, 492 and the host computer 430. The connection can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UE 491, 492 are configured to use the access network 411, the core network 414, any intermediate network 420, and possible other infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 450. The OTT connection 450 can be transparent in the sense that the participating communication devices through which the OTT connection 450 passes do not know the routes of uplink and downlink communications. For example, the base station 412 may not or need not be informed of the past routes of incoming downlink communications with data originating from the host computer 430 to be forwarded (e.g., switched) to the connected UE 491. Similarly, the base station 412 does not need to know the future routes of outgoing uplink communications originating from the UE 491 toward the host computer 430.
[0284] According to the embodiment, reference will now be made to Fig.10 Describe the example implementation of the UE, base station and host computer discussed in the preceding paragraph. In the communication system 500, the host computer 510 includes hardware 515 including a communication interface 516 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 500. The host computer 510 also includes a processing circuit 518 that may have storage and / or processing capabilities. In particular, the processing circuit 518 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 510 also includes software 511 stored in the host computer 510 or accessible by the host computer 510 and executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 is operable to provide services to remote users of UE 530 such as those connected via an OTT connection 550 that terminates at the UE 530 and the host computer 510. When providing services to remote users, the host application 512 can provide user data sent using the OTT connection 550.
[0285] The communication system 500 also includes a base station 520 provided in the telecommunication system and including hardware 525 enabling it to communicate with the host computer 510 and with the UE 530. The hardware 525 may include a communication interface 526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 500, and for establishing and maintaining connections with other devices located in the coverage area ( Fig.10The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct or may be through a core network (eg, a wireless network) of the telecommunications system. Fig.10 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 525 of the base station 520 also includes processing circuitry 528 that may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 520 also has software 521 stored internally or accessible via an external connection.
[0286] The communication system 500 also includes the UE 530 already mentioned. Its hardware 535 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area where the UE 530 is currently located. The hardware 535 of the UE 530 also includes a processing circuit 538 that 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 530 further includes software 531 stored in the UE 530 or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532 is operable to provide services to human or non-human users via the UE 530 with the support of the host computer 510. In the host computer 510, the executing host application 512 can communicate with the executing client application 532 via an OTT connection 550 terminated at the UE 530 and the host computer 510. When providing services to users, the client application 532 can receive request data from the host application 1012 and provide user data in response to the request data. The OTT connection 550 can transmit both the request data and the user data. The client application 532 can interact with the user to generate the user data it provides.
[0287] Notice, Fig.10 The host computer 510, base station 520 and UE 530 shown can be respectively Fig. 9 The host computer 430, one of the base stations 412a, 412b, 412c and one of the UEs 491, 492 may be similar or identical. That is, the internal operation of these entities may be similar to Fig.10 As shown, the independent surrounding network topology can be Fig. 9 Like that.
[0288] exist Fig.10, an OTT connection 550 has been abstractly drawn to illustrate communications between a host computer 510 and a UE 530 via a base station 520, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure may determine a route that may be configured to hide the route from the UE 530 or from a service provider operating the host computer 510, or both. While the OTT connection 550 is active, the network infrastructure may further make decisions to dynamically change the route therethrough (e.g., based on load balancing considerations or reconfiguration of the network).
[0289] The wireless connection 570 between the UE 530 and the base station 520 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 that forms the last segment of the wireless connection 570 provided to the UE 530 using the OTT connection 550. More precisely, the teachings of these embodiments can improve data rates and delays, for example by allowing more flexible scheduling of time domain resources, thereby providing benefits such as reduced user waiting time.
[0290] In order to monitor data rates, latency, and other factors improved by one or more embodiments, a measurement process is provided. There may also be an optional network function for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 550 can be implemented in the software 511 and hardware 515 of the host computer 510 or in the software 531 and hardware 1035 of the UE 530, or in both. In an embodiment, a sensor (not shown) can be deployed in or associated with a communication device through which the OTT connection 550 passes; the sensor can 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 511, 531 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not necessarily affect the base station 520, and it may be unknown or imperceptible to the base station 520. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 510's measurements of throughput, propagation time, latency, etc. The measurements may be implemented so that messages (particularly empty or "fake" messages) are sent using the OTT connection 550 while the software 511 and 531 monitors propagation time, errors, etc.
[0291] Fig.11 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a reference Fig. 9 and Fig.10In order to simplify the present disclosure, this section will only include the host computers, base stations and UEs described in the present disclosure. Fig.11 . In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission to the UE carrying the user data. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
[0292] Fig.12 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a reference Fig. 9 and Fig.10 In order to simplify the present disclosure, this section will only include the host computers, base stations and UEs described in the present disclosure. Fig.12 . In step 710 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 720, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be transmitted via a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.
[0293] Fig.13 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a reference Fig. 9 and Fig.10 The host computers, base stations and UEs described in the present invention are as follows. To simplify the present disclosure, this section only includes Fig.13. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application that provides user data in response to the 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, the UE initiates sending user data to the host computer in sub-step 830 (which may be optional). In step 840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.
[0294] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a reference Fig. 9 and Fig.10 In order to simplify the present disclosure, only the host computers, base stations and UEs described in the present invention are included in this section. Fig.14 In step 910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.
[0295] Group C Example
[0296] 39. A wireless device configured to perform any of the steps of any one of Group A embodiments.
[0297] 40. A network node (eg, a base station) configured to perform any of the steps of any one of Group B embodiments.
[0298] 41. A wireless device, comprising:
[0299] - a processing circuit configured to perform any of the steps of any one of the Group A embodiments; and
[0300] - A power circuit configured to provide power to the wireless device.
[0301] 42. A base station, comprising:
[0302] - a processing circuit configured to perform any of the steps of any one of Group B embodiments;
[0303] - A power circuit configured to provide power to the wireless device.
[0304] 43. A user equipment (UE), the UE comprising:
[0305] - an antenna configured to send and receive wireless signals;
[0306] - a radio front end circuit connected to the antenna and the processing circuit and configured to condition signals transmitted between the antenna and the processing circuit;
[0307] - a processing circuit configured to perform any of the steps of any one of the Group A embodiments;
[0308] - an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;
[0309] - an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and
[0310] - A battery connected to the processing circuit and configured to provide power to the UE.
[0311] 44. A communication system including a host computer, comprising:
[0312] - a processing circuit configured to provide user data; and
[0313] - a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
[0314] - wherein the cellular network comprises a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any of the steps of any one of the Group B embodiments.
[0315] 45. The communication system according to the preceding embodiment further comprises a base station.
[0316] 46. The communication system according to the two preceding embodiments further comprises a UE, wherein the UE is configured to communicate with a base station.
[0317] 47. The communication system according to the three preceding embodiments, wherein:
[0318] - the processing circuitry of the host computer is configured to execute a host application to provide user data; and
[0319] - The UE comprises a processing circuit configured to execute a client application associated with a host application.
[0320] 48. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:
[0321] - providing user data at a host computer; and
[0322] - At a host computer, initiating a transmission carrying user data to the UE via a cellular network including a base station, wherein the base station performs any steps of any one of the Group B embodiments.
[0323] 49. The method according to the preceding embodiment further comprises sending user data at a base station.
[0324] 50. The method of either preceding embodiment, wherein the user data is provided on a host computer by executing a host application, the method further comprising executing a client application associated with the host application at the UE.
[0325] 51. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform any one of the methods of the three preceding embodiments.
[0326] 52. A communication system including a host computer, comprising:
[0327] - a processing circuit configured to provide user data; and
[0328] - a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
[0329] - wherein the UE comprises a radio interface and a processing circuit, and the components of the UE are configured to perform any steps of any of any embodiments of Group A.
[0330] 53. The communication system according to the preceding embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.
[0331] 54. The communication system according to the two preceding embodiments, wherein:
[0332] - the processing circuitry of the host computer is configured to execute a host application to provide user data; and
[0333] - The processing circuitry of the UE is configured to execute a client application associated with the host application.
[0334] 55. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:
[0335] - providing user data on a host computer; and
[0336] - At the host computer, initiating a transmission carrying user data to the UE via a cellular network including a base station, wherein the UE performs any steps of any one of the Group A embodiments.
[0337] 56. The method according to the preceding embodiment further comprises receiving user data from a base station at a UE.
[0338] 57. A communication system including a host computer, comprising:
[0339] - a communication interface configured to receive user data originating from a user equipment (UE) sent to a base station,
[0340] - wherein the UE comprises a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any steps of any one of the embodiments of Group A.
[0341] 58. The communication system according to the aforementioned embodiment further includes a UE.
[0342] 59. The communication system according to the two preceding embodiments further comprises a base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.
[0343] 60. The communication system according to the three preceding embodiments, wherein:
[0344] - the processing circuitry of the host computer is configured to execute a host application; and
[0345] - The processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data.
[0346] 61. The communication system according to the four preceding embodiments, wherein:
[0347] - the processing circuitry of the host computer is configured to execute the host application to provide the requested data; and
[0348] - The processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the request data.
[0349] 62. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
[0350] - At a host computer, receiving user data sent to a base station from a UE, wherein the UE performs any steps of any one of the embodiments of Group A.
[0351] 63. The method according to the aforementioned embodiment further comprises providing user data to the base station at the UE.
[0352] 64. The method according to the above two embodiments further comprises:
[0353] - executing a client application at the UE, thereby providing user data to be sent; and
[0354] - At the host computer, executing a host application associated with the client application.
[0355] 65. The method according to the above three embodiments further comprises:
[0356] - executing a client application at the UE; and
[0357] - receiving, at the UE, input data for the client application, the input data being provided at the host computer by executing a host application associated with the client application,
[0358] - wherein user data to be sent is provided by the client application in response to input data.
[0359] 66. A communication system comprising a host computer, the host computer comprising a communication interface configured to receive user data originating from a user equipment (UE) sent to a base station, wherein the base station comprises a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform any step of any one of the embodiments of Group B.
[0360] 67. The communication system according to the preceding embodiment further comprises a base station.
[0361] 68. The communication system according to the two preceding embodiments further comprises a UE, wherein the UE is configured to communicate with a base station.
[0362] 69. The communication system according to the three preceding embodiments, wherein:
[0363] - the processing circuitry of the host computer is configured to execute a host application;
[0364] - The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.
[0365] 70. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:
[0366] - receiving at a host computer from a base station user data originating from a transmission that the base station has received from a UE, wherein the UE performs any of the steps of any one of the Group A embodiments.
[0367] 71. The method according to the preceding embodiment further comprises receiving user data from the UE at the base station.
[0368] 72. The method of either preceding embodiment, further comprising initiating, at the base station, transmission of the received user data to a host computer.
Claims
1. A method for determining time domain resource allocation performed by a wireless device (110), the method comprising: receiving downlink control information DCI scheduling downlink transmission from a network node (160); detecting a radio network temporary identifier RNTI used in scheduling the downlink transmission; selecting a time domain resource allocation table from a plurality of different time domain resource allocation tables based on the detected RNTI, wherein each of the different time domain resource allocation tables is defined by a plurality of entries, the plurality of entries specifying different combinations of starting orthogonal frequency division multiplexing (OFDM) symbols and OFDM symbol durations for time domain resource allocation; as well as A time domain resource allocation for the downlink transmission is determined based on a time domain resource allocation field in the DCI, the time domain resource allocation field indicating an entry within a selected time domain resource allocation table.
2. The method according to claim 1, wherein: The multiple different time domain resource allocation tables are related to time domain resource allocation for physical downlink shared channel PDSCH scheduling.
3. The method according to any one of claims 1 to 2, wherein: The plurality of different time domain resource allocation tables include at least one predefined table having default values for the time domain resource allocation.
4. The method according to any one of claims 1 to 2, wherein: The plurality of different time domain resource allocation tables include at least one radio resource control (RRC) configuration table.
5. The method according to any one of claims 1 to 2, further comprising: A physical downlink shared channel (PDSCH) is received on time domain resources corresponding to the determined time domain resource allocation.
6. The method according to any one of claims 1 to 2, wherein: Selecting the time domain resource allocation table further includes selecting the time domain resource allocation table based on at least one of a control resource set CORESET and a search space for scheduling the downlink transmission.
7. The method according to any one of claims 1 to 2, wherein: A first table among the plurality of different time-domain resource allocation tables includes a different number of entries than a second table among the plurality of different time-domain resource allocation tables.
8. The method according to any one of claims 1 to 2, wherein: The multiple different time-domain resource allocation tables include the same number of entries.
9. A wireless device (110) configured to determine time domain resource allocation, the wireless device comprising: a memory configured to store instructions; processing circuitry configured to execute the instructions to: receiving downlink control information DCI scheduling downlink transmission from a network node (160); detecting a radio network temporary identifier RNTI used in scheduling the downlink transmission; selecting a time domain resource allocation table from a plurality of different time domain resource allocation tables based on the detected RNTI, wherein each of the different time domain resource allocation tables is defined by a plurality of entries, the plurality of entries specifying different combinations of starting orthogonal frequency division multiplexing (OFDM) symbols and OFDM symbol durations for time domain resource allocation; as well as A time domain resource allocation for the downlink transmission is determined based on a time domain resource allocation field in the DCI, the time domain resource allocation field indicating an entry within a selected time domain resource allocation table.
10. The wireless device of claim 9, wherein: The multiple different time domain resource allocation tables are related to time domain resource allocation for physical downlink shared channel PDSCH scheduling.
11. The wireless device according to any one of claims 9 to 10, wherein: The plurality of different time domain resource allocation tables include at least one predefined table having default values for the time domain resource allocation.
12. The wireless device according to any one of claims 9 to 10, wherein: The plurality of different time domain resource allocation tables include at least one radio resource control (RRC) configuration table.
13. The wireless device of any one of claims 9 to 10, the processing circuit being further configured to execute the instructions to: A physical downlink shared channel (PDSCH) is received on time domain resources corresponding to the determined time domain resource allocation.
14. The wireless device according to any one of claims 9 to 10, the processing circuit is further configured to execute the instructions to select the time domain resource allocation table based on at least one of a control resource set CORESET and a search space for scheduling the downlink transmission.
15. The wireless device according to any one of claims 9 to 10, wherein: A first table of the plurality of different time domain resource allocation tables comprises a different number of entries than a second table of the plurality of different time domain resource allocation tables, or wherein the plurality of different time domain resource allocation tables comprise the same number of entries.
