WO2012019506A1 - Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile - Google Patents

Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile Download PDF

Info

Publication number
WO2012019506A1
WO2012019506A1 PCT/CN2011/077487 CN2011077487W WO2012019506A1 WO 2012019506 A1 WO2012019506 A1 WO 2012019506A1 CN 2011077487 W CN2011077487 W CN 2011077487W WO 2012019506 A1 WO2012019506 A1 WO 2012019506A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
fixed network
interface
bng
bras
Prior art date
Application number
PCT/CN2011/077487
Other languages
English (en)
Chinese (zh)
Inventor
蒋陶
毕以峰
霍玉臻
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012019506A1 publication Critical patent/WO2012019506A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1471—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network splitting of costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for implementing resource control in a fixed network mobile network convergence scenario. Background technique
  • the 3GPP AAA server (3GPP authentication and authorization accounting server), the Policy and Charging Rules Function (PCRF) entity and other supporting nodes. See the upper box section in Figures 1 and 2.
  • the MME is responsible for control plane related operations such as mobility management, non-access stratum signaling processing, and user mobility management context management;
  • the S-GW is an access gateway device connected to the E-UTRAN, in the E-UTRAN and P - The GW forwards data and is responsible for caching the paging wait data.
  • the P-GW is a border gateway of the 3GPP evolved packet system (EPS, Evolved Packet System) and PDN (Packet Data Network) network, and is responsible for PDN access and forwarding data between EPS and PDN.
  • EPS 3GPP evolved packet system
  • PDN Packet Data Network
  • the lower part of the dotted line shown in Figures 1 and 2 is the fixed network access part of the fixed network mobile network convergence architecture.
  • the fixed network part mainly includes the network element RG (Routing Gateway) and AN (Access). Network, Access Network), BNG (Broadband Network Gateway), BRAS (Broadband Remote Access Server), and BBF AAA (Broadband Forum AAA), Broadband Forum Policy Control Function (Broadband Forum Policy Control Function, BPCF).
  • the AN includes network elements such as a DSLAM (Digital Subscriber Line Access Multiplexer) and an ONT (Optical Network Terminal).
  • the EPS can be interoperable with non-3GPP networks. That is, the UE can also access the EPS through the non-3GPP access network.
  • the P-GW acts as an anchor between the 3GPP access network and the non-3GPP access network.
  • Non-3GPP systems can be further divided into trusted non-3GPP IP access and untrusted non-3GPP IP access.
  • the fixed network can be directly trusted as a non-3GPP access (as shown in FIG. 2) or through an interworking gateway (the interworking gateway in the present invention is called X-MAG.
  • the interworking gateway can define different names, Does not affect the essence of the invention) Indirect (as shown in Figure 1) access to the P-GW of the EPS system through the S2a interface, the S2a interface uses the PMIPv6 protocol.
  • the fixed network broadband network gateway/broadband remote access server (BNG/BRAS) needs to be connected to the P-GW through the S2a interface; when the user accesses, the user data passes the BNG/BRAS to the X. -MAG, then to the P-GW of the EPS core network, and finally to the external PDN (for example: Internet or carrier enterprise network, etc.);
  • BNG/BRAS fixed network broadband network gateway/broadband remote access server
  • the interworking gateway X-MAG and the P-GW are connected through the S2a interface.
  • the user data passes through the fixed network and the X-MAG network element, and reaches the external PDN (for example, the Internet or the carrier enterprise network, etc.) via the P-GW of the EPS core network.
  • the external PDN for example, the Internet or the carrier enterprise network, etc.
  • X-MAG, BNG/BRAS, BBF AAA, and 3GPP HSS/AAA implement authentication and authorization for user access.
  • BNG/BRAS, BPCF, 3GPP PCRF manage and control fixed network resources.
  • each interface In the fixed network, in order to describe each interface conveniently, two endpoint network elements of each interface can be used as the name of each interface.
  • the interface between BNG/BRAS and BBF AAA is called: (BNG/BRAS-BBF AAA) interface
  • the interface between BNG/BRAS and BPCF is called:
  • the Policy and Charging Enforcement Function exists in the P-GW.
  • the PCRF and the P-GW exchange information through the Gx interface.
  • the S-GW resides in the bearer binding and event reporting function (BBERF, Bearer Binding and Event Reporting Function), and the S-GW and the PCRF pass.
  • BBERF Bearer Binding and Event Reporting Function
  • the Gxc interface exchanges information.
  • the fixed network policy and charging control is formulated by BPCF and implemented by BNG/BRAS.
  • EPS network and fixed network convergence require unified management of policies and billing.
  • a PCRF-BPCF interface (also referred to as an S9* interface)
  • the policy formulation and the control point are unified in the PCRF
  • the BPCF obtains the policy from the PCRF through the PCRF-BPCF interface/S9* interface.
  • BNG/BRAS and BPCF also report local events (for example, resource usage status, etc.) to the PCRF.
  • the S9* interface is a new interface for the fixed network mobile network convergence technology.
  • the interface is introduced because: Without this interface, BPCF cannot obtain the PCC policy from the PCRF; in other words, the PCRF cannot control the fixed network resources. .
  • the PCRF cannot control the fixed network resources.
  • it is bound to affect the PCRF's own processing mechanism and external interaction characteristics, which requires PCRF enhancement. In other words, the convergence of fixed-line mobile networks has affected the EPS system and requires system enhancement. Summary of the invention
  • the main object of the present invention is to provide a method and system for realizing resource control in a fixed network mobile network convergence scenario, so as to reduce the impact on the EPS system and improve the current state of resource control and management.
  • a method for realizing resource control in a fixed network mobile network convergence scenario comprising: establishing a general packet radio service tunnel association between a packet data network gateway P-GW and a fixed network The GTP interface; the policy and charging rule function PCRF exchanges policy information with the fixed network via the P-GW and the GTP interface.
  • the policy information includes related quality of service information and/or event information related to communication;
  • the fixed network is provided with a broadband network gateway/broadband remote access server BNG/BRAS connected to the mobile network; the BNG/BRAS and The broadband forum policy control function in the fixed network is connected to the BPCF entity through the fixed network policy interface;
  • the fixed network is provided with an interworking gateway connected to the mobile network; the mobile network is connected to the interworking gateway through the GTP interface, and the interworking gateway is connected to the BPCF through the interworking policy interface.
  • the process of the interaction policy information includes:
  • the PCRF sends the related policy to the fixed network.
  • the path of the related policy is: The PCRF is transmitted to the P-GW through the IP-CAN session of the Gx interface, and the P-GW is transmitted to the BNG/BRAS through the GTP protocol, and the BNG/BRAS is passed.
  • the fixed network policy interface is mutually negotiated with the BPCF and executed by the BPCF or the BNG/BRAS;
  • the process of the interaction policy information includes:
  • the PCRF sends the related policy to the fixed network, and the transmission path of the related policy is: the PCRF is transmitted to the P-GW through the IP-CAN session of the Gx interface, and the P-GW is transmitted to the interworking gateway through the GTP protocol, where the interworking is performed.
  • the gateway transmits to the BPCF through the interworking policy interface, and the BPCF exchanges with the BNG/BRAS through the fixed network policy interface and is executed by the BPCF or the BNG/BRAS.
  • the process of the interaction policy information further includes:
  • the fixed network sends the related policy to the PCRF, and the transmission path of the related policy is: BNG/BRAS exchanges the negotiation policy with the BPCF through the fixed network policy interface, and the BNG/BRAS transmits the PNG to the P-GW through the GTP protocol, P- GW transmits to the PCRF through the IP-CAN session of the Gx interface Deliver
  • the process of the interaction policy information includes:
  • the fixed network sends the related policy to the PCRF, and the relevant path of the related policy is:
  • the BNG/BRAS communicates with the BPCF through the fixed network policy interface, and the BPCF passes the interworking policy interface to the interworking gateway, and the interworking gateway transmits the P-GW to the P-GW through the GTP interface, and the P-GW passes the Gx interface.
  • the IP-CAN session is passed to the PCRF.
  • the process of establishing a session and a delivery policy by the fixed network policy interface and the GTP interface, when the BNG/BRAS connected to the mobile network is set in the fixed network includes:
  • the process of establishing a session and a delivery policy of the fixed network policy interface, the interworking policy interface, and the GTP interface includes:
  • a system for implementing resource control in a fixed network mobile network convergence scenario including a P-GW and a PCRF located in a mobile network, and a fixed network; a GTP interface is established between the P-GW and the fixed network;
  • the PCRF is configured to interact with a fixed network via a P-GW and the GTP interface, where the policy information includes related quality of service information and/or event information related to communication; BNG/BRAS for mobile network connection; the BNG/BRAS and solid The BPCF in the network is connected;
  • the fixed network is provided with an interworking gateway connected to the mobile network;
  • the GTP interface is connected to the interworking gateway, and the interworking gateway is connected to the BPCF through the interworking policy interface.
  • the related policy is delivered to the fixed network, and the transmission path of the related policy is: the PCRF transmits to the P-GW through the IP-CAN session of the Gx interface, the P-GW transmits to the BNG/BRAS through the GTP protocol, and the BNG/BRAS passes through the solid
  • the network policy interface is negotiated with BPCF and is negotiated by BPCF or
  • the PCRF interacts with the policy information for:
  • the related policy is delivered to the fixed network, and the path of the related policy is: the PCRF is transmitted to the P-GW through the IP-CAN session of the Gx interface, and the P-GW is transmitted to the interworking gateway through the GTP protocol, and the interworking gateway passes the interworking policy interface. Passed to the BPCF, the BPCF executes or transmits the received content to the BNG/BRAS for execution.
  • the PCRF when the BNG/BRAS connected to the mobile network is set in the fixed network, when the PCRF interacts with the policy information, it is further used to:
  • the transmission path of the related policy is: BNG/BRAS exchanges the negotiation policy with the BPCF through the fixed network policy interface, the BNG/BRAS transmits to the P-GW through the GTP protocol, and the P-GW passes the Gx interface
  • the IP-CAN session is passed to the PCRF;
  • the PCRF When the fixed network is connected to the mobile network through the interworking gateway, when the PCRF interacts with the policy information, it is further used to:
  • the delivery path of the related policy is: BNG/BRAS exchanges a negotiation policy with the BPCF through the fixed network policy interface, and the BPCF transmits the policy to the interworking gateway through the interworking policy interface, The interworking gateway transmits to the P-GW through the GTP protocol, P-GW Passed to the PCRF via the IP-CAN session of the Gx interface.
  • the fixed network policy interface and the GTP interface are used when establishing a session and a delivery policy:
  • the interworking gateway When the interworking gateway is connected to the mobile network, the fixed network policy interface, the interworking policy interface, and the GTP interface are used to establish a session and a delivery policy when:
  • the method and system of the present invention can avoid the use of the current S9* interface, and can significantly reduce the impact on the self-processing mechanism and the external interaction feature of the policy and the charging rule function, and the policy and charging rule function enhancement is no longer needed.
  • the impact on the evolved packet system is significantly reduced.
  • the aforementioned new interface relationship and communication information interaction mode can effectively realize resource control and management, and achieve the purpose of improving resource control and management status.
  • FIG. 1 is a schematic diagram of a fixed network mobile network convergence architecture of the prior art
  • FIG. 2 is a schematic diagram of another fixed network mobile network convergence architecture in the prior art
  • FIG. 3 is a schematic diagram of a fixed network mobile network convergence architecture according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a fixed network mobile network convergence architecture according to another embodiment of the present invention.
  • FIG. 5 is an attached flow chart implemented by the architecture shown in Figure 3;
  • FIG. 6 is a flow chart of establishing a network initiated bearer implemented by the architecture shown in FIG. 3;
  • FIG. 7 is a flowchart of a bearer deletion initiated by a fixed network implemented by the architecture shown in FIG. 3; 8 is a flow chart of terminal-initiated detach/PDN connection release implemented by the architecture shown in FIG. 3;
  • FIG. 9 is a flowchart of modifying a bearer resource initiated by a terminal implemented by the architecture shown in FIG. 3;
  • FIG. 10 is a flowchart of attaching implemented by the architecture shown in FIG.
  • FIG. 11 is a flow chart of establishing a network initiated bearer implemented by the architecture shown in FIG. 4;
  • FIG. 12 is a flowchart of a bearer deletion initiated by a fixed network implemented by the architecture shown in FIG. 4;
  • FIG. 13 is a flowchart of a terminal-initiated detach/PDN connection release process implemented by the architecture shown in FIG. 4;
  • FIG. 14 is a flow chart of modifying a bearer resource initiated by a terminal implemented by the architecture shown in FIG. 4;
  • FIG. 15 is a schematic flowchart of implementing resource control in a fixed network mobile network convergence scenario according to the present invention. detailed description
  • the GTP interface needs to be adopted between the P-GW and the fixed network, and the PMIPv6-based interface previously adopted is no longer applied. Moreover, due to the interface change between the P-GW and the fixed network, the direct interface between the PCRF and the BPCF is no longer needed; finally, the PCRF can interact with the fixed network via the P-GW and the GTP interface, including communication. Relevant policy information.
  • the GTP protocol is used to establish a binding relationship between the interworking gateway X-MAG and the P-GW to transmit related policies and information; and in the interworking gateways X-MAG and BPCF. Through the interoperability policy interface to pass relevant policies and information.
  • the PCRF can send relevant policies and information to the fixed network system, and the path is: PCRF->P-GW->X-MAG->fixed network.
  • the PCRF is transmitted to the P-GW through the IP-CAN session of the Gx interface, and the P-GW is transmitted to the X-MAG through the GTP protocol, and the X-MAG is transmitted to the fixed network through the interworking policy interface.
  • the functional entity that the fixed network receives the relevant policies and information may be BPCF, BPCF and BNG/BRAS negotiate policy information and are executed by BPCF and/or BNG/BRAS.
  • the fixed network can report relevant policies and information to the PCRF; the path is: fixed network->XM AG->P-GW->PCRF 0 , where the corresponding functional entities in the fixed network collect relevant policies and information and pass each other
  • the policy interface is passed to the X-MAG; the X-MAG is delivered to the P-GW through the GTP protocol, and the P-GW is delivered to the PCRF through the IP-CAN session of the Gx interface.
  • the functional entities that the fixed network collects related policies and information may be BNG/BRAS and/or BPCF.
  • the GTP protocol can be used to establish a binding relationship between the BNG/BRAS and the P-GW to transmit related policies and information; and a fixed network policy interface is established between the BNG/BRAS and the BPCF. To pass relevant strategies and information.
  • the PCRF can issue relevant policies and information to the fixed network system.
  • the path is: PCRF -> P-GW -> BNG/BRAS ⁇ -> BPCF.
  • the PCRF is transmitted to the P-GW through the IP-CAN session of the Gx interface, and the P-GW is transmitted to the BNG/BRAS through the GTP protocol.
  • the BNG/BRAS exchanges with the BPCF through the fixed network policy interface and is executed by the BNG/BRAS.
  • the fixed network can report relevant policies and information to the PCRF; the path is: BPCF ⁇ -> BNG/BRAS -> P-GW -> PCRF.
  • the BNG/BRAS exchanges the policy with the BPCF through the fixed network policy interface
  • the BNG/BRAS transmits to the P-GW through the GTP protocol
  • the P-GW transmits the IP-CAN session to the PCRF through the Gx interface.
  • the P-GW can use the GTP protocol to establish a binding relationship between the BNG/BRAS and the P-GW to transmit related policies.
  • the BPCF can establish a fixed network policy interface between the BNG/BRAS and the BPCF to transmit related policies.
  • the BNG/BRAS indirectly connected to the mobile network through the X-MAG is set in the fixed network, and when the GTP interface is established, it is used to:
  • the P-GW can use the GTP protocol to establish a binding relationship between the X-MAG and the P-GW to transmit related policies.
  • the BPCF can establish an interworking policy interface between the X-MAG and the BPCF to transmit related policies.
  • FIG. 5 is an attached flow chart implemented by the architecture shown in FIG. 3, which describes a flow chart for establishing an attach/additional PDN connection for a terminal to access an EPS through a fixed network, and a trusted non-3GPP access for a fixed network as an EPS network.
  • the flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • a fixed network policy session is established between the BNG/BRAS and the BPCF, and an interworking policy session is established between the X-MAG and the BPCF.
  • the unified PCC policy is downloaded from the PCRF and The PCRF reports the fixed network event.
  • Step 501 The UE passes the authentication according to the fixed network authentication mode.
  • Step 502 The UE establishes a local connection with the fixed network, and obtains a local IP address allocated by the fixed network.
  • Step 503 Upon being triggered by the local connection establishment step and/or the authentication step, the BNG/BRAS initiates a fixed network policy session establishment request to the BPCF. Through this step, the BNG/BRAS establishes a session for applying/delivering a dynamic policy with the BPCF to achieve accurate control of network resource allocation and user admission.
  • Step 504 The UE sends a Layer 3 Negotiation Request message to the X-MAG to request access.
  • the UE carries a mobile network ID, an APN, and the like.
  • Step 505 The user accesses the mobile network authentication.
  • the 3GPP-based authentication method (such as EAP-AKA) is used to complete the access authentication for the user.
  • Step 506 The X-MAG initiates an interworking policy session establishment request to the BPCF, and establishes an interworking policy session between the X-MAG and the BPCF.
  • Step 507 After the X-MAG is triggered by the Layer 3 negotiation request sent by the UE, the XTP is sent to the P-GW to request the tunnel binding with the P-GW.
  • Step 508 After receiving the Create Session Request message, the P-GW allocates an IP address to the UE. The P-GW establishes an IP-CAN session with the PCRF.
  • Step 509 The P-GW sends an APN/P-GW identity pair to the 3GPP HSS/AAA, requesting The HSS/AAA stores the identity of the P-GW to implement P-GW identity update.
  • Step 510 The P-GW responds to the X-MAG network element to create a session response message, and carries the IP address assigned to the UE in the message.
  • Step 511 The X-MAG network element completes the Layer 3 negotiation with the UE, and sends the IP address of the UE to the UE, or sends the message to the UE through other messages.
  • step 506 the UE carries different APNs to the EPS core network, and an additional PDN connection can be established, and the additional PDN connection is not limited to one.
  • Step 506 can be operated in two ways:
  • the X-MAG is triggered by the step 504 to initiate an interworking policy session establishment request to the BPCF to establish a second interworking policy session with the BPCF. It should be noted that, when the UE is attached, the interworking policy session establishing the default PDN connection is the first interworking policy session, and if there are additional PDN connections established, the third and fourth number of interworking policy sessions are also established.
  • the X-MAG receives the message of step 504, and detects that an interworking policy session has been established when the UE is attached, and the X-MAG sends an interworking policy session update operation to the BPCF to reuse the session.
  • the fixed network policy session and the interworking policy session are one-to-many relationships; if the (II) scheme is adopted, the fixed network policy session and the interworking policy session are in a one-to-one relationship.
  • BPCF's fixed network policy session and interworking policy session are initiated by two different network elements (BNG/BRAS and X-MAG, respectively), so BPCF Two sessions belonging to the same UE or the same PDN connection need to be associated.
  • the association method can take any of the following scenarios:
  • step 503 When the local connection is established in step 502 and the fixed network policy session is established in step 503, the UE sends its own mobile network information to the BPCF; when the interworking policy session is established in step 506, the X-MAG sends the mobile network information of the UE to BPCF.
  • BPCF associates two types of sessions based on mobile network information;
  • the mobile network information may include: a fixed network ID of the UE (eg, IMSI/NAI), APN or other information.
  • step 506 In the Layer 3 Negotiation Request message of step 504 and the interworking policy session establishing operation of step 506, the UE sends its own fixed network information to the BPCF, and when the fixed network policy session is established in step 503, the BNG/BRAS will UE The fixed network information was sent to BPCF.
  • BPCF associates two types of sessions based on fixed network information.
  • the fixed network information may include: a fixed network ID of the UE (eg, a username), a fixed network IP address, or other information.
  • FIG. 6 is a flowchart of a network-initiated bearer setup implemented by the architecture shown in FIG. 3, which describes a flow chart of a network-side initiated bearer setup/modification, and a fixed network as a trusted non-3GPP access of an EPS network, where The flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • the UE accesses the EPS through the attach procedure, and the fixed-network policy session between the BNG/BRAS and the BPCF, and the interworking policy session between the X-MAG and the BPCF have been established and correctly associated.
  • Figure 6 illustrates: The PCRF sends the relevant PCC policy to the P-GW, and the P-GW sends the control signaling to the X-MAG through the GTP protocol.
  • the X-MAG then sends the policy to the fixed network BPCF through the interworking policy session. .
  • the BPCF After the BPCF receives the policy, it integrates the fixed network's own policy and notifies the BNG/BRAS to execute it. The execution result is finally fed back to the PCRF.
  • Step 601 The PCRF initiates an IP-CAN session modification operation, and sends the related PCC policy to the P-GW through the operation.
  • Step 602 The P-GW sends a bearer creation/update request message of the GTP protocol to the X-MAG, and carries the related PCC policy.
  • Step 603 The X-MAG negotiates resource configuration with the UE.
  • This step is an optional step, that is, if a corresponding TFT is sent to the UE on the network side, it is sent to the UE through this step. If no information such as TFT is required, the step can be skipped.
  • Step 604 X-MAG policy sent from the P-GW by the GTP signaling, and transmits to the interworking policy session by BPCF 0
  • Step 605 The BPCF maps the policy obtained from the X-MAG to a fixed network policy according to the local policy, and sends the BNG/BRAS and/or other fixed network policy execution network elements through the fixed network policy session.
  • the BNG/BRAS and/or other fixed network policy enforcement NEs implement the received policies and configure the fixed network resources.
  • the result is fed back to BPCF through the fixed network policy session.
  • Step 606 The BPCF sends an interworking policy session response signaling to the X-MAG to notify the X-MAG that the fixed network policy is complete.
  • Step 607 The X-MAG is triggered by step 606 to send a GTP-enabled create/update response message to the P-GW.
  • Step 608 The P-GW sends an IP-CAN session modification response signaling to the PCRF to notify the completion of the PCC policy delivered by the PCRF.
  • FIG. 7 is a flowchart of a bearer deletion initiated by the fixed network implemented by the architecture shown in FIG. 3, and describes a flow chart of the network side initiated to delete, and a fixed network as a trusted non-3GPP access of the EPS network, where The flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • the UE accesses the EPS through the attach procedure, the fixed network policy session between the BNG/BRAS and the BPCF, and the interworking policy session between the X-MAG and the BPCF have been established and correctly Association.
  • Figure 7 illustrates: The PCRF sends the relevant PCC policy (bearer deactivation) to the P-GW to trigger the P-GW to initiate bearer deactivation, or the P-GW initiates bearer deactivation for its own reasons, and the P-GW sends GTP.
  • the protocol deletes the bearer signaling to the X-MAG, and the X-MAG then sends the policy to the fixed network BPCF through the interworking policy session.
  • BPCF integrates the fixed network's own policy and notifies the BNG/BRAS to execute it. The execution result is finally fed back to the PCRF.
  • Step 701 The PCRF initiates an IP-CAN session modification operation, and the related PCC policy is sent to the P-GW, for example, the bearer identifier to be deactivated.
  • This step is an optional step.
  • Step 702 The P-GW sends a GTP protocol deletion request message to the X-M AG.
  • Step 703 The X-MAG negotiates resource configuration with the UE.
  • This step is an optional step, that is, if there is a corresponding TFT on the network side, the UE is notified to delete it; if not, the step can be skipped.
  • Step 704 The X-MAG is triggered by the delete bearer request message sent by the P-GW, and the interworking policy session modification step is initiated to notify the BPCF to release the corresponding resource.
  • Step 705 The BPCF maps the policy obtained from the X-MAG to a fixed network policy according to the local policy, and sends the BNG/BRAS and/or other fixed network policy execution network elements through the fixed network policy session.
  • the BNG/BRAS and/or other fixed network policy enforcement network elements implement the received policies and release the fixed network resources.
  • the result is fed back to BPCF through the fixed network policy session.
  • Step 706 The BPCF sends an interworking policy session response signaling to the X-MAG to notify the X-MAG that the fixed network policy execution (resource release) is completed.
  • Step 707 The X-MAG is triggered by step 706 to send a delete bearer response message of the GTP protocol to the P-GW.
  • Step 708 The P-GW sends an IP-CAN session modification response signaling to the PCRF to notify the PCRF that the bearer deactivation is performed. This step is optional and corresponds to step 701.
  • FIG. 8 is a flowchart of a terminal-initiated detach/PDN connection release implemented by the architecture shown in FIG. 3, and describes a flow chart of the detachment/additional PDN connection release of the terminal through the fixed network to the EPS, and the fixed network as a fixed network. Trusted non-3GPP access of the EPS network, wherein the flowchart includes various scenarios such as roaming, non-roaming, and the like.
  • a fixed network policy session is established between the BNG/BRAS and the BPCF, and an interworking policy session, a fixed network policy session, and an interworking policy session are established between the X-MAG and the BPCF, and the UE can exchange data with the external PDN.
  • Figure 8 illustrates: HSS/AAA or UE or fixed network itself or X-MAG initiates PDN connection release or user access detach operation, and delete operation of related bearer, session, context, etc. of EPS network.
  • Step 800 The HSS/AAA sends a detach indication to the X-MAG, instructing the X-MAG to initiate a detach/PDN connection release. This is a scenario that triggers the operation shown in Figure 8;
  • Step 801 The UE sends a Layer 3 negotiation termination signaling to the X-MAG to initiate a detach/PDN connection release. This is the second scenario that triggers the operation shown in Figure 8;
  • Step 802 The X-MAG decides to initiate the detach/PDN connection release for its own reasons. This is the third scenario that triggers the operation shown in Figure 8.
  • the X-MAG sends a GTP protocol delete session request message to the P-GW, requesting to cancel the tunnel binding with the P-GW.
  • Step 803 After receiving the delete session request message, the P-GW releases the binding relationship with the X-MAG. The P-GW terminates the IP-CAN session with the PCRF.
  • Step 804 The P-GW responds to the X-MAG network element with a delete session response message.
  • Step 805 If there is step 800, the X-MAG sends a de-attach to the HSS/AAA. Response signaling.
  • Step 806 The X-MAG network element completes three layers of negotiation with the UE, and releases the connection between the two.
  • Step 808 The fixed network resource is released or reconfigured.
  • step 807 may also occur after step 802, or may occur after step 804, or may occur after step 806 as shown.
  • FIG. 9 is a flowchart of a terminal-initiated bearer resource modification implemented by the architecture shown in FIG. 3, and describes a bearer resource modification operation initiated by a UE after a terminal uses a fixed network as a trusted non-3GPP access of an EPS network.
  • the flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • a fixed network policy session is established between the BNG/BRAS and the BPCF, and an interworking policy session is established between the X-MAG and the BPCF.
  • the unified PCC policy and the direction are downloaded from the PCRF.
  • the PCRF reports the fixed network event.
  • Step 901 The UE sends a Layer 3 bearer resource modification request to the X-MAG, where the UE requests to establish/repair the bearer resource from the EPS core network.
  • Step 902 The X-MAG sends a GTP protocol bearer resource command message to the P-GW to request resource modification.
  • Step 903 After receiving the resource command message, the P-GW initiates an IP-CAN session modification operation to the PCRF, requests the PCRF to verify the resource modification, and the PCRF verifies and returns the result to the P-GW.
  • Step 904 A bearer creation/modification/deletion operation initiated by the P-GW.
  • the operation of this step is similar to the principle of the corresponding operation in Figs. 6 and 7.
  • Step 905 The P-GW notifies the PCRF resource modification result by using the IP-CAN session modification completion message.
  • the interaction of the interworking policy session between the X-MAG and the BPCF may be as shown in the figure, that is, after the X-MAG receives the GTP message sent by the P-GW, it may also be sent. Born after the X-MAG receives the message of step 901. If it occurs after step 901, when the fixed network cannot provide the resource requested by the UE, the X-MAG can directly reject the request without performing the subsequent steps.
  • FIG. 10 is an attached flow chart implemented by the architecture shown in FIG. 4, which describes a flow chart for establishing an attach/additional PDN connection for a terminal to access an EPS through a fixed network, and a trusted non-3GPP access for a fixed network as an EPS network.
  • the flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • a fixed network policy session is established between BNG/BRAS and BPCF, the session, GTP signaling between BNG/BRAS and P-GW, and IP-CAN session between P-GW and PCRF,
  • the unified PCC policy is downloaded from the PCRF and the fixed network event is reported to the PCRF.
  • Step 1001 The UE passes the authentication according to the 3GPP authentication mode.
  • Step 1002 The UE initiates an access request in the fixed network.
  • Step 1003 Upon being triggered by the access request, the BNG/BRAS initiates a fixed network policy session establishment request to the BPCF. Through this step, the BNG/BRAS and the BPCF establish a session for applying/delivering a dynamic policy, so as to achieve accurate control of network resource allocation and user admission.
  • Step 1004 The BNG/BRAS sends a GTP session creation session request message to the P-GW to request a tunnel binding with the P-GW.
  • Step 1005 After receiving the Create Session Request message, the P-GW allocates an IP address to the UE. The P-GW establishes an IP-CAN session with the PCRF.
  • Step 1006 The P-GW sends an APN/P-GW identity pair to the 3GPP HSS/AAA, and requests the HSS/AAA to store the identifier of the P-GW to implement the P-GW identity update.
  • Step 1007 The P-GW responds to the BNG/BRAS to create a session response message, and carries the IP address assigned to the UE in the message.
  • Step 1008 The access is completed.
  • Step 1003 can be operated in two ways:
  • the BNG/BRAS is triggered by the step 1002 to initiate a fixed network policy session establishment request to the BPCF, and establish a second fixed network policy session belonging to the UE with the BPCF.
  • the fixed network policy session establishing the default PDN connection is the first fixed network policy session, and if there are additional PDN connections established, the third and fourth number of fixed network policies are also established. Conversation.
  • the BNG/BRAS receives the message of step 1002, and detects that a fixed network policy session has been established when the UE attaches, and the BNG/BRAS sends a fixed network policy session update operation to the BPCF to reuse the session.
  • each UE may have multiple fixed network policy sessions; if the (II) scheme is adopted, the UE has only one fixed network policy session.
  • FIG. 11 is a flowchart of a network-initiated bearer setup implemented by the architecture shown in FIG. 4, and describes a flow diagram of a network-side initiated bearer setup, and a fixed network as a trusted non-3GPP access of an EPS network, where the process
  • the diagram includes various scenarios such as roaming, non-roaming.
  • the UE accesses the EPS through the attach procedure.
  • the PCRF sends the relevant PCC policy to the P-GW, and the P-GW sends the control signaling to the BNG/BRAS through the GTP protocol.
  • the BNG/BRAS then sends the policy to the fixed network BPCF through the fixed network policy session.
  • BPCF integrates the fixed network's own strategy and feeds back the BNG/BRAS related results, and BNG/BRAS will implement the results.
  • Step 1101 The PCRF initiates an IP-CAN session modification operation, and the related operation is performed by the operation.
  • the PCC policy is sent to the P-GW.
  • Step 1102 The P-GW sends a GTP bearer creation/update request message to the BNG/BRAS, and carries the related PCC policy.
  • Step 1103 The BNG/BRAS negotiates the policy with the BPCF through the fixed network policy session, and the BPCF feeds back the result to the BNG/BRAS.
  • Step 1104 The BNG/BRAS initiates a specific step of the fixed network to complete the resource reconfiguration.
  • Step 1105 The BNG/BRAS is triggered by the resource reconfiguration completion event in step 1104, and sends a bearer creation/update response message of the GTP protocol to the P-GW.
  • Step 1108 The P-GW sends an IP-CAN session modification response signaling to the PCRF to notify the completion of the PCC policy delivered by the PCRF.
  • FIG. 12 is a flowchart of a bearer deletion initiated by a fixed network implemented by the architecture shown in FIG. 4, and describes a flow chart of a bearer deletion initiated by a network side.
  • the fixed network is a trusted non-3GPP access of the EPS network, and the flow chart includes various scenarios such as roaming and non-roaming.
  • the UE accesses the EPS through the attach procedure, and the PCRF sends the relevant PCC policy (bearer deactivation) to the P-GW to trigger the P-GW to initiate the bearer deactivation, or the P-GW initiates the bearer for its own reasons.
  • the P-GW sends the GTP protocol to delete the bearer signaling to the BNG/BRAS.
  • the BNG/BRAS negotiates with the BPCF, the fixed network resources are released, and the resource release result is finally fed back to the PCRF.
  • Step 1201 The PCRF initiates an IP-CAN session modification operation, and the related PCC policy is sent to the P-GW, for example, the bearer identifier to be deactivated.
  • This step is an optional step.
  • Step 1202 The P-GW sends a GTP protocol delete bearer request message to the BNG/BRAS.
  • Step 1205 The BNG/BRAS is triggered by the resource release completion event in step 1204, and sends a delete bearer response message of the GTP protocol to the P-GW.
  • Step 1206 The P-GW sends an IP-CAN session modification response signaling to the PCRF to notify the PCRF that the bearer deactivation is complete. This step is optional and corresponds to step 1201.
  • FIG. 13 is a flowchart of terminal-initiated detach/PDN connection release implemented by the architecture shown in FIG. 4, and describes a flow chart of detachment/additional PDN connection release of the terminal through the fixed network access EPS.
  • the fixed network is a trusted non-3GPP access of the EPS network, and the flow chart includes various scenarios such as roaming and non-roaming.
  • the HSS/AAA or UE or BNG/BRAS initiates a PDN connection release or a user access detach operation.
  • the operation of the EPS network related to bearer, session, context, etc.
  • Step 1301 The HSS/AAA sends a detach indication to the BNG/BRAS, instructing the BNG/BRAS to initiate a detach/PDN connection release. This is a scene that triggers the operation shown in Figure 13;
  • Step 1302 The UE sends a detach/PDN connection release request to the BNG/BRAS. This is the second scenario that triggers the operation shown in Figure 13;
  • Step 1303 BNG/BRAS decides to initiate the release of the detach/PDN connection for its own reasons. This is the third scenario that triggers the operation shown in Figure 13.
  • the BNG/BRAS sends a GTP protocol delete session request message to the P-GW, requesting to unbind the tunnel with the P-GW.
  • Step 1304 After receiving the delete session request message, the P-GW cancels the binding relationship with the BNG/BRAS. The P-GW terminates the IP-CAN session with the PCRF.
  • Step 1305 The P-GW responds to the BNG/BRAS network element with a delete session response message.
  • Step 1306 The BNG/BRAS initiates a fixed network policy session repair termination operation to the BPCF.
  • Step 1307 The BNG/BRAS initiates release or reconfiguration of the fixed network resource.
  • Step 1308 If step 1301 exists, the BNG/BRAS sends a de-attach response signaling to the HSS/AAA.
  • step 1306 may occur after step 1302, or may occur after step 1305 as shown in the figure.
  • FIG. 14 is a flowchart of a terminal-initiated bearer resource modification implemented by the architecture shown in FIG. 4, and describes a bearer resource modification operation initiated by a UE after a terminal uses a fixed network as a trusted non-3GPP access of an EPS network.
  • the flow chart includes various scenarios such as roaming, non-roaming, and the like.
  • Step 1401 The UE sends a resource modification request to the BNG/BRAS for requesting to establish/repair/delete the bearer resource to the EPS core network.
  • Step 1402 The BNG/BRAS sends a GTP protocol bearer resource instruction message to the P-GW to request resource modification.
  • Step 1403 After receiving the resource command message, the P-GW initiates an IP-CAN session modification operation to the PCRF, requests the PCRF to verify the resource modification, and the PCRF verifies and returns the result to the P-GW.
  • Step 1404 The bearer creation/modification/delete operation initiated by the P-GW.
  • the operation of this step is similar to the principle of the corresponding operation in Figs. 11 and 12.
  • Step 1405 The P-GW notifies the PCRF resource modification result by using an IP-CAN session modification completion message.
  • the interaction of the fixed network policy session between the BNG/BRAS and the BPCF may be as shown in the figure, that is, after the BNG/BRAS receives the GTP message sent by the P-GW, it may also occur in the BNG.
  • /BRAS receives the message of step 1401. If it occurs after step 1401, when the fixed network cannot provide the resources requested by the UE, the BNG/BRAS can directly reject the request without performing the subsequent steps.
  • FIG. 15 is a schematic flowchart of implementing resource control in a fixed network mobile network convergence scenario, where the process includes the following steps:
  • Step 1510 Establish a GTP interface between the P-GW and the fixed network.
  • Step 1520 The PCRF exchanges communication information such as policy information with the fixed network via the P-GW and the established GTP interface.
  • the policy information includes related service quality information and event information related to communication.
  • the BPCF sends the policy information to the BNG/BRAS and/or other fixed network policy enforcement network elements and is used for execution.
  • the execution network element here may also be the BPCF itself. That is, the BPCF may perform some of the acquired policies, such as admission control services. It is also possible to integrate BPCF into AAA.
  • the X-MAG is a network element that is assigned to the fixed network by default, but in reality, the possibility of classifying the X-MAG as part of the mobile network according to the network deployment is not excluded. For example: Add X-MAG to an existing mobile network. When the X-MAG joins a network, the X-MAG is not between the fixed network and the mobile network, but is part of the network.
  • X-MAG can also be integrated into the existing BNG/BRAS as an enhanced module, for example: Rejecting the BNG/BRAS machine without changing or slightly changing the BNG/BRAS
  • the above solution can be implemented by the X-MAG module.
  • Such an implementation method is simple, convenient, easy to implement, and has the advantage of reducing operating costs for the operator.
  • the method of implementing the resource control in the fixed network mobile network convergence scenario of the present invention can establish a GTP interface between the P-GW and the fixed network, and change the S2a interface to the GTP. Interface, and no longer use the PMIPv6 protocol-based interface that was previously used. Moreover, due to the interface change between the P-GW and the fixed network, the direct interface between the PCRF and the BPCF is no longer needed; finally, the PCRF can be established via the P-GW and the established The GTP interface interacts with the fixed network to include communication information such as policy information related to communication related policies.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé et à un système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile. Le procédé et le système selon l'invention sont tous les deux aptes à établir des interfaces du protocole de tunnelisation GPRS (General Packet Radio Service, service de communication radio en mode paquet) entre une passerelle d'un réseau de données en paquet et un réseau fixe. Selon la présente invention, une fonction de règles de politique et de facturation fait interagir des informations basées sur des règles avec le réseau fixe par le biais de la passerelle du réseau de données en paquet et lesdites interfaces du protocole de tunnelisation GPRS. Le procédé et le système selon la présente invention sont aptes à réduire de manière palpable l'influence sur le mécanisme de traitement de la fonction de règles de politique et de facturation elle-même et sur le caractère d'interaction externe sans utiliser l'interface S9*. Le procédé et le système selon l'invention suppriment également la nécessité d'améliorer la fonction de règles de politique et de facturation, ce qui permet à son tour de réduire de manière palpable l'influence sur un système de paquets évolué. D'autre part, ladite nouvelle relation d'interface et ladite nouvelle manière d'interagir en termes d'informations de communication permettent de mettre en œuvre une gestion et un contrôle de ressources avec une grande efficacité et d'atteindre l'objectif visé d'améliorer la mise à niveau du contrôle et de la gestion de ressources.
PCT/CN2011/077487 2010-08-09 2011-07-22 Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile WO2012019506A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010251617.2 2010-08-09
CN201010251617.2A CN102378267B (zh) 2010-08-09 2010-08-09 在固网移动网络融合场景下实现资源控制的方法和系统

Publications (1)

Publication Number Publication Date
WO2012019506A1 true WO2012019506A1 (fr) 2012-02-16

Family

ID=45567356

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077487 WO2012019506A1 (fr) 2010-08-09 2011-07-22 Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile

Country Status (2)

Country Link
CN (1) CN102378267B (fr)
WO (1) WO2012019506A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740283B (zh) * 2012-06-20 2015-02-04 北京傲天动联技术股份有限公司 Lte系统中的网关设备及其数据分流方法
CN103634941B (zh) * 2012-08-23 2018-04-10 中兴通讯股份有限公司 资源释放方法及装置
CN111770545B (zh) * 2019-04-02 2022-08-26 华为技术有限公司 一种业务流路由控制方法、装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369939A (zh) * 2007-08-17 2009-02-18 华为技术有限公司 接入网类型信息传递方法、系统和相关设备
WO2009055827A1 (fr) * 2007-10-25 2009-04-30 Starent Networks, Corp. Passerelle d'interfonctionnement pour nœuds mobiles
CN101494538A (zh) * 2008-01-23 2009-07-29 华为技术有限公司 一种数据传输控制方法及通讯系统以及加密控制网元
CN101730074A (zh) * 2009-04-28 2010-06-09 中兴通讯股份有限公司 链式连接建立方法、服务网关及分组数据网网关
CN101729265A (zh) * 2008-10-25 2010-06-09 华为技术有限公司 在演进的分组系统eps中进行计费的方法、装置和系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101267319B (zh) * 2008-04-30 2011-07-13 中兴通讯股份有限公司 一种下发策略计费控制规则的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369939A (zh) * 2007-08-17 2009-02-18 华为技术有限公司 接入网类型信息传递方法、系统和相关设备
WO2009055827A1 (fr) * 2007-10-25 2009-04-30 Starent Networks, Corp. Passerelle d'interfonctionnement pour nœuds mobiles
CN101494538A (zh) * 2008-01-23 2009-07-29 华为技术有限公司 一种数据传输控制方法及通讯系统以及加密控制网元
CN101729265A (zh) * 2008-10-25 2010-06-09 华为技术有限公司 在演进的分组系统eps中进行计费的方法、装置和系统
CN101730074A (zh) * 2009-04-28 2010-06-09 中兴通讯股份有限公司 链式连接建立方法、服务网关及分组数据网网关

Also Published As

Publication number Publication date
CN102378267B (zh) 2016-03-30
CN102378267A (zh) 2012-03-14

Similar Documents

Publication Publication Date Title
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
KR101340496B1 (ko) 차징 시스템 및 방법
US8849273B2 (en) Method and system for reporting fixed network access information
US9113436B2 (en) Method and system for information transmission
WO2009135362A1 (fr) Procédé de commande de politique et de facturation pour cacher la topologie d'un réseau visité
WO2011006317A1 (fr) Procédé et système permettant d'effacer des informations redondantes d'une fonction d’imputation et de règles domestique
WO2013104234A1 (fr) Procédé et système de contrôle de règles pour un réseau convergé
WO2010081329A1 (fr) Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services
WO2012051897A1 (fr) Système et procédé pour intégrer un réseau fixe avec un réseau mobile
WO2012003770A1 (fr) Système, dispositif et procédé permettant à un équipement utilisateur d'accéder à un réseau mobile
US9544832B2 (en) Method, apparatus and system for policy control
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2012022222A1 (fr) Procédé et système permettant une association de sessions de contrôle de politique
CN102904856A (zh) 一种共享会话的控制方法及装置
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
WO2010054560A1 (fr) Procédé et système de mise en œuvre d’un accès multiple
WO2013016967A1 (fr) Procédé et système d'accès, et point d'accès intelligent mobile
WO2011088702A1 (fr) Procédé et système permettant de contrôler des ressources dans un réseau de convergence multiservice
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
WO2012010036A1 (fr) Procédé et système de contrôle de politique
WO2012019506A1 (fr) Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile
WO2014169781A1 (fr) Procédé et système de fermeture de connexion par un utilisateur
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"
WO2011026409A1 (fr) Procédé, appareil et système de mise à jour de session

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11816065

Country of ref document: EP

Kind code of ref document: A1