WO2011134336A1 - 机器类通信事件上报方法、装置及系统 - Google Patents

机器类通信事件上报方法、装置及系统 Download PDF

Info

Publication number
WO2011134336A1
WO2011134336A1 PCT/CN2011/072394 CN2011072394W WO2011134336A1 WO 2011134336 A1 WO2011134336 A1 WO 2011134336A1 CN 2011072394 W CN2011072394 W CN 2011072394W WO 2011134336 A1 WO2011134336 A1 WO 2011134336A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
server
event
mtc event
mobility management
Prior art date
Application number
PCT/CN2011/072394
Other languages
English (en)
French (fr)
Inventor
李志军
谢宝国
曲爱妍
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/643,429 priority Critical patent/US9100771B2/en
Priority to EP11774327.8A priority patent/EP2566201B1/en
Publication of WO2011134336A1 publication Critical patent/WO2011134336A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/20Repeater circuits; Relay circuits
    • H04L25/202Repeater circuits; Relay circuits using mechanical devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202Channel estimation
    • H04L25/0224Channel estimation using sounding signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00Baseband systems
    • H04L25/02Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202Channel estimation
    • H04L25/0224Channel estimation using sounding signals
    • H04L25/0228Channel estimation using sounding signals with direct estimation from sounding signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0215Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices

Definitions

  • the present invention relates to the field of communications, and in particular to a method, device and system for reporting a machine type communication event.
  • MTC machine type communication
  • M2M machine to machine
  • M2M communication behavior is automatically controlled, that is, the initiation, termination, and control of admission and restriction in communication are automated behaviors. This behavior depends on the constraints and control of the behavior of the machine (ie, the terminal in the M2M communication) in the M2M communication.
  • the behavior of the terminal in the M2M communication is constrained by the service subscription data, and the network is in the M2M communication according to the service subscription data.
  • the terminal is managed.
  • the most typical communication method in machine type communication is the communication between the terminal and the application server.
  • the terminal is called MTC User Equipment (MTC UE), and the application server is called MTC server. ( MTC Server ).
  • MTC UE MTC User Equipment
  • MTC server MTC Server
  • the M2M communication mainly uses a Packet Service (PS) network as the underlying bearer network to implement service layer communication between the MTC terminal and the MTC server.
  • PS Packet Service
  • the M2M communication entity can access the Evolved Packet System (EPS) network through an Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
  • EPS Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the GSM/EDGE Radio Access Network (GERAN)/UTRAN network can also be used to access the General Packet Radio Service (GPRS).
  • Figure 1 is based on the related art. Schematic diagram of the architecture of the M2M communication entity accessing the EPS.
  • the MTC Server can function as an Application Function (AF).
  • the Rx interface is connected to the Policy and Charging Rules Function (PCRF). Control of the load.
  • the MTC Server can act as a SIP AS and connect to the Home Subscriber Server (HSS) through the Sh interface to access application service data.
  • the MTC UE accesses the EPS network through the E-UTRAN (eNodeB).
  • an IP channel can be established between the MTC UE and the MTC Server, thereby implementing an upper layer with the MTC Server.
  • the IP channel established between the MTC UE and the MTC Server is a logical IP channel, and its physical path passes through: eNodeB, Serving Gateway (S-GW, or SGW), and packet data network gateway ( Packet Data Network Gateway, referred to as PDN GW, or P-GW, or PGW).
  • S-GW Serving Gateway
  • PDN GW Packet Data Network Gateway
  • the status change of the MTC UE may include: the MTC UE detaches from the network, the MTC UE enters the non-connected state, the MTC UE releases the wireless connection, and the current location of the MTC UE changes.
  • the change of the state of these MTC UEs may be referred to as an MTC event, and the MTC event that needs to be monitored may be defined in the MTC subscription data of the Home Location Register (HLR)/HSS, and the MTC UE is used.
  • the process of attaching to the network is sent by the HLR/HSS to the Serving General Packet Radio Service Support Node (SGSN) / MME.
  • SGSN General Packet Radio Service Support Node
  • the network entity of the core network is usually required to detect.
  • the network element responsible for detecting the MTC event may be: MME/SGW/PGW, etc., such as the GPRS network, the network responsible for detecting the MTC event.
  • the element may be an SGSN/Gateway GPRS Support Node (GGSN).
  • GGSN GPRS Support Node
  • the MTC event can be reported by the MTC GW after the MTC event 4 is sent to the MTC GW in the following manners.
  • Sent to the MTC Server (1) If there is a direct interface between the SGSN/MME and the MTC GW, the SGSN/MME acts as an MTC event execution entity to directly report the MTC event to the MTC GW; (2) SGSN/MME utilization and GGSN/ The GTP-C message between the SGW/PGW sends the MTC event report to the GGSN/PGW.
  • the GGSN/PGW acts as an MTC event reporting entity to send an MTC event report to the MTC GW using the MTCi interface with the MTC GW; (3)
  • the SGSN/MME uses the GTP-C message to The report is sent to the GGSN/PGW, and the GGSN/PGW sends the MTC event 4 report to the PCRF by using the Gx interface with the PCRF.
  • the PCRF uses the Rx interface with the MTC GW as the MTC event 4 to send the MTC event report. To the MTC GW.
  • the MTC event can be sent to the MTC GW in two ways, and the MTC GW sends the MTC event report to the MTC GW.
  • MTC Server (1) The GGSN/PGW uses the MTCi interface with the MTC GW as the event reporting entity to send the MTC event report to the MTC GW; (2) The GGSN/PGW sends the MTC event report to the Gx interface between the PCRF and the PCRF.
  • the PCRF, PCRF, as the event 4 reporting entity uses the Rx interface with the MTC GW to send an MTC event 4 report to the MTC GW.
  • a primary object of the present invention is to provide an MTC event reporting method and system to solve at least one of the above problems.
  • a method for an MTC event including: a mobility management network element acquires, from a user subscription server, identifier information of an MTC server corresponding to an MTC device; mobility The management network element sends the identification information to the MTC event reporting entity.
  • the MTC event reporting entity reports the MTC event report of the MTC device to the MTC server corresponding to the identification information.
  • the mobility management network element obtains the identifier information of the MTC server, where: the mobility management network element sends a request to the user subscription server to request the subscription data of the MTC device; and the user subscription server sends the subscription data to the mobility management network element. Send identification information.
  • the MTC event reporting entity is a mobility management network element.
  • the MTC event reporting entity is the core network access gateway; the mobility management network element sends the identifier information to the MTC event reporting entity, including: when the bearer is created for the MTC device, the mobility management network element carries the identifier information in the bearer creation request.
  • the medium is sent to the core network gateway; or the mobility management network element sends the identification information to the core network gateway when sending the MTC event 4 to the core network gateway.
  • the MTC event reporting entity is a policy and charging rule function entity PCRF; the mobility management network element sends the identifier information to the MTC event.
  • the reporting entity includes: when the carrier is created for the MTC device, the mobility management network element identifies the information.
  • the bearer is sent to the core network gateway in the bearer creation request, and the core network gateway sends the identifier information to the PCRF by requesting the policy and charging control to the PCRF; or the mobility management network element sends the MTC event report to the core network gateway,
  • the identification information is sent to the core network gateway, and the core network gateway sends the identification information to the PCRF when sending the MTC event 4 to the PCRF.
  • the identification information is the IP address of the MTC server.
  • the MTC event reporting entity will be the MTC.
  • the MTC event report reported by the device to the MTC server corresponding to the identifier information includes: the MTC event reporting entity reports the MTC event report to the MTC server corresponding to the IP address; or the MTC event reporting entity carries the IP address in the MTC event 4
  • the advertisement is sent to the MTC access gateway, and the MTC access gateway sends the MTC event 4 report to the MTC server according to the IP address.
  • the MTC event reporting entity reports the MTC event report of the MTC device to the MTC server corresponding to the identifier information, and the MTC event reporting entity sends an MTC event report to the MTC access gateway, the MTC event.
  • the report carries the full domain name; the MTC access gateway sends a query request to the domain name server to query the IP address corresponding to the full domain name; the MTC access gateway receives the IP address returned by the domain name server, and sends the MTC event 4 report to the The MTC server corresponding to the IP address, wherein the MTC event reporting entity reports the MTC event report of the MTC device to the MTC server corresponding to the identifier information, including: the MTC event reporting entity sends a query request to the domain name server, and queries the IP address corresponding to the full domain name.
  • the MTC event reporting entity receives the IP address returned by the domain name server, and sends the MTC event 4 report to the MTC server corresponding to the IP address.
  • the MTC event reporting entity reports the MTC event report of the MTC device to the identification information.
  • the corresponding MTC server includes: The MTC event reporting entity sends a query request to the domain name server, Query the IP address corresponding to the full domain name; the MTC event reporting entity receives the IP address returned by the domain name server, and sends the IP address in the MTC event 4 to the MTC access gateway; the MTC access gateway sends the MTC event report according to the IP address.
  • a machine type communication system including: a user signing server, configured to send an identifier of an MTC server corresponding to an MTC device to a mobility management network element.
  • the mobility management network element is configured to send the identification information to the MTC event reporting entity.
  • the MTC event reporting entity is configured to report the MTC event report of the MTC device to the MTC server corresponding to the identification information.
  • the MTC event 4 reporting entity is a mobility management network element, a core network gateway, or a PCRF.
  • a mobility management network element including: an obtaining module, configured to acquire, from a user subscription server, identifier information of an MTC server corresponding to an MTC device; and a sending module, configured to send the identifier information to The MTC event reporting entity of the MTC device.
  • an MTC event reporting entity including: an obtaining module, configured to acquire, from a user subscription server or a mobility management network element, identifier information of an MTC server corresponding to an MTC device; and a sending module, configured to The MTC event report of the MTC device is sent to the MTC server corresponding to the identifier information.
  • the MTC event reporting entity reports the MTC event report to the mobility management network element when the MTC event reporting entity reports the MTC event report to the mobility management network element.
  • the MTC server corresponding to the identifier information solves the problem that the MTC server report is sent to the wrong MTC server when the MTC event report is not specified when reporting the MTC event report in the prior art, so that the MTC server can effectively The MTC device is monitored.
  • FIG. 2 is a schematic structural diagram of a machine type communication system according to Embodiment 1 of the present invention
  • FIG. 3 is a first embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an MTC event 4 reporting entity according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of a method for performing an MTC event according to Embodiment 1 of the present invention
  • FIG. 6 is a flowchart of sending identification information of an MTC server according to Embodiment 2 of the present invention
  • FIG. FIG. 8 is a signaling flowchart of an MTC event reporting method according to Embodiment 3 of the present invention
  • FIG. 8 is a signaling flowchart of an MTC event reporting method according to Embodiment 4 of the present invention.
  • FIG. 2 is a schematic structural diagram of a machine type communication system according to Embodiment 1 of the present invention.
  • the system includes: a user subscription data server 10, a mobility management network element 20, and an MTC event notification entity 30.
  • the user subscription server 10 is configured to send the identification information of the MTC server 2 corresponding to the MTC device 1 to the mobility management network element 20; the mobility management network element 20 is configured to send the identifier information of the MTC server to the
  • the MTC event notification entity 30 is configured to report the MTC event of the MTC device 1 to the MTC server 2 corresponding to the identification information.
  • the ⁇ 2 ⁇ communication entity accesses the EPS network through the E-UTRAN
  • the user subscription server 10 in the above system is the HSS
  • the mobility management network element 20 is the MME
  • the M2M communication entity passes the GERAN.
  • the user signing server 10 is the HLR
  • the mobility management network element 20 is the SGSN.
  • the MTC event 4 reporting entity 30 may be a mobility management network element 10, or may be a core network gateway (PGW in the EPS network, GGSN in the GPRS network), or may be a PCRF.
  • PGW core network gateway
  • PCRF PCRF
  • the MTC event detection entity and the MTC event 4 report entity do not specify a specific MTC server when reporting the last MTC event, thereby causing the MTC event report to be sent to the wrong MTC server, and in this embodiment
  • the user subscription server 10 sends the identification information of the MTC server corresponding to the MTC device to the mobility management network element 20, and the mobility management network element 20 sends the identification information to the MTC event reporting entity 30, where the MTC event reporting entity 30 is
  • the MTC event report is sent to the MTC server corresponding to the identifier information, so that the MTC event report can be sent to the correct MTC server, thereby ensuring that the MTC server can monitor the effective MTC device.
  • the mobility management network element 20 may include: an obtaining module 200 and a sending module 202.
  • the obtaining module 200 is configured to obtain the identifier information of the MTC server 2 corresponding to the MTC device 1 from the user subscription server;
  • the sending module 202 is configured to send the identifier information to the MTC event reporting entity 30 of the MTC device 1.
  • the obtaining module 200 may acquire the information of the MTC server from the user signing server 10 by sending a location update request to the user signing server 10 when the MTC device is attached to the network.
  • the mobility management network element 20 is used as the MTC event reporting entity 30 of the MTC event 4, the mobility management network element 20
  • the transmitting module 203 that is available does not need to send the identification information of the MTC server.
  • the mobility management network element 20 of the present embodiment can obtain the identification information of the MTC server corresponding to the MTC device from the user subscription server 10, and send the identification information to the MTC event reporting entity 30, so that the MTC event 4 reports the entity 30.
  • the MTC event report of the MTC device can be reported to the MTC server corresponding to the identifier information, and the reporting of the MTC event report to the wrong MTC server is avoided.
  • the MTC event reporting entity 30 mainly includes: an obtaining module 300 and a sending module 302. If the MTC event reporting entity 30 is the mobility management network element 20, the obtaining module 300 is configured to acquire the identification information of the MTC server 2 corresponding to the MTC device 1 from the user subscription server 10; if the MTC event reporting entity 30 is the core network gateway Or the PCRF, the obtaining module 300 is configured to acquire the identification information of the MTC server 2 corresponding to the MTC device 1 from the mobility management network element 20.
  • the sending module 302 is configured to send the MTC event report of the MTC device 1 to the MTC server corresponding to the identification information.
  • FIG. 5 is a flowchart of a method for reporting an MTC event report according to a first embodiment of the present invention.
  • the method mainly includes the following steps (step S502 - step S506): Step S502, the mobility management network element 20 acquires, from the user subscription server 10, identification information of the MTC server 2 corresponding to the MTC device 1 (that is, the MTC device 1 is connected to the MTC server 2, and the MTC server 2 manages the MTC device 1); for example
  • the user subscription server 10 may include the identification information of the MTC server 2 in the subscription data of the MTC device 1 and send it to the mobility management network element 20.
  • the identifier information may be the IP address of the MTC server 2, or may be the Fully Qualified Domain Name (FQDN) of the MTC server.
  • Step S504 the mobility management network element 20 Sending the identification information to the MTC event 4 reporting entity 30; for example, the mobility management network element 20 may send the identification information to the MTC event 4 reporting entity 30 when the bearer is created; or may be a mobility management network.
  • the element 20 serves as an MTC event detecting entity, and when transmitting the detected MTC event 4 to the MTC event 4 reporting entity 30, the mobility management network element 20 sends the identification information to the MTC event reporting entity 30.
  • the MTC event 4 reporting entity 30 is the mobility management network element 20, and the step S504 is not required to be performed.
  • the MTC event 4 reporting entity 30 reports the MTC event 4 of the MTC device 1 to the MTC server 2 corresponding to the identification information.
  • the MTC event reporting entity 30 reports the MTC event report to the corresponding MTC server 2 according to the IP address, if the identifier information is the MTC server 2
  • the FQDN the MTC event reporting entity 30 can obtain the address of the MTC server 2 from the domain name server (DNS) according to the FQDN, and report the MTC event report of the MTC device 1 to the MTC server 2.
  • DNS domain name server
  • the MTC event reporting entity 30 may directly send the MTC event report to the MTC server 2, or the MTC event reporting entity 30 may also
  • the identifier information of the MTC server 2 is sent to the MTC access gateway in the MTC event report, and the MTC access gateway sends an MTC event 4 report to the MTC server corresponding to the identifier information according to the identifier information.
  • the MTC event reporting entity 30 can obtain the IP address of the MTC server 2 according to the FQDN, and then carry the IP address in the MTC event report and send it to the MTC.
  • the FQDN may be carried in the MTC event report, and the MTC access gateway obtains the IP address of the MTC server 2 from the domain name server according to the FQDN.
  • the MTC event reporting entity 30 can use the MTC event identification information obtained by the mobility management network element 20 from the user subscription server 10 to determine the MTC device according to the above-mentioned MTC event 4 report method.
  • the MTC event report is sent to the MTC server corresponding to the MTC device, so that the MTC event report can be sent to the correct MTC server, thereby ensuring that the MTC server can effectively monitor the MTC device.
  • FIG. 6 is a flow chart of the user subscription server 10 (HLR/HSS) transmitting MTC Server information to the mobility management network element 20 (SGSN/MME) in the embodiment, which mainly includes the following steps:
  • the MTC UE requests to attach to the network
  • the SGSN/MME sends a location update request to the HLR/HSS. S603.
  • the HLR/HSS returns a location update response, and simultaneously inserts user subscription data of the MTC UE to the SGSN/MME; where, the HLR
  • the HSS includes the MTC subscription data, and defines the MTC events that need network detection, and the behaviors that the network should take after the event detection.
  • the HLR/MME sends the identifier information of the MTC server when the user subscription data is sent to the SGSN/MME.
  • the identification information of the MTC server can be the IP address of an MTC server or the FQDN of the MTC server. According to the FQDN, the DNS system can be queried to obtain the corresponding IP address.
  • the identification information of the MTC Server may be included in the MTC subscription data, or may be independent of the MTC subscription data but included in the user subscription data, or independent of the user subscription data.
  • the SGSN/MME receives the location update response, and parses the user subscription data, the MTC subscription data, and the identifier information of the MTC server.
  • the SGSN/MME can save the MTC Server information locally.
  • the MME may create a default load for the MTC UE, and initiate a create request to the PGW to create a default load for the MTC UE.
  • the SGW may interact with the PCRF to obtain a PCC policy to complete the creation of the default bearer.
  • the PGW may also obtain policies from the local policy library;
  • the SGSN/MME returns an attach response to the MTC UE, and the MTC UE successfully attaches to the network.
  • the HLR/HSS may send the identifier information of the MTC server that manages the MTC UE to the SGSN/MME when the MTC UE is attached to the network, so that when the MTC event of the MTC UE is reported subsequently,
  • the MTC event 4 reporting entity may obtain the identification information of the MTC server from the SGSN/MME to report the MTC event report to the corresponding MTC server.
  • the identifier information of the MTC server corresponding to the MTC UE is sent to the SGSN/MME, but
  • the SGSN/MME may send a request to the HLR/MME to request the identification information of the MTC server corresponding to the MTC UE, and the HLR/HSS will perform the MTC monthly service after receiving the request.
  • the identification information of the device is separately sent to the SGSN/MME.
  • Embodiment 3 This embodiment uses the mobility management network element 20 to transmit the identification information of the MTC server 2 to the MTC event and the advertising entity 30 as an example.
  • FIG. 7 is a flowchart of the SGSN/MME sending the MTC Server information to the MTC event reporting entity 30 when the SGSN/MME creates the payload for the MTC UE in the embodiment, which mainly includes the following steps:
  • the SGSN/MME obtains the identifier information of the MTC server from the HLR/HSS. In this step, the SGSN/MME may obtain the MTC from the HLR/HSS based on the foregoing Embodiment 2.
  • the MTC UE accesses the GPRS system, the MTC UE initiates a PDP context establishment process, and requests the SGSN to create a bearer for the SGSN. If the MTC UE accesses the EPS system, the S605 step corresponding to FIG. 6 is performed. The MME instructs the PGW to create a default bearer for the MTC UE. In this step, the SGSN/MME sends the identification information of the MTC Server to the GGSN/PGW in the bearer creation request, and the GGSN/PGW saves the MTC Server information. If the MTC event reporting entity 30 is a GGSN/PGW, the GGSN/PGW obtains the identification information of the MTC server in this step;
  • the GGSN/PGW needs to obtain the policy data from the PCRF in the process of creating the bearer, the GGSN/PGW requests the PCC policy from the PCRF to complete the bearer creation. In this step, if the MTC event reporting entity 30 For the PCRF, the GGSN/PGW includes the information of the MTC Server in the PCC policy request, and transmits it to the PCRF, and the PCRF saves the MTC Server information.
  • the mobility management network element may send the identifier information of the MTC server to the MTC event notification entity through the bearer creation process.
  • the fourth embodiment of the present invention uses the SGSN/MME as the MTC event detection entity, and the SGSN/MME sends the MTC server identifier to the MTC event reporting entity through the MTC event report as an example.
  • FIG. 8 is a flowchart of the SGSN/MME transmitting the identification information of the MTC Server to the MTC event 4 advertising entity (GGSN/PGW, PCRF) in the embodiment, which mainly includes the following steps:
  • Step S801 the SGSN/MME detects the MTC event; after the SGSN/MME detects the MTC event, if the SGSN/MME itself is the MTC event reporting entity, that is, the SGSN/MME has a direct connection with the MTC GW (or the MTC Server), then Step S802 is performed. If the MTC event reporting entity is the core network gateway (GGSN/PGW), step S803 is performed. If the MTC event reporting entity is the PCRF, step S803 is continued after step S803 is performed. S802: The SGSN/MME directly sends the MTC event 4 to the MTC GW (MTC Server).
  • the MTC event 4 carries the MTC Server identification information, and the MTC GW sends the MTC event.
  • the notification is sent to the MTC Server corresponding to the identification information; S803, the SGSN/MME sends the MTC event report to the GTP-C message to
  • the GGSN/PGW carries the identification information of the MTC Server at the same time. If there is a direct connection between the GGSN/PGW and the MTC Server, the GGSN/PGW sends an MTC event report to the corresponding MTC Server. Otherwise, the GGSN/PGW sends an MTC event report to the MTC GW, and the MTC event 4 is carried in the advertisement.
  • the MTC Server has the identification information of the MTC Server, and the MTC GW sends the MTC event 4 report to the MTC Server corresponding to the identifier information;
  • the GGSN/PGW sends the MTC event report to the PCRF by using the bearer change request, and carries the identifier information of the MTC server.
  • the PCRF and the MTC Server have a direct connection (Rx), and the PCRF sends an MTC event report message to the MTC Server through the Rx. Otherwise, the GGSN/PGW sends an MTC event report to the MTC GW, where the MTC event 4 is carried.
  • the MTC Server identifies the MTC event to be sent by the MTC GW to the MTC Server corresponding to the identifier information.
  • the address of the MTC Server acquired by the SGSN/MME is sent to the MTC event 4 advertising entity, so that the MTC event 4 can be sent to the correct one. MTC server.
  • the identification information of the MTC server corresponding to the MTC device is sent to the mobility management network element.
  • the MTC event reporting entity reports the MTC event report to the MTC server corresponding to the identifier information, which solves the prior art.
  • the specific MTC server is not specified, which causes the MTC event report to be sent to the wrong MTC server, so that the MTC server can effectively monitor the MTC device.
  • the computing device may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or They are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

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

Abstract

本发明公开了一种机器类通信事件上报方法、装置及系统。其中,该方法包括:移动性管理网元从用户签约服务器获取MTC设备对应的MTC服务器的标识信息;移动性管理网元将标识信息发送给MTC事件报告实体;MTC事件报告实体将MTC设备的MTC事件报告上报给标识信息对应的MTC服务器。通过本发明,使得MTC事件报告可以发送到正确的MTC服务器,进而使得MTC服务器可以有效的对MTC设备进行监控。

Description

机器类通信事件上艮方法、 装置及系统 技术领域 本发明涉及通信领域, 具体而言, 涉及一种机器类通信事件上报方法、 装置及系统。 背景技术 随着移动网络服务和自动化控制技术的发展, 出现了一种机器类通信 ( Machine Type Communication , 简称为 MTC ) 方式, 也称机器对机器 ( Machine To Machine, 简称为 M2M ) 的通信方式, 在该通信方式中, 通信 的双方为机器设备。 在 M2M通信中, 通信行为是自动化控制的, 即, 通信的发起、 终止、 及通信过程中的一些准入和限制的控制, 均是自动化的行为。 这种行为, 依 赖于 M2M 通信中对机器 (即, M2M 通信中的终端) 行为的约束和控制, M2M 通信中的终端的行为受业务签约数据约束, 网络才艮据业务签约数据对 M2M通信中的终端进行管理。 机器类通信中最典型的通信方式为终端和应用服务器之间的通信, 该终 端被称为 MTC终端 ( MTC User Equipment, 简称为 MTC UE ), 应用月艮务器 被称为 MTC月艮务器 ( MTC Server )。 在 2G/3G/LTE接入下, M2M通信主要以分组 (Packet Service, 简称为 PS )网络作为底层承载网络, 实现 MTC终端和 MTC服务器之间的业务层通 信。 具体地, M2M 通信实体可以通过演进的通用移动通信系统陆地无线接 入网 ( Evolved Universal Terrestrial Radio Access Network, 简称为 E-UTRAN ) 接入到演进的分组系统( Evolved Packet System, 简称为 EPS ) 网络, 也可以 通过 GSM/EDGE无线接入网络 ( GSM/EDGE Radio Access Network , 简称为 GERAN ) /UTRAN 网络接入到通用无线分组业务 (General Packet Radio Service, 简称为 GPRS ), 图 1是根据相关技术的 M2M通信实体接入到 EPS 的架构示意图。如图 1所示, MTC Server可以充当应用功能实体(Application Function,简称为 AF )的角色,通过 Rx接口和策略和计费规则功能实体( Policy and Charging Rules Function, 简称为 PCRF ) 连接, 以实现对 载的控制。 此外, MTC Server可以充当 SIP AS的角色, 通过 Sh接口和归属用户服务器 ( Home Subscriber Server, 简称为 HSS ) 连接, 以存取应用服务数据。 在图 1中, MTC UE通过 E-UTRAN ( eNodeB )接入到 EPS网络中, 在 被分配 IP地址后, MTC UE与 MTC Server之间可以建立起 IP通道, 从而实 现与 MTC Server之间的上层业务通信。 MTC UE与 MTC Server之间所建立 的 IP 通道为一条逻辑上的 IP 通道, 其物理路径经过: eNodeB, 月艮务网关 ( Serving Gateway,简称为 S-GW,或 SGW ),分组数据网络网关( Packet Data Network Gateway, 简称为 PDN GW, 或 P-GW, 或 PGW)。 在实际应用中, MTC Server需要监控 MTC UE的运行状态, 及时动态 地获知 MTC UE 当前的状态, 并在 MTC UE 当前的状态发生变化时 MTC Server及时获知。 其中, MTC UE的状态变化可能包括: MTC UE从网络去 附着、 MTC UE进入非连接状态、 MTC UE释放了无线连接、 MTC UE的当 前位置发生了变化等。 这些 MTC UE的状态的变化, 可以称之为一个 MTC 事件, 通常可以在归属位置寄存器 (Home Location Register, 简称为 HLR ) /HSS的 MTC签约数据中定义需要监控的 MTC事件, 并且通过 MTC UE的 附着到网络的流程由 HLR/HSS 下发给月艮务通用分组无线业务支撑节点 ( Serving General packet radio service support node, 简称为 SGSN ) /MME。 而对于 MTC事件的检测, 通常需要核心网的网络实体来检测, 如 EPS网络 中, 负责检测 MTC事件的网元可以是: MME/SGW/PGW等, 如 GPRS网络 中, 负责检测 MTC事件的网元可以是 SGSN/网关 GPRS支持节点( Gateway GPRS Support Node, 简称为 GGSN ) 等。 当 MTC事件被检测到后, 通常需 要上 4艮给 MTC Server, 以便 MTC Server及时获知 MTC UE的运行状况。 在相关技术中, 提出了由 MME/SGSN 作为 MTC 事件检测实体或 GGSN/PGW作为 MTC事件检测实体的上报方案。 其中, 在 MME/SGSN作为 MTC事件检测实体时, 当前 MME/SGSN检 测到有 MTC 事件发生时, 可以通过以下几种方式将 MTC事件 4艮告发送给 MTC GW后, 由 MTC GW将 MTC事件报告发送给 MTC Server: ( 1 ) 如果 SGSN/MME和 MTC GW间存在直接接口, 则 SGSN/MME作为 MTC事件 执行实体将 MTC事件报告, 直接发送给 MTC GW; (2)SGSN/MME利用与 GGSN/SGW/PGW间的 GTP-C消息, 将 MTC事件报告发送给 GGSN/PGW,
GGSN/PGW作为 MTC事件报告实体利用与 MTC GW的 MTCi接口,将 MTC 事件报告发送给 MTC GW; ( 3 ) SGSN/MME利用 GTP-C消息, 将 MTC事 件报告发送给 GGSN/PGW, GGSN/PGW利用与 PCRF间的 Gx接口将 MTC 事件 4艮告发送给 PCRF, PCRF作为 MTC事件 4艮告实体利用与 MTC GW间 的 Rx接口, 将 MTC事件报告发送给 MTC GW。 在 GGSN/PGW是 MTC事件检测实体时, 当前 GGSN/PGW检测到有 MTC事件发生时,可以通过以下两种方式将 MTC事件 4艮告发送给 MTC GW 后, 由 MTC GW将 MTC事件报告发送给 MTC Server: ( 1 ) GGSN/PGW作 为事件报告实体利用与 MTC GW间的 MTCi接口,将 MTC事件报告发送个 MTC GW; ( 2 ) GGSN/PGW利用与 PCRF间的 Gx接口将 MTC事件报告发 送给 PCRF, PCRF作为事件 4艮告实体利用与 MTC GW间的 Rx接口,将 MTC 事件 4艮告发送给 MTC GW。 发明人发现,在相关技术中在将 MTC事件检测实体在上报 MTC事件报 告时, 并没有指定将 MTC事件报告发送给哪个 MTC Server, 从而导致 MTC 事件报告被发送到错误的 MTC Server, 进而导致 MTC Server不能有效地对 MTC UE进行监控。 发明内容 本发明的主要目的在于提供一种 MTC事件上报方法及系统, 以至少解 决上述问题之一。 才艮据本发明的一个方面, 提供了一种 MTC事件上 4艮方法, 包括: 移动 性管理网元从用户签约月艮务器获取 MTC设备对应的 MTC月艮务器的标识信 息; 移动性管理网元将标识信息发送给 MTC事件报告实体; MTC事件报告 实体将 MTC设备的 MTC事件报告上报给标识信息对应的 MTC服务器。 其中, 移动性管理网元获取 MTC服务器的标识信息包括: 移动性管理 网元向用户签约服务器发送请求, 请求 MTC设备的签约数据; 用户签约服 务器在向移动性管理网元下发签约数据的同时下发标识信息。 其中, MTC事件报告实体为移动性管理网元。 其中, MTC事件报告实体为核心网接入网关; 移动性管理网元将标识信 息发送给 MTC事件报告实体包括: 在为 MTC设备创建承载时, 移动性管理 网元将标识信息携带在承载创建请求中发送给核心网网关; 或者移动性管理 网元在向核心网网关发送 MTC事件 4艮告时, 将标识信息发送给核心网网关。 其中, MTC事件报告实体为策略和计费规则功能实体 PCRF; 移动性管 理网元将标识信息发送给 MTC事件 4艮告实体包括:在为 MTC设备创建 载 时, 移动性管理网元将标识信息携带在承载创建请求中发送给核心网网关, 核心网网关通过向 PCRF请求策略和计费控制, 将标识信息发送给 PCRF; 或者移动性管理网元在向核心网网关发送 MTC事件报告时, 将标识信息发 送给核心网网关, 核心网网关在向 PCRF发送 MTC事件 4艮告时将标识信息 发送给 PCRF„ 其中, 标识信息为 MTC月艮务器的 IP地址。 其中, MTC事件报告实体将 MTC设备的 MTC事件报告上报给标识信 息对应的 MTC服务器包括: MTC事件报告实体将 MTC事件报告上报给与 IP地址对应的 MTC月艮务器;或者, MTC事件报告实体将 IP地址携带在 MTC 事件 4艮告中发送给 MTC接入网关, MTC接入网关才艮据 IP地址, 将 MTC事 件 4艮告发送给 MTC 艮务器。 其中, 标识信息为 MTC服务器的全域名。 其中, MTC事件报告实体将 MTC设备的 MTC事件报告上报给标识信 息对应的 MTC服务器包括: MTC事件报告实体向 MTC接入网关发送 MTC 事件报告, MTC事件报告中携带有全域名; MTC接入网关向域名服务器发 送查询请求, 查询全域名对应的 IP地址; MTC接入网关接收域名月艮务器返 回的 IP地址, 将 MTC事件 4艮告发送给与 IP地址对应的 MTC月艮务器。 其中, MTC事件报告实体将 MTC设备的 MTC事件报告上报给标识信 息对应的 MTC服务器包括: MTC事件报告实体向域名服务器发送查询请求, 查询全域名对应的 IP地址; MTC事件报告实体接收域名服务器返回的 IP地 址, 将 MTC事件 4艮告发送给与 IP地址对应的 MTC月艮务器。 其中, MTC事件报告实体将 MTC设备的 MTC事件报告上报给标识信 息对应的 MTC服务器包括: MTC事件报告实体向域名服务器发送查询请求, 查询全域名对应的 IP地址; MTC事件报告实体接收域名服务器返回的 IP地 址, 将 IP地址携带在 MTC事件 4艮告发送给 MTC接入网关; MTC接入网关 根据 IP地址, 将 MTC事件报告发送给 MTC服务器。 根据本发明的另一方面, 提供了一种机器类通信系统, 包括: 用户签约 月艮务器,设置为向移动性管理网元发送 MTC设备对应的 MTC 艮务器的标识 信息;移动性管理网元,设置为将标识信息发送给 MTC事件报告实体; MTC 事件报告实体,设置为将 MTC设备的 MTC事件报告上报给标识信息对应的 MTC 艮务器。 其中, MTC事件 4艮告实体为移动性管理网元、 核心网网关或 PCRF。 根据本发明的再一个方面, 提供了一种移动性管理网元, 包括: 获取模 块,设置为从用户签约服务器获取 MTC设备对应的 MTC服务器的标识信息; 发送模块, 设置为将标识信息发送给 MTC设备的 MTC事件报告实体。 根据本发明的又一个方面, 提供了一种 MTC事件报告实体, 包括: 获 取模块, 设置为从用户签约服务器或移动性管理网元获取 MTC设备对应的 MTC服务器的标识信息; 发送模块, 设置为将 MTC设备的 MTC事件报告 发送给标识信息对应的 MTC 艮务器。 通过本发明,由用户签约月艮务器将 MTC设备对应的 MTC月艮务器的标识 信息下发给移动性管理网元, MTC事件报告实体在上报 MTC事件报告时, 将 MTC事件报告上报给与该标识信息对应的 MTC服务器,解决了现有技术 中在上报 MTC事件报告时没有指定具体的 MTC服务器而导致将 MTC事件 报告发送到错误的 MTC服务器的问题,进而使得 MTC服务器可以有效的对 MTC设备进行监控。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据相关技术的 M2M通信实体接入到 EPS的架构示意图; 图 2是根据本发明实施例一的机器类通信系统的结构示意图; 图 3是 居本发明实施例一的移动性管理网元的结构示意图; 图 4是 居本发明实施例一的 MTC事件 4艮告实体的结构示意图; 图 5是 居本发明实施例一的 MTC事件上 ·ί艮方法的流程图; 图 6是根据本发明实施例二的 MTC服务器的标识信息下发流程图; 图 Ί是根据本发明实施例三的 MTC事件上报方法的信令流程图; 图 8是根据本发明实施例四的 MTC事件上报方法的信令流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 实施例一 图 2为根据本发明实施例一的机器类通信系统的结构示意图, 该系统包 括: 用户签约数据服务器 10、 移动性管理网元 20和 MTC事件 ^艮告实体 30。 其中, 用户签约服务器 10, 设置为向移动性管理网元 20发送 MTC设备 1 对应的 MTC服务器 2的标识信息; 移动性管理网元 20, 设置为将该 MTC 月艮务器的标识信息发送给 MTC事件 ^艮告实体 30; MTC事件 ^艮告实体 30, 设置为将 MTC设备 1的 MTC事件上报给该标识信息对应的 MTC服务器 2。 在本实施例中, 如果 Μ2Μ通信实体通过 E-UTRAN接入到 EPS网络, 则上述系统中的用户签约月艮务器 10为 HSS , 移动性管理网元 20为 MME, 如果 M2M通信实体通过 GERAN/UTRAN网络接入到 GPRS , 则用户签约月艮 务器 10为 HLR, 移动性管理网元 20为 SGSN。 其中, MTC事件 4艮告实体 30可以为移动性管理网元 10 , 也可以为核心 网网关(在 EPS网络中为 PGW,在 GPRS网络中为 GGSN ),还可以为 PCRF。 这样本实施例的系统可以釆用相关技术中所提供的任意一种方法进行 MTC 事件的检测和 4艮告。 相关技术中由于 MTC事件检测实体和 MTC事件 4艮告实体在上 4艮 MTC 事件报告时, 没有指定具体的 MTC服务器, 从而将导致 MTC事件报告被发 送到错误的 MTC服务器, 而本实施例中, 由用户签约服务器 10将 MTC设 备对应的 MTC服务器的标识信息下发给移动性管理网元 20, 由移动性管理 网元 20将该标识信息发送 MTC事件报告实体 30 , MTC事件报告实体 30在 上报 MTC事件报告时, 将 MTC事件报告发送给该标识信息对应的 MTC服 务器, 从而可以保证 MTC事件报告能够发送到正确的 MTC服务器, 进而确 保 MTC服务器可以有效的 MTC设备进行监控。 图 3 为 居本发明实施例一的移动性管理网元 20的结构示意图, 移动 性管理网元 20可以包括: 获取模块 200和发送模块 202。 其中, 获取模块 200设置为从用户签约服务器获取 MTC设备 1对应的 MTC服务器 2的标识 信息;发送模块 202设置为将该标识信息发送给 MTC设备 1的 MTC事件报 告实体 30。 例如, 获取模块 200可以在 MTC设备附着到网络时, 通过向用 户签约月艮务器 10发送位置更新请求从用户签约月艮务器 10获取 MTC月艮务器 的标 i只信息。 其中, 如果 MTC事件 ^艮告实体 30与移动性管理网元 20合一设置, 即 移动性管理网元 20作为 MTC事件 4艮告的 MTC事件 ^艮告实体 30 , 则移动性 管理网元 20可以中的发送模块 203不需要发送 MTC月艮务器的标识信息。 通过本实施例的移动性管理网元 20可以从用户签约服务器 10获取 MTC 设备对应的 MTC服务器的标识信息,并将该标识信息发送给 MTC事件报告 实体 30 , 从而使得 MTC事件 4艮告实体 30可以将该 MTC设备的 MTC事件 报告上报给该标识信息对应的 MTC服务器,避免了将 MTC事件报告上报给 错误的 MTC服务器。 图 4为才艮据本发明实施例一的 MTC事件 ^艮告实体 30的结构示意图, MTC事件报告实体 30主要包括: 获取模块 300和发送模块 302。 其中, 如 果 MTC事件报告实体 30为移动性管理网元 20 ,则获取模块 300设置为从用 户签约服务器 10获取 MTC设备 1对应的 MTC服务器 2的标识信息; 如果 MTC事件报告实体 30为核心网网关或 PCRF , 则获取模块 300设置为从移 动性管理网元 20获取 MTC设备 1对应的 MTC服务器 2的标识信息。 发送 模块 302设置为将 MTC设备 1的 MTC事件报告发送给该标识信息对应的 MTC 艮务器。 通过本实施例的上述 MTC事件报告实体, 可以将 MTC设备的 MTC事 件报告上报给与该 MTC设备对应的 MTC服务器, 从而可以保证将 MTC事 件 4艮告发送给正确的 MTC月艮务器。 图 5为根据本发明实施例一的 MTC事件报告上报方法的流程图, 该方 法主要包括以下步骤 (步骤 S502 -步骤 S506 ): 步骤 S502, 移动性管理网元 20从用户签约服务器 10获取 MTC设备 1 对应的 MTC服务器 2 (即 MTC设备 1与 MTC服务器 2连接, 由 MTC服务 器 2对 MTC设备 1进行管理) 的标识信息; 例如,用户签约服务器 10可以将 MTC服务器 2的标识信息包含在 MTC 设备 1的签约数据中发给移动性管理网元 20。 例如, 该标识信息可以为 MTC月艮务器 2 的 IP地址, 或者, 也可以为 MTC月艮务器的全域名 ( Fully Qualified Domain Name, 简称为 FQDN )„ 步骤 S504, 移动性管理网元 20将该标识信息发送给 MTC事件 4艮告实 体 30; 例如, 移动性管理网元 20可以在创建承载时, 将标识信息发送给 MTC 事件 4艮告实体 30; 或者, 也可以是移动性管理网元 20作为 MTC事件检测实 体, 在向 MTC事件 4艮告实体 30发送检测到的 MTC事件 4艮告时, 移动性管 理网元 20将该标识信息发送给 MTC事件 告实体 30。 其中, 如果 MTC事件报告实体 30为移动性管理网元 20, 则不需要执行 步骤 S504。 步骤 S506, MTC事件 4艮告实体 30将 MTC设备 1的 MTC事件 4艮告上 报给该标识信息对应的 MTC服务器 2。 例如, 如果该标识信息为 MTC服务器 2的 IP地址, 则 MTC事件报告 实体 30根据该 IP地址将 MTC事件报告上报给对应的 MTC服务器 2 , 如果 该标识信息为 MTC服务器 2的 FQDN, 则 MTC事件报告实体 30可以根据 该 FQDN从域名月艮务器 ( Domain Name Server, 简称为 DNS ) 获取 MTC 务器 2的地址,从而将 MTC设备 1的 MTC事件报告上报给 MTC服务器 2。 在实际应用中, 如果 MTC事件报告实体 30与 MTC服务器 2之前存在 直接连接的接口, 则 MTC事件报告实体 30可以直接将 MTC事件报告发送 给 MTC服务器 2 , 或者, MTC事件报告实体 30也可以将 MTC服务器 2的 标识信息携带在 MTC事件报告中发送给 MTC接入网关, MTC接入网关根 据该标识信息将 MTC事件 4艮告发送给该标识信息对应的 MTC月艮务器。在标 识信息为 FQDN时, MTC事件报告实体 30可以才艮据该 FQDN获取到 MTC 服务器 2的 IP地址后, 将该 IP地址携带在 MTC事件报告中发送给 MTC接 入网关, 或者, 也可以将该 FQDN携带在 MTC事件报告中, 由 MTC接入 网关根据该 FQDN从域名服务器获取 MTC服务器 2的 IP地址。 通过本实施例的上述 MTC 事件 4艮告上 4艮方法, MTC事件 ^艮告实体 30 可以才艮据移动性管理网元 20从用户签约服务器 10获取的 MTC服务器的标 识信息, 将 MTC设备的 MTC事件报告发送给与该 MTC设备对应的 MTC 服务器, 从而使得 MTC事件报告可以发送给正确的 MTC服务器, 进而保证 MTC月艮务器可以有效地对 MTC设备进行监控。 实施例二 本实施例以 MTC UE附着到网络时, 用户签约月艮务器 10向移动性管理 网元 20下发该 MTC UE对应的 MTC月艮务器为例进行说明。 图 6为本实施例中用户签约服务器 10 ( HLR/HSS ) 下发 MTC Server信 息给移动性管理网元 20 ( SGSN/MME ) 的流程图, 主要包括如下步 4聚:
5601 , MTC UE请求附着到网络;
5602, SGSN/MME向 HLR/HSS发送位置更新请求; S603 , 响应于 SGSN/MME的位置更新请求, HLR/HSS返回位置更新响 应, 同时向 SGSN/MME插入 MTC UE的用户签约数据; 其中, HLR/HSS在向 SGSN/MME下发用户签约数据时, 同时包含 MTC 签约数据, 在其中定义了需要网络检测的 MTC事件, 以及事件检测后网络 所应釆取的行为等。 其中, HLR/MME在向 SGSN/MME下发用户签约数据时, 下发 MTC 务器的标识信息。 MTC Server的标识信息可以是一个 MTC服务器的 IP地址, 也可以是 MTC月艮务器的 FQDN,根据该 FQDN可以查询 DNS系统获得对应 的 IP地址。 其中, MTC Server的标识信息可以包含在 MTC签约数据中, 也可以独 立于 MTC签约数据但包含在用户签约数据中, 或者独立于用户签约数据。
S604, SGSN/MME 接收到位置更新响应, 从中解析出用户签约数据、 MTC签约数据及 MTC月艮务器的标识信息; SGSN/MME可以在本地保存 MTC Server信息。
5605 , 可选地, 对于 EPS系统, MME可能为 MTC UE创建缺省 载, ΜΜΕ向 PGW发起 载创建请求, 为 MTC UE创建缺省 载;
5606, 基于 S605 , 在创建缺省承载的过程中, PGW可能与 PCRF交互 以获得 PCC策略, 以完成缺省承载的创建。 PGW也可能从本地策略库中获 取策略;
5607, SGSN/MME向 MTC UE返回附着响应, MTC UE成功附着到网 络。 通过本实施例, HLR/HSS可以在 MTC UE附着到网络时将管理该 MTC UE的 MTC服务器的标识信息下发给 SGSN/MME, 从而使得后续在上报该 MTC UE的 MTC事件 4艮告时, MTC事件 4艮告实体可以从 SGSN/MME获取 该 MTC服务器的标识信息,以将 MTC事件报告上报给对应的 MTC服务器。 需要说明的是, 虽然本实施例中以 MTC UE附着时, HLR/HSS下发该 MTC UE的用户签约信息时, 将该 MTC UE对应的 MTC服务器的标识信息 下发给 SGSN/MME, 但并不限于此, 例如, SGSN/MME 可以在需要时向 HLR/MME发送请求, 请求该 MTC UE对应的 MTC月艮务器的标识信息, HLR/HSS 在接收到该请求后, 将 MTC 月艮务器的标识信息单独下发给 SGSN/MME。 实施例三 本实施例以移动性管理网元 20在创建承载时将 MTC服务器 2的标识信 息发送给 MTC事件 ^艮告实体 30为例进行说明。 图 7为本实施例中 SGSN/MME在为 MTC UE创建 载时,将 MTC Server 信息下发给 MTC事件 ^艮告实体 30的流程图, 主要包括如下步骤:
S701 , SGSN/MME从 HLR/HSS获得 MTC Server的标识信息; 本步骤中, SGSN/MME可以基于上述实施例二从 HLR/HSS获得 MTC
Server的标 信息。 5702 , 如果 MTC UE所接入的是 GPRS系统, 则 MTC UE发起 PDP上 下文的建立过程, 请求 SGSN为其创建承载; 如果 MTC UE所接入的是 EPS 系统, 对应于图 6所述的 S605步骤, MME指示 PGW为 MTC UE创建缺省 承载; 在本步骤中, SGSN/MME将 MTC Server的标识信息包含在承载创建请 求中传递给 GGSN/PGW, GGSN/PGW保存该 MTC Server信息。 如果 MTC事件报告实体 30为 GGSN/PGW, 则在该步骤中 GGSN/PGW 获取到 MTC服务器的标识信息;
5703 ,基于 S702,如果 GGSN/PGW在创建承载的过程中, 需要从 PCRF 获取策略数据, GGSN/PGW则向 PCRF请求 PCC策略, 以完成承载的创建; 在本步骤中, 如果 MTC事件报告实体 30为 PCRF, 则 GGSN/PGW将 MTC Server的信息包含在 PCC策略请求中, 传递给 PCRF, PCRF保存该 MTC Server信息。
5704, 载创建完成, 返回 载创建响应。 通过本实施例, 移动性管理网元可以通过承载创建过程将 MTC服务器 的标识信息发送给 MTC事件 ^艮告实体。 实施例四 本实施例以 SGSN/MME为 MTC事件检测实体, SGSN/MME通过 MTC 事件报告将 MTC服务器的标识发送给 MTC事件报告实体为例进行说明。 图 8是本实施例中 SGSN/MME将 MTC Server的标识信息传递给 MTC 事件 4艮告实体 ( GGSN/PGW, PCRF ) 的流程图, 主要包括如下步 4聚:
S801 , SGSN/MME检测到 MTC事件; 当 SGSN/MME检测到 MTC事件后, 如果 SGSN/MME本身即为 MTC 事件报告实体, 即 SGSN/MME与 MTC GW(或 MTC Server )存在直连接口, 则执行步骤 S802; 如果 MTC事件报告实体为核心网网关 ( GGSN/PGW ), 则执行步骤 S803; 如果 MTC事件报告实体为 PCRF, 则在执行步骤 S803后 继续执行步 4聚 S804。 S802 , SGSN/MME 直接将 MTC 事件 4艮告发送给 MTC GW ( MTC Server ), 如果是发送 MTC GW, 则该 MTC事件 4艮告中携带有 MTC Server 的标识信息, MTC GW将 MTC事件 4艮告发送给与该标识信息对应的 MTC Server; S803 , SGSN/MME 通过 GTP-C 消息将 MTC 事件报告发送给
GGSN/PGW, 同时携带 MTC Server的标识信息。 如果 GGSN/PGW与 MTC Server间存在直连接口, 则 GGSN/PGW将 MTC事件报告发送给对应的 MTC Server, 否则, GGSN/PGW将 MTC事件 报告发送给 MTC GW, 该 MTC事件 4艮告中携带有该 MTC Server的标识信 息, 由 MTC GW将该 MTC事件 4艮告发送给该标识信息对应的 MTC Server;
S804 , GGSN/PGW通过承载变更请求将 MTC事件报告发送给 PCRF , 同时携带 MTC Server的标识信息。
PCRF与 MTC Server存在直连接口 ( Rx ), 则 PCRF通过 Rx将 MTC事 件报告消息发送给 MTC Server, 否则, GGSN/PGW将 MTC事件报告发送给 MTC GW, 该 MTC事件 4艮告中携带有该 MTC Server的标识信息, 由 MTC GW将该 MTC事件 4艮告发送给该标识信息对应的 MTC Server。 通过本实施例中, 可以在 SGSN/MME作为 MTC事件检测实体时, 将 SGSN/MME获取的 MTC Server的地址发送给 MTC事件 4艮告实体, 从而使 得可以将 MTC事件 4艮告发送给正确的 MTC月艮务器。 从以上的描述中, 可以看出, 通过本发明实施例, 由用户签约月艮务器将
MTC设备对应的 MTC服务器的标识信息下发给移动性管理网元, MTC事 件报告实体在上报 MTC事件报告时,将 MTC事件报告上报给与该标识信息 对应的 MTC服务器,解决了现有技术中在上报 MTC事件报告时没有指定具 体的 MTC服务器而导致将 MTC事件报告发送到错误的 MTC服务器的问题, 进而使得 MTC服务器可以有效的对 MTC设备进行监控。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 并 且在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步 4聚, 或者 将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 ^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种机器类通信 MTC事件上报方法, 包括:
移动性管理网元从用户签约服务器获取 MTC设备对应的 MTC服 务器的标识信息;
所述移动性管理网元将所述标识信息发送给 MTC事件 ^艮告实体; 所述 MTC事件报告实体将所述 MTC设备的 MTC事件报告上报 给所述标识信息对应的所述 MTC 艮务器。
2. 根据权利要求 1所述的方法,其中,所述移动性管理网元获取所述 MTC 服务器的标识信息包括:
所述移动性管理网元向所述用户签约服务器发送请求, 请求所述 MTC设备的签约数据;
所述用户签约服务器在向所述移动性管理网元下发所述签约数据 的同时下发所述标识信息。
3. 根据权利要求 1所述的方法, 其中, 所述 MTC事件报告实体为所述移 动性管理网元。
4. 根据权利要求 1所述的方法, 其中, 所述 MTC事件报告实体为核心网 接入网关;所述移动性管理网元将所述标识信息发送给 MTC事件报告 实体包括:
在为所述 MTC设备创建承载时,所述移动性管理网元将所述标识 信息携带在承载创建请求中发送给所述核心网网关; 或者
所述移动性管理网元在向所述核心网网关发送所述 MTC 事件 4艮 告时, 将所述标识信息发送给所述核心网网关。
5. 根据权利要求 1所述的方法, 其中, 所述 MTC事件报告实体为策略和 计费规则功能实体 PCRF;所述移动性管理网元将所述标识信息发送给 MTC事件报告实体包括:
在为所述 MTC设备创建承载时,所述移动性管理网元将所述标识 信息携带在 载创建请求中发送给核心网网关, 所述核心网网关通过 向所述 PCRF 请求策略和计费控制, 将所述标识信息发送给所述 PCRF; 或者
所述移动性管理网元在向所述核心网网关发送所述 MTC 事件 4艮 告时, 将所述标识信息发送给所述核心网网关, 所述核心网网关在向 所述 PCRF 发送所述 MTC 事件报告时将所述标识信息发送给所述 PCRF。
6. 根据权利要求 1至 5 中任一项所述的方法, 其中, 所述标识信息为所 述 MTC月艮务器的 IP地址。
7. 根据权利要求 6所述的方法, 其中, 所述 MTC事件报告实体将所述 MTC设备的 MTC事件报告上报给所述标识信息对应的所述 MTC服 务器包括: 所述 MTC事件报告实体将所述 MTC事件报告上报给与所 述 IP地址对应的所述 MTC月艮务器; 或者, 所述 MTC事件 ^艮告实体 将所述 IP地址携带在所述 MTC事件 4艮告中发送给 MTC接入网关, 所述 MTC接入网关根据所述 IP地址, 将所述 MTC事件报告发送给 所述 MTC 艮务器。
8. 根据权利要求 1至 5 中任一项所述的方法, 其中, 所述标识信息为所 述 MTC月艮务器的全域名。
9. 根据权利要求 8所述的方法, 其中, 所述 MTC事件报告实体将所述 MTC设备的 MTC事件报告上报给所述标识信息对应的所述 MTC服 务器包括:
所述 MTC事件报告实体向 MTC接入网关发送所述 MTC事件报 告, 所述 MTC事件报告中携带有所述全域名;
所述 MTC接入网关向域名服务器发送查询请求,查询所述全域名 对应的 IP地址;
所述 MTC接入网关接收所述域名服务器返回的 IP地址, 将所述 MTC事件 4艮告发送给与所述 IP地址对应的所述 MTC月艮务器。
10. 根据权利要求 8所述的方法, 其中, 所述 MTC事件报告实体将所述 MTC设备的 MTC事件报告上报给所述标识信息对应的所述 MTC服 务器包括: 所述 MTC事件报告实体向域名服务器发送查询请求,查询所述全 域名对应的 IP地址;
所述 MTC事件报告实体接收所述域名服务器返回的 IP地址, 将 所述 MTC事件 4艮告发送给与所述 IP地址对应的所述 MTC月艮务器。
11. 根据权利要求 8所述的方法, 其中, 所述 MTC事件报告实体将所述 MTC设备的 MTC事件报告上报给所述标识信息对应的所述 MTC服 务器包括:
所述 MTC事件报告实体向域名服务器发送查询请求,查询所述全 域名对应的 IP地址;
所述 MTC事件报告实体接收所述域名服务器返回的 IP地址, 将 所述 IP地址携带在所述 MTC事件报告发送给 MTC接入网关;
所述 MTC接入网关根据所述 IP地址, 将所述 MTC事件报告发 送给所述 MTC 艮务器。
12. 一种机器类通信系统, 包括:
用户签约服务器,设置为向移动性管理网元发送 MTC设备对应的 MTC月艮务器的标识信息;
所述移动性管理网元,设置为将所述标识信息发送给 MTC事件报 告实体;
所述 MTC事件报告实体, 设置为将所述 MTC设备的 MTC事件 艮告上 4艮给所述标识信息对应的所述 MTC 艮务器。
13. 根据权利要求 12所述的系统, 其中, 所述 MTC事件报告实体为所述 移动性管理网元、 核心网网关或 PCRF。
14. 一种移动性管理网元, 包括:
获取模块, 设置为从用户签约服务器获取 MTC设备对应的 MTC 服务器的标识信息;
发送模块, 设置为将所述标识信息发送给所述 MTC设备的 MTC 事件报告实体。
5. 一种 MTC事件 4艮告实体, 包括:
获取模块,设置为从用户签约服务器或移动性管理网元获取 MTC 设备对应的 MTC服务器的标识信息;
发送模块, 设置为将所述 MTC设备的 MTC事件报告发送给所述 标识信息对应的 MTC服务器。
PCT/CN2011/072394 2010-04-26 2011-04-01 机器类通信事件上报方法、装置及系统 WO2011134336A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/643,429 US9100771B2 (en) 2010-04-26 2011-04-01 Machine type communication event reporting method, device and system
EP11774327.8A EP2566201B1 (en) 2010-04-26 2011-04-01 Machine type communication events report method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010171476.3A CN102238517B (zh) 2010-04-26 2010-04-26 机器类通信事件上报方法、装置及系统
CN201010171476.3 2010-04-26

Publications (1)

Publication Number Publication Date
WO2011134336A1 true WO2011134336A1 (zh) 2011-11-03

Family

ID=44860850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072394 WO2011134336A1 (zh) 2010-04-26 2011-04-01 机器类通信事件上报方法、装置及系统

Country Status (4)

Country Link
US (1) US9100771B2 (zh)
EP (1) EP2566201B1 (zh)
CN (1) CN102238517B (zh)
WO (1) WO2011134336A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2835991A4 (en) * 2012-10-17 2015-08-19 Zte Corp METHOD, SYSTEM AND NETWORK SITE FOR MONITORING EVENTS IN MACHINE COMMUNICATION DEVICES

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5830361B2 (ja) * 2011-11-14 2015-12-09 株式会社Nttドコモ 移動通信方法、無線基地局及び移動局
CN103297946A (zh) * 2012-02-24 2013-09-11 中兴通讯股份有限公司 一种监控终端行为异常的方法和系统
CN103716822A (zh) * 2012-10-09 2014-04-09 中兴通讯股份有限公司 监控方法及装置
WO2014065492A1 (ko) * 2012-10-25 2014-05-01 엘지전자 주식회사 Mtc 모니터링 방법 및 네트워크 노드
CN104144434B (zh) * 2013-05-09 2018-10-09 华为技术有限公司 实现mtc监控的方法及装置
CN104168597A (zh) * 2013-05-17 2014-11-26 中兴通讯股份有限公司 监控处理方法、装置及m2m网关
EP3101928B1 (en) * 2014-02-27 2018-05-23 Huawei Technologies Co., Ltd. Method and system for providing service according to policy
CN106462536B (zh) * 2014-05-23 2019-11-08 富士通互联科技有限公司 机器类通信事件检测方法、系统及非暂态计算机可读介质
CN111385785B (zh) * 2018-12-27 2021-09-14 华为技术有限公司 一种事件监控的方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101384013A (zh) * 2008-09-26 2009-03-11 广州市聚晖电子科技有限公司 一种应用于数据采集平台的数据处理装置及处理方法
CN101459899A (zh) * 2009-01-09 2009-06-17 华为技术有限公司 机器用户的号码分配方法及通信网络
CN101500290A (zh) * 2008-01-28 2009-08-05 大唐移动通信设备有限公司 一种保留分组数据网网关地址信息的方法和系统
CN101622895A (zh) * 2007-02-02 2010-01-06 艾利森电话股份有限公司 用户设备标识符的导出

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7272397B2 (en) * 2003-10-17 2007-09-18 Kineto Wireless, Inc. Service access control interface for an unlicensed wireless communication system
CN102396284B (zh) * 2009-10-30 2015-05-06 华为技术有限公司 用于传输净负荷数据的方法和设备
US8750145B2 (en) * 2009-11-23 2014-06-10 Interdigital Patent Holdings, Inc. Method and apparatus for machine-to-machine communication registration
KR101167939B1 (ko) * 2010-01-08 2012-08-02 엘지전자 주식회사 이동통신 시스템에서의 mtc 장치의 모니터링 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101622895A (zh) * 2007-02-02 2010-01-06 艾利森电话股份有限公司 用户设备标识符的导出
CN101500290A (zh) * 2008-01-28 2009-08-05 大唐移动通信设备有限公司 一种保留分组数据网网关地址信息的方法和系统
CN101384013A (zh) * 2008-09-26 2009-03-11 广州市聚晖电子科技有限公司 一种应用于数据采集平台的数据处理装置及处理方法
CN101459899A (zh) * 2009-01-09 2009-06-17 华为技术有限公司 机器用户的号码分配方法及通信网络

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2566201A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2835991A4 (en) * 2012-10-17 2015-08-19 Zte Corp METHOD, SYSTEM AND NETWORK SITE FOR MONITORING EVENTS IN MACHINE COMMUNICATION DEVICES
US9706058B2 (en) 2012-10-17 2017-07-11 Zte Corporation Method, system and network side of monitoring machine type communication device event

Also Published As

Publication number Publication date
CN102238517B (zh) 2015-10-21
EP2566201A1 (en) 2013-03-06
US20130039277A1 (en) 2013-02-14
CN102238517A (zh) 2011-11-09
US9100771B2 (en) 2015-08-04
EP2566201B1 (en) 2015-03-18
EP2566201A4 (en) 2013-10-30

Similar Documents

Publication Publication Date Title
WO2011134336A1 (zh) 机器类通信事件上报方法、装置及系统
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
EP3094157B1 (en) Mtc-iwf entity, pcrf entity, and control method
US9100816B2 (en) Charging method, device, and system
WO2011054299A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2019137286A1 (zh) 一种本地数据网络的指示方法及装置
US20110182244A1 (en) Method for supporting context management by home node-b
WO2011050689A1 (zh) 机器类通讯终端的接入控制方法和系统
WO2011140884A1 (zh) Mtc组选择分组数据网网关的方法及移动性管理网元
US8837355B2 (en) Bearer processing method and mobile management device
WO2011054300A1 (zh) Mtc终端的接入控制方法和系统
US20110320544A1 (en) Diameter session audits
US8885608B2 (en) Mobile communication method
WO2008086754A1 (fr) Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur
WO2012068728A1 (zh) 获取用户的ip地址的方法和网络实体
WO2013163945A1 (zh) 一种机器类通信事件的上报方法及相应装置
WO2011050688A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2009089776A1 (fr) Procédé et appareil de maintenance des informations de fonction de règle de politique et de facturation
WO2016062025A1 (zh) 一种策略和计费规则功能的选择方法及装置
WO2011134370A1 (zh) 机器类通信事件上报方法及系统
WO2009138016A1 (zh) 信息传递方法、装置和系统
WO2013135213A1 (zh) Tdf会话的处理方法及pcrf
WO2013037271A1 (zh) 一种多接入方法及系统
WO2011134315A1 (zh) 业务授权方法、装置及系统
WO2011134321A1 (zh) 机器类通信的策略下发方法及系统

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13643429

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2011774327

Country of ref document: EP