Method and apparatus for managing protocol data units of devices with dual-direction capability

By sending registration and PDU session requests in the communication system, identifying identifiers, and communicating based on business rule information, the complexity of the PDU session process in existing technologies is solved, achieving efficient wireless network connection and information transmission, and improving system compatibility and stability.

CN123077261APending Publication Date: 2026-11-10INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026577.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-04
Filing Date
2025-04-03
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In existing communication systems, the process of managing Protocol Data Unit (PDU) sessions for devices with dual-direction capabilities is complex and inefficient, making it difficult to achieve efficient transmission of business rule information and wireless network communication.

Method used

By sending registration requests and PDU session establishment requests to the wireless network, determining the associated identifier, and conducting communication during the PDU session based on service rule information, an effective connection and information transmission between the wireless transmitting/receiving units of the first and second user equipment and the wireless network is achieved.

Benefits of technology

It improves the efficiency and flexibility of PDU sessions, ensures the accurate transmission of business rule information and efficient management of wireless networks, and supports compatibility with multiple radio access technologies and the stability of communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077261A_ABST
    Figure CN123077261A_ABST
Patent Text Reader

Abstract

A process, method, architecture, apparatus, system, radio transceiver unit (WTRU), and computer program product are provided for establishing a Protocol Data Unit (PDU) session between a WTRU, including a first user equipment (UE) and a second UE, and a wireless network. The method includes sending a registration request to the wireless network to register the first and second UEs with the wireless network, determining an identifier associated with the device, and sending a PDU session establishment request to the wireless network, the PDU session establishment request including data indicating the identifier and information about the device or the PDU session. The method also includes the first UE receiving an indication that the PDU session is permitted and service rule information for the PDU session, providing the service rule information to the second UE, and communicating with the wireless network, in part, based on the service rule information, during the PDU session.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications This disclosure claims priority and interest in co-pending, co-assigned U.S. Provisional Patent Application No. 63 / 574,728, filed April 4, 2024, which is incorporated herein by reference in its entirety. Background Technology

[0002] This disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, apparatus, and systems related to managing protocol data units (PDUs) of devices with dual-steer capabilities. Summary of the Invention

[0003] In some representative embodiments, a method or process and related apparatus for establishing a PDU session between a radio transceiver unit (WTRU) including a first user equipment (UE) and a second UE and a wireless network includes: sending a registration request to the wireless network to register the first and second UEs with the wireless network; determining an identifier associated with the WTRU; and sending a PDU session establishment request to the wireless network, the PDU session establishment request including information indicating the identifier and characteristics of the WTRU or the PDU session. The method further includes the first UE receiving an indication that the PDU session is permitted and service rule information for the PDU session; providing the service rule information to the second UE; and communicating with the wireless network, in part, based on the service rule information, during the PDU session. Attached Figure Description

[0004] A more detailed understanding can be obtained through the following detailed description, given by way of example in conjunction with the accompanying drawings. Like the detailed description, the figures in these drawings are illustrative. Similarly, the drawings and detailed description should not be considered limiting, and other equally valid examples are possible. Furthermore, the same reference numerals ("ref") in the figures denote the same elements.

[0005] Figure 1A This is a system diagram showing an example communication system.

[0006] Figure 1B It shows that it can be done Figure 1A The system diagram shown is of an example WTRU used in the communication system.

[0007] Figure 1C It shows that it can be done Figure 1A The system diagram shows an example radio access network (RAN) and an example core network (CN) used in the communication system shown.

[0008] Figure 1D It shows that it can be done Figure 1AThe system diagram shows another example RAN and another example CN used in the communication system shown.

[0009] Figure 2 It shows that it can be done Figure 1A A block diagram illustrating an example of a dual mobile terminal (MT) model used in a communication system.

[0010] Figure 3 It is the process of associating a PDU session between two UEs using a public identifier called a dual-direction specific ID. This process can use Figure 1A The communication system shown is used to implement this.

[0011] Figure 4 This is a flowchart illustrating the process of establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown.

[0012] Figure 5 This is another flowchart illustrating the process of establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown.

[0013] Figure 6 This is an additional flowchart illustrating the process of establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown. Detailed Implementation

[0014] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that these embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, processes, components, and circuits have not been described in detail so as not to obscure the description below. Furthermore, embodiments and examples not specifically described herein may be practiced in place of or in combination with the embodiments and other examples expressly, implicitly, and / or inherently described, disclosed, or otherwise provided herein (collectively, the “Provided”). Although this document describes and / or claims various embodiments in which apparatuses, systems, WTRUs, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any part thereof, it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, WTRU, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any part thereof.

[0015] Exemplary communication system.

[0016] The methods, apparatus, and systems provided herein are well-suited for communications involving both wired and wireless networks. References Figure 1A-1D An overview of various types of wireless devices and infrastructures is provided, wherein various elements of the network can utilize, perform, be arranged according to, and / or be adapted and / or configured for use with the methods, apparatuses and systems provided herein.

[0017] Figure 1A This is a system diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. Communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. Communication system 100 enables multiple wireless users to access this content by sharing system resources, including wireless bandwidth. For example, communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Spread Spectrum OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0018] like Figure 1AAs shown, the communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, core network (CN) 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include / or be UEs, mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as UEs.

[0019] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or Network 112). For example, base stations 114a and 114b may be any of a base transceiver station (BTS), a node-B (NB), an evolved Node-B (eNB), a home node-B (HNB), a home eNode-B (HeNB), a next-generation Node-B (gNB), an NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, etc. Although base stations 114a and 114b are each described as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base station and / or network elements.

[0020] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0021] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0022] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish an 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).

[0023] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0024] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish air interface 116 using new radio (NR).

[0025] In this embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0026] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0027] For example, Figure 1ABase station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In embodiments, base station 114b and WTRUs 102c and 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In embodiments, base station 114b and WTRUs 102c and 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In embodiments, base station 114b and WTRUs 102c and 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of small cells, pico cells, or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, it is not required that base station 114b access Internet 110 via CN 106 / 115.

[0028] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses any of the following radio technologies: GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi.

[0029] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 114 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example... Figure 1A The WTRU 102c shown can be configured to communicate with a base station 114a that can use cellular-based radio technology and with a base station 114b that can use IEEE 802 radio technology.

[0031] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other components / peripherals 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing components while remaining consistent with the embodiments.

[0032] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding / decoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B While processor 118 and transceiver 120 are described as separate components, it should be understood that processor 118 and transceiver 120 may be integrated together in, for example, an electronic package or chip.

[0033] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector, for example, configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0034] Although the transmitting / receiving element 122 is in Figure 1B While described as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. For example, WTRU 102 may employ MIMO technology. Therefore, in an embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0035] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0036] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory (e.g., non-removable memory 130 and / or removable memory 132). Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., on a server or home computer (not shown)).

[0037] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for powering the WTRU 102. For example, the power supply 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, etc.

[0038] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0039] Processor 118 may be further coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units providing additional features, functions, and / or wired or wireless connectivity. For example, components / peripherals 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (e.g., for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Components / peripherals 138 may include one or more sensors, which may be gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

[0040] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with a specific subframe of both the uplink (e.g., for transmitting) and the downlink (e.g., for receiving)) 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 hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with a specific subframe of either the uplink (e.g., for transmitting) or the downlink (e.g., for receiving) may be concurrent and / or simultaneous.

[0041] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0042] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the embodiments, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and receive radio signals from WTRU 102a.

[0043] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink (UL) and / or downlink (DL). Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface. Figure 1C The CN 106 shown 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 is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0044] The MME 162 can connect to each eNode-B 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0045] The SGW 164 can connect to each eNode B 160a, 160b, or 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, or 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover; triggering paging when DL data is available for WTRUs 102a, 102b, or 102c; and managing and storing the context of WTRUs 102a, 102b, or 102c.

[0046] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks such as Internet 110, to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0047] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108 to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0048] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is contemplated that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network. In a representative embodiment, the other network 112 may be a WLAN.

[0049] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or peer into a distributed system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the AP via it. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be sent via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peering traffic. Peering traffic can be sent between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to as the "self-organizing" communication mode in this document.

[0050] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel (e.g., the primary channel). The primary channel can be of a fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example in an 802.11 system. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0051] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels.

[0052] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration described above can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

[0053] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV Blank (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS. According to a representative embodiment, 802.11ah may support metering-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., only supporting) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain very long battery life).

[0054] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by one of the STAs operating in the BSS that supports the minimum bandwidth operating mode. In the 802.11ah example, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example due to STAs (only supporting the 1MHz operating mode) sending to the AP, the entire available band can be considered busy, even if most of the band remains idle and may be available.

[0055] In the United States, the available frequency band for 802.11ah is from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0056] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0057] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the embodiments, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from WTRUs 102a, 102b, and 102c. Therefore, for example, gNB 180a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c can implement carrier aggregation (CA) technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c can implement coordinated multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0058] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including different numbers of OFDM symbols and / or continuously varying lengths of absolute time).

[0059] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without simultaneously accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can be used as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0060] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0061] Figure 1DThe CN 115 shown 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. Although each of the foregoing elements is described as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0062] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating non-access stratum (NAS) signaling, mobility management (MM), etc. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases (e.g., services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for MTC access, etc.). AMF 162 can provide control plane functions for handover between 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 Wi-Fi.

[0063] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0064] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This interface can provide WTRU 102a, 102b, and 102c with access to a packet-switched network (e.g., Internet 110), for example, to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-destination PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0065] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, WTRUs 102a, 102b, and 102c can be connected to local DNs 185a and 185b via UPFs 184a and 184b through the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0066] Given Figure 1A-1D as well as Figure 1A-1D As described herein, one or more of the functions described for any of the WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF183a-b, DN 185a-b, and / or any other component / device described herein can be performed by one or more emulation components / devices (not shown). An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0067] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform 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 to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing and / or testing purposes that can be performed using over-the-air wireless communication.

[0068] One or more emulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in test scenarios outside of deployment (e.g., testing) wired and / or wireless communication networks and / or test laboratories to implement testing of one or more components. One or more emulation devices may be test equipment. Emulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0069] Overview.

[0070] Session and mobility management.

[0071] WTRUs (e.g., WTRUs 102a, 102b, 102c, 102d) can provide both their Session Management (SM) and MM capabilities to the core network 106 / 115. WTRUs can send WTRU MM core network capability information to the AMF (e.g., AMF 182a, 182b) during the initial registration and mobility registration update processes; this WTRU MM core network capability information is sent in NAS messages. Furthermore, WTRUs (e.g., WTRUs 102a, 102b, 102c, 102d) can include their respective 5G Session Management (5GSM) core network capabilities in PDU session establishment / modification requests. Each PDU session establishment / modification request can include the respective WTRU's Access Service Orientation, Handover, and Detachment (ATSSS) capabilities.

[0072] In some corresponding embodiments, WTRUs 102a, 102b, 102c, and 102d perform registration with the network when accessing services that require registration. In some embodiments, the WTRU performs a method to perform this registration, which includes Public Land Mobile Network (PLMN) selection or Independent Non-Public Network (SNPN) selection, cell selection and / or reselection, and registration. The selection of the PLMN or SNPN can be performed by the WTRU to select a radio network. The radio network can be any suitable public or non-public network (NPN). In some embodiments, the WTRU (e.g., WTRUs 102a, 102b, 102c, and 102d) follows rules regarding how to select from available radio networks at a given location and when to seek a higher priority network. The cell selection and reselection process may include the WTRU "camping" or idle on the cell. In some embodiments, once one of the cell selection or reselection processes is completed, the WTRU may reselect into an idle mode. The WTRU may perform registration by notifying the radio network of its presence and providing some (e.g., procedures) location information, capability exchange, and negotiation.

[0073] Separate services across two 3GPP access tributaries.

[0074] In some examples, CA is provided on a single 3GPP access (e.g., NR or LTE), but the WTRU is allowed to receive on two or more cells, such that each cell is on a different frequency carrier. In some embodiments, the use of two cells is managed in RAN 104 / 113.

[0075] In some implementations, WTRUs 102a, 102b, 102c, and 102d may also support DC. DC allows the WTRU to receive and transmit on two 3GPP access points (or 3GPP access tributaries). The access points can be NR (e.g., when using a gNB) or LTE (e.g., when using an eNB). For 5G systems (5GS), the initial deployment has a first tributary on LTE and a second tributary on NR. However, current deployments of DC also support two tributaries on NR. In this case, the two tributaries can be on two different frequency bands (e.g., a first frequency and a second frequency). For WTRUs using DC, the RF front-end should support each access point. When the WTRU uses DC, one access tributary is the primary tributary, and the other is the secondary tributary. In some embodiments, the primary tributary is one of at least two primary tributaries in a primary cell group (MCG), and the secondary tributary is one of at least two secondary tributaries in a secondary cell group (SCG). In implementations using PLMN and / or NPN, each network can be managed by the same operator or different operators.

[0076] Service orientation and handover on the two 3GPP access networks.

[0077] 3GPP supports mechanisms that enable traffic orientation, handover, and decoupling between 3GPP access networks (e.g., Evolved UMTS Terrestrial Radio Access (E-UTRA) or NR) and non-3GPP access networks (e.g., WiFi). An example of such a mechanism is the ATSSS feature. 3GPP also includes mechanisms to support traffic orientation and handover between two 3GPP access networks by using WTRUs compatible with Multiple Access Orientation, Handover, and Decoupling (MASSS) or dual orientation.

[0078] A dual-directed WTRU can be defined as a WTRU that supports service redirection and handover of user data across two 3GPP access networks. In some corresponding embodiments, a dual-directed WTRU is one of the following: (a) a single WTRU in the case of non-simultaneous data transmission on two networks, and (b) two separate WTRUs in the case of simultaneous data transmission on two networks. Each dual-directed WTRU may correspond to a subscriber of the dual-directed WTRU, wherein the subscriber of the dual-directed WTRU has two subscriptions and / or subscription permanent identifiers (SUPIs) that share a subscription profile from the same operator of the access network (AN). For any particular service, at any given time, the dual-directed WTRU can use (e.g., only) a single 3GPP access network to transmit all services for that service. In some implementations, different models can be used to define the dual-directed WTRU, for example, a model including two separate control plane / user plane (CP / UP) stacks, with an additional dual-directed control layer within a single MT block. Similarly, in some implementations, a dual-MT WTRU model can include a dual-MT WTRU with two separate MTs and two separate USIMs, where each MT provides the functions of the WTRU's MT, such as radio transmission / reception, baseband signal processing, access to the USIM, and the CP / UP stack. An internal inter-MT interface may exist between the two MTs, enabling them to exchange information. Alternatively, the two MTs can exchange information through an Inter-MT Coordination Function (IMCF) layer. Each of the two MTs can be identified by its own unique WTRU identifier, such as an International Mobile Equipment Identity (IMEI). Various implementations exist for the two 3GPP access types (e.g., NR, non-terrestrial NR, E-UTRA) and network types (e.g., Home PLMN (H-PLMN), Visited PLMN (V-PLMN), and PNI-NPN) connected to the 3GPP access network.

[0079] A WTRU can be considered dual-directed when it meets at least one of the following conditions: (1) the WTRU uses two SUPIs from the same operator to access two separate 3GPP access networks, and each SUPI is used to connect to (e.g., only) one of the 3GPP access networks; (2) the WTRU can transmit its user data through two 3GPP access networks belonging to the same PLMN, wherein the user data is transmitted non-simultaneously or simultaneously; and (3) the WTRU can transmit its user data through two 3GPP access networks belonging to two different PLMNs, wherein the user data is transmitted non-simultaneously or simultaneously. In the implementation of non-simultaneous data transmission through two networks, the dual-directed WTRU can be a single WTRU. In the implementation of simultaneous data transmission, the dual-directed WTRU can include two separate WTRUs. In some corresponding embodiments of performing simultaneous data transmission, the data on the two separate networks should belong to different services or different service data flows (SDFs). At any given point in time, traffic for a single service (e.g., all) can be transmitted through a single access network, therefore the WTRU does not perform service data separation.

[0080] WTRU identity.

[0081] The SUPI is a globally unique 5G identifier assigned to each subscriber. The SUPI value is provided in the Universal Subscriber Identity Module (USIM) and Unified Data Management (UDM) and / or User Data Repository (UDR) functions within the 5G core. The SUPI can be either the International Mobile Subscriber Identifier (IMSI) or the Network Access Identifier (NAI). In implementations that include an IMSI version of the SUPI, the first three digits represent the Mobile Country Code (MCC), the next two or three digits represent the Mobile Network Code (MNC), which identifies the network operator or PLMN, and the remaining digits represent the Mobile Subscriber Identifier Number (MSIN).

[0082] A Subscription Hidden Identifier (SUCI) is a privacy-preserving identifier that includes a hidden SUCI. In some embodiments, the SUCI includes the home network's PLMN ID, which includes the MCC and MNC. In some corresponding embodiments, the MCC and MNC are transmitted in plaintext.

[0083] A 5G Globally Unique Temporary Identifier (GUTI) is assigned by the AMF (e.g., AMF 182a, 182b). In some corresponding embodiments, the AMF (e.g., AMF 182a, 182b) can assign a new 5G-GUTI to the WTRU at any time. The 5G-GUTI includes a globally unique AMF ID (GUAMI) and a 5G Temporary Mobile Subscriber Identity (TMSI), where the GUAMI identifies the assigned AMF, and the 5G-TMSI identifies a unique WTRU within the AMF (e.g., AMF 182a, 182b). In some embodiments, the GUAMI is defined by a concatenation of the PLMN ID and the AMF identifier.

[0084] Multiple USIM (MUSIM) operations.

[0085] In some corresponding embodiments, the WTRU may have multiple USIMs operating simultaneously, where each USIM allows the WTRU to obtain services from a different wireless network. An example use case for the MUSIM WTRU is for professionals using both a business number and a separate personal number. In such examples, these professionals use a single WTRU with two USIMs instead of carrying two WTRUs (e.g., a telephone).

[0086] The terminal behavior that may involve processing multiple USIMs simultaneously depends on the WTRU's capabilities. Some example WTRUs include (1) a WTRU with a single receiver (Rx) and a single transmitter (Tx), (2) a WTRU with two Rxes and a single Tx, and (3) a WTRU with two Rxes and two Txes. In some implementations, each dual Rx enables the MUSIM WTRU to receive traffic from two networks simultaneously, each single Rx enables the MUSIM WTRU to receive traffic from one network at a time, and each single Tx allows the MUSIM WTRU to transmit traffic to one network at a time.

[0087] In some embodiments, the two USIMs of the MUSIM WTRU operate independently of each other. In some implementations, the WTRU has a dedicated NAS and access layer protocol stack for each of the two USIMs. However, depending on the capabilities of the WTRU, some coordination can be implemented to allow the WTRU to obtain services from both wireless networks. This coordination does not depend on wireless network interaction, thus the WTRU acts as an intermediary between the two wireless networks.

[0088] In this article, subscriptions to two network operators via MUSIM WTRU are referred to as "dual subscriptions," while each subscription to a network operator without involving MUSIM WTRU is referred to as a "single subscription."

[0089] Mobility between PLMNs.

[0090] In some corresponding embodiments, the AMF (e.g., AMF 182a, 182b) uses the N14 interface for AMF reallocation and AMF-to-AMF information transfer. The N14 interface can be implemented within or between PLMNs (e.g., in the case of inter-PLMN mobility). In some embodiments, the handover process can allow inter-PLMN mobility, and this handover process includes a source AMF that can select at least one AMF instance in the target PLMN by querying the target PLMN-level Network Repository Function (NRF) via the source PLMN-level NRF having the target PLMN ID. The target PLMN-level NRF then returns the AMF instance address based on the target operator configuration. Once the handover process is complete, the source AMF can choose a different target AMF.

[0091] Dual MT WTRU model.

[0092] Figure 2 A dual-MT WTRU model 200 with dual-MT WTRU 202 is shown. The dual-MT WTRU 202 may include two separate mobile terminals (MTs) (e.g., primary MT 208 and secondary MT 210) and two separate USIMs (e.g., primary USIM 212 and secondary USIM 214). Each MT (e.g., primary MT 208 and secondary MT 210) provides functions within the MT of the WTRU, such as radio transmission / reception, baseband signal processing, access to the USIM, and the CP / UP stack. In some implementations of the dual-MT WTRU 202, a common terminal equipment (TE) 218 ​​may be present (e.g., ...). Figure 2 (as shown) or two separate TEs ( Figure 2 (Not shown in the diagram), where each of the two individual TEs corresponds to one of the two MTs (e.g., primary MT 208 and secondary MT 210). In some corresponding embodiments, the dual MT WTRU 202 may include an internal inter-MT interface 215 between each of the two MTs (e.g., primary MT 208 and secondary MT 210), wherein the inter-MT interface 215 allows the two MTs (e.g., primary MT 208 and secondary MT 210) to exchange information with each other. Alternatively, the two MTs (e.g., primary MT 208 and secondary MT 210) may exchange information via an IMCF layer 216. Each corresponding MT in primary MT 208 and secondary MT 210 may be identified by a corresponding unique WTRU identifier, such as an IMEI. In other embodiments, an additional ID called a dual-direction specific WTRU ID (DS-specific WTRU ID) may be used to interconnect the primary MT 208 and secondary MT 210 in the dual MT WTRU 202.

[0093] Each of the primary MT 208 and the secondary MT 210 has a separate subscription for registering to a wireless network (e.g., a first network 204 or a second network 206). In some embodiments, the primary MT 208 may register to the PLMN first, and the secondary MT 210 may register (e.g., register only) directly by the primary MT 208 or triggered via the IMCF 216. Furthermore, a WTRU in a dual-direction capability may include information from either the primary MT 208 or the secondary MT 210 as part of a WTRU registration request message sent to the network.

[0094] MASSS or dual-directed WTRUs support service redirection and handover of user data across two 3GPP access networks for different services. In some implementations, a dual-directed WTRU can transmit its user data across two 3GPP access networks belonging to the same PLMN or different PMLNs, where the user data is transmitted asynchronously or simultaneously.

[0095] In implementations of a dual-directed WTRU using non-simultaneous data transmission over two networks, the dual-directed WTRU can be a single WTRU. In implementations of a dual-directed WTRU using simultaneous data transmission over two networks, the dual-directed WTRU can have two separate WTRUs and two USIMs, where each corresponding WTRU corresponds to a corresponding USIM. In some implementations of a dual-directed WTRU with two WTRUs, the WTRUs are either cooperatively located or can be physically separated but communicatively coupled (e.g., interconnected). In some embodiments of the MUSIM WTRU, the two USIMs in the WTRU operate independently of each other.

[0096] For a dual-directed WTRU with two WTRUs or a single WTRU with two stacks or two MTs, no SM is specified, especially if some coordination is assumed between WTRUs within the WTRU.

[0097] In some corresponding embodiments, a method is used to implement PDU session management for a dual-directed WTRU (e.g., dual-directed WTRU 202) having two WTRUs (e.g., primary MT 208 and secondary MT 210), wherein each WTRU can be registered on two 3GPP access types (e.g., NR, non-terrestrial NR, E-UTRA) and network types (e.g., H-PLMN, V-PLMN, PNI-NPN), which associates the PDU sessions of the two WTRUs by using a public identifier called a dual-directed specific ID (which is used to associate WTRUs within the same dual-directed WTRU). This disclosure addresses PDU session establishment in scenarios where coordination between Network Functions (NFs) is achieved using a common dual-direction specific ID, and two WTRUs can register at: (a) the same PLMN, where the SMF uses information of the primary WTRU (e.g., primary MT 208) or secondary WTRU (e.g., secondary MT 210) and / or the common dual-direction specific ID to associate the PDU sessions of the two WTRUs; or (b) different PLMNs, where NFs in different PLMNs exchange information of the primary WTRU (e.g., primary MT 208) or secondary WTRU (e.g., secondary WTRU 210) and / or the common dual-direction specific ID to associate the PDU sessions of the two WTRUs. In some embodiments, a new PDU session type, referred to as dual-direction with a cooperating WTRU type, is implemented for dual-direction WTRUs (e.g., dual-direction WTRU 202). This new PDU session type includes connections to two 3GPP tributaries on the same or different wireless networks, using a separate subscription for each WTRU of the dual-direction WTRU.

[0098] This PDU session management enables the dual-direction WTRU 202 to establish associated PDU sessions for two WTRUs (e.g., primary MT 208 and secondary MT 210) within the dual-direction WTRU 202. Furthermore, this association between WTRUs (e.g., primary MT 208 and secondary MT 210) allows for seamless redirection and switching of services (e.g., user data) between WTRUs (e.g., primary MT 208 and secondary MT 210), both for roaming and implementation (e.g., WTRUs connected to H-PLMN and V-PLMN) and for non-roaming implementation (e.g., WTRUs connected to at least one H-PLMN).

[0099] In some corresponding embodiments, a dual-direction WTRU (e.g., dual-direction WTRU 202) with two WTRUs (e.g., primary MT 208 and secondary MT 210) uses a dual-direction-specific WTRU ID (e.g., a public DS-specific WTRU-ID) to interconnect the primary WTRU (e.g., primary MT 208) and the secondary WTRU (e.g., secondary MT 210) to the network during initial registration and associates each PDU session of the two WTRUs. In some implementations, the dual-direction-specific ID is configured at the IMCF layer (e.g., IMCF layer 216) based on the application or service being used and provided to the WTRU. In other implementations, during the mobility registration process, the dual-direction-specific ID is configured by an NF (e.g., an AMF or a Policy Control Function (PCF)) in either the primary WTRU (e.g., primary MT 208) or the secondary WTRU (e.g., secondary MT 210), and the dual-direction-specific ID is exchanged internally between the WTRUs. In some implementations, the dual-direction specific ID is preset (e.g., pre-configured) on a WTRU with dual-direction capability (e.g., dual-direction WTRU202). In other implementations, the dual-direction specific ID is provided by one of the applications in one of the WTRUs and one of the application servers on the application layer (e.g., UP).

[0100] In some corresponding implementations, the PDU session is established on a dual-directed WTRU 202, where (e.g., only) the primary WTRU registers with the network (e.g., a 3GPP access network), and the secondary WTRU registers with the network in response to an internal signal (e.g., a trigger) indicating the establishment of a PDU session for the secondary WTRU. Alternatively, each of the primary and secondary WTRUs may register with the network, but (e.g., only) the primary WTRU establishes the PDU session first, and the secondary WTRU waits for a signal (e.g., a trigger) from the primary WTRU for PDU session establishment. In an alternative implementation, each WTRU performs simultaneous registration with the network, and a separate PDU session is established for each WTRU simultaneously using a public ID (e.g., a dual-directed specific ID that could be a public PDU session ID) as part of the PDU session establishment process, such that the network can identify that the PDU sessions of WTRUs are linked to the same WTRU (e.g., dual-directed WTRU 202). In another implementation, the primary WTRU (e.g., primary MT 208) includes an indicator signal to enable network-triggered PDU session establishment for the secondary WTRU (e.g., secondary MT 210) in response to the indicator signal. In this implementation, the network is configured to send a WTRU (e.g., dual-directed WTRU 202) indicator signal (e.g., a trigger message) to at least one application on the secondary WTRU (e.g., secondary MT 210). In some embodiments, the indicator signal (e.g., a WTRU trigger request) includes a payload message comprising (a) a dual-directed specific ID, (b) information about the primary WTRU (e.g., primary MT 208) that requests or configures network-triggered PDU session establishment, and (c) information about when to perform PDU session establishment for the secondary WTRU (e.g., secondary MT 210). Once the secondary WTRU receives the indicator signal, it performs the PDU session establishment process based on the information included in the payload message of the indicator message (e.g., the WTRU trigger request).

[0101] PDU session establishment for dual-guided WTRU and two UE models.

[0102] Figure 3 The procedure 300 or method shown illustrates the association of two UE PDU sessions using a common dual-direction specific ID, which can be used... Figure 1A The communication system shown is used to achieve this. As previously mentioned, PDU session establishment is performed by the UE (e.g., Figure 3The request is made by one of the primary UE 301 and secondary UE 303 shown in the diagram, or by two UEs in a dual-directed WTRU (e.g., dual-directed WTRU 202). In some embodiments, primary UE 301 includes primary MT 208 and primary USIM 212, and secondary UE 303 includes secondary MT 210 and secondary USIM 214. In some embodiments, each UE (e.g., primary UE 301 and secondary UE 303) registers to a different AMF belonging to the same network (e.g., PLMN). In some implementations, primary UE 301 and secondary UE 303 register to different networks (e.g., PLMN), thus establishing a communication link (e.g., coordination) between the NFs (e.g., AMF, PCF) of the two PMLNs to associate the UEs of dual-directed WTRU 202 (e.g., primary UE 301 and secondary UE 303) with their respective PDU sessions. The aforementioned PDU session establishment procedure also applies to the PDU session modification (e.g., release) procedure.

[0103] If a dual-direction specific ID is configured for a UE (e.g., primary UE 301 and secondary UE 303) before registering to their respective AMFs (e.g., first AMF 304a and second AMF 304b), then each corresponding UE (e.g., primary UE 301 and secondary UE 303) within a dual-direction WTRU (e.g., dual-direction WTRU 202) provides the corresponding UE information and dual-direction specific ID. The AMFs (e.g., first AMF 304a and second AMF 304b) can exchange the corresponding UE information and dual-direction specific ID with each other. For example, first AMF 304a sends primary UE 301 information and dual-direction specific ID to second AMF 304b (e.g., by using a Namf_Communicate_CreateUEContext message or a Namf_UpdateUEContext message, and vice versa). In some embodiments, one of the first AMF 304a and the second AMF 304b can send information to the UDM 310, so that when a UE associated with the other of the first AMF 304a and the second AMF 304b initiates registration, the other of the first AMF 304a and the second AMF 304b retrieves that information. In some implementations, the primary UE 301 and the secondary UE 302 use the same AMF, therefore Figure 3 The first AMF 304a and the second AMF 304b shown can be replaced by a single AMF.

[0104] For PDU session establishment, each of the primary UE 301 and secondary UE 303 can send its respective UE information to its respective SMF 306, such as UE ID, PDU session type, support services for the dual-directed WTRU, and the dual-directed specific ID in the PDU session establishment request message. In some embodiments, such as Figure 3 As shown, each of the primary UE 301 and secondary UE 303 uses the same SMF 306 for PDU session establishment.

[0105] In other implementations, two UEs (e.g., primary UE 301 and secondary UE 303) use two different SMFs, such as a first SMF and a second SMF. In these implementations, the two SMFs can exchange information, such as UE ID, supporting services, service PLMN information, and dual-direction specific IDs, to associate the PDU sessions of each of primary UE 301 and secondary UE 303, and can also select the same DN (e.g., UPF) for data services. In some embodiments, when exchanging information, the first SMF can invoke one of the following, for example, the Nsmf_PDUSession_Update service operation to the second SMF for direct information exchange between the two UEs (e.g., primary UE 301 and secondary UE 303), or indirectly via an AMF (e.g., one of the first AMF 304a and the second AMF 304b) through a service operation (e.g., Namf_Communication_N1N2MessageTransfer), or via a UPF through a setup and / or modification operation (e.g., N4 session). Associating PDUs from each of the two UEs (e.g., primary UE 301 and secondary UE 303) will facilitate the management of PDU sessions, for example, when at least one of primary UE 301 and secondary UE 303 requires PDU session modification and release.

[0106] In step 314, at least one of the primary UE 301 and secondary UE 303, along with their respective USIMs within the dual-direction WTRU 202, register with the network, indicating the dual-direction capability of the WTRU. Each UE (e.g., primary UE 301 and secondary UE 303) is configured with an ID, such as SUPI, GUTI, 5G-GUTI, or any suitable identifier. For example, primary UE 301 may register first, determining a public identifier called a dual-direction-specific ID, and then triggering secondary UE 303's registration. During the initial registration of one of the primary UE 301 and secondary UE 303, a dual-direction-specific ID for linking primary UE 301 and secondary UE 303 to each other may be assigned, for example, a DS-specific WTRU-ID of a public PDU session ID. In some embodiments, during the mobility registration process in at least one of the primary UE 301 and secondary UE 303, the dual-direction-specific ID may be configured by an NF (e.g., first AMF 304a, second AMF 304b, PCF 308). If the primary UE 301 (e.g., alone) receives a DS-specific WTRU-ID, then the UEs (e.g., primary UE 301 and secondary UE 303) internally exchange the DS-specific WTRU-ID with each other before the PDU session is established.

[0107] In step 316, for a PDU session establishment requested by a UE (e.g., by the primary UE 301 or secondary UE 303, or both UEs in the dual-direction WTRU 202), a dual-direction specific ID is determined and selected by one of the IMCF 216, the primary UE 301, and the secondary UE 303. The dual-direction specific ID can be one of the following: (1) an application layer ID, (2) a service-specific ID, (3) a public PDU session ID, (4) a public key set identifier negotiated between the respective UE (e.g., the primary UE 301 and secondary UE 303) and the network in step 316, or an identifier that can be assigned by the network, and (5) the SUPI of the primary UE 301 and secondary UE 303 used together. The determination of the dual-direction specific ID is based on the desired service to be used, and the dual-direction specific ID is selected from a list of configured IDs. In some embodiments, the dual-direction specific ID is configured at initial registration or pre-configured in a WTRU with dual-direction capability (e.g., preset on the dual-direction WTRU 202). The dual-direction specific ID may be (1) derived at IMCF layer 216 based on the support service or application, or (2) received from the application server from previous communications for use in the support service based on the capability of dual-direction WTRU 202, and the dual-direction specific ID is stored at the UE (e.g., primary UE 301 and secondary UE 303).

[0108] In step 318, the primary UE 301 sends a PDU session establishment request to the first AMF 304a. In some embodiments, the PDU session establishment request may include any one or more of the following: (1) PDU session-related information of the primary UE 301, (2) the dual-direction specific ID selected in step 316, (3) dual-direction capability, and (4) a PDU session type set to, for example, "DS PDU session with cooperating UE". This disclosure includes (e.g., new) PDU session types for the dual-direction WTRU 202, such as dual-direction with cooperating UE, which involves connecting to two 3GPP tributaries on the same or different networks using separate subscriptions for each WTRU. The WTRU with dual-direction capability has two USIMs, each associated with one of the primary UE 301 and the secondary UE 303. For example, the first USIM of the primary UE 301 is connected to a first network, while the second USIM of the secondary UE 303 is connected to a second network. The radio networks may be the same or different (e.g., H-PLMN or V-PLMN). The (e.g., new) PDU session type of the dual-directed WTRU 202 can further classify dual-directed WTRUs for simultaneous or non-simultaneous data transmission, such as dual-directed for simultaneous traffic and cooperative UEs, and dual-directed for non-simultaneous traffic and cooperative UEs. In some embodiments of step 318, the second AMF 304b is an AMF that receives a request.

[0109] In step 320, when dual-direction capability and / or dual-direction specific ID are provided in the request (e.g., PDU session establishment request), the first AMF 304a, which received the request in step 318, checks where the relevant information is stored locally and / or in a public repository (e.g., in the UDM / UDR (e.g., UDM 310)) and whether the dual-direction specific ID is already linked to any PDU session or another UE. If the first AMF 304a does not find any associated dual-direction specific ID, the first AMF 304a may store the relevant information locally and report the relevant information to the UDM / UDR (e.g., UDM 310). When the dual-direction specific ID is already linked to any PDU session or another UE, the first AMF 304a selects the (e.g., the same) SMF associated with the already linked dual-direction specific ID (e.g., SMF 306). If the dual-direction specific ID is not yet linked to any PDU session or another UE, the first AMF 304a may select an SMF with dual-direction capability (e.g., SMF 306). In some embodiments, each of the primary UE 301 and secondary UE 303 attempts to establish a PDU session simultaneously and registers on different AMFs. In this embodiment, step 320 may (e.g., only) be used to select SMF 306. Step 320 is performed when both the primary UE 301 and secondary UE 303 are registered to the same AMF (e.g., one of the first AMF 304a and the second AMF 304b). When each of the primary UE 301 and secondary UE 303 is registered to a different AMF (e.g., the first AMF 304a and the second AMF 304b), process 300 proceeds to step 322. In some embodiments of step 322, the second AMF 304b is the AMF for which the request was received in step 318.

[0110] In step 322, the first AMF 304a, which received the request in step 318, can pass the information of the first UE 301, along with the associated dual-direction specific ID, dual-direction capability, and UE ID (e.g., the 5G-GUTI used in the second AMF 304b), to the second AMF 304b (e.g., using the Namf_UpdateUEContext request and response message). Therefore, the second AMF 304b knows that another UE (e.g., primary UE 301) belonging to the same dual-direction WTRU 202 exists. If the second AMF 304b receives a PDU session establishment request from the other UE (e.g., primary UE 301), the second AMF 304b can select the same SMF 306 associated with the primary UE 301. In some embodiments, based on the receipt of the PDU session establishment request in step 318, the first AMF 304a may transmit information about the primary UE 301, along with the associated dual-direction specific ID, dual-direction capability, and UE ID (e.g., the 5G-GUTI used in the second (e.g., another) AMF 304b), to the UDM 310. In some embodiments, the dual-direction specific ID and its association with the corresponding UE (e.g., primary UE 301 and secondary UE 303) are updated in the UDM 310. The UDM 310 also provides notification to the subscribed AMFs or all AMFs with dual-direction capability for dual-direction, and, for example, the second AMF 304b stores the dual-direction specific ID and the associated SUPI so that it can be used at a later time to associate a dual-direction PDU session with another UE (e.g., primary UE 301). In an alternative embodiment, step 322 may be performed after receiving a response (e.g., Nsmf_PDUsession_CreateSMContext) from the SMF 306.

[0111] In step 324, the first AMF 304a selects an SMF 306 with dual-direction capability and sends a PDU session establishment request (e.g., an Nsmf_PDUsession_CreateSMContext request) which includes a dual-direction specific ID, a dual-direction PDU type, and dual-direction capability.

[0112] In step 326, SMF 306 can perform an SM policy association establishment procedure using a dual-direction specific ID, dual-direction PDU type, and dual-direction capability to receive policy and charging control (PCC) rules for a PDU session with a dual-direction capability WTRU (e.g., dual-direction WTRU 202). If the PDU session establishment request is for secondary UE 303, and primary UE 301 has already established a PDU session using the same dual-direction specific ID, SMF 306 initiates (e.g., if needed) an SM policy association modification procedure, assuming secondary UE 303 already has an SM policy association for the requested PDU session. In some embodiments, importance values ​​can be associated with each of primary UE 301 and secondary UE 303. For example, an application can use a PDU session through secondary UE 303 to send higher-priority data, resulting in (e.g., requiring) corresponding QoS processing from the network, while primary UE 301 is used for lower-priority data. These importance values ​​for each UE can be included in the received PCC rules.

[0113] In step 328, SMF 306 sends an (e.g., N4 session) establishment and / or modification request to UPF 312, providing packet detection, enforcement, and reporting rules for the dual-direction PDU session to be installed on UPF 312, and providing a dual-direction specific ID, a dual-direction service-specific rule, and at least one associated PDU session ID. If two UEs (e.g., primary UE 301 and secondary UE 303) do not establish a PDU session with the same SMF 306, UPF 312 may pass the rules to the SMF 306 of secondary UE 303 when secondary UE 303 reports the same dual-direction specific ID during PDU session establishment. UPF 312 confirms the passing of rules to SMF 306 by sending an N4 session establishment response, which in some embodiments may include indications and / or information about the PDU session of primary UE 301.

[0114] In step 330, the PDU session establishment accept message is relayed to the secondary UE 304. In some embodiments, the SMF 306 sends a PDU session request (e.g., N2) to the RAN 302 via the AMF, wherein the PDU session request includes (1) an acknowledgment allowing a dual-direction PDU session, (2) dual-direction specific service rules, which may include the association of a service with each PDU session and whether the PDU session is dedicated to a specific service type, QoS and Quality of Experience (QoE) parameters for each PDU session, and / or information to help the dual-direction WTRU select a PDU session based on traffic volume, and (3) an associated dual-direction specific ID. The dual-direction service rules may include QoS rules for each PDU session of the two UEs (e.g., primary UE 301 and secondary UE 303). In some corresponding embodiments, the QoS rules are explicit for each service PDU session of each UE within the dual-direction WTRU 202, for each UE of primary UE 301 and secondary UE 303. The dual-direction service rule is sent to the primary UE 301, but applies to the dual-direction WTRU 202 that hosts the primary UE 301.

[0115] In step 332, RAN 302 may publish an AN-specific signaling exchange with secondary UE 303, wherein the AN-specific signaling exchange is related to information received from SMF 306. Additionally, primary UE 301 receives dual-direction specific rules from RAN 302.

[0116] In step 334, the primary UE 301 transmits the dual-direction specific service rule received in step 332 to the secondary UE 303. In some embodiments, the primary UE 301 sends the dual-direction specific service rule directly to the secondary UE 302. In other embodiments, the primary UE 301 sends the dual-direction specific service rule via the IMCF coordination layer 216. If two UEs (e.g., primary UE 301 and secondary UE 303) attempt to establish a PDU session simultaneously, the IMCF layer 216 can later synchronize information between the two UEs once both PDU sessions have been established.

[0117] In step 336, the secondary UE 303 requests PDU session establishment using the same procedure 300 discussed for the primary UE 301 in steps 316-334. The request for PDU session establishment includes the same information (e.g., as described in 318): (1) PDU session-related information of the secondary UE 303, (2) the dual-direction specific ID selected in step 316, (3) dual-direction capability, and (4) the PDU session type set to, for example, "DS PDU session with cooperating UE". In some embodiments, in step 332, the procedure of step 336 can use dual-direction specific service rules received by the primary UE 301 from RAN 302 to establish the session.

[0118] When procedure 300 is used for secondary UE 303, the second AMF 304b and SMF 306 can determine, based on the dual-direction specific ID, that secondary UE 303 is associated with another UE (e.g., primary UE 301) on the same dual-direction WTRU 202. Upon making this determination, the second AMF 304b and SMF 306 can select the same SMF 306, associate using the same SM policy as for primary UE 301, and link the PDU session to select the same UPF 312.

[0119] exist Figure 3 In the provided example, primary UE 301 initiates PDU session establishment first, and then triggers secondary UE 303 to initiate PDU session establishment. In another example, each PDU session establishment of primary UE 301 and secondary UE 303 can be performed simultaneously.

[0120] In the above example, it is assumed that the first AMF 304a and the second AMF 304b (and the SMF (e.g., SMF 306)) belong to the same PLMN. In some embodiments, each of the two UEs (e.g., primary UE 301 and secondary UE 303) of the dual-directed WTRU 202 attempts to establish a PDU session on the respective PLMNs of two different PLMNs. Therefore, a new interface can be enabled to exchange information between the respective AMFs (e.g., the first AMF 304a and the second AMF 304b) and / or the respective SMFs (e.g., at least one of the first SMF and the second SMF) located in different PLMNs.

[0121] PDU session modification and release for dual-directed WTRU and dual-MT models.

[0122] The procedure 300 disclosed for establishing a PDU session for a dual-directed WTRU 202 and two UE models can also be used for PDU session modification and release procedures. However, for modification and release procedures, there may be additional parameters (e.g., enhancements) specific to the modification or release procedure, wherein the additional parameters (e.g., enhancements) are provided to the UE (e.g., primary UE 301 and secondary UE 303) as part of the dual-directed specific service rules when the PDU session is established.

[0123] For example, in the case of a dual-direction WTRU 202, both UEs have established PDU sessions, and the two PDU sessions are associated and / or bound using a dual-direction specific ID. In some embodiments, the two PDU sessions have the same PDU session ID. When the intent is to modify or release both PDU sessions, the PDU session modification and / or release process may use information including dual-direction capability, dual-direction specific ID, and at least one PDU session ID. When the PDU session modification and / or release is intended (e.g., only) for one of the two PDU sessions, the PDU session modification request or release request (e.g., only) includes the UE ID, dual-direction capability, and PDU session ID of the PDU session targeted by the request (e.g., the PDU session modification or release request). In some embodiments, the PDU session modification or release request does not include the dual-direction specific ID.

[0124] When two PDU sessions (e.g., a first PDU session and a second PDU session) are linked using a dual-direction specific ID, if the first PDU session is released for any reason (e.g., in response to a PDU session release request), the second PDU session may be modified (e.g., detached from the dual-direction associated PDU session, or delinked) in response to the release of the first PDU session, or it may also be released. In some embodiments, the second PDU session may also be released in response to the release of the first PDU session, depending on the policy. In an alternative implementation, a first UE that has already established a first PDU session triggers a second UE with a released second PDU session (e.g., directly or via IMCF 216) to initiate a PDU session establishment for the second UE.

[0125] Figure 4 This is a flowchart of the illustrative procedure 400 for establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown.

[0126] In step 402, the WTRU sends a registration request to the wireless network to register a first UE and a second UE with the wireless network, where the first UE is the primary UE.

[0127] In a 404 error, WTRU identifies the identifier associated with WTRU.

[0128] In step 406, the WTRU sends a PDU session establishment request to the wireless network, wherein the PDU session establishment request includes information indicating an identifier and at least one characteristic of at least one of the WTRU or the PDU session.

[0129] At 408, the first UE receives the service rule information of the PDU session.

[0130] At 410, the WTRU provides the second UE with the service rule information of the PDU session.

[0131] In 412, each of the first UE and the second UE communicates with the wireless network during the PDU session, at least in part, based on the service rule information of the PDU session.

[0132] Figure 5 This is another flowchart of the illustrative procedure 500 for establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown.

[0133] At 502, the AMF receives a PDU session establishment request from the first US, wherein the first UE is the primary UE, and the PDU session establishment request includes information indicating an identifier associated with the WTRU, and at least one feature of at least one of the WTRU or PDU session.

[0134] In 504, the AMF determines whether the identifier associated with the WTRU is linked to at least one other PDU session or a second UE.

[0135] In 506, the AMF selects the SMF based on the determination of whether the identifier associated with the WTRU is linked to at least one other PDU session or a second UE.

[0136] At 508, AMF sends a PDU session establishment request to SMF.

[0137] At 510, the AMF receives the service rule information of the PDU session.

[0138] At 512, the AMF sends the service rule information of the PDU session to the first UE.

[0139] In 514, the first UE and the second UE of the WTRU communicate with the wireless network at least in part based on the service rule information of the PDU session during the PDU session.

[0140] Figure 6 This is an additional flowchart of the illustrative procedure 600 for establishing a PDU session using a WTRU, which can be used... Figure 2 This is achieved using the dual MT WTRU shown.

[0141] At 602, the SMF receives a PDU session establishment request from the AMF, wherein the first UE is the primary UE, and the PDU session establishment request includes information indicating an identifier associated with the WTRU, and at least one feature of at least one of the WTRU or PDU session.

[0142] In 604, the SMF performs the SM policy association establishment process based on information indicating the identifier associated with the WTRU and at least one characteristic of the WTRU and the PDU session to generate business rule information for the PDU session.

[0143] In 606, the SMF sends a session request to the UPF, wherein the session request includes business rule information and information indicating an identifier associated with the WTRU, and at least one characteristic of one or both of the WTRU and PDU sessions.

[0144] At 608, the SMF receives an acknowledgment response from the UPF, which includes information about the PDU session.

[0145] In 610, the SMF sends the service rule information of the PDU session to the AN, which is communicatively coupled to the WTRU.

[0146] In 612, the first UE and the second UE of the WTRU communicate with the wireless network at least in part based on the service rule information of the PDU session during the PDU session.

[0147] In some corresponding embodiments, a release request is received from the AN. If the release request is network-triggered and the two PDU sessions are linked using a dual-direction-specific ID, the release request from the network may (e.g., only) include the dual-direction-specific ID, thereby allowing a higher layer (e.g., IMCF layer 216, TE 218, or the application layer) to determine which PDU session to release. This allows the UE of the dual-direction WTRU 202 to perform application-layer adjustments and release the PDU session with minimal service disruption.

[0148] Although features and elements have been provided above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in combination with other features and elements. This disclosure is not limited to the specific embodiments described herein, which are intended to illustrate various aspects. Many modifications and changes can be made without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. No element, action, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly provided so. Based on the foregoing description, functionally equivalent methods and apparatuses within the scope of this disclosure will be apparent to those skilled in the art, in addition to those listed herein. Such modifications and changes are intended to fall within the scope of the appended claims. This disclosure is limited only by the terms of the appended claims and the full scope of their equivalents. It should be understood that this disclosure is not limited to specific methods or systems.

[0149] For simplicity, the foregoing embodiments have been discussed regarding the terminology and structure of devices with wireless communication capabilities (e.g., radio wave transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (e.g., sound waves).

[0150] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" can refer to any one of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" and its abbreviation "HMD" can mean or include (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of several embodiments of a WTRU; (iii) a device configured with some or all of the structure and functions of a WTRU and having wireless and / or wired capabilities (e.g., tetherable); (iv) a device configured with fewer than all the structure and functions of a WTRU and having wireless and / or wired capabilities; or (iv) and so on. References herein Figure 1A-1D Details of an example WTRU, representative of any WTRU described herein, are provided. As another example, the various embodiments disclosed above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays can be utilized, and some or all of this disclosure and the various disclosed embodiments can be modified accordingly without excessive experimentation. Examples of such other devices may include drones, or other devices configured to stream information to provide an adaptive, realistic experience.

[0151] Furthermore, the methods provided herein can be implemented in computer programs, software, or firmware, which are included in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital versatile discs (DVDs). The processor associated with the software can be used to implement an RF transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0152] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the wide variety of applicable embodiments, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the appended claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source, such as a battery, which provides any suitable voltage.

[0153] Furthermore, in the embodiments provided above, references to processing platforms, computing systems, controllers, and other devices, including processors, are mentioned. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions may be referred to as “executed,” “computer-executed,” or “CPU-executed.”

[0154] Those skilled in the art will understand that the actions and symbols representing operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits that can result in the eventual transformation or reduction of electrical signals and are held at memory locations in the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0155] Data bits may also be stored on computer-readable media, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage systems. Computer-readable media may include cooperative or interconnected computer-readable media that reside exclusively on the processing system or are distributed among multiple interconnected processing systems that may be located locally or remotely to the processing system. It should be understood that the embodiments are not limited to the memories described above, and other platforms and memories may support the provided methods.

[0156] In the illustrative embodiments, any operations, processes, etc., described herein may be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions may be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0157] There is little difference between the hardware and software implementations of various aspects of the system. The use of hardware or software is often (but not always; in some cases, the choice between hardware and software may become important) a design choice representing a cost-efficiency trade-off. Various means can be used to implement the processes and / or systems and / or other technologies described herein (e.g., hardware, software, and / or firmware), and the preferred means can vary depending on the context of the deployment of the processes and / or systems and / or other technologies. For example, if the implementer determines that speed and accuracy are of paramount importance, the implementer may choose a primarily hardware and / or firmware approach. If flexibility is of paramount importance, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0158] The foregoing detailed description has illustrated various embodiments of the devices and / or processes using block diagrams, flowcharts, and / or examples. Within the scope of such block diagrams, flowcharts, and / or examples, which include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation in such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by various hardware, software, firmware, or virtually any combination thereof. In embodiments, several portions of the subject matter described herein can be implemented using application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be implemented, in whole or in part, equivalently in an integrated circuit, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or virtually any combination thereof, and that designing circuitry and / or writing code for software and / or firmware in accordance with this disclosure will be entirely within the skill of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as various forms of program products, and the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc.; and transmission media, such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0159] Those skilled in the art will recognize that it is common practice in the field to describe devices and / or processes in the manner set forth herein, and then integrate such described devices and / or processes into data processing systems using engineering practice. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable number of experiments. Those skilled in the art will recognize that a typical data processing system typically includes one or more of the following: a system unit housing, a video display device, a memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, drivers, a graphical user interface and applications, one or more interactive devices such as a touchpad or screen, and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0160] The topics described herein sometimes illustrate different components included within or connected to different other components. It should be understood that the architectures described in this way are merely examples, and many other architectures can indeed be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to enable the desired functionality. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associating can also be considered “operably connected” or “operably coupled” with each other to achieve the desired functionality, and any two components that can be so associating can also be considered “operably coupled” with each other to achieve the desired functionality. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0161] Regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately translate them from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural substitutions may be clearly illustrated herein.

[0162] Those skilled in the art will understand that, generally, the terminology used herein and especially in the appended claims (e.g., the body of the appended claims) is intended to be “open” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will further understand that if a particular number of claims is intended to be recited, such intention will be explicitly stated in the claims, and if such recitation is not present, such intention does not exist. For example, the term “single” or similar language may be used when only one item is intended. To aid understanding, the appended claims and / or the description herein may include the use of introductory phrases “at least one” and “one or more” to introduce claims. However, the use of such phrases should not be construed as implying that a claim recitation introduced by the indefinite article "a" or "an" limits any particular claim that includes such a recitation to only one embodiment of that recitation, even when the same claim includes the introductory phrase "one or more" or "at least one" along with an indefinite article (e.g., "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). This also applies to the use of definite articles used to introduce a claim recitation. Furthermore, even if the specific number of recitations in an introduced claim is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as indicating at least a number of recitations (e.g., the simple statement "two recitations" without other modifiers indicates at least two recitations, or two or more recitations). Moreover, in cases where conventions such as "at least one of A, B, and C" are used, this structure is generally intended to make the recitation easier for those skilled in the art. Those skilled in the art will understand that conventions (e.g., "a system having at least one of A, B, and C" will include, but are not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.) are acceptable. In the use of conventions similar to "at least one of A, B, or C," this structure is generally intended to make the conventions understandable to those skilled in the art (e.g., "a system having at least one of A, B, or C" will include, but are not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Those skilled in the art will further understand that, whether in the specification, claims, or drawings, any separate words and / or phrases that represent two or more optional terms should be understood to account for the possibility of including one of the terms, any one of the terms, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B."Furthermore, as used herein, the term "any" followed by a list of multiple items and / or multiple item categories is intended to include, individually or in combination with other items and / or other item categories, "any," "any combination," "any number," and / or "any combination of multiples." Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "quantity" is intended to include any quantity, including zero. And as used herein, the term "multiple" is intended to be synonymous with "plural."

[0163] Furthermore, in cases where features or aspects of this disclosure are described in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is also described in accordance with any individual member or subgroup of the Markush Group.

[0164] As those skilled in the art will understand, for any and all purposes, such as providing a written description, all scopes disclosed herein also include any and all possible subscopes and combinations thereof. Any listed scope can be readily considered adequately described and capable of being divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, a middle third, and an upper third, etc. Those skilled in the art will also understand that all language such as “up to,” “at least,” “greater than,” “less than,” etc., includes the listed numbers and refers to a scope that can subsequently be decomposed into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1-3 units means a group having 1, 2, or 3 units. Similarly, a group having 1-5 units means a group having 1, 2, 3, 4, or 5 units, and so on.

[0165] Furthermore, the claims should not be construed as limited to the order or elements provided, unless otherwise stated. Additionally, the use of the term "means for..." in any claim is intended to refer to 35 USC §112, ¶ 6 or the claim format of means plus function, and any claim without the term "means for..." is not.

Claims

1. A method for establishing a Protocol Data Unit (PDU) session between a Radio Transmit / Receive Unit (WTRU) including a first User Equipment (UE) and a second UE and a wireless network, the method comprising: Send a registration request to the wireless network to register the first UE and the second UE with the wireless network, wherein the first UE is the primary UE; Determine the identifier associated with the WTRU; Send a PDU session establishment request to the wireless network, wherein the PDU session establishment request includes information indicating an identifier and at least one characteristic of at least one of the WTRU or PDU session; The first UE receives the service rule information for the PDU session; Provide the second UE with service rule information for the PDU session; and Each of the first UE and the second UE communicates with the wireless network during a PDU session based at least in part on service rule information for the PDU session.

2. The method according to claim 1, wherein, At least one characteristic of either a WTRU or a PDU session includes information indicating the WTRU's WTRU capabilities and the PDU session type.

3. The method according to claim 2, wherein, Information indicating the WTRU's capabilities includes information indicating the WTRU's dual-direction capability.

4. The method according to claim 2 or 3, wherein, The PDU session type is a bidirectional PDU session.

5. The method according to any one of claims 1 to 4, wherein, Business rule information includes Quality of Service (QoS) rules used for PDU sessions.

6. The method according to any one of claims 1 to 5, wherein, Receiving business rule information for a PDU session includes receiving an indication that a PDU session is permitted.

7. A method for establishing a Protocol Data Unit (PDU) session between a Radio Transmit / Receive Unit (WTRU) including a first User Equipment (UE) and a second UE and a wireless network to which the WTRU is registered, the wireless network including an Access and Mobility Management Function (AMF), and the method comprising: The AMF receives a PDU session establishment request from a first UE, wherein the first UE is the primary UE, and the PDU session establishment request includes information indicating an identifier associated with the WTRU and at least one characteristic of at least one of the WTRU or PDU session; The AMF determines whether the identifier associated with the WTRU is linked to at least one other PDU session or a second UE; The Session Management Function (SMF) is selected by the AMF based on whether the identifier associated with the WTRU is linked to at least one other PDU session or a second UE. The AMF sends a PDU session establishment request to the SMF; The AMF receives service rule information for the PDU session; The AMF sends service rule information for the PDU session to the first UE; and The first and second UEs of the WTRU communicate during the PDU session, based at least in part on the service rule information used for the PDU session.

8. The method according to claim 7, wherein, At least one characteristic of either a WTRU or a PDU session includes information indicating the WTRU's WTRU capabilities and the PDU session type.

9. The method according to claim 8, wherein, Information indicating the WTRU's capabilities includes information indicating the WTRU's dual-direction capability.

10. The method according to claim 8 or 9, wherein, The PDU session type is a bidirectional PDU session.

11. The method according to any one of claims 7 to 10, wherein, Each of the first UE and the second UE is registered with the AMF.

12. The method according to any one of claims 7 to 11, wherein, The AMF is a first AMF to which the first UE registers, and a second UE registers to a second AMF, and the method further includes: The information of the first UE and the identifier of the associated WTRU are passed from the first AMF to the second AMF.

13. The method according to any one of claims 7 to 12, wherein, Business rule information includes Quality of Service (QoS) rules used for PDU sessions.

14. The method according to any one of claims 7 to 13, wherein, The selection of the Session Management Function (SMF) based on the determination of whether the identifier associated with the WTRU is linked to at least one other PDU session or a second UE includes: In response to determining that the identifier associated with the WTRU is linked to at least one other PDU session or a second UE: Select the first SMF associated with at least one other PDU session or a second UE; and In response to determining that the identifier associated with the WTRU is not linked to at least one other PDU session or a second UE: Select a second SMF that can be associated with more than one PDU session.

15. A method for establishing a Protocol Data Unit (PDU) session between a Radio Transmit / Receive Unit (WTRU) including a first User Equipment (UE) and a second UE and a wireless network to which the WTRU is registered, the wireless network including an Access Network (AN), Access and Mobility Management Functions (AMF), and Session Management Functions (SMF), and the method comprising: The SMF receives a PDU session establishment request from the AMF, wherein the first UE is the primary UE, and the PDU session establishment request includes information indicating an identifier associated with the WTRU, and at least one feature of at least one of the WTRU or PDU session; The SMF performs a session management (SM) policy association establishment process based on information indicating an identifier associated with the WTRU and at least one characteristic of at least one of the WTRU or PDU sessions to generate business rule information for PDU sessions; The SMF sends a session request to the User Plane Function (UPF), the session request including business rule information and information indicating an identifier associated with the WTRU and at least one characteristic of at least one of the WTRU or PDU sessions; The SMF receives an acknowledgment response from the UPF, the acknowledgment response including information about the PDU session; The SMF sends service rule information for PDU sessions to the AN, which is communicatively coupled to the WTRU. and The first and second UEs of the WTRU communicate during the PDU session, based at least in part on the service rule information used for the PDU session.

16. The method according to claim 15, wherein, At least one characteristic of either a WTRU or a PDU session includes information indicating the WTRU's WTRU capabilities and the PDU session type.

17. The method according to claim 16, wherein, Information indicating the WTRU's capabilities includes information indicating the WTRU's dual-direction capability.

18. The method according to claim 16 or 17, wherein, The PDU session type is a bidirectional PDU session.

19. The method according to any one of claims 15 to 18, wherein, Business rule information includes Quality of Service (QoS) rules used for PDU sessions.

20. A wireless transmit / receive unit (WTRU) including a first user equipment (UE) and a second UE, wherein the WTRU is configured to: Send a registration request to the wireless network to register the first UE and the second UE with the wireless network, wherein the first UE is the primary UE; Determine the identifier associated with the WTRU; Sending a Protocol Data Unit (PDU) session establishment request to a wireless network, wherein the PDU session establishment request includes information indicating an identifier and at least one characteristic of at least one of a WTRU or a PDU session; The first UE receives the service rule information for the PDU session; Provide the second UE with service rule information for the PDU session; and Each of the first UE and the second UE communicates with the wireless network during a PDU session based at least in part on service rule information for the PDU session.

21. The WTRU according to claim 20, wherein, At least one characteristic of either a WTRU or a PDU session includes information indicating the WTRU's WTRU capabilities and the PDU session type.

22. The WTRU according to claim 21, wherein, Information indicating the WTRU's capabilities includes information indicating the WTRU's dual-direction capability.

23. The WTRU according to claim 21 or 22, wherein, The PDU session type is a bidirectional PDU session.

24. The WTRU according to any one of claims 20 to 23, wherein, Business rule information includes Quality of Service (QoS) rules used for PDU sessions.

25. The WTRU according to any one of claims 20 to 24, wherein, In order to receive service rule information for PDU sessions, WTRU is configured to receive indications that allow PDU sessions.