WO2020168236A1 - Session pdu multi-accès - Google Patents

Session pdu multi-accès Download PDF

Info

Publication number
WO2020168236A1
WO2020168236A1 PCT/US2020/018355 US2020018355W WO2020168236A1 WO 2020168236 A1 WO2020168236 A1 WO 2020168236A1 US 2020018355 W US2020018355 W US 2020018355W WO 2020168236 A1 WO2020168236 A1 WO 2020168236A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
wtru
service request
3gpp access
3gpp
Prior art date
Application number
PCT/US2020/018355
Other languages
English (en)
Inventor
Guanzhou Wang
Saad Ahmad
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 WO2020168236A1 publication Critical patent/WO2020168236A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions

Definitions

  • Wireless communication devices may establish communications with other devices and data networks via various access networks.
  • a wireless communication device may establish communications via a 3GPP radio access network (RAN).
  • RAN radio access network
  • a wireless communication device may access a 3GPP network in order to communicate with other wireless devices and to interface with data networks communicatively coupled with the 3GPP RAN.
  • the wireless communication device may be adapted to also access non-3GPP radio access networks.
  • a wireless communication device which may be adapted to access a 3GPP RAN, may also be adapted to access 802.11 networks,
  • a wireless communication device may communicate over the 3GPP RAN and the non-3GPP RAN, e.g., an 802.1 1 network.
  • a computing system which may be, for example, a wireless transmit and receive unit (WTRU), may be programmed to receive a paging message.
  • the paging message may be received over a radio access network such as, for example, a 3GPP access network and may have originated from a server system comprised In a core network.
  • the paging message may comprise an indication associated with a multi-access PDU session.
  • the paging message may comprise an indication of“Multi-Access" and may be associated with reactivating an existing MA PDU session over the 3GPP access network and a non-3GPP access network.
  • the WTRU may be in a Connection Management-Idle (CM-IDLE) mode for the SGF ⁇ F 3 access network and may be In Connection Management-Idle (CM-IDLE) mode for the non-3GPP access network when the paging message is received.
  • CM-IDLE Connection Management-Idle
  • CM-IDLE Connection Management-Idle
  • the WTRU may respond to the paging message by generating a first Service Request.
  • the first Service Request may comprise an indication associated with the 3GPP access network,
  • the first Service Request may further comprise an indication that the first Service Request applies to the 3GPP access network only.
  • the first Service Request may also comprise one or more session identifiers associated with MA PDU sessions,
  • the session identifiers may be associated with one or more MA PDU sessions that may be identified for potential reactivation.
  • the WTRU may send the first Service Request via the 3GPP access network to the server system comprised in the core network.
  • the WTRU may further respond to the paging message by generating a second Service Request.
  • the second Service Request may comprise an indication associated with a non-3GPP access network
  • the second Service Request may comprise an indication that the second Service Request applies to the non-3GPP access network only.
  • the second Service Request may also comprise one or more session identifiers associated with MA PDU sessions.
  • the session Identifiers may be associated with one or more MA PDU sessions that may be reactivated and may be associated with the 3GPP access network and/or the non-3GPP access network.
  • the WTRU may send the second Service Request via the non- 3GPP access network to the server system comprised in the core network.
  • the WTRU may be programmed to receive a first Service Accept message in response to transmitting the first Service Request.
  • the first Service Accept message may be received via the 3GPP access network and may indicate the user plane has been activated for communications on the 3GPP access network,
  • the WTRU may send the second Service Request after receiving the first Service Accept message.
  • the WTRU may be programmed to receive a second Service Accept message in response to transmitting the second Service Request,
  • the second Service Accept message may be received via the non-3GPP access network and may indicate the user plane has been activated for communications on the non-3GPP access network.
  • the WTRU may receive data over a MA-PDU session using the 3GPP access network and the non-3GPP access network,
  • the WTRU may be programmed to establish and/or reactivate a MA PDU session wherein the WTRU may be in M-iDLE mode for a first access network and may be In CM-Connected mode for a second access network.
  • the WTRU may be in CM-IDLE mode for a 3GPP access network and in CM-Connected mode for a non-3GPP access network.
  • the WTRU may be in CM-IDLE mode for a non-3GPP access network and may be in CM-Connected mode for a 3GPP access network.
  • the WTRU may receive a message comprising an indication associated with a MA-PDU session. The message may be received, for example, over the second access network for which the WTRU may be in, for example, CM-Connected mode,
  • the WTRU may respond to the message by generating a first Service Request,
  • the Service Request may comprise an indication associated with the first access network which may be in, for example, a CM-id!e mode,
  • the Service Request may comprise an indication that the Service Request applies to the first access network only,
  • the Service Request may comprise one or more session identifiers associated with MA PDU sessions,
  • the WTRU may send the Service Request via the first access network,
  • the WTRU may be programmed to receive a Service Accept message in response to the first Service Request,
  • the WTRU may receive data over a MA-PDU session using the 3GPP access network and the non-3GPP access network.
  • a server system may be programmed to establish and/or reactivate MA PDU sessions with a WTRU,
  • the server system may be comprised In a network adapted to provide mobile-broadband functionality such as, for example, an Evolved Packet Core (EPC) or 5G core network,
  • the server system which may comprise, for example, an Access and Mobility Management Function (AMF) may receive a communication requesting to establish a A PDU session,
  • the communication may comprise a PDU session identifier corresponding to an existing PDU session that is to be reactivated,
  • the communication may identify a WTRU to which the MA PDU applies,
  • the server system in response to receiving the communication, may generate a message comprising an indication associated with a A PDU session,
  • the message may comprise, for example, a “Multi-Access” indication
  • the server system may send the message via a first access network which may be, for example, a 3GPP access network or a non-3GPP access network. If the message is sent over a 3GPP access network, the message may be a paging message, for example. If the message is sent over a non-3GPP access network, the message may be, for example, a non-Access Stratum (NAS) formatted signal,
  • NAS non-Access Stratum
  • the server system may receive a first Service Request which may comprise an indication associated with the first access network.
  • the first Service Request may comprise one or more session identifiers associated with multi-access PDU sessions.
  • the first Service Request may also comprise an indication the Service Request is associated with the first service access network only,
  • the server system may receive a second Service Request which may comprise an indication associated with the second access network.
  • the second Service Request may comprise one or more session identifiers associated with multi-access PDU sessions,
  • the second Service Request may also comprise an indication the Service Request is associated with the second service access network only.
  • the server system may activate a user plane for the first access network.
  • the server system may generate a first Service Accept message and may send the message via the first access network,
  • the server system may activate a user plane for the first access network,
  • the server system may generate a first Service Accept message and may send the message via the first access network,
  • the server system may send and receive data over a MA-PDU session using the first network, e.g., 3GPP access network, and the second network, e.g., non-3GPP access network.
  • the first network e.g., 3GPP access network
  • the second network e.g., non-3GPP access 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. 1 A 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. 1A according to an embodiment.
  • FIG. 2 depicts an example multi-access PDU session.
  • FIG. 3 depicts example processing tor selecting a URSP rule for PDU session establishment.
  • FIG. 4 depicts example processing for determining to reactivate a multi-access PDU session
  • FIG, 5 depicts example processing for network triggered Service Requests to activate a multi access PDU session
  • FIG. 6 depicts example processing for network triggered Service Requests to activate a multi access PDU session.
  • a WTRU may be configured to establish a communication session through one or both of a 3GPP RAN and a non-3GPP network, The WTRU may account for restricted service areas for 3GPP RAN service in configuring a communication session via one or both of a 3GPP RAN and a non-3GPP network.
  • a communications network may communicate with a WTRU to trigger activation of a MA-PDU session over a 3GPP RAN and a non-3GPP network,
  • 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 DFT-Spread OFDM (ZT UW DTS-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 DTS-s OFDM zero-tail unique-word DFT-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 RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs wireless transmit/receive units
  • Each of the 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 (!oT) 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
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b 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/115, the internet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an encode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, 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, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b 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 ceil 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 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, l.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (M!MO) technology and may utilize multiple transceivers for each sector of the cell.
  • M!MO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (!R), ultraviolet (UV), visible light, etc.).
  • the air interface 116 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 114a in the RAN 104/113 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 115/116/117 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 UL Packet Access (HSUPA).
  • the base station 114a 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 116 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 114a and the WTRUs 102a, 102b, 102c may Implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR),
  • NR New Radio
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a 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., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (l.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 (!S-95), Interim Standard 856 (!S-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like,
  • IEEE 802.11 l.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
  • CDMA2000 EV-DO Code Division Multiple Access 2000
  • iS-2000 interim Standard 95
  • the base station 114b 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.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 1G2d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 1Q2d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picoceil or femtoee!l.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, 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/115 may provide cal! 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/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 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/115 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 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of Interconnected computer networks and devices that use common
  • the networks 112 may Include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 1G2d 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, 1 A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, 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 118 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) circuits, any other type of integrated circuit (iC), a state machine, and the like,
  • the processor 118 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 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG, 1 B depicts the processor 118 and the transceiver 120 as separate components, It will be appreciated that the processor 118 and the transceiver 120 may be integrated together In an eiectronic 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 114a) over the air interface 116.
  • 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 iight signals, for example, in yet another embodiment, 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 116.
  • 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, thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , 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 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 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-removab!e memory 130 may include random-access memory (RAM), read-only 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 118 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 118 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 ceils, 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, in addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) 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.
  • location information e.g,, longitude and latitude
  • 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
  • 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
  • the WTRU 102 may inc!ude 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 downlink (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 self-interference 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 WRTU 102 may include a half-duplex radio for which transmission and reception of some or ail of the signals (e.g,, associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or ail of the signals (e.g,, associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the IRAN 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 1 16.
  • 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 116.
  • 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 ceil (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 (or PGW) 166, While each of 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.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • 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 conirol node, For example, 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, [0059]
  • 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 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices,
  • the CN 106 may facilitate communications with other networks, For example, 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 land-line communications devices, For example, 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, In addition, 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,
  • IMS IP multimedia subsystem
  • 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 112 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 (ST As) associated with the AP.
  • the AP may have an 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 ST As that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • DS Distribution System
  • 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.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., ail of the STAs) within or using the !BSS may communicate directly with each other.
  • the !BSS 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 via signaling.
  • 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 in 802,11 systems.
  • CSMA/CA 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.
  • VHT 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
  • time domain processing may be done on each stream separately.
  • the streams may be mapped on to the two 80 Hz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation or 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 l af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11 ah relative to those used in 802.11 h, and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11 ah may support Meter Type
  • 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.11 n, 802.1 lac, 802.1 laf, and 802.11 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 ail STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among ail 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 !VIHz mode, even if the AP, and other ST As in the BSS support 2 !VIHz, 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, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available,
  • the available frequency bands which may be used by 802.11 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.11 ah is 6 MHz to 26 MHz depending on the country code,
  • FIG. 1 D Is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 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 beamformlng 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, Iran embodiment, 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 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, In the 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).
  • 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, in the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band, In a non-standalone configuration 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.
  • eNode-Bs 160a, 160b, 160c eNode-Bs
  • 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 or 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, dual connectivity, 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 115 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 each of the foregoing elements are depicted as part of the CN 1 15, 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 1 13 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 PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like, Network slicing may be used by the AMF 182a, 182b in order to customize CN support or WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 162 may provide a control plane function for switching between the RAN 1 13 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.
  • the 8MF 183a, 183b may be connected to an AMF 182a, 182b in the CN 1 15 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 1 15 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 LIE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink 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 113 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 !P-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 1 15 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 1 15 and the PSTN 108,
  • the CN 1 15 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,
  • theWTRUs 102a, 102b, 102c may be connected to a local Data Network (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,
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-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, For example, the one or more emulation devices may perform the one or more, or a!!, functions while being fully or partially implemented and/or deployed as part of a wired and/or wlreiess 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 may 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.
  • a WTRU may be configured to establish a communication session through one or both of a 3GPP RAN and a non-3GPP network.
  • the WTRU may account for restricted service areas for 3GPP RAN service in configuring a communication session via one or both of a 3GPP RAN and a non-3GPP network.
  • a communications network may communicate with a WTRU to trigger activation of a MA-PDU session through one or both of a 3GPP RAN and a non-3GPP network.
  • a protocol data unit (PDU) session may be a logical connection between a WTRU and a data network.
  • a MA-PDU session may be a PDU session that provides PDU connectivity via more than one access network.
  • a MA-PDU session may be a PDU session that provides PDU connectivity simultaneously via a 3GPP access network and a non-3GPP access network, and/or provides PDU connectivity one-at-a-time via one of a 3GPP access network or non-3GPP access network.
  • MA-PDU sessions may be employed to support 3GPP processing such as, for example,“Access Traffic Steering, Switching and Splitting” (ATSSS) processing, which may support data traffic steering, switching, and/or splitting between a 3GPP access network and a non-3GPP access network.
  • ATSSS Access Traffic Steering, Switching and Splitting
  • a MA-PDU session may be established using an example PDU Session Establishment implementation, For example, a WTRU may provide a“MA-PDU Request” indication and the WTRU’s ATSSS capability info in a PDU Session Establishment Request message.
  • a network which may be, for example, a 3GPP or 5G core network, may select the session management function (SMF) and user plane functions (UPF) that support MA-PDU session processing and may activate the User Plane (UP) for a 3GPP RAN, which may be referred to as, for example, a 3GPP access network or a 3GPP access leg, and a non-3GPP network, which may be referred to as, for example, a non-3GPP access network or a non- 3GPP access leg.
  • SMF session management function
  • UPF user plane functions
  • FIG, 2 depicts an example MA-PDU session.
  • multiple data flows e.g., flow 1 , flow 2, and flow 3
  • WTR.U WTR.U
  • UPF user piane functionaiity
  • a network which may be, for example, a 5G core network, may coordinate the establishment of access through the 3GPP and non-3GPP networks,
  • the 5G network may generate ATSSS rules which may be used to control how data traffic may be distributed between a 3GPP access network and a non-3GPP access network.
  • the 3GPP network may install the rules on the WTRU and on related network functions such as, for example, user piane functions (UPFs).
  • UPFs user piane functions
  • Mobility Restrictions may be defined.
  • a Forbidden Area and/or non-Aliowed Area restriction may be defined.
  • a WTRU may not be permitted to initiate communication with the radio access network for a public land mobile network (PLMN).
  • PLMN public land mobile network
  • a non-A!owed Area restriction may not be permitted to initiate a Service Request or SM signaling to obtain user services.
  • a non-A!owed Area restriction may apply to a WTRU in various states including, for example, CM-IDLE and/or CM-CONNECTED states.
  • a WTRU located in a non-A!!owed Area may (e.g., sha!!) respond to core network paging and/or non-Access Stratum (NAS) Notification messages from the non-3GPP access network with a Service Request,
  • NAS non-Access Stratum
  • the term“Restricted Service Area 8 may be used to refer to either a Forbidden Area or non-A!iowed Area or both.
  • a WTRU may have pending uplink (UL) data that may be associated with a MA- PDU session as specified, for example, by a URSP rule, and may have not established a MA-PDU session.
  • the WTRU may not be allowed to initiate PDU session establishment if the associated PDU Session is a 3GPP-access-oniy PDU Session. But if the PDU Session is a Muiti-Access PDU session with a non-3GPP network or access leg, the non-3GPP access leg may not be impacted by the 3GPP-access area restriction.
  • the WTRU may be configured to Initiate MA-PDU session establishment if certain conditions are satisfied.
  • the WTRU may be configured with service logic to determine whether the WTRU may initiate a MA-PDU session establishment, and to determine the manner that MA-PDU session establishment may be performed in view of the WTRU possibly being restricted with respect to 3GPP network access.
  • the WTRU may have pending UL data that may be associated with a MA-PDU session as specified, for example, by a URSP rule, and may have previously established a MA-PDU session.
  • the WTRU may be configured to determine whether the WTRU may activate the MA-PDU session for UP data transmission, and to determine the manner the MA-PDU session activation may be performed while taking into consideration the WTRU may be restricted with respect to 3GPP access network,
  • a MA-PDU session may be triggered by a network such as, for example, a 5G core network.
  • a network such as, for example, a 5G core network.
  • the 5G network may use paging (e.g., on the 3GPP RAN or access leg only) or DL Notification (e.g., on either the 3GPP access leg or non-3GPP access !eg) to trigger a Service Request and bring the WTRU to Connected status on the particular access.
  • paging e.g., on the 3GPP RAN or access leg only
  • DL Notification e.g., on either the 3GPP access leg or non-3GPP access !eg
  • the network may be configured to trigger the activation of a MA-PDU session in instances where both 3GPP access and non-3GPP access legs may be involved.
  • the network may be configured to provide processing in instances that the WTRU Is in a Restricted Service Area for 3GPP access.
  • a WTRU that may be in a restricted service area (RSA) with respect to a 3GPP RAN and has uplink (UL) data for a MA-PDU session, may apply lower priority URSP (UE Route Selection Policy) ru!e(s) or Route Selection Descriptor(s) to associate the data with non-3GPP access network PDU sessions.
  • URSP UE Route Selection Policy
  • a WTRU that may be in an RSA and has UL data tor a MA-PDU session may determine whether to activate a MA-PDU session based on the preferred access as specified in Access Traffic Steering Switching Splitting (ATSSS) rules.
  • ATSSS Access Traffic Steering Switching Splitting
  • a WTRU that may be in an RSA and which determines to reactivate a MA-PDU session, may use indications in the Service Request (SR) message to activate the non-3GPP access leg (e.g., the non-3GPP access leg only),
  • SR Service Request
  • MA-PDU sessions may be established or activated when a WTRU is in Restricted Service Area, if the WTRU has UL pending data that may be associated with a MA-PDU Session (as specified by, for example, the URSP rules), and the WTRU is in the Restricted Service Area for 3GPP access, the WTRU may be configured to determine whether the WTRU may Initiate the MA-PDU Session establishment (if the target MA-PDU Session has not been established), or whether the WTRU may request the activation of an existing MA-PDU Session.
  • the WTRU may be configured to determine whether the WTRU may Initiate the MA-PDU Session establishment (if the target MA-PDU Session has not been established), or whether the WTRU may request the activation of an existing MA-PDU Session.
  • the WTRU may determine whether there are other URSP rules that satisfy the following conditions; the Traffic Descriptor of the URSP rule matches the pending data and the corresponding Route Selection Descriptor matches at least one existing non-3GPP-access F 3 DU Session; or the Traffic
  • the WTRU may use this URSP ru!e to establish a new non-3GPP-access PDU Session or to reactivate the existing non-3GPP-access PDU Session for the data, rather than establishing or reactivating the MA-PDU Session, [0098] FIG.
  • URSP rule which has a corresponding Traffic Descriptor
  • the URSP may have a higher priority Route Selection Descriptor (RSD) 1 which points to a Multi- Access PDU Session, and a lower priority RSD 2 which points to a non-3GPP access PDU Session, if the WTRU is in Restricted Service Area for 3GPP access, the lower priority RSD 2 may be applied and the WTRU may establish a non-SGPP-access-oniy PDU Session for the data.
  • Route selection descriptor 2 may be selected even though it has lower priority due to the location of the WTRU within a Restricted Service Area.
  • the WTRU may have two URSP rules, each of which may have a corresponding or matching Traffic Descriptor.
  • the RSD in the URSP Rule 1 which may have a higher priority, points to a Multi-Access PDU Session
  • the RSD in the URSP Rule 2 which may have a lower priority, points to a non-3GPP access PDU Session, li the WTRU is in Restricted Service Area for 3GPP access
  • the lower priority URSP Rule 2 may be applied and the WTRU may establish a non- 3GPP-access-on!y PDU Session for the data.
  • URSP rule 2 may be selected even though it has lower priority due to the location of the WTRU within a Restricted Service Area.
  • a MA-PDU Session may already exist and may have ATSSS rules associated with the MA-PDU session.
  • the WTRU may be configured to check the configured ATSSS rules that may be used to control data steering for the MA-PDU Session before reactivating the MA-PDU Session. If the ATSSS rules indicate that the preferred access or active access for the UL data is non-3GPP access, the WTRU may initiate the reactivation of the MA-PDU session.
  • the WTRU may indicate to the network, e.g., 5G network, to re-activate the user plane (UP) for the non-3GPP access leg (e.g., for the non-3GPP access leg only). If the ATSSS rules indicate that the preferred access or active access for the UL data is 3GPP access, the WTRU may determine to not initiate the reactivation of the MA-PDU session.
  • UP user plane
  • FIG. 4 depicts an example process for a WTRU to determine whether to reactivate a MA-PDU session
  • a WTRU in RSA may receive UL data from a higher layer.
  • the WTRU may select a URSP rule that points to a MA-PDU session.
  • the WTRU may determine the preferred access (e.g., 3GPP access or non-3GPP access) based on, for example, one or more ATSS rules.
  • the WTRU may perform processing to re-activate a MA-PDU session with non-3GPP access in the user plane (UP), li the WTRU determines the preferred access is non-3GPP access, the WTRU may not reactivate the MA-PDU session, in which case data may be buffered or discarded.
  • UP user plane
  • the WTRU may initiate the establishment or reactivation of the MA-PDU session, regardless of the ATSSS rules output.
  • the WTRU may indicate to the network to activate the user plane (UP) for the non-3GPP access leg only, If the WTRU is in the Service Restricted Area, the WTRU may determine not to follow the ATSSS rules for the MA-PDU session and may steer the data traffic associated with the MA-PDU session towards the non-3GPP access leg only.
  • UP user plane
  • the WTRU may initiate the MA-PDU session establishment over the non-3GPP access leg.
  • the WTRU may send a PDU Session Establishment Request over the non-3GPP access leg to the network, li the WTRU Is in CMJDLE state, it may Initiate Service Request Implementation over the non-3GPP access leg to enter CM_Connected state first.
  • the WTRU may include an Indication,“non-3GPP access leg only", to inform the network, e.g., 5G network, that only the UP for the non-3GPP access leg may presently be needed.
  • the WTRU may indicate in the request that the WTRU is In Restricted Service Area for 3GPP access, which may cause the network to set up the UP for the non- 3GPP access leg (e.g., for the non-3GPP access leg only).
  • the network may skip the UP activation processing for the 3GPP access leg, The network may also configure the ATSSS rules to steer traffic to the non-3GPP access leg.
  • the WTRU may initiate the MA-PDU session activation over the non-3GPP access leg, or the WTRU may initiate the MA-PDU session activation over the 3GPP access leg.
  • the WTRU may include in a Service Request message sent over the non-SGPP access leg, an indication,“non-3GPP access leg only,” to inform the network, e.g., 5G network, that only the UP for the non-3GPP access leg may presently be needed.
  • an indication “non-3GPP access leg only,” to inform the network, e.g., 5G network, that only the UP for the non-3GPP access leg may presently be needed.
  • the WTRU may indicate in the Service Request that the WTRU Is in Restricted Service Area for 3GPP access, which may cause the network to reactivate only the UP for the non-3GPP access leg, Upon receiving this“non-3GPP access leg only” or“3GPP access in RSA” Indication, the network may skip the UP activation processing for the 3GPP access leg. The network may also configure the ATSSS rules to steer ail the traffic to the non-3GPP access leg.
  • the WTRU may include in a Service Request message a MA- PDU Session ID to identify the PDU Session to be activated, If located in the Forbidden Area of Restricted Access Area, the WTRU may also include the“non-3GPP access leg only” or“3GPP access in RSA" indication to inform the network to reactivate only the UP for the non-3GPP access leg.
  • a network such as, for example, a 5G core network or EPC, may send a communication that triggers a WTRU to generate and send Service Requests for establishing MA-PDU sessions.
  • the network communication may include a“Multi-Access” indication in a paging message or NAS Notification.
  • the WTRU may initiate parallel Service Request implementations over both 3GPP access and non-3GPP access legs and may use indications to activate user plane (UP) functionality for each access leg respectively.
  • UP user plane
  • a network e.g., a 5G core network or EPC
  • different processing may be employed for triggering the WTRU to initiate the Service Request processing to activate the MA-PDU session depending on the WTRU connection management (CM) modes or states on the 3GPP access network and the non-3GPP access network.
  • the processing may be different, for example, depending upon: whether the WTRU is in CM-IDLE mode for both 3GPP access and non-3GPP access networks; and/or whether the WTRU is in CM-IDLE mode for 3GPP access network and CM jConnected mode for the non-3GPP access network.
  • a WTRU may be in CMJDLE state for both 3GPP access network and non-3GPP access network
  • the network e.g., 5G core network
  • the WTRU may initiate a Service Request implementation over the 3GPP access leg.
  • the WTRU may (e.g., may optionally) include the MA-PDU Session ID(s) as the“PDU Session to be activated" in one or more Service Request messages and may (e.g., may optionally) include an additional indication,“3GPP access leg only," in the Service Request message over 3GPP access, Each Service Request implementation may (e.g., may only) activate the UP for the 3GPP access leg (e.g., for only the 3GPP access leg).
  • the WTRU may also initiate a Service Request implementation over the non-3GPP access leg.
  • the WTRU may initiate a Service Request implementation over the non-3GPP access leg and may include an additional indication in the Service Request.
  • the additional indication may correspond to a“non-3GPP access leg only" flag and/or IE in the Service Request message over the non-3GPP access leg.
  • FIG, 5 depicts example processing for network-triggered Service Requests for a MA-PDU session where the WTRU may be in CM-IDLE for a 3GPP access network and a non-3GPP access network.
  • a User Plane Function which may be comprised in a 5G core network, may receive downlink (DL) data.
  • the UPF may notify the Session Management Function (SMF), which may also be comprised in a 5G core network, of the data arrival.
  • SMF Session Management Function
  • the SMF may determine a PDU Session ID associated with a MA-PDU session that may be used to communicate the received downlink data to the WTRU, At 3. the SMF may invoke the Access Management Function (AMF) service Namf_Communication_N1 N2MessageTransfer and may include the PDU Session ID in the request.
  • AMF Access Management Function
  • the AMF which may also be comprised in the 5G core network, may maintain information regarding which PDU sessions are MA-PDU sessions. Upon receiving a PDU session ID from the SMF, the AMF may search its stored session context Information to identify whether the particular Session ID received from the SMF corresponds to a MA-PDU session. At 4, the AMF may generate and communicate one or more messages (e.g., paging messages) to the radio access network (RAN) which may be a 3GPP RAN. The associated access in the one or more messages, e.g., paging messages, may be set to“Multi- Access.”
  • RAN radio access network
  • the RAN may receive the one or more messages, e.g., paging messages, from the AMF and may communicating messages, e.g., paging messages, to the WTRU.
  • The“Multi-Access” indication may be included in the one or more messages, e.g., paging messages, that are sent to the WTRU,
  • the WTRU may generate and send a Service Request over the 3GPP access network leg and may include its MA-PDU Session iD(s) and a“3GPP access network leg only” indication In the Service Request message, The WTRU may also include in the Service Request other 3GPP-access-on!y PDU Session IDs together with MA-PDU Session !D(s) as the“PDU Sessions to be activated.” The WTRU may send the Service Request to the AMF via the 3GPP access network.
  • the AMF may coordinate the activation of the user plane (UP) for the 3GPP access network leg of the MA-PDU session as a part of the Service Request implementation over the 3GPP access network leg.
  • UP user plane
  • the AMF may generate and send a Service Accept message over the 3GPP access network leg to the WTRU.
  • the WTRU may initiate a second Service Request over the non-3GPP access network leg and may include its MA- PDU Session !D(s) and an additional indication (e.g.,“non-3GPP access leg only" indication) in the Service Request message.
  • the WTRU may also include other non-3GPP-access-on!y PDU Session IDs together with MA-PDU Session !D(s) as the“PDU Sessions to be activated.”
  • the VVTRU may send the Service Request to the AMF via the non ⁇ 3GPP access network,
  • the AMF may coordinate activating the user plane (UP) for the non-3GPP access network leg of the MA-PDU session as part of the Service Request implementation over non-3GPP access network leg.
  • UP user plane
  • the A F may generate and send a Service Accept message over the non-3GPP access network ieg to the WTRU.
  • a VVTRU may be in CM JDLE mode or state for a 3GPP access network and CM_Connecied mode for a non-3GPP access network
  • the network e.g., 5G core network
  • A“Multi-Access” Indication may be included in the paging or Notification message,
  • the WTRU may initiate a Service Request over the 3GPP access network leg and may include, e.g., optionally include, the MA-PDU Session ID in the Service Request message, Because the WTRU may be in CM_Connected state over non-3GPP access network leg, the network may activate, e.g., directly activate, the user plane (UP) for the non-3GPP access network leg of the MA-PDU session without waiting for the Service Request from the 3GPP access network leg. When the network receives the Service Request from the 3GPP access network leg, the network may (e.g., may only) activate the UP for the 3GPP access network leg of the MA-PDU session.
  • UP user plane
  • the WTRU may include (e.g., explicitly Include) a“3GPP access ieg only” Indication in the Service Request message.
  • FIG, 6 depicts processing for network-triggered Service Request for a MA-PDU session where the WTRU may be in CM-!DLE mode for a 3GPP access network and in CM_Connected mode tor a non- 3GPP access network,
  • the UPF may receive downlink (DL) data, The data may be for deliver to the VVTRU.
  • DL downlink
  • the UPF may notify the SMF of the data arrival.
  • the SMF may determine the PDU Session ID which is associated with a MA-PDU Session that may be used to de!iver the data.
  • the SMF may invoke the AMF service Namf_Communication_N1 N2MessageTransfer and may include the determined PDU Session ID in the request, The request is received at the AMF.
  • the AMF may generate and send one or more NAS Notification messages over the non-3GPP access network ieg to the WTRU.
  • the associated access in the Notification message may be set to“Multi-Access.”
  • Ai 5 the AMF may coordinate activating the user plane (UP) for the non-3GPP access network leg of the MA-PDU session,
  • the WTRU may initiate, e.g., generate and send, a Service Request over the 3GPP access network leg and may include its MA-PDU Session iD(s) in the SR message, The WTRU may also include a “3GPP access leg only” indication.
  • the AMF may coordinate activating the user plane (UP) for the 3GPP access network leg of the MA-PDU session as part of the Service Request implementation over the 3GPP access network leg, [0129]
  • the AMF may communicate, e.g., generate and send, a Service Accept message over the 3GPP access network leg to the WTRU.
  • Similar processing may apply if the WTRU is in CM_Connected mode for 3GPP access network and In CMJDLE mode for non-3GPP access network.
  • the network may reactivate, e.g., directly reactivate, the UP connection for the 3GPP access network leg.
  • the WTRU upon receiving the triggering message (e.g., paging or NAS Notification over the 3GPP access network leg), may use a Service Request implementation to reactivate the UP connection for the non-3GPP access network leg.
  • a WTRU may be configured to establish a communication session through one or both of a 3GPP RAN and a non-3GPP network.
  • the WTRU may account for restricted service areas for 3GPP RAN service in configuring a communication session via one or both of a 3GPP RAN and a non-3GPP network.
  • a communications network may communicate with a WTRU to trigger activation of
  • a WTRU may be programmed to receive a paging message from a 5G core network system via a radio access network, such as, for example, a 3GPP access network.
  • the paging message may comprise an Indication of“Multi- Access” and may be associated with reactivating an existing MA PDU session over the 3GPP access network and a non-3GPP access network.
  • the WTRU may be in a CM-IDLE mode for both the 3GPP access network and the non-3GPP access network.
  • the WTRU may respond by generating a first Service Request and a second Service Request.
  • the first Service Request may comprise an indication associated with the 3GPP access network and may be communicated via the 3GPP access network
  • the second Service Request may comprise an Indication associated with the non-3GPP access network and may be communicated via the non-3GPP access network.
  • the 5G core network may activate user pianos for each of the 3GPP access network connection and the non-3GPP access network connection.
  • implementations extend to all types of service layer architectures, systems, and embodiments.
  • the techniques described herein may be applied independently and/or used In combination with other resource configuration techniques,
  • the entities performing the processes described herein may be logical entities that may be implemented in the form of software (i.e., computer-executable instructions) stored in a memory of, and executing on a processor of, a mobile device, network node or computer system. That is, the processes may be implemented in the form of software (i.e., computer-executable instructions) stored in a memory of a mobile device and/or network node, such as the node or computer system, which computer executable instructions, when executed by a processor of the node, perform the processes discussed. It is also understood that any transmitting and receiving processes illustrated in F!Gs may be performed by communication circuitry of the node under control of the processor of the node and the computer-executable instructions (e.g., software) that it executes.
  • software i.e., computer-executable instructions
  • the computing device In the case where program code is stored on media, it may be the case that the program code in question is stored on one or more media that collectively perform the actions in question, which is to say that the one or more media taken together contain code to perform the actions, but that - in the case where there is more than one single medium - there is no requirement that any particular part of the code be stored on any particular medium,
  • the computing device In the case of program code execution on programmable devices, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device,
  • One or more programs that may implement or utilize the processes described in connection with the subject matter described herein, e.g., through the use of an API, reusable controls, or the like.
  • Such programs are preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system, however, the program(s) can be implemented In assembly or machine language, if desired in any case, the language may be a compiled or interpreted language, and combined with hardware implementations.
  • example embodiments may refer to utilizing aspects of the subject matter described herein in the context of one or more stand-alone computing systems, the subject matter described herein is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment, Still further, aspects of the subject matter described herein may be implemented in or across a plurality of processing chips or devices, and storage may similarly be affected across a plurality of devices, Such devices might include personal computers, network servers, handheld devices, supercomputers, or computers integrated into other systems such as automobiles and airplanes.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs),
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs)
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
  • ATSSS Access Traffic Steering Switching Splitting
  • N3IWF Non-3GPP interworking Function
  • SMF Session Management Function
  • URSP UE Route Selection Policy

Landscapes

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

Abstract

L'invention concerne une WTRU pouvant recevoir un message de radiorecherche en provenance d'un système de réseau central par l'intermédiaire d'un réseau d'accès 3 GPP, le message de radiorecherche pouvant comprendre une indication "multi-accès" et pouvant être associé à la réactivation d'une session de PDU MA existante sur le réseau d'accès 3 GPP et un réseau d'accès non-3 GPP, la WTRU pouvant être en mode CM-iDLE pour les réseaux d'accès 3 GPP et non-3 GPP. La WTRU peut répondre par la génération d'une première demande de service et d'une seconde demande de service. La première demande de service peut comprendre une indication associée au réseau d'accès 3 GPP et peut être communiquée par l'intermédiaire du réseau d'accès 3 GPP. La seconde demande de service peut comprendre une indication associée au réseau d'accès non-3 GPP et peut être communiquée par l'intermédiaire du réseau d'accès non-3 GPP. En réponse aux demandes de service, le réseau central peut activer des plans d'utilisateur à la fois pour le réseau d'accès 3 GPP et le réseau d'accès non-3 GPP.
PCT/US2020/018355 2019-02-15 2020-02-14 Session pdu multi-accès WO2020168236A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962806133P 2019-02-15 2019-02-15
US62/806,133 2019-02-15
US201962826237P 2019-03-29 2019-03-29
US62/826,237 2019-03-29

Publications (1)

Publication Number Publication Date
WO2020168236A1 true WO2020168236A1 (fr) 2020-08-20

Family

ID=69844907

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/018355 WO2020168236A1 (fr) 2019-02-15 2020-02-14 Session pdu multi-accès

Country Status (1)

Country Link
WO (1) WO2020168236A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022222753A1 (fr) * 2021-04-19 2022-10-27 中兴通讯股份有限公司 Procédé et dispositif de traitement d'encombrement de réseau, terminal et support de stockage
WO2022227849A1 (fr) * 2021-04-27 2022-11-03 中兴通讯股份有限公司 Procédé et appareil d'accès wifi, dispositif électronique et support de stockage
US11895531B2 (en) 2021-07-05 2024-02-06 Samsung Electronics Co., Ltd. Method and device for regulating flow of data transmission in a wireless network
WO2024098033A1 (fr) * 2022-11-03 2024-05-10 Interdigital Patent Holdings, Inc. Sélection et enregistrement auprès d'un réseau mobile secondaire à fonctionnalité dualsteer
WO2024121754A1 (fr) * 2022-12-08 2024-06-13 Nokia Technologies Oy Procédés, appareils, et programme informatique pour établir une session de données d'accès multiple dans un réseau mobile
WO2024168230A1 (fr) * 2023-02-09 2024-08-15 Interdigital Patent Holdings, Inc. Unités d'émission/réception sans fil et procédés associés à des restrictions de modes d'orientation

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032972A1 (fr) * 2017-08-11 2019-02-14 Idac Holdings, Inc. Orientation et commutation de trafic entre de multiples réseaux d'accès

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032972A1 (fr) * 2017-08-11 2019-02-14 Idac Holdings, Inc. Orientation et commutation de trafic entre de multiples réseaux d'accès

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16)", vol. SA WG2, 4 February 2019 (2019-02-04), XP051697369, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/Latest%5FSA2%5FSpecs/DRAFT%5FINTERIM/Archive/INTERIM%5FDRAFT%5F23502%2DnewRel%2D16%2BCRs%2E%2Ezip> [retrieved on 20190204] *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16)", vol. SA WG2, 4 February 2019 (2019-02-04), XP051688561, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/Latest%5FSA2%5FSpecs/DRAFT%5FINTERIM/Archive/INTERIM%5FDRAFT%5F%28remove%5F862R3%5Femail%29%5F23501%2DnewRel%2D16%2BCRs%2Ezip> [retrieved on 20190204] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022222753A1 (fr) * 2021-04-19 2022-10-27 中兴通讯股份有限公司 Procédé et dispositif de traitement d'encombrement de réseau, terminal et support de stockage
WO2022227849A1 (fr) * 2021-04-27 2022-11-03 中兴通讯股份有限公司 Procédé et appareil d'accès wifi, dispositif électronique et support de stockage
US11895531B2 (en) 2021-07-05 2024-02-06 Samsung Electronics Co., Ltd. Method and device for regulating flow of data transmission in a wireless network
WO2024098033A1 (fr) * 2022-11-03 2024-05-10 Interdigital Patent Holdings, Inc. Sélection et enregistrement auprès d'un réseau mobile secondaire à fonctionnalité dualsteer
WO2024121754A1 (fr) * 2022-12-08 2024-06-13 Nokia Technologies Oy Procédés, appareils, et programme informatique pour établir une session de données d'accès multiple dans un réseau mobile
WO2024168230A1 (fr) * 2023-02-09 2024-08-15 Interdigital Patent Holdings, Inc. Unités d'émission/réception sans fil et procédés associés à des restrictions de modes d'orientation

Similar Documents

Publication Publication Date Title
US20230116626A1 (en) Network slice reselection
EP3643116B1 (fr) Relocalisation de plan d&#39;utilisateur
EP3881509B1 (fr) Activation d&#39;une communication de réseau non public
WO2020168236A1 (fr) Session pdu multi-accès
EP3811684A1 (fr) Manipulation de tranches de réseau mutuellement exclusives
WO2021163665A1 (fr) Procédés, appareil et systèmes pour sessions d&#39;unités de données de protocole d&#39;accès multiple
US20220337989A1 (en) Device to device discovery via a relay device
EP4154668A1 (fr) Découverte, sélection et accès optimal à des réseaux informatiques périphériques
WO2022236072A1 (fr) Transmission de service de multidiffusion/diffusion pour une wtru distante par l&#39;intermédiaire d&#39;une wtru de relais
EP4320897A1 (fr) Procédés, appareil et systèmes pour des services d&#39;exposition de commande d&#39;événement/exception de système volant sans équipage/sans pilote embarqué (uas) et de politique
EP4320923A1 (fr) Continuité de service pendant une procédure de relocalisation de contexte d&#39;application
WO2021237134A1 (fr) Procédé de commutation de mode de distribution de service de diffusion générale /diffusion groupée multimédia (mbms)
WO2021207165A1 (fr) Procédés et appareils pour une qualité de service de bout en bout pour une communication entre des unités d&#39;émission-réception sans fil
WO2024039843A1 (fr) Politique de sélection de réseau local sans fil (wlan)
WO2024211885A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u pendant une découverte
WO2024211891A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u sans découverte autonome
WO2024025922A1 (fr) Contrôle d&#39;accès à un réseau d&#39;hébergement et gestion de congestion
WO2023192146A1 (fr) Sélection d&#39;une route dans un système de communication sans fil
WO2024168262A1 (fr) Contrôle d&#39;accès d&#39;une wtru à un relais de réseau relatif à un service ai/ml
WO2024211895A1 (fr) Systèmes et procédés d&#39;établissement de sécurité entre une unité d&#39;émission-réception sans fil cible (wtru) et une wtru relais u2u
WO2024147984A9 (fr) Gestion de liaison de bout en bout par l&#39;intermédiaire d&#39;un relais wtru-à-wtru
WO2024168233A1 (fr) Dispositifs de réseau et procédés associés à des restrictions de mode de direction
EP4197169A1 (fr) Support de services de diffusion/multidiffusion pour relais de réseau

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

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

Country of ref document: EP

Kind code of ref document: A1