CN109842956B - Service data routing method, service gateway and mobile management entity - Google Patents
Service data routing method, service gateway and mobile management entity Download PDFInfo
- Publication number
- CN109842956B CN109842956B CN201710883830.7A CN201710883830A CN109842956B CN 109842956 B CN109842956 B CN 109842956B CN 201710883830 A CN201710883830 A CN 201710883830A CN 109842956 B CN109842956 B CN 109842956B
- Authority
- CN
- China
- Prior art keywords
- service
- anchor point
- terminal
- data
- service anchor
- 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
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention relates to the technical field of communication, in particular to a routing method, a service gateway and a mobile management entity of service data, which comprises the following steps: a service gateway receives a session establishment request message sent by a Mobile Management Entity (MME); the service gateway establishes a tunnel with each service anchor point in each service anchor point respectively; the service gateway receives service data sent by the terminal; then the service gateway determines the service anchor point of the service data from a plurality of service anchor points corresponding to the terminal according to the attribute information of the service data; and finally, the service gateway routes the service data to the corresponding packet data network through the service anchor point. It can be seen that, in one APN, the service gateway can determine the service anchor point of the service data according to the service data stream from the plurality of service anchor points corresponding to the terminal, so as to select the optimal route for the terminal, thereby reducing the service delay, alleviating the problem of alternate routes, and reducing the load of the transmission network.
Description
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a service data routing method, a service gateway and a mobile management entity.
Background
Currently, a 4G (the 4 Generation mobile communication technology, fourth Generation mobile communication technology) mobile communication core network is called an evolved packet core network, and mainly includes an MME (Mobility Management Entity), an S-GW (Serving gateway) and a service anchor point P-GW (pdn gateway) network element, where the MME completes functions such as terminal access, authentication, Mobility Management, connection Management, and the like; the S-GW is a service gateway, is used as an anchor point for connecting eNodeBs (Evolved Node Bs) and a forwarding Node of services, and is responsible for handling the mobility of the terminal between the eNodeBs; the service anchor point P-GW is a PDN gateway, is a gateway node of a mobile core network connected to an external PDN, and is responsible for functions of terminal address allocation, terminal service data routing, service data and bearer mapping, service policy control and the like. According to the 3GPP (the 3rd Generation Partnership Project) protocol standard, there is one and only one service anchor Point P-GW within one APN (Access Point Name). If a plurality of Service anchors are used, a plurality of APNs need to be set, which results in increased complexity of terminal implementation, the terminal needs to have a plurality of sets of configuration data, such as a plurality of IP addresses, a plurality of TFTs (traffic flow templates), a plurality of Qos (Quality of Service) policies, and the like, and the selected APN needs to be designated when the terminal initiates a Service, and this designation is usually implemented by pre-configuration, and there is no good measurement to implement selecting a suitable APN according to a destination of the Service, which also results in that an APN mechanism is rarely used in an actual network.
For a terminal, within one APN, there is one and only one service anchor point P-GW. This P-GW is allocated by the mobility management node MME at the time of terminal attachment and remains unchanged for a longer time. The assignment of the service anchor point P-GW does not take into account the actual service to be performed by the terminal, as well as the location of the packet data network. Any traffic initiated by the terminal, wherever the packet data network is located, is routed through a fixed traffic route: and the terminal sends the service data packet to the eNB through an RB (Radio bearer), the eNB completely encapsulates the service data packet in a GTP tunnel and sends the service data packet to a service forwarding node S-GW, and the S-GW sends the service data packet to the P-GW.
In the existing network, there is only one P-GW corresponding to the UE in most cases, and the user accesses any service and forwards it through the service anchor point, as shown in fig. 1. In fig. 1, in the attach process of the terminal, the mobility management entity MME allocates a service anchor point P-GW1 to the terminal, and establishes a default bearer between the UE and the P-GW1, where in general, various services initiated by the terminal are transmitted through the bearer. This approach is independent of the traffic performed by the UE (User Equipment), and the traffic is forwarded via the service anchor point P-GW1 regardless of where the service server in the packet data network is located. As can be seen from fig. 1, the UE initiates three services, accessing three service servers located in the three packet data networks of PDN1, PDN2, PDN3, respectively. For the service server 2, the best service anchor point is P-GW2 from the routing relation point of view; for the service server 3, the best service anchor point is P-GW3, but with the current selection mechanism, only P-GW1 can be selected for the terminal, and P-GW1 is used to access service server 2 and service server 3, so that the delay of the service is increased because the route is not the best route, and the load of the transmission network is increased.
Disclosure of Invention
The embodiment of the invention provides a service data routing method, a service gateway and a mobile management entity, which are used for reducing service time delay and reducing the load of a transmission network.
The embodiment of the invention provides a routing method of service data, which comprises the following steps:
a service gateway receives a session creation request message sent by a Mobility Management Entity (MME), wherein the session creation request message carries service anchor points distributed by the MME for a terminal in the attachment process of the terminal;
the service gateway establishes a tunnel with each service anchor point in the service anchor points respectively, and the tunnel is used for transmitting service data;
the service gateway receives the service data sent by the terminal;
the service gateway determines the service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data;
and the service gateway routes the service data to the corresponding packet data network through the service anchor point.
Preferably, the session creation request message also carries service characteristics corresponding to each service anchor point;
the service gateway stores each service anchor point and the corresponding relation of the service characteristics corresponding to each service anchor point;
the service gateway determines the service anchor point of the service data according to the attribute information of the service data, and the method comprises the following steps:
and the service gateway determines the service anchor point of the service data according to the attribute information of the service data and the corresponding relation.
Preferably, the method further comprises the following steps:
if the service gateway does not find the service anchor point corresponding to the service data in the corresponding relationship, determining the service anchor point corresponding to the service data according to a local configuration rule of the service gateway; or
Sending a configuration request to the MME, wherein the configuration request carries attribute information of the service data, so that the MME determines a service anchor point corresponding to the service data.
The embodiment of the invention also provides a method for configuring the service data route, which comprises the following steps:
a mobile management entity MME allocates a plurality of service anchor points for a terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points;
and the MME sends the parameter information of the service anchors to a serving gateway so as to enable the serving gateway and the service anchors to respectively establish a tunnel, wherein the tunnel is used for the terminal to transmit corresponding service data.
Preferably, the allocating, by the MME, a plurality of service anchor points to the terminal in the terminal attach process includes:
in the terminal attachment process, the MME acquires the addresses of a plurality of service anchor points which are configured in advance from a Home Subscriber Server (HSS); alternatively, the first and second electrodes may be,
the MME locally acquires the addresses of a plurality of service anchor points which are configured in advance; alternatively, the first and second electrodes may be,
and the MME determines a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selects the addresses of a plurality of service anchor points from the service anchor point address list.
Preferably, before the MME acquires the addresses of the plurality of service anchors configured in advance from the home subscriber server HSS, the method further includes:
determining access data of each packet data network in the network;
and configuring the service anchor point corresponding to the packet data network with the access data larger than the first threshold value into the HSS or the MME.
Preferably, the selecting addresses of a plurality of service anchors from the service anchor address list includes:
selecting the address of the service anchor point corresponding to the packet data network with the front access data from the address list of the service anchor point; alternatively, the first and second electrodes may be,
and determining the position information of each service anchor point in the service anchor point address list, and selecting a plurality of service anchor points from the service anchor point address list according to the position information of the terminal and the position information of each service anchor point in the service anchor point address list.
Preferably, the terminal has the same address information in the service anchors by the following means:
pre-configuring the address of the terminal in the HSS; alternatively, the first and second electrodes may be,
and the MME informs a second service anchor point of the address distributed by the first service anchor point for the terminal, wherein the time for the terminal to access the second service anchor point lags behind the time for accessing the first service anchor point.
An embodiment of the present invention further provides a service gateway, including:
a receiving module, configured to receive a session creation request message sent by a mobility management entity MME, where the session creation request message carries service anchors allocated by the MME to a terminal in an attachment process of the terminal;
a determining module, configured to establish a tunnel with each of the service anchors respectively, where the tunnel is used to transmit service data;
the receiving module is further configured to receive service data sent by the terminal;
the determining module is further configured to determine a service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data;
and the routing module is used for routing the service data to the corresponding packet data network through the service anchor point.
Preferably, the session creation request message also carries service characteristics corresponding to each service anchor point;
the determining module is used for storing the service anchor points and the corresponding relation of the service characteristics corresponding to the service anchor points;
the determining module is specifically configured to:
and determining the service anchor point of the service data according to the attribute information of the service data and the corresponding relation.
Preferably, the determining module is further configured to:
if the service anchor point corresponding to the service data is not found in the corresponding relation, determining the service anchor point corresponding to the service data according to a local configuration rule; or
Sending a configuration request to the MME, wherein the configuration request carries attribute information of the service data, so that the MME determines a service anchor point corresponding to the service data.
An embodiment of the present invention further provides a mobility management entity, including:
the distribution module is used for distributing a plurality of service anchor points for the terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points;
and the sending module is used for sending the parameter information of the service anchors to a service gateway so as to enable the service gateway and the service anchors to respectively establish a tunnel, and the tunnel is used for the terminal to transmit corresponding service data.
Preferably, the allocation module is specifically configured to:
in the terminal attachment process, acquiring the addresses of a plurality of service anchor points configured in advance from a Home Subscriber Server (HSS); alternatively, the first and second electrodes may be,
acquiring addresses of a plurality of service anchor points which are configured in advance from local; alternatively, the first and second electrodes may be,
determining a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selecting the addresses of a plurality of service anchor points from the service anchor point address list.
Preferably, the allocation module is further configured to:
before the addresses of a plurality of service anchors configured in advance are obtained from a Home Subscriber Server (HSS), the access data of each packet data network in the network is determined, and the service anchor corresponding to the packet data network with the access data larger than a first threshold value is configured to the HSS or the mobile management entity.
Preferably, the allocation module is specifically configured to:
selecting the address of the service anchor point corresponding to the packet data network with the front access data from the address list of the service anchor point; alternatively, the first and second electrodes may be,
and determining the position information of each service anchor point in the service anchor point address list, and selecting a plurality of service anchor points from the service anchor point address list according to the position information of the terminal and the position information of each service anchor point in the service anchor point address list.
Preferably, the terminal has the same address information in the service anchors by the following means:
pre-configuring the address of the terminal in the HSS; alternatively, the first and second electrodes may be,
and the mobile management entity informs a second service anchor point of the address distributed by the first service anchor point for the terminal, wherein the time for the terminal to access the second service anchor point lags behind the time for accessing the first service anchor point.
The method for configuring service data routing and the mobility management entity provided in the foregoing embodiments include: a mobile management entity MME allocates a plurality of service anchor points for a terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points; then, the MME sends the parameter information of the service anchors to a serving gateway, so that the serving gateway and the service anchors respectively establish a tunnel, and the tunnel is used for the terminal to transmit corresponding service data. It can be seen that the allocation of multiple service anchors to the terminal can be completed on the network side without any influence on the terminal, and since multiple service anchors are allocated to the terminal, the optimal routing can be selected for the service data of the terminal in one APN, and since the optimal routing can be selected for the service data of the terminal, the service delay can be reduced, the problem of circuitous routing can be alleviated, and the load of a transmission network can be reduced.
The routing method and the serving gateway for the service data provided by the above embodiments include: a service gateway receives a session creation request message sent by a Mobility Management Entity (MME), wherein the session creation request message carries service anchor points distributed by the MME for a terminal in the attachment process of the terminal; the service gateway establishes a tunnel with each service anchor point in the service anchor points respectively, and the tunnel is used for transmitting service data; the service gateway receives service data sent by the terminal; then the service gateway determines the service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data; and finally, the service gateway routes the service data to the corresponding packet data network through the service anchor point. It can be seen that, in one APN, the service gateway can determine the service anchor point of the service data from the plurality of service anchor points corresponding to the terminal according to the service data stream, so as to select the optimal route for the terminal.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described below.
Fig. 1 is a schematic structural diagram of service forwarding through a service anchor point in the prior art according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a method for configuring a service data route according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a method for an MME to allocate multiple service anchors for a terminal according to an embodiment of the present invention;
fig. 4 is a schematic flow chart of a method for establishing a user plane service tunnel for a terminal according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a service data routing method according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of service forwarding through multiple service anchors according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service gateway according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a mobility management entity according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more clearly apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Fig. 2 illustrates an example of a method for configuring service data routing provided in an embodiment of the present invention, and as shown in fig. 2, the method may include:
s201, an MME allocates a plurality of service anchor points for a terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points.
Specifically, the address of the terminal may be preconfigured in the HSS, so that the terminal has the same address information in the plurality of service anchors. The MME can also inform a second service anchor point of the address allocated to the terminal by the first service anchor point so as to realize that the terminal has the same address information in the plurality of service anchor points, wherein the time for accessing the second service anchor point by the terminal lags behind the time for accessing the first service anchor point.
S202, the MME sends the parameter information of the service anchors to the service gateway so that the service gateway and the service anchors respectively establish tunnels for the terminal to transmit corresponding service data.
Specifically, in the terminal attachment process, the MME may obtain a plurality of service anchors configured in advance from an HSS (Home Subscriber Server) to implement allocating the plurality of service anchors to the terminal; the MME can also locally acquire the addresses of a plurality of service anchor points which are configured in advance so as to realize the allocation of the plurality of service anchor points for the terminal; the MME can also determine a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selects the addresses of a plurality of service anchor points from the service anchor point address list.
Optionally, before the MME acquires the pre-configured multiple service anchors from the HSS, the user access data of each packet data network in the network may also be determined, and the service anchor corresponding to the packet data network whose user access data is greater than the first threshold is configured in the HSS or the MME.
Preferably, the MME may also adopt the following method flow shown in fig. 3 to allocate a plurality of service anchor points to the terminal.
S301, the MME receives an attachment request message sent by the UE.
S302, the MME determines whether the UE configures addresses of a plurality of service anchor points in the HSS, if so, the process goes to step S303, otherwise, the process goes to step S304.
S303, the MME acquires the addresses of a plurality of service anchor points of the UE from the HSS.
S304, the MME determines whether addresses of a plurality of service anchor points of the UE are configured locally, if so, goes to step S305, otherwise, goes to step S306.
S305, the MME locally acquires the addresses of a plurality of service anchor points which are configured in advance.
S306, MEE determines whether the UE configures the APN parameter in the HSS, if yes, go to step S209, otherwise, go to step S307.
S307, the MME judges whether the attach request message sent by the UE carries APN parameters, if so, the step is switched to S309, otherwise, the step is switched to S308.
S308, the MME uses the APN parameters configured locally.
S309, MME constructs FQDN (Fully Qualified Domain Name/full Name Domain Name) by using APN, then uses the FQDN to initiate Domain Name resolution request to DNS (Domain Name System), and DNS returns address list of service anchor points configured by operator and service characteristic information of each service anchor point.
The service feature information of each service anchor point may include, but is not limited to: the priority of the service anchor point, the weight factor, the location information, the port number, the protocol type, etc.
S310, the MME selects the addresses of a plurality of service anchors from the address list of the service anchors according to the address list of the service anchors and the service characteristic information of each service anchor.
Optionally, when the MME selects addresses of multiple service anchors in the address list of the service anchors, the MME may select an address of a service anchor corresponding to a packet data network with earlier access data.
Optionally, the MME may further determine location information of each service anchor in the service anchor address list, then combine the location information of the terminal with the location information of each service anchor, and select a plurality of service anchors close to the terminal side from the service anchor address list, so as to reduce service delay and transmission network load.
Optionally, when selecting multiple service anchors from the service anchor address list, the MME may select service anchors corresponding to several service networks with access data before considering the geographic location of the terminal and the statistical data of accessing each packet data network, for the terminal.
When the MME selects multiple service anchors from the service anchor address list, it may also make corresponding policies according to the core network structure of the operator and the services provided by the operator, such as: an operator has a service Network, a Network providing an IMS (IP Multimedia Subsystem) service, a Network accessing an Internet service, a CDN (Content Delivery Network) implementing Content Delivery at different locations, a Network providing a local service distributed at different geographical locations, and the like. These networks either provide different services to the users or are distributed over different locations to achieve load sharing and content acceleration. Since the service networks are built by the operators, the operators are aware of the services that each network can provide and the location distribution thereof. Each service network may be described by the address, port, type of service of the service server provided, and the distribution location of the service server.
After the service anchor selection is completed, the MME triggers the service forwarding node S-GW to establish a user plane service GTP (GPRS tunneling Protocol) tunnel by creating a Session Request (Create Session Request) message, and a message interaction flow is as shown in fig. 4 below.
S401, MME receives an attach request message sent by UE through eNodeB.
S402, the MME selects a plurality of service anchor points for the UE.
S403, the MME sends a first creating session request message to the S-GW.
The first creating session request message may carry parameters such as a service anchor address list, a service feature list corresponding to each service anchor, a bearer identifier, an APN, and a Qos.
If the address of the UE is statically configured in advance in the HSS, the first create session request message may also carry a PDN (Packet Data Network) address, where the PDN address is a terminal address, and therefore, the address of the terminal may be sent to each service anchor point by the MME according to the parameter, so as to ensure that the UE has the same address information in multiple service anchor points.
S404, after receiving a first session creation request message sent by MME, S-GW allocates S1 interface Tunnel identifiers, and allocates S5/S8 interface Tunnel identifiers TEID (Tunnel End point ID, Tunnel endpoint identifier) to each service anchor point according to a plurality of service anchor points selected for UE, and configures a local End Tunnel; and storing the service characteristic information corresponding to each service anchor point for the subsequent forwarding of the user service carried in the GTP tunnel.
S405, the S-GW sends a second session establishment request message to each service anchor point.
The second session request message carries parameters such as tunnel identifier TEID, bearer identifier, APN, Qos (Quality of Service), etc. of the S5/S8 interface allocated by the S-GW to each Service anchor.
If the address of the UE is statically configured in advance in the HSS, the second create session request message may also carry a PDN (Packet Data Network) address, where the PDN address is a terminal address, and therefore, the address of the terminal may be sent to each service anchor point by the MME according to the parameter, so as to ensure that the UE has the same address information in multiple service anchor points.
S406, after each service anchor point receives the second session creation request message sent by the S-GW, the forwarding plane tunnel parameters are configured.
S407, each service anchor point respectively sends a first session establishing response message to the S-GW.
If the address of the UE is statically configured in advance in the HSS, the first create session response message may carry the address of the UE statically configured in advance in the HSS, and if the address of the UE is not statically configured in advance in the HSS, after receiving the second create session request message sent by the S-GW, each service anchor point also needs to allocate an address to the terminal, and send the address allocated to the terminal to the S-GW through the first create session response message.
When the address of the UE is not statically configured in advance in the HSS, the first service anchor point can send the address allocated to the terminal to the S-GW through the first session creation response message, and then the S-GW sends the address allocated to the MME, and then the MME informs the second service anchor point of the address allocated to the terminal by the first service anchor point so as to realize that the terminal has the same address information in the plurality of service anchor points, wherein the time for the terminal to access the second service anchor point lags behind the time for the terminal to access the first service anchor point.
S408, after receiving the first session creating response message of each service anchor point, the S-GW sends a second session creating response message to the MME.
Wherein, the second session creating message may carry parameters such as S1 interface tunnel parameter, S-GW tunnel parameter, and terminal IP address.
S409, MME receives the attachment completion message sent by eNodeB in the UE attachment process.
S410, after receiving an attachment completion message sent by an eNodeB in a UE attachment process, an MME configures tunnel parameters at an eNodeB side to a serving gateway S-GW through a modification Bearer Request (Modify Bearer Request) message.
According to the above, it can be seen that, through the service data routing configured by the method, in the terminal, the eNodeB and the S-GW are one path, and one path exists between the S-GW and each service anchor point, so that a plurality of service forwarding paths are formed between the S-GW and a plurality of service anchor points. The mobile management entity carries service characteristics corresponding to the P-GW for providing services when configuring each service anchor point P-GW, the S-GW distributes service data streams received from the S1 to GTP tunnels corresponding to different service anchor points according to the service characteristics of each service anchor point, and therefore the fact that a plurality of service anchor points are distributed to a terminal on a network side can be achieved without any influence on the terminal.
Based on the method for configuring the service data routing provided in the foregoing embodiment, an embodiment of the present invention further provides a method for routing service data, as shown in fig. 5, where the method may include:
s501, the service gateway receives a session creating request message sent by a Mobility Management Entity (MME), wherein the session creating request message carries all service anchors distributed by the MME for the terminal in the attachment process of the terminal.
Creating parameters such as a portable service anchor point address list, a bearing identifier, an APN, a Qos and the like in the session request message. If the address of the UE is statically configured in advance in the HSS, the create session request message may also carry a PDN (Packet Data Network) address, where the PDN address is a terminal address, and therefore, the address of the terminal may be sent to each service anchor point by the MME according to the parameter, so as to ensure that the UE has the same address information in each service anchor point.
Then, the service gateway may allocate an S1 interface Tunnel identifier, allocate an S5/S8 interface Tunnel identifier TEID (Tunnel End point ID, Tunnel endpoint identifier) for each service anchor point, and configure the local End Tunnel; and storing the service characteristic information corresponding to each service anchor point for forwarding the user service loaded in the GTP tunnel.
S502, the service gateway establishes a tunnel with each service anchor point in each service anchor point respectively, and the tunnel is used for transmitting service data.
S503, the service gateway receives the service data sent by the terminal.
S504, the service gateway determines the service anchor point of the service data from the service anchor points corresponding to the terminal according to the attribute information of the service data.
And S505, the service gateway routes the service data to the corresponding packet data network through the selected service anchor point.
Optionally, the session creation request message may also carry service features corresponding to each service anchor, that is, the session creation request message may carry addresses, ports, service types, and the like of the packet data networks corresponding to each service anchor. The service gateway stores each service anchor point and the corresponding relation of the service characteristics corresponding to each service anchor point, and then the service gateway determines the service anchor point of the service data according to the attribute information and the corresponding relation of the service data.
Optionally, the created session request message may also carry a location information list of each service anchor point, that is, the created session request message may carry location information of each service anchor point, and then the service gateway combines the location information of the terminal and the location information of each service anchor point, and selects a service anchor point close to the terminal side, so as to reduce service delay and transmission network load.
Optionally, the serving gateway may further select a service anchor point closer to the packet data network to which the terminal needs to access according to a destination address used by the terminal to initiate the service, for example, according to an IP address used by the terminal to initiate the service, so as to reduce service delay and transmission network load.
Optionally, the service gateway further performs deep parsing on the service data stream of the terminal, and selects a service anchor point according to more specific service characteristics, thereby implementing effective distribution of the service stream.
When the service gateway distributes the service flow of the terminal according to the service characteristics of the service anchor point, if the service gateway does not find the service anchor point corresponding to the service data in the corresponding relationship, the service gateway can also determine the service anchor point corresponding to the service data according to the local configuration rule. The local configuration rule may be periodically updated by the mobility management entity or other external devices according to information such as new service deployment, service adjustment, network structure adjustment, and the like.
When the service gateway distributes the service flow of the terminal according to the service characteristics of the service anchor point, if the service gateway does not find the service anchor point corresponding to the service data in the corresponding relation, a new control plane message can be added between the mobile management entity and the service gateway, the characteristics of the service flow which can not be distinguished are forwarded to the MME through the newly added control message, and the MME makes a decision.
Whether the service anchor is selected according to the local configuration rule of the serving gateway or by the decision of the MME, it is possible to modify the service characteristics corresponding to the existing service anchor or add a new service anchor. If the service characteristics of the existing service anchor point are modified, the service gateway performs local recording for subsequent service flow distribution, and if a new service anchor point needs to be added, the processing procedure can be divided into the following two cases:
case 1
And the MME decides to add a new service anchor point, and the MME sends a session establishment request message to the service gateway, wherein the message carries a new service anchor point address and service characteristics. After receiving the message, the service gateway allocates tunnel parameters of the S5/S8 interface to the new service anchor point, stores service characteristics for forwarding service flow, and then sends a message to the corresponding service anchor point to establish a service tunnel of the S5/S8 interface.
Case 2
And the service gateway establishes a new service anchor point according to a local strategy, then allocates tunnel parameters of an S5/S8 interface of the local terminal, stores service characteristics for forwarding service flows, then sends a message to the corresponding service anchor point, establishes a service tunnel of an S5/S8 interface, and after the establishment is finished, needs to inform the MME of parameters such as newly-added service anchor point addresses and service characteristic information.
The above-described method flow is explained below by a specific example.
Referring to fig. 6, it is assumed that the MME allocates three service anchor points, P-GW1, P-GW2, and P-GW3, to the UE during the UE attach process. The MME sends three service anchor points of P-GW1, P-GW2 and P-GW3 allocated to the UE to the S-GW through a create session request message, then three service paths are respectively established between the S-GW and the P-GW1, between the P-GW2 and between the S-GW 3, assuming that the service path between the S-GW and the P-GW1 is a service path 1, the service path between the S-GW and the P-GW2 is a service path 2, the service path between the S-GW and the P-GW3 is a service path 3, after the S-GW receives the service packet 1 sent by the UE, it is assumed that the P-GW1 is determined as a service anchor of the service packet 1 according to the attribute information of the service packet 1 and the service characteristics of the service servers corresponding to the P-GW1, the P-GW2, and the P-GW3, the S-GW may route the traffic data packet to the traffic server 1 through the traffic path 1.
Similarly, after the S-GW receives the service data packet 2 sent by the UE, assuming that the P-GW2 is determined to be a service anchor point of the service data packet 2 according to the attribute information of the service data packet 2 and the service characteristics of the service servers corresponding to the P-GW1, the P-GW2, and the P-GW3, the S-GW may route the service data packet to the service server 2 through the service path 1; after the S-GW receives the service data packet 3 sent by the UE, assuming that the P-GW2 is determined to be a service anchor point of the service data packet 3 according to the attribute information of the service data packet 3 and the service characteristics of the service servers corresponding to the P-GW1, the P-GW2, and the P-GW3, the S-GW may route the service data packet to the service server 3 through the service path 3.
It should be noted that, since the terminal has the same address information in the P-GWs and the same address information has the same routing relationship when mapping the routing relationship, in order to ensure that the P-GWs have different routing relationships after mapping according to the address information of the terminal, the routing relationship needs to be modified at the P-GW.
According to the above contents, in one APN, the service gateway can determine the service anchor point of the service data from the plurality of service anchor points corresponding to the terminal according to the service data stream, so as to select the optimal route for the terminal.
Based on the same technical concept, an embodiment of the present invention further provides a service gateway, as shown in fig. 7, the fail service gateway may include:
a receiving module 701, configured to receive a session creation request message sent by a mobility management entity MME, where the session creation request message carries service anchors allocated by the MME to a terminal in an attachment process of the terminal;
a determining module 702, configured to establish a tunnel with each of the service anchors respectively, where the tunnel is used to transmit service data;
the receiving module 701 is further configured to receive service data sent by a terminal;
a determining module 702, configured to determine, according to the attribute information of the service data, a service anchor point of the service data from each service anchor point corresponding to the terminal;
a routing module 703, configured to route the service data to a corresponding packet data network through the service anchor.
Preferably, the receiving module 701 is further configured to: before receiving service data sent by a terminal, receiving a session creation request message sent by a Mobility Management Entity (MME), wherein the session creation request message carries service anchor points distributed by the MME to the terminal in the attachment process of the terminal;
the determining module is further configured to establish a tunnel with each of the service anchors respectively, where the tunnel is used to transmit service data.
Preferably, the session creation request message also carries service characteristics corresponding to each service anchor point;
a determining module 702, configured to store service anchor points and corresponding service features corresponding to the service anchor points;
the determining module 702 is specifically configured to:
and determining the service anchor point of the service data according to the attribute information of the service data and the corresponding relation.
Preferably, the determining module 702 is further configured to:
if the service anchor point corresponding to the service data is not found in the corresponding relation, determining the service anchor point corresponding to the service data according to a local configuration rule; alternatively, the first and second electrodes may be,
sending a configuration request to the MME, wherein the configuration request carries attribute information of the service data, so that the MME determines a service anchor point corresponding to the service data.
An embodiment of the present invention further provides a mobility management entity, as shown in fig. 8, where the mobility management entity may include:
an allocating module 801, configured to allocate multiple service anchors to a terminal in a terminal attachment process; the terminal has the same address information in the plurality of service anchor points;
a sending module 802, configured to send the parameter information of the multiple service anchors to a serving gateway, so that the serving gateway and the multiple service anchors respectively establish a tunnel, where the tunnel is used for the terminal to transmit corresponding service data.
Preferably, the allocating module 801 is specifically configured to:
in the terminal attachment process, acquiring the addresses of a plurality of service anchor points configured in advance from a Home Subscriber Server (HSS); alternatively, the first and second electrodes may be,
acquiring addresses of a plurality of service anchor points which are configured in advance from local; alternatively, the first and second electrodes may be,
determining a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selecting the addresses of a plurality of service anchor points from the service anchor point address list.
Preferably, the allocating module 801 is further configured to:
before the address of a plurality of service anchor points configured in advance is obtained from a Home Subscriber Server (HSS), determining the access data of each packet data network in the network, and configuring the service anchor point corresponding to the packet data network with the service access data larger than a first threshold value into the HSS or the mobile management entity.
Preferably, the allocating module 801 is specifically configured to:
selecting the address of the service anchor point corresponding to the packet data network with the front access data from the address list of the service anchor point; alternatively, the first and second electrodes may be,
and determining the position information of each service anchor point in the service anchor point address list, and selecting a plurality of service anchor points from the service anchor point address list according to the position information of the terminal and the position information of each service anchor point in the service anchor point address list.
Preferably, the terminal has the same address information in the service anchors by the following means:
pre-configuring the address of the terminal in the HSS; alternatively, the first and second electrodes may be,
and the mobile management entity informs a second service anchor point of the address distributed by the first service anchor point for the terminal, wherein the time for the terminal to access the second service anchor point lags behind the time for accessing the first service anchor point.
It should be noted that, in the embodiment of the present invention, the user service includes, but is not limited to, one of the following services: the terminal accesses the network to establish data connection, the network forwards the terminal service data, or the network processes the terminal service data, etc. In the embodiment of the present invention, the user service may be referred to as "service" for short, and the concepts of the two are equivalent. User data, which may also be referred to as "service data," is data that is transmitted between a terminal and a network for carrying a specific user service, and is distinguished from control signaling, which is signaling that is transmitted between the terminal and the network for implementing connection control, network security, bearer allocation, and the like, and inside the network.
The PDN in the embodiment of the present invention is an external packet data network to which a gateway is connected, and may be an Internet (Internet), a Virtual Private Network (VPN), an Internet Protocol (IP) multimedia Service (IMS) network, or a Wireless Application Protocol (WAP) network provided by an operator.
The communication system applicable to the embodiment of the invention includes but is not limited to: global System for Mobile communications (GSM), Code Division Multiple Access (CDMA) IS-95, Code Division Multiple Access (CDMA) 2000, Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), Time Division duplex-Long Term Evolution (TDD LTE), Frequency Division duplex-Long Term Evolution (FDD), Long Term Evolution (Long Term Evolution-Evolution), LTE-Mobile, Personal Mobile phone (WiFi-held), Wireless internet protocol (WiFi-802), Wireless internet protocol (WiFi-11), WiMAX), and various wireless communication systems that evolve in the future.
In embodiments of the present invention, a terminal may be a wireless terminal, which may be a device providing voice and/or data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. Wireless terminals, which may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers having mobile terminals, such as portable, pocket, hand-held, computer-included, or vehicle-mounted mobile devices, may communicate with one or more core networks via a Radio Access Network (e.g., RAN). For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. A wireless Terminal may also be referred to as a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), an Access Point (Access Point), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), a User Device (User Device), or a User Equipment (User Equipment).
To sum up, the method for configuring service data routing and the mobility management entity provided in the foregoing embodiments include: a mobile management entity MME allocates a plurality of service anchor points for a terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points; then, the MME sends the parameter information of the service anchors to a serving gateway, so that the serving gateway and the service anchors respectively establish a tunnel, and the tunnel is used for the terminal to transmit corresponding service data. It can be seen that the allocation of multiple service anchors to the terminal can be completed on the network side without any influence on the terminal, and since multiple service anchors are allocated to the terminal, the optimal routing can be selected for the service data of the terminal in one APN, and since the optimal routing can be selected for the service data of the terminal, the service delay can be reduced, the problem of circuitous routing can be alleviated, and the load of a transmission network can be reduced.
The routing method and the serving gateway for the service data provided by the above embodiments include: a service gateway receives a session creation request message sent by a Mobility Management Entity (MME), wherein the session creation request message carries service anchor points distributed by the MME for a terminal in the attachment process of the terminal; the service gateway establishes a tunnel with each service anchor point in the service anchor points respectively, and the tunnel is used for transmitting service data; the service gateway receives service data sent by the terminal; then the service gateway determines the service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data; and finally, the service gateway routes the service data to the corresponding packet data network through the service anchor point. It can be seen that, in one APN, the service gateway can determine the service anchor point of the service data from the plurality of service anchor points corresponding to the terminal according to the service data stream, so as to select the optimal route for the terminal.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (16)
1. A method for routing service data is characterized by comprising the following steps:
a service gateway receives a session creation request message sent by a Mobility Management Entity (MME), wherein the session creation request message carries service anchor points distributed by the MME for a terminal in the attachment process of the terminal;
the service gateway establishes a tunnel with each service anchor point in the service anchor points respectively, and the tunnel is used for transmitting service data;
the service gateway receives the service data sent by the terminal;
the service gateway determines the service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data;
and the service gateway routes the service data to the corresponding packet data network through the service anchor point.
2. The method of claim 1, wherein the create session request message further carries service characteristics corresponding to each service anchor;
the service gateway stores each service anchor point and the corresponding relation of the service characteristics corresponding to each service anchor point;
the service gateway determines the service anchor point of the service data according to the attribute information of the service data, and the method comprises the following steps:
and the service gateway determines the service anchor point of the service data according to the attribute information of the service data and the corresponding relation.
3. The method of claim 2, further comprising:
if the service gateway does not find the service anchor point corresponding to the service data in the corresponding relationship, determining the service anchor point corresponding to the service data according to a local configuration rule of the service gateway; or
Sending a configuration request to the MME, wherein the configuration request carries attribute information of the service data, so that the MME determines a service anchor point corresponding to the service data.
4. A method for configuring a service data route, comprising:
a mobile management entity MME allocates a plurality of service anchor points for a terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points;
the MME sends the parameter information of the service anchors to a service gateway so that the service gateway and the service anchors respectively establish tunnels, the tunnels are used for the terminal to transmit corresponding service data, the attribute information of the service data is used for the service gateway to determine the service anchor of the service data from the service anchors corresponding to the terminal, and the service anchor of the service data is used for the service gateway to route the service data to a corresponding packet data network.
5. The method of claim 4, wherein the Mobility Management Entity (MME) allocates a plurality of service anchors to the terminal during the terminal attach procedure, comprising:
in the terminal attachment process, the MME acquires the addresses of a plurality of service anchor points which are configured in advance from a Home Subscriber Server (HSS); alternatively, the first and second electrodes may be,
the MME locally acquires the addresses of a plurality of service anchor points which are configured in advance; alternatively, the first and second electrodes may be,
and the MME determines a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selects the addresses of a plurality of service anchor points from the service anchor point address list.
6. The method of claim 5, prior to the MME obtaining addresses of a plurality of pre-configured service anchors from a Home Subscriber Server (HSS), further comprising:
determining access data of each packet data network in the network;
and configuring the service anchor point corresponding to the packet data network with the access data larger than the first threshold value into the HSS or the MME.
7. The method of claim 5, wherein said selecting the addresses of the plurality of service anchors from the list of service anchor addresses comprises:
selecting the address of the service anchor point corresponding to the packet data network with the front access data from the address list of the service anchor point; alternatively, the first and second electrodes may be,
and determining the position information of each service anchor point in the service anchor point address list, and selecting a plurality of service anchor points from the service anchor point address list according to the position information of the terminal and the position information of each service anchor point in the service anchor point address list.
8. The method of claim 5, wherein the terminal having the same address information in the plurality of service anchors is implemented by:
pre-configuring the address of the terminal in the HSS; alternatively, the first and second electrodes may be,
and the MME informs a second service anchor point of the address distributed by the first service anchor point for the terminal, wherein the time for the terminal to access the second service anchor point lags behind the time for accessing the first service anchor point.
9. A serving gateway, comprising:
a receiving module, configured to receive a session creation request message sent by a mobility management entity MME, where the session creation request message carries service anchors allocated by the MME to a terminal in an attachment process of the terminal;
a determining module, configured to establish a tunnel with each of the service anchors respectively, where the tunnel is used to transmit service data;
the receiving module is further configured to receive service data sent by the terminal;
the determining module is further configured to determine a service anchor point of the service data from each service anchor point corresponding to the terminal according to the attribute information of the service data;
and the routing module is used for routing the service data to the corresponding packet data network through the service anchor point.
10. The serving gateway of claim 9, wherein the create session request message further carries service characteristics corresponding to each service anchor;
the determining module is used for storing the service anchor points and the corresponding relation of the service characteristics corresponding to the service anchor points;
the determining module is specifically configured to:
and determining the service anchor point of the service data according to the attribute information of the service data and the corresponding relation.
11. The serving gateway of claim 10, wherein the determining module is further to:
if the service anchor point corresponding to the service data is not found in the corresponding relation, determining the service anchor point corresponding to the service data according to a local configuration rule; or
Sending a configuration request to the MME, wherein the configuration request carries attribute information of the service data, so that the MME determines a service anchor point corresponding to the service data.
12. A mobility management entity, comprising:
the distribution module is used for distributing a plurality of service anchor points for the terminal in the terminal attachment process; the terminal has the same address information in the plurality of service anchor points;
a sending module, configured to send parameter information of the multiple service anchors to a service gateway, so that the service gateway and the multiple service anchors respectively establish a tunnel, where the tunnel is used for the terminal to transmit corresponding service data, attribute information of the service data is used for the service gateway to determine the service anchor of the service data from each service anchor corresponding to the terminal, and the service anchor of the service data is used for the service gateway to route the service data to a corresponding packet data network.
13. The mobility management entity of claim 12, wherein the assignment module is specifically configured to:
in the terminal attachment process, acquiring the addresses of a plurality of service anchor points configured in advance from a Home Subscriber Server (HSS); alternatively, the first and second electrodes may be,
acquiring addresses of a plurality of service anchor points which are configured in advance from local; alternatively, the first and second electrodes may be,
determining a service anchor point address list according to the APN parameters configured locally or the APN parameters carried by the terminal, and selecting the addresses of a plurality of service anchor points from the service anchor point address list.
14. The mobility management entity of claim 13, wherein the assignment module is further configured to:
before the addresses of a plurality of service anchors configured in advance are obtained from a Home Subscriber Server (HSS), the access data of each packet data network in the network is determined, and the service anchor corresponding to the packet data network with the access data larger than a first threshold value is configured to the HSS or the mobile management entity.
15. The mobility management entity of claim 13, wherein the assignment module is specifically configured to:
selecting the address of the service anchor point corresponding to the packet data network with the front access data from the address list of the service anchor point; alternatively, the first and second electrodes may be,
and determining the position information of each service anchor point in the service anchor point address list, and selecting a plurality of service anchor points from the service anchor point address list according to the position information of the terminal and the position information of each service anchor point in the service anchor point address list.
16. The mobility management entity according to claim 13, characterized in that the terminal having the same address information in the plurality of service anchors is implemented by:
pre-configuring the address of the terminal in the HSS; alternatively, the first and second electrodes may be,
and the mobile management entity informs a second service anchor point of the address distributed by the first service anchor point for the terminal, wherein the time for the terminal to access the second service anchor point lags behind the time for accessing the first service anchor point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710883830.7A CN109842956B (en) | 2017-09-26 | 2017-09-26 | Service data routing method, service gateway and mobile management entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710883830.7A CN109842956B (en) | 2017-09-26 | 2017-09-26 | Service data routing method, service gateway and mobile management entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109842956A CN109842956A (en) | 2019-06-04 |
| CN109842956B true CN109842956B (en) | 2021-04-16 |
Family
ID=66876214
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710883830.7A Active CN109842956B (en) | 2017-09-26 | 2017-09-26 | Service data routing method, service gateway and mobile management entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109842956B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109039950A (en) * | 2018-09-20 | 2018-12-18 | 四川警盛科技有限公司 | Business service system and method |
| CN112312426B (en) * | 2019-07-31 | 2023-07-21 | ***通信集团吉林有限公司 | Core network gateway selection method, mobility management entity and gateway equipment |
| CN113543270A (en) * | 2020-04-16 | 2021-10-22 | 华为技术有限公司 | Data transmission method and communication device |
| CN117136599A (en) * | 2021-07-12 | 2023-11-28 | Oppo广东移动通信有限公司 | Positioning method, device, equipment and medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102017719A (en) * | 2008-03-25 | 2011-04-13 | 北方电讯网络有限公司 | Method and system for maintaining multiple PDN network connection during inter-technology handover in idle mode |
| CN102917443A (en) * | 2012-10-23 | 2013-02-06 | 中国联合网络通信集团有限公司 | Method and device for selecting gateway and transmitting information, and network system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101686191A (en) * | 2008-09-24 | 2010-03-31 | 华为技术有限公司 | Method for accessing packet data network service, system, gateway and terminal |
| KR101575223B1 (en) * | 2008-11-25 | 2015-12-09 | 삼성전자주식회사 | Method and system for requesting local breakout in session home enhanced node b |
| CN102342144B (en) * | 2009-03-04 | 2015-09-02 | 思科技术公司 | Overload in Sampling network equipment |
| CN102238629A (en) * | 2010-05-07 | 2011-11-09 | 华为技术有限公司 | Access control method for machine type communication, equipment and communication system |
-
2017
- 2017-09-26 CN CN201710883830.7A patent/CN109842956B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102017719A (en) * | 2008-03-25 | 2011-04-13 | 北方电讯网络有限公司 | Method and system for maintaining multiple PDN network connection during inter-technology handover in idle mode |
| CN102917443A (en) * | 2012-10-23 | 2013-02-06 | 中国联合网络通信集团有限公司 | Method and device for selecting gateway and transmitting information, and network system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109842956A (en) | 2019-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10455403B2 (en) | Virtual mobility anchor for network sharing | |
| US10609608B2 (en) | Method for changing connection mode in base station, and base station therefor, and method for changing connection mode in user equipment, and user equipment thereof | |
| CN110121897B (en) | Method and equipment for establishing session | |
| US10750418B2 (en) | SDN based connectionless architecture with dual connectivity and carrier aggregation | |
| US11811670B2 (en) | Packet delay parameter obtaining method, system, and apparatus | |
| US9185545B2 (en) | Local breakout session establishment method and apparatus in wireless communication system | |
| CN109964468B (en) | Session processing method, device and system | |
| JP2022523818A (en) | Data transmission guarantee method and communication equipment | |
| EP2608457A2 (en) | System and method for resource management for operator services and internet | |
| US9788353B2 (en) | Mobile network communications method, communications apparatus, and communications system | |
| CN106664551B (en) | Method and device for allocating IP address | |
| CN109842956B (en) | Service data routing method, service gateway and mobile management entity | |
| US10536457B2 (en) | User data processing apparatus and method, and system | |
| WO2014058135A1 (en) | Method and device for selecting packet data network gateway in wireless communication system | |
| CN106470465B (en) | WIFI voice service initiating method, LTE communication equipment, terminal and communication system | |
| WO2018170747A1 (en) | Communication method and apparatus | |
| CN111770486A (en) | Terminal roaming method and device | |
| CN115209395A (en) | Network access method and device | |
| CN112584461B (en) | Router advertisement message sending method and device | |
| US11425621B2 (en) | Device control method and apparatus | |
| WO2018206101A1 (en) | Selection criteria for (non-ip) data destinations | |
| WO2023143212A1 (en) | Communication method and apparatus | |
| JP2017126808A (en) | Radio communication system, user station, and communication control method | |
| CN116113072A (en) | Mobility management method and device, equipment, communication system and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230117 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Patentee after: CITIC Mobile Communication Technology Co.,Ltd. Address before: 100083 No. 29, Haidian District, Beijing, Xueyuan Road Patentee before: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. |
|
| TR01 | Transfer of patent right |