CN102378164B - Method for configuring ECGI (evolution cell global identification) of terrestrial radio access network for relay node - Google Patents
Method for configuring ECGI (evolution cell global identification) of terrestrial radio access network for relay node Download PDFInfo
- Publication number
- CN102378164B CN102378164B CN201010256846.3A CN201010256846A CN102378164B CN 102378164 B CN102378164 B CN 102378164B CN 201010256846 A CN201010256846 A CN 201010256846A CN 102378164 B CN102378164 B CN 102378164B
- Authority
- CN
- China
- Prior art keywords
- information
- denb
- group
- cells
- oam entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a method for configuring an evolution cell global identification (ECGI) of a terrestrial radio access network to a relay node(RN), which comprises the steps that: a relay node (RN) operation and maintenance (OAM) entity ensures the cell number which is distributed for the RN and cell identity (CI) group information distributed for each RN cell; each CI in the CI group accesses into the cell of a donor evolution base station (DeNB), wherein all RN cells under the DeNB are sole, and the CI number in the CI group is as the same as the cell number distributed for the RN; and the RN OAM entity configures identification of a public land mobile network (PLMN) for each RN cell, configuring the CI for each RN cell according to the CI group information, and transmitting ECGI information of the RN to the RN. The method is used for configuring the global unique ECGI for the RN, so that the RN can normally work.
Description
Technical field
The present invention relates to wireless communication technology field, particularly the method for the grounding wireless access network evolution cellular global identity of a kind of configuration via node (RN).
Background technology
According to the demand of IMT-Advanced (IMT-Advanced), the wireless communication system of following a new generation should meet the transmission characteristic of the highest 1Gbps speed, with the various data services of supporting constantly to occur.In order to meet the demand of IMT-Advanced, 3GPP has carried out the research of enhanced long-term evolution (LTE-Advanced) project.The key technology of LTE-Advanced system comprises that many antennas strengthen (Enhanced MIMO), carrier aggregation (CA, Carrier Aggregation), relaying (Relaying) and coordinated multipoint transmission (CoMP, Coordinated Multi-point).
In several key technologies of LTE-Advanced, relaying technique is used for providing the low-cost cell edge throughput that covers and promote.So-called relaying, refer to that via node (RN, relay node) is via the community access network of alms giver's evolution base station (DeNB, donor eNB), thereby as evolution base station (eNB), be that user terminal (UE, User Equipment) provides service.Under RN normal operating conditions (as eNB for UE provides service), the interface between RN and UE is Uu interface, and the interface between RN and DeNB is Un interface.From UE, RN is eNB.At Un interface, the UE of RN and the service of DeNB community shares Radio Resource.
In LTE, universal land radio access web cellular global identity (the ECGI of evolution, E-UTRAN Cell Global Identifier) by the public land mobile network (PLMN under community, Public Land Mobile Network) sign and cell ID (CI, Cell Identity) form, for identifying cells globally.Wherein, PLMN sign is comprised of Mobile Country Code MCC (MCC, Mobile Country Code) and Mobile Network Code (MNC, Mobile Network Code).CI is totally 28 bits, and leftmost 20 bits (20leftmost bits) are eNB id information, for identifying eNB at PLMN.
The CI of each Cell Broadcast CB self and the PLMN identification list of self supporting.The main PLMN (Primary PLMN) of first PLMN Wei Gai community in PLMN identification list, main PLMN and CI form the ECGI of community.
In LTE-A relaying technique, RN as eNB for UE provides service.RN operation and maintenance (OAM) entity is RN configuration parameter, to guarantee that RN normally works.Because RN is by the communication of eNB/DeNB and evolution block core (EPC, Evolved Packet Core) and access RN OAM entity by EPC, the data of communicating by letter between RN OAM entity and RN are passed through eNB/DeNB physically.The eNB ID of RN is identical with the eNB ID of the DeNB of RN access.
At RN OAM entity, be in the parameter of RN configuration, the ECGI that configures global uniqueness for RN is an important content that guarantees the normal work of RN, yet still there is no the concrete methods of realizing for this content in prior art.
Summary of the invention
In view of this, the invention provides the method for the ECGI of a kind of RN of configuration, thereby be embodied as the ECGI that RN configuration has global uniqueness, thereby guarantee that RN normally works.
Method of the present invention is achieved through the following technical solutions:
A method that configures the grounding wireless access network evolution cellular global identity ECGI of via node RN, is characterized in that, the method comprises:
RN operation and maintenance OAM entity is defined as the number of cells of RN distribution and is the cell ID CI group information of each RN cell allocation; In described CI group, each CI accesses in the community of alms giver's evolution base station DeNB and in all RN community, is unique under this DeNB at described RN, and in CI group, the number of CI is identical with the number of cells distributing for RN;
Described RN OAM entity is the main public land mobile network PLMN sign of each RN cell configuration, and is each RN cell configuration CI according to described CI group information, sends the ECGI information of RN to described RN.
Wherein, the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity sends to described RN by the number of cells information of distributing for RN;
Described RN reports described number of cells information to DeNB;
Described DeNB is each RN cell allocation CI group according to the described number of cells information reporting, and will send to described RN for the CI group information of each RN cell allocation; Or, the described number of cells information reporting that described DeNB reports RN is to DeNB OAM entity, DeNB OAM entity is each RN cell allocation CI group according to the described number of cells information of DeNB report, and by for the CI group information of each RN cell allocation sends to described DeNB, described DeNB sends to RN by the CI group information from DeNB OAM entity of receiving;
Described RN will send to described RN OAM entity for the CI group information of each RN cell allocation.
Or the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity sends to DeNB OAM entity by the number of cells information of distributing for RN;
Described DeNB OAM entity is that described RN distributes CI group according to described number of cells information of distributing for RN, and the information of CI group is sent to described RN OAM entity.
Or the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity is to CI information or the ECGI information of each community of DeNB OAM entity requests DeNB;
Described DeNB OAM entity receives after request, sends CI information or the ECGI information of each community of DeNB to described RN OAM entity;
Described RN OAM entity is according to the CI information of each community of described DeNB or ECGI information, for described RN distributes CI group.
In addition, described RN OAM entity, according to the CI information of each community of described DeNB or ECGI information, specifically comprises for described RN distributes CI group:
Described RN OAM entity is by leftmost 20 bits of CI information in leftmost 20 bits of the CI information of each community of described DeNB or ECGI information, as leftmost 20 bits that are each CI in the described RN CI group of distributing, in the CI group of distributing for described RN, in rightmost 8 bits of rightmost 8 bits of each CI and the CI information of each community of described DeNB or ECGI information, rightmost 8 bits of CI information are different.
More preferably, send to rightmost 8 bits that only comprise each CI in the information of CI group of described RN OAM entity;
Described RN OAM entity also obtains the DeNB id information of the affiliated DeNB of described RN, leftmost 20 bits of each CI in the information of group using this DeNBID information as CI.
Wherein, described RN OAM entity specifically comprises for the main PLMN of each RN cell configuration identifies:
Described RN OAM entity is for each RN cell configuration PLMN identification list and indicate the main PLMN sign in list, or, for each RN community directly configures main PLMN sign.
The number of cells information of more preferably, distributing for RN comprises: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding number of cells;
Described CI group information is: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding CI group; Wherein, at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.
Wherein, according to described CI group information, for each RN cell configuration CI, comprise:
Each CI in CI group is distributed to GeRN community successively, or according to default rule, each CI in CI group is distributed to GeRN community.
The ECGI information that sends RN to described RN specifically comprises: will send to described RN for the CI information of each RN cell configuration and main PLMN identification information; Or, the ECGI for the CI of each RN cell configuration and main PLMN sign formation is sent to described RN.
In addition, described RN OAM entity is defined as the number of cells that RN distributes and specifically comprises:
Described RN OAM entity, according to the information of the RN safeguarding, is defined as the number of cells that described RN distributes; Or,
The number of cells information that described RN sends request to RN OAM entity or send this RN and prepare the number of cells information generating or send largest cell information of number that this RN can support or the hardware capabilities information of this RN; The information of the information that described RN OAM entity sends according to described RN and the RN of maintenance, or the information sending according to described RN, for described RN distributes number of cells.
A method that configures the grounding wireless access network evolution cellular global identity ECGI of via node RN, the method comprises:
RN is retrieved as number of cells that RN distributes and is the main public land mobile network PLMN sign of each RN cell configuration from RN operation and maintenance OAM entity, and the number of cells information for RN distribution is sent to alms giver's evolution base station DeNB;
Described DeNB will send to described RN for the cell ID CI group information of each RN cell allocation; Or described DeNB sends to DeNB OAM entity by the number of cells information of distributing for RN, DeNBOAM entity, by for the CI group information of each RN cell allocation sends to DeNB, is transmitted to described RN by DeNB; Wherein, in described CI group, each CI is unique in all RN community in the community of DeNB that described RN accesses and under this DeNB, and in CI group, the number of CI is identical with the number of cells distributing for RN;
Described RN is each RN cell configuration CI according to described CI group information, is utilized as the CI of each RN cell configuration and the ECGI that main PLMN identification information is determined GeRN community.
Wherein, described RN is retrieved as number of cells that RN distributes and specifically comprises for the main PLMN sign of each RN cell configuration from RN OAM entity:
Described RN OAM entity is defined as the number of cells that RN distributes, and will identify and send to RN for the index value of each RN cell allocation and main PLMN;
Described RN is defined as according to the number of index value the number of cells that RN distributes.
In addition, described RN OAM entity is defined as the number of cells that RN distributes and specifically comprises:
Described RN OAM entity, according to the information of the RN safeguarding, is defined as the number of cells that described RN distributes; Or,
The number of cells information that described RN sends request to RN OAM entity or send this RN and prepare the number of cells information generating or send largest cell information of number that this RN can support or the hardware capabilities information of this RN; The information of the information that described RN OAM entity sends according to RN and the RN of maintenance, or the information of sending according to RN, for described RN distributes number of cells.
Particularly, for the main PLMN sign of each RN cell configuration specifically comprises:
Described RN OAM entity is for each RN cell configuration PLMN identification list and indicate the main PLMN sign in list, or, for each RN community directly configures main PLMN sign.
More preferably, send to rightmost 8 bits that only comprise each CI in the information of CI group of described RN;
Described RN also obtains DeNB id information the system information block of DeNB broadcast under described RN, leftmost 20 bits of each CI in the information of group using this DeNB id information as CI.
The number of cells information of distributing for RN comprises: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding number of cells;
Described CI group information is: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding CI group; Wherein, at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.
As can be seen from the above technical solutions, the invention provides the concrete grammar of the ECGI of two kinds of configuration RN, the ECGI that can be embodied as RN configuration by the method has global uniqueness, thereby guarantees that RN normally works.
Accompanying drawing explanation
The method flow diagram that Fig. 1 provides for the embodiment of the present invention one;
The method flow diagram that Fig. 2 provides for the embodiment of the present invention two;
The method flow diagram that Fig. 3 provides for the embodiment of the present invention three;
The method flow diagram that Fig. 4 provides for the embodiment of the present invention four.
Embodiment
In order to make the object, technical solutions and advantages of the present invention clearer, below in conjunction with the drawings and specific embodiments, describe the present invention.
Method provided by the invention mainly comprises:
Below by several specific embodiments, said method is described in detail.
Embodiment mono-,
The method flow diagram that Fig. 1 provides for the embodiment of the present invention, as shown in Figure 1, the method can comprise the following steps:
Step 101:RN sends the number of cells information of this RN to RN OAM entity.
In this step, the number of cells that RN can send request to RN OAM entity, also can send this RN to RNOAM entity and prepare the number of cells generating or send largest cell number that this RN can support or the hardware capabilities of this RN.
In the time of with step 101, RN communicates by letter with EPC via eNB, and the cell data information that now RN sends to RN OAM entity sends to RN OAM entity via eNB physically; Or RN communicates by letter with EPC via DeNB, the number of cells information that now RN sends to RN OAM entity sends to RN OAM entity via DeNB physically.
In addition, it should be noted that, this step 101 is optional step, also can not carry out this step, RN OAM entity is directly determined the number of cells of RN according to the information of self maintained, wherein should can comprise in the information of self maintained: the information such as position of RN ability, type or deployment are all so in following examples, repeat no longer one by one.
Step 102:RN OAM entity is defined as the number of cells of RN configuration, and the index value of the cell allocation for each RN and main PLMN sign are sent to RN.
If execution step 101, the information of number of community that RN OAM entity can send according to RN and the information of the RN of maintenance, or the hardware capabilities information sending according to RN, or the number of cells information sending according to RN, or according to the information of this RN of self maintained, be defined as the number of cells of RN configuration.If do not perform step 101, RN OAM entity is directly defined as the number of cells of RN configuration according to the information of self maintained.The number of cells configuring for RN is positive integer.
In this step, the index value for the cell allocation of RN meets following condition: the index value that each RN community is assigned with is unique within the scope of this RN.Index value scope with can be relevant for the number of cells of all RN configuration, for example, consider that rightmost 8 bits of CI can only carry at most 256 signs, index value scope can be [0,255].RN can be defined as according to the number of index value the number of cells that this RN distributes.
RN OAM entity can comprise for the main PLMN of each RN cell allocation sign: for the cell configuration PLMN identification list of each RN and indicate main PLMN, this main PLMN can be positioned at the first place of PLMN identification list; Or RN OAM entity is the directly main PLMN sign of configuration of each RN community.
RN OAM entity can be carried at the index value of each RN community and main PLMN sign and in community configured information, send to RN.In addition, in this community configured information, can also comprise the cell parameter of each RN community, such as community maximum transmission power, reference signal parameter etc.
Meanwhile, RN communicates by letter with EPC via eNB, and the configuration information that now RN OAM entity sends to RN can be physically via eNB; Or RN communicates by letter with EPC via DeNB, the configuration information that now RN OAM entity sends to RN is physically via DeNB.
Step 103:RN reports the number of cells information into this RN configuration to DeNB.
RN receives after the community configured information from RN OAM entity, is reported as the number of cells of this RN configuration to DeNB.
The form that RN sends number of cells information to DeNB can be that Radio Resource is controlled the specific information unit (IE) for RN in (RRC) message, can be also for the special RRC message of RN or the IE in special RRC message.
The number of cells that step 104:DeNB reports according to RN is that RN distributes CI group, and the information of CI group is sent to RN.
Wherein, the number of cells that the CI number in CI group can report for RN.
The distribution of CI group meets following condition: each CI in CI group is unique in all RN community in the community of DeNB and under this DeNB.DeNB can be recorded as the CI group that RN distributes, to support follow-up CI to distribute.
The form that DeNB sends the information of CI group to RN can be the special IE for RN in RRC message, can be also for the special RRC message of RN or the IE in special RRC message.
More preferably, in order to save interface-free resources, in the information of the CI group sending to RN in this step, each CI can be only rightmost 8 bits of CI.
Step 105:RN distributes to GaiRNGe community by the CI in the CI group of acquisition, distributes to the CI of each community and the ECGI that main PLMN sign forms each community.
RN can be successively or default rule each CI in CI group is distributed to GaiRNGe community.Particularly, CI directly can be distributed to GaiRNGe community, also CI can be bound with distributing the index value of RN community.
The ECGI that forms community due to main PLMN sign and the CI of community, thus the method has guaranteed the global uniqueness of the ECGI of RN.
If during rightmost 8 bit that the CI group information sending in step 104 is each CI, before step 105 or with step 105 in, in the system information block that RN is broadcasted by DeNB (SIB) 1, obtain the CI value of the DeNB community of accessing, 20 eNB ID that obtain DeNB from this CI value, RN is obtained the CI distributing into this RN by rightmost 8 bits of the CI receiving and the eNB ID of DeNB.
Except the mode shown in Fig. 1, the CI group of RN community can be also DeNB OAM physical arrangements, in this case, in step 104, when DeNB receives from the number of cells information of RN, this number of cells information is sent to DeNB OAM entity as the newly-increased number of cells of DeNB self, by DeNB OAM entity, according to number of cells, configure CI group and CI group is sent to DeNB, DeNB OAM entity can record to support follow-up cell configuration by the CI group of configuration simultaneously, and DeNB receives after the CI group of DeNB OAM physical arrangements, the CI group of DeNB OAM physical arrangements is sent to RN.
Flow process shown in Fig. 1 can be applicable under following prerequisite: RN OAM entity from DeNB OAM entity cannot obtain DeNB and below the ECGI information of all communities of all RN; Or, other any possible prerequisite.
In addition, the mode of describing in above-mentioned flow process, the main PLMN that RN distributes is if designated a plurality of, and, in step 103, the number of cells information that RN reports to DeNB can be specially: each main PLMN sign and each main PLMN that RN is corresponding identify corresponding number of cells.And DeNB to be RN distribute, to RN, send and the CI group correspondence of self record can be: each main PLMN sign and each main PLMN that RN is corresponding identify corresponding CI group.The distributive condition of CI group can be: at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.The method can be so that DeNB and access largest cell number that its all RN serve likely over 256.
In these cases, it can be also DeNBOAM physical arrangements that each main PLMN of RN community identifies corresponding CI group, DeNB receives when each main PLMN from RN identifies corresponding number of cells information, using this, each main PLMN identifies corresponding number of cells information and sends to DeNB OAM entity as the information of the newly-increased community of DeNB self, by DeNB OAM entity, according to this, each main PLMN identifies corresponding number of cells information and identifies corresponding cell configuration CI group and the CI group that identifies corresponding cell configuration for each main PLMN is sent to DeNB and configuration information record is got off for follow-up cell configuration for each main PLMN, and DeNB receives that each main PLMN of DeNB OAM physical arrangements identifies after the CI group of corresponding community, the CI group that each main PLMN of DeNB OAM physical arrangements is identified to corresponding community sends to RN.
Embodiment bis-,
The method flow diagram that Fig. 2 provides for the embodiment of the present invention two, as shown in Figure 2, the method can comprise the following steps:
Step 201:RN OAM entity is defined as the number of cells of RN configuration, and the number of cells information for RN configuration is sent to RN.
The method that RN OAM entity is defined as the number of cells of RN configuration can be the method in embodiment mono-step 101 and step 102.
If RN communicates by letter with EPC via eNB, the number of cells information that RN sends to RN OAM entity is physically via eNB; Or if RN communicates by letter with EPC via DeNB, the number of cells information that RN sends to RN OAM entity is physically via DeNB.
Step 202:RN is sent as the number of cells information of this RN configuration to DeNB.
RN receives after the number of cells information that RN OAM entity is its configuration, reports the number of cells information of this RN to DeNB.The form that RN sends number of cells information to DeNB can be the special IE for RN in RRC message, can be also for the special RRC message of RN or the IE in special RRC message.
The number of cells information that step 203:DeNB reports according to RN is that RN distributes CI group, and the information of CI group is sent to RN.
Wherein, the CI number in CI group can be: the number of cells that RN reports.
The distribution of CI group meets following condition: each CI in CI group is unique in all RN community in the community of DeNB and under this DeNB.DeNB can be recorded as the CI group that RN distributes, to support follow-up CI to distribute.
The form that DeNB sends the information of CI group to RN can be the special IE for RN in RRC message, can be also for the special RRC message of RN or the IE in special RRC message.
More preferably, in order to save interface-free resources, in the information of the CI group sending to RN in this step, each CI can be only rightmost 8 bits of CI.
Step 204:RN sends to RN OAM entity by the information of the CI group of receiving.
Meanwhile, RN communicates by letter with EPC via DeNB, and the information of the CI group that RN OAM entity sends to RN is physically via DeNB.
If during rightmost 8 bit that the CI group information sending in step 203 is each CI, before step 204 or with step 204 in, in the SIB1 that RN is broadcasted by DeNB, obtain the CI value of the DeNB community of accessing, 20 eNB ID that obtain DeNB from this CI value, RN is obtained the CI distributing into this RN by rightmost 8 bits of the CI receiving and the eNB ID of DeNB.Or the information of the CI group that RN sends to RN OAM entity is 8, the right side of each CI, the eNB ID of DeNB sends to RN OAM entity by RN step 204 time or before step 204.
The CI group that the utilization of step 205:RN OAM entity receives and the information of self maintained, be each RN cell allocation CI, and be the main PLMN sign of each RN cell configuration, and RN OAM entity sends to RN by the information of the ECGI of RN.
RN OAM entity can comprise for the main PLMN of each RN cell allocation sign: for the cell configuration PLMN identification list of each RN and indicate main PLMN, this main PLMN can be positioned at the first place of PLMN identification list; Or RN OAM entity is the directly main PLMN sign of configuration of each RN community.
In addition, RN OAM entity can also be other parameter of RN cell configuration, community maximum transmission power for example, reference signal parameter etc.
RN OAM entity sends to RN by the CI for RN configuration and main PLMN sign; Or, directly the ECGI of CI and main PLMN sign formation is directly sent to RN.Meanwhile, also other parameter of PLMN list HeRN community can be sent to RN.
The information of the ECGI that RN OAM entity sends to RN physically can be via DeNB.
More preferably, in order to save interface-free resources, the CI information that in this step, RN OAM entity sends to RN can be only rightmost 8 bits of CI.RN is in this step or before this step, in the system information block of being broadcasted by DeNB, obtain the CI of the community of accessing, by leftmost 20 bits of this CI, obtained the eNB ID of DeNB, the eNB ID of RN namely, in this case, RN is obtained the CI of self each community by rightmost 8 bits of the CI from RN OAM entity Ge RN community and the eNB ID of self.
If what in step 204, RN OAM entity was received is rightmost 8 bits of CI, in step 205, according to the eNB ID (the namely eNB ID of DeNB) of the RN that receives or safeguard and rightmost 8 bits of the CI receiving, obtain CI.
Alternatively, the CI group of RN community can be also DeNB OAM physical arrangements, in step 203, when DeNB receives from the number of cells information of RN, this number of cells information is sent to DeNB OAM entity as the newly-increased number of cells of DeNB self, by DeNB OAM entity, according to number of cells, configured CI group and CI group is sent to DeNB, then DeNB sends to RN by the CI group of DeNB OAM physical arrangements.
Flow process shown in Fig. 2 can be applicable under following prerequisite: RN OAM entity from DeNB OAM entity cannot obtain DeNB and below the ECGI information of all communities of all RN; Or, other any possible prerequisite.
In addition, the mode of describing in above-mentioned flow process, the main PLMN that RN distributes is if designated a plurality of, and, in step 201, RN OAM entity is that the number of cells of RN configuration can be: each main PLMN sign and each main PLMN that this RN is corresponding identify corresponding number of cells.In step 202, the number of cells that RN sends to DeNB can be: each main PLMN sign and each main PLMN that this RN is corresponding identify corresponding number of cells.In step 203, DeNB is RN configuration, to RN, sends and the CI group information of self record can be: main PLMN sign and each main PLMN that this RN is corresponding identify corresponding CI group.Correspondingly, the distributive condition of CI group can be: at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.In step 204, RN sends CI group information to RN OAM entity and can be: send RN corresponding each main PLMN sign and each main PLMN identify corresponding CI group information.The method can be so that DeNB and access largest cell number that its all RN serve likely over 256.
In addition, it can be also DeNBOAM physical arrangements that each main PLMN of RN community identifies corresponding CI group, in this case, DeNB receives when each the main PLMN from RN identifies corresponding number of cells information, using this, each main PLMN identifies corresponding number of cells information and sends to DeNB OAM entity as the information of the newly-increased community of DeNB self, by DeNB OAM entity, according to this, each main PLMN identifies corresponding number of cells and identifies corresponding cell configuration CI group and the CI group that identifies corresponding cell configuration for each main PLMN is sent to DeNB and configuration information record is got off for follow-up cell configuration for each main PLMN, and DeNB receives that each main PLMN of DeNB OAM physical arrangements identifies after the CI group of corresponding community, the CI group that each main PLMN of DeNB OAM physical arrangements is identified to corresponding community sends to RN.
Embodiment tri-,
The method flow diagram that Fig. 3 provides for the embodiment of the present invention three, as shown in Figure 3, the method can comprise the following steps:
Step 301:RN OAM entity is defined as the number of cells of RN configuration, and the number of cells information for RN configuration is sent to DeNB OAM entity.
The method that RN OAM entity is defined as the number of cells of RN configuration can be the method in embodiment mono-step 101 and step 102.
Step 302:DeNB OAM entity is that RN distributes CI group according to the number of cells for RN configuration receiving, and the information of CI group is sent to RN OAM entity.
DeNB OAM entity is according to the number of cells receiving, or the DeNB Ge community of accessing according to this RN of the number of cells receiving and self maintained and the CI that has accessed all RNGe community of this DeNB, is defined as the CI group that RN distributes.
In the CI group of distributing for RN, the number of CI can be: be the number of cells of RN cell configuration.
The distribution of CI group meets following condition: each CI in CI group is unique in all RN community under DeNB and this DeNB.Meanwhile, DeNB OAM entity record is the CI group that RN distributes, to support follow-up CI to distribute.
Step 303:RN OAM entity, according to the CI group information receiving and the information of this RN of self maintained, is each RN cell configuration CI and main PLMN sign, and the ECGI information of this RN is sent to RN.
In this step, RN OAM entity can the ECGI information using CI information and main PLMN identification information as this RN send to RN, and the ECGI information that also CI and main PLMN sign can be formed send to RN.
Wherein, main PLMN identification information can be the indication information in list of PLMN identification list and main PLMN sign, and for example heading PLMN represents main PLMN, can be also direct main PLMN sign.
In addition, RN OAM entity can also send to RN by other configuration parameter distributing for RN, community maximum transmission power for example, reference signal parameter etc.
In addition, the information that RN OAM entity sends to RN physically can be via DeNB.
More preferably, in order to save interface-free resources, the CI information that in this step, RN OAM entity sends to RN can be only rightmost 8 bits of CI.RN is in this step or before this step, in the system information block of being broadcasted by DeNB, obtain the CI of the community of accessing, by leftmost 20 bits of this CI, obtained the eNB ID of DeNB, the eNB ID of RN namely, in this case, RN is obtained the CI of self each community by rightmost 8 bits of the CI from RN OAM entity Ge RN community and the eNB ID of self.
In the present embodiment, RN OAM can adhere to different domain manager (DM, Domain Manager) separately from DeNB OAM entity and communicate with one another by Itf-P2P interface, also can communicate by letter by network management system (NMS).For rear a kind of communication mode, the DM of RN OAM entity and NMS are with Itf-N interface communication, and the DM of DeNB OAM entity and NMS are with Itf-N interface communication.
Flow process shown in Fig. 3 can be applicable under following prerequisite: RN OAM entity can be with DeNBOAM entity communication to obtain relevant information.
Equally, the mode of describing in above-mentioned flow process, the main PLMN that RN distributes is if designated a plurality of,, in step 301, the number of cells information that RN OAM entity sends to DeNB OAM entity can be: each main PLMN sign and each main PLMN that RN is corresponding identify corresponding number of cells.In step 302, DeNB OAM entity is that the CI group information that RN distributes, sends to RN OAM entity can be: each main PLMN sign and each main PLMN that RN is corresponding identify corresponding CI group.Correspondingly, the distributive condition of CI group can change each PLMN into and identify in corresponding CI group, and it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.This extended method can be so that DeNB and access largest cell number that its all RN serve likely over 256.
Embodiment tetra-,
The method flow diagram that Fig. 4 provides for the embodiment of the present invention four, as shown in Figure 4, the method can comprise the following steps:
Step 401:RN OAM entity is to CI information or the ECGI information of each community of DeNB OAM entity requests DeNB.
Step 402:DeNB OAM entity receives after request, to CI information or the ECGI information of RN OAM entity report each community of DeNB.
DeNB OAM entity can be CI group or the ECGI group of all DeNB community to the CI of RN OAM entity report or the form of ECGI.Or, the CI information reporting can be the list of rightmost 8 bits of the eNB ID of DeNB and the CI of all DeNB community, and the ECGI information reporting can be the list of rightmost 8 bits and the main PLMN sign of the CI of the eNB ID of DeNB, all DeNB community.Wherein, ECGI group can replace with ECGI list.
Step 403:RN OAM entity, according to the CI information of each community of DeNB receiving or the information of the RN of ECGI information and maintenance, is each RN cell allocation CI and main PLMN sign, and the ECGI information of this RN is sent to RN.
RN OAM entity is for being defined as the number of cells of RN configuration before each RN cell allocation CI, wherein, the method that RN OAM entity is defined as the number of cells of RN configuration can be the method in embodiment mono-step 101.
RN OAM entity can obtain in DeNB id information (being leftmost 20 bits of CI information) or the CI information from ECGI information and obtain DeNB id information from the CI information of each community of DeNB, using this DeNB id information as being leftmost 20 bits in RN cell allocation CI, simultaneously, for rightmost 8 bits in the CI of RN distribution are not identical with the CI information of DeNB Zhong Ge community or rightmost 8 bits of the CI information in ECGI information, the CI that simultaneously meets each RN community is unique in all RN community under DeNB and this DeNB.
RN OAM entity can be recorded as the CI of each RN cell configuration, to support follow-up CI to distribute.
In addition, other configuration parameter that RN OAM entity can also distribute for each cell configuration PLMN identification list with for RN, community maximum transmission power for example, reference signal parameter etc., and send to RN together with ECGI information one.
In this step, it can be CI information and the main PLMN identification information distributing for RN that RN OAM entity sends to the ECGI information of RN; Also can be the ECGI that formed by CI and main PLMN sign (but not main PLMN sign, the separated form of CI two parts of ECGI), now can be so that DeNB and access largest cell number that its all RN serve likely over 256.
The ECGI information that RN OAM entity sends to RN physically can be via DeNB.
More preferably, in order to save interface-free resources, the CI information that in this step, RN OAM entity sends to RN can be only rightmost 8 bits of CI.RN is in this step or before this step, in the system information block of being broadcasted by DeNB, obtain the CI of the community of accessing, by leftmost 20 bits of this CI, obtained the eNB ID of DeNB, the eNB ID of RN namely, in this case, RN is obtained the CI of self each community by rightmost 8 bits of the CI from RN OAM entity Ge RN community and the eNB ID of self.
In the present embodiment, RN OAM can adhere to different domain manager (DM, Domain Manager) separately and communicate with one another by Itf-P2P interface from DeNB OAM entity, also can communicate by letter by network management system (NMS).For rear a kind of communication mode, the DM of RN OAM entity and NMS are with Itf-N interface communication, and the DM of DeNB OAM entity and NMS are with Itf-N interface communication.
Flow process shown in Fig. 4 can be applicable under following prerequisite: RN OAM entity can be with DeNBOAM entity communication to obtain relevant information.
In the various embodiments described above, CI group also can replace to CI list.
In the various embodiments described above, between RN and RN OAM, the form of mutual information can be relevant with the application protocol that RN and RN OAM entity communication are used, and for example, adopts the form of TR-039 or the network management technology standard based on Web.
Network design scene corresponding to method that the various embodiments described above provide can comprise following situation: the main PLMN of each community of DeNB is identical, access DeNB RNGe community and DeNB community belong to same PLMN, and the eNB ID of DeNB is unique within the scope of main PLMN corresponding to DeNB community; Or DeNB and all communities of accessing its all RN may correspondence be greater than 1 PLMN, and the eNB ID of DeNB is at DeNB and access within the scope of the related all main PLMN in its all RN community unique; Or, other any possible scene.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, be equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.
Claims (17)
1. a method that configures the grounding wireless access network evolution cellular global identity ECGI of via node RN, is characterized in that, the method comprises:
RN operation and maintenance OAM entity is defined as the number of cells of RN distribution and is the cell ID CI group information of each RN cell allocation; In described CI group, each CI accesses in the community of alms giver's evolution base station DeNB and in all RN community, is unique under this DeNB at described RN, and in CI group, the number of CI is identical with the number of cells distributing for RN;
Described RN OAM entity is the main public land mobile network PLMN sign of each RN cell configuration, and is each RN cell configuration CI according to described CI group information, sends the ECGI information of RN to described RN.
2. method according to claim 1, is characterized in that, the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity sends to described RN by the number of cells information of distributing for RN;
Described RN reports described number of cells information to DeNB;
Described DeNB is each RN cell allocation CI group according to the described number of cells information reporting, and will send to described RN for the CI group information of each RN cell allocation; Or, the described number of cells information that described DeNB reports RN sends to DeNB OAM entity, DeNB OAM entity is each RN cell allocation CI group according to the described number of cells information receiving, and by for the CI group information of each RN cell allocation sends to described DeNB, described DeNB will receive that described CI group information sends to described RN;
Described RN will send to described RN OAM entity for the CI group information of each RN cell allocation.
3. method according to claim 1, is characterized in that, the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity sends to DeNB OAM entity by the number of cells information of distributing for RN;
Described DeNB OAM entity is that described RN distributes CI group according to described number of cells information of distributing for RN, and the information of CI group is sent to described RN OAM entity.
4. method according to claim 1, is characterized in that, the CI group information that described RN OAM entity is defined as each RN cell allocation specifically comprises:
Described RN OAM entity is to CI information or the ECGI information of each community of DeNB OAM entity requests DeNB;
Described DeNB OAM entity receives after request, sends CI information or the ECGI information of each community of DeNB to described RN OAM entity;
Described RN OAM entity is according to the CI information of each community of described DeNB or ECGI information, for described RN distributes CI group.
5. method according to claim 4, is characterized in that, described RN OAM entity, according to the CI information of each community of described DeNB or ECGI information, specifically comprises for described RN distributes CI group:
Described RN OAM entity is by leftmost 20 bits of CI information in leftmost 20 bits of the CI information of each community of described DeNB or ECGI information, as leftmost 20 bits that are each CI in the described RN CI group of distributing, in the CI group of distributing for described RN, in rightmost 8 bits of rightmost 8 bits of each CI and the CI information of each community of described DeNB or ECGI information, rightmost 8 bits of CI information are different.
6. according to the method in claim 2 or 3, it is characterized in that, send to rightmost 8 bits that only comprise each CI in the information of CI group of described RN OAM entity;
Described RN OAM entity also obtains the DeNB id information of the affiliated DeNB of described RN, leftmost 20 bits of each CI in the information of group using this DeNBID information as CI.
7. according to the method described in the arbitrary claim of claim 1 to 5, it is characterized in that, described RN OAM entity specifically comprises for the main PLMN of each RN cell configuration identifies:
Described RN OAM entity is for each RN cell configuration PLMN identification list and indicate the main PLMN sign in list, or, for each RN community directly configures main PLMN sign.
8. according to the method described in the arbitrary claim of claim 2 to 5, it is characterized in that, the number of cells information of distributing for RN comprises: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding number of cells;
Described CI group information is: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding CI group; Wherein, at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.
9. according to the method described in the arbitrary claim of claim 1 to 5, it is characterized in that, according to described CI group information, for each RN cell configuration CI, comprise:
Each CI in CI group is distributed to GeRN community successively, or according to default rule, each CI in CI group is distributed to GeRN community successively.
10. according to the method described in the arbitrary claim of claim 1 to 5, it is characterized in that, the ECGI information that sends RN to described RN specifically comprises: will send to described RN for the CI information of each RN cell configuration and main PLMN identification information; Or, the ECGI for the CI of each RN cell configuration and main PLMN sign formation is sent to described RN.
11. according to the method described in the arbitrary claim of claim 1 to 5, it is characterized in that, the number of cells that described RN OAM entity is defined as RN distribution specifically comprises:
Described RN OAM entity, according to the information of the RN safeguarding, is defined as the number of cells that described RN distributes; Or,
The largest cell information of number that the number of cells information that the number of cells information that described RN sends request to RN OAM entity or this RN preparation generate or this RN can support or the hardware capabilities information of this RN; The information of the information that described RN OAM entity sends according to described RN and the RN of maintenance, or the information sending according to described RN, for described RN distributes number of cells.
12. 1 kinds of methods that configure the grounding wireless access network evolution cellular global identity ECGI of via node RN, is characterized in that, the method comprises:
RN is retrieved as number of cells that RN distributes and is the main public land mobile network PLMN sign of each RN cell configuration from RN operation and maintenance OAM entity, and the number of cells information for RN distribution is sent to alms giver's evolution base station DeNB;
Described DeNB will send to described RN for the cell ID CI group information of each RN cell allocation; Or described DeNB sends to DeNB OAM entity by the number of cells information of distributing for RN, DeNBOAM entity, by for the CI group information of each RN cell allocation sends to DeNB, is transmitted to described RN by DeNB; Wherein, in described CI group, each CI is unique in all RN community in the community of DeNB that described RN accesses and under this DeNB, and in CI group, the number of CI is identical with the number of cells distributing for RN;
Described RN is each RN cell configuration CI according to described CI group information, is utilized as the CI of each RN cell configuration and the ECGI that main PLMN identification information is determined GeRN community.
13. methods according to claim 12, is characterized in that, described RN is retrieved as number of cells that RN distributes and specifically comprises for the main PLMN sign of each RN cell configuration from RN OAM entity:
Described RN OAM entity is defined as the number of cells that RN distributes, and will identify and send to RN for the index value of each RN cell allocation and main PLMN;
Described RN is defined as according to the number of index value the number of cells that RN distributes.
14. methods according to claim 13, is characterized in that, the number of cells that described RN OAM entity is defined as RN distribution specifically comprises:
Described RN OAM entity, according to the information of the RN safeguarding, is defined as the number of cells that described RN distributes; Or,
The number of cells information that described RN sends request to RN OAM entity or send this RN and prepare the number of cells information generating or send largest cell information of number that this RN can support or the hardware capabilities information of this RN; The information of the information that described RN OAM entity sends according to RN and the RN of maintenance, or the information of only sending according to RN, for described RN distributes number of cells.
15. according to the method described in claim 12,13 or 14, it is characterized in that, for the main PLMN sign of each RN cell configuration specifically comprises:
Described RN OAM entity is for each RN cell configuration PLMN identification list and indicate the main PLMN sign in list, or, for each RN community directly configures main PLMN sign.
16. according to the method described in claim 12,13 or 14, it is characterized in that, sends to rightmost 8 bits that only comprise each CI in the information of CI group of described RN;
Described RN also obtains DeNB id information the system information block of DeNB broadcast under described RN, leftmost 20 bits of each CI in the information of group using this DeNB id information as CI.
17. according to the method described in claim 12,13 or 14, it is characterized in that, the number of cells information of distributing for RN comprises: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding number of cells;
Described CI group information is: main PLMN sign and each main PLMN of for described RN, distributing identify corresponding CI group; Wherein, at each PLMN, identify in corresponding CI group, it is unique in all RN community that each CI identifies under corresponding DeNB and this DeNB at this PLMN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010256846.3A CN102378164B (en) | 2010-08-18 | 2010-08-18 | Method for configuring ECGI (evolution cell global identification) of terrestrial radio access network for relay node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010256846.3A CN102378164B (en) | 2010-08-18 | 2010-08-18 | Method for configuring ECGI (evolution cell global identification) of terrestrial radio access network for relay node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102378164A CN102378164A (en) | 2012-03-14 |
| CN102378164B true CN102378164B (en) | 2014-11-26 |
Family
ID=45795991
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010256846.3A Expired - Fee Related CN102378164B (en) | 2010-08-18 | 2010-08-18 | Method for configuring ECGI (evolution cell global identification) of terrestrial radio access network for relay node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102378164B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103874046A (en) * | 2012-12-13 | 2014-06-18 | 电信科学技术研究院 | Process message management method and device |
| CN107295601B (en) * | 2016-04-12 | 2020-07-10 | 中兴通讯股份有限公司 | Method and device for accessing core network in multi-operator core network |
| CN116980925A (en) * | 2022-04-24 | 2023-10-31 | 大唐移动通信设备有限公司 | Method, device and storage medium for identifying host network equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101583175A (en) * | 2009-06-12 | 2009-11-18 | 中国科学技术大学 | Target NeNB cell identity method based on neighbor cell message in LTE-advanced network |
| CN101651950A (en) * | 2009-09-09 | 2010-02-17 | 新邮通信设备有限公司 | Business realization method, equipment and system in long-term evolution network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090268722A1 (en) * | 2008-04-29 | 2009-10-29 | Gallagher Michael D | User Equipment and System Architecture for Voice over Long Term Evolution via Generic Access |
-
2010
- 2010-08-18 CN CN201010256846.3A patent/CN102378164B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101583175A (en) * | 2009-06-12 | 2009-11-18 | 中国科学技术大学 | Target NeNB cell identity method based on neighbor cell message in LTE-advanced network |
| CN101651950A (en) * | 2009-09-09 | 2010-02-17 | 新邮通信设备有限公司 | Business realization method, equipment and system in long-term evolution network |
Non-Patent Citations (1)
| Title |
|---|
| CATT.Discussion on uniqueness of ECGI configuration.《3GPP TSG RAN WG3 Meeting #69 R3-102221》.2010, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102378164A (en) | 2012-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220182742A1 (en) | Gateway apparatus and methods for wireless iot (internet of things) services | |
| EP3560228B1 (en) | Support for frequency-overlapping carriers | |
| CN102340379B (en) | CSI-RS (Channel Status Information-Reference Signal) transmission method and detection method, and devices of CSI-RS transmission method and detection method | |
| CN107155187B (en) | Communication method, terminal equipment and network equipment | |
| US9935701B2 (en) | Apparatus for transmitting and receiving signal in distributed antenna system | |
| CN101777941B (en) | Downlink mode of transmission, network devices and wireless device in the coordinated multiple-point transmission systems | |
| CN102461010B (en) | User agency for combining public reference signal and corresponding network | |
| US9001717B2 (en) | Method and apparatus of transmitting and receiving signal in a distributed antenna system | |
| US20180376407A1 (en) | Access Control In A Network Comprising Network Slices | |
| US9258847B2 (en) | Method for transmitting coordinated multipoint transmission/reception coordinated group messages and an evolved NodeB thereof | |
| JP6346198B2 (en) | Mobile communication base station and method for allocating resources outside a virtual carrier based on UE capabilities | |
| US8750886B2 (en) | Apparatus and method for dynamic resolution of secondary communication system resources | |
| US9900873B2 (en) | Method and device for transmitting parameters and method and device for generating parameters | |
| JP2016510554A (en) | Communication device and method | |
| CN102595427A (en) | Radio communication method and radio base station | |
| US10390344B2 (en) | Carrier configuration method, base station, and user equipment | |
| CN103931253A (en) | Methods and devices for dynamic allocation of identifiers in hybrid cell identifier scenarios | |
| CN103650446A (en) | Methods of pdcch capacity enhancement in lte systems based on a tp-specific reference signal | |
| CN102468926A (en) | Configuration method of downlink control information, network equipment and access node | |
| CN102196581A (en) | Method and system for configuring downlink subframes in return link | |
| CN103997727A (en) | Device discovery method and apparatus | |
| CN102457964A (en) | Coordinated multipoint method and apparatus thereof | |
| CN104812053B (en) | The transmission method and system, transmitting terminal and receiving end of D2D communication synchronization channel | |
| CN104426830A (en) | Signaling transmission method and system for reference operation in multiple carriers, and network side | |
| CN109155794A (en) | Identification and/or general introduction to fixed user and mobile subscriber |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: CHINA POTEVIO CO., LTD. Free format text: FORMER OWNER: PUTIAN IT TECH INST CO., LTD. Effective date: 20130913 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20130913 Address after: 100080, No. two, 2 street, Zhongguancun science and Technology Park, Beijing, Haidian District Applicant after: CHINA POTEVIO CO.,LTD. Address before: 100080 Beijing, Haidian, North Street, No. two, No. 6, No. Applicant before: PETEVIO INSTITUTE OF TECHNOLOGY Co.,Ltd. |
|
| ASS | Succession or assignment of patent right |
Owner name: PUTIAN IT TECH INST CO., LTD. Free format text: FORMER OWNER: CHINA POTEVIO CO., LTD. Effective date: 20131202 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20131202 Address after: 100080 Beijing, Haidian, North Street, No. two, No. 6, No. Applicant after: PETEVIO INSTITUTE OF TECHNOLOGY Co.,Ltd. Address before: 100080, No. two, 2 street, Zhongguancun science and Technology Park, Beijing, Haidian District Applicant before: CHINA POTEVIO CO.,LTD. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20141126 Termination date: 20210818 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |