WO2013013541A1 - 会话关联方法、装置和*** - Google Patents
会话关联方法、装置和*** Download PDFInfo
- Publication number
- WO2013013541A1 WO2013013541A1 PCT/CN2012/077080 CN2012077080W WO2013013541A1 WO 2013013541 A1 WO2013013541 A1 WO 2013013541A1 CN 2012077080 W CN2012077080 W CN 2012077080W WO 2013013541 A1 WO2013013541 A1 WO 2013013541A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- session
- address
- port number
- pcrf
- bpcf
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
-
- 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/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- 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/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
-
- 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/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2517—Translation of Internet protocol [IP] addresses using port numbers
-
- 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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
Definitions
- the present invention relates to the field of mobile communications, and in particular to a session association method, apparatus, and system.
- the Evolved Packet System (EPS) of the 3rd Generation Partnership Project (3GPP) is evolved by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
- MME Mobility Management Entity
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- HSS Home Subscriber Server
- 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.
- 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) , 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 PMIPv6 (Proxy Mobile IP version 6, proxy mobile The IP protocol version 6) protocol exchanges information; in addition, the S2c interface provides user plane-related control and mobility support between the user equipment (User Equipment, UE) and the P-GW, and the supported mobility management protocol.
- Evolved Packet Data Gateway Evolved Packet Data Gateway
- Wireless Local Area Network can be used as a non-3GPP system to access EPS.
- FCC Fixed Mobile Convergence
- the interworking and address allocation technologies are as follows:
- the residential gateway (RG) is a routing mode and supports network address (port number) translation (Network Address (Port) Translation, NA(P)T).
- the RG can obtain the international mobile subscriber identity (International Mobile Subscriber Identity) in the process of performing the 3GPP-based Extended Extensible Authentication Protocol (EAP) authentication process. (IMSI) or Network Access Identity (NAI, Network Access Identity) 0
- IMSI International Mobile Subscriber Identity
- NAI Network Access Identity
- the RG establishes the NA(P)T entry table, it establishes the IMSI and port number set (when N is equal to 1, the port number is not assigned) and the local IP address.
- the association relationship (referred to as: user identification association table) is shown in Figure 2, where the port number set When (N is equal to 1, the port number is not assigned) and the local IP address is RG( ⁇ ) ⁇ after the RG is converted.
- the RG also supports transmitting the user identity association table to the Broadband Network Gateway I Broadband Remote Access Server (BNG/BRAS) through the Radius message.
- BNG/BRAS Broadband Network Gateway I Broadband Remote Access Server
- the BNG/BRAS can obtain the IMSI/NAI as an authenticator in performing the 3GPP-based EAP authentication process.
- the BNG/BRAS assigns a public network address to the mobile terminal as the local IP address
- the BNG/BRAS establishes the association between the IMSI/NAI and the local IP address, and does not include the port number set; otherwise, BNG/BRAS needs to support NA(P)T, and the association needs to include a set of port numbers (as shown in Figure 2).
- the EPC Evolved Packet Core
- the private address assigned by the RG, and the external communication is the public address plus the port number after the RG conversion. Because the terminal may have different services, and different services occupy different port numbers, that is, when a terminal has multiple services at the same time, the terminal has a public IP address plus a set of port numbers. When another terminal accesses the RG, the RG translated address is also the IP public address, but the set of port numbers is different. The public address and port number set will be reported to BNG/BRAS/AAA.
- the service offloading technology is as follows: The terminal introduced in the above interworking part has multiple services at the same time, including services that are offloaded from the WLAN and services that are routed through the EPC.
- the services that are offloaded from the WLAN and the services that are routed through the EPC are as follows:
- the user accesses multiple services at the same time due to the diversity of user services. If the services pass through the core network of the 3GPP, the data traffic of the core network is increased. Loads, and multiple services preempt the limited network resources, may not guarantee the quality of service with high QoS requirements. Therefore, it is necessary to effectively divert the business.
- S2b as an example, as shown in Figure 3
- operators can transmit some services through EPS according to the characteristics of services, while other services (such as Internet services, including services on the streaming media service platform of mobile networks) can directly Traffic off from the WLAN to reduce the traffic load on the 3GPP core network.
- the different services that are offloaded from the WLAN occupy multiple different port numbers in the port number set, and the data packets routed through the EPC are all encapsulated in the IPsec tunnel, and one of the port number sets is occupied.
- the port number The policy control technology is as follows: In the deep convergence of the FMC architecture, when the mobile terminal directly performs service offloading through the WLAN, the policy control server or the accounting server of the 3GPP network still issues specific policy control related to the mobile terminal to the mobile terminal.
- the charging decision is made to the fixed network, for example: policy control or charging for a specific service type of a mobile terminal; after the network element of the fixed network receives the policy decision of the policy control server or the charging decision of the charging server, The collection of policy control or billing information associated with a particular mobile terminal is performed.
- the broadband policy control function establishes a policy session with the BPCF (Broadband Forum Policy Control Function), and the BPCF establishes a session with the 3GPP policy control entity PCRF.
- the policy is obtained from the PCRF and sent to the BNG/BRAS.
- the service establishment request of the mobile terminal When the service establishment request of the mobile terminal is received, or when the service detection function is detected by the TDF (Traffic Detection Function), it interacts with the PCRF to request the PCRF whether the service is accepted or not.
- TDF Traffic Detection Function
- BPCF needs to be able to download the user-based policy from the PCRF and report the user-based information to the PCRF
- the PCRF Establishing an Rx session/AF session with the AF (or establishing a Sd session/TDF session with the PCRF and the TDF)
- the PCRF establishes an S9* session with the fixed network, and the PCRF needs to be able to perform an association session based on the end user level before the policy is transmitted (BPCF associated AF)
- the scenario of a session/Rx session (or Sd session/TDF session) and a fixed network policy session is also required by this).
- the S9* session may also be referred to as an S9a session, and the S9* interface is also referred to as an S9a interface.
- the S9a session refers to a gateway control session on the S9a interface, or an IP-CAN session, or both.
- the traditional association session of the policy control and charging technology may be: according to IP address management, or according to user identity association. (eg IMSI or NAI), or associated according to the PDN identity (eg APN). But here, this information is not enough, because there is no user ID on Rx/Sd, and there is no APN information.
- IP address information the IP address of the terminal is public and is an address shared by multiple UEs under the same RG (see analysis above). So simply correlating sessions based on addresses can lead to errors. It can be seen from the above analysis that the mobile terminal directly accesses the mobile network service scenario through the fixed network, and the above-mentioned session association mode has the problem of inaccurate association. In the related art, the mobile terminal directly accesses the mobile network service scenario through the fixed network, and the session association is inaccurate. The problem has not yet been put forward an effective solution.
- a session association method including: a PCRF or a BPCF receiving a first session from a fixed network; wherein the first session carries a set of IP addresses and port numbers; The BPCF receives the second session from the application function entity AF or the service detection function TDF; wherein the second session carries the IP address and the port number information; the PCRF or the BPCF associates the first session and the second according to the foregoing IP address and port number information. Conversation.
- the first session includes one of the following: a message triggering an S9* session, an S9* session, an S9 session, or a fixed network policy session; the second session is an Rx session or an AF session, or an Sd session, or a TDF session.
- the foregoing PCRF or BPCF associates the first session and the second session according to the IP address and the port number information.
- the PCRF or the BPCF determines that the first session and the second session meet the following two conditions, and associates the first session with the second session: 1) The IP address of the first session is the same as the IP address of the second session; 2) The port number in the port number information of the second session is an element in the set of port numbers of the first session.
- the method further includes: the PCRF or the BPCF formulating a policy for the service according to the association relationship between the first session and the second session, and issuing a policy.
- the method further includes: the PCRF or the BPCF saves the IP address and the port number in a manner that the user identifies the association table.
- the PCRF or the BPCF receives the first session from the fixed network, and includes one of the following manners: when the terminal is initially accessed, The network initiates a first session establishment process, where the first session carries a set of IP addresses and port numbers initially allocated by the fixed network for the terminal; when the fixed network updates the IP address and/or the port number set of the terminal, the first session modification process is initiated, A session carries a modified set of IP addresses and/or port numbers.
- a session association apparatus configured to receive a first session from a fixed network; wherein, the first session Carrying a set of IP addresses and port numbers; the second receiving module is configured to receive a second session from the AF or TDF; wherein the second session carries the IP address and port number information; the association module is set to be based on the IP address and the port The number information is associated with the first session and the second session.
- the foregoing association module includes: a determining unit, configured to determine whether the IP address carried in the first session is the same as the IP address carried in the second session, and whether the port number in the port number information carried in the second session is carried in the first session An element in the set of port numbers; an associating unit, configured to associate the first session and the second session when the judgment result of the determining unit is yes.
- a session association system including a PCRF or a BPCF, and the foregoing device is disposed on a PCRF or a BPCF, the system further includes: a fixed network element, configured to send a first session to the device ; AF or TDF, set to send a second session to the device.
- the session is associated by using the combination of the IP address and the port number to solve the problem that the mobile terminal directly accesses the mobile network service scenario through the fixed network, and the session association is inaccurate.
- the method does not add a new letter. It is compatible with existing protocols, and its development cost is low and easy to implement.
- 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 mobile terminal and a fixed network NA(P)T after the mobile terminal is offloaded by the WLAN service according to the related art.
- FIG. 3 is a schematic diagram of a network structure of a mobile terminal performing service offloading and accessing an EPC through a WLAN according to the related art
- FIG. 4 is an Rx/Sd session and an S9* session according to the related art.
- FIG. 5 is a flowchart of a session association method according to Embodiment 1 of the present invention
- FIG. 6 is a schematic diagram of a session association method according to Example 1 of the present invention;
- FIG. 7 is a schematic diagram of a session association method according to Example 2 of the present invention
- Is a schematic diagram of a session association method according to Example 3 of the present invention
- FIG. 9 is a block diagram showing the structure of a session association apparatus according to Embodiment 2 of the present invention.
- an Rx interface exists between the PCRF and the AF, and a session established between the PCRF and the AF is called an AF session or an Rx session; an Sd interface exists between the PCRF and the TDF, and a relationship between the PCRF and the TDF
- TDF sessions or Sd sessions The words are called TDF sessions or Sd sessions.
- the AF session and the Rx session may be used interchangeably, and the TDF session and the Sd session may be used interchangeably without affecting the essential content of the present invention.
- Embodiment 1 This embodiment provides a session association method. Referring to FIG. 5, the method includes the following steps: Step S502: A PCRF or a BPCF receives a first session from a fixed network, where the first session carries
- the network element in the fixed network includes one of the following: RG, BNG, BRAS, or AAA server (also referred to as AAA for short); Step S504, the PCRF or BPCF receives the second session from the AF (or TDF),
- the second session carries the IP address and port number information.
- the "port number information" described in the foregoing second session may be a single port number, or may be a set of port numbers. In order to express no confusion with the "port number set" of the first session, the address is simply referred to as port number information. It is only necessary to be clear that the possibility of carrying a set of port numbers is not excluded in the second session. The same is true of the following embodiments.
- Step S506 the PCRF or BPCF associates the first session and the second session according to the foregoing IP address and port number information. For example, when the PCRF or BPCF determines that the first session and the second session meet the following two conditions, the first session and the second session are associated:
- the port number in the port number information of the second session is an element in the port number set of the first session. That is, when the IP address carried in the first session is the same as the IP address carried in the second session, and the port number in the port number information carried in the second session is an element of the port number set carried in the first session, the PCRF or BPCF is associated with One session and two sessions. If the IP addresses in the two sessions are different, the two sessions are not associated. If only the IP addresses are the same, the port number in the port number information carried in the second session is not an element in the port number set carried in the first session. Do not associate two sessions.
- the order of checking IP addresses or port numbers can be changed, not necessarily according to the above description: first by address, then by strict order of port numbers.
- the above is only two conditions for listing the associated conversations. There is no order in the order, or even if there is a sequence in the order, the order does not affect the association effect.
- the mechanism for sending the port number to the PCRF or the BPCF in the second session may have at least the following two modes: 1) The second session in the prior art already carries the flow description information, where the flow description information is included in the flow description information.
- the first session in this embodiment includes one of the following: a message triggering an S9* session, an S9* session, an S9 session, or a fixed network policy session; the second session is an Rx session or an AF session, or an Sd session or a TDF session. Among them, S9* is also called S9a session, the same below.
- the session is associated with the combination of the IP address and the port number, which solves the problem that the mobile terminal directly accesses the mobile network service scenario through the fixed network, and the session association is inaccurate.
- the method does not add new signaling.
- This type of session association is also applicable to the case where there is no user identifier on Rx/Sd and no APN information, and it is possible to effectively avoid the occurrence of session error association when the IP addresses of multiple terminals are the same.
- the method further includes: the PCRF or the BPCF formulating a policy for the user-initiated service according to the association relationship between the first session and the second session, and issuing a policy.
- the above method further includes: the PCRF or the BPCF saves the user's IP address and port number set in a manner that the user identifies the association table.
- the method further includes: the PCRF or the BPCF receiving the update session from the fixed network, where the update session carries the changed IP address and port number set of the user; Or BPCF uses the user-changed IP address and port number set to update the IP address and port number set in the user's user identity association table.
- the session association is performed by using the PCRF as an example, and the foregoing method can be briefly described as follows:
- the fixed network initiates a first session to the PCRF, and sends the IP address and port number set to the PCRF;
- AF/TDF establishes a second session with the PCRF, and sends the IP address and port number to the PCRF;
- the PCRF associates the first session and the second session according to the IP address and the port number; for example, the IP address carried in the first session and the second session are the same, and the port number carried in the second session is the port number carried in the first session.
- the PCRF is associated with the first second session; wherein, the first session refers to an S9* session or an S9 session; the second session refers to an Rx session or an AF session, or an Sd session or a TDF session; Taking BPCF as the example of session association, the above method can be briefly described as follows:
- BNG/BRAS/AAA initiates the first session establishment to BPCF, and sends the IP address and port number set to BPCF;
- the AF/TDF establishes a second session with the BPCF, and sends the IP address and port number to the BPCF; 3) the BPCF associates the first session and the second session according to the IP address and the port number; wherein, the first session refers to the BNG
- the BPCF reports the local IP address, port number set and user identifier to the PCRF when establishing/modifying the S9* session;
- the AF/TDF When the AF/TDF establishes an Rx/Sd session or delivers service information through the Rx/Sd interface, it sends the "local IP address and port number" of the service to the PCRF. 4)
- the PCRF is detected as follows if the following two are met:
- the local address sent by AF/TDF is the same as the local address sent on BNG/BRAS/AAA/BPCF;
- the port number sent by the AF/TDF is an element in the set of port numbers sent on the BNG/BRAS/AAA/BPCF;
- the PCRF associates the S9* Session/Fixed Network Policy session with the Rx/Sd session.
- the first session may be the first session initiated in one of the following scenarios:
- the fixed network When the terminal is initially accessed, the fixed network initiates a first session establishment process, where the first session carries a fixed network with an initial set of IP addresses and port numbers (corresponding to instance one and instance two);
- Step 601 The mobile terminal accesses the fixed network and performs EAP connection based on 3GPP.
- the RG of the fixed network can obtain the 3GPP mobile subscriber identity, such as IMSI or NAI, from the 3GPP AAA server.
- the fixed network will complete the assignment of the local IP address, RG, BNG/BRAS AAA (optional) establish and pass the NA(P)T entry table information, and finally the RG, BNG/BRAS AAA (optional) both the user ID and the local IP address,
- the association of the port number set is abbreviated as the user ID association table.
- the table is shown in Figure 4 and will not be described here.
- Step 602 After receiving the fixed network (BNG/BRAS or AAA) trigger, the BPCF obtains a user identity association table, where the user identifier, the local IP address, and the port number set are obtained.
- Step 604 The UE accesses the EPC, and completes the PDN connection establishment process. This step is optional.
- the offload technology in this step means that the data no longer passes through the P-GW in the 3GPP network, and the P-GW is no longer responsible for sending/receiving data to/from the external network, but directly through the fixed network gateway, generally BNG/BRAS sends/receives data to and from the external network.
- This technology is also known as bypass technology or network load offload technology.
- the AF obtains the service information when the application layer negotiates, or the TDF obtains the service information after being detected.
- the AF/TDF finds a suitable PCRF, initiates an Rx/Sd session establishment operation/delivery service information to the PCRF, and carries an address (ie, a local IP address) and a port number of the service.
- the PCRF is implemented according to the association mechanism. The mechanism stated in the example associates the session.
- the service information is then sent to the PCRF through the Rx/Sd session, and the policy is formulated by the PCRF and sent to the fixed network policy execution unit via the S9* session and the fixed network policy session.
- the steps 605-607 are repeated; when other terminals access the fixed network link and access to the RG, the operations of 601-607 are repeated.
- the above scheme is discussed in the S2b access scheme, and in fact the mechanism is also applicable to the S2a/2b/2c access scheme. Described in the steps of the foregoing embodiment is a scenario in which the AF/TDF finds the PCRF of the 3GPP. In fact, there is a possibility that the BPCF of the fixed network found by the AF/TDF, and the corresponding step should be the steps 606a to 607a.
- the AF/TDF finds the appropriate BPCF, initiates Rx/Sd session establishment/sending service information to the BPCF, and carries the address (ie, the local IP address) and the port number of the service; BPCF according to the association mechanism embodiment
- the stated mechanism associates the sessions.
- the service information is then sent to the BPCF through the Rx/Sd session, and then sent by the BPCF to the fixed network policy execution unit.
- the related policy is downloaded to the fixed-layer policy enforcement entity, which is generally BNG/BRASo.
- BNG/BRAS obtains the user-based policy, that is, it has a corresponding for each user identifier.
- Example 2 This example mainly describes the association mechanism of the policy session when the terminal is initially accessed in the roaming scenario. As shown in Figure 7, the following steps are included: Steps 701-702: Same steps 601-602; Step 703: BPCF selects the appropriate vPCRF, the vPCRF is the visited PCRF, and initiates an S9* session establishment operation to the vPCRF.
- the BPCF needs to pass an association table including a user ID, a local IP address, and a set of port numbers to the vPCRF.
- Step 704 The vPCRF selects an appropriate hPCRF, which is a hometown PCRF, and initiates an S9 session establishment operation to the hPCRF.
- the vPCRF needs to pass an association table including a user ID, a local IP address, and a set of port numbers to the hPCRF.
- Step 705 The UE accesses the EPC to complete the PDN connection establishment process. This step is an optional step.
- Step 706 The terminal and the AF perform application layer negotiation.
- the application layer exchanges the application service through the BNG/BRAS network element offload, that is, when the application layer negotiates, the user's address is the local IP address described in steps 602 and 603.
- the AF obtains the service information when the application layer negotiates, or the TDF obtains the service information after being detected.
- Step 707 The AF/TDF finds an appropriate hPCRF, initiates an Rx/Sd session establishment operation to the hPCRF, delivers service information, and carries an address (ie, a local IP address) and a port number of the service.
- Step 708 The hPCRF associates the sessions according to the mechanisms set forth in the association mechanism embodiment.
- the service information is then sent to the PCRF through the Rx/Sd session, and the policy is formulated by the hPCRF and sent to the fixed network policy execution unit via the S9 session and the S9* session and the fixed network policy session.
- steps 706-708 are repeated; when other terminals access the fixed network link and access to the RG, the operations of 701-708 are repeated.
- the above steps 707 to 708 can be specifically implemented by using step 707a and step 708a in FIG. 7 and step 707b and step 708b.
- the solution of this example is discussed in the S2b access scheme. In fact, this mechanism is also applicable to the S2a/2b/2c access scheme. Described in the above example steps is the scenario where AF/TDF finds the 3GPP hPCRF, which is actually possible.
- the vPCRF or BPCF of the fixed network found by AF/TDF the corresponding steps should be step 707a - step 708a and step 707b - step 708b.
- the AF/TDF finds the appropriate vPCRF/BPCF, initiates Rx/Sd session establishment/sending service information to the vPCRF/BPCF, and carries the address (ie, the local IP address) and the port number of the service; vPCRF/
- the BPCF associates the sessions according to the mechanisms stated in the association mechanism embodiment.
- the service information is then sent to the vPCRF and BPCF through the S9 session and the Rx/Sd session, and then sent by the BPCF to the fixed network policy execution unit.
- the related policy is downloaded to the fixed-layer policy enforcement entity, which is generally BNG/BRAS.
- BNG/BRAS obtains the user-based policy, that is, it has a corresponding for each user identifier. Determining the local IP address + port number information, so that when the packet flowing through the BNG/BRAS matches the local IP address + port number information, the BNG/BRAS determines that the data packet is related to the user identity/user. . In this way, the BNG/BRAS can be based on the execution strategy of the user granularity and collect the charging information.
- Example 3 This example describes the operation of updating RG/BNG/BRAS to the Policy Rule Entity (BPCF, v/hPCRF) when the port number set of an end user changes in RG/BNG/BRAS, see Figure 8.
- the update operation includes the following steps: Step 801: The terminal has accessed the fixed network, and one or two of the following connections may have been established: 1. Connection of the fixed network BNG/BRAS to the packet data network/internet, 2. EPC to PDN connection for packet data network/internet.
- Step 802 The port number assignment on RG/BNG/BRAS changes. There are many reasons for the change of the port number assignment, for example, the configuration information is changed, or the user or other user initiates a service, and the port number is preempted/resigned.
- Step 803 The BNG/BRAS or AAA updates the user identity association table to the BPCF, including the user identifier, the local IP address, and the port number set.
- Step 804 The BPCF updates the association table of the user identifier, the local IP address, and the port number set to the PCRF through the S9* session. At this point, the update operation is complete.
- the remaining steps 805-807a are performed after the user initiates the service, according to the latest user identification association table for session association and policy formulation/delivery.
- the related mechanism is the same as the process instance one and two, and the related supplementary description is also the example one and The second example is the same and will not be described here.
- Embodiment 2 provides a session association device, which may be set on a policy control entity PCRF or BPCF.
- the device includes the following modules: a first receiving module 92, configured to receive from a fixed network. a first session, where the first session carries a set of IP addresses and port numbers; a second receiving module 94 is configured to receive a second session from the AF/TDF, wherein the second session carries an IP address and a port number
- the association module 96 is connected to the first receiving module 92 and the second receiving module 94, and is configured to associate the first session and the second session according to the foregoing IP address and port number information.
- the association module 96 of this embodiment includes: a determining unit, configured to determine whether an IP address carried in the first session is the same as an IP address carried in the second session; and determining whether the port number in the port number information carried in the second session is It is an element in the port number set carried by the first session; the association unit is connected to the judging unit, and is configured to associate the first session and the second session when the judgment result of the judging unit is yes. If the IP addresses in the two sessions are different, the two sessions are not associated. If only the IP addresses are the same, the port number in the port number information carried in the second session is not an element in the port number set carried in the first session. Nor is it associated with two sessions.
- the first session in this embodiment includes one of the following: a message triggering an S9* session, an S9* session, an S9 session, or a fixed network policy session; and the second session is an Rx/Sd session or an AF/TDF session.
- the session is associated with the combination of the IP address and the port number, which solves the problem that the mobile terminal directly accesses the mobile network service scenario through the fixed network, and the session association is inaccurate.
- the method does not add new signaling. Compatible with existing protocols, low development costs and easy implementation.
- the device includes: a measurement formulation and a lower module, configured to formulate a policy for a user initiated service according to an association relationship between the first session and the second session, and issue a policy.
- the device further includes: a saving module, configured to save the user's IP address and port number set in a manner that the user identifies the association table.
- the foregoing apparatus further includes: an update module configured to receive an update session from the fixed network element, wherein the update session carries the changed IP address and port of the user The set of numbers; and the set of IP addresses and port numbers in the user identification association table of the user is updated using the changed IP address and port number set of the user.
- the first session may be the first session initiated in one of the following scenarios:
- the fixed network When the terminal initially accesses, the fixed network initiates a first session establishment process, where the first session carries a fixed network to initially allocate an IP address and a port number set of the terminal;
- the embodiment further provides a session association system, the system includes a PCRF or a BPCF, and the session association device is disposed on the PCRF or the BPCF, the system further includes: a fixed network element, configured to send the first session to the device; The functional entity AF/TDF, set to send a second session to the device.
- the fixed network element includes one of the following: RG, BNG, BRAS, or AAA server.
- the IP address and the port number (set) carried in the session are used to determine whether the session is associated with each other, that is, whether the session is initiated by the same user, which improves the accuracy of the session association, and solves the problem that the mobile terminal directly accesses the mobile network through the fixed network.
- the session association is inaccurate.
- the method does not add new signaling, is compatible with existing protocols, and has low development cost and is easy to implement.
- This type of session association is also applicable to the case where there is no user identifier on Rx/Sd and no APN information, and it is possible to effectively avoid the occurrence of session error association when the IP addresses of multiple terminals are the same.
- the above embodiment determines whether the session is associated in the combination of the IP address and the port number, effectively avoids the occurrence of the session error association when the IP addresses of the multiple terminals are the same, and does not add a new one.
- Signaling simple to implement.
- 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 and, in some cases, may be different from the order herein.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种会话关联方法、装置和***。其中,该方法包括:PCRF或BPCF接收来自固网的第一会话,其中,该第一会话携带有IP地址和端口号集合;PCRF或BPCF接收来自AF或者业务检测功能TDF的第二会话,其中,该第二会话携带有IP地址和端口号信息;PCRF或BPCF根据用该IP地址和端口号信息关联上述第一会话和第二会话。通过本发明,解决了移动终端通过固网直接访问移动网络业务场景中,会话关联不准确的问题。
Description
会话关联方法、 装置和*** 技术领域 本发明涉及移动通信领域, 具体而言, 涉及一种会话关联方法、 装置和***。 背景技术 第三代合作伙伴计划 (3rd Generation Partnership Project, 3 GPP) 的演进的分组系 统 (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) 组成。 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接口采用 PMIPv6(Proxy Mobile IP version 6, 代理移 动 IP协议版本 6)协议进行信息交互;另夕卜, 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***接 入 EPS, 这涉及到很多运营商关注的固网移动融合(Fixed Mobile Convergence, FMC) 的互连互通问题。 其中, 互联互通及地址分配技术如下: 现有技术中, 在家庭网关 (Residential Gateway, RG) 为路由模式且支持网络地 址 (端口号)翻译 (Network Address (Port) Translation, NA(P)T) 为 N: l (N大于或等 于 1 )时, RG在执行基于 3GPP的扩展的身份验证协议 (Extensible Authentication Protocol EAP) 认证过程中, 作为认证方, 能够获得国际移动签约者标识 (International Mobile Subscriber Identity, IMSI)或者网络接入标识(NAI, Network Access Identity) 0 在 RG 建立 NA(P)T入口表时, 会建立 IMSI和端口号集合(N等于 1时, 不分配端口号) 以 及本地 IP地址的关联关系 (简称为: 用户标识关联表)如图 2所示, 其中, 端口号集
合 (N等于 1时, 不分配端口号) 以及本地 IP地址为 RG进行 ΝΑ(Ρ)Τ转换后的。 并 且, RG也支持通过 Radius消息, 将用户标识关联表传递给宽带网关 /宽带远端接入服 务器 (Broadband Network Gateway I Broadband Remote Access Server, BNG/BRAS)。 在 RG为桥接模式时, BNG/BRAS在执行基于 3GPP的 EAP认证过程中,作为认证者, 能够获得 IMSI/NAI。 通常情况下, BNG/BRAS 为该移动终端会分配一个公网地址作 为本地 IP地址时, 则 BNG/BRAS会建立 IMSI/NAI和本地 IP地址的关联关系, 而不 包含端口号集合; 否则的话, BNG/BRAS需要支持 NA(P)T, 该关联关系则需要包含 端口号集合 (如图 2所示)。 综上所述, 终端在通过 WLAN接入 EPC (Evolved Packet Core, 演进分组交换中 心) 的场景下, 如果 RG作为 NA(P)T, 特别是 N: l的场景, 终端上获取的 IP地址是
RG分配的私有地址,而与外部通讯的是 RG转换后的公有地址外加端口号。因为该终 端可能有不同的业务, 而不同的业务又占有不同的端口号, 也就是说当一个终端同时 拥有多个业务时, 标识该终端的有一个公有 IP地址外加一个端口号的集合。 当另一个 终端接入到该 RG时, RG转换后的地址也是该 IP公有地址, 但是其端口号的集合不 同而已。 该公有地址和端口号集合会上报给 BNG/BRAS/ AAA。 业务分流技术如下: 上述互联互通部分中介绍到的终端同时拥有多个业务, 包括 从 WLAN分流的业务和通过 EPC路由的业务。 其中, 从 WLAN分流的业务和通过 EPC路由的业务是这样的: 由于用户业务的多样性需求, 用户会同时访问多种业务, 如果业务都经过 3GPP的核心网, 不仅增加了核心网的数据流量负荷, 而且多种业务 抢占有限的网络资源, 可能无法保证对 QoS要求高的业务质量。 因此, 对业务采用有 效地分流是有必要的。 以 S2b为例, 如图 3所示, 运营商可以根据业务的特征, 部分 业务通过 EPS传输, 而另外一部分业务(比如: internet业务, 也包括移动网络的流媒 体业务平台上的业务) 可以直接从 WLAN分流, 以降低 3GPP核心网的流量负荷。 其中, 从 WLAN分流的不同业务占用上述端口号集合中的多个不同的端口号, 而 通过 EPC路由的数据包因为都是在 IPsec隧道封装之内的, 会占用端口号集合中的其 中的一个端口号。 策略控制技术如下: 在 FMC架构深度融合的趋势下, 当移动终端通过 WLAN直 接进行业务分流时, 3GPP网络的策略控制服务器或者计费服务器仍然会对移动终端下 发与移动终端相关的具体策略控制或者计费决策给固网, 比如: 针对某个移动终端的 具体业务类型进行策略控制或者计费等; 固网的网元收到策略控制服务器的策略决策 或者计费服务器的计费决策之后, 会执行与具体移动终端相关的策略控制或者计费信 息的收集。
为了支持与具体移动终端相关的策略下发给 BNG/BRAS, 宽带策略控制功能与 BPCF (Broadband Forum Policy Control Function, 宽带论坛策略控制功能) 建立策略 会话, BPCF与 3GPP的策略控制实体 PCRF建立会话并从 PCRF处获取策略, 从而下 发给 BNG/BRAS。 当 WLAN分流的是移动网络的流媒体业务平台时,在现有技术中, AF( Application
Function, 应用功能) 收到移动终端的业务建立请求时, 或者 TDF (Traffic Detection Function, 业务检测功能)检测到业务信息时, 会与 PCRF进行交互, 向 PCRF请求业 务是否接受的决策。 然而,如果想对从 BNG/BRAS直接路由到 internet/PDN的数据进行基于用户级别 的管理和控制, BPCF需要能够从 PCRF下载到基于用户的策略, 并能够向 PCRF上 报基于用户的信息,而且 PCRF与 AF建立 Rx会话 /AF会话(或者 PCRF与 TDF建立 Sd会话 /TDF会话), PCRF与固网建立 S9*会话, PCRF在进行策略传递前需要能够进 行基于终端用户级别地关联会话 (BPCF关联 AF会话 /Rx会话 (或者 Sd会话 /TDF会 话)和固网策略会话的场景同样由此需求)。其中,上述 S9*会话也可以称为 S9a会话, S9*接口也称为 S9a接口, S9a会话是指 S9a接口上的网关控制会话, 或者 IP-CAN会 话, 或者同时指两者。 参见图 4所示的 AF会话 /Rx会话(或者 Sd会话 /TDF会话)和 S9*会话关联机制, 策略控制与计费技术的传统关联会话的方式有: 根据 IP地址管理, 或者根据用户标识 关联 (例如: IMSI或者 NAI), 或者根据 PDN标识 (例如: APN) 关联。 但在这里, 这些信息都不足够, 因为 Rx/Sd上没有用户标识, 也没有 APN信息。 虽然有 IP地址 信息, 但是终端的 IP地址是公有的、 而且是接入到同一个 RG下的多个 UE共用的地 址 (见上述的分析)。 所以单纯根据地址关联会话是会导致错误的。 由上述分析可知, 对于移动终端通过固网直接访问移动网络业务场景, 应用上述 会话关联方式存在关联不准确的问题, 针对相关技术中移动终端通过固网直接访问移 动网络业务场景中, 会话关联不准确的问题, 目前尚未提出有效的解决方案。 发明内容 本发明实施例提供了一种会话关联方法、 装置和***, 以至少解决上述移动终端 通过固网直接访问移动网络业务场景中, 会话关联不准确的问题。 根据本发明实施例的一个方面, 提供了一种会话关联方法, 包括: PCRF或 BPCF 接收来自固网的第一会话; 其中, 该第一会话携带有 IP地址和端口号集合; PCRF或
BPCF接收来自应用功能实体 AF或者业务检测功能 TDF的第二会话; 其中, 该第二 会话携带有 IP地址和端口号信息; PCRF或 BPCF根据上述 IP地址和端口号信息关联 第一会话和第二会话。 上述第一会话包括以下之一: 触发 S9*会话的消息、 S9*会话、 S9会话或者固网 策略会话; 第二会话是 Rx会话或者 AF会话, 或者 Sd会话, 或者 TDF会话,。 上述 PCRF或 BPCF根据 IP地址和端口号信息关联第一会话和第二会话包括: PCRF或 BPCF判断第一会话和第二会话符合以下两个条件时, 关联第一会话和第二 会话: 1 )第一会话的 IP地址与第二会话的 IP地址相同; 2)第二会话的端口号信息 中的端口号是第一会话的端口号集合中的元素。 上述 PCRF或 BPCF关联第一会话和第二会话之后,该方法还包括: PCRF或 BPCF 根据第一会话和第二会话的关联关系, 为业务制定策略, 下发策略。 上述方法还包括: PCRF或 BPCF以用户标识关联表的方式保存 IP地址和端口号 鱼朱 A n 上述 PCRF或 BPCF接收来自固网的第一会话包括以下方式之一: 终端初始接入 时, 固网发起第一会话建立过程, 第一会话携带有固网为终端初始分配的 IP地址和端 口号集合; 固网更新终端的 IP地址和 /或端口号集合时, 发起第一会话修改过程, 第 一会话携带有修改后的 IP地址和 /或端口号集合。 根据本发明实施例的另一方面, 提供了一种会话关联装置, 该装置设置在 PCRF 或 BPCF上, 包括: 第一接收模块, 设置为接收来自固网的第一会话; 其中, 第一会 话携带有 IP地址和端口号集合;第二接收模块,设置为接收来自 AF或者 TDF的第二 会话; 其中, 第二会话携带有 IP地址和端口号信息; 关联模块, 设置为根据 IP地址 和端口号信息关联第一会话和第二会话。 上述关联模块包括: 判断单元, 设置为判断第一会话携带的 IP地址与第二会话携 带的 IP地址是否相同, 以及判断第二会话携带的端口号信息中的端口号是否是第一会 话携带的端口号集合中的元素; 关联单元, 设置为当判断单元的判断结果均为是时, 关联上述第一会话和第二会话。 根据本发明实施例的又一方面, 提供了一种会话关联***, 包括 PCRF或 BPCF, PCRF或 BPCF上设置有上述装置, 该***还包括: 固网网元, 设置为向装置发送第 一会话; AF或者 TDF, 设置为向装置发送第二会话。
通过本发明, 采用采用 IP地址与端口号组合匹配的方式关联会话, 解决了移动终 端通过固网直接访问移动网络业务场景中, 会话关联不准确的问题, 同时, 该方法并 未增加新的信令, 能够与现有协议兼容, 开发成本较低, 易于实现。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1是根据相关技术的 3GPP网络与非 3GPP网络互通的网络结构图; 图 2是根据相关技术的移动终端通过 WLAN业务分流时,移动终端与固网 NA(P)T 之后的 IP地址和端口号集合的关联关系示意图; 图 3是根据相关技术的移动终端通过 WLAN进行业务分流和接入 EPC的网络结 构图; 图 4是根据相关技术的 Rx/Sd会话和 S9*会话关联机制示意图; 图 5是根据本发明实施例 1的会话关联方法流程图; 图 6是根据本发明实例 1的会话关联方法示意图; 图 7是根据本发明实例 2的会话关联方法示意图; 图 8是根据本发明实例 3的会话关联方法示意图; 图 9是根据本发明实施例 2的会话关联装置结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例为了准确地将一个用户发起的多个业务关联起来, 提供了一种会话 关联方法、 装置和***, 适用于移动终端通过固网直接访问移动网络业务场景。 说明: 本发明中, PCRF与 AF之间存在 Rx接口, PCRF与 AF之间建立的会话 称作 AF会话或者 Rx会话; PCRF与 TDF之间存在 Sd接口, PCRF与 TDF之间的会
话称作 TDF会话或者 Sd会话。本发明中 AF会话和 Rx会话可能交替使用, TDF会话 和 Sd会话可能交替使用, 不影响本发明的本质内容。 实施例 1 本实施例提供了一种会话关联方法, 参见图 5, 该方法包括以下步骤: 步骤 S502, PCRF或 BPCF接收来自固网的第一会话, 其中, 该第一会话携带有
IP地址和端口号集合。 其中, 该固网中的网元包括以下之一: RG、 BNG、 BRAS, 或者 AAA服务器(也 可以简称为 AAA); 步骤 S504, 该 PCRF或 BPCF接收来自 AF (或者 TDF) 的第二会话, 其中, 该 第二会话携带有 IP地址和端口号信息。 其中, 上述第二会话中所述的"端口号信息"可能是一个单独的端口号, 也可能是 一组端口号的集合。 为了在表述上与第一会话的"端口号集合"不造成混淆, 该处称简 称端口号信息。 只是需要明确的是, 第二会话中不排除携带端口号集合的可能。 以下 实施例也如此。 步骤 S506, 该 PCRF或 BPCF根据上述 IP地址和端口号信息关联上述第一会话 和第二会话。 例如, PCRF或 BPCF判断第一会话和第二会话符合以下两个条件时, 关联第一会话和第二会话:
1 ) 第一会话的 IP地址与第二会话的 IP地址相同;
2) 第二会话的端口号信息中的端口号是第一会话的端口号集合中的元素。 即当第一会话携带的 IP地址与第二会话携带的 IP地址相同, 且第二会话携带的 端口号信息中的端口号是第一会话携带的端口号集合的元素时, PCRF或 BPCF关联 第一会话和第二会话。 如果两个会话中的 IP地址不同, 则不关联两会话, 如果仅 IP 地址相同, 第二会话携带的端口号信息中的端口号并不是第一会话携带的端口号集合 中的元素, 则也不关联两会话。 上述根据 IP地址和端口号关联会话的机制中, 检查 IP地址或端口号的先后顺序 可以更改, 未必按照上述的描述: 先按地址关联, 之后再按端口号关联的严格顺序。 上述只是罗列关联会话的两个条件, 没有次序上的先后, 或者说, 次序上即使有先后, 该先后顺序也不影响关联效果。 以下实施例也如此。
其中, 上述步骤 504中, 第二会话中, 端口号发送给 PCRF或 BPCF的机制可以 有至少以下两种方式: 1 )现有技术中的第二会话已经携带流描述信息, 该流描述信息 中携带端口号, PCRF或 BPCF收到流描述信息后可以从中解析出端口号; 2) 在第二 会话中增强新信元, 携带业务的端口号, 由 AF/TDF发送给 PCRF或 BPCF。 以下实 施例也如此。 本实施例中的第一会话包括以下之一: 触发 S9*会话的消息、 S9*会话、 S9会话 或者固网策略会话; 第二会话是 Rx会话或者 AF会话,或者, Sd会话或者 TDF会话。 其中, S9*也称作 S9a会话, 下同。 本实施例采用 IP地址与端口号组合匹配的方式关联会话,解决了移动终端通过固 网直接访问移动网络业务场景中, 会话关联不准确的问题, 同时, 该方法并未增加新 的信令, 能够与现有协议兼容, 开发成本较低, 易于实现。 这种会话关联方式对于因 为 Rx/Sd上没有用户标识, 也没有 APN信息的情况也适用,可以有效地避免多个终端 的 IP地址相同时的会话错误关联的发生。
PCRF或 BPCF关联第一会话和第二会话之后, 该方法还包括: PCRF或 BPCF根 据第一会话和第二会话的关联关系, 为用户发起的业务制定策略, 下发策略。 上述方法还包括: PCRF或 BPCF以用户标识关联表的方式保存用户的 IP地址和 端口号集合。考虑到为用户分配的 IP地址和端口号可能会发生变更,上述方法还包括: PCRF或 BPCF接收来自固网的更新会话, 其中, 更新会话携带有用户变更后的 IP地 址和端口号集合; PCRF或 BPCF使用用户变更后的 IP地址和端口号集合更新用户的 用户标识关联表中的 IP地址和端口号集合。 通过上述方法可知, 以 PCRF进行会话关联为例, 上述方法可以简单描述如下:
1 ) 固网向 PCRF发起第一会话, 并将 IP地址及端口号集合发送给 PCRF;
2) AF/TDF建立与 PCRF的第二会话, 并将 IP地址及端口号发送给 PCRF;
3 ) PCRF根据 IP地址和端口号关联第一会话和第二会话; 例如: 当第一会话和第 二会话携带的 IP地址相同,并且第二会话携带的端口号是第一会话携带的端口号集合 中的元素时, PCRF关联第一第二会话; 其中, 第一会话是指 S9*会话或者 S9会话; 第二会话是指 Rx会话或者 AF会话, 或者, Sd会话或者 TDF会话;
以 BPCF进行会话关联为例, 上述方法可以简单描述如下:
1 ) BNG/BRAS/AAA向 BPCF发起第一会话建立, 并将 IP地址及端口号集合发送 给 BPCF;
2) AF/TDF建立与 BPCF的第二会话, 并将 IP地址及端口号发送给 BPCF; 3 ) BPCF根据 IP地址和端口号关联第一会话和第二会话; 其中, 第一会话是指 BNG/BRAS/AAA向 BPCF发起的固网策略会话或者是触发 BPCF建立 S9*会话的消息; 针对移动终端通过固网直接访问移动网络业务场景下, PCRF 的关联机制也可以 包括下述过程: 1 ) BNG/BRAS/AAA向 BPCF上报终端的本地 IP地址, 端口号集合与用户标识;
2) BPCF在建立 /修改 S9*会话时向 PCRF上报本地 IP地址, 端口号集合与用户 标识;
3 ) AF/TDF建立 Rx/Sd会话或者通过 Rx/Sd接口下发业务信息时, 向 PCRF下发 业务的 "本地 IP地址和端口号"; 4) PCRF作如下检测, 如果满足以下两条:
AF/TDF发送来的本地地址与 BNG/BRAS/AAA/BPCF上发送来的本地地址相同;
AF/TDF发送来的端口号是 BNG/BRAS/AAA/BPCF上发送来的端口号集合中的元 素;
PCRF将 S9*会话 /固网策略会话和 Rx/Sd会话关联。 其中, 上述第一会话可以是以下之一场景中发起的第一会话:
1 )终端初始接入时, 固网发起第一会话建立过程, 该第一会话携带固网为该终端 初始分配的 IP地址和端口号集合 (对应实例一和实例二);
2) 固网更新终端的 IP地址和 /或端口号集合时, 发起第一会话修改过程, 该第一 会话携带修改后的 IP地址和 /或端口号集合 (对应实例三)。 实例一
该实例中主要描述非漫游场景下终端初始接入时策略会话的关联机制, 如图 6所 示的会话关联示意图, 包括以下步骤: 步骤 601 : 移动终端接入固网, 执行基于 3GPP的 EAP接入认证, 固网的 RG可 以从 3GPP AAA服务器获取 3GPP移动用户标识, 例如 IMSI或者 NAI。 固定网络会 完成分配本地 IP地址, RG、 BNG/BRAS AAA (可选) 建立、 传递 NA(P)T入口表 信息, 最终 RG、 BNG/BRAS AAA (可选) 都用户标识和本地 IP地址、 端口号集合 的关联关系, 简称为用户标识关联表, 该表如图 4所示, 这里不再赘述。 步骤 602: BPCF收到固网 (BNG/BRAS或者 AAA) 触发之后, 获取用户标识关 联表, 其中包括用户标识、 本地 IP地址以及端口号集合。 步骤 603 : BPCF选择到合适的 PCRF, 向 PCRF发起 S9*会话建立操作。 BPCF 需要将包括用户标识、 本地 IP地址以及端口号集合的关联表传递给 PCRF。 步骤 604: UE接入 EPC, 完成 PDN连接建立流程。 本步骤为可选。 步骤 605: 终端和 AF进行应用层协商, 该应用层交互协商的是经过 BNG/BRAS 网元 offload应用业务, 也就是说在应用层协商时, 用户的地址是 602和 603步中所述 的本地 IP地址。 本步骤中的 offload技术,是指数据不再经过 3GPP网络中的 P-GW,不再由 P-GW 负责向外网发送 /从外网接收数据, 而是直接通过固网的网关, 一般是 BNG/BRAS来 向外网发送 /从外网接收数据。 这种技术也称为旁路技术或者网络负荷卸载技术。
AF在应用层协商时获取了业务信息, 或者 TDF经过检测获取了业务信息。 步骤 606: AF/TDF找到合适的 PCRF, 向 PCRF发起 Rx/Sd会话建立操作 /下发业 务信息, 并携带地址 (即本地 IP地址) 和该业务的端口号; 步骤 607: PCRF根据关联机制实施例陈述的机制将会话进行关联。之后业务信息 通过 Rx/Sd会话到达 PCRF, 由 PCRF制定策略, 并经由 S9*会话以及固网策略会话下 发到固网策略执行单元。 需要指出的是: 当终端再次发起业务时, 重复 605-607步骤; 当其他终端接入到 该固网链路, 及接入到该 RG之下后, 重复 601-607的操作。 上述方案是以 S2b接入方案进行的论述,实际上该机制也适用于 S2a/2b/2c接入方 案。
上述实施例步骤中描述的是 AF/TDF找到 3GPP的 PCRF的场景, 实际上有可能 AF/TDF找到的固网的 BPCF, 此时对应的步骤应该是步骤 606a-步骤 607a。 在此场景 下, AF/TDF找到合适的 BPCF, 向 BPCF发起 Rx/Sd会话建立操作 /下发业务信息, 并携带地址 (即本地 IP地址) 和该业务的端口号; BPCF根据关联机制实施例陈述的 机制将会话进行关联。 之后业务信息通过 Rx/Sd会话到达 BPCF, 再由 BPCF下发到 固网策略执行单元。 当会话建立完成并关联成功后, 相关的策略下载到固网的策略执行实体, 一般是 BNG/BRASo此时 BNG/BRAS拿到的是基于用户的策略, 也就是针对每个用户标识都 有对应的确定本地 IP地址 +端口号信息,这样当流经 BNG/BRAS的数据包与该本地 IP 地址 +端口号信息匹配的话,那么 BNG/BRAS就判定该数据包就是与该用户标识 /用户 相关的。 这样 BNG/BRAS就能够基于用户粒度的执行策略和搜集计费信息了。 实例二 本实例中主要描述漫游场景下终端初始接入时策略会话的关联机制,如图 7所示, 包括以下步骤: 步骤 701-702: 同步骤 601-602; 步骤 703 : BPCF选择到合适的 vPCRF, 该 vPCRF是拜访地的 PCRF, 向 vPCRF 发起 S9*会话建立操作。 BPCF需要将包括用户标识、 本地 IP地址以及端口号集合的 关联表传递给 vPCRF。 步骤 704: vPCRF选择到合适的 hPCRF, 该 hPCRF是家乡地的 PCRF, 向 hPCRF 发起 S9会话建立操作。 vPCRF需要将包括用户标识、 本地 IP地址以及端口号集合的 关联表传递给 hPCRF。 步骤 705: UE接入 EPC, 完成 PDN连接建立流程, 本步骤为可选步骤。 步骤 706: 终端和 AF进行应用层协商。 该应用层交互协商的是经过 BNG/BRAS 网元 offload的应用业务, 也就是说在应用层协商时, 用户的地址是 602和 603步中所 述的本地 IP地址。
AF在应用层协商时获取了业务信息, 或者 TDF经过检测获取了业务信息。 步骤 707: AF/TDF找到合适的 hPCRF, 向 hPCRF发起 Rx/Sd会话建立操作, 下 发业务信息, 并携带地址 (即本地 IP地址) 和该业务的端口号;
步骤 708: hPCRF根据关联机制实施例陈述的机制将会话进行关联。 之后业务信 息通过 Rx/Sd会话到达 PCRF, 由 hPCRF制定策略, 并经由 S9会话及 S9*会话以及固 网策略会话下发到固网策略执行单元。 需要指出的是: 当终端再次发起业务时, 重复 706-708步骤; 当其他终端接入到 该固网链路, 及接入到该 RG之下后, 重复 701-708的操作。 上述步骤 707至步骤 708可以具体采用图 7中的步骤 707a和步骤 708a、 以及步 骤 707b和步骤 708b实现。 本实例的方案是以 S2b 接入方案进行的论述, 实际上该机制也适用于 S2a/2b/2c 接入方案。 上述实例步骤中描述的是 AF/TDF找到 3GPP的 hPCRF的场景, 实际上有可能
AF/TDF找到的固网的 vPCRF或者 BPCF,此时对应的步骤应该是步骤 707a-步骤 708a 和步骤 707b-步骤 708b。 在此场景下, AF/TDF 找到合适的 vPCRF/BPCF, 向 vPCRF/BPCF发起 Rx/Sd会话建立操作 /下发业务信息, 并携带地址 (即本地 IP地址) 和该业务的端口号; vPCRF/BPCF根据关联机制实施例陈述的机制将会话进行关联。 之后业务信息通过 S9会话和 Rx/Sd会话到达 vPCRF、 BPCF, 再由 BPCF下发到固网 策略执行单元。 当会话建立完成并关联成功后, 相关的策略下载到固网的策略执行实体, 一般是 BNG/BRAS 此时 BNG/BRAS拿到的是基于用户的策略, 也就是针对每个用户标识都 有对应的确定本地 IP地址 +端口号信息,这样当流经 BNG/BRAS的数据包与该本地 IP 地址 +端口号信息匹配的话,那么 BNG/BRAS就判定该数据包就是与该用户标识 /用户 相关的。 这样 BNG/BRAS就能够基于用户粒度的执行策略和搜集计费信息了。 实例三 本实例描述的是当某个终端用户的端口号集合在 RG/BNG/BRAS 发生变更时, RG/BNG/BRAS 向策略规则实体 (BPCF, v/hPCRF) 更新的操作, 参见图 8, 更新操 作包括以下步骤: 步骤 801 : 终端已经接入固网, 可能已经建立了以下一种或者两种连接: 1.经固网 BNG/BRAS到分组数据网络 /internet的连接,2.经 EPC到分组数据网络 /internet的 PDN 连接。
步骤 802: RG/BNG/BRAS 上的端口号分配发生改变。 导致端口号分配发生改变 的原因有很多, 比如说配置信息改变, 或者是本用户或者其他用户发起业务, 抢占 / 让出端口号等。 步骤 803 : BNG/BRAS或者 AAA向 BPCF更新用户标识关联表, 其中包括用户 标识、 本地 IP地址以及端口号集合。 步骤 804: BPCF向 PCRF通过 S9*会话更新用户标识、 本地 IP地址以及端口号 集合的关联表。 至此, 更新操作完成。 余下步骤 805-807a, 是用户发起业务后, 根据最新的用户 标识关联表进行会话关联和进行策略制定 /下发的操作, 相关机制同流程实例一和二, 相关的补充说明也实例一和是实例二相同, 这里不再赘述。 实施例 2 本实施例提供了一种会话关联装置, 该装置设置可以在策略控制实体 PCRF 或 BPCF上, 参见图 9, 该装置包括以下模块: 第一接收模块 92, 设置为接收来自固网的第一会话, 其中, 该第一会话携带有 IP 地址和端口号集合; 第二接收模块 94, 设置为接收来自 AF/TDF的第二会话, 其中, 该第二会话携带 有 IP地址和端口号信息; 关联模块 96, 与第一接收模块 92和第二接收模块 94相连, 设置为根据上述 IP 地址和端口号信息关联上述第一会话和第二会话。 其中, 本实施例的关联模块 96包括: 判断单元, 设置为判断第一会话携带的 IP 地址与第二会话携带的 IP地址是否相同; 以及判断第二会话携带的端口号信息中的端 口号是否是第一会话携带的端口号集合中的元素; 关联单元, 与判断单元相连, 设置 为当判断单元的判断结果均为是时, 关联第一会话和第二会话。 如果上述两个会话中的 IP地址不同, 则不关联两会话, 如果仅 IP地址相同, 第 二会话携带的端口号信息中的端口号并不是第一会话携带的端口号集合中的元素, 则 也不关联两会话。 本实施例中的第一会话包括以下之一: 触发 S9*会话的消息、 S9*会话、 S9会话 或者固网策略会话; 第二会话是 Rx/Sd会话或者 AF/TDF会话。
本实施例采用 IP地址与端口号组合匹配的方式关联会话,解决了移动终端通过固 网直接访问移动网络业务场景中, 会话关联不准确的问题, 同时, 该方法并未增加新 的信令, 能够与现有协议兼容, 开发成本较低, 易于实现。 这种会话关联方式对于因 为 Rx/Sd上没有用户标识, 也没有 APN信息的情况也适用,可以有效地避免多个终端 的 IP地址相同时的会话错误关联的发生。 该装置包括: 测量制定与下方模块, 设置为根据第一会话和第二会话的关联关系, 为用户发起的业务制定策略, 下发策略。 上述装置还包括: 保存模块, 设置为以用户标识关联表的方式保存用户的 IP地址 和端口号集合。考虑到为用户分配的 IP地址和端口号可能会发生变更, 上述装置还包 括: 更新模块, 设置为接收来自固网网元的更新会话, 其中, 更新会话携带有用户变 更后的 IP地址和端口号集合; 并使用用户变更后的 IP地址和端口号集合更新用户的 用户标识关联表中的 IP地址和端口号集合。 其中, 上述第一会话可以是以下之一场景中发起的第一会话:
1 )终端初始接入时, 固网发起第一会话建立过程, 该第一会话携带固网为该终端 初始分配的 IP地址和端口号集合;
2) 固网更新终端的 IP地址和 /或端口号集合时, 发起第一会话修改过程, 该第一 会话携带修改后的 IP地址和 /或端口号集合。 本实施例还提供了一种会话关联***,该***包括 PCRF或 BPCF,PCRF或 BPCF 上设置有上述会话关联装置, 该***还包括: 固网网元, 设置为向装置发送第一会话; 应用功能实体 AF/TDF, 设置为向装置发送第二会话。 其中, 固网网元包括以下之一: RG、 BNG、 BRAS, 或者 AAA服务器。 本实施例根据会话中携带的 IP地址与端口号(集合)确定会话间是否关联, 即是 否为同一用户发起的会话, 提高了会话关联的准确度, 解决了移动终端通过固网直接 访问移动网络业务场景中, 会话关联不准确的问题, 同时, 该方法并未增加新的信令, 能够与现有协议兼容, 开发成本较低, 易于实现。 这种会话关联方式对于因为 Rx/Sd 上没有用户标识, 也没有 APN信息的情况也适用, 可以有效地避免多个终端的 IP地 址相同时的会话错误关联的发生。
从以上的描述中可以看出, 以上实施例在 IP地址与端口号的组合方式下确定会话 是否关联, 有效地避免多个终端的 IP地址相同时的会话错误关联的发生, 并且未增加 新的信令, 实现简单。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1. 一种会话关联方法, 包括:
策略控制实体 PCRF或宽带论坛策略控制实体 BPCF接收来自固网的第一 会话; 其中, 所述第一会话携带有 IP地址和端口号集合;
所述 PCRF或所述 BPCF接收来自应用功能实体 AF或者业务检测功能 TDF 的第二会话; 其中, 所述第二会话携带有 IP地址和端口号信息;
所述 PCRF或所述 BPCF根据所述 IP地址和端口号信息关联所述第一会话 和所述第二会话。
2. 根据权利要求 1所述的方法, 其中,
所述第一会话包括以下之一: 触发 S9*会话的消息、 S9*会话、 S9会话或 者固网策略会话;
所述第二会话是 Rx会话, 或者 AF会话, 或者 Sd会话, 或者 TDF会话。
3. 根据权利要求 1所述的方法, 其中, 所述 PCRF或所述 BPCF根据所述 IP地址 和端口号信息关联所述第一会话和所述第二会话包括:
PCRF或 BPCF判断第一会话和第二会话符合以下两个条件时, 关联所述 第一会话和所述第二会话:
1 ) 所述第一会话的 IP地址与所述第二会话的 IP地址相同;
2)所述第二会话的端口号信息中的端口号是所述第一会话的端口号集合中 的元素。
4. 根据权利要求 1所述的方法, 其中, 所述 PCRF或所述 BPCF关联所述第一会 话和所述第二会话之后, 所述方法还包括:
所述 PCRF或 BPCF根据所述第一会话和所述第二会话的关联关系, 为业 务制定策略, 下发所述策略。
5. 根据权利要求 1所述的方法,其中,所述方法还包括: 所述 PCRF或所述 BPCF 以用户标识关联表的方式保存所述 IP地址和端口号集合。
6. 根据权利要求 1所述的方法, 其中, 所述 PCRF或 BPCF接收来自固网的第一 会话包括以下方式之一:
终端初始接入时, 所述固网发起第一会话建立过程, 所述第一会话携带有 所述固网为所述终端初始分配的 IP地址和端口号集合;
所述固网更新终端的 IP地址和 /或端口号集合时, 发起第一会话修改过程, 所述第一会话携带有修改后的 IP地址和 /或端口号集合。 一种会话关联装置, 所述装置设置在策略控制实体 PCRF或宽带论坛策略控制 实体 BPCF上, 包括: 第一接收模块, 设置为接收来自固网的第一会话; 其中, 所述第一会话携 带有 IP地址和端口号集合;
第二接收模块,设置为接收来自应用功能实体 AF,或者业务检测功能 TDF 的第二会话; 其中, 所述第二会话携带有 IP地址和端口号信息;
关联模块,设置为根据所述 IP地址和端口号信息关联所述第一会话和所述 第二会话。 根据权利要求 7所述的装置, 其中, 所述关联模块包括:
判断单元,设置为判断所述第一会话携带的 IP地址与所述第二会话携带的 IP地址是否相同, 以及判断所述第二会话携带的端口号信息中的端口号是否是 第一会话携带的端口号集合中的元素;
关联单元, 设置为当所述判断单元的判断结果均为是时, 关联所述第一会 话和所述第二会话。 一种会话关联***, 包括策略控制实体 PCRF或 BPCF, 所述 PCRF或 BPCF 上设置有权利要求 7或 8所述的装置, 所述***还包括:
固网网元, 设置为向所述装置发送所述第一会话;
应用功能实体 AF, 或者业务检测功能 TDF, 设置为向所述装置发送所述 第二会话。 根据权利要求 9所述的***, 其中, 所述固网网元包括以下之一:
家庭网关 RG、 宽带网关 BNG、 宽带远端接入服务器 BRAS, 或者验证、 授权与计费 AAA服务器。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP12817624.5A EP2738982B1 (en) | 2011-07-26 | 2012-06-18 | Session association method, device and system |
US14/234,740 US9456006B2 (en) | 2011-07-26 | 2012-06-18 | Method, device and system for session binding |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110210986 | 2011-07-26 | ||
CN201110210986.1 | 2011-07-26 | ||
CN201110308927.8A CN102905390B (zh) | 2011-07-26 | 2011-09-30 | 会话关联方法、装置和*** |
CN201110308927.8 | 2011-09-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013013541A1 true WO2013013541A1 (zh) | 2013-01-31 |
Family
ID=47577368
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/077080 WO2013013541A1 (zh) | 2011-07-26 | 2012-06-18 | 会话关联方法、装置和*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US9456006B2 (zh) |
EP (1) | EP2738982B1 (zh) |
CN (1) | CN102905390B (zh) |
WO (1) | WO2013013541A1 (zh) |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103269334B (zh) * | 2013-04-24 | 2017-06-20 | 华为技术有限公司 | 会话关联方法、装置及*** |
US9131071B2 (en) * | 2013-05-14 | 2015-09-08 | Alcatel Lucent | Binding of SD messages with radius messages |
JP6055105B2 (ja) * | 2013-09-11 | 2016-12-27 | フリービット株式会社 | アプリケーション状態変化通知プログラム及びその方法 |
WO2015051536A1 (zh) * | 2013-10-11 | 2015-04-16 | 华为技术有限公司 | 信息传输方法和装置 |
EP3073691B1 (en) * | 2013-12-12 | 2020-09-16 | Huawei Technologies Co., Ltd. | Method and device for improving qos |
CN103780613B (zh) * | 2014-01-21 | 2015-09-30 | 北京集奥聚合科技有限公司 | 将固定网络和移动网络用户关联的方法和*** |
CN104917742B (zh) * | 2014-03-11 | 2018-05-29 | 华为技术有限公司 | 一种信息传送方法及装置 |
EP3107352B1 (en) | 2014-03-11 | 2018-12-05 | Huawei Technologies Co., Ltd. | Information transfer method, system and apparatus |
CN105101176B (zh) * | 2014-05-05 | 2019-06-11 | 华为技术有限公司 | 一种漫游场景下的会话绑定方法、装置和*** |
CN105451289B (zh) * | 2014-08-30 | 2019-05-28 | 华为技术有限公司 | 一种业务处理方法及***、设备 |
CN105991619B (zh) * | 2015-03-05 | 2021-01-15 | 中兴通讯股份有限公司 | 一种安全认证方法和装置 |
CN106162686B (zh) * | 2015-03-31 | 2019-06-07 | 国家计算机网络与信息安全管理中心 | 一种基于wlan的信令获取与关联的方法及*** |
RU2679345C1 (ru) * | 2015-04-07 | 2019-02-07 | Хуавэй Текнолоджиз Ко., Лтд. | Способ и устройство для автоматического сетевого взаимодействия устройства шлюза |
US10148766B2 (en) | 2015-11-12 | 2018-12-04 | Oracle International Corporation | Methods, systems, and computer readable media for subscriber binding repository reconfiguration |
WO2018223304A1 (zh) * | 2017-06-07 | 2018-12-13 | 华为技术有限公司 | 一种数据传输的方法和装置 |
CN110650475B (zh) * | 2018-06-26 | 2022-06-03 | ***通信有限公司研究院 | 一种会话绑定处理方法及网络设备 |
CN112751902B (zh) * | 2019-10-31 | 2023-05-09 | ***通信有限公司研究院 | 网际协议地址重分配的方法及装置、终端、存储介质 |
CN111064650B (zh) * | 2019-12-23 | 2022-10-04 | 浙江宇视科技有限公司 | 一种动态变更隧道连接服务端口号的方法及装置 |
CN112152873B (zh) * | 2020-09-02 | 2022-10-21 | 杭州安恒信息技术股份有限公司 | 用户识别方法、装置、计算机设备和存储介质 |
US11283883B1 (en) * | 2020-11-09 | 2022-03-22 | Oracle International Corporation | Methods, systems, and computer readable media for providing optimized binding support function (BSF) packet data unit (PDU) session binding discovery responses |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1874328A (zh) * | 2006-03-03 | 2006-12-06 | 华为技术有限公司 | 实现业务互通的方法及*** |
CN1993947A (zh) * | 2004-07-30 | 2007-07-04 | 艾利森电话股份有限公司 | 在混合电信网络中提供相关手段的方法及装置 |
US20090207757A1 (en) * | 2008-02-15 | 2009-08-20 | Andreasen Flemming S | System and method for providing location and access network information support in a network environment |
CN101720108A (zh) * | 2009-04-28 | 2010-06-02 | 中兴通讯股份有限公司 | 业务层融合网络的策略控制方法与*** |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101047949B (zh) * | 2006-03-27 | 2010-05-12 | 华为技术有限公司 | 业务数据流的承载控制方法 |
CN101110766B (zh) * | 2007-03-23 | 2010-04-21 | 华为技术有限公司 | 一种信令ip流承载事件上报的控制方法和功能实体 |
EP2220841B1 (en) * | 2007-11-01 | 2011-09-28 | Telefonaktiebolaget LM Ericsson (publ) | Method and system for correlating aaa sessions |
CN101610240B (zh) * | 2008-06-16 | 2013-03-20 | 华为技术有限公司 | 业务信息与ip-can会话信息关联的方法和网络设备 |
CN101583112B (zh) * | 2008-08-12 | 2011-09-21 | 中兴通讯股份有限公司 | 会话信息的标识方法及装置 |
CN101771986A (zh) * | 2009-01-06 | 2010-07-07 | 中兴通讯股份有限公司 | 基于多接入技术的策略计费控制方法、装置和*** |
KR101332968B1 (ko) * | 2009-03-02 | 2013-11-25 | 엔이씨 유럽 리미티드 | 네트워크를 동작하는 방법 및 네트워크 |
US9264454B2 (en) * | 2009-05-28 | 2016-02-16 | Telefonaktiebolaget L M Ericsson (Publ) | Method and arrangement for implementing policy rules in peer-to-peer communication |
US9503483B2 (en) * | 2010-02-16 | 2016-11-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatuses for identifying and reporting quality of service rules applicable to a communication session |
US9537821B2 (en) * | 2011-02-01 | 2017-01-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for PCC support for scenarios with NAT in the GW |
-
2011
- 2011-09-30 CN CN201110308927.8A patent/CN102905390B/zh not_active Expired - Fee Related
-
2012
- 2012-06-18 WO PCT/CN2012/077080 patent/WO2013013541A1/zh active Application Filing
- 2012-06-18 EP EP12817624.5A patent/EP2738982B1/en not_active Not-in-force
- 2012-06-18 US US14/234,740 patent/US9456006B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1993947A (zh) * | 2004-07-30 | 2007-07-04 | 艾利森电话股份有限公司 | 在混合电信网络中提供相关手段的方法及装置 |
CN1874328A (zh) * | 2006-03-03 | 2006-12-06 | 华为技术有限公司 | 实现业务互通的方法及*** |
US20090207757A1 (en) * | 2008-02-15 | 2009-08-20 | Andreasen Flemming S | System and method for providing location and access network information support in a network environment |
CN101720108A (zh) * | 2009-04-28 | 2010-06-02 | 中兴通讯股份有限公司 | 业务层融合网络的策略控制方法与*** |
Also Published As
Publication number | Publication date |
---|---|
US20140164633A1 (en) | 2014-06-12 |
EP2738982B1 (en) | 2019-04-10 |
EP2738982A1 (en) | 2014-06-04 |
US9456006B2 (en) | 2016-09-27 |
EP2738982A4 (en) | 2015-03-04 |
CN102905390A (zh) | 2013-01-30 |
CN102905390B (zh) | 2017-12-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2013013541A1 (zh) | 会话关联方法、装置和*** | |
US9717019B2 (en) | Data flow control method, and related device and communications system | |
US8849273B2 (en) | Method and system for reporting fixed network access information | |
US9113436B2 (en) | Method and system for information transmission | |
EP2547049B1 (en) | Method, system and corresponding apparatus for implementing policy and charging control | |
US9544832B2 (en) | Method, apparatus and system for policy control | |
CN102958046B (zh) | 一种移动终端访问业务的控制方法、***及dra | |
WO2009094837A1 (en) | A method for selecting a policy and charging rules function server on a non-roaming scene | |
WO2013064070A1 (zh) | 一种实现反射QoS机制的方法、***和PCRF | |
WO2011137644A1 (zh) | 终端访问业务的方法、装置及*** | |
WO2011085614A1 (zh) | 在全业务融合网络中控制资源的方法和*** | |
WO2008154874A1 (fr) | Procédé et système permettant d'établir un tunnel dans le réseau en évolution | |
WO2014101755A1 (zh) | 业务数据分流方法及*** | |
EP2702785A1 (en) | Local access point name for use in accessing packet data networks | |
US20140177530A1 (en) | Access method and system and mobile intelligent access point | |
WO2011088702A1 (zh) | 在全业务融合网络中控制资源的方法和*** | |
CN104113930B (zh) | 一种实现用户终结连接的方法及*** | |
WO2012010036A1 (zh) | 一种策略控制方法及*** | |
WO2013060214A1 (zh) | 应用信息上报方法及装置 | |
EP2496049B1 (en) | Method, home agent and user equipment for processing multiple access | |
WO2013023515A1 (zh) | 一种解决服务质量策略控制冲突的方法和*** | |
WO2012171425A1 (zh) | 业务处理方法及装置 | |
WO2013020451A1 (zh) | 一种建立会话的方法及*** | |
WO2012041128A1 (zh) | 一种通信网络***、寻找家庭基站策略网元的方法及装置 | |
WO2012079443A1 (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: 12817624 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14234740 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012817624 Country of ref document: EP |