WO2020215848A1 - Procédé et dispositif de partage de ressources - Google Patents

Procédé et dispositif de partage de ressources Download PDF

Info

Publication number
WO2020215848A1
WO2020215848A1 PCT/CN2020/073297 CN2020073297W WO2020215848A1 WO 2020215848 A1 WO2020215848 A1 WO 2020215848A1 CN 2020073297 W CN2020073297 W CN 2020073297W WO 2020215848 A1 WO2020215848 A1 WO 2020215848A1
Authority
WO
WIPO (PCT)
Prior art keywords
prb
anchor
anchor prb
uplink
downlink
Prior art date
Application number
PCT/CN2020/073297
Other languages
English (en)
Chinese (zh)
Inventor
曾龙基
许建涛
陈冬明
何朗
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020215848A1 publication Critical patent/WO2020215848A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of wireless communication technology, and in particular to a method and device for resource sharing.
  • NB-IoT Narrow Band Internet of Things
  • the deployment bandwidth is 180kHz, which is the same as a physical resource block (PRB) bandwidth of the LTE system.
  • PRB physical resource block
  • the 3GPP standard introduces multi-carrier (Multi-PRB).
  • the PRB types are divided into anchor point carriers (Anchor PRB) and non-anchor point carriers (Non-Anchor PRB).
  • 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.
  • 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.
  • LTE Long Term Evolution
  • 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.
  • the embodiments of the present application provide a method and device for resource sharing.
  • 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.
  • 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.
  • 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.
  • 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-an
  • the number of the uplink non-anchor PRBs in the first configuration relationship is not equal to the downlink non-anchor PRBs.
  • 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.
  • the application rule is a rule of light load preference or channel quality preference.
  • 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.
  • 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 down
  • 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.
  • 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.
  • 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 .
  • 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 PR
  • the number of the uplink non-anchor PRBs in the third configuration relationship is not equal to the downlink non-anchor PRBs.
  • 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.
  • 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.
  • 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
  • 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 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 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 are examples of each system.
  • 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-
  • the number of the uplink non-anchor PRBs in the fourth configuration relationship is not equal to the downlink non-anchor PRBs.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a cell 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.
  • 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.
  • 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.
  • 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 are examples of the number of uplink non-anchor PRBs.
  • 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.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • the uplink non-anchor PRB or downlink non-anchor PRB can also perform data for other users transmission.
  • 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.
  • 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.
  • the uplink and downlink non-anchor PRBs can be assigned freely, and the The uplink and downlink non-anchor PRB data may be different.
  • 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.
  • user A can be assigned to uplink PRB#1 and downlink PRB#1
  • 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.
  • 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.
  • 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.
  • 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.
  • the NB-IoT system 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.
  • 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.
  • 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.
  • NB-IoT super cell These physical cells can be logically defined as an NB-IoT super cell.
  • 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 .
  • the application rules are rules such as light load priority and channel quality priority.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • the uplink non-anchor PRB or downlink non-anchor PRB can also perform data for other users transmission.
  • 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.
  • 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.
  • 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.
  • 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 ;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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 .
  • the application rules are rules such as light load priority and channel quality priority.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • the uplink non-anchor PRB or downlink non-anchor PRB can also perform data for other users transmission.
  • 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.
  • 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.
  • the base station 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.
  • 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:
  • 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.
  • step S1104 the NB-IoT system and the LTE system report their respective system information to the base station.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the non-anchor PRB of the NB-IoT system is deployed in the LTE system band.
  • 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.
  • 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.
  • 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.
  • 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.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the NB-IoT system 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.
  • 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.
  • the application rules are rules such as light load priority and channel quality priority.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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
  • 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.
  • 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.
  • 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.
  • the point PRB constitutes a downlink non-anchor PRB resource pool.
  • 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.
  • the application rules are rules such as light load priority and channel quality priority.
  • the application rules are rules such as light load priority and channel quality priority.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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 base station 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de partage de ressources, le procédé étant approprié pour un partage de ressources de PRB à une cellule unique dans un système NB-IoT, et comprend les étapes suivantes : acquérir des informations de libération de PRB d'un premier module de ressource physique ; et libérer une relation de configuration statique entre un premier PRB de non-ancrage de liaison montante et un premier PRB de non-ancrage de liaison descendante selon les premières informations de libération de PRB ; et sélectionner un PRB de non-ancrage de liaison montante conforme à la règle d'application à partir d'au moins un PRB de non-ancrage de liaison montante et sélectionner un PRB de non-ancrage de liaison descendante conforme à la règle d'application à partir d'au moins un PRB de non-ancrage de liaison descendante afin de former une première relation de configuration pour la transmission de données, l'au moins un PRB de non-ancrage de liaison montante comprenant le premier PRB de non-ancrage de liaison montante, et au moins un PRB de non-ancrage de liaison descendante comprenant le premier PRB de non-ancrage de liaison descendante. La combinaison de chaque PRB de non-ancrage de liaison montante et de multiples PRB non d'ancrage de liaison descendante et la combinaison de chaque PRB de non-ancrage de liaison descendante et de multiples PRB de non-ancrage de liaison montante sont mises en oeuvre, de sorte que le système NB-IoT puisse combiner librement les non-ancrages de liaison montante et de liaison descendante selon les exigences de configuration, ce qui permet d'éviter une charge de lumière ou une charge vide de ressources de PRB, et d'augmenter le taux d'utilisation des ressources de PRB.
PCT/CN2020/073297 2019-04-22 2020-01-20 Procédé et dispositif de partage de ressources WO2020215848A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910324688.1A CN111836265B (zh) 2019-04-22 2019-04-22 一种资源共享的方法和装置
CN201910324688.1 2019-04-22

Publications (1)

Publication Number Publication Date
WO2020215848A1 true WO2020215848A1 (fr) 2020-10-29

Family

ID=72912315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073297 WO2020215848A1 (fr) 2019-04-22 2020-01-20 Procédé et dispositif de partage de ressources

Country Status (2)

Country Link
CN (1) CN111836265B (fr)
WO (1) WO2020215848A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112566199B (zh) * 2020-12-01 2023-07-25 中国联合网络通信集团有限公司 通讯小区切换方法、装置、电子设备以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294681A (zh) * 2016-04-01 2017-10-24 夏普株式会社 配置非锚物理资源块的方法和基站、确定非锚物理资源块位置的方法和用户设备
CN107645371A (zh) * 2016-07-20 2018-01-30 中兴通讯股份有限公司 一种载波配置的方法、装置和系统
CN107734687A (zh) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 一种获取网络系统资源配置方法、终端、网络设备及系统
WO2018174607A1 (fr) * 2017-03-22 2018-09-27 엘지전자(주) Procédé d'émission et de réception d'informations système dans un système de communication sans fil et appareil associé

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10477537B2 (en) * 2016-02-11 2019-11-12 Qualcomm Incorporated Multi-PRB operation for narrowband systems
CN108307378B (zh) * 2016-08-10 2021-09-17 中兴通讯股份有限公司 一种寻呼方法、装置及系统、用户设备
CN108566680B (zh) * 2018-03-02 2022-07-05 中国科学院上海高等研究院 多物理资源块在上下行链路配置方法/系统、介质及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294681A (zh) * 2016-04-01 2017-10-24 夏普株式会社 配置非锚物理资源块的方法和基站、确定非锚物理资源块位置的方法和用户设备
CN107645371A (zh) * 2016-07-20 2018-01-30 中兴通讯股份有限公司 一种载波配置的方法、装置和系统
CN107734687A (zh) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 一种获取网络系统资源配置方法、终端、网络设备及系统
WO2018174607A1 (fr) * 2017-03-22 2018-09-27 엘지전자(주) Procédé d'émission et de réception d'informations système dans un système de communication sans fil et appareil associé

Also Published As

Publication number Publication date
CN111836265B (zh) 2023-04-18
CN111836265A (zh) 2020-10-27

Similar Documents

Publication Publication Date Title
US11109289B2 (en) Scheduling method and base station
RU2640736C2 (ru) Параллельная беспроводная связь по лицензируемому и нелицензируемому спектрам
JP6540717B2 (ja) 無線通信システムにおけるユーザー機器側の電子機器と無線通信方法
EP4236570A2 (fr) Procédé et appareil de connexion lumineuse à utiliser dans un système de communication sans fil
US8509162B2 (en) System and method for scheduling over multiple hops
CN105898770B (zh) 一种空频道检测方法及节点设备
WO2018028269A1 (fr) Procédé et dispositif de planification de ressource
CN106465471B (zh) 用于跨越授权和非授权频谱进行无线传输通信的系统和方法
KR101253531B1 (ko) 무선 통신 네트워크들에서 다중 업링크 캐리어 할당
JP2017516414A (ja) 認可スペクトルおよび無認可スペクトル上の動的リソース割り当てのためのシステムおよび方法
WO2010121560A1 (fr) Procédé de partage de charge, dispositif et système associés
JP6462179B2 (ja) 無線端末、基地局、及び方法
JP2020523916A (ja) 上りリンクリソース許可方法および上りリンクリソース許可装置、ならびにシステム
RU2687162C1 (ru) Способ передачи данных, точка доступа и станция
WO2020203446A1 (fr) Système de communication
WO2013017109A1 (fr) Procédé, équipement et station de base correspondante pour choisir des porteuses
WO2020215848A1 (fr) Procédé et dispositif de partage de ressources
WO2021088006A1 (fr) Procédé de communication et appareil de communication
US9326293B2 (en) Selection of a secondary component carrier based on interference information
CN112243296B (zh) 辅小区激活方法及装置
CN117099388A (zh) Rrm测量活动报告和使用
CN109041244A (zh) Sr资源复用方法及装置
WO2016197740A1 (fr) Procédé et appareil de division de débit et nœud évolué
EP3729893B1 (fr) Procédé et dispositif de partage de ressources
WO2017024570A1 (fr) Procédé et appareil pour déterminer la configuration de sous-trame d'un groupe de cellules

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20795469

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20795469

Country of ref document: EP

Kind code of ref document: A1