WO2015200644A1 - Améliorations apportées aux communications de type machine (mtc) à base de groupes - Google Patents

Améliorations apportées aux communications de type machine (mtc) à base de groupes Download PDF

Info

Publication number
WO2015200644A1
WO2015200644A1 PCT/US2015/037704 US2015037704W WO2015200644A1 WO 2015200644 A1 WO2015200644 A1 WO 2015200644A1 US 2015037704 W US2015037704 W US 2015037704W WO 2015200644 A1 WO2015200644 A1 WO 2015200644A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
maximum bit
mtc
bit rate
aggregated maximum
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2015/037704
Other languages
English (en)
Inventor
Saad Ahmad
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
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 WO2015200644A1 publication Critical patent/WO2015200644A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • EPC Evolved Packet Core
  • EPS may support simultaneous multiple packet data network (PDN) connections to the same access point name (APN) with termination on the same packet data network gateway (PGW).
  • PGW is the entity that enforces the access point name-aggregate maximum bit rate (APN-AMBR) by rate policing the maximum allowed total throughput across all non-guaranteed bit- rate (GBR) bearers for a specific APN.
  • APN-AMBR access point name-aggregate maximum bit rate
  • GRR non-guaranteed bit- rate
  • APN-AMBR may be independent of the number of PDN connections and non-GBR bearers.
  • the operator may limit total bandwidth for APN and prevent a WTRU from increasing bandwidth by opening new PDN connections.
  • the PGW may initiate signaling for each connection to update the APN-AMBR value.
  • This value may be defined in the HSS for each PDN connection in the "EPS subscribed QoS profile" which may contain bearer level QoS & subscribed APN-AMBR.
  • An exposure entity such as an MTC exposure layer, may send one or more group aggregated maximum bit rates to an application server (AS).
  • the exposure entity such as an MTC exposure layer, may receive a selected group aggregated maximum bit rate from the AS.
  • the exposure entity may forward the selected group aggregated maximum bit rate to a network enforcement entity for enforcement.
  • the exposure entity may determine an MTC group aggregated maximum bit rate.
  • the MTC group aggregated maximum bit rate may be determined based on the received selected group aggregated maximum bit rate.
  • the exposure entity such as the MTC exposure layer, may then forward the determined MTC group aggregated maximum bit rate to a network enforcement entity for enforcement.
  • the aggregated maximum bit rates may be access point name- aggregate maximum bit rates (APN-AMBRs).
  • the exposure entity such as the MTC exposure layer, may determine or receive the one or more aggregated maximum bit rate options for an MTC group.
  • the exposure entity such as the MTC exposure layer, may be located within one or more of a services capabilities exposure function (SCEF), an MTC-interworking function (IWF), a services capabilities server (SCS), a gateway general packet radio service (GPRS) Support Node (GGSN)/packet data network gateway (PGW) and a network entity.
  • the network enforcement entity may be located within one or more of a PGW, a charging enforcement function (PCEF) and a policy and charging rules function (PCRF).
  • PCEF policy and charging rules function
  • the MTC-IWF may calculate the APN-AMBR based on MTC applications running or other characteristics constituting a group of MTC devices. Methods for determining whether data traffic is intended for group communication are also described herein. Methods for monitoring and enforcing the group APN-AMBR are also described herein.
  • FIG. 1A 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. 1A;
  • 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. 2 is an example architecture used for an machine-type communication (MTC) device connecting to the 3 rd Generation Partnership Project (3GPP) network; and
  • MTC machine-type communication
  • 3GPP 3 rd Generation Partnership Project
  • FIG. 3 is a diagram of an example signaling flow for determining a group bit rate.
  • 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, 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • 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 (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
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and the like.
  • the communications systems 100 may also include a base station
  • 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, the Internet 110, and/or the other 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 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 104, 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, i.e., 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, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the base station 114a in the RAN 104 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 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • the base station 114a and the WTRUs are identical to the base station 114a and the WTRUs.
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE- Advanced
  • the base station 114a and the WTRUs are identical to the base station 114a and the WTRUs.
  • the base station 114b in FIG. 1A may be a wireless router, Home
  • Node B, Home eNode B, or access point 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 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 required to access the Internet 110 via the core network 106.
  • the RAN 104 may be in communication with the core network
  • the core network 106 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 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.
  • the RAN 104 and/or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106 may also serve as a gateway for the
  • 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.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • IP internet protocol
  • 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 104 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 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 processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 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 116.
  • 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 116.
  • 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 nonremovable 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 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 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 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals
  • the peripherals 138 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.
  • 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.
  • FM frequency modulated
  • FIG. 1C is a system diagram of the RAN 104 and the core network 106 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 116.
  • the RAN 104 may also be in communication with the core network 106.
  • the RAN 104 may include eNode-Bs 140a, 140b, 140c, 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 140a, 140b, 140c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 140a, 140b, 140c may implement MIMO technology.
  • the eNode-B 140a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 140a, 140b, 140c 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. 1C, the eNode-Bs 140a, 140b, 140c may communicate with one another over an X2 interface.
  • the core network 106 shown in FIG. 1C may include a mobility management entity gateway (MME) 142, a serving gateway 144, and a packet data network (PDN) gateway 146. 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.
  • MME mobility management entity gateway
  • PDN packet data network
  • the MME 142 may be connected to each of the eNode-Bs 140a,
  • the MME 142 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 142 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 144 may be connected to each of the eNode
  • the serving gateway 144 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the serving gateway 144 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 144 may also be connected to the PDN gateway 146, 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 146 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 106 may facilitate communications with other networks.
  • the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit- switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the core network 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 106 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 MME may receive an access point name-aggregate maximum bit rate (APN-AMBR) parameter from the home subscriber server (HSS) as part of the subscription data contained in an Update Location Acknowledgement (Ack) message.
  • APN-AMBR access point name-aggregate maximum bit rate
  • HSS home subscriber server
  • Ack Update Location Acknowledgement
  • This parameter may be sent to the packet data network gateway (PGW) during the bearer establishment process in a "Create Session Request Message" from the Serving Gateway (SGW) to the PGW.
  • PGW may receive this in the "Create Session Request Message" from the MME.
  • the PGW may enforce the rate in the downlink (DL) direction.
  • the MME may send the APN-AMBR information to a WTRU in an "Attach Accept” message.
  • the WTRU may police this rate in the uplink (UL) direction.
  • a WTRU may be connected to more than one PDN (e.g., PDN 1 for Internet, PDN 2 for VoIP using IMS, etc.).
  • the WTRU may have one unique IP address for each of its all PDN connections.
  • WTRU-AMBR (UL/DL) may indicate the maximum bandwidth allowed for all of the non- guaranteed bit-rate (GBR) Evolved Packet System (EPS) bearers associated to the WTRU, regardless of how many PDN connections the WTRU has.
  • GLR non- guaranteed bit-rate
  • EPS Evolved Packet System
  • Other PDNs may be connected through other PGWs, and this parameter may be applied by eNode Bs.
  • the eNode B may enforce the policing of WTRU-AMBR.
  • Group based policing of machine-type communication (MTC) devices may be enforced. Enforcing AMBR policing at a group level, i.e., for a group of MTC devices, allows for greater flexibility and easier enforcement of AMBR rate compared to enforcing the policy at an individual device level.
  • a per policy group DL APN-AMBR may be supported with group based policy control; a per device DL APN-AMBR may be supported in conjunction with group based policy control; and a per device UL APN-AMBR may be supported in conjunction with group based policy control.
  • FIG. 2 is an example architecture used for an MTC device connecting to the 3 rd Generation Partnership Project (3GPP) network. The descriptions below are made in reference to FIG. 2.
  • 3GPP 3 rd Generation Partnership Project
  • the example architecture 200 shows a WTRU 202 operating in a visited public land network (VPLMN) 270, which may be in communication with a home public land network (HPLMN) 250.
  • the WTRU may also operate in a HPLMN and the examples disclosed herein apply equally to that case.
  • the WTRU 202 may communicate with a RAN 204 over an interface, which may be a Um, Uu and/or LTE-Uu interface. Further, the WTRU 202 may be in communication via the RAN 204 with a mobile switching center (MSC) 280, MME 242, serving general packet radio service (GPRS) support node (SGSN) 290 and/or a SGW 244.
  • the WTRU 202 may run an MTC application 292.
  • the MSC 280, MME 242 and SSGN 290 may communicate with an MTC-Interworking Function (MTC-IWF) 220.
  • MTC-IWF MTC-Interworking Function
  • serving MSC 280 may communicate with MTC-IWF 220 via reference point T5c
  • serving MME 242 may communicate with MTC-IWF 220 via reference point T5b
  • serving SGSN 290 may communicate with MTC- IWF 220 via reference point T5a.
  • SGSN 290 may communicate with gateway GPRS Support Node (GGSN)/PGW 246.
  • GGSN gateway GPRS Support Node
  • a GGSN of the GGSN/PGW 246 may in turn communicate with application server (AS) 203 via reference point Gi and a PGW of GGSN/PGW 246 may communicate with AS 203 via reference point SGi.
  • AS application server
  • a GGSN of GGSN/PGW 246 may communicate with a services capabilities server (SCS) 210 via reference point Gi or and a PGW of GGSN/PGW 246 may communicate with SCS 210 via reference point SGi.
  • SCS 210 may in turn communicate with AS 201.
  • MTC-IWF 220 may communicate with SCS 210 via reference point Tsp, and may communicate with AS 201 through SCS 210.
  • the MTC-IWF 220 may also communicate with HSS 230 via reference point S6m and MTC-authentication, authorization and accounting (MTC-AAA) entity 235 may communicate with HSS 230 via reference point S6n.
  • the MTC-IWF 220 may communicate with charging data function (CDF)/charging gateway function (CGF) 260 via reference point Rf/Ga and short message service- service center (SMS-SC)/gateway mobile switching center (GMSC)/interworking mobile switching center (IWMSC) 240 via reference point T4.
  • SMS-SC/GMSC/IWMSC 240 may in turn communicate with short message entity (SME) 247 via reference point Tsms.
  • the SMS-SC/GMSC/IWMSC 240 may also communicate with IP-short message (SM)-gateway (GW) (IP-SM-GW) 245.
  • Group based policing for MTC devices may be enabled, but changes to the existing functionalities in the Evolved Packet Core (EPC) system may be needed. For example, methods and policies are needed to ensure that a particular group of MTC devices will not unduly overload the network.
  • EPC Evolved Packet Core
  • the subscription may define a group APN-AMBR for that group in the device's subscription profile in the HSS or in any other node in the system.
  • This group APN-AMBR value may not be defined as a subscription parameter but may be implicitly set by the system based on the characteristics of each group, e.g., the number of devices in the group, the type of services run by the devices in group, the other subscription parameters of group members, and the like.
  • the group APN-AMBR may be a dynamic parameter and the value of this parameter may be set up.
  • APN-AMBR policing in the DL direction may be performed by the PGW, as all the traffic may pass through the PGW.
  • a bit rate measurement and enforcement for a policy group may be within a common policy and charging enforcement function (PCEF) and that the same PCEF and policy and charging rules function (PCRF) may be selected for all members in the group. All group members may be connected to PCEF, and as PCEF may be a functional entity of a gateway (GW) (for example, a PGW or GGSN), all the group members may therefore be connected to the same PGW. Therefore, proper implantation of this group APN-AMBR rate within different network nodes serving a particular group is desirable.
  • PCEF policy and charging enforcement function
  • PCRF policy and charging rules function
  • PGW may perform APN-AMBR monitoring and in the case of an individual WTRU, the WTRU may be responsible for enforcing APN-AMBR in the UL direction.
  • the WTRU may be responsible for enforcing APN-AMBR in the UL direction.
  • a single WTRU may or may not monitor or enforce the group APN-AMBR. Therefore, a procedure for enforcing UL APN-AMBR for a group of MTC devices is desirable so that the maximum rate is not exceeded.
  • additional subscription parameters may be used by the 3GPP system to know whether a particular WTRU supports group MTC communication and hence group APN AMBR may be defined as part of WTRU's subscription profile in the HSS.
  • non- subscription methods may be used for setting up a group APN-AMBR.
  • the IWF may calculate this value based on the MTC applications running or other characteristics which constitutes a group of MTC devices.
  • a hybrid or direct model may be used for group communication between an MTC AS and a WTRU. Accordingly, there may be an SCS in the data path and the PGW may not receive any indication whether the traffic is intended for group communication.
  • PGW may use the Traffic Detection Function to figure out that this is group based traffic.
  • a group APN-AMBR rate may be used and a single WTRU may not monitor or enforce the group APN-AMBR. Therefore, the system may divide the UL group APN-AMBR rate equally into the number of group members, e.g., devices, in the group and assign it to every WTRU. Hence, every MTC WTRU may be responsible for monitoring/enforcing its portion of the group APN-AMBR in the UL direction.
  • a group APN-AMBR subscription parameter may be defined.
  • additional subscription parameters may be used by the 3GPP system to know whether a particular WTRU supports group MTC communication and hence a group APN-AMBR may be defined as part of the WTRU's subscription profile in the HSS. This information may be needed since all WTRUs or MTC WTRUs in the system may not support this group based feature or sign up for this feature when they sign up with a particular operator.
  • a group APN-AMBR may be used for every group that the MTC device or the WTRU is configured for or expects to be part of.
  • a particular device may be part of more than one group.
  • group APN-AMBR may be defined for the WTRU on a per group basis. All members within the same group may have the same group APN-AMBR value defined for that group in their subscription profile.
  • This group APN-AMBR parameter on a per group basis may be different from an already existing non- group APN-AMBR.
  • This group APN-AMBR parameter may further be defined at finer granularity, e.g., different parameters for group UL APN-AMBR and group DL APN-AMBR may be defined in the subscription profile on a per group basis.
  • the HSS may provide such subscription information, e.g., the group APN-AMBR to the MME or any other node or entity, e.g., MTC-IWF or PCEF, etc., that is fetching the WTRU's subscription information.
  • the MME or any other node with similar functionality, e.g., a SGSN
  • should forward such information to the rest of the core network nodes such as the SGW and/or PDN Gateway (PDN GW).
  • PDN Gateway PDN Gateway
  • the WTRU may provide its capability information, e.g., MTC group communication capability, to the network or MME. It may include a new capability information element (IE) which informs the MME that this WTRU is able or capable of being a part of MTC group, for instance.
  • the MME may use the information received from the HSS together with the WTRU capability IE to get the appropriate information from the HSS.
  • the source may include such information as part of the transferred WTRU context.
  • the source MME/SGSN may do so during handover to another system node such as an SGSN/MME, respectively.
  • All of the above information e.g., UL APN-AMBR rate may be provided to the WTRU via Open Mobile Alliance (OMA) Device Management (DM), Access Network Discovery and Selection Function (ANDSF), Short Message Service (SMS), and the like.
  • OMA Open Mobile Alliance
  • DM Device Management
  • ANDSF Access Network Discovery and Selection Function
  • SMS Short Message Service
  • non- subscription methods may be used for setting up group APN-AMBR.
  • the group APN-AMBR value may not be defined as a subscription parameter, but may be implicitly set by the system based on the characteristics of each group, e.g., the number of devices in the group, the type of services run by the devices in group, the other subscription parameters of group members, and the like.
  • the group APN-AMBR may be a dynamic parameter and setting up the value of the group APN-AMBR may be performed based on various group features and actions taken by different nodes in the network.
  • the MTC-IWF 220 may calculate the group APN-AMBR value based on the MTC WTRU applications 292 running or other characteristics which constitute a group of MTC devices.
  • the MTC-IWF 220 may have a S6m interface to the HSS 230/home location register (HLR) which may be currently used by the MTC-IWF 220 to interrogate HSS 230/HLR for an E.164 mobile station international subscriber directory number (MSISDN) or external identifier mapping to international mobile subscriber identity (IMSI) and gather WTRU reachability and configuration information.
  • HLR home location register
  • MSISDN E.164 mobile station international subscriber directory number
  • IMSI international mobile subscriber identity
  • the MTC-IWF 220 may query the HSS 230 for the stored APN- AMBR for each device that is part of a particular group. Based on this collected data (APN-AMBR) for all the devices, the MTC-IWF 220 may calculate the group APN-AMBR for a particular group. This value may then be sent to other nodes in the network for policy enforcement both in UL and DL as will be described below.
  • the MTC-IWF 220 may query the SGSN 290/MME
  • the MME 242 may use the T5a/T5b interface for the invidual APN-AMBR for each device in a particular group.
  • the MME 242 may already have this information (as it may obtain it from the HSS 230/HLR as part of the attach procedure). Therefore, the MME 242 may provide this information via T5a/T5b interface to the MTC-IWF 220.
  • the MTC-IWF 220 may calculate the group APN-AMBR for a particular group. This value may then be sent to other nodes in the network for policy enforcement both in UL and DL directions. [0065] FIG.
  • the group aggregated maximum bit rate may be derived based on application programming interfaces (APIs) exposed to the group AS 330, by an exposure entity, such as an MTC exposure layer 320.
  • APIs application programming interfaces
  • the group aggregated maximum bit rates may be derived by network nodes or network entities 310 and sent 340 to the exposure entity, such as the MTC exposure layer 320.
  • Each group aggregated maximum bit rate may be applicable to control an aggregated maximum bit rate for a group of MTC devices.
  • the group aggregated maximum bit rates may be derived as group aggregated maximum bit rate options.
  • the network nodes or network entities 310 may be one or more of a PCRF, PCEF, HSS, PGW and the like.
  • the exposure entity such as MTC exposure layer 320, may be within one or more of a services capabilities exposure function (SCEF), an MTC-IWF, an SCS, a GGSN/PGW and a network entity.
  • SCEF services capabilities exposure function
  • MTC-IWF MTC-IWF
  • SCS Serving GPRS Support Node
  • GGSN/PGW GGSN/PGW
  • the group aggregated maximum bit rates may be derived by the exposure entity, such as the MTC exposure layer 320.
  • the exposure entity, such as the MTC exposure layer 320 may derive the group aggregated maximum bit rates as group aggregated maximum bit rate options.
  • the API may provide different rate options for the application.
  • the exposure entity such as the MTC exposure layer 320
  • the group aggregated maximum bit rates may be provided as group aggregated maximum bit rate options.
  • the AS 330 may select one of the group aggregated maximum bit rates and respond to the exposure entity, such as the MTC exposure layer 320, with the selected group aggregated maximum bit rate 360.
  • the AS 330 may select one of the group aggregated maximum bit rate options.
  • the exposure entity such as MTC exposure layer 320, may forward the selected group aggregated maximum bit rate to one or more network nodes or network entities, which may be network enforcement entities, 310 for enforcement 370.
  • the exposure entity may determine an MTC group aggregated maximum bit rate. The determination of the MTC group aggregated maximum bit rate may be based on the received selected aggregated maximum bit rate. Further, the exposure entity, such as MTC exposure layer 320, may forward the determined MTC group aggregated maximum bit rate to one or more network nodes or network entities, which may be network enforcement entities, 310 for rate policing or enforcement 370. These network nodes or network entities 310 may then implement the group policy based on this rate 380.
  • the group aggregated maximum bit rates may be group APN-AMBRs.
  • the group aggregated maximum bit rate options may be group APN- AMBR options.
  • the group APN-AMBR may be derived or selected by one of the network nodes or network entities 310, such as MTC or 3GPP EPC nodes, e.g., MTC-IWF, MTC server, SCS or PCEF, and the like. These network nodes or network entities 310 may have a translation or mapping between the selected API bit rate option and group APN-AMBR which may be understood by various EPC nodes or entities, e.g., MME, GWs, PCRF, and the like. These network nodes or network entities 310 would then implement the group policy based on this rate 380.
  • MTC or 3GPP EPC nodes e.g., MTC-IWF, MTC server, SCS or PCEF, and the like.
  • These network nodes or network entities 310 may have a translation or mapping between the selected API bit rate option and group APN-AMBR which may be understood by various EPC nodes or entities, e.g., MME, GWs, PCRF, and the
  • rate enforcement may be performed in the
  • the APN-AMBR policing in the DL direction may be performed by the PGW 246 as the user plane traffic may pass through the PGW 246.
  • the PGW 246 may need to know whether a particular packet, data or IP flow, is for a group based communication or not.
  • the indirect model as shown in FIG. 2 may be used to serve this purpose.
  • the SCS 210 may therefore indicate to the PGW 246 whether a particular data/IP flow is for a group based communication by including the identification, e.g., MTC Group ID, etc., of such group communication.
  • the PCEF may apply the group APN- AMBR policy to such an IP flow to ensure that it does exceed the assigned or determined rate value.
  • the PGW 246 may not receive any indication regarding whether the traffic is intended for group communication.
  • the PGW 246 may use the traffic detection function (TDF) to determine that the traffic is group based traffic. This may be achieved by a TDF identifying the same traffic content going to multiple WTRU (different destination IP) addresses at a similar time. This may trigger the PGW/PCEF to apply group based policy for such traffic.
  • TDF traffic detection function
  • the PGW/PCEF may deploy one or more of the following steps.
  • the PGW/PCEF may send an indication or a message to the SCS 210 (e.g., in the case of indirect or hybrid model) identifying the issue.
  • the SCS 210 may notify the MTC AS 201. This may limit the rate or the SCS 210 may query the AS 201 to apply a back off mechanism indicating the time for which it may not accept any traffic. This back off indication may also come from the PCEF in the PGW 246. This method may also be applied directly between the PGW 246 and the AS 203.
  • the PGW 246 may send an indication to the SCS 210 or any other node which decides group membership to perform load balancing among the group, e.g., split WTRUs in one group into multiple groups, e.g., two or more groups.
  • the PGW/PCEF may also send a request to the system, e.g. MME 242 or PCRF, to assign a higher value for a particular group based on the traffic type or traffic pattern.
  • rate enforcement may be performed in the
  • the PGW 246 may perform APN-AMBR monitoring.
  • the WTRU 202 may be responsible for enforcing APN-AMBR in the UL direction.
  • a single WTRU 202 may not be capable of monitoring or enforcing the group APN-AMBR. Therefore, the system may divide the UL group APN-AMBR rate equally into the number of group members, e.g., devices, in the group and assign it to every WTRU. In this case, every MTC WTRU may responsible for monitoring/enforcing its portion of the group APN- AMBR in the UL direction.
  • each device in the group would be responsible for enforcing X/1000 bits/sec when sending data in the UL direction.
  • this group APN-AMBR enforcement may be different from the individual or regular APN-AMBR.
  • enforcement of regular APN-AMBR may be performed by the device simultaneously to the group APN-AMBR enforcement.
  • UL group APN-AMBR rate may not be divided or split equally in all the devices belonging to a certain group.
  • the network for example, MME 242, PCRF, or based on a selected API from SCS 210 by the AS 201, may assign some devices a higher rate while other devices may be assigned a low rate, but in total the aggregate of APN-AMBR rates assigned to all the devices should be equal to the UL group APN-AMBR.
  • the different rate assignment of the devices may be based on one of more of: WTRU capabilities, locations of the WTRUs, an API selected by the SCS/AS, operator policy, and the like.
  • an eNode B may perform rate monitoring in the UL direction, especially where group MTC devices only have one PDN connection.
  • the WTRU-AMBR may be equal to APN-AMBR.
  • the MME 242 may split the group APN-AMBR between various eNode Bs to monitor. It may be split proportionally based on the number of group devices under the coverage of a particular eNode B or the system may use other factors as described above to split this rate amongst different eNode Bs. In either case, the eNode B may ensure that the devices belonging to a particular group do not exceed the assigned rate in the UL direction.
  • the UL APN-AMBR When the UL APN-AMBR is sent to the eNode B by the MME 242 for a particular group of devices (e.g., a subset of devices belonging to a MTC group) it may inform the eNode B of the identity of the devices so the eNode B knows which devices to apply that rate monitoring policy on.
  • a particular group of devices e.g., a subset of devices belonging to a MTC group
  • 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 internal hard disks and removable disks, magneto -optical media, and optical media such as CD- ROM disks, and digital versatile disks (DVDs).
  • 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, UE, terminal, base station, RNC, or any host computer.
  • a method for determining whether a wireless transmit/receive unit (WTRU) supports group machine-type communication (MTC) and group access point name-aggregate maximum bit rate (APN-AMBR), comprising: receiving an indication that the WTRU supports MTC and is capable of being a member of an MTC group.
  • MTC group machine-type communication
  • APN-AMBR group access point name-aggregate maximum bit rate
  • HSS subscription information
  • the subscription information includes a group APN-AMBR for each group the WTRU has a membership.
  • OMA Open Mobile Alliance
  • DM Device Management
  • ANDSF Access Network Discovery and Selection Function
  • SMS Short Message Service
  • a method for dynamically determining a group access point name-aggregate maximum bit rate comprising:
  • the characteristics include a number of MTC devices in each group, types of services in use by the MTC devices in each group, and other subscription parameters.
  • a method for enforcing a determined access point name- aggregate maximum bit rate (APN-AMBR) in the downlink direction comprising:
  • AMBR AMBR
  • TDF traffic detection function
  • a method for enforcing a determined access point name- aggregate maximum bit rate (APN- AMBR) in the uplink direction by a wireless transmit/receive unit comprising:
  • a wireless transmit/receive unit configured to transmit and transmit signals
  • a network node configured to implement the method of any one of embodiments 1-18.
  • An infrastructure device configured to implement the method of any one of embodiments 1-18.
  • An access point configured to implement the method of any one of embodiments 1-18.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des appareils destinés à déterminer et à mettre en application un débit binaire maximum agrégé de groupe pouvant être utilisé par une unité d'émission/réception sans fil (WTRU, Wireless Transmit Receive Unit) dans une communication de type machine (MTC, Machine-Type Communication). Une entité d'exposition, telle qu'une couche d'exposition MTC, peut envoyer un ou plusieurs débits binaires maximaux agrégés de groupe à un serveur d'application (AS, Application Server). L'entité d'exposition peut recevoir un débit binaire maximum agrégé de groupe sélectionné en provenance de l'AS. L'entité d'exposition peut transmettre le débit binaire maximum agrégé de groupe sélectionné à une entité de mise en application au réseau pour sa mise en application. En outre, l'entité d'exposition peut déterminer un débit binaire maximum agrégé de groupe MTC. Le débit binaire maximum agrégé de groupe MTC peut être déterminé sur la base du débit binaire maximum agrégé de groupe sélectionné reçu. L'entité d'exposition déterminée peut ensuite transmettre le débit binaire maximum agrégé de groupe MTC à une entité de mise en application au réseau pour sa mise en application.
PCT/US2015/037704 2014-06-27 2015-06-25 Améliorations apportées aux communications de type machine (mtc) à base de groupes Ceased WO2015200644A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201462018402P 2014-06-27 2014-06-27
US62/018,402 2014-06-27

Publications (1)

Publication Number Publication Date
WO2015200644A1 true WO2015200644A1 (fr) 2015-12-30

Family

ID=53541941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/037704 Ceased WO2015200644A1 (fr) 2014-06-27 2015-06-25 Améliorations apportées aux communications de type machine (mtc) à base de groupes

Country Status (1)

Country Link
WO (1) WO2015200644A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017141750A1 (fr) * 2016-02-17 2017-08-24 Nec Corporation Procédé pour application de mise en place de politique de données non ip sur une fonction d'exposition de service

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120209978A1 (en) * 2011-02-11 2012-08-16 Industry-Academic Cooperation Foundation, Yonsei University Group-based control method and apparatus for mtc devices in mobile communication system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120209978A1 (en) * 2011-02-11 2012-08-16 Industry-Academic Cooperation Foundation, Yonsei University Group-based control method and apparatus for mtc devices in mobile communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YANG FENG-MING ET AL: "Group-Based Control Method for Machine Type Communications in LTE System", 2013 SEVENTH INTERNATIONAL CONFERENCE ON COMPLEX, INTELLIGENT, AND SOFTWARE INTENSIVE SYSTEMS, IEEE, 3 July 2013 (2013-07-03), pages 274 - 280, XP032485657, DOI: 10.1109/CISIS.2013.51 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017141750A1 (fr) * 2016-02-17 2017-08-24 Nec Corporation Procédé pour application de mise en place de politique de données non ip sur une fonction d'exposition de service
CN107925631A (zh) * 2016-02-17 2018-04-17 日本电气株式会社 基于服务开放功能实施非ip数据监管的方法
JP2019511849A (ja) * 2016-02-17 2019-04-25 日本電気株式会社 サービスエクスポージャ機能を介して非ｉｐデータのポリシングを実施するための方法
CN113691950A (zh) * 2016-02-17 2021-11-23 日本电气株式会社 基于服务开放功能实施非ip数据监管的方法

Similar Documents

Publication Publication Date Title
KR102398798B1 (ko) 고급 의사 소통을위한 우선 순위 처리
EP3251411B1 (fr) Procédés, appareil et système de contrôle d'encombrement spécifique à l'application pour la communication de données (acdc)
KR102677335B1 (ko) 네트워크 슬라이싱 동작
US9820335B2 (en) System and method for sharing a common PDP context
KR101611965B1 (ko) 무선 통신 시스템에서 다중 우선순위 제어 방법 및 장치
EP2941905B1 (fr) Procédé et appareil de traitement de commandes de détachement d'une couche de service et de notifications de rattachement
JP6093852B2 (ja) サービス能力サーバ（ｓｃｓ）終端型ショートメッセージサービス（ｓｍｓ）システムおよび方法
JP6449912B2 (ja) マシンタイプ通信グループ通信を可能にするためのシステム、方法、および手段
TWI701954B (zh) 使用增強專用核心網路(dcn)選擇方法、裝置及系統
WO2015200644A1 (fr) Améliorations apportées aux communications de type machine (mtc) à base de groupes

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: 15736740

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: 15736740

Country of ref document: EP

Kind code of ref document: A1