Method and system for improving resource allocation in wireless communication networks - Patents.com

Abstract

The present invention provides an improved physical layer processing method and system for a physical uplink control channel (PDCCH) resource allocation mechanism for high speed wireless communication networks. The method includes estimating PDCCH resources using a default resource configuration, can dynamically calculate operating parameters, can calculate PDCCH candidates using self-generated operating parameters, can configure the system using PDCCH resources to make the system operational, and can use feedback to modify the estimate of PDCCH candidates. Detailed methods for each of the above steps are also disclosed.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to communication networks and, more particularly, to improved resource allocation mechanisms for high speed wireless communication networks. [Background technology]

[0002] The following description of related art is intended to provide background information regarding the field of the present disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, this section should be understood as being used only to enhance the reader's understanding of the present disclosure and not as an admission of prior art.

[0003] Fifth generation (5G) technologies are expected to fundamentally change the role that telecommunications technologies play in industry and society at large. Thus, 5G wireless communication systems are expected to support a wide range of newly emerging applications in addition to the usual cellular mobile broadband services. These applications or services that will be supported can be categorized as enhanced mobile broadband, large-scale deployment of Internet of Things devices, and highly reliable low-latency communications. These services allow users to run video conferencing, television broadcasting, and video-on-demand (simultaneous streaming) applications using the Internet, high-speed browsing, voice calling, gaming, connected car communications, and other different types of multimedia services. To support the above applications and services, the 3GPP specifications provide a network deployment architecture that is summarized in Figure 1.

[0004] To transmit information of the physical layer processing of the physical control channel (PDCCH) and the physical layer processing of the physical shared channel (PDSCH) using CCE in the downlink direction, the prior art uses the bandwidth part (BWP) method. BWP allows a more flexible method of allocating CCE resources on each carrier. BWP allows multiplexing of different information of PDCCH and PDSCH, thus enabling better utilization and adaptation of the operator spectrum and UE battery consumption. The maximum carrier bandwidth of 5G NR is up to 100 MHz in frequency range 1 (FR1: 450 MHz to 6 GHz) or up to 400 MHz in frequency range 2 (FR2: 24.25 GHz to 52.6 GHz), which can be aggregated with a maximum bandwidth of 800 MHz.

[0005] According to another prior art, for gNB systems, there may be multiple candidates defined for each of the aggregation levels. Thus, using multiple candidates per aggregation level, the gNB system calculates the total number of CCE requirements to obtain the number of CCEs per aggregation level. This total number of CCEs is finally used to calculate the control resource set (CORESET). Thus, the CORESET is composed of multiple REGs in the frequency domain and "1 or 2 or 3" OFDM symbols in the time domain. Therefore, each of the BWPs needs to have its own CORESET definition in order to schedule users in that individual BWP. One such example showing the relationship between BWPs, CORESETs, aggregation levels, and CCEs is shown in Figures 2A and 2B, 4A and 4B. Figures 2A and 2B show representative representations of non-overlapping and overlapping BWP schemas, respectively. As can be seen from Figures 2A and 2B, three non-overlapping BWPs (i.e., BWP1, 2, 3) are created, and each of the BWPs has three such CORESETs (i.e., CORESET1, 2, 3). Each of these BWPs and CORESET configurations can be configured in the UE using RRC signaling. The information elements carrying the CORESET and search space configurations are shown in Figure 3. The search space parameters in Figure 3 are further defined with respect to those mentioned in the prior art, such as (a) monitoringSlotPeriodicityAndOffset, (b) nrofCandidates, and (c) searchSpaceType. One of the main entities in the search space design is the nrofCandidates parameter, which defines the number of candidates associated with one particular aggregation level. Depending on the number of candidates per aggregation level, the number of CCEs is also derived accordingly. For example, if there are two candidates for aggregation level 2, the total number of CCEs required for the system will be four. A more detailed level of calculation is shown in Figures 4A and 4B.As can be seen in FIG. 4A, eight candidates for aggregation level 1, four candidates for aggregation level 2, two candidates for aggregation level 4, one candidate for aggregation level 8, and zero candidates for aggregation level 16 are seen. The above explanation is interpreted as the fact that whenever we set the number of candidates per aggregation level, there is a definite amount of CCEs. As mentioned before, from the candidates of the aggregation level, we can determine the number of CCEs that define the final CORESET parameter definition. FIG. 4B is an interleaving pattern of the distribution of CCEs in both frequency and time domains. However, the 3GPP specifications do not provide a mechanism to identify the relevant candidates for each aggregation level based on the service and content for effective radio resource usage in terms of control channel elements (CCEs).

[0006] One prior art again proposes a method to construct a subframe of control channel elements for PDCCH transmission based on an evaluation of a cost function C(j) for each effective combination (j) of control channel elements that improves the system performance. This consists of a predefined distribution of the total number of transmitted resource elements, the total used transmit power, and a predefined distribution of interference per symbol. However, the prior art cannot provide a dynamic distribution of the total number of transmitted resource elements with respect to system variables such as channel conditions or the total number of connected users. The predefined options are only to handle the specific conditions of the system deployment to any wireless carrier.

[0007] Another prior art proposes a method for allocating control channel resources in a transmitter, where these control resources are allocated to multiple scheduling entities using the availability states of the control channel elements, such as unused, available, unavailable, conflicting, etc. A resource mapping circuit of this system is configured to determine the availability state of each candidate set by: (a) determining that a candidate set is available if the allocation states of all the control channel elements are unused, (b) determining that a candidate set is unavailable if the allocation state of at least one of its control channel elements is used, and (c) determining that a candidate set is conflicting if the allocation states of one or more of its control channel elements are alternate, the allocation states of the remaining control channel elements are unused, and allocating the control channel elements in the alternate state would not block other competing scheduling entities for which one or more of the control channel elements in the candidate set are designated as alternates.

[0008] However, the prior art does not consider how many such control channel elements are associated with a user based on the user's mobility, channel conditions, and user traffic data queued in the system. Another prior art describes a new structure of a control channel region in a subframe of a 3GPP-based communication system using OFDM in the downlink. The control channel region is divided into CCEs having equal sizes, regardless of the presence of further cell-specific and / or user-specific reference signals in the control channel region. The method consists of obtaining a number of CCEs from a region defined for a PDSCH region, assigning them to a number of devices, and determining CRC codes of downlink control information of the receiving device. However, the prior art does not consider how many such control channel elements should be associated with cell-specific and / or UE-specific reference signals. Nor does it consider the quantification of these CCEs with respect to user-specific reference signals. Therefore, if a user enters a bad channel condition, it is not considered how many such CCEs should be assigned or how such CCEs should be shared among a number of user devices. A wireless communication control channel apparatus and method provides control channel transmission in a wireless network. According to this method, at least one resource block (RB) including a first control channel element is associated with a first antenna port (AP), and a second control channel element is associated with a second AP. The first and second control channel elements may be used for a single control channel transmission, and a first reference signal sequence associated with one of the first AP and the second AP is selected for the single control channel transmission based on a control channel element index value. The prior art does not provide a method for associating an upper limit of RBs with a control channel element. This creates a situation where a user device will get fewer control channel elements for a particular control channel message. Also, from a system perspective, there is no defined method for restricting RBs to control channel elements. This leads to under- or over-utilization of RBs for control channel elements.In the control channel element indexing scheme, partitioning of control channel resources based on an indexing scheme is mentioned. The system understands partitioned data channel information, the channel resource elements are partitioned, and then the partitioned elements are associated with partitioned control resource elements, and thus the data channel information is partitioned into multiple partitions and transmitted to the device. In this method, a unique index pair of partitioned elements and partitioned control resource elements is also created. The method also includes obtaining information on which resource blocks carry downlink control channels, determining a number of control channel elements for each assigned resource block, and then defining at least one control channel element index based on the information on which resource blocks carry downlink control channels. However, this scheme does not provide how many CCE indexes can be generated in the system based on multiple system variables such as users in the network, interference generated due to consecutive common resource block transmissions, maximum and minimum allocation schemes of resource blocks for CCE allocation, etc.

[0009] Therefore, there is a need for an improved PDDCH resource allocation mechanism for an optimized CORESET definition without compromising the data rate requirements of the users. Summary of the Invention [Problem to be solved by the invention]

[0010] Some of the objectives of the present disclosure that are met by at least one embodiment herein are listed herein below.

[0011] An objective of the present disclosure is to provide a system and method that takes into account multiple system level parameters, such as connected users, along with estimated user channel state distributions to calculate PDDCH resources during start-up of a gNB system, where the channel state directly takes into account slow and fast fading effects.

[0012] An objective of the present disclosure is to provide a system and method for correcting estimates during steady-state operation of a gNB system, taking into account feedback from the scheduler and RRC entities.

[0013] It is an object of the present disclosure to provide a system and method that considers candidates in both a common search space and a user-specific search space.

[0014] It is an object of the present disclosure to provide a system and method that takes into account the calculation of CCE and checks whether it exceeds the maximum radio resource limit, and if it does, the method reduces the CCE to stay within the maximum radio resource limit. [Means for solving the problem]

[0015] This section is provided to introduce certain objects and aspects of the disclosure in a simplified form, which are further described below in the Detailed Description. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0016] In one aspect, the present disclosure provides a system that facilitates improved physical downlink control channel (PDDCH) resource allocation in a wireless network. The system may include one or more user equipment communicatively coupled to the wireless network. The wireless network may further include a plurality of base stations, one or more packet gateway nodes, and a scheduler configured to determine user traffic data queued in the system. The system may also include a radio resource control unit (RRC) operatively coupled to any or a combination of the one or more base stations, the one or more packet gateway nodes, and the scheduler. The RRC may comprise a processor that executes a set of executable instructions stored in a memory, which upon execution causes the system to initialize an improved PDCCH resource calculation (IPRC) unit operatively coupled to the RRC. Upon initialization, the IPRC unit may receive one or more data packets related to parameters associated with one or more PDCCH resources requiring allocation in the wireless network to one or more user equipment registered in the system via the respective packet gateway nodes from one or more base stations. The system may further extract, by the IPRC unit, a first set of attributes related to one or more parameters associated with the one or more PDCCH resources, and extract a second set of attributes from the scheduler, the second set of attributes related to user traffic data queued in the system that causes blocking of the one or more PDCCH resources. The IPRC unit may then calculate a number of operating parameters and one or more PDCCH resources to be assigned from the extracted first and second sets of attributes, and may update, by the IPRC unit, the number of the one or more PDCCH resources to the RRC and the scheduler.

[0017] In one aspect, the present disclosure provides a method for facilitating improved physical downlink control channel (PDDCH) resource allocation in a wireless network. The method may include initializing an improved PDCCH resource calculation (IPRC) unit operatively coupled to a radio resource control unit (RRC) operatively coupled to one or more of the base stations, the one or more packet gateway nodes, and a scheduler, and upon initialization, the method may further include receiving, from the one or more base stations, one or more data packets related to parameters associated with one or more PDCCH resources in the wireless network that request allocation to one or more user equipment registered in the system via the respective packet gateway nodes. The method may further include extracting, by the IPRC unit, a first set of attributes related to one or more parameters associated with the one or more PDCCH resources, and extracting, by the IPRC unit, a second set of attributes from the scheduler, the second set of attributes related to user traffic data queued in the system that causes blocking of one or more PDCCH resources. Further, the method may include calculating, by the IPRC unit, a number of operational parameters and one or more PDCCH resources to be assigned from the extracted first and second sets of attributes; and updating, by the IPRC unit, a number of the one or more PDCCH resources to the RRC and the scheduler.

[0018] The accompanying drawings, which are incorporated herein and form a part of the present invention, illustrate exemplary embodiments of the disclosed method and system, with like reference numerals referring to the same parts throughout the different drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed on clearly illustrating the principles of the invention. Some drawings may use block diagrams to illustrate components and may not show the internal circuitry of each component. Those skilled in the art will appreciate that the inventions in such drawings include inventions in electrical components, electronic components, or circuits commonly used to implement such components. [Brief description of the drawings]

[0019] [Figure 1A] 1 illustrates an exemplary network architecture in which or with which the system of the present disclosure may be implemented, according to one embodiment of the present disclosure. [Figure 1B] 1 shows an exemplary flow chart of the proposed method according to one embodiment of the present disclosure. [Figure 2A] 1 illustrates an example representation of an existing bandwidth portion method for resource allocation, according to one embodiment of the present disclosure. [Figure 2B] 1 illustrates an example representation of an existing bandwidth portion method for resource allocation, according to one embodiment of the present disclosure. [Diagram 3] 1 illustrates an example representation of an existing PDCCH configuration information element, in accordance with one embodiment of the present disclosure. [Figure 4A] 1 illustrates an example representation of CCE calculations for different aggregation levels, according to one embodiment of the present disclosure. [Figure 4B] 1 illustrates an example representation of CCE calculations for different aggregation levels, according to one embodiment of the present disclosure. [Diagram 5] 5 illustrates a typical baseline implementation level of an existing gNB system (500) according to one embodiment of the present disclosure. [Figure 6A] 1 illustrates an exemplary representation of a proposed gNB system (600) according to one embodiment of the present disclosure. [Figure 6B] 1 illustrates an exemplary representation of a proposed gNB system (600) according to one embodiment of the present disclosure. [Figure 7] 7 shows an exemplary representation of a flow chart of the proposed method (700) according to one embodiment of the present disclosure. [Figure 8] 1 illustrates an exemplary user plane protocol stack in a user equipment (UE) and a gNB that may utilize or with which embodiments of the present disclosure may be utilized, in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] The above will become more apparent from the following more detailed description of the invention.

[0021] In the following description, for purposes of explanation, various specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure. However, it will be apparent that the embodiments of the present disclosure can be practiced without these specific details. Some features described below can be used independently of each other or with any combination of other features. Individual features may not address all of the above problems, or may address only some of the above problems. Some of the above problems may not be fully addressed by any of the features described herein.

[0022] The present invention provides a robust and effective solution to an entity or organization by enabling the entity or organization to improve the Physical Downlink Control Channel (PDCCH) resource allocation mechanism with better resource block utilization without compromising service continuity and user data rate requirements.

[0023] FIG. 1 illustrates an exemplary network architecture in which the system of the present disclosure may be implemented or with which the system of the present disclosure may be implemented, according to an embodiment of the present disclosure. As illustrated, in one aspect, a base station (104) (also referred to as gNB (104)) may provide user plane (122) and control plane (124) protocol terminations towards one or more user equipment (102). In an exemplary embodiment, the user plane may be, but is not limited to, a 5G New Radio user plane, and the base station may be, but is not limited to, a 5G base station. The gNB may connect to the 5GC by a network gateway (NG) interface (NG1, NG2...NG15), and more specifically, to an access and mobility management function (106) (AMF 106) by an NG2 interface (NG-Control) interface, and to a user plane function (118) (UPF 118) by an NG3 (NG-User) interface. The network architecture (100) may further include an authentication server function (108) (AUSF 108), a user data management (114) (UDM 114), a session management function (110) (SMF 110), a policy control function (112) (PCF 112), and an application function unit (116).

[0024] The system may further include a scheduler configured to determine user traffic data queued in the system, and a radio resource control unit (RRC) operably coupled to any or a combination of the one or more base stations, the one or more packet gateway nodes, and the scheduler. The RRC may cause an improved PDCCH resource calculation (IPRC) unit operably coupled to the RRC to be initialized in the system. Upon initialization, the IPRC unit may receive from the one or more base stations via the respective packet gateway nodes one or more data packets related to parameters associated with one or more PDCCH resources requiring allocation in the wireless network to one or more user equipments registered in the system. The IPRC unit may extract a first set of attributes related to one or more parameters associated with the one or more PDCCH resources and extract a second set of attributes from the scheduler, the second set of attributes related to user traffic data queued in the system causing blocking of one or more PDCCH resources. The IPRC unit may then calculate a number of operating parameters and one or more PDCCH resources to be allocated from the extracted first and second sets of attributes, and update the number of the one or more PDCCH resources to the RRC and the scheduler.

[0025] In an exemplary embodiment, the IPRC unit can receive a combination of periodic performance feedback from the scheduler and periodic feedback of a fixed amount of usage from the RRC to update the IPRC unit. The combination of periodic performance feedback from the scheduler and periodic feedback of a fixed amount of usage from the RRC corrects the multiple estimates during steady state operation of the system. The IPRC unit can further optimize the calculation of one or more PDCCH resources by a set of predefined instructions.

[0026] In one embodiment, during initialization of the IPRC unit, the IPRC unit can interact with a configuration database coupled to the system via a configuration interface to obtain default configuration parameters for the system during system startup. The IPRC unit can then store the operating parameters and default configuration parameters for the system.

[0027] In one embodiment, the IPRC may be in a reconfiguration mode when there are changes to the default system configuration parameters. When the default system configuration parameters are changed, the IPRC may receive configuration information via a communication interface coupled to the system.

[0028] In one embodiment, the IPRC unit in the reconfiguration mode is configured to obtain a plurality of latest configuration parameters from a configuration database, configure the IPRC unit with the plurality of latest parameters, and store the latest configuration parameters in a local copy in a memory unit coupled to the IPRC unit.

[0029] In one embodiment, when the IPRC is not in a startup or reconfiguration mode, the IPRC unit can load a local copy of the system's configuration parameters into the memory unit.

[0030] In an exemplary embodiment, depending on the geographic deployment area, the IPRC unit may accept default configuration parameters for the system.

[0031] In one embodiment, the IPRC unit can dynamically generate operating parameters for PDCCH resource calculation for multiple aggregation levels based on system variables and conditions. The IPRC unit can further consider multiple system level parameters and estimated user channel condition distributions to calculate PDDCH resources during system startup. In an exemplary embodiment, the channel conditions can include, but are not limited to, slow fading effects and fast fading effects.

[0032] In an exemplary embodiment, the IPRC unit can check whether the maximum PDCCH resource has been exceeded, and if so, the IPRC unit reduces the control channel elements (CCEs) to fit the maximum PDCCH resource.

[0033] In an example embodiment, the functions of the Radio Resource Control (RRC) unit (also referred to as Radio Resource Management) may include, but are not limited to, radio bearer control, radio admission control, connection mobility control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink, IP header compression, encryption, and integrity protection of data, selection of an AMF at UE attachment time if routing to the AMF cannot be determined from information provided by the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and release, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (originating from AMF or OAM), configuration of measurements and measurement reports for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC_INACTIVE state, delivery function of NAS messages, sharing of radio access networks, dual connectivity, close coordination between NR and E-UTRA, etc.

[0034] The AMF (106) may host key functions such as, but not limited to, NAS signaling termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policy), support for network slicing, SMF selection, etc.

[0035] The UPF (118) may host key functions such as, but not limited to, anchor point for intra / inter-RAT mobility (when applicable), external PDU session point for interconnection to data networks, packet routing and forwarding, packet inspection and user plane portion for policy rule application, traffic usage reporting, uplink classifier supporting routing of traffic flows to data networks, branching point supporting multi-homed PDU sessions, user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (SDF to QoS flow mapping), downlink packet buffering and triggering of downlink data notifications.

[0036] The SMF (110) may host key functions such as, but not limited to, session management, allocation and management of UE IP addresses, selection and control of UP functions, configuring traffic steering in the UPF to route traffic to the appropriate destination, policy enforcement and part of QoS control, downlink data notification, etc.

[0037] The PCF (112) can host the main functions of the 5G PCF performing the same functions as the PCRF in 4G networks, providing policy rules for control plane functions, including but not limited to network slicing, roaming and mobility management, accessing subscription information for policy decisions made by the UDR, supporting new 5G QoS policy and charging control functions, etc.

[0038] The AUSF (108) may host major functions such as, but not limited to, the AUSF performing the authentication function of the 4G HSS, implementing an EAP authentication server, and storing keys.

[0039] The UDM (114) may host key functions such as, but not limited to, Authentication and Key Agreement (AKA) credential generation, user identification, access authentication, and subscription management, where the UDM performs some of the 4G HSS functions.

[0040] The AF (116) may host key functions such as, but not limited to, application influence on traffic routing, access to network exposure capabilities, and interaction with a policy framework for policy control.

[0041] Communication between the gNB (104) and the user equipment (102) can take place over the air interface using a protocol stack. One of the main protocol stacks is the physical layer (also called PHY). Whenever user traffic data from the data network (120) needs to be transmitted to the user equipment (102), the user traffic data passes through the UPF (118) and the gNB (104) and arrives at the user equipment (102) in the downlink direction and vice versa in the uplink direction. To schedule user traffic data in the downlink direction, at least two main PHY layer functions are considered: (a) physical layer processing of the Physical Downlink Shared Channel (PDSCH); (b) physical layer processing of the Physical Downlink Control Channel (PDCCH). In an exemplary embodiment, the user's traffic data may be transmitted over the PDSCH, while the user's signaling data of the user's traffic data regarding (i) modulation, (ii) coding rate, (iii) size of the user's traffic data, (iv) transmission beam identification, (v) bandwidth portion, (vi) physical resource block, etc. may be transmitted over the PDCCH. Downlink as well as uplink transmission is via, but not limited to, Cyclic Prefix-based Orthogonal Frequency Division Multiplexing (CP-OFDM), which is part of the PHY layer. Thus, to perform transmission, CP-OFDM can use physical resource blocks (PRBs) to transmit both a user's traffic data via the PDSCH and a user's signaling data via the PDCCH.

[0042] In an exemplary embodiment, resource elements can be used to construct physical resource blocks (PRBs). For the downlink direction, the higher layer stack can allocate the number of resource elements used for PDCCH and PDSCH processing. There may be at least four important concepts defined regarding resources and how resources are grouped and given to PDCCH. These concepts are: (a) Resource Element: It is the smallest unit of the resource grid consisting of one subcarrier in the frequency domain and one OFDM symbol in the time domain. (b) Resource Element Group (REG): One REG consists of one resource block (12 resource elements in the frequency domain) and one OFDM symbol in the time domain. (c) Control Channel Element (CCE): A CCE consists of multiple REGs. The number of REG bundles in a CCE can vary. (d) Aggregation Level: The aggregation level indicates the number of CCEs allocated to the PDCCH. The aggregation levels and the number of CCEs allocated are shown in Table 1: [Table 1]

[0043] In one aspect, the gNB (104) may include one or more processors operably coupled to a memory that may cause the gNB to receive user traffic data from a plurality of candidates and identify candidates associated with each aggregation level based on the effective radio resource usage services and content for CCEs. The associated candidates may be identified by enabling a set of predefined system parameters for candidate calculation. Depending on the geographical deployment area, the processor may cause the gNB system to accept predefined system parameters of the configuration and self-generate operational parameter values ​​for candidate calculation, dynamically generate operational parameter values ​​for candidate calculation for various aggregation levels based on system variables and conditions of the gNB, thereby improving candidate calculation for different aggregation levels, and updating default system parameters for an efficient number of candidate calculations by obtaining periodic feedback from the scheduler and RRC to update the default system parameters.

[0044] 1B illustrates an example flow diagram of a proposed method (150) for facilitating improved physical downlink control channel (PDDCH) resource allocation in a wireless network. The method may include initializing 152 an improved PDCCH resource calculation (IPRC) unit operatively coupled to a radio resource control unit (RRC) operatively coupled to one or more of the base stations, the one or more packet gateway nodes, and a scheduler, and upon initialization, the method may further include receiving 154, by the IPRC unit, from one or more base stations, one or more data packets associated with parameters associated with one or more PDCCH resources in the wireless network that are requested to be allocated to one or more user equipment registered in the system via the respective packet gateway nodes.

[0045] The method (150) may further include extracting, by the IPRC unit, at 156, a first set of attributes related to one or more parameters associated with the one or more PDCCH resources, and extracting, by the IPRC unit, at 158, a second set of attributes from the scheduler, the second set of attributes related to user traffic data queued in the system that causes blocking of the one or more PDCCH resources.

[0046] Further, the method (150) may include calculating, by the IPRC unit, at 160, a number of operational parameters and one or more PDCCH resources to be assigned from the extracted first and second sets of attributes, and updating, by the IPRC unit, a number of the one or more PDCCH resources to the RRC and scheduler, at 162.

[0047] FIG. 5 shows a typical reference implementation level of an existing gNB system (500). As seen in FIG. 5, the gNB system may include multiple components on the hardware including a configuration database (506), memory unit(s) (508), higher layer circuitry (502), and physical circuitry (504). The higher layer circuitry (502) may include a processing unit such as a radio resource management unit (510) having a subitem called physical downlink control channel (PDCCH) resource calculation (532). The PDCCH resource calculation (532) is configured to manage functions related to control resource set (CORESET) and search space design. The gNB system (500) may further include an RRC (512), an eGTPU (514), a PDCP (516), a MAC, and a scheduler (520) in the higher circuit layer. The scheduler is a real-time entity that considers user traffic data queued in the gNB system and calculates various PDCCH blocking that is fed back to the method.

[0048] The PHY layer may include a PDCCH processing block (522), a PUCCH processing block (524), an SSB processing block (526), ​​a PDSCH processing block (528), and a PUSCH processing block (530). The radio resource management unit (510) may further include a handover processing block (534), a bearer control processing block (536), a PUCCH resource calculation (538), an admission control processing block (540), and a load balancing processing block (542). The PDSCH may include, but is not limited to, functions such as transport block CRC attachment, code block segmentation and code block CRC attachment, channel coding: including but not limited to LDPC coding, physical layer hybrid ARQ processing, rate matching, scrambling, modulation: including but not limited to QPSK, 16QAM, 64QAM, and 256QAM, layer mapping, mapping to assigned resources and antenna ports, etc.

[0049] Detailed processing of physical layer processing of the Physical Downlink Control Channel (PDCCH) may include downlink assignment including at least modulation and coding format, resource allocation, and hybrid ARQ information related to DL-SCH. Uplink scheduling grant includes at least modulation and coding format, resource allocation, and hybrid ARQ information related to UL-SCH. In addition to scheduling, the PDCCH can be used for activating and deactivating configured PUSCH transmissions with configured grants, activating and deactivating PDSCH semi-persistent transmissions, informing one or more UEs of slot formats, informing one or more UEs of PRBs and OFDM symbols for which the UE may assume no transmission is intended for the UE, transmitting TPC commands for PUCCH and PUSCH, transmitting one or more TPC commands for SRS transmission by one or more UEs, switching active bandwidth portions of the UE, initiating random access procedures, PDCCH candidates for configured monitoring opportunities in one or more configured control resource sets (CORESETs) according to corresponding search space configurations. A CORESET consists of a set of PRBs with duration of 1 to 3 OFDM symbols, but is not limited to this. Resource Element Groups (REGs) and Control Channel Elements (CCEs) of resource units are defined within a CORESET, with each CCE consisting of a set of REGs. A control channel is formed by an aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE to REG mappings are supported in a CORESET.

[0050] Detailed physical layer processing of synchronization signals and PBCH (SSB) may include, but is not limited to, primary and secondary synchronization signals (PSS, SSS), broadcast information. Detailed physical layer processing of physical uplink shared channel (PUSCH) may include, but is not limited to, transport block CRC attachment, code block segmentation and code block CRC attachment, channel coding: LDPC coding, physical layer hybrid ARQ processing, rate matching, scrambling, modulation: π / 2BPSK (transform precoding only), QPSK, 16QAM, 64QAM, and 256QAM, but is not limited to, layer mapping, transform precoding (enabled / disabled by configuration), and precoding, mapping to assigned resources and antenna ports.

[0051] Detailed processing of the physical layer processing of the physical uplink control channel (PUCCH) may include the following. Format #0: Short PUCCH of 1 or 2 symbols with small UCI payload up to 2 bits with UE multiplexing capacity of up to 6 UEs with 1 bit payload in the same PRB. · Format #1: Long PUCCH of 4 to 14 symbols with small UCI payload of up to 2 bits with UE multiplexing capacity of up to 84 UE without frequency hopping and UE multiplexing capacity of 36 UE with frequency hopping in the same PRB. · Format #2: Short PUCCH of 1 or 2 symbols with large UCI payload >2 bits without UE multiplexing in the same PRB. · Format #3: Long PUCCH of 4 to 14 symbols with large UCI payload with no UE multiplexing capability in the same PRB. · Format #4: Long PUCCH of 4 to 14 symbols with medium UCI payload with multiplexing capacity of up to 4 UEs in the same PRB.

[0052] Short PUCCH formats with up to 2 UCI bits are based on sequence selection, while short PUCCH formats with 3 or more UCI bits frequency multiplex UCI and DMRS. Long PUCCH formats time multiplex UCI and DMRS. Frequency hopping is supported for long PUCCH formats and for short PUCCH formats with duration of at least 2 symbols. Long PUCCH formats can be repeated in multiple slots. UCI multiplexing on PUSCH is supported when UCI and PUSCH transmissions are time-aligned by transmission of UL-SCH transport block or by triggering A-CSI transmission without UL-SCH transport block, UCI carrying HARQ-ACK feedback with 1 or 2 bits is multiplexed by puncturing PUSCH, in all other cases UCI is multiplexed by rate-matching PUSCH. UCI consists of but is not limited to the following information CSI, ACK / NAK, scheduling request.

[0053] Referring to Figures 6A and 6B, an exemplary gNB system (600) is shown in which the present disclosure can be implemented, according to an embodiment of the present disclosure. As shown in Figure 6A, by way of example and not limitation, the exemplary gNB system (600) can include an improved PDCCH resource calculation (IPRC) (602) that can be configured to enable default system parameters for associated candidate calculations, as shown in Figure 6B. Depending on the geographical deployment area, the gNB can accept a default system configuration, self-generate operational parameter values ​​for candidate calculations, and dynamically generate operational parameter values ​​for candidate calculations of different aggregation levels based on gNB system variables and conditions. Candidate calculations of different aggregation levels are updated by obtaining periodic feedback from the scheduler and RRC to update the default system parameters. Figure 6A shows an improved gNB with a new module named IPRC (602) introduced in the radio resource management entity. As part of this improvement, the interaction between the IPRC and the remaining modules of the higher layer circuitry has been changed. A more detailed diagram showing the interaction of the IPRC with other entities is shown in Figure 6B.

[0054] As in FIG. 6B, in one aspect, the Radio Resource Management (510) entity can obtain configuration information from the configuration database (506) (CD) via the CD-RRM-Entity interface during the start of the system (600). The IPRC (602), which is part of the Radio Resource Management unit (510), can then obtain the required configuration and load it into the persistent memory unit (508) for local configuration (LC) (IPRC-PMU). In an exemplary embodiment, the IPRC (602) can cause the Radio Management unit (510) to extract the configuration information required for PDCCH resource calculation by accessing the local configuration (LC) of the IPRC-PMU, determine the overall resource configuration, and update the system configuration information in the persistent memory unit IPRC-Sys-PMU (508). The updated resource configuration information can then be transmitted to the RRC (512) and the scheduler (514) via the IPRC-RRC-Config and IPRC-Sch-Config interfaces, respectively. The scheduler (514) may also periodically send some performance metrics to the IPRC via the Sch-IPRC-Feedback interface. The RRC may also periodically send some metrics based on the IPRC via the RRC-IPRC-Feedback interface.

[0055] In one embodiment, the IPRC (602) in the gNB can be responsible for calculating PDCCH resources for the entire gNB system (104) that will ultimately be assigned to user equipment (102) that is registering with the gNB system (104).

[0056] In an exemplary embodiment, to perform resource calculation, the IPRC can interact with a configuration database via a configuration interface CD-RRM-Entity interface to obtain default system parameters during the startup of the gNB system. During steady state, once the resource calculation is completed, the IPRC can update the resource information to the RRC and the scheduler via separate configuration APIs IPRC-RRC-Config and IPRC-Sch-Config interfaces, respectively. Also, during steady state, the dynamic operation of the IPRC is maintained by periodic feedback from the scheduler via feedback APIs Sch-IPRC-Feedback interface and from the RRC via the RRC-IPRC-Feedback interface.

[0057] In one embodiment, the IPRC may keep all configurations related to predefined system parameters in a local copy (LC), for example, in the persistent memory unit IPRC-PMU. By way of example and not limitation, the predefined system parameters that may be stored are: ConnUsers: This configuration parameter indicates the total number of connected users who have been successfully registered in the gNB system. Total_QFI: This configuration parameter indicates the total number of quality of service flow indicators (QFIs) supported in the gNB system. Percentage_UserDist_per_QFI(i): This configuration parameter indicates the percentage distribution of the total number of ConnUsers across different QFIs. The index i can be changed for multiple QFIs supported in the gNB system. Number_of_cov_dist: This configuration parameter indicates the number of coverage distribution zones expected within the transmission area of ​​the gNB system. Percentage_User_per_Cov_Dist(i): This configuration parameter indicates the percentage distribution of the total number of connected users (i.e., ConnUsers) distributed throughout the coverage area. The coverage distribution can be based on the signal quality received by the user equipment. Number_of_sig_msg: This configuration parameter indicates the total number of signaling messages supported by the gNB system. For example, these signaling messages may be other system information, paging, random access, etc. Prob_of_Sig_Msg(i): This configuration parameter indicates the probability that such a PDCCH message is generated to transmit the i-th signaling message among the total number of PDCCH messages generated from the gNB system of the user equipment. Prob_of_Non-Sig_Msg(i): This configuration parameter indicates the probability that such a PDCCH message is generated to transmit the i-th non-signaling message among the total number of PDCCH messages generated from the gNB system of the user equipment. Number_of_msg_per_user_per_service(i): This configuration parameter indicates the average number of messages exchanged at any periodic instant between the user equipment and the gNB system of the service. The index i can be modified for multiple services supported by the gNB system. These services can be categorized as Enhanced Broadband (eMBB), Ultra-Reliable Low Latency Communications (URLLC) and Massive Internet of Things (mIoT). 5G_Numerology: This configuration parameter provides the different 5G numerologies supported by the gNB system. The numerology is defined from the set of values ​​as {0,1,2,3,4}. Total_sig_msgs: This configuration parameter indicates the total number of signaling messages supported by the gNB system. These signaling messages may be for Other-System-Information, Paging, and Random Access. If we obtain the above three signaling messages, the value of Total_sig_msgs will be 3. Total_Aggr_Lvl_sig: This configuration parameter indicates the total aggregation level defined for all signaling messages supported in the gNB system. And the aggregation levels supported by the above signaling messages are {4,8,16}. If we get the above three signaling messages, the value of Total_Aggr_Lvl_sig will be 3. Sig_Aggr_Lvl(i)(j): This configuration parameter indicates the aggregation levels assigned to different signaling messages. The index i can be changed for different types of signaling messages supported in the gNB system. And the index j can be changed for different types of aggregation levels given to each of the i-th signaling messages supported in the gNB system. For example, for Other-System-Information, this parameter Aggr_Lvl_for_sig(i)(j) holds the number of different aggregation levels defined. The aggregation levels can be any combination of {4, 8, 16}. Total_non-sig_msgs: This configuration parameter indicates the total number of signaling messages supported in the gNB system. One example of a non-signaling message may be for user equipment traffic data. Total_Aggr_Lvl_non-sig: This configuration parameter indicates the total aggregation level defined for all non-signaling messages supported in the gNB system. And the aggregation levels supported by the above signaling messages are {1,2,4,8,16}. If we get the above three signaling messages, the value of Total_Aggr_Lvl_sig will be 5. Non-sig_Aggr_Lvl(i)(j): This configuration parameter indicates the aggregation level assigned to non-signaling messages based on the coverage distribution zone. The index i can be changed for different types of non-signaling messages supported in the gNB system. And the index j can be changed for different types of aggregation levels given to each of the i-th non-signaling messages supported in the gNB system. For example, for traffic data, this parameter Aggr_Lvl_for_non-sig(i)(j) holds the number of different aggregation levels defined. The aggregation levels can be any combination of {1, 2, 4, 8, 16}. Obsr_duration: This configuration parameter indicates the total time to calculate the resource calculation method. Feedbk_time: This configuration parameter indicates the period for accumulating the number of messages exchanged between the user equipment and the gNB system for the service. HYST: This configuration parameter specifies the hysteresis value to control the difference between the two entities. PDCCH_Blk_per_CovDist(i)_per_QFI(j)_per_Sig_msg(k)_per_Aggr_Lvl(l)_Th: This configuration parameter indicates the PDCCH blocking threshold of signaling messages for the user equipment for a particular coverage distribution, QFI, signaling message and aggregation level. PDCCH_Blk_per_CovDist(i)_per_QFI(j)_per_non-Sig_msg(k)_per_Aggr_Lvl(l)_Th: This configuration parameter indicates the PDCCH blocking threshold for signaling messages for a user equipment for a particular coverage distribution, QFI, signaling message and aggregation level. Max_Number_PDCCH_candidate_for_Sig_per_Aggr_Lvl(i): This configuration parameter indicates a value from values ​​known in the art. Sys_Res_Avail: This configuration parameter indicates the total number of radio resources available in the gNB system. For example, when 5G_Numerology=0, the total number of radio resources is 275. STEP_cand: This configuration parameter indicates the value by which the number of PDCCH candidates for the gNB system is increased or decreased. STEP_aggr_Lvl: This configuration parameter indicates a value that increases or decreases the number of aggregation levels per signaling or non-signaling message in the gNB system. During steady state, the IPRC keeps all configuration related to its operational parameters, for example in a local copy (LC) in the persistent memory unit IPRC-PMU. These parameters stored are: UserDist_per_QFI(i): This is an operational parameter that describes the user distribution across different QFI values. It is calculated in step 2 of the proposed method section. User_per_Cov_Dist(i): This is the operational parameter that describes the user distribution across different coverage distributions. It is calculated in step 2 of the proposed method section. Number_of_Sig_msgs_per_CovDist(i)_per_QFI(j): This is an operational parameter indicating the total number of signaling messages generated for the i-th coverage distribution zone of the gNB system for every j-th QFI. This is calculated in step 2 of the proposed method section. Number_of_non-Sig_msgs_per_CovDist(i)_per_QFI(j): This is an operational parameter indicating the total number of signaling messages generated for the i-th coverage distribution zone of the gNB system for every j-th QFI. This is calculated in step 2 of the proposed method section. Obsr_duration_per_service(i): This is an operational parameter that indicates the total count for running the proposed method. This is calculated in step 2 of the proposed method section. Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_Sig_msg(k)_per_Aggr_Lvl(l): This is an operational parameter indicating the total number of PDCCH candidates in the i-th coverage distribution zone of the gNB system per j-th QFI for the k-th signaling message and l-th aggregation level. This is calculated in step 2 of the proposed method section. Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_non-sig(k)_per_Aggr_Lvl(l): This is an operational parameter indicating the total number of PDCCH candidates for the i-th coverage distribution zone of the gNB system per j-th QFI for the k-th signaling message and the l-th aggregation level.

[0058] 7 shows an example flow diagram of a proposed method for improved PDCCH resource allocation according to one embodiment of the present disclosure. As shown, in one aspect, the proposed method (700) may include initializing an IPRC at 702. If the IPRC is in startup mode, the IPRC performs startup initialization. During the initialization, the IPRC may perform steps such as: IPRC receives ConnUsers, Total_QFI, Percentage_UserDist_per_QFI(i), Number_of_cov_dist, Percentage_User_per_Cov_Dist(i), Number_of_sig_msg, Prob_of_Sig_Msg(i), Prob_of_Non-Sig_Msg(i), Number_of_msg_per_u from the configuration database via the CD-RRM-Entity interface. The latest input of configuration parameters such as ser_per_service(i), 5G_Numerology, Total_sig_msgs, Total_Aggr_Lvl_sig, Sig_Aggr_Lvl(i)(j), Total_non-sig_msgs, Total_Aggr_Lvl_non-sig, Non-sig_Aggr_Lvl(i)(j), Obsr_duration, and Feedbk_time can be obtained to configure the parameters received in the IPRC. The IPRC may then store the received configuration parameters in a local copy in the IPRC-PMU's memory. Otherwise, if the IPRC is in reconfiguration mode, the IPRC can perform a reconfiguration (the IPRC is already started and there are changes to the IPRC default system configuration). If there are any changes in the configuration parameters, the IPRC can receive the configuration information through the communication interface (CD-RRM-Entity interface). The IPRC then performs the following steps: - Retrieve the latest inputs for configuration parameters from the configuration database. - Configure the IPRC with the latest parameters. - Save the latest configuration parameters to a local copy in the IPRC-PMU's memory. Otherwise, load the current configuration. If the IPRC is not in startup or reconfiguration mode, the IPRC uses the following procedure to load a local copy of the configuration into its memory:

[0059] IPRC is ConnUsers, Total_QFI, Percentage_UserDist_per_QFI(i), Number_of_cov_dist, Percentage_User_per_Cov_Dist(i) , Number_of_sig_msg, Prob_of_Sig_Msg(i), Prob_of_Non-Sig_Msg(i), Number_of_msg_per_user_per_service(i), 5G_Numer A local configuration (LC) can be loaded from the configuration database to configure the IPRC-PMU with configuration parameters such as: ology, Total_sig_msgs, Total_Aggr_Lvl_sig, Sig_Aggr_Lvl(i)(j), Total_non-sig_msgs, Total_Aggr_Lvl_non-sig, Non-sig_Aggr_Lvl(i)(j), Obsr_duration, and Feedbk_time.

[0060] The method (700) may further include calculating IPRC operating parameters and PDCCH resources, at 704. The IPRC may calculate the operating parameters and PDCCH resources according to the following example set of instructions, where a first set of instructions may include the steps provided in the table below. [Table 2] [Table 3] [Table 4] [Table 5]

[0061] The method (700) may further include updating PDCCH resources to the RRC and the scheduler at 706. The IPRC may update resource information to the RRC and the scheduler via separate configuration APIs IPRC-RRC-Config and IPRC-Sch-Config interfaces, respectively. The main parameters that the IPRC updates are: · Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_Sig_msg(k)_per_Aggr_Lvl(l) · Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_Non-Sig_msg(k)_per_Aggr_Lvl(l)

[0062] The method (700) may further include receiving usage feedback from the scheduler and the RRC at 708. In one embodiment, the scheduler may provide constant periodic performance feedback via the API Sch-IPRC-Feedback interface and the RRC provides constant periodic feedback via the API RRC-IPRC-Feedback interface. The periodicity of this feedback is defined as Feedback_time. The main parameters of the feedback are: Actual_ConnUsers: The scheduler indicates the actual number of users physically registered and connected to the gNB system during steady state. Number_of_cov_dist: The scheduler indicates the actual number of coverage distributions measured using signal-to-noise ratio (SNR) during steady state and connected to the gNB system. Also, the RRC indicates the average number of coverage distributions measured using reference signal received power (RSRP). Users_per_QFI(i): The scheduler indicates the actual number of users across different QFIs during steady state. The index i can vary for multiple QFIs supported in the gNB system. · Users_per_Cov_Dist(i): The scheduler indicates the actual number of users across the coverage distribution during steady-state operation of the gNB system based on SNR. Similarly, the scheduler indicates the actual number of users per coverage distribution during steady-state operation of the gNB system based on RSRP. The index i can be modified for multiple coverage distributions observed in the gNB system. Number_of_Signal_Msg(i): The scheduler indicates the actual number of signaling messages observed during steady state of the gNB system. The index i can be changed for multiple signaling messages supported in the gNB system. Number_of_Non-Sig_Msg(i): The scheduler indicates the actual number of non-signaling messages observed during steady state of the gNB system. The index i can be changed for multiple non-signaling messages supported in the gNB system. Avg_Number_of_msg_per_user_per_service(i): The scheduler indicates the actual number of messages (both signaling and non-signaling) per user observed during steady state of the gNB system. The index i can vary for multiple services supported in the gNB system. PDCCH_Blk_per_CovDist(i)_per_QFI(j)_per_Sig_msg(k)_per_Aggr_Lvl(l): This parameter indicates the information how many times the scheduler failed to assign a particular candidate to a user equipment according to the operating parameters defined for a particular coverage distribution, QFI, signalling message and aggregation level. PDCCH_Blk_per_CovDist(i)_per_QFI(j)_per_Non-Sig_msg(k)_per_Aggr_Lvl(l): This parameter indicates the information how many times the scheduler failed to assign a particular candidate to a user equipment according to the operating parameters defined for a particular coverage distribution, QFI, signalling message and aggregation level.

[0063] The method (700) may further include optimizing the IPRC at 710. The IPRC performs parameter value modification using feedback obtained from the scheduler via the API Sch-IPRC-Feedback interface and from the RRC via the API RRC-IPRC-Feedback interface. Parameter values ​​optimized from default values ​​and different types of instructions are listed in the following table: Sig_Aggr_Lvl(i)(j) Non-sig_Aggr_Lvl(i)(j) · Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_Sig_msg(k)_per_Aggr_Lvl(l) · Number_of_PDCCH_candidate_per_CovDist(i)_per_QFI(j)_per_Non-Sig_msg(k)_per_Aggr_Lvl(l) [Table 6] [Table 7]

[0064] 8 illustrates an example user plane protocol stack in a user equipment (UE) and a gNB that may utilize or with which embodiments of the present invention may be utilized, in accordance with an embodiment of the present disclosure. As shown in the figure, in the user plane protocol stack, SDAP, PDCP, RLC, MAC and PHY sublayers are terminated at the gNB on the network side and at the user equipment (UE) side.

[0065] The PHY hosts key functions such as, but not limited to, physical layer processing of the Physical Downlink Shared Channel (PDSCH), physical layer processing of the Physical Downlink Control Channel (PDCCH), physical layer processing of synchronization signals and PBCH (SSB), physical layer processing of the Physical Uplink Shared Channel (PUSCH), and physical layer processing of the Physical Uplink Control Channel (PUCCH).

[0066] The MAC hosts main functions such as, but not limited to, mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from Transport Blocks (TBs) that are transmitted to / from the physical layer on the transport channels, scheduling information reporting, error correction with HARQ (one HARQ entity per cell in case of CA), prioritization between UEs with dynamic scheduling, prioritization of logical channels between logical channels of one UE, padding, etc.

[0067] RLC hosts the following main functions: transport of higher layer PDUs, sequence numbering independent of that of PDCP (UM and AM), error correction by ARQ (AM only), segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), RLC SDU discard (AM and UM), re-establishment of RLC, protocol error detection (AM only).

[0068] PDCP hosts the following main functions: sequence numbering, header compression and decompression: ROHC only, user data transport, reordering and duplicate detection, in-order delivery, PDCP PDU routing (for split bearers), PDCP SDU retransmission, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery in RLC AM, PDCP status reporting in RLC AM, PDCP PDU duplication (see subclause 16.1.3) and indication to lower layers to discard duplicates.

[0069] The SDAP hosts key functions such as, but not limited to, mapping between QoS flows and data radio bearers, marking of QoS Flow Identifier (QFI) on both DL and UL packets.

[0070] The present disclosure provides a method and system for an improved PDCCH resource allocation mechanism for high speed wireless communication networks that can be configured as follows: · Enable default system parameters for candidate computation: Depending on the geographic deployment area, the gNB system can accept default system configurations from the user. · Self-generate operational parameter values ​​for candidate calculations: Dynamically generate operational parameter values ​​for candidate calculations at different aggregation levels based on gNB system variables and conditions. · Improve candidate computation for different aggregation levels: Candidate computation for different aggregation levels using different parameters such as default system parameters and self-generated behavior parameters. · Updating default system parameters by getting feedback from scheduler and RRC: A procedure to get periodic feedback from the scheduler and update the default system parameters to efficiently calculate the number of candidates.

[0071] Although considerable emphasis has been placed herein on the preferred embodiment, it should be understood that many embodiments may be made and many changes may be made in the preferred embodiment without departing from the principles of the invention. These and other changes in the preferred embodiment of the invention will be apparent to those skilled in the art from the disclosure herein, and it should be clearly understood that the foregoing description is to be taken merely as illustrative and not limiting of the invention.

[0072] Advantages of the present disclosure The present disclosure provides a system and method that considers multiple system level parameters, such as connected users, along with estimated user channel state distributions to calculate PDDCH resources during start-up of a gNB system, where the channel state directly takes into account slow and fast fading effects.

[0073] The present disclosure provides systems and methods for correcting estimates during steady-state operation of a gNB system, taking into account feedback from scheduler and RRC entities.

[0074] The present disclosure provides systems and methods that consider candidates in both a common search space and a user-specific search space.

[0075] This disclosure provides a system and method that takes into account the calculation of the CCE and checks if it exceeds the maximum radio resource limit, and if it does, the method reduces the CCE to stay within the maximum radio resource limit.

Claims

1. 1. A system that facilitates improved physical downlink control channel (PDCCH) resource allocation in a wireless network, the system comprising: One or more user equipment (UEs) communicatively coupled to the wireless network, the wireless network comprising: A plurality of base stations, one or more packet gateway nodes; a scheduler configured to determine queued user traffic data within the system; A radio resource control unit (RRC) operatively coupled to one or more of the base stations, the one or more packet gateway nodes, and any or a combination of the scheduler, the RRC comprising a processor that executes a set of executable instructions stored in a memory, the processor, upon execution, providing to the system: initializing an improved PDCCH resource calculation (IPRC) unit operatively coupled to the RRC; causing, upon initialization, the IPRC unit to receive from the one or more base stations via the respective packet gateway nodes, one or more data packets relating to parameters associated with one or more PDCCH resources requiring allocation in the wireless network to the one or more user equipments registered in the system; causing the IPRC unit to extract a first set of attributes related to one or more parameters associated with the one or more PDCCH resources; causing the IPRC unit to extract from the scheduler a second set of attributes related to the user traffic data queued in the system that cause blocking of the one or more PDCCH resources; causing the IPRC unit to calculate a number of operating parameters and one or more assigned PDCCH resources from the extracted first and second sets of attributes; updating, by the IPRC unit, the number of the one or more PDCCH resources to the RRC and the scheduler; The RRC; the one or more user equipments, The system comprising:

2. 2. The system of claim 1, wherein the IPRC unit receives a combination of periodic performance feedback from the scheduler and periodic feedback of a fixed usage from the RRC to update the IPRC unit, the combination of periodic performance feedback from the scheduler and periodic feedback of the fixed usage from the RRC revising a plurality of estimates during steady state operation of the system.

3. The system of claim 1 , wherein the IPRC unit optimizes the calculation of the one or more PDCCH resources according to a set of predefined instructions.

4. 2. The system of claim 1, wherein during the initialization of the IPRC unit, the IPRC unit interacts with a configuration database coupled to the system via a configuration interface to obtain default configuration parameters for the system during startup of the system.

5. The system of claim 1 , wherein the IPRC unit stores the operational and default configuration parameters of the system.

6. 2. The system of claim 1, wherein the IPRC is in a reconfiguration mode when there is a change to a default system configuration parameter, and when the default system configuration parameter is changed, the IPRC receives configuration information via a communications interface coupled to the system.

7. the IPRC in the reconstruction mode; Retrieves multiple, up-to-date configuration parameters from a configuration database, configuring said plurality of latest parameters in said IPRC unit; The latest configuration parameters are stored in a local copy in a memory unit coupled to the IPRC unit. The system of claim 6 , configured as follows:

8. The system of claim 1 , wherein the IPRC unit loads a local copy of the system's configuration parameters into a memory unit when the IPRC is not in a startup or reconfiguration mode.

9. The system of claim 1 , wherein the IPRC unit accepts default configuration parameters of the system depending on a geographic deployment area.

10. The system of claim 1 , wherein the IPRC unit dynamically generates the operating parameters for PDCCH resource calculation for multiple aggregation levels based on system variables and conditions.

11. The system of claim 1 , wherein the IPRC unit considers a number of system level parameters and an estimated user channel condition distribution to calculate the PDCCH resource during start-up of the system.

12. 2. The system of claim 1, wherein the IPRC unit checks whether the maximum number of PDCCH resources is exceeded, and if the maximum number of PDCCH resources is exceeded, the IPRC unit reduces control channel elements (CCEs) to fit the maximum number of PDCCH resources.

13. 1. A method for facilitating improved physical downlink control channel (PDCCH) resource allocation in a wireless network, comprising: initializing an improved PDCCH resource calculation (IPRC) unit operatively coupled to a radio resource control unit (RRC) operatively coupled to one or more base stations, one or more packet gateway nodes, and / or a scheduler; receiving, upon initialization, by said IPRC unit from said one or more base stations via respective packet gateway nodes, one or more data packets related to parameters associated with one or more PDCCH resources requiring allocation in said wireless network to one or more user equipments registered in said system; extracting, by the IPRC unit, a first set of attributes related to one or more parameters associated with the one or more PDCCH resources; extracting, by the IPRC unit, from the scheduler, a second set of attributes related to user traffic data queued in the system that causes blocking of the one or more PDCCH resources; calculating, by the IPRC unit, a number of operating parameters and one or more assigned PDCCH resources from the extracted first and second sets of attributes; updating, by the IPRC unit, a number of the one or more PDCCH resources to the RRC and the scheduler; The method comprising:

14. and receiving, by the IPRS unit, a combination of periodic performance feedback from the scheduler and periodic feedback of the fixed usage from the RRC to update the IPRC unit, wherein the combination of periodic performance feedback from the scheduler and periodic feedback of the fixed usage from the RRC modifies a plurality of estimates during steady state operation of the system. The method of claim 13.

15. optimizing, by the IPRC unit, the calculation of the one or more PDCCH resources according to a set of predefined instructions. The method of claim 13 further comprising:

16. interacting with a configuration database coupled to the system via a configuration interface by the IPRC unit to obtain default configuration parameters for the system during startup of the system; The method of claim 13 further comprising:

17. storing, by said IPRC unit, said operational parameters and default configuration parameters of said system; The method of claim 13 further comprising:

18. receiving configuration information by the IPRC unit via a communication interface coupled to the system when the IPRC unit is in a reconfiguration mode and when there is a change to a default system configuration parameter; The method of claim 13 further comprising:

19. The method in the reconstruction mode further comprises: Retrieving a plurality of latest configuration parameters from a configuration database; configuring said plurality of latest parameters in said IPRC unit; storing the latest configuration parameters in a local copy in a memory unit coupled to the IPRC unit; 20. The method of claim 18, further comprising:

20. loading, by the IPRC, a local copy of configuration parameters of the system into a memory unit when the IPRC is not in a startup mode or a reconfiguration mode. The method of claim 13 further comprising:

Images