CN101426258A - Terminal information processing method and apparatus - Google Patents
Terminal information processing method and apparatus Download PDFInfo
- Publication number
- CN101426258A CN101426258A CNA2007101667351A CN200710166735A CN101426258A CN 101426258 A CN101426258 A CN 101426258A CN A2007101667351 A CNA2007101667351 A CN A2007101667351A CN 200710166735 A CN200710166735 A CN 200710166735A CN 101426258 A CN101426258 A CN 101426258A
- Authority
- CN
- China
- Prior art keywords
- anchor point
- terminal
- network
- shared core
- entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
An embodiment of the invention provides a method for processing terminal information, wherein the method comprises the following procedures: determining whether the anchor point corresponding with the terminal provides service for the terminal when the terminal initializes a first access network resource releasing; and cancelling the address of the anchor point when the anchor point does not provided service for the terminal. A sharing core controlling entity stores the anchor point address corresponding with the terminal when the terminal is accessed into the first access network. Through the invention provided by the embodiment of the invention, the sharing core controlling entity or management entity determines whether the anchor point corresponding with the terminal provides service for the terminal when the terminal initializes the accessing network resource releasing. The address of anchor point of network is reserved if the anchor point still provides service for the terminal. The inconsistency of user information and actual condition on the sharing core controlling entity can be avoided.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of processing method and device of end message.
Background technology
Conventional telecommunication network, wireless communication networks particularly, as GSM (Global System for Mobilecommunications, Global Systems for Mobile communications), UMTS (General Packet Radio Service, GPRS) etc., possess advantages such as class of business is abundant, the network control ability is strong, but because the wireless communication system frequency resource is limited, transmission environment is abominable etc. factor, can't provide high access rate, and emerging wireless access wide band technology these shortcomings have well been remedied.With WLAN (WirelessLocal Area Network, WLAN (wireless local area network)) and WiMAX (Worldwide InteroperabilityforMicrowave Access, World Interoperability for Microwave Access, WiMax) can provide the broadband wireless access business of two-forty for the wireless access wide band technology of representative, and support nomadic and mobile application, improved the access capability of radio communication greatly.At present, the fusion between different networks becomes trend gradually, and a kind of evolution network framework of new fusion also progressively is shaped, as shown in Figure 1.
In the evolvement network that merges, there are a shared shared core controlled entity and the management entity of two keys: Mobility Management Entity and AAA Server/Proxy (authentication and authorization charging server/agency).In the wireless communication system, user's mobility is a most important characteristic, and therefore, for cordless communication network, user's mobile management is one of most important component.Different wireless communication systems are at mobile management, design different agreements, in the communication network of this fusion, comprised the agreement of two kinds of mobile management: GTP (GPRS Tunneling Protocol at least, GPRS Tunnel Protocol) and MIP (Mobile IP, mobile IP protocol).
Wherein, different agreements have the different characteristics and the scope of application.The GTP agreement is mainly used in GPRS/UMTS (General Packet Radio Service/Universal MobileTelecommunications System, GPRS/universal mobile telecommunications system) in some evolvement network and based on GPRS/UMTS, and the MIP agreement is mainly used in WiMAX (WorldwideInteroperability for Microwave Access, World Interoperability for Microwave Access, WiMax), in the WLAN networks such as (Wireless Local Area Network, WLAN (wireless local area network)).
The GTP agreement can also provide session management when the user mobility management is provided, functions such as charging in conjunction with MAP (Mobile Application Part, mobile application protocol), can be finished each side management and control to user and network.And MIP agreement itself mainly provides the ability of mobile management, and it need be in conjunction with other control protocol, and for example Diameter (diameter) agreement can provide complete management and the control ability of a cover to network and user.
Different agreements also corresponding the different network architectures, as shown in fig. 1, the network portion that top left region is to use the GTP agreement to manage and control, and the network portion that lower zone is to use the MIP agreement to manage and control.
Access Network provides basic wireless connections ability, and various access technologies can both be included in the communication system of this fusion, GSM for example, GPRS, UMTS, WLAN, WiMAX and based on their access technology of some evolution.Can will adopt the Access Network of Network Dept.'s branch control of GTP agreement to be called access network type 1, will adopt the Access Network of Network Dept.'s branch control of MIP agreement to be called access network type 2.
As shown in fig. 1, shared core controlled entity to the user management user contracting data, the maintenance terminal relevant location information that insert by various access networks, provide and preserve authentication information.A kind of typical shared core controlled entity is HSS (Home Subscriber Sever, a home subscriber servers).
Aaa server/agency provides management and controlled function to the network portion that adopts the MIP agreement, for example: the user from the WiMAX network insertion is implemented Certificate Authority and charging etc.Aaa server/agency can adopt agreements such as Diameter to control other network entity.
Mobility Management Entity is to the user storage that inserts by access network type 1 and management identity information, mobility state information, security parameter etc., and the user is carried out Certificate Authority.
The local service gateway is the data anchor point that moves among a small circle of terminal, is the interface entities of core net and access network type 1, is responsible for the routing forwarding of user data.
Data gateway is an entity that is in the core net border, is responsible for setting up terminal to the secure tunnel between the core net.
Network anchor point is the mobile anchor point on a large scale of terminal, and is the interface entities of core net and Packet Data Network, and user data is transmitting between core net and Packet Data Network after the polymerization of data gateway place.Network anchor point may be responsible for implementing access strategy, for the end-filtration packet and for terminal distribution IP address etc.
Terminal will select a network anchor point to be connected to outside PDN (Packet Data Network, Packet Data Network) after selecting and being linked into a kind of access network, and the IP address that terminal is used will be distributed or provided by the PDN network of outside by network anchor point.When terminal inserts from access network type 1, the address that network side entity can obtain network anchor point by the mode that adopts DNS (Domain Name System, domain name system) to resolve service identification or network identity; And terminal is when access network type 2 inserts, and terminal can directly be obtained the address of network anchor point when access authentication, or service identification or the network identity obtained during by access authentication carry out the address that network anchor point is obtained in dns resolution.This shows that the mode of obtaining the network anchor point address between different access technologies may be different.Like this, when terminal is switched between different access networks, source network and objective network are that the network anchor point of terminal distribution may be just different, this just will cause the connection of User IP aspect to change, conversation, the loss of data phenomenon takes place, even can take place to cause the IP address change because anchor point changes, and then the service disconnection that causes.Therefore, when terminal was switched between different access networks, keeping network anchor point not change was a primary condition that keeps business continuance.
For keeping network anchor point not change, network anchor point information (for example IP address, service identification or network identification information etc.) is saved on the shared core controlled entity.When terminal inserted by access network type 1, Mobility Management Entity was responsible for the network anchor point information of terminal is registered on the shared core controlled entity.When terminal inserted by access network type 2, network anchor point was registered to network anchor point information on the shared core controlled entity by aaa server/agency.When terminal is switched between access network type 1 and access network type 2, shared core controlled entity can send to the network anchor point address information of preserving the management entity (Mobility Management Entity or aaa server/agency) in the objective network, like this, which kind of network no matter terminal switch to, can obtain the address of same network anchor point by shared core controlled entity, and then guarantee that user data can not lose.
The present inventor finds in realizing process of the present invention, in the prior art, when terminal is switched, at first carry out attaching process between Access Network by the purpose Access Network, the actual back terminal of switching takes place leave the source access network, the source access network is carried out relevant resource dispose procedure.After the source access network discharges resource, management entity (Mobility Management Entity or aaa server/agency) the source Access Network of judging no longer is Terminal Service, therefore can nullify the network anchor point address information of terminal to shared core controlled entity, after shared core controlled entity receives the notice of the cancellation terminal that management entity sends, the network anchor point address information of deletion terminal also may be deleted other user profile such as authentication information, authorization message and control information etc. simultaneously.But in fact terminal just changes into by purpose Access Network access network, and this moment, the network anchor point address information on the shared core controlled entity etc. was should be not deleted.
When the prior art scheme can cause terminal to switch between different Access Networks, user profile and actual conditions are not inconsistent on the shared core controlled entity, further may cause the request of shared core controlled entity refusal terminal next operation, thereby cause serious consequence such as service disconnection.
Summary of the invention
The problem to be solved in the present invention provides a kind of processing method and device of end message, the problem that user terminal information is deleted by mistake on the shared core controlled entity when avoiding terminal to switch.
For achieving the above object, the embodiment of the invention provides a kind of processing method of end message: may further comprise the steps:
When terminal is initiated the release of first access network resource,
Whether the anchor point of judging described terminal correspondence provides service for described terminal;
If described anchor point no longer provides service for described terminal, then nullify the address of described anchor point.
When terminal inserted first Access Network, shared core controlled entity was preserved the anchor point address of described terminal correspondence.
The embodiment of the invention also provides a kind of management entity, comprising:
Judging unit is used for judging the type that described terminal resource discharges, and judged result being sent to notification unit when terminal is initiated the release of first access network resource;
Notification unit, the type that is used for when described resource discharges is when moving back the resource release of net triggering, to notify shared core controlled entity to nullify the anchor point address of described terminal correspondence.
A kind of shared core controlled entity comprises:
Judging unit is used for initiating first access network resource when discharging when terminal, and whether the anchor point of judging described terminal correspondence related other management entities except that the management entity of the first Access Network correspondence, and judged result is sent to the cancellation unit;
Nullify the unit, be used for when not related other management entities of the anchor point of described terminal correspondence, nullifying the anchor point address of described terminal correspondence.
Compared with prior art, embodiments of the invention have the following advantages:
The method that provides by the embodiment of the invention, when terminal is initiated access network resource release, shared core controlled entity or management entity judge that whether the anchor point of this terminal correspondence provides service for terminal, if anchor point still provides service for terminal, then keep this network anchor point address, can avoid the situation that user profile and actual conditions are not inconsistent on the shared core controlled entity.
Description of drawings
Fig. 1 is a kind of typical UNE structural representation in the prior art;
Fig. 2 is the process flow figure of a kind of end message in the embodiment of the invention one;
Fig. 3 is the processing method schematic diagram of a kind of end message in the embodiment of the invention two;
Fig. 4 is a terminal connection status schematic diagram in the embodiment of the invention two;
Fig. 5 is the processing method schematic diagram of a kind of end message in the embodiment of the invention three;
Fig. 6 is the processing method schematic diagram of a kind of end message in the embodiment of the invention four;
Fig. 7 is the processing method schematic diagram of a kind of end message in the embodiment of the invention five;
Fig. 8 is the processing method schematic diagram of a kind of end message in the embodiment of the invention six;
Fig. 9 is the processing method schematic diagram of a kind of end message in the embodiment of the invention seven;
Figure 10 is the processing method schematic diagram of a kind of end message in the embodiment of the invention eight;
Figure 11 is a kind of shared core controlled entity schematic diagram in the embodiment of the invention nine;
Figure 12 is a kind of management entity schematic diagram in the embodiment of the invention ten.
Embodiment
Below in conjunction with drawings and Examples, the specific embodiment of the present invention is described in further detail.
In the embodiments of the invention one, a kind of processing method of end message as shown in Figure 2, concrete steps are as follows:
Step S201, when terminal inserts first Access Network, shared core controlled entity is preserved the anchor point address of terminal correspondence.
Step S202, initiate first access network resource when discharging when terminal, whether the anchor point of judging the terminal correspondence for terminal provides service, if shared core controlled entity keeps the address of anchor point, otherwise commentaries on classics step S203.
If step S203 anchor point is then nullified the address of anchor point no longer for terminal provides service.
In the above-mentioned steps, whether the anchor point of judging the terminal correspondence can be shared core controlled entity for terminal provides the judgement entity of service, also can be the management entity of the first Access Network correspondence, following examples judge that with two kinds entity is that the present invention will be described for example respectively.
In the embodiments of the invention two, with shared core controlled entity as the anchor point of judging the terminal correspondence whether be terminal the judgement entity of service is provided is example, a kind of processing method of end message as shown in Figure 3, concrete steps are as follows:
Step S301, when terminal inserts first Access Network, the access procedure of the pairing management entity processing terminal of first Access Network sends the endpoint registration request to shared core controlled entity, is terminal registration network anchor point address information.
Concrete, management entity can be Mobility Management Entity or aaa server/agency, the endpoint registration request message can be put request message or update packet data network gateway address message for updated space.
After step S302, shared core controlled entity receive the endpoint registration request, preserve the network anchor point address information of terminal and upgrade the network connection state of this terminal.
Concrete, the entity (can be Mobility Management Entity or aaa server/agency) that carries out the registration of network anchor point address information is called for short registering entities.The method of shared core controlled entity registration terminal can be in the following method one or more, is specially:
(1) the shared core controlled entity network anchor point address information of preserving terminal related with between registering entities identifies.If terminal is registered by two registering entities, then shared core controlled entity is associated together the sign of these two registering entities simultaneously with the network anchor point address information of terminal.Further, shared core controlled entity can be preserved related between each APN (Access Point Name, APN) that terminal will activate and the registering entities sign.
A kind of typical network anchor point address information storage condition is as shown in table 1.Wherein, terminal has two network anchor point: network anchor point 1 and network anchor point 2, network anchor point 1 are the data anchor points of APN1 and two business of APN2, and network anchor point 2 is data anchor points of APN3 business.The address of network anchor point 1 and network anchor point 2 all is by the Mobility Management Entity registration, with related being kept at together of Mobility Management Entity sign.
Network anchor point address information after table 1 registration
(2) shared core controlled entity is preserved corresponding network anchor point address information for each registering entities.If terminal is registered (being that terminal is in two networks simultaneously) by two registering entities to shared core controlled entity, then shared core controlled entity is that each registering entities (being each network) is preserved particular network anchor point address information, even two registering entities registrations is the address information of same network anchor point.
(3) shared core controlled entity is provided with a network type identifier or terminal connect state machine for each network anchor point, and the value of identifier/state machine can be represented the connection status of " not in network ", " network type 1 ", " network type 2 " and " network type 1 and network type 2 " four kinds of terminals.When terminal was only registered the network anchor point address information by Mobility Management Entity, identifier/state machine was set to " network type 1 "; When terminal was only crossed the network anchor point address information by aaa server/agency of trademark registration, identifier/state machine was set to " network type 2 "; When terminal was crossed the network anchor point address information by Mobility Management Entity and aaa server/agency of trademark registration, identifier/state machine was set to " network type 1 and network type 2 ".Further, shared core controlled entity can also be provided with a network type identifier or service connected state machine for each APN.
(4) shared core controlled entity is provided with two network type identifiers for each network anchor point, and whether an expression terminal is in the network type 1, and whether another expression terminal is in the network type 2.When Mobility Management Entity is terminal registration network anchor point address information, shared core controlled entity will represent whether terminal is in the identifier set of network type 1; Aaa server/when acting on behalf of to terminal registration network anchor point address information, shared core controlled entity will represent whether terminal is in the identifier set of network type 2.
In this step, after shared core controlled entity receives this endpoint registration request, can also check the network anchor point address information of whether preserving this terminal, if preserve, then user contracting data and this network anchor point address information are sent to management entity, and the network connection state of new terminal more.
After the terminal access procedure is finished, may at a time need to switch in another network, after terminal is left management entity place network, carry out the resource dispose procedure; Terminal also may at a time disconnect all-network and connect, and promptly moves back net, and exiting network process also comprises the process of network releasing resource.
Step S303, initiate first access network resource when discharging when terminal, the management entity of the first Access Network correspondence sends the terminal log-down request to shared core controlled entity.
After step S304, shared core controlled entity receive the terminal log-down request, judge whether related other management entities except that the management entity of the first Access Network correspondence of anchor point address information of terminal correspondence, if in having, change step S305, otherwise shared core controlled entity is nullified the network anchor point address information of terminal.
If relevant other management entities except that the management entity of the first Access Network correspondence of the anchor point address information of step S305 terminal correspondence, shared core controlled entity are the connection status of new terminal more only, keep the network anchor point address information of terminal.
Concrete, carry out the entity (can be Mobility Management Entity or aaa server/agency) that the network anchor point address information is nullified, be called for short and nullify entity.Corresponding to aforementioned register method, the method that shared core controlled entity is nullified terminal can be in the following method one or more, is specially:
(1) nullifies entity when shared core controlled entity is nullified the network anchor point address information of terminal, shared core controlled entity is at first judged this network anchor point address information, and whether related other management entities identify, if have, then only entity identification is nullified in deletion, keeps the address information of the network anchor point of this terminal; Otherwise the network anchor point address information of deletion terminal and cancellation entity identification.Further, whether related shared core controlled entity can also judge each APN of terminal other management entities signs respectively, if having, then deletes the cancellation entity identification of this APN association, keep this APN information, and deletion there is not the APN information of related other management entity signs.
A kind of typical network anchor point address information storage condition is as shown in table 2.Wherein, terminal has two network anchor point: network anchor point 1 and network anchor point 2, network anchor point 1 are the data anchor points of APN1, and network anchor point 2 is data anchor points of APN2.The address of network anchor point 1 and APN1 are by the Mobility Management Entity registration, with related being kept at together of Mobility Management Entity sign; The address of network anchor point 2 and APN2 be by Mobility Management Entity and aaa server/agency of trademark registration, with the Mobility Management Entity sign with aaa server/agent identification is related is kept at together.
Network anchor point address information before table 2 is nullified
If this moment, shared core controlled entity received the request for this terminal log-down network anchor point 1 and network anchor point 2 addresses that Mobility Management Entity sends, then only delete address, APN1 and the Mobility Management Entity sign of network anchor point 1, the address, APN2 and the aaa server/agency that keep network anchor point 2.The network anchor point address information storage condition of nullifying on the shared core controlled entity in back is shown in the table 3:
Network anchor point address information after table 3 is nullified
| Title | Memory contents |
| User ID | User's IMSI or NAI |
| The network anchor point address | The IP address of network anchor point 2 |
| Service identification | APN3 |
| Related registering entities | Aaa server/agent identification |
(2) to receive and nullify entity be after the request of terminal log-down network anchor point address information to shared core controlled entity, deletes the network anchor point address information of this cancellation entity correspondence.
(3) after shared core controlled entity received the request of nullifying terminal network anchor point address information, shared core controlled entity was according to state transitions mode modified logo symbol/state machine shown in Figure 4.Only when turning back to " not network " state from other states, shared core controlled entity is deleted the network anchor point address information of terminal.Further, shared core controlled entity can be provided with network type identifier or service connected state machine for each APN, and only when turning back to " not network " state from other states, shared core controlled entity is deleted this APN information.
When (4) the cancellation entity is terminal log-down network anchor point address information, shared core controlled entity will represent to nullify the identifier zero clearing of physical network type; When two network type identifiers are zero, the network anchor point address information of shared core controlled entity deletion terminal; During any one identifier set, shared core controlled entity can not be deleted the network anchor point address information of terminal.
In the above step, when management entity is nullified the network anchor point address information of terminal to shared core controlled entity, need to judge whether the network anchor point address information of deletion terminal by shared core controlled entity, be understandable that, when management entity is nullified the network anchor point address information of terminal to shared core controlled entity, can also need judge whether the network anchor point address information of deletion terminal by management entity, be specially: can nullify the type that the entity terminal resource discharges by other entity notices of knowing the resource release cause, for example: terminal points out it is to nullify owing to moving back net in sending to the logout message of Mobility Management Entity, still nullifies owing to switching; Network anchor point points out it is to nullify owing to moving back net in the logout message of issuing aaa server/agency, still nullify owing to switching.If move back the resource release that net triggers, then notify shared core controlled entity to nullify the network anchor point address information of terminal; If the resource of handover trigger discharges, then do not notify shared core controlled entity to nullify the network anchor point address information of terminal.
Following examples are example with shared core controlled entity and management entity as the judgement entity respectively, and the present invention is described in detail respectively.Be understandable that the processing method to end message of the present invention can be divided into two processes: registration process and log off procedure.Following examples will be described respectively registration process and log off procedure, and the present invention's process is described.
In the embodiments of the invention three, as judging entity, Mobility Management Entity is described to shared core controlled entity registered network anchor point address information with shared core controlled entity, a kind of processing method of end message as shown in Figure 5, concrete steps are as follows:
Step S501, terminal are attached to core net by access network type 1 request, Mobility Management Entity control and treatment terminal adhere to request.
Concrete, may comprise Certificate Authority, old deleting load-bearing, new processes such as carrying foundation in the attaching process.Shared core controlled entity may be preserved the sign of Mobility Management Entity in this step process.
Step S502, Mobility Management Entity send to shared core controlled entity and upgrade position requests (Update location message), are terminal registration network anchor point address information.
Concrete, may comprise the information such as APN of sign, user ID, network anchor point address and the needs access of Mobility Management Entity in this renewals position requests.
After step S503, shared core controlled entity receive the renewal position requests of Mobility Management Entity transmission, preserve the network anchor point address information of carrying in the request message, the network anchor point address and the corresponding APN that may comprise user ID, terminal, and the network connection state of new terminal more, promptly this terminal of mark is connected to network type 1.Further, shared core controlled entity each APN token network connection status that can will activate for this terminal.
The method of shared core controlled entity registration terminal is specially:
(1) the shared core controlled entity network anchor point address information of preserving terminal related with between Mobility Management Entity identifies.Further, shared core controlled entity can also be preserved related between each APN that this terminal will activate and the Mobility Management Entity sign.
The network anchor point address information storage condition of terminal is shown in table 1 among the embodiment one in the present embodiment.Wherein, terminal has two network anchor point: network anchor point 1 and network anchor point 2, and wherein network anchor point 1 is the data anchor point of APN1 and two business of APN2, network anchor point 2 is data anchor points of APN3 business.The address of network anchor point 1 and network anchor point 2 is all by the Mobility Management Entity registration, all with related being kept at together of Mobility Management Entity sign.
(2) shared core controlled entity is preserved the network anchor point address information of corresponding terminal for this Mobility Management Entity.
(3) shared core controlled entity is preserved the network anchor point address information of terminal, and identifier/state machine symbol is changed to " network type 1 ".Further, shared core controlled entity can also be provided with a network type identifier or service connected state machine for each APN that terminal will activate, and identifier/state machine symbol is changed to " network type 1 ".
(4) shared core controlled entity saves as the network anchor point address information of terminal, and will represent whether terminal is in the identifier set of network type 1.Further, shared core controlled entity can also be provided with two network type identifiers for each APN that terminal will activate, and will represent the professional identifier set that whether is in network type 1.
After shared core controlled entity receives the endpoint registration request of Mobility Management Entity transmission, can also check the network anchor point address information of whether preserving this terminal, if preserve, then user contracting data and this network anchor point address information are sent to Mobility Management Entity, more the network connection state of new terminal.
Step S504, shared core controlled entity send to Mobility Management Entity and upgrade the position response, confirm that the network anchor point address information of terminal succeeds in registration.
In the embodiments of the invention four, as judging entity, aaa server/agency is described to shared core controlled entity registered network anchor point address information with shared core controlled entity, a kind of processing method of end message as shown in Figure 6, concrete steps are as follows:
The access request that step S601, network anchor point entity receiving terminal send, the access procedure of execution terminal.
Concrete, may comprise processes such as authentication, mandate and tunnel foundation in the attaching process.
Step S602, network anchor point entity are to the network anchor point address information of aaa server/agency of trademark registration terminal, and this network anchor point address information may comprise the information such as APN that network anchor point address, needs insert.
Step S603, aaa server/agency preserve the network anchor point address information of terminal, and send the renewal position requests to shared core controlled entity, are terminal registration network anchor point address information.
Concrete, may comprise the information such as APN of user ID, aaa server/agency's sign, network anchor point address and needs access in this renewals position requests.
After step S604, shared core controlled entity receive the renewal position requests of aaa server/agency's transmission, preserve and upgrade the network anchor point address information of carrying in the position requests, this network anchor point address information may comprise the network anchor point address of user ID, terminal and corresponding APN, and the network connection state of new terminal more.Further, the network connection state of each APN tagged traffic that can will activate for this terminal.
The method of shared core controlled entity registration terminal can be specially in the following method one or more:
(1) shared core controlled entity saves as related between address information and the aaa server/agent identification of network anchor point 2 of terminal.Further, shared core controlled entity can also be preserved related between each APN that this terminal will activate and the aaa server/agent identification.In the present embodiment, the network anchor point address information of the terminal of preserving on the shared core controlled entity is as shown in table 4.
Table 4 network anchor point address information
Wherein, terminal has two network anchor point: network anchor point 1 and network anchor point 2, network anchor point 1 is the data anchor point of APN1 and two business of APN2, network anchor point 2 is data anchor points of APN3 business, register by Mobility Management Entity the address of network anchor point 1, with related being kept at together of Mobility Management Entity sign, the address of network anchor point 2 is by Mobility Management Entity and aaa server/agency of trademark registration, simultaneously with two related being kept at together of management entity sign.
(2) shared core controlled entity is the network anchor point address information that aaa server/agency preserves corresponding terminal.Be shared core controlled entity except preserving (network anchor point 1, APN1, APN2) and (network anchor point 2, APN3), preserved for aaa server/agency again (network anchor point 2, APN3) for Mobility Management Entity.
(3) shared core controlled entity is preserved the network anchor point address information of terminal, and the identifier/state machine of network anchor point 2 is transformed into " network type 1 and network type 2 " by " network type 1 ", the identifier/state machine of network anchor point 1 still keeps " network type 1 ".Further, shared core controlled entity can also be provided with a network type identifier or service connected state machine for each APN that terminal will activate, and identifier/state machine of APN3 is converted to " network type 1 and network type 2 " from " network type 1 ", identifier/state machine of APN1 and APN2 still keeps " network type 1 ".
(4) shared core controlled entity saves as the address information of the network anchor point 2 of Terminal Service, and whether the expression terminal of network anchor point 2 be in the identifier set of network type 2, whether the expression terminal that does not influence network anchor point 2 after the set is in the identifier of network type 1.Further, shared core controlled entity can also be provided with two network type identifiers for each APN that terminal will activate, and whether the expression business of APN3 is in the identifier set of network type 2.
After shared core controlled entity receives this endpoint registration request, can also check the network anchor point address information of whether preserving this terminal, if preserve, then user contracting data and this network anchor point address information are sent to aaa server/agency, more the network connection state of new terminal.
Step S605, shared core controlled entity are to aaa server/acting on behalf of the body transmission upgrades the position response, confirms that the network anchor point address information of terminal succeeds in registration.
Among embodiment two and the embodiment three, as judging entity, the process of management entity to the network anchor point address information of shared core controlled entity registration terminal is described in detail with shared core controlled entity.When terminal was switched between Access Network, management entity also needed to nullify to shared core controlled entity the network anchor point address information of terminal, below implemented this log off procedure is described in detail.
In the embodiments of the invention five, as judging entity, Mobility Management Entity is nullified the network anchor point address information to shared core controlled entity is described with shared core controlled entity, a kind of processing method of end message as shown in Figure 7, concrete steps are as follows:
Step S701, terminal are left access network type 1, and access network type 1 is carried out exiting network process or resource dispose procedure.
Step S702, Mobility Management Entity send de-registration request to shared core controlled entity, and the network anchor point address information of terminal is nullified in request.
After step S703, shared core controlled entity receive de-registration request, network anchor point address information according to the terminal of preserving judges whether terminal also is in the network type 2, if terminal also is in the network type 2, change step S704, otherwise shared core controlled entity is nullified the network anchor point address information of terminal.
Concrete, corresponding to register method described in embodiment two and the embodiment three, the method that shared core controlled entity is nullified terminal can be in the following method one or more, is specially:
(1) shared core controlled entity is judged whether related aaa server/agent identification of network anchor point address information, if having, then only deletes the Mobility Management Entity sign, keeps the address information of the network anchor point of this terminal; Otherwise the network anchor point address information of deletion terminal and Mobility Management Entity sign.
Further, shared core controlled entity can also be judged whether relevant aaa server/agent identification of each APN that this terminal will nullify, if have, then delete the Mobility Management Entity sign of this APN association, the information that reservation is relevant with this APN, and deletion there is not the APN information of related aaa server/agent identification.
In the present embodiment, before terminal was left access network type 1, the network anchor point address information that shared core controlled entity is preserved was as shown in table 4.Nullify the address information and the relevant information of the shared core controlled entity deletion in back Mobility Management Entity sign and network anchor point 1, network anchor point address information storage condition becomes situation shown in the table 5 from table 4.
Table 5 network anchor point address information
| Title | Memory contents |
| User ID | User's IMSI or NAI |
| The network anchor point address | The IP address of network anchor point 2 |
| Service identification | APN3 |
| Related registering entities | Aaa server/agent identification |
(2) shared core controlled entity receives after the request that Mobility Management Entity is a terminal log-down network anchor point address information, network anchor point address information and relevant information that deletion is preserved for Mobility Management Entity do not influence the network anchor point address information of preserving for aaa server/agency after the deletion.
(3) after shared core controlled entity receives the request of Mobility Management Entity cancellation terminal network anchor point address information, nullify terminal network anchor point address information and identifier/state machine state metastatic rule according to Mobility Management Entity, identifier/state machine the symbol of network anchor point 1 is transformed into " not network " from " network type 1 ", and the address information and the relevant information of deletion network anchor point 1; Identifier/the state machine of network anchor point 2 is transformed into " network type 2 " from " network type 1 and network type 2 ".
Further, shared core controlled entity can also be provided with network type identifier or service connected state machine for each APN that terminal will activate, nullify terminal network anchor point address information and identifier/state machine state metastatic rule according to Mobility Management Entity, identifier/state machine of APN1 and APN2 is transformed into " not network " from " network type 1 ", and deletion APN1 and APN2, the address and the relevant information of deletion network anchor point 1; Identifier/state machine of APN3 is transformed into " network type 2 " by " network type 1 and network type 2 ".
(4) after shared core controlled entity receives the message of Mobility Management Entity cancellation terminal network anchor point address information, whether shared core controlled entity is in the identifier zero clearing of network type 1 with the expression of network anchor point 1, and deletes the address information and the relevant information of network anchor point 1; Whether the expression of network anchor point 2 is in the identifier zero clearing of network type 1, and keeps the expression of network anchor point 2 whether to be in the sign set of network type 2.
Further, shared core controlled entity can also be provided with two network type identifiers for each APN that terminal will activate, when Mobility Management Entity is terminal log-down network anchor point address information, shared core controlled entity is with the identifier zero clearing of all relevant expression network types 1, deletion APN1, APN2, the address information and the relevant information of deletion network anchor point 1.
Step S704, shared core controlled entity be the connection status of new terminal more only, does not nullify the network anchor point address information of terminal.
In the embodiments of the invention six, as judging entity, aaa server/agency is described to shared core controlled entity cancellation network anchor point address information with shared core controlled entity, a kind of processing method of end message as shown in Figure 8, concrete steps are as follows:
Step S801, terminal are left access network type 2, and access network type 2 is carried out the resource dispose procedure.
After step S802, aaa server/agency learn that terminal is left access network type 2, nullify local terminal network anchor point address information, also may be simultaneously with other user profile deletions, for example authentication information, authorization message and control information etc.
Concrete, aaa server/agency learns that terminal leaves the method for access network type 2 and can be: aaa server/agency receives the notice of other entities, perhaps aaa server/agency to detect oneself no longer be this Terminal Service.
Step S803, aaa server/agency send de-registration request to shared core controlled entity, and the network anchor point address information of terminal is nullified in request.
After step S804, shared core controlled entity receive de-registration request, network anchor point address information according to the terminal of preserving judges whether terminal also is in the network type 1, if terminal also is in the network type 1, change step S805, otherwise shared core controlled entity is nullified the network anchor point address information of terminal.
Concrete, corresponding to register method described in embodiment two and the embodiment three, the method that shared core controlled entity is nullified terminal is specially:
(1) shared core controlled entity is judged whether related Mobility Management Entity sign of network anchor point address information, if having, then only deletes aaa server/agent identification, keeps the address information of the network anchor point of this terminal; Otherwise the network anchor point address information and the aaa server/agent identification of deletion terminal.
Further, whether each APN that shared core controlled entity can also be judged terminal relevant Mobility Management Entity sign, if have, then delete this APN association aaa server/agent identification, keep this APN information, and deletion does not have the APN information of related Mobility Management Entity sign.
In the present embodiment, before terminal was switched, the network anchor point address information of the terminal that shared core controlled entity is preserved was as shown in table 5.Nullify the address information and the relevant information (APN3) of shared core controlled entity deletion aaa server/agent identification in back and network anchor point 2, promptly nullified the all-network anchor point address information and the relevant information of this terminal, wherein authentication information, authentication information etc. also can be deleted together.
(2) shared core controlled entity receives aaa server/act on behalf of after the request into terminal log-down network anchor point address information, network anchor point address information and relevant information that deletion is preserved for aaa server/agency, the i.e. network anchor point address information of this terminal not on shared core controlled entity this moment, wherein authentication information, authentication information etc. also can be deleted together.
(3) after shared core controlled entity receives the request of aaa server/agency's cancellation terminal network anchor point address information, nullify terminal network anchor point address information and identifier/state machine state metastatic rule according to aaa server/agency, identifier/the state machine of network anchor point 2 is transformed into " not network " from " network type 2 ", and the address information and the relevant information of deletion network anchor point 2.
Further, shared core controlled entity can also be provided with network type identifier or service connected state machine for each APN that terminal will activate, nullify terminal network anchor point address information and identifier/state machine state metastatic rule according to aaa server/agency, identifier/state machine of APN3 is transformed into " not network " from " network type 2 ", and deletes the address information and the relevant information of APN3, network anchor point 2.
(4) after shared core controlled entity receives the message of aaa server/agency's cancellation terminal network anchor point address information, whether the expression of network anchor point 2 is in the identifier zero clearing of network type 2, and deletes the address information and the relevant information of network anchor point 2.
Further, shared core controlled entity can also be provided with two network type identifiers for each APN that terminal will activate, aaa server/when acting on behalf of to terminal log-down network anchor point address information, shared core controlled entity is deleted the address information and the relevant information of APN3, network anchor point 2 with the identifier zero clearing of all relevant expression network types 2.
Step S805, shared core controlled entity be the connection status of new terminal more only, does not nullify the network anchor point address information of terminal.
When aaa server/agency nullifies the network anchor point address information of terminal to shared core controlled entity, can also adopt following method: aaa server/agency judges the type that resource discharges, if move back the resource release that net triggers, the shared core controlled entity of aaa server/agent advertisement is nullified the network anchor point address information; If the cancellation of handover trigger, aaa server/agency only nullifies the network anchor point address information in this locality, can not notify shared core controlled entity to nullify the network anchor point address information.
Concrete, aaa server/agency judges that the method for the type that resource discharges can be: know the entity notice type that aaa server/the proxy terminal resource discharges of resource release cause by other, for example: network anchor point points out it is to nullify owing to moving back net in the logout message of issuing aaa server/agency, still nullifies owing to switching.
Above embodiment all with shared core controlled entity as judge entity be example present invention is described, following examples, are described log off procedure of the present invention as judging entity with management entity.
In the embodiment of the invention seven, as judging entity, Mobility Management Entity is nullified the network anchor point address information to shared core controlled entity is described with Mobility Management Entity, a kind of processing method of end message as shown in Figure 9, concrete steps are as follows:
Step 901, terminal are left access network type 1, carry out exiting network process or resource dispose procedure by access network type 1.
Concrete, thereby terminal may be left access network type 1 owing to reasons such as shutdown, insufficient credit exit network, thus also may be to switch between terminal generation access technology to have left access network type 1.
What step 902, Mobility Management Entity were judged terminal moves back the net type, if the exiting network process that reasons such as terminal closedown, insufficient credit take place then changes step S903, if the source network after switching between access technology discharges resource, step S904.
Concrete, Mobility Management Entity judges that the method for moving back the net type of terminal can be: know the type that the entity notice Mobility Management Entity terminal resource of resource release cause discharges by other, for example: (1) terminal points out it is to nullify owing to moving back net in sending to the logout message of Mobility Management Entity, still nullifies owing to switching; Perhaps (2) network anchor point discharges in the Indication message to point out it is to nullify owing to moving back net in the resource of issuing Mobility Management Entity, still nullifies owing to switching.
Step S903, Mobility Management Entity are notified the network anchor point address information of shared core controlled entity deletion terminal, also may delete other user profile such as authentication information, authorization message and control information etc. simultaneously.
Step S904, Mobility Management Entity do not trigger the network anchor point address information of shared core controlled entity deletion terminal, and shared core controlled entity still keeps the network anchor point address information of terminal after terminal is switched.
In the embodiment of the invention eight,, aaa server/agency is nullified the network anchor point address information to shared core controlled entity be described as judging entity with aaa server/agency, a kind of processing method of end message as shown in figure 10, may further comprise the steps:
Step S1001, terminal are left access network type 2, carry out exiting network process by access network type 2.
Concrete, thereby terminal may be left access network type 2 owing to reasons such as shutdown, insufficient credit exit network; Thereby also may be to switch between terminal generation access technology to have left access network type 2.
After step S1002, aaa server/agency learn that terminal is left access network type 2, nullify local terminal network anchor point address information, also may delete other user profile such as authentication information, authorization message and control information etc. simultaneously.
Step S1003, aaa server/agency's judgement terminal are left the reason of access network type 2, if the exiting network process that reasons such as terminal closedown, insufficient credit take place, then change step S904,, change step S905 if the source network after switching between access technology discharges resource.
Concrete, aaa server/agency judges that the method for moving back the net type of terminal can be: know the entity notice type that aaa server/the proxy terminal resource discharges of resource release cause by other, for example: network anchor point points out it is to nullify owing to moving back net in issuing aaa server/agency's update packet data network gateway address message, still nullifies owing to switching.
Step S1004, the shared core controlled entity of aaa server/agent advertisement are nullified the network anchor point address information of terminal, also may delete other user profile such as authentication information, authorization message and control information etc. simultaneously.
Step S1005, aaa server/agency do not trigger the network anchor point address information of shared core controlled entity deletion terminal, and shared core controlled entity still keeps the network anchor point address information of terminal after terminal is switched.
The method that provides by above embodiment, when terminal is initiated access network resource release, shared core controlled entity or management entity judge that whether the anchor point of this terminal correspondence provides service for terminal, if anchor point still provides service for terminal, then keep this network anchor point address, can avoid the situation that user profile and actual conditions are not inconsistent on the shared core controlled entity.
Provide a kind of shared core controlled entity in the embodiments of the invention nine as shown in figure 11, comprising:
Judging unit 11 is used for initiating first access network resource when discharging when terminal, and whether the anchor point of judging the terminal correspondence related other management entities except that the management entity of the first Access Network correspondence, and judged result is sent to cancellation unit 12.
Nullify unit 12, be used for when not related other management entities of the anchor point of terminal correspondence the anchor point address of cancellation terminal correspondence.
Shared core controlled entity further comprises: registering unit 13 is used for preserving the anchor point address of terminal correspondence when terminal inserts described first Access Network.
Provide a kind of management entity as shown in figure 12 in the embodiments of the invention ten, comprising:
Judging unit 21 is used for judging the type that terminal resource discharges, and judged result being sent to notification unit 22 when terminal is initiated the release of first access network resource.
Notification unit 22, the type that is used for when resource discharges is when moving back the resource release of net triggering, to notify shared core controlled entity to nullify the anchor point address of terminal correspondence.
The device that provides by above embodiment, when terminal is initiated access network resource release, shared core controlled entity or management entity judge that whether the anchor point of this terminal correspondence provides service for terminal, if anchor point still provides service for terminal, then keep this network anchor point address, can avoid the situation that user profile and actual conditions are not inconsistent on the shared core controlled entity.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this obtains the machine software product and is stored in the storage medium, comprises that some instructions are used so that the network equipment is carried out the described method of each embodiment of the present invention.
More than disclosed only be several specific embodiment of the present invention, still, the present invention is not limited thereto, any those skilled in the art can think variation all should fall into protection scope of the present invention.
Claims (18)
1, a kind of processing method of end message is characterized in that, may further comprise the steps:
When terminal is initiated the release of first access network resource,
Whether the anchor point of judging described terminal correspondence provides service for described terminal;
If described anchor point no longer provides service for described terminal, then nullify the address of described anchor point.
2, the processing method of end message according to claim 1 is characterized in that, described terminal is initiated further to comprise before first access network resource discharges:
Described shared core controlled entity is preserved the anchor point address of described terminal correspondence.
3, the processing method of end message according to claim 1 is characterized in that, describedly judges whether the anchor point of described terminal correspondence is specially for described terminal provides service:
Management entity is judged the type that described resource discharges,
If, judge that then described anchor point no longer provides service for described terminal for moving back the described resource release that net triggers.
4, as the processing method of end message as described in the claim 3, it is characterized in that the address of the described anchor point of described cancellation is specially:
Described management entity notifies shared core net controlled entity to nullify described anchor point address.
5, the processing method of end message according to claim 1 is characterized in that, describedly judges whether the anchor point of described terminal correspondence is specially for described terminal provides service:
Whether related shared core net controlled entity judge described anchor point other management entities except that the management entity of the first Access Network correspondence;
If not related other management entities of described anchor point judge that then described anchor point no longer provides service for described terminal.
6, as the processing method of end message as described in the claim 5, it is characterized in that the address of the described anchor point of described cancellation is specially:
The address that described shared core net controlled entity is nullified described anchor point.
7, the processing method of end message according to claim 1 is characterized in that, if described anchor point provides service for described terminal, then described shared core net controlled entity is deleted the management entity sign of first Access Network of described terminal correspondence;
If perhaps described anchor point provides service for described terminal, and described shared core net controlled entity is deleted the management entity sign and the service identification that identifies of the management entity of related first Access Network only of first Access Network of described terminal correspondence.
8, the processing method of end message according to claim 1, it is characterized in that, comprise that further if described anchor point provides service for described terminal, described shared core controlled entity is according to identifier/state machine state metastatic rule modified logo symbol/transfering state.
9, the processing method of end message according to claim 1 is characterized in that further comprise, if described anchor point provides service for described terminal, described shared core controlled entity is with the network identifier zero clearing at the management entity place of first Access Network.
10, as the processing method of end message as described in any one claim of claim 1-9, it is characterized in that, described management entity is Mobility Management Entity or authentication and authorization charging server/act on behalf of AAAServer/Proxy, and described shared core controlled entity is home subscriber servers HSS.
11, a kind of processing method of end message is characterized in that, may further comprise the steps:
When terminal inserted first Access Network, shared core controlled entity was preserved the anchor point address of described terminal correspondence.
12, as the processing method of end message as described in the claim 11, it is characterized in that the anchor point address that described shared core controlled entity is preserved described terminal correspondence is specially:
The incidence relation of the management entity sign that preserve shared core net controlled entity described anchor point address and described terminal are inserted;
Or shared core net controlled entity is preserved the incidence relation of the service identification that described anchor point address, management entity that described terminal inserted sign and described terminal activate.
13, as the processing method of end message as described in the claim 11, it is characterized in that further comprise, described shared core net controlled entity is that described anchor point is provided with a network type identifier or terminal connection status.
14, as the processing method of end message as described in the claim 11, it is characterized in that further comprise, described shared core controlled entity is provided with two network type identifiers for each network anchor point.
15, as the processing method of end message as described in any one claim of claim 11-14, it is characterized in that, described management entity is Mobility Management Entity or authentication and authorization charging server/act on behalf of AAAServer/Proxy, and described shared core controlled entity is home subscriber servers HSS.
16, a kind of management entity is characterized in that, comprising:
Judging unit is used for judging the type that described terminal resource discharges, and judged result being sent to notification unit when terminal is initiated the release of first access network resource;
Notification unit, the type that is used for when described resource discharges is when moving back the resource release of net triggering, to notify shared core controlled entity to nullify the anchor point address of described terminal correspondence.
17, a kind of shared core controlled entity is characterized in that, comprising:
Judging unit is used for initiating first access network resource when discharging when terminal, and whether the anchor point of judging described terminal correspondence related other management entities except that the management entity of the first Access Network correspondence, and judged result is sent to the cancellation unit;
Nullify the unit, be used for when not related other management entities of the anchor point of described terminal correspondence, nullifying the anchor point address of described terminal correspondence.
18, as shared core controlled entity as described in the claim 17, it is characterized in that, further comprise:
Registering unit is used for preserving the anchor point address of described terminal correspondence when described terminal inserts described first Access Network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101667351A CN101426258B (en) | 2007-11-01 | 2007-11-01 | Terminal information processing method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101667351A CN101426258B (en) | 2007-11-01 | 2007-11-01 | Terminal information processing method and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101426258A true CN101426258A (en) | 2009-05-06 |
| CN101426258B CN101426258B (en) | 2011-02-09 |
Family
ID=40616540
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101667351A Active CN101426258B (en) | 2007-11-01 | 2007-11-01 | Terminal information processing method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101426258B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017098442A1 (en) * | 2015-12-08 | 2017-06-15 | Huawei Technologies Co., Ltd. | System and method of user equipment state configurations for multiple services |
| CN107534648A (en) * | 2015-02-25 | 2018-01-02 | 诺基亚通信公司 | For supporting the mechanism of operator's auxiliary parent's control |
| CN109548190A (en) * | 2017-07-28 | 2019-03-29 | 中兴通讯股份有限公司 | A kind of method and device managing UPF anchor point |
| US10356608B2 (en) | 2016-02-18 | 2019-07-16 | Huawei Technologies Co., Ltd. | System and method of user equipment state configurations |
| US10536946B2 (en) | 2015-12-08 | 2020-01-14 | Huawei Technologies Co., Ltd. | Method and system for performing network slicing in a radio access network |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ATE425643T1 (en) * | 2004-12-17 | 2009-03-15 | Huawei Tech Co Ltd | METHOD AND SYSTEM FOR MAINTAINING SESSION CONTINUITY |
| CN101001442B (en) * | 2006-01-10 | 2011-02-02 | 华为技术有限公司 | Overcell switching method and system in mobile network |
| CN101009858A (en) * | 2006-01-25 | 2007-08-01 | 华为技术有限公司 | Two-layer node evolution network structure |
-
2007
- 2007-11-01 CN CN2007101667351A patent/CN101426258B/en active Active
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107534648A (en) * | 2015-02-25 | 2018-01-02 | 诺基亚通信公司 | For supporting the mechanism of operator's auxiliary parent's control |
| WO2017098442A1 (en) * | 2015-12-08 | 2017-06-15 | Huawei Technologies Co., Ltd. | System and method of user equipment state configurations for multiple services |
| US10536946B2 (en) | 2015-12-08 | 2020-01-14 | Huawei Technologies Co., Ltd. | Method and system for performing network slicing in a radio access network |
| US10356608B2 (en) | 2016-02-18 | 2019-07-16 | Huawei Technologies Co., Ltd. | System and method of user equipment state configurations |
| US10924918B2 (en) | 2016-02-18 | 2021-02-16 | Huawei Technologies Co., Ltd. | System and method of user equipment state configurations |
| CN109548190A (en) * | 2017-07-28 | 2019-03-29 | 中兴通讯股份有限公司 | A kind of method and device managing UPF anchor point |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101426258B (en) | 2011-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101330753B (en) | Method for establishing and erasuring resource as well as network appliance | |
| RU2456774C2 (en) | Method to update information on location of user equipment | |
| CN101801102B (en) | PDN connection establishment method, relevant device and system | |
| CN101150838B (en) | A method and system for inter-system switching | |
| CN101521871B (en) | Method, device and system for updating tracking area | |
| CN102244908A (en) | Handover method supporting terminal mobility | |
| CN101568149B (en) | Method and system for preferably selecting service gateway | |
| KR20120123337A (en) | Voice transmission technology selection | |
| CN103517252A (en) | Packet gateway identification information updating method, AAA server and packet gateway | |
| CN101677470A (en) | Processing method, device and system of service request | |
| CN103249096B (en) | A kind of switching handling method, equipment and system | |
| CN101426258B (en) | Terminal information processing method and apparatus | |
| CN101325583B (en) | Method for registering gateway address and mobility management entity | |
| CN101321392A (en) | Load deleting method and system, gateway equipment | |
| CN102238727A (en) | Method, device and system for selecting packet data network gateway (PDN GW) node | |
| CN102006673B (en) | Method, device and system for releasing connection | |
| CN101330720A (en) | Method for processing access user, user access system and equipment | |
| CN102348193B (en) | The method and system that a kind of gateway identification reports | |
| CN104427568A (en) | Method and device for realizing unloading of 3GPP network flow | |
| CN102014452B (en) | Method and system for implementing mobility of local IP (Internet Protocol) access connection | |
| CN101626611B (en) | Method, device and system for maintaining loading | |
| CN101483899A (en) | Method, system and network anchor point for initiating source network bearing release in switching process | |
| CN102572783B (en) | Registration processing method, system and device | |
| CN101567843B (en) | Method and device for deleting control plane tunnel | |
| CN101500220B (en) | Method, apparatus and system for notifying network releasing resource |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |