WO2017196547A1 - Service de minimessages dans l'internet des objets cellulaire - Google Patents

Service de minimessages dans l'internet des objets cellulaire Download PDF

Info

Publication number
WO2017196547A1
WO2017196547A1 PCT/US2017/029870 US2017029870W WO2017196547A1 WO 2017196547 A1 WO2017196547 A1 WO 2017196547A1 US 2017029870 W US2017029870 W US 2017029870W WO 2017196547 A1 WO2017196547 A1 WO 2017196547A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
data
mme
sms
ack
Prior art date
Application number
PCT/US2017/029870
Other languages
English (en)
Inventor
Aghili Behrouz
Saad Ahmad
Mahmoud Watfa
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2017196547A1 publication Critical patent/WO2017196547A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • SMS Short Message Service
  • 3GPP 3rd Generation Partnership Project
  • CIoT Cellular Internet of Things
  • a CIoT device may use SMS to communicate with a server.
  • SMS protocols may have been designed to support the types of signaling and data transfer scenarios than may be present in a CIoT deployment, which may lead to wasted power and decreased battery life.
  • SMS protocols for example, for Cellular Internet of Thing (CIoT) type applications.
  • the SMS protocols described herein may reduce a number of packets or signaling messages used by one or more devices.
  • a wireless transmit/receive unit (WTRU) and a network (NW) may negotiate the level of support for SMS protocols that may be used for CIoT.
  • WTRU wireless transmit/receive unit
  • NW network
  • a control protocol may be used by a WTRU in order to perform an SMS transmission and/or reception.
  • messages between the WTRU and an anchor point in the core network e.g., mobile switching center (MSC)/ Serving General Packet Radio Service (GPRS) Support Node (SGSN)/Mobility Management Entity (MME)
  • MSC mobile switching center
  • GPRS General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • MME Mobility Management Entity
  • the WTRU may transmit an SMS message, which may include CP-DATA, using a Service Request message in CIoT.
  • the network may return a Service Accept message, which may act as a CP-ACK.
  • the network may include the CP-ACK in a Service Accept message.
  • a relay protocol may be used by a WTRU in order to perform an SMS transmission and/or reception.
  • messages exchanged between a WTRU and a service center (SC) may use an RP.
  • An acknowledgement, such as a RP-ACK, from the SMS Service Center (SC) may be sent to the WTRU by the network in a CP-DATA.
  • the WTRU may be informed that there may not be a need to send a CP-ACK to the network.
  • the RAN may send an indication to a core network (CN) node that the RAN has received a lower layer acknowledgement from the WTRU. This indication may serve the same functionality as a CP-ACK.
  • CN core network
  • a WTRU may start a timer to allow the MME to receive an RP-ACK from the Service Center and send it back to the WTRU.
  • the network (MME/SGSN) may transmit RP-ACK and/or CP-ACK in a Service Accept message.
  • An indication that a WTRU may be operating in a reduced (e.g., optimized) transmission mode for SMS may be sent to a MME.
  • the WTRU may communicate with the MME using fewer messages in the reduced (e.g., optimized) transmission mode for SMS than in a normal mode for SMS.
  • a data service request may be sent to the MME via a CP.
  • the data service request may include CP- DATA and/or the data service request may include RP-DATA.
  • a service accept message may be received from the MME, via the CP. Based on receiving the service accept message from the MME, the WTRU may implicitly determine that the CP-DATA has been successfully acknowledged.
  • FIG. 1 A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. IB is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A.
  • WTRU wireless transmit/receive unit
  • FIG. 1C is a system diagram of an example radio access network and an example core network that may be used within the communications system illustrated in FIG. 1A.
  • FIG. ID is a system diagram of another example radio access network and another example core network that may be used within the communications system illustrated in FIG.
  • FIG. IE is a system diagram of another example radio access network and another example core network that may be used within the communications system illustrated in FIG. 1A.
  • FIG. 2 shows an example short message services (SMS) signaling exchange for a mobile originating (MO) signaling, for example, when the device is in connected mode.
  • SMS short message services
  • FIG. 3 shows an example SMS signaling exchange for a MO signaling, for example, when the WTRU is in idle mode.
  • FIG. 4 shows an example message flow for SMS communications that may be used when transitioning from an idle mode to a connected, for example, for signaling associated with CIoT devices.
  • FIG. 5 shows an example message flow that may use a Service Accept message indicate one or more SMS communication messages.
  • FIG. 6 shows an example message flow that may be used to negotiate capabilities for SMS procedures and/or timers between a WTRU and a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • FIG. 7 shows an example message flow for SMS communications that may be used in connected mode.
  • FIG. 1A is a diagram of 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.
  • 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), and/or the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single- carrier FDMA
  • the communications system 100 may include wireless
  • WTRUs transmit/receive units
  • 102a, 102b, 102c, and/or 102d which generally or collectively may be referred to as WTRU 102
  • RAN radio access network
  • PSTN public switched telephone network
  • RAN radio access network
  • PSTN public switched telephone network
  • Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (WTRU), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and/or the like.
  • WTRU user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and/or the like.
  • the communications systems 100 may also include a base station 114a and 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 core network 106/107/109, the Internet 110, and/or the networks 112.
  • 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 site controller, an access point (AP), a wireless router, and/or 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.
  • the base station 114a may be part of the RAN 103/104/105, 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.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown).
  • the cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, e.g., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a,
  • an air interface 115/116/117 which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • RF radio frequency
  • IR infrared
  • UV ultraviolet
  • the air interface 115/116/117 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • 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/or the like.
  • the base station 114a in the RAN 103/104/105 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 using wideband CDMA (WCDMA).
  • UMTS Universal Mobile Telecommunications System
  • UTRA Universal Mobile Telecommunications System
  • WCDMA wideband CDMA
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • HSPA High-Speed Packet Access
  • HSDPA High-Speed Downlink Packet Access
  • HSUPA High-Speed Uplink Packet Access
  • 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 115/116/117 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE- A).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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/or the like.
  • IEEE 802.16 e.g., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • 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, and/or the like.
  • 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).
  • 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).
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g. , WCDMA, CDMA2000, GSM, LTE, LTE- A, etc.) to establish a picocell or femtocell.
  • a cellular- based RAT e.g. , WCDMA, CDMA2000, GSM, LTE, LTE- A, etc.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be used to access the Internet 110 via the core network 106/107/109.
  • the RAN 103/104/105 may be in communication with the core network 106/107/109, 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 core network 106/107/109 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.
  • VoIP voice over internet protocol
  • the RAN 103/104/105 and/or the core network 106/107/109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103/104/105 or a different RAT.
  • the core network in addition to being connected to the RAN 103/104/105, which may be utilizing an E-UTRA radio technology, the core network
  • 106/107/109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106/107/109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • 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 the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 103/104/105 or a different RAT.
  • One or more 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.
  • the WTRU 102c shown in FIG. 1 A 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.
  • FIG. IB is a system diagram of an example WTRU 102.
  • 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 other peripherals 138.
  • GPS global positioning system
  • the base stations 114a and 114b, and/or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved node-B (eNodeB or eNB), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, may include one or more of the elements depicted in FIG. IB and described herein.
  • BTS transceiver station
  • Node-B a Node-B
  • AP access point
  • AP access point
  • eNodeB or eNB evolved node-B
  • HeNB home evolved node-B gateway
  • proxy nodes among others, may include one or more of the elements depicted in FIG. IB and described herein.
  • 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,
  • DSP digital signal processor
  • 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
  • FIG. IB 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.
  • 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 115/116/117.
  • a base station e.g., the base station 114a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and 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.
  • 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 115/116/117.
  • 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 115/116/117.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
  • 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.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the 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/or the like.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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.
  • 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/or the like.
  • 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.
  • location information e.g. , longitude and latitude
  • the WTRU 102 may receive location information over the air interface 115/116/117 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 location-determination method while remaining consistent with an embodiment.
  • 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.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs 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, and/or the like.
  • FIG. 1C is a system diagram of the RAN 103 and the core network 106 according to an embodiment.
  • the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 115.
  • the RAN 103 may also be in communication with the core network 106.
  • the RAN 103 may include Node-Bs 140a, 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115.
  • the Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103.
  • the RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
  • the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b.
  • the Node- Bs 140a, 140b, 140c may communicate with the respective RNCs 142a, 142b via an Iub interface.
  • the RNCs 142a, 142b may be in communication with one another via an lur interface.
  • Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected.
  • each of the RNCs 142a, 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, and/or the like.
  • the core network 106 shown in FIG. 1C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MGW media gateway
  • MSC mobile switching center
  • SGSN serving GPRS support node
  • GGSN gateway GPRS support node
  • the RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface.
  • the MSC 146 may be connected to the MGW 144.
  • the MSC 146 and the MGW 144 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 land-line communications devices.
  • the RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface.
  • the SGSN 148 may be connected to the GGSN 150.
  • the SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the core network 106 may also be connected to the networks 1 12, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. ID is a system diagram of the RAN 104 and the core network 107 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the RAN 104 may also be in communication with the core network 107.
  • 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
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • 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 uplink and/or downlink, and/or the like. As shown in FIG. ID, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the core network 107 shown in FIG. ID may include a mobility management entity (e.g., gateway) (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MME mobility management entity
  • PDN packet data network
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S I interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer
  • the MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
  • the serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the S I interface.
  • the serving gateway 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the serving gateway 164 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and/or the like.
  • the serving gateway 164 may also be connected to the PDN gateway 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.
  • the PDN gateway 166 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 core network 107 may facilitate communications with other networks.
  • the core network 107 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 land-line communications devices.
  • the core network 107 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. IE is a system diagram of the RAN 105 and the core network 109 according to an embodiment.
  • the RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 117.
  • ASN access service network
  • the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
  • the RAN 105 may include base stations 180a, 180b, 180c, and an
  • the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with an embodiment.
  • the base stations 180a, 180b, 180c may each be associated with a particular cell (not shown) in the RAN
  • 105 may each include one or more transceivers for communicating with the WTRUs 102a,
  • the base stations 180a, 180b, 180c may implement MIMO technology.
  • the base station 180a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • the base stations 180a, 180b, 180c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and/or the like.
  • the ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and/or the like.
  • the air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an Rl reference point that implements the IEEE 802.16 specification.
  • each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 109.
  • the logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication,
  • the communication link between each of the base stations 180a, 180b, 180c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations.
  • the communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point.
  • the R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.
  • the RAN 105 may be connected to the core network 109.
  • the communication link between the RAN 105 and the core network 109 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example.
  • the core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements are depicted as part of the core network 109, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MIP-HA mobile IP home agent
  • AAA authentication, authorization, accounting
  • the MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, 102c to roam between different ASNs and/or different core networks.
  • the MIP-HA 184 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 AAA server 186 may be responsible for user authentication and for supporting user services.
  • the gateway 188 may facilitate interworking with other networks.
  • the gateway 188 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 land-line communications devices.
  • the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks.
  • the communication link between the RAN 105 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs.
  • the communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.
  • a WTRU and/or network device e.g., MME, eNodeB, gNodeB,
  • TRP transmission/reception point
  • CIoT Short Message Service
  • devices e.g., a WTRU, such as a CIoT WTRU
  • CIoT WTRU may communicate using the modified Short Message Service (SMS) signaling.
  • SMS Short Message Service
  • CIoT devices e.g., CIoT WTRUs
  • CIoT WTRUs may include low power and/or low cost devices that communicate in one or more contexts, such as sensors, vehicles, buildings, embedded electronics, actuators, etc.
  • CIoT communications may provide network connectivity that may enable WTRUs to collect and/or exchange data.
  • Such connectivity may implement one or more technologies, such as smart grids, virtual power plants, smart homes, intelligent transportation, smart cities, and/or the like.
  • the signaling associated with CIoT devices may be infrequent and/or may be small in terms of pay load size.
  • CIoT devices may be power-constrained, for example, when operating on a battery that may not be rechargeable or in a deployment that may make it difficult to obtain power.
  • Reducing the amount of control signaling utilized for data transfer by CIoT devices may increase the efficiency (e.g., overall efficiency) and/or operating life associated with the CIoT devices.
  • Reducing network-side signaling that supports CIoT device data transfer may increase a network's ability to support a large number of CIoT devices.
  • SMS procedures may allow CIoT devices to communicate in an efficient manner and/or may allow networks to support large numbers of CIoT devices.
  • CIoT devices may use SMS to communicate with one or more other devices (e.g., a server).
  • the number of packets/signaling messages used for communicating with the network may be decreased. Decreasing the number of packets/signaling messages used by the CIoT devices and network when communicating may save power of the CIoT devices and/or may result in a longer battery life of the CIoT devices.
  • a CIoT device e.g., a WTRU and/or network may exchange a Service Request message.
  • the CIoT device may send the network the Service Request message.
  • the Service Request message may include an indication that the WTRU is able to support and/or is using a reduced transmission SMS data exchange.
  • a Data Service Request may be used by a CIoT device (e.g., a WTRU) to transition from Idle Mode to Connected Mode, and/or may send data/messages to the network.
  • FIG. 2 illustrates an example SMS signaling exchange for a mobile originating (MO) case, for example, where the CIoT device (e.g., WTRU) is in connected mode.
  • FIG. 3 shows an example SMS signaling exchange for a MO case, for example, when the CIoT (e.g., WTRU) begins in IDLE mode and transitions to connected mode.
  • the example illustrated in FIG. 3 may be an example of a reduced transmission SMS procedure that may reduce control plane signaling, and/or which may be used by CIoT device.
  • CIoT WTRUs or CIoT devices the examples may be applicable to any type of device or WTRU and this description is not meant to be limited to a certain type of device.
  • FIG. 2 and FIG. 3 illustrate examples of how MO SMS traffic may work in a connected mode and/or idle mode.
  • the SMS transmission procedure may utilize a first protocol for communications between a WTRU and an SMS Service Center (SMS-SC, which may be referred to as an SC).
  • SMS-SC SMS Service Center
  • the SMS transmission procedure may utilize a first protocol for communications between a WTRU 210 and an SMS-SC 216.
  • the protocol for communications between a WTRU (e.g., WTRU 210) and an SMS Service Center (e.g., SMS-SC 216) may be referred to as a Relay Protocol (RP).
  • RP Relay Protocol
  • an SMS-SC may send data to a WTRU (e.g., WTRU 210) and/or a WTRU (e.g., WTRU 210) may send data to an SMS-SC (e.g., SMS-SC 216).
  • the data sent corresponding to the RP level may be referred to as RP-DATA.
  • the receiver (e.g., SMS-SC or WTRU) of the RP data may reply using an acknowledgement, which may be referred to as an RP-ACK. If an RP-ACK is not received within a predefined time of receipt of the RP data, a retransmission may be performed by the transmitter of the RP data.
  • NAS Non- Access Stratum
  • CP Control Protocol
  • the CP protocol may be used by an entity (e.g., a WTRU or MME) to send information to another entity.
  • a WTRU e.g., WTRU 2
  • MME Mobility Management Entity
  • MME Mobility Management Entity
  • the CP may carry RP data to and/or from an SMS-SC (e.g., SMS-SC 216).
  • the data transferred via the CP may be referred to as CP-DATA.
  • the receiver e.g., WTRU or MME
  • the CP-ACK message may be an acknowledgement at the CP layer and may contain information.
  • the sending entity may retransmit the CP-DATA. For example, if the sending entity does not receive a CP-ACK from another entity, the sending entity may start a retransmission of the CP-DATA.
  • SMS may be used with various types of cellular communication systems, for example, Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications Service (UMTS), Evolved Packet System (EPS) (e.g., LTE), and/or 5G protocols.
  • GSM Global System for Mobile communication
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications Service
  • EPS Evolved Packet System
  • LTE Long Term Evolution
  • 5G protocols e.g., LTE
  • SMS may be used with various types of cellular communication systems, for example, Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications Service (UMTS), Evolved Packet System (EPS) (e.g., LTE), and/or 5G protocols.
  • GSM Global System for Mobile communication
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications Service
  • EPS Evolved Packet System
  • acknowledgements exchanged between communication entities such as acknowledgements between a mobile device (e.g., WTRU) and on more core network entities.
  • acknowledgement(s) may be exchanged using one or more protocol layers.
  • the WTRU and the core network entity may send and/or receive acknowledgements at the Control Protocol (CP) layer when sending and/or receiving SMS messages.
  • the WTRU and/or the SMS Service Center (SC) may send and/or receive acknowledgements at a protocol layer called Relay Protocol (RP).
  • RP Relay Protocol
  • Using one or more types of acknowledgements may increase the total signaling level (e.g., may increase total traffic) in SMS.
  • using one or more types of acknowledgements may cause traffic in SMS, whether the acknowledgements are mobile originated (MO) or mobile terminated (MT).
  • MO mobile originated
  • MT mobile terminated
  • a WTRU sends an SMS message there may be one or more (e.g., four) messages exchanged over the air.
  • the example shown in FIG. 2 includes WTRU 210, eNB 212, MME 214, and SMS-SC 216.
  • WTRU 210 sends a CP-DATA to MME 214.
  • the CP-DATA may contain an RP-DATA intended for an SMS-SC, for example, at 202.
  • the MME 214 acknowledges the reception of the CP-DATA, for example, by a CP-ACK.
  • the MME 214 receives an RP-ACK from the SMS-SC 216, which may be intended for the WTRU 210.
  • the MME 214 may insert the RP-ACK in a CP-DATA and/or the MME 214 may send the RP- ACK to the WTRU 210, at 205.
  • the WTRU 210 sends a CP-ACK to the MME 214.
  • the WTRU 210 may send a CP-ACK to the MME 214 to acknowledge the reception of the CP-DATA.
  • the example shown in FIG. 3 includes WTRU 310, eNB 312, MME 314, and SMS-SC
  • WTRU 310 sends a Service Request message to MME 314.
  • the Service Request message may contain an RP-DATA intended for an SMS-SC 316, for example, at 302.
  • the MME 314 sends a Service Accept message to WTRU 310.
  • the MME 314 may acknowledge the reception of the CP-DATA, for example, by a CP-ACK, at 304.
  • the MME 314 receives an RP-ACK from the SMS-SC 316, which may be intended for the WTRU 310.
  • the MME 314 may insert the RP-ACK in a CP-DATA and/or the MME 314 may send the RP-ACK to the WTRU 310, at 306.
  • the WTRU 310 sends a CP-ACK to the MME 314.
  • the WTRU 310 may send a CP-ACK to the MME 314 to acknowledge the reception of the CP-DATA.
  • SMS Short Message Service
  • CIoT Cellular Internet of Things
  • WTRU Wireless Telecommunications
  • SM Session Management
  • the use of fewer messages may be achieved by including some types of signaling messages (e.g., such as a CP-ACK) in other messages of the procedure (e.g., a service accept message).
  • the use of fewer messages may be achieved implicitly determining that a message has been provided (e.g., such as a CP-ACK) based on the presence or reception of another message of the procedure (e.g., a service accept message).
  • a WTRU may be configured to treat reception of a first message (e.g., a service accept message) as if two messages had been received (e.g., a CP-ACK and a service accept message).
  • the user data, signaling information, and/or an SMS message may be transmitted and/or received in fewer messages when a CIoT device transitions from an idle mode to a connected mode.
  • user data, signaling information, and/or an SMS message may be transmitted and/or received in fewer messages by transmitting and/or receiving the user data, signaling information, and/or an SMS message in a Service Request Message (e.g., Service
  • User data, signaling information, and/or an SMS message may be transmitted and/or received in fewer messages when the WTRU is in a connected mode by using an EMM message.
  • a WTRU may transition from an idle mode to a connected mode upon request from an SMS protocol entity to send an SMS message.
  • the WTRU and the network may negotiate a level of support.
  • the WTRU and the network may negotiate SMS capabilities of the WTRU and the network.
  • the SMS capabilities may relate to whether the WTRU and/or the network supports legacy SMS signaling and/or reduced transmission SMS signaling.
  • the WTRU may inform the network that the WTRU may have capabilities related to handling SMS messages.
  • the WTRU may indicate whether the WTRU supports legacy SMS signaling and/or reduced transmission SMS signaling.
  • the network e.g., MME
  • the WTRU of the network's level of support e.g.
  • the WTRU may inform the network of the WTRU's level of support by adding information elements in the Request message (e.g., Service Request message 301, shown in FIG. 3)
  • the network (MME) may inform the WTRU of the network's level of support by adding information elements in the Accept message (e.g., Service Accept message 303, shown in FIG. 3).
  • the WTRU and/or the network may inform the other entity the respective levels of support by modifying existing information elements, such as a WTRU Network Capability, an EPS Feature Support, or the like.
  • the WTRU may use a timer (e.g., an extended timer) that may be associated with a Service Request message (e.g., Service Request message 301, shown in FIG. 3).
  • a timer e.g., an extended timer
  • the timer may start based on the transmitting and/or receiving of the Service Request message 301.
  • the timer may be referred to as a Service Request timer or a Service Request timer associated with a reduced transmission SMS transfer (e.g., an optimized transmission mode).
  • the timer may be a
  • the Service Request message may be a Data Service Request message.
  • a Data Service Request message may be a type of Service Request message used for requesting service when the WTRU attempts to transmit/receive SMS data using a modified (e.g., reduced) SMS procedure.
  • the WTRU may use a timer (e.g., the Service Request timer) when it is determined that the WTRU and the network support a reduced transmission SMS protocol, and/or when the network indicates that the network uses a reduced transmission SMS protocol for the WTRU.
  • the Service Request timer which may be the T3417ext timer, may have a longer timeout value than a T3417 timer. If the network does not support a reduced transmission SMS protocol, such as those described herein, and/or if the network determines not to use the reduced transmission SMS protocol for the WTRU, the WTRU may use timer T3417 to guard the completion of the service request.
  • the WTRU and the network may identify a timer that may guard a wait period within which an RP-ACK may be received (e.g., received by the WTRU) before the CP-DATA is re-transmitted (e.g., re-transmitted by the WTRU). For example, if a predetermined amount of time passes and the WTRU does not receive an RP-ACK, the WTRU may retransmit a CP-DATA.
  • the WTRU and/or the network may identify a timer that may provide an indication that a predefined time interval, such as TsMS_extended, has passed.
  • the timer (e.g., the time interval, TsMS_extended) may guard a period of SMS re-transmission (e.g.
  • the WTRU may not re-transmit CP-DATA. If the WTRU fails to receive the RP- ACK before the timer expires, the WTRU may re-transmit CP-DATA.
  • Use of the timer, as described herein, may reduce associated signaling between the WTRU and the network and make transmitting an SMS more efficient.
  • the WTRU and the network may determine a timer as part of an Attach or a
  • the WTUR and/or the network may use indications, information elements, and/or capability indications (e.g., separate indications, information elements, and/or capability indications).
  • one or more acknowledgement messages may be eliminated and/or acknowledgments may be indicated implicitly rather than explicitly.
  • predefined explicit acknowledgement messages in a mobile originated case may be eliminated.
  • FIG. 4 illustrates an example message flow for SMS communications that may be used, for example when the WTRU transitions from an idle mode to a connected mode.
  • one or more predefined acknowledgement messages may be eliminated and/or acknowledgments may be indicated implicitly rather than explicitly.
  • Eliminating CP-ACK messages, including the CP-ACK in other service request procedure messages, and/or implicitly indicating CP-ACK messages, may reduce SMS communications.
  • An RP-ACK may be utilized.
  • an RP-ACK may be used by a device (e.g., WTRU) in order to determine whether to attempt to resend an SMS (RP-DATA) message if the device does not receive the RP-ACK with a time window.
  • a device e.g., WTRU
  • SMS RP-DATA
  • the example shown in FIG. 4 includes WTRU 410, eNB 412, MME 414, and
  • SMS-SC 416 As shown in FIG. 4, at 401 WTRU 410 sends a Service Request message to MME
  • the Service Request message may contain an RP-DATA intended for an SMS-SC 416, for example, at 402.
  • the MME 414 sends an EPS Mobility Management (EMM) Service
  • the EMM Service Accept message may be used (e.g., transmitted) in response to a Service Request, such as a Data Service Request.
  • Receiving the EMM Service Accept message may indicate (e.g., implicitly indicate) to the WTRU that the service request may be finalized.
  • An EMM layer in the WTRU may send an indication to an SMS protocol entity, which may be in the WTRU, that the network may have sent a positive response.
  • the indication may be interpreted by the WTRU, which may be the EMM entity in the WTRU and/or the SMS entity in the WTRU, as a CP-ACK.
  • the MME 414 may transmit the CP-ACK in the Service Accept message and/or the EMM layer in the device. Transmitting the CP-ACK in the Service Accept message may indicate (e.g., explicitly indicate) to the WTRU that the service request may be finalized.
  • the EMM entity in the WTRU may provide the CP-ACK to the SMS entity.
  • the MME 414 may include the CP-ACK in the Service Accept message and/or the EMM in the WTRU may send the CP-ACK to the SMS entity.
  • FIG. 5 shows an example message flow that may use a Service Accept message to reduce SMS communications.
  • FIG. 5 shows messages between an EMM entity 512 and an SMS entity 510 that may be in WTRU.
  • the EMS entity 512 may send a Data Service Request, at 501, and may receive a Service Accept message, at 502.
  • the Service Accept message may include a CP- ACK. If the EMM entity 512 receives a CP-ACK in the Service Accept message, the EMM entity 512 may, at 503 A, forward the CP-ACK to the SMS entity 510. If the EMM entity 512 does not receive a CP-ACK in the Service Accept message, the EMM entity 512 may, at 503B, send an implicit CP-ACK indicator to the SMS entity 510.
  • the SMS entity 510 may consider the implicit CP-ACK as an equivalent to the reception of a CP-ACK.
  • SMS (or CP-DATA) re-transmissions by the WTRU may be reduced. For example, unnecessary SMS (or CP-DATA) re-transmissions by the WTRU may be reduced.
  • the WTRU may start a timer, such as a T3417ext timer. For example, the WTRU may start a timer when the WTRU sends the Data Service Request.
  • the WTRU may include a time period in the Data Service Request.
  • the WTRU may include a time period in the Data Service Request, for example, to inform the MME about the period of time that the WTRU may wait before re-transmitting a CP-DATA.
  • the time period may be longer than the T3417ext timer and/or the time period may be the time that is associated with the Data
  • the time period may be used by the MME to send an RP-ACK, which may be embedded in a CP-DATA, to the WTRU after an RP-ACK is received by the MME from the
  • the MME may wait for a predetermined time in the Data Service Request, a time period that may be configured in the MME, and/or a reception of the RP-ACK as indicated in the subscription profile of the WTRU. If the timer expires and the MME did not receive an RP-ACK from the SMS-SC, the MME may send a CP- ACK to the WTRU. If the MME receives an RP-ACK from the SMS-SC before the timer expires, the MME may send the CP-ACK and/or the RP-ACK to the WTRU. The CP-ACK and/or the RP-ACK may be sent in the Service Accept message. The RP-ACK may be embedded in a CP-DATA in the Service Accept message.
  • FIG. 6 shows an example message flow that may be used to negotiate SMS messages and/or timers between a WTRU and a MME.
  • the example shown in FIG. 6 includes WTRU 610, MME 614, and SMS-SC 616.
  • the WTRU 610 and MME 614 may determine (e.g., negotiate) a timer for CP-DATA Retransmission.
  • the WTRU 610 and MME 614 may determine a timer as part of an Attach procedure and/or Tracking Area Update (TAU) and/or Routing Area Update (RAU).
  • WTRU 610 at 602, sends a Service Request message to MME 614.
  • TAU Tracking Area Update
  • RAU Routing Area Update
  • the Service Request message may contain a timer for CP-DATA retransmission by the WTRU 610.
  • the Service Request may contain an RP-DATA intended for an SMS-SC 616.
  • the MME 614 sends an RP-DATA message to SMS-SC 616, at 603
  • MME 614 may send a Service Accept message with CP-ACK and/or CP-DATA (with RP-ACK).
  • the MME 614 may send a Service Accept message with CP-ACK and/or CP-DATA (with RP-ACK) if a timer does not expire at the MME 614.
  • the MME 614 may send a Service Accept message with the CP-ACK if the timer expires.
  • the SMS-SC 616 sends an RP-ACK to the MME 614, at 605 (e.g., 605 A, 605B).
  • the MME 614 may include the messages as one or more (e.g., two) separate components and/or information elements.
  • the MME 614 may use one or more (e.g., two, such as two different) information elements of TLV (e.g. Type, Length and Value) format to separate the CP-ACK from the CP-DATA, which may include the RP- ACK.
  • TLV e.g. Type, Length and Value
  • the type field may be set to an SMS container and/or the length field may be set to the length of the CP-ACK and/or the CP-DATA, which may include the RP-ACK.
  • the EMM entity e.g., the EMM entity of the WTRU 610
  • the SMS entity e.g., the SMS entity of the WTRU 610
  • the SMS entity may interpret one or more (e.g., both) components to determine that a first component may be a CP-ACK and/or the second component may be a CP-DATA (which may include the RP-ACK).
  • the WTRU 610 sends a Data Service Request, at 602, the Data Service
  • the Request may indicate to the MME 614 that a CP-ACK may be omitted.
  • the indication that the CP-ACK may be omitted may be performed using an indication and/or information element (IE) in the message.
  • the WTRU 610 may rely on the lower layer acknowledgements, such as the Radio Link Control (RLC)-ACK at the RLC level, to determine that the message (e.g. CP- DATA) has been received in the MME.
  • the lower layers such as the RLC or PDCP, may inform the EMM entity that an acknowledgement has been received. For example, a lower layer may indicate to the EMM entity that an acknowledgment from the eNB at the peer RLC or PDCP entity has been received.
  • the EMM entity may identify the indication that the acknowledgement has been received as an implicit CP-ACK.
  • the EMM entity may send an indication to the SMS entity that an implicit CP-ACK has been received.
  • the WTRU 610 may wait for the Service Accept message. Waiting for the Service Accept message may give the MME 614 the option to wait for the RP-ACK from the SMS-SC before sending the Service Accept message to the WTRU 610.
  • the MME 614 may send a Service Accept message with the CP-DATA, which may include the RP-ACK.
  • the MME 614 may send a Service Accept message with the CP-DATA to the WTRU 610.
  • the WTRU 610 may determine the service request to have successfully completed, and/or the WTRU 610 may stop the associated timer, which may be a T3417ext timer.
  • the EMM entity may forward the CP-DATA, which may include the RP-ACK, to the SMS entity.
  • the MME 614 may send CP-DATA in one or more NAS messages, at 607. If the MME 614 determines to send (e.g., send separately) the CP-DATA (which may include an RP-ACK) in NAS messages, the MME 614 may indicate in the NAS message that a CP-ACK may not be needed. The NAS messages may not be the Service Accept message. Not needing a CP-ACK may save a transmission from the WTRU 610. The MME 614 may send the NAS message (which may include the CP-DATA) and/or may request the eNB to release the NAS connection of the WTRU 610. The eNB may send the NAS message embedded in an RRC Connection Release message.
  • the WTRU 610 may receive a NAS message in the RRC Connection Release message.
  • the NAS message may include an SMS container.
  • the EMM entity may forward the SMS container to the SMS entity and/or may indicate that a CP-ACK may not be needed.
  • the EMM may indicate whether the NAS message is received in the RRC Connection Release message and/or if the NAS message (which may be sent by the MME) includes an indication (e.g. set by the MME) that no CP-ACK may be needed and/or transmitted by the WTRU.
  • FIG. 7 shows an example message flow for SMS communications that may be used in a connected mode.
  • the example shown in FIG. 7 includes WTRU 710, eNB 712, MME 714, and SMS-SC 716.
  • An efficient (e.g., a more efficient) SMS protocol may be provided for a connected mode.
  • a reduced transmission SMS protocol may be used by a WTRU operating in connected mode.
  • WTRU 710 may send a CP-DATA message.
  • the WTRU 710 may be in connected mode.
  • the CP-DATA message may contain an SMS message.
  • the CP- DATA may not expect a CP-ACK message from the MME 714.
  • the MME 714 may send RP-DATA to SMS-SC 716 and, at 704, the MME 714 may receive an RP-ACK from SMS- SC 716.
  • MME 714 may send the CP-DATA with an RP-ACK to the WTRU 710.
  • MME 714 may send the CP-DATA with an RP-ACK to the WTRU 710 when MME 714 receives a RP-ACK from the SMS service center 716.
  • the EMM 714 may send the CP-DATA to the SMS entity, which may determine the CP-DATA to be a CP-ACK.
  • the RP-ACK may arrive at the MME 714.
  • the MME 714 may insert the RP-ACK in a CP-DATA and may send the RP-ACK to the WTRU 710, at 705.
  • the reception of the RP-ACK at the WTRU 710 may indicate that the Mobile Originated SMS service may be successful.
  • the WTRU 710 may send one or more CP- ACKs to the MME 714.
  • the MME 714 may insert an indicator and/or an information element that may inform the WTRU 710 that sending a CP-ACK may be unnecessary.
  • a mechanism other than the CP-ACK may be used to allow the MME 714 to ensure that the WTRU 710 received the CP-DATA that includes the RP-ACK.
  • the RAN may send an indication to the MME 714 upon receiving final acknowledgement at the Layer 2 (e.g. RLC) to indicate to the MME 714 that the WTRU received the CP-DATA with the RP-ACK.
  • the WTRU 710 at 706, may send an RLC-ACK to the eNB 712.
  • the eNB 712 may send a CP-ACK to the MME 714.
  • a reduced transmission SMS protocol may be used by the network and/or WTRU for a mobile terminated SMS scenario.
  • a WTRU may be paged.
  • the WTRU may respond to the network by using a Service Request message, which may be a Data Service Request message.
  • the MME may send a CP-DATA, which may include RP-DATA.
  • the MME may use an indicator and/or IE that may inform the WTRU that the MME may not have to reply to the CP- DATA using a CP-ACK.
  • the WTRU may send a CP-DATA that may include an RP-ACK to the SMS-SC.
  • the message may have an indicator and/or IE that may inform the MME that the
  • the WTRU received and/or decoded the CP-DATA from the MME.
  • the WTRU may include an information element (IE) and/or indicator that may inform the MME that there may not be a need to send back a CP-ACK.
  • IE information element
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, WTRU, terminal, base station, RNC, or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des systèmes, des procédés et des instruments à utiliser dans un service SMS (service de minimessages). Une indication selon laquelle une unité WTRU (unité d'émission-réception sans fil) peut fonctionner dans un mode de transmission optimisé pour le service SMS peut être envoyée à une entité MME (entité de gestion de la mobilité). L'unité WTRU peut communiquer avec l'entité MME en utilisant moins messages dans le mode de transmission optimisé pour un service SMS que dans un mode normal pour un service SMS. Une demande de service de données peut être envoyée à l'entité MME via un protocole CP (protocole de commande). La demande de service de données peut inclure des données de protocole CP et/ou la demande de service de données peut inclure des données de protocole RP (protocole de relais). Un message d'acceptation de service peut être reçu, en provenance de l'entité MME, via le protocole CP. Sur la base de la réception du message d'acceptation de service en provenance de l'entité MME, l'unité WTRU peut implicitement déterminer que les données de protocole CP ont été acquittées avec succès. Des protocoles de service SMS peuvent être utilisés pour l'Internet des objets (IdO) cellulaire.
PCT/US2017/029870 2016-05-12 2017-04-27 Service de minimessages dans l'internet des objets cellulaire WO2017196547A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662335608P 2016-05-12 2016-05-12
US62/335,608 2016-05-12

Publications (1)

Publication Number Publication Date
WO2017196547A1 true WO2017196547A1 (fr) 2017-11-16

Family

ID=58692635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/029870 WO2017196547A1 (fr) 2016-05-12 2017-04-27 Service de minimessages dans l'internet des objets cellulaire

Country Status (1)

Country Link
WO (1) WO2017196547A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022278A1 (en) * 2019-04-02 2022-01-20 Nokia Technologies Oy Method and apparatus for cellular internet of things (ciot) data transfer over a control plane in a wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140287752A1 (en) * 2011-10-03 2014-09-25 Lg Electronics Inc. Mobility management entity handling sms-related signal

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140287752A1 (en) * 2011-10-03 2014-09-25 Lg Electronics Inc. Mobility management entity handling sms-related signal

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture enhancements for Cellular Internet of Things (Release 13)", 3GPP STANDARD; 3GPP TR 23.720, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.0.0, 15 March 2016 (2016-03-15), pages 1 - 94, XP051087943 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220022278A1 (en) * 2019-04-02 2022-01-20 Nokia Technologies Oy Method and apparatus for cellular internet of things (ciot) data transfer over a control plane in a wireless communication system

Similar Documents

Publication Publication Date Title
US10531366B2 (en) Efficient signaling for machine type communication
TWI816160B (zh) 在傳訊平面上傳送小資料ｎａｓ協定之增強的裝置及方法
US9426698B2 (en) Method and apparatus for transmitting extended service request messages in a congested network
KR101614999B1 (ko) Ｍ2ｍ 디바이스에 대하여 다운링크 데이터에 대한 페이징을 수행하는 방법
EP2478741A2 (fr) Procédé et appareil de fourniture d'une communication poste à poste au moyen d'une connexion réseau
WO2012135582A1 (fr) Déclenchement demandé par réseau d'un dispositif hors ligne
US20110069676A1 (en) Information service and event service mechanisms for wireless communications
WO2017196547A1 (fr) Service de minimessages dans l'internet des objets cellulaire
US20150319587A1 (en) Short message service in prose

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17722613

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17722613

Country of ref document: EP

Kind code of ref document: A1