Method and apparatus for information synchronization

Abstract

Embodiments of the present disclosure provide a method and apparatus for information synchronization. A method at a data management node includes receiving a first message including an identifier of the first gateway from a first gateway. The first gateway services a session of a terminal device. The terminal device accesses a network from a second gateway. The method also includes sending a second message including the identifier of the first gateway to an authentication, authorization, and accounting (AAA) server. The first message also includes a first indication that the terminal device accessed the network from the second gateway.

Description

Technical Field

[0001] Non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and more particularly, to methods and apparatus for information synchronization. Background Art

[0002] This section introduces various 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 admissions about what is or is not in the prior art.

[0003] The 3GPP (3rd Generation Partnership Project) EPS (Evolved Packet System) core network supports UE connectivity to non-3GPP IP (Internet Protocol) access networks (e.g., WLAN (Wireless Local Area Network)) via the Evolved Packet Core (EPC) integrated via the Evolved Packet Data Gateway (ePDG). 3GPP also defines interworking between the ePDG connected to the EPC and the 5GS (Fifth Generation System).

[0004] In order to support smooth switching between 3GPP access and non-3GPP access and IP address preservation for user equipment (UE), the address information of the combined session management function plus packet data network gateway control plane (SMF+PGW-C) entity is shared and / or synchronized between EPC and 5GC (fifth generation core network) via HSS (home subscriber server) / UDM (unified data management). The AMF (access and mobility management function) can read data from HSS / UDM and select the same combined SMF+PGW-C if conditions permit (for example, UE terminal supports this function, UE subscription support, combined SMF+PGW-C is available, etc.). Summary of the Invention

[0005] This Summary is provided in a simplified form to introduce selected concepts 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 3GPP TS 23.501 V16.4.0 (the disclosure of which is incorporated herein by reference in its entirety), enhancements to the interworking between ePDG / EPC and 5GS (i.e., using the N10 interface instead of S6b) were introduced to make the S6b interface optional between the SMF+PGW-C and the 3GPP AAA server. However, there are some issues with using the N10 interface instead of S6b. For example, as defined in 3GPP TS 23.402 V16.0.0, the notification of PGW-C assignment from the HSS to the 3GPP AAA server will trigger the 3GPP AAA server to update the ePDG with the new PGW identity data via the SWm interface request procedure. However, in this case, it is the ePDG that selects the SMF+PGW-C, so notifying the ePDG of the PGW-C allocation is redundant and may lead to incorrect interpretation and processing in the ePDG, such as releasing the existing established PDN connection and establishing a new PDN connection on the SMF+PGW-C as shown in the PGW-C allocation message notification.

[0007] In order to overcome or alleviate the above problems or other problems, embodiments of the present disclosure provide an improved information synchronization solution.

[0008] In a first aspect of the present disclosure, a method at a data management node is provided. The method includes receiving a first message including an identifier of the first gateway from a first gateway. The first gateway services a session of a terminal device. The terminal device accesses a network through a second gateway. The method also includes sending a second message including the identifier of the first gateway to an authentication, authorization, and accounting (AAA) server.

[0009] In one embodiment, the first message may further include a first indication that the terminal device accesses the network from the second gateway.

[0010] In one embodiment, the second message may further include a second instruction for instructing the AAA server to suppress the request toward the second gateway.

[0011] In one embodiment, the request may be a reauthorization request.

[0012] In one embodiment, the second message may further include a second instruction for instructing the terminal device to access the network from the second gateway.

[0013] In one embodiment, the method may further include storing an identification of the first gateway.

[0014] In one embodiment, the identifier of the first gateway may be a fully qualified domain name (FQDN) or an Internet Protocol (IP) address.

[0015] In one embodiment, the data management node may be a combined Home Subscriber Server plus Unified Data Management (HSS+UDM) entity.

[0016] In one embodiment, the first gateway may be a combined Session Management Function plus Packet Data Network Gateway Control Plane (SMF+PGW-C) entity.

[0017] In one embodiment, the second gateway may be an evolved packet data gateway (ePDG).

[0018] In one embodiment, the first message may be a Nudm_UECM_Registration request.

[0019] In one embodiment, the second message may be a Push-Profile-Request message.

[0020] In a second aspect of the present disclosure, a method is provided at an authentication, authorization, and accounting (AAA) server. The method includes receiving, from a data management node, a message including an identifier of a first gateway serving a session with an end-point device. The method also includes suppressing a request to a second gateway based on the message. The end-point device accesses a network from the second gateway.

[0021] In one embodiment, the request may be a reauthorization request.

[0022] In one embodiment, the message may further include an instruction for instructing the AAA server to suppress the request towards the second gateway.

[0023] In one embodiment, the message may further include an instruction for instructing the terminal device to access the network from the second gateway.

[0024] In one embodiment, the method may further include storing an identification of the first gateway.

[0025] In one embodiment, the message may be a Push-Profile-Request message.

[0026] In a third aspect of the present disclosure, a data management node is provided. The data management node includes a processor; and a memory coupled to the processor, the memory storing instructions executable by the processor, whereby the data management node is operable to receive a first message including an identifier of the first gateway from a first gateway. The first gateway services a session of a terminal device. The terminal device accesses a network from a second gateway. The data management node is further operable to send a second message including the identifier of the first gateway to an authentication, authorization, and accounting (AAA) server. The first message also includes a first indication that the terminal device accessed the network from the second gateway.

[0027] In a fourth aspect of the present disclosure, an authentication, authorization, and accounting (AAA) server is provided. The AAA server includes a processor; and a memory coupled to the processor, the memory storing instructions executable by the processor, whereby the AAA server is operable to receive a message from a data management node including an identification of a first gateway serving a session of an end-point device. The AAA server is also operable to suppress a request to a second gateway based on the message. The end-point device accesses a network from the second gateway.

[0028] In a fifth aspect of the present disclosure, a data management node is provided. The data management node includes a receiving module and a sending module. The receiving module can be configured to receive a first message including an identifier of the first gateway from a first gateway. The first gateway serves a session of a terminal device. The terminal device accesses a network from a second gateway. The sending module can be configured to send a second message including an identifier of the first gateway to an authentication, authorization, and accounting (AAA) server. The first message also includes a first indication that the terminal device accesses the network from the second gateway.

[0029] In one embodiment, the data management node may further include a storage module configured to store an identifier of the first gateway.

[0030] In a sixth aspect of the present disclosure, an AAA server is provided. The AAA server includes a receiving module and a suppression module. The receiving module may be configured to receive a message from a data management node including an identifier of a first gateway serving a session of a terminal device. The suppression module may be configured to suppress a request to a second gateway based on the message. The terminal device accesses a network through the second gateway.

[0031] In one embodiment, the AAA server may further include a storage module configured to store the identification of the first gateway.

[0032] In a seventh aspect of the present disclosure, a computer program product is provided, comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to any one of the first and second aspects of the present disclosure.

[0033] In an eighth aspect of the present disclosure, a computer-readable storage medium storing instructions is provided. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method according to any one of the first and second aspects of the present disclosure.

[0034] The embodiments herein provide many advantages, the following is a non-exhaustive list of examples of the advantages. In some embodiments herein, if the PGW-C+SMF is selected from the ePDG for the UE to establish a PDN connection, and the N10 interface is used to report the PGW allocation information to the HSS / UDM, the proposed solution can ensure that the correct PGW allocation information is available in the 3GPP AAA server. Therefore, in a later handover, the 3GPP AAA server can provide the ePDG with appropriate information of the PGW. In some embodiments herein, the proposed solution can ensure that appropriate indications are provided to the 3GPP AAA server, so that it can suppress the request process to the ePDG to avoid misinterpretation / mishandling in the ePDG. The embodiments herein are not limited to the above-mentioned features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description taken in conjunction with the accompanying drawings, by way of example, in which like reference numerals or letters are used to designate similar or equivalent elements. The accompanying drawings are illustrated to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0036] Figure 1 Schematically illustrates a non-roaming architecture for intercommunication between ePDG / EPC and 5GS according to an embodiment of the present disclosure;

[0037] Figure 2 Schematically illustrates a local breakout roaming architecture for intercommunication between ePDG / EPC and 5GS according to an embodiment of the present disclosure;

[0038] Figure 3 Schematically illustrates a home routing roaming architecture for intercommunication between ePDG / EPC and 5GS according to an embodiment of the present disclosure;

[0039] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0040] Figure 5 A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0041] Figure 6 A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0042] Figure 7a A simplified block diagram illustrating an apparatus that may be implemented in / as a data management node according to an embodiment of the present disclosure is shown;

[0043] Figure 7b shows a simplified block diagram of an apparatus that may be implemented in / as an AAA server according to an embodiment of the present disclosure;

[0044] Figure 8 is a block diagram illustrating a data management node according to an embodiment of the present disclosure; and

[0045] Figure 9 is a block diagram illustrating an AAA server according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] 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 for the purpose of enabling those skilled in the art to better understand and therefore implement the present disclosure, and that no limitation on the scope of the present disclosure is suggested. References to features, advantages or similar language throughout the specification do not mean that all features and advantages that can be implemented with the present disclosure should be in or in any single embodiment of the present disclosure. On the contrary, language referring to features and advantages should be understood to mean that specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, in one or more embodiments, the features, advantages and characteristics described in the present disclosure may be combined in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, while the additional features and advantages may not be present in all embodiments of the present disclosure.

[0047] As used herein, the term "network" refers to a network that complies with any suitable wireless / wired communication standard, such as 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. A CDMA network can implement a radio technology such as Universal Terrestrial Radio Access (UTRA). UTRA includes WCDMA and other variants of CDMA. A TDMA network can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, and the like. In the following description, the terms "network" and "system" may be used interchangeably. Furthermore, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to communication protocols defined by some standards organizations such as 3GPP (3rd Generation Partnership Project). For example, the communication protocols defined by 3GPP may include third generation (3G), fourth generation (4G), 4.5G, fourth generation (5G) communication protocols, and / or any other protocols currently known or developed in the future.

[0048] As used herein, the term "network node" refers to a network device or entity, such as a core network device, in a communication network. For example, in a wireless communication network such as a 3GPP-type cellular network, a network node may be a core network device that provides a variety of services to clients interconnected via access network devices. Each access network device may be connected to the core network device via a wired or wireless connection.

[0049] The term "network function (NF)" refers to any appropriate function that can be implemented in a network entity (physical or virtual) of a communications network. For example, a 5G system (5GS) may include multiple NFs, such as an AMF (Access and Mobility Management Function), an SMF (Session Management Function), an AUSF (Authentication Service Function), an UDM (Unified Data Management), a PCF (Policy Control Function), an AF (Application Function), a NEF (Network Exposure Function), an UPF (User Plane Function), and an NRF (Network Resource Function), as well as RAN (Radio Access Network), an SCP (Service Communication Agent), and an NWDAF (Network Data Analysis Function). In other embodiments, for example, depending on the specific network, the network function may include different types of NFs. A 4G system may include multiple network entities, such as a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network (PDN) Gateway (PGW), a PCRF (Policy and Charging Rules Function), a 3GPP AAA server, an HSS, an ePDG, and an eNB. The control and user plane separation (CUPS) architecture for various network devices (such as SGW and PGW) has been introduced into communications networks. In the CUPS architecture, various interfaces between control plane nodes (or functions) and user plane nodes (or functions) have been defined. For example, the Sxb interface is defined between the PGW control plane (PGW-C) and the PGW user plane (PGW-U), and the Sxa interface is defined between the SGW control plane and the SGW user plane. The N4 interface is defined between the session management function (SMF) and the user plane function (UPF). In some embodiments, network entities or functions with the same or similar functions in different networks can be referred to as combined network entities, such as PGW-C+SMF, PGW-U+UPF, PCF+PCRF, etc.

[0050] The term "terminal device" refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, 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). Terminal devices may include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (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 in accordance with one or more communication standards promulgated by 3GPP (3rd Generation Partnership Project), such as 3GPP's LTE standard or NR standard. As used herein, a human user who owns and / or operates the relevant device is referred to as a UE.

[0051] A "user equipment" or "UE" may not necessarily have a "user." 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 communications network, a terminal device may be designed to send information to the network on a predetermined schedule. Alternatively, a UE may represent a device that is intended for sale to or operated by a human user but may not initially be associated with a specific human user.

[0052] As another example, in an Internet of Things (IoT) scenario, a terminal device 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 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 (e.g., electricity meters, industrial machinery), or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (e.g., watches), etc. In other scenarios, the terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0053] References in the specification to "one embodiment," "an embodiment," "an exemplary 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. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of those skilled in the art to influence such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0054] It should be understood that although the terms "first" and "second" 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. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0055] As used herein, the phrase "at least one of A and 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 both A and B."

[0056] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the example embodiments. Unless the context clearly indicates otherwise, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well. It will be further understood that when used herein, the terms "include," "comprising," "having," "having," "containing," and / or "covering" specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0057] Note that these terms are used herein only for convenience of description and to distinguish between nodes, devices, or networks, etc. As technology develops, other terms with similar / identical meanings may also be used.

[0058] 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.

[0059] Note that some embodiments of the present disclosure are primarily described with respect to cellular networks, as defined by 3GPP, used as non-limiting examples of certain exemplary network configurations and system deployments. Therefore, the description of the exemplary embodiments presented herein specifically refers to terms directly related thereto. Such terms are used only in the context of the non-limiting examples and embodiments presented and naturally do not limit the present disclosure in any way. Rather, any other system configuration or radio technology may be used equally, provided that the exemplary embodiments described herein are applicable.

[0060] While the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to systems that conform to Figure 1-3 The exemplary system architecture shown is described for a communication system. Figure 1-3 Only some exemplary elements are depicted. In practice, a communication system may also include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). A communication system may provide communication and various types of services to one or more terminal devices, facilitating the terminal devices to access the communication system and / or use services provided by or via the communication system.

[0061] Figure 1 The non-roaming architecture for intercommunication between ePDG / EPC and 5GS according to an embodiment of the present disclosure is schematically shown. Figure 1 The system architecture is consistent with 3GPP TS 23.501V16.4.0 Figure 4 .3.4.1-1, and may include some exemplary network nodes, such as UE, ePDG, 3GPP AAA server, UPF+PGW-U, SMF+PGW-C, PCF, HSS+UDM, AMF, NG-RAN (Next Generation RAN). Figure 1 As further shown, the exemplary system architecture also includes some interfaces, such as S2b-C, S2b-U, SWm, SWx, S6b, N10, N7, N4, N1, N2, N3, N8, N11 and N15. Figure 1 The various network nodes shown in may be responsible for functions as defined, for example, in various 3GPP specifications (eg, 3GPP TS 23.501 V16.4.0 and 3GPP TS 23401 V16.6.0, the disclosures of which are incorporated herein by reference in their entireties).

[0062] Figure 2 The figure schematically illustrates a local grooming roaming architecture for interworking between ePDG / EPC and 5GS according to an embodiment of the present disclosure. Figure 3The figure schematically illustrates a home routing roaming architecture for interworking between ePDG / EPC and 5GS according to an embodiment of the present disclosure. Figure 2 The system architecture is consistent with 3GPP TS 23.501V16.4.0 Figure 4 .The architecture is the same as 3.4.2-1. Figure 3 The system architecture is consistent with 3GPP TS 23.501V16.4.0 Figure 4 .The architecture of 3.4.2-2 is the same.

[0063] Figure 2 The system architecture may include some exemplary network nodes, such as UE, ePDG, 3GPP AAA agent, 3GPP AAA server, UPF+PGW-U, SMF+PGW-C, h-PCF (home PCF), v-PCF (visited PCF), HSS+UDM, AMF, NG-RAN. Figure 2 As further shown, the exemplary system architecture also includes some interfaces, such as S2b-C, S2b-U, SWm, SWx, SWd, S6b, N10, N24, N7, N4, N1, N2, N3, N8, N11 and N15. Figure 2 The various network nodes shown in FIG may be responsible for functions as defined, for example, in various 3GPP specifications (e.g., 3GPP TS 23.501 V16.4.0 and 3GPP TS 23401 V16.6.0, the disclosures of which are incorporated herein by reference in their entireties). HPLMN stands for Home Public Land Mobile Network. VPLMN stands for Visited Public Land Mobile Network.

[0064] Figure 3 The system architecture may include some exemplary network nodes, such as UE, ePDG, 3GPP AAA agent, 3GPP AAA server, UPF+PGW-U, SMF+PGW-C, h-PCF (home PCF), HSS+UDM, v-PCF (visited PCF), v-SMF (visited SMF), UPF, AMF, NG-RAN. Figure 3 As further shown, the exemplary system architecture also includes some interfaces, such as S2b-C, S2b-U, SWm, SWx, SWd, S6b, N10, N7, N4, N1, N2, N3, N4, N8, N9, N16, N24, N11 and N15, etc. Figure 3 The various network nodes shown in may be responsible for functionality as defined, for example, in various 3GPP specifications (eg, 3GPP TS 23.501 V16.4.0 and 3GPP TS 23401 V16.6.0, the disclosures of which are incorporated herein by reference in their entireties).

[0065] 3GPP TS 23.402 V16.0.0 records the detailed information of the interfaces between the UE and the ePDG and between the EPC nodes (i.e., SWm, SWd, SWx, S2b, and S6b).

[0066] Interworking with ePDG is only supported using S2b over GTP (GPRS (General Packet Radio Service) Tunneling Protocol). The S6b interface is optional.

[0067] The PGW (Packet Data Network Gateway) allocation information for non-3GPP access can be reported by the selected SMF + PGW-C to the 3GPP AAA server via the S6b interface, where the 3GPP AAA server further reports this information to the HSS / UDM via the Swx interface. Therefore, the HSS / UDM can save and store the PGW allocation information.

[0068] In 3GPP TS 23.501 V16.4.0, enhancements to interworking between the ePDG / EPC and 5GS were introduced to make the S6b interface optional between the SMF+PGW-C and the 3GPP AAA server. The N10 interface of the SMF+PGW-C can instead provide the previously required functionality of S6b, such as registering and deregistering the PGW-C address with the HSS / UDM via the Nudm_UECM_registration service operation of the N10 interface. This functionality allows the removal or avoidance of the diameter-based S6b interface on the SMF+PGW-C in preparation for the rollout of the 5GC core network.

[0069] Regarding the synchronization of address information of SMF+PGW-C based on this optional feature, 3GPP TS 23.502 V16.4.0 (the disclosure of which is incorporated herein by reference in its entirety) further defines "Indication that access is from ePDG" (also known as "ePDG access indication"), which allows HSS / UDM to synchronize SMF+PGW-C information, but does not further affect the legacy 3GPP AAA / ePDG.

[0070] As described in 3GPP TS 23.502 V16.4.0, Section 4.11.4.3.6, this clause applies to the case where the ePDG is connected to the SMF+PGW-C and S6b is not used. It applies to the procedures specified in 3GPP TS 23.402 V16.0.0 (the disclosure of which is incorporated herein by reference), including mobility between EPC / ePDG and EPC / EUTRAN (Evolved Universal Terrestrial Radio Access Network), and also applies to mobility between EPC / ePDG and 5GS.

[0071] When S6b is not deployed between the PGW-C+SMF and the 3GPP AAA server as specified in 3GPP TS 23.402 V16.0.0, and the UE creates and deletes a PDN connection through the ePDG connected to the SMF+PGW-C, registration and deregistration of the PDN GW are performed on the N10 interface instead of the S6b interface.

[0072] If PGW-C+SMF is selected for a UE that does not support 5GC NAS (Non-Access Stratum), the PGW-C+SMF determines the PDU (Protocol Data Unit) Session ID (Identifier) ​​and S-NSSAI (Single Network Slice Selection Assistance Information) in the same way as specified in clause 4.11.0a.5 of 3GPP TS 23.402 V16.0.0 for PDN connections over EPC / EUTRAN.

[0073] For roaming scenarios with local breakout (such as 3GPP TS 23.501 V16.4.0 Figure 4 .3.4.2.1), using the N10 interface instead of the S6b interface can be based on the support of this function of the N10 interface from HSS+UDM to SMF+PGW-C.

[0074] The specific impact on the procedures in clauses 7 and 8 of 3GPP TS 23.402 V16.0.0 is as follows:

[0075] 7.2.4 Initial Attachment Using GTP (GPRS (General Packet Radio Service) Tunneling Protocol) on S2b

[0076] - Instead of step C.1 in Figure 7.2.4-1 of 3GPP TS 23.402 V16.0.0, perform the following between SMF+PGW-C and HSS+UDM: Figure 4 Step 16c in 3.2.2.1-1 (Nudm_UECM_Registration with optional indication of access from ePDG) Based on this indication, HSS+UDM does not send notification of PGW-C allocation to AAA on SWx.

[0077] However, the above optional functions in 3GPP Release 16 do not work in certain scenarios. For example, when the UE triggers one or more PDN connection establishments in the EPC on the ePDG, the 3GPP AAA reads the user profile (including APN (Access Point Name) configuration and available SMF+PGW-C information) from the HSS and caches the user profile locally.

[0078] As a first example, assuming that a PDN connection over an Internet APN has been established through EPC / LTE, the cached information in AAA and in HSS / UDM may be as follows:

[0079] HSS / UDM:

[0080] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0081] APN: "IMS", PGW address: "None"

[0082] AAA:

[0083] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0084] APN: "IMS", PGW address: "None"

[0085] When establishing a PDN connection (e.g., on an IMS (IP Multimedia Subsystem) APN), the ePDG selects the SMF+PGW-C (e.g., node2.PGW-s5s8.3gppnetwork.org). The SMF+PGW-C updates its address information to the HSS / UDM along with the "ePDG Access Indication." Based on the received "ePDG Access Indication," the HSS / UDM will not update the selected SMF+PGW-C address information to the 3GPP AAA. Consequently, the 3GPP AAA maintains the old cached SMF+PGW-C information.

[0086] As a second example, the cached information in AAA and in HSS / UDM might be as follows: HSS / UDM:

[0087] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0088] APN: "IMS", PGW address: "node2.PGW-s5s8.3gppnetwork.org", epdg-access-indication=true

[0089] AAA:

[0090] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0091] APN: "IMS", PGW address: "None"

[0092] When the UE performs a handover of one of the PDN connections (e.g., IMS APN) to another 3GPP access (e.g., NG-RAN, E-UTRAN), for example, when there are multiple PDN connections established on the ePDG or even if there is no active PDN connection but the 3GPP AAA is configured to cache the user profile, the 3GPP AAA retains the old user profile. The 3GPP access reads the PGW allocation information from the HSS / UDM and selects the same node for the handover, e.g., APN: "IMS", PGW address: "node2.PGW-s5s8.3gppnetwork.org".

[0093] When the PDN connection is switched back to the EPC / ePDG again, the 3GPP AAA does not read the user profile from the HSS again because there is a local cache in the 3GPP AAA.

[0094] As a third example, during handover between 3GPP access and non-3GPP access, the cached information in AAA and HSS / UDM may be as follows:

[0095] HSS / UDM:

[0096] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0097] APN: "IMS", PGW address: "node2.PGW-s5s8.3gppnetwork.org", epdg-access-indication=true

[0098] AAA:

[0099] APN: "Internet", PGW address: "node1.PGW-s5s8.3gppnetwork.org"

[0100] APN: "IMS", PGW address: "None"

[0101] In this case, the 3GPP AAA provides the ePDG with incorrect SMF+PGW-C information (i.e., APN: "IMS", PGW address: "None"). Then, the handover from 3GPP access to non-3GPP access will fail.

[0102] In order to overcome or alleviate the above problems or other problems, embodiments of the present disclosure provide an improved information synchronization solution.

[0103] Figure 4A flow chart of a method according to an embodiment of the present disclosure is shown, which may be performed by an apparatus implemented in a data management node or communicatively coupled to a data management node. Thus, the apparatus may provide components or modules for implementing various parts of method 400, as well as components or components for implementing other processes together with other components. The data management node may be any suitable node capable of implementing data management functions. For example, Figure 1-3 As shown, the data management node can be HSS+UDM.

[0104] In block 402, a data management node may receive a first message including an identifier of the first gateway from a first gateway. The first gateway may service a session of a terminal device. The terminal device accesses a network through a second gateway.

[0105] In one embodiment, the first gateway may be, for example, Figure 1-3 The combined session management function and packet data network gateway control plane (SMF+PGW-C) entity is shown.

[0106] In one embodiment, the second gateway may be, for example, Figure 1-3 The evolved packet data gateway (ePDG) is shown.

[0107] In one embodiment, the first message may be a Nudm_UECM_Registration request as described in clause 5.2.3.2 of 3GPP TS 23.502 V16.4.0.

[0108] In one embodiment, the identifier of the first gateway may be a fully qualified domain name (FQDN) or an Internet Protocol (IP) address.

[0109] In one embodiment, the first message may be sent via the N10 interface between the SMF+PGW-C and the HSS+UDM. For example, when the ePDG is connected to the SMF+PGW-C, S6b is not used, and the UE creates and deletes a PDN connection via the ePDG connected to the SMF+PGW-C. Registration and deregistration of the PDN GW may be performed over the N10 interface instead of the S6b interface.

[0110] In one embodiment, the first message further includes a first indication that the terminal device accesses the network from the second gateway.

[0111] In one embodiment, the first message may be Nudm_UECM_Registration with optional indication of access from ePDG as described in clause 7.2.4 of 3GPP TS 23.502 V16.4.0.

[0112] At block 404, the data management node may optionally store the identification of the first gateway. For example, a data management node such as a UDM may store this information in a UDR via Nudr_DM_Update.

[0113] At block 406 , the data management node may send a second message including an identification of the first gateway to an authentication, authorization, and accounting (AAA) server.

[0114] In one embodiment, the AAA server may be, for example, Figure 1-3 The 3GPP AAA server is shown.

[0115] In one embodiment, the second message may further include a second indication for instructing the AAA server to suppress requests, such as reauthorization, to the second gateway. The second indication may be in any suitable form, such as a new value for an existing flag or a new parameter, such as "ePDG Access Indication." The AAA server may use this indication to suppress requests, such as reauthorization procedures, to the ePDG to avoid misinterpretation / mishandling in the ePDG.

[0116] In one embodiment, the second message may further include a second instruction for instructing the terminal device to access the network from the second gateway.

[0117] In one embodiment, when the SMF+PGW-C uses the N10 interface, the HSS / UDM may update the selected SMF+PGW-C address information to the 3GPP AAA server.

[0118] In one embodiment, the HSS / UDM should include an indication (new value of an existing flag and / or new parameter, such as "ePDG Access Indication") in the notification of the PGW-C allocation to the 3GPP AAA server to indicate the reason for this update to the 3GPP AAA server. The 3GPP AAA server uses this indication to suppress requests such as re-authorization procedures to the ePDG.

[0119] In one embodiment, the HSS / UDM may update the selected SMF+PGW-C address to the 3GPP AAA server and include a reason for this update.

[0120] In one embodiment, the second message is a Push-Profile-Request message.

[0121] According to various embodiments, it may enable the HSS / UDM to update the 3GPP AAA server with information about the selected SMF+PGW to ensure that the 3GPP AAA server can use the information for later handover procedures between 3GPP access and non-3GPP access.

[0122] According to various embodiments, a new indication may be introduced in the Push-Profile-Request message on Swx so that the HSS may instruct the 3GPP AAA server to suppress requests such as re-authorization to the ePDG.

[0123] Figure 5 5. A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an AAA server or communicatively coupled to an AAA server. Therefore, the device can provide components or modules for implementing various parts of the method 500, as well as components or components for implementing other processes together with other components. The AAA server can be any suitable node capable of implementing authentication, authorization, and accounting functions. For example, the AAA server can be, for example, Figure 1-3 For the sake of brevity, the description of some parts described in the above embodiments is omitted here.

[0124] At block 502, the AAA server may receive a message from a data management node that includes an identification of a first gateway serving a session of an end-point device. Figure 4 In block 406 , the data management node may send a message including the identifier of the first gateway to the AAA server, and the AAA server may then receive the message including the identifier of the first gateway.

[0125] In one embodiment, the message may be a Push-Profile-Request message.

[0126] Optionally, the AAA server may store the identification of the first gateway at block 504. For example, the AAA server may store the identification of the first gateway in its local memory.

[0127] At block 506, the AAA server may suppress requests, such as reauthorization, to the second gateway based on the message.

[0128] In one embodiment, the request may be a reauthorization request.

[0129] In one embodiment, the message also includes an indication for instructing the AAA server to suppress requests such as re-authorization to the second gateway.

[0130] In one embodiment, the message further includes an instruction for instructing the terminal device to access the network from the second gateway.

[0131] In one embodiment, the identifier of the first gateway is a fully qualified domain name (FQDN) or an Internet Protocol (IP) address.

[0132] In one embodiment, the data management node is a combined Home Subscriber Server plus Unified Data Management (HSS+UDM) entity.

[0133] In one embodiment, the first gateway is a combined Session Management Function and Packet Data Network Gateway Control Plane (SMF+PGW-C) entity.

[0134] In one embodiment, the second gateway is an evolved packet data gateway (ePDG).

[0135] Figure 6 A flowchart of a method according to another embodiment of the present disclosure is shown.

[0136] In step 601, the UE triggers a PDN connection to the EPC / ePDG.

[0137] In step 602, the ePDG may send a Diameter EAP (Extensible Authentication Protocol) request to the 3GPP AAA server through the Swm interface.

[0138] In step 603, the 3GPP AAA server may send a multimedia authentication request to the HSS / UDM through the Swx interface, and receive a multimedia authentication response from the HSS / UDM through the Swx interface.

[0139] In step 604, the 3GPP AAA server may send a server allocation request to the HSS / UDM via the Swx interface.

[0140] In step 605, the 3GPP AAA server may receive a server allocation answer (including the user profile) from the HSS / UDM via the Swx interface.

[0141] In step 606, the 3GPP AAA server may send a Diameter EAP response to the ePDG via the Swm interface.

[0142] In step 607, the ePDG may discover and select a combined SMF+PGW based on the received user profile, UE capabilities, local policies, etc.

[0143] In step 608, the ePDG may send a create session request to the selected SMF+PGW via S2b.

[0144] In step 609, the SMF+PGW may send a Nudm_UECM_Registration request to the HSS / UDM via the N10 interface. The Nudm_UECM_Registration request may include PGW information (e.g., PGW FQDN) and / or an ePDG access indication. The HSS / UDM may store the PGW information (e.g., PGW FQDN) and / or the ePDG access indication. For example, the PGW information may be stored in the user profile.

[0145] In step 610, the HSS / UDM may send a Nudm_UECM_Registration response to the SMF+PGW via the N10 interface.

[0146] In steps 601-610, according to clause 4.11.4.3.6 of 3GPP TS 23.502 V16.4.0, the UE triggers a PDN connection to the EPC / ePDG, where the selected SMF+PGW-C reports the PGW information to the HSS / UDM using the N10 interface.

[0147] At step 611 , the HSS / UDM may determine to send a notification of the PGW-C assignment to the 3GPP AAA server, along with an indication that requests such as a reauthorization procedure to the ePDG should be suppressed (eg, an ePDG Access Indication).

[0148] For example, when the SMF+PGW-C registers its address with the HSS / UDM using the N10 interface, the HSS / UDM updates the selected SMF+PGW-C address information to the 3GPP AAA server. If an ePDG Access Indication is received in the previous step, the HSS / UDM populates an indication to instruct the 3GPP AAA server to suppress requests to the ePDG, such as the reauthorization process. For example, this indication can be an ePDG Access Indication. Note that the HSS / UDM can also populate the same indication in other scenarios.

[0149] The HSS / UDM may send a Push-Profile-Request to the 3GPP AAA server at step 612. The Push-Profile-Request may include PGW information as part of the user profile and an indication such as an ePDG access indication.

[0150] In step 613 , if there is an indication such as an ePDG access indication in the received message, the 3GPP AAA server may store the PGW information locally and suppress the re-authorization request / re-authorization answer procedure to the ePDG.

[0151] Figure 7a1 shows a simplified block diagram of an apparatus 710 according to an embodiment of the present disclosure, which may be embodied in / as a data management node. Figure 7b A simplified block diagram of an apparatus 720 according to an embodiment of the present disclosure is shown, which may be embodied in / as an AAA server.

[0152] The apparatus 710 may include at least one processor 711, such as a data processor (DP), and at least one memory (MEM) 712 coupled to the processor 711. The apparatus 710 may also include a transmitter TX and a receiver RX 713 coupled to the processor 712. The memory 712 stores a program (PROG) 714. The program 714 may include instructions that, when executed on the associated processor 711, enable the apparatus 710 to operate in accordance with embodiments of the present disclosure, such as performing methods related to user plane function nodes. The combination of the at least one processor 711 and the at least one memory 712 may form a processing component 715 suitable for implementing various embodiments of the present disclosure.

[0153] The apparatus 720 includes at least one processor 721 (e.g., a DP) and at least one memory 722 coupled to the processor 721. The apparatus 720 may also include a transmitter TX and a receiver RX 723 coupled to the processor 721. The memory 722 stores a program 724. The program 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 720 to operate in accordance with embodiments of the present disclosure, such as performing methods related to control plane function nodes. The combination of the at least one processor 721 and the at least one memory 722 may form a processing component 725 suitable for implementing various embodiments of the present disclosure.

[0154] Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processors 711 and 721 , software, firmware, hardware, or a combination thereof.

[0155] Memories 712 and 722 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology such as, by way of non-limiting example, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory.

[0156] Processors 711 and 721 may be of any type suitable to the local technical environment, and may include one or more of: as non-limiting examples, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0157] In an embodiment where the apparatus is implemented as a data management node or at a data management node, the memory 721 stores instructions executable by the processor 721, whereby the data management node performs the following operations according to the reference. Figure 4 The method 400 operates as described.

[0158] In an embodiment where the apparatus is implemented as or at an AAA server, the memory 722 stores instructions executable by the processor 721 whereby the AAA server processes the data according to the reference data. Figure 5 The method 500 operates as described.

[0159] Figure 8 800 is a block diagram illustrating a data management node according to an embodiment of the present disclosure. As shown in the figure, the data management node 800 includes a receiving module 802 and a sending module 804. The receiving module 802 can be configured to receive a first message including a first gateway identifier from a first gateway. The first gateway serves a session of a terminal device. The terminal device accesses the network from a second gateway. The sending module 804 can be configured to send a second message including an identifier of the first gateway to an authentication, authorization, and accounting (AAA) server. The first message also includes a first indication that the terminal device accesses the network from the second gateway.

[0160] In one embodiment, the data management node 800 may further include a storage module 806 configured to store the identification of the first gateway.

[0161] Figure 9 is a block diagram illustrating an AAA server according to an embodiment of the present disclosure. As shown, AAA server 900 includes a receiving module 902 and a suppression module 904. Receiving module 904 may be configured to receive a message from a data management node including the identifier of a first gateway serving a session with an end-point device. Suppression module 904 may be configured to suppress requests, such as reauthorization, to a second gateway based on the message. The end-point device accesses the network through the second gateway.

[0162] In one embodiment, the AAA server 900 may further include a storage module 906 configured to store the identification of the first gateway.

[0163] The term "unit" has a conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include: (for example) electrical circuits and / or circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing respective tasks, processes, calculations, output and / or display functions, etc. (such as those described herein).

[0164] By using functional units, data management nodes and / or AAA servers may not require fixed processors or memories.The introduction of virtualization technology and network computing technology can improve the efficiency of network resource utilization and network flexibility.

[0165] According to one aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method related to the above-mentioned data management node.

[0166] According to one aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform the method related to the above-mentioned AAA server.

[0167] According to one aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed by at least one processor, the instructions cause the at least one server to perform the method related to the above-mentioned data management node.

[0168] According to one aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed by at least one processor, the instructions cause the at least one server to perform the method related to the above-mentioned AAA server.

[0169] The embodiments herein provide many advantages, the following is a non-exhaustive list of examples of the advantages. In some embodiments herein, if the PGW-C+SMF is selected from the ePDG for the UE to establish a PDN connection, and the N10 interface is used to report the PGW allocation information to the HSS / UDM, the proposed solution can ensure that the correct PGW allocation information is available in the 3GPP AAA server. Therefore, in a later handover, the 3GPP AAA server can provide the ePDG with appropriate information of the PGW. In some embodiments herein, the proposed solution can ensure that appropriate indications are provided to the 3GPP AAA server, so that it can suppress the request process to the ePDG to avoid misinterpretation / mishandling in the ePDG. The embodiments herein are not limited to the above-mentioned features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description.

[0170] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is 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 disc or an electronic storage device such as RAM (random access memory), ROM (read-only memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0171] The techniques described herein can be implemented in various ways such that a device that implements one or more functions of the corresponding devices described with the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding devices described with the embodiments, and it can 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), or a combination thereof. For firmware or software, implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0172] The exemplary embodiments of the present invention have been described above with reference to the block diagrams and flowchart illustrations of the methods and apparatus. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various components including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed on the computer or other programmable data processing device create components for implementing the functions specified in the flowchart block or blocks.

[0173] In addition, although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequence, or that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion contains several specific implementation details, these should not be interpreted as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0174] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or the scope of what may be claimed, but rather should be interpreted as descriptions of features that may be specific to a particular embodiment of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments, either individually or in any suitable subcombination. Furthermore, although the features described above may be described as working in certain combinations, or even initially claimed to be so protected, in some cases one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0175] It will be apparent to those skilled in the art that, as technology advances, the present invention can be implemented in various ways. The above embodiments are provided to illustrate, not to limit, the present disclosure, and it should be understood that, as those skilled in the art will readily appreciate, modifications and variations can be made without departing from the spirit and scope of the present disclosure. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (400) at a data management node, comprising: receiving (402) a first message including an identification of a first gateway from a first gateway, wherein the first gateway services a session of an end device and the end device accesses a network from a second gateway; and sending (406) a second message including the identification of the first gateway to an authentication, authorization and accounting (AAA) server, The first message also includes a first instruction for the terminal device to access the network from the second gateway. The second message further includes a second instruction for instructing the AAA server to suppress the request toward the second gateway. The data management node is a combined home subscriber server plus unified data management (HSS+UDM) entity. wherein the first gateway is a combined session management function plus packet data network gateway control plane (SMF+PGW-C) entity, and The second gateway is an evolved packet data gateway (ePDG).

2. The method according to claim 1, wherein The request is a reauthorization request.

3. The method according to claim 1, wherein The second message also includes a second instruction for instructing the terminal device to access the network from the second gateway.

4. The method according to claim 1, further comprising: The identification of the first gateway is stored (404).

5. The method according to claim 1, wherein The identifier of the first gateway is a fully qualified domain name (FQDN) or an Internet Protocol (IP) address.

6. The method according to claim 1, wherein The first message is a Nudm_UECM_Registration request.

7. The method according to claim 1, wherein The second message is a Push-Profile-Request message.

8. A method (500) at an authentication, authorization, and accounting (AAA) server, comprising: receiving (502) a message from a data management node including an identification of a first gateway serving a session of an end-point device; as well as suppressing (506) a request towards a second gateway based on the message, The terminal device accesses the network through the second gateway. The message further includes an instruction for instructing the AAA server to suppress the request toward the second gateway, The data management node is a combined home subscriber server plus unified data management (HSS+UDM) entity. wherein the first gateway is a combined session management function plus packet data network gateway control plane (SMF+PGW-C) entity, and The second gateway is an evolved packet data gateway (ePDG).

9. The method according to claim 8, wherein The request is a reauthorization request.

10. The method according to claim 8, wherein The message also includes an instruction for instructing the terminal device to access the network from the second gateway.

11. The method according to claim 8 or 10, wherein: The message is a Push-Profile-Request message.

12. The method according to claim 8, further comprising: The identification of the first gateway is stored (504).

13. The method according to claim 8, wherein The identifier of the first gateway is a fully qualified domain name (FQDN) or an Internet Protocol (IP) address.

14. A data management node (710), comprising: Processor (711); and A memory (712) coupled to the processor (711), the memory (713) storing instructions executable by the processor (711), whereby the data management node (710) is operable to: receiving a first message including an identification of a first gateway from a first gateway, wherein the first gateway services a session of an end device and the end device accesses a network from a second gateway; and sending a second message including the identification of the first gateway to an authentication, authorization, and accounting (AAA) server, The first message also includes a first indication that the terminal device accesses the network from the second gateway. The second message further includes a second instruction for instructing the AAA server to suppress the request toward the second gateway. The data management node is a combined home subscriber server plus unified data management (HSS+UDM) entity. wherein the first gateway is a combined session management function plus packet data network gateway control plane (SMF+PGW-C) entity, and The second gateway is an evolved packet data gateway (ePDG).

15. An authentication, authorization, and accounting (AAA) server (721), comprising: Processor (721); and a memory (722) coupled to the processor (721), the memory (722) storing instructions executable by the processor (721), whereby the AAA server (721) is operable to: receiving, from the data management node, a message including an identification of a first gateway serving a session of an end-point device; and suppressing a request towards the second gateway based on the message, Wherein, the terminal device accesses the network from the second gateway The message further includes an instruction for instructing the AAA server to suppress the request toward the second gateway, The data management node is a combined home subscriber server plus unified data management (HSS+UDM) entity. wherein the first gateway is a combined session management function plus packet data network gateway control plane (SMF+PGW-C) entity, and The second gateway is an evolved packet data gateway (ePDG).

16. A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of claim 1.

17. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method of claim 1.

Images