num="00003">

Available resource = 150 * 14* 12 * 6 = 151200

in which, as corrupted by PDCCH data, gNodeB = 6 * 6 ~ 32

resource blocks (using equal split of the total used of 64 RBs for UE0 and

UE1); or = 32 * 12 * 6 = 2,304 bits, resulting in

151,200 − 2,304 = 148,896 or total bits transmitted = 148,896 * 0.8027 =

119, 518 bits. Similarly, UE1 = 79,062 bits.

One or more aspects can be embodied in network equipment, such as represented in the example operations of FIG. 6, and for example can include a memory that stores computer executable components and/or operations, and a processor that executes computer executable components and/or operations stored in the memory. Example operations can include operation 602, which represents overwriting physical downlink shared channel data, scheduled within a defined control resource set within slot data, with physical downlink control channel information specific to a user equipment, resulting in punctured physical downlink shared channel data. Example operation 604 represents transmitting the slot data to the user equipment, in which the user equipment is configured to locate the physical downlink control channel information specific to the user equipment within the defined control resource set of the slot data, and recover the punctured scheduled physical downlink shared channel data as part of a user equipment decoding operation.

The defined downlink control information control resource set can include an entire symbol of the slot data.

The defined downlink control information control resource set can be within a first symbol of the slot data, (or the first few symbols), for example.

Further operations can include, prior to the overwriting of the defined control resource set, scheduling the physical downlink control channel information within the defined symbol of the slot data.

Overwriting the physical downlink shared channel data can be performed by a gNodeB.

Overwriting the defined control resource set can include overwriting a first subgroup of a larger group of locations in the defined control resource set, and not overwriting a second subgroup, of the larger group of locations in a defined symbol, which can include a portion of the punctured scheduled physical downlink shared channel data.

Further operations can include determining a coding rate that is able to be used to increase a likelihood that the user equipment receives sufficient data according to a defined sufficiency criterion, and wherein the coding rate corresponds to the transmitting of the slot data, to recover the punctured scheduled physical downlink shared channel data.

Further operations can include determining a repetition pattern associated with the transmitting of the slot data that is able to be used to increase a likelihood that the user equipment receives sufficient data according to a defined sufficiency criterion, and wherein the repetition pattern corresponds to the transmitting of the slot, to recover the punctured scheduled physical downlink shared channel data.

The user equipment can be a first user equipment, wherein the overwriting of the physical downlink shared channel data can include overwriting with first physical downlink control channel information for the first user equipment and overwriting with second physical downlink control channel information for a second user equipment, and transmitting the slot data can include transmitting the slot data to the first user equipment and to the second user equipment.

One or more example aspects, such as corresponding to example operations of a method, are represented in FIG. 7. Example operation 702 represents scheduling, by a system comprising a processor, physical downlink shared channel data within a slot, comprising mapping the physical downlink shared channel data for a user equipment to symbol locations within the slot, the symbol locations comprising a specified control resource set symbol location reserved for physical downlink control channel information. Example operation 704 represents overwriting, by the system, the physical downlink shared channel data within the specified control resource set location, with physical downlink control channel data, resulting in physical downlink shared channel data punctured with physical downlink control channel data that maps the user equipment to the symbol locations within the slot. Example operation 706 represents transmitting, by the system, the slot to the user equipment with a redundancy pattern via which the user equipment is able to recover the physical downlink shared channel data that was punctured with the physical downlink control channel data.

Overwriting the specified control resource set can include overwriting a first subgroup of a larger group of locations in the predefined control resource set, and not overwriting a second subgroup, of the larger group of locations in a specified symbol, that can include a portion of the scheduled physical downlink shared channel data.

Further operations can include determining, by the system, a coding rate corresponding to the redundancy pattern.

Further operations can include determining, by the system, a repetition pattern corresponding to the redundancy pattern.

Overwriting the physical downlink shared channel data within the specified control resource set location can be performed by gNodeB equipment.

The user equipment can be a first user equipment, the scheduling can include scheduling of first physical downlink shared channel data within the slot, the overwriting can include overwriting the first the physical downlink shared channel data with first physical downlink control channel data, and further operations can include scheduling, by the system, second physical downlink shared channel data within the slot, comprising mapping the second physical downlink shared channel data for a second user equipment to second symbol locations within the slot, the second symbol locations comprising the specified control resource set symbol location reserved for physical downlink control channel information, and overwriting, by the system, the second physical downlink shared channel data with second physical downlink control channel data, resulting in second physical downlink shared channel data punctured with second physical downlink control channel data that maps the second user equipment to the second symbol locations within the slot; transmitting the slot can include transmitting the slot to the first user equipment and to the second user equipment, with the redundancy pattern via which the first user equipment is able to recover the first physical downlink shared channel data that was punctured with the first physical downlink control channel data, and via which the second user equipment is able to recover the second physical downlink shared channel data that was punctured with the second physical downlink control channel data.

FIG. 9 summarizes various example operations, e.g., corresponding to a machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations. Example operation 802 represents overwriting first physical downlink shared channel data, scheduled within a predefined symbol within a slot, with first physical downlink control channel information, resulting in first punctured physical downlink shared channel data. Example operation 804 represents overwriting second physical downlink shared channel data, scheduled within the predefined symbol within a slot, with second physical downlink control channel information, resulting in second punctured physical downlink shared channel data. Example operation 806 represents transmitting the slot to a first user equipment and a second user equipment, wherein the first user equipment is configured to locate the first physical downlink control channel information specific to the first user equipment within the predefined symbol, and recover the first punctured scheduled physical downlink shared channel data, and wherein the second user equipment is configured to locate the second physical downlink control channel information specific to the second user equipment within the predefined symbol, and recover the second punctured scheduled physical downlink shared channel data.

Further operations can include determining a coding rate usable to increase a likelihood that the first user equipment receives sufficient data, corresponding to the transmitting of the slot, to recover the first punctured scheduled physical downlink shared channel data.

Further operations can include determining a repetition pattern associated with the transmitting of the slot usable to increase a likelihood that the first user equipment receives sufficient data, corresponding to the transmitting of the slot, to recover the punctured scheduled physical downlink shared channel data.

Further operations can include, prior to the overwriting of the predefined control resource set, scheduling the first physical downlink control channel information within the predefined symbol of the slot, and scheduling the second physical downlink control channel information within the predefined symbol of the slot.

Overwriting the first physical downlink control channel information can include inserting a first radio network temporary identifier associated with the first user equipment into the first physical downlink control channel information, and inserting a second radio network temporary identifier associated with the second user equipment into the second physical downlink control channel information.

As can be seen, the technology described herein facilitates the scheduling of PDSCH data in a symbol otherwise reserved for PDCCH information. Although the PDCCH overwrites/punctures at least some of the PDSCH locations, and therefore some of the PDSCH data is lost, the needed PDCCH information is present, such that user equipment are able to decode PDCCH normally as in present systems. However, the even though some of the scheduled PDSCH data are corrupted by PDCCH and thus lost, the LDPC decoder on the UE side is able to correct the data for proper decoding. Increasing the coding rate adds more redundancy (aligns the coding rate properly and/or increase repetition is increased such that a UE is able to decode the signal even if there is some data is lost).

FIG. 9 is a schematic block diagram of a computing environment 900 with which the disclosed subject matter can interact. The system 900 comprises one or more remote component(s) 910. The remote component(s) 910 can be hardware and/or software (e.g., threads, processes, computing devices). In some embodiments, remote component(s) 910 can be a distributed computer system, connected to a local automatic scaling component and/or programs that use the resources of a distributed computer system, via communication framework 940. Communication framework 940 can comprise wired network devices, wireless network devices, mobile devices, wearable devices, radio access network devices, gateway devices, femtocell devices, servers, etc.

The system 900 also comprises one or more local component(s) 920. The local component(s) 920 can be hardware and/or software (e.g., threads, processes, computing devices). In some embodiments, local component(s) 920 can comprise an automatic scaling component and/or programs that communicate/use the remote resources 910, etc., connected to a remotely located distributed computing system via communication framework 940.

One possible communication between a remote component(s) 910 and a local component(s) 920 can be in the form of a data packet adapted to be transmitted between two or more computer processes. Another possible communication between a remote component(s) 910 and a local component(s) 920 can be in the form of circuit-switched data adapted to be transmitted between two or more computer processes in radio time slots. The system 900 comprises a communication framework 940 that can be employed to facilitate communications between the remote component(s) 910 and the local component(s) 920, and can comprise an air interface, e.g., Uu interface of a UMTS network, via a long-term evolution (LTE) network, etc. Remote component(s) 910 can be operably connected to one or more remote data store(s) 950, such as a hard drive, solid state drive, SIM card, device memory, etc., that can be employed to store information on the remote component(s) 910 side of communication framework 940. Similarly, local component(s) 920 can be operably connected to one or more local data store(s) 930, that can be employed to store information on the local component(s) 920 side of communication framework 940.

In order to provide additional context for various embodiments described herein, FIG. 10 and the following discussion are intended to provide a brief, general description of a suitable computing environment 1000 in which the various embodiments of the embodiment described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which can include computer-readable storage media, machine-readable storage media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media or machine-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 10, the example environment 1000 for implementing various embodiments of the aspects described herein includes a computer 1002, the computer 1002 including a processing unit 1004, a system memory 1006 and a system bus 1008. The system bus 1008 couples system components including, but not limited to, the system memory 1006 to the processing unit 1004. The processing unit 1004 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit 1004.

The system bus 1008 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1006 includes ROM 1010 and RAM 1012. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 1002, such as during startup. The RAM 1012 can also include a high-speed RAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD) 1014 (e.g., EIDE, SATA), and can include one or more external storage devices 1016 (e.g., a magnetic floppy disk drive (FDD) 1016, a memory stick or flash drive reader, a memory card reader, etc.). While the internal HDD 1014 is illustrated as located within the computer 1002, the internal HDD 1014 can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment 1000, a solid state drive (SSD) could be used in addition to, or in place of, an HDD 1014.

Other internal or external storage can include at least one other storage device 1020 with storage media 1022 (e.g., a solid state storage device, a nonvolatile memory device, and/or an optical disk drive that can read or write from removable media such as a CD-ROM disc, a DVD, a BD, etc.). The external storage 1016 can be facilitated by a network virtual machine. The HDD 1014, external storage device(s) 1016 and storage device (e.g., drive) 1020 can be connected to the system bus 1008 by an HDD interface 1024, an external storage interface 1026 and a drive interface 1028, respectively.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 1002, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to respective types of storage devices, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, whether presently existing or developed in the future, could also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 1012, including an operating system 1030, one or more application programs 1032, other program modules 1034 and program data 1036. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1012. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

Computer 1002 can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system 1030, and the emulated hardware can optionally be different from the hardware illustrated in FIG. 10. In such an embodiment, operating system 1030 can comprise one virtual machine (VM) of multiple VMs hosted at computer 1002. Furthermore, operating system 1030 can provide runtime environments, such as the Java runtime environment or the .NET framework, for applications 1032. Runtime environments are consistent execution environments that allow applications 1032 to run on any operating system that includes the runtime environment. Similarly, operating system 1030 can support containers, and applications 1032 can be in the form of containers, which are lightweight, standalone, executable packages of software that include, e.g., code, runtime, system tools, system libraries and settings for an application.

Further, computer 1002 can be enabled with a security module, such as a trusted processing module (TPM). For instance, with a TPM, boot components hash next in time boot components, and wait for a match of results to secured values, before loading a next boot component. This process can take place at any layer in the code execution stack of computer 1002, e.g., applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any level of code execution.

A user can enter commands and information into the computer 1002 through one or more wired/wireless input devices, e.g., a keyboard 1038, a touch screen 1040, and a pointing device, such as a mouse 1042. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and/or virtual reality headset, a game pad, a stylus pen, an image input device, e.g., camera(s), a gesture sensor input device, a vision movement sensor input device, an emotion or facial detection device, a biometric input device, e.g., fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit