CN111836265B

CN111836265B - Resource sharing method and device

Info

Publication number: CN111836265B
Application number: CN201910324688.1A
Authority: CN
Inventors: 曾龙基; 许建涛; 陈冬明; 何朗
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-04-22
Filing date: 2019-04-22
Publication date: 2023-04-18
Anticipated expiration: 2039-04-22
Also published as: WO2020215848A1; CN111836265A

Abstract

The application provides a method and a device for resource sharing, wherein the method is suitable for NB-IoT system single-cell PRB resource sharing and comprises the following steps: acquiring PRB release information of a first physical resource module; according to the first PRB release information, releasing the static configuration relation between the first uplink non-anchor PRB and the first downlink non-anchor PRB; selecting an uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a first configuration relation for data transmission; the at least one uplink non-anchor PRB includes a first uplink non-anchor PRB, and the at least one downlink non-anchor PRB includes a first downlink non-anchor PRB. And each uplink non-anchor point PRB and a plurality of downlink non-anchor point PRBs are combined, and each downlink non-anchor point PRB and a plurality of uplink non-anchor point PRBs are combined, so that the NB-IoT system can freely combine the uplink and downlink non-anchor point PRBs according to the configuration requirement, and the light load or no load of PRB resources is avoided, thereby improving the utilization rate of the PRB resources.

Description

Resource sharing method and device

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for resource sharing.

Background

With the rapid development of the internet of things, operators in the world use the internet of things as a key development strategy in order to help the operators quickly seize the market of the internet of things and reuse the LTE network infrastructure. A Narrow-Band Internet of Things (NB-IoT) technology is proposed, and the NB-IoT system technology has the characteristics of low cost, low power consumption, wide coverage, large connection and the like.

In an NB-IoT system, since a deployment bandwidth is 180kHz and is the same as a Physical Resource Block (PRB) bandwidth of an LTE system, for the capacity expansion requirement of the NB-IoT system, the 3GPP standard introduces a Multi-carrier (Multi-PRB) design, and divides PRB types into two types, namely, an Anchor carrier (Anchor PRB) and a Non-Anchor carrier (Non-Anchor PRB). The anchor PRB carries synchronization, broadcast channel and system message transmission, is used for user cell residence, and can also carry access, paging, control and service channels, and is used for user access and data transmission; the non-anchor PRB may carry access, paging, control, and traffic channels for user access and data transmission.

In the deployment scenario of NB-IoT, one cell usually has only one anchor PRB and can carry multiple non-anchor PRBs, and the carrier resource configuration of these NB-IoT is deployed in a static configuration manner, which means that if the carrier resource is occupied by NB-IoT configuration, other systems (e.g. LTE) cannot use it, and for the scenario that the anchor PRB or non-anchor PRB of NB-IoT is deployed in LTE band, such static configuration deployment manner may result in reduction of available LTE resources, and reduce system capacity of LTE.

Disclosure of Invention

In order to overcome the above problem, embodiments of the present application provide a method and apparatus for resource sharing.

In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

in a first aspect, the present application provides a method for resource sharing, where the method is applicable to NB-IoT system single-cell PRB resource sharing, and includes: acquiring PRB release information of a first physical resource module; according to the first PRB release information, releasing the static configuration relation between the first uplink non-anchor PRB and the first downlink non-anchor PRB; selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a first configuration relation for data transmission; the at least one uplink non-anchor PRB comprises the first uplink non-anchor PRB, and the at least one downlink non-anchor PRB comprises the first downlink non-anchor PRB.

In another possible implementation, the removing, according to the first PRB removal information, the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB specifically includes: and releasing the one-to-one configuration relation between the uplink non-anchor PRB and the downlink non-anchor PRB according to the first PRB release information.

In another possible implementation, the canceling the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB according to the first PRB canceling information specifically includes: and releasing the configuration relation that the number of the uplink non-anchor PRBs is equal to the number of the downlink non-anchor PRBs.

In another possible implementation, the selecting an uplink non-anchor PRB that meets an application rule from the at least one uplink non-anchor PRB and a downlink non-anchor PRB that meets the application rule from the at least one downlink non-anchor PRB form a first configuration relationship for data transmission, which includes: selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB and including an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB and including a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein selecting an application-compliant uplink non-anchor PRB from at least one uplink non-anchor PRB comprises selecting an application-compliant uplink non-anchor PRB from the uplink non-anchor PRB resource pool, and selecting an application-compliant downlink non-anchor PRB from at least one downlink non-anchor PRB comprises selecting an application-compliant downlink non-anchor PRB from the downlink non-anchor PRB resource pool.

In another possible implementation, the number of uplink non-anchor PRBs in the first configuration relationship is not equal to the number of downlink non-anchor PRBs.

In another possible implementation, the method includes: selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a second configuration relation for data transmission; wherein the first configuration relationship and the second configuration relationship comprise the same uplink non-anchor PRB or the same downlink non-anchor PRB.

In another possible implementation, the application rule is a light load preference or a channel quality preference rule.

In a second aspect, the present application provides an apparatus for resource sharing, the apparatus being adapted to share NB-IoT system single-cell PRB resources, including: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 1-7.

In a third aspect, the present application provides a resource sharing method, which is applicable to PRB resource sharing of NB-IoT system multi-cells, where the multi-cells include at least a first cell and a second cell, and includes: acquiring second physical resource module PRB release information; according to the second PRB release information, releasing the static configuration relation and the first fixed configuration relation between the second uplink non-anchor PRB and the second downlink non-anchor PRB; the first fixed configuration relation refers to the resource attribute of non-anchor PRB fixed configuration to the cell; selecting an uplink non-anchor PRB which accords with the application rule from at least one uplink non-anchor PRB, and selecting the downlink non-anchor PRB which accords with the application rule from at least one downlink non-anchor PRB to form a third configuration relation for data transmission; the at least one uplink non-anchor PRB comprises the second uplink non-anchor PRB, and the at least one downlink non-anchor PRB comprises the second downlink non-anchor PRB, wherein at least one uplink non-anchor PRB of the uplink non-anchor PRBs that conforms to the application rule belongs to one of the first cell and the second cell, and at least one downlink non-anchor PRB of the downlink non-anchor PRBs that conforms to the application rule belongs to the other of the first cell and the second cell.

In another possible implementation, the removing, according to the second PRB removal information, the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB specifically includes: and releasing the one-to-one configuration relationship between the uplink non-anchor PRBs and the downlink non-anchor PRBs in each cell and the fixed configuration relationship for releasing the non-anchor PRB resource attributes of each cell according to the second PRB release information.

In another possible implementation, the canceling the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB according to the second PRB canceling information specifically includes: and releasing the configuration relationship that the number of the uplink non-anchor PRBs in each cell is equal to that of the downlink non-anchor PRBs and the fixed configuration relationship that the non-anchor PRB resource attributes of each cell are released according to the second PRB release information.

In another possible implementation, the selecting an uplink non-anchor PRB meeting an application rule from the at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB form a third configuration relationship for data transmission, which specifically includes: selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB and including an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB and including a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein selecting an application-compliant uplink non-anchor PRB from at least one uplink non-anchor PRB comprises selecting an application-compliant uplink non-anchor PRB from the uplink non-anchor PRB resource pool, and selecting an application-compliant downlink non-anchor PRB from at least one downlink non-anchor PRB comprises selecting an application-compliant downlink non-anchor PRB from the downlink non-anchor PRB resource pool.

In another possible implementation, the number of uplink non-anchor PRBs in the third configuration relationship is not equal to the number of downlink non-anchor PRBs.

In another possible implementation, the method includes: selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a fourth configuration relation for data transmission; wherein the third configuration relationship and the fourth configuration relationship include the same uplink non-anchor PRB or the same downlink non-anchor PRB.

In a fourth aspect, the present application provides an apparatus for resource sharing, which is adapted to PRB resource sharing for NB-IoT system multi-cells, where the multi-cells include at least a first cell and a second cell, and includes: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 9-14.

In a fifth aspect, the present application provides a method for resource sharing, the method is applicable to PRB resource sharing across systems, where the cross systems at least include an NB-IoT system and a second system, and includes: acquiring PRB release information of a third physical resource module; according to the third PRB release information, releasing the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB; the second fixed configuration relation refers to the resource attribute of the non-anchor PRB fixedly configured to the cell and the resource attribute of the non-anchor PRB fixedly configured to the system; selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a fifth configuration relation for data transmission; the at least one uplink non-anchor PRB comprises the third uplink non-anchor PRB, the at least one downlink non-anchor PRB comprises the third downlink non-anchor PRB, wherein at least one uplink non-anchor PRB in the uplink non-anchor PRB that conforms to the application rule belongs to one of the NB-IoT system and the second system, and at least one downlink non-anchor PRB in the downlink non-anchor PRB that conforms to the application rule belongs to the other of the NB-IoT system and the second system.

In another possible implementation, the canceling, according to the third PRB canceling information, the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB specifically includes: and releasing the one-to-one configuration relationship between the uplink non-anchor PRBs and the downlink non-anchor PRBs in each cell in each system according to the third PRB release information, and releasing the fixed configuration relationship of the non-anchor PRB resource attributes of each cell and the fixed configuration relationship of the non-anchor PRB resource attributes of each system.

In another possible implementation, the canceling, according to the third PRB canceling information, the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB specifically includes: and according to the third PRB release information, releasing the configuration relationship that the number of the uplink non-anchor PRBs in each cell in each system is equal to the number of the downlink non-anchor PRBs, and releasing the fixed configuration relationship of the non-anchor PRB resource attributes of each cell and the fixed configuration relationship of the non-anchor PRB resource attributes of each system.

In another possible implementation, the selecting an uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB form a fifth configuration relationship for data transmission, which specifically includes: selecting an uplink non-anchor PRB which accords with an application rule from at least one uplink non-anchor PRB and comprises an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB; selecting a downlink non-anchor PRB which accords with an application rule from at least one downlink non-anchor PRB and comprises a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein selecting an application-compliant uplink non-anchor PRB from at least one uplink non-anchor PRB comprises selecting an application-compliant uplink non-anchor PRB from the uplink non-anchor PRB resource pool, and selecting an application-compliant downlink non-anchor PRB from at least one downlink non-anchor PRB comprises selecting an application-compliant downlink non-anchor PRB from the downlink non-anchor PRB resource pool.

In another possible implementation, the number of uplink non-anchor PRBs in the fourth configuration relationship is not equal to the number of downlink non-anchor PRBs.

In another possible implementation, the method includes: selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a sixth configuration relation for data transmission; wherein the fifth configuration relationship and the sixth configuration relationship comprise the same uplink non-anchor PRB or the same downlink non-anchor PRB.

In another possible implementation, the method further comprises: setting the NB-IoT system and the second system to share a PRB resource pool; receiving system information reported by the NB-IoT system and the second system; performing intersystem negotiation according to the system information, and determining the use attribute of the shared PRB resource in the shared PRB resource pool in a subsequent period of time; the NB-IoT system and the second system perform data transmission according to the usage attributes of the shared PRB.

In another possible implementation, the performing inter-system negotiation according to the system information to determine a usage attribute of the shared PRB resources in the shared PRB resource pool in a subsequent period further includes: when reporting the system information of the NB-IoT system and the second system, starting a timer to time, and judging whether the time measured by the timer exceeds a set threshold value; and when the time measured by the timer exceeds the set threshold value, re-receiving the system information reported by the NB-IoT system and the second system.

In a sixth aspect, the present application provides an apparatus for resource sharing, the apparatus being adapted to perform PRB resource sharing across systems, where the cross systems at least include an NB-IoT system and a second system, and the apparatus includes: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 16-23.

According to the resource sharing method applicable to the resource sharing of the single-cell PRB of the NB-IoT system, by removing the static configuration relation between the uplink and downlink non-anchor PRBs, each uplink non-anchor PRB can be combined with a plurality of downlink non-anchor PRBs, each downlink non-anchor PRB can be combined with a plurality of uplink non-anchor PRBs, so that the NB-IoT system can freely combine the uplink and downlink non-anchor PRBs according to the configuration requirement, the condition that the PRBs are lightly loaded or unloaded is avoided, and the utilization rate of the PRBs is improved.

Drawings

The drawings that accompany the detailed description can be briefly described as follows.

Fig. 1 is a schematic diagram of an uplink and downlink PRB relationship when PRB resources are configured in a single cell of an NB-IoT system in the prior art;

fig. 2 is a schematic diagram of a NB-IoT system in the prior art employing in-band deployment within the LTE system bandwidth;

fig. 3 is a flowchart of a resource sharing method according to an embodiment of the present application;

fig. 4 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool when an NB-IoT system configures a single-cell PRB resource according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram of NB-IoT system single-cell PRB resource sharing provided in an embodiment of the present application;

fig. 6 is a flowchart of a resource sharing method according to an embodiment of the present application;

fig. 7 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool in multi-cell PRB resource configuration of an NB-IoT system according to an embodiment of the present application;

fig. 8 is a schematic diagram of NB-IoT system multi-cell PRB resource sharing provided in an embodiment of the present application;

fig. 9 is a flowchart of a resource sharing method according to an embodiment of the present application

Fig. 10 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool during cross-system PRB resource configuration provided in an embodiment of the application

Fig. 11 is a flowchart illustrating an NB-IoT system and an LTE system negotiating to share PRB resources in a PRB resource pool according to an embodiment of the present disclosure;

fig. 12 is a schematic diagram of cross-system PRB resource sharing and adaptive adjustment according to an embodiment of the present disclosure;

fig. 13 is a block diagram illustrating a resource sharing apparatus according to an embodiment of the present disclosure;

fig. 14 is a block diagram of a resource sharing apparatus according to an embodiment of the present application;

fig. 15 is a block diagram of a resource sharing apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The basic deployment scenario of the NB-IoT system in the present application includes three ways, namely independent deployment, guardband deployment and in-band deployment, where the guardband deployment and the in-band deployment refer to ways in which the NB-IoT system deploys within a guardband or bandwidth of an inter-system. The heterogeneous systems may include LTE, GSM, UMTS, etc. systems. The embodiment of the present application will take an NB-IoT system as an example to adopt an inband deployment scheme in an LTE system, but the scheme described in the embodiment of the present application is still effective in other deployment manners and other heterogeneous systems.

Fig. 1 is a schematic diagram of an uplink and downlink PRB relationship in PRB resource configuration in a single cell of an NB-IoT system in the prior art. As shown in fig. 1, when PRB resource allocation of an NB-IoT system is performed, conventionally, uplink PRBs and downlink PRBs are configured in pairs, each uplink PRB can only be paired with one downlink PRB, each downlink PRB can only be paired with one uplink PRB, and the number of uplink PRBs is equal to the number of downlink PRBs. For example, when the uplink and downlink PRB resources of the NB-IoT system are not loaded equally, the uplink and downlink PRB resources required by the system are not consistent, so that the uplink or downlink PRB resources may be in a low-load or idle state, and PRB resources may be wasted.

In addition, in the existing PRB resource configuration scheme for multiple cells of an NB-IoT system, a static configuration method is used for PRB resources of each cell, and PRB resources between different cells cannot be used mutually. If the load of the PRB resources among the cells is unbalanced, the cells cannot dynamically call the PRB resources of other cells or borrow the PRB resources to other cells according to the load state, so that the PRB resources are wasted.

Fig. 2 is a diagram illustrating an NB-IoT system employing in-band deployment within an LTE system bandwidth in the prior art. As shown in fig. 2, the PRB resources in each system are configured statically, and the NB-IoT system monopolizes part of the PRB resources of the LTE system according to the configuration. However, after the PRB resources of the LTE system are configured and occupied by the NB-IoT system, no matter whether the PRB resources occupied by the NB-IoT system carry the user traffic, the part of PRB resources cannot be released for the LTE system to use.

Fig. 3 is a flowchart of a resource sharing method according to an embodiment of the present application. As shown in fig. 3, the present application provides a resource sharing method, which is suitable for sharing single cell PRB resources of an NB-IoT system, and the specific implementation steps are as follows:

step S302, obtaining the PRB release information of the first physical resource module.

Specifically, the first PRB release information is used to release the static configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB.

In the deployment scenario of the NB-IoT system, there is usually only one uplink anchor PRB and one downlink anchor PRB in one cell, so it is meaningless to release the static configuration relationship between the uplink anchor PRB and the downlink anchor PRB in the embodiment of the present application.

Step S304, according to the first PRB release information, releasing the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB.

And after the NB-IoT system receives the first PRB release information, the static configuration relation between the uplink non-anchor PRB and the downlink non-anchor PRB resource in the cell of the NB-IoT system is released, namely the one-to-one configuration relation between the uplink non-anchor PRB and the downlink non-anchor PRB is released, and the configuration that the number of the uplink non-anchor PRB and the number of the downlink non-anchor PRB are equal is released. And after the static configuration relation is removed, forming an uplink non-anchor PRB resource pool by all uplink non-anchor PRBs, and forming a downlink non-anchor PRB resource pool by all downlink non-anchor PRBs.

Fig. 4 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool in a single cell PRB resource configuration of an NB-IoT system provided in the embodiment of the present application. As shown in fig. 4, after the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB is released, each uplink non-anchor PRB may be combined with multiple downlink non-anchor PRBs, and each downlink non-anchor PRB may be combined with multiple uplink non-anchor PRBs. Because each non-anchor PRB can be combined with a plurality of non-anchor PRBs, the number of uplink non-anchor PRBs and the number of downlink non-anchor PRBs are not required to be equal to each other by force, and the corresponding number of uplink non-anchor PRBs and downlink non-anchor PRBs can be provided according to the configuration requirement of the NB-IoT system.

It should be noted that, although the static configuration relationship of the non-anchor PRBs is removed, and all the uplink non-anchor PRBs are configured into the uplink non-anchor PRB resource pool and all the downlink non-anchor PRBs are configured into the downlink non-anchor PRB resource pool, the non-anchor PRBs can only be combined with the non-anchor PRBs, but the non-anchor PRBs cannot be combined with the anchor PRBs.

Step S306, selecting the uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and the downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB to form a first configuration relation for data transmission.

Specifically, the application rule is a rule such as a light load priority rule, a channel quality priority rule, or the like. When a user accesses an NB-IoT system and is assigned to a non-anchor PRB, selecting a downlink non-anchor PRB which meets the rules from a downlink non-anchor PRB resource pool according to the principles of light load priority or channel quality priority and the like; and simultaneously, according to the principles of light load priority or channel quality priority and the like, selecting the uplink non-anchor PRBs conforming to the rules from the uplink non-anchor PRBs resource pool, and then combining the downlink non-anchor PRBs and the uplink non-anchor PRBs conforming to the application rules to provide data transmission for the user.

If the load of data transmission is too large, the system can select a light-load PRB from a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, in the NB-IoT system, if a user already performs data transmission on an uplink non-anchor PRB or a downlink non-anchor PRB, the uplink non-anchor PRB or the downlink non-anchor PRB may also perform data transmission for other users.

Preferably, in the present application, the number of the uplink non-anchor PRBs or the downlink non-anchor PRBs providing data transmission for one user may be one. However, if the load of data transmission is too large and one uplink non-anchor PRB or downlink non-anchor PRB cannot provide data transmission, the system may provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, the number of the uplink non-anchor PRBs and the number of the downlink non-anchor PRBs for performing data transmission for the user may not be equal, and the determination is performed according to the load of the data transmission.

According to the resource sharing method applicable to the NB-IoT system single-cell PRB resource sharing, the static configuration relation between the uplink and downlink non-anchor PRBs is removed, each uplink non-anchor PRB can be combined with a plurality of downlink non-anchor PRBs, each downlink non-anchor PRB can be combined with a plurality of uplink non-anchor PRBs, the NB-IoT system can freely combine the uplink and downlink non-anchor PRBs according to the configuration requirement, the condition that the PRB resources are lightly loaded or unloaded is avoided, and the utilization rate of the PRB resources is improved.

Fig. 5 is a schematic diagram of NB-IoT system single-cell PRB resource sharing provided in an embodiment of the present application. As shown in fig. 5, after the non-anchor PRB resources in the non-anchor PRB resource pool of the single cell of the NB-IoT system have been released from the static configuration, the uplink and downlink non-anchor PRBs may be freely combined and assigned, and the uplink and downlink non-anchor PRB data in the cell may be different. In the figure, the number of downlink PRBs is 4, and the number of uplink PRBs is 3; the downlink PRB #1 may be combined with the uplink PRB #1 and the uplink PRB #2, and the downlink PRB #3 may be combined with the uplink PRB #1. After accessing the NB-IoT system for different users a, B, and C, user a may be assigned to uplink PRB #1 and downlink PRB #1, user B may be assigned to uplink PRB #1 and downlink PRB #2, and user C may be assigned to uplink PRB #2 and downlink PRB #1.

Fig. 6 is a flowchart of a resource sharing method according to an embodiment of the present application. As shown in fig. 6, the present application provides a resource sharing method, which is applicable to PRB resource sharing of multiple cells of an NB-IoT system, where the multiple cells at least include a first cell and a second cell, and the specific implementation steps are as follows:

step S602, obtaining second physical resource module PRB release information.

Specifically, the second PRB release information is used to release the static allocation relationship between the uplink PRB and the downlink PRB and to release the PRB resource allocation relationship of each cell.

Step S604, according to the second PRB release information, releasing the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB.

Specifically, the first fixed configuration relationship refers to a resource attribute of the non-anchor PRB fixed configuration to the cell. That is, after the base station allocates the non-anchor PRB resources to each cell, the non-anchor PRB resources can only provide data transmission for users in the cell corresponding to the non-anchor PRB resources, but cannot provide data transmission for users outside the cell corresponding to the non-anchor PRB resources.

For anchor point PRB resources of each cell of an NB-IoT system, according to a 3GPP protocol, a physical cell of the NB-IoT system and an anchor point PRB are required to be in a one-to-one corresponding relationship, and an uplink anchor point PRB and a downlink anchor point PRB are also in a one-to-one corresponding relationship, so that pairing of the uplink PRB and the downlink PRB cannot be performed in a pairwise combination manner like a non-anchor point PRB. Therefore, the static configuration relation and the fixed configuration relation of the anchor point PRB resources are not solved.

For the non-anchor-point PRB resources of each cell of the NB-IoT system, after the NB-IoT system receives the second PRB release information, the NB-IoT system firstly releases the static configuration relationship of the non-anchor-point PRB resources in each cell, namely releases the one-to-one configuration relationship between the uplink non-anchor-point PRB and the downlink non-anchor-point PRB, and releases the configuration that the number of the uplink non-anchor-point PRB and the number of the downlink non-anchor-point PRB must be equal. And then releasing the fixed configuration relation of the non-anchor point PRB resources of each cell, so that the uplink non-anchor point PRBs of all the cells form an uplink non-anchor point PRB resource pool, and the downlink non-anchor point PRBs of all the cells form a downlink non-anchor point PRB resource pool.

Fig. 7 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool in multi-cell PRB resource configuration of an NB-IoT system according to an embodiment of the present application. As shown in fig. 7, after the uplink non-anchor PRB resource pool and the downlink non-anchor PRB resource pool are formed, each uplink non-anchor PRB may be combined with downlink non-anchor PRBs of multiple arbitrary cells, and each downlink non-anchor PRB may be combined with uplink non-anchor PRBs of multiple arbitrary cells. Non-anchor PRB resources of multiple cells form a non-anchor PRB resource pool, so that the non-anchor PRB resources in each physical cell are shared and multiplexed.

These physical cells can be logically defined as one NB-IoT super cell, and by constructing the NB-IoT super cell, the available channel resources (e.g., NPRACH channel resources) of the NB-IoT system can be extended and better real-time resource deployment can be facilitated.

Step S606, selecting the uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and selecting the downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB to form a third configuration relationship for data transmission.

Wherein, the application rule is the rule of light load priority, channel quality priority and the like. When a user accesses an NB-IoT system and is assigned to a non-anchor PRB, selecting a downlink non-anchor PRB which meets the rules from a downlink non-anchor PRB resource pool according to the principles of light load priority or channel quality priority and the like; and simultaneously, according to the principles of light load priority or channel quality priority and the like, selecting the uplink non-anchor PRB which accords with the rule from the uplink non-anchor PRB resource pool, and then combining the downlink non-anchor PRB and the uplink non-anchor PRB which accord with the application rule to provide data transmission for the user.

If the load of data transmission is too large, the system can select a lightly loaded PRB from a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, in the NB-IoT system, if a user already performs data transmission on an uplink non-anchor PRB or a downlink non-anchor PRB, the uplink non-anchor PRB or the downlink non-anchor PRB may also perform data transmission for other users.

The uplink non-anchor PRB and the downlink non-anchor PRB which provide data transmission for the user come from different cells. If a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs provide data transmission for users, part of the uplink non-anchor PRBs and part of the downlink non-anchor PRBs may be from the same cell.

According to the resource sharing method applicable to the NB-IoT system multi-cell PRB resource sharing, the static configuration relation between the uplink and downlink non-anchor PRB resources in each cell of the NB-IoT system is removed, the fixed configuration relation of the non-anchor PRB resources between the cells is removed, each uplink non-anchor PRB can be combined with the downlink non-anchor PRBs of a plurality of any cells, each downlink non-anchor PRB can be combined with the uplink non-anchor PRBs of the plurality of any cells, each cell can dynamically call the non-anchor PRB resources of other cells or borrow the non-anchor PRB resources to the other cells according to the load state, and the waste of the PRB resources is avoided. In addition, by constructing the NB-IoT system super cell, the base station can realize the scheduling of the cross-physical cell in the frame of the NB-IoT system super cell, which is beneficial to improving the utilization rate of resources.

Fig. 8 is a schematic diagram of NB-IoT system multi-cell PRB resource sharing provided in the embodiment of the present application. As shown in fig. 8, after the non-anchor PRB resources in the NB-IoT system multi-cell PRB resource pool have been released from the static configuration and the static configuration relationship of the non-anchor PRB resources in each cell is released, the uplink and downlink non-anchor PRB resources of any cell can be freely combined and assigned. Cell #0 and cell #1 are shown; the number of the downlink non-anchor PRBs in the cell #0 is 3, the number of the uplink non-anchor PRBs is 2, and the number of the uplink non-anchor PRBs and the number of the downlink non-anchor PRBs in the cell #1 are 1; wherein the uplink PRB #1 in the cell #0 can be combined with the downlink PRB #3 in the cell #0 and the downlink PRB #1 in the cell #1, the uplink PRB #2 in the cell #0 can be combined with the downlink PRB #1 in the cell #0, and the uplink PRB #1 in the cell #1 can be combined with the downlink PRB #2 in the cell # 0. After different users a, B, C and D access the NB-IoT system through different cells, the user a may be assigned to the uplink PRB #1 of the cell #0 and the downlink PRB #1 of the cell #1, the user B may be assigned to the uplink PRB #1 of the cell #0 and the downlink PRB #3 of the cell #0, the user C may be assigned to the uplink PRB #2 of the cell #0 and the downlink PRB #1 of the cell #0, and the user D may be assigned to the uplink PRB #1 of the cell #1 and the downlink PRB #2 of the cell # 0.

Fig. 9 is a flowchart of a resource sharing method according to an embodiment of the present application. As shown in fig. 9, the present application provides a resource sharing method, which is suitable for across-system PRB resource sharing, and the specific implementation steps are as follows:

step S902, obtaining third physical resource module PRB release information.

Specifically, the third PRB release information is used to release the static allocation relationship between the uplink PRB and the downlink PRB, release the PRB resource fixed allocation relationship of each cell, and release the PRB resource fixed allocation relationship of each system.

Step S904, according to the third PRB release information, releasing the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB.

Specifically, the second fixed configuration relationship refers to the resource attribute of the non-anchor PRB fixed configuration to the cell and the resource attribute of the non-anchor PRB fixed configuration to the system. That is, after the base station allocates the non-anchor PRB resources to each cell, the non-anchor PRB resources can only provide data transmission for its corresponding cell users, but cannot provide data transmission for users outside its corresponding cell; similarly, after the base station allocates the non-anchor-point PRB resources to each system, the non-anchor-point PRB resources intelligently provide data transmission for the system users corresponding to the non-anchor-point PRB resources, and cannot provide data transmission for users other than the system corresponding to the non-anchor-point PRB resources.

For the anchor point PRB resources of each cell of the NB-IoT system, the system and the anchor point PRB are required to be in one-to-one correspondence, and the uplink anchor point PRB and the downlink anchor point PRB are also in one-to-one correspondence, so that the static configuration relationship and the fixed configuration relationship between the anchor point PRBs are not released in the application.

For the non-anchor PRB resources of each cell of each system, after each system receives the third PRB release information, it first releases the static configuration relationship of the non-anchor PRB resources in each cell, i.e. releases the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB, and releases the configuration that the number of uplink non-anchor PRBs and the number of downlink non-anchor PRBs must be equal. Then, the fixed configuration relation of the non-anchor point PRB resources among all the cells is released, so that the uplink and downlink non-anchor point PRB resources of all the cells in the same system can be freely combined in pairs. And then, the fixed configuration relation of the non-anchor point PRB resources among all the systems is released, so that the uplink non-anchor point PRBs of all the cells in all the systems form an uplink non-anchor point PRB resource pool, and the downlink non-anchor point PRBs of all the cells in all the systems form a downlink non-anchor point PRB resource pool.

Fig. 10 is a schematic diagram of an uplink PRB resource pool and a downlink PRB resource pool in cross-system PRB resource configuration provided in the embodiment of the present application. As shown in fig. 10, after the anchor PRB resource pool is constructed, the anchor PRB resources in each cell and each system are not configured across cells and systems, and they still follow the previous static configuration relationship. After the uplink non-anchor PRB resource pool and the downlink non-anchor PRB resource pool are formed, each uplink non-anchor PRB may be combined with multiple downlink non-anchor PRBs in the same cell or different cells, or may be combined with multiple downlink non-anchor PRBs in the same system or different systems (in the figure, a non-anchor PRB in an NB-IoT super cell and a non-anchor PRB in an LTE cell are not shown in order to avoid the figure being too complicated). Similarly, each downlink non-anchor PRB may be combined with an uplink non-anchor PRB in the same cell or different cells, or may be combined with an uplink non-anchor PRB in the same system or different systems. Non-anchor-point PRB resources in each cell and each system form a non-anchor-point PRB resource pool, so that the non-anchor-point PRB resources in each system can share and multiplex.

Preferably, the method can make the shared non-anchor-point PRBs in each cell and each system form an uplink non-anchor-point shared PRB resource pool and a downlink non-anchor-point shared PRB resource pool, then set a use attribute for each non-anchor-point PRB, and each system selects the corresponding shared non-anchor-point PRB for providing data transmission for the system according to the use attribute.

Step S906, selecting an uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB to form a fifth configuration relationship for data transmission.

Wherein, the application rule is the rule of light load priority, channel quality priority and the like. When a user accesses an NB-IoT system and is assigned to a non-anchor PRB, selecting a downlink non-anchor PRB conforming to a rule from a downlink non-anchor PRB resource pool according to the principles of light load priority or channel quality priority and the like; and simultaneously, according to the principles of light load priority or channel quality priority and the like, selecting the uplink non-anchor PRBs conforming to the rules from the uplink non-anchor PRBs resource pool, and then combining the downlink non-anchor PRBs and the uplink non-anchor PRBs conforming to the application rules to provide data transmission for the user.

Preferably, in the present application, the number of the uplink non-anchor PRBs or the downlink non-anchor PRBs providing data transmission for one user may be one. However, if the load of data transmission is too large and one uplink non-anchor PRB or downlink non-anchor PRB cannot provide data transmission, the system may provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, the number of uplink non-anchor PRBs and the number of downlink non-anchor PRBs for data transmission of a user may not be equal, and are determined according to the load of data transmission.

The uplink non-anchor PRB and the downlink non-anchor PRB which provide data transmission for users come from different systems. If a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs provide data transmission for users, part of the uplink non-anchor PRBs and part of the downlink non-anchor PRBs may come from the same system.

According to the resource sharing method applicable to the resource sharing of the cross-system PRB resource, the static configuration relation between the uplink and downlink non-anchor PRBs of each cell of each system is removed, the non-anchor PRB resource configuration relation between the cells is removed, and the non-anchor PRB resource configuration relation between the systems is removed, so that each uplink non-anchor PRB can be combined with the downlink non-anchor PRBs of any cells of a plurality of any systems, each downlink non-anchor PRB can be combined with the uplink non-anchor PRBs of any cells of the plurality of any systems, each cell of each anchor can dynamically call the PRB resources of other systems or borrow the PRB resources to other systems according to the load state, and the waste of the PRB resources is avoided.

After the NB-IoT system calls or occupies the non-anchor PRB resources of the LTE system, the base station needs to adjust the conditions of the non-anchor PRB resources occupied by the NB-IoT system and the LTE system after the non-anchor PRB resources occupied by the NB-IoT system and the LTE system change with the passage of time.

Fig. 11 is a flowchart of an NB-IoT system and an LTE system negotiating for PRB resources in a shared PRB resource pool according to an embodiment of the present application. As shown in fig. 11, in the embodiment of the present application, taking the in-band deployment of PRB resources of an NB-IoT system on a PRB bandwidth of an LTE system as an example, a specific implementation process is as follows:

step S1102 is to set a shared PRB resource pool in the LTE system band, where the shared PRB resource pool allows the NB-IoT system to share with the LTE system.

According to the resource sharing method and device, based on a resource sharing mechanism of a cross-system PRB resource pool, the attribute shared by an NB-IoT system and an LTE system is set for in-band PRB resources of a part of LTE systems, namely, non-anchor-point PRBs used for sharing in each system form a non-anchor-point shared PRB resource pool. The shared PRB resource pool allows the NB-IoT system and the LTE system to share and use in a time sharing way, and the usage attribution of the shared PRB in the subsequent period of time is adaptively adjusted based on a cross-system negotiation mechanism.

And step S1104, the NB-IoT system and the LTE system report respective system information to the base station.

The system information refers to information such as the load of PRB resources in the system and channel quality.

Step S1106, after receiving the system information reported by the two systems, the base station performs inter-system negotiation according to the system information, and determines the usage attribute of the shared PRB resources in the shared PRB resource pool in the following period of time.

If the use attribute of the shared non-anchor PRB is used by the NB-IoT system, the NB-IoT system calls the non-anchor PRB resource to perform data transmission; and if the use attribute of the shared non-anchor PRB is used by the LTE system, the LTE system calls the non-anchor PRB resource to carry out data transmission. In one embodiment, if the system information reported by the NB-IoT system indicates that the load of the PRB resources is large, the idle shared non-anchor PRB resources in the shared PRB resource pool are set as the usage attributes used by the NB-IoT system according to the inter-system negotiation, so that the subsequent NB-IoT system can call the non-anchor PRB resources to perform data transmission.

Step S1108, when the system information of the NB-IoT system and the LTE system is reported, a timer is started to time.

The timer is used for detecting the time for reporting the system information of the NB-IoT system and the LTE system, and setting a threshold, wherein the threshold is the timing length. And if the time of the reported system information exceeds the set threshold value, the base station is informed to receive the reported system information of the NB-IoT system and the LTE system again, and the time of the timer is reset at the same time. Therefore, the base station is ensured to report the system information by continuously receiving the NB-IoT system and the LTE system, and the use attribution of the shared PRB is changed in real time.

In step S1110, it is determined whether the time measured by the timer exceeds a set threshold.

If the system information exceeds the set threshold value, the system information reported by the NB-IoT system and the LTE system is received again; if the threshold value is not exceeded, step S1112 is executed.

Step S1112, according to the usage attribute of the shared PRB, the NB-IoT system and the LTE system call the PRB resources with the corresponding usage attribute to perform data transmission.

According to the method and the device, the attributes of the shared PRB of the NB-IoT system and the LTE system in a follow-up period are adaptively adjusted to be used for sharing the PRB based on the cross-system PRB resource pool through a cross-system negotiation mechanism, the resource sharing and using are realized in a mode of adaptively adjusting the usage attribution of the shared PRB, and the resource utilization efficiency of the whole system is improved.

Fig. 12 is a schematic diagram of cross-system PRB resource sharing and adaptive adjustment provided in the embodiment of the present application. As shown in fig. 12, the non-anchor PRBs of the NB-IoT system are deployed in-band of the LTE system, the NB-IoT system and the LTE system are allowed to share time and use shared by using time and shared PRBs based on a sharing mechanism of a cross-system PRB resource pool by setting part of PRB resources in-band of the LTE system as an attribute shared by the NB-IoT system and the LTE system, and the usage attribution of shared PRBs in a subsequent period of time is adaptively adjusted based on a negotiation mechanism of the cross-system. The base station can dynamically adjust the use attribution of each PRB in the shared region according to the load change of the NB-IoT system and the LTE system, and schedulers of the NB-IoT system and the LTE system can allocate scheduling resources to different users according to the attribution of the shared PRBs.

Fig. 13 is a block diagram of a resource sharing apparatus according to an embodiment of the present application. As shown in fig. 13, the present application provides a resource sharing apparatus 1300, where the apparatus 1300 is suitable for NB-IoT system single-cell PRB resource sharing, and includes a first obtaining unit 1301, a first processing unit 1302, and a first generating unit 1303.

The first obtaining unit 1301 is configured to obtain PRB release information of the first physical resource module.

The first PRB release information is used for releasing the static configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB.

It should be noted that in a deployment scenario of an NB-IoT system, generally, one cell only has one uplink anchor PRB and one downlink anchor PRB, so it is meaningless to release the static configuration relationship between the uplink anchor PRB and the downlink anchor PRB in the embodiment of the present application.

The first processing unit 1302 is configured to release the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB according to the first PRB release information.

Specifically, after the NB-IoT system receives the first PRB release information, the NB-IoT system releases the static configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB resources in the NB-IoT system cell, that is, releases the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB, and releases the configuration that the number of the uplink non-anchor PRB and the number of the downlink non-anchor PRB must be equal. And after the static configuration relation is removed, forming an uplink non-anchor PRB resource pool by all uplink non-anchor PRBs, and forming a downlink non-anchor PRB resource pool by all downlink non-anchor PRBs.

It should be noted that, although the static configuration relationship of the non-anchor PRBs is removed, and all uplink non-anchor PRBs are configured into an uplink non-anchor PRB resource pool and all downlink non-anchor PRBs are configured into a downlink non-anchor PRB resource pool, the non-anchor PRBs can only be combined with the non-anchor PRBs, but the non-anchor PRBs cannot be combined with the anchor PRBs.

The first generating unit 1303 is configured to select an uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and form a first configuration relationship with a downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB for data transmission.

Preferably, the number of the uplink non-anchor PRBs or the downlink non-anchor PRBs providing data transmission for one user in the present application may be one. However, if the load of data transmission is too large and one uplink non-anchor PRB or downlink non-anchor PRB cannot provide data transmission, the system may provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, in the NB-IoT system, if the load that a user needs to perform data transmission is smaller than the load of an uplink non-anchor PRB or a downlink non-anchor PRB, the uplink non-anchor PRB or the downlink non-anchor PRB may also perform data transmission for other users.

According to the resource sharing device applicable to the resource sharing of the single-cell PRB resource of the NB-IoT system, each uplink non-anchor PRB can be combined with a plurality of downlink non-anchor PRBs, each downlink non-anchor PRB can be combined with a plurality of uplink non-anchor PRBs, so that the NB-IoT system can freely combine the uplink non-anchor PRBs and the downlink non-anchor PRBs according to the configuration requirement, the condition that the PRB resource is lightly loaded or unloaded is avoided, and the utilization rate of the PRB resource is improved.

Fig. 14 is a block diagram of a resource sharing apparatus according to an embodiment of the present application. As shown in fig. 14, the present application provides a resource sharing apparatus 1400, the apparatus 1400 is suitable for PRB resource sharing of NB-IoT system multi-cell, and includes a second obtaining unit 1401, a second processing unit 1402 and a second generating unit 1403.

The second acquiring unit 1401 is configured to acquire second physical resource block PRB release information.

The second PRB release information is used to release the static allocation relationship between the uplink PRB and the downlink PRB and to release the PRB resource allocation relationship of each cell.

The second processing unit 1402 is configured to release the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB according to the second PRB release information.

For anchor point PRB resources of each cell of an NB-IoT system, according to a 3GPP protocol, a physical cell of the NB-IoT system and an anchor point PRB are required to be in a one-to-one corresponding relationship, and an uplink anchor point PRB and a downlink anchor point PRB are also in a one-to-one corresponding relationship, so that pairing of the uplink PRB and the downlink PRB cannot be performed in a pairwise combination manner like a non-anchor point PRB. Therefore, the static configuration relation and the fixed configuration relation of the anchor PRB resources are not solved.

For the non-anchor-point PRB resources of each cell of the NB-IoT system, after the NB-IoT system receives the second PRB release information, the NB-IoT system firstly releases the static configuration relationship of the non-anchor-point PRB resources in each cell, namely releases the one-to-one configuration relationship between the uplink non-anchor-point PRB and the downlink non-anchor-point PRB, and releases the configuration that the number of the uplink non-anchor-point PRB and the number of the downlink non-anchor-point PRB must be equal. Then, the fixed configuration relation of the non-anchor point PRB resources of each cell is released, so that the uplink non-anchor point PRBs of all the cells form an uplink non-anchor point PRB resource pool, and the downlink non-anchor point PRBs of all the cells form a downlink non-anchor point PRB resource pool.

The second generating unit 1403 is configured to select an uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and select a downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB to form a third configuration relationship for data transmission.

Preferably, in the present application, the number of the uplink non-anchor PRBs or the downlink non-anchor PRBs providing data transmission for one user may be one. However, if the load of data transmission is too large and one uplink non-anchor PRB or downlink non-anchor PRB cannot provide data transmission, the system may provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for the user. In addition, in the NB-IoT system, if the load that a user needs to perform data transmission is smaller than the load of an uplink non-anchor PRB or a downlink non-anchor PRB, the uplink non-anchor PRB or the downlink non-anchor PRB may also perform data transmission for other users.

It should be noted that the uplink non-anchor PRB and the downlink non-anchor PRB providing data transmission for the user come from different cells. If a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs provide data transmission for users, part of the uplink non-anchor PRBs and part of the downlink non-anchor PRBs may come from the same cell.

According to the resource sharing device applicable to the resource sharing of the multi-cell PRB resource of the NB-IoT system, each uplink non-anchor PRB can be combined with downlink non-anchor PRBs of a plurality of arbitrary cells, and each downlink non-anchor PRB can be combined with the uplink non-anchor PRBs of the plurality of arbitrary cells, so that each cell can dynamically call the non-anchor PRB resources of other cells or borrow the non-anchor PRB resources to other cells according to the load state, and the waste of the PRB resources is avoided.

Fig. 15 is a block diagram of a resource sharing apparatus according to an embodiment of the present application. As shown in fig. 15, the present application provides a resource sharing apparatus 1500, and the apparatus 1500 is adapted to across-system PRB resource sharing and includes a third acquisition unit 1501, a third processing unit 1502, and a third generation unit 1503.

The third acquiring unit 1501 is configured to acquire third physical resource module PRB release information.

The third PRB release information is used to release the static allocation relationship between the uplink PRB and the downlink PRB, release the PRB resource fixed allocation relationship of each cell, and release the PRB resource fixed allocation relationship of each system.

Third processing unit 1502 is configured to release the static allocation relationship and the second fixed allocation relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB according to the third PRB release information.

For anchor point PRB resources of each cell of the NB-IoT system, the system and the anchor point PRBs are required to be in one-to-one correspondence, and the uplink anchor point PRBs and the downlink anchor point PRBs are also in one-to-one correspondence, so that the static configuration relationship and the fixed configuration relationship between the anchor point PRBs are not removed.

The third generating unit 1503 is configured to select an uplink non-anchor PRB compliant with the application rule from the at least one uplink non-anchor PRB and select a downlink non-anchor PRB compliant with the application rule from the at least one downlink non-anchor PRB to form a fifth configuration relationship for data transmission.

Wherein, the application rule is the rule of light load priority, channel quality priority and the like. When a user accesses an NB-IoT system and is assigned to a non-anchor PRB, selecting a downlink non-anchor PRB which meets the rules from a downlink non-anchor PRB resource pool according to the principles of light load priority or channel quality priority and the like; and simultaneously, according to the principles of light load priority or channel quality priority and the like, selecting the uplink non-anchor PRBs conforming to the rules from the uplink non-anchor PRBs resource pool, and then combining the downlink non-anchor PRBs and the uplink non-anchor PRBs conforming to the application rules to provide data transmission for the user.

It should be noted that the uplink non-anchor PRB and the downlink non-anchor PRB providing data transmission for the user come from different systems. If a plurality of uplink non-anchor PRBs or downlink non-anchor PRBs provide data transmission for users, part of the uplink non-anchor PRBs and part of the downlink non-anchor PRBs may come from the same system.

According to the resource sharing device applicable to the resource sharing of the cross-system PRB resource, each uplink non-anchor PRB can be combined with the downlink non-anchor PRBs of any cells of any systems, and each downlink non-anchor PRB can be combined with the uplink non-anchor PRBs of any cells of any systems, so that each cell of each system can dynamically call the PRB resources of other systems or borrow the PRB resources to other systems according to the load state, and the waste of the PRB resources is avoided.

After the NB-IoT system calls or occupies the non-anchor PRB resources of the LTE system, and after the non-anchor PRB resources occupied by the NB-IoT system and the LTE system change over time, the base station needs to adjust the non-anchor PRB resource conditions occupied by the NB-IoT system and the LTE system.

The apparatus 1500 further comprises an adjustment unit 1505. The adjusting unit 1505 specifically includes:

the generation subunit 1505A is used to set the NB-IoT system to share the PRB resource pool with the LTE system.

The receiving subunit 1505B is configured to receive system information reported by the NB-IoT system and the LTE system.

The determining subunit 1505C is configured to perform intersystem negotiation according to the system information, and determine a usage attribute of the shared PRB resource in the shared PRB resource pool in a subsequent period of time; and the NB-IoT system and the LTE system carry out data transmission according to the use attribute of the shared PRB.

A time subunit 1505D, configured to start a timer to count time when reporting the system information of the NB-IoT system and the LTE system, and determine whether the time measured by the timer exceeds a set threshold; and when the time measured by the timer exceeds the set threshold value, re-receiving the system information reported by the NB-IoT system and the LTE system.

In the description herein, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.

Finally, the description is as follows: the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present application.

Claims

1. A method for resource sharing, the method being applicable to NB-IoT system single-cell PRB resource sharing, comprising:

acquiring PRB release information of a first physical resource module;

according to the first PRB release information, releasing the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB;

selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a first configuration relation for data transmission; the at least one uplink non-anchor PRB comprises the first uplink non-anchor PRB, and the at least one downlink non-anchor PRB comprises the first downlink non-anchor PRB.

2. The method according to claim 1, wherein the releasing the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB according to the first PRB release information includes:

and releasing the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB according to the first PRB release information.

3. The method according to claim 1, wherein the canceling the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB according to the first PRB canceling information specifically comprises:

and releasing the configuration relation that the number of the uplink non-anchor PRBs is equal to the number of the downlink non-anchor PRBs.

4. The method according to claim 1, wherein the selecting the uplink non-anchor PRB that meets the application rule from the at least one uplink non-anchor PRB and the selecting the downlink non-anchor PRB that meets the application rule from the at least one downlink non-anchor PRB form a first configuration relationship for data transmission, specifically comprising:

selecting an uplink non-anchor PRB which accords with an application rule from at least one uplink non-anchor PRB and comprises an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB which accords with the application rule from at least one downlink non-anchor PRB and comprises a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB;

wherein selecting an application-compliant uplink non-anchor PRB from at least one uplink non-anchor PRB comprises selecting an application-compliant uplink non-anchor PRB from the uplink non-anchor PRB resource pool, and selecting an application-compliant downlink non-anchor PRB from at least one downlink non-anchor PRB comprises selecting an application-compliant downlink non-anchor PRB from the downlink non-anchor PRB resource pool.

5. The method of claim 1, wherein the number of uplink non-anchor PRBs in the first configuration relationship is not equal to the number of downlink non-anchor PRBs.

6. The method according to claim 1, characterized in that it comprises:

selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and selecting any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a second configuration relation for data transmission; wherein the first configuration relationship and the second configuration relationship comprise the same uplink non-anchor PRB or the same downlink non-anchor PRB.

7. The method of claim 1, wherein the application rule is a light load preferred or channel quality preferred rule.

8. An apparatus for resource sharing, the apparatus being adapted for NB-IoT system single cell PRB resource sharing, comprising: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 1-7.

9. A method of resource sharing, the method being adapted for PRB resource sharing of NB-IoT system multi-cells, the multi-cells including at least a first cell and a second cell, comprising:

acquiring second physical resource module PRB release information;

according to the second PRB release information, releasing the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB; the first fixed configuration relation refers to the resource attribute of non-anchor PRB fixed configuration to the cell;

selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a third configuration relation for data transmission; the at least one uplink non-anchor PRB includes the second uplink non-anchor PRB, the at least one downlink non-anchor PRB includes the second downlink non-anchor PRB, wherein at least one uplink non-anchor PRB of the uplink non-anchor PRB that complies with the application rule belongs to one of the first cell and the second cell, and at least one downlink non-anchor PRB of the downlink non-anchor PRB that complies with the application rule belongs to the other of the first cell and the second cell.

10. The method according to claim 9, wherein the canceling, according to the second PRB canceling information, the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB specifically includes:

and releasing the one-to-one configuration relationship between the uplink non-anchor PRBs and the downlink non-anchor PRBs in each cell and the fixed configuration relationship for releasing the non-anchor PRB resource attributes of each cell according to the second PRB release information.

11. The method according to claim 9, wherein the canceling, according to the second PRB canceling information, the static configuration relationship and the first fixed configuration relationship between the second uplink non-anchor PRB and the second downlink non-anchor PRB specifically includes:

and releasing the configuration relationship that the number of the uplink non-anchor PRBs in each cell is equal to that of the downlink non-anchor PRBs and the fixed configuration relationship that the non-anchor PRB resource attributes of each cell are released according to the second PRB release information.

12. The method according to claim 9, wherein the selecting an uplink non-anchor PRB that complies with an application rule from the at least one uplink non-anchor PRB and the selecting a downlink non-anchor PRB that complies with the application rule from the at least one downlink non-anchor PRB form a third configuration relationship for data transmission, comprising:

selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB and including an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB and including a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB;

wherein selecting an uplink non-anchor PRB that complies with an application rule from the at least one uplink non-anchor PRB comprises selecting an uplink non-anchor PRB that complies with the application rule from the uplink non-anchor PRB resource pool, and selecting a downlink non-anchor PRB that complies with the application rule from the at least one downlink non-anchor PRB comprises selecting a downlink non-anchor PRB that complies with the application rule from the downlink non-anchor PRB resource pool.

13. The method of claim 9, wherein the number of uplink non-anchor PRBs in the third configuration relationship is not equal to the number of downlink non-anchor PRBs.

14. The method of claim 9, wherein the method comprises:

selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and selecting any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a fourth configuration relation for data transmission; wherein the third configuration relationship and the fourth configuration relationship include the same uplink non-anchor PRB or the same downlink non-anchor PRB.

15. An apparatus for resource sharing, the apparatus being adapted for PRB resource sharing for NB-IoT system multi-cells, the multi-cells including at least a first cell and a second cell, comprising: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 9-14.

16. A method of resource sharing, the method being adapted for PRB resource sharing across systems, the across systems including at least an NB-IoT system and a second system, the method comprising:

acquiring PRB release information of a third physical resource module;

according to the third PRB release information, releasing the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB; the second fixed configuration relation refers to the resource attribute of fixedly configuring the non-anchor PRB to the cell and the resource attribute of fixedly configuring the non-anchor PRB to the system;

selecting an uplink non-anchor PRB meeting an application rule from at least one uplink non-anchor PRB, and selecting a downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a fifth configuration relation for data transmission; the at least one uplink non-anchor PRB comprises the third uplink non-anchor PRB, the at least one downlink non-anchor PRB comprises the third downlink non-anchor PRB, wherein at least one uplink non-anchor PRB in the uplink non-anchor PRB that conforms to the application rule belongs to one of the NB-IoT system and the second system, and at least one downlink non-anchor PRB in the downlink non-anchor PRB that conforms to the application rule belongs to the other of the NB-IoT system and the second system.

17. The method according to claim 16, wherein the canceling, according to the third PRB canceling information, the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB specifically includes:

and releasing the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB in each cell in each system, the fixed configuration relationship of the non-anchor PRB resource attribute of each cell and the fixed configuration relationship of the non-anchor PRB resource attribute of each system according to the third PRB release information.

18. The method according to claim 16, wherein the canceling, according to the third PRB canceling information, the static configuration relationship and the second fixed configuration relationship between the third uplink non-anchor PRB and the third downlink non-anchor PRB specifically includes:

and according to the third PRB release information, releasing the configuration relationship that the number of the uplink non-anchor PRBs in each cell in each system is equal to the number of the downlink non-anchor PRBs, and releasing the fixed configuration relationship of the non-anchor PRB resource attributes of each cell and the fixed configuration relationship of the non-anchor PRB resource attributes of each system.

19. The method according to claim 16, wherein the selecting the uplink non-anchor PRB meeting the application rule from the at least one uplink non-anchor PRB and the selecting the downlink non-anchor PRB meeting the application rule from the at least one downlink non-anchor PRB form a fifth configuration relationship for data transmission, which specifically includes:

selecting an uplink non-anchor PRB which accords with an application rule from at least one uplink non-anchor PRB and comprises an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB; selecting a downlink non-anchor PRB which accords with an application rule from at least one downlink non-anchor PRB and comprises a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB;

20. The method of claim 16, wherein the number of uplink non-anchor PRBs in the fifth configuration relationship is not equal to the number of downlink non-anchor PRBs.

21. The method of claim 16, wherein the method comprises:

selecting any uplink non-anchor PRB meeting the application rule from at least one uplink non-anchor PRB and selecting any downlink non-anchor PRB meeting the application rule from at least one downlink non-anchor PRB to form a sixth configuration relation for data transmission; wherein the fifth configuration relationship and the sixth configuration relationship comprise the same uplink non-anchor PRB or the same downlink non-anchor PRB.

22. The method of claim 16, further comprising:

setting the NB-IoT system and the second system to share a PRB resource pool;

receiving system information reported by the NB-IoT system and the second system;

performing intersystem negotiation according to the system information, and determining the use attribute of the shared PRB resource in the shared PRB resource pool in a subsequent period of time;

the NB-IoT system and the second system perform data transmission according to the usage attribute of the shared PRB.

23. The method of claim 22, wherein the performing inter-system negotiation according to the system information to determine the usage property of the shared PRB resources in the shared PRB resource pool in a subsequent period of time further comprises:

when reporting the system information of the NB-IoT system and the second system, starting a timer to time, and judging whether the time measured by the timer exceeds a set threshold value;

and when the time measured by the timer exceeds the set threshold value, re-receiving the system information reported by the NB-IoT system and the second system.

24. An apparatus for resource sharing, the apparatus being adapted for PRB resource sharing across systems, the across systems including at least an NB-IoT system and a second system, comprising: a transceiver, a processor, and a memory; the memory stores one or more programs, the one or more programs comprising instructions, which when executed by the apparatus, cause the apparatus to perform the method of any of claims 16-23.