Patent Description:
Certain wireless systems support a feature called multi-access data connections (e.g., multi-access PDU ("MA PDU") session) between a UE and a UPF, and the policy-controlled routing of the MA PDU Session traffic over two access networks. Essentially, an MA PDU Session is a data connection between a UE and a UPF that can transfer data traffic of a service data flow ("SDF") (e.g., data traffic of an application) by using both a 3GPP access network (e.g., new radio ("NR") access or evolved universal terrestrial access ("E-UTRA") access) and a non-3GPP access network (e.g., Wi-Fi or wireline access) by applying multi-access rules (e.g., Access Traffic Steering, Switching and Splitting ("ATSSS") rules and N4 rules in the UE and in the UPF respectively) and/or port mapping. Round trip communications may take a variable amount of time in such connections.

"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enablers for network automation for the <NUM> System (5GS); Phase <NUM> (Release <NUM>)", 3GPP DRAFT; <NUM>-<NUM>-<NUM>, (<NUM>-<NUM>-<NUM>) discloses ATSSS based on NWDA by creating a new NWDA type which includes RTT NWDA or by adding RTT NWDA to the existing "Observed Service Experience" NWDA type.

According to the present disclosure, there are provided a method according to claim <NUM>, a user equipment according to claim <NUM>, an apparatus according to claim <NUM>, a method according to claim <NUM>, and a processor according to claim <NUM>.

Methods for round trip time determination based on analytics are disclosed. Apparatuses and systems also perform the functions of the methods.

One method of a user equipment ("UE") for round trip time determination based on analytics includes establishing a multiaccess data connection with a user plane function in the mobile communication network. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network. The method includes transmitting a first performance measurement functionality message to the user plane function. The first performance measurement functionality message includes a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function in the mobile communication network to request a first type of analytics from a network data analytics function. The method includes receiving a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics. The second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

One method of a first network function for round trip time determination based on analytics includes establishing a multiaccess data connection with a user equipment. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network. The method includes receiving a first message including a first set of parameters including a quality of service flow identifier. The method includes transmitting a request a first type of analytics to a network data analytics function in response to receiving the first message. The method includes, in response to transmitting the request for the first type of analytics, receiving estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagram.

Methods, apparatuses, and systems are disclosed for round trip time determination based on analytics.

In certain configurations, a UE capable of supporting Access Traffic Steering, Switching, Splitting ("ATSSS"), may simultaneously communicate over a 3GPP access network (e.g., NG-RAN) and over a non-3GPP access network (e.g., wide local access network ("WLAN")). In such configurations, the traffic exchanged between a UE and a remote host may either be distributed over both accesses, or may be sent on a best access only (e.g., on an access characterized by less latency), or a less Round Trip Time ("RTT"). In an uplink ("UL") direction, the UE may decide how to distribute the traffic across the two accesses based on policy rules (e.g., ATSSS rules) provided by the network. Similarly, in a downlink ("DL") direction, a UPF at the edge of the <NUM> Core ("5GC") network decides how to distribute the traffic across the two accesses based on corresponding policy rules (e.g., N4 rules).

In some embodiments, if communication latency is important, policy rules may indicate that specific traffic should be routed according to a latency-dependent condition. For example, the policy rules in a UE may indicate: <NUM>) traffic of App-X may be routed over 3GPP access if latency over 3GPP access < <NUM>; or <NUM>) internet protocol ("IP") multimedia services ("IMS") voice traffic may be routed to an access with a smallest Latency.

To enforce the above policy rules, a UE may be required to measure a latency (or RTT) over 3GPP access and the latency (or RTT) over non-3GPP access. Similarly, the UPF may be required to measure the latency (or RTT) over 3GPP access and the latency (or RTT) over non-3GPP access to decide how to route the DL traffic to comply with the policy rules.

In various embodiments, a Performance Measurement Functionality ("PMF") may be supported in a UE and in a UPF (e.g., which assists in taking real-time RTT measurements over the two accesses). In particular, RTT measurements may be taken by exchanging PMF-Echo Request and/or PMF-Echo Response messages between a PMF function in the UE (UE-PMF) and the PMF function in the UPF (UPF-PMF). Thus, the UE may calculate a RTT over each access, which is associated with the latency of each access. However, sending frequent PMF-Echo Request and/or Response messages (e.g., once every <NUM>-<NUM> sec) between the UE and UPF, and over UDP and/or IP may be inefficient since it uses a lot of overhead and consumes a lot of radio, network, and battery resources. Furthermore, it may create additional traffic, which may increase congestion and may result to much higher latency values.

In certain embodiments, there may be methods for estimating a RTT in a UE and in a UPF that does not require the exchange of real-time measurement messages between the UE and the UPF and, thus, may improve efficiency of RTT estimations for each access type. As described herein, different embodiments use RTT analytics information provided by a Network Data Analytics Function ("NWDAF").

<FIG> depicts a wireless communication system <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. In one embodiment, the wireless communication system <NUM> includes at least one remote unit <NUM> (having multi-access rules <NUM> and QoS rules <NUM>), a fifth-generation radio access network ("<NUM>-RAN") <NUM>, and a mobile core network <NUM>. The <NUM>-RAN <NUM> and the mobile core network <NUM> form a mobile communication network. The <NUM>-RAN <NUM> may be composed of a third generation partnership program ("3GPP") access network <NUM> containing at least one cellular base unit <NUM> and/or a non-3GPP access network <NUM> containing at least one access point <NUM>. The remote unit communicates with the 3GPP access network <NUM> using 3GPP communication links <NUM> and communicates with the non-3GPP access network <NUM> using non-3GPP communication links <NUM>. Even though a specific number of local units <NUM>, <NUM>, remote units <NUM>, 3GPP access networks <NUM>, cellular base units <NUM>, 3GPP communication links <NUM>, non-3GPP access networks <NUM>, access points <NUM>, non-3GPP communication links <NUM>, and mobile core networks <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM>, 3GPP access networks <NUM>, cellular base units <NUM>, 3GPP communication links <NUM>, non-3GPP access networks <NUM>, access points <NUM>, non-3GPP communication links <NUM>, and mobile core networks <NUM> may be included in the wireless communication system <NUM>.

In one implementation, the wireless communication system <NUM> is compliant with the <NUM> system specified in the 3GPP specifications. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication network, for example, long term evolution ("LTE") or worldwide interoperability for microwave access ("WiMAX"), among other networks.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. Moreover, the remote units <NUM> may be referred to as UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit ("WTRU"), a device, or by other terminology used in the art.

The remote units <NUM> may communicate directly with one or more of the cellular base units <NUM> in the 3GPP access network <NUM> via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over the 3GPP communication links <NUM>. Similarly, the remote units <NUM> may communicate with one or more access points <NUM> in the non-3GPP access network(s) <NUM> via UL and DL communication signals carried over the non-3GPP communication links <NUM>. Here, the access networks <NUM> and <NUM> are intermediate networks that provide the remote units <NUM> with access to the mobile core network <NUM>.

In some embodiments, the remote units <NUM> communicate with a remote host <NUM> via a network connection with the mobile core network <NUM>. For example, an application in a remote unit <NUM> (e.g., web browser, media client, telephone/VoIP application) may trigger the remote unit <NUM> to establish a PDU session (or other data connection (e.g., multi-access data connection <NUM>)) with the mobile core network <NUM> using the <NUM>-RAN <NUM> (e.g., a 3GPP access network <NUM> and/or a non-3GPP access network <NUM>). The mobile core network <NUM> then relays traffic between the remote unit <NUM> and the data network <NUM> (e.g., remote host <NUM>) using the PDU session. Note that the remote unit <NUM> may establish one or more PDU sessions (or other data connections) with the mobile core network <NUM>. As such, the remote unit <NUM> may have at least one PDU session for communicating with the data network <NUM>. The remote unit <NUM> may establish additional PDU sessions for communicating with other data network and/or other remote hosts.

Moreover, the remote unit <NUM> may establish a multi-access PDU session (i.e., multi-access data connection) with the mobile core network <NUM> whereby traffic of the multi-access PDU session is steered over one or both of the 3GPP access network <NUM> and/or a non-3GPP access network <NUM>, according to steering rules. Additionally, a user-plane connection over 3GPP access <NUM> may be established over the 3GPP access network <NUM> for transferring traffic of the multi-access PDU session. Similarly, a user-plane connection over non-3GPP access <NUM> may be established over the non-3GPP access network <NUM> for handling traffic of the multi-access PDU session. Accordingly, the remote unit <NUM> may be configured with multi-access rules <NUM> and QoS rules <NUM> for determining QoS data flows for performing measurements.

The cellular base units <NUM> may be distributed over a geographic region. In certain embodiments, a cellular base unit <NUM> may also be referred to as an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, or by any other terminology used in the art. The cellular base units <NUM> are generally part of a radio access network ("RAN"), such as the 3GPP access network <NUM>, that may include one or more controllers communicably coupled to one or more corresponding cellular base units <NUM>. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The cellular base units <NUM> connect to the mobile core network <NUM> via the 3GPP access network <NUM>.

The cellular base units <NUM> may serve a number of remote units <NUM> within a serving area, for example, a cell or a cell sector, via a 3GPP communication link <NUM>. The cellular base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the cellular base units <NUM> transmit DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the 3GPP communication links <NUM>. The 3GPP communication links <NUM> may be any suitable carrier in licensed or unlicensed radio spectrum. The 3GPP communication links <NUM> facilitate communication between one or more of the remote units <NUM> and/or one or more of the cellular base units <NUM>.

The non-3GPP access networks <NUM> may be distributed over a geographic region. Each non-3GPP access network <NUM> may serve a number of remote units <NUM> with a serving area. An access point <NUM> in a non-3GPP access network <NUM> may communicate directly with one or more remote units <NUM> by receiving UL communication signals and transmitting DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Both DL and UL communication signals are carried over the non-3GPP communication links <NUM>. The 3GPP communication links <NUM> and non-3GPP communication links <NUM> may employ different frequencies and/or different communication protocols. In various embodiments, an access point <NUM> may communicate using unlicensed radio spectrum. The mobile core network <NUM> may provide services to a remote unit <NUM> via the non-3GPP access networks <NUM>, as described in greater detail herein.

In some embodiments, a non-3GPP access network <NUM> connects to the mobile core network <NUM> via an interworking function <NUM>. The interworking function <NUM> provides interworking between the remote unit <NUM> and the mobile core network <NUM>. In some embodiments, the interworking function <NUM> is a Non-3GPP Interworking Function ("N3IWF") and, in other embodiments, it is a Trusted Non-3GPP Gateway Function ("TNGF"). The N3IWF supports the connection of "untrusted" non-3GPP access networks to the mobile core network (e.g., 5GC), whereas the TNGF supports the connection of "trusted" non-3GPP access networks to the mobile core network. The interworking function <NUM> supports connectivity to the mobile core network <NUM> via the "N2" and "N3" interfaces, and it relays "N1" signaling between the remote unit <NUM> and the AMF <NUM>. Both the 3GPP access network <NUM> and the interworking function <NUM> communicate with the AMF <NUM> using a "N2" interface. The interworking function <NUM> also communicates with the UPF <NUM> using a "N3" interface.

In certain embodiments, a non-3GPP access network <NUM> may be controlled by an operator of the mobile core network <NUM> and may have direct access to the mobile core network <NUM>. Such a non-3GPP AN deployment is referred to as a "trusted non-3GPP access network. " A non-3GPP access network <NUM> is considered as "trusted" when it is operated by the 3GPP operator, or a trusted partner, and supports certain security features, such as strong air-interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by an operator (or trusted partner) of the mobile core network <NUM>, does not have direct access to the mobile core network <NUM>, or does not support the certain security features is referred to as a "non-trusted" non-3GPP access network.

In one embodiment, the mobile core network <NUM> is a <NUM> core ("5GC") or the evolved packet core ("EPC"), which may be coupled to a data network (e.g., the data network <NUM>, such as the Internet and private data networks, among other data networks. A remote unit <NUM> may have a subscription or other account with the mobile core network <NUM>. Each mobile core network <NUM> belongs to a single public land mobile network ("PLMN").

The mobile core network <NUM> includes several network functions ("NFs"). As depicted, the mobile core network <NUM> includes at least a UPF <NUM> that serves the 3GPP access network <NUM> and the non-3GPP access network <NUM>. Note that in certain embodiments, the mobile core network may contain one or more intermediate UPFs, for example a first intermediate UPF that serves the non-3GPP access network <NUM> and the second intermediate UPF that serves the 3GPP access network <NUM>. In such embodiments, the UPF <NUM> would be an anchor UPF receiving UP traffic of both intermediate UPFs.

The mobile core network <NUM> also includes multiple control plane functions including, but not limited to, an Access and Mobility Management Function ("AMF") <NUM> that serves both the 3GPP access network <NUM> and the non-3GPP access network <NUM>, a Session Management Function ("SMF") <NUM>, a Policy Control Function ("PCF") <NUM>, and a Unified Data Management function ("UDM") <NUM>. In certain embodiments, the mobile core network <NUM> may also include an Authentication Server Function ("AUSF"), a Network Repository Function ("NRF") (used by the various NFs to discover and communicate with each other over application programming interfaces ("APIs")), or other NFs defined for the 5GC. In various embodiments, the mobile core network <NUM> may include a PMF (not shown) to assist the remote unit <NUM> and/or the UPF <NUM> in taking performance measurements over the two accesses, including latency measurements. In one embodiment, the PMF may be co-located with the UPF <NUM>.

In various embodiments, the mobile core network <NUM> supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network <NUM> optimized for a certain traffic type or communication service. Each slice may be identified using a single network slice selection assistance information ("S-NSSAI"). In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF <NUM> and UPF <NUM>. In some embodiments, the different network slices may share some common network functions, such as the AMF <NUM>. The different network slices are not shown in <FIG> for ease of illustration, but their support is assumed.

Although specific numbers and types of network functions are depicted in <FIG>, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network <NUM>. Moreover, where the mobile core network <NUM> is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a mobility management entity ("MME"), secondary ("S") gateway ("GW") ("S-GW"), primary ("P") GW ("P-GW"), home subscriber server ("HSS"), and the like.

As depicted, a remote unit <NUM> (e.g., a UE) may connect to the mobile core network (e.g., to a <NUM> mobile communication network) via two types of accesses: (<NUM>) via 3GPP access network <NUM> and (<NUM>) via a non-3GPP access network <NUM>. The first type of access (e.g., 3GPP access network <NUM>) uses a 3GPP-defined type of wireless communication (e.g., next generation radio access network ("NG-RAN")) and the second type of access (e.g., non-3GPP access network <NUM>) uses a non-3GPP-defined type of wireless communication (e.g., WLAN). The <NUM>-RAN <NUM> refers to any type of <NUM> access network that can provide access to the mobile core network <NUM>, including the 3GPP access network <NUM> and the non-3GPP access network <NUM>.

The remote unit <NUM> may estimate a RTT over each user-plane path to transmit data to the remote host <NUM> via an access type with the smallest-delay. As described herein, the remote unit <NUM> estimates a RTT over each user-plane path by using RTT analytics provided by an NWDAF.

In some embodiments, a remote unit <NUM> (e.g., UE) sends a new PMF request message to a UPF which triggers a network (e.g., either the UPF or the SMF) to request RTT analytics from an NWDAF valid at the present UE location and in a certain time period. The RTT analytics provided by the NWDAF contains a predicted RTT for each access type and is derived by the NWDAF based on historical RTT measurements available in the NWDAF. The predicted RTT values in the RTT analytics are then sent back to the remote unit <NUM> (e.g., UE) and are applied for determining a smallest-delay access type, or evaluating RTT thresholds, and so forth.

In a first embodiment (e.g., embodiment A), RTT analytics from an NWDAF are requested by an SMF. If a UE does not provide its location to the SMF (e.g., via the UPF), then the SMF determines the UE location (e.g., by creating a mobility subscription with the AMF serving the UE and receiving location_update event reports from the AMF) if the UE changes cells or changes Wi-Fi access point ("AP").

In a second embodiment (e.g., embodiment B), RTT analytics from an NWDAF are requested by a UPF. If the UE does not provide its location to the UPF, then the UPF determines the UE location (e.g., by creating a mobility subscription with the AMF serving the UE and receiving location_update event reports from the AMF) if the UE changes cells or Wi-Fi AP.

<FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and <FIG> may be applied to the first embodiment and/or the second embodiment.

<FIG> and <FIG> depict a procedure <NUM> including part <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. The procedure <NUM> involves a UE <NUM> (e.g., one embodiment of the remote unit <NUM>) and a <NUM> network <NUM>. The <NUM> network <NUM> includes a UPF <NUM>, an SMF <NUM>, an AMF <NUM>, and an NWDAF <NUM>.

In <FIG> Step <NUM>, the NWDAF <NUM> collects <NUM> data (e.g., see Table <NUM> for some examples) from several network functions in the mobile communication network, including operations, administration, and maintenance ("OAM"), application functions ("AFs"), UPFs, AMFs, and so forth. The data collected at the NWDAF <NUM> may have a structure (e.g., see Table <NUM>) and may be used for deriving RTT analytics for a specific access type, quality of service ("QoS") flow, location, and time period. The RTT analytics may be used to predict the RTT that will be experienced if data is transmitted in a certain 3GPP cell or non-3GPP AP at a certain time period and via a certain QoS flow.

In Step <NUM>, the UE <NUM> establishes <NUM> a MA PDU session. A PDU Session establishment accept message received by the UE <NUM> contains Measurement Assistance Information, which may include an IP address and user datagram protocol ("UDP") ports (one for each access type) for which the UE <NUM> should send PMF messages. The Measurement Assistance Information may also indicate to the UE <NUM> whether the network supports analytics-based RTT estimation.

In Part <NUM>, the UE <NUM> requests and receives RTT analytics from the network.

In Step <NUM>, the UE <NUM> connects <NUM> to Cell-A over 3GPP access and to a basic service set identifier ("BSSID") <NUM> ("BSSID-<NUM>") over non-3GPP access (e.g., Wi-Fi).

In Step <NUM>, the UE <NUM> determines <NUM> that it should estimate a RTT over 3GPP access and over non-3GPP access. This may be determined if the UE <NUM> needs to apply an ATSSS rule that requires traffic steering based on a smallest-delay steering policy.

In Step <NUM>, since the UE <NUM> knows that the network supports analytics-based RTT estimation, the UE <NUM> requests <NUM> from the network to provide RTT estimations for its present location. In particular, the UE <NUM> sends a PMF-RttReport request message over 3GPP or over non-3GPP access including: <NUM>) the identity of the QoS flow ("QFI") for which RTT estimations are needed; <NUM>) optionally, its present cell identity (Cell-A) and Wi-Fi AP identity (BSSID-<NUM>); and <NUM>) an indication of whether the RTT reports should be provided periodically or if a threshold condition is met.

In Step <NUM>, a conditional step required in the first embodiment, where the SMF <NUM> requests the RTT analytics from the NWDAF <NUM>. The UPF <NUM> forwards <NUM> the UE's <NUM> request for RTT reports to the SMF <NUM> by sending a message over the N4 interface (N4 message <NUM>).

In Step <NUM>, if the UE <NUM> location (Cell-A, BSSID-<NUM>) is not provided by the UE <NUM> in Step <NUM>, the network (SMF <NUM> or UPF <NUM>) obtains <NUM> itself the UE <NUM> location. In one scenario applicable to embodiment A, the SMF <NUM> subscribes to the AMF <NUM> serving the UE <NUM> and receives mobility notifications indicating the Cell ID and the BSSID used by the UE <NUM>. In another scenario applicable to embodiment B, the UPF <NUM> subscribes to the AMF <NUM> serving the UE <NUM> and receives mobility notifications indicating the Cell ID and the BSSID used by the UE <NUM>.

In Step <NUM>, the SMF <NUM> (in embodiment A) or the UPF <NUM> (in embodiment B) sends <NUM> a subscription request message to NWDAF <NUM>, which requests from NWDAF <NUM> (a) to provide RTT analytics for the present cell of the UE <NUM> (Cell-A) and (b) to provide RTT analytics for the present Wi-Fi AP of the UE <NUM> (BSSID-<NUM>). The subscription request message indicates also the QFI for which analytics are requested and may include a Time Period for which the RTT analytics should be valid. In addition, it may contain reporting information indicating when the RTT analytics should be reported (e.g., periodically or when a threshold condition is met).

Turning to <FIG>, in Step <NUM>, if the NWDAF <NUM> has not already collected data to be used for RTT analytics, the NWDAF <NUM> initiates <NUM> a data collection procedure.

In Step <NUM>, the NWDAF <NUM> responds <NUM> to the SMF <NUM> or the UPF <NUM> with a response message acknowledging the creation of the requested subscription.

In Step <NUM>, the NWDAF <NUM> derives <NUM> the requested RTT analytics based on the collected data available in the NWDAF <NUM>.

In Step 11a, if the requested RTT analytics are available, the NWDAF <NUM> provides <NUM> the RTT analytics by sending a notify request message to the SMF <NUM> or the UPF <NUM>. As an example, the notify request message may indicate that the estimated RTT over 3GPP access is <NUM> with confidence <NUM>%, and the estimated RTT over non-3GPP access is <NUM> with confidence <NUM>%. In Step 11b, the SMF <NUM> or the UPF <NUM> acknowledges <NUM> the reception of the notify message.

In Step <NUM>, a conditional step required in embodiment A, the SMF <NUM> requests the RTT analytics from the NWDAF <NUM>. The SMF <NUM> forwards <NUM> to the UPF <NUM> the RTT analytics received from the NWDAF <NUM> by sending a message <NUM> over the N4 interface.

In Step <NUM>, the UPF <NUM> sends <NUM> to the UE <NUM> a PMF-RttReport notify message containing the estimated RTT values for the two accesses. This message may also contain the confidence received by the NWDAF <NUM>, although this confidence may not be used by the UE <NUM>. Based on the received RTT values, the UE <NUM> identifies the access that provides the smallest delay at the present UE <NUM> location and time. It then steers the relevant traffic over this access.

In Part <NUM>, the UE <NUM> receives updated and/or fresh RTT analytics from the network while it remains in the same cell and Wi-Fi AP.

<FIG> depicts a procedure <NUM> including part <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. The procedure <NUM> involves the UE <NUM> (e.g., one embodiment of the remote unit <NUM>) and the <NUM> network <NUM>. The <NUM> network <NUM> includes the UPF <NUM>, the SMF <NUM>, and the NWDAF <NUM>.

In Step <NUM>, the NWDAF <NUM> determines <NUM> that fresh RTT analytics should be provided (e.g., because a reporting period has expired, or a threshold condition has been met). A threshold condition may indicate that fresh RTT analytics should be provided when the estimated RTT over 3GPP access changes by <NUM>%, the estimated RTT over 3GPP access exceeds <NUM>, or the estimated RTT over 3GPP access exceeds the estimated RTT over non-3GPP access, for example.

In Step 2a, the NWDAF <NUM> provides <NUM> the fresh RTT analytics by sending a notify request message to the SMF <NUM> or the UPF <NUM>. As an example, the notify request message may indicate that the new estimated RTT over 3GPP access is <NUM> with confidence <NUM>%, and the estimated RTT over non-3GPP access is <NUM> with confidence <NUM>%. In Step 2b, the SMF <NUM> or the UPF <NUM> acknowledges <NUM> the reception of the notify message.

In Step <NUM>, a conditional step may be required in embodiment A, the SMF <NUM> requests <NUM> the RTT analytics from the NWDAF <NUM>. The SMF <NUM> forwards to the UPF <NUM> the fresh RTT analytics received from the NWDAF <NUM> by sending a message <NUM> over the N4 interface.

In Step <NUM>, the UPF <NUM> sends <NUM> to the UE <NUM> a new PMF-RttReport notify message containing the estimated fresh RTT values for the two accesses. This message may also contain the confidence received by the NWDAF <NUM>, although this confidence may not be used by the UE <NUM>. The UE <NUM> adjusts its steering operation based on the received fresh RTT values.

In Part <NUM>, the UE <NUM> receives updated and/or fresh RTT analytics from the network if it moves to a new cell or Wi-Fi AP.

<FIG> and <FIG> depict a procedure <NUM> including part <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. The procedure <NUM> involves the UE <NUM> (e.g., one embodiment of the remote unit <NUM>) and the <NUM> network <NUM>. The <NUM> network <NUM> includes the UPF <NUM>, the SMF <NUM>, and the NWDAF <NUM>.

In <FIG> Step <NUM>, the UE <NUM> moves <NUM> to a new cell (e.g., Cell-B).

In Step <NUM>, a conditional step required if the UE <NUM> provides its location to the network. It is not required if the UE <NUM> location is determined by the network. In Step 2a, the UE <NUM> sends <NUM> a new PMF-RttReport request message including its new location (e.g., [Cell-B, BSSID-<NUM>]). In Step 2b and in embodiment A where the SMF <NUM> requests the RTT analytics from the NWDAF <NUM>, the UPF <NUM> sends <NUM> an N4 message <NUM> to the SMF <NUM> to provide the new location of the UE <NUM>.

In Step <NUM>, if the UE <NUM> location is not provided by the UE <NUM> (as in the previous step), the network itself determines <NUM> the new location of the UE <NUM>. In one scenario applicable to embodiment A, the SMF <NUM> receives a location_update event report from the AMF indicating the new Cell ID and/or the new BSSID used by the UE <NUM>. In another scenario applicable to embodiment B, the UPF <NUM> receives a location_update event report from the AMF indicating the new Cell ID and/or the new BSSID used by the UE <NUM>.

In Step 4a, the SMF <NUM> (in embodiment A) or the UPF <NUM> (in embodiment B) updates <NUM> the created subscription in the NWDAF <NUM> by sending an update request message that contains the new Cell ID (Cell-B) and BSSID of the UE <NUM>. In Step 4b, the NWDAF <NUM> responds <NUM> to the SMF <NUM> or the UPF <NUM> with a response message acknowledging the update of the subscription.

Turning to <FIG> Step <NUM>, the NWDAF <NUM> derives <NUM> fresh RTT analytics based on the new location of the UE <NUM> and the collected data available in the NWDAF <NUM>.

In Step 6a, if the requested RTT analytics are available, the NWDAF <NUM> provides <NUM> the RTT analytics by sending a notify request message to the SMF <NUM> or the UPF <NUM>. In Step 6b, the SMF <NUM> or the UPF <NUM> acknowledges <NUM> the reception of the notify message.

In Step <NUM>, a conditional step required in embodiment A, the SMF <NUM> requests the RTT analytics from the NWDAF <NUM>. The SMF <NUM> forwards <NUM> to the UPF <NUM> the fresh RTT analytics received from the NWDAF <NUM> by sending a message <NUM> over the N4 interface.

In Step <NUM>, the UPF <NUM> sends <NUM> to the UE <NUM> a PMF-RttReport notify message containing the estimated fresh RTT values for the two accesses. The UE <NUM> adjusts its steering operation based on the received fresh RTT values.

In Part <NUM>, the UE <NUM> stops receiving RTT analytics when one access becomes unavailable in the UE <NUM>.

In Step <NUM>, one of the two accesses becomes unavailable <NUM> in the UE <NUM>. This may occur if the UE <NUM> loses the 3GPP signal or the non-3GPP signal.

In Step 2a, the UE <NUM> reports <NUM> the unavailability of the access by sending a PMF-AccessReport to the UPF <NUM> via the available access. In Step 2b, the UPF <NUM> responds <NUM> with a PMF-Ack message.

In Step <NUM>, a conditional step required in embodiment A, the SMF <NUM> requests the RTT analytics from the NWDAF <NUM>. The UPF <NUM> indicates <NUM> to the SMF <NUM> that one access has become unavailable in the UE <NUM>.

In Step 4a, the SMF <NUM> (in embodiment A) or the UPF <NUM> (in embodiment B) sends <NUM> a message to the NWDAF <NUM> to delete a created RTT analytics subscription. The NWDAF <NUM> deletes this subscription and provides a response message. Optionally, in Step 4b, the NWDAF <NUM> may stop collecting <NUM> data for RTT analytics derivation. After this step, the UE <NUM> does not receive further RTT analytics because the UE <NUM> has only one access available and cannot use RTT information for determining how to route uplink data traffic. In Step 4c, the NWDAF <NUM> sends a response message.

<FIG> depicts one embodiment of a user equipment apparatus <NUM> that may be used for round trip time determination based on analytics, according to embodiments of the disclosure. The user equipment apparatus <NUM> may be one embodiment of the remote unit <NUM> and/or the UE <NUM>. Furthermore, the user equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, a transceiver <NUM>. In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touch screen. In certain embodiments, the user equipment apparatus <NUM> does not include any input device <NUM> and/or output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. Here, the transceiver <NUM> communicates with a mobile core network (e.g., a 5GC) via one or more access networks. Additionally, the transceiver <NUM> may support at least one network interface <NUM>. Here, the at least one network interface <NUM> facilitates communication with an eNB or gNB (e.g., using the "Uu" interface). Additionally, the at least one network interface <NUM> may include an interface used for communications with an AMF, an SMF, and/or a UPF.

In some embodiments, the transceiver <NUM> comprises a first transceiver that communicates with a mobile communication network via a first access network and a second transceiver that communicates with the mobile communication network via a second access network. In other embodiments, the transceiver <NUM> comprises a first functionality (e.g., modem) for communicating with the mobile communication network via the first access network and a second functionality (e.g., modem) for communicating with the mobile communication network via the second access network.

In various embodiments, the processor <NUM> establishes a multiaccess data connection with a user plane function in a mobile communication network. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network.

The transmitter <NUM> transmits a first performance measurement functionality message to the user plane function. The first performance measurement functionality message includes a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function in the mobile communication network to request a first type of analytics from a network data analytics function.

The receiver <NUM> receives a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics. The second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network and/or the third generation partnership program access network.

In some embodiments, the memory <NUM> stores data relating to round trip time determination based on analytics, for example storing access network information ("ANI"), IP addresses, and the like. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system ("OS") or other controller algorithms operating on the user equipment apparatus <NUM> and one or more software applications.

The output device <NUM>, in one embodiment, may include any known electronically controllable display or display device. The output device <NUM> may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device <NUM> includes an electronic display capable of outputting visual data to a user. For example, the output device <NUM> may include, but is not limited to, a liquid crystal display ("LCD") display, an LED display, an organic light emitting diode ("OLED") display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device <NUM> may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like.

In other embodiments, all or portions of the output device <NUM> may be located near the input device <NUM>.

As discussed above, the transceiver <NUM> communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver <NUM> operates under the control of the processor <NUM> to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor <NUM> may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages.

The transceiver <NUM> may include one or more transmitters <NUM> and one or more receivers <NUM>. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the user equipment apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers. In one embodiment, the transceiver <NUM> includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

In various embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit ("ASIC"), or other type of hardware component. In certain embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface <NUM> or other hardware components/circuits may be integrated with any number of transmitters <NUM> and/or receivers <NUM> into a single chip. In such embodiment, the transmitters <NUM> and receivers <NUM> may be logically configured as a transceiver <NUM> that uses one more common control signals or as modular transmitters <NUM> and receivers <NUM> implemented in the same hardware chip or in a multi-chip module.

<FIG> depicts one embodiment of a network equipment apparatus <NUM> that may be used for round trip time determination based on analytics, according to embodiments of the disclosure. In some embodiments, the network equipment apparatus <NUM> may implement a UPF. In other embodiments, the network equipment apparatus <NUM> may implement other network functions. Furthermore, network equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, a transceiver <NUM>. In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touch screen. In certain embodiments, the network equipment apparatus <NUM> does not include any input device <NUM> and/or output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. Here, the transceiver <NUM> communicates with one or more remote units <NUM>. Additionally, the transceiver <NUM> may support at least one network interface <NUM>. In some embodiments, the transceiver <NUM> supports a first interface for communicating with a RAN node, a second interface for communicating with one or more network functions in a mobile core network (e.g., a 5GC) and a third interface for communicating with a remote unit (e.g., UE).

The processor <NUM> is communicatively coupled to the memory <NUM>, the input device <NUM>, the output device <NUM>, and the first transceiver <NUM>.

In various embodiments, the network equipment apparatus <NUM> operates as a first network function. In such embodiments, the processor <NUM> establishes a multiaccess data connection with a user equipment. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network.

In some embodiments, the memory <NUM> stores data relating to round trip time determination based on analytics, for example storing ANI, IP addresses, UE contexts, and the like. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system ("OS") or other controller algorithms operating on the network equipment apparatus <NUM> and one or more software applications.

The output device <NUM>, in one embodiment, may include any known electronically controllable display or display device. The output device <NUM> may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device <NUM> includes an electronic display capable of outputting visual data to a user. As another, non-limiting, example, the output device <NUM> may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like.

As discussed above, the transceiver <NUM> may communicate with one or more remote units and/or with one or more interworking functions that provide access to one or more PLMNs. The transceiver <NUM> may also communicate with one or more network functions (e.g., in the mobile core network <NUM>). The transceiver <NUM> operates under the control of the processor <NUM> to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor <NUM> may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages.

The transceiver <NUM> may include one or more transmitters <NUM> and one or more receivers <NUM>. In certain embodiments, the one or more transmitters <NUM> and/or the one or more receivers <NUM> may share transceiver hardware and/or circuitry. For example, the one or more transmitters <NUM> and/or the one or more receivers <NUM> may share antenna(s), antenna tuner(s), amplifier(s), filter(s), oscillator(s), mixer(s), modulator/demodulator(s), power supply, and the like. In one embodiment, the transceiver <NUM> implements multiple logical transceivers using different communication protocols or protocol stacks, while using common physical hardware.

In one embodiment, the receiver <NUM> receives a first message includes a first set of parameters including a quality of service flow identifier. In some embodiments, the transmitter <NUM> transmits a request a first type of analytics to a network data analytics function in response to receiving the first message. In certain embodiments, in response to transmitting the request for the first type of analytics, the receiver <NUM> receives estimated round trip time values for the non-third generation partnership program access network and/or the third generation partnership program access network.

<FIG> depicts a method <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. In some embodiments, the method <NUM> is performed by a UE, such as the remote unit <NUM>, the UE <NUM> and/or the user equipment apparatus <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and establishes <NUM>, a multiaccess data connection with a user plane function in the mobile communication network. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network. The method <NUM> includes transmitting <NUM> a first performance measurement functionality message to the user plane function. The first performance measurement functionality message includes a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function in the mobile communication network to request a first type of analytics from a network data analytics function. The method <NUM> includes receiving <NUM> a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics. The second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof. The method <NUM> ends.

In certain embodiments, the method <NUM> further comprises applying the estimated round trip time values for determining how to route data traffic via the multiaccess data connection. In some embodiments, the first set of parameters comprises a cell identifier, a base station set identifier, a reporting period, at least one threshold, or some combination thereof. In various embodiments, the request for a first type of analytics comprises the quality of service flow identifier and the cell identifier, the base station set identifier, or a combination thereof. In one embodiment, the first network function comprises the user plane function.

In certain embodiments, the first network function comprises a session management function, and the user plane function transmits a first N4 message to the session management function in response to receiving the first performance measurement functionality message from the user equipment. In some embodiments, the first type of analytics comprises round trip time analytics for a non-third generation partnership program access network, for a third generation partnership program access network, or a combination thereof. In various embodiments, the round trip time analytics for the non-third generation partnership program access network, for the third generation partnership program access network, or the combination thereof are associated with the quality of service flow identifier.

<FIG> depicts a method <NUM> for round trip time determination based on analytics, according to embodiments of the disclosure. In some embodiments, the method <NUM> is performed by a network function, such as the UPF <NUM>, the SMF <NUM>, and/or the network apparatus <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and establishes <NUM> a multiaccess data connection with a user equipment. The multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network. The method <NUM> includes receiving <NUM> a first message including a first set of parameters including a quality of service flow identifier. The method <NUM> includes transmitting <NUM> a request a first type of analytics to a network data analytics function in response to receiving the first message. The method <NUM>, in response to transmitting the request for the first type of analytics, receives <NUM> estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof. The method <NUM> ends.

In certain embodiments, the first set of parameters comprises a cell identifier, a base station set identifier, a reporting period, at least one threshold, or some combination thereof. In some embodiments, the request for a first type of analytics comprises the quality of service flow identifier and the cell identifier, the base station set identifier, or a combination thereof.

In various embodiments, the first network function comprises a user plane function, and the first message is a first performance measurement functionality message transmitted by a user equipment. In one embodiment, the user plane function transmits a second performance measurement functionality message to the user equipment in response to receiving the estimated round trip time values, and the second performance measurement functionality message contains the estimated round trip time values. In certain embodiments, the first network function comprises a session management function, and the first message is a first N4 message transmitted by a user plane function in response to the user plane function receiving a first performance measurement functionality message from a user equipment.

In some embodiments, the session management function transmits a second N4 message to the user plane function in response to receiving the estimated round trip time values, the second N4 message contains the estimated round trip time values, the user plane function transmits a second performance measurement functionality message to the user equipment in response to receiving the second N4 message, and the second performance measurement functionality message contains the estimated round trip time values. In various embodiments, the first type of analytics comprises round trip time analytics for the non-third generation partnership program access network, for the third generation partnership program access network, or a combination thereof. In one embodiment, the round trip time analytics for the non-third generation partnership program access network and for the third generation partnership program access network are associated with the quality of service flow identifier.

In one embodiment, a method of a user equipment comprises: establishing a multiaccess data connection with a user plane function in the mobile communication network, wherein the multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network; transmitting a first performance measurement functionality message to the user plane function, wherein the first performance measurement functionality message comprises a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function in the mobile communication network to request a first type of analytics from a network data analytics function; and receiving a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics, wherein the second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

In certain embodiments, the method further comprises applying the estimated round trip time values for determining how to route data traffic via the multiaccess data connection.

In some embodiments, the first set of parameters comprises a cell identifier, a base station set identifier, a reporting period, at least one threshold, or some combination thereof.

In various embodiments, the request for a first type of analytics comprises the quality of service flow identifier and the cell identifier, the base station set identifier, or a combination thereof.

In one embodiment, the first network function comprises the user plane function.

In certain embodiments, the first network function comprises a session management function, and the user plane function transmits a first N4 message to the session management function in response to receiving the first performance measurement functionality message from the user equipment.

In some embodiments, the first type of analytics comprises round trip time analytics for a non-third generation partnership program access network, for a third generation partnership program access network, or a combination thereof.

In various embodiments, the round trip time analytics for the non-third generation partnership program access network, for the third generation partnership program access network, or the combination thereof are associated with the quality of service flow identifier.

In one embodiment, an apparatus comprises a user equipment. The apparatus further comprises: a processor that establishes a multiaccess data connection with a user plane function in a mobile communication network, wherein the multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network; a transmitter that transmits a first performance measurement functionality message to the user plane function, wherein the first performance measurement functionality message comprises a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function in the mobile communication network to request a first type of analytics from a network data analytics function; and a receiver that receives a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics, wherein the second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

In certain embodiments, the processor applies the estimated round trip time values for determining how to route data traffic via the multiaccess data connection.

In one embodiment, a method at a first network function in a mobile communication network comprises: establishing a multiaccess data connection with a user equipment, wherein the multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network; receiving a first message comprising a first set of parameters including a quality of service flow identifier; transmitting a request a first type of analytics to a network data analytics function in response to receiving the first message; and in response to transmitting the request for the first type of analytics, receiving estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

In certain embodiments, the first set of parameters comprises a cell identifier, a base station set identifier, a reporting period, at least one threshold, or some combination thereof.

In some embodiments, the request for a first type of analytics comprises the quality of service flow identifier and the cell identifier, the base station set identifier, or a combination thereof.

In various embodiments, the first network function comprises a user plane function, and the first message is a first performance measurement functionality message transmitted by a user equipment.

In one embodiment, the user plane function transmits a second performance measurement functionality message to the user equipment in response to receiving the estimated round trip time values, and the second performance measurement functionality message contains the estimated round trip time values.

In certain embodiments, the first network function comprises a session management function, and the first message is a first N4 message transmitted by a user plane function in response to the user plane function receiving a first performance measurement functionality message from a user equipment.

In some embodiments, the session management function transmits a second N4 message to the user plane function in response to receiving the estimated round trip time values, the second N4 message contains the estimated round trip time values, the user plane function transmits a second performance measurement functionality message to the user equipment in response to receiving the second N4 message, and the second performance measurement functionality message contains the estimated round trip time values.

In various embodiments, the first type of analytics comprises round trip time analytics for the non-third generation partnership program access network, for the third generation partnership program access network, or a combination thereof.

In one embodiment, the round trip time analytics for the non-third generation partnership program access network and for the third generation partnership program access network are associated with the quality of service flow identifier.

In one embodiment, an apparatus comprises a first network function in a mobile communication network. The apparatus further comprises: a processor that establishes a multiaccess data connection with a user equipment, wherein the multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network; a receiver that receives a first message comprising a first set of parameters including a quality of service flow identifier; and a transmitter that transmits a request a first type of analytics to a network data analytics function in response to receiving the first message; wherein, in response to transmitting the request for the first type of analytics, the receiver receives estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.

Claim 1:
A method (<NUM>) performed by a user equipment (<NUM>, <NUM>) the method comprising:
establishing (<NUM>) a multiaccess data connection with a user plane function (<NUM>) in a mobile communication network, wherein the multiaccess data connection enables data communication via a non-third generation partnership program access network and via a third generation partnership program access network;
transmitting (<NUM>) a first performance measurement functionality message to the user plane function, wherein the first performance measurement functionality message comprises a first set of parameters including a quality of service flow identifier, and the first performance measurement functionality message triggers a first network function (<NUM>, <NUM>) in the mobile communication network to request a first type of analytics from a network data analytics function (<NUM>); and
receiving (<NUM>) a second performance measurement functionality message from the user plane function in response to the network data analytics function providing the first type of analytics, wherein the second performance measurement functionality message contains estimated round trip time values for the non-third generation partnership program access network, the third generation partnership program access network, or a combination thereof.