Influence of AF on policy evaluation

Abstract

According to one aspect, the present invention provides a method of operating a Policy and Charging Function, PCF, (202), in a communications network to enable Quality of Service, QoS, changes for a User Equipment, UE. The method comprises: sending (601) a request for policy data and / or application data for the UE to a Unified Data Repository, UDR, in the communication network; receiving (603), from the UDR (203), information identifying the UE and one or both of a start time of a QoS change of the UE and a duration of a QoS change of the UE; and sending (605) a message to a session management function, SMF (201), the message comprising (i) a first event trigger of QoS change based on the start time and / or duration; or (ii) QoS of the SMF (201) for the session sent after the start time or at the expiration of the duration.

Description

Technical Field

[0001] The present disclosure relates to one or more of the 5th Generation (5G) Core (5GC), Application Function (AF), Network Exposure Function (NEF), Policy and Charging Function (PCF), Network Capability Exposure, Policy and Charging Control, and Reporting of Presence Reporting Area (PRA). The main use case described herein involves changing the Quality of Service (QoS) policy of a User Equipment (UE) based on a request from an external party. Background Art

[0002] In 5th generation (5G) networks, a service-based architecture has been introduced for the core network, which is decomposed into communication services called Network Functions (NFs). Figure 1 A 5G system reference architecture 101 is shown, which shows the service-based interface used within the control plane (CP). It should be understood that not all types of NF instances / NF services are depicted. The service-based interface is represented in Nxyz format and the point-to-point interface is represented in Nx format. Figure 1 The reference architecture 101 shown includes the following types of NF instances: Network Slice Selection Function (NSSF) 102 with Nnssf interface, Network Exposure Function (NEF) 103 with Nnef interface, Network Repository Function (NRF) 104 with Nnrf interface, Policy Control Function (PCF) 105 with Npcf interface, Unified Data Repository (UDR) 106 with Nudr interface, Application Function (AF) 107 with Naf interface, Authentication Server Function (AUSF) 108 with Nausf interface, Access and Mobility Management Function (AMF) 109 with Namf interface, Session Management Function (SMF) 110 with Nsmf interface, Service Communication Agent (SCP) 111 with Nscp interface and Unified Data Management (UDM) 116 with Nudm interface.

[0003] AMF 109 has an N1 interface to user equipment (UE) 112, and an N2 interface to radio access network (AN) 113 (which may be a radio AN, RAN). SMF 110 has an N4 interface to user plane function (UPF) 114. The interface between R (AN) 113 and UPF 114 is an N3 interface, and the interface between UPF 114 and data network (DN) 115 is an N6 interface.

[0004] The 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 (System Architecture for 5G System (5GS); Phase 2) v17.4.0, clause 5.2 defines a framework for exposing network functions to the outside world via the Network Exposure Function (NEF). This includes exposing the policy / charging capabilities of the user equipment (UE) based on requests from external parties.

[0005] 3GPP TS23.503 (Policy and Charging Control Framework for 5G System (5GS); Stage 2) v17.4.0 clause 4.2.6 specifies the following non-session management related network capability exposure from the policy control function of the NEF:

[0006] Packet Flow Description (PFD) management

[0007] Negotiation of future background data transfer (BDT)

[0008] Apply a previously negotiated background data transfer policy to a UE or UE group

[0009] Traffic steering control for traffic diversion affected by application function (AF)

[0010] · Provision of service-specific parameters for vehicle-to-everything (V2X) communications

[0011] 5G virtual network (VN) group management

[0012] Service-specific parameter provisioning for Proximity Services (ProSe) functionality

[0013] Service specific parameter provisioning for time synchronization services

[0014] The above process allows the AF to provide policy requirements for specific use cases (BDT, traffic steering, 5G VN groups, ProSe, etc.) via the NEF, for any existing or future protocol data unit (PDU) sessions for multiple UEs or any UE.

[0015] After relevant validation (and possible parameter mapping) of the AF request, the NEF stores the request received from the AF into the selected Unified Data Repository (UDR) instance as a data subset of application data. The PCF subscribes to receive notifications about such AF request information from the UDR and considers the policy requirements received from the AF when making policy decisions for existing and future related PDU sessions.

[0016] A Presence Reporting Area (PRA) is specified as a UE entering a geographical area defined, for example, by a list of radio cell identifiers. The PRA can be used to evaluate policies and determine different outcomes by the PCF, such as zero billing when a UE enters a PRA or leaves a PRA. The PCF can request a Session Management Function (SMF) to receive a notification when a given UE / user enters or leaves an area / PRA. This can be done with the event PRA_CHG (PRA Change).

[0017] Furthermore, a Time Of Day (ToD) policy may be used alone or in conjunction with PRA, such that the PCF may instruct the SMF to re-authorize a data session when a time and date is reached, for example, upgrading the QoS when a certain point in time is reached and during a specific duration.

[0018] 3GPP has defined the possibility to provide Operator Specific Data (OSD) as part of the PCF policy subscription data. The OSD is statically pre-configured in the UDR by the operator (via the configuration system) and can also be modified by the PCF. It should be noted that the content and format / coding of the Operator Specific Data and Operator Specific Data Sets are not constrained by the standard. Summary of the invention

[0019] There are certain challenges.

[0020] Currently, 3GPP specifications allow an external party (A)F to provide policy requirements for specific use cases via the NEF, as described above. However, network operators require support for additional use cases that are not currently covered by 3GPP.

[0021] In a first example, a network operator may need functionality associated with users being able to purchase or obtain a data rate boost ("turbo-speed"). When a user purchases turbo-speed, they can log into a web page associated with the network operator and then decide when to start the service ((higher) speed / (higher) bit rate) and the duration of the turbo-speed. Therefore, the network operator needs to be able to modify the ToD policy in order to dynamically configure the time window for upgrading the QoS after the user interacts with their web service.

[0022] In a second example, a network operator may want the possibility of having a "local SIM" (Subscriber Identity Module) which is intended to provide data connectivity only when the owner of the SIM (e.g. a hospital employee) moves within certain areas (e.g. a hospital). Thus, data connectivity is allowed only when the user enters or is located in those geographical areas. Otherwise, if they are outside the associated "home" geographical area, data connectivity is prohibited or restricted (e.g. for certain services, lower QoS, additional charges, etc.). As in the first example, this second example enables the network operator to request the possibility of allocating a PRA to a specific UE in a dynamic manner, the PCF evaluating the policy based on this / these PRAs. Again, there is no standard or standardized mechanism for this.

[0023] Typically, there is no mechanism for external parties to provide specific AF information to influence policy decisions that is not currently included in the policy subscription data or associated with the specific use cases described above. Extensions to the policy subscription data stored in the UDR (e.g., vendor-specific information, operator-specific information) are not intended to be managed by external parties (i.e., application servers, verticals), but rather by the network operator Operational Support System (OSS) / Business Support System (BSS) provisioning system.

[0024] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges.

[0025] The Application Server (AS) / AF (external party) provides the NEF with a set of specific AF information that can be used to influence policy decisions for a UE, a group of UEs, or any UE. The NEF may store the received AF information in the UDR. The content, meaning, and format / encoding of the container of such AF-specific information may be the result of an agreement between the AS / AF and the network operator (NEF / PCF).

[0026] For existing PDU sessions, the PCF can subscribe to receive notifications about such AF-specific information from the UDR. For new PDU sessions, the PCF can read the AF-specific information from the UDR if it is not already available in the local cache. The PCF can then take the AF-specific information into account when making policy decisions.

[0027] The implementation of the specific use case outlined in the two examples above would be as follows.

[0028] Overall solution: Policy data can be exposed via the NEF (Network Exposure Function) by extending the Nnef_Service_Parameter application programming interface (API), which will allow it to be stored as application data in the UDR (e.g., in a new resource such as: / application-data / policy-influence / af-specific-data) or directly as policy data (e.g., in a new resource such as: / policy-data / af-specific-data). This data can be stored in the UDR and retrieved by the NEF so that it can be evaluated in the PCF policy. The PCF can then determine whether to upgrade the QoS (e.g., turbo-speed) or allow data connectivity (local SIM).

[0029] 1) An AF (e.g. a web application server that can purchase a "turbo speed" service) can call the Nnef_Service_Parameter API and include the new "AF impact on policy data" element, e.g. containing a start time and duration, to enable turbo-speed service for users who requested it.

[0030] 2) NEF can store new "AF impact on policy data" in UDR as part of application data or as part of policy data. This can be determined by NEF based on new local policies or enhanced Network Repository Function (NRF) discovery.

[0031] 3) PCF can obtain information from UDR and take it into account to evaluate the policy.

[0032] The techniques in this disclosure enable an external party AF / AS to influence policy / charging control decisions based on predefined data sets and business logic resulting from an agreement between the external party (AS / AF) and the network operator (NEF / PCF).

[0033] The above solution can be used to satisfy both network operator use case examples, since the ultimate goal of the network operator in these examples is to have the AF influence the policy evaluation performed by the PCF, either by setting a new ToD policy (e.g., turbo-speed button) or by setting a PRA policy (e.g., local SIM).

[0034] Certain embodiments may provide one or more of the following technical advantages: In particular, embodiments provide a new mechanism to allow an authorized AF to influence the policy evaluation performed by a PCF in a dynamic manner, ie, without requiring the network operator to statically provision the information via its provisioning system.

[0035] This new mechanism may enable an external third party AF / AS to define new use cases for policy and charging control based on previous agreements between the external party (AS / AF) and the network operator (NEF / PCF).

[0036] Various aspects and embodiments are described herein.

[0037] In particular, according to a first aspect, a method of operating an AF to implement a QoS change of a UE is provided. The method comprises sending a message to a NEF in a communication network, the message identifying the UE and one or both of a start time of the QoS change of the UE and a duration of the QoS change of the UE.

[0038] According to a second aspect, a method of operating an NEF in a communication network to implement a QoS change for a UE is provided. The method comprises: receiving a message from an AF identifying the UE and one or both of a start time of the QoS change for the UE and a duration of the QoS change for the UE; and sending information identifying the UE and one or both of the start time and duration to a UDR in the communication network.

[0039] According to a third aspect, a method for operating a UDR in a communication network to implement a QoS change for a UE is provided. The method comprises: receiving information identifying the UE and one or both of a start time of the QoS change for the UE and a duration of the QoS change for the UE from a NEF; storing the received information; and in response to a request from a PCF for policy data and / or application data for the UE, sending information identifying one or both of a start time and a duration of the QoS change for the UE to a PCF.

[0040] According to a fourth aspect, a method for operating a PCF in a communication network to implement a QoS change for a UE is provided. The method comprises: sending a request for policy data and / or application data of the UE to a UDR in the communication network; receiving information identifying the UE and one or both of a start time of a QoS change for the UE and a duration of a QoS change for the UE from the UDR; and sending a message to an SMF, the message comprising (i) a first event trigger for a QoS change based on the start time and / or duration; or (ii) a QoS for a session sent by the SMF after the start time or at the expiration of the duration.

[0041] According to a fifth aspect, a method for operating an SMF in a communication network to implement a QoS change for a UE is provided. The method comprises: receiving a message from a PCF in the communication network, the message comprising a first event trigger for a QoS change based on a start time of the QoS change for the UE and / or a duration of the QoS change for the UE; establishing a data session for the UE and monitoring the occurrence of the first event trigger; after the occurrence of the first event trigger, sending a request to the PCF to reauthorize the data session; and receiving updated policy data of the UE implementing the QoS change from the PCF.

[0042] According to a sixth aspect, there is provided a method of operating an AF to implement data session control based on the location of a UE. The method comprises sending a message to a NEF in a communication network identifying the UE and a geographical area in which data sessions for the UE are allowed or blocked.

[0043] According to a seventh aspect, there is provided a method of operating a NEF in a communication network to implement data session control based on the location of a UE. The method comprises: receiving a message from an AF identifying a UE and a geographical area in which a data session of the UE is allowed or blocked; and sending information identifying the UE and the geographical area to a UDR in the communication network.

[0044] According to an eighth aspect, there is provided a method of operating a UDR in a communication network to implement data session control based on the location of a UE. The method comprises: receiving information identifying a UE and a geographical area in which a data session of the UE is allowed or blocked from a NEF; storing the received information; and in response to a request for policy data and / or application data of the UE from a PCF, sending the information identifying the geographical area to a PCF.

[0045] According to a ninth aspect, a method for operating a PCF in a communication network to implement data session control according to a location of a UE is provided. The method comprises: sending a request for policy data and / or application data of a UE to a UDR in the communication network; receiving information identifying the UE and a geographical area in which a data session of the UE is allowed or blocked from the UDR; and sending a message including a first event trigger for controlling a data session of the UE to an SMF.

[0046] According to the tenth aspect, a method for operating an SMF in a communication network to implement data session control according to the location of a UE is provided. The method comprises: receiving a message from a PCF in the communication network, the message comprising a first event trigger for controlling a data session according to the location of the UE, wherein the first event trigger is triggered if the UE moves into or out of an indicated geographical area; monitoring the location of the UE for the occurrence of the first event trigger; after the occurrence of the first event trigger, sending a request for policy data for the data session to the PCF, wherein the request indicates whether the UE is inside or outside the geographical area; and receiving updated policy data for the UE from the PCF, the updated policy data indicating whether the data session of the UE is allowed.

[0047] According to the eleventh aspect, a computer program product is provided, comprising a computer-readable medium having a computer-readable code embodied therein, wherein the computer-readable code is configured to, when executed by a suitable computer or processor, cause the computer or processor to perform a method according to any one of the first to tenth aspects.

[0048] According to a twelfth aspect, a network node is provided, wherein the network node is configured to execute the method according to any one of the first aspect to the tenth aspect.

[0049] According to a thirteenth aspect, there is provided a network node comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the network node is operable to perform the method according to any one of the first to tenth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which:

[0051] Figure 1 A 5G system reference architecture is shown, which shows the service-based interfaces used within the control plane;

[0052] Figure 2 is a signaling diagram illustrating signaling between different network functions according to the disclosed technology in order to implement QoS changes through an external AF;

[0053] Figure 3 is a flow chart illustrating a method of operating an AF to implement QoS changes for a UE;

[0054] Figure 4 is a flow chart illustrating a method of operating a NEF to implement QoS changes for a UE;

[0055] Figure 5is a flow chart illustrating a method of operating a UDR to implement QoS changes for a UE;

[0056] Figure 6 is a flow chart illustrating a method of operating a PCF to implement QoS changes for a UE;

[0057] Figure 7 is a flow chart illustrating a method of operating an SMF to implement QoS changes for a UE;

[0058] Figure 8 is a signaling diagram illustrating signaling between different network functions according to the disclosed technology in order to enable or disable data connectivity according to the geographical area in which the UE is located;

[0059] Fig. 9 is a flow chart illustrating a method of operating an AF to implement data session control according to the location of a UE;

[0060] Fig.10 is a flow chart illustrating a method of operating a NEF to implement data session control according to the location of a UE;

[0061] Fig.11 is a flow chart showing a method of operating a UDR to implement data session control according to a location of a UE;

[0062] Fig.12 is a flow chart showing a method of operating a PCF according to a location of a UE to implement data session control;

[0063] Fig.13 is a flow chart showing a method of operating an SMF to implement data session control according to a location of a UE;

[0064] Fig.14 is a simplified block diagram of a network node according to some embodiments; and

[0065] Fig.15 is a block diagram illustrating a virtualized environment in which functionality implemented by some embodiments may be virtualized. DETAILED DESCRIPTION

[0066] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings.The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0067] As described above, the solution provided in the present disclosure enables an external party AF / AS to influence policy / charging control decisions based on predefined data sets and business logic generated by the agreement between the external party (AS / AF) and the network operator (NEF / PCF).

[0068] In short, the disclosed solution extends the Nnef_Service_Parameter application programming interface (API) so that policy data can be exposed via the NEF, which will allow the NEF to store it as application data in the UDR (e.g., in a new resource such as: / application-data / policy-influence / af-specific-data), or directly as policy data (e.g., in a new resource such as: / policy-data / af-specific-data). This data can be stored in the UDR and retrieved by the NEF so that it can be evaluated in the PCF policy. The PCF can then determine the appropriate policy modifications, such as upgraded QoS, or allowing data connections in specific geographic locations.

[0069] Figure 2 is a signaling diagram illustrating signaling between different network functions according to the disclosed technology in order to implement QoS changes through an external AF. In this example, the network operator or other external party provides functionality related to users who can purchase or obtain a data rate boost ("turbo-speed"). In particular, when a user purchases turbo-speed / speed boost / higher data rate, they can log into a web page associated with the network operator and then decide when to start the service ((higher) speed / (higher) bit rate), as well as the duration of the (higher) speed. Therefore, the external party / network operator needs to be able to modify the ToD policy in order to dynamically configure the time window for upgrading the QoS after the user interacts with its web service.

[0070] Figure 2 Signaling between SMF 201, PCF 202, UDR 203, NEF 204 and AF 205 is shown.

[0071] In step 211, AF 205 sends a message to NEF 204 that identifies the affected UE(s), indicates when / how long a QoS change is needed, and optionally, what the QoS upgrade is (e.g., a specific data rate requested or required, a general QoS level, such as "high", etc.). This information is generally referred to herein as AF impact policy data (i.e., data from AF 205 for impact policy) or AflnfluencePolicyData. In some embodiments, the message sent by AF 205 in step 211 may call the Nnef_Service_Parameter API and may be a Nnef_ServiceParameterCreate message.

[0072] In step 212, NEF 204 decides that AF impact policy data will be stored in UDR 203, and in step 213, NEF 204 sends a message to UDR 203 to store AF impact policy data in UDR 203. The target resource / storage (e.g., / application data or / policy data) in UDR 203 can be based on a new local policy in NEF 204, or based on a response from NRF when discovering UDR (depending on whether UDR service is discovered for application data and AF impact on policy data subset). The message sent by NEF 204 to UDR 203 can be a Nudr_ApplicationData_Create message, and can include AF impact policy data received from AF 205.

[0073] In step 214, a new session management (SM) session for the UE is to be established, and in step 215, SMF 201 sends a message to PCF 202 to obtain policy information for the new SM session. The new SM session may be established when the UE attaches to the network and requests a data connection. The message sent by SMF 201 may be a Npcf_SM_PolicyControl_Create message.

[0074] After receiving the request from SMF 201, PCF 202 determines that it needs to read the policy data and application data of the UE stored in UDR 203. In step 216, PCF 202 obtains the policy data from UDR 203, and in step 217, PCF 202 sends a request for the policy and / or application data of the UE to UDR 203. The request may be a Nudr_ApplicationData_Get message.

[0075] In step 218, UDR 203 sends the UE's policy and / or application data to PCF 202. In this embodiment, the policy and application data include the start time and / or duration of enhanced QoS, and may also provide information related to enhanced QoS, especially when different levels of QoS upgrades are available. This data may be sent in a Nudr_ApplicationData_Get_Rsp message.

[0076] In step 219, based on the start time / duration information, the PCF 202 updates the policy in the SMF 201 with the applicable QoS, and includes a revalidation event triggered by the arrival of the start time or the expiration of the duration (if the QoS upgrade starts immediately, in which case the QoS may be downgraded upon revalidation (e.g., falling back to the original QoS)). The occurrence of the event (e.g., the start time occurs or the duration expires) will cause the SMF 201 to request reauthorization / revalidation of the SM session from the PCF 202, allowing the PCF 202 to change the required QoS. This is shown by the PCF 202 sending a message to the SMF 201 in step 220, which indicates the QoS to be applied and the time when the PCF 202 will revalidate the session. The QoS indicated to the SMF 201 at this stage may be the upgraded QoS (if the upgrade will start immediately, for example, for a specified "duration"), or the "standard" QoS (if the upgrade will start at a later time ("start time")). The revalidation time may be equal to the start time plus the duration (if the upgraded QoS session has not yet started and it will start at a later time). The message sent in step 220 may be a Npcf_SM_PolicyControl_Create response message (ie, a response to the message sent in step 215).

[0077] When the revalidation time expires / is met (step 221), SMF 201 sends a message 222 indicating the expiration to PCF 202 and requests reauthorization / revalidation of the session. The message 222 may be an Npcf_SM_PolicyControl_Update message and may indicate the occurrence of an event trigger. In step 223, PCF 202 evaluates one or more policies and determines the applicable QoS. If the applicable QoS is an upgrade, PCF 202 may also determine a new revalidation time. This information is transmitted to SMF 201 in message 224. Message 224 may be an Npcf_SM_PolicyControl_Update response message and may indicate the QoS and, optionally, a new event trigger for requesting revalidation of the session.

[0078] In the right Figure 2 In a first alternative to the method shown, instead of the SMF 201 monitoring the occurrence of the start time or the expiration of the duration, the PCF 202 can monitor this directly and signal the required QoS to the SMF 201 at the appropriate time. In this case, the PCF 202 does not need to include an event trigger in the message 220 (or message 224).

[0079] In the right Figure 2In a second alternative to the method shown, PCF 202 may signal an event trigger to SMF 201 in message 220 as described above, and also include (in message 220) the QoS to be used after the event trigger occurs. In this alternative, SMF 201 monitors the occurrence of the event trigger and then automatically applies the QoS indicated by SMF 201 (in this case, messages 222 and 224 are not required).

[0080] Figure 3 is a flow chart illustrating a method of operating an AF 205 to implement a QoS change for a UE. The method may be performed by an AF node 205 or a general network node configured to operate as an AF 205. The AF / network node 205 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0081] In step 301, AF 205 sends a message to NEF 204. The message identifies the UE and one or both of: (i) the start time of the UE's QoS change, and (ii) the duration of the UE's QoS change. The message may be Figure 2 Message 211.

[0082] The message may also include an indication of a start time and / or duration for the QoS change to be implemented.The QoS change may be an increase in the data rate provided by the communications network to the UE.

[0083] In some cases, the QoS change is performed in response to a request sent from a user of the UE to the AF 205. Figure 3 The method in .

[0084] Figure 4 2 is a flow chart illustrating a method of operating NEF 204 to implement QoS changes for a UE. The method may be performed by NEF node 204 or a general network node configured to operate as NEF 204. NEF / network node 204 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0085] In step 401, NEF 204 receives a message from AF 205. The message identifies the UE and one or both of: (i) the start time of the UE's QoS change and (ii) the duration of the UE's QoS change. The message may be Figure 2Message 211.

[0086] In step 403, NEF 204 sends information identifying the UE and one or both of the start time and duration to UDR 203 in the communication network. The sending of this information may correspond to Figure 2 Message 213 in.

[0087] Figure 5 2 is a flow chart illustrating a method of operating a UDR 203 to implement a QoS change for a UE. The method may be performed by a UDR node 203 or a general network node configured to operate as a UDR 203. The UDR / network node 203 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0088] In step 501, UDR 203 may receive information identifying a UE for which QoS is to be changed, and one or both of: (i) a start time of the UE's QoS change and (ii) a duration of the UE's QoS change. The information is received from NEF 204. The information may correspond to Figure 2 Message 213 in.

[0089] In step 503, UDR 203 stores the received information.

[0090] In step 505, UDR 203 sends information identifying one or both of the start time and duration of the UE's QoS change to PCF 202 in response to the request for the UE's policy data and / or application data from PCF 202. The sending of this information may correspond to Figure 2 Message 218.

[0091] Figure 6 2 is a flow chart illustrating a method of operating PCF 202 to implement QoS changes for a UE. The method may be performed by PCF node 202 or a general network node configured to operate as PCF 202. PCF / network node 202 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0092] In step 601, PCF 202 sends a request for UE policy data and / or application data to UDR 203. The request may correspond to Figure 2 Message 217.

[0093] In step 603, PCF 202 receives information identifying the UE and one or both of a start time of a QoS change for the UE and a duration of a QoS change for the UE. The information is received from UDR 203. The sending of the information may correspond to Figure 2 Message 218.

[0094] In step 605, PCF 202 sends a message to SMF 201 (e.g., Figure 2 The message includes (i) a first event trigger for QoS change based on the start time and / or duration; or (ii) QoS for the session sent by SMF 201 after the start time or at the expiration of the duration.

[0095] The message sent to the SMF 201 may also include the QoS of the UE applied until the first event trigger occurs.

[0096] In some cases, after receiving a message from SMF 201 indicating that a first event trigger for a QoS change has occurred, PCF 202 sends another message to SMF 201 indicating a changed QoS to be used for the UE. The other message to SMF 201 may include a second event trigger related to the end of the QoS change.

[0097] Figure 7 2 is a flow chart illustrating a method of operating an SMF 201 to implement a QoS change for a UE. The method may be performed by an SMF node 201, or a general network node configured to operate as an SMF 201. The SMF / network node 201 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0098] In step 701, SMF 201 receives a message (e.g., Figure 2 The message 220 in the PCF 202 includes a first event trigger for QoS change, which is based on the start time of the UE's QoS change and / or the duration of the UE's QoS change. The message is received from the PCF 202.

[0099] In step 703, SMF 201 establishes a data session for the UE and monitors the occurrence of a first event trigger.

[0100] In step 705 , which occurs after the first event trigger occurs, the SMF 201 sends a request to the PCF 202 to reauthorize the data session.

[0101] Subsequently, in step 707, SMF 201 receives updated policy data of the UE implementing the QoS change from PCF 202.

[0102] The message received from PCF 202 in step 701 may also include the QoS applied to the user of the established data session until the first event trigger occurs.

[0103] The received update policy data may also include a second event trigger related to the end of the QoS change.

[0104] Figure 8 is a signaling diagram illustrating signaling between different network functions according to the disclosed technology to provide the capability of having a local SIM / UE that provides data connectivity only when the SIM / UE is in a specific geographical area. Data connectivity is then allowed only when the SIM / UE enters or is in that geographical area. Otherwise, if they are outside the associated "home" geographical area, data connectivity is prohibited or restricted (e.g. for certain services, lower QoS, additional charges, etc.). This second example results in the possibility for the network operator to request the allocation of a presence reporting area (PRA) to a specific UE in a dynamic manner, so that the PCF evaluates the policy based on this / these PRAs.

[0105] Figure 8 Signaling between SMF 201, PCF 202, UDR 203, NEF 204 and AF 205 is shown.

[0106] In step 811, the AF 205 sends a message to the NEF 204, which identifies the affected (multiple) UEs and indicates the geographic area in which data connections are allowed (or optionally, indicates the geographic area in which data connections are blocked). In some embodiments, the geographic information may identify one or more cells or base stations of the network to which the policy (data / no data) is to be applied. In some embodiments, the geographic information may be in the form of a set of coordinates that define the boundaries of the geographic area, such as latitude, longitude. The geographic information is generally referred to as AF influence policy data (i.e., data from the AF 205 for influencing the policy) or AflnfluencePolicyData. In some embodiments, the message sent by the AF 205 in step 811 may call the Nnef_Service_Parameter API and may be a Nnef_ServiceParameterCreate message. The geographic area information is in Figure 8 It is represented as "GeoArea" in.

[0107] In step 812, NEF 204 maps the geographic area information received from AF 205 to PRA information, such as a list of affected cells / base stations (e.g., a list of cell IDs). In step 812, NEF 204 decides that AF impact policy data / PRA information will be stored in UDR 203, and in step 813, NEF 204 sends a message to UDR 203 to store AF impact policy data (PRA information) in UDR 203.

[0108] The target resource / storage (e.g. / application data or / policy data) in UDR 203 may be based on a new local policy in NEF 204, or based on a response from NRF when discovering UDR (depending on whether UDR service is discovered for application data and AF impact policy data subset). The message sent by NEF 204 to UDR 203 may be a Nudr_ApplicationData_Create message, and may include AF impact policy data received from AF 205.

[0109] In step 814, a new session management (SM) session for the UE is to be established, and in step 815, SMF 201 sends a message to PCF 202 to obtain policy information for the new SM session. A new SM session may be established when the UE is attached to the network and requests a data connection. The message sent by SMF 201 may be a Npcf_SM_PolicyControl_Create message.

[0110] After receiving the request from SMF 201, PCF 202 determines in step 816 that it needs to read the policy data and application data of the UE stored in UDR 203. In step 816, PCF 202 obtains the policy data from UDR 203, and in step 817, PCF 202 sends a request for the policy and / or application data of the UE to UDR 203. The request may be a Nudr_ApplicationData_Get message.

[0111] In step 818, UDR 203 sends the UE's policy and / or application data to PCF 202. In this embodiment, the policy and application data include PRA information or other forms of geographic information. The data can be sent in a Nudr_ApplicationData_Get_Rsp message.

[0112] In step 819, based on the PRA / other geographical information, PCF 202 updates the policy in SMF 201 to include an event triggered by a change in the UE's PRA (event = PRA change), and includes the PRA information (or other geographical information). This is shown by PCF 202 sending a message indicating the PRA_CHG event trigger and the PRA information to SMF 201 in step 820. Thus, when the UE enters or leaves a PRA (e.g., when the UE enters any cell in the list), SMF 201 will report to PCF 202. The message sent in step 820 may be an Npcf_SM_PolicyControl_Create response message.

[0113] The reporting by PCF 202 to SMF 201 when the UE enters or leaves the PRA is shown in steps 821-824. In particular, in step 821, the UE is not in the PRA (e.g., the UE is not / no longer camped in a cell that matches one of the cells in the PRA information), and therefore in step 822, SMF 201 may send a message to PCF 202 indicating that the UE is outside the PRA area. The message sent in step 822 may be an Npcf_SM_PolicyControl_Update message, and it may indicate the event that has been triggered, as well as the current state (e.g., the UE is outside the area).

[0114] After receiving message 822, PCF 202 evaluates the policy and determines (in this embodiment) that no data connection (i.e., no PDU session) is allowed when the UE is outside the PRA. In this case, in step 824, PCF 202 sends a message to SMF 201 indicating that any existing data connection will be ended or terminated. The message may be a Npcf_SM_PolicyControl_Update_Rsp message.

[0115] In response to this message, SMF 201 may terminate any data connection with the UE.

[0116] Fig. 9 is a flow chart illustrating a method of operating an AF 205 to implement data session control based on the location of a UE. The method may be performed by an AF node 205 or a general network node configured to operate as an AF 205. The AF / network node 205 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, an optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0117] In step 901, AF 205 sends a message to NEF 204. The message (e.g., Figure 8 The message 811 in identifies the UE and the geographical area in which the UE's data session is allowed or blocked.

[0118] The geographic area may be identified using coordinates and / or by cell and / or base station identifiers.

[0119] Fig.10 2 is a flow chart illustrating a method of operating NEF 204 to implement data session control based on the location of the UE. The method may be performed by NEF node 204 or a general network node configured to operate as NEF 204. NEF / network node 204 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0120] In step 1001, NEF 204 receives a message from AF 205 (eg, Figure 8 811 in the message identifying the UE and the geographical area in which the UE's data session is allowed or blocked.

[0121] In step 1003, NEF 204 sends information identifying the UE and the geographic area to UDR 203 (e.g., Figure 8 813 in the message).

[0122] Fig.11 2 is a flow chart illustrating a method of operating a UDR 203 to implement data session control based on the location of a UE. The method may be performed by a UDR node 203 or a general network node configured to operate as a UDR 203. The UDR / network node 203 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0123] In step 1101, UDR 203 receives information from NEF 204 (e.g., via Figure 8 813 in the message, which identifies the UE and the geographical area in which the UE's data session is allowed or blocked.

[0124] In step 1103, UDR 203 stores the received information.

[0125] In step 1105, UDR 203 sends information identifying a geographic area to PCF 202 in response to a request from PCF 202 for policy data and / or application data of the UE. The sending of this information may correspond to Figure 8 Message 818 in.

[0126] Fig.12 2 is a flow chart illustrating a method of operating PCF 202 to implement data session control based on the location of the UE. The method may be performed by PCF node 202 or a general network node configured to operate as PCF 202. PCF / network node 202 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk, or other storage medium. The computer readable medium may be part of a computer program product.

[0127] In step 1201, PCF 202 sends a request for policy data and / or application data for the UE to UDR 203. The request may correspond to Figure 8 Message 817 in.

[0128] In step 1203, PCF 202 receives information from UDR 203 (e.g., via Figure 8 Message 818 in ), which identifies the UE and the geographical area in which the UE's data session is allowed or blocked.

[0129] In step 1205, PCF 202 sends a message to SMF 201 (e.g., Figure 8 The message 820 in the embodiment includes a first event trigger for controlling a data session of the UE. The first event trigger may be triggered if the UE moves into or out of a geographical area.

[0130] After receiving a message indicating that the first event trigger has occurred from SMF 201, PCF 202 can determine whether to allow the data session based on the location of the UE relative to the geographical area. Then, based on the result of the determination, PCF 202 sends another message to SMF indicating whether the data session is allowed.

[0131] The information received from UDR 203 may include information identifying a geographic area in which the UE is allowed to conduct a data session. In this case, if the UE is located in the geographic area, the data session is determined to be allowed, otherwise the data session is not allowed or the data rate of the data session is to be reduced.

[0132] Optionally, the information received from UDR 203 may include information identifying a geographical area in which the UE is not allowed to conduct a data session. In this case, if the UE is located in the geographical area, it is determined that the data session is not allowed, otherwise it is determined that the data session is allowed.

[0133] Fig.13 is a flow chart illustrating a method of operating SMF 201 to implement data session control according to the location of the UE. The method may be performed by SMF node 201 or a general network node configured to operate as SMF 201. SMF / network node 201 may perform the method in response to executing appropriately formulated computer readable code. The computer readable code may be embodied or stored on a computer readable medium, such as a memory chip, optical disk or other storage medium. The computer readable medium may be part of a computer program product.

[0134] In step 1301, SMF 201 receives a message from PCF 202 (e.g., Figure 8 The message 820 in the embodiment includes a first event trigger for controlling a data session according to a location of the UE. If the UE moves into or out of the indicated geographical area, the first event trigger is triggered.

[0135] In step 1303, SMF 201 monitors the location of the UE for the occurrence of a first event trigger.

[0136] In step 1305, after the first event trigger occurs, SMF 201 sends a request for policy data for the data session to PCF 202. The request may indicate whether the UE is inside or outside the geographical area.

[0137] In step 1307, SMF 201 receives updated policy data for the UE from PCF 202, the updated policy data indicating whether the data session of the UE is allowed.

[0138] Therefore, the technology described in this article can be implemented by one or more network functions (NFs) in the network, such as SMF, PCF, UDR and NEF, as well as an external AF. Fig.14 is a simplified block diagram of a network node 1400 according to some embodiments that can be used to implement the techniques described herein. Any of the SMF, PCF, UDR, NEF, and AF may be implemented as Fig.14 The network nodes shown in .

[0139] The network node 1400 includes a processing circuit (or logic) 1401. It should be understood that the network node 1400 may include one or more virtual machines running different software and / or processes. Therefore, the network node 1400 may include one or more servers, switches, and / or storage devices, or be implemented in one or more servers, switches, and / or storage devices, or be implemented as one or more servers, switches, and / or storage devices, and / or may include a cloud computing infrastructure running software and / or processes.

[0140] The processing circuit 1401 controls the operation of the network node 1400 and can implement the methods described herein with respect to any one of the SMF, PCF, UDR, NEF and / or AF. The processing circuit 1401 may include one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the network node 1400 in the manner described herein. In a specific embodiment, the processing circuit 1401 may include multiple software and / or hardware modules, each of which is configured to perform or is used to perform individual or multiple steps of the methods described herein with respect to the SMF, PCF, UDR, NEF and / or AF.

[0141] The network node 1400 may also include a communication interface 1402. The communication interface 1402 is used to implement communication with other nodes, such as any one or more of the SMF, PCF, UDR, NEF and / or AF. For example, the communication interface 1402 may be configured to transmit and / or receive requests, confirmations, information, data, signals or the like to other nodes. The communication interface 1402 may use any suitable communication technology.

[0142] The processing circuit 1401 may be configured to control the communication interface 1402 to transmit and / or receive requests, acknowledgements, information, data, signals, or the like to other nodes according to the methods described herein.

[0143] The network node 1400 may include a memory 1403. In some embodiments, the memory 1403 may be configured to store program code that can be executed by the processing circuit 1401 to perform the methods described herein with respect to the network node 1400. Alternatively or additionally, the memory 1403 may be configured to store any request, confirmation, information, data, signal, or the like described herein. The processing circuit 1401 may be configured to control the memory 1403 to store such information therein.

[0144] Fig.151500 is a block diagram showing a virtualized environment in which the functions implemented in some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a network function (e.g., SMF, PCF, UDR, NEF and / or AF), a device or equipment, which may include a virtualized hardware platform, a storage device and a network resource. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtualized environments 1500, and the virtualized environment 1500 is managed by one or more of the hardware nodes, such as hardware computing devices operating as access network nodes, wireless devices / UEs or core network nodes. In addition, in an embodiment (e.g., a core network node) in which a virtual node does not require radio connectivity, the node may be fully virtualized.

[0145] Application 1502 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment 1500 to implement some features, functions, and / or benefits of some embodiments disclosed herein.

[0146] Hardware 1504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. Virtualization layer 1506 may present a virtual operating platform that appears to be networked hardware to VMs 1508.

[0147] VM 1508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of instances of virtual devices 1502 may be implemented on one or more of VM 1508, and may be implemented in different ways. Virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV may be used to merge many network device types onto industry standard high-capacity server hardware, physical switches, and physical storage, which may be located in data centers as well as customer premises equipment.

[0148] In the NFV scenario, VMs 1508 can be software implementations of physical machines that run programs, just as if they were executed on physical, non-virtualized machines. Each of the VMs 1508 and the portion of the hardware 1504 on which the VM is executed, whether it is hardware dedicated to the VM and / or hardware shared by the VM with other VMs, forms a separate virtual network element. Still in the NFV scenario, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on the hardware 1504 and correspond to an application 1502.

[0149] Hardware 1504 may be implemented in a standalone network node with general or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger hardware cluster (e.g., such as in a data center or customer premises equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration 1510, which in particular oversees the lifecycle management of application 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations. In some embodiments, a control system 1512 may be used to provide some signaling, which control system 1512 is optionally used for communication between hardware nodes and radio units.

[0150] Although the computing devices (e.g., NFs, network nodes) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any appropriate combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the computing device may include multiple different physical components constituting a single shown component, and functionality may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be partitioned between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0151] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to separate processing circuits or other components of a computing device, but are generally enjoyed by the computing device as a whole and / or by end users and wireless networks.

[0152] The foregoing merely illustrates the principles of the present disclosure. In view of the teachings herein, various modifications and changes to the described embodiments will be apparent to those skilled in the art. It will therefore be appreciated that those skilled in the art will be able to design many systems, arrangements, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and are therefore within the scope of the present disclosure. It will be appreciated by those of ordinary skill in the art that the various exemplary embodiments may be used together or interchangeably with each other.

[0153] References

[0154] 1.3GPP TS29.522 Version 17.5.0: Northbound API for network open functions

[0155] 2.3GPP TS29.122 version 17.5.0: T8 reference point for northbound API

[0156] 3.3GPP TS29.508 Version 17.7.0: 5G system; Unified data management service; Stage 3

Claims

1. A method for operating an application function AF (205) to implement a change in the quality of service (QoS) of a user equipment (UE), the method comprising: A message is sent (301) to a network open function (NEF) (204) in a communication network, the message identifying a UE and one or both of a start time of a QoS change for the UE and a duration of the QoS change for the UE.

2. The method according to claim 1, wherein: The message also includes an indication of a QoS change to be implemented at the start time and / or during the duration.

3. The method according to claim 1 or 2, wherein: The QoS change is an increase in the data rate provided by the communication network to the UE.

4. The method according to any one of claims 1 to 3, wherein: The method is performed in response to a request to change QoS from a user of the UE to the AF (205).

5. A method for operating a network open function NEF (204) in a communication network to implement a change in the quality of service (QoS) of a user equipment (UE), the method comprising: receiving (401) a message from an application function AF (205) identifying a UE and one or both of a start time of a QoS change for the UE and a duration of the QoS change for the UE; as well as Information identifying the UE and one or both of the start time and duration is sent (403) to a unified data repository UDR (203) in the communication network.

6. A method for operating a unified data repository (UDR) (203) in a communication network to implement a change in the quality of service (QoS) of a user equipment (UE), the method comprising: receiving (501) information identifying a UE and one or both of a start time of a QoS change for the UE and a duration of a QoS change for the UE from a network open function NEF (204); storing (503) the received information; as well as In response to a request from a policy and charging function PCF (202) for policy data and / or application data for the UE, information identifying one or both of a start time and a duration of a QoS change for the UE is sent (505) to the PCF (202).

7. A method of operating a policy and charging function (PCF) (202) in a communication network to implement a change in the quality of service (QoS) of a user equipment (UE), the method comprising: Sending (601) a request for policy data and / or application data of the UE to a unified data repository UDR (203) in the communication network; receiving (603) information identifying the UE and one or both of a start time of a QoS change for the UE and a duration of the QoS change for the UE from the UDR (203); as well as A message is sent (605) to a session management function SMF (201), the message comprising (i) a first event trigger for QoS change based on the start time and / or duration; or (ii) the QoS of the session sent by the SMF (201) after the start time or upon expiration of the duration.

8. The method according to claim 7, wherein: The message sent to the SMF (201) also includes the QoS of the UE applied until the first event trigger occurs.

9. The method according to claim 7 or 8, wherein: The method further comprises: After receiving a message from the SMF (201) indicating that a first event trigger for QoS change has occurred, another message is sent to the SMF (201) indicating a changed QoS for the UE.

10. The method according to claim 9, wherein: Said further message to said SMF (201) further comprises a second event trigger related to the end of the QoS change.

11. A method for operating a session management function (SMF) (201) in a communication network to implement a change in the quality of service (QoS) of a user equipment (UE), the method comprising: receiving (701) a message from a policy and charging function PCF (202) in the communication network, the message comprising a first event trigger for QoS change based on a start time of QoS change of the UE and / or a duration of QoS change of the UE; establishing (703) a data session for the UE and monitoring the occurrence of the first event trigger; After the first event trigger occurs, sending (705) a request to re-authorize the data session to the PCF (202); as well as Updated policy data for the UE implementing the QoS change is received (707) from the PCF (202).

12. The method according to claim 11, wherein: The message received from the PCF (202) also includes the UE's QoS applied to the established data session until the first event trigger occurs.

13. The method according to claim 11 or 12, wherein: The received update policy data further comprises a second event trigger related to the end of the QoS change.

14. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured to, when executed by a suitable computer or processor, cause the computer or processor to perform the method according to any one of claims 1 to 13.

15. A network node (1400) configured to perform the method according to any one of claims 1-13.

16. A network node comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the network node is operable to perform the method according to any one of claims 1-13.

17. A method of operating an application function AF (205) to implement data session control according to a location of a user equipment UE, the method comprising: A message is sent (901) to a network opening function, NEF (204) in a communication network, identifying a UE and a geographical area in which a data session for the UE is allowed or blocked.

18. The method of claim 17, wherein the geographical area is identified using coordinates and / or by cell and / or base station identifiers.

19. A method of operating a network open function (NEF) (204) in a communication network to implement data session control according to a location of a user equipment (UE), the method comprising: receiving (1001) a message from an application function AF (205) identifying a UE and a geographical area in which a data session for the UE is allowed or blocked; as well as Information identifying the UE and the geographical area is sent (1003) to a unified data repository UDR (203) in the communication network.

20. A method of operating a unified data repository (UDR) (203) in a communication network to implement data session control according to a location of a user equipment (UE), the method comprising: receiving (1101) information identifying a UE and a geographical area in which a data session of the UE is allowed or blocked from a network opening function NEF (204); storing (1103) the received information; as well as In response to a request from a Policy and Charging Function (PCF) (202) for policy data and / or application data for the UE, information identifying the geographical area is sent (1105) to the PCF (202).

21. A method of operating a policy and charging function (PCF) (202) in a communication network to implement data session control based on the location of a user equipment (UE), the method comprising: Sending (1201) a request for policy data and / or application data for a UE to a unified data repository UDR (203) in a communication network; receiving (1203) from the UDR (203) information identifying the UE and a geographical area in which data sessions for the UE are allowed or blocked; as well as A message including a first event trigger for controlling a data session of a UE is sent (1205) to a session management function SMF (201).

22. The method according to claim 21, wherein: If the UE moves into or out of the geographical area, the first event trigger is triggered.

23. The method according to claim 21 or 22, wherein: The method further comprises: After receiving a message from the SMF (201) indicating that the first event trigger has occurred, determining whether to allow a data session based on the location of the UE relative to the geographical area; and Another message indicating whether the data session is allowed is sent to the SMF (201) according to the result of the determination.

24. The method according to claim 23, wherein: The information received from the UDR (203) includes information identifying a geographical area in which data sessions for the UE are permitted; The determining step includes: if the location of the UE is within the geographical area, determining to allow the data session; otherwise, determining not to allow the data session or to reduce the data rate of the data session.

25. The method according to claim 23, wherein: The information received from the UDR (203) includes information identifying a geographical area in which data sessions for the UE are not allowed; The determining step includes: if the location of the UE is within the geographical area, determining that the data session is not allowed; otherwise, determining that the data session is allowed.

26. A method of operating a session management function (SMF) (201) in a communication network to implement data session control according to the location of a user equipment (UE), the method comprising: receiving (1301) a message from a policy and charging function PCF (202) in the communication network, the message comprising a first event trigger for controlling a data session according to a location of the UE, wherein the first event trigger is triggered if the UE moves into or out of an indicated geographical area; monitoring (1303) a location of the UE for occurrence of the first event trigger; After the first event trigger occurs, sending (1305) a request for policy data for a data session to the PCF (202), wherein the request indicates whether the UE is inside or outside the geographic area; and Updated policy data for the UE is received (1307) from the PCF (202), the updated policy data indicating whether a data session for the UE is allowed.

27. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured to, when executed by a suitable computer or processor, cause the computer or processor to perform the method according to any one of claims 17-26.

28. A network node (1400) configured to perform the method of any one of claims 17-26.

29. A network node comprising a processor and a memory, the memory containing instructions executable by the processor, whereby the network node is operable to perform a method according to any one of claims 17-26.

Images