Methods and nodes for implementing service management
By passing extended PFD rules between user data nodes, network open nodes and session nodes, the problem of detection problems of non-HTTP/HTTPS services and insufficient fraud prevention in existing systems is solved, and the accuracy of multiple protocol services is achieved. Classification and billing enhances the flexibility and security of the system.
Patent Information
- Application Number
- CN201880095409.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-05-08
- Filing Date
- 2018-06-04
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2038-06-04
AI Technical Summary
The existing service management system is difficult to effectively detect and classify services that are not HTTP/HTTPS protocols in communication devices, which makes it difficult to prevent fraudulent behaviors, and the PFD rules lack flexibility and cannot accurately match services that are not free.
By passing extended PFD rules between user data nodes, network open nodes and session nodes, including protocol parameters such as CNS, DNS domain names, SNI, IP addresses, HTTP-related indications, etc., it is used to classify services and prevent fraud.
It realizes more accurate classification and billing of services of different protocols, enhances the prevention of fraud, and provides more flexible PFD rules to support business management of multiple protocols and service types.
Smart Images

Figure CN112369115B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to service management in a network such as a computer network, a communication network, etc. Service management may include service differentiation, policy execution, etc. In particular, a method and a user data node for managing services between a client application running in a communication device and a server application hosted by an application node, a method and a network open node for implementing service management, and a method and a session node for implementing service management are disclosed. Corresponding computer programs and computer program carriers are also disclosed. Background Art
[0002] Traffic management occurs in various architectures for entities of a given communication system.The 3rd Generation Partnership Project (3GPP) provides standardized Technical Specifications (TS) for entities in a communication system.
[0003] A known system may therefore include an operator network of a fifth generation (5G) architecture according to 3GPP specifications. Traffic passes through the operator network between a server hosted by a service capability server (SCS) / application server (AS) and a client executed on a user equipment (UE). In this context, the operator network may be operated by a network service provider (NSP), and the server may be operated by an application service provider (ASP), over-the-top (OTT), etc.
[0004] In addition, the operator network usually includes a network open function (NEF), which may include a packet flow description function (PFDF) and a service capability function (SCEF), a session management function (SMF) and a user plane function (UPF). A so-called T8 interface is provided for communication between the SCS / AS and the NEF.
[0005] The PFDF is a functional element that receives and manages a Packet Flow Description (PFD) associated with a specific application identifier. The specific application identifier identifies an application running on a server hosted by the ASP. The PFD is received from the SCEF via the so-called Nu interface.
[0006] PFD is a set of information used to detect application services, including:
[0007] PFD identifier (id); and
[0008] A triplet consisting of the protocol, the server-side Internet Protocol (IP) address, and the port number; or
[0009] A valid part of the URL to be matched, such as a hostname; or
[0010] Domain name matching criteria.
[0011] The PFDF provides the SMF with the PFD or PFD rules for the corresponding application identifier.
[0012] A similar architecture is provided for the so-called fourth generation (4G) networks. 3GPP provides, among other things, the following specifications for standardization of relevant entities and interfaces for 4G and 5G: TS 29.122, TS 29.244, TS 23.203, TS 23.214, TS 23.401 and TS 23.402.
[0013] With the aid of the above-mentioned known system, the following types of PFD are specified:
[0014] flowDescription, i.e., a triplet with the protocol, server IP address, and server port for UpLink / DownLink (UL / DL) traffic,
[0015] url, a universal resource locator (URL), or a regular expression that is used to match valid parts of a URL,
[0016] domainNames, that is, fully qualified domain names (FQDN) or regular expressions that serve as domain name matching criteria.
[0017] The above PFD allows for traffic detection and classification for Hypertext Transfer Protocol (HTTP) / HTTP Security (HTTPS) based applications. In scenarios involving traffic based on other protocols, the inability to detect and classify traffic may be disadvantageous.
[0018] Furthermore, PFD is a target for fraud. For example, if an ASP provides a url or domainNames, the operator network (e.g., UPF) may be deceived into not charging for services that match the specified PFD rules but are not related to the intended application. When the operator network checks the url or domainNames, since the PFD specifies domainNames that are permitted to be browsed free of charge, the operator network identifies the service as free. However, a fake application can trigger services that match the above url or domainNames, but the service will actually flow to another server (not the ASP server), resulting in fraud because this service will not be billed (although it should be). Summary of the invention
[0019] The aim may be to achieve flexibility with respect to traffic management (eg traffic classification and enforcement of rules for eg billing etc.) in systems of the kind described above.
[0020] According to one aspect, the object is achieved by a method performed by a user data node for managing traffic between a client application running in a communication device and a server application hosted by an application node. An operator network comprises a session node and the user data node.
[0021] The user data node receives a management request from the session node including PFD rules for the server application.
[0022] The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following: an indication related to a common name CNS, an indication related to a domain name system DNS domain name, a server name indication SNI, an indication related to fraud prevention, an indication related to a server IP address, an IP header field for an IP protocol version, an indication related to HTTP-host, an indication related to HTTP-user-agent, an indication related to HTTP-content-type, an indication related to HTTP-GET, an indication related to HTTP-POST, an indication related to HTTP-PUT, an indication related to HTTP-PATCH, and an indication related to HTTP-Response-Codes.
[0023] The user data node receives the service destined for the server application from the client application. The user data node classifies the service according to the PFD rule, thereby obtaining the classified service.
[0024] In addition, the user data node performs an action for the classified service, wherein the action is based on the PFD rule.
[0025] According to another aspect, the object is achieved by a method performed by a network open node for enabling management of traffic between a client application running in a communication device and a server application hosted by an application node.An operator network comprises a network open node and a session node.
[0026] The network open node receives the PFD rules for the server application from the application node. The PFD rules have been specified above.
[0027] The network open node sends the PFD rule to the session node.
[0028] According to another aspect, the object is achieved by a method performed by a session node enabling management of traffic between a client application running in a communication device and a server application hosted by an application node. An operator network comprises a network open node, said session node and a user data node.
[0029] The session node receives the PFD rules for the server application from the network open node. The PFD rules have been specified above.
[0030] The session node sends a management request including the PFD rule to the user data node.
[0031] According to yet another aspect, the object is achieved by a user data node configured to manage traffic between a client application running in a communication device and a server application hosted by an application node. An operator network comprises a session node and the user data node.
[0032] The user data node is configured to receive from the session node a management request comprising PFD rules for the server application. The PFD rules have been specified above.
[0033] The user data node is configured to receive services from the client application to the server application. The user data node is configured to classify the services according to the PFD rules, thereby obtaining classified services.
[0034] In addition, the user data node is configured to perform an action on the classified service. The action is based on the PFD rule.
[0035] According to yet another aspect, the object is achieved by a network open node configured to enable management of traffic between a client application running in a communication device and a server application hosted by an application node. An operator network comprises a network open node and a session node.
[0036] The network open node is configured to receive PFD rules for the server application from the application node. The PFD rules have been specified above.
[0037] The network open node is configured to send the PFD rules to the session node.
[0038] According to yet another aspect, the object is achieved by a session node configured to enable management of traffic between a client application running in a communication device and a server application hosted by an application node. An operator network comprises a network open node, the session node and a user data node.
[0039] The session node is configured to receive PFD rules for the server application from the network open node. The PFD rules have been specified above.
[0040] The session node is configured to send a management request including the PFD rule to the user data node.
[0041] According to other aspects, the object is achieved by a computer program and a computer program carrier corresponding to the above aspects.
[0042] As an example, the user data node can use the indication related to the common name "CNS", the indication related to the domain name system "DNS" domain name, and the server name indication "SNI" to infer which protocol these indications are related to. Therefore, the user data node can know which fields and / or headers to monitor, for example, to be able to detect and classify traffic to use other protocols besides HTTP / HTTPS.
[0043] As another example, an indication related to fraud prevention can be interpreted by the user data node as a command to activate a fraud prevention process, as described in more detail in the detailed description.
[0044] According to some embodiments, one advantage can be allowing an ASP to specify a PFD in a more detailed manner, which can result in more accurate classification of traffic at a user data node.
[0045] Furthermore, according to some embodiments, an advantage may be that fraud can be prevented or at least made more difficult.
[0046] Therefore, through the embodiments of this article, the ASP is able to provide a more flexible PFD to the operator network. BRIEF DESCRIPTION OF THE DRAWINGS
[0047]
[0013] Various aspects of the embodiments disclosed herein, including particular features and advantages thereof, will be readily understood from the following detailed description and the accompanying drawings briefly described hereinafter.
[0048] Figure 1 is a schematic overview of an exemplary system in which embodiments herein may be implemented;
[0049] Figure 2 is a signaling and flow chart illustrating a combination of methods herein;
[0050] Figure 3 is another combined signaling and flow chart illustrating an exemplary method;
[0051] Figure 4is another combined signaling and flow chart illustrating another exemplary method;
[0052] Figure 5 is a flow chart illustrating an embodiment of a method in a user data node;
[0053] Figure 6 is a block diagram illustrating an embodiment of a user data node;
[0054] Figure 7 is a flow chart illustrating an embodiment of a method in a network open node;
[0055] Figure 8 is a block diagram illustrating an embodiment of a network open node;
[0056] Fig. 9 is a flow chart illustrating an embodiment of a method in a conversation node;
[0057] Fig.10 is a block diagram illustrating an embodiment of a session node. DETAILED DESCRIPTION
[0058] Throughout the following description, when applicable, like reference numerals have been used to denote like features, such as nodes, acts, modules, circuits, components, items, elements, units, etc. In the drawings, features that appear in some embodiments are indicated by dashed lines.
[0059] Figure 1 An exemplary system 100 is depicted in which embodiments herein may be implemented.
[0060] In this example, the system 100 may include an operator network 101. The operator network 101 may include a Global System for Mobile Communications network, Long Term Evolution (LTE), Universal Mobile Telecommunications System (UMTS), and Worldwide Interoperability for Microwave Access (WiMAX) and its evolutions, among others.
[0061] The system 100 may be considered to include a user equipment 110. This may mean that the user equipment 110 is present in the operator network 101, eg attached thereto, connected thereto, etc. In a similar manner, multiple user equipments may be connected (not shown here for simplicity).
[0062] As used herein, the term "user device" may refer to a wireless communication device, a machine-to-machine (M2M) device, a mobile phone, a cellular phone, a personal digital assistant (PDA) with radio communication capabilities, a smart phone, a laptop or personal computer (PC) equipped with an internal or external mobile broadband modem, a tablet computer with radio communication capabilities, a portable electronic radio communication device, a sensor device with radio communication capabilities, etc. The sensor device can detect any kind of measurement, such as wind, temperature, air pressure, humidity, light, electricity, sound, image, etc. The term "user" may indirectly refer to a wireless device. Sometimes, the term "user" may be used to refer to a user device as described above, etc. It should be understood that a user may not necessarily involve a human user. The term "user" may also refer to a machine, a software component, etc. that uses a specific function, method, etc.
[0063] In addition, the system 100 and / or the operator network 101 may include a user data node 120 such as a UPF, an access and mobility function (AMF) 130, a session node 140 such as an SMF, a policy and charging function (PCF) 150, a network open node 160 such as an NEF, and a user data repository (UDR) 180. These functions or entities may have their known functions in addition to those described below.
[0064] User data node 120 may handle deep packet inspection and service classification, which requires updated rules from policy node 150 in order to correctly classify traffic from UE 110 and apply, for example, desired QoS, charging, etc.
[0065] PCF 150 may make policy decisions in a known manner and manage charging based on so-called charging rules.
[0066] The system 100 may include an application node 170, shown as an SCS / AS, which may host a server application 190, such as a server, application, service application, service, etc. It can be said that the server application 190 provides services, such as streaming video, providing sensor data, providing any information upon request, being able to receive any information for storage, etc. The server application 190 may implement any service provided by an OTT, ASP, etc. In other words, the application node 170 may host a server, such as providing the above services, while communicating with the operator network 101 via a T8 interface known in 3GPP terminology.
[0067] Furthermore, user data node 120 may manage forwarding of user data or traffic from application 190 hosted by application node 170 to user device 110 and / or from user device 110 to application 190 hosted by application node 170 .
[0068] System 100 may sometimes further include a domain name node 200, such as a DNS server, etc. Domain name node 200 handles mapping from a plain text URL such as "www.facebook.com" to a server IP address such as "101.15.13.226" or other appropriate addresses.
[0069] Additionally, user device 110 may host client application 115, which may act as a client of application 190. Client application 115 is represented in the figure as “app.” User data node 120 manages traffic between client application 115 and server application 190.
[0070] Figure 2 Shows that when Figure 1 When implemented in the system 100, it is an exemplary method according to the embodiments of the present invention.
[0071] The user data node 120 performs a method for managing traffic between a client application 115 running in the communication device 110 and a server application 190 hosted by the application node 170. The network open node 160 performs a method for enabling management of traffic between a client application 115 running in the communication device 110 and a server application 190 hosted by the application node 170. The session node 140 performs a method for enabling management of traffic between a client application 115 running in the communication device 110 and a server application 190 hosted by the application node 170.
[0072] As mentioned, the operator network 101 includes at least one of a user data node 120 , a session node 140 , and a network open node 160 .
[0073] One or more of the following actions may be performed in any suitable order.
[0074] Action A010
[0075] The network open node 160 receives the application node 170 ( Figure 2 The PFD rule for the server application 190 is received by the server application 190 (not shown). This means that the PFD rule is associated with the server application 190, for example, by means of an application identifier. The PFD rule includes a packet flow description identifier (commonly referred to as pfdId) and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters. According to the present specification, the one or more protocol parameters include one or more of the following:
[0076] Instructions related to the common name CNS,
[0077] Instructions related to Domain Name System DNS domain names,
[0078] Server Name Indication SNI,
[0079] Instructions relating to fraud prevention,
[0080] an indication of the server IP address and possibly the server port at, for example, layer 4 and / or layer 7 of the OSI protocol stack,
[0081] IP header fields for IP protocol version,
[0082] Instructions related to HTTP-host,
[0083] HTTP-user-agent related instructions,
[0084] Instructions related to HTTP-content-type,
[0085] HTTP-GET related instructions,
[0086] Instructions related to HTTP-POST,
[0087] Instructions related to HTTP-PUT,
[0088] HTTP-PATCH related instructions,
[0089] Indications related to HTTP-Response-Codes, and
[0090] analog.
[0091] Due to, for example, an indication related to a DNS domain name, the application node 170 can enable the operator network 101 (in particular the network open node 160 and the user data node 120) to know later that the DNS protocol is used. The fact that the DNS protocol may be used in the service can be inferred from the indication related to the DNS domain name given in the PFD rule.
[0092] In this way, the operator network 101 is able to identify other protocols, such as Quick User Datagram Protocol (UDP) Internet Connections (QUIC), Spotify protocol, non-IP traffic (such as Internet of Things (IoT) data, etc.).
[0093] Further details about these one or more protocol parameters are provided below so as not to obscure the Figure 2 Description of the process.
[0094] Action A020
[0095] The network open node 160 sends the PFD rules to the session node 140. In this way, the network open node 160 allows the information included in the PFD rules to propagate in the operator network 101.
[0096] Action A030
[0097] After action A020 , session node 140 receives PFD rules for server application 190 from network open node 160 .
[0098] Action A040
[0099] To distribute the PFD rules in operator network 101 , session node 140 sends a management request including the PFD rules to user data node 120 .
[0100] Action A050
[0101] After action A040 , user data node 120 thus receives a management request from session node 140 .
[0102] Action A060
[0103] The client application 115 may trigger a session establishment (est.) procedure in order to establish a session (eg, a PDU session) for exchanging traffic between the client application 115 and the server application 190 .
[0104] Action A070
[0105] After the session has been established, the client application 115 can initiate traffic towards the server application 190. In other words, the client application 115 can send traffic to the server application 190.
[0106] Action A080
[0107] When the client application 115 sends traffic, the traffic will pass through the operator network 101. While passing through the operator network 101, the user data node 120 thus receives the traffic from the client application 115 destined for the server application 190.
[0108] Action A090
[0109] The user data node 120 classifies the services according to the PFD rule, thereby obtaining the classified services.
[0110] Action A100
[0111] The user data node 120 performs actions for the classified services. The actions performed by the user data node 120 or other nodes cooperating with the user data node are based on the PFD rules, such as derived from the PFD rules, given by the PFD rules, and so on.
[0112] In some embodiments, the one or more protocol parameters may include an indication of a DNS domain name. In these embodiments, actions A110, A120, and A130 may be performed.
[0113] Action A110
[0114] The user data node 120 may obtain the server IP address corresponding to the indication of the DNS domain name from the domain name node 200 .
[0115] Action A120
[0116] User data node 120 may receive other traffic from client application 115 that is identified by a destination IP address and that may be destined for a particular domain name.
[0117] Action A130
[0118] Before sending other traffic to the server application 190, the user data node 120 may verify that the destination IP address and the specific domain name match the obtained server IP address.
[0119] In view of the above, embodiments of the present invention may implement one or more extensions to the PFD rules exchanged between the ASP and the NSP, particularly between the application node 170 and the network open node 160 on the so-called T8 interface, with protocol identifiers (e.g., DNS, HTTP, HTTPS, QUIC, etc.) and with corresponding protocol parameters (e.g., SNI, public name, etc. listed above). Optionally, the PFD rules may include fraud prevention indications and / or other fields, such as one or more of the PFD version, PFD origin, and MNO identifier.
[0120] Thus, a method for handling extended PFDs exchanged between an ASP and an NSP in a telecommunications network, such as the system 100 described above, is provided.
[0121] Therefore, the embodiments of this article may affect the following interfaces:
[0122] - As mentioned above, the T8 interface between the application node (eg SCS / AS) and the network open node (eg SCEF).
[0123] -5G version of the Gw interface between the PFDF (which may be included in the network open node) and the session node (e.g. SMF).
[0124] - N4 interface between session nodes and user data nodes, such as N4 PFD management program.
[0125] -Nu interface between SCEF and PFDF.
[0126] - Gw / Gwn interface between PFDF and Packet Gateway – Control Plane (PGW-C) / Traffic Detection Function – Control Plane (TDF-C).
[0127] - Sx interface between PGW-C / TDF-C and PGW – User Plane (U) / TDF-U.
[0128] In specific use cases, embodiments herein extend PFD rules with protocol identifiers, either explicitly or implicitly. "Implicitly" means that the protocol identifier is optional for those cases where the protocol can be derived from one or more protocol parameters (as will be apparent from the following examples).
[0129] In more detail, with respect to Stateful Packet Inspection (SPI) (L3 / L4 inspection), the following types of PFD rules are supported today:
[0130] -flowDescriptions (triplets with protocol, server ip and server port for UL / DL application services)
[0131] An example of a rule of this type (for use with the T8 API in PFD management JSON format):
[0132] "pfdId": "facebook",
[0133] "flowDescriptions": [
[0134] "The permitted range of IP is from any IP to 31.13.60.32 / 29",
[0135] "tcp allowed range from any tcp to 31.13.62.32 / 29 80,8080"]
[0136] This only covers triplets.
[0137] This paper proposes to extend the PFD flowDescriptions syntax with IP header fields for IP protocol version (such as IPv4ToS / DSCP), IPv6 flow labels, etc. This will allow differentiation of services when different application components (such as audio and video) are carried in the same triplet. This will be common in HTTP / 2 based applications where different HTTP / 2 flows are carried on the same TCP connection (triplet).
[0138] In relation to deep packet inspection (DPI) (e.g., layer 7 (L7) inspection), the following types of PFD rules are supported today:
[0139] url (a URL or a regular expression to be used to match valid parts of a URL).
[0140] domainNames (FQDN or regular expression matching criteria for domain names).
[0141] Assume that url refers to the plaintext HTTP protocol and URL parameters. It lacks other HTTP parameters such as HTTP Host, HTTP content-type, HTTP User-agent, and HTTP operations (e.g., HTTP GET, POST, PUT, PATCH, and HTTP Response Codes (2xx for success or 4xx / 5xx for failure)).
[0142] According to an embodiment of the present invention, protocol parameters are provided with the help of indications related to HTTP-host, indications related to HTTP-user-agent, indications related to HTTP-content-type, indications related to HTTP-GET, indications related to HTTP-POST, indications related to HTTP-PUT, indications related to HTTP-PATCH, and indications related to HTTP-Response-Codes.
[0143] In the case of domainNames according to existing solutions, the protocol and protocol parameters referenced by domainNames are not specified. Therefore, the UPF, when receiving a PFD with domainNames (e.g., *facebook*), does not know which protocol / protocol parameters to look for when analyzing incoming traffic.
[0144] Due to the above limitations of existing solutions, it is recommended to add support for the indication protocol (DNS, HTTP, HTTPS, etc.) and corresponding protocol parameters (SNI, CN, etc.) of PFD.
[0145] Thus, in some embodiments, a PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters. This is particularly useful when a particular protocol (perhaps given a protocol identifier) cannot be unambiguously derived from the protocol parameters included in the PFD rule. However, as described above, an identifier for identifying a protocol may not be required when the protocol can be derived from the protocol parameters provided in the PFD rule. For example, if an indication related to CNS is provided, it may be inferred that a Transport Layer Security (TLS) common name is used.
[0146] In some embodiments, the existing domainNames parameter (also referred to herein as an indication related to a DNS domain name) may be retained for backward compatibility, but where it is used, it may be specified to reference only the TLS protocol and SNI parameters, as these are the most common parameters for matching HTTPS-based applications. Thus, a PFD rule may include:
[0147] "domainNames": ["fb\.com$", "fbcdn\.com$],
[0148] The above PFD rule can indicate a set of TLS SNI or a regular expression that is used to match the valid part of TLS SNI, i.e. Server Name Indication.
[0149] To add support for other protocols such as DNS, the following syntax is recommended:
[0150] “dnsDomainNames”: [“fb\.com$”, “fbcdn\.com$], where dnsDomainNames is an example of an indication related to a DNS domain name.
[0151] The above PFD rules may indicate a set of DNS domain names or regular expressions to be used to match valid parts of DNS domain names.
[0152] Furthermore, since most applications today are based on HTTPS (thus using the TLS protocol), some embodiments imply a PFD for the TLS protocol and the Common Name Parameter (cns):
[0153] "cns": ["^facebook\.com$", "^fbcdn\.com$", where cns is an example of an indication related to a common name.
[0154] The PFD rule above may indicate a set of TLS common names or a regular expression to be used to match the valid part of a common name. This information may be given by an indication related to the CNS.
[0155] Now, go to Figure 3 , shows a combined signaling and flow chart of an exemplary implementation of the embodiments of the present invention. In this example, the application node 170 is exemplified by SCS / AS, the network open node 160 is exemplified by NEF / PFDF, the session node 140 is exemplified by SMF, and the user data node 120 is exemplified by UPF.
[0156] One or more of the following steps or actions may be performed.
[0157] Actions 1 and 2
[0158] SCS / AS (e.g., Facebook, etc.) can provide PFD rules for specific applications (e.g., Facebook Messenger) by triggering an HTTP POST method (including a JavaScript Object Notation (JSON) body, new PFD types shown in italics (dnsDomainName and cns)), via the T8 API for PFD management, etc. At least in part, these actions can be similar to Figure 2 Action A010.
[0159]
[0160]
[0161] Actions 3 and 4
[0162] The NEF / PFDF may store the PFD rules according to the embodiments herein in the UDR.
[0163] Actions 5 and 6
[0164] NEF / PFDF can push PFD rules to SMF. At least in part, these actions can be similar to Figure 2 Action A020.
[0165] Actions 7 and 8
[0166] The SMF may push the PFD rules to the UPF via the PFCP PFD Management procedure, for example, through the above-mentioned management request. At least in part, these actions may be similar to Figure 2 Action A040.
[0167] Action 9
[0168] The UE may trigger a PDU session establishment procedure and may start an application service such as Facebook Messenger. At least in part, this action may be similar to Figure 2 Action A060 and / or A070.
[0169] Action 10
[0170] UPF can analyze the incoming traffic and classify it as Facebook Messenger (because it matches the PFD rule above). UPF applies the corresponding execution action, such as free rating, etc. This action can be similar to Figure 2 One or more of actions A080, A090, A100, etc.
[0171] Action 11
[0172] As an example of server application 190, UPF can forward the service to the application server. This action can be similar to Figure 2 Action A100.
[0173] In another use case, existing PFD rules can be used to target fraud. For example, an ASP or SCS / AS can provide URLs or domainNames without specifying the server IP address. This way, free browsing can be obtained for non-free services / server applications.
[0174] According to embodiments herein, by extending PFD rules to allow for IP address validation and / or DNS validation, fraud can be stopped, or at least made more difficult to accomplish.
[0175] Allows IP address verification of PFDs.
[0176] To avoid fraud, it is recommended that urls, domainNames, and cns include support for at least one of the server IP address, L4, and L7 server ports (shown in italics):
[0177] "urls":[url,L7_port,host_IP,L4_port]
[0178] "domainNames":[sni,L7_port,host_IP,L4_port]
[0179] "cns":[commonName,L7_port,host_IP,L4_port"]
[0180] Here, the indication related to the server IP address is exemplified by host_IP. Similarly, according to some embodiments, corresponding indications for ports at layer 4 and layer 7 may be introduced, such as L4_port and L7_port. In other words, the indication related to the server IP address may also be related to a server port at layer 4 and / or layer 7 of the OSI protocol stack, where OSI refers to the Open Systems Interconnection model.
[0181] For this use case, the process is similar to Figure 3 The flow is similar. However, action 1 is replaced by the following operation: SCS / AS provides PFD rules for a specific application via T8 API for PFD management by triggering HTTP POST method including JSON body, wherein the PFD rules include extensions shown in italics. Here, IPv4 address is added as an example, but IPv6 can also be added or alternatively.
[0182]
[0183] In the above example, where the UPF receives an uplink packet, the packet is classified as Facebook Messenger only if the URL ends with "facebook.com" and the destination IP address in the IP header matches "101.15.13.226".
[0184] These embodiments require knowledge of the server IP address and optionally also the port.The following embodiments do not require knowledge of the server IP address.
[0185] PFD extension to allow DNS validation
[0186] In the case where the SCS / AS does not know the server IP address and port and wants to provide a PFD for an application that is subject to spoofing, it is recommended to extend the following PFD rules with the indications / flags shown in italics:
[0187] "urls":[url,fraudPrevention]
[0188] "domainNames":[domainName,fraudPrevention]
[0189] "cns":[commonName,fraudPrevention]
[0190] In the above examples, fraudPrevention is given as an example of instructions related to fraud prevention.
[0191] Alternatively, the fraudPrevention policy can also be configured locally in the operator's network (for example in the UPF or SMF). This means that no changes to the T8 interface are required.
[0192] Figure 4 is another combined signaling and flow diagram showing an example of how PFD rules may be extended to allow DNS validation. One or more of the following actions may be performed.
[0193] Actions 1 and 2
[0194] SCS / AS (e.g. Facebook) can provide PFD rules for a specific application (e.g. Facebook Messenger) via the T8 API for PFD management by triggering an HTTP POST method (including a JSON body, new extensions in italics (fraudPrevention)). This action can be similar to Figure 2 Action A010.
[0195]
[0196] Actions 3 and 4
[0197] NEF / PFDF may store PFD rules in the UDR that allow DNS validation according to some embodiments.
[0198] Actions 5 and 6
[0199] NEF / PFDF can push PFD rules to SMF. At least in part, these actions can be similar to action A020.
[0200] Actions 7 and 8
[0201] The SMF may push the PFD rules to the UPF via the PFCP PFD Management procedure, for example, by means of the above-mentioned management request. This action may be at least partially similar to action A040.
[0202] Action 9
[0203] The UE may trigger a PDU session establishment procedure in a known manner and may initiate application services, such as to / from Facebook Messenger, by triggering a DNS query for DomainName=facebook-messenger.com. This action may be similar to actions A060 and / or A070.
[0204] Actions 10 and 11
[0205] UPF analyzes the incoming traffic, and because fraudPrevention is enabled, UPF looks for a DNS query message to facebook-messenger.com and waits for a DNS answer. This action may be similar to one or more of actions A090, A100, and A110.
[0206] Actions 12 to 14
[0207] The UPF detects the DNS reply and stores a list of IP addresses and maps the IP address to facebook-messenger.com. This action may be part of action A110.
[0208] Actions 15 to 17
[0209] For all subsequent packets matching one of the above (server-side) IP addresses, the UPF may check the following:
[0210] In HTTP services (such as the above Figure 4 ), and for all HTTP request methods (e.g., GET, POST), the UPF may check whether the HTTP URL matches the above PFD rule (facebook-messenger).
[0211] In HTTPS business (the above Figure 4 In the case where the TLS Client Hello SNI is not shown in Figure 1, the UPF can check whether the TLS Client Hello SNI matches the above PFD rules.
[0212] • Only if any of the above matches, the service can be classified into the corresponding app id (Facebook Messenger). UPF applies the corresponding execution action (eg free rating). This will result in a strong fraud avoidance mechanism.
[0213] This action may be similar to actions A120 and / or A130.
[0214] According to another example, the PFD rule may be extended with one or more of a PFD version, a PFD origin, and an MNO identifier. In other words, the PFD rule may include at least one of a PFD version, a PFD origin, an MNO identifier identifying a mobile network operator to which the PFD rule applies, and configuration information.
[0215] The PFD version can be an identifier for the PFD data to improve the tracing and debugging capabilities of the PFD. The PFD version date is also possible (in addition to the PFD version):
[0216] - This may help identify old PFDs in case of misclassification of UPF reports and may help in updating and refreshing of PFDs.
[0217] - This identifier allows identification of the version of the PFD.
[0218] The PFD Origin may identify the source of the PFD data. Typically, if the OTT provides PFDs for its own services, the PFD Origin may be equal to the SCS / AS identifier, but if a third party collects PFDs from the OTT, the PFD Origin may be different from the SCS / AS identifier:
[0219] - This may be required if a single third party may provide PFDs from multiple OTTs. The PFD origin identifier may identify the third party and the SCS / AS identifier.
[0220] - This identifier allows the source of the PFD to be identified.
[0221] The MNO identifier can identify the network operator:
[0222] - This may be necessary in situations where an OTT shares different PFDs with different operator networks or a third party can provide a set of PFDs that only applies to selected operator networks (potentially only to operator networks with which the third party has a commercial relationship).
[0223] - This identifier allows identification of the target network operator.
[0224] Therefore the following syntax is proposed:
[0225] ; Version (if included) is expected to have a different value for each update of the PFD
[0226] $version="version":string? ,
[0227] ; Origin of the data provided: identity of the application service provider or identity of the providing client unit
[0228] $origin="origin":string?
[0229] ; Mobile network operator to which PFD applies
[0230] $networkOperator="operator":[string+]?
[0231] Example HTTP POST sent by the SCS / AS to the NEF with the suggested extended fields for the T8 API for PFD management in the JSON body shown in italics:
[0232]
[0233]
[0234] exist Figure 5 , a schematic flow chart of an exemplary method in a user data node 120 is shown. The same reference numerals as above have been used to denote the same or similar features, and in particular, the same reference numerals have been used to denote the same or similar actions. Thus, the user data node 120 performs a method for managing traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170. As described above, the operator network 101 includes a session node 140 and a user data node 120.
[0235] One or more of the following actions may be performed in any suitable order.
[0236] Action A050
[0237] User data node 120 receives a management request including a packet flow description PFD rule for server application 190 from session node 140. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol associated with the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0238] Instructions related to the common name CNS,
[0239] Instructions related to Domain Name System DNS domain names,
[0240] Server Name Indication SNI,
[0241] Instructions relating to fraud prevention,
[0242] Indications related to the server IP address,
[0243] IP header fields for IP protocol version,
[0244] Instructions related to HTTP-host,
[0245] HTTP-user-agent related instructions,
[0246] Instructions related to HTTP-content-type,
[0247] HTTP-GET related instructions,
[0248] Instructions related to HTTP-POST,
[0249] Instructions related to HTTP-PUT,
[0250] HTTP-PATCH related instructions, and
[0251] Indications related to HTTP-Response-Codes.
[0252] Action A080
[0253] User data node 120 receives traffic from client application 115 destined for server application 190 .
[0254] Action A090
[0255] The user data node 120 classifies the services according to the PFD rule, thereby obtaining the classified services.
[0256] Action A100
[0257] The user data node 120 performs actions on the classified services, and these actions are based on PFD rules.
[0258] In some embodiments, the one or more protocol parameters may include an indication of a DNS domain name. In these embodiments, the method may also include the following actions A110, A120 and A130.
[0259] Action A110
[0260] The user data node 120 may obtain the server IP address corresponding to the indication of the DNS domain name from the domain name node 200 .
[0261] Action A120
[0262] User data node 120 may receive other traffic from client application 115 that is identified by a destination IP address and that may be destined for a particular domain name.
[0263] Action A130
[0264] Before sending other traffic to the server application 190, the user data node 120 may verify that the destination IP address and the specific domain name match the obtained server IP address.
[0265] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0266] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0267] SNI can be used as a domain name.
[0268] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0269] refer to Figure 6 , showing Figure 1 1 is a schematic block diagram of an embodiment of a user data node 120.
[0270] The user data node 120 may include a processing unit 601, such as a device for performing the methods described herein. The device may be embodied in the form of one or more hardware units and / or one or more software units. Therefore, the term "unit" may refer to a circuit, a software block, etc. according to various embodiments described below.
[0271] The user data node 120 may further include a memory 602. The memory may include (eg, contain or store) instructions, for example in the form of a computer program 603 (which may include computer readable code means).
[0272] According to some embodiments herein, the user data node 120 and / or the processing unit 601 includes a processing circuit 604 as an exemplary hardware unit, which may include one or more processors. Therefore, the processing unit 601 may be embodied in the form of or implemented by the processing circuit 604. The instructions may be executed by the processing circuit 604, whereby the user data node 120 may be operable to perform Figure 2 and / or Figure 5 As another example, when the instructions are executed by the user data node 120 and / or the processing circuit 604, the user data node 120 may perform the following steps: Figure 2 and / or Figure 5 method.
[0273] In view of the above, in one example, a user data node 120 for managing traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170 is provided. As described above, the operator network 101 includes a session node 140 and a user data node 120. Similarly, the memory 602 contains instructions executable by the processing circuit 604, whereby the user data node 120 may be used to:
[0274] A management request including a packet flow description (PFD) rule for server application 190 is received from session node 140, wherein the PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol associated with the one or more protocol parameters, wherein the one or more protocol parameters include one or more of the following:
[0275] - indications related to the common name CNS,
[0276] - indications related to Domain Name System DNS domain names,
[0277] - Server Name Indication SNI,
[0278] - instructions related to fraud prevention,
[0279] - Indications related to the server IP address,
[0280] - IP header fields for IP protocol version,
[0281] - HTTP-host related instructions,
[0282] - HTTP-user-agent related instructions,
[0283] - HTTP-content-type related instructions,
[0284] - instructions related to HTTP-GET,
[0285] - instructions related to HTTP-POST,
[0286] - instructions related to HTTP-PUT,
[0287] - instructions related to HTTP-PATCH, and
[0288] - instructions related to HTTP-Response-Codes,
[0289] Receive traffic from client application 115 destined for server application 190,
[0290] Classifying the services according to the PFD rules, thereby obtaining the classified services, and
[0291] Actions are executed for the classified services, wherein the actions are based on PFD rules.
[0292] Figure 6Also shown is a carrier 605 or program carrier which provides (eg comprises, mediates, supplies, etc.) a computer program 603 such as described above. The carrier 605 may be one of an electric signal, an optical signal, a radio signal, and a computer readable medium.
[0293] In some embodiments, the user data node 120 and / or the processing unit 601 may include one or more of a receiving unit 610, a classification unit 620, an execution unit 630, an obtaining unit 640, and a verification unit 650 as example hardware units. When the term "unit" refers to a hardware unit, the term "unit" may refer to a circuit. In other examples, one or more of the aforementioned exemplary hardware units may be implemented as one or more software units.
[0294] Furthermore, the user data node 120 and / or the processing unit 601 may include an input / output unit 606, which may be instantiated by a receiving unit and / or a sending unit, when applicable.
[0295] Thus, the user data node 120 is configured to manage traffic between the client application 115 running in the communication device 110 and the server application 190 hosted by the application node 170. The operator network 101 comprises a session node 140 and a user data node 120.
[0296] Therefore, according to the above various embodiments, the user data node 120 and / or the processing unit 601 and / or the receiving unit 610 are configured to receive a management request including a packet flow description PFD rule for the server application 190 from the session node 140. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0297] Instructions related to the common name CNS,
[0298] Instructions related to Domain Name System DNS domain names,
[0299] Server Name Indication SNI,
[0300] Instructions relating to fraud prevention,
[0301] Indications related to the server IP address,
[0302] IP header fields for IP protocol version,
[0303] Instructions related to HTTP-host,
[0304] HTTP-user-agent related instructions,
[0305] Instructions related to HTTP-content-type,
[0306] HTTP-GET related instructions,
[0307] Instructions related to HTTP-POST,
[0308] Instructions related to HTTP-PUT,
[0309] HTTP-PATCH related instructions, and
[0310] Indications related to HTTP-Response-Codes.
[0311] The user data node 120 and / or the processing unit 601 and / or the receiving unit 610 are configured to receive traffic from the client application 115 destined for the server application 190 .
[0312] The user data node 120 and / or the processing unit 601 and / or the classification unit 620 are configured to classify the services according to the PFD rules, thereby obtaining the classified services.
[0313] The user data node 120 and / or the processing unit 601 and / or the execution unit 630 are configured to execute actions for the classified services. These actions are based on PFD rules.
[0314] In some embodiments, one or more protocol parameters may include an indication of a DNS domain name. In these embodiments, the user data node 120 and / or the processing unit 601 and / or the obtaining unit 640 may be configured to obtain a server IP address corresponding to the indication of the DNS domain name from the domain name node 200. In addition, the user data node 120 and / or the processing unit 601 and / or the receiving unit 610 may be configured to receive other services identified by the destination IP address and the specific domain name from the client application 115. In addition, the user data node 120 and / or the processing unit 601 and / or the verification unit 650 may be configured to verify that the destination IP address and the specific domain name match the obtained server IP address before sending other services to the server application 190.
[0315] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0316] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0317] SNI can be used as a domain name.
[0318] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0319] exist Figure 7 , a schematic flow chart of an exemplary method in a network open node 160 is shown. Again, the same reference numerals as above have been used to denote the same or similar features, in particular the same reference numerals have been used to denote the same or similar actions. Thus, the network open node 160 performs a method for enabling management of traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170. As described above, the operator network 101 includes the network open node 160 and the session node 140.
[0320] One or more of the following actions may be performed in any suitable order.
[0321] Action A010
[0322] The network open node 160 receives a packet flow description PFD rule for the server application 190 from the application node 170. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying services using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0323] Instructions related to the common name CNS,
[0324] Instructions related to Domain Name System DNS domain names,
[0325] Server Name Indication SNI,
[0326] Instructions relating to fraud prevention,
[0327] Indications related to the server IP address,
[0328] IP header fields for IP protocol version,
[0329] Instructions related to HTTP-host,
[0330] HTTP-user-agent related instructions,
[0331] Instructions related to HTTP-content-type,
[0332] HTTP-GET related instructions,
[0333] Instructions related to HTTP-POST,
[0334] Instructions related to HTTP-PUT,
[0335] HTTP-PATCH related instructions, and
[0336] Indications related to HTTP-Response-Codes.
[0337] Action A020
[0338] The network open node 160 sends the PFD rules to the session node 140 .
[0339] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0340] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0341] SNI can be used as a domain name.
[0342] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0343] refer to Figure 8 , showing Figure 1 FIG. 1 is a schematic block diagram of an embodiment of a network open node 160 .
[0344] The network open node 160 may include a processing unit 801, such as a device for performing the methods described herein. The device may be embodied in the form of one or more hardware units and / or one or more software units. Therefore, the term "unit" may refer to a circuit, a software block, etc. according to various embodiments described below.
[0345] The network open node 160 may further include a memory 802. The memory may include (eg, contain or store) instructions, for example in the form of a computer program 803 (which may include computer readable code means).
[0346] According to some embodiments of the present invention, the network open node 160 and / or the processing unit 801 includes a processing circuit 804 as an exemplary hardware unit. Therefore, the processing unit 801 can be embodied in the form of or implemented by the processing circuit 804. The instructions can be executed by the processing circuit 804, so that the network open node 160 can be operated to perform Figure 2 and / or Figure 7 As another example, these instructions, when executed by the network open node 160 and / or the processing circuit 804, may cause the network open node 160 to perform the following steps: Figure 2 and / or Figure 7 method.
[0347] In view of the above, in one example, a network open node 160 is provided for enabling management of traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170. As described above, the operator network 101 includes the network open node 160 and the session node 140. Again, the memory 802 contains instructions executable by the processing circuit 804, whereby the network open node 160 can be used to:
[0348] A packet flow description (PFD) rule for the server application 190 is received from the application node 170, wherein the PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters include one or more of the following:
[0349] - indications related to the common name CNS,
[0350] - indications related to Domain Name System DNS domain names,
[0351] - Server Name Indication SNI,
[0352] - instructions related to fraud prevention,
[0353] - Indications related to the server IP address,
[0354] - IP header fields for IP protocol version,
[0355] - HTTP-host related instructions,
[0356] - HTTP-user-agent related instructions,
[0357] - HTTP-content-type related instructions,
[0358] - instructions related to HTTP-GET,
[0359] - instructions related to HTTP-POST,
[0360] - instructions related to HTTP-PUT,
[0361] - instructions related to HTTP-PATCH, and
[0362] - indications related to HTTP-Response-Codes, and
[0363] The PFD rules are sent to session node 140 .
[0364] Figure 8 Also shown is a carrier 805 or program carrier which provides (eg comprises, mediates, supplies, etc.) a computer program 803 such as described above. The carrier 805 may be one of an electric signal, an optical signal, a radio signal, and a computer readable medium.
[0365] In other embodiments, the network open node 160 and / or the processing unit 801 may include one or more of the receiving unit 810 and the sending unit 820 as exemplary hardware units. When the term "unit" refers to a hardware unit, the term "unit" may refer to a circuit. In other examples, one or more of the aforementioned exemplary hardware units may be implemented as one or more software units.
[0366] Furthermore, the network open node 160 and / or the processing unit 801 may include an input / output unit 806 , which may be instantiated by a receiving unit and / or a sending unit when applicable.
[0367] Thus, the network open node 160 is configured to enable management of traffic between the client application 115 running in the communication device 110 and the server application 190 hosted by the application node 170. The operator network 101 comprises the network open node 160 and the session node 140.
[0368] Therefore, according to the above various embodiments, the network open node 160 and / or the processing unit 801 and / or the receiving unit 810 are configured to receive a packet flow description PFD rule for the server application 190 from the application node 170. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying services using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0369] Instructions related to the common name CNS,
[0370] Instructions related to Domain Name System DNS domain names,
[0371] Server Name Indication SNI,
[0372] Instructions relating to fraud prevention,
[0373] Indications related to the server IP address,
[0374] IP header fields for IP protocol version,
[0375] Instructions related to HTTP-host,
[0376] HTTP-user-agent related instructions,
[0377] Instructions related to HTTP-content-type,
[0378] HTTP-GET related instructions,
[0379] Instructions related to HTTP-POST,
[0380] Instructions related to HTTP-PUT,
[0381] HTTP-PATCH related instructions, and
[0382] Indications related to HTTP-Response-Codes.
[0383] The network open node 160 and / or the processing unit 801 and / or the sending unit 820 are configured to send the PFD rule to the session node 140 .
[0384] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0385] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0386] SNI can be used as a domain name.
[0387] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0388] exist Fig. 9, a schematic flow chart of an exemplary method in a session node 140 is shown. Again, the same reference numerals as above have been used to denote the same or similar features, in particular the same reference numerals have been used to denote the same or similar actions. Thus, the session node 140 performs a method for enabling management of traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170. As mentioned, the operator network 101 comprises a network open node 160, a session node 140 and a user data node 120.
[0389] One or more of the following actions may be performed in any suitable order.
[0390] Action A030
[0391] The session node 140 receives a packet flow description PFD rule for the server application 190 from the network open node 160. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0392] Instructions related to the common name CNS,
[0393] Instructions related to Domain Name System DNS domain names,
[0394] Server Name Indication SNI,
[0395] Instructions relating to fraud prevention,
[0396] Indications related to the server IP address,
[0397] IP header fields for IP protocol version,
[0398] Instructions related to HTTP-host,
[0399] HTTP-user-agent related instructions,
[0400] Instructions related to HTTP-content-type,
[0401] HTTP-GET related instructions,
[0402] Instructions related to HTTP-POST,
[0403] Instructions related to HTTP-PUT,
[0404] HTTP-PATCH related instructions, and
[0405] Indications related to HTTP-Response-Codes.
[0406] Action A040
[0407] Session node 140 sends a management request including the PFD rules to user data node 120 .
[0408] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0409] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0410] SNI can be used as a domain name.
[0411] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0412] refer to Fig.10 , showing Figure 1 A schematic block diagram of an embodiment of a session node 140 is provided.
[0413] The session node 140 may include a processing unit 1001, such as a device for performing the methods described herein. The device may be embodied in the form of one or more hardware units and / or one or more software units. Thus, the term "unit" may refer to a circuit, a software block, etc. according to various embodiments described below.
[0414] The session node 140 may also include a memory 1002. The memory may include (eg, contain or store) instructions, for example, in the form of a computer program 1003 (which may include computer readable code means).
[0415] According to some embodiments herein, session node 140 and / or processing unit 1001 include processing circuit 1004 as an exemplary hardware unit. Thus, processing unit 1001 may be embodied in the form of or implemented by processing circuit 1004. Instructions may be executed by processing circuit 1004, whereby session node 140 may be operable to perform Figure 2 and / or Fig. 9 As another example, the instructions, when executed by session node 140 and / or processing circuit 1004, may cause session node 140 to perform an operation according to Figure 2 and / or Fig. 9 method.
[0416] In view of the above, in one example, a session node 140 is provided for enabling management of traffic between a client application 115 running in a communication device 110 and a server application 190 hosted by an application node 170. As mentioned, the operator network 101 includes a network open node 160, a session node 140, and a user data node 120. Again, the memory 1002 contains instructions that can be executed by the processing circuit 1004, whereby the session node 140 can be used to:
[0417] A packet flow description (PFD) rule for the server application 190 is received from the network open node 160, wherein the PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters include one or more of the following:
[0418] - indications related to the common name CNS,
[0419] - indications related to Domain Name System DNS domain names,
[0420] - Server Name Indication SNI,
[0421] - instructions related to fraud prevention,
[0422] - Indications related to the server IP address,
[0423] - IP header fields for IP protocol version,
[0424] - HTTP-host related instructions,
[0425] - HTTP-user-agent related instructions,
[0426] - HTTP-content-type related instructions,
[0427] - instructions related to HTTP-GET,
[0428] - instructions related to HTTP-POST,
[0429] - instructions related to HTTP-PUT,
[0430] - instructions related to HTTP-PATCH, and
[0431] - indications related to HTTP-Response-Codes, and
[0432] A management request including the PFD rules is sent to the user data node 120 .
[0433] Fig.10 Also shown is a carrier 1005 or program carrier, which provides (eg, includes, accommodates, supplies, etc.) a computer program 1003, such as described above. The carrier 1005 may be one of an electric signal, an optical signal, a radio signal, and a computer readable medium.
[0434] In other embodiments, session node 140 and / or processing unit 1001 may include one or more of receiving unit 1010 and sending unit 1020 as exemplary hardware units. When the term "unit" refers to a hardware unit, the term "unit" may refer to a circuit. In other examples, one or more of the aforementioned exemplary hardware units may be implemented as one or more software units.
[0435] Furthermore, session node 140 and / or processing unit 1001 may include an input / output unit 1006, which may be instantiated by a receiving unit and / or a sending unit, as applicable.
[0436] Thus, the session node 140 is configured to enable management of traffic between the client application 115 running in the communication device 110 and the server application 190 hosted by the application node 170. The operator network 101 comprises a network open node 160, a session node 140 and a user data node 120.
[0437] Therefore, according to the above various embodiments, the session node 140 and / or the processing unit 1001 and / or the receiving unit 1010 are configured to receive a packet flow description PFD rule for the server application 190 from the network open node 160. The PFD rule includes a packet flow description identifier and one or more protocol parameters for classifying a service using a protocol related to the one or more protocol parameters. The one or more protocol parameters include one or more of the following:
[0438] Instructions related to the common name CNS,
[0439] Instructions related to Domain Name System DNS domain names,
[0440] Server Name Indication SNI,
[0441] Instructions relating to fraud prevention,
[0442] Indications related to the server IP address,
[0443] IP header fields for IP protocol version,
[0444] Instructions related to HTTP-host,
[0445] HTTP-user-agent related instructions,
[0446] Instructions related to HTTP-content-type,
[0447] HTTP-GET related instructions,
[0448] Instructions related to HTTP-POST,
[0449] Instructions related to HTTP-PUT,
[0450] HTTP-PATCH related instructions, and
[0451] Indications related to HTTP-Response-Codes.
[0452] The session node 140 and / or the processing unit 1001 and / or the sending unit 1020 are configured to send a management request including the PFD rule to the user data node 120 .
[0453] The PFD rule may include a protocol identifier for identifying a protocol associated with one or more protocol parameters.
[0454] The indication related to the server IP address may also be related to the server port at layer 4 and / or layer 7 of the OSI protocol stack.
[0455] SNI can be used as a domain name.
[0456] The PFD rule may also include at least one of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information. In some examples, the management request may also include one or more of a PFD version, a PFD origin, an MNO identifier identifying the mobile network operator to which the PFD rule applies, and configuration information.
[0457] As used herein, the term "node" or "network node" may refer to one or more physical entities, such as devices, apparatuses, computers, servers, etc. This may mean that the embodiments of the present invention may be implemented in one physical entity. Alternatively, the embodiments of the present invention may be implemented in multiple physical entities, such as arrangements including one or more physical entities, that is, the embodiments may be implemented in a distributed manner, such as on a cloud system, which may include a group of server computers. In the case of a cloud system, the term "node" may refer to a virtual machine, such as a container, a virtual runtime environment, etc. Virtual machines may be assembled from hardware resources (e.g., memory, processing, network, and storage resources) that may reside in different physical machines (e.g., in different computers).
[0458] As used herein, the term "unit" may refer to one or more functional units, each of which may be implemented as one or more hardware units and / or one or more software units and / or combined software / hardware units in a node. In some examples, a unit may represent a functional unit implemented as software and / or hardware of a node.
[0459] As used herein, the term "computer program carrier", "program carrier" or "carrier" may refer to one of an electric signal, an optical signal, a radio signal, and a computer-readable medium. In some examples, the computer program carrier may exclude transient propagating signals such as electric, optical and / or radio signals. Thus, in these examples, the computer program carrier may be a non-transitory carrier, such as a non-transitory computer-readable medium.
[0460] As used herein, the term "processing unit" may include one or more hardware units, one or more software units, or a combination thereof. Any such unit (whether hardware, software, or a combined hardware-software unit) may be a determining device, an estimating device, a capturing device, an associating device, a comparing device, an identifying device, a selecting device, a receiving device, a sending device, etc., as disclosed herein. As an example, the expression "device" may be a unit corresponding to the units listed above in conjunction with the accompanying drawings.
[0461] As used herein, the term "software unit" may refer to a software application, a dynamic link library (DLL), a software component, a software object, an object according to the Component Object Model (COM), a software function, a software engine, an executable binary software file, etc.
[0462] The term "processing unit" or "processing circuit" herein may encompass a processing unit including, for example, one or more processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc. A processing circuit, etc. may include one or more processor cores.
[0463] As used herein, the expression “configured to / for” may mean that the processing circuit is configured to (such as adapted to or operable to) perform one or more actions described herein by means of software configuration and / or hardware configuration.
[0464] As used herein, the term "action" may refer to an action, step, operation, response, reaction, activity, etc. It should be noted that, where applicable, an action herein may be divided into two or more sub-actions. In addition, also where applicable, it should be noted that two or more actions described herein may be combined into a single action.
[0465] As used herein, the term "memory" may refer to a hard disk, a magnetic storage medium, a portable computer disk or diskette, flash memory, random access memory (RAM), etc. In addition, the term "memory" may refer to an internal register memory of a processor or the like.
[0466] As used herein, the term "computer-readable medium" may be a Universal Serial Bus (USB) memory, a Digital Versatile Disc (DVD), a Blu-ray Disc, a software unit received as a data stream, a flash memory, a hard drive, a memory card such as a MemoryStick, a MultiMedia Card (MMC), a Secure Digital (SD) card, etc. One or more of the above examples of computer-readable media may be provided as one or more computer program products.
[0467] As used herein, the term "computer readable code unit" may be the text of a computer program, a partial or complete binary file representing a computer program in a compiled format, or anything in between.
[0468] As used herein, the expressions "transmit" and "send" are considered interchangeable. These expressions include transmission by broadcast, unicast, multicast, etc. In this context, a transmission by broadcast can be received and decoded by any authorized device within range. In the case of unicast, one specifically addressed device can receive and decode the transmission. In the case of multicast, a group of specifically addressed devices can receive and decode the transmission.
[0469] As used herein, the terms "quantity" and / or "value" may be any kind of number, such as binary, real, imaginary or rational numbers, etc. In addition, a "quantity" and / or "value" may be one or more characters, such as letters or strings of letters. A "quantity" and / or "value" may also be represented by a string of bits (i.e., 0 and / or 1).
[0470] As used herein, unless obvious from the context, the terms “first”, “second”, “third”, etc. are only used to distinguish features, devices, elements, units, etc. from one another.
[0471] As used herein, the term "subsequent action" may refer to performing one action after a previous action, while additional actions may or may not be performed before the one action but after the previous action.
[0472] As used herein, the term "a group" may refer to one or more things. For example, according to embodiments of the present invention, a group of devices may refer to one or more devices, a group of parameters may refer to one or more parameters, and the like.
[0473] As used herein, the expression "in some embodiments" has been used to indicate that features of a described embodiment can be combined with any other embodiments disclosed herein.
[0474] Although various embodiments have been described, many different variations, modifications, etc. thereof will become apparent to those skilled in the art. Therefore, the described embodiments are not intended to limit the scope of the present disclosure.
Claims
1. A method for managing traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), performed by an operator network (101) comprising a network open node (160), a session node (140) and a user data node (120), wherein: The method comprises: The network open node (160) receives (A010) a packet flow description (PFD) rule for the server application (190) from the application node (170), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, sending (A020) the PFD rules from the network open node (160) to the session node (140), sending (A040) a management request including the PFD rule from the session node (140) to the user data node (120), receiving (A080) traffic from the client application (115) to the server application (190) by the user data node (120), The user data node (120) classifies the service according to the PFD rule (A090), thereby obtaining the classified service, and The user data node (120) performs (A100) an action on the classified service, wherein the action is based on the PFD rule.
2. The method according to claim 1, wherein: The PFD rule includes a protocol identifier for identifying a protocol associated with the one or more protocol parameters.
3. The method according to claim 1 or 2, wherein: The one or more protocol parameters include an indication related to a server IP address, and the indication related to the server IP address is further related to a server port at layer 4 and / or layer 7 of the OSI protocol stack.
4. The method according to claim 1 or 2, wherein: The one or more protocol parameters include an indication of a DNS domain name, the method comprising: The user data node (120) obtains (A110) a server IP address corresponding to the indication of the DNS domain name from the domain name node (200), receiving (A120) by the user data node (120) from the client application (115) other traffic identified by a destination IP address and a specific domain name, and Before sending the other service to the server application (190), the user data node (120) verifies (A130) that the destination IP address and the specific domain name match the obtained server IP address.
5. The method according to claim 1 or 2, wherein: The method further comprises: triggering (A060) a PDU session establishment procedure from the client application (115) to the user data node (120), and A transaction is initiated (A070) from the client application (115) to the server application (190).
6. The method according to claim 1 or 2, wherein: The PFD rule includes at least one of: a PFD version, a PFD origin, an MNO identifier identifying a mobile network operator to which the PFD rule applies, and configuration information.
7. A method performed by a user data node (120) for managing traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The method comprises: receiving (A050) from a session node (140) a management request comprising a packet flow description (PFD) rule for the server application (190), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, receiving (A080) traffic from said client application (115) destined for said server application (190), classifying the service according to the PFD rule (A090), thereby obtaining the classified service, and An action is performed (A100) for the classified service, wherein the action is based on the PFD rule.
8. The method according to claim 7, wherein: The one or more protocol parameters include an indication of a DNS domain name, the method comprising: obtaining (A110) from the domain name node (200) a server IP address corresponding to the indication of the DNS domain name, receiving (A120) from said client application (115) other traffic identified by a destination IP address and a specific domain name, and Before sending the other service to the server application (190), verifying (A130) that the destination IP address and the specific domain name match the obtained server IP address.
9. A method performed by a network open node (160) for enabling management of traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The method comprises: receiving (A010) a packet flow description (PFD) rule for the server application (190) from the application node (170), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, and The PFD rules are sent (A020) to a session node (140).
10. A method performed by a session node (140) for enabling management of traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The method comprises: receiving (A030) a packet flow description (PFD) rule for the server application (190) from a network open node (160), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, and A management request including the PFD rule is sent (A040) to a user data node (120).
11. An operator network (101), comprising a network open node (160), a session node (140) and a user data node (120), and configured to manage traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The operator network (101) is also configured to: The network open node (160) receives a packet flow description (PFD) rule for the server application (190) from the application node (170), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, sending (A020) the PFD rules from the network open node (160) to the session node (140), sending (A040) a management request including the PFD rule from the session node (140) to the user data node (120), receiving (A080) traffic from the client application (115) to the server application (190) by the user data node (120), The user data node (120) classifies the service according to the PFD rule (A090), thereby obtaining the classified service, and The user data node (120) performs (A100) an action on the classified service, wherein the action is based on the PFD rule.
12. The operator network (101) according to claim 11, wherein: The PFD rule includes a protocol identifier for identifying a protocol associated with the one or more protocol parameters.
13. The operator network (101) according to claim 11 or 12, wherein: The one or more protocol parameters include an indication related to a server IP address, and the indication related to the server IP address is further related to a server port at layer 4 and / or layer 7 of the OSI protocol stack.
14. The operator network (101) according to claim 11 or 12, wherein: The one or more protocol parameters include an indication of a DNS domain name, and the operator network (101) is further configured to: The user data node (120) obtains (A110) a server IP address corresponding to the indication of the DNS domain name from the domain name node (200), receiving (A120) by the user data node (120) from the client application (115) other traffic identified by a destination IP address and a specific domain name, and Before sending the other service to the server application (190), the user data node (120) verifies (A130) that the destination IP address and the specific domain name match the obtained server IP address.
15. The operator network (101) according to claim 11 or 12, wherein: The operator network (101) is also configured to: triggering (A060) a PDU session establishment procedure from the client application (115) to the user data node (120), and A transaction is initiated (A070) from the client application (115) to the server application (190).
16. The operator network (101) according to claim 11 or 12, wherein: The PFD rule includes at least one of: a PFD version, a PFD origin, an MNO identifier identifying a mobile network operator to which the PFD rule applies, and configuration information.
17. A user data node (120) configured to manage traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The user data node (120) comprises a processing unit configured to: receiving (A050) from a session node (140) a management request comprising a packet flow description (PFD) rule for the server application (190), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, receiving (A080) traffic from said client application (115) destined for said server application (190), classifying the services according to the PFD rules (A090), thereby obtaining classified services, and An action is performed (A100) for the classified service, wherein the action is based on the PFD rule.
18. The user data node (120) according to claim 17, wherein: The one or more protocol parameters include an indication of a DNS domain name, and the processing unit is configured to: obtaining (A110) from the domain name node (200) a server IP address corresponding to the indication of the DNS domain name, receiving (A120) other traffic from said client application (115) identified by a destination IP address and a specific domain name, and Before sending the other traffic to the server application (190), verifying (A130) that the destination IP address and the specific domain name match the obtained server IP address.
19. A network open node (160) configured to enable management of traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The network open node (160) comprises a processing unit, wherein the processing unit is configured to: receiving (A010) a packet flow description (PFD) rule for the server application (190) from the application node (170), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, and The PFD rules are sent (A020) to the session node (140).
20. A session node (140) configured to enable management of traffic between a client application (115) running in a communication device (110) and a server application (190) hosted by an application node (170), wherein: The session node (140) comprises a processing unit configured to: receiving (A030) a packet flow description (PFD) rule for the server application (190) from a network open node (160), wherein the PFD rule comprises a packet flow description identifier and one or more protocol parameters for classifying traffic using a protocol related to the one or more protocol parameters, wherein the one or more protocol parameters comprise an indication related to fraud prevention as a command for activating a fraud prevention process, and A management request including the PFD rule is sent (A040) to a user data node (120).
21. A non-transitory computer readable medium comprising computer readable code means which, when executed on a user data node (120), causes the user data node (120) to perform the method according to claim 7 or 8.
22. A non-transitory computer readable medium comprising computer readable code means which, when executed on a network open node (160), causes the network open node (160) to perform the method according to claim 9.
23. A non-transitory computer readable medium comprising computer readable code means which, when executed on a session node (140), causes the session node (140) to perform the method according to claim 10.
