User device connection policy

Abstract

A method for enabling detection of tethered services at a user equipment (UE) and application of tethering policies to such services. The method comprises: receiving subscription information from a subscriber data repository entity at a policy control entity, the subscription information comprising an indication of an action to be applied at the UE to services of a tethered device; transmitting a tethering policy from the policy control entity to the UE, the tethering policy comprising the received action to be applied to services of the tethered device; and applying the tethering policy to services of the tethered device at the UE. The policy control entity may be a PCF. The subscriber data repository entity may be a UDR. The tethering policy may comprise an indication to block tethered services, mark tethered services, or report information or events related to tethered services and tethered devices.

Description

Technical Field

[0001] The present invention generally relates to provisioning of policy rules in mobile networks, and more particularly, the present invention relates to provisioning of policy rules to user equipment. Background Art

[0002] Tethering refers to coupling a tethered device, such as a computer, with a tethering-enabling device, such as a mobile phone, that provides a so-called hotspot, enabling the tethered device to use the mobile connection and data plan services of the tethering-enabling device. The mobile phone is configured to act as a modem, providing a network connection to the tethered device. The coupling between the tethered device and the tethering-enabling device can be via a data cable, such as a USB cable or a proprietary cable, or through a wireless LAN (Wi-Fi), through Bluetooth, or a proprietary communication protocol, to name a few.

[0003] The use of mobile phones as modems for other devices to access the Internet has caused serious concern among telecommunications operators (also known as wireless operators, network operators or mobile network operators) for the use of access to their mobile networks in this way to provide Internet services to laptops, computers, tablets or third-party users without signing contracts or paying them fees.

[0004] Wireless operators are working to identify tethered traffic and apply specific policies to it, such as blocking unauthorized or inappropriate tethered traffic, applying specific quality of service or routing rules, charging it differently, etc. Today, this is possible using solutions implemented in the network gateway, for example, by using fingerprinting techniques to try to detect patterns that indicate the source of the traffic is not a mobile device to identify tethered traffic. Actions performed on tethered traffic are, for example: counting the number of tethered devices; blocking tethered traffic if the subscriber has not requested the service; blocking based on the number of tethered devices; applying a different tariff; changing the quality of service; reporting the detection of a tethered device or tethered traffic.

[0005] The concept of tethering can also be applied to other scenarios. For example, 5G-RG (5G Residential Gateway) is a special UE device that provides connectivity for fixed and mobile home devices. Devices connected to 5G-RG are tethered devices, and in this case, the network operator may want to provide specific services or apply specific policies to devices connected to 5G-RG.

[0006] The problematic aspect is that wireless operators have not come up with adequate solutions to fully identify tethered traffic. Especially as traffic encryption continues to grow and encrypted traffic cannot be inspected on the network side, no solution currently exists to fully detect and control tethered traffic. In addition, some users will jailbreak their mobile devices to avoid tethered detection on the network side. Summary of the invention

[0007] It is an object of the present invention to enable detection of tethered traffic and application of tethered policies to such traffic.

[0008] A first aspect of the present invention relates to a method performed by a user equipment (UE) for enforcing a tethering policy at the UE. The method comprises: receiving a tethering policy from a control plane (CP) entity of a mobile communication system, the tethering policy comprising an action applied to the traffic of a tethered device; and applying the tethering policy to the traffic of the tethered device. In an embodiment of the method, the tethering policy comprises an indication of blocking the traffic of the tethered device. In an embodiment of the method, the tethering policy comprises an indication of allowing only the traffic transmission of a maximum number of tethered devices connected at the same time. In an embodiment of the method, the tethering policy comprises an indication of marking the traffic of the tethered device with a specific value contained in a protocol header, the value being the same for all tethered devices or different for each tethered device. In an embodiment of the method, the tethering policy comprises an indication of reporting an event to a CP entity or another CP entity in response to detecting the traffic of the tethered device. In an embodiment of the method, the indication of reporting the event comprises an indication of reporting the number of tethered devices, the detection of a new tethered device, or the traffic volume of the tethered device. In an embodiment of the method, applying the tethering policy comprises transmitting a report to the CP entity or another CP entity, the report comprising the number of tethered devices, the detection of new tethered devices or the traffic volume of tethered devices. In an embodiment of the method, the tethering policy is received from the access and mobility management entity in a protocol data unit session response message or in a UE routing policy URSP. In an embodiment of the method, the tethering policy is received from the policy control entity in a UE routing policy (URSP).

[0009] A second aspect of the present invention relates to a method performed by a policy control entity for providing a tethering policy to a user equipment. The method comprises: receiving subscription information from a subscriber data repository entity of a mobile communication system, the subscription information comprising an indication of an action applied to a service of a tethered device at a UE; and transmitting a tethering policy to the UE, the tethering policy comprising the received action applied to the service of the tethered device. In an embodiment of the method, the tethering policy comprises an indication of blocking the service of the tethered device. In an embodiment of the method, the tethering policy comprises an indication of allowing only the service transmission of a maximum number of tethered devices connected at the same time. In an embodiment of the method, the tethering policy comprises an indication of marking the service of the tethered device with a specific value contained in a protocol header, the value being the same for all tethered devices or different for each tethered device. In an embodiment of the method, the tethering policy comprises an indication of reporting an event to a CP entity or another CP entity in response to detecting the service of the tethered device. In an embodiment of the method, the indication of reporting the event comprises an indication of reporting the number of tethered devices, the detection of a new tethered device, or the amount of service of the tethered device. In an embodiment of the method, the tethering policy is transmitted in a UE Routing Policy (URSP).

[0010] A third aspect of the present invention relates to a method performed by an access and mobility management entity for providing a tethering policy to a user equipment. The method comprises: receiving a tethering policy from a policy control entity of a mobile communication system, the tethering policy comprising an indication of an action applied to the traffic of a tethered device at a UE; and transmitting the tethering policy to the UE. In an embodiment of the method, the tethering policy comprises an indication of blocking the traffic of the tethered device. In an embodiment of the method, the tethering policy comprises an indication of allowing only the traffic transmission of a maximum number of tethered devices connected at the same time. In an embodiment of the method, the tethering policy comprises an indication of marking the traffic of the tethered device with a specific value contained in a protocol header, the value being the same for all tethered devices or different for each tethered device. In an embodiment of the method, the tethering policy comprises an indication of reporting an event to a CP entity or another CP entity in response to detecting the traffic of the tethered device. In an embodiment of the method, the indication of reporting the event comprises an indication of reporting the number of tethered devices, the detection of a new tethered device, or the traffic volume of the tethered device. In an embodiment of the method, the tethering policy is transmitted in a protocol data unit session response message or in a UE routing policy (URSP).

[0011] Other aspects of the invention relate to mobile network nodes, in particular user equipment and control plane nodes, each node being configured to perform a corresponding method as described herein. In some embodiments of these aspects, the control plane node may refer to an access and mobility management function (AMF) or a policy control function (PCF). Other aspects of the invention relate to corresponding computer programs or computer program products.

[0012] Advantageously, the solution disclosed herein enables detection of tethered traffic at the UE in a simple and efficient manner, which would be impossible to detect at the network side, for example, when the traffic is encrypted.

[0013] Further advantageously, the solution disclosed herein enables controlling tethering traffic at the UE and applying tethering policies at the UE that would not be possible to apply at the network side.

[0014] Further advantageously, the solution disclosed herein enables marking of tethered traffic at the UE and applying tethering policies at the network side based on the marking.

[0015] Further objectives, features and advantages of the enclosed embodiments will appear from the following detailed disclosure, from the attached dependent claims as well as from the drawings.

[0016] In general, unless otherwise explicitly defined herein, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field. Unless otherwise explicitly stated, all references to "an / a / the element, device, component, part, module, step, etc." are to be openly interpreted as referring to at least one instance of the element, device, component, part, module, step, etc. Unless explicitly stated otherwise, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention may be best understood by referring to the following description and accompanying drawings which are used to illustrate specific embodiments of the invention. In the drawings:

[0018] Figure 1 is a networked system according to a particular embodiment of the solution described herein;

[0019] Figure 2 is a signaling diagram illustrating a procedure according to a specific embodiment of the solution described herein;

[0020] Figure 3 is a signaling diagram illustrating a procedure according to a specific embodiment of the solution described herein;

[0021] Figure 4is a signaling diagram illustrating a procedure according to a specific embodiment of the solution described herein;

[0022] Figure 5 is a flow chart illustrating a method performed by a UE according to a specific embodiment of the solution described herein;

[0023] Figure 6 is a flow chart illustrating a method performed by a mobile network node according to a particular embodiment of the solution described herein;

[0024] Figure 7 is a flow chart illustrating a method performed by a mobile network node according to a particular embodiment of the solution described herein;

[0025] Figure 8 is a block diagram of a mobile network node configured according to a particular embodiment of the solution described herein;

[0026] Fig. 9 is a block diagram of a UE configured according to certain embodiments of the solutions described herein. DETAILED DESCRIPTION

[0027] The present invention will now be described in detail below with reference to the accompanying drawings, in which embodiments of the present invention or examples of implementation are shown. However, the present invention may be implemented or realized in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be defaulted to existing / using in another embodiment. These embodiments of the disclosed subject matter are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted or expanded without departing from the scope of the described subject matter.

[0028] The example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate aspects of fifth generation (5G) architecture. Figure 1 is an example networking system 100 according to an example embodiment of the present disclosure. Figure 1In particular, a user equipment (UE) 101 is shown, which can communicate with a (radio) access network (RAN) 102, as well as an access and mobility management function (AMF) 106 and a user plane function (UPF) 103. The AMF 106 can in turn communicate with core network services, including a session management function (SMF) 107 and a policy control function (PCF) 111. The core network services can also communicate with an application server / application function (AS / AF) 113. Other networking services also include a network slice selection function (NSSF) 108, an authentication server function (AUSF) 105, a user data management (UDM) 112, a user data repository (UDR) 114, a network exposure function (NEF) 109, a network repository function (NRF) 110, and a data network (DN) 104. In some example implementations of the embodiments of the present disclosure, AMF 106, SMF 107, UPF 103, PCF 111, AUSF 105, NRF 110, UDM 112, UDR 114, NEF 109, AF 113, and NSSF 108 are all considered NFs. One or more additional instances of a network function (NF) may be incorporated into a networked system.

[0029] 3GPP TS 24.526 describes the UE policies for 5G systems, which are delivered from the PCF to the UE. The UE policies include the UE Routing Selection Policy (URSP) and the Access Network Discovery and Selection Policy (ANDSP).

[0030] The network (PCF) installs URSP rules in the UE. URSP rules include a list of service descriptors and routing descriptors as specified in 3GPP TS 23.503. The service descriptor may include an application descriptor in the form of an application identifier or a service filter.

[0031] The solution described herein aims to enable detection of tethered traffic and application of tethered policies to such traffic.

[0032] To achieve such objectives, the present disclosure provides a method performed by a UE 101, an access and mobility management entity, a session management entity, a policy control entity, and a user data repository entity. In some embodiments, the access and mobility management entity is an AMF 106. In some embodiments, the session management entity is an SMF 107. In some embodiments, the policy control entity is a PCF 111. In some embodiments, the user data repository entity is a UDR 114.

[0033] The method includes: receiving subscription information from a subscriber data repository entity at a policy control entity, the subscription information including an indication of an action to be applied to a service of a connected device at a UE; transmitting a connection policy from the policy control entity to the UE, the connection policy including the received action to be applied to the service of the connected device; and applying the connection policy to the service of the connected device at the UE.

[0034] In some embodiments of the method, the tethering policy includes an indication of blocking traffic for tethered devices. In some embodiments of the method, the tethering policy includes an indication of allowing only a maximum number of traffic transmissions for tethered devices connected at the same time. In some embodiments of the method, the tethering policy includes an indication of marking traffic for tethered devices with a specific value contained in a protocol header, the value being the same for all tethered devices or different for each tethered device. In some embodiments of the method, the tethering policy includes an indication of reporting an event to a CP entity or another CP entity in response to detecting traffic for a tethered device. In some embodiments of the method, the indication of reporting an event includes an indication of reporting the number of tethered devices, the detection of new tethered devices, or the traffic volume of tethered devices. In some embodiments of the method, applying the tethering policy includes transmitting a report, the report including the number of tethered devices, the detection of new tethered devices, or the traffic volume of tethered devices. In some embodiments of the method, the tethering policy is received from an access and mobility management entity at the UE in a protocol data unit session response message or in a UE routing policy URSP. In some embodiments of the method, the tethering policy is received at the UE from a policy control entity in a UE routing policy URSP.

[0035] The present disclosure also provides a mobile network node, in particular a control plane entity 800 and a UE 900, each node being configured to perform a corresponding method as described herein. The present disclosure also provides a corresponding computer program including a code, for example in the form of a computer program, which when executed on a processing circuit of the mobile network node causes the mobile network node to perform the disclosed method.

[0036] Advantageously, the solution disclosed herein enables detection of tethered traffic at the UE in a simple and efficient manner, which would be impossible to detect at the network side, for example, when the traffic is encrypted.

[0037] Further advantageously, the solution disclosed herein enables controlling tethering traffic at the UE and applying tethering policies at the UE that would not be possible to apply at the network side.

[0038] Further advantageously, the solution disclosed herein enables marking of tethered traffic at the UE and applying tethering policies at the network side based on the marking.

[0039] In the following, various figures showing examples of embodiments of the solution are described in detail.

[0040] Figure 2 1 is a signaling diagram illustrating a process for provisioning a UE with a tethering policy at PDU session establishment. In this figure, the access and mobility management entity is AMF 106, the session management entity is SMF 107, the policy control entity is PCF 111, and the user data repository entity is UDR 114. Before performing this process, the UDR should be provisioned with corresponding subscription data indicating that the UE is subject to the appropriate tethering policy.

[0041] In step 211, UE 101 triggers the PDU session establishment process and sends a PDU session establishment request to SMF. This request is relayed by AMF. As part of this process, AMF 106 creates a policy association with PCF 111.

[0042] At step 212, SMF 107 creates a policy association with PCF 111 and sends a request to the PCF to retrieve a policy for the user.

[0043] In step 213, the PCF sends a request for the corresponding subscription data to the UDR.

[0044] At step 214, the PCF retrieves a subscriber policy profile from the UDR, which profile includes a tethering policy containing actions to be applied to services of the tethered device.

[0045] In step 215, the PCF generates PCC rules including the tie-in strategy and transmits it to the SMF. The tie-in strategy may include:

[0046] Priority: Determines the priority in which this policy is enforced relative to other policies.

[0047] Traffic descriptor: Identifies the traffic to which the policy applies. For example, it could be a match-all rule, meaning all traffic passing through the hotspot, or if connections need to be detected on a per-application basis, a different set of traffic filters (e.g., IP triples or quintuples) could be included in the traffic descriptor.

[0048] ·Tie Descriptor: Determines the tie enforcement actions. It may include:

[0049] o Tether Enforcement Action: Determines the action to be applied when tethering is detected, e.g. blocking tethered traffic after a maximum number of devices are connected simultaneously, or marking tethered traffic (using a token), e.g. with an IP options header or with a DSCP code or source port (different for each tethered device). The latter part will allow the network (e.g. in the UPF) to detect tethered traffic and differentiate between each of the tethered devices.

[0050] o Tethering metrics for reporting: Determine the tethering metrics that need to be reported, such as reporting tethering events, reporting tethering capacity to UE, reporting the number of tethered devices, etc. Alternatively, the tethering action may be explicitly called through some UE internal API.

[0051] o Destination URI: When present, it indicates the URI of the entity receiving the report to which the tie metrics should be forwarded. It can be the NF IP address or the IP of the reporting server. If the destination URI is not included, it may indicate that the tie metrics should be forwarded to the PCF (via the non-access stratum through the AMF).

[0052] In step 216, the SMF sends a PDU Session Establishment Response message to the UE, which includes the connection strategy as described in the previous steps. This message is relayed by the AMF.

[0053] In step 217, the UE receives and installs the tethering policy.

[0054] Figure 3 is a signaling diagram illustrating a procedure for provisioning a tethering policy to a UE 101. In this figure, the access and mobility management entity is the AMF 106, the session management entity is the SMF 107, the policy control entity is the PCF 111, and the user data repository entity is the UDR 114. Before performing this procedure, the UDR should be provisioned with corresponding subscription data indicating that the UE is subject to the appropriate tethering policy.

[0055] In step 311, the PDU session establishment process is performed. In this step, the PCF retrieves the connection strategy from the UDR, for example, Figure 2 As in steps 213 and 214 in .

[0056] In step 312, the PCF sends the UE policy including the tethering policy to the UE. In some embodiments, this step is based on an extension of the UE policy (generated by the PCF and sent to the UE via the AMF, as shown in steps 313 and 314), which allows the network operator to trigger the tethering policy for the user's service. The tethering policy may include:

[0057] Priority: Determines the priority in which this policy is enforced relative to other policies.

[0058] Traffic descriptor: Identifies the traffic to which the policy applies. For example, it could be a match-all rule, meaning all traffic passing through the hotspot, or if connections need to be detected on a per-application basis, a different set of traffic filters (e.g., IP triples or quintuples) could be included in the traffic descriptor.

[0059] ·Tie Descriptor: Determines the tie enforcement actions. It may include:

[0060] o Tether Enforcement Action: Determines the action to be applied when tethering is detected, e.g. blocking tethered traffic after a maximum number of devices are connected simultaneously, or marking tethered traffic (using a token), e.g. with an IP options header or with a DSCP code or source port (different for each tethered device). The latter part will allow the network (e.g. in the UPF) to detect tethered traffic and differentiate between each of the tethered devices.

[0061] o Tethering metrics for reporting: Determine the tethering metrics that need to be reported, such as reporting tethering events, reporting tethering capacity to UE, reporting the number of tethered devices, etc. Alternatively, the tethering action may be explicitly called through some UE internal API.

[0062] o Destination URI: When present, it indicates the URI of the entity receiving the report to which the tie metrics should be forwarded. It can be the NF IP address or the IP of the reporting server. If the destination URI is not included, it may indicate that the tie metrics should be forwarded to the PCF (via the non-access stratum through the AMF).

[0063] Steps 313 and 314 illustrate the situation where the AMF relays the UE policy sent from the PCF to the UE.

[0064] In step 315, the UE receives and installs the tethering policy.

[0065] Figure 4 4 is a signaling diagram showing the enforcement of a tethering policy at UE 101 when tethering device 401 connects to the UE's hotspot or sends a tethering service to the UE. Before performing this process, Figure 2 or Figure 3 The process described in should have occurred and the UE should have installed the association policy.

[0066] In step 411, the tethered device 401 connects to the hotspot of the UE.

[0067] In step 412, the UE detects the tethered device and applies the corresponding tethering policy. For example, the UE may be configured to drop traffic from the tethered device 401 if the maximum number of tethered devices has been reached, or it may not allow the tethered device to connect, or it may configure a reporting action to be performed on the tethered device 401.

[0068] In step 413, if the tethered device 401 successfully connects to the hotspot of the UE, the tethered device 401 sends the service to the UE.

[0069] In step 414, the UE detects tethered traffic for tethered device 401 and applies the corresponding tethered policy. For example, if the maximum number of tethered devices has been reached, the UE may drop traffic from tethered device 401, it may route traffic according to the tethered policy, it may perform a reporting action included in the tethered policy, or it may perform a traffic marking action included in the tethered policy.

[0070] In some embodiments, if the UE applies a marking policy, the UE may mark the traffic with the following information (e.g., in an IP options header):

[0071] • An indication of a tethered service (eg a token), which allows the network (eg a UPF) to detect that the service is a tethered service.

[0072] • An indication of a specific tether or tether identifier. This allows the network (eg, UPF) to distinguish between tethers and apply differentiated policies on a per-tether basis.

[0073] Packet Flow Descriptor (PFD), PFD Set or Application Identifier. This indicates the matching service filter or application and allows the UPF to identify the specific application that is delivering the tethered service.

[0074] Figure 5 is a flow chart illustrating a method performed by a UE to enforce a tethering policy at the UE.

[0075] In step 501, the UE receives a tethering strategy from a control plane entity. In some embodiments, the control plane entity is a PCF. In some embodiments, the control plane entity is an AMF. The tethering strategy is as defined in step 215.

[0076] The UE applies the tethering policy to the traffic of the tethered devices at step 502. For example, the UE may drop traffic from the tethered devices if the maximum number of tethered devices has been reached, it may route traffic according to the tethering policy, it may perform a reporting action included in the tethering policy, or it may perform a traffic marking action included in the tethering policy.

[0077] Figure 6is a flow chart illustrating a method performed by a policy control entity to provide tethering policies to a user equipment. In some embodiments, the policy control entity is a PCF.

[0078] At step 601, the policy control entity receives subscription information from a subscriber data repository entity, the subscription information comprising an indication of actions to be applied to services of tethered devices at the UE.

[0079] At step 602, the policy control entity transmits a tethering policy to the UE, the tethering policy including the received actions to be applied to the traffic of the tethered device.

[0080] Figure 7 1 is a flow chart illustrating a method performed by an access and mobility management entity to provide a tethering strategy to a user equipment. In some embodiments, the access and mobility management entity is an AMF.

[0081] At step 701, the access and mobility management entity receives a tethering policy from a policy control entity, the tethering policy comprising an indication of actions to be applied to traffic of a tethered device at the UE.

[0082] At step 702, the access and mobility management entity transmits a tethering policy to the UE.

[0083] Figure 8 800 is a block diagram illustrating elements of a mobile network node 800 of a mobile communication network. In some embodiments, the mobile network node 800 is an AMF. In some embodiments, the mobile network node 800 is an SMF. As shown, the mobile network node may include a network interface circuit 801 (also referred to as a network interface) configured to provide communication with a core network and / or other nodes of the network. The mobile network node may also include a processing circuit 802 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 803 (also referred to as a memory) coupled to the processing circuit. The memory circuit 803 may include a computer-readable program code, which, when executed by the processing circuit 802, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 802 may be defined as including a memory so that a separate memory circuit is not required. As discussed herein, the operation of the mobile network node may be performed by the processing circuit 802 and / or the network interface circuit 801. For example, the processing circuit 802 may control the network interface circuit 801 to transmit communications to one or more other network nodes through the network interface circuit 801 and / or receive communications from one or more other network nodes through the network interface circuit. In addition, modules may be stored in the memory 803, and these modules may provide instructions so that when the processing circuit 802 executes the instructions of the modules, the processing circuit 802 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to core network nodes).

[0084] Fig. 9 900 (also referred to as a communication device, mobile terminal, mobile communication terminal, wireless device, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment node / terminal / device, etc.) configured to provide wireless communication according to embodiments of the present disclosure. As shown, the communication device UE may include an antenna 907 and a transceiver circuit 901 (also referred to as a transceiver), the transceiver circuit 901 including a transmitter and a receiver configured to provide uplink and downlink radio communications with (one or more) base stations of a radio access network (also referred to as RAN nodes). The UE may also include a processing circuit 903 (also referred to as a processor) coupled to the transceiver circuit and a memory circuit 905 (also referred to as a memory, e.g., corresponding to a device-readable medium) coupled to the processing circuit. The memory circuit 905 may include computer-readable program code such as an application client 909, which, when executed by the processing circuit 903, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 903 may be defined as including a memory so that a separate memory circuit is not required. The UE 900 may also include an interface (such as a user interface) coupled to the processing circuit 903, and / or the UE may be incorporated into a vehicle. As discussed herein, the operations of the UE may be performed by the processing circuit 903 and / or the transceiver circuit 901. For example, the processing circuit 903 may control the transceiver circuit 901 to transmit communications to a radio access network node (also known as a base station) over a radio interface through the transceiver circuit 901 and / or receive communications from a RAN node over a radio interface through the transceiver circuit 901. In addition, modules may be stored in the memory circuit 905, and these modules may provide instructions so that when the processing circuit 903 executes the instructions of the module, the processing circuit 903 performs corresponding operations (e.g., the operations disclosed herein with respect to the example embodiments related to the UE).

Claims

1. A method performed by a user equipment UE (101) for enforcing a tethering policy at the UE, the method comprising: receiving (216, 312, 314) a tethering policy from a control plane CP entity of the mobile communication system, the tethering policy comprising actions to be applied to traffic of the tethered device; as well as Applying (412, 414) the tethering policy to the services of the tethered device; The tethering strategies include: A service descriptor, used to identify the service to which the policy applies; and The indication of the traffic of the tethered device is marked with a specific value contained in the protocol header, which is different for each tethered device.

2. The method of claim 1, wherein: The tethering policy includes an indication to block traffic to the tethered device.

3. The method of claim 1, wherein: The tethering policy includes an indication that traffic transmission is allowed only to a maximum number of simultaneously connected tethered devices.

4. The method of claim 1, wherein: The tethering policy includes an indication to report an event to the CP entity or another CP entity in response to detecting traffic of a tethered device.

5. The method of claim 4, wherein: Reporting the indication of the event includes reporting a number of tethered devices, detection of a new tethered device, or an indication of traffic volume of tethered devices.

6. The method of claim 5, wherein: Applying the tethering policy includes transmitting a report to the CP entity or another CP entity, the report including the number of tethered devices, detection of new tethered devices, or traffic volume of tethered devices.

7. The method according to any one of claims 1 to 6, wherein: The tie-in policy is received from the access and mobility management entity in a protocol data unit session response message or in a UE routing policy URSP.

8. The method according to any one of claims 1 to 6, wherein: The tie-in policy is received in the UE routing policy URSP from a policy control entity.

9. A method performed by a policy control entity (111) for providing a tethering policy to a user equipment UE (101), the method comprising: receiving (214, 311) subscription information from a subscriber data repository entity of a mobile communication system, the subscription information comprising an indication of an action to be applied at the UE for services of a tethered device; and transmitting (215, 312, 313) a tethering policy to the UE, the tethering policy comprising the received action to be applied to the service of the tethered device; The tethering strategies include: Service descriptors, which identify the services to which the policy applies; and The indication of the traffic of the tethered device is marked with a specific value contained in the protocol header, which is different for each tethered device.

10. The method of claim 9, wherein: The tethering policy includes an indication to block traffic to the tethered device.

11. The method of claim 9, wherein: The tethering policy includes an indication that traffic transmission is allowed only to a maximum number of simultaneously connected tethered devices.

12. The method of claim 9, wherein: The tethering policy includes instructions to report an event to a CP entity or another CP entity in response to detecting traffic of a tethered device.

13. The method of claim 12, wherein: Reporting the indication of the event includes reporting a number of tethered devices, detection of a new tethered device, or an indication of traffic volume of tethered devices.

14. The method according to any one of claims 9 to 13, wherein: The tie-in strategy is conveyed in the UE Routing Strategy URSP.

15. A method performed by an access and mobility management entity (106) for providing a tethering strategy to a user equipment UE (101), the method comprising: receiving (313) a tethering policy from a policy control entity of a mobile communication system, the tethering policy comprising an indication of an action to be applied at the UE to traffic of a tethered device; as well as transmitting (314) the tethering policy to the UE; The tethering strategies include: A service descriptor, used to identify the service to which the policy applies; and The indication of the traffic of the tethered device is marked with a specific value contained in the protocol header, which is different for each tethered device.

16. The method of claim 15, wherein: The tethering policy includes an indication to block traffic to the tethered device.

17. The method of claim 15, wherein: The tethering policy includes an indication that traffic transmission is allowed only to a maximum number of simultaneously connected tethered devices.

18. The method of claim 15, wherein: The tethering policy includes instructions to report an event to a CP entity or another CP entity in response to detecting traffic of a tethered device.

19. The method of claim 18, wherein: Reporting the indication of the event includes reporting a number of tethered devices, detection of a new tethered device, or an indication of traffic volume of tethered devices.

20. The method of any one of claims 15 to 19, wherein: The tie-in policy is transmitted in a protocol data unit session response message or in a UE routing policy URSP.

21. A computer program comprising program code portions for performing the method of any one of claims 1 to 14 when said computer program is executed on one or more computing devices.

22. The computer program of claim 21, stored on a computer readable recording medium.

23. A user equipment UE (900) for enforcing a tethering policy at the UE, the UE being adapted to perform the method according to any one of claims 1 to 8.

24. The UE of claim 23, comprising at least one processor and at least one memory, wherein the at least one memory contains instructions executable by the at least one processor, so that the UE is operable to perform the method of any one of claims 1 to 8.

25. A computing unit (800) configured to operate a control plane node of a mobile communication system to provide a tethering strategy to a user equipment UE, adapted to perform any one of claims 9 to 14 and 15 to 20.

26. A computing unit as claimed in claim 25, comprising at least one processor and at least one memory, the at least one memory containing instructions executable by the at least one processor, so that the control plane node is operable to perform the method as claimed in any one of claims 9 to 14 and 15 to 20.

27. A system comprising a UE according to any of claims 23 and 24, a computing unit according to any of claims 25 and 26, and a further computing unit according to any of claims 25 and 26.

Images