Patent Description:
Documents detailing the defining architecture and specifications for Fifth Generation (<NUM>) wireless communication networks include Technical Specification (TS) <NUM> V16. <NUM> (<NUM>-<NUM>) and TS <NUM> V16. <NUM> (<NUM>-<NUM>), released by the Third Generation Partnership Project (3GPP). Relevant details for <NUM> Core (5GC) networks include different "roaming" scenarios-see at least Sections <NUM>. <NUM>, <NUM>. <NUM>, and <NUM>. <NUM> of TS <NUM>. Other 3GPP documents of interest include 3GPP TS <NUM> V17. <NUM>, and 3GPP TS <NUM> V16.

A first roaming scenario between a Visited Public Mobile Network (VPMN) and a Home PMN (HPMN) involves "home routing" (HR). In an example based on visited and home 5GC networks, user traffic carried by the visited 5GC network for a communication session involving a roaming UE is routed back to the home 5GC network of the UE. HR provides a direct mechanism for the home 5GC network to determine traffic usage for the communication session and carry out corresponding charging operations.

A second roaming scenario does not involve home routing of the user traffic exchanged between the roaming UE and the visited 5GC network. Instead, the visited 5GC network performs a "local breakout" (LBO). With LBO, the visited 5GC network offloads at least some of the user traffic in the communication session to a data network (DN), rather than routing it back to the home 5GC network. Current 3GPP specifications do not define traffic-usage reporting by the visited network back to the home network, for offloaded traffic.

<CIT> describes a traffic offload method, comprising receiving, by a first traffic offload function entity, user information that is of a user equipment within coverage of the first traffic offload function entity and sent by a core network device; obtaining, by the first traffic offload function entity, a traffic offload policy; matching the traffic offload policy with the user information; and offloading, by the first traffic offload function entity, traffic corresponding to the user equipment according to the user information that successfully matches the traffic offload policy.

<CIT> describes after determining that an access subscriber is a roaming subscriber, establishing, by a visited-place packet data network gateway, an online charging session for the access subscriber; determining a first charging information parameter list; sending, to a home online charging system, a first quota request message carrying a rating group; receiving a roaming data service quota of the rating group sent by the home online charging system; and sending first charging information to the home online charging system according to the first charging information parameter list.

According to techniques disclosed herein, a Visited Communication Network (VCN) selectively reports usage information back to a Home Communication Network (HCN) for user traffic that is offloaded at the VCN to a Data Network (DN) rather than routed back to the HCN. Among the various advantages, the reporting supports charging operations in the HCN regarding the offloaded traffic. Further advantages include the application of policy and service-authorization control jointly between the VCN and the HCN.

Further example embodiments will now be described in more detail and with references to the enclosed drawings.

<FIG> illustrates an example of a Visited Communication Network (VCN) <NUM>, also referred to as a Visited Public Mobile Network (VPMN) or a Visited Public Land Mobile Network (VPLMN). The VCN <NUM> supports a communication session between a User Equipment (UE) <NUM> and a Data Network (DN) <NUM>. Referring hereafter to the UE <NUM> as the "communication device <NUM>", the VCN <NUM> communicatively couples to the communication device <NUM> via one or more radio links provided by a Radio Access Network (RAN) portion of the VCN <NUM>, illustrated as a Next Generation (NG) RAN <NUM> in the diagram. The NG designation indicates configuration according to the New Radio (NR) standards developed by the Third Generation Partnership Project (3GPP) for Fifth Generation (<NUM>) communication networks. A network node in the VCN <NUM> operating as a User Plane Function (UPF) <NUM> provides the data-network connectivity.

One or more further network nodes of the VCN <NUM> implement various functions associated with operation of the VCN <NUM> as a <NUM> Core (5GC) network. Such functions include an Application Management Function (AMF) <NUM>, a Session Management Function (SMF) <NUM>, a Charging Function (CHF) <NUM>, which couples to a billing domain <NUM> of the VCN <NUM>. Further example functions include a Network Slice Selection Function (NSSF) <NUM>, a Network Exposure Function (NEF) <NUM>, a Network Repository Function (NRF) <NUM>, a Policy Control Function (PCF) <NUM>, a User Data Management (UDM) <NUM>, an Applicant Function (AF) <NUM>, and a Network Data Analytics Function (NWDAF) <NUM>.

A Home Communication Network (HCN) <NUM> includes one or more network nodes <NUM> ("NW NODE(s)" in the diagram), and further includes a billing domain <NUM>. The HCN <NUM> may also be referred to as a Home Public Mobile Network (HPMN) or a Home Public Land Mobile Network (HPLMN).

Advantageously, the SMF <NUM> or the CHF <NUM> in the VCN <NUM> provides an interface <NUM> or <NUM>, for selectively reporting usage information for user traffic that is "offloaded" by the VCN <NUM> rather than routed back to the HCN <NUM>. Here, the communication device <NUM> is associated with the HCN <NUM>-e.g., via a subscription arrangement-but the communication device <NUM> is operating outside of the HCN <NUM> ("roaming") and it uses the VCN <NUM> to establish a communication session with a DN <NUM>.

In a home-routing scenario, the user traffic conveyed in the communication session is routed through the HCN, e.g., the HCN <NUM> provides the connection to the DN <NUM> and the user traffic goes through both the VCN <NUM> and the HCN <NUM>. Home routing provides direct visibility and charging control by the HCN <NUM> with respect to the communication session. However, traffic "offloading", also referred to as Local Breakout or LBO, may be used at the VCN <NUM>. With traffic offloading, the VCN <NUM> connects the communication device <NUM> to the DN <NUM> and the user traffic going between the communication device <NUM> and the DN <NUM> for the communication session is not routed back through the HCN <NUM>.

In one or more embodiments contemplated herein, the interface <NUM> or <NUM> implemented via the SMF <NUM> or the CHF <NUM> in the VCN <NUM> provides for usage reporting by the VCN <NUM> back to the HCN <NUM>, for offloaded traffic. Such reporting may be selective and undertaken only for offloaded user traffic for which usage reporting back to the HCN <NUM> is indicated. Further, in at least one contemplated embodiment, the interface <NUM> or <NUM> provides for service authorization and policy control for the communication session, based on policy and authorization control agreed between the VCN <NUM> and the HCN <NUM>.

<FIG> illustrates an example embodiment using the interface <NUM>. Named functions in the VCN <NUM> are prepended by a "V" to denote the "Visited" network. Similarly, named functions in the HCN <NUM> are prepended by an "H" to denote the "Home" network. These visited and home designations are relative to the scenario where a communication device <NUM> of the HCN <NUM> is roaming and connects to the VCN <NUM> for one or more communication services. Further, the illustrated functions in the VCN <NUM> shall be understood as being implemented on one or more network nodes, e.g., computer systems, and the same understanding holds regarding the illustrated functions in the HCN <NUM>.

In the VCN <NUM>, a V-PCF <NUM> interfaces to a V-AMF <NUM>, a V-SMF <NUM>, a V-NEF <NUM>, a V-AF <NUM>, and a V-NWDAF <NUM>. See the N15 interface point between the V-PCF <NUM> and the V-AMF <NUM>, the N7 interface point between the V-PCF <NUM> and the V-SMF <NUM>, the N30 interface point between the V-PCF <NUM> and the V-NEF <NUM>, the N5 interface point between the V-PCF <NUM> and the V-AF <NUM>, and the N23 interface point between the V-PCF <NUM> and the V-NWDAF <NUM>. Additional interface points include the N4 interface between the V-UPF <NUM> and the V-SMF <NUM>, and an N40 interface point between an H-SMF <NUM> and an H-CHF <NUM> in the HCN <NUM>, which also includes an H-NRF <NUM>. An interface <NUM> between the V-SMF <NUM> and the V-CHF <NUM> supports communications between the V-SMF <NUM> and the V-CHF <NUM> in the context of usage-information reporting back to the HCN <NUM>, for offloaded traffic.

<FIG> illustrates additional example details for the VCN <NUM> and the HCN <NUM> in relation to <FIG>. According to the embodiment of <FIG> and <FIG>, usage information for user traffic offloaded at the VCN <NUM> is reported from the V-SMF <NUM> to the H-SMF <NUM> in the HCN <NUM>. In turn, the H-SMF <NUM> communicates the usage information to the H-CHF <NUM>. In an example, the V-SMF <NUM> in the VCN <NUM> determines that usage reporting is to be used for the offloaded traffic based on traffic-steering information in a Policy Control and Charging (PCC) rule. That is, there may be some types of offloaded traffic or some instances of traffic offloading for which usage reporting back to the HCN <NUM> is not performed by the VCN <NUM>, such that the usage reporting described herein happens on a selective basis, responsive to determining that the offloaded traffic at issue is to be reported.

PCC rules applicable to the communication session in question include Charging Keys that are agreed between the VCN <NUM> and the HCN <NUM> or are otherwise set by the VCN <NUM> on behalf of the HCN <NUM>. Such PCC rules may be provided to the VCN <NUM> by an H-PCF in the HCN <NUM>. For a communication session of a communication device <NUM> that has some traffic offloaded at the VCN <NUM> and some traffic routed to the HCN <NUM>, the V-SMF <NUM> in the VCN <NUM> is instructed to report the traffic usage to the H-SMF <NUM>, which reports the usage to the H-CHF <NUM>. In an online charging case, the H-SMF <NUM> requests quotas from the H-CHF <NUM> for authorizing corresponding amounts of service consumption for the communication session, and correspondingly provides service-authorization information to the V-SMF <NUM> in the VCN <NUM> via the interface <NUM>.

In one or more embodiments, the V-SMF <NUM> in the VCN <NUM> receives instructions from the H-PCF via the H-SMF <NUM> for a service data flow that may be routed through different Data Network Access Identifier (DNAIs). A communication session may contain more than one service data flow, where each service data flow is an aggregate set of packet flows carried through the UPF that match a service data flow template defined in a PCC rule. For DNAIs associated with traffic offloading, the V-SMF <NUM> reports usage information back to the H-SMF <NUM>.

A PCC rule for AF-influenced traffic steering may be extended, to cause usage information reporting from the VCN <NUM> back to the HCN <NUM> for certain user traffic offloaded at the VCN <NUM>. AF-influenced traffic steering enables the routing of the user traffic matching the service data flow templates provided in the PCC rule to a DN identified by a DNAI. An example PCC rule includes the following Information Elements (IEs):.

In the above rule example, the IE used to indicate whether usage information reporting to the H-SMF <NUM> is requested provides a mechanism for selective or conditional reporting. That is, this IE extends the PCC rule.

<FIG> illustrates another embodiment wherein, in comparison to the embodiment of <FIG>, the V-SMF <NUM> reports usage information directly to the H-CHF <NUM> in the HCN <NUM>. Thus, rather than the interface <NUM> coupling the V-SMF <NUM> to the H-SMF <NUM>, the interface <NUM> in this embodiment communicatively couples the V-SMF <NUM> to the H-CHF <NUM> and operates as a "roaming interface" between the V-SMF <NUM> and the H-CHF <NUM>. <FIG> indicates the roaming distinction by labeling the logical interface point between the V-SMF <NUM> and the H-CHF <NUM> as "N40r", to differentiate between the conventional interface point N40 that exits between an SMF and a CHF that belong to the same 5GC network. Of course, a new reference point between the V-SMF <NUM> and H-CHF <NUM> may be introduced. Regardless, Nchf services are offered by the H-CHF <NUM> and consumed for the V-SMF <NUM>, where "Nchf' refers to the service-based interface exhibited by the H-CHF <NUM> according to the 3GPP standards.

The H-CHF address is obtained from any of (i) the V-SMF <NUM> using the V-NRF <NUM> and the H-NRF <NUM> following the procedure defined in Section <NUM>. <NUM> of TS <NUM>, entitled "NF discovery across PLMNs in the case of discovery made by NF service consumer", (ii) a local configuration in the V-SMF <NUM> that is based on Subscription Permanent Identifier SUPI ranges or (iii) the V-PCF <NUM> at the establishment of a Session Management SM Policy association as defined in Section <NUM>. <NUM> in TS <NUM>. For example, the V-PCF <NUM> provides the H-CHF address to the V-SMF <NUM> based on the roaming profile per roaming partner.

PCC rules provided to the V-SMF <NUM> by the V-PCF <NUM> include Charging Keys, for example, that are agreed between the HCN <NUM> and the VCN <NUM>. Charging Keys identify the type of communication service and how to charge for it-see 3GPP TS <NUM> and TS <NUM>. Charging Keys for some specific services such as general Mobile Broadband (MBB) may be standardized by GSMA, for example. The term "rating group" may be used rather than "Charging Key"-see 3GPP TS <NUM>. The V-SMF <NUM> supports interfaces <NUM>, <NUM> to both the H-CHF <NUM> and the V-CHF <NUM> for the purpose of charging data collection as defined in TS <NUM>. This means that the V-SMF <NUM> must set up double reporting and usage monitoring for service consumption occurring in the communication session.

<FIG> illustrates another embodiment, wherein the V-CHF <NUM> reports to the H-CHF <NUM>, as compared to the embodiments of <FIG> and <FIG>, in which the V-SMF <NUM> operated as the network node in the VCN <NUM> that reports usage information back to the HCN <NUM>. The interface <NUM> implemented between the V-CHF <NUM> and the H-CHF <NUM> provides communicative coupling between them and may be regarded as an N40r roaming interface.

The address of the H-CHF <NUM> is obtained from the H-NRF <NUM> via the V-NRF <NUM>, or by a local configuration at the V-SMF <NUM> that is based on SUPIs, or it is provided by the V-PCF <NUM> based on the roaming profile per roaming partner. In example operation, the address of the H-CHF <NUM> flows to the V-CHF <NUM> through the V-SMF <NUM>, such as part of the V-SMF <NUM> providing PCC rules or information derived therefrom, based on the V-PCF <NUM> providing the PCC rules to the V-SMF <NUM>. The PCC rules provided by the V-PCF <NUM> may include Charging Keys known to the VCN <NUM>. The V-CHF <NUM> performs a mapping of the Charging Keys known to the VCN <NUM> to the Charging Keys known by the HCN <NUM>. For example, the V-CHF <NUM> can map a Charging Key of the HCN <NUM> to a Charging Key of the VCN <NUM> as long as the VCN/HCN Charging Keys have the same meanings, and also in cases where the VCN <NUM> has Charging-Key definitions that are more granular than those used in the HCN <NUM>.

In a scenario involving online charging of a communication session that involves offloaded traffic for which usage information is to be reported from the VCN <NUM> to the HCN <NUM>, the V-CHF <NUM> requests service quotas for authorizing consumption of the communication service represented by the communication session. Such requesting happens per Charging Key from the H-CHF <NUM>, and the V-CHF <NUM> provides authorized quotas to the V-SMF <NUM>, to support service consumption by the communication device <NUM>. Further, the V-CHF <NUM> in such embodiments combines the VCN and HCN charging triggers applicable to the communication session, to fulfill the trigger requirements for the H-CHF <NUM> and the V-CHF <NUM>.

In at least one embodiment, the V-PCF <NUM> provides rules to V-SMF <NUM>, indicating that usage reporting is required for at least some offloaded traffic of a communication session that involves a visiting communication device <NUM>-i.e., a communication device <NUM> that is associated with another communication network as a home network of that device. In one or more embodiments, the V-SMF <NUM> in the VCN <NUM> implements the reporting and sends the usage information to an H-SMF <NUM> in the HCN <NUM>. Alternatively, the V-SMF <NUM> sends the usage information directly to an H-CHF <NUM> in the HCN <NUM>, rather than reporting it to the H-SMF <NUM>. In still other embodiments, the V-CHF <NUM> rather than the V-SMF <NUM> performs the usage. In such embodiments, information indicating when and how to perform the usage reporting may flow to the V-CHF <NUM> from the V-PCF <NUM>, via the V-SMF <NUM>.

<FIG> is a signal flow diagram according to one embodiment. The diagram illustrates example signaling for a Charging Data Request and Update for a Protocol Data Unit (PDU) session that involves user traffic offloaded at the VCN <NUM> and other user traffic that is routed back to the HCN <NUM>. The signaling flow provides for a PDU session establishment procedure for LBO, according to the VCN/HCN implementation depicted in <FIG>.

Steps <NUM>-<NUM> describes PDU session establishment as defined in Section <NUM>. <NUM> of TS <NUM>, for the non-roaming case. In Step 9a, the V-SMF <NUM> finds the address of the V-CHF <NUM> based on VPLMN Id or SUPI ranges locally configured or based on CHF addresses received from the V-PCF <NUM> or via NRF discovery. The V-SMF <NUM> sends an initial Charging Data Request to the V-CHF <NUM> and then, in Step 9b, the V-CHF <NUM> maps the Charging Key (CK) in the VCN <NUM> to the Charging Key in the HCN <NUM> and finds the H-CHF <NUM> in the HCN <NUM>, based on local configuration information, or based on NRF information received from the V-SMF <NUM>.

The H-CHF <NUM> may further include a transaction Id that may be used to confirm that the reported units have been stored by the H-CHF <NUM>. This transaction Id can be linked or contain the used units and the communication session it relates to. The transaction id can then be stored in the V-CHF <NUM> for later accounting purposes.

At Step 9c, the H-CHF <NUM> allocates a quota, Charging Data Records (CDRs) are opened, and a Charging ID is assigned. In steps <NUM>-<NUM> the PDU session establishment follows, as defined in Section <NUM>. <NUM> of TS <NUM> for the non-roaming case.

Various embodiments described herein may encompass the advantage of allowing the HCN <NUM> to have an improved overview of traffic usage, for traffic offloaded to a DN <NUM> at a VCN <NUM>, for a communication session involving the VCN <NUM> and a communication device <NUM> associated with the HCN <NUM>. Example advantages include:.

<FIG> illustrates an example signaling flow for carrying out a procedure to request a service quota for traffic offloaded at the VCN <NUM>, according to one or more embodiments. At Step 1a, the V-SMF <NUM> reports to the H-SMF <NUM> the list of supported DNAIs. The H-SMF <NUM> decides to instruct the V-SMF <NUM> to route a service data flow to a DNAI that is controlled by the V-SMF <NUM>. At Step 2a, the H-SMF <NUM> may request quota for the CK for the service data flow, and report that a change of DNAI (or UPF) will happen.

At Step 2b, the H-SMF <NUM> performs authorization, performs Charging Data Record (CDR) creation, and performs quota allocation to Ratings Groups (RGs) / Charging Keys (CK). A Converged Charging System (CCS) of the HCN <NUM> provides the quota at issue.

At Step <NUM>, the H-SMF <NUM> provides N4 rules, including the quota per CK and an indication that the traffic usage is to be reported to the H-SMF <NUM>. Step <NUM> involves UPF addition, relocation, or removal. At Step <NUM>, the V-SMF <NUM> sends an Nsmf_PDUSession_UpdateResponse message to the H-SMF <NUM>.

Turning to other considerations, for purposes of explanation and not limitation, specific details set forth herein, such as particular nodes, functional entities, techniques, protocols, standards, etc., are provided to facilitate an understanding of the described technology. It will be apparent to one skilled in the art that other embodiments may be practiced apart from the specific details disclosed below. In other instances, detailed descriptions of well-known methods, devices, techniques, etc., are omitted so as not to obscure the description with unnecessary detail. Individual function blocks are shown in the figures. Those skilled in the art will appreciate that the functions of those blocks may be implemented using individual hardware circuits, using software programs and data in conjunction with a suitably programmed microprocessor or general purpose computer, using applications specific integrated circuitry (ASIC), and/or using one or more digital signal processors (DSPs). The software program instructions and data may be stored on computer-readable storage medium and when the instructions are executed by a computer or other suitable processor control, the computer or processor performs the functions.

Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudocode, and the like represent various processes which may be substantially represented in a non-transitory computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

The functions of the various elements including functional blocks, including but not limited to those labeled or described as "computer", "processor" or "controller" may be provided through the use of hardware such as circuit hardware and/or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being hardware-implemented and/or computer-implemented, (e.g., machine-implemented).

In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) (ASIC), and (where appropriate) state machines capable of performing such functions.

In terms of computer implementation, a computer is generally understood to comprise one or more processors, or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer, processor, or controller, by a single shared computer, processor, or controller, or by a plurality of individual computers, processors, or controllers, some of which may be shared or distributed. Moreover, use of the term "processor" or "controller" shall also be construed to refer to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above. The term "processing circuitry" shall cover all such possibilities.

The technology may be used in any type of cellular radio communications (e.g., GSM, CDMA, <NUM>, <NUM>, etc.). For ease of description, the term UE and the alternative term "communication device" encompass any kind of radio communications terminal/device, mobile station (MS), PDAs, cell phones, laptops, etc..

With the foregoing "computer" implementation flexibility in mind, <FIG> is a block diagram illustrating a network node <NUM> according to one or more embodiments, wherein the network node <NUM> implements any one or more of the functions detailed herein for the VCN <NUM>. For example, in one or more embodiments, an instance of the network node <NUM> is configured for operation as a V-SMF <NUM> in a VCN <NUM>, another instance of the network node <NUM> is operative as a V-CHF <NUM> in the VCN <NUM>, and yet another instance of the network node <NUM> is operative as a V-PCF <NUM> in the VCN <NUM>. Of course, a given instance of the network node <NUM> may implement more than one function and different instances of the network node <NUM> may be configured to implement different functions based on executing different computer programs.

Thus, the network node <NUM> may also be understood as a computing system environment that is configurable according to the particular computer program instructions executed in the computing system environment. However, the illustrated computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the subject matter disclosed herein. Further, the computing system environment shown is not intended to suggest any dependency or requirement relating to the disclosed subject matter and any one or combination of components illustrated in the computing system environment.

Illustrated components of the network node <NUM> include a processing unit <NUM>, a system memory <NUM>, and a system bus <NUM> that couples various system components including the system memory <NUM> to the processing unit <NUM>. The system bus <NUM> can be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.

The example network node <NUM> may include or access a variety of transitory and non-transitory computer readable media. By way of example, and not limitation, computer readable media can comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile as well as removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media examples include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CDROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information, and which can be accessed by the processing unit <NUM>. Communication media can embody computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and can include any suitable information delivery media.

Turning to <FIG> momentarily, a computer program product <NUM> comprises a computer program <NUM> embodied in a computer readable medium <NUM>, such as a disk. The network node <NUM> may be configured to operate as a V-SMF <NUM>, a V-CHF <NUM>, or a V-PCF <NUM>, according to the particulars of the computer program <NUM> loaded or otherwise stored in the network node <NUM> for execution by the processing unit <NUM>. The processing unit <NUM> may be a digital signal processor, a microprocessor, or other digital processing circuitry and is also referred to as processing circuitry <NUM>.

The system memory <NUM> can include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and/or random access memory (RAM). A basic input/output system (BIOS), containing the basic routines that help to transfer information between elements within network node <NUM>, such as during start-up, can be stored in the system memory <NUM>. Further, the system memory <NUM> can also contain data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit <NUM>. By way of non-limiting example, the system memory <NUM> can also include an operating system, application programs, other program modules, and program data.

The system memory <NUM> may include a software module loaded in the memory and processable by the processing unit <NUM>, or other circuitry which causes the network node <NUM> to carry out the V-SMF, V-CHF, or V-PCF operations described herein, for enabling and performing usage information reporting for user traffic offloaded at the VCN <NUM>.

In particular, the system memory <NUM> may include an execution module <NUM> that is executed by the processing unit <NUM> or other processing circuitry of the network node <NUM>, which causes the network node <NUM> to perform the V-SMF or the V-CHF functions described herein.

The network node <NUM> can also include other removable/non-removable and volatile/nonvolatile computer storage media. For example, network node <NUM> can include a hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive that reads from or writes to a removable, nonvolatile magnetic disk, and/or an optical disk drive that reads from or writes to a removable, nonvolatile optical disk, such as a CD-ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM and the like. A hard disk drive can be connected to the system bus <NUM> through a non-removable memory interface such as an interface, and a magnetic disk drive or optical disk drive can be connected to the system bus <NUM> by a removable memory interface, such as an interface.

A user can enter commands and information into the network node through input devices such as a keyboard or a pointing device such as a mouse, trackball, touch pad, and/or another pointing device. Other input devices can include a microphone, joystick, game pad, satellite dish, scanner, or similar devices. These and/or other input devices can be connected to the processing unit <NUM> through a user input interface <NUM> that is coupled to the system bus <NUM> but can be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB).

A graphics subsystem can also be connected to the system bus <NUM>. In addition, a monitor or other type of display device can be connected to the system bus <NUM> through an output interface <NUM>, which can in turn communicate with video memory. In addition to a monitor, other peripheral output devices may be coupled via the output interface <NUM>, such as speakers and/or printing devices.

The network node <NUM> can operate in a networked or distributed environment using logical connections to one or more other computing systems, such as a remote server <NUM>, which can in turn have media capabilities different from the network node <NUM>. The remote server <NUM> can be a personal computer, a server, a router, a network PC, a peer node in the VCN <NUM> or another common network node, and/or any other remote media consumption or transmission device and can include any or all of the elements described above relative to the network node <NUM>.

Interface circuitry <NUM> of the network node <NUM> may be configured for interfacing the network node <NUM> to a local area network (LAN) or a wide area network (WAN) and is labeled in the drawing as a network interface. The interface circuitry <NUM> may be used to communicatively couple the network node <NUM> to one or more other network nodes <NUM> in the VCN <NUM> and/or to one or more network nodes <NUM> in the HCN <NUM>. Of course, such connections may be indirect and involve intermediary nodes/connections.

When used in a LAN networking environment, the interface circuitry <NUM> includes a LAN network interface or adapter. When used in a WAN networking environment, the interface circuitry <NUM> includes a communications component, such as a modem, or other means for establishing communications over a WAN, such as the Internet. Additionally, or alternatively, communications component, such as a modem, which can be internal or external, can be connected to the system bus <NUM> through the user input interface at input <NUM> and/or other appropriate mechanism.

In a networked environment, program modules depicted relative to the network node <NUM>, or portions thereof, can be stored in a remote memory storage device. It should be noted that the network connections shown and described are exemplary and other means of establishing a communications link between nodes can be used.

Using <FIG> for example reference, a network node <NUM> in a VCN <NUM> includes interface circuitry <NUM> and processing circuitry <NUM>. The processing circuitry <NUM> is configured to determine that usage information for offloaded traffic shall be reported back to an HCN <NUM>. The offloaded traffic is user traffic of a communication session that is offloaded to a DN <NUM> at the VCN <NUM> rather than routed back to the HCN <NUM>. The communication session involves a communication device <NUM> that is associated with the HCN <NUM>. The processing circuitry <NUM> is further configured to obtain addressing information for reporting the usage information back to the HCN <NUM>, and report, via the network interface <NUM>, the usage information for the offloaded traffic back to the HCN <NUM> in accordance with the addressing information, for charging of the communication session in the HCN <NUM>.

In at least one embodiment, or in an example operating scenario, the charging is online charging, and the processing circuitry <NUM> is configured to request a quota that grants a certain amount of service consumption for the communication session, and monitor service consumption for the communication session against the quota.

The VCN <NUM> and the HCN <NUM> are 5GC networks in one or more embodiments. Further, in one or more embodiments, the communication session is a PDU session providing a logical connection between the communication device <NUM> and the DN <NUM>.

In one or more embodiments, the network node <NUM> is operative as a V-SMF <NUM> with respect to the communication session and the processing circuitry <NUM> is configured to report the usage information to a network node <NUM> in the HCN <NUM> that is operative as an H-SMF <NUM> or operative as an H-CHF <NUM> in the HCN <NUM>. Further, in at least one such embodiment, the processing circuitry <NUM> is configured to obtain the addressing information from one of: another network node <NUM> in the VCN <NUM> that is operative as a V-NRF <NUM>, a network node <NUM> in the HCN <NUM> that is operative as an H-NRF <NUM>, another network node <NUM> in the VCN <NUM> that is operative as a V-PCF <NUM>, or local configuration information relevant to a SUPI associated with the communication device <NUM>.

In at least one embodiment where the network node <NUM> in the VCN <NUM> that reports the usage information back to the HCN <NUM> is the V-SMF <NUM>, the processing circuitry <NUM> is configured to obtain PCC rules from a V-PCF <NUM> in the VCN <NUM>. Correspondingly, the processing circuitry <NUM> uses the PCC rules in supporting the communication session, wherein the PCC rules are agreed between PCC rules applicable to the communication session in the VCN <NUM> and PCC rules applicable to the communication session in the HCN <NUM>.

In at least one such embodiment, the processing circuitry <NUM> is configured to determine that the DN <NUM> has a DNAI that was indicated in policy information provided to the V-SMF <NUM> by a V-PCF <NUM> in the VCN <NUM>.

Further, in at least one embodiment, the processing circuitry <NUM> is configured to obtain an address for communicating with a network node <NUM> in the HCN <NUM> that is operative as an H-CHF <NUM> that performs charging operations in the HCN <NUM> for the communication session, according to the usage information reported for the offloaded traffic. The processing circuitry <NUM> in such embodiments is configured to output the usage information towards the H-CHF <NUM> via the network interface <NUM>.

In embodiments where the network node <NUM> is operative as the V-SMF <NUM>, the processing circuitry <NUM> may be further configured to maintain interfaces <NUM>, <NUM> towards the H-CHF <NUM> in the HCN <NUM> and a V-CHF <NUM> in the VCN <NUM>. The processing circuitry <NUM> is configured to use the two interfaces for obtaining service authorizations for the communication session from the V-CHF <NUM> and the H-CHF <NUM>, and for reporting the usage information to the V-CHF <NUM> and the H-CHF <NUM>. Usage information reported to the H-CHF <NUM> comprises usage information for user traffic of the communication session that is offloaded at the VCN <NUM>, and for which reporting to the HCN <NUM> is indicated.

Responses from H-CHF <NUM> to the V-SMF <NUM> may be hashed and the processing circuitry <NUM> or other circuitry within the network node is configured to process the hashed responses via a corresponding hash function or hash table, to recover the original responses.

In one or more other embodiments, the network node <NUM> that reports usage information back to the HCN <NUM> is operative as a V-CHF <NUM> in the VCN <NUM> with respect to the communication session. For reporting the usage information in such embodiments, the processing circuitry <NUM> is configured to report the usage information to a network node <NUM> in the HCN <NUM> that is operative as an H-CHF <NUM> in the HCN <NUM>. In at least one such embodiment, the processing circuitry <NUM> is configured to maintain an interface <NUM> with the H-CHF <NUM>. Here, and elsewhere, the processing circuitry <NUM> "maintaining" or "providing" an interface involves communicative coupling of the involved nodes/entities and denotes the processing circuitry <NUM> performing processing and signaling for communication with the other involved entity/node.

Further, in at least one such embodiment, the processing circuitry <NUM> is configured to obtain the addressing information from another network node <NUM> in the VCN <NUM> that is operative in the VCN <NUM> as a V-NRF <NUM> or operative as a V-SMF <NUM>, with respect to providing session management for the communication session. Further, in at least one such embodiment, the processing circuitry <NUM> is configured to perform service authorization with respect to the communication session at least in part according to authorization decisions made by the H-CHF <NUM> in the HCN <NUM>. Still further, in at least one such embodiment the processing circuitry <NUM> is configured to generate charging information for the communication session in joint dependence on PCC rules used by the VCN <NUM> and PCC rules used by the HCN <NUM>.

In one or more embodiments, the H-CHF <NUM> in the HCN <NUM> provides a return response or responses that include a transaction Id that may be used to confirm that the reported units indicated in the reported usage information have been stored by the H-CHF <NUM>. The transaction Id can be linked or contain the used units and the communication session it relates to, and the transaction Id can then be stored in the V-CHF <NUM> for later accounting purposes. In cases where a V-SMF <NUM> in the VCN <NUM> reports the usage information back to the HCN <NUM>, the processing circuitry <NUM> in the network node <NUM> operating as the V-SMF <NUM> is configured to provide the responses/transaction Id to the involved V-CHF <NUM> in the VCN <NUM>, for storage. In cases where a V-CHF <NUM> in the VCN <NUM> reports the usage information back to the HCN <NUM>, the processing circuitry <NUM> in the network node <NUM> operating as the V-CHF <NUM> is configured to receive the responses/transaction Id and perform the storage, accordingly.

<FIG> illustrates one embodiment of a method <NUM> of operation by a network node <NUM> in a VCN <NUM>. The method <NUM> includes determining (Block <NUM>) that usage information for offloaded traffic shall be reported back to an HCN <NUM>, the offloaded traffic being user traffic of a communication session that is offloaded to a DN <NUM> at the VCN <NUM> rather than routed back to the HCN <NUM>, and the communication session involving a communication device <NUM> that is associated with the HCN <NUM>. The method <NUM> further includes obtaining (Block <NUM>) addressing information for reporting the usage information back to the HCN <NUM>, and reporting (Block <NUM>) the usage information for the offloaded traffic back to the HCN <NUM> in accordance with the addressing information, for charging of the communication session in the HCN <NUM>. The addressing information indicates, for example, a network address or other information for contacting the network node (<NUM>) in the HCN <NUM> that is the target for the VCN's reporting and indicates the type of network function implemented by the targeted network node <NUM>, e.g., that the targeted network node <NUM> operates as an SMF or a CHF in the HCN <NUM>.

In an example scenario, the charging is online charging, and the method <NUM> further comprises the network node <NUM> requesting a quota that grants a certain amount of service consumption for the communication session, and monitoring service consumption for the communication session against the quota.

In one or more embodiments of carrying out the method <NUM>, the VCN <NUM> and HCN <NUM> are 5GC networks. Further, in one or more embodiments, the communication session is a PDU session providing a logical connection between the communication device <NUM> and the DN <NUM>.

In one or more embodiments, the network node <NUM> that performs the method <NUM> is operative as a V-SMF <NUM> in the VCN <NUM> with respect to the communication session. Reporting (Block <NUM>) the usage information comprises the V-SMF <NUM> reporting the usage information to a network node <NUM> in the HCN <NUM> that is operative as an H-SMF <NUM> or operative as an H-CHF <NUM> in the HCN <NUM>. In at least one such embodiment, obtaining (Block <NUM>) the addressing information comprises obtaining the addressing information from one of: another network node <NUM> in the VCN <NUM> that is operative as a V-NRF <NUM>, a network node <NUM> in the HCN <NUM> that is operative as an H-NRF <NUM>, another network node <NUM> in the VCN <NUM> that is operative as a V-PCF <NUM>, or local configuration information relevant to a SUPI associated with the communication device <NUM>.

Further, in at least one embodiment of the V-SMF <NUM> performing the method <NUM>, the V-SMF <NUM> obtains PCC rules from a V-PCF <NUM> in the VCN <NUM>, for use in supporting the communication session. Advantageously, the PCC rules are agreed between PCC rules applicable to the communication session in the VCN <NUM> and PCC rules applicable to the communication session in the HCN <NUM>.

Still further, in at least one embodiment of the V-SMF <NUM> performing the method <NUM>, determining (Block <NUM>) that the usage information shall be reported back to the HCN <NUM> comprises the V-SMF <NUM> determining that the DN <NUM> has a DNAI indicated in policy information provided to the V-SMF <NUM> by a V-PCF <NUM> in the VCN <NUM>. Still further, in one or more embodiments, obtaining (Block <NUM>) the addressing information comprises the V-SMF <NUM> obtaining an address for communicating with a network node <NUM> in the HCN <NUM> that is operative as an H-CHF <NUM> that performs charging operations in the HCN <NUM> for the communication session according to the usage information reported for the offloaded traffic. Reporting (Block <NUM>) the usage information comprises the V-SMF <NUM> reporting the usage information to the H-CHF <NUM>.

For one or more such embodiments of the method <NUM>, the method <NUM> includes the V-SMF <NUM> maintaining interfaces <NUM>, <NUM> towards the H-CHF <NUM> in the HCN <NUM> and a V-CHF <NUM> in the VCN <NUM>. The V-SMF <NUM> uses the interfaces <NUM>, <NUM> for obtaining service authorizations for the communication session from the V-CHF <NUM> and the H-CHF <NUM>, and for reporting the usage information to the V-CHF <NUM> and the H-CHF <NUM>.

In one or more other embodiments, the network node <NUM> in the VCN <NUM> that performs the method <NUM> is operative as a V-CHF <NUM> with respect to the communication session. Here, reporting (Block <NUM>) the usage information comprises the V-CHF <NUM> reporting the usage information to a network node <NUM> in the HCN <NUM> that is operative as an H-CHF <NUM> in the HCN <NUM>. For reporting (Block <NUM>) the usage information includes, for example, the V-CHF (<NUM>) maintains an interface <NUM> with the H-CHF <NUM>.

Further, one or more embodiments of the method <NUM> includes the V-CHF <NUM> obtaining the addressing information from another network node <NUM> that is operative in the VCN <NUM> as a V-NRF <NUM> or operative as a V-SMF <NUM>, with respect to providing session management for the communication session. The V-CHF <NUM> carrying out the method <NUM> may also include the V-CHF <NUM> performing service authorization with respect to the communication session at least in part according to authorization decisions made by the H-CHF <NUM> in the HCN <NUM>. Additionally, in at least one embodiment where the V-CHF <NUM> carries out the method <NUM>, the method <NUM> includes the V-CHF <NUM> generating charging information for the communication session in joint dependence on PCC rules used by the VCN <NUM> and PCC rules used by the HCN <NUM>.

As noted above, in one or more embodiments, the H-CHF <NUM> in the HCN <NUM> provides a return response or responses that include a transaction Id that may be used to confirm that the reported units indicated in the reported usage information have been stored by the H-CHF <NUM>. The transaction Id can be linked or contain the used units and the communication session it relates to, and the transaction Id can then be stored in the V-CHF <NUM> for later accounting purposes. In cases where a V-SMF <NUM> in the VCN <NUM> reports the usage information back to the HCN <NUM>, the method <NUM> includes the V-SMF <NUM> providing the responses/transaction Id to the involved V-CHF <NUM> in the VCN <NUM>, for storage. In cases where a V-CHF <NUM> in the VCN <NUM> reports the usage information back to the HCN <NUM>, the method <NUM> includes the V-CHF <NUM> receiving the responses/transaction Id and performing the storage.

Regarding the above example details, it should be noted that as used in this application, terms such as "component," "display," "interface," and other similar terms are intended to refer to a computing device, either hardware, a combination of hardware and software, software, or software in execution as applied to a computing device. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computing device. As an example, both an application running on a computing device and the computing device can be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computing device and/or distributed between two or more computing devices, and/or communicatively connected modules. Further, it should be noted that as used in this application, terms such as "system user," "user," and similar terms are intended to refer to the person operating the computing device referenced above.

As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components, or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est", may be used to specify a particular item from a more general recitation.

Claim 1:
A method (<NUM>) of operation by Visited Session Management Function, V-SMF, (<NUM>) in a Visited Communication Network, VCN, (<NUM>), the method (<NUM>) comprising:
determining (<NUM>) that usage information for offloaded traffic shall be reported back to a Home Communication Network, HCN, (<NUM>), the offloaded traffic being user traffic of a communication session that is offloaded to a Data Network, DN, (<NUM>) at the VCN (<NUM>) rather than routed back to the HCN (<NUM>), and the communication session involving a communication device (<NUM>) that is associated with the HCN (<NUM>);
obtaining (<NUM>) addressing information of a Home Charging Function, H-CHF, for reporting the usage information back to the HCN (<NUM>); and
reporting (<NUM>) the usage information for the offloaded traffic back to the Home Charging Function, H-CHF, (<NUM>) in the HCN (<NUM>) in accordance with the addressing information, for charging of the communication session in the HCN (<NUM>); and
characterised in that wherein determining that the usage information shall be reported back to the HCN comprises the V-SMF (<NUM>) determining that the DN (<NUM>) has a Data Network Access Identifier, DNAI, indicated in policy information provided to the V-SMF (<NUM>) _by a Visited Policy Control Function, V-PCF, (<NUM>) in the VCN (<NUM>).