Method for grouping and prioritizing different pdu sessions in a telecommunication system and system therefor

Abstract

A method for grouping different PDU sessions in a telecommunication system comprising: a user equipment, UE; one or more access networks, AN; a core network, CN; and one or more data networks, DN, the method comprising: providing, by the AN, the UE with access to the CN; providing, by the CN, the UE with connectivity to the one or more data networks, DN; accessing, by the UE, a DN by using different protocol data unit, PDU, sessions established between the UE and the CN via the AN that provide connectivity to one or more DN, each PDU session comprising a PDU session identifier; and signaling, by the CN, to the UE the established PDU sessions via the AN, wherein the established PDU sessions are identified by a PDU session identifier, ID, and at least one PDU session group ID, wherein the PDU session group identifier is a same identifier assigned to one or more different PDU sessions and indicates that said one or more different PDU sessions belong together.

Description

Technical Field

[0001] This invention relates to a method and a telecommunications system for grouping and prioritizing different PDU sessions in a telecommunications system. Background Technology

[0002] In current 5G systems, mobile networks are typically divided into two main parts: the access network (AN) and the core network (CN). Figure 1 An exemplary 5G system is shown, including UE 10, radio access network 20 (RAN), CN 30 and data network 40 (DN) (such as the Internet, for example).

[0003] The primary goal of mobile networks is to provide UEs with connectivity toward the RAN. Currently, to achieve this, UEs communicate with the RAN via a radio interface used to convey both signaling information and data traffic. More specifically, even in the presence of logical separation (logical channels), both types of data are transmitted over the same physical medium.

[0004] Between the RAN and CN, signaling information (the so-called control plane (CP)) and user data (the so-called user plane (UP)) are separated in different interfaces: N1 / N2 and N3 in the 5G scenario, the former runs on the SCTP / NG-AP / NAS protocol stack, while the latter runs on the UDP / GTPU-U protocol stack. This is in Figure 2 As shown in the figure, Figure 2 An exemplary data transmission between UE 10 and DN 40 is explained.

[0005] exist Figure 2 In this configuration, UE 10 connects to the gNB at the RAN via the Uu interface. The gNB connects to the Access and Mobility Management Function (AMF) of CN 30 on the control plane via the N1 / N2 interface. Furthermore, on the user plane, the gNB connects to the User Plane Function (UPF) via the N3 interface. The UPF connects to DN 40 on the user plane via the N6 interface.

[0006] To establish a data connection enabling the UE to communicate with the DN, a PDU session is required. A PDU session is a logical data transmission channel terminated at the CN, providing connectivity to the DN. The termination point of a given PDU session ( Figure 2 In the case of UPF and existing technologies in 5G, this is called PDU Session Anchor (PSA). A PDU session has an associated QoS or QoS set because a PDU session can contain several QoS flows.

[0007] When the UE moves (e.g., during handover), the PSA typically remains constant (hence the term "anchor").

[0008] Figure 3 An example of the PDU session establishment process according to the 3GPP specification is explained. For example... Figure 3 As shown, the PDU session is established by UE 10 via the radio interface. RAN 20 is aware of the PDU session because it needs this information, for example, to allocate physical resources on Uu, but the PDU session is managed by CN 30.

[0009] exist Figure 3 In this process, the UE sends a (S1) PDU session establishment request to the AMF via the gNB through the Uu and N1 / N2 interfaces (see...). Figure 2 ).

[0010] The AMF and UPF exchange (S2A) messages to establish an N3 data path between the gNB and the UPF. Message exchange may involve other network functions (NFs) (e.g., Session Management Function (SMF), Policy Control Function (PCF)). Subsequently, the AMF and gNB exchange (S2B) messages to establish an N3 data path between the gNB and the UPF.

[0011] AMF sends a (S3) PDU session establishment response to UE 1 via gNB.

[0012] Finally, data traffic is exchanged between UE 1 and gNB via the Uu interface (radio) (S4A); between gNB and UPF via the N3 interface (GTP-U tunnel) (S4B); and between UPF and DN 40 via the N6 interface (unencapsulated) (S4C).

[0013] Currently, different PDU sessions are considered independent; that is, a PDU session is not linked to other PDU sessions.

[0014] Technical issues

[0015] However, according to the existing technology, it is not possible to group certain PDU sessions belonging to the UE so that the notification to the access network (AN) and / or core network (CN) of certain PDU sessions, although different (i.e., they are not redundant PDU sessions), must be regarded as a group.

[0016] Specifically, current limitations include, for example, that a PDU session is always associated with a given single network slice selection aid information (S-NSSAI, i.e., “slice ID”) and data network name (DNN). Therefore, connectivity to different DNNs (potentially on different slices) requires several PDU sessions, even if said connectivity is established to support a single application.

[0017] Furthermore, when several QoS flows can exist in a given PDU session, they are all linked to the same PDU session, and thus linked to the same S-NSSAI / DNN.

[0018] In view of the foregoing, the object of the present invention is to provide a method and system for implementing grouping of different PDU sessions. This facilitates the joint consideration of the PDU sessions for system procedures such as mobility, release (e.g., moving / releasing PDU sessions in a linked manner) by other network components (e.g., AN, CN). Summary of the Invention

[0019] The above objectives are achieved through the features of the independent claims.

[0020] According to one aspect of the present invention, a telecommunications system is provided, comprising: a user equipment (UE); one or more access networks (ANs); a core network (CN); and one or more data networks (DNs), wherein the one or more ANs are configured to provide the UE with access to the CN; the CNs are configured to provide connectivity to the one or more data networks (DNs); the UE is configured to access the DNs by using different Protocol Data Unit (PDU) sessions established between the UE and the CNs via the one or more ANs, providing connectivity to the one or more DNs, each PDU session including a PDU session identifier; the CNs are configured to signal to the UE via the one or more ANs the established PDU sessions, wherein the established PDU sessions are identified by a PDU session identifier ID and at least one PDU session group ID, wherein the PDU session group identifier refers to the same identifier assigned to one or more different PDU sessions and indicates that the one or more different PDU sessions belong together.

[0021] According to a preferred aspect, each PDU session may include a priority identifier for identifying the priority of a given PDU session within a given group of PDU sessions.

[0022] According to a preferred aspect, the UE can be configured to request a PDU session by sending a PDU session establishment request message to the CN via one or more ANs. The request includes: a previously received PDU session group ID, or an indication that a new PDU session group ID should be provided by the CN, and optionally, a priority identifier within the PDU session group.

[0023] According to a preferred aspect, the PDU session group ID may further include a relevant PDU session group purpose ID used to identify the use and / or purpose of the PDU session group.

[0024] According to a preferred aspect, the UE can be configured to trigger the release of all PDU sessions within a PDU session group by sending a message to the CN via one or more ANs, the message indicating at least the PDU session group ID and an indication to be released.

[0025] According to a preferred aspect, prior to the establishment of a PDU session, the UE can be configured to register with the CN via one or more ANs, and the UE is configured to notify the CN of its ability to support PDU session groups.

[0026] According to preferred embodiments, the AN can be configured to use PDU session group information to guide UE mobility.

[0027] According to another aspect of the present invention, a method for grouping different PDU sessions in a telecommunications system is provided, the telecommunications system comprising: a user equipment (UE); one or more access networks (ANs); a core network (CN); and one or more data networks (DNs), the method comprising: providing the UE with access to the CN via the one or more ANs; providing the UE with connectivity to the one or more data networks (DNs) via the one or more ANs; the UE accessing the DN by using different Protocol Data Unit (PDU) sessions established between the UE and the CN via the one or more ANs, providing connectivity to the one or more DNs, each PDU session including a PDU session identifier; and the CN signaling to the UE via the one or more ANs the established PDU sessions, wherein the established PDU sessions are identified by a PDU session identifier ID and at least one PDU session group ID, wherein the PDU session group identifier refers to the same identifier assigned to one or more different PDU sessions and indicates that the one or more different PDU sessions are grouped together.

[0028] According to a preferred aspect, each PDU session may include a priority identifier for identifying the priority of a given PDU session within a given group of PDU sessions.

[0029] According to a preferred aspect, the method may further include the UE requesting a PDU session by sending a PDU session establishment request message to the CN via one or more ANs. The request includes: a previously received PDU session group ID, or an indication that a new PDU session group ID should be provided by the CN, and optionally, a priority identifier within the PDU session group.

[0030] According to a preferred aspect, the PDU session group ID may further include a relevant PDU session group purpose ID used to identify the use and / or purpose of the PDU session group.

[0031] According to a preferred aspect, the method may further include: the UE triggering the release of all PDU sessions within the PDU session group by sending a message to the CN via one or more ANs, the message indicating at least the PDU session group ID and an indication to be released.

[0032] According to a preferred aspect, prior to the establishment of a PDU session, the method may further include the UE registering with the CN via one or more ANs, and the UE notifying the CN of its ability to support a group of PDU sessions.

[0033] According to a preferred aspect, the method may further include the one or more ANs using PDU session group information to guide UE mobility.

[0034] Other aspects, features, and advantages will be apparent from the above overview and from the following description (including the drawings and claims).

[0035] Brief description of the attached figures

[0036] In the attached diagram:

[0037] Figure 1 An exemplary 5G system was explained.

[0038] Figure 2 An exemplary data transmission between the UE and DN is explained.

[0039] Figure 3 The process of establishing a sample PDU session according to 3GPP is explained.

[0040] Figure 4 The present invention describes a grouping of several PDU sessions using a PDU session group ID according to an embodiment of the present invention. Detailed Implementation

[0041] According to an embodiment of the present invention, the PDU session establishment process includes adding an indication to the PDU session establishment request that the PDU session is a warp-stacked PDU session; a PDU session group ID; and / or a request for a new PDU session group ID. The indication is considered part of the PDU session establishment request and / or is guided by the network.

[0042] According to an embodiment of the present invention, a telecommunications system includes: a user equipment 10 (UE); one or more access networks 20 (AN); a core network 30 (CN); and one or more data networks 40-1, 40-2, 40-3 (DN).

[0043] AN 20-1 or 20-2 provides UE 10 with access to CN 30. At the same time, CN 30 provides connectivity to one or more DN40-1, 40-2, 40-3.

[0044] UE 10 accesses DNs 40-1, 40-2, and 40-3 by using different Protocol Data Unit (PDU) sessions established between UE 10 and CN 30 via AN 20. Each PDU session provides connectivity to one or more DNs 40-1, 40-2, and 40-3. Furthermore, each PDU session includes a PDU session identifier.

[0045] CN 30 signals the established PDU session to UE 10 via AN 20. The established PDU session is identified by a PDU session identifier (ID) and at least one PDU session group ID.

[0046] In addition, the PDU session group identifier can be the same identifier assigned to one or more different PDU sessions, and indicates that the one or more different PDU sessions belong together.

[0047] Optionally, each PDU session may also include a priority identifier for identifying the priority of a given PDU session within a given group of PDU sessions.

[0048] Optionally, the UE may request a PDU session by sending a PDU session establishment request message to the CN via the AN. In this case, the request may include: a previously received PDU session group ID, or an indication that a new PDU session group ID should be provided by the CN, and optionally, a priority identifier within the PDU session group.

[0049] Optionally, the PDU session group ID may further include a relevant PDU session group purpose ID used to identify the use and / or purpose of the PDU session group.

[0050] Optionally, UE 10 can trigger the release of all PDU sessions within a PDU session group by sending a message to CN 30 via AN 20. For example, the message may include at least the PDU session group ID and an indication to be released.

[0051] Optionally, the UE may register with CN 30 via AN 20 before a PDU session is established. Afterward, the UE may notify CN 30 of its ability to support PDU session groups.

[0052] Optionally, AN 20 may use PDU session group information to guide UE 10 mobility.

[0053] According to the present invention, several advantageous technical effects can be achieved, such as allowing 5GS components (RAN, CN) to be aware of PDU sessions (regardless of the requested QoS level, i.e., latency, packet loss) used for backhauling data belonging to a specific application (e.g., an edge application deployed at the UE). Specifically, for the CN, different PDU sessions can arrive at the CN from different ANs (e.g., private 5G-NR and public terrestrial mobile network (PLMN) 5G-NR or PLMN and / or WiFi). In this case, the CN can be aware of specific PDU sessions belonging to a given UE. This method can be generalized to groups of PDU sessions spanning more than one UE (e.g., applications connected via two separate UEs). On the AN side, it enables the AN to use PDU session group information for, for example, guiding mobility, resource allocation (all PDU sessions scheduled at the same frequency in the group, handover always within the same group, etc.).

[0054] Furthermore, according to the invention, when managing several PDU sessions, they can be considered as a group belonging to the same entity. In typical applications, if one network segment fails, application connectivity will be irreversibly interrupted. Therefore, the network can take this into account when, for example, terminating PDU sessions from the network side. This is an important aspect because in some cases, the network should be aware that certain resource / logical connections will be separated (e.g., for resilience purposes).

[0055] Furthermore, the PDU session group ID (or information also included in the identifier) ​​can indicate the purpose of the group, such as, for example, that the group is used for data backhaul.

[0056] Furthermore, the use of PDU session grouping advantageously allows applications that require different QoS flows and connectivity to different data network names (DNNs) to group PDU sessions (within a DNN, QoS flows can be used within a PDU session).

[0057] Furthermore, a hierarchical structure can be introduced within a PDU session group.

[0058] Furthermore, it can advantageously enable several applications, such as: edge applications deployed at the UE, which require several backhaul connections; vehicle-to-everything (V2X) applications with simultaneous connectivity to several services; and / or relay PDU sessions from similar locations.

[0059] Although the invention has been described and illustrated in detail in the accompanying drawings and the foregoing description, such description and illustration are to be regarded as illustrative or exemplary, and not restrictive. It will be understood that changes and modifications can be made by those skilled in the art within the scope of the appended claims. Specifically, the invention covers further embodiments having any combination of features from the various embodiments described above and below.

[0060] Furthermore, in the claims, the word "a" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude the plural. A single unit can perform the function of several features recited in the claims. Specifically, terms related to attributes or values, such as "substantially," "about," and "approximately," precisely define the attribute or precisely define the value, respectively. Any reference numerals in the claims should not be construed as limiting the scope.

Claims

1. A telecommunications system, comprising: User Equipment (10) UE; One or more access networks (20)AN; Core network (30) CN; and one or more data networks (40-1, 40-2, 40-3) DNs, wherein: The one or more ANs (20) are configured to provide the UE (10) with access to the CN (30); The CN (30) is configured to provide connectivity to the one or more data networks (40-1, 40-2, 40-3) DN; The UE (10) is configured to access the DN (40-1, 40-2, 40-3) by using different Protocol Data Unit (PDU) sessions established between the UE (10) and the CN (30) via the one or more ANs (20), providing connectivity to the one or more DNs (40-1, 40-2, 40-3), each PDU session including a PDU session identifier; The CN (30) is configured to signal to the UE (10) via the one or more ANs (20) an established PDU session, wherein the established PDU session is identified by a PDU session identifier ID and at least one PDU session group ID. The PDU session group identifier refers to the same identifier assigned to two or more different PDU sessions belonging to the UE and transmitting different data, and indicates that the two or more different PDU sessions should be jointly considered for system mobility and release system procedures. The UE (10) is configured to request a PDU session by sending a PDU session establishment request message to the CN (30) via one or more ANs, the request including: Previously received PDU session group ID, or The new PDU session group ID should be indicated by the CN (30).

2. The telecommunications system of claim 1, wherein each PDU session includes a priority identifier for identifying the priority of a given PDU session within a given group of PDU sessions.

3. The telecommunications system of claim 1, wherein the PDU session group ID further includes a related PDU session group destination ID for identifying the use of the PDU session group.

4. The telecommunications system of claim 1, wherein the PDU session group ID further includes a related PDU session group destination ID for identifying the purpose of the PDU session group.

5. The telecommunications system of claim 1, wherein the PDU session group ID further includes a related PDU session group destination ID for identifying the use and purpose of the PDU session group.

6. The telecommunications system of claim 1, wherein the PDU session ID includes the PDU session group ID.

7. The telecommunications system of claim 1, wherein the UE (10) is configured to trigger the release of all PDU sessions within a PDU session group by sending a message to the CN (30) via one or more ANs (20), the message indicating at least the PDU session group ID and an indication to be released.

8. The telecommunications system of claim 1, wherein prior to the establishment of the PDU session, the UE (10) is configured to register with the CN (30) via the one or more ANs (20), and the UE (10) is configured to notify the CN (30) of the UE (10)'s ability to support PDU session groups.

9. The telecommunications system of claim 1, wherein one or more ANs (20) are configured to use PDU session group information to guide the mobility of UE (10).

10. The telecommunications system of claim 1, wherein a PDU session assigned a given PDU session group ID is assigned to two or more UEs.

11. A method for grouping different PDU sessions belonging to a User Equipment (UE) and transmitting different data in a telecommunications system, said telecommunications system comprising: User Equipment (UE); One or more access networks (ANs); Core network CN; and one or more data networks (DNs), the method includes: The one or more ANs provide the UE with access to the CN; The CN provides connectivity to the UE to the one or more data networks DN; The UE accesses the DN by using different Protocol Data Unit (PDU) sessions established between the UE and the CN via one or more ANs, providing connectivity to one or more DNs, each PDU session including a PDU session identifier; and The CN signals the established PDU session to the UE via one or more ANs, wherein the established PDU session is identified by a PDU session identifier ID and at least one PDU session group ID. The PDU session group identifier refers to the same identifier assigned to two or more different PDU sessions belonging to the UE and transmitting different data, and indicates that the two or more different PDU sessions should be jointly considered for system mobility and release system procedures. The method further includes: The UE requests a PDU session by sending a PDU session establishment request message to the CN via one or more ANs, the request including: Previously received PDU session group ID, or The new PDU session group ID should be indicated by the CN.

12. The method of claim 11, wherein each PDU session includes a priority identifier for identifying the priority of a given PDU session within a given group of PDU sessions.

13. The method of claim 11, wherein the PDU session group ID further includes a related PDU session group destination ID for identifying the use of the PDU session group.

14. The method of claim 11, wherein the PDU session group ID further includes a related PDU session group destination ID for identifying the purpose of the PDU session group.

15. The method of claim 11, wherein the PDU session group ID further includes a related PDU session group purpose ID for identifying the use and purpose of the PDU session group.

16. The method of claim 11, wherein the PDU session ID includes the PDU session group ID.

17. The method of claim 11, further comprising: The UE triggers the release of all PDU sessions within the PDU session group by sending a message to the CN via one or more ANs, the message indicating at least the PDU session group ID and an indication to be released.

18. The method of claim 11, wherein prior to the establishment of the PDU session, the method comprises: The UE registers with the CN via one or more ANs; as well as The UE notifies the CN of its ability to support PDU session groups.

19. The method of claim 11, further comprising: The AN or one AN uses PDU session group information to guide UE mobility.

Images