A method of providing insight in connectivity for a user of a user equipment, ue, as well as a corresponding ue

Abstract

A method of providing insight in connectivity for a user of a User Equipment, UE, wherein said UE is capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network, wherein said method comprises the steps of establishing, by said UE, a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session established when said UE first attaches to the telecommunication network, establishing, by said UE, a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session, associating, by said UE, traffic to said second PDU session and providing, by a said connectivity verification application of said UE, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

Description

[0001] Title

[0002] A method of providing insight in connectivity for a user of a User Equipment, UE, as well as a corresponding UE.

[0003] Technical field

[0004] The present disclosure generally relates to the field of Graphical User Interfaces, GUIs, and, more specifically, to GUIs in the context of User Equipment that are able to support different connectivity types.

[0005] Background

[0006] Currently, all consumer smartphones come preconfigured with only a single PDU Session for Non-CSP usage (e.g. MBB), even though there might be additional sessions like those for the Internet Protocol, IP, Multimedia Subsystem, IMS, they aren't visible or usable for regular applications. However, the introduction of Network Slicing in 3GPP Release 15's 5G Core Network specifications brought about a change. This new concept also brought along the possibility to support multiple PDU Sessions on the User Equipment, UE, side.

[0007] Both enterprises and consumers should have the ability to activate and use extra PDU Sessions alongside the default Mobile Broadband, MBB, PDU Session. To streamline management and provide policies for PDU Session Selection to the UE, the "UE Route Selection Policy" was introduced. Within these UE Route Selection Policy, URSP, rules, there's a section called "Traffic Descriptor" that furnishes the UE with details about the type of traffic that should be associated with the PDU Session described by the URSP rule.

[0008] This Traffic Descriptor can take various forms, such as an Application Descriptor, an IP Descriptor, a Domain Descriptor, Ethernet Descriptors, Connection Capability, or some other descriptor. Additionally, URSP rules include supplementary conditions related to the PDU Session, such as the SSC Mode, specific Time Windows during which the PDU Session can be activated, or location criteria when the PDU Session is geofenced. In the context of Android, support for Network Slicing and URSP rules was introduced in Android 12. Initially, Android 12 allowed the establishment of only a single PDU Session, but with Android 13, it supports multiple simultaneous active PDU Sessions. This enhancement is particularly valuable for Fully Managed Devices, where an enterprise IT administrator defines a set of device policies for accessing enterprisespecific services.

[0009] An example of deploying multiple PDU Sessions demonstrates how URSP rules simplify the description and management of these sessions. Each URSP rule contains parameters that the UE may need to provide when establishing a PDU Session, namely the Data Network Name, DNN, and, in some cases, the Network Slice Selection Identifier, S-NSSAI.

[0010] Furthermore, each URSP rule includes a Traffic Description that allows the UE to match the appropriate URSP rule for a given traffic or application request. While the usage of URSP rules is an important simplification, it is not essential to the present disclosure.

[0011] When a device has established multiple PDU Sessions, it gains more than one IP path to the network.

[0012] The Data Network Name, DNN, plays a role in identifying either the external Data Network to which the PDU Session connects the client or the N6 IP address pool from which the UE obtains an IP address assignment. These different Data Networks can be interconnected within the CSP environment or through the public internet.

[0013] Although not explicitly depicted, the PDU Session Selection function can be an extension of the existing UE routing function. Most smartphones offer both cellular and Wi-Fi connectivity. In today's smartphones, a more fixed route selection is typically implemented, choosing between Wi-Fi and cellular connectivity. These policies are usually determined by the smartphone OEM, with Wi-Fi being the preferred choice when available, often considered a cost-effective option. Smartphones continually check and monitor the availability of public internet connectivity.

[0014] Many applications also offer additional device-user policies. For example, some applications may exclusively use Wi-Fi connectivity. Internet radio apps, for instance, allow users to select Wi-Fi-only usage, and video-on-demand applications like Netflix provide options to download content when connected to Wi-Fi. In summary, the introduction of URSP rules and support for multi-PDU Session setups introduces a greater need for device-side policies, which can be defined by the device user or the subscription owner, particularly in the context of enterprise subscriptions.

[0015] Summary

[0016] The inventors have found that there is currently no GUI or similar notification mechanism to notify the user of a User Equipment, UE, about the selected or available PDU sessions, nor regarding these PDU sessions connection capabilities and usage costs.

[0017] It would therefore be advantageous to achieve a method of providing insights in connectivity for a UE, wherein the UE is capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network.

[0018] The method comprises the step of establishing, by said UE, a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session established when said UE first attaches to the telecommunication network.

[0019] The first PDU session may be known as the "Default PDU Session." This default PDU session is typically used for basic connectivity and services, such as internet access, without any specific quality of service, QoS, requirements.

[0020] The Default PDU Session is the initial and default bearer that may be established for a UE upon attachment to the telecommunication network. It provides the initial connectivity for the UE to access data services. Additional PDU sessions, known as dedicated or secondary PDU sessions, can be established for specific services or applications with different QoS requirements, or traffic treatment policies, as needed.

[0021] The method further comprises a step of establishing, by said UE, a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session.

[0022] In a telecommunication network, for example a 5G telecommunication network, a UE can establish multiple PDU sessions simultaneously. These additional sessions are often referred to as "secondary PDU sessions" or "dedicated PDU sessions."

[0023] Secondary PDU sessions are established to support different services, applications, or quality of service, QoS, requirements. Each secondary PDU session can have its own set of QoS parameters tailored to the specific needs of the service or application.

[0024] For example, a UE might have one secondary PDU session for high- priority real-time video streaming, another secondary PDU Session for general internet browsing, and yet another (e.g. the default PDU Session or another secondary PDU Session) for low-priority background data synchronization.

[0025] Secondary PDU sessions may be useful for optimizing network resources and efficiently managing traffic. Different applications and services have varying QoS requirements, and using separate PDU sessions may allow for better resource allocation.

[0026] They enable the simultaneous use of multiple services with distinct QoS characteristics, ensuring a seamless and reliable user experience. For instance, a UE can engage in a video call while concurrently downloading a large file.

[0027] It is noted that the wording primary and secondary above does not entail or indicate any preference or order. The secondary PDU session may be viewed as an additional PDU session for the UE, for example a purpose specific PDU session.

[0028] The method further comprises the steps of associating, by said UE, traffic to said second PDU session and providing, by a said connectivity verification application of said UE, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

[0029] The inventors have found that it may be useful to inform the user of a User Equipment about the PDU session related information of the established second PDU session, especially in situations wherein the second PDU session is not the so- called default PDU session. The default PDU session may be the first PDU session that is established between the UE and the telecommunication network.

[0030] The advantage of the method described above is that the user of the UE is able to get more insight in the PDU session related information of the established second PDU session. As a first step, the user may be notified that the second PDU session is actually used for the traffic. The user may have initially assumed that the default PDU session was used for the traffic, but the present disclosure enables that the user is informed that the second PDU session is used for the traffic.

[0031] The traffic may, for example, be application specific. That is, only the traffic of a particular application may be tunnelled over the second PDU session. Another option is that traffic with a particular characteristic may be tunnelled over the second PDU session.

[0032] As a second step, the user may be notified with respect to the details of the established second PDU session, i.e. the PDU session related information may comprise details with respect to charging and quality of service or anything alike.

[0033] The PDU session related information of said established second PDU session may relate to the usage costs. For example, PDU sessions in telecommunication networks may come with various usage costs. These costs can typically be categorized into data volume costs and establishment costs.

[0034] Data volume costs are typically associated with the amount of data that is being exchanged. This can be charged on a per-byte basis, where the costs relate to the actual data used, or through flat-rate plans, where the costs relate to a fixed fee for a certain amount of data. If the data limit in flat-rate plans is exceeded, additional charges may apply.

[0035] Establishment costs may relate to the setup and duration of PDU sessions. These might include connection setup costs, incurred when initiating a session, and session duration costs - i.e. based on how long a particular service is used.

[0036] In the context of the present disclosure, the wording PDU session is utilized. It is noted that he PDU Session is typically a logical channel established between the UE and the core network. It is used to carry packets between the UE and the telecommunication network. A PDU Session may be associated with specific Quality of Service, QoS, parameters to ensure a certain level of service quality.

[0037] To ensure secure and efficient transmission of packets, PDU Sessions are typically implemented through tunnels. A tunnel may be considered as a virtual pathway that connects the UE to the telecommunication network. It may encapsulate and route packets between two endpoints, ensuring data integrity and security. In an example of the method in accordance with the present disclosure, the method further comprises the step of: identifying, by said connectivity verification application, that said traffic is not associated to said first PDU session, being said default tunnel session and triggering, by said connectivity verification application, said step of providing based on said identification.

[0038] The selection of a PDU session is often handled as a separate decision within the UE and the telecommunication network. Each PDU session typically corresponds to a specific service or application, and the UE and 5GC work together to establish and manage these sessions based on the service requirements and QoS parameters associated with each session.

[0039] In a telecommunications network, a specific application or service is typically associated with a particular PDU session. This association may be established and managed by the network infrastructure, and it allows for efficient handling of different types of traffic.

[0040] When a user initiates a specific application or service on their UE, the UE and the network infrastructure work together to identify the type of service or application being used. Based on the type of service or application, the network infrastructure initiates the establishment of, or a selection of, a corresponding PDU session. Each PDU session may be uniquely identified by its characteristics, which include QoS Parameters. These parameters define the quality of service requirements for the session, such as data rate, latency, and reliability. Different services may have different QoS requirements, and the network sets up the PDU session accordingly. Each PDU session may be assigned a unique session identifier, allowing the network to differentiate between multiple sessions concurrently active on the same UE. The network may create a session context that includes information about the service, the UE, and the session's QoS parameters. This context is used to manage and route traffic for the session. Once the PDU session is established, or selected, data traffic generated by the specific application or service is routed through the corresponding PDU session. This ensures that the traffic receives the QoS treatment defined for that session. That corresponding PDU session may be considered the default PDU session for the application. In the above described example, the first PDU session is the default PDU session for the traffic.

[0041] As such, a user may typically assume that the traffic, i.e. corresponding to a particular application, may be routed via the default PDU session.

[0042] However, in some cases the traffic may be routed to a different PDU session, for example the second PDU session as explained above. In prior art situations, the user of a UE is not informed about the traffic being routed over a nondefault PDU session.

[0043] The present disclosure enables this particular notification. That is, the user is informed that the traffic is routed over a non-default PDU session.

[0044] The inventors have found that it may be beneficial to provide the PDU session related information only in cases where a non-default PDU session is used for the traffic.

[0045] In a further example, the UE comprises a plurality of User Equipment Route Selection Policy, URSP, rules, wherein each of said plurality of URSP rules provides information on which PDU session said UE should use, and wherein said step of associating comprises: associating, by said UE, traffic to said second PDU session based on matching properties of said traffic with said plurality of URSP rules.

[0046] In a telecommunication network, where a UE has established multiple distinct PDU sessions, the User Equipment Route Selection Policy, URSP, rules may come into play to route data traffic. URSP rules may be preconfigured, or set, on the UE to specify the conditions and actions for traffic routing. Each rule may be designed to determine which PDU session should be utilized for specific types of data traffic. These rules typically involve traffic classification based on factors like destination IP addresses, port numbers, and protocol types.

[0047] Having multiple PDU sessions allows the UE to apply URSP rules to differentiate or separate traffic. For example, URSP rules enable the UE to, for example, route real-time services like video conferencing through one PDU session to guarantee low latency and high quality. Furthermore, URSP rules can enable load balancing by directing less critical or lower-priority traffic through an alternative PDU session to balance network load. This dynamic adaptability of URSP rules ensures that the UE optimally routes traffic, responding to changing network conditions while maintaining connectivity and meeting the diverse requirements of various applications and services.

[0048] In another example, the method further comprises the step of: logging, by said connectivity verification application, usage of said second PDU session.

[0049] The corresponding log file may be made available for alter retrieval or via period upload or anything alike.

[0050] In a further example, the PDU session related information comprises any of: charging scheme related information; ownership of a connectivity over said second PDU session; expected performance of said connectivity over said second PDU session; an indication that a charging rule, deviating from a default charging rule, is applied.

[0051] In another example, the PDU session related information comprises charging scheme related information only.

[0052] In a further example, the PDU session related information comprises PDU session capabilities related information.

[0053] In yet another example, the connectivity verification application is realized as any of: an application or service residing in an Operating System, OS, of said UE;

[0054] OS Level System Service; an Application.

[0055] In the first approach, certain functionality may be embedded within an application or service that operates directly within the UE's operating system, OS. This means that the functionality becomes an integral part of the UE's OS environment. Other applications and services running on the UE can access and utilize this embedded functionality seamlessly. This approach offers a high degree of integration and efficiency within the device's software ecosystem.

[0056] The second approach involves implementing the same functionality as a standalone system service or application that operates independently of other apps and services at the OS level. This means that the functionality is encapsulated within a separate entity that runs on the UE. This approach provides flexibility and modularity, allowing users to choose and install specific applications to access desired functionality.

[0057] The choice between these two approaches depends on various factors, including the specific functionality requirements, the desired level of integration, and the overall software development strategy for the UE. Both approaches offer unique advantages, catering to different use cases and user preferences within the UE's software ecosystem.

[0058] In a further example, the method further comprises the step of: determining, by said connectivity verification application, that a connection over said second PDU session is correctly set-up by interacting, by said connectivity verification application, over said second PDU session, with a connectivity conformation function residing in either a public communication network or in said telecommunication network.

[0059] In yet another example, the method further comprises the step of: transmitting, by said connectivity verification application, a result of said interaction with said connectivity conformation function, to either said telecommunication network of said public communication network.

[0060] In a second aspect of the present disclosure, there is provided a User Equipment, UE, capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network, wherein said UE comprises: a processor arranged for establishing a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session when said UE first attaches to said telecommunication network, said processor further being arranged for establishing a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session, said processor further arranged for associating traffic to said second PDU session; a connectivity verification application arranged for providing, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE. It is noted that the advantages as explained with reference to the first aspect of the present disclosure, being the method of providing insight, are also applicable to the second aspect of the present disclosure, being related to the User Equipment.

[0061] In an example, the connectivity verification application is further arranged for identifying that said traffic is not associated to said first PDU session, being said default tunnel session and triggering said step of providing based on said identification.

[0062] In a further example, the UE comprises a plurality of User Equipment Route Selection Policy, URSP, rules, wherein each of said plurality of URSP rules provides information on which PDU session said UE should use, and wherein said processor is further arranged for associating traffic to said second PDU session, said second PDU session being different from said first PDU session, based on matching properties of said traffic with said plurality of URSP rules.

[0063] In a further example, the connectivity verification application is further arranged for logging usage of said second PDU session.

[0064] In yet another example, the PDU session related information comprises any of: charging scheme related information; ownership of a connectivity over said second PDU session; expected performance of said connectivity over said second PDU session; an indication that a charging rule, deviating from a default charging rule, is applied.

[0065] In an example, the PDU session related information comprises charging scheme related information only.

[0066] In a further example, the PDU session related information comprises PDU session capabilities related information.

[0067] In another example, the connectivity verification application is realized as any of: an application or service residing in an Operating System, OS, of said UE;

[0068] OS Level System Service; an Application.

[0069] In an example, the connectivity verification application is arranged for determining that a connection over said second PDU session is correctly set-up by interacting, over said second PDU session, with a connectivity conformation function residing in either a public communication network or said telecommunication network.

[0070] In another example, the connectivity verification application is further arranged for transmitting a result of said interaction with said connectivity conformation function, to either said telecommunication network of said public communication network

[0071] In a third aspect of the present disclosure, there is provided a computer program product comprising a computer readable medium having instructions stored thereon which, when executed by a User Equipment, UE, in a telecommunication network, cause said UE to implement a method in accordance with any of the examples provided above.

[0072] The present disclosure is described in conjunction with the appended figures. It is emphasized that, in accordance with the standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.

[0073] In the appended figures, similar components and / or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

[0074] The above and other aspects of the disclosure will be apparent from and elucidated with reference to the examples described hereinafter.

[0075] Brief description of the drawings

[0076] Fig. 1 discloses an example deployment of a User Equipment, UE, in a telecommunication network, wherein the UE has multiple PDU sessions simultaneously; Fig. 2 discloses a high level architecture of a UE in combination with a telecommunication network in accordance with the present disclosure;

[0077] Fig. 3 discloses UE behaviour when using a provisioned URSP rule;

[0078] Fig. 4 discloses an example of a method in accordance with the present disclosure;

[0079] Fig. 5 discloses an example of a UE in accordance with the present disclosure.

[0080] Detailed Description

[0081] It is noted that in the description of the figures, same reference numerals refer to the same or similar components performing a same or essentially similar function.

[0082] A more detailed description is made with reference to particular examples, some of which are illustrated in the appended drawings, such that the manner in which the features of the present disclosure may be understood in more detail. It is noted that the drawings only illustrate typical examples and are therefore not to be considered to limit the scope of the subject matter of the claims. The drawings are incorporated for facilitating an understanding of the disclosure and are thus not necessarily drawn to scale. Advantages of the subject matter as claimed will become apparent to those skilled in the art upon reading the description in conjunction with the accompanying drawings.

[0083] The ensuing description above provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment of the disclosure, it being understood that various changes may be made in the function and arrangement of elements, including combinations of features from different embodiments, without departing from the scope of the disclosure.

[0084] Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise," "comprising," and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to." As used herein, the terms "connected," "coupled," or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, electromagnetic, or a combination thereof. Additionally, the words "herein," "above," "below," and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word "or," in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

[0085] These and other changes can be made to the technology in light of the following detailed description. While the description describes certain examples of the technology, and describes the best mode contemplated, no matter how detailed the description appears, the technology can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the technology to the specific examples disclosed in the specification, unless the Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the technology encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the technology under the claims.

[0086] Fig. 1 discloses an example 1 wherein the User Equipment, UE, 2 has established two PDU sessions 3, 4, both with private IP addresses.

[0087] The Data Network Name, DNN, identifies the external Data Network 5, 6 (or N6 Interface to a specific data network) to which the PDU Session connects the client. Or, the DNN identifies the N6 IP address pool, from which the UE gets an IP address assigned. The different Data Networks may be interconnection within the CSP environment or through the public internet. The PDU Session Selection function is not depicted. However, the PDU Session selection function can be an extension of the existing UE routing function: Majority of UEs offer cellular connectivity and WIFI. In today’s UEs, a more hard-wired route selection is realized, i.e. selecting between WIFI connectivity and cellular connectivity. Today’s policies are typically determined by the UEs OEM. Typically, usage of WIFI is preferred, when available. Usage of WIFI is considered “for free”. The UE is checking I monitoring, whether connectivity to the public internet is available.

[0088] Many applications offer some additional device-user policies, e.g. the application can only use WIFI connectivity. For example, several Internet Radio apps allow selection of Wl Fl-only. Video On Demand applications offer a policy to download VOD assets when in WIFI connectivity.

[0089] Generally, with introduction of URSP rules and multi-PDU Session support, there may be a greater need for device side policies, defined by the device user and I or the subscription owner, e.g. enterprise subscriptions.

[0090] The basic idea of the present disclosure is to provide PDU session related information like connectivity charging or connectivity performance related information to a user of a UE, for example via a dedicated device application. This dedicated application, for example the connectivity verification application, may reside within the operating system, may be installed by the enterprise admin (in application space of the UE, i.e. not is OS level space) or by the user.

[0091] Note, this “connectivity verification application” can also be realized as an OS level System Service of by other means.

[0092] This connectivity verification application may indicate to the user, that a non-default PDU Session is selected for particular traffic routing or may provide additional information about which traffic is routed differently. For example, when an enterprise application is launched and the operating system associates the traffic to a different PDU Session, i.e. according to the matching rules of the URSP rules, this dedicated application may be notifying the user about the charging conditions, e.g. the employer is covering the connectivity cost.

[0093] In addition, the connectivity verification application may be logging the non-default PDU session usage. Depending on an application configuration, the connectivity verification application may send a PDU Session usage notification immediately to the enterprise or may make the log file available for later retrieval or periodic upload.

[0094] The dedicated application may also offer performance related information to manage the device user expectation.

[0095] As a first basic check, the connectivity verification session may double check the routing correctness, i.e. is the PDU Session connected to the correct Data Network, e.g. by connecting to a Data Network server, which can only be reached through the given PDU Session, e.g. sending ping using the PDU Session.

[0096] In more advanced cases, the connectivity verification session may capture connectivity performance related metrics, including application specific metrics like video QoE. The captured PDU Session performance metrics, like throughput, RTT I latency, jitter I throughput variation, can be send to a metrics collection server by the enterprise.

[0097] Note, the URSP rules may not contain any details about charging, i.e. increase cost or decreased cost compared to normal connectivity cost. The application may fetch according information from a network service.

[0098] Figure 2 illustrates a high level architecture 21. The majority of functions are contained within the UE 22. The telecommunication network, i.e. the 5G System cloud 23, may contain all necessary functions to provide 5G connectivity services, specifically it includes the UPF, PCF, SMF, AMF, RAN, etc.

[0099] Figure 3 illustrates the UE behaviour between the URSP Rule Provision and activation of a PDU session in multiple steps.

[0100] The UE may be split into three main areas, focusing on connectivity: The application space, the operating system space and the modem space. The operating space is responsible for multi-tenant operations, meaning that different Apps are not influencing each other. The operating system provides, among others, all the needed functions to interact with the screen, e.g. to provide notifications, and to use connectivity. The operating system is also ensuring I enforcing, that an application is “connected” to the authorized PDU Session. This can be secured through routing policies.

[0101] The operating system is also responsible for managing the establishment and usage of the PDU Sessions. A dedicated function, the PDU Session Selection, is responsible here. When multiple PDU Sessions are established, the UE becomes a so-called “multi-homed device”, i.e. the UE has multiple IP paths, each with an own IP address, to interact with one or more data networks. The operating system determines, based on routing policies, which application session is routed to what PDU Session. The routing policies are preferably expressed in form of LIRSP rules.

[0102] For enterprise devices, the UE contains a set of enterprise related policies, for example, a mapping between a dedicated enterprise application and the authorized PDU Session. URSP rules introduce an additional layer of abstraction, i.e. the enterprise IT admin maps enterprise applications to URSP rules, which then allow the operating system to select the correct PDU Session. This abstraction allows, that the PDU Session realization can be dynamically modified, without touching the enterprise application policies.

[0103] The “Connectivity Confirmation Function” may be a Network Function, NF, which allows the UE to check, whether the related connectivity is set up correctly. Specifically, it allows to confirm, whether the PDU Session Selection function has associated the application to the intended PDU Session.

[0104] Fig. 4 discloses an example of a method 51 in accordance with the present disclosure.

[0105] The method is directed to providing insight in connectivity for a user of a User Equipment, UE, wherein said UE is capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network. The telecommunication network may, for example, be a Service Based Architecture, SBA, based telecommunication network. The 5G telecommunication network is an example of such an SBA based telecommunication network.

[0106] The method comprises the step of establishing 52, by said UE, a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session established when said UE first attaches to the telecommunication network.

[0107] The method further comprises the step of establishing 53, by said UE, a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session.

[0108] The method further comprises the steps of associating 54, by said UE, traffic to said second PDU session and providing 55, by a said connectivity verification application of said UE, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

[0109] Fig. 5 discloses an example of a User Equipment, UE, 51 capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network.

[0110] The UE comprises a processor 62 arranged for establishing a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session when said UE first attaches to said telecommunication network, said processor further being arranged for establishing a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session.

[0111] The processor is in direct contact with a memory 63.

[0112] The processor is further arranged for associating traffic to said second PDU session.

[0113] A connectivity verification application 64 is provided and is arranged for providing, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

[0114] The UE further comprises an incoming terminal 66 connected to receiving means 65 and an outgoing terminal 67 connected to transmitting means 68.

[0115] To reduce the number of claims, certain aspects of the technology are presented below in certain claim forms, but the applicant contemplates the various aspects of the technology in any number of claim forms. For example, while some aspect of the technology may be recited as a computer-readable medium claim, other aspects may likewise be embodied as a computer-readable medium claim, or in other forms, such as being embodied in a means-plus-function claim.

[0116] In the description above, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of implementations of the disclosed technology. It will be apparent, however, to one skilled in the art that embodiments of the disclosed technology may be practiced without some of these specific details.

[0117] Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. Any reference signs in the claims should not be construed as limiting the scope thereof.

Claims

CLAIMS1. A method of providing insight in connectivity for a user of a User Equipment, UE, wherein said UE is capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network, wherein said method comprises the steps of: establishing, by said UE, a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session established when said UE first attaches to the telecommunication network; establishing, by said UE, a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session; associating, by said UE, traffic to said second PDU session providing, by a said connectivity verification application of said UE, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

2. A method in accordance with claim 1 , wherein said method further comprises the step of: identifying, by said connectivity verification application, that said traffic is not associated to said first PDU session, being said default tunnel session and triggering, by said connectivity verification application, said step of providing based on said identification.

3. A method in accordance with any of the previous claims, wherein said UE comprises a plurality of User Equipment Route Selection Policy, URSP, rules, wherein each of said plurality of URSP rules provides information on which PDU session (an application of) said UE should use, and wherein said step of associating comprises: associating, by said UE, traffic to said second PDU session based on matching properties of said traffic with said plurality of URSP rules.

4. A method in accordance with any of the previous claims, wherein said method further comprises the step of: logging, by said connectivity verification application, usage of said second PDU session.

5. A method in accordance with any of the previous claims, wherein said PDU session related information comprises any of: charging scheme related information; ownership of a connectivity over said second PDU session; expected performance of said connectivity over said second PDU session; an indication that a charging rule, deviating from a default charging rule, is applied.

6. A method in accordance with claim 5, wherein said PDU session related information comprises charging scheme related information only.

7. A method in accordance with any of the previous claims, wherein said PDU session related information comprises PDU session capabilities related information.

8. A method in accordance with any of the previous claims, wherein said connectivity verification application is realized as any of: an application or service residing in an Operating System, OS, of said UE;OS Level System Service; an Application.

9. A method in accordance with any of the previous claims, wherein said method further comprises the step of: determining, by said connectivity verification application, that a connection over said second PDU session is correctly set-up by interacting, by said connectivity verification application, over said second PDU session, with a connectivityconformation function residing in either a public communication network or in said telecommunication network.

10. A method in accordance with claim 9, wherein said method further comprises the step of: transmitting, by said connectivity verification application, a result of said interaction with said connectivity conformation function, to either said telecommunication network of said public communication network.

11. A User Equipment, UE, capable of having multiple simultaneous Packet Data Unit, PDU, sessions with a telecommunication network, wherein said UE comprises: a processor arranged for establishing a first PDU session between said UE and said telecommunication network, said first PDU session being a default PDU session when said UE first attaches to said telecommunication network, said processor further being arranged for establishing a second PDU session between said UE and said telecommunication network, said second PDU session being different from said first PDU session, said processor further arranged for associating traffic to said second PDU session; a connectivity verification application arranged for providing, via a GUI of said UE, PDU session related information of said established second PDU session to said user of said UE.

12. A UE in accordance with claim 11 , wherein said connectivity verification application is further arranged for identifying that said traffic is not associated to said first PDU session, being said default tunnel session and triggering said step of providing based on said identification.

13. A UE in accordance with any of the claims 11 - 12, wherein said UE comprises a plurality of User Equipment Route Selection Policy, URSP, rules, wherein each of said plurality of URSP rules provides information on which PDU session (an application of) said UE should use, and wherein said processor is further arranged forassociating traffic to said second PDU session, said second PDU session being different from said first PDU session, based on matching properties of said traffic with said plurality of URSP rules.

14. A UE in accordance with any of the claims 11 - 13, wherein said connectivity verification application is further arranged for logging usage of said second PDU session.

15. A UE in accordance with any of the claims 11 - 14, wherein said PDU session related information comprises any of: charging scheme related information; ownership of a connectivity over said second PDU session; expected performance of said connectivity over said second PDU session; an indication that a charging rule, deviating from a default charging rule, is applied.

16. A UE in accordance with claim 15, wherein said PDU session related information comprises charging scheme related information only.

17. A UE in accordance with any of the claims 11 - 16, wherein said PDU session related information comprises PDU session capabilities related information.

18. A UE in accordance with any of the claims 11 - 17, wherein said connectivity verification application is realized as any of: an application or service residing in an Operating System, OS, of said UE;OS Level System Service; an Application.

19. A UE in accordance with any of the claims 11 - 18, wherein said connectivity verification application is arranged for determining that a connection over said second PDU session is correctly set-up by interacting, over said second PDUsession, with a connectivity conformation function residing in either a public communication network or said telecommunication network.

20. A UE in accordance with claim 19, wherein said connectivity verification application is further arranged for transmitting a result of said interaction with said connectivity conformation function, to either said telecommunication network of said public communication network21. A computer program product comprising a computer readable medium having instructions stored thereon which, when executed by a User Equipment, UE, in a telecommunication network, cause said UE to implement a method in accordance with any of the claims 1 - 10.

Images