WO2017101045A1 - 一种网元选择方法及网元选择器 - Google Patents

一种网元选择方法及网元选择器 Download PDF

Info

Publication number
WO2017101045A1
WO2017101045A1 PCT/CN2015/097601 CN2015097601W WO2017101045A1 WO 2017101045 A1 WO2017101045 A1 WO 2017101045A1 CN 2015097601 W CN2015097601 W CN 2015097601W WO 2017101045 A1 WO2017101045 A1 WO 2017101045A1
Authority
WO
WIPO (PCT)
Prior art keywords
controller
service
network element
base station
session index
Prior art date
Application number
PCT/CN2015/097601
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 EP15910518.8A priority Critical patent/EP3364694B1/en
Priority to PCT/CN2015/097601 priority patent/WO2017101045A1/zh
Priority to CN201580084662.4A priority patent/CN108353352B/zh
Publication of WO2017101045A1 publication Critical patent/WO2017101045A1/zh
Priority to US16/002,023 priority patent/US10349344B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H04W28/0861—Load balancing or load distribution among access entities between base stations
    • H04W28/0862—Load balancing or load distribution among access entities between base stations of same hierarchy level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a network element selection method and a network element selector.
  • the prior art provides a converged controller including the existing core network control network element function, which includes mobility management (for example, implementing a certain MME (Mobility Management Entity) )), session management, billing, and policy management reduce control interfaces and interaction signaling.
  • the converged controller is the control core in the core network architecture.
  • the MME Pool (AM Pool) technology is used in the SAE (System Architecture Evolution) to implement load balancing and disaster recovery backup of the converged controller.
  • SAE System Architecture Evolution
  • the eNodeB (Evolved Node B) is connected to each of the converged controllers in the pool group.
  • the eNodeB is based on the capacity and current of each converged controller.
  • the load capacity to select the appropriate fusion controller for the accessed UE to achieve load balancing.
  • the existing core network architecture can only achieve limited load balancing within the scope of the converged controller to which the eNodeB is connected.
  • the future network architecture as the network capacity continues to expand, it needs to be at a higher level.
  • direct communication between the eNodeB and the converged controller to dynamically obtain feedback on the load situation is relatively expensive;
  • the network element selection method is only applicable to the selection of the converged controller for the UE access, and it is difficult to implement a more flexible and dynamic load balancing strategy according to the actual load situation.
  • the present invention provides a network element selection method and a network element selector, which can provide load balancing functions by deploying a network element selector.
  • a first aspect of the present invention provides a network element selection method, including:
  • the network element selector receives a request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, the service chain header includes a session index, the session index is empty, or the session index is described by the service.
  • the network element selector sends the request message to the controller providing the service to enable the controller providing the service to serve the UE.
  • the network element selector determines, according to the session index, a controller that provides a service, including:
  • the network element selector determines that the controller providing the service is the first controller.
  • the network element selector determines, according to the session index, a controller that provides a service, including:
  • the network element selector determines a controller that provides a service according to the session index and attribute information of each controller, and the attribute information of each controller is location information and/or load capability information of the respective controllers.
  • the network element selector determines, according to the session index and attribute information of each controller, a service providing control , including:
  • the network element selector identifies that the session index is empty
  • the network element selector obtains location information and/or load capability information of the respective controllers
  • the network element selector acquires location information of the base station
  • the distance and/or load capability information determines the controller that provides the service.
  • the network element selector determines, according to the session index and attribute information of each controller, a service providing control , including:
  • the network element selector obtains, from the session index, a label of a controller that allocates the session index Identifying, and identifying that the identifier of the controller that allocates the session index is an identifier of the first controller;
  • the network element selector acquires location information and/or load capability information of the first controller
  • the network element selector acquires location information of the base station
  • the distance and/or load capability information determines whether the first controller is used to provide the service
  • the network element selector determines that the controller providing the service is the first controller
  • the network element selector obtains location information and/or load capability information of the controller other than the first controller
  • the network element selector determines, between the base station and the controller other than the first controller, according to location information of the base station and location information of the controller other than the first controller And determining a service providing service according to a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller Controller.
  • a second aspect of the present invention provides a network element selector, including:
  • a receiving module configured to receive a request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, where the service chain header includes a session index, the session index is empty, or the session index is used by the service center. Determining the first controller assignment of the UE;
  • a determining module configured to determine, according to a session index received by the receiving module, a controller that provides a service
  • a sending module configured to send the request message received by the receiving module to the controller that provides the service determined by the determining module, so that the controller providing the service serves the UE.
  • the determining module includes:
  • An identifying unit configured to obtain, from the session index, an identifier of a controller that allocates the session index, and identify that the identifier of the controller that allocates the session index is an identifier of the first controller;
  • a determining unit configured to determine that the controller providing the service is the first controller.
  • the determining module is specifically configured to:
  • the attribute information of each controller is location information and/or load capability information of the respective controllers.
  • the determining module includes:
  • the identifying unit is further configured to identify that the session index is empty;
  • An acquiring unit configured to acquire location information and/or load capability information of each controller
  • the acquiring unit is further configured to acquire location information of the base station
  • the determining unit is further configured to determine a distance between the base station and each controller according to location information of the base station and location information of each controller, according to the base station and each controller
  • the distance and/or load capacity information determines the controller that provides the service.
  • the determining module includes:
  • the identifying unit is further configured to obtain, from the session index, an identifier of a controller that allocates the session index, and identify that an identifier of a controller that allocates the session index is an identifier of the first controller;
  • the obtaining unit is further configured to acquire location information and/or load capability information of the first controller
  • the acquiring unit is further configured to acquire location information of the base station
  • a determining unit configured to determine a distance between the base station and each controller according to location information of the base station and location information of the first controller, according to between the base station and each of the controllers
  • the distance and/or load capability information determines whether the first controller is used to provide the service
  • the determining unit is further configured to: when the determination result of the determining unit is yes, determine that the controller that provides the service is the first controller;
  • the acquiring unit is further configured to: when the determination result of the determining unit is negative, acquire location information and/or load capability information of the controller other than the first controller;
  • the determining unit is further configured to determine, according to the location information of the base station and the location information of the controller other than the first controller, the base station and the controller other than the first controller a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller The controller of the service.
  • a third aspect of the present invention provides a network element selector, where the network element selector includes a communication bus and a transmission Into the device, the output device, and the processor, wherein:
  • the communication bus is configured to implement connection communication between the input device, the output device, and the processor
  • the input device is configured to receive a request message sent by a base station, where the request message includes information of a user equipment UE and a service chain header, where the service chain header includes a session index, the session index is empty, or the session index is Serving the first controller assignment of the UE;
  • the processor configured to determine, according to the session index, a controller that provides a service
  • the output device is configured to send the request message to the controller that provides the service, so that the controller that provides the service serves the UE.
  • the processor determines, according to the session index, a controller that provides a service, specifically, performing the following steps:
  • the processor determines, according to the session index, a controller that provides a service, and specifically performs the following steps:
  • the processor determines, according to the session index and attribute information of each controller, a controller that provides a service, Specifically, perform the following steps:
  • the processor determines, according to the session index and attribute information of each controller, The controller of the service, the specific steps are as follows:
  • Determining a distance between the base station and the respective controllers according to location information of the base station and location information of the first controller, according to a distance and/or load between the base station and the respective controllers
  • the capability information determines whether the first controller is used to provide a service
  • Determining a distance between the base station and the controller other than the first controller according to location information of the base station and location information of the controller other than the first controller, according to the A controller that provides a service is determined by a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller.
  • the network element selector receives the request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, the service chain header includes a session index, and the session index is empty or the session index Assigned by a first controller serving the UE; the network element selector determines a controller that provides a service according to the session index; the network element selector sends the request message to the controller that provides the service, So that the controller providing the service serves the UE.
  • the independent network element selector belongs to the core network element, and the cost of obtaining the current attribute status of each controller is small, so system consumption can be reduced to support more dynamic and flexible controller load balancing for the whole core network.
  • Figure 1 is a diagram of a conventional core network structure
  • FIG. 2 is a schematic flowchart of an embodiment of a network element selection method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a service chain header according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of another embodiment of a network element selection method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a system according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart diagram of another embodiment of a network element selection method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network element selector according to an embodiment of the present invention.
  • FIG. 8 is another schematic structural diagram of a network element selector according to an embodiment of the present invention.
  • FIG. 9 is another schematic structural diagram of a network element selector according to an embodiment of the present invention.
  • the embodiment of the invention provides a network element selection method and a network element selector, which can provide a load balancing function by deploying a network element selector.
  • the network element selector may be a network element selector, and the controller may be a fusion controller.
  • the following uses the network element selector as the network element selector and the controller as the fusion controller.
  • the embodiment of the present invention uses the network element selector to receive the request message sent by the base station, reads the session index carried in the service chain header of the request message sent by the base station, and determines to provide the session index according to the session index and the pre-acquired attribute information of each fusion controller.
  • the fusion controller for the service.
  • the device equipment involved is as follows:
  • the UE includes a mobile phone, a smart terminal, a multimedia device, a streaming media device, a mobile internet device (MID), a wearable device (such as a smart watch (such as iwatch), and a smart device. Hand ring, pedometer, etc.) or other terminal equipment that can communicate with the base station.
  • a mobile phone a smart terminal
  • a multimedia device a streaming media device
  • MID mobile internet device
  • a wearable device such as a smart watch (such as iwatch)
  • a smart device such as iwatch
  • Hand ring, pedometer, etc. or other terminal equipment that can communicate with the base station.
  • a base station a radio base station in an LTE (Long Term Evolution) network, is the only network element of the LTE radio access network and is responsible for all functions related to the air interface.
  • LTE Long Term Evolution
  • the controller also known as the Converged Controller, is the control network element in the core network architecture and is responsible for handling all control signaling, including mobility management, session management, policy and billing management.
  • the network element selector can be deployed in a single service domain to implement the selection and load balancing of the converged controllers in the service domain. It can also be deployed independently of the service domain, and is responsible for implementing the selection and load balancing functions of the converged controller across the service domain.
  • a user database (Database Sever, DB Server for short) is used to store related data of the user, including status information and bearer information.
  • the user data local cache (Local Data Cache) synchronizes the user context data to the local cache to improve the data access efficiency of the converged control plane.
  • the UE and the converged controller In most enterprise applications and e-commerce applications, the UE and the converged controller often go through multiple interactions to complete a transaction or a service. On the one hand, these interactions are closely related to the user's identity. On the other hand, when the fusion controller performs a certain step of these interaction processes, it is often necessary to know the processing result of the previous interaction process or the result of the interaction process of the previous steps. Therefore, application requests related to this UE often need to be forwarded to a fusion controller, but cannot be forwarded by the network element selector to different fusion controllers for processing. In order to meet the above requirements, the network element selector needs to identify the association between the UE and the fusion controller.
  • FIG. 2 is a schematic flowchart diagram of an embodiment of a network element selection method according to an embodiment of the present invention.
  • the embodiments of the present invention are applicable to related requests periodically sent after the UE accesses or accesses the MME.
  • a network element selection method may include the following steps.
  • the network element selector receives a request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, where the service chain header includes a session index, the session index is empty, or the session index is served by The first controller of the UE is assigned.
  • the UE sends a request to the base station, and the base station identifies that the received request is the information of the UE, Set the session index corresponding to the UE.
  • the session index is empty or assigned by the first controller serving the UE. If the session index is empty, indicating that the current request of the UE is access, there is no fusion controller serving the UE; if the session index is allocated by the first controller serving the UE, the session index stored in the session index is allocated.
  • the identifier of the controller is the identifier of the first controller, indicating that the current base station learns that the fusion controller currently serving the UE is the first controller.
  • the base station sets the session index according to the current access situation of the UE, carries the session index by the service chain header, generates a request message according to the service chain header and the information of the UE, and finally sends the request message to the network element selector.
  • the request message generated by the base station may be encapsulated by a Service Function Chaining (SFC).
  • SFC Service Function Chaining
  • the service chain header can be set as shown in FIG. 3, and the session index is saved by using the Service Path Identifier field in the service chain header, thereby implementing the session hold function.
  • the service chain header includes Metadata Length, Protocol Type, Service Index, and Optional Metadata TLVs (optional metadata threshold), etc., which appear in Figure 3.
  • Other parameters are part of the service chain header in the prior art, and are not described in this embodiment.
  • the network element selector determines, according to the session index, a controller that provides a service.
  • the network element selector determines, according to the session index, a fusion controller that provides a service.
  • the network element selector may further determine a fusion controller that provides a service according to the session index and attribute information of each fusion controller.
  • the network element selector obtains attribute information of each fusion controller, and the attribute information of each fusion controller includes location information and/or load capability information of each fusion controller to obtain location deployment and load status of each fusion controller.
  • the network element selector determines the fusion controller that provides the service by combining the session index and the attribute information of each fusion controller.
  • the network element selector sends the request message to the controller that provides the service, so that the controller that provides the service serves the UE.
  • the network element selector removes the service chain header, and forwards the request message carrying the information of the UE to the convergence controller that provides the service, so that the convergence controller that provides the service receives the information of the UE forwarded by the network element selector, and starts.
  • the specific operation of serving the UE is the specific operation of serving the UE.
  • the fusion controller providing the service can be in the corresponding service domain.
  • the Local Data Cache (Local Data Cache) establishes or updates the context for the UE, acquires related data of the UE from the User Context Database (DB Server), and allocates a session index to the UE.
  • the service providing converged controller then sends the response information about the UE to the network element selector, and the network element selector forwards the information to the base station, so that the base station knows that the converged controller determined by the network element selector serves the UE.
  • the response information may be an S1 Application Protocol (S1-AP) message, where the message includes a Controller S1-AP UE ID, and the Controller S1-AP UE ID is used as a session index, and the base station reads the information.
  • the Controller S1-AP UE ID is used to obtain a session index, thereby saving the session index as a UE context, and continuing the interaction process of the UE.
  • the GUTI parameter or the controller ID (Controller ID) allocated to the UE by the controller providing the service is used as a session index, and the UE notifies the base station to obtain the session index of the service provided by the base station, thereby The session index is saved as the UE context, and the interaction process of the UE is continued.
  • the network element selector receives the request message sent by the base station, where the request message includes the information of the user equipment UE and the service chain header, the service chain header includes a session index, and the session index is empty or the The session index is allocated by a first controller serving the UE; the network element selector determines a controller providing a service according to the session index; the network element selector sends the request to the controller providing the service a message to cause the controller providing the service to serve the UE.
  • the independent network element selector belongs to the core network element, and the cost of obtaining the current attribute status of each controller is small, so system consumption can be reduced to support more dynamic and flexible controller load balancing for the whole core network.
  • FIG. 4 is a schematic flowchart diagram of another embodiment of a network element selection method according to an embodiment of the present invention.
  • the embodiment of the present invention is applicable to requesting access that is periodically sent after the UE accesses or accesses the MME.
  • the initial access of the UE is taken as an example for description.
  • the network element selector receives a request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, where the service chain header includes a session index, the session index is empty, or the session index is served by The first controller of the UE is assigned.
  • the UE sends the information of the UE to the base station, where the information of the UE is the information of the UE, And including the UE's International Mobile Subscriber Identity (IMSI) to uniquely identify the UE.
  • IMSI International Mobile Subscriber Identity
  • the base station identifies, according to the request message, that the received message is information of the UE, and sets a session index corresponding to the UE. Since the UE is the initial access, there is currently no converged controller serving the UE, so the base station sets the session index to null.
  • the base station carries the session index by the service chain header, generates a request message according to the service chain header and the information of the UE, and finally sends the request message to the network element selector.
  • the session index may be set to be empty (ie, the value of the controller's ID (Controller ID) is 0) or the identifier of the first controller of the currently serving UE.
  • the network element selector obtains, from the session index, an identifier of a controller that allocates the session index, and identifies that the identifier of the controller that allocates the session index is an identifier of the first controller. .
  • the network element selector may allocate the session index.
  • the identifier of the controller is identified, and the identifier of the controller that allocates the session index is identified as an identifier of the first controller.
  • the network element selector determines that the controller that provides the service is the first controller.
  • the network element selector may directly determine that the controller that provides the service is the first controller, and notify the first controller to continue to serve the UE.
  • the network element selector identifies that the session index is empty.
  • the network element selector determines, according to the attribute information of each controller, a controller that provides a service, and the attribute information of each controller is the respective control. Location information and/or load capability information. Specifically, after receiving the request message sent by the base station, the network element selector obtains the session index from the Service Path ID field in the service chain header of the request message, and identifies the value of the identifier of the controller in the session index, if the controller is identified. If the value of the identifier is 0, the session index is empty, indicating that there is currently no converged controller serving the UE.
  • the network element selector acquires location information and/or load capability information of the respective controllers.
  • the network element selector since no fusion controller currently serves the UE, the network element selector needs to allocate a fusion controller to the UE.
  • the NE selector can obtain the location of the fusion controller in each service domain. Information and/or load capability information to obtain location deployment and/or load conditions for each fusion controller.
  • the network element selector can determine the convergence controller serving the UE by using the location information of each fusion controller. By knowing the location information of each fusion controller, the specific location of each fusion controller can be obtained to find the closest distance to the UE or can be A converged controller in which the UE communicates within its own service domain.
  • the network element selector can also determine the convergence controller serving the UE by using the load capability information of each fusion controller, and the load condition can know the current load pressure of each fusion controller to identify the fault fusion controller and cross-domain shielding.
  • the change of the fault fusion controller affects other network elements, and the fusion controller that distributes the minimum load pressure in the fusion controller whose load pressure meets the load pressure threshold serves the UE.
  • an automatic scaling strategy is implemented based on the load situation.
  • the network element selector can also comprehensively utilize the location information of each of the fusion controllers and the load capability information to determine a fusion controller serving the UE. For example, the network element selector can select a distance from the UE that is less than a preset distance value and the load capability is lower than a preset.
  • the load pressure fusion controller serves the UE.
  • the network element selector acquires location information of the base station.
  • the network element selector determines the convergence controller serving the UE according to the location information of each of the fusion controllers or the location information and the load capability information of each of the fusion controllers, the network element selector needs to acquire the location of the base station. Information to determine the actual physical distance between the base station and each of the fusion controllers.
  • the network element selector determines a distance between the base station and each controller according to location information of the base station and location information of each controller, according to the base station and each controller.
  • the distance and/or load capacity information determines the controller that provides the service.
  • the network element selector calculates the actual physical distance between the base station and each of the fusion controllers according to the location information of the base station and the location information of each of the fusion controllers, and then according to the base station and each of the fusion controllers.
  • the actual physical distance and/or load capacity information of each of the fusion controllers determines the fusion controller that provides the service.
  • the network element selector sends the request message to the controller that provides the service, so that the controller that provides the service serves the UE.
  • the network element selector removes the service chain header, and forwards the request message carrying the information of the UE to the convergence controller that provides the service, so that the convergence controller that provides the service receives the network element selector for forwarding.
  • the request message informs the base station to provide the service by analyzing the information of the UE.
  • the service providing converged controller may establish a context for the UE in the Local Data Cache of the corresponding service domain, and acquire related data of the UE from the DB server. Session Data is stored in the DB Server. Different fusion controllers may respectively have different service domains.
  • the service domain 1 may include at least one fusion controller
  • the service domain 2 may include at least one fusion control other than the convergence controller of the service domain 1.
  • Device may include at least one fusion controller, and the service domain 2 may include at least one fusion control other than the convergence controller of the service domain 1.
  • the convergence controller that provides the service sends the response information about the UE to the network element selector, and the network element selector forwards the information to the base station, so that the base station learns that the fusion controller determined by the network element selector is the UE. service.
  • the response information may be a Controller S1-AP UE ID, and the Controller S1-AP UE ID is used as a session index, and the base station obtains a session index by reading the Controller S1-AP UE ID, thereby The index is saved as the UE context, and the interaction process of the UE is continued.
  • the GUTI parameter or the controller ID (Controller ID) allocated to the UE by the controller providing the service is used as a session index, and the UE notifies the base station to obtain the session index of the service provided by the base station, thereby The session index is saved as the UE context, and the interaction process of the UE is continued.
  • the network element selector receives the request message sent by the base station, where the request message includes the information of the user equipment UE and the service chain header, the service chain header includes a session index, and the session index is empty or the The session index is allocated by a first controller serving the UE; the network element selector determines a controller providing a service according to the session index; the network element selector sends the request to the controller providing the service a message to cause the controller providing the service to serve the UE.
  • the independent network element selector belongs to the core network element, and the cost of obtaining the current attribute status of each controller is small, so system consumption can be reduced to support more dynamic and flexible controller load balancing for the whole core network.
  • FIG. 6 is a schematic flowchart diagram of another embodiment of a network element selection method according to an embodiment of the present invention.
  • the embodiment of the present invention is applicable to a request that is periodically sent after the UE accesses or accesses the MME.
  • the request sent periodically after the UE accesses the MME is taken as an example for description.
  • the network element selector receives a request message sent by a base station, where the request message includes a user equipment.
  • the UE sends a request to the base station, where the request may be NAS (Non-Access Stratum) signaling.
  • the base station reads the Globally Unique Temporary UE Identity (GUTI) parameter through the NAS signaling or the Controller S1-AP UE ID sent by the pre-stored NE selector to identify the Controller ID of the first controller.
  • the first controller is a converged controller that previously served the UE, and the base station carries the identifier of the first controller by the service chain header, and generates a request message according to the service chain header and the NAS signaling sent by the UE, and finally the base station will request the message. It is sent to the network element selector, which is not limited in this embodiment.
  • the session index is allocated by the first controller serving the UE, and the identifier of the controller that allocates the session index stored in the session index is the identifier of the first controller.
  • the network element selector obtains, from the session index, an identifier of a controller that allocates the session index, and identifies that an identifier of a controller that allocates the session index is an identifier of the first controller.
  • the network element selector after receiving the request message, identifies the identifier of the first controller from the Service Path ID field in the service chain header of the request message, indicating that the current convergence controller serving the UE is the first controller. .
  • the network element selector acquires location information and/or load capability information of the first controller.
  • the network element selector may obtain location information and/or load capability information of the first controller to obtain a location deployment of the first controller and / or load situation.
  • the network element selector can determine the fusion controller serving the UE by using the location information of the first controller, and obtain the specific location of the first controller by acquiring the location information of the first controller.
  • the network element selector can also determine the load condition of the first controller by using the load capability information of the first controller, and the current load pressure of the first controller can be known by the load condition to identify whether the first controller is faulty.
  • the first controller is shielded if the first controller fails.
  • the network element selector can also comprehensively utilize the location information of the first controller and the load capability information to determine whether it can continue to serve the UE.
  • the network element selector acquires location information of the base station.
  • the network element selector determines whether the first controller can continue to serve the UE.
  • the network element selector also needs to obtain location information of the base station to determine the actual physical distance between the base station and the first controller.
  • the network element selector determines a distance between the base station and each controller according to location information of the base station and location information of the first controller, according to the base station and each controller.
  • the distance between and/or the load capability information determines whether the first controller is used to provide the service.
  • the network element selector calculates an actual physical distance between the base station and the first controller according to the location information of the base station and the location information of the first controller, and then according to the base station and the first controller.
  • the actual physical distance and/or the load capacity information of the first controller determines whether the first controller can continue to serve the UE. If the determination is yes, step S605 is performed, and if the determination is no, step S606 is executed.
  • the network element selector determines that the controller that provides the service is the first controller.
  • the network element selector determines, according to the actual physical distance between the base station and the first controller and/or the load capacity information of the first controller, the first controller is still the most suitable for the UE to control the convergence control. Then, it is determined that the first controller can continue to serve the UE.
  • the network element selector acquires location information and/or load capability information of a controller other than the first controller.
  • the network element selector determines, according to the actual physical distance between the base station and the first controller and/or the load capability information of the first controller, that the first controller is not suitable for serving the UE. Since the first controller belongs to the service domain, and the network element selector is independent of the service domain, and each of the fusion controllers belongs to a different service domain, the network element selector can shield the first controller, and obtain the The location information and/or load capability information of the fusion controller outside the controller is obtained for location deployment and/or load conditions of other fusion controllers.
  • the network element selector determines, according to the location information of the base station and the location information of the controller other than the first controller, the base station and the controller other than the first controller. a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller The controller of the service.
  • the network element selector calculates the actual physical distance between the base station and the fusion controllers outside the fusion controller according to the location information of the base station and the location information of other fusion controllers, and then according to the base station and other fusion control. Actual physical distance between devices and / or load of other fusion controllers Capability information, which is determined from other fusion controllers as a converged controller serving the UE.
  • the network element selector sends the request message to the controller that provides the service, so that the controller that provides the service serves the UE.
  • the network element selector determines that the convergence controller that provides the service is still the first controller
  • the network element selector removes the service chain header, and forwards the NAS signaling to the first controller, so that the A controller receives the NAS signaling forwarded by the network element selector, and notifies the base station to provide the service by analyzing the NAS signaling.
  • the first controller may update the context of the UE and update related data of the UE acquired from the DB Server in the Local Data Cache of the corresponding service domain.
  • the first controller then sends response information about the UE to the network element selector, which is forwarded by the network element selector to the base station, so that the base station knows that the first controller continues to serve the UE.
  • the process of obtaining the session index by the base station refer to step S407 in FIG. 4 of the embodiment, and details are not described in this embodiment.
  • the network element selector determines that the convergence controller that provides the service is the convergence controller (for example, the second controller) in the other convergence controller
  • the network element selector removes the service chain header and forwards the NAS signaling. And to the second controller, so that the second controller receives the NAS signaling forwarded by the network element selector, and notifies the base station to provide the service by analyzing the NAS signaling.
  • the second controller may save the session index as the UE context and related data of the UE acquired from the DB server in the Local Data Cache of the corresponding service domain.
  • the second controller allocates a new GUTI parameter to the UE, initiates a GUTI reassignment command, and sends the GUTI reassignment command and the Controller S1-AP UE ID of the second controller to the network element selector, and the network element selects
  • the device forwards to the base station to let the base station know that the second controller continues to serve the UE.
  • the controller S1-AP UE ID includes the identifier of the second controller, and the base station learns that the fusion controller that provides the service has been changed to the second controller by reading the Controller S1-AP UE ID, thereby reallocating according to the received GUTI.
  • the command updates the pre-saved GUTI parameter, updates the session index, changes the identifier of the first controller to the identifier of the second controller, and continues the interaction process of the UE.
  • the GUTI parameter allocated by the second controller to the UE or the identifier of the second controller (Controller ID) is used as a session index, and the UE notifies the base station to acquire the session index, thereby updating the context of the UE, and continuing the UE. Interaction process.
  • the base station sends the NAS signaling to the network element selector, and the network element selector reads the value of the Controller ID in the service chain header as the identifier of the first controller, and if the first controller is no longer suitable, Continue to provide services, such as the first controller overload, failure, etc., then decide to be the UE Selecting a new converged controller and forwarding signaling, the new converged controller initiates the GUTI reassignment process and continues the interworking process to provide uninterrupted service for the UE and implement the session hold function.
  • FIG. 7 is a schematic structural diagram of a network element selector according to an embodiment of the present invention.
  • the network element selector shown in FIG. 7 includes a receiving module 700, a determining module 701, and a sending module 702.
  • the receiving module 700 is configured to receive a request message sent by the base station, where the request message includes information of the user equipment UE and a service chain header, where the service chain header includes a session index, the session index is empty, or the session index is served by The first controller of the UE is allocated;
  • a determining module 701 configured to determine, according to the session index received by the receiving module 700, a controller that provides a service
  • the sending module 702 is configured to send, by the controller that provides the service to the determining module 701, the request message that is received by the receiving module, so that the controller that provides the service serves the UE.
  • the determining module 701 includes an identifying unit 7011 and a determining unit 7013:
  • the identifying unit 7011 is configured to obtain, from the session index, an identifier of a controller that allocates the session index, and identify that the identifier of the controller that allocates the session index is an identifier of the first controller;
  • the determining unit 7013 is configured to determine that the controller that provides the service is the first controller.
  • the determining module is specifically configured to:
  • the determining module 701 further includes an obtaining unit 7012:
  • the identifying unit 7011 is further configured to identify that the session index is empty;
  • An obtaining unit 7012 configured to acquire location information and/or load capability information of each controller
  • the acquiring unit 7012 is further configured to acquire location information of the base station
  • a determining unit 7013 configured to determine a distance between the base station and each controller according to location information of the base station and location information of each controller, according to between the base station and each controller
  • the distance and/or load capability information determines the controller that provides the service.
  • the determining module 701 further includes a determining unit 7014:
  • the identifying unit 7011 is further configured to: obtain an identifier of a controller that allocates the session index from the session index, and identify that an identifier of a controller that allocates the session index is an identifier of the first controller;
  • the acquiring unit 7012 is further configured to acquire location information and/or load capability information of the first controller.
  • the acquiring unit 7012 is further configured to acquire location information of the base station
  • the determining unit 7014 is configured to determine, according to location information of the base station and location information of the first controller, a distance between the base station and each controller, according to the base station and each controller The distance and/or load capability information determines whether the first controller is used to provide the service;
  • the determining unit 7013 is further configured to: when the determination result of the determining unit 7014 is YES, determine that the controller that provides the service is the first controller;
  • the obtaining unit 7012 is further configured to: when the determining result of the determining unit 7014 is negative, acquiring location information and/or load capability information of the controller other than the first controller;
  • the determining unit 7013 is further configured to determine, according to the location information of the base station and the location information of the controller other than the first controller, the base station and the control other than the first controller The distance between the devices is determined according to a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller The controller that provides the service.
  • the network element selector receives the request message sent by the base station, where the request message includes the information of the user equipment UE and the service chain header, the service chain header includes a session index, and the session index is empty or the The session index is allocated by a first controller serving the UE; the network element selector determines a controller providing a service according to the session index; the network element selector sends the request to the controller providing the service a message to cause the controller providing the service to serve the UE.
  • the independent network element selector belongs to the core network element, and the cost of obtaining the current attribute status of each controller is small, so system consumption can be reduced to support more dynamic and flexible controller load balancing for the whole core network.
  • FIG. 9 is another schematic structural diagram of a network element selector according to an embodiment of the present invention.
  • the mobile terminal of this embodiment includes a communication bus 900, an input device 901, an output device 902, and a processor 903.
  • the number of processors 903 of the network element selector may be one or more, in FIG. A processor is an example), where:
  • the communication bus 900 is configured to implement connection communication between the input device, the output device, and the processor 903;
  • the input device 901 is configured to receive a request message sent by a base station, where the request message includes information of a user equipment UE and a service chain header, where the service chain header includes a session index, and the session index is empty or the session index Assigned by a first controller that services the UE;
  • the processor 903 is configured to determine, according to the session index, a controller that provides a service
  • the output device 902 is configured to send the request message to the controller that provides the service, so that the controller that provides the service serves the UE.
  • the processor 903 determines, according to the session index, a controller that provides a service, specifically, to perform the following steps:
  • the processor 903 determines, according to the session index, a controller that provides a service, and specifically performs the following steps:
  • the processor 903 determines, according to the session index and attribute information of each controller, a controller that provides a service, and specifically performs the following steps:
  • Determining a distance between the base station and the respective controllers according to location information of the base station and location information of the respective controllers, according to a distance between the base station and the respective controllers and/or Or load capacity information to determine the controller that provides the service.
  • the processor 903 determines, according to the session index and attribute information of each controller, a controller that provides a service, and specifically performs the following steps:
  • Determining a distance between the base station and the respective controllers according to location information of the base station and location information of the first controller, according to a distance and/or load between the base station and the respective controllers
  • the capability information determines whether the first controller is used to provide a service
  • Determining a distance between the base station and the controller other than the first controller according to location information of the base station and location information of the controller other than the first controller, according to the A controller that provides a service is determined by a distance between the base station and the controller other than the first controller and/or load capacity information of the controller other than the first controller.
  • the network element selector receives the request message sent by the base station, where the request message includes the information of the user equipment UE and the service chain header, the service chain header includes a session index, and the session index is empty or the The session index is allocated by a first controller serving the UE; the network element selector determines a controller providing a service according to the session index; the network element selector sends the request to the controller providing the service a message to cause the controller providing the service to serve the UE.
  • the independent network element selector belongs to the core network element, and the cost of obtaining the current attribute status of each controller is small, so system consumption can be reduced to support more dynamic and flexible controller load balancing for the whole core network.
  • Computer readable media includes both computer storage media and communication media.
  • Communication media includes any medium that facilitates the transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • the desired program code and any other medium that can be accessed by the computer may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixing of the associated media.
  • coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixing of the associated media.
  • a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Landscapes

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

Abstract

本发明公开了一种网元选择方法及网元选择器，包括：网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。本申请通过部署网元选择器，提供负载均衡的功能。

Description

一种网元选择方法及网元选择器 技术领域
本发明涉及通信技术领域，尤其涉及一种网元选择方法及网元选择器。
背景技术
随着移动互联网业务的发展、企业网业务的丰富，以及多种制式的移动接入网络的融合，对核心网架构提出了越来越高的要求。为了进一步简化核心网络架构、提高网络效率，现有技术提供了包含现有的核心网控制网元功能的融合控制器，其包括移动性管理(例如实现某个MME(Mobility Management Entity，移动管理实体)的功能)、会话管理、计费与策略管理等，减少了控制接口及交互信令。融合控制器是核心网架构中的控制核心，SAE(System Architecture Evolution，系统架构演进)中采用MME池组(MME Pool)化技术来实现融合控制器的负载均衡和容灾备份。现有的池组的组网方式如图1所示，eNodeB(Evolved Node B，演进型Node B)同时连接到池组内的每一个融合控制器，eNodeB根据每个融合控制器的容量和当前的负载能力来为接入的UE选择合适的融合控制器，从而达到负载均衡的目的。
然而，一方面，现有的核心网架构只能在eNodeB所连接的融合控制器范围内实现有限的负载均衡，对于未来的网络架构，随着网络容量的不断扩大增长，需要在更高的层次实现负载均衡和容灾备份，以提高网络的资源利用率和可靠性；另一方面，eNodeB与融合控制器之间需要直接通信以动态获取负载情况的反馈，其代价相对较高；此外，当前的网元选择方法只适用于UE接入时为其选择融合控制器，难以依据实际的负载情况,实现更为灵活动态的负载均衡策略。
发明内容
本发明在于提供一种网元选择方法及网元选择器，可通过部署网元选择器，提供负载均衡的功能。
本发明第一方面提供一种网元选择方法，包括：
网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
所述网元选择器根据所述会话索引确定提供服务的控制器；
所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
结合第一方面的实现方式，在第一方面的第一种可能的实现方式中，所述网元选择器根据所述会话索引确定提供服务的控制器，包括：
所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
所述网元选择器确定提供服务的控制器为所述第一控制器。
结合第一方面的实现方式，在第一方面的第二种可能的实现方式中，所述网元选择器根据所述会话索引确定提供服务的控制器，包括：
所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，包括：
所述网元选择器识别出所述会话索引为空；
所述网元选择器获取所述各个控制器的位置信息和/或负载能力信息；
所述网元选择器获取所述基站的位置信息；
所述网元选择器根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
结合第一方面的第二种可能的实现方式，在第一方面的第四种可能的实现方式中，所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，包括：
所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标 识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
所述网元选择器获取所述第一控制器的位置信息和/或负载能力信息；
所述网元选择器获取所述基站的位置信息；
所述网元选择器根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
若判断为是，则所述网元选择器确定提供服务的控制器为所述第一控制器；
若判断为否，则所述网元选择器获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
所述网元选择器根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
本发明第二方面提供一种网元选择器，包括：
接收模块，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
确定模块，用于根据所述接收模块接收的会话索引确定提供服务的控制器；
发送模块，用于向所述确定模块确定的提供服务的控制器发送所述接收模块接收的所述请求消息，以使所述提供服务的控制器为所述UE服务。
结合第二方面的实现方式，在第二方面的第一种可能的实现方式中，所述确定模块包括：
识别单元，用于从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
确定单元，用于确定提供服务的控制器为所述第一控制器。
结合第二方面的实现方式，在第二方面的第二种可能的实现方式中，所述确定模块具体用于：
根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所 述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
结合第二方面的第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述确定模块包括：
所述识别单元，还用于识别出所述会话索引为空；
获取单元，用于获取所述各个控制器的位置信息和/或负载能力信息；
所述获取单元，还用于获取所述基站的位置信息；
所述确定单元，还用于根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
结合第二方面的第二种可能的实现方式，在第二方面的第四种可能的实现方式中，所述确定模块包括：
所述识别单元，还用于从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
所述获取单元，还用于获取所述第一控制器的位置信息和/或负载能力信息；
所述获取单元，还用于获取所述基站的位置信息；
判断单元，用于根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
所述确定单元，还用于当所述判断单元的判断结果为是时，则确定提供服务的控制器为所述第一控制器；
所述获取单元，还用于当所述判断单元的判断结果为否时，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
所述确定单元，还用于根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
本发明第三方面提供一种网元选择器，所述网元选择器包括通信总线、输 入装置、输出装置以及处理器，其中：
所述通信总线，用于实现所述输入装置、所述输出装置、所述处理器之间的连接通信；
所述输入装置，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
所述处理器，用于根据所述会话索引确定提供服务的控制器；
所述输出装置，用于向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
结合第三方面的实现方式，在第三方面的第一种可能的实现方式中，所述处理器根据所述会话索引确定提供服务的控制器，具体用于执行如下步骤：
从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
确定提供服务的控制器为所述第一控制器。
结合第三方面的实现方式，在第三方面的第二种可能的实现方式中，所述处理器根据所述会话索引确定提供服务的控制器，具体执行如下步骤：
根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
结合第三方面的第二种可能的实现方式，在第三方面的第三种可能的实现方式中，所述处理器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，具体执行如下步骤：
识别出所述会话索引为空；
获取所述各个控制器的位置信息和/或负载能力信息；
获取所述基站的位置信息；
根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
结合第三方面的第二种可能的实现方式，在第三方面的第四种可能的实现方式中，所述处理器根据所述会话索引以及各个控制器的属性信息确定提供服 务的控制器，具体执行如下步骤：
从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
获取所述第一控制器的位置信息和/或负载能力信息；
获取所述基站的位置信息；
根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
若判断为是，则确定提供服务的控制器为所述第一控制器；
若判断为否，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
通过本发明，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。独立网元选择器属于核心网网元，获取各个控制器的当前属性状况的代价较小，因此能够减少系统消耗，以支持面向全核心网的、更为动态灵活的控制器负载均衡。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是现有的核心网结构图；
图2是本发明实施例的一种网元选择方法的一实施例的流程示意图；
图3是本发明实施例的业务链头的示意图；
图4是本发明实施例的一种网元选择方法的另一实施例的流程示意图；
图5是本发明实施例的一种系统示意图；
图6是本发明实施例的一种网元选择方法的另一实施例的流程示意图；
图7是本发明实施例的一种网元选择器的结构示意图；
图8是本发明实施例的一种网元选择器的另一种结构示意图；
图9是本发明实施例的一种网元选择器的另一种结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供了一种网元选择方法及网元选择器，可通过部署网元选择器，提供负载均衡的功能。
本发明实施例涉及的网元选择器可为网元选择器，控制器则可为融合控制器。下面将以网元选择器作为网元选择器、将控制器作为融合控制器进行具体说明。
本发明实施例利用网元选择器接收基站发送的请求消息，读取基站发送的请求消息的业务链头中携带的会话索引，根据会话索引以及预先获取的各个融合控制器的属性信息，确定提供服务的融合控制器。其中涉及的装置设备如下所示：
UE(User Equipment，用户设备)，这里的UE包含手机，智能终端，多媒体设备，流媒体设备、移动互联网设备(MID，mobile internet device)、可穿戴设备(例如智能手表(如iwatch等)、智能手环、计步器等)或其他可与基站通讯的终端设备。
基站，LTE(Long Term Evolution，长期演进)网络中的无线基站，是LTE无线接入网的唯一网元,负责空中接口相关的所有功能。
控制器，也即融合控制器(Converged Controller)，是核心网络架构中的控制网元，负责处理所有控制信令，包括移动性管理、会话管理、策略与计费管理等。
网元选择器，可以部署于单个服务域内，实现服务域内的融合控制器的选择与负载均衡，亦可独立于服务域部署，负责实现跨服务域的融合控制器的选择与负载均衡功能。
用户上下文数据库(Database Sever，简称DB Server)，用以保存用户的相关数据，包括状态信息、承载信息等。
用户数据本地缓存(Local Data Cache)，将用户上下文数据同步到本地缓存，以提高融合控制面的数据访问效率。
在大多数的企业级应用及电子商务应用系统中，UE与融合控制器经常经过多次的交互过程才能完成一次事务或者一次服务。一方面，这些交互与用户身份密切相关，另一方面，融合控制器在进行这些交互过程的某一个步骤时，往往需要了解上一次交互过程的处理结果，或者上几步的交互过程结果。因此，与这个UE相关的应用请求，往往需要转发至一台融合控制器完成，而不能被网元选择器转发至不同的融合控制器上进行处理。为满足上述需求，网元选择器需要识别出UE与融合控制器之间交互过程的关联性，在作负载均衡的同时，还保证一系列相关联的访问请求会保持分配到一台融合控制器上，这种机制被称为会话保持。因此，在提供服务的融合控制器为UE分配会话索引后，UE在此后的每次交互中携带会话索引，网元选择器可以依据会话索引将同一用户请求发送到同一融合控制器，从而实现会话保持。
请参见图2，图2是本发明实施例的一种网元选择方法的一实施例的流程示意图。本发明实施例适用于UE接入或者接入MME之后周期发送的相关请求。
如图2所示，本发明实施例的一种网元选择方法可以包括如下步骤。
S200，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配。
具体实现中，UE向基站发送请求，基站识别出接收的请求为UE的信息， 设定与UE对应的会话索引。会话索引为空或者由服务所述UE的第一控制器分配。若会话索引为空表明UE当前的请求为接入，不存在为UE服务的融合控制器；若会话索引由服务所述UE的第一控制器分配，则会话索引中存储的分配所述会话索引的控制器的标识为第一控制器的标识，表明当前基站获知当前为UE服务的融合控制器为第一控制器。因此基站根据UE当前的接入情况设定会话索引，将会话索引由业务链头进行携带，并根据业务链头以及UE的信息生成请求消息，最后将请求消息发送至网元选择器。
作为一种可实施的方式，基站生成的请求消息可采用业务链(Service Function Chaining，简称SFC)封装。
作为一种可实施的方式，业务链头的设置方式可如图3所示，利用业务链头中的Service Path Identifier(服务路径标识)字段来保存会话索引，进而实现Session(会话)保持功能。图3中，业务链头包括Metadata Length(元数据长度)、Protocol Type(协议类型)、Service Index(服务指数)和Optional Metadata TLVs(可选的元数据阈限值)等，图3中出现的其他参数属于现有技术中业务链头的组成部分，本实施例则不再赘述。
S201，所述网元选择器根据所述会话索引确定提供服务的控制器。
具体实现中，网元选择器根据所述会话索引确定提供服务的融合控制器。
作为一种可实施的方式，网元选择器还可根据所述会话索引以及各个融合控制器的属性信息确定提供服务的融合控制器。网元选择器获取各个融合控制器的属性信息，各个融合控制器的属性信息包括各个融合控制器的位置信息和/或负载能力信息，以获取各个融合控制器的位置部署和负载情况。最后网元选择器结合会话索引以及各个融合控制器的属性信息确定提供服务的融合控制器。
S202，所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
具体实现中，网元选择器去除业务链头，将携带UE的信息的请求消息转发至提供服务的融合控制器，以使提供服务的融合控制器接收网元选择器转发的UE的信息，启动为UE服务的具体操作。
作为一种可实施的方式，提供服务的融合控制器可在对应的服务域的 Local Data Cache(用户数据本地缓存)为UE建立或更新上下文，从用户上下文数据库(Database Sever，简称DB Server)获取UE的相关数据，并为UE分配会话索引。提供服务的融合控制器再将关于UE的响应信息发送至网元选择器，由网元选择器转发给基站，以使基站得知由网元选择器确定的融合控制器为UE服务。
作为一种可实施的方式，响应信息可为S1应用协议(S1Application Protocol，S1-AP)消息该消息包含Controller S1-AP UE ID，并将Controller S1-AP UE ID作为会话索引，基站通过读取Controller S1-AP UE ID以获取会话索引，由此将会话索引作为UE上下文进行保存，继续UE的交互流程。
作为一种可实施的方式，可由提供服务的控制器分配给UE的GUTI参数或者控制器的标识(Controller ID)作为会话索引，由UE通知基站，使基站获取到提供服务的会话索引，由此将会话索引作为UE上下文进行保存，继续UE的交互流程。
采用本发明实施例，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。独立网元选择器属于核心网网元，获取各个控制器的当前属性状况的代价较小，因此能够减少系统消耗，以支持面向全核心网的、更为动态灵活的控制器负载均衡。
请参阅图4，图4是本发明实施例的一种网元选择方法的另一实施例的流程示意图。本发明实施例适用于UE接入或者接入MME之后周期发送的请求接入，本实施例则以UE初始接入为例进行举例说明。
S400，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配。
具体实现中，UE向基站发送UE的信息，其中，UE的信息为UE的信息， 并包括UE的国际移动用户识别码(International Mobile Subscriber Identity，简称IMSI)用以唯一标识UE。基站根据请求消息识别出接收的消息为UE的信息，设定与UE对应的会话索引。由于UE为初始接入，当前没有为UE服务的融合控制器，因此基站将会话索引设置为空。基站将会话索引由业务链头进行携带，并根据业务链头以及UE的信息生成请求消息，最后将请求消息发送至网元选择器。
作为一种可实施的方式，可设置会话索引为空(即控制器的标识(Controller ID)的值为0)或者为当前服务UE的第一控制器的标识。
S401，所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识。
具体实现中，若网元选择器从会话索引中获取到的分配所述会话索引的控制器的标识，说明当前已有控制器为UE服务，因此网元选择器可对分配所述会话索引的控制器的标识进行识别，识别出分配所述会话索引的控制器的标识为所述第一控制器的标识。
S402，所述网元选择器确定提供服务的控制器为所述第一控制器。
具体实现中，网元选择器可直接确定提供服务的控制器为所述第一控制器，并通知第一控制器继续服务UE。
S403，所述网元选择器识别出所述会话索引为空。
具体实现中，若网元选择器识别出会话索引为空，则所述网元选择器根据各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。具体的，网元选择器接收到基站发送的请求消息后，从请求消息的业务链头中的Service Path ID字段获取会话索引，识别会话索引中控制器的标识的值，若识别出控制器的标识的值为0，则获知会话索引为空，表明当前没有融合控制器为UE服务。
S404，所述网元选择器获取所述各个控制器的位置信息和/或负载能力信息。
具体实现中，由于当前没有融合控制器为UE服务，因此网元选择器需要为UE分配融合控制器。网元选择器可获取各个服务域中的融合控制器的位置 信息和/或负载能力信息，以获取各个融合控制器的位置部署和/或负载情况。网元选择器可利用各个融合控制器的位置信息确定为UE服务的融合控制器，通过了解各个融合控制器的位置信息可以得到各个融合控制器的具体位置，以找到与UE距离最近或能够和UE在所属的服务域内通信的融合控制器。网元选择器还可利用各个融合控制器的负载能力信息确定为UE服务的融合控制器，负载情况可得知每个融合控制器当前的负载压力，以识别出故障融合控制器，跨域屏蔽故障融合控制器的变化给其它网元带来的影响，在负载压力符合负载压力阈值的融合控制器中分配负载压力最小的融合控制器为UE服务。通过与融合控制器的弹性管理功能集成，基于负载情况实现自动伸缩策略。网元选择器还可综合利用各个融合控制器的位置信息以及负载能力信息确定为UE服务的融合控制器，例如网元选择器可选择与UE距离小于预设距离值且负载能力低于预设负载压力的融合控制器为UE服务。
S405，所述网元选择器获取所述基站的位置信息。
具体实现中，若网元选择器根据各个融合控制器的位置信息或者以及根据各个融合控制器的位置信息以及负载能力信息确定为UE服务的融合控制器，则网元选择器需要获取基站的位置信息，以确定基站和各个融合控制器之间的实际物理距离。
S406，所述网元选择器根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
具体实现中，网元选择器根据所述基站的位置信息和所述各个融合控制器的位置信息，计算基站和各个融合控制器之间的实际物理距离，再根据基站和各个融合控制器之间的实际物理距离和/或各个融合控制器的负载能力信息，确定提供服务的融合控制器。
S407，所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
具体实现中，如图5所示，网元选择器去除业务链头，将携带UE的信息的请求消息转发至提供服务的融合控制器，以使提供服务的融合控制器接收网元选择器转发的请求消息，通过分析UE的信息通知基站提供服务。具体地， 提供服务的融合控制器可在对应的服务域的Local Data Cache为UE建立上下文，从DB Server获取UE的相关数据。DB Server中保存着会话数据(Session Data)。不同融合控制器可分别享有不同的服务域，在图5中，服务域1可包括至少1个融合控制器，服务域2可包括除服务域1的融合控制器之外的至少1个融合控制器。
具体实现中，提供服务的融合控制器再将关于UE的响应信息发送至网元选择器，由网元选择器转发给基站，以使基站得知由网元选择器确定的融合控制器为UE服务。
作为一种可实施的方式，响应信息可为Controller S1-AP UE ID，并将Controller S1-AP UE ID作为会话索引，基站通过读取Controller S1-AP UE ID以获取会话索引，由此将会话索引作为UE上下文进行保存，继续UE的交互流程。
作为一种可实施的方式，可由提供服务的控制器分配给UE的GUTI参数或者控制器的标识(Controller ID)作为会话索引，由UE通知基站，使基站获取到提供服务的会话索引，由此将会话索引作为UE上下文进行保存，继续UE的交互流程。
采用本发明实施例，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。独立网元选择器属于核心网网元，获取各个控制器的当前属性状况的代价较小，因此能够减少系统消耗，以支持面向全核心网的、更为动态灵活的控制器负载均衡。
请参阅图6，图6是本发明实施例的一种网元选择方法的另一实施例的流程示意图。本发明实施例适用于UE接入或者接入MME之后周期发送的请求，本实施例则以UE接入MME之后周期发送的请求为例进行举例说明。
S600，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备 UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配。
具体实现中，UE向基站发送请求，其中，该请求可为NAS(Non-Access Stratum，非接入层)信令。例如，基站通过NAS信令读取全球唯一临时UE标识(Globally Unique Temporary UE Identity，GUTI)参数或者预先存储的网元选择器发送的Controller S1-AP UE ID识别出第一控制器的Controller ID，第一控制器为先前服务UE的融合控制器，则基站将第一控制器的标识由业务链头进行携带，并根据业务链头以及UE发送的NAS信令生成请求消息，最后基站将请求消息发送至网元选择器，本实施例不作限定。
作为一种可实施的方式，会话索引由服务所述UE的第一控制器分配，则会话索引中存储的分配所述会话索引的控制器的标识为第一控制器的标识。
S601，所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识。
具体实现中，网元选择器接收到请求消息后，从请求消息的业务链头中的Service Path ID字段识别出第一控制器的标识，表明当前为UE服务的融合控制器是第一控制器。
S602，所述网元选择器获取所述第一控制器的位置信息和/或负载能力信息。
具体实现中，由于当前为UE服务的融合控制器是第一控制器，因此网元选择器可获取第一控制器的位置信息和/或负载能力信息，以获取第一控制器的位置部署和/或负载情况。网元选择器可利用第一控制器的位置信息确定为UE服务的融合控制器，通过获取第一控制器的位置信息可以得到第一控制器的具体位置。网元选择器还可利用第一控制器的负载能力信息确定第一控制器的负载情况，通过负载情况可得知第一控制器当前的负载压力，以识别出第一控制器是否发生故障，若第一控制器发生故障则屏蔽第一控制器。网元选择器还可综合利用第一控制器的位置信息以及负载能力信息确定是否能够继续为UE服务。
S603，所述网元选择器获取所述基站的位置信息。
具体实现中，网元选择器为了判断第一控制器是否能够继续为UE服务， 网元选择器还需要获取基站的位置信息，以确定基站和第一控制器之间的实际物理距离。
S604，所述网元选择器根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务。
具体实现中，网元选择器根据所述基站的位置信息和所述第一控制器的位置信息，计算基站和第一控制器之间的实际物理距离，再根据基站和第一控制器之间的实际物理距离和/或第一控制器的负载能力信息，判断第一控制器是否能够继续为UE服务。若判断为是，则执行步骤S605，若判断为否，则执行步骤S606。
S605，所述网元选择器确定提供服务的控制器为所述第一控制器。
具体实现中，若网元选择器根据基站和第一控制器之间的实际物理距离和/或第一控制器的负载能力信息，判断出第一控制器仍然是最适合为UE服务的融合控制器，则确定第一控制器能够继续为UE服务。
S606，所述网元选择器获取除所述第一控制器外的控制器的位置信息和/或负载能力信息。
具体实现中，网元选择器根据基站和第一控制器之间的实际物理距离和/或第一控制器的负载能力信息，判断出第一控制器不适合为UE服务。由于第一控制器归属于服务域，且网元选择器独立于服务域，每个融合控制器归属于不同服务域，因此所述网元选择器可屏蔽第一控制器，获取除所述第一控制器外的融合控制器的位置信息和/或负载能力信息，以得到其他融合控制器的位置部署和/或负载情况。
S607，所述网元选择器根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
具体实现中，网元选择器根据所述基站的位置信息和其他融合控制器的位置信息，计算基站和其他融合控制器外的融合控制器之间的实际物理距离，再根据基站和其他融合控制器之间的实际物理距离和/或其他融合控制器的负载 能力信息，从其他融合控制器中确定为UE服务的融合控制器。
S608，所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
具体实现中，当网元选择器确定提供服务的融合控制器依旧为所述第一控制器时，则网元选择器去除业务链头，将NAS信令转发至第一控制器，以使第一控制器接收网元选择器转发的NAS信令，通过分析NAS信令通知基站提供服务。具体地，第一控制器可在对应的服务域的Local Data Cache更新UE的上下文和更新从DB Server获取的UE的相关数据。第一控制器再将关于UE的响应信息发送至网元选择器，由网元选择器转发给基站，以使基站得知由第一控制器继续为UE服务。基站获取会话索引的过程可详见实施例图4的步骤S407，本实施例则不再赘述。
具体实现中，当网元选择器确定提供服务的融合控制器为其他融合控制器中的融合控制器(例如第二控制器)时，则网元选择器去除业务链头，将NAS信令转发至第二控制器，以使第二控制器接收网元选择器转发的NAS信令，通过分析NAS信令通知基站提供服务。具体地，第二控制器可在对应的服务域的Local Data Cache将会话索引作为UE上下文进行保存和从DB Server获取的UE的相关数据。并且第二控制器为UE分配新的GUTI参数，发起GUTI的重新分配命令，将GUTI的重新分配命令以及关于第二控制器的Controller S1-AP UE ID发送至网元选择器，由网元选择器转发给基站，以使基站得知由第二控制器继续为UE服务。Controller S1-AP UE ID包括第二控制器的标识，基站通过读取Controller S1-AP UE ID，获知提供服务的融合控制器已更改为第二控制器，由此根据接收到的GUTI的重新分配命令更新预先保存的GUTI参数，更新会话索引，将第一控制器的标识更改为第二控制器的标识，继续UE的交互流程。或者，可由第二控制器分配给UE的GUTI参数或者第二控制器的标识(Controller ID)作为会话索引，由UE通知基站，使基站获取到会话索引，由此更新UE的上下文，继续UE的交互流程。
采用本发明实施例，基站将NAS信令发送至网元选择器，网元选择器读取业务链头中Controller ID的值为第一控制器的标识，若发现第一控制器已经不再适合继续提供服务，比如第一控制器的负载过重，故障等，则决定为UE 选择新的融合控制器并转发信令，新的融合控制器会发起GUTI重新分配流程，并继续交互流程，为UE提供不间断的服务，实现Session保持功能。
请参阅图7，图7是本发明实施例的一种网元选择器的结构示意图。如图7所示的网元选择器包括接收模块700、确定模块701以及发送模块702。
接收模块700，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
确定模块701，用于根据所述接收模块700接收的会话索引确定提供服务的控制器；
发送模块702，用于向所述确定模块701确定的提供服务的控制器发送所述接收模块接收的所述请求消息，以使所述提供服务的控制器为所述UE服务。
作为一种可实施的方式，如图8所示，所述确定模块701包括识别单元7011以及确定单元7013：
识别单元7011，用于从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
确定单元7013，用于确定提供服务的控制器为所述第一控制器。
作为一种可实施的方式，所述确定模块具体用于：
根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
作为一种可实施的方式，如图8所示，所述确定模块701还包括获取单元7012：
所述识别单元7011，还用于识别出所述会话索引为空；
获取单元7012，用于获取所述各个控制器的位置信息和/或负载能力信息；
所述获取单元7012，还用于获取所述基站的位置信息；
确定单元7013，用于根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
作为一种可实施的方式，如图8所示，所述确定模块701还包括判断单元7014：
所述识别单元7011，还用于从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
所述获取单元7012，还用于获取所述第一控制器的位置信息和/或负载能力信息；
所述获取单元7012，还用于获取所述基站的位置信息；
判断单元7014，用于根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
所述确定单元7013，还用于当所述判断单元7014的判断结果为是时，则确定提供服务的控制器为所述第一控制器；
所述获取单元7012，还用于当所述判断单元7014的判断结果为否时，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
所述确定单元7013，还用于根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
采用本发明实施例，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。独立网元选择器属于核心网网元，获取各个控制器的当前属性状况的代价较小，因此能够减少系统消耗，以支持面向全核心网的、更为动态灵活的控制器负载均衡。
请参阅图9，图9是本发明实施例的一种网元选择器的另一种结构示意图。本发明实施例的各个装置所实施的具体步骤可详见实施例图2至图6，本发明实施例则不再赘述。如图9所示，本实施例的移动终端包括通信总线900、输入装置901、输出装置902以及处理器903(网元选择器的处理器903的数量可以为一个或多个，图9中以一个处理器为例)，其中：
所述通信总线900，用于实现所述输入装置、所述输出装置、所述处理器903之间的连接通信；
所述输入装置901，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
所述处理器903，用于根据所述会话索引确定提供服务的控制器；
所述输出装置902，用于向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
作为一种可实施的方式，所述处理器903根据所述会话索引确定提供服务的控制器，具体用于执行如下步骤：
从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
确定提供服务的控制器为所述第一控制器。
作为一种可实施的方式，所述处理器903根据所述会话索引确定提供服务的控制器，具体执行如下步骤：
根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
作为一种可实施的方式，所述处理器903根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，具体执行如下步骤：
识别出所述会话索引为空；
获取所述各个控制器的位置信息和/或负载能力信息；
获取所述基站的位置信息；
根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/ 或负载能力信息，确定提供服务的控制器。
作为一种可实施的方式，所述处理器903根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，具体执行如下步骤：
从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
获取所述第一控制器的位置信息和/或负载能力信息；
获取所述基站的位置信息；
根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
若判断为是，则确定提供服务的控制器为所述第一控制器；
若判断为否，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
采用本发明实施例，网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；所述网元选择器根据所述会话索引确定提供服务的控制器；所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。独立网元选择器属于核心网网元，获取各个控制器的当前属性状况的代价较小，因此能够减少系统消耗，以支持面向全核心网的、更为动态灵活的控制器负载均衡。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质， 其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
以上所揭露的仅为本发明较佳实施例而已，当然不能以此来限定本发明之权利范围，因此依本发明权利要求所作的等同变化，仍属本发明所涵盖的范围。

Claims (15)

  1. 一种网元选择方法，其特征在于，包括：
    网元选择器接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
    所述网元选择器根据所述会话索引确定提供服务的控制器；
    所述网元选择器向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
  2. 根据权利要求1所述的网元选择方法，其特征在于，所述网元选择器根据所述会话索引确定提供服务的控制器，包括：
    所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
    所述网元选择器确定提供服务的控制器为所述第一控制器。
  3. 根据权利要求1所述的网元选择方法，其特征在于，所述网元选择器根据所述会话索引确定提供服务的控制器，包括：
    所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
  4. 根据权利要求3所述的网元选择方法，其特征在于，所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，包括：
    所述网元选择器识别出所述会话索引为空；
    所述网元选择器获取所述各个控制器的位置信息和/或负载能力信息；
    所述网元选择器获取所述基站的位置信息；
    所述网元选择器根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器 之间的距离和/或负载能力信息，确定提供服务的控制器。
  5. 根据权利要求3所述的网元选择方法，其特征在于，所述网元选择器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，包括：
    所述网元选择器从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
    所述网元选择器获取所述第一控制器的位置信息和/或负载能力信息；
    所述网元选择器获取所述基站的位置信息；
    所述网元选择器根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
    若判断为是，则所述网元选择器确定提供服务的控制器为所述第一控制器；
    若判断为否，则所述网元选择器获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
    所述网元选择器根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
  6. 一种网元选择器，其特征在于，包括：
    接收模块，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
    确定模块，用于根据所述接收模块接收的会话索引确定提供服务的控制器；
    发送模块，用于向所述确定模块确定的提供服务的控制器发送所述接收模块接收的所述请求消息，以使所述提供服务的控制器为所述UE服务。
  7. 根据权利要求6所述的网元选择器，其特征在于，所述确定模块包括：
    识别单元，用于从所述会话索引中获取分配所述会话索引的控制器的标识， 并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
    确定单元，用于确定提供服务的控制器为所述第一控制器。
  8. 根据权利要求6所述的网元选择器，其特征在于，所述确定模块具体用于：
    根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
  9. 根据权利要求8所述的网元选择器，其特征在于，所述确定模块包括：
    所述识别单元，还用于识别出所述会话索引为空；
    获取单元，用于获取所述各个控制器的位置信息和/或负载能力信息；
    所述获取单元，还用于获取所述基站的位置信息；
    所述确定单元，还用于根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
  10. 根据权利要求8所述的网元选择器，其特征在于，所述确定模块包括：
    所述识别单元，还用于从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
    所述获取单元，还用于获取所述第一控制器的位置信息和/或负载能力信息；
    所述获取单元，还用于获取所述基站的位置信息；
    判断单元，用于根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
    所述确定单元，还用于当所述判断单元的判断结果为是时，则确定提供服务的控制器为所述第一控制器；
    所述获取单元，还用于当所述判断单元的判断结果为否时，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
    所述确定单元，还用于根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
  11. 一种网元选择器，其特征在于，所述网元选择器包括通信总线、输入装置、输出装置以及处理器，其中：
    所述通信总线，用于实现所述输入装置、所述输出装置、所述处理器之间的连接通信；
    所述输入装置，用于接收基站发送的请求消息，所述请求消息包括用户设备UE的信息以及业务链头，所述业务链头包括会话索引，所述会话索引为空或者所述会话索引由服务所述UE的第一控制器分配；
    所述处理器，用于根据所述会话索引确定提供服务的控制器；
    所述输出装置，用于向所述提供服务的控制器发送所述请求消息，以使所述提供服务的控制器为所述UE服务。
  12. 根据权利要求11所述的网元选择器，其特征在于，所述处理器根据所述会话索引确定提供服务的控制器，具体用于执行如下步骤：
    从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出所述分配所述会话索引的控制器的标识为所述第一控制器的标识；
    确定提供服务的控制器为所述第一控制器。
  13. 根据权利要求11所述的网元选择器，其特征在于，所述处理器根据所述会话索引确定提供服务的控制器，具体执行如下步骤：
    根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，所述各个控制器的属性信息为所述各个控制器的位置信息和/或负载能力信息。
  14. 根据权利要求13所述的网元选择器，其特征在于，所述处理器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，具体执行如 下步骤：
    识别出所述会话索引为空；
    获取所述各个控制器的位置信息和/或负载能力信息；
    获取所述基站的位置信息；
    根据所述基站的位置信息和所述各个控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息，确定提供服务的控制器。
  15. 根据权利要求13所述的网元选择器，其特征在于，所述处理器根据所述会话索引以及各个控制器的属性信息确定提供服务的控制器，具体执行如下步骤：
    从所述会话索引中获取分配所述会话索引的控制器的标识，并识别出分配所述会话索引的控制器的标识为所述第一控制器的标识；
    获取所述第一控制器的位置信息和/或负载能力信息；
    获取所述基站的位置信息；
    根据所述基站的位置信息和所述第一控制器的位置信息确定所述基站和所述各个控制器之间的距离，根据所述基站和所述各个控制器之间的距离和/或负载能力信息判断是否采用所述第一控制器提供服务；
    若判断为是，则确定提供服务的控制器为所述第一控制器；
    若判断为否，则获取除所述第一控制器外的控制器的位置信息和/或负载能力信息；
    根据所述基站的位置信息和所述除所述第一控制器外的控制器的位置信息确定所述基站和所述除所述第一控制器外的控制器之间的距离，根据所述基站和所述除所述第一控制器外的控制器之间的距离和/或所述除所述第一控制器外的控制器的负载能力信息，确定提供服务的控制器。
PCT/CN2015/097601 2015-12-16 2015-12-16 一种网元选择方法及网元选择器 WO2017101045A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP15910518.8A EP3364694B1 (en) 2015-12-16 2015-12-16 Network element selection method and network element selector
PCT/CN2015/097601 WO2017101045A1 (zh) 2015-12-16 2015-12-16 一种网元选择方法及网元选择器
CN201580084662.4A CN108353352B (zh) 2015-12-16 2015-12-16 一种网元选择方法及网元选择器
US16/002,023 US10349344B2 (en) 2015-12-16 2018-06-07 Network element selection method and network element selector

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/097601 WO2017101045A1 (zh) 2015-12-16 2015-12-16 一种网元选择方法及网元选择器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/002,023 Continuation US10349344B2 (en) 2015-12-16 2018-06-07 Network element selection method and network element selector

Publications (1)

Publication Number Publication Date
WO2017101045A1 true WO2017101045A1 (zh) 2017-06-22

Family

ID=59055348

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/097601 WO2017101045A1 (zh) 2015-12-16 2015-12-16 一种网元选择方法及网元选择器

Country Status (4)

Country Link
US (1) US10349344B2 (zh)
EP (1) EP3364694B1 (zh)
CN (1) CN108353352B (zh)
WO (1) WO2017101045A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708676A (zh) * 2018-07-09 2020-01-17 普天信息技术有限公司 一种s1口集群消息处理方法、网络节点及基站

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112533236B (zh) * 2019-09-19 2023-06-02 华为技术有限公司 通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247634A (zh) * 2007-02-15 2008-08-20 北京三星通信技术研究有限公司 移动通信系统选择服务节点的方法
CN101400084A (zh) * 2007-09-30 2009-04-01 北京三星通信技术研究有限公司 改变ue的服务核心网络节点的方法
US20110235505A1 (en) * 2010-03-29 2011-09-29 Hitachi, Ltd. Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
CN102281532A (zh) * 2007-07-27 2011-12-14 华为技术有限公司 识别用户设备的方法和装置及临时标识传递和分配方法
CN103765948A (zh) * 2013-06-21 2014-04-30 华为技术有限公司 选择移动管理实体的方法、装置和系统

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7586868B2 (en) * 2003-07-14 2009-09-08 Motorola, Inc Method and apparatus for controlling distributed transcoders
CN101784035B (zh) * 2009-01-16 2013-05-08 中兴通讯股份有限公司 一种业务网元与mme建立关联的方法、系统及用户设备
CN102014365B (zh) * 2010-11-04 2015-01-28 中兴通讯股份有限公司 一种无线网络共享中选择核心网运营商的方法和系统
US9088501B2 (en) * 2013-07-31 2015-07-21 Citrix Systems, Inc. Systems and methods for least connection load balancing by multi-core device
US9755960B2 (en) * 2013-09-30 2017-09-05 Juniper Networks, Inc. Session-aware service chaining within computer networks
US9467382B2 (en) * 2014-02-03 2016-10-11 Cisco Technology, Inc. Elastic service chains
EP2922252B1 (en) * 2014-03-21 2017-09-13 Juniper Networks, Inc. Selectable service node resources
CN104980374B (zh) * 2014-04-04 2018-07-03 华为技术有限公司 一种业务路由报文的封装方法、业务转发实体及控制平面
US20150333930A1 (en) * 2014-05-15 2015-11-19 Akamai Technologies, Inc. Dynamic service function chaining
CN105099919B (zh) * 2014-05-15 2018-07-31 华为技术有限公司 报文处理方法及装置
US20150341285A1 (en) * 2014-05-22 2015-11-26 Akamai Technologies, Inc. Metadata transport between mobile network core and external data network
US9722927B2 (en) * 2014-06-05 2017-08-01 Futurewei Technologies, Inc. Service chain topology map construction
US9398486B2 (en) * 2014-06-10 2016-07-19 Cisco Technology, Inc. Conveying subscriber information to service chain services using tunnel protocol header encapsulation for mobile network applications in a network environment
US9749229B2 (en) * 2015-07-01 2017-08-29 Cisco Technology, Inc. Forwarding packets with encapsulated service chain headers
US10439886B2 (en) * 2015-07-13 2019-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Analytics-driven dynamic network design and configuration
US20170048815A1 (en) * 2015-08-12 2017-02-16 Cisco Technology, Inc. Location Awareness to Packet Flows using Network Service Headers
CN105141617B (zh) * 2015-09-14 2018-06-15 上海华为技术有限公司 一种数据中心间服务功能体的部署调整方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247634A (zh) * 2007-02-15 2008-08-20 北京三星通信技术研究有限公司 移动通信系统选择服务节点的方法
CN102281532A (zh) * 2007-07-27 2011-12-14 华为技术有限公司 识别用户设备的方法和装置及临时标识传递和分配方法
CN101400084A (zh) * 2007-09-30 2009-04-01 北京三星通信技术研究有限公司 改变ue的服务核心网络节点的方法
US20110235505A1 (en) * 2010-03-29 2011-09-29 Hitachi, Ltd. Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
CN103765948A (zh) * 2013-06-21 2014-04-30 华为技术有限公司 选择移动管理实体的方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3364694A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708676A (zh) * 2018-07-09 2020-01-17 普天信息技术有限公司 一种s1口集群消息处理方法、网络节点及基站
CN110708676B (zh) * 2018-07-09 2021-10-26 普天信息技术有限公司 一种s1口集群消息处理方法、网络节点及基站

Also Published As

Publication number Publication date
CN108353352A (zh) 2018-07-31
EP3364694A4 (en) 2018-09-12
EP3364694A1 (en) 2018-08-22
US20180288693A1 (en) 2018-10-04
US10349344B2 (en) 2019-07-09
EP3364694B1 (en) 2019-10-30
CN108353352B (zh) 2020-06-16

Similar Documents

Publication Publication Date Title
US11271846B2 (en) Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs)
CN112136294B (zh) 应用功能影响业务路由的消息和系统
EP3886404B1 (en) Domain name server allocation method and device
US20190174321A1 (en) Network slice selection method, device and system
WO2017170690A1 (ja) スライス管理システム及びスライス管理方法
KR20180134685A (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
CN109167670B (zh) Pfcp连接处理方法、装置、网元、系统及存储介质
WO2019134648A1 (zh) 一种控制面资源迁移的实现方法、装置及网络功能实体
CN103765948B (zh) 选择移动管理实体的方法、装置和系统
KR20190077510A (ko) 부하 마이그레이션 방법, 장치 및 시스템
WO2018090386A1 (zh) 一种nf组件异常的处理方法、设备及系统
WO2018000202A1 (zh) 一种负载迁移方法、装置及系统
US11917720B2 (en) Methods, systems, and computer readable media for enabling forwarding of subsequent network function subscription updates
WO2021170033A1 (zh) 一种网络配置方法及装置
KR20190056914A (ko) 네트워크 슬라이스를 통한 서비스 제공 방법 및 장치
US11743363B1 (en) Methods, systems, and computer readable media for utilizing network function (NF) service attributes associated with registered NF service producers in a hierarchical network
JP7145197B2 (ja) ハンドオーバ方法、デバイス及びシステム
WO2021052109A1 (zh) 通信方法及装置
US20210258872A1 (en) A method of and a device for operating network gateway services in a service based telecommunications system
CN112533236B (zh) 通信方法及装置
WO2017101045A1 (zh) 一种网元选择方法及网元选择器
WO2017045454A1 (zh) 一种实现终端接入的方法、装置和系统
US20230318960A1 (en) Methods, systems, and computer readable media for service communication proxy (scp) routing
WO2021115464A1 (zh) 一种网络切片选择方法及相关装置
JP2023543428A (ja) モビリティ管理エンティティ（ｍｍｅ）へのｓ１接続、および、アクセスおよびモビリティ管理機能（ａｍｆ）へのｎ２接続を分配するための方法、システムならびにコンピュータ読取可能媒体

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: 15910518

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE