Patent ID: 12261753

DETAILED DESCRIPTION

The Invention according to the present disclosure is further elaborated with the help of diagrams that enable further understanding of the present disclosure. The illustrations are not limiting and are merely explanatory.

FIG.1schematically illustrates a part of the architecture of a Fifth Generation, 5G, telecommunication network,50. InFIG.1, reference numeral50indicates a reference architecture for a 5G system. The 5G system architecture comprises the following Network Functions, NFs:Authentication Server Function, AUSF,55Access and Mobility Management Function, AMF,56Data network, DN, e.g. operator services, Internet access or third party services,54Network Exposure Function, NEF,62NF Repository Function, NRF,61Policy Control Function, PCF,60Session Management Function, SMF,57Unified Data Management, UDM,59User Plane Function, UPF,53Application Function, AF,58User Equipment, UE,51Network Slice Selection Function, NSSF,63.

The functional description of these network functions is specified in clause 6 of the 3GPP standard 23.501, “System Architecture for the 5G system”, the contents of which are included herein, by reference.

FIG.2shows the AF58onboard procedure100in case it implements a new PFD Management service.

In step101, the AF sends a newly defined onboard request to NEF62including:Service=PFDManagement—Indication of the new service supportedlist (App-ID, classification-types)—List of supported App-IDs along with the supported classification type. The classification types are:deterministic traffic filtersnon-deterministic heuristic rulesmachine learning modelsNew App-IDs allowed (yes/no)—An indication of whether the AF58admits requests for App-IDs not included in the above list.

In step102, the NEF62acknowledges the onboard request.

FIG.3shows110the request from NEF62to the PFD management service offered by the AF58. In the step111, NEF62invokes the NafPFDManagement Request service in AF58including:list (App-ID)—The list of App-IDs to retrieve the PFDsoperator-ID—The ID of the operator so that AF can identify it and apply the proper permissions.location-ID—An indication of the location of operation of the operator. This may influence the App-IDs the operator is able to retrieve given the operation zone (e.g. a given country).

In step112, the AF112responds including a list of tuples, each tuple including App-ID, PFDs—Including deterministic traffic filters non-deterministic heuristic rules and machine learning models. Both the non-deterministic heuristic rules and machine learning models are new parameters within the standard PFD specification.

FIG.4shows the subscription procedure120from NEF62to the new PFD management service in AF58. Alternate to the request response procedure, the NEF62may subscribe to notifications from the AF58regarding PFDs. In step121, the NEF62invokes the NafPFDManagement Subscribe service in AF58including list (App-ID)—As described in connection withFIG.3, operator-ID—as described previously, and location-ID.

In step122, the AF58acknowledges the subscription request. And if available, AF58can include in the response the corresponding list of App-IDs, PFDs.

When a new PFD is available for an App-ID, AF58invokes the NafPFDManagement Notify service operation123including App-ID, PFD including the heuristic rules and machine learning models if available.

FIG.5shows the AF58onboard procedure130in case it implements a new Event-ID. The AF58sends131an onboard request to NEF62including Event-ID=TRAFFIC_RULES/TRAFFIC_MODELS—Indication of the new Event supported, list (App-ID, classification-types)—List of supported App-IDs along with the supported classification type. The classification types are deterministic traffic filters, non-deterministic heuristic rules, and machine learning models. The onboard request also includes New App-IDs allowed (yes/no)—An indication of whether the AF admits requests for App-IDs not included in the above list. In step132, the NEF62acknowledges the onboard request.

FIG.6shows140the request from NEF62to the new event offered by the AF58. The NEF62invokes141the Naf_EventExposure Request service in AF including Event-ID=TRAFFIC_RULES/TRAFFIC_MODELS, list (App-ID)—The list of App-IDs to retrieve the PFDs, operator-ID—The ID of the operator so that AF can identify it and apply the proper permissions, and location-ID—An indication of the location of operation of the operator. This may influence the App-IDs the operator is able to retrieve given the operation zone (e.g. a given country).

The AF58responds142including a list of tuples, each tuple including App-ID, PFDs—Including deterministic traffic filters, non-deterministic heuristic rules, and machine learning models. Both the non-deterministic heuristic rules and machine learning models are new parameters within the standard PFD specification.

FIG.7shows the subscription procedure150from NEF62to the event exposed by AF58. The NEF62invokes the Naf_EventExposure Subscribe service151in AF58including Event-ID=TRAFFIC_RULES/TRAFFIC_MODELS, list (App-ID) operator-ID, and location-ID. These parameters have been described previously in the present disclosure. The AF58acknowledges152the subscription request. If available, AF58can include in the response the corresponding list of (App-IDs, PFDs).

In a new message, when a new PFD is available for an App-ID, AF58invokes153the Naf_EventExposure Notify service operation including App-ID, and PFD including the heuristic rules and machine learning models if available.

FIG.8shows an example160of Use Case, PFD Management pull procedure, using the external AF58traffic classification service for a certain application (example.com):

AF58sends1an onboard request to NEF62including Service=PFDManagement—Indication of the new service supported, list of App-ID (including example.com). In this example, for simplicity, no classification-types are included. The NEF62acknowledges2the onboard request.

The UE51triggers3PDU session establishment, by means of sending a PDU Session Establishment Request to AMF56. The AMF56selects4an SMF57to manage the PDU session. The SMF57selection function in the AMF56selects an SMF instance based on the available SMF instances obtained from NRF61or on the configured SMF information in the AMF56and triggers Nsmf PDU Session Create. Note the sequence diagram inFIG.8does not include all the signaling messages involved in the PDU Session Establishment procedure. Only the steps relevant to the present disclosure are illustrated and elaborated.

SMF57triggers5Npcf_SMPolicyControl_Create Request message to retrieve SM policies for the user PDU session. The PCF60triggers6Nudr_Query Request message to retrieve the policy data for this user's PDU session. The UDR161answers7with Nudr_Query Response message including the Subscriber Policy Data.

PCF60generates8the corresponding PCC rule/s based on Subscriber Policy Data. Based on the above, the PCF60triggers9Npcf_SMPolicyControl_Create Response message including the PCC rules to be applied for this user PDU session. In this case, there will be a PCC rule for App-IDId=example.com, including some enforcement actions such as Charging and QoS.

SMF57has no PFD rules for App-ID=example.com so it triggers10PFD Management pull procedure. SMF57triggers11towards NEF62a Nnef HTTP GET (Request) for the Nnef_PFDManagement service and for App-ID=example.com

NEF62contacts12UDR161and triggers a Nudr_Query Request message including App-ID=example.com as a parameter. UDR161determines13that it has no PFDs for appId=example.com

In step14, UDR161answers NEF62with a Nudr_Query Response message indicating no data for App-ID=example.com as a parameter. In step15, NEF62invokes the Naf_PFDManagement Request service in AF58including App-ID=example.com, operator-ID=operator X.

The AF58looks16for the PFDs corresponding to App-ID=example.com and operator-ID, and answers17NEF62with a Naf_PFDManagement Response message including the PFDs: App-ID=example.com, PFDs.

NEF62answers18the message in Step11above by triggering a Nnef 200 OK including the PFDs for App-ID=example.com. SMF57triggers19PFCP PFD Management request towards UPF including the PFDs for App-ID=example.com.

UPF53answers20with a PFCP PFD Management response message. SMF57triggers21a PFCP Session Establishment request message towards UPF53with the PDRs (Packet Detection Rules) for the App-IDs, specifically a PDR for App-ID=example.com with the associated FAR, QER and URR. UPF53answers22SMF57with a PFCP Session Establishment response message. When a user51starts23an application (example.com), the UPF53detects24example.com traffic, based on the PFDs, and applies the corresponding enforcement actions such as Charging, QoS. Finally, the UPF53forwards25the application traffic towards the application server,162.

FIG.9schematically illustrates an application function58according to the present disclosure. The application function58comprises a receiver201,202arranged to receive signals from other devices in the communication network. The function58also comprises transmitting means203,204arranged to transmit signal to other devices in the communication network. It may be understood by the skilled person that the receiver201,202and transmitter203,204are separately shown merely for illustrative purposes. The combined functionality may be achieved by a transceiver, for example.

The receiver201,202may further be arranged for receiving, a request message for requesting a PFD, wherein said request message comprises an application identification for identifying an application. The transmitter203,204is arranged for transmitting, by said AF, to said NEF, a response message comprising said application identification and said requested PFD.

The application function58further comprises processor205and memory206. The memory may be arranged to store a computer program product which when executed by the processor205causes the device58to perform a method according to the present disclosure. The internal components communicate with one another using an internal bus207.

FIG.10schematically illustrates an network exposure function62according to the present disclosure. The function62comprises a receiver301,302arranged to receive signals from other devices in the communication network. The function62also comprises transmitting means303,304arranged to transmit signal to other devices in the communication network. It may be understood by the skilled person that the receiver301,302and transmitter303,304are separately shown merely for illustrative purposes. The combined functionality may be achieved by a transceiver, for example.

The transmitter303,304is arranged for sending to said AF, a PFD management request, wherein said PFD management request identifies an application and operator for which PFDs are requested. The receiver301,302is arranged for receiving from said AF, said requested PFDs for said identified application and operator. The transmitter303,304may further be arranged for sending a PFD management request for one of the applications identified in a list of application IDs received by said NEF during on-boarding.

The receiver301,302may further be arranged for receiving, from a Session Management Function, SMF, a trigger message requesting PFDs for a particular application identified by a corresponding application ID.

The network exposure function62further comprises processor305and memory306. The memory may be arranged to store a computer program product which when executed by the processor305causes the device62to perform a method according to the present disclosure. The internal components communicate with one another using an internal bus307.

Other variations to the disclosed examples can be understood and effected by those skilled in the art in practicing the claimed disclosure, from a study of the drawings, the disclosure and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. A single processor or other unit may fulfil the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

A computer program may be stored/distributed on a suitable medium, such as optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. Any reference signs in the claims should not be construed as limiting scope thereof.

The present disclosure is not limited to the examples as disclosed above, and can be modified and enhanced by those skilled in the art beyond the scope of the present disclosure as disclosed in the appended claims without having to apply inventive skills.