Enable SMS over NAS delivery to a human user based on user identity

Abstract

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

Description

ENABLE SMS OVER NAS DELIVERY TO A HUMAN USER BASED ON USER IDENTITYCROSS-REFERENCE TO RELATED APPLICATIONS

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

[0002] Mobile communications using wireless communication continue to evolve. A fifth generation of mobile communication radio access technology (RAT) may be referred to as 5G new radio (NR). A previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Systems, methods, and instrumentalities are disclosed herein for identifying a user (e.g., an active user) and delivering a short message service (SMS) over non-access stratum (NAS). For example, a device may include a processor configured to do one or more of the following.

[0004] The device may receive a registration message from a wireless transmit / receive unit (WTRU). The device may be, or may be associated with, an access and mobility management function (AMF). In some examples, the registration message (e.g., from the WTRU) may indicate that the SMS over NAS is supported (e.g., delivering the SMS over NAS is supported). 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 may determine whether a user identifier (e.g., user identification (ID)) associated with a user has been identified. For example, the user that is determined may be an active user using the WTRU. The device may send a request message to a user data repository (UDR) and / or a user data management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include the SUPI associated with the WTRU. The device may receive a response message from the UDR and / or the UDM. For example, the response message may include the SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., may be configured to indicate) that the SMS over NAS is allowed (e.g., delivering the SMSover NAS is allowed) for the user identifier (e.g., the user ID) associated with the active user using the WTRU.

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

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

[0008] The device may send a response message to the WTRU. For example, the response message may indicate that an SMS over NAS is allowed.

[0009] In some examples, the device may authenticate the user identifier (e.g., user ID) associated with the user, e.g., with at least one of a UDR or a UDM. The user may be the active user using the WTRU. The device may determine that the authentication is successful. Based on the determination that the authentication is successful, the device may obtain at least one of the user profile information or SMS subscription data. For example, the user profile information may include at least one of a generic public subscription identifier (GPSI) or a mobile subscriber integrated services digital network number (MSISDN) associated with the active user. For example, the SMS subscription data may be associated with at least one of a UDR or a UDM.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0011] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0012] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.

[0013] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0014] FIG. 2 illustrates an example of delivering a Short Message Service (SMS) over Non-Access Stratum (NAS) to a user (e.g., an active human user).

[0015] FIG. 3 illustrates an example of delivering an SMS over NAS being restricted if a user, such as a human user of a WTRU, logs out.EXAMPLE NETWORKS FOR IMPLEMENTATION OF THE EMBODIMENTS

[0016] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0017] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / orother wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0018] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the I nternet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0021] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 usingwideband 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 UL Packet Access (HSUPA).

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

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

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

[0025] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0026] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0027] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

[0030] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include 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 source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0031] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

[0034] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0035] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such asthe non-removable memory 130 and / or the removable memory 132. The 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. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

[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) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

[0038] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

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

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

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

[0042] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0043] The CN 106 shown in FIG. 1 C 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 are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

[0048] Although the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

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

[0050] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.

[0051] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with theAP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0052] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0053] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0054] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0055] WLAN systems, which may support multiple channels and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) thatsupport (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

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

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

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

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

[0060] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0061] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0062] The CN 115 shown in FIG. 1 D 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. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0063] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access,services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0064] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

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

[0066] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0067] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0068] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devicesmay perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0069] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be testing equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0070] Systems, methods, and instrumentalities are disclosed herein for identifying a user (e.g., an active user) and delivering a short message service (SMS) over non-access stratum (NAS). For example, a device may include a processor configured to do one or more of the following.

[0071] The device may receive a registration message from a wireless transmit / receive unit (WTRU). The device may be, or may be associated with, an access and mobility management function (AMF). In some examples, the registration message (e.g., from the WTRU) may indicate that the SMS over NAS is supported (e.g., delivering the SMS over NAS is supported). 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 may determine whether a user identifier (e.g., user identification (ID)) associated with a user has been identified. For example, the user that is determined may be an active user using the WTRU. The device may send a request message to a user data repository (UDR) and / or a user data management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include the SUPI associated with the WTRU. The device may receive a response message from the UDR and / or the UDM. For example, the response message may include the SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., may be configured to indicate) that the SMS over NAS is allowed (e.g., delivering the SMS over NAS is allowed) for the user identifier (e.g., the user ID) associated with the active user using the WTRU.

[0073] In some examples, based on a determination that the user identifier (e.g., user ID) associated with the user has been identified, the device may obtain SMS subscription information associated with theuser. In some examples, based on a determination that the user identifier (e.g., user ID) associated with the active user has not been identified, the device may send a response message (e.g., a second response message) to the WTRU. For example, the second response message may indicate that the SMS over NAS is not allowed (e.g., delivering the SMS over NAS is not allowed).

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

[0075] The device may send a response message to the WTRU. For example, the response message may indicate that an SMS over NAS is allowed.

[0076] In some examples, the device may authenticate the user identifier (e.g., user ID) associated with the user, e.g., with at least one of a UDR or a UDM. The user may be the active user using the WTRU. The device may determine that the authentication is successful. Based on the determination that the authentication is successful, the device may obtain at least one of the user profile information or SMS subscription data. For example, the user profile information may include at least one of a generic public subscription identifier (GPSI) or a mobile subscriber integrated services digital network number (MSISDN) associated with the active user. For example, the SMS subscription data may be associated with at least one of a UDR or a UDM.

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

[0078] An AMF may perform one or more of the following steps. FIG. 2 illustrates an example of delivering an SMS over NAS to an active user, such as an active human user.

[0079] As illustrated in FIG. 2, an AMF may receive a message, such as a registration message. For example, the AMF may receive a registration request (e.g., a registration request message) from a WTRU. The registration request (e.g., the registration message) may be, or may include an indication that access to an SMS Service is requested. For example, the registration message (e.g., from the WTRU) may indicate that the SMS over NAS service is supported (e.g., delivering the SMS over NAS is supported). The registration request may be, or may include (e.g., may also include) a user identifier. For example, theregistration message may include a subscription permanent identifier (SUPI) and / or information associated with the SUPI.

[0080] As described herein, based on the registration message, the device may determine whether a user identifier (e.g., user identification (ID)) associated with a user has been identified. For example, the user to de determined may be an active user using the WTRU. The device may send a request message to a user data repository (UDR) and / or a user data management (UDM). The request message may include a request to retrieve SMS subscription data. The request may include the SUPI associated with the WTRU. The device may receive a response message from the UDR and / or the UDM. For example, the response message may include the SMS subscription information associated with the SUPI. The SMS subscription information may indicate (e.g., may be configured to indicate) that the SMS over NAS service is allowed (e.g., delivering the SMS over NAS is allowed) for the user identifier (e.g., user ID) associated with the active user using the WTRU.

[0081] In some examples, based on a determination that the user identifier (e.g., user ID) associated with the user has been identified, the device may obtain SMS subscription information associated with the user. In some examples, based on a determination that the user identifier (e.g., user ID) associated with the active user has not been identified, the device may send a response message (e.g., a second response message) to the WTRU. For example, the second response message may indicate that the SMS over NAS service is not allowed (e.g., delivering the SMS over NAS is not allowed).

[0082] In some example, as illustrated in FIG. 2, the AMF may send a message (e.g., an indication and / or a response message) to the WTRU. For example, the AMF may send a response message (e.g., an indication) to the WTRU. The response message may indicate that access to the SMS Service is not allowed because no user has been authenticated to use the WTRU.

[0083] In some examples, as illustrated in FIG. 2, the AMF may detect that the user identifier (e.g., User ID) has been authenticated and may obtain user profile information, such as a Generic Public Subscription Identifier (GPSI) or a Mobile Subscriber Integrated Services Digital Network Number (MSISDN) of the user. The AMF may retrieve SMS subscription data, e.g., from a User Data Repository (UDR) and / or a User Data Management (UDM) for the WTRU and the user with the user identifier (e.g., the User ID). An MSISDN may be a type of GPSI.

[0084] As illustrated in FIG. 2, the AMF may select (e.g., configure) a Short Message Service Function (SMSF) and / or activate an SMS over NAS service for the user in the SMSF. The user identifier may be an input to the SMSF selection process. The AMF may send a Subscription Permanent Identifier (SUPI) and / or a user identifier to the SMSF. A SUPI may be a subscription identifier for a WTRU. An International Mobile Subscriber Identity (IMSI) may be a type of SUPI. For example, as described herein, the devicemay configure an SMSF. The device may send a service activate request message. The service activate request message may request (e.g., may be configured to request) an activation of the SMS over NAS service associated with the active user. The service activate request message may include a SUPI associated with the WTRU and an MSISDN associated with the active user using the WTRU.

[0085] As illustrated in FIG. 2, the AMF may receive service activation information from the SMSF. For example, the device may receive a response message from the SMSF. The response message may include service activation information.

[0086] As illustrated in FIG. 2, the AMF may send a response message (e.g., a response) to the WTRU. For example, the AMF may send a response message to the WTRU, informing the WTRU that an SMS over NAS is allowed and / or activated for an active user with the supplied user identifier (e.g., the supplied user ID). For example, the device may send a response message to the WTRU. For example, the response message may indicate that an SMS over NAS is allowed.

[0087] In some examples, the device may authenticate the user identifier (e.g., the user ID) associated with the user, e.g., with at least one of a UDR or a UDM. The user may be the active user using the WTRU. The device may determine that the authentication is successful. Based on the determination that the authentication is successful, the device may obtain at least one of the user profile information or SMS subscription data. For example, the user profile information may include at least one of a generic public subscription identifier (GPSI) or a mobile subscriber integrated services digital network number (MSISDN) associated with the active user. For example, the SMS subscription data may be associated with at least one of a UDR or a UDM.

[0088] One or more user identifiers in a system, such as a 5G system, may be used.

[0089] For example, in a system, such as a 5G system, one or more operators may be configured to utilize one or more user-specific identities in a network, such as a 3GPP network, e.g., to provide service delivery tailored based on the user identity. A user identity may be that of a human (e.g., an active user) using a WTRU and / or an application running on the WTRU and / or a device behind a WTRU gateway.

[0090] One or more service level parameters (e.g., requirements) and / or definitions related to user profiles and / or user identity may be defined (e.g., specified).

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

[0092] Secondary authentication processes may be (e.g., may include) a WTRU being authenticated. For example, the secondary authentication process may be a WTRU being authenticated by a third party authentication server, e.g., via intermediate functions in a core, such as a 5GC. For example, authentication may be performed by a session management function (SMF), an AMF, or a networkexposure function (NEF). The one or more processes may be known as PDU Session Secondary Authentication and Authorization (A&A), Network Slice Specific Authentication and Authorization (NSSAA), and / or Uncrewed Aerial Vehicles (UAV) Uncrewed Aerial System Service Supplier (USS) authentication and authorization (UUAA). The WTRU may use a non-3GPP user identity and / or credentials during an authentication and authorization process before being granted access to network resources (e.g., a Protocol Data Unit (PDU) Session, network slice, or data network (DN)).

[0093] An SMS may be sent over an NAS. For example, during a registration process (e.g., in a 5GS), to enable an SMS over NAS transporting, the WTRU may include an SMS support indication (e.g., an SMS supported indication) in a Registration Request (e.g., a registration request message). For example, as described herein, the AMF may receive a registration message (e.g., the registration request message) from the WTRU. The SMS supported indication in the registration request may indicate the capability of the WTRU for an SMS over NAS transport. The WTRU may include one or more subscriber identifiers, such as a Subscription Concealed Identifier (SUCI), a 5G Globally Unique Temporary Identifier (5G-GUTI), and / or a Permanent Equipment Identifier (PEI), to identify the WTRU. The SMS supported indication may indicate whether the WTRU supports an SMS delivery over an NAS.

[0094] The AMF may retrieve SMS Subscription data and / or the WTRU context. For example, the AMF may retrieve the SMS Subscription data and / or the WTRU context from SMSF, e.g., using Nudm_SDM_Get. The AMF may extract subscription data (e.g., including Network Slice Selection Assistance Information (NSSAIs)) for a WTRU SUPI (e.g., any given WTRU SUPI), e.g., by asking the UDM (e.g., may use the Nudm_SDM_Get service (SDM=SubscriberDataManagement)).

[0095] The UDM may retrieve the information from the UDR. The UDM may include the SMSF information in a message (e.g., a response message), such as an Nudm_SDM_Get response message, if the stored SMSF belongs to the same public land mobile network (PLMN) of the AMF. After a successful response is received, and if SMS service is allowed, the AMF may subscribe to be notified if and / or when the SMS Subscription data is modified.

[0096] If the SMS supported indication is included in the Registration Request, the AMF may check in the SMS Subscription data. For example, the AMF may check in the SMS Subscription data to determine whether the SMS service is allowed for the WTRU. If SMS service is allowed and the WTRU context received includes an available SMSF of the serving PLMN, the AMF may activate the SMSF Address and / or continue the registration process. If SMS service is allowed but the SMSF of the serving PLMN was not received, the AMF may discover and / or select an SMSF to serve the WTRU.

[0097] The AMF may invoke an operation, such as a Nsmsf_SMService_Activate service operation, from the SMSF. The invocation may include one or more of the following: an AMF address, access type,radio access technology (RAT) type, trace requirements, Generic Public Subscription Identifier (GPSI) (e.g., if available), and / or SUPI. The AMF may use the 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 may 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 may consider the WTRU context as a registration request from a new Access Type, and the SMSF may register with the UDM, e.g., using Nudm_UECM_Registration with the Access Type. As a result, the UDM may store the following information: SUPI, SMSF identity, and / or SMSF address, Access Type(s) in WTRU Context in SMSF data. The UDM may further store SMSF Information in the User Data Repository (UDR), e.g., using (e.g., by) Nudr_DM_Update (e.g., SUPI, Subscription Data, and / or WTRU Context in SMSF data).

[0099] As illustrated in FIG. 2, the SMSF may retrieve SMS Management Subscription data (e.g., SMS teleservice, SMS barring list, and / or the like), e.g., using Nudm_SDM_Get. Retrieving the SMS Management Subscription data may be configured (e.g., required) that the UDM gets the information from the UDR, e.g., using (e.g., by) Nudr_DM_Query (e.g., SUPI, Subscription Data, SMS Management Subscription data, and / or the like).

[0100] The SMSF may respond to the AMF, e.g., with an Nsmsf_SMService_Activate service operation response message. For example, the SMSF may send a response message to the AMF, as illustrated in FIG. 2. The AMF may store the SMSF Information received as part of the WTRU context.

[0101] The AMF may include an SMS allowed indication to the WTRU, e.g., in the Registration Accept message.

[0102] An SMS may be delivered over an NAS based on a user identifier (e.g., a User ID).

[0103] As described herein, if a user with a User Identifier = User_ID#1 intends to use the WTRU, theWTRU may send a request, such as a Registration Request, including UserJ D#1 to the AMF. The AMF may inform the SMSF that an SMS activation needs to be updated from the subscriber to the user of UserJ D#1 . The AMF may provide UserJ D#1 and / or the GPSI of UserJ D#1 to the SMSF. The AMF may not check SMS Subscription data for a user with UserJ D#1 .

[0104] As described herein, the AMF may discover and / or select an SMSF, e.g., to serve a human User (e.g., a User Identifier) via the WTRU. The AMF may not consider the SMS subscription policy for the user.

[0105] In a system (e.g., a 5G System), a subscription associated with a human user may not be identifiable and / or may not deliver an SMS over NAS to a human user who may be using a WTRU. For example, the system may not be aware of the identity of the user (e.g., a human) who may be using a WTRU to send and receive the SMS over NAS.

[0106] The human user of a subscription may be identified (e.g., may need to be identified as described herein) and focus on how to deliver an SMS over NAS to a human user if the human user accesses services via the system (e.g., a 5GS) using a user identifier.

[0107] A network, such as a 5G core network, may be able to identify a human user and / or deliver an SMS over NAS (e.g., an NAS message) to an active user using the WTRU.

[0108] If a user logs in to a device, the WTRU may register with the user identifier (e.g., the user ID) and may indicate that the device is SMS capable. A system, such as a 5GS, may authenticate the user identifier (e.g., the user ID) and may obtain SMS subscription policy information associated with the user identifier (e.g., the user ID). If allowed, the system (e.g., 5GS) and / or the AMF may select an SMSF and configure the SMSF with an MSISDN / GPSI of the user and / or routing information. The selection and / or configuration may allow an SMS to be delivered to the user using the WTRU.

[0109] An SMS may be enabled or disabled for a WTRU, e.g., based on the user of the WTRU. For example, if a user is authenticated to use a WTRU, the SMS feature may be disabled or enabled based on information from the user identity profile. One or more example processes may be described herein: a WTRU may provide a user identifier in a registration request (e.g., registration message); a network may authenticate the user; and / or the network may indicate to the WTRU whether or not the user is authorized to use the SMS feature on the WTRU.

[0110] In one or more example processes described herein, the network may send an indication of whether or not the user is authorized to use the SMS feature in a message, such as a registration message and / or a Registration Accept message. In an example, the indication of whether or not SMS is allowed for the user may be sent in a message, such as a WTRU Configuration Update message. Sending the indication in a Configuration Update message may be useful where the user is not yet authenticated when the network sends the Registration Accept message. For example, the process to authenticate the user may be an extensible authentication protocol (EAP) procedure that is separate from the Registration process.

[0111] If a user logs in with a user identifier (e.g., a USER ID) and indicates SMS capable, the AMF may authenticate the user identifier (e.g., the user ID).

[0112] The AMF may determine SMS subscription information for the user based on the user identifier (e.g., the USER ID). The AMF may obtain the information from the User profile, user’s GPSI, or MSISDN.

[0113] The AMF may select and / or configure an SMSF, e.g., to receive an SMS over NAS by providing routing information and / or user identifier information (e.g., user ID information), such as MSISDN or GPSI.

[0114] An SMS may be delivered over NAS to a user, such as an active human user. FIG. 2 illustrates an example of delivery of an SMS over NAS to an active human user. For example, FIG. 2 may provide anexample process of how an SMS over NAS may be delivered based on an active human user logged onto a device. One or more processes illustrated in FIG. 2 may or may not be performed (e.g., skipped).

[0115] As illustrated in FIG. 2, the WTRU SMS subscription may be modified and / or updated, e.g., to include additional information for a WTRU and / or a SUPI. For example, an UDM and / or an UDR may update the WTRU SMS subscription. The UDM and / or the UDR may update the WTRU SMS subscription to include an indication that an SMS over NAS may not be allowed if there is no active user and / or an indication that an SMS may be allowed for a certain active user(s). For example, the SMS Management Subscription data in the UDM / UDR may be updated with one or more of the following information: the SMS Management Subscription data may be updated to include an indication that an SMS over NAS is not allowed if a user identifier has not been authenticated to use the WTRU; and / or the SMS Management Subscription data may be updated to include an indication that an SMS over NAS is allowed (e.g., only allowed) if one or more certain users are authenticated to use the WTRU. For example, the identities of the user that are allowed to use an SMS over NAS with the WTRU may be included in the SMS Management Subscription data.

[0116] During the initial startup of the WTRU, if no user is active, the WTRU may initiate (e.g., perform) a registration process, e.g., as illustrated in FIG. 2.

[0117] The WTRU may try to register with the AMF. For example, the WTRU may try to register with the AMF by sending a message, such as a registration message. For example, the registration message may include a subscription identifier associated with the WTRU, e.g., a SUPI. The WTRU may indicate that there is no active user at that point by sending an indication, such as a flag indicating No user identifier (e.g., no User ID). The WTRU may indicate that the WTRU supports an SMS over NAS, e.g., by sending an indication, such as an SMS SUPPORTED FLAG, to the AMF in the registration message.

[0118] As illustrated in FIG. 2, the AMF may retrieve the SMS subscription data from the UDM / UDR. The request from the AMF may include the SUPI of the WTRU.

[0119] The UDM / UDR, based on the SUPI, may retrieve subscription information. The UDM may respond to the AMF by including SMS subscription information. The SMS subscription information may include at least one of an indication indicating that an SMS over NAS is not allowed if a user identifier (e.g., a user ID) is not present, an indication indicating that an SMS over NAS is not allowed if a user identifier (e.g., a user ID) is not active, an indication indicating that an SMS over NAS is not allowed if a user identifier (e.g., a user ID) is not authenticated, or an indication indicating that an SMS over NAS is allowed (e.g., allowed only) for one or more certain users.

[0120] As illustrated in FIG. 2, the AMF may store and parse the subscription information. The AMF may decide that the WTRU is not allowed for an SMS over NAS service as no user is active. The AMF mayactivate and / or subscribe (e.g., optionally activate and / or subscribe) with the SMSF for future use. The AMF may keep the SMSF activated ahead of time for future use. The AMF may indicate that SMS is restricted. The AMF may subscribe to the SMSF to be informed if the SMS intended for the WTRU and / or the SMS intended for another user is received. The AMF may take an action to notify the WTRU and / or the user about an incoming SMS.

[0121] As illustrated in FIG. 2, the AMF may inform the WTRU that an SMS over NAS is not allowed as no user is present, e.g., by sending a message, such as the registration response message.

[0122] In some examples, User A may log into the WTRU, e.g., with user identifier (e.g., user ID) = A. As illustrated in FIG. 2, the WTRU may send a message, such as a registration message and / or a registration Request message. The message may include a subscription identifier associated with the WTRU, e.g., SUPI. The WTRU may indicate (e.g., also indicate) that user A is active by including USERJD = A. The WTRU may indicate that the WTRU supports an SMS over NAS by sending an indication, such as an SMS SUPPORTED FLAG, to the AMF. The WTRU may include the indication that the WTRU supports an SMS over NAS in the registration message.

[0123] As illustrated in FIG. 2, the AMF may authenticate the user identifier A (e.g., USERJD, such as user ID A) with the UDM / UDR. The AMF may obtain the User Profile information and may retrieve the MSISDN of the user.

[0124] If the AMF has stored SMS subscription information for the WTRU and no change has happened to the subscription, one or more processes (e.g., process 10 and / or process 11) may be skipped, e.g., as illustrated in FIG. 2. If the AMF has not stored SMS subscription information for the WTRU and / or a change has happened to the subscription, the AMF may retrieve SMS subscription data from the UDM / UDR. The AMF may include the SUPI of the WTRU and / or USERJD = A of the active user in the subscription retrieval request.

[0125] As illustrated in FIG. 2, the UDM / UDR, based on the SUPI, may retrieve subscription information. The UDM may respond to the AMF. For example, the UDM / UDR may send a response message to the AMF. The response message may include including SMS subscription information, such as an indication that an SMS over NAS is not allowed if there is no active user and / or an indication that SMS is allowed for certain active users. The response and / or the response message may include (e.g., further include) SMSF information.

[0126] The AMF may store the SMS subscription information. The AMF may determine that the SMS over NAS is allowed (e.g., delivering the SMS over NAS is allowed) for the WTRU and / or the User. As illustrated in FIG. 2, the AMF may select (e.g., activate and / or configure) an SMSF from information (e.g.,from the stored and / or parsed subscription information as described herein) and / or the SMSF information (e.g., received in the response message from the UDM / UDR as described herein).

[0127] As illustrated in FIG. 2, the AMF may activate an SMS over NAS service with the SMSF, e.g., by sending a request, such as a Service Activate message and / or a service activate request message. The request and / or the request message may include at least one of the AMF address, the SUPI, and / or the MSISDN of User A.

[0128] As illustrated in FIG. 2, the SMSF may retrieve SMS Management subscription data.

[0129] As illustrated in FIG. 2, the SMSF may respond to the AMF, e.g., indicating that the activation was successful and may include SMSF information. For example, the SMSF may send a message, such as a service activate response message.

[0130] As illustrated in FIG. 2, the AMF may inform the WTRU, e.g., by sending a message, such as a registration response message, indicating that an SMS over NAS is allowed for USER = A.

[0131] Mobile terminated (MT) SMS may be configured.

[0132] As illustrated in FIG. 2, the UDM / UDR may receive an indication that a user is actively using a subscription associated with the WTRU (e.g., that a user is logged on and / or there is an active user).

[0133] An SMS Gateway Mobile Switching Centre (SMS-GMSC) may receive an SMS message that is addressed to a GPSI of the SUPI of the WTRU. As described herein, an SMS Service Centre (SMS-SC) and / or an SMS-GMSC may attempt to deliver the SMS message to the WTRU. The SMS-GMSC may send a request to the UDM / UDR, e.g., for the identity of the SMSF that serves the WTRU. The WTRU may be in the registration management registered state (e.g., RM-REGISTERED state). The UDM / UDR may determine to respond to the SMS-GMSC with an indication that the WTRU is not available. The UDM / UDR may determine to indicate that the WTRU is not available because the UDM / UDR is configured with information that indicates the user that is currently logged into the WTRU is not permitted to receive one or more SMS messages that are directed to the subscription associated with the WTRU. In some examples, the response message from the UDM / UDR to the SMS-GMSC may indicate that the SMS may not be delivered because the user who is currently using the subscription is not permitted to receive one or more SMS messages.

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

[0135] SMS transmission over an NAS may be restricted if a user, such as a human user, of the WTRU logs out. FIG. 3 illustrates an example process to suspend an SMS delivery over an NAS to a human user if the user logs out of the WTRU. One or more processes illustrated in FIG. 3 may or may not be performed (e.g., skipped).

[0136] As illustrated in FIG. 3, an active human user may log out from a WTRU. The WTRU may send a message, such as a Registration Update message, and / or other NAS control plane signaling messages, e.g., an uplink (UL) NAS transport message. The message may indicate that User A has logged out. The message may include (e.g., also include) the SUPI of the WTRU. In some examples, the WTRU may indicate whether to END or SUSPEND SMS over NAS service.

[0137] As illustrated in FIG. 3, the AMF may check if the USER A / SUPI has an active SMS over NAS service. If the AMF determines that the USER A / SUPI has an active SMS over NAS service, the AMF may decide to terminate or suspend (e.g., temporarily suspend) the service. The AMF may select the SMSF, e.g., which is serving the AMF.

[0138] As illustrated in FIG. 3, the AMF may send a request message, such as a Service Deactivate request message, to the SMSF. The request message (e.g., the service deactivate request message) may include one or more of the AMF address, the WTRU subscription identifier SUPI, and / or the like. The request message (e.g., the service deactivate request message) may indicate the reason (e.g., the cause) for the deactivation, e.g., User Inactive and / or the MSISDN of the User A, who became inactive.

[0139] As illustrated in FIG. 3, the SMSF may process the request and update SMS service information. For example, the SMSF may update the SMS Management Subscription Data in the UDM / UDR.

[0140] As illustrated in FIG. 3, the SMSF may inform the AMF, e.g., that the service has been deactivated successfully. For example, the SMSF may send a response message, e.g., a service deactivate response message, to the AMF. The service deactivate response message may indicate that the service deactivation has been successful.

[0141] As illustrated in FIG. 3, the AMF may inform the WTRU that an SMS over NAS for USER = A is no longer active and available. For example, the AMF may send a message, e.g., a de-register message, to the WTRU. The de-register message may indicate that the SMS over NAS is not allowed (e.g., delivering the SMS over NAS is not allowed) for the user A or the userJD = A is not allowed.

[0142] The processes described above may be implemented in a computer program, software, and / or firmware 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 overwired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as CD-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMSWhat is Claimed:

1. A device comprising: a processor configured to: receive a registration message from a wireless transmit / receive unit (WTRU); based on the registration message, determine whether a user identifier associated with a user has been identified; based on a determination that the user identifier associated with the user has been identified, obtain short message service (SMS) subscription information associated with the user; configure a short message service function (SMSF); and send a response message to the WTRU, wherein the response message indicates that an SMS over a non-access stratum (NAS) is allowed.

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

3. The device of claim 1 or 2, wherein the registration message indicates that the SMS over the NAS is supported.

4. The device of any of claims 1 to 3, wherein the registration message comprises a subscription permanent identifier (SUPI).

5. The device of claim 4, wherein the user is an active user using the WTRU, wherein the processor being configured to determine whether the user identifier associated with the user has been identified comprises the processor being configured to: send a request message to at least one of a user data repository (UDR) or a user data management (UDM), wherein the request message comprises a request to retrieve SMS subscription data, and wherein the request comprises the SUPI associated with the WTRU; and receive a response message from the at least one of the UDR or the UDM, wherein the response message comprises the SMS subscription information associated with the SUPI, wherein the SMS subscription information is configured to indicate that the SMS over the NAS is allowed for the user identifier associated with the active user using the WTRU.

6. The device of any of claims 1 to 5, wherein the processor is configured to: authenticate the user identifier associated with the user, with at least one of a UDR or a UDM, wherein the user is the active user using the WTRU; determine that the authentication is successful; and based on the determination that the authentication is successful, obtain user profile information, wherein the user profile information comprises at least one of a generic public subscription identifier (GPSI) or a mobile subscriber integrated services digital network number (MSISDN) associated with the active user.

7. The device of any of claims 1 to 6, wherein the processor being configured to configure the SMSF comprises the processor being configured to: send a service activate request message, wherein the service activate request message is configured to request an activation of the SMS over a NAS service associated with the active user, and wherein the service activate request message comprises a SUPI associated with the WTRU and an MSISDN associated with the active user using the WTRU; and receive a response message from the SMSF, wherein the response message comprises service activation information.

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

9. A method comprising: receiving a registration message from a wireless transmit / receive unit (WTRU); based on the registration message, determining whether a user identifier associated with a user has been identified; based on a determination that the user identifier associated with the user has been identified, obtaining short message service (SMS) subscription information associated with the user; configuring a short message service function (SMSF); and sending a response message to the WTRU, wherein the response message indicates that an SMS over a non-access stratum (NAS) is allowed.

10. The method of claim 9, wherein the method is performed by an access and mobility management function (AMF).11 . The method of claim 9 or 10, wherein the registration message indicates that the SMS over the NAS is supported.

12. The method of any of claims 9 to 11 , wherein the registration message comprises 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: sending a request message to at least one of a user data repository (UDR) or a user data management (UDM), wherein the request message comprises a request to retrieve SMS subscription data, and wherein the request comprises the SUPI associated with the WTRU; and receiving a response message from the at least one of the UDR or the UDM, wherein the response message comprises the SMS subscription information associated with the SUPI, wherein the SMS subscription information is configured to indicate that the SMS over the NAS is allowed for the user identifier associated with the active user using the WTRU.

14. The method of any of claims 9 to 13, wherein the method comprises: authenticating the user identifier associated with the user with at least one of a UDR or a UDM, wherein the user is the active user using the WTRU; determining that the authentication is successful; and based on the determination that the authentication is successful, obtaining user profile information, wherein the user profile information comprises at least one of a generic public subscription identifier (GPSI) or a mobile subscriber integrated services digital network number (MSISDN) associated with the active user.

15. The method of any of claims 9 to 14, wherein configuring the SMSF comprises: sending a service activate request message, wherein the service activate request message is configured to request an activation of the SMS over a NAS service associated with the active user, and wherein the service activate request message comprises a SUPI associated with the WTRU and an MSISDN associated with the active user using the WTRU; andreceiving a response message from the SMSF, wherein the response message comprises service activation information.

Images