WO2020015469A1

WO2020015469A1 - Carrier sharing method, device and system, and storage medium

Info

Publication number: WO2020015469A1
Application number: PCT/CN2019/089702
Authority: WO
Inventors: 刘芙蕾; 芮华; 施风; 黄河
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-07-20
Filing date: 2019-05-31
Publication date: 2020-01-23
Also published as: CN110740453A; CN110740453B

Abstract

Disclosed in the present application are a carrier sharing method, device and system, and a storage medium. The carrier sharing method comprises: when a first communication node determines that carrier resources thereof are insufficient and receives a first message of a second communication node, the first communication node transmits data on an idle carrier, wherein the first message comprises a first correspondence between the cell identifier of the second communication node and carrier information of the idle carrier; the first communication node sends a second message to the second communication node, the second message comprising a second correspondence between the cell identifier of the first communication node and carrier information of the occupied carrier, wherein the first communication node and the second communication node belong to different communication systems.

Description

Carrier sharing method, device, system and storage medium

Cross-reference to related applications

This application is based on a Chinese patent application with an application number of 201810806041.8 and an application date of July 20, 2018, and claims the priority of the Chinese patent application. The entire contents of the Chinese patent application are incorporated herein by reference.

Technical field

This application relates to, but is not limited to, the field of wireless communications, and in particular, to a carrier sharing method, device, system, and storage medium.

Background technique

With the gradual increase in the number of users, the narrowband Internet of Things (NB-IoT) of the cellular-based narrowband Internet of Things appears to have insufficient spectrum resources, and the Global System for Mobile Communication (GSM) After that, with the decrease of the number of users, GSM has a situation of idle spectrum resources, resulting in low spectrum efficiency, and related technologies have not yet given effective solutions.

Summary of the invention

In view of this, the embodiments of the present application are expected to provide a carrier sharing method, device, system and storage medium, which can improve spectrum efficiency.

An embodiment of the present application provides a carrier sharing method, including:

When the first communication node determines that its own carrier resources are insufficient and receives a first message from a second communication node, the first communication node transmits data on an idle carrier; wherein the first message includes: a second A first correspondence between a cell identifier of a communication node and carrier information of an idle carrier;

Sending, by the first communication node, a second message to the second communication node, the second message includes: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

The first communication node and the second communication node belong to different communication systems.

In the above solution, when the first communication node determines that its own carrier resource is insufficient, before the receiving the first message of the second communication node, the method further includes:

The first communication node sends a third message to the second communication node, the third message includes a cell identifier corresponding to a carrier with insufficient resources of the first communication node, or a carrier with insufficient resources of the first communication node A third correspondence relationship between the corresponding cell identifier and the cell identifier of the second communication node.

In the above solution, the method further includes:

When the first communication node receives a fifth message, the fifth message includes a fourth correspondence between a cell identifier of the second communication node and carrier information of a carrier to be recovered;

The first communication node releases the carrier that needs to be recovered, and sends a sixth message to the second communication node, where the sixth message includes the cell identifier of the first communication node and the carrier information of the released carrier. The fifth correspondence relationship.

In the above solution, the absolute value of the difference between the spectral bandwidth of the carrier of the first communication node and the spectral bandwidth of the carrier of the second communication node is less than or equal to a preset threshold.

An embodiment of the present application further provides a carrier sharing method, including:

The second communication node evaluates the load status of its own carrier, and sends a first message to the first communication node according to the load status of its own carrier. The first message includes: the cell identifier of the second communication node and carrier information of the idle carrier. A first correspondence relationship between them;

Receiving, by the second communication node, a second message of the first communication node, the second message includes: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

In the above solution, before the second communication node evaluates the load condition of its own carrier, the method further includes:

Receiving, by the second communication node, a third message of the first communication node, the third message includes: a cell identifier of the first communication node, or a cell identifier of the first communication node and the first communication node A third correspondence relationship between the cell identifiers of the two communication nodes;

The evaluating, by the second communication node, the load status of the carrier includes:

The second communication node evaluates a load condition of a carrier corresponding to a cell identifier of the second communication node in the third correspondence.

In the above solution, the second communication node evaluates a load condition of its own carrier within a shared time period.

In the above solution, the method further includes:

When the second communication node needs to recover a carrier that has been occupied by the first communication node, the second communication node sends a fifth message to the first communication node, where the fifth message includes: a cell identifier of the second communication node A fourth correspondence relationship with the carrier information of the carrier to be recovered;

Receiving, by the second communication node, a sixth message of the first communication node, the sixth message includes: a fifth correspondence between a cell identifier of the first communication node and carrier information of a released carrier .

An embodiment of the present application proposes a carrier sharing device, including:

A first determining module configured to determine that its own carrier resource is insufficient;

A first receiving module configured to receive a first message of a second communication node, the first message including: a first correspondence between a cell identifier of the second communication node and carrier information of an idle carrier;

A first sending module configured to transmit data on the idle carrier; sending a second message to the second communication node, the second message including: a cell identifier of the first communication node and carrier information of an occupied carrier A second correspondence relationship between them; wherein the first communication node and the second communication node belong to different communication systems.

The second sending module is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier, where the first message includes a cell identifier of the second communication node and an idle carrier. A first correspondence relationship between the carrier information of

A second receiving module configured to receive a second message of the first communication node, the second message including: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

An embodiment of the present application provides a carrier sharing device, including a processor and a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed by the processor, any one of the foregoing is implemented. Carrier sharing method.

An embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the foregoing carrier sharing methods are implemented.

An embodiment of the present application proposes a carrier sharing system, including:

A first communication node configured to transmit data on the idle carrier when it is determined that its own carrier resources are insufficient and a first message from a second communication node is received; and send a second message to the second communication node; The first message includes: a first correspondence between a cell identifier of a second communication node and carrier information of an idle carrier, and the second message includes: a cell identifier of the first communication node and the occupied carrier A second correspondence relationship between carrier information; the first communication node and the second communication node belong to different communication systems;

The second communication node is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier; and receive a second message of the first communication node.

Embodiments of the present application include: when the first communication node determines that its own carrier resource is insufficient and receives a first message from a second communication node, the first communication node transmits data on an idle carrier; wherein, the first A message includes: a first correspondence between a cell identifier of a second communication node and carrier information of an idle carrier; the first communication node sends a second message to the second communication node, and the second message includes The second correspondence between the cell identifier of the first communication node and the carrier information of the occupied carrier; wherein the first communication node and the second communication node belong to different communication systems. The embodiments of the present application enable a communication system to which a first communication node belongs to share a carrier resource of a communication system to which a second communication node belongs, thereby improving spectrum efficiency.

Other features and advantages of the embodiments of the present application will be explained in the following description, and part of them will become apparent from the description, or be understood by implementing the embodiments of the present application. The objects and other advantages of the embodiments of the present application can be achieved and obtained by the structures specifically pointed out in the description, the claims, and the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic diagram of downlink channel configuration of each carrier in a multi-carrier cell of an NB-IoT system according to an embodiment of the present application;

2 is a schematic diagram of a GSM channel configuration according to an embodiment of the present application;

3 is a flowchart of a carrier sharing method according to an embodiment of the present application;

4 is a flowchart of a carrier sharing method according to an embodiment of the present application;

5 is a schematic structural composition diagram of a carrier sharing device according to an embodiment of the present application;

6 is a schematic structural composition diagram of a carrier sharing device according to an embodiment of the present application;

7 is a schematic structural composition diagram of a carrier sharing system according to an embodiment of the present application;

FIG. 8 is a diagram of an NB-IoT system and a GSM sharing architecture according to an embodiment of the present application; FIG.

9 is a schematic interaction diagram of a carrier sharing method according to an embodiment of the present application;

FIG. 10 is a schematic interaction diagram of a carrier sharing method proposed in the present application;

11 is an interaction schematic diagram of a carrier sharing method according to an embodiment of the present application;

FIG. 12 is an interaction schematic diagram of a carrier sharing method according to an embodiment of the present application.

detailed description

The embodiments of the present application will be described in detail below with reference to the drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other.

The steps shown in the flowchart of the figures may be performed in a computer system such as a set of computer-executable instructions. And, although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

Some frequency bands used by NB-IoT are the same as GSM, and the working principles of the two systems are partially similar, so carrier sharing is possible. The working principles of the two systems are as follows.

FIG. 1 is a schematic diagram of downlink channel configuration of each carrier in a multi-carrier cell of an NB-IoT system according to an embodiment of the present application. As shown in Figure 1, a cell includes an anchor carrier (ie, the control carrier) and several non-anchor carriers (ie, the data carrier). Each carrier has a spectral bandwidth of 180 kHz ( KHz), the maximum spectrum span of all carriers in the cell does not exceed 20 megahertz (MHz).

Among them, there is only one downlink carrier in a multi-carrier cell that supports the simultaneous narrowband primary synchronization signal (NPSS, Narrowband Primary Synchronization Signal), narrowband secondary synchronization signal (NSSS, Narrowband Secondary Synchronization Signal), and narrowband physical broadcast channel (NPBCH, Narrowband Physical Physical Channel) Broadcast Channel and Narrowband Physical Downlink Control Channel (NPDCCH), Narrowband Physical Downlink Shared Channel (NPDSCH) and Narrowband Physical Downlink Shared Channel (NPDSCH) channels. This carrier is called Anchor carrier. The UE needs to monitor NPSS, NSSS, NPBCH, NPDCCH, and NPDSCH information on the Anchor carrier.

In a multi-carrier cell, there may be several downlink carriers that only carry NPDCCH and NPDSCH, but do not carry NPSS, NSSS, and NPBCH channels, and are called Non-Anchor carriers. The UE needs to monitor NPDCCH and NPDSCH information on the Non-Anchor carrier.

FIG. 2 is a schematic diagram of a GSM channel configuration according to an embodiment of the present application. As shown in Figure 2, in GSM, suppose a cell has n carrier frequencies, which are represented by C0, C1 ... Cn. Each carrier frequency is represented by 8 time slots, and represented by Ts0, Ts1 ... Ts7. The slot width is 15/26. Milliseconds (ms).

The control channel is fixedly mapped to the Ts0 slot of the carrier frequency C0, such as the frequency correction channel (FCCH, Frequency Channel, Channel), synchronization channel (SCH, Synchronization channel), broadcast control channel (BCCH, Broadcast control channel), and CCCH , Common Control Channel). C1 to Cn are all used for data transmission, and Ts0 to Ts7 are data channels.

In summary, the GSM and NB-IoT systems use a 200KHz bandwidth, and the control channel is sent on a fixed carrier, and the data channel is sent on other carriers. Therefore, when the anchor carrier of the NB-IoT system and the control carrier frequency of GSM are respectively Independent, the carrier frequency of the transmission data channel can be shared between the NB-IoT system and GSM, but the carrier sharing method given in the embodiment of the present application is not limited to the sharing between the NB-IoT system and GSM, and can be any two Carrier sharing between two communication systems.

Referring to FIG. 3, an embodiment of the present application provides a carrier sharing method, including:

Step 300: When the first communication node determines that its own carrier resources are insufficient and receives a first message from a second communication node, the first communication node transmits data on the idle carrier; wherein the first message When the first correspondence between the cell identifier of the second communication node and the carrier information of the idle carrier is included, the first communication node and the second communication node belong to different communication systems.

In some embodiments, the absolute value of the difference between the spectral bandwidth of the carrier of the first communication node and the spectral bandwidth of the carrier of the second communication node is less than or equal to a preset threshold.

In some embodiments, the first communication node may determine whether its own carrier resources are sufficient by at least one of the following: the current used power of the carrier and the number of Physical Resource Blocks (PRBs) currently used by the carrier.

For example, when the current used power of the carrier is greater than or equal to the first predetermined threshold, the carrier resource is considered insufficient; when the current used power of the carrier is less than the first predetermined threshold, the carrier resource is considered sufficient.

For another example, when the number of currently used PRBs of the carrier is greater than or equal to the first predetermined threshold, the carrier resource is considered insufficient; when the number of currently used PRBs of the carrier is less than the first predetermined threshold, the carrier resource is considered sufficient.

In some embodiments, the first correspondence relationship further includes: a cell identifier of the first communication node.

In some embodiments, the carrier information includes a frequency point value.

In some embodiments, the first communication node may first determine whether its carrier resources are sufficient before receiving the first message from the second communication node; or the first communication node first receives the first message from the second communication node, and then Determine whether its own carrier resources are sufficient. These two cases are explained separately below.

(1) The first communication node first determines whether its own carrier resource is sufficient, and then receives the first message from the second communication node.

In this case, the first communication node needs to determine whether the resources of all the carriers of the first communication node are sufficient. When the carrier resources of the first communication node are insufficient, before receiving the first message of the second communication node, the method further includes: include:

In some embodiments, the information carried in the third message is determined according to the configuration mode of the carrier shared cell. In actual implementation, when the third correspondence between the cell identity of the first communication node and the cell identity of the second communication node is configured only in the first communication node, the third message includes the carrier correspondence of insufficient resources of the first communication node A third correspondence between the cell identity of the cell and the cell identity of the second communication node;

When the third correspondence is configured only in the second communication node, the third message includes a cell identifier corresponding to a carrier with insufficient resources of the first communication node;

When the third correspondence relationship is configured in the first communication node and the second communication node at the same time, the third message may include a cell identifier corresponding to a carrier with insufficient resources of the first communication node, or a carrier with insufficient resources of the first communication node The third correspondence relationship between the corresponding cell identity and the cell identity of the second communication node.

In some embodiments, the third message may be a carrier sharing request (Frequency Sharing Request).

In some embodiments, the cell identifier may include a base station identifier and a cell identifier; or the cell identifier includes only the cell identifier and does not include the base station identifier. When the cell identifier includes the base station identifier and the cell identifier, the first communication node sends a third message to the cell of the second communication node corresponding to the cell identifier corresponding to the carrier with insufficient resources of the first communication node when its own carrier resource is insufficient. The second communication node corresponding to the base station identifier in the identifier is sufficient; when the cell identifier does not include the base station identifier, it is necessary to configure between the first communication node identifier and the second communication node identifier between the first communication node and the second communication node. Based on the correspondence between the first communication node identifier and the second communication node identifier, it can be known to which second communication node the third message is sent.

In some embodiments, when the first communication node does not receive a response message (such as the first message or the fourth message) from the second communication node within a preset time after sending the third message to the second communication node, the first communication node The communication node sends a third message to the second communication node again.

(2) The first communication node first receives the first message from the second communication node, and then judges whether its own carrier resource is sufficient.

In this case, the first communication node only needs to determine whether the carrier resource corresponding to the cell identifier of the first communication node corresponding to the cell identifier of the second communication node in the first correspondence relationship is sufficient. Data is transmitted on an idle carrier corresponding to the cell identity of the second communication node.

In actual implementation, when a cell identifier of a first communication node is included in the first correspondence relationship, the first communication node directly determines whether resources of a carrier corresponding to a cell identifier of the first communication node in the first correspondence relationship are sufficient; When the cell identifier of the first communication node is not included in a correspondence relationship, the first communication node searches the pre-configured third correspondence relationship for the cell of the first communication node corresponding to the cell identification of the second communication node in the first correspondence relationship. Identification, and then determine whether the carrier corresponding to the cell identity of the found first communication node has sufficient resources.

In some embodiments, whether the carrier information of the idle carrier in the first message is empty can be used to determine whether there is an idle carrier in the second communication node. In actual implementation, when the carrier information of the idle carrier is empty, it means that there is no idle carrier in the second communication node; when the carrier information of the idle carrier is not empty, it means that there is an idle carrier in the second communication node information.

In some embodiments, when the second communication node does not have an idle carrier, the first communication node may wait for the next cycle or receive the first message again. Before the first message is not received again, the second communication node is deemed to have no Idle carriers can be shared.

In some embodiments, the first communication node transmits data on the carrier corresponding to the cell identifier of the second communication node corresponding to the cell identifier of the carrier corresponding to the carrier with insufficient resources of the first communication node, that is, the first communication node satisfies the third correspondence relationship. The cell identity of the first communication node and the cell identity of the second communication node can be used for carrier sharing, and the cell identity of the first communication node and the cell identity of the second communication node that do not satisfy the third correspondence cannot be used for carrier sharing.

Step 301: The first communication node sends a second message to the second communication node. The second message includes a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier.

In actual implementation, when the first communication node does not occupy any idle carrier, the carrier information of the occupied carrier is empty.

In some embodiments, the first communication node may periodically send a second message to the second communication node.

In some embodiments, after the first communication node sends a third message to the second communication node, before the first communication node receives the first message from the second communication node, the method further includes:

The first communication node receives a fourth message of the second communication node.

The fourth message may be a response message or a carrier sharing response, which is used to inform the first communication node that the third message has been received, so that the first communication node does not receive the first message for a long time. The third message is repeatedly sent. It should be noted that the fourth message is only a response to the third message and does not need to carry any information. Any form of notification message is acceptable.

This method avoids message redundancy caused by the first communication node repeatedly sending the third message without receiving the first message for a long time after sending the third message.

In some embodiments, the method further includes:

When the first communication node receives a fifth message, the fifth message includes: a fourth correspondence between the cell identifier of the second communication node and the carrier information of the carrier to be recovered; the first communication node releases The carrier that needs to be recovered sends a sixth message to the second communication node, where the sixth message includes a fifth correspondence between the cell identifier of the first communication node and the carrier information of the released carrier .

In some embodiments, after the first communication node receives the fifth message, before the first communication node releases a carrier to be recovered, the method further includes:

The first communication node sends a seventh message to the second communication node.

The seventh message may be a response message, used to inform the second communication node that the fifth message has been received, so that the second communication node does not repeatedly send the fifth message because it has not received the sixth message for a long time. It should be noted that the seventh message is only a response to the fifth message and does not need to carry any information. Any form of notification message is acceptable.

This method avoids message redundancy caused by the second communication node repeatedly sending the fifth message without receiving the sixth message after sending the fifth message for a long time.

Referring to FIG. 4, another embodiment of the present application provides a carrier sharing method, including:

Step 400: The second communication node evaluates the load status of its own carrier and sends a first message to the first communication node according to the load status of its own carrier. The first message includes: the cell identifier of the second communication node and the idle carrier A first correspondence relationship between the carrier information of the first carrier; wherein the first communication node and the second communication node belong to different communication systems.

In some embodiments, the first correspondence relationship further includes a cell identifier of the first communication node. In actual implementation, when the third correspondence relationship is configured only at the first communication node, the first correspondence relationship does not include the cell identifier of the first communication node;

When the third correspondence relationship is configured only at the second communication node, the first correspondence relationship includes a cell identifier of the first communication node;

When the third correspondence relationship is configured on the first communication node and the second communication node at the same time, the first correspondence relationship may or may not include the cell identifier of the first communication node.

In some embodiments, the carrier information includes a frequency point value.

When there is no idle carrier, the carrier information is empty.

In some embodiments, the second communication node may evaluate the load status of its own carrier by at least one of the following: the current power used by the carrier, and the number of users currently carried by the carrier.

For example, when the current used power of the carrier is less than or equal to the second predetermined threshold, the load of the carrier is considered to be less than or equal to the second preset threshold, that is, the carrier is in an idle state; when the current used power of the carrier is greater than the second predetermined threshold, it is considered that The load of the carrier is greater than a second preset threshold, that is, the carrier is in a non-idle state.

For another example, when the number of users currently carried on the carrier is less than or equal to the second predetermined threshold, the load of the carrier is considered to be less than or equal to the second preset threshold, that is, the carrier is idle; when the number of users currently carried on the carrier is greater than the second predetermined threshold At the time limit, the load of the carrier is considered to be greater than the second preset threshold, that is, the carrier is in a non-idle state.

In some embodiments, the second communication node may evaluate the load condition of its own carrier after receiving the third message from the first communication node; or, the second communication node may evaluate the load condition of its own carrier within the shared time period. These two cases are described separately below.

(1) After receiving the third message from the first communication node, the second communication node evaluates the load condition of its own carrier.

In this case, the third message includes: a cell identity of the first communication node, or a third correspondence between the cell identity of the first communication node and the cell identity of the second communication node.

The second communication node only evaluates the load status of the carrier corresponding to the cell identity of the second communication node in the third correspondence relationship.

When the third message includes only the cell identifier of the first communication node, the second communication node searches the pre-configured third correspondence relationship for the cell identifier of the second communication node corresponding to the cell identifier of the first communication node in the third message. , And then evaluate the carrier load status corresponding to the cell identity of the found second communication node.

(2) The second communication node evaluates the load condition of its own carrier within the shared time period.

In this case, the second communication node evaluates the load conditions of all its carriers within the shared time period.

The second communication node may periodically send a first message to the first communication node; or, when the carrier state of the second communication node changes (for example, from idle to non-idle, or from non-idle to idle), the first communication node may Message.

Step 401: The second communication node receives a second message of the first communication node, where the second message includes a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier.

In some embodiments, after the second communication node receives the third message from the first communication node, before the second communication node evaluates the load condition of its own carrier, the method further includes:

The second communication node sends a fourth message to the first communication node, indicating that the first message is received.

The fourth message may be a response message or a carrier sharing response (Frequency Sharing Response) configured to inform the first communication node that the third message has been received, so that the first communication node does not receive the first message for a long time. The third message is repeatedly sent. It should be noted that the fourth message is only a response to the third message and does not need to carry any information. Any form of notification message is acceptable.

In some embodiments, the method further includes:

Receiving, by the second communication node, a sixth message of the first communication node, the sixth message: a fifth correspondence between a cell identifier of the first communication node and carrier information of a released carrier, Instruct the user to send data on the released carrier.

In some embodiments, the need to recover a carrier that has been occupied by the first communication node includes the following two cases: when the sharing period ends, or the carrier load of the second communication node suddenly increases, that is, when the carrier resource of the second communication node is insufficient .

In actual implementation, when the sharing period ends, the second communication node recycles all shared carriers;

When the carrier resource of the second communication node is insufficient, the second communication node recycles all shared carriers, or recycles one carrier at a time, that is, it determines whether the carrier resource is sufficient after each carrier is recovered, which is not limited in this embodiment of the present application.

In some embodiments, after sending the fifth message to the first communication node, before the second communication node receives the sixth message from the first communication node, the method further includes:

The second communication node receives a seventh message of the first communication node.

The seventh message may be a response message used to inform the second communication node that the fifth message has been received, so that the second communication node does not repeatedly send the fifth message because it has not received the sixth message for a long time. It should be noted that the seventh message is only a response to the fifth message and does not need to carry any information. Any form of notification message is acceptable.

In the above embodiment, the first communication node and the second communication node may be base stations belonging to different communication systems. For example, the first communication node is an eNodeB of an NB-IoT system, and the second communication node is a GSM BSC.

Referring to FIG. 5, another embodiment of the present application provides a carrier sharing device (such as a first communication node), including:

A first determining module 501 configured to determine that its own carrier resource is insufficient;

The first receiving module 502 is configured to receive a first message from a second communication node, where the first message includes a first correspondence between a cell identifier of the second communication node and carrier information of an idle carrier;

A first sending module 503 configured to transmit data on the idle carrier; and send a second message to the second communication node, where the second message includes: a cell identifier of the first communication node and a carrier of an occupied carrier The second correspondence between the information; wherein the first communication node and the second communication node belong to different communication systems.

In some embodiments, the first sending module 503 is further configured:

Send a third message to the second communication node, where the third message includes a cell identifier corresponding to a carrier with insufficient resources of the first communication node, or a cell identifier and a cell corresponding to a carrier with insufficient resources of the first communication node The third correspondence relationship between the cell identifiers of the second communication nodes is described.

In some embodiments, the first receiving module 502 is further configured:

A fourth message is received from the second communication node.

In some embodiments, the carrier sharing device further includes:

The processing module 504 is configured such that when the first receiving module 502 receives a fifth message or does not need to use a carrier of the second communication node, the fifth message includes: a cell identifier of the second communication node and a carrier of the carrier to be recovered. A fourth correspondence relationship between carrier information; releasing the carrier to be recovered or the carrier not to be used;

The first sending module 503 is further configured:

Sending a sixth message to the second communication node, where the sixth message includes a fifth correspondence between a cell identifier of the first communication node and carrier information of a released carrier.

In some embodiments, the first sending module 503 is further configured:

Sending a seventh message to the second communication node.

Referring to FIG. 6, another embodiment of the present application provides a carrier sharing device (such as a second communication node), including:

The second sending module 601 is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier, where the first message includes: a cell identifier of the second communication node and an idle A first correspondence relationship between carrier information of carriers;

The second receiving module 602 is configured to receive a second message of the first communication node, where the second message includes a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

In some embodiments, the second receiving module 602 is further configured to receive a third message of the first communication node, where the third message includes: a cell identifier of the first communication node, or the first communication node A third correspondence between a cell identifier of a communication node and a cell identifier of the second communication node;

The second sending module 601 is further configured:

Evaluate the load status of the carrier corresponding to the cell identity of the second communication node in the third correspondence relationship, and send a first message to the first communication node according to the load status of the own carrier.

In some embodiments, the second sending module 601 is further configured:

Sending a fourth message to the first communication node.

In some embodiments, the second sending module 601 is further configured:

The load status of the own carrier is evaluated within the shared time period, and a first message is sent to the first communication node according to the load status of the own carrier.

In some embodiments, the second sending module 601 is further configured:

When the carrier that has been occupied by the first communication node needs to be recovered, a fifth message is sent to the first communication node, and the fifth message includes: the cell identifier of the second communication node and the carrier that needs to be recovered. A fourth correspondence relationship between carrier information;

The second receiving module 602 is further configured to receive a sixth message of the first communication node, where the sixth message includes: the first message between the cell identifier of the first communication node and the carrier information of the released carrier. Five correspondences.

In some embodiments, the second receiving module 602 is further configured to: receive a seventh message of the first communication node.

An embodiment of the present application further provides a carrier sharing device, including a processor and a computer-readable storage medium. The computer-readable storage medium stores instructions, and when the instructions are executed by the processor, implements any of the foregoing tasks. A carrier sharing method.

An embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the foregoing carrier sharing methods are implemented.

Computer storage media includes, but is not limited to, Read-Only Memory (ROM) / Random Access Memory (RAM), Electrically Erasable Programmable Read-only Memory (EEPROM), Flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic case, magnetic tape, disk storage or other magnetic storage device, or any device that can be used to store desired information and can be accessed by a computer Other media.

Referring to FIG. 7, an embodiment of the present application provides a carrier sharing system, including:

The first communication node 701 is configured to transmit data on the idle carrier when it is determined that its own carrier resources are insufficient and receive a first message from the second communication node; and send a second message to the second communication node. Wherein, the first message includes a first correspondence between a cell identifier of a second communication node and carrier information of an idle carrier, and the second message includes: a cell identifier of the first communication node and an occupied carrier A second correspondence relationship between the carrier information of the first communication node; the first communication node and the second communication node belong to different communication systems;

The second communication node 702 is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier; and receive a second message of the first communication node.

In some embodiments, the first communication node 701 is further configured:

Send a third message to the second communication node, where the third message includes a cell identifier corresponding to a carrier with insufficient resources of the first communication node, or a cell identifier and a cell corresponding to a carrier with insufficient resources of the first communication node The third correspondence relationship between the cell identifiers of the second communication nodes;

The second communication node 702 is further configured:

Receiving the third message of the first communication node; evaluating the load condition of the carrier corresponding to the cell identity of the second communication node in the third correspondence relationship, and sending the load to the first communication node according to the load condition of the own carrier The first message.

In some embodiments, the first communication node 701 is further configured:

Receiving a fourth message from the second communication node;

The second communication node 702 is further configured to send a fourth message to the first communication node.

In some embodiments, the first communication node 701 is further configured:

When the fifth message is received or the carrier of the second communication node is not required to be used, the fifth message includes: a fourth correspondence between the cell identifier of the second communication node and the carrier information of the carrier to be recovered; release And sending a sixth message to the second communication node for the carrier that needs to be recovered or the carrier that does not need to be used, the sixth message includes: a cell identifier of the first communication node and carrier information of the released carrier The fifth corresponding relationship between them;

The second communication node 702 is further configured:

When the carrier that has been occupied by the first communication node needs to be recovered, a fifth message is sent to the first communication node, and the fifth message includes: the cell identifier of the second communication node and the carrier that needs to be recovered. A fourth correspondence relationship between carrier information; a sixth message of the first communication node is received, the sixth message includes: a cell identifier of the first communication node and carrier information of a released carrier Fifth correspondence.

In some embodiments, the first communication node 701 is further configured to: send a seventh message to the second communication node;

The second communication node 702 is further configured to receive a seventh message of the first communication node.

NB-IoT and GSM network element connection methods According to Figure 3, an interface is established between the BSC and the MME, and the message interaction between the BSC and the eNodeB is transparently transmitted through the MME to assist NB-IoT and GSM to complete the carrier sharing function.

The following uses the NB-IoT system to share a GSM carrier as an example to describe in detail the implementation manners of the embodiments of the present application.

NB-IoT system and GSM use a set of carriers in the same frequency band. Among them, NB-IoT system and GSM have their own control carriers; NB-IoT system and GSM only share data carriers, that is, the NB-IoT system is on the Non-Anchor carrier. When the resources are insufficient, use the GSM data carrier to send the information that the Non-Anchor carrier needs to send. The NB-IoT system and GSM send control signaling and scheduling commands on their respective control carriers. The NB-IoT system and GSM negotiate how to share the data carrier with each other, and alternately use the data carrier to send related services. The interference between the NB-IoT system and GSM is avoided by configuring non-interfering carriers or carrier isolation.

The control nodes shared by the NB-IoT system and the GSM carrier are: eNodeB (Evolved NodeB) and base station controller (BSC). The eNodeB and BSC control whether to use the NB-IoT system and GSM, respectively. Carrier sharing function between. As shown in Figure 8, the GSM BSC and the Mobility Management Entity (MME) create a new interface. The MME transparently transmits the content that needs to be exchanged between the BSC and the eNodeB.

In an example, when the number of users in GSM decreases, the GSM spectrum resources are underutilized. The BSC evaluates the load status of its own carrier (such as the current power usage of the carrier), and then gradually migrates the user to one or several Carriers, so that user data is sent on several carriers in a concentrated manner, and the remaining carriers are vacated for energy-saving sleep. With the use of NB-IoT base stations deployed in the same frequency band, with the increase of users, when spectrum resources are insufficient, GSM spectrum resources can be shared.

Referring to FIG. 9, the method includes:

Step 900: Configure a third correspondence relationship between the cell identifier of the eNodeB and the cell identifier of the BSC in the eNodeB in advance.

In this step, the cell identifier of the eNodeB that satisfies the third correspondence relationship can share the carrier corresponding to the cell identifier of the BSC. For example, if cell 11 of eNodeB and cell 21 of BSC satisfy the third correspondence relationship, then cell 11 of eNodeB can share the carrier corresponding to cell 21 of BSC; cell 12 of eNodeB and cell 22 of BSC do not satisfy the third correspondence, then eNodeB The cell 21 of cannot share the carrier corresponding to the cell 22 of the BSC.

Step 901: The eNodeB determines whether its own carrier resources are sufficient. When its own carrier resources are insufficient, the eNodeB sends a carrier sharing request to the BSC through the MME. The carrier sharing request includes the cell identifier between the carrier identifier of the carrier with insufficient resources of the eNodeB and the cell identifier of the BSC. The third correspondence relationship; when the carrier resources of the carrier are sufficient, the process ends.

In this step, the eNodeB determines whether its own carrier resources are sufficient by at least one of the following: the current power used by the carrier and the number of PRBs currently used by the carrier.

When the current power used by the carrier or the number of PRBs currently used by the carrier is greater than or equal to the first predetermined threshold, it means that the carrier resources of the NB-IoT system are tight and need to share GSM idle carrier resources. At this time, the eNodeB can perform carrier sharing through the MME The BSC (that is, the BSC corresponding to the cell identifier of the BSC in the third correspondence in the carrier sharing request) sends the carrier sharing request.

If the eNodeB does not receive a BSC response message within a timer duration, it will re-initiate a carrier sharing request.

In this step, the MME transparently transmits the carrier sharing request.

Step 902: The BSC sends a response message to the eNodeB, indicating that a carrier sharing request is received.

Step 903: The BSC evaluates the load condition of the carrier corresponding to the cell identifier of the BSC in the third correspondence in the carrier sharing request, and periodically sends a first message to the eNodeB through the MME according to the load condition of the carrier. The first message includes the cell of the BSC. The first correspondence between the identification and the frequency value of the idle carrier.

In this step, when the BSC has no idle carrier, the frequency value of the idle carrier is null.

Step 904: When the frequency value of the idle carrier in the first message is not empty, the eNodeB transmits data on the idle carrier, and sends a second message to the BSC through the MME. The second message includes the cell identifier of the eNodeB and the occupied The second correspondence between the frequency points of the carriers; when the frequency point of the idle carrier in the first message is empty, the eNodeB waits for the next period to receive the first message.

Step 905: When the BSC needs to recover the carrier occupied by the eNodeB, send a fifth message to the eNodeB through the MME. The fifth message includes a fourth correspondence between the cell identifier of the BSC and the frequency point value of the carrier to be recovered.

Step 906: The eNodeB sends a response message to the BSC through the MME, indicating that the fifth message is received.

Step 907: The eNodeB releases the carrier to be recovered in the fifth message. After the release is completed, a sixth message is sent to the BSC through the MME. The sixth message includes a fifth correspondence between the cell identifier of the eNodeB and the frequency value of the released carrier. relationship.

Step 908: The BSC transmits data on the released carrier in the sixth message.

FIG. 10 is an interaction schematic diagram of a carrier sharing method proposed in the implementation of this application. Referring to FIG. 10, the method includes:

Step 1000: Configure a third correspondence relationship between the cell identifier of the eNodeB and the cell identifier of the BSC in the BSC in advance.

Step 1001: The eNodeB determines whether its own carrier resources are sufficient. When its own carrier resources are insufficient, the eNodeB sends a carrier sharing request to the BSC through the MME. The carrier sharing request includes the cell identifier corresponding to the carrier with insufficient resources of the eNodeB. When its own carrier resources are sufficient, End this process.

When the current power used by the carrier or the number of PRBs currently used by the carrier is greater than or equal to the first predetermined threshold, it means that the carrier resources of the NB-IoT system are tight and need to share GSM idle carrier resources. At this time, the eNodeB can perform carrier sharing through the MME. The BSC (that is, the BSC corresponding to the cell identifier of the BSC in the third correspondence in the carrier sharing request) sends the carrier sharing request.

In this step, the MME transparently transmits the carrier sharing request.

Step 1002: The BSC sends a response message to the eNodeB, indicating that a carrier sharing request is received.

Step 1003: The BSC searches for a preset third correspondence to find the cell identifier of the BSC corresponding to the cell identifier of the carrier with insufficient resources of the eNodeB in the carrier sharing request, and evaluates the load status of the carrier corresponding to the cell identifier of the found BSC. , Periodically sending a first message to the eNodeB through the MME according to the load condition of the carrier. The first message includes a first correspondence between a cell identifier of the eNodeB, a cell identifier of the BSC, and a frequency value of an idle carrier.

Step 1004: When the frequency value of the idle carrier in the first message is not empty, the eNodeB transmits data on the idle carrier, and sends a second message to the BSC through the MME. The second message includes the cell identifier and occupied The second correspondence between the frequency points of the carriers; when the frequency point of the idle carrier in the first message is empty, the eNodeB waits for the next period to receive the first message.

Step 1005: When the BSC needs to recover the carrier occupied by the eNodeB, send a fifth message to the eNodeB through the MME. The fifth message includes a fourth correspondence between the cell identifier of the BSC and the frequency point value of the carrier to be recovered.

Step 1006: The eNodeB sends a response message to the BSC through the MME, indicating that the fifth message is received.

Step 1007: The eNodeB releases the carrier to be recovered in the fifth message. After the release is completed, a sixth message is sent to the BSC through the MME. The sixth message includes a fifth correspondence between the cell identifier of the eNodeB and the frequency of the released carrier relationship.

Step 1008: The BSC transmits data on the released carrier in the sixth message.

In one example, GSM enables carrier sharing within a shared time period.

FIG. 11 is an interaction schematic diagram of a carrier sharing method proposed in the implementation of this application. Referring to FIG. 11, the method includes:

Step 1100: Configure a shared time period (for example, 22:00 to 06:00) in which carrier sharing with the NB-IoT can be performed on the BSC of the GSM in advance; at the same time, configure the first time between the cell identity of the eNodeB and the cell identity of the BSC on the BSC. Three correspondences.

Step 1101: At the beginning of the configured sharing time period (for example, 22:00), the GSM evaluates the load condition of its own carrier and releases the GSM carrier that can be shared. If no GSM carrier can be released, no processing is performed.

In this step, the BSC can evaluate the load status of the carrier by at least one of the following: the current power used by the carrier, and the number of users currently carried by the carrier.

In this step, if the GSM has an energy saving function, that is, when the GSM service data is small, the BSC needs to migrate user data to one or several carriers according to the load status of the GSM carriers, and other idle carriers sleep. When GSM traffic comes up, BSC can relocate user data to dormant carriers, making full use of spectrum resources. If GSM does not have the energy-saving function, then the BSC can directly detect the idle carrier.

If NB-IoT receives a certain frequency point being occupied at a certain time, but has not received a notification of an unoccupied event subsequently, then NB-IoT considers that the frequency point is always occupied. That is, if a frequency point is always occupied, GSM does not need to repeat the notification.

Step 1102: The BSC periodically sends a first message to the eNodeB through the MME. The first message includes a first correspondence between a cell identifier of the eNodeB, a cell identifier of the BSC, and a frequency value of an idle carrier.

In this step, the BSC sends the first message only to the eNodeB corresponding to the cell identifier of the eNodeB having the third correspondence relationship with the cell identifier of the BSC corresponding to the idle carrier.

Step 1103: The eNodeB determines whether the carrier resource corresponding to the cell identifier of the eNodeB in the first message is sufficient. When the carrier resource corresponding to the cell identifier of the eNodeB in the first message is insufficient, data is transmitted on the idle carrier in the first message. And periodically send a second message to the BSC through the MME, the second message includes a second correspondence between the cell identifier of the eNodeB and the frequency value of the occupied carrier; when the carrier corresponding to the cell identifier of the eNodeB in the first message corresponds When resources are sufficient, the frequency value of the carrier occupied in the second message sent to the BSC is empty.

Step 1104: When the eNodeB does not need to use the carrier of the BSC, it releases the unused carrier, and sends a sixth message to the BSC through the MME. The sixth message includes the first between the cell identifier of the eNodeB and the frequency value of the released carrier. Five correspondences.

Step 1105: At the end of the shared time period (for example, 06:00), the BSC sends a fifth message to the eNodeB through the MME. The fifth message includes a fourth correspondence between the cell identity of the BSC and the frequency value of the carrier to be recovered. Relationship, indicating the carrier that needs to be recycled.

Step 1106: The eNodeB releases the carrier to be recovered, and sends a sixth message to the BSC through the MME. The sixth message includes a fifth correspondence between the cell identifier of the eNodeB and the frequency value of the released carrier.

Step 1107: The BSC transmits data on the released carrier in the sixth message.

In one example, GSM enables carrier sharing within a shared time period.

FIG. 12 is an interaction schematic diagram of a carrier sharing method according to an embodiment of the present application. Referring to FIG. 12, the method includes:

Step 1200: Configure a shared time period (eg, 22:00 to 06:00) in which carrier sharing with the NB-IoT can be performed in the BSC of the GSM in advance; at the same time, configure the eNodeB cell ID and the BSC cell ID in the eNodeB. Three correspondences.

Step 1201: At the beginning of the configured sharing time period (for example, 22:00), GSM evaluates the load status of its own carrier and releases the GSM carrier that can be shared. If no GSM carrier can be released, no processing is performed.

Step 1202: The BSC periodically sends a first message to the eNodeB through the MME. The first message includes a first correspondence between a cell identifier of the BSC and a frequency value of an idle carrier.

Step 1203: The eNodeB searches for the cell identifier of the eNodeB corresponding to the cell identifier of the BSC in the first message in the third correspondence, and determines whether the carrier resource corresponding to the cell identifier of the found eNodeB is sufficient. When the cell identifier of the eNodeB is found, When the corresponding carrier resource is insufficient, data is transmitted on the idle carrier in the first message, and a second message is periodically sent to the BSC through the MME. The second message includes the cell ID of the eNodeB and the frequency value of the occupied carrier. When the carrier resources corresponding to the cell identity of the found eNodeB are sufficient, the frequency value of the carrier occupied in the second message sent to the BSC is empty.

Step 1204: When the eNodeB does not need to use the carrier of the BSC, it releases the unused carrier, and sends a sixth message to the BSC through the MME. The sixth message includes the first message between the eNodeB's cell identity and the frequency value of the released carrier. Five correspondences.

Step 1205: At the end of the shared time period (for example, 06:00), the BSC sends a fifth message to the eNodeB through the MME. The fifth message includes a fourth correspondence between the cell identity of the BSC and the frequency value of the carrier to be recovered. Relationship, indicating the carrier that needs to be recycled.

Step 1206: The eNodeB releases the carrier to be recovered, and sends a sixth message to the BSC through the MME. The sixth message includes a fifth correspondence between the cell identity of the eNodeB and the frequency value of the released carrier.

Step 1207: The BSC transmits data on the released carrier in the sixth message.

Although the implementation manners disclosed in the examples of the present application are as above, the content described is only the implementation manners for facilitating the understanding of the examples of the present application, and is not intended to limit the examples of the present application. Any person skilled in the art to which this embodiment of the present application belongs can make any modifications and changes in the form and details of implementation without departing from the spirit and scope disclosed in this embodiment of the present application. The scope of patent protection shall still be subject to the scope defined by the appended claims.

Claims

A carrier sharing method includes:

When the first communication node determines that its own carrier resources are insufficient and receives a first message from a second communication node, the first communication node transmits data on an idle carrier; wherein the first message includes: a second A first correspondence between a cell identifier of a communication node and carrier information of an idle carrier;

Sending, by the first communication node, a second message to the second communication node, the second message includes: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

The first communication node and the second communication node belong to different communication systems.
The carrier sharing method according to claim 1, wherein when the first communication node determines that its own carrier resources are insufficient, before the receiving the first message from the second communication node, the method further comprises:

The first communication node sends a third message to the second communication node, the third message includes a cell identifier corresponding to a carrier with insufficient resources of the first communication node, or a carrier with insufficient resources of the first communication node A third correspondence relationship between the corresponding cell identifier and the cell identifier of the second communication node.
The carrier sharing method according to claim 1 or 2, wherein the method further comprises:

When the first communication node receives a fifth message, the fifth message includes a fourth correspondence between a cell identifier of the second communication node and carrier information of a carrier to be recovered;

The first communication node releases the carrier that needs to be recovered, and sends a sixth message to the second communication node, where the sixth message includes the cell identifier of the first communication node and the carrier information of the released carrier. The fifth correspondence relationship.
The carrier sharing method according to claim 1 or 2, wherein an absolute value of a difference between a spectrum bandwidth of a carrier of the first communication node and a spectrum bandwidth of a carrier of the second communication node is less than or equal to a preset threshold.
A carrier sharing method includes:

The second communication node evaluates the load status of its own carrier, and sends a first message to the first communication node according to the load status of its own carrier. The first message includes: the cell identifier of the second communication node and carrier information of the idle carrier. A first correspondence relationship between them;

Receiving, by the second communication node, a second message of the first communication node, the second message includes: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

The first communication node and the second communication node belong to different communication systems.
The carrier sharing method according to claim 5, wherein before the second communication node evaluates the load condition of its own carrier, the method further comprises:

Receiving, by the second communication node, a third message of the first communication node, the third message includes: a cell identifier of the first communication node, or a cell identifier of the first communication node and the first communication node A third correspondence relationship between the cell identifiers of the two communication nodes;

The evaluating, by the second communication node, the load status of the carrier includes:

The second communication node evaluates a load condition of a carrier corresponding to a cell identifier of the second communication node in the third correspondence.
The carrier sharing method according to claim 5, wherein the second communication node evaluates a load condition of its own carrier within a shared time period.
The carrier sharing method according to any one of claims 5 to 7, wherein the method further comprises:

When the second communication node needs to recover a carrier that has been occupied by the first communication node, the second communication node sends a fifth message to the first communication node, where the fifth message includes: a cell identifier of the second communication node A fourth correspondence relationship with the carrier information of the carrier to be recovered;

Receiving, by the second communication node, a sixth message of the first communication node, the sixth message includes: a fifth correspondence between a cell identifier of the first communication node and carrier information of a released carrier .
A carrier sharing device includes:

A first determining module configured to determine that its own carrier resource is insufficient;

A first receiving module configured to receive a first message of a second communication node, the first message including: a first correspondence between a cell identifier of the second communication node and carrier information of an idle carrier;

A first sending module configured to transmit data on the idle carrier; sending a second message to the second communication node, the second message including: a cell identifier of the first communication node and carrier information of an occupied carrier A second correspondence relationship between them; wherein the first communication node and the second communication node belong to different communication systems.
A carrier sharing device includes:

The second sending module is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier, where the first message includes a cell identifier of the second communication node and an idle carrier. A first correspondence relationship between the carrier information of

A second receiving module configured to receive a second message of the first communication node, the second message including: a second correspondence between a cell identifier of the first communication node and carrier information of an occupied carrier;

The first communication node and the second communication node belong to different communication systems.
A carrier sharing device includes a processor and a computer-readable storage medium, and the computer-readable storage medium stores instructions. When the instructions are executed by the processor, the device implements any one of claims 1 to 8. The carrier sharing method.
A computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the steps of the carrier sharing method according to any one of claims 1 to 8 are implemented.
A carrier sharing system includes:

A first communication node configured to transmit data on the idle carrier when it is determined that its own carrier resources are insufficient and a first message from a second communication node is received; and send a second message to the second communication node; The first message includes a first correspondence between a cell identifier of a second communication node and carrier information of an idle carrier, and the second message includes: a cell identifier of the first communication node and a carrier of the occupied carrier. A second correspondence relationship between carrier information; the first communication node and the second communication node belong to different communication systems;

The second communication node is configured to evaluate a load condition of the own carrier, and send a first message to the first communication node according to the load condition of the own carrier; and receive a second message of the first communication node.