Charging using a connection-oriented stateful transport protocol

Abstract

The present disclosure provides a method and devices to facilitate charging for a session between an Application Function (AF) device (512) and a User Equipment (UE) (800) when using a connection-oriented stateful transport protocol (e.g., such as QUIC). The UE (800) and the AF device (512) can exchange respective sets of connection IDs that can be used to identify the session, and the connection IDs can be stored at either a Charging Function (CHF) device (516), or a Policy Control Function (PCF) device (510). When messages are exchanged between the AF device (512) and the UE (800) using the connection IDs, the PCF (510) or CHF (516) can identify which sessions the messages correspond to based on the connection IDs, and can produce a charging data record (CDR) that links messages to sessions to facilitate charging.

Description

[0001] CHARGING USING A CONNECTION-ORIENTED STATEFUL TRANSPORT

[0002] PROTOCOL

[0003] Technical Field

[0004] The present disclosure relates to a method for facilitating charging of a communication session using QUIC connection identifiers (IDs) or other connection- oriented stateful transport protocols. The disclosure also relates to a network node, and a user equipment device.

[0005] Background

[0006] There is a drive towards using QUIC (formerly "Quick User Datagram Protocol (UDP) Internet Connections) (described in IETF RFC 9000: "QUIC: A UDP-Based Multiplexed and Secure Transport"), instead of Transmission Control Protocol (TCP) and it is used for Hypertext Transfer Protocol (HTTP) / 3 and is supported by all major web browsers. This gives an indication that more and more applications and services on the web will be moving towards the use of QUIC. QUIC is a UDP based protocol.

[0007] One of the improvements in QUIC is the performance during network-switch events, which is accomplished by introducing a connection identifier (ID). The connection ID ensures that changes in addressing at lower protocol layers, (e.g., UDP and internet protocol (IP)), do not cause packets to be delivered to the wrong endpoint. The reason for this is that UDP doesn't maintain any type of connection or session, instead each message will be treated separately, and all knowledge of a connection or session is handled at an application level. Since QUIC also focuses on security there are several connection IDs used for one connection and there is a possibility to update the set of connection IDs used. This means that each QUIC connection possesses a set of connection identifiers, or connection IDs, each of which can identify the connection. Connection IDs are independently selected by endpoints and each endpoint selects the connection IDs that its peer uses.

[0008] Summary

[0009] The object of the invention is to improve flexibility when charging for communication sessions. The present disclosure provides a method and devices to facilitate charging for a session between an Application Function (AF) device and a User Equipment (UE) when using a connection-oriented stateful transport protocol (e.g., such as QUIC - formerly "Quick User Datagram Protocol (UDP) Internet Connections). The UE and the AF device can exchange respective sets of connection identifiers (IDs) that can be used to identify the session, and the connection IDs can be stored at either a Charging Function (CF) device, or a Policy Control Function (PCF) device. When messages are exchanged between the AF device and the UE using the connection IDs, the PCF or CHF can identify which sessions the messages correspond to based on the connection IDs, and can produce a charging data record (CDR) that links messages to sessions to facilitate charging.

[0010] In an embodiment, a method for facilitating charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol performed by the AF device is disclosed. The method includes receiving from the UE, a first set of connection IDs for identifying the session. The method can also include providing to the UE a second set of connection IDs for identifying the session. The method can also include providing to a CHF device or a PCF device, information identifying the first set of connection IDs and the second set of connection IDs.

[0011] In an embodiment, the receiving the first set of connection identifier and providing the second set of connection IDs is in response to receiving from the UE a request to set up the session.

[0012] In an embodiment, the receiving the first set of connection identifier and providing the second set of connection IDs is in response to providing to the UE a request to set up the session.

[0013] In an embodiment, the method can include providing one or more messages to the UE, each message of the one or more messages comprising a connection ID from the second set of connection IDs.

[0014] In an embodiment, in response to using all connection IDs in the one or more messages to the UE the method can include, providing a connection ID update request to the UE, and receiving an updated first set of connection IDs from the UE.

[0015] In an embodiment, the method can include receiving a connection ID update request from the UE, and receiving an updated first set of connection IDs from the UE. In an embodiment, the method can include providing the updated first set of connection IDs associated with the UE and an updated second set of connection IDs associated with the AF device to the CHF device or PCF device.

[0016] In an embodiment, the information identifying the first set of connection IDs and the second set of connection IDs also comprises information identifying the UE and the AF device or the session.

[0017] In an embodiment, a network node is provided that implements an AF device that is configured to facilitate charging of a session between the AF device and a UE using a connection-oriented stateful transport protocol. The network node includes processing circuitry configured to cause the network node to receive from the UE a first set of connection IDs for identifying the session, provide to the UE, a second set of connection IDs for identifying the session, and provide to a CHF device or a PCF device, information identifying the first set of connection IDs and the second set of connection IDs.

[0018] In an embodiment, a method is provided for facilitating charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol performed by a CHF device. The method includes receiving, from one or more of the UE or the AF device, a first set of connection IDs for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE, and the second set of connection IDs are associated with the AF device. The method also includes receiving, a connection ID from a Session Management Function (SMF) device. The method also includes associating the connection ID to the session in response to matching the connection ID to a connection ID from the first set of connection IDs or the second set of connection IDs and providing, to the SMF device, a charging data record that comprises an indication the connection ID is associated with the session.

[0019] In an embodiment, a network node is provided that implements a CHF device that is configured to facilitate charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol. The network node includes processing circuitry configured to cause the network node to receive, from one or more of the UE or the AF device , a first set of connection IDs, for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE, and the second set of connection IDs are associated with the AF device, receive, a connection ID from an SMF device, associate the connection ID to the session in response to matching the connection ID to a connection ID from the first set of connection IDs or the second set of connection IDs, and provide, to the SMF device, a charging data record that comprises an indication the connection ID is associated with the session.

[0020] In another embodiment, a method for facilitating charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol performed by a PCF device is provided. The method includes receiving from one or more of the UE or the AF device, information about a first set of connection IDs, for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE, and the second set of connection IDs are associated with the AF device and providing, to an SMF device the information about the first set of connection IDs and the second set of connection IDs.

[0021] In an embodiment, a network node is provided that implements a PCF device that is configured to facilitate charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol. The network node includes processing circuitry configured to cause the network node to receive from one or more of the UE or the AF device, information about a first set of connection IDs for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE, and the second set of connection IDs are associated with the AF device and provide, to an SMF device the information about the first set of connection IDs and the second set of connection IDs.

[0022] In an embodiment, a method for facilitating charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol performed by the UE is provided. The method includes providing, to the AF device, a first set of connection IDs, for identifying the session, receiving, from the AF device, a second set of connection IDs for identifying the session, and providing, to a CHF device or a PCF device, information identifying the first set of connection IDs and the second set of connection IDs.

[0023] In an embodiment, a UE is provided that is configured to facilitate charging of a session between an AF device and the UE using a connection-oriented stateful transport protocol. The UE comprises processing circuitry to cause the UE to provide to the AF device a first set of connection IDs for identifying the session, receive from the AF device a second set of connection IDs for identifying the session, and provide, to a CHF device or a PCF device information identifying the first set of connection IDs and the second set of connection IDs.

[0024] An advantage provided by the methods and techniques disclosed herein is that it becomes possible to identify, on a low level, a connection or session even if the usage is reported from an observer and not the server (or client).

[0025] Brief Description of the

[0026] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0027] Figure 1 illustrates a representative service deployment cluster architecture according to one or more embodiments of the present disclosure;

[0028] Figure 2 illustrates a block diagram representation of several nodes of a communication system according to one or more embodiments of the present disclosure;

[0029] Figure 3 illustrates a message sequence chart of an embodiment for facilitating charging of a session between an Application Function (AF) device and a User Equipment (UE) using a connection-oriented stateful transport protocol according to one or more embodiments of the present disclosure;

[0030] Figure 4 illustrates a message sequence chart for another embodiment for facilitating charging of a session between an AF device and a UE using a connection- oriented stateful transport protocol according to one or more embodiments of the present disclosure;

[0031] Figures 5 illustrates example embodiments of a Fifth Generation (5G) System (5GS);

[0032] Figure 6 is a schematic block diagram of a network node according to some embodiments of the present disclosure;

[0033] Figure 7 is a schematic block diagram of the network node of Figure 6 according to some other embodiments of the present disclosure;

[0034] Figure 8 is a schematic block diagram of a UE according to some embodiments of the present disclosure; and Figure 9 is a schematic block diagram of the UE of Figure 8 according to some other embodiments of the present disclosure.

[0035] Detailed

[0036] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0037] User Equipment (UE): One type of communication device is a wireless communication device or a UE, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a cellular phone or smart phone in a Third Generation Partnership Project (3GPP) network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless connection.

[0038] Network Node: As used herein, a "network node" can be any type of apparatus / device in a 5G core network, or any apparatus / device that implements a network function. Some examples of a network nodes include, a computer or server host for e.g., a Policy and Control Function (PCF), Charging Function (CHF), Session Management Function (SMF), or Application Function (AF). In the following description, when stating that any of these functions, such as a PCF, SMF, CHF, or AF device, perform an action, such as examining / initiating / monitoring, etc., then it is to be understood that it is in practice the network node / computer / server host / device that hosts the PCF, SMF, CHF, or AF Function, respectively, that performs the action. One or both of the PCF, SMF, CHF, or AF may be part(s) of the IMS core network.

[0039] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0040] The current charging and accounting techniques do not take the connection identifiers (IDs) into account meaning that switching between networks may be more difficult to follow and may result in that a change in the network is seen as a new connection and a termination of an old.

[0041] Another issue with using the connection ID is that multiple connection IDs are used so that endpoints can send packets that cannot be identified by an observer as being for the same connection without cooperation from an endpoint.

[0042] The present disclosure provides a method and devices to facilitate charging for a session between an AF device and a UE when using a connection-oriented stateful transport protocol (e.g., such as QUIC - formerly "Quick User Datagram Protocol (UDP) Internet Connections). The UE and the AF device can exchange respective sets of connection IDs that can be used to identify the session, and the connection IDs can be stored at either a CHF device, or a PCF device. When messages are exchanged between the AF device and the UE using the connection IDs, the PCF or CHF can identify which sessions the messages correspond to based on the connection IDs, and can produce a charging data record (CDR) that links messages to sessions to facilitate charging.

[0043] In an embodiment, this enables online or offline charging to use the QUIC connection ID as part of the charging and identification of the connection or session between a client and a server. This means having the server (or client) submit all connection IDs related to a connection to the charging and then having any report from any observer including the connection ID when reporting usage.

[0044] Having the charging being able to determine that several messages belong to the same connection means that it can charge the connection differently i.e., a message belonging to a specific connection may be charged based on the volume from a specific account / bucket and cheaper than the individual messages that may instead be charged on a per message basis. Additionally, if a user is changed per every started kilobyte (kB), then a connection isn't rounded until the connection is ended, while for individual messages it will be rounded per message, e.g., if each message contains 1,5 kB and you have like 5 messages for the connection, then a connection based charging would result in charging 10 kB (each message would be rounded to 2 kB giving 10*2), if it instead is charged based on the connection then all 5 would be added before the rounding resulting in a charge of 8 kB (1, 5*5=7, 5 rounded to 8).

[0045] An advantage provided by the methods and techniques disclosed herein is that it becomes possible to identify, on a low level, a connection or session even if the usage is reported from an observer and not the server (or client).

[0046] Figure 1 illustrates a representative service deployment cluster architecture according to one or more embodiments of the present disclosure.

[0047] Some of the functions included in the service deployment cluster architecture include an SMF device 508, an AF device 512, a PCF 510, and a CHF 516.

[0048] Figure 2 illustrates a block diagram representation of several nodes of a communication system according to one or more embodiments of the present disclosure.

[0049] The AF device 512 holds the application and acts as a QUIC server interacting with the UE 800 acting as a QUIC client. It reports the QUIC connection IDs used for a specific application, both from the client and server side to the CHF device 516.

[0050] The SMF device 508 manages the Fifth Generation (5G) data connections and reports the usage to the CHF 516. This is done through the User Plane Function (UPF) device 516. The SMF device 508 may not have access to the connection IDs, and so cannot distinguish the messages and determine which communication session they messages are related to, but the CHF device 516 or the PCF device 510 has access to the connection IDs used by both the UE 800 and the AF device 512.

[0051] The CHF device 516 will store the connection IDs related to a specific application.

[0052] PCF device 510 sets the policies used for the 5G data connection.

[0053] Figure 3 illustrates a message sequence chart of an embodiment for facilitating charging of a session between an AF device and a UE using a connection-oriented stateful transport protocol according to one or more embodiments of the present disclosure. In an embodiment the connection-oriented stateful transport protocol can be QUIC, but in other embodiments, other protocols could be used.

[0054] In an embodiment, at 302, optionally a connection setup request can be sent from either the UE 800 or the AF device 512 to the other entity in order to setup a communication session.

[0055] At 304 the UE 800 sets up a connection (e.g., a QUIC connection) with the AF device 512 by sending a first set of connection IDs to help facilitate identifying the communication session. As an example, the first set of connection IDs could be sent using the current QUIC NEW_CONNECTION_ID frame.

[0056] At 306, the AF device 512 can respond with a second set of connection IDs to identify the communication session using the current QUIC NEW_CONNECTION_ID frame. The UE 800, when sending messages or packets to the AF device 512 can use connection IDs from the first set of connection IDs to appended or otherwise associated with the message to link the messages to the communication session. Likewise, the AF device 512, when sending messages to the UE 800, can use connection IDs from the second set of connection IDs.

[0057] Since the first and second set of connection IDs are exchanged with each of the AF device 512 and the UE 800, either the AF device 512 can provide both the first and the second set of connection IDs to the CHF device 516 at 308, or alternatively, the UE 800 can provide both the first and the second set of connection IDs to the CHF device 516 at 310.

[0058] AF device 512 or the UE 800 at steps 308 and 310 update the CHF device 516 with the information about the connection IDs (both from the UE 800 and AF device 512) used for a specific UE and application to the CHF device 516, using a new service. The CHF device 516 will then store this information. In an embodiment, the information identifying the first set of connection IDs and the second set of connection IDs also comprises information identifying the UE 800 and the AF device 512 or the session / connection.

[0059] At 312, optionally, packages can then be exchanged by the AF device 512 and the UE 800 using the respective connection IDs appended or associated with the messages. The UPF 514 can then inform or otherwise provide the SMF device 508 with the connection ID for the messages. At step 314, the SMF device 508 triggers a charging data record (CDR) request based on the network events or messages exchanged at step 312 and includes the respective connection IDs used with the messages. The connection ID would need to be added to the current Nchf_ConvergedCharging service, 3GPP TS 32.291 V18.2.0, clause 6.1.6.2.2. At this point the SMF device 508 does not know which connection IDs are associated with which communication session. The CHF device 516 does however. And so, the CHF device 516 matches the connection ID to the connection IDs received from the AF device 512 or the UE 800 to be able to associate this to the specific connection or session. The CHF device 516 then outputs this in the CDR at step 316, and provides the information to the SMF device 508. The information about the connection can be added to the current 3GPP TS 32.298 V18.2.0 clause 5.2.5.2.

[0060] At step 318, more messages can be exchanged, each message using an additional connection ID from either the first set of connection IDs or the second set of connection IDs. At step 320, if either the UE 800 or the AF device 512 needs to update its connection IDs used (in response to all the connection IDs in the respective sets being used at least once already) the AF device 512 or the UE 800 can trigger an update towards the UE 800 or the AF device 512 respectively using the current QUIC NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frame.

[0061] At 322 and 324, the UE 800 and the AF device 512 may, respectively update each other with an updated first set of connection IDs or an updated second set of connection IDs using the current QUIC NEW_CONNECTION_ID and RETIREJ2ONN ECTION-ID frame.

[0062] At steps 326 and / or 328, the AF device 512 or the UE 800 can update the CHF device 516 with the information about the connection IDs used for a specific UE and AF connection, and the CHF device 516 can store the information.

[0063] Figure 4 illustrates a message sequence chart for another embodiment for facilitating charging of a session between an AF device and a UE using a connection- oriented stateful transport protocol according to one or more embodiments of the present disclosure. The message sequence chart in Figure 4 is similar to that in Figure 3, except that the AF device 512 and the UE 800 may provide the first and second set of connection IDs to the PCF device 510 instead or in addition to providing the first and second set of connection IDs to the CHF device 516. In an embodiment, at 302, optionally a connection setup request can be sent from either the UE 800 or the AF device 512 to the other entity in order to setup a communication session.

[0064] At 304 the UE 800 sets up a connection (e.g., a QUIC connection) with the AF device 512 by sending a first set of connection IDs to help facilitate identifying the communication session. As an example, the first set of connection IDs could be sent using the current QUIC NEW_CONNECTION_ID frame.

[0065] At 306, the AF device 512 can respond with a second set of connection IDs to identify the communication session using the current QUIC NEW_CONNECTION_ID frame. The UE 800, when sending messages or packets to the AF device 512 can use connection IDs from the first set of connection IDs to appended or otherwise associated with the message to link the messages to the communication session. Likewise, the AF device 512, when sending messages to the UE 800, can use connection IDs from the second set of connection IDs.

[0066] Since the first and second set of connection IDs are exchanged with each of the AF device 512 and the UE 800, either the AF device 512 can provide both the first and the second set of connection IDs to the PCF device 510 at 402, or alternatively, the UE 800 can provide both the first and the second set of connection IDs to the PCF device 510 at 404.

[0067] AF device 512 or the UE 800 at steps 402 and 404 update the PCF device 510 with the information about the connection IDs (both from the UE 800 and AF device 512) used for a specific UE and application to the PCF device 510, using a new service Npcf_PolicyAuthorization service, 3GPP TS 23.502 V18.2.0 clause 5.2.5.3.. The PCF device 510 will then store this information.

[0068] At step 406, the PCF device 510 can provide the first and second set of connection IDs to the SMF device 508, this will make it possible for the SMF to match the QUIC messages to a session.

[0069] At 312, optionally, packages can then be exchanged by the AF device 512 and the UE 800 using the respective connection IDs appended or associated with the messages. The UPF 514 can then inform or otherwise provide the SMF device 508 with the connection ID for the messages.

[0070] At step 408, the SMF device 508 triggers a CDR request based on the QIUC messages being part of a connection / session. Information about the connection would need to be added to the current Nchf_ConvergedCharging service, 3GPP TS

[0071] 32.291 V18.2.0 clause 6.I.6.2.2.

[0072] At step 410, CHF device 516 rates the input based on that it is QUIC [3] and part of a session. The CHF outputs this in the CDR, information about the connection would need to be added to the current 3GPP TS 32.298 V18.2.0 clause 5.2.5.2.

[0073] At step 318, more messages can be exchanged, each message using an additional connection ID from either the first set of connection IDs or the second set of connection IDs. At step 320, if either the UE 800 or the AF device 512 needs to update its connection IDs used (in response to all the connection IDs in the respective sets being used at least once already) the AF device 512 or the UE 800 can trigger an update towards the UE 800 or the AF device 512 respectively using the current QUIC NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frame.

[0074] At 322 and 324, the UE 800 and the AF device 512 may, respectively update each other with an updated first set of connection IDs or an updated second set of connection IDs using the current QUIC NEW_CONNECTION_ID and RETIREJ2ONN ECTION-ID frame.

[0075] At steps 412 and / or 414, the AF device 512 or the UE 800 can update the PCF device 510 with the information about the connection IDs used for a specific UE and AF connection, and the PCF device 510 can store the information.

[0076] At 416, the PCF device 510 can then provide the updated first and second sets of connection IDs to the SMF device 508.

[0077] Figure 5 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface.

[0078] Seen from the access side the 5G network architecture shown in Figure 5 comprises a plurality of UEs 800 connected to either a Radio Access Network (RAN) 518 or an Access Network (AN) as well as an AMF 500. Typically, the R(AN) 518 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 5 include a NSSF 502, an AUSF 504, a UDM 506, the AMF 500, a SMF 508, a PCF 510, a CHF 516, and an AF 512.

[0079] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 800 and AMF 500. The reference points for connecting between the RAN 518 and AMF 500 and between the RAN 518 and UPF 514 are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF 500 and SMF 508, which implies that the SMF 508 is at least partly controlled by the AMF 500. N4 is used by the SMF 508 and UPF 514 so that the UPF 514 can be set using the control signal generated by the SMF 508, and the UPF 514 can report its state to the SMF 508. N9 is the reference point for the connection between different UPFs 514, and N14 is the reference point connecting between different AMFs 500, respectively. N15 and N7 are defined since the PCF 510 applies policy to the AMF 500 and SMF 508, respectively. N12 is required for the AMF 500 to perform authentication of the UE 800. N8 and N10 are defined because the subscription data of the UE 800 is required for the AMF 500 and SMF 508.

[0080] The 5GC network aims at separating User Plane (UP) and Control Plane (CP). The UP carries user traffic while the CP carries signaling in the network. In Figure 5, the UPF 514 is in the UP and all other NFs, i.e., the AMF 500, SMF 508, PCF 510, AF 512, NSSF 502, AUSF 504, and UDM 506, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0081] The core 5G network architecture is composed of modularized functions. For example, the AMF 500 and SMF 508 are independent functions in the CP. Separated AMF 500 and SMF 508 allow independent evolution and scaling. Other CP functions like the PCF 510 and AUSF 504 can be separated as shown in Figure 5. Modularized function design enables the 5GC network to support various services flexibly.

[0082] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0083] Some properties of the NFs shown in Figures 5 may be described in the following manner. The AMF 500 provides UE-based authentication, authorization, mobility management, etc. A UE 800 even using multiple access technologies is basically connected to a single AMF 500 because the AMF 500 is independent of the access technologies. The SMF 508 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 514 for data transfer. If a UE 800 has multiple sessions, different SMFs 508 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 512 provides information on the packet flow to the PCF 510 responsible for policy control in order to support QoS. Based on the information, the PCF 510 determines policies about mobility and session management to make the AMF 500 and SMF 508 operate properly. The AUSF 504 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 506 stores subscription data of the UE 800. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0084] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0085] Figure 6 is a schematic block diagram of a network node 600 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 600 may for example implement SMF device 508, PCF device 510, CHF device 516, and AF device 512. As illustrated, the network node 600 includes a control system 602 that includes one or more processors 604 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory / computer readable storage medium 606, and a network interface 608. The one or more processors 604 are also referred to herein as processing circuitry. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 606 and executed by the one or more processors 604.

[0086] In some embodiments, the function(s) are implemented in one or more computer programs 610 that are stored, e.g., in the memory 606 and executed by the one or more processors 604. The computer program 610 can include instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of network node 600 or a node implementing one or more of the functions of the network node 600. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0087] Figure 7 is a schematic block diagram of the network node 600 according to some other embodiments of the present disclosure. The network node 600 includes one or more modules, each of which is implemented in software. The module(s) (e.g., SMF device 508, PCF device 510, CHF device 516, and AF device 512) provide the functionality of the network node 600 described herein.

[0088] Figure 8 is a schematic block diagram of a wireless communication device 800 according to some embodiments of the present disclosure. As illustrated, the wireless communication device 800 includes one or more processors 802 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 804, and one or more transceivers 806 each including one or more transmitters 808 and one or more receivers 810 coupled to one or more antennas 812. The transceiver(s) 806 includes radio-front end circuitry connected to the antenna(s) 812 that is configured to condition signals communicated between the antenna(s) 812 and the processor(s) 802, as will be appreciated by one of ordinary skill in the art. The processors 802 are also referred to herein as processing circuitry. The transceivers 806 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 800 described above may be fully or partially implemented in software that is, e.g., stored in the memory 804 and executed by the processor(s) 802. Note that the wireless communication device 800 may include additional components not illustrated in Figure 8 such as, e.g., one or more user interface components (e.g., an input / output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and / or the like and / or any other components for allowing input of information into the wireless communication device 800 and / or allowing output of information from the wireless communication device 800), a power supply (e.g., a battery and associated power circuitry), etc.

[0089] In some embodiments, a computer program 812 is included which includes instructions which, when executed by at least one processor 802, causes the at least one processor to carry out the functionality of the wireless communication device 800 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0090] Figure 9 is a schematic block diagram of the wireless communication device 800 according to some other embodiments of the present disclosure. The wireless communication device 800 includes one or more modules 900, each of which is implemented in software. The module(s) 900 provide the functionality of the wireless communication device 800 described herein.

[0091] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0092] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0093] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims1. A method for facilitating charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol performed by the AF device (512), the method comprising: receiving (304) from the UE (800), a first set of connection identifiers, IDs, for identifying the session; providing (306) to the UE (800), a second set of connection IDs for identifying the session; and providing (308, 402), to a Charging Function, CHF, device (516) or a Policy Control Function, PCF, device (510), information identifying the first set of connection IDs and the second set of connection IDs.

2. The method of claim 1, wherein the receiving the first set of connection identifier and providing the second set of connection IDs is in response to: receiving (302) from the UE (800) a request to set up the session.

3. The method of claim 1, wherein the receiving the first set of connection identifier and providing the second set of connection IDs is in response to: providing (302) to the UE (800) a request to set up the session.

4. The method of any of claims 1 to 3, further comprising: providing (312) one or more messages to the UE (800), each message of the one or more messages comprising a connection ID from the second set of connection IDs.

5. The method of claim 4, further comprising: in response to using all connection IDs in the one or more messages to the UE (800), providing (320) a connection ID update request to the UE (800); and receiving (322) an updated first set of connection IDs from the UE (800).

6. The method of claim 4, further comprising: receiving (320) a connection ID update request from the UE; and receiving (322) an updated first set of connection IDs from the UE (800).

7. The method of claims 5 and 6, further comprising: providing (326, 412) the updated first set of connection IDs associated with the UE (800) and an updated second set of connection IDs associated with the AF device (512) to the CHF device (516) or PCF device (510).

8. The method of any of claims 1 to 7, wherein the information identifying the first set of connection IDs and the second set of connection IDs also comprises information identifying the UE (800) and the AF device (512) or the session.

9. A network node that implements an Application Function, AF, device (512) that is configured to facilitate charging of a session between the AF device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol, the network node comprising processing circuitry configured to cause the network node to: receive (304) from the UE (800), a first set of connection identifiers, IDs, for identifying the session; provide (306) to the UE (800), a second set of connection IDs for identifying the session; and provide (308, 402), to a Charging Function, CHF, device (516) or a Policy Control Function, PCF, device (510), information identifying the first set of connection IDs and the second set of connection IDs.

10. The network node of claim 9, wherein the processing circuitry is further configured to perform the methods of claims 2 to 8.

11. A method for facilitating charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol performed by a Charging Function, CHF, device (516), the method comprising: receiving (308, 310), from one or more of the UE (800) or the AF device (512), a first set of connection identifiers, IDs, for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs areassociated with the UE (800), and the second set of connection IDs are associated with the AF device (512); receiving (314), a connection ID from a Session Management Function, SMF, device (508); associating (316) the connection ID to the session in response to matching the connection ID to a connection ID from the first set of connection IDs or the second set of connection IDs; and providing (316), to the SMF device (508), a charging data record that comprises an indication the connection ID is associated with the session.

12. The method of claim 11, further comprising: receiving (326, 328), from the UE (800) or the AF device (512), an updated first set of connection IDs associated with the UE (800) and an updated second set of connection IDs associated with the AF device (512).

13. The method of claim 11, further comprising: receiving (408) from the SMF device (508) an indication that the connection ID is associated with the session.

14. A network node that implements a Charging Function, CHF, device (516) that is configured to facilitate charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol, the network node comprising processing circuitry configured to cause the network node to: receive (308, 310), from one or more of the UE (800) or the AF device (512), a first set of connection identifiers, IDs, for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE (800), and the second set of connection IDs are associated with the AF device (512); receive (314), a connection ID from a Session Management Function, SMF, device (508);associate (316) the connection ID to the session in response to matching the connection ID to a connection ID from the first set of connection IDs or the second set of connection IDs; and provide (316), to the SMF device (508), a charging data record that comprises an indication the connection ID is associated with the session.

15. The network node of claim 14, wherein the processing circuitry is further configured to perform the methods of claims 12 to 13.

16. A method for facilitating charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol performed by a Policy Control Function, PCF, device (510), the method comprising: receiving (402, 404), from one or more of the UE (800) or the AF device (512), information about a first set of connection identifiers, IDs, for identifying the session and a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE (800), and the second set of connection IDs are associated with the AF device (512); and providing (406), to a Session Management Function, SMF, device (508), the information about the first set of connection IDs and the second set of connection IDs.

17. The method of claim 16, further comprising: receiving, from the UE (800) or the AF device (512), an updated first set of connection IDs associated with the UE (800) and an updated second set of connection IDs associated with the AF device (512).

18. A network node that implements a Policy Control Function, PCF, device (510) that is configured to facilitate charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol, the network node comprising processing circuitry configured to cause the network node to: receive (402, 404), from one or more of the UE (800) or the AF device (512), information about a first set of connection identifiers, IDs, for identifying the sessionand a second set of connection IDs for identifying the session, wherein the first set of connection IDs are associated with the UE (800), and the second set of connection IDs are associated with the AF device (512); and provide (406), to a Session Management Function, SMF, device (508), the information about the first set of connection IDs and the second set of connection IDs.

19. The network node of claim 18, wherein the processing circuitry is further configured to perform the method of claim 17.

20. A method for facilitating charging of a session between an Application Function, AF, device (512) and a User Equipment, UE, (800) using a connection-oriented stateful transport protocol performed by the UE (800), the method comprising: providing (304), to the AF device (512), a first set of connection identifiers, IDs, for identifying the session; receiving (306), from the AF device (512), a second set of connection IDs for identifying the session; and providing (310, 404), to a Charging Function, CHF, device (516) or a Policy Control Function, PCF, device (510), information identifying the first set of connection IDs and the second set of connection IDs.

21. The method of claim 20, further comprising: receiving (302) from the AF device (512) a request to set up the session.

22. The method of claim 20, further comprising: providing (302) to the AF device (512) a request to set up the session.

23. The method of any of claims 20 to 22, further comprising: providing (312, 318) one or more messages to the AF device (512), each message of the one or more messages comprising a connection ID from the first set of connection IDs.

24. The method of claim 23, further comprising:in response to using all connection IDs in the one or more messages to the AF device (512), providing (320) a connection ID update request to the AF device (512); and receiving (324) an updated second set of connection IDs from the UE.

25. The method of claim 23, further comprising: receiving (320) a connection ID update request from the AF device (512); and receiving (324) an updated second set of connection IDs from the AF device (512).

26. The method of claims 24 and 25, further comprising: providing (328, 414) the updated first set of connection IDs associated with the UE (800) and an updated second set of connection IDs associated with the AF device (512) to the CHF device (516) or PCF device (510).

27. A User Equipment, UE, (800) that is configured to facilitate charging of a session between an Application Function, AF, device (512) and the UE (800), using a connection-oriented stateful transport protocol, the UE (800) comprising processing circuitry configured to cause the UE to: provide (304), to the AF device (512), a first set of connection identifiers, IDs, for identifying the session; receive (306), from the AF device (512), a second set of connection IDs for identifying the session; and provide (310, 404), to a Charging Function, CHF, device (516) or a Policy Control Function, PCF, device (510), information identifying the first set of connection IDs and the second set of connection IDs.

28. The UE (800) of claim 27, wherein the processing circuitry is further configured to perform the methods of claims 21 to 26.

Images