WO2011015147A1 - 数据传输方法、装置和通信系统 - Google Patents

数据传输方法、装置和通信系统 Download PDF

Info

Publication number
WO2011015147A1
WO2011015147A1 PCT/CN2010/075766 CN2010075766W WO2011015147A1 WO 2011015147 A1 WO2011015147 A1 WO 2011015147A1 CN 2010075766 W CN2010075766 W CN 2010075766W WO 2011015147 A1 WO2011015147 A1 WO 2011015147A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
service
node
base station
radio access
Prior art date
Application number
PCT/CN2010/075766
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 WO2011015147A1 publication Critical patent/WO2011015147A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • the present invention relates to the field of communications, and in particular, to a data transmission method, apparatus, and communication system. Background technique
  • a user equipment can access the mobile network through the home wireless access point and communicate with the packet data network through the mobile network.
  • the home wireless access point may be: 3G Home NodeB (HNB), Home evolved NodeB (HeNB), or Home Non-3GPP Wireless Access Point (Home non-3 GPP Wireless) Access Point, Home non-3GPP WAP); HNB, HeNB, and Home non-3GPP WAP are connected to the 3G home base station gateway, the home evolved base station gateway, and the home non-3GPP wireless access point gateway through the universal IP access network, respectively, through the 3G family.
  • the base station gateway, the home evolved base station gateway, and the home non-3GPP wireless access point gateway are connected to the mobile network.
  • the data transmission between the UE and the packet data network is performed by using the home access system architecture
  • the data needs to be transmitted through multiple network elements.
  • the HNB passes the data sent by the UE through the general IP.
  • the access network is transmitted to the 3G home base station gateway, and the 3G home base station gateway transmits the data to the packet data network through the SGSN and the GGSN.
  • the data transmission path is long, and the data element passing through the network element needs to be It allocates transmission resources, which makes the network transmission occupy more network resources.
  • the embodiment of the invention provides a data transmission method, device and communication system, which can save network resources occupied by data transmission and improve transmission efficiency.
  • Embodiments of the present invention adopt the following technical solutions:
  • a data transmission method includes: a node having a service offload function establishing a correspondence between a service flow of a user equipment and a radio access bearer; and the node having the service offload function according to the correspondence relationship, the received packet data network
  • the service flow is directly sent to the user equipment by using a radio access bearer; or the service flow of the user equipment received through the radio access bearer is directly forwarded to the packet data network.
  • a node with a service offload function including:
  • a establishing unit configured to establish a correspondence between a service flow of the user equipment and a radio access bearer
  • a transmitting unit configured to: according to the correspondence between the service flow and the radio access bearer established by the establishing unit, the received packet data network
  • the service flow is directly sent to the user equipment by using a radio access bearer; or the service flow of the user equipment received through the radio access bearer is directly forwarded to the packet data network.
  • a communication system comprising: a service offloading device, configured to establish a correspondence between a service flow of a user equipment and a radio access bearer, and to receive a service of the packet data network according to the correspondence between the service flow and the radio access bearer
  • the flow is directly sent to the user equipment by using the radio access bearer; or the service flow of the user equipment received through the radio access bearer is directly forwarded to the packet data network.
  • FIG. 1 is a schematic diagram of a home access system architecture provided by the prior art
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present invention.
  • FIG. 3 is a timing diagram of a data transmission method according to another embodiment of the present invention.
  • FIG. 4 is a sequence diagram of a data transmission method according to another embodiment of the present invention.
  • FIG. 5 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 6 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 7 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 8 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 9 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 10 is a timing diagram of a data transmission method according to still another embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a data offloading apparatus according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram showing the structure of an establishing unit in the data unloading apparatus according to the embodiment of the present invention shown in FIG. detailed description
  • the network element in the mobile network may include: Mobility Management Entity (MME) in the evolved UMTS Territorial Radio Access Network (E-UTRAN), traditional Serving GPRS Supporting Node (SGSN) in the core network, Gateway GPRS Supporting Node (GGSN) in the traditional core network, and Serving Gateway (S- in the evolved core network) GW), Packet Data Network Gateway (P-GW) in the evolved core network, non-3GPP gateway (non-3GPP GW) including multiple implementing entities in the non-3GPP network, and Home Subscriber Server (Home Subscriber Server) , HSS) and Authentication, 4 Authorization and Accounting Server (AAA Server).
  • MME Mobility Management Entity
  • E-UTRAN evolved UMTS Territorial Radio Access Network
  • SGSN Serving GPRS Supporting Node
  • GGSN Gateway GPRS Supporting Node
  • S- Serving Gateway
  • P-GW Packet Data Network Gateway
  • non-3GPP gateway non-3GPP gateway
  • HSS Home Subscriber Server
  • AAA Server
  • the embodiment of the present invention provides a data. Transmission method, device and communication system.
  • the data transmission method provided by the embodiment of the present invention includes:
  • Step 201 The node with the service offload function establishes a correspondence between the service flow of the UE and the radio access bearer.
  • Step 202 The node 4 with the service offload function sends the downlink service flow from the packet data network to the UE directly through the radio access bearer according to the corresponding relationship between the service flow and the radio access bearer; or, the radio access bearer receives the radio access bearer.
  • the uplink traffic of the arriving UE is directly forwarded to the packet data network.
  • the packet data network may be an Internet or an enterprise network, etc.
  • the node having the service offload function may be a home base station or a home base station gateway that integrates a core network user plane gateway, where the user plane gateway is an SGSN, or a P-GW, or a P-GW and an S-GW
  • the home base station may be an HNB, a HeNB, a NodeB, or an eNodeB
  • the home base station gateway is a 3G home base station gateway, or a home evolved base station gateway, or a base station controller, Or a wireless network controller, etc.
  • step 201 may specifically establish a correspondence between the service flow of the UE and the wireless access by using any one of the following methods:
  • the node with the service offload function receives the bearer setup request, and the bearer setup request includes the IP address of the GPRS Tunneling Protocol (GTP) tunnel and the Tunnel Endpoint Identifier (TEID).
  • the node with the service offload function obtains the core network-borne context corresponding to the UE locally according to the IP address and the TEID of the GTP tunnel that receives the uplink data, and associates the service flow related to the core network-loaded context with the radio access bearer. relationship.
  • GTP GPRS Tunneling Protocol
  • TEID Tunnel Endpoint Identifier
  • the mapping between the service flow of the UE and the radio access bearer may be a mapping relationship between the service flow of the UE and the radio access bearer.
  • the mapping relationship table may be a mapping relationship table.
  • UE1's service flow A ... wireless access 7 a
  • UE2's service flow B ... wireless access bearer b
  • the corresponding relationship between the service flow of the UE and the radio access may be added to the service flow of the UE, or the corresponding UE may be added to the radio access 7
  • the identifier of the service flow may also be that the identifier of the corresponding radio access bearer is added to the service flow of the UE, and the identifier of the service flow of the corresponding UE is added to the radio access bearer.
  • a node with a service offloading function can also establish a correspondence between a service flow and a wireless access bearer by other methods, and details are not described herein.
  • the correspondence between the service flow of the UE and the wireless access can also be referred to the description herein.
  • the bearer setup request may further include the service offloading indication information, where the node with the service offloading function determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, according to the IP address and TEID of the GTP tunnel receiving the uplink data,
  • the core network bearer context corresponding to the UE is obtained locally, and the core network bearer context-related service flow and the radio access bearer are associated with each other.
  • the node with the service offloading function receives the bearer setup request.
  • the bearer request may include the bearer identifier, and the node with the service offloading function according to the bearer identifier included in the bearer setup request and the obtained user identity identifier (international mobile subscriber identity) , IMSI), obtaining the core network bearer context corresponding to the UE from the local, and establishing a corresponding relationship between the core network bearer context-related service flow and the wireless access bearer.
  • IMSI international mobile subscriber identity
  • the node with the service offload function can also obtain the context of the core network corresponding to the UE according to the acquired IMSI, and establish a corresponding relationship between the context-related service flow of the core network and the wireless access bearer.
  • the identifier may also be a Radio Access Bearer Identity (RAB ID) or a Net Service Access Point Identity (Net Service Access Point Identity, etc.).
  • RAB ID Radio Access Bearer Identity
  • Net Service Access Point Identity Net Service Access Point Identity
  • the node with the service offload function may obtain the IMSI of the UE from the user context (3G home base station gateway service offload scenario); or, when the bearer setup request includes the IMSI, the node with the service offload function may also The IMSI of the UE is obtained in the bearer setup request.
  • the bearer setup request may further include a service offloading indication information, where the node with the service offloading function determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, and obtains the core network bearer corresponding to the UE according to the IMSI and the bearer identifier. Context, and the core network bearer context-related service flow and the radio access bearer are associated with each other. Further, when the bearer setup request includes the IMSI, the IMSI is used as the service offloading indication information.
  • the node with the service offloading function receives the update bearer request, and the update bearer request includes the IP address and TEID of the GTP tunnel receiving the downlink data.
  • the node with the service offload function is based on the IP address and TEID of the GTP tunnel receiving the downlink data.
  • the update bearer request may further include the service offloading indication information, and the node having the service offloading function determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, and is locally obtained according to the IP address and TEID of the GTP tunnel receiving the downlink data.
  • the node having the service offloading function determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, and is locally obtained according to the IP address and TEID of the GTP tunnel receiving the downlink data.
  • the node with the service offload function receives the update bearer request.
  • the update bearer request may include the bearer identifier.
  • the node with the service offload function obtains the radio connection corresponding to the UE according to the bearer identifier and the IMSI of the update bearer request. Enter a context, and associate the radio access bearer with the service flow corresponding to the core network bearer context associated with the update bearer request.
  • the bearer identifier may also be a RAB ID or an NSAPI
  • the core network bearer context is a core network bearer context corresponding to the UE.
  • the node with the service offload function can also obtain the UE correspondingly according to the acquired IMSI.
  • carries the context, and establishes a correspondence between the core network 7
  • the update bearer request may further include the service offloading indication information, and the node that has the service offloading function determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, according to
  • the IMSI and the bearer identifier obtain the radio access bearer context corresponding to the UE from the local device, and establish a corresponding relationship between the radio access bearer and the service flow corresponding to the core bearer context associated with the update bearer request.
  • the node with the service offload function can associate the service flow of the UE with the radio access bearer, and directly forward the data transmitted between the UE and the packet data network according to the corresponding relationship. It does not occupy the transmission resources of the access network to the core network and the processing bandwidth of the core network user plane, which saves the network resources occupied by the data transmission, and solves the problem of using the home access system architecture provided by the prior art between the UE and the packet data network.
  • the data transmission occupies too much network resources, improves the data transmission rate, and thus improves the user's service experience.
  • the node with the service offload function is a home base station gateway integrating the core network user plane gateway; wherein the home base station gateway may be a 3G home base station gateway (Home NodeB Gateway), or a home evolved base station
  • the home eNodeB Gateway the core network user plane gateway can be a GGSN, or an S-GW and a P-GW.
  • a data transmission method provided by another embodiment of the present invention includes:
  • Step 301 The UE sends a bearer setup request to the core network mobility management entity.
  • the mobility management entity may be an SGSN or an MME or the like.
  • Step 302 The core network mobility management entity sends a create bearer request to the core network user plane gateway.
  • Step 303 The core network user plane gateway creates a ⁇ load for the UE, and allocates an IP for the created ⁇ load.
  • the core network user plane gateway may send the IP address assigned to the UE to the UE through an independent message, or may include the IP address allocated for the bearer in the create bearer response and send the message to the UE. I will not repeat them.
  • Step 304 The core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes an IP address and a TEID of the GTP tunnel that receives the uplink data allocated by the core network user plane gateway.
  • the bearer setup request is further
  • the service offload indication information and/or the IMSI may be included. Further, the service offload indication information may be an IMSI.
  • Step 305 The home base station gateway allocates the user plane resource, and obtains the core network load context corresponding to the UE from the locally integrated core network user plane gateway according to the IP address and the TEID of the GTP tunnel that receives the uplink data that is included in the bearer setup request.
  • the core network-loaded context-related service flow and the Radio Access Bearer Identity (RAB) establish a correspondence.
  • RAB Radio Access Bearer Identity
  • the home base station gateway may establish a correspondence between the service flow and the wireless access bearer in the form of a corresponding relationship table; or may add a corresponding identifier of the wireless access in the service flow, and/or The wireless access device adds the identifier corresponding to the service flow to establish a correspondence between the service flow and the radio access bearer.
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the home base station gateway may further obtain a core network-based context from the locally integrated core network user plane gateway according to the bearer identifier and the IMSI included in the bearer setup request, and the core network 7 carries the context-corresponding service.
  • the flow and the RAB establish a correspondence.
  • the 7-digit identifier can also be a RAB ID or NSAPI.
  • the home base station gateway may obtain the IMSI from the bearer setup request; or, when the home base station gateway is the 3G home base station gateway, may also be in the pre-acquired user context. Get the IMSI, not here for each case - repeat.
  • the home base station gateway may first determine, according to the service offloading indication information, that the bearer is established by using the service offloading manner, and then allocate the user plane resource, and establish a relationship between the core network bearer and the RAB. Correspondence relationship.
  • the home base station gateway After the home base station gateway establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station gateway can be penetrated, and the subsequent user service data can be sent and received through the interface of the home base station gateway to the packet data network.
  • Step 306 The home base station gateway sends a bearer setup request to the home base station.
  • the home base station may be an HNB or an HeNB.
  • Step 307 The home base station allocates a user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 308 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 309 The home base station gateway allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes the IP address of the GTP tunnel that receives the downlink data allocated by the home base station gateway. And TEID.
  • Step 310 The core network mobility management entity sends an update bearer request to the core network user plane gateway, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station gateway.
  • Step 311 The core network user plane gateway sends an update bearer response to the core network mobility management entity as a response.
  • step 312 the core network mobility management entity sends a setup bearer accept message to the UE to notify the UE that the bearer setup is complete.
  • step 312 may also be performed during the air interface bearer establishment process of step 307, and details are not described herein.
  • the home base station gateway receives the downlink service flow sent by the packet data network, and may The corresponding relationship sends the downlink service flow to the UE by using a radio bearer.
  • the home base station gateway receives the uplink service flow sent by the UE through the radio access bearer, the uplink service flow of the UE may be sent to the packet data network without being forwarded by the core network according to the established correspondence.
  • the home base station gateway can establish a correspondence between the service flow related to the core network of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence relationship. It does not occupy the transmission resources of the access network to the core network and the processing bandwidth of the core network user plane, which saves the network resources occupied by the data transmission, and solves the problem of using the home access system architecture provided by the prior art for data transmission between the UE and the Internet. The problem of too much network resources increases the data transmission rate, which in turn improves the user's business experience.
  • the node with the service offload function is a home base station that integrates the core network user plane gateway; wherein, the home base station may be an HNB or a HeNB, and the core network user plane gateway may be a GGSN, or S-GW and P-GW.
  • a data transmission method includes:
  • Step 404 The core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes the IP address and TEID of the GTP tunnel that receives the uplink data allocated by the core network user plane gateway, and the service offload indication information, optionally
  • the bearer setup request may further include an IMSI.
  • the service offload indication information may be an IMSI.
  • Step 405 The home base station gateway forwards the bearer setup request to the home base station according to the service offload indication information included in the bearer setup request, without allocating user plane resources.
  • Step 406 The home base station allocates a user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • the home base station determines that the bearer is established by using the service offloading manner according to the service offloading indication information included in the bearer setup request. Then, according to the IP address and TEID of the GTP tunnel receiving the uplink data included in the bearer setup request, from the locally integrated core network user Obtaining a core network bearer context on the gateway, and carrying the service flow corresponding to the context of the core network
  • the RAB establishes a correspondence.
  • the home base station may establish a correspondence between the service flow and the wireless access 7 in the form of a correspondence table; or may add an identifier corresponding to the radio access bearer in the service flow, and/or in the wireless connection. Enter 7
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the home base station may further obtain the core network context from the locally integrated core network user plane gateway according to the bearer identifier and the IMSI included in the bearer setup request.
  • the bearer identifier may also be a RAB ID or an NS API.
  • the home base station After the home base station establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station can be penetrated, and the subsequent user service data can be sent and received through the interface of the home base station to the packet data network.
  • Step 407 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 408 The home base station gateway sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 409 The core network mobility management entity sends an update bearer request to the core network user plane gateway, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 410 The core network user plane gateway sends an update bearer response to the core network mobility management entity as a response.
  • step 411 the core network mobility management entity sends an establishment acceptance message to the UE.
  • the UE is notified that the bearer setup is complete.
  • the step 411 can also be performed in the air interface bearer establishment process in step 406, and details are not described herein.
  • the home base station can directly send the downlink service flow from the packet data network to the UE through the RAB, and pass the uplink service flow from the UE to the RAB. After receiving, it is directly forwarded to the packet data network.
  • the home base station can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources of the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network occupies too much network resources by using the home access system architecture provided by the prior art.
  • the problem is that the data transfer rate is increased, which in turn improves the user's business experience.
  • the node with the service offload function is a home base station gateway that integrates the core network user plane gateway; wherein the home base station gateway may be a 3G home base station gateway (Home NodeB Gateway), or a home evolved base station.
  • the home eNodeB Gateway, the core network user plane gateway can be a GGSN, or an S-GW and a P-GW.
  • a data transmission method includes:
  • Step 505 The home base station gateway allocates a user plane resource, and sends a bearer setup request to the home base station.
  • Step 506 The home base station allocates a user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 507 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 508 The home base station gateway allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes the IP address of the GTP tunnel that receives the downlink data allocated by the home base station gateway. And TEID.
  • Step 509 The core network mobility management entity sends an update bearer request to the core network user plane gateway, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station gateway.
  • the bearer request is updated. It can include service offload indication information.
  • Step 510 The core network user plane gateway acquires the RAB context from the locally integrated home base station gateway according to the IP address and TEID of the GTP tunnel that receives the downlink data allocated by the home base station gateway included in the update bearer request, and associates the RAB with the update bearer request.
  • the core network bears the corresponding service flow to establish a corresponding relationship.
  • the core network user plane gateway may establish a correspondence between the service flow and the wireless access in the form of a corresponding relationship table; or may add an identifier corresponding to the radio access bearer in the service flow, and/or The identifier corresponding to the service flow is added to the radio access port 7 to establish a correspondence between the service flow and the radio access bearer.
  • the correspondence between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the core network user plane gateway may further obtain an RAB context from the locally integrated home base station gateway according to the bearer identifier and the IMSI of the update bearer request, and establish a core according to the core network bearer context related to the update bearer request.
  • the network carries the correspondence between the context-related service flow and the RAB.
  • the bearer identifier may also be a RAB ID or an NSAPI.
  • the core network user plane gateway may first determine, according to the service offloading indication information, the bearer service service offload mode, and then establish a correspondence between the service flow and the RAB.
  • the core network user plane gateway Since the core network user plane gateway is integrated on the home base station gateway, after the core network user plane gateway establishes the correspondence between the UE service flow and the RAB, the uplink and downlink routes inside the home base station gateway can be penetrated, and the subsequent user service data can pass through the home.
  • the base station gateway sends and receives data to the interface of the packet data network.
  • Step 511 The core network user plane gateway sends an update bearer response to the core network mobility management entity as a response.
  • step 512 the core network mobility management entity sends a bearer acceptance message to the UE. Notify the UE.
  • the step 512 can also be performed in the air interface bearer establishment process of step 506, and details are not described herein.
  • the home base station gateway can directly send the downlink service flow from the packet data network to the UE through the RAB, and pass the uplink service flow from the UE. After receiving the RAB, the RAB forwards directly to the packet data network.
  • the home base station gateway can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources to the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network is occupied by the network access system architecture provided by the prior art. Many problems have increased the data transmission rate, which in turn improves the user's business experience.
  • the node with the service offload function is a home base station that integrates the core network user plane gateway; wherein, the home base station may be an HNB or a HeNB, and the core network user plane gateway may be a GGSN, or S-GW and P-GW.
  • a data transmission method includes:
  • Step 604 the core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes the IP address and TEID of the GTP tunnel that receives the uplink data allocated by the core network user plane gateway, and the service offload indication information, optionally
  • the bearer setup request may further include an IMSI.
  • the service offload indication information may be an IMSI.
  • Step 605 The home base station gateway forwards the bearer setup request to the home base station according to the service offload indication information included in the bearer setup request, without allocating user plane resources.
  • Step 606 The home base station allocates a user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 607 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes the assignment of the home base station The TP address and TETD of the GTP tunnel that receives the downlink data.
  • Step 608 The home base station gateway sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 609 The core network mobility management entity sends an update bearer request to the core network user plane gateway, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • the update bearer request may also be Contains service offload indication information.
  • Step 610 The core network user plane gateway acquires the RAB context from the locally integrated home base station according to the IP address and TEID of the GTP tunnel that receives the downlink data allocated by the home base station included in the update bearer request, and associates the RAB with the core that updates the bearer request.
  • the corresponding traffic flows of the network bearer establish a corresponding relationship.
  • the core network user plane gateway may establish a correspondence between the service flow and the wireless access 7 in the form of a corresponding relationship table; or may add an identifier corresponding to the radio access bearer in the service flow, and/or Add the identifier corresponding to the service flow in the radio access bearer, and establish the corresponding relationship between the service flow and the wireless access.
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the core network user plane gateway in step 610 may further obtain the RAB context from the locally integrated home base station according to the updated bearer request related bearer identifier and the IMSI, and associate the RAB corresponding to the RAB context with the update bearer request.
  • the core network bears the corresponding service flow to establish a corresponding relationship.
  • the bearer identifier may also be a RAB ID or an NSAPI.
  • the core network user plane gateway may first determine that the bearer is established by using the service offloading manner according to the service offloading indication information, and then establish a correspondence between the service flow and the RAB.
  • the core network user plane gateway Since the core network user plane gateway is integrated on the home base station, after the core network user plane gateway establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station can be penetrated, and the subsequent user service data can be accessed through the home base station. Packet data network interface for data collection hair.
  • Steps 611 and 612 are substantially the same as steps 511 and 512 shown in Fig. 5, and are not mentioned here.
  • the home base station can directly send the downlink service flow from the packet data network to the UE through the RAB, and pass the uplink service flow from the UE to the RAB. After receiving, it is directly forwarded to the packet data network.
  • the home base station can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources of the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network is occupied by the network access system architecture provided by the prior art. Many problems have increased the data transmission rate, which in turn improves the user's business experience.
  • the node with the service offload function is a home base station gateway integrated with the P-GW, and the node of the service offload function does not include the S-GW; wherein the home base station gateway can be a 3G home base station gateway (Home NodeB Gateway), or Home eNodeB Gateway.
  • the home base station gateway can be a 3G home base station gateway (Home NodeB Gateway), or Home eNodeB Gateway.
  • a data transmission method includes:
  • Step 701 The UE sends a setup bearer request to the mobility management entity.
  • the mobility management entity may be an SGSN or an MME or the like.
  • Step 702 The core network mobility management entity sends a create bearer request to the S-GW.
  • Step 703 The S-GW allocates a user plane resource, allocates an IP address and a TEID of the GTP tunnel that receives the uplink data, and sends a create bearer request to the P-GW, where the created bearer request includes the GTP tunnel that receives the uplink data allocated by the S-GW. IP address and TEID.
  • Step 704 The P-GW allocates an IP address to the created bearer, allocates an IP address and a TEID of the GTP tunnel that receives the uplink data, and sends a create bearer response to the S-GW, where the created bearer response includes the received uplink data allocated by the P-GW. IP address and TEID of the GTP tunnel.
  • the P-GW may send the TP address allocated for the bearer to the UE by using a separate message, or may include the IP address allocated for the bearer in the create bearer response, and details are not described herein.
  • Step 705 The S-GW sends a create bearer response to the core network mobility management entity, where the creation bearer response includes an IP address and a TEID of the GTP tunnel that receives the uplink data allocated by the S-GW and the P-GW.
  • Step 706 The core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes an IP address and a TEID of the GTP tunnel that receives the uplink data that is allocated by the P-GW.
  • the bearer setup request may further include The service offloading indication information and/or the IMSI. Further, the service offloading indication information may be an IMSI.
  • Step 707 The home base station gateway allocates a user plane resource, and obtains a core network bearer context from the local integrated P-GW according to the bearer establishment request, including the IP address and TEID of the GTP tunnel that receives the uplink data allocated by the P-GW, and the core
  • the service flow corresponding to the network bearer context is associated with the Radio Access Bearer Identity (RAB).
  • RAB Radio Access Bearer Identity
  • the home base station gateway may establish a correspondence between the service flow and the wireless access bearer in the form of a corresponding relationship table; or may add a corresponding identifier of the wireless access in the service flow, and/or The wireless access device adds the identifier corresponding to the service flow to establish a correspondence between the service flow and the radio access bearer.
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the home base station gateway in step 707 may further obtain the core network bearer context from the locally integrated P-GW according to the bearer identifier and the obtained IMSI included in the bearer setup request, and the core network bears the context corresponding service flow.
  • the bearer identifier may also be a RAB ID or an NSAPI.
  • the home base station gateway may obtain the IMSI from the bearer setup request; or, when the home base station gateway is the 3G home base station gateway, may also be in the pre-acquired user context. Get the IMSI, not here for each case - repeat.
  • the home base station gateway may first determine that the bearer is established by using the service offloading manner according to the service offloading indication information, and then allocate the user plane resource, and establish a correspondence between the service flow and the RAB. relationship.
  • the home base station gateway After the home base station gateway establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station gateway can be penetrated, and the subsequent user service data can be sent and received through the interface of the home base station gateway to the packet data network.
  • Step 708 The home base station gateway sends a bearer setup request to the home base station.
  • the home base station may be an HNB or an HeNB.
  • Step 709 The home base station allocates user plane resources according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 710 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 711 The home base station gateway allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes the IP address of the GTP tunnel that receives the downlink data allocated by the home base station gateway. And TEID.
  • Step 712 The core network mobility management entity sends an update bearer request to the S-GW, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station gateway.
  • Step 713 The S-GW sends an update bearer response to the core network mobility management entity as a response.
  • the core network mobility management entity sends a setup bearer accept message to the UE to notify the UE.
  • the step 714 is also performed in the air interface bearer establishment process in step 709, and details are not described herein.
  • the home base station gateway can directly send the downlink service flow from the packet data network to the RAB through the RAB.
  • the UE forwards the uplink service flow from the UE to the packet data network after receiving the RAB.
  • the home base station gateway can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources to the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network is occupied by the network access system architecture provided by the prior art. Many problems have increased the data transmission rate, which in turn improves the user's business experience.
  • the node having the service offload function is a home base station integrated with the P-GW, and the node of the service offload function does not include the S-GW; wherein the home base station may be an HNB or an HeNB.
  • a data transmission method includes:
  • Steps 801-805 are basically the same as steps 701-705 shown in FIG. 7, and are not described herein.
  • Step 806 The core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes an IP address and a TEID of the GTP tunnel received by the P-GW to receive uplink data, and service offload indication information, optionally,
  • the bearer setup request may further include an IMSI.
  • the service offload indication information may be an IMSI.
  • Step 807 The home base station gateway forwards the bearer setup request to the home base station according to the service offload indication information included in the bearer setup request, without allocating user plane resources.
  • Step 808 The home base station allocates the user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE. Meanwhile, the home base station determines that the bearer is established by using the service offloading manner according to the service offloading indication information included in the bearer setup request. Then, according to the IP address and TEID of the GTP tunnel that receives the uplink data allocated by the P-GW included in the bearer setup request, the core network is obtained from the locally integrated P-GW, and the core network is context-corresponding. The service flow and the RAB establish a correspondence.
  • the home base station may establish a correspondence between the service flow and the radio access bearer in the form of a correspondence relationship table, or may add an identifier corresponding to the radio access bearer in the service flow, and/or in the radio access. 7 Add the form of the identifier corresponding to the service flow to establish service flow and wireless access.
  • the corresponding relationship of the bearer may be established by other methods, and details are not described herein.
  • the home base station may further obtain the core network bearer context from the locally integrated P-GW according to the 7-package identifier and the IMSI included in the 7-layer setup request.
  • the service flow corresponding to the core network bearer context and the RAB establish a corresponding relationship.
  • the bearer identifier can also be a RAB ID or an NSAPI.
  • the home base station After the home base station establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station can be penetrated, and the subsequent user service data can be sent and received through the interface of the home base station to the packet data network.
  • Step 809 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 810 The home base station gateway sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 811 The core network mobility management entity sends an update bearer request to the S-GW, where the update bearer request includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 812 The S-GW sends an update bearer response to the core network mobility management entity as a response.
  • the core network mobility management entity sends a setup bearer accept message to the UE to notify the UE.
  • the step 813 may also be performed in the air interface bearer establishment process of step 808, and details are not described herein.
  • the home base station can directly send the downlink service flow from the packet data network to the UE through the RAB, and receive the uplink service flow from the UE through the RAB. It is then forwarded directly to the packet data network.
  • the home base station can establish a correspondence between the service flow of the UE and the RAB, and perform data transmission between the UE and the packet data network according to the correspondence relationship.
  • Direct forwarding does not occupy the transmission resources of the access network to the core network and the processing bandwidth of the core network user plane, saves the network resources occupied by the data transmission, and solves the UE and packet data network using the home access system architecture provided by the prior art. The problem of excessive data resources between data transfers.
  • the node with the service offload function is a home base station gateway integrated with the P-GW, and the node of the service offload function does not include the S-GW; wherein the home base station gateway can be a 3G home base station gateway (Home NodeB Gateway), or Home eNodeB Gateway.
  • the home base station gateway can be a 3G home base station gateway (Home NodeB Gateway), or Home eNodeB Gateway.
  • a data transmission method includes:
  • Steps 901-906 are substantially the same as steps 701-706 shown in FIG. 7, and are not described herein again.
  • Step 907 The home base station gateway allocates a user plane resource, and sends a bearer setup request to the home base station.
  • Step 908 The home base station allocates user plane resources according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 909 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 910 The home base station gateway allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes the IP address of the GTP tunnel that receives the downlink data allocated by the home base station gateway. And TEID.
  • Step 911 The core network mobility management entity sends an update bearer request to the S-GW, where the update bearer request includes the IP address and TEID of the GTP tunnel and the service offloading indication information of the GTP tunnel that is received by the home base station gateway.
  • Step 912 The S-GW forwards the update bearer request to the P-GW according to the service offloading indication information included in the update bearer request.
  • Step 913 The P-GW determines, according to the service offloading indication information, that the bearer is established by using the service offloading manner, and according to the IP address and TEID of the GTP tunnel that receives the downlink data allocated by the home base station gateway included in the update bearer request, from the locally integrated home base station. Get the RAB context on the gateway, The RAB and the update 7 are associated with the service flow corresponding to the core network 7
  • the P-GW may establish a correspondence between the service flow and the wireless access 7 in the form of a correspondence table; or may add an identifier corresponding to the radio access bearer in the service flow, and/or in the wireless Add the identity of the service flow corresponding to the traffic load in the 7-load, and establish the corresponding relationship between the service flow and the wireless access bearer.
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the P-GW may further obtain the RAB context from the locally integrated home base station gateway according to the bearer identifier and the IMSI of the update bearer request, and the RAB and the core network 7 associated with the update bearer request are correspondingly carried.
  • the business flow establishes a correspondence.
  • the 7-digit identifier can also be a RAB ID or NSAPI.
  • the P-GW Since the P-GW is integrated on the home base station gateway, after the P-GW establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station gateway can be penetrated, and the subsequent user service data can be sent to the group through the home base station gateway.
  • the interface of the data network performs data transmission and reception.
  • Step 914 The P-GW sends an update bearer response to the S-GW as a response.
  • Step 915 The S-GW sends an update bearer response to the core network mobility management entity as a response.
  • the core network mobility management entity sends a setup bearer accept message to the UE to notify the UE.
  • the step 916 may also be performed during the air interface establishment process of step 908, and details are not described herein.
  • the home base station gateway can directly send the downlink service flow from the packet data network to the UE through the RAB, and pass the uplink service flow from the UE. After receiving the RAB, the RAB forwards directly to the packet data network.
  • the home base station gateway can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources to the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network is occupied by the network access system architecture provided by the prior art. Many questions, Increased data transfer rates, which in turn improve the user's business experience.
  • the node with the service offload function is a home base station integrated with the P-GW, and the node of the service offload function does not include the S-GW; the home base station may be an HNB or a HeNB.
  • a data transmission method includes:
  • Step 1006 The core network mobility management entity sends a bearer setup request to the home base station gateway, where the bearer setup request includes an IP address and a TEID of the GTP tunnel that receives the uplink data that is allocated by the P-GW, and the service offload indication information, optionally,
  • the bearer setup request may further include an IMSI.
  • the service offload indication information may be an IMSI.
  • Step 1007 The home base station gateway forwards the bearer setup request to the home base station according to the service offload indication information included in the bearer setup request, without allocating user plane resources.
  • Step 1008 The home base station allocates a user plane resource according to the received bearer setup request content, and initiates a process of establishing an air interface bearer with the UE.
  • Step 1009 The home base station allocates an IP address and a TEID of the GTP tunnel that receives the downlink data, and sends a bearer setup response to the home base station gateway, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 1010 The home base station gateway sends a bearer setup response to the core network mobility management entity, where the bearer setup response includes an IP address and a TEID of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 1011 The core network mobility management entity sends an update bearer request to the S-GW, where the update bearer request includes an IP address, a TEID, and a service offloading indication information of the GTP tunnel that receives the downlink data allocated by the home base station.
  • Step 1012 The S-GW forwards the update bearer request to the P-GW according to the service offload indication information included in the update bearer request.
  • Step 1013 The P-GW determines, according to the service offloading indication information, that the bearer adopts a service offloading manner. And establishing, according to the IP address and TEID of the GTP tunnel that receives the downlink data allocated by the home base station that is included in the update bearer request, acquiring the RAB context from the locally integrated home base station, and corresponding to the core network bearer associated with the update bearer request. The business flow establishes a correspondence.
  • P-GW may be established in the form of a correspondence table of correspondence relationship between the traffic flow and the radio access carrier 7; may be added to the wireless access service stream identifier corresponding to the carrier, and / or wireless The access identifier is added to the identifier corresponding to the service flow, and the correspondence between the service flow and the wireless access is established.
  • the corresponding relationship between the service flow and the radio access bearer may be established by other methods, and details are not described herein.
  • the P-GW may also obtain the RAB context from the locally integrated home base station according to the 7-load identifier and the IMSI related to the update request, and the core network bearer associated with the RAB and the update request. Corresponding relationship is established for the corresponding service flow.
  • the bearer identifier can also be a RAB ID or an NSAPI.
  • the P-GW Since the P-GW is integrated on the home base station, after the P-GW establishes the correspondence between the service flow of the UE and the RAB, the uplink and downlink routes inside the home base station can be penetrated, and the subsequent user service data can pass through the home base station to the packet data network.
  • the interface performs data transmission and reception.
  • Steps 1014-1016 are substantially the same as steps 914-916 shown in FIG. 9, and are not described herein again.
  • the home base station can directly send the downlink service flow from the packet data network to the UE through the RAB, and pass the uplink service flow from the UE to the RAB. After receiving, it is directly forwarded to the packet data network.
  • the home base station can establish a correspondence between the service flow of the UE and the RAB, and directly forward the data transmitted between the UE and the packet data network according to the correspondence, without occupying the access network.
  • the transmission resources of the core network and the processing bandwidth of the core network user plane save the network resources occupied by the data transmission, and solve the problem that the data transmission between the UE and the packet data network occupies too much network resources by using the home access system architecture provided by the prior art.
  • the problem is that the data transfer rate is increased, which in turn improves the user's business experience.
  • the embodiment of the present invention further provides a node with a service offload function, including:
  • the establishing unit 1101 is configured to establish a correspondence between the service flow of the user equipment and the radio access, and the transmission unit 1102 is configured to: according to the correspondence between the service flow established by the establishing unit 1101 and the radio access bearer, The service flow of the received packet data network is directly sent to the user equipment by using a radio access bearer; or
  • the service flow of the user equipment received through the radio access bearer is directly forwarded to the packet data network.
  • the establishing unit 1101 may include:
  • the first receiving subunit 1201 is configured to receive a bearer setup request, where the bearer setup request includes an IP address of the GTP tunnel receiving the uplink data and a tunnel end identifier TEID;
  • the first obtaining sub-unit 1202 is configured to obtain, according to the IP address and the TEID of the GTP tunnel that receives the uplink data that is acquired by the first receiving sub-unit 1201, the core corresponding to the user equipment from the locally integrated core network user plane gateway.
  • Network bearer context ;
  • the first establishing sub-unit 1203 is configured to establish a correspondence between a core network bearer context-related service flow and a radio access bearer acquired by the first acquiring sub-unit 1202.
  • the establishing unit 1101 may include:
  • the second receiving subunit 1204 is configured to receive a bearer setup request.
  • the second obtaining sub-unit 1205 is configured to obtain, according to the bearer identifier included in the bearer setup request received by the second receiving sub-unit 1204, and the pre-acquired IMSI, locally acquiring the core network corresponding to the user equipment;
  • the second establishing sub-unit 1206 is configured to establish a correspondence between the core network bearer context-related service flow and the radio access bearer acquired by the second obtaining sub-unit 1205.
  • the establishing unit 1101 may include:
  • the third receiving subunit 1207 is configured to receive an update bearer request, where the update bearer request includes an IP address of the GTP tunnel receiving the downlink data and a tunnel end identifier TEID;
  • the third obtaining sub-unit 1208 is configured to acquire, according to the IP address and the TEID of the GTP tunnel that receives the downlink data that is acquired by the third receiving sub-unit 1207, the wireless device corresponding to the user equipment. Access 7
  • the third establishing sub-unit 1209 is configured to establish a correspondence between the radio access bearer acquired by the third obtaining sub-unit 1208 and the core network 7 that is related to the update request.
  • the establishing unit 1101 may include:
  • the fourth receiving subunit 1210 is configured to receive an update bearer request.
  • the fourth obtaining sub-unit 1211 is configured to obtain the radio access bearer context corresponding to the user equipment according to the bearer identifier and IMSI related to the update bearer request received by the fourth receiving sub-unit 1210.
  • the fourth establishing sub-unit 1212 is configured to establish a correspondence between the radio access bearer acquired by the fourth obtaining sub-unit 1211 and the service flow corresponding to the core network bearer associated with the update bearer request.
  • the establishing unit 1101 may further include:
  • the first determining unit 1213 is configured to: when the bearer setup request received by the first receiving subunit 1201 or the second receiving subunit 1204 further includes the service offloading indication information, determine, according to the offloading indication information, that the bearer adopts a service offloading manner Establishing, indicating that the first establishing subunit 1203 or the second establishing subunit 1206 establishes a correspondence between the service flow and the radio access bearer; and/or, the second determining unit 1214 is configured to be used as the first When the update bearer request received by the third receiving subunit 1207 or the fourth receiving subunit 1210 further includes the service offloading indication information, determining, according to the offloading indication information, that the bearer service splitting mode is established, indicating the third establishing subunit 1209 Or the fourth establishing subunit 1212 establishes a correspondence between the service flow and the radio access bearer.
  • the node with the service offload function shown in FIG. 11 and FIG. 12 above may be a home base station or a home base station gateway that integrates a core network user plane gateway; the user plane gateway is an SGSN, a P-GW, or a P. -GW and S-GW, etc.
  • the node with the service offloading function provided by the embodiment of the present invention can establish a correspondence between the service flow of the user equipment and the radio access bearer, and the user equipment and the packet data according to the corresponding relationship.
  • the data transmitted between the networks is directly forwarded, and the transmission resources of the access network to the core network and the processing bandwidth of the core network user plane are not occupied, which saves the network resources occupied by the data transmission, and solves the home access system provided by the prior art.
  • the architecture carries out the problem that the data transmission between the UE and the packet data network occupies too much network resources, improves the data transmission rate, and improves the user experience.
  • the embodiment of the present invention further provides a communication system, including: a node with a service offload function, configured to establish a correspondence between a service flow of a user equipment and a radio access bearer, according to a correspondence between the service flow and a radio access bearer. Transmitting, by the wireless access bearer, the service flow of the received packet data network to the user equipment; or
  • the service flow of the user equipment received through the radio access bearer is directly forwarded to the packet data network.
  • the node with the service offload function can associate the service flow of the user equipment with the radio access bearer, and directly directly transmit the data transmitted between the user equipment and the packet data network according to the correspondence relationship. Forwarding, does not occupy the transmission resources of the access network to the core network and the processing bandwidth of the core network user plane, saves the network resources occupied by the data transmission, and solves the problem of using the home access system architecture provided by the prior art for the UE and the packet data network. Inter-data transmission occupies too much network resources, improves the data transmission rate, and thus improves the user's service experience.
  • the data transmission method, device and communication system provided by the embodiments of the present invention can be applied to a home access system or a general macro network such as 3G or LTE.
  • the home base station corresponds to a common 3G base station (NodeB), or an evolved base station (eNodB) of an evolved network such as LTE.
  • the home base station gateway corresponds to a base station controller or a 3G Radio Network Controller (RNC). It can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium such as a ROM/RAM, a magnetic disk or an optical disk.

Landscapes

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

Description

数据传输方法、 装置和通信系统
本申请要求了 2009年 8月 7日提交的、 申请号为 200910166406.6、 发明 名称为 "数据传输方法、 装置和通信系统" 的中国申请的优先权， 其全部内 容通过引用结合在本申请中。 技术领域
本发明涉及通信领域， 尤其涉及一种数据传输方法、 装置和通信系统。 背景技术
在家庭接入系统架构中， 用户设备（ User Equipment, UE )可以通过家庭 无线接入点接入移动网络， 并通过移动网络与分组数据网络进行通信。 例如 根据使用的频谱不同， 家庭无线接入点可以为： 3G家庭基站（Home NodeB, HNB )、 家庭演进基站（Home evolved NodeB, HeNB )或者家庭非 3GPP无 线接入点 （ Home non-3 GPP Wireless Access Point, Home non-3GPP WAP ); HNB、 HeNB和 Home non-3GPP WAP分别通过通用 IP接入网络与 3G家庭基 站网关、 家庭演进基站网关和家庭非 3GPP无线接入点网关相连， 通过 3G家 庭基站网关、家庭演进基站网关和家庭非 3GPP无线接入点网关连接到移动网 络。
使用家庭接入系统架构进行 UE与分组数据网络之间的数据传输时，数据 需要经过多个网元进行传输， 例如： UE通过 HNB接入网络以后， 所述 HNB 将 UE发送的数据通过通用 IP接入网络传输到 3G家庭基站网关， 3G家庭基 站网关将所述数据通过 SGSN和 GGSN传输到分组数据网络， 采用这种数据 传输方法， 数据传输的路径较长， 数据经过的网元均需要为其分配传输资源， 使得数据传输占用的网络资源较多。 发明内容
本发明实施例提供一种数据传输方法、 装置和通信系统， 能够节省数据 传输占用的网络资源， 提高传输效率。 本发明的实施例采用如下技术方案：
一种数据传输方法， 包括： 具有业务分流功能的节点建立用户设备的业 务流和无线接入承载的对应关系； 所述具有业务分流功能的节点根据所述对 应关系 , 将接收到的分组数据网络的业务流直接通过无线接入承载发送给所 述用户设备； 或者， 将通过无线接入承载接收到的所述用户设备的业务流直 接转发给所述分组数据网络。
一种具有业务分流功能的节点， 包括：
建立单元， 用于建立用户设备的业务流和无线接入承载的对应关系； 传输单元， 用于根据所述建立单元建立的业务流和无线接入承载的对应 关系， 将接收到的分组数据网络的业务流直接通过无线接入承载发送给所述 用户设备； 或者， 将通过无线接入承载接收到的所述用户设备的业务流直接 转发给所述分组数据网络。
一种通信系统， 包括： 业务分流装置， 用于将用户设备的业务流和无线 接入承载建立对应关系 , 根据所述业务流和无线接入承载的对应关系将接收 到的分组数据网络的业务流直接通过无线接入承载发送给所述用户设备； 或 者， 将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分 組数据网络。 附图说明 目 、、 ^ 、 、 、 、 ， 、、 施例或现有技术描述中所需要使用的附图作筒单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例 , 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为现有技术提供的家庭接入系统架构示意图；
图 2为本发明实施例提供的数据传输方法流程图；
图 3为本发明另一实施例提供的数据传输方法时序图；
图 4为本发明又一实施例提供的数据传输方法时序图； 图 5为本发明再一实施例提供的数据传输方法时序图；
图 6为本发明再一实施例提供的数据传输方法时序图；
图 7为本发明再一实施例提供的数据传输方法时序图；
图 8为本发明再一实施例提供的数据传输方法时序图；
图 9为本发明再一实施例提供的数据传输方法时序图；
图 10为本发明再一实施例提供的数据传输方法时序图；
图 11为本发明实施例提供的数据卸载装置结构示意图；
图 12为图 11所示的本发明实施例提供的数据卸载装置中建立单元的结 构示意图。 具体实施方式
下面将结合本发明实施例中的附图 , 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
如图 1所示， 移动网络中的网元可以包括： 演进的 UMTS陆地无线接入 网 （Evolved UMTS Territorial Radio Access Network, E-UTRAN ) 中的移动性 管理实体（ Mobility Management Entity, MME )、 传统核心网中的服务 GPRS 支持节点（ Serving GPRS Supporting Node, SGSN )、传统核心网中的网关 GPRS 支持节点（ Gateway GPRS Supporting Node, GGSN )、 演进核心网中的月良务网 关 （Serving Gateway, S-GW )、 演进核心网中的分组数据网关 （Packet Data Network Gateway, P-GW )、 non-3GPP网络中包括多种实现实体的非 3GPP网 关 （non-3GPP GW )、 归属用户服务器（ Home Subscriber Server, HSS ) 以及 认证、 4受权与计费月良务器 ( Authentication Authorization and Accounting Server, AAA Server )等。
为了解决采用现有技术提供的家庭接入系统架构进行用户设备与分组数 据网络之间数据传输占用网络资源过多的问题， 本发明实施例提供一种数据 传输方法、 装置和通信系统。
如图 2所示， 本发明实施例提供的数据传输方法， 包括：
步驟 201， 具有业务分流功能的节点建立 UE的业务流和无线接入承载的 对应关系；
步驟 202,具有业务分流功能的节点 4 据业务流和无线接入 载的对应关 系， 将来自分组数据网络的下行业务流直接通过无线接入承载发送给 UE; 或 者， 将通过无线接入承载接收到的 UE 的上行业务流直接转发给分组数据网 络。
在本实施例中， 分组数据网络可以是因特网或企业网等； 具有业务分流 功能的节点可以为集成核心网用户面网关的家庭基站或者家庭基站网关， 其 中， 所述用户面网关为 SGSN, 或者 P-GW, 或者 P-GW和 S-GW; 所述家庭 基站可以为 HNB、 HeNB、 NodeB或者 eNodeB等； 所述家庭基站网关为 3G 家庭基站网关， 或者家庭演进基站网关， 或者基站控制器， 或者无线网络控 制器等。
进一步地， 在本实施例中， 步骤 201 具体可以通过以下任意一种方法建 立 UE的业务流和无线接入 7|载的对应关系：
1、 具有业务分流功能的节点接收承载建立请求， 该承载建立请求包含接 收上行数据的通用无线分组业务隧道协议 ( GPRS Tunnelling Protocol, GTP ) 隧道的 IP地址和隧道端点标识 ( Tunnel Endpoint Identifier, TEID ); 具有业务 分流功能的节点根据接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地获 取 UE对应的核心网 载上下文，并将与该核心网 载上下文相关的业务流和 无线接入 载建立对应关系。
在本实施例中， UE的业务流和无线接入 7|载的对应关系可以是 UE的业 务流和无线接入承载的映射关系， 进一步的， 该映射关系表可以是一个映射 关系表， 也可以是其他的表现形式， 如：
UE1的业务流 A……无线接入 7 载 a; UE2的业务流 B……无线接入承载 b;
UE的业务流和无线接入 7|载的对应关系也可以是在 UE的业务流中添加 所对应的无线接入 7 载的标识，也可以是无线接入 7 载中添加所对应的 UE的 业务流的标识， 也可以是在 UE 的业务流中添加所对应的无线接入 载的标 识 , 同时在无线接入 载中添加所对应的 UE的业务流的标识。
具有业务分流功能的节点还可以通过其他方法建立业务流和无线接入承 载的对应关系， 此处不作赘述。
在其他实施例中，对 UE的业务流和无线接入 7 载的对应关系也可以参照 此处的描述。
可选地， 承载建立请求中还可以包含业务分流指示信息， 具有业务分流 功能的节点根据业务分流指示信息确定承载采用业务分流方式建立之后 , 根 据接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地获取 UE对应的核心 网承载上下文 , 并将该核心网承载上下文相关的业务流和无线接入承载建立 对应关系。
2、 具有业务分流功能的节点接收承载建立请求； 其中， 该承载请求中可 以包含承载标识， 具有业务分流功能的节点根据该承载建立请求包含的承载 标识和获取的用户身份标识 ( international mobile subscriber identity, IMSI ), 从本地获取 UE对应的核心网承载上下文，并将核心网承载上下文相关的业务 流和无线接入 7 载建立对应关系。
具有业务分流功能的节点也可以根据获取的 IMSI, 从本地获取 UE对应 的核心网 7 载上下文， 并将核心网 7 载上下文相关的业务流和无线接入 载 建立对应关系。
在本实施例中 , 载标识还可以为无线接入 7 载标识（ Radio Access Bearer Identity, RAB ID ), 或者网络业务接入点标识 （Net Service Access Point Identity, 等。 在本实施例中， 具有业务分流功能的节点可以从用户上下文（3G 家庭基 站网关业务分流场景） 中获取 UE的 IMSI; 或者， 当承载建立请求包含 IMSI 时， 具有业务分流功能的节点也可以从该承载建立请求中获取 UE的 IMSI。
可选地， 承载建立请求还可以包含业务分流指示信息， 具有业务分流功 能的节点根据业务分流指示信息确定承载采用业务分流方式建立之后， 根据 IMSI和承载标识 , 从本地获取 UE对应的核心网承载上下文 , 并将该核心网 承载上下文相关的业务流和无线接入承载建立对应关系， 进一步地， 当承载 建立请求中包含 IMSI时 , 该 IMSI作为业务分流指示信息。
3、 具有业务分流功能的节点接收更新承载请求， 该更新承载请求包含接 收下行数据的 GTP隧道的 IP地址和 TEID; 具有业务分流功能的节点根据接 收下行数据的 GTP隧道的 IP地址和 TEID, 从本地获取 UE对应的无线接入 7|载上下文 , 并将该无线接入 7|载和更新 7|载请求相关的核心网 7|载上下文 相关的业务流建立对应关系，其中，所述核心网 载上下文为与 UE对应的核 心网 7|载上下文。
可选地， 更新承载请求还可以包含业务分流指示信息， 具有业务分流功 能的节点根据业务分流指示信息确定承载采用业务分流方式建立之后， 根据 接收下行数据的 GTP隧道的 IP地址和 TEID, 从本地获取 UE对应的无线接 入 7 载上下文， 并将该无线接入 7 载和更新 7 载请求关联的核心网 7 载上下 文所对应的业务流建立对应关系。
4、 具有业务分流功能的节点接收更新承载请求； 其中， 该更新承载请求 中可以包含承载标识， 具有业务分流功能的节点根据更新承载请求相关的承 载标识和 IMSI, 从本地获取 UE对应的无线接入 7 载上下文， 并将该无线接 入承载和更新承载请求关联的核心网承载上下文所对应的业务流建立对应关 系。 在本实施例中 , 承载标识还可以为 RAB ID或者 NSAPI等， 所述核心网 承载上下文为与 UE对应的核心网承载上下文。
具有业务分流功能的节点也可以根据获取的 IMSI, 从本地获取 UE对应 的核心网 7|载上下文， 并将核心网 7|载上下文相关的业务流和无线接入 7|载 建立对应关系。
可选地， 更新承载请求还可以包含业务分流指示信息， 具有业务分流功 能的节点根据业务分流指示信息确定承载采用业务分流方式建立之后 , 根据
IMSI和承载标识从本地获取 UE对应的无线接入承载上下文 , 并将该无线接 入承载和更新承载请求关联的核心网承载上下文所对应的业务流建立对应关 系。
本发明实施例提供的数据传输方法， 具有业务分流功能的节点能够将 UE 的业务流和无线接入承载建立对应关系 ,并根据该对应关系将 UE与分组数据 网络之间传输的数据进行直接转发， 不占用接入网到核心网的传输资源以及 核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了采用现有 技术提供的家庭接入系统架构进行 UE 与分组数据网之间数据传输占用网络 资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
为了使本领域技术人员能够更清楚地理解本发明实施例提供的技术方 明。
在本发明提供的另一实施例中， 具有业务分流功能的节点为集成核心网 用户面网关的家庭基站网关； 其中， 家庭基站网关可以为 3G 家庭基站网关 ( Home NodeB Gateway )， 或者家庭演进基站网关（ Home eNodeB Gateway ), 核心网用户面网关可以为 GGSN, 或者 S-GW和 P-GW。
如图 3所示， 本发明另一实施例提供的数据传输方法， 包括：
步驟 301 , UE向核心网移动性管理实体发送建立承载请求。
在本实施例中 , 移动性管理实体可以为 SGSN或者 MME等。
步骤 302, 核心网移动性管理实体向核心网用户面网关发送创建承载请 求。
步骤 303, 核心网用户面网关为该 UE创建^ ^载， 并为创建的^^载分配 IP 地址， 分配接收上行数据的 GTP隧道的 TP地址和 TETD, 向核心网移动性管 理实体发送创建承载响应 , 该创建承载响应中包含接收上行数据的 GTP隧道 的 IP地址和 TEID。
在本实施例中， 核心网用户面网关可以通过一条独立的消息将为^^载分 配的 IP地址发送给 UE, 也可以将为承载分配的 IP地址包含在创建承载响应 中发送给 UE, 此处不作赘述。
步驟 304, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该 承载建立请求包含核心网用户面网关分配的接收上行数据的 GTP隧道的 IP地 址和 TEID; 可选地， 承载建立请求还可以包含业务分流指示信息和 /或 IMSI, 进一步地， 所述业务分流指示信息可以为 IMSI。
步驟 305, 家庭基站网关分配用户面资源， 根据承载建立请求包含的接收 上行数据的 GTP隧道的 IP地址和 TEID, 从本地集成的核心网用户面网关上 获取 UE对应的核心网 载上下文，将该核心网 载上下文相关的业务流和无 线接入 7 载（Radio Access Bearer Identity, RAB )建立对应关系。
在本实施例中， 家庭基站网关可以以对应关系表的形式建立业务流和无 线接入 载的对应关系； 也可以以在业务流中添加无线接入 7|载对应的标识 , 和 /或在无线接入 ^^载中添加业务流对应的标识的形式， 建立业务流和无线接 入承载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立 业务流和无线接入承载的对应关系， 此处不作赘述。
可选地， 步驟 305 中家庭基站网关还可以根据承载建立请求中包含的承 载标识和 IMSI, 从本地集成的核心网用户面网关上获取核心网 载上下文， 将该核心网 7 载上下文对应的业务流和 RAB建立对应关系。 其中， 7 载标识 还可以为 RAB ID或者 NSAPI等。在本实施例中，当承载建立请求中包含 IMSI 时， 家庭基站网关可以从该承载建立请求中获取 IMSI; 或者， 当家庭基站网 关为 3G家庭基站网关时， 也可以从预先获取的用户上下文中获取 IMSI, 此 处不对每种情况进行——赘述。 可选地， 如果承载建立请求中包含业务分流指示信息， 家庭基站网关可 以先根据该业务分流指示信息确定承载采用业务分流方式建立， 然后， 再分 配用户面资源， 建立核心网承载和 RAB之间对应关系。
当家庭基站网关将 UE的业务流和 RAB建立对应关系以后， 家庭基站网 关内部的上下行路由得以贯通， 后续用户业务数据可以通过家庭基站网关到 分组数据网的接口进行数据收发。
步驟 306, 家庭基站网关向家庭基站发送承载建立请求。
在本实施例中 , 家庭基站可以为 HNB或者 HeNB。
步驟 307 , 家庭基站根据接收到的承载建立请求内容分配用户面资源，发 起和 UE建立空口承载的过程。
步驟 308, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应， 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 309,家庭基站网关分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向核心网移动性管理实体发送承载建立响应， 该承载建立响应包含家庭基站 网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步骤 310, 核心网移动性管理实体向核心网用户面网关发送更新承载请 求， 该更新承载请求中包含家庭基站网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 311 ,核心网用户面网关向核心网移动性管理实体发送更新承载响应 作为应答。
可选地， 步驟 312, 核心网移动性管理实体向 UE发送建立承载接受消息 通知 UE承载建立完成。在本实施例中， 步驟 312也可以在步驟 307的空口承 载建立过程中执行， 此处不做赘述。
进一步的， 通过以上如图 3所示的流程， 将 UE的业务流与 RAB建立对 应关系以后， 家庭基站网关接收分组数据网络发送的下行业务流， 可以根据 所述对应关系将所述下行业务流通过无线承载发送给 UE。 或者 , 家庭基站网关接收 UE通过无线接入承载发送的上行业务流时，可以根据 建立的对应关系，获取该 UE的上行业务流不需要通过核心网承载转发， 直接 发送给分组数据网络。 本发明的其他实施例中的对应地方 , 也可以参照本发 明实施例的描述。
本发明实施例提供的数据传输方法，家庭基站网关能够将 UE的核心网承 载相关的业务流和 RAB建立对应关系， 并根据该对应关系将 UE与分组数据 网络之间传输的数据进行直接转发， 不占用接入网到核心网的传输资源以及 核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了采用现有 技术提供的家庭接入系统架构进行 UE 与因特网之间数据传输占用网络资源 过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
在本发明实施例提供的又一实施例中 , 具有业务分流功能的节点为集成 核心网用户面网关的家庭基站； 其中 , 家庭基站可以为 HNB或者 HeNB , 核 心网用户面网关可以为 GGSN, 或者 S-GW和 P-GW。
如图 4所示， 本发明又一实施例提供的数据传输方法， 包括：
步驟 401-403与如图 3所示的步驟 301-303基本相同， 此处不再赘述。 步骤 404, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该 承载建立请求包含核心网用户面网关分配的接收上行数据的 GTP隧道的 IP地 址和 TEID,以及业务分流指示信息，可选地，承载建立请求还可以包含 IMSI, 进一步地， 所述业务分流指示信息可以为 IMSI。
步驟 405, 家庭基站网关根据承载建立请求中包含的业务分流指示信息， 不分配用户面资源， 向家庭基站转发所述承载建立请求。
步驟 406, 家庭基站根据接收到的承载建立请求内容分配用户面资源 ,发 起和 UE建立空口承载的过程； 同时 , 家庭基站根据承载建立请求中包含的业 务分流指示信息确定承载采用业务分流方式建立， 然后根据承载建立请求包 含的接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地集成的核心网用户 面网关上获取核心网承载上下文， 将该核心网承载上下文对应的业务流和
RAB建立对应关系。
在本实施例中， 家庭基站可以以对应关系表的形式建立业务流和无线接 入7 载的对应关系； 也可以以在业务流中添加无线接入承载对应的标识， 和 / 或在无线接入 7| ^载中添加业务流对应的标识的形式， 建立业务流和无线接入 载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立业 务流和无线接入承载的对应关系， 此处不作赘述。
可选地， 当承载建立请求中包含 IMSI时， 步驟 406中家庭基站还可以根 据承载建立请求中包含的承载标识和 IMSI, 从本地集成的核心网用户面网关 上获取核心网^^载上下文， 将该核心网^ ^载上下文相关的业务流和 RAB建立 对应关系。 其中， 承载标识还可以为 RAB ID或者 NS API等。
当家庭基站将 UE的业务流和 RAB建立对应关系以后 , 家庭基站内部的 上下行路由得以贯通， 后续用户业务数据可以通过家庭基站到分组数据网络 的接口进行数据收发。
步骤 407, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应 , 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 408, 家庭基站网关向核心网移动性管理实体发送承载建立响应， 该 承载建立响应包含家庭基站分配的接收下行数据的 GTP 隧道的 IP 地址和 TEID。
步驟 409, 核心网移动性管理实体向核心网用户面网关发送更新承载请 求，该更新承载请求中包含家庭基站分配的接收下行数据的 GTP隧道的 IP地 址和 TEID。
步骤 410,核心网用户面网关向核心网移动性管理实体发送更新承载响应 作为应答。
可选地， 步骤 411 , 核心网移动性管理实体向 UE发送建立^ ^载接受消息 通知 UE承载建立完成。在本实施例中， 步驟 411也可以在步驟 406的空口承 载建立过程中执行， 此处不做赘述。
通过以上如图 4所示的流程，将 UE的业务流与 RAB建立对应关系以后 , 家庭基站可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE, 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站能够将 UE的业务流和 RAB 建立对应关系，并根据该对应关系将 UE与分组数据网络之间传输的数据进行 直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了采用现有技术提供的家庭接入系统 架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题，提高了 数据传输速率， 进而改善了用户的业务体验。
在本发明提供的再一实施例中 , 具有业务分流功能的节点为集成核心网 用户面网关的家庭基站网关； 其中， 家庭基站网关可以为 3G 家庭基站网关 ( Home NodeB Gateway ), 或者家庭演进基站网关（ Home eNodeB Gateway ), 核心网用户面网关可以为 GGSN, 或者 S-GW和 P-GW。
如图 5所示， 本发明再一实施例提供的数据传输方法， 包括：
步骤 501-504与如图 3所示的步骤 301-304基本相同， 此处不再赘述。 步驟 505,家庭基站网关分配用户面资源，向家庭基站发送承载建立请求。 步驟 506, 家庭基站根据接收到的承载建立请求内容分配用户面资源，发 起和 UE建立空口承载的过程。
步驟 507, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应， 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步骤 508 ,家庭基站网关分配接收下行数据的 GTP隧道的 IP地址和 TEID , 向核心网移动性管理实体发送承载建立响应， 该承载建立响应包含家庭基站 网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID。 步驟 509, 核心网移动性管理实体向核心网用户面网关发送更新承载请 求， 该更新承载请求包含家庭基站网关分配的接收下行数据的 GTP隧道的 IP 地址和 TEID; 可选地， 更新承载请求还可以包含业务分流指示信息。
步骤 510,核心网用户面网关根据更新承载请求包含的家庭基站网关分配 的接收下行数据的 GTP隧道的 IP地址和 TEID, 从本地集成的家庭基站网关 上获取 RAB上下文， 将 RAB和更新承载请求关联的核心网承载对应的业务 流建立对应关系。
在本实施例中， 核心网用户面网关可以以对应关系表的形式建立业务流 和无线接入 ? 载的对应关系； 也可以以在业务流中添加无线接入承载对应的 标识， 和 /或在无线接入 7Ϊ载中添加业务流对应的标识的形式， 建立业务流和 无线接入承载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方 法建立业务流和无线接入承载的对应关系 , 此处不作赘述。
可选地， 步骤 510 中核心网用户面网关还可以根据更新承载请求相关的 承载标识和 IMSI, 从本地集成的家庭基站网关上获取 RAB上下文， 根据更 新承载请求相关的核心网承载上下文， 建立核心网承载上下文相关的业务流 和 RAB的对应关系。 其中， 承载标识还可以为 RAB ID或者 NSAPI等。
可选地， 如果更新承载请求包含业务分流指示信息， 核心网用户面网关 可以先根据该业务分流指示信息确定承载釆用业务分流方式建立， 然后， 再 建立业务流和 RAB之间对应关系。
由于核心网用户面网关集成在家庭基站网关上， 所以当核心网用户面网 关将 UE的业务流和 RAB建立对应关系以后， 家庭基站网关内部的上下行路 由得以贯通， 后续用户业务数据可以通过家庭基站网关到分组数据网的接口 进行数据收发。
步骤 511 ,核心网用户面网关向核心网移动性管理实体发送更新承载响应 作为应答。
可选地， 步骤 512, 核心网移动性管理实体向 UE发送建立承载接受消息 通知 UE。 在本实施例中， 步驟 512也可以在步驟 506的空口承载建立过程中 执行， 此处不做赘述。
通过以上如图 4所示的流程，将 UE的业务流与 RAB建立对应关系以后 , 家庭基站网关可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE , 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站网关能够将 UE的业务流和 RAB建立对应关系， 并根据该对应关系将 UE与分组数据网络之间传输的数 据进行直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理 带宽， 节省了数据传输占用的网络资源， 解决了采用现有技术提供的家庭接 入系统架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
在本发明实施例提供的再一实施例中 , 具有业务分流功能的节点为集成 核心网用户面网关的家庭基站； 其中 , 家庭基站可以为 HNB或者 HeNB , 核 心网用户面网关可以为 GGSN, 或者 S-GW和 P-GW。
如图 6所示， 本发明再一实施例提供的数据传输方法， 包括：
步驟 601-603与如图 3所示的步驟 301-303基本相同， 此处不再赘述。 步骤 604, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该 承载建立请求包含核心网用户面网关分配的接收上行数据的 GTP隧道的 IP地 址和 TEID,以及业务分流指示信息，可选地，承载建立请求还可以包含 IMSI, 进一步地， 所述业务分流指示信息可以为 IMSI。
步驟 605, 家庭基站网关根据承载建立请求中包含的业务分流指示信息， 不分配用户面资源， 向家庭基站转发所述承载建立请求。
步驟 606, 家庭基站根据接收到的承载建立请求内容分配用户面资源 ,发 起和 UE建立空口承载的过程。
步驟 607, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应， 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 TP地址和 TETD。
步骤 608, 家庭基站网关向核心网移动性管理实体发送承载建立响应， 该 承载建立响应包含家庭基站分配的接收下行数据的 GTP 隧道的 IP 地址和 TEID。
步驟 609, 核心网移动性管理实体向核心网用户面网关发送更新承载请 求，该更新承载请求包含家庭基站分配的接收下行数据的 GTP隧道的 IP地址 和 TEID; 可选地， 更新承载请求还可以包含业务分流指示信息。
步驟 610,核心网用户面网关根据更新承载请求包含的家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID,从本地集成的家庭基站上获取 RAB 上下文， 将 RAB和更新承载请求关联的核心网承载对应的业务流建立对应关 系。
在本实施例中， 核心网用户面网关可以以对应关系表的形式建立业务流 和无线接入7 载的对应关系； 也可以以在业务流中添加无线接入承载对应的 标识， 和 /或在无线接入承载中添加业务流对应的标识的形式， 建立业务流和 无线接入 7 载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方 法建立业务流和无线接入承载的对应关系 , 此处不作赘述。
可选地， 步骤 610 中核心网用户面网关还可以根据更新承载请求相关的 7 载标识和 IMSI, 从本地集成的家庭基站上获取 RAB上下文， 将该 RAB上 下文对应的 RAB和更新承载请求关联的核心网承载对应的业务流建立对应关 系。 其中， 承载标识还可以为 RAB ID或者 NSAPI等。
可选地， 如果更新承载请求包含业务分流指示信息， 核心网用户面网关 可以先根据该业务分流指示信息确定承载采用业务分流方式建立， 然后， 再 建立业务流和 RAB之间对应关系。
由于核心网用户面网关集成在家庭基站上， 所以当核心网用户面网关将 UE的业务流和 RAB建立对应关系以后， 家庭基站内部的上下行路由得以贯 通， 后续用户业务数据可以通过家庭基站到分组数据网络的接口进行数据收 发。
步骤 611和 612与如图 5所示的步骤 511和 512基本相同， 此处不做赞 述。
通过以上如图 6所示的流程，将 UE的业务流与 RAB建立对应关系以后 , 家庭基站可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE, 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站能够将 UE的业务流和 RAB 建立对应关系，并根据该对应关系将 UE与分组数据网络之间传输的数据进行 直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了釆用现有技术提供的家庭接入系统 架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题，提高了 数据传输速率， 进而改善了用户的业务体验。
在本发明提供的再一实施例中， 具有业务分流功能的节点为集成 P-GW 的家庭基站网关， 该业务分流功能的节点不包含 S-GW; 其中， 家庭基站网关 可以为 3G家庭基站网关（Home NodeB Gateway ), 或者家庭演进基站网关 ( Home eNodeB Gateway )。
如图 7所示， 本发明再一实施例提供的数据传输方法， 包括：
步驟 701 , UE向移动性管理实体发送建立承载请求。
在本实施例中， 移动性管理实体可以为 SGSN或者 MME等。
步驟 702, 核心网移动性管理实体向 S-GW发送创建承载请求。
步驟 703, S-GW分配用户面资源， 分配接收上行数据的 GTP隧道的 IP 地址和 TEID , 向 P-GW发送创建承载请求， 该创建承载请求中包含 S-GW分 配的接收上行数据的 GTP隧道的 IP地址和 TEID。
步骤 704, P-GW为创建的承载分配 IP地址， 分配接收上行数据的 GTP 隧道的 IP地址和 TEID, 向 S-GW发送创建承载响应， 该创建承载响应中包 含 P-GW分配的接收上行数据的 GTP隧道的 IP地址和 TEID。 在本实施例中， P-GW可以通过一条独立的消息将为承载分配的 TP地址 发送给 UE, 也可以将为承载分配的 IP地址包含在创建承载响应中， 此处不 作赘述。
步骤 705, S-GW向核心网移动性管理实体发送创建承载响应， 该创建承 载响应包含 S-GW和 P-GW分配的接收上行数据的 GTP隧道的 IP地址和 TEID。
步驟 706, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该 承载建立请求包含 P-GW分配的接收上行数据的 GTP隧道的 IP地址和 TEID; 可选地， 承载建立请求还可以包含业务分流指示信息和 /或 IMSI, 进一步地， 所述业务分流指示信息可以为 IMSI。
步驟 707, 家庭基站网关分配用户面资源， 根据承载建立请求包含 P-GW 分配的接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地集成的 P-GW上 获取核心网承载上下文， 将该核心网承载上下文对应的业务流和无线接入承 载（Radio Access Bearer Identity, RAB )建立对应关系。
在本实施例中， 家庭基站网关可以以对应关系表的形式建立业务流和无 线接入 载的对应关系； 也可以以在业务流中添加无线接入 7|载对应的标识， 和 /或在无线接入 ^^载中添加业务流对应的标识的形式， 建立业务流和无线接 入承载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立 业务流和无线接入承载的对应关系， 此处不作赘述。
可选地， 步驟 707 中家庭基站网关还可以根据承载建立请求中包含的承 载标识和获取的 IMSI, 从本地集成的 P-GW上获取核心网承载上下文， 将该 核心网承载上下文对应的业务流和 RAB建立对应关系。 其中， 承载标识还可 以为 RAB ID或者 NSAPI等。 在本实施例中， 当承载建立请求中包含 IMSI 时， 家庭基站网关可以从该承载建立请求中获取 IMSI; 或者， 当家庭基站网 关为 3G家庭基站网关时， 也可以从预先获取的用户上下文中获取 IMSI, 此 处不对每种情况进行——赘述。 可选地， 如果承载建立请求中包含业务分流指示信息， 家庭基站网关可 以先根据该业务分流指示信息确定承载采用业务分流方式建立， 然后， 再分 配用户面资源 , 建立业务流和 RAB之间对应关系。
当家庭基站网关将 UE的业务流和 RAB建立对应关系以后， 家庭基站网 关内部的上下行路由得以贯通， 后续用户业务数据可以通过家庭基站网关到 分组数据网络的接口进行数据收发。
步驟 708, 家庭基站网关向家庭基站发送承载建立请求。
在本实施例中 , 家庭基站可以为 HNB或者 HeNB。
步驟 709, 家庭基站根据接收到的承载建立请求内容分配用户面资源 ,发 起和 UE建立空口承载的过程。
步驟 710, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应， 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 711 ,家庭基站网关分配接收下行数据的 GTP隧道的 IP地址和 TEID , 向核心网移动性管理实体发送承载建立响应， 该承载建立响应包含家庭基站 网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步骤 712,核心网移动性管理实体向 S-GW发送更新承载请求，该更新承 载请求中包含家庭基站网关分配的接收下行数据的 GTP 隧道的 IP 地址和 TEID。
步驟 713 , S-GW向核心网移动性管理实体发送更新承载响应作为应答。 可选地， 步驟 714, 核心网移动性管理实体向 UE发送建立承载接受消息 通知 UE。 在本实施例中， 步驟 714也可以在步驟 709的空口承载建立过程中 执行， 此处不做赘述。
通过以上如图 7所示的流程，将 UE的业务流与 RAB建立对应关系以后 , 家庭基站网关可以将来自分组数据网络的下行业务流直接通过 RAB发送给
UE , 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。 本发明实施例提供的数据传输方法，家庭基站网关能够将 UE的业务流和 RAB建立对应关系， 并根据该对应关系将 UE与分组数据网络之间传输的数 据进行直接转发 , 不占用接入网到核心网的传输资源以及核心网用户面处理 带宽， 节省了数据传输占用的网络资源， 解决了采用现有技术提供的家庭接 入系统架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
在本发明提供的再一实施例中， 具有业务分流功能的节点为集成 P-GW 的家庭基站， 该业务分流功能的节点不包含 S-GW; 其中， 家庭基站可以为 HNB或者 HeNB。
如图 8所示， 本发明再一实施例提供的数据传输方法， 包括：
步驟 801-805与如图 7所示的步驟 701-705基本相同， 此处不作赘述。 步驟 806, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该 承载建立请求包含 P-GW分配的接收上行数据的 GTP隧道的 IP地址和 TEID, 以及业务分流指示信息， 可选地， 承载建立请求还可以包含 IMSI, 进一步地， 所述业务分流指示信息可以为 IMSI。
步驟 807, 家庭基站网关根据承载建立请求中包含的业务分流指示信息， 不分配用户面资源， 向家庭基站转发所述承载建立请求。
步驟 808, 家庭基站根据接收到的承载建立请求内容分配用户面资源 ,发 起和 UE建立空口承载的过程； 同时， 家庭基站根据承载建立请求中包含的业 务分流指示信息确定承载采用业务分流方式建立， 然后根据承载建立请求包 含的 P-GW分配的接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地集成 的 P-GW上获取核心网^^载上下文， 将该核心网^ ^载上下文对应的业务流和 RAB建立对应关系。
在本实施例中， 家庭基站可以以对应关系表的形式建立业务流和无线接 入承载的对应关系； 也可以以在业务流中添加无线接入承载对应的标识， 和 / 或在无线接入 7 载中添加业务流对应的标识的形式， 建立业务流和无线接入 承载的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立业 务流和无线接入承载的对应关系， 此处不作赘述。
可选地， 当承载建立请求中包含 IMSI时， 步驟 808中家庭基站还可以根 据 7 载建立请求中包含的 7 载标识和 IMSI, 从本地集成的 P-GW上获取核心 网承载上下文， 将该核心网承载上下文对应的业务流和 RAB建立对应关系。 其中 , 承载标识还可以为 RAB ID或者 NSAPI等。
当家庭基站将 UE的业务流和 RAB建立对应关系以后， 家庭基站内部的 上下行路由得以贯通， 后续用户业务数据可以通过家庭基站到分组数据网络 的接口进行数据收发。
步驟 809, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应， 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步骤 810, 家庭基站网关向核心网移动性管理实体发送承载建立响应， 该 承载建立响应包含家庭基站分配的接收下行数据的 GTP 隧道的 IP 地址和 TEID。
步驟 811 ,核心网移动性管理实体向 S-GW发送更新承载请求， 该更新承 载请求中包含家庭基站分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 812, S-GW向核心网移动性管理实体发送更新承载响应作为应答。 可选地， 步驟 813, 核心网移动性管理实体向 UE发送建立承载接受消息 通知 UE。 在本实施例中， 步驟 813也可以在步驟 808的空口承载建立过程中 执行， 此处不做赘述。
通过以上如图 8所示的流程， UE的业务流与 RAB建立对应关系以后 , 家庭基站可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE, 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站能够将 UE的业务流和 RAB 建立对应关系，并根据该对应关系将 UE与分组数据网络之间传输的数据进行 直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了采用现有技术提供的家庭接入系统 架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题。
在本发明提供的再一实施例中， 具有业务分流功能的节点为集成 P-GW 的家庭基站网关， 该业务分流功能的节点不包含 S-GW; 其中， 家庭基站网关 可以为 3G家庭基站网关（Home NodeB Gateway ), 或者家庭演进基站网关 ( Home eNodeB Gateway )。
如图 9所示， 本发明再一实施例提供的数据传输方法， 包括：
步驟 901-906与如图 7所示的步驟 701-706基本相同， 此处不再赘述。 步驟 907,家庭基站网关分配用户面资源，向家庭基站发送承载建立请求。 步驟 908, 家庭基站根据接收到的承载建立请求内容分配用户面资源，发 起和 UE建立空口承载的过程。
步骤 909, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应 , 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 910,家庭基站网关分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向核心网移动性管理实体发送承载建立响应， 该承载建立响应包含家庭基站 网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 911 ,核心网移动性管理实体向 S-GW发送更新承载请求， 该更新承 载请求包含家庭基站网关分配的接收下行数据的 GTP隧道的 IP地址和 TEID 以及业务分流指示信息。
步驟 912, S-GW根据更新承载请求中包含的业务分流指示信息，向 P-GW 转发所述更新承载请求。
步骤 913, P-GW根据该业务分流指示信息确定承载采用业务分流方式建 立， 并根据更新承载请求包含的家庭基站网关分配的接收下行数据的 GTP隧 道的 IP地址和 TEID, 从本地集成的家庭基站网关上获取 RAB上下文， 将该 RAB和更新 7|载请求关联的核心网 7|载所对应的业务流建立对应关系。
在本实施例中， P-GW可以以对应关系表的形式建立业务流和无线接入7 载的对应关系； 也可以以在业务流中添加无线接入承载对应的标识， 和 /或在 无线接入 7 载中添加业务流对应的标识的形式， 建立业务流和无线接入 载 的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立业务流 和无线接入承载的对应关系， 此处不作赘述。
可选地， 步驟 913中 P-GW还可以根据更新承载请求相关的承载标识和 IMSI, 从本地集成的家庭基站网关上获取 RAB上下文， 将该 RAB和更新承 载请求关联的核心网 7 载所对应的业务流建立对应关系。 其中， 7 载标识还 可以为 RAB ID或者 NSAPI等。
由于 P-GW集成在家庭基站网关上，所以当 P-GW将 UE的业务流和 RAB 建立对应关系以后， 家庭基站网关内部的上下行路由得以贯通， 后续用户业 务数据可以通过家庭基站网关到分组数据网络的接口进行数据收发。
步驟 914, P-GW向 S-GW发送更新承载响应作为应答。
步骤 915, S-GW向核心网移动性管理实体发送更新承载响应作为应答。 可选地， 步驟 916, 核心网移动性管理实体向 UE发送建立承载接受消息 通知 UE。 在本实施例中 , 步骤 916也可以在步骤 908的空口 载建立过程中 执行， 此处不做赘述。
通过以上如图 9所示的流程，将 UE的业务流与 RAB建立对应关系以后， 家庭基站网关可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE , 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站网关能够将 UE的业务流和 RAB建立对应关系 , 并根据该对应关系将 UE与分组数据网络之间传输的数 据进行直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理 带宽， 节省了数据传输占用的网络资源， 解决了采用现有技术提供的家庭接 入系统架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
在本发明提供的再一实施例中， 具有业务分流功能的节点为集成 P-GW 的家庭基站， 该业务分流功能的节点不包含 S-GW; 该家庭基站可以为 HNB 或者 HeNB。
如图 10所示， 本发明再一实施例提供的数据传输方法， 包括：
步骤 1001-1005与如图 7所示的步骤 701-705基本相同， 此处不再赘述。 步驟 1006, 核心网移动性管理实体向家庭基站网关发送承载建立请求， 该承载建立请求包含 P-GW分配的接收上行数据的 GTP 隧道的 IP地址和 TEID, 以及业务分流指示信息， 可选地， 承载建立请求还可以包含 IMSI, 进 一步地， 所述业务分流指示信息可以为 IMSI。
步驟 1007,家庭基站网关根据承载建立请求中包含的业务分流指示信息， 不分配用户面资源， 向家庭基站转发所述承载建立请求。
步骤 1008, 家庭基站根据接收到的承载建立请求内容分配用户面资源， 发起和 UE建立空口承载的过程。
步骤 1009, 家庭基站分配接收下行数据的 GTP隧道的 IP地址和 TEID, 向家庭基站网关发送承载建立响应 , 该承载建立响应包含家庭基站分配的接 收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 1010, 家庭基站网关向核心网移动性管理实体发送承载建立响应， 该承载建立响应包含家庭基站分配的接收下行数据的 GTP隧道的 IP地址和 TEID。
步驟 1011 , 核心网移动性管理实体向 S-GW发送更新承载请求， 该更新 承载请求包含家庭基站分配的接收下行数据的 GTP隧道的 IP地址和 TEID以 及业务分流指示信息。
步骤 1012, S-GW根据更新承载请求中包含的业务分流指示信息， 向 P-GW转发所述更新承载请求。
步骤 1013, P-GW根据该业务分流指示信息确定承载采用业务分流方式 建立， 并根据更新承载请求包含的家庭基站分配的接收下行数据的 GTP隧道 的 IP地址和 TEID, 从本地集成的家庭基站上获取 RAB上下文， 将该 RAB 和更新承载请求关联的核心网承载所对应的业务流建立对应关系。
在本实施例中， P-GW可以以对应关系表的形式建立业务流和无线接入7 载的对应关系； 也可以以在业务流中添加无线接入 载对应的标识， 和 /或在 无线接入 ^^载中添加业务流对应的标识的形式， 建立业务流和无线接入 ^^载 的对应关系。 当然， 在实际的使用过程中， 还可以通过其他方法建立业务流 和无线接入承载的对应关系， 此处不作赘述。
可选地， 步骤 1013中 P-GW还可以才艮据更新 7 载请求相关的 7 载标识和 IMSI, 从本地集成的家庭基站上获取 RAB上下文， 将该 RAB和更新 载请 求关联的核心网承载所对应的业务流建立对应关系。 其中， 承载标识还可以 为 RAB ID或者 NSAPI等。
由于 P-GW集成在家庭基站上， 所以当 P-GW将 UE的业务流和 RAB建 立对应关系以后， 家庭基站内部的上下行路由得以贯通， 后续用户业务数据 可以通过家庭基站到分组数据网络的接口进行数据收发。
步驟 1014-1016与如图 9所示的步驟 914-916基本相同， 此处不再赘述。 通过以上如图 9所示的流程，将 UE的业务流与 RAB建立对应关系以后， 家庭基站可以将来自分组数据网络的下行业务流直接通过 RAB发送给 UE, 将来自 UE的上行业务流通过 RAB接收后直接转发给分组数据网络。
本发明实施例提供的数据传输方法，家庭基站能够将 UE的业务流和 RAB 建立对应关系，并根据该对应关系将 UE与分组数据网络之间传输的数据进行 直接转发， 不占用接入网到核心网的传输资源以及核心网用户面处理带宽， 节省了数据传输占用的网络资源 , 解决了采用现有技术提供的家庭接入系统 架构进行 UE与分组数据网络之间数据传输占用网络资源过多的问题，提高了 数据传输速率， 进而改善了用户的业务体验。
如图 11所示，本发明实施例还提供一种具有业务分流功能的节点， 包括： 建立单元 1101 ,用于建立用户设备的业务流和无线接入^ ^载的对应关系； 传输单元 1102,用于才艮据所述建立单元 1101建立的业务流和无线接入 载的对应关系将接收到的分组数据网络的业务流直接通过无线接入承载发送 给所述用户设备； 或者
将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分 组数据网络。
进一步地， 如图 12所示， 所述建立单元 1101可以包括：
第一接收子单元 1201 , 用于接收承载建立请求， 所述承载建立请求包含 接收上行数据的 GTP隧道的 IP地址和隧道端点标识 TEID;
第一获取子单元 1202,用于根据所述第一接收子单元 1201获取的接收上 行数据的 GTP隧道的 IP地址和 TEID, 从本地集成的核心网用户面网关上获 取所述用户设备对应的核心网承载上下文；
第一建立子单元 1203,用于建立所述第一获取子单元 1202获取的核心网 承载上下文相关的业务流和无线接入承载的对应关系。
或者， 如图 12所示， 所述建立单元 1101可以包括：
第二接收子单元 1204, 用于接收承载建立请求；
第二获取子单元 1205,用于根据所述第二接收子单元 1204接收的承载建 立请求包含的承载标识和预先获取的 IMSI, 从本地获取所述用户设备对应的 核心网 7|载上下文；
第二建立子单元 1206,用于建立所述第二获取子单元 1205获取的核心网 承载上下文相关的业务流和无线接入承载的对应关系。
或者， 如图 12所示， 所述建立单元 1101可以包括：
第三接收子单元 1207, 用于接收更新承载请求， 所述更新承载请求包含 接收下行数据的 GTP隧道的 IP地址和隧道端点标识 TEID;
第三获取子单元 1208,用于根据所述第三接收子单元 1207获取的接收下 行数据的 GTP隧道的 IP地址和 TEID, 从本地获取所述用户设备对应的无线 接入 7|载上下文；
第三建立子单元 1209,用于将所述第三获取子单元 1208获取的无线接入 载和更新 7|载请求相关的核心网 7|载下文对应的业务流建立对应关系。 或者， 如图 12所示， 所述建立单元 1101可以包括：
第四接收子单元 1210, 用于接收更新承载请求；
第四获取子单元 1211 ,用于根据所述第四接收子单元 1210接收的更新承 载请求相关的承载标识和 IMSI, 从本地获取所述用户设备对应的无线接入承 载上下文；
第四建立子单元 1212,用于将所述第四获取子单元 1211获取的无线接入 承载和更新承载请求关联的核心网承载所对应的业务流建立对应关系。
进一步地， 如图 12所示， 所述建立单元 1101还可以包括：
第一确定单元 1213,用于当所述第一接收子单元 1201或者第二接收子单 元 1204接收到的承载建立请求还包含业务分流指示信息时， 根据所述分流指 示信息确定承载采用业务分流方式建立， 指示所述第一建立子单元 1203或者 第二建立子单元 1206建立所述业务流和无线接入 ^^载的对应关系； 和 /或， 第二确定单元 1214,用于当所述第三接收子单元 1207或者第四接收子单 元 1210接收到的更新承载请求还包含业务分流指示信息时， 根据所述分流指 示信息确定承载釆用业务分流方式建立， 指示所述第三建立子单元 1209或者 第四建立子单元 1212建立所述业务流和无线接入 载的对应关系。
在本实施例中， 以上如图 11和 12所示的具有业务分流功能的节点可以 为集成核心网用户面网关的家庭基站或者家庭基站网关； 所述用户面网关为 SGSN、 P-GW或者 P-GW和 S-GW等。
本发明实施例提供的业务分流装置具体实现方法可以参见本发明实施例 提供的数据传输方法所述， 此处不再赘述。
本发明实施例提供的具有业务分流功能的节点， 能够将用户设备的业务 流和无线接入承载建立对应关系， 并根据该对应关系将用户设备与分组数据 网络之间传输的数据进行直接转发， 不占用接入网到核心网的传输资源以及 核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了采用现有 技术提供的家庭接入系统架构进行 UE 与分组数据网络之间数据传输占用网 络资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务体验。
本发明实施例还提供一种通信系统， 包括： 具有业务分流功能的节点， 用于将用户设备的业务流和无线接入承载建立对应关系 , 根据所述业务流和 无线接入承载的对应关系 , 将接收到的分组数据网络的业务流直接通过无线 接入承载发送给所述用户设备； 或者
将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分 组数据网络。
本发明实施例提供的通信系统的具体实现方法可以参见本发明实施例提 供的具有业务分流功能的节点所述， 此处不再赘述。
本发明实施例提供的通信系统， 具有业务分流功能的节点能够将用户设 备的业务流和无线接入承载建立对应关系， 并根据该对应关系将用户设备与 分组数据网络之间传输的数据进行直接转发， 不占用接入网到核心网的传输 资源以及核心网用户面处理带宽， 节省了数据传输占用的网络资源， 解决了 采用现有技术提供的家庭接入系统架构进行 UE 与分組数据网络之间数据传 输占用网络资源过多的问题， 提高了数据传输速率， 进而改善了用户的业务 体验。
本发明实施例提供的数据传输方法、 装置和通信系统， 既可以应用在家 庭接入系统中， 也可以应用在普通的 3G或者 LTE等宏网络中。 当本发明实 施例提供的数据传输方法、 装置和通信系统应用在普通的 3G或者 LTE等宏 网络中时， 家庭基站对应普通 3G的基站（NodeB )，或者 LTE等演进网络的 演进基站 ( eNodB )，家庭基站网关对应基站控制器或者 3G的无线网络控制器 ( Radio Network Controller, RNC )。 是可以通过程序来指令相关的硬件完成， 所述的程序可以存储于一计算机可 读存储介质中， 如 ROM/RAM、 磁碟或光盘等。
以上所述， 仅为本发明的具体实施方式， 但本发明的保护范围并不局限 于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易 想到变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本发明的保护 范围应所述以权利要求的保护范围为准。

Claims

权利 要求 书
1、 一种数据传输方法， 其特征在于， 包括：
具有业务分流功能的节点建立用户设备的业务流和无线接入承载的对应关 系；
所述具有业务分流功能的节点根据所述对应关系， 将接收到的分组数据网 络的业务流直接通过无线接入承载发送给所述用户设备； 或者
将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分组 数据网络。
2、 根据权利要求 1所述的方法， 其特征在于， 所述具有业务分流功能的节 点建立业务流和无线接入承载的对应关系包括：
所述具有业务分流功能的节点接收承载建立请求 , 所述承载建立请求包含 接收上行数据的通用无线分组业务隧道协议 GTP隧道的 IP地址和隧道端点标识 TEID;
所述具有业务分流功能的节点根据接收上行数据的 GTP隧道的 IP地址和 TEID , 从本地获取所述用户设备对应的核心网 7 载上下文；
所述具有业务分流功能的节点建立所述核心网承载上下文相关的业务流和 无线接入承载的对应关系。
3、 根据权利要求 2所述的方法， 其特征在于， 当所述具有业务分流功能的 节点为集成分组数据网关的家庭基站或家庭基站网关时， 所述承载建立请求包 含由所述分组数据网关分配的接收上行数据的 GTP隧道的 IP地址和 TEID。
4、 根据权利要求 1所述的方法， 其特征在于， 所述具有业务分流功能的节 点建立用户设备的业务流和无线接入承载的对应关系包括：
所述具有业务分流功能的节点接收承载建立请求；
所述具有业务分流功能的节点根据所述承载建立请求包含的承载标识和获 取的用户身份标识 IMSI, 从本地获取所述用户设备对应的核心网承载上下文； 所述具有业务分流功能的节点建立所述核心网承载上下文相关的业务流和 无线接入承载的对应关系。
5、 根据权利要求 4所述的方法， 其特征在于， 获取所述 IMSI的方式包括： 所述具有业务分流功能的节点从所述承载建立请求中获取所述 IMSI; 或者 所述具有业务分流功能的节点从所述用户设备的上下文信息中获取所述
IMSL
6、 根据权利要求 1所述的方法， 其特征在于， 所述具有业务分流功能的节 点建立用户设备的业务流和无线接入承载的对应关系包括：
所述具有业务分流功能的节点接收更新承载请求， 所述更新承载请求包含 接收下行数据的 GTP隧道的 IP地址和 TEID;
所述具有业务分流功能的节点根据接收下行数据的 GTP隧道的 IP地址和 TEID , 从本地获取所述用户设备对应的无线接入承载上下文；
所述具有业务分流功能的节点根据更新承载请求相关的核心网承载上下 文， 建立核心网 载上下文相关的业务流和无线接入 7 载的对应关系。
7、 根据权利要求 1所述的方法， 其特征在于， 所述具有业务分流功能的节 点建立用户设备的业务流和无线接入承载的对应关系包括：
所述具有业务分流功能的节点接收更新承载请求；
所述具有业务分流功能的节点根据所述更新承载请求相关的承载标识和
IMSI , 从本地获取所述用户设备对应的无线接入承载上下文；
所述具有业务分流功能的节点根据更新承载请求相关的核心网承载上下 文， 建立核心网 7 载上下文相关的业务流和无线接入 7 载的对应关系。
8、 根据权利要求 2、 4、 6或 7所述的方法， 其特征在于， 所述具有业务分 流功能的节点接收承载建立请求之后， 还包括：
当所述承载建立请求还包含业务分流指示信息时 , 所述具有业务分流功能 的节点根据所述分流指示信息确定承载采用业务分流方式建立； 或者，
所述具有业务分流功能的节点接收更新承载请求之后， 还包括：
当所述更新承载请求还包含业务分流指示信息时， 所述具有业务分流功能 的节点根据所述分流指示信息确定承载采用业务分流方式建立。
9、 一种具有业务分流功能的节点， 其特征在于， 包括：
建立单元 , 用于建立用户设备的业务流和无线接入承载的对应关系； 传输单元， 用于根据所述建立单元建立的业务流和无线接入承载的对应关 系， 将接收到的分组数据网络的业务流直接通过无线接入承载发送给所述用户 设备； 或者
将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分组 数据网络。
10、 根据权利要求 9所述的具有业务分流功能的节点， 其特征在于， 所述 建立单元包括：
第一接收子单元， 用于接收承载建立请求， 所述承载建立请求包含接收上 行数据的 GTP隧道的 IP地址和隧道端点标识 TEID;
第一获取子单元， 用于根据所述第一接收子单元获取的接收上行数据的 GTP隧道的 IP地址和 TEID, 从本地获取所述用户设备对应的核心网承载上下 文；
第一建立子单元， 用于建立所述第一获取子单元获取的核心网承载上下文 相关的业务流和无线接入承载的对应关系。
11、 根据权利要求 9所述的具有业务分流功能的节点， 其特征在于， 所述 建立单元包括：
第二接收子单元， 用于接收承载建立请求；
第二获取子单元， 用于根据所述第二接收子单元接收的承载建立请求包含 的承载标识和预先获取的 IMSI, 从本地获取所述用户设备对应的核心网承载上 下文；
第二建立子单元， 用于建立所述第二获取子单元获取的核心网承载上下文 相关的业务流和无线接入承载的对应关系。
12、 根据权利要求 9所述的具有业务分流功能的节点， 其特征在于， 所述 建立单元包括：
第三接收子单元， 用于接收更新承载请求， 所述更新承载请求包含接收下 行数据的 GTP隧道的 IP地址和隧道端点标识 TEID;
第三获取子单元， 用于根据所述第三接收子单元获取的接收下行数据的 GTP隧道的 IP地址和 TEID, 从本地获取所述用户设备对应的无线接入 载上 下文；
第三建立子单元， 用于将所述第三获取子单元获取的无线接入承载和更新 载请求相关的核心网 载下文对应的业务流建立对应关系。
13、 4艮据权利要求 9所述的具有业务分流功能的节点， 其特征在于， 所述 建立单元包括：
第四接收子单元， 用于接收更新承载请求；
第四获取子单元， 用于根据所述第四接收子单元接收的更新承载请求相关 的承载标识和 IMSI, 从本地获取所述用户设备对应的无线接入承载上下文； 第四建立子单元， 用于将所述第四获取子单元获取的无线接入承载和更新 载请求相关的核心网 7 载上下文对应的业务流建立对应关系。
14、根据权利要求 10-13中任意一项所述的具有业务分流功能的节点，其特 征在于， 所述建立单元还包括：
第一确定单元， 用于当所述第一接收子单元或者第二接收子单元接收到的 承载建立请求还包含业务分流指示信息时， 根据所述分流指示信息确定承载釆 用业务分流方式建立， 指示所述第一建立子单元或者第二建立子单元建立所述 业务流和无线接入 载的对应关系； 和 /或，
第二确定单元， 用于当所述第三接收子单元或者第四接收子单元接收到的 更新承载请求还包含业务分流指示信息时 , 根据所述分流指示信息确定承载采 用业务分流方式建立， 指示所述第三建立子单元或者第四建立子单元建立所述 业务流和无线接入承载的对应关系。
15、 根据权利要求 9所述的具有业务分流功能的节点， 其特征在于， 所述具有业务分流功能的节点为集成核心网用户面网关的家庭基站或者家 庭基站网关；
其中， 所述用户面网关为服务通用分组无线业务 GPRS 支持节点， 或者分 组数据网关，或者分组数据网关和服务网关；所述家庭基站为 3G家庭基站 HNB, 或者家庭演进基站 HeNB, 或者宏网络基站 NodeB, 或者演进基站 eNodeB; 所 述家庭基站网关为 3G家庭基站网关，或者家庭演进基站网关，或者基站控制器， 或者无线网络控制器。
16、 一种通信系统， 其特征在于， 包括：
具有业务分流功能的节点， 用于将用户设备的业务流和无线接入承载建立 对应关系， 根据所述业务流和无线接入承载的对应关系， 将接收到的分组数据 网络的业务流直接通过无线接入承载发送给所述用户设备； 或者
将通过无线接入承载接收到的所述用户设备的业务流直接转发给所述分组 数据网络。
PCT/CN2010/075766 2009-08-07 2010-08-06 数据传输方法、装置和通信系统 WO2011015147A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910166406.6 2009-08-07
CN 200910166406 CN101990247B (zh) 2009-08-07 2009-08-07 数据传输方法、装置和通信系统

Publications (1)

Publication Number Publication Date
WO2011015147A1 true WO2011015147A1 (zh) 2011-02-10

Family

ID=43543939

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075766 WO2011015147A1 (zh) 2009-08-07 2010-08-06 数据传输方法、装置和通信系统

Country Status (2)

Country Link
CN (1) CN101990247B (zh)
WO (1) WO2011015147A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102932842A (zh) * 2012-09-14 2013-02-13 北京中创信测科技股份有限公司 一种应用于Gn接口的用户会话级分流方法
CN104349393A (zh) * 2013-07-31 2015-02-11 华为技术有限公司 一种网络分流的方法和设备
CN105208585A (zh) * 2014-06-23 2015-12-30 中兴通讯股份有限公司 调度信息的配置、配置参数的处理方法及装置
CN105450473A (zh) * 2015-12-07 2016-03-30 湖南戎腾网络科技有限公司 一种面向lte网络的用户溯源关联方法及前端采集器

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102918885B (zh) * 2011-05-30 2015-07-08 华为技术有限公司 一种实现业务数据流分流的方法、系统及相关装置
CN102892143B (zh) 2011-07-20 2015-11-25 华为技术有限公司 数据分流的方法以及用户设备
CN103096474B (zh) * 2011-10-27 2016-06-08 华为技术有限公司 数据分流传输方法、用户设备和基站
CN103096398B (zh) 2011-11-08 2016-08-03 华为技术有限公司 一种网络切换的方法和装置
CN107172684B (zh) 2011-12-08 2020-09-29 华为技术有限公司 接入方法及系统、用户设备与网络侧设备
CN102711184B (zh) * 2012-06-18 2015-06-10 西安邮电学院 异构无线网络的分流系统
CN110087332B (zh) * 2012-10-05 2024-02-02 日本电气株式会社 基站、用户设备及其通信方法
CN103796246A (zh) * 2012-10-31 2014-05-14 中兴通讯股份有限公司 数据的分流方法、装置及系统
CN103959855B (zh) * 2012-11-07 2018-01-12 华为技术有限公司 数据分流方法及数据分流控制设备、传输点、终端
CN110337150B (zh) 2014-04-21 2023-06-27 华为技术有限公司 承载控制方法及系统
CN107277927B (zh) * 2016-04-08 2023-04-25 中兴通讯股份有限公司 一种用户文本感知业务的处理方法及网络设备
WO2018045515A1 (zh) * 2016-09-07 2018-03-15 华为技术有限公司 一种数据分流方法及相关装置
CN109040671B (zh) * 2018-07-09 2021-09-17 上海顶竹通讯技术有限公司 一种lte网络移动视频监控的实现方法

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1523819A (zh) * 2003-02-20 2004-08-25 华为技术有限公司 网络中指定路由的方法
CN1750504A (zh) * 2004-09-15 2006-03-22 华为技术有限公司 一种在网络中路由转发的方法
KR20060070249A (ko) * 2004-12-20 2006-06-23 한국전자통신연구원 다중 채널 링크에서 프레임의 순서유지 및 전송량 분배장치, 방법 및 이를 이용한 다중채널 송신기
US20070195750A1 (en) * 2006-02-21 2007-08-23 Lehman Brothers Inc. System and method for network traffic splitting
CN101237372A (zh) * 2008-02-27 2008-08-06 中兴通讯股份有限公司 分组数据业务传输方法及无线终端
CN101360348A (zh) * 2008-08-25 2009-02-04 中兴通讯股份有限公司 一种业务首尾节点之间的虚拟控制通道建立方法
KR20090041868A (ko) * 2007-10-25 2009-04-29 엘지전자 주식회사 Ｂｃａｓｔ 서비스에서의 콘텐츠 전송 방법
US20090116513A1 (en) * 2007-11-05 2009-05-07 Cisco Technology, Inc. System and Method for Providing Single IP Tunnel

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1523819A (zh) * 2003-02-20 2004-08-25 华为技术有限公司 网络中指定路由的方法
CN1750504A (zh) * 2004-09-15 2006-03-22 华为技术有限公司 一种在网络中路由转发的方法
KR20060070249A (ko) * 2004-12-20 2006-06-23 한국전자통신연구원 다중 채널 링크에서 프레임의 순서유지 및 전송량 분배장치, 방법 및 이를 이용한 다중채널 송신기
US20070195750A1 (en) * 2006-02-21 2007-08-23 Lehman Brothers Inc. System and method for network traffic splitting
KR20090041868A (ko) * 2007-10-25 2009-04-29 엘지전자 주식회사 Ｂｃａｓｔ 서비스에서의 콘텐츠 전송 방법
US20090116513A1 (en) * 2007-11-05 2009-05-07 Cisco Technology, Inc. System and Method for Providing Single IP Tunnel
CN101237372A (zh) * 2008-02-27 2008-08-06 中兴通讯股份有限公司 分组数据业务传输方法及无线终端
CN101360348A (zh) * 2008-08-25 2009-02-04 中兴通讯股份有限公司 一种业务首尾节点之间的虚拟控制通道建立方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102932842A (zh) * 2012-09-14 2013-02-13 北京中创信测科技股份有限公司 一种应用于Gn接口的用户会话级分流方法
CN102932842B (zh) * 2012-09-14 2016-01-06 北京中创信测科技股份有限公司 一种应用于Gn接口的用户会话级分流方法
CN104349393A (zh) * 2013-07-31 2015-02-11 华为技术有限公司 一种网络分流的方法和设备
CN105208585A (zh) * 2014-06-23 2015-12-30 中兴通讯股份有限公司 调度信息的配置、配置参数的处理方法及装置
CN105450473A (zh) * 2015-12-07 2016-03-30 湖南戎腾网络科技有限公司 一种面向lte网络的用户溯源关联方法及前端采集器
CN105450473B (zh) * 2015-12-07 2018-07-13 湖南戎腾网络科技有限公司 一种面向lte网络的用户溯源关联方法及前端采集器

Also Published As

Publication number Publication date
CN101990247A (zh) 2011-03-23
CN101990247B (zh) 2013-08-28

Similar Documents

Publication Publication Date Title
WO2011015147A1 (zh) 数据传输方法、装置和通信系统
US9357571B2 (en) Local network and method for establishing connection between local gateway and home base station
JP5970614B2 (ja) マルチネットワークジョイント伝送に基づくオフロード方法、システム及びアクセスネットワーク要素
JP5972290B2 (ja) Ｅｐｓにおけるモバイルルータ
US8730831B2 (en) Method and system for acquiring route strategies
EP2317821B1 (en) Wireless communication system and routing method for packet switching service, femto AP using the routing method
WO2011020386A1 (zh) 承载类型的指示方法、系统及传输分流网元
WO2009049529A1 (fr) Procédé d'établissement de support de charge et dispositif associé
WO2011095100A1 (zh) 一种对本地ip连接的建立进行控制的方法和系统
WO2010015189A1 (zh) 移动网络高速接入公网的节点、方法及系统
WO2012129923A1 (zh) 接入网网元、接入网络系统及接入方法
WO2009100628A1 (zh) 基于lte/sae系统的连接建立方法、系统、装置
WO2011054264A1 (zh) 一种建立本地ip访问下行数据通道的方法及系统
WO2009026761A1 (fr) Procédé de contrôle d'un ambr partagé à supports multiples
WO2013004121A1 (zh) 本地网关信息处理方法及装置
CN102457931B (zh) 一种数据路由控制方法及系统
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
WO2014067371A1 (zh) 集群业务实现方法、系统及网元
WO2012028071A1 (zh) 一种查询本地网关的方法和系统
WO2011050663A1 (zh) 支持本地ip访问的通信系统中隧道更新方法与系统
WO2011109999A1 (zh) 信息的指示方法及移动管理网元
WO2011009353A1 (zh) 建立ip分流连接的实现方法和系统
WO2013082987A1 (zh) 对本地卸载数据进行资源控制的方法及系统
WO2012041131A1 (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: 10806051

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: 10806051

Country of ref document: EP

Kind code of ref document: A1