CN102083144B - Method and system for distinguishing network link type for data cache unit - Google Patents
Method and system for distinguishing network link type for data cache unit Download PDFInfo
- Publication number
- CN102083144B CN102083144B CN200910241579.XA CN200910241579A CN102083144B CN 102083144 B CN102083144 B CN 102083144B CN 200910241579 A CN200910241579 A CN 200910241579A CN 102083144 B CN102083144 B CN 102083144B
- Authority
- CN
- China
- Prior art keywords
- data
- management unit
- link
- mobility management
- type
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000006870 function Effects 0.000 description 25
- 230000005540 biological transmission Effects 0.000 description 19
- 230000004044 response Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 15
- 238000012546 transfer Methods 0.000 description 5
- 230000007704 transition Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 238000001994 activation Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/782—Hierarchical allocation of resources, e.g. involving a hierarchy of local and centralised entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/14—Multichannel or multilink protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/824—Applicable to portable or mobile terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for distinguishing a network link type for a data cache unit, comprising: when a mobility management unit builds network link, notifying the network link type to a data cache unit; and performing or indicating the mobility management unit to release resource according to the network link type by the data cache unit. The invention discloses a system for distinguishing a network link type for a data cache unit, comprising a notification module and a release module, wherein the notification module notifies the network link type to the release unit on the data cache unit side when the mobility management unit builds the network link, and the release modules performs or indicates the mobility management unit to release resource according to the network link type. The method and the system can effectively release resource reserved by forwarding links, and improve the resource utilization ratio of a core network element.
Description
Technical Field
The invention relates to the technical field of mobile communication, in particular to a method and a system for distinguishing network link types by a data cache unit under the condition of local access function use.
Background
In order to maintain the competitiveness of the third Generation mobile communication System in the communication field, provide a mobile communication service with faster rate, lower delay and more personalization for users, and at the same time, reduce the operation cost of operators, the third Generation Partnership Project (3 GPP) standard working group is working on the research of the Evolved Packet System (EPS). As shown in fig. 1, which is a schematic structural diagram of an EPS system, in fig. 1, the whole EPS system is divided into two parts, namely a radio access network and a core network, and in fig. 1, the final unified explanation of english-related chinese please see text is shown. In the core network, a home subscriber server, a mobility management entity, a serving General Packet Radio Service (GPRS) support node, a policy charging rule function entity, a serving gateway, a packet data gateway and a packet data network are included. The functions of the parts are detailed as follows:
the home subscriber server is a permanent storage place of the user subscription data and is positioned in a home network subscribed by the user.
The mobility management entity is a storage place of the user subscription data in the current network and is responsible for non-access stratum signaling management from the terminal to the network, the security verification function of the terminal, the mobility management of the terminal, the tracking and paging management function and the bearing management in the idle mode of the user.
The serving GPRS support node is a service support point for GERAN and UTRAN users to access the core network, and is similar to the mobility management entity in function, and is responsible for functions such as location update, paging management, bearer management, and the like of the users. Wherein, GERAN is a wireless Access part of GSM/EDGE and is expressed by GSM EDGEradio Access Network; UTRAN is global terrestrial Radio Access, denoted universal terrestrial Radio Access.
The service gateway is a gateway from a core network to a wireless system and is responsible for user plane bearing from a terminal to the core network, data caching in a terminal idle mode, a function of initiating a service request at a network side, legal monitoring and a function of routing and forwarding packet data; the service gateway is responsible for counting the condition of the user terminal using the wireless network, generating a bill of the terminal using the wireless network and transmitting the bill to the charging gateway.
The packet data gateway is connected to Internet and packet data network and is responsible for IP address allocation, charging function, packet filtering, policy control and other functions of terminal.
The packet data network is an IP service network of an operator, and provides IP services for users through a core network of the operator.
The policy charging rule function entity is a server in the evolution system responsible for providing rules in charging control, online credit control, threshold control and Quality of service (QoS) policies.
The Radio access Network is composed of an evolution base station (eNB, E-UTRAN NodeB) and a 3G Radio Network controller (RNC, Radio Network Control), and is mainly responsible for receiving and transmitting Radio signals, and manages Radio resources, resource scheduling and access Control of an air interface through the contact of the air interface and a terminal.
The serving GPRS support node is an upgraded serving GPRS support node, and can support an S4 interface with a serving gateway and perform interworking with a mobility management entity using a GTPv2 protocol. For the serving GPRS support node supporting the 3G core network, the network architecture of the data domain (PS) domain is different from that in fig. 1, and at this time, the serving GPRS support node is connected to the mobility management entity through a Gn interface, and the interworking is performed through a GTPv1 protocol. The serving GPRS support node cannot be connected with the serving gateway, and is connected to the gateway GPRS support node through the Gn interface to directly access the packet data network.
The femtocell or the evolved femtocell is a small-sized and low-power base station, is used as a special resource of some users, is deployed in private places such as homes, groups, companies or schools and the like, and mainly aims to provide higher service rate for the users, reduce the cost required by using high-rate services and make up for the deficiency of coverage of the existing distributed cellular wireless communication system. The home base station has the advantages of being economical, convenient, low in power output, plug and play, broadband access, single-mode terminal and the like.
The home base station may be directly connected to the core network, as shown in fig. 2, where the wireless side network element in fig. 2 may be the home base station; the home base station may also access the core network through the logical network element of the home base station gateway, as shown in fig. 3 and 4, here, the wireless side network element in fig. 3 and 4 may be a home base station. The home base station gateway has the main functions as follows: the safety of the home base station is verified, the registration of the home base station is processed, the home base station is operated, maintained and managed, the home base station is configured and controlled according to the requirements of an operator, and the home base station is responsible for exchanging data of a core network and the home base station.
In order to implement a local access function, that is, a terminal locally accesses other IP devices in a home network, IP devices in an enterprise network, or an internet, a local access gateway is added, as shown in fig. 2, 3, and 4. The local access gateway can be arranged in combination with the wireless side network element or near the wireless side network element (namely, external), or in combination with the home base station gateway or near the home base station gateway (namely, external). The Local access gateway may be a L-SGW (Local SGW), a Local L-PGW (Local PGW), a L-GGSN (Local GGSN), an external L-gw (Local gw), etc.
Fig. 5 shows data flow paths for local access and legacy core network access in a mobile communication network architecture. For a user supporting local access, a traditional core network access data path and a local access data path can be established. As shown in fig. 5, for the connection of local access, the local access data path is from the terminal to the wireless side network element to the local access gateway (L-SGW, L-PGW, L-GGSN), and data transmission does not pass through the core network. In order to realize local access of the terminal to other IP devices of the home network or the Internet, two connections can be established, and the first local access data path directly accesses the Internet, namely the Internet local access connection. The second local access data path directly accesses other IP devices of the home network, namely the home network local access connection.
Fig. 5 shows a transmission path of local access data in a connected state after a user establishes a local access connection. When the user does not receive or send local access data for a long time, the wireless side network element releases the air interface connection to enable the user to enter an idle state. At this time, if local access downlink data of the user comes, the local access gateway sends the data to a service gateway of a core network for caching, and the cached data is sent down when the user is paged to a connection state. The data transmission path in the case of the specific user state transition is shown in the schematic diagrams of the respective scenarios in fig. 6, 7, and 8. FIG. 6 is a schematic diagram of a data path when a user is in a connected state; fig. 7 is a schematic diagram illustrating a downlink data buffer when a user is in an idle state; fig. 8 is a diagram illustrating a data path when a user pages to a connected state. The scenario shown in fig. 7 is the scenario after the scenario shown in fig. 6 enters the idle state; the scenario shown in fig. 8 is the scenario after the scenario shown in fig. 7 enters the connected state.
For the data path diagram shown in fig. 8, a specific data path updating process is shown in fig. 9, where the data path updating process includes the following steps:
step 501, when the user is in an idle state, the core network mobility management entity transfers the downlink tunnel accessed locally to the core network side, and when the local access gateway receives downlink data, the data is sent to the core network service gateway for caching.
Step 502, the service gateway informs the core network mobility management entity through a downlink data notification message after receiving the downlink data.
Step 503, the core network mobility management entity triggers paging in the wireless side network element within the coverage area of the user registration area.
In step 504, the user receives the paging message and responds to the paging by initiating a service request message.
Step 505, the core network mobility management entity establishes an air interface bearer for the user, and sends all uplink tunnel identifiers of established links, security contexts, Qos parameters of radio bearers, and the like to the wireless side network element in the initial context establishment request message.
Step 506, the wireless side network element establishes a wireless bearer with the terminal user according to the indication information of the core network.
Step 507, after the air interface bearer is established, the wireless side network element informs the core network mobility management entity of the downlink tunnel identifier and the address information through the initial context establishment completion message.
In step 508, the core network mobility management entity brings the downlink tunnel identifier and the address information to the local access gateway by modifying the bearer request message.
In step 509, the local access gateway replies with a modify bearer response message.
Step 510, the wireless side network element learns the uplink tunnel identifier of the local access direct tunnel through step 505, and the local access gateway obtains the downlink tunnel identifier of the local access direct tunnel through step 508, so that the local access uplink and downlink data can be normally transmitted.
In step 511, the core network mobility management entity brings the downlink tunnel identifier and the address information to the serving gateway by modifying the bearer request message.
Step 512, the serving gateway replies with a modify bearer response message.
Step 513, after receiving the downlink tunnel identifier and the address information, the service gateway sends the cached downlink data to the user, and the local access uplink data of the user is sent through step 510 without passing through the service gateway.
In the existing implementation process, when the serving gateway receives downlink data sent from the core network access gateway, the steps of the process are also executed, even if the core network mobility management unit does not have local access data, the core network mobility management unit establishes the forwarding of local access and a direct data channel, and when the subsequent local access data exists, the steps can be directly applied. After the downlink local access cache data is sent, the data forwarding link is released by the core network mobility management unit, and the specific deletion time can be ensured by setting a timer. However, this implementation is not optimized, because even if the downlink data is only core network data, the core network mobility management unit still needs to establish a forwarding link for local access data, and reserves data link resources in a staged manner without local access cache data, that is, cannot release reserved resources in time, which may result in a problem of a decrease in resource utilization of a core network element, and there is no effective solution to this problem at present.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for distinguishing network link types by a data cache unit, which can effectively release reserved resources of a forwarding link and improve the resource utilization rate of a network element of a core network.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a method for distinguishing network link types by a data cache unit comprises the following steps: when the mobile management unit establishes a network link, the mobile management unit informs the data caching unit of the type of the network link; and the data caching unit executes or instructs the mobility management unit to release resources according to the type of the network link.
And after acquiring the type of the network link, the data caching unit locally stores the type of the network link.
Wherein, the executing or instructing, by the data caching unit according to the type of the network link, the mobility management unit to release the resource specifically includes:
when the data cache unit receives downlink data from a network link, judging that the data type of the downlink data is core network data or local data or comprises the core network data and the local data according to the stored type of the network link; and respectively executing or indicating the mobility management unit to perform corresponding operation of releasing the resources according to different judgment results.
When the data caching unit determines that the data type of the downlink data is core network data, the operation of executing or instructing the mobility management unit to release the resource specifically includes:
the data cache unit releases the forwarding link resources of the local and core network mobility management units; or,
the data cache unit informs the mobility management unit of the information capable of representing the downlink data type, and the mobility management unit releases the forwarding link resources in the local and data cache units.
Wherein the information for representing the downlink data type includes: at least one of access gateway address, access gateway identification, and newly defined downlink data type indication.
When the data caching unit determines that the data type of the downlink data is local data, instructing the mobility management unit to execute an operation of releasing resources specifically includes:
the data buffer unit informs the mobile management unit through a normal downlink data notification message;
the mobile management unit starts a forwarding link timer, and releases forwarding link resources after the forwarding link timer is overtime; or,
when the data caching unit determines that the data type of the downlink data includes core network data and local data, the operation of instructing the mobility management unit to release the resource specifically includes:
the data buffer unit informs the mobile management unit through a normal downlink data notification message;
the mobile management unit starts a forwarding link timer, and releases the forwarding link resource after the forwarding link timer is overtime.
Wherein the network link types include: at least one of a core network link and a local link.
A system for a data cache unit to distinguish network link types, the system comprising: a notification module at the side of the mobile management unit and a release module at the side of the data cache unit; wherein,
the notification module is used for notifying the type of the network link to a release module at the data cache unit side when the mobile management unit establishes the network link;
and the releasing module is used for executing or indicating the mobility management unit to release the resources according to the type of the network link.
Wherein, this system still includes: and the storage module at the data cache unit side is used for locally storing the type of the network link after the data cache unit obtains the type of the network link.
Wherein the release module further comprises: the device comprises an acquisition module, a judgment module and a release execution module; wherein,
the acquisition module is used for acquiring the type of the network link stored by the storage module when downlink data is received from the network link;
the judging module is used for judging that the data type of the downlink data is core network data or local data or comprises the core network data and the local data according to the type of the network link;
and the release execution module is used for respectively executing or indicating the mobility management unit to perform corresponding resource release operation according to different judgment results.
When the mobile management unit of the invention establishes the network link, the mobile management unit informs the data cache unit of the type of the network link; the data caching unit executes or instructs the mobility management unit to release resources according to the type of the network link.
By adopting the invention, the data cache unit can acquire the type of the network link, so the release of the reserved resource of the forwarding link can be effectively carried out, and the resource utilization rate of the core network element is improved, namely, the core network bearing processing capacity of the core network element is improved.
Drawings
FIG. 1 is a schematic diagram of an EPS system;
fig. 2 is a schematic diagram of a wireless side network element accessing a core network;
fig. 3 is another schematic diagram of the wireless side network element accessing the core network;
fig. 4 is another schematic diagram of the wireless side network element accessing the core network;
fig. 5 is a schematic diagram of data flow paths for local access and conventional core network access;
FIG. 6 is a diagram of a data transmission path in the case of user state transition;
FIG. 7 is another diagram of the data transmission path in the case of user state transition;
FIG. 8 is another schematic diagram of the data transmission path in the case of a user state transition;
FIG. 9 is a diagram illustrating a data link update when a user transitions from an idle state to a connected state;
fig. 10 is a flowchart illustrating a first embodiment of the present invention when a core network link is established in an LTE system attach process;
fig. 11 is a flowchart illustrating a second embodiment of the present invention when a core network link is established in an LTE system PDN connection establishment procedure;
fig. 12 is a flowchart illustrating a third example of the present invention when a local access forwarding link is established in a release process of an LTE system S1;
fig. 13 is a schematic flowchart of a fourth example of the present invention in which a data caching unit of an LTE system updates a link after receiving downlink data of a core network;
fig. 14 is a schematic flowchart of a fifth example of the present invention in which a data caching unit of an LTE system receives downlink data of a core network and then updates a link;
FIG. 15 is a flowchart illustrating an example six of the present invention for indicating a network link type for a GPRS system PDP context activation procedure;
fig. 16 is a flowchart illustrating a seventh example of the present invention in which a GPRS system data caching unit receives downlink data of a core network and updates a link.
Detailed Description
The basic idea of the invention is: when the mobile management unit establishes the network link, the mobile management unit informs the data caching unit of the type of the network link; the data caching unit executes or instructs the mobility management unit to release resources according to the type of the network link.
The following describes the embodiments in further detail with reference to the accompanying drawings.
A method for distinguishing network link types by a data cache unit comprises the following steps: when the core network mobility management unit establishes the network link, the core network mobility management unit informs the data cache unit of the type of the network link; the data caching unit executes or instructs the mobility management unit to release resources according to the type of the network link.
Here, after learning the type of the network link, the data caching unit locally stores the type of the network link.
Here, the step of executing or instructing, by the data caching unit, the mobility management unit to release the resource according to the type of the network link specifically includes the following steps:
step 531, when the data caching unit receives the downlink data from the network link, determining, according to the type of the stored network link, that the data type of the downlink data is core network data, or local access data, or includes the core network data and the local access data.
Step 532, respectively according to the difference of the judgment results, namely: and respectively executing or indicating the mobility management unit to perform corresponding resource releasing operation when the judgment result is the core network data, the local access data or the data including the core network data and the local access data.
The specific processing procedure of step 532 is described below.
In the first case: and the data caching unit judges the condition that the data type of the downlink data is core network data.
At this time, the operation of executing or instructing the mobility management unit to release the resource specifically includes: the data cache unit releases the forwarding link resources of the local and core network mobility management units; or the data cache unit informs the mobility management unit of the information capable of representing the downlink data type, and the mobility management unit releases the forwarding link resources in the local and data cache units.
The information for representing the downlink data type comprises: at least one of access gateway address, access gateway identification, and newly defined downlink data type indication.
In the second case: and the data cache unit judges that the data type of the downlink data is the condition of local access data.
At this time, the operation of instructing the mobility management unit to release the resource specifically includes: the data buffer unit informs the mobile management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases forwarding link resources after the forwarding link timer is overtime.
In the third case: and the data caching unit judges that the data type of the downlink data comprises core network data and local access data.
At this time, the operation of releasing the resource specifically includes: the data buffer unit informs the mobile management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases forwarding link resources after the forwarding link timer is overtime.
It should be noted that: the second and third conditions are realized by adopting the invention, which is a compatibility treatment of the prior art, and the invention not only effectively releases resources in time, but also has a compatibility function to the prior art.
The types of network links referred to above include: at least one of a core network link and a local access link.
The above-mentioned data cache unit includes: a service gateway and a service GPRS support node. Wherein, the service GPRS support node is used for supporting Gn interface.
In summary, the present invention mainly includes the following contents:
a core network mobility management unit, such as: the MME, the SGSN supporting the S4 interface and the SGSN supporting the Gn interface inform the data caching unit of the type of the network link when the network link is established, and the data caching unit stores the information. Specifically, the network link types include: core network link, local access link.
Further, when the data caching unit receives downlink data from a certain network link, it can determine whether the data type is core network data or local access data.
If the data cache unit judges that the data is core network data, two ways of releasing the resources exist, and the releaser executing the releasing operation is different.
Specifically, one way is: and the data cache unit releases the forwarding link resources of the local and core network mobility management units by deleting the bearing request message. Wherein, the delete bearer request message requires the reason value to indicate the mobility management unit to release the tunnel only and not release the bearer.
The other mode is as follows: the data buffer unit informs the mobility management unit of the information capable of representing the type of the downlink data through the downlink data notification message, and the mobility management unit initiates a session deletion request message to release the forwarding link resources in the local data buffer unit and the data buffer unit. The information characterizing the downlink data type may include the following: the access gateway address, the access gateway identifier and the newly defined downlink data type indication.
If the data cache unit judges that the data is the local access data, the data cache unit informs the mobility management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases the forwarding link resource after the timer is overtime.
If the data cache unit judges that the data has both core network data and local access data, the data cache unit informs the mobility management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases the forwarding link resource after the timer is overtime.
Here, it should be noted that: for the case that the mobility management unit is a serving GPRS support node supporting the Gn interface, the above-mentioned judgment and storage of the network link type and the release processing of the local access forwarding link resource are all completed locally in the mobility management unit, which belongs to an internal operation.
Wherein the local access function comprises: local access to the home network through the home base station, local access to the enterprise network through the home base station, access to the internet through the home base station or the macro cell.
Wherein, the data buffer unit includes: a service gateway and a service GPRS support node. Wherein, the service GPRS support node is used for supporting Gn interface.
The invention is illustrated below.
Example one: fig. 10 is an embodiment of the present invention when establishing a core network link in an LTE system attach process, specifically including the following steps:
step 601, when the user starts up and registers in the network, an attach request is initiated, wherein the attach request carries an APN or willingness indication that the user needs to request network link.
Step 602, the wireless side network element forwards the attach request message, and brings the capability of whether the wireless side network element supports local access to the mobility management unit through the initialized non-access stratum message of the bottom layer. Wherein the wireless side network element comprises: a home base station, a macro base station, and a home base station gateway. The mobility management element may be a mobility management entity or a serving GPRS support node supporting the S4 interface.
Step 603, the mobility management unit authenticates and authorizes the user according to the user security information in the attach request message, and ensures that the authorized user accesses the network.
Step 604, if the mobility management unit does not have the subscription data of the user, the home subscriber data server is requested to issue the subscription information of the user through the update location request message.
Step 605, the home subscriber data server issues the subscription data of the user to the mobility management unit through the update location confirmation message.
Step 606, the mobility management unit determines the type of the network link established for the user according to the Access Point Name (APN) or willingness indication requested by the user in combination with the subscription data of the user, and selects a suitable access gateway.
Here, if the user requests a local access link or the network decides to establish a local access link for the user, the mobility management unit selects a local access gateway for the user to complete the local access function of the user. If the user requests the core network link or the network determines to establish the core network link for the user, the mobility management unit selects a core network access gateway for the user to complete the function that the user accesses the internet through the core network. In this embodiment, a description is given by taking an example that a user requests a core network link or a network decides to establish a core network link for the user, and corresponding processes for establishing a local access link are similar, except that a brief description is given in the implementation steps.
In step 607, if the established link is a core network link, the mobility management unit selects a suitable serving gateway according to the access gateway and performs a network link establishment procedure through a create session request message. Which carries the network link type information determined in step 606.
Here, if the established link is a local access link, the mobility management unit directly sends a session establishment request message to the local access gateway in the existing direct tunnel manner, and does not perform service gateway selection and establish a local access link through the service gateway, at this time, the mobility management unit stores the network link type, and notifies the network link type when the user subsequently transfers to an idle state to establish a local access forwarding channel, as shown in the embodiment described in example three of fig. 12.
Step 608, the serving gateway establishes a context corresponding to the network link at the access gateway through the session creation request message, and reports the access gateway address and the tunnel identifier to the access gateway for downlink data transmission.
In step 609, the access gateway replies to the serving gateway with a create session response message. And bringing the uplink tunnel identifier allocated by the access gateway for uplink data transmission to the access gateway.
The serving gateway replies 610 with a create session response message to the mobility management unit. And bringing the uplink tunnel identifier allocated by the serving gateway for uplink data transmission to the mobility management unit.
Step 611, performing subsequent attach procedures including procedures of establishing a radio bearer, opening an uplink tunnel and a downlink tunnel, which are the same as in the prior art and are not described in detail.
Example two: fig. 11 is an implementation manner of the present invention when a core network link is established in an LTE system PDN connection establishment procedure, specifically including the following steps:
step 701, when a user needs to access new internet content, a PDN connection request is initiated, where the PDN connection request carries an APN or willingness indication for which the user needs to request a network link.
Step 702, the wireless side network element forwards the PDN connection request message, and brings the capability of whether the wireless side network element supports local access to the mobility management unit through the bottom layer direct transfer message. Wherein the wireless side network element comprises: a home base station, a macro base station, and a home base station gateway. The mobility management unit may be a mobility management entity MME or a serving GPRS support node SGSN supporting the S4 interface.
In step 703, the mobility management unit determines the type of the network link established for the user according to the APN requested by the user or the willingness indication in combination with the user subscription data downloaded in the attach process, and selects a suitable access gateway.
Here, if the user requests a local access link or the network decides to establish a local access link for the user, the mobility management unit selects a local access gateway for the user to complete the local access function of the user. If the user requests the core network link or the network determines to establish the core network link for the user, the mobility management unit selects a core network access gateway for the user to complete the function that the user accesses the internet through the core network. In this embodiment, a description is given by taking an example that a user requests a core network link or a network decides to establish a core network link for the user, and corresponding processes for establishing a local access link are similar, except that a brief description is given in the implementation steps.
In step 704, if the established link is a core network link, the mobility management unit selects a suitable serving gateway according to the access gateway and performs a network link establishment procedure through a create session request message. The information of the network link type determined in step 703 is carried.
Here, if the established link is a local access link, the mobility management unit directly sends a session establishment request message to the local access gateway in the existing direct tunnel manner, and does not perform service gateway selection and establish a local access link through the service gateway, at this time, the mobility management unit stores the network link type, and notifies the network link type when the user subsequently transfers to an idle state to establish a local access forwarding channel, as shown in the embodiment described in example three of fig. 12.
Step 705, the serving gateway establishes a context corresponding to the network link at the access gateway through the session creation request message, and reports the access gateway address and the tunnel identifier to the access gateway for downlink data transmission.
In step 706, the access gateway replies a create session response message to the serving gateway. And bringing the uplink tunnel identifier allocated by the access gateway for uplink data transmission to the access gateway.
In step 707, the serving gateway replies to the mobility management unit with a create session response message. And bringing the uplink tunnel identifier allocated by the serving gateway for uplink data transmission to the mobility management unit.
Step 708, the subsequent PDN connection establishment procedure is executed, which includes the establishment of radio bearer, the opening of uplink and downlink tunnels, and so on, and is the same as the prior art and is not described again.
Example three: fig. 12 is an embodiment of the present invention when a local access forwarding link is established in a release process of S1 in an LTE system, and specifically includes the following steps:
step 801, if the wireless side network element decides to release the signaling connection of the user due to O & M interoperation, user deactivation, repeated integrity check failure, etc., a user context release request message is sent S1 to the mobility management unit. After the mobility management unit completes the signaling and data transmission process, the signaling connection release of the user is also initiated to save network resources, and the user is converted from the connection state to the idle state, at this time, step 801 is not needed.
In step 802, the mobility management unit determines whether the user currently has an activated local access link, and if not, performs a normal S1-U interface bearer release process, which is not described in detail for the prior art. If so, a forwarding channel of the local access link is created.
If the current user has an activated local access link, step 803, the mobility management unit informs the serving gateway of the network link type by creating a session request.
Step 804, the serving gateway informs the local access gateway of the address of the serving gateway and the tunnel identification information of the downlink cache channel by modifying the bearer request message. At this time, the local access gateway already has context information of the local access link, so that only the serving gateway needs to perform tunnel update. And after the local access gateway tunnel is updated, the local access downlink data can be cached.
In step 805, the local access gateway replies to the serving gateway with a modify bearer response message.
The serving gateway replies to the mobility management unit with a create session response message, step 806.
In step 807, the subsequent S1 link releasing process is continuously completed, the air interface resource is released, and the user is switched from the connection state to the idle state.
Example four: fig. 13 is a first embodiment of a data caching unit in an LTE system after receiving downlink data from a core network, where the method includes the following steps:
step 901, the core network access gateway sends the received user downlink data to the serving gateway serving as the cache unit.
Step 902, the serving gateway determines the source of the downlink data according to the network link used for downlink data transmission and in combination with the stored network link type.
In step 903, the serving gateway brings information characterizing the downlink data type to the mobility management unit in the downlink data notification message, where the information characterizing the downlink data type may include the following: the access gateway address, the access gateway identifier and the newly defined downlink data type indication.
In step 904, the mobility management unit initiates paging in the area where the user is registered.
Step 905, the user initiates a service request to respond after receiving the paging message.
Step 906, the mobility management unit instructs the wireless side to establish an air interface bearer through the initial context establishment request message, where the message carries the uplink tunnel identifier, the address information, and the bearer Qos information of the local access direct tunnel.
And step 907, the wireless side network element establishes an air interface bearer according to the bearer Qos information. Wherein the wireless side network element comprises: a home base station, a macro base station, and a home base station gateway.
Step 908, the wireless side network element brings the allocated downlink tunnel id and address information to the mobility management unit through the initial context setup complete message.
In step 909, the user enters a connection state, the mobility management unit brings the downlink tunnel identifier, address information, and the like allocated by the wireless side network element to the local access gateway by modifying the bearer request message, and opens the data downlink transmission channel of the local access link.
In step 910, the local access gateway replies a modify bearer response message to the mobility management unit.
In step 911, the wireless side network element knows the uplink tunnel identifier of the local access direct tunnel through step 906, and the local access gateway obtains the downlink tunnel identifier of the local access direct tunnel through step 909, so that the uplink and downlink data of the local access can be normally transmitted.
In step 912, since the downlink data is from the core network, the mobility management unit initiates deletion of the local access downlink forwarding network link, and the mobility management unit deletes the context corresponding to the forwarding network link through the delete session request.
In step 913, if the serving gateway finds that the network link is for local access, the corresponding context is deleted and a delete session response message is replied.
In the present invention, when the mobility management unit learns the downlink data source in step 903, step 912 and step 913 may be initiated to delete the local access forwarding network link, so the order of the steps is not limited.
Example five: fig. 14 is a second embodiment of a data caching unit in an LTE system after receiving downlink data from a core network, where the method includes the following steps:
step 1001, the core network access gateway sends the received user downlink data to the serving gateway serving as the cache unit.
Step 1002, the serving gateway determines a source of the downlink data according to the network link used for downlink data transmission and in combination with the stored network link type.
Step 1003, the serving gateway sends a downlink data notification message to the mobility management unit to trigger a paging procedure.
In step 1004, the mobility management unit initiates paging in the area where the user is registered.
Step 1005, the user initiates the service request to respond after receiving the paging message.
Step 1006, the mobility management unit instructs the wireless side to establish an air interface bearer through the initial context establishment request message, where the message carries the uplink tunnel identifier, the address information, and the bearer Qos information of the local access direct tunnel.
Step 1007, the wireless side network element establishes an air interface bearer according to the bearer Qos information. Wherein the wireless side network element comprises: a home base station, a macro base station, and a home base station gateway.
Step 1008, the wireless side network element brings the allocated downlink tunnel identifier and address information to the mobility management unit through the initial context setup complete message.
Step 1009, the user enters the connection state, the mobility management unit brings the downlink tunnel identifier, the address information and the like allocated by the wireless side network element to the local access gateway through modifying the bearer request message, and gets through the data downlink transmission channel of the local access link.
Step 1010, the local access gateway replies a modify bearer response message to the mobility management unit.
In step 1011, the wireless side network element knows the uplink tunnel identifier of the local access direct tunnel in step 1006, and the local access gateway obtains the downlink tunnel identifier of the local access direct tunnel in step 1009, so that the uplink and downlink data of the local access can be normally transmitted.
In step 1012, since the downlink data is from the core network, the serving gateway initiates deletion of the local access downlink forwarding network link, and the serving gateway deletes the user plane tunnel corresponding to the forwarding network link through a delete bearer request carrying a special cause value. The special reason value is used for indicating the mobility management unit to only delete the tunnel information, and the carried control plane information is reserved for being used when the local access direct tunnel is established.
Step 1013, the mobility management unit deletes the bearer information corresponding to the network link and replies a delete bearer response message.
In the present invention, when the serving gateway learns the downlink data source in step 1002, step 1012 and step 1013 may be initiated to delete the local access forwarding network link, so the order of the steps is not limited. In the method of this embodiment, the mobility management unit cannot know the source of the downlink data, and therefore, if the establishment of the radio bearer is completed before step 1012 is received, it still initiates the update of the forwarding network link, and at this time, the serving gateway receives the update message, ignores it and does not respond.
Example six: fig. 15 is an implementation of a GPRS system Packet Data Protocol (PDP) context activation process, in which a core network indicates a network link type, and specifically includes the following steps:
step 1101, when the user needs to access new internet content, a request message for activating PDP context is initiated, wherein the request message carries an APN or willingness indication that the user needs to request a network link.
Step 1102, the wireless side network element forwards the activate PDP context request message and brings the capability of whether the wireless side network element supports local access to the serving GPRS support node through the bottom layer direct transfer message.
Step 1103, the serving GPRS support node determines the type of network link established for the user according to the APN requested by the user or the willingness indication in combination with the user subscription data downloaded during the attach procedure, and selects a suitable access gateway.
Here, since the serving GPRS support node serves as a cache point for downlink data of the 3G system, the type of the established network link is locally stored after the determination. If the user requests the local access link or the network decides to establish the local access link for the user, the mobility management unit selects a local access gateway for the user to complete the local access function of the user. If the user requests the core network link or the network determines to establish the core network link for the user, the mobility management unit selects a core network access gateway for the user to complete the function that the user accesses the internet through the core network. In this embodiment, a description is given by taking an example that a user requests a core network link or a network decides to establish a core network link for the user, and corresponding processes for establishing a local access link are similar, except that a brief description is given in the implementation steps.
In step 1104, if the established link is a core network link, the serving GPRS support node performs a network link establishment procedure by creating a PDP context request message. And if the established link is a local access link, the serving GPRS support node directly sends a request message for creating the PDP context to the local access gateway.
Step 1105, the access gateway, including the core network access gateway and the locally visited access gateway, replies to create a PDP context response and brings the allocated uplink tunnel identifier and address information to the serving GPRS support node.
Step 1106, the serving GPRS support node indicates the wireless side network element to establish an air interface bearer, where the wireless side network element may be: a home base station, a macro base station, and a home base station gateway.
If the established network link is a local access link, the serving GPRS support node judges that a direct tunnel mode is adopted to bring the uplink tunnel identifier and the address information distributed by the local access gateway to the wireless side network element. And if the established network link is a core network link, the serving GPRS support node brings the uplink tunnel identifier and the address information allocated by the serving GPRS support node to the wireless side network element.
And after the radio bearer is established, the radio side network element brings the downlink tunnel identifier and the address information distributed by the radio side network element to the serving GPRS support node.
Step 1107, when establishing the core network link, if the Qos negotiation is needed, then the step is executed, and the Qos information requested by the wireless side is brought to the access gateway, otherwise, the step can be ignored. If the local access link is established, the step establishes a direct tunnel of the local access, brings the downlink tunnel identifier and the address information distributed by the wireless side network element to the local access gateway, and gets through the downlink channel.
In step 1108, the access gateway replies with an update PDP context response message.
The serving GPRS support node returns an activate PDP context accept message, step 1109.
Since the serving GPRS support node itself is also a data cache unit, the network link type is always saved after the network link is established, and even if the user enters an idle state (Iu connection release process), the network link type is not released, and the serving GPRS support node only needs to update the tunnel to the local access gateway.
Example seven: fig. 16 is an implementation of a link update after a GPRS system data cache unit receives core network downlink data, which specifically includes the following steps:
step 1201, the core network access gateway sends the received user downlink data to the serving GPRS support node as a cache unit.
Step 1202, the serving GPRS support node determines the source of the downlink data according to the network link used for downlink data transmission, in combination with the stored network link type. If the downlink data is known to be core network data, the user plane information of the local access forwarding link is released, which is the internal operation of the serving GPRS support node, and the specific mode is not described.
In step 1203, the serving GPRS support node initiates paging in the area where the user is registered.
Step 1204, the user initiates a service request to respond after receiving the paging message.
Step 1205, the serving GPRS support node indicates the radio side to establish an air interface bearer through the radio bearer assignment request message, where the message carries the uplink tunnel identifier, address information, and bearer Qos information of the local access direct tunnel.
And step 1206, the wireless side network element establishes an air interface bearer according to the bearer Qos information. Wherein the wireless side network element comprises: a home base station, a macro base station, and a home base station gateway.
Step 1207, the wireless side network element sends the allocated downlink tunnel identifier and address information to the serving GPRS support node through the radio bearer assignment response message.
Step 1208, when the user enters the connection state, the serving GPRS support node sends the downlink tunnel id, address information, etc. allocated by the radio side network element to the local access gateway through the PDP context update request message, and gets through the data downlink transmission channel of the local access link.
Step 1209, the local access gateway replies to the serving GPRS support node with a modify bearer response message.
Step 1210, the wireless side network element learns the uplink tunnel identifier of the local access direct tunnel through step 1205, and the local access gateway obtains the downlink tunnel identifier of the local access direct tunnel through step 1208, so that the local access uplink and downlink data can be normally transmitted through the direct tunnel.
In all the scenarios of the above embodiments of the present invention, if the data caching unit determines that the data is the local access data, the data caching unit notifies the mobility management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases the forwarding link resource after the timer is overtime.
If the data cache unit judges that the data has both core network data and local access data, the data cache unit informs the mobility management unit through a normal downlink data notification message. The core network mobility management unit starts a forwarding link timer according to the prior art, and releases the forwarding link resource after the timer is overtime.
A system for a data cache unit to distinguish network link types, the system comprising: a notification module at the side of the mobility management unit and a release module at the side of the data cache unit. The notification module is used for notifying the type of the network link to the release module at the data cache unit side when the mobility management unit establishes the network link. And the releasing module is used for executing or indicating the mobility management unit to release the resources according to the type of the network link.
Here, the system further includes: and the storage module at the data cache unit side is used for locally storing the type of the network link after the data cache unit obtains the type of the network link.
Here, the release module further includes: the device comprises an acquisition module, a judgment module and a release execution module. The acquisition module is used for acquiring the type of the network link stored by the storage module when downlink data is received from the network link. And the judging module is used for judging that the data type of the downlink data is core network data or local access data or comprises the core network data and the local access data according to the type of the network link. And the release execution module is used for respectively executing or indicating the mobility management unit to perform corresponding resource release operation according to different judgment results.
Here, the matters related to the chinese and english comments referred to in the above figures and characters are explained collectively as follows:
the Home Subscriber Server is expressed by a Home Subscriber Server, abbreviated as HSS; the Mobility Management Entity is expressed by Mobility Management Entity, and is abbreviated as MME; the Serving GPRS Support Node is expressed by Serving GPRS Support Node, abbreviated as SGSN; the policy Charging Rule Function is expressed by policy and Charging Rule Function, abbreviated as PCRF; the Serving Gateway is expressed by Serving Gateway, abbreviated as S-GW, which is Serving GW in fig. 1; the packet data Gateway is denoted by PDN Gateway, abbreviated as P-GW, which is the PDN GW in fig. 1; packet data networks are denoted by Packet data networks, abbreviated as PDNs; the RNC in fig. 1 is a radio network controller; the E-NodeB in fig. 1 is an evolved node b, which may also be denoted as eNB; the CN in fig. 5 is a core network; the Gateway GPRS Support Node is expressed by Gateway GPRS Support Node, abbreviated as GGSN; the Home base station is expressed by Home NodeB, abbreviated as HNB; the evolved Home base station is denoted by Home eNodeB, abbreviated as HeNB; the Local Access function is denoted by Local IP Access or Selected IP Traffic off flow, abbreviated LIPA or SIPTO.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (7)
1. A method for distinguishing network link types by a data cache unit is characterized by comprising the following steps: when the mobile management unit establishes a network link, the mobile management unit informs the data caching unit of the type of the network link; the data caching unit executes or instructs a mobility management unit to release resources according to the type of the network link; wherein,
the data caching unit executes or instructs a mobility management unit to release resources according to the type of the network link, and specifically includes: when the data cache unit receives downlink data from a network link, judging that the data type of the downlink data is core network data or local data or comprises the core network data and the local data according to the type of the network link, and respectively executing or indicating a mobility management unit to perform corresponding resource releasing operation according to different judgment results; wherein,
when the data caching unit determines that the data type of the downlink data is core network data, the operation of executing or instructing the mobility management unit to release resources includes: the data cache unit releases the forwarding link resources of the local and core network mobility management units; or the data cache unit informs the mobility management unit of the information capable of representing the downlink data type, and the mobility management unit releases the forwarding link resources in the local and data cache units.
2. The method according to claim 1, wherein the data caching unit locally saves the type of the network link after learning the type of the network link.
3. The method according to claim 1 or 2, wherein the information characterizing the downlink data type comprises: at least one of access gateway address, access gateway identification, and newly defined downlink data type indication.
4. The method according to claim 1 or 2, wherein, when the data caching unit determines that the data type of the downlink data is local data, instructing the mobility management unit to perform the operation of releasing the resource specifically includes:
the data buffer unit informs the mobile management unit through a normal downlink data notification message;
the mobile management unit starts a forwarding link timer, and releases forwarding link resources after the forwarding link timer is overtime; or,
when the data caching unit determines that the data type of the downlink data includes core network data and local data, the operation of instructing the mobility management unit to release the resource specifically includes:
the data buffer unit informs the mobile management unit through a normal downlink data notification message;
the mobile management unit starts a forwarding link timer, and releases the forwarding link resource after the forwarding link timer is overtime.
5. The method according to any of claims 1 or 2, wherein the network link type comprises: at least one of a core network link and a local link.
6. A system for a data cache unit to distinguish network link types, the system comprising: a notification module at the side of the mobile management unit and a release module at the side of the data cache unit; wherein,
the notification module is used for notifying the type of the network link to a release module at the data cache unit side when the mobile management unit establishes the network link;
a release module, configured to execute or instruct a mobility management unit to release resources according to the type of the network link; wherein the release module further comprises:
the acquisition module is used for acquiring the type of the network link when downlink data is received from the network link; the judging module is used for judging that the data type of the downlink data is core network data or local data or comprises the core network data and the local data according to the type of the network link; a release execution module, configured to respectively execute or instruct the mobility management unit to perform a corresponding resource release operation according to different determination results; wherein,
when the determining module determines that the data type of the downlink data is core network data, the release executing module executes or instructs the mobility management unit to release the resource, specifically including: the releasing execution module releases the forwarding link resources of the local and core network mobility management units; or, the release execution module informs the mobility management unit of the information capable of representing the downlink data type, and the mobility management unit releases the forwarding link resources in the local and data cache units.
7. The system of claim 6, further comprising: and the storage module at the data cache unit side is used for locally storing the type of the network link after the data cache unit obtains the type of the network link.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910241579.XA CN102083144B (en) | 2009-11-26 | 2009-11-26 | Method and system for distinguishing network link type for data cache unit |
| PCT/CN2010/078107 WO2011063692A1 (en) | 2009-11-26 | 2010-10-26 | Method and system for distinguishing type of network link by data buffer unit |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910241579.XA CN102083144B (en) | 2009-11-26 | 2009-11-26 | Method and system for distinguishing network link type for data cache unit |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102083144A CN102083144A (en) | 2011-06-01 |
| CN102083144B true CN102083144B (en) | 2014-01-01 |
Family
ID=44065853
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910241579.XA Expired - Fee Related CN102083144B (en) | 2009-11-26 | 2009-11-26 | Method and system for distinguishing network link type for data cache unit |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102083144B (en) |
| WO (1) | WO2011063692A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015077921A1 (en) * | 2013-11-26 | 2015-06-04 | 华为技术有限公司 | Access network entity, core network device, and method therefor for acquiring related policy of ue |
| CN106412948B (en) * | 2015-07-31 | 2019-09-20 | 联芯科技有限公司 | A kind of transmission method and its transmission terminal being related to NAS signaling message |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101282511A (en) * | 2008-05-16 | 2008-10-08 | 中兴通讯股份有限公司 | Bearing processing method |
| CN101296493A (en) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | Resource release method and network equipment |
| CN101448249A (en) * | 2008-01-25 | 2009-06-03 | 中兴通讯股份有限公司 | Method for releasing data cached in serving gateway |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101060709A (en) * | 2006-04-20 | 2007-10-24 | 华为技术有限公司 | The objective network reserve resource processing method and system during the heterogeneous network switching process |
| KR101012004B1 (en) * | 2006-10-18 | 2011-01-31 | 삼성전자주식회사 | Apparatus and method for resource saving between core network and control station in mobile communication system |
| CN101330753B (en) * | 2007-06-22 | 2014-07-09 | 华为技术有限公司 | Method for establishing and erasuring resource as well as network appliance |
| CN101867983B (en) * | 2009-04-16 | 2013-03-27 | 电信科学技术研究院 | Switching method, system and device |
-
2009
- 2009-11-26 CN CN200910241579.XA patent/CN102083144B/en not_active Expired - Fee Related
-
2010
- 2010-10-26 WO PCT/CN2010/078107 patent/WO2011063692A1/en not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101296493A (en) * | 2007-04-24 | 2008-10-29 | 华为技术有限公司 | Resource release method and network equipment |
| CN101448249A (en) * | 2008-01-25 | 2009-06-03 | 中兴通讯股份有限公司 | Method for releasing data cached in serving gateway |
| CN101282511A (en) * | 2008-05-16 | 2008-10-08 | 中兴通讯股份有限公司 | Bearing processing method |
Non-Patent Citations (3)
| Title |
|---|
| 3GPP.Technical Specification Group Services and System Aspects * |
| Architecture enhancements for non-3GPP accesses(Release 8).《3GPP TS 23.402》.2008, * |
| General Packet Radio Service (GPRS) enhancements forEvolved Universal Terrestrial Radio Access Network(E-UTRAN) access (Release 8).《3GPP TS 23.401》.2008, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102083144A (en) | 2011-06-01 |
| WO2011063692A1 (en) | 2011-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10219143B2 (en) | Data transmission method, mobility management entity, and mobile terminal | |
| EP2445261B1 (en) | Method, apparatus and system for routing user plane data in mobile network | |
| US8811317B2 (en) | Method for implementing local access and system thereof | |
| US20100226314A1 (en) | Method for user equipment performing direct communications via hnb access systems | |
| US8730831B2 (en) | Method and system for acquiring route strategies | |
| CN102056142B (en) | Method and system for setting local IP access downlink data channel | |
| US8743752B2 (en) | Method and apparatus for status transition | |
| WO2011095100A1 (en) | Method and system for controlling establishment of local ip access | |
| WO2012094957A1 (en) | Method and system for performing mobility management on mtc terminal | |
| CN101990192A (en) | Notification method and device for local IP access connection property | |
| CN102469619B (en) | A kind of mobile communication system and the method for gateway reorientation thereof | |
| CN102378160B (en) | Based on carrying establishing method and the system of this locality access | |
| CN101998365B (en) | Method and device for source management of communication system supporting local IP access | |
| CN102056141B (en) | System and method for realizing local access | |
| CN102056145B (en) | Method and system for releasing tunnel connection in communication system supporting local IP access | |
| CN103428888A (en) | Method and system for establishing direct tunnel | |
| CN102056136B (en) | Tunnel updating method and system in communication system supporting local IP access | |
| CN102256326B (en) | A kind of method and apparatus realizing Route Selection | |
| CN102083144B (en) | Method and system for distinguishing network link type for data cache unit | |
| CN101959176A (en) | Implementation method and system for establishing local IP access connection | |
| CN102026409B (en) | System and method for releasing local internet protocol (IP) access connection | |
| CN102857936B (en) | The processing method and processing device of local IP access connection in handoff procedure | |
| CN102026400A (en) | System and method for realizing local access | |
| CN101998364B (en) | Method and system for managing local internet protocol access connection | |
| CN102149067B (en) | Method for managing local IP data and mobile communication system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140101 Termination date: 20171126 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |