First node, second node, another node, communication system and method performed thereby for handling session for application of device

Abstract

A computer-implemented method performed by a first node (111). The method is for handling a session of a device (130) for an application. The first node (111) and the device (130) operate in the communication system (100). The first node (111) obtains (401) a first indication directly or indirectly from a second node (112) operating in the communication system (100). The first indication comprises first information capable of identifying one or more third nodes (113) operating in the communication system (100). The one or more third nodes (113) open services of an operator that serves the device (130) 's session for the application. An operator operates in a communication system (100). The first node (111) also initiates (405) providing the first information to another node (114) external to the communication system (100) in response to the acquired first indication. The other node (114) serves the device (130) in a session for the application.

Description

Technical Field

[0001] The present disclosure generally relates to a first node and a method implemented thereby for handling application-specific sessions for a device. The present disclosure also generally relates to a second node and a method implemented thereby for handling application-specific sessions for a device. The present disclosure also generally relates to another node and a method implemented thereby for handling application-specific sessions for a device operating in a communication system. The present disclosure also generally relates to a communication system including a first node, a second node, and another node. Background Art

[0002] A computer system in a communication network or system may include one or more nodes. A node may include processing circuitry, memory, a receiving port, and a transmitting port. The processing circuitry, together with computer program code, may perform various functions and actions. A node may be, for example, a server. A node may perform its functions entirely in the cloud.

[0003] A communication system can cover a geographic area that can be divided into cell areas, each of which is served by a type of node, such as a network node, radio network node, or transmission point (TP) in the radio access network (RAN). For example, an access node such as a base station (BS), such as a radio base station (RBS), which may sometimes be referred to as, for example, a gNB, evolved Node B ("eNB"), "eNodeB," "NodeB," "NodeB," or "Node B," or a base transceiver station (BTS), depending on the technology and terminology used. Base stations can be categorized into different types based on transmit power and, therefore, cell size, such as wide-area base stations, medium-range base stations, local-area base stations, and home base stations. A cell can be understood as a geographic area where a base station can provide radio coverage at a base station site. A base station located at a base station site can serve one or more cells. Furthermore, each base station can support one or more communication technologies. The telecommunications network may also include network nodes that can provide beamforming services to receiving nodes (e.g., user equipment).

[0004] The standardization organization Third Generation Partnership Project (3GPP) is currently developing a new radio interface called Next Generation Radio or New Radio (NR) or 5G-Universal Terrestrial Radio Access (UTRA), and a Fifth Generation (5G) packet core network, which can be called 5G Core Network (5GC), abbreviated as 5GC.

[0005] Figure 1 is a schematic diagram depicting a specific example of the 5G reference architecture defined by 3GPP, which may be used as a reference for the present disclosure. An Application Function (AF) 1 may interact with the 3GPP core network through a Network Exposure Function (NEF) 2. AF 1 may allow external parties to use open Application Program Interfaces (APIs) provided by a Mobile Network Operator (MNO). If the AF may be trusted, for example, within a network operator, the AF may interact directly with the 3GPP core network without involving the NEF. NEF 2 may support different functionalities, such as a set of APIs, such as sponsored data, Quality of Service (QoS), etc., which may allow content providers to request policies from the MNO, for example, on a per-user session and / or application basis. NEF 2 may be understood as acting as an entry point into the operator's network, so that external AFs (e.g., content providers) may interact with the 3GPP core network through NEF 2.

[0006] The Unified Data Repository (UDR) (not depicted) can store data grouped into different subscription-related information sets: subscription data, policy data, structured data for exposure, and application data. The Unified Data Management Function (UDM) 3 can generate 3GPP 5G AKA authentication vectors, handle user identification processing, support UE service network function (NF) registration management (for example, storing the UE's service access and mobility function (AMF), storing the UE's protocol data unit (PDU) session service session management function (SMF), etc.), support retrieval of the UE's individual subscription data for slice selection, and process subscription data for network exposure functions applicable to a single UE or UE group. The Policy Control Function (PCF) 4 can support a unified policy framework to manage network behavior. Specifically, PCF 4 can provide Policy and Charging Control (PCC) rules to the Policy and Charging Enforcement Function (PCEF). Figure 1Not depicted in the figure. The SMF 5 / User Plane Function (UPF) 6 can execute policy and charging decisions according to the specified Policy and Charging Control (PCC) rules. The SMF 5 can support different functions, such as session establishment, modification and release, as well as policy-related functionality, such as terminating interfaces towards policy control functions, charging data collection, supporting charging interfaces, and controlling and coordinating charging data collection at the UPF 6. Specifically, the SMF 5 can receive PCC rules from the PCF 4 and configure the UPF 6, for example, to perform event reporting accordingly via the following N47 reference point, the Packet Flow Control Protocol (PFCP) protocol. The SMF 5 can control packet processing in the UPF 6 by establishing, modifying, or deleting PFCP sessions and by providing (e.g., adding, modifying, or deleting) packet detection rules (PDRs), forwarding action rules (FARs), quality enforcement rules (QERs), and / or usage reporting rules (URRs) for each PFCP session, whereby a PFCP session can correspond to a single PDU session or an independent PFCP session that is not bound to any PDU session. Each packet data rule (PDR) can contain a packet identifier (PDI) that specifies a traffic filter or signature to which an incoming packet can match. Each PDR can be associated with the following rules, which provide a set of instructions to be applied to packets matching the PDR: a) a FAR, which can contain instructions related to the processing of the packet, specifically, forwarding, redirecting, applying header enhancements, duplicating, dropping, or buffering the packet with or without notifying the CP function of the arrival of the DL packet; b) zero, one, or more QERs, which can contain instructions related to QoS enforcement for the traffic; and c) zero, one, or more URRs, which can contain instructions related to traffic measurement and reporting. 3GPP TS 29.244, v18.0.1 supports the SMF requesting triggering of header enhancements from the UPF via a FAR containing a Header Enhancement Information Element (IE). The UPF 6 can support processing of user plane traffic based on rules received from the SMF 5, specifically, for example, packet inspection via the PDR, and different enforcement actions such as traffic steering, QoS, and charging / reporting, for example, via the FAR, QER, and / or URR. The PCF 4 can provide policy rules to the UE 8 via the AMF 9.The AMF 9 may manage the access of the UE 8 , for example, when the UE 8 may connect through different access networks, and the mobility aspects of the UE 8 . Figure 1 Also depicted are a Network Slice Selection Function (NSSF) 10, a Network Repository Function (NRF) 11, an Authentication Server Function (AUSF) 12, a Radio Access Network (RAN) 13, and a Data Network (DN) 14. Each of the NSSF 10, NEF 2, NRF 11, PCF 4, UDM 3, AF 1, AUSF 12, AMF 9, SMF 5, UE 8, RAN 13, UPF 6, and DN 14 may have an interface through which they may be accessed, which may be, as shown, Nnssf 15, Nnef 16, Nnrf 17, Npcf 18, Nudm 19, Naf 20, Nausf 21, Namf 22, Nsmf 23, N1 24, and N2 25, respectively. The RAN 13 may have an interface N3 26 with the UPF 6 , and the UPF 6 may have an interface N6 27 with the DN 14 .

[0007] Common API Framework (CAPIF)

[0008] The CAPIF framework may be understood as allowing a content provider acting as an AF or an application programming interface (API) caller to request different services provided by an MNO, for example, through different APIs. Figure 22e reference point 28, which can be understood as existing between the API caller 22 and the API provider domain 29, can be used by the API caller 22 outside the PLMN trust domain 24 to call the requested service API 25, authenticate, and obtain authorization. Similarly, the CAPIF-2 reference point 30, which can be understood as existing between the API caller 27 and the service API 25 within the PLMN trust domain 24, can be used by the API caller 27 within the PLMN trust domain 24 to call the requested service API provided by the MNO (PLMN). The CAPIF-3 reference point 31, which can be understood as existing between the API exposure function 32 and the CAPIF core function 23, can be used. The CAPIF-4 reference point 33, which can be understood as existing between the API publishing function 34 and the CAPIF core function 23, can be used to control access and policy-related aspects of service API communications initiated by the API caller. The CAPIF-5 reference point 35, which can be understood as existing between the API management function 36 and the CAPIF core function 23, can be used to publish service API information. The CAPIF API 37 can be understood as being used to manage service APIs, API callers, and API provider domain function information.

[0009] Traffic encryption and content enhancement

[0010] Traffic encryption is becoming increasingly important in mobile networks, and encryption mechanisms are becoming increasingly sophisticated. In particular, most applications today are not based on plaintext Hypertext Transport Protocol (HTTP), but rather on Hypertext Transfer Protocol Secure (HTTPS) using Transport Layer Security (TLS). Furthermore, a significant portion of traffic is transmitted over Quick User Datagram Protocol Internet Connections (QUIC), which can be considered to have a higher level of encryption than TLS.

[0011] Based on the above encryption trends and due to the fact that the HTTP header enhancement of UPF can only be used for traffic in plain text HTTP as part of the 3GPP Best Practices of PFCP (BEPoP) study project, a solution has been approved where, based on operator policy, when the User Equipment (UE) can initiate the TLS handshake procedure to use HTTPS between the UE and the AS, the SMF can instruct the UPF to insert the information as a TLS extension in the Client Hello message to the Application Server (AS).

[0012] Existing methods of handling a UE's application-specific sessions (eg, requesting different services provided by an MNO through different APIs) may result in inefficient signaling between the involved entities, leading to high signaling overhead and long delays. Summary of the Invention

[0013] As part of the development of the embodiments herein, one or more challenges faced by the prior art will first be identified and discussed.

[0014] According to existing methods, the NEF can open a set of APIs to third-party content / application providers to interact with the operator network. In order to utilize the APIs provided by the NEF, the AS or AF may need to know which mobile operator network the client requesting the application resources may be using. As an example, when an AS (e.g., an online movie provider) may receive traffic for a specific application (e.g., a movie delivery session), the AS does not know which MNO (e.g., telecom provider A or telecom provider B) may be handling the traffic, and therefore does not know which NEF (e.g., telecom provider A's NEF or telecom provider B's NEF) to contact.

[0015] The CAPIF framework can be understood as assuming a Service Level Agreement (SLA) may exist between a content provider (i.e., AF) and an MNO (i.e., NEF). Therefore, the content provider knows the address of the MNO entry point (i.e., CAPIF core function) via CAPIF-1e, for example, as part of the SLA. This is impossible without an SLA. An example is a user browsing the example.com website via a browser. It is possible that example.com, acting as the AF, may want to trigger the NNEF "AS Session with QoS" API to, for example, provide high QoS for a movie provider's traffic. However, it does not know which CAPIF core function to contact via CAPIF-1e, or which NEF to contact via CAPIF-2e, to request high QoS from the MNO in this example. Furthermore, as mentioned above, the AF does not know which MNO to contact. The movie provider's server (i.e., AS / AF) may only see the source Internet Protocol (IP) address from the received packet, which does not identify the MNO, such as telecom provider A or telecom provider B. Therefore, if the AS / AF wants to trigger eg the Nnef "AS Session with QoS" API, eg to provide high QoS to a movie provider's traffic, it does not know which MNO's CAPIF core functionality and / or NEF it should contact.

[0016] Based on the above, there are two problems related to NEF discovery. The first is the AF discovering the MNO, such as telecom provider A. The AF may have locally configured / stored a list of CAPIF core functions and NEFs on a per-MNO basis. In this case, the AF can trigger a request for the CAPIF core functions of that MNO simply by knowing the MNO. The second problem is the AF discovering the CAPIF core functions and / or NEF instances of the MNO (such as telecom provider A) discovered in the previous problem. These problems can be understood to apply to the following two situations: there may be no SLA between the content provider and the MNO, and there may be an SLA between the content provider and the MNO but the content provider does not know which MNO to contact.

[0017] The first case, where an SLA may not exist between the content provider and the MNO, is a relevant case, as it can be understood that there are a large number of content providers, and the MNO may not be able to manage SLAs with all of them. The second case, where an SLA may exist between the content provider and the MNO but the content provider does not know which MNO to contact, can be understood as limiting the deployability and applicability of the NEF interface.

[0018] The consequence of the above problem can be understood as that the services provided by the network operator (such as requesting the MNO to apply specific QoS to AF application traffic, such as the Nnef_AFsessionWithQoS service, requesting the MNO to sponsor AF application traffic, such as the Nnef_ChargeableParty service, or requesting the MNO to route AF application traffic in a specific way, such as the Nnef_TrafficInfluence service) are not discoverable and usable for new applications that may not have SLAs and applications that may have SLAs.

[0019] The embodiments herein may be understood to provide a mechanism that may address the above-mentioned issues and may be based on defining new procedures to make one or more nodes within a communication system discoverable by nodes operating outside the communication system.

[0020] In light of the foregoing, it is an object of embodiments herein to improve the handling of application-oriented sessions for devices via a communication system.

[0021] According to a first aspect of the embodiments herein, the objective is achieved by a computer-implemented method executed by a first node. The method comprises processing a session for an application on a device. The first node and the device operate in a communication system. The first node obtains a first indication, directly or indirectly, from a second node operating in the communication system. The first indication includes first information capable of identifying one or more third nodes operating in the communication system. The one or more third nodes provide services of an operator that provides services for the session for the application on the device. The operator operates in the communication system. Then, in response to the obtained first indication, the first node initiates provision of the first information to another node outside the communication system. The other node serves the device in the session for the application.

[0022] According to a second aspect of the embodiments herein, the objective is achieved by a computer-implemented method executed by a second node. The method is configured to process a session for an application on a device. The second node and the device operate in a communication system. The second node obtains first information capable of identifying one or more third nodes operating in the communication system. The one or more third nodes provide services to an operator that provides services for the session for the application on the device. The operator operates in the communication system. The second node also initiates provision of the first information to another node external to the communication system via the first node operating in the communication system. The first node and the other node serve the device in the session for the application.

[0023] According to a third aspect of the embodiments herein, the object is achieved by a computer-implemented method performed by another node. The other node is configured to process an application-specific session for a device operating in a communication system. The other node is external to the communication system. The other node serves the device in the application-specific session. The other node obtains first information from a first node operating in the communication system. The first information can identify one or more third nodes operating in the communication system. The one or more third nodes provide services of an operator that provides services for the application-specific session of the device. The operator operates in the communication system. The other node then determines the identity of the one or more third nodes in response to the obtained first information. The other node also initiates a third request for services for the session application to at least one of the identified one or more third nodes 113.

[0024] According to a fourth aspect of the embodiments of this document, the purpose is achieved by a first node for processing a session for an application of a device. The first node and the device are configured to operate in a communication system. The first node is configured to directly or indirectly obtain a first indication from a second node configured to operate in the communication system. The first indication is configured to include first information, and the first information is configured to be able to identify one or more third nodes configured to operate in the communication system. The one or more third nodes are configured to open the services of an operator configured to provide services for the session for an application of the device. The operator is configured to operate in the communication system. The first node is also configured to initiate the provision of the first information to another node outside the communication system in response to the first indication configured to be obtained. The other node is configured to serve the device in the session for the application.

[0025] According to a fifth aspect of the embodiments of this document, the purpose is achieved by a second node for processing a session for an application of a device. The second node and the device are configured to operate in a communication system. The second node is configured to obtain first information, which is configured to be able to identify one or more third nodes configured to operate in the communication system. The one or more third nodes are configured to open the services of an operator configured to provide services for the session for the application of the device. The operator is configured to operate in the communication system. The second node is also configured to initiate the provision of the first information to another node outside the communication system via the first node configured to operate in the communication system. The first node and the other node are configured to serve the device in the session for the application.

[0026] According to a sixth aspect of the embodiments of this document, the purpose is achieved by another node for processing an application-specific session for a device configured to operate in a communication system. The another node is configured to be external to the communication system. The another indication is configured to serve the device in the application-specific session. The another node is further configured to obtain first information from a first node configured to operate in the communication system. The first information is configured to be able to identify one or more third nodes configured to operate in the communication system. The one or more third nodes are configured to open services of an operator configured to provide services for the application-specific session of the device. The operator is configured to operate in the communication system. The another node is further configured to determine the identity of the one or more third nodes in response to the first information configured to be obtained. The another node is further configured to initiate a third request for service for the session application to at least one of the one or more third nodes configured to be identified.

[0027] According to a seventh aspect of the embodiments of this document, the object is achieved by a communication system comprising a first node, a second node and another node.

[0028] By obtaining the first indication, the first node may be enabled to initiate providing the first information to another node.

[0029] Because the first information enables identification of one or more third nodes that offer services of the operator that provides services for the device's application-specific session, the first node, by initiating provision of the first information to another node, can enable the other node to contact the one or more third nodes to discover which services of the operator that provides services for the device's application-specific session are available to the device. As an external node to the communication system, the other node may not have other means to obtain this information or to easily obtain this information.

[0030] In situations where an SLA may exist between the MNO and another node (e.g., a content provider), a first node can enable the other node to obtain the first information. In this case, the MNO can share all configuration modifications to use one or more third nodes, such as the Nnef API. This can be understood as providing flexibility, such as enabling the server hosting the API to be moved without hard-coded information. Furthermore, even in situations where an SLA may not exist between the MNO and the other node, the first node can enable the other node to obtain the first information. In this case, the MNO can advertise available services to the other node and allow the other node to begin communicating via one or more third nodes (e.g., the Nnef API) to begin obtaining network services. This can then enable the other node to not only provide those services to the device (e.g., for application-specific sessions), but also avoid relying on existing SLAs and / or having to contact another node (e.g., from another MNO) that may not serve the device to learn what those services may be. For example, the other node can be enabled to identify one or more third nodes (e.g., CAPIF core functionality and / or NEF instances) and trigger an API service request, such as requesting a specific QoS for application traffic.

[0031] By acquiring the first information, the second node may be able to provide the first information to the first node.

[0032] By initiating the provision of the first information, the second node can directly or indirectly forward the retrieved first information to the first node. As described above, this can then enable the first node to provide the first information to another node outside the communication system that might otherwise be unable to access the information. This can ultimately enable the fourth node to identify one or more third nodes that offer the services of an operator that provides services for the device's application-specific session.

[0033] By obtaining the first information from the first node, the other node can then be enabled to determine the identity of one or more third nodes (e.g., CAPIF core functions and / or NEF instances), thereby opening the services of the operator that provides services for the device's application-oriented sessions. The other node is then enabled to contact the one or more third nodes (e.g., NEF) and trigger a request for a service, such as an API service request, such as an AF session with a QoS API. This can be done in a more efficient manner, with less signaling and lower latency, because the other node may not need to contact nodes of other operators (e.g., NEFs) that may not serve the device. In addition, as described above, the other node can obtain the first information independently of whether an SLA exists between the MNO and the other node. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] According to the following description, examples of embodiments of this document are described in more detail with reference to the accompanying drawings.

[0035] Figure 1 is a schematic diagram illustrating an example of a 5G network architecture according to an existing approach.

[0036] Figure 2 is a diagram illustrating an example of a CAPIF interface according to an existing method.

[0037] Figure 3 is a schematic diagram illustrating a non-limiting example of a communication system according to embodiments herein.

[0038] Figure 4 is a flow chart depicting an embodiment of a method in a first node according to embodiments herein.

[0039] Figure 5 is a flow chart depicting an embodiment of a method in a second node according to embodiments herein.

[0040] Figure 6 is a flow chart depicting an embodiment of a method in another node according to embodiments herein.

[0041] Figure 7 is a schematic diagram illustrating a non-limiting example of signaling between nodes in a communication system according to embodiments herein.

[0042] Figure 8 are schematic block diagrams illustrating two non-limiting examples a) and b) of a first node according to embodiments herein.

[0043] Figure 9 are schematic block diagrams illustrating two non-limiting examples a) and b) of a second node according to embodiments herein.

[0044] Figure 10 are schematic block diagrams illustrating two non-limiting examples a) and b) of another node according to embodiments herein. DETAILED DESCRIPTION

[0045] Certain aspects of the present disclosure and embodiments thereof address one or more challenges present in existing approaches and provide solutions to the challenges discussed.

[0046] Embodiments herein may relate to methods for discovering one or more nodes inside a communication system by a node outside the communication system. More particularly, embodiments herein may relate to methods for discovering MNOs, CAPIF core functions, and NEF instances by a node outside the communication system (e.g., a content provider). Other specific embodiments herein may provide a mechanism that may be understood as solving the above-mentioned problem and may indicate user plane application content enhancement based on the 5GC control plane, for example, based on each user's PDU session and / or based on each application. Content enhancement may apply the following parameters: Mobile Network Code (MNC)-Mobile Country Code (MCC), CAPIF core function instance ID (which may be understood as processing the user's PDU session), NEF instance ID (which may be understood as processing the user's PDU session), and optionally, Nnef available APIs for the user's application session.

[0047] In summary, the embodiments of this document can provide a simple mechanism based on content enhancement at a node that processes the user plane for a user (e.g., UPF), a method for an AF as a content provider to discover an MNO and information indicating one or more nodes within the communication system, such as a CAPIF core function instance ID and a NEF instance ID, which can process the PDU session of a subscriber.

[0048] Embodiments will now be described more fully below with reference to the accompanying drawings in which examples are shown. In this section, the embodiments herein are described by exemplary embodiments. It should be noted that these embodiments are not mutually exclusive. Components from one embodiment or example can be assumed to exist in another embodiment or example by default, and how to use those components in other exemplary embodiments will be clear to those skilled in the art. In order to simplify the description, not all possible combinations are described.

[0049] Figure 3 Two non-limiting examples of communication systems 100 in which embodiments herein may be implemented are depicted in panels "a" and "b," respectively. In some exemplary embodiments, for example Figure 3 As depicted in the non-limiting example of FIG. 1 , the communication system 100 may be a computer network. In other example embodiments, for example, Figure 3As depicted in the non-limiting example of FIG. 1 , the communication system 100 can be implemented in a telecommunications system, sometimes also referred to as a telecommunications network, a cellular radio system, a cellular network, or a wireless communication system. In some examples, the telecommunications system can include a network node that can serve a receiving node (e.g., a wireless device). The communication system 100 can be, for example, a network such as a 5G system, or a newer system or Long-Term Evolution (LTE) network supporting similar functionality, such as LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), or LTE operating in a common frequency band.The communication system 100 may also use other technologies, such as Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System Terrestrial Radio Access (UTRA) TDD, Global System for Mobile Communications (GSM) network, GSM / GSM Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, a network including any combination of Radio Access Technology (RAT), such as Multi-Standard Radio (MSR) base station, multi-RAT base station, etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network (WLAN) or WiFi network, Worldwide Interoperability for Microwave Access (WiMax), IEEE-based Low-power short-range networks based on 802.15.4 (such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN)), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may, for example, support Low Power Wide Area Networks (LPWAN). LPWAN technologies may include the Long Range (LoRa) physical layer protocol, Haystack, SigFox, LTE-M, and Narrow-Band IoT (NB-IoT).

[0050] The communication system 100 may include multiple nodes and / or operate in communication with another node, wherein Figure 3A first node 111, a second node 112, one or more third nodes 113, another node 114 (or a fourth node 114), and a fifth node 115 are depicted. In some examples, as Figure 3 As depicted in panel b), the communication system 100 may include a first second node 112a, a second second node 112b, and a third second node 112c. Similarly, in some examples, as Figure 3 As depicted in panel b), the one or more third nodes 113 may include a first third node 113a and a second third node 113b. It is understood that the communication system 100 may include more than Figure 3 More nodes are shown, such as an additional second node 112 and an additional third node 113. The first node 111, the second node 112 (e.g., the first second node 112a, the second second node 112b, and the third second node 112c), one or more third nodes 113 (e.g., the first third node 113a and the second third node 113b), and the fifth node 115 are included in or within the communication system 100. The fourth node 114 is external to the communication system 100 but can operate via the communication system 100. With reference to the description of the drawings, any reference to the second node 112 can be understood to apply equally to any of the first second node 112a, the second second node 112b, and the third second node 112c.

[0051] Any one of the first node 111 , the first second node 112 a , the second second node 112 b , and the fifth node 115 may be referred to as a further node 111 , 115 , 112 a , 112 b .

[0052] Any of the first node 111, the second node 112, the one or more third nodes 113, the fourth node 114, and the fifth node 115 can be understood as a first computer system, a second computer system, one or more third computer systems, a fourth computer system, and a fifth computer system, respectively. In some examples, any of the first node 111, the second node 112, the one or more third nodes 113, the fourth node 114, and the fifth node 115 can be implemented as, for example, a standalone server in a host computer in the cloud 120, such as Figure 3In some examples, any of first node 111, second node 112, one or more third nodes 113, fourth node 114, and fifth node 115 can be a distributed node or a distributed server, where some of their respective functions are implemented locally, for example, by a client manager, and some of their functions are implemented in cloud 120, for example, by a server manager. However, in other examples, any of first node 111, second node 112, one or more third nodes 113, fourth node 114, and fifth node 115 can also be implemented as a processing resource in a server farm.

[0053] Any of the first node 111 , the second node 112 , the one or more third nodes 113 , and the fifth node 115 may be co-located.

[0054] According to the embodiments of this document, the first node 111 can be understood as a node that can process user plane traffic based on rules. Traffic processing can include, for example, packet inspection through PDR, and different execution actions, such as traffic steering, QoS, charging / reporting, such as through FAR, QER and / or URR. These rules may have been received from the second node 112. Figure 3 As shown, the communication system 100 may be a 5G network, and a non-limiting example of the first node 111 may be a UPF. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the first node 111 may be a Packet Data Network Gateway User (PGW-U) or a Traffic Detection Function User (TDF-U).

[0055] The second node 112 may be a node capable of processing a control plane for an application-specific session of a device (eg, the device 130 described below) operating in the communication system 100 .

[0056] The first second node 112a is capable of managing sessions for devices (e.g., device 130 described below) in the communication system 100, for example, based on one or more specified rules. The first second node 112a may be a node capable of executing policy and charging decisions based on one or more preconfigured rules (e.g., PCC rules). The first second node 112a may support various functions, such as session establishment, modification, and release, as well as policy-related functionality, such as terminating interfaces to policy control functions, charging data collection, supporting charging interfaces, and controlling and coordinating charging data collection at the first node 111. In some examples, the first second node 112a may receive PCC rules from the second second node 112b and configure the first node 111 accordingly, for example, for event reporting. The first second node 112a may control packet processing in the first node 111 by establishing, modifying, or deleting PFCP sessions and by configuring (e.g., adding, modifying, or deleting) PDRs, FARs, QERs, and / or URRs for each PFCP session. Thus, a PFCP session may correspond to a single PDU session or an independent PFCP session not bound to any PDU session. Each PDR may contain a PDI that specifies traffic filters or signatures to which incoming packets may match. Each PDR may be associated with the following rules that provide a set of instructions to be applied to packets matching the PDI: a) a FAR that may contain instructions related to packet processing, specifically, forwarding, redirecting, applying header enhancement, copying, dropping, or buffering packets with or without notifying the control plane (CP) function of the arrival of downlink (DL) packets, b) zero, one, or more QERs that may contain instructions related to QoS implementation for traffic, and c) zero, one, or more URRs that may contain instructions related to traffic measurement and reporting. In a specific example, the first second node 112a may request the first node 111 to trigger header enhancement via a FAR that includes a header enhancement IE. As Figure 3 As shown, the communication system 100 may be a 5G network, and a non-limiting example of the first and second nodes 112a may be SMF. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the first and second nodes 112a may be packet data network gateway control plane functions (Packet Data Network Gateway Control, PGW-C) or traffic detection function control plane functions (Traffic Detection Function Control, TDF-C).

[0057] According to an embodiment of the present invention, the second second node 112b may be a node capable of supporting a unified policy framework to manage network behavior. The second second node 112b may provide policy rules to a device (eg, device 130) via the fifth node 115. Figure 3 As shown, where the communication system 100 may be a 5G network, a specific non-limiting example of the second node 112b may be a PCF. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the second node 112b may be a Policy and Charging Rule Function (PCRF).

[0058] The third second node 112c may be a node capable of storing data, such as data grouped into different sets of subscription-related information: subscription data, policy data, structured data for opening, and application data. Figure 3 As shown, where the communication system 100 may be a 5G network, a specific non-limiting example of the third second node 112c may be a UDR. Figure 3 In other non-limiting examples not depicted, where, for example, the communication system 100 may be a 4G network, the third second node 112c may be a Subscriber Profile Repository (SPR).

[0059] Any of the one or more third nodes 113 may be an open node capable of managing services of an operator that provides services for application sessions of a device (e.g., device 130 described below). That is, for example, any of the one or more third nodes 113 may be a node capable of managing, for example, different open APIs.

[0060] The first third node 113a is a node that can allow the fifth node 115 (e.g., a content provider) acting as an AF or API caller to request different services provided by the MNO through different APIs. For example, the first third node 113a can be used by another node 114 outside the trust domain of the communication system 100 to discover the service API, perform authentication, and obtain authorization. Figure 3 As shown, where the communication system 100 may be a 5G network, a specific non-limiting example of the first third node 113a may be CAPIF. Figure 3 In other non-limiting examples not depicted, where, for example, the communication system 100 may be a 4G network, the first third node 113a may be a SCEF.

[0061] The second third node 113b is a node that can support different functionalities, such as a set of APIs, such as handling sponsorship data, quality of service (QoS), etc., which can allow another node 114 to request policies from the MNO, such as on a per-user session and / or application basis. The second third node 113b can be understood as acting as an entry point into the communication system 100, so that the fourth node 114 (e.g., a content provider) can interact with the core network of the communication system 100 through one or more third nodes 113. Figure 3 As shown, the communication system 100 may be a 5G network, and a specific non-limiting example of the second and third nodes 113b may be NEF. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the second or third node 113b may be a Service Capability Exposure Function (SCEF).

[0062] Another node 114 may be a node capable of managing services for applications of the device. Another node 114 may interact with the core network of the communication system 100 through one or more third nodes 113. Another node 114 may allow external parties to use an API provided by the MNO of the communication system 100. Figure 3 As shown, a specific non-limiting example of a node 114 in which the communication system 100 may be a 5G network may be an AF or an AS. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the other node 114 may be a service capability server / application server (SCS / Application Server, AS), such as the device 130 described below.

[0063] When the devices can be connected via different access networks, the fifth node 115 may be a node capable of managing the access of the devices (eg, the device 130 described below) to the communication system 100 and the mobility of the devices. Figure 3 As shown, where the communication system 100 may be a 5G network, a specific non-limiting example of the fifth node 115 may be an AMF. Figure 3 In other non-limiting examples not depicted, for example, the communication system 100 may be a 4G network, and the fifth node 115 may be a Mobility Management Engine (MME).

[0064] The communication system 100 may also include a device 130. The device 130 may also be referred to as, for example, a user equipment (UE), a wireless device, a mobile terminal, a wireless terminal and / or a mobile station, a mobile phone, a cellular phone or a laptop computer with wireless capabilities, an Internet of Things (IoT) device, or Customer Premises Equipment (CPE), to mention only some other examples. The device 130 in this context may be, for example, a portable, pocket-storable, handheld, computer-built-in, or vehicle-mounted mobile device capable of voice and / or data communication via the RAN with another entity, such as a server, a laptop, a personal digital assistant (PDA) or tablet, a machine-to-machine (M2M) device, an Internet of Things (IoT) device (e.g., a sensor or camera), a device equipped with a wireless interface (e.g., a printer or file storage device), a modem, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a CPE, or any other radio network element capable of communicating over a radio link in the communication system 100. The device 130 may be wireless, i.e., capable of wireless communication in the communication system 100, and in some specific examples, capable of supporting beamforming transmissions. The communication may be, for example, between two devices, between a device and a radio network node, and / or between a device and a server. Communications may be performed, for example, via the RAN and possibly one or more core networks, respectively comprised within the communication system 100 .

[0065] The communication system 100 may include one or more radio network nodes, wherein the radio network node 140 is Figure 3b. The radio network node 140 may generally be a base station or a transmission point (TP) or any other network element capable of serving wireless devices or machine-type nodes in the communication system 100. The radio network node 140 may be, for example, a 5G gNB, a 4G eNB, or a radio network node in an alternative 5G radio access technology (e.g., fixed or WiFi). Based on transmit power and, therefore, also based on coverage size, the radio network node 140 may be, for example, a wide area base station, a medium range base station, a local area base station, or a home base station. The radio network node 140 may be a fixed relay node or a mobile relay node. The radio network node 140 may support one or more communication technologies, and its name may depend on the technology and terminology used. The radio network node 140 may be directly connected to one or more networks and / or one or more core networks.

[0066] The communication system 100 covers a geographical area that may be divided into cell areas, where each cell area may be served by a radio network node, although one radio network node may serve one or more cells.

[0067] The first node 111 can communicate with the second node 112 via a first link 151 (e.g., a radio link or a wired link). The first node 111 can communicate with the other node 114 via a second link 152 (e.g., a radio link or a wired link). The first node 111 can communicate with the device 130, for example, indirectly via a third link 153 (e.g., a radio link or a wired link). The third node 113 can communicate with the other node 114 via a fourth link 154 (e.g., a radio link or a wired link). The fifth node 115 can communicate with the second node 112, for example, indirectly via a fifth link 155 (e.g., a radio link or a wired link). The device 130 can communicate with the fifth node 115 via a sixth link 156 (e.g., a radio link or a wired link). The other node 114 can communicate with the device 130 via a seventh link 157 (e.g., a radio link or a wired link). The first node 111 can communicate with the first second node 112a via an eighth link 158 (e.g., a radio link or a wired link). The first second node 112a can communicate with the second second node 112b via a ninth link 159 (e.g., a radio link or a wired link). The second second node 112b can communicate with the third second node 112c via a tenth link 160 (e.g., a radio link or a wired link). The other node 114 can communicate with the first third node 113a via an eleventh link 161 (e.g., a radio link or a wired link). The other node 114 can communicate with the second third node 113b via a twelfth link 162 (e.g., a radio link or a wired link). The first second node 112a can communicate with the fifth node 115 via a thirteenth link 163 (e.g., a radio link or a wired link). The first node 111 can communicate with the radio network node 140 via a fourteenth link 164 (e.g., a radio link or a wired link). The fifth node 115 can communicate with the radio network node 140 via a fifteenth link 165 (e.g., a radio link or a wired link). The radio network node 140 may communicate directly or indirectly with the device 130 via a sixteenth link 166 (e.g., a radio link). The fifth node 115 may communicate with the third second node 112c via a seventeenth link 167 (e.g., a radio link or a wired link). The first second node 112a may communicate with the third second node 112c via an eighteenth link 168 (e.g., a radio link or a wired link).

[0068] Any one of the first link 151, the second link 152, the third link 153, the fourth link 154, the fifth link 155, the sixth link 156, the seventh link 157, the eighth link 158, the ninth link 159, the tenth link 160, the eleventh link 161, the twelfth link 162, the thirteenth link 163, the fourteenth link 164 and / or the fifteenth link 165 may be a direct link, or it may go through one or more computer systems or one or more core networks in the communication system 100, or it may go through an optional intermediate network. The intermediate network may be one or more combinations of a public network, a private network or a managed network; the intermediate network (if any) may be a backbone network or the Internet, which is not in the Figure 3 Shown in.

[0069] Although the present disclosure has used terminology from Long Term Evolution (LTE) / 5G to illustrate the embodiments herein, this should not be considered to limit the scope of the embodiments herein to only such systems. Other wireless systems supporting similar or equivalent functionality may also benefit from utilizing the concepts encompassed by the present disclosure.

[0070] The embodiments of this article can be understood as being applicable not only to the 5G network architecture, but the same mechanism can also be applied to 4G by simply replacing AF with SCS / AS, NEF with SCEF, UDR with SPR, PCF with PCRF, AMF with MME, SMF with PGW-C or TDF-C, and / or UPF with PGW-U or TDF-U.

[0071] In some embodiments, where the communication system 100 may be a 5G system, the first node 111 may be a UPF, the other node 114 may be an AS or an AF, and the second node 112 may be a node that processes the control plane of the session. The second node 112 may be at least one of the following: i) an SMF, ii) a PCF, and iii) a UDR.

[0072] In some embodiments, where communication system 100 may be a 4G system, first node 111 may be a PGW-U or TDF-U, another node 114 may be an AS or SCS, and second node 112 may be a node that processes the control plane of the session. Second node 112 may be at least one of: i) a PGW-C or a TDF-C, ii) a PCRF, and iii) an SPR.

[0073] In future telecommunication networks, such as the sixth generation (6G), the terms used herein may need to be reinterpreted in view of possible terminological changes in future technologies. Generally, the use of "first", "second", "third", "fourth", "fifth", "sixth", "seventh", "eighth", "ninth", "tenth", "eleventh", "twelfth", "thirteenth" or "fourteenth", "fifteenth", "sixteenth", "seventeenth" and / or "eighteenth" herein may be understood as any way of indicating different elements or entities, and may be understood as not giving cumulative or temporal characteristics to the nouns they modify.

[0074] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0075] Now refer to Figure 4 The flowchart depicted in describes an embodiment of a computer-implemented method performed by the first node 111. The method may be understood as being for handling a session for an application of a device 130. The first node 111 and the device 130 operate in a communication system 100.

[0076] This document includes several embodiments. In some embodiments, all actions can be performed. In some embodiments, two or more actions can be performed. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments can be combined. To simplify the description, not all possible combinations are described. Components from one embodiment can be assumed to exist in another embodiment by default, and how to use these components in other exemplary embodiments will be clear to those skilled in the art. Figure 4 A non-limiting example of a method performed by the first node 111 is depicted.

[0077] exist Figure 4 Optional actions are indicated by dashed lines.

[0078] Action 401

[0079] In this action 401, the first node 111 obtains a first indication directly or indirectly from the second node 112. The second node 112 operates in the communication system 100. The second node 112 may be a node in the control plane (e.g., 5GC control plane) of the communication system 100. The first node 111 may be a node in the user plane.

[0080] Acquiring may include receiving, for example, via the first link 151 .

[0081] In some of these embodiments, the first indication may be obtained in act 401 , at PDU session establishment, and during the PDU session for updates.

[0082] The first indication includes first information capable of identifying one or more third nodes 113 operating in the communication system 100. The one or more third nodes 113 provide services of an operator that provides services for application-specific sessions of the device 130. The operator operates in the communication system 100. The operator may be understood as an MNO, for example.

[0083] In some embodiments, the first information may include at least one of the following options: According to the first option, the first information may include a first identifier of the operator. In some embodiments, the first identifier may be a mobile network code-mobile country code (MNC-MCC). The first identifier may be used to identify the MNO.

[0084] According to a second option, the first information may include a second identifier of a first third node 113a among the one or more third nodes 113. The first third node 113a may be a CAPIF core function for the session. In some embodiments, the second identifier may be a first address of the CAPIF core function instance. In such embodiments, the second identifier may be understood as CAPIF core function address information. This may be, for example, a domain name, a server name or host name, or an IP address, which may allow identification of the CAPIF core function instance that processes the PDU session for the user of device 130.

[0085] According to a third option, the first information may include a third identifier of a second third node 113b among the one or more third nodes 113. The second third node 113b may be one of: i) an NEF instance handling the session, and ii) an SCEF instance handling the session. In some embodiments, the third identifier may be a second address of the NEF instance. In the first case, the third identifier may be understood as NEF address information. This may be, for example, a domain name, a server name or host name, or an IP address, which may allow identification of the NEF instance handling the PDU session of the user of device 130.

[0086] According to a fourth option, the first information may include one or more corresponding fourth identifiers of session-available APIs. In some embodiments, the one or more corresponding fourth identifiers may include a list of Nnef available APIs. For example, a list of Nnef available APIs for a PDU session of a user of device 130 may be provided on a per-application basis. The list of Nnef available APIs may be, for example, a list of (App-ID, allowed Nnef APIs). For example, for App-ID = example.com, the subscriber may be allowed to use the following services. The first service may be a QoS service, such as the Nnef_AFsessionWithQoS service, thereby allowing a content provider to request specific QoS for an application. The second service may be a sponsorship service, such as the Nnef_ChargeableParty service, thereby allowing application data to be sponsored by a third party (e.g., a content provider). In some examples, to support dynamic SLA creation, for example, when an explicit SLA may not exist between the MNO and the content provider, a default Nnef API list, such as App-ID = default, may be provided for applications that may be unknown to the MNO. In this case, the content provider may provide the MNO with detection rules for those applications.

[0087] In a specific embodiment, the first information may include one of: a) a first identifier and a second identifier, and b) a first identifier and a third identifier.

[0088] As a prerequisite, it may be assumed that the first information may already be stored at, for example, the second node 112 , eg, the third second node 112 c , eg, a UDR.

[0089] More specifically, in some embodiments, this may be understood as a first prerequisite that the MNO has stored a list of CAPIF core functions and NEF instances. It may be assumed that this information may be stored in a third second node 112c, such as a UDR.

[0090] In some embodiments, this can be understood as a second prerequisite that the MNO has stored a list of available NEF APIs, services, and instances. It can be assumed that this information can be stored in a third second node 112c, such as a UDR.

[0091] In some embodiments, this may be understood as a third prerequisite that the MNO has stored a list of allowed services on a per application and subscriber basis. It may be assumed that this information may be stored as subscriber data in a third second node 112c, such as a UDR.

[0092] In some embodiments, the first indication may be a PFCP session establishment request.

[0093] In some embodiments, the first instruction may further include another instruction instructing the first node 111 to execute a content-enhanced application, as will be described in action 404 .

[0094] In some embodiments, another indication may be FAR.

[0095] In some examples, another indication may instruct the first node 111 to perform content enhancement applications on a per-user PDU session basis and / or on a per-application basis.

[0096] In some embodiments, the further indication may include one or more respective fourth identifiers and a fifth identifier identifying an application to which the session may belong.

[0097] By obtaining the first indication in this action 401, the first node 111 can then initiate the provision of the first information to another node 114, which is an external node to the communication system 100 and which otherwise may not have other means to obtain or easily obtain the first information. By obtaining the first information, the other node 114 can ultimately be enabled to contact one or more third nodes 113 to learn which services of the operator providing service for the application-specific session of the device 130 are available to the device 130. This other node 114 can then be enabled not only to provide those services to the device 130 (e.g., for the application-specific session), but also to avoid relying on existing SLAs and / or avoiding having to contact another node (e.g., from another MNO) that may not serve the device 130 to learn what those services may be.

[0098] Action 402

[0099] In action 402 , the first node 111 may store the acquired first information. The first node 111 may store the acquired first information in a memory of the first node 111 .

[0100] By storing the acquired first information by the first node 111 in this action 402 , the first node 111 is able to retrieve the first information and initiate provision thereof to the fourth node 114 of the device 130 , as described in the following actions.

[0101] Action 403

[0102] In some embodiments, in this act 403, after having received the first indication, first node 111 may detect traffic from device 130 by receiving a second indication from device 130. First node 111 may detect the second indication, for example, when device 130 may open an application (e.g., example.com).

[0103] The second indication may be, for example, a first TLS message. The first TLS message may be a first client hello message.

[0104] By detecting the second indication in this action 403 , the first node 111 can then be enabled to apply content enhancement to the second indication, for example according to instructions provided in the other indication, as will be described in the next action 404 , so that the other node 114 can ultimately obtain the first information.

[0105] Action 404

[0106] In some embodiments, in action 404, the first node 111 may apply content enhancement to the received second indication using the first information obtained in action 401. The application of the content enhancement in action 404 may be based on instructions provided in another indication.

[0107] In some examples, the first node 111 can enhance the second indication, i.e., application traffic (e.g., TLS Client Hello), with a first identifier (e.g., MCC-MNC) identifying the MNO and a second identifier (e.g., CAPIF core function address information), so that the other node 114 can then contact the corresponding one or more third nodes 113 (e.g., CAPIF core function instances) to retrieve more information about the available Nnef APIs for the user and application session.

[0108] In some examples, the first node 111 can enhance the second indication, i.e., application traffic (e.g., TLS client hello), with a first identifier (e.g., MCC-MNC) identifying the MNO and a third identifier (e.g., NEF address information) and one or more corresponding fourth identifiers (e.g., a list of available NEF APIs for user and application sessions). This can be understood as the fastest process, which can allow the other node 114 to directly contact the corresponding NEF instance to call a service API, such as an AF session with QoS.

[0109] However, in some examples, the first node 111 may enhance the second indication, i.e., application traffic (e.g., TLS client hello), with a first identifier (e.g., MCC-MNC), a second identifier (e.g., CAPIF core function address information), a third identifier (e.g., NEF address information), and one or more corresponding fourth identifiers (e.g., allowed services with App-ID=example.com, such as Nnef_ChargeableParty service and Nnef_AFsessionWithQoS service).

[0110] By applying the content enhancement in this action 404, the first node 111 can then initiate, in a next action 405, provision of the first information to the further node 114. Obtaining the first information ultimately enables the further node 114 to contact one or more third nodes 113 to learn which services of the operator servicing the application-specific session of the device 130 are available to the device 130. For example, the further node 114 can be enabled to identify one or more third nodes 113 (e.g., CAPIF core functions and / or NEF instances) and trigger an API service request (e.g., an AF session with a QoS API) to, for example, request specific QoS for the application traffic. This, in turn, can then enable the further node 114 to not only provide those services (e.g., for the application-specific session) to the device 130, but also avoid relying on existing SLAs and / or having to contact another node (e.g., from another MNO) that may not be servicing the device 130 to learn what those services may be.

[0111] Action 405

[0112] In this action 405, the first node 111 initiates, in response to the acquired first indication, provision of first information to another node 114 external to the communication system 100. The another node 114 serves the device 130 in a session for the application.

[0113] Initiate can be understood as triggering, starting, promoting or enabling.

[0114] The initiating provision in action 405 may include providing the stored first information from action 404 to the other node 114 .

[0115] The initiating provision in act 405 may include sending a third indication including the second indication with the applied content enhancement.

[0116] In some embodiments, the second indication may be, for example, a first TLS message and the third indication is a second TLS message.

[0117] In some embodiments, the first TLS message may be a first Client Hello message and the second TLS message may be a second Client Hello message.

[0118] The initiating provision (eg, sending) in action 405 may be performed, for example, via the fourth link 154 .

[0119] By initiating the provision of the first information to another node 114 in action 405, first node 111 may enable another node 114 to contact one or more third nodes 113 to learn which services of the operator servicing the application-specific session of device 130 are available to device 130. For example, another node 114 may be enabled to identify one or more third nodes 113 (e.g., CAPIF core functionality and / or NEF instances) and trigger an API service request, such as requesting a specific QoS for application traffic. In situations where an SLA may exist between the MNO and another node 114 (e.g., a content provider), first node 111 may enable another node 114 to obtain the first information. In such situations, the MNO may share all configuration changes to utilize one or more third nodes 113, such as the NNEF API. This can be understood as providing flexibility, such as enabling the server hosting the API to be moved without hard-coded information. Furthermore, even in situations where an SLA may not exist between the MNO and another node 114 (e.g., a content provider), first node 111 may enable another node 114 to obtain the first information. In this case, the MNO may advertise the available services to the other node 114 and allow the other node 114 to begin communicating via one or more third nodes 113 (eg, Nnef API) to begin acquiring network services.

[0120] This other node 114 may then be enabled not only to provide those services to device 130 (e.g., for a session for an application), but also to avoid relying on an existing SLA and / or avoiding having to contact another node (e.g., from another MNO) that may not serve device 130 to learn what those services might be.

[0121] Now refer to Figure 5 The flowchart depicted in describes an embodiment of a computer-implemented method performed by the second node 112. The method may be understood as being for processing a session for an application of a device. The second node 112 operates via the communication system 100.

[0122] The method may include the following actions. This document includes several embodiments. In some embodiments, the method may include all actions. In other embodiments, the method may include two or more actions. Where applicable, one or more embodiments may be combined. To simplify the description, not all possible combinations are described. It should be noted that the examples herein are not mutually exclusive. Components from one example may be tacitly assumed to exist in another example, and how to use these components in the other examples will be clear to those skilled in the art. Figure 5 Optional actions are indicated by dashed lines.

[0123] Regarding the actions described for the first node 111, the detailed description of some of the contents below corresponds to the same references provided above and will therefore not be repeated here to simplify the description. For example, in some embodiments, the second node 112 may be a node in the control plane (e.g., 5GC control plane) of the communication system 100. The first node 111 may be a node in the user plane.

[0124] Action 501

[0125] In this action 501 , the second node 112 may receive a first request from a further node 111 , 115 , 112a , 112b .

[0126] The receiving in action 501 may be performed, for example, via the first link 151 , the fifth link 155 , or the ninth link 159 .

[0127] The characteristics of action 501 can be based on the node type of the second node 112, and are described below as: action 501a (for an embodiment in which the second node 112 can be a first second node 112a); action 501b (for an embodiment in which the second node 112 can be a second second node 112b); and action 501c (for an embodiment in which the second node 112 can be a third second node 112c).

[0128] Action 501a

[0129] In some embodiments, the second node 112 may be a first second node 112a. In some such embodiments, at least one of the following options may apply. The first second node 112a may be an SMF. The first request may be a first first request received from a fifth node 115 operating in the communication system 100. The fifth node 115 may be an AMF. The first first request may be to establish a session for the device 130. The first first request may include an identifier of the device 130, such as a UE-ID. The first first request may be an Nsmf PDU session creation request. Receipt of the first first request may be a result of the device 130 triggering a PDU session establishment procedure.

[0130] Action 501b

[0131] In some embodiments, the second node 112 may be a second-second node 112b. In some such embodiments, at least one of the following options may apply. The second-second node 112b may be a PCF. The first request may be a second-first request received from the first-second node 112a. The first-second node 112a may be an SMF. The second-first request may be a policy control for the session. The second-first request may include an identifier of the device 130. The second-first request may be an Npcf_SMPolicyControl_Create request. The second-first request may include an identifier of the device 130, such as a UE-ID. Receipt of the second-first request may be a result of the device 130 triggering a PDU session establishment procedure.

[0132] Action 501c

[0133] In some embodiments, second node 112 may be a third second node 112c. In some such embodiments, at least one of the following options may apply: third second node 112c may be a UDR. The first request may be a third first request received from second second node 112b. Second second node 112b may be a PCF. The third first request may be subscriber data for device 130. The third first request may include an identifier of device 130. The third first request may be a Nudr_Query request.

[0134] By receiving the first request from the further node 111, 115, 112a, 112b, the second node 112 may trigger the retrieval of the first information, as will be explained in the following actions, thereby enabling the identification of one or more third nodes 113 that offer the services of an operator that provides services for the application-specific session of the device 130. The first information may then be enabled to be stored at the first node 111 and provided to another node 114 external to the communication system 100 that may otherwise not have access to the information.

[0135] Action 502

[0136] In action 502, second node 112 may send a second request based on the received first request. The second request may be to directly or indirectly obtain the first information. The first information may be understood as being able to identify one or more third nodes 113 operating in communication system 100. The one or more third nodes 113 may be understood as providing services of an operator that provides services for application-specific sessions of device 130. The operator may be understood as operating in communication system 100.

[0137] The type of the second request may depend on the identity of the second node 112, as described below.

[0138] The characteristics of action 502 can be based on the node type of the second node 112 and are described below as: action 502a (for an embodiment in which the second node 112 can be a first second node 112a); action 502b (for an embodiment in which the second node 112 can be a second second node 112b); and action 502c (for an embodiment in which the second node 112 can be a third second node 112c).

[0139] Action 502a

[0140] In some embodiments, second node 112 may be first-second node 112a. In some such embodiments, at least one of the following options may apply. The second request may be a first-second request sent to second-second node 112b. Second-second node 112b may be a PCF. The first-second request may be an Npcf_SMPolicyControl_Create request. The sending of the first-second request may be a result of device 130 triggering a PDU session establishment procedure. The first-second request may include an identifier of device 130, such as a UE-ID.

[0141] Action 502b

[0142] In some embodiments, the second node 112 may be a second-second node 112b. In some such embodiments, at least one of the following options may apply. The second request may be a second-second request sent to a third-second node 112c. The third-second node 112c may be a UDR. The second-second request may be a Nudr_Query request. The first-second request may include an identifier of the device 130, such as a UE-ID.

[0143] Action 502c

[0144] In some embodiments, the second node 112 may be a third-second node 112c. In some such embodiments, at least one of the following options may apply: The second request may be a third-second request for storage managed by the third-second node 112c.

[0145] By sending the second request in action 502, the second node 112 can be enabled to ultimately request the retrieval of first information, such as session and subscriber data for the identified device 130 (e.g., the indicated UE-ID), directly or indirectly, as will be explained in the following actions. When requesting the retrieval of the first information indirectly, the second node 112 can forward the request to an intermediate node between the second node 112 sending the second request and the memory in which the first information can be stored. By requesting the retrieval of the first information, the second node 112 can thereby be enabled to identify one or more third nodes 113 that offer services of an operator that provides services for the application-specific session of the device 130. The first information can then be stored at the first node 111 and provided to another node 114 external to the communication system 100, which may otherwise not have access to the information.

[0146] Action 503

[0147] In action 503, the second node 112 obtains first information that can identify one or more third nodes 113 operating in the communication system 100. The one or more third nodes 113 open services of an operator that provides services for the application session of the device 130. The operator operates in the communication system 100.

[0148] The first information in action 503 is obtained in the first response to the second request sent in action 502.

[0149] Therefore, the first request received in action 501 may trigger the acquisition of first information in this action 503 .

[0150] In some embodiments, the first information may include at least one of the following options: According to the first option, the first information may include a first identifier of the operator. In some embodiments, the first identifier may be an MNC-MCC.

[0151] According to the second option, the first information may include a second identifier of a first third node 113a of the one or more third nodes 113. The first third node 113a may be a CAPIF core function for the session. In some embodiments, the second identifier may be a first address of a CAPIF core function instance.

[0152] According to a third option, the first information may include a third identifier of a second third node 113b among the one or more third nodes 113. The second third node 113b may be one of: i) an NEF instance processing the session, and ii) an SCEF instance processing the session. In some embodiments, the third identifier may be a second address of the NEF instance.

[0153] According to a fourth option, the first information may include one or more corresponding fourth identifiers of the session available APIs. In some embodiments, the one or more corresponding fourth identifiers may include a list of Nnef available APIs.

[0154] In some embodiments, the first information may include one of: a) a first identifier and a second identifier, and b) a first identifier and a third identifier.

[0155] According to the foregoing, the first information (e.g., session and subscriber data of the device 130) may be extended with the following parameters: a first identifier (e.g., MCC-MNC), a second identifier (e.g., a first address of a CAPIF core function instance), a third identifier (e.g., a second address of an NEF instance), and one or more corresponding fourth identifiers (e.g., a list of allowed Nnef APIs). In some examples of the embodiments herein, the N7 interface may be extended, for example, to carry the second identifier (e.g., CAPIF core function address information), the third identifier (e.g., NEF address information), and by extending the PCC rules to include one or more corresponding fourth identifiers (e.g., allowed Nnef APIs) on a per-application basis.

[0156] The characteristics of action 503 can be based on the node type of the second node 112, and are described below as: action 503a (for an embodiment in which the second node 112 can be a first second node 112a); action 503b (for an embodiment in which the second node 112 can be a second second node 112b); and action 503c (for an embodiment in which the second node 112 can be a third second node 112c).

[0157] Action 503a

[0158] In some embodiments, the second node 112 may be the first second node 112a. In some such embodiments, at least one of the following options may apply: The first response may be a first first response from the second second node 112b. The first first response may be an Npcf_SMPolicyControl_Create response.

[0159] Action 503b

[0160] In some embodiments, the second node 112 may be a second second node 112b. In some such embodiments, at least one of the following options may apply: The first response may be a second first response from the third second node 112c. The second first response may be a Nudr_Query response.

[0161] Action 503c

[0162] In some embodiments, the second node 112 may be a third second node 112c. In some such embodiments, at least one of the following options may apply: The first response may be a third first response from storage.

[0163] By performing this action 503, the second node 112 can be enabled to directly or indirectly obtain the first information, such as session and subscriber data for the device 130. The second node 112 can then be enabled to provide the first information to the first node 111. This can in turn enable the first node 111 to store the first information at the first node 111 and provide it to another node 114 outside the communication system 100, which may otherwise not be able to access the information. This can ultimately enable the fourth node 114 to identify one or more third nodes 113 that are open to the services of an operator that provides services for the application-specific session of the device 130.

[0164] Action 504

[0165] In this action 504, the second node 112 may initiate providing first information to the other node 114 via the first node 111 operating in the communication system 100. The other node 114 is external to the communication system 100. The first node 111 and the other node 114 serve the device 130 in a session for an application.

[0166] As previously described, in some embodiments where the communication system 100 may be a 5G system, the first node 111 may be a UPF, the other node 114 may be an AS or an AF, and the second node 112 may be a node that handles the control plane of the session. The second node 112 may be at least one of the following: i) an SMF, ii) a PCF, and iii) a UDR.

[0167] In some examples of the embodiments herein, the N4 interface can be extended, for example, to carry a second identifier (e.g., CAPIF core function address information), a third identifier (e.g., NEF address information), and to indicate content enhancement actions with one or more corresponding fourth identifiers (e.g., allowed Nnef APIs) in the FAR on a per-application basis.

[0168] In some embodiments where the communication system 100 may be a 4G system, the first node 111 may be a PGW-U or a TDF-U, the other node 114 may be an AS or an SCS, and the second node 112 may be a node that handles the control plane of the session. The second node 112 may be at least one of the following: i) a PGW-C or a TDF-C, ii) a PCRF, and iii) an SPR.

[0169] The characteristics of action 504 can be based on the node type of the second node 112 and are described below as: action 504a (for an embodiment in which the second node 112 can be a first second node 112a); action 504b (for an embodiment in which the second node 112 can be a second second node 112b); and action 504c (for an embodiment in which the second node 112 can be a third second node 112c).

[0170] Action 504a

[0171] In some embodiments, the second node 112 may be a first second node 112a. In some such embodiments, at least one of the following options may apply. The first request may be a first first request received from a fifth node 115 operating in the communication system 100. The first first request may be to establish a session for the device 130. The first first request may include an identifier of the device 130. The first second node 112a may be an SMF. The fifth node 115 may be an AMF. The first first request may be an Nsmf PDU Session Create Request. The second request may be a first second request sent to the second second node 112b. According to an eighth option, the second second node 112b may be a PCF. The first second request may be an Npcf_SMPolicyControl_Create request. The first response may be a first first response from the second second node 112b. The first first response may be an Npcf_SMPolicyControl_Create response. The first node 111 may be a UPF. The initiating provision in action 504 may include sending first information to the first node 111 in a first indication. The first indication may be a PFCP session establishment request. The first indication may also include another indication instructing the first node 111 to apply content enhancement to the second indication received from the device 130. The other indication may be a FAR. The second indication may be a first TLS message. The first TLS message may be a first Client Hello message.

[0172] Action 504b

[0173] In some embodiments, the second node 112 may be a second-second node 112b. In some such embodiments, at least one of the following options may apply. The first request may be a second-first request received from the first-second node 112a. The second-first request may be a policy control for the session. The second-first request may include an identifier of the device 130. The second-second node 112b may be a PCF. The first-second node 112a may be an SMF. The second-first request may be an Npcf_SMPolicyControl_Create request. The second request may be a second-second request sent to the third-second node 112c. The third-second node 112c may be a UDR. The second-second request may be a Nudr_Query request. The first response may be a second-first response from the third-second node 112c. The second-first response may be a Nudr_Query response. The first node 111 may be a UPF. The initiating provision in action 504 may include sending the first information to the first-second node 112a in a first-second response. The second response may be an Npcf_SMPolicyControl_Create response.

[0174] Action 504c

[0175] In some embodiments, second node 112 may be a third-second node 112c. In some such embodiments, at least one of the following options may apply. The first request may be a third-first request received from second-second node 112b. The third-first request may be for subscriber data of device 130. The third-first request may include an identifier of device 130. Third-second node 112c may be a UDR. Second-second node 112b may be a PCF. The third-first request may be a Nudr_Query request. The second request may be a third-second request for storage managed by third-second node 112c. The first response may be a third-first response from the storage. First node 111 may be a UPF. Initiating provision in act 504 may include sending the first information to second-second node 112b in a second-second response. The second-second response may be a Nudr_Query response.

[0176] By initiating the provision of the first information in action 504a, the second node 112 can directly or indirectly forward the information retrieved in action 503 to the first node 111. As previously described, this can in turn enable the first node 111 to store the first information at the first node 111 and provide it to another node 114 outside the communication system 100, which may otherwise be unable to access the information. This can ultimately enable the fourth node 114 to identify one or more third nodes 113 that offer the services of an operator that provides services for the application-specific session of the device 130.

[0177] Now refer to Figure 6 The flowchart depicted in FIG. 1 describes an embodiment of a computer-implemented method performed by another node 114. The method may be understood as being used to handle an application-specific session for a device operating in the communication system 100. The another node 114 is external to the communication system 100, and the another node 114 serves the device 130 in the application-specific session.

[0178] The method may include the following actions. This document includes several embodiments. In some embodiments, the method may include all actions. In other embodiments, the method may include three or more actions. Where applicable, one or more embodiments may be combined. To simplify the description, not all possible combinations are described. It should be noted that the examples herein are not mutually exclusive. Components from one example may be tacitly assumed to exist in another example, and how to use these components in the other examples will be clear to those skilled in the art. Figure 6 Optional actions are indicated by dashed lines.

[0179] Regarding the actions described for the first node 111, some of the detailed descriptions below correspond to the same references provided above and will therefore not be repeated here to simplify the description. For example, in some embodiments, the first node 111 may be a node in the user plane.

[0180] Action 601

[0181] In this action 601, another node 114 obtains first information from a first node 111 operating in the communication system 100. The first information can identify one or more third nodes 113 operating in the communication system 100. The one or more third nodes 113 provide services of an operator that provides services for application-specific sessions of the device 130. The operator operates in the communication system 100.

[0182] The obtaining (eg, receiving) in action 601 may be performed, for example, via the second link 152 .

[0183] The obtaining of the first information in action 601 may include receiving a third indication including the second indication with content enhancement.

[0184] The second indication may be a first TLS message, and the third indication may be a second TLS message.The first TLS message may be a first Client Hello message, and the second TLS message may be a second Client Hello message.

[0185] As previously described, in some embodiments where the communication system 100 may be a 5G system, the first node 111 may be a UPF, and the other node 114 may be an AS or an AF.

[0186] In some embodiments where the communication system 100 may be a 4G system, the first node 111 may be a PGW-U or a TDF-U, and the further node 114 may be an AS or an SCS.

[0187] In some embodiments, the first information may include at least one of the following options: According to a first option, the first information may include a first identifier of the operator.

[0188] According to the second option, the first information may include a second identifier of a first third node 113a of the one or more third nodes 113. The first third node 113a may be a CAPIF core function for the session.

[0189] According to a third option, the first information may include a third identifier of a second third node 113b of the one or more third nodes 113. The second third node 113b may be one of: i) an NEF instance handling the session, and ii) an SCEF instance handling the session.

[0190] According to a fourth option, the first information may include one or more respective fourth identifiers of the session-available APIs.

[0191] In some embodiments, at least one of the following may apply. In some embodiments, the first identifier may be MNC-MCC. In some embodiments, the second identifier may be the first address of a CAPIF core functionality instance. In some embodiments, the third identifier may be the second address of an NEF instance. In some embodiments, one or more corresponding fourth identifiers may include a list of NNEF available APIs.

[0192] In some embodiments, the first information may include one of: a) a first identifier and a second identifier, and b) a first identifier and a third identifier.

[0193] Action 602

[0194] In this action 602 , the further node 114 determines the identity of the one or more third nodes 113 in response to the obtained first information.

[0195] Determining the identity in act 602 may include extracting content enhancements from the third indication. Another node 114 (e.g., a provider or content AS / AF) may extract the enhanced information and use it to identify one or more third nodes 113. For example, a first identifier (e.g., MCC-MNC) may allow another node 114 to identify which MNO it can receive application session traffic from. The other node 114 may then retrieve information from the second and third identifiers regarding which MNO's CAPIF core functions and NEF instances, respectively, can handle sessions for the user of the device 130, as well as information regarding which NNEF APIs are available for application traffic.

[0196] By determining the identity of one or more third nodes 113 (e.g., CAPIF core functions and / or NEF instances) in this action 602, the other node 114 can be further enabled to trigger a third request for a service, such as an API service request, such as an AF session with a QoS API. The other node 114 can then be further enabled to contact the one or more third nodes 113 (e.g., NEF) and trigger a selected API (e.g., Nnef API).

[0197] Action 603

[0198] In this action 603, another node 114 initiates sending a third request for a service of the session application to at least one of the identified one or more third nodes 113. The third request for service (eg, API service request) may be, for example, an AF session with QoS API.

[0199] As an example, in this action 603, by including the following information, the other node 114 can use the third identifier (e.g., NEF address information) to identify the NEF instance and trigger an API service request to request specific QoS for the application traffic through the Nnef_AFSessionWithQoS API: the sixth identifier AF-ID of the other node 114, the fifth identifier of the application to which the session belongs (e.g., App-ID=example.com), the third request (e.g., API=Nnef_AFSessionWithQoS), and the seventh identifier of the requested service (e.g., QoSReference), which can be understood as indicating the requested QoS to be applied.

[0200] Action 604

[0201] In some embodiments, in action 604, the other node 114 may receive a third response to the sent third request from at least one of the one or more third nodes 113. For example, if the other node 114 has sent the third request to the NEF, the third response may be an authorization of the third request by the NEF.

[0202] Figure 7 is a signaling diagram depicting on panels a), b), c) and d) a non-limiting example of a method performed in a communication system 100 according to an embodiment of the present invention. Figure 7 In the embodiment, the communication system 100 is a 5G network, the first node 111 is a UPF, the first second node 112a is an SMF, the second second node 112b is a PCF, the third second node 112c is a UDR, the third node 113 is an NEF, the fourth node 114 is an AF / AS of the content provider, the fifth node 115 is an AMF, and the device 130 is a UE. It can be understood that in Figure 7 In the following examples depicted in , any reference to UPF may be understood as equivalent to a reference to the first node 111, any reference to SMF may be understood as equivalent to a reference to the first second node 112a, any reference to PCF may be understood as equivalent to a reference to the second second node 112b, any reference to UDR may be understood as equivalent to a reference to the third second node 112c, any reference to NEF may be understood as equivalent to a reference to the third node 113, any reference to AF / AS or content provider may be understood as equivalent to a reference to the fourth node 114, any reference to AMF may be understood as equivalent to a reference to the fifth node 115, and any reference to UE may be understood as equivalent to a reference to the device 130. Figure 7The example can be understood as having the following prerequisites: the MNO has stored a list of CAPIF core functions and NEF instances. It is assumed that this information is stored in the UDR. The MNO has stored a list of available NEF APIs, services, instances. It is assumed that this information is stored in the UDR. The MNO has stored a list of allowed services on a per-application and per-subscriber basis. It is assumed that this is stored in the UDR as subscriber data. Starting from panel a), in steps 1 to 3, the device 130 triggers the PDU session establishment process. For simplicity, not all steps are shown. In particular, in step 1, the device 130 sends an N1 PDU session establishment request to the fifth node 115, which includes an identifier of the device 130 (such as UE-ID). In step 2, the fifth node 115 sends a first request to the first second node 112a, which receives it according to action 501a. The first request is an Nsmf PDU session creation request including the identifier UE-ID of the device 130. In step 3, first-second node 112a sends a first second request as an Npcf_SMPolicyControl_Create request including the identifier UE-ID of device 130 to second-second node 112b, in accordance with actions 502a and 501b. In steps 4 to 6, second-second node 112b retrieves first information, namely, session and subscriber data for device 130 identified by its UE-ID, from third-second node 112b. Specifically, in step 4, second-second node 112b sends a second second request as a Nudr_Query request including the identifier UE-ID of device 130 to third-second node 112c, in accordance with actions 502b and 501c. In step 5, third-second node 112c sends a third second request to a storage managed by the third-second node, in accordance with action 502c, requesting the first information, in this case, session and subscriber data for device 130. According to embodiments herein, the session and subscriber data of the device 130 is extended with the following parameters: a) a first identifier as the MCC-MNC, which can be used to identify the MNO, b) a second identifier as the CAPIF core function address information, which can be, for example, a domain name, server name, or host name, or an IP address of a CAPIF core function instance that can allow identification of the user PDU session, c) a third identifier as the NEF address information, which can be, for example, a domain name, server name, or host name, or an IP address of a NEF instance that can allow identification of the user PDU session, and optionally, d) one or more corresponding fourth identifiers as a list of (App-ID, allowed Nnef APIs). This can be understood as a list of allowed Nnef APIs on a per-application basis.For example, for App-ID=example.com, the following services may be allowed for the subscriber: i) QoS service (Nnef_AFsessionWithQoSService), thereby allowing another node 114 to request a specific QoS for the application, and ii) sponsorship service (Nnef_ChargeablePartyService), thereby allowing application data to be sponsored by a third party (e.g., the fourth node 114) and thus not be deducted from the subscriber's monthly quota. Figure 7 Not shown in the sequence diagram example in , but in order to support dynamic SLA creation, when there may not be an explicit SLA between the MNO and the fourth node 114, a list of default Nnef APIs may be provided for applications that may be unknown to the MNO, such as App-ID=Default. In this case, the other node 114 may also provide detection rules for those applications to the MNO. According to the foregoing, in step 5, the third second node 112c looks up the CAPIF / NEF information and allowed services of the device 130 identified by its UE-ID, and retrieves the first information according to action 503c. In step 6, the third second node 112c provides the first information to the second second node 112b by sending a second second response (such as Nudr_Query response) according to action 504c and action 503c, the Nudr_Query response including a first identifier as the MCC-MNC, a second identifier as the CAPIF core function address information, a third identifier as the NEF address information, and one or more corresponding fourth identifiers as a list of (App-ID, allowed Nnef APIs). Continuing in Figure 7In panel b), in steps 7 and 8, the second second node 112b forwards the first information retrieved in step 6 above to the first second node 112a according to action 504b. In particular, the second second node 112b sends a first second response (e.g., an Npcf_SMPolicyControl_Create response), which includes a first identifier as the MCC-MNC, a second identifier as the CAPIF core function address information, a third identifier as the NEF address information, and a PCC rule indicating one or more corresponding fourth identifiers as a list of (App-ID, allowed NnefAPIs). According to embodiments of the present invention, the N7 interface can be extended, for example, to carry the second identifier as the CAPIF core function address information, the third identifier as the NEF address information, and by extending the PCC rule to include one or more corresponding fourth identifiers as allowed Nnef APIs on a per-application basis. In steps 9 and 10, the first second node 112a triggers the PFCP session establishment process and, in accordance with operations 504a and 401, forwards the first information retrieved in step 8 above to the first node 111. Specifically, the first second node 112a sends a first indication as a PFCP session establishment request, the PFCP session establishment request including a first identifier as the MCC-MNC, a second identifier as the CAPIF core function address information, a third identifier as the NEF address information, and another indication instructing the first node 111 to apply content enhancements having one or more corresponding fourth identifiers as a list of allowed Nnef APIs to the second indication received from the device 130 as a list of (PDR (App-ID), FAR (Content Enhancement Action, List of Allowed Nnef APIs)). According to an embodiment of the present invention, the N4 interface may be extended, for example, to carry the second identifier as the CAPIF core function address information, the third identifier as the NEF address information, and to indicate content enhancement actions using allowed Nnef APIs by indicating in the FAR on a per-application basis. In step 11, first node 111 stores the received first information according to action 402. In step 12, first node 111 responds with a PFCP Session Establishment Response message to first second node 112a, indicating a successful operation. In step 13, first second node 112a responds to the message in step 2 by triggering an Nsmf PDU Session Create Response message. In step 14, fifth node 115 responds to the message in step 1 by triggering an N1 PDU Session Establishment Response message. Continuing with panel c), in steps 15 and 16, the user of device 130 opens an application, such as example.com.In steps 17 and 18, the first node 111 detects application traffic from example.com according to action 403 and applies content enhancement to the first TLS Client Hello message using the indication parameters received in step 10, including a first identifier as the MCC-MNC, a second identifier as the CAPIF core function address information, a third identifier as the NEF address information, and one or more corresponding fourth identifiers of allowed services (e.g., Nnef_ChargeableParty service and Nnef_AFsessionWithQoS service) for App-ID=example.com. Then, in step 18, the first node 111 sends the first information as a third indication (e.g., a second TLS Client Hello message) to the other node 114 according to actions 405 and 601, which is enhanced with the MCC-MNC, the second identifier as the CAPIF core function address information, the third identifier as the NEF address information, and one or more corresponding fourth identifiers of allowed services (e.g., Nnef_ChargeableParty service and Nnef_AFsessionWithQoS service) for App-ID=example.com. Continuing with panel c), in steps 19 and 20, the other node 114 extracts the enhanced information and uses it to identify the CAPIF core functionality and / or NEF instance and trigger an API service request, such as an AF session with QoS API, according to action 602. In this example, the other node 114 uses the NEF address information to identify the NEF instance and triggers an Nnef API service request, according to action 603, to request specific QoS for the application traffic via the Nnef_AFSessionWithQoS API by including the following information: the sixth identifier of the other node 114, its AF-ID, a fifth identifier identifying the application to which the session belongs (here, App-ID=example.com), a third request (e.g., API=Nnef_AFSessionWithQoS), and a seventh identifier of the requested service (e.g., QoSReference), which can be understood as indicating the requested QoS to be applied. In steps 21 and 22, the third node 113 (here, the NEF) authorizes the request and, according to action 604, sends a third response (e.g., Nnef API service response) and applies the corresponding action. In this example, the NEF triggers a request for a specific QoS for the subscriber's application session to the second second node 112b. Figure 7 It is not shown in the sequence diagram because it is based on the existing process.

[0203] Certain embodiments disclosed herein may provide one or more of the following technical advantages, which can be summarized as follows.

[0204] The embodiments herein can be understood as enabling the provision of services that a network may have to applications and services without prior knowledge of what the network may be able to provide. The embodiments herein can be understood as enabling technologies such as dynamic SLA creation and intent creation. The embodiments herein can be understood as addressing the problem of deploying NEFs and network services on the Internet when SLAs have not yet been established between the parties, and providing methods for addressing such issues.

[0205] Figure 8 The first node 111 may include a Figure 4 and / or Figure 7 The first node 111 may be understood as being configured to handle a session for an application of the device 130. The first node 111 and the device 130 are configured to operate in the communication system 100.

[0206] This document includes several embodiments. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. To simplify the description, not all possible combinations are described. Components from one embodiment may be assumed to exist in another embodiment by default, and it will be clear to those skilled in the art how to use these components in other exemplary embodiments. With respect to the actions described for the first node 111, the detailed description of some of the contents below corresponds to the same references provided above and will therefore not be repeated here. For example, in some embodiments, the second node 112 may be configured as a node in the control plane (e.g., 5GC control plane) of the communication system 100. The first node 111 may be configured as a node in the user plane.

[0207] The first node 111 is configured to directly or indirectly obtain a first indication from a second node 112 configured to operate in the communication system 100. The first indication is configured to include first information, and the first information is configured to be able to identify one or more third nodes 113 configured to operate in the communication system 100. The one or more third nodes 113 are configured to open services of an operator, and the operator is configured to provide services for application-specific sessions of the device 130. The operator is configured to operate in the communication system 100.

[0208] The first node 111 is further configured to initiate providing the first information to another node 114 external to the communication system 100 in response to the first indication configured to be obtained. The another node 114 is configured to serve the device 130 in a session for the application.

[0209] In some embodiments, the first information can be configured to include at least one of: a) a first identifier of the operator, b) a second identifier of a first third node 113a among the one or more third nodes 113, wherein the first third node 113a can be configured as a CAPIF core function for the session, c) a third identifier of a second third node 113b among the one or more third nodes 113, wherein the second third node 113b can be configured as one of: i) an NEF instance configured to process the session, and ii) a SCEF instance configured to process the session, and d) one or more corresponding fourth identifiers of the session-available APIs.

[0210] In some embodiments, at least one of the following may apply: a) the first identifier may be configured as MNC-MCC, b) the second identifier may be configured as the first address of the CAPIF core function instance, c) the third identifier may be configured as the second address of the NEF instance, and d) one or more corresponding fourth identifiers may be configured to include a list of Nnef available APIs.

[0211] In some embodiments, the first node 111 may also be configured to store the first information configured to be obtained. In such embodiments, initiating the providing may be configured to include providing the first information configured to be stored to the other node 114.

[0212] In some embodiments, the first node 111 may be further configured to detect traffic from the device 130 by receiving a second indication from the device 130 after having received the first indication.

[0213] In some embodiments, the first node 111 may be further configured to apply the content enhancement to a second indication configured to be received using the first information. In such embodiments, initiating the provision may be configured to include sending a third indication configured to include the second indication with the applied content enhancement.

[0214] In some embodiments, at least one of the following may apply: a) the first indication may be configured as a PFCP session establishment request, b) the first indication may be further configured to include another indication configured to indicate that the first node 111 executes a content enhanced application, c) another indication may be configured as a FAR, d) the second indication may be configured as a first TLS message, and the third indication may be configured as a second TLS message, e) the first TLS message may be configured as a first client hello message, and the second TLS message may be configured as a second client hello message, f) the first information may be configured to include one of the following: a) a first identifier and a second identifier, and b) the first identifier and a third identifier, and g) another indication may be configured to include one or more corresponding fourth identifiers and a fifth identifier configured to identify an application to which the session may belong.

[0215] In some embodiments, one of the following two options may apply. According to the first option, the communication system 100 may be configured as a 5G system, the first node 111 may be configured as a UPF, the other node 114 may be configured as an AS or AF, and the second node 112 may be configured as a node configured to handle the control plane of the session. The second node 112 may be configured as at least one of the following: i) SMF, ii) PCF, and iii) UDR. According to the second option, the communication system 100 may be configured as a 4G system, the first node 111 may be configured as a PGW-U or TDF-U, the other node 114 may be configured as an AS or SCS, and the second node 112 may be configured as a node configured to handle the control plane of the session. The second node 112 may be configured as at least one of the following: i) PGW-C or TDF-C, ii) PCRF, and iii) SPR.

[0216] The embodiments of the present invention in the first node 111 may be implemented by one or more processors (e.g. Figure 8 The processing circuit 801 in the first node 111 depicted in FIG. 1 and computer program code for performing the functions and actions of the embodiments herein are implemented. As used herein, a processor may be understood as a hardware component. The program code may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code, which is used to execute the embodiments herein when loaded into the first node 111. One such carrier may be in the form of a CD ROM disk. However, other data carriers, such as a memory stick, may also be used. The computer program code may also be provided as pure program code on a server and downloaded to the first node 111.

[0217] The first node 111 may further include a memory 802 including one or more storage units. The memory 802 is configured to store acquired information, stored data, configurations, schedules, and applications, etc., to perform the methods herein when executed in the first node 111 .

[0218] In some embodiments, the first node 111 can receive information via the receive port 803 from, for example, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, another node 114, a fifth node 115, a radio network node 140, a device 130, another node, and / or another structure in the communication system 100. In some embodiments, the receive port 803 can be connected to one or more antennas in the first node 111, for example. In other embodiments, the first node 111 can receive information from another structure in the communication system 100 via the receive port 803. Because the receive port 803 can communicate with the processing circuit 801, the receive port 803 can then send the received information to the processing circuit 801. The receive port 803 can also be configured to receive other information.

[0219] The processing circuit 801 in the first node 111 may also be configured to transmit or send information to, for example, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, another node 114, a fifth node 115, a wireless network node 140, a device 130, another node, and / or another structure in the communication system 100 via a transmit port 804 that may communicate with the processing circuit 801 and the memory 802.

[0220] Those skilled in the art will also understand that the units included in the first node 111 described above as being configured to perform different actions may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware stored in a memory (e.g., when executed by one or more processors (e.g., processing circuit 801), as described above). One or more of these processors and other digital hardware may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple separate components, whether packaged separately or assembled into a system-on-a-chip (SoC).

[0221] Furthermore, in some embodiments, the different units included in the first node 111 described above as being configured to perform the above-described different actions may be implemented as one or more applications running on one or more processors (eg, the processing circuit 801 ).

[0222] Thus, the methods for first node 111 according to the embodiments described herein can each be implemented by a computer program product 805 comprising instructions (i.e., software code portions) that, when executed on at least one processing circuit 801, cause the at least one processing circuit 801 to perform the actions described herein as performed by first node 111. Computer program product 805 can be stored on a computer-readable storage medium 806. The computer-readable storage medium 806 having computer program 805 stored thereon can include instructions that, when executed on at least one processing circuit 801, cause the at least one processing circuit 801 to perform the actions described herein as performed by first node 111. In some embodiments, computer-readable storage medium 806 can be a non-transitory computer-readable storage medium, such as a CD ROM disk or a memory stick. In other embodiments, computer program product 805 can be stored on a carrier containing the computer program 805 as just described, where the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 806 as described above.

[0223] The first node 111 may include a communication interface or interface unit configured to facilitate communication between the first node 111 and another node or device, such as the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the further node 114, the fifth node 115, the radio network node 140, the device 130, a further node, and / or another structure in the communication system 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface according to a suitable standard.

[0224] In other embodiments, the first node 111 may include a radio circuit 807 , which may include, for example, a receive port 803 and a transmit port 804 .

[0225] The radio circuitry 807 may be configured to establish and maintain at least a wireless connection with the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the further node 114, the fifth node 115, the radio network node 140, the device 130, a further node, and / or another structure in the communication system 100. Circuitry may be understood herein as a hardware component.

[0226] Therefore, embodiments herein also relate to a first node 111 operable to operate in the communication system 100. The first node 111 may include a processing circuit 801 and a memory 802, the memory 802 including instructions executable by the processing circuit 801, whereby the first node 111 is further operable to perform the actions described herein with respect to the first node 111, for example, Figure 4 and / or Figure 7 As shown in .

[0227] Figure 9 The second node 112 may include a Figure 5 and / or Figure 7 The second node 112 may be understood as being configured to handle a session for an application of the device 130. The second node 112 and the device 130 are configured to operate in the communication system 100.

[0228] This document includes several embodiments. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. To simplify the description, not all possible combinations are described. Components from one embodiment may be assumed to exist in another embodiment by default, and it will be clear to those skilled in the art how to use these components in other exemplary embodiments. With respect to the actions described for the second node 112, the detailed description of some of the contents below corresponds to the same references provided above and will therefore not be repeated here. For example, in some embodiments, the second node 112 may be configured as a node in the control plane (e.g., 5GC control plane) of the communication system 100. The first node 111 may be configured as a node in the user plane.

[0229] The second node 112 is configured to obtain first information that is configured to identify one or more third nodes 113 configured to operate in the communication system 100. The one or more third nodes 113 are configured to provide services of an operator configured to provide services for sessions of the application's device 130. The operator is configured to operate in the communication system 100.

[0230] The second node 112 is further configured to initiate providing the first information to another node 114 external to the communication system 100 via the first node 111 configured to operate in the communication system 100. The first node 111 and the another node 114 are configured to serve the device 130 in a session for an application.

[0231] In some embodiments, the first information can be configured to include at least one of: a) a first identifier of the operator, b) a second identifier of a first third node 113a among the one or more third nodes 113, wherein the first third node 113a can be configured as a CAPIF core function for the session, c) a third identifier of a second third node 113b among the one or more third nodes 113, wherein the second third node 113b can be configured as one of: i) an NEF instance configured to process the session, and ii) a SCEF instance configured to process the session, and d) one or more corresponding fourth identifiers of the session-available APIs.

[0232] In some embodiments, at least one of the following may apply: a) the first identifier may be configured as MNC-MCC, b) the second identifier may be configured as a first address of a CAPIF core function instance, c) the third identifier may be configured as a second address of an NEF instance, and d) one or more corresponding fourth identifiers may be configured to include a list of Nnef available APIs, and e) the first information may be configured to include one of: a) the first identifier and the second identifier, and b) the first identifier and the third identifier.

[0233] In some embodiments, one of the following two options may apply. According to the first option, the communication system 100 may be configured as a 5G system, the first node 111 may be configured as a UPF, the other node 114 may be configured as an AS or AF, and the second node 112 may be configured as a node configured to handle the control plane of the session. The second node 112 may be configured as at least one of the following: i) SMF, ii) PCF, and iii) UDR. According to the second option, the communication system 100 may be configured as a 4G system, the first node 111 may be configured as a PGW-U or TDF-U, the other node 114 may be configured as an AS or SCS, and the second node 112 may be configured as a node configured to handle the control plane of the session. The second node 112 may be configured as at least one of the following: i) PGW-C or TDF-C, ii) PCRF, and iii) SPR.

[0234] In some embodiments, the second node 112 may be further configured to receive a first request from the further node 111 , 115 , 112a , 112b The first request may be configured to trigger the acquisition of the first information.

[0235] In some embodiments, the second node 112 may be further configured to send a second request to directly or indirectly obtain the first information based on the first request configured to be received. The first information may be obtained in a first response to the second request configured to be sent.

[0236] In some embodiments, the second node 112 may be configured as a first second node 112a. In some such embodiments, at least one of the following may apply: a) the first request may be configured as a first first request received from a fifth node 115 configured to operate in the communication system 100, b) the first first request may be configured to establish a session for the device 130, c) the first first request may be configured to include an identifier of the device 130, d) the first second node 112a may be configured as an SMF, e) the fifth node 115 may be configured as an AMF, f) the first first request may be configured as an Nsmf PDU session creation request, g) the second request can be configured as a first second request configured to be sent to the second second node 112b, h) the second second node 112b can be configured as a PCF, i) the first second request can be configured as an Npcf_SMPolicyControl_Create request, j) the first response can be configured as a first first response from the second second node 112b, k) the first first response can be configured as an Npcf_SMPolicyControl_Create response, l) the first node 111 can be configured as a UPF, m) initiate provision can be configured to include sending first information to the first node 111 in a first indication, n) the first indication can be configured as a PFCP session establishment request, o) the first indication can be configured to also include another indication, the other indication is configured to instruct the first node 111 to apply content enhancement to the second indication, the second indication is configured to be received from the device 130, p) the other indication can be configured as a FAR, q) the second indication can be configured as a TLS message, and r) the first TLS message can be configured as a first client hello message.

[0237] In some embodiments, the second node 112 may be configured as a second-second node 112b. In some such embodiments, at least one of the following may apply: a) the first request may be configured as a second-first request configured to be received from the first-second node 112a, b) the second-first request may be configured as policy control for a session, c) the second-first request may be configured to include an identifier of the device 130, d) the second-second node 112b may be configured as a PCF, e) the first-second node 112a may be configured as an SMF, f) the second-first request may be configured as an Npcf_SMPolicyControl_Create request, g) the second request may be configured to be sent to a third-second node. 112c, h) the third second node 112c can be configured as a UDR, i) the second second request can be configured as a Nudr_Query request, j) the first response can be configured as a second first response from the third second node 112c, k) the second first response can be configured as a Nudr_Query response, l) the first node 111 can be configured as a UPF, m) the initiate provision can be configured to include sending the first information to the first second node 112a in the first second response, and n) the second response can be configured as an Npcf_SMPolicyControl_Create response.

[0238] The second node 112 may be configured as a third-second node 112c. In some such embodiments, at least one of the following may apply: a) the first request may be configured as a third-first request that is configured to be received from the second-second node 112b, b) the third-first request may be configured for subscriber data of the device 130, c) the third-first request may be configured to include an identifier of the device 130, d) the third-second node 112c may be configured as a UDR, e) the second-second node 112b may be configured as a PCF, f) the third-first request may be configured as a Nudr_Query request, g) the second request may be configured as a third-second request to a storage configured to be managed by the third-second node 112c, h) the first response may be configured as a third-first response from the storage, i) the first node 111 may be configured as a UPF, j) the initiate offer may be configured to include sending the first information to the second-second node 112b in the second-second response, and k) the second-second response may be configured as a Nudr_Query response.

[0239] The embodiments of the present invention in the second node 112 may be implemented by one or more processors (e.g. Figure 9The program code may be implemented as a processing circuit 901 in the second node 112 depicted in FIG. 1 and computer program code for performing the functions and actions of the embodiments herein. As used herein, a processor may be understood as a hardware component. The program code may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code, which is used to execute the embodiments herein when loaded into the second node 112. One such carrier may be in the form of a CD ROM disk. However, other data carriers, such as a memory stick, may also be used. The computer program code may also be provided as pure program code on a server and downloaded to the second node 112.

[0240] The second node 112 may further include a memory 902 including one or more memory units. The memory 902 is configured to store acquired information, stored data, configurations, schedules, and applications, etc., to perform the methods herein when executed in the second node 112.

[0241] In some embodiments, the second node 112 can receive information via the receive port 903 from, for example, the first node 111, another second second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, another node 114, the fifth node 115, the radio network node 140, the device 130, another node, and / or another structure in the communication system 100. In some embodiments, the receive port 903 can be connected to one or more antennas in the second node 112, for example. In other embodiments, the second node 112 can receive information from another structure in the communication system 100 via the receive port 903. Since the receive port 903 can communicate with the processing circuit 901, the receive port 903 can then send the received information to the processing circuit 901. The receive port 903 can also be configured to receive other information.

[0242] The processing circuit 901 in the second node 112 may also be configured to transmit or send information to, for example, the first node 111, another second second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, another node 114, a fifth node 115, a wireless network node 140, a device 130, another node, and / or another structure in the communication system 100 via a transmission port 904 that may communicate with the processing circuit 901 and the memory 902.

[0243] Those skilled in the art will also understand that the units included in the second node 112 described above as being configured to perform different actions may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware stored in a memory (e.g., when executed by one or more processors (e.g., processing circuit 901), as described above). One or more of these processors and other digital hardware may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0244] Furthermore, in some embodiments, the different units included in the second node 112 described above as being configured to perform the above-described different actions may be implemented as one or more applications running on one or more processors (eg, the processing circuit 901 ).

[0245] Thus, the methods for second node 112 according to the embodiments described herein can each be implemented by a computer program product 905 comprising instructions (i.e., software code portions) that, when executed on at least one processing circuit 901, cause the at least one processing circuit 901 to perform the actions described herein as performed by second node 112. Computer program product 905 can be stored on a computer-readable storage medium 906. The computer-readable storage medium 906 having computer program 905 stored thereon can include instructions that, when executed on at least one processing circuit 901, cause the at least one processing circuit 901 to perform the actions described herein as performed by second node 112. In some embodiments, computer-readable storage medium 906 can be a non-transitory computer-readable storage medium, such as a CD ROM disk or a memory stick. In other embodiments, computer program product 905 can be stored on a carrier containing the computer program 905 as just described, where the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 906 as described above.

[0246] The second node 112 may include a communication interface or interface unit configured to facilitate communication between the second node 112 and another node or device, such as the first node 111, another second second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, another node 114, the fifth node 115, the radio network node 140, the device 130, another node, and / or another structure in the communication system 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface according to a suitable standard.

[0247] In other embodiments, the second node 112 may include a radio circuit 907 , which may include, for example, a receive port 903 and a transmit port 904 .

[0248] The radio circuit 907 may be configured to establish and maintain at least a wireless connection with the first node 111, the further second-second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the further node 114, the fifth node 115, the radio network node 140, the device 130, a further node and / or another structure in the communication system 100. A circuit may be understood herein as a hardware component.

[0249] Therefore, embodiments herein also relate to a first node 112 operable to operate in the communication system 100. The second node 112 may include a processing circuit 901 and a memory 902 containing instructions executable by the processing circuit 901, whereby the second node 112 is further operable to perform the actions described herein with respect to the second node 112, e.g. Figure 5 and / or Figure 7 middle.

[0250] Figure 10 Another node 114 may include a Figure 6 and / or Figure 7 The present invention provides an example of an arrangement of the method described in

[0026] . Another node 114 is configured to be accessible via the communication system 100. The another node 114 can be understood as being configured to handle application-specific sessions for a device 130 operating in the communication system 100. The another node 114 is configured to be external to the communication system 100. The another node 114 is configured to serve the device 130 in the application-specific sessions.

[0251] This document includes several embodiments. It should be noted that the examples herein are not mutually exclusive. Where applicable, one or more embodiments may be combined. To simplify the description, not all possible combinations are described. Components from one embodiment may be assumed to exist in another embodiment by default, and it will be clear to those skilled in the art how to use these components in other exemplary embodiments. With respect to the actions described for another node 114, the detailed description of some of the contents below corresponds to the same reference provided above and will therefore not be repeated here. For example, in some embodiments, the second node 112 may be configured as a node in the control plane (e.g., 5GC control plane) of the communication system 100. The first node 111 may be configured as a node in the user plane.

[0252] Another node 114 is configured to obtain first information from a first node 111 configured to operate in the communication system 100. The first information is configured to be able to identify one or more third nodes 113 configured to operate in the communication system 100. The one or more third nodes 113 are configured to provide services of an operator configured to provide services for application-specific sessions of the device 130. The operator is configured to operate in the communication system 100.

[0253] The further node 114 is further configured to determine the identity of the one or more third nodes 113 in response to the first information configured to be obtained.

[0254] Another node 114 is further configured to initiate sending a third request for a service of the session application to at least one of the one or more third nodes 113 configured to be identified.

[0255] In some embodiments, the first information may include at least one of the following: a) a first identifier of the operator, b) a second identifier of a first third node 113a among the one or more third nodes 113, wherein the first third node 113a can be configured as a CAPIF core function for the session, c) a third identifier of a second third node 113b among the one or more third nodes 113, wherein the second third node 113b can be configured as one of the following: i) an NEF instance configured to process the session, and ii) a SCEF instance configured to process the session, and d) one or more corresponding fourth identifiers of the session-available APIs.

[0256] In some embodiments, at least one of the following may apply: a) the first identifier may be configured as MNC-MCC, b) the second identifier may be configured as the first address of the CAPIF core function instance, c) the third identifier may be configured as the second address of the NEF instance, and d) one or more corresponding fourth identifiers may be configured to include a list of Nnef available APIs.

[0257] In some embodiments, at least one of the following may apply: a) acquisition of the first information may be configured to include receiving a third indication, the third indication configured to include the second indication with a content enhancement, b) determination of the identity may be configured to include extracting the content enhancement from the third indication, c) the second indication may be configured as a TLS message, and the third indication may be configured as a second TLS message, d) the first TLS message may be configured as a first client hello message, and the second TLS message may be configured as a second client hello message, and e) the first information may be configured to include one of: a) a first identifier and a second identifier, and b) the first identifier and a third identifier.

[0258] In some embodiments, the further node 114 may be further configured to receive a third response to the sent third request from at least one of the one or more third nodes 113 .

[0259] In some embodiments, one of the following two options may apply. According to the first option, the communication system 100 may be configured as a 5G system, the first node 111 may be configured as a UPF, and the other node 114 may be configured as an AS or an AF. According to the second option, the communication system 100 may be configured as a 4G system, the first node 111 may be configured as a PGW-U or a TDF-U, and the other node 114 may be configured as an AS or an SCS.

[0260] The embodiments of the present invention in another node 114 may be implemented by one or more processors (e.g. Figure 10 The program code can be implemented by processing circuit 1001 in another node 114 depicted in FIG and computer program code for performing the functions and actions of the embodiments herein. As used herein, a processor can be understood as a hardware component. The program code can also be provided as a computer program product, for example in the form of a data carrier carrying computer program code, which is used to execute the embodiments herein when loaded into another node 114. One such carrier can be in the form of a CD ROM disk. However, other data carriers, such as memory sticks, can also be used. The computer program code can also be provided as pure program code on a server and downloaded to another node 114.

[0261] The other node 114 may further include a memory 1002 including one or more memory units. The memory 1002 is configured to store acquired information, stored data, configurations, schedules, and applications, etc., to perform the methods herein when executed in the other node 114.

[0262] In some embodiments, the other node 114 can receive information from, for example, the first node 111, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the fifth node 115, the radio network node 140, the device 130, another node, and / or another structure in the communication system 100 via the receive port 1003. In some embodiments, the receive port 1003 can be connected to one or more antennas in the other node 114, for example. In other embodiments, the other node 114 can receive information from another structure in the communication system 100 via the receive port 1003. Since the receive port 1003 can communicate with the processing circuit 1001, the receive port 1003 can then send the received information to the processing circuit 1001. The receive port 1003 can also be configured to receive other information.

[0263] The processing circuit 1001 in the other node 114 can also be configured to transmit or send information to, for example, the first node 111, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the fifth node 115, the wireless network node 140, the device 130, another node and / or another structure in the communication system 100 through a transmission port 1004 that can communicate with the processing circuit 1001 and the memory 1002.

[0264] Those skilled in the art will also understand that the units included in another node 114 described above as being configured to perform different actions may refer to a combination of analog and digital circuits, and / or one or more processors configured with, for example, software and / or firmware stored in a memory (e.g., executed as described above when executed by one or more processors (e.g., processing circuit 1001)). One or more of these processors and other digital hardware may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed across multiple separate components, whether packaged separately or assembled into a system-on-a-chip (SoC).

[0265] Furthermore, in some embodiments, the different units included in the other node 114 described above as being configured to perform the above-described different actions may be implemented as one or more applications running on one or more processors (eg, the processing circuit 1001 ).

[0266] Thus, methods for another node 114 according to embodiments described herein can each be implemented by a computer program product 1005 comprising instructions (i.e., software code portions) that, when executed on at least one processing circuit 1001, cause the at least one processing circuit 1001 to perform the actions described herein as performed by another node 114. Computer program product 1005 can be stored on a computer-readable storage medium 1006. The computer-readable storage medium 1006 having computer program 1005 stored thereon can include instructions that, when executed on at least one processing circuit 1001, cause the at least one processing circuit 1001 to perform the actions described herein as performed by another node 114. In some embodiments, computer-readable storage medium 1006 can be a non-transitory computer-readable storage medium, such as a CD ROM disk or a memory stick. In other embodiments, computer program product 1005 can be stored on a carrier containing the computer program 1005 as just described, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium 1006 as described above.

[0267] The further node 114 may include a communication interface or interface unit configured to facilitate communication between the further node 114 and another node or device, such as the first node 111, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the fifth node 115, the radio network node 140, the device 130, another node, and / or another structure in the communication system 100. The interface may include, for example, a transceiver configured to transmit and receive radio signals over an air interface according to a suitable standard.

[0268] In other embodiments, the further node 114 may include a radio circuit 1007 , which may include, for example, a receive port 1003 and a transmit port 1004 .

[0269] The radio circuit 1007 may be configured to establish and maintain at least a wireless connection with the first node 111, the second node 112, the first second node 112a, the second second node 112b, the third second node 112c, one or more third nodes 113, the fifth node 115, the radio network node 140, the device 130, a further node, and / or another structure in the communication system 100. Circuitry may be understood herein as a hardware component.

[0270] Therefore, embodiments herein also relate to another node 114 operable to operate in the communication system 100. The another node 114 may include a processing circuit 1001 and a memory 1002, the memory 1002 including instructions executable by the processing circuit 1001, whereby the another node 114 is further operable to perform the actions described herein with respect to the another node 114, for example, in Figure 6 and / or Figure 7 middle.

[0271] The embodiments herein may further include a communication system 100 including the communication system 100 as described above. Figure 8 The first node 111 of the configuration, as described in Figure 9 The second node 112 of the configuration and Figure 10 Another node 114 of the configuration.

[0272] When the word "comprise" or "comprising" is used, it should be understood as non-limiting, ie meaning "consisting at least of.

[0273] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications, and equivalents may be used. Therefore, the above embodiments should not be considered to limit the scope of the present invention.

[0274] Generally, all terms used in this article should be interpreted according to their ordinary meaning in the relevant technical field, unless clearly given and / or implied different meanings in the context of its use. Unless otherwise clearly stated, all references to elements, equipment, components, devices, steps, etc. should be openly interpreted as referring to at least one instance of elements, equipment, components, devices, steps, etc. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a certain step is clearly described as after or before another step, and / or implies that a certain step must be after or before another step. Any feature of any embodiment disclosed herein can be applied to any other embodiment when appropriate. Similarly, any advantage of any embodiment can be applied to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0275] As used herein, the expression "at least one of the following:" followed by a comma-separated list of alternatives, and wherein the last alternative is preceded by the term "and," may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply, or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression "at least one of the following:" followed by a comma-separated list of alternatives, and wherein the last alternative is preceded by the term "or."

[0276] Any of the terms "processor" and "circuit" may be understood herein as a hardware component.

[0277] As used herein, the expression "in some embodiments" is used to indicate that features of a stated embodiment can be combined with any other embodiments or examples disclosed herein.

[0278] As used herein, the expression "in some examples" has been used to indicate that features of the described example can be combined with any other embodiments or examples disclosed herein.

[0279] References

[0280] 1.3GPP TS 23.222 v17.7.0 (September 2022): Common API framework for 3GPP northbound APIs.

Claims

1. A computer-implemented method, executed by a first node (111), for processing a session for an application of a device (130), the first node (111) and the device (130) operating in a communication system (100), the method comprising: - obtaining (401) a first indication directly or indirectly from a second node (112) operating in the communication system (100), the first indication comprising first information capable of identifying one or more third nodes (113) operating in the communication system (100), the one or more third nodes (113) being open to services of an operator providing services for a session for the application of the device (130), the operator operating in the communication system (100), and - in response to the obtained first indication, initiating (405) providing the first information to another node (114) external to the communication system (100), the other node (114) serving the device (130) in a session for the application.

2. The method according to claim 1, wherein The first information includes at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is a common application programming interface framework CAPIF core function for the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is one of: i. a network open function NEF instance that handles the session, and ii. Processing the session service capability exposure function SCEF, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

3. The method according to claim 2, wherein: At least one of the following: a. The first identifier is the mobile network code - mobile country code MNC-MCC, b. The second identifier is the first address of the CAPIF core function instance, c. the third identifier is the second address of the NEF instance, and d. The one or more corresponding fourth identifiers include a list of Nnef available APIs.

4. The method according to any one of claims 1 to 3, further comprising at least one of the following: - storing (402) the acquired first information, and wherein said initiating (405) providing comprises providing the stored first information to said further node (114), - after having received said first indication, detecting (403) traffic from said device (130) by receiving a second indication from said device (130), and - applying (404) a content enhancement to the received second indication using said first information, and wherein said initiating (405) providing comprises sending a third indication comprising the second indication with said applied content enhancement.

5. The method according to claim 4 and 2 or 3, wherein: At least one of the following: a. The first indication is a packet flow control protocol PFCP session establishment request, b. The first instruction further includes another instruction instructing the first node (111) to execute the content enhanced application (404), c. The other instruction is a forwarding action rule, d. the second indication is a first Transport Layer Security (TLS) message, and the third indication is a second TLS message, e. the first TLS message is a first Client Hello message, and the second TLS message is a second Client Hello message, f. The first information includes one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier, and g. The further indication comprises the one or more corresponding fourth identifiers and a fifth identifier identifying the application to which the session belongs.

6. The method according to any one of claims 1 to 5, wherein One of the following: a. The communication system (100) is a fifth generation 5G system, the first node (111) is a user plane function (UPF), the other node (114) is an application server (AS) or an application function (AF), and the second node (112) is a node that processes the control plane of the session, wherein the second node (112) is at least one of the following: i. Session Management Function SMF, ii. Policy Control Function PCF, and iii. User Data Repository (UDR), and b. The communication system (100) is a fourth generation (4G) system, the first node (111) is a packet data network gateway user plane function (PGW-U) or a traffic detection function user plane (TDF-U), the other node (114) is an application server (AS) or a service capability service (SCS), and the second node (112) is a node that processes the control plane of the session, wherein the second node (112) is at least one of the following: i. Packet Data Network Gateway Control Plane Function PGW-C or Traffic Detection Function Control Plane TDF-C, ii. Policy and Charging Rules Function PCRF, and iii. Subscriber Profile Repository SPR.

7. A computer-implemented method, performed by a second node (112), for processing a session for an application of a device (130), the second node (112) and the device (130) operating in a communication system (100), the method comprising: - obtaining (503) first information capable of identifying one or more third nodes (113) operating in the communication system (100), the one or more third nodes (113) opening services of an operator providing services for a session for the application of the device (130), the operator operating in the communication system (100), and - initiating (504) providing said first information to another node (114) external to said communication system (100) via a first node (111) operating in said communication system (100), said first node (111) and said another node (114) serving said device (130) in a session for said application.

8. The method according to claim 7, wherein: The first information includes at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is a common application programming interface framework CAPIF core function for the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is one of: i. a network open function NEF instance that handles the session, and ii. Processing the session service capability exposure function SCEF, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

9. The method according to claim 8, wherein At least one of the following: a. The first identifier is the mobile network code - mobile country code MNC-MCC, b. The second identifier is the first address of the CAPIF core network function instance, c. The third identifier is a second address of the NEF instance, d. the one or more corresponding fourth identifiers include a list of Nnef available APIs, and e. The first information includes one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier.

10. The method according to any one of claims 7 to 9, wherein One of the following: a. The communication system (100) is a fifth generation 5G system, the first node (111) is a user plane function (UPF), the other node (114) is an application server (AS) or an application function (AF), and the second node (112) is a node that processes the control plane of the session, wherein the second node (112) is one of the following: i. Session Management Function SMF, ii. Policy Control Function PCF, and iii. User Data Repository (UDR), and b. The communication system (100) is a fourth generation (4G) system, the first node (111) is a packet data network gateway user plane function (PGW-U) or a traffic detection function user plane (TDF-U), the other node (114) is an application server (AS) or a service capability service (SCS), and the second node (112) is a node that processes the control plane of the session, wherein the second node (112) is one of the following: i. Packet Data Network Gateway Control Plane Function PGW-C or Traffic Detection Function Control Plane TDF-C, ii. Policy and Charging Rules Function PCRF, and iii. Subscriber Profile Repository SPR.

11. The method according to any one of claims 7 to 10, wherein The method further comprises at least one of the following: - receiving (501) a first request from a further node (111, 115, 112a, 112b), said first request triggering the acquisition (503) of said first information, and - Based on the received first request, sending (502) a second request to directly or indirectly obtain the first information, and wherein the obtaining (503) of the first information is obtained in a first response to the sent second request.

12. The method according to claim 11, wherein The second node (112) is a first second node (112a), and wherein at least one of the following: - said first request is a first first request received from a fifth node (115) operating in said communication system (100), - said first request is to establish a session for said device (130), - said first request comprises an identifier of said device (130), - said first second node (112a) is an SMF, - said fifth node (115) is an Access and Mobility Function AMF, - the first request is an Nsmf PDU session creation request, - the second request is a first second request sent to a second second node (112b), - said second second node (112b) is a PCF, - the first second request is a Npcf_SMPolicyControl_Create request, - said first response is a first first response from said second second node (112b), - the first response is a Npcf_SMPolicyControl_Create response, - said first node (111) is a UPF, - said initiating (504) providing comprises sending said first information to said first node (111) in a first indication, - the first indication is a Packet Flow Control Protocol PFCP session establishment request, - the first indication further comprises a further indication instructing the first node (111) to apply content enhancement to the second indication received from the device (130), - the further indication is a forwarding action rule, - the second indication is a first Transport Layer Security (TLS) message, and - The first TLS message is a first Client Hello message.

13. The method according to claim 11, wherein The second node (112) is a second second node (112b), and wherein at least one of the following: - said first request being a second first request received from a first second node (112a), - the second first request is for policy control of the session, - said second first request comprises an identifier of said device (130), - said second second node (112b) is a PCF, - said first second node (112a) is an SMF, - the second first request is a Npcf_SMPolicyControl_Create request, - said second request is a second second request sent to a third second node (112c), - said third second node (112c) is a UDR, - the second request is a Nudr_Query request, - said first response is a second first response from said third second node (112c), - the second first response is a Nudr_Query response, - said first node (111) is a UPF, - said initiating (504) providing comprises sending said first information to said first second node (112a) in a first second response, and -The second response is a Npcf_SMPolicyControl_Create response.

14. The method according to claim 11, wherein The second node (112) is a third second node (112c), and wherein at least one of the following: - said first request is a third first request received from a second second node (112b), - said third first request is for subscriber data of said device (130), - said third first request comprises an identifier of said device (130), - said third second node (112c) is a UDR, - said second second node (112b) is a PCF, - the third first request is a Nudr_Query request, - said second request is a third second request for storage managed by said third second node (112c), - said first response is a third first response from said storage, - said first node (111) is a UPF, - said initiating (504) providing comprises sending said first information to said second second node (112b) in a second second response, and -The second response is a Nudr_Query response.

15. A computer-implemented method, executed by another node (114), for handling a session for an application of a device (130) operating in a communication system (100), the another node (114) being external to the communication system (100) and servicing the device (130) in the session for the application, the method comprising: - obtaining (601) first information from a first node (111) operating in the communication system (100), the first information being capable of identifying one or more third nodes (113) operating in the communication system (100), the one or more third nodes (113) being open to services of an operator providing services for a session for the application of the device (130), the operator being operated in the communication system (100), - determining (602) the identity of the one or more third nodes (113) in response to the obtained first information, and - initiating (603) sending a third request for a service of the session application to at least one third node of the identified one or more third nodes (113).

16. The method according to claim 15, wherein The first information includes at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is a common application programming interface framework CAPIF core function for the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is one of: i. a network open function NEF instance that handles the session, and ii. Processing the session service capability exposure function SCEF, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

17. The method according to claim 16, wherein At least one of the following: a. The first identifier is the mobile network code - mobile country code MNC-MCC, b. The second identifier is the first address of the CAPIF core function instance, c. the third identifier is the second address of the NEF instance, and d. The one or more corresponding fourth identifiers include a list of Nnef available APIs.

18. The method according to any one of claims 16 to 17, wherein At least one of the following: a. The acquisition of the first information (601) includes receiving a third indication, the third indication including a second indication having content enhancement, b. The determination of the identity (602) comprises extracting the content enhancement from the third indication, c. the second indication is a first Transport Layer Security (TLS) message, and the third indication is a second TLS message, d. the first TLS message is a first Client Hello message, and the second TLS message is a second Client Hello message, and e. The first information includes one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier.

19. The method according to any one of claims 15 to 18, further comprising: - receiving (604) a third response to said sent third request from at least one third node of said one or more third nodes (113).

20. The method according to any one of claims 15 to 19, wherein One of the following: a. The communication system (100) is a fifth generation 5G system, the first node (111) is a user plane function UPF, and the other node (114) is an application server AS or an application function AF, b. The communication system (100) is a fourth generation 4G system, the first node (111) is a packet data network gateway user plane function PGW-U or a traffic detection function user plane TDF-U, and the other node (114) is an application server AS or a service capability service SCS.

21. A first node (111) for processing a session for an application of a device (130), the first node (111) and the device (130) being configured to operate in a communication system (100), the first node (111) being further configured to: - obtaining, directly or indirectly, a first indication from a second node (112) configured to operate in the communication system (100), the first indication being configured to include first information, the first information being configured to be able to identify one or more third nodes (113) configured to operate in the communication system (100), the one or more third nodes (113) being configured to be open to services of an operator configured to provide services for a session for the application of the device (130), the operator being configured to operate in the communication system (100), and - in response to a first indication configured to be obtained, initiating (405) providing the first information to another node (114) external to the communication system (100), the other node (114) being configured to serve the device (130) in a session for the application.

22. The first node (111) according to claim 21, wherein The first information is configured to include at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is configured to be used for a common application programming interface framework CAPIF core functionality of the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is configured as one of the following: i. a network open function NEF instance configured to handle the session, and ii. A service capability openness function SCEF instance configured to handle the session, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

23. The first node (111) according to claim 22, wherein At least one of the following: a. The first identifier is configured as a mobile network code - mobile country code MNC-MCC, b. The second identifier is configured as the first address of the CAPIF core function instance, c. the third identifier is configured as the second address of the NEF instance, and d. The one or more corresponding fourth identifiers are configured to include a list of Nnef available APIs.

24. The first node (111) according to any one of claims 21 to 23, further configured to perform at least one of the following: - storing first information configured to be obtained, and wherein said initiating provision is configured to include providing said first information configured to be stored to said further node (114), - after having received said first indication, detecting traffic from said device (130) by receiving a second indication from said device (130), and - applying a content enhancement to said second indication configured to be received using said first information, and wherein said initiating provision is configured to comprise sending a third indication configured to comprise the second indication with said applied content enhancement.

25. The first node (111) according to claim 24 and 22 or 23, wherein at least one of the following: a. The first indication is configured as a packet flow control protocol PFCP session establishment request, b. The first instruction is further configured to include another instruction, the other instruction being configured to instruct the first node (111) to execute the content enhancement application, c. The other instruction is configured as a forwarding action rule, d. the second indication is configured as a first Transport Layer Security (TLS) message, and the third indication is configured as a second TLS message, e. the first TLS message is configured as a first client hello message, and the second TLS message is configured as a second client hello message, f. The first information is configured to include one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier, and g. The further indication is configured to include the one or more corresponding fourth identifiers and a fifth identifier configured to identify the application to which the session belongs.

26. The first node (111) according to any one of claims 21 to 25, wherein One of the following: a. The communication system (100) is configured as a fifth generation 5G system, the first node (111) is configured as a user plane function (UPF), the other node (114) is configured as an application server (AS) or an application function (AF), and the second node (112) is configured as a node configured to process the control plane of the session, wherein the second node (112) is configured as at least one of the following: i. Session Management Function SMF, ii. Policy Control Function PCF, and iii. User Data Repository (UDR), and b. The communication system (100) is configured as a fourth generation (4G) system, the first node (111) is configured as a packet data network gateway user plane function (PGW-U) or a traffic detection function user plane (TDF-U), the other node (114) is configured as an application server (AS) or a service capability service (SCS), and the second node (112) is configured as a node configured to process the control plane of the session, wherein the second node (112) is configured as at least one of the following: i. Packet Data Network Gateway Control Plane Function PGW-C or Traffic Detection Function Control Plane TDF-C, ii. Policy and Charging Rules Function PCRF, and iii. Subscriber Profile Repository SPR.

27. A second node (112) for processing a session for an application of a device (130), the second node (112) and the device (130) being configured to operate in a communication system (100), the second node (112) being further configured to: - obtaining first information configured to be able to identify one or more third nodes (113) operating in the communication system (100), the one or more third nodes (113) being configured to open a service of an operator configured to provide a service for a session for the application of the device (130), the operator being configured to operate in the communication system (100), and - initiating provision of the first information to another node (114) external to the communication system (100) via a first node (111) configured to operate in the communication system (100), the first node (111) and the another node (114) being configured to serve the device (130) in a session for the application.

28. The second node (112) of claim 27, wherein The first information is configured to include at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is configured to be used for a common application programming interface framework CAPIF core functionality of the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is configured as one of the following: i. a network open function NEF instance configured to handle the session, and ii. A service capability openness function SCEF instance configured to handle the session, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

29. The second node (112) of claim 28, wherein At least one of the following: a. The first identifier is configured as a mobile network code - mobile country code MNC-MCC, b. The second identifier is configured as the first address of the CAPIF core network function instance, c. The third identifier is configured as a second address of the NEF instance, d. the one or more corresponding fourth identifiers are configured to include a list of Nnef available APIs, and e. The first information is configured to include one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier.

30. The second node (112) according to any one of claims 27 to 29, wherein One of the following: a. The communication system (100) is configured as a fifth generation 5G system, the first node (111) is configured as a user plane function (UPF), the other node (114) is configured as an application server (AS) or an application function (AF), and the second node (112) is configured as a node configured to process the control plane of the session, wherein the second node (112) is configured as one of the following: i. Session Management Function SMF, ii. Policy Control Function PCF, and iii. User Data Repository (UDR), and b. The communication system (100) is configured as a fourth generation (4G) system, the first node (111) is configured as a packet data network gateway user plane function (PGW-U) or a traffic detection function user plane (TDF-U), the other node (114) is configured as an application server (AS) or a service capability service (SCS), and the second node (112) is configured as a node configured to process the control plane of the session, wherein the second node (112) is configured as one of the following: i. Packet Data Network Gateway Control Plane Function PGW-C or Traffic Detection Function Control Plane TDF-C, ii. Policy and Charging Rules Function PCRF, and iii. Subscriber Profile Repository SPR.

31. The second node (112) according to any one of claims 27 to 30, wherein The second node (112) is further configured to perform at least one of the following: - receiving a first request from a further node (111, 115, 112a, 112b), said first request being configured to trigger the acquisition of said first information, and - Based on the first request configured to be received, sending a second request to directly or indirectly obtain the first information, and wherein the acquisition of the first information is configured to be obtained in a first response to the second request configured to be sent.

32. The second node (112) according to claim 31, wherein The second node (112) is configured as a first second node (112a), and wherein at least one of the following: - said first request being configured as a first first request received from a fifth node (115) configured to operate in said communication system (100), - said first request being configured to establish said session for said device (130), - said first request being configured to include an identifier of said device (130), - said first second node (112a) being configured as an SMF, - said fifth node (115) is configured as an Access and Mobility Function AMF, - the first request is configured as an Nsmf PDU Session Create Request, - the second request is configured to be a first second request configured to be sent to the second second node (112b), - said second second node (112b) being configured as a PCF, - the first second request is configured as an Npcf_SMPolicyControl_Create request, - said first response being configured as a first first response from said second second node (112b), - the first response is configured as a Npcf_SMPolicyControl_Create response, - said first node (111) being configured as a UPF, - said initiating provision being configured to comprise sending said first information to said first node (111) in a first indication, - the first indication is configured as a Packet Flow Control Protocol PFCP session establishment request, - the first indication is configured to further include a further indication configured to instruct the first node (111) to apply content enhancement to a second indication configured to be received from the device (130), - the further indication is configured as a forwarding action rule, - the second indication is configured as a first Transport Layer Security (TLS) message, and - The first TLS message is configured as a first Client Hello message.

33. The second node (112) of claim 31, wherein The second node (112) is configured as a second second node (112b), and wherein at least one of the following: - said first request being configured as a second first request being configured to be received from a first second node (112a), - the second first request is configured as a policy control for the session, - said second first request being configured to include an identifier of said device (130), - said second second node (112b) being configured as a PCF, - said first second node (112a) being configured as an SMF, - the second first request is configured as a Npcf_SMPolicyControl_Create request, - the second request is configured to be a second second request configured to be sent to a third second node (112c), - said third second node (112c) is configured as a UDR, - the second request is configured as a Nudr_Query request, - said first response being configured as a second first response from said third second node (112c), - the second first response is configured as a Nudr_Query response, - said first node (111) being configured as a UPF, - said initiating provision being configured to comprise sending said first information to said first second node (112a) in a first second response, and -The second response is configured as an Npcf_SMPolicyControl_Create response.

34. The second node (112) of claim 31, wherein: The second node (112) is configured as a third second node (112c), and wherein at least one of the following: - the first request is configured to be a third first request configured to be received from a second second node (112b), - said third first request being configured for subscriber data of said device (130), - said third first request being configured to include an identifier of said device (130), - said third second node (112c) is configured as a UDR, - said second second node (112b) being configured as a PCF, - the third first request is configured as a Nudr_Query request, - said second request being configured as a third second request for storage configured to be managed by said third second node (112c), - the first response is configured as a third first response from the storage, - said first node (111) being configured as a UPF, - said initiating provision being configured to comprise sending said first information to said second second node (112b) in a second second response, and -The second response is configured as a Nudr_Query response.

35. A further node (114) for handling a session for an application of a device (130) configured to operate in a communication system (100), the further node (114) being configured to be external to the communication system (100) and configured to serve the device (130) in the session for the application, the further node (114) being further configured to: - obtaining first information from a first node (111) configured to operate in the communication system (100), the first information being configured to be able to identify one or more third nodes (113) configured to operate in the communication system (100), the one or more third nodes (113) being configured to open a service of an operator configured to provide a service for a session for the application of the device (130), the operator being configured to operate in the communication system (100), - determining the identity of the one or more third nodes (113) in response to the first information being configured to be obtained, and - initiating a third request for a service of the session application to at least one of the one or more third nodes (113) configured to be identified.

36. Another node (114) according to claim 35, wherein The first information is configured to include at least one of the following: a. the first identifier of the operator, b. a second identifier of a first third node (113a) of the one or more third nodes (113), wherein the first third node (113a) is configured to be used for a common application programming interface framework CAPIF core functionality of the session, c. a third identifier of a second third node (113b) of the one or more third nodes (113), wherein the second third node (113b) is configured as one of the following: i. a network open function NEF instance configured to handle the session, and ii. A service capability openness function SCEF instance configured to handle the session, and d. One or more respective fourth identifiers of available application programming interfaces (APIs) for the session.

37. Another node (114) according to claim 36, wherein At least one of the following: a. The first identifier is configured as a mobile network code - mobile country code MNC-MCC, b. The second identifier is configured as the first address of the CAPIF core function instance, c. the third identifier is configured as the second address of the NEF instance, and d. The one or more corresponding fourth identifiers are configured to include a list of Nnef available APIs.

38. Another node (114) according to any one of claims 36 to 37, wherein At least one of the following: a. obtaining the first information is configured to include receiving a third indication, the third indication being configured to include a second indication having content enhancement, b. The determination of the identity is configured to include extracting the content enhancement from the third indication, c. the second indication is configured as a first Transport Layer Security (TLS) message, and the third indication is configured as a second TLS message, d. the first TLS message is configured as a first Client Hello message, and the second TLS message is configured as a second Client Hello message, and e. The first information is configured to include one of the following: a) the first identifier and the second identifier, and b) the first identifier and the third identifier.

39. Another node (114) according to any one of claims 35 to 38, further configured to: - receiving a third response to said sent third request from at least one third node of said one or more third nodes (113).

40. Another node (114) according to any one of claims 35 to 39, wherein One of the following: a. The communication system (100) is configured as a fifth generation 5G system, the first node (111) is configured as a user plane function UPF, and the other node (114) is configured as an application server AS or an application function AF, b. The communication system (100) is configured as a fourth generation 4G system, the first node (111) is configured as a packet data network gateway user plane function PGW-U or a traffic detection function user plane TDF-U, and the other node (114) is configured as an application server AS or a service capability service SCS.

41. A communication system (100) comprising a first node (111) according to any one of claims 21 to 26, a second node (112) according to any one of claims 27 to 34 and a further node (114) according to any one of claims 35 to 40.

Images