TECHNICAL FIELD OF THE DEVICE AND METHOD FOR UE SERVICE MANAGEMENT
By sharing UE's IP address information and using external network elements, the method addresses IPv6 multihoming issues in 5G networks, ensuring consistent IP address management and smooth UE mobility.
Patent Information
- Application Number
- JP2023524797
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-10-23
- Filing Date
- 2021-06-22
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2041-06-22
AI Technical Summary
In IP address management of 5G networks, the insertion of an intermediate SMF (I-SMF) for UE mobility leads to issues with IPv6 multihoming due to lack of information on subscriber IP indexes and DN-AAA server addresses, causing improper address assignment and disrupting IPv6 multihoming functionality.
The method involves providing the UE's IP address information, including the subscriber IP index, from the old SMF to the new I-SMF during insertion or modification procedures, ensuring consistent IP address management across SMFs by using the IPv6 prefix and address information of external network elements like DN-AAA servers.
This approach ensures uniform IP address management, enabling proper IPv6 multihoming and addressing across multiple SMFs, thereby maintaining seamless network operations during UE mobility.
Smart Images

Figure 0007581508000001 
Figure 0007581508000002 
Figure 0007581508000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to the technical field of telecommunications, and more particularly to methods, network elements, devices, computer-readable storage media, carriers, etc. for UE service management network element discovery and selection, etc. [Background technology]
[0002] This section is intended to provide background for various embodiments of the technology described in this disclosure. The description in this section may include concepts that could be achieved, but not necessarily concepts that have been previously conceived or achieved. Thus, unless otherwise indicated in this disclosure, what is described in this section is not prior art to the description and / or claims of this disclosure, and is not admitted to be prior art merely by inclusion in this section.
[0003] In the IP address management of the user equipment (UE) in the 5G network, there is a scenario in which the UE has a PDU session established with a UPF including a PDU session anchor 1 controlled by the SMF, and an I-SMF and an I-UPF controlled by the I-SMF have already been inserted for this PDU session. At some point, using a list of noted DNAI(s) for this PDU session received from the SMF, the I-SMF decides to establish a new PDU session anchor, for example, for UE mobility. The I-SMF selects a UPF and establishes a new PDU session anchor 2 (PSA2) for the PDU session using N4. Summary of the Invention
[0004] One or more objectives of the present disclosure are to address one or more of the problems that arise in IP address management.
[0005] According to a first embodiment of the present disclosure, a method for UE service management network element in a communication network is provided, comprising: Receiving a first request; In response to determining that the first request is to request the UE service management network element to be an intermediate UE service management network element for a service of a UE: sending a second request to another UE service management network element indicated in the first request; and receiving a response corresponding to the second request, the response including Internet Protocol (IP) address information of the UE.
[0006] According to a second embodiment of the present disclosure, there is provided a UE service management network element operating in a communication network, comprising: a first receiving component configured to receive a first request; a first sending component configured to, in response to determining that the first request is requesting the UE service management network element to be an intermediate UE service management network element for a service of a UE, send a second request to another UE service management network element indicated in the first request; and a second receiving component configured to receive a response corresponding to the second request, where the response includes Internet Protocol (IP) address information of the UE.
[0007] According to a third embodiment of the present disclosure, there is provided a communication device in a network, comprising: a storage device adapted to store instructions; and a processor adapted to execute the instructions to cause the communication device to perform any step of the method of the present disclosure.
[0008] According to a fourth embodiment of the present disclosure, one or more computer-readable storage media are provided that store computer-executable instructions that, when executed by a computing device, cause the computing device to implement any of the methods of the present disclosure.
[0009] According to a fifth embodiment of the present disclosure, there is provided a computer program comprising instructions which, when executed on at least one processor, cause said at least one processor to perform a method according to any one of the methods of the present disclosure.
[0010] According to a sixth embodiment of the present disclosure, there is provided a carrier comprising the computer program of the eighth embodiment, said carrier being one of an electrical signal, an optical signal, a radio signal, or a computer readable storage device.
[0011] According to a seventh embodiment of the present disclosure, there is provided an apparatus adapted to perform a method according to any one of the methods of the present disclosure.
[0012] The UE service management network element in the present disclosure is a network function element and may provide service management for the UE, for example, a network function element in a 5G core or an NG core such as an SMF. The communication network in the present disclosure may be a 5G network, a 5G network combined with a 4G network, or any other suitable network. [Brief description of the drawings]
[0013] The foregoing and other features of the present disclosure will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings, in which: The present disclosure will be described with additional specificity and detail through the use of the accompanying drawings, with the understanding that these drawings illustrate only some embodiments according to the present disclosure and therefore should not be considered as limiting the scope of the disclosure.
[0014] [Figure 1]1 illustrates a high-level view of an example 5G network architecture to which embodiments of the present disclosure may be applied.
[0015] [Diagram 2] illustrates an exemplary service-based architecture for a non-roaming 5G or next-generation core network.
[0016] [Figure 3a] and [Figure 3b] and [Figure 3c] illustrates a scenario in which embodiments of the present disclosure may be applied.
[0017] [Figure 4a] shows the addition of a PDU session anchor controlled by the I-SMF.
[0018] [Figure 4b] 1 illustrates an I-SMF insertion procedure according to an embodiment of the present disclosure.
[0019] [Figure 4c] 1 illustrates an I-SMF modification procedure according to an embodiment of the present disclosure.
[0020] [Diagram 5] 3 illustrates a flowchart of an embodiment of a UE service management network element according to an embodiment of the present disclosure.
[0021] [Figure 6] 1 illustrates a schematic block diagram of a UE service management network element according to an embodiment of the present disclosure.
[0022] [Figure 7] 1 illustrates generally an embodiment of a configuration that may be used for a network element of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0023] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings illustrating the embodiments. However, these embodiments in this disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments set forth in this disclosure. Elements of the drawings are not necessarily to scale relative to each other. Like reference characters refer to like elements throughout.
[0024] The terms used in this disclosure are for the purpose of describing particular embodiments only and are not intended to be limiting. As used in this disclosure, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly indicates otherwise. The terms "comprises", "includes" and / or "including", as used in this disclosure, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0025] The terms "A or B," "at least one of A or / and B," or "one or more of A or / and B," as used in this disclosure, include all possible combinations of the items listed therewith. For example, "A or B," "at least one of A and B," or "at least one of A or B" means (1) including at least one A, (2) including at least one B, or (3) including both at least one A and at least one B.
[0026] Terms such as "first" and "second" used in this disclosure may be used to distinguish one component from another, regardless of importance or order, and are used to distinguish the corresponding components from one another, without limiting the components. These terms may be used to distinguish one element from another. For example, a first requirement and a second requirement indicate different requirements, regardless of order or importance.
[0027] The phrase "configured to" as used in this disclosure may be used interchangeably with "suitable for," "capable of," "designed to," "adapted to," "made to," or "capable of," depending on the context. The term "configured to" does not necessarily mean "specially designed to" at the hardware level. Instead, the phrase "apparatus configured to" may mean that the apparatus is "capable of" in some context with other devices or components. For example, "a processor configured to execute A, B, and C" may mean a dedicated processor (e.g., an embedded processor) for executing the corresponding operations, or a general-purpose processor (e.g., a central processing unit (CPU) or application processor (AP)) capable of executing the corresponding operations by executing one or more software programs stored in a memory device.
[0028] Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure have the same meaning as commonly understood. Terms used in this disclosure should be interpreted to have a meaning consistent with their meaning in the context of this disclosure and related art, and are not interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure, for example, concepts such as AMF, SMF, etc. are commonly understood in the context of 3GPP specifications, it will be further noted. Many embodiments of the present disclosure are described in the context of next-generation networks (such as 5G mobile wireless networks), although other networks may be applicable.
[0029] It should be noted that while many embodiments are described in the context of inserting or modifying an I-SMF, embodiments of the present disclosure are not limited to I-SMFs but may also be applied to other NFs as desired.
[0030] Both "address / prefix" and "address" are used in this disclosure with the understanding that they refer to the same thing and are interchangeable since a prefix is a type of address. Similarly, "IP address information" can include an IP address, including an IP prefix, etc.
[0031] FIG. 1 illustrates a high-level view of an example NG (e.g., 5G mobile wireless) network architecture to which embodiments of the present disclosure may be applied, including a Next Generation Radio Access Network (NG-RAN) 104 and an NG Core (NGC) 106. As shown in the figure, the NG-RAN 104 may include a gNB 1041 (e.g., 1041a, 1041b) and a ng-eNB 1042 (e.g., 1042a, 1042b) interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected to the NGC 106 via an NG interface, and more specifically to an AMF (Access and Mobility Management Function) 208 (e.g., AMF 208a, 208b) via respective NG-C interfaces, and to a UPF (User Plane Function) 212 (e.g., UPF 212b, 212a) via respective NG-U interfaces.
[0032] Each of the gNBs 1041 may support an NR radio interface, including frequency division multiplexing (FDD), time division multiplexing (TDD), or a combination thereof. In contrast, each of the ng-eNBs 1042 supports an LTE radio interface, but unlike a conventional LTE eNB (as shown in FIG. 1), connects to the NGC via an NG interface.
[0033] Deployments based on different 3GPP architecture options (e.g., EPC-based or 5GC-based) and UEs with different capabilities (e.g., EPC NAS and 5GC NAS) may coexist simultaneously in one network (e.g., PLMN). It is generally assumed that a UE that can support 5GC NAS procedures can also support EPC NAS procedures to operate in legacy networks, such as when roaming. Thus, a UE will use EPC NAS or 5GC NAS procedures depending on the core network (CN) that serves it.
[0034] Another change in NG networks (e.g., in 5GC) is that traditional peer-to-peer interfaces and protocols (e.g., those found in LTE / EPC networks) are modified by a so-called Service-Based Architecture (SBA), where a network function offers one or more services to one or more service consumers. This can be done, for example, by HTTP / REST (Hypertext Transfer Protocol / Representational State Transfer) Application Programming Interfaces (APIs).
[0035] A service is composed of various "service operations", which are finer divisions of the overall service functionality. To access a service, both the service name and the desired service operation must be specified. The interaction between service consumers and producers can be of the "request / response" type, or of the "subscribe / notify" type. In the 5G SBA, the Network Repository Function (NRF) allows every network function to discover the services offered by other network functions, and the Data Storage Function (DSF) allows every network function to store its context.
[0036] This architectural model further employs principles such as modularity, reusability, and self-containment of network functions, and enables deployments to take advantage of the latest virtualization and software technologies.
[0037] FIG. 2 illustrates a service-based architecture for an exemplary non-roaming 5G or next generation core network (5GCN / NGCN / NCN). The diagram illustrates logical connections between nodes and functions, and the illustrated connections should not be interpreted as direct physical connections. The UE 210 forms a radio access network connection with a (radio) access network ((R)AN) node 211 (which may be, for example, a gNodeB (gNB)), which is connected to a CN user plane (UP) function (UPF) 212, such as a UP gateway, via a network interface that provides a defined interface, such as an N3 interface. The UPF 212 provides a logical connection to a data network (DN) 213 via a network interface, such as an N6 interface. The radio access network connection between the UE 210 and the (R)AN node may be referred to as a data radio bearer (DRB).
[0038] DN 213 may be a data network used to provide operator services, or may be outside the scope of Third Generation Partnership Project (3GPP) standardization, such as the Internet, and may be a network used to provide third party services; according to some embodiments, DN 213 may represent an edge computing network or resource, such as a Mobile Edge Computing (MEC) network.
[0039] The UE 210 also connects to an Access and Mobility Management Function (AMF) 208 via a logical N1 connection (although the physical path of the connection is not direct). The AMF 208 is responsible for authentication and authorization of access requests, as well as mobility management functions. The AMF 208 may perform other roles and functions defined by 3GPP Technical Specification (TS) 23.501. In a service-based view, the AMF 208 may communicate with other core network control plane functions via service-based interfaces, denoted as Namf.
[0040] The Session Management Function (SMF) 209 is a network function responsible for allocating and managing IP addresses allocated to EDs, and for selecting a UPF 212 (or a specific instance of a UPF 212) for traffic related to a specific session of a UE 210. It will be understood that typically there are multiple SMFs 209 in the network 226, each of which may be associated with a respective group of UEs 210, (R)AN nodes 211 or UPFs 212. The SMF 209 can communicate with other core network functions in a service-based view through a service-based interface, denoted as Nsmf. The SMF 209 can also be connected to the UPF 212 through a logical interface, such as the network interface N4. It is also possible to use an SMF as an intermediate SMF (I-SMF). A UE may be located in an area where the UPF cannot be controlled by the original SMF because it belongs to a different SMF service area, in which case the I-SMF is the SMF inserted to support the PDU session.
[0041] The Authentication Server Function (AUSF) 207 provides authentication services to other network functions via a service-based Nausf interface.
[0042] A network publishing function (NEF) 202 may be deployed within a network to allow entities located outside the trusted domain, such as servers, functions, and other entities, to publish and obtain services and capabilities within the network. According to one such example, the NEF 202 may act like a proxy between application servers outside the illustrated network and network functions, such as the policy control function (PCF) 204, SMF 209, UDM 205, and AMF 208, such that the external application servers can provide information that may be useful in setting up parameters related to data sessions. The NEF 202 may communicate with other network functions via a service-based NEF network interface. The NEF 202 may also have interfaces to non-3GPP functions.
[0043] The Network Repository Function (NRF) 203 provides functionality for discovering network elements. The NRF 203 may be specific to the Public Land Mobile Network (PLMN) or network operator with which it is associated. The service discovery function may enable network functions and UEs connected to the network to determine addresses and methods for accessing existing network functions, and may present a service-based interface Nnrf.
[0044] The PCF 204 communicates with other network functions via a service-based Npcf interface and may be used to provide policies and rules to other network functions, including those in the control plane. The enforcement and application of policies and rules is not necessarily the responsibility of the PCF 204, but is typically the responsibility of the function to which the PCF 204 sends the policies. In one such example, the PCF 204 may send policies related to session management to the SMF 209. This may be used to enable a unified policy framework by which network behavior can be managed.
[0045] Unified Data Management (UDM) 205 may present a service-based Nudm interface for communicating with other network functions and may provide data storage functionality to other network functions. Unified data storage may enable a unified view of network information that may be used to ensure that the most relevant information may be made available to different network functions from a single resource. This may make implementation of other network functions easier since they do not need to determine where in the network a particular type of data is stored. UDM 205 may use an interface such as Nudr to connect to User Data Repository (UDR) 214. It should be understood that PCF 204 may be associated with UDM 205 because it may be involved in requesting and providing subscription policy information to UDR 214, but typically PCF 204 and UDM 205 are independent functions.
[0046] The PCF 204 may have a direct interface to the UDR 214 or may use a Nudr interface to connect with the UDR 214. The UDM 205 may receive requests to retrieve content stored in the UDR 214 or to store content in the UDR 214. The UDM 205 is typically responsible for functions such as credential processing, location management, and subscription management. The UDR 214 may also support any or all of authentication credential processing, user identification processing, access permission, registration / mobility management, subscription management, and short message service (SMS) management. The UDR 214 is typically responsible for storing data provided by the UDM 205. The stored data is typically associated with policy profile information (which may be provided by the PCF 204) that governs access rights to the stored data. According to some embodiments, the UDR 214 may store policy data and user subscription data, which may include any or all of subscription identifiers, security credentials, access and mobility related subscription data, and session related data.
[0047] The Application Function (AF) 206 represents the non-data plane (also referred to as non-user plane) functions of applications deployed within the network operator domain and within 3GPP® compliant networks. The AF 206 can interact with other core network functions via a service-based Naf interface to access network capability publication information as well as provide application information for use in decisions such as traffic routing. The AF 206 can also interact with functions such as the PCF 204 to provide application-specific inputs to policy and policy enforcement decisions. It should be understood that in many situations, the AF 206 does not provide network services to other NFs, but instead is often considered a consumer or user of services provided by other NFs. Applications outside the 3GPP® network can perform many of the same functions as the AF 206 by using the NEF 202.
[0048] The UE 210 communicates with network functions that reside in the User Plane (UP) and Control Plane (CP). The UPF 212 is part of the CN UP (the DN 213 is outside the 5GCN). The (R)AN node 211 may be considered part of the user plane, but is not strictly part of the CN and is therefore not considered part of the CN UP or UPF 212. The AMF 208, SMF 209, AUSF 207, NEF 202, NRF 203, PCF 204, and UDM 205 are functions that reside in the CN CP and are often referred to as control plane functions. The AF 206 may communicate with other functions in the CN CP (either directly or indirectly via the NEF 202), but is not typically considered to be part of the CN CP.
[0049] The DN-AAA server 215 may belong to a 5GC (not shown) or a DN. The DN-AAA server performs authentication and authorization. The response (if positive) may include network information such as the user's IPv4 address and / or IPv6 prefix when the SMF 209 is interworking with the DN-AAA server. In the DN, the DN-AAA server communicates with the SMF 209 via the UPF 212, and in the 5GC, the DN-AAA server communicates directly with the SMF 209.
[0050] There were other network functions in 5GC, not shown in Figure 2, but shown in Figures 3a-3c, such as the Charging Function (CHF) 301, responsible for charging, and the Network Slice Specific Authentication and Authorization Function (NSSAAF) 302, supporting network slice specific authentication and authorization by the AAA server (AAA-S). The reference point between the SMF and the CHF is N40. The reference point between the AMF and the NSSAAF is N58. The reference point between the UDM and the NSSAAF is N59.
[0051] Those skilled in the art will appreciate that there may be multiple UPFs connected in series between the (R)AN node 211 and the DN 213, and multiple data sessions to various DNs may be accommodated by using multiple UPFs in parallel.
[0052] 3a-3c show the architecture where I-SMF exists in various situations of an exemplary roaming 5G or next generation core network. FIG. 3a shows a non-roaming architecture with I-SMF insertion into a PDU session in a reference point representation without an uplink classifier / branch point (UL-CL / BP). FIG. 3b shows a non-roaming architecture with I-SMF insertion into a PDU session in a reference point representation with a UL-CL / BP. FIG. 3c shows a local breakout scenario in a roaming 5G system architecture with SMF / I-SMF-reference point representation. As shown in FIG. 3a-3c, each SMF 209 (including I-SMF 209a) can connect to UPF 212 via a logical interface such as network interface N4, where N16a is an interface between SMF and I-SMF, and N38 is an interface between I-SMFs. According to the roaming scenario of FIG. 3c, the SMF controlling the UPF connecting to the NG-(R)AN is separated from the SMF controlling the PDU session anchor. The architecture with I-SMF modification is similar to the architecture with I-SMF insertion in those scenarios, except that a new I-SMF is added.
[0053] As mentioned above, because the UPFs belong to different SMF service areas and the UE is located in an area that cannot be controlled by the original SMF, the intermediate SMF (I-SMF) is an SMF that is inserted to support a PDU session.
[0054] The AMF is responsible for detecting when to add or remove an I-SMF for a PDU session. For this purpose, the AMF obtains information about the service area of the SMF from the NRF. During a mobility event, such as a handover or AMF change, if the service area of the SMF does not cover the new UE location, the AMF selects and inserts an I-SMF that can serve the UE location and the S-NSSAI. Conversely, when the AMF detects that an I-SMF is no longer needed (because the service area of the SMF covers the new UE location), the AMF removes the I-SMF and directly interfaces with the SMF of the PDU session. If the AMF detects that the SMF cannot serve the UE location (for example, due to mobility), the AMF selects a new I-SMF to serve the UE location. If the existing I-SMF cannot serve the UE location (e.g., due to mobility) and the service area of the SMF does not cover the new UE location (or the PDU session is home-routed), the AMF initiates an I-SMF change. In PDU session establishment in non-roaming and roaming with LBO scenarios, if the AMF or SCP cannot select an SMF with a service area that supports the current UE location for the selected (DNN, S-NSSAI) and required SMF capabilities, the AMF selects an SMF for the selected (DNN, S-NSSAI) and required capabilities, and additionally selects an I-SMF that serves the UE location and S-NSSAI.
[0055] In the case of user equipment (UE) IP address management in 5G networks, for PDU session types of IPv4 or IPv6 or IPv4v6, during the PDU session establishment procedure, if a static IP address / prefix is stored in the UDM, the SMF retrieves this static IP address / prefix from the UDM. If the UE's IP address / prefix is not yet assigned and provided to the PCF, the SMF may instead receive a subscriber IP index from the PCF. The subscriber IP index indicates what allocation method (e.g., a specific IP pool, an external server such as a DN-AAA server) should be used for IP address / prefix allocation for the UE. The SMF can use this to help select how the IP address / prefix should be assigned when multiple allocation methods or multiple instances of the same method are supported. Whether the PLMN or the external data network assigns the IP address is transparent to the UE.
[0056] The multiple allocation methods include the SMF allocates an IP address from a pool corresponding to a selected PDU Session Anchor (UPF) and the UE IP address is obtained from the UPF. In that case, the SMF interacts with the UPF via the N4 procedure to obtain any IP address. The SMF provides the UPF with the information (e.g., network instance) it needs to enable it to derive a suitable IP address, and if the UE IP address is obtained from an external data network, the SMF further sends request messages related to allocation, renewal, and release to the external data network, i.e., the DHCP / DN-AAA server, and maintains the corresponding state information. The IP address / prefix allocation request sent to the DHCP / DN-AAA server can include an IP address pool ID to identify which range of IP addresses should be assigned. In this case, the SMF is provisioned with a separate IP address pool ID and a mapping between the IP address pool ID and the UPF Id, DNN, S-NSSAI, IP version. The provisioning is done by OAM or during the N4 related setup procedure.
[0057] A PDU session may be associated with multiple IPv6 prefixes. This is called a multi-homed PDU session. A multi-homed PDU session provides access to a data network via multiple PDU session anchors. Different user plane paths to different PDU session anchors branch off at a "common" UPF, which supports a "branching point" (BP) function and is called the UPF. The branching point provides forwarding of UL traffic to different PDU session anchors and merging of DL traffic to the UE, i.e. merging of traffic from different PDU session anchors on the link to the UE.
[0058] A UPF supporting BP functionality may also be controlled by the SMF to support traffic measurement for charging, traffic duplication for LI, and bit rate enforcement (session per PDU session - AMBR). The insertion and removal of a UPF supporting branching points is determined by the SMF and controlled by the SMF using generic N4 and UPF capabilities. The SMF may decide to insert a UPF supporting branching point functionality into the data path of a PDU session during or after PDU session establishment, or to remove a UPF supporting branching point functionality from the data path of a PDU session after PDU session establishment.
[0059] Multi-homing of PDU sessions applies only to IPv6 type PDU sessions. When the UE requests a PDU session of type "IPv4v6" or "IPv6", the UE also provides an indication to the network whether it supports multi-homed IPv6 PDU sessions or not.
[0060] Fig. 4a shows the addition of a PDU session anchor controlled by an I-SMF. In step 401, the UE 210 establishes a PDU session with the UPF 212a including a PDU session anchor 1 controlled by the SMF 209, and the I-SMF 209a and the I-UPF controlled by the I-SMF 209a are inserted for the PDU session. At some point, using a list of DNAIs received from the SMF and important for this PDU session, the I-SMF 209a decides to establish a new PDU session anchor, for example due to UE mobility. Thus, in step 402, the I-SMF 209a selects the UPF 212b and establishes a new PDU session anchor 2 (PSA2) for the PDU session using N4.
[0061] It should be noted that during step 402, if IPv6 multihoming is applied to the PDU session, a new IPv6 prefix corresponding to PSA2 is assigned by the I-SMF or by the UPF 212b that supports PSA2.
[0062] However, as described above, it is the SMF 209 that receives the Subscribers IP Index from the PCF, and the I-SMF 209a does not have information on the Subscribers IP Index. If an incorrect allocation method is used for IPv6 prefix allocation by the I-SMF, IPv6 multihoming may not function.
[0063] It should also be noted that since the I-SMF 209a does not know the address information of the DN-AAA server, it cannot request an address / prefix allocation from the DN-AAA server 215 and therefore cannot communicate with the DN-AAA server.
[0064] FIG. 4b illustrates an I-SMF insertion procedure according to an embodiment of the present disclosure.
[0065] In step 403, the UE 210 establishes a PDU session with the UPF 212a, which includes a PDU Session Anchor 1 controlled by the SMF 209.
[0066] In step 404, if the AMF 208 selects the I-SMF1 209a, the AMF 208 sends a first request to the I-SMF1 209a to request insertion of the I-SMF1 209a as an I-SMF for the PDU session. The first request may be, for example, a Nsmf_PDUSession_CreateSMContext Request according to the 3GPP standard, including a PDU session ID, an SM context ID, UE location information, an access type, a RAT type, an operation type, etc. The SM context ID points to the SMF 209.
[0067] In step 405, the I-SMF1 209a invokes a second request to create a PDU session for it. The second request may be, for example, an Nsmf_PDUSession_Create Request according to the 3GPP standard, which includes new I-UPF DL tunnel information, new I-UPF tunnel endpoints for buffered DL data, SM context ID in I-SMF1 209a, access type, RAT type, DNAI list supported by I-SMF1 209a, etc.
[0068] The SMF 209 performs some actions to create a PDU session using the received parameters and responds to the I-SMF1 209a in step 406 with a response, for example, Nsmf_PDUSession_Create Response according to the 3GPP standard, which includes the important DNAI for this PDU session, the tunnel information in the UPF (PSA) for UL data is assigned, etc., but if a new element is available, it is added in the response, i.e., the Internet Protocol (IP) address information of the UE is added, such as the subscriber IP index. The premise that a new element is available may be, for example, that some other NF (such as a PCF) has sent the IP address information of the UE to the SMF 209 (such as during the SM policy creation procedure). The subscriber IP index includes the IPv6 prefix. The received IP address information is used for further address association allocation by the I-SMF 209a.
[0069] Additionally or alternatively, if the IP address information indicates that an external network element (such as a DN-AAA server) is used for address / prefix allocation, the response sent from SMF209 to I-SMF209a further includes the address information of the external network element, so that I-SMF209a can obtain the assigned address / prefix by itself.
[0070] At some point, using the list of important DNAIs for this PDU session received from the SMF 209, the I-SMF 209a decides to establish a new PDU session anchor, for example due to UE mobility. In step 407, the I-SMF 209a selects the UPF 212b and establishes a new PDU session anchor 2 (PSA2) for the PDU session using N4. During this step, if IPv6 multihoming is applied to the PDU session, the I-SMF 209a can use the IPv6 prefix received in step 405 for the allocation of a new IPv6 prefix corresponding to PSA2. A similar method applies for multiple new PSAs 2. If an external network element is used for address / prefix allocation, the I-SMF 209a can obtain the assigned address / prefix from the external network element using only the address information of the external network element. In this way, IPv6 indexes are unified across multiple SMFs, therefore IPv6 multihoming works properly, and address / prefix allocation method by external network elements is enabled in the I-SMF by notifying the I-SMF address information of the external network element.
[0071] FIG. 4c illustrates an I-SMF modification procedure according to an embodiment of the present disclosure.
[0072] In step 408, the UE 210 establishes a PDU session with the UPF 212a that includes a PDU Session Anchor 1 controlled by the SMF 209. The PDU session includes an I-SMF 209a and an I-UPF controlled by the I-SMF 209a.
[0073] In step 408, if the AMF selects a new I-SMF 209b, the AMF 208 sends a first request to the I-SMF1 209a requesting the I-SMF 209b to become the I-SMF for the PDU session instead of the I-SMF 209a. The first request may be, for example, a Nsmf_PDUSession_CreateSMContext Request according to the 3GPP standard, comprising a PDU session ID, an SM context ID, UE location information, access type, RAT type, action type, etc. The SM context ID points to the old I-SMF 209a.
[0074] In step 409, the new I-SMF 209b obtains the SM context from the old I-SMF 209a by invoking a second request to obtain the UE service management context. The second request can be, for example, a Nsmf_PDUSession_Context Request according to the 3GPP standard, including a SM context type, a SM context ID, etc. The new I-SMF 209b uses the SM context ID received from the AMF 208 for this service operation. The SM context ID is used by the recipient of the Nsmf_PDUSession_Context Request 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.
[0075] In step 410, the old I-SMF 209a responds with the SM context of the indicated PDU session in a response, e.g., Nsmf_PDUSession_Context Response. The SM context in the response may include the UE's address information, such as Internet Protocol (IP) address, subscriber IP index, etc., if available. The assumption that the UE's IP address information is available may be, for example, that some other NF (such as SMF 209) sent the UE's IP address information to the old I-SMF 209a. The subscriber IP index includes an IPv6 prefix. The received IP address information is used for further address association allocation by the new I-SMF 209b.
[0076] Additionally or alternatively, if the IP address information indicates that an external network element (such as a DN-AAA server) is used for address / prefix allocation, the response sent from the old SMF 209a to the new I-SMF 209b further includes the address information of the external network element, so that the I-SMF 209b can obtain the assigned address / prefix by itself.
[0077] In step 411, the new I-SMF 209b invokes an update request towards the SMF 209, which may be an Nsmf_PDUSession_Update Request according to the 3GPP standard, including, for example, an SM context ID, new I-UPF DL tunnel information, an SM context ID in the I-SMF 209b, an access type, a RAT type, a DNAI list supported by the new I-SMF 209b, and IP address information.
[0078] In step 412, the SMF responds with an update response to the new I-SMF 209b, which may be, for example, an Nsmf_PDUSession_Update Response with the critical DNAI for this PDU session.
[0079] At some point, using the list of important DNAIs for this PDU session received from the SMF 209, the I-SMF 209a decides to establish a new PDU session anchor, for example due to UE mobility. In step 413, the I-SMF 209b selects the UPF 212b and establishes a new PDU session anchor 2 (PSA2) for the PDU session using N4. During this step, if IPv6 multihoming is applied to the PDU session, the I-SMF 209b can use the IPv6 prefix received in step 410 for allocation of a new IPv6 prefix corresponding to PSA2. A similar method applies to multiple new PSAs 2. If an external network element is used for address / prefix allocation, the I-SMF 209a can obtain the assigned address / prefix from the external network element using only the address information of the external network element. In this way, the IPv6 indexes will be consistent between SMFs, therefore IPv6 multihoming will work properly, and the method of address / prefix allocation by the external network element will be enabled in the new I-SMF by notifying the external network element's new I-SMF address information.
[0080] 5 shows a flowchart of an embodiment of a UE service management network element according to an embodiment of the present disclosure. In one example, the UE service management network element comprises an SMF network element. The SMF network element may simply play the role of the SMF for the UE, or may play the role of the I-SMF for the UE. This flowchart shows a flowchart for both of these cases, where the communication network may be a 5G network, a 5G network combined with a 4G network, or any other suitable network.
[0081] In step 501, the UE service management network element receives a first request. Then, in step 502, it is determined whether the first request is to request the UE service management network element to be an intermediate UE service management network element for the service of the UE, and if the answer is yes, the flowchart proceeds to step 503, to send a second request to another UE service management network element indicated in the first request, and in step 504, a response corresponding to the second request can be received, where the response can include Internet Protocol (IP) address information of the UE.
[0082] According to one embodiment, the first request is to request insertion of the UE service management network element as an intermediate UE service management network element for the UE service, for example, Nsmf_PDUSession_CreateSMContext Request according to the 3GPP® standard, and the second request is a request to create the UE service, such as Nsmf_PDUSession_Create Request according to the 3GPP® standard. Further details can be found in steps 404 and 405 above and will not be repeated here. According to this embodiment, the response corresponding to the second request received in step 504, for example, Nsmf_PDUSession_Create Response according to the 3GPP® standard, includes the essential DNAI for this PDU session, tunnel information in UPF (PSA) for UL data, etc., but may also include a new element, i.e., Internet Protocol (IP) address information of the UE, such as a subscriber IP index, if available. The subscriber IP index includes an IPv6 prefix. The received IP address information may be used for another address association allocation by the UE service management network element. If the IP address information indicates that an external network element (e.g., a DN-AAA server) is used for address / prefix allocation, the response further includes address information of the external network element (e.g., a DN-AAA server), so that the UE service management network element can obtain the assigned address / prefix from the external network element (e.g., the DN-AAA server) itself.
[0083] According to one embodiment, the first request is a request for the UE service management network element to be an intermediate UE service management network element for the UE's service for a change, such as Nsmf_PDUSession_CreateSMContext Request according to the 3GPP® standard, and the second request is a request for obtaining a UE service management context, such as Nsmf_PDUSession_Context Request according to the 3GPP® standard. Further details can be found in steps 408 and 409 above and will not be repeated here. According to this embodiment, a response corresponding to the second request received in step 504, for example, Nsmf_PDUSession_Context Response, is received. The SM context stored in the response may include Internet Protocol (IP) address information of the UE, such as a subscriber IP index, if available. The subscriber IP index includes an IPv6 prefix. The received IP address information may be used for another address association allocation by the UE service management network element. If the IP address information indicates that an external network element (e.g., a DN-AAA server) is used for address / prefix allocation, the response further includes address information of the external network element (e.g., a DN-AAA server), so that the UE service management network element can obtain the assigned address / prefix from the external network element (e.g., the DN-AAA server) itself.
[0084] Then, in step 505, the UE service management network element may use the IP address information for another address related allocation, for example, if IPv6 multihoming is applied to a UE service such as a PDU session, the received IPv6 prefix may be used for allocation of one or more new UE service anchors (such as PDU Session Anchor 2 (PSA2)) for the UE service (such as a PDU session), and if the IP address information indicates that an external network element (such as a DN-AAA server) is used for address / prefix allocation, the received DN-AAA server address information may be used to obtain an assigned address / prefix from the external network element (such as the DN-AAA server).
[0085] In this way, the IP address information of the UE is unified across multiple SMFs, and in the specific case where the IP address information is an IPv6 prefix, IPv6 multihoming works properly, and by receiving the new I-SMF address information of the external network element, the method of address / prefix allocation by the external network element is enabled in the receiving SMF.
[0086] If the UE service management network element determines in step 506 that the first request is a request for creating a service for the UE, for example, a Nsmf_PDUSession_Create Request according to the 3GPP® standard, then in step 507, a corresponding response is sent as a corresponding response including the IP address information of the UE, if available. The corresponding response is, for example, a Nsmf_PDUSession_Create Response according to the 3GPP® standard, which may include the important DNAI for this PDU session, tunnel information in UPF (PSA) for UL data, etc. However, if available, a new element, i.e., the Internet Protocol (IP) address information of the UE, such as a subscriber IP index, will be added. The subscriber IP index includes an IPv6 prefix. If the IP address information indicates that an external network element (e.g., a DN-AAA server) is used for address / prefix allocation, the corresponding response further includes address information of the external network element (e.g., a DN-AAA server), so that the recipient of the corresponding response can obtain the assigned address / prefix from the external network element (e.g., the DN-AAA server) by itself.
[0087] 6a illustrates a schematic block diagram of a UE service management network element operating in a communication network according to an embodiment of the present disclosure. The UE service management network element may be an SMF, and the communication network here may be a 5G network, a 5G network combined with a 4G network, or any other suitable network.
[0088] The parts of the UE service management network element 61 that are most affected by the adaptation of the methods described in the present disclosure, e.g. the parts of the methods described with reference to Figures 4b, 4c and 5, are shown as arrangement 611 surrounded by a dashed line. The UE service management network element 61 and the arrangement 611 may be further configured to communicate with other entities, such as network elements of the AMF, via a communication component 612, which may be considered as part of the arrangement 611 (shown here). The communication component 612 comprises means for communication. The arrangement 611 or the UE service management network element 61 may further comprise further functions 614, such as functional components providing normal UE functions, and may further comprise one or more storage devices 613.
[0089] The arrangement 611 may be implemented by, for example, one or more of a processor or microprocessor, suitable software and memory for storing the software, a programmable logic device (PLD) or other electronic component(s), and processing circuitry configured to perform the operations described above, for example as shown in Figures 4b, 4c, and / or 5. The UE service management network element arrangement 611 may be implemented and / or described as follows.
[0090] Referring to FIG. 6, the UE service management network element may comprise a first receiving component 6111, a first transmitting component 6112, a second receiving component 6113, an allocating component 6114, and a second transmitting component 6115.
[0091] The first receiving component 6111 is configured to receive a first request, the details of the operation of which can be found in step 501 as described above and will not be repeated in this disclosure.
[0092] The first sending component 6112 is configured to send a second request to another UE service management network element indicated in the first request in response to the first request being a request to the UE service management network element to be an intermediate UE service management network element for the UE's service, the details of the action being found in step 503 as described above and not repeated in this disclosure. The second receiving component 6113 is configured to receive a response corresponding to the second request, the response including Internet Protocol, IP, address information of the UE, and additionally or alternatively, the response including address information of the external network element if the UE's IP address information indicates that the external network element is used for address / prefix allocation. The details of the action can be found in step 505 as described above and not repeated in this disclosure.
[0093] The allocation component 6114 is configured to use the IP address information for other address-related allocations and additionally or alternatively use the address information of the external network element to obtain an assigned address / prefix from the external network element. Details of the actions can be found in step 505, as described above, and will not be repeated in this disclosure.
[0094] The second sending component 6115 is configured to send a corresponding response including the IP address information of the UE in response to determining that the first request is a request to create a service for the UE, and additionally or alternatively, the corresponding response includes the address information of the external network element if the IP address information of the UE indicates that the external network element is to be used for address / prefix allocation. Details of the actions can be found in step 507 as described above and will not be repeated in this disclosure.
[0095] It should be noted that two or more different units in the present disclosure may be logically or physically combined.
[0096] FIG. 7 illustrates an embodiment of an arrangement 700 that may be used in a UE service management network element or a network function selection network element. The arrangement 700 includes a processor 706 having, for example, a digital signal processor (DSP). The processor 706 may be a single unit or multiple units for performing different operations of the procedures described in the present disclosure. The arrangement 700 may also include an input unit 702 for receiving signals from other entities and an output unit 704 for providing signals to other entities. The input and output units may be arranged as an integrated network element or as shown in the examples of FIGS. 6a-6c.
[0097] Furthermore, the arrangement 700 comprises at least one computer program product 708 in the form of a non-volatile or volatile memory, e.g., Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory and hard drive, and from a network or cloud connected via the input 702 and the output 704. The computer program product 708 comprises a computer program 710 comprising code / computer readable instructions, which when executed by the processor 706 in the arrangement 700, causes the arrangement 700 and / or the UE service management network element or the network function selection network element to perform operations of the procedures described above in relation to, e.g., Figure 4b, Figure 4c or Figure 5.
[0098] The computer program 710 may be configured as a computer program code structured in a computer program module. Thus, according to an exemplary embodiment, when the arrangement 700 is used in a UE service management network element, the code in the computer program of the arrangement 700, when executed, causes the processor 706 to perform the steps described with reference to FIG.
[0099] The processor 706 may be a single central processing unit (CPU), but may also comprise two or more processing units. For example, the processor 706 may include a general-purpose microprocessor, an instruction set processor, and / or an associated chipset, and / or a special-purpose microprocessor, such as an application-specific integrated circuit (ASIC). The processor 706 may also comprise on-board memory for cache purposes. The computer program 710 may be carried by a computer program product 708 connected to the processor 706. The computer program product may comprise a computer-readable medium on which the computer program is stored. For example, the computer program product may be a flash memory, a random access memory (RAM), a read-only memory (ROM), or an EEPROM, and the above computer program modules may be distributed on various computer program products in the form of memory according to alternative embodiments.
[0100] Overall, or depending on the scenario, by providing the UE's IP address information from the old SMF to the new SMF in the I-SMF insertion procedure or I-SMF change procedure, the UE's IP address information, e.g., subscriber IP index, including the IPv6 index, will match between the SMFs serving the UE, and the address / index allocation by the new SMF can work well with the IP address information of the old SMF. By providing the new I-SMF address information of the external network element, a method of address / prefix allocation by the external network element (such as a DN-AAA server) is enabled in the receiving SMF.
[0101] Although the embodiments have been described above, those skilled in the art will understand that various changes and modifications can be made without departing from the true scope of the present technology, and equivalents can be substituted for the elements. In addition, many modifications can be made to adapt to a particular situation and the teachings of the present disclosure without departing from its central scope. Therefore, the present embodiments are not limited to the specific embodiments disclosed as the best mode contemplated for carrying out the present technology, but are intended to include all embodiments falling within the scope of the appended claims.
Claims
1. A method for User Equipment (UE) service management network element in a communication network, comprising: Receiving a first request (501); in response to determining that the first request includes an SM context ID that points to another UE service management network element; sending (503) a second request to the other UE service management network element indicated in the first request; and receiving (504) a first response corresponding to the second request, the first response including Internet Protocol (IP) address information of the UE; The IP address information of the UE indicates what allocation method is used to allocate an IP address or prefix for the UE.
2. A method for User Equipment (UE) service management network element in a communication network, comprising: Receiving a first request (501); in response to determining that the first request is for the UE service management network element to be an intermediate UE service management network element for a service of the UE; sending (503) a second request to another UE service management network element indicated in the first request; and receiving (504) a first response corresponding to the second request, the first response including Internet Protocol (IP) address information of the UE, the IP address information of the UE including an IP index.
3. 2. The method of claim 1, wherein the IP address information of the UE indicates that an external network element is to be used for address allocation, and the first response further includes address information of the external network element.
4. 4. The method of claim 3, comprising: ● Obtaining an assigned address for the UE from the external network element using the address information of the external network element.
5. 2. The method of claim 1, wherein the first request is for insertion of the UE service management network element as an intermediate UE service management network element for a service of the UE, and the second request is a request to create the service of the UE.
6. 2. The method of claim 1, wherein the first request is a request to change the UE service management network element to be an intermediate UE service management network element for a service of the UE, and the second request is a request to obtain a UE service management context.
7. 10. The method of claim 1 further comprising: in response to determining that the first request is a request to create a service for the UE; The method further comprises: sending (507) a second response including IP address information of the UE.
8. 8. The method of claim 7, wherein the IP address information of the UE indicates that an external network element is used for address allocation, the second response further includes address information of the external network element, and / or the first request is an Nsmf_PDUSession_Create Request.
9. The method of claim 1 , wherein the IP address information of the UE includes an IP index.
10. 5. The method according to claim 3 or 4, wherein IPv6 multihoming is applied to the service of the UE, and the IP address information includes an IPv6 prefix, the method further comprising: and using the IPv6 prefix for IPv6 prefix allocation to one or more UE service anchors (212b).
11. 2. The method of claim 1, wherein the UE service management network element comprises a Session Management Function (SMF) network element, the UE service comprises a Protocol Data Unit (PDU) session of the UE, and / or the communication network comprises a fifth generation network.
12. 6. The method of claim 5, wherein the first request is a Nsmf_PDUSession_CreateSMContext Request and the second request is a Nsmf_PDUSession_Create Request.
13. 7. The method of claim 6, wherein the first request is a Nsmf_PDUSession_CreateSMContext Request and the second request is a Nsmf_PDUSession_Context Request.
14. 9. The method of claim 3, 4 or 8, wherein the external network element comprises a Data Network Authentication, Authorization and Accounting (DN-AAA) server.
15. A communication device in a communication network, comprising: A storage device (708) adapted to store instructions; and A communications device comprising: a processor (706) adapted to execute said instructions to cause said communications device to perform the steps of any one of claims 1 to 14.
Citation Information
Patent Citations
SMF Insertion Method and AMF Entity
JP2020523870A
Data Processing Method and Apparatus, and Device
US20200274805A1
Session processing method, communication device and communication system
WO2020200242A1
