WO2022203553A1

WO2022203553A1 - Using user equipment to gather local break out network resource usage information for communication sessions

Info

Publication number: WO2022203553A1
Application number: PCT/SE2021/050267
Authority: WO
Inventors: Robert TÖRNKVIST; Peter Hedman
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-03-26
Filing date: 2021-03-26
Publication date: 2022-09-29

Abstract

A user equipment (UE) sends a local break out (LBO) access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function. The UE receives from the network function, LBO setup information that configures what network resource usage measurements and reporting the UE is to perform. The UE sets up a session with a network. The UE then performs network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information. Corresponding network functions, methods, and computer program products are disclosed.

Description

USING USER EQUIPMENT TO GATHER LOCAL BREAK OUT NETWORK RESOURCE USAGE INFORMATION FOR COMMUNICATION SESSIONS

TECHNICAL FIELD

[0001] The present disclosure relates to communications networks and gathering network resource usage information related to communication sessions.

BACKGROUND

[0002] In current public land mobile networks (PLMNs) roaming is an essential process to allow subscribers to take their user equipments UEs (e.g., smartphones, laptops, tablet computers, etc.) when travelling and using other PLMNs. The charging settlement between operators is usually based on the records generated by the subscribers’ UE activity in the visited network. These records are sometimes verified by the home network, this verification relies on that all traffic generated by the subscribers’ UE being routed to the home network. For calls this is normally the case since most calls dialed by someone abroad is to the home country, and even a lot of the data traffic may be destined to servers in the home country or international where the extra routing step may have very little impact.

[0003] A process called local break out (LBO) has been developed with allows both calls and data traffic to avoid home routing, e.g., so calls not destined to the home country or home network are not routed home and data traffic can access the Internet in the visited network instead of the home. More particularly, LBO enables the Mobile Network Operator (MNO) to break out Internet sessions into a Visited network, to provide inbound roamers with an ability to order data, which is provided directly by the visited network. LBO is a component of technology that allows mobile subscribers to, e.g., sign up to an alternative roaming provider separate from their HPLMN (Home Public Land Mobile Network). It enables inbound roamers to receive data services directly from the visited mobile network instead of tunneling back to the HPLMN. It offers lower latency experienced by the roaming device and has a lower GRX bandwidth requirement between the Home network and Visited network.

[0004] For circuit switched calls network resources can be monitored using Customized Applications for Mobile networks Enhanced Logic (CAMEL), e.g., as defined by 3GPP TS 23.078 rel. 16.0.0, independent of whether the calls are home routed or not.

[0005] When the calls or data traffic are destined to the visited country the home routing adds latency and, in some cases, cost since there can be intervening other operator networks which forward the traffic between the visited and home networks and require associated payment for the service.

[0006] For phone calls, an issue which arises with use of home routing is that most calls are moving away from circuit switched calls to voice over LTE (VoLTE) and IP multimedia service (IMS).

[0007] For data traffic, an issue which arises with use of home routing is that with Internet of Things (IoT) and high speed data the quantity of traffic is growing but the monetary amount that can be charged for each byte is becoming smaller, which incentivizes making the operations for routing the traffic more efficient. Similar efficiency improvements are needed for use cases involving edge computing which relies on LBO to ensure low latency communications. It is becoming increasingly inefficient to route the traffic to the home network for the purpose of being able to ensure that the charges by the visited network are correct.

[0008] While using the LBO option avoids at least some of this inefficiency, LBO necessitates that the home operator trust the information from the visited operator since the home operator will lack information indicating how the user has used resources in the visited network. The CAMEL operations can improve efficiency, however they are not supported in 5GC and would require completion of much testing and development of new agreements to expand to 5GC. CAMEL today is also mostly used for prepaid subscriptions since the cost of maintenance and signaling is not negligible.

SUMMARY

[0009] As will be explained in further detail below, some embodiments of the present disclosure are directed to a method by a user equipment (UE) that includes sending a local break out (LBO) access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function. The method receives from the network function, LBO setup information that configures what network resource usage measurements and reporting the UE is to perform. The method sets up a session with a network. The method then performs network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information.

[0010] Some other related embodiments are directed to a method by a network function that includes receiving a LBO access request containing an indication of network resource usage reporting capabilities of a UE. The method generates LBO setup information that configures what network resource usage measurements and reporting the UE is to perform, and sends the LBO setup information to the UE. The network function may be a Charging UE Setup Function (CTTSF).

[0011] Some other related embodiments are directed to a method by a network function that includes obtaining EE LBO information for a EE identity and a network identified by at least one of a data network name (DNN) and a single network slice selection assistance information (S-NSSAI). The method determines based on the EE LBO information whether the EE identity is allowed to use LBO for network resource usage measurements and reporting for the network. The network function may be an Access and Mobility Management Function (AMF) or a Charging Function (CHF).

[0012] Another corresponding embodiment is directed to a EE that includes at least one processor in at least one memory coupled to the at least one processor and storing computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations. The operations are configured to send a LBO access request containing an indication of network resource usage reporting capabilities of the EE, toward a network function. The operations receive, from the network function, LBO setup information that configures what network resource usage measurements and reporting the EE is to perform. The operations setup a session with a network. The operations then perform network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information.

[0013] Another corresponding embodiment is directed to a network function that includes at least one processor in at least one memory coupled to the at least one processor and storing computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations. The operations are configured to receive a LBO access request containing an indication of network resource usage reporting capabilities of a EE. The operations generate LBO setup information that configures what network resource usage measurements and reporting the EE is to perform, and send the LBO setup information to the EE. The network function may be a CUSF

[0014] Another corresponding embodiment is directed to a network function that includes at least one processor in at least one memory coupled to the at least one processor and storing computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations. The operations are configured to obtain EE LBO information for a EE identity and a network identified by at least one of a DNN and a S-NSSAI. The network function may be an Access and Mobility Management Function (AMF) or a Charging Function (CHF). [0015] Potential advantages that may be provided by one or more of these embodiments is that they enable a home operator to setup and get information of usage of a UE using LBO while roaming. The home operator can validate the information coming from a visited network of usage without requiring any extra testing or special agreements to exist between the home operator and visiting operator. With a large of number of services available in 5G, enabling more trusted use of LBO can result in more effective utilization of network resources for communication sessions and increased availability and responsiveness of services for end subscribers. As a result, these embodiments may cause increased revenue streams for the network service providers.

[0016] It is noted that aspects described with respect to one embodiment may be incorporated in different embodiments although not specifically described relative thereto. That is, all embodiments and/or features of any embodiments can be combined in any way and/or combination. Moreover, other methods, network functions, and computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such other methods, network functions, and computer program products be included within this description and protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS [0017] Aspects of the present disclosure are illustrated by way of example and are not limited by the accompanying drawings. In the drawings:

[0018] Figure 1 illustrates a system block diagram of various network functions of a Visited Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) which are configured to operate in accordance with various embodiments of the present disclosure;

[0019] Figure 2 illustrates a data flow diagram for communications between a UE, CUSF, and CHF for obtaining LBO setup information which is used to configure network resource usage measurements for a session and reporting of the network resource usage measurements in accordance with some embodiments of the present disclosure;

[0020] Figure 3 illustrates a data flow diagram for communications between a UE, CUSF, CHF, and Unified Data Repository (UDR) or User Data Management (UDM) for obtaining LBO setup information which is used to configure network resource usage measurements for a session and reporting of the network resource usage measurements in accordance with some embodiments of the present disclosure; [0021] Figure 4 illustrates components of a UE which are configured to operate according to some embodiments of the present disclosure;

[0022] Figure 5 illustrates a components of a network function which are configured to operate according to some embodiments of the present disclosure;

[0023] Figure 6 is a flowchart illustrating operations that can be performed by a UE according to some embodiments of the present disclosure;

[0024] Figure 7 is a flowchart illustrating operations that can be performed by a network function that receives a LBO access request containing an indication of network resource usage reporting capabilities of a UE according to some embodiments of the present disclosure; and

[0025] Figure 8 is a flowchart illustrating operations that can be performed by a network function that obtains UE LBO information for a UE identity and a network identified by DNN and/or a S-NSSAI according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

[0026] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of various present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0027] Various embodiments of the present disclosure are directed to operations by which a home operator performs setup of measurement(s) to be performed by a UE relating to the UE's network usage. The setup may configure what measurement(s) the UE will make and report, and how the UE report will depend on the UE capacity and capability. In one embodiment, if the UE doesn’t support this setup the operator can refuse to allow the UE to operationally use local break-out.

[0028] In a relatively simpler operational setup, the UE reports to a specific address how much resources were used on which network per defined time unit, e.g., hour, or more advanced rules or information can be configured by the network to the UE as to what the UE is to measure and report, which avoids requiring the UE to be aware when LBO is used for a Session, which may be a protocol data unit (PDU) session. [0029] Various potential advantages that may be provided by one or more of the embodiments disclosed herein are now explained. The operations may allow the home operator to validate the information coming from the visited network of usage without requiring any extra testing or special agreements to exist between the home operator and visiting operator. It is anticipated that in the future most UEs will have the possibility to use a data connection which hasn't before been available. For example, very small, e.g., operationally constrained, Internet of Things (IOT) devices will be able to use at least NB- IoT type of communication. It is further anticipated that most IOT devices will to some extent also measure the usage, even if the measurement is performed at a very high level of tracking of resource utilization (e.g., low granularity of utilization tracking). A relatively small amount of network traffic would be used by the UE or other device to send its usage to the Home Public Land Mobile Network (HPLMN) when performing LBO in the Visited Public Land Mobile Network (VPLMN). These operations may need extra storage capacity and energy consumption by the UE. The storage requirement could be adapted to capabilities of the UE, such as where UEs with relatively small available storage space being configured to gather less measurement metadata regarding the network resource usage and where other UEs with relatively greater available storage space can be configured to gather greater measurement metadata regarding network resource usage.

[0030] Although some example systems and operations are discussed in the context of PLMNs, these and other embodiments can be used with private networks, such as for 3GPP Non-Public Networks. As used herein a UE can be any type of electronic communication device which may or may not be configured to be directly operated by a user, and can include without limitation a mobile phone, tablet computer, or residential appliance (e.g., smart thermostat, refrigerator, utility meter, etc.).

[0031] Figure 1 shows an architecture that includes various network functions (NFs) and reference points connecting NFs, of a VPLMN and a HPLMN, which are configured to operate in accordance with various embodiments of the present disclosure.

[0032] Referring to Figure 1, a UE is connected to either a Radio Access Network (RAN) or Access Network (AN) as well as an Access and Mobility Function (AMF). The RAN may correspond to a base station or other radio access node using radio access technology (RAT). The AN may be a general base station including 3GPP and/or non-3GPP access, e.g., Wi-Fi. In the simplified example of Figure 1, there are several NextGen core NFs in the VPLMN, namely, (1) the AMF, (2) a Session Management Function (SMF), (3) a User Plane Function (UPF), and (4) a visited Charging Function (vCHF). Further in the simplified example of Figure 1, NFs of the HPLMN can include a Charging UE Setup Function (CUSF) and a home Charging Function (hCHF).

[0033] The UE performs data connection and transmissions, and monitors resource usage and reports usage to the CHF. The AMF provides UE-based authentication, authorization, mobility management, etc, and sets up data connectivity, creates charging request for data connectivity, and monitors resource usage and sets reporting triggers in the user plane. A UE using multiple access technologies may be connected to a single AMF because the AMF is independent of the access technologies. SMF is responsible for session management including, setting up data connectivity, creating charging request for data connectivity, and monitoring the usage and setting reporting triggers in the user plane, and allocates IP addresses to UEs. The SMF also selects and controls the UPF for data transfer. If a UE has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per session. The UPF handles and monitors actual data transmissions from the UE. An access function (AF) can provide information on the packet flow to a policy control function (PCF) responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies about mobility and session management to make AMF and SMF operate properly. The vCHF collects information for interconnection charges for the UE's resource utilization of the visited network. The hCHF collects information for interconnection verification, and collects information that may be used for rating and billing. The CUSF sets up UE network resource usage monitoring and reporting in the UE.

[0034] Figure 2 illustrates a data flow diagram for communications between a UE 100, CUSF 102, and CHF 104 for obtaining LBO setup information which is used to configure network resource usage measurements for a session, such as a PDU session, and reporting of the network resource usage measurements in accordance with some embodiments of the present disclosure.

[0035] Referring to Figure 2, the UE 100 sends 200 a LBO access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function (NF) which is a CUSF 102 in the example context of Figure 2. The NF (CUSF 102) sends 202 to the UE 100, LBO setup information that configures what network resource usage measurements and reporting the UE 100 is to perform. As noted in communication 202, the LBO setup information may, for example, instruct the UE of the destination address to use for reporting and the frequency of the reporting. The UE 100 responsively performs 204 network resource usage measurements and reporting of the network resource usage measurements, as configured by the LBO setup information. The UE reporting of network resource usage measurements can correspond to the illustrated charging data requests that is sent to the CHF 104.

[0036] Figure 3 illustrates a data flow diagram for communications between a UE 100, CUSF 102, CHF 104, and Unified Data Repository (UDR) or User Data Management (UDM) 106 for obtaining LBO setup information which is used to configure network resource usage measurements for a session, such as a PDU session, and reporting of the network resource usage measurements in accordance with some embodiments of the present disclosure.

[0037] Referring to Figure 3, a UE 100 sends 300 a LBO access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function which is illustrated as a CUSF 102. The UE's LBO access request indicates a preference for using LBO while roaming, e.g., either when the UE is roaming or at signing up to the service. The UE's network resource usage reporting capabilities may be indicated by embedding in the LBO access request an indication of at least one of the following: storage capacity at the UE 100 for storing network resource usage measurements by the UE 100 for reporting; time accuracy of the UE 100 when performing network resource usage measurements for reporting; location determination capability of the UE 100 when performing network resource usage measurements for reporting; and indication of a defined type characteristic of the UE 100. Alternatively or additionally, the UE's network resource usage reporting capabilities may be indicated by embedding in the LBO access request an indication of at least one of: an indication of which network the UE is registered to; a combination of data network name (DNN) and single network slice selection assistance information (S-NSSAI) associated with a HPLMN or a serving PLMN that the UE wants to use for communications; and a Subscription Permanent Identifier (SUPI) of the UE and a Permanent Equipment Identifier (PEI) of the UE.

[0038] The CUSF 102 receives 300 the LBO access request containing the indication of network resource usage reporting capabilities of the UE 100, and responsively generates 301 LBO setup information that configures what network resource usage measurements and reporting the UE 100 is to perform. The CUSF 102 can determine the capability of the UE and whether, based on the UEs capability, it is allowed to use LBO.

[0039] When generating 301 the LBO setup information, the CUSF 102 can determine whether the UE 100 is allowed for LBO based on content of the LBO access request. When the UE 100 is determined to be allowed for LBO, the CUSF 102 can initiate recordation 302 in the unified data repository (UDR) 106 or in the unified data management (UDM) 106 that an identity of the UE 100 will use LBO for network resource usage measurements and reporting for a network identified by at least one of a data network name (DNN) and a single network slice selection assistance information (S-NSSAI) which the network function determines based on content of the LBO access request. For example, LBO can be allowed for a specific DNN, for a specific S NSSAI (in which case LBO will be enabled for all DNNs using the S-NSSAI), for one or more DNNs with a specific S-NSSAI, or for all S- NSSAIs and DNNs. Moreover, LBO can be enabled for one or more specific networks (e.g., registered PLMNs), in which case the UE reports its location and a specific registered PLMN, so the HPLMN can operate to differentiate for which network to enable LBO. The UDR 106 or UDM 106 confirms 304 the recordation that the UE 100 is LBO allowed for a requested DNN.

[0040] Moreover, the operation for generating 301 the LBO setup information by the CUSF 102 may include generating the LBO setup information to control at least one of the following: what destination address is indicated in reports of the network resource usage measurements sent by the UE 100; frequency at which reports of the network resource usage measurements are sent by the UE 100; what type of event triggers new measurements of the network resource usage by the UE 100; and what combination of a S-NSSAI and DNN for which the UE 100 is to perform the network resource usage measurements and reporting. [0041] Alternatively or additionally, the operation for generating 301 the LBO setup information by the CUSF 102 may include identifying the type of event that will trigger new measurements of the network resource usage by the UE 100, as at least one of the following: network change by the UE 100 for ongoing communications of a session, such as a PDU session; location change by the UE 100 during ongoing communications of a session; and radio access technology (RAT) change by the UE 100 for ongoing communications of a session.

[0042] The CUSF 102 sends 306 the LBO setup information to the UE 100.

[0043] The UE 100 receives 306, from the CUSF 102, the LBO setup information that configures what network resource usage measurements and reporting the UE 100 is to perform. The UE 100 sets up 308 a session with a network. The UE 100 performs 308 network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information.

[0044] In some embodiments, the UE connects to the Internet or other network using LBO and service monitoring the usage as requested. When the UE 100 has determined that a reporting trigger event has occurred, which can be configured by the LBO setup information from the CUSF 102, the UE 100 is triggered to send 310 a report to the CHF 104, e.g., a hCHF. The report may use the existing session in the internet connection or by setting up a separate session. A separate session could be setup for reporting using a home routed data connection, and/or the reporting could include sending a Short Messaging Service (SMS) or and/or using use another type of communications, e.g. Control Plane CIoT 5GS Optimisation. [0045] The operation for performing 308 the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, may include controlling the following. The UE 100 may control at least one of the following responsive to the LBO setup information: what destination address is indicated in reports of the network resource usage measurements sent by the UE; frequency at which reports of the network resource usage measurements are sent by the UE; what type of event triggers new measurements of the network resource usage by the UE; and what combination of a S-NSSAI, associated with a HPLMN or a serving PLMN, and a DNN for which the UE performs the network resource usage measurements and reporting.

[0046] In a further embodiment, the UE 100 may respond to the LBO setup information by controlling what type of event triggers new measurements of the network resource usage by the UE 100, wherein the type of event comprises at least one of: network change by the UE 100 for ongoing communications of the session; location change by the UE 100 during ongoing communications of the session; and radio access technology change by the UE 100 for ongoing communications of the session.

[0047] The UE 100 may measure a defined type of network resource usage that is indicated by the LBO setup information. The UE may send a report of the network resource usage measurements for the session to a home charging function (hCHF) using the session or using another session that is setup with the network. Alternatively or additionally, the UE 100 may send reports of the network resource usage measurements for the session to a hCHF using short messaging service (SMS) communications and/or using control plate communications. In the example embodiment of Figure 3, the UE 100 sends the report using a charging data request 310 to the CHF 104. The CHF 104 records the reported resource usage, generates a charging data record (CDR), and can send an acknowledgment of receipt using a charging data response 312 sent to the UE 100.

[0048] Although various operations of the UE and the network function have been described in the context of Figures 2 and 3, these and other embodiments are not limited thereto. Accordingly, a more general description of UE and network function operations is now be made with reference to Figures 6 and 7 without any limitation to embodiments described in the context of Figures 2 and 3. Figure 6 is a flowchart illustrating operations that can be performed by a UE according to some embodiments of the present disclosure. Figure 7 is a flowchart illustrating operations that can be performed by a network function that receives a LBO access request containing an indication of network resource usage reporting capabilities of a UE according to some embodiments of the present disclosure. [0049] In the figures used herein, although various arrows are used to convey example communication directions, the illustrated arrows are not limiting, and the communications can occur in the opposite directions to those illustrated and often occur in both directions. [0050] Referring initially to Figure 6, the UE sends 600 a LBO access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function. The UE receives 602, from the network function, LBO setup information that configures what network resource usage measurements and reporting the UE is to perform. The UE sets up 604 a session with a network. The UE then performs 606 network resource usage measurements for the session and reporting of the network resource usage measurements, where the measurements and reporting are performed according to the as configured by the LBO setup information.

[0051] The network function may be a CUSF or other NF.

[0052] The UE operation to send 600 the LBO access request may include embedding in the LBO access request an indication of at least one of the following: storage capacity at the UE for storing network resource usage measurements by the UE for reporting; time accuracy of the UE when performing network resource usage measurements for reporting; location determination capability of the UE when performing network resource usage measurements for reporting; and indication of a defined type characteristic of the UE.

[0053] Alternatively or additionally the UE operation to send 600 LBO access request may include embedding in the LBO access request an indication of at least one of: a combination of DNN and S-NSSAI that the UE wants to use for communications; and a SUPI of the UE and a PEI of the UE.

[0054] The UE may perform 606 the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, by operations that include controlling at least one of the following responsive to the LBO setup information: what destination address is indicated in reports of the network resource usage measurements sent by the UE; frequency at which reports of the network resource usage measurements are sent by the UE; what type of event triggers new measurements of the network resource usage by the UE; and what combination of a S- NSSAI, associated with a HPLMN or a serving PLMN, and a DNN for which the UE performs the network resource usage measurements and reporting.

[0055] The UE may control at least one of the following responsive to the LBO setup information: what type of event triggers new measurements of the network resource usage by the UE, wherein the type of event comprises at least one of: network change by the UE for ongoing communications of the session; location change by the UE during ongoing communications of the session; and radio access technology change by the UE for ongoing communications of the session.

[0056] The UE may perform 606 the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, by operations that include measuring a defined type of network resource usage that is indicated by the LBO setup information.

[0057] The UE may send a report of the network resource usage measurements for the session to a hCHF using the session or using another session that is setup with the network. Alternatively or additionally, the UE may send reports of the network resource usage measurements for the session to a home charging function, hCHF, using short messaging service, SMS, communications and/or using control plate communications.

[0058] The corresponding NF operations are now described in the context of Figure 7. Referring now to Figure 7, the NF receives 700 a LBO access request containing an indication of network resource usage reporting capabilities of a UE. The NF generates 702 LBO setup information that configures what network resource usage measurements and reporting the UE is to perform. The NF sends 704 the LBO setup information to the UE. [0059] The NF may be a CUSF or other network function.

[0060] The NF operation to generate 702 the LBO setup information may include generating the LBO setup information based on an indication embedded in the LBO access request of at least one of the following: storage capacity at the UE for storing network resource usage measurements by the UE for reporting; time accuracy of the UE when performing network resource usage measurements for reporting; location determination capability of the UE when performing network resource usage measurements for reporting; and indication of a defined type characteristic of the UE.

[0061] Alternatively or additionally, the NF operation to generate 702 the LBO setup information may include generating the LBO setup information based on an indication embedded in the LBO access request of at least one of: a combination of a DNN and a S- NSSAI that the UE wants to use for communications; and a SUPI of the UE and a PEI of the UE.

[0062] The NF operation to generate 702 the LBO setup information may include generating the LBO setup information to control at least one of the following: what destination address is indicated in reports of the network resource usage measurements sent by the UE; frequency at which reports of the network resource usage measurements are sent by the UE; what type of event triggers new measurements of the network resource usage by the UE; and what combination of a S-NSSAI and DNN for which the UE is to perform the network resource usage measurements and reporting.

[0063] Alternatively or additionally, the NF operation to generate 702 the LBO setup information may include identifying the type of event that will trigger new measurements of the network resource usage by the UE, as at least one of the following: network change by the UE for ongoing communications of a session; location change by the UE during ongoing communications of a session; and radio access technology change by the UE for ongoing communications of a session.

[0064] The NF operation to generate 702 the LBO setup information may include determining whether the UE is allowed for LBO based on content of the LBO access request. When the UE is determined to be allowed for LBO, the NF can initiate recordation in a UDR or in a UDM that an identity of the UE is authorized to use LBO roaming or is preferred to use LBO roaming, for network resource usage measurements and reporting for a network identified by at least one of a DNN and a S-NSSAI which the network function determines based on content of the LBO access request.

[0065] Some alternative embodiments are now described in the context of approaches that can store the UE LBO information in the UDM or the UDR, and from where the AMF retrieves the information. These approaches may still require the UE to interact with the CUSF or CHF in this case to set up the monitoring. The UE can therefore need the CHF to have been correspondingly configured beforehand.

[0066] The CHF may retrieve information on the frequency of which the reports are expected from the CUSF and may in the case reports are missing instruct the CUSF to bar the UE from using local break-out if the reporting is failing.

[0067] The CUSF may provide information to the UE for which DNN and S-NSSAI combinations the UE are to report. If the information is provided to the UE then UE reports for the Sessions with the indicated Single Network Slice Selection Assistance Information (S- NSSAI), DNNS or S-NSSAI and DNN. The HPLMN would then also configure the UDM to indicate that LBO is allowed for the same S-NSSAI and DNN combination to the roamed to PLMN i.e. as per TS 23.502 [1] "Table 5.2.3.3.1-1: UE Subscription data types", the "LBO Roaming Information" is set as allowed for the relevant S-NSSAI and DNN combinations (set as bold in below table):

[0068] As per current architecture and procedures, the AMF gets the SMF Selection Subscription data using the Nudm SubscriberDataManagement service towards the UDM, e.g., when the UE registers to the network (see TS 23.502 [1] clause 4.2.2.2.2). The AMF selects an AMF as per factors described in clause 6.3.2 of TS 23.501 [2] including the above "LBO Roaming Information" and other factors like UE location and operator policies. Therefore, these embodiments do not require any further impacts to serving network (e.g. visited PLMN during roaming).

[0069] As stated above, the HPLMN would then also configure the UDM to indicate that LBO is allowed for the same S-NSSAI and DNN combination to the roamed to PLMN. The HPLMN would do this configuration for the specific UE, i.e., for the Subscription Permanent Identifier (SUPI) and Permanent Equipment Identifier (PEI) combination. When a new SUPI and PEI combination is registered the HPLMN determines how to set the "LBO Roaming Information" based on ME capability and HPLMN policies. To ensure that the HPLMN only enables LBO for UEs that have requested it and that are capable of performing the monitoring and reporting such as illustrated in Figure 3, the UE also in operation 300 of Figure 3 can indicate its SUPI and PEI. The HPLMN is then configuring the UDM/UDR such that LBO is allowed for the PEI and SUPI combination, and UDM checks the registered SUPI and PEI before determining the values of the "LBO Roaming Information".

[0070] Note the AMF is already providing the SUPI to the UDM, and is also assumed to provide the PEI as stated in TS 23.502 [2]:

[0071] "If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm UECM Regi strati on in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association."

[0072] Operations that may be a less optimal option (i.e. mainly described here for completeness as it impacts the AMF in the VPLMN) to enable LBO in a VPLMN would be to add a new value in the UDM subscription data sent to the AMF, e.g. "LBO allowed if data reporting is supported by the UE". If UDM has set the new value, the AMF checks such that the UE indicates support for data reporting capability to the AMF (e.g. a new capability in the UE Mobility Management (MM) Core Network Capability, see TS 23.501 [2] clause 5.4.4a), and if UE supports data reporting the AMF enables LBO for the DNN and S-NSSAIs as per the LBO Roaming Information.

[0073] Figure 8 is a flowchart illustrating corresponding operations that can be performed by a network function that obtains UE LBO information for a UE identity and a network identified by DNN and/or a S-NSSAI according to some embodiments of the present disclosure.

[0074] Referring to Figure 8, the NF obtained 800 UE LBO information for a UE identity and a network identified by at least one of a DNN and a S-NSSAI. The NF determines 802 based on the UE LBO information whether the UE identity is allowed to use LBO for network resource usage measurements and reporting for the network.

[0075] The NF may obtain 800 the UE LBO information by operations that include querying a UDR or a UDM to obtain the UE LBO information using the UE identity and the network identified by at least one of the DNN and the S-NSSAI.

[0076] The NF may determine 802 whether the UE identity is allowed to use LBO based on LBO roaming information contained in the response to the query from the UDR or the UDM.

[0077] The NF may be an AMF or a CHF.

[0078] The NF may instruct a CUSF to bar the UE from using LBO to access the network responsive to determining that the UE identity is not allowed to use LBO for network resource usage measurements and reporting for the network. [0079] The UE LBO information for the UE identity may be obtained 800 as content of UDM subscription data received by the NF.

[0080] The EE LBO information for the EE identity may indicate LBO reporting is allowed if the UE supports LBO reporting to the network function. The operations can then include the UE sending to the AMF an indication that the UE supports LBO reporting to the network function.

[0081] Figure 4 illustrates components of a UE 100 which are configured to operate according to some embodiments of the present disclosure.

[0082] Referring to Figure 4, can include one or more transceivers 430 (referred to as "transceiver" for brevity), one or more processors 410 (referred to as "processor" for brevity), and one or more memories 420 (referred to as "memory" for brevity) containing program code 522.

[0083] The transceiver 430 may be configured to communicate according to one or more proprietary and/or industry standardized wireless communication protocols, e.g.,

WiFi, 3GPP 4G, 5G (NR), etc. The processor 410 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor 410 is configured to execute program code 422 in the memory 420, described below as a computer readable medium, to perform some or all of the operations and methods that are described above for a UE in accordance with one or more of the embodiments disclosed herein.

[0084] Figure 5 illustrates a components of a network function 500 which are configured to operate according to some embodiments of the present disclosure.

[0085] Referring to Figure 5, the NF 500 may correspond to a CUSF, CITF, UDR, UDM, or other network function disclosed herein. The NF 500 can include one or more network interfaces 530 (referred to as "network interface" for brevity), one or more processors 510 (referred to as "processor" for brevity), and one or more memories 520 (referred to as "memory" for brevity) containing program code 522.

[0086] The network interface 530 may be configured to communicate through a wired interface, e.g., Ethernet, and/or wireless interface, e.g., wireless transceiver, according to one or more proprietary protocols and/or industry standardized protocols, e.g., WiFi, 3GPP 4G, 5G (NR), etc. The processor 510 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks. The processor 510 is configured to execute program code 522 in the memory 520, described below as a computer readable medium, to perform some or all of the operations and methods that are described above for one or more of the embodiments of CUSF, CHF, UDR, UDM, or other network function disclosed herein.

[0087] Abbreviations Explanation

AMF Access and Mobility Management Function

AN Access Network

CAMEL Customized Applications for Mobile networks

Enhanced Logic

CDR Charging Data Record

CHF Charging Function

CUSF Charging UE Setup Function

DNN Data Network Name

HPLMN Home Public Land Mobile Network

IMS IP multimedia service

LBO Local Break Out (roaming)

NF Network Function

PDU Protocol Data Unit

PEI Permanent Equipment Identifier

PLMN Public Land Mobile Network

(R)AN (Radio) Access Network

S-NSSAI Single Network Slice Selection Assistance Information

SMF Session Management Function

SMS Short Messaging Service

SUPI Subscription Permanent Identifier

UDM Unified Data Management

UDR Unified Data Repository

UE User Equipment

UPF User Plane Function

VPLMN Visited Public Land Mobile Network

[0088] In the above-description of various embodiments of the present disclosure, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense expressly so defined herein.

[0089] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. [0090] The terminology used herein is for the purpose of describing particular aspects only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. Like reference numbers signify like elements throughout the description of the figures.

[0091] The corresponding structures, materials, acts, and equivalents of any means or step plus function elements in the claims below are intended to include any disclosed structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The aspects of the disclosure herein were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure with various modifications as are suited to the particular use contemplated.

[0092] Cited References:

[0093] [1] TS 23.502 vl6.6.0

[0094] [2] TS 23.501 vl6.6.0

Claims

Claims:

1. A method performed by a user equipment, UE, comprising: sending (200, 300, 600) a local break out, LBO, access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function; receiving (306, 602), from the network function, LBO setup information that configures what network resource usage measurements and reporting the UE is to perform; setting-up (308, 604) a session with a network; and performing (308, 606) network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information.

2. The method of Claim 1, wherein the network function comprises a charging UE setup function, CUSF.

3. The method of any of Claims 1 to 2, wherein the sending (300, 600) of the LBO access request comprises: embedding in the LBO access request an indication of at least one of the following: storage capacity at the UE for storing network resource usage measurements by the UE for reporting; time accuracy of the UE when performing network resource usage measurements for reporting; location determination capability of the UE when performing network resource usage measurements for reporting; and indication of a defined type characteristic of the UE.

4. The method of any of Claims 1 to 3, wherein the sending (300, 600) of the LBO access request comprises: embedding in the LBO access request an indication of at least one of: an indication of which network the UE is registered to; a combination of data network name,

DNN, and single network slice selection assistance information, S-NSSAI, that the UE wants to use for communications; and a Subscription Permanent Identifier, SUPI, of the UE and a Permanent Equipment Identifier, PEI, of the UE.

5. The method of any of Claims 1 to 4, wherein the performing (308, 606) of the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, comprises: controlling at least one of the following responsive to the LBO setup information: what destination address is indicated in reports of the network resource usage measurements sent by the UE; frequency at which reports of the network resource usage measurements are sent by the UE; what type of event triggers new measurements of the network resource usage by the UE; and what combination of a single network slice selection assistance information, S- NSSAI associated with a HPLMN or a serving PLMN, and a data network name, DNN, for which the UE performs the network resource usage measurements and reporting.

6. The method of Claim 5, wherein the controlling at least one of the following responsive to the LBO setup information, comprises: responsive to the LBO setup information, controlling what type of event triggers new measurements of the network resource usage by the UE, wherein the type of event comprises at least one of: network change by the UE for ongoing communications of the session; location change by the UE during ongoing communications of the session; and radio access technology change by the UE for ongoing communications of the session.

7. The method of any of Claims 1 to 6, wherein the performing (308, 606) of the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, comprises: measuring a defined type of network resource usage that is indicated by the LBO setup information.

8. The method of any of Claims 1 to 7, wherein the performing (308, 606) of the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, comprises: sending a report of the network resource usage measurements for the session to a home charging function, hCHF, using the session or using another session that is setup with the network.

9. The method of any of Claims 1 to 8, wherein the performing (308, 606) of the network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information, comprises: sending reports of the network resource usage measurements for the session to a home charging function, hCHF, using short messaging service, SMS, communications and/or using control plane communications.

10. A computer program product comprising: a non-transitory computer readable medium storing instructions configured to be executed by at least one processor of a network function of a network node to cause the at least one processor to perform the method of any of Claims 1 to 9.

11. A method performed by a network function comprising: receiving (300, 700) a local break out, LBO, access request containing an indication of network resource usage reporting capabilities of a UE; generating (301, 702) LBO setup information that configures what network resource usage measurements and reporting the UE is to perform; and sending (306, 704) the LBO setup information to the UE.

12. The method of Claim 11, wherein the network function comprises a charging UE setup function, CUSF.

13. The method of any of Claims 11 to 12, wherein the generating (301, 702) of the LBO setup information that configures what network resource usage measurements and reporting the UE is to perform, comprises: generating the LBO setup information based on an indication embedded in the LBO access request of at least one of the following: storage capacity at the UE for storing network resource usage measurements by the UE for reporting; time accuracy of the UE when performing network resource usage measurements for reporting; location determination capability of the UE when performing network resource usage measurements for reporting; and indication of a defined type characteristic of the UE.

14. The method of any of Claims 11 to 13, wherein the generating (301, 702) of the LBO setup information that configures what network resource usage measurements and reporting the UE is to perform, comprises: generating the LBO setup information based on an indication embedded in the LBO access request of at least one of: a combination of a data network name, DNN, and a single network slice selection assistance information, S-NSSAI, that the UE wants to use for communications; and a Subscription Permanent Identifier, SUPI, of the UE and a Permanent Equipment Identifier, PEI, of the UE.

15. The method of any of Claims 11 to 14, wherein the generating (301, 702) of the LBO setup information that configures what network resource usage measurements and reporting the UE is to perform, comprises: generating the LBO setup information to control at least one of the following: what destination address is indicated in reports of the network resource usage measurements sent by the UE; frequency at which reports of the network resource usage measurements are sent by the UE; what type of event triggers new measurements of the network resource usage by the UE; and what combination of a single network slice selection assistance information, S-NSSAI, associated with a HPLMN or a serving PLMN, and a data network name, DNN, for which the UE is to perform the network resource usage measurements and reporting.

16. The method of Claim 15, wherein the generating of the LBO setup information to control at least one of the following, comprises: identifying the type of event that will trigger new measurements of the network resource usage by the UE, as at least one of the following: network change by the UE for ongoing communications of a session; location change by the UE during ongoing communications of a session; and radio access technology change by the UE for ongoing communications of a session.

17. The method of any of Claims 11 to 16, wherein the generating (301, 702) of the LBO setup information that configures what network resource usage measurements and reporting the UE is to perform, comprises: determining whether the UE is allowed for LBO based on content of the LBO access request; and when the UE is determined to be allowed for LBO, initiating (302) recordation in a unified data repository, UDR, or in a unified data management, UDM, that an identity of the UE is authorized to use LBO roaming or is preferred to use LBO roaming, for network resource usage measurements and reporting for a network identified by at least one of a data network name, DNN, and a single network slice selection assistance information, S-NSSAI, which the network function determines based on content of the LBO access request.

18. A computer program product comprising: a non-transitory computer readable medium storing instructions configured to be executed by at least one processor of a network function of a network node to cause the at least one processor to perform the method of any of Claims 11 to 17.

19. A method performed by a network function comprising: obtaining (800) user equipment, UE, local break out, LBO, information for a UE identity and a network identified by at least one of a data network name, DNN, and a single network slice selection assistance information, S-NSSAI; and determining (802) based on the UE LBO information whether the UE identity is allowed to use LBO for network resource usage measurements and reporting for the network.

20. The method of Claim 19, wherein the obtaining (800) of the UE LBO information comprises: querying a unified data repository, UDR, or a unified data management, UDM, to obtain the UE LBO information using the UE identity and the network identified by at least one of the DNN and the S-NSSAI.

21. The method of Claim 20, wherein the network function determines (802) whether the UE identity is allowed to use LBO based on LBO roaming information contained in the response to the query from the UDR or the UDM.

22. The method of any of Claims 19 to 21, wherein the network function comprises an access management function, AMF, or a charging function, CHF.

23. The method of any of Claims 19 to 22, further comprising instructing a charging UE setup function, CUSF, to bar the UE from using LBO to access the network responsive to determining that the UE identity is not allowed to use LBO for network resource usage measurements and reporting for the network.

24. The method of any of Claims 19 to 23, wherein the UE LBO information for the UE identity is obtained (800) as content of unified data management, UDM, subscription data received by the network function.

25. The method of any of Claims 19 to 23, wherein the UE LBO information for the UE identity indicates LBO reporting is allowed if the UE supports LBO reporting to the network function; the method further comprising receiving from the UE an indication that the UE supports LBO reporting to the network function.

26. A computer program product comprising: a non-transitory computer readable medium storing instructions configured to be executed by at least one processor of a network function of a network node to cause the at least one processor to perform the method of any of Claims 19 to 24.

27. A user equipment, UE, (100) comprising: at least one processor (410); and at least one memory (420) coupled to the at least one processor (410) and storing computer readable program code that when executed by the at least one processor (410) causes the at least one processor (410) to perform operations configured to: send a local break out, LBO, access request containing an indication of network resource usage reporting capabilities of the UE, toward a network function; receive, from the network function, LBO setup information that configures what network resource usage measurements and reporting the UE is to perform; setup a session with a network; and perform network resource usage measurements for the session and reporting of the network resource usage measurements, as configured by the LBO setup information.

28. The UE (100) of Claim 27, wherein: the computer readable program code when executed by the at least one processor (410) further causes the at least one processor (410) to perform operations configured to perform the method of any of Claims 2 to 9.

29. A network function (500) comprising: at least one processor (510); and at least one memory (520) coupled to the at least one processor (510) and storing computer readable program code that when executed by the at least one processor (510) causes the at least one processor (510) to perform operations configured to: receive a local break out, LBO, access request containing an indication of network resource usage reporting capabilities of a UE; generate LBO setup information that configures what network resource usage measurements and reporting the UE is to perform; and send the LBO setup information to the UE.

30. The network function (500) of Claim 29, wherein: the computer readable program code when executed by the at least one processor (510) further causes the at least one processor (510) to perform operations configured to perform the method of any of Claims 12 to 17.

31. A network function (500) comprising: at least one processor (510); and at least one memory (520) coupled to the at least one processor (510) and storing computer readable program code that when executed by the at least one processor (510) causes the at least one processor (510) to perform operations configured to: obtain user equipment, UE, local break out, LBO, information for a UE identity and a network identified by at least one of a data network name, DNN, and a single network slice selection assistance information, S-NSSAI; and determine based on the UE LBO information whether the UE identity is allowed to use LBO for network resource usage measurements and reporting for the network.

32. The network function (500) of Claim 31, wherein: the computer readable program code when executed by the at least one processor (510) further causes the at least one processor (510) to perform operations configured to perform the method of any of Claims 20 to 24.