应用信息上报方法及装置 Application information reporting method and device
技术领域 本发明涉及通信领域， 具体而言， 涉及一种应用信息上报方法及装置。 背景技术 第三代合作伙伴计划（3rd Generation Partnership Project, 简称为 3GPP)的演进的 分组系统（Evolved Packet System,简称为 EPS)由演进的通用地面无线接入网（Evolved Universal Terrestrial Radio Access Network,简称为 E-UTRAN)、移动管理单元（Mobility Management Entity, 简称为 MME)、 服务网关 （Serving Gateway, 简称为 S-GW)、 分 组数据网络网关 （Packet Data Network Gateway, 简称为 P-GW) 和归属用户服务器 (Home Subscriber Server, 简称为 HSS) 组成。 The present invention relates to the field of communications, and in particular to an application information reporting method and apparatus. BACKGROUND OF THE INVENTION The Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is evolved by the Evolved Universal Terrestrial Radio Access Network (referred to as Evolved Universal Terrestrial Radio Access Network). E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW) and attribution User Subscriber Server (HSS).
EPS支持与非 3GPP系统的互通 （如图 1所示）， 其中， 与非 3GPP系统的互通通 过 S2a/b/c接口实现， P-GW作为 3GPP与非 3GPP系统间的锚点。 在 EPS的系统架构 图中， 非 3GPP系统接入被分为不可信任非 3GPP接入和可信任非 3GPP接入， 其中， 不可信任非 3GPP接入需经过演进的分组数据网关 （Evolved Packet Data Gateway, 简 称为 ePDG) 与 P-GW相连， ePDG与 P-GW间的接口为 S2b; 可信任非 3GPP接入可 直接通过 S2a接口与 P-GW连接， S2a接口采用代理移动因特网协议版本 6 (Proxy Mobile IP version 6, 简称为 PMIPv6 )协议进行信息交互； 另夕卜， S2c接口提供了用户 设备（User Equipment, 简称为 UE)与 P-GW之间的用户面相关的控制和移动性支持， 其支持的移动性管理协议为支持双桟的移动 IPv6 ( Mobile IPv6 Support for Dual Stack Hosts and Routers, 简称为 DSMIPv6)， 其可用于不可信任非 3GPP和可信任非 3GPP 接入。 无线局域网络 （Wireless Local Area Network, 简称为 WLAN) 可以作为非 3GPP 系统接入演进的分组核心网 （Evolved Packet Core, 简称为 EPC)， 这涉及到很多运营 商关注的固网移动融合 （Fixed Mobile Convergence, 简称为 FMC) 的互连互通问题。 目前， 业界正在开展固定宽带接入网 （Fixed Broadband Access Network) 与 EPC的互 联互通的研究。 其中考虑了两种业务访问的方式： 一种是通过固网直接访问业务 （也 称业务分流（traffic offload)),另一种是通过 3GPP核心网进行业务访问。以 S2b为例， 如图 2所示， 运营商可以根据业务的特征， 部分业务通过 EPS传输， 而另外一部分业
务 （比如： internet业务， 也包括移动网络的流媒体业务平台上的业务） 可以直接从 WLAN分流， 以降低 3GPP核心网的流量负荷。 图 3是根据相关技术的移动终端通过 WLAN直接进行业务分流策略控制的架构示 意图， 3GPP策略和计费规则功能 （Policy and Charging Rule Function, 简称为 PCRF) 与宽带策略控制功能 （Broadband Policy Control Function, 简称为 BPCF) 进行策略互 通以实现对于 UE的策略控制。 此外， 在网络中 (即在 BNG/BRAS之后)部署业务检测 功能（Traffic Detection Function, 简称为 TDF)检测 UE访问的业务信息， 用于 PCRF 或 BPCF的策略决策。 在请求上报（Solicited Reporting)模式下， PCRF或 BPCF需要 为 UE的每一个 IP连接接入网 （IP Connectivity Access Network, 简称为 IP-CAN) 会 话和 TDF建立 TDF会话， 以便 TDF上报检测到该 UE通过该 IP-CAN访问的业务信 息。 然而， UE通过路由模式的 RG接入网络时， 由于通过同一个 RG接入的 UE访问 业务所使用的 IP地址都是相同的 (即均是本地 IP地址)， 所以 TDF无法判断检测到的 业务是哪个 IP-CAN会话， 甚至是哪个 UE访问的业务， 也就无法向该 UE或 IP-CAN 会话对应的 PCRF进行业务信息的上报， 从而也无法实现策略决策和策略控制。 发明内容 本发明提供了一种应用信息上报方法及装置， 以至少解决相关技术中， UE通过固 定宽带接入网进行业务分流时， 无法正确上报检测到的应用信息的问题。 根据本发明的一个方面， 提供了一种应用信息上报方法， 包括： 接收 RG的 IP地 址和 RG为 UE预留的端口号集； 根据 IP地址和端口号集， 上报检测到的应用信息。 优选地， 接收 RG的 IP地址和 RG为 UE预留的端口号集包括： 接收来自策略服 务器的携带有 RG的 IP地址和 RG为 UE预留的端口号集的 TDF会话消息， 其中 RG 的 IP地址和 RG为 UE预留的端口号集用于标识 TDF会话。 优选地， 根据 IP地址和端口号集， 上报检测到的应用信息包括： 通过 TDF会话， 上报检测到的应用信息给策略服务器。 优选地， 在通过 TDF会话， 上报检测到的应用信息给策略服务器之前， 还包括： 当业务数据流使用的 IP地址与 IP地址相匹配， 并且业务数据流使用的端口号与端口 号集相匹配时， 确定业务数据流与 TDF会话是关联的； 对业务数据流的应用信息进行 检测。
优选地， 在根据 IP地址和端口号集， 上报检测到的应用信息之后， 上述方法还包 括： 策略服务器根据上报的应用信息进行策略决定。 优选地， 策略服务器包括以下之一： PCRF、 BPCF。 根据本发明的另一方面， 提供了一种应用信息上报装置， 包括： 接收模块， 设置 为接收 RG的 IP地址和 RG为 UE预留的端口号集； 上报模块， 设置为根据 IP地址和 端口号集， 上报检测到的应用信息。 优选地， 接收模块包括： 接收子模块， 设置为接收来自策略服务器的携带有 RG 的 IP地址和 RG为 UE预留的端口号集的 TDF会话建立消息， 其中 RG的 IP地址和 RG为 UE预留的端口号集唯一标识 TDF会话。 优选地， 上报模块包括： 上报子模块， 设置为通过 TDF会话， 上报检测到的应用 信息给策略服务器。 优选地， 上述装置还包括： 确定模块， 设置为当业务数据流使用的 IP地址与 IP 地址相匹配， 并且业务数据流使用的端口号与端口号集相匹配时， 确定业务数据流与 TDF会话是关联的； 检测模块， 设置为对业务数据流的应用信息进行检测。 本发明中， TDF根据策略服务器提供的 IP地址和端口号集， 以确定是哪个 UE访 问的业务， 从而可以正确上报检测到的应用信息给策略服务器。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1是根据相关技术的 3GPP网络与非 3GPP网络互通的网络结构图； 图 2是根据相关技术的移动终端通过 WLAN进行业务分流和接入 EPC的网络结 构图； 图 3是根据相关技术的移动终端通过 WLAN直接进行业务分流策略控制的架构示 意图； 图 4是根据本发明实施例的应用信息上报方法的流程图；
图 5是根据本发明优选实施例一的应用信息上报方法的交互流程图； 图 6是根据本发明优选实施例二的应用信息上报方法的交互流程图； 图 7是根据本发明实施例的应用信息上报装置的结构框图； 图 8是根据本发明优选实施例一的应用信息上报装置的结构框图； 图 9是根据本发明优选实施例二的应用信息上报装置的结构框图； 图 10是根据本发明优选实施例三的应用信息上报装置的结构框图。 具体实施方式 需要说明的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相 互组合。 下面将参考附图并结合实施例来详细说明本发明。 本发明实施例提供了一种应用信息上报方法， 图 4是根据本发明实施例的应用信 息上报方法的流程图， 如图 4所示， 包括如下的步骤 S402至步骤 S404。 步骤 S402， 接收 RG的 IP地址和 RG为 UE预留的端口号集。 步骤 S404， 根据 IP地址和端口号集， 上报检测到的应用信息。 相关技术中， UE通过固定宽带接入网进行业务分流时，无法正确上报检测到的应 用信息。本发明实施例中， TDF根据策略服务器提供的 IP地址和端口号集， 以确定是 哪个 UE访问的业务， 从而可以正确上报检测到的应用信息给策略服务器。 其中， 步骤 S402通过以下步骤实现： 接收来自策略服务器的携带有 RG的 IP地 址和 RG为 UE预留的端口号集的 TDF会话建立请求消息，其中， RG的 IP地址和 RG 为 UE预留的端口号集用于唯一标识 TDF会话。 步骤 S404通过以下步骤实现： 通过 TDF会话， 上报检测到的应用信息给策略服 务器。 在步骤 S404之前， 还包括如下步骤： 当业务数据流使用的 IP地址与 IP地址相匹 配， 并且业务数据流使用的端口号与端口号集相匹配时， 确定业务数据流与 TDF会话 是关联的； 对业务数据流的应用信息进行检测。
优选地， 在步骤 S404之后， 还包括： 策略服务器根据上报的应用信息进行策略决 定。 本优选实施例中， 策略服务器根据正确上报的应用信息进行策略决定， 保证了策 略的正确性。 优选地， 上述策略服务器包括以下之一： PCRF、 BPCFo 下面将结合实例和附图对本发明实施例的实现过程进行详细描述。 优选实施例一 本优选实施例主要描述在非漫游场景下， UE接入固定宽带接入网后采用业务分流 方式访问业务场景下进行策略控制的流程， 其中， TDF与 PCRF交互。 如图 5所示， 包括如下的步骤 S502至步骤 S518。 步骤 S502， UE 接入固定宽带接入网， 执行基于 3GPP 的 EAP 接入认证 （即The EPS supports interworking with non-3GPP systems (as shown in FIG. 1), wherein interworking with non-3GPP systems is implemented through an S2a/b/c interface, and the P-GW acts as an anchor between 3GPP and non-3GPP systems. In the system architecture diagram of EPS, non-3GPP system access is divided into untrusted non-3GPP access and trusted non-3GPP access, wherein untrusted non-3GPP access requires evolved packet data gateway (Evolved Packet Data Gateway) , referred to as ePDG) is connected to the P-GW, the interface between the ePDG and the P-GW is S2b; the trusted non-3GPP access can be directly connected to the P-GW through the S2a interface, and the S2a interface adopts the proxy mobile Internet protocol version 6 (Proxy Mobile IP version 6, referred to as PMIPv6) protocol for information exchange; In addition, the S2c interface provides user plane related control and mobility support between the user equipment (User Equipment, UE for short) and the P-GW. The supported mobility management protocol is Mobile IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6), which can be used for untrusted non-3GPP and trusted non-3GPP access. Wireless Local Area Network (WLAN) can be used as a non-3GPP system to access the Evolved Packet Core (EPC). This involves fixed-line mobile convergence (Fixed Mobile) that many operators pay attention to. Convergence, referred to as FMC, is interconnected. Currently, the industry is conducting research on the interconnection of the Fixed Broadband Access Network and the EPC. Two ways of accessing the service are considered: one is to directly access the service through the fixed network (also called traffic offload), and the other is to access the service through the 3GPP core network. Taking S2b as an example, as shown in Figure 2, operators can transmit some services through EPS according to the characteristics of the service, while another part of the industry Services (such as: Internet services, including services on the streaming service platform of the mobile network) can be directly offloaded from the WLAN to reduce the traffic load on the 3GPP core network. FIG. 3 is a schematic structural diagram of a mobile terminal directly performing service offload policy control by using a WLAN according to the related art, a 3GPP policy and charging rule function (PCRF) and a broadband policy control function (Broadband Policy Control Function, Referred to as BPCF), policy interworking is implemented to implement policy control for the UE. In addition, the traffic detection function (Traffic Detection Function, referred to as TDF) is deployed in the network (ie, after the BNG/BRAS) to detect the service information accessed by the UE, and is used for policy decision of the PCRF or the BPCF. In the Solicited Reporting mode, the PCRF or the BPCF needs to establish a TDF session for each IP Connectivity Access Network (IP-CAN) session of the UE and the TDF, so that the TDF reports the UE. Business information accessed through the IP-CAN. However, when the UE accesses the network through the routing mode RG, the TDF cannot determine the detected service because the IP addresses used by the UE accessed by the same RG are the same (that is, the local IP address). Which IP-CAN session, even which UE accesses the service, cannot report the service information to the PCRF corresponding to the UE or the IP-CAN session, and thus cannot implement policy decision and policy control. SUMMARY OF THE INVENTION The present invention provides an application information reporting method and apparatus, so as to solve at least the problem that the UE cannot correctly report the detected application information when the UE performs service offloading through the fixed broadband access network. According to an aspect of the present invention, an application information reporting method is provided, including: receiving an IP address of an RG and a port number set reserved by the RG for the UE; and reporting the detected application information according to the IP address and the port number set. Preferably, the IP address of the receiving RG and the set of port numbers reserved by the RG for the UE include: receiving a TDF session message from the policy server carrying the RG-based IP address and the RG reserved port number set for the UE, where the RG IP address The set of port numbers reserved by the address and RG for the UE is used to identify the TDF session. Preferably, the reported application information is reported according to the IP address and the port number set, and the detected application information is reported to the policy server by using the TDF session. Preferably, before the detected application information is reported to the policy server by using the TDF session, the method further includes: when the IP address used by the service data stream matches the IP address, and the port number used by the service data stream matches the port number set. When it is determined that the service data flow is associated with the TDF session; the application information of the service data flow is detected. Preferably, after the reported application information is reported according to the IP address and the port number set, the method further includes: the policy server performing policy determination according to the reported application information. Preferably, the policy server comprises one of the following: PCRF, BPCF. According to another aspect of the present invention, an application information reporting apparatus is provided, including: a receiving module, configured to receive an IP address of an RG and a port number set reserved by the RG for the UE; and a reporting module, configured to be based on the IP address and the port The set of numbers, report the detected application information. Preferably, the receiving module includes: a receiving submodule, configured to receive a TDF session setup message from the policy server that carries the RG-based IP address and the RG reserved port number set for the UE, where the RG IP address and the RG are UE pre- The set of port numbers that are left uniquely identifies the TDF session. Preferably, the reporting module includes: a reporting sub-module, configured to report the detected application information to the policy server through the TDF session. Preferably, the apparatus further includes: a determining module, configured to determine that the service data stream and the TDF session are determined when the IP address used by the service data stream matches the IP address, and the port number used by the service data stream matches the port number set Is associated; the detection module is configured to detect application information of the service data flow. In the present invention, the TDF determines the UE to access the service according to the IP address and port number set provided by the policy server, so that the detected application information can be correctly reported to the policy server. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a network structure diagram of a 3GPP network interworking with a non-3GPP network according to the related art; FIG. 2 is a network structure diagram of a mobile terminal performing service offloading and accessing EPC through a WLAN according to the related art; FIG. 4 is a schematic diagram of an application information reporting method according to an embodiment of the present invention; FIG. 4 is a flowchart of an application information reporting method according to an embodiment of the present invention; 5 is an interaction flowchart of an application information reporting method according to a preferred embodiment of the present invention; FIG. 6 is an interaction flowchart of an application information reporting method according to a preferred embodiment of the present invention; FIG. 7 is an application according to an embodiment of the present invention. FIG. 8 is a block diagram showing the structure of an application information reporting apparatus according to a preferred embodiment of the present invention; FIG. 9 is a block diagram showing the structure of an application information reporting apparatus according to a preferred embodiment of the present invention; A block diagram of a structure of an application information reporting apparatus according to a third preferred embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. The embodiment of the present invention provides an application information reporting method. FIG. 4 is a flowchart of an application information reporting method according to an embodiment of the present invention. As shown in FIG. 4, the following steps S402 to S404 are included. Step S402, receiving an IP address of the RG and a set of port numbers reserved by the RG for the UE. Step S404, reporting the detected application information according to the IP address and the port number set. In the related art, when the UE performs service offloading through the fixed broadband access network, the detected application information cannot be correctly reported. In the embodiment of the present invention, the TDF determines the UE to access the service according to the IP address and the port number set provided by the policy server, so that the detected application information can be correctly reported to the policy server. Step S402 is implemented by: receiving a TDF session establishment request message from the policy server that carries the RG-based IP address and the RG reserved for the UE, where the RG IP address and the RG are reserved for the UE. The port number set is used to uniquely identify the TDF session. Step S404 is implemented by the following steps: Reporting the detected application information to the policy server through the TDF session. Before step S404, the method further includes the following steps: determining that the service data stream is associated with the TDF session when the IP address used by the service data stream matches the IP address, and the port number used by the service data stream matches the port number set. ; Detecting application information of the business data stream. Preferably, after step S404, the method further includes: the policy server performing policy determination according to the reported application information. In the preferred embodiment, the policy server performs policy decision according to the correctly reported application information, thereby ensuring the correctness of the policy. Preferably, the foregoing policy server includes one of the following: PCRF, BPCFo The implementation process of the embodiment of the present invention will be described in detail below with reference to the examples and the accompanying drawings. The preferred embodiment is described in the following. In the non-roaming scenario, the UE controls the process of performing policy control in the service scenario after the UE accesses the fixed broadband access network, and the TDF interacts with the PCRF. As shown in FIG. 5, the following steps S502 to S518 are included. Step S502, the UE accesses the fixed broadband access network, and performs 3GPP-based EAP access authentication (ie,
3GPP-based接入认证）。 RG为 UE分配私有 IP地址，同时 RG会为该 UE预留 NA(P)T 转换后的端口号集。 RG将 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以及 RG为该 UE预留的端口号集发送给 BNG/BRAS或者 BBF AAA。 步骤 S504， BNG将 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以 及 RG为该 UE预留的端口号集发送给 BPCF。 步骤 S506， BPCF向 PCRF发起 S9*会话建立操作。 BPCF将 UE的用户标识， NA(P)T 后的 IP地址（即本地 IP地址）以及 RG为该 UE预留的端口号集发送给 PCRF。 PCRF 向 BPCF返回确认消息， 该确认消息可能携带默认策略， 包括策略和计费控制（Policy and Charging Control, 简称为 PCC)规则或服务质量（Quality of Service, 简称为 QoS) 规则。 步骤 S508， PCRF根据配置或从用户签约数据库 （Subscription Profile Repository, 简称为 SPR) 获得的文档配置选项决定与 TDF之间建立 TDF会话。 PCRF向 TDF发 送 TDF会话建立请求消息， 携带 ADC规则。 同时 PCRF会向 TDF提供本地 IP地址 和端口号集。 步骤 S510， UE采用 RG分配的私有 IP地址和通信对端进行应用层协商， 进行业 务访问。 消息经过 RG NA(P)T后， 地址将转换成本地 IP地址， 端口号将选择 RG在 步骤 S502中为该 UE预留的端口号集中的一个或多个。
步骤 S512， TDF根据 ADC规则对业务数据流进行检测。本地 IP地址和端口号集 可以唯一标识一个 TDF会话， 而 ADC规则是和 TDF会话是关联的。 当 TDF进行应 用检测时， TDF根据业务数据流的源 IP地址、 源端口号（针对上行数据）或业务数据 流的目的 IP地址、 目的端口号 （针对下行数据） 来确定该业务数据流是跟哪个 TDF 会话关联的 （即业务数据流的 IP地址与 TDF会话的 IP地址相同， 端口号属于 TDF 会话的端口号集合的子集）， 也可以确定根据哪些 ADC规则进行业务检测。 一旦检测 到与 ADC规则匹配的业务时， TDF也可以确定通过哪个 TDF会话向 PCRF上报检测 的应用标识和流描述信息等。 步骤 S514， TDF检测到与 ADC规则匹配的业务数据流时， TDF通过步骤 S508 建立的会话向 PCRF上报应用标识 Application ID以及可选的流描述信息，如果该业务 数据流的流描述信息是可推导的， 即 TDF通过与业务数据流使用的 IP地址和端口号 匹配的 TDF会话上报应用信息。 步骤 S516， PCRF根据 TDF上报的应用信息、用户签约和网络策略等进行策略决 定。 步骤 S518， PCRF向 BPCF提供策略， 固定宽带接入网执行策略， 包括执行接纳 控制。 需要说明的是， 步骤 S504也可以由 BBF AAA触发， 由 BBF AAA向 BPCF提供 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以及 RG为该 UE预留的端 口号集。 优选实施例二 本优选实施例主要描述在非漫游场景下， UE接入固定宽带接入网后采用业务分流 方式访问业务场景下进行策略控制的流程， 其中， TDF与 BPCF交互。 如图 6所示， 包括如下的步骤 S602至步骤 S620。 步骤 S602， UE 接入固定宽带接入网， 执行基于 3GPP 的 EAP 接入认证 （即 3GPP-based接入认证）。 RG为 UE分配私有 IP地址，同时 RG会为该 UE预留 NA(P)T 转换后的端口号集。 RG将 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以及 RG为该 UE预留的端口号集发送给 BNG/BRAS或者 BBF AAA。 步骤 S604， BNG将 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以 及 RG为该 UE预留的端口号集发送给 BPCF。
步骤 S606， BPCF向 PCRF发起 S9*会话建立操作。 BPCF将 UE的用户标识， NA(P)T 后的 IP地址（即本地 IP地址）以及 RG为该 UE预留的端口号集发送给 PCRF。 PCRF 向 BPCF返回确认消息， 该确认消息可能携带默认策略,包括 PCC规则或 QoS规则。 若 PCRF根据网络策略或从 SPR获得的文档配置选项决定需要对 Offload业务访问进 行应用检测， 则 PCRF还向 BPCF提供 ADC规则。 步骤 S608， 若 BPCF从 PCRF获得 ADC规则， 贝 U BPCF与 TDF之间建立 TDF 会话。 BPCF向 TDF发送 TDF会话建立请求消息， 携带 ADC规则。 同时 BPCF会向 TDF提供本地 IP地址和端口号集。 步骤 S610， UE采用 RG分配的私有 IP地址和通信对端进行应用层协商， 进行业 务访问。 消息经过 RG NA(P)T后， 地址将转换成本地 IP地址， 端口号将选择 RG在 步骤 S602中为该 UE预留的端口号集中的一个或多个。 步骤 S612， TDF根据 ADC规则对业务数据流进行检测。本地 IP地址和端口号集 可以唯一标识一个 TDF会话， 而 ADC规则是和 TDF会话是关联的。 当 TDF进行应 用检测时， TDF根据业务数据流的源 IP地址、 源端口号（针对上行数据）或业务数据 流的目的 IP地址、 目的端口号 （针对下行数据） 来确定该业务数据流是跟哪个 TDF 会话关联的 （即业务数据流的 IP地址与 TDF会话的 IP地址相同， 端口号属于 TDF 会话的端口号集合的子集）， 也可以确定根据哪些 ADC规则进行业务检测。 一旦检测 到与 ADC规则匹配的业务时， TDF也可以确定通过哪个 TDF会话向 PCRF上报检测 的应用标识和流描述信息等。 步骤 S614， TDF检测到与 ADC规则匹配的业务数据流时， TDF通过步骤 S608 建立的会话向 BPCF上报应应用标识 Application ID以及可选的流描述信息，如果该业 务数据流的流描述信息是可推导的， 即 TDF通过与业务数据流使用的 IP地址和端口 号匹配的 TDF会话上报应用信息。 步骤 S616， BPCF向 PCRF提供 TDF上报的应用标识以及可选的流描述信息。 步骤 S618， PCRF根据 BPCF上报的应用信息、 用户签约和网络策略等进行策略 决定。 步骤 S620， PCRF向 BPCF提供策略， 包括 PCC规则或 QoS规则， 固定宽带接 入网执行策略， 包括执行接纳控制。
需要说明的是， 步骤 S604也可以由 BBF AAA触发， 由 BBF AAA向 BPCF提供 UE的用户标识， NA(P)T后的 IP地址 （即本地 IP地址） 以及 RG为该 UE预留的端 口号集。 需要说明的是， 在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的 计算机系统中执行， 并且， 虽然在流程图中示出了逻辑顺序， 但是在某些情况下， 可 以以不同于此处的顺序执行所示出或描述的步骤。 本发明实施例还提供了一种应用信息上报装置， 该应用信息上报装置可以用于实 现上述应用信息上报方法。图 7是根据本发明实施例的应用信息上报装置的结构框图， 如图 7所示， 包括接收模块 72和上报模块 74。 其中， 接收模块 72， 设置为接收 RG的 IP地址和 RG为 UE预留的端口号集； 上 报模块 74， 连接至接收模块 72， 设置为根据接收模块 72接收的 IP地址和端口号集， 上报检测到的应用信息。 图 8是根据本发明优选实施例一的应用信息上报装置的结构框图， 如图 8所示， 接收模块 72包括接收子模块 722，设置为接收来自策略服务器的携带有 RG的 IP地址 和 RG为 UE预留的端口号集的 TDF会话建立请求消息， 其中， RG的 IP地址和 RG 为 UE预留的端口号集用于唯一标识 TDF会话。 图 9是根据本发明优选实施例二的应用信息上报装置的结构框图， 如图 9所示， 上报模块 74包括上报子模块 742，连接至接收子模块 722，设置为通过接收子模块 722 接收的 RG的 IP地址和 RG为 UE预留的端口号集唯一标识的 TDF会话，上报检测到 的应用信息给策略服务器。 图 10是根据本发明优选实施例三的应用信息上报装置的结构框图，如图 10所示， 上述应用信息上报装置还包括： 确定模块 76， 连接至接收模块 72， 设置为当业务数据 流使用的 IP地址与 IP地址相匹配， 并且业务数据流使用的端口号与端口号集相匹配 时， 确定业务数据流与 TDF会话是关联的； 检测模块 78， 连接至确定模块 76， 设置 为在确定模块 76确定业务数据流与 TDF会话关联之后， 对业务数据流的应用信息进 行检测。 需要说明的是，装置实施例中描述的应用信息上报装置对应于上述的方法实施例， 其具体的实现过程在方法实施例中已经进行过详细说明， 在此不再赘述。
综上所述， 根据本发明的上述实施例， 提供了一种应用信息上报方法及装置。 本 发明中， TDF根据策略服务器提供的 IP地址和端口号集， 以确定是哪个 UE访问的业 务， 从而可以正确上报检测到的应用信息给策略服务器。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 或者将它们分别制作成各个集成电路模 块， 或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明 不限制于任何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。
3GPP-based access authentication). The RG allocates a private IP address to the UE, and the RG reserves the NA(P)T converted port number set for the UE. The RG sends the UE's user identity, the IP address after NA(P)T (ie, the local IP address), and the set of port numbers reserved by the RG for the UE to the BNG/BRAS or BBF AAA. Step S504, the BNG sends the user identifier of the UE, the IP address after the NA(P)T (ie, the local IP address), and the set of port numbers reserved by the RG for the UE to the BPCF. Step S506, the BPCF initiates an S9* session establishment operation to the PCRF. The BPCF sends the UE's user identity, the IP address after NA(P)T (ie, the local IP address), and the set of port numbers reserved by the RG for the UE to the PCRF. The PCRF returns an acknowledgment message to the BPCF. The acknowledgment message may carry a default policy, including a Policy and Charging Control (PCC) rule or a Quality of Service (QoS) rule. Step S508, the PCRF determines to establish a TDF session with the TDF according to a configuration or a document configuration option obtained from a Subscription Profile Repository (SPR). The PCRF sends a TDF session establishment request message to the TDF, carrying the ADC rules. At the same time, the PCRF will provide the TDF with a local IP address and port number set. Step S510: The UE performs application layer negotiation by using the private IP address allocated by the RG and the communication peer to perform service access. After the message passes RG NA(P)T, the address will be converted to the local IP address, and the port number will select one or more of the port number sets reserved by the RG for the UE in step S502. Step S512, the TDF detects the service data flow according to the ADC rule. The local IP address and port number set can uniquely identify a TDF session, and the ADC rules are associated with the TDF session. When the TDF performs application detection, the TDF determines that the service data flow is based on the source IP address of the service data flow, the source port number (for uplink data), or the destination IP address of the service data flow, and the destination port number (for downlink data). Which TDF session is associated (ie, the IP address of the service data stream is the same as the IP address of the TDF session, and the port number belongs to a subset of the port number set of the TDF session), it is also possible to determine which ADC rules to perform service detection based on. Once the service matching the ADC rule is detected, the TDF can also determine which TDF session to report the detected application identifier and flow description information to the PCRF. Step S514, when the TDF detects the service data flow that matches the ADC rule, the TDF reports the application identifier Application ID and the optional flow description information to the PCRF through the session established in step S508, if the flow description information of the service data flow is derivable That is, the TDF reports the application information through the TDF session that matches the IP address and port number used by the service data flow. Step S516, the PCRF determines the policy according to the application information reported by the TDF, the user subscription, and the network policy. Step S518, the PCRF provides a policy to the BPCF, and the fixed broadband access network performs the policy, including performing admission control. It should be noted that step S504 may also be triggered by the BBF AAA, and the BBF AAA provides the user identifier of the UE to the BPCF, the IP address after the NA(P)T (ie, the local IP address), and the port number reserved by the RG for the UE. set. The preferred embodiment is described in the following. The preferred embodiment mainly describes a process of performing policy control in a service scenario in which a UE accesses a fixed broadband access network and accesses a service in a non-roaming scenario. The TDF interacts with the BPCF. As shown in FIG. 6, the following steps S602 to S620 are included. Step S602: The UE accesses the fixed broadband access network, and performs 3GPP-based EAP access authentication (ie, 3GPP-based access authentication). The RG allocates a private IP address to the UE, and the RG reserves the NA(P)T converted port number set for the UE. The RG sends the UE's user identity, the IP address after NA(P)T (ie, the local IP address), and the set of port numbers reserved by the RG for the UE to the BNG/BRAS or BBF AAA. Step S604, the BNG sends the user identifier of the UE, the IP address after the NA(P)T (that is, the local IP address), and the set of port numbers reserved by the RG for the UE to the BPCF. Step S606, the BPCF initiates an S9* session establishment operation to the PCRF. The BPCF sends the UE's user identity, the IP address after NA(P)T (ie, the local IP address), and the set of port numbers reserved by the RG for the UE to the PCRF. The PCRF returns an acknowledgement message to the BPCF, which may carry a default policy, including PCC rules or QoS rules. If the PCRF determines that application detection is required for Offload service access according to the network policy or the document configuration option obtained from the SPR, the PCRF also provides an ADC rule to the BPCF. Step S608, if the BPCF obtains the ADC rule from the PCRF, a TDF session is established between the Bay U BPCF and the TDF. The BPCF sends a TDF session establishment request message to the TDF, carrying the ADC rules. At the same time, BPCF will provide the TDF with a local IP address and port number set. Step S610: The UE performs application layer negotiation by using the private IP address allocated by the RG and the communication peer to perform service access. After the message passes RG NA(P)T, the address will be converted to the local IP address, and the port number will select one or more of the port number sets reserved by the RG for the UE in step S602. Step S612, the TDF detects the service data flow according to the ADC rule. The local IP address and port number set can uniquely identify a TDF session, and the ADC rules are associated with the TDF session. When the TDF performs application detection, the TDF determines that the service data flow is based on the source IP address of the service data flow, the source port number (for uplink data), or the destination IP address of the service data flow, and the destination port number (for downlink data). Which TDF session is associated (ie, the IP address of the service data stream is the same as the IP address of the TDF session, and the port number belongs to a subset of the port number set of the TDF session), it is also possible to determine which ADC rules to perform service detection based on. Once the service matching the ADC rule is detected, the TDF can also determine which TDF session to report the detected application identifier and flow description information to the PCRF. In step S614, when the TDF detects the service data flow that matches the ADC rule, the TDF reports the application identification application ID and the optional flow description information to the BPCF through the session established in step S608, if the flow description information of the service data flow is Derived, that is, the TDF reports application information through a TDF session that matches the IP address and port number used by the service data flow. Step S616, the BPCF provides the PCRF with the application identifier reported by the TDF and optional flow description information. Step S618: The PCRF performs policy determination according to the application information reported by the BPCF, the user subscription, and the network policy. Step S620, the PCRF provides a policy to the BPCF, including a PCC rule or a QoS rule, and the fixed broadband access network performs the policy, including performing admission control. It should be noted that step S604 may also be triggered by the BBF AAA, and the BBF AAA provides the user identifier of the UE to the BPCF, the IP address after the NA(P)T (ie, the local IP address), and the port number reserved by the RG for the UE. set. It should be noted that the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein. The embodiment of the present invention further provides an application information reporting device, where the application information reporting device can be used to implement the application information reporting method. FIG. 7 is a structural block diagram of an application information reporting apparatus according to an embodiment of the present invention. As shown in FIG. 7, the receiving module 72 and the reporting module 74 are included. The receiving module 72 is configured to receive the IP address of the RG and the port number set reserved by the RG for the UE. The reporting module 74 is connected to the receiving module 72, and is configured to report according to the IP address and port number set received by the receiving module 72. Detected application information. FIG. 8 is a structural block diagram of an application information reporting apparatus according to a preferred embodiment of the present invention. As shown in FIG. 8, the receiving module 72 includes a receiving submodule 722 configured to receive an RG-carrying IP address and RG from the policy server. The TDF session establishment request message of the port number set reserved by the UE, where the IP address of the RG and the port number set reserved by the RG for the UE are used to uniquely identify the TDF session. FIG. 9 is a structural block diagram of an application information reporting apparatus according to a second embodiment of the present invention. As shown in FIG. 9, the reporting module 74 includes a reporting sub-module 742 connected to the receiving sub-module 722 and configured to be received by the receiving sub-module 722. The RG's IP address and the RG are the TDF sessions uniquely identified by the port number set reserved by the UE, and the detected application information is reported to the policy server. FIG. 10 is a structural block diagram of an application information reporting apparatus according to a preferred embodiment of the present invention. As shown in FIG. 10, the application information reporting apparatus further includes: a determining module 76 connected to the receiving module 72, configured to use when the service data stream is used. The IP address matches the IP address, and when the port number used by the service data stream matches the port number set, it is determined that the service data flow is associated with the TDF session; the detecting module 78 is connected to the determining module 76, and is set to determine After determining that the service data flow is associated with the TDF session, the module 76 detects the application information of the service data flow. It should be noted that the application information reporting device described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and details are not described herein again. In summary, according to the above embodiments of the present invention, an application information reporting method and apparatus are provided. In the present invention, the TDF determines the UE to access the service according to the IP address and port number set provided by the policy server, so that the detected application information can be correctly reported to the policy server. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.