WO2020215848A1

WO2020215848A1 - Resource sharing method and device

Info

Publication number: WO2020215848A1
Application number: PCT/CN2020/073297
Authority: WO
Inventors: 曾龙基; 许建涛; 陈冬明; 何朗
Original assignee: 华为技术有限公司
Priority date: 2019-04-22
Filing date: 2020-01-20
Publication date: 2020-10-29
Also published as: CN111836265B; CN111836265A

Abstract

The present application provides a resource sharing method and device, wherein the method is suitable for single-cell PRB resource sharing in an NB-IoT system, and comprises: acquiring PRB release information of a first physical resource module; and releasing a static configuration relationship between a first uplink non-anchor PRB and a first downlink non-anchor PRB according to the first PRB release information; and selecting an uplink non-anchor PRB conforming to the application rule from at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB conforming to the application rule from at least one downlink non-anchor PRB to form a first configuration relationship for data transmission, wherein the at least one uplink non-anchor PRB includes the first uplink non-anchor PRB, and at least one downlink non-anchor PRB includes the first downlink non-anchor PRB. The combination of each uplink non-anchor PRB and multiple downlink non-anchor PRBs and the combination of each downlink non-anchor PRB and multiple uplink non-anchor PRBs are implemented, such that the NB-IoT system can freely combine the uplink and downlink non-anchors according to the configuration requirements, thereby avoiding light load or empty load of PRB resources, and increasing the utilization rate of the PRB resources.

Description

Method and device for resource sharing

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office on April 22, 2019, the application number is 201910324688.1, the application name is "a method and device for resource sharing", the entire content of which is incorporated into this application by reference in.

Technical field

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

Background technique

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

In the NB-IoT system, the deployment bandwidth is 180kHz, which is the same as a physical resource block (PRB) bandwidth of the LTE system. For the expansion requirements of the NB-IoT system, the 3GPP standard introduces multi-carrier (Multi-PRB). ) Design, and the PRB types are divided into anchor point carriers (Anchor PRB) and non-anchor point carriers (Non-Anchor PRB). Among them, the anchor PRB carries synchronization, broadcast channels and system message transmission, which is used for user cell camping. It can also carry access, paging, control and service channels for user access and data transmission; non-anchor PRB It can carry access, paging, control and service channels for user access and data transmission.

In NB-IoT deployment scenarios, usually a cell has only one anchor PRB and can carry multiple non-anchor PRBs. The carrier resource configuration of these NB-IoT is deployed through static configuration, which means that if the carrier After resources are occupied by NB-IoT configuration, other systems (such as LTE) cannot be used. For scenarios where NB-IoT anchor PRB or non-anchor PRB is deployed in the LTE band, such a static configuration deployment method will cause The available resources of LTE are reduced, reducing the system capacity of LTE.

Utility model content

In order to overcome the aforementioned problems, the embodiments of the present application provide a method and device for resource sharing.

In order to achieve the foregoing objectives, the embodiments of the present application adopt the following technical solutions:

In the first aspect, this application provides a resource sharing method, which is suitable for single-cell PRB resource sharing in an NB-IoT system, and includes: acquiring PRB release information of a first physical resource module; and according to the first PRB release information, Release the static configuration relationship between the first uplink non-anchor PRB and the first downlink non-anchor PRB; select from at least one uplink non-anchor PRB that meets the application rules and from at least one downlink non-anchor PRB The downlink non-anchor PRBs in the PRB that comply with the application rules constitute a first configuration relationship for data transmission; the at least one uplink non-anchor PRB includes the first uplink non-anchor PRB, and the at least one downlink non-anchor PRB The PRB includes the first downlink non-anchor PRB.

In another possible implementation, 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 specifically includes: The PRB release information releases the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB.

In another possible implementation, 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 specifically includes: releasing the uplink non-anchor PRB A configuration relationship in which the number of anchor PRBs is equal to the number of downlink non-anchor PRBs.

In another possible implementation, the uplink non-anchor PRB that meets the application rule is selected from at least one uplink non-anchor PRB and the downlink non-anchor PRB that meets the application rule from the at least one downlink non-anchor PRB Forming the first configuration relationship for data transmission specifically includes: selecting from at least one uplink non-anchor PRB that conforms to the application rule, including an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB , Selecting a downlink non-anchor PRB from at least one downlink non-anchor PRB that conforms to the application rule includes a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein, from at least one uplink non-anchor PRB Selecting an uplink non-anchor PRB that meets the application rule in the above includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool, and selecting from at least one downlink non-anchor PRB that meets the application The regular downlink non-anchor PRB includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.

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

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

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

In a second aspect, this application provides a resource sharing device, which is suitable for single-cell PRB resource sharing in an NB-IoT system, and includes: a transceiver, a processor, and a memory; the memory stores one or more programs, The one or more programs include instructions, which when executed by the device, cause the device to perform the method according to any of claims 1-7.

In the third aspect, this application provides a method for resource sharing, which is suitable for PRB resource sharing of multiple cells in an NB-IoT system. The multiple cells include at least a first cell and a second cell, including: acquiring a second physical Resource module PRB release information; according to the second PRB release information, 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; the first fixed configuration relationship Refers to the resource attributes of the non-anchor PRBs that are fixedly configured to the cell; select the uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and select the uplink non-anchor PRB that meets the application rule from at least one downlink non-anchor PRB The downlink non-anchor PRBs form a third configuration relationship for data transmission; the at least one uplink non-anchor PRB includes the second uplink non-anchor PRB, and the at least one downlink non-anchor PRB includes the second downlink non-anchor PRB. Anchor PRB, wherein at least one of the uplink non-anchor PRBs that comply with the application rule belongs to one of the first cell and the second cell, and the At least one downlink non-anchor PRB in the downlink non-anchor PRB belongs to another cell of the first cell and the second cell.

In another possible implementation, the 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 according to the second PRB release information specifically includes: According to the second PRB release information, release the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB in each cell and release the fixed non-anchor PRB resource attribute of each cell Configuration relationship.

In another possible implementation, the 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 according to the second PRB release information specifically includes: According to the second PRB release information, release the configuration relationship in which the number of uplink non-anchor PRBs in each cell is equal to the number of downlink non-anchor PRBs and release the fixed configuration relationship of the non-anchor PRB resource attributes of each cell .

In another possible implementation, the selection of an uplink non-anchor PRB conforming to an application rule from at least one uplink non-anchor PRB and a downlink non-anchor PRB conforming to the application rule from at least one downlink non-anchor PRB The PRB forms a third configuration relationship for data transmission, which specifically includes: selecting from at least one uplink non-anchor PRB that conforms to the application rule, including uplink non-anchor PRB resources formed by the at least one uplink non-anchor PRB Pool, selecting from at least one downlink non-anchor PRB that conforms to the application rule includes a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein, from at least one uplink non-anchor PRB; Selecting an uplink non-anchor PRB that meets the application rule from the anchor PRB includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool, and selecting from at least one downlink non-anchor PRB that meets The applying the ruled downlink non-anchor PRB includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.

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

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

In a fourth aspect, the present application provides a device for resource sharing, which is suitable for PRB resource sharing of multiple cells in an NB-IoT system. The multiple cells include at least a first cell and a second cell, including: transceivers, processing And a memory; the memory stores one or more programs, the one or more programs include instructions, when the instructions are executed by the device, the device executes any of claims 9-14 The method described in the item.

In a fifth aspect, the present application provides a resource sharing method, which is suitable for cross-system PRB resource sharing. The cross-system includes at least an NB-IoT system and a second system, including: acquiring a third physical resource module PRB Release information; according to the third PRB release information, release 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 relationship refers to non- The anchor PRB is fixedly configured to the resource attribute of the cell and the non-anchor PRB is fixedly configured to the resource attribute of the system; from at least one uplink non-anchor PRB, an uplink non-anchor PRB that meets the application rules is selected and at least one downlink non-anchor is selected Select a downlink non-anchor PRB that meets the application rule from the PRB to form a fifth configuration relationship for data transmission; the at least one uplink non-anchor PRB includes the third uplink non-anchor PRB, and the at least one downlink non-anchor PRB The point PRB includes the third downlink non-anchor PRB, wherein at least one of the uplink non-anchor PRBs that comply with the application rule belongs to one of the NB-IoT system and the second system In the system, at least one of the downlink non-anchor PRBs that comply with the application rule belongs to the other system of the NB-IoT system and the second system.

In another possible implementation, the 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 according to the third PRB release information specifically includes: According to the third PRB release information, release the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB in each cell in each cell, and release the non-anchor point of each cell The fixed configuration relationship of PRB resource attributes and the fixed configuration relationship of releasing the non-anchor PRB resource attributes of each system.

In another possible implementation, the 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 according to the third PRB release information specifically includes: According to the third PRB release information, release the configuration relationship in which the number of uplink non-anchor PRBs in each cell in each system is equal to the number of downlink non-anchor PRBs, and release the non-anchor PRB resources of each cell The fixed configuration relationship of attributes and the fixed configuration relationship of releasing the non-anchor PRB resource attributes of each system.

In another possible implementation, the selection of the uplink non-anchor PRB conforming to the application rule from at least one uplink non-anchor PRB and the selection of the downlink non-anchor PRB conforming to the application rule from the at least one downlink non-anchor PRB are constituted The fifth configuration relationship for data transmission specifically includes: selecting from at least one uplink non-anchor PRB that conforms to the application rule, including an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB; The selection of a downlink non-anchor PRB that meets application rules from at least one downlink non-anchor PRB includes a downlink non-anchor PRB resource pool formed by the at least one downlink non-anchor PRB; wherein, from at least one uplink non-anchor PRB Selecting an uplink non-anchor PRB that meets the application rule includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool, and selecting from at least one downlink non-anchor PRB that meets the application rule The downlink non-anchor PRB includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.

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

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

In another possible implementation, the method further includes: 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; Perform inter-system negotiation according to the system information to determine the usage attributes of the shared PRB resources in the shared PRB resource pool for a subsequent period of time; the NB-IoT system and the second system according to the usage attributes of the shared PRB Perform data transfer.

In another possible implementation, the performing inter-system negotiation according to the system information to determine the usage attributes of the shared PRB resources in the shared PRB resource pool for a subsequent period of time further includes: reporting the NB-IoT When the system and the system information of the second system, a timer is started for timing, and it is determined whether the time measured by the timer exceeds the set threshold; when the time measured by the timer exceeds the set threshold, Re-receiving the system information reported by the NB-IoT system and the second system.

In a sixth aspect, this application provides a resource sharing device, which is suitable for cross-system PRB resource sharing. The cross-system includes at least an NB-IoT system and a second system, including: a transceiver, a processor, and a memory The memory stores one or more programs, the one or more programs include instructions, and when the instructions are executed by the device, the device executes the device according to any of claims 16-23 Methods.

Based on a resource sharing method suitable for single-cell PRB resource sharing in an NB-IoT system provided by the embodiments of this application, the static configuration relationship between the uplink and downlink non-anchor PRBs is released, so that each uplink non-anchor PRB can be Combining with multiple downlink non-anchor PRBs, each downlink non-anchor PRB can be combined with multiple uplink non-anchor PRBs, so that the NB-IoT system can freely combine uplink and downlink non-anchor PRBs according to configuration needs, avoiding light PRB resources Loaded or unloaded, thereby improving the utilization of PRB resources.

Description of the drawings

The following briefly introduces the drawings needed in the description of the embodiments or the prior art.

FIG. 1 is a schematic diagram of the relationship between uplink and downlink PRB during PRB resource configuration in a single cell of an NB-IoT system in the prior art;

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

FIG. 3 is a flowchart of a method for resource sharing provided by an embodiment of the application;

FIG. 4 is a schematic diagram of the uplink and downlink PRB resource pools during single-cell PRB resource configuration of the NB-IoT system provided by an embodiment of the application;

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

FIG. 6 is a flowchart of a method for resource sharing provided by an embodiment of the application;

FIG. 7 is a schematic diagram of uplink and downlink PRB resource pools during multi-cell PRB resource configuration of the NB-IoT system provided by an embodiment of the application;

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

FIG. 9 is a flowchart of a method for resource sharing provided by an embodiment of the application

Figure 10 is a schematic diagram of the uplink and downlink PRB resource pools during cross-system PRB resource configuration provided by an embodiment of the application

FIG. 11 is a flowchart of the NB-IoT system and the LTE system provided by an embodiment of the application negotiating to share PRB resources in the PRB resource pool;

FIG. 12 is a schematic diagram of cross-system PRB resource sharing and adaptive adjustment provided by an embodiment of this application;

FIG. 13 is a structural block diagram of a resource sharing device provided by an embodiment of this application;

FIG. 14 is a structural block diagram of a resource sharing device provided by an embodiment of this application;

FIG. 15 is a structural block diagram of a resource sharing device provided by an embodiment of this application.

Detailed ways

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

The basic deployment scenarios of the NB-IoT system in this application include independent deployment, guard band deployment and in-band deployment. Among them, guard band deployment and in-band deployment indicate that the NB-IoT system is in the guard band or bandwidth of a different system. How to deploy. Different systems may include LTE, GSM, UMTS and other systems. The embodiment of this application will take the in-band deployment solution of the NB-IoT system in the LTE system as an example, but the solution described in the embodiment of this application is still effective under other deployment methods and other different systems.

Figure 1 is a schematic diagram of the relationship between uplink and downlink PRBs during PRB resource allocation in a single cell of an NB-IoT system in the prior art. As shown in Figure 1, in the PRB resource allocation of the NB-IoT system, the traditional approach is that the uplink PRB and the downlink PRB are configured in pairs. Each uplink PRB can only be paired with one downlink PRB, and each downlink PRB It can only be paired with one uplink PRB, and the number of uplink PRBs is equal to the number of downlink PRBs. This static configuration method has many disadvantages. For example, when the uplink and downlink PRB resources of the NB-IoT system are unbalanced, the uplink and downlink PRB resources required by the system are inconsistent, which causes the uplink or downlink PRB resources to be under load or empty. The status of loading will cause a waste of PRB resources.

In addition, in the existing NB-IoT system multi-cell PRB resource configuration scheme, the PRB resource of each cell adopts a static configuration method, and the PRB resources between different cells cannot be used mutually. If the load of the PRB resources among the cells is not balanced, each cell cannot dynamically call the PRB resources of other cells or second the PRB resources to other cells according to the load status, which will also cause a waste of PRB resources.

Figure 2 is a schematic diagram of the NB-IoT system in the prior art adopting in-band deployment within the LTE system bandwidth. As shown in Figure 2, the PRB resources in each system adopt a static configuration method, and the NB-IoT system will exclusively occupy a part of the PRB resources of the LTE system according to the configuration. However, when the PRB resources of the LTE system are occupied by the NB-IoT system configuration, regardless of whether the PRB resources occupied by the NB-IoT system carry user services, these PRB resources cannot be released for use by the LTE system.

Fig. 3 is a flowchart of a resource sharing method provided by an embodiment of the application. As shown in Figure 3, this application provides a resource sharing method, which is suitable for single-cell PRB resource sharing in an NB-IoT system. The specific implementation steps are as follows:

Step S302: Acquire 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.

Among them, in the deployment scenario of the NB-IoT system, usually a cell has only one uplink anchor PRB and downlink anchor PRB, so in the embodiment of this application, the static configuration relationship between the uplink anchor PRB and the downlink anchor PRB is meaningless.

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

After receiving the first PRB release information, the NB-IoT system releases the static configuration relationship between the uplink non-anchor PRB and downlink non-anchor PRB resources in the NB-IoT system cell, that is, releases the uplink non-anchor PRB and downlink non-anchor PRB resources. The one-to-one configuration relationship between anchor PRBs, and the configuration that the number of uplink non-anchor PRBs and the number of downlink non-anchor PRBs must be equal. After the static configuration relationship is released, all the uplink non-anchor PRBs form an uplink non-anchor PRB resource pool, and all the downlink non-anchor PRBs form a downlink non-anchor PRB resource pool.

Fig. 4 is a schematic diagram of the uplink and downlink PRB resource pools during single-cell PRB resource configuration of the NB-IoT system provided by an embodiment of the application. As shown in Figure 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 can be combined with multiple downlink non-anchor PRBs. The non-anchor PRB can be combined with multiple uplink non-anchor PRBs. Since each non-anchor PRB can be combined with multiple non-anchor PRBs, there is no need to force the number of uplink non-anchor PRBs to be equal to the number of downlink non-anchor PRBs. The corresponding number can be provided according to the requirements of the NB-IoT system configuration. Uplink non-anchor PRB and downlink non-anchor PRB.

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

Step S306: Select an uplink non-anchor PRB that meets the application rule from the at least one uplink non-anchor PRB and the downlink non-anchor PRB that meets the application rule from the at least one downlink non-anchor PRB to form a first configuration relationship for data transmission.

Specifically, the application rules are rules such as light load priority and channel quality priority. When a user accesses the NB-IoT system and is assigned to a non-anchor PRB, according to the principle of light load priority or channel quality priority, select the downlink non-anchor point that meets the rules in the downlink non-anchor PRB resource pool PRB; At the same time, according to the principle of light load priority or channel quality priority, select the uplink non-anchor PRB that meets the rules in the uplink non-anchor PRB resource pool, and then combine the downlink non-anchor PRB and uplink non-anchor PRB that meet the application rules PRB combines to provide data transmission for the user.

Among them, if the load of data transmission is too large, the system can select the lightly loaded PRB among 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 a user has already performed data transmission on an uplink non-anchor PRB or downlink non-anchor PRB, then the uplink non-anchor PRB or downlink non-anchor PRB can also perform data for other users transmission.

Preferably, the number of uplink non-anchor PRBs or downlink non-anchor PRBs that provide data transmission for one user in this application may be one. But 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 can provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data for the user transmission. In addition, the number of uplink non-anchor PRBs for data transmission for the user and the number of downlink non-anchor PRBs may not be equal, which is determined according to the load of data transmission.

This application provides a resource sharing method suitable for single-cell PRB resource sharing in the NB-IoT system. By removing the static configuration relationship between uplink and downlink non-anchor PRBs, each uplink non-anchor PRB can be combined with multiple downlinks Non-anchor PRB combination, each downlink non-anchor PRB can be combined with multiple uplink non-anchor PRBs, so that the NB-IoT system can freely combine the uplink and downlink non-anchor PRBs according to configuration requirements, avoiding light or empty PRB resources , Thereby improving the utilization of PRB resources.

FIG. 5 is a schematic diagram of PRB resource sharing of a single cell in an NB-IoT system provided by an embodiment of the application. As shown in Figure 5, since the non-anchor PRB resources in the non-anchor PRB resource pool of a single cell of the NB-IoT system have been statically configured, the uplink and downlink non-anchor PRBs can be assigned freely, and the The uplink and downlink non-anchor PRB data may be different. In the figure, the number of downlink PRBs is 4, and the number of uplink PRBs is 3; downlink PRB#1 can be combined with uplink PRB#1 and uplink PRB#2, and downlink PRB#3 can be combined with uplink PRB#1. After different users A, B and C access the NB-IoT system, user A can be assigned to uplink PRB#1 and downlink PRB#1, and user B can be assigned to uplink PRB#1 and downlink PRB#2 , User C can be assigned to uplink PRB#2 and downlink PRB#1.

Fig. 6 is a flowchart of a method for resource sharing provided by an embodiment of the application. As shown in Figure 6, this application provides a method for resource sharing, which is suitable for PRB resource sharing of multiple cells in an NB-IoT system, where the multiple cells at least include a first cell and a second cell. Specific implementation steps as follows:

Step S602: Acquire PRB release information of the second physical resource module.

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

Step S604: According to the second PRB release information, 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.

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

For the anchor PRB resources of each cell of the NB-IoT system, according to the 3GPP protocol, the physical cell of the NB-IoT system and the anchor PRB must have a one-to-one correspondence, and the uplink anchor PRB and the downlink anchor PRB are also one-to-one. The corresponding relationship cannot be paired with uplink and downlink PRBs in a pairwise combination like non-anchor PRBs. Therefore, this application does not remove the static configuration relationship and the fixed configuration relationship of the anchor PRB resources.

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

FIG. 7 is a schematic diagram of the uplink and downlink PRB resource pools during multi-cell PRB resource configuration of the NB-IoT system provided by an embodiment of the application. As shown in Figure 7, after forming the uplink non-anchor PRB resource pool and the downlink non-anchor PRB resource pool, each uplink non-anchor PRB can be combined with the downlink non-anchor PRB of multiple arbitrary cells, and each downlink non-anchor PRB The anchor PRB can be combined with the uplink non-anchor PRBs of multiple arbitrary cells. By forming non-anchor PRB resources of multiple cells into a non-anchor PRB resource pool, non-anchor PRB resources in each physical cell are shared and reused.

These physical cells can be logically defined as an NB-IoT super cell. By constructing an NB-IoT super cell, the available channel resources of the NB-IoT system (such as NPRACH channel resources) can be expanded, and it is conducive to better real-time performance. Resource allocation.

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

Among them, the application rules are rules such as light load priority and channel quality priority. When a user accesses the NB-IoT system and is assigned to a non-anchor PRB, according to the principle of light load priority or channel quality priority, select the downlink non-anchor point that meets the rules in the downlink non-anchor PRB resource pool PRB; At the same time, according to the principle of light load priority or channel quality priority, select the uplink non-anchor PRB that meets the rules in the uplink non-anchor PRB resource pool, and then combine the downlink non-anchor PRB and uplink non-anchor PRB that meet the application rules PRB combines to provide data transmission for the user.

Among them, the uplink non-anchor PRB and the downlink non-anchor PRB that provide users with data transmission come from different cells. If there are multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide users with data transmission, some of the uplink non-anchor PRBs and downlink non-anchor PRBs may come from the same cell.

This application provides a resource sharing method suitable for multi-cell PRB resource sharing in the NB-IoT system, by removing the static configuration relationship between the uplink and downlink non-anchor PRB resources in each cell of the NB-IoT system and removing the relationship between each cell The fixed configuration relationship of non-anchor PRB resources between the two, realizes that each uplink non-anchor PRB can be combined with the downlink non-anchor PRB of multiple arbitrary cells, and each downlink non-anchor PRB can be combined with the uplink non-anchor PRB of multiple arbitrary cells. Anchor PRB combination enables each cell to dynamically call or second non-anchor PRB resources of other cells to other cells according to the load status, avoiding the waste of PRB resources. In addition, by constructing the NB-IoT system super cell, within the framework of the NB-IoT system super cell, the base station can realize cross-physical cell scheduling, which is conducive to improving resource utilization.

FIG. 8 is a schematic diagram of PRB resource sharing of multiple cells in an NB-IoT system provided by an embodiment of the application. As shown in Figure 8, since the non-anchor PRB resources in the multi-cell PRB resource pool of the NB-IoT system have been released from the static configuration and the static configuration of the non-anchor PRB resources in each cell, the uplink and downlink of any cell Non-anchor PRBs can be assigned freely in combination. In the figure, there are cell #0 and cell #1; the number of downlink non-anchor PRBs in cell #0 is 3, the number of uplink non-anchor PRBs is 2, and the number of uplink and downlink non-anchor PRBs in cell #1 is 1 ; Wherein the uplink PRB#1 in cell #0 can be combined with downlink PRB#3 in cell #0 and downlink PRB#1 in cell #1, and uplink PRB#2 in cell #0 can be combined with downlink PRB#1 in cell #0 , The uplink PRB#1 in cell #1 can be combined with the downlink PRB#2 in cell #0. After different users A, B, C, and D access the NB-IoT system through different cells, user A can be assigned to the uplink PRB#1 of cell #0 and the downlink PRB#1 of cell #1. B can be assigned to the uplink PRB#1 of cell #0 and the downlink PRB#3 of cell #0. User C can be assigned to the uplink PRB#2 of cell #0 and the downlink PRB#1 of cell #0. User D can The uplink PRB#1 assigned to the cell #1 and the downlink PRB#2 of the cell #0.

FIG. 9 is a flowchart of a method for resource sharing provided by an embodiment of the application. As shown in Figure 9, this application provides a resource sharing method, which is suitable for cross-system PRB resource sharing. The specific implementation steps are as follows:

Step S902: Acquire PRB release information of the third physical resource module.

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

Step S904: According to the third PRB release information, release 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 fixedly configured to the cell and the resource attribute of the non-anchor PRB fixedly configured to the system. In other words, after the base station allocates non-anchor PRB resources to each cell, the non-anchor PRB resources can only provide data transmission for users in the corresponding cell, but cannot provide data transmission for users outside the corresponding cell; the same goes for After the base station configures the non-anchor PRB resource to each system, the non-anchor PRB resource intelligently provides data transmission for its corresponding system users, and cannot provide data transmission for users outside the corresponding system.

For the anchor PRB resources of each cell of the NB-IoT system, the system and the anchor PRB must have a one-to-one correspondence, and the uplink anchor PRB and the downlink anchor PRB also have a one-to-one correspondence, so this application does not Remove the static configuration relationship and the fixed configuration relationship between the anchor PRBs.

For the non-anchor PRB resources of each cell of each system, after receiving the third PRB release information, each system first releases the static configuration relationship of the non-anchor PRB resources in each cell, that is, releases the uplink non-anchor PRB and The one-to-one configuration relationship between the downlink non-anchor PRBs, and 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 relationship of the non-anchor PRB resources between the cells is released, so that the uplink and downlink non-anchor PRB resources of each cell in the same system can be freely combined in pairs. Then release the fixed configuration relationship of non-anchor PRB resources between each system, so that the uplink non-anchor PRBs of all cells in all systems form an uplink non-anchor PRB resource pool, and the downlink non-anchor PRBs of all cells in all systems The point PRB constitutes a downlink non-anchor PRB resource pool.

FIG. 10 is a schematic diagram of uplink and downlink PRB resource pools during cross-system PRB resource configuration according to an embodiment of the application. As shown in Figure 10, after the anchor PRB resource pool is formed, the anchor PRB resources in each cell and in each system will not be configured across cells and systems. They still follow the previous static configuration relationship. After forming the uplink non-anchor PRB resource pool and the downlink non-anchor PRB resource pool, each uplink non-anchor PRB can be combined with multiple downlink non-anchor PRBs in the same cell or different cells, or with the same one The combination of multiple downlink non-anchor PRBs in the system or in different systems (the combination of the non-anchor PRBs in the NB-IoT super cell and the non-anchor PRBs in the LTE cell is not shown in order to avoid the diagram from being too complicated). Similarly, each downlink non-anchor PRB can be combined with uplink non-anchor PRBs in the same cell or different cells, and can also be combined with uplink non-anchor PRBs in the same system or in different systems. By forming non-anchor PRB resources in each cell and each system into a non-anchor PRB resource pool, non-anchor PRB resources in each system can be shared and reused.

Preferably, this application can form an uplink non-anchor shared PRB resource pool and a downlink non-anchor shared PRB resource pool from non-anchor PRBs used for sharing in each cell and each system, and then set each non-anchor PRB Using attributes, each system selects the corresponding shared non-anchor PRB to provide data transmission for it according to the usage attributes.

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

Among them, the uplink non-anchor PRB and the downlink non-anchor PRB that provide users with data transmission come from different systems. If there are multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for users, some of the uplink non-anchor PRBs and downlink non-anchor PRBs may come from the same system.

This application provides a resource sharing method suitable for cross-system PRB resource sharing, by removing the static configuration relationship between the uplink and downlink non-anchor PRBs of each cell of each system, and the non-anchor PRB resource configuration between cells Relation and release the non-anchor PRB resource configuration relationship between the system and the system, so that each uplink non-anchor PRB can be combined with the downlink non-anchor PRB of any cell of any system, and each downlink non-anchor PRB can Combined with the uplink non-anchor PRBs of any cell of any system, each cell of each system can dynamically call PRB resources of other systems or second PRB resources to other systems according to the load status, avoiding the waste of PRB resources.

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

FIG. 11 is a flowchart of the NB-IoT system and the LTE system provided by an embodiment of the application negotiating to share PRB resources in the PRB resource pool. As shown in FIG. 11, the embodiment of the present application takes the in-band deployment of the PRB resources of the NB-IoT system on the PRB bandwidth of the LTE system as an example, and the specific implementation process is as follows:

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

This application is based on the resource sharing mechanism of the cross-system PRB resource pool, by setting the in-band PRB resources of some LTE systems as attributes shared by the NB-IoT system and the LTE system, that is, the non-anchor PRBs in each system are used as shared Form a non-anchor shared PRB resource pool. The shared PRB resource pool allows the NB-IoT system and the LTE system to be used in a time-sharing manner, and based on a cross-system negotiation mechanism, adaptively adjust the use of shared PRB in the subsequent period of time.

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

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

Step S1106: After receiving the system information reported by the two systems, the base station conducts inter-system negotiation according to the system information, and determines the usage attributes of the shared PRB resources in the shared PRB resource pool for a subsequent period of time.

Among them, if the shared non-anchor PRB is used by the NB-IoT system, the NB-IoT system calls the non-anchor PRB resource for data transmission; if the shared non-anchor PRB is used by the LTE system, the LTE The system calls the non-anchor PRB resource for data transmission. In one embodiment, if the system information reported by the NB-IoT system indicates that the load of PRB resources is large, according to the inter-system negotiation, the idle shared non-anchor PRB resources in the shared PRB resource pool are set to be used by the NB-IoT system The use attribute of the NB-IoT system for the subsequent NB-IoT system to call the non-anchor PRB resource for data transmission.

Step S1108, when reporting the system information of the NB-IoT system and the LTE system, a timer is started for timing.

Among them, the timer is used to detect the time for reporting the system information of the NB-IoT system and the LTE system, and set a threshold, which is a specified length of time. If the time of the reported system information exceeds the set threshold, the base station is notified to re-receive the system information reported by the NB-IoT system and the LTE system, and at the same time reset the timer time. This ensures that the base station continuously receives the NB-IoT system and the LTE system to report system information, and changes the ownership of the shared PRB in real time.

Step S1110: It is judged whether the time measured by the timer exceeds a set threshold.

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

Step S1112: According to the usage attributes of the shared PRB, the NB-IoT system and the LTE system call the PRB resources of the corresponding usage attributes for data transmission.

This application is based on a cross-system PRB resource pool, through a cross-system negotiation mechanism, adaptively adjusts the properties of the NB-IoT system and the LTE system in the subsequent period of time to share the use of PRBs, and realizes the method of adaptively adjusting the use of shared PRBs The shared use of resources improves the resource utilization efficiency of the overall system.

FIG. 12 is a schematic diagram of cross-system PRB resource sharing and adaptive adjustment provided by an embodiment of this application. As shown in Figure 12, the non-anchor PRB of the NB-IoT system is deployed in the LTE system band. Based on the cross-system PRB resource pool sharing mechanism, some PRB resources in the LTE system band are set to the NB-IoT system and LTE system. The attributes shared by the system allow the NB-IoT system and the LTE system to share time-sharing use, and based on the cross-system negotiation mechanism, adaptively adjust the ownership of the shared PRB for a period of time. The base station can dynamically adjust the ownership of each PRB in the shared area according to the load changes of the NB-IoT system and the LTE system. The scheduler of the NB-IoT system and the LTE system can allocate scheduling resources to different users according to the ownership of the shared PRB.

FIG. 13 is a structural block diagram of a resource sharing device provided by an embodiment of this application. As shown in FIG. 13, the present application provides a device 1300 for resource sharing. The device 1300 is suitable for single-cell PRB resource sharing in an NB-IoT system. It includes a first acquiring unit 1301, a first processing unit 1302, and a first generating unit. Unit 1303.

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

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.

It should be noted that in the deployment scenario of the NB-IoT system, there is usually only one uplink anchor PRB and downlink anchor PRB in a cell. Therefore, in the embodiment of this application, the static state between the uplink anchor PRB and the downlink anchor PRB is released. The configuration relationship is meaningless.

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 receiving the first PRB release information, the NB-IoT system releases the static configuration relationship between the uplink non-anchor PRB and downlink non-anchor PRB resources in the cell of the NB-IoT system, that is, releases the uplink non-anchor PRB. One-to-one configuration relationship with downlink non-anchor PRBs, and the configuration that the number of uplink non-anchor PRBs and the number of downlink non-anchor PRBs must be equal. After the static configuration relationship is released, all the uplink non-anchor PRBs form an uplink non-anchor PRB resource pool, and all the downlink non-anchor PRBs form a downlink non-anchor PRB resource pool.

The first generating unit 1303 is configured to select, from at least one uplink non-anchor PRB, an uplink non-anchor PRB that meets the application rule and from at least one downlink non-anchor PRB that meets the application rule to form a first configuration relationship Perform data transfer.

Preferably, the number of uplink non-anchor PRBs or downlink non-anchor PRBs that provide data transmission for one user in this application may be one. But 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 can provide multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data for the user transmission. In addition, in the NB-IoT system, if the load that a user needs to perform data transmission is less than the load of an uplink non-anchor PRB or downlink non-anchor PRB, then the uplink non-anchor PRB or downlink non-anchor PRB can also be Data transfer by other users.

This application realizes that each uplink non-anchor PRB can be combined with multiple downlink non-anchor PRBs through a resource sharing device suitable for single-cell PRB resource sharing in the NB-IoT system, and each downlink non-anchor PRB can Combining with multiple uplink non-anchor PRBs allows the NB-IoT system to freely combine uplink and downlink non-anchor PRBs according to configuration requirements, avoiding light or empty PRB resources, thereby improving the utilization of PRB resources.

FIG. 14 is a structural block diagram of a resource sharing device provided by an embodiment of this application. As shown in FIG. 14, the present application provides a device 1400 for resource sharing. The device 1400 is suitable for PRB resource sharing of multiple cells in the NB-IoT system. It includes a second acquiring unit 1401, a second processing unit 1402, and a second Generating unit 1403.

The second acquiring unit 1401 is configured to acquire PRB release information of the second physical resource module.

Among them, the second PRB release information is used to release the static configuration relationship between the uplink PRB and the downlink PRB and to release the PRB resource configuration 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.

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

It should be noted that the uplink non-anchor PRB and the downlink non-anchor PRB that provide users with data transmission come from different cells. If there are multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide users with data transmission, some of the uplink non-anchor PRBs and downlink non-anchor PRBs may come from the same cell.

This application realizes that each uplink non-anchor PRB can be combined with the downlink non-anchor PRB of multiple arbitrary cells through a resource sharing device suitable for multi-cell PRB resource sharing of the NB-IoT system, and each downlink non-anchor PRB The point PRB can be combined with the uplink non-anchor PRBs of multiple arbitrary cells, so that each cell can dynamically call the non-anchor PRB resources of other cells or second the non-anchor PRB resources to other cells according to the load status, avoiding the waste of PRB resources.

FIG. 15 is a structural block diagram of a resource sharing device provided by an embodiment of this application. As shown in FIG. 15, the present application provides a resource sharing device 1500, which is suitable for cross-system PRB resource sharing, and includes a third obtaining unit 1501, a third processing unit 1502, and a third generating unit 1503.

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

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

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

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

It should be noted that the uplink non-anchor PRB and the downlink non-anchor PRB that provide users with data transmission come from different systems. If there are multiple uplink non-anchor PRBs or downlink non-anchor PRBs to provide data transmission for users, some of the uplink non-anchor PRBs and downlink non-anchor PRBs may come from the same system.

This application realizes that each uplink non-anchor PRB can be combined with the downlink non-anchor PRB of any cell of any system through a resource sharing device suitable for cross-system PRB resource sharing, and each downlink non-anchor The PRB can be combined with the uplink non-anchor PRB of any cell of any system, so that each cell of each system can dynamically call PRB resources of other systems or second PRB resources to other systems according to the load status, avoiding the waste of PRB resources.

The device 1500 further includes an adjustment unit 1505. The adjustment unit 1505 specifically includes:

The generating subunit 1505A is used to set the NB-IoT system and the LTE system to share the PRB resource pool.

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

The determining subunit 1505C is used for inter-system negotiation according to system information to determine the usage attributes of the shared PRB resources in the shared PRB resource pool for a subsequent period of time; and the NB-IoT system and the LTE system perform data transmission according to the usage attributes of the shared PRB.

The time subunit 1505D is used to start a timer for timing when reporting the system information of the NB-IoT system and the LTE system, to determine whether the time measured by the timer exceeds the set threshold; and when the time measured by the timer exceeds the When the threshold is set, the system information reported by the NB-IoT system and the LTE system is received again.

In the description of this specification, specific features, structures, materials, or characteristics may be combined in any one or more embodiments or examples in a suitable manner.

The last thing to note is that the above embodiments are only used to illustrate the technical solutions of the application, but limit it; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A method for resource sharing, which is suitable for single-cell PRB resource sharing in an NB-IoT system, and is characterized in that it includes:

Acquiring PRB release information of the first physical resource module;

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

Select an uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and at least one downlink non-anchor PRB that meets the application rule to form a first configuration relationship for data transmission; The at least one uplink non-anchor PRB includes the first uplink non-anchor PRB, and the at least one downlink non-anchor PRB includes the first downlink non-anchor PRB.
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 specifically comprises:

According to the first PRB release information, release the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB.
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 specifically comprises:

Release the configuration relationship in which the number of uplink non-anchor PRBs is equal to the number of downlink non-anchor PRBs.
The method according to claim 1, wherein said selecting from at least one uplink non-anchor PRB that meets the application rule and from at least one downlink non-anchor PRB that meets the application rule The downlink non-anchor PRB forms the first configuration relationship for data transmission, which specifically includes:

Selecting from at least one uplink non-anchor PRB that conforms to the application rules includes an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting from at least one downlink non-anchor PRB that conforms to The rule-applied downlink non-anchor PRB includes 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 meets the application rule from at least one uplink non-anchor PRB includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool. Selecting a downlink non-anchor PRB that meets the application rule from the non-anchor PRBs includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.
The method according to claim 1, wherein the number of the uplink non-anchor PRBs in the first configuration relationship is not equal to the downlink non-anchor PRBs.
The method according to claim 1, wherein the method comprises:

Select any uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB that meets the application rule from at least one downlink non-anchor PRB to form a second configuration relationship. Data transmission; wherein, the first configuration relationship and the second configuration relationship include the same uplink non-anchor PRB or the downlink non-anchor PRB.
The method according to claim 1, wherein the application rule is a rule of light load preference or channel quality preference.
A device for resource sharing, the device is suitable for single-cell PRB resource sharing of an NB-IoT system, and is characterized by comprising: a transceiver, a processor, and a memory; the memory stores one or more programs, and the one The or more programs include instructions, which when executed by the device, cause the device to perform the method according to any of claims 1-7.
A method for resource sharing, which is suitable for PRB resource sharing of multiple cells in an NB-IoT system. The multiple cells include at least a first cell and a second cell, and are characterized in that they include:

Acquiring PRB release information of the second physical resource module;

According to the second PRB release information, 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; the first fixed configuration relationship refers to the non-anchor PRB Fixed allocation to the resource attributes of the cell;

Selecting an uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and selects the downlink non-anchor PRB that meets the application rule from at least one downlink non-anchor PRB to form a third configuration relationship 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, and the uplink At least one uplink non-anchor PRB in the non-anchor PRB belongs to one of the first cell and the second cell, and at least one downlink non-anchor PRB in the downlink non-anchor PRB that complies with the application rule belongs to The other cell of the first cell and the second cell.
The method according to claim 9, wherein the static configuration relationship and the first fixed configuration between the second uplink non-anchor PRB and the second downlink non-anchor PRB are released according to the second PRB release information The relationship includes:

According to the second PRB release information, release the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB in each cell and release the fixed non-anchor PRB resource attribute of each cell Configuration relationship.
The method according to claim 9, wherein the static configuration relationship and the first fixed configuration between the second uplink non-anchor PRB and the second downlink non-anchor PRB are released according to the second PRB release information The relationship includes:

According to the second PRB release information, release the configuration relationship in which the number of uplink non-anchor PRBs in each cell is equal to the number of downlink non-anchor PRBs and release the fixed configuration relationship of the non-anchor PRB resource attributes of each cell .
The method according to claim 9, wherein the selecting an uplink non-anchor PRB conforming to an application rule from at least one uplink non-anchor PRB and selecting at least one downlink non-anchor PRB conforming to the application rule The downlink non-anchor PRB forms the third configuration relationship for data transmission, which specifically includes:

Selecting from at least one uplink non-anchor PRB that conforms to the application rules includes an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB, and selecting from at least one downlink non-anchor PRB that conforms to The downlink non-anchor PRB to which the rule is applied includes 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 meets the application rule from at least one uplink non-anchor PRB includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool. Selecting a downlink non-anchor PRB that meets the application rule from the non-anchor PRBs includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.
The method according to claim 9, wherein the number of the uplink non-anchor PRBs in the third configuration relationship is not equal to the downlink non-anchor PRBs.
The method of claim 9, wherein the method comprises:

Select any uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB that meets the application rule from at least one downlink non-anchor PRB to form a fourth configuration relationship. Data transmission; wherein the third configuration relationship and the fourth configuration relationship include the same uplink non-anchor PRB or the downlink non-anchor PRB.
A device for resource sharing, which is suitable for PRB resource sharing of multiple cells in an NB-IoT system. The multiple cells include at least a first cell and a second cell, and are characterized in that they include: a transceiver, a processor, and a memory The memory stores one or more programs, the one or more programs include instructions, when the instructions are executed by the device, the device executes the device according to any of claims 9-14 Methods.
A method for resource sharing, the method is suitable for cross-system PRB resource sharing, the cross-system includes at least an NB-IoT system and a second system, and is characterized in that it includes:

Acquiring PRB release information of the third physical resource module;

According to the third PRB release information, release 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 relationship refers to the non-anchor PRB The resource attributes fixed to the cell and the non-anchor PRBs fixed to the system resource attributes;

Selecting an uplink non-anchor PRB conforming to the application rule from at least one uplink non-anchor PRB and selecting a downlink non-anchor PRB conforming to the application rule from the at least one downlink non-anchor PRB to form a fifth configuration relationship for data transmission; The at least one uplink non-anchor PRB includes the third uplink non-anchor PRB, the at least one downlink non-anchor PRB includes the third downlink non-anchor PRB, and the uplink non-anchor PRB that complies with the application rule At least one uplink non-anchor PRB in the non-anchor PRB 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 complies with the application rule It belongs to the other system of the NB-IoT system and the second system.
The method according to claim 16, wherein the static configuration relationship and the second fixed configuration between the third uplink non-anchor PRB and the third downlink non-anchor PRB are released according to the third PRB release information The relationship includes:

According to the third PRB release information, release the one-to-one configuration relationship between the uplink non-anchor PRB and the downlink non-anchor PRB in each cell in each cell, and release the non-anchor point of each cell The fixed configuration relationship of PRB resource attributes and the fixed configuration relationship of releasing the non-anchor PRB resource attributes of each system.
The method according to claim 16, wherein the static configuration relationship and the second fixed configuration between the third uplink non-anchor PRB and the third downlink non-anchor PRB are released according to the third PRB release information The relationship includes:

According to the third PRB release information, release the configuration relationship in which the number of uplink non-anchor PRBs in each cell in each system is equal to the number of downlink non-anchor PRBs, and release the non-anchor PRB resources of each cell The fixed configuration relationship of attributes and the fixed configuration relationship of releasing the non-anchor PRB resource attributes of each system.
The method according to claim 16, wherein the selecting the uplink non-anchor PRB conforming to the application rule from at least one uplink non-anchor PRB and selecting the downlink non-anchor PRB conforming to the application rule from the at least one downlink non-anchor PRB The non-anchor PRB forms the fifth configuration relationship for data transmission, which specifically includes:

Selecting from at least one uplink non-anchor PRB that conforms to the application rules includes an uplink non-anchor PRB resource pool formed by the at least one uplink non-anchor PRB; selecting from at least one downlink non-anchor PRB that conforms to The rule-applied downlink non-anchor PRB includes 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 meets the application rule from at least one uplink non-anchor PRB includes selecting an uplink non-anchor PRB that meets the application rule from the uplink non-anchor PRB resource pool. Selecting a downlink non-anchor PRB that meets the application rule from the non-anchor PRBs includes selecting a downlink non-anchor PRB that meets the application rule from the downlink non-anchor PRB resource pool.
The method according to claim 16, wherein the number of the uplink non-anchor PRBs in the fourth configuration relationship is not equal to the downlink non-anchor PRBs.
The method of claim 16, wherein the method comprises:

Select any uplink non-anchor PRB that meets the application rule from at least one uplink non-anchor PRB and any downlink non-anchor PRB that meets the application rule from at least one downlink non-anchor PRB to form a sixth configuration relationship. Data transmission; wherein the fifth configuration relationship and the sixth configuration relationship include the same uplink non-anchor PRB or the downlink non-anchor PRB.
The method of claim 16, wherein 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;

Conducting inter-system negotiation according to the system information, and determining the usage attributes of the shared PRB resources 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 use attribute of the shared PRB.
The method according to claim 16, wherein the performing inter-system negotiation according to the system information to determine the usage attributes 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, start a timer for timing, and determine whether the time measured by the timer exceeds a set threshold;

When the time measured by the timer exceeds the set threshold, the system information reported by the NB-IoT system and the second system is received again.
A device for resource sharing, the device is suitable for cross-system PRB resource sharing, the cross-system includes at least an NB-IoT system and a second system, and is characterized in that it includes: a transceiver, a processor, and a memory; The memory stores one or more programs, and the one or more programs include instructions, and when the instructions are executed by the device, the device executes the method according to any of claims 16-23.