System and method for u2u relay state detection during discovery

Abstract

A method performed by a first WTRU may include: receiving one or more RSCs from a network, wherein each of the one or more RSCs includes a network assisted security indicator; selecting a first RSC from the one or more RSCs, wherein the selection of the first RSC is based on a first network assisted security indicator associated with the first RSC and a network coverage status of the first WTRU; under the condition that the network coverage range state of the first WTRU exceeds the coverage range, a discovery message is sent to a second WTRU, and the discovery message comprises the first RSC; and receiving the DCR message from the second WTRU, wherein the DCR message comprises the second RSC. The first WTRU may be a relay WTRU, and the second WTRU may be a source WTRU. The second RSC may be the same as the first RSC.

Description

[0001] Cross Reference to Related Applications This application claims the benefit of U.S. Provisional Application No. 63 / 457,586, filed April 6, 2023, the contents of which are incorporated by reference herein. BACKGROUND

[0002] Direct and WTRU-to-network discovery security procedures are specified in certain wireless standards. Specifically, the restricted discovery messages are protected from replay and integrity using security material associated with ProSe Restricted Code and RSC, respectively. A mechanism based on UTC time is used to prevent replay to ensure freshness of discovery message protection.

[0003] For direct discovery, security material associated with ProSe Restricted Code can be provided to a WTRU by a Direct Discovery Name Management Function (DDNMF). For WTRU-to-network discovery, security material associated with RSC can be provided to end WTRU / s and relay WTRU by a DDNMF or a Policy Control Function (PCF) or a ProSe Key Management Function (PKMF).

[0004] For 5G ProSe WTRU-to-WTRU relay discovery, both Model A and Model B discovery are supported. Model A uses a single discovery protocol message (advertisement), while Model B uses two discovery protocol messages (solicitation and response). Procedures for 5G ProSe WTRU-to-WTRU relay discovery using Model A and Model B are defined in 3GPP wireless standards.

[0005] 5G ProSe communication via 5G ProSe WTRU-to-WTRU relay is supported, where discovery is integrated into the PC5 unicast link establishment procedure. The link establishment procedure using integrated discovery does not require running independent discovery. Detailed procedures are defined in 3GPP wireless standards. SUMMARY

[0006] A method performed by a first WTRU can include receiving one or more relay service codes (RSCs) from a network, wherein each of the one or more RSCs includes a network assisted security indicator; selecting a first RSC from the one or more RSCs, wherein the selection of the first RSC is based on a first network assisted security indicator associated with the first RSC and a network coverage status of the first WTRU; transmitting a discovery message to a second WTRU in an instance in which the network coverage status of the first WTRU is out of coverage, the discovery message including the first RSC; and receiving a direct communication request (DCR) message from the second WTRU, wherein the DCR message includes a second RSC. The first WTRU can be a relay WTRU and the second WTRU can be a source WTRU. The second RSC can be the same as the first RSC.

[0007] A method performed by a first WTRU can include receiving one or more relay service codes (RSCs) from a network, wherein each of the one or more RSCs includes a network assisted security indicator; receiving a discovery message from a second WTRU, the discovery message including a first RSC; and transmitting a direct communication request (DCR) message to the second WTRU, the DCR message including a second RSC. The first WTRU can be a source WTRU and the second WTRU can be a relay WTRU. The second RSC can be the same as the first RSC. BRIEF DESCRIPTION OF DRAWINGS

[0008] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings wherein like reference numerals indicate like parts. For a better understanding: Figure 1A FIG. 1 is a system diagram illustrating an example communications system in which one or more disclosed embodiments can be implemented; Figure 1B FIG. 2 is a system diagram illustrating an example wireless access network (WAN) and an example core network (CN) that can be used within the communications system illustrated in FIG. 1 and according to one embodiment; Figure 1A FIG. 3 is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in FIG. 1 and according to one embodiment; Figure 1C FIG. 4 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system illustrated in FIG. 1 and according to one embodiment; Figure 1A FIG. 5 is a system diagram illustrating yet another example RAN and yet another example CN that can be used within the communications system illustrated in FIG. 1 and according to one embodiment; Figure 1D FIG. 6 is a system diagram illustrating yet another example RAN and yet another example CN that can be used within the communications system illustrated in FIG. 1 and according to one embodiment; Figure 1A Figure 2 FIG. 7 illustrates an example of a status indication procedure during discovery; Figure 3 ​The figure illustrates an example of a WTRU relay status detection process that does not involve independent discovery; Figure 4 The diagram illustrates an example of a secure establishment process between a target WTRU and a relay WTRU. Figure 5 The diagram illustrates an example of a process executed by a WTRU; and Figure 6 The diagram illustrates an example of a process executed by WTRU. Detailed Implementation

[0009] Figure 1A This is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables 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 Unique Word Discrete Fourier Transform Spread Spectrum OFDM (ZT UW-DTS-S-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

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

[0011] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), NodeBs, eNodeBs (eNBs), home node Bs, home eNode Bs, next-generation NodeBs such as gNodeBs (gNBs), new radio (NR) NodeBs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base station and / or network elements.

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

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

[0014] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish an air interface 116 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

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

[0016] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use NR to establish air interface 116.

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

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

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

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

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

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

[0023] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

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

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

[0026] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals on air interface 116.

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

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

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

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

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

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

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

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

[0035] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0036] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. While the foregoing elements are described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

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

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

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

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

[0041] Despite WTRU in Figures 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0042] In a representative embodiment, another network 112 may be a WLAN.

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

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

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

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

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

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

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

[0050] Figure 1D This diagram illustrates a system diagram of RAN 104 and CN 106 according to one embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 104 can also communicate with CN 106.

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

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

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

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

[0055] Figure 1DThe CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are depicted as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0056] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN104 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating Non-Access Stratum (NAS) signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be created for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for MTC access, and so on. AMF 182a and 182b can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

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

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

[0060] Given Figures 1A-1D as well as Figures 1A-1D As described herein, one or more of the following functions can be performed by one or more emulation 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-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0061] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device and / or use over-the-air wireless communication to perform tests for testing purposes.

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

[0063] The following abbreviations and acronyms may be involved: CP control plane DCR Direct Communication Request DCA direct communication acceptance DCReject Direct Communication Rejection DDNMF Direct Discovery Name Management Function IC coverage area OoC is outside coverage area PRUK ID ProSe Remote User Key Identification RSC Relay Service Code SUCI subscription hidden identifier UP User Plane U2U User Equipment to User Equipment WTRU (Wireless Transmit / Receive Unit)

[0064] In the following text, the terms L3 U2U trunk WTRU, L3 WTRU to WTRU trunk WTRU, L3 U2U trunk WTRU, U2U trunk WTRU, trunk WTRU, and trunk are used interchangeably. The term "terminal WTRU" can refer to the source WTRU and / or the destination WTRU.

[0065] Some 3GPP wireless standards address the security requirements of 3GPP systems for relay WTRUs. These standards stipulate that 3GPP systems must be able to protect the security (i.e., integrity and confidentiality) of information transmitted between peer WTRUs via the relay WTRU. Failure to comply with this may open vulnerabilities in 5GS and allow various attacks, such as unauthorized disclosure and modification of information. Communication protection between peer WTRUs assumes that the relay WTRU is a trusted node.

[0066] When security is established between the end WTRU and the relay WTRU with network assistance, and the relay WTRU is within the 5G network coverage area, the security process is the same as PC5 security for 5GProSe communication via 5GProSe L3 WTRU to network relay as defined in the wireless standard.

[0067] For 5G ProSe WTRU to network relay, there are two security mechanism options: a security procedure on the user plane (UP) as defined in some 3GPP radio standards, and a security procedure on the control plane (CP) as defined in some 3GPP radio standards. The security mechanism for 5G ProSe remote WTRU and 5G ProSe WTRU to network relay is determined based on the control plane security indicator associated with the RSC, which is specified in some 3GPP radio standards.

[0068] The 3GPP radio standard specifies that a secure procedure between the end WTRU and relay WTRUs (with and without network assistance) can be initiated using different parameters in the DCR message sent by the end WTRU, and therefore different security credentials (e.g., PRUK ID or SUCI against the MSB of KNRP ID / KNRP-sess ID) are used to establish security. Therefore, the parameters and security materials used to establish security between the end WTRU and relay WTRU should take into account the coverage status (i.e., IC or OoC) of the relay WTRU.

[0069] Network-assisted security procedures may require the WTRU relay to be within coverage. However, one or more end WTRUs may not know the coverage status (i.e., IC or OoC) of the relay WTRU because the mechanism by which the end WTRU determines the coverage status of the relay WTRU is not defined.

[0070] Therefore, one issue is how to select a suitable security procedure between one or more end WTRUs and relay WTRUs. More specifically, this issue includes which security procedure should be performed between the source WTRU and the relay WTRU, and which security procedure should be selected between the relay WTRU and the target WTRU. Another issue may be the procedure that enables the end WTRU to detect the coverage status of the relay WTRU.

[0071] In one embodiment, in order for the source WTRU to detect the coverage status of the relay WTRU, the relay WTRU may indicate its coverage status (i.e., IC or OoC and / or support for network-assisted or network-unassisted security) during the discovery process. Based on the relay WTRU's coverage status and / or network-assisted support indication, the source WTRU can select the appropriate security parameters for security establishment.

[0072] In another embodiment, when discovery is integrated into PC5 link establishment (i.e., no independent discovery), if the received security parameters are inconsistent with the current coverage status of the relay WTRU, the relay WTRU can send a Direct Communication Reject (DCReject) message to the end WTRU. The DCReject message may include a reason code indicating the coverage status of the relay WTRU.

[0073] In another embodiment, once security is established with both the source WTRU and the relay WTRU, the relay WTRU can send an indication (i.e., coverage status and / or network assistance support) to the target WTRU in a DCR message. Based on this indication, the target WTRU can either initiate a security establishment (e.g., without network assistance) or send a DCReject message indicating that the target WTRU can initiate a PC5 link establishment with the relay WTRU (e.g., with network assistance).

[0074] In one embodiment, the selection of security materials may depend on whether the relay WTRU is IC or OoC. During the discovery process, the status of the relay WTRU can be indicated to the end WTRU. The indication of the relay WTRU's coverage status (e.g., IC or OoC) applies to both Model A and Model B discovery processes. The selection of security materials during discovery can take into account whether the end WTRU and relay WTRU are in IC or OoC status.

[0075] In another embodiment, the network may require more control over the WTRUs and, for those service sets, may prefer to use network-assisted security procedures rather than non-network-assisted security procedures. Therefore, the network can indicate the preference associated with the RSC to the end WTRU and the trunk WTRU, which ensures that the network-assisted security procedure is used whenever the trunk WTRU is in the IC state. The indicator associated with the RSC can indicate whether security for communication with the trunk WTRU is supported with network assistance, without network assistance, or both.

[0076] In another embodiment, the selection of the relay WTRU can be based on the relay WTRU's coverage status (e.g., for network-assisted security, the preferred RSC is that the relay WTRU is selected by the source WTRU only when its coverage status is indicated as IC). If there is no preference associated with the RSC used for network-assisted security, the source WTRU can learn the relay WTRU's coverage status during discovery and use that information to select appropriate parameters for establishing security with the relay WTRU.

[0077] Figure 2 The figure illustrates an example of the status indication process 200 during discovery.

[0078] In 210, the source WTRU 202, trunk WTRU 204, and target WTRU 206 may be equipped with one or more RSCs, which include a network-assisted security indicator that indicates whether a network-assisted security procedure or a non-network-assisted security procedure should be used. The source WTRU 202, trunk WTRU 204, and target WTRU 206 may be equipped with security materials to support IC and OoC scenarios.

[0079] At 212, as part of the discovery process, the relay WTRU 204 may send its status indication (e.g., IC or OoC and / or with or without a network auxiliary indicator) to the source WTRU 202. If Model A is implemented, the relay WTRU status indication may be sent via a discovery announcement message. If Model B is implemented, the relay WTRU status indication may be sent via a solicitation response message sent in response to a solicitation request received by the relay WTRU from the source WTRU 202.

[0080] At 214, the source WTRU 202 can learn or track the status of the relay WTRU, including its coverage status, and can use the status of the relay to determine whether it is connected to the relay WTRU 204, and if it is connected to the relay WTRU 204, which security procedure to perform.

[0081] For example, if trunk WTRU 204 is an IC (Independent Core), source WTRU 202 can initiate a network-assisted security procedure. If trunk WTRU 204 is an OoC (Out of Memory), source WTRU 202 can initiate an OoC security procedure by sending a PRUK ID or SUCI (i.e., using a PRUK as credentials), a KNRP ID (if available), or a KNRP-sess ID with a KNRP ID / MSB (e.g., using provided long-term credentials). For example, source WTRU 202 can decide to select a different trunk based on preferences associated with RSC and the state of trunk selection for trunk WTRU 204. For example, if the trunk is an OoC and the RSC prefers network assistance, source WTRU 202 can choose not to select that trunk, but instead select and / or search for a trunk WTRU that is an IC. In another example, when trunk WTRU 204 is an OoC, trunk WTRU 204 can decide to stop announcing and / or responding to solicitation messages for RSCs that only support network assistance.

[0082] At 216, source WTRU 202 may send a DCR message to relay WTRU 204. The DCR message may include an RSC. This RSC may be the same RSC received by source WTRU 202 from the relay WTRU at 212. Based on previous security procedures, the DCR message may also include security parameters for network assistance and / or security parameters for no network assistance. Upon receiving the DCR message, if the state of relay WTRU 204 has changed (e.g., from IC to OoC when the DCR message was sent by source WTRU 202 and received at relay WTRU 204, and the DCR includes parameters for network assistance), relay WTRU 204 may send a DCReject message. Source WTRU 202 may send a new DCR message with the correct security parameters (e.g., no network assistance), unless a preference associated with the RSC exists.

[0083] Following the DCR message, the PC5 link and security between the source WTRU 202 and the relay WTRU 204 can be established as defined by various 3GPP radio standards.

[0084] If discovery is integrated into the PC5 link establishment (i.e., no independent discovery), the source WTRU can know the status of the relay WTRU, and if the source WTRU includes incorrect security parameters in its DCR message, the relay WTRU can send a DCReject message with a reason code indicating the relay WTRU's coverage status and / or an indication of whether network-assisted security parameters are expected. Based on the reason code and / or RSC indicator, the source WTRU can send a new DCR message with appropriate parameters to the same relay.

[0085] Figure 3 The figure illustrates an example of a relay WTRU status detection process without independent discovery.

[0086] In 310, the source WTRU 302, trunk WTRU 304, and target WTRU 306 may be equipped with one or more RSCs, which include a network-assisted security indicator that indicates whether a network-assisted security procedure or a non-network-assisted security procedure should be used. The source WTRU 302, trunk WTRU 304, and target WTRU 306 may be equipped with security materials to support IC and OoC scenarios.

[0087] At 312, source WTRU 302 can send a first DCR message to relay WTRU 304. The first DCR message can be based on an RSC with a security indicator, with or without a network assistance indicator (e.g., using parameters for network assistance, such as SUCI).

[0088] In section 314, the trunk WTRU 304 can determine whether to proceed with the next security establishment steps based on its coverage status and RSC network assistance support configuration. For example, if the received security parameters are compatible with the trunk WTRU's coverage status and the trunk's RSC configuration (e.g., RSC supports network assistance when the trunk is within coverage), the trunk WTRU 304 can proceed with conventional security establishment. Otherwise, the trunk WTRU 304 can proceed according to the procedure described below.

[0089] At 316, the source WTRU 302 can receive a DCReject message from the relay WTRU 304. The DCReject message may include a reason code indicating the coverage status of the relay WTRU 304 and / or the security parameters for expecting network assistance or not (e.g., "Relay status is OoC" when network assistance is expected).

[0090] In 318, the source WTRU 302 can send a second DCR message using security parameters, with or without network assistance, based on the DCReject message and reason code.

[0091] Alternatively, if more than one relay WTRU is available within the range of source WTRU 302, source WTRU 302 may wait for a period of time after sending the first DCR message before sending a new DCR message with different security parameters. For example, source WTRU 302 may initiate a timer called a DCR retransmission timer. While the timer is running, source WTRU 302 may receive DCA or DCReject messages from one or more relay WTRUs in the IC. If source WTRU 302 receives a DCA message from a relay WTRU, source WTRU 302 may stop the timer and may not send another DCR message. If source WTRU 302 receives a DCReject message from a relay WTRU, source WTRU 302 may retransmit the DCR message with security parameters based on the OoC indication from the relay WTRU when the timer expires.

[0092] At 320, following the second DCR message, the PC5 link and security between the source WTRU 302 and the relay WTRU 304 can be established as defined by various 3GPP radio standards.

[0093] In one embodiment, a control plane security (CP) procedure between the source WTRU and the relay WTRU can be used to utilize network assistance. For example, at 316, if the procedure fails because the serving network does not support the CP procedure, the relay WTRU 304 can send a DCReject message, which instructs the source WTRU 302 to send a second DCR message to the relay WTRU 304 using non-network-assisted security parameters instead of searching for another relay.

[0094] Figure 4 The diagram illustrates an example of a secure establishment process between a target WTRU and a relay WTRU.

[0095] At 410, the source WTRU 402, trunk WTRU 404, and destination WTRU 406 may be equipped with one or more RSCs, which include a network-assisted security indicator that indicates whether a security procedure with or without network assistance should be used. The source WTRU 402, trunk WTRU 404, and destination WTRU 406 may be equipped with security materials to support IC and OoC scenarios. Alternatively, the list of RSCs may include all RSCs with a preferred order and associated state (e.g., IC, OoC, or any other state).

[0096] In 412, the source WTRU 402 and the relay WTRU 404 can select a security process (e.g., both are ICs, and there is a network auxiliary preference indication for RSC).

[0097] At 414, relay WTRU 404 (which is in the IC) can send a DCR message to target WTRU 406. The DCR message can trigger the IC's security procedure selection and can include indications that relay WTRU 404 is within coverage and / or has network assistance or does not have network assistance indicators.

[0098] At 416, target WTRU 406 may send a DCReject message in response to a DCR message from relay WTRU 404. This message contains a reason code indicating that target WTRU 406 may initiate a DCR. Relay WTRU 404 may start a timer to receive the expected new DCR from target WTRU 406.

[0099] At 418, the target WTRU 406 can send DCR messages, which include security parameters related to the establishment of network-assisted security.

[0100] At 420, following the DCR message, security can be established between the target WTRU406 and the relay WTRU404 as described in various 3GPP radio standards.

[0101] Figure 5 The diagram illustrates an example of the process used for status indication during discovery. At 502, the first WTRU can receive one or more RSCs from the network, each of which includes a Network Auxiliary Security Indicator (RAS). At 504, the first WTRU can select a first RSC from the one or more RSCs, where the selection of the first RSC is based on a first RSC associated with a first RSC and the network coverage status of the first WTRU. At 506, if the network coverage status of the first WTRU is not within coverage, the first WTRU can send a discovery message to a second WTRU. The discovery message may include the first RSC. At 508, the first WTRU can receive a DCR message from the second WTRU. The DCR message may include a second RSC, which may be the same as the first RSC. The first WTRU may be a relay WTRU, and the second WTRU may be a source WTRU.

[0102] Figure 6The diagram illustrates an example of the process used for status indication during discovery. At 602, the first WTRU can receive one or more Relay Service Codes (RSCs) from the network, each of which includes a network-assisted security indicator. At 604, the first WTRU can receive a discovery message from the second WTRU, which includes the first RSC. At 606, the first WTRU can send a Direct Communication Request (DCR) message to the second WTRU, which includes the first RSC and security parameters based on the network-assisted security indicator. The first WTRU can be the source WTRU, and the second WTRU can be the target WTRU.

[0103] Although the features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented in a computer program, software, or firmware contained in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital multifunction discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, terminal, base station, RNC, or any host.

Claims

1. A method performed by a first wireless / transmitter-receiver unit (WTRU), the method comprising: Receive one or more Relay Service Codes (RSCs) from the network, each of the one or more RSCs including a network auxiliary security indicator; A first RSC is selected from the one or more RSCs, wherein the selection of the first RSC is based on a first network auxiliary security indicator associated with the first RSC and the network coverage status of the first WTRU; If the network coverage status of the first WTRU is out of coverage, a discovery message is sent to the second WTRU, the discovery message including the first RSC; as well as Receive a Direct Communication Request (DCR) message from the second WTRU, wherein the DCR message includes a second RSC.

2. The method according to claim 1, wherein the first WTRU is a relay WTRU.

3. The method of claim 1, wherein the second WTRU is a source WTRU.

4. The method according to claim 1, further comprising: The DCR message is accepted based on the first network auxiliary security indicator and the network coverage status of the first WTRU.

5. The method according to claim 1, wherein the second RSC is the same as the first RSC.

6. The method according to claim 1, wherein, The DCR message includes security parameters for network-assisted security procedures.

7. The method according to claim 1, wherein, The DCR message includes security parameters for a network-unassisted security procedure.

8. A first wireless / transmitter-receiver unit (WTRU), comprising: processor; and transceiver; The processor and transceiver are configured as follows: Receive one or more Relay Service Codes (RSCs) from the network, each of the one or more RSCs including a network auxiliary security indicator; A first RSC is selected from the one or more RSCs, wherein the selection of the first RSC is based on a first network auxiliary security indicator associated with the first RSC and the network coverage status of the first WTRU; If the network coverage status of the first WTRU is out of coverage, a discovery message is sent to the second WTRU, the discovery message including the first RSC; and Receive a Direct Communication Request (DCR) message from the second WTRU, wherein the DCR message includes a second RSC.

9. The first WTRU of claim 8, wherein the first WTRU is a relay WTRU.

10. The first WTRU of claim 8, wherein the second WTRU is a source WTRU.

11. The first WTRU according to claim 8, wherein, The processor and transceiver are also configured to: The DCR message is accepted based on the first network auxiliary security indicator and the network coverage status of the first WTRU.

12. The first WTRU according to claim 8, wherein the second RSC is the same as the first RSC.

13. The first WTRU according to claim 8, wherein, The DCR message includes security parameters for network-assisted security procedures.

14. The first WTRU according to claim 8, wherein, The DCR message includes security parameters for a network-unassisted security procedure.

15. A method performed by a first wireless transmit / receive unit (WTRU), the method comprising: Receive one or more Relay Service Codes (RSCs) from the network, each of the one or more RSCs including a network auxiliary security indicator; Receive a discovery message from the second WTRU, which includes the first RSC; and Send a Direct Communication Request (DCR) message to the second WTRU, which includes a second RSC.

16. The method of claim 15, wherein the first WTRU is a source WTRU.

17. The method according to claim 15, wherein, The second WTRU is a relay WTRU.

18. The method according to claim 15, wherein, The DCR message includes security parameters for network-assisted security procedures.

19. The method according to claim 15, wherein, The DCR message includes security parameters for a network-unassisted security procedure.

20. The method of claim 15, wherein the second RSC is the same as the first RSC.

21. A first wireless / transmitter-receiver unit (WTRU), comprising: processor; and transceiver; The processor and transceiver are configured as follows: Receive one or more Relay Service Codes (RSCs) from the network, each of the one or more RSCs including a network auxiliary security indicator; Receive a discovery message from the second WTRU, which includes the first RSC; and Send a Direct Communication Request (DCR) message to the second WTRU, the DCR message including a second RSC.

22. The first WTRU of claim 21, wherein the first WTRU is a source WTRU.

23. The first WTRU of claim 21, wherein the second WTRU is a target WTRU.

24. The first WTRU according to claim 21, wherein, The DCR message includes security parameters for network-assisted security procedures.

25. The first WTRU according to claim 21, wherein, The DCR message includes security parameters for a network-unassisted security procedure.

26. The first WTRU of claim 21, wherein the second RSC is the same as the first RSC.

Images