WO2019140385A1 - Procédé et architectures permettant de gérer des sessions de sécurité de couche de transport entre des points de protocole de bord - Google Patents

Procédé et architectures permettant de gérer des sessions de sécurité de couche de transport entre des points de protocole de bord Download PDF

Info

Publication number
WO2019140385A1
WO2019140385A1 PCT/US2019/013489 US2019013489W WO2019140385A1 WO 2019140385 A1 WO2019140385 A1 WO 2019140385A1 US 2019013489 W US2019013489 W US 2019013489W WO 2019140385 A1 WO2019140385 A1 WO 2019140385A1
Authority
WO
WIPO (PCT)
Prior art keywords
etp
fqdn
flow
tls
https
Prior art date
Application number
PCT/US2019/013489
Other languages
English (en)
Inventor
Scott C. Hergenhan
Dirk Trossen
Sebastian Robitzsch
Original Assignee
Idac Holdings, Inc.
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 Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2019140385A1 publication Critical patent/WO2019140385A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/16—Implementing security features at a particular protocol layer
    • H04L63/166—Implementing security features at a particular protocol layer at the transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0464—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H04L63/306—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information intercepting packet switched data communications, e.g. Web, Internet or IMS communications

Definitions

  • ICN Information-centric networking
  • protocol stack implementations for such dual-stack WTRUs may be outlined where IP applications being executed on those WTRUs can remain unchanged.
  • the transition to ICN at the network level shows many benefits, such as increased efficiency through the usage of in-network caches and the general spatial/temporal decoupling of sender/receiver, the utilization of software-defined networking (SDN) upgrades for better flow management, and the like.
  • SDN software-defined networking
  • Described herein is a method and architecture for routing transport layer security (TLS) sessions over a transport network.
  • the method and architecture uses a first Edge Termination Point (ETP) to receive an IP application flow, determine a requested fully qualified domain name (FQDN) associated with the IP flow, and determine whether the IP flow is a transport layer security (TLS) flow.
  • the FQDN may be identified based on a HTTP request or a TLS client hello message.
  • the method and architecture further determine whether the ETP has a hypertext transfer protocol (FITTPS) certificate corresponding to the FQDN.
  • FITTPS hypertext transfer protocol
  • the ETP In response to a determination that the ETP has an HTTPS certificate, the ETP terminates the TLS session, extracts an HTTP stream using decryption, and forwarding the HTTP stream to a second ETP to establish a new TLS session with a server. In response to a determination that the ETP does not have an HTTPS certificate, the ETP maintains a TLS layer and routes an encrypted HTTP stream to the second ETP based on the FQDN to establish an end-to-end (E2E) TLS session.
  • the ETP may be found in a network attachment point (NAP) or within a convergence layer of a dual-stack terminal.
  • the ETP may also be found in a cellular Node B or a Wireless Local Area Network (WLAN) Access Point (AP).
  • NAP network attachment point
  • WLAN Wireless Local Area Network
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment
  • FIG. 2 shows an example architecture for a system of ETPs connected via an SDN-based L2 network
  • FIG. 3 demonstrates both TLS endpoint and TLS proxy modes of operation as implemented in the example architecture of FIG. 2.
  • FIG. 4 is a flowchart describing the handling of incoming TCP connections at the ETP; and
  • FIG. 5 shows the resulting message sequence chart for the TLS endpoint operation.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT-UW-DFT-S-OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 1 12, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 1 14b.
  • Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 1 10, and/or the other networks 112.
  • the base stations 1 14a, 1 14b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like.
  • the base station 1 14a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 1 14a may be divided into three sectors.
  • the base station 1 14a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 1 14a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 1 16 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 1 14a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 1 16 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 1 16 using NR.
  • a radio technology such as NR Radio Access
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 1 14b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.1 1 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 1 14b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 1 14b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 1 14b may have a direct connection to the Internet 1 10.
  • the base station 1 14b may not be required to access the Internet 1 10 via the CN 106.
  • the RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106 may provide call control, billing services, mobile location- based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high- level security functions, such as user authentication.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 1 12.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 1 10 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 1 18 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 1 18 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 1 14a) over the air interface 1 16.
  • a base station e.g., the base station 1 14a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.1 1 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), readonly memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 1 18 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 1 16 from a base station (e.g., base stations 1 14a, 1 14b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors.
  • the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate selfinterference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 1 10
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 1 12 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.1 1 e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an“ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • V HT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.1 1 af and 802.1 1 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.1 1 ah relative to those used in 802.1 1 h, and 802.1 1 ac.
  • 802.1 1 ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.1 1 h, 802.1 1 ac, 802.1 1 af, and 802.1 1 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.1 1 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 1 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultrareliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like.
  • URLLC ultrareliable low latency
  • eMBB enhanced massive mobile broadband
  • the AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N1 1 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
  • a PDU session type may be IP- based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • U.S.Patent Application No. 15/518,688 describe a method for providing IP-level services over an ICN network, mapping IP packets into appropriate ICN packets published towards appropriate ICN names.
  • U.S. Patent Application No. 15/546,719 present a specific mapping on ICN and allow, among other things, to deliver a single HTTP-level response to more than one requestor in the case of quasi-synchronous requests arriving at the server side.
  • the teachings of U.S. Patent Application No. 62/537,947 place the teachings being realized in U.S. Patent Application Nos.
  • Service Function Chaining i.e., functions being realized over an overlay transport network based on mechanisms developed in Internet Engineering Task Force (IETF) Service Function Chaining (SFC) working group (WG) or over a Bit Indexed Explicit Replication (BIER) overlay network.
  • IETF Internet Engineering Task Force
  • SFC Service Function Chaining
  • WG working group
  • BIER Bit Indexed Explicit Replication
  • the teachings disclosed herein may be implemented in so-called Edge Termination Points (ETP), which terminate one or more IP-level relationships and translate the latter into relationships between said ETPs.
  • ETP Edge Termination Points
  • the communication between two ETPs is realized through a flow-based forwarding where suitable ETP node identification is used to establish such long-term flow relationship between two or more ETPs.
  • a network may use Ethernet-based Software- defined Networking (SDN) technology and forwarding rules.
  • the transport between the ETPs may be IP-based, and thereby the teachings disclosed herein may be an overlay.
  • BIER and SFC may work within the overlay network to provide another suitable communication platform between ETPs.
  • FIG. 2 shows an example architecture for a system of ETPs connected via an SDN-based L2 network.
  • the dotted lines show the local IP path, while the solid lines outline the L2 (in this example) flow throughout the network.
  • an ETP 220 described in any of the above embodiments may communicate with one or more communication elements 230, 231 , 232, 233, or 234 (e.g., L2 switches, in the network between ETPs) while it communicates through a suitable IP-level interface to an IP application 210.
  • the ETP may be realized in: a network attachment point (NAP) akin to those utilized in U.S. Patent Application Nos.
  • NAP network attachment point
  • the architecture may also include an ETP 221 that communicates over an IP-level interface to an IP application 21 1 , providing an egress for traffic flowing from the ETP 220 over the L2 network.
  • special handling is provided to some TCP flows.
  • Some examples of special handling that may be required are any one or a combination of the following: sending the flow to a destination different from the one selected by the client (for sending the information to a so- called alternative service endpoint or service surrogate); and using new protocols to route the flow differently over L2 networks.
  • the end-to-end (E2E) TCP connection on these flows at the ETPs 220 and 221 of FIG. 2 is broken.
  • Such breaking of the E2E TCP connection is necessary since otherwise the content of a TCP-based session would be opaque to the underlying ICN network, (i.e., only IP address and port information would be visible).
  • all TCP traffic would need to be sent via IP methods as described in U.S. Patent Application No. 15/518,688 since the methods in U.S. Patent Application No. 15/546,719 (and for dual-stack UEs, the methods described in U.S. Patent Application No. 62/537,947) would require visibility of the payload.
  • the incoming traffic is interpreted purely as an incoming IP packet from the WTRU (or server) with the ETP then publishing the appropriate ICN message to the L2 (ICN) network.
  • the decision to break the E2E TCP connection is made on the first packet, before the TCP handshake occurs.
  • the only information available at this point is the IP 5-tuple (destination address & port, source address and port, and protocol).
  • IP 5-tuple destination address & port, source address and port, and protocol.
  • it is problematic to identify traffic flows based solely on the 5-tuple For example, some web services will use alternative ports and an opportunity to provide better service to those flows will be missed.
  • some handling may only be applicable to specific service providers (i.e., FQDN’s).
  • an FQDN may resolve to multiple IP addresses, and the list may change.
  • a reverse DNS query (or multiple forward DNS queries) is needed at the beginning of each flow.
  • CDN content delivery network
  • multiple FQDN’s may resolve to the same IP address, making the reverse mapping, and therefore correct flow FQDN identification, impossible. This is especially true without control of how a client will resolve an FQDN to an IP address and/or which address it will use.
  • all traffic is directed within the client-facing ETP 220 in FIG. 2, the ETP 220 therefore effectively acts as a TCP proxy. Now, the 5-tuple may be examined and a second TCP connection to the original destination may be created. Alternatively, a different destination may be chosen for the second TCP connection, due to proximity, load balancing, or any number of factors.
  • the ETP 220 may fall back to routing based solely on the tuple.
  • This mode of operation may be called‘opaque mode’ since it directly applies the teachings of U.S. Patent Application No. 15/546,719 on the fully encrypted content.
  • the HTTP-level payload may be retrieved from the incoming TLS connection at the ETP in order to determine the CID and rCID, according to the teachings of U.S. Patent Application No. 15/546,719, which in turn can be used to publish the appropriate message to the L2 (i.e., the ICN) network.
  • L2 i.e., the ICN
  • the ETP acts as a TLS endpoint, terminating the TLS session and establishing a new TLS session with the server.
  • the ETP leaves the TLS layer intact and routes the HTTP stream, instead acting as a TLS Proxy.
  • FIG. 3 depicts both modes of operation as implemented in the example architecture of FIG. 2.
  • a client-facing ETP 320 may receive an HTTP request from IP application 310.
  • IP application 310 For this, once the requested FQDN is extracted following the aforementioned TCP-level termination, a determination may be made regarding whether the FQDN to which the request is sent (in FIG. 2., for example,“foo.com”) is one for which there is a (server) certificate/key locally at the ETP. If the certificate is available at the ETP, the TLS session may be terminated and the HTTP stream may be extracted through decryption by using the certificate and available credentials. After this, the teachings of U.S. Patent Application Nos.
  • 15/518,688, 15/546,719, and 62/537,947 may be applied for advanced routing, (i.e., calculate the appropriate CID and rCID (through hashing of appropriate HTTP header information) as well as determining the so-called proxy rule ID (PRID) for publication of an ICN message to the L2 (ICN) network).
  • PID proxy rule ID
  • the transfer of messages from incoming to outgoing ETP 321 (and back) may be separately encrypted (with credentials associated with the transport network provider, not the content provider) although such encryption is orthogonal to the original TLS encryption.
  • a second TLS connection may be created, creating the perception of an E2E TLS connection from the ETP 320 to the server upon which IP application 31 1 is running. For any return traffic, both end-to-ETP connections may be used.
  • Decryption at the incoming and outgoing ETPs 320 and 321 may be necessary in this mode but the teachings of U.S. Patent Application Nos. 15/518,688, 15/546,719, and 62/537,947 may be applied to the decrypted data. Furthermore, the decryption can also serve to meet legal interception requirements, recording information about service endpoints and header information from the decrypted HTTP information of the incoming TLS message. When switching service endpoints at the server side from one outgoing ETP to another, the TLS connection establishment may need to be part of the initial connection from the (now new) ETP to the (now new) service endpoint.
  • a client-facing ETP 322 may receive an HTTP request from IP application 312 (for example, towards the domain name“something.com”).
  • IP application 312 for example, towards the domain name“something.com”.
  • the certificate/key for the requested FQDN is not available at the incoming ETP 322.
  • the TLS layer may remain intact and the encrypted HTTP data may be routed based on the FQDN and tuple to a server, for example, upon which IP application 313 is running.
  • This may be referred to as a TLS proxy mode where the TLS connection (including its session keys and other cryptographic information) is preserved from end-to-end.
  • the request would be sent to the most appropriate service endpoint, not necessarily being located at the DNS-provided IP address.
  • the TLS proxy realization may still apply (optimal) name-based routing, while the opaque TCP proxy option merely routes on the IP address.
  • a minimum of recording the details of the service endpoint information i.e., the FQDN
  • FIG. 4 is a diagram showing the handling of incoming TCP connections at the client-facing ETP.
  • the incoming TCP connections at the ETP are handled according to the teachings of U.S. Patent Application Nos. 15/518,688, 15/546,719, and 62/537,947.
  • the ETP may determine whether the traffic received is a TLS or HTTP type at step 402. In the event the type of traffic cannot be ascertained, the ETP may encapsulate and route the stream via an ICN based on the IP 5-tuple at step 403.
  • the ETP may, for example, route the traffic via an ICN based on the FQDN and URL in accordance with U.S. Patent Application Nos. 15/546,719 and 62/537,947, shown at step 405.
  • the ETP may determine whether a certificate exists at the ETP for the requested FQDN. If not, at step 407, the ETP may act as a TLS proxy and apply the methods of U.S. Patent Application Nos. 15/546,719, and 62/537,947 while maintaining encryption of the routed content. If a valid certificate does exist at the ETP, at step 408, the ETP may instead act as a TLS endpoint, first decrypting the stream to extract HTTP information and then applying the advanced routing methods of U.S. Patent Application Nos. 15/546,719, and 62/537,947.
  • FIG. 5 shows an example message sequence chart for the TLS endpoint operation described above, (i.e., the operation which yields the full advantages of applying the teachings of U.S. Patent Application Nos. 15/518,688, 15/546,719, and 62/537,947.
  • IP Application A and ETP A perform a TLS handshake.
  • ETP A receives an HTTP request from IP application A. For purposes of this embodiment, it is assumed at this point that ETP A has terminated the TCP connection, extracted the requested FQDN and determined that a valid server certificate exists for the requested FQDN.
  • ETP A terminates the TLS connection and decrypts the HTTP stream.
  • ETP A applies the teachings of U.S. Patent Application Nos. 15/518,688, 15/546,719, and/or 62/537,947 for advanced routing, publishing an ICN message to the L2 network, to which the server-facing ETP C subscribes and receives the published content.
  • ETP C and IP application C perform a TLS handshake, establishing a second TLS connection.
  • encryption of the HTTPs request derived from the L2 network is performed, and the request is forwarded to the IP application corresponding to the FQDN originally derived from the HTTP stream.
  • the server-facing ETP may receive the same HTTP request from another client-facing ETP B.
  • IP application B and ETP B may perform substantially the same procedures performed by IP application A and ETP A in steps 501 through 504.
  • the server-facing ETP C has already subscribed for the content published previously by ETP A, and likewise receives ETP B’s ICN message as a subscriber.
  • IP application C sends an HTTP response to server-facing ETP C.
  • ETP C may decrypt the HTTP response and apply methods for advanced routing according to U.S. Patent Application Nos. 15/518,688, 15/546,719, and/or 62/537,947, providing multicast delivery of the HTTP response to ETPs A and B.
  • ETPs A and B perform encryption and deliver the HTTP response respectively to IP applications A and B.
  • WTRU Wireless Fidelity
  • UE User Equipment
  • terminal terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, un procédé et une architecture utilisent un premier point de terminaison de bord (ETP) pour recevoir un flux d'application IP, détermine un nom de domaine complètement qualifié demandé (FQDN) associé au flux IP, et détermine si le flux IP est un flux de sécurité de couche de transport (TLS). Le procédé et l'architecture déterminent en outre (406) si l'ETP a un certificat de protocole de transfert hypertexte (HTTPS) correspondant au FQDN. En réponse à une détermination selon laquelle l'ETP possède un certificat HTTPS, l'ETP termine la session TLS, extraire un flux HTTP à l'aide du déchiffrement, et acheminer le flux HTTP vers un second ETP afin d'établir une nouvelle session TLS avec un serveur (408). En réponse à une détermination selon laquelle L'ETP n'a pas de certificat HTTPS, l'ETP maintient une couche TLS et achemine un flux HTTP chiffré vers le second ETP sur la base du FQDN afin d'établir une session TLS de bout en bout (407).
PCT/US2019/013489 2018-01-12 2019-01-14 Procédé et architectures permettant de gérer des sessions de sécurité de couche de transport entre des points de protocole de bord WO2019140385A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862616535P 2018-01-12 2018-01-12
US62/616,535 2018-01-12

Publications (1)

Publication Number Publication Date
WO2019140385A1 true WO2019140385A1 (fr) 2019-07-18

Family

ID=65276288

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/013489 WO2019140385A1 (fr) 2018-01-12 2019-01-14 Procédé et architectures permettant de gérer des sessions de sécurité de couche de transport entre des points de protocole de bord

Country Status (1)

Country Link
WO (1) WO2019140385A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120209942A1 (en) * 2008-10-28 2012-08-16 Cotendo, Inc. System combining a cdn reverse proxy and an edge forward proxy with secure connections
US20170237660A1 (en) * 2014-10-14 2017-08-17 Idac Holdings, Inc. Anchoring ip devices in icn networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120209942A1 (en) * 2008-10-28 2012-08-16 Cotendo, Inc. System combining a cdn reverse proxy and an edge forward proxy with secure connections
US20170237660A1 (en) * 2014-10-14 2017-08-17 Idac Holdings, Inc. Anchoring ip devices in icn networks

Similar Documents

Publication Publication Date Title
US11985062B2 (en) Methods and apparatuses for enabling multi-host multipath secure transport with QUIC
WO2019036494A1 (fr) Terminal demandant des capacités de tranche de réseau à partir d'un réseau d'accès non 3gpp
US20210266254A1 (en) Device to device forwarding
US20230164641A1 (en) Extended 5g local area network interworking with a home network and change of access network for 5g lan connected devices
EP3959858A1 (fr) Protocole d'attribution d'adresse de commande d'accès au support (mac) de multidiffusion et de monodiffusion (mumaap)
KR20210127142A (ko) Pc5 인터페이스를 통한 v2x 유니캐스트 통신 활성화 절차
US20210211510A1 (en) Pinning service function chains to context-specific service instances
EP4104477A1 (fr) Support de sécurité et de confidentialité de communications sans fil directes
US20200162270A1 (en) Methods and apparatus for secure content delegation via surrogate servers
WO2023158781A1 (fr) Activation d'une strate de non-accès en tant que service
US11736905B2 (en) Methods and apparatus for Layer-2 forwarding of multicast packets
EP4320896A1 (fr) Authentification de bout en bout par l'intermédiaire d'un relais de wtru à wtru
US11765255B2 (en) Transport protocol for communication between edge termination points
EP4176577A1 (fr) Procédés et dispositifs de gestion de domaines virtuels
EP4055861A1 (fr) Découverte à base de service prose 5g
WO2019140385A1 (fr) Procédé et architectures permettant de gérer des sessions de sécurité de couche de transport entre des points de protocole de bord
US20240114014A1 (en) Methods and apparatuses for handling end-to-end encryption
WO2023215575A1 (fr) Activation de mandataires de service xr
WO2024044186A1 (fr) Autorisation d'unité de transmission/réception sans fil en itinérance pour des applications périphériques
WO2024112908A1 (fr) Services de relais centrés sur l'utilisateur
WO2022125855A1 (fr) Procédés, architectures, appareils et systèmes pour la résolution de fqdn et la communication
WO2024168262A1 (fr) Contrôle d'accès d'une wtru à un relais de réseau relatif à un service ai/ml
WO2024015403A1 (fr) Procédés d'authentification pour dispositifs activés par sba
WO2023219828A1 (fr) Commutation d'un service d'une wtru à un pin et d'un pin à une wtru

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: 19703003

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: 19703003

Country of ref document: EP

Kind code of ref document: A1