FLEXIBLE PROGRAMMING IN NOVA RADIO NETWORKS (NR)

专利摘要:
aspects of the present disclosure provide a mechanism for flexible scheduling of concessions for downlink and uplink transmissions. in some examples, a concession can be programmed using several control signals, where subsequent control signals can modify one or more properties of the concession. for example, the lease can be modified to add a package to the lease for transmission on a different set of frequency and time resources or a different set of layers of multiple inputs and multiple outputs (mimo), modify a resource allocation frequency and time of the concession, modify the form of where used for the concession, modify the transmission diversity scheme used for the concession, or indicate the specific process for the package.
公开号:BR112019022028A2
申请号:R112019022028-3
申请日:2018-04-25
公开日:2020-05-12
发明作者:Akkarakaran Sony；Luo Tao；Sadiq Bilal
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

FLEXIBLE PROGRAMMING IN NOVA RADIO NETWORKS (NR)
CROSS REFERENCE WITH RELATED REQUESTS
[0001] This application claims priority and benefit from Provisional Patent Application No. 62 / 489,981, filed with the United States Patent and Trademark Office on April 25, 2017 and from Non-Provisional Patent Application No. 15 / 961,446, filed with the United States Patent and Trademark Office on April 24, 2018, the contents of which in its entirety are incorporated into this document by reference as if fully disclosed below in its entirety and for all applicable purposes.
TECHNICAL FIELD
[0002] The technology discussed below relates in general to non-wired communication systems, and more particularly, to programming downlink and uplink transmissions in non-wired communication systems.
INTRODUCTION
[0003] Unwired communication networks are widely used to provide various telecommunication services such as telephony, video, data, message exchanges, broadcasting, among others. Such networks, which are usually multiple access networks, support communications for multiple users by sharing available network resources.
[0004] Legacy non-wired communication networks (for example, 4G), such as the Long Term Evolution (LTE) network, may allow multiple packets to be transmitted to the same user equipment (UE) on different communication resources. frequency and time within the
Petition 870190106063, of 10/21/2019, p. 6/145
2/94 same subframe. However, there are scheduling restrictions on the types of transmissions allowed for the same UE when different frequency and time resources are being used within the same subframe. In particular, a UE may not receive multiple unicast transmissions (for example, transmissions from a base station to a single UE) on different frequency and time resources within the same subframe.
[0005] In general, since a base station reserves the frequency and downlink time resources within a subframe for the transmission of a packet to one or more UEs, the base station generates a physical downlink control channel ( PDCCH) containing downlink control information (DCI) indicating the resources reserved for the package and scrambling the DCI with a temporary radio network identifier (RNTI) that can be used by a UE to identify a DCI containing information belonging to that HUH. To reduce the amount of decoding performed by the UE in the DCI, only a PDCCH / DCI can be shuffled with a specific RNTI from the UE (for example, the Cell RNTI or C-RNTI) to the UE within a subframe. Other packets that can be transmitted at different frequency and time resources within the same subframe can be, for example, broadcast packets (for example, packets transmitted from the base station to several UEs). The DCI generated for a broadcast packet can be scrambled, for example, with a system RNTI (for example, a System Information RNTI or SI-RNTI).
[0006] LTE networks additionally support the
Petition 870190106063, of 10/21/2019, p. 7/145
3/94 transmission of several packets to the same UE on the same frequency and time resources during the same subframe. However, packages are spatially separated from one another, using a Multiple Inputs and Multiple Outputs (MIMO) approach. In this example, each packet can be assigned the same hybrid automatic repeat request (HARQ) process identifier (ID) to provide packet recognition. Each HARQ process ID identifies a respective parallel stop and wait (SAW) process running at the base station and the UE. In addition, downlink assignments for both packages are included in the same PDCCH and the same modulation and encoding scheme (MCS) is used for both packages.
[0007] For next generation networks (eg 5G), such as the Nova Radio network, additional flexibility in scheduling packets for a UE may be required to meet the strict requirements for data speed and latency.
BRIEF SUMMARY OF SOME EXAMPLES
[0008] The following statement presents a summary of one or more aspects of the present disclosure, in order to provide a basic understanding of such aspects. This summary is not an overview of all the features contemplated in the disclosure, nor is it intended to identify key or critical elements of all aspects of the disclosure or to outline the scope of one or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the revelation as a prelude to the more detailed description
Petition 870190106063, of 10/21/2019, p. 8/145
4/94 which is presented later.
[0009] Several aspects of the disclosure refer to mechanisms for flexible scheduling of concessions (for example, downlink assignments or uplink concessions) for user equipment (UEs). A base station can schedule a lease for a package to a UE and transmit a first control channel (for example, a PDCCH) including the first control information (for example, the DCI) that includes the lease for the package to the UE . The base station can then modify at least one concession property to produce the concession modification information. For example, the base station can add a concession package for transmission on a different set of frequency and time resources or a different set of MIMO layers, modify a concession frequency and time resource allocation, modify the form waveform used for the concession, modify the transmission diversity scheme used for the concession or indicate specific processing for the packet. The base station can then transmit a second control channel including the second control information that includes at least the grant modification information to the UE.
[0010] In some examples, the second control channel can be transmitted within the same partition as the first control channel, within a subsequent partition as the first control channel or subsequent to the transmission of the packet. In examples where the grant modification information adds a packet to be transmitted within the same partition in a set
Petition 870190106063, of 10/21/2019, p. 9/145
5/94 different from MIMO layers, the same or different hybrid automatic repeat request (HARQ) process identifiers (IDs) can be assigned to each of the packages.
[0011] In one aspect of the disclosure, a method for a programming entity to schedule transmissions with a set of one or more entities programmed on an unwired communication network is provided. The method includes scheduling a lease including a downlink assignment or an uplink lease for a first packet to a first programmed entity in the set of one or more programmed entities and transmitting a first control channel including the first control information to the first entity programmed, where the first control information includes the concession for the first package. The method additionally includes modifying at least one property of several concession properties to produce the concession modification information and transmitting a second control channel including the second control information to the first programmed entity, where the second control information includes at least the concession modification information.
[0012] Another aspect of the disclosure provides a programming entity in a non-wired communication network. The programming entity includes a processor, a transceiver coupled communicatively with the processor and a memory coupled communicatively with the processor. The processor is configured to schedule a lease, including a downlink assignment or a
Petition 870190106063, of 10/21/2019, p. 10/145
6/94 uplink for a first packet for a first programmed entity from a set of one or more programmed entities in unwired communication with the programmed entity and transmit a first control channel, including the first control information to the first programmed entity, where the first control information includes the concession for the first package. The processor is further configured to modify at least one property of various properties of the concession to produce the concession modification information and transmit a second control channel including the second control information to the first programmed entity, where the second control information includes at least grant modification information.
[0013] Another aspect of the disclosure provides a programming entity in a non-wired communication network. The scheduling entity includes a means to schedule a lease, including a downlink assignment or a uplink lease for a first package to a first scheduled entity from a set of one or more entities scheduled in unwired communication with the scheduling entity and medium to transmit a first control channel including the first control information to the first programmed entity, where the first control information includes the concession for the first packet. The method additionally includes a means to modify at least one property of the various concession properties to produce the concession modification information and a means to transmit a second control channel including the second control information.
Petition 870190106063, of 10/21/2019, p. 11/145
7/94 control for the first programmed entity, where the second control information includes at least the concession modification information.
[0014] Another aspect of the disclosure provides a non-temporary, computer-readable medium for storing computer executable code. The computer-readable, non-temporary medium includes the code to have a programming entity on a non-wired communication network program a lease, including a downlink assignment or an uplink lease for a first packet to a first programmed entity of a a set of one or more programmed entities in non-wired communication with the programmed entity and transmit a first control channel, including the first control information to the first programmed entity, where the first control information includes the concession of the first packet. The computer-readable non-temporary medium additionally includes code to cause the programming entity to modify at least one property of the various concession properties to produce the concession modification information and transmit a second control channel including the second control information to the first programmed entity, where the second control information includes at least the concession modification information.
[0015] These and other aspects of the invention will become more fully understood upon inspection of the detailed description below. Other aspects, characteristics and embodiments of the present invention will become more evident to those skilled in the art, after
Petition 870190106063, of 10/21/2019, p. 12/145
8/94 inspect the following description of specific illustrative embodiments of the present invention in conjunction with the accompanying figures. Although the features of the present invention can be discussed in relation to some embodiments and figures below, all embodiments of the present invention can include one or more of the advantageous features discussed in this document. In other words, while one or more embodiments can be discussed as having some advantageous features, one or more of such features can also be used in accordance with the various embodiments of the invention discussed in this document. Similarly, while illustrative embodiments can be discussed below as device, system or method embodiments, it should be understood that such illustrative embodiments can be implemented in various devices, systems and methods.
BRIEF DESCRIPTION OF THE DRAWINGS
[0016] FIG. 1 is a schematic illustration of a non-wired communication system.
[0017] FIG. 2 is a conceptual illustration of an example of a radio access network.
; 0018 ] FIG. 3 is one diagram illustrating one example in an frame structure for use in an network access by radio. ; 0019 ] FIG. 4 is one diagram illustrating one example in an centered partition at the downlink (DL). ; 0020 ] FIG. 5 is one diagram illustrating one example in an centered partition in uplink (UL). ; 0021 ] FIG. 6 is one diagram illustrating one
Petition 870190106063, of 10/21/2019, p. 13/145
9/94 example of a non-wired communication system that supports the Multiple Inputs and Multiple Outputs (MIMO) technology.
[0022] FIG. 7 is a block diagram illustrating an example of hardware implementation for a programming entity employing a processing system in accordance with some aspects of the present disclosure.
[0023] FIG. 8 is a block diagram illustrating an example of hardware implementation for a programmed entity employing a processing system in accordance with some aspects of the present disclosure.
[0024] FIG. 9 illustrates an example of scheduling a lease for at least one packet transmitted within a partition, using multiple control channels, according to some aspects of the present disclosure.
[0025] FIG. 10 illustrates another example of scheduling a lease for at least one packet transmitted within a partition, using multiple control channels, according to some aspects of the present disclosure.
[0026] FIG. 11 illustrates another example of scheduling a lease for at least one packet transmitted within a partition, using multiple control channels, according to some aspects of the present disclosure.
[0027] FIG. 12 illustrates another example of scheduling a lease for at least one packet transmitted within a partition, using several
Petition 870190106063, of 10/21/2019, p. 14/145
10/94 control channels, according to some aspects of the present disclosure.
[0028] FIG. 13 illustrates another example of scheduling a concession for at least one package within a single control channel using various control information in accordance with some aspects of the present disclosure.
[0029] FIG. 14 illustrates an example of programming multiple packets for transmission on a partition using different MIMO layers according to some aspects of the disclosure.
[0030] FIG. 15 illustrates another example of scheduling multiple packets for transmission on a partition using different MIMO layers according to some aspects of the disclosure.
[0031] FIG. 16 illustrates an example of downlink control information, including a concession having modifiable concession properties in accordance with some aspects of the present disclosure.
[0032] FIG. 17 is a flowchart illustrating an illustrative process for scheduling a concession using various control signals in accordance with some aspects of the present disclosure.
[0033] FIG. 18 is a flowchart illustrating another illustrative process for scheduling a concession using various control signals in accordance with some aspects of the present disclosure.
[0034] FIG. 19 is a flow chart illustrating another illustrative process for scheduling a concession using various control signals according to some
Petition 870190106063, of 10/21/2019, p. 15/145
11/94 aspects of the present disclosure.
[0035] FIG. 20 is a flowchart illustrating another illustrative process for scheduling a concession using various control signals in accordance with some aspects of the present disclosure.
[0036] FIG. 21 is a flowchart illustrating another illustrative process for scheduling a concession using various control signals in accordance with some aspects of the present disclosure.
DETAILED DESCRIPTION
[0037] The detailed description set out below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described in this document can be practiced. The detailed description includes specific details for the purpose of providing a complete understanding of various concepts. However, it will be evident to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are presented in the form of a block diagram in order to avoid obscuring these concepts.
[0038] Although the aspects and embodiments are described in this application by way of illustration for some examples, those skilled in the art will understand that additional implementations and use cases can occur in several different arrangements and scenarios. The innovations described in this document can be implemented on several different types of platforms, devices,
Petition 870190106063, of 10/21/2019, p. 16/145
12/94 systems, formats, sizes, packaging arrangements. For example, embodiments and / or uses may arise via integrated chip embodiments and other devices based on non-modular components (for example, end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping, medical devices, AI enabled devices, etc.). Although some examples may or may not be specifically targeted to use cases or applications, there may be a wide range of applicability of the innovations described. Implementations can vary a spectrum from the chip level or with modular components to non-modular and non-chip implementations, and in addition to aggregated, distributed or OEM devices or systems, incorporating one or more aspects of the described innovations. In some practical configurations, devices incorporating described aspects and features may also necessarily include additional components and features for implementing and practicing claimed and described embodiments. For example, the transmission and reception of non-wired signals necessarily includes several components for analog and digital purposes (for example, hardware components, including antenna, RE chains, power amplifiers, modulators, storage (buffer), processor (processors) , interleaver, adders, etc.). It is intended that the innovations described in this document can be practiced in a wide variety of
Petition 870190106063, of 10/21/2019, p. 17/145
13/94 devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitutions.
[0039] The various concepts presented throughout this disclosure can be implemented through a wide variety of telecommunication systems, network architectures and communication standards. Referring now to FIG. 1, as an illustrative example without limitation, the various aspects of the present disclosure are illustrated with reference to an unwired communication system 100. Unwired communication system 100 includes three interaction domains: a main network 102, an access network radio (RAN) 104, and user equipment (UE) 106. Due to the non-wired communication system 100, the UE 106 can be enabled to perform data communication with an external data network 110, such as (but limited a) the Internet.
[0040] RAN 104 can implement any appropriate wired communication technology or technologies to provide radio access to the UE 106. As an example, RAN 104 can operate in accordance with the Nova Rádio (NR) specifications of the Parceria de Projeto Third Generation (3GPP), often referred to as 5G. As another example, RAN 104 can operate under a hybrid of 5G NR standards and standards of the Evolved Terrestrial Radio Universal Access Network (eUTRAN), generally referred to as LTE. 3GPP refers to this hybrid RAN as a next generation RAN, or NG-RAN. Obviously, several other examples can be used within the scope of the present disclosure.
Petition 870190106063, of 10/21/2019, p. 18/145
14/94
[0041] As illustrated, RAN 104 includes several base stations 108. In general terms, a base station is a network element in a radio access network responsible for transmitting and receiving radio in one or more cells to or from of an UE. In different technologies, patterns or contexts, a base station can be referred to differently by those skilled in the art as a base transceiver station (BTS), a base station, a radio transceiver, a transceiver function, a set of basic services (BSS ), a set of services
extended (ESS), one point of access (AP), a NodeB (NB), an eNode B (eNB), a gNode B (gNB) or some another proper terminology • [0042] A network access by radio 104 is
additionally illustrated, supporting non-wired communication for multiple mobile devices. A mobile device can be referred to as user equipment (EU) in 3GPP standards, but it can also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, a subscriber unit, an unwired unit, a remote unit, a mobile device, an un-wired device, an un-wired communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, an un-wired terminal, a remote terminal , a handset, a terminal, a user agent, a mobile client, a client or some other suitable terminology. A UE can be a device that provides the user with access to network services.
[0043] Within the present document, a
Petition 870190106063, of 10/21/2019, p. 19/145
15/94 mobile device does not necessarily need to be able to move and can be stationary. The term mobile device or mobile device refers widely to a diverse variety of devices and technologies. UEs can include various structural hardware components sized, modeled and arranged to aid communication; these components can include antennas, antenna sets, RE chains, amplifiers, one or more processors, etc. electrically coupled with each other. For example, some non-limiting examples of a mobile device include a cell phone, a cell phone (cell), a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC), a notebook, a netbook, smartbook, tablet, a personal digital assistant (PDA) and a wide variety of embedded systems, for example, corresponding to an Internet of Things (IoT). A mobile device can additionally be an automotive or other transport vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, multicopter, quadcopter, remote control device, consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker , a digital audio player (e.g. MP3 player), camera, game console, etc. A mobile device can additionally be a digital home device or a home device
Petition 870190106063, of 10/21/2019, p. 20/145
16/94 smart, such as a home audio, video and / or multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. A mobile device can additionally be an intelligent energy device, a security device, a solar panel or photovoltaic solar panel, a municipal infrastructure device that controls electricity (for example, a smart grid), lighting, water etc. .; a corporate and industrial automation device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships and armament, etc. In addition, a mobile device can provide support connected to medicine or telemedicine, that is, remote healthcare. Telehealth devices may include telehealth monitoring devices and telehealth management devices, the communication of which may receive preferential treatment or priority access over other types of information, for example, in terms of priority access for transporting critical data from service and / or QoS relevant for transporting critical service data.
[0044] Unwired communication between a RAN 104 and a UE 106 can be described as using an overhead interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmission. According to some aspects of the present disclosure, the term downlink can refer to a transmission from point to multipoint originating
Petition 870190106063, of 10/21/2019, p. 21/145
17/94 in a programming entity (described further below; for example, base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. In accordance with additional aspects of the present disclosure, the term uplink can refer to a point-to-point transmission originating in a programmed entity (described further below; for example, UE 106).
[0045] In some examples, access to the air interface can be programmed, where a programming entity (for example, a base station 108) allocates resources for communication between some or all devices and equipment within its area or cell of service. Within the present disclosure, as further discussed below, the programming entity may be responsible for programming, assigning, reconfiguring and releasing resources to one or more programmed entities. That is, for programmed communication, UEs 106, which can be programmed entities, can use resources allocated by the programming entity 108.
[0046] Base stations 108 are not the only entities that can function as programming entities. That is, in some examples, a UE can function as a programming entity, programming resources for one or more programmed entities (for example, one or more other UEs).
[0047] As illustrated in FIG. 1, an entity
Petition 870190106063, of 10/21/2019, p. 22/145
Programming 18/94 108 can broadcast downlink traffic 112 to one or more programmed entities 106. In general terms, programming entity 108 is a node or device responsible for programming traffic on a non-wired communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more programmed entities 106 to programming entity 108. On the other hand, programmed entity 106 is a node or device that receives control information downlink 114, including, but not limited to, scheduling information (for example, a lease), timing or timing information or other control information from another entity on the non-wired communication network, such as the entity of programming 108.
[0048] Additionally, traffic information and / or uplink and / or downlink control information can be divided by time into frames, subframes, partitions and / or symbols. As used in this document, a symbol can refer to a unit of time that, in an orthogonal frequency division multiplexed waveform (OFDM), carries one resource element (RE) per subcarrier. A partition can contain 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Several subframes or partitions can be grouped together to form a single frame or radio frame. Obviously, these definitions are not necessary and any suitable scheme for organizing the waveforms can be used, and the various time divisions of the waveform can be of adequate duration.
Petition 870190106063, of 10/21/2019, p. 23/145
19/94
[0049] In general, base stations 108 may include a return transport channel interface for communication with a return transport channel portion 120 of the non-wired communication system. The return transport channel 120 can provide a link between a base station 108 and the main network 102. Additionally, in some examples, a return transport channel network can provide interconnection between the respective base stations 108. Various types of interfaces return transport channel can be used, such as a direct physical connection, a virtual network, among others, using any suitable transport network.
[0050] The main network 102 can be part of the non-wired communication system 100 and can be independent of the radio access technology used in RAN 104. In some examples, the main network 102 can be configured according to 5G standards ( for example, 5GC). In other examples, the main network 102 can be configured according to an evolved 4G packet core (EPC), or any other suitable standard or configuration.
[0051] Referring now to FIG. 2, by way of example and without limitation, a schematic illustration of a RAN 200 is provided. In some examples, RAN 200 may be the same as RAN 104 described above and illustrated in FIG. 1. The geographical area covered by the RAN 200 can be divided into cell regions (cells) that can be uniquely identified by user equipment (UE) based on an identification transmitted by broadcast from an access point or base station. FIG. 2
Petition 870190106063, of 10/21/2019, p. 24/145
20/94 illustrates macrocells 202, 204 and 206 and a small cell 208, each of which may include one or more sectors (not shown). A sector is a subarea of a cell. All sectors within a cell are served by the same base station. A radio link within a sector can be identified by a unique logical identification pertaining to that sector. In a cell that is divided into sectors, the various sectors within a cell can be formed by groups of antennas, with each antenna responsible for communicating with the UEs in a part of the cell.
[0052] In FIG. 2, the two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station may have an integrated antenna or may be connected with an antenna or RRH by feeder cables. In the illustrated example, cells 202, 204 and 126 can be referred to as macro cells, as base stations 210, 212 and 214 support cells having a large size. In addition, a base station 218 is shown in small cell 208 (for example, a micro cell, a peak cell, a femto cell, a home base station, a home Node B, an eNode B home, etc.) which can be overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell, as base station 218 supports a cell having a relatively small size. The dimensioning of the cells can be done according to the system design, as well as the restrictions of the components.
[0053] It must be understood that the access network
Petition 870190106063, of 10/21/2019, p. 25/145
Radio 21/94 200 can include any number of base stations and non-wired cells. In addition, a retransmission node can be implemented to extend the size or area of coverage of a given cell. Base stations 210, 212, 214, 218 provide non-wired access points for a core network to any number of mobile devices. In some examples, the base stations 210, 212, 214 and / or 218 can be the same as the base station / programming entity 108 described above and illustrated in FIG. 1.
[0054] Within the RAN 200, cells can include UEs that can be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214 and 218 can be configured to provide an access point for a main network 102 (see FIG. 1) for all UEs in the respective cells. For example, UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UE 230 and 232 can be in communication with base station 214 via RRH 216; and UE 234 may be in communication with base station 218. In some instances, UEs 222, 224, 226, 228, 230, 232, 234, 238, 240 and / or 242 may be the same as the UE / entity programmed 106 described above and illustrated in FIG.
1.
[0055] In some examples, an unmanned aerial vehicle (UAV) 220, which can be a drone or a quadcopter, can be a mobile network node and can be configured to function as a UE. For example, UAV 220 can operate within cell 202 by communicating with the
Petition 870190106063, of 10/21/2019, p. 26/145
22/94 base station 210.
[0056] In an additional aspect of the RAN 200, sidelink signals can be used between UEs without necessarily relying on programming or control information from a base station. For example, two or more UEs (for example, UEs 226 and 228) can communicate using point-to-point (P2P) signals or sidelink 227 without relaying that communication through a base station (for example, base station 212 ). In an additional example, UE 238 is illustrated communicating with UEs 240 and 242. Here, UE 238 can function as a programming entity or a primary sidelink device, and UEs 240 and 242 can function as a programmed entity or a non-primary (for example, secondary) sidelink device. In yet another example, a UE can function as a programming entity on a device to device (D2D), point to point (P2P) or vehicle to vehicle (V2V) network and / or on a mesh network. In an example of a mesh network, UEs 240 and 242 can optionally communicate directly with each other, in addition to communicating with programming entity 238. Thus, in a non-wired communication system with programmed access to frequency resources and time and having a cellular configuration, a P2P configuration or a mesh configuration, a programming entity and one or more programmed entities can communicate using the programmed resources. In some instances, sidelink signals 227 include traffic and sidelink control. The sidelink control information may, in some instances, include a request signal, such as
Petition 870190106063, of 10/21/2019, p. 27/145
23/94 a request to send (RTS), a source transmission signal (STS) and / or a direction selection signal (DSS). The request signal can provide a programmed entity to request a length of time to maintain a sidelink channel available for a sidelink signal. The sidelink control information may additionally include a response signal, such as a Clear to send (CTS) and / or a destination receiving signal (DRS). The response signal can provide the programmed entity to indicate the availability of the sidelink channel, for example, for a requested period of time. An exchange of request and response signals (for example, a handshake) can allow different programmed entities executing sidelink communications to negotiate the availability of the sidelink channel before communicating sidelink traffic information.
[0057] In the radio access network 200, the ability of a UE to communicate while moving, regardless of its location, is referred to as mobility. The various physical channels between the UE and the radio access network are generally configured, maintained and released under the control of an access and mobility management function (AME, not shown, part of the main network 102 in FIG. 1), which can include a security context management (SCMF) function that manages the security context for the control plan and user plan functionality and a security anchor function (SEAF) that performs authentication.
[0058] A radio access network 200 can use DL-based mobility or mobility based on
Petition 870190106063, of 10/21/2019, p. 28/145
24/94 on UL to allow mobility and handovers (ie transferring a UE connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a programming entity, or at any other time, a UE can monitor various signal parameters from its service cell, as well as the various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more of the neighboring cells. During that time, if the UE moves from one cell to another, or if the signal quality of a neighboring cell exceeds that of the serving cell for a given period of time, the UE may perform a handoff or handover from the server cell to the neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, although any suitable form of UE can be used) can move from the corresponding geographic area for its service cell 202 to the geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds that of its service cell 202 for a specified period of time, UE 224 can transmit a report message to its service base station 210 indicating this condition. In response, the UE 224 can receive a handover command and the UE can be handovered to cell 206.
[0059] In a network configured for UL-based mobility, UL reference signals from each UE can be used by the network to select a service cell for each UE. In some examples,
Petition 870190106063, of 10/21/2019, p. 29/145
25/94 base stations 210, 212 and 214/216 can broadcast unified sync signals (for example, unified Primary Sync Signals (PSSs), unified Secondary Sync Signals (SSSs) and Physical Broadcast Channels (PBCH ) unified). UEs 222, 224, 226, 228, 230 and 232 can receive the unified sync signals, derive the carrier frequency and partition timing from the sync signals and, in response to the bypass timing, transmit an uplink pilot or reference signal. The uplink pilot signal transmitted by a UE (for example, UE 224) can be received simultaneously by two or more cells (for example, base stations 210 and 214/216) within radio access network 200. Each of the cells can measure a pilot signal strength and the radio access network (for example, one or more of base stations 210 and 214/216 and / or a central node within the main network) can determine a service cell for the UE 224. As the UE 224 moves through the radio access network 200, the network can continue to monitor the uplink pilot signal transmitted by the UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the strength or quality of the signal measured by the service cell, network 200 can handover the UE 224 from the service cell to the neighboring cell, with or without informing the UE 224.
[0060] Although the synchronization signal transmitted by base stations 210, 212 and 214/216 can be unified, the synchronization signal may not identify a specific cell, but it can identify a
Petition 870190106063, of 10/21/2019, p. 30/145
26/94 zone of several cells operating at the same frequency and / or with the same timing. The use of zones in 5G networks or other next generation communication networks allows for the uplink-based mobility structure and improves the efficiency of the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.
[0061] In various implementations, the air interface in the radio access network 200 can use the licensed spectrum, the unlicensed spectrum or the shared spectrum. The licensed spectrum provides exclusive use of part of the spectrum, usually by virtue of a mobile network operator acquiring a license from a government regulator. The unlicensed spectrum allows for the shared use of part of the spectrum without the need for a license granted by the government. Although compliance with some technical rules is additionally generally necessary to access the unlicensed spectrum, generally, any operator or device can gain access. The shared spectrum can be located between the licensed and the unlicensed spectrum, where technical rules or limitations may be necessary to access the spectrum, but the spectrum can additionally be shared by several operators and / or by several RATs. For example, a license holder for a part of the licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, for example, under the appropriate conditions determined by the licensee to obtain access.
Petition 870190106063, of 10/21/2019, p. 1/31
27/94
[0062] So that transmissions through the radio access network 200 obtain a low block error rate (BLER) while additionally reaching very high data rates, channel encoding can be used. That is, non-wired communication can generally use an appropriate error correction block code. In a typical block code, a message or information string is divided into code blocks (CBs) and an encoder (for example, a CODEC) in the transmitting device then mathematically adds redundancy to the information message. The exploitation of this redundancy in the coded information message can improve the reliability of the message, allowing the correction of any bit errors that may occur due to noise.
[0063] In the initial 5G NR specifications, user data traffic is encoded using the almost cyclic low density parity check (LDPC) with two different base graphics: a base graphic is used for large blocks of code and / or high code rates, while the other base graph is used in another way. Control information and the physical broadcast channel (PBCH) are encoded using Polar encoding, based on nested strings. For these channels, puncture, shortening and repetition are used for rate matching.
[0064] However, those skilled in the art will understand that aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of programming entities 108 and
Petition 870190106063, of 10/21/2019, p. 32/145
Programmed entities 106 may include suitable hardware and capabilities (for example, an encoder, a decoder and / or a CODEC) to use one or more of these channel codes for non-wired communication.
[0065] The aerial interface in the radio access network 200 may use one or more multiplexing and multiple access algorithms to allow simultaneous communication of the various devices. For example, the 5G NR specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210 and multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224, using multiplexing by orthogonal frequency division (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specifications provide support for the discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided using time division multiple access (TDMA), code division multiple access (CDMA), multiple access by frequency division (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA) or other suitable multiple access schemes.
In addition, multiplexing DL transmissions from base station 210 to UEs 222 and 224 can be provided using time division multiplexing (TDM), code division multiplexing (CDM),
Petition 870190106063, of 10/21/2019, p. 33/145
29/94 frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other suitable multiplexing schemes.
[0066] The air interface in the radio access network 200 may additionally use one or more duplexing algorithms. Duplex refers to a point-to-point communication link where the two endpoints can communicate with each other in both directions. Full duplex means that the two endpoints can communicate simultaneously. Half duplex means that only one endpoint can send information to the other at a time. On a non-wired link, a full duplex channel generally depends on the physical isolation of a transmitter and receiver and on appropriate interference cancellation technologies. Full duplex emulation is often implemented for non-wired links, using Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, sometimes the channel is dedicated to transmissions in one direction, while other times the channel is dedicated to transmissions in the other direction, where the direction can change very quickly, for example, several times per partition.
[0067] Various aspects of the present disclosure will be described with reference to an OFDM waveform, illustrated schematically in FIG. 3. Must be understood
Petition 870190106063, of 10/21/2019, p. 34/145
30/94 by those skilled in the art that the various aspects of the present disclosure can be applied to an SC-FDMA waveform in substantially the same manner as described in this document below. That is, although some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.
[0068] Referring now to FIG. 3, an expanded view of an illustrated DL subframe 302 is illustrated, showing an OFDM resource grid. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may vary from the example described in this document, depending on any number of factors. Here, time is in the horizontal direction with units of OFDM symbols; and the frequency is in the vertical direction with the subcarrier units.
[0069] Resource grid 304 can be used to schematically represent frequency and time resources for a given antenna port. That is, in a multi-input and multi-output (MIMO) implementation with several antenna ports available, a corresponding multiple number of resource grids 304 may be available for communication. The resource grid 304 is divided into several resource elements (REs) 306. An RE, which is 1 χ 1 symbol subcarrier, is the smallest discrete part of the frequency and time grid and contains a single complex value representing data from a channel or physical signal. Depending on the modulation used in a specific implementation, each RE can represent
Petition 870190106063, of 10/21/2019, p. 35/145
31/94 one or more bits of information. In some instances, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, a number independent of the numerology used. In some examples, depending on numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB 308 corresponds entirely to a single communication direction (transmission or reception for a given device).
[0070] A set of continuous or discontinuous resource blocks can be referred to in this document as a resource block group (RBG) or subband. A set of sub-bands can cover the entire bandwidth. Programming UEs (programmed entities) for downlink or uplink transmissions typically involves programming one or more resource elements 306 within one or more sub-bands. Thus, an UE usually uses only a subset of the 304 resource grid. In some instances, a RB may be the smallest unit of resources that can be allocated to an UE. Thus, the more RBs are programmed for a UE, and the larger the modulation scheme chosen for the air interface, the higher the data rate for the UE.
[0071] In this illustration, the RB 308 is shown to occupy less than the entire bandwidth of subframe 302, with some illustrated subcarriers
Petition 870190106063, of 10/21/2019, p. 36/145
32/94 above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Additionally, in this illustration, RB 308 is shown to occupy less than the entire duration of subframe 302, although this is only one possible example.
[0072] Each 1 ms 302 subframe can consist of one or more adjacent partitions. In the example shown in FIG. 3, a subframe 302 includes four partitions 310, as an illustrative example. In some examples, a partition can be defined according to a specified number of OFDM symbols with a given cyclic prefix length (CP). For example, a partition can include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-partitions having a shorter duration (for example, one or two OFDM symbols). These mini-partitions can in some cases be transmitted using resources programmed for the partition transmissions in progress to the same or to different UEs. Any number of resource blocks or groups of resource blocks (for example, groups of subcarriers and OFDM symbols) can be used within a subframe or partition.
[0073] An expanded view of one of the partitions 310 illustrates the partition 310 including a control region 312 and a data region 314. In general, the control region 312 can carry the control channels (for example, the PDCCH) and the data region 314 can carry the data channels (for example, PDSCH or PUSCH). Obviously, a partition can contain all
Petition 870190106063, of 10/21/2019, p. 37/145
33/94
DL, all UL or at least a part of DL and at least a part of UL. The simple structure illustrated in FIG. 3 is merely illustrative in nature, and different partition structures can be used and may include one or more of each of the control regions and data regions.
[0074] Although not illustrated in FIG. 3, the various REs 306 within an RB 308 can be programmed to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilot signals or reference signals, including, but not limited to, a demodulation reference signal (DMRS), a control reference signal (CRS) or an audible reference signal ( SRS). These pilot signals or reference signals can provide a receiving device to perform the channel estimation of the corresponding channel, which can allow for coherent demodulation / detection of the control and / or data channels within the RB 308.
[0075] In a DL transmission, the transmission device (for example, programming entity 108) can allocate one or more REs 306 (for example, within a 312 control region) to carry DL control information , including one or more DL control channels, such as a PBCH; a PSS; an SSS; a physical control format indicator channel (PCFICH); a physical hybrid auto-repeat request (HARQ) indicator channel (PHICH); and / or a physical downlink control channel (PDCCH) etc. for one or more scheduled entities. THE
Petition 870190106063, of 10/21/2019, p. 38/145
34/94
PCFICH provides information to assist a receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), including, but not limited to power control commands, programming information, a grant and / or an assignment of REs for DL and UL transmissions. 0
PHICH carries HARQ feedback transmissions, such as recognition (ACK) or negative recognition (NACK). HARQ is a technique well known to those skilled in the art, where the integrity of packet transmissions can be checked on the receiving side for accuracy, for example, using any suitable integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK can be transmitted, while, if not confirmed, a NACK can be transmitted. In response to a NACK, the transmitting device can send an HARQ retransmission, which can implement chase combination, incremental redundancy, etc.
[0076] In a UL transmission, the transmission device (for example, programmed entity 106) can use one or more REs 306 to carry UL control information, including one or more UL control channels, as a channel physical uplink control (PUCCH), for the programming entity. UL control information can include a variety of packet types and categories, including pilots, reference signals and information configured to allow or assist in decoding data transmissions from
Petition 870190106063, of 10/21/2019, p. 39/145
35/94 uplink. In some instances, the control information may include a scheduling request (SR), that is, the request for the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the control channel, the programming entity can transmit the downlink control information which can program the resources for the uplink packet transmissions. UL control information can also include HARQ feedback, channel state feedback (CSF) or any other appropriate UL control information.
[0077] In addition to the control information, one or more REs 306 (for example, within the data region 314) can be allocated for user data traffic. Such traffic can be carried on one or more traffic channels, such as, for a DL transmission, a shared physical downlink channel (PDSCH); or for a UL transmission, a shared physical uplink (PUSCH) channel. In some examples, one or more REs 306 within the data region 314 can be configured to carry system information blocks (SIBs), carrying information that can allow access to a given cell.
[0078] These physical channels described above are usually multiplexed and mapped to transport annals for manipulation in the medium access control layer (MAC). Transport channels carry blocks of information called transport blocks (TB). The transport block size (TBS), which can correspond to a number of bits of information, can be a controlled parameter, based on the modulation scheme and
Petition 870190106063, of 10/21/2019, p. 40/145
36/94 coding (MCS) and the number of RBs in a given transmission.
[0079] The channels or carriers illustrated in FIG. 3 are not necessarily all channels or carriers that can be used between a programming entity and the programmed entities, and those skilled in the art will recognize that other channels or carriers can be used in addition to those illustrated, such as other traffic, control and feedback.
[0080] According to one aspect of the disclosure, one or more partitions can be structured as independent partitions. For example, FIGs. 4 and 5 illustrate two illustrative structures of the independent partitions 400 and 500. The independent partitions 400 and / or 500 can be used, in some examples, in place of the partition 310 described above and illustrated in FIG. 3.
[0081] FIG. 4 is a diagram illustrating an example of a downlink-centered (DL) 400 partition according to some aspects of the disclosure. The DL-centered nomenclature generally refers to a structure where more resources are allocated for transmissions towards the DL (for example, transmissions from programming entity 108 to programmed entity 106). In the example shown in FIG. 4, time is shown along with a horizontal geometric axis, while frequency is shown along with a vertical geometric axis. The frequency and time resources of the DL 400-centered partition can be divided into a DL burst of 402, a traffic region of DL 404 and a burst of UL 406.
[0082] The burst of DL 402 can exist in the
Petition 870190106063, of 10/21/2019, p. 41/145
37/94 initial part or at the beginning of the partition centered on DL. The burst of DL 402 can include any suitable DL information on one or more channels. In some instances, the DL 402 burst may include various programming information and / or control information corresponding to various parts of the DL-centered partition. In some configurations, the burst of DL 402 may be a physical DL control channel (PDCCH), as indicated in FIG. 4. The DL centered partition can also include a DL 404 traffic region. The DL 404 traffic region can sometimes be referred to as the DL centered partition payload. The DL 404 traffic region can include the communication resources used to communicate DL user data traffic from programming entity 108 (for example, eNB) to programmed entity 106 (for example, UE) . In some configurations, the DL 404 traffic region can include a shared physical DL channel (PDSCH).
[0083] The UL 406 burst can include any suitable UL information on one or more channels. In some instances, the UL 406 burst may include feedback information corresponding to several other parts of the DL-centered partition. For example, the UL 406 burst may include the feedback information corresponding to the DL 402 burst and / or the DL 404 traffic region. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, an identifier (ID) of HARQ process, and / or various other suitable types of information. The burst of UL 406 can include additional or alternative information, such as the
Petition 870190106063, of 10/21/2019, p. 42/145
38/94 information pertaining to the procedures of the random access channel (RACH), the programming requests (SRs) (for example, within a PUCCH) and various other suitable types of information.
[0084] Here, a partition such as the partition centered on DL 400 can be referred to as an independent partition when all data transported in the DL 404 traffic region is programmed in the DL 402 burst of the same partition; and in addition, when all data carried in the DL 404 traffic region is recognized (or at least has an opportunity to be recognized) in the UL 406 burst of the same partition. In this way, each independent partition can be considered an independent entity, not necessarily requiring another partition to complete a transmission-acknowledgment programming cycle for a given package.
[0085] Like illustrated at FIG. 4, the end gives region in traffic from DL 404 can to be separated in time The leave of beginning of the UL burst 406. This separation in
time can sometimes be referred to as an interval, a guard period, a guard interval and / or several other suitable terms. This separation provides time for switching from DL communication (eg, receiving operation by programmed entity 106 (eg, UE)) to UL communication (eg, transmission by programmed entity 106 (eg, HUH)) . Those skilled in the art will understand that the foregoing is just an example of a partition centered on DL and alternative structures having similar characteristics may exist without necessarily
Petition 870190106063, of 10/21/2019, p. 43/145
39/94 deviate from the aspects described in this document.
[0086] FIG. 5 is a diagram showing an example of a partition centered on uplink (UL) 500 according to some aspects of the disclosure. The UL-centric nomenclature generally refers to a structure where more resources are allocated for transmissions towards UL (for example, transmissions from programmed entity 106 to programming entity 108). In the example shown in FIG. 5, time is shown along a horizontal geometric axis, while frequency is shown along a vertical geometric axis. The frequency and time resources of the UL 500-centered partition can be divided into a burst of DL 502, a traffic region of UL 504 and a burst of UL 506.
[0087] The DL 502 burst can exist at the beginning or at the beginning of the UL-centered partition. The burst of DL 502 in FIG. 5 may be similar to the burst of DL 402 described above with reference to FIG. 4. The UL centered partition can also include a UL 504 traffic region. The UL 504 traffic region can sometimes be called the UL centered partition payload. The UL 504 traffic region may include the communication resources used to communicate UL user data traffic from programmed entity 106 (e.g., UE) to programming entity 108 (e.g., eNB). In some configurations, the UL 504 traffic region can be a shared physical UL channel (PUSCH). As illustrated in FIG. 5, the burst end of DL 502 can be separated in time from the beginning of the UL 504 traffic region. This time, the separation can sometimes
Petition 870190106063, of 10/21/2019, p. 44/145
40/94 be referred to as an interval, guard period, guard interval and / or various other suitable terms. This separation provides time for the transition from DL communication (eg, receiving operation by programmed entity 106 (eg, UE)) to UL communication (eg, transmission by programmed entity 106 (eg, the EU)).
[0088] The burst of UL 506 in FIG. 5 may be similar to the burst of UL 406 described above with reference to FIG. 4. The burst of UL 506 can additionally or alternatively include the information pertaining to the channel quality indicator (CQI), the sound reference signals (SRSs) and the various other suitable types of information. Those skilled in the art will understand that the precedent is just an example of a UL-centered partition, and alternative structures with similar characteristics can exist without necessarily deviating from the aspects described in this document.
[0089] FIG. 6 illustrates an example of a non-wired communication system 600 supporting MIMO technology. In a MIMO system, a transmitter 602 includes several transmit antennas 604 (for example, N transmit antennas) and a receiver 606 includes several receive antennas 608 (for example, M receive antennas). Thus, there are N x M signal paths 610 from transmitting antennas 604 to receiving antennas 608. Each of transmitter 602 and receiver 606 can be implemented, for example, within a programmed entity, an entity programming or other non-wired communication device.
Petition 870190106063, of 10/21/2019, p. 45/145
41/94
[0090] The use of MIMO technology allows the non-wired communication system to explore the spatial domain to support spatial multiplexing, beam conformation and transmission diversity. Spatial multiplexing can be used to transmit the different data streams, also referred to as layers, simultaneously on the same frequency and time resource. Traffic flows can be transmitted to a single programmed entity or to the UE to increase the data rate or to the various programmed entities or UEs to increase the overall capacity of the system, the latter being referred to as multiuser MIMO (MU- MIMO). This is achieved by spatially pre-coding each traffic stream (that is, applying a scale of one amplitude and one phase) and then transmitting each pre-coded stream spatially through a respective transmission antenna on the downlink. Spatially pre-coded traffic flows arrive at the UE (s) with different spatial signatures, which allows each UE to retrieve the one or more traffic flows destined for that UE. In the uplink, each programmed entity or UE transmits a spatially pre-coded traffic flow, which allows the programming entity to identify the source of each spatially pre-coded traffic flow.
[0091] The number of flows or layers of traffic corresponds to the classification of the transmission. In general, the classification of the MIMO 600 system is limited by the number of transmit or receive antennas 604 or 608, whichever is less. Additionally, the channel conditions in the programmed entity, as well as other considerations, such as
Petition 870190106063, of 10/21/2019, p. 46/145
42/94 as the resources available in the programmed entity, can also affect the classification of the transmission. For example, the classification (and therefore the number of traffic flows) assigned to a particular programmed entity in the downlink can be determined based on the classification indicator (RI) transmitted from the programmed entity to the programming entity. The IR can be determined based on the antenna configuration (for example, the number of transmit and receive antennas) and the signal to interference plus noise ratio (SINR) on each of the receiving antennas. The IR can indicate, for example, the number of layers that can be supported under the current channel conditions. The scheduling entity can use the RI, along with the resource information (for example, the available resources and the amount of data to be programmed for the scheduled entity), to assign a transmission rating to the scheduled entity.
[0092] In Time Division Duplexing (TDD) systems, the uplink and downlink are reciprocal, as each uses different time partitions of the same frequency bandwidth. Thus, in TDD systems, the programming entity can assign the classification based on uplink SINR measurements (for example, based on a Sound Reference Signal (SRS) transmitted from the programmed entity or another pilot signal). Based on the assigned rating, the programming entity can then transmit the CSI-RS with separate C-RS sequences for each layer to provide multi-layer channel estimation. From the CSI-RS, the programmed entity can measure the quality of the channel through
Petition 870190106063, of 10/21/2019, p. 47/145
43/94 of the layers and resource blocks and feedback the channel quality indicator (CQI), the pre-coding matrix indicator (PMI) and the RI values for the programming entity for use in updating the classification and assign resource elements for future downlink transmissions.
[0093] In the simplest case, as shown in FIG. 6, a classification 2 space multiplexing transmission in a 2x2 MIMO antenna configuration will transmit a traffic stream from each transmitting antenna 604. Each traffic stream reaches each receiving antenna 608 along a different signal path 610. The receiver 606 can then reconstruct the
traffic using the signals received from decade antenna reception 608. [0094] In nets communication wired inherited (for example, to 4G) , the various packages (too
referred to in this document as transport blocks or code words) can be programmed in the same partition. However, there are several restrictions on programming. For example, when programming multiple DCIs within a PDCCH, each DCI is scrambled with a different temporary radio network identifier (RNTI) to identify the recipient (s) of the DCI, thus limiting the types of concessions that can be programmed simultaneously. Additionally, when multiple packages are programmed in the same frequency and time resources, but spatially separated from each other using MIMO, each package receives the same hybrid automatic repeat request process identifier (ID) and the
Petition 870190106063, of 10/21/2019, p. 48/145
44/94 concession for the two packages is included in the same PDCCH. Additionally, the same modulation and coding scheme (MCS) is used for both packages.
[0095] According to various aspects of this disclosure, to provide flexibility in programming downlink and uplink transmissions in the next generation (for example, 5G) wired communication networks, a concession (for example, an allocation of downlink or uplink lease) can be programmed using the various control signals, where subsequent control signals can modify one or more properties of the lease. In some examples, a lease for a package indicated in the first DCI of a first PDCCH can be modified by transmitting subsequent control information (for example, second DCI) on a subsequent control channel (for example, a second PDCCH). For example, the lease can be modified to add a package to the lease for transmission on a different set of frequency and time resources or on a different set of one or more MIMO layers on the same partition, modify a resource allocation for frequency and time of the concession, modify the waveform used for the concession, modify the transmission diversity scheme used for the concession or indicate specific processing for the package.
[0096] The first and second PDCCHs can be simultaneous (for example, within the same partition) or separated in time (for example, transmitted within different partitions). In some examples, the second PDCCH
Petition 870190106063, of 10/21/2019, p. 49/145
45/94 includes a new concession for an additional packet to be transmitted in one or more different MIMO layers of the same frequency and time resources or in one or more MIMO layers of different frequency and time resources in the same partition. When the same frequency and time resources are used for the starter package and the add-on package, the same HARQ process ID or different HARQ process IDs can be assigned to the packages. When different frequency and time resources are used for the add-on package, different HARQ process IDs can be assigned to each of the packages. The packages can additionally use different MCSs.
[0097] FIG. 7 is a conceptual diagram illustrating an example of hardware implementation for an illustrative programming entity 700 employing a processing system 714. For example, programming entity 700 can be a next generation (5G) base station, as illustrated in any one or more of FIGS. 1 and 2. In another example, programming entity 700 may be user equipment (UE), as illustrated in any one or more of FIGs. 1 and 2.
[0098] Programming entity 700 can be implemented with a processing system 714 that includes one or more processors 704. Examples of processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable port arrangements (FPGAs) ), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits and other suitable hardware
Petition 870190106063, of 10/21/2019, p. 50/145
46/94 configured to execute the various functionalities described throughout this disclosure. In several examples, programming entity 700 can be configured to perform any one or more of the functions described in this document. That is, processor 704, as used in a programming entity 700, can be used to implement any one or more of the processes described below. The processor 704 may, in some cases, be implemented via a baseband or modem chip and in other implementations, the 704 processor itself may comprise a number of distinct and different devices from a baseband chip or modem (for example , in such scenarios, can work together to achieve the achievements discussed in this document). And, as mentioned above, various layouts and hardware components outside of a baseband modem processor can be used in implementations, including RE chains, power amplifiers, modulators, storage devices, interleavers, adders, etc.
[0099] In this example, processing system 714 can be implemented with a bus architecture, generally represented by bus 702. Bus 702 can include any number of interconnecting buses and bridges, depending on the specific application of processing system 714 and general design restrictions. The 702 bus communicates several circuits, including one or more processors (usually represented by the 704 processor), a 705 memory and the computer-readable media (usually represented by the computer-readable medium)
Petition 870190106063, of 10/21/2019, p. 51/145
47/94
706). The bus 702 can also connect several other circuits, such as timing sources, peripherals, voltage regulators and power management circuits, which are well known in the art and, therefore, will not be described further. A bus interface 708 provides an interface between bus 702 and a transceiver 710. Transceiver 710 provides a means of communicating with various other devices via a transmission means (e.g., the overhead interface). Depending on the nature of the device, a 712 user interface (for example, numeric keypad, video, speaker, microphone, game controller) may also be provided. Obviously, this 712 user interface is optional and can be omitted in some examples, such as a base station.
[00100] The processor 704 is responsible for managing the bus 702 and for general processing, including running the software stored in the computer-readable medium 706. The software, when run by the processor 704, makes the processing system 714 perform the various functions described below for any particular device. Computer-readable media 706 and memory 705 can also be used to store data that is handled by processor 704 when running the software.
[00101] One or more 704 processors in the processing system can run the software. The software must be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms,
Petition 870190106063, of 10/21/2019, p. 52/145
48/94 software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution thread, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, description language hardware or otherwise. The software may reside on a computer-readable medium 706.
[00102] The computer-readable medium 706 can be a computer-readable non-temporary medium. A computer-readable non-temporary medium includes, for example, a magnetic storage device (for example, hard disk, floppy disk, magnetic stripe), an optical disk (for example, a compact disk (CD) or a versatile digital disk (DVD)), a smart card, a flash memory device (for example, a card, a pen drive or a key drive), a random access memory (RAM), a read-only memory (ROM), a Programmable ROM (FROM), an erasable FROM (EPROM), an electrically erasable PROM (EEPROM), a recorder, a removable disk and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium may also include, for example, a carrier wave, a transmission line and any other suitable medium for transmitting software and / or instructions that can be accessed and read by a computer. The computer-readable medium 706 can reside in the processing system 714, external to the processing system 714 or distributed by several entities, including the processing system 714. The computer-readable medium 706 can be
Petition 870190106063, of 10/21/2019, p. 53/145
49/94 embedded in a computer program product. For example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize the best way to implement the described functionality presented throughout this disclosure, depending on the specific application and the general design restrictions imposed on the general system.
[00103] In some aspects gives revelation, The processor 704 can include the system of circuits configured to the various functions. For example, The processor 704 can include a system in circuits in
scheduling and resource assignment 741, configured to generate, schedule and modify a resource assignment or resource assignment of frequency and time (for example, a set of one or more resource elements). For example, the 741 resource scheduling and resource circuits system can program frequency and time resources within various time division (TDD) and / or frequency division (FDD) subframes and partitions. ) to transport user data traffic and / or control information to and / or from various UEs (programmed entities).
[00104] In various aspects of the disclosure, the 741 resource assignment and programming circuit system can be configured to initially schedule a lease (for example, a downlink assignment or an uplink lease) for a package associated with a programmed entity and subsequently modify one or
Petition 870190106063, of 10/21/2019, p. 54/145
50/94 more concession properties to produce concession modification information. For example, grant modification information may indicate that additional resources have been reserved to transmit one or more additional packets (for example, a different set of frequency and time resources or a different set of MIMO layers in the same partition), an allocation of frequency and time resource of the concession has been modified, the waveform used for the concession has been modified, the diversity and transmission scheme used for the concession has been modified or the specific processing to be used for the package.
[00105] In some examples, the 741 resource assignment and programming circuit system may generate a first physical downlink control channel (PDCCH) carrying the first downlink control information (DCI), including the initial concession for transmission within a first partition and a second PDCCH carrying the second DCI including the grant modification information for transmission within a second partition that occurs later in time than the first partition. For example, the second partition can include the shared physical downlink channel (PDSCH) or the shared physical uplink channel (PUSCH) programmed to transmit the packet (s). In other examples, the grant modification information can be transmitted within a separate PDCCH on the same partition as the PDCCH containing the initial grant. In addition to other examples, the PDCCH containing the initial concession may include several DCIs, each containing a separate concession for
Petition 870190106063, of 10/21/2019, p. 55/145
51/94 the programmed entity (for example, a dynamic grant, a semi persistently scheduled grant and / or other types of grants) and the grant modification information can be transmitted within the different DCI (for example, the later DCI) of the than the DCI containing the initial concession of the same PDCCH.
[00106] Thus, the 741 resource assignment and programming circuit system can use a simultaneous or later PDCCH (or DCI within the same PDCCH) to modify a subset of properties (for example, fields, sections or information) of another Simultaneous or previous PDCCH (or DCI in the same PDCCH) for a downlink or uplink lease (for example, PDSCH or PUSCH) for modifying a value of one or more of the properties. In some examples, the previous PDCCH can be transmitted within the same partition on a previous OFDM symbol or on a previous partition, as discussed above.
[00107] In some examples, the properties and / or grants of the PDCCH that can potentially be modified can be displayed within the PDCCH. For example, an indication that a PDCCH property and / or concession may be modified may include one or more bits that may inform the programmed entity that the property and / or the concession may be modified, will be modified or will not be modified in a simultaneous or subsequent PDCCH (or the DCI within the same PDCCH). So one
Final PDCCH (or DCI in the same
PDCCH) for a set of resource elements in a partition may include an unmodified indicator or another indicator that the
PDCCH (or the DCI in the same PDCCH) is a final PDCCH. Require
Petition 870190106063, of 10/21/2019, p. 56/145
52/94 a final PDCCH can avoid the need for multiple chances of a lost concession. In some examples, a first (or any previous) PDCCH (or the DCI within the same PDCCH) can be ignored if a final PDCCH (or the DCI within the PDCCH) terminating the lease is lost. In some examples, separate final PDCCHs (or the DCI within the same PDCCH) can be passed on to different properties of a concession.
[00108] In some examples, to reduce the overhead of the PDCCH, a second DCI / PDCCH that modifies a first DCI / PDCCH may not include any non-modifiable information (for example, any information that cannot be changed from the first to the second DCI / PDCCH). In other examples, the second DCI / PDCCH can define the non-modifiable information to the same as the first DCI / PDCCH. If non-modifiable information is established to be the same as the first DCI / PDCCH on the PDCCH transmitter, and the PDCCH receiver on the programmed entity determines that that information is not the same on the first and second DCI / PDCCH, the programmed entity may ignore the first and second DCI / PDCCHs.
[00109] In some examples, the second DCI / PDCCH may include a pointer to the first DCI / PDCCH. For example, the pointer can be an explicit pointer to the first DCI / PDCCH (for example, a pointer to the DCI / PDCCH transmitted in the control feature set #i on partition N). As another example, the pointer can be an implicit pointer carried by the frequency and time resources (for example, the control feature set #) carrying the second DCI / PDCCH.
Petition 870190106063, of 10/21/2019, p. 57/145
53/94
[00110] In some examples, after programming the initial concession, the resource allocation and the 741 programming circuit system may determine that the channel between the programming entity 7 00 and the programmed entity can support one or more MIMO layers additional (for example, based on an updated CQI or SRS received from the programmed entity) or may determine that an additional urgent package (for example, an Ultra Trusted Low Latency Communication (URLLC) package may need to be transmitted to the entity programmed and can therefore generate concession modification information for the additional package. For example, the 741 resource assignment and programming circuit system can be configured to generate a first control signal (for example, control information downlink (DCI)) within a physical downlink control channel (PDCCH)) within a first partition that includes a concession for the transmission of a first package within a first set of resource elements (for example, the first set of frequency and time resources) and in one or more MIMO layers of a second partition (which may, in some examples, be the same as first partition). The 741 resource assignment and programming circuit system can be configured to generate a second control signal within the first partition or a subsequent partition (for example, a partition prior to or equal to the second partition) that includes modification information. concession for the transmission of a second packet within a second set of resource elements and in one or more layers
Petition 870190106063, of 10/21/2019, p. 58/145
54/94
Additional MIMO within the second partition. In some examples, the first and second sets of resource elements are the same.
[00111] For example, a first PDCCH transmitted in partition nl can program a PDSCH (or PUSCH) in partition nl + kOl, where kOl represents a delay or displacement of partition nl. In addition, a second PDCCH transmitted on partition n2 may include the grant modification information that programs an additional PDSCH (or PUSCH) on partition n2 + k02, where k02 represents a delay or displacement of partition n2. It should be noted that kOl and k02 can represent delays in terms of partitions, mini-partitions or other suitable time units, such as chip duration or sample duration of a waveform. When nl + kOl = n2 + k02 and each PDCCH grant the same block (s) of resources in different MIMO spatial layers, this results in two PDSCHs (or two PUSCHs) being programmed simultaneously in the same frequency and time resources.
[00112] Additionally, the 741 programming and resource assignment circuit system can assign the same modulation and coding scheme (MCS) to each of the packages or can assign a different MCS to the second package (for example, based on an index Updated MCS received from the scheduled entity). If the same MCS is used, the MCS may not be included in the DCI for the second package. In this example, the programmed entity will infer the MCS for the second MCS package included in the initial lease for the first package. In some examples, the non-wired network may not allow the MCS
Petition 870190106063, of 10/21/2019, p. 59/145
55/94 switch between the first and second packages. In this example, if the lease modification information includes a different MCS, the programmed entity can ignore the lease modification information.
[00113] The 741 programming and resource allocation circuitry can additionally program the same HARQ process ID for both packages or different HARQ process IDs for the packages. In some examples, the different HARQ process IDs can be used for each of the packages when the initial modification and grant information is transmitted within the different PDCCH. In other examples, the different HARQ process IDs can be used for each of the packages when the 741 programming and resource assignment circuit system programs different frequency and time resources in the same partition for each of the packages. The number of HARQ process IDs is configurable and can be determined, for example, based on the type of duplexing (for example, TDD or FDD), the subframe or partition structure and other factors. Each HARQ process ID identifies a parallel stop and wait (SAW) process running on the programming entity and the programmed entity.
[00114] The system of programming and resource allocation circuits 741 can additionally reserve frequency and time resources for the transmission of recognition information (for example, ACK or NACK) for each of the packets. In some examples, the 741 resource assignment and programming circuit system may use a block ACK, in which the
Petition 870190106063, of 10/21/2019, p. 60/145
56/94 frequency and time are automatically reserved for a maximum number of packages that a programmed entity can receive simultaneously (for example, in the same frequency and time resources), which can be based, for example, on the maximum supported rating by a scheduled entity. For example, the maximum rating can be four or eight.
[00115] If the 741 programming and resource assignment circuit system uses a block ACK and the spatially transmitted packets have the same HARQ process ID, The 741 programming and resource assignment circuit system may not program the resources Additional ACK for each new packet that is transmitted simultaneously to an entity programmed in different MIMO streams. However, when different HARQ process IDs are used for each of the packages, the 741 resource assignment and programming circuit system can program separate subfields for each HARQ process ID within an ACK block.
[00116] For packets with the same HARQ process ID, if there are fewer reserved ACK bits than spatially transmitted packets, the 741 programming and resource assignment circuitry can use an ACK grouping scheme in which a single ACK bit is used for more than one packet. Thus, if one of the packets is not received correctly at the programmed entity (or the programming entity for PUSCH transmissions), the programmed entity (or the programming entity) transmits a NACK in the ACK bit. ACK grouping works well when all packages are programmed in the same DCI
Petition 870190106063, of 10/21/2019, p. 61/145
57/94 (for example, after successful DCI decoding, the programmed entity is aware of the number of packets to be recognized). However, when grouping several DCIs, as in various aspects of the present disclosure, an ACK may also include the number of packets received or the programmed entity may be informed of the number of packets associated with the ACK grouping for PDSCH grants. In some examples, one or more DCIs may include the total number of packages to be recognized in the ACK cluster.
[00117] In some examples, each packet may have a different retransmission sequence number (RSN) / redundancy version (RV). The RSN indicates the number of times that the same packet was retransmitted, while the RV indicates the specific configuration of systematic and parity bits used in the retransmission. So, for example, one of the packages can be a new package, while the other package can be a retransmission of a package that has NACK. In some instances, the retransmitted packet may use the same beam direction as the new packet.
[00118] In some examples, if the first and second packages are new packages, the concession modification information can modify the initial concession to allocate additional resources to accommodate a single larger package containing the first and second new packages. In this example, each of the first and second new packets can use the same HARQ process ID and the same RSN / RV for retransmitting them. In other examples, each of the first and second packages can be recognized separately, as described above.
Petition 870190106063, of 10/21/2019, p. 62/145
58/94
[00119] In some examples, the 741 resource assignment and programming circuit system may determine that a low-latency packet (for example, a URLLC packet) of control and / or user data traffic to it or to a different programmed entity may need to puncture the initial concession. In this example, the programming and resource allocation circuit system 741 can transmit a second PDCCH including the grant modification information that modifies the initial grant. For example, the second PDCCH can modify the start and / or end of the lease (for example, the initial OFDM symbol and / or the final OFDM symbol) or the transmission bandwidth (for example, the number of resource blocks ) to accommodate the punching. In some instances, the MCS may not be changed and the transport block size calculation may automatically adapt to the revised number of resource elements (REs) in the concession.
[00120] In some examples, the second PDCCH can be transmitted in a partition subsequent to the partition containing the package to indicate the specific processing to be applied to the package as a result of the punching. In this example, the RB allocation of the package is not changed, but the programmed entity is provided with the puncture information that indicates the punctured resources and any special processing to be used for the punctured package.
[00121] In some examples, the second PDCCH can carry the DCI, including an anticipation indicator that indicates specific resource elements
Petition 870190106063, of 10/21/2019, p. 63/145
59/94 (REs) that were punctured for a DL award or a UL award. In examples where REs for the various UEs have been punctured, the DCI of the anticipation indicator can be multicast (ie sent to two or more UEs) and each UE can be configured to extract punching information relevant to that UE . In some examples, the second PDCCH may contain the DCI, including a partition format indicator (SEI) that indicates whether each of the OFDM symbols within a partition is a DL symbol, a UL symbol, or a flexible symbol that can be used for DL or UL. In this example, the SEI can modify one or more flexible OFDM symbols within a partition to be DL symbols or UL symbols, which can have the effect of canceling an earlier semi-statically scheduled transmission (or puncturing the semi-statically scheduled transmission) statically) on these symbols. In some instances, the second PDCCH may indicate that an additional UL concession has been scheduled
on resources in frequency and time UL overlapping associated with a broadcast in UL scheduled previously in control and / or data programmed for a
UE, and the UE may use the predetermined disposal rules to determine that the overlapping UL concession programmed later will puncture at least part of the previously scheduled UL concession for the UE. The programming and resource assignment circuit system 741 can additionally operate in coordination with the resource assignment and programming software 751.
[00122] The 704 processor can additionally
Petition 870190106063, of 10/21/2019, p. 64/145
60/94 include the 742 control and downlink traffic channel and transmission circuit generation system, configured to generate and transmit downlink user data traffic and control channels within one or more subframes , partitions and / or mini-partitions. The DL 742 traffic and control channel generation and transmission circuitry system can operate in coordination with the 741 programming and resource assignment circuitry system to place the DL user data traffic and / or the control information in a time division duplex (TDD) or frequency division duplex (FDD) carrier, as it includes DL user data traffic and / or control information in one or more subframes, partitions and / or mini-partitions, according to the resources allocated for the data traffic of the DL user and / or for the control information.
[00123] For example, the DL 742 transmission and traffic channel generation and control circuit system can be configured to operate in coordination with the 741 programming and resource assignment circuit system to generate a physical channel of downlink control (PDCCH) (or enhanced PDCCH (ePDCCH)) including downlink control (DCI) information. In some examples, one or more of the PDCCHs may include lease modification information that modifies a previous lease submitted on a previous PDCCH, a simultaneous PDCCH or on the same PDCCH. The DL 742 traffic and control channel generation and transmission circuit system can additionally be configured to generate a shared physical downlink channel (PDSCH) (or enhanced PDSCH)
Petition 870190106063, of 10/21/2019, p. 65/145
61/94 (ePDSCH)) including downlink user data traffic. The DL 742 traffic and control channel transmission and generation circuit system can additionally operate in coordination with the DL 752 traffic and control channel transmission and generation software.
[00124] 0 processor 704 can additionally include the system of circuits in processing and reception channel control and in UL 743 traffic,
configured to receive and process uplink control channels and uplink traffic channels from one or more programmed entities. For example, the UL 743 control and traffic channel processing and receiving circuitry system can be configured to receive uplink user data traffic from one or more programmed entities. In addition, the UL 743 control and traffic channel processing and receiving circuitry system can operate in coordination with the 741 resource assignment and programming circuitry to schedule UL user data traffic transmissions. , DL data traffic transmissions and / or DL data traffic retransmissions according to the UCI received. The UL 743 control and traffic channel processing and receiving circuit system can additionally operate in coordination with UL 753 traffic and control channel processing and reception software.
[00125] FIG. 8 is a conceptual diagram illustrating an example of hardware implementation for an illustrative programmed entity 800 employing a system
Petition 870190106063, of 10/21/2019, p. 66/145
62/94 processing 814. According to the various aspects of the disclosure, an element or any part of an element or any combination of elements can be implemented with an 814 processing system that includes one or more 804 processors. programmed entity 800 can be a user equipment (UE) as illustrated in any one or more of FIGs. 1 and 2.
[00126] Processing system 814 can be substantially the same as processing system 714 illustrated in FIG. 7, including a bus interface 808, a bus 802, a memory 805, a processor 804 and a computer-readable medium 806. In addition, programmed entity 800 may include a user interface 812 and a transceiver 810 substantially similar to that described above in FIG. 7. That is, processor 804, as used in a programmed entity 800, can be used to implement any one or more of the processes described below.
[00127] In some aspects of the disclosure, the 804 processor may include the uplink (UL) 841 control and traffic channel transmission and generation circuitry system, configured to generate and transmit control / feedback / acknowledgment information uplink on an UL control channel (for example, a PUCCH) or UL traffic channel (for example, a PUSCH) according to an uplink lease. The UL 841 traffic and control channel generation and transmission circuit system can additionally be configured to generate and transmit uplink user data traffic on an UL traffic channel (for example, a PUSCH). THE
Petition 870190106063, of 10/21/2019, p. 67/145
63/94 UL 841 traffic and control channel generation and transmission circuit system can operate in coordination with UL 851 traffic and control channel generation and control software.
[00128] Processor 804 may additionally include the system of processing and receiving circuits of control channel and downlink traffic (DL) 842, configured to receive and process downlink user data traffic in a traffic channel and to receive and process control information on one or more downlink control channels. For example, the DL 842 traffic and control channel processing and receiving circuitry system can be configured to receive leases for downlink transmissions or uplink transmissions within the downlink control information (DCI) of a PDCCH.
[00129] In various aspects of the present disclosure, the DL 842 control and traffic channel processing and receiving circuitry system can be configured to receive a concession within a PDCCH and the concession modification information by modifying the concession within a subsequent PDCCH received in a subsequent partition, a simultaneous PDCCH received in the same partition or the same PDCCH. For example, grant modification information may indicate that additional resources have been reserved to transmit one or more additional packets (for example, a different set of frequency and time resources or a different set of MIMO layers in the same partition), allocation of frequency resources and concession time
Petition 870190106063, of 10/21/2019, p. 68/145
64/94 has been modified, the waveform used for the concession has been modified, the transmission diversity scheme used for the concession has been modified or the specific processing to be used for the package.
[00130] In some examples, the concession modification information indicates that the additional packet (s) can be transmitted or received simultaneously on different frequency and time resources or on different MIMO layers of the same frequency and time resources within the same partition. The grant modification information may additionally indicate the MCS to be used for the additional package (s), the HARQ process ID to be used for the additional package (s), the resources allocated for recognition of the additional package (s), the RSV / RV assigned to the additional package (s) and other pertinent information. The DL 842 control and traffic channel processing and reception circuit system can operate in coordination with the DL 852 traffic and control channel processing and reception software.
[00131] FIG. 9 illustrates an example of scheduling a concession for at least one packet transmitted within a partition, using several control channels, according to some aspects of the present disclosure. In the example shown in FIG. 9, three partitions 902a, 902b and 902c are illustrated, each including a respective control region 904a, 904b and 904c and a respective traffic region 906a, 906b, 906c. Each of partitions 902a, 902b and 902c can be, for example, a DL-centered partition or a partition
Petition 870190106063, of 10/21/2019, p. 69/145
65/94 centered on UL. Thus, in some examples, control regions 904a, 904b and 904c may correspond to a burst of DL 402 from a partition centered on DL 400 shown in FIG. 4 or a burst of DL 502 from a UL 500 centered partition shown in FIG. 5. Traffic regions 906a, 906b and 906c can correspond, for example, to a DL 404 traffic region of a DL 400-centered partition shown in FIG. 4 or a UL 504 traffic region from a UL-centered partition shown in FIG. 5. Additionally, although not shown, it should be understood that a burst of UL corresponding, for example, to the burst of UL 406 or 506 shown in FIG. 4 or 5 can additionally be included at the end of traffic regions 906a, 906b and 906c.
[00132] A first control channel (PDCCH) 908a carrying the first downlink control information (DCI) 910a including a lease (for example, a downlink assignment or an uplink lease) to a UE (programmed entity) is presented transmitted in the control region 904a of the first partition 902a. The lease indicates that the frequency and time resources within the traffic region 906c of the third partition 902c have been allocated for the transmission of a 912 packet (for example, a PDSCH or PUSCH lease). A second control channel 908b carrying the second DCI 910b including the grant modification information (GMI) is presented transmitted in the control region 904b of the second partition 902b. GMI indicates changes made to one or more of the concession properties transmitted in the first DCI 910a. For example, GMI may indicate that
Petition 870190106063, of 10/21/2019, p. 70/145
66/94 additional resources have been reserved to transmit one or more additional packets (not shown) within the third partition 902c, a frequency and time resource allocation for packet 912 on the third partition 902c has been modified, the waveform used to packet 912 has been modified, the transmission diversity scheme used for packet 912 has been modified or the specific processing to be used for packet 912.
[00133] FIG. 10 illustrates another example of scheduling a concession for at least one packet transmitted within a partition, using several control channels, according to some aspects of the present disclosure. In the example shown in FIG. 10, two partitions 902a and 902b are illustrated, each including a respective control region 904a and 904b and a respective traffic region 906a and 906b.
[00134] A first control channel (PDCCH) 908a carrying the first downlink control information (DCI) 910a including a lease (for example, a downlink assignment or an uplink lease) to a UE (programmed entity) is presented transmitted in the control region 904a of the first partition 902a. The lease indicates the frequency and time resources within traffic region 906b of the second partition 902b that have been allocated for the transmission of a 912 packet (for example, a PDSCH or PUSCH lease). A second control channel 908b carrying the second DCI 910b including the grant modification information (GMI) is presented transmitted in the control region 904b of the
Petition 870190106063, of 10/21/2019, p. 71/145
67/94 second partition 902b. GMI indicates changes made to one or more of the concession properties transmitted in the first DCI 910a.
[00135] FIG. 11 illustrates another example of scheduling a concession for at least one packet transmitted within a partition, using several control channels, according to some aspects of the present disclosure. In the example shown in FIG. 11, two partitions 902a and 902b are illustrated, each including a respective control region 904a and 904b and a respective traffic region 906a and 906b.
[00136] A first control channel (PDCCH) 908a carrying the first downlink control information (DCI) 910a including a lease (for example, a downlink assignment or an uplink lease) to a UE (programmed entity) is presented transmitted in the control region 904a of the first partition 902a. The lease indicates the frequency and time resources within traffic region 906b of the second partition 902b that have been allocated for the transmission of a 912 packet (for example, a PDSCH or PUSCH lease). A second control channel 908b carrying the second DCI 910b including the grant modification information (GMI) is also shown in control region 904a of the first partition 902a. GMI indicates modifications made to one or more of the concession properties transmitted in the first DCI 910a.
[00137] In this example, the second PDCCH 908b can be transmitted in one or more subsequent OFDM symbols in control region 904a or in partition 902a. For example, the first PDCCH 908a can be
Petition 870190106063, of 10/21/2019, p. 72/145
68/94 transmitted in a first OFDM symbol of partition 902a, while the second PDCCH 908b can be transmitted in a second or other subsequent OFDM symbol of partition 902a.
[00138] FIG. 12 illustrates another example of scheduling a concession for at least one packet transmitted within a partition, using several control channels, according to some aspects of the present disclosure. In the example shown in FIG. 12, two partitions 902a and 902b are illustrated, each including a respective control region 904a and 904b and a respective traffic region 906a and 906b.
[00139] A first control channel (PDCCH) 908a carrying the first downlink control information (DCI) 910a including a lease (for example, a downlink assignment or an uplink lease) to a UE (programmed entity) is presented transmitted in the control region 904a of the first partition 902a. The lease indicates the frequency and time resources within traffic region 906a of the first partition 902a that have been allocated for the transmission of a 912 packet (for example, a PDSCH or PUSCH lease).
[00140] In the example shown in FIG. 12, a portion of packet 912 has been punctured to accommodate low latency traffic (for example, URLLC traffic) 1100. Therefore, a second control channel 908b carrying the second DCI 910b including concession modification information (GMI) can be transmitted in the control region 904b of the second partition 902b after the transmission of packet 912 in the first partition 902a. GMI may include puncture information indicating the punctured resources and
Petition 870190106063, of 10/21/2019, p. 73/145
69/94 any special processing to be used for the punctured package.
[00141] Although not presented, it should be understood that in other examples, the GMI can be transmitted before the transmission of the packet. In this case, GMI may modify the start and / or end of the concession (for example, the initial OFDM symbol and / or the final OFDM symbol) or the transmission bandwidth (for example, the number of resource blocks) to accommodate the punching. In some instances, the MCS may not be changed and the transport block size calculation may automatically adapt to the revised number of resource elements (REs) in the concession.
[00142] FIG. 13 illustrates another example of scheduling a concession for at least one package within a single control channel using various control information in accordance with some aspects of the present disclosure. In the example shown in FIG. 13, a single control channel (PDCCH) 908 includes several DCIs 910a, 910b, 910N, called DCI-1, DCI-2, ... DCI-N. Each DCI 910a, 910b, ... 910N may contain a separate grant for the programmed entity (for example, a dynamic grant, a semi-persistently scheduled grant and / or other types of grants) and / or one or more DCI 910a, 910b,. . . 910N may include the grant modification information (GMI) that modifies a previous grant.
[00143] In the example shown in FIG. 13, DCI-1 910a includes a concession 1302, and DCI-N 910N includes GMI 1304 which modifies concession 1302 included in DCI-1 910a. GMI 1304 can modify one or more properties
Petition 870190106063, of 10/21/2019, p. 74/145
70/94 of concession 1302, such as the number of packages associated with concession 1302, the frequency and time resources allocated for concession 1302, the waveform used for concession 1302, the transmission diversity scheme used for concession 1302, or the specific processing to be used for concession 1302. In some instances, instead of modifying concession 1302 included in DCI-1 910a, GMI 1304 can modify another concession included in the same PDCCH 908 or in another PDCCH .
[00144] FIG. 14 illustrates an example of programming several packets for transmission in a partition using different MIMO layers according to some aspects of the disclosure. In the example shown in FIG. 14, a portion of a bandwidth is spatially illustrated through several MIMO layers. For simplicity, only three MIMO layers 1402a, 1402b and 1402c are shown in FIG. 14. The portion of the illustrated bandwidth may correspond, for example, to a portion of the system's bandwidth used by a radio access network (for example, a base station to communicate with one or more UEs) or to a portion of the device's bandwidth used by a given UE (which may be less than the total available system bandwidth). In some examples, the illustrated bandwidth portion may correspond to a portion of the 304 resource grid shown in FIG. 3. In the example shown in FIG. 14, the illustrated bandwidth portion includes three resource blocks (RBs) 308a, 308b and 308c, each including twelve respective resource elements (REs) 306
Petition 870190106063, of 10/21/2019, p. 75/145
71/94 in the frequency and time domain.
[00145] In some examples, each MIMO layer 1402a, 1402b and 1402c can be associated with a respective transmitting antenna at the transmitter and can be used to transmit a spatially pre-coded stream (for example, a packet or part of a packet spatially) pre-coded) via the respective transmitting antenna to a receiver. In the example shown in FIG. 14, a first packet, called Pack 1, can be transmitted in a first MIMO 1402a layer to a programmed entity (UE), while a second packet, called Pack 2, can be transmitted in a second MIMO 1402b layer to the same UE. In addition, each packet can receive the same frequency and time resources in the system or device bandwidth. In the example shown in FIG. 14, each packet can receive the same RB 308c.
[00146] FIG. 15 illustrates another example of programming multiple packets for transmission in a partition using different MIMO layers according to some aspects of the disclosure. In some instances, a high-rate packet can be divided into several lower-rate streams, each transmitted from a different antenna (on a different MIMO layer). In the example shown in FIG. 15, the first packet (Packet 1) can be divided into two streams and transmitted in the same frequency and time resources (for example, RB 308c) in a set of two layers MIMO 1402a and 1402b. Additionally, the second packet (Packet 2) can be transmitted in a third layer MIMO 1402c in the same or
Petition 870190106063, of 10/21/2019, p. 76/145
72/94 in different frequency and time resources. In the example shown in FIG. 15, the second packet is transmitted on a different RB (RB 308b) than the first packet.
[00147] FIG. 16 illustrates an example of downlink control information, including a concession that has modifiable concession properties in accordance with some aspects of the present disclosure. The concession is illustrated as being transmitted within DCI 910 of a PDCCH 908. DCI 910 may include, for example, several of concession properties 1602 of the concession, together with a modifiable indication 1604 for each of the concession properties 1602. Each modifiable indication 1604 can include, for example, one or more bits that can inform the programmed entity that property 1602 can be further modified (Y) in a simultaneous or subsequent PDCCH (or DCI within the same PDCCH), cannot be modified (N) (for example, not modifiable) in a simultaneous or subsequent PDCCH (or
DCI no same PDCCH] 1 or will not be more modified (Final) on a PDCCH simultaneous or subscribe hot (or the DCI the same PDCCH) In some examples, one Final PDCCH (or the DCI in same PDCCH) for one set of elements in resources inside partition can include the indicator End when
the PDCCH (or the DCI in the same PDCCH) is a final PDCCH.
[00148] In some examples, to reduce the overhead of the PDCCH, a second DCI / PDCCH that modifies a first DCI / PDCCH may not include any non-modifiable information (for example, any information that cannot be changed from the first to the second DCI / PDCCH).
Petition 870190106063, of 10/21/2019, p. 77/145
73/94
In other examples, the second DCI / PDCCH can define information that cannot be modified to the same information as the first DCI / PDCCH. If the non-modifiable information is defined as the same DCI / PDCCH on the PDCCH transmitter, and the PDCCH receiver on the programmed entity determines that that information is not the same on the first and second DCI / PDCCH, the programmed entity can ignore the first and the second DCI / PDCCHs.
[00149] FIG. 17 is a flowchart illustrating an illustrative process 1700 for programming a concession using the various control signals in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated may be omitted in a specific implementation within the scope of the present disclosure, and some features illustrated may not be necessary for the implementation of all embodiments. In some examples, process 1700 can be performed by the programming entity 700 illustrated in FIG. 7. In some examples, the 1700 process can be performed by any suitable device or medium to perform the functions or algorithms described below.
[00150] In block 1702, the programming entity can program a concession for a package for a programmed entity. For example, the programming and resource allocation circuit system 741 shown and described with reference to FIG. 7 above you can schedule the lease for the package. In block 1704, the programming entity can transmit a first control channel (for example, a PDCCH) including the first control information (for example, the DCI) that includes the
Petition 870190106063, of 10/21/2019, p. 78/145
74/94 concession for the package to the programmed entity. For example, the resource allocation and programming circuit system 741, the DL 742 traffic and control channel generation and transmission circuit system and transceiver 710 shown and described with reference to FIG. 7 above can generate and transmit the first control channel to the programmed entity.
[00151] In block 1706, the programming entity can modify at least one concession property to produce the concession modification information. For example, the programming entity may add a package to the concession for transmission in different frequency and time resources or a different set of one or more MIMO layers, modify a concession's RB allocation, modify the waveform used for the concession or modify the transmission diversity scheme used for the concession. For example, programming and resource allocation circuit system 741 shown and described with reference to FIG. 7 above can modify at least one concession property.
[00152] In block 1708, the programming entity can transmit a second control channel (for example, PDCCH) including the second control information (for example, DCI) that includes at least the grant modification information for the programmed entity . In some examples, the second control information (DCI) can be transmitted within the same PDCCH as the first control information. In some examples, the first and second control channels can be
Petition 870190106063, of 10/21/2019, p. 79/145
75/94 transmitted separately within the same partition or on different partitions. In some examples, the second control information may also include the concession's unmodified properties. For example, the resource allocation and programming circuit system 741, the DL 742 traffic and control channel generation and transmission circuit system and transceiver 710 shown and described with reference to FIG. 7 above can transmit the second control channel to the programmed entity.
[00153] FIG. 18 is a flow chart illustrating an illustrative process 1800 for scheduling a concession using various control signals in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated may be omitted in a specific implementation within the scope of the present disclosure, and some features illustrated may not be necessary for the implementation of all embodiments. In some examples, process 1800 can be performed by the programming entity 700 illustrated in FIG. 7. In some examples, the 1800 process can be performed by any device or suitable means to perform the functions or algorithms described below.
[00154] In block 1802, the programming entity can program a concession for a first package for a programmed entity. For example, the programming and resource allocation circuit system 741 shown and described with reference to FIG. 7 above you can schedule the lease for the first package. In block 1804, the programming entity can transmit a
Petition 870190106063, of 10/21/2019, p. 80/145 first control channel (for example, a PDCCH) including the first control information (for example, the DCI) that includes the granting of the first package to the programmed entity. For example, the programming and resource assignment circuit system 741, the DL 742 traffic and control channel generation and transmission circuit system and transceiver 710 shown and described with reference to FIG. 7 above can generate and transmit the first control channel to the programmed entity.
[00155] In block 1806, the programming entity can determine whether at least part of the first package will be punctured. In some instances, the first packet may be punctured to support the transmission of a second packet containing low latency traffic to the same scheduled entity or to another scheduled entity (for example, to accommodate a URLLC packet for the same or a scheduled entity different). In other examples, the second packet may contain other types of DL or UL control and / or user data traffic. For example, programming and resource allocation circuit system 741 shown and described with reference to FIG. 7 above can determine whether the package will be punctured.
[00156] If at least part of the first package will be punctured (S branch of block 1806), in block 1808, the programming entity may modify the concession to produce the concession modification information indicating at least the punctured resources of the concession. In some examples, the modification information for the
Petition 870190106063, of 10/21/2019, p. 81/145
77/94 concession may include information about the punctured resources indicating the resource elements (REs) allocated to the concession that need to be punctured to support the transmission of the second package. In some instances, the grant modification information may additionally include the processing to be applied to the first package as a result of the punching. For example, any special processing can be included in the concession modification information transmitted after the transmission of the first packet. For example, the programming and resource allocation circuit system 741 shown and described with reference to FIG. 7 above can modify the lease.
[00157] In the programming block you can determine if transmitted. For example, the programming and assignment described in reference to FIG. 7
1810, the entity of the first packet was already featured resource circuit system 741 and above can determine whether the first packet was transmitted. If the packet was transmitted (block S of block 1810), in block 1812, the programming entity can transmit a second control channel (for example, the PDCCH) including the second control information (for example, the DCI) including at least less the grant modification information for the entity programmed into a partition that occurs later in time than the partition that contains the first package. If the first packet was not additionally transmitted (block N of block 1810), in block 1814, the programming entity can transmit a second control channel (for example, the PDCCH) including
Petition 870190106063, of 10/21/2019, p. 82/145
78/94 the second control information (for example, the DCI) that includes at least the grant modification information for the entity programmed in a previous partition or equal to the partition containing the first package. For example, the resource allocation and programming circuit system 741, the DL 742 traffic and control channel transmission and generation circuit system and transceiver 710 shown and described above with reference to FIG. 7 can transmit the second control channel to the programmed entity.
[00158] FIG. 19 is a flow chart illustrating an illustrative process 1900 for programming a concession using various control signals in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated may be omitted in a specific implementation within the scope of the present disclosure, and some features illustrated may not be necessary for the implementation of all embodiments. In some examples, process 1900 may be performed by the programming entity 700 illustrated in FIG. 7. In some examples, the 1900 process can be performed by any device or suitable means to execute the functions or algorithms described below.
[00159] In block 1902, the programming entity can program a concession for a first package for a programmed entity. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above you can schedule the lease for the package. In block 1904, the programming entity can transmit a first channel
Petition 870190106063, of 10/21/2019, p. 83/145
79/94 control (for example, a PDCCH) including the first control information (for example, the DCI) that includes the granting of the first package to the programmed entity. For example, the resource programming and assignment circuit system 741, DL 742 traffic and control channel generation and transmission circuit system and transceiver 710 shown and described with reference to FIG. 7 above can generate and transmit the first control channel to the programmed entity.
[00160] In block 1906, the programming entity can determine whether to add a second package to the concession. In some examples, the programming entity may determine that the channel between the programming entity and the programmed entity may support one or more additional MIMO layers (for example, based on an updated CQI or SRS received from the programmed entity) or may determine that an additional urgent package (for example, an Ultra Trusted Low Latency Communication (URLLC) package) may need to be transmitted to the scheduled entity and therefore may determine that the second package must be added to the concession. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above can determine whether a second package should be added to the concession.
[00161] If the programming entity determines that a second package should be added to the concession (S branch of block 1906), in block 1908, the programming entity may modify the concession to produce the concession modification information indicating at least
Petition 870190106063, of 10/21/2019, p. 84/145
80/94 resources (for example, frequency and time resources) allocated to the second package. For example, the first package can be programmed into a first set of resource elements and the second package can be programmed into a second set of resource elements. In some examples, the first and second sets of resource elements are the same or at least partially overlapping (for example, the packages are programmed in the same set or in the overlapping sets of resource elements). In other examples, the first and second sets of resource elements are different. In examples in which packages are programmed in the same (or overlapping) sets of resource elements, each package can be programmed in a different set of one or more MIMO layers. For example, the first package can be programmed into a first set of one or more MIMO layers and the second package can be programmed into a second set of one or more MIMO layers, where each set of MIMO layers is different (without overlapping).
For example, the system in circuits programming and resource assignment 741 introduced and described in reference to FIG. 7 above can modify the concession.[00162] No block 1910, the entity in
The programming may transmit a second control channel (for example, PDCCH), including the second control information (for example, the DCI) that includes at least the concession modification information for the programmed entity. In some examples, the second control information (DCI) can be transmitted within the same PDCCH as the first control information. In some examples,
Petition 870190106063, of 10/21/2019, p. 85/145
81/94 the first and second control channels can be transmitted separately within the same partition or on different partitions. In some examples, the second control information may also include the concession's unmodified properties. For example, the resource allocation and programming circuit system 741, the DL 742 traffic and control channel transmission and generation circuit system and transceiver 710 shown and described with reference to FIG. 7 above can transmit the second control channel to the programmed entity.
[00163] FIG. 20 is a flow chart illustrating an illustrative process 2000 for programming a concession using various control signals in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated may be omitted in a specific implementation within the scope of the present disclosure, and some features illustrated may not be necessary for the implementation of all embodiments. In some examples, process 2000 can be performed by the programming entity 700 illustrated in FIG. 7. In some examples, the 2000 process can be performed by any device or suitable means to perform the functions or algorithms described below.
[00164] In block 2002, the programming entity can program a concession for a first package for a programmed entity. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above you can schedule the lease for the package. In block 2004, the
Petition 870190106063, of 10/21/2019, p. 86/145
The programming entity may transmit a first control channel (for example, a PDCCH) including the first control information (for example, the DCI) which includes the granting of the first package to the programmed entity.
For example, the system in circuits programming and allocation of resource 741, The system of circuits in transmission and generation of channel traffic and of control in DL 742 and the transceiver 710 presented and : described in reference to FIG. 7 above can generate and to transmit The first channel control for the programmed entity.[00165] No block 2006, the entity in
programming can determine whether to add a second package to the concession. In some examples, the programming entity may determine that the channel between the programming entity and the programmed entity may support one or more additional MIMO layers (for example, based on an updated CQI or SRS received from the programmed entity) or may determine that an additional urgent package (for example, an Ultra Trusted Low Latency Communication (URLLC) package) may need to be transmitted to the scheduled entity and therefore may determine that the second package must be added to the concession. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can determine whether a second package should be added to the lease.
[00166] If the programming entity determines that a second package should be added to the concession (block S of block 2006), in block 2008, the programming entity can determine whether to transmit the second
Petition 870190106063, of 10/21/2019, p. 87/145
83/94 package on the same resources (for example, frequency and time resources) as the first package. For example, the scheduling entity can determine whether the channel between the scheduling entity and the scheduled entity can support one or more additional MIMO layers in the same (or overlapping) sets of resource elements to transmit the second packet. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can determine whether to use the same resources for the first and second packages.
[00167] If the programming entity determines which different resources should be used for the first and second packages (branch N of block 2008), in block 2010, the programming entity can modify the concession to produce information for modifying the concession indicating at least the different resources (for example, frequency and time resources) allocated to the second package. For example, the first package can be programmed into a first set of resource elements and the second package can be programmed into a second set of resource elements other than the first set of resource elements. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can modify the lease.
[00168] If the programming entity determines that the same resources (or overlapping) should be used for the first and second packets, where each packet is transmitted in a different set of one or more
Petition 870190106063, of 10/21/2019, p. 88/145
84/94 more MIMO layers (S branch of block 2008), in block 2012, the programming entity can determine whether the second packet should receive the same HARQ process ID as the first packet. In some examples, the different HARQ process IDs can be used for each of the packages when the initial lease and lease modification information is transmitted within the different PDCCH. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can determine whether the same HARQ process ID should be used for both packages.
[00169] If the programming entity determines that the same HARQ process ID must be assigned for each package (block S of block 2012), in block 2014, the programming entity can modify the concession to produce the concession modification information indicating at least that the same resources (for example, frequency and time resources) are allocated to the second package as for the first package in a different set of one or more MIMO layers and that the same package is allocated to the second package HARQ process ID. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can modify the lease.
[00170] If the programming entity determines that different HARQ process IDs must be assigned to each package (block N of block 2012), in block 2016, the programming entity can modify the concession to produce the concession modification information indicating
Petition 870190106063, of 10/21/2019, p. 89/145
85/94 at least that the same resources (for example, frequency and time resources) are allocated to the second package as for the first package in a different set of one or more MIMO layers and which is assigned to the second package a different HARQ process ID. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can modify the lease.
[00171] In block 2018, the programming entity can transmit a second control channel, (for example, the PDCCH), including the second control information (for example, the DCI) that includes at least the concession modification information for the scheduled entity. In some examples, the second control information (DCI) can be transmitted within the same PDCCH as the first control information. In some examples, the first and second control channels can be transmitted separately within the same partition or on different partitions. In some examples, the second control information may also include the concession's unmodified properties. For example, the resource allocation and programming circuit system 741, the DL 742 traffic and control channel transmission and generation circuit system and transceiver 710 shown and described with reference to FIG. 7 above, they can transmit the second control channel to the programmed entity.
[00172] FIG. 21 is a flow chart illustrating an illustrative 2100 process for programming a concession using various control signals according to some
Petition 870190106063, of 10/21/2019, p. 90/145
86/94 aspects of the present disclosure. As described below, some or all of the features illustrated may be omitted in a specific implementation within the scope of the present disclosure, and some features illustrated may not be necessary for the implementation of all embodiments. In some examples, process 2100 can be performed by the programming entity 700 illustrated in FIG. 7. In some examples, the 2100 process can be performed by any device or medium suitable for performing the functions or algorithms described below.
[00173] In block 2102, the programming entity can program a concession for a first package for a programmed entity. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can schedule the lease for the package. In block 2104, the programming entity can transmit a first control channel (for example, a PDCCH) including the first control information (for example, the DCI) that includes the granting of the first packet to the programmed entity.
For example, the system in circuits programming and resource assignment 741, The system of circuits in transmission and generation of channel . traffic and of control in DL 742 and the transceiver 710 presented and described in reference to FIG. 7 ac magnet, can generate and to transmit The
first control channel for the programmed entity.
[00174] In block 2106, the programming entity can determine whether to add a second package to the concession. In some instances, the programming entity may determine that the channel between the programming entity
Petition 870190106063, of 10/21/2019, p. 91/145
87/94 programming and the programmed entity may support one or more additional MIMO layers (for example, based on an updated CQI or SRS received from the programmed entity) or may determine that an additional urgent package (for example, a Low Communication package Ultra Trusted Latency (URLLC)) may need to be transmitted to the scheduled entity and, therefore, may determine that the second package should be added to the lease. For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can determine whether a second package should be added to the lease.
[00175] If the programming entity determines that a second package should be added to the concession (S branch of block 2106), in block 2108, the programming entity can modify the concession to produce the concession modification information indicating at least the resources (for example, frequency and time resources) allocated to the second package. For example, the first package can be programmed into a first set of resource elements and the second package can be programmed into a second set of resource elements. In some examples, the first and second sets of resource elements are the same or at least partially overlapping (for example, packages are programmed in the same set or in overlapping sets of resource elements). In other examples, the first and second sets of resource elements are different. In examples where packages are programmed into the same (or overlapping) sets of resource elements, each
Petition 870190106063, of 10/21/2019, p. 92/145
88/94 package can be programmed in a different set of one or more MIMO layers. For example, the first package can be programmed into a first set of one or more MIMO layers and the second package can be programmed into a second set of one or more MIMO layers, where each set of MIMO layers is different (not overlapping). For example, the system programming and resource allocation circuit 741 shown and described with reference to FIG. 7 above, you can modify the lease.
[00176] In block 2110, the programming entity may additionally program the resources for a grouped recognition for the first and second concessions to produce a grouped recognition grant. For example, the 741 resource assignment and programming circuit system can schedule the granting of grouped recognition.
[00177] In block 2110, the programming entity may transmit a second control channel (for example, the PDCCH), including the second control information (for example, the DCI), which includes at least the concession modification information and the granting of grouped recognition for the programmed entity. In some examples, the second control information (DCI) can be transmitted within the same PDCCH as the first control information. In some examples, the first and second control channels can be transmitted separately within the same partition or on different partitions. In some examples, the second control information may also include the concession's unmodified properties. In some instances, granting
Petition 870190106063, of 10/21/2019, p. 93/145
89/94 grouped recognition can additionally indicate the number of packages associated with the granting of grouped recognition. For example, the resource allocation and programming circuit system 741, the DL 742 control and traffic channel generation and transmission circuit system and transceiver 710 shown and described with reference to FIG. 7 above, they can transmit the second control channel to the programmed entity.
[00178] In block 2114, the programming entity can determine whether the grant of grouped recognition has indicated the number of packages associated with the grouped recognition. If the number of packets has been included in the grouped recognition grant (S branch of block 2114), after the transmission of the first and second packets, in block 2116, the programming entity can receive a grouped recognition (ACK / NACK) from of the programmed entity that collectively recognizes both the first and second packages. For example, the UL 743 traffic and control channel processing and receiving circuitry system and transceiver 710 shown and described with reference to FIG. 7 above, can receive grouped recognition from the programmed entity.
[00179] If the number of packets has not been included in the grouped recognition concession (branch N of block 2114), after the transmission of the first and second packets, in block 2118, the programming entity can receive a grouped recognition (ACK / NACK) from the programmed entity that additionally includes an indication
Petition 870190106063, of 10/21/2019, p. 94/145
90/94 of the number of packets received at the programmed entity. For example, the UL 743 traffic and control channel processing and receiving circuitry system and transceiver 710 shown and described with reference to FIG. 7 above, can receive grouped recognition from the programmed entity.
[00180] In a configuration, a scheduling entity in an unwired communication network includes a means to schedule a lease including a downlink assignment or an uplink lease for a first package for a first scheduled entity in a set of one or more entities programmed in the non-wired communication with the programming entity and the means to transmit a first control channel, including the first control information to the first programmed entity, where the first control information includes the concession for the first package. The method further includes a means to modify at least one property of the various concession properties to produce the concession modification information and a means to transmit a second control channel, including the second control information to the first programmed entity, where the second information control system includes at least the concession modification information.
[00181] In one aspect, the aforementioned means for scheduling the lease and the means for modifying at least one property of the lease may be the processor (processors) 704 shown in FIG. 7 and configured to perform the functions mentioned by the means mentioned above. For example, the aforementioned means for programming
Petition 870190106063, of 10/21/2019, p. 95/145
91/94 the concession and the means for modifying the concession may include the system programming and resource allocation circuit 741 shown in FIG. 7. In another aspect, the means mentioned above for transmitting the first control channel and the means for transmitting the second control channel can be the processor 704 shown in FIG. 7 configured to perform the functions mentioned by the means mentioned above. For example, the aforementioned means for transmitting the first control channel and the means for transmitting the second control channel may include the DL 742 transmission and traffic channel generation and control circuit system shown in FIG. 7, in conjunction with transceiver 710 shown in FIG. 7. In yet another aspect, the medium mentioned above can be a circuit or any device configured to perform the functions mentioned by the medium mentioned above.
[00182] Several aspects of an unwired communication network were presented with reference to an illustrative implementation. As those skilled in the art will readily appreciate, several aspects described throughout this disclosure can be extended to other telecommunication systems, network architectures and communication standards.
[00183] As an example, several aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), the Evolved Package System (EPS), the Universal Mobile Telecommunication System (UMTS) and / or the Global System for Furniture (GSM). Several aspects can also be
Petition 870190106063, of 10/21/2019, p. 96/145
92/94 extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Optimized Data in Evolution (EV-DO). Other examples can be implemented in systems using IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wide Band (UWB), Bluetooth and / or other suitable systems. The current telecommunication standard, the network architecture and / or the communication standard employed will depend on the specific application and the general design restrictions imposed on the system.
[00184] Within the present revelation, the word illustrative is used to mean serving as an example, instance or illustration. Any implementation or aspect described in this document as illustrative should not necessarily be interpreted as preferred or advantageous over other aspects of the disclosure. Likewise, the term aspects does not require that all aspects of the disclosure include the feature, advantage or mode of operation discussed. The term coupled is used in this document to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B and object B touches object C, then objects A and C can still be considered to be coupled together - even if they do not touch each other directly physically. For example, a first object can be coupled with a second object, even though the first object is never directly in physical contact with the second object. The terms circuit and circuit system are widely used and intended to include hardware implementations of
Petition 870190106063, of 10/21/2019, p. 97/145
93/94 electrical devices and conductors that, when connected and configured, allow the performance of the functions described in this disclosure, without limitation as to the type of electronic circuits, as well as the software implementations of information and instructions that, when executed by a processor , allow the performance of the functions described in the present disclosure.
[00185] One or more of the components, steps, characteristics and / or functions illustrated in FIGs. 1 through 21 can be reorganized and / or combined into a single component, step, feature or function, or incorporated into several components, steps or functions. Additional elements, components, steps and / or functions can also be added without diverging from the new features revealed in this document. The apparatus, devices and / or components illustrated in FIGS. 1, 2, 6, 7 and / or 8 can be configured to perform one or more of the methods, features or steps described in this document. The new algorithms described in this document can also be efficiently implemented in software and / or incorporated into hardware.
[00186] It must be understood that the specific order or hierarchy of steps in the revealed methods is an illustration of the illustrative processes. Based on the project's preferences, it is understood that the specific order or hierarchy of steps in the methods can be reorganized. Accompanying method claims present elements of the various steps in a sample order and are not to be limited to the order or the
Petition 870190106063, of 10/21/2019, p. 98/145
94/94 specific hierarchy presented, unless specifically mentioned in this document.

权利要求:
Claims (70)
[1]
1. Method for a programming entity to program transmissions with a set of one or more program entities on an unwired communication network, the method comprising:
schedule a lease comprising a downlink assignment or a uplink lease for a first package for a first programmed entity in the set of one or more programmed entities;
transmitting a first control channel comprising first control information to the first programmed entity, where the first control information comprises the concession for the first packet;
modify at least one property of several of the concession properties to produce the concession modification information; and transmitting a second control channel comprising second control information to the first programmed entity, wherein the second control information comprises at least the first concession modification information and is separated from the first control information.
[2]
2. Method according to claim 1, wherein the concession modification information comprises an indication that at least a part of the first package will be punctured.
[3]
A method according to claim 2, wherein modifying at least one property of the various properties of the concession to produce the concession modification information further comprises:
Petition 870190106063, of 10/21/2019, p. 100/145
2/21 identify a second packet comprising ultra-reliable low-latency communication traffic (URLLC) for transmission:
identify at least a part of the resource elements (REs) allocated to the first packet which are necessary to support the transmission of the second packet to produce the punctured resource information; and generate the concession modification information comprising the punctured resource information.
[4]
A method according to claim 1, wherein:
transmitting the first control channel comprising the first control information to the first programmed entity additionally comprises:
transmitting the first control channel comprising the first control information to the first programmed entity within a first partition; and transmitting the second control channel comprising the second control information to the first programmed entity additionally comprises:
transmitting the second control channel comprising the second control information to the first programmed entity within a second partition.
[5]
5. Method according to claim 4, wherein the first partition is the same as the second partition:
[6]
A method according to claim 4, further comprising:
transmit the first packet to the first
Petition 870190106063, of 10/21/2019, p. 101/145
3/21 entity programmed into a third partition, where the second partition occurs later in time than the third partition.
[7]
A method according to claim 1, wherein modifying at least one property of the various properties of the concession additionally comprises:
add a second package to the lease, where the first package is programmed into a first set of resource elements within a partition and the second package is programmed into a second set of resource elements within the partition.
[8]
A method according to claim 7, wherein the first packet is programmed into a first set of one or more layers of several inputs and several outputs (MIMO) and the second packet is programmed into a second set of one or more more MIMO layers.
[9]
A method according to claim 8, wherein the first set of resource elements comprises at least part of the second set of resource elements.
[10]
A method according to claim 9, further comprising:
assign a first hybrid automatic repeat request (HARQ) process identifier (HARQ) to the first packet; and assigning a second HARQ process ID to the second package.
[11]
A method according to claim 10, wherein the first HARQ process ID and the second HARQ process ID are the same.
Petition 870190106063, of 10/21/2019, p. 102/145
4/21
[12]
12. The method of claim 7, further comprising:
programming the resources for a block recognition comprising a respective recognition bit for each of the first packet and the second packet to produce a block recognition grant; and transmitting the block recognition concession to the first programmed entity within the first control channel.
[13]
A method according to claim 7, further comprising:
programming the resources for a grouped recognition comprising a single recognition bit for the first packet and the second packet to produce a grouped recognition grant; and transmitting the grant of grouped recognition to the first programmed entity within at least one of the first control channel and the second control channel.
[14]
14. The method of claim 13, wherein the grant of grouped recognition additionally comprises an indication of a number of packages associated with the grant of grouped recognition.
[15]
A method according to claim 13, further comprising:
transmitting the first packet and the second packet to the first programmed entity;
receive grouped recognition information using the grouped recognition grant from the first programmed entity; and
Petition 870190106063, of 10/21/2019, p. 103/145
5/21 receive an indication of a number of packages associated with the grouped recognition information from the first programmed entity.
[16]
16. The method of claim 7, wherein adding the second package to the concession additionally comprises:
select a first coding and modulation scheme (MCS) for the first package; and selecting a second MCS for the second package, where the second MCS is different from the first MCS.
[17]
17. The method of claim 7, wherein adding the second package to the concession additionally comprises:
identifying a first retransmission sequence number of the first packet and a second retransmission sequence number of the second packet, wherein the first retransmission sequence number is different from the second retransmission sequence number.
[18]
18. The method of claim 1, wherein modifying at least one property of the various properties of the concession to produce the concession modification information further comprises:
modify at least one of the concession's frequency and time resource allocation, a waveform used for the concession or a transmission diversity scheme used for the concession to produce the concession modification information.
[19]
19. Method according to claim 1, wherein the first control information additionally comprises a respective modification indication for
Petition 870190106063, of 10/21/2019, p. 104/145
6/21 each property of the various properties of the concession.
[20]
20. The method of claim 19, wherein the respective indication of modification of each of the various properties indicates whether the respective property is further modifiable.
[21]
21. The method of claim 19, wherein the respective modification indication for each of the various properties is defined as final when the respective property is no longer modifiable.
[22]
22. Programming entity in a non-wired communication network, comprising:
a transceiver for non-wired communication with a set of one or more programmed entities;
a memory; and a processor connected communicatively with the transceiver and with the memory, the processor configured for:
schedule a lease comprising a downlink assignment or a uplink lease for a first packet for a first programmed entity from a set of one or more entities programmed in non-wired communication with the programming entity;
transmitting a first control channel comprising the first control information to the first programmed entity via the transceiver, where the first control information comprises the concession for the first packet;
modify at least one property of several concession properties to produce the concession modification information; and
Petition 870190106063, of 10/21/2019, p. 105/145
7/21 transmitting a second control channel comprising the second control information to the first programmed entity via the transceiver, wherein the second control information comprises at least the grant modification information and is separate from the first control information.
[23]
23. Programming entity, according to claim 22, in which the concession modification information comprises an indication that at least part of the first package will be punctured.
[24]
24. Programming entity according to claim 23, in which the processor is additionally configured to:
identify a second packet comprising ultra-reliable low-latency communication traffic (URLLC) for transmission;
identify at least part of the resource elements (REs) allocated to the first packet which are necessary to support the transmission of the second packet to produce the punctured resource information; and generate the concession modification information comprising the punctured resource information.
[25]
25. Programming entity according to claim 22, wherein the processor is additionally configured to:
transmitting the first control channel comprising the first control information to the first programmed entity within a first partition; and transmit the second control channel
Petition 870190106063, of 10/21/2019, p. 106/145
8/21
understanding the second information from control to the first ent programmed age within in an Monday partition. 26. Programming entity, in wake up with the claim 25, where the first partition is the same as
the second partition.
27. Entity programming, in according to claim 25, where the processor is additionally
configured for:
transmitting the first packet to the first programmed entity within a third partition, where the second partition occurs later than the third partition.
[26]
28. Programming entity according to claim 22, in which the processor is additionally configured to:
add a second package to the lease, where the first package is programmed into a first set of resource elements within a partition and the second package is programmed into a second set of resource elements within the partition.
[27]
29. Programming entity according to claim 28, in which the first package is programmed in a first set of one or more layers of several inputs and several outputs (MIMO) and the second package is programmed in a second set of one or more MIMO layers.
[28]
30. Programming entity according to claim 29, wherein the first set of resource elements comprises at least part of the second set
Petition 870190106063, of 10/21/2019, p. 107/145
9/21 elements of appeal.
[29]
31. Programming entity according to claim 30, in which the processor is additionally configured to:
assign a first hybrid automatic repeat request (HARQ) process identifier (HARQ) to the first packet; and assigning a second HARQ process ID to the second package.
[30]
32. Programming entity according to claim 31, wherein the first HARQ process ID and the second HARQ process ID are the same.
[31]
33. Programming entity according to claim 28, wherein the processor is additionally configured to:
programming the resources for a block recognition comprising a respective recognition bit for each of the first packet and the second packet to produce a block recognition grant; and transmitting the block recognition concession to the first programmed entity within the first control channel.
[32]
34. Programming entity according to claim 28, wherein the processor is additionally configured to:
programming the resources for a grouped recognition comprising a single recognition bit for the first packet and the second packet to produce a grouped recognition grant; and transmit the grant of recognition of
Petition 870190106063, of 10/21/2019, p. 108/145
10/21 grouped for the first programmed entity in at least one of the first control channel and the second control channel.
[33]
35. Programming entity according to claim 34, wherein the grant of grouped recognition additionally includes an indication of a number of packages associated with the grant of grouped recognition.
[34]
36. Programming entity according to claim 34, in which the processor is additionally configured to:
transmitting the first packet and the second packet to the first programmed entity via the transceiver;
receiving the grouped recognition information using the grouped recognition grant from the first programmed entity via the transceiver; and receiving an indication of a number of packets associated with the grouped recognition information from the first entity programmed via the transceiver.
[35]
37. Programming entity according to claim 28, wherein the processor is additionally configured to:
select a first coding and modulation scheme (MCS) for the first package; and selecting a second MCS for the second package, where the second MCS is different from the first MCS.
[36]
38. Programming entity according to claim 28, wherein the processor is additionally configured to:
identify a first sequence number
Petition 870190106063, of 10/21/2019, p. 109/145
11/21 retransmission of the first packet and a second retransmission sequence number of the second packet, wherein the first retransmission sequence number is different from the second retransmission sequence number.
[37]
39. Programming entity according to claim 22, wherein the processor is additionally configured to:
modify at least one of the frequency and time allocation resources of the concession, a waveform used for the concession or a transmission diversity scheme used for the concession to produce the concession modification information.
[38]
40. Programming entity, according to claim 22, in which the first control information additionally comprises a respective modification indication for each property of the various properties of the concession.
41. Entity in programming, a deal with The claim 4 0 in what the respective recommendation in modification of each one of various properties indicates whether : a respective property it is additionally modifiable. 42. Entity in programming, a deal with The claim 4 0 in what the respective recommendation in modification of each one 1 of multiple properties is defined as final when respective ownership is no longer modifiable. 43. Entity in programming in a network in
non-wired communication, comprising:
means to schedule a lease comprising a downlink assignment or a uplink lease for
Petition 870190106063, of 10/21/2019, p. 110/145
12/21 a first package for a first programmed entity from a set of one or more entities programmed in non-wired communication with the programming entity;
means for transmitting a first control channel comprising the first control information to the first programmed entity, wherein the first control information comprises the concession for the first packet;
means for modifying at least one property of the various concession properties to produce the concession modification information; and means for transmitting a second control channel comprising the second control information to the first programmed entity, wherein the second control information comprises at least the concession modification information and is separate from the first control information.
[39]
44. Programming entity according to claim 43, in which the concession modification information comprises an indication that at least part of the first package will be punctured.
[40]
45. Programming entity according to claim 44, wherein the means for modifying at least one property of the various properties of the concession to produce the concession modification information additionally comprises:
means for identifying a second packet comprising ultra-reliable low-latency communication traffic (URLLC) for transmission;
means to identify at least part of the
Petition 870190106063, of 10/21/2019, p. 111/145
13/21 resource elements (REs) allocated to the first packet that are needed to support the transmission of the second packet to produce the punctured resource information; and means for generating concession modification information comprising punctured resource information.
[41]
46. Programming entity, according to claim 43, in which:
the means for transmitting the first control channel comprising the first control information to the first programmed entity additionally comprises:
means for transmitting the first control channel comprising the first control information for the first programmed entity within a first partition; and the means for transmitting the second control channel comprising the second control information to the first programmed entity additionally comprises:
means for transmitting the second control channel comprising the second control information to the first programmed entity within a second partition.
[42]
47. Programming entity according to claim 46, wherein the first partition is the same as the second partition.
[43]
48. Programming entity according to claim 46, further comprising:
means to transmit the first packet to the first programmed entity within a third
Petition 870190106063, of 10/21/2019, p. 112/145
14/21 partition, where the second partition occurs later in time than the third partition.
[44]
49. Programming entity according to claim 43, wherein the means for modifying at least one property of the various properties of the concession additionally comprises:
means for adding a second package to the lease, where the first package is programmed into a first set of resource elements within a partition and the second package is programmed into a second set of resource elements within the partition.
[45]
50. Programming entity according to claim 49, in which the first package is programmed in a first set of one or more layers of several inputs and several outputs (MIMO) and the second package is programmed in a second set of one or more MIMO layers.
[46]
51. Programming entity according to claim 50, wherein the first set of resource elements comprises at least part of the second set of resource elements.
[47]
52. Programming entity according to claim 51, further comprising:
middle for assign a first identifier process (ID) in automatic retry request hybrid (HARQ) for the first package; andmiddle for assign a second ID HARQ process
for the second package.
[48]
53. Programming entity according to claim 52, wherein the first HARQ process ID and the
Petition 870190106063, of 10/21/2019, p. 113/145
15/21 according to HARQ process ID are the same.
[49]
54. Programming entity according to claim 49, further comprising:
means for programming the resources for a grouped recognition comprising a single recognition bit for the first packet and the second packet for producing a grouped recognition grant; and means for transmitting the grant of grouped recognition to the first programmed entity within at least one of the first control channel and the second control channel.
[50]
55. Programming entity, according to claim 49, wherein the grant of grouped recognition additionally includes an indication of a number of packages associated with the grant of grouped recognition.
[51]
56. Programming entity according to claim 54, further comprising:
means for transmitting the first packet and the second packet to the first programmed entity;
means for receiving grouped recognition information using the grouped recognition grant from the first programmed entity; and means for receiving an indication of a number of packets associated with the grouped recognition information from the first programmed entity.
[52]
57. Programming entity according to claim 49, wherein the means for adding the second package to the concession additionally comprises:
means to select a first scheme of
Petition 870190106063, of 10/21/2019, p. 114/145
16/21 coding and modulation (MCS) for the first package; and a half to select a second MCS for the second pack, where the second MCS is different from the first MCS.
[53]
58. The programming entity according to claim 49, wherein the means for adding the second package to the concession additionally comprises:
means for identifying a first retransmission sequence number of the first packet and a second retransmission sequence number of the second packet, wherein the first retransmission sequence number is different from the second retransmission sequence number.
[54]
59. The programming entity according to claim 43, wherein the means for modifying at least one property of the various properties of the concession to produce the concession modification information additionally comprises:
modify at least one of the frequency and time allocation resources of the concession, a waveform used for the concession or a transmission diversity scheme used for the concession to produce the concession modification information.
[55]
60. Computer readable non-temporary medium, storing computer executable code, comprising code to make a programming entity on an unwired communication network:
schedule a lease comprising a downlink assignment or a uplink lease for a first package for a first programmed entity in a set of one or more entities programmed in
Petition 870190106063, of 10/21/2019, p. 115/145
17/21 non-wired communication with the programming entity;
transmit a first control channel comprising the first control information to the first programmed entity, where the first control information comprises the concession for the first packet;
modify at least one property of the various properties of the concession to produce the concession modification information; and transmitting a second control channel comprising the second control information to the first programmed entity, wherein the second control information comprises at least the concession modification information and is separated from the first control information.
[56]
61. Computer-readable non-temporary medium according to claim 60, wherein the concession modification information comprises an indication that at least part of the first package will be punctured.
[57]
62. Computer-readable non-temporary medium according to claim 61, further comprising the code to make the programming entity:
identify a second packet comprising ultra reliable low latency communication traffic (URLLC) for transmission;
identify at least part of the resource elements (REs) allocated to the first packet that are needed to support the transmission of the second packet to produce the punctured resource information; and generate the grant modification information
Petition 870190106063, of 10/21/2019, p. 116/145
18/21 including information on punctured resources.
[58]
63. Computer-readable non-temporary medium according to claim 60, further comprising the code to make the programming entity:
transmit the first control channel comprising the first control information to the first programmed entity within a first partition; and transmitting the second control channel comprising the second control information to the first programmed entity within a second partition.
[59]
64. Computer-readable non-temporary medium according to claim 63, wherein the first partition is the same as the second partition.
[60]
65. Computer-readable non-temporary medium according to claim 63, additionally comprising the code to make the programming entity:
transmit the first packet to the first programmed entity within a third partition, where the second partition occurs later than the third
partition. by computer, 66. Half not readable temporary according with the claim 60, additionally understanding the code to make the entity of programming:
add a second package to the concession, where the first package is scheduled in a first set
Petition 870190106063, of 10/21/2019, p. 117/145
19/21 resource elements within a partition and the second package It is programmed into a second set of resource elements within the partition.
[61]
67. Computer readable non-temporary medium according to claim 66, wherein the first packet is programmed into a first set of one or more layers of several inputs and several outputs (MIMO) and the second packet is programmed into a second set of one or more MIMO layers.
[62]
68. Computer-readable non-temporary medium according to claim 67, wherein the first set of resource elements comprises at least part of the second set of resource elements.
[63]
69. Computer-readable non-temporary medium according to claim 68, further comprising the code to make the programming entity:
assign a first hybrid auto-repeat request process identifier (HARQ) to the first packet; and assigning a second HARQ process ID to the second package.
[64]
70. Computer readable non-temporary medium according to claim 69, wherein the first HARQ process ID and the second HARQ process ID are the same.
[65]
71. Computer readable, non-temporary medium according to claim 66, further comprising the code to make the programming entity:
Petition 870190106063, of 10/21/2019, p. 118/145
20/21 program resources for cluster recognition comprising a single recognition bit for the first packet and the second packet to produce a cluster recognition grant; and transmit the grant of grouped recognition to the first programmed entity in at least one of the first control channel and the second control channel.
[66]
72. Computer readable non-temporary medium according to claim 71, wherein the grant of grouped recognition additionally includes an indication of a number of packages associated with granting of grouped recognition.
[67]
73. Computer readable non-temporary medium according to claim 71, further comprising the code to make the programming entity:
transmit the first packet and the second packet to the first programmed entity via the transceiver;
receive grouped recognition information using the grouped recognition grant from the first programmed entity via the transceiver; and receive an indication of a number of packets associated with the grouped recognition information from the first entity programmed via the transceiver.
[68]
74. Computer-readable non-temporary medium according to claim 66, further comprising the code to make the programming entity:
select a first modulation and coding scheme (MCS) for the first package; and
Petition 870190106063, of 10/21/2019, p. 119/145
21/21 select a second MCS for the second pack, where the second MCS is different from the first MCS.
[69]
75. Computer-readable non-temporary medium according to claim 66, further comprising the code to make the programming entity:
identify a first retransmission sequence number of the first packet and a second retransmission sequence number of the second packet, where the first retransmission sequence number is different from the second retransmission sequence number.
[70]
76. Computer readable non-temporary medium according to claim 60, further comprising the code to make the programming entity:
modify at least one of the frequency and time allocation resources of the concession, a waveform used for the concession or a transmission diversity scheme used for the concession to produce the concession modification information.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019022028A2|2020-05-12|FLEXIBLE PROGRAMMING IN NOVA RADIO NETWORKS |

---

KR102258539B1|2021-05-28|Downlink Control Information Piggyback in Physical Downlink Shared Channel

---

JP2020533890A|2020-11-19|Uplink acknowledgment mapping and resource allocation

---

BR112019021354A2|2020-05-05|sync signal block designs for wireless communication

---

US10742234B2|2020-08-11|Code block group definition configuration for wireless communication

---

BR112020004707A2|2020-09-08|system and method for selecting resources to transmit beam failure recovery request

---

BR112019025634A2|2020-06-23|STRATEGIC MAPPING OF UPLINK RESOURCES

---

US10972937B2|2021-04-06|Group indicator for code block group based retransmission in wireless communication

---

BR112019022292A2|2020-05-19|port group and port subset indication in a csi-rs resource for new radio |

---

BR112020000198A2|2020-07-07|uplink hop pattern modes for hybrid auto-repeat request | transmissions

---

BR112019022026A2|2020-05-12|TRANSMISSION OF UPLINK CONTROL INFORMATION |

---

BR112019025530A2|2020-06-23|TRANSMISSION OF UPLINK CONTROL INFORMATION ON THE NEW RADIO

---

BR112020010044A2|2020-11-03|mapping of uplink control information to uplink data channel in wireless communication

---

WO2019210193A1|2019-10-31|Mapping a physical downlink control channel | across multiple transmission configuration indication | states

---

BR112019015528A2|2020-03-17|PROJECTS OF VARIOUS GRAPHICS LOW DENSITY PARITY CHECK BASE

---

BR112020009678A2|2020-11-10|methods and devices for determining transport block size in wireless communication

---

TWI740007B|2021-09-21|Hybrid automatic repeat request buffer configuration

---

US10952196B2|2021-03-16|DMRS indication for transmissions scheduled by fallback DCI in NR

---

US10925041B2|2021-02-16|Common indexing for uplink physical resource blocks

---

BR112019026574A2|2020-06-23|DYNAMIC FILLING FIELD TO CORRELATE THE LENGTH OF CONTROL INFORMATION UPLINK DOWNLINK

---

BR112019009409A2|2019-07-30|cyclic prefix management on new radio

---

US11284432B2|2022-03-22|Flexible scheduling in new radio | networks

---

US11277860B2|2022-03-15|Rate-matching behavior for overlapping resource block | sets

---

US20190349977A1|2019-11-14|Rate-matching behavior for overlapping resource block | sets

---

US10849110B2|2020-11-24|Resource allocation for the physical uplink control channel

同族专利:

---

公开号 | 公开日

---

SG11201908258QA|2019-11-28|

---

CN110547019A|2019-12-06|

---

JP2020518167A|2020-06-18|

---

US20200146050A1|2020-05-07|

---

KR20190140025A|2019-12-18|

---

US10548165B2|2020-01-28|

---

US20180310333A1|2018-10-25|

---

TW201844048A|2018-12-16|

---

WO2018200748A1|2018-11-01|

---

EP3616451A1|2020-03-04|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

KR101146866B1|2007-11-13|2012-05-16|삼성전자주식회사|System and method to allocate resource in a communication system|

---

EP2472762A2|2009-10-20|2012-07-04|LG Electronics Inc.|Method for allocating fixed resource in broadband wireless communication system|

---

US9872304B1|2013-11-21|2018-01-16|Sprint Communications Company L.P.|Packet fragmentation for VoLTE communication sessions|

---

US11019620B2|2014-05-19|2021-05-25|Qualcomm Incorporated|Apparatus and method for inter-band pairing of carriers for time division duplex transmit- and receive-switching and its application to multiplexing of different transmission time intervals|

---

US20150334729A1|2014-05-19|2015-11-19|Qualcomm Incorporated|Apparatus and method for interference mitigation utilizing thin control|

---

US10779283B2|2016-05-31|2020-09-15|Nokia Technologies Oy|Physical resource sharing on wireless interface|

---

US10433326B2|2016-06-13|2019-10-01|Qualcomm Incorporated|Techniques for communicating in a discontinuous receive mode|US10139820B2|2016-12-07|2018-11-27|At&T Intellectual Property I, L.P.|Method and apparatus for deploying equipment of a communication system|

---

US10588148B2|2017-08-10|2020-03-10|At&T Intellectual Property I, L.P.|Configurable groups of control channel resource sets for wireless communication|

---

ES2882594T3|2018-03-28|2021-12-02|Asustek Comp Inc|Method and apparatus for the determination of the interval format in a wireless communication system|

---

GB2572429A|2018-03-29|2019-10-02|Tcl Communication Ltd|Resource allocation|

---

US20190387502A1|2018-06-15|2019-12-19|At&T Intellectual Property I, L.P.|Single user super position transmission for future generation wireless communication systems|

---

US11140668B2|2018-06-22|2021-10-05|At&T Intellectual Property I, L.P.|Performance of 5G MIMO|

---

CN111148260A|2018-11-02|2020-05-12|华为技术有限公司|Method for transmitting and receiving data and communication device|

---

US11133909B2|2018-11-30|2021-09-28|T-Mobile Usa, Inc.|Scheduling HARQ transmissions in mini-slots based on fading conditions|

---

US11233620B2|2018-11-30|2022-01-25|T-Mobile Usa, Inc.|Scheduling HARQ transmissions in mini-slots|

---

US10790939B2|2018-11-30|2020-09-29|T-Mobile Usa, Inc.|Selecting mini-slots according to conditions|

---

CN113519138A|2019-02-13|2021-10-19|Idac控股公司|Physical uplink shared channel transmission|

---

US10945281B2|2019-02-15|2021-03-09|At&T Intellectual Property I, L.P.|Facilitating improved performance of multiple downlink control channels in advanced networks|

---

CN111800802B|2019-08-23|2022-02-11|维沃移动通信有限公司|Parameter modification method and equipment|

---

CN111031513B|2019-12-02|2020-12-15|北京邮电大学|Multi-unmanned-aerial-vehicle-assisted Internet-of-things communication method and system|

---

WO2021141363A1|2020-01-06|2021-07-15|삼성전자 주식회사|Method and apparatus for modifying pdu session and always-on pdu session in wireless communication system|

---

WO2021186400A1|2020-03-18|2021-09-23|Telefonaktiebolaget Lm Ericsson |Multi-dci based pdsch scheduling for urllc|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762489981P| true| 2017-04-25|2017-04-25|

---

US62/489,981|2017-04-25|

---

US15/961,446|2018-04-24|

---

US15/961,446|US10548165B2|2017-04-25|2018-04-24|Flexible scheduling in new radionetworks|

---

PCT/US2018/029470|WO2018200748A1|2017-04-25|2018-04-25|Flexible scheduling in new radionetworks|

---