WO2015172079A1 - Services de surveillance de communications de type machine - Google Patents

Services de surveillance de communications de type machine Download PDF

Info

Publication number
WO2015172079A1
WO2015172079A1 PCT/US2015/029985 US2015029985W WO2015172079A1 WO 2015172079 A1 WO2015172079 A1 WO 2015172079A1 US 2015029985 W US2015029985 W US 2015029985W WO 2015172079 A1 WO2015172079 A1 WO 2015172079A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
event
request
inter
wtrus
Prior art date
Application number
PCT/US2015/029985
Other languages
English (en)
Inventor
Mahmoud Watfa
Samian Kaur
Pascal M. Adjakple
Dimitrios Karampatsis
Saad Ahmad
Ulises Olvera-Hernandez
Original Assignee
Interdigital Patent 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 Interdigital Patent Holdings, Inc. filed Critical Interdigital Patent Holdings, Inc.
Publication of WO2015172079A1 publication Critical patent/WO2015172079A1/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/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • Machine type communication (MTC) devices also referred to as machine to machine (M2M) communication devices
  • MTC applications are proliferating to provide a variety of MTC applications to support different wireless systems for services areas (e.g., security systems, tracking and tracing systems, payment systems, health care systems, remote maintenance and control systems, metering systems and the like), as well as supporting wireless consumer electronic devices.
  • WTRUs wireless transmit/receive units
  • Such MTC devices maybe herein after referred to as MTC wireless transmit/receive units (MTC WTRU).
  • MTC WTRU MTC wireless transmit/receive units
  • MTC Machine type communication
  • the enhanced event monitoring function may include monitoring one or more machine type communication (MTC) wireless transmit/receive units (WTRUs) to detect one or more changes to a plurality of configured enhanced MTC WTRUs events and logging and reporting the configured enhanced MTC WTRUs events to a service capability server (SCS) and/or application server (AS) for further predetermined actions.
  • MTC machine type communication
  • WTRUs wireless transmit/receive units
  • the example one or more network nodes may include one or more designated
  • MTC WTRUs mobility management entities, serving general packet radio service (GPRS) support nodes, mobile switching center (MSC), visitor location register (VLR), access point (AP), base station (BS), evolved Node B (eNB), radio network controller (RNC), base station controller (BSC), and/or any other radio access network (RAN) node.
  • GPRS general packet radio service
  • MSC mobile switching center
  • VLR visitor location register
  • AP access point
  • BS base station
  • eNB evolved Node B
  • RNC radio network controller
  • BSC base station controller
  • RAN radio access network
  • the one or more network nodes may be configured to employ one or more MTC MONTE techniques to perform the enhanced event monitoring function monitoring.
  • Examples of MTC MONTE techniques may include a technique employing monitoring by way of a policy charging and control (PCC) platform and a home subscriber server (HSS), a technique which employs monitoring an association between International Mobile Subscriber Identity (IMSI) - IMEI- software version (SV) of the MTC WTRU, and a technique which employs monitoring via MTC-interworking function (IWF) using a Tsp reference point.
  • PCC policy charging and control
  • HSS home subscriber server
  • IMSI International Mobile Subscriber Identity
  • SV International Mobile Subscriber Identity
  • IWF MTC-interworking function
  • the MTC MONTE may be configured to include requesting a supported list of events and/or functions that are available for the SCS and/or AS for an identified MTC WTRU and/or a group of MTC WTRU. This request may be verified with a home subscriber server to determine if the SCS and/or AS is authorized to obtain such a function and/or service and, if so authorized, provide the supported list of events and/or functions.
  • the MTC MONTE may be configured to include an indication to the SCS and/or AS that a set of services is either temporarily unavailable and/or has been resumed.
  • Monitoring of a group of MTC WTRUs may be provided by a gateway
  • G-WTRU configured to monitor and/or handle configured enhanced MTC WTRUs events and report the enhanced MTC WTRUs events to other devices.
  • the MTC MONTE may be configured to associate the configured enhanced
  • MTC machine type communication
  • Techniques may include receiving, at a first MTC device, a request for information from a second MTC device regarding at least one of: an MTC event or an MTC function. The information may include an identification of the at least one of the MTC event or the MTC function.
  • Techniques may include sending a first signal to a third device.
  • the first signal may initiate a verification of an authorization of the second MTC device to receive the information.
  • the verification may be at least one of: successful or unsuccessful.
  • Techniques may include receiving the information from the third device upon the verification being successful.
  • Techniques may include sending the information to the second device upon receipt of the information from the third device.
  • Techniques may include receiving, at a first MTC device, a request for information from a second MTC device regarding an inter-radio access technology (inter-RAT) handover event.
  • the information may include a request to monitor the inter-RAT handover event.
  • Techniques may include sending a first signal to a third device.
  • the first signal may initiate a verification of an authorization of the second MTC device to receive the information.
  • the verification may be at least one of: successful or unsuccessful.
  • Techniques may include requesting, from the third device, an address of a fourth device.
  • Techniques may include receiving the address of the fourth device from the third device upon the verification being successful.
  • Techniques may include sending the request to monitor the inter-RAT handover event to the fourth device upon receipt of the address of the fourth device.
  • Techniques may include receiving, at a first MTC device, a request for information from a second MTC device regarding an inter-radio access technology (inter-RAT) handover event.
  • the information may include a request to monitor the inter-RAT handover event.
  • Techniques may include receiving, at a first MTC device, a request for information from a second MTC device regarding an inter-radio access technology (inter-RAT) handover event.
  • the information may include a request to monitor the inter-RAT handover event.
  • Techniques may include sending a first signal to a third device.
  • the first signal may initiate a verification of an authorization of the second MTC device to receive the information.
  • the verification being at least one of: successful or unsuccessful.
  • Techniques may include determining an address of a fourth device based on one or more policies of the first MTC device.
  • Techniques may include sending the request to monitor the inter-RAT handover event to the fourth device upon the verification being successful.
  • FIG. 1A depicts a system diagram of an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. IB depicts a system diagram of an example wireless transmit/receive unit
  • WTRU wireless communications
  • FIG. 1 C depicts 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.
  • FIG. ID depicts 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. IE depicts 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. 2 illustrates an example architecture model for monitoring a policy charging and control (PCC) platform and a home subscriber server (HSS) in a non-roaming scenario.
  • PCC policy charging and control
  • HSS home subscriber server
  • FIG. 3 illustrates an example technique for monitoring an event configuration by a SCS (monitoring configuration flow).
  • FIG. 4 illustrates an example monitoring of an event by way of a home subscriber server (HSS) and interworking function (IWF).
  • HSS home subscriber server
  • IWF interworking function
  • FIG. 5 illustrates an example reporting of an event by way of a policy control rule function (PCRF) and IWF.
  • PCRF policy control rule function
  • FIG. 6 illustrates an example MTC monitoring configurations at a serving general packet radio service support node (SGSN)/ mobility management entity (MME).
  • SGSN general packet radio service support node
  • MME mobility management entity
  • FIG. 7 illustrates an example MTC monitoring configuration at a wireless transmit/receive unit (WTRU).
  • FIG. 8 illustrates an example reporting of monitoring events from core network nodes (CN) (e.g., SGSN/MME) and IWF to a service capability server and an application server (SCS/AS).
  • CN core network nodes
  • SCS/AS application server
  • FIG. 9 illustrates an example flow diagram of a process of providing a MTC enhanced monitoring enhancement (MONTE) configured to request activation of an enhanced event monitoring function on one or more network nodes.
  • MONTE MTC enhanced monitoring enhancement
  • WTRU wireless transmit/receive unit
  • UE user equipment
  • 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 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 transmit/receive units (WTRUs) 102a, 102b, 102c, and/or 102d (which generally or collectively may be referred to as WTRU 102), a radio access network (RAN) 103/104/105, a core network 106/107/109, a public switched telephone network (PSTN) 108, the Internet
  • WTRUs wireless transmit/receive units
  • 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 any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (UE), 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 the like.
  • UE user equipment
  • PDA personal digital assistant
  • the communications systems 100 may also include a base station 1 14a and a base station 1 14b.
  • Each of the base stations 1 14a, 1 14b 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
  • the base stations 1 14a, 1 14b 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 the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 1 14b may include any number of interconnected base stations and/or network elements.
  • BTS base transceiver station
  • AP access point
  • the base station 1 14a 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 1 14a and/or the base station 1 14b 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 1 14a may be divided into three sectors.
  • the base station 1 14a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 1 14a 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 1 14a, 1 14b may communicate with one or more of the
  • WTRUs 102a, 102b, 102c, 102d over an air interface 115/1 16/117 which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 1 15/1 16/1 17 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 the like.
  • the base station 1 14a 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 (UTPvA), which may establish the air interface 1 15/1 16/1 17 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • the base station 1 14a and the WTRUs 102a, 102b are identical to the base station 1 14a and the WTRUs 102a, 102b,
  • E- UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • the base station 1 14a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., 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 the like.
  • IEEE 802.16 i.e., 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 1 14b in FIG. 1A may be a wireless router, Home Node B,
  • the base station 1 14b 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 1 14b 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 1 14b 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 1 14b may have a direct connection to the Internet 1 10.
  • the base station 114b may not be required to access the Internet 1 10 via the core network 106/107/109.
  • the RAN 103/104/105 may be in communication with the core network
  • the RAN 103/104/105 and/or the core network 106/107/109 may be in direct or indirect
  • 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
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 1 10 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 1 12 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 1 12 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.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., 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. 1A may be configured to communicate with the base station 1 14a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.
  • FIG. IB is a system diagram of an example WTRU 102. As shown in FIG.
  • the WTRU 102 may include a processor 1 18, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, nonremovable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
  • GPS global positioning system
  • the base stations 114a and 1 14b, and/or the nodes that base stations 1 14a 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 home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node- B gateway, and proxy nodes, among others, may include some or all of the elements depicted in FIG. IB and described herein.
  • BTS transceiver station
  • Node-B a Node-B
  • AP access point
  • eNodeB evolved home node-B
  • HeNB home evolved node-B gateway
  • proxy nodes among others, may include some or all of the elements depicted in FIG. IB and described herein.
  • the processor 1 18 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 Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 1 18 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 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. IB depicts the processor 1 18 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 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 1 14a) over the air interface 1 15/1 16/1 17.
  • a base station e.g., the base station 1 14a
  • 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 1 15/1 16/1 17.
  • 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.1 1, for example.
  • the processor 1 18 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 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 1 18 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 the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 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 1 18 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 the like.
  • the processor 1 18 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 1 15/1 16/1 17 from a base station (e.g., base stations 1 14a, 1 14b) 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 1 18 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 the like.
  • 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
  • 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, and/or 102c over the air interface 1 15.
  • 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 1 15.
  • 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 Iur 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 the like.
  • the core network 106 shown in FIG. 1C may include a media gateway
  • MGW 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 traditional 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 1 10, 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
  • 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, and/or 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 1 16.
  • 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 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 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 gateway
  • 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 activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • 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,
  • 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 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 traditional 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 1 12, 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 1 17.
  • 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,
  • 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 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 17.
  • the base stations 180a, 180b, 180c may implement MIMO technology.
  • the base station 180a for example, 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
  • 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 the like.
  • the air interface 1 17 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, authorization, IP host configuration management, and/or mobility management.
  • 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
  • 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.
  • 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 1 10, 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. For example, 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 traditional land- line communications devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 1 12, 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.
  • MSC 146, SGSN 148, MGW 144, CGSN 150, eNode-B 160a-c, MME 162, Serving Gateway 164, PDN Gateway 166, Base Station 180a-c, ASN Gateway 182, AAA 186, MIP-HA 184, and/or Gateway 188, or the like, may include one or more of the components described with respect to FIG. IB, and/or may function in the same or similar manner as described herein with respect to WTRU 102(a-d).
  • WTRU 102a-d one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, Node B 140a-c, RNC 142a-b, MSC 146, SGSN 148, MGW 144, CGSN 150, eNode-B 160a-c, MME 162, Serving Gateway 164, PDN Gateway 166, Base Station 180a-c, ASN Gateway 182, AAA 186, MIP-HA 184, and/or Gateway 188, or the like, may be performed by one or more emulation devices (not shown) (e.g., one or more devices configured to emulate one or more, or all, of the functions described herein).
  • emulation devices not shown
  • the one or more emulation devices may be configured to perform the one or more, or all, functions in one or more modalities.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented/deployed as part of a wired and/or wireless 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 one or more emulation devices may perform the one or more, or all, functions while not being implemented/deployed as part of a wired and/or wireless communication network (e.g., such as in a testing scenario in a testing laboratory and/or a non-deployed (e.g. testing) wired and/or wireless communication network, and/or testing performed on one or more deployed components of a wired and/or wireless communication network).
  • the one or more emulation devices may be test equipment.
  • FIG. 2 illustrates an example architecture model for monitoring a policy charging and control (PCC) platform and a home subscriber server (HSS) in a non-roaming scenario.
  • the interworking function receives a monitoring event subscription request or status queries from a service capability server SCS or application server (AS) and distributes those to an HSS and/or policy charging rule function PCRF in a home public land mobile network (HPLMN).
  • the PCC and/or HSS based monitoring functionality provides monitoring event reports by way of an s interface to SCS/AS or monitoring events may be reported to a Monitor Collection Entity (not shown).
  • FIG. 3 to 8 illustrate several example machine type monitoring enhancement (MTC MONTE) techniques at various network nodes, that may be configured to monitor and/or configure events.
  • FIG. 3 illustrates a procedure for monitoring an event configuration by a SCS (monitoring configuration flow).
  • FIG. 4 illustrates an example monitoring an event by way of HSS and/or IWF (monitoring event reporting flow from SGSN/MME/HSS).
  • FIG. 5 illustrates an example reporting an event by way of the PCRF and/or IWF (monitoring event reporting flow from the (GGSN/P-GW).
  • FIG. 6 illustrates example MTC monitoring configurations at SGSN/MME (monitoring MTC-IWF using the Tsp reference point shown in FIG. 2).
  • FIG. 3 illustrates a procedure for monitoring an event configuration by a SCS (monitoring configuration flow).
  • FIG. 4 illustrates an example monitoring an event by way of HSS and/or IWF (monitoring event reporting flow from SGSN/MME
  • FIG. 7 illustrates an example MTC monitoring configuration at a WTRU (monitoring configuration at the WTRU using the Tsp reference point shown in FIG. 2, by way of example).
  • FIG. 8 illustrates an example reporting of monitoring events from core network nodes (CN) (e.g., SGSN/MME) and/or IWF to SCS/AS.
  • CN core network nodes
  • MTC Machine type communication
  • the enhanced event monitoring function 900 may include monitoring one or more machine type communication (MTC) wireless transmit/receive units (WTRUs) to detect one or more changes to a plurality of configured enhanced MTC WTRUs events (902) and/or logging and/or reporting the configured enhanced MTC WTRUs events to a service capability server (SCS) and/or application server (AS) for further predetermined actions (904).
  • MTC machine type communication
  • WTRUs wireless transmit/receive units
  • AS application server
  • the MTC MONTE may be configured to report events to machine-to-machine
  • M2M mobile multi-media Subsystem
  • 3 rd party application providers may be configured to allow the 3 rd party application providers to submit additional events related to M2M services for monitoring and/or configuration by the MTC MONTE.
  • reporting of an event may be provided.
  • the change of RAT event may be configured by the system, e.g., for monitoring and/or reporting.
  • a node may report the event, e.g., assuming that the SCS/AS may configure the monitoring of a change of RAT event and/or this event may be monitored by the core network.
  • the WTRU/UE may be currently in the LTE system.
  • the serving CN node may be an MME which has been configured to monitor inter-RAT handover (HO). For example, if an inter- RAT HO occurs from LTE to UMTS, the HO may involve signaling via the MME and/or towards the SGSN.
  • HO inter-RAT handover
  • the SGSN may be the target serving CN for the after the HO is completed.
  • the MME may report the event during the detection of the HO in progress, and/or the MME may forward the configuration to the target SGSN and/or the SDSN may report the event to the HO.
  • Rate policy based triggering may be provided.
  • An operator and/or the MTC service provider and/or application owner may consider that the MTC devices do not overload (e.g. inappropriately overload) the network.
  • a trigger based on rate policing may be provided. Such a trigger may be defined and/or procedures to configure different nodes this type of trigger may be provided.
  • This type of event triggering may occur, e.g., when an individual WTRU/UE initiates a new (e.g., "fresh") PDN connection and/or a group basis. For example, event triggering may occur when the number of connections initiated by a group of WTRUs/UEs exceed the threshold of connections assigned to that group.
  • the configured enhanced MTC WTRUs/UEs events may include an enhanced list of events monitored by the system (e.g., Mobility Management Entity (MME), MTC WTRU, evolved node Base eNB, and the like).
  • MME Mobility Management Entity
  • MTC WTRU evolved node Base e
  • the configured enhanced MTC WTRUs/UEs events may include the detection of a change in radio access technology (RAT) used by the MTC WTRU.
  • RAT radio access technology
  • a detected change in RAT may include a change from long term evolution (LTE) to Global System for Mobile Communications (GSM) to an enhanced data rates for GSM evolution (EDGE) radio access network (GERAN), and/or from a LTE to Universal Mobile
  • the nodes that can report this event may be the WTRU/UE, the serving core network (CN), and/or the packet data network (PDN) gateway (GW). This may be reported by way of the IWF and/or other evolved packet core (EPC) entities, and/or directly to the SCS and/or AS.
  • EPC evolved packet core
  • the configured enhanced MTC WTRUs events may include detection of a designation of the MTC WTRU as a back off device (e.g., back off timer expires).
  • the system may monitor backing off devices.
  • the CN node may know when a non-access stratum (NAS) procedure is rejected with a backoff (BO) timer. It may report this event to the IWF which, in turn, reports to the SCS/AS.
  • a base station e.g., eNB
  • One or more MTC WTRUs may be configured such that they are identified as low access priority devices as such they may have their remote radio control (RRC) connection released with an indication of a BO time during which the MTC WTRU may BO.
  • RRC remote radio control
  • the MTC WTRUs, for which the eNB still has context, the eNB may inform the MME about the BO when it happens.
  • the MME may in turn report to the IWF which passes the report to the SCS/AS.
  • the configured enhanced MTC WTRUs events may include detection of a failed attachment associated with the MTC WTRU and/or detection of a failed tracking area update (TAU) procedure associated with the MTC WTRU.
  • a failed Attach and/or TAU procedure can be reported even if no event has been previously submitted.
  • the device may be identified by its IMSI. This notification can be provided from the CN node (e.g., MME) to the IWF.
  • a MTC WTRU's NAS request that is rejected may be configured as an event and/or may be reported when it happens.
  • the SCS/AS can request monitoring when the MTC WTRU enters, and/or leaves, a certain closed subscriber group (CSG) cell and/or local network.
  • CSG closed subscriber group
  • the SCS/AS may be configured to request to monitoring if the MTC WTRU gets rejected for access from a CSG cell and/or local network, and the like.
  • the MME sees such an event (e.g., a NAS message sent from a CSG cell, and/or if, for example, the MME rejects a MTC WTRU request either based on location and/or access restriction, and/or other reasons, the CN (e.g., MME) reports this to the IWF).
  • the configured enhanced MTC WTRUs events may include detection of the use of one or more service parameters associated with the MTC WTRU. That is, an event that reflects the MTC WTRU's service parameters: such as a number of access barring faced, amount of other delay at access (e.g., any form of BO by the RAN e.g., generated by an eNB), uplink and/or downlink metrics related to user plane such as quality of service (QoS), packet rate, and the like. Other events may include radio link failure, and the number of RRC connections established and/or rejected within a certain time.
  • service parameters associated with the MTC WTRU may include detection of the use of one or more service parameters associated with the MTC WTRU. That is, an event that reflects the MTC WTRU's service parameters: such as a number of access barring faced, amount of other delay at access (e.g., any form of BO by the RAN e.g., generated by an eNB), uplink and/or downlink metrics related
  • These events may be submitted by the SCS/AS which may then use one or more techniques described herein to request their configuration and/or monitoring at various nodes (e.g., UE, and/or eNB).
  • Other events that may be requested include the number of hand overs HOs, and/or number of cell change in general (e.g., in idle and/or connected mode), the number of inter-RAT HO, and the like. These events may also be monitored by the eNB.
  • the configured enhanced MTC WTRUs events may include detection of a combined registration performed by the MTC WTRU.
  • the configured enhanced MTC WTRUs events may include detection of an event that the MTC WTRU's registration changed from combined to non-combined registration (e.g., from combined EPS and IMSI to EPS only, and/or the like).
  • a non-combined registration may be done when the MTC WTRU performs a TAU and sets the request type to "EPS only," which may cause the MTC
  • the registration type may be reported for example when the MTC WTRU registers (e.g., the reporting node may differentiate the registration based on its type such as packet switch (PS) only, and/or circuit switch (CS) only, and/or combined PS/CS, and the like).
  • PS packet switch
  • CS circuit switch
  • the configured enhanced MTC WTRUs events may include detection of a change in the WTC WTRU's data settings, and/or a change in the WTC WTRU's voice settings. An event that the WTRU's data and/or voice settings change may be reported by the WTRU when it happens, and/or it can be reported by the MME when it receives registration messages that can hint at these events.
  • the configured enhanced MTC WTRUs events may include detection of a transmission, and/or a reception of a short message service (SMS), by the WTC WTRU. This enhanced event may, for example, be reported by the WTRU and/or MME.
  • SMS short message service
  • the configured enhanced MTC WTRUs events may include detection of a predetermined packet data network (PDN) connection for an emergency service that was established by the MTC WTRU.
  • PDN packet data network
  • the configured enhanced MTC WTRUs events may include detection of one or more predetermined PDN parameters and/or Internet Protocol (IP) type employed by the MTC WTRU. For example, an event that a PDN connection with a certain IP type (e.g., IPv4 or IPv6) was established.
  • IP Internet Protocol
  • the configured enhanced MTC WTRUs events may include detection that a certain number of PDN connections and/or bearers are present.
  • the configured enhanced MTC WTRUs events may include detection that a certain access point name (APN) was used for establishment of a PDN connection.
  • APN access point name
  • This type of event triggering may occur, e.g., when an individual WTRU/UE initiates a new (e.g., fresh) PDN connection and/or a group basis. Perhaps for example, when the number of connections initiated by a group of WTRUs/UEs may exceed the threshold of connections assigned to that group.
  • the configured enhanced MTC WTRUs events may include detection of a failed authentication (e.g., bootstrapping authentication) by the MTC WTRU after a predetermined number of attempts.
  • a failed authentication e.g., bootstrapping authentication
  • an event may be that authentication fails after N trials where N is an integer that may be preconfigured and/or provided in the event submission (e.g., from the SCS/AS).
  • the configured enhanced MTC WTRUs events may include detection of the activation and/or deactivation of power saving mode by the MTC WTRU.
  • the configured enhanced MTC WTRUs events may include detection of an occurrence of a mobile originated (MO) circuit switch fallback (CSFB) associated with the MTC WTRU.
  • MO mobile originated
  • CSFB circuit switch fallback
  • the configured enhanced MTC WTRUs events may include detection of an occurrence of a mobile termination (MT) CSFB associated with the MTC WTRU.
  • MT mobile termination
  • the configured enhanced MTC WTRUs events may include detection that proximity service (ProSe) communication is used, enabled and/or deactivated by the MTC WTRU.
  • the configured enhanced MTC WTRUs events may include detection that group communication system enabler (GCSE) communication is used, enabled and/or deactivated by the MTC WTRU.
  • GCSE group communication system enabler
  • the configured enhanced MTC WTRUs events may include detection that the
  • MTC WTRU has overridden its low access priority characteristics. This event may be, for example, monitored by the CN (e.g., MME since the WTRU includes a low access priority information element in the NAS message, but it does not set it to true). In this scenario, the MME may know that the WTRU is overriding its low access priority feature and may report that to any other node that requested this event (e.g., HSS, IWF, MSC/VLR, and the like).
  • the CN e.g., MME since the WTRU includes a low access priority information element in the NAS message, but it does not set it to true.
  • the MME may know that the WTRU is overriding its low access priority feature and may report that to any other node that requested this event (e.g., HSS, IWF, MSC/VLR, and the like).
  • the configured enhanced MTC WTRUs events may include detection and reporting of an event that an IP connectivity to application server is not successful.
  • the configured enhanced MTC WTRUs events may include detection of an event to notify application server, e.g., if data limit exceeded.
  • the event notification may be provided over an IP connection.
  • the configured enhanced MTC WTRUs events may include detection of an event to notify application server general diagnostic information.
  • the detecting may include detection of crash of an MTC application.
  • the event notification may be provided over an IP connection.
  • the configured enhanced MTC WTRUs events may include detection of an event to notify the application server, e.g., when a request for digital certificate/public key is denied.
  • the configured enhanced MTC WTRUs events may include detection of an event that access to the SCS/AS through the network of a particular operator is denied.
  • the event notification may include the identifier of the operator and/or the identifier of the network.
  • a report for such event may be provided by the device and/or by a network node.
  • the configured enhanced MTC WTRUs events may include detection of an event that service request establishment failed for one or more (e.g. a particular) APN(s).
  • a report for such event may be provided by the device and/or by a network node.
  • the configured enhanced MTC WTRUs events may include detection of an event to report access failure over a specific RAT, e.g., E-UTRAN, UTRAN, GERAN, WiFi, etc.
  • a report for such event may be provided by the device and/or by a network node.
  • the configured enhanced MTC WTRUs events may include detection of an event for reaching and/or exceeding a spending limit.
  • the configured enhanced MTC WTRUs events may include detection of an event triggered when there is a policy enforcement conflict. For example, the event may be detected when policy rates may exceed the predefined thresholds. For such purpose various nodes in the system may monitor the defined rates.
  • the WTRU/UE may monitor the UL APN-AMBR and it may trigger and/or send an event report to SCS and/or AS, when bit rate reaches above a certain threshold. This threshold may be different from the UL APN-AMBR and/or APN-AMBR and/or Group APN-AMBR values etc.
  • the eNB may be configured to monitor AMBR and report an event when the value goes above the predefined threshold.
  • This WTRU/UEAMBR event triggering may be provided at an individual device level and/or for a group of MTC devices.
  • the S-GW and the P-GWs may be configured to monitor the rate in the downlink direction and may report, e.g., if there rates exceed the assigned threshold.
  • the configured enhanced MTC WTRUs events may include detection of an event including traffic for services and/or application not defined by the SCS and/or the AS (e.g., traffic for an MTC Server).
  • the configured enhanced MTC WTRUs events may include detection of an event that includes traffic destined for an unknown destination, e.g., not defined by the SCS and/or the AS (e.g., traffic destined to an MTC server).
  • the configured enhanced MTC WTRUs events may include detection of an event that includes traffic not destined to and/or not related to the service defined for a particular MTC device.
  • the configured enhanced MTC WTRU may detect traffic for services and/or application, e.g., not defined by the MTC Server and/or it might detect traffic destined for an unknown destination and/or a destination that has nothing to do with the Service Defined for a particular MTC device. For example, if an MTC device is reporting traffic towards an exampledomain.com server when the device may have been sending traffic to the utility company's server (e.g. perhaps in some embodiments, perhaps only the utility's company's server), detection of such traffic may be determined and/or detected as an abnormal behavior event.
  • the utility company's server e.g. perhaps in some embodiments, perhaps only the utility's company's server
  • the configured enhanced MTC WTRUs events may include detection of a predetermined number of occurrences of a plurality monitoring events described herein and/or a predetermined combination of monitoring events associated with the MTC WTRU.
  • a monitoring event may be defined such that when N (where N is an integer) occurrences of this event occurs, the system can report it (e.g., one report generated).
  • the SCS/AS can submit such a request to the IWF and the IWF can then forward to the SCS/AS.
  • the configured enhanced MTC WTRUs events may include detection of a change in location (e.g., change in IP address and/or change in geographic location), a change in the association between the MTC WTRU and a universal integrated circuit card (UICC), a change in the WTRU reachability, and a loss of connectivity.
  • a change in location e.g., change in IP address and/or change in geographic location
  • UICC universal integrated circuit card
  • One or more network nodes may be designated (e.g., MTC WTRUs, mobility management entities, serving general packet radio service (GPRS) support nodes, a mobile switching center (MSC), a visitor location register (VLR), an access point (AP), a base station (BS), an evolved Node B (eNB), a radio network controller (RNC), a base station controller (BSC) and/or any other radio access network (RAN) node. More than one node can monitor an event. The nodes that monitor an event may report the event using the same manner in which they were configured, for example.
  • GPRS general packet radio service
  • MSC mobile switching center
  • VLR visitor location register
  • AP access point
  • BS base station
  • eNB evolved Node B
  • RNC radio network controller
  • BSC base station controller
  • RAN radio access network
  • the one or more network nodes may employ one or more MTC MONTE techniques to perform the enhanced event monitoring function monitoring as described herein: a technique employing monitoring by way of a policy charging and control (PCC) platform and a home subscriber server (HHS), a technique which employs monitoring an association between and International Mobile Subscriber Identity (IMSI) and an IMEI- software version (SV) of the MTC WTRU, and a technique which employs monitoring via MTC-interworking function (IWF) using a Tsp reference point.
  • the IWF and/or any other node e.g., HSS
  • the IWF may configure MME and MSC/VLR to monitor events.
  • the HSS may notify the IWF and/or the SCS/AS that the WTRU is registered in both core network (CN) nodes.
  • CN core network
  • a service capability server (SCS) / application server (AS) and various entities within a network defined by one or more third generation partnership project (3GPP) standards for the purpose of providing a supported list of events.
  • 3GPP third generation partnership project
  • a HSS, IWF, P-GW, and/or PCRF and the like including a combination of any interface that exposes an event and/or related functionality
  • the application layer e.g., IWF, SCS, AS, SCS/AS, or the like
  • the SCS/AS may request a supported list of events and/or functions that are available for the SCS/AS.
  • the SCS/AS may be configured, for example, to request the support list of events for a particular MTC WTRU and/or for a group of WTRUs as defined by a predefined identity (e.g., authorized external entity and/or 3 rd party application provider).
  • a predefined identity e.g., authorized external entity and/or 3 rd party application provider.
  • One or more network nodes may be configured to verify with the
  • the IWF may be configured to provide the identity of the MTC WTRU, and/or a group of MTC WTRUs which SCS/AS is seeking to obtain services.
  • the HSS may be configured to reply with a list of events and/or services to a predetermined list of MTC WTRUs that is authorized, and/or a group of authorized MTC WTRUs.
  • the IWF may be configured to forward the list of events and/or services and/or a list of events and/or services associated with authorized MTC WTRUs and/or a group of authorized MTC WTRUs to the SCS/AS.
  • the SCS/AS may be configured to request the monitoring of events and/or requested services from the provided lists.
  • a procedure may be provided to indicate to the AS/SCS that a set of services (e.g., event monitoring, and/or exposure functions, and/or any other function and the like) is either temporarily unavailable and/or has been resumed.
  • This indication procedure may be triggered by any node defined by one or more 3GPP standards when a failure is detected and/or due to other policies and/or events and/or maintenance aspects in the network.
  • a first node may inform a second node (e.g., SCS/AS, IWF, HSS and the like) about the unavailability of a set of services (e.g., monitoring events or other functions and the like).
  • the indication procedure may be configured, for example, to provide and/or generate a cause code, a time window during which the service may not be available, an identity of the WTRUs and/or group of WTRUs affected, and an identity of the SCS/AS that is affected.
  • the second node may in turn forward the cause code, time window during which the service may not be available, identity of the WTRUs and/or group of WTRUs affected, and/or identity of the SCS/AS that is affected to another node (e.g., SCS/AS).
  • the indication procedure may be configured, for example, to provide that the final node may refrain from submitting requests for the indicated services, for the indicated MTC WTRUs and/or group of MTC WTRUs.
  • the indication procedure may be configured, for example, to refrain from submitting requests for the indicated services, for the indicated MTC WTRUs and/or group of MTC WTRUs for a predetermined indicated time.
  • the indication procedure may be configured, for example, to indicate the resumption of a service that was previously indicated to be unavailable.
  • a gateway WTRU e.g., a gateway UE (GUE)
  • GUE gateway UE
  • a gateway WTRU may be configured to handle configuring events, and/or monitoring events, and/or reporting events for a group of other MTC WTRUs.
  • Such a GUE may be preconfigured with this function using reconfigurations in a mobile entity (ME), a universal integrated circuit card (UICC), operation management administration (OMA) entity, and/or by way of non-access stratum (NAS)/radio resource control (RRC) signaling.
  • MME mobile entity
  • UICC universal integrated circuit card
  • OMA operation management administration
  • RRC radio resource control
  • the GUE may be configured to receive a request to configure certain predetermined events for monitoring. In response to those requests, the GUE may configure one or more MTC WTRUs that are members of a predetermined group whose identity may have been received as part of the request, and/or whose identity is preconfigured in the MTC WTRU.
  • the GUE may be configured to contact one or more MTC WTRUs by employing one or more communication techniques. For example, employing a proximity-based services (ProSe), direct 1 -to-many communication devices and the like (over IP which is broadcast over RAN as defined by the ProSe operating in a service and system aspect (SA), core network terminal (CT) and/or RAN groups).
  • the GUE may be configured to receive the list of MTC WTRUs to configure, and/or may already have the information regarding the WTRUs that belong to the identified group.
  • the individual MTC WTRUs may be configured by a particular designated
  • the GUE may be configured to report to a requesting node (e.g., the node that previously submitted a request, such as a MME, a IWF, and the like) when the requesting node receives a report from any MTC WTRU and/or M2M device from the group, and/or when the requesting node receives N reports (where N is an integer, and where N may be coming from N individual MTC WTRU and/or M2M device, and/or where N may be a total of reports received from any number of MTC WTRUs and M2M devices, and/or any combination) from the MTC WTRUs and/or M2M devices.
  • a requesting node e.g., the node that previously submitted a request, such as a MME, a IWF, and the like
  • N reports where N is an integer, and where N may be coming from N individual MTC WTRU and/or M2M device, and/or where N may be a total of reports
  • the GUE may be configured, for example, to report an event that is composed of a list of events when it receives a report of one or more event defined in the list from any MTC WTRU, and/or when it receives reports for one or more events from one or more of a subset of MTC WTRU, and/or predetermined designated subset of MTC WTRUs.
  • the GUE may be configured to include the number of reported events, the number of MTC WTRUs that reported the events, the ID of the MTC WTRUs that reported the events, and/or the group of the MTC WTRUs, and/or any combination of these and/or other aspects or information.
  • a first node e.g., SCS/AS and/or HSS
  • the recipient of this request e.g., IWF, HSS, MME, and/or the like
  • This node may be configured to further send the request to a target node with the list of affected MTC WTRUs and/or the list of events to monitor.
  • This node (and/or the target node) may be configured to then generate individual monitoring requests towards one or more MTC WTRU.
  • the SCS/AS may be configured to submit a request to the IWF for a group of UEs to monitor a list of events.
  • the IWF may be configured to verify with the HSS if the request is authorized for the SCS/AS, and/or for the list of events, and/or for the group ID.
  • the IWF may be configured to hold a mapping for group ID to member MTC WTRUs ID.
  • the HSS may be configured to reply with an internal group ID that the request is applicable to the request.
  • the HSS may be configured to reply with an internal group ID that is applicable to a list of MTC WTRU IDs and/or a list of events.
  • the IWF may be configured to forward the request to the MME with the information received from HSS.
  • the MME may be configured to then monitor for one or more events set forth in the list of events.
  • the MME may be configured to then monitor one or more of the identified MTC WTRUs.
  • the MME and/or the IWF may be configured to employ one or more monitoring techniques described herein to configure a list of events for one or more of the WTRUs that are member of the identified group.
  • a priority level may define a scenario where a high priority event may cause the MTC WTRU to access the system as a high priority device.
  • a high priority event may be defined to cause a minimal delay to report the event as compared to lower priority events which may be subject to some delay.
  • a lifetime may be defined as the lifetime during which the event may be monitored.
  • the entity to which the event is requested for monitoring may stop monitoring the events. Perhaps for example if one or more of the events occurs during this time, one or more monitoring entities may report the event. After this time expires, for example, the monitoring entities may delete the event. The event may be reported for example, perhaps if a new (e.g., "fresh") request may be received, among other scenarios.
  • a new (e.g., "fresh") request may be received, among other scenarios.
  • a validity time window may define the time during which a report may be sent after an event occurs.
  • the validity time window may be defined such that if the reporting and/or monitoring entity cannot send the report during a predetermined time (which may start after the event occurs), the entity may save this as a new (e.g. "fresh") event and/or may report it (e.g., later) as a failure and/or other event.
  • the priority level, a lifetime during which the event may be monitored, and/or validity time window which defines the time during which a report may be sent after an event occurs may be preconfigured in the entity that requests them, and/or may be configured in the entity that monitors these events, and/or may be provided by the entity that submits the monitoring of any event.
  • a system may configure an MTC device on how to report monitoring events.
  • the 3 GPP system may provide configuration details, e.g., when sending monitoring requests to the MTC device.
  • the MTC configuration details may be provided by the Application Server and/or by the ANDSF.
  • the configuration information sent to MTC devices may include, e.g., the APN to provide the events (e.g., if the monitoring events are provided over an IP interface), an indication of whether monitoring events are to be provided via WLAN and/or via 3 GPP signaling, a time window to inform the MTC devices when to provide events (e.g., via NAS and/or IP signaling).
  • the SCS/AS may request the monitoring of an inter-RAT HO event and/or its reporting, e.g., when the event is about to happen and/or after the event has occurred (such as proximate to the event).
  • the SCS/AS may request the monitoring of an inter-RAT HO event and/or its reporting, e.g., when the event is about to happen and/or after the event has occurred (such as proximate to the event).
  • the IWF and/or GWF may send this request to the serving CN node.
  • IWF Interworking Function
  • GWF gateway function
  • the IWF and/or GWF may verify with the HSS, e.g., if the SCS/AS is authorized to submit this request.
  • the IWF and/or GWF may request the address of the serving CN node.
  • the HSS may perform authorization and/or respond to the IWF and/or GWF. Perhaps for example if authorized, for example, among other scenarios, the HSS may provide the address of the serving CN node.
  • the HSS may provide a policy related to where (or which node, e.g., an MME, an eNodeB, etc.) may (e.g. perhaps may best) monitor this event.
  • the HSS may include a validity timer for which this event is valid for monitoring.
  • the IWF and/or GWF may have local policies about which node may (e.g., perhaps may best) monitor the requested event and/or may have an address of this node.
  • the IWF and/or GWF may use its available (e.g. local) addressing information and/or the address provided by the HSS to send the request to the appropriate node, e.g., the MME.
  • the IWF and/or GWF may indicate that the node to monitor the event, e.g., the MME and/or the eNodeB and/or the UE, and/or a combination, and/or a target CN node in the case of inter- RAT HO, and/or other nodes that may be defined accordingly.
  • the IWF and/or GWF may include a validity timer for which this event is valid for monitoring.
  • the MME may save the requested event and/or may forward the request to other nodes, e.g., if this event is to be monitored by another node, e.g., an eNodeB and/or an UE.
  • the MME may use an S1AP message and/or may include a set of IE to indicate the event type, and/or other details, e.g., the RAT for which an inter-RAT HO may (e.g., perhaps may best) be monitored. For example, from LTE to GERAN, and/or LTE to UMTS, and/or LTE to LTE (intra- RAT HO).
  • the MME may include a validity timer for which this event is valid for monitoring.
  • the validity timer may be provided by the MME, e.g., whenever there is a connection established with the RAN (e.g., an eNodeB) for the WTRU/UE in question.
  • the MME may forward the request to the UE, e.g., using an NAS message.
  • the request may include a set of IEs to indicate the event type, and/or other details that may be desired, e.g., for which RAT an inter-RAT HO may be monitored, e.g. from LTE to GERAN, and/or LTE to UMTS, and/or LTE to LTE (intra-RAT HO).
  • the MME may include a validity timer for which this event may be valid for monitoring.
  • a source node may be a source serving CN node (e.g. MME, SGSN, etc.), and/or the source serving RAN node (e.g., an eNodeB), and/or the WTRU/UE (e.g., in a source system).
  • Target node may referred to the target CN node (e.g. SGSN, MME, etc.), and/or the target RAN node (e.g. eNodeB and/or RNC, and/or BSC) and/or the WTRU/UE (e.g., in the target system).
  • the source node may report the event, e.g., when the HO signaling starts.
  • the source node may report the event, e.g., after a HO may be completed, e.g., after the source node may receive a confirmation from the target node about completion of the HO.
  • the source MME may report the event to the eNodeB, e.g., after the MME may receive the Forward Relocation Complete Notification message from a target SGSN.
  • the MME may report after responding with Forward Relocation Complete Acknowledge message to the SGSN.
  • the source eNodeB may report the event, e.g., after initiating a HO and after receiving a request from the MME to release the UE's resources/context.
  • the target node may report the event.
  • the source node e.g., an MME
  • the target node e.g., an SGSN
  • the context may include the configuration for one or more, or each, of the events (e.g., each of the other related parameters, e.g., validity timer per event, etc.) that may be monitored.
  • the context may also include the address of the IWF and/or GWF.
  • the target node may send a report to the IWF and/or GWF, e.g., using the address provided from the source node and/or using any local addressing information.
  • the target node may send the report, e.g., after the HO completes and/or at any time after the reception of the context from the source node.
  • the target node e.g., target RAN node e.g. RNC, BSC, etc.
  • the configured event may be forwarded from the source node (e.g., source RAN in the HO request e.g.
  • the target node e.g. target RNC, BSC
  • the target node may send the report once the HO request is received and/or after the completion of the HO.
  • One or more, or each, of the source and/or target nodes described herein may report a failure of HO if detected.
  • Idle mode inter-RAT reselection may be provided.
  • one or more of the following may be provided for the report of the mobility event.
  • a source node e.g., an MME and/or an SGSN may report the event, e. g., when the target node sends a request to fetch the WTRU/UE context.
  • the target node e.g., a target SGSN and/or target MME
  • the source node may report the mobility event.
  • the source node may report the event, e.g., after responding with a Context Response message.
  • the source node may include the address of the target node to the IWF and/or GWF. If the source node reports an event, the source node may include the address of the IWF and/or GWF to the SCS/AS, e.g., if the address is known. This may help the SCS/AS to follow up with other requests it may have towards the target serving nodes.
  • the target node may report the event, e.g., after the target node may fetch the WTRU/UE context which may be proposed to include the list of configured events to be reported and/or other related parameters.
  • the WTRU/UE context may include an address for the SCS/AS.
  • the target node may send the report to the SCS/AS, e.g., after completing security (e.g., at a layer) for the WTRU/UE in question.
  • the target node may send the report after the MME and/or the SGSN activates the security context and/or algorithms for the WTRU/UE.
  • the inter and intra-RAT reelection may also applied to intra- RAT HO where the source node may be a source RAN node, a source MME and/or a WTRU/UE, and/or the target node may be a target eNodeB, the same source MME, and/or a new (e.g., "fresh") target MME, and/or the WTRU/UE.
  • the mobility event reporting is described using a mobility event from LTE to UTRAN/GERAN and/or an intra-LTE HO, the reporting may apply equally for other HO and/or mobility directions using the corresponding signaling and/or procedures.
  • Bit rate based event reporting may be provided.
  • the rate based policing and/or event reporting a as described herein may be performed at one of the nodes including, e.g., an UE, an eNodeB, an S-GW, a P-GW, etc.
  • One or some of these nodes may be configured by the network (e.g., an MME and/or an MTC-IWF etc.) to perform this event reporting.
  • the selection of these nodes may be based on one or more of the following. The selection may be based on the type of API(s) exposed and/or chosen by the MTC AS for a particular type of event reporting. One of more type of event reporting options may be offered by the SCS to the MTC AS.
  • the MTC may choose a certain API, e.g., choose an API that may report event when the bit rate at the eNodeB goes above a certain threshold.
  • the network may configure the eNodeB (for example in some embodiments perhaps only the eNodeB) for such event reporting.
  • the selection of the nodes may be based on one or more of the following factors.
  • the level of congestion at the application server may result in the configuration bit rate based event reporting. If the level of data congestion is extremely high, one or more nodes may be configured to perform rate reporting, e.g., WTRU/UE in the UL direction and/or P-GW in the downlink direction.
  • the eNodeB may also be configured to report the bit rate for a particular MTC device.
  • one of the nodes may be configured for this type of event reporting.
  • the nodes which are configured to report the event may be based on the characteristics of the group. For example, if one or more, or each, of the devices in the group are under the coverage of the same eNodeB, the eNodeB may configured to monitor and/or report this event. Perhaps for example, if a particular group is connected to multiple eNodeBs, an S-GW and/or a P-GW may be configured to report this event for such a group.
  • the assignment and/or determination of threshold values that may trigger the rate based event report may be based on one or more of the factors described above.
  • the nodes may decide not to report the events to SCS and/or AS.
  • the non-reporting of the events may be based on the type of API(s) used by the application server and/or the amount of congestion in the network etc. For example, the event may be reported if congestion is really high. Furthermore, in case of emergency situation this type of event may not reported as the devices might allowed to exceed the allowed AMBR values.
  • the techniques, processes and/or procedure described in this disclosure may apply to a Global System for Mobile communications radio access network (GERAN), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), a universal terrestrial radio access network (UTRAN), an evolved universal terrestrial radio access (eUTRAN), first responder network authority (FirstNet) or other cellular networks employing Wideband Code Division Multiple Access (WCDMA), a High Speed Packet Access (HSPA), a vehicle ad hoc network, other 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), and the like.
  • GERAN Global System for Mobile communications radio access network
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GSM EDGE
  • the techniques, processes and/or procedures described in this disclosure may be executed at the MTC WTRU, eNB, MME, HSS, SCS/AS, and the like when applicable, and in any combination.
  • a MTC WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc.
  • MTC WTRU may refer to application-based identities, e.g., user names that may be used per application.
  • 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 over wired 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).
  • ROM read only memory
  • RAM random access memory
  • 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 MTC WTRU, UE, terminal, base station, RNC, and/or any host computer.

Landscapes

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

Abstract

L'invention concerne un renforcement de la surveillance renforcée (MONTE) d'une communication de type machine (MTC), qui peut être conçu pour demander l'activation d'une fonction de surveillance d'événements renforcée sur un ou plusieurs nœuds de réseau. La fonction de surveillance d'événements renforcée peut comprendre la surveillance d'une ou plusieurs unités d'émission/réception sans fil (WTRU) de communication de type machine (MTC), afin de détecter un ou plusieurs changements d'une pluralité d'événements de WTRU de MTC renforcés et configurés et/ou l'enregistrement dans un journal et/ou le rapport des événements de WTRU de MTC renforcés et configurés vers un serveur de capacité de service (SCS) et/ou un serveur d'applications (AS) pour d'autres actions prédéfinies. La MONTE de MTC peut être conçue pour comprendre la demande d'une liste prise en charge d'événements ou de fonctions, qui sont disponibles pour le SCS et/ou l'AS, pour une WTRU de MTC identifiée et/ou un groupe de WTRU de MTC. La MONTE de MTC peut être conçue pour comprendre une indication au SCS et/ou à l'AS qu'un ensemble de services est temporairement indisponible et/ou a été repris.
PCT/US2015/029985 2014-05-08 2015-05-08 Services de surveillance de communications de type machine WO2015172079A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201461990655P 2014-05-08 2014-05-08
US61/990,655 2014-05-08
US201462018490P 2014-06-27 2014-06-27
US62/018,490 2014-06-27

Publications (1)

Publication Number Publication Date
WO2015172079A1 true WO2015172079A1 (fr) 2015-11-12

Family

ID=53268882

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/029985 WO2015172079A1 (fr) 2014-05-08 2015-05-08 Services de surveillance de communications de type machine

Country Status (1)

Country Link
WO (1) WO2015172079A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019192326A1 (fr) * 2018-04-04 2019-10-10 华为技术有限公司 Procédé, appareil et système d'abonnement à un événement
WO2020132354A1 (fr) * 2018-12-21 2020-06-25 Rj Wilson, Inc. Système et procédé de mise en œuvre de fonctions pcrf et pcef dans un véhicule
CN111435921A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 配置监控事件的方法、通信装置和通信系统
US10805841B2 (en) 2018-07-23 2020-10-13 Cisco Technology, Inc. Policy enforcement methods and apparatus for background data transfers involving multiple UEs
US10805178B2 (en) 2017-11-27 2020-10-13 Cisco Technology, Inc. Subscription-based event notification techniques for reducing data buffering in mobile networks
CN112235757A (zh) * 2019-07-15 2021-01-15 上海诺基亚贝尔股份有限公司 用于定位的方法、设备、装置和计算机可读存储介质
US20210274387A1 (en) * 2018-09-17 2021-09-02 Huawei Technologies Co., Ltd. Device and method for providing a quality of service function
CN114040482A (zh) * 2017-01-27 2022-02-11 高通股份有限公司 用于增强型空闲模式功率节省的动态ue类别切换

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
WO2014059821A1 (fr) * 2012-10-17 2014-04-24 中兴通讯股份有限公司 Procédé, système et côté réseau pour surveillance d'évènement de dispositif de communication du type machine

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
WO2014059821A1 (fr) * 2012-10-17 2014-04-24 中兴通讯股份有限公司 Procédé, système et côté réseau pour surveillance d'évènement de dispositif de communication du type machine

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Machine-Type Communications (MTC) and other mobile data applications communications enhancements (Release 12)", 3GPP STANDARD; 3GPP TR 23.887, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V12.0.0, 20 December 2013 (2013-12-20), pages 1 - 151, XP050729146 *
ZTE ET AL: "Report MTC Monitoring Event using T5 and Tsp", vol. SA WG2, 12 October 2012 (2012-10-12), XP050683710, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_93_Sofia/Docs/> [retrieved on 20121012] *

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114040482A (zh) * 2017-01-27 2022-02-11 高通股份有限公司 用于增强型空闲模式功率节省的动态ue类别切换
US10805178B2 (en) 2017-11-27 2020-10-13 Cisco Technology, Inc. Subscription-based event notification techniques for reducing data buffering in mobile networks
CN110351698B (zh) * 2018-04-04 2022-04-05 华为技术有限公司 事件订阅的方法、装置和系统
CN110351698A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 事件订阅的方法、装置和系统
WO2019192326A1 (fr) * 2018-04-04 2019-10-10 华为技术有限公司 Procédé, appareil et système d'abonnement à un événement
US11438860B2 (en) 2018-04-04 2022-09-06 Huawei Technologies Co., Ltd. Event subscription method, apparatus, and system
US10805841B2 (en) 2018-07-23 2020-10-13 Cisco Technology, Inc. Policy enforcement methods and apparatus for background data transfers involving multiple UEs
US11943663B2 (en) * 2018-09-17 2024-03-26 Huawei Technologies Co., Ltd. Device and method for providing a quality of service function
US20210274387A1 (en) * 2018-09-17 2021-09-02 Huawei Technologies Co., Ltd. Device and method for providing a quality of service function
WO2020132354A1 (fr) * 2018-12-21 2020-06-25 Rj Wilson, Inc. Système et procédé de mise en œuvre de fonctions pcrf et pcef dans un véhicule
US11076292B1 (en) 2018-12-21 2021-07-27 RJWilson, Inc. System and method for implementation of PCRF and PCEF functions in a vehicle
WO2020147717A1 (fr) * 2019-01-15 2020-07-23 华为技术有限公司 Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication
CN111435921B (zh) * 2019-01-15 2022-04-22 华为技术有限公司 配置监控事件的方法、通信装置和通信系统
CN111435921A (zh) * 2019-01-15 2020-07-21 华为技术有限公司 配置监控事件的方法、通信装置和通信系统
CN112235757A (zh) * 2019-07-15 2021-01-15 上海诺基亚贝尔股份有限公司 用于定位的方法、设备、装置和计算机可读存储介质
CN112235757B (zh) * 2019-07-15 2024-03-12 上海诺基亚贝尔股份有限公司 用于定位的方法、设备、装置和计算机可读存储介质

Similar Documents

Publication Publication Date Title
US11737019B2 (en) Application layer group services for machine type communications
US11706598B2 (en) Interface of an M2M server with the 3GPP core network
JP6725472B2 (ja) オフロードを通じた改善されたｗｌａｎ使用のための３ｇｐｐ ｗｌａｎ相互作用のための方法
US10939483B2 (en) Optimizations for prose communications
JP6100389B2 (ja) 回線交換フォールバック（ｃｓｆｂ）中のパケット交換サービスを改善するためのシステムおよび／または方法
JP6640663B2 (ja) サービスレイヤデタッチコマンドおよびアタッチ通知を処理するための方法および装置
JP6002819B2 (ja) 無線ネットワークにアタッチされていないデバイスのトリガ
EP2564622B1 (fr) Utilisation de dispositifs sans fil personnels pour des essais de réseau
US20140057566A1 (en) Enhanced higher layer discovery methods for proximity services
WO2015172079A1 (fr) Services de surveillance de communications de type machine
US20130324170A1 (en) Short messaging service (sms) over evolved packet core using wifi access
KR20160132079A (ko) 로컬 오프로드 및 소형 셀 아키텍쳐(sca)

Legal Events

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

Ref document number: 15725157

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15725157

Country of ref document: EP

Kind code of ref document: A1