Method and apparatus for user plane function selection

Abstract

Embodiments of the present disclosure provide a method and apparatus for local protocol data unit session anchor (PSA) selection. A method (300) performed by a first network node comprises: receiving (S302) a first data network access identifier (DNAI) list from a second network node; and selecting (S304) a user plane function (UPF) based at least on the first DNAI list. According to the embodiment of the invention, by receiving the first DNAI list, the first network node can select the UPF in time when needed. Therefore, the problem that the DNAI may not be used when the network node needs to select the UPF at a certain time point can be avoided.

Description

Technical Field

[0001] The present disclosure relates generally to communication network technology, and more particularly to a method and apparatus for user plane function (UPF) selection. Background Art

[0002] This section introduces aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light and should not be understood as an admission of what is or is not prior art.

[0003] In communication networks, many techniques are applied to improve performance.

[0004] For example, mobile edge computing (MEC) technology can be used to provide low latency between terminal devices (such as user equipment (UE)) and servers. To utilize MEC technology, a UPF should be selected from multiple UPFs that are connected to the server and capable of relatively high-speed communication with the server, such as an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a protocol data unit session anchor (PSA). Typically, the selected UPF should be close to the terminal device to achieve efficient service delivery by reducing end-to-end latency and load on the transport network. Summary of the invention

[0005] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0006] In order to select a UPF for a PDU session in edge computing, the network node should have information about the candidate UPFs. For example, in current communication standards (e.g., in the Third Generation Partnership Project Technical Specification 3GPP TS 23.502, V17.5.0 (2022-06)), such information can be included in a list, such as a list of interested data network access identifiers (DNAI). DNAI is a mandatory input for network nodes to select UPFs in edge computing. However, one problem is that DNAI may not be available when the network node needs to select a UPF at a certain point in time.

[0007] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Various embodiments are presented herein that solve one or more of the problems disclosed herein.

[0008] A first aspect of the present disclosure provides a method performed by a first network node. The method includes: receiving a first data network access identifier (DNAI) list from a second network node; and selecting a user plane function (UPF) based at least on the first DNAI list.

[0009] In an embodiment of the present disclosure, the UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0010] In an embodiment of the present disclosure, the method may further include: storing the first DNAI list.

[0011] In an embodiment of the present disclosure, the method may further include: receiving an updated first DNAI list from the second network node; and storing the updated first DNAI list.

[0012] In an embodiment of the present disclosure, selecting the UPF may include: acquiring a second DNAI list based at least on the first DNAI list and / or configuration; and selecting one or more UPFs based at least on the second DNAI list.

[0013] In an embodiment of the present disclosure, the second DNAI list is a list of DNAIs included in the first DNAI list and supported by the first network node.

[0014] In an embodiment of the present disclosure, the method may further include: before selecting any local UPF, selecting an uplink classifier or branch point to be inserted into the user plane data path.

[0015] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list.

[0016] In an embodiment of the present disclosure, the complete DNAI list is an interesting DNAI list of a protocol data unit (PDU) session, which excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0017] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0018] In an embodiment of the present disclosure, the second network node may include: a session management function (SMF).

[0019] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or an anchor SMF.

[0020] In an embodiment of the present disclosure, the first DNAI list may be received via at least one of the following: a Nsmf_PDUSession_Context (Nsmf_PDU session_context) response message, a Nsmf_PDUSession_Update (Nsmf_PDU session_update) request message, a Nsmf_PDUSession_Update (Nsmf_PDU session_update) response message or a Nsmf_PDUSession_Create (Nsmf_PDU session_create) response message.

[0021] In an embodiment of the present disclosure, the first I-SMF is a newly inserted I-SMF or a target I-SMF during inter-I-SMF mobility; alternatively, the first I-SMF may be an I-SMF inserted when the I-SMF is changed, or a target I-SMF.

[0022] In an embodiment of the present disclosure, the first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from non-third generation partnership project access to a fifth generation system.

[0023] A second aspect of the present disclosure provides a method performed by a second network node. The method includes: sending a first data network access identifier (DNAI) list to a first network node. The first DNAI list can be used by the first network node to select a user plane function (UPF) based at least on the first DNAI list.

[0024] In an embodiment of the present disclosure, the UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0025] In an embodiment of the present disclosure, the method may further include: receiving an updated first DNAI list from the PCF; and sending the updated first DNAI list to the first network node.

[0026] In an embodiment of the present disclosure, the first DNAI list may be used by the first network node to obtain a second DNAI list based at least on the first DNAI list and / or configuration, and to select one or more UPFs based at least on the second DNAI list.

[0027] In an embodiment of the present disclosure, the second DNAI list may be a list of DNAIs included in the first DNAI list and supported by the first network node.

[0028] In an embodiment of the present disclosure, the first network node selects an uplink classifier or branching point to be inserted into the user plane data path before selecting any local PSA.

[0029] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list.

[0030] In an embodiment of the present disclosure, the complete DNAI list is a list of interested DNAIs for a protocol data unit (PDU) session, which excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0031] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0032] In an embodiment of the present disclosure, the second network node may include: a session management function (SMF).

[0033] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or an anchor SMF.

[0034] In an embodiment of the present disclosure, the first DNAI list may be sent via at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response message.

[0035] In an embodiment of the present disclosure, the first I-SMF is a newly inserted I-SMF or a target I-SMF during inter-I-SMF mobility; alternatively, the first I-SMF may be an I-SMF inserted when the I-SMF is changed, or a target I-SMF.

[0036] In an embodiment of the present disclosure, the first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from non-third generation partnership project access to a fifth generation system.

[0037] A third aspect of the present disclosure provides a method performed by a system including a first network node and a second network node. The method includes: sending a first data network access identifier (DNAI) list by the second network node to the first network node; receiving the first DNAI list from the second network node by the first network node; and selecting a user plane function (UPF) for a PDU session by the first network node based at least on the first DNAI list.

[0038] In an embodiment of the present disclosure, the UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0039] In an embodiment of the present disclosure, the method may further include: storing, by the first network node, the first DNAI list.

[0040] In an embodiment of the present disclosure, the method may also include: receiving, by the second network node, an updated first DNAI list from the PCF; sending, by the second network node, the updated first DNAI list to the first network node; receiving, by the first network node, the updated first DNAI list from the second network node; and storing, by the first network node, the updated first DNAI list.

[0041] In an embodiment of the present disclosure, the selection of the UPF for the PDU session by the first network node includes: the first network node obtaining a second DNAI list based at least on the first DNAI list and / or configuration; and the first network node selecting one or more UPFs for the PDU session based at least on the second DNAI list.

[0042] In an embodiment of the present disclosure, the second DNAI list may be a list of DNAIs included in the first DNAI list and supported by the first network node.

[0043] In an embodiment of the present disclosure, the method further includes: before selecting any local UPF, selecting an uplink classifier or branch point to be inserted into the user plane data path.

[0044] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list.

[0045] In an embodiment of the present disclosure, the complete DNAI list is an interesting DNAI list of a protocol data unit (PDU) session, which excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0046] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0047] In an embodiment of the present disclosure, the second network node may include: a session management function (SMF).

[0048] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or an anchor SMF.

[0049] In an embodiment of the present disclosure, the first DNAI list may be received via at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response message.

[0050] In an embodiment of the present disclosure, the first I-SMF is a newly inserted I-SMF or a target I-SMF during inter-I-SMF mobility; alternatively, the first I-SMF may be an I-SMF inserted when the I-SMF is changed, or a target I-SMF.

[0051] In an embodiment of the present disclosure, the first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from non-third generation partnership project access to a fifth generation system.

[0052] A fourth aspect of the present disclosure provides an apparatus for a first network node. The apparatus for the first network node includes: a processor; and a memory. The memory includes instructions executable by the processor. The apparatus for the first network node is operable to: receive a first data network access identifier (DNAI) list from a second network node; and select a user plane function (UPF) based at least on the first DNAI list.

[0053] In an embodiment of the present disclosure, the device may also be used to execute the method according to any of the above embodiments.

[0054] A fifth aspect of the present disclosure provides an apparatus for a second network node. The apparatus for the second network node includes: a processor; and a memory. The memory includes instructions executable by the processor. The apparatus for the second network node is operable to: send a first data network access identifier (DNAI) list to a first network node. The first DNAI list can be used by the first network node to select a user plane function (UPF) based at least on the first DNAI list.

[0055] In an embodiment of the present disclosure, the device may also be used to execute the method according to any of the above embodiments.

[0056] A sixth aspect of the present disclosure provides a system, comprising: an apparatus for a first network node, and an apparatus for a second network node. The apparatus for the first network node comprises: a processor; and a memory. The memory comprises instructions executable by the processor. The apparatus for the first network node is operable to: receive a first data network access identifier (DNAI) list from the second network node; and select a UPF based at least on the first DNAI list. The apparatus for the second network node comprises: a processor; and a memory. The memory comprises instructions executable by the processor. The apparatus for the second network node is operable to: send a first data network access identifier (DNAI) list to the first network node. The first DNAI list can be used by the first network node to select a user plane function (UPF) based at least on the first DNAI list.

[0057] In an embodiment of the present disclosure, the system may also be operable to execute the method according to any of the above embodiments.

[0058] A seventh aspect of the present disclosure provides a computer-readable storage medium storing instructions, which, when executed by the at least one processor, causes the at least one processor to execute the method according to any of the above embodiments.

[0059] Another aspect of the present disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service. The host includes: a processing circuit configured to provide user data; and a network interface configured to initiate sending the user data to a network node in a cellular network for sending to a user equipment (UE). The network node has a communication interface and a processing circuit. The processing circuit of the network node is configured to perform any of the methods performed by the first network node and / or the second network node to send the user data from the host to the UE.

[0060] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application that provides the user data; and the UE includes a processing circuit, which is configured to execute a client application associated with the host application to receive the transmission of the user data from the host.

[0061] Another aspect of the present disclosure provides a method implemented in a host, the host being configured to operate in a communication system, the communication system also comprising a network node and a user equipment (UE). The method comprises: providing user data to the UE; and initiating a transmission to the UE carrying the user data through a cellular network including the network node. The network node performs any of the methods performed by the first network node and / or the second network node to send the user data from the host to the UE.

[0062] In an embodiment of the present disclosure, the method further includes, at the network node, sending the user data provided by the host for the UE.

[0063] In an embodiment of the present disclosure, the user data is provided at the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0064] Another aspect of the present disclosure provides a communication system configured to provide an over-the-top service. The communication system comprises: a host, the host comprising: a processing circuit configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate sending the user data to a cellular network node for sending to the UE. The network node has a communication interface and a processing circuit. The processing circuit of the network node is configured to perform any of the methods performed by the first network node and / or the second network node to send the user data from the host to the UE.

[0065] In an embodiment of the present disclosure, the communication system described in the previous embodiment further includes: the network node; and / or the user equipment.

[0066] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application to provide the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0067] Another aspect of the present disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service. The host includes: a processing circuit configured to initiate reception of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and a processing circuit. The processing circuit of the network node is configured to perform any of the methods performed by the first network node and / or the second network node to receive the user data for the host from the UE.

[0068] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application to provide the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0069] In an embodiment of the present disclosure, the initiating reception of the user data includes requesting the user data.

[0070] Another aspect of the present disclosure provides a method implemented by a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE). The method comprises: at the host, initiating reception of user data from the UE, the user data originating from a transmission received by the network node from the UE. The network node performs any of the methods performed by the first network node and / or the second network node, and receives the user data for the host from the UE.

[0071] In an embodiment of the present disclosure, the method of the aforementioned embodiment further includes, at the network node, sending the received user data to the host.

[0072] Another aspect of the present disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service. The host includes: a processing circuit configured to provide user data; and a network interface configured to initiate sending the user data to a cellular network for sending to a user equipment (UE). The UE includes a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the methods to receive the user data from the host.

[0073] In an embodiment of the present disclosure, the cellular network further comprises a network node, and the network node is configured to communicate with the UE to send the user data from the host to the UE.

[0074] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application to provide the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0075] Another aspect of the present disclosure provides a method implemented by a host operating in a communication system further comprising a network node and a user equipment (UE). The method comprises: providing user data for the UE; and initiating a transmission to the UE carrying the user data through a cellular network comprising the network node. The UE performs any of the methods performed by the first network node and / or the second network node to receive the user data from the host.

[0076] In an embodiment of the present disclosure, the method of the previous embodiment further includes: at the host, executing a host application associated with the client application executed on the UE to receive the user data from the UE.

[0077] In an embodiment of the present disclosure, the method of the previous embodiment further includes: at the host, sending input data to the client application executed on the UE, the input data being provided by executing the host application. The client application provides the user data in response to the input data from the host application.

[0078] Another aspect of the present disclosure provides a host configured to operate in a communication system to provide an over-the-top (OTT) service. The host includes: a processing circuit configured to utilize user data; and a network interface configured to receive transmission of the user data to a cellular network for transmission to a user equipment (UE). The UE includes a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the methods to transmit the user data to the host.

[0079] In an embodiment of the present disclosure, the cellular network further comprises a network node, and the network node is configured to communicate with the UE to send the user data from the UE to the host.

[0080] In an embodiment of the present disclosure, the processing circuit of the host is configured to execute a host application to provide the user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0081] Another aspect of the present disclosure provides a method implemented by a host, the host being configured to operate in a communication system further comprising a network node and a user equipment (UE). The method comprises: receiving, at the host, user data sent by the UE to the host via the network node. The UE performs any of the methods performed by the first network node and / or the second network node to send the user data to the host.

[0082] In an embodiment of the present disclosure, the method of the aforementioned embodiment further includes: at the host, executing a host application associated with the client application executed on the UE to receive the user data from the UE.

[0083] In an embodiment of the present disclosure, the method of the aforementioned embodiment further includes: at the host, sending input data to the client application executed on the UE, the input data being provided by executing the host application. The user data is provided by the client application in response to the input data from the host application.

[0084] Embodiments herein have many advantages. According to embodiments of the present disclosure, an improved method and an improved apparatus for local protocol data unit session anchor (PSA) selection may be provided.

[0085] In particular, by receiving the first DNAI list and selecting a UPF, such as an I-UPF, a V-UPF or a PSA, based at least on the first DNAI list, the first network node can select a UPF in time to save some signaling transactions between the first network node and the second network node, thereby reducing signaling delays. Therefore, the problem that the DNAI may not be available when the network node needs to select a UPF at a certain point in time will be avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] The above and other aspects, features and advantages of various embodiments of the present disclosure will become more fully apparent through, for example, the following detailed description with reference to the accompanying drawings, in which similar reference numerals or letters are used to represent similar or equivalent elements. In order to facilitate a better understanding of the embodiments of the present disclosure, the accompanying drawings are shown, and the drawings are not necessarily drawn to scale, wherein:

[0087] Figure 1A is a signaling diagram for simultaneous change of branching points or UL CL and additional PSA controlled by different I-SMFs.

[0088] Figure 1B is the signaling diagram of UE triggered service request procedure with I-SMF insertion / change / removal.

[0089] Figure 1C It is the signaling diagram for N2-based handover,preparation phase between NG-RAN nodes, with I-SMF insertion / change / removal.

[0090] Figure 1D It is the signaling diagram used for PDU session creation.

[0091] Figure 2 is a diagram illustrating a problem of simultaneous changes in branch points or UL CL and additional PSA controlled by different I-SMFs.

[0092] Figure 3A is an exemplary flow chart of a method performed by a first network node according to an exemplary embodiment of the present disclosure.

[0093] Figure 3B is a diagram showing an exemplary embodiment according to the present disclosure Figure 3A An exemplary flow chart of additional steps of the method shown in .

[0094] Figure 3C is a diagram showing an exemplary embodiment according to the present disclosure Figure 3A An exemplary flow chart of further additional steps of the method shown in .

[0095] Figure 3D is a diagram showing an exemplary embodiment according to the present disclosure Figure 3A An exemplary flow chart of the sub-steps of the method shown in .

[0096] Figure 4A is an exemplary flow chart of a method performed by a second network node according to an exemplary embodiment of the present disclosure.

[0097] Figure 4B According to an exemplary embodiment of the present disclosure, Figure 4A An exemplary flow chart of additional steps of the method shown in .

[0098] Figure 5A is an exemplary flow chart of a method performed by a system including a first network node and a second network node according to an exemplary embodiment of the present disclosure.

[0099] Figure 5B According to an exemplary embodiment of the present disclosure, Figure 5A An exemplary flow chart of additional steps of the method shown in .

[0100] Figure 5C According to an exemplary embodiment of the present disclosure, Figure 5A An exemplary flow chart of further additional steps of the method shown in .

[0101] Fig. 6A is a diagram showing a solution of simultaneous change of ULCL / BP and additional PSA controlled by an inserted I-SMF according to an embodiment of the present disclosure.

[0102] Figure 6B is a diagram illustrating a solution of simultaneous change of UL CL / BP controlled by a changed I-SMF and additional PSA according to an embodiment of the present disclosure.

[0103] Figure 6C is a diagram showing a PDU session establishment procedure, in which a first DNAI list (fullDaniList) is sent to a first network node (inserted I-SMF).

[0104] Fig.6D is a diagram showing a process during which a first DNAI list (fullDaniList) is sent to a first network node (inserted I-SMF).

[0105] Fig. 6E This is a diagram showing a process during which the latest fullDnaiList is notified from the PCF to the I-SMF.

[0106] Fig. 7A is a block diagram illustrating an exemplary apparatus of a first network node suitable for performing a method according to an embodiment of the present disclosure.

[0107] Figure 7B is a block diagram illustrating an exemplary apparatus of a second network node suitable for performing a method according to an embodiment of the present disclosure.

[0108] Figure 7C is a block diagram illustrating an exemplary system including a first network node and a second network node.

[0109] Figure 8 is a block diagram illustrating a device / computer-readable storage medium according to an embodiment of the present disclosure.

[0110] Fig. 9A is a block diagram illustrating modules of a first network node suitable for performing a method according to an embodiment of the present disclosure.

[0111] Fig. 9Bis a block diagram illustrating modules of a second network node suitable for performing a method according to an embodiment of the present disclosure.

[0112] Fig.10 An example of a communication system 1000 is shown in accordance with some embodiments.

[0113] Fig.11 A UE 1100 is shown in accordance with some embodiments.

[0114] Fig.12 A network node 1200 is shown according to some embodiments.

[0115] Fig.13 is a block diagram of a host 1300 according to various aspects described herein, and the host 1300 may be Fig.10 An embodiment of host 1016.

[0116] Fig.14 is a block diagram illustrating a virtualization environment 1400 in which functionality implemented by some embodiments may be virtualized.

[0117] Fig.15 A communication diagram is shown in which a host 1502 communicates with a UE 1506 through a network node 1504 over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION

[0118] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thus implement the present disclosure, rather than suggesting any limitation to the scope of the present disclosure. References to features, advantages or similar language throughout this specification do not mean that all features and advantages that can be implemented by the present disclosure should be in or present in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages is understood to mean specific features, advantages or characteristics described in conjunction with the embodiments included in at least one embodiment of the present disclosure. In addition, the described features, advantages and characteristics of the present disclosure may be combined in one or more embodiments in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, which may not be present in all embodiments of the present disclosure.

[0119] Generally, unless different meanings are clearly given and / or implied in the context of using the term, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless otherwise clearly stated, all references to one / an / the element, device, assembly, part, step, etc. should be openly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0120] As used herein, the term "network" or "communication network" refers to a network (e.g., an Internet network or any wireless network) that complies with any appropriate communication standard. For example, wireless communication standards may include New Radio (NR), Long Term Evolution (LTE), Advanced LTE, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. In the following description, the terms "network" and "system" may be used interchangeably. In addition, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to wireless communication protocols or wired communication protocols defined by standard organizations (e.g., the Third Generation Partnership Project (3GPP)).

[0121] The term "network node" used herein refers to a network device or network entity or network function or any other device (physical or virtual) in a communication network. For example, a network node in a network may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a server node / function (e.g., a service capability server / application server (SCS / AS), a group communication service application server (GCS AS), an application function (AF)), an open node / function (e.g., a service capability exposure function (SCEF), a network exposure function (NEF)), a unified data management (UDM), a home subscriber server (HSS), a session management function (SMF), an access and mobility management function (AMF), a mobility management entity (MME), a controller, or any other suitable device in a wireless communication network. A BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as a femto, a micro, etc.).

[0122] In addition, the terms "network node", "network function", "network entity" in this document may also refer to any suitable node, function, entity that can be implemented (physically or virtually) in a communication network. For example, a 5G system (5GS) may include multiple NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), etc. In other embodiments, for example, depending on the specific network, the network function may include different types of NFs (such as PCRF (Policy and Charging Rules Function), etc.).

[0123] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. As an example and not a limitation, a terminal device may refer to a mobile terminal, a user equipment (UE), or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client device (CPE), etc. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate according to one or more communication standards promulgated by 3GPP (e.g., LTE and / or NR standards of 3GPP). As used herein, a "user equipment" or "UE" may not necessarily have a "user" in terms of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network on a predetermined schedule. In contrast, a UE may represent a device that is intended to be sold to or operated by a human user but may not, or may not initially, be associated with a specific human user.

[0124] As yet another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring, sensing and / or measurement, etc. and transmits the results of such monitoring, sensing and / or measurement, etc. to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (such as watches), etc. In other cases, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0125] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0126] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the example embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0127] As used herein, the phrase "at least one of A and / or B" should be understood to mean "only A, only B, or both A and B". The phrase "A and / or B" should be understood to mean "only A, only B, or A and B".

[0128] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "comprises, comprising", "has, having", and / or "includes, including" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0129] It should be noted that the terms used in this article are only used to facilitate the description and distinction of nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.

[0130] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0131] As an example of UPF selection, the following scenario is shown.

[0132] In TS 23.502 (V17.5.0), which is incorporated herein by reference in its entirety, some exemplary scenarios are defined as follows.

[0133] 4.23.9 Branching point or UL CL controlled by I-SMF

[0134] 4.23.9.0 Overview

[0135] The procedures in this section describe the addition, removal and change of PDU Session Anchor Points (PSA2), Branch Points or UL CL controlled by I-SMF. They all rely on the following principles:

[0136] 1. When a (new) I-SMF is inserted (e.g. as described in Section 4.23.7 ​​or Section 4.23.11), the I-SMF provides the SMF with List of supported DNAIs This list is assumed to remain unchanged during the N16a association between the I-SMF and the SMF for a PDU session.

[0137] 2. Based on the DNAI list information received from the I-SMF, the SMF can then provide or update the I-SMF with the List of DNAIs of interest for this PDU Session. This can happen, for example, when the I-SMF provides a list of DNAIs it supports, or When the SMF receives new, updated or removed PCC rules (as defined in section 4.23.6). The Interest DNAI List indicates to the I-SMF the list of candidate DNAIs for local service steering within the PDU Session.

[0138] …

[0139] 4.23.9.5 Simultaneous changes of branch points or UL CL controlled by different I-SMFs

[0140] This section describes the simultaneous changes of UL-CL / BP functionality and additional PSA, such as the addition of a new UL CL / BP and PDU session anchor (i.e., PSA2) and the release of an existing UL CL / BP and PDU session anchor (i.e., PSA0), where both the target UPF and the source UPF are controlled by different I-SMFs.

[0141] This process can be triggered after N2 handover or Xn-based handover process.

[0142] …(See Figure 1A )

[0143] Figure 4.23.9.5-1: Simultaneous change of branch point or UL CL and additional PSA controlled by different I-SMFs

[0144] 1. The UE has established a PDU session with the source branching point or UL CL, the source UPF (PSA0) controlled by the source I-SMF, and the remote PSA. The UE has mobility with a change of I-SMF, such as switching from the source RAN to the target RAN. After the mobility, the path between the target I-UPF and the remote PSA (PSA1) has been established.

[0145] 2. This step is related to chapter Same as step 2 in 4.23.9.3.

[0146] 3. Same as step 3 in Figure 4.23.9.4-1.

[0147] 4. Same as step 4 in Figure 4.23.9.4-1.

[0148] 5. Same as step 5 in Figure 4.23.9.4-1.

[0149] …

[0150] (See Section 4.23.9.3 Step 2:

[0151] 2. At some point, the I-SMF decides to establish a new PDU Session Anchor and release the existing PDU Session Anchor, for example due to UE mobility. The I-SMF selects the UPF and uses N4 to establish a new PDU Session Anchor for the PDU Session 2. )

[0152] (See Figure 4.23.9.4-1, steps 3-5 in TS 23.502 (V17.5.0):

[0153] 3. The I-SMF selects the UPF and uses N4 to establish the target UL CL or BP for the PDU session.

[0154] 4. I-SMF calls the Nsmf_PDUSession_Update (Nsmf_PDU Session_Update) request to SMF (indicating service offloading changes, (newly allocated IPv6 prefix @PSA2, (multiple) DNAIs supported by PSA2), (removed IPv6 prefix @PSA0, (multiple) DNAIs supported by PSA0), DL tunnel information of new UL CL / branching point).

[0155] The DL tunnel information of the target UL CL / branching point is provided to the SMF.

[0156] 5. The SMF updates the remote PSA (PSA1) via N4 with the DL tunnel information of the target UL CL / BP for downlink traffic.

[0157] 4.23.4.3 UE-triggered service request with I-SMF insertion / change / removal

[0158] …

[0159] …(See Figure 1B )

[0160] Figure 4.23.4.3-1: UE-triggered service request procedure with I-SMF insertion / change / removal

[0161] …

[0162] Scenario: I-SMF insertion or I-SMF change, for I-SMF removal case, skip steps 3-9.

[0163] 3. If AMF selects a new I-SMF, AMF sends a Nsmf_PDUSession_CreateSMContext (Nsmf_PDU Session_Create SM Context) request (PDU Session ID, SM Context ID, UE location information, access type, RAT type, operation type) to the new I-SMF. In the case of I-SMF change, the SM Context ID points to the old I-SMF, or in the case of I-SMF insertion, it points to the SMF.

[0164] 4a. The new I-SMF requests (SM Context type, SM context ID) from the old I-SMF (in case of I-SMF change) or SMF (in case of I-SMF insertion) Next) Retrieve SM context The New-I-SMF performs this service operation using the SM Context ID received from the AMF. The recipient of the Nsmf_PDUSession_Context request uses the SM Context ID to determine the target PDU Session. The SM Context Type indicates that the requested information is all SM contexts, i.e., PDN Connection Context and 5G SM Context.

[0165] 4b. The old I-SMF in case of I-SMF change or the SMF in case of I-SMF insertion responds with the SM context of the indicated PDU session.

[0166] 5. The new I-SMF selects a new I-UPF: Based on the received SM context (e.g. S-NSSAI) and UE location information, the new I-SMF selects a new I-UPF as described in section 6.3.3 of TS 23.501 [2].

[0167] 6. The new I-SMF initiates N4 session establishment to the new I-UPF. The new I-UPF provides a tunnel endpoint for the new I-SMF.

[0168] 7a. If a tunnel endpoint for cached DL data has been allocated, in the event of a change in the I-SMF, the new I-SMF calls Nsmf_PDUSession_UpdateSMContext (Nsmf_PDU session_Update SM context) request (tunnel endpoint for cached DL data) to the old I-SMF to establish a forwarding tunnel. The new I-SMF performs this service operation using the SM context ID received from the AMF.

[0169] 7b. In the case of I-SMF change, the old I-SMF initiates N4 session modification to the old I-UPF to send the tunnel endpoint of the buffered DL data to the old I-UPF. After this step, the old I-UPF starts sending the buffered DL data to the new I-UPF.

[0170] 7c. In case of I-SMF change, the old I-SMF responds to the new I-SMF using Nsmf_PDUSession_UpdateSMContext response.

[0171] 8a. In the case of I-SMF change, the new I-SMF calls the Nsmf_PDUSession_Update request to the SMF (SM context ID, new I-UPF DL tunnel information, SM context ID at I-SMF, access type, RAT type, New I-SMF support List of DNAI , operation type). The new I-SMF uses the SM context ID at the SMF received from the old I-SMF to perform this service operation.

[0172] In the case of I-SMF insertion, the new I-SMF calls Nsmf_PDUSession_Create (Nsmf_PDU session_create) request to SMF (new I-UPF DL tunnel information, new I-UPF tunnel endpoint for cached DL data, SM context ID at I-SMF, access type, RAT type, List of DNAIs supported by the new I-SMF , operation type).

[0173] 8b.SMF initiates N4 session modification to the PDU session anchor UPF. In this step:

[0174] -SMF provides new I-UPF DL tunnel information.

[0175] - If the PSA UPF needs to use different CN tunnel information, that is, the CN tunnel information for N3 and N9 at the PSA is different, the CN tunnel information used for the PDU session anchor UPF is allocated.

[0176] - For I-SMF insertion, if a new I-UPF tunnel endpoint for buffered DL data is received, the SMF triggers the transfer of the buffered DL data to the new I-UPF tunnel endpoint for buffered DL data.

[0177] If the DL tunnel information has changed, the SMF instructs the UPF (PSA) to send one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to the new I-UPF. From now on, the PDU session anchor UPF starts sending DL data to the new I-UPF as indicated in the new I-UPF DL tunnel information. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to the new I-UPF. If the new I-SMF indicates in step 6, the new I-UPF reports to the SMF upon receiving the "end marker". The new SMF initiates the N4 session modification procedure to instruct the new I-UPF to send the DL packets received from the UPF (PSA).

[0178] 8c. The SMF responds with an Nsmf_PDUSession_Update response (for the DNAI of interest for this PDU Session in case of I-SMF change) or an Nsmf_PDUSession_Create response (if allocated in step 8b, for the DNAI of interest for this PDU Session in case of I-SMF insertion). DNAI of interest for this PDU session , tunnel information at UPF (PSA) for UL data) to respond to the new I-SMF.

[0179] 9. The new I-SMF sends Nsmf_PDUSession_CreateSMContext response (N2 SM information (PDU session ID, (multiple) QFI, (multiple) QoS profile, CN N3 tunnel information, S-NSSAI, user plane security enforcement, UE integrity protection maximum data rate), N1 SM container, cause) to AMF. The CN N3 tunnel information is the UL tunnel information of the new I-UPF. ...

[0181] 4.23.7.3 N2-based handover between NG-RAN nodes with I-SMF insertion / change / removal ...

[0183] ...(See Figure 1C )

[0184] Figure 4.23.7.3.2-1: N2-based handover between NG-RAN nodes, preparation phase, with I-SMF insertion / change / removal ...

[0186] 4a. (I-SMF change case) Target I-SMF to source I-SMF: The target I-SMF retrieves the SM context from the source I-SMF by calling Nsmf_PDUSession_Context request (SM context type, SM context ID).

[0187] The target I-SMF performs this service operation using the SM Context ID received from the T-AMF. The SM Context Type indicates that the requested information is all SM contexts, i.e., PDN connection context and 5G SM context. The recipient of the Nsmf_PDUSession_Context request uses the SM Context ID to determine the target PDU Session.

[0188] 4b. Source I-SMF to target I-SMF: Nsmf_PDUSession_Context response. The source I-SMF responds with the requested SM context.

[0189] Scenario: I-SMF insertion, for the scenario where I-SMF is changed, skip step 5.

[0190] 5a. Target I-SMF to SMF: The target I-SMF retrieves the SM context from the SMF by calling Nsmf_PDUSession_Context request (SM context type, SM context ID).

[0191] …

[0192] In TS 29.502 (V17.5.0) (the entire contents of which are incorporated herein by reference), some exemplary scenarios are defined as follows.

[0193] 5.2.2.7 Create Service Operation

[0194] 5.2.2.7.1 Overview

[0195] The Create Service operation shall be used to create a separate PDU Session in the H-SMF for HR roaming scenarios, or to create a separate PDU Session in the SMF for PDU Sessions involving the I-SMF.

[0196] It is used in the following processes:

[0197] - The UE requests a PDU session establishment with or without I-SMF intervention (see sections 4.3.2.2.2 and 4.23.5.1 of 3GPP TS 23.502 [3]);

[0198] - when the I-SMF is inserted during registration, service request, N2-based handover between NG-RAN nodes, Xn-based handover, handover from EPC / ePDG to 5GS, and handover from non-3GPP to 3GPP access procedures (see sections 4.23.3, 4.23.4, 4.23.7.3, 4.23.11.2 and 4.23.16 of 3GPP TS 23.502 [3]);

[0199] - EPS to 5GS idle mode mobility or handover using the N26 interface (see sections 4.11, 4.23.12.3, 4.23.12.5 and 4.23.12.7 of 3GPP TS 23.502 [3]);

[0200] - EPS to 5GS mobility without N26 interface (see section 4.11.2.3 of 3GPP TS 23.502 [3]);

[0201] - switching a PDU session between 3GPP access and non-3GPP access when the target AMF is not aware of the SMF resource identifier of the SM context used by the source AMF, for example when the target AMF is not in the PLMN of the N3IWF (see section 4.9.2.3.2 of 3GPP TS 23.502 [3]);

[0202] - Handover from EPS to 5GC-N3IWF (see section 4.11.3.1 of 3GPP TS 23.502 [3]);

[0203] -Switch from EPC / ePDG to 5GS (see section 4.11.4.1 of 3GPP TS 23.502 [3]).

[0204] The NF service consumer (e.g. V-SMF or I-SMF) shall create a PDU Session in an SMF (i.e. H-SMF for HR PDU Session, or SMF for PDU Session involving I-SMF) by using HTTP POST method as shown in Figure 5.2.2.7.1-1.

[0205] …(See Figure 1D )

[0206] Figure 5.2.2.7.1-1: PDU session creation

[0207] …

[0208] Table 6.1.6.2.9-1: Definition of type PduSessionCreateData (Pdu session creation data)

[0209]

[0210] Table 6.1.6.2.10-1: Definition of type PduSessionCreatedData (data created by Pdu session)

[0211]

[0212] 6.1.6.2.39 Type: SmContext

[0213] Table 6.1.6.2.39-1: Definition of type SmContext

[0214]

[0215]

[0216]

[0217]

[0218]

[0219]

[0220]

[0221] In these example scenarios, there are several problems.

[0222] Figure 2 is a diagram illustrating a problem of simultaneous changes in branch points or UL CL and additional PSA controlled by different I-SMFs.

[0223] In the scenario of simultaneous change of I-SMF or V-SMF or PSA controlled by different I-SMFs, such as branching point or UL CL and additional PSA, there are two signaling processing ways.

[0224] In application scenario 1, the change of ULCL / BP and local PSA is performed after the mobility process (Xn or N2 mobility). There is no problem with this signaling processing method.

[0225] In application scenario 2, the change of ULCL / BP and local PSA is embedded in the mobility procedure. The picture in section 4.23.9.5 of TS 23.502 (V17.5.0) indicates this scenario.

[0226] As stated in TS 23.502:

[0227] - In case of I-SMF change, the new I-SMF calls Nsmf_PDUSession_Update request to SMF (SM context ID, new I-UPF DL tunnel information, SM context ID at I-SMF, access type, RAT type, list of DNAIs supported by the new I-SMF, operation type). The new I-SMF performs this service operation using the SM context ID at SMF received from the old I-SMF.

[0228] - In case of I-SMF insertion, the new I-SMF calls Nsmf_PDUSession_Create request to SMF (new I-UPF DL tunnel information, new I-UPF tunnel endpoint for cached DL data, SM context ID at I-SMF, access type, RAT type, list of DNAIs supported by the new I-SMF, operation type).

[0229] -…

[0230] - The SMF responds to the new I-SMF with an Nsmf_PDUSession_Update response (the DNAI(s) of interest for this PDU session in case of I-SMF change) or an Nsmf_PDUSession_Create response (if it allocated in step 8b the DNAI(s) of interest for this PDU session, tunnel information at the UPF (PSA) for UL data in case of I-SMF insertion).

[0231] -…

[0232] Please refer to the following TS 23.502 description, SMF provides a "list of interesting (multiple) DNAIs" based on the DNAI list information received from I-SMF.

[0233] 4.23.5.1PDU session establishment process

[0234] ...The I-SMF provides the SMF with a list of the DNAIs it supports, and the SMF provides the I-SMF with the DNAI(s) of interest for this PDU session based on the DNAI list information received from the I-SMF, as defined in step 1 of Figure 4.23.9.1-1.

[0235] 4.23.9 Branching point or UL CL controlled by I-SMF ...

[0237] 2. Based on the DNAI list information received from the I-SMF, the SMF may then provide or update the list of interesting (multiple) DNAIs for this PDU session to the I-SMF at any time. This may occur, for example, when the I-SMF provides its supported list of DNAIs, or when the SMF receives new, updated or removed (multiple) PCC rules, as defined in section 4.23.6. The list of interesting (multiple) DNAIs for this PDU session indicates to the I-SMF the list of candidate (multiple) DNAIs for local traffic steering within the PDU session.

[0238] According to the above standard description, in the case of I-SMF change / insertion, the DNAI(s) of interest for this PDU session is the final common list of DNAI(s) of interest for this PDU session and the list of DNAI(s) supported by the new I-SMF, which is generated by excluding the list of DNAI(s) not supported by the I-SMF.

[0239] For TS 23.502, 4.23.9.5 application scenario 2, there are the following two problems:

[0240] For problem 1, during the mobility process, the I-SMF changes, and the UL CL and local PSA also change. When the I-SMF changes, the local PSA needs to be selected immediately, and DNAI is a mandatory input for the I-SMF to select the local PSA. ask The problem is that DNAI was not available at that point in time , the interested (multiple) DNAIs of this PDU session need to wait for the post procedure Nsmf_PDUSession_Update request / response with the anchor SMF. Alternatively, the I-SMF may select only the I-UPF and wait for the post procedure Nsmf_PDUSession_Update request / response to obtain the interested dnailist to select the new UL CL / PSA0, and then if the combined UL CL / PSA0 is selected, the previous I-UPF may need to be removed.

[0241] For question 2, during the mobility process, an I-SMF is inserted, and the UL CL and local PSA change at the same time. When the I-SMF is inserted, the local PSA needs to be selected immediately, and DNAI is a mandatory input for the I-SMF to select the local PSA. The problem is that DNAI at that time Interval is not available , the interested (multiple) DNAIs of this PDU session need to wait for the post-procedure Nsmf_PDUSession_Create request / response with the anchor SMF. Alternatively, the I-SMF may select only the I-UPF and wait for the post-procedure Nsmf_PDUSession_Update request / response to obtain the interested dnailist to select the new UL CL / PSA0, and then if the combined UL CL / PSA0 is selected, the previous I-UPF may need to be removed.

[0242] Generally speaking, without DANI list information, the simultaneous change of branch points or UL CL and additional PSA controlled by different I-SMFs in application scenario 2 in TS 23.502, 4.23.9.5 cannot be achieved, or the UL CL / PSA cannot be selected as early as possible.

[0243] For question 3, it is not optimal and flexible to let the anchor SMF generate the dnai of interest. For example, if the I-SMF changes the list of locally supported DNAs, it needs to always notify the anchor SMF to generate the dnai of interest. The embodiment of the present disclosure can let the I-SMF generate it.

[0244] In order to solve the above problems, the embodiments of the present disclosure propose the following solutions.

[0245] Figure 3A is an exemplary flow chart of a method performed by a first network node according to an exemplary embodiment of the present disclosure.

[0246] like Figure 3A As shown, the method 300 includes: step S302, receiving a first data network access identifier (DNAI) list from a second network node; and step S304, selecting a user plane function (UPF) based at least on the first DNAI list.

[0247] In an embodiment of the present disclosure, the UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0248] According to an embodiment of the present disclosure, an improved method and an improved apparatus for UPF (eg, I-UPF, V-UPF) or protocol data unit session anchor (PSA) selection may be provided.

[0249] Specifically, by receiving the first DNAI list, the first network node can select a UPF based on at least one first DNAI list in a timely manner when needed, thereby avoiding the problem that the DNAI may be unavailable when the network node needs to select a UPF at a certain time point.

[0250] Figure 3B According to an exemplary embodiment of the present disclosure, Figure 3A An exemplary flow chart of additional steps of the method shown in .

[0251] like Figure 3B As shown, in an embodiment of the present disclosure, method 300 may further include: step 303, storing the first DNAI list.

[0252] Figure 3C According to an exemplary embodiment of the present disclosure, Figure 3A An exemplary flow chart of further additional steps of the method shown in .

[0253] like Figure 3CAs shown, in an embodiment of the present disclosure, the method 300 may further include: step S308, receiving an updated first DNAI list from the second network node; and step S310, storing the updated first DNAI list.

[0254] Figure 3D According to an exemplary embodiment of the present disclosure, Figure 3A An exemplary flow chart of the sub-steps of the method shown in .

[0255] like Figure 3D As shown, selecting UPF includes: sub-step S3041, obtaining a second DNAI list based at least on the first DNAI list and / or configuration; and sub-step S3042, selecting one or more UPFs (for example, which may be a new local PSA) for a PDU session (especially in edge computing) based at least on the second DNAI list.

[0256] In an embodiment of the present disclosure, the method may further include: before selecting any local UPF (for example, which may specifically be a new local PSA), step S3031, selecting an uplink classifier or branch point to be inserted into the user plane data path, for example, for a PDU session.

[0257] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list. The second DNAI list may be a list of DNAIs included in the first DNAI list and supported by the first network node.

[0258] In an embodiment of the present disclosure, the complete DNAI list is an interesting DNAI list of a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0259] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0260] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or a session management function (SMF).

[0261] In an embodiment of the present disclosure, the first DNAI list may be received through an Nsmf_PDUSession_Context response, and / or an Nsmf_PDUSession_Update request and / or response, and / or an Nsmf_PDUSession_Create response message.

[0262] In the embodiment of the present disclosure, the first I-SMF may be an I-SMF newly inserted during the inter-I-SMF movement process, or a target I-SMF. Alternatively, the first I-SMF may be an I-SMF inserted when the I-SMF is changed, or a target I-SMF.

[0263] In an embodiment of the present disclosure, the second network node may include: an anchor SMF.

[0264] In an embodiment of the present disclosure, the first DNAI list may be received via at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update request response message, or a Nsmf_PDUSession_Create response message.

[0265] In an embodiment of the present disclosure, the first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from non-third generation partnership project access to third generation partnership project access (particularly a fifth generation system).

[0266] According to an embodiment of the present disclosure, the first network node (e.g., an inserted / changed I-SMF or V-SMF) generates a second DNAI list (e.g., "a common supported Dnai list of I-SMF and SMF") based on a local configuration (e.g., a supported Dnai list of the local configuration of the I-SMF) and a received first DNAI list (e.g., a new fullDnailList). This means that the I-SMF generates an "interested Dnai list" by itself.

[0267] In particular, for certain scenarios such as simultaneous change of ULCL / BP and additional PSA controlled by different I-SMFs applied during mobility procedures (TS 23.502 4.23.9.5), the changed I-SMF can select a local PSA.

[0268] Furthermore, for other scenarios such as simultaneous change of ULCL / BP and additional PSA controlled by different I-SMFs applied during mobility procedures (TS 23.502 4.23.9.5), the inserted I-SMF can select a local PSA.

[0269] Figure 4Ais an exemplary flow chart of a method performed by a second network node according to an exemplary embodiment of the present disclosure.

[0270] like Figure 4A As shown, the method 400 includes: step S402, sending a first data network access identifier (DNAI) list to a first network node. The first DNAI list can be used by the first network node to select a user plane function (UPF) for a PDU session based at least on the first DNAI list.

[0271] In an embodiment of the present disclosure, the local UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0272] Figure 4B According to an exemplary embodiment of the present disclosure, Figure 4A An exemplary flow chart of additional steps of the method shown in .

[0273] like Figure 4B As shown, in an embodiment of the present disclosure, the method 400 may further include: step S404, receiving an updated first DNAI list from the PCF; and step S406, sending the updated first DNAI list to the first network node.

[0274] In an embodiment of the present disclosure, the first DNAI list is used for the first network node to obtain the second DNAI list based at least on the first DNAI list and / or configuration, and to select one or more UPFs (for example, which may be a new I-UPF, V-UPF or local PSA) for the PDU session based at least on the second DNAI list.

[0275] In an embodiment of the present disclosure, the first network node selects an uplink classifier or branching point to be inserted into the user plane data path of the PDU session before selecting any local UPF (eg, which may be a new local PSA).

[0276] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list. The second DNAI list may be a list of DNAIs included in the first DNAI list and supported by the first network node.

[0277] In an embodiment of the present disclosure, the complete DNAI list is a list of DNAIs of interest for a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0278] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0279] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or a session management function (SMF).

[0280] In an embodiment of the present disclosure, the first DNAI list may be sent through at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a response message, or a Nsmf_PDUSession_Create response message.

[0281] In the embodiments of the present disclosure, the first I-SMF may be a newly inserted I-SMF in the inter-I-SMF mobility process, or a target I-SMF.

[0282] In an embodiment of the present disclosure, the second network node may include: an anchor SMF.

[0283] In an embodiment of the present disclosure, the first DNAI list may be received through an Nsmf_PDUSession_Context response message, and / or an Nsmf_PDUSession_Update request message and / or response message, and / or an Nsmf_PDUSession_Create response message.

[0284] In an embodiment of the present disclosure, the first I-SMF may be an I-SMF inserted when changing the I-SMF, or a target I-SMF. The first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to the fifth generation system, and / or handover from non-third generation partnership project access to third generation partnership project access (fifth generation system).

[0285] Figure 5A is an exemplary flow chart of a method performed by a system including a first network node and a second network node according to an exemplary embodiment of the present disclosure.

[0286] like Figure 5AAs shown, the method 500 executed by the system includes: step S502, the second network node sends a first data network access identifier (DNAI) list to the first network node; step S504, the first network node receives the first DNAI list from the second network node; step S506, the first network node selects a user plane function (UPF) based at least on the first DNAI list.

[0287] In an embodiment of the present disclosure, the local UPF includes at least one of the following for a protocol data unit (PDU) session: an intermediate UPF (I-UPF), a visited UPF (V-UPF), or a local protocol data unit session anchor (PSA).

[0288] Figure 5B According to an exemplary embodiment of the present disclosure, Figure 5A An exemplary flow chart of additional steps of the method shown in .

[0289] In an embodiment of the present disclosure, the method 500 may further include: step S505, storing the first DNAI list by the first network node.

[0290] In an embodiment of the present disclosure, method 500 may also include: step S508, the second network node receives the updated first DNAI list from the PCF; step S510, the second network node sends the updated first DNAI list to the first network node; step S512, the first network node receives the updated first DNAI list from the second network node; and step S514, the first network node stores the updated first DNAI list.

[0291] Figure 5C According to an exemplary embodiment of the present disclosure, Figure 5A An exemplary flow chart of the sub-steps of the method shown in .

[0292] In an embodiment of the present disclosure, the selection of UPF by the first network node for the terminal device includes: sub-step S5061, the first network node obtains the second DNAI list based on at least the first DNAI list and / or configuration; sub-step S5062, the first network node selects one or more UPFs (for example, a new I-UPF, or a V-UPF, or a local PSA) for the PDU session based on at least the second DNAI list.

[0293] In an embodiment of the present disclosure, the method may further include: before selecting any local PSA (for example, it may be a new local PSA), step S5051, selecting an uplink classifier or branch point to be inserted into the user plane data path of the PDU session.

[0294] In an embodiment of the present disclosure, the first DNAI list may be a complete DNAI list. The second list of DNAIs may be a list of DNAIs included in the first DNAI list and supported by the first network node.

[0295] In an embodiment of the present disclosure, the complete DNAI list is an interesting DNAI list of a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

[0296] In an embodiment of the present disclosure, the first network node may include: a first intermediate session management function (I-SMF), or a first V-SMF.

[0297] In an embodiment of the present disclosure, the second network node may include: a second intermediate session management function (I-SMF), or a second V-SMF, or a session management function (SMF).

[0298] In an embodiment of the present disclosure, the first DNAI list may be received via at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response message.

[0299] In the embodiments of the present disclosure, the first I-SMF may be a newly inserted I-SMF or a target I-SMF in the inter-I-SMF mobility process.

[0300] In an embodiment of the present disclosure, the second network node may include: an anchor SMF.

[0301] In an embodiment of the present disclosure, the first DNAI list may be received through an Nsmf_PDUSession_Context response message, and / or an Nsmf_PDUSession_Update request message and / or response message, and / or an Nsmf_PDUSession_Create response message.

[0302] In an embodiment of the present disclosure, the first I-SMF may be an I-SMF inserted when changing the I-SMF, or a target I-SMF. The first network node may receive the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from an evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from a non-third generation partnership project access to a third generation partnership project access.

[0303] According to an embodiment of the present disclosure, the anchor SMF stores a list of DNAIs of interest, which are used to instruct the user plane function to route the relevant application data to the required data network access point (identified by the DNAI). The DNAI list is provided by the PCF as part of the PCC rule authorization of the PDU session. The PCF determines the DNAI list of the PDU session by retrieving the AF business impact request information as part of the application data from the UDR (Unified Data Repository), and / or is provided by the NEF when the NEF is established or when the application session context is updated after receiving a business impact subscription request from the application function (by consuming the Npcf_PolicyAuthorization service). The new parameter "fullDnaiList" includes a DNAI list, which is a list of DNAIs of interest for the PDU session, excluding one or more DNAIs supported by the second network node, or not excluding one or more DNAIs supported by the second network node. That is, "all DnaiLists from the PCF configuration, not limited to the list of Dnai supported by the I-SMF". The I-SMF can obtain this new "fullDnaiList" in the following situations:

[0304] As scenario 1, when a new I-SMF is inserted during UE (User Equipment) mobility, the inserted I-SMF sends a message Nsmf_PDUSession_Context request to retrieve smContext from the anchor SMF. The anchor SMF provides the inserted I-SMF with a new attribute fullDnaiList in the Nsmf_PDUSession_Context response (SmContextRetrievedData\smContext\fullDnaiList). The inserted I-SMF stores the received fullDnaiList, and the new fullDnaiList can be placed directly under SmContextRetrievedData.

[0305] As scenario 2, during the mobility process of I-SMF change, the target I-SMF sends Nsmf_PDUSession_Context request to retrieve smContext from the source I-SMF. The source I-SMF provides the new attribute fullDnaiList to the target I-SMF in Nsmf_PDUSession_Context response (SmContextRetrievedData\smContext\fullDnaiList), and the target I-SMF stores the received fullDnaiList. The new fullDnaiList can be placed directly under SmContextRetrievedData.

[0306] As scenario 3, during the PDU session establishment process, the anchor SMF sends a Nsmf_PDUSession_Create response (PduSessionCreatedData\dnaiList, fullDnaiList).

[0307] As scenario 4, the PCF notifies the SMF of the updated fullDnaiList. The anchor SMF sends a Nsmf_PDUSession_Update request (VsmfUpdateData(Vsmf update data)\dnaiList, fullDnaiListfullDnaiList) to the I-SMF.

[0308] As scenario 5, the SMF will send a Nsmf_PDUSession_Update response (HsmfUpdatedData (Hsmf updated data) (dnaiList, fullDnaiList) to the I-SMF.

[0309] If the inserted / changed I-SMF needs to select ULCL / BP and local PSA0 immediately, the inserted / changed I-SMF generates the "commonly supported Dnai list of I-SMF and SMF" based on the locally configured I-SMF supported dnaiList and the new fullDnaiList. This means that the I-SMF generates the "dnailist of interest" by itself, instead of receiving it from the subsequent Nsmf_PDUSession_Update response of the anchor SMF, which is too late for the inserted I-SMF to select local PSA0.

[0310] Using this new fullDnaiList information, the local PSA can be selected timely, ie correctly and early, for simultaneous changes of different I-SMF controlled ULCL / BP and additional PSA applied during mobility (TS 23.502 4.23.9.5).

[0311] Embodiments of the present disclosure may provide the following advantages.

[0312] The inserted / changed I-SMF generates a "common supported Dnai list of I-SMF and SMF" based on the supported dnaiList configured locally by the I-SMF and the received new fullDnaiList. This means that the I-SMF generates the "dnailists of interest" by itself.

[0313] For simultaneous changes of ULCL / BP and additional PSA controlled by different I-SMFs applied during the mobility procedure (TS 23.502 4.23.9.5), the changed I-SMF can select UPF, such as I-UPF, V-UPF or local PSA, timely, i.e. correctly and as early as possible.

[0314] For simultaneous changes of ULCL / BP and additional PSA controlled by different I-SMFs applied during the mobility procedure (TS 23.502 4.23.9.5), the inserted I-SMF is able to correctly select the UPF, such as I-UPF, V-UPF or local PSA, in a timely manner (i.e., as early as possible).

[0315] Further detailed exemplary application scenarios of the embodiments of the present disclosure may be described below.

[0316] An exemplary application scenario may be associated with a solution for simultaneous changes of an inserted I-SMF controlled ULCL / BP and an additional PSA.

[0317] Fig. 6A is a diagram illustrating a solution of simultaneous change of inserted I-SMF-controlled ULCL / BP and additional PSA according to an embodiment of the present disclosure.

[0318] The improvement process of this solution includes the following steps:

[0319] 1.UE has established a PDU session with SMF, and SMF selects PSA1.

[0320] 2. Due to UE Mobility AMF is inserted into I-SMF.

[0321] 3.AMF sends a Nsmf_PDUSession_CreateSMContext request (PDU session ID, SM context ID) to the inserted I-SMF.

[0322] 4. Inserted I-SMF with simultaneous change of ULCL / BP and local PSA as in TS 23.502 4.23.9.5.

[0323] 5. The inserted I-SMF sends a Nsmf_PDUSession_Context request (SmContextRetrieveData) to the anchor SMF.

[0324] 6. The anchor SMF sends a Nsmf_PDUSession_Create response (SmContextRetrievedData (data retrieved by the Sm context)\smContext (Sm context) \fullDnaiList(full Dnai list)), fullDnaiList Means: All DnaiLists from PCF provided, not limited to the list of supported DNAIs. For example, fullDnaiList may include DNA I, b, c, d, e .

[0325] 7. I-SMF storage fullDnaiList .

[0326] 8. The inserted I-SMF is based on the received fullDnaiList Select ULCL / BP, select Local PSA0. That is: inserted I-SMF generates the new fullDnaiList based on the supported dnaiList (such as a, b, c) configured locally by I-SMF and the received new fullDnaiList "I-SMF and SMF's common supported Dnai list". This means that the inserted I-SMF generates its own "interested dnailist" (b, c) .

[0327] 9. The inserted I-SMF performs PFCP session establishment request / response with ULCL / BP.

[0328] 10. The inserted I-SMF performs PFCP session establishment request / response with the local PSA0.

[0329] 11. The inserted I-SMF sends a Nsmf_PDUSession_Create request (psaInfo (pas information), ul Info (ul information), ULCL-N9-for (for)-PSA1-FTEID) to the anchor SMF.

[0330] 12. The anchor SMF sends a Nsmf_PDUSession_Update response (HsmfUpdatedData(dnaiList,fullDnaiList) to the I-SMF.

[0331] 13. The anchor SMF and the anchor UPF perform the PFCP (Packet Forwarding Control Protocol) session modification process.

[0332] 14. The anchor SMF sends a Nsmf_PDUSession_Update request (n4Info (n4 information)) to the I-SMF.

[0333] 15. The inserted I-SMF performs PFCP session modification request / response with ULCL / BP.

[0334] 16. The inserted I-SMF performs a PFCP session modification request / response with the local PSA0.

[0335] 17. The inserted I-SMF sends a Nsmf_PDUSession_Update response to the anchor SMF.

[0336] 18. The inserted I-SMF sends a Nsmf_PDUSession_CreateSMContext response (ULCL / BP-N3-F-TEID) to AMF.

[0337] An exemplary application scenario may be associated with a solution of simultaneous changes of UL CL / BP and additional PSA controlled by a changed I-SMF.

[0338] Figure 6B is a diagram illustrating a solution of simultaneous change of UL CL / BP controlled by a changed I-SMF and additional PSA according to an embodiment of the present disclosure.

[0339] The improvement process of this solution includes the following steps:

[0340] 1. The UE has established a PDU session with the SMF and I-SMF. The I-SMF selects the source ULCL / BP and local PSA0x, and the anchor SMF selects PSA1.

[0341] 2. Due to UE Mobility AMF changes SI-SMF to TI-SMF.

[0342] 3.AMF sends a Nsmf_PDUSession_CreateSMContext request (PDU session ID, SM context ID) to TI-SMF.

[0343] 4. TI-SMF with simultaneous change of ULCL / BP and local PSA as described in TS 23.502 4.23.9.5.

[0344] 5. TI-SMF sends a Nsmf_PDUSession_Context request (SmContextRetrieveData (Sm context retrieval data)) to SI-SMF.

[0345] 6. SI-SMF sends Nsmf_PDUSession_Create response (SmContextRetrievedData\smContext\ fullDnaiList), fullDnaiList means: all DnaiLists provided by PCF, not limited to I- List of DNAIs supported by SMF .

[0346] 7. TI-SMF stores fullDnaiList .

[0347] 8.TI-SMF receives fullDnaiList Select ULCL / BP, select LocalPSA0. The changed I-SMF is based on the received fullDnaiList Select ULCL / BP, select LocalPSA0. That is, the changed I-SMF is based on I-SMF local dnaiList of supported configurations and received New fullDnaiList Generate a "list of Dnais supported by both I-SMF and SMF", that is, change I-SMF to generate "interested dnailists" by itself.

[0348] 9.TI-SMF performs PFCP session establishment request / response with ULCL / BP.

[0349] 10.TI-SMF performs PFCP session establishment request / response with local PSA0.

[0350] 11. The inserted I-SMF sends a Nsmf_PDUSession_Update request (psaInfo, ulclInfo, ULCL-N9-for-PSA1-FTEID) to the anchor SMF.

[0351] 12. The anchor SMF sends a Nsmf_PDUSession_Update response (HsmfUpdatedData(dnaiList,fullDnaiList) to the I-SMF.

[0352] 13. The anchor SMF and anchor UPF perform the PFCP session modification process.

[0353] 14. The anchor SMF sends a Nsmf_PDUSession_Update request (n4Info) to the TI-SMF.

[0354] 15.TI-SMF and ULCL / BP perform PFCP session modification request / response.

[0355] 16.TI-SMF performs PFCP session modification request / response with local PSA0.

[0356] 17.TI-SMF sends a Nsmf_PDUSession_Update response to the anchor SMF.

[0357] 18.TI-SMF sends Nsmf_PDUSession_CreateSMContext response (ULCL / BP-N3-F-TEID) to AMF.

[0358] Figure 6C is a diagram showing a PDU session establishment process, during which a first DNAI list (fullDaniList) is sent to a first network node (inserted I-SMF).

[0359] The improvement process of this solution includes the following steps:

[0360] 1.UE sends a PDU_Session_Establishment request to AMF;

[0361] 2.AMF sends Nsmf_PDUSession_CreateSMContext request to I-SMF;

[0362] 3.I-SMF sends Nsmf_PDUSession_CreateSMContext request to AMF;

[0363] 4. I-SMF sends a PFCP session establishment request to I-UPF;

[0364] 5. I-UPF sends a PFCP session establishment response to I-SMF;

[0365] 6. I-SMF sends Nsmf_PDUSession_Create request (PduSessionCreateData\dnaiList(I-SMF support)) to the anchor SMF;

[0366] 7. The anchor SMF sends a PFCP session establishment request to PSA1, and PSA1 sends a PFCP session establishment response to the anchor SMF;

[0367] 8. The anchor SMF sends a Nsmf_PDUSession_Create response (PduSessionCreatedData\dnaiList, fullDnaiList) to the I-SMF;

[0368] 9. I-SMF and I-UPF perform PFCP session modification request / response;

[0369] 10.I-SMF sends Namf_Communication_N1N2MessageTransfer to AMF;

[0370] 11. Continue with the remaining process of PDU session establishment.

[0371] Fig.6Dis a diagram showing a process in which a first DNAI list (fullDaniList) is sent to a first network node (inserted I-SMF).

[0372] When a new I-SMF is inserted during registration, service request, N2-based handover between NG-RAN nodes, Xn-based handover, handover from EPC / ePDG to 5GS, and non-3GPP to 3GPP access procedures (see sections 4.23.3, 4.23.4, 4.23.7.3, 4.23.11.2, and 4.23.16 of 3GPP TS 23.502), The anchor SMF can be used to retrieve the smContext The inserted I-SMF sends a new attribute fullDnaiList. The inserted I-SMF stores this fullDnaiList. The I-SMF can use This stored fullDnaiList selects the local PSA when needed, or forwards if the I-SMF changes due to UE mobility To the new I-SMF .

[0373] The improvement process of this solution includes the following steps:

[0374] 1.UE has established a PDU session with SMF, and PCF provides PCC rules and DNAI Information .

[0375] 2.AMF due to UE Mobility Instead, insert I-SMF.

[0376] 3.AMF sends a Nsmf_PDUSession_CreateSMContext request (PDU session ID, SM context ID) to the inserted I-SMF.

[0377] 4. The inserted I-SMF sends a Nsmf_PDUSession_Context request (SmContextRetrieveData) to the anchor SMF.

[0378] 5. The anchor SMF sends a Nsmf_PDUSession_Context response (SmContextRetrievedData\smContext\ fullDnaiList), fullDnaiList means: all DnaiLists provided by PCF, not limited to I- List of DNAIs supported by SMF .

[0379] 6. Inserted I-SMF storage fullDnaiList .

[0380] 7. The inserted I-SMF selects I-UPF (Intermediate User Plane Function).

[0381] 8. The inserted I-SMF sends a PFCP session establishment request to the I-UPF.

[0382] 9. The I-UPF sends a PFCP session establishment response to the inserted I-SMF.

[0383] 10. The inserted I-SMF sends a Nsmf_PDUSession_Create request with supported dnaiList to the anchor SMF.

[0384] 11. The anchor SMF sends a Nsmf_PDUSession_Create request with a preferred dnaiList (limited to the dnaiList supported by both the I-SMF and the anchor SMF, fullDnaiList) to the inserted I-SMF.

[0385] Notice: The anchor SMF can expand the existing dnaiList to fullDnaiList, or send a new fullDnaiList .

[0386] 12. The inserted I-SMF sends a Nsmf_PDUSession_CreateSMContext response (PDU session ID, SM context ID) to AMF.

[0387] Fig. 6E It is a diagram showing a process during which the PCF notifies the I-SMF of the latest fullDnailList.

[0388] During the PDU session lifetime, the AF can send a new Dnai list to the PCF, the PCF can update it to the anchor SMF, the anchor SMF can update it to the I-SMF, and then the I-SMF stores it locally.

[0389] The solution improvement process includes the following steps:

[0390] 1.UE has established a PDU session with SMF, PCF provides PCC (Policy and Charging Control) rules and DNAI Information

[0391] 2. AF notifies PCF of the new policy and new Dnai list. PCF notifies the anchor SMF through the following process:

[0392] -Npcf_SMPolicyControl_UpdateNotify_Request(dnaiList) / Response(Npcf_SM Policy Control_Update Notification_Request(dnaiList) / Response)

[0393] -Npcf_SMPolicyControl_UpdateRequest / Response(dnaiList) / Response(Npcf_SMPolicyControl_UpdateRequest / Response(dnaiList) / Response)

[0394] Note: smPolicyDecsion\pccRule\trafficControlData\RouteToLocationlist\dnaiList (sm policy decision\pcc rule\traffic control data\to location route list\dnaiList)

[0395] 3. The anchor SMF sends a Nsmf_PDUSession_Update request to the I-SMF ( fullDnaiList ).

[0396] 4. I-SMF stores the received fullDnaiList .

[0397] 5-17. New policies are implemented to NG-RAN, UE and PSA1.

[0398] Further, the new attribute "fullDnaiList" may be defined as follows, as an improvement to the definition of "6.1.6.2.39 Type: SmContext" in TS 29.502 (V17.5.0).

[0399] Table 6.1.6.2.39-1: Definition of type SmContext

[0400]

[0401]

[0402]

[0403]

[0404]

[0405]

[0406]

[0407]

[0408] TS 29.502 6.1.6.2.10 Type: PduSessionCreatedData

[0409] Table 6.1.6.2.10-1: Definition of type PduSessionCreatedData

[0410]

[0411] TS 29.502 6.1.6.2.12 Type: HsmfUpdatedData

[0412]

[0413]

[0414] TS29.502 6.1.6.2.15 Type: VsmfUpdateData

[0415] Table 6.1.6.2.15-1: Definition of type VsmfUpdateData

[0416]

[0417] Embodiments of the present disclosure provide the following benefits.

[0418] The inserted / changed I-SMF generates the "Common Supported Dnai List of I-SMF and SMF" based on the supported dnaiList configured locally by the I-SMF and the received new fullDnailist. This means that the I-SMF generates the "Interested Dnailist" by itself.

[0419] In particular, for simultaneous change of ULCL / BP and additional PSA controlled by different I-SMFs applied during the mobility procedure (TS 23.502 4.23.9.5), the changed I-SMF can select the local PSA correctly and early.

[0420] For simultaneous changes of ULCL / BP and additional PSA controlled by different I-SMFs applied during the mobility procedure (TS 23.502 4.23.9.5), the inserted I-SMF is able to select the local PSA correctly and early.

[0421] Fig. 7A is a block diagram illustrating an exemplary apparatus for a first network node, which is suitable for performing a method according to an embodiment of the present disclosure.

[0422] like Fig. 7AAs shown, the device 70 for the first network node includes: a processor 701; and a memory 702. The memory 702 includes instructions executable by the processor 701. The device 70 of the first network node is used to: receive a first data network access identifier (DNAI) list from the second network node; and select a local user plane function (UPF) based on at least the first DNAI list.

[0423] In an embodiment of the present disclosure, the apparatus 70 may also be operable to perform a method according to any of the above embodiments, for example Figure 3A , 3B , the embodiments shown in 3C, 3D, 5A, 5B, 5C, 6A, 6B, 6C, and 6D.

[0424] Figure 7B is a block diagram illustrating an exemplary apparatus for a second network node, which is suitable for performing a method according to an embodiment of the present disclosure.

[0425] like Figure 7B As shown, the device 71 for the second network node includes: a processor 711; and a memory 712. The memory 712 includes instructions executable by the processor 711. The device 71 of the second network node is operable to: send a first data network access identifier (DNAI) list to the first network node. The first DNAI list can be used by the first network node to select a local user plane function (UPF) based at least on the first DNAI list.

[0426] In an embodiment of the present disclosure, the apparatus 71 may also be operable to perform a method according to any of the above embodiments, for example Figure 4A , 4B , the embodiments shown in 5A, 5B, 5C, 6A, 6B, 6C, and 6D.

[0427] The processors 701, 711 may be any kind of processing components, such as one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The memories 702, 712 may be any kind of storage components, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc.

[0428] Figure 7C is a block diagram illustrating an exemplary system including a first network node and a second network node.

[0429] The system 700 includes: an apparatus 70 for a first network node, and an apparatus 71 for a second network node.

[0430] The apparatus 70 for the first network node comprises: a processor 701; and a memory 702. The memory 702 comprises instructions executable by the processor 701. The apparatus 70 for the first network node is operable to: receive a first data network access identifier (DNAI) list from a second network node; and select a local user plane function (UPF) based at least on the first DNAI list.

[0431] The apparatus 71 for the second network node includes: a processor 711; and a memory 712. The memory 712 includes instructions executable by the processor 711. The apparatus 71 for the second network node is operable to: send a first data network access identifier (DNAI) list to the first network node. The first DNAI list can be used by the first network node to select a local user plane function (UPF) for the terminal device based at least on the first DNAI list.

[0432] In an embodiment of the present disclosure, the system may also be operable to perform a method according to any of the above embodiments, for example Figure 3A , 3B , the embodiments shown in 3C, 3D, 4A, 4B, 5A, 5B, 5C, 6A, 6B, 6C, and 6D.

[0433] Figure 8 is a block diagram illustrating a device / computer-readable storage medium according to an embodiment of the present disclosure.

[0434] like Figure 8 As shown, 8. A computer-readable storage medium 80, or any other type of product, stores instructions 801, which, when executed by at least one processor, causes the at least one processor to perform the method according to any of the above embodiments, for example Figure 3A , 3B , the embodiments shown in 3C, 3D, 4A, 4B, 5A, 5B, 5C, 6A, 6B, 6C, and 6D.

[0435] In addition, the present disclosure may also provide a carrier including the computer program as described above, the carrier being one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical high-density disk or an electronic storage device, such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0436] Fig. 9A is a block diagram illustrating modules for a first network node, the modules being suitable for performing a method according to an embodiment of the present disclosure.

[0437] like Fig. 9AAs shown, the device 90 for the first network node may include: a receiving module 902, which is configured to receive a first data network access identifier (DNAI) list from the second network node; and a selection module 904, which selects a user plane function (UPF) based on at least the first DNAI list.

[0438] In an embodiment of the present disclosure, the device 90 may also be operable to perform the operation according to any of the above embodiments (eg Figure 3A , 3B , 3C, 3D, 5A, 5B, 5C, 6A, 6B, 6C, 6D) methods.

[0439] Fig. 9B is a block diagram illustrating modules for a second network node, which is suitable for performing a method according to an embodiment of the present disclosure.

[0440] like Fig. 9B As shown, the device 91 for the second network node may include: a sending module 912, which is configured to send a first data network access identifier (DNAI) list to the first network node. The first DNAI list can be used by the first network node to select a user plane function (UPF) based at least on the first DNAI list.

[0441] In an embodiment of the present disclosure, the apparatus 91 may also be operable to perform a method according to any of the above embodiments, for example Figure 4A , 4B , the embodiments shown in 5A, 5B, 5C, 6A, 6B, 6C, and 6D.

[0442] The term "module" may have a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, units, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0443] By using these modules, the device may not need a fixed processor or memory, and may arrange any type of computing resources and storage resources from at least one network node / device / entity / device related to the communication system. Virtualization technology and network computing technology (e.g., cloud computing) may be further introduced to improve the efficiency of network resource utilization and network flexibility.

[0444] The techniques described herein can be implemented in various ways so that the device that implements one or more functions of the corresponding device described using the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding device described using the embodiments, and it may include separate components for each separate function, or components that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules / units), or a combination thereof. For firmware or software, it can be implemented by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0445] Specifically, these functional modules may be implemented as network elements on dedicated hardware, software instances running on dedicated hardware, or virtualized functions instantiated on a suitable platform (eg, on a cloud infrastructure).

[0446] The first network node and the second network node may be any communication device and / or computing device in the network, such as any server, personal computer, user equipment, router, gateway device, etc. Examples of the first network node and / or the second network node may be as follows.

[0447] Fig.10 An example of a communication system 1000 is shown in accordance with some embodiments.

[0448] In this example, the communication system 1000 includes a telecommunications network 1002 including an access network 1004 such as a radio access network (RAN) and a core network 1006 including one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. The network node 1010 facilitates direct or indirect connection of user equipment (UE), such as by connecting UE 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UE 1012) to the core network 1006 via one or more wireless connections.

[0449] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. In addition, in various embodiments, the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether or not via a wired or wireless connection. The communication system 1000 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0450] UE 1012 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 1010 and other communication devices. Similarly, network node 1010 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1012 and / or with other network nodes or devices in telecommunication network 1002 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management in telecommunication network 1002.

[0451] In the depicted example, the core network 1006 connects the network node 1010 to one or more hosts, such as the host 1016. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1006 includes another core network node (e.g., core network node 1008) consisting of hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, network node, and / or host, so that the description is generally applicable to the corresponding components of the core network node 1008. The example core network node includes a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF) One or more functions.

[0452] The host 1016 may be under the ownership or control of a service provider other than the operator or provider of the access network 1004 and / or the telecommunications network 1002, and may be operated by or on behalf of the service provider. The host 1016 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions of an alarm and monitoring center, or any other such functions performed by a server.

[0453] on the whole, Fig.10 The communication system 1000 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards or any applicable future generation standards (such as 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0454] In some examples, the telecommunication network 1002 is a cellular network implementing 3GPP standardized features. Therefore, the telecommunication network 1002 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 1002. For example, the telecommunication network 1002 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine type communication (mMTC) / massive IoT services to more UEs.

[0455] In some examples, UE 1012 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1004 on a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1004. In addition, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0456] In this example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and / or 1012d) and a network node (e.g., network node 1010b). In some examples, the hub 1014 may be a controller, a router, a content source, and an analyzer, or any other communication device described herein with respect to the UE. For example, the hub 1014 may be a broadband router that enables the UE to access the core network 1006. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1010, or received by an executable code, a script, a process, or other instructions in the hub 1014. As another example, the hub 1014 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1014 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and the hub 1014 then provides it to the UE directly or after performing local processing and / or after adding additional local content. In another example, the hub 1014 acts as a proxy server or orchestrator for the UE, particularly in the case where one or more UEs are low-energy IoT devices.

[0457] Hub 1014 can have constant / persistent or intermittent connection to network node 1010b. Hub 1014 can also allow different communication schemes and / or scheduling between hub 1014 and UE (e.g., UE 1012c and / or 1012d) and hub 1014 and core network 1006. In other examples, hub 1014 is connected to core network 1006 and / or one or more UE via wired connection. In addition, hub 1014 can be configured to be connected to M2M service provider and / or connected to another UE via direct connection through access network 1004. In some scenarios, UE can establish wireless connection with network node 1010, while still connected via hub 1014 via wired or wireless connection. In some embodiments, hub 1014 can be a dedicated hub-that is, its main function is to route communication from network node 1010b to UE / route communication from UE to network node 1010b. In other embodiments, the hub 1014 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 1010b, but which is also operable as a communications start and / or end point for certain data channels.

[0458] Fig.11 UE 1100 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0459] The UE may support device-to-device (D2D) communications, such as by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user owning and / or operating the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0460] UE 1100 includes processing circuitry 1102, which is operatively coupled to input / output interface 1106, power supply 1108, memory 1110, communication interface 1112, and / or any other components or any combination thereof via bus 1104. Some UEs may utilize Fig.11 All or a subset of the components shown. The level of integration between components may vary from one UE to another. In addition, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0461] The processing circuit 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1110 as a machine-readable computer program. The processing circuit 1102 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 1102 may include multiple central processing units (CPUs).

[0462] In this example, the input / output interface 1106 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1100. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, directional boards, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0463] In some embodiments, the power supply 1108 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 1108 may also include a power circuit for delivering power from the power supply 1108 itself and / or an external power supply to various parts of the UE 1100 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, for charging the power supply 1108. The power circuit may perform any formatting, conversion, or other modification to the power from the power supply 1108 so that the power is suitable for the various components of the UE 1100 to which it is powered.

[0464] The memory 1110 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 1110 includes one or more application programs 1114, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1116. The memory 1110 may store any one or a combination of various operating systems for use by the UE 1100.

[0465] The memory 1110 may be configured to include a plurality of physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, a built-in hard disk drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more user identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a “SIM card”. The memory 1110 may allow the UE 1100 to access instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1110 , which may be or include a device-readable storage medium.

[0466] The processing circuit 1102 may be configured to communicate with an access network or other network using a communication interface 1112. The communication interface 1112 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1118 and / or a receiver 1120 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1118 and the receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software, or firmware, or may be implemented separately, alternatively.

[0467] In the illustrated embodiment, the communication functionality of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication (e.g., using a global positioning system (GPS) to determine location), another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards (e.g., IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, new radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.).

[0468] Regardless of the type of sensor, the UE may provide an output of data captured by its sensor via a wireless connection to a network node through its communication interface 1112. The data captured by the UE's sensor may be transmitted to the network node via another UE via a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to balance the load of reports from multiple sensors), in response to a trigger event (e.g., sending an alert when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0469] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0470] When in the form of an Internet of Things (IoT) device, a UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are the following devices or devices embedded in the following devices: a connected refrigerator or freezer, a television, connected lighting devices, an electric meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electronic door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, an augmented reality (AR) or virtual reality (VR) head mounted display, a wearable device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, Fig.11 In addition to the other components depicted in the illustrated UE 1100 , a UE in the form of an IoT device may include circuitry and / or software depending on the intended application of the IoT device.

[0471] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0472] In fact, for a single use case, any number of UEs may be used together. For example, a first UE may be a drone or integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first and / or second UE may also include more than one of the above functions. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.

[0473] Fig.12A network node 1200 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0474] Base stations may be classified based on the amount of coverage they provide (or in other words, their transmit power level), and therefore, based on the amount of coverage provided, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0475] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device (e.g., an MSR BS), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT).

[0476] The network node 1200 includes a processing circuit 1202, a memory 1204, a communication interface 1206, and a power supply 1208. The network node 1200 may include multiple physically separated components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own components. In certain scenarios where the network node 1200 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered to be a single separate network node in some cases. In some embodiments, the network node 1200 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be duplicated (e.g., separate memories 1204 for different RATs) and some components may be reused (e.g., the same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of various components shown for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into the network node 1200. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1200.

[0477] The processing circuit 1202 may include a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic for providing network node 1200 functionality alone or in combination with other network node 1200 components (e.g., memory 1204).

[0478] In some embodiments, the processing circuit 1202 includes a system on a chip (SOC). In some embodiments, the processing circuit 1202 includes one or more radio frequency (RF) transceiver circuits 1212 and baseband processing circuits 1214. In some embodiments, the radio frequency (RF) transceiver circuits 1212 and baseband processing circuits 1214 may be located on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of the RF transceiver circuits 1212 and baseband processing circuits 1214 may be located on the same chip or chipset, board, or unit.

[0479] The memory 1204 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, a persistent storage device, a solid-state memory, a remotely mounted memory, a magnetic medium, an optical medium, a random access memory (RAM), a read-only memory (ROM), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a flash drive, a compact disk (CD), or a digital video disk (DVD)), and / or any other volatile storage medium or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 1202. The memory 1204 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 1202 and used by the network node 1200. The memory 1204 may be used to store any calculations performed by the processing circuit 1202 and / or any data received via the communication interface 1206. In some embodiments, the processing circuit 1202 and the memory 1204 are integrated.

[0480] The communication interface 1206 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1206 includes a port / terminal 1216 for sending data to the network and receiving data from the network, for example, via a wired connection. The communication interface 1206 also includes a radio front-end circuit 1218, which can be coupled to the antenna 1210, or can be a part of the antenna 1210 in some embodiments. The radio front-end circuit 1218 includes a filter 1220 and an amplifier 1222. The radio front-end circuit 1218 can be connected to the antenna 1210 and the processing circuit 1202. The radio front-end circuit can be configured to adjust the signal communicated between the antenna 1210 and the processing circuit 1202. The radio front-end circuit 1218 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1218 can use a combination of a filter 1220 and / or an amplifier 1222 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1210. Similarly, when receiving data, antenna 1210 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1218. The digital data may be passed to processing circuit 1202. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0481] In some alternative embodiments, the network node 1200 does not include a separate radio front end circuit 1218, instead the processing circuit 1202 includes the radio front end circuit and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuit 1212 is part of the communication interface 1206. In yet another embodiment, the communication interface 1206 includes one or more ports or terminals 1216, the radio front end circuit 1218, and the RF transceiver circuit 1212 as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuit 1214, which is part of a digital unit (not shown).

[0482] Antenna 1210 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1210 may be coupled to radio front end circuit 1218 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1210 is separate from network node 1200 and may be connected to network node 1200 via an interface or port.

[0483] Antenna 1210, communication interface 1206 and / or processing circuit 1202 can be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data and / or signal can be received from a UE, another network node and / or any other network device. Similarly, antenna 1210, communication interface 1206 and / or processing circuit 1202 can be configured to perform any sending operation performed by a network node described herein. Any information, data and / or signal can be sent to a UE, another network node and / or any other network device.

[0484] The power supply 1208 provides power to the various components of the network node 1200 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 1208 may also include or be coupled to a power management circuit to provide power to the components of the network node 1200 for performing the functions described herein. For example, the network node 1200 may be connected to an external power source (e.g., an electrical grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source supplies power to the power circuit of the power supply 1208. As a further example, the power supply 1208 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit. If the external power source fails, the battery can provide backup power.

[0485] Embodiments of network node 1200 may include Fig.12Additional components beyond those shown are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 1200 may include a user interface device to allow information to be input into the network node 1200 and to allow information to be output from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1200.

[0486] Fig.13 is a block diagram of a host 1300 according to various aspects described herein, and the host 1300 may be Fig.10 1016 of the embodiment of the host. As used herein, the host 1300 can be or include a combination of various hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a processing resource in a server farm. The host 1300 can provide one or more services to one or more UEs.

[0487] Host 1300 includes processing circuitry 1302, which is operably coupled to input / output interface 1306, network interface 1308, power supply 1310, and memory 1312 via bus 1304. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.11 and 12 ) so that its description is generally applicable to the corresponding components of the host 1300.

[0488] The memory 1312 may include one or more computer programs, including one or more host applications 1314 and data 1316, which may include user data, such as data generated by a UE for the host 1300 or data generated by the host 1300 for the UE. An embodiment of the host 1300 may utilize only a subset or all of the components shown. The host application 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for a variety of different categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, heads-up display systems). The host application 1314 may also provide user authentication and permission checks, and may periodically report health, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1300 can select and / or instruct different hosts for over-the-top services for the UE. The host application 1314 can support various protocols, such as HTTP live streaming (HLS) protocol, real-time messaging protocol (RTMP), real-time streaming protocol (RTSP), dynamic adaptive streaming over HTTP (MPEG-DASH), etc.

[0489] Fig.14 1400 is a block diagram showing a virtualized environment 1400 in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components performed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more hardware nodes (e.g., hardware computing devices running as network nodes, UEs, core network nodes, or hosts). In addition, in an embodiment in which a virtual node does not require radio connectivity (e.g., a core network node or host), the node may be fully virtualized.

[0490] Application 1402 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some of the features, functions and / or advantages of some of the embodiments disclosed herein.

[0491] The hardware 1404 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, and the like. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and / or perform any of the functions, features, and / or benefits described in connection with some of the embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears to be networked hardware to the VMs 1408.

[0492] VM 1408 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 1406. Different embodiments of instances of virtual devices 1402 can be implemented on one or more of VM 1408 and can be implemented in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and client devices.

[0493] In the context of NFV, VMs 1408 can be software implementations of physical machines that run programs as if they were executed on physical, non-virtualized machines. Each VM 1408 and the portion of the hardware 1404 on which it executes (whether hardware dedicated to that VM and / or hardware shared by that VM with other VMs) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1408 on top of hardware 1404 and corresponds to an application 1402.

[0494] Hardware 1404 may be implemented in a standalone network node with general or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed through management and orchestration 1410, which in particular oversees the lifecycle management of application 1402. In some embodiments, hardware 1404 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities (e.g., radio access nodes or base stations) to virtual nodes. In some embodiments, a control system 1412 may be utilized to provide some signaling, which may be used alternatively for communication between hardware nodes and radio units.

[0495] Fig.15 A communication diagram is shown in which a host 1502 communicates with a UE 1506 via a network node 1504 over a partially wireless connection according to some embodiments. Fig.15 Describe the UE discussed in the previous paragraph (such as Fig.10 UE 1012a and / or Fig.11 UE 1100), network nodes (such as Fig.10 The network node 1010a and / or Fig.12 ), and a host (e.g. Fig.10 Host 1016 and / or Fig.13 Host 1300) according to various embodiments of the example implementation.

[0496] Similar to the host 1300, an embodiment of the host 1502 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1502 also includes software, which is stored in the host 1502 or accessible by the host 1502 and can be executed by the processing circuit. The software includes a host application, which can be used to provide services to a remote user (e.g., a UE 1506 connected via an over-the-top (OTT) connection 1550 extending between the UE 1506 and the host 1502). When providing services to a remote user, the host application can provide user data sent using the OTT connection 1550.

[0497] The network node 1504 includes hardware that enables it to communicate with the host 1502 and the UE 1506. The connection 1560 can be direct or through a core network (such as Fig.10The core network 1006 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

[0498] UE 1506 includes hardware and software stored in or accessible by UE 1506 and executable by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "app", which is operable to provide services to human or non-human users via UE 1506 with the support of host 1502. In host 1502, the executed host application can communicate with the executed client application via an OTT connection 1550 terminated at UE 1506 and host 1502. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 1550 can transmit both the request data and the user data. The client application of the UE can interact with the user to generate the user data provided to the host application via the OTT connection 1550.

[0499] The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide connectivity between the host 1502 and the UE 1506. The connection 1560 and the wireless connection 1570 over which the OTT connection 1550 may be provided have been drawn abstractly to illustrate communications between the host 1502 and the UE 1506 via the network node 1504 without explicit reference to any intermediate devices and the precise routing of messages through those devices.

[0500] As an example of sending data via OTT connection 1550, in step 1508, host 1502 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1506. In other embodiments, the user data is associated with UE 1506 that shares data with host 1502 without explicit human interaction. In step 1510, host 1502 initiates a transmission carrying user data to UE 1506. Host 1502 may initiate the transmission in response to a request sent by UE 1506. The request may be caused by human interaction with UE 1506 or by an operation performed by a client application executed on UE 1506. According to the teachings of the embodiments described throughout this disclosure, the transmission may be delivered via network node 1504. Therefore, in step 1512, according to the teachings of the embodiments described throughout this disclosure, network node 1504 sends the user data carried in the transmission initiated by host 1502 to UE 1506. In step 1514 , UE 1506 receives the user data carried in the transmission, which may be performed by a client application executing on UE 1506 associated with a host application executed by host 1502 .

[0501] In some examples, UE 1506 executes a client application that provides user data to host 1502. The user data may be provided as a reaction to or in response to data received from host 1502. Thus, in step 1516, UE 1506 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may also take into account user input received from a user via an input / output interface of UE 1506. Regardless of the specific manner in which the user data is provided, UE 1506 initiates transmission of the user data to host 1502 via network node 1504 in step 1518. In step 1520, network node 1504 receives user data from UE 1506 and initiates transmission of the received user data to host 1502 in accordance with the teachings of the embodiments described throughout this disclosure. In step 1522, host 1502 receives the user data carried in the transmission initiated by UE 1506.

[0502] One or more of the various embodiments improves the performance of OTT services provided to UE 1506 using an OTT connection 1550 in which a wireless connection 1570 forms the last segment. According to an embodiment of the present disclosure, an improved method and an improved device for UPF selection may be provided. Specifically, by receiving a first DNAI list, the first network node may select a UPF in a timely manner when needed. Therefore, the problem that the DNAI may not be available when the network node needs to select a UPF at a certain point in time will be avoided. More precisely, the teachings of these embodiments can improve the performance of the communication network, such as data rate, delay, power consumption, thereby providing benefits such as reducing user waiting time, relaxing restrictions on file size, improving content resolution, better responsiveness, and extending battery life.

[0503] In an example scenario, plant status information may be collected and analyzed by host 1502. As another example, host 1502 may process audio and video data that may have been retrieved from a UE for use in creating a map. As another example, host 1502 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, host 1502 may store surveillance videos uploaded by a UE. As another example, host 1502 may store or control access to media content such as video, audio, VR, or AR that it may broadcast, multicast, or unicast to a UE. As other examples, host 1502 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function for collecting, retrieving, storing, analyzing, and / or sending data.

[0504] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments improve. There may also be an optional network function for reconfiguring the OTT connection 1550 between the host computer 1502 and the UE 1506 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 1550 may be implemented in the software and hardware of the host 1502 and / or the UE 1506. In some embodiments, sensors (not shown) may be deployed in or associated with other communication devices through which the OTT connection 1550 passes. The sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above or providing the values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1550 may include message formats, retransmission settings, preferred routes, etc.; reconfiguration does not require direct changes to the operation of the network node 1504. Such processes and functions are known in the art and can be practiced. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1502 to measure throughput, propagation time, delay, etc. Measurements may be implemented as follows, where the software causes messages (particularly empty or "dummy" messages) to be sent using the OTT connection 1550 while monitoring message propagation times, errors, etc.

[0505] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the acquired information into other information, comparing the acquired information or the converted information with the information stored in the network node, and / or performing one or more operations based on the acquired information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components constituting a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0506] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without the need to execute instructions stored on a separate or discrete device-readable storage medium (e.g., in a hardwired manner). In any of those specific embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0507] The following are references, the entire contents of which are incorporated herein:

[0508] 3GPP TS 23.502, V17.5.0(2022-06)

[0509] 3GPP TS 29.502 V17.5.0(2022-06)

[0510] abbreviation illustrate

[0511] SMF session management functions

[0512] UPF User Plane Function

[0513] I-SMF Intermediate Session Management Function

[0514] UL CL Uplink Classifier

[0515] BP branch point

[0516] PSA Protocol Data Unit Session Anchor

[0517] appendix

[0518] According to an embodiment of the present disclosure, the following change request may also be provided to improve the current 3GPP standard.

[0519] 3GPP TSG-CT WG4 Meeting #111-e C4-224abc Electronic Meeting, August 18-26, 2022

[0520]

[0521] About using this form help : For detailed instructions, visit

[0522] http: / / www.3gpp.org / Change-Requests.

[0523] Proposed changes impact: UICC Applications □ ME □ Radio Access Network □ Core Network

[0524]

[0525]

[0526]

[0527]

[0528] 6.1.6.2.10 Type: PduSessionCreatedData

[0529] Table 6.1.6.2.10-1: Definition of type PduSessionCreatedData

[0530]

[0531]

[0532]

[0533]

[0534]

[0535]

[0536]

[0537] 6.1.6.2.12 Type: HsmfUpdatedData

[0538] Table 6.1.6.2.12-1: Definition of type HsmfUpdatedData

[0539]

[0540]

[0541]

[0542] 6.1.6.2.15 Type: VsmfUpdateData

[0543] Table 6.1.6.2.15-1: Definition of type VsmfUpdateData

[0544]

[0545]

[0546]

[0547]

[0548]

[0549] 6.1.6.2.39 Type: SmContext

[0550] Table 6.1.6.2.39-1: Definition of type SmContext

[0551]

[0552]

[0553]

[0554]

[0555]

[0556]

[0557]

[0558]

[0559]

[0560]

[0561]

[0562]

[0563]

[0564]

[0565]

[0566]

[0567]

[0568]

[0569]

[0570]

Claims

1. A method (300) performed by a first network node, comprising: Receiving (S302) a first data network access identifier DNAI list from a second network node; as well as A user plane function UPF is selected (S304) based at least on the first DNAI list.

2. The method (300) according to claim 1, in, The UPF includes at least one of the following for a protocol data unit PDU session: an intermediate UPF, namely, an I-UPF, a visited UPF, namely, a V-UPF, or a local protocol data unit session anchor point PSA.

3. The method (300) according to claim 1 or 2, further comprising: The first DNAI list is stored (S303).

4. The method (300) according to any one of claims 1 to 3, further comprising: receiving (S308) an updated first DNAI list from the second network node; as well as The updated first DNAI list is stored (S310).

5. The method (300) according to any one of claims 1 to 4, in, Selecting (S304) the UPF includes: Based at least on the first DNAI list and / or configuration, obtaining (S3041) a second DNAI list; and Based at least on the second DNAI list, one or more UPFs are selected (S3042).

6. The method (300) according to claim 5, in, The second DNAI list is a list of DNAIs included in the first DNAI list and supported by the first network node.

7. The method (300) according to claim 5 or 6, further comprising: Before selecting any local UPF, an uplink classifier or branch point to be inserted into the user plane data path is selected (S3031).

8. The method (300) according to any one of claims 1 to 7, in, The first DNAI list is a complete DNAI list.

9. The method (300) according to claim 8, in, The complete DNAI list is a list of DNAIs of interest for a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

10. The method (300) according to any one of claims 1 to 9, in, The first network node includes: a first intermediate session management function I-SMF, or a first visited session management function V-SMF.

11. The method (300) according to claim 10, in, The second network node comprises: a session management function SMF.

12. The method (300) according to claim 11, in, The second network node includes: a second intermediate session management function I-SMF, or a second V-SMF, or an anchor SMF.

13. The method (300) according to any one of claims 10 to 12, in, The first DNAI list is received via at least one of: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response message.

14. The method (300) according to any one of claims 10 to 13, in, The first I-SMF is a newly inserted I-SMF or a target I-SMF in the inter-I-SMF mobility process; or The first I-SMF is an I-SMF inserted when the I-SMF is changed or a target I-SMF.

15. The method (300) according to any one of claims 1 to 14, in, The first network node receives the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from a non-third generation partnership project access to a fifth generation system.

16. A method (400) performed by a second network node, comprising: Sending (S402) a first data network access identifier DNAI list to a first network node; The first DNAI list is used by the first network node to select a user plane function UPF based at least on the first DNAI list.

17. The method (400) according to claim 16, in, The UPF includes at least one of the following for a protocol data unit PDU session: an intermediate UPF, ie, an I-UPF, a visited UPF, ie, a V-UPF, or a local protocol data unit session anchor point PSA.

18. The method (400) according to claim 16 or 17, further comprising: receiving (S404) an updated first DNAI list from the PCF; as well as The updated first DNAI list is sent (S406) to the first network node.

19. The method (400) according to claim 15 or 16, in, The first DNAI list is used by the first network node to obtain a second DNAI list based at least on the first DNAI list and / or configuration, and to select one or more UPFs based at least on the second DNAI list.

20. The method (400) according to claim 19, in, The second DNAI list is a list of DNAIs included in the first DNAI list and supported by the first network node.

21. The method (400) according to claim 19 or 20, in, The first network node selects an uplink classifier or branching point to be inserted into the user plane data path before selecting any local UPF.

22. The method (400) according to any one of claims 16 to 21, in, The first DNAI list is a complete DNAI list.

23. The method (400) according to claim 22, in, The complete DNAI list is a list of DNAIs of interest for a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node or does not exclude one or more DNAIs supported by the second network node.

24. The method (400) according to any one of claims 16 to 23, in, The first network node includes: a first intermediate session management function I-SMF, or a first V-SMF.

25. The method (400) according to claim 24, in, The second network node comprises: a session management function SMF.

26. The method (400) of claim 25, in, The second network node includes: a second intermediate session management function I-SMF, or a second V-SMF, or an anchor SMF.

27. The method (400) according to any one of claims 22 to 26, in, The first DNAI list is sent via at least one of the following: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response.

28. The method (400) according to any one of claims 22 to 27, in, The first I-SMF is a newly inserted I-SMF or a target I-SMF in the inter-I-SMF mobility process; or The first I-SMF is an I-SMF inserted when the I-SMF is changed or a target I-SMF.

29. The method (400) according to claims 16 to 28, in, The first network node receives the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from a non-third generation partnership project access to a fifth generation system.

30. A method (500) performed by a system comprising a first network node and a second network node, comprising: The second network node sends (S502) a first data network access identifier DNAI list to the first network node; The first network node receives (S504) the first DNAI list from the second network node; as well as The first network node selects (S506) a user plane function UPF based at least on the first DNAI list.

31. The method (500) according to claim 30, in, The UPF includes at least one of the following for a protocol data unit PDU session: an intermediate UPF, namely, an I-UPF, a visited UPF, namely, a V-UPF, or a local protocol data unit session anchor point PSA.

32. The method (500) according to claim 30 or 31, further comprising: The first network node stores (S505) the first DNAI list.

33. The method (500) according to any one of claims 30 to 32, further comprising: Receiving (S508) by the second network node an updated first DNAI list from the PCF; as well as The second network node sends (S510) the updated first DNAI list to the first network node; Receiving (S512) the updated first DNAI list from the second network node by the first network node; as well as The updated first DNAI list is stored (S514) by the first network node.

34. The method (500) according to any one of claims 30 to 33, in, The selecting (S506) of the UPF by the first network node includes: The first network node obtains (S5061) a second DNAI list based at least on the first DNAI list and / or configuration; One or more UPFs are selected (S5062) by the first network node based at least on the second DNAI list.

35. The method (500) of claim 34, in, The second DNAI list is a list of DNAIs included in the first DNAI list and supported by the first network node.

36. The method (500) according to claim 34 or 35, further comprising: Before selecting any local UPF, an uplink classifier or branching point to be inserted into the user plane data path is selected (S5051).

37. The method (500) according to any one of claims 30 to 36, in, The first DNAI list is a complete DNAI list.

38. The method (500) of claim 37, in, The complete DNAI list is a list of DNAIs of interest for a protocol data unit (PDU) session that excludes one or more DNAIs supported by the second network node, or does not exclude one or more DNAIs supported by the second network node.

39. The method (500) according to any one of claims 30 to 38, The first network node comprises: A first intermediate session management function I-SMF, or a first V-SMF.

40. The method (500) of claim 39, in, The second network node comprises: a session management function SMF.

41. The method (500) according to claim 40, in, The second network node includes: a second intermediate session management function I-SMF, or a second V-SMF, or an anchor SMF.

42. The method (500) of claim 36, in, The first DNAI list is received via at least one of: a Nsmf_PDUSession_Context response message, a Nsmf_PDUSession_Update request message, a Nsmf_PDUSession_Update response message, or a Nsmf_PDUSession_Create response message.

43. The method (500) according to any one of claims 39 to 42, in, The first I-SMF is a newly inserted I-SMF or a target I-SMF in the inter-I-SMF mobility process; or The first I-SMF is an I-SMF inserted when the I-SMF is changed or a target I-SMF.

44. The method (500) according to any one of claims 30 to 43, in, The first network node receives the first DNAI list during at least one of the following processes: protocol data unit session establishment, registration, service request, N2-based handover between next generation radio access network nodes, Xn-based handover, handover from evolved packet core / evolved packet data gateway to a fifth generation system, and / or handover from a non-third generation partnership project access to a fifth generation system.

45. An apparatus (70) for a first network node, comprising: Processor (701); as well as a memory (702) comprising instructions executable by the processor (701), whereby the apparatus (70) for the first network node is operable to: receiving a first data network access identifier DNAI list from a second network node; and A user plane function UPF is selected based at least on the first DNAI list.

46. ​​The device (70) of claim 42, wherein: The apparatus (70) is further operable to perform a method according to any one of claims 2 to 15.

47. An apparatus (71) for a second network node, comprising: Processor (711); as well as a memory (712) comprising instructions executable by the processor (711), whereby the apparatus for the second network node is operable to: Sending a first data network access identifier DNAI list to the first network node; The first DNAI list is used by the first network node to select a user plane function UPF based at least on the first DNAI list.

48. The device (71) according to claim 44, wherein: The device (71) can also be used to perform a method according to any one of claims 17 to 29.

49. A system (700), comprising: an apparatus (70) for a first network node, and an apparatus (71) for a second network node; The device (71) for the second network node comprises: a processor (711); and a memory (712), wherein the memory (712) comprises instructions executable by the processor (711), whereby the device (71) for the second network node is operable to: send a first data network access identifier (DNAI) list to the first network node; The device (70) for the first network node includes: a processor (701); and a memory (702), wherein the memory (702) includes instructions executable by the processor (701), whereby the device (70) for the first network node is operable to: receive the first DNAI list from the second network node; and select a user plane function UPF based at least on the first DNAI list.

50. The system (700) of claim 46, wherein: The system (700) is further operable to perform a method according to any one of claims 31 to 44.

51. A computer readable storage medium (80) storing instructions (801) which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 44.

Images