Enabling delivery of nas-based sms to human users based on user identity

Abstract

Systems, methods, and instrumentalities are disclosed herein for identifying a user (e.g., an active user) and delivering non-access stratum (NAS)-based short message service (SMS). For example, an apparatus can receive a registration message from a wireless transmit / receive unit (WTRU). Based on the registration message, the apparatus can determine whether a user identifier (e.g., a user identity (ID)) associated with a user has been identified. Based on a determination that the user identifier associated with the user has been identified, the apparatus can obtain SMS subscription information associated with the user. The apparatus can configure a short message service function. The apparatus can send a response message to the WTRU. For example, the response message can indicate that NAS-based SMS is allowed.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application 63 / 570,282, filed March 27, 2024, the contents of which are incorporated herein by reference. Background Technology

[0002] Mobile communications using wireless communication continue to evolve. The fifth-generation mobile communication radio access technology (RAT) can be referred to as 5G New Radio (NR). Previous-generation (traditional) mobile communication RATs could be, for example, fourth-generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This document discloses systems, methods, and means for identifying users (e.g., active users) and delivering Short Message Service (SMS) based on Non-Access Stratum (NAS). For example, an apparatus may include a processor configured to perform one or more of the following.

[0004] The device may receive registration messages from a Wireless Transmit / Receive Unit (WTRU). The device may be an Access and Mobility Management Function (AMF) or associated with an AMF. In some examples, the registration message (e.g., a registration message from a WTRU) may indicate support for NAS-based SMS (e.g., support for delivering NAS-based SMS). The registration message may include a Subscription Permanent Identifier (SUPI) and / or information associated with the SUPI.

[0005] Based on the registration message, the device can determine whether a user identifier (e.g., user ID) associated with a user has been identified. For example, the identified user could be an active user using the WTRU. The device can send a request message to the User Data Repository (UDR) and / or User Data Management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include a SUPI associated with the WTRU. The device can receive a response message from the UDR and / or UDM. For example, the response message may include SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., can be configured to indicate) that NAS-based SMS (e.g., allowing the delivery of NAS-based SMS) is permitted for a user identifier (e.g., user ID) associated with an active user using the WTRU.

[0006] In some examples, based on determining that a user identifier (e.g., user ID) associated with a user has been identified, the device can obtain SMS subscription information associated with that user. In some examples, based on determining that a user identifier (e.g., user ID) associated with an active user has not yet been identified, the device can send a response message (e.g., a second response message) to the WTRU. For example, the second response message could indicate that NAS-based SMS is not allowed (e.g., NAS-based SMS delivery is not allowed).

[0007] The device can be configured with a Short Message Service Function (SMSF). For example, the device can use a user identifier (e.g., user ID) to determine and configure the SMSF. The device can send a service activation request message. The service activation request message can request (e.g., can be configured to request) activation of a NAS-based SMS service associated with an active user. The service activation request message may include a SUPI associated with a WTRU and an MSISDN associated with an active user using the WTRU. The device can receive a response message from the SMSF. The response message may include service activation information.

[0008] The device can send a response message to the WTRU. For example, the response message could indicate that NAS-based SMS is allowed.

[0009] In some examples, the device may authenticate a user identifier (e.g., user ID) associated with the user, for example, with at least one of the UDR and UDM. The user may be an active user using the WTRU. The device may determine that authentication was successful. Based on the successful authentication, the device may obtain at least one of user profile information and SMS subscription data. For example, the user profile information may include at least one of a General Public Subscription Identifier (GPSI) associated with the active user and a Mobile Subscriber Integrated Services Digital Network Number (MSISDN). For example, the SMS subscription data may be associated with at least one of the UDR and UDM. Attached Figure Description

[0010] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0011] Figure 1B This illustrates that, according to one embodiment, it is possible to Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used in the communication system shown.

[0012] Figure 1C This illustrates that, according to one embodiment, it is possible to Figure 1AThe system diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used in the communication system shown.

[0013] Figure 1D This illustrates that, according to one embodiment, it is possible to Figure 1A The system diagram shows another exemplary RAN and another exemplary CN used in the communication system shown.

[0014] Figure 2 An example of delivering a Short Message Service (SMS) based on the Non-Access Layer (NAS) to a user (e.g., an active human user) is shown.

[0015] Figure 3 This example illustrates how delivery of NAS-based SMS is restricted if a WTRU user (e.g., a human user) logs out.

[0016] Exemplary network for implementing embodiments Figure 1A This diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting 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 DFT Extended OFDM (ZT-UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0017] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Any of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include 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 MiFi 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 may be interchangeably referred to as a UE.

[0018] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), NodeBs, eNodeBs, home NodeBs, home eNodeBs, gNBs, NR NodeBs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0019] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may 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 per 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.

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

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

[0022] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-A Advanced (LTE-A) and / or LTE-A Pro Advanced (LTE-A Pro) to establish air interface 116.

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

[0024] 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, for instance, use a dual connectivity (DC) principle to implement both LTE and NR radio access. 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).

[0025] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA 2000 1X, CDMA 2000 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), GSMEDGE (GERAN), etc.

[0026] Figure 1ABase station 114b can be, for example, a wireless router, a home NodeB, a home eNodeB, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, 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, CDMA 2000, GSM, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

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

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

[0029] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers to communicate 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 can use cellular-based radio technology, and with base station 114b, which can use IEEE 802 radio technology.

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

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

[0032] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, 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.

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

[0034] 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 multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via various RATs, such as NR and IEEE 802.11.

[0035] The processor 118 of 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) 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, keyboard 126, and / or display / touchpad 128. Additionally, the processor 118 may access information from any type of suitable memory and store data in said 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 may access information from memory that is not physically located on WTRU 102 (e.g., located on a server or home computer (not shown)) and store data in said memory.

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

[0037] 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) about the current location of the WTRU 102. In addition to, or alternatively to, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more neighboring 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.

[0038] The processor 118 may also be 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 video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which 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, gesture sensors, biometric sensors, and / or humidity sensors.

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

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

[0041] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but 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 to communicate with WTRUs 102a, 102b, and 102c via 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.

[0042] 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 via the X2 interface.

[0043] 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 (or PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0045] The SGW 164 can connect to each 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 handover between eNode Bs, triggering paging when DL data is available to WTRUs 102a, 102B, and 102c, managing and storing the context of WTRUs 102a, 102B, and 102c, etc.

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

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

[0048] Although WTRU is Figures 1A to 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.

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

[0050] 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 distribution system (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the STA via the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. This peer-to-peer traffic can be sent between the source and destination STAs (e.g., directly between the source and destination STAs) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode cannot have access points (APs), 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 as the "ad-hoc" communication mode in this document.

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

[0052] 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 to form a 40 MHz wide channel.

[0053] 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; this can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the 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).

[0054] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. 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 may support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities including support for certain and / or limited bandwidths (e.g., only support). MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0055] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel can have a bandwidth 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 the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the 802.11ah example, for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices), the primary channel can be 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 Assignment Vector (NAV) settings can 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, the entire available band can be considered busy even if most of the band remains idle and available.

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

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

[0058] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c includes one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via 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, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to 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 one embodiment, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

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

[0060] 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 needing to access 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, and also with another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate essentially 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 serve as mobility anchors for WTRUs 102a, 102b, and 102c, while gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0061] 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 fragmentation support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0062] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and may include data networks (DN) 185a, 185b. While each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0063] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 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 PDU sessions with different needs), selecting specific SMF 183a and 183b, managing registration areas, terminating 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 type of service being used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and services for Machine Type Communication (MTC) access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies (such as WiFi)).

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

[0065] UPF 184a and 184b can connect to one or more of gNB 180a, 180b, and 180c in RAN 113 via the N3 interface. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0066] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 may 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 can be connected to DNs 185a and 185b via UPFs 184a and 184b through their N3 interfaces and the N6 interface between UPFs 184a and 184b and local data networks (DNs) 185a and 185b.

[0067] Given Figures 1A to 1D and Figures 1A to 1D As described herein, one or more of the functions described with respect to one or more of the following 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-b, UPF184a-b, SMF 183a-b, DN 185a-b, and / or any other device 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.

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

[0069] One or more simulation devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices can be used in test scenarios within a test laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to perform testing of one or more components. One or more simulation devices can be test equipment. Simulation devices can 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).

[0070] This document discloses systems, methods, and means for identifying users (e.g., active users) and delivering Short Message Service (SMS) via Non-Access Stratum (NAS). For example, an apparatus may include a processor configured to perform one or more of the following.

[0071] The device may receive registration messages from a Wireless Transmit / Receive Unit (WTRU). The device may be an Access and Mobility Management Function (AMF) or associated with an AMF. In some examples, the registration message (e.g., a registration message from a WTRU) may indicate support for NAS-based SMS (e.g., support for delivering NAS-based SMS). The registration message may include a Subscription Permanent Identifier (SUPI) and / or information associated with the SUPI.

[0072] Based on the registration message, the device can determine whether a user identifier (e.g., user ID) associated with a user has been identified. For example, the identified user could be an active user using the WTRU. The device can send a request message to the User Data Repository (UDR) and / or User Data Management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include a SUPI associated with the WTRU. The device can receive a response message from the UDR and / or UDM. For example, the response message may include SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., can be configured to indicate) that NAS-based SMS (e.g., allowing the delivery of NAS-based SMS) is permitted for a user identifier (e.g., user ID) associated with an active user using the WTRU.

[0073] In some examples, based on determining that a user identifier (e.g., user ID) associated with a user has been identified, the device can obtain SMS subscription information associated with that user. In some examples, based on determining that a user identifier (e.g., user ID) associated with an active user has not yet been identified, the device can send a response message (e.g., a second response message) to the WTRU. For example, the second response message could indicate that NAS-based SMS is not allowed (e.g., NAS-based SMS delivery is not allowed).

[0074] The device can be configured with a Short Message Service Function (SMSF). For example, the device can use a user identifier (e.g., user ID) to determine and configure the SMSF. The device can send a service activation request message. The service activation request message can request (e.g., can be configured to request) activation of a NAS-based SMS service associated with an active user. The service activation request message may include a SUPI associated with a WTRU and an MSISDN associated with an active user using the WTRU. The device can receive a response message from the SMSF. The response message may include service activation information.

[0075] The device can send a response message to the WTRU. For example, the response message could indicate that NAS-based SMS is allowed.

[0076] In some examples, the device may authenticate a user identifier (e.g., user ID) associated with the user, for example, with at least one of the UDR and UDM. The user may be an active user using the WTRU. The device may determine that authentication was successful. Based on the successful authentication, the device may obtain at least one of user profile information and SMS subscription data. For example, the user profile information may include at least one of a General Public Subscription Identifier (GPSI) associated with the active user and a Mobile Subscriber Integrated Services Digital Network Number (MSISDN). For example, the SMS subscription data may be associated with at least one of the UDR and UDM.

[0077] Access and Mobility Management Functions (AMFs) can be configured (e.g., to take action) to enable the delivery of Non-Access Stratum (NAS) based Short Message Service (SMS) to users (e.g., human users and / or active users). For example, as described herein, a device can be configured to perform one or more of the following. The device may include an AMF and / or be associated with an AMF.

[0078] AMF can perform one or more of the following steps. Figure 2 This illustrates an example of delivering NAS-based SMS to active users (e.g., active human users).

[0079] like Figure 2 As shown, the AMF can receive messages (e.g., registration messages). For example, the AMF can receive a registration request (e.g., a registration request message) from the WTRU. The registration request (e.g., the registration message) may be an indication to request access to an SMS service or may include such an indication. For example, the registration message (e.g., a registration message from the WTRU) may indicate support for NAS-based SMS services (e.g., support for delivering NAS-based SMS). The registration request may be a user identifier or may include (e.g., may also include) a user identifier. For example, the registration message may include a Subscription Persistent Identifier (SUPI) and / or information associated with the SUPI.

[0080] As described herein, based on the registration message, the device can determine whether a user identifier (e.g., user ID) associated with a user has been identified. For example, the user to be identified could be an active user using the WTRU. The device can send a request message to the User Data Repository (UDR) and / or User Data Management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include a SUPI associated with the WTRU. The device can receive a response message from the UDR and / or UDM. For example, the response message may include SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., can be configured to indicate) that NAS-based SMS services (e.g., allowing the delivery of NAS-based SMS) are permitted for a user identifier (e.g., user ID) associated with an active user using the WTRU.

[0081] In some examples, based on determining that a user identifier (e.g., user ID) associated with a user has been identified, the device can retrieve SMS subscription information associated with that user. In some examples, based on determining that a user identifier (e.g., user ID) associated with an active user has not yet been identified, the device can send a response message (e.g., a second response message) to the WTRU. For example, the second response message could indicate that NAS-based SMS services are not allowed (e.g., NAS-based SMS delivery is not allowed).

[0082] In some examples, such as Figure 2 As shown, the AMF can send messages (e.g., indication and / or response messages) to the WTRU. For example, the AMF can send a response message (e.g., an indication) to the WTRU. The response message could indicate that access to the SMS service is not permitted because no user is authenticated to use the WTRU.

[0083] In some examples, such as Figure 2 As shown, the AMF can detect that a user identifier (e.g., user ID) has been authenticated and can obtain user profile information, such as the user's Common Public Subscription Identifier (GPSI) or Integrated Services Digital Network Number (MSISDN). The AMF can retrieve SMS subscription data for the WTRU and the user with the user identifier (e.g., user ID) from, for example, the User Data Repository (UDR) and / or User Data Management (UDM). The MSISDN can be a type of GPSI.

[0084] like Figure 2As shown, the AMF can select (e.g., configure) a Short Message Service Function (SMSF) and / or activate a NAS-based SMS service for the user within the SMSSF. The user identifier can be an input to the SMSSF selection process. The AMF can send a Subscription Permanent Identifier (SUPI) and / or a user identifier to the SMSSF. The SUPI can be the subscription identifier of the WTRU. The International Mobile Subscriber Identifier (IMSI) can be a type of SUPI. For example, as described herein, the device can configure the SMSSF. The device can send a Service Activation Request message. The Service Activation Request message can request (e.g., can be configured to request) activation of the NAS-based SMS service associated with the active user. The Service Activation Request message can include the SUPI associated with the WTRU and the MSISDN associated with the active user using the WTRU.

[0085] like Figure 2 As shown, the AMF can receive service activation information from the SMSF. For example, the device can receive a response message from the SMSF. The response message may include service activation information.

[0086] like Figure 2 As shown, the AMF can send a response message (e.g., a response) to the WTRU. For example, the AMF can send a response message to the WTRU informing the WTRU that NAS-based SMS is allowed and / or activated for an active user with a provided user identifier (e.g., a provided user ID). For example, the device can send a response message to the WTRU. For example, the response message can indicate that NAS-based SMS is allowed.

[0087] In some examples, the device may, for example, use at least one of a UDR and a UDM to authenticate a user identifier (e.g., a user ID) associated with the user. The user may be an active user using the WTRU. The device may determine that authentication was successful. Based on the successful authentication, the device may obtain at least one of user profile information and SMS subscription data. For example, the user profile information may include at least one of a General Public Subscription Identifier (GPSI) associated with the active user and a Mobile Subscriber Integrated Services Digital Network Number (MSISDN). For example, the SMS subscription data may be associated with at least one of a UDR and a UDM.

[0088] In a system (such as a 5G system), one or more user identifiers may be used.

[0089] For example, in a system (such as a 5G system), one or more operators can be configured to leverage one or more user-specific identities within a network (such as a 3GPP network) to deliver customized services based on those user identities. A user identity could be the identity of a human using a WTRU (e.g., an active user) and / or the identity of an application running on the WTRU and / or the identity of a device behind the WTRU gateway.

[0090] You can define (e.g., specify) one or more service level parameters (e.g., requirements) and / or define that are related to a user profile and / or user identity.

[0091] Authentication can be configured (e.g., 3GPP secondary authentication). For example, 3GPP secondary authentication can be configured by a third party.

[0092] The secondary authentication process can be (for example, may include) authenticating the WTRU. For example, the secondary authentication process can be, for instance, authentication of the WTRU by a third-party authentication server via an intermediate function in the core network (e.g., 5GC). For example, authentication can be performed by a Session Management Function (SMF), an AMF, or a Network Open Function (NEF). One or more of these processes can be referred to as PDU Session Secondary Authentication and Authorization (A&A), Network Slice Specific Authentication and Authorization (NSSAA), and / or Unmanned Aerial Vehicle (UAV) Unmanned Aerial Vehicle System Service Provider (USS) Authentication and Authorization (UUAA). The WTRU may use a non-3GPP user identity and / or credentials during the authentication and authorization process before obtaining authorized access to network resources (e.g., Protocol Data Unit (PDU) sessions, network slices, or data networks (DNs)).

[0093] SMS can be sent via NAS. For example, during the registration process (e.g., in 5GS), to enable NAS-based SMS delivery, the WTRU may include an SMS support indication (e.g., a supported SMS indication) in the registration request (e.g., a registration request message). For example, as described herein, the AMF can receive a registration message (e.g., a registration request message) from the WTRU. The supported SMS indication in the registration request can indicate the WTRU's ability to support NAS-based SMS delivery. The WTRU may include one or more subscriber identifiers (e.g., Subscription Hidden Identifier (SUCI), 5G Globally Unique Temporary Identifier (5G-GUTI), and / or Permanent Device Identifier (PEI)) for identifying the WTRU. The supported SMS indication can indicate whether the WTRU supports NAS-based SMS delivery.

[0094] AMF can retrieve SMS subscription data and / or WTRU context. For example, AMF can retrieve SMS subscription data and / or WTRU context from an SMSF, for example, using Nudm_SDM_Get. AMF can also retrieve subscription data (e.g., including Network Slice Selection Auxiliary Information (NSSAI)) for a WTRUSUPI (e.g., any given WTRU SUPI) by querying a UDM (e.g., using the Nudm_SDM_Get service (SDM = SubscriberDataManagement)).

[0095] The UDM can retrieve information from the UDR. If the stored SMSF belongs to the same Public Land Mobile Network (PLMN) as the AMF, the UDM can include the SMSF information in a message (e.g., a response message, such as the Nudm_SDM_Get response message). Upon receiving a successful response and if SMS service is permitted, the AMF can subscribe to receive notifications if the SMS subscription data is modified and / or when the SMS subscription data is modified.

[0096] If the registration request includes an SMS support indication, the AMF can examine the SMS subscription data. For example, the AMF can examine the SMS subscription data to determine whether SMS service is permitted for the WTRU. If SMS service is permitted and the received WTRU context includes an available SMSF for the serving PLMN, the AMF can activate the SMSF address and / or continue the registration process. If SMS service is permitted but no SMSF for the serving PLMN is received, the AMF can discover and / or select an SMSF to serve the WTRU.

[0097] The AMF can invoke operations from the SMSF (e.g., the Nsmsf_SMService_Activate service operation). The invocation may include one or more of the following: AMF address, access type, radio access technology (RAT) type, tracking request, General Public Subscription Identifier (GPSI) (if available), and / or SUPI. The AMF can use SMSF information to invoke the operation.

[0098] If the WTRU context for the current access type exists (e.g., already exists) in the SMSF, the SMSF can replace the old AMF address with the new AMF address. If the WTRU context for the current access type does not exist in the SMSF, the SMSF can treat the WTRU context as a registration request from a new access type, and the SMSF can register with the UDM, for example, using Nudm_UECM_Registration with the access type. Therefore, the UDM can store the following information: SUPI, SMSF identity and / or SMSF address, and the access type in the WTRU context within the SMSF data. The UDM can also store SMSF information in the User Data Repository (UDR), for example, using (e.g., via) Nudr_DM_Update (e.g., SUPI, subscription data, and / or the WTRU context in the SMSF data).

[0099] like Figure 2 As shown, the SMSF can, for example, use Nudm_SDM_Get to retrieve SMS management subscription data (e.g., SMS telecom services, SMS ban lists, and / or similar items). Retrieving SMS management subscription data can be configured (e.g., required) for the UDM to obtain information from the UDR using (e.g., via) Nudr_DM_Query (e.g., SUPI, subscription data, SMS management subscription data, and / or similar items).

[0100] SMSF can respond to AMF, for example, with an Nsmsf_SMService_Activate service operation response message. For example, as... Figure 2 As shown, the SMSF can send a response message to the AMF. The AMF can store the received SMSF information as part of the WTRU context.

[0101] AMF can include, for example, an SMS permission instruction to be sent to WTRU in the registration acceptance message.

[0102] NAS-based SMS can be delivered based on user identifiers (e.g., user ID).

[0103] As described herein, if a user with User ID #1 intends to use the WTRU, the WTRU can send a request to the AMF (e.g., a registration request including User ID #1). The AMF can notify the SMSF that SMS activation needs to be updated from subscriber to user_ID #1. The AMF can provide the SMSF with User_ID #1 and / or User_ID #1's GPSI. The AMF may not need to check the SMS subscription data of the user with User_ID #1.

[0104] As described herein, the AMF can discover and / or select SMSFs, for example, to serve human users (e.g., user identifiers) via WTRU. The AMF may disregard the SMS subscription policy for said user.

[0105] In a system (e.g., a 5G system), subscriptions associated with human users may be unidentifiable, and / or may be unable to deliver NAS-based SMS to human users who may be using a WTRU. For example, the system may not know the identity of users (e.g., humans) who may be using a WTRU to send and receive NAS-based SMS.

[0106] Subscribed human users may be identified (e.g., may need to be identified as described herein), and the focus is on how to deliver NAS-based SMS to human users if they access the service via a system (e.g., 5GS) using a user identifier.

[0107] Networks (such as 5G core networks) may be able to identify human users and / or deliver SMS to active users using WTRUs via NAS (e.g., NAS messages).

[0108] If a user logs into the device, the WTRU can register using a user identifier (e.g., user ID) and can instruct the device to support SMS. A system (such as a 5GS) can authenticate the user identifier (e.g., user ID) and obtain SMS subscription policy information associated with that user identifier (e.g., user ID). If permitted, the system (e.g., 5GS) and / or AMF can select an SMSF and configure it with the user's MSISDN / GPSI and / or routing information. This selection and / or configuration can allow the use of the SMS that the WTRU wants to deliver to the user.

[0109] SMS can be enabled or disabled for a WTRU, for example, based on the user of the WTRU. For instance, if a user is authenticated to use the WTRU, the SMS function can be disabled or enabled based on information from the user's identity profile. This document may describe one or more exemplary processes: the WTRU may provide a user identifier in a registration request (e.g., a registration message); the network may authenticate the user; and / or the network may indicate to the WTRU whether the user is authorized to use the SMS function on the WTRU.

[0110] In one or more exemplary processes described herein, the network may send an indication in a message (e.g., a registration message and / or a registration acceptance message) indicating whether a user is authorized to use SMS functionality. In one example, the indication of whether the user is allowed to use SMS may be sent in a message (e.g., a WTRU configuration update message). Sending the indication in a configuration update message may be useful if the user has not yet been authenticated when the network sends the registration acceptance message. For example, the process of authenticating a user may be a separate Extensible Authentication Protocol (EAP) process from the registration process.

[0111] If a user logs in with a user identifier (e.g., user ID) and indicates that SMS is supported, the AMF can authenticate the user identifier (e.g., user ID).

[0112] AMF can determine a user's SMS subscription information based on a user identifier (e.g., user ID). AMF can obtain this information from a user profile, the user's GPSI, or MSISDN.

[0113] AMF can select and / or configure SMSF to receive NAS-based SMS, for example, by providing routing information and / or user identifier information (e.g., user ID information) (e.g., MSISDN or GPSI).

[0114] NAS-based SMS can be delivered to users (such as active human users). Figure 2 This illustrates an example of delivering NAS-based SMS to active human users. For example, Figure 2 An exemplary process can be provided on how to deliver NAS-based SMS messages based on active human users logged into the device. This process may or may not be performed (e.g., it can be skipped). Figure 2 One or more processes are shown.

[0115] like Figure 2As shown, WTRU SMS subscriptions can be modified and / or updated to include, for example, additional information about the WTRU and / or SUPI. For example, UDM and / or UDR can update WTRU SMS subscriptions. UDM and / or UDR can update WTRU SMS subscriptions to include indications that NAS-based SMS may not be allowed if there are no active users, and / or indications that SMS may be allowed for one or more specific active users. For example, SMS management subscription data in UDM / UDR can be updated with one or more of the following: SMS management subscription data can be updated to include indications that NAS-based SMS is not allowed if a user identifier is not authenticated to use the WTRU; and / or SMS management subscription data can be updated to include indications that NAS-based SMS is allowed (e.g., allowed only) if one or more specific users are authenticated to use the WTRU. For example, the identity of users allowed to use NAS-based SMS with the WTRU can be included in the SMS management subscription data.

[0116] During the initial startup of WTRU, if no users are active, WTRU can initiate (e.g., execute) a registration process, such as... Figure 2 As shown.

[0117] A WTRU may attempt to register with the AMF. For example, a WTRU may attempt to register with the AMF by sending a message (e.g., a registration message). This registration message may include, for example, a subscription identifier (e.g., SUPI) associated with the WTRU. The WTRU may indicate that there are no active users at this time by sending an indication (e.g., a flag indicating no user identifier, e.g., no user ID). The WTRU may indicate that it supports NAS-based SMS, for example, by sending an indication to the AMF in the registration message (e.g., an SMS SUPPORTED FLAG).

[0118] like Figure 2 As shown, the AMF can retrieve SMS subscription data from the UDM / UDR. Requests from the AMF may include the SUPI of the WTRU.

[0119] UDM / UDR can retrieve subscription information based on SUPI. UDM can respond to AMF by including SMS subscription information. SMS subscription information can include at least one of the following: an indication that NAS-based SMS is not allowed if a user identifier (e.g., user ID) does not exist; an indication that NAS-based SMS is not allowed if a user identifier (e.g., user ID) is inactive; an indication that NAS-based SMS is not allowed if a user identifier (e.g., user ID) is not authenticated; or an indication that NAS-based SMS is allowed (e.g., allowed only) for one or more specific users.

[0120] like Figure 2 As shown, the AMF can store and parse subscription information. Since no user is active, the AMF can determine that the WTRU is not allowed to use the NAS-based SMS service. The AMF can activate and / or subscribe to (e.g., optionally activate and / or subscribe to) the SMSF for future use. The AMF can keep the SMSF active in advance for future use. The AMF can indicate that SMS is restricted. The AMF can subscribe to the SMSF to be notified when an SMS is received for the WTRU and / or for another user. The AMF can take action to notify the WTRU and / or user of an incoming SMS.

[0121] like Figure 2 As shown, the AMF can notify the WTRU by sending a message (such as a registration response message) that NAS-based SMS is not allowed because no user exists.

[0122] In some examples, user A can log in to WTRU, for instance, using a user identifier (e.g., user ID) = A. Figure 2 As shown, the WTRU can send messages (e.g., registration messages and / or registration request messages). These messages may include a subscription identifier (e.g., SUPI) associated with the WTRU. The WTRU can indicate (e.g., also indicate) that user A is active by including USER_ID=A. The WTRU can indicate that it supports NAS-based SMS by sending an indication to the AMF (e.g., an SMS SUPPORTED FLAG). The WTRU can include this indication of NAS-based SMS support in the registration message.

[0123] like Figure 2 As shown, the AMF can authenticate the user identifier A (e.g., USER_ID, such as user ID A) with the UDM / UDR. The AMF can obtain user profile information and retrieve the user's MSISDN.

[0124] If the AMF has already stored the SMS subscription information of the WTRU and the subscription has not changed, then skipping, for example... Figure 2 One or more processes are shown (e.g., process 10 and / or process 11). If the AMF does not store the SMS subscription information of the WTRU and / or the subscription has changed, the AMF can retrieve the SMS subscription data from the UDM / UDR. The AMF may include the WTRU's SUPI and / or the active user's USER_ID = A in the subscription retrieval request.

[0125] like Figure 2 As shown, the UDM / UDR can retrieve subscription information based on SUPI. The UDM can respond to the AMF. For example, the UDM / UDR can send a response message to the AMF. The response message may include SMS subscription information (e.g., an indication that NAS-based SMS is not allowed if there are no active users, and / or an indication that SMS is allowed for specific active users). The response and / or response message may include (e.g., further include) SMSF information.

[0126] The AMF can store SMS subscription information. The AMF can determine whether NAS-based SMS is permitted for the WTRU and / or the user (e.g., allowing the delivery of NAS-based SMS). Figure 2 As shown, the AMF can select (e.g., activate and / or configure) the SMSF from information (e.g., information from stored and / or parsed subscription information as described herein) and / or SMSF information (e.g., SMSF information received in response messages received from the UDM / UDR as described herein).

[0127] like Figure 2 As shown, the AMF can activate the NAS-based SMS service with the SMSF by sending a request (e.g., a service activation message and / or a service activation request message). The request and / or request message may include at least one of the AMF address, SUPI, and / or the MSISDN of user A.

[0128] like Figure 2 As shown, SMSF can retrieve SMS management subscription data.

[0129] like Figure 2 As shown, the SMSF can respond to the AMF, for example, indicating successful activation, and this response can include SMSF information. For example, the SMSF can send a message, such as a service activation response message.

[0130] like Figure 2 As shown, the AMF can notify the WTRU by sending a message (such as a registration response message) indicating that NAS-based SMS is allowed for USER = A.

[0131] Mobile Termination (MT) SMS can be configured.

[0132] like Figure 2 As shown, UDM / UDR can receive indications that a user is actively using a subscription associated with WTRU (e.g., the user is logged in and / or there is an active user).

[0133] The SMS Gateway Mobile Switching Center (SMS-GMSC) can receive SMS messages addressed to the WTRU's SUPI GPSI. As described herein, the SMS Service Center (SMS-SC) and / or SMS-GMSC can attempt to deliver the SMS message to the WTRU. The SMS-GMSC can send a request to the UDM / UDR (e.g., a request for the identity of the SMSF serving the WTRU). The WTRU may be in a registered management state (e.g., RM-REGISTERED state). The UDM / UDR can determine to respond to the SMS-GMSC with an indication that the WTRU is unavailable. The UDM / UDR can determine to indicate that the WTRU is unavailable because the UDM / UDR is configured to indicate that users currently logged into the WTRU are not allowed to receive one or more SMS messages sent to subscriptions associated with the WTRU. In some examples, the response message from the UDM / UDR to the SMS-GMSC may indicate that the SMS cannot be delivered because users currently using the subscription are not allowed to receive one or more SMS messages.

[0134] The SMS-GMSC can receive SMS messages addressed to a user's GPSI. As described herein, the SMS-SC and / or SMS-GMSC can attempt to deliver the SMS message to the user. The SMS-GMSC can send a request (e.g., a request message) to the UDM / UDR for the identity of the SMSF serving the WTRU (e.g., the WTRU the user is logged into). The UDM / UDR can respond, for example, with the identity of the SMSF serving the WTRU the user is logged into. In an example, the response message from the UDM / UDR to the SMS-GMSC may include the SUPI of the WTRU the user is logged into.

[0135] If a WTRU user (e.g., a human user) logs out, NAS-based SMS delivery may be restricted. Figure 3 This illustrates an exemplary process that suspends the delivery of NAS-based SMS to the human user if the user logs out from the WTRU. This process may or may not be executed (e.g., it may be skipped). Figure 3 One or more processes are shown.

[0136] like Figure 3 As shown, an active human user can log out from the WTRU. The WTRU can send messages (such as registration update messages and / or other NAS control plane signaling messages, such as uplink (UL) NAS transport messages). The messages can indicate that user A has logged out. The messages may include (for example, also include) the WTRU's SUPI. In some examples, the WTRU can indicate END (termination) or SUSPEND (suspension) of the NAS-based SMS service.

[0137] like Figure 3 As shown, the AMF can check whether user A / SUPI has an active NAS-based SMS service. If the AMF determines that user A / SUPI has an active NAS-based SMS service, the AMF can decide to terminate or suspend (e.g., temporarily suspend) the service. The AMF can select an SMSF (e.g., the SMSF currently serving the AMF).

[0138] like Figure 3 As shown, the AMF can send a request message (e.g., a service deactivation request message) to the SMSF. The request message (e.g., the service deactivation request message) may include one or more of the following: the AMF address, the WTRU subscription identifier SUPI, and / or similar items. The request message (e.g., the service deactivation request message) may indicate the reason for deactivation (e.g., a justification), such as user inactivity and / or the MSISDN of user A who has become inactive.

[0139] like Figure 3 As shown, the SMSF can process the request and update SMS service information. For example, the SMSF can update the SMS management subscription data in the UDM / UDR.

[0140] like Figure 3 As shown, the SMSF can notify the AMF, for example, that the service has been successfully deactivated. For instance, the SMSF can send a response message (e.g., a service deactivation response message) to the AMF. This service deactivation response message can indicate that service deactivation was successful.

[0141] like Figure 3 As shown, the AMF can notify the WTRU that NAS-based SMS for USER = A is no longer active and available. For example, the AMF can send a message (e.g., a deregistration message) to the WTRU. The deregistration message can indicate that NAS-based SMS is not allowed for user A or user_ID = A (e.g., delivery of NAS-based SMS is not allowed).

[0142] The processes described above can be implemented in computer programs, software, and / or firmware, which are incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or 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 memory devices, magnetic media (e.g., but not limited to internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., CD-ROMs and / or DVDs). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

1. An apparatus comprising: The processor is configured as follows: Receive registration messages from the Wireless Transmit / Receive Unit (WTRU); Based on the registration message, determine whether a user identifier associated with the user has been identified; Based on the user identifier that has been identified as being associated with the user, obtain the SMS subscription information associated with the user; Configure Short Message Service (SMSF); as well as A response message is sent to the WTRU, wherein the response message indicates that SMS based on the Non-Access Stratum (NAS) is permitted.

2. The device of claim 1, wherein the device includes an access and mobility management function (AMF).

3. The device according to claim 1 or 2, wherein the registration message indicates support for the NAS-based SMS.

4. The device according to any one of claims 1 to 3, wherein the registration message includes a Subscription Permanent Identifier (SUPI).

5. The device of claim 4, wherein the user is an active user using the WTRU, and wherein the processor is configured to determine whether the user identifier associated with the user has been identified, including: The processor is configured to: Send a request message to at least one of the User Data Repository (UDR) and User Data Management (UDM), wherein the request message includes a request to retrieve SMS subscription data, and wherein the request includes the SUPI associated with the WTRU; and Receive a response message from at least one of the UDR and the UDM, wherein the response message includes the SMS subscription information associated with the SUPI, wherein the SMS subscription information is configured to indicate that the NAS-based SMS is allowed for the user identifier associated with the active user using the WTRU.

6. The device according to any one of claims 1 to 5, wherein the processor is configured to: The user identifier associated with the user is authenticated by at least one of the UDR and UDM, wherein the user is the active user using the WTRU; The authentication was confirmed to be successful; as well as Based on the successful authentication, user profile information is obtained, wherein the user profile information includes at least one of the General Public Subscription Identifier (GPSI) and the Integrated Services Digital Network Number (MSISDN) associated with the active user.

7. The device according to any one of claims 1 to 6, wherein the processor is configured to configure the SMSF by: The processor is configured to: Send a service activation request message, wherein the service activation request message is configured to request activation of a NAS-based SMS service associated with the active user, and wherein the service activation request message includes a SUPI associated with the WTRU and an MSISDN associated with the active user using the WTRU; as well as Receive a response message from the SMSF, wherein the response message includes service activation information.

8. The device according to any one of claims 1 to 7, wherein the response message is a first response message, and wherein the processor is further configured to: Based on the determination that the user identifier associated with the active user has not yet been identified, a second response message is sent to the WTRU, wherein the second response message indicates that the NAS-based SMS is not allowed.

9. A method comprising: Receive registration messages from the Wireless Transmit / Receive Unit (WTRU); Based on the registration message, determine whether a user identifier associated with the user has been identified; Based on the user identifier that has been identified as being associated with the user, obtain the SMS subscription information associated with the user; Configure Short Message Service (SMSF); as well as A response message is sent to the WTRU, wherein the response message indicates that SMS based on the Non-Access Stratum (NAS) is permitted.

10. The method of claim 9, wherein the method is performed by the Access and Mobility Management Function (AMF).

11. The method of claim 9 or 10, wherein the registration message indicates support for the NAS-based SMS.

12. The method according to any one of claims 9 to 11, wherein the registration message includes a Subscription Permanent Identifier (SUPI).

13. The method of claim 12, wherein the user is an active user using the WTRU, wherein determining whether the user identifier associated with the active user has been identified comprises: Send a request message to at least one of the User Data Repository (UDR) and User Data Management (UDM), wherein the request message includes a request to retrieve SMS subscription data, and wherein the request includes the SUPI associated with the WTRU; and Receive a response message from at least one of the UDR and the UDM, wherein the response message includes the SMS subscription information associated with the SUPI, wherein the SMS subscription information is configured to indicate that the NAS-based SMS is allowed for the user identifier associated with the active user using the WTRU.

14. The method according to any one of claims 9 to 13, wherein the method comprises: The user identifier associated with the user is authenticated by at least one of the UDR and UDM, wherein the user is the active user using the WTRU; The authentication was confirmed to be successful; as well as Based on the successful authentication, user profile information is obtained, wherein the user profile information includes at least one of the General Public Subscription Identifier (GPSI) and the Integrated Services Digital Network Number (MSISDN) associated with the active user.

15. The method according to any one of claims 9 to 14, wherein configuring the SMSF comprises: Send a service activation request message, wherein the service activation request message is configured to request activation of a NAS-based SMS service associated with the active user, and wherein the service activation request message includes a SUPI associated with the WTRU and an MSISDN associated with the active user using the WTRU; as well as Receive a response message from the SMSF, wherein the response message includes service activation information.

Images