Method, architecture, apparatus and system for device association over direct communication for aggregated devices

Abstract

Programs, methods, architectures, apparatus, systems, devices, and computer program products for artificial intelligence specific idle / inactive / connected mode measurement programs. In an embodiment, a method implemented by a wireless transmit receive unit (WTRU) includes: receiving a first message containing aggregation related information from a network component; registering with a network component indicating capability / availability with respect to aggregation of the plurality of WTRUs; receiving a second message containing registration acceptance information for aggregation from the network component; and establishing side link communication with the plurality of WTRUs.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 410,699, filed on September 28, 2022, which is incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, and systems for device association over direct communications for aggregated devices. Background Art

[0004] The device-to-device (D2D) direct communication protocol enables two devices to communicate directly between themselves with or without the help of the network. There are different scenarios for D2D communication depending on whether the wireless transmitter / receiver units (WTRUs) involved are within the coverage of the cellular network. In 3GPP, Release 16 introduced the 5G NR Sidelink (SL), enabling neighboring devices to communicate directly without the need for data packets to pass through the 3GPP network. Target applications may include mission-critical services, V2X services, and Industrial Internet of Things (IIoT). D2D communication promises ultra-low latency links, making it an ideal solution for a variety of emerging applications such as AR, VR, XR, etc.

[0005] It supports two key technologies: 1) Proximity Services (ProSe) and 2) Group Communication. ProSe services may allow devices in proximity to each other to communicate with each other. This is achieved through D2D discovery and D2D direct communication procedures. The discovery mechanism may allow a WTRU to discover another WTRU in its proximity, which may be performed directly by the WTRU or through the network. The group communication mechanism may allow the WTRU to communicate one-to-many in a highly resource-efficient manner, allowing messages to be easily propagated to a large group of people over a common downlink flow.

[0006] For unicast communications, the communicating entity may use a layer 2 identifier (ID) to uniquely identify the WTRU. An application layer ID may be associated with one or more V2X applications within the same WTRU, and in scenarios where the WTRU has multiple application layer IDs, each application layer ID of the same WTRU is considered a different WTRU. The WTRU may maintain an application layer ID and a layer 2 ID for unicast links, and an application may not use a layer 2 ID but may use an application layer ID instead, allowing the layer 2 ID to be changed without updating the application.

[0007] A user ID (e.g., an EPC ProSe user ID) can uniquely identify a WTRU registered with ProSe. An application layer group ID can uniquely identify an application layer group to which a WTRU belongs, a user in a specific application context, or a user group in a specific application context. According to "TS23.304, Proximity Services (ProSe) in 5G System (5GS) (Release 17); V17.3.0", for commercial services, the application layer group ID is provided by the application server; for public safety services, a preconfigured or pre-allocated application layer group ID will be used for multicast communications.

[0008] In order to provide a single service, application, and experience to a single user using multiple devices simultaneously, enhanced mechanisms are needed to associate, connect, and manage multiple WTRUs together. Summary of the invention

[0009] In an embodiment, a method implemented by a wireless transmit receive unit (WTRU) may include the step of sending a registration request message for aggregation to a network, the message including first information indicating WTRU capabilities aggregated by multiple WTRUs. The method may also include the step of receiving a registration accept message from the network, the message including second information indicating aggregation related information. The method may also include: the step of sending a message including third information indicating that the aggregate registration is complete to the network; and the step of establishing sidelink communications with multiple WTRUs based on the aggregation related information.

[0010] Aggregation related information may include any of one or more WTRU identifiers, a WTRU aggregation identifier, a time window for WTRU aggregation, and a subscriber identifier. WTRU capabilities / availability may include an indication of whether the WTRU supports single WTRU aggregation or multiple simultaneous WTRU aggregations. The sidelink establishment of communications may be based on a preconfigured trigger event. The WTRU may be a base station, may be configured as a base station, and / or may be configured with an element of a base station.

[0011] In an embodiment, a method implemented by a wireless transmit receive unit (WTRU) may include the step of receiving a first message from a network, the first message including a WTRU first aggregate revocation notification, the notification including identifiers of one or more WTRUs to be revoked from a plurality of WTRUs associated with an aggregation of the WTRU. The method may also include the steps of sending a revocation request message to the one or more WTRUs to be revoked; and receiving a revocation response message from the one or more WTRUs to be revoked.

[0012] The method may also include an additional step of sending a second aggregate revocation notification to the non-revokated WTRUs among the multiple WTRUs, the notification including identifiers of one or more revoked WTRUs; wherein the second aggregate revocation notification may include information indicating the release of any resources associated with one or more revoked WTRUs.

[0013] In an embodiment, a method implemented by a first wireless transmit receive unit (WTRU) may include the step of receiving a WTRU aggregation event, the event being used to trigger a registration request message for a WTRU aggregation of the first WTRU and a second WTRU. The method may also include the step of sending a registration request message to the second WTRU, the registration request message including information indicating the WTRU aggregation, wherein the second WTRU has registered with the WTRU aggregation. The method may also include the step of receiving a registration accept message from the second WTRU regarding the registration of the first WTRU with the WTRU aggregation; and the step of establishing sidelink communication with the second WTRU.

[0014] The WTRU aggregation event may include any of application information about the WTRU aggregation and a predetermined application event. Establishing the sidelink communication may include exchanging information related to any of directional communication, IP communication related information, and QoS information. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with the accompanying drawings. The figures in such drawings, like the detailed description, are examples. Therefore, these figures (FIG.) and detailed description should not be considered limiting, and there can and likely are other equally effective examples.

[0016] Additionally, like reference numerals ("ref.") in the drawings represent like elements, wherein:

[0017] Figure 1A is a system diagram illustrating an exemplary communication system;

[0018] Figure 1B It shows that Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used in a communication system as shown in;

[0019] Figure 1C It shows that Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used in a communication system shown in ;

[0020] Figure 1D It shows that Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown in ;

[0021] Figure 2 is a system diagram illustrating an example of a single aggregation of a set of WTRUs for providing an application experience for a single user;

[0022] Figure 3 is a block diagram showing an example of the relationship between a WTRU aggregate ID and other IDs, aggregated WTRUs and users;

[0023] Figure 4 is a message flow diagram illustrating an example of a WTRU receiving aggregation parameters;

[0024] Figure 5 is a message flow diagram illustrating an example of a WTRU triggered registration procedure;

[0025] Figure 6 is a message flow diagram illustrating an example of a process for establishing direct communications between WTRUs participating in WTRU aggregation;

[0026] Figure 7 is a message flow diagram illustrating an example of revoking a WTRU membership from a WTRU aggregation;

[0027] Figure 8 is a flow chart illustrating an example of a method implemented in a WTRU for aggregating WTRUs to WTRUs;

[0028] Fig. 9 is a flow chart illustrating an example of a method implemented in a WTRU for revoking a WTRU membership from a WTRU aggregation; and

[0029] Fig.10 is a flow chart illustrating an example of a method implemented in a WTRU for aggregating a first WTRU into a second WTRU portion of a WTRU aggregation. DETAILED DESCRIPTION

[0030] In the following detailed description, many specific details are set forth to fully understand the embodiments and / or examples disclosed herein. However, it should be understood that these embodiments and examples can be implemented without some or all of the specific details described herein. In other cases, well-known methods, procedures, components and circuits are not described in detail to avoid confusion in the following description. In addition, the embodiments and examples not specifically described herein can replace the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "providing") herein or be combined with them. Although various embodiments are described and / or required herein, wherein devices, systems, equipment, etc. and / or any elements thereof perform operations, processes, algorithms, functions, etc. and / or any part thereof, it should be understood that any embodiments described and / or required herein assume that any devices, systems, equipment, etc. and / or any elements thereof are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0031] The following are examples of communication systems. The methods, devices, and systems provided herein are well suited for communications involving wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided, in which various elements of a network may utilize, execute, be arranged according to, and / or be adapted and / or configured for use with the methods, apparatus, and systems provided herein.

[0032] Figure 1A 1 is a system diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content (e.g., voice, data, video, messaging, broadcast, etc.) to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources (including wireless bandwidth). For example, the 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 OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0033] like Figure 1AAs shown, the communication system 100 may include: wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d; radio access networks (RANs) 104 / 113; core networks (CNs) 106 / 115; public switched telephone networks (PSTNs) 108; the Internet 110; and other networks 112, but 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, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include (or may be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

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

[0036] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

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

[0038] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0039] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR wireless access, which may establish the air interface 116 using New Radio (NR).

[0040] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access simultaneously, for example using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions to / from multiple types of base stations (e.g., eNBs and gNBs).

[0041] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0042] Figure 1AThe base station 114b in may be a wireless router, a home Node-B, a home eNode-B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area (e.g., a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc.). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-APro, NR, etc.) to establish any of a small cell, a micro cell, or a femto cell. As Figure 1A As shown, base station 114b may be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0043] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although Figure 1A Although not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may employ NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0044] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 114 or a different RAT.

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

[0046] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the above elements while remaining consistent with an embodiment.

[0047] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors 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. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

[0048] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to send and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to send and / or receive IR, UV, or visible light signals. In an embodiment, the transmit / receive element 122 may be configured to send and / or receive RF and light signals. It should be appreciated that the transmit / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0049] although Figure 1B 102 as a single element, but the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0050] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11).

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

[0052] The processor 118 may receive power from the power source 134 and may be configured to distribute the power to and / or control the other components in the WTRU 102. The power source 134 may be any device suitable for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0053] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0054] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Components / peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0055] The WTRU 102 may include a full-duplex radio in which transmission and reception of some or all signals (e.g., associated with specific subframes of an uplink (e.g., for transmission) and a downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference through hardware (e.g., a choke) or through signal processing by a processor (e.g., a separate processor (not shown) or through the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio in which transmission and reception of some or all signals (e.g., associated with specific subframes of an uplink (e.g., for transmission) or a downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0056] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0057] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0058] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0059] Figure 1C The CN 106 shown in FIG. 1 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although each of the above elements is depicted as part of the CN 106, it is understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0060] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway, etc. during an initial attach of the WTRUs 102a, 102b, 102c. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0061] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode-B handovers, triggering paging when the WTRUs 102a, 102b, 102c have DL data, managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0062] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0063] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway, such as an IP Multimedia Subsystem (IMS) server, that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0064] although Figures 1A to 1D Although the WTRU is described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may communicate with a communication network using (eg, temporarily or permanently) a wired communication interface.

[0065] In a representative embodiment, other network 112 may be a WLAN.

[0066] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that transmits a communication stream into and / or out of the BSS. A STA communication stream originating from outside the BSS may be reached by the AP and may be transmitted to the STA. A communication stream originating from the STA and destined for a destination outside the BSS may be sent to the AP for transmission to the corresponding destination. Communication streams between STAs within the BSS may be sent by the AP, for example, where a source STA may send a communication stream to the AP, and the AP may transmit the communication stream to the target STA. Communication streams between STAs within the BSS may be considered and / or referred to as peer-to-peer communication streams. Peer-to-peer communication streams may be sent between a source STA and a target STA (e.g., directly between them) with a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11eDLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode is sometimes referred to herein as an "ad-hoc" communication mode.

[0067] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP can transmit beacons on a fixed channel (e.g., a primary channel). The primary channel can be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set through signaling. The primary channel can be an operating channel of the BSS, and the STA can use the primary channel to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access and collision avoidance (CSMA / CA) can be implemented, such as in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) can listen to the main channel. If a particular STA senses / detects the main channel and / or determines that it is busy, the particular STA can exit. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0068] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[0069] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or combining two discontinuous 80MHz channels, which can be called an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segment parser that divides the data into two streams. Each stream can be subjected to inverse fast Fourier transform (IFFT) processing and time domain processing respectively. The stream can be mapped onto two 80MHz channels, and the data can be sent by the transmitting STA. At the receiver of the receiving STA, the operation for the above-mentioned 80+80 configuration can be reversed, and the combined data can be sent to a medium access control (MAC) layer, an entity, etc.

[0070] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidths and carriers in 802.11af and 802.11ah are reduced relative to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah uses non-TVWS spectrum to support 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain functionality, such as limited functionality, including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include a battery whose battery life is above a threshold (e.g., to maintain a very long battery life).

[0071] WLAN systems (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) that may support multiple channels and channel bandwidths include channels that may be designated as primary channels. The bandwidth of the primary channel may be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC type devices) that support (e.g., only support) 1MHz mode, the primary channel may 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 sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (e.g., due to a STA (supporting only 1MHz operating mode) transmitting to the AP), the entire available band may be considered busy, even if most of the band remains idle and may be available.

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

[0073] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0074] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with the embodiments. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRU 102a. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may send multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point transmission (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0075] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0076] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may serve as a mobility anchor for the WTRU 102a, 102b, 102c, while the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0077] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interworking between NR and E-UTRA, routing user plane data to a user plane function (UPF) 184a, 184b, routing control plane information to an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0078] Figure 1DThe CN 115 shown in FIG. 1 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 above elements is depicted as part of the CN 115, it is understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0079] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing, for example, to customize CN support for the WTRU 102a, 102b, 102c based on the type of service used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies (e.g., LTE, LTE-A, LTE-APro) and / or non-3GPP access technologies (e.g., Wi-Fi).

[0080] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure communication flow routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy implementation and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0082] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 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, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b through the UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0083] Given that Figures 1A to 1D as well as Figures 1A to 1D , one or more or all of the functions described herein with respect to any of the following may be performed by one or more simulation elements / devices (not shown) WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other element / device described herein. A simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, a simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0084] The simulation device may be designed to perform one or more tests on other devices in a laboratory environment and / or in a carrier network environment. For example, one or more simulation devices may be fully or partially implemented and / or deployed as part of a wired and / or wireless communication network while performing one or more or all functions in order to test other devices within the communication network. One or more simulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing and / or may perform testing using wireless wireless communications.

[0085] One or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test lab and / or a test scenario in which a wired and / or wireless communication network is not deployed (e.g., testing) to implement testing of one or more components. One or more simulation devices may be test devices. The simulation device may send and / or receive data using direct RF coupling and / or wireless communication through RF circuitry (e.g., which may include one or more antennas).

[0086] Emerging multimodal media applications may require a user to use multiple devices / WTRUs for the same application, for example, a user using a VR headset, a haptic suit, and a game controller simultaneously to play a fully immersive game. Similarly, various emerging IoT applications may require the use / deployment of a collection of IoT devices, including sensors, to serve a single application and user. In such scenarios, in order to achieve a common task (e.g., an application), a group of WTRUs / devices may be associated with each other and with a specific user to achieve the application, improved QoS / QoE, and / or system efficiency. This is in contrast to a user using only a single device to consume an application (e.g., a user playing a game using his mobile device).

[0087] In order to provide a single service, application or experience to a single user using multiple devices simultaneously, a mechanism is needed to associate, connect and manage multiple WTRUs together.

[0088] Communication flows (e.g., data, frames, packets, streams, flows, PDUs) belonging to the same application experience can be distributed across these devices via a D2D direct communication link (e.g., a side link). For example, a direct communication link (e.g., a side link) can be used to improve user experience or system efficiency. Therefore, data delivery (and reception) between devices grouped for a single user must be associated and coordinated.

[0089] For a single multimodal application (involving multiple modes of communication, e.g., audio, video, tactile) for a single user, the requirements of the devices and communication flows transmitted in the aggregated WTRU group may vary. For example, a subset of communication flows may require high priority transmissions that will be sent to the subset of devices in the aggregated WTRU, and if such communication flows experience any interruptions or any degradation in their QoS, the overall service, application, or experience will be negatively impacted. Conversely, a subset of devices or communication flows in the same aggregated WTRU group may not be as critical, so any interruption (e.g., latency, packet loss) for these devices may not significantly affect the overall operation, the user's end goal (e.g., the task being performed by a group of WTRUs, devices, robots, or UAVs), or the delivery of critical data.

[0090] A first step to addressing the above issues may be to determine an aggregation of WTRUs / devices that are configured to serve a single user.

[0091] Existing 5G programs may define powerful functions such as QoS, session management, and mobility management. However, almost all of these powerful functions are designed for one WTRU. On the network side, the WTRU context can also be managed by network functions (e.g., UDM / SMF / AMF, etc.) at the WTRU granularity. In addition, most functions are based on the assumption that one WTRU can complete the task.

[0092] Existing 5G procedures do not allow a group of devices in direct D2D communications to be aggregated and associated with a single user. Existing application layer group IDs may allow a user to be identified in the context of a specific application or a group of users to be identified in the context of a specific application. However, this is not sufficient to group together a set of WTRUs associated with a specific user to use a single application or experience. For example, if two users are playing a game, both using multiple WTRUs, both users may have the same application layer group ID and does not allow grouping together the specific WTRUs that each user is using and then associating them to the corresponding user.

[0093] Furthermore, existing procedures and methods do not allow a WTRU / device to indicate WTRU aggregation capabilities and interest in potentially joining or leaving any WTRU aggregation in the future so that a WTRU aggregation capable device available for WTRU aggregation can be identified when aggregation is required.

[0094] Existing procedures and methods do not allow a WTRU to specify the WTRU aggregate to which it belongs during direct communication (eg, sidelink), thereby achieving efficient communication flow management and enhanced security.

[0095] Figure 2is a system diagram showing an example of a single aggregation of a set of WTRUs (for the purpose of providing an application experience for a single user). This shows that for a given WTRU aggregation, multiple WTRUs with different form factors can be used (e.g., Figure 2 WTRU1-audio system, WTRU2-haptic suit, and WTRU3-VR goggles), and they communicate via D2D (e.g., Figure 2 to communicate using the direct communication mechanism in the , thereby presenting a single experience to the user.

[0096] Figure 3 is a block diagram showing an example of the relationship between a WTRU aggregate ID and other IDs, aggregated WTRUs, and users. Figure 3 , the WTRU can be either a user equipment or a base station. Figure 3 , a parameter for D2D communication is introduced, here defined as WTRU aggregation ID, which is used to aggregate a group of WTRUs and their direct communication links (e.g., side links) for a single user.

[0097] A single user may have one WTRU Aggregate at a given time (e.g., only one application / experience is executed for that user and therefore there is only one active WTRU Aggregate ID). Alternatively, a single user may need to execute multiple applications / experiences. Thus, a user may be associated with multiple WTRU Aggregate IDs at the same time. As a non-limiting example, in a work environment, one Aggregate may be used for a video conference call application while a second Aggregate may be used for a data analytics application where multiple devices may be used for processing and data presentation. Additionally, a WTRU Aggregate ID may provide different functionality than an Application Layer Group ID. For example, if two players are playing the same game and both users have multiple WTRUs, the two users may have the same Application Layer Group ID but different Aggregate IDs.

[0098] In the case where only one WTRU aggregation is required for a user, the user ID can be used as the WTRU aggregation ID without having to create and maintain separate IDs and their mappings. A single WTRU aggregation can be associated with / group multiple WTRUs. In another scenario where an existing WTRU grouping ID (e.g., an application layer group ID) is used to group multiple WTRUs, the WTRU aggregation ID can be used to aggregate one or more WTRU groups for a specific user / application. The WTRU aggregation ID can be used to aggregate both WTRUs and WTRU groups.

[0099] A layer 2 link for a one-to-one direct communication (e.g., side link) may be identified by the combination of the layer 2 IDs of the two WTRUs, whereas a WTRU aggregate ID may be associated with multiple direct communication links (e.g., side links). This also means that a WTRU may use the same WTRU aggregate ID for multiple direct layer 2 links.

[0100] In scenarios where multi-mode / XR communication services are used, the WTRU aggregate ID may be used to associate multi-mode streams in D2D communications.

[0101] The following are examples of parameters related to WTRU aggregation. Table 1 below describes parameters that may be related to (eg, a specific) WTRU aggregation and are used by various procedures described below.

[0102] The procedures of Table 1 may include any of the following parameters in the message being transmitted.

[0103]

[0104] Table 1

[0105] Figure 4 is a message flow diagram illustrating an example of a WTRU receiving aggregation parameters. More specifically, Figure 4 is a message flow diagram illustrating an example procedure for receiving WTRU aggregate information from an application function (AF). Figure 4 , WTRU can be a user equipment or a base station.

[0106] refer to Figure 4 , at step 4.1, the AF / AS (e.g., V2X Application Server) may create or modify information related to the network and the WTRU aggregation group that the WTRU may have, which may be triggered by an event. For example, a change in the user's location may trigger the network to update the WTRU aggregation information, such as a newly added device. Such a trigger may also include any event that causes the WTRU aggregation requirement (e.g., a user logging into an application).

[0107] In step 4.2, the AF / AS may provide the network system with WTRU aggregation related information by calling the Network Exposure Function (NEF) application programming interface (API). The information may include the WTRU aggregation ID, the IP address used by the aggregated WTRU (or any ID that identifies the direct communication link (e.g., side link), such as the D2D session ID), the WTRU ID that identifies each WTRU in the system, and the user ID (e.g., the General Public Subscription Identifier (GPSI), the Subscription Permanent Identifier (SUPI)). The NEF may use the information received in step 4.2 to query the Binding Support Function (BSF) to determine which Policy Control Functions (PCFs) provide services to the WTRU. The information may also include a WTRU revocation trigger for revoking the WTRU aggregation membership.

[0108] In step 4.3, the NEF may forward all WTRU aggregation related information received in step 4.2 to the identified PCF. The PCF may use the received information to derive relevant configurations related to the WTRU and session involved (e.g., policy charging and control (rules)). Alternatively, the NEF may forward the information directly to the SMF. Alternatively, the Policy Control Function (PCF) or Session Management Function (SMF) or Access and Mobility Function (AMF) generates a new aggregation ID and stores it for a given WTRU aggregation. In some cases, the PCF may provide WTRU aggregation related information and PCC rules directly to the SMF. The SMF may store the received configuration information for later use.

[0109] In step 4.4, the PCF may forward the WTRU aggregation information together with the QoS rules to the RAN via the AMF over the N2 interface.

[0110] In step 4.5, the WTRU may receive a configuration message from the network (e.g., 5G) system. The PCF may configure the WTRU for direct communication (e.g., sidelink) for WTRU aggregation. WTRU aggregation related information may be sent to the WTRU via the AMF and N1 (non-access stratum (NAS)) interface. The message may also include QoS rules.

[0111] Alternatively, in an embodiment, instead of using the WTRU aggregate ID to associate users, devices / WTRUs and their communication links, the network (e.g., 5G) system may store and maintain records of user-WTRU-network / communication link associations in the network (e.g., in the SMF, AMF, AF). For example, the 5G network system may maintain a mapping between the aggregate device group and all other existing WTRU grouping IDs (e.g., broadcast group ID) and a specific user.

[0112] In other embodiments (e.g., when the WTRU is out of coverage, using direct communication without connecting to a network (e.g., 5G) system), one of the WTRUs participating / intending to participate in a new WTRU aggregation may generate a new WTRU aggregation ID. This ID will then be used in the process currently used for the out of coverage direct communication (e.g., sidelink) establishment process.

[0113] Any combination of information may be pre-configured / pre-assigned to a WTRU with WTRU aggregation capability, which may then be used for WTRU aggregation later. For example, WTRU aggregation parameters may be pre-configured in a library / application at the WTRU provided by a WTRU aggregation service provider. In another example, the WTRU may be configured to periodically download the latest WTRU aggregation information from an application server on the Internet.

[0114] Figure 5 is a message flow diagram illustrating an example of a WTRU triggered registration procedure. More specifically, Figure 5 is a message flow diagram illustrating a WTRU registration procedure for WTRU aggregation. Figure 5 , a WTRU may be a user equipment or a base station. A WTRU aggregation group or a plurality of WTRU aggregation groups may include any one of a user equipment and a base station.

[0115] refer to Figure 5 In step 5.1, the WTRU may register with the network (or update an existing registration). The WTRU may indicate its availability and / or capability to be part of a WTRU aggregation group or multiple WTRU aggregation groups. The WTRU may indicate the WTRU aggregation capabilities in the Registration Request message. In some cases, the WTRU aggregation capabilities may be indicated as part of any of the V2X, ProSe, and Sidelink capability indications.

[0116] If the WTRU already knows an existing WTRU aggregation that it wants to join, it may include the corresponding WTRU aggregation ID in the Registration Request message.

[0117] If the WTRU is to create a new WTRU aggregation group, it includes the information specified and received as described above. Alternatively, the WTRU aggregation ID may be created by the network (e.g., by AMF, SMF) and may be sent back to the WTRU in response to the Registration Request message.

[0118] The Registration Request message may indicate its availability / interest in participating in any future WTRU aggregations. In this case, the WTRU should include any of the following information: the WTRU aggregation ID of the target desired group communication, information about the communication flow requirements (e.g., foreseeable communication flow size and type for UL / DL), the specific time the WTRU wants to participate in the communication, the time window the WTRU wants to participate in the communication (if the WTRU can generate it), and specific user or WTRU IDs (or a set / subset of them) that the registering WTRU may know in advance and directly use for communication.

[0119] In step 5.2, if a valid AMF has not been indicated for the communication, the RAN (or an AMF configured to select an AMF) may select an AMF based on the provided information. The RAN forwards the Registration Request message to the AMF.

[0120] In step 5.3, the network (e.g., 5G) system (AMF) may verify the identity of the WTRU. If the WTRU has not sent identity-related information in step 5.1, it sends identity-related information as described above.

[0121] The AMF may initiate WTRU aggregation authentication by invoking the authentication server function (AUSF) and sending WTRU aggregation related information.

[0122] This expands the existing certification procedures in clause 4.2.2.2.2 of "TS23.502, 5G System (5GS) Procedures; Stage 2 (Release 17); V17.3.0"

[0123] In step 5.4, a unified data manager (UDM) component may be selected as described in Section 4.2.2.2.2 of "TS 23.502, 5G System (5GS) Procedures; Stage 2 (Release 17); V17.3.0". In the case where only some UDM functions support WTRU aggregation functions, step 5.4 may select UDM functions that support WTRU aggregation functions.

[0124] In step 5.5, the AMF may select a PCF that supports WTRU aggregation parameter / policy allocation and establish a WTRU policy association with the PCF for WTRU policy / parameter configuration.

[0125] In step 5.6, the AMF may report the capabilities received in step 5.1 to the PCF.

[0126] In step 5.7, the PCF may determine the WTRU aggregation strategy and parameters for a specific RAT based on the received WTRU capabilities regarding WTRU aggregation.

[0127] In step 5.8, the WTRU may receive a registration accept message from the network (e.g., 5G) system. The accept message may include the WTRU aggregate ID, which is generated by the AMF, SMF or PCF, or provided to the network by the AF / AS.

[0128] In step 5.9, the WTRU may respond to the network (e.g., 5G) system with a registration completion message.

[0129] Figure 6 is a message flow diagram showing an example of a process for establishing direct communications (e.g., sidelink) between WTRUs participating in a WTRU aggregation (including WTRU triggers for the aggregation process). The following steps may be repeated when participating in multiple WTRU aggregations. Step 6.1 details the Aggregation ID generation / acquisition / reception process, while step 6.2 lists the triggers for the WTRU to establish D2D (e.g., sidelink) communications. The remaining steps detail all other relevant procedures for establishing direct communications (e.g., sidelink) between aggregated WTRUs. Reference Figure 6 , WTRU can be either a user equipment or a base station.

[0130] In step 6.1, the WTRU may determine the destination Layer 2 ID and the WTRU Aggregation ID (generated by the WTRU or received from the network) for signaling reception for PC5 link (e.g., sidelink) establishment. The Layer 2 destination ID may be pre-configured or dynamically configured. The WTRU Aggregation ID may be determined based on WTRU aggregation information received from the network (as described above). Alternatively, the WTRU Aggregation ID may be established or generated by the WTRU itself through initial direct control communications between WTRUs prior to setting up direct communications for data communications (e.g., sidelink). In another arrangement, the WTRU Aggregation ID may be provided to the WTRU by an application running on the WTRU.

[0131] This step may include other information in step 6.1 of clause 6.3.3.1-1 of "TS23.287, 5G system (5GS) architecture enhancements to support vehicle-to-everything (V2X) services; Release 17; V17.3.0".

[0132] In step 6.2, at WTRU-1, a WTRU aggregation event may trigger the establishment of direct communications (e.g., sidelinks) with other WTRUs. Such events may include, but are not limited to, application, user, or WTRU context changes that provide information for WTRU aggregation and WTRU-direct communications (e.g., a change in user location may trigger a WTRU to update WTRU aggregation information and WTRU direct communications) or predetermined application events that establish direct (e.g., sidelink) communications based on a pre-configured benchmark (e.g., a specific time and / or location).

[0133] The received information may include a direct communication (e.g., ProSe, sidelink, multimode) service type, as well as the application layer ID and WTRU aggregation ID of the initiating WTRU. The WTRU aggregation may be specified as a new service type here (e.g., specified as a V2X service type or specifying the WTRU aggregation as a separate new service type). Any target WTRU ID and application layer ID may be included in the application information.

[0134] The application layer in the WTRU 1 may provide application requirements (eg, multimode flow requirements) for this PC5 direct (eg, sidelink) communication. It may determine QoS parameters (including the PC5 QoS Flow Identifier (PFI)).

[0135] In step 6.3, WTRU-1 may send a direct communication (e.g., sidelink) request to WTRU-N. WTRU-1 may initiate direct communication (e.g., sidelink) by sending a unicast Layer 2 Link Establishment procedure. ProSe / Sidelink direct communication (e.g., sidelink) establishment procedure may be used when the message sent over PC5 (e.g., sidelink) uses PC5 broadcast or unicast with a source Layer 2 ID and a target Layer 2 ID. Any of the following information may be included in the direct communication (e.g., sidelink) request:

[0136] User information may include an ID that uniquely identifies the user (eg, user ID, subscription information) and the WTRU's application layer ID.

[0137] The source and target Layer 2 IDs of the WTRU as defined in clauses 5.6.1.1 and 5.6.1.4 of "TS 23.287, Architecture enhancements for the 5G System (5GS) to support vehicle-to-everything (V2X) services; Release 17; V17.3.0".

[0138] WTRU aggregation ID, which uniquely identifies the aggregation of WTRUs.

[0139] Service information, which may include any of WTRU aggregation, ProSe, Sidelink, and multimodal service types as new service types.

[0140] Target WTRU information: Application layer ID of the target WTRU (optional)

[0141] Duration for which the link must be active / used.

[0142] Any combination of the above.

[0143] If a link to the target WTRU already exists, the WTRU may trigger a layer 2 link modification procedure.

[0144] Any other parameters specified in step 3 of clause 6.3.3.1-1 of “TS 23.287, 5G System (5GS) architecture enhancements to support vehicle-to-everything (V2X) services; Release 17; V17.3.0”.

[0145] At step 6.4, security may be established with WTRU-1. The target WTRU may respond by responding to the Direct Communication (e.g., Sidelink) Request message to establish security with WTRU-1. As part of step 6.4, WTRU aggregation information (e.g., WTRU aggregation ID) may be checked. If target WTRU information is not specified in the Direct Communication (e.g., Sidelink) Request, all WTRUs that are interested in (or authorized for) the WTRU aggregation or the specified service type may respond to WTRU-1 to establish security.

[0146] In step 6.5, WTRU-1 and WTRU-2 may exchange information related to directional communication, IP communication related information (e.g., IP address configuration, local IP address, IP address allocation mechanism (e.g., specifying whether to act as an IP router)), QoS information (including information about QoS flows to be added to specific direct communication (e.g., sidelink) links (PC5, ProSe, Sidelink) (e.g., specifying their PFI and PQI and related services) and their corresponding QoS parameters).

[0147] Some configurations are described in Section 6.3.3 of "TS23.287, Architecture enhancements for 5G System (5GS) to support vehicle-to-everything (V2X) services; Release 17; V17.3.0" and Section 5.4.5 of "TS23.303, Proximity-based Services (ProSe); Stage 2 (Release 17); V17.0.0".

[0148] At step 6.6, WTRU-1 may store the Layer 2 ID of the peer WTRU for future communications.

[0149] At step 6.7, if the communication acceptance criteria are met, the target WTRU, having successfully established security, may send a direct communication (e.g., sidelink) accept message to WTRU-1. Otherwise, a direct communication (e.g., sidelink) reject message may be sent. Information in such criteria may include any of the following: matching user information, matching WTRU aggregation ID, matching application layer ID, matching WTRU ID (as described above), and having sufficient resources to maintain the link for the time period specified in step 6.3.

[0150] The direct communication (eg, side link) accept message may include the information (eg, QoS information) specified in the direct communication (eg, side link) setup request in steps 6.3 to 6.5.

[0151] Optionally, information related to the direct link (e.g., side link) established in steps 6.3 to 6.5 (e.g., QoS information) may be sent by WTRU-1 or the target WTRU to the network. This information is then stored in the RAN and / or core network (e.g., SMF, AMF, AF, NWDAF) to monitor the status of the aggregated WTRU.

[0152] At step 6.8, data may be transmitted over the established unicast link. In some cases, the WTRU Aggregate ID may be included in messages transmitted between devices (this may be at any selected layer, e.g., frame, packet). Additionally, any combination of the above parameters may be included.

[0153] The following are examples of revoking a WTRU from an aggregation. Revocation of one or more WTRUs may be performed based on a variety of triggers. Some examples may include any of the following triggering events: expiration of the duration for which the WTRU is authorized to be part of an aggregation, a subscriber / user changes his or her preference for using a particular WTRU, malicious activity is detected, and resources are limited.

[0154] Figure 7 is a message flow diagram illustrating an example of revoking a WTRU membership from a WTRU aggregation. Figure 7 , WTRU can be either a user equipment or a base station.

[0155] In step 7.1, WTRU-1 may receive a deconfiguration notification from a network system (e.g., 5GS). In addition to the above parameters, the deconfiguration notification may also include the ID of the WTRU to be revoked and a WTRU revocation trigger (as described above). The revocation trigger may be specified as a policy or a set of conditions that specify when the membership of the corresponding WTRU is revoked (e.g., if the user moves from location A, then WTRU-2 is revoked). Alternatively, the deconfiguration notification may specify that the WTRU be removed from the WTRU aggregation immediately or after a certain period of time.

[0156] The deconfiguration notification may be sent from the RAN, AMF, SMF, PCF, AF / AS. Alternatively, the deconfiguration notification may be provided to the WTRU by an application running on the WTRU or by an application running on a cloud server. In another case, the deconfiguration notification may be sent by another WTRU (e.g., a trusted WTRU that broadcasts WTRU revocation information).

[0157] In step 7.2, WTRU-1 may trigger WTRU revocation after receiving the deconfiguration notification in step 7.1 or after the WTRU revocation conditions provided in step 7.1 are met.

[0158] In step 7.3, WTRU-1 may send a WTRU Withdraw Request message to WTRU-2 to remove WTRU-2 from the WTRU aggregation. The Withdraw Request message may specify any of the WTRU aggregation ID, user / subscriber information, and a withdrawal reason, as well as the other parameters described above. In addition, the Withdraw Request message may include deleting all context and other data related to the WTRU aggregation. The Withdraw Request message may include releasing the Layer 2 link. In a scenario where multiple WTRUs are removed from a WTRU aggregation, a Withdraw Request message may be sent to all WTRUs to be removed from the aggregation.

[0159] In step 7.4, WTRU-2 may respond to WTRU-1 with a WTRU Withdraw Response message and may delete all data related to the WTRU aggregation. Alternatively, UE-2 may send this message to all WTRUs and / or networks (e.g., 5GS (RAN, AMF, SMF, PCF, AF / AS)) related to the WTRU aggregation and applications running on the WTRU to release any resources related to WTRU-2 and update the WTRU aggregation related information with the current status. In some deployments, the Withdraw Response message may be optional.

[0160] In step 7.5, WTRU-1 may notify applications running on the WTRU to remove WTRU-2 (or all removed WTRUs in the case of removing multiple WTRUs) from the WTRU aggregation by transmitting a withdrawal notification message. WTRU-1 may also send a withdrawal notification message to all WTRUs and / or networks (e.g., 5GS (RAN, AMF, SMF, PCF, AF / AS)) associated with the WTRU aggregation to release any resources associated with WTRU-2 and update the WTRU aggregation related information with the current status.

[0161] refer to Figure 8, a method 800 implemented in a WTRU for aggregating a WTRU into a WTRU aggregation may include the step of sending 810 a registration request message for aggregation to a network, the message including first information indicating WTRU capabilities regarding a plurality of WTRU aggregations. The aggregation related information may include any one of one or more WTRU identifiers, a WTRU aggregation identifier, a time window for WTRU aggregation, and a subscriber identifier. The WTRU capabilities may include an indication of whether the WTRU supports a single WTRU aggregation or multiple simultaneous WTRU aggregations. The registration request message may include an indication of interest in an aggregation operation. The registration request message may include a WTRU aggregation identifier associated with the aggregation operation.

[0162] The method 800 may further include a step 820 of receiving a registration accept message from the network, the registration accept message including second information indicating the aggregation related information.

[0163] The method 800 may also include: step 830 of sending a message including third information indicating that the aggregate registration is complete to the network; and step 840 of establishing side link communications with multiple WTRUs based on the aggregate related information, wherein the side link communication is established based on a preconfigured trigger event.

[0164] refer to Fig. 9 , a method 900 implemented in a WTRU for revoking a WTRU membership from a WTRU aggregation may include a step 910 of receiving a first message from a network, the first message including a WTRU first aggregation revocation notification, the notification including an identifier of one or more WTRUs to be revoked from a plurality of WTRUs associated with the WTRU aggregation. The method may also include a step 920 of sending a revocation request message to the one or more WTRUs to be revoked; and a step 930 of receiving a revocation response message from the one or more WTRUs to be revoked.

[0165] In addition, method 900 may also include the step of sending a second aggregate revocation notification to the non-revokated WTRUs among the multiple WTRUs, wherein the second aggregate revocation notification includes identifiers of one or more revoked WTRUs; wherein the second aggregate revocation notification includes information indicating the release of any resources associated with one or more revoked WTRUs.

[0166] See also Fig.10, a method 1000 implemented in a WTRU for a WTRU aggregation of a first WTRU to a second WTRU portion of a WTRU aggregation may include the step of receiving 1010 a WTRU aggregation event for triggering a registration request message for the WTRU aggregation of the first WTRU and the second WTRU; wherein the WTRU aggregation event may include any of application information about the WTRU aggregation and a predetermined application event. The method 1000 may also include the step of sending 1020 a registration request message to the second WTRU, the registration request message including information indicating the WTRU aggregation, wherein the second WTRU has registered with the WTRU aggregation. The method 1000 may also include: the step of receiving 1030 a registration accept message from the second WTRU regarding the registration of the first WTRU with the WTRU aggregation; and the step of establishing 1040 side link communication with the second WTRU. Establishing the side link communication may include exchanging information related to any of directional communication, IP communication related information, and QoS information.

[0167] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this application, which are intended to illustrate multiple aspects. It will be understood by those skilled in the art that many modifications and changes may be made without departing from its spirit and scope. Unless explicitly provided, any element, action or instruction used in the description of this application should not be interpreted as being essential or indispensable to the present invention. In addition to those listed herein, those skilled in the art will understand from the foregoing description that functionally equivalent methods and devices within the scope of the present disclosure. Such modifications and changes are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the full scope of equivalents enjoyed by these claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0168] For simplicity, the foregoing embodiments are discussed with respect to the terminology and structure of infrared devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (e.g., sound waves).

[0169] It should also be understood that the terms used herein are used only to describe specific embodiments and are not intended to be limiting. The term "video" or the term "image" used herein may refer to any of a snapshot, a single image, and / or multiple images displayed over time. As another example, the term "user equipment" and its abbreviation "UE", "remote" and / or the term "head-mounted display" or its abbreviation "HMD" mentioned herein may refer to or include: (i) a wireless transmit and / or receive unit (WTRU); (ii) any of multiple embodiments of the WTRU; (iii) a wireless and / or wired (e.g., bindable) device configured with some or all of the structure and functionality of the WTRU; (iii) a wireless and / or wired device configured with less than all of the structure and functionality of the WTRU; or (iv), etc. References herein Figures 1A to 1D Details of an example WTRU are provided, which may represent any WTRU described herein. As another example, various embodiments disclosed herein above and below are described as using a head mounted display. Those skilled in the art will recognize that devices other than head mounted displays may be used, and that some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0170] In addition, the methods provided herein may be implemented in a computer program, software, or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) 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, caches, semiconductor storage devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and optical media (e.g., CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host.

[0171] Variations of the above methods, devices, and systems are possible without departing from the scope of the present invention. In view of the wide variety of embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source, such as a battery, to provide any suitable voltage.

[0172] In addition, in the embodiments provided above, 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, multiple CPUs and memories may perform references to actions and symbolic representations of operations or instructions. These actions and operations or instructions may be referred to as "execution", "computer execution" or "CPU execution".

[0173] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation or reduction of electrical signals and the maintenance of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU, as well as other processing of signals. The memory locations where data bits are maintained are physical locations having specific electrical, magnetic, optical, or organic properties corresponding to or representing data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0174] The data bits may also be stored on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage systems that can be read by the CPU. The computer-readable media may include cooperating or interconnected computer-readable media that exist only on the processing system or distributed among multiple interconnected processing systems, which may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may support the provided methods.

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

[0176] There is little distinction between hardware and software implementations of aspects of the system. The use of hardware or software is often (but not always, as the choice between hardware and software may become important in certain circumstances) a design choice that represents a trade-off between cost and efficiency. There may be a variety of carriers for implementing the processes and / or systems and / or other techniques described herein (e.g., hardware, software, and / or firmware), and the preferred carrier may vary depending on the environment in which the processes and / or systems and / or other techniques are deployed. For example, if the implementer determines that speed and accuracy are critical, the implementer may select a primarily hardware and / or firmware carrier. If flexibility is critical, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0177] The foregoing detailed description has described various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. As long as these block diagrams, flow charts and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation in these block diagrams, flow charts or examples can be implemented individually and / or collectively by various hardware, software, firmware or almost any combination. In an embodiment, several parts of the subject matter described herein can be implemented by application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will recognize that certain aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented 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 as almost any combination thereof, and according to the present disclosure, designing circuits and / or writing software and / or firmware codes are completely within the skill of those skilled in the art. Furthermore, those skilled in the art will recognize that the mechanisms of the subject matter described herein may be distributed as a program product in various forms, and that the illustrative embodiments of the subject matter described herein are applicable to the particular type of signal-bearing media used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media, such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memories, etc., and transmission type media, such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0178] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein and then use engineering practices to integrate the devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into data processing systems through reasonable experiments. Those skilled in the art will recognize that a typical data processing system can generally include a system unit housing, a video display device, a memory (e.g., volatile and non-volatile memory), a processor (e.g., a microprocessor and a digital signal processor), a computing entity (e.g., an operating system, a driver, a graphical user interface, and an application), one or more interactive devices (e.g., a touch pad or screen), and / or a control system (including feedback loops and control motors) (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as components typically found in data computing / communication and / or network computing / communication systems.

[0179] The subject matter described herein sometimes illustrates different components contained in or connected to different other components. It should be understood that these depicted architectures are merely examples, and in fact many other architectures that implement the same function can be implemented. In a conceptual sense, any component arrangement that implements the same function is effectively "associated" so that the desired function can be achieved. Therefore, any two components combined to achieve a specific function herein can be regarded as "associated" with each other, so as to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be regarded as "operably connected" or "operably coupled" to each other to achieve the desired function, and any two components that can be so associated can also be regarded as "operably coupled" to each other to achieve the desired function. Specific examples of operable coupling include, but are not limited to, physically matchable and / or physically interacting components and / or wirelessly interacting and / or wirelessly interacting components and / or logically interacting and / or logically interacting components.

[0180] With respect to the use of almost any plural and / or singular terms herein, those skilled in the art may translate the plural to the singular and / or the singular to the plural, depending on the context and / or application. For clarity, various singular / plural arrangements may be expressly set forth herein.

[0181] Those skilled in the art will understand that, in general, the terms used herein, especially in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" 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 also understand that if a specific number of claim recitations are intended to be introduced, such intent will be explicitly stated in the claim, and if no such statement is made, no such intent exists. For example, if only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite article "a" or "an" will limit any particular claim including such introduced claim recitation to embodiments containing only one such recitation, even if the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same is true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of claim recitations is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the number of recitations (e.g., a simple recitation of "two recitations" without other modifiers means at least two recitations, or two or more recitations). In addition, where a convention similar to "at least one of A, B, and C, etc." is used, generally the intention of such construction is a convention that can be understood by those skilled in the art (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, a system having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Where a convention similar to "at least one of A, B, or C, etc." is used, generally the intention of such construction is a convention that can be understood by those skilled in the art (e.g., "a system having at least one of A, B, or C" would include, but is not limited to, a system having A alone, B alone, C alone, 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 also appreciate that almost any disjunctive word and / or phrase that indicates two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of one, either, or both terms. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B" or "A and B".Furthermore, as used herein, the term "any" followed by a listing of multiple items and / or multiple categories of items is intended to include "any," "any combination," "any multiple," and / or "any combination of multiples" of the items and / or categories of items, alone or in combination with other items and / or other categories of items. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "number" is intended to include any number, including zero. And as used herein, the term "plurality" is intended to be synonymous with "plurality."

[0182] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0183] It will be understood by those skilled in the art that all ranges disclosed herein also encompass any possible sub-ranges and combinations of sub-ranges thereof for any purpose, such as in providing a written description. Any listed range can be easily understood to fully describe and be able to decompose the same range into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily decomposed into the lower third, the middle third, and the upper third, etc. It will also be understood by those skilled in the art that all languages, such as "at most", "at least", "greater than", "less than", etc., include the listed numbers and refer to the ranges that can be subsequently decomposed into sub-ranges as described above. Finally, it will be understood by those skilled in the art that the range includes each individual member. Therefore, for example, a group with 1-3 cells refers to a group with 1, 2, or 3 cells. Similarly, a group with 1-5 cells refers to a group with 1, 2, 3, 4, or 5 cells, and so on.

[0184] Furthermore, the claims should not be read as limited to the order or elements provided unless otherwise stated. Furthermore, use of the term "for" in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, any claim without the term “for” is not intended to be recited.

Claims

1. A method implemented by a wireless transmit receive unit (WTRU), comprising: sending a registration request message for aggregation to a network, the registration request message including first information indicating WTRU capabilities regarding aggregation of a plurality of WTRUs; receiving a registration acceptance message from the network, the registration acceptance message including second information indicating aggregation related information; sending a message including third information indicating that the aggregate registration is completed to the network; and Sidelink communications are established with a plurality of WTRUs based on the aggregated relevant information.

2. The method of claim 1, wherein the aggregation-related information comprises any one of one or more WTRU identifiers, a WTRU aggregation identifier, a time window for WTRU aggregation, and a subscriber identifier.

3. The method of any one of claims 1 and 2, wherein the WTRU capabilities include an indication of whether the WTRU supports WTRU aggregation or multiple simultaneous WTRU aggregation.

4. The method according to any of the preceding claims, wherein the side link establishes communication based on a preconfigured trigger event.

5. A method according to any preceding claim, wherein the registration request message comprises an indication of interest in aggregation operations.

6. The method of claim 5, wherein the registration request message includes a WTRU aggregation identifier associated with the aggregation operation.

7. A method according to any of the preceding claims, wherein the WTRU is configured as a base station or is configured with elements of a base station.

8. A method implemented by a wireless transmit receive unit (WTRU), comprising: receiving a first message from a network, the first message comprising a WTRU first aggregate withdrawal notification, the WTRU first aggregate withdrawal notification comprising identifiers of one or more WTRUs to be withdrawn from a plurality of WTRUs associated with an aggregation of the WTRU; Sending a revocation request message to the one or more WTRUs to be revoked; as well as A revocation response message is received from the one or more WTRUs to be revoked.

9. The method according to claim 8, comprising: sending a second aggregate revocation notification to non-revoked WTRUs among the plurality of WTRUs, the second aggregate revocation notification including identifiers of one or more revoked WTRUs; The second aggregated revocation notification includes information indicating the release of any resources associated with the one or more revoked WTRUs.

10. A method implemented by a first wireless transmit receive unit (WTRU), comprising: receiving a WTRU aggregation event, the WTRU aggregation event being used to trigger a registration request message for a WTRU aggregation of the first WTRU and a second WTRU; sending the registration request message to the second WTRU, the registration request message including information indicating the WTRU aggregation, wherein the second WTRU is registered with the WTRU aggregation; receiving a registration accept message from the second WTRU regarding registration of the first WTRU with the WTRU aggregation; as well as Establishing sidelink communication with the second WTRU.

11. The method of claim 10, wherein the WTRU aggregation event comprises any one of application information aggregated by the WTRU and a predetermined application event.

12. The method of any one of claims 10 and 11, wherein establishing the sidelink communication comprises: Information related to any one of directional communication, IP communication related information, and QoS information is exchanged.

13. A wireless transmit / receive unit (WTRU), the WTRU comprising a processor, a transceiver unit, and a memory unit and configured to: sending a registration request message for aggregation to a network, the registration request message including first information indicating WTRU capabilities regarding aggregation of a plurality of WTRUs; receiving a registration acceptance message for aggregation from the network, the registration acceptance message including second information indicating aggregation-related information; sending a message including third information indicating completion of the aggregate registration to the network; and Sidelink communications are established with a plurality of WTRUs based on the aggregated relevant information.

14. The WTRU of claim 13, wherein the aggregation-related information comprises any one of one or more WTRU identifiers, a WTRU aggregation identifier, a time window for WTRU aggregation, and a subscriber identifier.

15. The WTRU of any one of claims 13 and 14, wherein the WTRU capabilities include an indication of whether the WTRU supports WTRU aggregation or multiple simultaneous WTRU aggregation.

16. The WTRU of any one of claims 13 to 15, wherein the sidelink communication establishment is based on a preconfigured trigger event.

17. The WTRU of any one of claims 13 to 16, wherein the registration request message includes an indication of interest in aggregation operations.

18. The WTRU of claim 17, wherein the registration request message includes a WTRU aggregation identifier associated with the aggregation operation.

19. The WTRU of any one of claims 13 to 18, wherein the WTRU is configured as a base station or is configured with elements of a base station.

20. A wireless transmit / receive unit (WTRU), the WTRU comprising a processor, a transceiver unit, and a memory unit and configured to: receiving a first message from a network, the first message comprising a WTRU first aggregate withdrawal notification, the WTRU first aggregate withdrawal notification comprising identifiers of one or more WTRUs to be withdrawn from a plurality of WTRUs associated with an aggregation of the WTRU; Sending a revocation request message to the one or more WTRUs to be revoked; as well as A revocation response message is received from the one or more WTRUs to be revoked.

21. The WTRU according to claim 20 is configured to send a second aggregate revocation notification to the non-revoked WTRUs among the multiple WTRUs, wherein the second aggregate revocation notification includes the IDs of one or more revoked WTRUs; wherein the second aggregate revocation notification includes information indicating the release of any resources associated with the one or more revoked WTRUs.

22. A first wireless transmit / receive unit (WTRU), the WTRU comprising a processor, a transceiver unit, and a memory unit and configured to: receiving a WTRU aggregation event, the WTRU aggregation event being used to trigger a registration request message for a WTRU aggregation of the first WTRU and a second WTRU; sending the registration request message to the second WTRU, the registration request message including information indicating the WTRU aggregation, wherein the second WTRU is registered with the WTRU aggregation; receiving a registration accept message from the second WTRU regarding registration of the first WTRU with the WTRU aggregation; as well as Establishing sidelink communication with the second WTRU.

23. The first WTRU of claim 22, wherein the WTRU aggregated event comprises any one of application information aggregated by the WTRU and a predetermined application event.

24. The first WTRU of any one of claims 22 and 23, wherein establishing the sidelink communication comprises: Information related to any one of directional communication, IP communication related information, and QoS information is exchanged.

Images