CN103327510A - Method and equipment for determining load factors - Google Patents

Abstract

The invention relates to the technical field of communication, in particular to a method and equipment for determining load factors. The method and equipment for determining the load factors is used for determining the control channel load factors. The method comprises the steps of determining a total resource overhead valve in a downlink control domain of a wireless frame under a standard control domain load value and determining a control domain load value according to the total resource number of the control domain of the wireless frame and the determined resource overhead value. Due to the fact that the control channel load factors can be determined, the precision rate of pre-calculated results of a downlink control channel link is improved, and real covering level of the downlink control channel is reflected veritably to the greatest extent; furthermore, the system performance is guaranteed.

Description

Method and equipment for determining load factor

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a method and a device for determining a load factor.

Background

The link budget is to estimate the coverage capability of the system by investigating and analyzing various influence factors in the propagation paths of uplink signals and downlink signals in the system, so as to obtain the maximum propagation loss allowed by the link under the condition of keeping a certain call quality.

Factors affecting the link budget are many, including the transmission power of the mobile phone, the receiving sensitivity of the base station, the shadow fading margin, the penetration loss of the building, the traffic rate, the demodulation threshold of the traffic, and the like, so the link budget generally needs to be performed by differentiating the geographic environment, the traffic rate, and the channel type. Link budgeting is required to be performed according to different channel types because the link budgeting targets of the traffic channel and the control channel are different; the traffic channel performs link budget on the premise of ensuring the target Rate of the edge, and the control channel performs link budget on the premise of ensuring the BLER (Block Error Rate).

The link budget method and process of the downlink service channel and the control channel of the TD-LTE (Time Division-Synchronous Code Division Multiple Access long term Evolution) system are basically the same, and the basic process is as follows:

(1) calculating and determining downlink Equivalent Isotropic Radiated Power (EIRP) according to the configured transmitting end parameters and resource combinations;

(2) calculating to obtain interference reserve according to system load, coverage environment and the like;

(3) calculating to obtain the sensitivity and the minimum receiving level of the receiver according to a link demodulation threshold, interference reserve and the like;

(4) calculating to obtain the maximum path loss by considering shadow fading margin, penetration loss and the like;

(5) and calculating according to the road loss model parameters and the like to obtain the maximum coverage distance and the number of the station sites.

In the current downlink budgeting method of the LTE system, a method of calculating interference reserve by using a load factor of a traffic channel is uniformly adopted in the process of carrying out the budget of the traffic channel and a control channel link. However, in principle, the load factor of the traffic channel is different from that of the control channel in the actual operation process of the LTE system. Load factors of the traffic channels are uniformly adopted for calculation, so that the link budget result of the downlink control channel is inaccurate to a certain extent, and the actual coverage level of the downlink control channel cannot be actually reflected. There is currently no scheme for determining the control channel loading factor.

In summary, there is no scheme for determining the control channel loading factor.

Disclosure of Invention

The method and the device for determining the load factor are used for determining the control channel load factor.

The method for determining the load factor provided by the embodiment of the invention comprises the following steps:

determining a total resource overhead value in a downlink control domain of a wireless frame under a reference control domain load value;

and determining a control domain load value according to the total resource number of the control domain in the wireless frame and the determined total resource overhead value.

The device for determining the load factor provided by the embodiment of the invention comprises:

a first determining module, configured to determine a total resource overhead value in a downlink control domain of a radio frame under a reference control domain load value;

and the second determining module is used for determining the load value of the control domain according to the total resource number of the control domain in the wireless frame and the determined total resource overhead value.

The load factor of the control channel can be determined, so that the accuracy of the link budget result of the downlink control channel is improved, and the real coverage level of the downlink control channel is truly reflected to the maximum extent; further ensuring system performance.

Drawings

FIG. 1 is a schematic flow chart of a method for determining a load factor according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of an apparatus for determining a load factor according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a method for determining a load factor through a load list according to an embodiment of the present invention.

Detailed Description

The embodiment of the invention determines the control domain load value according to the total resource number of the control domain in the wireless frame and the total resource overhead value in the downlink control domain of the wireless frame under the reference control domain load value. The load factor of the control channel can be determined, so that the accuracy of the link budget result of the downlink control channel is improved, and the real coverage level of the downlink control channel is truly reflected to the maximum extent.

In implementation, the scheme of the embodiment of the invention can be applied to a TD-LTE system.

The embodiments of the present invention will be described in further detail with reference to the drawings attached hereto.

As shown in fig. 1, the method for determining the load factor according to the embodiment of the present invention includes the following steps:

step 101, determining a total resource overhead value in a downlink control domain of a wireless frame under a reference control domain load value;

and step 102, determining a control domain load value according to the total resource number of the control domain in the wireless frame and the determined total resource overhead value.

Preferably, if only one reference control domain load value is preset, in step 102, the determined control domain load value is used as the actual control domain load value;

if a plurality of reference control domain load values are preset, step 102 may further include:

aiming at a reference control domain load value, comparing the control domain load value determined under the reference control domain load value with the reference control domain load value to obtain a difference value;

and comparing the difference value corresponding to each control domain load value, and taking the control domain load value corresponding to the minimum difference value as an actual control domain load value.

For example, there are three reference control domain load values of 10%, 20%, and 30%, and the corresponding control domain load values are a1, B1, and C1, the smallest value is selected from | 10% -a1|, | 20% -B1|, and | 30% -C1 |. Assuming that | 20% -B1| is minimum, then B1 is taken as the actual control domain load value.

The load value of each reference control domain and the load value of each reference control domain can be set according to the requirement.

In implementation, the actual control domain load may be determined according to equation one:

${\mathrm{\η}}_{\mathrm{Control}\_\mathrm{Domain}}=\underset{j}{\min }\left(\right|{{\mathrm{\η}}^j}_{\mathrm{Control}\_\mathrm{Domain}}-{{\mathrm{\η}}^{-j}}_{\mathrm{Control}\_\mathrm{Domain}}\left|\right)$ ................ equation one;

wherein,

representing a control domain load value determined at the reference control domain load value;

indicating reference controlA domain load value; eta_{Control_Domain}Representing the actual control domain load.

Preferably, in step 101, the resource overhead values of each downlink pilot signal and/or control channel in one radio frame are added to obtain a total resource overhead value.

The control channel of the embodiment of the present invention includes, but is not limited to, the following partial or all channels:

PDCCH (Physical Downlink Control Channel), PHICH (Physical HARQ Indication Channel), and PCFICH (Physical Control Format Indication Channel);

the control channel downlink pilot signal comprises:

CRS (Cell-specific reference signals).

For example, the total resource overhead value is obtained by adding the resource overhead values of each downlink pilot signal and the control channel in one radio frame, where the downlink pilot signal includes CRS, and the control channel includes PDCCH, PHICH and PCFICH, the total resource overhead value may be determined according to the formula two:

$\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFram}{e}_{\mathrm{Occupied}\_\mathrm{In}\_\mathrm{Control}\_\mathrm{Domain}}$

$=\underset{j}{\mathrm{\Σ}}{\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{PDCCH}\_\mathrm{AggregationLevel}\_j}+{\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{PHICH}}$ .., formula two;

$+{\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{CRS}\_\mathrm{In}\_\mathrm{Control}\_\mathrm{Domain}}+{\mathrm{Re}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{PCFICH}}$

wherein RE _ Num _ PerFrame_{Occupied_In_Control_Domain}Representing a total resource overhead value; RE _ Num _ PerFrame_{PDCCH_AggregationLevel_j}Representing a resource overhead value of a PDCCH in a radio frame under a polymerization degree level j; RE _ Num _ PerFrame_PHICHRepresenting a resource overhead value of a radio frame PHICH; RE _ Num _ PerFrame_{CRS_In_Control_Domain}A resource overhead value representing a CRS within a radio frame; RE _ Num _ PerFrame_PCFICHA resource overhead value of PCFICH within one radio frame is indicated.

Preferably, if the control channel includes a PDCCH, step 101 determines a resource overhead value of the PDCCH in a radio frame according to the following steps:

and determining resource overhead values occupied by the PDCCH in each radio frame in scheduling under different polymerization degree levels according to the scheduling times of the PDCCH in each radio frame and the user proportion of each polymerization degree level under the load value of the reference control domain.

Preferably, in step 101, the resource overhead value of PDCCH in one radio frame is determined according to formula three:

RE_Num_PerFrame_{PDCCH_AggregationLevel_j}

＝ScheduleNum_PerFrame_PDCCH*Ratio_User_{AggregationLevel_j}

*CCE_Num_{AggregationLevel}equation three;

wherein RE _ Num _ PerFrame_{PDCCH_AggregationLevel_j}Representing a resource overhead value of a PDCCH in a radio frame under a polymerization degree level j; SchedulNum _ PerFrame_PDCCHIndicating the number of times of scheduling of the PDCCH within each radio frame; ratio _ User_{AggregationLevel_j}Representing the user proportion of each polymerization degree grade under the load value of the reference control domain; CCE _ Num_{AggregationLevel}Representing the number of CCEs at different aggregation level; RENum _ CCE represents the number of REs in each CCE.

Preferably, in step 101, the number of times of scheduling the PDCCH in each radio frame is determined according to the following steps:

s1, determining the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene according to the proportion distribution of uplink users and downlink users of various service types and the number of resource blocks required by uplink and downlink of various services in each wireless frame;

s2, determining the number of uplink users and the number of downlink users accommodated by various service types according to the number of uplink users and the number of downlink users accommodated by a single cell under a mixed service scene;

s3, determining the number of the scheduled users of PDCCH uplink single sub-frames in various services according to the average scheduling times of uplink in a downlink sub-frame of various service types and the determined number of the uplink users accommodated by various service types, and determining the number of the scheduled users of PDCCH downlink single sub-frames in various services according to the average scheduling times of downlink in a downlink sub-frame of various service types and the determined number of the downlink users accommodated by various service types;

and S4, determining the dispatching times of the PDCCH in each radio frame according to the determined number of the dispatching users of the PDCCH uplink single sub-frame in various services and the number of the dispatching users of the PDCCH downlink single sub-frame in various services.

Preferably, in S1: the number of resource blocks (considering the maximum allowed resource occupancy rate of the system) RB _ Num _ PerFrame needed by various services in uplink and downlink in each radio frame can be determined firstly_{i_UL}、RB_Num_PerFrame_{i_DL}And then determining the number of uplink users and the number of downlink users accommodated in a single cell in a mixed service scene.

Specifically, the number of resource blocks (i.e., resource demand) required for each service in uplink and downlink of each Radio frame is determined according to various service types (e.g., FTP (File Transfer Protocol), HTTP (hypertext Transfer Protocol), VOIP (voice over IP ), Video, Gaming, etc.) and service source characteristics (air interface support rate, average size of data packets, delay, RLC (Radio Link Control) mode, etc.), and considering Protocol overhead of a high layer and a physical layer.

Wherein, for a service, according to the physical layer HARQ downlink initial transmission Data volume HARQ _ InitTx _ Data _ Per _ Frame of the service in a single radio Frame_DLiAnd downlink Data amount Data _ Per _ PRB which can be carried by single resource block_DLDetermining the downlink resource demand Service _ PRB _ Num of the Service in a wireless frame_DLi。

Specifically, the method comprises the following steps: the downlink resource demand Service _ PRB _ Num of the Service in a wireless frame_DLiCan be determined according to the following formula:

Service_PRB_Num_DLi

＝HARQ_InitTx_Data_Per_Frame_DLi/Data_Per_PRB_DL。

aiming at the physical layer HARQ downlink initial transmission Data volume HARQ _ InitTx _ Data _ Per _ Frame of the service in a single radio Frame_DLiThe determination can be made in the following manner:

based on service rate requirement and high-level service downlink data packet Size App _ Pkt _ Size_DLiThe service downlink data packet Rate App _ Pkt _ Rate can be obtained_DLiAccording to the overhead of the high-level protocol, the physical layer HARQ initial transmission Data rate MAC _ PDU _ Data corresponding to a certain service can be obtained_DLiFurther, the physical layer HARQ initial transmission data volume of the Service in a single wireless frame is obtained, so that the resource requirement Service _ PRB _ Num of the Service in a wireless frame is obtained_DLi(unit: resource block/radio frame, where resource requirement does not take into account activation ratio of traffic).

For business downlink data packet Rate App _ Pkt _ Rate_DLiThe following formula can be used for determination.

Setting the downlink Rate of the air interface supporting service as Traffic _ Rate_DLi：

App_Pkt_Rate_DLi＝Traffic_Rate_DLi/App_Pkt_Size_DLi。

Wherein, Traffic _ Rate_DLiThe downlink rate demand of the service is; app _ Pkt _ Size_DLiThe size of the downlink data packet of the high-level service.

The high layer Protocol overhead comprises header compression overhead and Protocol header overhead of a Packet Data Convergence Protocol (PDCP) sublayer; protocol header overhead under an RLC (Radio Link Control) sublayer UM (Unacknowledged Mode), retransmission overhead, status report overhead and protocol header overhead under an RLC sublayer AM (Acknowledged Mode); the overhead of the MAC (Medium Access Control, media Access layer) sublayer includes MAC CE (MAC Control Element) overhead and protocol header overhead, and various overheads are calculated according to the flows of protocols (such as 36.322, 36.321, and the like) of the 3GPP LTE 36 series, which is not described herein again.

Aiming at the DATA volume PDCP _ PDU _ DATA delivered by the PDCP sublayer every second_DLi(unit: bps) can be determined according to the following formula:

PDCP_PDU_Rate_DLi＝App_Pkt_Size_DLi；

PDCP_PDU_Size_DLi＝App_Pkt_Size_DLi-PDCP_Wastage_DLi；

PDCP_PDU_DATA_DLi＝PDCP_PDU_Size_DLi×PDCP_PDU_Rate_DLi；

wherein, PDCP _ PDU _ Rate_DLiThe downlink data rate of the PDCP sublayer; PDCP _ Wasstage_DLiThe sum of the downlink header compression overhead and the downlink protocol header overhead of the PDCP sublayer; PDCP _ PDU _ Size_DLiThe size of a downlink data packet is the PDCP sublayer.

Data quantity RLC _ PDU _ Data transmitted by RLC sublayer every second_DLi(unit: bps) can be determined according to the following formula:

RLC_PDU_Rate_DLi＝；

(PDCP_PDU_Size_DLi×PDCP_PDU_Rate_DLi)/RLC_Data_Size_DLi

RLC_Data_Size_DLi＝RLC_PDU_Size_DLi-RLC_Wastage_DLi；

RLC_PDU_Data_DLi＝RLC_PDU_Size_DLi×RLC_PDU_Rate_DLi；

wherein RLC _ PDU _ Rate_DLiIs the downlink data rate of the RLC sublayer; RLC _ Data _ Size_DLiThe size of a downlink data packet of an RLC sublayer; RLC _ PDU _ Size_DLiThe size of a downlink PDU (protocol data Unit) of an RLC sublayer; RLC _ Wastage_DLiThe sum of the downlink retransmission overhead, the downlink state report overhead and the downlink protocol header overhead of the RLC sublayer; RLC _ PDU _ Data_DLiThe data size delivered by the RLC sublayer per second.

HARQ primary transmission MAC layer Data downlink rate MAC _ PDU _ Data_DLi(unit: bps) can be determined according to the following formula:

MAC_PDU_Data_DLi

＝RLC_PDU_Data_DLi+MAC_Subheader_Data_DLi+MAC_CE_Data_DLi；

wherein, MAC _ CE _ Data_DLiIs MAC CE downlink overhead; MAC _ Subheader _ Data_DLiIs the MAC sublayer downlink protocol header overhead.

The service has the physical layer HARQ downlink initial transmission data volume in a single wireless frame

HARQ_InitTx_Data_Per_Frame_DLiCan be determined according to equation twenty:

HARQ_InitTx_Data_Per_Frame_DLi＝MAC_PDU_Data_DLi/100；

wherein 100 represents the unit conversion result, which is converted into millisecond by second and then converted into a wireless frame (10ms), i.e. 100 wireless frames.

The method comprises the steps of determining the number of uplink resource blocks of a service in a radio frame according to the physical layer HARQ uplink initial transmission data volume of the service in a single radio frame and the uplink data volume which can be borne by a single resource block.

In implementation, the determination of the number of uplink resource blocks of the service in one radio frame is similar to the determination of the number of downlink resource blocks of the service in one radio frame, except that: all the data involved is uplink, and will not be described herein.

Preferably, the number of uplink users accommodated by a single cell in a mixed service scenario can be determined according to a formula four, and the number of downlink users accommodated by a single cell in a mixed service scenario can be determined according to a formula five:

${\mathrm{User}\_\mathrm{Num}}_{\mathrm{mix}\_\mathrm{UL}}=\frac{{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{Total}\_\mathrm{UL}}}{\underset{i}{\mathrm{\Σ}}{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{i\_\mathrm{UL}}*{\mathrm{Ratio}\_\mathrm{Traffic}}_{i\_\mathrm{UL}}}$ .... formula four;

${\mathrm{User}\_\mathrm{Num}}_{\mathrm{mix}\_\mathrm{DL}}=\frac{{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{Total}\_\mathrm{DL}}}{\underset{i}{\mathrm{\Σ}}{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{i\_\mathrm{DL}}*{\mathrm{Ratio}\_\mathrm{Traffic}}_{i\_\mathrm{DL}}}$ .... formula five;

wherein RB _ Num _ PerFame_{Total_UL}、RB_Num_PerFrame_{Total_DL}Respectively representing the number of uplink users and the number of downlink users accommodated in a single cell in a mixed service scene; RB _ Num _ PerFrame_{i_UL}、RB_Num_PerFrame_{i_DL}Respectively representing the number of resource blocks needed by various services in uplink and downlink in each wireless frame; ratio _ Traffic_{i_UL}、Ratio_Traffic_{i_DL}Respectively representing the proportion distribution of the uplink users and the proportion distribution of the downlink users of various service types.

Preferably, in S2: determining the number of uplink users accommodated by various service types according to a formula six; determining the number of downlink users accommodated by various service types according to a formula seven:

User_Num_{i_UL}＝min(User_Num_{mix_UL}，User_Num_{mix_DL})*Ratio_Traffic_{i_UL}.... formula six;

User_Num_{i_DL}＝min(User_Num_{mix_UL}，User_Num_{mix_DL})*Ratio_Traffic_{i_DL}.... formula seven;

wherein, User _ Num_{i_UL}、User_Num_{i_DL}Respectively indicating the number of uplink users and the number of downlink users accommodated by various service types.

Preferably, in S3: determining the number of the scheduled users of the PDCCH uplink single sub-frame in various services according to a formula eight; determining the number of the scheduled users of the PDCCH downlink single sub-frame in various services according to a formula nine:

Schedule_UserNum_PerSubframe_{i_UL}＝User_Num_{i_UL}*Schedule_Num_{i_UL}.., equation eight;

Schedule_UserNum_PerSubframe_{i_DL}＝User_Num_{i_DL}*Sehedule_Num_{i_DL}.., formula nine;

wherein Schedule _ UserNum _ PerSubframe_{i_UL}、Schedule_UserNum_PerSubframe_{i_DL}Respectively representing the number of uplink users and the number of downlink users accommodated by various service types; schedule _ Num_{i_UL}、Schedule_Num_{i_DL}Respectively representing the average scheduling times of an uplink and the average scheduling times of a downlink in a downlink subframe.

Preferably, in S4: the number of times of scheduling of PDCCH in each radio frame can be determined according to the formula:

$\mathrm{ScheduleNum}\_\mathrm{PerFram}{e}_{\mathrm{PDCCH}}$

$={\mathrm{Subframe}\_\mathrm{PerFrame}}_{\mathrm{UL}}*\underset{i}{\mathrm{\Σ}}{\mathrm{Schedule}\_\mathrm{UserNum}\_\mathrm{PerSubframe}}_{i\_\mathrm{UL}}$

$+{\mathrm{Subframe}\_\mathrm{PerFrame}}_{\mathrm{DL}}*\underset{i}{\mathrm{\Σ}}{\mathrm{Schedule}\_\mathrm{UserNum}\_\mathrm{PerSubframe}}_{i\_\mathrm{DL}}$ .., equation ten;

wherein, ScheduleNum _ PerFrame_PDCCHIndicating the number of times of scheduling of the PDCCH within each radio frame; subframe _ PerFrame_UL、Subframe_PerFrame_DLThe number of uplink subframes and the number of downlink subframes in each radio frame are respectively represented and related to subframe configuration in an actual system.

Due to the limitation of the uplink capacity, the downlink also has a partial Margin RB _ Margin_DL. According to the resource margin allocation principle, the number of users cannot exceed the number of uplink users for symmetric services (VoIP, video streaming, and Gaming), so the resource margin can only be used for downlink of asymmetric services.

Specifically, the quality monitoring in step S2 and step S3 may further include:

and if the downlink has asymmetric services, adding the downlink user allowance and the number of downlink users which are contained in the determined various service types to obtain the number of downlink users for determining the number of scheduling users of the PDCCH downlink single sub-frame in the various services.

Preferably, the partial Margin RB _ Margin may be determined according to formula eleven_DL：

${\mathrm{RB}\_M\arg \mathrm{in}}_{\mathrm{DL}}={\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{Total}\_\mathrm{DL}}$ .... 9.. formula eleven;

$-\underset{i}{\mathrm{\Σ}}{\mathrm{User}\_\mathrm{Num}}_{i\_\mathrm{DL}}*{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{i\_\mathrm{DL}}$

wherein RB _ Num _ PerFrame_{Total_DL}Representing the total number of resource blocks available for downlink in each radio frame; RB _ Num _ PerFrame_{i_DL}Indicating the number of resource blocks occupied by various services in each wireless frame; user _ Num_{i_DL}Indicating the number of downstream users accommodated by the various service types.

If the downlink asymmetric service comprises HTTP, the number of downlink users accommodated according to the formula twelve HTTP:

${\mathrm{HTTP}\_\mathrm{User}\_M\arg \mathrm{in}}_{\mathrm{DL}}$ .... formula twelve;

$=\frac{{\mathrm{RB}\_M\arg \mathrm{in}}_{\mathrm{DL}}*{\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{HTTP}\_\mathrm{DL}}}{({\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{FTP}\_\mathrm{DL}}+{\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{HTTP}\_\mathrm{DL}})*{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{HTTP}\_\mathrm{DL}}}$

wherein RB _ Margin_DLRepresents; ratio _ Traffic_{HTTP_DL}Representing the proportion distribution of HTTP downlink traffic; RB _ Num _ PerFame_{HTTP_DL}The number of resource blocks required by HTTP in each wireless frame in the downlink is represented; ratio _ Traffic_{FTP_DL}Indicating the FTP downlink traffic proportional distribution.

If the downlink has asymmetric services including FTP, the number of downlink users accommodated by the FTP can be determined according to a formula thirteen:

${\mathrm{FTP}\_\mathrm{User}\_M\arg \mathrm{in}}_{\mathrm{DL}}$ .... formula thirteen;

$=\frac{{\mathrm{RB}\_M\arg \mathrm{in}}_{\mathrm{DL}}*{\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{FTP}\_\mathrm{DL}}}{({\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{FTP}\_\mathrm{DL}}+{\mathrm{Ratio}\_\mathrm{Traffic}}_{\mathrm{HTTP}\_\mathrm{DL}})*{\mathrm{RB}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{FTP}\_\mathrm{DL}}}$

wherein RB _ M argin_DLRepresenting the downlink resource allowance; ratio _ Traffic_{HTTP_DL}Representing the proportion distribution of HTTP downlink traffic; RB _ Num _ PeFrame_{FTP_DL}The number of resource blocks required by FTP in each radio frame in the downlink is represented; ratio _ Traffic_{FTP_DL}Indicating the FTP downlink traffic proportional distribution.

Preferably, in step 101, the resource overhead value of PHICH in a radio frame is determined according to the formula fourteen:

RE_Num_PerFrame_PHICH

＝Schedule_UserNum_PerSubframe_UL/User_Num_PerGroup_PHICH

*RE_Num_PerGroup_PHICH*Subframe_PerFrame_UL.... fourteen formula;

wherein RE _ Num _ PerFrame_PHICHRepresenting a resource overhead value of a radio frame PHICH; schedule _ UserNum _ presubframe_ULRepresenting the number of users scheduled on the uplink of each subframe; user _ Num _ per group_PHICHRepresenting the number of multiplexed users in each PHICH group; RE _ Num _ Pergroup_PHICHIndicating the number of REs occupied by each PHICH group; subframe _ PerFrame_ULAnd the number of uplink subframes in each radio frame is shown.

Preferably, in step 101, the resource overhead value of the CRS in a radio frame is determined according to formula fifteen:

RE_Num_PerFrame_{CRS_In_Control_Domain}

＝RENum_PerRB_PerPortNum_PerSubframe_{CRS_In_Control_Domain}

*RBNum_PerSubframe*Port_Num*Subframe_PerFrame_DL... formula fifteen;

wherein RE _ Num _ PerFrame_{CRS_In_Control_Domain}A resource overhead value representing a CRS within a radio frame; RENum _ PerRB_PerPortNum_PerSubframe_{CRS_In_Control_Domain}Indicating the number of REs occupied by the CRS in each subframe in each RB port in a control domain; RBNum _ PerSubframe represents the number of RBs contained within the system bandwidth of each subframe; port _ Num represents the number of ports.

Preferably, in step 101, the resource overhead value of the PCFICH in one radio frame is determined according to the formula sixteen:

RE_Num_PerFrame_PCFICH

＝RENum_PerSubframe_PCFICH*Subframe_PerFrame_DL.... formula sixteen;

wherein RE _ Num _ PerFrame_PCFICHA resource overhead value representing the PCFICH within one radio frame; RENum _ Persubframe_PCFICHIndicating the number of REs occupied by the PCFICH in one subframe; subframe _ PerFrame_DLAnd the number of downlink subframes in each radio frame is represented.

Preferably, in step 102, the total number of resources of the control field in the radio frame is determined according to the formula seventeen:

RE_Num_PerFrame_{Total_In_Control_Domain}

＝Subframe_PerFrame_DL*RBNum_PerSubframe

seventeenth, CFI, SCNum _ perb.;

wherein RE _ Num _ PerFrame_{Total_In_Control_Domain}Represents the total number of resources of the control domain in the radio frame; subframe _ PerFrame_DLRepresenting the number of downlink subframes in each wireless frame; CFI represents the number of OFDM symbols occupied by a control domain in a downlink subframe; SCNum _ perb denotes the number of subcarriers contained in each RB.

Preferably, in step 102, the determined total resource overhead value is divided by the total number of resources of the control field in the radio frame to obtain a control field load value.

Specifically, the control domain load value can be obtained according to the formula eighteen:

${\mathrm{\η}}_{\mathrm{Control}\_\mathrm{Domain}}^j=\frac{{\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{Occupied}\_\mathrm{In}\_\mathrm{Control}\_\mathrm{Domain}}}{{\mathrm{RE}\_\mathrm{Num}\_\mathrm{PerFrame}}_{\mathrm{Total}\_\mathrm{In}\_\mathrm{Control}\_\mathrm{Domain}}}$ ...

The execution main body of the embodiment of the present invention may be a user equipment, or a network side device. The network side device may be a base station (such as a macro base station, a home base station, etc.), an RN (relay) device, or another network side device.

Based on the same inventive concept, the embodiment of the present invention further provides a device for determining a load factor, and since the principle of solving the problem of the device is similar to the method for determining a load factor according to the embodiment of the present invention, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 2, the apparatus for determining a load factor according to an embodiment of the present invention includes: a first determination module 20 and a second determination module 21.

A first determining module 20, configured to determine a total resource overhead value in a downlink control domain of a radio frame under a reference control domain load value;

a second determining module 21, configured to determine a control domain load value according to the total resource number of the control domain in the radio frame and the determined total resource overhead value.

Preferably, if there are a plurality of reference control domain load values, for a reference control domain load value, the second determining module 21 compares the control domain load value determined under the reference control domain load value with the reference control domain load value to obtain a difference value; and comparing the difference value corresponding to each control domain load value, and taking the control domain load value corresponding to the minimum difference value as an actual control domain load value.

Preferably, the first determining module 20 adds the resource overhead values of each downlink pilot signal and/or control channel in a radio frame to obtain a total resource overhead value.

Preferably, the first determining module 20 determines the resource overhead value of the PDCCH in one radio frame according to the following steps:

and determining resource overhead values occupied by the PDCCH in each radio frame in scheduling under different polymerization degree levels according to the scheduling times of the PDCCH in each radio frame and the user proportion of each polymerization degree level under the load value of the reference control domain.

Preferably, the first determining module 20 determines the resource overhead value of the PDCCH in one radio frame according to formula three.

Preferably, the first determining module 20 determines the number of times of scheduling the PDCCH in each radio frame according to the following steps:

determining the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene according to the uplink user proportion distribution and the downlink user proportion distribution of various service types and the number of resource blocks required by various services in uplink and downlink in each wireless frame; determining the number of uplink users and the number of downlink users accommodated by various service types according to the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene; determining the number of the scheduled users of PDCCH uplink single sub-frames in various services according to the average uplink scheduling times of various service types in a downlink sub-frame and the determined number of uplink users accommodated by various service types, and determining the number of the scheduled users of PDCCH downlink single sub-frames in various services according to the average downlink scheduling times of various service types in a downlink sub-frame and the determined number of downlink users accommodated by various service types; and determining the number of times of dispatching the PDCCH in each radio frame according to the determined number of dispatching users of the PDCCH uplink single sub-frame in various services and the number of dispatching users of the PDCCH downlink single sub-frame in various services.

Preferably, after the first determining module 20 determines the number of downlink users accommodated by each service type, if there is an asymmetric downlink service, the number of downlink users for determining the number of downlink users accommodated by each service type is obtained by adding the remaining number of downlink users to the number of downlink users for determining the number of scheduling users of the PDCCH downlink single subframe in each service.

Preferably, the first determining module 20 determines the resource overhead value of the PHICH within one radio frame according to the formula fourteen.

Preferably, the first determining module 20 determines the resource overhead value of the CRS in one radio frame according to formula fifteen.

Preferably, the first determining module 20 determines the resource overhead value of the PCFICH in one radio frame according to the formula sixteen.

Preferably, the second determining module 21 determines the total number of resources of the control field in the radio frame according to formula seventeen.

Preferably, the second determining module 21 divides the determined total resource overhead value by the total resource number of the control domain in the radio frame to obtain the control domain load value.

As shown in fig. 3, the method for determining the load factor through the load list according to the embodiment of the present invention includes the following steps:

step 301, calculating the number of scheduled users of PDCCH in each radio frame.

Step 302, selecting a reference control domain load value from the reference control domain load list, and calculating the user proportion of each polymerization degree grade under the reference control domain load value.

For example, the SINR (signal to interference Noise Ratio) obtained by system simulation under different loads according to the PDCCH channel, i.e. the Ratio S/(I + N) of the sum of signal, interference and Noise₀) A distribution curve result and a link simulation curve result of the PDCCH under different CCE (Control Channel Element) polymerization degree levels under different DCI (Downlink Control Information) formats, and a User Ratio _ User under each polymerization degree Level under the Control domain load is calculated_{AggregationLevel_j}。

Step 303, calculating resource overhead value RE _ Num _ PerFrame occupied by PDCCH in each wireless frame under different polymerization degree levels_{PDCCH_AggregationLevel_j}。

Step 304, calculating a resource overhead value RE _ Num _ PerFrame of the PHICH in a radio frame according to the scheduling times of the uplink PDCCH_PHICH。

Step 305, calculating resource overhead value of CRS in control domain in a wireless frame

RE_Num_PerFrame_{CRS_In_Control_Domain}。

Step 306, calculating resource overhead value RE _ Num _ PerFrame of PCFICH in a radio frame_PCFICH。

There is no necessary timing relationship between steps 303 to 306.

Step 307, calculating the total resource overhead RE _ Num _ PerFrame in the downlink control domain of a radio frame_{Occupied_In_Control_Domain}。

Step 308, according to the total resource number RE _ Num _ PerFrame of the control domain in the radio frame_{Total_In_Control_Domain}Calculate the speciesControl domain load value under load assumption

309, judging whether the currently selected reference control domain load value is the last one of the reference control domain load list, if not, taking the next reference control domain load value in the reference control domain load list, and executing the steps 302 to 308 again; if it is the last in the baseline control domain load list, the loop ends and step 310 is executed.

Step 310, calculating the control domain load under each load condition

And reference control domain load value

With the smallest difference

As the actual control domain load η_{Control_Domain}。

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (26)

1. A method of determining a load factor, the method comprising:

determining a total resource overhead value in a downlink control domain of a wireless frame under a reference control domain load value;

and determining a control domain load value according to the total resource number of the control domain in the wireless frame and the determined total resource overhead value.

2. The method of claim 1, wherein the determining the control domain load further comprises:

if a plurality of reference control domain load values exist, aiming at one reference control domain load value, comparing the control domain load value determined under the reference control domain load value with the reference control domain load value to obtain a difference value;

and comparing the difference value corresponding to each control domain load value, and taking the control domain load value corresponding to the minimum difference value as an actual control domain load value.

3. The method of claim 1, wherein determining a total resource overhead value comprises:

and adding the resource overhead values of each downlink pilot signal and/or control channel in one wireless frame to obtain a total resource overhead value.

4. The method of claim 3, wherein the control channel comprises some or all of the following:

a physical downlink control channel PDCCH, a physical hybrid automatic repeat request indicator channel PHICH and a physical control format indicator channel PCFICH;

the control channel downlink pilot signal comprises:

cell-specific pilot signals CRS.

5. The method of claim 4, wherein the resource overhead value for the PDCCH within a radio frame is determined according to the following steps:

and determining resource overhead values occupied by the PDCCH in each radio frame in scheduling under different polymerization degree levels according to the scheduling times of the PDCCH in each radio frame and the user proportion of each polymerization degree level under the load value of the reference control domain.

6. The method of claim 5, wherein the resource overhead value for the PDCCH within a radio frame is determined according to the following formula:

RE_Num_PerFrame_{PDCCH_AggregationLevel_j}

＝ScheduleNum_PerFrame_PDCCH*Ratio_User_{AggregationLevel_j}

*CCE_Num_{AggregationLevel}*RENum_PerCCE；

wherein RE _ Num _ PerFrame_{PDCCH_AggregationLevel_j}Representing a resource overhead value of a PDCCH in a radio frame under a polymerization degree level j; SchedulNum _ PerFrame_PDCCHIndicating the number of times of scheduling of the PDCCH within each radio frame; ratio _ User_{AggregationLevel_j}Representing the user proportion of each polymerization degree grade under the load value of the reference control domain; CCE _ Num_{AggregationLevel}Representing the number of CCEs at different aggregation level; RENum _ CCE represents the number of REs in each CCE.

7. The method of claim 5, wherein the number of schedules of PDCCH in each radio frame is determined according to the following steps:

determining the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene according to the uplink user proportion distribution and the downlink user proportion distribution of various service types and the number of resource blocks required by various services in uplink and downlink in each wireless frame;

determining the number of uplink users and the number of downlink users accommodated by various service types according to the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene;

determining the number of the scheduled users of PDCCH uplink single sub-frames in various services according to the average uplink scheduling times of various service types in a downlink sub-frame and the determined number of uplink users accommodated by various service types, and determining the number of the scheduled users of PDCCH downlink single sub-frames in various services according to the average downlink scheduling times of various service types in a downlink sub-frame and the determined number of downlink users accommodated by various service types;

and determining the number of times of dispatching the PDCCH in each radio frame according to the determined number of dispatching users of the PDCCH uplink single sub-frame in various services and the number of dispatching users of the PDCCH downlink single sub-frame in various services.

8. The method of claim 7, wherein determining the number of downlink users for each service type further comprises:

and if the downlink has asymmetric services, adding the downlink user allowance and the number of downlink users which are contained in the determined various service types to obtain the number of downlink users for determining the number of scheduling users of the PDCCH downlink single sub-frame in the various services.

9. The method of claim 4, wherein the resource overhead value of the PHICH within a radio frame is determined according to the following formula:

RE_Num_PerFrame_PHICH

＝Schedule_UserNum_PerSubframe_UL/User_Num_PerGroup_PHICH

*RE_Num_PerGroup_PHICH*Subframe_PerFrame_UL；

wherein RE _ Num _ PerFrame_PHICHRepresenting a resource overhead value of a radio frame PHICH; schedule _ UserNum _ presubframe_ULRepresenting the number of users scheduled on the uplink of each subframe; user _ Num _ per group_PHICHRepresenting the number of multiplexed users in each PHICH group; RE _ Num _ Pergroup_PHICHIndicating the number of REs occupied by each PHICH group; subframe _ PerFrame_ULAnd the number of uplink subframes in each radio frame is shown.

10. The method of claim 4, wherein the resource overhead value for CRS within a radio frame is determined according to the following formula:

RE_Num_PerFrame_{CRS_In_Control_Domain}

＝RENum_PerRB_PerPortNum_PerSubframe_{CRS_In_Control_Domain}

*RBNum_PerSubframe*Port_Num*Subframe_PerFrame_DL；

wherein RE _ Num _ PerFrame_{CRS_In_Control_Domain}A resource overhead value representing a CRS within a radio frame; RENum _ PerRB _ PerPortNum _ PerSubframe_{CRS_In_Control_Domain}Means CRS is in each sub-port of each RB in control domainNumber of REs occupied by the frame; RBNum _ PerSubframe represents the number of RBs contained within the system bandwidth of each subframe; port _ Num represents the number of ports.

11. The method of claim 4, wherein the resource overhead value for the PCFICH in a radio frame is determined according to the following formula:

RE_Num_PerFrame_PCFICH

＝RENum_PerSubframe_PCFICH*Subframe_PerFrame_DL；

wherein RE _ Num _ PerFrame_PCFICHA resource overhead value representing the PCFICH within one radio frame; RENum _ Persubframe_PCFICHIndicating the number of REs occupied by the PCFICH in one subframe; subframe _ PerFrame_DLAnd the number of downlink subframes in each radio frame is represented.

12. A method according to any of claims 1 to 11, wherein the total number of resources of the control field in a radio frame is determined according to the following formula:

RE_Num_PerFrame_{Total_In_Control_Domain}

＝Subframe_PerFrame_DL*RBNum_PerSubframe

*CFI*SCNum_PerRB；

wherein RE _ Num _ PerFrame_{Total_In_Control_Domain}Represents the total number of resources of the control domain in the radio frame; subframe _ PerFrame_DLRepresenting the number of downlink subframes in each wireless frame; CFI represents the number of OFDM symbols occupied by a control domain in a downlink subframe; SCNum _ perb denotes the number of subcarriers contained in each RB.

13. The method of any of claims 1 to 11, wherein determining a control domain load value comprises:

and dividing the determined total resource overhead value by the total resource number of the control domain in the wireless frame to obtain a load value of the control domain.

14. An apparatus for determining a load factor, the apparatus comprising:

a first determining module, configured to determine a total resource overhead value in a downlink control domain of a radio frame under a reference control domain load value;

and the second determining module is used for determining the load value of the control domain according to the total resource number of the control domain in the wireless frame and the determined total resource overhead value.

15. The device of claim 14, wherein the second determination module is further to:

if a plurality of reference control domain load values exist, aiming at one reference control domain load value, comparing the control domain load value determined under the reference control domain load value with the reference control domain load value to obtain a difference value; and comparing the difference value corresponding to each control domain load value, and taking the control domain load value corresponding to the minimum difference value as an actual control domain load value.

16. The device of claim 14, wherein the first determination module is specifically configured to:

and adding the resource overhead values of each downlink pilot signal and/or control channel in one wireless frame to obtain a total resource overhead value.

17. The apparatus of claim 16, wherein the control channel comprises some or all of the following:

a physical downlink control channel PDCCH, a physical hybrid automatic repeat request indicator channel PHICH and a physical control format indicator channel PCFICH;

the control channel downlink pilot signal comprises:

cell-specific pilot signals CRS.

18. The apparatus of claim 17, wherein the first determining module determines the resource overhead value for the PDCCH in one radio frame based on:

and determining resource overhead values occupied by the PDCCH in each radio frame in scheduling under different polymerization degree levels according to the scheduling times of the PDCCH in each radio frame and the user proportion of each polymerization degree level under the load value of the reference control domain.

19. The apparatus of claim 18, wherein the first determining module determines the resource overhead value for PDCCH in one radio frame according to the following formula:

RE_Num_PerFrame_{PDCCH_AggregationLevel_j}

＝ScheduleNum_PerFrame_PDCCH*Ratio_User_{AggregationLevel_j}

*CCE_Num_{AggregationLevel}*RENum_PerCCE；

wherein RE _ Num _ PerFrame_{PDCCH_AggregationLevel_j}Representing a resource overhead value of a PDCCH in a radio frame under a polymerization degree level j; SchedulNum _ PerFrame_PDCCHIndicating the number of times of scheduling of the PDCCH within each radio frame; ratio _ User_{AggregationLevel_j}Representing the user proportion of each polymerization degree grade under the load value of the reference control domain; CCE _ Num_{AggregationLevel}Representing the number of CCEs at different aggregation level; RENum _ CCE represents the number of REs in each CCE.

20. The apparatus of claim 18, wherein the first determining module determines the number of schedules of PDCCHs within each radio frame according to:

determining the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene according to the uplink user proportion distribution and the downlink user proportion distribution of various service types and the number of resource blocks required by various services in uplink and downlink in each wireless frame; determining the number of uplink users and the number of downlink users accommodated by various service types according to the number of uplink users and the number of downlink users accommodated by a single cell in a mixed service scene; determining the number of the scheduled users of PDCCH uplink single sub-frames in various services according to the average uplink scheduling times of various service types in a downlink sub-frame and the determined number of uplink users accommodated by various service types, and determining the number of the scheduled users of PDCCH downlink single sub-frames in various services according to the average downlink scheduling times of various service types in a downlink sub-frame and the determined number of downlink users accommodated by various service types; and determining the number of times of dispatching the PDCCH in each radio frame according to the determined number of dispatching users of the PDCCH uplink single sub-frame in various services and the number of dispatching users of the PDCCH downlink single sub-frame in various services.

21. The device of claim 20, wherein the first determination module is further to:

after the number of downlink users accommodated by various service types is determined, if asymmetric services exist in downlink, the downlink user allowance is added with the number of downlink users accommodated by various service types, and the number of downlink users for determining the number of scheduling users of PDCCH downlink single sub-frames in various services is obtained.

22. The apparatus of claim 17, wherein the first determining module determines the resource overhead value of the PHICH within a radio frame according to the following formula:

RE_Num_PerFrame_PHICH

＝Schedule_UserNum_PerSubframe_UL/User_Num_PerGroup_PHICH

*RE_Num_PerGroup_PHICH*Subframe_PerFrame_UL；

wherein RE _ Num _ PerFrame_PHICHRepresenting a resource overhead value of a radio frame PHICH; schedule _ UserNum _ presubframe_ULRepresenting the number of users scheduled on the uplink of each subframe; user _ Num _ per group_PHICHRepresenting the number of multiplexed users in each PHICH group; RE _ Num _ Pergroup_PHICHIndicating the number of REs occupied by each PHICH group; subframe _ PerFrame_ULAnd the number of uplink subframes in each radio frame is shown.

23. The apparatus of claim 17, wherein the first determining module determines the resource overhead value for CRS within a radio frame according to the following equation:

RE_Num_PerFrame_{CRS_In_Control_Domain}

＝RENum_PerRB_PerPortNum_PerSubframe_{CRS_In_Control_Domain}

*RBNum_PerSubframe*Port_Num*Subframe_PerFrame_DL；

wherein RE _ Num _ PerFrame_{CRS_In_Control_Domain}A resource overhead value representing a CRS within a radio frame; RENum _ PerRB _ PerPortNum _ PerSubframe_{CRS_In_Control_Domain}Indicating the number of REs occupied by the CRS in each subframe in each RB port in a control domain; RBNum _ PerSubframe represents the number of RBs contained within the system bandwidth of each subframe; port _ Num represents the number of ports.

24. The apparatus of claim 17, wherein the first determining module determines the resource overhead value for the PCFICH within a radio frame according to the following formula:

RE_Num_PerFrame_PCFICH

＝RENum_PerSubframe_PCFICH*Subframe_PerFrame_DL；

wherein RE _ Num _ PerFrame_PCFICHA resource overhead value representing the PCFICH within one radio frame; RENum _ Persubframe_PCFICHIndicating the number of REs occupied by the PCFICH in one subframe; subframe _ PerFrame_DLAnd the number of downlink subframes in each radio frame is represented.

25. The apparatus of any of claims 14 to 24, wherein the second determining module determines the total number of resources of the control field in the radio frame according to the following formula:

RE_Num_PerFrame_{Total_In_Control_Domain}

＝Subframe_PerFrame_DL*RBNum_PerSubframe

*CFI*SCNum_PerRB；

wherein RE _ Num _ PerFrame_{Total_In_Control_Domain}Represents the total number of resources of the control domain in the radio frame; subframe _ PerFrame_DLRepresenting the number of downlink subframes in each wireless frame; CFI represents the number of OFDM symbols occupied by a control domain in a downlink subframe; SCNum _ perb denotes the number of subcarriers contained in each RB.

26. The device of any one of claims 14 to 24, wherein the second determining module is specifically configured to:

and dividing the determined total resource overhead value by the total resource number of the control domain in the wireless frame to obtain a load value of the control domain.

Images