WO2013185720A1 - 一种无线接入网中的通讯方法及无线接入网设备 - Google Patents

一种无线接入网中的通讯方法及无线接入网设备 Download PDF

Info

Publication number
WO2013185720A1
WO2013185720A1 PCT/CN2013/080808 CN2013080808W WO2013185720A1 WO 2013185720 A1 WO2013185720 A1 WO 2013185720A1 CN 2013080808 W CN2013080808 W CN 2013080808W WO 2013185720 A1 WO2013185720 A1 WO 2013185720A1
Authority
WO
WIPO (PCT)
Prior art keywords
party application
message
uplink
tcp
packet
Prior art date
Application number
PCT/CN2013/080808
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 中兴通讯股份有限公司
Priority to US14/421,852 priority Critical patent/US9344834B2/en
Priority to EP13804456.5A priority patent/EP2879350A4/en
Publication of WO2013185720A1 publication Critical patent/WO2013185720A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/59—Network arrangements, protocols or services for addressing or naming using proxies for addressing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/35—Network arrangements, protocols or services for addressing or naming involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • the present invention relates to communication and base station technologies, and more particularly to third party application technologies for wireless access networks.
  • the base station is actually a data dumb pipeline. As a pure data forwarding node, it can not distinguish between user type, user equipment type and service type, and has localized storage and data optimization capabilities.
  • the rapid growth of data traffic, the real-time requirements of game data, the large-scale application of video data, and the large-scale application of M2M (Machine-to-Machine) have caused significant impact on the base station backhaul (Backhaul) and the core network. The impact.
  • the third embodiment of the present invention provides a third-party application platform and a communication method thereof in the radio access network, and the third-party application software is resident in the radio access network, so that the radio access device can process the context data of the UE, and reduce the radio access. Up and down traffic of the device exit.
  • the third-party application platform monitors an uplink message from the UE, and parses and determines whether the uplink authentication message is an uplink third-party application message;
  • the third-party application platform When it is determined that the uplink packet is an uplink third-party application packet, the third-party application platform performs local processing on the uplink third-party application by using a third-party application of the third-party application platform.
  • the step of the third-party application platform parsing and determining whether the uplink packet is an uplink third-party application packet includes: The third-party application platform searches the third-party application information structure table of the third-party application platform according to the destination Internet Protocol (IP) address and the destination port number of the uplink packet, and determines, according to the search result, the Whether the packet is the uplink third-party application packet.
  • IP Internet Protocol
  • the method further includes:
  • the third-party application platform sends an uplink third-party application domain name system (DNS) message to the DNS server via a third-party application proxy server disposed in the wireless access network, and receives the DNS server response.
  • DNS domain name system
  • the method further includes:
  • the third-party application platform sends an uplink third-party application control protocol/User Datagram Protocol (TCP/UDP) packet to the third-party application via the third-party application proxy server. And receiving, by the server, the third-party application TCP/UDP packet that is sent by the third-party application server.
  • TCP/UDP uplink third-party application control protocol/User Datagram Protocol
  • the step of the third-party application platform sending the third-party application TCP/UDP packet to the third-party application server by using the third-party application proxy server includes:
  • the third-party application platform sends the encapsulated third-party application TCP/UDP packet to the third-party application proxy server by encapsulating the outer IP header for the uplink third-party application TCP/UDP packet.
  • the third-party application proxy server strips the outer IP header of the uplink third-party application TCP/UDP packet, and modifies the upstream third-party application TCP/ by modifying the inner IP address of the outer IP header.
  • the UDP packet is sent to the third-party application server.
  • the method further includes:
  • the third-party application proxy server sends the encapsulated third-party application TCP/UDP packet to the third-party application platform by encapsulating the outer IP header for the downlink third-party application TCP/UDP packet. After the third-party application platform strips the outer IP header of the downlink third-party application TCP/UDP, the third-party application TCP/UDP packet is sent to the third-party application platform. Third-party applications.
  • a radio access network device including a third-party application platform, is provided by an embodiment of the present invention.
  • the third-party application platform includes: a message parsing module and a third-party application module.
  • the text parsing module is configured to: monitor an uplink packet from a user equipment (UE), parse and determine whether the uplink packet is And sending, by the third-party application module, the uplink packet to the third-party application module, where the third-party application module is configured to: The third-party application of the third-party application module is used to locally process the upstream third-party application.
  • UE user equipment
  • the radio access network device further includes: a packet pre-processing module and a third-party application framework;
  • the packet pre-processing module is configured to: send the uplink third-party application message to the third-party application module via the third-party application framework, and receive the third-party application via the third-party application framework And the downlink third-party application message sent by the program module is sent to the packet parsing module;
  • the third-party application framework is configured to: forward the uplink third-party application message to the third-party application module, and forward the downlink third-party application message to the message pre-processing module.
  • the third-party application module is further configured to: send, by using a third-party application proxy server disposed in the radio access network, an uplink third-party application (TCP/UDP) packet to a third-party application server, And receiving and saving the downlink third-party application TCP/UDP packet of the third-party application server in response to the uplink third-party application TCP/UDP packet.
  • TCP/UDP uplink third-party application
  • the packet pre-processing module is further configured to: receive, by using the third-party application framework, the uplink third-party application TCP/UDP file, and encapsulate the TCP/UDP packet for the uplink third-party application.
  • the outer layer Internet Protocol (IP) header sends the encapsulated uplink third-party application TCP/UDP packet to the third-party application proxy server, and applies the outer layer of the downlink third-party application TCP/UDP packet
  • IP header is stripped, and the downlink third-party application TCP/UDP message is sent to the third-party application membrane block via the third-party application framework.
  • IP Internet Protocol
  • the embodiment of the present invention enables a third-party application server to push data to a third-party application platform residing in each base station by setting a third-party application platform on the base station side; 2.
  • the embodiment of the present invention enables the base station side to process the context data of the UE by using a third-party application platform that resides in the base station, which reduces the distance and number of nodes that the data traffic is transmitted in the network, and reduces the uplink and downlink traffic of the base station outlet. Increased user experience and network efficiency for growing data services;
  • FIG. 1 is a structural diagram of a base station based on a third-party application according to a first embodiment of the present invention
  • FIG. 2 is a schematic diagram of a base station architecture based on a third-party application according to a second embodiment of the present invention
  • FIG. 3 is a first embodiment of the present invention
  • FIG. 4 is a flowchart of processing uplink and downlink data of a third-party application of a base station side according to the first embodiment of the present invention
  • FIG. 5 is a schematic diagram of a third-party application information structure table provided by the first embodiment and the second embodiment of the present invention.
  • FIG. 6 is a flowchart of uplink data processing of a UE according to the first embodiment of the present invention
  • FIG. 7 is a flowchart of downlink data processing of a UE according to the first embodiment of the present invention.
  • Base stations based on third-party applications support 2G/3G/LTE (2nd Gerneration/3G/Long Term Evolution, second-generation/third-generation/long-term evolution), where third-party applications refer to not being used by telecommunication equipment providers and operators.
  • Developed applications, such as software applications QQ, UC, etc. 1 is an architectural diagram of a base station based on a third-party application according to a first embodiment of the present invention, that is, an architecture diagram of a base station of the LTE
  • FIG. 2 is an architecture diagram of a base station based on a third-party application according to the second embodiment of the present invention. That is, the architecture diagram of the 2G/3G base station.
  • Base stations based on third-party applications like traditional base stations, only need to add third-party application platforms on the base station side.
  • PDCP Packet Data
  • the Convergence Protocol Packet Data Centralization Protocol
  • RNC Radio Network Controller
  • a third-party application platform is added to the base station, and the local base station for implementing the uplink and downlink user plane data of the third-party application software client of the UE (User Equipment) is implemented. Processing, and performing context data interaction between the UE and the third-party application server of the public network through the third-party application platform.
  • a third-party application proxy server is added to the radio access network for implementing communication between the third-party application platform on the base station side and the third-party application server on the public network.
  • the third-party application platform includes a third-party application module (a third-party application software executable file), a third-party application framework, a message pre-processing module, and a message parsing module.
  • the packet parsing module is responsible for parsing, classifying, and identifying the packet;
  • the packet preprocessing module is responsible for GTPU (GPRS Tunneling Protocol User Plane), GPRS tunneling protocol user plane resolution processing, IPinIP packet processing, and The three-party application packet uplink and downlink statistics and message identification.
  • the third-party application platform is disposed on the base station side, and includes a third-party application module 30, a third-party application framework 31, and a third-party application framework 31.
  • the third-party application module 30 is configured to: perform local processing on the uplink third-party application by using a third-party application thereof; and upload the uplink through a third-party application proxy server set in the wireless access network.
  • the third party sends the TCP/UDP packet to the third-party application server, and receives and saves the third-party application server's TCP/UDP packet for the downlink third-party application that responds to the packet.
  • the third-party application module 30 mainly processes the uplink and downlink data of the third-party application software client on the UE, and centrally uploads the data to the third-party application server according to the storage situation of the local base station, and according to the requirements of the local base station,
  • the third-party application server downloads data in advance and manages the third-party application software, including configuration management, version management, alarm management, and real-time monitoring.
  • the third-party application framework 31 is configured to: forward the third-party application packet to the third-party application module 30, and forward the third-party application packet to the packet pre-processing module 33; And forwarding the third-party application TCP/UDP packet from the third-party application module 30 to the packet pre-processing module 33, and stripping the downlink third-party application of the outer IP (Internet Protocol) header
  • the TCP/UDP file is forwarded to the third party application module 30.
  • the third-party application framework 31 provides various function interfaces and callback functions for the third-party application software, and implements the interaction function between the third-party application module 30 and the message pre-processing module 33.
  • the packet pre-processing module 33 is configured to: send the uplink third-party application message to the third-party application module 30 via the third-party application framework 31, and receive the third-party application via the third-party application framework 31.
  • the downlink third-party application message that is sent by the program module 30 is sent to the message parsing module 32; and the third-party application framework 31 receives the uplink third-party application TCP/UDP packet, which is encapsulated by the packet.
  • the layer IP header is sent to the third-party application proxy server, and the outer IP header of the downlink third-party application TCP/UDP packet is stripped and sent to the third-party application module 30 via the third-party application framework 31.
  • the text pre-processing module 33 identifies and counts the uplink and downlink packets between the UE and the third-party application module 30, and the uplink and downlink packets between the third-party application module 30 and the third-party application server.
  • the GTPU header is stored according to the IP quintuple information, and the packet payload is sent to the third-party application module 30; for the UE and the third party After the MPLS packet is searched for the GTPU header according to the IP quintuple information, the GTPU header is added to the packet and sent to the UE.
  • the packet parsing module 32 is configured to: monitor an uplink packet from the UE, and parse and determine whether the packet is an uplink third-party application packet, and when determining that the packet is an uplink third-party application packet, The uplink third party application message is delivered to the third party application module 30.
  • the message parsing module 32 mainly distinguishes between the uplink and downlink packets between the UE and the third-party application module 30, and the uplink and downlink DNS (Domain Name System) message between the UE and the third-party application module 30.
  • the other media streams of the UE are the uplink and downlink packets, and the statistics of the uplink and downlink packets between the UE and the third-party application module 30 are completed.
  • the uplink and downlink packets between the UE and the third-party application module 30 are sent to the packet pre-processing module 33 for processing, and the other packets are sent to the core network according to the existing process.
  • the workflow of the third-party application platform includes the following steps:
  • the third-party application module 30 passes the third-party application box
  • the frame 31 sends an uplink third-party application DNS packet or a TCP/UDP packet;
  • the third-party application framework 31 sends the packet to the packet pre-processing module 32;
  • the packet pre-processing module 32 constructs an IPinIP packet, wherein the outer layer The source IP address of the IP header is equal to the intranet IP address of the third-party application platform, and the destination IP address is the intranet IP address of the third-party application proxy server.
  • the base station determines that the destination IP address is equal to the intranet IP address of the third-party application proxy server, the IPinIP is used.
  • the packet is sent to the third-party application proxy server.
  • the third-party application proxy server strips the outer IP header of the IPinIP packet, the packet is sent to the DNS server or the third-party application server.
  • the DNS server or the third-party application server sends the downlink third-party application DNS response packet or the TCP/UDP packet to the third-party application proxy server; the third-party application proxy server encapsulates the packet.
  • the IPinIP packet is sent to the base station.
  • the packet pre-processing module 33 of the third-party application platform removes the outer IP header of the IPinIP packet and sends it to the third-party application framework 31.
  • the third-party application framework 31 sends the packet to the third-party application module 30. .
  • FIG. 4 is a flowchart of processing uplink and downlink data of a third-party application of a base station side according to the first embodiment of the present invention, that is, a flowchart of processing uplink and downlink data of a third-party application platform and a third-party application server of the public network, where Describes where each module is located and the data interaction process between them.
  • the UE, the third-party application server, and the DNS server have an external network IP address (ie, a public network IP address)
  • the third-party application module has an intranet IP address
  • the third-party application proxy server has an external network IP address and an internal network address. Network IP address.
  • the third-party application proxy server is responsible for communication between the third-party application platform and the public network DNS server and the third-party application server.
  • the process of sending the uplink packet of the third-party application includes the following steps:
  • Step 1.1 The third-party application module sends the uplink third-party application DNS packet or TCP/UDP packet to the third-party application framework.
  • the third-party application module For DNS packets, the third-party application module first sends a DNS packet through the third-party application framework.
  • the third-party application module sends TCP/UDP through a third-party application framework. Message.
  • Step 1.2 The third-party application framework sends the uplink third-party application DNS packet or TCP/UDP packet to the packet pre-processing module.
  • Step 1.3 The packet pre-processing module identifies the uplink third-party application DNS packet or TCP/UDP packet.
  • the third-party application information structure table as shown in FIG. 5 is searched according to the destination IP address of the packet, and the uplink third-party application and server traffic information is updated; the IPinIP packet is constructed.
  • the source IP address of the outer IP header is the intranet IP address of the third-party application module
  • the destination IP address is the intranet IP address of the third-party application proxy server.
  • Step 1.4 If the base station determines that the destination IP address of the IPinIP packet is an intranet IP address of the third-party application proxy server, the base station sends the IPinIP packet to the third-party application proxy server.
  • Step 1.5 The third-party application proxy server strips the outer IP header of the IPinIP packet; replaces the inner source IP address with the external network IP address of the third-party application proxy server, and replaces the inner destination destination IP address of the uplink third-party application DNS packet. Replace the IP address of the DNS server's external network with the internal IP address of the third-party application TCP/UDP packet with the external network IP address of the third-party application server; and send the packet to the DNS server or third-party application server.
  • the downlink packet receiving process of the third-party application includes the following steps:
  • Step 2.1 The DNS server or the third-party application server sends the third-party application DNS response packet or TCP/UDP packet to the third-party application proxy server.
  • Step 2.2 The third-party application proxy server encapsulates the outer IP header of the packet to form an IPinIP packet, and sends the IPinIP packet to the base station.
  • the source IP address of the outer IP header is the intranet IP address of the third-party application proxy server.
  • the destination IP address is the intranet IP address of the third-party application platform.
  • Step 2.3 After receiving the packet, the base station sends the packet to the third-party application platform when it determines that the destination IP address is the intranet IP address of the third-party application platform.
  • Step 2.4 The packet pre-processing module of the third-party application platform removes the outer IP header of the IPinIP packet, and identifies whether the IPinIP packet is a downlink third-party DNS packet or a downlink third-party TCP/UDP packet. For the downlink third-party DNS packets, find the third-party application server URL (Uniform Resource Locator) and the third-party application according to the content of the packet.
  • the public network IP address of the server is used to search the third-party application information structure table shown in FIG. 5 according to the URL information, and update the public network IP address of the third-party application server to the structure table.
  • extract The source IP address of the packet is used as the public network IP address index of the third-party application server, and the third-party application information structure table is searched, and the downlink third-party application and server traffic are updated, and then the packet is sent to the third-party application framework.
  • Step 2.5 The third-party application framework sends the message to the third-party application module.
  • FIG. 6 is a flowchart of uplink data processing of a UE according to the first embodiment of the present invention, which includes the following steps:
  • Step 3.1 The UE prepares a packet according to different uplink packet types and sends the packet to the base station.
  • Step 3.2 The base station forwards the received packet to the third-party application platform.
  • the packet parsing module of the third-party application platform first determines whether the packet is an uplink control flow message or an uplink media flow message, and extracts the quintuple data in the message. If the packet is an uplink control flow packet, the packet is directly transmitted to the main control access module, and steps 3.5 and 3.6 are performed; if the packet is an uplink media stream packet, the packet is based on the destination IP address. The address and destination port number are searched for the third-party application information structure table as shown in FIG. 5, and the packet is determined to be the third-party application packet of the uplink media stream, and the packet is the third-party application packet of the uplink media stream. And sending the packet to the packet pre-processing module. When the packet is not the third-party application packet of the uplink media stream, the packet is directly transmitted to the master after the packet stream classification, flow identification, and flow statistics are completed. Access the module and perform steps 3.5 and 3.6.
  • Step 3.3 The packet pre-processing module removes the GTPU header of the third-party application packet of the uplink media stream, stores the GTPU header information according to the quintuple information in the payload, and sends the packet that removes the GTPU header to the third party.
  • Application framework removes the GTPU header of the third-party application packet of the uplink media stream, stores the GTPU header information according to the quintuple information in the payload, and sends the packet that removes the GTPU header to the third party.
  • Step 3.4 The third-party application framework sends the message to the third-party application module.
  • Step 3.5 The base station processes the packet according to the existing process, and forwards the packet to the core network.
  • Step 3.6 The core network processes according to the existing process, and forwards the packet to the DNS server and other application servers on the public network.
  • FIG. 7 is a flowchart of processing downlink data of a UE according to the first embodiment of the present invention.
  • the process of receiving a response packet includes the following steps: Step 4.1: The DNS server and other application servers on the public network process and send other packets and DNS packets of the downlink media stream according to the existing process.
  • Step 4.2 The core network processes other packets of the downlink media stream according to the existing process, and forwards the packet to the base station.
  • Step 4.3 The base station forwards the other packets of the downlink media stream to the packet parsing module of the third-party application platform.
  • Step 4.4 The third-party application module sends the third-party application message of the downlink media stream to the third-party application framework.
  • Step 4.5 The third-party application framework sends the third-party application packet of the downlink media stream to the packet pre-processing module.
  • Step 4.6 The packet pre-processing module searches for the GTPU header according to the quintuple information in the payload of the third-party application packet of the downlink media stream, and sends the GTPU header to the packet parsing module after encapsulating the GTPU header.
  • Step 4.7 The packet parsing module first determines whether the received packet is a control flow message or a media flow message.
  • the downlink media stream packet For the downlink media stream packet, find the third-party information structure table as shown in FIG. 5 according to the source IP address and the source port number of the packet, and determine whether it is a third-party application packet of the downlink media stream, and if it is a third-party application of the downlink media stream. "3 ⁇ 4 ⁇ , then the downlink third-party application and UE traffic are counted, and then the " ⁇ text is sent to the UE;
  • the message is sent to the base station.
  • Step 4.8 The base station sends other packets of the downlink media stream to the UE.
  • the embodiment of the present invention uses the third-party application platform that resides on the base station side to process the data of the third-party application software client of the UE, and saves the data pushed by the third-party application server, thereby greatly reducing the egress flow of the base station. It reduces the distance and number of nodes that data traffic is transmitted in the network, which improves the user experience and network efficiency of the service.
  • a program to instruct the associated hardware, such as a read only memory, a magnetic disk, or an optical disk.
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may be implemented in the form of a software function module. Embodiments of the invention are not limited to any specific form of combination of hardware and software.
  • the base station side can process the context data of the UE, reduce the distance and number of nodes that the data traffic is transmitted in the network, reduce the uplink and downlink traffic of the base station egress, and improve the user experience and network of the growing data service. effectiveness.

Landscapes

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

Abstract

一种无线接入网中的通讯方法及无线接入网设备。所述通信方法包括：在无线接入网中设置用于处理用户设备（UE）的第三方应用请求的第三方应用平台；第三方应用平台监听来自UE的上行报文，解析并判断所述上行报文是否是上行第三方应用报文；以及当判断所述上行报文是上行第三方应用报文时，第三方应用平台利用第三方应用平台的第三方应用程序对所述上行第三方应用报文进行本地处理。本发明实施例中，能够减少数据流量在网络中传送的距离和节点数，减少基站出口的上下行流量，提升用户体验和网络效率。

Description

一种无线接入网中的通讯方法及无线接入网设备
技术领域
本发明涉及通信和基站技术， 特别涉及无线接入网的第三方应用技术。
背景技术
随着通信技术的发展以及智能手机的逐渐普及， 无线通信系统中的数据 流量正在呈现快速增长的趋势。 基站实际上是一个数据哑管道， 其作为一个 单纯的数据转发节点， 既不能区分用户类型、 用户设备类型和业务类型， 也 不具备本地化存储和数据优化能力。 而数据流量的快速增长、 游戏数据的实 时要求、 视频数据的大规模应用、 以及 M2M ( Machine-to-Machine, 机对机） 的大规模应用等对基站回程（Backhaul )和核心网造成了重大的冲击。
发明内容
本发明实施例提供无线接入网中的第三方应用平台及其通讯方法， 通过 在无线接入网中驻留第三方应用软件， 使无线接入设备能够处理 UE的上下 文数据， 减少无线接入设备出口的上下行流量。
本发明实施例提供的一种无线接入网中第三方应用平台的通讯方法包 括：
在所述无线接入网中设置用于处理用户设备 ( User Equipment, UE ) 的 第三方应用请求的第三方应用平台；
所述第三方应用平台监听来自 UE的上行 文， 解析并判断所述上行才艮 文是否是上行第三方应用报文；
当判断所述上行报文是上行第三方应用报文时， 所述第三方应用平台利 用所述第三方应用平台的第三方应用程序对所述上行第三方应用 "^文进行本 地处理。
可选地， 所述第三方应用平台解析并判断所述上行报文是否是上行第三 方应用报文的步骤包括： 所述第三方应用平台根据所述上行报文的目的互联网协议 （Internet Protocol, IP )地址和目的端口号查找所述第三方应用平台的第三方应用信息 结构表， 并根据查找结果， 判断所述报文是否是所述上行第三方应用报文。
可选地， 所述方法还包括：
所述第三方应用平台经由设置在所述无线接入网中的第三方应用代理服 务器将上行第三方应用域名系统（Domain Name System, DNS )报文发送至 DNS服务器，并接收所述 DNS服务器响应的下行第三方应用 DNS回应报文； 以及第三方应用平台利用所述下行第三方应用 DNS回应报文，找到需要进行 交互的第三方应用服务器。
可选地， 所述方法还包括：
所述第三方应用平台经由所述第三方应用代理服务器将上行第三方应用 传输控制协议 /用户数据才艮协议 ( Transmission Control Protocol/User Datagram Protocol, TCP/UDP )报文发送至所述第三方应用服务器， 并接收和保存所述 第三方应用服务器响应的下行第三方应用 TCP/UDP报文。
可选地， 所述第三方应用平台经由所述第三方应用代理服务器将上行第 三方应用 TCP/UDP报文发送至所述第三方应用服务器的步骤包括：
所述第三方应用平台通过为所述上行第三方应用 TCP/UDP报文封装外 层 IP头， 将封装后的所述上行第三方应用 TCP/UDP报文发送至所述第三方 应用代理服务器， 所述第三方应用代理服务器将所述上行第三方应用 TCP/UDP报文的外层 IP头剥离， 并通过修改所述外层 IP头的内层 IP地址， 将所述上行第三方应用 TCP/UDP报文发送至所述第三方应用服务器。
可选地， 所述方法还包括：
所述第三方应用代理服务器通过为所述下行第三方应用 TCP/UDP报文 封装外层 IP头， 将封装后的所述下行第三方应用 TCP/UDP报文发送至所述 第三方应用平台，所述第三方应用平台将所述下行第三方应用 TCP/UDP " ^艮文 的外层 IP头剥离后， 并将所述下行第三方应用 TCP/UDP报文发送至所述第 三方应用平台的第三方应用程序。
本发明实施例还提供的一种无线接入网设备， 包括第三方应用平台， 所 述第三方应用平台包括： 报文解析模块和第三方应用程序模块； 其中， 所述 文解析模块设置成： 监听来自用户设备（UE )的上行报文， 解析 并判断所述上行报文是否是上行第三方应用报文， 并当判断所述上行报文是 上行第三方应用报文时， 将所述上行报文传递至所述第三方应用程序模块； 所述第三方应用程序模块设置成： 利用所述第三方应用程序模块的第三 方应用程序， 对所述上行第三方应用>¾文进行本地处理。
可选地， 所述无线接入网设备还包括： 报文预处理模块和第三方应用框 架； 其中，
所述报文预处理模块设置成： 将所述上行第三方应用报文经由所述第三 方应用框架发送至所述第三方应用程序模块， 并经由所述第三方应用框架接 收所述第三方应用程序模块响应的下行第三方应用 >¾文， 并将所述下行第三 方应用报文发送至所述报文解析模块；
所述第三方应用框架设置成： 将所述上行第三方应用报文转发至所述第 三方应用程序模块， 并将所述下行第三方应用报文转发至所述报文预处理模 块。
可选地， 所述第三方应用程序模块还设置成： 经由设置在所述无线接入 网中的第三方应用代理服务器将上行第三方应用 （TCP/UDP )报文发送至第 三方应用服务器， 并接收和保存所述第三方应用服务器响应所述上行第三方 应用 TCP/UDP报文的下行第三方应用 TCP/UDP报文。
可选地， 所述报文预处理模块还设置成： 经由所述第三方应用框架接收 所述上行第三方应用 TCP/UDP 4艮文， 通过为所述上行第三方应用 TCP/UDP 报文封装外层互联网协议（IP )头，将封装后的所述上行第三方应用 TCP/UDP 报文发送至所述第三方应用代理服务器， 并将所述下行第三方应用 TCP/UDP 报文的外层 IP 头剥离， 经由所述第三方应用框架将所述下行第三方应用 TCP/UDP报文发送至所述第三方应用程序膜块。
本发明实施例的有益效果在于：
1、本发明实施例通过在基站侧设置第三方应用平台， 使第三方应用服务 器可以把数据推送到驻留在各个基站的第三方应用平台； 2、本发明实施例通过驻留在基站的第三方应用平台， 使基站侧能够处理 UE的上下文数据， 减少了数据流量在网络中传送的距离和节点数， 减少了基 站出口的上下行流量， 提升了不断增长的数据业务的用户体验和网络效率；
3、 本发明实施例中， UE上的应用和公网服务器与现有架构一致， 不需 要对无线网络架构进行修改和重新设计， 极大的保护了运营商的投资。 附图概述
图 1是本发明第一实施例提供的基于第三方应用的基站的架构图； 图 2是本发明第二实施例提供的基于第三方应用的基站 架构图； 图 3 是本发明第一实施例和第二实施例中所述第三方应用平台的结构 图；
图 4是本发明第一实施例提供的基站侧第三方应用的上下行数据的处理 流程图；
图 5是本发明第一实施例和第二实施例提供的第三方应用信息结构表的 示意图；
图 6是本发明第一实施例提供的 UE的上行数据处理的流程图； 图 7是本发明第一实施例提供的 UE的下行数据处理的流程图。 本发明的较佳实施方式
以下结合附图对本发明的优选实施例进行详细说明， 应当理解， 在不冲 突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
基于第三方应用的基站支持 2G/3G/LTE ( 2nd Gerneration/3G/Long Term Evolution, 第二代 /第三代 /长期演进） ， 其中， 第三方应用是指不是由电信设 备提供商和运营商开发的应用， 例如软件应用 QQ、 UC等。 图 1是本发明第 一实施例提供的基于第三方应用的基站的架构图， 即， LTE的基站的架构图， 图 2是本发明第二实施例提供的基于第三方应用的基站的架构图， 即， 2G/3G 的基站的架构图。 基于第三方应用的基站与传统的基站一样， 只需要在基站 侧增加第三方应用平台， 对于 2G/3G 的基站来说， PDCP ( Packet Data Convergence Protocol , 分组数据集中协议） 层在 RNC ( Radio Network Controller, 无线网络控制器）上处理， RNC的功能下移到基站。
如图 1和图 2所示，本发明实施例中在基站内部增加了第三方应用平台， 用于实现 UE ( User Equipment, 用户设备） 的第三方应用软件客户端上下行 用户面数据的本地基站处理， 并通过所述第三方应用平台， 完成 UE与公网 的第三方应用服务器的上下文数据交互。 同时， 在无线接入网中增加了第三 方应用代理服务器， 用于实现驻留基站侧的第三方应用平台与公网的第三方 应用服务器之间的通信。
所述第三方应用平台包括第三方应用程序模块（第三方应用软件可执行 文件） 、 第三方应用框架、 报文预处理模块、 报文解析模块。 其中， 所述报 文解析模块负责报文的解析、 分类和识别； 所述报文预处理模块负责 GTPU ( GPRS Tunneling Protocol User Plane , GPRS隧道协议用户平面）解析处理、 IPinIP报文的处理、 第三方应用报文上下行统计和报文识别。
下面以 LTE基站为例对本发明实施方式进行解释和说明， 其原理也可以 用于 2G/3G制式的基站。
图 3 是本发明第一实施例和第二实施例中所述第三方应用平台的结构 图， 第三方应用平台设置在基站侧， 包括第三方应用程序模块 30、 第三方应 用框架 31、 ^艮文解析模块 32和^艮文预处理模块 33。
所述第三方应用程序模块 30设置成： 利用其第三方应用程序， 对所述上 行第三方应用 ^艮文进行本地处理； 以及经由设置在无线接入网中的第三方应 用代理服务器将上行第三方应用 TCP/UDP报文发送至第三方应用服务器，并 接收和保存第三方应用服务器响应所述报文的下行第三方应用 TCP/UDP报 文。 也就是说， 所述第三方应用程序模块 30主要处理 UE上的第三方应用软 件客户端的上下行数据， 根据本地基站的存储情况， 集中上传数据到第三方 应用服务器， 并根据本地基站的需求从第三方应用服务器预先下载数据， 并 对第三方应用软件进行统一管理， 包括配置管理、 版本管理、 告警管理和实 时监控等功能。
所述第三方应用框架 31设置成：将所述上行第三方应用报文转发至第三 方应用程序模块 30, 并将下行第三方应用报文转发至报文预处理模块 33; 以 及将来自第三方应用程序模块 30的上行第三方应用 TCP/UDP报文转发至所 述报文预处理模块 33 , 并将剥离了外层 IP ( Internet Protocol, 互联网协议 ) 头的下行第三方应用 TCP/UDP 文转发至所述第三方应用程序模块 30。 所 述第三方应用框架 31为第三方应用软件提供各类函数接口以及回调函数，实 现第三方应用程序模块 30与报文预处理模块 33之间的交互功能。
所述报文预处理模块 33设置成：将所述上行第三方应用报文经由第三方 应用框架 31发送至所述第三方应用程序模块 30, 并经由第三方应用框架 31 接收所述第三方应用程序模块 30响应的下行第三方应用报文，发送至报文解 析模块 32 ; 以及经由所述第三方应用框架 31 接收所述上行第三方应用 TCP/UDP报文， 通过为所述报文封装外层 IP头， 将其发送至第三方应用代 理服务器， 并将所述下行第三方应用 TCP/UDP报文的外层 IP头剥离， 经由 第三方应用框架 31发送至第三方应用程序膜块 30。 所述 文预处理模块 33 识别和统计 UE与第三方应用程序模块 30之间的上下行报文和第三方应用程 序模块 30与第三方应用服务器之间上下行报文。 其中， 对于第三方应用服务 器与第三方应用程序模块 30之间的上行报文，根据 IP五元组信息存储 GTPU 头， 将报文净荷送给第三方应用程序模块 30; 对于 UE与第三方应用程序模 块 30之间的下行报文，根据 IP五元组信息查找 GTPU头后，将找到的 GTPU 头添加到报文后发送至 UE。
所述报文解析模块 32设置成： 监听来自 UE的上行报文， 解析并判断所 述报文是否是上行第三方应用报文， 当判断所述报文是上行第三方应用报文 时， 将所述上行第三方应用报文传递至第三方应用程序模块 30。 所述报文解 析模块 32主要区分 UE与第三方应用程序模块 30之间的上下行报文、 UE与 第三方应用程序模块 30之间的上下行 DNS( Domain Name System,域名系统 ) 报文和 UE其他的媒体流上下行报文， 并完成 UE与第三方应用程序模块 30 之间的上下行报文统计。 对于 UE与第三方应用程序模块 30之间的上下行报 文， 传送给报文预处理模块 33处理， 对于其他报文， 按照现有的流程发送到 核心网。
所述第三方应用平台的工作流程包括如下步骤：
对于第三方应用的上行>¾文，第三方应用程序模块 30通过第三方应用框 架 31发送上行第三方应用 DNS报文或 TCP/UDP报文； 第三方应用框架 31 将所述报文发送到报文预处理模块 32; 报文预处理模块 32构造 IPinIP报文， 其中外层 IP头的源 IP地址等于第三方应用平台内网 IP地址， 目的 IP地址为 第三方应用代理服务器内网 IP地址； 当基站判断目的 IP地址等于第三方应 用代理服务器内网 IP地址时， 将 IPinIP报文发送至第三方应用代理服务器； 第三方应用代理服务器剥离 IPinIP报文的外层 IP头后将报文发送至 DNS服 务器或第三方应用服务器。
对于第三方应用的下行报文， DNS服务器或第三方应用服务器将下行第 三方应用 DNS回应报文或 TCP/UDP报文发送至第三方应用代理服务器； 第 三方应用代理服务器将所述报文封装外层 IP头后形成 IPinIP报文， 并发送至 基站； 当基站收到的 IPinIP报文的目的 IP地址是第三方应用平台的内网 IP 地址时， 将所述报文转发给第三方应用平台； 所述第三方应用平台的报文预 处理模块 33将 IPinIP报文的外层 IP头去掉后发送给第三方应用框架 31 ; 第 三方应用框架 31再将报文发送给第三方应用程序模块 30。
图 4是本发明第一实施例提供的基站侧第三方应用的上下行数据的处理 流程图， 即， 第三方应用平台与公网的第三方应用服务器通讯的上下行数据 的处理流程图， 其中描述了各个模块所处位置， 以及它们之间的数据交互流 程。 图 4中， UE、 第三方应用服务器和 DNS服务器具有外网 IP地址（即， 公网 IP地址 ) , 第三方应用程序模块具有内网 IP地址， 第三方应用代理服 务器具有外网 IP地址和内网 IP地址。 第三方应用代理服务器负责第三方应 用平台与公网 DNS服务器和第三方应用服务器的通信。
第三方应用的上行报文发送流程包括如下步骤：
步骤 1.1、 第三方应用程序模块将上行第三方应用 DNS报文或 TCP/UDP 报文发送至第三方应用框架。
对于 DNS报文，第三方应用程序模块建立 socket的同时首先通过第三方 应用框架发送 DNS报文。
对于数据报文， 第三方应用程序模块通过第三方应用框架发送 TCP/UDP 报文。
步骤 1.2、第三方应用框架将上行第三方应用 DNS报文或 TCP/UDP报文 发送到报文预处理模块。
步骤 1.3、报文预处理模块识别上行第三方应用 DNS报文或 TCP/UDP报 文。
对于上行第三方应用 TCP/UDP报文， 根据所述报文的目的 IP地址查找 如图 5所示的第三方应用信息结构表， 更新上行第三方应用与服务器流量信 息； 构造 IPinIP报文， 使其外层 IP头的源 IP地址是第三方应用程序模块的 内网 IP地址， 目的 IP地址是第三方应用代理月良务器的内网 IP地址。
步骤 1.4、 若基站判断所述 IPinIP报文的目的 IP地址是第三方应用代理 服务器内网 IP地址， 则将所述 IPinIP报文发送至第三方应用代理服务器。
步骤 1.5、 第三方应用代理服务器剥离 IPinIP报文的外层 IP头； 将内层 源 IP地址替换为第三方应用代理服务器外网 IP地址， 上行第三方应用 DNS 报文的内层目的 IP地址替换为 DNS服务器外网 IP地址、 上行第三方应用 TCP/UDP报文的内层目的 IP地址替换为第三方应用服务器外网 IP地址； 以 及将报文送往 DNS服务器或第三方应用服务器。
第三方应用的下行报文接收流程包括如下步骤：
步骤 2.1、 DNS服务器或第三方应用服务器将下行第三方应用 DNS回应 报文或 TCP/UDP报文发送给第三方应用代理服务器。
步骤 2.2、第三方应用代理服务器为所述报文封装外层 IP头后形成 IPinIP 报文， 发送至基站， 所述外层 IP头的源 IP地址是第三方应用代理服务器的 内网 IP地址， 目的 IP地址是第三方应用平台的内网 IP地址。
步骤 2.3、 基站收到所述报文后， 当判断其目的 IP地址是第三方应用平 台内网 IP地址时发送至第三方应用平台。
步骤 2.4、 第三方应用平台的报文预处理模块将 IPinIP报文的外层 IP头 去掉， 并识别所述 IPinIP 报文是下行第三方 DNS 报文还是下行第三方 TCP/UDP报文。 对于下行第三方 DNS报文， 根据报文的内容查找第三方应 用服务器 URL ( Uniform Resource Locator, 统一资源定位符）和第三方应用 服务器公网 IP地址， 根据 URL信息查找图 5所示第三方应用信息结构表， 将第三方应用服务器公网 IP地址更新至所述结构表中； 对于下行第三方应用 TCP/UDP报文， 提取报文的源 IP地址作为第三方应用服务器公网 IP地址索 引， 查找第三方应用信息结构表， 并更新下行第三方应用与服务器流量， 然 后将报文发送至第三方应用框架；
步骤 2.5、 第三方应用框架把报文发送给第三方应用程序模块。
图 6是本发明第一实施例提供的 UE的上行数据处理流程图， 包括如下 步骤：
步骤 3.1、 UE根据不同的上行报文类型准备报文并发送给基站。
步骤 3.2、 基站将收到的报文转发给第三方应用平台。
第三方应用平台的报文解析模块首先判断所述报文是上行控制流报文还 是上行媒体流报文， 并提取报文中的五元组数据。 如果所述报文是上行控制 流报文， 则将报文直接传送给主控接入模块， 并执行步骤 3.5和 3.6; 如果所 述报文是上行媒体流报文， 则根据报文目的 IP地址和目的端口号查找如图 5 所示的第三方应用信息结构表， 判断所述报文是否是上行媒体流第三方应用 报文， 当所述报文是上行媒体流第三方应用报文时， 将其发送至报文预处理 模块， 当所述报文不是上行媒体流第三方应用报文时， 则在完成报文流分类、 流识别和流统计后，将报文直接传送给主控接入模块，并执行步骤 3.5和 3.6。
步骤 3.3、报文预处理模块将所述上行媒体流第三方应用报文的 GTPU头 去掉， 根据净荷中的五元组信息存储 GTPU头信息， 并将去除 GTPU头的报 文发送给第三方应用框架。
步骤 3.4、 第三方应用框架将所述报文发送给第三方应用程序模块。
步骤 3.5、 基站按照现有流程处理， 将报文转发至核心网。
步骤 3.6、 核心网按照现有流程处理， 将报文转发至公网上的 DNS服务 器和其他应用服务器。
图 7是本发明第一实施例提供的 UE的下行数据处理流程图， 服务器应 答报文的接收流程包括如下步骤： 步骤 4.1、 公网上的 DNS服务器和其他应用服务器按照现有流程处理发 送下行媒体流其他报文和 DNS报文。
步骤 4.2、核心网对于下行媒体流其他报文按照现有流程处理， 转发给基 站。
步骤 4.3、基站将下行媒体流其他报文转发给第三方应用平台的报文解析 模块。
步骤 4.4、第三方应用程序模块将下行媒体流第三方应用报文发送给第三 方应用框架。
步骤 4.5、第三方应用框架将所述下行媒体流第三方应用报文发送给报文 预处理模块。
步骤 4.6、报文预处理模块根据所述下行媒体流第三方应用报文的净荷中 的五元组信息查找 GTPU头， 并在封装 GTPU头后发送至报文解析模块。
步骤 4.7、报文解析模块首先判断收到的报文是控制流报文还是媒体流报 文。
对于下行控制流报文， 直接发送给基站；
对于下行媒体流报文，根据报文源 IP地址和源端口号查找如图 5所示的 第三方信息结构表， 判断是否是下行媒体流第三方应用报文， 如果是下行媒 体流第三方应用"¾文， 则统计下行第三方应用与 UE流量， 然后将所述 "^文 发送至 UE;
对于下行媒体流其他 文， 完成 文流分类、 流识别和流统计后， 将所 述报文送到基站。
步骤 4.8、 基站把下行媒体流其它报文发送到 UE。
综上所述， 本发明实施例利用基站侧驻留的第三方应用平台， 处理 UE 的第三方应用软件客户端的数据， 保存第三方应用服务器推送的数据， 极大 的降低了基站的出口流量， 减少了数据流量在网络中传送的距离和节点数， 提升了业务的用户体验和网络效率。 本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明实施例不限 制于任何特定形式的硬件和软件的结合。
照本发明实施例原理所作的修改， 都应当理解为落入本发明的保护范围。
工业实用性
本发明实施例中， 基站侧能够处理 UE的上下文数据， 减少了数据流量 在网络中传送的距离和节点数， 减少了基站出口的上下行流量， 提升了不断 增长的数据业务的用户体验和网络效率。

Claims

权 利 要 求 书
1、 一种无线接入网中的通讯方法， 包括：
在所述无线接入网中设置用于处理用户设备 ( UE )的第三方应用请求的 第三方应用平台；
所述第三方应用平台监听来自 UE的上行 文， 解析并判断所述上行才艮 文是否是上行第三方应用报文；
当判断所述上行报文是上行第三方应用报文时， 所述第三方应用平台利 用所述第三方应用平台的第三方应用程序对所述上行第三方应用 >¾文进行本 地处理。
2、 根据权利要求 1所述的方法， 其中， 所述第三方应用平台解析并判断 所述上行报文是否是上行第三方应用报文的步骤包括：
所述第三方应用平台根据所述上行报文的目的互联网协议（IP )地址和 目的端口号查找所述第三方应用平台的第三方应用信息结构表， 并根据查找 结果， 判断所述报文是否是所述上行第三方应用报文。
3、 根据权利要求 1所述的方法， 其中， 还包括：
所述第三方应用平台经由设置在所述无线接入网中的第三方应用代理服 务器将上行第三方应用域名系统（DNS )报文发送至 DNS服务器， 并接收所 述 DNS服务器响应的下行第三方应用 DNS回应报文； 以及第三方应用平台 利用所述下行第三方应用 DNS回应报文，找到需要进行交互的第三方应用服 务器。
4、 根据权利要求 3所述的方法， 其中， 还包括：
所述第三方应用平台经由所述第三方应用代理服务器将上行第三方应用 传输控制协议 /用户数据报协议（TCP/UDP )报文发送至所述第三方应用服务 器，并接收和保存所述第三方应用服务器响应的下行第三方应用 TCP/UDP报 文。
5、 根据权利要求 4所述的方法， 其中， 所述第三方应用平台经由所述第 三方应用代理服务器将上行第三方应用 TCP/UDP报文发送至所述第三方应 用服务器的步骤包括： 所述第三方应用平台通过为所述上行第三方应用 TCP/UDP报文封装外 层 IP头， 将封装后的所述上行第三方应用 TCP/UDP报文发送至所述第三方 应用代理服务器， 所述第三方应用代理服务器将所述上行第三方应用 TCP/UDP "^文的外层 IP头剥离， 并通过 改所述外层 IP头的内层 IP地址， 将所述上行第三方应用 TCP/UDP报文发送至所述第三方应用服务器。
6、 根据权利要求 5所述的方法， 还包括：
所述第三方应用代理服务器通过为所述下行第三方应用 TCP/UDP报文 封装外层 IP头， 将封装后的所述下行第三方应用 TCP/UDP报文发送至所述 第三方应用平台，所述第三方应用平台将所述下行第三方应用 TCP/UDP " ^艮文 的外层 IP头剥离后， 并将所述下行第三方应用 TCP/UDP报文发送至所述第 三方应用平台的第三方应用程序。
7、 一种无线接入网设备， 包括第三方应用平台， 所述第三方应用平台包 括： 报文解析模块和第三方应用程序模块； 其中，
所述 文解析模块设置成： 监听来自用户设备（UE )的上行报文， 解析 并判断所述上行报文是否是上行第三方应用报文， 并当判断所述上行报文是 上行第三方应用报文时， 将所述上行报文传递至所述第三方应用程序模块； 所述第三方应用程序模块设置成： 利用所述第三方应用程序模块的第三 方应用程序， 对所述上行第三方应用>¾文进行本地处理。
8、 根据权利要求 7所述无线接入网设备， 其中， 还包括： 报文预处理模 块和第三方应用框架； 其中，
所述报文预处理模块设置成： 将所述上行第三方应用报文经由所述第三 方应用框架发送至所述第三方应用程序模块， 并经由所述第三方应用框架接 收所述第三方应用程序模块响应的下行第三方应用 >¾文， 并将所述下行第三 方应用报文发送至所述报文解析模块；
所述第三方应用框架设置成： 将所述上行第三方应用报文转发至所述第 三方应用程序模块， 并将所述下行第三方应用报文转发至所述报文预处理模 块。
9根据权利要求 7或 8所述的无线接入网设备， 其中， 所述第三方应用程序模块还设置成： 经由设置在所述无线接入网中的第 三方应用代理服务器将上行第三方应用传输控制协议 /用户数据报协议
( TCP/UDP )报文发送至第三方应用服务器， 并接收和保存所述第三方应用 服务器响应所述上行第三方应用 TCP/UDP报文的下行第三方应用 TCP/UDP 报文。
10、 根据权利要求 9所述的无线接入网设备， 其中，
所述报文预处理模块还设置成： 经由所述第三方应用框架接收所述上行 第三方应用 TCP/UDP报文， 通过为所述上行第三方应用 TCP/UDP报文封装 外层互联网协议（IP )头， 将封装后的所述上行第三方应用 TCP/UDP报文发 送至所述第三方应用代理服务器，并将所述下行第三方应用 TCP/UDP报文的 外层 IP头剥离， 经由所述第三方应用框架将所述下行第三方应用 TCP/UDP 报文发送至所述第三方应用程序膜块。
PCT/CN2013/080808 2012-08-29 2013-08-05 一种无线接入网中的通讯方法及无线接入网设备 WO2013185720A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/421,852 US9344834B2 (en) 2012-08-29 2013-08-05 Communication method in wireless access network and wireless access network device
EP13804456.5A EP2879350A4 (en) 2012-08-29 2013-08-05 COMMUNICATION METHOD IN A WIRELESS ACCESS NETWORK AND WIRELESS ACCESS NETWORK DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210312311.2A CN103634365A (zh) 2012-08-29 2012-08-29 一种无线接入网中的第三方应用平台及其通讯方法
CN201210312311.2 2012-08-29

Publications (1)

Publication Number Publication Date
WO2013185720A1 true WO2013185720A1 (zh) 2013-12-19

Family

ID=49757592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/080808 WO2013185720A1 (zh) 2012-08-29 2013-08-05 一种无线接入网中的通讯方法及无线接入网设备

Country Status (4)

Country Link
US (1) US9344834B2 (zh)
EP (1) EP2879350A4 (zh)
CN (1) CN103634365A (zh)
WO (1) WO2013185720A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104918224A (zh) * 2014-03-14 2015-09-16 中国移动通信集团江苏有限公司 一种应用服务的提供方法、系统及客户端服务平台

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106027757B (zh) * 2016-04-28 2020-03-31 努比亚技术有限公司 一种移动终端数据分布式上报的装置及方法
CN106302661B (zh) * 2016-08-02 2019-08-13 网宿科技股份有限公司 P2p数据加速方法、装置和系统
CN113709242A (zh) * 2021-08-26 2021-11-26 华为技术有限公司 报文转发方法和通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070067385A1 (en) * 2005-09-20 2007-03-22 Accenture S.P.A. Third party access gateway for telecommunications services
CN101159923A (zh) * 2007-11-09 2008-04-09 华为技术有限公司 业务处理方法及系统、sip应用接入网关模块
CN103067428A (zh) * 2011-10-21 2013-04-24 华为技术有限公司 基站、服务处理方法和云计算系统
CN103167637A (zh) * 2011-12-12 2013-06-19 大唐联诚信息系统技术有限公司 一种移动通信的网元

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8085810B2 (en) * 2008-08-06 2011-12-27 Movik Networks Cross-layer pipelining optimizations for reduced roundtrips and improving quality of experience
CN101932074B (zh) * 2009-06-25 2013-01-23 华为技术有限公司 一种家庭基站本地ip接入的控制方法及装置
CN101998369B (zh) * 2009-08-18 2015-03-25 中兴通讯股份有限公司 一种上行消息的传输方法及系统
ES2963460T3 (es) * 2010-07-02 2024-03-27 Vodafone Ip Licensing Ltd Facturación en redes de telecomunicaciones
US9801233B2 (en) * 2010-08-02 2017-10-24 Interdigital Patent Holdings, Inc. Method and apparatus for supporting femtocell service capabilities for services
CN102036230B (zh) * 2010-12-24 2013-06-05 华为终端有限公司 本地路由业务的实现方法、基站及系统
US8392289B1 (en) * 2011-04-04 2013-03-05 Google Inc. Cancelling a purchasing request
US20130060679A1 (en) * 2011-09-06 2013-03-07 Rawllin International Inc. Third-party payments for electronic commerce

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070067385A1 (en) * 2005-09-20 2007-03-22 Accenture S.P.A. Third party access gateway for telecommunications services
CN101159923A (zh) * 2007-11-09 2008-04-09 华为技术有限公司 业务处理方法及系统、sip应用接入网关模块
CN103067428A (zh) * 2011-10-21 2013-04-24 华为技术有限公司 基站、服务处理方法和云计算系统
CN103167637A (zh) * 2011-12-12 2013-06-19 大唐联诚信息系统技术有限公司 一种移动通信的网元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2879350A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104918224A (zh) * 2014-03-14 2015-09-16 中国移动通信集团江苏有限公司 一种应用服务的提供方法、系统及客户端服务平台

Also Published As

Publication number Publication date
EP2879350A4 (en) 2015-07-22
CN103634365A (zh) 2014-03-12
US20150223007A1 (en) 2015-08-06
US9344834B2 (en) 2016-05-17
EP2879350A1 (en) 2015-06-03

Similar Documents

Publication Publication Date Title
CN102143035B (zh) 数据业务处理方法、网络设备和网络系统
CN107995069B (zh) 一种终端视频推送的方法和装置
WO2019033920A1 (zh) 网络侧对远端用户设备的识别和控制方法以及设备
US20140140211A1 (en) Classification of traffic for application aware policies in a wireless network
US10609181B2 (en) Method and apparatus for controlling service chain of service flow
CN108574818B (zh) 一种信息显示的方法、装置和服务器
WO2012079396A1 (zh) 一种带宽控制的方法、设备和系统
CN110121059A (zh) 监控视频处理方法、装置及存储介质
CN109547417A (zh) 码流传输方法和装置
CN108965223A (zh) 一种基于视联网的网页处理方法、代理服务器及视联网终端
AU2015264883A1 (en) Access control method and system, and access point
CN107888401B (zh) 一种实时监控视联网终端cpu利用率的方法和系统
CN108810579A (zh) 一种视频数据请求方法、协转服务器以及视联网服务器
WO2013182120A1 (zh) 一种异构终端环境中的终端信息获取方法及装置
WO2013185720A1 (zh) 一种无线接入网中的通讯方法及无线接入网设备
CN109302642A (zh) 数据采集方法和装置
WO2012159525A1 (zh) 一种用于自治网络的业务控制方法及系统
CN109587432A (zh) 一种会议发言终端切换方法及系统
CN110233982A (zh) 一种基于视联网的监控方法和装置
CN110035297A (zh) 视频处理方法和装置
CN104168302B (zh) 设备操控实现方法、系统和代理网关
CN109743265A (zh) 一种获取证件信息的方法和装置
EP3082320B1 (en) Identifying browsing sessions based on temporal transaction pattern
CN108064441A (zh) 一种加速网络传输优化方法以及系统
CN108900653A (zh) 一种基于onvif协议及数据链路层实现跨网段搜索系统

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14421852

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2013804456

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013804456

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE