WO2021259510A1 - Dispositifs et procédés pour la gestion des politiques de nat dans un réseau de communication sans fil - Google Patents

Dispositifs et procédés pour la gestion des politiques de nat dans un réseau de communication sans fil Download PDF

Info

Publication number
WO2021259510A1
WO2021259510A1 PCT/EP2020/071778 EP2020071778W WO2021259510A1 WO 2021259510 A1 WO2021259510 A1 WO 2021259510A1 EP 2020071778 W EP2020071778 W EP 2020071778W WO 2021259510 A1 WO2021259510 A1 WO 2021259510A1
Authority
WO
WIPO (PCT)
Prior art keywords
nat
session
napt
enforcement action
pools
Prior art date
Application number
PCT/EP2020/071778
Other languages
English (en)
Inventor
Miguel Angel MUÑOZ DE LA TORRE ALONSO
Raul BARREDA SOTO
Veronica SANCHEZ VEGA
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2021259510A1 publication Critical patent/WO2021259510A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/255—Maintenance or indexing of mapping tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/256—NAT traversal
    • H04L61/2585—NAT traversal through application level gateway [ALG]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses

Definitions

  • Embodiments herein relate to a session management node, a gateway node and methods therein. In some aspects, they relate to handling Network Address Translation (NAT) policies in a wireless communications network.
  • NAT Network Address Translation
  • wireless devices also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipments (UE), communicate via a Local Area Network such as a WiFi network or a Radio Access Network (RAN) to one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5th Generation (5G).
  • 5G 5th Generation
  • a service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.
  • the radio network node communicates to the wireless device in DownLink (DL) and from the wireless device in UpLink (UL).
  • DL DownLink
  • UL UpLink
  • the Evolved Packet System also called a Fourth Generation (4G) network
  • EPS also called a Fourth Generation (4G) network
  • 3GPP 3rd Generation Partnership Project
  • 5G New Radio NR
  • the EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN also known as the Long Term Evolution (LTE) radio access network
  • EPC also known as System Architecture Evolution (SAE) core network.
  • SAE System Architecture Evolution
  • E- UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs used in 3rd Generation (3G) networks.
  • 3G 3rd Generation
  • the functions of a 3G RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network.
  • the RAN of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs.
  • the E-UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.
  • Multi-antenna techniques can significantly increase the data rates and reliability of a wireless communication system. The performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel.
  • MIMO Multiple-Input Multiple-Output
  • Such systems and/or related techniques are commonly referred to as MIMO.
  • 5G planning aims at higher capacity than current 4G, allowing higher number of mobile broadband users per area unit, and allowing consumption of higher or unlimited data quantities in gigabyte per month and user. This would make it feasible for a large portion of the population to stream high-definition media many hours per day with their mobile devices, when out of reach of Wi-Fi hotspots.
  • 5G research and development also aims at improved support of machine to machine communication, also known as the Internet of things, aiming at lower cost, lower battery consumption and lower latency than 4G equipment.
  • the 3GPP 5G core network comprises several Network Functions (NF), some of which are discussed here.
  • Figure 1 depicts 3GPP reference architecture for 5G and 3GPP 5GC reference architecture for policy and charging according to prior art.
  • PCF Policy Control Function
  • PCF Policy and Charging Control
  • PCEF Policy and Charging Enforcement Function
  • SMF Session Management Function
  • UPF User Plane Function
  • the SMF supports different functionality, such as e.g. session establishment, modify and release, and policy related functionalities like termination of interfaces towards the PCF, charging data collection, support of charging interfaces and control and coordination of charging data collection at the UPF.
  • the SMF receives PCC rules from the PCF and configures the UPF accordingly through a N4 reference point, e.g. Packet Flow Control Protocol (PFCP) protocol.
  • PFCP Packet Flow Control Protocol
  • the SMF controls the packet processing in the UPF by establishing, modifying or deleting PFCP Sessions and by provisioning, e.g. adding, modifying or deleting, Packet Detection Rules (PDR), Forward Acton Rule (FAR), Quality of Service Enforcement Rules (QER) and/or Usage Reporting Rules (URR) per PFCP session, whereby a PFCP session may correspond to an individual Protocol Data Unit (PDU) session or a standalone PFCP session not tied to any PDU session.
  • PDR Packet Flow Control Protocol
  • FAR Forward Acton Rule
  • QER Quality of Service Enforcement Rules
  • URR Usage Reporting Rules
  • Each PDR contains a Packet Detection Information (PDI) specifying the traffic filters or signatures against which incoming packets are matched.
  • PDI Packet Detection Information
  • Each PDR is associated to rules providing the set of instructions to apply to packets matching the PDI.
  • the rules comprise one FAR, which contains instructions related to the processing of the packets, specifically forward, duplicate, drop or buffer the packet with or without notifying the control plane (CP) function about the arrival of a DL packet.
  • the rules comprise zero, one or more QERs, which comprises instructions related to the Quality of Service (QoS) enforcement of the traffic and zero, one or more URRs, which comprises instructions related to traffic measurement and reporting.
  • QoS Quality of Service
  • the UPF supports handling of user plane traffic based on the rules received from the SMF.
  • the UPF performs packet inspection, through PDRs, and different enforcement actions, e.g. traffic steering, QoS, Charging/Reporting, through FARs, QERs, URRs.
  • NAT Network Address Translation
  • NAT is a method of remapping one Internet Protocol (IP) address space into another by modifying network address information in the IP header of packets while they are in transit across a traffic routing device.
  • IP Internet Protocol
  • NAPT Network address and port translation
  • NAT provides a translation technology which allows multiple end customers to use common and overlapping private IP address ranges internally. Any number of end customers can use the same private IP address ranges.
  • NAT translates the private IP addresses to public IP addresses, e.g. NAT44 which translates from private to public IP version 4 (IPv4) address needed to cope with IPv4 address depletion.
  • IPv4 IP version 4
  • CGNAT Carrier Grade NAT
  • AAG Application Level Gateway
  • 464XLAT allows clients on IPv6-only networks to access IPv4-only Internet services.
  • the client uses a translator to convert IPv4 packets into IPv6 packets to send, over an IPv6-only network, to a NAT64 translator.
  • the NAT64 translator translates them back into IPv4 packets to send, over an IPv4-capable network, to an IPv4-only server.
  • the Client Address Translator (CLAT) may be implemented in the client itself e.g. as special software, or in an intermediate IPv4-capable LAN.
  • the NAT64 translator, Provider Address Translator (PLAT) requires be able to reach both the server and the client, through the CLAT.
  • the use of NAT64 limits connections to a client-server model using UDP, TCP, and ICMP.
  • PLAT is a provider-side translator that implements a protocol translation. It translates N : 1 global IPv6 addresses to public IPv4 addresses, and vice versa.
  • the PLAT holds the Pref64/n prefix. All traffic towards this IPv6 prefix is routed to the PLAT.
  • the PLAT derives the destination IPv4 address from the destination IPv6 address.
  • the PLAT implements Application Layer Gateways (ALG) to allow certain protocols to traverse the CGNAT component. Examples of these protocols include: File Transfer Protocol (FTP), Session Initiation Protocol (SIP), Real Time Streaming Protocol (RTSP) and Point-to-Point Tunnelling Protocol (PPTP).
  • FTP File Transfer Protocol
  • SIP Session Initiation Protocol
  • RTSP Real Time Streaming Protocol
  • PPTP Point-to-Point Tunnelling Protocol
  • ATSSS Access Steering Switching Splitting
  • MPTCP Multi Path Transport Control Protocol
  • 3GPP Rel16 has standardized the support of MPTCP proxy in the UPF as a method for UE and UPF steering of the traffic on 3GPP or non 3GPP access.
  • the SMF in addition to the public PDU session IP address, assigns two link specific addresses, not routable over the N6 interface, to the UE to be used only for the MPTCP sub-flow in each access.
  • 3GPP has defined N4 MAR rule extensions to enable such proxy.
  • CGNAT entities are usually highly loaded and costly, handling all traffic from millions of subscribers.
  • country regulatory laws require that service providers log subscriber activity, including translated IP addresses and subscriber identities.
  • One problem with existing solutions is its complexity and lack of efficiency.
  • a problem is that current 3GPP specifications do not define support for NAT integrated in a gateway.
  • CUPS Control User Plane Separation
  • An object of embodiments herein is to improve the performance of a wireless communications network handling rules and policies related to NAT.
  • the object is achieved by a method performed by a session management node, for handling Network Address Translation, NAT, policies in a wireless communications network.
  • the session management node transmits a NAT request to a gateway node.
  • the NAT request comprises a set of NAT Internet Protocol, IP, pools for NAT purposes.
  • IP Internet Protocol
  • the NAT IP pools relate to IP addresses.
  • the session management node Upon receiving a session establishment request for a User Equipment, UE, session, the session management node obtains a NAT policy for the UE session from a policy node.
  • the NAT policy relates at least partially to the set of NAT IP pools.
  • the session management node transmits a detection rule and an instruction rule to the gateway node.
  • the detection rule is used to detect and identify an application traffic in the UE session.
  • the instruction rule instructs the gateway node to apply a NAT enforcement action for the UE session.
  • the NAT enforcement action is determined based on the obtained NAT policy.
  • the session management node obtains a report from the gateway node.
  • the report comprises an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE session.
  • the object is achieved by method performed by a gateway node for handling Network Address Translation, NAT, policies in a wireless communications network.
  • the gateway node receives a NAT request from a session management node.
  • the NAT request comprises a set of NAT Internet Protocol, IP, pools for NAT purposes.
  • IP Internet Protocol
  • the NAT IP pools relate to IP addresses.
  • the gateway node Upon establishment of a UE session, receives a detection rule and an instruction rule from the session management node.
  • the detection rule is used to detect and identify an application traffic in the UE session.
  • the instruction rule instructs the gateway node to apply a NAT enforcement action for the UE session.
  • the gateway node When receiving in the UE session, application traffic identified based on the detection rule, the gateway node applies the NAT enforcement action on the identified application traffic.
  • the gateway node provides a report to the session management node.
  • the report comprises one UE IP address selected from of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE session.
  • the object is achieved by a session management node configured to handle Network Address Translation, NAT, policies in a wireless communications network.
  • the method session management node id further configured to:
  • NAT request which NAT request is adapted to comprise a set of NAT Internet Protocol, IP, pools for NAT purposes, wherein the NAT IP pools are adapted to relate to IP addresses,
  • NAT policy for the UE session, wherein the NAT policy is adapted to at least partially relate to the set of NAT IP pools
  • a detection rule which detection rule is adapted to be used to detect and identify an application traffic in the UE session
  • an instruction rule which instruction rule is adapted to instruct the gateway node to apply a NAT enforcement action for the UE session, wherein the NAT enforcement action is adapted to be determined based on the obtained NAT policy
  • the gateway node UPF obtains a report, from the gateway node UPF, wherein the report is adapted to comprise an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE session.
  • the object is achieved by a gateway node configured to handle Network Address Translation, NAT, policies in a wireless communications network.
  • the gateway node is further configured to:
  • NAT request which NAT request is adapted to comprise a set of NAT Internet Protocol, IP, pools for NAT purposes, wherein the NAT IP pools are adapted to relate to IP addresses,
  • a detection rule which detection rule is adapted to be used to detect and identify an application traffic in the UE session
  • an instruction rule which instruction rule is adapted to instruct the gateway node to apply a NAT enforcement action for the UE session
  • the session management node provides a report, to the session management node, wherein the report is adapted to comprise one UE IP address selected from of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE session.
  • the gateway node receives a NAT request comprising a set of NAT IP pools for NAT purposes and that the gateway node receives a detection rule for detecting and identifying application traffic, and an instruction rule instructing the gateway node to apply a NAT enforcement action on the identified application traffic, an efficient mechanism for handling NAT policies is achieved, which results in a less complex network implementation.
  • Embodiments herein bring the advantage of an efficient mechanism for handling NAT policies. This is achieved by making it possible to request a gateway node to apply NAT enforcement actions on identified application traffic and avoiding deploying and integrating external service functions for handling NAT. This results in an improved performance of the wireless communications network handling policies related to NAT.
  • Figure 1 is a schematic block diagrams illustrating prior art.
  • Figure 2a is a schematic block diagram illustrating embodiments of a wireless communications network.
  • Figure 2b is a sequence diagram illustrating example embodiments of a method.
  • Figure 3 is a flowchart depicting embodiments of a method in a session management node.
  • Figure 4 is a flowchart depicting embodiments of a method in a gateway node.
  • Figures 5 a and b are sequence diagrams depicting embodiments of a method.
  • Figures 6 a and b are a schematic block diagrams illustrating embodiments of a session management node.
  • Figures 7 a and b are a schematic block diagrams illustrating embodiments of a gateway node.
  • Figure 8 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.
  • Figure 9 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.
  • FIGS. 10 to 13 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Embodiments herein relates to a wireless communications network and the handling of rules and policies for application data traffic related to Network Address Translation (NAT).
  • Example embodiments herein enables network operators to support NAT policies in the context of 4G and 5G networks supporting CUPS by defining an efficient mechanism improving the handling of NAT policies, allowing a gateway node, such as e.g. a UPF, to enforce NAT policies.
  • the gateway node according to embodiments herein applies NAT enforcement actions on application traffic in a UE session according to rules and policies.
  • some embodiments herein provide an efficient mechanism improving the handling of NAT policies since the gateway node receives the rules from a session management node, such as e.g. a SMF, instructing the gateway node of NAT enforcement actions to apply, thereby avoiding deploying and integrating external service functions for handling NAT. This results in an improved performance of the wireless communications network handling policies related to NAT.
  • a session management node such as e.g. a SMF
  • Embodiments herein may imply some extensions in different 3GPP interfaces, referred to as e.g. Nsmf, Npcf and Nudr, and to 3GPP protocols, referred to as e.g. PFCP protocol.
  • 3GPP protocols referred to as e.g. PFCP protocol.
  • FIG. 2a is a schematic overview depicting a wireless communications network 100 wherein embodiments herein may be implemented.
  • the wireless communications network 100 comprises one or more RANs and one or more CNs.
  • the wireless communications network 100 may use 5G NR but may further use a number of other different technologies, such as, Wi-Fi, , Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • LTE Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • GSM/EDGE Global System for Mobile communications/enhanced Data rate for GSM Evolution
  • WMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • Network nodes such as the network node 105 operate in the wireless communications network 100.
  • the network node 105 is a radio node and may be a transmission and reception point e.g. a radio access network node such as a base station, e.g.
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wreless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, or any other network unit capable of communicating with a UE, such as the UE 120, within a cell 115 served by the network node 105 depending e.g. on the radio access technology and terminology used.
  • the network node 105 may be referred to as a serving radio network node and communicates with a UE 120 with Downlink (DL) transmissions to the UE 120 and Uplink (UL) transmissions from the UE 120.
  • DL Downlink
  • UL Uplink
  • Wireless devices such as e.g. the UE 120 operate in the wireless communications network 100.
  • the UE 120 may e.g. be an NR device, a mobile station, a wireless terminal, an NB-loT device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and an a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g. a network node 105, one or more Access Networks (AN), e.g. a RAN, to one or more core networks (CN).
  • a base station such as e.g. a network node 105, one or more Access Networks (AN), e.g. a RAN, to one or more core networks (CN).
  • AN Access Networks
  • CN core networks
  • UE is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a car or any small base station communicating within a cell 115 provided by the network node 105.
  • D2D Device to Device
  • one or more of the following network nodes operate in the CN of the wireless communications network 100.
  • a session management node 110 such as e.g. a SMF node in 5G or a PGW-C node or TDF-C node in 4G.
  • the session management node 110 supports different functionality, such as e.g. session establishment, modify and release, and policy related functionalities such as e.g. termination of interfaces towards the policy node 150, charging data collection, support of charging interfaces and control and coordination of charging data collection at the gateway node 130.
  • the session management node 110 may control packet processing in the gateway node 130 by e.g. establishing, modifying or deleting PFCP Sessions and by provisioning, e.g. adding, modifying or deleting, PDR, FAR, QER and/or URR per PFCP session, whereby a PFCP session may correspond to an individual PDU session or a standalone PFCP session not tied to any PDU session.
  • Each PDR may comprise a PDI specifying the traffic filters or signatures against which incoming packets are matched.
  • Each PDR is associated to rules providing the set of instructions to apply to packets matching the PDI.
  • the rules e.g. comprises one FAR, which e.g. comprises instructions related to the processing of the packets, specifically address translation, forward, duplicate, drop or buffer the packet with or without notifying the control plane (CP) function about the arrival of a DL packet.
  • the rules comprise zero, one or more QERs, which comprises instructions related to the QoS enforcement of the traffic and zero, one or more URRs, which comprises instructions related to traffic measurement and reporting.
  • a gateway node 130 such as e.g. a UPF node in 5G or a PGW-U node or TDF-U node in 4G.
  • the gateway node 130 supports handling of user plane traffic.
  • the gateway node 130 performs packet inspection, e.g. through PDRs, and different enforcement actions, e.g. network address translation, traffic steering, QoS, Charging/Reporting, e.g. through FAR, QER or URR.
  • a Unified Data Repository (UDR) node 140 such as a UDR node in 5G or an HSS node in 4G.
  • the UDR node 140 supports storage and retrieval of e.g. subscription data, and policy data.
  • a policy node 150 such as e.g. a PCF node in 5G or a PCRF node in 4G.
  • the policy node 150 supports a unified policy framework to govern network behaviour.
  • the policy node 150 provides PCC rules to a PCEF such as e.g. the gateway node 130 that enforces policy and charging decisions e.g. according to provisioned PCC rules.
  • the application server 160 may e.g. belong to an Over the Top (OTT) or 3rd party.
  • OTT Over the Top
  • a mobility node 170 such as an Access and Mobility Function (AMF) node in 5G or an Mobility Management Entity (MME) node in 4G.
  • the mobility node 170 supports handling of connection and mobility management.
  • AMF Access and Mobility Function
  • MME Mobility Management Entity
  • the session management node 110, gateway node 130, UDR node 140, policy node 150 and mobility node 170 may be owned by a network operator.
  • the UE 120 may have a subscription with the network operator.
  • Methods according to embodiments herein are performed by the session management node 110, and the gateway node 130.
  • These nodes may be Distributed Nodes (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 2a, and may be used for performing or partly performing the methods.
  • DN Distributed Nodes
  • node may refer to one or more physical entities, such as devices, apparatuses, computers, servers or the like. This may mean that embodiments herein may be implemented in one physical entity. Alternatively, the embodiments herein may be implemented in a plurality of physical entities, such as an arrangement comprising said one or more physical entities, i.e. the embodiments may be implemented in a distributed manner.
  • Figure 2b shows a signaling scheme of an example scenario of embodiments herein.
  • the session management node 110 communicates with the gateway node 130 e.g. regarding NAT IP pools.
  • the session management node 110 communicates with the policy node 150 e.g.
  • the gateway node 130 Upon establishing the session, the gateway node 130 communicates with the session management node 110, e.g. in order to receive rules or policies to handle NAT policies. The UE 120 communicates with the application server 160, at which point the gateway node 130 may e.g. identify the application traffic and enforce the rules or policies.
  • the session management node 110 transmits 201 a request message to the gateway node 130.
  • the message comprises the set of NAT IP pools NAT purposes. This action relates to actions 301 and 401 described below.
  • the session management node 110 receives 202 a request message from the UE 120 requesting a session to be established. This action relates to action 302 described below.
  • the session management node 110 Upon receiving a request to establish a session for the UE 120, the session management node 110 obtains 203 a NAT policy from the policy node 150. This action is related to action 303 described below.
  • the session management node 110 may determine 204 a NAT enforcement action based on the NAT policy.
  • the NAT enforcement action is to be applied on application traffic in the UE 120 session. This action is related action 304 described below.
  • the session management node 110 transmits 205 a message to the gateway node 130.
  • the message comprises a detection rule and an instruction rule.
  • the detection rule is used to detect and identify application traffic in the UE 120 session.
  • the instruction rule instructs the gateway node 130 to apply the NAT enforcement action for the UE 120 session.
  • the message requests that the NAT enforcement action is applied to the UE 120 session.
  • the detection rule and instruction rule may e.g. be comprised in a respective Packet Detection Rule (PDR) and Forward Action Rule (FAR). This action is related to actions 305 and 402 described below.
  • PDR Packet Detection Rule
  • FAR Forward Action Rule
  • the gateway node 130 may identify 207 the application traffic on which to apply the NAT enforcement action.
  • the gateway node 130 may identify the application traffic based on the detection rule. This action is related to action 403 described below.
  • the gateway node 130 applies 208 the NAT enforcement action on the identified application traffic. This action is related to action 404 described below.
  • the gateway node 130 forwards 209 the application traffic towards the AS node 160.
  • the session management node 110 obtains 210 a report from the gateway node 130.
  • the report comprises an IP address, from the set of IP pools, that is affected by the NAT enforcement action. Affected when used herein means that the data packets related to the application traffic have been modified so that their IP header comprise the IP address from the set of IP pools for NAT purposes. This action is related to actions 306 and 405 described below.
  • Example embodiments of a method performed by the session management node 110, for handling NAT policies in a wireless communications network 100, will now be described with reference to a flowchart depicted in Figure 3.
  • an application is to be used in the UE 120.
  • Using the application results in application traffic between the UE 120 and the application server 160.
  • the UE 120 may be connected to the wireless communications network 100 via the base station 105.
  • the method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 3.
  • the session management node 110 selects a gateway node such as the gateway node 130 to handle user plane application traffic based on rules and policies related to the application traffic.
  • the session management node 110 transmits a NAT request to a gateway node 130.
  • the NAT request comprises a set of NAT IP pools for NAT purposes.
  • the NAT IP pools relate to IP addresses.
  • a NAT IP pool for NAT purposes when used herein means a set of IP addresses which may be used to replace an original UE IP address in IP header of user plane data packets.
  • the IP addresses related to the set of NAT IP pools is any one out of: public IP addresses or external IP addresses.
  • a UE session such as a UE 120 session, may comprise several data flows. Each data flow may be related to a port.
  • the NAT request further comprises a set of ports to be used by the gateway node 130 for NAPT purposes.
  • NAT may represented by NAPT.
  • the NAPT policy relates at least partially to the set of NAT IP pools and set of ports. This may allow the gateway node 130 to handle both NAT and NAPT policies.
  • a session For the UE 120 to be able to transmit application data traffic to an application server 160, a session needs to be requested to be established.
  • the session management node 110 receives a session establishment request for a UE 120 session.
  • the session management node 110 In order to handle policies for the UE 120 session, the session management node 110 needs to know what policies are provisioned for the UE 120.
  • the session management node 110 obtains a NAT policy for the UE 120 session from the policy node 150.
  • the NAT policy relates at least partially to the set of NAT IP pools. Obtaining the NAT policy allows the session management node 110 to provide the gateway node 130 with one or more rules for enforcing the NAT policy.
  • the gateway node 130 In order to enforce the NAT policy, the gateway node 130 needs instructions, e.g. rules, to follow.
  • the session management node 110 may use the obtained NAT policy to determine such rules or instructions.
  • the session management node 110 may determine any one out of: based on the NAT policy, a NAT enforcement action to be applied for the UE 120 session, or based on the NAPT policy, a NAPT enforcement action to be applied for the UE 120 session.
  • the session management node 110 may determine based on the NAT policy, a NAT enforcement action to be applied for the UE 120 session. As an alternative, the session management node 110 may determine based on the NAPT policy, a NAPT enforcement action to be applied for the UE 120 session. The instruction rule may instruct the gateway node 130 to apply the NAPT enforcement action.
  • the session management node 110 needs to provide the gateway node 130 with one or more rules comprising e.g. enforcement actions.
  • the session management node 110 transmits a detection rule and an instruction rule to the gateway node 130.
  • the detection rule is used to detect and identify an application traffic in the UE 120 session.
  • the instruction rule instructs the gateway node 130 to apply a NAT enforcement action for the UE 120 session.
  • the NAT enforcement action is determined based on the obtained NAT policy.
  • the NAT enforcement action may be comprised in the instruction rule.
  • the detection rule and instruction rule may e.g. be transmitted to the gateway node 130 in a PFCP Session Establishment Request message.
  • the detection rule and instruction rule may e.g. be comprised in a respective PDR and FAR.
  • the session management node 110 further transmits a reporting rule to the gateway node 130.
  • the reporting rule instructs the gateway node 130 to report an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the in the UE 120 session.
  • the reporting rule may further instruct the gateway node 130 to report a port out the set of port for NAPT purposes, that is affected by the NAPT enforcement action applied on the identified application traffic in the in the UE 120 session.
  • the reporting rule may be comprised in a URR.
  • the URR may e.g. be comprised in the PFCP Session Establishment Request message.
  • the detection rule is used by the gateway node 130 in order to detect and identify application traffic in the UE 120 session on which to apply the NAT enforcement action.
  • the detection rule comprises an identifying rule for any one out of: identifying application traffic in the UE 120 session on which to apply the NAT enforcement action, or identifying application traffic in the UE 120 session on which to apply the NAPT enforcement action.
  • the instruction rule may indicate any one of: an XLAT procedure and/or an ALG procedure.
  • the XLAT procedure may e.g. comprise instructing the gateway node 130 to generate an IPv6 address from an IPv4 address and an IPv6 prefix or suffix.
  • the IPv6 prefix or suffix may be indicated in the instruction rule.
  • the ALG procedure may e.g. comprise modifying other protocols, such as e.g. SIP or FTP, by replacing, e.g. in Layer 7 (L7), an original UE IP address with one UE IP address selected from of the set of NAT IP pools for NAT purposes.
  • L7 Layer 7
  • the session management node 110 e.g. for charging purposes, needs to keep track of IP addresses used in the UE 120 session.
  • the session management node 110 therefore obtains a report from the gateway node 130.
  • the report comprises an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE 120 session.
  • the report may e.g. be obtained periodically or when the UE 120 session is disconnected.
  • the UE 120 session comprises several data flows, each data flow related to a port.
  • the report further comprises a port out of the set of ports for NAPT purposes that is affected by the NAPT enforcement action applied on application traffic in the UE 120 session.
  • Example embodiments of a method performed by the gateway node 130 for handling Network Address Translation, NAT, policies in a wireless communications network 100 will now be described with reference to a flowchart depicted in Figure 4.
  • an application is to be used in the UE 120.
  • Using the application may result in application data traffic between the UE 120 and the application server 160.
  • the UE may be connected to the wireless communications network 100 via the base station 105.
  • the method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 4.
  • the session management node 110 selects a gateway node such as the gateway node 130 to handle user plane application traffic based on rules and policies related to the application traffic. Therefore, selected a gateway node such as the gateway node 130 receives a NAT request from the session management node 110.
  • the NAT request comprises the set of NAT IP pools for NAT purposes.
  • the NAT IP pools relate to IP addresses. By receiving the NAT IP pools from the session management node 110, the gateway node 130 is prepared to handle NAT policies should it be requested.
  • the IP addresses related to the set of NAT IP pools is any one out of: public IP addresses or external IP addresses.
  • each data flow of the UE 120 session may be related to a port. Therefore, in some embodiments, the NAT request further comprises a set of ports to be used by the gateway node 130 for NAPT purposes. NAT is represented by NAPT.
  • the NAPT policy relates at least partially to the set of NAT IP pools and set of ports.
  • the gateway node 130 needs to be provided with one or more rules comprising e.g. enforcement actions.
  • the gateway node 130 Upon establishment of the UE 120 session, the gateway node 130 receives a detection rule and an instruction rule from the session management node 110.
  • the detection rule is used to detect and identify an application traffic in the UE 120 session.
  • the instruction rule instructs the gateway node 130 to apply the NAT enforcement action for the UE 120 session.
  • the NAT enforcement action may be comprised in the instruction rule.
  • the detection rule and instruction rule may e.g. be received in the PFCP Session Establishment Request message. As mentioned above, the detection rule and instruction rule may e.g. be comprised in a respective PDR and FAR.
  • the gateway node 130 further receives a reporting rule from the session management node 110.
  • the reporting rule instructs the gateway node 130 to report an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the in the UE 120 session.
  • the reporting rule may further instruct the gateway node 130 to report a port out the set of port for NAPT purposes, that is affected by the NAPT enforcement action applied on the identified application traffic in the in the UE 120 session.
  • the reporting rule may be comprised in a URR.
  • the URR may e.g. be comprised in the PFCP Session Establishment Request message.
  • the detection rule is used by the gateway node 130 in order to detect and identify application traffic in the UE 120 session on which to apply the NAT enforcement action. Therefore, in some embodiments, the detection rule comprises an identifying rule for any one out of: identifying application traffic in the UE 120 session on which to apply the NAT enforcement action, or identifying application traffic in the UE 120 session on which to apply the NAPT enforcement action.
  • the instruction rule may indicate any one of: an XLAT procedure and/or an ALG procedure.
  • the XLAT procedure may e.g. comprise instructing the gateway node 130 to generate an IPv6 address from an IPv4 address and an IPv6 prefix or suffix.
  • the IPv6 prefix or suffix may be indicated in the instruction rule.
  • the ALG procedure may e.g. comprise modifying other protocols, such as e.g. SIP or FTP, by replacing, e.g. in L7, an original UE IP address with one UE IP address selected from of the set of NAT IP pools for NAT purposes.
  • the application traffic in the UE 120 session needs to be identified by the gateway node 130 which is possible by using the detection rule.
  • the gateway node 130 when receiving application traffic in the UE 120 session, the gateway node 130 identifies based on the detection rule, application traffic on which to apply any one out of: the NAT enforcement action, or a NAPT enforcement action.
  • the gateway node 130 When receiving in the UE 120 session, application traffic identified based on the detection rule, the gateway node 130 applies the NAT enforcement action on the identified application traffic.
  • the gateway node 130 has received a set of NAT IP pools for NAT purposes.
  • the NAT IP pools relates to IP addresses to be used when applying the NAT enforcement action.
  • applying the NAT enforcement action on the identified application traffic comprises any one out of:
  • the gateway node 130 applies the NAT enforcement action by selecting the UE IP address from the set of NAT IP pools.
  • the gateway node 130 replaces in the IP header the original UE IP address with the selected UE IP address, or
  • the gateway node 130 applies the NAPT enforcement action by selecting the UE IP address from the set of NAT IP pools and further selecting a port from the set of ports for NAPT purposes.
  • the gateway node 130 replaces in the IP header the original UE IP address and port with the selected UE IP address and port.
  • the session management node 110 needs to keep track of IP addresses used in the UE 120 session e.g. for charging purposes.
  • the gateway node 130 therefore provides a report, to the session management node 110.
  • the report comprises one UE IP address selected from of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE 120 session.
  • the report may e.g. be provided periodically or when the UE 120 session is disconnected.
  • the UE 120 session comprises several data flows, each data flow related to a port.
  • the report further comprises a port out of the set of ports for NAPT purposes that is affected by the NAPT enforcement action applied on application traffic in the UE 120 session.
  • Steps 1-12 of Figure 5a and Steps 13-23 of Figure 5b depict examples of detailed steps for a 5G implementation according to embodiments herein.
  • the session management node 110 is referred to as SMF 110
  • the UE 120 is referred to as UE 120
  • the gateway node 130 is referred to as UPF 130
  • the UDR node 140 is referred to as UDR 140
  • the policy node 150 is referred to as PCF 150
  • the application server 160 is referred to as AS 160
  • the mobility node 170 is referred to as AMF 170.
  • a NAT policy may be pre-provisioned in a Unified Data Repository (UDR), such as e.g. UDR 140, as subscriber policy data.
  • UDR Unified Data Repository
  • the wording “NAT policy” when used in the below example may be used interchangeably with “NAPT policy”.
  • the SMF 110 may be configured with public IP address pools and port chunks. “Port chunks” when used herein means a range of ports.
  • the wording “public” when used in the below example may be used interchangeably with “external”. According to the example, the SMF 110 allocates the NAT IP address pools, and the UPF 130 selects an IP address from the allocated pool and reports the selected IP address to the SMF.
  • the subscriber policy may include one or more rules or actions related to the NAT policy.
  • Step 501 The UPF 130 sends a message, in this example a PFCP Association Request message, to the SMF 110.
  • the message comprises an indication indicating support for NAT policies. This may allow the SMF 110 to know which UPFs that support this capability and thus may influence on UPF selection.
  • Step 502. The SMF 110 sends a PFCP Association Response message to the UPF 130 in response to the request. This may be to acknowledge the request.
  • Step 503. When UPF 130 reports the NAT capability, a new PFCP NAT procedure is triggered in the SMF 110.
  • the SMF 110 sends a NAT request, in this example a PFCP NAT Request message, to the UPF 130.
  • the message comprises the set of NAT pools related to public IP address
  • the request may further comprise a set of ports or port-chunks.
  • the set of IP address NAT pools and set of ports is to be used by the UPF 130 for NAT purposes. This step is related to actions 301 and 401 described above.
  • Step 504. The UPF 130 stores the received information and answers with a successful PFCP NAT Response message.
  • Step 505. The UE 120 triggers a PDU session establishment, by means of sending a N1 PDU session establishment request message to the AMF 170.
  • Step 506 The AMF 170 selects the SMF 110 to manage the PDU session relating to the UE 120 and sends a session establishment request, in this example a Nsmf PDU session create request message, to the SMF 110. This step is related to action 302 described above. Step 507.
  • the SMF 110 sends towards the PCF 150 a Npcf session management (SM) policy control create, e.g. referred to as
  • SM Npcf session management
  • Npcf_SMPolicyControl_Create request message to retrieve SM policies for the PDU session relating to the UE 120.
  • Step 508 The PCF 150 sends towards the UDR 140 a Nudr query, e.g. referred to as Nudr_Query, request message to retrieve the policy data for the PDU session relating to the UE 120.
  • Nudr_Query a Nudr query
  • Step 509 The UDR 140 answers the PCF 150 with a Nudr_Query response message comprising the subscriber policy data.
  • the subscriber policy data comprises a NAT policy.
  • the NAT policy may need to additionally run XLAT or ALG functionality.
  • Step 510 The PCF 150 sends to the SMF 110 a NAT policy, in this example a Npcf_SMPolicyControl_Create response message, comprising policies, e.g. the NAT policy, to be applied for the PDU session relating to the UE 120.
  • a NAT policy in this example a Npcf_SMPolicyControl_Create response message, comprising policies, e.g. the NAT policy, to be applied for the PDU session relating to the UE 120.
  • This step is related to action 303 described above.
  • Step 511 If the policies comprises the NAT policy, the SMF 110 may select the UPF 130 supporting enforcement of NAT policies. The SMF 110 may determine, based on the NAT policy, the NAT enforcement action to apply on application traffic in the UE 120 session. This step is related to action 304 described above.
  • the SMF 110 sends a detection rule and an instruction rule, in this example and PFCP Session Establishment Request message, to the UPF 130.
  • the PFCP Session Establishment Request message comprises rules for handling user plane traffic, such as e.g. PDRs, FARs, QERs and URRs.
  • the message further comprises the detecting rule and the instruction rule.
  • the instruction rule e.g. comprised in the FAR, instructs the UPF 130 to apply the NAT enforcement action on application traffic in the UE 120 session.
  • the NAT enforcement action indicates the UPF 130 to select a public IP address from the pool.
  • the NAT enforcement action may further indicate the UPF 130 to select a port from the set of ports.
  • the instruction rule may further instruct the UPF 130 to apply, based on the NAT policy, any one of a XLAT enforcement action and an ALG enforcement action.
  • the XLAT enforcement action may comprise any one of an IPv6 prefix or IPv6 suffix.
  • the XLAT enforcement action may instruct the UPF 130 to generate an IPv6 address from an IPv4 address and the IPv6 prefix of suffix.
  • the ALG enforcement action may comprise modifying other protocols, such as e.g. SIP or FTP, by replacing the private UE IP address with the selected public IP address.
  • the NAT, XLAT and ALG enforcement actions may be comprised in the FAR.
  • the detecting rule e.g. comprised in the PDR, is used to detect and identify application traffic on which to apply the NAT enforcement action.
  • the detecting rule may comprise an identifying rule for identifying application traffic on which to apply the NAT enforcement action.
  • the SMF 110 may further send a reporting rule, in this example comprised in the PFCP Session Establishing Request message to the UPF 130.
  • the reporting rule may e.g. be comprised in the URR.
  • the reporting rule may instruct the UPF 130 to report an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement
  • the reporting rule may further instruct the gateway node 130 to report a port out the set of port for NAPT purposes, that is affected by the NAPT enforcement action. This step is related to actions 305 and 402 described above.
  • the UPF 130 may store the instruction rule and detection rule, and send a PFCP Session Establishment Response message to the SMF 110.
  • Step 514 An application is started in the UE 120.
  • Step 515 Application traffic is sent to the UPF 130 from the UE 120 executing the application.
  • Step 516 The UPF 130 detects and identifies the application data traffic in the UE 120 session based on the detection rule. If there is match between the application traffic and the detection rule, the UPF 130 applies the NAT enforcement action on the identified application traffic. This step is related to actions 403 and 404 described above.
  • Step 517 The UPF 130 may forward the application traffic towards the AS 160 using the established PDU session. Step 518. Periodically the UPF 130 may be triggered to send a PFCP Session Report to the SMF 110.
  • the UPF 130 sends the report, in this example the PFCP Session Report Request message, to the SMF 110.
  • the message comprises the selected UE IP address that is affected by the NAT enforcement action.
  • the message may further comprise the selected port, out of the set port, that is affected by the NAT enforcement action.
  • the message may further comprise the original UE IP address.
  • the report may e.g. be sent periodically or when the UE 120 session is disconnected. This step is related to actions 306 and 405 described above.
  • Step 520 The SMF 110 may store the content of the PFCP Session Report Request message.
  • the SMF 110 my further send to the UPF 130 a PFCP Session Report Response message.
  • the SMF 110 may extract the selected UE IP address from the stored PFCP Session Report Request message.
  • the extracted selected UE IP address may e.g. be used for purposes such as in CDRs for charging purposes or for other reporting purposes.
  • the session management node 110 may comprise an arrangement depicted in Figures 6a and b.
  • the session management node 110 is configured to handle Network Address Translation, NAT, policies in a wireless communications network 100.
  • the session management node 110 may comprise an input and output interface 600 configured to communicate with the UE 120 and with network nodes , such as e.g. the gateway node 130, and the policy node 150, in the wireless communications network 100.
  • network nodes such as e.g. the gateway node 130, and the policy node 150, in the wireless communications network 100.
  • the session management node 110 is further configured to, e.g. by means of a transmitting unit 610 in the session management node 110, transmit to the gateway node 130, a NAT request.
  • the NAT request is adapted to comprise a set of NAT Internet Protocol, IP, pools for NAT purposes.
  • the NAT IP pools are adapted to relate to IP addresses.
  • the NAT request may further be adapted to comprise a set of ports adapted to be used by the gateway node 130 for NAPT purposes.
  • NAT may be represented by NAPT.
  • the NAPT policy may be adapted to at least partially relates to the set of NAT IP pools and set of ports.
  • the IP addresses related to the set of NAT IP pools may be adapted to be any one out of: public IP addresses or external IP addresses.
  • the session management node 130 is further configured to, e.g. by means of the transmitting unit 610 in the session management node 110, transmit to the gateway node 130, a detection rule and an instruction rule.
  • the detection rule is adapted to be used to detect and identify an application traffic in the UE session.
  • the instruction rule is adapted to instruct the gateway node 130 to apply a NAT enforcement action for the UE 120 session.
  • the NAT enforcement action is adapted to be determined based on the obtained NAT policy.
  • the detection rule may be adapted to comprise an identifying rule to any one out of: identify application traffic in the UE 120 session on which to apply the NAT enforcement action, or identify application traffic in the UE 120 session on which to apply the NAPT enforcement action.
  • the instruction rule may be adapted to indicate any one of: an XLAT procedure and an ALG procedure.
  • the session management node 130 is further configured to, e.g. by means of a receiving unit 620 in the session management node 110, receive a session establishment request for the UE 120 session.
  • the session management node 130 is further configured to, e.g. by means of an obtaining unit 630 in the session management node 110, obtain from the policy node 150, a NAT policy for the UE 120 session.
  • the NAT policy is adapted to at least partially relate to the set of NAT IP pools.
  • the session management node 130 is further configured to, e.g. by means of the obtaining unit 630 in the session management node 110, obtain a report, from the gateway node 130.
  • the report is adapted to comprise an IP address out of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE 120 session.
  • the report may further be adapted comprise a port out of the set of ports for NAPT purposes that is affected by the NAPT enforcement action applied on application traffic in the UE 120 session.
  • the session management node 130 may further be configured to, e.g. by means of a determining unit 640 in the session management node 110, determine any one out of: based on the NAT policy, a NAT enforcement action adapted to be applied for the UE 120 session, or based on the NAPT policy, a NAPT enforcement action adapted to be applied for the UE 120 session.
  • the instruction rule may be adapted to instructs the gateway node 130 to apply the NAPT enforcement action.
  • the embodiments herein may be implemented through a respective processor or one or more processors, such as a processor 650 of a processing circuitry in the session management node 110 depicted in Figure 7a, together with respective computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the session management node 110.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the session management node 110.
  • the session management node 110 may further comprise a memory 660 comprising one or more memory units.
  • the memory 660 comprises instructions executable by the processor 650 in the session management node 110.
  • the memory 660 is arranged to be used to store e.g. NAT policies, rules, NAT enforcement actions, NAT IP pools, ports and applications to perform the methods herein when being executed in the session management node 110.
  • a respective computer program 670 comprises instructions, which when executed by the respective at least one processor 650, cause the at least one processor 650 of the session management node 110 to perform the actions above.
  • a respective carrier 680 comprises the respective computer program 670, wherein the carrier 680 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the units in the session management node 110 mentioned above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the session management node 110 that when executed by the respective one or more processors such as the processors described above.
  • processors as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC Application-Specific Integrated Circuitry
  • SoC system-on-a-chip
  • the gateway node 130 may comprise an arrangement depicted in Figures 7a and b.
  • the gateway node 130 is configured to handle NAT in a wireless communications network 100.
  • the gateway node 130 may comprise an input and output interface 700 configured to communicate with the UE 120 and network nodes such as e.g. the session management node 110 and the application server 160 in the wireless communications network 100.
  • the gateway node 130 is further configured to, e.g. by means of a receiving unit 710 in the gateway node 130, receive from the session management node 110, a NAT request.
  • the NAT request is adapted to comprise a set of NAT IP pools for NAT purposes.
  • the NAT IP pools are adapted to relate to IP addresses.
  • the NAT request may further be adapted to comprise a set of ports adapted to be used by the gateway node 130 for NAPT purposes.
  • NAT may be adapted to be represented by NAPT.
  • the NAPT policy may be adapted to at least partially relates to the set of NAT IP pools and set of ports.
  • the IP addresses related to the set of NAT IP pools may be adapted to be any one out of: public IP addresses or external IP addresses.
  • the gateway node 130 is further configured to, e.g. by means of the receiving unit 710 in the gateway node 130, upon establishment of a UE 120 session, receive from the session management node 110, a detection rule and an instruction rule.
  • the detection rule is adapted to be used to detect and identify an application traffic in the UE session.
  • the instruction rule is adapted to instruct the gateway node 130 to apply a NAT enforcement action for the UE 120 session.
  • the instruction rule may be adapted to indicate any one of: an XLAT procedure and an ALG procedure.
  • the gateway node 130 may further be configured to, e.g. by means of an identifying unit 720 in the gateway node 130, when receiving application traffic in the UE 120 session, identify based on the detection rule, application traffic on which to apply any one out of: the NAT enforcement action, or a NAPT enforcement action.
  • the gateway node 130 is further configured to, e.g. by means of an applying unit 730 in the gateway node 130, when receiving in the UE 120 session application traffic identified based on the detection rule, apply the NAT enforcement action on the identified application traffic.
  • the gateway node 130 may further be configured to, e.g. by means of the applying unit 730 in the gateway node 130, apply the NAT enforcement action on the identified application traffic by any one out of: apply the NAT enforcement action by selecting the UE IP address from the set of NAT IP pools, and replacing in the IP header the original UE IP address with the selected UE IP address, or apply the NAPT enforcement action by selecting the UE IP address from the set of NAT IP pools and further selecting a port from the set of ports for NAPT purposes, and replacing in the IP header the original UE IP address and port with the selected UE IP address and port.
  • the gateway node 130 is further configured to, e.g. by means of a providing unit 740 in the gateway node 130, provide a report to the session management node 110.
  • the report is adapted to comprise one UE IP address selected from of the set of NAT IP pools for NAT purposes, that is affected by the NAT enforcement action applied on the identified application traffic in the UE (120) session.
  • the report may further be adapted to comprise a port out of the set of ports for NAPT purposes that is affected by the NAPT enforcement action applied on application traffic in the UE (120) session.
  • the embodiments herein may be implemented through a respective processor or one or more processors, such as a processor 750 of a processing circuitry in the gateway node 130 depicted in Figure 8a, together with respective computer program code for performing the functions and actions of the embodiments herein.
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the gateway node 130.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the gateway node 130.
  • the user UE 120 may further comprise a memory 760 comprising one or more memory units.
  • the memory 760 comprises instructions executable by the processor 750 in the gateway node 130.
  • the memory 760 is arranged to be used to store e.g. NAT policies, rules, NAT enforcement actions, NAT IP pools, ports and applications to perform the methods herein when being executed in the gateway node 130.
  • a respective computer program 770 comprises instructions, which when executed by the respective at least one processor 750, cause the at least one processor 750 of gateway node 130 to perform the actions above.
  • a respective carrier 780 comprises the respective computer program 770, wherein the carrier 780 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
  • the units in the gateway node 130 mentioned above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the gateway node 130, that when executed by the respective one or more processors such as the processors described above.
  • processors as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a- chip (SoC).
  • ASIC Application-Specific Integrated Circuitry
  • SoC system-on-a- chip
  • a communication system includes a telecommunication network 3210 such as the wireless communications network 100, e.g. a NR network, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as the network node 105, access nodes, AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) e.g. the UE 120 such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 e.g. the wireless device 122 such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 8 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications.
  • a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 9) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • connection 3360 may be direct or it may pass through a core network (not shown in Figure 9) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to.
  • Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 9 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 8, respectively.
  • the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 8.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, power consumption and thereby provide benefits such as user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311 , 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • FIG 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figures 32 and 33.
  • a host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figures 32 and 33.
  • a host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIG 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figures 32 and 33.
  • a host computer e.g., a AP STA
  • a UE e.g., a Non-AP STA
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third subaction 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figures 32 and 33.
  • a first action 3710 of the method in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé exécuté par un nœud de passerelle pour gérer les politiques de traduction d'adresse de réseau (NAT) dans un réseau de communication sans fil est fourni. Le nœud de passerelle reçoit (401) une demande de NAT de la part d'un nœud de gestion de session. La demande de NAT comprend un ensemble de groupes de protocole Internet (IP) NAT à des fins de NAT. Les groupes d'IP NAT se rapportent à des adresses IP. Lors de l'établissement d'une session d'équipement d'utilisateur (UE), le nœud de passerelle reçoit (402) une règle de détection et une règle d'instruction de la part du nœud de gestion de session. La règle de détection est utilisée pour détecter et identifier un trafic d'application dans la session d'UE. La règle d'instruction ordonne au nœud de passerelle d'appliquer une action d'exécution de la NAT pour la session d'UE. Lors de la réception, dans la session d'UE, du trafic d'application identifié sur la base de la règle de détection, la passerelle applique (404) l'action d'exécution de la NAT sur le trafic d'application identifié. Le nœud de passerelle fournit (405) un rapport au nœud de gestion de session. Le rapport comprend une adresse IP d'UE sélectionnée parmi l'ensemble de groupes d'IP NAT à des fins de NAT, qui est affecté par l'action d'exécution de la NAT appliquée au trafic d'application identifié dans la session d'UE.
PCT/EP2020/071778 2020-06-24 2020-08-03 Dispositifs et procédés pour la gestion des politiques de nat dans un réseau de communication sans fil WO2021259510A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP20382556 2020-06-24
EP20382556.7 2020-06-24

Publications (1)

Publication Number Publication Date
WO2021259510A1 true WO2021259510A1 (fr) 2021-12-30

Family

ID=71575334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/071778 WO2021259510A1 (fr) 2020-06-24 2020-08-03 Dispositifs et procédés pour la gestion des politiques de nat dans un réseau de communication sans fil

Country Status (1)

Country Link
WO (1) WO2021259510A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499409A (zh) * 2022-09-29 2022-12-20 阿里巴巴（中国）有限公司 Nat网关、服务器和网络系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013004558A1 (fr) * 2011-07-01 2013-01-10 Telefonica, S.A. Procédé et système pour configurer des règles de politique de traduction de port et d'adresse réseau dans des dispositifs napt
EP2665335A1 (fr) * 2012-05-14 2013-11-20 Juniper Networks, Inc. Traduction d'adresse de réseau en ligne dans un routeur de passerelles mobiles

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013004558A1 (fr) * 2011-07-01 2013-01-10 Telefonica, S.A. Procédé et système pour configurer des règles de politique de traduction de port et d'adresse réseau dans des dispositifs napt
EP2665335A1 (fr) * 2012-05-14 2013-11-20 Juniper Networks, Inc. Traduction d'adresse de réseau en ligne dans un routeur de passerelles mobiles

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Discussion on support of NAT in 5GS", vol. SA WG2, no. Reno, NV, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), XP051821819, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_136_Reno/Docs/S2-1911742.zip S2-1911742 DP NAT rev1.doc> [retrieved on 20191108] *
T-MOBILE USA INC: "IP Index for IP Address Allocation based on PCF", vol. SA WG2, no. Dubrovnik, Croatia; 20170213 - 20170217, 13 February 2017 (2017-02-13), XP051217067, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA2/Docs/> [retrieved on 20170213] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499409A (zh) * 2022-09-29 2022-12-20 阿里巴巴（中国）有限公司 Nat网关、服务器和网络系统

Similar Documents

Publication Publication Date Title
US20220386232A1 (en) Method for connecting a user terminal to a network slice
US11026165B2 (en) Radio network node, network node, database, configuration control node, and methods performed thereby
US10581747B2 (en) System and method for low-overhead interoperability between 4G and 5G networks
US20160330077A1 (en) WiFi VIRTUAL NETWORK SOLUTION
US11696182B2 (en) Core network node, user equipment and methods in a packet communications network
US20220377043A1 (en) Enabling nat for user plane traffic
EP3895470B1 (fr) Noeud de politique, noeud de plan utilisateur, noeud de plan de commande et procédés associés pour gérer la qualité de service dans un réseau de communication sans fil
WO2020164747A1 (fr) Nœud amf, nœud nssf, nœud smf cible et procédés exécutés dans un réseau de communication
WO2021063657A1 (fr) Fourniture d&#39;informations de fonction de réseau à un service fourni pour permettre au fournisseur de service de trouver un nœud alternatif afin de transmettre des informations demandées
WO2018188728A1 (fr) Transfert intercellulaire sans implication ou implication limitée de mme
US20230042754A1 (en) Gateway node, user equipment and methods therein for handling rules and policies in a wireless communications network
US11974174B2 (en) First service communication proxy node, second communication proxy node and methods in a wireless communication network
WO2021259510A1 (fr) Dispositifs et procédés pour la gestion des politiques de nat dans un réseau de communication sans fil
US20240008103A1 (en) First ims node, second server, subscriber server and methods in a communications network
WO2022266993A1 (fr) Procédés de gestion d&#39;un service pour un dispositif de communication et nœuds de réseau mettant en œuvre le procédé dans un réseau de communication
EP3977761B1 (fr) Noeud de données d&#39;abonné, noeud de desserte, noeud à fonction d&#39;exposition et procédés dans un réseau de communication
WO2023191690A1 (fr) Nœuds de réseau et procédés destinés à des politiques d&#39;orientation de trafic
WO2023134885A1 (fr) Premier nœud ims, second nœud ims, nœud de réseau et procédés dans un réseau de communication
WO2024041762A1 (fr) Noeuds de réseau et procédés dans un réseau de communication
WO2022124955A1 (fr) Premier nœud de réseau et procédé dans un réseau de communications
WO2023068974A1 (fr) Nœud de politique, dispositif radio et procédés d&#39;un réseau de communications
WO2024035303A1 (fr) Coordination entre nœuds pour rapport d&#39;expérience de qualité visible de réseau d&#39;accès radio en double connectivité

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20747424

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20747424

Country of ref document: EP

Kind code of ref document: A1