Method for configuring global identification of evolution cell of ground wireless access network of relay node
Technical Field
The invention relates to the technical field of wireless communication, in particular to a method for configuring global identity of a terrestrial radio access network evolution cell of a Relay Node (RN).
Background
According to the demand of Advanced international mobile telecommunications (IMT-Advanced), a future generation of wireless communication system should satisfy transmission characteristics up to 1Gbps rate to support various data services that are continuously emerging. In order to meet the requirement of IMT-Advanced, 3GPP has conducted research on the project of enhanced long term evolution system (LTE-Advanced). Key technologies of the LTE-Advanced system include multiple antenna enhancement (Enhanced MIMO), Carrier Aggregation (CA), Relaying (Relaying), and Coordinated Multi-point (CoMP).
Among several key technologies of LTE-Advanced, relay technology is used to provide low cost coverage and improve cell edge throughput. The relay refers to a Relay Node (RN) accessing a network via a cell of a donor evolved base station (DeNB) to serve a User Equipment (UE) like an evolved base station (eNB). Under the normal working state of the RN (providing service for the UE like the eNB), the interface between the RN and the UE is a Uu interface, and the interface between the RN and the DeNB is a Un interface. From the UE perspective, RN is eNB. At the Un interface, the RN shares radio resources with UEs served by the DeNB cell.
In LTE, an evolved universal terrestrial radio access Network (ECGI) Cell Global Identity (E-UTRANCell Global Identity) is composed of a Public Land Mobile Network (PLMN) Identity and a Cell Identity (CI) to which a Cell belongs, and is used to globally identify the Cell. The PLMN identity is composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). The CI has 28 bits in total, and the leftmost 20 bits (20leftmost bits) are eNB ID information for identifying the eNB in the PLMN.
Each cell broadcasts its own CI and its own list of supported PLMN identities. The first PLMN in the PLMN identity list is the primary PLMN (primary PLMN) of the cell, and the primary PLMN and the CI form the ECGI of the cell.
In LTE-a relay technology, the RN serves the UE like an eNB. An RN operation and maintenance (OAM) entity configures parameters for the RN to ensure the RN operates normally. Since the RN communicates with an Evolved Packet Core (EPC) through the eNB/DeNB and accesses the RN OAM entity through the EPC, data communicated between the RN OAM entity and the RN physically passes through the eNB/DeNB. The eNB ID of the RN is the same as the eNB ID of the DeNB accessed by the RN.
In the parameters configured by the RN OAM entity for the RN, configuring a globally unique ECGI for the RN is an important content for ensuring the normal operation of the RN, however, a specific implementation method for the content is not available in the prior art.
Disclosure of Invention
In view of this, the present invention provides a method for configuring an ECGI of an RN, so as to configure an ECGI having global uniqueness for the RN, thereby ensuring that the RN operates normally.
The method is realized by the following technical scheme:
a method for configuring a terrestrial radio access network Evolved Cell Global Identity (ECGI) of a Relay Node (RN), the method comprising:
the RN operation and maintenance OAM entity determines the number of cells allocated to the RN and cell identification CI group information allocated to each RN cell; each CI in the CI group is unique in a cell of a donor evolution base station DeNB accessed by the RN and all RN cells under the DeNB, and the number of the CIs in the CI group is the same as the number of the cells allocated to the RN;
and the RN OAM entity configures a PLMN identification for each RN cell, configures CI for each RN cell according to the CI group information, and sends ECGI information of the RN to the RN.
Wherein, the determining, by the RN OAM entity, CI group information allocated to each RN cell specifically includes:
the RN OAM entity sends the cell number information distributed for the RN to the RN;
the RN reports the cell number information to a DeNB;
the DeNB allocates CI groups for the RN cells according to the reported cell number information and sends the CI group information allocated for the RN cells to the RN; or the DeNB reports the cell number information reported by the RN to a DeNB OAM entity, the DeNB OAM entity allocates a CI group for each RN cell according to the cell number information reported by the DeNB and sends the CI group information allocated for each RN cell to the DeNB, and the DeNB sends the received CI group information from the DeNB OAM entity to the RN;
and the RN sends the CI group information distributed for each RN cell to the RN OAM entity.
Or, the determining, by the RN OAM entity, CI group information allocated to each RN cell specifically includes:
the RN OAM entity sends the cell number information allocated for the RN to a DeNB OAM entity;
and the DeNB OAM entity allocates a CI group for the RN according to the cell number information allocated for the RN and sends the information of the CI group to the RN OAM entity.
Or, the determining, by the RN OAM entity, CI group information allocated to each RN cell specifically includes:
the RN OAM entity requests CI information or ECGI information of each cell of the DeNB to the DeNB OAM entity;
after receiving the request, the DeNB OAM entity sends CI information or ECGI information of each cell of the DeNB to the RN OAM entity;
and the RN OAM entity allocates a CI group for the RN according to the CI information or the ECGI information of each cell of the DeNB.
In addition, the allocating, by the RN OAM entity, a CI group to the RN according to the CI information or the ECGI information of each cell of the DeNB specifically includes:
the RN OAM entity takes the leftmost 20 bits of the CI information of each cell of the DeNB or the leftmost 20 bits of the CI information in the ECGI information as the leftmost 20 bits of each CI in the CI group allocated to the RN, and the rightmost 8 bits of each CI in the CI group allocated to the RN are different from the rightmost 8 bits of the CI information of each cell of the DeNB or the rightmost 8 bits of the CI information in the ECGI information.
Preferably, the information of the CI group sent to the RN OAM entity includes only rightmost 8 bits of each CI;
the RN OAM entity also acquires DeNB ID information of a DeNB to which the RN belongs, and the DeNBID information is used as the leftmost 20 bits of each CI in the information of the CI group.
Wherein, the configuring, by the RN OAM entity, the primary PLMN identifier for each RN cell specifically includes:
and the RN OAM entity configures a PLMN identification list for each RN cell and indicates a primary PLMN identification in the list, or directly configures the primary PLMN identification for each RN cell.
Preferably, the information on the number of cells allocated to the RN includes: primary PLMN identifications distributed for the RNs and the number of cells corresponding to each primary PLMN identification;
the CI group information is: allocating primary PLMN identifications and CI groups corresponding to each primary PLMN identification for the RNs; in the CI group corresponding to each PLMN identity, each CI is unique in the DeNB corresponding to the PLMN identity and all RN cells under the DeNB.
Wherein configuring CI for each RN cell according to the CI group information includes:
and sequentially allocating each CI in the CI group to each RN cell, or allocating each CI in the CI group to each RN cell according to a preset rule.
The sending of the ECGI information of the RN to the RN specifically includes: sending CI information and main PLMN identification information configured for each RN cell to the RN; or, sending the ECGI formed by the CI configured for each RN cell and the primary PLMN identity to the RN.
In addition, the determining, by the RN OAM entity, the number of cells allocated to the RN specifically includes:
the RN OAM entity determines the number of cells allocated to the RN according to the maintained information of the RN; or,
the RN sends the requested cell number information to an RN OAM entity or sends the cell number information prepared and generated by the RN or sends the maximum cell number information which can be supported by the RN or the hardware capability information of the RN; and the RN OAM entity allocates the cell number to the RN according to the information sent by the RN and the maintained information of the RN or according to the information sent by the RN.
A method for configuring a terrestrial radio access network Evolved Cell Global Identity (ECGI) of a Relay Node (RN), the method comprising:
the RN acquires the cell number distributed for the RN and a primary Public Land Mobile Network (PLMN) identifier configured for each RN cell from an RN operation and maintenance (OAM) entity, and sends the cell number information distributed for the RN to a donor evolution base station (DeNB);
the DeNB sends cell identification CI group information distributed for each RN cell to the RN; or the DeNB sends the cell number information allocated to the RN to a DeNB OAM entity, the DeNBOAM entity sends the CI group information allocated to each RN cell to the DeNB, and the DeNB forwards the CI group information to the RN; each CI in the CI group is unique in a cell of a DeNB accessed by the RN and all RN cells under the DeNB, and the number of the CIs in the CI group is the same as the number of the cells allocated to the RN;
and the RN configures CI for each RN cell according to the CI group information and determines the ECGI of each RN cell by using the CI configured for each RN cell and the identification information of the primary PLMN.
The acquiring, by the RN from the RN OAM entity, the cell number allocated to the RN and the primary PLMN identifier configured for each RN cell specifically include:
the RN OAM entity determines the number of cells allocated to the RN and sends an index value and a primary PLMN identification allocated to each RN cell to the RN;
and the RN determines the number of the cells allocated to the RN according to the number of the index values.
In addition, the determining, by the RN OAM entity, the number of cells allocated to the RN specifically includes:
the RN OAM entity determines the number of cells allocated to the RN according to the maintained information of the RN; or,
the RN sends the requested cell number information to an RN OAM entity or sends the cell number information prepared and generated by the RN or sends the maximum cell number information which can be supported by the RN or the hardware capability information of the RN; and the RN OAM entity allocates the cell number for the RN according to the information sent by the RN and the maintained information of the RN or according to the information sent by the RN.
Specifically, configuring the primary PLMN identifier for each RN cell specifically includes:
and the RN OAM entity configures a PLMN identification list for each RN cell and indicates a primary PLMN identification in the list, or directly configures the primary PLMN identification for each RN cell.
Preferably, the information of the CI group sent to the RN only includes rightmost 8 bits of each CI;
the RN also acquires DeNB ID information from a system information block broadcast by the DeNB to which the RN belongs, and the DeNB ID information is used as the leftmost 20 bits of each CI in the information of the CI group.
The information on the number of cells allocated to the RN includes: primary PLMN identifications distributed for the RNs and the number of cells corresponding to each primary PLMN identification;
the CI group information is: allocating primary PLMN identifications and CI groups corresponding to each primary PLMN identification for the RNs; in the CI group corresponding to each PLMN identity, each CI is unique in the DeNB corresponding to the PLMN identity and all RN cells under the DeNB.
According to the technical scheme, the invention provides two specific methods for configuring the ECGI of the RN, and the ECGI configured for the RN has global uniqueness by the methods, so that the RN is ensured to normally work.
Drawings
FIG. 1 is a flowchart of a method provided in accordance with an embodiment of the present invention;
FIG. 2 is a flowchart of a method provided in a second embodiment of the present invention;
FIG. 3 is a flowchart of a method provided in a third embodiment of the present invention;
fig. 4 is a flowchart of a method according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.
The method provided by the invention mainly comprises the following steps:
the above process is described in detail below by means of several specific examples.
The first embodiment,
Fig. 1 is a flowchart of a method provided in an embodiment of the present invention, and as shown in fig. 1, the method may include the following steps:
step 101: and the RN sends the cell number information of the RN to an RN OAM entity.
In this step, the RN may send the requested number of cells to the RN OAM entity, or may send the number of cells that the RN prepares to generate, or send the maximum number of cells that the RN can support, or the hardware capability of the RN to the RN OAM entity.
Simultaneously with step 101, the RN may communicate with the EPC through the eNB, and at this time, the cell data information sent by the RN to the RN OAM entity is physically sent to the RN OAM entity through the eNB; alternatively, the RN may communicate with the EPC through the DeNB, and in this case, the cell number information transmitted by the RN to the RN OAM entity is physically transmitted to the RN OAM entity through the DeNB.
In addition, it should be noted that step 101 is an optional step, and may not be performed, and the RN OAM entity directly determines the number of cells of the RN according to the information maintained by itself, where the information maintained by itself may include: the RN capability, type, or location of deployment, etc. are the same in the following embodiments, and are not described in detail.
Step 102: the RN OAM entity determines the number of cells configured for the RNs and sends an index value allocated to each cell of the RNs and a primary PLMN identification to the RNs.
If step 101 is executed, the RN OAM entity may determine the number of cells configured for the RN according to the number information of cells sent by the RN and the maintained information of the RN, or according to the hardware capability information sent by the RN, or according to the number information of cells sent by the RN, or according to the information of the RN maintained by itself. If step 101 is not executed, the RN OAM entity directly determines the number of cells configured for the RN according to the information maintained by itself. The number of cells configured for the RN is a positive integer.
In this step, the index value allocated to the cell of the RN satisfies the following condition: the cell assigned index value of each RN is unique within the RN. The index value range is related to the number of cells that can be configured for all RNs, e.g. the index value range may be 0, 255, considering that the rightmost 8 bits of the CI can only carry 256 identities at most. The RN may determine the number of cells allocated to the RN according to the number of index values.
The allocating, by the RN OAM entity, the primary PLMN identity for each RN cell may include: configuring a PLMN identification list for each RN cell and indicating a primary PLMN, wherein the primary PLMN can be positioned at the first position of the PLMN identification list; or, the RN OAM entity directly configures the primary PLMN identity for the cell of each RN.
The RN OAM entity may carry the index value and the primary PLMN identity of each RN cell in the cell configuration information and send the cell configuration information to the RN. In addition, the cell configuration information may further include cell parameters of each RN cell, such as a cell maximum transmission power, a reference signal parameter, and the like.
Meanwhile, the RN may communicate with the EPC through the eNB, and the configuration information sent by the RN OAM entity to the RN may be physically through the eNB; alternatively, the RN may communicate with the EPC through the DeNB, and in this case, the configuration information transmitted by the RN OAM entity to the RN may physically pass through the DeNB.
Step 103: and the RN reports the cell number information configured for the RN to the DeNB.
And after receiving the cell configuration information from the RN OAM entity, the RN reports the number of the cells configured for the RN to the DeNB.
The cell number information transmitted by the RN to the DeNB may be in the form of a special Information Element (IE) for the RN in a Radio Resource Control (RRC) message, or may be a dedicated RRC message for the RN or an IE in the dedicated RRC message.
Step 104: and the DeNB allocates CI groups for the RNs according to the cell number reported by the RNs and sends the information of the CI groups to the RNs.
Wherein, the number of CIs in the CI group may be the number of cells reported by the RN.
The assignment of CI groups satisfies the following condition: each CI in the CI group is unique in the cell of the DeNB and in the cells of all RNs under the DeNB. The DeNB may record the CI group allocated for the RN to support subsequent CI allocations.
The information of the CI group sent by the DeNB to the RN may be in the form of a special IE for the RN in an RRC message, or may be a dedicated RRC message for the RN or an IE in the dedicated RRC message.
Preferably, in order to save air interface resources, each CI in the information of the CI group sent to the RN in this step may be only 8 rightmost bits of the CI.
Step 105: and the RN allocates the CIs in the obtained CI group to each cell of the RN, and the CIs allocated to the cells and the primary PLMN identification form the ECGI of the cells.
The RN may allocate each CI in the CI group to each cell of the RN in sequence or according to a preset rule. Specifically, the CI may be directly allocated to each cell of the RN, or may be bound to an index value of the allocated cell of the RN.
Since the primary PLMN identity and CI of the cell are the ECGI that constitutes the cell, the method ensures the global uniqueness of the ECGI of the RN.
If the CI group information sent in step 104 is 8 rightmost bits of each CI, before or simultaneously with step 105, the RN obtains the CI value of the accessed DeNB cell from a System Information Block (SIB)1 broadcasted by the DeNB, obtains the eNB ID of the DeNB from the first 20 bits of the CI value, and obtains the CI allocated to the RN from the 8 rightmost bits of the received CI and the eNB ID of the DeNB.
In addition to the method shown in fig. 1, the CI group of the RN cell may also be configured by the DeNB OAM entity, in this case, in step 104, when the DeNB receives the cell number information from the RN, the DeNB OAM entity sends the cell number information to the DeNB OAM entity as the newly added cell number of the DeNB itself, the DeNB OAM entity configures the CI group according to the cell number and sends the CI group to the DeNB, meanwhile, the DeNB OAM entity records the configured CI group to support the subsequent cell configuration, and after the DeNB receives the CI group configured by the DeNB OAM entity, the DeNB sends the CI group configured by the DeNB OAM entity to the RN.
The process shown in fig. 1 may be applied on the following premise: the RN OAM entity cannot obtain ECGI information of the DeNB and all cells of all RNs below the DeNB from the DeNB OAM entity; or, any other possible precondition.
In addition to the manner described in the above flow, if there are multiple primary PLMN identities allocated to the RN, in step 103, the cell number information reported by the RN to the DeNB may specifically be: and each primary PLMN identification corresponding to the RN and the number of cells corresponding to each primary PLMN identification. And the CI group corresponding to the RN allocated by the DeNB, sent to the RN and recorded by the DeNB itself can be as follows: and each primary PLMN identification corresponding to the RN and the CI group corresponding to each primary PLMN identification. The assignment conditions for the CI group may be: in the CI group corresponding to each PLMN identity, each CI is unique in the DeNB corresponding to the PLMN identity and the cells of all RNs under the DeNB. The method can make the maximum number of cells served by the DeNB and all RNs accessing the DeNB possibly exceed 256.
In the above situation, the CI group corresponding to each primary PLMN identifier of the RN cell may also be configured by the DeNB OAM entity, and when the DeNB receives the cell number information corresponding to each primary PLMN identifier from the RN, the DeNB OAM entity sends the cell number information corresponding to each primary PLMN identifier to the DeNB OAM entity as information of a newly added cell of the DeNB itself, the DeNB OAM entity configures, according to the cell number information corresponding to each primary PLMN identifier, the CI group corresponding to each primary PLMN identifier and sends the CI group configured for the cell corresponding to each primary PLMN identifier to the DeNB and records the configuration information for subsequent cell configuration, and after the DeNB receives the CI group of the cell corresponding to each primary PLMN identifier configured by the DeNB OAM entity, the CI group of the cell corresponding to each primary PLMN identifier configured by the DeNB OAM entity is sent to the RN.
Example II,
Fig. 2 is a flowchart of a method according to a second embodiment of the present invention, and as shown in fig. 2, the method may include the following steps:
step 201: and the RN OAM entity determines the number of the cells configured for the RN and sends the information of the number of the cells configured for the RN to the RN.
The method by which the RN OAM entity determines the number of cells configured for the RN may be the method in embodiment step 101 and step 102.
If the RN is communicated with the EPC through the eNB, the cell number information sent by the RN to the RN OAM entity is physically passed through the eNB; alternatively, if the RN is in communication with the EPC via the DeNB, the cell number information transmitted by the RN to the RN OAM entity is physically via the DeNB.
Step 202: and the RN sends the cell number information configured for the RN to the DeNB.
And after receiving the cell number information configured by the RN OAM entity for the RN, the RN reports the cell number information of the RN to the DeNB. The cell number information sent by the RN to the DeNB may be in the form of a special IE for the RN in an RRC message, or may be a dedicated RRC message for the RN or an IE in the dedicated RRC message.
Step 203: and the DeNB allocates a CI group for the RN according to the cell number information reported by the RN and sends the information of the CI group to the RN.
Wherein, the number of CIs in the CI group may be: the number of cells reported by the RN.
The assignment of CI groups satisfies the following condition: each CI in the CI group is unique in the cell of the DeNB and in the cells of all RNs under the DeNB. The DeNB may record the CI group allocated for the RN to support subsequent CI allocations.
The information of the CI group sent by the DeNB to the RN may be in the form of a special IE for the RN in an RRC message, or may be a dedicated RRC message for the RN or an IE in the dedicated RRC message.
Preferably, in order to save air interface resources, each CI in the information of the CI group sent to the RN in this step may be only 8 rightmost bits of the CI.
Step 204: and the RN sends the received information of the CI group to the RN OAM entity.
Meanwhile, the RN communicates with the EPC through the DeNB, and the information of the CI group transmitted to the RN by the RN OAM entity is physically through the DeNB.
If the CI group information sent in step 203 is 8 rightmost bits of each CI, before or simultaneously with step 204, the RN obtains the CI value of the accessed DeNB cell from SIB1 broadcast by the DeNB, obtains the eNB ID of the DeNB from the first 20 bits of the CI value, and obtains the CI allocated to the RN from the 8 rightmost bits of the received CI and the eNB ID of the DeNB. Alternatively, the information of the CI group sent by the RN to the RN OAM entity is the right 8 bits of each CI, and the eNB ID of the DeNB is sent to the RN OAM entity at the same time as the RN step 204 or before the step 204.
Step 205: and the RN OAM entity allocates a CI for each RN cell by using the received CI group and the information maintained by the RN OAM entity, allocates a main PLMN mark for each RN cell, and sends the information of the ECGI of the RN to the RN.
The allocating, by the RN OAM entity, the primary PLMN identity for each RN cell may include: configuring a PLMN identification list for each RN cell and indicating a primary PLMN, wherein the primary PLMN can be positioned at the first position of the PLMN identification list; or, the RN OAM entity directly configures the primary PLMN identity for the cell of each RN.
In addition, the RN OAM entity may also configure other parameters for the RN cell, such as cell maximum transmission power, reference signal parameters, etc.
The RN OAM entity sends the CI configured for the RN and the main PLMN identification to the RN; or directly sending the ECGI formed by the CI and the primary PLMN identification to the RN. Meanwhile, the PLMN list and other parameters of the RN cell may also be sent to the RN.
The information of the ECGI sent by the RN OAM entity to the RN may be physically via the DeNB.
Preferably, in order to save air interface resources, the CI information sent by the RN OAM entity to the RN in this step may be only 8 rightmost bits of the CI. At the same time or before the step, the RN obtains the CI of the accessed cell from the system information block broadcast by the DeNB, and obtains the eNB ID of the DeNB, that is, the eNB ID of the RN from the leftmost 20 bits of the CI, in this case, the RN obtains the CI of each cell from the rightmost 8 bits of the CI of each RN cell from the RN OAM entity and the eNB ID of the RN.
If the RN OAM entity receives 8 rightmost bits of CI in step 204, then in step 205, the CI is obtained according to the received or maintained eNB ID of RN (i.e. eNB ID of DeNB) and the received 8 rightmost bits of CI.
Optionally, the CI group of the RN cell may also be configured by the DeNB OAM entity, then in step 203, when the DeNB receives the cell number information from the RN, the DeNB sends the cell number information to the DeNB OAM entity as a newly added cell number of the DeNB itself, the DeNB OAM entity configures the CI group according to the cell number and sends the CI group to the DeNB, and then the DeNB sends the CI group configured by the DeNB OAM entity to the RN.
The process shown in fig. 2 may be applied on the following premise: the RN OAM entity cannot obtain ECGI information of the DeNB and all cells of all RNs below the DeNB from the DeNB OAM entity; or, any other possible precondition.
In addition, in addition to the manner described in the above flow, if there are multiple primary PLMN identities allocated to the RN, in step 201, the number of cells configured by the RN OAM entity for the RN may be: and the number of cells corresponding to each primary PLMN identification and each primary PLMN identification corresponding to the RN. In step 202, the number of cells sent by the RN to the DeNB may be: and the number of cells corresponding to each primary PLMN identification and each primary PLMN identification corresponding to the RN. In step 203, the CI group information configured by the DeNB for the RN, sent to the RN, and recorded by the DeNB may be: and the primary PLMN identification corresponding to the RN and the CI group corresponding to each primary PLMN identification. Accordingly, the assignment condition for the CI group may be: in the CI group corresponding to each PLMN identity, each CI is unique in the DeNB corresponding to the PLMN identity and the cells of all RNs under the DeNB. In step 204, the sending, by the RN, the CI group information to the RN OAM entity may be: and sending each main PLMN identification corresponding to the RN and CI group information corresponding to each main PLMN identification. This approach may make it possible for the maximum number of cells served by the DeNB and all RNs accessing it to exceed 256.
In addition, the CI group corresponding to each primary PLMN identifier of the RN cell may also be configured by the DeNB OAM entity, in this case, when the DeNB receives the cell number information corresponding to each primary PLMN identifier from the RN, the DeNB OAM entity sends the cell number information corresponding to each primary PLMN identifier to the DeNB OAM entity as information of a newly added cell of the DeNB itself, the DeNB OAM entity configures, according to the cell number corresponding to each primary PLMN identifier, the CI group corresponding to each primary PLMN identifier and sends the CI group configured for the cell corresponding to each primary PLMN identifier to the DeNB and records the configuration information for subsequent cell configuration, and after the DeNB receives the CI group of the cell corresponding to each primary PLMN identifier configured by the DeNB OAM entity, the CI group of the cell corresponding to each primary PLMN identifier configured by the DeNB OAM entity is sent to the RN.
Example III,
Fig. 3 is a flowchart of a method according to a third embodiment of the present invention, and as shown in fig. 3, the method may include the following steps:
step 301: and the RN OAM entity determines the number of the cells configured for the RN and sends the information of the number of the cells configured for the RN to the DeNB OAM entity.
The method by which the RN OAM entity determines the number of cells configured for the RN may be the method in embodiment step 101 and step 102.
Step 302: and the DeNB OAM entity allocates CI groups for the RNs according to the received cell number configured for the RNs, and sends the information of the CI groups to the RN OAM entity.
And the DeNB OAM entity determines a CI group allocated to the RN according to the number of the received cells, or according to the number of the received cells, the CI of each cell of the DeNB accessed by the RN and the CI of each cell of all RNs accessed to the DeNB, which are maintained by the DeNB OAM entity.
The number of CIs in the CI group allocated for the RN may be: the number of cells configured for the RN cell.
The assignment of CI groups satisfies the following condition: each CI in the CI group is unique in the DeNB and the cells of all RNs under the DeNB. Meanwhile, the DeNB OAM entity records a CI group allocated for the RN to support subsequent CI allocation.
Step 303: and the RN OAM entity configures CI and a main PLMN mark for each RN cell according to the received CI group information and the information of maintaining the RN by the RN OAM entity, and sends the ECGI information of the RN to the RN.
In this step, the RN OAM entity may send the CI information and the primary PLMN identification information to the RN as ECGI information of the RN, or may send ECGI information configured by the CI and the primary PLMN identification to the RN.
The primary PLMN identification information may be a PLMN identification list and indication information of the primary PLMN identification in the list, for example, the table-head PLMN represents the primary PLMN, or may be a direct primary PLMN identification.
In addition, the RN OAM entity may also send other configuration parameters allocated for the RN, such as cell maximum transmission power, reference signal parameters, etc.
In addition, the information transmitted by the RN OAM entity to the RN may be physically via the DeNB.
Preferably, in order to save air interface resources, the CI information sent by the RN OAM entity to the RN in this step may be only 8 rightmost bits of the CI. At the same time or before the step, the RN obtains the CI of the accessed cell from the system information block broadcast by the DeNB, and obtains the eNB ID of the DeNB, that is, the eNB ID of the RN from the leftmost 20 bits of the CI, in this case, the RN obtains the CI of each cell from the rightmost 8 bits of the CI of each RN cell from the RN OAM entity and the eNB ID of the RN.
In this embodiment, the RN OAM and the DeNB OAM entities may belong to different Domain managers (DM, Domain Manager) to communicate with each other through an Itf-P2P interface, or may communicate through a Network Management System (NMS). For the latter communication mode, the DM of the RN OAM entity communicates with the NMS through an Itf-N interface, and the DM of the DeNB OAM entity communicates with the NMS through an Itf-N interface.
The process shown in fig. 3 may be applied on the following premise: the RN OAM entity may communicate with the denba OAM entity to obtain relevant information.
Also, in addition to the manner described in the above flow, if there are multiple primary PLMN identities allocated to the RN, in step 301, the cell number information sent by the RN OAM entity to the DeNB OAM entity may be: and each primary PLMN identification corresponding to the RN and the number of cells corresponding to each primary PLMN identification. In step 302, the CI group information allocated by the DeNB OAM entity to the RN and sent to the RN OAM entity may be: and each primary PLMN identification corresponding to the RN and the CI group corresponding to each primary PLMN identification. Accordingly, the assignment condition of the CI group may be changed to a CI group corresponding to each PLMN identifier, where each CI is unique in the DeNB corresponding to the PLMN identifier and the cells of all RNs under the DeNB. This extension method may make it possible for the maximum number of cells served by the DeNB and all RNs accessing it to exceed 256.
Example four,
Fig. 4 is a flowchart of a method according to a fourth embodiment of the present invention, and as shown in fig. 4, the method may include the following steps:
step 401: and the RN OAM entity requests CI information or ECGI information of each cell of the DeNB from the DeNB OAM entity.
Step 402: and after receiving the request, the DeNB OAM entity reports CI information or ECGI information of each cell of the DeNB to the RN OAM entity.
The CI or ECGI reported by the DeNB OAM entity to the RN OAM entity may be in the form of a CI group or an ECGI group of all DeNB cells. Or, the reported CI information may be eNB IDs of the DeNB and a rightmost 8-bit list of CIs of all DeNB cells, and the reported ECGI information may be eNB IDs of the DeNB, a rightmost 8-bit list of CIs of all DeNB cells, and a primary PLMN identity. Wherein the ECGI group may be replaced with an ECGI list.
Step 403: and the RN OAM entity allocates CI and a main PLMN identification for each RN cell according to the received CI information or ECGI information of each cell of the DeNB and the maintained RN information, and sends the ECGI information of the RN to the RN.
The RN OAM entity may determine the number of cells configured for the RN before allocating a CI for each RN cell, wherein the method for the RN OAM entity to determine the number of cells configured for the RN may be the method in embodiment step 101.
The RN OAM entity can acquire DeNB ID information (namely, the leftmost 20 bits of the CI information) from the CI information of each cell of the DeNB or acquire DeNB ID information from the CI information in the ECGI information, the DeNB ID information is taken as the leftmost 20 bits of the CI allocated to the RN cell, meanwhile, the rightmost 8 bits of the CI allocated to the RN are different from the CI information of each cell in the DeNB or the rightmost 8 bits of the CI information in the ECGI information, namely, the CI of each RN cell is unique in the DeNB and all the cells of the RNs under the DeNB.
The RN OAM entity may record the configured CI for each RN cell to support subsequent CI allocations.
In addition, the RN OAM entity may also configure a PLMN identity list for each cell and other configuration parameters allocated to the RN, such as cell maximum transmission power, reference signal parameters, etc., and send the PLMN identity list and other configuration parameters to the RN together with the ECGI information.
In this step, the ECGI information sent by the RN OAM entity to the RN may be CI information and primary PLMN identification information allocated to the RN; or an ECGI consisting of CI and primary PLMN identity (instead of the primary PLMN identity of the ECGI, in separate form of CI), it is possible to make the maximum number of cells served by the DeNB and all RNs accessing it possibly exceed 256.
ECGI information sent by the RN OAM entity to the RN may be physically via the DeNB.
Preferably, in order to save air interface resources, the CI information sent by the RN OAM entity to the RN in this step may be only 8 rightmost bits of the CI. At the same time or before the step, the RN obtains the CI of the accessed cell from the system information block broadcast by the DeNB, and obtains the eNB ID of the DeNB, that is, the eNB ID of the RN from the leftmost 20 bits of the CI, in this case, the RN obtains the CI of each cell from the rightmost 8 bits of the CI of each RN cell from the RN OAM entity and the eNB ID of the RN.
In this embodiment, the RN OAM and the DeNB OAM entities may belong to different Domain managers (DM, Domain Manager) and communicate with each other through an Itf-P2P interface, or may communicate through a Network Management System (NMS). For the latter communication mode, the DM of the RN OAM entity communicates with the NMS through an Itf-N interface, and the DM of the DeNB OAM entity communicates with the NMS through an Itf-N interface.
The process shown in fig. 4 may be applied on the following premise: the RN OAM entity may communicate with the denba OAM entity to obtain relevant information.
In the above embodiments, the CI group may be replaced with a CI list.
In the above embodiments, the format of the information exchanged between RN and RN OAM may be related to the application protocol used by the RN and RN OAM entities to communicate, for example, in the format of TR-039 or Web-based network management specification.
The network deployment scenario corresponding to the method provided by each embodiment may include the following cases: the main PLMN of each cell of the DeNB is the same, each cell of the RN accessed to the DeNB and the DeNB cell belong to the same PLMN, and the eNB ID of the DeNB is unique in the range of the main PLMN corresponding to the DeNB cell; or, the DeNB and all cells accessing all RNs may correspond to more than 1 PLMN, and the eNB ID of the DeNB is unique within the range of all primary PLMNs involved in the DeNB and the cells accessing all RNs; or, any other possible scenario.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.