Method and apparatus for managing data sessions in home routing session offload mode

Abstract

The invention relates to a method and apparatus for managing data sessions in a home routing session offload mode. Techniques for managing data sessions in a home routing (HR) session offload (SBO) mode in a wireless communication system are provided. For example, a method for managing data sessions in an HR-SBO mode includes providing, by a home session management function (H-SMF) of a home network, information about how to affect traffic routing for data sessions served by a visited network to a visited session management function (V-SMF) of a visited network; and configuring, by the V-SMF, at least a user plane (UP) function based on the information on how traffic routing for the data session is affected.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system. More particularly, the present disclosure relates to methods and apparatuses for managing data sessions in a home routing (HR) session splitting offload (SBO) mode for roaming user equipment (UE) and a network in a wireless communication system. Background Art

[0002] Various embodiments relate to considerations in a (e.g., mobile / wireless) communication system or network (such as a 5G / NR system and next generation systems beyond 5G). For example, various embodiments are applicable to 3GPP standardized mobile / wireless communication systems or networks prior to Release 18.

[0003] A wireless communication system (such as 5G) may support a roaming service for a home routing (HR) user equipment (UE) (referred to as an HR roaming service). In the case of HR, data traffic in a visited network (VPLMN) may be routed to a data network through a home network (HPLM). To apply an edge computing service to a roaming UE, an HR session may be split offload to a local data network in which an edge computing server of the visited network is installed. A specific process related to splitting offload an HR session in the visited network may be required.

[0004] List of Acronyms and Abbreviations

[0005] The following acronyms and abbreviations are used throughout the present disclosure:

[0006] C-DNS Central DNS

[0007] C-NEF Central NEF

[0008] C-PSA UPF Central PSA UPF

[0009] EAS Edge Application Server

[0010] EASDF Edge Application Server Discovery Function

[0011] ECS Edge Configuration Server

[0012] EDC Edge DNS Client

[0013] EEC Edge Enabler Client

[0014] EES Edge Enabler Server

[0015] EHE Edge Hosting Environment

[0016] L-DN Local Part of DN

[0017] L-DNS Local DNS

[0018] L-NEF Local NEF

[0019] L-PSA UPF Local PSA UPF

[0020] HR-SBO Home Routing Session Breakout Summary of the Invention

[0021] The object of the present disclosure is to provide a mechanism for managing data sessions in a home routing (HR) session breakout (SBO) mode in a wireless communication system. A method and apparatus for managing data sessions in a home routing (HR) session breakout (SBO) mode are provided.

[0022] According to some aspects, the current content of the independent claims is provided. Some further aspects are defined in the dependent claims.

[0023] According to a first aspect of the present disclosure, a method for managing data sessions in a home routing (HR) session breakout (SBO) mode is provided. The method may be performed by one or more nodes in a wireless communication system. The method includes: providing, by a home session management function (H-SMF) of a home network, information on how to affect the traffic routing for a data session served by a visited network, to a visited session management function (V-SMF) of the visited network; and configuring, by the V-SMF, at least a user plane (UP) function based on the received information on how to affect the traffic routing for the data session.

[0024] In some examples of the first aspect, the method may further include: determining, by the H-SMF, information on how to affect the traffic routing for the data session, based on one or more policy and charging control (PCC) rules received from a home policy control function (H-PCF) of the home network.

[0025] In some examples of the first aspect, the method may further include: receiving, by the H-PCF, a request from an application function (AF) to affect the traffic of the data session; generating, by the H-PCF, one or more PCC rules based on the request; and providing, by the H-PCF, one or more PCC rules to the H-SMF.

[0026] In some examples of the first aspect, the method may further include: receiving, by a home network exposure function (H-NEF) of the home network, a request from the AF to affect the traffic of the data session; storing / updating in / removing from a unified data repository (UDR) information on how to affect the traffic routing for the data session, by the H-NEF; and sending, by the UDR, a notification of an update of the information on how to affect the traffic routing for the data session, to the H-PCF of the data session.

[0027] In some examples of the first aspect, the method may further include: an H-NEF looking up an H-PCF for a data session to authorize a request that affects the service for the data session. In some examples, the looking up may include using a Binding Support Function (BSF) to look up the H-PCF.

[0028] In some examples of the first aspect, the request that affects the service may be received by the H-PCF directly from the AF.

[0029] In some examples of the first aspect, the information on how to affect the service routing for a data session may include a request received from an Application Function (AF) that affects the service for the data session.

[0030] In some examples of the first aspect, the information on how to affect the service routing for a data session includes a subscription request for notifications of any user plane management events received from an Application Function (AF).

[0031] In some examples of the first aspect, the information on how to affect the service routing for a data session may include one or more of the following: information for identifying the service, information on one or more Data Network Access Identifiers (DNAIs) of the visited network, an indication of service relevance, an indication of application relocation possibility, an indication of address reservation for the user equipment, and a request to be notified when the UP path of the data session has changed.

[0032] In some examples of the first aspect, the information on how to affect the service routing for a data session may further include, per DNAI, a service steering policy identifier and / or service routing information related to the interface between a User Plane Function (UPF) and a Data Network (DN).

[0033] In some examples of the first aspect, providing the information on how to affect the service routing for a data session from the H-SMF to the V-SMF may further include using the interface between the H-SMF and the V-SMF to provide the information on how to affect the service routing for a data session.

[0034] In some examples of the first aspect, providing the information on how to affect the service routing for a data session from the H-SMF to the V-SMF may include the H-SMF sending a Session Management (SM) message or SM context including information elements or containers to the V-SMF to provide the information on how to affect the service routing for a data session.

[0035] In some examples of the first aspect, the method may further include the H-SMF providing the V-SMF with offloading rules or information on how the visited network should affect the traffic routing for the data session.

[0036] In some examples of the first aspect, the method may further include: the H-SMF mapping the parameters affecting the traffic requests for the data session from one or more PCC rules to the parameters to be exchanged between the H-SMF and the V-SMF, and the H-SMF providing the mapped parameters to the V-SMF in a session management (SM) message; and extending the SM message or context with the parameters affecting the traffic requests for the data session that are not mapped to existing parameters.

[0037] In some examples of the first aspect, the H-SMF providing the V-SMF with information on how to affect the traffic routing for the data session may include the H-SMF providing the V-SMF with notification endpoint information, which the V-SMF uses to send a notification to the application function (AF) via the home network.

[0038] In some examples of the first aspect, the method may further include: the H-SMF receiving a request for notification of an event on the data session, the request including notification endpoint information associated with the AF or with the home network exposure function (H-NEF) of the home network, the request from the AF being received via the H-NEF; and the H-SMF providing an indication to the V-SMF that the provided notification endpoint information is notification endpoint information associated with the AF or with the H-NEF. In some examples, the indication may be provided when the H-SMF does not provide itself as the notification endpoint information.

[0039] In some examples of the first aspect, the method may further include: the V-SMF sending a notification using the notification endpoint information to the H-SMF; and the H-SMF forwarding the notification to the AF.

[0040] In some examples of the first aspect, the method may further include: receiving, by an H-SMF, a notification request regarding an event on a data session, the request including notification endpoint information associated with an AF or with a home network exposure function (H-NEF) of a home network; associating, by the H-SMF, the notification endpoint information associated with the H-SMF with the received notification endpoint information; storing, by the H-SMF, an association between the notification endpoint information associated with the H-SMF and the received notification endpoint information; providing, by the H-SMF, the notification endpoint information associated with the H-SMF to a V-SMF as notification endpoint information for the V-SMF to use to send a notification regarding an event on a data session to the AF; receiving, by the H-SMF, a notification sent using the notification endpoint information associated with the H-SMF from the V-SMF; obtaining, by the H-SMF, notification endpoint information for the H-SMF to use to forward a notification regarding an event based on the association; and forwarding, by the H-SMF, a notification regarding an event to the AF using the obtained notification endpoint information.

[0041] According to a second aspect of the present disclosure, there is provided a network node (e.g., a home session management function (H-SMF)) or an apparatus in such a network node. The network node or apparatus may be located in a home network of a wireless communication system. The network node or apparatus according to the second aspect includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the instructions cause the network node or apparatus to: provide information to a visited session management function (V-SMF) of a visited network regarding how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network, and the information regarding how to affect the traffic routing for the data session is used by the V-SMF to configure at least a user plane (UP) function.

[0042] In some examples of the second aspect, when the instructions are executed by the at least one processor, the instructions may further cause the network node or apparatus to determine the information regarding how to affect the traffic routing for a data session based on one or more policy and charging control (PCC) rules received from a home policy control function (H-PCF) of the home network.

[0043] In some examples of the second aspect, when the instructions are executed by the at least one processor, the instructions may further cause the network node or apparatus to receive from the H-PCF one or more PCC rules generated based on a request from an application function (AF) to affect the traffic of a data session.

[0044] In some examples of the second aspect, the information regarding how to affect the traffic routing for a data session may include a request received from an application function (AF) to affect the traffic of the data session.

[0045] In some examples of the second aspect, the information on how to affect the service routing for a data session includes one or more of the following: information for identifying a service, information on one or more data network access identifiers (DNAIs) of a visited network, an indication of service relevance, an indication of application relocation possibility, an indication of address reservation of a user equipment, a request to be notified when the UP path of the data session has changed.

[0046] In some examples of the second aspect, the information on how to affect the service routing for a data session may further include, per DNAI, a service steering policy identifier and / or service routing information related to the interface between a user plane function (UPF) and a data network (DN).

[0047] In some examples of the second aspect, when instructions are executed by at least one processor, the instructions may further cause a network node or device to use the interface between an H-SMF and a V-SMF to provide information on how to affect the service routing for a data session.

[0048] In some examples of the second aspect, when instructions are executed by at least one processor, the instructions may further cause a network node or device to send a session management (SM) message or SM context including an information element or container to the V-SMF to provide information on how to affect the service routing for a data session.

[0049] In some examples of the second aspect, when instructions are executed by at least one processor, the instructions may further cause a network node or device to provide offloading rules or information to the V-SMF on how the visited network should affect the service routing for a data session.

[0050] In some examples of the second aspect, when instructions are executed by at least one processor, the instructions may further cause a network node or device to map parameters of a request affecting the service for a data session from one or more PCC rules to parameters to be exchanged between the H-SMF and the V-SMF, and provide the mapped parameters to the V-SMF in a session management message; and extend the session management message or context with parameters of the request affecting the service for a data session that are not mapped to existing parameters.

[0051] In some examples of the second aspect, when instructions are executed by at least one processor, the instructions may further cause a network node or device to provide notification endpoint information to the V-SMF, which is used by the V-SMF to send a notification to an application function (AF) via a home network.

[0052] In some examples of the second aspect, when instructions are executed using at least one processor, the instructions may further cause a network node or device to receive a notification request regarding an event on a data session, the request including notification endpoint information associated with an AF or notification endpoint information associated with a home network exposure function (H-NEF) of the home network, the request from the AF being received via the H-NEF; and provide an indication to the V-SMF that the provided notification endpoint information is notification endpoint information associated with the AF or notification endpoint information associated with the H-NEF when the H-SMF does not offer itself as notification endpoint information.

[0053] In some examples of the second aspect, when instructions are executed using at least one processor, the instructions may further cause a network node or device to receive a notification using notification endpoint information from the V-SMF; and forward the notification to the AF.

[0054] In some examples of the second aspect, when instructions are executed using at least one processor, the instructions may further cause a network node or device to: receive a notification request regarding an event on a data session, the request including notification endpoint information associated with an AF or associated with a home network exposure function (H-NEF) of the home network; associate notification endpoint information associated with the H-SMF with the received notification endpoint information; store the association between the notification endpoint information associated with the H-SMF and the received notification endpoint information; provide the notification endpoint information associated with the H-SMF to the V-SMF as notification endpoint information for the V-SMF to use to send a notification regarding an event on the data session to the AF; receive a notification sent using the notification endpoint information associated with the H-SMF from the V-SMF; obtain notification endpoint information for the H-SMF to use to forward a notification regarding the event based on the association; and forward a notification regarding the event to the AF using the obtained notification endpoint information.

[0055] According to a third aspect of the present disclosure, a home subscriber session management function (H-SMF) in a home network is provided. The H-SMF includes: a communication interface; and at least one processor coupled to the communication interface. The at least one processor is configured to provide information to a visited session management function (V-SMF) of a visited network regarding how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network, and the information regarding how to affect the traffic routing for the data session is used by the V-SMF to configure at least a user plane (UP) function.

[0056] In some examples of the third aspect, at least one processor of the H-SMF may further be configured to perform one or more examples according to the second aspect.

[0057] According to a fourth aspect of the present disclosure, there is provided a network node (e.g., a home session management function (H-SMF)) or an apparatus in such a network node. The network node or apparatus may be located in a home network of a wireless communication system. The network node or apparatus according to the fourth aspect includes circuitry for providing information to a visited session management function (V-SMF) of a visited network on how to affect the traffic routing of a data session in a home routed (HR) session break-out (SBO) mode served by the visited network, and the information on how to affect the traffic routing for the data session is used by the V-SMF to configure at least a user plane (UP) function.

[0058] In some examples of the fourth aspect, the network node or apparatus may further include circuitry for performing one or more examples according to the second aspect.

[0059] According to a fifth aspect of the present disclosure, there is provided a network node (e.g., a home session management function (H-SMF)) or an apparatus in such a network node. The network node or apparatus may be located in a home network of a wireless communication system. The network node or apparatus according to the fifth aspect includes components or modules for providing information to a visited session management function (V-SMF) of a visited network on how to affect the traffic routing of a data session in a home routed (HR) session break-out (SBO) mode served by the visited network, and the information on how to affect the traffic routing for the data session is used by the V-SMF to configure at least a user plane (UP) function.

[0060] In some examples of the fifth aspect, the network node or apparatus may further include components or modules for performing one or more examples according to the second aspect.

[0061] According to a sixth aspect of the present disclosure, there is provided a method performed by a home session management function (H-SMF) in a home network. The method includes: providing information to a visited session management function (V-SMF) of a visited network on how to affect the traffic routing of a data session in a home routed (HR) session break-out (SBO) mode served by the visited network, and the information on how to affect the traffic routing for the data session is used by the V-SMF to configure at least a user plane (UP) function.

[0062] In some examples of the sixth aspect, the method may further include performing operations according to one or more examples of the second aspect.

[0063] According to a seventh aspect of the present disclosure, a network node (e.g., an access session management function (V-SMF)) or a device in such a network node is provided. The network node or device may be located in a visited network of a wireless communication system. The network node or device according to the seventh aspect includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the instructions cause the network node or device to: receive information from a home session management function (H-SMF) of a home network regarding how to affect the traffic routing of a data session in a home routed (HR) session splitting offload (SBO) mode served by the visited network; and configure at least a user plane (UP) function based on the received information regarding how to affect the traffic routing for the data session.

[0064] In some examples of the seventh aspect, the information regarding how to affect the traffic routing for the data session may include a request received from an application function (AF) to affect the traffic for the data session.

[0065] In some examples of the seventh aspect, the information regarding how to affect the traffic routing for the data session may include one or more of the following: information for identifying the traffic, information regarding one or more data network access identifiers (DNAIs) of the visited network, an indication of traffic relevance, an indication of application relocation possibility, an indication of address reservation for a user equipment, and a request to be notified when the UP path of the data session has changed.

[0066] In some examples of the seventh aspect, the information regarding how to affect the traffic routing for the data session may further include, per DNAI, a traffic steering policy identifier and / or traffic routing information related to an interface between a user plane function (UPF) and a data network (DN).

[0067] In some examples of the seventh aspect, when the instructions are executed by the at least one processor, the instructions may further cause the network node or device to receive, using an interface between the H-SMF and the V-SMF, information from the H-SMF regarding how to affect the traffic routing for the data session.

[0068] In some examples of the seventh aspect, when the instructions are executed by the at least one processor, the instructions may further cause the network node or device to receive from the H-SMF a session management (SM) message or SM context including information elements or containers to provide information regarding how to affect the traffic routing for the data session.

[0069] In some examples of the seventh aspect, when the instructions are executed by the at least one processor, the instructions may further cause the network node or device to receive from the H-SMF offload rules or information regarding how the visited network should affect the traffic routing for the data session.

[0070] In some examples of the seventh aspect, when the instructions are executed using at least one processor, the instructions may further cause the network node or device to: receive notification endpoint information from the H-SMF; and use the notification endpoint information to send a notification to an application function (AF) via the home network.

[0071] In some examples of the seventh aspect, when the instructions are executed using at least one processor, the instructions may further cause the network node or device to receive an indication that the notification endpoint information received from the H-SMF is notification endpoint information associated with the AF or notification endpoint information associated with a home network exposure function (H-NEF) of the home network.

[0072] In some examples of the seventh aspect, when the instructions are executed using at least one processor, the instructions may further cause the network node or device to send a notification to the H-SMF using the notification endpoint information.

[0073] According to an eighth aspect of the present disclosure, a visited session management function (V-SMF) in a visited network is provided. The V-SMF includes: a communication interface; and at least one processor coupled to the communication interface. The at least one processor is configured to: receive information from a home session management function (H-SMF) of a home network on how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network; and configure at least a user plane (UP) function based on the received information on how to affect the traffic routing for the data session.

[0074] In some examples of the eighth aspect, at least one processor of the V-SMF may also be configured to perform one or more examples according to the seventh aspect.

[0075] According to a ninth aspect of the present disclosure, a network node (e.g., a visited session management function (V-SMF)) or a device in such a network node is provided. The network node or device may be located in a visited network of a wireless communication system. The network node or device according to the ninth aspect includes circuitry for: receiving information from a home session management function (H-SMF) of a home network on how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network; and configuring at least a user plane (UP) function based on the received information on how to affect the traffic routing for the data session.

[0076] In some examples of the ninth aspect, the network node or device may further include circuitry for performing one or more examples according to the seventh aspect.

[0077] According to an eleventh aspect of the present disclosure, there is provided a network node (e.g., a visited session management function (V-SMF)) or a device in such a network node. The network node or device may be located in a visited network of a wireless communication system. The network node or device according to the eleventh aspect includes components or modules for performing the following operations: receiving information from a home session management function (H-SMF) of a home network on how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network; and configuring at least a user plane (UP) function based on the received information on how to affect the traffic routing for the data session.

[0078] In some examples of the eleventh aspect, the network node or device may further include components or modules for performing one or more examples according to the seventh aspect.

[0079] According to a twelfth aspect of the present disclosure, there is provided a method performed by a visited session management function (V-SMF) in a visited network. The method includes: receiving information from a home session management function (H-SMF) of a home network on how to affect the traffic routing of a data session in a home routed (HR) session breakout (SBO) mode served by the visited network; and configuring at least a user plane (UP) function based on the received information on how to affect the traffic routing for the data session.

[0080] In some examples of the twelfth aspect, the method may further include performing operations according to one or more examples of the seventh aspect.

[0081] According to a thirteenth aspect of the present disclosure, a computer program product includes program instructions stored on a computer-readable medium that, when executed on a computer, perform the steps of any of the examples of the methods according to the first, sixth, and twelfth aspects as outlined above.

[0082] According to a fourteenth aspect of the present disclosure, a non-transitory computer-readable medium contains computer-executable instructions that, when run on one or more processors, perform the steps of any of the examples of the methods according to the first, sixth, and twelfth aspects as outlined above.

[0083] The above aspects and features may be implemented in a system, device, method, article, and / or non-transitory computer-readable medium depending on the desired configuration. The present disclosure may be implemented in and / or used with a variety of different types of devices, including but not limited to any of a cellular phone, a tablet computer, a wearable computing device, a portable media player, and various other computing devices.

[0084] The present invention content aims to provide a brief overview of some of the aspects and features according to the present disclosure. Thus, it will be recognized that the above features are merely examples and should not be construed as narrowing the scope of the present disclosure in any way. Other features, aspects, and advantages of the present disclosure will become apparent from the following detailed description, drawings, and claims. Description of the Drawings

[0085] A better understanding of the present disclosure can be obtained when considering the following detailed description of various embodiments in conjunction with the following drawings, in which:

[0086] Figure 1 is a schematic diagram of an example of a (mobile / wireless) communication system or network according to an embodiment of the present disclosure;

[0087] Figure 2 is a schematic diagram of an example wireless device or entity according to an embodiment of the present disclosure;

[0088] Figure 3 is a schematic diagram of an example network node or entity according to an embodiment of the present disclosure;

[0089] Figure 4 is a diagram illustrating the system architecture of a fifth-generation (5G) system supporting edge computing according to an embodiment of the present disclosure.

[0090] Figure 5 is a diagram illustrating the 5G system architecture of an edge application server (EAS) for accessing edge computing services operating in a visited network in an HR roaming scenario according to an embodiment of the present disclosure;

[0091] Figure 6 is a flowchart of a method or process for managing a data session in HR-SBO mode according to an embodiment of the present disclosure;

[0092] Figure 7 is an exemplary message sequence diagram of a method or process for managing a data session in HR-SBO mode according to an embodiment of the present disclosure;

[0093] Figure 8 is another exemplary message sequence diagram of a method or process for managing a data session in HR-SBO mode according to an embodiment of the present disclosure; and

[0094] Figure 9 is yet another exemplary message sequence diagram of a method or process for managing a data session in HR-SBO mode according to an embodiment of the present disclosure. Detailed Description

[0095] The examples and embodiments described below represent information that enables those skilled in the art to practice the present disclosure. After reading the following description in view of the figures of the drawings, those skilled in the art will understand the described concepts and will recognize applications of these concepts that are not specifically recited herein. It should be understood that these concepts and applications fall within the scope of the description.

[0096] In the following description, numerous specific details are set forth. However, it should be understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of the description. Using the included description, a person of ordinary skill in the art will be able to implement appropriate functionality without undue experimentation.

[0097] References in the specification to "one embodiment", "an embodiment", "example embodiment", etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that one of ordinary skill in the art can implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0098] Note that the detailed description sometimes refers to one or more specifications that are used as non-limiting and illustrative examples of certain architectures, network configurations, and system deployments. More specifically, the detailed description refers to the 3GPP standards, which are used as non-limiting and illustrative examples. Thus, the various embodiments provided herein may specifically adopt terms that are directly related to them. Such terms are used only in the context of non-limiting and illustrative examples and are not intended to limit the various embodiments in any way. Instead, any other system configuration or deployment may be utilized while complying with what is described herein and / or the various embodiments applicable thereto.

[0099] For example, the various embodiments are applicable in any (e.g., mobile / wireless) communication system (such as 5G / NR systems and next-generation systems beyond 5G). For example, the various embodiments are applicable in 3GPP standardized mobile / wireless communication systems prior to Release 18.

[0100] In the following, several variants and / or alternatives are used to describe the various embodiments. Generally, it should be noted that all the described variants and / or alternatives may be provided individually or in any conceivable combination (e.g., also including combinations of the individual features of these various variants and / or alternatives) according to certain implementations or constraints.

[0101] As used herein, the terms "comprising" and "including" should be understood not to limit an embodiment to only the features that have been mentioned, and an embodiment may also particularly include features, structures, units, modules, etc. that have not been specifically mentioned.

[0102] As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar expressions, such as "one or more of the following", where the list of two or more elements is connected by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0103] As used herein, according to various embodiments, any operation of sending or receiving may include an actual transmission or communication operation, i.e., sending or transmitting an associated message or signal, but may additionally or alternatively include relevant processing operations, i.e., preparing / generating / issuing an associated message or signal before sending, and / or obtaining / disposing / processing an associated message or signal after receiving. For example, sending a message at / by an entity may include generating / issuing, and / or sending / transmitting the message or corresponding signal in / at / by the entity, and receiving a message at / by an entity may include obtaining / disposing, and / or processing the message or corresponding signal in / at / by the entity. As used herein, a message may refer to and / or cover any kind of corresponding information, signal, etc.

[0104] In the figures, it should be noted that the lines / arrows interconnecting individual blocks or entities generally aim to illustrate the operational coupling between them, which can be a physical and / or logical coupling, which on the one hand is independent of the implementation (e.g., wired or wireless), and on the other hand may also include any number of intermediate functional blocks or entities not shown. In a flowchart or sequence diagram, the illustrated order of operations or actions is generally non - restrictive and illustrative, and any other order of corresponding operations or actions can be envisioned if feasible.

[0105] Before explaining various embodiments in detail, reference Figures 1 to 5 is made to briefly explain some general principles of a (mobile / wireless) communication system or network to help understand the technology on which the described embodiments are based.

[0106] Figure 1 An example of a (mobile / wireless) communication system or network 100 according to an embodiment of the present disclosure is illustrated. Figure 1 The embodiment of the communication system or network 100 shown is for illustrative purposes only. Other embodiments of the communication system or network 100 may be used without departing from the scope of the present disclosure.

[0107] As shown Figure 1 in, the communication system or network 100 includes wireless devices or entities, such as UEs 110 (three exemplary UEs 110A - 110C are illustrated Figure 1 in), and includes network nodes or entities, such as radio access nodes 120 (two exemplary radio access nodes 120A - 120B are illustrated Figure 1 in), which are connected to one or more network nodes or entities 130 via an interconnect network 125 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network). UEs 110 within the coverage area 115 can each be capable of directly communicating with radio access nodes 120 via a wireless interface. Radio access nodes 120 can also be referred to as eNBs, gNBs, etc., and communicate with each other via the interconnect network 125.

[0108] As an example, UE 110A can communicate with radio access node 120A via a wireless interface. That is, UE 110A can send wireless signals to radio access node 120A and / or receive wireless signals from radio access node 120A. The wireless signals can include voice services, data services, control signals, and / or any other suitable information.

[0109] As used herein, the term "user equipment" (UE) has the full scope of its ordinary meaning and can refer to any type of wireless device or entity that can communicate with network nodes or entities, and / or with another UE in a cellular or mobile or wireless / mobile communication system. Depending on the network type, examples of UEs include target devices, D2D UEs, machine type UEs or UEs capable of machine - to - machine (M2M) communication, personal digital assistants, tablets, mobile terminals, smart phones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, ProSe UEs, vehicle - to - vehicle (V2V) UEs, V2X UEs, MTC UEs, eMTC UEs, FeMTC UEs, UE Cat0, UE Cat Ml, narrowband IoT (NB - IoT) UEs, UE Cat NB1, etc.

[0110] As described in more detail below, one or more of the UEs 110 include circuitry, programming, or a combination thereof for efficient network management in an advanced wireless communication system. Embodiments of the UE will be described in more detail below with reference to Figure 2 more specifically.

[0111] In some embodiments, the wireless signal coverage area 115 associated with the radio access node 120 may be referred to as a cell. However, particularly with respect to fifth generation (5G) / New Radio (NR) mobile communication concepts, beams may be used instead of cells, and thus, it is important to note that the concepts described herein apply equally to both cells and beams.

[0112] With respect to a beam-based mobile communication system, the radio access node 120 (base station) may transmit beamformed signals to the UE 110 in one or more transmission directions (transmission beams, Tx beams). The UE 110 may receive beamformed signals from the base station 120 in one or more reception directions (reception beams, Rx beams). The UE 110 may also transmit beamformed signals to the base station 120 in one or more directions, and the base station 120 may receive beamformed signals from the UE 110 in one or more directions. The base station 120 and the UE 110 may determine the optimal reception and transmission directions for each base station / UE pair in the base station / UE pair, for example, optimal in the sense that these directions result in the highest link quality or satisfy other quality conditions in the most appropriate manner.

[0113] The interconnected network 125 may refer to any interconnected system capable of sending audio, video, signals, data, messages, etc., or any combination of the foregoing. The interconnected network 125 may include a public switched telephone network (PSTN), public or private data networks, local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), local, regional, or global communication or computer networks (such as the Internet), wired or wireless networks, enterprise intranets, or any other suitable communication link, including combinations thereof.

[0114] In some embodiments, the network node 130 may be a core network node that manages the establishment of communication sessions for the UE 110 and various other functions. Examples of the network node 130 may include a mobile switching center (MSC), MME, serving gateway (SGW), packet data network gateway (PGW), operations and maintenance (O&M), operation support system (OSS), SON, positioning node (e.g., enhanced serving mobile location center, E-SMLC), location server node, MDT node, etc. The UE 110 may exchange certain signals with the network node 130 using the non-access stratum (NAS). In non-access stratum signaling, the signals between the UE 110 and the network node 130 may be transparently passed through the radio access network. In some embodiments, the radio access node 120 may interface with one or more network nodes 130 through an inter-node interface.

[0115] As used herein, the term "network node or entity" has the full scope of its ordinary meaning and can correspond to any type of radio access node (or radio network node) or any network node, such as a base station (BS), which provides wireless access to a cellular or mobile or wireless communication system and can communicate with a UE and / or with another network node in the cellular or mobile or wireless communication system. Depending on the network type, examples of a base station (BS) include a transmit point (TP), a transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femto cell, a Wi-Fi access point (AP), or other wireless-enabled devices. A base station can provide wireless access according to one or more wireless communication protocols, for example, 5G 3GPP new radio interface / access (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), High-Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.

[0116] As described in more detail below, one or more of the network nodes (such as radio access node 120) include circuitry, programming, or a combination thereof for efficient network management in an advanced wireless communication system. This will be described below with respect to Figure 3 Embodiments of the network node will be described in more detail.

[0117] In some embodiments, radio access node 120 can be a distributed radio access node. The components of radio access node 120 and its associated functions can be separated into two main units (or sub-radio network nodes), which can be referred to as a central unit (CU) and a distributed unit (DU). Different distributed radio network node architectures are possible. For example, in some architectures, the DU can be connected to the CU via a dedicated wired or wireless link (e.g., an optical fiber cable), while in other architectures, the DU can be connected to the CU via a transport network. Additionally, how the various functions of radio access node 120 are separated between the (one or more) CUs and the (one or more) DUs may vary depending on the selected architecture.

[0118] An exemplary wireless communication system is an architecture standardized by the 3rd Generation Partnership Project (3GPP). The latest 3GPP-based development is generally referred to as Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) Radio Access Technology (RAT). The various development stages of 3GPP specifications are referred to as releases. The more recent developments of LTE are generally referred to as LTE-Advanced (LTE-A). LTE (LTE-A) employs a radio access architecture called the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and a core network called the Evolved Packet Core (EPC). The base stations of such a system are called evolved or enhanced Node Bs (eNBs), and provide E-UTRAN functions to communication devices, such as user plane packet data convergence / radio link control / media access control / physical layer protocol (PDCP / RLC / MAC / PHY) and control plane radio resource control (RRC) protocol termination. Other examples of RATs include those provided by base stations of systems based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). Base stations can provide coverage for an entire cell or similar radio service area. Core network elements include the Mobility Management Entity (MME), Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW).

[0119] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR may be similar to that of LTE-A. The base stations of an NR system may be called Next Generation Node Bs (gNBs). Changes to the network architecture can depend on the need to support various radio technologies and finer Quality of Service (QoS) support, as well as some on-demand requirements for QoS levels to support Quality of Experience (QoE) from the user perspective. Additionally, network-aware services and applications, and service- and application-aware networks can bring about changes to the architecture. These are related to Information-Centric Networking (ICN) and User-Centric Content Delivery Network (UC-CDN) scenarios. NR can use multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller sites and perhaps also employing various radio technologies for better coverage and enhanced data rates.

[0120] Future networks can utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be manipulated, connected, or chained together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines that run instructions using standard or general - type servers instead of custom hardware. Cloud computing or data storage can also be utilized. In radio communications, this can mean that node operations are at least partially performed in a server, host, or node that is operationally coupled to a remote radio head operation. Node operations will also likely be distributed among multiple servers, nodes, or hosts. It should also be understood that the labor distribution between core network operations and base station operations may be different from or even non - existent as in the case of LTE.

[0121] An example 5G Core Network (CN) includes functional entities. The CN is connected to a UE via a Radio Access Network (RAN). A User Plane Function (UPF) whose role is called PSA (PDU Session Anchor) can be responsible for forwarding frames back and forth between a DN (Data Network) and a tunnel established via 5G, the tunnel being towards the UE that exchanges traffic with the Data Network (DN). The UPF is controlled by a Session Management Function (SMF) that receives policies from a Policy Control Function (PCF). The CN can also include an Access and Mobility Function (AMF).

[0122] Generally, all concepts disclosed herein can be applied to different communication networks, including but not limited to LTE, LTE - A, 5G, 5G Advanced, 6G, and other future or already implemented networks.

[0123] Figure 2 is a schematic diagram of an example wireless device (e.g., Figure 1 the UE 110 shown in

[0124] UE 110 can include one or more of at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In certain embodiments, the transceiver 210 facilitates sending wireless signals to and receiving wireless signals from a radio access node 120 (e.g., via (multiple) transmitters (Tx), (multiple) receivers (Rx), and (multiple) antennas). The processor 220 executes instructions to provide some or all of the functions described herein provided by the wireless device / entity or UE, and the memory 230 stores the instructions executed by the processor 220. In some embodiments, the processor 220 and the memory 230 form a processing circuit system.

[0125] The processor 220 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of a wireless device or entity, such as the functions of the UE 110 described herein. In some embodiments, the processor 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), and / or other logic.

[0126] The memory 230 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by the processor 220. Examples of the memory 230 include computer memory (e.g., random access memory (RAM) or read only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processor 220 of the UE 110. For example, the memory 230 includes instructions that cause the processor 220 to perform processing according to any of the corresponding methods described herein.

[0127] The network interface 240 is communicatively coupled to the processor 220 and may refer to any suitable device operable to receive input for the UE 110, transmit output from the UE 110, perform suitable processing on the input or output or both, communicate with other devices, or any combination thereof. The network interface 240 may include appropriate hardware (e.g., ports, modems, network interface cards, etc.) and software that includes protocol conversion and data processing capabilities to communicate over a network.

[0128] Other embodiments of the UE 110 may include Figure 2 additional components other than those shown in, which may be responsible for providing certain aspects of the functionality of the wireless device, including any of the functions described herein and / or any additional functions (including any functions necessary to support the mechanisms according to the present disclosure). By way of example, the UE 110 may include input devices and circuitry, output devices, and one or more synchronization units or circuitry, which may be part of the processor 220. The input devices include mechanisms for entering data into the UE 110. For example, the input devices may include input mechanisms such as microphones, input elements, displays, etc. The output devices may include mechanisms for outputting data in audio, video, and / or hard copy format. For example, the output devices may include speakers, displays, etc.

[0129] In some embodiments, the wireless device UE 110 may include a series of modules configured to implement the functions of the wireless device described herein.

[0130] It should be understood that the various modules may be implemented as a combination of hardware and software, for example, Figure 2 the processor, memory, and (multiple) transceivers of the UE 110 shown in. Some embodiments may also include additional modules to support additional and / or optional functions.

[0131] Figure 3 is a schematic diagram of an example radio access node 120, or network node or entity 130, according to an embodiment of the present disclosure.

[0132] The radio access node 120, or network node or entity 130, may include one or more of at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In some embodiments, the transceiver 310 facilitates sending wireless signals to and receiving wireless signals from wireless devices (such as UE 110) (e.g., via (multiple) transmitters (Tx), (multiple) receivers (Rx), and (multiple) antennas). The processor 320 executes instructions to provide some or all of the functions described herein as provided by the radio access node 120, or network node or entity 130, and the memory 330 stores the instructions executed by the processor 320. In some embodiments, the processor 320 and the memory 330 form a processing circuit system. The network interface 340 may transmit signals to backend network components such as gateways, switches, routers, the Internet, the public switched telephone network (PSTN), core network nodes, or radio network controllers, etc.

[0133] The processor 320 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of the radio access node 120, or network node or entity 130, such as the functions described herein. In some embodiments, the processor 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), and / or other logic.

[0134] Memory 330 is generally operable to store instructions, such as computer programs, software, applications including one or more of logic, rules, algorithms, code, tables, etc., and / or other instructions executable by processor 320. Examples of memory 330 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device that stores information. For example, memory 330 includes instructions that cause processor 320 to perform processing according to any of the corresponding methods described herein.

[0135] In certain embodiments, network interface 340 is communicatively coupled to processor 320 and may refer to any suitable device operable to receive inputs for radio access node 120, or network node or entity 130, send outputs from radio access node 120, or network node or entity 130, perform suitable processing on the inputs or outputs or both, communicate with other devices, or any combination of the foregoing. Network interface 340 may include appropriate hardware (e.g., ports, modems, network interface cards, etc.) and software that includes protocol conversion and data processing capabilities to communicate over a network.

[0136] Other embodiments of radio access node 120, or network node or entity 130 may include Figure 3 additional components other than those shown in, which may be responsible for providing certain aspects of the functionality of the node, including any of the functionality described herein and / or any additional functionality (including any functionality necessary to support the solutions described herein). Various different types of radio access nodes or network nodes may include components having the same physical hardware but (e.g., via programming) configured to support different radio access technologies, or may represent partially different or completely different physical components.

[0137] Similar to those described with respect to Figure 3 processors, interfaces, and memories may be included in other nodes or entities (such as UE 110, radio access node 120, etc.). Other nodes or entities may optionally include or not include a wireless interface (such as the transceiver described in Figure 3 .

[0138] In certain embodiments, radio access node 120, or network node or entity 130 may include a series of modules configured to implement the functionality of radio access node 120, or network node or entity 130 described herein.

[0139] It should be understood that various modules can be implemented as a combination of hardware and software. For example, Figure 3 the processors, memories, and (multiple) transceivers of the radio access node 120 or the network node or entity 130 as shown. Some embodiments may also include additional modules to support additional functions and / or optional functions.

[0140] 3GPP has proposed edge computing as a technology to allow services of operators and / or third parties to be hosted close to the access point (such as a BS), reducing the end-to-end latency and load in the network and thus enabling efficient service provisioning. In edge computing technology, the data processing time can be shortened by processing the generated data in real time at the UE at a short distance from the site without sending the data to the central cloud network (hereinafter referred to as the "central cloud") where the data is generated. For example, edge computing technology can be applied to technical fields such as autonomous vehicles, which require fast processing in various situations that may occur during driving.

[0141] Edge computing is a concept of a network architecture that enables cloud computing functions and service environments, and the network for edge computing can be deployed close to the UE. Compared with the cloud environment, edge computing can provide benefits such as reduced latency, increased bandwidth, reduced backhaul traffic, and new service prospects. The 5G or post-sixth-generation (6G) core network (CN) proposed by 3GPP can expose network information and functions to edge computing applications (hereinafter referred to as edge applications). In mobile edge computing, the UE can establish a data connection with an edge data network (EDN) close to its location to use low-latency or broadband services, and access an edge application server (EAS) operating in an edge-hosted environment or an edge computing platform operated by an edge enabler server (EES) of the EDN to use data services.

[0142] The 5G system has been enhanced by 3GPP to support edge computing. For example, in 3GPP TS23.548 (e.g., version v18.4.0), the entire content of which is incorporated herein by reference.

[0143] Figure 4 is a diagram illustrating the system architecture of a fifth-generation (5G) system supporting edge computing according to an embodiment of the present disclosure. The illustrated architecture may include various network functions (NFs) depending on the system implementation.

[0144] Reference Figure 4, the network structure of the 5G system 400 may include various network entities. For example, the 5G system 400 may include at least one of an Authentication Server Function (AUSF) 408, (Core) AMF 403, SMF 405, PCF 406, Application Function (AF) 407, Unified Data Management (UDM) 409, Data Network (DN) 410, Network Exposure Function (NEF) 413, Edge Application Service Domain Repository (EDR) 415, Edge Application Server (EAS) 414, EAS Discovery Function (EASDF) 412, User Plane Function (UPF) 404, Radio Access Network (RAN) 402, or UE 401.

[0145] In embodiments of the present disclosure, the NF may support the following functions:

[0146] The AUSF 408 may process and store data for authenticating the UE 401.

[0147] The AMF 403 may provide functions for UE-based access and mobility management, and one UE may be substantially coupled to one AMF. For example, the AMF 403 may support inter-CN node signaling for mobility between 3GPP access networks, termination of the RAN control plane (CP) interface (e.g., the N2 interface), termination of non-access stratum (NAS) signaling (the N1 interface), NAS encryption and integrity protection, access stratum (AS) security control, registration management (registration area management), connection management, idle mode UE reachability (including control and execution of paging retransmission), mobility management control (subscription and policy), support for intra-system mobility and inter-system mobility, support for network slicing, SMF selection, lawful interception (for AMF events and interfaces to the L1 system), delivery of session management (SM) messages between the UE 401 and the SMF 405, transparent proxy for routing of session management (SM) messages, access authentication, access authorization including roaming authorization check, security anchor function (SAF), and / or security context management (SCM). Some or all of the functions of the AMF 403 may be supported in a single instance of the AMF. In a home routing (HR) scenario (or what is referred to as a roaming scenario), the visited AMF (V-AMF) may refer to the AMF of the visited network of a subscriber (e.g., UE401), and the home AMF (H-AMF) may refer to the AMF of the home network of the subscriber.

[0148] The DN 410 may mean, for example, operator services, Internet access, or third-party services. The DN 410 may send downlink (DL) protocol data units (PDUs) to the UPF 404 or receive PDUs sent by the UE 401 from the UPF 404.

[0149] The PCF 406 can receive information about packet flows from an application server (e.g., AF 407) and provide functions for determining policies, such as mobility management or SM. In an embodiment of the present disclosure, the PCF 406 can support functions such as support for a unified policy framework for controlling network behavior, pre - configuration of policy rules so that one or more control plane functions (e.g., AMF 403 or SMF 405) can enforce the policy rules, or implementation of a front - end for accessing relevant subscription information in the User Data Repository (UDR) for policy making.

[0150] The SMF 405 provides session management functions, and when the UE 401 has multiple sessions, each session can be managed by a different SMF. In an embodiment of the present disclosure, the SMF 405 can support functions such as: session management (e.g., session establishment, modification, and release, including maintenance of tunnels between the UPF 404 and the RAN 402), UE Internet Protocol (IP) address allocation and management (optionally including authentication), selection and control of user plane (UP) functions, traffic steering configuration for routing traffic to an appropriate destination at the UPF 404, termination of interfaces towards the PCF, execution of the control part of policies and Quality of Service (QoS), lawful interception (for SM events and the interface to the LI system), termination of the SM part of NAS messages, DL data notification, AN - specific SM information initiator (sent to the RAN 402 via the SMF 403 on N2), determination of the SSC mode of a session, or roaming. Some or all of the functions of the SMF 405 can be supported in a single instance of the SMF.

[0151] The UDM 409 can store subscription data and / or policy data of a user (e.g., UE 401). The UDM 409 can include two parts, namely, an Application Front - End (FE) (not shown) and a UDR (not shown).

[0152] The FE can include a UDM FE responsible for location management, subscription management, or credentials and a PCF responsible for policy control. The UDR can store data required for the functions provided by the UDM FE and policy configuration files required by the PCF. The data stored in the UDR can include policy data and user subscription data, which includes subscription identifier (ID), security credentials, access, and mobility - related subscription data, and / or session - related subscription data. The UDM FE can support functions such as accessing subscription information stored in the UDR, authentication credential processing, user identity processing, access authentication, registration / mobility management, subscription management, or session management.

[0153] The UPF 404 can forward the DL PDU received from the DN 410 to the UE 401 via the RAN 402, and forward the uplink (UL) PDCU received from the UE 401 to the DN 410 via the RAN 402. In an embodiment of the present disclosure, the UPF 404 may support functions such as: an anchor for in-radio access technology (RAT) / inter-radio access technology (RAT) mobility (e.g., PDU session anchor (PSA)), an external PDU session point for interconnecting with data networks, packet routing and forwarding, the user plane part of packet inspection and policy rule enforcement, lawful interception, traffic usage reporting, a UL classifier for supporting routing traffic flows to data networks, a branch point (BP) for supporting multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, and UL / DL rate enforcement), UL traffic authentication (service data flow (SDF) to QoS flow mapping), transport-level packet marking in UL and DL, or DL packet buffering and DL data notification triggering. Some or all of the functions of the UPF 404 may be supported in a single instance of the UPF.

[0154] The AF 407 can interact with the 3GPP CN to provide services (e.g., support the following: application impact on traffic routing, access network capability exposure, and interaction with the policy framework for policy control).

[0155] The RAN 402 can generally refer to a radio access network that supports at least one of an evolved version of the 4G RAT, evolved UMTS terrestrial radio access (E-UTRA), or a new RAT (New Radio (NR)) (e.g., gNB). The gNB can support functions such as: functions for radio resource management (radio bearer control, radio access control, connection mobility control, dynamic allocation of resources to the UE in both UL and DL (i.e., scheduling)), IP header compression, encryption and integrity protection of user data streams, selection of the AMF when attaching the UE when no route to the AMF is determined based on the information provided by the UE, routing of user plane data towards the (one or more) UPFs, routing of control plane information towards the AMF, connection establishment and release, scheduling and transmission of paging messages (originating from the AMF), scheduling and transmission of system broadcast information (originating from operation and maintenance (OAM)), configuration of measurements and measurement reports for mobility and scheduling, transport-level packet tagging in the UL, SM, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in the inactive mode, distribution function for NAS messages, radio access network sharing, dual connectivity, or tight interworking between NR and E-UTRA. The (R)AN can also correspond to a non-3GPP access network that corresponds to the N3IWF (for untrusted non-3GPP access to the 3GPP core network), the TNGF (for trusted non-3GPP access to the 3GPP core network), or the W-AGF (for wired access to the 3GPP core network). The considered 3GPP network can correspond to a PLMN or an SNPN (standalone non-public network).

[0156] The UE 401 can refer to a user equipment. The UE can be referred to as a terminal, a mobile device (ME), a mobile station (MS), etc. For example, the UE can be a portable device such as a laptop computer, a mobile phone, a personal digital assistant (PDA), a smart phone, a multimedia device, etc., or can be a non-portable device such as a personal computer (PC) or an in-vehicle device.

[0157] The NEF 413 can provide a way to securely expose the services and capabilities provided by 3GPP network functions, e.g., including third parties, internal exposure / re-exposure, application functions, and / or edge computing. The NEF 413 can receive information from the (one or more) other NFs (based on the (one or more) exposed capabilities of the (one or more) other NFs). The NEF 413 can store the received information as structured data using a standardized interface to the UDR. The stored information can be "re-exposed" by the NEF 413 to the (one or more) other NFs and the (one or more) AFs, or used for other purposes such as analysis.

[0158] The EASDF 412 can add, on a per fully qualified domain name (FQDN) basis, the address of the domain name service (DNS) server to which the DNS queries of the UE 401 are to be forwarded, and the DNS extension mechanism (EDNS) client subnet (ECS) option, which can be represented as an IP subnet address to be added when forwarding the DNS queries of the UE 401. The EASDF 412 can receive EAS domain configuration information from the EDR 413 and process the DNS query messages received from the UE (e.g., UE 401) according to the received information. The EASDF 412 can receive the UE IP address, the location information of the UE 401 in 3GPP, the DNS message processing rules, and the DNS message reporting rules from the SMF 405, process the DNS query messages received from the UE 401 and the DNS response messages received from the DNS server, and send the information within the DNS messages and the statistical information obtained by processing this information to the SMF 405.

[0159] Although Figure 4 the reference model illustrates the case where the UE 401 accesses a DN 410 through one PDU session, the embodiments of the present disclosure are not limited thereto.

[0160] The UE 401 can use multiple PDU sessions to simultaneously access two data networks (e.g., a local DN and a central DN). In this case, two SMFs can be selected for different PDU sessions. In the embodiments of the present disclosure, each SMF can have the ability to control both the local UPF and the central UPF within the PDU session.

[0161] The UE 401 can simultaneously access two data networks (e.g., a local DN and a central DN) provided in a single PDU session.

[0162] In the 3GPP system, the conceptual links between connected NFs are defined as reference points. For example, Figure 4 the (multiple) reference points included in the 5G system 400 are as follows.

[0163] N1: The reference point between the UE 401 and the AMF 403

[0164] N2: The reference point between the RAN 402 and the AMF 403

[0165] N3: The reference point between the RAN 402 and the UPF 404

[0166] N4: The reference point between the SMF 405 and the UPF 404

[0167] N5: The reference point between the PCF 406 and the AF 407

[0168] N6: Reference point between UPF 404 and DN 410

[0169] N7: Reference point between SMF 405 and PCF 406

[0170] N8: Reference point between UDM 409 and AMF 403

[0171] N9: Reference point between two core UPFs 404

[0172] N10: Reference point between UDM 409 and SMF 405

[0173] N11: Reference point between AMF 403 and SMF 405

[0174] N12: Reference point between AMF 403 and AUSF 408

[0175] N13: Reference point between UDM 409 and AUSF 408

[0176] N14: Reference point between two AMFs 403

[0177] N15: Reference point between PCF and AMF in a non-roaming scenario, and reference point between PCF and AMF in the visited network in a roaming scenario

[0178] Nx: Reference point between EASDF 412 and another NF (e.g., SMF 405)

[0179] Figure 5 FIG. is a diagram showing a 5G system architecture for an edge application server (EAS) to access edge computing services operated in a visited network in an HR roaming scenario according to an embodiment of the present disclosure.

[0180] Reference Figure 5 , the visited network 510, which can be identified as a visited public land mobile network (VPLMN), may include AMF 503-2 (e.g., Figure 4 AMF 403 shown in Figure 4 ), SMF (also referred to as visited SMF, V-SMF) 505-2 (e.g., Figure 4 SMF 405 shown in Figure 4at least one of the EASDF 412) shown in, or a DNS server (also referred to as the visited DNS server; not shown).

[0181] AMF 503-2 may reside in the visited network 510. In an embodiment of the present disclosure, AMF 503-2 may receive and store a home routing (HR) session breakout (SBO) permission indication from the UDM 509-1 in the home network 520 (e.g., Figure 4 the UDM 409 shown in) during the registration process of the UE 501 (e.g., Figure 4 the UE 401 shown in). AMF 503-2 may identify a request for a data network name / single network slice selection assistance information (DNN / S-NSSAI) sent by the UE 501 during the PDU session creation process, and send the HR-SBO permission indication to the V-SMF 505-2. In an embodiment of the present disclosure, AMF 503-2 may send the address and / or ID of the SMF (also referred to as the home SMF, H-SMF) 505-1 in the home network 520 (e.g., Figure 4 the SMF 405 shown in) together with the request for the HR session.

[0182] V-SMF 505-2 may perform tunnel management for the UPF 504-1 (also referred to as the home UPF, H-UPF) in the home network 520 through the V-UPF (not shown). V-SMF 505-2 may determine the SBO (UL classifier (ULCL) / BP) in the visited network 510, and manage the UP session for the local PDU session anchor (L-PSA) UPF 504-2a, UPF 504-2b, and the V-UPF (not shown) via N4. V-SMF 505-2 may notify the H-SMF 505-1 that an add / change / delete event for the local UPF (e.g., H-UPF) has been performed by sending an HR-SBO indication.

[0183] The V-SMF 505-2 can manage the sessions of the UE 501 in the visited network 510. When the UE 501 requests PDU session establishment, the V-SMF 505-2 can receive a PDU session establishment request from the AMF 503-2. The V-SMF 505-2 can receive from the AMF 503-2 a request including HR-SBO and the ID / address of the H-SMF 505-1. When the V-SMF 505-2 is able to receive from the AMF 503-2 an HR-SBO permission indication, the session is an HR session, and the V-SMF 505-2 has received the ID / IP address of the H-SMF 505-1 from the AMF 503-2, the V-SMF 505-2 can send an HR session establishment request to the H-SMF 505-1. An indication to request the pre-provisioning of HR-SBO and / or an indication indicating support for the HR-SBO function can be sent to the H-SMF 505-1 in the HR session establishment request. The V-SMF505-2 can send the address of the V-EASDF 512-2 (the address of the visited DNS server (V-DNS server)) to the H-SMF 505-1. The V-SMF 505-2 can notify the H-SMF 505-1 of the routing rules for the local data network (LDN).

[0184] In an embodiment of the present disclosure, the V-SMF 505-2 can determine the addition / change / removal of the ULCL / BP UPF (e.g., UPF 504-2a) and the L-PSA UPF (e.g., UPF 504-2a). When the V-SMF 505-2 determines to add the ULCL / BP UPF504-2a, it can report the network address of the LDN to be forwarded to the L-PSA UPF 504-2b to the H-SMF 505-1. The H-SMF 505-1 identified as the home PLMN in the home network 520 is responsible for the packet forwarding of the HR session.

[0185] The V-UPF (not shown) can act as an anchor within the visited network 510, perform DL data packet buffering for the UE 501 in the idle state, and perform packet forwarding to the H-UPF 504-1 via the N9 tunnel. The V-UPF (not shown) can support the functions of the ULCL / BP UPF 504-2a or the L-PSA UPF 504-2b together. For example, the V-UPF (not shown) can be arranged in a separated form including the ULCL / BP UPF 504-2a and the L-PSA UPF 504-2b.

[0186] The L-PSA UPF 504-2b can be used as a local PSA UPF, connected to the LDN via N6, and forward packets sent to the EAS514-2 / packets received from the EAS 514-2.

[0187] The ULCL / BP UPF 504-2a can perform the PDU branching function. The ULCL / BP UPF 504-2a can receive packet forwarding rules corresponding to ULCL from the V-SMF505-2, and branch and forward the packets received from the UE 501 to the V-UPF (not shown) based on the destination address of the UE 501 and / or the IPv6 prefix of the UE 501.

[0188] In embodiments of the present disclosure, according to a specific implementation model, the following co-locations may be possible:

[0189] - Co-location of the ULCL / BP UPF and the V-UPF

[0190] - Co-location of the L-PSA UPF and the V-UPF

[0191] - Co-location of the ULCL / BP UPF, the L-PSA UPF, and the V-UPF

[0192] The V-EASDF 512-2 can perform the EAS discovery function in the visited network 510. The V-EASDF 512-2 located in the visited network 510 can be connected to the V-SMF 505-2. The V-EASDF 512-2 can receive DNS message handling rules for session level and node level from the V-SMF 505-2. When a PDU session is created or changed, the address of the V-EASDF 512-2 can be used as the DNS address sent to the UE 501 in the protocol configuration option (PCO). The home DNS server address can be sent by the V-SMF505-2 to the V-EASDF 512-2 through the message handling rules for DNS queries, and used as the DNS server address to which the V-EASDF 512-2 will forward the DNS queries sent by the UE 501 that has not been registered to the local network, so that the DNS queries are sent to the DNS server of the home network 520 for resolving the IP address of the FQDN included in the DNS queries. Alternatively, the home DNS server address can be used as the default DNS server address. The V-EASDF 512-2 can be located in the LDN. In embodiments of the present disclosure, the V-UPF (not shown) and the V-EASDF 512-2 can be co-located.

[0193] The home network 520 may include at least one of UDM 509-1, home PCF (H-PCF) 506-1, H-SMF 505-1, H-UPF 504-1, or a home DNS server (not shown), NEF (also referred to as home NEF, H-NEF) 513-1 (e.g., Figure 4 the NEF 413 shown in Figure 4 ), and serves an AF (also referred to as home AF, H-AF) 507-1 (e.g.,

[0194] the AF 407 shown in

[0195] ). The H-PCF 506-1 may be the PCF of the home network 520 and determine the policy for the HR session. The H-PCF 506-1 may receive a report of the AF request received from the AF 507-1 by the NEF 513-1 of the home network 520 through the UDR (not shown), receive the AF-impacted traffic routing policy, and the H-SMF 505-2 may determine the SBO policy based on the AF-impacted traffic routing policy received from the H-PCF 506-1.

[0196] The UDM 509-1 may record whether HR-SBO is allowed for each DNN / S-NSSAI of the UE according to the roaming pre-agreement between PLMNs. The UDM 509-1 is the NF that indicates whether HR-SBO is allowed to the AMF 503-2 by the visited network 510 of the UE 501 during registration.

[0197] The H-SMF 505-1 may receive the SM-related context from the UDM 509-1 and determine whether to support HR-SBO. When the H-SMF 505-1 allows HR-SBO, the H-SMF 505-1 may send a HR-SBO permission confirmation indication to the V-SMF 505-2. The DNS server address of the PCO message sent to the UE 501 is set to the address of the V-EASDF 512-2 provided by the V-SMF 505-2. The H-SMF 505-1 may send a raw data collection request to the V-SMF 505-2 to collect raw data for charging. The V-SMF 505-2 may collect usage data from the V-UPF (not shown) by using the usage reporting rule (URR).

[0198] UE 501 exchanges 5G control plane messages with AMF 503-2. UE 501 can access EAS 514-2 via the UPF on the user plane through a PDU session. UE 501 can receive the DNS server address from V-SMF 505-1. UE 501 can send a DNS query to the DNS server address.

[0199] In an embodiment of the present disclosure, the AMF (e.g., AMF 503-2) can operate as follows: The AMF can obtain HR roaming session policy configuration information (e.g., including an HR roaming session policy indication indicating a policy decision controlled by the VPLMN or a policy decision controlled by the HPLMN) from the UDM (e.g., UDM 509-1), consider this information to select an SMF (e.g., V-SMF 505-2), and send the HR roaming session policy configuration information to the SMF.

[0200] In an embodiment of the present disclosure, H-SMF 505-1 can obtain SM policy information related to HR roaming SBO from H-PCF 506-1, determine information on how to affect the traffic routing of data sessions (e.g., PDU sessions) in the HR-SBO mode served by the VPLMN, and deliver the information on how to affect the traffic routing for PDU sessions in the HR-SBO mode to V-SMF (e.g., V-SMF 505-2), and then this V-SMF can configure the (multiple) UPFs serving the PDU session in the VPLMN. For example, the V-SMF can configure the (multiple) UPFs based on the information obtained from H-SMF 505-1, using corresponding N4 rules related to the UP path configuration (e.g., including the configuration of ULCL and the local V-PSA UPF).

[0201] Therefore, as Figure 5 illustrated, during roaming, UE 501 establishes a home routing session based on the subscription that can support session splitting in the visited network 510. In this scenario, the home network 520 and the visited network 510 reach an agreement on supporting local traffic routing in the visited network 510 for the home routing session (i.e., session splitting performed by V-SMF 505-2, also known as HR-SBO).

[0202] After establishing the HR-SBO PDU session, UE 501 can access the EAS deployed in the edge hosting environment (EHE) in the visited network 510, while UE 501 can also access the data network (DN) in the home network 520.

[0203] In reference Figures 6 to 9And before describing the method for managing a data session in a Home Routing (HR) Session BreakOut (SBO) mode (i.e., in an HR-SBO scenario) according to an embodiment of the present disclosure, some background information and aspects related to the present disclosure will be provided.

[0204] In the above 5G system, the insertion, change, or removal of the V-SMF for an HR-SBO session follows a process defined as part of the Rel-16 study item on the topology of SMF and UPF in enhanced 5G networks (ETSUN). The process for the insertion, change, or removal of the Intermediate SMF (I-SMF) is specified in clause 4.23 of 3GPP TS 23.502 (e.g., version v18.4.0), which is hereby incorporated by reference in its entirety. In clause 6.7.2 of 3GPP TS 23.548, the process for the insertion, change, or removal of the V-SMF is specified by replacing the I-SMF with the V-SMF and the SMF with the H-SMF, as well as the differences specific to the HR-SBO scenario. This process covers the inter-V-SMF inter-PLMN N2 handover and mobility registration, as well as the inter-V-SMF intra-PLMN N2 handover and Xn handover or mobility registration update in the HR-SBO scenario. During the insertion, change, or removal of the V-SMF, the SM context is exchanged between V-SMFs or between the H-SMF and the V-SMF, and vice versa.

[0205] In the 5G system, the Application Function (AF) may send a request that affects the traffic routing decision for user plane traffic. The AF request may affect the UPF (re)selection and allow routing of user traffic to a local Data Network (DN) or an Edge Application Server (EAS). The AF request may be for an individual UE or a group of UEs. The process related to the AF impact on traffic routing is specified in clause 5.6.7 of 3GPP TS 23.501 (e.g., version v18.4.0) (which is hereby incorporated by reference in its entirety), clause 4.3.6 of 3GPP TS 23.502, and the clauses of 3GPP TS 23.548. For example, as part of clause 6.7.3 of 3GPP TS 23.548, the EAS rediscovery and edge relocation processes are defined. Thus, due to UE mobility, AF interaction with the HPLMN, or AF interaction with the VPLMN, the EAS rediscovery and edge relocation in the VPLMN may be triggered.

[0206] However, supporting local traffic offloading for home routed PDU sessions in a roaming scenario (i.e., the HR-SBO scenario) in the VPLMN requires certain considerations that need to be made and addressed by embodiments of the present disclosure. For example, embodiments of the present disclosure enable a trusted or untrusted third-party AF to affect an HR-SBO PDU session, allow the V-SMF to send a notification to the AF that has affected the PDU session via the HPLMN, allow the H-SMF to convey an AF traffic impact request to the V-SMF for the (multiple) HR-SBO sessions served by the VPLMN, and enable the provision of EAS IP replacement information during V-SMF insertion or change for both cases when the change occurs within the same VPLMN or between VPLMNs.

[0207] Now, an exemplary method for managing a data session in a home routed (HR) session splitting (SBO) mode according to an embodiment of the present disclosure will be described.

[0208] Figure 6 A flowchart of a method 600 or process for managing a data session in a home routed (HR) session splitting (SBO) mode according to an embodiment of the present disclosure is shown. The method 600 or process may be executed in a wireless communication system. For example, the method 600 or process may be executed in a 5G system that supports access to an edge application server (EAS) of an edge computing service operating in a visited network in an HR roaming scenario, as described above with reference to Figure 5 as described. The wireless communication system may include a visited public land mobile network (VPLMN) and a home public land mobile network (HPLMN) having a system architecture as described above with reference to Figure 4 and Figure 5 as described.

[0209] The method 600 may be executed by one or more network nodes or network functions of the wireless communication system (including a base station (BS)). In some examples, the method 600 may be executed by a device in such one or more network nodes or network functions, or a device for use in such one or more network nodes or network functions. For example, one or more network nodes may be represented by any one of the network nodes such as gNBs 120A - 120B of the wireless network 100 or network node 130 as described above with reference to Figure 1 as described, network node 120 / network node 130 as described above with reference to Figure 3 as described, or one or more network functions as described above with reference to Figure 4 and Figure 5 as described.

[0210] According to an embodiment of the present disclosure, a method 600 for managing a data session (such as a protocol data unit (PDU) session) in the HR-SBO mode includes providing, by a home session management function (H-SMF) of a home public land mobile network (HPLMN), information on how to affect the traffic routing for a data session served by a visited network (VPLMN) to a visited session management function (V-SMF) of the visited network (see Figure 6 operation 640), and configuring, by the V-SMF, a user plane (UP) (or at least one UP function) based on the received information on how to affect the traffic routing for the data session (see Figure 6 operation 650).

[0211] In some examples, method 600 may start at operation 610. At operation 610, an application function (AF) of the home network may send a request (also referred to as an AF TI request) to a home policy control function (H-PCF) of the home network to affect the traffic for a data session in the HR-SBO mode served by the visited network.

[0212] For example, in a 5G system, the AF may send a traffic impact request to modify a traffic routing decision based on an internal trigger or a user plane-related event (such as UE mobility). Generally, the AF may send a traffic impact request to the serving PLMN directly or indirectly as follows:

[0213] - If the UE is not roaming, the AF may send a request directly to the HPLMN (i.e., the H-NEF);

[0214] - If the UE has established a local breakout (LBO) session and there is a service level agreement (SLA) between the AF and the VPLMN (serving PLMN), the AF may send a request directly to the VPLMN (i.e., the V-NEF);

[0215] - If the UE has established an HR-SBO session and there is an SLA between the AF and the VPLMN (serving PLMN for the HR session), the AF may send a request directly to the VPLMN (i.e., the V-NEF); and

[0216] - If the UE has established an HR-SBO session and there is no SLA between the AF and the VPLMN (serving PLMN for the HR session), the AF may interact with the HPLMN (i.e., the H-NEF) to send a traffic impact request to the VPLMN; this case is also considered when the AF sends a request to affect the traffic for the HR-SBO session to the VPLMN (i.e., the serving PLMN) via the HPLMN of the UE having the HR-SBO session.

[0217] In some examples, the AF may send a request to affect the traffic for a data session in the HR-SBO mode to the H-PCF via the Home Network Exposure Function (H-NEF) of the home network. That is, the AF may send a request to affect the traffic to the H-NEF. In response to receiving the request to affect the traffic, the H-NEF updates the information into the Unified Data Repository (UDR), and then the Unified Data Repository (UDR) notifies the same information to the H-PCF of the data session in the HR-SBO mode.

[0218] In other examples, the AF may directly (i.e., without going through the H-NEF) send a request to affect the traffic for a data session in the HR-SBO mode to the H-PCF.

[0219] As part of the AF TI request, the AF may also invoke an Edge Application Server (EAS) instance to change / relocate (e.g., as specified in clause 6.3.3 of 3GPP TS 23.548). To enable EAS change / relocation without including the UE in the process (in a way that the UE is not aware of the EAS change / relocation, e.g., the destination IP address changes), EAS IP replacement may be used. Using a notification procedure, the SMF may notify the AF about the ability to support EAS IP replacement. During the EAS change / relocation, if the AF receives the capability information, the AF may provide EAS IP replacement information, which includes the (multiple) source EAS IP addresses and the (multiple) source port numbers, as well as the (multiple) destination EAS IP addresses and the (multiple) destination port numbers.

[0220] In operation 620, the H-PCF may generate or update one or more PCC rules based on the request to affect the traffic. For example, one or more PCC rules generated or updated by the H-PCF may include the AF impact on the traffic routing control information, which is related to the content of the request to affect the traffic (e.g., the traffic impact API). One or more PCC rules may also include other information, such as information for charging and Quality of Service (QoS) control. In some examples, one or more PCC rules may also include the request to affect the traffic.

[0221] In some examples, one or more PCC rules may include one or more of the following: information for identifying the service to be affected, information about one or more data network access identifiers (DNAIs) of the visited network, an indication of service relevance, an indication of application relocation possibility, an indication of address reservation for the user equipment (UE), and a request to be notified when the UP path of a data session in HR-SBO mode has changed. In some examples, one or more PCC rules may also include, per DNAI, a service steering policy identifier and / or service routing information (e.g., N6 service routing information) related to the interface between the user plane function (UPF) and the data network (DN) (such as N6). In some examples, N6 service routing information may be included if it is explicitly provided in the request to affect the service.

[0222] In operation 630, the H-PCF may provide one or more generated or updated PCC rules to the H-SMF in the home network. For example, the H-PCF may send an update notification message (e.g., Npcf_SMPolicyControl_UpdateNotify) including the PCC rules related to session management policy control to the H-SMF.

[0223] That is, in the HR-SBO scenario, the H-PCF may provide a VPLMN-specific offloading policy to the H-SMF, and the offloading policy includes an IP range / (s) FQDN allowed to be routed to the local part of the DN in the visited network.

[0224] The H-SMF may determine or derive information on how to affect the service routing for a data session in HR-SBO mode based on one or more PCC rules received from the H-PCF. For example, the H-SMF may determine or derive information on how to affect the service routing for a data session in HR-SBO mode based on the AF impact on the service routing control information related to the content of the request to affect the service, or based on the request to affect the service, and this information is included in the PCC rule. That is, the information on how to affect the service routing for a data session in HR-SBO mode (also referred to herein as the visited network-related (e.g., VPLMN-related) application function impact on the service routing control information) may represent the information corresponding to the part of the PCC rule.

[0225] In operation 640, the H-SMF provides information to the V-SMF of the visited network on how to affect the service routing for data sessions in the HR-SBO mode. For example, if service offloading is allowed for data sessions in the HR-SBO mode, the H-SMF can provide this information by sending, via session management (SM) signaling, information on how to affect the service routing for data sessions in the HR-SBO mode. For example, the H-SMF can send a create or update message (e.g., Nsmf_PDUSession_Create / Update) related to a PDU session (such as a data session in the HR-SBO mode) to the V-SMF, or send a session management (SM) context. The message sent to the V-SMF can include, in an information element or container related to AF service impact (also referred to as an AF TI container), information on how to affect the service routing for data sessions in the HR-SBO mode. That is, the information element or container includes or provides information on how to affect the service routing for data sessions.

[0226] For example, similar to the PCC rules received by the H-SMF, the information on how to affect the service routing for data sessions in the HR-SBO mode can include one or more of the following: information for identifying a service, information on one or more data network access identifiers (DNAIs) of the visited network, an indication of service relevance, an indication of application relocation possibility, an indication of address reservation for a user equipment, and a request to be notified when the UP path of the data session has changed. In some examples, the information on how to affect the service routing for data sessions in the HR-SBO mode can also include, per DNAI, a service steering policy identifier and / or service routing information (e.g., N6 service routing information) related to the interface between a user plane function (UPF) and a data network (DN).

[0227] The H-SMF can use the N16 or N16a interface with an information element or container (transparent or non-transparent) dedicated to AF TI-related PCC rules / rule updates (e.g., as an AF TI container) to provide the V-SMF with information on how to affect the service routing for data sessions in the HR-SBO mode.

[0228] In some examples, the H-SMF may provide information on how to affect the service routing for data sessions in the HR-SBO mode, or an AF TI request, as part of the VPLMN-specific offloading rules / information. For example, the VPLMN-specific offloading rules / information may include an AF TI container. The AF TI container may also be used to convey some or all of the parameters / information elements defined / used in an existing AF request, as specified by 3GPP TS23.503 (e.g., version v18.4.0), which is incorporated herein by reference in its entirety.

[0229] In some other examples, the H-SMF (or H-PCF) may also map information elements as part of an AF TI request to existing parameters (such as an SM context) exchanged between the H-SMF and the V-SMF. Information elements that are not mapped to any other existing parameters may be sent as individual parameters in an extended version of an existing message / context (e.g., an SM context).

[0230] That is, in the HR-SBO scenario, the H-SMF may generate VPLMN-specific offloading information and provide this information to the SMF at the serving PLMN, i.e., the V-SMF.

[0231] In operation 650, the V-SMF configures or reconfigures the UP based on information on how to affect the service routing for data sessions in the HR-SBO mode. For example, the V-SMF may consider the information on how to affect the service routing for data sessions in the HR-SBO mode and reconfigure the user plane, e.g., N4 rule updates, PSA-UPF insertion or relocation, DNAI change, EAS relocation decision, and any required notifications (if requested).

[0232] In response to (re)configuring the service plane, in operation 660, the V-SMF may send a create or update response message related to the PDU session (e.g., an Nsmf_PDUSession_Create / Update response) to the H-SMF. Additionally, in operation 670, the H-SMF may send an update notification message (response) related to session management policy control (e.g., an Npcf_SMPolicyControl_UpdateNotify) to the H-PCF.

[0233] According to some embodiments of the present disclosure, an exemplary method for managing data sessions in the HR-SBO mode may further include providing notification endpoint information (e.g., the uniform resource identifier (URI) information of the H-SMF) from the H-SMF to the V-SMF. The notification endpoint information may be in Figure 6It is provided in operation 640 as shown (e.g., as information on how to affect the service routing for a data session in the HR-SBO mode, or as part of an AF TI container). For example, the H-SMF may send notification endpoint information to the V-SMF as part of Nsmf_PDUSession_Create / Update. The V-SMF may use the notification endpoint information to send a notification to the AF via the home network. More specifically, using the notification endpoint information, the V-SMF may send a notification to the H-SMF, which may forward at least some of the notifications (directly or via the H-NEF) to the AF.

[0234] In some examples, the H-SMF may provide notification endpoint information to the V-SMF in response to a request for a notification regarding an event on a data session (e.g., received from the AF). The request for the notification may include notification endpoint information associated with the AF, or if the request is received via the H-NEF, include notification endpoint information associated with the H-NEF. The H-SMF may internally maintain an indication of the notification endpoint information to allow notifications from the V-SMF to be forwarded directly or via the H-NEF to the AF. In other words, the H-SMF may process the notification from the V-SMF and remap the notification to the AF or the H-NEF.

[0235] In some examples, when the H-SMF does not provide its own notification endpoint information, the H-SMF may provide an indication to the V-SMF that the notification endpoint information is either notification endpoint information associated with the AF or notification endpoint information associated with the H-NEF.

[0236] In some examples, the notification endpoint information (e.g., URI information) may be provided as part of the SM context, where the information element is part of the AF coordination information. For example, the information element including the notification endpoint information may be included in the SM context as specified in 3GPP TS23.502.

[0237] According to some embodiments of the present disclosure, an exemplary method for managing a data session in the HR-SBO mode may further include receiving, at an H-SMF, a request for a notification regarding an event on the data session. The request may include notification endpoint information associated with an AF or with a home network exposure function (H-NEF) of the home network. The H-SMF may associate a notification endpoint at the H-SMF (i.e., the notification endpoint information associated with the H-SMF) with a notification endpoint at the AF or the H-NEF (i.e., the notification endpoint information associated with the AF or the H-NEF), and store the association between the notification endpoint at the H-SMF and the notification endpoint at the AF or the H-NEF (i.e., the association between the notification endpoint information associated with the H-SMF and the notification endpoint information associated with the AF or the H-NEF). Then, the H-SMF may provide the notification endpoint information associated with the H-SMF to the V-SMF as notification endpoint information (e.g., as part of information on how to affect the service routing for the data session in the HR-SBO mode). The notification endpoint information may be used by the V-SMF to send a notification regarding an event on the data session to the AF (i.e., to the H-SMF). The H-SMF may obtain or determine the notification endpoint information to be used by the H-SMF to forward a notification regarding an event based on the stored association. That is, the H-SMF uses the notification endpoint information used by the V-SMF to send a notification regarding an event on the data session to obtain or determine, based on the stored association, the notification endpoint information associated with the AF or the H-NEF. Then, the H-SMF may use the obtained or determined notification endpoint information associated with the AF or the H-NEF to forward a notification regarding an event to the AF (e.g., via the H-NEF).

[0238] Reference will now be made to Figures 7 to 9 describe an exemplary message sequence diagram of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure. The method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure is related to the HR-SBO scenario to support local service routing in a visited network for a home routed PDU session for roaming, as described in reference Figure 5 is described.

[0239] Reference Figure 7 , illustrates an exemplary message sequence diagram of a method or process for managing a data session (e.g., a PDU session) in the HR-SBO mode according to an embodiment of the present disclosure. The exemplary message sequence diagram illustrates the signaling of an AF service impact request from a home network (e.g., an HPLMN) to a visited network (e.g., a VPLMN) in the HR-SBO scenario as illustrated in Figure 5 .

[0240] AF (e.g., Figure 5 AF 507-2 shown in Figure 5 interacts with the home network (e.g., HPLMN) to affect the traffic for a PDU session in HR-SBO mode served by a visited network (e.g., VPLMN). For example, the AF may send a traffic impact request to the home network. The traffic impact request may be sent directly in step 710B or, via the network exposure function of the home network (i.e., H-NEF), in step 710A, to the policy control function of the home network (e.g.,

[0241] H-PCF 506-1 shown in

[0242] If the traffic impact request is sent via the H-NEF (step 710A), the H-NEF may store / update / remove in step 712A the information affecting the traffic for the HR-SBO session (i.e., PDU session) to / from the unified data repository (UDR). In this case, when there is an update to the information affecting the traffic for the HR-SBO session, the UDR sends a notification of the HR-SBO session to the H-PCF in step 714A. For example, the UPF may send Nudr_DM_Notify to the H-PCF in step 714A. In some examples, the H-NEF may use the binding support function (BSF) to find the H-PCF for the PDU session.

[0243] In response to receiving the traffic impact request, the H-PCF may generate or update one or more policy and charging control (PCC) rules based on the traffic impact request. The PCC rules to be generated or updated may include information requiring the enabling of user plane detection for policy control and proper charging for service data flows. For example, the PCC rules may include the AF impact on the traffic routing control information related to the content of the request affecting the traffic. Figure 5The H-SMF505-1) shown in [description] provides one or more generated / updated PCC rules. For example, the H-PCF may send an update notification (e.g., Npcf_SMPolicyControl_UpdateNotify) of one or more generated / updated PCC rules to the H-SMF signaling.

[0244] In step 730, the H-SMF may send the received service impact information (e.g., received as a PCC rule from the H-PCF) to the V-SMF. The H-SMF may also determine the application function impact of applying control information for service routing related to the visited network (i.e., the VPLMN-related application function impact of applying control information for service routing), and provide the VPLMN-related application function impact of applying control information for service routing to the SMF in the visited network (e.g., Figure 5 the V-SMF505-2) shown in [description]. For example, the H-SMF may send the VPLMN-related application function impact of applying control information for service routing to the V-SMF by invoking a message (e.g., Nsmf_PDUSession_Create / Update) to the V-SMF.

[0245] In some examples, the message may include the VPLMN-related application function impact of applying control information for service routing (i.e., information on how to affect service routing for a PDU session in the HR-SBO mode, or service impact-related information according to a service impact request) in an information element or container (also referred to as an AF service impact (TI) container). The H-SMF may use the N16 or N16a interface including the AF TI container to provide the VPLMN-related application function impact of applying control information for service routing to the V-SMF. In some examples, the AF TI container may be a transparent or non-transparent container dedicated to an AF service impact-related PCC rule or rule update.

[0246] In some examples, some or all of the parameters / information elements defined / used in the AF request provided in Table 5.6.7-1 of 3GPP TS23.501 or Table 6.3.1 of 3GPP TS23.503 may be communicated from the H-SMF to the V-SMF as part of the AF TI container in the N16 or N16a interface in step 730.

[0247] In step 740, the V-SMF considers the VPLMN-related application function impact of the control information (i.e., the information in the AF TI container) on the service routing and (re)configures the user plane (UP) (or at least the UP function) based on the VPLMN-related application function impact of the control information on the service routing to affect the service for the PDU session in the HR-SBO mode. Reconfiguring the user plane may include PSA-UPF (e.g., PSA-UPF 504-2b) insertion or relocation, DNAI change, EAS relocation decision, N4 rule update, and any required notifications (if requested). In some examples, the V-SMF may also generate or update one or more PCC rules based on the VPLMN-related application function impact of the control information on the service routing and configure the UP based on the one or more PCC rules.

[0248] In step 750, the V-SMF may confirm the VPLMN-related application function impact of the control information on the service routing received in step 730. For example, the V-SMF may send a message (e.g., Nsmf_PDUSession_Create / Update response) to the H-SMF to confirm the receipt of the message (e.g., Nsmf_PDUSession_Create / Update) received in step 730.

[0249] In response to receiving the confirmation from the V-SMF, the H-SMF may send a response (e.g., Npcf_SMPolicyControl_UpdateNotify) to the H-PCF in step 760.

[0250] In other words, Figure 7 the exemplary message sequence diagram of... is used to provide the AF service impact request sent to the H-NEF / H-PCF to the V-SMF via the H-SMF. In this example of the method or process for managing a PDU session in the HR-SBO mode according to an embodiment of the present disclosure, the V-SMF inserted into the PDU session (i.e., the PDU session in the HR-SBO mode) may provide a list of DNAIs supported by the V-SMF to the H-SMF. In some examples, this list may remain unchanged during the N16 or N16a association between the V-SMF and the H-SMF for the PDU session.

[0251] Additionally, or alternatively, in Figure 7In an exemplary message sequence diagram and an example of a method or process for managing a PDU session in HR-SBO mode according to an embodiment of the present disclosure, an AF service impact request (i.e., the service impact request received in step 710), or a VPLMN-related application function impact that exercises control information on service routing, can be provided from the H-SMF to the V-SMF as part of specific offloading rules / information related to the visited network (also referred to as the VPLMN-specific offloading policy).

[0252] In such an example, an AF TI container as described above can be used to convey some or all of the parameters / information elements defined / used in the AF requests provided in Table 5.6.7-1 of 3GPP TS23.501 or Table 6.3.1 of 3GPP TS23.503.

[0253] An example of including an AF TI container as part of the VPLMN-specific offloading policy is shown in the following table:

[0254] Table: PDU session-related policy information

[0255]

[0256] In these examples, the procedure of using (a) offloading identifier(s) as specified in 3GPP TS23.548 can be used to send an (updated) service impact request from the AF.

[0257] Additionally, or alternatively, in Figure 7 the exemplary message sequence diagram and an example of a method or process for managing a PDU session in HR-SBO mode according to an embodiment of the present disclosure, the H-SMF can map information elements that are part of the AF service impact to existing parameters exchanged between the H-SMF and the V-SMF as part of session management (SM) signaling (such as Nsmf_PDUSession_Create / Update). In such an example, information elements that are not mapped to any other existing parameters can be sent as individual parameters in an extended version of the existing message / context.

[0258] Additionally, or alternatively, in Figure 7 the example message sequence diagram and an example of a method or process for managing a PDU session in HR-SBO mode according to an embodiment of the present disclosure, the H-SMF can send the AF TI container as part of the PDU session information sent by the H-SMF to the V-SMF via SM-related signaling (Nsmf_PDUSession_Create / Update).

[0259] As will be described in more detail below, inFigure 7 In an exemplary message sequence diagram and an example of a method or process for managing a PDU session in the HR-SBO mode according to an embodiment of the present disclosure, the H-PCF may be provided in or with one or more PCC rule notification endpoint information (e.g., including information notified by the H-NEF to the endpoint) for the SMF to notify the H-NEF. For example, information determined by the 5GC related to UE members in the set of UEs identified by the service association ID may be notified.

[0260] In addition, as will be described in more detail below, in Figure 7 another exemplary message sequence diagram of a method or process for managing a PDU session in the HR-SBO mode according to an embodiment of the present disclosure, the H-PCF may be provided in or with one or more PCC rule information to enable the AF (or H-NEF) to subscribe to SMF events (e.g., UP path change) corresponding to the AF service impact request. In this example, for instance, by providing a policy at the time of PDU session establishment or by initiating a PDU session modification process, information received in the AF service impact request regarding the AF subscription to the corresponding SMF event is provided. More specifically, the H-SMF may initiate establishment and modification processes to the V-SMF.

[0261] Reference Figure 8 shows an exemplary message sequence diagram of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure. The exemplary message sequence diagram illustrates enabling the V-SMF to send notifications to the AF via the H-SMF, or directly to the AF or H-NEF, in the HR-SBO scenario illustrated in Figure 5

[0262] According to one aspect, Figure 8 the exemplary message sequence diagram of a method or process for managing a data session (e.g., PDU session) (also simply referred to as an HR-SBO session) in the HR-SBO mode according to an embodiment of the present disclosure shown in

[0263] Figure 8The example message sequence diagram of the method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure as shown may represent or supplement the process of EAS rediscovery and edge relocalization when HR-SBO is supported and allowed in the target serving PLMN as specified in clause 6.7.3.2 of 3GPP TS 23.548.

[0264] In step 0, the processes specified in clauses 6.7.2.6, 6.7.2.7, and 6.7.2.9 of 3GPP TS 23.548 may be performed, such as an inter-V-SMF inter-PLMN N2 handover or mobility registration (step 0a) in an HR-SBO scenario; or an inter-V-SMF intra-PLMN N2 handover or Xn handover or mobility registration update (step 0b) in an HR-SBO scenario.

[0265] In step 1, if the process of step 0a has been performed, and if the AF has subscribed to the corresponding event, and the serving PLMN changes towards a PLMN where local traffic offloading for the PDU session can be performed, the H-SMF may notify the AF, indicating the new serving PLMN ID and the HPLMN DNN and S-NSSAI for the HR-SBO session. This may occur immediately after the H-SMF has received an indication of handover completion (i.e., step 13 of the process specified in clause 6.7.2.6 of 3GPP TS 23.548).

[0266] Via the mechanism of step 1, the AF knows the PLMN to contact to issue a traffic impact request for the HR-SBO session, and if available, the AF knows the PLMN to contact using the HPLMN DNN and S-NSSAI information. Assume the AF checks whether the AF has an SLA with the new serving PLMN. If the AF does not have an SLA with the new serving VPLMN, the AF interacts with the H-NEF to issue a traffic impact request. This may trigger AF-triggered edge relocalization / EAS rediscovery as specified in step 1b of clause 6.2.3.3 and step 4a of clause 6.3.3.1.1 of 3GPP TS 23.548.

[0267] In step 2a, for AF-triggered EAS rediscovery and edge relocalization via interaction with the HPLMN, the AF may use the AF impact on the traffic routing process (as specified in clause 4.3.6 of 3GPP TS 23.502) to indicate, via the H-PCF to the H-SMF, the EAS rediscovery for the affected application (identified by the (multiple) application identifiers). The AF may also provide EAS IP replacement information and the target DNAI, and together provide an indication of the PLMN associated with the target DNAI (i.e., the serving PLMN ID).

[0268] In step 2b, for EAS rediscovery and edge relocalization triggered by the AF via interaction with the serving VPLMN, the AF may use the procedure specified in clause 4.3.6 of 3GPP TS 23.502 to indicate, via the V-NEF, EAS rediscovery for the affected application.

[0269] The AF may also provide the VPLMN (i.e., the V-SMF) with EAS IP replacement information and the target DNAI, in which case steps 3 and 4 described below may be skipped.

[0270] In step 3a, for EAS rediscovery and edge relocalization triggered by the AF via interaction with the HPLMN, the AF service impact request information (i.e., the application function impact on the service routing enforcement control information) may be sent to the H-SMF via one or more PCC rules. This may trigger step 2 of the procedure specified in clause 6.2.3.3 of 3GPP TS 23.548, where the SMF initiating the PDU session modification is the H-SMF.

[0271] For example, the H-SMF may issue an Nsmf_PDUSession_Update request, which may include the EAS IP replacement information and the target DNAI provided by the AF in step 2.

[0272] According to an embodiment of the present disclosure, the H-SMF may include its own notification URI, to which the V-SMF may provide any notifications, which are ultimately forwarded by the H-SMF (directly or via the H-NEF) to the AF. The Nsmf_PDUSession_Update request may also include a policy due to the service impact information provided by the AF (e.g., the AF TI container as described above).

[0273] In addition, in step 3a, if the V-SMF is unable to serve the target DNAI, the V-SMF may invoke the Nsmf_PDUSession_SMContextStatusNotify service operation to send the target DNAI to the AMF, and the AMF may select the target V-SMF by replacing the I-SMF with the V-SMF based on the target DNAI specified in clause 4.23.5.4 of 3GPP TS 23.502. The target V-SMF obtains the SM context from the source V-SMF using the Nsmf_PDUSession_Context request / response, including the authorization result for HR-SBO, the EAS IP replacement information, and the target DNAI in the request. The target V-SMF may select a new V-EASDF according to the procedure specified in steps 2 to 12 of clause 6.7.2.6 of 3GPP TS 23.548.

[0274] According to an embodiment of the present disclosure, the Nsmf_PDUSession_Context request / response may further include a notification URI.

[0275] In step 3b, for EAS rediscovery and edge relocalization triggered by the AF via interaction with the VPLMN, the V-SMF may initiate an Nsmf_PDUSession_Update request with an EAS rediscovery indication and an impact field to the H-SMF, and the H-SMF may initiate an Nsmf_PDUSession_Update response to the (target) V-SMF, including the PCO information to be sent to the UE, as specified in step 2 of clause 6.2.3.3 of 3GPP TS 23.548. In the case of a V-SMF change within the PLMN, the target V-SMF may use the source DNAI and the target DNAI to determine the impact field to be sent to the UE. In the case of inter-PLMN mobility, the target V-SMF may provide EAS rediscovery information without an impact field.

[0276] According to an embodiment of the present disclosure, if the AF has subscribed to user plane management event notifications (such as DNAI change, PSA UPF relocalization, or EAS replacement capability) from the H-SMF, the V-SMF may send a notification to the notification URI received from the H-SMF and send a notification to the notification URI provided by the H-SMF.

[0277] In step 4, the V-SMF may initiate a PDU session modification command to the UE, including the PCO. The PCO may include an EAS rediscovery indication (optional) and an impact field (optional).

[0278] Finally, in step 5, the V-SMF may configure the V-UPF (UL CL and L-PSA) using the EAS IP replacement information.

[0279] As described in the reference Figure 8 An exemplary message sequence diagram of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure enables the V-SMF to provide the required notification information to the AF (trusted or untrusted third-party AF).

[0280] In an example of an exemplary message sequence diagram of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure, the notification endpoint information (e.g., notification URI) may be provided to the V-SMF as part of the signaling described above Figure 7 e.g., via the AF TI container. In this case, the H-SMF may change the NEF information parameter of the notification endpoint used for the NEF subscription to be notified to the H-SMF itself. The H-SMF may also maintain internally an indication of the URI information on which V-SMF notification will be forwarded (directly or via the H-NEF) to the AF. That is, the H-SMF processes any notification from the V-SMF and remaps the notification to the H-NEF. This aspect is further described in Figure 9 In.

[0281] In another example of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure, the VPLMN-related application function impact of the service routing enforcement control information (including the notification URI information) may be provided as part of the SM context exchanged between the V-SMF and the H-SMF (e.g., as part of the V-SMF insertion process), or exchanged between the source V-SMF and the target V-SMF as part of the AF coordination information including the notification URI IE (e.g., as part of the V-SMF change process).

[0282] For example, the notification URI IE and the EAS IP replacement information may be included in the SM context table as specified in Table 5.2.8.2.10-1 of 3GPP TS 23.502:

[0283] Table: SM context of the PDU session transmitted between (multiple) I-SMFs or between (multiple) V-SMFs or between the I / V-SMF and the (H-)SMF

[0284]

[0285]

[0286]

[0287]

[0288] According to an embodiment of the present disclosure, the SM context table may further include the following:

[0289]

[0290] When the H-SMF notifies the AF (or H-NEF) about the events described in Table 5.2.8.3.1-1 of 3GPP TS 23.502: Examples of event filters for SMF exposure events and the events described in clause 5.2.8.3.2 of 3GPP TS 23.502 applicable to HR-SBO sessions served by the VPLMN (V-SMF), the H-SMF may include the ability to support EAS IP replacement in the 5GC using the PLMN ID of the VPLMN.

[0291] Provided that the VPLMN (V-SMF) supports the EAS IP replacement capability, the confirmation notification regarding the (multiple) UE PDU session-related events from the V-SMF may also be relayed via the H-SMF as part of the Nsmf_EventExposure_AppRelocationInfo service operation specified in clause 5.2.8.3.2A of 3GPP TS 23.502. The notification may also include a cause code that indicates whether the confirmation is positive or negative. Thus, the PLMN ID or SMF ID may be considered part of the input parameters of the service to distinguish whether the confirmation is for the H-SMF or the V-SMF.

[0292] According to another aspect, Figure 8 The exemplary message sequence diagram of the method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure shown in involves enabling the V-SMF to provide the required notification information directly or via the H-NEF to the AF (trusted or untrusted third-party AF).

[0293] In the example, a direct notification to the AF may require an SLA between the PLMN and the third-party AF. The AF may request a notification from the 5GC and provide its notification URI. If the request is sent via the NEF, the NEF provides its own / translated URI to the PCF / SMF, as specified, for example, in clause 4.3.6.2 of 3GPP TS 23.502.

[0294] According to an embodiment of the present disclosure, in Figure 8In step 3a as shown, the H-SMF may forward the received notification to the V-SMF as part of the Nsmf_PDUSession_Update procedure. The H-SMF may indicate whether the URI belongs to the H-NEF (in the HPLMN) or the AF as part of notifying the URI owner in the table above. The V-SMF may send the notification directly to the AF (if there is an SLA there) or the H-NEF, and the H-NEF in turn forwards the information to the AF.

[0295] Now referring to Figure 9 , another exemplary message sequence diagram of a method or process for managing a data session in the HR-SBO mode according to an embodiment of the present disclosure is illustrated. The exemplary message sequence diagram illustrates the details that enable the V-SMF to send a notification to the AF via the H-SMF in the Figure 5 HR-SBO scenario shown.

[0296] According to one aspect, Figure 9 The exemplary message sequence diagram of a method or process for managing a data session (e.g., PDU session) in the HR-SBO mode according to an embodiment of the present disclosure as shown involves providing notification endpoint information to the V-SMF. Thus, the V-SMF is enabled to send notifications about events on the PDU session to the AF via the home network (mainly via the H-SMF).

[0297] In step 900, the H-PCF in the home network (e.g., Figure 5 the H-PCF 506-1 shown) receives a request from the AF in the HPLMN to affect traffic routing, where the request is for a PDU session controlled by the H-PCF. In some examples, step 900 may correspond to Figure 7 steps 710-714A or step 710B of

[0298] In step 910, the H-SMF in the home network (e.g., Figure 5 the H-SMF 505-1 shown) may receive a request for a notification about an event on the PDU session from the H-PCF in the home network (e.g., Figure 5 the H-PCF 506-1 shown). The request for a notification about an event on the PDU session may be a subset of the application function impact on the traffic routing control information sent by the H-PCF to the H-SMF and includes notification endpoint information associated with the AF (e.g., Figure 5 the AF 507-1 shown) or with the H-NEF of the home network (e.g., Figure 5Notification endpoint information associated with the H-NEF 513-1) shown in. The notification endpoint information may include a notification URI associated with the AF or the H-NEF. In some examples, step 910 may correspond to Figure 7 step 720 of

[0299] In step 920, the H-SMF may associate the notification endpoint at the H-SMF with the notification endpoint received in the application function impact of the service route enforcement control information sent by the H-PCF to the H-SMF at the AF or the H-NEF. That is, the H-SMF may associate the notification endpoint information associated with itself (the H-SMF) with the notification endpoint information received in step 910 and associated with the AF or the H-NEF. Forcing notifications from the V-SMF to pass through the H-SMF allows avoiding creating a direct interface from the V-SMF to the H-NEF / AF of the HPLMN, which would mean managing a new inter-operator interworking point and thus a new inter-operator interface (operators tend to avoid this).

[0300] In step 930, the H-SMF may store the association between the notification endpoint at the H-SMF and the notification endpoint received in the application function impact of the service route enforcement control information sent by the H-PCF to the H-SMF (the notification endpoint at the AF or the H-NEF). That is, the H-SMF may store the association between the notification endpoint information associated with the H-SMF and the notification endpoint information received in step 910 and associated with the AF or the H-NEF.

[0301] In step 940, the H-SMF may provide the notification endpoint information associated with the H-SMF to the V-SMF in the visited network (e.g., Figure 5 the V-SMF 505-2) shown in, as notification endpoint information for the V-SMF to use for sending notifications about events on the PDU session to the AF. The H-SMF may provide the notification endpoint information associated with the H-SMF as part of the VPLMN-related application function impact of the service route enforcement control information sent to the V-SMF. For example, the H-SMF may send a message (e.g., Nsmf_PDUSession_Create / Update) that includes an information element or container dedicated to the VPLMN-related application function impact of the service route enforcement control information (e.g., the AF TI container as described above), and includes the notification endpoint information associated with the H-SMF (e.g., the notification URI associated with the H-SMF).

[0302] Then, the V-SMF may consider the VPLMN-related application function impact on the service routing of the control information (i.e., the information in the AF TI container), and (re)configure the user plane (UP) of the PDU session based on the VPLMN-related application function impact on the service routing of the control information, so as to affect the service for the PDU session in the HR-SBO mode, as described in step 740 of the reference Figure 7 as described above.

[0303] In step 940b, the V-SMF may confirm the VPLMN-related application function impact on the service routing of the control information received in step 940. For example, the V-SMF may send a message (e.g., Nsmf_PDUSession_Create / Update response) to the H-SMF to confirm the receipt of the message (e.g., Nsmf_PDUSession_Create / Update) received in step 940.

[0304] In step 950a, the V-SMF may detect the event required to send a notification according to the VPLMN-related application function impact on the service routing of the control information. In response, the V-SMF may send a notification to the H-SMF in step 950b, where the notification is for the notification endpoint at the H-SMF. The V-SMF may use the notification endpoint information associated with the H-SMF received in step 940 to send a notification to the H-SMF. For example, the V-SMF may send Nsmf_EventExposure_Notify to the notification URI associated with the H-SMF.

[0305] In response to receiving the notification from the V-SMF, the H-SMF may obtain or determine the notification endpoint information for the H-SMF to use to forward the notification to the AF or H-NEF in step 970. The H-SMF may use the notification endpoint information used by the V-SMF in step 950b to obtain or determine the notification endpoint information associated with the AF or H-NEF based on the association stored in step 930. For example, the H-SMF may obtain the notification endpoint received by the H-SMF in the PCC rule, which has been associated with the notification endpoint at the H-SMF in step 920.

[0306] In step 980, the H-SMF may forward the received notification to the AF (e.g., via the H-NEF) using the notification endpoint information associated with the AF or the H-NEF. For example, the H-SMF may send an Nsmf_EventExposure_Notify including the notification to the notification URI associated with the AF or the H-NEF. Embodiments of the present disclosure described above enhance the H-SMF function and the corresponding interfaces to enable an AF service impact request for an HR-SBO session to the V-SMF, the H-SMF function, and the corresponding interfaces with the H-SMF to relay the notification sent from the V-SMF to the AF, such that the H-SMF differentiates the notifications sent to the AF (i.e., whether the notification is from the (multiple) V-SMF or its own notification), and enables the H-SMF to provide the notification URI and indicate whether the notification URI belongs to the H-SMF itself, the H-NEF, or the AF.

[0307] It should be understood that the apparatus may include or be coupled to other units or modules for transmission and / or reception, such as radio components or radio heads. Although the apparatus has been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0308] It should be noted that although the embodiments have been described with respect to LTE and 5G NR, similar principles may be applied to other networks and communication systems that require forced fast connection re-establishment. Thus, although certain embodiments have been described above by way of example with reference to certain exemplary architectures for wireless networks, technologies, and standards, the embodiments may be applied to any other suitable form of communication system other than the communication systems illustrated and described herein.

[0309] It should also be noted herein that although the exemplary embodiments have been described above, several variations and modifications may be made to the disclosed solutions without departing from the scope of the present disclosure.

[0310] In general, the various exemplary embodiments may be implemented in hardware or in a dedicated circuit, software, logic, or any combination thereof. Some aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, a microprocessor, or other computing devices, but the present disclosure is not limited thereto. Although the various aspects of the present disclosure may be illustrated and described in terms of block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, apparatus, systems, technologies, or methods described herein may be implemented in hardware, software, firmware, a dedicated circuit or logic, general hardware or a controller or other computing devices, or some combination thereof.

[0311] Embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device, such as in a processor entity, or by hardware, or by a combination of software and hardware. The computer software or program, also referred to as a program product, includes software routines, applets, and / or macros and may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. The computer program product may include one or more computer-executable components, which are configured to perform the embodiments when the program runs. One or more computer-executable components may be at least one software code or a portion thereof.

[0312] In this regard, it should be noted that any block of the logical flow in the figures may represent a program step, or an interconnected logical circuit, block, and function, or a combination of program steps and logical circuit, block, and function. The software may be stored on a physical medium such as a memory chip or a memory block implemented within a processor, a magnetic medium such as a hard disk or a floppy disk, and an optical medium such as a DVD and its data variant CD. The physical medium is a non-transitory medium.

[0313] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and, by way of non-limiting example, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0314] Embodiments of the present disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Sophisticated and powerful software tools may be used to transform a logic-level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0315] The foregoing description has provided a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, various modifications and adaptations will become apparent to those skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of the present invention will still fall within the scope of the present disclosure as defined in the appended claims. In fact, there is another embodiment that includes a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

1. A method for managing a data session in a home routed (HR) session splitting offload (SBO) mode, the method comprising: - Receiving, by a home policy control function (H-PCF) of a home network, a request from an application function (AF) that affects the service for the data session; - Generating, by the H-PCF, one or more policy and charging control (PCC) rules based on the request, wherein a PCC rule among the one or more PCC rules includes the request that affects the service for the data session; And - Providing, by the H-PCF, the one or more PCC rules to a home session management function (H-SMF); And - Providing, by the H-SMF, information on how to affect the service routing for the data session served by the visited network to a visited session management function (V-SMF) of the visited network, the information on how to affect the service routing for the data session being based on at least the PCC rule among the one or more PCC rules, and the information on how to affect the service being used by the V-SMF to configure the use of at least a user plane (UP) function of the visited network based on the information on how to affect the service routing for the data session.

2. The method according to claim 1, further comprising: - Determining, by the H-SMF, the information on how to affect the service routing for the data session based on at least one PCC rule among the one or more PCC rules provided by the H-PCF.

3. The method according to claim 1 or 2, wherein the information on how to affect the service routing for the data session includes a subscription request for notification of any user plane management event received from the AF.

4. The method according to any one of claims 1 to 3, wherein the information on how to affect the service routing for the data session includes one or more of the following: information for identifying the service, information on one or more data network access identifiers (DNAIs) of the visited network, an indication of service relevance, an indication of application relocation possibility, an indication of address reservation for a user equipment, a request to be notified when the UP path of the data session has changed.

5. The method according to claim 4, wherein the information on how to affect the service routing for the data session further includes, per DNAI, a service steering policy identifier and / or service routing information related to an interface between a user plane function (UPF) and a data network (DN).

6. The method according to any one of claims 1 to 5, wherein providing, by the H-SMF, the information on how to affect the service routing for the data session to the V-SMF includes the H-SMF sending a session management (SM) message or SM context including an information element or container to the V-SMF to provide the information on how to affect the service routing for the data session.

7. The method according to any one of claims 1 to 6, further comprising: - The H-SMF provides the V-SMF with offloading rules or information on how the visited network should affect the service routing for the data session.

8. The method according to any one of claims 1 to 7, further comprising: - The H-SMF maps the parameters affecting the request for the service of the data session from the one or more PCC rules to the parameters to be exchanged between the H-SMF and the V-SMF, and the H-SMF provides the mapped parameters to the V-SMF in a session management message; and - Extend the session management message or context with the parameters affecting the request for the service of the data session that are not mapped to the parameters of the session management message.

9. The method according to any one of claims 1 to 8, wherein the H-SMF providing the V-SMF with the information on how to affect the service routing for the data session includes the H-SMF providing the V-SMF with notification endpoint information for the V-SMF to use to send a notification to the AF via the home network.

10. The method according to claim 9, further comprising: - The H-SMF receives a request for a notification about an event on the data session, the request indicating that the notification is to include the notification endpoint information, wherein when the H-SMF does not provide its own notification endpoint information, the notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the home network exposure function H-NEF of the home network, and the request from the AF is received via the H-NEF; and - When the H-SMF does not provide its own notification endpoint information, the H-SMF provides the V-SMF with an indication that the provided notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the H-NEF.

11. The method according to claim 9 or 10, further comprising: - The H-SMF receives a notification request for an event on the data session, the request indicating that the notification is to include the notification endpoint information, wherein the notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the home network exposure function H-NEF of the home network; - The H-SMF associates the notification endpoint information associated with the H-SMF with the received notification endpoint information; - The H-SMF stores the association between the notification endpoint information associated with the H-SMF and the received notification endpoint information; - The H-SMF provides the notification endpoint information associated with the H-SMF to the V-SMF as the notification endpoint information to be used by the V-SMF to send a notification about an event on the data session to the AF; - The H-SMF receives, from the V-SMF, a notification about an event that is sent using the notification endpoint information associated with the H-SMF; - The H-SMF obtains the notification endpoint information to be used by the H-SMF to forward the notification based on the association; And - The H-SMF uses the obtained notification endpoint information to forward the notification about the event to the AF.

12. A device for communication, the device comprising: At least one processor; And At least one memory storing instructions for a home session management function H-SMF of a home network, the instructions, when executed by the at least one processor, cause the device to at least: - Determine information on how to affect the traffic routing of a data session in a session break-off (SBO) mode of a home routed (HR) session served by a visited network based on one or more policy and charging control (PCC) rules received from a home policy control function H-PCF of the home network, wherein the PCC rules in the one or more PCC rules include requests affecting the traffic of the data session received by the H-PCF from an application function AF; - Provide the information on how to affect the traffic routing of the data session to a visited session management function V-SMF of the visited network, and the information on how to affect the traffic routing of the data session is used by the V-SMF to configure at least a user plane (UP) function.

13. The device according to claim 12, wherein the instructions are further configured to cause the device to at least: - Receive the one or more PCC rules from the H-PCF, the one or more PCC rules having been generated based on the request affecting the traffic of the data session from the AF.

14. The device according to any one of claims 12 to 13, wherein the information on how to affect the traffic routing of the data session includes the request affecting the traffic of the data session received from the application function AF.

15. The device according to any one of claims 12 to 14, wherein the information on how to affect the traffic routing of the data session includes one or more of the following: information for identifying the traffic, information on one or more data network access identifiers (DNAIs) of the visited network, an indication of traffic relevance, an indication of application relocation possibility, an indication of address reservation for a user equipment, a request to be notified when the UP path of the data session has changed.

16. The device according to claim 15, wherein the information on how to affect the traffic routing of the data session further includes, per DNAI, a traffic steering policy identifier and / or traffic routing information related to an interface between a user plane function (UPF) and a data network (DN).

17. The device according to any one of claims 12 to 16, wherein the instructions are further configured to cause the device to at least: - Send a session management (SM) message or SM context including information elements or containers to the V-SMF to provide the information on how to affect the service routing for the data session.

18. The apparatus according to any one of claims 12 to 17, wherein the instructions are further configured to cause the apparatus to at least perform: - Provide the V-SMF with offloading rules or information on how the visited network should affect the service routing for the data session.

19. The apparatus according to any one of claims 12 to 18, wherein the instructions are further configured to cause the apparatus to at least perform: - Map the parameters of the request affecting the service for the data session from the one or more PCC rules to the parameters to be exchanged between the H-SMF and the V-SMF, and provide the mapped parameters to the V-SMF in a session management message; and - Extend the session management message or context with the parameters of the request affecting the service for the data session that are not mapped to the existing parameters of the session management message.

20. The apparatus according to any one of claims 12 to 19, wherein the instructions are further configured to cause the apparatus to at least: - Provide the V-SMF with notification endpoint information for the V-SMF to use to send a notification to the AF via the home network.

21. The apparatus according to claim 20, wherein the instructions are further configured to cause the apparatus to at least: - Receive a request for a notification about an event on the data session, the request indicating that the notification is to include the notification endpoint information, wherein when the H-SMF does not provide its own notification endpoint information, the notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the home network exposure function H-NEF of the home network, and the request from the AF is received via the H-NEF; and - When the H-SMF does not provide its own notification endpoint information, provide the V-SMF with an indication that the provided notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the H-NEF.

22. The apparatus according to claim 20 or claim 21, wherein the instructions are further configured to cause the apparatus to at least: - Receive a notification request about an event on the data session, the request indicating that the notification is to include the notification endpoint information, wherein the notification endpoint information is the notification endpoint information associated with the AF or the notification endpoint information associated with the home network exposure function H-NEF of the home network; - Associate the notification endpoint information associated with the H-SMF with the received notification endpoint information; - Store the association between the notification endpoint information associated with the H-SMF and the received notification endpoint information; - Provide the V-SMF with the notification endpoint information associated with the H-SMF as the notification endpoint information to be used by the V-SMF to send a notification to the AF about an event on the data session; - Receive, from the V-SMF, a notification about an event sent using the notification endpoint information associated with the H-SMF; - Obtain the notification endpoint information to be used by the H-SMF to forward the notification about the event based on the association; And - Forward the notification about the event to the AF using the obtained notification endpoint information.

23. A device for communication, the device comprising: At least one processor; And At least one memory storing instructions for a visited session management function V-SMF of a visited network, the instructions, when executed by the at least one processor, cause the device to at least: - Receive, from a home session management function H-SMF of a home network, information on how to affect traffic routing for a data session in a handover split-off SBO mode of a home routed HR session served by the visited network, wherein the information on how to affect traffic routing for the data session includes a request to affect traffic for the data session received by the H-SMF from an application function AF; And - Configure at least a user plane UP function based on the received information on how to affect traffic routing for the data session.

24. The device according to claim 23, wherein the information on how to affect traffic routing for the data session further comprises one or more of the following: information for identifying the traffic, information on one or more data network access identifiers DNAIs of the visited network, an indication of traffic relevance, an indication of application relocation possibility, an indication of address reservation for a user equipment, a request to be notified when the UP path of the data session has changed.

25. The device according to claim 24, wherein the information on how to affect traffic routing for the data session further comprises, per DNAI, a traffic steering policy identifier and / or traffic routing information related to an interface between a user plane function UPF and a data network DN.

26. The device according to any one of claims 23 to 25, wherein the instructions are further configured to cause the device to at least: - Receive, from the H-SMF, a session management SM message or SM context comprising an information element or container that includes the information on how to affect traffic routing for the data session.

27. The device according to any one of claims 23 to 26, wherein the instructions are further configured to cause the device to at least: - Receive, from the H-SMF, offloading rules or information on how the visited network should affect traffic routing for the data session.

28. The device according to any one of claims 23 to 27, wherein the instructions are further configured to cause the device to at least: - Receive notification endpoint information from the H-SMF; and - Use the notification endpoint information to send a notification to the Application Function AF via the home network.

29. The apparatus according to claim 28, wherein the instructions are further configured to cause the apparatus to at least: - Receive an indication that the notification endpoint information received from the H-SMF is notification endpoint information associated with the AF or notification endpoint information associated with the Home Network Exposure Function H-NEF of the home network.

30. The apparatus according to claim 28 or claim 29, wherein the instructions are further configured to cause the apparatus to at least: - Send a notification to the H-SMF using the notification endpoint information.

31. A computer program product comprising program instructions stored on a computer-readable medium, which when executed by one or more computers, cause the one or more computers to perform the method according to any one of claims 1 to 11.

Images