WO2025240776A1 - Procédés et appareils d'enregistrement et de désenregistrement coordonnés de dispositifs qui communiquent à l'aide de deux branches d'accès ou plus - Google Patents

Procédés et appareils d'enregistrement et de désenregistrement coordonnés de dispositifs qui communiquent à l'aide de deux branches d'accès ou plus

Info

Publication number
WO2025240776A1
WO2025240776A1 PCT/US2025/029617 US2025029617W WO2025240776A1 WO 2025240776 A1 WO2025240776 A1 WO 2025240776A1 US 2025029617 W US2025029617 W US 2025029617W WO 2025240776 A1 WO2025240776 A1 WO 2025240776A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
leg
wtru
registration
access leg
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/US2025/029617
Other languages
English (en)
Inventor
Magurawalage Chathura Madhusanka Sarathchandra
Rocco Di Girolamo
Taimoor ABBAS
Anuj Sethi
Xavier De Foy
Guanzhou Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent 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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025240776A1 publication Critical patent/WO2025240776A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems related to coordinated registration and deregistration of devices.
  • Devices e.g., wireless transmit/receive units (WTRUs) may be communicatively coupled to a wireless network, e.g., as a radio access network (RAN).
  • a wireless network e.g., as a radio access network (RAN).
  • Some devices such as a DualSteer device, may communicate using two or more independent access legs, each access leg providing a wireless connection between the device and the network node, such as a base station (BS).
  • BS base station
  • a system may need to register and to deregister a first access leg and a second access leg of the device with the RAN or other network node.
  • a DualSteer WTRU configured to communicate using two or more access legs, may communicate with a RAN using one of the access legs to register and/or to deregister both access legs. Accordingly, systems and methods for registering multiple access legs and receiving configuration notification for the registration, as well as a method for deregistering the access privileges, are described.
  • a method performed by the WTRU for registering a first access leg and a second access leg may include: enabling, by the WTRU, combined registration of the first access leg and the second access leg based on a trigger; determining, by the WTRU, to perform the combined registration of the first access leg and the second access leg based on at least one first condition being satisfied; identifying, by the WTRU, the first access leg as a primary leg to use for the combined registration based on at least one second condition being satisfied; transmitting, via the first access leg, registration data for the first access leg and for the second access leg; receiving, via the first access leg, a message based on the registration data, wherein the message includes first configuration data for the first access leg and second configuration data for the second access leg, such that the first configuration data and the second configuration data include respective indications that the first access leg and the second access leg are registered; configuring, by the WTRU, the first access leg based on the first configuration data; and configuring
  • Such a method may also include receiving, by the first access leg, a deregistration message comprising an indication to deregister the first access leg; determining, by the WTRU, to maintain a registration of the second access leg; and transmitting, by the second access leg, a second message to register the second access leg.
  • the deregistration message may include data indicative of what to do with the registration of the second access leg, and wherein determining to maintain the registration of the second access leg is based on the deregistration message.
  • the trigger may be, or may include, a determination that a subscription is to be changed or a preconfiguration for combined registration or a configuration message or updated capability support or Dual Steer connectivity support.
  • Other trigger examples may be, or may include a requirement to change a subscription from one access leg to another or a resource reallocation or load sharing or steering mode rules.
  • the first condition may be, or may include, a change in location of the WTRU, a load balancing, a change in coverage in one or both of the first and second access legs, the Radio Access Technology (RAT) in use on one or both of the first and second access legs, signal quality on one or both of the first and second access legs, a notification or configuration message received by the WTRU, network congestion, or network coverage.
  • RAT Radio Access Technology
  • the method may also include determining, by the WTRU, a combined registration configuration, the combined registration configuration including an indication that the first access leg is the primary leg.
  • the determining the combined registration configuration may include determining whether combined registration of the first access leg and the second access leg is available.
  • the registration data may include a request for the primary leg and secondary leg to be swapped, an indication of which of the first access leg or second access leg should receive the message based on the registration data, timing information, a message containing registration information for the first and second access legs, or a message containing registration information for the second access leg.
  • the configuring of the second access leg may entail communicating the second configuration data to the second access leg.
  • the method may include any combination of the foregoing features as part of the method.
  • FIG. 1A is a system diagram illustrating an example communications system
  • FIG. IB 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;
  • WTRU wireless transmit/receive unit
  • FIG. 1C 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;
  • RAN radio access network
  • CN core network
  • FIG. ID 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;
  • FIG. 2 is a diagram illustrating an example of a UE
  • FIG. 3 is a diagram illustrating an example of a dual-MT device
  • FIG. 4 is a an exemplary signaling diagram which shows procedures for coordinated registration
  • FIG. 5 is an exemplary signaling diagram which shows procedures for coordinated deregistration.
  • FIG. 6 is a flowchart of an illustrative method for registering the first and second access legs, in accordance with some embodiments of the disclosure.
  • the methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks.
  • An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.
  • FIG. 1A is a system 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), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (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 singlecarrier FDMA
  • ZT zero-tail
  • ZT UW unique-word
  • DFT discreet Fourier transform
  • OFDM ZT UW DTS-s 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/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, 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.
  • 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 (or be) 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
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • 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, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112.
  • the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 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 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 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any 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 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 (IR), 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 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 Packet Access (HSDPA) and/or High-Speed Uplink 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).
  • a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • 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., an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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 (Wi-Fi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-2000 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global
  • 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, 102d 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, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.
  • 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 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/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 any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi 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 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 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 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/114 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 114b, which may employ an IEEE 802 radio technology.
  • FIG. IB 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/mi crophone 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 elements/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. IB 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, e.g., 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 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 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.
  • the WTRU 102 may employ MIMO technology.
  • 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.
  • 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-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 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 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 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.
  • the processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity.
  • the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., 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 elements/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, and/or a humidity sensor.
  • 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, and/or a humidity sensor.
  • 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 uplink (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 118).
  • 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 uplink (e.g., for transmission) or the downlink (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 uplink (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1C 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, and 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 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 receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one 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 160a, 160b, and 160c in the RAN 104 via an SI 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 SI 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 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • 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 land-line 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. 1A-1D 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 (STAs) 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 into 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 le DLS or an 802.1 Iz 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 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.
  • 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 nonadj acent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20 MHz, 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 a medium access control (MAC) layer, entity, etc.
  • MAC medium access control
  • Sub 1 GHz modes of operation are supported by 802.1 laf and 802.1 lah.
  • the channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in
  • 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum
  • 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,
  • MTC meter type control/machine-type communications
  • 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 In, 802.1 lac, 802.1 laf, and 802.1 lah 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, 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.1 lah, 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 lah is 6 MHz to 26 MHz depending on the country code.
  • FIG. ID 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, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c.
  • 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).
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, 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., including 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, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPFs user plane functions
  • AMFs access and mobility management functions
  • the CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • AMF session management function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 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 NAS signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b, e.g., 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 ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • the AMF 162 may provide a control plane function for switching between the RAN 113 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 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 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 183 a, 183b may perform other functions, such as managing and allocating UE 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 110, e.g., 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 downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 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 115 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 115 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 WTRUs 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 any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/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. For example, 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 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.
  • RF circuitry e.g., which may include one or more antennas
  • traffic steering and switching over two 3 GPP access networks are provided.
  • support mechanisms for traffic steering are provided.
  • Switching and splitting between a 3GPP access network e.g., E-UTRA or NR
  • a non-3GPP access network e.g., WiFi
  • ATSSS Access Traffic Steering Switching and Splitting
  • mechanisms to support traffic steering and switching over two 3GPP access networks e.g., MASSS and/or DualSteer
  • various scenarios of one or more 3GPP access types e.g., NR, Non-Terrestrial NR, E-UTRA
  • one or more network types e.g., Home Public Land Mobile Network (HPLMN), Visiting PLMN (VPLMN), Public Network Integrated-Non- Public Network (PNLNPN)
  • HPLMN Home Public Land Mobile Network
  • VPN Visited PLMN
  • PNLNPN Public Network Integrated-Non- Public Network
  • a device which may be a WTRU may enable combined registration, based on triggers.
  • the device may determine combined registration configuration information.
  • Such information may include an access leg to be used as the primary access leg, and may also include authorization information.
  • the device may determine whether to send combined registration information, based upon triggers and conditions.
  • the triggers may trigger when to send registration, and conditions may define when to use single or combined registration.
  • the device may also determine a first leg to use for combined registration, and this may be based on the conditions.
  • the device may include new information in the combined registration, and this may include scenarios in which, for example, primary and secondary roles need to be swapped, where to receive responses from signaling exchanges with the network, which may be access leg 1 or access leg 2, timing information (e.g. when to perform the registration), and/or a NAS message which may contain the registration message of a second leg, or the Non-Access Stratum (NAS) container of leg 1 and leg 2.
  • NAS Non-Access Stratum
  • the device may also receive a combined registration accept message on a first leg.
  • This message may contain registration responses (which may be in separate NAS containers), one for each access leg.
  • This message may also contain policy configuration information associated with both legs and authorization information of each access leg.
  • the device may also forward the registration accept message to the second leg.
  • the conditions referenced above may include, for example, a Traffic Steering Decision, changes in device location, a notification from the application layer, and/or changes to the characteristics of any of the legs. For example, one leg might be out of coverage, while the other leg is in coverage. In another example, the network connected to one network is under congestion while the other may not be.
  • the conditions may also include a configuration message, e.g., UE Configuration Update or another NAS message, received from the network, signal quality of both access legs, load on both access legs, the RAT of each access leg, and/or the type of coordinated/combined signaling: the device may use separate signaling for certain procedures and combined signaling for other procedures.
  • a configuration message e.g., UE Configuration Update or another NAS message
  • the triggers referenced above may include, for example, a determination that the UE and/or user may change subscription associated to a UE (e.g., based on updates to subscription records in Unified Data Repository [UDR]), preconfiguration, e.g. the device may be preconfigured to coordinate its regi strati on/deregi strati on procedures.
  • the triggers may also include, for example, a configuration message, e.g., UE Configuration Update or another NAS message, received from the network, and/or dual-steer UE capability support for coordinated registration.
  • each access leg may perform a capability negotiation with the network, and may establish coordinated/combined signaling support for each leg.
  • the triggers may also include, for example, a configuration message or notification from the application layer, a need/condition to change the subscription associated with one access leg (for example such that a requirement that a subscription is to be swapped/transferred to another access leg may be met).
  • Other triggers may include, for example, in scenarios where multiple USIMs are supported by the device, a device (e.g. a WTRU) may determine to switch between the USIMs for better utlizing the resources, or Steering Mode rules.
  • a device e.g. a WTRU
  • a primary leg e.g. a primary UE
  • a secondary leg e.g. a secondary UE
  • the device may receive a policy which may dictate how to operate if a primary registration is registered.
  • the primary leg of the device may receive a deregistration message and may also receive an indication to keep secondary registration, time to keep secondary registration, indication to re-register on secondary registration, for example.
  • the device may also determine to maintain a secondary leg registration. This may, for example, be based on a primary registration message or a pre-configured policy.
  • the secondary leg of the device may send a registration message to the network.
  • the Subscription Permanent Identifier is a 5G globally unique identifier allocated to each subscriber.
  • the SUPI value is provisioned in Universal Subscriber Identity Module (USIM) and in Unified Data Management (UDM) and Unified Data Repository (UDR) functions in the 5G Core.
  • the SUPI can be either an International Mobile Subscriber Identifier (IMSI) or a Network Access Identifier (NAI).
  • IMSI International Mobile Subscriber Identifier
  • NAI Network Access Identifier
  • For the IMSI version of the SUPI the first three digits represent the Mobile Country Code (MCC), the next two or three represent the Mobile Network Code (MNC) identifying the network operator or Public Land Mobile Network (PLMN). The remainder represents the Mobile Subscriber identification number (MSIN).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • PLMN Public Land Mobile Network
  • Subscription Concealed Identifier is a privacy preserving identifier containing the concealed SUPI.
  • the SUCI includes the PLMN ID of the home network (in MCC and MNC).
  • the MCC/MNC are transmitted in plain text.
  • the 5G GUTI Globally Unique Temporary Identifier
  • the AMF may assign a new 5G-GUTI to the UE at any time.
  • the 5G-GUTI comprises a GUAMI (Globally Unique AMF ID) and a 5G-TMSI (Temporary Mobile Subscriber Identity), where GUAMI identifies the assigned AMF and 5G-TMSI identifies the UE uniquely within the AMF.
  • GUAMI is a concatenation of the PLMN ID and the AMF identifier.
  • FIG. 2 illustrates a UE Functional Model.
  • a UE is a device allowing a user access to network services.
  • the interface between the UE and the network is the radio interface.
  • the UE may be subdivided into a number of domains, the domains being separated by reference points.
  • the domains may include the Universal Subscriber Identity Module (USIM) and Mobile Equipment (ME) domains.
  • the ME Domain may be further subdivided into several components showing the connectivity between multiple functional groups, e.g., the Terminal Equipment (TE) and Mobile Termination (MT) domains.
  • TE Terminal Equipment
  • MT Mobile Termination
  • each MT in a dual-MT device may have a configuration for PLMN selection.
  • the configuration for PLMN selection may be independent.
  • the configuration may be stored in either MT or the USIM connected to the MT.
  • a status e.g., primary or secondary
  • the primary and/or secondary MT may be coordinated for automatic PLMN selection.
  • the primary MT may control the activation and/or deactivation of the secondary MT based on one or more criteria.
  • the primary MT may provide information (e.g., primary -registered-PLMN and/or RAT and/or frequency) to the secondary MT.
  • the information may guide a search for a PLMN and/or a RAT.
  • the information may guide selection of a PLMN and/or a RAT.
  • the primary MT may receive a list of available PLMN and/or RAT from the secondary MT.
  • the primary MT may give guidance to the secondary MT for PLMN selection.
  • the configuration (e.g., thresholds) and/or policy related to the Inter-MT coordination for PLMN selection may be provided by the HPLMN.
  • the primary MT may perform a combined mobility registration update and/or a periodical registration update.
  • the primary MT may provide the information of both primary and secondary MTs to the PLMN.
  • the primary MT may receive updated information for the secondary MT during the combined registration update procedure.
  • the primary MT may forward updated information to the secondary MT.
  • a dual-MT device is provided as two separate UEs.
  • each UE of a dual-MT device may function as a normal UE.
  • Each UE of the dual-MT device may, in some embodiments, function without adapting hardware, stacks and/or behaviors.
  • the dual-MT device may be configured to support Dual Steer simultaneous data transmission.
  • a dual-MT device that includes two separate MTs.
  • the dual MTs may be configured for inter-MT communication over one or more internal interfaces.
  • Each MT may be configured in a manner that emulates a UE.
  • coordination of the two UEs and/or two MTs is provided.
  • Enhancements and/or optimizations are provided to support one or more functionalities (e.g., for accessing a network and/or one or more services).
  • two UEs and/or MTs may be coordinated for cell and/or PLMN search and/or access.
  • two UEs and/or MTs may be optimized for mobility related procedures.
  • FIG. 3 is a diagram illustrating an example of a dual-MT WTRU device.
  • a dual-MT WTRU device may have two separate MTs and USIMs.
  • each MT may provide one or more functionalities that are in an MT of a UE (e.g., at least one of radio transmission, radio reception, baseband signal processing, access to USIM, access to CP stack (the control plane stack), access to UP stack (the user plane stack), combinations of the same, or the like).
  • a common TE may be provided (as shown, for example, in FIG. 3).
  • Two separate TEs corresponding to two MTs may be provided (not shown in FIG. 3).
  • An internal inter-MT interface between two MTs may be provided.
  • the internal inter-MT interface may be configured to allow two MTs to exchange information.
  • two MTs may exchange information through a higher layer (e.g., Layer 2 or Layer 3).
  • a system 300 may include a dual -MT WTRU device 302 configured to communicate with a first 3GPP access network 310 and/or a second 3GPP access network 320.
  • the dual -MT WTRU device 302 may be similar to WTRU 102a, 102b, 102c.
  • the dual -MT device 302 may include a first or primary MT 370 and a second or secondary MT 380.
  • the first or primary MT 370 and the second or secondary MT 380 may communicate, e.g., via an internal inter-MT interface 350.
  • the first or primary MT 370 may have a first USIM 375.
  • the second or secondary MT 380 may have a second USIM 385.
  • an Inter-MT Coordination Function (IMCF) 360 may be provided.
  • the IMCF 360 may be provided in the higher layer.
  • the IMCF 360 may be part of a TE 390.
  • the communication between MTs or between the MT and the IMCF 360 may use AT commands.
  • Two MTs may be identified by two unique device identifiers such as International Mobile Equipment Identities (IMEIs).
  • IMEIs International Mobile Equipment Identities
  • Such a device may be termed a Dual -MT device model and may have two separate Mobile Terminations (MTs) and USIMs, with each MT providing functionalities that are in a MT of a traditional UE, such as radio transmission/reception, baseband signal processing, access to USIM, CP/UP stacks, etc.
  • MTs Mobile Terminations
  • USIM Access Management Function
  • two separate TEs may be used, and the two TEs may correspond to two MTs.
  • There may be an internal inter-MT interface between two MTs, allowing two MTs to exchange information.
  • two MTs may exchange information through a higher layer “Inter-MT Coordination Function (IMCF)” 360.
  • IMCF Inter-MT Coordination Function
  • Two MTs may be identified by two unique device identifiers such as IMEIs.
  • An additional ID called DualSteer specific UE ID (DS-specific-UE-ID) may be used to interlink the Primary and Secondary MT 370, 380 in a dual-MT device.
  • Both of the MTs may have a separate subscription for registering to a mobile network.
  • a primary MT or UE may Register to a PMLN first, with the secondary MT or UE Registering subsequently.
  • the secondary MT or UE may Register only when it is triggered by the primary MT or UE (or leg) directly or via the IMCF layer.
  • a MT or UE (or leg) in a Dual Steer capable device e.g. dual-MT WTRU device 302
  • a DualSteer device may have two independent access legs, two UEs, or two independent MTs (one for each subscription).
  • leg, access leg, UE and MT may be used interchangeably.
  • a device may be a DualSteer device with 2 UEs. In some examples, a device may be a Dual Steer device with a single UE. In some examples, a device may be a DualSteer device with 2 MTs (e.g. a dual-MT WTRU device 302). In some examples a device may be a DualSteer device with a single MT.
  • the term ‘device’ may include a Dual Steer device with 2 UEs, a Dual Steer device with a single UE, a DualSteer device with 2 MTs, and/or a DualSteer device with a single MT.
  • the Dual Steer device has a single MT, in some examples the device may include stacks or instances of software for managing two connections or access legs.
  • the registration of these MTs or UEs may be managed independently, but the management procedures of the MTs or UEs may be impacted by the fact that both MTs or UEs are in the same device (e.g. dual-MT WTRU device 302). Such management procedures may be impacted by, for example, modified mobility management (including paging), triggers for secondary MT or UE registration, and/or network handling of secondary registration (e.g. access control, selection of AMF, authentication).
  • modified mobility management including paging
  • triggers for secondary MT or UE registration e.g. access control, selection of AMF, authentication
  • each UE may be deregistered independently by the network.
  • Examples of when such a network initiated deregistration event may occur may include: implicit deregistration timer for primary and/or secondary registration, O&M intervention, an AMF (access management function) determination that no Single-Network Slice Selection Assistance Information (S-NSSAI), which may be used to uniquely identify a network slice, can be provided in the Allowed Network Slice Selection Assistance Information (NSSAI) for the UE, an AMF determination that the MT or UEs registered PLMN is not allowed to operate in the present UE location, and/or an AMF determination that a disaster condition is no longer being applicable, allowing the return of UEs to the PLMN that had a Disaster Condition.
  • S-NSSAI Access Management Function
  • Each MT or UE of a device e.g. dual-MT WTRU device 302 with multiple MTs or UEs (or access legs) may perform its registration and deregistration to the network separately, despite the MTs or UEs being physically associated with the same user and the same device, thus resulting in two independent messages/procedures. This may lead to unnecessary control plane signaling and delays to services (e.g., mobility management).
  • Mobility Registration Update messages may be sent from both MTs or UEs (access legs) as a result of a changes in the user’s location. This may not only multiply the amount of control signaling, but it may also introduce unnecessary delays or disruptions to traffic/services (when registering separately, the two legs may register at two different times, despite being in the proximity to the new cells).
  • more than one subscription may be associated with a device (e.g. dual- MT WTRU device 302).
  • a first subscription may be associated with leg 1 (or MT1 or UE1)
  • a second subscription may be associated with leg 2 (or MT2 or UE2).
  • leg 1 may want to swap its subscription with the subscription associated with leg 2, or vice versa.
  • the first subscription may offer better connectivity and services, i.e., the characteristics of the connectivity and services offered may be a limit of the user’s subscription package, but if leg 1 (or MT1 or UE1) is not connected, is in an out-of-service, out- of-coverage, and/or unreliable condition, the first subscription may be allocated to leg 2 (or MT2 or UE2).
  • two subscriptions may be provided for DualSteer.
  • One subscription may be a main or primary subscription, which may be a fully-featured subscription, and may be allocated to leg 1.
  • the second subscription may have limited capabilities and may be a secondary subscription, and may be allocated to leg 2.
  • a scenario may arise where the main subscription of leg 1 has ongoing communication but is asked by the network to deregister or any of the conditions as described herein for the main leg or leg 1. In such a case, the device or the network may initiate the subscription swap.
  • the device may be able to switch between the USIMs for better utilizing the resources.
  • the terms ‘coordinated/combined signaling’, ‘coordinated signaling’, ‘combined signaling’, and ‘coordinated control plane signaling’ are used interchangeably. These terms may be used to represent signaling that is optimized for a DualSteer device, that is to say a device (e.g. dual-MT WTRU device 302) where one signaling exchange carries information for both UEs (or MTs) of the Dual Steer device.
  • coordinated/combined signaling examples include coordinated/combined registration and coordinated/combined deregistration.
  • Such an arrangement is in contrast to separate signaling (or single signaling) where the signaling for each UE is done independently - with a separate signaling exchange for each UE of a DualSteer device.
  • both legs are within the same device (e.g. dual-MT WTRU device 302)
  • a single regi strati on/procedure may be utilized for updating the registration status of both legs.
  • Described herein are procedures which may enable coordinated registration and deregistration for devices (e.g. dual-MT WTRU device 302) with multiple access legs, and may include procedures for sending registration and deregistration messages of both legs combined in a single leg, and procedures to handle scenarios where the primary UE/access leg gets deregistered by the network.
  • devices e.g. dual-MT WTRU device 302
  • procedures for sending registration and deregistration messages of both legs combined in a single leg and procedures to handle scenarios where the primary UE/access leg gets deregistered by the network.
  • the registration procedures described herein may enhance any of existing, Initial Registration to a network system (e.g., 5GS), Mobility Registration Update, Periodic Registration Update, Emergency Registration, Disaster Roaming Initial Registration, Disaster Roaming Mobility Registration Update, SNPN Onboarding Registration or any other registration.
  • the registration procedures are described on the basis that both access legs belong to the same PLMN. However this is only for exemplary purposes, and the concepts can be extended to the case where the access legs are in different PLMNs.
  • FIG. 4 illustrates an exemplary signaling diagram which shows procedures for coordinated registration.
  • both of the MTs/UEs/legs 402 associated with a device may register with the network. Such a registration may result in independent registration procedures from each of the access legs.
  • the device may inform the network that the first and second MTs/UEs/legs 402 belong to the same device (e.g. dual-MT WTRU device 302) and/or to the same user.
  • ‘primary’ and ‘secondary’ roles may be associated to the access legs within the same device (e.g. dual-MT WTRU device 302).
  • the network may indicate that the device (e.g. dual-MT WTRU device 302) may reregister with coordinated/combined registration capabilities.
  • This message may include configuration information that may be used for the coordinated regi strati on/deregi strati on procedures. For example, this may specify which access leg (of the first and second legs) may be used as the primary leg.
  • This message may include authorization information.
  • This message may include information of the subscription (e.g., SUPI) that may be used by each leg.
  • the device may have policies which indicate that the device (e.g. dual-MT WTRU device 302) may use a coordinated regi strati on/deregi strati on. This policy may apply also for the initial MT/UE/leg registration.
  • the policy may additionally include the access leg to use for the combined regi strati on/deregi strati on, or the conditions to check to determine the access leg to use for the combined regi strati on/deregi strati on.
  • One or more of the following conditions may be used by the device (e.g. dual-MT WTRU device 302) to determine the access leg to use for the combined regi strati on/deregi strati on.
  • the signal quality of each access leg may be determined based upon the access leg which has the best connection to the PLMN(s).
  • the RAT used by each access leg may be used to determine which access leg is to be used, because some RATs may be preferred, for example because they have better coverage.
  • the load on each access leg may be considered, and the access leg with the lower load may be selected.
  • a coordinated registration, registration update trigger or deregistration trigger may occur at the device (e.g. dual-MT WTRU device 302) or the network, such that the trigger prompts the device or the network to enable the coordinated registration and deregistration procedures among UEs’ access legs, in such a way that minimizes duplication and control signaling.
  • These triggers may be used by the device (e.g. dual-MT WTRU device 302) for deciding when to enable coordinated registration, as well as for deciding when to send the combined registration message.
  • trigger may include the following.
  • pre-configuration of a device e.g. dual-MT WTRU device 302
  • the device e.g. dual-MT WTRU device 302
  • the device e.g. dual-MT WTRU device 302
  • the trigger may be a configuration message, for example a UE Configuration Update or another NAS message, received from the network, such that the network may determine to configure devices (e.g. devices such as dual-MT WTRU device 302) with multiple access legs to coordinate to minimize control signaling (e.g., in an event of congestion).
  • devices e.g. devices such as dual-MT WTRU device 302
  • control signaling e.g., in an event of congestion
  • Such a configuration may, for example specify that multiple NAS containers, belonging to multiple access legs, may be included in the coordinated/combined control signals, and/or may specify that the device (e.g. dual-MT WTRU device 302) may re-register with the coordinated control signaling feature enabled.
  • the trigger may be dual-steer UE capability support for coordinated registration.
  • each access leg may perform a capability negotiation with the network, and may then establish coordinated/combined signaling support for each leg.
  • Changes in device may trigger the registration update or deregistration. Additionally, changes to the characteristics of any of the legs may also trigger such a registration update or deregistration. For example, one leg might be out of coverage, while the other leg is in coverage. In another example, the network connected to one network is under congestion while the other may not be.
  • the trigger may be configured/notified from the application layer.
  • the trigger may be a need or condition to change the subscription associated with one access leg is to be swapped/transferred to another access leg, such that the need is met.
  • the device e.g. dual-MT WTRU device 302
  • the device may determine to switch between the USIMs for better utilizing the associated resources.
  • the device e.g. dual-MT WTRU device 302
  • the device may always use combined signaling or it may make a decision per signaling message about whether to use separate signaling or combined signaling. If combined signaling is chosen, the device (e.g. dual-MT WTRU device 302) may also make a determination as to which access leg to use to carry the combined signaling.
  • the device e.g. dual-MT WTRU device 302) may rely on policy information or some configuration information from the network.
  • the device may make such a determination based on one or more of the following conditions.
  • the conditions may include, for example, device (e.g. dual-MT WTRU device 302) location, application layer preference, signal quality of both access legs, load on both access legs, RAT of each access leg, and/or the type of coordinated/combined signaling, such that the device (e.g. dual-MT WTRU device 302) may use separate signaling for certain procedures and combined signaling for other procedures.
  • the Unified Data Repository may be updated with information about the support for coordinated control plane signaling for the corresponding device, subscription, and/or user. This update may indicate that coordinated regi strati on/deregi strati on procedures are to be enabled.
  • the updated information gets populated at the Unified Data Management (UDM) 412, the Policy Control Function (PCF) 410, the Session Management Function (SMF) 408 and other Network Functions (NF) 414.
  • the PCF 410 may generate policy information (e.g., Policy and Charging Control (PCC) rules). This policy information may indicate that the device may enable coordinated registration/deregistration procedures.
  • PCC Policy and Charging Control
  • the UEs may then receive a configuration message from the 5G system.
  • the PCF 410 may configure the UEs for coordinated registration/deregistration.
  • Such a configuration message may be sent to the UE, via the AMF and N1 (NAS) interface.
  • This message may contain information of the access legs, and may contain information about subscriptions and roles that may associated with the access legs. The subscription and roles may be changed between access legs as described herein.
  • a NF 414 sends a configuration notification to the PCF.
  • This message may indicate that coordinated registration/deregistration procedures are to be enabled.
  • this may be a Network Exposure Function (NEF), where the message contains information received from an AF.
  • the PCF may generate policy information (e.g., PCC rules). This may indicate that the device may enable coordinated registration/deregistration procedures.
  • the UEs may receive a configuration message from the 5G system.
  • the PCF may configure the UEs for coordinated registration/deregistration.
  • This message may be sent to the UE, via the AMF 406 and N1 (NAS) interface.
  • This message may contain information of the access legs, and may contain information about subscriptions and roles that may associated with the access legs. The subscription and roles may be changed between access legs as described herein.
  • the device e.g. dualMT WTRU device 302 or a coordination function in the device may determine that coordinated registration/deregistration procedures are to be used, and may also determine that a reduced (e.g., only one) set of registration/deregistration procedures representing all or a subset of UEs/ Access Legs/MTs is to be used.
  • the device e.g. dualMT WTRU device 302) or coordination function in the device (e.g. dualMT WTRU device 302) may determine that the messages that were conventionally sent over multiple legs to be sent over a single or a reduced number of UEs.
  • the device may determine to use a separate NAS containers per each of leg 1 and leg 2. These NAS messages may be security protected.
  • the access legs within the device e.g. dualMT WTRU device 302 coordinates within the device (e.g. dualMT WTRU device 302) or the device (e.g. dualMT WTRU device 302) may determine the subscription to be associated with each leg.
  • the subscriptions associated with the access legs may be changed due to steering mode rules/decisions. For example, the primary and secondary legs may need to be swapped, as a result of traffic that has been swapped from one leg to the other.
  • the “primary” and “secondary” roles associated with the access legs may be changed due to steering mode rules/decisions.
  • the primary and secondary legs may need to be swapped as a result of traffic that has been swapped from one leg to the other.
  • the access legs within the device may coordinate within the device (e.g. dual-MT WTRU device 302), or the device (e.g. dual-MT WTRU device 302) may determine, that an access leg, for example access leg 2, is to be used for communicating the regi strati on/deregi strati on messages to the network combining registration/deregistration information of other access legs. This may be determined as a result of considering conditions in various scenarios, described above and in connection with in step 1 and may include, for example, mobility and/or subscription swapping.
  • the access legs within the device may coordinate within the device (e.g. dual-MT WTRU device 302) or the device (e.g. dual-MT WTRU device 302) may determine the ‘primary’ and ‘secondary’ roles assigned to the access legs. This may be determined considering conditions in various scenarios, described above and in connection with step 1 and may include, for example, connectivity characteristics and/or subscription. In an example, ‘primary’ and ‘secondary’ roles may be swapped.
  • Step 2 may also include the access legs within the device coordinating within the device (e.g. dual-MT WTRU device 302) or the device (e.g. dual-MT WTRU device 302) determining if existing protocol data unit (PDU) sessions or flows from one leg are to be moved to another access leg. For example, if leg 1 is determined to be out-of-coverage, PDU sessions of leg 1 may be moved to the access leg 2. Along with the PDU sessions, the subscription that was associated with leg 1 may also be transferred to leg 2.
  • PDU protocol data unit
  • the access leg 2 is chosen to send coordinated registration/deregistration procedures on behalf of one or more other access legs, may initiate registration/deregistration by sending a registration/deregistration message including registration information of leg 1.
  • This message may include the information about the access leg 1 in a separate NAS container.
  • the information about the access legs include: (new) roles associated with each leg, information of (new) subscription associated with each leg (e.g., SUPI), and/or timing information of when the registration/deregistration may be executed. This information may be sent to the RAN 404.
  • the information may include whether the following response to be sent to the same leg (leg 2 in this example), or to be sent their corresponding access legs (Registration response that belongs to the access leg 1 may be sent directly over the access leg 1, instead of leg 2).
  • the information may include information about the USIM that are associated with the access legs.
  • the UE may include in the List Of PDU Sessions To Be Activated, the PDU Sessions for which there are pending uplink data.
  • the UE may indicate PDU Sessions only associated with the access the Registration Request is related to.
  • the information may also include routing information for pending downlink data on each leg. For example, it may specify that pending downlink data of access leg 1 may be sent to leg 2. Additionally, the information may include any existing flows or PDU sessions that may be moved from one leg to another.
  • step 2 the device may determine different registration completion timing information associated with each leg.
  • step 3 the timing information associated with each leg may be included in the request.
  • the device e.g. dual-MT WTRU device 302
  • the device may determine that leg 2 may register effective now, while the registration of the leg 1 may be delayed until a certain condition is met (e.g., switching/migration of a set of flows has been successfully completed in leg 2).
  • the RAN may select, based on RAT(s) requested, suitable AMF(s) 406 for the requested access legs, and the coordinated control signaling capabilities of the UEs may be known to the AMF 406.
  • step 5 based on information received, the 5G system may authorize requested registration parameters (in step 3) per each access leg. This may occur at leg 2 of the device (e.g. dual-MT WTRU device 302), the RAN 404, and the AMF 406. Additionally, in step 5, authorization and other security procedures per each NAS container in the message may be carried out.
  • step 6 for the authorization of param eters/services associated with each access leg in the request, the AMF 406 may check with UDM 412 if there exists stored information associated with the UE and authorization information related to coordinated regi strati on/deregi strati on. This check may include the SMF and the PCF. This information may have been stored previously in the UDM 412. If there is no such information at the UDM 412, after authorizing with the AUSF, the authorized information may be stored in the UDM 412 to be used in the future.
  • the AMF 406 may select the PCF(s) 410 which supports access leg coordination and establishes UE policy association with the PCF for UE policy/parameter provisioning.
  • the PCF 410 may determine the policy information specific for each access leg and send it back to the UE as new policy or UE configuration updates, i.e., policy configurations (PCC rules) for both legs are sent to leg 2.
  • PCC rules policy configurations
  • access leg 2 may receive a Registration Accept message from the 5G system. This message may be received from the AMF 406 and may be a combined message including information of access legs that were specified in the registration request. This message may specify authorization information of all parameters of each access leg (both access leg 1 and access leg 2).
  • the Registration Accept message may contain policy configurations for both UEs.
  • the Registration Accept message may contain policy configurations for both UEs.
  • Responses that belong to other access legs may be sent via their corresponding access legs.
  • the Registration Accept response in step 8 may specify a time period (e.g., through a timer) the coordinated/combined control plane signaling may be valid for, and additionally the Registration Accept response in step 8 may specify a time period (e.g., through a timer) this registration may be valid for.
  • access leg 2 may forward the registration accept message associated with the leg 1 to the access leg 1 of the device (e.g. dual-MT WTRU device 302).
  • the device e.g. dual-MT WTRU device 302).
  • a WTRU (e.g. dual-MT WTRU device 302) is configured to enable combined registration of the first access leg and the second access leg based on a trigger.
  • the WTRU (e.g. dual-MT WTRU device 302) may determine to perform the combined registration of the first access leg and the second access leg based on at least one first condition being satisfied and identify the first access leg as a primary leg to use for the combined registration based on at least one second condition being satisfied.
  • the WTRU (e.g.
  • dual-MT WTRU device 302 may transmit, by the first access leg, registration data for the first access leg and for the second access leg, and receive by the first access leg, a message based on the registration data, wherein the message comprises first configuration data for the first access leg and second configuration data for the second access leg and wherein the first configuration data and the second configuration data comprise respective indications that the first access leg and the second access leg are registered.
  • the WTRU e.g. dual-MT WTRU device 302 may configure the first access leg based on the first configuration data, and configure the second access leg based on the second configuration data.
  • the trigger may comprise at least one of a determination that a subscription is to be changed, a preconfiguration for combined registration, a configuration message, updated capability support, Dual Steer connectivity support, a requirement to change a subscription from one access leg to another, a resource reallocation, load sharing, or steering mode rules.
  • the at least one first condition may comprise at least one of a change in location of the WTRU (e.g.
  • dual -MT WTRU device 302 load balancing, a change in coverage in one or both of the first and second access legs, the Radio Access Technology (RAT) in use on one or both of the first and second access legs, signal quality on one or both of the first and second access legs, a notification or configuration message received by the WTRU (e.g. dual- MT WTRU device 302), network congestion, or network coverage.
  • RAT Radio Access Technology
  • the WTRU (e.g. dual-MT WTRU device 302) may determine a combined registration configuration, and the combined registration configuration may comprise an indication of the first access leg being the primary leg.
  • the combined registration configuration may be determined by determining whether combined or coordinated registration of the first access leg and the second access leg is available.
  • the registration data may further comprise at least one of a request for the primary and secondary leg to be swapped, which of the first access leg or second access leg should receive the message based on the registration data, timing information, a message containing registration information for the first and second access legs, or a message containing registration information for the second access leg.
  • Configuring the second access leg may comprise communicating the second configuration data to the second access leg.
  • a WTRU may comprise a first mobile termination 370 and a second MT 390, and the WTRU (e.g. dual-MT WTRU device 302) may be configured to determine which of the first MT and the second MT is to be used the primary MT for a combined registration request and which of the first MT and the second MT is to be used as the secondary MT.
  • the WTRU e.g. dual-MT WTRU device 302 may transmit a combined registration request, the combined registration request including an indication of the primary MT to be used for the combined registration request and information about both the first MT and the second MT, and the WTRU (e.g.
  • dual-MT WTRU device 302 may receive, at the primary MT, a registration acceptance message.
  • the registration message may include a registration response, and the WTRU (e.g. dual-MT WTRU device 302) may provide, to the secondary MT, the registration acceptance message.
  • the combined registration request may be transmitted from the primary MT.
  • the combined registration request may be transmitted from the secondary MT.
  • the combined registration request may include a time for the combined registration to be effected.
  • the combined registration request may be transmitted to a Radio Access Network (RAN).
  • the registration acceptance message may be received from an Access and Mobility Management Function (AMF).
  • the WTRU e.g. dual-MT WTRU device 302 may determine whether to transmit a combined registration request. The determination whether to transmit a combined registration request may be based on a predetermined condition.
  • FIG. 5 illustrates an exemplary signaling diagram which shows procedures for coordinated deregistration.
  • access leg 1 is the primary access leg and that access leg 2 is the secondary access leg.
  • each leg may be an MT or a UE, and the terms leg, MT, and UE may be used interchangeably.
  • operation over access leg 2 is tailored to a UE using the access leg as a secondary leg. Examples of this tailored behavior include scenarios in which the UE is not paged over access leg 2, that UE over access leg 2 does not use an implicit deregister timer, or similar.
  • step 1 information related to the device (e.g. dual-MT WTRU device 302) and the access legs may be updated in the UDR 512 to revoke the support for coordinated/combined control plane signaling.
  • the configuration in UDM 412, PCF 410, SMF 408 and any other NF 414 may be updated with the feature revocation information.
  • the network may send a deregistration message to the access leg 1, to complete deregistration procedures and release connectivity to the access leg 1.
  • This message may be sent to the UE, from the AMF 406.
  • the deregistration message may include an indication to keep secondary registration, and may also provide a timer to say how long the secondary registration may be kept.
  • the device may determine what to do with the existing access leg. This determination may be based on a policy provided to the device (e.g. dual-MT WTRU device 302), related to secondary registration, and/or based on the information received in the deregistration message in step 1. Additionally, the device (e.g. dual-MT WTRU device 302) may determine to keep the secondary registration. The device (e.g. dual-MT WTRU device 302) may determine to keep the secondary registration but, re-register over leg 2 under a new configuration. If the device (e.g. dual-MT WTRU device 302) decides to keep the access leg 2 registered, it may follow the guidance as to how long this registration may be maintained (from policy or from step 1).
  • the device may determine that it is to change its subscription.
  • the leg 1 may be associated with the primary subscription, while the leg 2 may be associated with the secondary subscription. Due to the benefits in primary subscription, the device (e.g. dual-MT WTRU device 302) may determine to swap leg 2’s subscription to the primary subscription.
  • the subscriptions associated with the access legs may be changed due to steering mode rules. For example, the primary and secondary legs need to be swapped, due to traffic that has been swapped from one leg to the other.
  • the access leg 2 of the device and the network may use the registration procedures described above in connection with FIGS. 4 and 5. Furthermore, the leg 2 of the device (e.g. dual-MT WTRU device 302) (in the Registration Request) or the network (in the Registration Accept message) may specify that the new registration with new parameters (e.g., primary subscription) may be used by the device (e.g. dual-MT WTRU device 302) only for a limited time. [0175] Also in step 3, the leg 2 of the device (e.g. dual-MT WTRU device 302) or the network may specify that the new registration with new parameters (e.g., primary subscription) may be used by the device (e.g.
  • a Registration Update message may be sent from leg 2 of the device to the AMF 406. If this Registration Update message being sent is requested by the device (e.g. dual-MT WTRU device 302), this may be included in the Registration request. If this is a condition that the network providing to the device (e.g. dual-MT WTRU device 302), a Registration Accept message may be sent and this information may be included in the Registration Accept message. The Registration Accept message may be sent from the AMF 406 to leg 2 of the device (e.g. dual-MT WTRU device 302).
  • the network may send a deregistration message to the access leg 2 of the device (e.g. dual-MT WTRU device 302).
  • This message may be sent from leg 2 of the device to the AMF 406.
  • This message may be sent as described in connection with step 2.
  • This message may specify that access leg 1 or leg 2 or both may re-register with the network along with the conditions to be met by the device (e.g. dual-MT WTRU device 302) before sending the registration request(s), e.g., a timer value.
  • a WTRU may receive, by the first access leg, a deregistration message comprising an indication to deregister the first access leg, and determine to maintain a registration of the second access leg.
  • the WTRU may transmit, by the second access leg, a second message to register the second access leg.
  • the deregistration message may further comprise data indicative of what to do with the registration of the second access leg.
  • the determination to maintain the registration of the second access leg may be based on the deregistration message.
  • a WTRU may receive, at a first MT, a deregistration message requesting deregistration of the first MT from the registered network, deregister the first MT, determine whether to retain registration of the second MT, and maintain registration of the second MT.
  • the WTRU e.g. dual-MT WTRU device 302 may also receive a registration policy.
  • the registration policy may include information about the registration of the first MT. Maintaining the registration of the second MT may include transmitting a registration request for the second MT.
  • FIG. 6 illustrates an example of a process for coordinated registration of the first and second access legs.
  • a process 600 is performed by a WTRU (e.g., WTRU 102 of FIGS. 1 A-1D, dual-MT WTRU 302 of FIG. 3, multi- UE/leg/MT device 402 of FIGS. 4 and 5) in connection with a wireless network (e.g., RAN 104 and 113 of FIGS. 1A-D and/or core network 106 and 115 of FIGS. 1A-1D), which may be implemented in communications system 100 illustrated in FIG. 1 A-1D.
  • a wireless network e.g., RAN 104 and 113 of FIGS. 1A-D and/or core network 106 and 115 of FIGS. 1A-1D
  • the wireless network may include and/or be associated with at least one of a RAN (e.g., RAN 104 and 113 of FIGS. 1A-1D, RAN 404 of FIGS. 4 and 5); an AMF (e.g., AMF 182a and 182b of FIGS. 1A-1D, AMF 202 of FIG. 2, AMF 406 of FIGS. 4 and 5); a sensing NF (e.g., sensing NF 414 of FIG. 4); a UDM (e.g., UDM 412 of FIG. 4), combinations of the same; or the like.
  • a RAN e.g., RAN 104 and 113 of FIGS. 1A-1D, RAN 404 of FIGS. 4 and 5
  • an AMF e.g., AMF 182a and 182b of FIGS. 1A-1D, AMF 202 of FIG. 2, AMF 406 of FIGS. 4 and 5
  • a sensing NF e.g., sensing
  • the WTRU may enable combined registration of the first access leg and the second access leg based on a trigger.
  • the trigger may be, or may include, a variety of events and conditions, for example, a determination that a subscription is to be changed, or a preconfiguration for combined registration, or a configuration message, or updated capability support, or Dual Steer connectivity support.
  • Other trigger examples may be, or may include a requirement to change a subscription from one access leg to another or a resource reallocation, or load sharing, or steering mode rules.
  • the WTRU may determine to perform the combined registration of the first access leg and the second access leg, for example, based on a first condition being satisfied.
  • step 604 may correspond to, or be performed as part of, step 0 of FIG. 4.
  • a variety of conditions may constitute, or may server as one part of, the first condition.
  • the first condition may be, or may include, a change in location of the WTRU, a load balancing, a change in coverage in one or both of the first and second access legs, the Radio Access Technology (RAT) in use on one or both of the first and second access legs, signal quality on one or both of the first and second access legs, a notification or configuration message received by the WTRU, network congestion, or network coverage.
  • the WTRU may determine to request a combined registration configuration, the combined registration configuration including an indication that the first access leg is the primary leg.
  • the determining the combined registration configuration may include determining whether combined registration of the first access leg and the second access leg is available.
  • the WTRU may identify the first access leg as a primary leg to use for the combined registration based on at least one second condition being satisfied.
  • the WTRU may request that the primary leg and secondary leg be swapped.
  • the WTRU may request that an indication of which of the first access leg or second access leg should receive the message based on the registration data, timing information, a message containing registration information for the first and second access legs, or a message containing registration information for the second access leg.
  • the WTRU may transmit, via the first access leg, registration data for the first access leg and for the second access leg.
  • step 608 may correspond to, or be performed as part of, step3 of FIG. 4.
  • the WTRU may receive, via the first access leg, a message based on the registration data.
  • step 610 may correspond to, or be performed as part of, step 8 of FIG. 4.
  • Such a message may include first configuration data for the first access leg and second configuration data for the second access leg and wherein the first configuration data and the second configuration data includes respective indications that the first access leg and the second access leg are registered.
  • the WTRU configures the first access leg based on the first configuration data, and configures the second access leg based on the second configuration data.
  • step 612 may correspond to, or be performed as part of, step 9 of FIG. 4.
  • the configuring of the second access leg may entail communicating the second configuration data to the second access leg.
  • Other sequences of the steps outlined herein are also contemplated.
  • video or the term “imagery” may mean any of a snapshot, single image and/or multiple images displayed over a time basis.
  • the terms “user equipment” and its abbreviation “UE”, the term “remote” and/or the terms “head mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like.
  • WTRU wireless transmit and/or receive unit
  • any of a number of embodiments of a WTRU any of a number of embodiments of a WTRU
  • a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some
  • FIGs. 1A-1D Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1A-1D.
  • various disclosed embodiments herein supra and infra are described as utilizing a head mounted display.
  • a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.
  • the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor.
  • Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media.
  • 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).
  • 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.
  • processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit (“CPU”) and memory.
  • CPU Central Processing Unit
  • memory In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being “executed,” “computer executed” or “CPU executed.”
  • an electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals.
  • the memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.
  • the data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU.
  • the computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.
  • any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium.
  • the computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.
  • a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc.
  • a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities).
  • a typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
  • any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
  • the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
  • the terms “any of followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include “any of,” “any combination of,” “any multiple of,” and/or “any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items.
  • the term “set” is intended to include any number of items, including zero.
  • the term “number” is intended to include any number, including zero.
  • the term “multiple”, as used herein, is intended to be synonymous with “a plurality”.
  • a range includes each individual member.
  • a group having 1-3 cells refers to groups having 1, 2, or 3 cells.
  • a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes, des dispositifs et des produits programmes informatiques pour un enregistrement et un désenregistrement coordonnés pour des dispositifs/UE présentant de multiples branches d'accès, des messages d'enregistrement et de désenregistrement des deux branches étant envoyés de manière combinée dans une seule branche, avec des scénarios dans lesquels la branche d'accès/l'UE primaire est désenregistré par le réseau.
PCT/US2025/029617 2024-05-16 2025-05-15 Procédés et appareils d'enregistrement et de désenregistrement coordonnés de dispositifs qui communiquent à l'aide de deux branches d'accès ou plus Pending WO2025240776A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463648587P 2024-05-16 2024-05-16
US63/648,587 2024-05-16

Publications (1)

Publication Number Publication Date
WO2025240776A1 true WO2025240776A1 (fr) 2025-11-20

Family

ID=95981661

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/029617 Pending WO2025240776A1 (fr) 2024-05-16 2025-05-15 Procédés et appareils d'enregistrement et de désenregistrement coordonnés de dispositifs qui communiquent à l'aide de deux branches d'accès ou plus

Country Status (1)

Country Link
WO (1) WO2025240776A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8744437B2 (en) * 2009-08-25 2014-06-03 Zte Corporation Method for realizing user accessibility and multi-mode terminal
US20200068647A1 (en) * 2018-08-27 2020-02-27 Samsung Electronics Co., Ltd. Method and ue for optimizing resources of wireless communication network while providing 5g services
WO2021109031A1 (fr) * 2019-12-04 2021-06-10 华为技术有限公司 Procédé de communication, appareil de communication et système de communication
US20220303934A1 (en) * 2019-05-03 2022-09-22 Nec Corporation Core network node, ue, access network node and controlling method
US20230112588A1 (en) * 2020-06-12 2023-04-13 Huawei Technologies Co., Ltd. Communication method and related device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8744437B2 (en) * 2009-08-25 2014-06-03 Zte Corporation Method for realizing user accessibility and multi-mode terminal
US20200068647A1 (en) * 2018-08-27 2020-02-27 Samsung Electronics Co., Ltd. Method and ue for optimizing resources of wireless communication network while providing 5g services
US20220303934A1 (en) * 2019-05-03 2022-09-22 Nec Corporation Core network node, ue, access network node and controlling method
WO2021109031A1 (fr) * 2019-12-04 2021-06-10 华为技术有限公司 Procédé de communication, appareil de communication et système de communication
US20230112588A1 (en) * 2020-06-12 2023-04-13 Huawei Technologies Co., Ltd. Communication method and related device

Similar Documents

Publication Publication Date Title
KR20220050937A (ko) 무인 항공기에 의해 네트워크에 엑세스하기 위한 인증 및 인가
US12587819B2 (en) Methods, apparatus, and systems using closed access group (CAG) support in minimization of service interruptions (MINT)
EP4295633A1 (fr) Identifications d'applications multiples au moyen d'un relais de couche 3
WO2023146811A1 (fr) Procédés, architectures, appareils et systèmes pour prendre en charge une zone de desserte de découpage en tranches de réseau
WO2022216740A1 (fr) Continuité de service pendant une procédure de relocalisation de contexte d'application
CN119278646A (zh) 用于将数据业务流从蜂窝网络的边缘网络卸载到非蜂窝网络的方法、架构、装置和系统
EP4331291A1 (fr) Gestion de resélection de réseau pour un grand nombre d'utilisateurs
EP4544832A1 (fr) Contrôle d'accès à un réseau d'hébergement et gestion de congestion
EP4320833B1 (fr) Procédés, architectures, appareils et systèmes pour unifier un approvisionnement de serveur de configuration de bord
EP4500963A1 (fr) Sélection d'une route dans un système de communication sans fil
WO2021141983A1 (fr) Sélection et configuration de réseau permettant une mise en service à distance
WO2025240776A1 (fr) Procédés et appareils d'enregistrement et de désenregistrement coordonnés de dispositifs qui communiquent à l'aide de deux branches d'accès ou plus
US20250358647A1 (en) Methods, architectures, apparatuses and systems for protocol data unit session handover for dualsteer devices
US20260101174A1 (en) Methods, architectures, apparatuses and systems for associating usims with a dualsteer device
US20260046728A1 (en) Methods, architectures, apparatuses and systems for managing protocol data unit sessions for dualsteer capable devices
US20250317881A1 (en) Methods, architectures, apparatuses and systems for dual mobile termination
US20260046804A1 (en) Methods, architectures, apparatuses and systems for signaling reduction for dualsteer devices
WO2025212849A1 (fr) Procédés et appareils de gestion d'unité de données de protocole pour dispositifs aptes à une double orientation
WO2025213073A1 (fr) Procédés d'activation et d'authentification d'identifiant d'utilisateur
EP4690996A1 (fr) Sélection de réseau sensible à la tranche
WO2025175210A1 (fr) Association d'un utilisateur humain à un abonnement
WO2025212905A1 (fr) Identification d'un profil d'utilisateur et connexion à celui-ci
WO2026076415A1 (fr) Procédés, architectures, appareils et systèmes de sélection de réseau secondaire pour des dispositifs dualsteer
WO2025034999A1 (fr) Établissement d'une session pdu ma sur un accès
WO2025240854A1 (fr) Procédés, architectures, appareils et systèmes de partage de crédit d'énergie pour des dispositifs dualsteer

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

Country of ref document: EP

Kind code of ref document: A1