Method, apparatus and computer program

Abstract

There is provided an apparatus in a user equipment, the apparatus comprising: means for receiving at least one user equipment routing policy rule from a core network entity, the at least one user equipment routing policy rule comprising a component having information associated with a source device capable of requesting data traffic via the user equipment; and means for receiving a request for uplink data traffic from an application of the source device, where the request comprises information about the source device. The apparatus further comprises means for determining, using the at least one user equipment routing policy rule and based on information about the source device received in the request, how to route data traffic from the application to determine a route; and means for routing the data traffic according to the determined route.

Description

Technical Field

[0001] The present application relates to methods, apparatus and computer programs for wireless communication systems. Background Art

[0002] A communication system may be a facility that enables communication sessions between two or more entities (e.g., user terminals, base stations / access points, and / or other nodes) by providing carrier waves between the various entities involved in the communication path. A communication system may be provided, for example, with the aid of a communication network and one or more compatible communication devices. A communication session may include, for example, communications of data for carrying communications (e.g., voice, email, text messages, multimedia and / or content data, etc.). Non-limiting examples of services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems (e.g., the Internet). Summary of the invention

[0003] According to one aspect, a device in a user equipment is provided, the device comprising: a component for receiving at least one user equipment routing selection policy rule from a core network entity, wherein the at least one user equipment routing selection policy rule includes a component having information associated with a source device capable of requesting data services via the user equipment; a component for receiving a request for uplink data services from an application of the source device, wherein the request includes information about the source device; a component for determining how to route the data services from the application to determine a route using the at least one user equipment routing selection policy rule and based on the information about the source device received in the request; and a component for routing the data services according to the determined route.

[0004] In one example, the user equipment is configured as a gateway for the device.

[0005] In one example, the information identifying at least one source application is included in a traffic descriptor component of the user equipment routing policy rule.

[0006] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0007] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0008] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0009] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0010] In one example, the at least one user device routing selection policy rule includes multiple user device routing selection policy rules, and wherein the component for determining includes: a component for comparing i) information about the source device received in the request with ii) corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules; and a component for selecting a user device routing selection policy rule in the multiple user device routing selection policy rules based on the comparison.

[0011] In one example, the component for comparing the information about the source device received in the request with the corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules includes: a component for matching the information received about the source device with the corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules.

[0012] In one example, the route is determined using a routing descriptor associated with the selected user equipment routing policy rule.

[0013] In one example, the apparatus includes: a component for determining whether there is an existing protocol data unit session that has been established and that complies with the routing descriptor; and a component for routing the data service using the protocol data unit session when there is an existing protocol data unit session that complies with the routing descriptor.

[0014] In one example, the apparatus includes means for performing quality of service mapping for the protocol data unit session using at least one quality of service rule.

[0015] In one example, the user device is configured as a gateway of a personal Internet of Things network, and the personal Internet of Things network includes at least one personal Internet of Things network unit.

[0016] In one example, the apparatus includes means for providing an indication to another core network entity that the user equipment supports user equipment routing policy rules including a component having information associated with a source device capable of requesting data services via the user equipment.

[0017] In one example, the indication is provided to the another core network entity within a registration request message.

[0018] According to one aspect, a device for a core network entity is provided, the device comprising: a component for determining at least one user equipment routing selection policy rule for a user equipment, wherein the at least one user equipment routing selection policy rule comprises a component having information associated with a source device capable of requesting a data service via the user equipment; and a component for providing the at least one user equipment routing selection policy rule to the user equipment.

[0019] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0020] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0021] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0022] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0023] In one example, the component for determining includes: a component for determining the at least one user device routing selection policy rule based on input received from an application function, wherein the application function is associated with a personal Internet of Things network associated with the user device.

[0024] In one example, the apparatus includes means for receiving an indication from the user equipment that the user equipment supports a user equipment routing policy rule including a component having information associated with a source device capable of requesting data services via the user equipment.

[0025] In one example, the apparatus includes a component for using the received indication to trigger determination of the at least one user equipment routing policy rule, the at least one user equipment routing policy rule including the component having information associated with the source device capable of requesting data services via the user equipment.

[0026] According to one aspect, a device is provided, comprising: one or more processors, and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the device to perform: receiving at least one user device routing selection policy rule from a core network entity, wherein the at least one user device routing selection policy rule includes a component having information associated with a source device capable of requesting data services via the user device; receiving a request for uplink data services from an application of the source device, wherein the request includes information about the source device; determining how to route the data services from the application to determine a route using the at least one user device routing selection policy rule and based on the information about the source device received in the request; and routing the data services according to the determined route.

[0027] In one example, the user equipment is configured as a gateway for the device.

[0028] In one example, the information identifying at least one source application is included in a traffic descriptor component of the user equipment routing policy rule.

[0029] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0030] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0031] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0032] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0033] In one example, the at least one user device routing selection policy rule includes multiple user device routing selection policy rules, and wherein the determination includes: comparing i) information about the source device received in the request with ii) corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules; and selecting a user device routing selection policy rule from the multiple user device routing selection policy rules based on the comparison.

[0034] In one example, comparing the information received about the source device in the request with corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules includes: matching the received information about the source device with corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules.

[0035] In one example, the route is determined using a routing descriptor associated with the selected user equipment routing policy rule.

[0036] In one example, the device is caused to perform: determining whether there is an existing protocol data unit session that has been established and is consistent with the routing descriptor; and when there is an existing protocol data unit session that is consistent with the routing descriptor, using the protocol data unit session to route the data service.

[0037] In one example, the apparatus is caused to perform: performing quality of service mapping for the protocol data unit session using at least one quality of service rule.

[0038] In one example, the user device is configured as a gateway of a personal Internet of Things network, and the personal Internet of Things network includes at least one personal Internet of Things network unit.

[0039] In one example, the apparatus is caused to perform: providing an indication to another core network entity that the user equipment supports a user equipment routing policy rule including a component having information associated with a source device capable of requesting data services via the user equipment.

[0040] In one example, the indication is provided to the another core network entity within a registration request message.

[0041] According to one aspect, a device is provided, comprising: one or more processors, and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the device to perform: determining at least one user device routing selection policy rule for a user device, wherein the at least one user device routing selection policy rule comprises a component having information associated with a source device capable of requesting a data service via the user device; and providing the at least one user device routing selection policy rule to the user device.

[0042] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0043] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0044] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0045] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0046] In one example, the determining includes determining the at least one user device routing policy rule based on input received from an application function, wherein the application function is associated with a personal Internet of Things network associated with the user device.

[0047] In one example, the apparatus is caused to perform: receiving an indication from the user equipment that the user equipment supports a user equipment routing policy rule including a component having information associated with a source device capable of requesting data services via the user equipment.

[0048] In one example, the apparatus is caused to execute: using the received indication to trigger determining the at least one user equipment routing policy rule, the at least one user equipment routing policy rule including the component having information associated with the source device capable of requesting data services via the user equipment.

[0049] According to one aspect, a method performed by a user device is provided, the method comprising: receiving at least one user device routing selection policy rule from a core network entity, wherein the at least one user device routing selection policy rule comprises a component having information associated with a source device capable of requesting a data service via the user device; receiving a request for an uplink data service from an application of the source device, wherein the request comprises information about the source device; determining how to route the data service from the application to determine a route using the at least one user device routing selection policy rule and based on the information about the source device received in the request; and routing the data service according to the determined route.

[0050] In one example, the user equipment is configured as a gateway for the device.

[0051] In one example, the information identifying at least one source application is included in a traffic descriptor component of the user equipment routing policy rule.

[0052] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0053] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0054] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0055] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0056] In one example, the at least one user device routing selection policy rule includes multiple user device routing selection policy rules, and wherein the determination includes: comparing i) information about the source device received in the request with ii) corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules; and selecting a user device routing selection policy rule from the multiple user device routing selection policy rules based on the comparison.

[0057] In one example, comparing the information received about the source device in the request with corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules includes: matching the received information about the source device with corresponding information within the component of each user device routing selection policy rule in the multiple user device routing selection policy rules.

[0058] In one example, the route is determined using a routing descriptor associated with the selected user equipment routing policy rule.

[0059] In one example, the method includes determining whether there is an existing protocol data unit session that has been established and that complies with the routing descriptor; and when there is an existing protocol data unit session that complies with the routing descriptor, routing the data service using the protocol data unit session.

[0060] In one example, the method includes performing quality of service mapping for the protocol data unit session using at least one quality of service rule.

[0061] In one example, the user device is configured as a gateway of a personal Internet of Things network, and the personal Internet of Things network includes at least one personal Internet of Things network unit.

[0062] In one example, the method includes providing an indication to another core network entity that the user equipment supports user equipment routing policy rules including a component having information associated with a source device capable of requesting data traffic via the user equipment.

[0063] In one example, the indication is provided to the another core network entity within a registration request message.

[0064] According to one aspect, a method performed by a core network entity is provided, the method comprising: determining at least one user equipment routing selection policy rule for a user equipment, wherein the at least one user equipment routing selection policy rule comprises a component having information associated with a source device capable of requesting a data service via the user equipment; and providing the at least one user equipment routing selection policy rule to the user equipment.

[0065] In one example, for the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identifier of at least one source device; an identifier of a network associated with the user equipment.

[0066] In one example, at least one of the following: the identification of the source device is an identification of a personal Internet of Things network unit; and the identification of the network is an identification of a personal Internet of Things network.

[0067] In one example, the identification of the source device includes at least one of: a MAC address, a source IP address, a port number, a Bluetooth identification, a unique identification of the PINE, a network access identifier received by the user device after the source device has been authenticated.

[0068] In one example, the identifier of the personal Internet of Things network includes at least one of the following: an SSID of an access point, a unique identifier of the PIN.

[0069] In one example, the determining includes determining the at least one user device routing policy rule based on input received from an application function, wherein the application function is associated with a personal Internet of Things network associated with the user device.

[0070] In one example, the method includes receiving an indication from the user equipment that the user equipment supports a user equipment routing policy rule including a component having information associated with a source device capable of requesting data traffic via the user equipment.

[0071] In one example, the method includes using the received indication to trigger determining the at least one user equipment routing policy rule, the at least one user equipment routing policy rule including the component having information associated with the source device capable of requesting data services via the user equipment.

[0072] According to one aspect, a computer program is provided that includes computer executable instructions that, when executed on one or more processors, perform: receiving at least one user device routing selection policy rule from a core network entity, wherein the at least one user device routing selection policy rule includes a component having information associated with a source device capable of requesting data services via the user device; receiving a request for uplink data services from an application of the source device, wherein the request includes information about the source device; determining how to route the data services from the application to determine a route using the at least one user device routing selection policy rule and based on the information about the source device received in the request; and routing the data services according to the determined route.

[0073] According to one aspect, a computer program comprising computer executable instructions is provided, the computer executable instructions when executed on one or more processors performing: determining at least one user equipment routing policy rule for a user equipment, wherein the at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data services via the user equipment; and providing the at least one user equipment routing policy rule to the user equipment. A computer product stored on a medium can cause an apparatus to perform a method as described herein.

[0074] An electronic device may comprise an apparatus as described herein.

[0075] Various aspects have been described above. It should be understood that further aspects may be provided by combining any two or more of the various aspects described above.

[0076] Various further aspects and other embodiments are also described in the following detailed description and appended claims.

[0077] According to some aspects, the subject matter of the independent claims is provided. Some other aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims are to be construed as examples for understanding the present disclosure.

[0078] List of abbreviations

[0079] AF: Application Function

[0080] AMF: Access Management Function

[0081] AN: Access Network

[0082] ANDSP: Access Network Discovery and Selection Strategy

[0083] BS: Base Station

[0084] CN: Core Network

[0085] DL: Downlink

[0086] eNB: eNodeB

[0087] gNB: gNodeB

[0088] IoT: Internet of Things

[0089] IIoT: Industrial Internet of Things

[0090] LTE: Long Term Evolution

[0091] NEF: Network Open Function

[0092] NG-RAN: Next Generation Radio Access Network

[0093] NF:Network Function

[0094] NR: New Radio

[0095] NRF: Network Repository Function

[0096] NW:Network

[0097] MS: Mobile Station

[0098] PCF: Policy Control Function

[0099] PEGC: PIN unit with gateway capability

[0100] PEMC: PIN unit with management capabilities

[0101] PIN: Personal IoT Network

[0102] PINE: PIN unit

[0103] PLMN: Public Land Mobile Network

[0104] RAN: Radio Access Network

[0105] RF: Radio Frequency

[0106] SMF: Session Management Function

[0107] SSID: Service Set Identifier

[0108] UE: User Equipment

[0109] UDR: Unified Data Repository

[0110] UDM: Unified Data Management

[0111] UL: Uplink

[0112] UPF: User Plane Function

[0113] URSP: User Equipment Routing Selection Policy

[0114] 3GPP: Third Generation Partnership Project

[0115] 5G: Fifth Generation

[0116] 5GC: 5G Core Network

[0117] 5G-AN: 5G Radio Access Network

[0118] 5GS: 5G System BRIEF DESCRIPTION OF THE DRAWINGS

[0119] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0120] Figure 1 A schematic representation of a 5G system is shown;

[0121] Figure 2 A schematic representation of the control arrangement is shown;

[0122] Figure 3 A schematic representation of a terminal is shown;

[0123] Figure 4 A schematic representation of an example personal Internet of Things network is shown;

[0124] Figure 5 An example signaling diagram between a user equipment and a network entity is shown;

[0125] Figure 6 Another example signaling diagram between a user equipment and a network entity is shown;

[0126] Figure 7 A flow chart of an example method performed by a user device is shown;

[0127] Figure 8 A flow chart showing an example method performed by a network entity; and

[0128] Fig. 9 A schematic representation of a non-volatile storage medium storing instructions that, when executed by a processor, allow the processor to perform Figure 7 Or one or more steps of the method of 8. DETAILED DESCRIPTION

[0129] Before explaining some examples of the present disclosure in detail, Figures 1 to 3 Certain general principles of wireless communication systems and mobile communication devices are briefly explained to aid understanding of the underlying technology of the described examples.

[0130] In e.g. Figure 1 In the wireless communication system 100 shown in FIG, wireless access is provided to a mobile communication device / terminal or user device and / or user equipment (UE) and / or machine type communication device 102 via at least one base station (not shown) or similar wireless transmission and / or reception node or wireless transmission and / or reception point. The communication device is equipped with appropriate signal receiving and transmitting devices to achieve communication, such as access to a communication network or direct communication with other devices. The communication device can access a carrier provided by a station or access point and send and / or receive communications on the carrier.

[0131] In the following, specific examples are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system serving such a mobile communication device. Figure 1 , 2 3 briefly explain certain general principles of wireless communication systems, their access systems, and mobile communication devices to help understand the underlying technologies of the described examples.

[0132] Figure 1 A schematic representation of a 5G system (5GS) 100 is shown. The 5GS may include a device 102 (e.g., a user equipment or terminal), a 5G access network (5G-AN) 106, a 5G core network (5GC) 104, one or more network functions (NFs), one or more application functions (AFs) 108, and one or more data networks (DNs) 110.

[0133] The 5G-AN 106 may include one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) centralized unit functions. Although one or more of the following examples reference 5G RAN and gNodeB (gNB), the described mechanisms are not limited to the 5G access network (5G-AN) as they also apply to UEs that are connected to the 5GC 104 via a non-3GPP interworking function (N3IWF) to enable untrusted access to the 5GC, connected to the 5GC 104 via a trusted non-3GPP gateway function (TNGF) to enable trusted access to the 5GC, or connected to the 5GC 104 via a wireless access gateway function (W-AGF) to enable wired access to the 5GC.

[0134] 5GC 104 may include access management function (AMF) 112, session management function (SMF) 114, authentication server function (AUSF) 116, user data management (UDM) 118, user plane function (UPF) 120, network open function (NEF) 122 and / or other NFs. Some examples as shown below may be applicable to 3GPP 5G standards. However, some examples may also be applicable to 4G, 3G and other 3GPP standards.

[0135] In e.g. Figure 1In the communication system shown in , wireless access is provided to mobile communication devices / terminals or user devices and / or user equipment (UE) and / or machine type communication devices via at least one base station or similar wireless transmission and / or reception node or wireless transmission and / or reception point. The terminal is equipped with appropriate signal receiving and transmitting devices to achieve communication, such as access to a communication network or direct communication with other devices. The communication device can access a carrier provided by a station or access point and send and / or receive communications on the carrier.

[0136] Figure 2 shows the control method for Figure 1 200 for the functions of a 5G-AN or 5GC shown in FIG. The control device may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be executed to perform one or more current aspects. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 that controls another function of a 5G-AN or 5GC. In some examples, each function of a 5G-AN or 5GC includes a control device 200. In an alternative example, two or more functions of a 5G-AN or 5GC may share a control device.

[0137] Figure 3 An example of a terminal 300 is shown, for example Figure 1 The terminal 300 is a terminal shown in . The terminal 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, a mobile station (MS) or a mobile device (e.g., a mobile phone or a so-called "smart phone"), a computer with a wireless interface card or other wireless interface facilities (e.g., a USB adapter), a personal data assistant (PDA) or tablet computer with wireless communication capabilities, a machine type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination of these items, etc. The terminal 300 can provide, for example, communication for carrying data for communication. The communication can be one or more of voice, email, text message, multimedia, data, machine data, etc.

[0138] The terminal 300 may receive signals over the air or radio interface 307 via suitable means for receiving and may transmit signals via suitable means for transmitting radio signals. Figure 3In the mobile device, the transceiver arrangement is schematically designated by block 306. The transceiver arrangement 306 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0139] The terminal 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for software and hardware assisted execution of the tasks that the terminal 300 is designed to perform, including controlling access to access systems and other communication devices and controlling communication with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow execution of one or more current aspects. The software code 308 may be stored in the ROM 302a.

[0140] The processor, storage device and other related control devices may be arranged on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface, such as a keypad 305, a touch-sensitive screen or touchpad, a combination thereof, etc. Optionally, one or more of a display, a speaker and a microphone may be provided, depending on the type of device.

[0141] One or more of the following examples apply to a personal Internet of Things network (PIN). A PIN is a network of devices (e.g., home automation, gaming, enterprise infrastructure, etc.) that may or may not have 3GPP UE capabilities and communicate with a data network via a gateway (GW). A PIN is configured to manage a set of at least one PIN unit (PEGC) with gateway capabilities and one or more PIN units (PINEs) that can communicate with each other and with a 5G network via the PEGC. A user device may be configured as a PEGC UE. Each PINE in a PIN is a device that can communicate within the PIN via a direct connection to other PINEs, a PEGC, or communicate outside the PIN via the PEGC. A PIN direct connection is a connection between two PIN units without any 3GPP RAN or core network entity in the middle, such as on a Zigbee or Bluetooth connection. A PEGC is a PIN unit that can provide connections to and from a 5G network for other PINEs. A PEGC can provide a repeater for communications between PINEs. A PIN may also include one or more PIN units (PEMCs) with management capabilities. A PEMC is a PIN unit that has the ability to manage a PIN. In some systems, the PIN unit may have both PIN management capabilities and gateway capabilities.

[0142] Figure 4 A schematic representation of an example personal Internet of Things network (PIN) 400 is shown. In this example, the PIN 400 is a home automation PIN. In other examples, the PIN may include other types of devices.

[0143] In this example, PIN 400 includes multiple PINEs 401. PINEs 401 may include smart doorbells, motion sensors, smart light bulbs, and smart sockets, such as Figure 4 . A PEMC 403 is also provided. The PEMC may be configured to manage each component of the PIN 400. The PIN 400 further includes a PEGC 405. The PEGC 405 may be a UE. In other examples, the PEGC 405 is another suitable device with gateway capabilities, such as a wired residential gateway.

[0144] Each PINE 401 is capable of communicating with a PEGC 405. Some PINEs 401 are capable of communicating directly with a PEGC 405. Other PINEs are capable of communicating with a PEGC 405 via a relay device. Many PINEs are configured as relay devices so that a PINE 401 can communicate with a PEGC 405 via a relay PINE.

[0145] Other devices 407 may be connected to the PEGC, such as a printer device. For example, the device 407 may be connected via an Ethernet connection.

[0146] PEGC 405 is capable of communicating with 5G core network 409. PEGC 405 can communicate with 5GC 409 via a suitable wireless connection. Any data service provided by PINE 401 of PIN will be sent to 5GC409 via PEGC 405.

[0147] The device of PIN 400 can be an IoT device or a non-3GPP device acting as PINE 401, and can be, for example, a smart socket, a smart watch, a smart pet collar, an earplug, a VR head-mounted display, etc., which are usually connected to PEGC UE 405 via non-3GPP access. Examples of non-3GPP access include wireless local area network (WLAN) and Bluetooth. When PEGC UE 405 moves, PIN 400 moves with PEGC UE 405 and the associated PINE 401. There may also be other IoT devices or non-3GPP devices, which are typically fixed devices connected to an evolved residential gateway (eRG) using non-3GPP access (WLAN, wired). Examples of fixed devices include media servers, printers, smart thermostats, smart sprinklers, smart blinds, smart garages, etc.

[0148] In an example, when an application running on PINE 401 requests uplink (UL) data service from a UE, the UE may perform two steps:

[0149] First, the UE processes the UE Routing Policy (URSP) rules to decide how to route the application data traffic. The UE attempts to match the information received from the application with the traffic descriptors in the URSP rules. For URSP rules with matching traffic descriptors, the UE selects a valid Routing Selection Descriptor (RSD) associated with the URSP rule. The UE then checks if there is an existing Protocol Data Unit (PDU) session that matches the RSD and uses the same PDU session for the application data traffic. If there is no suitable PDU session, the UE establishes a new PDU session for the application data traffic.

[0150] Secondly, when application data traffic is associated with a PDU session (new or existing), the UE performs QoS mapping using Quality of Service (QoS) rules. QoS rules may be provided to the UE by a core network entity (eg, SMF).

[0151] However, the first part of the above mechanism does not apply to the PIN unit (PEGC) UE with GW capability in the PIN. The PEGC UE acts as the gateway function of the PIN unit (PINE) device in the PIN. This is because the PINE behind the PEGC can run applications with different routing and policy control requirements. For example, the PEGC UE may need to use one data network name (DNN) and / or one single network slice assistance information (S-NSSAI) for a group of PINEs behind the PEGC, and different DNNs, S-NSSAIs for another group of PINEs. It should be understood that in the context of PINE and PEGC, the word "behind" means that the PINE is connected to the 5G network via the PEGC. The PEGC acts as a gateway or repeater for the PINE to the network.

[0152] The UE uses the service descriptor in each URSP rule to uniquely identify the application data service. In the current system, the URSP rule supports the components in the service descriptor shown in Table 1 below:

[0153]

[0154] Table 1: Description of the "Traffic Descriptor" that is part of the URSP.

[0155] Each URSP rule includes a traffic descriptor (comprising one or more of the components described in Table 1) that determines when the URSP rule is applicable. The URSP rule is determined to be applicable when a component in the traffic descriptor matches corresponding information from the requesting application. The URSP rule is determined to be inapplicable when, for any given component in the traffic descriptor: corresponding information from the application is not available, or corresponding information from the application does not match any value in the traffic descriptor component.

[0156] It has been determined that the current components of the service descriptors of the URSP rules do not provide a mechanism to identify applications running on PINE devices behind PEGC UEs. For example, the application descriptors (see Table 1) identify applications running on UEs based on "AppId" and "OSId". However, these descriptors do not provide any information about applications running on PINEs behind PEGC UEs. DNN, IP / non-IP / domain descriptors can be provided to determine destination information that can be used to identify application services, but this is not sufficient to uniquely identify applications in (or running on) PINEs behind PEGC UEs. Alternatively, PINEs may not (or cannot) provide such information because the goal is to use "off-the-shelf" PINE devices (i.e., without forcing changes to the interface between PINE and PEGC) to carry, for example, DNNs. For example, there may be multiple PINEs using the same DNN or the same server, but each PINE may need to be treated differently by the network. For example, different PINEs may use different network slices. Furthermore, in a large PIN network, the network may not be able to identify all destination IPs / domains and configure them in the traffic descriptor of the URSP rules to uniquely identify the application running on the PINE. It may be cumbersome for the network operator to know in advance all the destination addresses of the data traffic of each different PINE, and the type of PDU session to be used may be related to the type of PINE device rather than the destination address of their traffic. For example, a video surveillance camera may require a low latency associated PDU session regardless of the destination of its traffic.

[0157] Therefore, the PEGC UE cannot determine how to route traffic from applications running on a PINE device behind the PEGC UE because the PEGC UE cannot uniquely identify the PINE application traffic.

[0158] One or more of the problems discussed previously are addressed in the following examples.

[0159] In an example, an enhanced URSP rule structure is provided that includes a new component in the traffic descriptor component of the URSP rule. The new component is configured so that it includes information referencing the devices (e.g., PINEs) served by the UE (for which the UE acts as a relay or gateway), thereby allowing the traffic descriptor of the URSP rule to target data traffic from a specific device. This will be described in more detail below.

[0160] Figure 5 An example signaling diagram between a user equipment and network entities is shown. The network entities include RAN, AMF and PCF. In this example, the UE can be configured as a PEGC for PIN.

[0161] In S501, the PCF determines that a UE policy is to be provided to the UE. In some examples, the UE has been configured with a UE policy. In this case, the PCF will update the UE policy at the UE.

[0162] The PCF may decide to update UE policies based on triggering conditions (e.g., initial registration, registration with 5GS when the UE moves from EPS to 5GS, or the need to update UE policies).

[0163] In S502, the PCF provides the AMF with a message including the UE policy information determined by the PCF.

[0164] In an example, the message from PCF to AMF may be a "Namf_Communication_N1N2MessageTransfer" message.

[0165] In an example, the UE policy information is included in a UE policy container. The UE policy container may include a list of policy parts. A policy part is identified by a policy part identifier (PSI) and includes one or more URSP rules.

[0166] The UE policy information includes at least one URSP rule, the at least one URSP rule including a component having information associated with a source device capable of requesting data services. The request for data services is via a user device (i.e., the user device is configured as a gateway / repeater). This component may be referred to as a "source descriptor". In other examples, other suitable names are used. The "source descriptor" may be a service descriptor component. In some examples, the UE policy information includes a plurality of URSP rules, each of which includes a "source descriptor" having an identifier associated with a request for data services via a user device.

[0167] In this manner, the URSP rules support the following components in the service descriptor as shown in Table 2 below:

[0168]

[0169] Table 2: Extended list of "Traffic Descriptors" as part of URSP.

[0170] Note that the GW UE may correspond to different types of devices, such as a smartphone. In other examples, the GW UE is a wired residential gateway. In other examples, the GW UE is any suitable device configured as a gateway.

[0171] In S503, there is a network-triggered service request between the UE and the AMF via the RAN. In S503, the AMF attempts to reach the UE. If the UE is registered in a 3GPP access or a non-3GPP access and can be reached by the AMF, the AMF can transmit the UE policy information to the UE (transparently) via the registered and reachable access.

[0172] In S504, the AMF provides the UE with UE policy information including at least one URSP rule with a "source descriptor". In an example, the UE policy information is provided in a UE policy container, wherein the UE policy container includes a list of policy parts.

[0173] In S505, in response to receiving the UE policy information from the AMF, the UE updates the UE policy (at the UE). The UE then provides the updated result to the AMF.

[0174] In S506, if the AMF receives the UE policy information (in S502), and the PCF subscribes to be notified after receiving the UE policy information, the AMF forwards the result from the UE (of S505) to the PCF. The AMF may provide a response message to the PCF using "Namf_Communication_N1MessageNotify".

[0175] Once the UE has been configured with UE policy information (S505), this means that the UE as a PEGC is able to route data traffic from the PINE behind the UE. For example, the UE may receive a request for uplink data traffic from an application of a device (e.g., a PINE). In this way, the UE and the device (which provides the request) are separate devices. The request includes information about the application and / or the requesting device. The UE will then determine how to route the data traffic from the application based on the information received about the device (e.g., a PINE) using at least one URSP rule of the UE policy information to determine the route. In this way, the UE determines the route using both at least one URSP rule and the received information about the device. The UE then routes the data traffic from the application according to the determined route.

[0176] In some examples, the at least one URSP rule includes multiple URSP rules in the UE policy information. Each URSP rule may have a "source descriptor" that identifies the PINE / PIN.

[0177] As just one example, to aid understanding, a UE (or other gateway device) may be configured with three URSP policies. URSP Policy 1: If the data traffic comes from a device at MAC address XYZ (where MAC address XYZ is associated with PINE#1), use Route 1. URSP Policy 2: If the data traffic comes from a device at MAC address ABC (where MAC address ABC is associated with PINE#2) and for IP address CDEF, use Route 2. URSP Policy 3: Otherwise, for any other relayed traffic, use Route 3. In this way, in some examples, the "Source Descriptor" traffic descriptor and the "IP Descriptor" from Table 2 may be used in combination in the URSP rules. For example, the URSP enhancement in Table 2 implements a combination of a source device (address / identifier) ​​and a target IP address for UL traffic in the URSP rules. In other examples, the URSP rules may use other combinations of traffic descriptors.

[0178] When the UE is determining how to route data traffic (for a requesting application), the UE may compare / match the received information about the device (from the request for UL data traffic) with the "source descriptor" (i.e., identified information) of each of the multiple URSP rules. The applicable URSP rule of the multiple URSP rules will be the URSP rule that matches the information about the application. In this way, the UE selects the applicable URSP rule for the received request.

[0179] Each URSP rule may include a routing selection descriptor (RSD). The UE may utilize the RSD of the determined URSP rule in order to determine the routing of the data traffic.

[0180] When the UE has determined the applicable URSP rules and the associated RSD, the UE can determine whether there is an existing PDU session that has been established and matches the RSD. If there is an existing PDU session that matches the RSD, the UE can utilize the PDU session to route data traffic. In other examples, when there is no established PDU session, the UE will establish a new PDU session. Thereafter, the UE may perform QoS mapping for the PDU session (whether new or pre-established) using at least one QoS rule. The QoS rules may have been provided to the UE via the SMF. In other examples, the QoS rules are provided via other suitable NFs.

[0181] The "source descriptor" (as a service descriptor) contains identification information of a device that is using the UE (acting as a PEGC) as a gateway to access the data network via 5GS. In addition, the "source descriptor" may also include network information (e.g., SSID) where the data service is received.

[0182] The source descriptor can contain one or more of the following information:

[0183] i) A unique identification of the device that is using the UE as a gateway. The unique identification may include a Media Access Control (MAC) address of the device. The unique identification may include a source Internet Protocol (IP) address / port. The unique identification may include a Bluetooth identification. In other examples, the unique identification may include any unique identifier provided to the PINE within the PIN. The unique identification of the device may be received by the UE during authentication of the PINE. In this way, the UE will know the unique identification of the device.

[0184] ii) Identification of the PIN. The identification of the PIN may include a service set identifier (SSID) of an access point supported by the PEGC UE. The identification of the PIN may include any other unique identifier for identifying the PIN. In some examples, URSP rules may be provided only for the PIN. For example, if the PEGC UE is used for different PINs and data traffic from different PINs is routed differently, it may not be necessary to identify the PIN (identifying the PIN in the source descriptor is sufficient).

[0185] iii) Uniquely identifies the PIN and / or PINE and / or any other information of the device that is using the UE as a GW (PEGC).

[0186] iv) Any other information that uniquely identifies the application running on the PINE (or device) behind the UE acting as a GW (PEGC).

[0187] for Figure 5 The signaling provided in , assumes that the PCF has information available to include the "source descriptor" information in the service descriptor of the URSP rules for the GW (PEGC) UE. As part of the UE policy, this information can be made available to the PCF via provision in the UDR. In other examples, this information can be made available to the PCF by an application function (AF) using a mechanism that provides "application guidance for URSP determination" to the PCF. In this example, the AF represents the user who manages the PIN: via this AF, the user can manage the PIN and associate the PIN or PINE with a dedicated DNN / S-NSSAI provided by the operator.

[0188] Some UEs from older versions may not support "Source Descriptor" as a traffic descriptor component in URSP rules. It may be advantageous for the network to know whether a particular UE supports "Source Descriptor".

[0189] Figure 6 Another example signaling diagram between user equipment and network entities is shown. In this example, the UE communicates with AMF, PCF, UDR, NEF and AF.

[0190] In S600a, the AF provides at least one URSP including "source descriptor" information to the PCF.

[0191] In S600b, at the UDR, the UE policy includes "source descriptor" information.

[0192] In S601, the UE provides an indication to the AMF that the UE supports the "source descriptor" service descriptor in the URSP rule. The indication may be provided in a registration request message. The UE may receive a response message from the AMF.

[0193] In an example, the indication may be an indirect indication. For example, the UE may indicate that it is a PEGC UE.

[0194] In S602, the AMF forwards the indication to the PCF. The indication may be forwarded to the PCF during the UE policy establishment process. Through the indication, the PCF knows that the PCF may include a "source descriptor" in the service descriptor of the URSP rule. The PCF may include a "source descriptor" based on the UE's policy subscription data and / or "AF guidance for URSP determination".

[0195] In S603, the PCF provides a response message to the AMF.

[0196] In S604, after providing the indication in S602, the PCF may determine that a UE policy is to be provided to the UE. If the UE has already been configured with a UE policy, this may be an update process. This will trigger the following: Figure 5 The signaling shown in .

[0197] Figure 6 The signaling means that the UE is able to provide an indication of the new URSP capability of supporting "source descriptor" to the AMF in a message (e.g., a registration request). The AMF includes this UE indication in the UE policy control establishment request to the PCF. The PCF then decides to provide at least one URSP rule containing the new "source descriptor" service descriptor based on the UE policy information available to the PCF (assuming that the indication from the UE is that the UE supports the new URSP service descriptor component).

[0198] One or more of the above examples allow a UE (configured as a PEGC) to determine how to route data traffic from applications running on a PINE device behind the UE in an efficient manner. Data traffic can be routed from the PINE so that minimal resources are used. Data traffic can be routed from the PINE so that QoS rules are adhered to. Data traffic can be routed so that the correct DNN and / or S-NSSAI is used for the PINE that is requesting UL data traffic. In addition, the network knows whether a particular UE can support the "source descriptor" component in the URSP rule. In this way, the network knows not to provide URSP rules with "source descriptors" to UEs that do not support "source descriptors". This saves resources at the network by not making unnecessary transmissions from the network to the UE.

[0199] Figure 7 An example method flow performed by an apparatus is shown. The apparatus may be included in a user equipment. The apparatus may be included in a terminal. The apparatus may be included in a device configured as a gateway. The apparatus may be included in a PEGC.

[0200] In S701 , the method includes: receiving at least one user equipment routing policy rule from a core network entity, wherein the at least one user equipment routing policy rule includes a component having information associated with a source device capable of requesting a data service via the user equipment.

[0201] In S703 , the method includes: receiving a request for an uplink data service from an application of a source device, wherein the request includes information about the source device.

[0202] In S705 , the method includes determining how to route data traffic from the application using at least one user equipment routing policy rule and based on information about the source device received in the request to determine a route.

[0203] In S707, the method includes: routing the data service according to the determined route.

[0204] Figure 8 An example method flow performed by an apparatus is shown. The apparatus may be included in a core network entity. The apparatus may be included in a network function. The apparatus may be included in a PCF.

[0205] In S801, the method includes: determining at least one user equipment routing policy rule for a user equipment, wherein the at least one user equipment routing policy rule includes a component having information associated with a source device capable of requesting a data service via the user equipment.

[0206] In S803, the method includes: providing at least one user equipment routing policy rule to the user equipment.

[0207] Fig. 9 Schematic representations of non-volatile storage media 900a (e.g., a computer compact disk (CD) or digital versatile disk (DVD)) and 900b (e.g., a universal serial bus (USB) memory stick) storing instructions and / or parameters 902 that, when executed by a processor, allow the processor to perform Figure 7 or Figure 8 One or more steps of a method.

[0208] It is noted that while exemplary embodiments are described above, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0209] Therefore, these examples may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, however, the embodiments are not limited thereto. Although various embodiments may be shown and described as block diagrams, flow charts, or using some other graphical representation, it is understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0210] These examples can be implemented by computer software (which is stored in a memory and can be executed by at least one data processor of the entity involved) or hardware or a combination of software and hardware. In addition, it should be noted at this point that any process can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software can be stored on a physical medium such as a memory chip, or a storage block implemented in a processor, a magnetic medium (such as a hard disk or a floppy disk), and an optical medium (such as a DVD and its data variant CD).

[0211] The data processor may be of any type suitable for the local technical environment, and may include, by way of non-limiting example, one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), gate level circuits, and processors based on multi-core processor architectures.

[0212] Alternatively or additionally, some examples may be implemented using a circuit. The circuit may be configured to perform one or more functions and / or method steps described previously. The circuit may be arranged in a base station and / or a communication device.

[0213] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) a pure hardware circuit implementation (e.g., an implementation in a pure analog and / or digital circuit); (b) a combination of hardware circuits and software, such as: (i) a combination of analog and / or digital hardware circuits with software / firmware, and (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory, which work together to enable an apparatus (e.g., a communication device or a base station) to perform the various functions previously described; and (c) a hardware circuit and / or processor, such as a microprocessor or a portion of a microprocessor, which requires software (e.g., firmware) to operate, but the software may not be present when it is not required for operation.

[0214] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term "circuitry" also covers, for example, an integrated device.

[0215] The above description is provided by way of exemplary and non-limiting examples, i.e., a comprehensive and informative description of some embodiments. However, various modifications and variations may become apparent to those skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications to the teachings still fall within the scope as defined in the appended claims.

Claims

1. A device in a user equipment, the device comprising: means for receiving at least one user equipment routing policy rule from a core network entity, wherein the at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data services via the user equipment; means for receiving a request for uplink data traffic from an application of the source device, wherein the request includes information about the source device; means for determining how to route the data traffic from the application using the at least one user equipment routing policy rule and based on information about the source device received in the request to determine a route; and Means for routing the data traffic according to the determined route.

2. The device according to claim 1, wherein: For the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identification of at least one source device; An identifier of a network associated with the user equipment.

3. The device according to claim 2, wherein: At least one of the following: The identity of the source device is an identity of a personal Internet of Things network unit; and The network identifier is the identifier of the personal Internet of Things network.

4. The device according to claim 2 or claim 3, wherein: The identification of the source device includes at least one of the following: a media access control address, a source Internet Protocol address, a port number, a Bluetooth identification, a unique identification of the personal Internet of Things network unit, and a network access identifier received by the user device after the source device has been authenticated.

5. The device according to claim 3, wherein: The identification of the personal Internet of Things network includes at least one of the following: a service set identifier of the access point, and a unique identification of the personal Internet of Things network.

6. The device according to any one of claims 1 to 5, wherein: The at least one user equipment routing selection policy rule comprises a plurality of user equipment routing selection policy rules, and wherein the means for determining comprises: means for comparing i) information about the source device received in the request with ii) corresponding information within the component of each of the plurality of user equipment routing policy rules; and Means for selecting a user equipment routing policy rule from among the plurality of user equipment routing policy rules based on the comparing.

7. The device according to claim 6, wherein: The route is determined using a routing descriptor associated with the selected user equipment routing policy rule.

8. The device according to claim 7, wherein: The device comprises: means for determining whether there is an existing protocol data unit session that has been established and that complies with said routing descriptor; and Means for routing the data traffic using the protocol data unit session when there is an existing protocol data unit session that complies with the routing descriptor.

9. The device according to claim 8, wherein: The device comprises: Means for performing quality of service mapping for the protocol data unit session using at least one quality of service rule.

10. The device according to any one of claims 1 to 9, wherein: The device comprises: Means for providing an indication to another core network entity that the user equipment supports user equipment routing policy rules including a component having information associated with a source device capable of requesting data traffic via the user equipment.

11. The device according to claim 10, wherein: The indication is provided to the other core network entity within a registration request message.

12. An apparatus for a core network entity, the apparatus comprising: means for determining at least one user equipment routing policy rule for a user equipment, wherein the at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data services via the user equipment; and Means for providing said at least one user equipment routing policy rule to said user equipment.

13. The device according to claim 12, wherein: For the at least one user equipment routing selection policy rule, the information associated with the source device includes at least one of the following: an identification of at least one source device; An identifier of a network associated with the user equipment.

14. The device according to claim 13, wherein: At least one of the following: The identity of the source device is an identity of a personal Internet of Things network unit; and The network identifier is the identifier of the personal Internet of Things network.

15. The device according to claim 13 or claim 14, wherein: The identification of the source device includes at least one of the following: a media access control address, a source Internet Protocol address, a port number, a Bluetooth identification, a unique identification of the personal Internet of Things network unit, and a network access identifier received by the user device after the source device has been authenticated.

16. The device according to claim 15, wherein: The identification of the personal Internet of Things network includes at least one of the following: a service set identifier of the access point, and a unique identification of the personal Internet of Things network.

17. The device according to any one of claims 12 to 16, wherein: The means for determining includes means for determining the at least one user device routing policy rule based on input received from an application function associated with a personal Internet of Things network associated with the user device.

18. The device according to any one of claims 12 to 17, wherein: The device comprises: Means for receiving an indication from the user equipment that the user equipment supports user equipment routing policy rules including a component having information associated with a source device capable of requesting data traffic via the user equipment.

19. The device according to any one of claims 12 to 18, wherein: The device comprises: Means for using the received indication to trigger determining the at least one user equipment routing policy rule including the component having information associated with the source device capable of requesting data service via the user equipment.

20. A method performed by a user equipment, the method comprising: receiving at least one user equipment routing policy rule from a core network entity, wherein the at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data services via the user equipment; receiving a request for an uplink data service from an application of the source device, wherein the request includes information about the source device; determining how to route the data traffic from the application using the at least one user equipment routing policy rule and based on the information about the source device received in the request to determine a route; and The data traffic is routed according to the determined route.

21. A method performed by a core network entity, the method comprising: determining at least one user equipment routing policy rule for a user equipment, wherein the at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data services via the user equipment; and The at least one user equipment routing policy rule is provided to the user equipment.

22. A computer program comprising computer executable instructions which, when executed on one or more processors, perform: receiving at least one user equipment routing policy rule from a core network entity, wherein: The at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data traffic via the user equipment; receiving a request for an uplink data service from an application of the source device, wherein the request includes information about the source device; determining how to route the data traffic from the application using the at least one user equipment routing policy rule and based on the information about the source device received in the request to determine a route; and The data traffic is routed according to the determined route.

23. A computer program comprising computer executable instructions which, when executed on one or more processors, perform: At least one user equipment routing policy rule is determined for the user equipment, wherein: The at least one user equipment routing policy rule comprises a component having information associated with a source device capable of requesting data traffic via the user equipment; as well as The at least one user equipment routing policy rule is provided to the user equipment.

Images