WO2014079141A1 - 一种网关重定位的方法、移动管理实体及宿主基站 - Google Patents

一种网关重定位的方法、移动管理实体及宿主基站 Download PDF

Info

Publication number
WO2014079141A1
WO2014079141A1 PCT/CN2013/001215 CN2013001215W WO2014079141A1 WO 2014079141 A1 WO2014079141 A1 WO 2014079141A1 CN 2013001215 W CN2013001215 W CN 2013001215W WO 2014079141 A1 WO2014079141 A1 WO 2014079141A1
Authority
WO
WIPO (PCT)
Prior art keywords
mrn
relocation
gateway
denb
information
Prior art date
Application number
PCT/CN2013/001215
Other languages
English (en)
French (fr)
Inventor
黄莹
高音
褚丽
梁爽
谢峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP13857309.2A priority Critical patent/EP2925052A4/en
Priority to US14/646,492 priority patent/US9807667B2/en
Publication of WO2014079141A1 publication Critical patent/WO2014079141A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W64/00Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16Gateway arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/005Moving wireless networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems
    • H04W84/047Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • Gateway relocation method mobile management entity and host base station
  • the present invention relates to the field of wireless communication technologies, and in particular, to a method for relocation of a gateway, a Mobility Management Entity (MME), and a host base station.
  • MME Mobility Management Entity
  • the Relay Node provides similar functions and services to the evolved Node B (eNB) for the User Equipment (UE) accessing its cell, and uses a wireless interface to be similar to the normal UE. Access to an eNB serving it (called a Donor eNB (DeNB)).
  • eNB evolved Node B
  • UE User Equipment
  • DeNB Donor eNB
  • MRNs Mobile Relay Nodes
  • the mobile relay technology can enable users (UE1 and UE2) in the high-speed train to communicate with the relatively stationary MRN, and the MRN can be in different DeNBs as the high-speed rail moves. Inter-switching, thereby avoiding the simultaneous handover of a large number of users in the high-speed rail car, ensuring the communication quality between the UE and the MRN, and further improving the series of problems of the high-speed rail by enhancing the backbone connection between the MRN and the DeNB. .
  • the mobile relay system can use the architecture shown in Figure 1 (i.e., the same architecture as the standardized RIO fix relay, commonly referred to as architecture 2), in which the MRN is built into the DeNB.
  • control plane signaling provides SI and/or X2 proxy functionality.
  • the S-GW, P-GW, and relay GW (collectively referred to as GWs) of the MRN are located in the initial DeNB (initial DeNB) that is accessed when it is attached, when on the high-speed rail.
  • the MRN moves to the far side of the initial DeNB, the data of the UE arrives at the P-GW of the MRN, and then the route is forwarded through the multiple DeNBs to reach the DeNB serving the MRN, that is, the routing path is too long, and the UE data is caused.
  • the delay increases. Therefore, a route optimization scheme may be considered.
  • the GW of the MRN is replaced with a gateway built in the DeNB of the MRN service during the handover of the MRN. As shown in FIG.
  • the GW is located on the DeNB1, and when the MRN is served by the base station function of the DeNB3, the data of the UE first reaches the GW function of the DeNB1, and then the DeNB2 routes to the base station function of the DeNB3, and the MRN can be During the handover, the GW is relocated to the GW built in the DeNB4, so that the data of the UE can directly reach the GW in the DeNB4, shortening the path length and reducing the data delay. Since the relocation of the gateway is not required every time the MRN is switched, it is only required when the routing path is long.
  • the target DeNB needs to meet certain conditions to relocate the MRN's gateway to the S-GW and P-GW built in the target DeNB.
  • it is necessary to solve the problem of how to determine whether to perform gateway relocation in the handover process of this MRN.
  • the mobile relay system can also use the architecture shown in Figure 3 (commonly referred to as architecture 1).
  • the architecture does not have a relay GW functional entity.
  • the S-GW and P-GW serving the MRN are located in the core network, and the DeNB will be the UE.
  • the general packet radio service (GPRS) Tunneling Protocol for Userplane (GTP-U) packet encapsulated into the user plane and the control plane signaling is sent to the MRN by the bearer of the mobile relay.
  • the GW and the P-GW are then routed to the MME or S-GW of the UE via an Internet Protocol (IP).
  • IP Internet Protocol
  • the embodiment of the present invention provides a method for relocation of a gateway, a mobility management entity, and a host base station, which can determine whether to relocate a mobile relay node when the mobile relay node switches the host base station. Gateway.
  • the embodiment of the invention provides a method for relocation of a gateway, including:
  • the mobility management entity MME of the MRN determines whether it is necessary to perform relocation of the gateway serving the MRN according to the current location of the MRN.
  • the MME of the MRN determines, according to the current location of the MRN, whether a relocation of the gateway that performs the MRN service is required, including:
  • the MME determines, according to the distance between the MRN and the gateway serving the MRN, whether to perform relocation of the gateway serving the MRN, including:
  • the location-related information of the gateway serving the MRN is when the MRN accesses the DeNB where the gateway serving the MRN is located. a tracking area code and/or a cell identifier of a cell serving the MRN under the DeNB where the gateway serving the MRN is located.
  • the method further includes:
  • the MME After determining that the relocation of the gateway serving the MRN needs to be performed, the MME determines to perform relocation of the gateway serving the MRN.
  • the method further includes: After determining that the MME needs to perform the relocation of the gateway serving the MRN, the MME determines whether the target DeNB of the MRN satisfies the gateway relocation under the system architecture of the DeNB built in the gateway for the MRN. a condition, if satisfied, the MME determines to perform relocation of a gateway serving the MRN; if not, the MME determines not to perform relocation of a gateway serving the MRN;
  • the MME determines to perform relocation of the gateway serving the MRN after determining that the relocation of the gateway serving the MRN needs to be performed.
  • the method further includes:
  • the MME determines to perform relocation of the gateway serving the MRN, performing relocation of the gateway serving the MRN, where the relocation includes a packet data network gateway P-GW serving the MRN And/or relocation of the serving gateway S-GW; and transferring the Packet Data Nework (PDN) connection of the MRN to the relocated gateway.
  • PDN Packet Data Nework
  • the MME determines whether the target DeNB of the MRN meets a gateway relocation condition, and includes:
  • the MME determines whether the tracking area supported by the target DeNB includes a tracking area supported by the DeNB where the gateway currently serving the MRN is located.
  • the MME determines whether the target DeNB of the MRN meets a gateway relocation condition, and includes:
  • PLMN public land mobile network
  • the MME determines whether the PLMN where the target DeNB is located includes the PLMN where the DeNB currently serving the MRN is located.
  • the embodiment of the invention further provides a method for gateway relocation, including:
  • the MRN In the process of the mobile relay node MRN switching the host base station DeNB, the MRN is shifted
  • the MME receives the relocation judgment indication information, and determines, according to the relocation judgment indication information, whether relocation of the gateway serving the MRN needs to be performed;
  • the relocation determination indication information is that the source DeNB or the target DeNB of the MRN determines, according to the relocation determination assistance information, whether to perform relocation of the gateway serving the MRN, and then sends the information to the MME; or The target DeNB of the MRN determines whether it is necessary to perform relocation of the gateway serving the MRN according to the configuration information, and then sends the information to the MME.
  • the relocation determining auxiliary information includes: counting information used to count the number of times that the MRN performs switching after the last time the gateway relocation occurs; or
  • the MRN generates identification information of the source cell or the target cell when the gateway is relocated; or the MRN records information of the historical visited cell after the last time the gateway relocation occurs.
  • the source DeNB or the target DeNB 4 of the MRN determines, according to the relocation determining auxiliary information, whether to perform relocation of the gateway serving the MRN, including:
  • the method further includes:
  • the target DeNB is built in the target DeNB.
  • the address information of the gateway of the MRN service is sent to the MME as the relocation judgment indication information; after receiving the address information of the gateway serving the MRN, the MME determines that the relocation of the gateway serving the MRN needs to be performed. .
  • the method further includes:
  • the MME determines to perform relocation of the gateway serving the MRN.
  • the method further includes:
  • the MME determines whether the target DeNB of the MRN is satisfied. a gateway relocation condition, if satisfied, the MME determines to perform relocation of a gateway serving the MRN; if not, the MME determines not to perform relocation of a gateway serving the MRN;
  • the MME determines to perform relocation of the gateway serving the MRN after determining that the relocation of the gateway serving the MRN needs to be performed.
  • the method further includes:
  • the MME determines to perform relocation of the gateway serving the MRN, performing relocation of the gateway serving the MRN, where the relocation includes at least a packet data network gateway P- serving the MRN.
  • the relocation determining auxiliary information is saved by using context information of the MRN.
  • the DeNB saves and maintains; when the MRN is handed over, the relocation determining assistance information is sent by the source DeNB to the target DeNB.
  • the method further includes:
  • the relocation determination auxiliary information includes the counting information
  • the counting information is cleared, where The counting information is obtained by the source DeNB or the target DeNB of the MRN adding 1 to the counting information when the MRN does not need to perform the relocation process of the relocation of the gateway serving the MRN.
  • the source DeNB or the target DeNB adds the indication information to the source cell or the target cell corresponding to the current handover in the historical visited cell list of the MRN;
  • the source DeNB or the target DeNB sets the identification information of the source cell or the target cell corresponding to the current handover as the relocation judgment.
  • the source DeNB or the target DeNB clears the historical access cell record information when the relocation determining assistance information includes the historical visited cell record information of the MRN after the last occurrence of the gateway relocation.
  • the MME determines, according to the relocation determination indication information, whether the execution needs to be performed.
  • Relocation of the gateway of the MRN service including:
  • the MME determines that relocation of the gateway serving the MRN needs to be performed; The MME determines that the relocation of the gateway serving the MRN does not need to be performed when the MMME does not receive the relocation determination indication information or the relocation determination indication information indicates that relocation is not required to be performed; or
  • the relocation determination indication information is implicit indication information
  • the relocation determination indication information is used as an address implicit indication of a gateway served by the MRN
  • the MME receives the address
  • the MME determines that relocation of the gateway serving the MRN needs to be performed; when the MME does not receive the address, the MME determines that relocation of the gateway serving the MRN does not need to be performed.
  • the embodiment of the present invention further provides a mobility management entity, including: a location determining unit and a first determining unit, where:
  • the location determining unit is configured to: determine, in a process in which the mobile relay node MRN switches the donor base station DeNB, a current location of the MRN;
  • the first determining unit is configured to: determine, according to the current location of the MRN, whether to perform relocation of the gateway that performs the MRN service.
  • the first determining unit is configured to determine, according to the current location of the MRN, whether to perform relocation of a gateway serving the MRN in the following manner:
  • the location determining unit is configured to determine a current location of the MRN by: obtaining the MRN according to a tracking area code and/or a cell identifier of a cell under the DeNB where the MRN is currently located. Current location
  • the location determining unit is further configured to: obtain a location of a gateway serving the MRN according to the saved location-related information of the gateway serving the MRN;
  • the first determining unit is configured to determine, according to a distance between the MRN and a gateway serving the MRN, whether to perform relocation of a gateway serving the MRN: according to a current state of the MRN.
  • the location and the location of the gateway serving the MRN determine the distance between the MRN and the gateway serving the MRN, and determine whether a relocation of the gateway serving the MRN needs to be performed.
  • the mobility management entity further includes: a second determining unit, where:
  • the second determining unit is configured to: after the first determining unit determines that the relocation of the gateway serving the MRN needs to be performed, and determines that the gateway served by the MRN is built in the system architecture of the DeNB, Whether the target DeNB of the MRN satisfies the gateway relocation condition, and if so, determines to perform relocation of the gateway serving the MRN; if not, determines not to perform relocation of the gateway serving the MRN.
  • the second determining unit is configured to determine whether the target DeNB of the MRN meets a gateway relocation condition in the following manner:
  • the second determining unit is configured to determine whether the target DeNB of the MRN meets a gateway relocation condition in the following manner:
  • Determining whether the public land mobile network PLMN in which the target DeNB is located includes the PLMN in which the MRN is located; or determining whether the PLMN in which the target DeNB is located includes the PLMN in which the DeNB currently serving the MRN is located.
  • An embodiment of the present invention further provides a mobility management entity, including: a receiving unit and a relocation determining unit, where: The receiving unit is configured to: receive relocation determination indication information during a process in which the mobile relay node MRN switches the donor base station DeNB;
  • the relocation determining unit is configured to: determine, according to the relocation determining indication information, whether relocation of a gateway serving the MRN needs to be performed;
  • the relocation determination indication information is that the source DeNB or the target DeNB of the MRN determines, according to the relocation determination auxiliary information, whether to perform relocation of the gateway serving the MRN, and then sends the information to the receiving unit; or The target DeNB of the MRN determines, according to the configuration information, whether it needs to perform relocation of the gateway serving the MRN, and then sends the information to the receiving unit.
  • the relocation determining unit is configured to determine, according to the relocation determining indication information, whether to perform relocation of a gateway serving the MRN in the following manner:
  • the relocation determination indication information is explicit indication information
  • when the relocation determination indication information indicates that relocation needs to be performed it is determined that relocation of the gateway serving the MRN needs to be performed.
  • the relocation determination indication information or the relocation determination indication information indicates that relocation is not required to be performed, it is determined that relocation of the gateway serving the MRN is not required to be performed;
  • the relocation determination indication information is implicit indication information
  • the relocation determination indication information is used as an address implicit indication of a gateway served by the MRN
  • the embodiment of the present invention further provides a host base station, including: a determining unit and a sending unit, where: the determining unit is configured to: determine, according to the relocation determining auxiliary information, in the process of the mobile relay node MRN switching the host base station DeNB Re-positioning of the gateway serving the MRN needs to be performed; or determining, according to the configuration information, whether relocation of the gateway serving the MRN needs to be performed;
  • the sending unit is configured to: send relocation judgment indication information to the mobility management entity MME of the MRN.
  • the relocation determining auxiliary information includes: counting information used to count the number of times that the MRN switches after the last time the gateway relocation occurs; or In the history access cell list of the MRN, used to mark the indication information of the source cell or the target cell when the MRN generates a gateway relocation; or
  • the MRN generates identification information of the source cell or the target cell when the gateway is relocated; or the MRN records information of the historical visited cell after the last time the gateway relocation occurs.
  • the determining unit is configured to determine, according to the relocation determining auxiliary information, whether the relocation of the gateway serving the MRN needs to be performed according to the following manner:
  • the sending unit is configured to send relocation determination indication information to the MME of the MRN in the following manner:
  • the determining unit determines that the relocation of the gateway serving the MRN needs to be performed, the address information of the gateway served by the MRN is determined as the relocation according to the system architecture of the gateway served by the MRN.
  • the indication information is sent to the MME.
  • the host base station further includes an information maintenance unit, where:
  • the information maintenance unit is configured to: after performing relocation of the gateway serving the MRN in the current handover process, when the relocation determination auxiliary information includes the counting information, clear the counting information,
  • the counting information is obtained by the source DeNB or the target DeNB of the MRN adding 1 to the counting information when the MRN does not need to perform the handover process of the relocation of the gateway serving the MRN.
  • the relocation determining assistance information includes the indication information, adding indication information to an item of a source cell or a target cell corresponding to the current handover in the historical visited cell list of the MRN;
  • the information includes the identification information, the identification information of the source cell or the target cell corresponding to the current handover is set as the relocation determination auxiliary information;
  • the re-location determining assistance information includes the history access cell record information of the MRN after the last time the gateway relocation occurs, and clearing the historical visited cell record information.
  • the MRN it can be determined whether the MRN is performed during the handover process.
  • the problem of gateway relocation enables route optimization to be performed smoothly, thereby shortening the delay of UE data and signaling.
  • FIG. 1 is a schematic diagram of a first architecture of a mobile relay system in a high-speed rail scenario
  • FIG. 2 is a schematic diagram of route optimization in a first architecture of a mobile relay system
  • FIG. 3 is a schematic diagram of a second architecture of a mobile relay system in a high-speed rail scenario
  • FIG. 4 is a schematic flowchart of a gateway relocation method according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic flowchart of a gateway relocation method according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic flowchart of a gateway relocation method according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic flowchart of a gateway relocation method according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic flowchart of a gateway relocation method according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic flowchart of a gateway relocation method according to Embodiment 6 of the present invention.
  • FIG. 10 is a structural diagram of a mobility management entity according to an embodiment of the present invention.
  • FIG. 11 is a block diagram of another mobility management entity according to an embodiment of the present invention.
  • FIG. 12 is a structural diagram of a host base station according to an embodiment of the present invention. Preferred embodiment of the invention
  • the mobility management entity serving the mobile relay node determines, according to the current location of the mobile relay node, whether to perform relocation of the gateway serving the mobile relay node. .
  • the mobility management entity determines, according to the current location of the mobile relay node, whether to perform relocation of the gateway serving the mobile relay node, including:
  • the mobility management entity determines, according to the distance between the mobile relay node and the gateway serving the mobile relay node, whether to perform relocation of the gateway serving the mobile relay node, when the mobile relay node is currently a mobile relay node When the distance between the serving gateways is greater than the gateway relocation distance threshold, the mobility management entity determines that the relocation of the gateway serving the mobile relay node needs to be performed; When the distance between the node and the gateway currently serving the mobile relay node is not greater than the gateway relocation distance threshold, the mobility management entity determines that the relocation of the gateway does not need to be performed.
  • the mobility management entity determines, according to the distance between the mobile relay node and the gateway serving the mobile relay node, whether to perform relocation of the gateway serving the mobile relay node, including:
  • the mobility management entity stores the location-related information of the gateway currently serving the mobile relay node, where the location-related information of the gateway serving the mobile relay node refers to the tracking area code and/or the cell identifier of the cell under the host base station where the gateway is located;
  • a cell refers to a cell serving a mobile relay node under a host base station when the mobile relay node accesses the donor base station;
  • the mobility management entity obtains the location of the gateway serving the mobile relay node based on the location-related information of the gateway serving the mobile relay node;
  • the mobility management entity obtains a current location of the mobile relay node according to a tracking area code and/or a cell identifier of a cell under the host base station where the mobile relay node is located;
  • the mobility management entity determines the distance between the mobile relay node and the gateway serving the mobile relay node according to the current location of the mobile relay node and the location of the gateway serving the mobile relay node, and determines whether it needs to be performed as a mobile relay. Relocation of the gateway served by the node.
  • the mobility management entity of the mobile relay node receives the relocation determination indication information, and determines, according to the relocation determination indication information, whether the gateway serving the mobile relay node needs to be executed. Relocation
  • the relocation determination indication information is that the source-homing base station or the target-homing base station of the mobile relay node determines, according to the relocation determination auxiliary information, whether to perform relocation of the gateway serving the mobile relay node, and then sends the information to the mobility management entity; or The target host base station that is the mobile relay node determines whether it needs to perform relocation of the gateway serving the mobile relay node according to the configuration information, and then sends the information to the mobility management entity.
  • the relocation judgment indication information is used to indicate whether relocation of the gateway needs to be performed.
  • Relocation judgment auxiliary information including:
  • Counting information used to count the number of times the mobile relay node switches after the last time the gateway relocation occurs; wherein, after each mobile relay node switches, the counting information needs to be entered.
  • the line is accumulated and passed between the source host base station and the target host base station;
  • the indication information may be one bit, and is marked in the historical visited cell list. In the entry of the corresponding source cell or target cell.
  • the identification information of the source cell or the target cell when the mobile relay node generates the relocation of the gateway where the identifier information includes at least the cell identifier
  • the mobile relay node records the historical access cell record information after the last occurrence of the gateway relocation.
  • the relocation judgment assistance information is saved and maintained by the donor base station holding the context information of the mobile relay node.
  • the source host base station transmits the relocation judgment auxiliary information to the target host base station directly or through other network elements.
  • the host base station storing the context information of the mobile relay node saves and maintains the relocation judgment auxiliary information, including: if the source host base station or the target host base station determines that the relocation of the gateway needs to be performed: when the relocation determines that the auxiliary information is the count information.
  • the source host station or the target host base station clears the count information.
  • the count information is a source DeNB or a target DeNB pair of the MRN when the MRN does not need to perform the handover process of the relocation of the gateway serving the MRN every time the MRN occurs. Adding 1 to the count information;
  • the source host base station or the target host base station adds the indication information to the source cell or the target cell corresponding to the current handover in the historical access cell list of the mobile relay node;
  • the source host station or the target host base station sets the identification information of the source cell or the target cell corresponding to the current handover as the relocation determination auxiliary information;
  • the relocation judgment auxiliary information is the historical access cell record information
  • the source host base station or the target host base station clears the historical access cell record information. After the mobile relay node switches, the historical access cell record information needs to be updated.
  • the foregoing configuration information is indication information indicating whether it is necessary to perform relocation of a gateway serving the MRN; for example, operation and maintenance management of the network management system ( (Operation Administration and Maintenance, OAM) Configures the configuration information indicating that the gateway relocation needs to be performed for the DeNB deployed in the station along the high-speed rail.
  • OAM Operaation Administration and Maintenance
  • the source-homing base station or the target-homing base station of the mobile relay node determines whether it is necessary to perform relocation of the gateway serving the mobile relay node according to the relocation judgment auxiliary information, including:
  • the source or base station base station determines, according to the relocation determining assistance information, the number of cells visited by the mobile relay node after the last gateway relocation;
  • the source host base station or the target host base station determines whether the number of cells visited by the mobile relay node after the last relocation of the gateway served by the mobile relay node reaches the threshold number of visited cells, and if so, determines that the MRN service needs to be performed. Relocation of the gateway.
  • the number of visited cells can be obtained by pre-configuration or by the network management system.
  • the source-homing base station or the target-homing base station determines, according to the relocation determining auxiliary information, the number of cells that the mobile relay node accesses after the last gateway relocation, including:
  • the relocation judgment auxiliary information is the counting information
  • the number of cells actually accessed after the relocation gateway can be directly obtained according to the value
  • the relocation auxiliary information is the indication information
  • the calculated value is also decremented by 1 to obtain the number of cells actually accessed after the relocation gateway is obtained;
  • the relocation auxiliary information is the identification information
  • the identifier information is searched from the historical access cell list of the mobile relay node, and the number of cells visited by the MRN after the item of the identification information in the list is calculated, and the identification information is the source cell.
  • the identification information it is also necessary to decrement the calculated value by 1 to obtain the number of cells actually accessed after relocating the gateway;
  • the relocation auxiliary information is the historical access cell record information in the historical access cell list of the mobile relay node after the last time the gateway relocation occurs, the record included in the history access cell record information is directly calculated. The number of bars that are actually accessed after the relocation gateway is obtained.
  • the historical visited cell list in (2) and (3) above may be a historical visited cell list, and the historical visited cell list in (4) may be the historical visited cell list in (2) and (3).
  • the same historical visited cell list, the historical visited cell list in (2) and (3) can save the cell accessed multiple times before and after the gateway relocation; (4) The historical visited cell list is saved after the last gateway relocation is saved. Community.
  • the source host base station or the target host base station sends relocation judgment indication information to the mobility management entity directly or through other network elements.
  • the relocation judgment indication information is an explicit indication information or an implicit information implicitly indicated by a specific cell.
  • the specific cell includes address information of a gateway built in the host base station.
  • the mobility management entity determines, according to the relocation determination indication information, whether to perform relocation of the gateway serving the mobile relay node, including:
  • the relocation judgment indication information is an explicit indication information
  • the mobility management entity determines that the relocation of the gateway needs to be performed; if the mobility management entity does not receive the relocation judgment
  • the indication information or the relocation judgment indication information indicates that the relocation of the gateway does not need to be performed, the mobility management entity determines that the relocation of the gateway does not need to be performed;
  • the relocation judgment indication information is implicit information, and is used to indicate the specific cell of the implicit information.
  • the mobility management entity In the case of the address information of the gateway, if the mobility management entity receives the address information of the gateway, it is determined that the relocation of the gateway needs to be performed; if the mobility management entity does not receive the address information of the gateway, it is determined that the relocation of the gateway is not required to be performed.
  • the relocation of the gateway includes relocation of the packet data network gateway and/or the service gateway serving the mobile relay node. After the mobility management entity performs relocation of the gateway serving the MRN, the PDN connection of the mobile relay node is transferred to the relocated gateway.
  • the relocation of the gateway may also include relocation of the trunking gateway.
  • the mobility management entity determines the mobile relay node. Whether the target home base station satisfies the gateway relocation condition, if satisfied, the mobility management entity determines to perform relocation of the gateway serving the mobile relay node; if not, the mobility management entity determines not to perform the service for the mobile relay node Relocation of the gateway; After the gateway serving the mobile relay node is located in the core network, the MME determines to perform relocation of the gateway as the mobile relay node after determining that the relocation of the gateway serving the MRN needs to be performed.
  • the mobile management entity determines to perform relocation of the gateway serving the mobile relay node.
  • the mobility management entity determines whether the target host base station of the mobile relay node satisfies the gateway relocation condition, and includes:
  • the mobility management entity determines whether the tracking area supported by the target host base station includes a tracking area supported by the mobile relay node;
  • the mobility management entity determines whether the tracking area supported by the target host base station includes a tracking area supported by the host base station where the gateway currently serving the mobile relay node is located.
  • the mobility management entity determines whether the target host base station of the mobile relay node satisfies the gateway relocation condition, and includes:
  • the mobility management entity determines whether the PLMN where the target host base station is located includes the PLMN where the mobile relay node is located;
  • the mobility management entity determines whether the PLMN where the target donor base station is located contains the PLMN where the host base station where the gateway currently serving the mobile relay node is located.
  • the following embodiments are applicable to both mobile relay system architectures shown in Figures 1 and 3.
  • the S-GW and the P-GW serving the MRN are both built in the DeNB.
  • the S-GW and P-GW serving the MRN are not built into the DeNB, but It is located in the core network as an independent network element.
  • FIG. 4 is a flowchart of the embodiment, where the flow is a process in the case of the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB, or may not be built in The source DeNB is built in the initial DeNB.
  • the method of this embodiment is also applicable to the mobile relay system architecture shown in FIG. 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW and the target P-GW are all located in the core network.
  • the process described in this embodiment includes the following steps:
  • Step 401 The MRN measures, by the MRN, that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report by using the measurement report.
  • Step 402 After receiving the measurement report of the MRN, the source DeNB determines that there is an X2 interface between the source DeNB and the target DeNB, and the MRN does not need to replace the MME after the handover, and the source DeNB initiates an X2 handover for the MRN.
  • the source DeNB selects a target cell for the MRN according to the measurement.
  • the source DeNB sends an X2 interface handover request message to the target DeNB.
  • the handover request message includes relocation judgment assistance information for transmitting the relocation judgment assistance information to the target DeNB.
  • the relocation judgment auxiliary information includes one of the following:
  • the identification information of the source cell or the target cell when the MRN is relocated by the MRN where the cell identity information includes an Evolved Cell Global Identifier (ECGI);
  • ECGI Evolved Cell Global Identifier
  • the MRN records the historical access cell record information after the last occurrence of the gateway relocation.
  • Step 403 The target DeNB selects the Evolved Universal Terrestrial Radio Access Network (EUTRAN)-Radio Access Bearer (E-RAB) according to the handover request message.
  • Information such as of Service, QoS) reserves resources for the MRN and creates context information, and then replies to the handover request acknowledgement message.
  • the handover request acknowledgement message includes a transparent command message of the transparent air interface.
  • Step 404 The source DeNB sends an air interface control radio resource control (RRC) connection reconfiguration message to the MRN, where the RRC connection reconfiguration message carries the target DeNB.
  • RRC radio resource control
  • Step 405 The source DeNB sends a sequence number (SN) status transfer message to the target DeNB, and is used to transmit an uplink and downlink packet data convergence protocol of a radio link control acknowledgement mode (RCC AM) radio bearer.
  • RRCAM radio link control acknowledgement mode
  • Step 406 After receiving the handover command, the MRN detaches from the cell of the source DeNB, synchronizes with the target cell, and initiates a random access channel (RACH) process to access the target cell. After completing the RRC connection establishment with the target cell, the MRN sends an RRC connection reconfiguration complete message to the target DeNB.
  • RACH random access channel
  • Step 407 The target DeNB determines, according to the relocation determining auxiliary information, whether it is necessary to perform relocation of the gateway.
  • the target DeNB first determines the number of cells visited by the MRN after the last gateway relocation according to the relocation determining assistance information, and then determines whether it is necessary to perform relocation of the gateway according to the number of visited cells. If the number of cells visited by the MRN after the last gateway relocation exceeds the pre-configured or the number of visited cells obtained from the OAM, it is determined that the relocation of the gateway needs to be performed; if the number of visited cells that are pre-configured or acquired from the OAM is not exceeded The threshold value determines that the relocation of the gateway does not need to be performed. In addition, the target DeNB needs to save and maintain the relocation judgment auxiliary information. If the target DeNB determines that the relocation of the gateway needs to be performed, and
  • the target DeNB clears the counting information; wherein, the counting information is a switching process of relocation of the gateway that does not need to perform the service for the MRN every time the MRN occurs, The source DeNB or the target DeNB of the MRN adds 1 to the counting information;
  • the target DeNB adds the indication information to the source cell or the target cell corresponding to the current handover in the historical visited cell list of the mobile relay node;
  • the target DeNB sets the identification information of the source cell or the target cell corresponding to the current handover as the relocation determining auxiliary information
  • the relocation judgment auxiliary information is historical access cell record information
  • the target DeNB The historical access cell record information is cleared. After the mobile relay node switches, the historical access cell record information needs to be updated.
  • Step 408 After receiving the RRC connection reconfiguration complete message sent by the MRN, the target DeNB sends a path transfer request message to the MME of the MRN to update the S1 user plane and the control plane path of the MRN.
  • the path transfer request message includes relocation judgment indication information, which is used to indicate whether relocation of the gateway needs to be performed.
  • the relocation determination indication information may be explicit indication information.
  • the path transfer request message further includes an address of the S-GW and the P-GW built in the target DeNB to assist the MRN.
  • the MME relocates the gateway of the MRN to the gateway in the target DeNB.
  • the relocation judgment indication information may also be implicit information implicitly indicated by a specific cell.
  • the specific cell may be the address information of the S-GW and the P-GW built in the target DeNB. If the relocation of the gateway needs to be performed, the address information of the GW built in the DeNB may be carried in the relocation judgment indication message. To indicate to the MME.
  • Step 409 The MME determines whether to perform relocation of the gateway.
  • the MME first determines whether the relocation of the gateway is required according to the received relocation determination instruction information. The judgment process is described as follows:
  • the relocation determination indication information is an explicit indication, if the relocation determination indication information indicates that the relocation of the gateway needs to be performed, the MME determines that the relocation of the gateway needs to be performed; if the MME does not receive the relocation determination indication information or The positioning judgment indication information indicates that the relocation of the gateway does not need to be performed, and the MME determines that the relocation of the gateway does not need to be performed;
  • the relocation determination indication information is implicit information, and is used to indicate that the specific information of the implicit information is the address information of the gateway built in the DeNB,
  • the MME receives the address information of the gateway, and determines that the relocation of the gateway needs to be performed. If the MME does not receive the address information of the gateway, it is determined that the relocation of the gateway does not need to be performed.
  • the mobile relay system architecture shown in FIG. 1 is used. If the MME determines that the relocation of the gateway needs to be performed, it is also required to determine whether the target DeNB satisfies the condition of the gateway relocation. If yes, the MME determines to perform the gateway. Relocation; if not, the MME determines not to perform relocation of the gateway. If the MME determines to perform the relocation of the gateway, the S-GW and the P-GW built in the target DeNB are selected as the new gateway serving the MRN according to the address of the received gateway (referred to as the target S-GW and the target). P-GW).
  • the conditions for the relocation of the gateway include:
  • the Tracking Area (TA) supported by the target DeNB includes the TA supported by the MRN.
  • the TA supported by the target DeNB needs to include the dedicated TA. If the dedicated TA is configured for the MRN, the TA supported by the target DeNB needs to include the initial DeNB (ie, the MRN). The TA supported by the S-GW and the DeNB where the P-GW is located.
  • the gateway relocation condition further includes: the PLMN where the target DeNB is located needs to include the PLMN where the MRN is located. This condition can be judged by whether the PLMN in which the target DeNB is located contains the PLMN in which the initial DeNB is located.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in FIG. Then, if the MME determines that the relocation of the gateway needs to be performed, it is not required to determine whether the condition of the gateway relocation is met, and the relocation of the gateway that performs the MRN service is determined; if the MME determines that the relocation of the gateway is not required to be performed, it is determined not to Perform a relocation of the gateway serving the MRN. If the MME determines to perform the relocation of the gateway, it reselects the new gateway (referred to as the target S-GW and the target P-GW) located in the core network for the MRN.
  • the target S-GW and the target P-GW the new gateway located in the core network for the MRN.
  • Step 410 The MME of the MRN sends a Create Session Request message to the target S-GW (S-GW built in the target DeNB), where the Evolved Packet System (EPS) bearer information of the MRN to be created and the target P- are included.
  • S-GW built in the target DeNB
  • EPS Evolved Packet System
  • P-GW built in the target DeNB
  • Step 411 The target S-GW creates a context of the MRN, and sends a create session request message to the target P-GW.
  • Step 412 After the target P-GW creates the context and the EPS bearer of the MRN, the target P-GW replies to the target S-GW to create a session response message.
  • the target P-GW can assign a new IP address to the MRN.
  • the target S-GW and the P-GW are built in the DeNB, and the signaling in step 411 and step 412 are internal interface messages in the target DeNB.
  • Step 413 The target S-GW replies to the MME of the MRN to create a session response message to confirm The context of the MRN and the establishment of the EPS 7 are completed.
  • Step 414 The MME of the MRN sends a path transfer request acknowledgement message to the target DeNB. Then, the MRN or the target DeNB may initiate a path transfer request process for the UE served by the MRN to transfer the downlink S1 path of the UE. The target DeNB then instructs the source DeNB and the built-in source S-GW and the source P-GW to release the resources of the MRN.
  • FIG. 5 illustrates the flow of the embodiment, where the flow is in the case of the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB or may not be built in the source.
  • the DeNB is built in the initial DeNB.
  • the method of this embodiment is also applicable to the mobile relay system architecture shown in Figure 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW and the target P-GW are all located in the core network.
  • Step 501 The MRN measures, by the MRN, that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report by using the measurement report.
  • Step 502 The source DeNB determines, according to the relocation in the context of the MRN that it maintains, the auxiliary information to determine whether the relocation of the gateway needs to be performed.
  • the source DeNB first determines the number of cells that the MRN accesses after the last gateway relocation according to the relocation determination assistance information, and then determines whether the relocation of the gateway needs to be performed according to the number of visited cells. If the number of cells visited by the MRN after the last gateway relocation exceeds the pre-configured or the number of visited cells obtained from the OAM, it is determined that the relocation of the gateway needs to be performed; if the number of visited cells that are pre-configured or acquired from the OAM is not exceeded The threshold value determines that the relocation of the gateway does not need to be performed.
  • the relocation judgment auxiliary information includes at least one of the following:
  • the identification information of the source cell or the target cell when the MRN has a relocation of the gateway where the cell identity information includes the cell identity ECGI;
  • the MRN records the historical access cell record information after the last occurrence of the gateway relocation.
  • the source DeNB needs to maintain the relocation determining auxiliary information according to the judgment result. If the source DeNB determines that the relocation of the gateway needs to be performed, then
  • the source DeNB clears the counting information; wherein, the counting information is a switching process that does not need to perform relocation of the gateway serving the MRN every time the MRN occurs, The source DeNB or the target DeNB of the MRN adds 1 to the counting information;
  • the source DeNB adds the indication information to the source cell or the target cell corresponding to the current handover in the historical visited cell list of the mobile relay node;
  • the source DeNB sets the identification information of the source cell or the target cell corresponding to the current handover as the relocation determining auxiliary information
  • the target DeNB clears the historical access cell record information. After the mobile relay node switches, the historical access cell record information needs to be updated.
  • Step 503 After receiving the measurement report of the MRN, the source DeNB determines that there is an X2 interface between the source DeNB and the target DeNB, and after the handover, the MRN does not need to replace the MME, and the source DeNB initiates an X2 handover for the MRN.
  • the source DeNB selects a target cell for the MRN according to the measurement report.
  • the source DeNB sends an X2 interface handover request message to the target DeNB.
  • the handover request message includes relocation determination assistance information for transmitting the relocation judgment assistance information to the target DeNB.
  • the handover request message further includes relocation judgment indication information for indicating whether relocation of the gateway needs to be performed.
  • Steps 504-507 are the same as steps 403-406 and will not be repeated here.
  • Step 508 After receiving the RRC connection reconfiguration complete message sent by the MRN, the target DeNB sends a path transfer request message to the MME of the MRN to update the S1 user plane and the control plane path of the MRN.
  • the path transfer request message includes relocation judgment indication information, and is used to indicate whether Perform a relocation of the gateway.
  • the relocation judgment indication information may be explicit indication information, and in the case that relocation of the gateway needs to be performed, the path transfer request message further includes an address of the S-GW and the P-GW built in the target DeNB to assist the MRN.
  • the MME relocates the gateway of the MRN to the gateway in the target DeNB.
  • the relocation judgment indication information may also be implicit information implicitly indicated by a specific cell.
  • the specific cell may be the address information of the S-GW and the P-GW built in the target DeNB. If the relocation of the gateway needs to be performed, the address information of the GW built in the DeNB may be carried in the relocation judgment indication message. To indicate to the MME.
  • Step 509 The MME determines whether to perform relocation of the gateway.
  • the MME first determines whether the relocation of the gateway is required according to the received relocation determination instruction information. The judgment process is described as follows:
  • the relocation determination indication information is an explicit indication, if the relocation determination indication information indicates that the relocation of the gateway needs to be performed, the MME determines that the relocation of the gateway needs to be performed; if the MME does not receive the relocation determination indication information or The positioning judgment indication information indicates that the relocation of the gateway does not need to be performed, and the MME determines that the relocation of the gateway does not need to be performed;
  • the relocation judgment indication information is implicit information, and is used to indicate that the specific information of the implicit information is the address information of the gateway built in the DeNB, if the MME Receiving the address information of the gateway, determining that the relocation of the gateway needs to be performed; if the MME does not receive the address information of the gateway, determining that the relocation of the gateway is not required to be performed;
  • the mobile relay system architecture shown in FIG. 1 is used. If the MME determines that the relocation of the gateway needs to be performed, it is also required to determine whether the target DeNB satisfies the condition of the gateway relocation. If yes, the MME determines to perform the gateway. Relocation; if not, the MME determines not to perform relocation of the gateway. If the MME determines to perform the relocation of the gateway, the S-GW and the P-GW built in the target DeNB are selected as the new gateway serving the MRN according to the address of the received gateway (referred to as the target S-GW and the target). P-GW).
  • the conditions for the gateway relocation include: The target DeNB supports the TA including the MRN support.
  • the gateway relocation condition further includes: the PLMN supported by the target DeNB needs to include the PLMN supported by the MRN. This condition can be determined by whether the PLMN supported by the target DeNB includes the PLMN supported by the initial DeNB.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in FIG. Then, if the MME determines that the relocation of the gateway needs to be performed, it is not required to determine whether the condition of the gateway relocation is met, and the relocation of the gateway that performs the MRN service is determined; if the MME determines that the relocation of the gateway is not required to be performed, it is determined not to Perform a relocation of the gateway serving the MRN. If the MME determines to perform the relocation of the gateway, it reselects the new gateway (referred to as the target S-GW and the target P-GW) located in the core network for the MRN.
  • the target S-GW and the target P-GW the new gateway located in the core network for the MRN.
  • Steps 510-514 are the same as steps 410-414 and will not be repeated here.
  • FIG. 6 illustrates the flow of the embodiment, where the process is the same as the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB or may not be built in the source.
  • the DeNB is built in the initial DeNB.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in FIG. 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW, and the target P-GW are all located in the core network.
  • Step 601 The MRN measures that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report.
  • Step 602 After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source DeNB and the target DeNB, or needs to reselect an MME for the MRN, and needs to perform an S1 handover for the source DeNB, and the source DeNB selects one for the MRN according to the measurement report. Target cell.
  • the source DeNB sends an S1 interface handover request message to the source MME of the MRN.
  • the handover request message includes relocation judgment assistance information for transmitting the relocation judgment assistance information to the target DeNB.
  • the relocation judgment assistance information is stored in the context of the MRN in the source DeNB.
  • the source DeNB may send the relocation determining assistance information through a transparent transmission container of the source base station to the target base station.
  • the relocation judgment auxiliary information includes at least one of the following: 1) counting information for counting the number of times the MRN has switched after the last occurrence of gateway relocation;
  • the identification information of the source cell or the target cell when the MRN has a relocation of the gateway where the cell identity information includes the cell identity ECGI;
  • the MRN records the historical access cell record information after the last occurrence of the gateway relocation.
  • Step 603 The source MME determines, according to the base station identifier or the Tracking Area Identifier (TAI) of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, select a target according to the two parameters. And sending, by the MME, a forwarding relocation request message, where the transparent transmission container, the target base station identifier, the target location area identifier, and the MRN context information of the source base station to the target base station are carried. If the source MME of the MRN receives the relocation determination assistance information from the source DeNB, the forward relocation request message includes the received relocation determination assistance information.
  • the relocation judging assistance information may be included in a transparent transmission container of the source base station to the target base station.
  • Step 604 The target MME of the MRN sends an S1 interface handover request message to the target DeNB.
  • the S1 interface switching request message includes relocation determining assistance information received by the target MME from the source MME.
  • the relocation judging assistance information may be included in a transparent transmission container of the source base station to the target base station.
  • Step 605 The target DeNB determines, according to the relocation determining auxiliary information, whether it is necessary to perform relocation of the gateway.
  • the target DeNB first determines the number of cells that the MRN accesses after the last gateway relocation, and then determines whether the relocation of the gateway needs to be performed according to the number of visited cells. If the number of cells visited by the MRN after the last gateway relocation exceeds the pre-configured or the number of visited cells obtained from the OAM, it is determined that the relocation of the gateway needs to be performed; if the number of visited cells that are pre-configured or acquired from the OAM is not exceeded The threshold value determines that the relocation of the gateway does not need to be performed. In addition, the target DeNB needs to save and maintain the relocation judgment auxiliary information. If the target DeNB determines that the relocation of the gateway needs to be performed, and
  • the target DeNB clears the counting information; wherein, the counting information is a switching process of relocation of the gateway that does not need to perform the service for the MRN every time the MRN occurs, The source DeNB or the target DeNB of the MRN counts the number Add 1 to the information;
  • the target DeNB When the relocation judgment auxiliary information is the indication information, the target DeNB adds the indication information in the item of the source cell or the target cell corresponding to the current handover in the historical visited cell list of the mobile relay node; 3) when relocating When the determining that the auxiliary information is the cell identification information, the target DeNB sets the identification information of the source cell or the target cell corresponding to the current handover as the relocation determining auxiliary information;
  • the target DeNB clears the historical access cell record information. After the mobile relay node switches, the historical access cell record information needs to be updated.
  • Step 606 After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN.
  • the handover request acknowledgement message includes relocation judgment indication information for indicating whether to perform relocation of the gateway.
  • the relocation judgment indication information may be explicit indication information, and in the case that relocation of the gateway needs to be performed, the handover request acknowledgement message further includes an address of the S-GW and the P-GW built in the target DeNB to assist the MRN.
  • the MME relocates the gateway of the MRN to the gateway in the target DeNB.
  • the relocation judgment indication information may also be implicit information implicitly indicated by a specific cell.
  • the specific cell may be the address information of the S-GW and the P-GW built in the target DeNB. If the relocation of the gateway needs to be performed, the address information of the GW built in the DeNB may be carried in the relocation judgment indication message. To indicate to the MME.
  • Steps 607-611 are the same as steps 509-513 and will not be repeated here.
  • the target S-GW and the target P-GW are built in the DeNB, and the signaling in step 609 and step 610 are internal interface messages in the target DeNB.
  • Step 612 The target MME of the MRN sends a Forward Relocation Response message to the source MME. It should be noted that if it is not necessary to select a new MME, step 603 and step 612 are skipped, and the behaviors of the source MME and the target MME are the same MME behavior.
  • Step 613 The source MME of the MRN sends an S1 interface switching command message to the source DeNB.
  • a handover command message in the container is passed to instruct the MRN to perform the handover.
  • Step 615 After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH process to access the target cell. After the MRN completes the RRC connection establishment with the target cell, it sends an RRC connection reconfiguration complete message to the target DeNB.
  • Step 616 The target DeNB sends an S1 interface handover notification message to the target MME of the MRN. Then the target MME of the MRN completes the subsequent operations.
  • the MRN or the target DeNB may initiate a path transfer request process for the UE served by the MRN to transfer the downlink S1 path of the UE. Then, the resource release process of the source DeNB and the built-in source S-GW and the source P-GW is performed.
  • steps 607-611 may also be performed after step 616.
  • the relocation determination indication information may not be carried in step 606, and the relocation determination indication information may be carried in the handover notification message in step 616. Accordingly, steps 607-611 are performed after step 616.
  • FIG. 7 illustrates the flow of the embodiment, where the flow is in the case of the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB or may not be built in the source.
  • the DeNB is built in the initial DeNB.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in FIG. 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW, and the target P-GW are all located in the core network.
  • Step 701 The MRN measures, by the MRN, that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report by using the measurement report.
  • Step 702 is the same as step 502 and will not be repeated here.
  • Step 703 After receiving the measurement report of the MRN, the source DeNB determines the source DeNB and the target.
  • the source DeNB selects a target cell for the MRN according to the measurement report.
  • the source DeNB sends an S1 interface handover request message to the source MME of the MRN.
  • the handover request message includes relocation
  • the determining auxiliary information is used to deliver the relocation determining auxiliary information to the target DeNB.
  • the relocation assistance information is stored in the context of the MRN in the source DeNB.
  • the source DeNB may send the relocation determining assistance information through a transparent transmission container of the source base station to the target base station.
  • the handover request message further includes relocation judgment indication information, which is used to indicate whether relocation of the gateway needs to be performed.
  • the relocation judgment auxiliary information includes at least one of the following:
  • the identification information of the source cell or the target cell when the MRN has a relocation of the gateway where the cell identity information includes the cell identity ECGI;
  • the MRN records the historical access cell record information after the last occurrence of the gateway relocation.
  • Step 704 The source MME determines, according to the base station identifier or the target TAI of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, selects the target MME according to the two parameters, and sends a forwarding relocation to the source MME.
  • the request message carries information such as a transparent transmission container of the source base station to the target base station, a target base station identifier, a target location area identifier, and context information of the MRN. If the source MME of the MRN receives the relocation determining assistance information from the source DeNB, the forwarding relocation request message includes the received relocation determining assistance information.
  • the relocation judging assistance information may be included in a transparent transmission container of the source base station to the target base station. If the source MME receives the relocation determination indication information from the source DeNB, the forwarding relocation request message further includes relocation determination indication information.
  • Step 705 The target MME of the MRN sends an S1 interface handover request message to the target DeNB.
  • the S1 interface switching request message includes relocation determining assistance information received by the target MME from the source MME.
  • the relocation judging assistance information may be included in a transparent transmission container of the source base station to the target base station.
  • the S1 interface switching request message may further include relocation judgment indication information received from the source MME.
  • Step 706 After the target DeNB creates a context for the MRN and the UE and reserves resources for the bearer of the MRN, the target DeNB sends a handover request acknowledgement message to the target MME of the MRN. If the target DeNB receives the relocation determination indication information from the MME, and the relocation determination indication information indicates that the relocation of the gateway needs to be performed, the handover request message further includes the S-GW and the built-in D-GW in the target DeNB. The address information of the P-GW is used to assist the MMME's MME to relocate the MRN's gateway to the gateway in the target DeNB.
  • Step 707 The target MME determines whether to perform relocation of the gateway.
  • the target MME first determines whether it is necessary to perform relocation of the gateway according to the received relocation judgment indication information. If the relocation determination indication information indicates that the relocation of the gateway needs to be performed, the target MME determines that the relocation of the gateway needs to be performed; if the target MME does not receive the relocation determination indication information or the relocation determination indication information indicates that the relocation of the gateway is not required to be performed , the target MME determines that relocation of the gateway does not need to be performed;
  • the mobile relay system architecture shown in FIG. 1 is used. If the MME determines that the relocation of the gateway needs to be performed, it is also required to determine whether the target DeNB satisfies the condition of the gateway relocation. If yes, the MME determines to perform the gateway. Relocation; if not, the MME determines not to perform relocation of the gateway. If the MME determines to perform the relocation of the gateway, the S-GW and the P-GW built in the target DeNB are selected as the new gateway serving the MRN according to the address of the received gateway (referred to as the target S-GW and the target). P-GW).
  • the conditions for the gateway relocation include: The target DeNB supports the TA including the MRN support.
  • the TA supported by the target DeNB needs to include the dedicated TA. If the dedicated TA is configured for the MRN, the TA supported by the target DeNB needs to include the initial DeNB (ie, the MRN). The TA supported by the S-GW and the DeNB where the P-GW is located.
  • the gateway relocation condition further includes: the PLMN supported by the target DeNB needs to include the PLMN supported by the MRN. This condition can be judged by whether the PLMN supported by the target DeNB includes the PLMN supported by the initial DeNB.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in FIG. Then, if the MME determines that the relocation of the gateway needs to be performed, it is not required to determine whether the condition of the gateway relocation is met, and the relocation of the gateway that performs the MRN service is determined; if the MME determines that the relocation of the gateway is not required to be performed, it is determined not to Perform a relocation of the gateway serving the MRN. If the MME determines to perform the relocation of the gateway, it reselects the new gateway (referred to as the target S-GW and the target P-GW) located in the core network for the MRN.
  • the target S-GW and the target P-GW the new gateway located in the core network for the MRN.
  • Steps 708-716 are the same as steps 608-616 and will not be repeated here. It should be noted that steps 707-711 may also be performed after step 716.
  • the relocation determination indication information may not be carried in step 706, and the relocation determination indication information may be carried in the handover notification message in step 716. Accordingly, steps 707-711 are performed after step 716.
  • Steps 707-711 may also be performed after step 704 and before step 705.
  • the target MME selects a new S-GW and P-GW located in the core network for the MRN.
  • FIG. 8 depicts the flow of the embodiment, where the flow is in the case of the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB or may not be built in the source.
  • the DeNB is built in the initial DeNB.
  • the method of the embodiment is also applicable to the mobile relay system architecture shown in Figure 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW and the target P-GW are all located in the core network.
  • Step 801 The MRN measures that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report.
  • Step 802 After receiving the measurement report of the MRN, the source DeNB determines that there is an X2 interface between the source DeNB and the target DeNB, and after the handover, the MRN does not need to replace the MME, and the source DeNB initiates an X2 handover for the MRN.
  • the source DeNB selects a target cell for the MRN according to the measurement.
  • the source DeNB sends an X2 interface handover request message to the target DeNB.
  • Step 803 The target DeNB reserves resources for the MRN and creates context information according to the QoS information of the E-RAB to be established in the handover request message, and then returns a handover request acknowledgement message.
  • the handover request acknowledgement message includes a transparently transmitted handover command message.
  • Step 804 The source DeNB sends an air interface message to the MRN, and the RRC connection reconfiguration message carries a transparent handover command message sent by the source DeNB to the MRN by the source DeNB to instruct the MRN to perform handover.
  • Step 805 The source DeNB sends an SN state transition message to the target DeNB for transmitting the RLC.
  • Uplink and downlink PDCP SN receive and transmit status for AM mode radio bearers.
  • Step 806 After receiving the handover command, the MRN detaches from the source DeNB cell, synchronizes with the target cell, and initiates a RACH procedure to access the target cell. After the MRN completes the RRC connection establishment with the target cell, it sends an RRC connection reconfiguration complete message to the target DeNB.
  • Step 807 After receiving the RRC connection reconfiguration complete message sent by the MRN, the target DeNB sends a path transfer request message to the MME of the MRN to update the S1 user plane and the control plane path of the MRN.
  • the mobile relay system architecture shown in FIG. 1 is used, and the path transfer request message further includes an address of the S-GW and the P-GW built in the target DeNB, to assist the MME of the MRN to use the gateway of the MRN. Relocate to the gateway in the target DeNB. If the mobile relay system architecture shown in Figure 3 is used, the address of the S-GW and the P-GW does not need to be carried in the message.
  • Step 808 The MME determines whether to perform relocation of the gateway.
  • the MME first determines whether the relocation of the gateway needs to be performed according to the current location of the MRN.
  • the MME may obtain the current location of the MRN according to the TAI and/or ECGI of the cell of the DeNB currently serving the MRN.
  • the mobile relay system architecture shown in FIG. 1 is used, and the MME can save the TAI and/or ECGI of the cell of the initial DeNB served by the MRN when the MRN accesses the DeNB (called the initial DeNB) where the gateway is located.
  • the initial DeNB the DeNB
  • the MME determines that the relocation of the gateway needs to be performed; if not greater than the gateway relocation distance, the MME determines that the gateway does not need to be executed. Relocation.
  • the MME determines that the relocation of the gateway needs to be performed, it also needs to determine whether the target DeNB satisfies the condition of the gateway relocation. If yes, the MME determines to perform relocation of the gateway; if not, the MME determines not to perform relocation of the gateway. If the MME determines to perform the relocation of the gateway, the S-GW and the P-GW built in the target DeNB are selected as the new gateway serving the MRN according to the address of the received gateway (referred to as the target S-GW and the target). P-GW).
  • the conditions for the gateway relocation include: The TA supported by the target DeNB includes the TA supported by the MRN. If the dedicated TA is configured for the MRN, the TA supported by the target DeNB needs to include the dedicated TA. If the dedicated TA is configured for the MRN, the TA supported by the target DeNB needs to include the initial DeNB (ie, the MRN). The TA supported by the S-GW and the DeNB where the P-GW is located.
  • the gateway relocation condition further includes: a target DeNB
  • the supported PLMN needs to include the PLMN supported by the MRN. This condition can be determined by whether the PLMN supported by the target DeNB includes the PLMN supported by the initial DeNB.
  • the method described in this embodiment is also applicable to the mobile relay system architecture shown in FIG. Similarly, when the distance between the MRN and the S-GW and the P-GW is greater than the gateway relocation distance threshold, the MME determines that the relocation of the gateway needs to be performed; if not greater than the gateway relocation distance threshold, the MME determines that the MME does not need to perform Relocation of the gateway. If the MME determines that the relocation of the gateway needs to be performed, it is not required to determine whether the condition of the gateway relocation is met, and the relocation of the gateway that performs the MRN service is determined; if the MME determines that the relocation of the gateway is not required to be performed, the MME determines not to perform the relocation. Relocation of the gateway of the MRN service. If the MME determines to perform the relocation of the gateway, it reselects the new gateway (referred to as the target S-GW and the target P-GW) located in the core network for the MRN.
  • the new gateway referred to as the target S-GW and the target P
  • Steps 809-813 are the same as steps 410-414 and will not be repeated here.
  • FIG. 9 is a flowchart of the embodiment, where the flow is in the case of the architecture shown in FIG. 1, where the source S-GW and the source P-GW of the MRN may be built in the source DeNB or may not be built in the source.
  • the DeNB is built in the initial DeNB.
  • the method in this embodiment is also applicable to the mobile relay system architecture shown in Figure 3.
  • the source S-GW and the source P-GW of the MRN, the target S-GW and the target P-GW are all located in the core network.
  • Step 901 The MRN measures that the one or more cells meet the trigger condition of the measurement report, and sends the identifier and the measurement parameter of the cell that meet the condition to the source DeNB served by the measurement report by using the measurement report.
  • Step 902 After receiving the measurement report of the MRN, the source DeNB determines that there is no X2 interface between the source DeNB and the target DeNB, or needs to reselect an MME for the MRN, and then needs to perform an S1 handover for the source DeNB, and the source DeNB selects one for the MRN according to the measurement report. Target cell.
  • the source DeNB sends an S1 interface handover request message to the source MME of the MRN.
  • Step 903 The source MME determines, according to the base station identifier or the target TAI of the target DeNB in the received handover request message, whether to select a new MME, and if necessary, selects the target MME according to the two parameters, and sends a forwarding relocation to the source MME.
  • Request message which carries the source base station to Information such as the transparent transmission container of the target base station, the target base station identifier, the target location area identifier, and the context information of the MRN.
  • Step 904 The target MME of the MRN sends an S1 interface handover request message to the target DeNB.
  • the handover request acknowledgement message further includes the addresses of the S-GW and the P-GW built in the target DeNB to assist the MME of the MRN to relocate the gateway of the MRN to the gateway in the target DeNB.
  • the handover request acknowledgement message does not need to include the addresses of the S-GW and the P-GW.
  • Step 906 is the same as step 808 and will not be repeated here.
  • Steps 907-915 are the same as steps 608-616 and will not be repeated here.
  • step 908 and step 909 are internal interface messages in the target DeNB. And, if it is not necessary to select a new MME, step 903 and step 911 are skipped, and the behaviors of both the source MME and the target MME are the same MME behavior.
  • steps 906-910 may also be performed after step 915.
  • the address information of the S-GW and the P-GW built in the target DeNB may not be carried in the step 905, and the address information of the S-GW and the P-GW may be in step 915.
  • the handover notification message carries, and accordingly, steps 906-910 are performed after step 915.
  • Steps 906-910 may also be performed after step 903 and before step 904.
  • the target MME selects a new S-GW and P-GW located in the core network for the MRN.
  • the embodiment further provides a mobility management entity, including: a location determining unit 100 and a first determining unit 101, where:
  • the location determining unit 100 is configured to: determine, in a process of the MRN switching the DeNB, a current location of the MRN;
  • the first determining unit 101 is configured to: determine, according to the current location of the MRN, whether execution is required to be Relocation of the gateway of the MRN service.
  • the first judging unit 101 is for relocating the gateway of the MRN service according to the current location of the MRN in the following manner:
  • the location determining unit 100 is configured to determine a current location of the MRN by: obtaining a current location of the MRN according to a tracking area code and/or a cell identifier of a cell under the DeNB where the MRN is currently located;
  • the location determining unit 100 is further configured to: obtain a location of a gateway serving the MRN according to the saved location related information of the gateway serving the MRN;
  • the first determining unit 101 is configured to determine, according to the distance between the MRN and the gateway serving the MRN, whether to perform relocation of the gateway serving the MRN: according to the current location of the MRN and the location of the gateway serving the MRN Determining the distance between the MRN and the gateway serving the MRN, and determining whether it is necessary to perform relocation of the gateway serving the MRN.
  • the mobility management entity further includes: a second determining unit 102, wherein:
  • the second determining unit 102 is configured to: after the first determining unit determines that the relocation of the gateway serving the MRN needs to be performed, determine whether the target DeNB of the MRN satisfies the gateway relocation under the system architecture of the DeNB built in the gateway serving the MRN The condition, if satisfied, determines the relocation of the gateway performing the MRN service; if not, it determines that the relocation of the gateway serving the MRN is not performed.
  • the second determining unit 102 is configured to determine whether the target DeNB of the MRN satisfies the gateway relocation condition in the following manner:
  • the second determining unit 102 is configured to determine whether the target DeNB of the MRN satisfies a gateway relocation condition in the following manner: Determining whether the PLMN in which the target DeNB is located includes the PLMN in which the MRN is located; or determining whether the PLMN in which the target DeNB is located includes the PLMN in which the DeNB where the gateway currently serving the MRN is located.
  • another mobility management entity provided by this embodiment includes: a receiving unit
  • the receiving unit 110 is configured to: receive, during the MRN handover, the relocation determination indication information;
  • the relocation determining unit 111 is configured to: determine, according to the relocation determining indication information, whether relocation of the gateway serving the MRN needs to be performed;
  • the relocation determination indication information is that the source DeNB or the target DeNB of the MRN determines whether it needs to perform relocation of the gateway serving the MRN according to the relocation determination assistance information, and then sends the information to the receiving unit 110.
  • the target DeNB of the MRN is configured according to the configuration information. It is determined whether it is necessary to perform relocation of the gateway serving the MRN and then send to the receiving 110.
  • the relocation judging unit 111 is for relocating the gateway that needs to perform the service for the MRN according to the relocation judgment indication information in the following manner:
  • the relocation determination indication information is explicit indication information
  • the relocation determination indication information indicates that relocation needs to be performed, it is determined that relocation of the gateway serving the MRN needs to be performed; and the relocation determination indication information is not received.
  • the relocation judgment indication information indicates that the relocation is not required to be performed, determining that the relocation of the gateway serving the MRN does not need to be performed; or
  • the relocation judgment indication information is implicit indication information
  • the relocation judgment indication information is used as an address implied indication of the gateway of the MRN service
  • when receiving the address it is determined that the gateway serving as the MRN needs to be executed. Relocation; when no address is received, it is judged that it is not necessary to perform relocation of the gateway serving the MRN.
  • the embodiment further provides a host base station, including: a determining unit 120 and a sending unit 121, where:
  • the determining unit 120 is configured to: determine, according to the relocation, in the process of the MRN switching the DeNB The information is used to determine whether the relocation of the gateway serving the MRN needs to be performed; or, according to the configuration information, whether the relocation of the gateway serving the MRN needs to be performed;
  • the sending unit 121 is configured to: send relocation determination indication information to the MME of the MRN.
  • the relocation determining auxiliary information includes: counting information for counting the number of times the MRN switches after the last occurrence of the gateway relocation; or
  • the indication information of the source cell or the target cell when the MRN is relocated by the gateway is marked;
  • the MRN records the historical access cell record information after the last occurrence of the gateway relocation.
  • the judging unit 120 is for relocating the gateway that serves the MRN service according to the relocation judging assistance information in the following manner:
  • Determining, according to the relocation determining assistance information, the number of cells visited by the MRN after the last relocation of the MRN serviced gateway; and determining whether the number of cells visited by the MRN after the last relocation of the MRN serviced gateway reaches the visited cell The number of thresholds, if reached, determines the need to perform a relocation of the gateway serving the MRN.
  • the transmitting unit 121 is configured to send relocation judgment indication information to the MME of the MRN in the following manner:
  • the determining unit 120 determines that the relocation of the gateway serving the MRN needs to be performed, the address information of the gateway served by the MRN is sent to the MME as the relocation judgment indication information. After receiving the address information of the gateway serving the MRN, the MME determines that the relocation of the gateway serving the MRN needs to be performed.
  • the host base station further includes: an information maintenance unit 122, where:
  • the information maintenance unit 122 is configured to: after performing the relocation of the gateway serving the MRN in the current handover process, when the relocation determination auxiliary information includes the counting information, clear the counting information, where the counting information is generated every time in the MRN When the handover process of the relocation of the gateway serving the MRN does not need to be performed at one time, the source DeNB or the target DeNB of the MRN adds 1 to the count information;
  • the relocation judgment auxiliary information includes the indication information
  • the indication information is added to the source cell or the target cell corresponding to the current handover in the historical visited cell list of the MRN;
  • the relocation determining auxiliary information includes the identification information, setting the identification information of the source cell or the target cell corresponding to the current handover as the relocation determining auxiliary information;
  • the relocation judgment auxiliary information includes the history access cell record information of the MRN after the last occurrence of the gateway relocation, and clears the historical access cell record information.
  • the problem of determining whether to perform gateway relocation in the MRN handover process can be solved, so that route optimization is smoothly performed, thereby shortening delay of UE data and signaling.

Landscapes

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

Abstract

一种网关重定位的方法、MME及DeNB。所述方法包括:在MRN切换DeNB的过程中,所述MRN的MME根据所述MRN的当前位置判断是否需要执行为所述MRN服务的网关的重定位。

Description

一种网关重定位的方法、 移动管理实体及宿主基站
技术领域
本发明涉及无线通信技术领域, 尤其涉及一种网关重定位的方法、 移动 管理实体(Mobility Management Entity, MME )及宿主基站。
背景技术
在第三代合作伙伴项目 ( the 3rd Generation Partnership Project, 3 GPP ) 标准组织推出的高级长期演进 ( Long Term Evolution-Advanced LTE-A )标准 中无线中继( Wireless Relay )技术中, 中继节点( Relay Node , 简称 RN )对 接入其小区的用户设备 ( User Equipment , UE ) 提供与普通演进型基站 ( evolved Node B, eNB )类似的功能和服务, 又通过无线接口以类似于普通 UE的方式接入一个服务于它的 eNB(称为宿主基站( Donor eNB , DeNB ) )。 随着高速铁路大规模地建设和投入运行, 在列车上通信的需求不断增大。 但 由于高速移动的列车受到多普勒频移、 小区频繁切换和高铁车厢穿透损耗大 等影响, 现有网络基站的覆盖很难满足高铁的通信质量需求。 因此业界提出 在高铁上部署中继节点,这种中继节点通常称为移动中继节点(Mobile Relay Node, MRN )。 如图 1和图 2所示, 通过移动中继技术, 可以使得高铁列车 中的用户 ( UE1和 UE2 )与相对静止的 MRN进行通信, 而 MRN在随着高 铁移动过程中可在不同的 DeNB之间进行切换, 从而避免了高铁车厢中大量 用户的同时切换, 保证了 UE和 MRN之间的通信质量, 此外通过增强 MRN 与 DeNB之间的骨干连接, 能够较好地解决高铁存在的一系列问题。
移动中继 ( mobile relay ) 系统可以釆用图 1中所示架构 (即, 与已标准 化的 RIO fix relay相同的架构, 通常称为架构 2 ) , 在该架构中, DeNB中内 置的为 MRN服务的服务网关( Service Gateway, S-GW ) 、 分组数据网络网 关(Packet Data Network Gateway, P-GW )和中继网关 ( relay Gateway, relay GW ) , 其中 DeNB中的 relay GW为 UE的用户面数据和控制面信令提供 SI 和 /或 X2代理功能。 在该架构中, MRN的 S-GW、 P-GW和 relay GW (可统 称为 GW )位于其附着时接入的初始 DeNB ( initial DeNB ) 中, 当高铁上的 MRN移动至离 initial DeNB较远时, UE的数据到达 MRN的 P-GW后 , 将 经由多个 DeNB转发路由才能到达为 MRN服务的 DeNB , 即, 存在路由路 径太长的问题,进而导致 UE数据的延迟增加。 因此,可考虑路由优化方案, 当 MRN移动至离 initial DeNB较远时,在 MRN的切换过程中将 MRN的 GW 更换成为 MRN服务的 DeNB中内置的网关。 如图 2所示, MRN切换前, 其 GW位于 DeNBl上, 而 MRN由 DeNB3的基站功能提供服务时, UE的数据 首先到达 DeNBl的 GW功能, 再经过 DeNB2路由至 DeNB3的基站功能, MRN可在切换过程中将其 GW重定位至 DeNB4 中内置的 GW, 从而使得 UE的数据可直接到达 DeNB4中的 GW, 缩短路径长度, 减少数据延迟。 由 于并不是每次 MRN的切换都需要执行网关的重定位, 而只有在路由路径较 长时才需要。而且在架构 2下,由于 DeNB的 S1和 X2代理功能,目标 DeNB 需要满足一定的条件,才能将 MRN的网关重定位至目标 DeNB内置的 S-GW 和 P-GW。 总之, 需解决如何判断本次 MRN的切换过程中是否执行网关重 定位的问题。
mobile relay系统还可以釆用图 3中所示架构 (通常称为架构 1 ) , 该架 构并没有 relay GW功能实体,为 MRN提供服务的 S-GW和 P-GW位于核心 网, DeNB将 UE的用户面数据和控制面信令封装成用户面的通用分组无线 业务隧道协议 ( General Packet Radio Service ( GPRS ) Tunneling Protocol for Userplane, GTP-U )数据包通过移动中继的承载发送给 MRN 的 S-GW和 P-GW,再经过互联网协议( Internet Protocol, IP )路由至 UE的 MME或 S-GW。 随着列车的高速移动,当位于核心网的为 MRN服务的 GW离 MRN较远时, 同样存在上述路由路径过长问题, 也可考虑在 MRN 的切换过程中将 MRN 的 GW重定位至当前为 MRN服务的 DeNB附近的 S-GW和 P-GW。 同架构 2 中所述, 也需解决如何判断本次 MRN的切换过程中是否执行网关重定位 的问题。
发明内容
本发明实施例提供一种网关重定位的方法、 移动管理实体及宿主基站, 在对移动中继节点切换宿主基站时能够确定是否为移动中继节点重定位服务 的网关。
本发明实施例提供一种网关重定位的方法, 包括:
在移动中继节点 MRN切换宿主基站 DeNB的过程中, 所述 MRN的移 动管理实体 MME根据所述 MRN的当前位置判断是否需要执行为所述 MRN 服务的网关的重定位。
可选地,所述 MRN的 MME根据所述 MRN的当前位置判断是否需要执 行为所述 MRN服务的网关的重定位, 包括:
所述 MME根据所述 MRN与为所述 MRN服务的网关之间的距离,判断 是否需要执行为所述 MRN服务的网关的重定位,在所述 MRN与为所述 MRN 服务的网关之间的距离大于网关重定位距离阔值时, 判断需要执行为所述 MRN服务的网关的重定位。
可选地,所述 MME根据所述 MRN与为所述 MRN服务的网关之间的距 离, 判断是否需要执行为所述 MRN服务的网关的重定位, 包括:
所述 MME根据所述 MRN当前所在的 DeNB下的小区的跟踪区域码和 / 或小区标识, 得到所述 MRN的当前位置;
所述 MME根据所保存的为所述 MRN服务的网关的位置相关信息, 得 到为所述 MRN服务的网关的位置; 以及
所述 MME根据所述 MRN的当前位置和为所述 MRN服务的网关的位置, 确定所述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要执行 为所述 MRN服务的网关的重定位。
可选地, 在为所述 MRN月良务的网关内置于 DeNB的系统架构下, 为所 述 MRN服务的网关的位置相关信息是所述 MRN接入为所述 MRN服务的网 关所在的 DeNB 时, 在为所述 MRN服务的网关所在的 DeNB 下, 为所述 MRN服务的小区的跟踪区域码和 /或小区标识。
可选地, 所述方法还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 则确 定执行为所述 MRN服务的网关的重定位。
可选地, 所述方法还包括: 所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 在为 所述 MRN服务的网关内置在 DeNB的系统架构下,所述 MME判断所述 MRN 的目标 DeNB是否满足网关重定位条件, 如果满足, 则所述 MME确定执行 为所述 MRN服务的网关的重定位; 如果不满足, 则所述 MME确定不执行 为所述 MRN服务的网关的重定位;
在为所述 MRN服务的网关位于核心网的架构下, 所述 MME在判断需 要执行为所述 MRN服务的网关的重定位后 , 则确定执行为所述 MRN服务 的网关的重定位。
可选地, 所述方法还包括:
所述 MME在确定执行为所述 MRN服务的网关的重定位后 , 执行为所 述 MRN服务的网关的重定位, 其中, 所述重定位包括为所述 MRN服务的 分组数据网络网关 P-GW和 /或服务网关 S-GW的重定位; 以及将所述 MRN 的分组数据网络( Packet Data Nework , PDN )连接转移至所述重定位后的网 关。
可选地, 所述 MME判断所述 MRN的目标 DeNB是否满足网关重定位 条件, 包括:
所述 MME判断所述目标 DeNB支持的跟踪区域是否包含所述 MRN支 持的跟踪区域; 或者,
所述 MME判断所述目标 DeNB 支持的跟踪区域是否包含当前为所述 MRN服务的网关所在的 DeNB支持的跟踪区域。
可选地, 所述 MME判断所述 MRN的目标 DeNB是否满足网关重定位 条件, 包括:
所述 MME判断所述目标 DeNB所在的公共陆地移动网络( Public Land Mobile Network, PLMN )是否包含所述 MRN所在的 PLMN; 或者 ,
所述 MME判断所述目标 DeNB所在的 PLMN是否包含当前为所述 MRN 服务的网关所在的 DeNB所在的 PLMN。
本发明实施例还提供一种网关重定位的方法, 包括:
在移动中继节点 MRN切换宿主基站 DeNB的过程中, 所述 MRN的移 动管理实体 MME接收重定位判断指示信息, 根据所述重定位判断指示信息 判断是否需要执行为所述 MRN服务的网关的重定位;
其中, 所述重定位判断指示信息是所述 MRN的源 DeNB或目标 DeNB 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关的重定 位后发送给所述 MME; 或者,是所述 MRN的目标 DeNB根据配置信息判断 是否需要执行为所述 MRN服务的网关的重定位后发送给所述 MME。
可选地, 所述重定位判断辅助信息包括: 用于统计所述 MRN在上一次 发生网关重定位之后发生切换的次数的计数信息; 或者,
在所述 MRN的历史访问小区列表中用于标记所述 MRN发生网关重定 位时的源小区或目标小区的指示信息; 或者,
所述 MRN发生网关重定位时的源小区或目标小区的标识信息; 或者, 所述 MRN在上一次发生网关重定位之后的历史访问小区记录信息。 可选地, 所述 MRN的源 DeNB或目标 DeNB 4艮据重定位判断辅助信息 判断是否需要执行为所述 MRN服务的网关的重定位, 包括:
所述源 DeNB 或目标 DeNB 居所述重定位判断辅助信息确定所述
MRN在上一次为 MRN服务的网关重定位之后访问的小区的个数; 以及 所述源 DeNB或目标 DeNB判断所述 MRN在上一次为 MRN服务的网 关重定位之后访问的小区的个数是否达到访问小区数量阔值, 如果达到, 则 判断需要执行所述为 MRN服务的网关的重定位。
可选地, 所述方法还包括:
在为所述 MRN服务的网关内置于 DeNB 的系统架构下, 如果所述源 DeNB或目标 DeNB判断需要执行为所述 MRN服务的网关的重定位, 则所 述目标 DeNB将内置在目标 DeNB的为 MRN服务的网关的地址信息作为所 述重定位判断指示信息发送给所述 MME;所述 MME在接收到为 MRN服务 的网关的地址信息后, 确定需要执行为所述 MRN服务的网关的重定位。
可选地, 所述方法还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 则确 定执行为所述 MRN服务的网关的重定位。 可选地, 所述方法还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 在为 所述 MRN服务的网关内置在所述 MRN的目标 DeNB中时 ,所述 MME判断 所述 MRN的目标 DeNB是否满足网关重定位条件,如果满足,则所述 MME 确定执行为所述 MRN服务的网关的重定位; 如果不满足, 则所述 MME确 定不执行为所述 MRN服务的网关的重定位; 以及
在为所述 MRN服务的网关位于核心网的架构下, 所述 MME在判断需 要执行为所述 MRN服务的网关的重定位后 , 则确定执行为所述 MRN服务 的网关的重定位。
可选地, 所述方法还包括:
所述 MME在确定执行为所述 MRN服务的网关的重定位后 , 执行为所 述 MRN服务的网关的重定位, 其中, 所述重定位至少包括为所述 MRN服 务的分组数据网络网关 P-GW和 /或服务网关 S-GW的重定位; 以及将所述 MRN的分组数据网络 PDN连接转移至所述重定位后的网关。
可选地, 所述重定位判断辅助信息由保存有所述 MRN的上下文信息的
DeNB保存和维护; 当所述 MRN发生切换时, 所述重定位判断辅助信息由 所述源 DeNB发送给目标 DeNB。
可选地, 所述方法还包括:
所述源 DeNB或目标 DeNB在本次切换过程中执行为所述 MRN服务的 网关的重定位后, 在所述重定位判断辅助信息包含所述计数信息时, 将所述 计数信息清零, 其中, 所述计数信息是在 MRN每发生一次不需要执行为所 述 MRN服务的网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB 对所述计数信息加 1得到;
在所述重定位判断辅助信息包含所述指示信息时, 所述源 DeNB或目标 DeNB在所述 MRN的历史访问小区列表中的本次切换对应的源小区或目标 小区的项目中添加指示信息;
在所述重定位判断辅助信息包含所述标识信息时, 所述源 DeNB或目标 DeNB将本次切换对应的源小区或目标小区的标识信息设置为所述重定位判 断辅助信息; 以及
在所述重定位判断辅助信息包含所述 MRN在上一次发生网关重定位之 后的历史访问小区记录信息时, 所述源 DeNB或目标 DeNB将所述历史访问 小区记录信息清空。
可选地, 所述 MME根据重定位判断指示信息判断是否需要执行为所述
MRN服务的网关的重定位, 包括:
在所述重定位判断指示信息是显式的指示信息的情况下, 在所述重定位 判断指示信息指示需要执行重定位时,所述 MME判断需要执行为所述 MRN 服务的网关的重定位; 在所述 MMME没有接收到所述重定位判断指示信息 或者所述重定位判断指示信息指示不需要执行重定位时, 所述 MME判断不 需要执行为所述 MRN服务的网关的重定位; 或者,
在所述重定位判断指示信息是隐式的指示信息的情况下, 且所述重定位 判断指示信息釆用为 MRN服务的网关的地址隐含指示时, 在所述 MME接 收到所述地址时, 所述 MME判断需要执行为所述 MRN服务的网关的重定 位; 在所述 MME未接收到所述地址时, 则所述 MME判断不需要执行为所 述 MRN服务的网关的重定位。
本发明实施例还提供一种移动管理实体, 包括: 位置确定单元和第一判 断单元, 其中:
所述位置确定单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB 的过程中, 确定所述 MRN的当前位置; 以及
所述第一判断单元设置成: 根据所述 MRN的当前位置判断是否需要执 行为所述 MRN服务的网关的重定位。
可选地, 所述第一判断单元是设置成以如下方式根据所述 MRN的当前 位置判断是否需要执行为所述 MRN服务的网关的重定位:
根据所述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要 执行为所述 MRN服务的网关的重定位 ,在所述 MRN与为所述 MRN服务的 网关之间的距离大于网关重定位距离阔值时, 判断需要执行为所述 MRN服 务的网关的重定位。 可选地, 所述位置确定单元元是设置成以如下方式确定所述 MRN的当 前位置: 根据所述 MRN的当前所在的 DeNB下的小区的跟踪区域码和 /或小 区标识, 得到所述 MRN的当前位置;
所述位置确定单元还设置成: 根据所保存的为所述 MRN服务的网关的 位置相关信息, 得到为所述 MRN服务的网关的位置; 以及
所述第一判断单元是设置成以如下方式根据所述 MRN与为所述 MRN 服务的网关之间的距离, 判断是否需要执行为所述 MRN服务的网关的重定 位: 根据所述 MRN的当前位置和为所述 MRN服务的网关的位置, 确定所 述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要执行为所述 MRN服务的网关的重定位。
可选地, 所述移动管理实体还包括: 第二判断单元, 其中:
所述第二判断单元设置成: 在所述第一判断单元判断需要执行为所述 MRN服务的网关的重定位后,在为所述 MRN服务的网关内置在 DeNB的系 统架构下, 判断所述 MRN的目标 DeNB是否满足网关重定位条件, 如果满 足, 则确定执行为所述 MRN服务的网关的重定位; 如果不满足, 则确定不 执行为所述 MRN服务的网关的重定位。
可选地, 所述第二判断单元是设置成以如下方式判断所述 MRN的目标 DeNB是否满足网关重定位条件:
判断所述目标 DeNB支持的跟踪区域是否包含所述 MRN支持的跟踪区 域; 或者, 判断所述目标 DeNB支持的跟踪区域是否包含当前为所述 MRN 服务的网关所在的 DeNB支持的跟踪区域。
可选地, 所述第二判断单元是设置成以如下方式判断所述 MRN的目标 DeNB是否满足网关重定位条件:
判断所述目标 DeNB 所在的公共陆地移动网络 PLMN是否包含所述 MRN所在的 PLMN; 或者 , 判断所述目标 DeNB所在的 PLMN是否包含当 前为所述 MRN服务的网关所在的 DeNB所在的 PLMN。
本发明实施例还提供一种移动管理实体, 包括: 接收单元和重定位判断 单元, 其中: 所述接收单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB的过 程中, 接收重定位判断指示信息; 以及
所述重定位判断单元设置成: 根据所述重定位判断指示信息判断是否需 要执行为所述 MRN服务的网关的重定位;
其中, 所述重定位判断指示信息是所述 MRN的源 DeNB或目标 DeNB 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关的重定 位后发送给所述接收单元; 或者, 是所述 MRN的目标 DeNB根据配置信息 判断是否需要执行为所述 MRN服务的网关的重定位后发送给所述接收单元。
可选地, 所述重定位判断单元是设置成以如下方式 4艮据所述重定位判断 指示信息判断是否需要执行为所述 MRN服务的网关的重定位:
在所述重定位判断指示信息是显式的指示信息的情况下, 在所述重定位 判断指示信息指示需要执行重定位时, 判断需要执行为所述 MRN服务的网 关的重定位; 在没有接收到所述重定位判断指示信息或者所述重定位判断指 示信息指示不需要执行重定位时, 判断不需要执行为所述 MRN服务的网关 的重定位; 或者,
在所述重定位判断指示信息是隐式的指示信息的情况下, 且所述重定位 判断指示信息釆用为 MRN服务的网关的地址隐含指示时, 在接收到所述地 址时, 判断需要执行为所述 MRN服务的网关的重定位; 在未接收到所述地 址时, 则判断不需要执行为所述 MRN服务的网关的重定位。
本发明实施例还提供一种宿主基站,包括:判断单元和发送单元,其中: 所述判断单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB的过 程中, 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关 的重定位; 或者, 根据配置信息判断是否需要执行为所述 MRN服务的网关 的重定位; 以及
所述发送单元设置成: 向所述 MRN的移动管理实体 MME发送重定位 判断指示信息。
可选地, 所述重定位判断辅助信息包括: 用于统计所述 MRN在上一次 发生网关重定位之后发生切换的次数的计数信息; 或者, 在所述 MRN的历史访问小区列表中用于标记所述 MRN发生网关重定 位时的源小区或目标小区的指示信息; 或者,
所述 MRN发生网关重定位时的源小区或目标小区的标识信息; 或者, 所述 MRN在上一次发生网关重定位之后的历史访问小区记录信息。
可选地, 所述判断单元是设置成以如下方式 4艮据重定位判断辅助信息判 断是否需要执行为所述 MRN服务的网关的重定位:
根据所述重定位判断辅助信息确定所述 MRN在上一次为 MRN服务的 网关重定位之后访问的小区的个数; 以及判断所述 MRN在上一次为 MRN 服务的网关重定位之后访问的小区的个数是否达到访问小区数量阔值, 如果 达到, 则判断需要执行所述为 MRN服务的网关的重定位。
可选地, 所述发送单元是设置成以如下方式向所述 MRN的 MME发送 重定位判断指示信息:
在为所述 MRN服务的网关内置于 DeNB的系统架构下, 如果所述判断 单元判断需要执行为所述 MRN服务的网关的重定位, 将为 MRN服务的网 关的地址信息作为所述重定位判断指示信息发送给所述 MME。
可选地, 所述宿主基站还包括信息维护单元, 其中:
所述信息维护单元设置成: 在本次切换过程中执行为所述 MRN服务的 网关的重定位后, 在所述重定位判断辅助信息包含所述计数信息时, 将所述 计数信息清零, 其中, 所述计数信息是在 MRN每发生一次不需要执行为所 述 MRN服务的网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB 对所述计数信息加 1得到;
在所述重定位判断辅助信息包含所述指示信息时, 在所述 MRN的历史 访问小区列表中的本次切换对应的源小区或目标小区的项目中添加指示信息; 在所述重定位判断辅助信息包含所述标识信息时, 将本次切换对应的源 小区或目标小区的标识信息设置为所述重定位判断辅助信息; 以及
在所述重定位判断辅助信息包含所述 MRN在上一次发生网关重定位之 后的历史访问小区记录信息时, 将所述历史访问小区记录信息清空。
综上所述, 本发明实施例中, 能够解决 MRN切换过程中判断是否执行 网关重定位的问题, 使得路由优化顺利执行, 进而缩短 UE数据和信令的延 迟。 附图概述
图 1是高铁场景下移动中继系统的第一种架构的示意图;
图 2是在移动中继系统第一种架构下的路由优化的示意图;
图 3是高铁场景下移动中继系统的第二种架构的示意图;
图 4是根据本发明实施例一的网关重定位方法的流程示意图;
图 5是根据本发明实施例二的网关重定位方法的流程示意图;
图 6是根据本发明实施例三的网关重定位方法的流程示意图;
图 7是根据本发明实施例四的网关重定位方法的流程示意图;
图 8是根据本发明实施例五的网关重定位方法的流程示意图;
图 9是根据本发明实施例六的网关重定位方法的流程示意图;
图 10是本发明实施例的移动管理实体的架构图;
图 11是本发明实施例的另一种移动管理实体的架构图; 以及
图 12是本发明实施例的宿主基站的架构图。 本发明的较佳实施方式
本实施方式中, 在移动中继节点切换宿主基站的过程中, 为移动中继节 点服务的移动管理实体根据移动中继节点的当前位置判断是否需要执行为移 动中继节点服务的网关的重定位。
移动管理实体根据移动中继节点的当前位置判断是否需要执行为移动中 继节点服务的网关的重定位, 包括:
移动管理实体根据移动中继节点与为移动中继节点服务的网关之间的距 离, 判断是否需要执行为移动中继节点服务的网关的重定位, 当移动中继节 点与当前为移动中继节点服务的网关之间的距离大于网关重定位距离阔值时 , 移动管理实体判断需要执行为移动中继节点服务的网关的重定位; 当移动中 继节点与当前为移动中继节点服务的网关之间的距离不大于网关重定位距离 阔值时, 则移动管理实体判断不需要执行网关的重定位。
移动管理实体根据移动中继节点与为移动中继节点服务的网关之间的距 离, 判断是否需要执行为移动中继节点服务的网关的重定位, 包括:
移动管理实体保存当前为移动中继节点服务的网关的位置相关信息, 其 中, 为移动中继节点服务的网关的位置相关信息指网关所在的宿主基站下小 区的跟踪区域码和 /或小区标识; 小区指移动中继节点接入宿主基站时在宿主 基站下为移动中继节点服务的小区;
移动管理实体根据为移动中继节点服务的网关的位置相关信息得到为移 动中继节点服务的网关的位置;
移动管理实体根据移动中继节点所在宿主基站下的小区的跟踪区域码和 /或小区标识得到所述移动中继节点的当前位置; 以及
移动管理实体根据移动中继节点的当前位置和为移动中继节点服务的网 关的位置, 确定移动中继节点与为移动中继节点服务的网关之间的距离, 判 断是否需要执行为移动中继节点服务的网关的重定位。
本实施方式中, 在移动中继节点切换宿主基站的过程中, 移动中继节点 的移动管理实体接收重定位判断指示信息, 根据重定位判断指示信息判断是 否需要执行为移动中继节点服务的网关的重定位;
其中, 重定位判断指示信息是移动中继节点的源宿主基站或目标宿主基 站根据重定位判断辅助信息判断是否需要执行为移动中继节点服务的网关的 重定位后发送给移动管理实体; 或者, 是移动中继节点的目标宿主基站根据 配置信息判断是否需要执行为移动中继节点服务的网关的重定位后发送给移 动管理实体。
重定位判断指示信息用于指示是否需要执行网关的重定位。
重定位判断辅助信息, 包括:
用于统计移动中继节点在上一次发生网关重定位之后发生切换的次数的 计数信息; 其中, 在每次移动中继节点发生切换后, 均需要对该计数信息进 行累计, 并在源宿主基站与目标宿主基站之间传递;
或者, 在移动中继节点的历史访问小区列表中用于标记移动中继节点发 生网关重定位时的源小区或目标小区的指示信息; 其中, 指示信息可以是一 个比特, 标记在历史访问小区列表中相应源小区或目标小区的条目中。
或者,移动中继节点发生网关重定位时的源小区或目标小区的标识信息, 其中, 标识信息至少包括小区标识;
或者, 移动中继节点在上一次发生网关重定位之后的历史访问小区记录 信息。
重定位判断辅助信息由保存有移动中继节点的上下文信息的宿主基站保 存和维护。 当移动中继节点发生切换时, 源宿主基站将重定位判断辅助信息 直接或通过其他网元发送给目标宿主基站。
保存有移动中继节点的上下文信息的宿主基站保存和维护重定位判断辅 助信息, 包括: 若源宿主基站或目标宿主基站判断需要执行网关的重定位: 在重定位判断辅助信息为计数信息情况下, 源宿主基站或目标宿主基站 将计数信息清零; 其中, 计数信息是在 MRN每发生一次不需要执行为所述 MRN服务的网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB对 所述计数信息加 1得到;
在重定位判断辅助信息为指示信息情况下, 源宿主基站或目标宿主基站 在移动中继节点的历史访问小区列表中的本次切换对应的源小区或目标小区 的项目中添加指示信息;
在重定位判断辅助信息为小区标识信息情况下, 源宿主基站或目标宿主 基站将本次切换对应的源小区或目标小区的标识信息设置为重定位判断辅助 信息; 以及
在重定位判断辅助信息为历史访问小区记录信息情况下, 源宿主基站或 目标宿主基站将历史访问小区记录信息清空。 在移动中继节点发生切换后, 均需要对历史访问小区记录信息进行更新。
上述配置信息为指示是否需要执行为 MRN服务的网关的重定位的指示 信息; 例如, 网络管理系统的操作维护管理( ( Operation Administration and Maintenance, OAM )为部署在高铁沿线的车站内的 DeNB 配置指示需要执 行网关重定位的配置信息。
移动中继节点的源宿主基站或目标宿主基站根据重定位判断辅助信息判 断是否需要执行为所述移动中继节点服务的网关的重定位, 包括:
源宿主基站或目标宿主基站根据重定位判断辅助信息确定移动中继节点 在上一次网关重定位之后访问的小区个数; 以及
源宿主基站或目标宿主基站判断移动中继节点在上一次为移动中继节点 服务的网关重定位之后访问的小区的个数是否达到访问小区数量阔值, 如果 达到, 则判断需要执行为 MRN服务的网关的重定位。
访问小区数量阔值可由预配置方式获得, 也可从网络管理系统处获得。 源宿主基站或目标宿主基站根据重定位判断辅助信息确定移动中继节点 在上一次网关重定位之后访问的小区个数, 包括:
( 1 )在重定位判断辅助信息为计数信息时,可以直接根据数值得到重定 位网关后, 实际访问的小区的数量;
( 2 )在重定位辅助信息为指示信息时,计算移动中继节点的历史访问小 区列表中在指示信息所在项目之后 MRN访问的小区的个数。 在指示信息对 应源小区时, 还需要对计算得到的数值减 1 , 得到重定位网关后, 实际访问 的小区的数量;
( 3 )在重定位辅助信息为标识信息时,从移动中继节点的历史访问小区 列表中查找标识信息, 计算列表中标识信息所在项目之后 MRN访问的小区 的个数,在标识信息为源小区的标识信息时,还需要对计算得到的数值减 1 , 得到重定位网关后, 实际访问的小区的数量;
( 4 )在重定位辅助信息为移动中继节点在上一次发生网关重定位之后移 动中继节点的历史访问小区列表中的历史访问小区记录信息时, 直接计算历 史访问小区记录信息中包含的记录的条数, 得到重定位网关后, 实际访问的 小区的数量。
上述( 2 )和( 3 )中的历史访问小区列表可以是一个历史访问小区列表, ( 4 )中的历史访问小区列表可以是与(2 )和(3 )中的历史访问小区列表不 同的历史访问小区列表, (2 )和(3 ) 中的历史访问小区列表可以保存多次 网关重定位前后访问的小区; (4 )中的历史访问小区列表保存上一次网关重 定位之后访问的小区。
源宿主基站或目标宿主基站直接或者通过其他网元发送重定位判断指示 信息给移动管理实体。
重定位判断指示信息是显式的指示信息, 或者是通过特定信元隐含指示 的隐式信息。 特定信元包括宿主基站中内置的网关的地址信息。
移动管理实体根据重定位判断指示信息判断是否需要执行为移动中继节 点服务的网关的重定位, 包括:
重定位判断指示信息是显式的指示信息情况下, 若重定位判断指示信息 指示需要执行网关的重定位, 则移动管理实体判断需要执行网关的重定位; 若移动管理实体没有接收到重定位判断指示信息或者重定位判断指示信息指 示不需要执行网关的重定位, 移动管理实体判断不需要执行网关的重定位; 重定位判断指示信息是隐式信息, 且用于指示隐式信息的特定信元是网 关的地址信息情况下, 若移动管理实体接收到网关的地址信息, 则判断需要 执行网关的重定位; 若移动管理实体未接收到网关的地址信息, 则判断不需 要执行网关的重定位。
网关的重定位包括为移动中继节点服务的分组数据网络网关和 /或服务 网关的重定位。 移动管理实体执行为所述 MRN服务的网关的重定位后, 将 移动中继节点的 PDN连接转移至重定位后的网关。网关的重定位还可以包括 中继网关的重定位。
移动管理实体在判断需要执行为移动中继节点服务的网关的重定位后, 在为移动中继节点服务的网关内置在移动中继节点的目标宿主基站中时, 移 动管理实体判断移动中继节点的目标宿主基站是否满足网关重定位条件, 如 果满足, 则移动管理实体确定执行为移动中继节点服务的网关的重定位; 如 果不满足,则移动管理实体确定不执行为移动中继节点服务的网关的重定位; 在为移动中继节点服务的网关位于核心网的架构下, MME在判断需要 执行为 MRN服务的网关的重定位后, 则确定执行为移动中继节点的网关的 重定位。
此外, 移动管理实体在判断需要执行为移动中继节点服务的网关的重定 位后, 则确定执行为移动中继节点服务的网关的重定位。
移动管理实体判断移动中继节点的目标宿主基站是否满足网关重定位条 件, 包括:
移动管理实体判断目标宿主基站支持的跟踪区域是否包含移动中继节点 支持的跟踪区域;
或者, 移动管理实体判断目标宿主基站支持的跟踪区域是否包含当前为 移动中继节点服务的网关所在的宿主基站支持的跟踪区域。
移动管理实体判断移动中继节点的目标宿主基站是否满足网关重定位条 件, 包括:
移动管理实体判断目标宿主基站所在的 PLMN是否包含移动中继节点 所在的 PLMN;
或者,移动管理实体判断目标宿主基站所在的 PLMN是否包含当前为移 动中继节点服务的网关所在的宿主基站所在的 PLMN。
下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互任意组合。
以下实施例对图 1和图 3所示的两种移动中继系统架构均适用。 在图 1 所示架构下, 为 MRN服务的 S-GW和 P-GW都内置于 DeNB, 在图 3所示 架构下, 为 MRN服务的 S-GW和 P-GW不内置于 DeNB , 而是作为独立网 元位于核心网。
实施例一
本实施例描述的是由目标 DeNB判断是否需要执行网关重定位并指示给 MME的方法下, 在 MRN的 X2切换过程中执行网关重定位的流程。 图 4描 述了该实施例所述流程, 所述流程为釆用图 1所示架构情况下的流程, 其中 MRN 的源 S-GW和源 P-GW可能内置于源 DeNB ,也可能不内置于源 DeNB , 而是内置于初始 DeNB。该实施例方法还适用于图 3所示移动中继系统架构, 则 MRN的源 S-GW和源 P-GW, 目标 S-GW和目标 P-GW都位于核心网。 本实施例所述流程包括如下步骤:
步骤 401 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 402, 源 DeNB接收到 MRN的测量报告后, 若判断源 DeNB与目 标 DeNB之间存在 X2接口,并且切换后 MRN不需要更换 MME ,则源 DeNB 为 MRN发起 X2切换。 源 DeNB根据测量 4艮告为 MRN选择一个目标小区。 源 DeNB发送 X2接口切换请求消息给目标 DeNB。 该切换请求消息中包含 重定位判断辅助信息, 用于将重定位判断辅助信息传递给目标 DeNB。 该重 定位判断辅助信息包括以下之一:
1 )用于统计 MRN在上一次发生网关重定位之后发生切换的次数的计数 信息;
2 )在 MRN的历史访问小区列表中用于标记 MRN发生网关重定位时的 源小区或目标小区的指示信息;
3 ) MRN发生网关重定位时的源小区或目标小区的标识信息, 其中, 小 区标识信息包括演进小区全局标识( Evolved Cell Global Identifier, ECGI );
4 ) MRN在上一次发生网关重定位之后的历史访问小区记录信息。
步骤 403 , 目标 DeNB根据切换请求消息中需建立的演进通用陆地无线 接入网络无线接入承载 ( Evolved Universal Terrestrial Radio Access Network ( EUTRAN ) -Radio Access Bearer, E-RAB )的月良务质量( Quality of Service, QoS )等信息为 MRN预留资源并创建上下文信息, 之后回复切换请求确认 消息。 该切换请求确认消息中包含透传的空口的切换命令消息。
步骤 404,源 DeNB发送空口消息无线资源控制( Radio Resource Control, RRC )连接重配置消息给 MRN, 该 RRC连接重配置消息中携带目标 DeNB 通过源 DeNB发送给 MRN的透传的切换命令消息,以指示 MRN执行切换。 步骤 405 , 源 DeNB发送序列号( Sequence Number, SN )状态转移消息 给目标 DeNB , 用于传递无线链路控制确认模式 ( Radio Link Control Acknowledged Mode, RLC AM )无线承载的上行和下行分组数据汇聚协议 ( Packet Data Convergence Protocol, PDCP ) SN接收和发送状态。
步骤 406, MRN接收到切换命令后, 从源 DeNB的小区去附着, 并与目 标小区同步, 并发起随机接入信道(Random Access Channel, RACH )过程 接入目标小区。 MRN与目标小区完成 RRC连接建立后, 发送 RRC连接重 配置完成消息给目标 DeNB。
步骤 407, 目标 DeNB根据重定位判断辅助信息判断是否需要执行网关 的重定位。
目标 DeNB首先根据该重定位判断辅助信息确定 MRN在上一次网关重 定位之后访问的小区个数, 然后再根据访问的小区个数判断是否需要执行网 关的重定位。 若 MRN在上一次网关重定位之后访问的小区个数超过预配置 或从 OAM获取的访问小区数量阔值, 则判断需要执行网关的重定位; 若未 超过预配置或从 OAM获取的访问小区数量阔值, 则判断不需要执行网关的 重定位。 另外, 目标 DeNB还需对重定位判断辅助信息进行保存和维护。 若 目标 DeNB判断需要执行网关的重定位, 并且,
1 ) 当重定位判断辅助信息为计数信息情况下, 目标 DeNB将计数信息 清零; 其中, 计数信息是在 MRN每发生一次不需要执行为所述 MRN服务 的网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB对所述计数 信息加 1得到;
2 ) 当重定位判断辅助信息为指示信息情况下, 目标 DeNB在移动中继 节点的历史访问小区列表中的本次切换对应的源小区或目标小区的项目中添 加指示信息;
3 ) 当重定位判断辅助信息为小区标识信息情况下, 目标 DeNB将本次 切换对应的源小区或目标小区的标识信息设置为重定位判断辅助信息; 以及
4 )当重定位判断辅助信息为历史访问小区记录信息情况下, 目标 DeNB 将历史访问小区记录信息清空。 在移动中继节点发生切换后, 均需要对历史 访问小区记录信息进行更新。
步骤 408 , 目标 DeNB接收 MRN发送的 RRC连接重配置完成消息后, 向 MRN的 MME发送路径转移请求消息, 以更新 MRN的 S1用户面及控制 面路径。 该路径转移请求消息中包含重定位判断指示信息, 用于指示是否需 执行网关的重定位。
该重定位判断指示信息可以是显式的指示信息, 在需要执行网关的重定 位情况下, 该路径转移请求消息还包含目标 DeNB中内置的 S-GW和 P-GW 的地址,以辅助 MRN的 MME将 MRN的网关重定位至目标 DeNB中的网关。
在釆用图 1所示移动中继系统架构下, 重定位判断指示信息也可以是通 过特定信元隐含指示的隐式信息。 该特定信元可以是目标 DeNB 中内置的 S-GW和 P-GW的地址信息, 若需要执行网关的重定位, 则可通过在该重定 位判断指示消息中携带 DeNB中内置的 GW的地址信息来指示给 MME。
步骤 409, MME判断是否执行网关的重定位。 MME先根据接收的重定 位判断指示信息判断是否需要网关的重定位。 判断过程描述如下:
1 )重定位判断指示信息是显式指示情况下,若重定位判断指示信息指示 需要执行网关的重定位, 则 MME确定需要执行网关的重定位; 若 MME没 有接收到重定位判断指示信息或者重定位判断指示信息指示不需要执行网关 的重定位, 则 MME确定不需要执行网关的重定位;
2 )在釆用图 1所示移动中继系统架构下,重定位判断指示信息是隐式信 息, 且用于指示隐式信息的特定信元是 DeNB中内置的网关的地址信息情况 下, 若 MME接收到网关的地址信息, 则确定需要执行网关的重定位; 若 MME未接收到网关的地址信息, 则确定不需要执行网关的重定位。
本实施例中釆用的是图 1所示移动中继系统架构, MME若确定需要执 行网关的重定位, 还需要判断目标 DeNB是否满足网关重定位的条件, 若满 足, 则 MME确定执行网关的重定位; 若不满足, 则 MME确定不执行网关 的重定位。若 MME确定执行网关的重定位 ,则根据其接收到的网关的地址, 将内置在目标 DeNB的 S-GW和 P-GW选择为新的为 MRN服务的网关 (称 为目标 S-GW和目标 P-GW ) 。 其中网关重定位的条件包括: 目标 DeNB支持的跟踪区域(Tracking Area, TA ) 包含 MRN支持的 TA。 若釆用为 MRN配置专用 TA的方式, 则目标 DeNB支持的 TA需包含该专用 TA;若不釆用为 MRN配置专用 TA的方式, 则目标 DeNB所支持的 TA需包含初始 DeNB (即 , MRN的 S-GW和 P-GW 所在的 DeNB )所支持的 TA。
在 MRN支持网络共享)的情况下,该网关重定位条件还包括:目标 DeNB 所在的 PLMN需包含 MRN所在的 PLMN。 该项条件可以通过目标 DeNB所 在的 PLMN是否包含初始 DeNB所在的 PLMN来判断。
本实施例所述方法还适用于图 3所示移动中继系统架构。那么,若 MME 判断需要执行网关的重定位, 则不需要判断是否满足网关重定位的条件, 且 确定执行为 MRN服务的网关的重定位; 若 MME判断不需要执行网关的重 定位 , 则确定不执行为 MRN服务的网关的重定位。 若 MME确定执行网关 的重定位, 则重新选择新的位于核心网的为 MRN月良务的网关 (称为目标 S-GW和目标 P-GW ) 。
在这两种架构下, 也可以均不判断目标 DeNB是否满足网关重定位的条 件, 在判断需要执行为 MRN服务的网关的重定位后, 就确定执行网关的重 定位。
步骤 410, MRN的 MME向目标 S-GW (目标 DeNB中内置的 S-GW ) 发送创建会话请求消息,其中包括需要创建的 MRN的演进分组系统( Evolved Packet System, EPS )承载信息和目标 P-GW(内置于目标 DeNB中的 P-GW ) 的地址。
步骤 411 , 目标 S-GW创建 MRN的上下文, 并向目标 P-GW发送创建 会话请求消息。 步骤 412, 目标 P-GW创建 MRN的上下文和 EPS承载后,向目标 S-GW 回复创建会话响应消息。 目标 P-GW可为 MRN分配新的 IP地址。
本实施例釆用图 1 所示系统架构情况下, 目标 S-GW和 P-GW内置在 DeNB中, 步骤 411和步骤 412中信令均为目标 DeNB中内部接口消息。
步骤 413 , 目标 S-GW向 MRN的 MME回复创建会话响应消息, 以确认 MRN的上下文及 EPS 7 载建立完成。
步骤 414, MRN的 MME向目标 DeNB发送路径转移请求确认消息。 之后, MRN或目标 DeNB可为 MRN所服务的 UE发起路径转移请求过 程, 以转移 UE的下行 S1路径。 然后目标 DeNB指示源 DeNB及内置的源 S-GW和源 P-GW释放该 MRN的资源。
实施例二
本实施例描述的是由源 DeNB判断是否需要执行网关重定位并通过目标 DeNB指示给 MME的方法下,在 MRN的 X2切换过程中执行网关重定位的 流程。 图 5描述了该实施例所述流程, 该流程为釆用图 1所示架构情况下的 流程, 其中 MRN 的源 S-GW和源 P-GW可能内置于源 DeNB , 也可能不内 置于源 DeNB , 而是内置于初始 DeNB。 该实施例方法还适用于图 3所示移 动中继系统架构,则 MRN的源 S-GW和源 P-GW, 目标 S-GW和目标 P-GW 都位于核心网。
步骤 501 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 502, 源 DeNB根据其维护的 MRN的上下文中的重定位判断辅助 信息判断是否需要执行网关的重定位。
源 DeNB首先根据该重定位判断辅助信息确定 MRN在上一次网关重定 位之后访问的小区个数, 然后再根据访问的小区个数判断是否需要执行网关 的重定位。 若 MRN在上一次网关重定位之后访问的小区个数超过预配置或 从 OAM获取的访问小区数量阔值, 则判断需要执行网关的重定位; 若未超 过预配置或从 OAM获取的访问小区数量阔值, 则判断不需要执行网关的重 定位。
该重定位判断辅助信息至少包括以下之一:
1 )用于统计 MRN在上一次发生网关重定位之后发生切换的次数的计数 信息;
2 )在 MRN的历史访问小区列表中用于标记 MRN发生网关重定位时的 源小区或目标小区的指示信息;
3 ) MRN发生网关重定位时的源小区或目标小区的标识信息, 其中, 小 区标识信息包括小区标识 ECGI; 以及
4 ) MRN在上一次发生网关重定位之后的历史访问小区记录信息。
另外, 源 DeNB还需根据判断结果对重定位判断辅助信息进行维护。 若 源 DeNB判断需要执行网关的重定位, 则
1 ) 当重定位判断辅助信息为计数信息情况下, 源 DeNB将计数信息清 零; 其中, 计数信息是在 MRN每发生一次不需要执行为所述 MRN服务的 网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB对所述计数信 息加 1得到;
2 ) 当重定位判断辅助信息为指示信息情况下, 源 DeNB在移动中继节 点的历史访问小区列表中的本次切换对应的源小区或目标小区的项目中添加 指示信息;
3 ) 当重定位判断辅助信息为小区标识信息情况下, 源 DeNB 将本次切 换对应的源小区或目标小区的标识信息设置为重定位判断辅助信息; 以及
4 )当重定位判断辅助信息为历史访问小区记录信息情况下, 目标 DeNB 将历史访问小区记录信息清空。 在移动中继节点发生切换后, 均需要对历史 访问小区记录信息进行更新。
步骤 503 , 源 DeNB接收到 MRN的测量报告后, 判断源 DeNB与目标 DeNB之间存在 X2接口, 并且切换后 MRN不需要更换 MME, 则源 DeNB 为 MRN发起 X2切换。 源 DeNB根据测量报告为 MRN选择目标小区。 源 DeNB发送 X2接口切换请求消息给目标 DeNB。该切换请求消息中包含重定 位判断辅助信息, 用于将重定位判断辅助信息传递给目标 DeNB。 该切换请 求消息中还包含重定位判断指示信息,用于指示是否需要执行网关的重定位。
步骤 504-507与步骤 403-406相同, 此处不再重复。
步骤 508 , 目标 DeNB接收 MRN发送的 RRC连接重配置完成消息后, 向 MRN的 MME发送路径转移请求消息, 以更新 MRN的 S1用户面及控制 面路径。 该路径转移请求消息中包含重定位判断指示信息, 用于指示是否需 执行网关的重定位。
重定位判断指示信息可以是显式的指示信息, 则在需要执行网关的重定 位情况下, 该路径转移请求消息还包含目标 DeNB中内置的 S-GW和 P-GW 的地址,以辅助 MRN的 MME将 MRN的网关重定位至目标 DeNB中的网关。
在釆用图 1所示移动中继系统架构下, 重定位判断指示信息也可以是通 过特定信元隐含指示的隐式信息。 该特定信元可以是目标 DeNB 中内置的 S-GW和 P-GW的地址信息, 若需要执行网关的重定位, 则可通过在该重定 位判断指示消息中携带 DeNB中内置的 GW的地址信息来指示给 MME。
步骤 509, MME判断是否执行网关的重定位。 MME先根据接收的重定 位判断指示信息判断是否需要网关的重定位。 判断过程描述如下:
1 )重定位判断指示信息是显式指示情况下,若重定位判断指示信息指示 需要执行网关的重定位, 则 MME确定需要执行网关的重定位; 若 MME没 有接收到重定位判断指示信息或者重定位判断指示信息指示不需要执行网关 的重定位, 则 MME确定不需要执行网关的重定位;
2 )在釆用图 1所示移动中继架构下, 重定位判断指示信息是隐式信息, 且用于指示隐式信息的特定信元是 DeNB 中内置的网关的地址信息情况下, 若 MME接收到网关的地址信息, 则确定需要执行网关的重定位; 若 MME 未接收到网关的地址信息, 则确定不需要执行网关的重定位;
本实施例中釆用的是图 1所示移动中继系统架构, MME若确定需要执 行网关的重定位, 还需要判断目标 DeNB是否满足网关重定位的条件, 若满 足, 则 MME确定执行网关的重定位; 若不满足, 则 MME确定不执行网关 的重定位。若 MME确定执行网关的重定位 ,则根据其接收到的网关的地址, 将内置在目标 DeNB的 S-GW和 P-GW选择为新的为 MRN服务的网关 (称 为目标 S-GW和目标 P-GW ) 。
其中网关重定位的条件包括: 目标 DeNB支持的 TA包含 MRN支持的
TA。 若釆用为 MRN配置专用 TA的方式, 则目标 DeNB支持的 TA需包含 该专用 TA; 若不釆用为 MRN配置专用 TA的方式, 则目标 DeNB所支持的 TA需包含初始 DeNB (即 , MRN的 S-GW和 P-GW所在的 DeNB ) 所支持 的 TA。 在 MRN支持网络共享的情况下,该网关重定位条件还包括: 目标 DeNB 支持的 PLMN需包含 MRN所支持的 PLMN。 该项条件可以通过目标 DeNB 支持的 PLMN是否包含初始 DeNB所支持的 PLMN来判断。
本实施例所述方法还适用于图 3所示移动中继系统架构。那么,若 MME 判断需要执行网关的重定位, 则不需要判断是否满足网关重定位的条件, 且 确定执行为 MRN服务的网关的重定位; 若 MME判断不需要执行网关的重 定位 , 则确定不执行为 MRN服务的网关的重定位。 若 MME确定执行网关 的重定位, 则重新选择新的位于核心网的为 MRN月良务的网关 (称为目标 S-GW和目标 P-GW ) 。
步骤 510-514与步骤 410-414相同, 此处不再重复。
实施例三
本实施例描述的是由目标 DeNB判断是否需要执行网关重定位并指示给 MME的方法下, 在 MRN的 S1切换过程中执行网关重定位的流程。 图 6描 述了该实施例所述流程, 该过程为釆用图 1 所示架构情况下的流程, 其中 MRN 的源 S-GW和源 P-GW可能内置于源 DeNB ,也可能不内置于源 DeNB , 而是内置于初始 DeNB。该实施例方法还适用于图 3所示移动中继系统架构, 则 MRN的源 S-GW和源 P-GW, 目标 S-GW和目标 P-GW都位于核心网。
步骤 601 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 602, 源 DeNB接收到 MRN的测量报告后, 判断源 DeNB和目标 DeNB间没有 X2接口, 或需要为 MRN重新选择一个 MME, 则需要为其执 行 S1切换, 源 DeNB根据测量报告为 MRN选择一个目标小区。 源 DeNB发 送 S1接口切换要求消息给 MRN的源 MME。 该切换要求消息中包含重定位 判断辅助信息, 用于将重定位判断辅助信息传递给目标 DeNB。 该重定位判 断辅助信息存储在源 DeNB中的 MRN的上下文中。 源 DeNB可通过源基站 到目标基站的透传容器发送该重定位判断辅助信息。 该重定位判断辅助信息 至少包括以下之一: 1 )用于统计 MRN在上一次发生网关重定位之后发生切换的次数的计数 信息;
2 )在 MRN的历史访问小区列表中用于标记 MRN发生网关重定位时的 源小区或目标小区的指示信息;
3 ) MRN发生网关重定位时的源小区或目标小区的标识信息, 其中, 小 区标识信息包括小区标识 ECGI; 以及
4 ) MRN在上一次发生网关重定位之后的历史访问小区记录信息。
步骤 603 , 源 MME根据接收的切换要求消息中的目标 DeNB的基站标 识或者目标跟踪区域标识( Tracking Area Identifier, TAI )判断是否要选择一 个新的 MME, 如果需要, 则根据这两个参数选择目标 MME, 并向其发送转 发重定位请求消息,其中携带源基站到目标基站的透传容器、目标基站标识、 目标位置区标识, 以及 MRN的上下文信息等信息。若 MRN的源 MME从源 DeNB接收到重定位判断辅助信息, 则该转发重定位请求消息中包含所接收 到的重定位判断辅助信息。 该重定位判断辅助信息可以包含在源基站到目标 基站的透传容器中。
步骤 604, MRN的目标 MME发送 S1接口切换请求消息给目标 DeNB。 该 S 1接口切换请求消息中包含目标 MME从源 MME接收的重定位判断辅助 信息。 该重定位判断辅助信息可以包含在源基站到目标基站的透传容器中。
步骤 605 , 目标 DeNB根据重定位判断辅助信息判断是否需要执行网关 的重定位。 目标 DeNB首先 居该重定位判断辅助信息确定 MRN在上一次 网关重定位之后访问的小区个数, 然后再根据访问的小区个数判断是否需要 执行网关的重定位。 若 MRN在上一次网关重定位之后访问的小区个数超过 预配置或从 OAM获取的访问小区数量阔值,则判断需要执行网关的重定位; 若未超过预配置或从 OAM获取的访问小区数量阔值, 则判断不需要执行网 关的重定位。另外,目标 DeNB还需对重定位判断辅助信息进行保存和维护。 若目标 DeNB判断需要执行网关的重定位, 并且,
1 ) 当重定位判断辅助信息为计数信息情况下, 目标 DeNB将计数信息 清零; 其中, 计数信息是在 MRN每发生一次不需要执行为所述 MRN服务 的网关的重定位的切换过程时, MRN的源 DeNB或目标 DeNB对所述计数 信息加 1得到;
2 ) 当重定位判断辅助信息为指示信息情况下, 目标 DeNB在移动中继 节点的历史访问小区列表中的本次切换对应的源小区或目标小区的项目中添 加指示信息; 3 ) 当重定位判断辅助信息为小区标识信息情况下, 目标 DeNB将本次 切换对应的源小区或目标小区的标识信息设置为重定位判断辅助信息; 以及
4 )当重定位判断辅助信息为历史访问小区记录信息情况下, 目标 DeNB 将历史访问小区记录信息清空。 在移动中继节点发生切换后, 均需要对历史 访问小区记录信息进行更新。
步骤 606 , 目标 DeNB为 MRN和 UE创建上下文并为 MRN的承载预留 资源之后, 向 MRN的目标 MME发送切换请求确认消息。 该切换请求确认 消息中包含重定位判断指示信息, 用于指示是否需执行网关的重定位。
重定位判断指示信息可以是显式的指示信息, 则在需要执行网关的重定 位情况下, 该切换请求确认消息还包含目标 DeNB中内置的 S-GW和 P-GW 的地址,以辅助 MRN的 MME将 MRN的网关重定位至目标 DeNB中的网关。
在釆用图 1所示移动中继系统架构下, 重定位判断指示信息也可以是通 过特定信元隐含指示的隐式信息。 该特定信元可以是目标 DeNB 中内置的 S-GW和 P-GW的地址信息, 若需要执行网关的重定位, 则可通过在该重定 位判断指示消息中携带 DeNB中内置的 GW的地址信息来指示给 MME。
步骤 607-611与步骤 509-513相同, 此处不再重复。
需要注意的是,目标 S-GW和目标 P-GW内置在 DeNB情况下,步骤 609 和步骤 610中信令均为目标 DeNB中内部接口消息。
步骤 612 , MRN的目标 MME向源 MME发送转发重定位响应消息。 需注意的是,如果不需要选择新的 MME,则步骤 603和步骤 612跳过, 并且源 MME和目标 MME的行为都是同一 MME的行为。
步骤 613 , MRN的源 MME向源 DeNB发送 S1接口切换命令消息。 步骤 614,源 DeNB发送空口消息 RRC连接重配置消息给 MRN,该 RRC 连接重配置消息中携带目标 DeNB通过 MRN的 MME发送给源 DeNB的透 传容器中的切换命令消息, 以指示 MRN执行切换。
步骤 615, MRN接收到切换命令后, 从源 DeNB小区去附着, 并与目标 小区同步, 并发起 RACH过程接入目标小区。 MRN与目标小区完成 RRC连 接建立后, 发送 RRC连接重配置完成消息给目标 DeNB。
步骤 616,目标 DeNB发送 S1接口切换通知消息给 MRN的目标 MME。 然后 MRN的目标 MME完成后续操作。
之后, MRN或目标 DeNB可为 MRN所服务的 UE发起路径转移请求过 程, 以转移 UE的下行 S1路径。然后再执行源 DeNB及内置的源 S-GW和源 P-GW的资源释放过程。
需要注意的是, 步骤 607-611也可以在步骤 616后执行。
另外, 步骤 606中可不携带重定位判断指示信息, 该重定位判断指示信 息可以在步骤 616中切换通知消息中携带,相应地,步骤 607-611在步骤 616 后执行。
实施例四
本实施例描述的是由源 DeNB 判断是否需要执行网关重定位并指示给 MME的方法下, 在 MRN的 S1切换过程中执行网关重定位的流程。 图 7描 述了该实施例所述流程, 该流程为釆用图 1 所示架构情况下的流程, 其中 MRN 的源 S-GW和源 P-GW可能内置于源 DeNB ,也可能不内置于源 DeNB , 而是内置于初始 DeNB。该实施例方法还适用于图 3所示移动中继系统架构, 则 MRN的源 S-GW和源 P-GW, 目标 S-GW和目标 P-GW都位于核心网。
步骤 701 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 702与步骤 502相同, 此处不再重复。
步骤 703 , 源 DeNB接收到 MRN的测量报告后, 判断源 DeNB和目标
DeNB间没有 X2接口, 或需要为 MRN重新选择一个 MME, 则需要为其执 行 S1切换, 源 DeNB根据测量报告为 MRN选择一个目标小区。 源 DeNB发 送 S1接口切换要求消息给 MRN的源 MME。 该切换要求消息中包含重定位 判断辅助信息, 用于将重定位判断辅助信息传递给目标 DeNB。 该重定位辅 助信息存储在源 DeNB中的 MRN的上下文中。 源 DeNB可通过源基站到目 标基站的透传容器发送该重定位判断辅助信息。 该切换要求消息中还包含重 定位判断指示信息, 用于指示是否需要执行网关的重定位。 其中, 重定位判 断辅助信息至少包括以下之一:
1 )用于统计 MRN在上一次发生网关重定位之后发生切换的次数的计数 信息;
2 )在 MRN的历史访问小区列表中用于标记 MRN发生网关重定位时的 源小区或目标小区的指示信息;
3 ) MRN发生网关重定位时的源小区或目标小区的标识信息, 其中, 小 区标识信息包括小区标识 ECGI; 以及
4 ) MRN在上一次发生网关重定位之后的历史访问小区记录信息。
步骤 704 , 源 MME根据接收的切换要求消息中的目标 DeNB的基站标 识或者目标 TAI判断是否要选择一个新的 MME, 如果需要, 则根据这两个 参数选择目标 MME, 并向其发送转发重定位请求消息, 其中携带源基站到 目标基站的透传容器、 目标基站标识、 目标位置区标识, 以及 MRN的上下 文信息等信息。若 MRN的源 MME从源 DeNB接收到重定位判断辅助信息, 则该转发重定位请求消息中包含所接收到的重定位判断辅助信息。 该重定位 判断辅助信息可以包含在源基站到目标基站的透传容器中。 若源 MME从源 DeNB接收到重定位判断指示信息, 则该转发重定位请求消息中还包含重定 位判断指示信息。
步骤 705 , MRN的目标 MME发送 S1接口切换请求消息给目标 DeNB。 该 S 1接口切换请求消息中包含目标 MME从源 MME接收的重定位判断辅助 信息。 该重定位判断辅助信息可以包含在源基站到目标基站的透传容器中。 该 S1接口切换请求消息中还可以包含从源 MME接收的重定位判断指示信息。
步骤 706, 目标 DeNB为 MRN和 UE创建上下文并为 MRN的承载预留 资源之后 , 向 MRN的目标 MME发送切换请求确认消息。 若目标 DeNB从 MME接收到重定位判断指示信息, 且该重定位判断指示信息指示需要执行 网关的重定位, 则该切换请求消息中还包括目标 DeNB 中内置的 S-GW和 P-GW的地址信息,以辅助 MRN的 MME将 MRN的网关重定位至目标 DeNB 中的网关。
步骤 707 , 目标 MME判断是否执行网关的重定位。 目标 MME先根据 接收的重定位判断指示信息判断是否需要执行网关的重定位。 若重定位判断 指示信息指示需要执行网关的重定位, 则目标 MME确定需要执行网关的重 定位; 若目标 MME没有接收到重定位判断指示信息或者重定位判断指示信 息指示不需要执行网关的重定位, 则目标 MME确定不需要执行网关的重定 位;
本实施例中釆用的是图 1所示移动中继系统架构, MME若确定需要执 行网关的重定位, 还需要判断目标 DeNB是否满足网关重定位的条件, 若满 足, 则 MME确定执行网关的重定位; 若不满足, 则 MME确定不执行网关 的重定位。若 MME确定执行网关的重定位 ,则根据其接收到的网关的地址, 将内置在目标 DeNB的 S-GW和 P-GW选择为新的为 MRN服务的网关 (称 为目标 S-GW和目标 P-GW ) 。
其中网关重定位的条件包括: 目标 DeNB支持的 TA包含 MRN支持的
TA。 若釆用为 MRN配置专用 TA的方式, 则目标 DeNB支持的 TA需包含 该专用 TA; 若不釆用为 MRN配置专用 TA的方式, 则目标 DeNB所支持的 TA需包含初始 DeNB (即 , MRN的 S-GW和 P-GW所在的 DeNB ) 所支持 的 TA。
在 MRN支持网络共享的情况下,该网关重定位条件还包括: 目标 DeNB 支持的 PLMN需包含 MRN所支持的 PLMN。 该项条件可以通过目标 DeNB 支持的 PLMN是否包含初始 DeNB所支持的 PLMN来判断。
本实施例所述方法还适用于图 3所示移动中继系统架构。那么,若 MME 判断需要执行网关的重定位, 则不需要判断是否满足网关重定位的条件, 且 确定执行为 MRN服务的网关的重定位; 若 MME判断不需要执行网关的重 定位 , 则确定不执行为 MRN服务的网关的重定位。 若 MME确定执行网关 的重定位, 则重新选择新的位于核心网的为 MRN月良务的网关 (称为目标 S-GW和目标 P-GW ) 。
步骤 708-716与步骤 608-616相同, 此处不再重复。 需要注意的是, 步骤 707-711也可以在步骤 716后执行。
另外, 步骤 706中可不携带重定位判断指示信息, 该重定位判断指示信 息可以在步骤 716中切换通知消息中携带,相应地,步骤 707-711在步骤 716 后执行。
本实施例方法还适用于图 3所示系统架构, 则步骤 707-711还可以在步 骤 704之后 , 步骤 705之前执行。 在该系统架构下, 目标 MME为 MRN选 择新的位于核心网的 S-GW和 P-GW。
方法实施例五
本实施例描述的是由 MME判断是否执行网关重定位的方法下,在 MRN 的 X2切换过程中执行网关重定位的流程。 图 8描述了该实施例所述流程, 该流程为釆用图 1所示架构情况下的流程,其中 MRN 的源 S-GW和源 P-GW 可能内置于源 DeNB, 也可能不内置于源 DeNB, 而是内置于初始 DeNB。 该 实施例方法还适用于图 3所示移动中继系统架构, 则 MRN的源 S-GW和源 P-GW, 目标 S-GW和目标 P-GW都位于核心网。
步骤 801 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 802, 源 DeNB接收到 MRN的测量报告后, 判断源 DeNB与目标 DeNB之间存在 X2接口, 并且切换后 MRN不需要更换 MME, 则源 DeNB 为 MRN发起 X2切换。 源 DeNB根据测量 4艮告为 MRN选择一个目标小区。 源 DeNB发送 X2接口切换请求消息给目标 DeNB。
步骤 803 , 目标 DeNB根据切换请求消息中需建立的 E-RAB的 QoS等 信息为 MRN预留资源并创建上下文信息, 之后回复切换请求确认消息。 该 切换请求确认消息中包含透传的空口的切换命令消息。
步骤 804 ,源 DeNB发送空口消息 RRC连接重配置消息给 MRN ,该 RRC 连接重配置消息中携带目标 DeNB通过源 DeNB发送给 MRN的透传的切换 命令消息, 以指示 MRN执行切换。
步骤 805,源 DeNB发送 SN状态转移消息给目标 DeNB,用于传递 RLC AM模式无线承载的上行和下行 PDCP SN接收和发送状态。
步骤 806, MRN接收到切换命令后, 从源 DeNB小区去附着, 并与目标 小区同步, 并发起 RACH过程接入目标小区。 MRN与目标小区完成 RRC连 接建立后, 发送 RRC连接重配置完成消息给目标 DeNB。
步骤 807 , 目标 DeNB接收 MRN发送的 RRC连接重配置完成消息后, 向 MRN的 MME发送路径转移请求消息, 以更新 MRN的 S1用户面及控制 面路径。 本实施例流程中釆用的是图 1所示移动中继系统架构, 该路径转移 请求消息还包含目标 DeNB中内置的 S-GW和 P-GW的地址, 以辅助 MRN 的 MME将 MRN的网关重定位至目标 DeNB中的网关。 若釆用图 3所示移 动中继系统架构, 则该消息中不需要携带 S-GW和 P-GW的地址。
步骤 808, MME判断是否执行网关的重定位。 MME先根据 MRN的当 前位置判断是否需要执行网关的重定位。 MME 可根据当前服务 MRN 的 DeNB的小区的 TAI和 /或 ECGI得到 MRN的当前位置。
本实施例中釆用的是图 1所示移动中继系统架构 , MME可保存 MRN接 入其网关所在 DeNB (称为初始 DeNB ) 时, 为其服务的初始 DeNB的小区 的 TAI和 /或 ECGI, 以得到 MRN的 S-GW和 P-GW的当前位置。 当 MRN 与其 S-GW和 P-GW之间的距离大于网关重定位距离阔值时, 则 MME判断 需要执行网关的重定位; 若不大于网关重定位距离阔值, 则 MME判断不需 要执行网关的重定位。 MME 若确定需要执行网关的重定位, 还需要判断目 标 DeNB是否满足网关重定位的条件, 若满足, 则 MME确定执行网关的重 定位; 若不满足, 则 MME确定不执行网关的重定位。 若 MME确定执行网 关的重定位, 则根据其接收到的网关的地址, 将内置在目标 DeNB的 S-GW 和 P-GW选择为新的为 MRN服务的网关(称为目标 S-GW和目标 P-GW )。
其中网关重定位的条件包括: 目标 DeNB支持的 TA包含 MRN支持的 TA。 若釆用为 MRN配置专用 TA的方式, 则目标 DeNB支持的 TA需包含 该专用 TA; 若不釆用为 MRN配置专用 TA的方式, 则目标 DeNB所支持的 TA需包含初始 DeNB (即 , MRN的 S-GW和 P-GW所在的 DeNB ) 所支持 的 TA。
在 MRN支持网络共享的情况下,该网关重定位条件还包括: 目标 DeNB 支持的 PLMN需包含 MRN所支持的 PLMN。 该项条件可以通过目标 DeNB 支持的 PLMN是否包含初始 DeNB所支持的 PLMN来判断。
本实施例所述方法还适用于图 3 所示移动中继系统架构。 同样地, 当 MRN与其 S-GW和 P-GW的距离大于网关重定位距离阔值时 , 则 MME判 断需要执行网关的重定位; 若不大于网关重定位距离阔值, 则 MME判断不 需要执行网关的重定位。 若 MME判断需要执行网关的重定位, 则不需要判 断是否满足网关重定位的条件, 且确定执行为 MRN服务的网关的重定位; 若 MME判断不需要执行网关的重定位, 则确定不执行为 MRN服务的网关 的重定位。 若 MME确定执行网关的重定位, 则重新选择新的位于核心网的 为 MRN服务的网关 (称为目标 S-GW和目标 P-GW ) 。
步骤 809-813与步骤 410-414相同, 此处不再重复。
实施例六
本实施例描述的是由 MME判断是否需要执行网关重定位的方法下, 在 MRN的 S1切换过程中执行网关重定位的流程。 图 9描述了该实施例所述流 程, 该流程为釆用图 1所示架构情况下的流程, 其中 MRN 的源 S-GW和源 P-GW可能内置于源 DeNB,也可能不内置于源 DeNB,而是内置于初始 DeNB。 该实施例方法还适用于图 3所示移动中继系统架构, 则 MRN的源 S-GW和 源 P-GW, 目标 S-GW和目标 P-GW都位于核心网。
步骤 901 , MRN测量到一个或多个小区满足测量报告的触发条件, 则将 满足条件的小区的标识和测量参数通过测量报告发送给为其服务的源 DeNB。
步骤 902, 源 DeNB接收到 MRN的测量报告后, 判断源 DeNB和目标 DeNB间没有 X2接口, 或需要为 MRN重新选择一个 MME,则需要为其执行 S1切换, 源 DeNB根据测量报告为 MRN选择一个目标小区。 源 DeNB发送 S1接口切换要求消息给 MRN的源 MME。
步骤 903 , 源 MME根据接收的切换要求消息中的目标 DeNB的基站标 识或者目标 TAI判断是否要选择一个新的 MME, 如果需要, 则根据这两个 参数选择目标 MME, 并向其发送转发重定位请求消息, 其中携带源基站到 目标基站的透传容器、 目标基站标识、 目标位置区标识, 以及 MRN的上下 文信息等信息。
步骤 904, MRN的目标 MME发送 S1接口切换请求消息给目标 DeNB。 步骤 905 , 目标 DeNB为 MRN和 UE创建上下文并为 MRN的承载预留 资源之后, 向 MRN的目标 MME发送切换请求确认消息。 釆用图 1所示系 统架构情况下, 该切换请求确认消息还包含目标 DeNB 中内置的 S-GW和 P-GW的地址,以辅助 MRN的 MME将 MRN的网关重定位至目标 DeNB中 的网关。 釆用图 3所示系统架构下, 该切换请求确认消息不需要包含 S-GW 和 P-GW的地址。
步骤 906与步骤 808相同, 此处不再重复。
步骤 907-915与步骤 608-616相同, 此处不再重复。
需要注意的是, 目标 S-GW和 P-GW内置在 DeNB情况下, 步骤 908和 步骤 909中信令均为目标 DeNB中内部接口消息。 并且, 如果不需要选择新 的 MME, 则步骤 903和步骤 911跳过, 并且源 MME和目标 MME的行为都 是同一 MME的行为。
需要注意的是, 步骤 906-910也可以在步骤 915后执行。
另外, 釆用图 1所示系统架构情况下, 步骤 905中可不携带目标 DeNB 中内置的 S-GW和 P-GW的地址信息,该 S-GW和 P-GW的地址信息可以在 步骤 915中切换通知消息中携带,相应地,步骤 906-910在步骤 915后执行。
本实施例方法还适用于图 3所示系统架构, 则步骤 906-910还可以在步 骤 903之后 , 步骤 904之前执行。 在该系统架构下, 目标 MME为 MRN选 择新的位于核心网的 S-GW和 P-GW。
如图 10所示, 本实施方式还提供了一种移动管理实体, 包括: 位置确定 单元 100和第一判断单元 101 , 其中:
位置确定单元 100用于: 在 MRN切换 DeNB的过程中, 确定 MRN的 当前位置; 以及
第一判断单元 101 用于: 根据 MRN 的当前位置判断是否需要执行为 MRN服务的网关的重定位。
第一判断单元 101是用于以如下方式根据 MRN的当前位置判断是否需 要执行为 MRN服务的网关的重定位:
根据 MRN与为 MRN服务的网关之间的距离,判断是否需要执行为 MRN 服务的网关的重定位, 在 MRN与为 MRN服务的网关之间的距离大于网关 重定位距离阔值时, 判断需要执行为 MRN服务的网关的重定位。
位置确定单元 100是用于以如下方式确定 MRN的当前位置:根据 MRN 的当前所在的 DeNB下的小区的跟踪区域码和 /或小区标识, 得到 MRN的当 前位置;
位置确定单元 100还用于: 根据所保存的为 MRN服务的网关的位置相 关信息, 得到为 MRN服务的网关的位置; 以及
第一判断单元 101是用于以如下方式根据 MRN与为 MRN服务的网关 之间的距离, 判断是否需要执行为 MRN服务的网关的重定位: 根据 MRN 的当前位置和为 MRN服务的网关的位置,确定 MRN与为 MRN服务的网关 之间的距离, 判断是否需要执行为 MRN服务的网关的重定位。
移动管理实体还包括: 第二判断单元 102, 其中:
第二判断单元 102用于: 在第一判断单元判断需要执行为 MRN服务的 网关的重定位后, 在为 MRN服务的网关内置在 DeNB的系统架构下, 判断 MRN的目标 DeNB是否满足网关重定位条件,如果满足,则确定执行为 MRN 服务的网关的重定位; 如果不满足, 则确定不执行为 MRN服务的网关的重 定位。
第二判断单元 102是用于以如下方式判断 MRN的目标 DeNB是否满足 网关重定位条件:
判断目标 DeNB支持的跟踪区域是否包含 MRN支持的跟踪区域;或者, 判断目标 DeNB 支持的跟踪区域是否包含当前为 MRN服务的网关所在的 DeNB支持的跟踪区域。
第二判断单元 102是用于以如下方式判断所述 MRN的目标 DeNB是否 满足网关重定位条件: 判断目标 DeNB所在的 PLMN是否包含 MRN所在的 PLMN; 或者, 判 断目标 DeNB所在的 PLMN是否包含当前为 MRN服务的网关所在的 DeNB 所在的 PLMN。
如图 11所示, 本实施方式提供的另一种移动管理实体, 包括: 接收单元
110和重定位判断单元 111 , 其中:
接收单元 110用于: 在 MRN切换 DeNB的过程中, 接收重定位判断指 示信息; 以及
重定位判断单元 111用于: 根据重定位判断指示信息判断是否需要执行 为 MRN服务的网关的重定位;
其中, 重定位判断指示信息是 MRN的源 DeNB或目标 DeNB根据重定 位判断辅助信息判断是否需要执行为 MRN服务的网关的重定位后发送给接 收单元 110; 或者, 是 MRN的目标 DeNB根据配置信息判断是否需要执行 为 MRN服务的网关的重定位后发送给接收 110。
重定位判断单元 111是用于以如下方式根据重定位判断指示信息判断是 否需要执行为 MRN服务的网关的重定位:
在重定位判断指示信息是显式的指示信息的情况下, 在重定位判断指示 信息指示需要执行重定位时, 判断需要执行为 MRN服务的网关的重定位; 在没有接收到重定位判断指示信息或者重定位判断指示信息指示不需要执行 重定位时, 判断不需要执行为 MRN服务的网关的重定位; 或者,
在重定位判断指示信息是隐式的指示信息的情况下, 且重定位判断指示 信息釆用为 MRN服务的网关的地址隐含指示时, 在接收到地址时, 判断需 要执行为 MRN服务的网关的重定位; 在未接收到地址时, 则判断不需要执 行为 MRN服务的网关的重定位。
如图 12所示, 本实施方式还提供了一种宿主基站, 包括: 判断单元 120 和发送单元 121 , 其中:
判断单元 120用于: 在 MRN切换 DeNB的过程中, 根据重定位判断辅 助信息判断是否需要执行为 MRN服务的网关的重定位; 或者, 根据配置信 息判断是否需要执行为 MRN服务的网关的重定位; 以及
发送单元 121用于: 向 MRN的 MME发送重定位判断指示信息。
重定位判断辅助信息包括: 用于统计 MRN在上一次发生网关重定位之 后发生切换的次数的计数信息; 或者,
在 MRN的历史访问小区列表中用于标记 MRN发生网关重定位时的源 小区或目标小区的指示信息; 或者,
MRN发生网关重定位时的源小区或目标小区的标识信息; 或者,
MRN在上一次发生网关重定位之后的历史访问小区记录信息。
判断单元 120是用于以如下方式根据重定位判断辅助信息判断是否需要 执行为 MRN服务的网关的重定位:
根据重定位判断辅助信息确定 MRN在上一次为 MRN服务的网关重定 位之后访问的小区的个数; 以及判断 MRN在上一次为 MRN服务的网关重 定位之后访问的小区的个数是否达到访问小区数量阔值, 如果达到, 则判断 需要执行为 MRN服务的网关的重定位。
发送单元 121是用于以如下方式向 MRN的 MME发送重定位判断指示 信息:
在为 MRN服务的网关内置于 DeNB的系统架构下, 如果判断单元 120 判断需要执行为 MRN服务的网关的重定位, 将为 MRN服务的网关的地址 信息作为重定位判断指示信息发送给 MME。 MME在接收到为 MRN服务的 网关的地址信息后, 确定需要执行为 MRN服务的网关的重定位。
宿主基站还包括: 信息维护单元 122, 其中:
信息维护单元 122用于: 在本次切换过程中执行为 MRN服务的网关的 重定位后,在重定位判断辅助信息包含计数信息时,将计数信息清零,其中, 计数信息是在 MRN每发生一次不需要执行为 MRN服务的网关的重定位的 切换过程时, MRN的源 DeNB或目标 DeNB对计数信息加 1得到;
在重定位判断辅助信息包含指示信息时, 在 MRN的历史访问小区列表 中的本次切换对应的源小区或目标小区的项目中添加指示信息; 在重定位判断辅助信息包含标识信息时, 将本次切换对应的源小区或目 标小区的标识信息设置为重定位判断辅助信息; 以及
在重定位判断辅助信息包含 MRN在上一次发生网关重定位之后的历史 访问小区记录信息时, 将历史访问小区记录信息清空。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成, 所述程序可以存储于计算机可读存储介质中, 如, 只 读存储器、 磁盘或光盘等。 可选地, 上述实施例的全部或部分步骤也可以使 用一个或多个集成电路来实现。 相应地, 上述实施例中的各模块 /单元可以釆 用硬件的形式实现, 也可以釆用软件功能模块的形式实现。 本发明实施例不 限制于任何特定形式的硬件和软件的结合。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡在本 发明实施例的精神和原则之内所作的任何修改、 等同替换和改进等, 均应包 含在本发明所附权利要求的保护范围之内。
工业实用性
本发明实施例中, 能够解决 MRN切换过程中判断是否执行网关重定位 的问题, 使得路由优化顺利执行, 进而缩短 UE数据和信令的延迟。

Claims

权利要求书
1、 一种网关重定位的方法, 包括:
在移动中继节点 MRN切换宿主基站 DeNB的过程中, 所述 MRN的移 动管理实体 MME根据所述 MRN的当前位置判断是否需要执行为所述 MRN 服务的网关的重定位。
2、如权利要求 1所述的方法,其中, 所述 MRN的 MME根据所述 MRN 的当前位置判断是否需要执行为所述 MRN服务的网关的重定位, 包括:
所述 MME根据所述 MRN与为所述 MRN服务的网关之间的距离,判断 是否需要执行为所述 MRN服务的网关的重定位,在所述 MRN与为所述 MRN 服务的网关之间的距离大于网关重定位距离阔值时, 判断需要执行为所述 MRN服务的网关的重定位。
3、 如权利要求 2所述的方法, 其中, 所述 MME根据所述 MRN与为所 述 MRN服务的网关之间的距离, 判断是否需要执行为所述 MRN服务的网 关的重定位, 包括:
所述 MME根据所述 MRN当前所在的 DeNB下的小区的跟踪区域码和 / 或小区标识, 得到所述 MRN的当前位置;
所述 MME根据所保存的为所述 MRN服务的网关的位置相关信息, 得 到为所述 MRN服务的网关的位置; 以及
所述 MME根据所述 MRN的当前位置和为所述 MRN服务的网关的位置, 确定所述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要执行 为所述 MRN服务的网关的重定位。
4、 如权利要求 3所述的方法, 其中: 在为所述 MRN服务的网关内置于 DeNB的系统架构下, 为所述 MRN服务的网关的位置相关信息是所述 MRN 接入为所述 MRN服务的网关所在的 DeNB时, 在为所述 MRN服务的网关 所在的 DeNB下, 为所述 MRN服务的小区的跟踪区域码和 /或小区标识。
5、 如权利要求 2所述的方法, 还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 则确 定执行为所述 MRN服务的网关的重定位。
6、 如权利要求 2所述的方法, 还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 在为 所述 MRN服务的网关内置在 DeNB的系统架构下,所述 MME判断所述 MRN 的目标 DeNB是否满足网关重定位条件, 如果满足, 则所述 MME确定执行 为所述 MRN服务的网关的重定位; 如果不满足, 则所述 MME确定不执行 为所述 MRN服务的网关的重定位;
在为所述 MRN服务的网关位于核心网的架构下, 所述 MME在判断需 要执行为所述 MRN服务的网关的重定位后 , 则确定执行为所述 MRN服务 的网关的重定位。
7、 如权利要求 5或 6所述的方法, 还包括:
所述 MME在确定执行为所述 MRN服务的网关的重定位后 , 执行为所 述 MRN服务的网关的重定位, 其中, 所述重定位包括为所述 MRN服务的 分组数据网络网关 P-GW和 /或服务网关 S-GW的重定位; 以及将所述 MRN 的分组数据网络 PDN连接转移至所述重定位后的网关。
8、 如权利要求 6所述的方法, 其中, 所述 MME判断所述 MRN的目标
DeNB是否满足网关重定位条件, 包括:
所述 MME判断所述目标 DeNB支持的跟踪区域是否包含所述 MRN支 持的跟踪区域; 或者,
所述 MME判断所述目标 DeNB 支持的跟踪区域是否包含当前为所述 MRN服务的网关所在的 DeNB支持的跟踪区域。
9、 如权利要求 6所述的方法, 其中, 所述 MME判断所述 MRN的目标 DeNB是否满足网关重定位条件, 包括:
所述 MME判断所述目标 DeNB所在的公共陆地移动网络 PLMN是否包 含所述 MRN所在的 PLMN; 或者,
所述 MME判断所述目标 DeNB所在的 PLMN是否包含当前为所述 MRN 服务的网关所在的 DeNB所在的 PLMN。
10、 一种网关重定位的方法, 包括:
在移动中继节点 MRN切换宿主基站 DeNB的过程中, 所述 MRN的移 动管理实体 MME接收重定位判断指示信息, 根据所述重定位判断指示信息 判断是否需要执行为所述 MRN服务的网关的重定位;
其中, 所述重定位判断指示信息是所述 MRN的源 DeNB或目标 DeNB 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关的重定 位后发送给所述 MME; 或者,是所述 MRN的目标 DeNB根据配置信息判断 是否需要执行为所述 MRN服务的网关的重定位后发送给所述 MME。
11、 如权利要求 10所述的方法, 其中:
所述重定位判断辅助信息包括: 用于统计所述 MRN在上一次发生网关 重定位之后发生切换的次数的计数信息; 或者,
在所述 MRN的历史访问小区列表中用于标记所述 MRN发生网关重定 位时的源小区或目标小区的指示信息; 或者,
所述 MRN发生网关重定位时的源小区或目标小区的标识信息; 或者, 所述 MRN在上一次发生网关重定位之后的历史访问小区记录信息。
12、 如权利要求 11所述的方法, 其中, 所述 MRN的源 DeNB或目标 DeNB根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关 的重定位, 包括:
所述源 DeNB或所述目标 DeNB 居所述重定位判断辅助信息确定所述 MRN在上一次为所述 MRN服务的网关重定位之后访问的小区的个数; 以及 所述源 DeNB或所述目标 DeNB判断所述 MRN在上一次为所述 MRN 服务的网关重定位之后访问的小区的个数是否达到访问小区数量阔值, 如果 达到, 则判断需要执行所述为所述 MRN服务的网关的重定位。
13、 如权利要求 10所述的方法, 还包括:
在为所述 MRN服务的网关内置于 DeNB 的系统架构下, 如果所述源 DeNB或所述目标 DeNB判断需要执行为所述 MRN服务的网关的重定位, 则所述目标 DeNB将内置在所述目标 DeNB的为所述 MRN服务的网关的地 址信息作为所述重定位判断指示信息发送给所述 MME; 所述 MME在接收 到为所述 MRN服务的网关的地址信息后, 确定需要执行为所述 MRN服务 的网关的重定位。
14、 如权利要求 12所述的方法, 还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 则确 定执行为所述 MRN服务的网关的重定位。
15、 如权利要求 12所述的方法, 还包括:
所述 MME在判断需要执行为所述 MRN服务的网关的重定位后, 在为 所述 MRN服务的网关内置在所述 MRN的目标 DeNB中时 ,所述 MME判断 所述 MRN的目标 DeNB是否满足网关重定位条件,如果满足,则所述 MME 确定执行为所述 MRN服务的网关的重定位; 如果不满足, 则所述 MME确 定不执行为所述 MRN服务的网关的重定位; 以及
在为所述 MRN服务的网关位于核心网的架构下, 所述 MME在判断需 要执行为所述 MRN服务的网关的重定位后 , 则确定执行为所述 MRN服务 的网关的重定位。
16、 如权利要求 14或 15所述的方法, 还包括:
所述 MME在确定执行为所述 MRN服务的网关的重定位后 , 执行为所 述 MRN服务的网关的重定位, 其中, 所述重定位至少包括为所述 MRN服 务的分组数据网络网关 P-GW和 /或服务网关 S-GW的重定位; 以及将所述 MRN的分组数据网络 PDN连接转移至所述重定位后的网关。
17、 如权利要求 11所述的方法, 其中:
所述重定位判断辅助信息由保存有所述 MRN的上下文信息的 DeNB保 存和维护; 当所述 MRN发生切换时, 所述重定位判断辅助信息由所述源 DeNB发送给所述目标 DeNB。
18、 如权利要求 11所述的方法, 还包括:
所述源 DeNB或所述目标 DeNB在本次切换过程中执行为所述 MRN服 务的网关的重定位后, 在所述重定位判断辅助信息包含所述计数信息时, 将 所述计数信息清零, 其中, 所述计数信息是在所述 MRN每发生一次不需要 执行为所述 MRN服务的网关的重定位的切换过程时,所述 MRN的源 DeNB 或目标 DeNB对所述计数信息加 1得到;
在所述重定位判断辅助信息包含所述指示信息时, 所述源 DeNB或所述 目标 DeNB在所述 MRN的历史访问小区列表中的本次切换对应的源小区或 目标小区的项目中添加指示信息;
在所述重定位判断辅助信息包含所述标识信息时, 所述源 DeNB或所述 目标 DeNB将本次切换对应的源小区或目标小区的标识信息设置为所述重定 位判断辅助信息; 以及
在所述重定位判断辅助信息包含所述 MRN在上一次发生网关重定位之 后的历史访问小区记录信息时, 所述源 DeNB或所述目标 DeNB将所述历史 访问小区记录信息清空。
19、如权利要求 13所述的方法, 所述 MME根据所述重定位判断指示信 息判断是否需要执行为所述 MRN服务的网关的重定位, 包括:
在所述重定位判断指示信息是显式的指示信息的情况下, 在所述重定位 判断指示信息指示需要执行重定位时,所述 MME判断需要执行为所述 MRN 服务的网关的重定位; 在所述 MMME没有接收到所述重定位判断指示信息 或者所述重定位判断指示信息指示不需要执行重定位时, 所述 MME判断不 需要执行为所述 MRN服务的网关的重定位; 或者,
在所述重定位判断指示信息是隐式的指示信息的情况下, 且所述重定位 判断指示信息釆用为所述 MRN服务的网关的地址隐含指示时,在所述 MME 接收到所述地址时, 所述 MME判断需要执行为所述 MRN服务的网关的重 定位; 在所述 MME未接收到所述地址时, 则所述 MME判断不需要执行为 所述 MRN服务的网关的重定位。
20、 一种移动管理实体, 包括: 位置确定单元和第一判断单元, 其中: 所述位置确定单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB 的过程中, 确定所述 MRN的当前位置; 以及
所述第一判断单元设置成: 根据所述 MRN的当前位置判断是否需要执 行为所述 MRN服务的网关的重定位。
21、 如权利要求 20所述的移动管理实体, 其中:
所述第一判断单元是设置成以如下方式根据所述 MRN的当前位置判断 是否需要执行为所述 MRN服务的网关的重定位: 根据所述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要 执行为所述 MRN服务的网关的重定位 ,在所述 MRN与为所述 MRN服务的 网关之间的距离大于网关重定位距离阔值时, 判断需要执行为所述 MRN服 务的网关的重定位。
22、 如权利要求 21所述的移动管理实体, 其中:
所述位置确定单元是设置成以如下方式确定所述 MRN的当前位置: 根 据所述 MRN当前所在的 DeNB下的小区的跟踪区域码和 /或小区标识, 得到 所述 MRN的当前位置;
所述位置确定单元还设置成: 根据所保存的为所述 MRN服务的网关的 位置相关信息, 得到为所述 MRN服务的网关的位置; 以及
所述第一判断单元是设置成以如下方式根据所述 MRN与为所述 MRN 服务的网关之间的距离, 判断是否需要执行为所述 MRN服务的网关的重定 位: 根据所述 MRN的当前位置和为所述 MRN服务的网关的位置, 确定所 述 MRN与为所述 MRN服务的网关之间的距离, 判断是否需要执行为所述 MRN服务的网关的重定位。
23、如权利要求 21所述的移动管理实体,还包括:第二判断单元,其中: 所述第二判断单元设置成: 在所述第一判断单元判断需要执行为所述
MRN服务的网关的重定位后,在为所述 MRN服务的网关内置在 DeNB的系 统架构下, 判断所述 MRN的目标 DeNB是否满足网关重定位条件, 如果满 足, 则确定执行为所述 MRN服务的网关的重定位; 如果不满足, 则确定不 执行为所述 MRN服务的网关的重定位。
24、 如权利要求 23所述的移动管理实体, 其中:
所述第二判断单元是设置成以如下方式判断所述 MRN的目标 DeNB是 否满足网关重定位条件:
判断所述目标 DeNB支持的跟踪区域是否包含所述 MRN支持的跟踪区 域; 或者, 判断所述目标 DeNB支持的跟踪区域是否包含当前为所述 MRN 服务的网关所在的 DeNB支持的跟踪区域。
25、 如权利要求 23所述的移动管理实体, 其中: 所述第二判断单元是设置成以如下方式判断所述 MRN的目标 DeNB是 否满足网关重定位条件:
判断所述目标 DeNB 所在的公共陆地移动网络 PLMN是否包含所述 MRN所在的 PLMN; 或者 , 判断所述目标 DeNB所在的 PLMN是否包含当 前为所述 MRN服务的网关所在的 DeNB所在的 PLMN。
26、 一种移动管理实体, 包括: 接收单元和重定位判断单元, 其中: 所述接收单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB的过 程中, 接收重定位判断指示信息; 以及
所述重定位判断单元设置成: 根据所述重定位判断指示信息判断是否需 要执行为所述 MRN服务的网关的重定位;
其中, 所述重定位判断指示信息是所述 MRN的源 DeNB或目标 DeNB 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关的重定 位后发送给所述接收单元; 或者, 是所述 MRN的目标 DeNB根据配置信息 判断是否需要执行为所述 MRN服务的网关的重定位后发送给所述接收单元。
27、 如权利要求 26所述的移动管理实体, 其中:
所述重定位判断单元是设置成以如下方式 4艮据所述重定位判断指示信息 判断是否需要执行为所述 MRN服务的网关的重定位:
在所述重定位判断指示信息是显式的指示信息的情况下, 在所述重定位 判断指示信息指示需要执行重定位时, 判断需要执行为所述 MRN服务的网 关的重定位; 在没有接收到所述重定位判断指示信息或者所述重定位判断指 示信息指示不需要执行重定位时, 判断不需要执行为所述 MRN服务的网关 的重定位; 或者,
在所述重定位判断指示信息是隐式的指示信息的情况下, 且所述重定位 判断指示信息釆用为所述 MRN服务的网关的地址隐含指示时, 在接收到所 述地址时, 判断需要执行为所述 MRN服务的网关的重定位; 在未接收到所 述地址时, 则判断不需要执行为所述 MRN服务的网关的重定位。
28、 一种宿主基站, 包括: 判断单元和发送单元, 其中:
所述判断单元设置成: 在移动中继节点 MRN切换宿主基站 DeNB的过 程中, 根据重定位判断辅助信息判断是否需要执行为所述 MRN服务的网关 的重定位; 或者, 根据配置信息判断是否需要执行为所述 MRN服务的网关 的重定位; 以及
所述发送单元设置成: 向所述 MRN的移动管理实体 ΜΜΕ发送重定位 判断指示信息。
29、 如权利要求 28所述的宿主基站, 其中:
所述重定位判断辅助信息包括: 用于统计所述 MRN在上一次发生网关 重定位之后发生切换的次数的计数信息; 或者,
在所述 MRN的历史访问小区列表中用于标记所述 MRN发生网关重定 位时的源小区或目标小区的指示信息; 或者,
所述 MRN发生网关重定位时的源小区或目标小区的标识信息; 或者, 所述 MRN在上一次发生网关重定位之后的历史访问小区记录信息。
30、 如权利要求 29所述的宿主基站, 其中:
所述判断单元是设置成以如下方式根据重定位判断辅助信息判断是否需 要执行为所述 MRN服务的网关的重定位:
根据所述重定位判断辅助信息确定所述 MRN在上一次为所述 MRN服 务的网关重定位之后访问的小区的个数; 以及判断所述 MRN在上一次为所 述 MRN服务的网关重定位之后访问的小区的个数是否达到访问小区数量阔 值, 如果达到, 则判断需要执行所述为所述 MRN服务的网关的重定位。
31、 如权利要求 28所述的宿主基站, 其中:
所述发送单元是设置成以如下方式向所述 MRN的 ΜΜΕ发送重定位判 断指示信息:
在为所述 MRN服务的网关内置于 DeNB的系统架构下, 如果所述判断 单元判断需要执行为所述 MRN服务的网关的重定位, 将为所述 MRN服务 的网关的地址信息作为所述重定位判断指示信息发送给所述 MME。
32、 如权利要求 28所述的宿主基站, 还包括: 信息维护单元, 其中: 所述信息维护单元设置成: 在本次切换过程中执行为所述 MRN服务的 网关的重定位后, 在所述重定位判断辅助信息包含所述计数信息时, 将所述 计数信息清零, 其中, 所述计数信息是在所述 MRN每发生一次不需要执行 为所述 MRN服务的网关的重定位的切换过程时 , 所述 MRN的源 DeNB或 目标 DeNB对所述计数信息加 1得到;
在所述重定位判断辅助信息包含所述指示信息时, 在所述 MRN的历史 访问小区列表中的本次切换对应的源小区或目标小区的项目中添加指示信息; 在所述重定位判断辅助信息包含所述标识信息时, 将本次切换对应的源 小区或目标小区的标识信息设置为所述重定位判断辅助信息; 以及
在所述重定位判断辅助信息包含所述 MRN在上一次发生网关重定位之 后的历史访问小区记录信息时, 将所述历史访问小区记录信息清空。
PCT/CN2013/001215 2012-11-21 2013-10-09 一种网关重定位的方法、移动管理实体及宿主基站 WO2014079141A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13857309.2A EP2925052A4 (en) 2012-11-21 2013-10-09 METHOD FOR IMPLEMENTING A GATEWAY, A MOBILE ADMINISTRATION UNIT AND A HOST BASE STATION
US14/646,492 US9807667B2 (en) 2012-11-21 2013-10-09 Method for relocating gateway, mobile management entity and host base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210475631.XA CN103841607A (zh) 2012-11-21 2012-11-21 一种网关重定位的方法、移动管理实体及宿主基站
CN201210475631.X 2012-11-21

Publications (1)

Publication Number Publication Date
WO2014079141A1 true WO2014079141A1 (zh) 2014-05-30

Family

ID=50775446

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/001215 WO2014079141A1 (zh) 2012-11-21 2013-10-09 一种网关重定位的方法、移动管理实体及宿主基站

Country Status (4)

Country Link
US (1) US9807667B2 (zh)
EP (1) EP2925052A4 (zh)
CN (1) CN103841607A (zh)
WO (1) WO2014079141A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6399746B2 (ja) * 2013-12-10 2018-10-03 株式会社Nttドコモ 移動通信システム、無線基地局、無線移動局及び移動通信方法
CN105657836B (zh) 2014-11-14 2021-09-14 索尼公司 用于移动基站的物理小区标识分配的设备和方法
CN105007622A (zh) * 2015-07-07 2015-10-28 大唐移动通信设备有限公司 一种定位方法及装置
EP3363235B1 (en) * 2015-10-14 2020-02-26 Telefonaktiebolaget LM Ericsson (PUBL) Method and nodes for handling network connections
CN109156045A (zh) * 2016-05-12 2019-01-04 华为技术有限公司 访问资源的方法、装置和系统
WO2017193348A1 (zh) * 2016-05-12 2017-11-16 华为技术有限公司 访问资源的方法、装置和系统
EP4138455A1 (en) * 2016-06-22 2023-02-22 Huawei Technologies Co., Ltd. Communication path switching method and device
GB2552845A (en) * 2016-08-12 2018-02-14 Nec Corp Communication system
US10455464B1 (en) * 2017-05-12 2019-10-22 Sprint Spectrum L.P. Dynamic handover threshold adjustment
WO2019246446A1 (en) * 2018-06-21 2019-12-26 Google Llc Maintaining communication and signaling interfaces through a donor base station handover
US10645533B1 (en) * 2018-11-28 2020-05-05 Verizon Patent And Licensing Inc. Detection and remediation of island tracking area codes in a network
US11399320B2 (en) * 2020-08-03 2022-07-26 Blue Ocean Robotics Aps Methods of connecting to communications networks and switching network connectivity
CN114125951A (zh) * 2020-08-25 2022-03-01 华为技术有限公司 一种定位方法及相关装置
US11671910B1 (en) * 2022-03-22 2023-06-06 At&T Intellectual Property I, L.P. Communication network application programming interface promulgation
CN117014809A (zh) * 2022-04-29 2023-11-07 华为技术有限公司 一种通信方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008020788A1 (en) * 2006-08-18 2008-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Intersystem change involving mapping between different types of radio bearers
CN101651950A (zh) * 2009-09-09 2010-02-17 新邮通信设备有限公司 一种长期演进网络中的业务实现方法、设备及系统
WO2011100892A1 (en) * 2010-02-22 2011-08-25 Huawei Technologies Co., Ltd. System and method for communications in communications systems with relay nodes
CN102892155A (zh) * 2012-09-18 2013-01-23 中兴通讯股份有限公司 一种网关重定位的方法及移动性管理实体

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8483174B2 (en) * 2007-04-20 2013-07-09 Qualcomm Incorporated Method and apparatus for providing gateway relocation
CN101998554A (zh) * 2009-08-18 2011-03-30 中兴通讯股份有限公司 基于移动中继的切换方法和移动无线中继系统
CN102006639B (zh) * 2009-09-03 2014-01-01 华为技术有限公司 切换处理方法和系统、中继装置以及基站
CN102457958B (zh) * 2010-10-25 2016-08-03 中兴通讯股份有限公司 一种服务网关重定位的判定方法及系统
CN102469619B (zh) * 2010-11-12 2016-12-28 中兴通讯股份有限公司 一种移动通信系统及其服务网关重定位的方法
US9451508B2 (en) * 2012-05-02 2016-09-20 Lg Electronics Inc. Method and apparatus for transmitting cell information in wireless communication system
US9538450B2 (en) * 2012-08-03 2017-01-03 Futurewei Technologies, Inc. System and method for mobile relay packet gateway relocation for path optimization

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008020788A1 (en) * 2006-08-18 2008-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Intersystem change involving mapping between different types of radio bearers
CN101651950A (zh) * 2009-09-09 2010-02-17 新邮通信设备有限公司 一种长期演进网络中的业务实现方法、设备及系统
WO2011100892A1 (en) * 2010-02-22 2011-08-25 Huawei Technologies Co., Ltd. System and method for communications in communications systems with relay nodes
CN102892155A (zh) * 2012-09-18 2013-01-23 中兴通讯股份有限公司 一种网关重定位的方法及移动性管理实体

Also Published As

Publication number Publication date
CN103841607A (zh) 2014-06-04
EP2925052A4 (en) 2016-01-06
US20150312832A1 (en) 2015-10-29
US9807667B2 (en) 2017-10-31
EP2925052A1 (en) 2015-09-30

Similar Documents

Publication Publication Date Title
WO2014079141A1 (zh) 一种网关重定位的方法、移动管理实体及宿主基站
US10356665B2 (en) Source base station gateway (GW) for releasing resources associated with a mobile device
US10306521B2 (en) Method and apparatus for performing handover of user equipment in wireless communication system supporting dual connectivity
US8687592B2 (en) Method for switching session of user equipment in wireless communication system and system employing the same
JP2019135865A (ja) ネットワークシステムと方法と装置並びにプログラム
EP2783531B1 (en) Method for handing over a mobile relay node
WO2012134116A2 (en) Method and apparatus for performing handover procedure in wireless communication system including mobile relay node
US9445336B2 (en) Method and device for supporting group handover
US20110075633A1 (en) Data Forwarding During Handover in a Self-Backhauled Cell
WO2009006774A1 (en) Interior hangover method in a system
US9503393B2 (en) S-GW relocation and QoS change without mobility
JP6169717B2 (ja) ローカルipアクセス接続解放方法及びmrn
CN106162774B (zh) 跨MeNB切换方法、装置及基站
WO2014044117A1 (zh) 一种网关重定位的方法及移动性管理实体
CN102457958B (zh) 一种服务网关重定位的判定方法及系统
KR101690642B1 (ko) 무선 통신 시스템에서 릴레이 노드에 연결된 단말의 핸드오버 과정에서 순차적 데이터 전달을 지원하는 방법 및 장치
US20130065634A1 (en) Method for communication of terminal and method for communication of base station
EP3031288A1 (en) S-gw relocation and qos change without mobility

Legal Events

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

Ref document number: 13857309

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2013857309

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14646492

Country of ref document: US