EP3286879B1 - Commande de politique basée sur un réseau pour des accès hybrides - Google Patents

Commande de politique basée sur un réseau pour des accès hybrides Download PDF

Info

Publication number
EP3286879B1
EP3286879B1 EP16718641.0A EP16718641A EP3286879B1 EP 3286879 B1 EP3286879 B1 EP 3286879B1 EP 16718641 A EP16718641 A EP 16718641A EP 3286879 B1 EP3286879 B1 EP 3286879B1
Authority
EP
European Patent Office
Prior art keywords
hcpe
policy
server
network
hag
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP16718641.0A
Other languages
German (de)
English (en)
Other versions
EP3286879A1 (fr
Inventor
Jaume Rius I Riu
Sumit Singhal
Suresh Krishnan
Filipe Alexandre RODRIGUES DE MOURA LEITAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3286879A1 publication Critical patent/EP3286879A1/fr
Application granted granted Critical
Publication of EP3286879B1 publication Critical patent/EP3286879B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • 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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention generally relates to network-based control of policies for hybrid fixed broadband access and mobile broadband access for end user service delivery; and, more specifically, the invention relates to coordination and synchronization of policies.
  • Hybrid Access for broadband networks is defined as the bonding of two heterogeneous access technologies, opening the way to new scenarios based on higher throughputs and increased network resilience. Operators with the Hybrid Access may provide extra capacity when instantaneous capacity demand exceeds capacity available through one access technology.
  • the customer premises can be materialized in residential or enterprise access gateways that mask network complexity and serving WAN accesses from the end users or services. All-in-all, the end user is agnostic about the access or path being used by the service's traffic, which is totally transparent to him.
  • CPE Customer Premises Equipment
  • CWMP CPE WAN Management Protocol
  • Broadband Forum SDO specifically in BBHome Working Group
  • ACS auto-configuration server
  • Hybrid Access concept has been extended to use a mobile access technology in addition to the fixed access technology.
  • the operator is enhancing and complementing the network coverage in places where fixed access deployments are not mature, or where investment and evolution is not feasible (e.g. rural and remote areas). Even urban areas with mature fixed access deployments can benefit from this paradigm.
  • a basic high-level scenario for implementation of the Hybrid Access includes a Hybrid Access Customer Premises Equipment (HCPE), which can be a residential or enterprise gateway with two WAN links for each network access; a Hybrid Access Gateway (HAG), which may be placed in the packet core network to serve as central node for possible bonding and traffic distribution; and a Policy Controller in charge of controlling the remotely and dynamically oriented traffic distribution on the HCPE and HAG.
  • HCPE Hybrid Access Customer Premises Equipment
  • HAG Hybrid Access Gateway
  • the functional aspects associated with the logical HAG may be implemented in different network nodes and domains: in a PDN Gateway (PGW), if the traffic aggregation point is to be placed at the mobile network domain; in a Broadband Network Gateway (BNG), if the traffic aggregation point is to be placed at the fixed network domain; or as a stand-alone node.
  • PGW PDN Gateway
  • BNG Broadband Network Gateway
  • WO 2014067711 A1 and also EP 2728802 A1 are apparently tailored for digital subscriber line (DSL) and 3GPP system and focus on tunnelling implementation.
  • PEPs policy enforcement points
  • HAG hybrid access gateway
  • HCPE hybrid customer premises equipment
  • the present invention is aimed to at least minimize the above drawbacks and provides for a method of controlling policies for accesses to a core network, through a fixed network and a mobile network, for a HCPE.
  • the present invention provides for this method carried out by the HCPE, carried out by a policy server and carried out by a configuration server.
  • the present invention also provides for enhanced HCPE, policy server and configuration server respectively carrying out the above methods.
  • This method comprises: a step of establishing a communication session, by the HCPE with a network gateway, through at least one of the fixed network and the mobile network; a step of receiving, at a policy server from the network gateway, information about the communication session; and a step of transmitting, from the policy server to a configuration server, subscription data for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • This method also comprises: a step of obtaining, by the configuration server, the first policy associated with the subscription data and to be applied at the HCPE; a step of installing, from the configuration server to the HCPE, the first policy to trigger traffic distribution at the HCPE; a step of transmitting, from the HCPE to a HAG, traffic addressing the core network; a step of establishing a protocol session, by the HAG with the policy server, for the HCPE; and a step of installing, from the policy server to the HAG, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • this method may further comprise transmitting from the policy server, and receiving at the configuration server, the first policy associated with the subscription data and to be applied at the HCPE. So that the configuration server directly obtains from the policy server this first policy associated with the subscription data.
  • the first policy may be associated with the subscription data at a data repository, and the method may further comprise using the subscription data to obtain, at the configuration server from the data repository, the first policy associated with the subscription data.
  • this method may further comprise installing, from the policy server to the network gateway, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this method may still further comprise obtaining, by the configuration server, a fourth policy to be applied at the HCPE, and installing, from the configuration server, the fourth policy to the HCPE.
  • this fourth policy may be any one of a further policy to trigger downlink traffic distribution at the HCPE and an update policy to update traffic distribution at the HCPE.
  • this fourth policy may be obtained by the configuration server from the policy server or from the data repository.
  • any policy to trigger traffic distribution at the HCPE may be installed, from the configuration server to the HCPE, with a configuration message in accordance with a so-called TR-069 protocol or CWMP.
  • any transmission, from the policy server to the configuration server may be carried out with a SOAP notification.
  • a method of controlling policies for accesses to a core network, through a fixed network and a mobile network, for a HCPE the method carried out by the HCPE.
  • This method comprises: a step of establishing a communication session, by the HCPE with a network gateway, through at least one of the fixed network and the mobile network; a step of receiving from a configuration server, and enforcing at the HCPE, a policy to be applied at the HCPE to trigger traffic distribution at the HCPE; and a step of transmitting, to a HAG, traffic addressing the core network based on the received policy.
  • the received policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • this method may further comprise receiving from the configuration server, and enforcing at the HCPE, a further policy to be applied at the HCPE to trigger downlink traffic distribution at the HCPE.
  • this method may further comprise receiving from the configuration server, and enforcing at the HCPE, an update policy to update traffic distribution at the HCPE.
  • the update policy may update any one of downlink and uplink traffic distribution at the HCPE.
  • a method of controlling policies for accesses to a core network, through a fixed network and a mobile network, for a HCPE the method carried out by a policy server.
  • This method comprises: a step of receiving, at the policy server from a network gateway, information about a communication session established by the HCPE through at least one of the fixed network and the mobile network; a step of transmitting, from the policy server to a configuration server, subscription data for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE; a step of establishing a protocol session, between the policy server and a HAG, for the HCPE; and a step of installing, from the policy server to the HAG, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • this method may further comprise transmitting, from the policy server to the configuration server, the first policy associated with the subscription data and to be applied at the HCPE. So that the configuration server directly obtains from the policy server this first policy associated with the subscription data.
  • the subscription data is transmitted from the policy server to obtain, at the configuration server from a data repository, the first policy to be applied at the HCPE and associated with the subscription data at the data repository.
  • the first policy may be generated by the policy server to trigger uplink traffic distribution at the HCPE, whereas the second policy may be installed to trigger downlink traffic distribution at the HAG.
  • this method may further comprise installing, from the policy server to the network gateway, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway.
  • a method of controlling policies for accesses to a core network, through a fixed network and a mobile network, for a HCPE the method carried out by a configuration server.
  • This method comprises: a step of receiving, from a policy server, subscription data for the HCPE, the subscription data associated with a policy to be applied at the HCPE to trigger traffic distribution at the HCPE; a step of obtaining, at the configuration server, the policy associated with the subscription data and to be applied at the HCPE; and a step of installing the policy, from the configuration server to the HCPE, to trigger traffic distribution at the HCPE.
  • this method may further comprise receiving, from the policy server, the policy associated with the subscription data and to be applied at the HCPE. So that the configuration server directly obtains from the policy server this policy associated with the subscription data.
  • the policy may be associated with the subscription data at a data repository and this method may further comprise using the subscription data to obtain, from the data repository, the policy to be applied at the HCPE and associated with the subscription data.
  • the obtained policy may be installed to trigger uplink traffic distribution at the HCPE.
  • this method may further comprise installing to the HCPE, for enforcement therein, a further policy to be applied at the HCPE to trigger downlink traffic distribution at the HCPE.
  • this method may further comprise installing to the HCPE, for enforcement therein, an update policy to update traffic distribution at the HCPE.
  • the update policy may update any one of downlink and uplink traffic distribution at the HCPE.
  • a HCPE for accesses to a core network through a fixed network and a mobile network.
  • This HCPE may comprise at least one processor and at least one memory that stores processor-executable instructions, wherein the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby said HCPE is operable to: establish a communication session, by the HCPE with a network gateway via a transmitter and a receiver, through at least one of the fixed network and the mobile network; receive, from a configuration server via a receiver, a policy to be applied at the HCPE to trigger traffic distribution; enforce, with a processor, the policy to be applied at the HCPE; and transmit, to a HAG via the transmitter, traffic addressing the core network based on the received policy. In particular, this policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • the HCPE may further be operable to receive, from the configuration server via the receiver, a further policy to be applied at the HCPE, and enforce with the processor the further policy.
  • This further policy may be enforced with the processor to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the HCPE may comprise a traffic handler configured to establish a communication session with a network gateway, via the transmitter and the receiver, through at least one of the fixed network and the mobile network, and configured to transmit, to the HAG via the transmitter, traffic addressing the core network based on a policy received to trigger traffic distribution.
  • the HCPE may comprise a policy handler configured to receive, from a configuration server via a receiver, a policy to be applied at the HCPE to trigger traffic distribution, and configured to enforce the policy to trigger traffic distribution.
  • this policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • the policy handler may further be configured to receive, from the configuration server via the receiver, a further policy to be applied at the HCPE, and the policy handler may further be configured to enforce the further policy to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • a policy server for controlling policies for accesses by a HCPE to a core network through a fixed network and a mobile network.
  • This policy server may comprise at least one processor and at least one memory that stores processor-executable instructions, wherein the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby said policy server is operable to: receive, from a network gateway via a receiver, information about a communication session established by the HCPE through at least one of the fixed network and the mobile network; transmit, to a configuration server via a transmitter, subscription data for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE; establish, by a processor via the transmitter and the receiver, a protocol session with a HAG for the HCPE; and install, to the HAG via the transmitter, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • the policy server may further be operable to transmit, to the configuration server via the transmitter, the first policy associated with the subscription data and to be applied at the HCPE.
  • this first policy may be generated by the processor to trigger uplink traffic distribution at the HCPE.
  • the second policy may be installed to trigger downlink traffic distribution at the HAG.
  • the policy server may further be operable to install, to the network gateway via the transmitter, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway.
  • the policy server may comprise a session handler configured to receive, from a network gateway via a receiver, information about a communication session established by the HCPE through at least one of the fixed network and the mobile network, and configured to establish, via the transmitter and the receiver, a protocol session, e.g. a Gx session, with a HAG for the HCPE.
  • a protocol session e.g. a Gx session
  • the policy server may comprise a policy handler configured to transmit, to a configuration server via a transmitter, subscription data for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and configured to install to the HAG, via the transmitter, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • a policy handler configured to transmit, to a configuration server via a transmitter, subscription data for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and configured to install to the HAG, via the transmitter, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • the policy handler may further be configured to transmit, to the configuration server via the transmitter, the first policy associated with the subscription data and to be applied at the HCPE.
  • the first policy may be generated by the policy handler to trigger uplink traffic distribution at the HCPE.
  • the second policy may be installed by the policy handler via the transmitter to trigger downlink traffic distribution at the HAG.
  • the policy handler 157 may further be configured to install, to the network gateway via the transmitter, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway.
  • a configuration server for controlling policies for accesses to a core network, through a fixed network and a mobile network, for a HCPE.
  • This configuration server may comprise at least one processor and at least one memory that stores processor-executable instructions, wherein the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby said configuration server is operable to: receive, from a policy server via a receiver, subscription data for the HCPE, the subscription data associated with a policy to be applied at the HCPE to trigger traffic distribution at the HCPE; obtain, by a processor, the policy associated with the subscription data and to be applied at the HCPE; and install, to the HCPE via a transmitter, the obtained policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the configuration server may further be operable to receive, from the policy server via the receiver, the policy associated with the subscription data and to be applied at the HCPE.
  • the policy may be associated with the subscription data at a data repository and the configuration server may further be operable to use the subscription data to obtain, by the processor from the data repository, the policy to be applied at the HCPE and associated with the subscription data at the data repository.
  • the obtained policy may be installed to trigger uplink traffic distribution at the HCPE.
  • the configuration server may further be operable to install, to the HCPE via the transmitter, a further policy to be applied at the HCPE.
  • This further policy may be installed to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the configuration server may comprise a policy handler configured to receive, from a policy server via a receiver, subscription data for the HCPE, the subscription data associated with a policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and configured to install, to the HCPE via a transmitter, the obtained policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the obtained policy may be installed by the policy handler to trigger uplink traffic distribution at the HCPE.
  • the policy handler may further be configured to receive, from the policy server via the receiver, the policy associated with the subscription data and to be applied at the HCPE. So that the policy handler may directly obtain this policy from the policy server.
  • the policy may be associated with the subscription data at a data repository and the configuration server may further comprise a subscription handler configured to use the subscription data to obtain, from the data repository, the policy to be applied at the HCPE and associated with the subscription data at the data repository.
  • the policy handler may further be configured to install, to the HCPE via the transmitter, a further policy to be applied at the HCPE.
  • This further policy may be installed to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the invention may be practised by a number of computer programs, in accordance with an eighth aspect of the invention, the computer programs comprising instructions which, when executed on at least the number of processors, cause the number of processors to carry out the methods discussed above.
  • the scope of the invention is defined by the appended claims.
  • the word “comprising” does not exclude the presence of other elements or steps than those listed and the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements.
  • any reference signs do not limit the scope of the claims; the invention may be at least in part implemented by means of both hardware and software; and several "means”, “modules” or “units” may be represented by a same item of hardware.
  • FIG. 3 A detailed architecture and mechanisms for network-based policy control in a hybrid access scenario is further discussed with reference to Fig. 3 .
  • the user plane is based on MP-TCP mechanisms, but it could be based in other link and transmission layer protocols and technologies.
  • Fig. 3 illustrates a HCPE 3, such as e.g. BelAir CPE + LTE dongle, enhancing the traditional wired connectivity with LTE connectivity, which is MP-TCP capable to bond and configure TCP flows in the uplink direction (but, again, any other user plane technology and protocol that can be policy controlled, could be used as well such as e.g. PPP, GRE tunneling, IP flows, etc.).
  • HCPE such as e.g. BelAir CPE + LTE dongle
  • MP-TCP capable to bond and configure TCP flows in the uplink direction
  • any other user plane technology and protocol that can be policy controlled could be used as well such as e.g. PPP, GRE tunneling, IP flows, etc.
  • This HCPE 3 exemplary comprises a 3GPP link connected with a PGW 5, a wired link connected with a BNG 6, and the MP-TCP functionality.
  • the 3GPP link is connected with the PGW 5 for both user plane and control of a TCP 2 flow, the latter carried out with an in-band control interface/protocol.
  • the wired link is connected with the BNG 6 for both user plane and control of a TCP 1 flow, the latter carried out with an in-band control interface/protocol.
  • Fig. 3 also illustrates a configuration server, such as e.g. Ericsson Remote Device Manager (ERDM) 4 implementing an ACS, to be able to communicate with the HCPE the required MP-TCP control messages, via the so-called TR-069 protocol.
  • the configuration server e.g. ERDM 4
  • the configuration server may communicate with a policy server, e.g. SAPC 1, via a Simple Object Access Protocol (SOAP).
  • SOAP Simple Object Access Protocol
  • Fig. 3 also illustrates a policy server, such as e.g. a SAPC Ericsson product 1 implementing a Policy and Charging Rules Function (PCRF) of a Policy and Charging Control (PCC) architecture, and which is able to configure profiles and subscriptions both at the network side (HAG 2, exemplary implemented by MSP) and the HCPE 3 side (via ERDM 4, as highlighted above).
  • this policy server e.g. SAPC 1
  • the configuration server e.g. ERDM 4 via SOAP
  • the MSP implementing the HAG 2 via a 3GPP Gx interface, as described in 3GPP TS 29.212 V13.4.0 and TS 29.213 V13.4.0.
  • Fig. 3 also illustrates a HAG 2, which may be MP-TCP capable, such as the MSP, and which is is able to bond and configure the TCP flows in the downlink direction.
  • HAG 2 may be MP-TCP capable, such as the MSP, and which is is able to bond and configure the TCP flows in the downlink direction.
  • Fig. 4 shows a more general scenario than the one illustrated in Fig. 3 and illustrates a high-level flow scheme also applicable for the exemplary scenario shown in Fig. 2 .
  • the policy enforcement domain includes a centralized policy server 10, which in Fig. 3 is implemented by the PCRF 1, and signaling interfaces (1) (2) (3) towards the HAG 20 and the HCPE 30. While the policy server interface towards the HAG can be based on existing signaling protocols, such as the 3GPP Diameter Gx disclosed in 3GPP TS 29.212, there is no similar interface that can be re-used between the policy server 10 and the HCPE 30.
  • the HCPE 30 being TR-069 capable.
  • This HCPE may thus be configured from the configuration server 70, e.g. ACS, through the TR-069 protocol (3).
  • the ACS may be responsible for remotely configuring and controlling hundreds of CPEs.
  • the solution throughout this specification takes advantage of the wide implementation of T-069 protocol between the ACS and the HCPE, and extends the policy server 10 with an interface to the configuration server 70, so that policies can be transmitted from the policy server 10 to the HCPE 30 via the configuration server 70, e.g. ACS.
  • the policy server is maintaining, or has access to, subscriber information for hybrid access clients, i.e. the operator would have only one entry point of configuration for both the HAG and HCPE traffic distribution policies; a second reason is that the 3GPP access link establishment can be used as trigger for the HCPE policies provision.
  • a first action could be the establishment of a 3GPP Gx session, between the HAG and the policy server 10, for example, through the HCPE 3GPP link (e.g. LTE link session establishment).
  • a Gx session is generally established between a Policy and Charging Enforcement Function, PCEF, included in a gateway and a PCRF 1, which is an exemplary policy server 10, as disclosed in 3GPP TS 23.203 V13.5.1 and TS 29.212 V13.4.0, so that the HAG may include a complete PCEF as disclosed in the standards, or only selected functionality for the purpose of the invention.
  • PCEF Policy and Charging Enforcement Function
  • a second action could be the transmission of corresponding policies from the policy server 10 to the configuration server 70, e.g. ACS, using a SOAP interface.
  • a third action could be the transmission of a corresponding TR-069 message from the configuration server 70, e.g. ACS, to the destination HCPE.
  • policies to trigger traffic distribution at the HCPE different embodiments are foreseeable.
  • the policy server 10 may transmit subscription data 71, i.e. subscription identification details, for the HCPE 30 to the configuration server 70, e.g. ACS, and the latter may use that information to obtain the policy to trigger traffic distribution at the HCPE on its own database, or in an external database accessible to the configuration server.
  • subscription data may comprise a subscriber identifier or an International Mobile Subscriber Identity (IMSI).
  • a policy is associated with the subscription data at a data repository, internal or external, and the configuration server 70 uses the subscription data 71 to obtain, from the data repository, the policy associated with the subscription data.
  • the policy server 10 may transmit to the configuration server 70, e.g. ACS, along with the subscription data 72 for the HCPE 30 shown in Fig. 5a , a corresponding policy or policy identifier that the configuration server 70 may install to the HCPE 30 through the TR-069 interface.
  • this policy or policy identifier may correspond to a rule or rule identifier.
  • the policy to trigger traffic distribution at the HCPE which is associated with the subscription data, may be sent from the policy server 10 to the configuration server 70 along with the subscription data 72.
  • these two embodiments can be generalized by stating that the policy server 10 transmits to the configuration server 70 configuration data 71 or 72 to obtain a first policy to be applied at the HCPE in order to trigger traffic distribution at the HCPE.
  • the configuration data 72 comprises the policy to be applied at the HCPE and subscription data for the HCPE.
  • the configuration data 71 comprises subscription data for the HCPE, and the configuration server 70 uses the subscription data to obtain, from a data repository, the policy to be applied at the HCPE, policy which is associated with the subscription data at that data repository.
  • the SOAP message sent to this end is preferably compliant with the standard defined by SOAP Version 1.2 Part 1: Messaging Framework, World Wide Web Consortium, 2007 (W3C ).
  • This exemplary method is carried out by a system fitting the scenarios shown in any one of Fig. 1 to Fig. 4 and is exemplarily based on the use of the 3GPP link to connect the HCPE 3 with the PGW 5 of the mobile network, as illustrated in Fig. 3 .
  • the HCPE 3 establishes a first communication session, e.g. PPPoE through the fixed network via the fixed link, with the BNG 6, during step S-910, and a second communication session, e.g. LTE IP-CAN through the mobile network via the mobile link, with the PGW 5, during step S-920.
  • a first communication session e.g. PPPoE
  • a second communication session e.g. LTE IP-CAN through the mobile network via the mobile link, with the PGW 5, during step S-920.
  • Further details for IP-CAN session establishment procedures can be found in section 4.1 of 3GPP TS 29.213.
  • the PGW 5 requests PCC rules from the PCRF 1.
  • the PCRF may have obtained one or more provisioned rules associated with the subscription profile applicable for the request, to be installed at the PGW.
  • the PCRF may install a rule with traffic redirection indication towards the HAG 2. This way selected traffic, e.g. TCP, may be redirected automatically to the HAG. Details about redirection of traffic from PGW 5 to HAG 2 may be found on 3GPP TS 29.212 and 3GPP TS 29.213.
  • the PCRF 1 transmits to the ACS 4 configuration data, with e.g. a SOAP notification, to trigger the corresponding remote HCPE configuration.
  • This message may follow the communication details as presented above.
  • the configuration data may be obtained by the PCRF 1 from data received in the request and/or from the subscription profile.
  • the SOAP message transmitted from the PCRF 1 to the ACS 4 comprises a subscription identification, e.g. IMSI, as illustrated in Fig. 5a and Fig. 5b , and it may also comprise corresponding dynamic or pre-defined policies, as illustrated in Fig. 5b , to be installed or configured at the HCPE 3.
  • a subscription identification e.g. IMSI
  • Fig. 5a and Fig. 5b may also comprise corresponding dynamic or pre-defined policies, as illustrated in Fig. 5b , to be installed or configured at the HCPE 3.
  • pre-defined policies the PCRF only needs to transmit the corresponding policy identification that is to be activated.
  • dynamic policies are those generated at the PCRF, whereas pre-defined policies are defined in a target entity and the PCRF simply activates them by providing the corresponding policy identifications to the target entity.
  • the ACS 4 Upon receipt of the SOAP notification, the ACS 4 builds a corresponding TR-069 message and transmits it to the HCPE 3 during step S-940. During this process, if neither dynamic nor pre-defined policies were received from the PCRF, the ACS may select the corresponding policies to install using the received subscription identification.
  • the HCPE 3 may start transmitting traffic to the network during step S-950. As indicated by the policies installed at PGW 5 during step S-920, the PGW 5 redirects traffic to the HAG 2. At this point, and if the configuration data had not been received by the ACS and policies are not received at the HCPE, the HCPE may use default or pre-installed traffic distribution policies existing at the HCPE or received from previous interactions with the ACS.
  • step S-260 The reception of traffic from the HCPE 3 at the HAG 2, during step S-950, triggers a step S-260 wherein the HAG engages in a Gx session establishment with the PCRF 1, as per 3GPP TS 29.213, but with the exception that there is no bearer establishment.
  • the PCRF 1 may transmit to the HAG 2 the corresponding dynamic or pre-defined policies that will trigger the downlink traffic distribution at the HAG.
  • the PCRF 1 may optionally be triggered to transmit a further SOAP notification towards the ACS 4 to trigger a corresponding further remote HCPE configuration, such as for updating a previous policy, or for installing or removal of a previous policy.
  • a further SOAP notification towards the ACS 4 to trigger a corresponding further remote HCPE configuration, such as for updating a previous policy, or for installing or removal of a previous policy.
  • This process is similar as the one described during step S-930.
  • the ACS 4 behaves as during step S-940, builds a corresponding TR-069 message and transmits the TR-069 message to the HCPE 3 during step S-980.
  • An embodiment for an overall method of controlling policies for accesses to a core network, through a fixed network and a mobile network, for the HCPE, is further discussed with reference to Fig. 10 .
  • This embodiment does not distinguish between using the mobile link or the fixed link because the actions are substantially similar, or the same.
  • the HCPE 3 or 30 establishes a communication session with a network gateway through at least one of the fixed network 40 and the mobile network 50.
  • the network gateway is the BNG 6 illustrated in e.g. Fig. 2 ; and, where the communication session is established through the mobile network, the network gateway is the PGW 5 illustrated in e.g. Fig. 2 .
  • the network gateway 5 or 6 transmits to the policy server 1 or 10, and the policy server receives, information about the communication session to be established for the HCPE. Also during step S-110, the policy server may obtain, if not already available at the policy server, configuration data 71 or 72 for the HCPE based on the information about the communication session received from the network gateway and/or subscription data obtained from a subscription profile repository, SPR, as disclosed on 3GPP TS 23.203.
  • the policy server transmits toward a configuration server 4 or 70, during step S-120, the configuration data 71 or 72 to obtain a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • a configuration server 4 or 70 transmits toward a configuration server 4 or 70, during step S-120, the configuration data 71 or 72 to obtain a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • any one of the embodiments discussed above with reference to Fig. 5a and Fig. 5b may be applied for this transmission.
  • the configuration data 72, transmitted from the policy server and received at the configuration server may comprise the first policy to be applied at the HCPE and the configuration server directly obtains the first policy amongst the received configuration data; whereas, in a second embodiment, the configuration data 71, transmitted from the policy server and received at the configuration server, may comprise subscription data for the HCPE.
  • the method may further comprise using, during step S-130, the subscription data 71 to obtain, at the configuration server from a data repository, the first policy to be applied at the HCPE and associated with the subscription data at the data repository.
  • the policy server may transmit instead, toward a configuration server 4 or 70, subscription data 71 or 72 for the HCPE, the subscription data associated with a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the policy server may or may not transmit to the configuration server the first policy 72 associated with the subscription data and to be applied at the HCPE.
  • the first policy is associated with the subscription data at a data repository, and the method may further comprise using, during step S-130, the subscription data 71 to obtain, at the configuration server from the data repository, the first policy associated with the subscription data.
  • any transmission, from the policy server to the configuration server, may be carried out with a SOAP notification following the communication details already discussed above.
  • the configuration server obtains, during step S-130, the first first policy to be applied at the HCPE.
  • the policy server any one of the embodiments discussed above with reference to Fig. 5a and Fig. 5b are also applicable for the configuration server to obtain the first first policy to be applied at the HCPE.
  • the configuration server installs to the HCPE 3 or 30, during step S-140, the first policy to trigger traffic distribution at the HCPE.
  • this first policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • any policy to trigger traffic distribution at the HCPE may be installed, from the configuration server to the HCPE, with a configuration message in accordance with a so-called TR-069 protocol or Customer Premises Equipment, CPE, WAN Management Protocol, CWMP.
  • traffic addressing the core network may be sent, during step S-150, from the HCPE to the HAG 2 or 20.
  • a protocol session e.g. 3GPP Gx session
  • the policy server may install to the HAG a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • this second policy is installed to trigger downlink traffic distribution at the HAG.
  • this method illustrated in Fig. 10 may further comprise a step of installing, from the policy server to the network gateway 5 or 6, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway 5 or 6.
  • this method may further comprise obtaining, by the configuration server, a fourth policy to be applied at the HCPE; and installing, from the configuration server, the fourth policy to the HCPE.
  • this fourth policy may be a further policy to be applied at the HCPE to trigger downlink traffic distribution at the HCPE, or an update policy to update traffic distribution at the HCPE.
  • the skilled person may arrive to corresponding specific methods respectively carried out by the HCPE 3 or 30, the policy server 1 or 10, and the configuration server 4 or 70.
  • the HCPE 3 or 30, the policy server 1 or 10, and the configuration server 4 or 70 are respectively illustrated in Fig. 6 , Fig. 7 and Fig. 8 , in accordance with an embodiment, and in Fig. 11, Fig. 12 and Fig. 13 , in accordance with another embodiment.
  • the HCPE 3 or 30 may comprise, as shown in Fig. 6 , at least one processor 320, and at least one memory 310 that stores processor-executable instructions 314.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the HCPE is operable to perform the actions disclosed in the following.
  • the HCPE 3 or 30 is thus operable to: establish a communication session, with a network gateway 5 or 6 via transmitter 340 and receiver 330, through at least one of the fixed network 40 and the mobile network 50; receive, from a configuration server 4 or 70 via receiver 330, a policy to be applied at the HCPE to trigger traffic distribution; enforce, with processor 320, the policy to be applied at the HCPE; and transmit, to a HAG 2 or 20 via transmitter 340, traffic addressing the core network 60 based on the received policy.
  • a traffic handler 322 running in a processor 320 may handle the establishment of the communication session and the traffic addressing the core network
  • a policy handler 326 also running in the processor 320 may handle the reception and enforcement of policies to trigger traffic distribution. Also in particular, this policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • the HCPE 3 or 30 may further be operable to receive, from the configuration server 4 or 70 via the receiver 330, a further policy to be applied at the HCPE, and to enforce with the processor 320 the further policy.
  • This further policy may be enforced with the processor 320 to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the HCPE 3 or 30 may be complemented with a data section 318 in memory to store any policy to be applied at the HCPE, any communication session data and/or addressing data.
  • the HCPE 3 or 30 illustrated in Fig. 6 may thus comprise the at least one processor 320 and the at least one memory 310, both in communication with each other, with the traffic handler 322, the policy handler 326, the receiver 330 and the transmitter 340, and with other elements or units of the HCPE 3 or 30.
  • the at least one memory 310 may comprise volatile and/or non-volatile memory.
  • the at least one memory 310 may have a computer program 314 and data 318 stored therein.
  • the computer program 314 may be loaded in the at least one memory 310 from a computer program product 350, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the at least one processor 320 may be configured to carry out the functions of the traffic handler 322 and the policy handler 326.
  • the HCPE 3 or 30 may comprise, as shown in Fig. 11 , a traffic handler 322 configured to establish a communication session with a network gateway 5 or 6, via the transmitter 340 and the receiver 330, through at least one of the fixed network 40 and the mobile network 50, and configured to transmit, towards the HAG 2 or 20 via the transmitter 340, traffic addressing the core network 60 based on a policy received to trigger traffic distribution.
  • a traffic handler 322 configured to establish a communication session with a network gateway 5 or 6, via the transmitter 340 and the receiver 330, through at least one of the fixed network 40 and the mobile network 50, and configured to transmit, towards the HAG 2 or 20 via the transmitter 340, traffic addressing the core network 60 based on a policy received to trigger traffic distribution.
  • the HCPE 3 or 30 may comprise a policy handler 326 configured to receive, from a configuration server 4 or 70 via the receiver 330, a policy to be applied at the HCPE to trigger traffic distribution, and configured to enforce the policy to trigger traffic distribution. In particular, this policy may be enforced to trigger uplink traffic distribution at the HCPE.
  • the policy handler 326 may further be configured to receive, from the configuration server 4 or 70 via the receiver 330, a further policy to be applied at the HCPE. This further policy may be enforced by the policy handler 326 to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • Fig. 7 illustrates a basic component structure of a policy server 1 or 10 in accordance with an embodiment.
  • This policy server may comprise, as shown in Fig. 7 , at least one processor 150, and at least one memory 160 that stores processor-executable instructions 162.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the policy server is operable to perform the actions disclosed in the following.
  • the policy server 1 or 10 is thus operable to: receive, from a network gateway 5 or 6 via receiver 180, information about a communication session established by a HCPE 3 or 30 through at least one of the fixed network 40 and the mobile network 50; transmit, to a configuration server 4 or 70 via transmitter 170, configuration data 71 or 72 to obtain a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE; establish, by a processor 150 via the transmitter 170 and the receiver 180, a protocol session, e.g. a Gx session, with a HAG 2 or 20 for the HCPE; and install, to the HAG via the transmitter 170, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • a protocol session e.g. a Gx session
  • a session handler 153 running in a processor 150 may handle the information about the communication session established by the HCPE 3 or 30 through at least one of the fixed network 40 and the mobile network 50, and may also handle the establishment of the protocol session, e.g. a Gx session, with the HAG 2 or 20 for the HCPE.
  • the protocol session e.g. a Gx session
  • a policy handler 157 running in the processor 150 may handle the configuration data 71 or 72 to obtain the first policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and may handle the second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • the configuration data transmitted from the policy server 1 or 10 to the configuration server 4 or 70 may follow the scheme illustrated in any one of Fig. 5a or Fig. 5b . That is, the configuration data 71 may comprise subscription data, as illustrated in Fig. 5a , to be used by the configuration server to obtain the first policy to be applied at the HCPE and associated with the subscription data at a data repository; or the configuration data 72 may directly comprise the first policy to be applied at the HCPE.
  • the policy server 1 or 10 may transmit to the configuration server 4 or 70 subscription data associated with the first policy at a data repository, which is accessible to the configuration server to obtain the first policy, or may directly transmit the first policy to be applied at the HCPE.
  • the first policy may be generated by the processor 150 to trigger uplink traffic distribution at the HCPE.
  • the second policy may be installed to trigger downlink traffic distribution at the HAG.
  • the policy server 1 or 10 may further be operable to install, to the network gateway 5 or 6 via the transmitter 170, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway 5 or 6.
  • the policy server 1 or 10 may be complemented with a data section 166 in memory to store any policy to be applied at the HCPE, any communication session data and/or any subscription data.
  • the policy server 1 or 10 illustrated in Fig. 7 may thus comprise the at least one processor 150 and the at least one memory 160, both in communication with each other, with the session handler 153, the policy handler 157, the receiver 180 and the transmitter 170, and with other elements or units of the policy server 1 or 10.
  • the at least one memory 160 may comprise volatile and/or non-volatile memory.
  • the at least one memory 160 may have a computer program 162 and data 166 stored therein.
  • the computer program 162 may be loaded in the at least one memory 160 from a computer program product 190, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the at least one processor 150 may be configured to carry out the functions of the session handler 153 and the policy handler 157.
  • the policy server 1 or 10 may comprise, as shown in Fig. 12 , a session handler 153 configured to receive, from a network gateway 5 or 6 via receiver 180, information about a communication session established by a HCPE 3 or 30 through at least one of the fixed network 40 and the mobile network 50, and configured to establish, via the transmitter 170 and the receiver 180, a protocol session, e.g. a Gx session, with a HAG 2 or 20 for the HCPE.
  • a protocol session e.g. a Gx session
  • the policy server 1 or 10 may comprise a policy handler 157 configured to transmit, to a configuration server 4 or 70 via transmitter 170, configuration data 71 or 72 to obtain a first policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and configured to install, to the HAG via the transmitter 170, a second policy to be applied at the HAG to trigger traffic distribution at the HAG.
  • the first policy may be generated by the policy handler 157 to trigger uplink traffic distribution at the HCPE.
  • the second policy may be installed by the policy handler 157 via the transmitter 170 to trigger downlink traffic distribution at the HAG.
  • the policy handler 157 may further be configured to install, to the network gateway 5 or 6 via the transmitter 170, a third policy with redirection information indicating a HCPE traffic redirection towards the HAG, and whereby the traffic addressing the core network and received at the network gateway is redirected to the HAG.
  • this third policy may be installed to trigger uplink traffic distribution at the network gateway 5 or 6.
  • the configuration data transmitted from the policy handler 157 to the configuration server 4 or 70 may follow the scheme illustrated in any one of Fig. 5a or Fig. 5b . That is, the configuration data 71 may comprise subscription data, as illustrated in Fig. 5a , to be used by the configuration server to obtain the first policy to be applied at the HCPE and associated with the subscription data at a data repository; or the configuration data 72 may directly comprise the first policy to be applied at the HCPE.
  • the policy handler 157 may transmit to the configuration server 4 or 70 subscription data associated with the first policy at a data repository, which is accessible to the configuration server to obtain the first policy, or may directly transmit the first policy to be applied at the HCPE.
  • Fig. 8 illustrates a basic component structure of a configuration server 4 or 70 in accordance with an embodiment.
  • This configuration server may comprise, as shown in Fig. 8 , at least one processor 450, and at least one memory 460 that stores processor-executable instructions 462.
  • the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the configuration server is operable to perform the actions disclosed in the following.
  • the configuration server 4 or 70 is thus operable to: receive, from a policy server 1 or 10 via receiver 480, configuration data 71 or 72 to obtain a policy to be applied at the HCPE 3 or 30 to trigger traffic distribution at the HCPE; obtain, by processor 450 and by using the received configuration data, the policy to be applied at the HCPE; and install, to the HCPE via transmitter 470, the obtained policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the configuration data received at the configuration server 4 or 70 from the policy server 1 or 10 may follow the scheme illustrated in any one of Fig. 5a or Fig. 5b . That is, the configuration data 71 may comprise subscription data, as illustrated in Fig. 5a , to be used by the configuration server to obtain the policy to be applied at the HCPE and associated with the subscription data at a data repository; or the configuration data 72 may directly comprise the policy to be applied at the HCPE.
  • the configuration server 4 or 70 may receive from the policy server 1 or 10 subscription data associated with the policy at a data repository, which is accessible to the configuration server to obtain the policy, or may directly receive, from the policy server, the policy to be applied at the HCPE.
  • a subscription handler 454 running in a processor 450 may obtain, by using the received configuration data 71, the policy to be applied at the HCPE to trigger traffic distribution at the HCPE; whereas, when the policy 72 to be applied at the HCPE is received at the configuration server from the policy server, a policy handler 456 running in the processor 450 may directly obtain the policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the policy handler 456 running in the processor 450 may handle the reception of the configuration data 71 or 72, transmitted from the policy server 1 or 10, and may handle the installation of the obtained policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the policy may be installed by the policy handler 456 to trigger uplink traffic distribution at the HCPE.
  • the configuration server 4 or 70 may further be operable to install, to the HCPE 3 or 30 via the transmitter 470, a further policy to be applied at the HCPE.
  • This further policy may be installed to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the configuration server 4 or 70 may be complemented with a data section 466 in memory to store any policy to be applied at the HCPE and/or any subscription data.
  • the configuration server 4 or 70 illustrated in Fig. 8 may thus comprise the at least one processor 450 and the at least one memory 460, both in communication with each other, with the subscription handler 454, the policy handler 456, the receiver 480 and the transmitter 470, and with other elements or units of the configuration server 4 or 70.
  • the at least one memory 460 may comprise volatile and/or non-volatile memory.
  • the at least one memory 460 may have a computer program 462 and data 466 stored therein.
  • the computer program 462 may be loaded in the at least one memory 460 from a computer program product 490, such as any non-transitory computer readable medium, in which the computer program is stored.
  • the at least one processor 450 may be configured to carry out the functions of the subscription handler 454 and the policy handler 456.
  • the configuration server 4 or 70 may comprise, as shown in Fig. 13 , a policy handler 456 configured to receive, from a policy server 1 or 10 via receiver 480, configuration data 71 or 72 to obtain a policy to be applied at the HCPE to trigger traffic distribution at the HCPE, and configured to install, to the HCPE via transmitter 470, the obtained policy to be applied at the HCPE to trigger traffic distribution at the HCPE.
  • the obtained policy may be installed by the policy handler 456 to trigger uplink traffic distribution at the HCPE.
  • the configuration data 71 may comprise subscription data, as illustrated in Fig. 5a , to be used by the configuration server to obtain the policy to be applied at the HCPE and associated with the subscription data at a data repository; or the configuration data 72 may directly comprise the policy to be applied at the HCPE. So that the policy is directly obtained from the policy server.
  • the configuration server 4 or 70 may further comprise, as shown in Fig. 13 , a subscription handler 454 configured to obtain, by using the received subscription data 71 and from a data repository, the policy to be applied at the HCPE and associated with the subscription data at the data repository; whereas, when the policy 72 to be applied at the HCPE is received from the policy server, the policy handler 456 is configured to directly obtain the policy to be applied at the HCPE.
  • the policy handler 456 may further be configured to install, to the HCPE 3 or 30 via the transmitter 470, a further policy to be applied at the HCPE.
  • This further policy may be installed to trigger downlink traffic distribution at the HCPE, or to update traffic distribution at the HCPE.
  • the invention may also be practised by one or more computer programs, loadable into an internal memory of one or more computers with one or more processors.
  • the one or more computer programs comprise instructions executable by the one or more processors to carry out the above methods.
  • the computer programs may be recorded in carriers readable in a computer.
  • Embodiment 1 A method of controlling policies for simultaneous accesses to a core network through a fixed network and a mobile network for a hybrid customer premises equipment (HCPE), the method comprising the steps of:
  • Embodiment 2 The method of embodiment 1, wherein sending the subscription data to the configuration server comprises sending the first policy to be applied at the HCPE.
  • Embodiment 3 The method of any one of embodiments 1 or 2, wherein the subscription data are sent to the configuration server with a SOAP notification.
  • Embodiment 4 The method of any one of embodiments 1 to 3, wherein the first policy is installed to the HCPE with a configuration message in accordance with TR-069 or CPE WAN Management Protocol (CWMP).
  • CWMP CPE WAN Management Protocol
  • Embodiment 5 The method of any one of embodiments 1 to 4, further comprising sending, from the policy server to the mobile network gateway, a third policy with redirection information indicating HCPE traffic redirection towards the HAG, and wherein the traffic addressing the core network is received at the mobile network gateway and redirected to the HAG.
  • Embodiment 6 The method of any one of embodiments 1 to 5, wherein the second policy is installed to trigger downlink traffic distribution at the HAG.
  • Embodiment 7 The method of any one of embodiments 1 to 6, wherein the first policy is installed to trigger uplink traffic distribution at the HCPE.
  • Embodiment 8 The method of any one of embodiments 1 to 7, further comprising: obtaining, by the configuration server, a fourth policy to be applied at the HCPE, and installing, from the configuration server, the fourth policy to the HCPE, wherein the fourth policy is installed to trigger downlink traffic distribution at the HCPE.
  • Embodiment 9 A policy server for controlling policies for simultaneous accesses by a hybrid customer premises equipment (HCPE) to a core network through a fixed network and a mobile network, the policy server comprising:
  • Embodiment 10 The policy server of embodiment 9, wherein the transmitter is configured to send the subscription data along with a second policy to be applied at the HCPE.
  • Embodiment 11 The policy server of any one of embodiments 9 or 10, wherein the transmitter is configured to send the subscription data to the configuration server with a SOAP notification.
  • Embodiment 12 The policy server of any one of embodiments 9 to 11, wherein the transmitter is configured to send, to the mobile network gateway, a third policy with redirection information indicating HCPE traffic redirection towards the HAG.
  • Embodiment 13 A hybrid customer premises equipment (HCPE) for simultaneous accesses to a core network through a fixed network and a mobile network, the HCPE comprising:
  • a configuration server e.g. ACS, RDM for controlling policies for simultaneous accesses to a core network through a fixed network and a mobile network for a hybrid customer premises equipment (HCPE), the configuration server comprising:
  • Embodiment 15 The configuration server of embodiment 14, wherein the receiver is configured to receive, from the policy server, the policy to be applied at the HCPE along with the subscription data.
  • Embodiment 16 The configuration server of embodiment 14, wherein the receiver is configured to obtain the policy to be applied at the HCPE from a data repository accessible to the configuration server.
  • Embodiment 17 The configuration server of any one of embodiments 14 to 16, wherein the receiver is configured to receive the subscription data with a SOAP notification.
  • Embodiment 18 The configuration server of any one of embodiments 14 to 17, wherein the transmitter is configured to send the policy to be applied at the HCPE with a configuration message in accordance with TR-069 or CPE WAN Management Protocol (CWMP).
  • CWMP CPE WAN Management Protocol
  • Embodiment 19 A computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of embodiments 1 to 8.
  • Embodiment 20 A computer program product comprising the computer program of embodiment 19.

Landscapes

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

Claims (16)

  1. Procédé de commande de politiques pour des accès à un réseau central (60), par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (50), pour un équipement de local de client hybride, HCPE, (3, 30), le procédé étant effectué par le HCPE (3, 30) et comprenant :
    l'établissement (S-110) d'une session de communication, par le HCPE avec une passerelle de réseau (5, 6), par l'intermédiaire d'au moins l'un du réseau fixe (40) et du réseau mobile (50) ;
    la réception (S-140), en provenance d'un serveur de configuration, et l'exécution (S-140), au HCPE, d'une politique à appliquer au HCPE pour déclencher une distribution de trafic au HCPE ; et
    la transmission (S-150), à une passerelle d'accès hybride, HAG, (2, 20), d'un trafic adressant le réseau central (60) sur la base de la politique reçue.
  2. Procédé de commande de politiques pour des accès à un réseau central (60), par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (50), pour un équipement de local de client hybride, HCPE, (3, 30), le procédé étant effectué par un serveur de politiques (1, 10) et comprenant :
    la réception (S-110), en provenance d'une passerelle de réseau (5, 6), d'informations relatives à une session de communication établie par le HCPE par l'intermédiaire d'au moins l'un du réseau fixe (40) et du réseau mobile (50) ;
    la transmission (S-120), à destination d'un serveur de configuration (4, 70), de données d'abonnement (71, 72) pour le HCPE, les données d'abonnement étant associées à une première politique à appliquer au HCPE pour déclencher une distribution de trafic au HCPE ;
    l'établissement (S-160) d'une session de protocole (3GPP Gx), entre le serveur de politiques et une passerelle d'accès hybride, HAG, (2, 20), pour le HCPE ; et
    l'installation (S-160), à la HAG, d'une deuxième politique à appliquer à la HAG pour déclencher une distribution de trafic à la HAG.
  3. Procédé de commande de politiques pour des accès à un réseau central (60), par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (50), pour un équipement de local de client hybride, HCPE, (3, 30), le procédé étant effectué par un serveur de configuration (4, 70) et comprenant :
    la réception (S-120), en provenance d'un serveur de politiques (1, 10), de données d'abonnement (71, 72) pour le HCPE, les données d'abonnement étant associées à une politique à appliquer au HCPE pour déclencher une distribution de trafic au HCPE ;
    l'obtention (S-130), au serveur de configuration, de la politique associée aux données d'abonnement et à appliquer au HCPE ; et
    l'installation (S-140) de la politique, du serveur de configuration au HCPE, pour déclencher une distribution de trafic au HCPE.
  4. Equipement de local de client hybride, HCPE, (3, 30) pour des accès à un réseau central (60) par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (50), le HCPE comprenant :
    au moins un processeur (320) ; et
    au moins une mémoire (310) qui mémorise des instructions exécutables par processeur (314), dans lequel l'au moins un processeur est en interface avec l'au moins une mémoire pour exécuter les instructions exécutables par processeur, de telle manière que ledit HCPE soit utilisable pour effectuer :
    l'établissement d'une session de communication, par le HCPE avec une passerelle de réseau (5, 6) par le biais d'un émetteur (340) et d'un récepteur (330), par l'intermédiaire d'au moins l'un du réseau fixe (40) et du réseau mobile (50) ;
    la réception, en provenance d'un serveur de configuration (4, 70) par le biais d'un récepteur (330), d'une politique à appliquer au HCPE pour déclencher une distribution de trafic ;
    l'exécution, avec un processeur (320), de la politique à appliquer au HCPE ; et
    la transmission, à une passerelle d'accès hybride, HAG, (2, 20) par le biais de l'émetteur (340), d'un trafic adressant le réseau central (60) sur la base de la politique reçue.
  5. HCPE selon la revendication 4, dans lequel la politique reçue est exécutée pour déclencher une distribution de trafic de liaison montante au HCPE.
  6. HCPE selon l'une quelconque des revendications 4 et 5, utilisable en outre pour effectuer :
    la réception, en provenance du serveur de communication (4, 70) par le biais du récepteur (330), d'une autre politique à appliquer au HCPE ; et
    l'exécution, avec le processeur (320), de l'autre politique pour déclencher une distribution de trafic de liaison descendante au HCPE.
  7. Serveur de politiques (1, 10) pour commander des politiques pour des accès par un équipement de local de client hybride, HCPE, (3, 30) à un réseau central (60), par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (50), le serveur de politiques comprenant :
    au moins un processeur (150) ; et
    au moins une mémoire (160) qui mémorise des instructions exécutables par processeur (162), dans lequel l'au moins un processeur est en interface avec l'au moins une mémoire pour exécuter les instructions exécutables par processeur, de telle manière que ledit serveur de politiques soit utilisable pour effectuer :
    la réception, en provenance d'une passerelle de réseau (5, 6) par le biais d'un récepteur (180), d'informations relatives à une session de communication établie par le HCPE par l'intermédiaire d'au moins l'un du réseau fixe (40) et du réseau mobile (50) ;
    la transmission, à destination d'un serveur de configuration (4, 70) par le biais d'un émetteur (170), de données d'abonnement (71, 72) pour le HCPE, les données d'abonnement étant associées à une première politique à appliquer au HCPE pour déclencher une distribution de trafic au HCPE ;
    l'établissement, par un processeur (150) par le biais de l'émetteur (170) et du récepteur (180), d'une session de protocole (3GPP Gx) avec une passerelle d'accès hybride, HAG, (2, 20), pour le HCPE ; et
    l'installation, à la HAG (2, 20) par le biais de l'émetteur (170), d'une deuxième politique à appliquer à la HAG pour déclencher une distribution de trafic à la HAG.
  8. Serveur de politiques selon la revendication 7, utilisable en outre pour transmettre, à destination du serveur de configuration (4, 70) par le biais de l'émetteur (170), la première politique (72) associée aux données d'abonnement et à appliquer au HCPE.
  9. Serveur de politiques selon la revendication 8, dans lequel la première politique est générée par le processeur (150) pour déclencher une distribution de trafic de liaison montante au HCPE.
  10. Serveur de politiques selon l'une quelconque des revendications 7 à 9, dans lequel la deuxième politique est installée pour déclencher une distribution de trafic de liaison descendante à la HAG.
  11. Serveur de politiques selon l'une quelconque des revendications 7 à 10, utilisable en outre pour effectuer l'installation, à la passerelle de réseau (5, 6) par le biais de l'émetteur (170), d'une troisième politique avec des informations de redirection indiquant une redirection de trafic HCPE vers la HAG, et de telle manière que le trafic adressant le réseau central et reçu à la passerelle de réseau soit redirigé vers la HAG.
  12. Serveur de configuration (4, 70) pour commander des politiques pour des accès à un réseau central (60), par l'intermédiaire d'un réseau fixe (40) et d'un réseau mobile (5) pour un équipement de local de client hybride, HCPE, (3, 30), le serveur de configuration comprenant :
    au moins un processeur (450) ; et
    au moins une mémoire (460) qui mémorise des instructions exécutables par processeur (462), dans lequel l'au moins un processeur est en interface avec l'au moins une mémoire pour exécuter les instructions exécutables par processeur, de telle manière que ledit serveur de configuration soit utilisable pour effectuer :
    la réception, en provenance d'un serveur de politiques (1, 10) par le biais d'un récepteur (480), de données d'abonnement (71, 72) pour le HCPE, les données d'abonnement étant associées à une politique à appliquer au HCPE pour déclencher une distribution de trafic au HCPE ;
    l'obtention, par un processeur (450), de la politique associée aux données d'abonnement et à appliquer au HCPE ; et
    l'installation, au HCPE par le biais d'un émetteur (470), de la politique obtenue à appliquer au HCPE pour déclencher une distribution de trafic au HCPE.
  13. Serveur de configuration selon la revendication 12, utilisable en outre pour effectuer :
    la réception, en provenance du serveur de politiques par le biais du récepteur (480), de la politique associée aux données d'abonnement (72) et à appliquer au HCPE ; ou
    l'utilisation des données d'abonnement (71) pour obtenir, par le processeur (450) à partir du répertoire de données, la politique à appliquer au HCPE et associée aux données d'abonnement au répertoire de données.
  14. Serveur de configuration selon l'une quelconque des revendications 12 et 13, dans lequel la politique obtenue est installée pour déclencher une distribution de trafic de liaison montante au HCPE.
  15. Serveur de configuration selon l'une quelconque des revendications 12 à 14, utilisable en outre pour installer, au HCPE par le biais de l'émetteur (470), une autre politique à appliquer au HCPE pour déclencher une distribution de trafic de liaison descendante au HCPE.
  16. Programme informatique (314, 162, 462), comprenant des instructions qui, lorsqu'elles sont exécutées sur au moins un processeur (320, 150, 450), amènent l'au moins un processeur à effectuer le procédé selon l'une quelconque des revendications 1 à 3.
EP16718641.0A 2015-04-20 2016-04-20 Commande de politique basée sur un réseau pour des accès hybrides Active EP3286879B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562150001P 2015-04-20 2015-04-20
PCT/EP2016/058790 WO2016170006A1 (fr) 2015-04-20 2016-04-20 Commande de politique basée sur un réseau pour des accès hybrides

Publications (2)

Publication Number Publication Date
EP3286879A1 EP3286879A1 (fr) 2018-02-28
EP3286879B1 true EP3286879B1 (fr) 2018-11-21

Family

ID=57143753

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16718641.0A Active EP3286879B1 (fr) 2015-04-20 2016-04-20 Commande de politique basée sur un réseau pour des accès hybrides

Country Status (3)

Country Link
US (1) US20170118081A1 (fr)
EP (1) EP3286879B1 (fr)
WO (1) WO2016170006A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105657748B (zh) * 2016-03-16 2020-06-26 华为技术有限公司 基于隧道绑定的通信方法和网络设备
US11303560B2 (en) * 2017-09-15 2022-04-12 Nokia Technologies Oy HCPE-based intelligent path selection over a multipath network
CN109714376B (zh) 2017-10-26 2021-02-05 华为技术有限公司 一种固网报文的发送方法、装置及系统
US11240858B2 (en) * 2018-04-27 2022-02-01 Nokia Solutions And Networks Oy Traffic steering for stateless packets over multipath networks
US11943731B2 (en) 2018-09-14 2024-03-26 Telefonaktiebolaget Lm Ericsson (Publ) Registration of legacy fixed network residential gateway (FN-RG) to a 5G core network
US11075844B2 (en) * 2019-08-15 2021-07-27 Netsia, Inc. Apparatus and method for providing hybrid access coordination
US11477072B2 (en) * 2019-09-17 2022-10-18 OpenVault, LLC System and method for prescriptive diagnostics and optimization of client networks

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8638717B2 (en) * 2010-08-20 2014-01-28 Time Warner Cable Enterprises Llc System and method for maintaining a communication session
WO2013091705A1 (fr) * 2011-12-22 2013-06-27 Nokia Siemens Networks Oy Procédés et appareils pour établissement de session avec commande de politique entre réseaux mobiles et fixes
EP2728802B1 (fr) * 2012-11-02 2020-08-12 Deutsche Telekom AG Méthode et système pour le réseau et service hybride contrôlée
EP2959657A2 (fr) * 2013-02-25 2015-12-30 Interdigital Patent Holdings, Inc. Gestion des memoires tampon dans un reseau cellulaire

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
WO2016170006A1 (fr) 2016-10-27
US20170118081A1 (en) 2017-04-27
EP3286879A1 (fr) 2018-02-28

Similar Documents

Publication Publication Date Title
EP3286879B1 (fr) Commande de politique basée sur un réseau pour des accès hybrides
US11083033B2 (en) Small data usage enablement in 3GPP networks
US11412418B2 (en) Third party charging in a wireless network
US11690005B2 (en) Network slice for visited network
US20210075915A1 (en) Charging Policy Information for a Packet Data Unit Session in a Wireless Network
US11909907B2 (en) Charging policy information for a home session management function
JP7190031B2 (ja) 通信システムにおいてアプリケーションごとにポリシルールを実行するための方法およびデバイス
CN114008980A (zh) 用于非公共网络的收费控制
JP2018530193A (ja) ユーザ機器のためのモバイルコアネットワークサービスエクスポージャ
WO2015139724A1 (fr) Dispositif et procédé pour gérer des politiques et/ou des ressources utilisées pour configurer un réseau
WO2022021971A1 (fr) Procédé de communication, premier élément de réseau de commande de politique et système de communication
EP2909993B1 (fr) Procédé et système de traitement de traffic de réseau d'un abonné
KR101007736B1 (ko) 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
EP2887580A1 (fr) Procédé et système permettant de modifier des paramètres de configuration sur un équipement utilisateur et une configuration serveur-passerelle automatique
WO2022258642A1 (fr) Système et procédé pour établir une session pdu double couche

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170926

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
INTG Intention to grant announced

Effective date: 20180625

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1068837

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181215

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016007436

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20181121

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1068837

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190221

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190221

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190321

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190321

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190222

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016007436

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20190822

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190420

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190430

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20160420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016007436

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181121

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230425

Year of fee payment: 8

Ref country code: DE

Payment date: 20230427

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230427

Year of fee payment: 8