CHANGE OF RADIO ACCESS NETWORK IN A NETWORK SHARING ARCHITECTURE

Abstract

In network sharing deployments, a policy control rules server ignores the used radio access network, RAN, and cannot apply RAN-related policies. This specification provides for a system and method for notifying the policy control rules server of a shared RAN used to connect a UE with a serving core network. This method comprises: receiving, at a network node of a serving core network, a request for establishment or modification of a network connection between the UE and the serving core network through a shared RAN; transmitting, from the network node towards the policy control rules server, a serving core network identifier, a RAN identifier and, optionally, a RAN sharing indicator; determining at the policy control rules server that policies related to the RAN identifier exist; transmitting, from the policy control rules server towards a network device, an event trigger subscribing to notifications of a RAN change; and monitoring, at the network device, whether the RAN identifier changes to notify the policy control rules server of a new RAN identifier.

Claims

1. A method for notifying a policy control rules server, which handles policies related to a radio access network, RAN, of a shared RAN used to connect a user equipment, UE, with a serving core network, the method comprising: receiving, at a network node of a serving core network, a request for establishment or modification of a network connection between a UE and the serving core network through a shared RAN; transmitting, from the network node towards a policy control rules server handling policies related to the shared RAN, an identifier of the serving core network and an identifier of the RAN; determining at the policy control rules server that policies related to the identifier of the RAN exist; transmitting, from the policy control rules server towards a network device handling subscriptions to events, an event trigger subscribing to notifications of a RAN change; and monitoring, at the network device, whether the identifier of the RAN changes in order to notify the policy control rules server of a new identifier of the RAN.

2. The method of claim 1, wherein the identifier of the serving core network is a serving-PLMN-ID and the identifier of the RAN is a RAN-PLMN-ID.

3-4. (canceled)

5. The method of claim 1, wherein prior to transmitting the identifier of the serving core network and the identifier of the RAN, the method further comprises determining, at the network node, that the RAN is a shared network.

6. The method of claim 1, wherein the identifier of the serving core network and the identifier of the RAN are transmitted from the network node towards the policy control rules server through one or more gateway nodes.

7. (canceled)

8. The method of claim 1, wherein the network device implements a Policy and Charging Enforcement Function, PCEF, and resides in any one of a Packet Data Network Gateway, PGW, and a Gateway GPRS Support Node, GGSN.

9. The method of claim 6, wherein the network device resides in a gateway node, and the method further comprises transmitting, from the network device towards the network node, an indication requesting to be notified of a RAN change.

10. The method of claim 1, wherein the identifier of the serving core network and the identifier of the RAN are directly transmitted from the network node towards the policy control rules server via a direct interface.

11. (canceled)

12. The method of claim 1, wherein an indicator indicating a RAN sharing is transmitted and received along with the identifier of the serving core network and the identifier of the RAN.

13. A system for notifying a policy control rules server, which handles policies related to a radio access network, RAN, of a shared RAN used to connect a user equipment, UE, with a serving core network, the system comprising: a network node of a serving core network configured to: receive a request for establishment or modification of a network connection between a UE and the serving core network through a shared RAN; transmit, towards a policy control rules server handling policies related to the shared RAN, an identifier of the serving core network and an identifier of the RAN; a policy control rules server configured to: receive, from the network node of the serving core network, the identifier of the serving core network and the identifier of the RAN; determine that policies related to the identifier of the RAN exist; transmit, towards a network device handling subscriptions to events, an event trigger subscribing to notifications of a RAN change; and a network device configured to: receive, from the policy control rules server, the event trigger subscribing to notifications of a RAN change; and monitor whether the identifier of the RAN changes in order to notify the policy control rules server of a new identifier of the RAN.

14. (canceled)

15. The system of claim 13, wherein the policy control rules server is a server implementing a Policy and Charging Rules Function, PCRF.

16. The system of claim 13, wherein the network node is any one of a Mobility Management Entity, MME, a Serving GPRS Support Node supporting a so-called Gn/Gp interface, hereinafter SGSN, a Serving GPRS Support Node supporting a so-called S4 interface, hereinafter S4-SGSN, a Serving Network Gateway, SGW, a Packet Data Network Gateway, PGW, and a Gateway GPRS Support Node, GGSN.

17. The system of claim 13, wherein the network node of the serving core network is configured to determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network and the identifier of the RAN.

18. The system of claim 13, further comprising one or more gateway nodes configured to receive, from the network node, the identifier of the serving core network and the identifier of the RAN and transmit, towards the policy control rules server, the identifier of the serving core network and the identifier of the RAN.

19. The system of claim 18, wherein the one or more gateway nodes comprises any ones of a Serving Network Gateway, SGW, a Packet Data Network Gateway, PGW, and a Gateway GPRS Support Node, GGSN.

20. The system of claim 16, wherein the network device implements a Policy and Charging Enforcement Function, PCEF and resides in any one of the PGW and the GGSN.

21. The system of claim 18, wherein the network device resides in a gateway node and is configured to transmit, towards the network node, an indication requesting to be notified of a RAN change.

22. (canceled)

23. The system of claim 13, wherein the network device resides in the network node.

24. (canceled)

25. A network node of a serving core network for notifying a policy control rules server, which handles policies related to a radio access network, RAN, of a shared RAN used to connect a user equipment, UE, with the serving core network, the network node comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the network node is operative to: receive a request for establishment or modification of a network connection between a UE and a serving core network through a shared RAN; and transmit, towards a policy control rules server, an identifier of the serving core network and an identifier of the RAN.

26. The network node of claim 25, further operative to: receive, from the policy control rules server, an event trigger subscribing to notifications of a RAN change; and monitor whether the identifier of the RAN changes in order to notify the policy control rules server of a new identifier of the RAN.

27. The network node of claim 25, further operative to: determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network and the identifier of the RAN.

28. (canceled)

29. The network node of claim 25, further operative to: receive, from a gateway node, an indication requesting to be notified of a RAN change; and monitor whether the identifier of the RAN changes in order to notify the gateway node of a new identifier of the RAN.

30. The network node of claim 25, wherein an indicator indicating a RAN sharing is transmitted and received along with the identifier of the serving core network and the identifier of the RAN.

31. A policy control rules server handling policies related to a radio access network, RAN, the RAN being used to connect a user equipment, UE, with a serving core network, the policy control rules server comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the policy control rules server is operative to: receive, from a network node of a serving core network, an identifier of the serving core network and an identifier of the RAN; determine that policies related to the identifier of the RAN exist; and transmit, towards a network device handling subscriptions to events, an event trigger subscribing to notifications of a RAN change.

32. The policy control rules server of claim 31, wherein the network device resides in at least one of the network node of the serving core network and a gateway node.

33. The policy control rules server of claim 31, wherein an indicator indicating a RAN sharing is received along with the identifier of the serving core network and the identifier of the RAN.

34-35. (canceled)

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The features, objects and advantages of the invention will become apparent by reading this description in conjunction with the accompanying drawings, in which:

[0059] FIG. 1 basically represents the functional elements of a PCC architecture.

[0060] FIG. 2 shows a network sharing architecture wherein more than one core network share a radio access network.

[0061] FIG. 3 shows an exemplary 3GPP EPS Architecture with LTE as RAN.

[0062] FIG. 4 shows a proprietary architecture with a direct interface Sx between a PCRF and network nodes of a serving core network.

[0063] FIG. 5 shows an exemplary network sharing, wherein two PLMNs with CN and RAN overlap and, in the overlapping area, share the RAN of a third operator.

[0064] FIG. 6 shows a component structure of a network node of a serving core network in accordance with an embodiment.

[0065] FIG. 7 shows a component structure of a network device in accordance with an embodiment.

[0066] FIG. 8 shows a component structure of a policy control rules server in accordance with an embodiment.

[0067] FIG. 9 shows a component structure of a gateway node in accordance with an embodiment.

[0068] FIG. 10 illustrates an exemplary sequence of actions carried out in an EPS deployment with E-UTRAN as radio network to notify a PCRF of a shared RAN, in accordance with an embodiment.

[0069] FIG. 11 illustrates an exemplary sequence of actions carried out in an EPS deployment with E-UTRAN as radio network to notify a PCRF of a shared RAN, in accordance with another embodiment aligned with the proprietary architecture shown in FIG. 4.

[0070] FIG. 12 shows a basic component structure of a network node of a serving core network in accordance with another embodiment.

[0071] FIG. 13 shows a basic component structure of a network device in accordance with another embodiment.

[0072] FIG. 14 shows a basic component structure of a policy control rules server in accordance with another embodiment.

[0073] FIG. 15 illustrates a method for notifying a policy control rules server of a shared RAN used to connect a UE with a serving core network.

[0074] FIG. 16 shows a basic component structure of a gateway node in accordance with another embodiment.

[0075] FIG. 17 schematically shows an exemplary identifier of a serving core network.

[0076] FIG. 18 illustrates complementary steps in accordance with an embodiment of a method for notifying a policy control rules server of a shared RAN used to connect a UE with a serving core network.

DETAILED DESCRIPTION

[0077] The following describes currently preferred embodiments of enhanced network node, network device and policy control rules server as well as a method for network sharing.

[0078] In particular, the policy control rules server 1a may be a network element arranged for carrying out the functionality of a PCRF 1, i.e. a PCRF server, in accordance with conventional PCC standards; the network device may be a network element arranged for carrying out the functionality of a PCEF 2, i.e. a PCEF device, in accordance with conventional PCC standards; and the network node may be a network element arranged for carrying out the functionality of at least one of an MME, an SGSN and an S4-SGSN in accordance with conventional EPS standards.

[0079] Prior to discussing embodiments and main actors of the invention, some aspects of the architectures involved are discussed to better orientate the reader.

[0080] Generally speaking, the PCC architecture is illustrated in FIG. 1. A central entity of the PCC architecture is the PCRF 1 in communication with a Subscription Profile Repository (SPR) 3 via an Sp reference point; in communication with a Resource Admission Control Function (RACF) 10 via an Np reference point; in communication with an Application Function (AF) 5 via an Rx reference point; in communication with a User Data Repository (UDR) 8 via a Ud reference point; in communication with an Online Charging System (OCS) 7 via an Sy reference point; in communication with an Application Function (AF) 5 via an Rx reference point; in communication with a Bearer Binding and Event Reporting Function (BBERF) 9 via a Gxx reference point; in communication with a Traffic Steering Support Function (TSSF) 11 via an St reference point; in communication with a Traffic Detection Function (TDF) 4 via an Sd reference point; in communication with a PCEF 2, which may reside in Gateway 22, via a Gx reference point. In addition, the TDF 4 is in communication with an Offline Charging System (OFCS) 6 via a Gzn reference point and is in communication with the OCS 7 via a Gyn reference point. Also in addition, the PCEF 2 is in communication with an OFCS 6 via a Gz reference point and is in communication with the OCS 7 via a Gy reference point.

[0081] FIG. 2 illustrates an exemplary network sharing scenario wherein three different CNs, i.e. CN 30 of operator A, CN 35 of operator B and CN 40 of operator C share a same RAN 45 of operator X.

[0082] Particularly in respect of FIG. 2, 3GPP TR 23.707 studies and evaluates architectural enhancements required to support dedicated core networks within the scope of an ongoing Rel-13 work item called DECOR. This feature enables an operator to deploy multiple core networks within a PLMN, wherein each core network is dedicated for a specific type of subscribers, devices or customers and with different characteristics, such as machine type devices, Mobile Virtual Network Operator (MVNO), data usage, specific enterprise, etc.

[0083] These dedicated core networks (DECOR) may be used by an operator in combination with network sharing. Where the MOCN architecture, commented above for network sharing, applies along with DECOR, each operator may deploy one or more dedicated core networks sharing a same RAN network owned by the same operator or another. For example, the FIG. 2 may be interpreted as if the CN 30 of operator A and the CN 35 of operator B respectively correspond to a first dedicated CN network of operator D and a second dedicated CN network of operator D.

[0084] Further examples of dedicated core networks along with network sharing, where the present invention is applicable, are Network Slicing and Cellular Internet of Things (CIoT).

[0085] Network slicing is an evolution of the concept of dedicated core networks, from a business perspective, that also introduces the concepts of network function virtualization (NFV), software defined networks (SDN) and network management (orchestration). Network slicing may be regarded as a logical network serving a defined business purpose or customer, consisting of all required network resources configured together. It is created, changed and removed by management functions. In this context, network resources may be any physical or virtual, dedicated or shared network resource.

[0086] The CIoT is a specific case of dedicated networks and is disclosed in 3GPP TR 23.270 v1.2.0. An operator offering CIoT can have separate core networks for Mobile Broadband (MBB) and CIoT that can be identified by a same or different PLMN Identifier. When network sharing applies, the radio network can be identified by a PLMN Identifier that is different than the PLMN Identifiers representing the slices and/or dedicated core networks.

[0087] FIG. 3 shows an exemplary 3GPP EPS Architecture with LTE as RAN, for which embodiments of the invention are further discussed. As illustrated in FIG. 3, a UE 12 connects through E-UTRAN 18 with the packet core network. Other possible accesses to the packet core network may be UTRAN 20 or GERAN 21. The packet core network may comprise an MME 13, an SGSN 14, or both. The MME is connected with E-UTRAN via interface S1-MME, with the SGSN via interface S3, with the HSS 15 via interface S6a, and with the SGW 16 via interface S11. The SGW 16 is also connected with the SGSN via interface S4 (i.e. the illustrated SGSN is in fact an S4-SGSN), with UTRAN via interface S12, and with a PGW 17 via interface S5. The PGW is connected with a PCRF 1 via interface Gx, and with Operator's IP services 19 via interface SGi. The PCRF is also connected with the Operator's IP services 19 via interface Rx.

[0088] FIG. 4 shows a proprietary architecture with a direct interface Sx between a PCRF and network nodes of a serving core network. As illustrated in FIG. 4, any one of MME 13, SGSN or S-GSN 14, individually or co-located, are connected with a GGSN 23 via interface Gn, with a SGW 16 via respective interfaces S11 or S4, and with a PCRF 1 via a direct interface Sx. The GGSN 23 is connected with the PCRF 1 via interface Gx, the SGW 16 is connected with the PGW 17 via interface S5, and the PGW 17 is connected with the PCRF 1 via interface Gx.

[0089] In this respect, particular embodiments are discussed throughout this specification depending on whether communications between the MME/SGSN and the PCRF are directly transmitted over the Sx interface or through the gateways SGW and PGW, or GGSN.

[0090] Generally speaking, FIG. 15 illustrates the overall method for notifying a policy control rules server 1a of a shared RAN used to connect a UE with a serving core network. The policy control rules server handles policies related to different RANs and, in particular, one or more policies related to the shared RAN. In an embodiment, the policy control rules server 1a may be a PCRF server 1 of the PCC architecture.

[0091] In this method, at a network node 60 of the serving core network, there is a step S-300 of receiving a request for establishment or modification of a network connection, between the UE and the serving core network, through a shared RAN, and there is a step S-320 of transmitting, from the network node 60 towards the policy control rules server 1a, an identifier of the serving core network, an identifier of the RAN and, optionally, an indicator indicating a RAN sharing.

[0092] Upon receipt of the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing during a step S-330, the method comprises, at the policy control rules server 1a, a step S-340 of determining that one or more policies related to the identifier of the RAN exist, and a step S-350 of transmitting, towards a network device 2a handling subscriptions to events, an event trigger subscribing to notifications of a RAN change. In this respect, the event trigger is submitted during establishment of the network connection and may not be submitted during modification of the network connection, if the modification does not imply a different RAN.

[0093] Upon receipt of the event trigger subscribing to notifications of a RAN change during a step S-360, the method includes at the network device 2a a step S-370 of monitoring whether the identifier of the RAN changes in order to notify the policy control rules server 1a of a new identifier of the RAN.

[0094] In this method, an exemplary identifier of the serving core network may be a serving-PLMN-ID and an exemplary identifier of the RAN may be a RAN-PLMN-ID. In particular, the serving-PLMN-ID may follow the scheme illustrated in FIG. 17 and the RAN-PLMN-ID may follow such scheme as well.

[0095] In this method, the policy control rules server 1a may be a PCRF server 1 of the PCC architecture illustrated in FIG. 1, whereas the network node 60 may be any one of the MME 13, SGSN 14, S4-SGSN 14, SGW 16, PGW 17 and GGSN 23 entities illustrated in FIG. 3 and/or FIG. 4. In this respect, depending on which of these entities is the network node, the network device 2a may reside in said network node, or in another entity.

[0096] Participating in this method, there is provided a system for notifying a policy control rules server, which handles policies related to a radio access network, RAN, of a shared RAN 45 used to connect a UE 12 with a serving core network.

[0097] This system comprises the network node 60 configured to receive a request for establishment or modification of a network connection between a UE 12 and the serving core network through a shared RAN 45 and transmit, towards a policy control rules server 1a handling policies related to the shared RAN, an identifier of the serving core network, an identifier of the RAN and, optionally, an indicator indicating a RAN sharing.

[0098] This system also comprises a policy control rules server 1a configured to receive, from the network node 60 of the serving core network, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing, determine that policies related to the identifier of the RAN exist and transmit, towards a network device 2a handling subscriptions to events, an event trigger subscribing to notifications of a RAN change.

[0099] This system also comprises a network device 2a configured to receive, from the policy control rules server 1a, the event trigger subscribing to notifications of a RAN change and monitor whether the identifier of the RAN changes in order to notify the policy control rules server 1a of a new identifier of the RAN.

[0100] As for the above method, the policy control rules server 1a may be a PCRF server 1 of the PCC architecture illustrated in FIG. 1, whereas the network node 60 may be any one of the MME 13, SGSN or S4-SGSN 14, SGW 16, PGW 17 and GGSN 23 entities illustrated in FIG. 3 and/or FIG. 4. In this respect, depending on which of these entities is the network node, the network device 2a may reside in said network node, or in another entity.

[0101] As for the above method, an exemplary identifier of the serving core network may be a serving-PLMN-ID and an exemplary identifier of the RAN may be a RAN-PLMN-ID. In particular, the serving-PLMN-ID may follow the scheme illustrated in FIG. 17 and the RAN-PLMN-ID may follow such scheme as well.

[0102] The network node 60, the network device 2a and the policy control rules server 1a of this system are respectively illustrated in FIG. 6, FIG. 7 and FIG. 8, in accordance with an embodiment; and in FIG. 12, FIG. 13 and FIG. 14, in accordance with another embodiment.

[0103] In accordance with an embodiment, the network node 60 may comprise, as shown in FIG. 6, at least one processor 620, and at least one memory 600 that stores processor-executable instructions 604. In this network node, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the network node is operable to perform the actions disclosed in the following.

[0104] The network node 60 is thus operable to receive a request for establishment or modification of a network connection between a UE 12 and a serving core network through a shared RAN 45 and transmit, towards a policy control rules server 1a, an identifier of the serving core network, an identifier of the RAN and, optionally, an indicator indicating a RAN sharing.

[0105] In particular, a RAN handler 622 running in a processor 620 may handle the request received via receiver 630 for establishment or modification of the network connection between the UE 12 and the serving core network through the shared RAN 45, and may handle the transmission, via transmitter 640 towards a policy control rules server 1a, of the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0106] In particular, where the network device 2a resides in the network node 60, a monitoring handler 626 running in a processor 620 may handle the event trigger received from the policy control rules server 1a via receiver 630 and monitor whether the identifier of the RAN changes in order to notify the policy control rules server via the transmitter 640 of a new identifier of the RAN.

[0107] If required at all, the network node may be complemented with a data section 608 in memory to store any one of the indicator indicating the RAN sharing, the identifier of the serving core network and any identifier of the RAN.

[0108] The network node 60 illustrated in FIG. 6 may thus comprise the at least one processor 620 and the at least one memory 600, both in communication with each other, with the RAN handler 622, the monitoring handler 626, the receiver 630 and the transmitter 640, and with other elements or units of the network node 60. The at least one memory 600 may comprise volatile and/or non-volatile memory. In particular, the at least one memory 600 may have a computer program 604 and data 608 stored therein. The computer program 604 may be loaded in the at least one memory 600 from a computer program product 610, such as any non-transitory computer readable medium, in which the computer program is stored. The data 608 may comprise any one of the identifier of the serving core network, any identifier of the RAN and, optionally, the indicator indicating the RAN sharing. The at least one processor 620 may be configured to carry out the functions of the RAN handler 622 and the monitoring handler 626.

[0109] In accordance with another embodiment, the network node 60 may comprise, as shown in FIG. 12, a RAN handler module 622 configured to receive via a receiver 630 the request for establishment or modification of the network connection between the UE 12 and the serving core network through the shared RAN 45, and configured to transmit, via a transmitter 640 and towards the policy control rules server 1a, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0110] Where the network device 2a resides in the network node 60, the network node 60 may also comprise, as shown in FIG. 12, a monitoring handler module 626 configured to receive via the receiver 630 the event trigger from the policy control rules server 1a and monitor whether the identifier of the RAN changes in order to notify the policy control rules server 1a via the transmitter 640 of a new identifier of the RAN.

[0111] In accordance with an embodiment, the network device 2a may comprise, as shown in FIG. 7, at least one processor 770, and at least one memory 750 that stores processor-executable instructions 754. In this network device, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the network device is operable to perform the actions disclosed in the following.

[0112] The network device 2a is thus operable to receive, from the policy control rules server 1a, the event trigger subscribing to notifications of a RAN change and monitor whether the identifier of the RAN changes in order to notify the policy control rules server of a new identifier of the RAN.

[0113] In particular, a monitoring handler 777 running in a processor 770 may handle the event trigger received at receiver 790 and may monitor whether the identifier of the RAN changes; and a notifications handler 773 running in a processor 770 may notify the policy control rules server, via transmitter 780, of a new identifier of the RAN when there is a change of RAN.

[0114] The network device 2a may be complemented with a data section 758 in memory to store the event-trigger and any identifier of the RAN.

[0115] The network device 2a illustrated in FIG. 7 may thus comprise the at least one processor 770 and the at least one memory 750, both in communication with each other, with the notifications handler 773, the monitoring handler 777, the receiver 790 and the transmitter 780, and with other elements or units of the network device 2a. The at least one memory 750 may comprise volatile and/or non-volatile memory. In particular, the at least one memory 750 may have a computer program 754 and data 758 stored therein. The computer program 754 may be loaded in the at least one memory 750 from a computer program product 760, such as any non-transitory computer readable medium, in which the computer program is stored. The data 758 may comprise the event-trigger and any identifier of the RAN. The at least one processor 770 may be configured to carry out the functions of the monitoring handler 777 and the notifications handler 773.

[0116] In the case where the network device 2a resides in the network node 60 illustrated in FIG. 6, the functionality carried out by the at least one processor 770, the at least one memory 750, the receiver 790 and the transmitter 780 of the network device 2a may be carried out by the at least one processor 620, the at least one memory 600, the receiver 630 and the transmitter 640 of the network node 60. Likewise, the functionality carried out by the monitoring handler 777 and the notifications handler 773 running in the processor 770 of the network device 2a may be carried out by the monitoring handler 626 running in the processor 620 of the network node 60.

[0117] In accordance with another embodiment, the network device 2a may comprise, as shown in FIG. 13, a monitoring handler module 777 configured to handle the event trigger received via receiver 790 and monitor whether the identifier of the RAN changes, and a notifications handler module 773 configured to notify the policy control rules server 1a, via transmitter 780, of a new identifier of the RAN when there is a change of RAN.

[0118] In the case where the network device 2a resides in the network node 60 illustrated in FIG. 12, the functionality carried out by the receiver 790 and the transmitter 780 of the network device 2a may be carried out by the receiver 630 and the transmitter 640 of the network node 60. Likewise, the functionality carried out by the monitoring handler module 777 and the notifications handler module 773 of the network device 2a may be carried out by the monitoring handler module 626 of the network node 60. Alternatively, the functionality carried out by the monitoring handler module 777 may be carried out by the monitoring handler module 626 and the functionality carried out by the notifications handler module 773 may be carried out by a corresponding notifications handler module, not illustrated, included in the network node 60.

[0119] In accordance with an embodiment, the policy control rules server 1a may comprise, as shown in FIG. 8, at least one processor 820, and at least one memory 800 that stores processor-executable instructions 813. In this policy control rules server 1a, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the policy control rules server is operable to perform the actions disclosed in the following.

[0120] This policy control rules server 1a is thus operable to receive, from the network node 60 of the serving core network, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing, determine that one or more policies related to the identifier of the RAN exist and transmit, towards the network device 2a handling subscriptions to events, an event trigger subscribing to notifications of a RAN change.

[0121] In particular, a RAN handler 822 running in a processor 820 may handle the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing received via receiver 840; and a policies handler 828 running in a processor 820 may determine that policies related to the identifier of the RAN exist and may transmit, towards the network device 2a via transmitter 830, the event trigger subscribing to notifications of a RAN change.

[0122] The policy control rules server 1a may be complemented with a data section 816 in memory to store the indicator indicating the RAN sharing, the identifier of the serving core network and any identifier of the RAN.

[0123] The policy control rules server 1aillustrated in FIG. 8 may thus comprise the at least one processor 820 and the at least one memory 800, both in communication with each other, with the RAN handler 822, the policies handler 828, the receiver 840 and the transmitter 830, and with other elements or units of the policy control rules server 1a. The at least one memory 800 may comprise volatile and/or non-volatile memory. In particular, the at least one memory 800 may have a computer program 813 and data 816 stored therein. The computer program 813 may be loaded in the at least one memory 800 from a computer program product 810, such as any non-transitory computer readable medium, in which the computer program is stored. The data 816 may comprise the identifier of the serving core network, any identifier of the RAN and, optionally, the indicator indicating the RAN sharing. The at least one processor 820 may be configured to carry out the functions of the RAN handler 822 and the policies handler 828.

[0124] In accordance with another embodiment, the policy control rules server 1a may comprise, as shown in FIG. 14, a RAN handler module 822 configured to receive, via receiver 840, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing; and a policies handler module 828 configured to determine that policies related to the identifier of the RAN exist and transmit, towards the network device 2a via transmitter 830, the event trigger subscribing to notifications of a RAN change.

[0125] Back to the method discussed above with reference to FIG. 15, the method may further comprise a step of determining at the network node 60 that the RAN is a shared network, prior to transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0126] In an embodiment of the invention and when the network node 60 is any one of the MME 13, the SGSN 14 and the S4-SGSN 14, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing may be directly transmitted, from the network node 60 towards the policy control rules server 1a, via the direct interface Sx illustrated in FIG. 4. Also when the network node 60 is any one of the PGW 17 and GGSN 23, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing may be directly transmitted, from the network node 60 towards the policy control rules server 1a, via the direct interface Gx illustrated in FIG. 4.

[0127] In another embodiment, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing may be transmitted, from the network node 60 towards the policy control rules server 1a, through one or more gateway nodes, such as the Gateway 22 illustrated in FIG. 1.

[0128] In particular, the one or more gateways may comprise any one of the SGW 16, the PGW 17 and the GGSN 23. Still in this case and also in particular, the network device 2a may reside in the network node 60, i.e. the MME 13, the SGSN 14 and the S4-SGSN 14, or may reside in any one of the PGW 17 and the GGSN 23.

[0129] In this case, where the network device 2a resides in one of the PGW 17 and the GGSN 23, the method may further comprise a step of transmitting, from the network device 2a towards the network node 60, an indication requesting to be notified of a RAN change.

[0130] Moreover, where the network device 2a resides in one of the PGW 17 and the GGSN 23, the network device 2a may implement a PCEF 2 of the PCC architecture illustrated in FIG. 1.

[0131] At least some of these particular embodiments, discussed for the general method explained with reference to FIG. 15, are further discussed with reference to the exemplary embodiment of the method illustrated in FIG. 18.

[0132] In this embodiment illustrated in FIG. 18, at a network node 60 of the serving core network, i.e. the MME 13, the SGSN 14 or the S4-SGSN 14, there is a step S-400 of receiving a request for establishment or modification of a network connection, between the UE and the serving core network, through a shared RAN; there is a step S-410 of determining that the RAN is a shared network; and there is a step S-420 of transmitting, from the network node 60 towards the policy control rules server 1a via one or more gateways (such as gateway 22 in FIG. 1), an identifier of the serving core network, an identifier of the RAN and, optionally, an indicator indicating a RAN sharing.

[0133] The method at the one or more gateways, e.g. SGW 16 and PGW 17, or

[0134] GGSN 23, comprises a step S-430 of receiving the identifier of the serving core network, the identifier of the RAN (thus determining at the gateway that the RAN is shared) and, optionally, the indicator indicating the RAN sharing, and a step of transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing towards the policy control rules server 1a. The policy control rules server 1a may carry out steps S-330 to S-350 as in the general method illustrated in FIG. 15. And, where the gateway is any one of the PGW 17 and the GGSN 23, the method comprises a step S-450 of receiving, at the gateway node 17 or 23 from the policy control rules server 1a, an event trigger subscribing to notifications of a RAN change, and a step S-460 of transmitting, from the gateway node 17 or 23 towards the network node 13 or 14, an indication requesting to be notified of a RAN change.

[0135] Upon receipt of the indicator requesting to be notified of a RAN change, the method includes at the network node 13 or 14 a step S-470 of monitoring whether the identifier of the RAN changes in order to notify the gateway node 17 or 23 of a new identifier of the RAN.

[0136] In order to carry out these further embodiments of the method discussed above with reference to FIG. 15 and FIG. 18, corresponding embodiments for the system, the network node 60, the policy control rules server 1a, the network device 2a and, where applicable, the gateway 22 are discussed in the following.

[0137] In the embodiment illustrated in FIG. 6, the network node 60 of the serving core network may be operable to determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0138] In particular, the RAN handler 622 running in the processor 620 may determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0139] In another embodiment illustrated in FIG. 12, the RAN handler module 622 may be configured to determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0140] In an embodiment, the network node 60 of the serving core network shown in FIG. 6 may be operable to directly transmit, via the direct interface Sx illustrated in FIG. 4, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing to the policy control rules server 1a. In particular, the RAN handler 622 running in the processor 620 and illustrated in FIG. 6 may handle the direct transmission, via transmitter 640, of the identifier of the serving core network and the identifier of the RAN and, optionally, the indicator indicating the RAN sharing to the policy control rules server 1a.

[0141] In the embodiment of the network node 60 illustrated in FIG. 12, the RAN handler module 622 may be configured to directly transmit over the Sx interface, via a transmitter 640 and to the policy control rules server 1a, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0142] In another embodiment, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing may be transmitted, from the network node 60 towards the policy control rules server 1a, through one or more gateway nodes, such as the Gateway 22 illustrated in FIG. 1.

[0143] Where this is the case, and where the network device 2a resides in the gateway node 22, the network node 60 of the serving core network, in the embodiment shown in FIG. 6, may be operable to receive, from the gateway node 22, an indication requesting to be notified of a RAN change, and monitor whether the identifier of the RAN changes in order to notify the gateway node of a new identifier of the RAN.

[0144] In particular, the monitoring handler 626 running in the processor 620 and illustrated in FIG. 6 may handle the indication, received via receiver 630, requesting to be notified of a RAN change, monitor when the identifier of the RAN changes and, when there is a change, notify the gateway node via transmitter 640 of a new identifier of the RAN.

[0145] Still in this case, the system may further comprise one or more gateway nodes, e.g. gateway 22, interposed between the network node 60 and the policy control rules server 1a. Exemplary gateways may be e.g. SGW and PGW, or GGSN.

[0146] In accordance with an embodiment, the gateway node 22 may comprise, as shown in FIG. 9, at least one processor 970, and at least one memory 950 that stores processor-executable instructions 954. In this gateway node, the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby the gateway node is operable to perform the actions disclosed in the following.

[0147] The gateway node 22 is thus operable to receive, from a network node 60 or from another gateway, a request for establishment or modification of a network connection between a UE 12 and a serving core network through a shared RAN 45. This request comprises the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing, which were submitted from the network node 60 in its way to the policy control rules server 1a.

[0148] As receiving such information, the gateway node 22 is thus operable to determine that the RAN is a shared network, prior to transmitting the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0149] The gateway node 22 is also operable to transmit, towards a policy control rules server 1a, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0150] In particular, a RAN handler 973 running in a processor 970 may handle the request received via receiver 990 for establishment or modification of the network connection between the UE 12 and the serving core network through the shared RAN 45, may determine that the RAN is a shared network and may handle the transmission, via transmitter 980 towards a policy control rules server 1a, of the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0151] In particular, where the network device 2a resides in the gateway node 22, a monitoring handler 975 running in a processor 970 may handle the event trigger received from the policy control rules server 1a via receiver 990 and monitor whether the identifier of the RAN changes in order to notify the policy control rules server via the transmitter 980 of a new identifier of the RAN.

[0152] In an embodiment, in order to monitor whether the identifier of the RAN changes, this monitoring handler 975 may submit, via transmitter 980 to the network node 60, an indication requesting to be notified of a RAN change; may receive, from the network node 60 via receiver 990, a notification of a new identifier of the RAN; and may transmit, towards the policy control rules server 1a via transmitter 980, the notification of the new identifier of the RAN.

[0153] If required at all, the gateway node may be complemented with a data section 958 in memory to store any one of the identifier of the serving core network, any identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0154] The gateway node 22 illustrated in FIG. 9 may thus comprise the at least one processor 970 and the at least one memory 950, both in communication with each other, with the RAN handler 973, the monitoring handler 975, the receiver 990 and the transmitter 980, and with other elements or units of the gateway node 22. The at least one memory 950 may comprise volatile and/or non-volatile memory. In particular, the at least one memory 950 may have a computer program 954 and data 958 stored therein. The computer program 954 may be loaded in the at least one memory 950 from a computer program product 960, such as any non-transitory computer readable medium, in which the computer program is stored. The data 958 may comprise any one of the identifier of the serving core network, any identifier of the RAN and, optionally, the indicator indicating the RAN sharing. The at least one processor 970 may be configured to carry out the functions of the RAN handler 973 and the monitoring handler 975.

[0155] In accordance with another embodiment, the gateway node 22 may comprise, as shown in FIG. 16, a RAN handler module 973 configured to receive via a receiver 990 the request for establishment or modification of the network connection between the UE 12 and the serving core network through the shared RAN 45, the request including the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing. The RAN handler module 973 thus configured to determine that the RAN is a shared network, and configured to transmit, via a transmitter 980 towards the policy control rules server 1a, the identifier of the serving core network, the identifier of the RAN and, optionally, the indicator indicating the RAN sharing.

[0156] In particular, where the network device 2a resides in the gateway node 22 illustrated in FIG. 16, a monitoring handler module 975 may be configured to receive via the receiver 990 the event trigger from the policy control rules server 1a, and monitor whether the identifier of the RAN changes in order to notify the policy control rules server 1a via the transmitter 980 of a new identifier of the RAN.

[0157] In an embodiment, in order to monitor whether the identifier of the RAN changes, this monitoring handler module 975 may be configured to submit, via transmitter 980 to the network node 60, an indication requesting to be notified of a RAN change; receive, from the network node 60 via receiver 990, a notification of a new identifier of the RAN; and transmit, towards the policy control rules server 1a via transmitter 980, the notification of the new identifier of the RAN.

[0158] Some exemplary network procedures with at least some of the above embodiments are discussed in the following with reference to FIG. 10 and FIG. 11.

[0159] FIG. 10 exemplary illustrates how the solution works in an EPS deployment with E-UTRAN as RAN and having GTP between the MME 13 and the PGW 17. The MME is just an example and it could be any one of S4-SGSN, MME or Gn/Gp SGSN. Likewise, a GGSN 23 may follow a similar approach as for the PGW 17. The UE may camp on any one of 2G, 3G or LTE.

[0160] Step S-100 in FIG. 10 represents a sort of pre-condition: a network sharing applies when the UE requests establishment or modification of a PDN connection. The fact is that, unless otherwise specified, a similar procedure applies for establishment of a new connection as for modification of an existing connection.

[0161] During step S-110 the UE initiates a PDN connection establishment or modification, by submitting e.g. a create session request or a modify bearer request to the MME 13 through a shared RAN, as per current procedures. In particular, the PDN modification may occur when a UE with an active PDN connection moves to a different RAN. The MME is a network node of a serving core network selected by the UE or assigned by the network.

[0162] For the sake of simplicity, the create session request and modify bearer request are indistinctly referred to in FIG. 10 as create/modify session request.

[0163] During step S-115, the MME determines there is a RAN sharing and, during step S-120, transmits to a SGW 16 the create/modify session request including a network sharing indicator that indicates a RAN sharing, an identifier of the serving core network (abbreviated as SN) and an identifier of the RAN (abbreviated as RAN). The identifier of the serving core network, e.g. serving-PLMN-ID, identifies the PLMN where the MME is located. The identifier of the RAN, e.g. RAN-PLMN-ID, may be derived from location information provided by the RAN, or by a so-called Global eNB ID received during the Setup procedure over the S1 interface, or even by configuration.

[0164] The SGW 16 receives the create/modify session request with the network sharing indicator, the identifier of the serving core network and the identifier of the RAN and, aware of the RAN sharing, transmits to a PGW 17, during step S-125, the create/modify session request with the network sharing indicator, the identifier of the serving core network and the identifier of the RAN.

[0165] The PGW 17 receives the create/modify session request with the network sharing indicator, the identifier of the serving core network and the identifier of the RAN and, aware of the RAN sharing, transmits to a PCRF server 1, during step S-130, a Gx session establishment or modification request, i.e. Gx Session Create/Modify Request, including the network sharing indicator, the identifier of the serving core network and the identifier of the RAN.

[0166] The PCRF server 1 receives the network sharing indicator, the identifier of the serving core network and the identifier of the RAN, determines during step S-135 that one or more policies related to the identifier of the RAN exist and, in order to subscribe to notifications of a RAN change, transmits during step S-140 a Gx session response with a specific event trigger, e.g. RAN_PLMN_Change, for this purpose to a network device located in the PGW 17. In addition, and not illustrated in any drawing, the PCRF server 1 may submit PCC rules towards the PGW as well.

[0167] In particular, when the PCRF server 1 receives a Gx session modification, the PCRF server may determine between steps S-135 and S-140 that the event trigger had already been submitted during the correspondingly previous Gx session establishment and may skip submitting the same event trigger again.

[0168] The network device, which is in charge of handling subscriptions to events at the PGW 17, starts monitoring, during step S-145, if the RAN changes in order to notify the PCRF server of a new RAN identifier.

[0169] The PGW 17 transmits a corresponding session response to the SGW 16 during step S-150, the SGW transmits a corresponding session response to the MME 13 during step S-155, and the MME 13 transmits a corresponding session response to the UE 12, during step S-160, via the RAN network.

[0170] A similar procedure can be followed when the Sx interface shown in FIG. 4 is used between an MME/SGSN and the PCRF server 1.

[0171] Step S-200 in FIG. 11 represents a sort of pre-condition: a network sharing applies when the UE requests establishment or modification of a PDN connection. Unless otherwise specified, a similar procedure applies for establishment of a new connection as for modification of an existing connection.

[0172] During step S-210 the UE initiates a PDN connection establishment or modification, by submitting e.g. a create session request or a modify bearer request to the MME 13 through a shared RAN, as per current procedures. In particular, the PDN modification may occur when a UE with an active PDN connection moves to a different RAN. The MME is a network node of a serving core network selected by the UE or assigned by the network.

[0173] For the sake of simplicity, the create session request and modify bearer request are indistinctly referred to in FIG. 11 as create/modify session request or, simply, as session request.

[0174] During step S-215, the MME determines there is a RAN sharing and, during step S-220, transmits to a PCRF server 1 an Sx session establishment or modification request including a network sharing indicator that indicates a RAN sharing, an identifier of the serving core network (abbreviated as SN) and an identifier of the RAN (abbreviated as RAN). As for the procedure illustrated in FIG. 10, also in this procedure illustrated in FIG. 11, the identifier of the serving core network, e.g. serving-PLMN-ID, identifies the PLMN where the MME is located. The identifier of the RAN, e.g. RAN-PLMN-ID, may be derived from location information provided by the RAN, or by a so-called Global eNB ID received during the Setup procedure over the S1 interface, or even by configuration.

[0175] The PCRF server 1 receives the network sharing indicator, the identifier of the serving core network and the identifier of the RAN, determines during step S-225 that one or more policies related to the identifier of the RAN exist and, in order to subscribe to notifications of a RAN change, transmits during step S-230 an Sx session response (for the session establishment or for the session modification, as the case may be) with a specific event trigger, e.g. RAN_PLMN_Change, for this purpose to a network device located in the MME 13.

[0176] In particular, when the PCRF server 1 receives an Sx session modification, the PCRF server may determine between steps S-225 and S-230 that the event trigger had already been submitted during the correspondingly previous Sx session establishment and may skip submitting the same event trigger again.

[0177] The network device, which is in charge of handling subscriptions to events at the MME 13, starts monitoring, during step S-235, if the RAN changes in order to notify the PCRF server of a new RAN identifier.

[0178] Then, the MME 13 transmits to a SGW 16, during step S-240, the session request, i.e. the create session request or modify bearer request received from the UE, in accordance with existing procedures. The SGW 16 transmits to a PGW 17, during step S-245, the session request, i.e. the create session request or modify bearer request received from the MME, in accordance with existing procedures.

[0179] The PGW 17 transmits to a PCRF server 1, during step S-250, a Gx session establishment or modification request. For the sake of simplicity, illustrated as Gx Session Create/Modify Request, in accordance with existing procedures.

[0180] The PCRF server may behave in accordance with existing procedures and transmit during step S-255 a Gx session response, ack for the sake of simplicity, to the PGW 17. In addition, and not illustrated in any drawing, the PCRF server 1 may submit PCC rules towards the PGW as well.

[0181] The PGW 17 transmits a corresponding session response, ack, to the SGW 16 during step S-260, the SGW transmits a corresponding session response, ack, to the MME 13 during step S-265, and the MME 13 transmits a corresponding session response, not illustrated in any drawing, to the UE 12 via the RAN network.

[0182] 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. In particular, the computer programs may be recorded in carriers readable in a computer.

[0183] The invention is described above in connection with various embodiments that are intended to be illustrative and non-restrictive. It is expected that those of ordinary skill in this art may modify these embodiments. The scope of the invention is defined by the claims in conjunction with the description and drawings, and all modifications that fall within the scope of the claims are intended to be included therein.