WO2011063692A1 - 一种数据缓存单元区分网络链接类型的方法及系统 - Google Patents

一种数据缓存单元区分网络链接类型的方法及系统 Download PDF

Info

Publication number
WO2011063692A1
WO2011063692A1 PCT/CN2010/078107 CN2010078107W WO2011063692A1 WO 2011063692 A1 WO2011063692 A1 WO 2011063692A1 CN 2010078107 W CN2010078107 W CN 2010078107W WO 2011063692 A1 WO2011063692 A1 WO 2011063692A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
mobility management
type
link
management unit
Prior art date
Application number
PCT/CN2010/078107
Other languages
English (en)
French (fr)
Inventor
王静
周娜
梁爽
霍玉臻
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011063692A1 publication Critical patent/WO2011063692A1/zh

Links

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

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method and system for distinguishing a network link type by a data buffer unit in the case of a local access function. Background technique
  • FIG. 1 shows the structure of the EPS system.
  • the entire EPS system is divided into two parts: the wireless access network and the core network.
  • the Chinese in English in Figure 1 can be found in the final explanation of the text.
  • a home subscriber server, a mobility management entity, a service general packet radio service (GPRS) support node, a policy charging rule function entity, a service gateway, a packet data gateway, and a packet data network are included.
  • GPRS general packet radio service
  • the home subscriber server is the permanent storage location of the subscriber's subscription data, and is located in the home network to which the subscriber subscribes.
  • the mobility management entity is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging. Management functions and bearer management.
  • the service GPRS support node is a service support point for GERAN and UTRAN users to access the core network, and is similar in function to the mobility management entity, and is responsible for user location update, paging management, and bearer management functions.
  • GERAN is the wireless access part of GSM/EDGE, represented by GSM EDGE Radio Access Network
  • UTRAN is the global terrestrial wireless access, According to Universal Terrestrial Radio Access.
  • the service gateway is a gateway of the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function; It is responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDR of the terminal using the wireless network, and transmits it to the charging gateway.
  • the packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy control of the terminal.
  • the packet data network is the operator's IP service network, which provides IP services to users through the carrier's core network.
  • the policy charging rule function entity is a server in the evolved system that provides rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.
  • the radio access network is composed of an evolved base station (eNB, E-UTRAN NodeB) and a 3G radio network controller (RNC, Radio Network Control), which is mainly responsible for transmitting and receiving wireless signals, and communicating with the terminal through the air interface to manage the air interface. Radio resources, resource scheduling, access control.
  • eNB evolved base station
  • RNC Radio Network Control
  • the above service GPRS support node is an upgraded service GPRS support node, capable of supporting the S4 interface with the service gateway, and interworking with the mobility management entity using the GTPv2 protocol.
  • the data domain (PS) domain network architecture is different from that of FIG. 1.
  • the service GPRS support node and the mobility management entity are connected by using the Gn interface, and the interworking is performed.
  • the service GPRS support section cannot be connected to the service gateway, and is connected to the gateway via the Gn interface.
  • the GPRS support node directly accesses the packet data network.
  • a home base station or an evolved home base station is a type of small, low-power base station, as some
  • the user's exclusive resources are deployed in private places such as homes, groups, companies, or schools, primarily to provide users with higher service rates and lower the cost of using high-rate services, while compensating for existing distributed cellular wireless communications. Insufficient system coverage.
  • the advantages of home base stations are affordability, convenience, low power output, plug and play, broadband access, use of single mode terminals, and more.
  • the home base station can be directly connected to the core network, as shown in FIG. 2, where the wireless side network element in FIG. 2 can be a home base station; the home base station can also access the core network through the home base station gateway. 3, 4, here, the wireless side network element in Figures 3 and 4 can be a home base station.
  • the main functions of the home base station gateway are: verifying the security of the home base station, processing the registration of the home base station, performing operation and maintenance management on the home base station, configuring and controlling the home base station according to the operator's requirements, and exchanging data of the core network and the home base station.
  • the terminal adds local gateways to other IP devices on the home network, IP devices in the enterprise network, or the Internet access, as shown in Figures 2, 3, and 4.
  • the addition of the local gateway can provide strong support for the local access technology.
  • the local gateway can be set up with the wireless side network element, or near the wireless side network element (ie, externally), or can be set up with the home base station gateway, or at home. Near the base station gateway (ie external).
  • the local gateway may be an L-SGW (Local SGW, Local SGW), a local L-PGW (Local PGW, Local PGW), an L-GGSN (Local GGSN, Local GGSN), an external L-GW (Local GW), and the like.
  • Figure 5 shows the data flow path for local access and traditional core network access in a mobile communication network architecture.
  • traditional core network access data paths and local access data paths can be established.
  • the local access data path is from the terminal to the wireless side network element to the local gateway (L-SGW, L-PGW, L-GGSN), and the data transmission does not pass through the core network.
  • L-SGW, L-PGW, L-GGSN local gateway
  • two connections may be established, and the first local access data path directly accesses the Internet, that is, the Internet local access connection.
  • the second local access data path directly accesses other IP devices on the home network, that is, the home network local access connection.
  • Figure 5 shows the transmission path of the locally accessed data in the connected state after the user establishes a local access connection.
  • the wireless side network element releases the air interface to make the user enter the idle state.
  • the local gateway sends the data to the service gateway of the core network for caching, and the cached data is sent when the user is paged to the connection state.
  • the local access downlink data is not lost, providing users with good service awareness.
  • the data transmission path in the case of a specific user state transition is shown in the schematic diagrams of various scenarios in FIGS. 6, 7, and 8. 6 is a schematic diagram of a data path when the user is in a connected state; FIG.
  • FIG. 7 is a schematic diagram of a downlink data cache when the user is in an idle state
  • FIG. 8 is a schematic diagram of a data path when the user is paging to a connected state.
  • the scene shown in FIG. 6 is the scene shown in FIG. 7 after entering the idle state; the scene shown in FIG. 7 is the scene shown in FIG. 8 after entering the connected state.
  • the update process of the data path includes the following steps:
  • Step 501 The core network mobility management entity transfers the locally visited downlink tunnel to the core network side when the user is in an idle state, and sends the data to the core network serving gateway for buffering when the local gateway receives the downlink data.
  • Step 502 After receiving the downlink data, the serving gateway notifies the core network mobility management entity by using a downlink data notification message.
  • Step 503 The core network mobility management entity triggers paging in the wireless side network element in the coverage area of the user registration area.
  • Step 504 The user receives the paging message and responds to the paging by initiating the service request message.
  • Step 505 The core network mobility management entity establishes an air interface bearer for the user, and sends an uplink tunnel identifier, a security context, a wireless bearer Qos parameter, and the like of all the established links to the radio side network element in the initial context setup request message.
  • Step 506 The wireless side network element establishes a presence with the end user according to the indication information of the core network. Line bearing.
  • Step 507 After the air interface bearer is established, the radio side network element informs the core network mobility management entity by using the initial context setup complete message and the downlink tunnel identifier and the address information.
  • Step 508 The core network mobility management entity brings the downlink tunnel identifier and the address information to the local gateway by modifying the bearer request message.
  • Step 509 The local gateway replies with the tamper response message.
  • step 510 the wireless side network element learns to access the uplink tunnel identifier of the direct tunnel through the step 505.
  • the local gateway obtains the downlink tunnel identifier of the local tunnel through the step 508, and the local access uplink and downlink data can be normally transmitted.
  • 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 to modify the bearer response message.
  • Step 513 After receiving the downlink tunnel identifier and the address information, the serving gateway sends the buffered downlink data to the user, and the local access uplink data of the user is sent through step 510, and no longer passes through the service gateway.
  • Steps 508 and 509 are optionally forwarded through the serving gateway.
  • the steps described in this process are also performed, even if there is no local access data core network mobility management unit, the local access forwarding and direct The data channel is established and can be directly applied when there is local access data.
  • the data forwarding link is initiated by the core network mobility management unit. The specific deletion time can be guaranteed by setting a timer.
  • the main purpose of the present invention is to provide a method and system for distinguishing a network link type by a data buffer unit, which can effectively release a reserved resource of a forwarding link and improve resource utilization of a core network element.
  • a data cache unit distinguishes a network link type, the method includes: the mobility management unit notifying a data cache unit of a type of the network link when establishing a network link; the data cache unit according to the type of the network link Execute or instruct the mobility management unit to release resources.
  • the data cache unit saves the type of the network link locally after learning the type of the network link.
  • the data cache unit performs or indicates that the mobility management unit releases the resource according to the type of the network link, including:
  • the data buffering unit When the data buffering unit receives the downlink data from the network link, determining, according to the type of the stored network link, the data type of the downlink data is core network data, or local data, or includes core network data and Local data; respectively, according to different judgment results, respectively performing or instructing the mobility management unit to perform corresponding operations of releasing resources.
  • the performing or instructing the mobility management unit to release the resource includes:
  • the forwarding link resources of the local and core network mobility management units are released by the data buffer unit;
  • the data buffer unit notifies the mobility management unit of the information capable of characterizing the downlink data type, and the mobility management unit releases the forwarding link resources in the local and data buffer units.
  • the information indicating the downlink data type includes: a gateway address, a gateway identifier, and a new At least one of the defined downstream data type indications.
  • the operation of instructing the mobility management unit to perform the release of the resource includes:
  • the data buffering unit informs the mobility management unit by using a normal downlink data notification message; the forwarding link timer is enabled by the mobility management unit, and the forwarding link resource is released after the forwarding link timer expires; or
  • the operation for instructing the mobility management unit to release the resource includes:
  • the data buffer unit notifies the mobility management unit of the normal downlink data notification message; the mobility management unit enables the forwarding link timer to release the forwarding link resource after the forwarding link timer expires.
  • the network link type includes: at least one of a core network link and a local link.
  • a data cache unit distinguishes a network link type system, the system includes: a notification module on the mobility management unit side, and a release module on the data cache unit side;
  • a notification module configured to: when the network link is established, the mobility management unit notifies the release module of the data cache unit side of the type of the network link;
  • a release module configured to perform or instruct the mobility management unit to release the resource according to the type of the network link.
  • the system further includes: a saving module on the data cache unit side, configured to save the type of the network link locally after the data cache unit learns the type of the network link.
  • the release module further includes: an obtaining module, a determining module, and a release executing module; wherein,
  • An obtaining module configured to acquire, when receiving downlink data from the network link, a type of the network link saved by the saving module
  • a determining module configured to determine, according to the type of the network link, data of the downlink data
  • the type is the core network data, or the local data, or includes the core network data and the local data.
  • the release execution module is configured to respectively perform or instruct the mobility management unit to perform a corresponding release resource operation according to the difference of the determination result.
  • the mobility management unit of the present invention notifies the data cache unit of the type of the network link when establishing the network link; the data cache unit executes or instructs the mobility management unit to release the resource according to the type of the network link.
  • the data cache unit can know the type of the network link, the release of the reserved resources of the forwarding link can be effectively performed, and the resource utilization of the core network element is improved, that is, the core network element is improved.
  • the core network carries processing power.
  • Figure 1 is a schematic structural view 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 a wireless side network element accessing a core network
  • FIG. 4 is another schematic diagram of a wireless side network element accessing a core network
  • Figure 5 is a schematic diagram of data flow paths for local access and traditional core network access
  • FIG. 6 is a schematic diagram of a data transmission path in a case of a user state transition
  • Figure 7 is another schematic diagram of a data transmission path in the case of a user state transition
  • FIG. 8 is another schematic diagram of a data transmission path in the case of a user state transition
  • FIG. 9 is a schematic diagram of data link update from a idle state to a connected state
  • FIG. 10 is a schematic flow chart of the first embodiment of the present invention when the core network link of the LTE system attach process is established
  • Embodiment 11 is a schematic flowchart of Embodiment 2 of the present invention when a core network link is established in a PDN connection establishment process of an LTE system;
  • FIG. 12 is a schematic flowchart of Embodiment 3 of the present invention when a local access forwarding link is established in an LTE system S1 release process;
  • FIG. 13 is a schematic flowchart of Embodiment 4 of the present invention after the LTE system data buffer unit receives the downlink data of the core network;
  • LTE system data buffer unit receives the downlink data of the core network and updates the link;
  • FIG. 15 is a schematic flowchart of a sixth embodiment of the present invention in which a PDP context activation process of a GPRS system indicates a network link type;
  • FIG. 16 is a schematic flowchart of the seventh embodiment of the present invention after the GPRS system data buffer unit receives the downlink data of the core network. detailed description
  • the mobility management unit notifies the data cache unit of the type of the network link when establishing the network link; the data cache unit executes or instructs the mobility management unit to release the resource according to the type of the network link.
  • a data cache unit distinguishes a network link type, the method includes: the core network mobility management unit notifies a data cache unit of a type of a network link when establishing a network link; and the data cache unit performs or indicates a move according to a type of the network link The sex management unit releases resources.
  • the type of the network link is saved locally.
  • the data cache unit performs or indicates that the mobility management unit releases the resource according to the type of the network link, and specifically includes the following steps:
  • Step 531 When the data buffering unit receives the downlink data from the network link, determining, according to the type of the saved network link, the data type of the downlink data is core network data, or local access data, or includes core network data and local access. data.
  • Step 532 According to different judgment results, that is, the judgment result is core network data, or Locally accessing data, or including core network data and local access data, respectively performing or instructing the mobility management unit to perform corresponding operations of releasing resources.
  • step 532 The specific processing of step 532 is separately explained below.
  • the data buffer unit determines that the data type of the downlink data is the core network data.
  • the performing or instructing the mobility management unit to release the resource specifically includes: releasing, by the data buffer unit, the forwarding link resources of the local and core network mobility management units; or, the data buffering unit is capable of characterizing the downlink data type.
  • the information informs the mobility management unit that the forwarding link resources in the local and data buffer units are released by the mobility management unit.
  • the information indicating the downlink data type includes: at least one of a gateway address, a gateway identifier, and a newly defined downlink data type indication.
  • the data buffer unit determines that the data type of the downlink data is local access data.
  • the operation of instructing the mobility management unit to release the resource specifically includes: the data cache unit notifying the mobility management unit by using a normal downlink data notification message.
  • the core network mobility management unit starts the forwarding link timer according to the existing technology, and releases the forwarding link resource after the forwarding link timer expires.
  • the data buffer unit determines that the data type of the downlink data includes the core network data and the local access data.
  • the operation of releasing the resource specifically includes: the data buffer unit notifies the mobility management unit by using a normal downlink data notification message.
  • the core network mobility management unit starts the forwarding link timer according to the prior art, and releases the forwarding link resource after the forwarding link timer expires.
  • the types of network links mentioned above include: at least one of a core network link and a local access link.
  • the data cache unit involved above includes: a service gateway, a service GPRS support node.
  • the service GPRS support node is in the case of supporting the Gn interface.
  • the present invention mainly includes the following contents:
  • the core network mobility management unit for example, the MME, the SGSN supporting the S4 interface, and the SGSN supporting the Gn interface, notify the data cache unit of the type of the network link when establishing the network link, and the data cache unit saves the information.
  • the network link types include: a core network link, a local access link.
  • the data buffer unit when the data buffer unit receives the downlink data from a network link, it can determine whether the data type is core network data or local access data.
  • the data buffer unit determines that the data is core network data, there are two ways to release the resources, and the release of the release operation is different.
  • one way is: releasing, by the data buffer unit, the forwarding link resources of the local and core network mobility management units by deleting the bearer request message.
  • the deleting the bearer request message requires a cause value to indicate that the mobility management unit only releases the tunnel and does not release the bearer.
  • the data buffering unit informs the mobility management unit of the information capable of characterizing the downlink data type by using the downlink data notification message, and the session deletion request message is initiated by the mobility management unit, and the forwarding chain in the local and data buffering unit is The road resources are released.
  • the information indicating the downlink data type may include the following: a gateway address, a gateway identifier, and a newly defined downlink data type indication.
  • the data buffer unit determines that the data is local access data, the data buffer unit notifies the mobility management unit of the normal downlink data notification message.
  • the core network mobility management unit starts the forwarding link timer according to the prior art, and releases the forwarding link resource after the timer expires.
  • the data cache unit determines that the data has both core network data and local access data, then The data buffer unit notifies the mobility management unit of the normal downlink data notification message.
  • the core network mobility management unit starts the forwarding link timer according to the existing technology, and releases the forwarding link resource after the timer expires.
  • the mobility management unit is a serving GPRS support node supporting the Gn interface
  • the above network link type judgment, saving, and local access forwarding link resource release processing are all completed locally in the mobility management unit. , is an internal operation.
  • the local access function includes: locally accessing the home network through the home base station, locally accessing the enterprise network through the home base station, accessing the Internet or other specific IP network through the home base station or the macro cell.
  • the data cache unit includes: a service gateway and a service GPRS support node.
  • the service GPRS support node is in the case of supporting the Gn interface.
  • the invention is illustrated by way of example below.
  • FIG. 10 is an implementation manner of the present invention when the core network link of the LTE system attach process is established, and specifically includes the following steps:
  • Step 601 When the user starts to register in the network, the user initiates an attach request, where the user carries the APN or the willingness indication to request the network link.
  • Step 602 The radio side network element forwards the attach request message, and brings the capability of the radio side network element to support local access to the mobility management unit by using the underlying initialization non-access stratum message.
  • the wireless side network element includes: a home base station, a macro base station, and a home base station gateway.
  • the mobility management unit can be a mobility management entity or a service GPRS support node that supports the S4 interface.
  • Step 603 The mobility management unit authenticates and authenticates the user according to the user security information in the attach request message to ensure that the authorized user accesses the network.
  • Step 604 If there is no subscription data of the user in the mobility management unit, request the home subscriber data server to perform the delivery of the user subscription information by updating the location request message.
  • Step 605 The number of subscriptions of the user by the home subscriber data server by updating the location confirmation message It is issued to the mobility management unit.
  • Step 606 The mobility management unit determines, according to the access point name (APN, access point name) or the willingness requested by the user, the type of the network link established by the user in combination with the subscription data of the user, and selects a suitable gateway.
  • APN access point name
  • API access point name
  • the mobility management unit selects the local gateway for the user to complete the user local access function. If the user requests a core network link or the network decides to establish a core network link for the user, the mobility management unit selects the core network gateway for the user to complete the function of the user accessing the Internet through the core network.
  • This example describes the case where the user requests the core network link or the network to establish a core network link for the user. The process of establishing a local access link is similar, and the difference is briefly described in the implementation steps.
  • Step 607 If the established link is a core network link, the mobility management unit selects a suitable service gateway according to the core network gateway and performs a network link establishment process by creating a session request message.
  • the network link type information determined in step 606 is carried.
  • the mobility management unit may directly send a create session request message to the local gateway by using the existing direct tunnel mode, no longer select the service gateway and establish a local access link through the service gateway.
  • the mobility management unit saves the network link type, and then notifies the network link type when the user subsequently transfers to the idle state to establish the local access forwarding channel, as shown in the embodiment described in Example 3 of FIG.
  • the mobility management unit can also perform the service gateway selection and establish a local access connection through the service gateway.
  • the core network mobility management unit directly notifies the service gateway of the network link type.
  • Step 608 The service gateway establishes a context corresponding to the network link in the core network gateway by creating a session request message, and reports the service gateway address and the tunnel identifier to the core network gateway for downlink data transmission.
  • Step 609 The gateway replies to the service gateway to create a session response message. Put the gateway as uplink data The assigned uplink tunnel identity is transmitted to the serving gateway.
  • Step 610 The service gateway replies to the mobility management unit with a create session response message.
  • the upstream tunnel identifier assigned by the serving gateway for the uplink data transmission is brought to the mobility management unit.
  • the process of performing the subsequent attaching process includes the establishment of the radio bearer and the opening of the uplink and downlink tunnels, which are the same as the prior art, and are not described herein.
  • FIG. 11 is an implementation manner of the present invention when the core network link is established in the PDN connection establishment process of the LTE system, and specifically includes the following steps:
  • Step 701 The user needs to initiate a PDN connection request when accessing the new Internet content, where the APN or the willingness indication that the user wants to request the network link is carried.
  • Step 702 The radio side network element forwards the PDN connection request message, and brings the capability of the radio side network element to support local access to the mobility management unit by using the underlying direct transmission message.
  • the wireless side network element includes: 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 an S4 interface.
  • Step 703 The mobility management unit determines, according to the APN or the willingness requested by the user, the type of the network link established by the user in combination with the user subscription data downloaded by the attaching process, and selects a suitable gateway.
  • the mobility management unit selects the local gateway for the user to complete the user local access function. If the user requests a core network link or the network decides to establish a core network link for the user, the mobility management unit selects the core network gateway for the user to complete the function of the user accessing the Internet through the core network.
  • This example describes the case where the user requests the core network link or the network to establish a core network link for the user. The process of establishing a local access link is similar, and the difference is briefly described in the implementation steps.
  • Step 704 If the established link is a core network link, the mobility management unit selects a suitable service gateway according to the core network gateway and establishes a network link by creating a session request message. Process. The network link type information determined in step 703 is carried.
  • the mobility management unit may directly send a create session request message to the local gateway by using the existing direct tunnel mode, no longer select the service gateway and establish a local access link through the service gateway.
  • the mobility management unit saves the network link type, and then notifies the network link type when the user subsequently transfers to the idle state to establish the local access forwarding channel, as shown in the embodiment described in Example 3 of FIG.
  • the mobility management unit can also perform the service gateway selection and establish a local access connection through the service gateway.
  • the core network mobility management unit directly notifies the service gateway of the network link type.
  • Step 705 The service gateway establishes a context corresponding to the network link in the core network gateway by creating a session request message, and reports the service gateway address and the tunnel identifier to the core network gateway for downlink data transmission.
  • Step 706 The core network gateway replies to the service gateway to create a session response message.
  • the core network gateway is brought to the serving gateway by the uplink tunnel identifier allocated for the uplink data transmission.
  • Step 707 The service gateway replies to the mobility management unit with a create session response message.
  • the upstream tunnel identifier assigned by the serving gateway for the uplink data transmission is brought to the mobility management unit.
  • the process of establishing the subsequent PDN connection includes the establishment of the radio bearer and the process of the uplink and downlink tunnels, which are the same as the prior art, and are not mentioned.
  • FIG. 12 is an implementation manner of the present invention when the local access forwarding link is established in the S1 release process of the LTE system, and specifically includes the following steps:
  • Step 801 If the radio side network element decides to release the signaling connection of the user due to the O&M interoperation, the user deactivation, the repeated integrity check failure, and the like, the S1 user context release request message is sent to the mobility management unit. After the mobility management unit completes the signaling and data transmission process, in order to save network resources, the user's signaling connection release is initiated, and the user is switched from the connected state to the idle state. Step 801 is not needed at this time.
  • Step 802 The mobility management unit determines whether the user currently has an activated local access chain. If no, the normal Sl-U interface bearer release process is performed, which is not described in the prior art. If there is one, create a forwarding channel for the local access link.
  • Step 803 If the current user has an activated local access link, the mobility management unit notifies the service gateway of the network link type by creating a session request.
  • Step 804 The serving gateway notifies the local gateway of the address of the serving gateway and the tunnel identification information of the downlink cache channel by modifying the bearer request message. Since the local gateway already has context information of the local access link at this time, only the serving gateway needs to perform tunnel update. After the local gateway tunnel is updated, the local access downlink data can be cached.
  • Step 805 The local gateway returns a response message to the monthly service gateway.
  • Step 806 The service gateway replies to the mobility management unit with a create session response message.
  • Step 807 the subsequent S1 link release process is continued, the air interface resource is released, and the user transits from the connection state to the idle state.
  • FIG. 13 is a first implementation manner of the link update after the LTE system data buffer unit receives the downlink data of the core network, and includes the following steps:
  • Step 901 The core network gateway sends the received user downlink data to the service gateway as a cache unit.
  • Step 902 The serving gateway determines the source of the downlink data according to the network link used in the downlink data transmission and the saved network link type.
  • Step 903 The serving gateway sends information indicating the downlink data type to the mobility management unit in the downlink data notification message, where the information indicating the downlink data type may include the following content: a gateway address, a gateway identifier, and a newly defined downlink data type indication. .
  • Step 904 The mobility management unit initiates paging in an area registered by the user.
  • Step 905 After receiving the paging message, the user initiates a service request and responds.
  • Step 906 The mobility management unit instructs the wireless side to establish an air interface bearer by using an initial context setup request message, where the message carries the uplink tunnel identifier and address information of the local access direct tunnel and Host QoS information.
  • Step 907 The radio side network element establishes an air interface bearer according to the bearer Qos information.
  • the wireless side network element includes: a home base station, a macro base station, and a home base station gateway.
  • Step 908 The radio side network element brings the assigned downlink tunnel identifier and address information to the mobility management unit by using an initial context setup complete message.
  • Step 909 the user enters the connection state, and the mobility management unit directly transmits the downlink tunnel identifier and the address information allocated by the radio side network element to the local gateway or forwards through the service gateway by modifying the bearer request message, and clears the downlink transmission of the data of the local access link. aisle.
  • Step 910 The local gateway replies to the mobility management unit to modify the bearer response message, or forwards the message through the serving gateway.
  • step 911 the wireless side network element learns that the uplink tunnel identifier of the direct tunnel is locally accessed through step 906.
  • the local gateway obtains the downlink tunnel identifier of the direct tunnel through the local access in step 909, and the local access uplink and downlink data can be normally transmitted.
  • 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 by deleting the session request.
  • Step 913 The service gateway finds that the network link is used for local access, deletes the corresponding context, and replies to the delete session response message.
  • step 912 and step 913 may be initiated to perform the deletion of the local access forwarding network link, and thus the sequence of the subsequent steps is not limited.
  • FIG. 14 is a second implementation manner of the link update after the data buffer unit of the LTE system receives the downlink data of the core network, and includes the following steps:
  • Step 1001 The core network gateway sends the received user downlink data to a serving gateway as a cache unit.
  • Step 1003 The serving gateway sends a downlink data notification message to the mobility management unit to trigger a paging process.
  • Step 1004 The mobility management unit initiates paging in an area registered by the user.
  • Step 1005 After receiving the paging message, the user initiates a service request and responds.
  • Step 1006 The mobility management unit instructs the radio side to establish an air interface bearer by using an initial context setup 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 radio side network element establishes an air interface bearer according to the bearer Qos information.
  • the wireless side network element includes: a home base station, a macro base station, and a home base station gateway.
  • Step 1008 The radio side network element brings the allocated downlink tunnel identifier and address information to the mobility management unit by using an initial context setup complete message.
  • Step 1009 The user enters a connection state, and the mobility management unit directly sends the downlink tunnel identifier and the address information allocated by the radio side network element to the local gateway or forwards through the service gateway by modifying the bearer request message, and clears the downlink transmission of the data of the local access link. aisle.
  • Step 1010 The local gateway directly replies to the mobility management unit to modify the bearer response message, or forwards the message through the serving gateway.
  • Step 1011 The radio side network element learns to access the uplink tunnel identifier of the direct tunnel through the step 1006.
  • the local gateway obtains the downlink tunnel identifier of the local access direct tunnel through the step 1009, and the local access uplink and downlink data can be normally transmitted.
  • Step 1012 The downlink information is originated from the core network, and the serving gateway initiates local deletion of the downlink forwarding network link.
  • the serving gateway deletes the user plane tunnel corresponding to the forwarding network link by using the deletion bearer request carrying the special cause value.
  • the special cause value is used to indicate that the mobility management unit only deletes the tunnel information, and retains the control plane information of the bearer for local access. Used when the tunnel is established.
  • Step 1013 The mobility management unit deletes the bearer information corresponding to the network link and returns the bearer response message.
  • step 1012 and step 1013 may be initiated to perform the deletion of the local access forwarding network link, and thus the sequence of subsequent steps is not limited.
  • the mobility management unit of the method in this example cannot know the downlink data source. Therefore, if the establishment of the radio bearer is completed before receiving step 1012, it will still initiate an update of the forwarding network link, and the service gateway receives the update. The message ignores no response.
  • Example 6 is a GPRS system packet data protocol (PDP) context activation process.
  • the core network indicates the implementation of the network link type, which specifically includes the following steps:
  • Step 1101 When the user needs to access the new Internet content, initiate an Activate PDP Context Request message, where the APN or the willingness indication that the user wants to request the network link is carried.
  • Step 1102 The radio side network element forwards the activated PDP context request message, and brings the capability of the radio side network element to support local access to the serving GPRS support node by using the underlying direct transmission message.
  • Step 1103 The serving GPRS support node determines the type of the network link established by the user according to the APN or the willingness of the user to indicate the user subscription data downloaded by the attaching process, and selects a suitable gateway.
  • the serving GPRS support node serves as a cache point for the downlink data of the 3G system
  • the type of the established network link is locally saved after the judgment. 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 the local gateway for the user to complete the user local access function. If the user requests a core network link or the network decides to establish a core network link for the user, the mobility management unit selects the core network gateway for the user to complete the function of the user accessing the Internet through the core network. This example describes the case where the user requests the core network link or the network decides to establish a core network link for the user.
  • Step 1104 If the established link is a core network link, the serving GPRS support node performs a network link establishment process by creating a PDP context request message. Similarly, if the created link is a local access link, the serving GPRS support node directly sends a Create PDP Context Request message to the local gateway.
  • Step 1105 The gateway, including the core network gateway and the locally visited gateway, replies to create a PDP context response and bring the allocated uplink tunnel identity and address information to the serving GPRS support node.
  • Step 1106 The serving GPRS support node instructs the radio side network element to establish an air interface bearer, where the radio side network element may be: a home base station, a macro base station, and a home base station gateway.
  • the serving GPRS support node determines that the uplink tunnel identity and address information assigned by the local gateway is brought to the wireless side network element by using the direct tunnel mode. If the established network link is a core network link, the serving GPRS support node brings its assigned uplink tunnel identity and address information to the wireless side network element.
  • the radio side network element brings its assigned downlink tunnel identifier and address information to the serving GPRS support node.
  • step 1107 when the core network link is established, if QoS negotiation is required, the step is executed to bring the Qos information requested by the wireless side to the core network gateway, otherwise the step may be omitted. If a local access link is established, this step establishes a direct tunnel for local access, and brings the downlink tunnel identifier and address information allocated by the radio side network element to the local gateway to open the downlink channel.
  • Step 1108 The core network gateway replies with an update PDP context response message.
  • Step 1109 the serving GPRS support node replies to the Activate PDP Context Accept message.
  • FIG. 16 is an implementation manner of link update after the data buffer unit of the GPRS system receives the downlink data of the core network, and specifically includes the following steps:
  • Step 1201 The core network gateway sends the received user downlink data to a serving GPRS support node that is a cache unit.
  • Step 1202 The serving GPRS support node determines the source of the downlink data according to the network link used in the downlink data transmission and the saved network link type. If it is known that the downlink data is the core network data, the user plane information of the local access forwarding link is released, which is the internal operation of the serving GPRS supporting node, and the specific manner is not described.
  • Step 1203 The serving GPRS support node initiates paging in an area registered by the user.
  • Step 1204 After receiving the paging message, the user initiates a service request and responds.
  • Step 1205 The serving GPRS support node instructs the wireless side to establish an air interface bearer by using a radio bearer assignment 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 1206 The radio side network element establishes an air interface bearer according to the bearer Qos information.
  • the wireless side network element includes: a home base station, a macro base station, and a home base station gateway.
  • Step 1207 The radio side network element carries the allocated downlink tunnel identifier and address information to the serving GPRS support node by using a radio bearer assignment response message.
  • Step 1208 The user enters the connection state, and the serving GPRS support node brings the downlink tunnel identifier and the address information allocated by the radio side network element to the local gateway by updating the PDP context request message, and opens the data downlink transmission channel of the local access link.
  • Step 1209 The local gateway replies to the serving GPRS support node to modify the bearer response message.
  • the radio side network element learns to access the uplink tunnel identifier of the direct tunnel through the step 1202.
  • the local gateway obtains the downlink tunnel identifier of the local access direct tunnel through the step 1208, and the local access uplink and downlink data can be normally transmitted through the direct tunnel.
  • the data buffer unit determines that the data is To access the data, the data buffer unit notifies the mobility timer to release the forwarding link resource after a timeout through the normal downlink data notification message.
  • the data buffer unit determines that the data has both core network data and local access data, the data buffer unit notifies the mobility management unit of the normal downlink data notification message.
  • the core network mobility management unit starts the forwarding link timer according to the existing technology, and releases the forwarding link resource after the timer expires.
  • a system for distinguishing a network link type by a data cache unit comprising: a notification module on the mobility management unit side, and a release module on the data cache unit side.
  • the notification module is configured to notify the release module of the data cache unit side of the type of the network link when the network management link is established.
  • a release module configured to perform or instruct the mobility management unit to release resources according to a type of the network link.
  • the system further includes: a saving module on the data buffer unit side, configured to save the type of the network link locally after the data cache unit learns the type of the network link.
  • the release module further includes: an acquisition module, a determination module, and a release execution module.
  • the obtaining module is configured to obtain a type of the network link saved by the saving module when receiving the downlink data from the network link.
  • the determining module is configured to determine, according to the type of the network link, that the data type of the downlink data is core network data, or local access data, or includes core network data and local access data.
  • releasing an execution module configured to separately perform or instruct the mobility management unit to perform a corresponding operation of releasing resources according to the difference of the determination result.
  • the home subscriber server is represented by Home Subscriber Server, abbreviated as HSS; the mobility management entity is represented by Mobility Management Entity, abbreviated as MME; the service GPRS support node is represented by Serving GPRS Support Node, abbreviated as SGSN;
  • the function is represented by Policy and Charging Rule Function, abbreviated as PCRF;
  • the service gateway is represented by Serving Gateway, abbreviated as S-GW, which is the Serving GW in FIG. 1;
  • the packet data gateway is represented by PDN Gateway, abbreviated as P-GW. That is, the PDN GW in FIG. 1; the packet data network is represented by Packet Data Network, abbreviated as PDN; the RNC in FIG.
  • the E-NodeB in FIG. 1 is an evolved base station, and may also be represented by an eNB;
  • the CN in FIG. 5 is the core network;
  • the gateway GPRS support node is represented by the Gateway GPRS Support Node, abbreviated as GGSN;
  • the home base station is represented by Home NodeB, abbreviated as HNB;
  • the evolved home base station is represented by Home eNodeB, abbreviated as HeNB; local access
  • the function is represented by Local IP Access or Selected IP Traffic Offload, abbreviated as LIPA or SIPTO.

Landscapes

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

Description

一种数据緩存单元区分网络链接类型的方法及系统 技术领域
本发明涉及移动通信技术领域， 尤其涉及一种本地访问功能使用情况 下数据緩存单元区分网络链接类型的方法及系统。 背景技术
为了保持第三代移动通信系统在通信领域的竟争力， 为用户提供速率 更快、 时延更低、 更加个性化的移动通信服务， 同时， 降低运营商的运营 成本， 第三代合作伙伴计划 （3GPP, 3rd Generation Partnership Project )标 准工作组正致力于演进分组系统（ EPS , Evolved Packet System ) 的研究。 如图 1所示为 EPS系统的结构示意图， 图 1中， 整个 EPS系统分为无线接 入网和核心网两部分， 图 1 中涉及英文的中文请见文字最后的统一解释。 在核心网中， 包含了归属用户服务器、 移动性管理实体、 服务通用分组无 线业务（GPRS )支持节点、 策略计费规则功能实体、 服务网关、 分组数据 网关和分组数据网络。 下面详细各部分功能：
归属用户服务器， 是用户签约数据的永久存放地点， 位于用户签约的 归属网。
移动性管理实体， 是用户签约数据在当前网络的存放地点， 负责终端 到网络的非接入层信令管理、 终端的安全验证功能、 终端的移动性管理、 用户空闲模式下的跟踪和寻呼管理功能和承载管理。
服务 GPRS支持节点 ,是 GERAN和 UTRAN用户接入核心网络的业务 支持点， 功能上与移动性管理实体类似， 负责用户的位置更新、 寻呼管理 和承载管理等功能。其中， GERAN是 GSM/EDGE的无线接入部分，以 GSM EDGE Radio Access Network 表示； UTRAN 是全球陆上无线接入， 以 Universal Terrestrial Radio Access表示。
服务网关， 是核心网到无线系统的网关， 负责终端到核心网的用户面 承载、 终端空闲模式下的数据緩存、 网络侧发起业务请求的功能、 合法监 听和分组数据路由和转发功能； 服务网关负责统计用户终端使用无线网的 情况， 并产生终端使用无线网的话单， 传送给计费网关。
分组数据网关， 是演进系统和该系统外部分组数据网络的网关， 它连 接到因特网和分组数据网络上， 负责终端的 IP地址分配、 计费功能、 分组 包过滤、 策略控制等功能。
分组数据网络， 是运营商的 IP业务网络， 该网络通过运营商的核心网 为用户提供 IP服务。
策略计费规则功能实体， 是演进系统中负责提供计费控制、 在线信用 控制、 门限控制、 服务质量（QoS, Quality of Service ) 策略方面规则的服 务器。
无线接入网， 是由演进基站（eNB, E-UTRAN NodeB )和 3G无线网 络控制器（ RNC , Radio Network Control )组成， 它主要负责无线信号的收 发， 通过空中接口和终端联系， 管理空中接口的无线资源、 资源调度、 接 入控制。
上述服务 GPRS支持节点是升级过的服务 GPRS支持节点， 能够支持 与服务网关之间的 S4接口， 并与移动性管理实体之间釆用 GTPv2协议进 行互通。 而对于支持 3G核心网的服务 GPRS支持节点来说， 数据域（ PS ) 域网络架构与图 1有所不同， 此时， 服务 GPRS支持节点与移动性管理实 体之间釆用 Gn接口相连， 互通釆用 GTPvl协议。 服务 GPRS支持节不能 与服务网关相连，通过 Gn接口连接到网关 GPRS支持节点直接进行分组数 据网络访问。
家庭基站或者演进的家庭基站是一类小型、 低功率的基站， 作为某些 用户的专属资源， 部署在家庭、 团体、 公司或者学校等私人场所使用， 主 要是为了给用户提供更高的业务速率并降低使用高速率服务所需要的费 用， 同时弥补已有分布式蜂窝无线通信系统覆盖的不足。 家庭基站的优点 是实惠、 便捷、 低功率输出、 即插即用、 宽带接入、 使用单模终端等。
家庭基站可以直接连接到核心网， 如图 2所示， 这里， 图 2中的无线 侧网元可以为家庭基站； 家庭基站也可以通过家庭基站网关这个逻辑网元 接入到核心网， 如图 3、 4所示， 这里， 图 3、 4中的无线侧网元可以为家 庭基站。 其中， 家庭基站网关主要功能为： 验证家庭基站的安全性， 处理 家庭基站的注册， 对家庭基站进行运行维护管理， 根据运营商要求配置和 控制家庭基站， 负责交换核心网和家庭基站的数据。
为了实现本地访问功能， 即终端对家庭网络其他 IP设备、 企业网络中 的 IP设备或者互联网络的本地接入， 增设了本地网关， 如图 2、 3、 4所示。 本地网关的增设可提供对本地访问技术的有力支持， 本地网关可以和无线 侧网元合设、 或者在无线侧网元附近（即外置）， 也可以和家用基站网关合 设、 或者在家用基站网关附近（即外置）。 本地网关可以是 L-SGW (本地 SGW, Local SGW )、 本地 L-PGW (本地 PGW, Local PGW )、 L-GGSN (本 地 GGSN, Local GGSN )、 外置 L-GW ( Local GW )等。
图 5显示了在移动通信网络架构中， 本地访问和传统核心网访问的数 据流路径。 对于支持本地访问的用户， 可以建立传统的核心网访问数据路 径和本地访问数据路径。 如图 5 所示， 对于本地访问的连接， 本地访问数 据路径从终端至无线侧网元至本地网关 （L-SGW, L-PGW, L-GGSN ), 数 据传输不经过核心网。 为了实现终端对家庭网络其他 IP设备或者互联网络 的本地访问， 可以建立两条连接， 第一条本地访问数据路径直接访问互联 网， 即互联网本地访问连接。 第二条本地访问数据路径直接访问家庭网络 其他 IP设备， 即家庭网络本地访问连接。 图 5 所示为用户建立本地访问连接后， 连接状态下本地访问数据的传 输路径。 当用户长时间没有本地访问数据接收或者发送时， 无线侧网元会 释放空口连接使用户进入空闲状态。 此时如果再有用户的本地访问下行数 据到来， 则本地网关将数据发送至核心网的服务网关进行緩存， 在将用户 寻呼至连接状态时将緩存的数据下发， 通过这种方式能够保证本地访问下 行数据不丟失， 为用户提供良好的业务感知。 具体用户状态转移情况下数 据传送路径如图 6、 7、 8各个场景的示意图所示。 其中， 图 6所示为用户 处于连接状态时的数据路径示意图； 图 7所示为用户处于空闲状态时的下 行数据緩存示意图； 图 8所示为用户寻呼至连接状态时的数据路径示意图。 图 6所示的场景进入空闲状态后即为图 7所示的场景； 图 7所示的场景进 入连接状态后即为图 8所示的场景。
对于图 8所示的数据路径示意图， 具体的数据路径更新过程如图 9所 示， 该数据路径的更新过程包括以下步骤：
步骤 501 , 由于用户处于空闲状态时， 核心网移动性管理实体将本地访 问的下行隧道转移至核心网侧， 则当本地网关收到下行数据时就将数据发 送到核心网服务网关进行緩存。
步骤 502 ,服务网关收到下行数据后通过下行数据通知消息告知核心网 移动性管理实体。
步骤 503 ,核心网移动性管理实体在用户注册区覆盖范围内的无线侧网 元中触发寻呼。
步骤 504, 用户收到寻呼消息通过发起业务请求消息响应寻呼。
步骤 505 ,核心网移动性管理实体为用户建立空口承载， 在初始上下文 建立请求消息中， 将所有已建链接的上行隧道标识、 安全上下文、 无线承 载 Qos参数等发送给无线侧网元。
步骤 506,无线侧网元根据核心网的指示信息建立与终端用户之间的无 线承载。
步骤 507 , 无线侧网元在空口承载建立完成之后， 通过初始上下文建立 完成消息， 将下行隧道标识和地址信息告知核心网移动性管理实体。
步骤 508 ,核心网移动性管理实体通过修改承载请求消息， 将下行隧道 标识和地址信息带给本地网关。
步骤 509 , 本地网关回复爹改 载响应消息。
步骤 510,无线侧网元通过步骤 505得知本地访问直接隧道的上行隧道 标识， 本地网关通过步骤 508得到本地访问直接隧道的下行隧道标识则本 地访问上下行数据可以正常传输。
步骤 511 , 核心网移动性管理实体通过修改承载请求消息， 将下行隧道 标识和地址信息带给服务网关。
步骤 512 , 服务网关回复修改承载响应消息。
步骤 513 ,服务网关接收到下行隧道标识和地址信息后将緩存的下行数 据发送至用户， 用户的本地访问上行数据通过步骤 510发送， 不再经过服 务网关。
补充说明： 其中步骤 508和步骤 509可选通过服务网关进行转发。 现有实现过程中， 当服务网关收到从核心网网关发来的下行数据时也 会执行本过程所述步骤， 即便没有本地访问数据核心网移动性管理单元也 会把本地访问的转发和直接数据通道建立起来， 当后续有本地访问数据时 可以直接应用。 在下行本地访问緩存数据发送完毕之后数据转发链路会由 核心网移动性管理单元发起释放， 具体删除时间可以通过设置定时器来保 证。 但是这种实现方式并不优化， 因为即便下行数据仅为核心网数据时， 核心网移动性管理单元仍然需要建立本地访问数据的转发链路， 并在无本 地访问緩存数据的情况下阶段性预留数据链路资源， 也就是说， 不能及时 释放预留资源， 这会导致核心网网元的资源利用率降低的问题， 目前对于 这个问题尚没有有效的解决方案。 发明内容
有鉴于此， 本发明的主要目的在于提供一种数据緩存单元区分网络链 接类型的方法及系统， 能有效地进行转发链路预留资源的释放， 提高核心 网网元的资源利用率。
为达到上述目的， 本发明的技术方案是这样实现的：
一种数据緩存单元区分网络链接类型的方法， 该方法包括： 移动性管 理单元在建立网络链接时， 将所述网络链接的类型通知数据緩存单元； 所 述数据緩存单元根据所述网络链接的类型执行或者指示移动性管理单元释 放资源。
其中， 所述数据緩存单元获知所述网络链接的类型后， 在本地保存所 述网络链接的类型。
其中， 所述数据緩存单元根据所述网络链接的类型执行或者指示移动 性管理单元释放资源包括：
当所述数据緩存单元从网络链接上接收到下行数据时， 根据保存的所 述网络链接的类型， 判断出所述下行数据的数据类型为核心网数据、 或本 地数据、 或者包括核心网数据和本地数据； 根据判断结果的不同， 分别执 行或者指示移动性管理单元进行相对应的释放资源的操作。
其中， 当所述数据緩存单元判断出所述下行数据的数据类型为核心网 数据时， 执行或者指示移动性管理单元释放资源的操作包括：
由数据緩存单元将本地和核心网移动性管理单元的转发链路资源进行 释放； 或者，
数据緩存单元将能够表征下行数据类型的信息告知移动性管理单元， 由移动性管理单元将本地和数据緩存单元中的转发链路资源进行释放。
其中， 所述表征下行数据类型的信息包括： 网关地址、 网关标识、 新 定义的下行数据类型指示中至少一种。
其中， 当所述数据緩存单元判断出所述下行数据的数据类型为本地数 据时， 指示移动性管理单元执行释放资源的操作包括：
数据緩存单元通过正常的下行数据通知消息告知移动性管理单元； 由移动性管理单元开启转发链路定时器， 在转发链路定时器超时后释 放转发链路资源； 或者，
当所述数据緩存单元判断出所述下行数据的数据类型为包括核心网数 据和本地数据时， 指示移动性管理单元执行的释放资源的操作包括：
数据緩存单元通过正常的下行数据通知消息告知移动性管理单元； 由移动性管理单元开启转发链路定时器， 在转发链路定时器超时后释 放转发链路资源。
其中， 所述网络链接类型包括： 核心网链接、 本地链接中至少一种。 一种数据緩存单元区分网络链接类型的系统， 该系统包括： 移动性管 理单元侧的通知模块、 和数据緩存单元侧的释放模块； 其中，
通知模块， 用于移动性管理单元在建立网络链接时， 将所述网络链接 的类型通知数据緩存单元侧的释放模块；
释放模块， 用于根据所述网络链接的类型执行或者指示移动性管理单 元释放资源。
其中， 该系统还包括： 数据緩存单元侧的保存模块， 用于数据緩存单 元获知所述网络链接的类型后， 在本地保存所述网络链接的类型。
其中， 所述释放模块， 进一步包括： 获取模块、 判断模块和释放执行 模块； 其中，
获取模块， 用于当从网络链接上接收到下行数据时， 获取保存模块所 保存的所述网络链接的类型；
判断模块， 用于根据所述网络链接的类型判断出所述下行数据的数据 类型为核心网数据、 或本地数据、 或者包括核心网数据和本地数据； 释放执行模块， 用于根据判断结果的不同， 分别执行或者指示移动性 管理单元进行相对应的释放资源的操作。
本发明的移动性管理单元在建立网络链接时， 将网络链接的类型通知 数据緩存单元； 数据緩存单元根据网络链接的类型执行或者指示移动性管 理单元释放资源。
釆用本发明， 由于数据緩存单元能获知网络链接的类型， 因此， 能有 效地进行转发链路预留资源的释放， 提高核心网网元的资源利用率， 也就 是说， 提高核心网网元的核心网承载处理能力。 附图说明
图 1为 EPS系统的结构示意图；
图 2为无线侧网元接入核心网的一示意图；
图 3为无线侧网元接入核心网的另一示意图；
图 4为无线侧网元接入核心网的又一示意图；
图 5为本地访问和传统核心网访问的数据流路径示意图；
图 6为用户状态转移情况下数据传送路径的一示意图；
图 7为用户状态转移情况下数据传送路径的另一示意图；
图 8为用户状态转移情况下数据传送路径的又一示意图；
图 9为用户从空闲状态转为连接状态的数据链路更新示意图； 图 10为 LTE系统附着过程核心网链接建立时本发明实例一的流程示意 图；
图 11为 LTE系统 PDN连接建立过程核心网链接建立时本发明实例二 的流程示意图；
图 12为 LTE系统 S1释放过程本地访问转发链接建立时本发明实例三 的流程示意图； 图 13为 LTE系统数据緩存单元收到核心网下行数据后链路更新的本发 明实例四的流程示意图；
图 14为 LTE系统数据緩存单元收到核心网下行数据后链路更新的本发 明实例五的流程示意图；
图 15为 GPRS系统 PDP上下文激活过程指示网络链接类型的本发明实 例六的流程示意图；
图 16为 GPRS系统数据緩存单元收到核心网下行数据后链路更新的本 发明实例七的流程示意图。 具体实施方式
本发明的基本思想是： 移动性管理单元在建立网络链接时， 将网络链 接的类型通知数据緩存单元； 数据緩存单元根据网络链接的类型执行或者 指示移动性管理单元释放资源。
下面结合附图对技术方案的实施作进一步的详细描述。
一种数据緩存单元区分网络链接类型的方法， 该方法包括： 核心网移 动性管理单元在建立网络链接时， 将网络链接的类型通知数据緩存单元； 数据緩存单元根据网络链接的类型执行或者指示移动性管理单元释放资 源。
这里， 数据緩存单元获知网络链接的类型后， 在本地保存网络链接的 类型。
这里， 数据緩存单元根据网络链接的类型执行或者指示移动性管理单 元释放资源具体包括以下步骤：
步骤 531、 当数据緩存单元从网络链接上接收到下行数据时，根据保存 的网络链接的类型， 判断出下行数据的数据类型为核心网数据、 或本地访 问数据、 或者包括核心网数据和本地访问数据。
步骤 532、 分别根据判断结果的不同， 即： 判断结果为核心网数据、 或 本地访问数据、 或者包括核心网数据和本地访问数据， 分别执行或者指示 移动性管理单元进行相对应的释放资源的操作。
以下对步骤 532的具体处理过程分别阐述。
第一种情况： 数据緩存单元判断出下行数据的数据类型为核心网数据 的情况。
此时， 执行或者指示移动性管理单元释放资源的操作具体包括： 由数 据緩存单元将本地和核心网移动性管理单元的转发链路资源进行释放； 或 者， 数据緩存单元将能够表征下行数据类型的信息告知移动性管理单元， 由移动性管理单元将本地和数据緩存单元中的转发链路资源进行释放。
其中， 表征下行数据类型的信息包括： 网关地址、 网关标识、 新定义 的下行数据类型指示中至少一种。
第二种情况： 数据緩存单元判断出下行数据的数据类型为本地访问数 据的情况。
此时， 指示移动性管理单元释放资源的操作具体包括： 数据緩存单元 通过正常的下行数据通知消息告知移动性管理单元。 核心网移动性管理单 元按照现有技术开启转发链路定时器， 在转发链路定时器超时后释放转发 链路资源。
第三种情况： 数据緩存单元判断出下行数据的数据类型为包括核心网 数据和本地访问数据的情况。
此时， 释放资源的操作具体包括： 数据緩存单元通过正常的下行数据 通知消息告知移动性管理单元。 核心网移动性管理单元按照现有技术开启 转发链路定时器， 在转发链路定时器超时后释放转发链路资源。
需要指出的是： 釆用本发明， 实现第二、 第三种情况是对现有技术的 一种兼容性处理， 本发明除了及时有效地释放资源外， 对现有技术还存在 兼容作用。 以上涉及到的网络链接类型包括： 核心网链接、 本地访问链接中至少 一种。
以上涉及到的数据緩存单元包括： 服务网关、 服务 GPRS 支持节点。 其中， 服务 GPRS支持节点为支持 Gn接口的情况。
综上所述， 本发明主要包括以下内容：
核心网移动性管理单元， 比如： MME、 支持 S4接口的 SGSN、 支持 Gn接口的 SGSN, 在建立网络链接时告知数据緩存单元该网络链接的类 型， 数据緩存单元保存该信息。 具体地， 网络链接类型包括： 核心网链接、 本地访问链接。
进一步地， 当数据緩存单元从某条网络链接收到下行数据时即可判断 出数据类型是核心网数据还是本地访问数据。
如果数据緩存单元判断数据是核心网数据， 那么释放资源的方式有两 种， 执行释放操作的释放者有所不同。
具体来说， 一种方式是： 由数据緩存单元通过删除承载请求消息， 将 本地和核心网移动性管理单元的转发链路资源进行释放。 其中， 删除承载 请求消息需要原因值用来指示移动性管理单元仅释放隧道不释放承载。
另一种方式是： 数据緩存单元通过下行数据通知消息， 将能够表征下 行数据类型的信息告知移动性管理单元， 由移动性管理单元发起会话删除 请求消息， 将本地和数据緩存单元中的转发链路资源进行释放。 其中， 表 征下行数据类型的信息可以包括以下内容： 网关地址、 网关标识、 新定义 的下行数据类型指示。
如果数据緩存单元判断数据是本地访问数据， 那么数据緩存单元通过 正常的下行数据通知消息告知移动性管理单元。 核心网移动性管理单元按 照现有技术开启转发链路定时器， 在定时器超时后释放转发链路资源。
如果数据緩存单元判断数据既有核心网数据也有本地访问数据， 那么 数据緩存单元通过正常的下行数据通知消息告知移动性管理单元。 核心网 移动性管理单元按照现有技术开启转发链路定时器， 在定时器超时后释放 转发链路资源。
这里需要指出的是： 对于移动性管理单元是支持 Gn接口的服务 GPRS 支持节点的情况， 那么上述网络链接类型的判断、 保存及本地访问转发链 路资源的释放处理均在移动性管理单元本地完成， 属于内部操作。
其中， 本地访问功能包括： 通过家庭基站本地访问家庭网络、 通过家 庭基站本地访问企业网络、 通过家庭基站或者宏蜂窝访问互联网或者其它 特定 IP网络。
其中， 数据緩存单元包括： 服务网关、 服务 GPRS 支持节点。 其中， 服务 GPRS支持节点为支持 Gn接口的情况。
以下对本发明进行举例阐述。
实例一：图 10为 LTE系统附着过程核心网链接建立时本发明的实施方 式， 具体包括以下步骤：
步骤 601 , 用户开机注册到网络中时发起附着请求， 其中携带用户所要 请求网络链接的 APN或者意愿指示。
步骤 602, 无线侧网元转发附着请求消息， 并通过底层的初始化非接入 层消息将无线侧网元是否支持本地访问的能力带给移动性管理单元。 其中 无线侧网元包括： 家庭基站、 宏基站、 家庭基站网关。 移动性管理单元可 以是移动性管理实体或者支持 S4接口的服务 GPRS支持节点。
步骤 603 ,移动性管理单元根据附着请求消息中的用户安全信息对该用 户进行鉴权和认证， 确保授权用户接入网络。
步骤 604, 如果移动性管理单元中没有用户的签约数据， 那么通过更新 位置请求消息请求归属用户数据服务器进行用户签约信息的下发。
步骤 605 ,归属用户数据服务器通过更新位置确认消息将用户的签约数 据下发给移动性管理单元。
步骤 606,移动性管理单元根据用户请求的接入点名（ APN, access point name )或者意愿指示结合用户的签约数据判断为用户所建立网络链接的类 型， 并选择适合的网关。
这里， 如果用户请求的是本地访问链接或者网络决定为用户建立本地 访问链接， 那么移动性管理单元为该用户选择本地网关完成用户本地访问 功能。 如果用户请求的是核心网链接或者网络决定为用户建立核心网链接 , 那么移动性管理单元为该用户选择核心网网关完成用户通过核心网访问互 联网的功能。 本实例以用户请求的是核心网链接或者网络决定为用户建立 核心网链接为例进行描述， 相应的建立本地访问链接的过程类似， 不同之 处在实施步骤中做简要描述。
步骤 607, 如果所建链接为核心网链接， 那么移动性管理单元根据核心 网网关选择适合的服务网关并通过创建会话请求消息进行网络链接的建立 过程。 其中携带步骤 606所判断的网络链接类型信息。
这里， 如果所建链接为本地访问链接， 那么移动性管理单元可以釆用 现有的直接隧道方式向本地网关直接发送创建会话请求消息， 不再进行服 务网关选择并通过服务网关建立本地访问链接， 此时移动性管理单元保存 网络链接类型， 在用户后续转移至空闲状态建立本地访问转发通道时再通 知其网络链接类型， 详见图 12实例三所描述的实施方式。 移动性管理单元 也可以进行服务网关选择并通过服务网关建立本地访问连接， 此时核心网 移动性管理单元将网络链接类型直接通知服务网关。
步骤 608,服务网关通过创建会话请求消息在核心网网关建立网络链接 所对应的上下文， 并将服务网关地址及隧道标识上报给核心网网关作为下 行数据传输使用。
步骤 609, 网关向服务网关回复创建会话响应消息。将网关为上行数据 传输所分配的上行隧道标识带给服务网关。
步骤 610,服务网关向移动性管理单元回复创建会话响应消息。 将服务 网关为上行数据传输所分配的上行隧道标识带给移动性管理单元。
步骤 611 , 执行后续附着过程包括无线承载的建立、 上下行隧道打通等 过程， 与现有技术相同， 不做赘述。
实例二： 图 11为 LTE系统 PDN连接建立过程核心网链接建立时本发 明的实施方式， 具体包括以下步骤：
步骤 701 , 用户需要访问新的互联网内容时发起 PDN连接请求， 其中 携带用户所要请求网络链接的 APN或者意愿指示。
步骤 702 , 无线侧网元转发 PDN连接请求消息， 并通过底层的直传消 息将无线侧网元是否支持本地访问的能力带给移动性管理单元。 其中无线 侧网元包括： 家庭基站、 宏基站、 家庭基站网关。 移动性管理单元可以是 移动性管理实体 MME或者支持 S4接口的服务 GPRS支持节点 SGSN。
步骤 703 , 移动性管理单元根据用户请求的 APN或者意愿指示结合附 着过程所下载的用户签约数据判断为用户所建立网络链接的类型， 并选择 适合的网关。
这里， 如果用户请求的是本地访问链接或者网络决定为用户建立本地 访问链接， 那么移动性管理单元为该用户选择本地网关完成用户本地访问 功能。 如果用户请求的是核心网链接或者网络决定为用户建立核心网链接 , 那么移动性管理单元为该用户选择核心网网关完成用户通过核心网访问互 联网的功能。 本实例以用户请求的是核心网链接或者网络决定为用户建立 核心网链接为例进行描述， 相应的建立本地访问链接的过程类似， 不同之 处在实施步骤中做简要描述。
步骤 704, 如果所建链接为核心网链接， 那么移动性管理单元根据核心 网网关选择适合的服务网关并通过创建会话请求消息进行网络链接的建立 过程。 其中携带步骤 703所判断的网络链接类型信息。
这里， 如果所建链接为本地访问链接， 那么移动性管理单元可以釆用 现有的直接隧道方式向本地网关直接发送创建会话请求消息， 不再进行服 务网关选择并通过服务网关建立本地访问链接， 此时移动性管理单元保存 网络链接类型， 在用户后续转移至空闲状态建立本地访问转发通道时再通 知其网络链接类型， 详见图 12实例三所描述的实施方式。 移动性管理单元 也可以进行服务网关选择并通过服务网关建立本地访问连接， 此时核心网 移动性管理单元将网络链接类型直接通知服务网关。
步骤 705 ,服务网关通过创建会话请求消息在核心网网关建立网络链接 所对应的上下文， 并将服务网关地址及隧道标识上报给核心网网关作为下 行数据传输使用。
步骤 706 ,核心网网关向服务网关回复创建会话响应消息。将核心网网 关为上行数据传输所分配的上行隧道标识带给服务网关。
步骤 707,服务网关向移动性管理单元回复创建会话响应消息。 将服务 网关为上行数据传输所分配的上行隧道标识带给移动性管理单元。
步骤 708, 执行后续 PDN连接建立过程包括无线承载的建立、 上下行 隧道打通等过程， 与现有技术相同， 不做赞述。
实例三： 图 12为 LTE系统 S 1释放过程本地访问转发链接建立时本发 明的实施方式， 具体包括以下步骤：
步骤 801 , 如果无线侧网元因为 0&M互操作、 用户去激活、 重复的完 整性检查失败等原因决定释放用户的信令连接时， 会向移动性管理单元发 送 S1用户上下文释放请求消息。 在移动性管理单元完成信令及数据传输过 程后， 为了节省网络资源也会发起用户的信令连接释放， 将用户从连接状 态转为空闲状态， 此时不需要步骤 801。
步骤 802 , 移动性管理单元判断用户当前是否有已激活的本地访问链 接， 如果没有则进行正常的 Sl-U接口承载释放过程， 此为现有技术不做赘 述。 如果有则创建本地访问链接的转发通道。
步骤 803 , 如果当前用户有已激活的本地访问链接， 那么移动性管理单 元通过创建会话请求将网络链接类型告知服务网关。
步骤 804,服务网关通过修改承载请求消息将服务网关的地址和下行緩 存通道的隧道标识信息告知本地网关。 由于此时本地网关已经存在本地访 问链接的上下文信息， 因此仅需要服务网关进行隧道更新即可。 本地网关 隧道更新后即可进行本地访问下行数据的緩存。
步骤 805 , 本地网关向月良务网关回复爹改 载响应消息。
步骤 806, 服务网关向移动性管理单元回复创建会话响应消息。
步骤 807 , 继续完成后续的 S1链接释放过程， 将空口资源释放， 用户 从连接状态转入空闲状态。
实例四：图 13为 LTE系统数据緩存单元收到核心网下行数据后链路更 新的实施方式一， 包括以下步骤：
步骤 901 ,核心网网关将收到的用户下行数据发送到作为緩存单元的服 务网关。
步骤 902,服务网关根据下行数据传输所釆用的网络链接， 结合已保存 的网络链接类型判断下行数据的来源。
步骤 903 ,服务网关在下行数据通知消息中将表征下行数据类型的信息 带给移动性管理单元， 其中表征下行数据类型的信息可以包括以下内容： 网关地址、 网关标识、 新定义的下行数据类型指示。
步骤 904, 移动性管理单元在用户注册的区域内发起寻呼。
步骤 905 , 用户收到寻呼消息后发起业务请求进行响应。
步骤 906,移动性管理单元通过初始上下文建立请求消息指示无线侧建 立空口承载， 消息中携带本地访问直接隧道的上行隧道标识、 地址信息及 承载 Qos信息。
步骤 907,无线侧网元根据承载 Qos信息建立空口承载。其中无线侧网 元包括： 家庭基站、 宏基站、 家庭基站网关。
步骤 908,无线侧网元通过初始上下文建立完成消息将分配的下行隧道 标识和地址信息带给移动性管理单元。
步骤 909, 用户进入连接状态， 移动性管理单元通过修改承载请求消息 将无线侧网元分配的下行隧道标识、 地址信息等直接带给本地网关或者通 过服务网关转发， 打通本地访问链接的数据下行传输通道。
步骤 910, 本地网关为移动性管理单元回复修改承载响应消息， 或者通 过服务网关转发。
步骤 911 ,无线侧网元通过步骤 906得知本地访问直接隧道的上行隧道 标识， 本地网关通过步骤 909得到本地访问直接隧道的下行隧道标识则本 地访问上下行数据可以正常传输。
步骤 912, 由于下行数据来源于核心网， 则移动性管理单元发起本地访 问下行转发网络链接的删除， 移动性管理单元通过删除会话请求将转发网 络链接所对应的上下文删除。
步骤 913 ,服务网关发现该条网络链接用于本地访问， 则删除相应的上 下文并回复删除会话响应消息。
本发明中， 当移动性管理单元在步骤 903 获知下行数据来源时， 即可 发起步骤 912和步骤 913 , 以进行本地访问转发网络链接的删除， 因此与后 续步骤的先后顺序不做限定。
实例五：图 14为 LTE系统数据緩存单元收到核心网下行数据后链路更 新的实施方式二， 包括以下步骤：
步骤 1001 , 核心网网关将收到的用户下行数据发送到作为緩存单元的 服务网关。 步骤 1002 , 服务网关根据下行数据传输所釆用的网络链接， 结合已保 存的网络链接类型判断下行数据的来源。
步骤 1003 , 服务网关向移动性管理单元发送下行数据通知消息触发寻 呼过程。
步骤 1004, 移动性管理单元在用户注册的区域内发起寻呼。
步骤 1005 , 用户收到寻呼消息后发起业务请求进行响应。
步骤 1006, 移动性管理单元通过初始上下文建立请求消息指示无线侧 建立空口承载， 消息中携带本地访问直接隧道的上行隧道标识、 地址信息 及承载 Qos信息。
步骤 1007, 无线侧网元根据承载 Qos信息建立空口承载。 其中无线侧 网元包括： 家庭基站、 宏基站、 家庭基站网关。
步骤 1008 , 无线侧网元通过初始上下文建立完成消息将分配的下行隧 道标识和地址信息带给移动性管理单元。
步骤 1009 , 用户进入连接状态， 移动性管理单元通过修改承载请求消 息将无线侧网元分配的下行隧道标识、 地址信息等直接带给本地网关或者 通过服务网关转发， 打通本地访问链接的数据下行传输通道。
步骤 1010, 本地网关为移动性管理单元直接回复修改承载响应消息， 或者通过服务网关转发。
步骤 1011 ,无线侧网元通过步骤 1006得知本地访问直接隧道的上行隧 道标识， 本地网关通过步骤 1009得到本地访问直接隧道的下行隧道标识则 本地访问上下行数据可以正常传输。
步骤 1012 , 由于下行数据来源于核心网， 则服务网关发起本地访问下 行转发网络链接的删除， 服务网关通过携带特殊原因值的删除承载请求将 转发网络链接所对应的用户面隧道进行删除。 其中特殊的原因值用于指示 移动性管理单元仅删除隧道信息， 保留承载的控制面信息以便本地访问直 接隧道建立时使用。
步骤 1013 , 移动性管理单元删除该条网络链接所对应的承载信息并回 复删除承载响应消息。
本发明中， 当服务网关在步骤 1002获知下行数据来源时， 即可发起步 骤 1012和步骤 1013 , 以进行本地访问转发网络链接的删除， 因此与后续步 骤的先后顺序不做限定。 本实例所述方法移动性管理单元不能得知下行数 据来源， 因此若在收到步骤 1012步之前完成了无线承载的建立， 那么它仍 会发起转发网络链接的更新， 此时服务网关收到更新消息忽略不做响应。
实例六： 图 15为 GPRS系统分组数据协议（PDP )上下文激活过程核 心网指示网络链接类型的实施方式， 具体包括以下步骤：
步骤 1101 , 用户需要访问新的互联网内容时发起激活 PDP上下文请求 消息， 其中携带用户所要请求网络链接的 APN或者意愿指示。
步骤 1102, 无线侧网元转发激活 PDP上下文请求消息， 并通过底层的 直传消息将无线侧网元是否支持本地访问的能力带给服务 GPRS支持节点。
步骤 1103 ,服务 GPRS支持节点根据用户请求的 APN或者意愿指示结 合附着过程所下载的用户签约数据判断为用户所建立网络链接的类型， 并 选择适合的网关。
这里， 由于服务 GPRS支持节点作为 3G系统下行数据的緩存点， 因此 判断后本地保存所建网络链接的类型。 如果用户请求的是本地访问链接或 者网络决定为用户建立本地访问链接， 那么移动性管理单元为该用户选择 本地网关完成用户本地访问功能。 如果用户请求的是核心网链接或者网络 决定为用户建立核心网链接， 那么移动性管理单元为该用户选择核心网网 关完成用户通过核心网访问互联网的功能。 本实例以用户请求的是核心网 链接或者网络决定为用户建立核心网链接为例进行描述， 相应的建立本地 访问链接的过程类似， 不同之处在实施步骤中做简要描述。 步骤 1104, 如果所建链接为核心网链接， 那么服务 GPRS支持节点通 过创建 PDP上下文请求消息进行网络链接的建立过程。 同理如果所建链接 为本地访问链接， 那么服务 GPRS支持节点向本地网关直接发送创建 PDP 上下文请求消息。
步骤 1105 , 网关， 包括核心网网关及本地访问的网关回复创建 PDP上 下文响应并将分配的上行隧道标识和地址信息带给服务 GPRS支持节点。
步骤 1106, 服务 GPRS支持节点指示无线侧网元建立空口承载， 其中 无线侧网元可以是： 家庭基站、 宏基站、 家庭基站网关。
如果所建立的网络链接为本地访问链接， 那么服务 GPRS 支持节点判 断釆用直接隧道方式就将本地网关分配的上行隧道标识和地址信息带给无 线侧网元。 如果所建立的网络链接为核心网链接， 那么服务 GPRS 支持节 点将其分配的上行隧道标识和地址信息带给无线侧网元。
无线承载建立完成后无线侧网元将其分配的下行隧道标识和地址信息 带给服务 GPRS支持节点。
步骤 1107, 在建立核心网链接时， 如果需要进行 Qos协商， 那么就执 行该步骤， 将无线侧请求的 Qos信息带给核心网网关， 否则本步骤可以忽 略。 如果建立的是本地访问链接， 那么本步骤建立本地访问的直接隧道， 将无线侧网元分配的下行隧道标识和地址信息带给本地网关， 打通下行通 道。
步骤 1108, 核心网网关回复更新 PDP上下文响应消息。
步骤 1109, 服务 GPRS支持节点回复激活 PDP上下文接受消息。
由于服务 GPRS 支持节点本身也为数据緩存单元， 所以建立了网络链 接之后就一直保存网络链接类型， 即便是用户进入空闲状态 （Iu连接释放 过程）也不释放， 服务 GPRS 支持节点仅完成至本地网关间隧道的更新即 可。 实例七： 图 16为 GPRS系统数据緩存单元收到核心网下行数据后链路 更新的实施方式， 具体包括以下步骤：
步骤 1201 , 核心网网关将收到的用户下行数据发送到作为緩存单元的 服务 GPRS支持节点。
步骤 1202 ,服务 GPRS支持节点根据下行数据传输所釆用的网络链接， 结合已保存的网络链接类型判断下行数据的来源。 如果得知下行数据为核 心网数据那么就释放本地访问转发链接的用户面信息， 这是服务 GPRS 支 持节点的内部操作， 具体方式不做说明。
步骤 1203 , 服务 GPRS支持节点在用户注册的区域内发起寻呼。
步骤 1204, 用户收到寻呼消息后发起业务请求进行响应。
步骤 1205 , 服务 GPRS支持节点通过无线承载指派请求消息指示无线 侧建立空口承载， 消息中携带本地访问直接隧道的上行隧道标识、 地址信 息及承载 Qos信息。
步骤 1206, 无线侧网元根据承载 Qos信息建立空口承载。 其中无线侧 网元包括： 家庭基站、 宏基站、 家庭基站网关。
步骤 1207 , 无线侧网元通过无线承载指派响应消息将分配的下行隧道 标识和地址信息带给服务 GPRS支持节点。
步骤 1208, 用户进入连接状态， 服务 GPRS支持节点通过更新 PDP上 下文请求消息将无线侧网元分配的下行隧道标识、 地址信息等带给本地网 关， 打通本地访问链接的数据下行传输通道。
步骤 1209, 本地网关为服务 GPRS支持节点回复修改承载响应消息。 步骤 1210,无线侧网元通过步骤 1205得知本地访问直接隧道的上行隧 道标识， 本地网关通过步骤 1208得到本地访问直接隧道的下行隧道标识则 本地访问上下行数据可以通过直接隧道正常传输。
在本发明的以上各实例所有场景中， 如果数据緩存单元判断数据是本 地访问数据， 那么数据緩存单元通过正常的下行数据通知消息告知移动性 定时器超时后释放转发链路资源。
如果数据緩存单元判断数据既有核心网数据也有本地访问数据， 那么 数据緩存单元通过正常的下行数据通知消息告知移动性管理单元。 核心网 移动性管理单元按照现有技术开启转发链路定时器， 在定时器超时后释放 转发链路资源。
一种数据緩存单元区分网络链接类型的系统， 该系统包括： 移动性管 理单元侧的通知模块、 和数据緩存单元侧的释放模块。 其中， 通知模块， 用于移动性管理单元在建立网络链接时， 将网络链接的类型通知数据緩存 单元侧的释放模块。 释放模块， 用于根据网络链接的类型执行或者指示移 动性管理单元释放资源。
这里， 该系统还包括： 数据緩存单元侧的保存模块， 用于数据緩存单 元获知网络链接的类型后， 在本地保存网络链接的类型。
这里， 释放模块， 进一步包括： 获取模块、 判断模块和释放执行模块。 其中， 获取模块用于当从网络链接上接收到下行数据时， 获取保存模块所 保存的网络链接的类型。 判断模块， 用于根据网络链接的类型判断出下行 数据的数据类型为核心网数据、 或本地访问数据、 或者包括核心网数据和 本地访问数据。 释放执行模块， 用于根据判断结果的不同， 分别执行或者 指示移动性管理单元进行相对应的释放资源的操作。
这里， 对以上各图及文字中所涉及的有关中英文注释的事项统一解释 下：
归属用户服务器以 Home Subscriber Server表示， 缩写为 HSS; 移动性 管理实体以 Mobility Management Entity表示， 缩写为 MME; 服务 GPRS 支持节点以 Serving GPRS Support Node表示， 缩写为 SGSN; 策略计费规 则功能以 Policy and Charging Rule Function表示， 缩写为 PCRF; 服务网关 以 Serving Gateway表示， 缩写为 S-GW, 即为图 1中的 Serving GW; 分组 数据网关以 PDN Gateway表示， 缩写为 P-GW, 即为图 1中的 PDN GW; 分组数据网络以 Packet Data Network表示， 缩写为 PDN; 图 1中的 RNC 为无线网络控制器； 图 1中的 E-NodeB为演进基站， 也可以用 eNB表示； 图 5中的 CN为核心网；网关 GPRS支持节点以 Gateway GPRS Support Node 表示， 缩写为 GGSN； 家庭基站以 Home NodeB表示， 缩写为 HNB； 演进 的家庭基站以 Home eNodeB表示，缩写为 HeNB; 本地访问功能以 Local IP Access或者 Selected IP Traffic Offload表示， 缩写为 LIPA或者 SIPTO。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种数据緩存单元区分网络链接类型的方法， 其特征在于， 该方法 包括： 移动性管理单元在建立网络链接时， 将所述网络链接的类型通知数 据緩存单元； 所述数据緩存单元根据所述网络链接的类型执行或者指示移 动性管理单元释放资源。
2、 根据权利要求 1所述的方法， 其特征在于， 所述数据緩存单元获知 所述网络链接的类型后， 在本地保存所述网络链接的类型。
3、 根据权利要求 2所述的方法， 其特征在于， 所述数据緩存单元根据 所述网络链接的类型执行或者指示移动性管理单元释放资源包括：
当所述数据緩存单元从网络链接上接收到下行数据时， 根据保存的所 述网络链接的类型， 判断出所述下行数据的数据类型为核心网数据、 或本 地数据、 或者包括核心网数据和本地数据； 根据判断结果的不同， 分别执 行或者指示移动性管理单元进行相对应的释放资源的操作。
4、 根据权利要求 3所述的方法， 其特征在于， 当所述数据緩存单元判 断出所述下行数据的数据类型为核心网数据时， 执行或者指示移动性管理 单元释放资源的操作包括：
由数据緩存单元将本地和核心网移动性管理单元的转发链路资源进行 释放； 或者，
数据緩存单元将能够表征下行数据类型的信息告知移动性管理单元， 由移动性管理单元将本地和数据緩存单元中的转发链路资源进行释放。
5、 根据权利要求 4所述的方法， 其特征在于， 所述表征下行数据类型 的信息包括： 网关地址、 网关标识、 新定义的下行数据类型指示中至少一 种。
6、 根据权利要求 3所述的方法， 其特征在于， 当所述数据緩存单元判 断出所述下行数据的数据类型为本地数据时， 指示移动性管理单元执行释 放资源的操作包括：
数据緩存单元通过正常的下行数据通知消息告知移动性管理单元； 由移动性管理单元开启转发链路定时器， 在转发链路定时器超时后释 放转发链路资源； 或者，
当所述数据緩存单元判断出所述下行数据的数据类型为包括核心网数 据和本地数据时， 指示移动性管理单元执行的释放资源的操作包括：
数据緩存单元通过正常的下行数据通知消息告知移动性管理单元； 由移动性管理单元开启转发链路定时器， 在转发链路定时器超时后释 放转发链路资源。
7、 根据权利要求 1至 6中任一项所述的方法， 其特征在于， 所述网络 链接类型包括： 核心网链接、 本地链接中至少一种。
8、 一种数据緩存单元区分网络链接类型的系统， 其特征在于， 该系统 包括： 移动性管理单元侧的通知模块、 和数据緩存单元侧的释放模块； 其 中，
通知模块， 用于移动性管理单元在建立网络链接时， 将所述网络链接 的类型通知数据緩存单元侧的释放模块；
释放模块， 用于根据所述网络链接的类型执行或者指示移动性管理单 元释放资源。
9、 根据权利要求 8所述的系统， 其特征在于， 该系统还包括： 数据緩 存单元侧的保存模块， 用于数据緩存单元获知所述网络链接的类型后， 在 本地保存所述网络链接的类型。
10、 根据权利要求 9所述的系统， 其特征在于， 所述释放模块， 进一 步包括： 获取模块、 判断模块和释放执行模块； 其中，
获取模块， 用于当从网络链接上接收到下行数据时， 获取保存模块所 保存的所述网络链接的类型； 判断模块， 用于根据所述网络链接的类型判断出所述下行数据的数据 类型为核心网数据、 或本地数据、 或者包括核心网数据和本地数据；
释放执行模块， 用于根据判断结果的不同， 分别执行或者指示移动性 管理单元进行相对应的释放资源的操作。
PCT/CN2010/078107 2009-11-26 2010-10-26 一种数据缓存单元区分网络链接类型的方法及系统 WO2011063692A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910241579.XA CN102083144B (zh) 2009-11-26 2009-11-26 一种数据缓存单元区分网络链接类型的方法及系统
CN200910241579.X 2009-11-26

Publications (1)

Publication Number Publication Date
WO2011063692A1 true WO2011063692A1 (zh) 2011-06-03

Family

ID=44065853

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/078107 WO2011063692A1 (zh) 2009-11-26 2010-10-26 一种数据缓存单元区分网络链接类型的方法及系统

Country Status (2)

Country Link
CN (1) CN102083144B (zh)
WO (1) WO2011063692A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104904261B (zh) * 2013-11-26 2019-07-23 华为技术有限公司 接入网实体、核心网设备及其获取ue的相关策略的方法
CN106412948B (zh) * 2015-07-31 2019-09-20 联芯科技有限公司 一种涉及nas信令消息的传输方法及其传输终端

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060709A (zh) * 2006-04-20 2007-10-24 华为技术有限公司 异质网络切换过程中目标网络预留资源处理方法及系统
US20080095051A1 (en) * 2006-10-18 2008-04-24 Samsung Electronics Co., Ltd. Apparatus and method for saving resources between core network and base station controller in a mobile communication system
CN101330753A (zh) * 2007-06-22 2008-12-24 华为技术有限公司 一种资源创建方法、资源删除方法及网络设备
CN101867983A (zh) * 2009-04-16 2010-10-20 大唐移动通信设备有限公司 切换方法、系统及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296493B (zh) * 2007-04-24 2013-02-13 华为技术有限公司 资源释放方法和网络设备
CN101448249B (zh) * 2008-01-25 2011-03-16 中兴通讯股份有限公司 一种释放服务网关缓存数据的方法
CN101282511B (zh) * 2008-05-16 2011-07-13 中兴通讯股份有限公司 承载处理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060709A (zh) * 2006-04-20 2007-10-24 华为技术有限公司 异质网络切换过程中目标网络预留资源处理方法及系统
US20080095051A1 (en) * 2006-10-18 2008-04-24 Samsung Electronics Co., Ltd. Apparatus and method for saving resources between core network and base station controller in a mobile communication system
CN101330753A (zh) * 2007-06-22 2008-12-24 华为技术有限公司 一种资源创建方法、资源删除方法及网络设备
CN101867983A (zh) * 2009-04-16 2010-10-20 大唐移动通信设备有限公司 切换方法、系统及装置

Also Published As

Publication number Publication date
CN102083144B (zh) 2014-01-01
CN102083144A (zh) 2011-06-01

Similar Documents

Publication Publication Date Title
EP2445261B1 (en) Method, apparatus and system for routing user plane data in mobile network
US8855045B2 (en) Method and system for controlling establishment of local IP access
US8842636B2 (en) Method and device for managing Internet Protocol offload connection
WO2011020405A1 (zh) 指示数据分流的方法、系统及传输分流网元
WO2011026392A1 (zh) 一种路由策略的获取方法及系统
WO2011054264A1 (zh) 一种建立本地ip访问下行数据通道的方法及系统
WO2011035732A1 (zh) 本地ip接入或选定的ip流量卸载的控制方法、装置与系统
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及系统
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
EP2790457B1 (en) Method and device for processing local access connection
WO2011026407A1 (zh) 一种本地网际协议访问连接移动性支持的方法及系统
WO2011015124A1 (zh) 实现本地ip访问控制的方法、通知方法及系统
CN102056141B (zh) 一种实现本地接入的系统和方法
WO2012025031A1 (zh) 基于本地接入的承载建立方法及系统
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
WO2010127580A1 (zh) 一种本地ip访问的寻呼方法及相关装置
WO2011050663A1 (zh) 支持本地ip访问的通信系统中隧道更新方法与系统
CN102014452B (zh) 一种本地ip访问连接实现移动性的方法和系统
WO2011020418A1 (zh) 终端转为连接态时更改服务网关的连接激活方法及系统
WO2011157100A1 (zh) 一种数据缓存的方法和系统
WO2011085623A1 (zh) 本地接入网关获取终端的寻呼信息的方法和系统
WO2011009353A1 (zh) 建立ip分流连接的实现方法和系统
WO2011063692A1 (zh) 一种数据缓存单元区分网络链接类型的方法及系统
WO2011035719A1 (zh) 一种释放本地连接的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10832599

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10832599

Country of ref document: EP

Kind code of ref document: A1