CN105828315B - Gateway selection method and system - Google Patents
Gateway selection method and system Download PDFInfo
- Publication number
- CN105828315B CN105828315B CN201610141227.7A CN201610141227A CN105828315B CN 105828315 B CN105828315 B CN 105828315B CN 201610141227 A CN201610141227 A CN 201610141227A CN 105828315 B CN105828315 B CN 105828315B
- Authority
- CN
- China
- Prior art keywords
- control plane
- plane entity
- gateway control
- entity
- service gateway
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000010187 selection method Methods 0.000 title abstract description 12
- 238000000034 method Methods 0.000 claims description 22
- 238000012937 correction Methods 0.000 claims description 18
- 238000002360 preparation method Methods 0.000 claims 1
- 230000006870 function Effects 0.000 description 18
- 230000004044 response Effects 0.000 description 16
- 230000005540 biological transmission Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
- H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a kind of gateway selection method and systems, it is that user equipment chooses suitable gateway control face entity by mobile management entity, and be that user equipment selects gateway user entity by the selected gateway control face entity of mobile management entity, guarantee effective operation of evolution block core net framework after SGW is separated into two entities of SGW-C and SGW-U.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and a system for selecting a serving gateway.
Background
With the increase of user Data transmission services, an existing Evolved Packet Core (EPC) architecture cannot meet user requirements, and becomes a bottleneck limiting the increase of user Data transmission rate, and therefore, an existing 3GPP organization is considering to enhance an existing Core Network architecture, and separates functions of a control plane and functions of a user plane of a Serving Gateway (SGW) and a PDN Gateway (Packet Data Network Gateway, PGW). Wherein the SGW is separated into two entities: the method comprises a service gateway control plane entity SGW-C and a service gateway user plane entity SGW-U, wherein the SGW-C is used for realizing the control plane function of the original SGW, and the SGW-U is used for realizing the user plane function of the original SGW.
In the EPC core network architecture, an MME and a serving gateway are required to establish a bearer, that is, a Mobility Management Entity (MME) selects an SGW for a user equipment UE. After the SGW is separated into two entities, namely SGW-C and SGW-U, the original method for selecting the SGW for the UE by the mobility management entity is no longer applicable, and there is no current theory on how to select the SGW-C and the SGW-U for the UE.
Disclosure of Invention
The invention aims to provide a method and a system for selecting a service gateway, which are used for ensuring that an SGW is separated into an SGW-C entity and an SGW-U entity and then evolves effective operation of a packet core network architecture.
In order to achieve the purpose, the invention provides the following technical scheme:
a method of serving gateway selection, comprising:
the mobile management entity selects a target service gateway control plane entity for the user equipment;
the mobile management entity sends a first bearer establishment request to the target service gateway control plane entity;
the target service gateway control plane entity responds to the first bearer establishment request and selects a target service gateway user plane entity for the user equipment;
and the target service gateway control plane entity sends a second bearer establishment request to the target service gateway user plane entity.
In the foregoing method, preferably, the selecting, by the mobility management entity, the target serving gateway control plane entity for the user equipment includes:
the mobility management entity obtains a list of service gateway control plane entities available to the user equipment;
distributing weight to each service gateway control plane entity in the list;
and determining the service gateway control plane entity with the largest weight as a target service gateway control plane entity.
In the foregoing method, preferably, the obtaining, by the mobility management entity, the list of serving gateway control plane entities available to the user equipment includes:
the mobility management entity obtains a list of serving gateway control plane entities available to the user equipment as determined by a domain name server.
In the foregoing method, preferably, the allocating weights to each serving gateway control plane entity in the list includes:
and distributing weight for each service gateway control plane entity in the list based on the interface protocol type supported by the service gateway control plane entity and the load condition of the service gateway control plane entity.
Preferably, the allocating, to each serving gateway control plane entity in the list, a weight based on an interface protocol type supported by the serving gateway control plane entity and a load condition of the serving gateway control plane entity includes:
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, or the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity is 0;
if the interface protocol type supported by the service gateway control plane entity is matched with the service transmitted by the user equipment, and the load condition of the service gateway control plane entity does not exceed a preset load threshold value, allocating weight to the service gateway control plane entity according to a first formula, wherein the first formula is as follows:
wc＝1/Lc+μc
wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
A service gateway selection system comprising: the mobile management entity, at least one service gateway control plane entity connected with the mobile management entity, and a plurality of service gateway user plane entities connected with the at least one service gateway control plane entity;
the mobile management entity is used for selecting a target service gateway control plane entity for user equipment from the at least one service gateway control plane entity and sending a first bearer establishment request to the target service gateway control plane entity;
the service gateway control plane entity is used for responding to a first bearer establishment request when receiving the first bearer establishment request, selecting a target service gateway user plane entity for the user equipment from the plurality of service gateway user plane entities, and sending a second bearer establishment request to the target service gateway user plane entity.
The above system, preferably, in terms of selecting a target serving gateway control plane entity for the user equipment from the at least one serving gateway control plane entity, the mobility management entity is configured to,
acquiring a list of service gateway control plane entities available for the user equipment; distributing weight to each service gateway control plane entity in the list; and determining the service gateway control plane entity with the largest weight as a target service gateway control plane entity.
The above system, preferably, in terms of obtaining the list of serving gateway control plane entities available to the user equipment, the mobility management entity is configured to,
obtaining a list of serving gateway control plane entities available to the user equipment as determined by a domain name server.
The above system, preferably, is a method of assigning a weight to each serving gateway control plane entity in the list, the mobility management entity is configured to,
and distributing weight for each service gateway control plane entity in the list based on the interface protocol type supported by the service gateway control plane entity and the load condition of the service gateway control plane entity.
The above system, preferably, in terms of assigning weights to each serving gateway control plane entity in the list based on the interface protocol type supported by the serving gateway control plane entity and the load status of the serving gateway control plane entity, the mobility management entity is configured to,
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, or the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity is 0;
if the interface protocol type supported by the service gateway control plane entity is matched with the service transmitted by the user equipment, and the load condition of the service gateway control plane entity does not exceed a preset load threshold value, allocating weight to the service gateway control plane entity according to a first formula, wherein the first formula is as follows:
wc＝1/Lc+μc
wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
According to the scheme, the service gateway selection method and the service gateway selection system provided by the embodiment of the invention have the advantages that the mobile management entity selects a proper service gateway control plane entity for the user equipment, and the service gateway control plane entity selected by the mobile management entity selects a service gateway service plane entity for the user equipment, so that the effective operation of the packet core network architecture is guaranteed after the SGW is separated into two entities, namely the SGW-C entity and the SGW-U entity.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a network architecture of an EPC core network currently specified by 3 GPP;
fig. 2 is a schematic diagram of a network architecture of an enhanced EPC core network;
fig. 3 is a flowchart of an implementation of a service gateway selection method according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating an implementation of selecting, by a mobility management entity, a target serving gateway control plane entity for a user equipment according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating an implementation of selecting a target serving gateway user plane entity for a user equipment in response to a first bearer establishment request by a target serving gateway control plane entity according to an embodiment of the present invention;
fig. 6 is a flowchart of another implementation of a service gateway selection method according to an embodiment of the present invention;
fig. 7 is a flowchart of another implementation of the service gateway selection method according to the embodiment of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be practiced otherwise than as specifically illustrated.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without inventive effort based on the embodiments of the present invention, are within the scope of the present invention.
For better understanding of the embodiment of the present invention, an existing evolved packet core EPC will first be described.
The core network device in the existing EPC includes: a mobility management entity MME, a serving gateway SGW, a PDN gateway PGW, a Home Subscriber Server (HSS) for storing subscriber subscription information, a Policy and Charging Rules Function (PCRF) for measuring control and charging rules, and so on. Wherein,
the MME is a device of the unique control plane of the EPC core network, and its main functions include: access control, mobility management, session management, network element selection, user bearer information storage, and the like.
The SGW is located in a user plane, is a gateway facing an evolved universal radio access network (E-UTRAN) side, and can be served by only one SGW at a time for each user equipment UE accessing the E-UTRAN. The SGW has the main functions of session management, routing and data forwarding, Quality of service (QOS) control, charging, and information storage.
The PGW is located in a user plane, and is a gateway facing a Public Data Network (PDN) and terminating at an SGi interface, that is, the PGW communicates with an IP server (e.g., Packet Switching Service (PSS), IP Multimedia Subsystem (IMS)) of an operator through the SGi interface. If the UE accesses multiple PDNs, the UE will correspond to one or more PGWs. The main functions of the PGW include IP address allocation, session management, PCRF selection, routing and data forwarding, QOS control, charging, policy and charging enforcement, etc.
The PCRF contains Policy and Charging Enforcement Function (PCEF) functions related to service data flow detection, gating, QOS-based and Charging-based network control functions, and functions related to flow Charging control, and is located in the PGW.
Fig. 1 is a schematic diagram of a network architecture of an EPC core network currently specified by 3 GPP. In fig. 1, the user is within the home network and is not roaming. When the user does not roam, the structure is simple, the signaling and the media are connected through the home network, and all network elements are provided by the home network. The control plane of the LTE system is connected with the MME through an S1-MME interface, the user plane is directly connected with the SGW through an S1-U interface, and the SGW and the PGW are connected through an S5 interface.
At present, a control plane and a user plane of an EPC core network element are not separated, an SGW is generally centrally deployed in a machine room of an operator, the SGW not only needs to transmit user plane data, but also needs to transmit some control plane signaling, with the increasing forwarding number of EPC core network data packets, the capacity of the SGW becomes a bottleneck limiting the increase of the transmission rate of the core network, and the centralized deployment of the SGW makes networking inflexible, poor expansibility, and is unable to adapt to the development of future services. For this reason, the 3GPP determines a research project for separating the control plane and the user plane of the LTE core network, and separates the control plane Function and the user plane Function of a core network element SGW, a PGW, and a TDF (Traffic Detection Function, which belongs to optional network element equipment in the core network and is not shown in fig. 1).
Fig. 2 is a schematic diagram of a network architecture of an enhanced EPC core network. The SGW in the original core network architecture is separated into two entities: the method comprises a service gateway control plane entity SGW-C and a service gateway user plane entity SGW-U, wherein the SGW-C is used for realizing the control plane function of the original SGW, and the SGW-U is used for realizing the user plane function of the original SGW. A new interface (shown by a dotted line in fig. 2) is introduced between the serving gateway control plane entity and the serving gateway user plane entity for information interaction. Similarly, the original PGW is also divided into a packet data gateway control plane entity PGW-C and a packet data gateway user plane entity PGW-U. The SGW-C and the PGW-C carry out interaction of control plane information through an S5 interface; and the SGW-U and the PGW-U carry out interaction of user plane information through an S5 interface.
After the control plane and the user plane are separated, the design of each entity can be simplified, so that the distributed network structure is more suitable for the distributed network structure, and the networking flexibility and the expandability are stronger, thereby being more suitable for the development of future services. The service gateway control plane entity and the service gateway user plane entity may be in one-to-many (that is, one service gateway control plane entity is connected with a plurality of service gateway user plane entities) or in many-to-many connection relationship, and may be deployed flexibly according to different service scenarios. For example, for an urban scenario with dense users, the serving gateway user plane entity may be deployed on the cell side close to the access network, while for a suburban scenario with sparse users, the serving gateway user plane entity may be concentrated in the center of the area (i.e., the central area of the suburban users); meanwhile, the serving gateway control plane entity may still be centrally deployed in the machine room of the operator, so as to facilitate interaction with other control plane core network nodes (MME, HSS, etc.) in the machine room, and may also be deployed on the access network side as needed.
It should be noted that the enhanced EPC network architecture is a hot spot of research of various companies of the current 3GPP organization, the final architecture is not determined yet, the enhanced EPC network architecture diagram of fig. 2 is a scheme that most member organizations of the current 3GPP tend to adopt, and the EPC architecture written into the standard finally may be slightly different from that of fig. 2.
In addition, only network elements related to the embodiment of the present invention are shown in fig. 1 and fig. 2, and other network elements are not shown.
Before the control plane and the user plane are separated, the MME is responsible for the gateway selection of the core network, namely, the selection of a service gateway and a PDN gateway is realized in the MME. After the control plane and the user plane are separated, because the serving gateway user plane entity belongs to a user plane node, and the MME is a control plane node, the association between the serving gateway user plane entity and the user plane node is not large, and there is no direct interface between the serving gateway user plane entity and the control plane node for communication, the MME is difficult to obtain the load condition of the serving gateway user plane entity and the link state of the serving gateway user plane entity and other networks, so the scheme of selecting a serving gateway by the MME is not suitable for the enhanced EPC network architecture. Based on this, the embodiment of the present invention provides a service gateway selection method and system suitable for an enhanced EPC network architecture.
Referring to fig. 3, fig. 3 is a flowchart of an implementation of a service gateway selection method according to an embodiment of the present invention, where the method includes:
step S31: the mobile management entity selects a target service gateway control plane entity for the user equipment;
in the embodiment of the invention, a mobile management entity MME selects a serving gateway control plane entity SGW-C from a plurality of serving gateway control plane entities connected with the MME to serve user equipment UE.
Step S32: the mobile management entity sends a first bearer establishment request to a target service gateway control plane entity;
after selecting a target service gateway control plane entity, the mobility management entity sends a bearer establishment request to the target service gateway control plane entity to establish a bearer with the target service gateway control plane entity, and triggers the target service gateway control plane entity to select a service gateway user plane entity SGW-U for the user equipment.
Step S33: and the target service gateway control plane entity responds to the first bearer establishment request and selects a target service gateway user plane entity for the user equipment.
And the target serving gateway control plane entity selects one serving gateway user plane entity from a plurality of serving gateway user plane entities connected with the target serving gateway control plane entity to serve the user equipment UE.
Step S34: and the target service gateway control plane entity sends a second bearer establishment request to the target service gateway user plane entity.
After the serving gateway user plane entity is selected, a second bearer establishment request may be sent to the selected serving gateway user plane entity to establish a bearer with the selected serving gateway user plane entity.
In the service gateway selection method provided by the embodiment of the present invention, the mobility management entity selects an appropriate service gateway control plane entity for the user equipment, and the service gateway control plane entity selected by the mobility management entity selects a service gateway service plane entity for the user equipment, thereby ensuring that the SGW is separated into two entities, i.e., an SGW-C entity and an SGW-U entity, and then the effective operation of the packet core network architecture is evolved.
Optionally, an implementation flowchart of selecting, by the mobility management entity, the target serving gateway control plane entity for the user equipment according to the embodiment of the present invention is shown in fig. 4, and may include:
step S41: the mobile management entity obtains a list of service gateway control plane entities available for the user equipment;
the serving gateway control plane entities in the list are all serving gateway control plane entities that can serve the user equipment.
If the list is empty, that is, there is no serving gateway control plane entity in the list, indicating that there is no serving gateway control plane entity meeting the transmission requirement of the user equipment, the mobility management entity fails to select the serving gateway, and the user equipment cannot access the EPC core network through the mobility management entity.
Step S42: the mobile management entity distributes weight to each service gateway control plane entity in the list;
the weight may be assigned to the serving gateway control plane entity based on the configuration parameters of the serving gateway control plane entity and the actual operational parameters.
Step S43: and the mobility management entity determines the service gateway control plane entity with the maximum weight as a target service gateway control plane entity.
In the embodiment of the invention, the larger the weight of the service gateway control plane entity is, the higher the priority of the service gateway control plane entity is selected is, the higher the priority is, the priority is selected.
Optionally, an implementation manner of the mobility management entity obtaining the list of the serving gateway control plane entity available to the user equipment provided in the embodiment of the present invention may be:
the mobility management entity obtains a list of serving gateway control plane entities available to the user equipment as determined by the domain name server.
Specifically, the domain name server may parse available serving gateway control plane entities that may serve the user equipment according to a location of the user equipment (i.e., a Tracking Area Identity (TAI) where the user equipment is located), where the serving gateway control plane entities constitute a list of selectable serving gateway control plane entities of the user equipment.
Optionally, an implementation manner of the mobility management entity allocating a weight to each serving gateway control plane entity in the list provided in the embodiment of the present invention may specifically be:
the mobility management entity assigns a weight to each serving gateway control plane entity in the list based on the interface protocol type supported by the serving gateway control plane entity and the load condition of the serving gateway control plane entity.
The interface protocol type supported by the service gateway control plane entity belongs to the configuration parameter of the service gateway control plane entity, and the load condition of the service gateway control plane entity reflects the actual operation condition of the service gateway control plane entity.
If the interface protocol type supported by the service gateway control plane entity is matched with the service transmitted by the user equipment, the larger the load of the service gateway control plane entity is, the smaller the weight of the service gateway control plane entity is; the smaller the load, the more weight it is.
The matching of the interface protocol type supported by the service gateway control plane entity and the service transmitted by the user equipment means that: the serving gateway control plane entity may satisfy the data transmission requirements of the user equipment. For example, according to the interface protocol type supported by the serving gateway control plane entity, the serving gateway control plane entity can be divided into three types: the system comprises a service gateway control plane entity only supporting a GTP interface protocol, a service gateway control plane entity only supporting a PMIP interface protocol and a service gateway control plane entity supporting both the GTP interface protocol and the PMIP interface protocol. If the service transmitted by the user equipment requires to support a GTP interface protocol and a certain service gateway control plane entity only supports a PMIP interface protocol, the type of the interface protocol supported by the certain service gateway control plane entity is not matched with the service transmitted by the user equipment; and if the certain serving gateway control plane entity only supports the GTP interface protocol, or supports both the GTP interface protocol and the PMIP interface protocol, the interface protocol type supported by the certain serving gateway control plane entity is matched with the service transmitted by the user equipment.
Optionally, in order to ensure that the mobility management entity learns the load status of the serving gateway control plane entity in time, all serving gateway control plane entities controlled by the mobility management entity report the load status to the mobility management entity. In particular, the method comprises the following steps of,
the serving gateway control plane entity may report periodically, that is, at intervals, the serving gateway control plane entity reports its load status to the mobility management entity.
The load status may also be reported in an event-triggered manner, for example, if the load status of the serving gateway control plane entity is changed from the last reported load status by more than a preset variable threshold, the load status is reported to the mobility management entity.
The load condition may be measured by a percentage, that is, a ratio of a current load of the serving gateway control plane entity to a load in a full load state.
Optionally, an implementation manner of the mobility management entity allocating a weight to each serving gateway control plane entity in the list based on an interface protocol type supported by the serving gateway control plane entity and a load condition of the serving gateway control plane entity may specifically be:
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, the weight distributed to the service gateway control plane entity by the mobile management entity is 0;
if the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity by the mobile management entity is also 0;
optionally, if the weight of the serving gateway control plane entity is 0, the serving gateway control plane entity is regarded as an invalid serving gateway control plane entity, and is removed from the serving gateway control plane entity list.
If the interface protocol type supported by the serving gateway control plane entity is matched with the service transmitted by the user equipment, and the load of the serving gateway control plane entity does not exceed the preset load threshold value, the mobile management entity allocates weight to the serving gateway control plane entity according to a first formula, wherein the first formula is as follows:
wc＝1Lc+μc
wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
In the embodiment of the present invention, the correction factors corresponding to different service gateway control plane entities may be the same or different. The specific value of the correction factor may be specifically set according to the stability of the serving gateway control plane entity within a certain time period. That is, the values of the correction factors may be different in different time periods for the same serving gateway control plane entity. For example, if a certain serving gateway control plane entity has unstable performance in a recent period, and is frequently overloaded or has a link failure with another device, compared with other serving gateway control plane entities around the certain serving gateway control plane entity, the value of the correction factor of the certain serving gateway control plane entity needs to be reduced, so that the certain serving gateway control plane entity maintains a lower load. And if the certain serving gateway control plane entity has stable performance in a recent period, is less overloaded, and has no fault in a link with other equipment relative to other serving gateway control plane entities around, the value of the correction factor of the certain serving gateway control plane entity can be increased, so that the certain serving gateway control plane entity maintains higher load.
The serving gateway control plane entity c is any one serving gateway control plane entity in the serving gateway control plane entity list.
Similar to the implementation manner of selecting the target serving gateway control plane entity for the ue by the mobility management entity, in the embodiment of the present invention, an implementation flowchart of selecting the target serving gateway user plane entity for the ue in response to the first bearer establishment request is shown in fig. 5, and may include:
step S51: a target service gateway control plane entity acquires a list of service gateway user plane entities available for user equipment;
the serving gateway user plane entities in the list are all serving gateway user plane entities that can serve the user equipment.
If the list is empty, that is, there is no serving gateway user plane entity in the list, it indicates that none of the serving gateway user plane entities controlled by the target serving gateway control plane entity can meet the data transmission requirement of the user equipment, and the target serving gateway control plane entity sends a response message of failure in establishing a bearer to the mobility management entity. After receiving the response message of failing to establish the bearer, the mobility management entity sets the weight of the target serving gateway control plane entity to 0, and may also delete the target serving gateway control plane entity from the serving gateway control plane entity list, and then reselect a new target serving gateway control plane entity.
Step S52: the target service gateway control plane entity distributes weight for each service gateway user plane entity in the list;
the weight can be distributed to the service gateway user plane entity according to the configuration parameters and the actual operation parameters of the service gateway user plane entity.
Step S53: and the target service gateway control plane entity determines the service gateway user plane entity with the maximum weight as the target service gateway user plane entity.
In the embodiment of the invention, the higher the weight of the user plane entity of the service gateway is, the higher the priority level of the selected user plane entity of the service gateway is, the more preferred the user plane entity is.
Optionally, an implementation manner of acquiring, by the target serving gateway control plane entity, the list of serving gateway user plane entities available to the user equipment, provided by the embodiment of the present invention, may be:
the target serving gateway control plane entity obtains a list of serving gateway user plane entities available to the user equipment as determined by the domain name server.
Specifically, the domain name server may parse available service gateway user plane entities that may serve the ue according to a location of the ue (i.e., a Tracking Area Identity (TAI) of the ue, where the service gateway user plane entities constitute an optional service gateway user plane entity list of the ue.
Optionally, an implementation manner of the target serving gateway control plane entity allocating a weight to each serving gateway user plane entity in the list provided in the embodiment of the present invention may specifically be:
the target serving gateway control plane entity assigns a weight to each serving gateway user plane entity in the list based on the interface protocol type supported by the serving gateway user plane entity and the load condition of the serving gateway user plane entity.
The interface protocol type supported by the service gateway user plane entity belongs to the configuration parameters of the service gateway user plane entity, and the load condition of the service gateway user plane entity reflects the actual operation condition of the service gateway user plane entity.
If the interface protocol type supported by the service gateway user plane entity is matched with the service transmitted by the user equipment, the larger the load of the service gateway user plane entity is, the smaller the weight of the service gateway user plane entity is; the smaller the load, the more weight it is.
The matching between the interface protocol type supported by the service gateway user plane entity and the service transmitted by the user equipment means that: the service gateway user plane entity can meet the data transmission requirement of the user equipment. For example, according to the interface protocol type supported by the serving gateway user plane entity, the serving gateway user plane entity can be divided into three types: a serving gateway user plane entity supporting only the GTP interface protocol, a serving gateway user plane entity supporting only the PMIP interface protocol, and a serving gateway user plane entity supporting both the GTP interface protocol and the PMIP interface protocol. If the service transmitted by the user equipment requires to support a GTP interface protocol and a certain service gateway user plane entity only supports a PMIP interface protocol, the interface protocol type supported by the certain service gateway user plane entity is not matched with the service transmitted by the user equipment; and if the certain serving gateway user plane entity only supports the GTP interface protocol, or supports both the GTP interface protocol and the PMIP interface protocol, the interface protocol type supported by the certain serving gateway user plane entity is matched with the service transmitted by the user equipment.
Optionally, in order to ensure that the serving gateway control plane entity learns the load status of the serving gateway user plane entity in time, all the serving gateway user plane entities controlled by the serving gateway control plane entity report the load status of the serving gateway user plane entity to the serving gateway control plane entity. In particular, the method comprises the following steps of,
the serving gateway user plane entity may report periodically, that is, at intervals, the serving gateway user plane entity reports its load status to the serving gateway control plane entity.
The reporting may also be performed in an event-triggered manner, for example, if the load condition of the serving gateway user plane entity is changed from the last reported load condition by more than a preset variable threshold, the load condition is reported to the serving gateway control plane entity.
The load condition may be measured by a percentage, that is, a ratio of a current load of the service gateway user plane entity to a load in a full load state.
Optionally, a specific implementation manner of the target serving gateway control plane entity allocating a weight to each serving gateway user plane entity in the list based on an interface protocol type supported by the serving gateway user plane entity and a load condition of the serving gateway user plane entity may be:
if the interface protocol type supported by the service gateway user plane entity is not matched with the service transmitted by the user equipment, the weight distributed to the service gateway user plane entity by the target service gateway control plane entity is 0;
if the load condition of the service gateway user plane entity exceeds a preset load threshold value, the weight distributed by the target service gateway control plane entity for the service gateway user plane entity is also 0;
optionally, if the weight of the service gateway user plane entity is 0, the service gateway user plane entity is regarded as an invalid service gateway user plane entity, and is removed from the service gateway user plane entity list.
If the interface protocol type supported by the service gateway user plane entity is matched with the service transmitted by the user equipment, and the load of the service gateway user plane entity does not exceed the preset load threshold value, the target service gateway control plane entity distributes weight to the service gateway user plane entity according to a first formula, wherein the first formula is as follows:
wu＝1/Lu+μu
wherein, wuAs weight, L, of serving gateway user plane entity uuFor the load capacity, mu, of the service gateway user plane entity uuIs the correction factor corresponding to the serving gateway user plane entity u.
In the embodiment of the present invention, the correction factors corresponding to different service gateway user plane entities may be the same or different. The specific value of the correction factor may be specifically set according to the stability of the service gateway user plane entity in a certain time period. That is, the values of the correction factors may be different in different time periods for the same serving gateway user plane entity. For example, when a certain serving gateway user plane entity has unstable performance in a recent period, and is frequently overloaded or has a link failure with another device, compared with other serving gateway user plane entities around, the value of the correction factor of the certain serving gateway user plane entity needs to be reduced to maintain a lower load for the certain serving gateway user plane entity. And if the certain service gateway user plane entity has stable performance in a recent period, is less overloaded and has no fault in a link with other equipment compared with other surrounding service gateway user plane entities, the value of the correction factor of the certain service gateway user plane entity can be increased, so that the certain service gateway user plane entity maintains higher load.
The service gateway control plane entity u is any one service gateway user plane entity in the service gateway user plane entity list.
Another implementation flowchart of the service gateway selection method provided in the embodiment of the present invention is shown in fig. 6, and may include:
step S61: the MME selects a target SGW-C for User Equipment (UE);
step S62: the MME sends a first bearer establishment request to the selected target SGW-C;
step S63: the target SGW-C responds to the first bearer establishing request and selects a target SGW-U for the UE;
step S64: the target SGW-C sends a second bearer establishment request to the selected target SGW-U;
step S65: the target SGW-U responds to the second bearer establishing request and sends a first response message of successful bearer establishment to the target SGW-C;
step S66: and the target SGW-C sends a second response message of successful bearer establishment to the MME.
Fig. 7 shows a flowchart of another implementation of the service gateway selection method according to the embodiment of the present invention, which may include:
step S71: and the MME updates an optional SGW-C list of the UE and sets weights for all SGW-Cs in the SGW-C list.
Step S72: and judging whether the SGW-C list is empty, if so, ending, otherwise, executing the step S73.
Step S73: and selecting the SGW-C with the largest weight as the optimal SGW-C (namely the target SGW-C), and sending a first bearer establishment request to the optimal SGW-C.
Step S74: the SGW-C receiving the first bearer establishment request judges whether the UE can be admitted or not according to the load condition of the SGW-C; if yes, step S75 is executed, and if not, step S710 is executed.
Step S75: and the SGW-C receiving the first bearer establishment request updates an optional SGW-U list of the UE and sets weight for each SGW-U in the SGW-U list.
Step S76: and judging whether the SGW-U list is empty, if so, executing step S710, otherwise, executing step S77.
Step S77: and selecting the SGW-U with the largest weight as the optimal SGW-U, and sending a second bearer establishment request to the optimal SGW-U. Step S78: the SGW-U receiving the second bearer establishment request judges whether the UE can be admitted or not according to the load condition of the SGW-U; if yes, step S79 is executed, and if not, step S712 is executed.
Step S79: transmitting a response message, comprising: and the SGW-U receiving the second bearer establishment request sends a first response message of successful bearer establishment to the SGW-C sending the second bearer establishment request, and the SGW-C receiving the first response message sends a second response message of successful bearer establishment to the MME.
Step S710: and the SGW-C receiving the first bearer establishment request sends a third response message of failure in bearer establishment to the MME.
Step S711: after receiving the third response message, the MME deletes the SGW-C that sent the third response message from the SGW-C list, and then proceeds to step S72.
Step S712: and the SGW-U receiving the second bearer establishment request sends a fourth response message of failed bearer establishment to the SGW-C sending the second bearer establishment request.
Step S713: the SGW-C receiving the fourth response message deletes the SGW-U transmitting the fourth response message from the SGW-U list, and then proceeds to step S76.
Wherein, steps S71-S73, and S711 are executed by the MME. Step S74 to step S77, and step S710 and step S713 are performed by the optimum SGW-C. Step S78 and step S712 are performed by the optimal SGW-U.
Corresponding to the method embodiment, the embodiment of the present invention further provides a service gateway selection system, where the service gateway selection system provided in the embodiment of the present invention includes: the mobile management entity, at least one service gateway control plane entity connected with the mobile management entity, and a plurality of service gateway user plane entities connected with the at least one service gateway control plane entity; the service gateway control plane entity and the service gateway user plane entity may be in a one-to-many connection relationship (that is, one service gateway control plane entity is connected with a plurality of service gateway user plane entities), or may be in a many-to-many connection relationship.
The mobile management entity is used for selecting a target service gateway control plane entity for the user equipment from at least one service gateway control plane entity and sending a first bearer establishment request to the target service gateway control plane entity;
the service gateway control plane entity is used for responding to the first bearer establishment request when receiving the first bearer establishment request, selecting a target service gateway user plane entity for the user equipment from the plurality of service gateway user plane entities, and sending a second bearer establishment request to the target service gateway user plane entity.
In the service gateway selection system provided by the embodiment of the present invention, the mobility management entity selects an appropriate service gateway control plane entity for the user equipment, and the service gateway control plane entity selected by the mobility management entity selects a service gateway service plane entity for the user equipment, thereby ensuring that the SGW is separated into two entities, i.e., an SGW-C entity and an SGW-U entity, and then the effective operation of the packet core network architecture is evolved.
Optionally, in an aspect of selecting a target serving gateway control plane entity for the user equipment from the at least one serving gateway control plane entity, the mobility management entity may be specifically configured to,
acquiring a list of service gateway control plane entities available for user equipment; distributing weight for each service gateway control plane entity in the list; and determining the service gateway control plane entity with the largest weight as a target service gateway control plane entity.
Alternatively, in terms of obtaining a list of serving gateway control plane entities available to the user equipment, the mobility management entity may specifically be configured to,
a list of serving gateway control plane entities available to the user equipment as determined by the domain name server is obtained.
Optionally, in terms of assigning weights to the respective serving gateway control plane entities in the list, the mobility management entity may specifically be configured to,
and allocating weight for each service gateway control plane entity in the list based on the interface protocol type supported by the service gateway control plane entity and the load condition of the service gateway control plane entity.
Alternatively, the mobility management entity may be specifically configured to assign a weight to each serving gateway control plane entity in the list based on the type of interface protocol supported by the serving gateway control plane entity and the load status of the serving gateway control plane entity,
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, or the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity is 0;
if the interface protocol type supported by the serving gateway control plane entity is matched with the service transmitted by the user equipment, and the load condition of the serving gateway control plane entity does not exceed a preset load threshold value, allocating weight to the serving gateway control plane entity according to a first formula, wherein the first formula is as follows:
wc＝1/Lc+μc
wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
Optionally, in an aspect of selecting a target serving gateway user plane entity for the user equipment from the plurality of serving gateway user plane entities, the serving gateway control plane entity may be specifically configured to:
acquiring a list of service gateway user plane entities available to user equipment; distributing weight to each service gateway user plane entity in the list; and determining the service gateway user plane entity with the maximum weight as a target service gateway user plane entity.
Optionally, in terms of obtaining the list of service gateway user plane entities available to the user equipment, the service gateway control plane entity may specifically be configured to:
a list of serving gateway user plane entities available to the user equipment as determined by the domain name server is obtained.
Optionally, in the aspect of assigning a weight to each serving gateway user plane entity in the list, the serving gateway control plane entity may specifically be configured to:
and distributing weight for each service gateway user plane entity in the list based on the interface protocol type supported by the service gateway user plane entity and the load condition of the service gateway user plane entity.
Optionally, in an aspect that a weight is allocated to each serving gateway user plane entity in the list based on an interface protocol type supported by the serving gateway user plane entity and a load condition of the serving gateway user plane entity, the serving gateway control plane entity may specifically be configured to:
if the interface protocol type supported by the service gateway user plane entity is not matched with the service transmitted by the user equipment, the weight distributed to the service gateway user plane entity by the target service gateway control plane entity is 0;
if the load condition of the service gateway user plane entity exceeds a preset load threshold value, the weight distributed by the target service gateway control plane entity for the service gateway user plane entity is also 0;
optionally, if the weight of the service gateway user plane entity is 0, the service gateway user plane entity is regarded as an invalid service gateway user plane entity, and is removed from the service gateway user plane entity list.
If the interface protocol type supported by the service gateway user plane entity is matched with the service transmitted by the user equipment, and the load of the service gateway user plane entity does not exceed the preset load threshold value, the target service gateway control plane entity distributes weight to the service gateway user plane entity according to a first formula, wherein the first formula is as follows:
wu＝1/Lu+μu
wherein, wuAs weight, L, of serving gateway user plane entity uuFor the load capacity, mu, of the service gateway user plane entity uuIs the correction factor corresponding to the serving gateway user plane entity u.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses (if any), and units (if any) may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus (if present), and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A method for serving gateway selection, comprising:
the mobile management entity selects a target service gateway control plane entity for the user equipment;
the mobile management entity sends a first bearer establishment request to the target service gateway control plane entity;
the target service gateway control plane entity responds to the first bearer establishment request and selects a target service gateway user plane entity for the user equipment;
the target service gateway control plane entity sends a second bearer establishment request to the target service gateway user plane entity;
wherein, the selecting, by the mobility management entity, a target serving gateway control plane entity for the user equipment includes:
the mobility management entity obtains a list of service gateway control plane entities available to the user equipment;
assigning a weight to each serving gateway control plane entity in the list, comprising: distributing weight for each service gateway control plane entity in the list based on the interface protocol type supported by the service gateway control plane entity and the load condition of the service gateway control plane entity;
determining the service gateway control plane entity with the largest weight as a target service gateway control plane entity;
wherein the allocating weights to each serving gateway control plane entity in the list based on the interface protocol type supported by the serving gateway control plane entity and the load condition of the serving gateway control plane entity includes:
if the interface protocol type supported by the service gateway control plane entity is matched with the service transmitted by the user equipment, and the load condition of the service gateway control plane entity does not exceed a preset load threshold value, allocating weight to the service gateway control plane entity according to a first formula, wherein the first formula is as follows: w is ac＝1/Lc+μc(ii) a Wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
2. The method of claim 1, wherein the obtaining, by the mobility management entity, the list of serving gateway control plane entities available to the user equipment comprises:
the mobility management entity obtains a list of serving gateway control plane entities available to the user equipment as determined by a domain name server.
3. The method of claim 1, wherein the assigning weights to each serving gateway control plane entity in the list based on the interface protocol type supported by the serving gateway control plane entity and the load condition of the serving gateway control plane entity comprises:
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, or the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity is 0.
4. A service gateway selection system comprising: the mobile management entity, at least one service gateway control plane entity connected with the mobile management entity, and a plurality of service gateway user plane entities connected with the at least one service gateway control plane entity; it is characterized in that the preparation method is characterized in that,
the mobile management entity is used for selecting a target service gateway control plane entity for user equipment from the at least one service gateway control plane entity and sending a first bearer establishment request to the target service gateway control plane entity;
the service gateway control plane entity is used for responding to a first bearer establishment request when receiving the first bearer establishment request, selecting a target service gateway user plane entity for the user equipment from the plurality of service gateway user plane entities, and sending a second bearer establishment request to the target service gateway user plane entity;
in the aspect of selecting a target serving gateway control plane entity for the user equipment from the at least one serving gateway control plane entity, the mobility management entity is configured to obtain a list of serving gateway control plane entities available to the user equipment; assigning a weight to each serving gateway control plane entity in the list, comprising: distributing weight for each service gateway control plane entity in the list based on the interface protocol type supported by the service gateway control plane entity and the load condition of the service gateway control plane entity; determining the service gateway control plane entity with the largest weight as a target service gateway control plane entity;
in an aspect that a weight is allocated to each serving gateway control plane entity in the list based on an interface protocol type supported by the serving gateway control plane entity and a load condition of the serving gateway control plane entity, the mobility management entity is configured to, if the interface protocol type supported by the serving gateway control plane entity matches with a service transmitted by the user equipment, and the load condition of the serving gateway control plane entity does not exceed a preset load threshold value, allocate the weight to the serving gateway control plane entity according to a first formula, where the first formula is: w is ac＝1/Lc+μc(ii) a Wherein, wcControlling the weight of the plane entity c for the serving gateway, LcControlling the load of the plane entity c, mu, for the serving gatewaycIs a correction factor corresponding to the serving gateway control plane entity c.
5. The system according to claim 4, wherein in obtaining the list of serving gateway control plane entities available to the user equipment, the mobility management entity is configured to,
obtaining a list of serving gateway control plane entities available to the user equipment as determined by a domain name server.
6. The system according to claim 4, wherein the mobility management entity is configured to assign a weight to each serving gateway control plane entity in the list based on the type of interface protocol supported by the serving gateway control plane entity and the load status of the serving gateway control plane entity,
if the interface protocol type supported by the service gateway control plane entity is not matched with the service transmitted by the user equipment, or the load condition of the service gateway control plane entity exceeds a preset load threshold value, the weight distributed to the service gateway control plane entity is 0.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610141227.7A CN105828315B (en) | 2016-03-11 | 2016-03-11 | Gateway selection method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610141227.7A CN105828315B (en) | 2016-03-11 | 2016-03-11 | Gateway selection method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105828315A CN105828315A (en) | 2016-08-03 |
| CN105828315B true CN105828315B (en) | 2019-06-04 |
Family
ID=56987206
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610141227.7A Active CN105828315B (en) | 2016-03-11 | 2016-03-11 | Gateway selection method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105828315B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107222899A (en) * | 2016-03-21 | 2017-09-29 | 中兴通讯股份有限公司 | The system of selection of user plane gateway and system |
| CN108307402A (en) * | 2016-08-31 | 2018-07-20 | 中兴通讯股份有限公司 | Manage the method, apparatus and system of UPF |
| WO2018076184A1 (en) * | 2016-10-25 | 2018-05-03 | 华为技术有限公司 | User plane selection method and apparatus, and storage medium |
| EP3528447B1 (en) | 2016-11-29 | 2020-11-11 | Huawei Technologies Co., Ltd. | Communication method and apparatus |
| WO2018129665A1 (en) * | 2017-01-10 | 2018-07-19 | 华为技术有限公司 | Communication method, network exposure function network element, and control plane network element |
| CN108512878B (en) | 2017-02-28 | 2021-01-29 | 华为技术有限公司 | Service management method and device |
| CN108924849B (en) * | 2017-04-01 | 2020-12-08 | 华为技术有限公司 | Session connection establishing method and control plane network element |
| CN108989194B (en) * | 2017-05-31 | 2021-07-09 | 微软技术许可有限责任公司 | Distributed IPSec gateway |
| CN109246778B (en) * | 2017-06-16 | 2020-12-04 | 华为技术有限公司 | Method for selecting functional network element and related equipment |
| CN109698800B (en) * | 2017-10-24 | 2022-05-10 | 中国电信股份有限公司 | Method, device and system for realizing control plane entity selection |
| CN110868762B (en) * | 2018-08-27 | 2022-04-12 | 华为技术有限公司 | Data stream processing method, device and system |
| CN110336746B (en) * | 2019-04-23 | 2020-07-14 | 东南大学成贤学院 | User plane node selection method, system and storage medium |
| CN111865621B (en) * | 2019-04-24 | 2021-12-03 | 华为技术有限公司 | Method and device for accessing gateway |
| CN112312426B (en) * | 2019-07-31 | 2023-07-21 | 中国移动通信集团吉林有限公司 | Selection method of core network gateway, mobility management entity and gateway device |
| CN112449317B (en) * | 2019-09-02 | 2022-06-10 | 华为技术有限公司 | Charging information reporting method and device |
| CN114124737B (en) * | 2020-08-25 | 2023-07-11 | 华为技术有限公司 | Method and device for controlling user equipment to access network |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323847A (en) * | 2014-07-04 | 2016-02-10 | 中国移动通信集团河北有限公司 | Communication method based on virtualized evolved packet core network, controller and virtual machine |
-
2016
- 2016-03-11 CN CN201610141227.7A patent/CN105828315B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105323847A (en) * | 2014-07-04 | 2016-02-10 | 中国移动通信集团河北有限公司 | Communication method based on virtualized evolved packet core network, controller and virtual machine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105828315A (en) | 2016-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105828315B (en) | Gateway selection method and system | |
| CN107113599B (en) | Communication device, core network node, system, computer program and method of rerouting NAS messages | |
| US9271165B2 (en) | Method for establishing connection by HNB | |
| US8824365B2 (en) | Method for establishing connection by HNB | |
| CN106912012B (en) | The selection method and control face entity of user entity in mobile communications network | |
| US8837326B2 (en) | Session management method and system based on M2M application, and apparatus | |
| US20160262073A1 (en) | System and method for providing maximum fill link via bonded services | |
| EP2843887A1 (en) | Communication system, and path control method | |
| CN104937978A (en) | Method and apparatus for controlling traffic in wireless communication system | |
| WO2011150564A1 (en) | Method, equipment and system for processing data gateway load | |
| KR101726357B1 (en) | Method and apparatus for updating application list for multi-path packet data service | |
| KR20170034314A (en) | Access Independent Converged Network System and Method thereof | |
| US10314101B2 (en) | Controlling wireless local area network access | |
| US20170318513A1 (en) | Communication device, communication method, communication system, and storage medium | |
| CN110831086B (en) | Method, device and system for sending indication information and storage medium | |
| CN103379555B (en) | A kind of communication system, apparatus and method | |
| KR102314382B1 (en) | Method and apparatus for providing multi-path packet data service | |
| US10524163B2 (en) | Base station, communication terminal, communication method, communication system, and storage medium | |
| US11057764B2 (en) | Communication device, communication method, communication system, and storage medium | |
| WO2013091499A1 (en) | Policy and charging rules function module selection method, system, and apparatus | |
| KR102315347B1 (en) | HSS(Home Subscriber Server) and HSS control method | |
| KR20210014350A (en) | Method and apparatus for managing subscriber profile | |
| US20170318512A1 (en) | Communication device, communication method, communication system, and storage medium | |
| KR20230157048A (en) | DATA GATEWAY DEVICE AND QoS CONTROL METHOD IN THE DEVICE, TERMINAL DEVICE | |
| CN102196500B (en) | Network element load control method and IP-CAN (Internet Protocol-Connectivity Access Network) network element |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20190403 Address after: 430205 No. 88, Academy of Posts Road, Hongshan District, Wuhan City, Hubei Province Applicant after: Wuhan Hongxin Communication Technology Co., ltd. Address before: 100085 No. 1 Building, No. 5 Hospital, Shangdi East Road, Haidian District, Beijing (Beacon Fire Science and Technology Building) Applicant before: Beifang Fenghuo Tech Co., Ltd., Beijing |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 430205 Hubei city of Wuhan province Jiangxia Hidden Dragon Island Tan lake two Road No. 1 Patentee after: CITIC Mobile Communication Technology Co., Ltd Address before: 430205, No. 88, postal academy road, Hongshan District, Hubei, Wuhan Patentee before: Wuhan Hongxin Telecommunication Technologies Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province Patentee after: CITIC Mobile Communication Technology Co.,Ltd. Address before: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province Patentee before: CITIC Mobile Communication Technology Co., Ltd |