WO2013056486A1 - 一种消息类型的指示方法、系统及装置 - Google Patents

一种消息类型的指示方法、系统及装置 Download PDF

Info

Publication number
WO2013056486A1
WO2013056486A1 PCT/CN2011/082474 CN2011082474W WO2013056486A1 WO 2013056486 A1 WO2013056486 A1 WO 2013056486A1 CN 2011082474 W CN2011082474 W CN 2011082474W WO 2013056486 A1 WO2013056486 A1 WO 2013056486A1
Authority
WO
WIPO (PCT)
Prior art keywords
control plane
signaling
user
plane signaling
plane data
Prior art date
Application number
PCT/CN2011/082474
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 EP11861326.4A priority Critical patent/EP2608581B1/en
Priority to US13/636,335 priority patent/US20140219183A1/en
Publication of WO2013056486A1 publication Critical patent/WO2013056486A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • 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]

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a method, system and apparatus for indicating a message type. Background technique
  • Machine to Machine refers to all the techniques and means of establishing a connection between machines.
  • the M2M concept emerged in the 1990s, but only stayed at the theoretical stage.
  • M2M business appeared on the market and developed rapidly in the following years, becoming the focus of many communication equipment vendors and telecom operators.
  • the number of machines in the world is much larger than that of people, so it is possible to foresee the good market prospects of M2M technology.
  • the existing mobile communication networks are mainly designed for communication between people, and the communication between machines and machines, people and machines is insufficiently optimized.
  • how operators can provide M2M communication services at low cost is also the key to the successful deployment of M2M communication.
  • MTC Machine Type Communication
  • H2H Human to human
  • MTC Machine to Machine and Machine
  • H2H human to human
  • MTC in terms of access control, billing, security, QoS, business model, etc.
  • the current H2H communication mode is quite different.
  • an EPS includes a radio access network and a core network
  • the radio access network may be a terrestrial radio access network (UTRAN (Universal Terrestrial Radio Access Network), Evolved UTRAN (E-UTRAN, Evolved UTRAN), GSM or EDGE Radio Access Network (GERAN, GSM or EDGE Radio Access Network), EPC, Evolved Packet Core
  • the core network may be a mobility management entity (MME, Mobility Management Entity), a service gateway (S-GW, Serving Gateway), a packet data network management (P-GW, Packet Data Network Gateway), and the like, in the GPRS core network.
  • the core network may be a network element such as a Serving GPRS Support Node (SGSN); in E-UTRAN, the core network may be an evolved Node B (eNB).
  • SGSN Serving GPRS Support Node
  • eNB evolved Node B
  • Small Data is one of the features of the MTC.
  • the focus of the Feature is: For some MTC devices, the amount of data transmitted is small, but still requires a complete signaling flow. The data is asymmetrical to the signaling involved, which causes waste of network resources. Moreover, since the number of MTC devices is often large, centralized access will inevitably bring a large amount of signaling, which is likely to cause network congestion. Therefore, it is required. A more efficient approach to the transmission of Small Data.
  • Small Data includes mobile originating (MO, Mobile Originated) services and mobile called (MT, Mobile Terminating ) A service that includes an MTC device to send or receive information.
  • MO Mobile Originated
  • MT Mobile Terminating
  • the proposed solution includes: Send Small Data via SMS, or carry Small Data through control plane signaling.
  • 2 is a schematic diagram of the architecture of the MTC in the 3GPP in the prior art. As shown in FIG. 2, for the manner of carrying the Small Data through the control plane signaling, the related control plane signaling is sent to the network node, and the network node controls the surface information. The Small Data in the command is parsed and sent to the corresponding user equipment or other network node or MTC server (MTC Server).
  • MTC server MTC server
  • the main object of the present invention is to provide a method, a system, and a device for indicating a message type, which are used to solve the problem that the user plane data is lost when the user plane data is included in the control plane signaling.
  • the present invention provides a method for indicating a message type, and setting a message type identifier in the sent control plane signaling; the method further includes:
  • the network node that receives the control plane signaling determines whether the control plane signaling includes the user plane data according to the message type identifier, and determines that the user plane data is included in the control plane signaling, and sends the user plane data to the user through the control plane signaling.
  • the device, or other network node, or the MTC Server; the user equipment or the MTC Server determines whether the control plane signaling includes user plane data, and when the control plane signaling includes user plane data, the user plane data is parsed therefrom.
  • the method further includes: When it is determined that the control plane signaling does not include the user plane data, the network node forwards the control plane signaling that does not include the user plane data to the corresponding user equipment, or other network node, or the MTC Server.
  • the message type identifier is set in the sent control plane signaling: the user equipment and/or the network node and/or the MTC server adds a message type identifier to the sent control plane signaling; wherein, the control Facet signaling is control plane signaling that includes user plane data or conventional control plane signaling.
  • the user equipment is a UE, a mobile device (ME), and a mobile station (MS);
  • the network node is an eNB, an MME, an SGSN, a P-GW, a Gateway GPRS Support Node (GGSN), and an MTC Interworking Function Entity (MTC-IWF).
  • MTC-IWF MTC Interworking Function Entity
  • control plane signaling is non-access stratum (NAS) signaling sent by the user equipment to the MME or the SGSN, or NAS signaling sent by the MME or the SGSN to the user equipment, or P-GW or GGSN.
  • NAS non-access stratum
  • the message type identifier is a message type indication bit.
  • the network node that receives the control plane signaling determines, according to the message type identifier, whether the user plane data is included in the control plane signaling:
  • the message type indication bit When the message type indication bit is 1, it indicates that the control plane signaling includes user plane data, and when it is 0, it indicates that the control plane signaling does not include user plane data;
  • the control plane signaling when the message type indication bit is 0, the control plane signaling includes user plane data, and when it is 1, it indicates that the control plane signaling does not include user plane data;
  • the message type identifier exists in the sent control plane signaling, indicating that the control plane signaling includes user plane data, and the message type identifier does not exist in the sent control plane signaling, indicating that the control plane User plane data is not included in the signaling.
  • the user plane data is sent to the user equipment or other network node or the MTC Server by using control plane signaling:
  • the network node parses the user plane data from the control plane signaling including the user plane data, and encapsulates the user plane data and the message type identifier in the control plane signaling, and sends the control plane signaling to the user equipment, or Other network nodes, or MTC Server.
  • the MTC Server determines whether the control plane signaling includes user plane data.
  • the control plane signaling includes user plane data
  • the user plane data is parsed from:
  • control plane signaling is MO signaling
  • the user equipment or the network node forwards the control plane signaling including the user plane data to the corresponding network node, and the corresponding network node forwards the received control plane signaling to the MTC Server.
  • the MTC Server determines whether the control plane signaling includes the user plane data according to the message type identifier.
  • the control plane signaling includes the user plane data
  • the user plane data is parsed from the received control plane signaling.
  • the user equipment determines whether the user plane data is included in the control plane signaling.
  • the control plane signaling includes the user plane data
  • the user plane data is parsed from:
  • control plane signaling is MT signaling
  • the MTC Server or the network node sends control plane signaling including user plane data to other network nodes, and the other network nodes send control plane data to the user equipment, and the user equipment according to the
  • the message type identifier determines whether the user plane data is included in the control plane signaling.
  • the control plane signaling includes the user plane data
  • the user plane data is parsed from the control plane signaling.
  • the present invention also provides a message type indication system, including: a user equipment, a network node, and an MTC Server;
  • the network node is further configured to determine, according to the message type identifier, whether the control plane signaling is included The user data, when the control plane signaling includes the user plane data, sends the user plane data to the user equipment, or other network node, or the MTC Server through the control plane signaling;
  • the user equipment or the MTC Server is also used to determine whether the control plane signaling includes user plane data.
  • the control plane signaling includes user plane data
  • the user plane data is parsed therefrom.
  • the network node is further configured to: when determining that the control plane signaling does not include the user plane data, forward the control plane signaling that does not include the user plane data to the corresponding user equipment, or other network node, or the MTC. Server.
  • the present invention further provides a user equipment, where the user equipment is configured to set a message type identifier in the sent control plane signaling, and is further configured to receive control plane signaling sent by the network node, and determine whether the control plane signaling includes a user plane. Data, when the control plane signaling includes user plane data, the user plane data is parsed therefrom.
  • the present invention further provides a network node, which is configured to set a message type identifier in the sent control plane signaling, and is further configured to determine, according to the message type identifier, whether the control plane signaling includes user plane data, and determine the control plane.
  • a network node which is configured to set a message type identifier in the sent control plane signaling, and is further configured to determine, according to the message type identifier, whether the control plane signaling includes user plane data, and determine the control plane.
  • the user plane data is included in the signaling, the user plane data is sent to the user equipment, or other network node, or the MTC Server through control plane signaling.
  • the network node is further configured to: when determining that the control plane signaling does not include the user plane data, forward the control plane signaling that does not include the user plane data to the corresponding user equipment, or another network node, or the MTC Server.
  • the present invention also provides an MTC server, where the MTC server is configured to set a message type identifier in the sent control plane signaling;
  • the method, system and device for indicating a message type provided by the present invention set a message type identifier in the sent control plane signaling, determine whether the control plane signaling includes user plane data, and the network node that receives the control plane signaling according to the message Type identifier, determining that the control plane signaling contains the user plane
  • the user plane data is sent to the user equipment, or other network node, or the MTC Server through control plane signaling; the user equipment or the MTC Server determines whether the control plane signaling includes user plane data, and is included in the control plane signaling.
  • the user plane data is used, the user plane data is parsed out, and the user plane data is lost when the user plane data is included in the control plane signaling, and the user plane data carried by the control plane signaling is correctly transmitted.
  • FIG. 1 is a schematic structural diagram of a 3GPP EPS in the prior art
  • FIG. 2 is a schematic structural diagram of an MTC in 3GPP in the prior art
  • FIG. 3 is a schematic flowchart of a method for indicating a message type according to the present invention.
  • FIG. 4 is a schematic flowchart of Embodiment 1 of a method for indicating a message type according to the present invention
  • FIG. 5 is a schematic flowchart of Embodiment 2 of a method for indicating a message type according to the present invention
  • FIG. 6 is a schematic diagram of an indication system for implementing a message type according to the present invention. Schematic. detailed description
  • the basic idea of the present invention is: setting a message type identifier in the sent control plane signaling; the network node receiving the control plane signaling determines whether the control plane signaling includes user plane data according to the message type identifier, and determines the control plane letter.
  • the user plane data is sent to the user equipment, or other network node, or the MTC Server through the control plane signaling; the user equipment or the MTC Server determines whether the control plane signaling includes the user plane data, when the control When the user plane data is included in the plane signaling, the user plane data is parsed therefrom.
  • FIG. 3 is a schematic flowchart of a method for indicating a message type according to the present invention. As shown in FIG. 3, the method includes the following steps:
  • Step 301 Set a message type identifier in the sent control plane signaling.
  • control device sent by the user equipment and/or the network node and/or the MTC Server Add a message type identifier to the order;
  • the control plane signaling is control plane signaling including user plane data or a conventional control plane signaling; the user plane data is Small Data in the MTC characteristic;
  • the user equipment may be a UE, a mobile device (ME, Mobile Equipment), a mobile station (MS, Mobile Station), and the user equipment is configured with a function supporting the MTC feature;
  • the network node may be an eNB, an MME, an SGSN, and a P -GW, Gateway GPRS Support Node (GGSN, Gateway GPRS Support Node), MTC Interworking Function (MTC-IWF, MTC Inter Working Function);
  • the control plane signaling is a non-access stratum (NAS, Non Access Stratum) signaling sent by the user equipment to the MME or the SGSN, or NAS signaling sent by the MME or the SGSN to the user equipment, or P-GW or GGSN.
  • NAS Non Access Stratum
  • control plane signaling sent to the MME or SGSN by the MTC-IWF or the control plane signaling sent by the MTC-IWF to the MME or the SGSN or the MTC Server, or sent by the P-GW or GGSN to the MME or the SGSN or the MTC Server Control plane signaling, or control plane signaling sent by the MTC Server to the MTC-IWF or the P-GW or the GGSN; wherein the MME or the SGSN sends the NAS signaling to the user equipment through the eNB;
  • the message type identifier added in the sent control plane signaling may be a message type indication bit, and when the message type indication bit is 1, it indicates that the control plane signaling includes user plane data, and the message type indication bit is 0. Indicates that the control plane signaling does not include user plane data, or when the message type indication bit is 0, the control plane signaling includes user plane data. When the message type indication bit is 1, it indicates that the control plane signaling does not include the user.
  • the message type identifier is added only in the sent control plane signaling including the user plane data, that is, the message type identifier exists in the sent control plane signaling, indicating that the control plane signaling includes the user plane data, The message type identifier in the sent control plane signaling does not exist, indicating that the control plane signaling does not include user plane data.
  • Step 302 The network node that receives the control plane signaling determines whether the control plane signaling includes the user plane data according to the message type identifier. If yes, go to step 303. Otherwise, perform the step. 304.
  • Step 303 The network node sends the user plane data to the user equipment or other network node or the MTC server by using the control plane signaling, and the user equipment or the MTC Server determines whether the control plane signaling includes the user plane data, and is included in the control plane signaling.
  • the user plane data the user plane data is parsed therefrom;
  • the network node parses the user plane data from the control plane signaling that includes the user plane data, and encapsulates the user plane data and the message type identifier in the control plane signaling, and sends the control plane signaling to the user.
  • the network node If the network node is a network node close to the user equipment or the MTC Server, the user plane data does not need to be forwarded through other network nodes. If the network node is not a network node close to the user equipment or the MTC Server, the user plane data needs to pass through other networks. The node performs forwarding, and the operations of other network nodes that receive control plane signaling are the same as steps 302 and 303;
  • control plane signaling arrives at the user equipment or the MTC server.
  • the user equipment or the MTC server determines whether the control plane signaling includes the user plane data according to the message type identifier therein.
  • the user equipment or the MTC Server parses the control plane signaling to obtain user plane data.
  • the user equipment or network node MME or SGSN may not parse the user plane data from the control plane signaling including the user plane data, but will control the user plane data.
  • the MTC Server forwards the control plane signaling to the MTC Server, and the MTC Server determines the control plane signaling.
  • the P-GW or the GGSN or the MTC IWF forwards the received control plane signaling to the MTC Server. Whether the user plane data is included, and when the control plane signaling includes the user plane data, the user plane data is parsed from the received control plane signaling;
  • the MTC Server or the network node MTC-IWF or the P-GW or the GGSN may not parse the user plane from the control plane signaling including the user plane data.
  • the control plane signaling including the user plane data is sent to the other network node MME or SGSN, and the MME or the SGSN sends the control plane data to the user equipment, and the user equipment determines whether the control plane signaling includes the user plane data.
  • the control plane signaling includes user plane data
  • the user plane data is parsed from the control plane signaling.
  • Step 304 The network node forwards control plane signaling that does not include user plane data to the corresponding user equipment or other network node or MTC Server.
  • Step 401 A user equipment sends an MME or an SGSN Sending NAS signaling, and setting a message type indication bit in the NAS signaling;
  • the user equipment sends the NAS signaling to the MME or the SGSN, and adds a message type indication bit to the NAS signaling;
  • the NAS signaling may be the NAS signaling sent by the user equipment in any one of the following signaling processes: The request (Attach Request), the service request (Service Request), the TAU/RAU Request, etc.; the NAS signaling includes user plane data Small Data; the size of the Small Data is generally signed by the user or the operator operates or maintains the entity. (O&M, Operation and Maintenance) or MTC Server gives;
  • the message type indication bit is a bit, and the bit is 1 or 0 or the presence indicates that the control plane signaling includes user plane data, and the bit is 0 or 1 or does not exist, indicating that the control plane signaling does not include user plane data. Whether the user plane data is included in the control plane signaling may be determined according to the value of the bit or whether it exists.
  • Step 402 The MME or the SGSN that receives the NAS signaling determines whether the NAS signaling includes user plane data according to the message type indication bit, and if yes, step 403 is performed, otherwise, step 409 is performed;
  • the MME or the SGSN first checks the message type refers to The bit is displayed to determine whether the user plane data is included in the NAS signaling.
  • Step 403 The MME or the SGSN parses the user plane data in the NAS signaling. Specifically, the MME or the SGSN parses the user plane data in the NAS signaling according to the protocol.
  • Step 404 the MME or SGSN determines whether to continue to send user plane data through the control plane, and if so, step 405 is performed, otherwise, step 407 is performed;
  • the MME or the SGSN determines whether to continue to send the user plane data through the control plane or the user plane according to the O&M indication, and if yes, execute step 405, otherwise, perform step 407.
  • Step 405 The MME or the SGSN sends the user plane data or the user plane data and the message type indication bit to the MTC-IWF through the control plane signaling.
  • the MME or the SGSN encapsulates the user plane data or the user plane data and the message type indication bit in the control plane signaling, and sends the control plane signaling to the MTC-IWF; Control plane signaling between the MME or SGSN and the MTC-IWF.
  • Step 406 The MTC-IWF determines, according to the message type indication bit, the user plane data included in the control plane signaling, and parses the user plane data from the user plane data, and sends the user plane data to the MTC Server, and the process ends;
  • the MTC-IWF belongs to a control plane network node, and the MTC-IWF determines that the control plane signaling includes user plane data according to the message type indication bit, and parses the user plane data from the user plane data or the user plane data.
  • the message type indication bit re-encapsulation is sent to the MTC Server in the control plane signaling, where the control plane signaling is control plane signaling between the MTC-IWF and the MTC Server; the MTC Server receives the control plane signaling from the control plane
  • the user plane data is parsed out.
  • Step 407 the MME or the SGSN forwards the user plane data to the P-GW or the GGSN.
  • the MME forwards the user plane data to the P-GW, or the SGSN forwards the user plane data to the P-GW or the GGSN; the MME or the SGSN and the P-GW generally have no direct The interface, the MME or the SGSN may forward the user plane data to the P-GW through the S-GW, or the SGSN forwards the user plane data directly to the GGSN.
  • Step 408 The P-GW or the GGSN forwards the user plane data to the MTC Server, and the process ends.
  • Step 409 The MME or the SGSN forwards the control plane signaling to the MTC-IWF.
  • control plane signaling has no user plane data
  • the MME or the SGSN passes the indication of the control plane signaling or queries the home subscriber server (HSS, Home Subscriber Server) or the home location register (HLR, Home).
  • HSS Home Subscriber Server
  • HLR home location register
  • the registration information in the Location Register finds the corresponding MTC-IWF, and forwards the control plane signaling to the MTC-IWF.
  • Step 410 The MTC-IWF sends control plane signaling to the MTC Server, and the process ends.
  • the MTC-IWF finds the corresponding MTC Server through control plane signaling indication or by querying the registration information in the HSS or the HLR, and forwards the control plane signaling to the MTC.
  • FIG. 5 is a schematic flowchart of Embodiment 2 of the method for indicating a message type according to the present invention.
  • the scenario for transmitting MT signaling to the network side is shown in FIG. 5.
  • the method includes the following steps:
  • Step 501 The MTC Server sets a message type indication bit in the control plane signaling.
  • the control plane signaling refers to a signaling between the MTC Server and the P-GW or the GGSN or the MTC-IWF.
  • Step 502 the MTC Server determines whether the control plane signaling is sent through the MTC-IWF, if yes, step 503 is performed, otherwise, step 510 is performed;
  • the MTC Server may determine whether the control plane signaling is sent by the MTC-IWF according to the O&M indication; if yes, go to step 503; otherwise, go to step 510.
  • Step 503 The MTC-IWF receives the control plane signaling, and determines the control by using the message type indication bit. Whether the user plane data is included in the plane signaling, if yes, step 504 is performed, otherwise, step 509 is performed.
  • Step 504 the MTC-IWF sends control plane signaling including user plane data and message type indication bits to the MME or the SGSN;
  • the MTC-IWF parses the user plane data, and then encapsulates the user plane data and the message type indication bit into the new control plane signaling;
  • the control plane signaling refers to the MTC-IWF and the MME or the SGSN.
  • Control plane signaling; the MTC-IWF queries the corresponding MME or SGSN according to the control plane signaling indication, or the subscription data in the HSS or the HLR, and sends control plane signaling to the MME or the SGSN.
  • Step 505 The MME or the SGSN determines whether the user plane data is included in the control plane signaling. If yes, go to step 506, otherwise go to step 508.
  • Step 506 The MME or the SGSN parses the user plane data from the control plane signaling, and encapsulates the data in the NAS signaling. After adding the message type bit in the NAS signaling, the NAS signaling is sent to the user equipment.
  • Step 507 The user equipment determines, according to the message type bit, that the control plane signaling includes the user plane data, the user equipment parses the user plane data from the control plane signaling, and the process ends; where the user equipment is configured to control the control plane according to the protocol.
  • the user plane data is parsed out.
  • Step 508 The MME or the SGSN forwards the control plane signaling to the user equipment through the NAS signaling, and the process ends.
  • Step 509 The MTC-IWF forwards the control plane signaling to the MME or the SGSN, and performs step 508.
  • the control plane signaling is control plane signaling for adding a message type indication bit.
  • Step 511 The P-GW or the GGSN that receives the control plane signaling determines whether the control plane signaling includes the user plane data by using the message type bit. If yes, go to step 512. Otherwise, go to step 513.
  • Step 512 The P-GW or the GGSN sends the control plane signaling including the user plane data and the message type indication bit to the MME or the SGSN, and performs step 505.
  • the GW-GW may forward the signaling to the MME or the SGSN through the S-GW, or the GGSN forwards the signaling directly to the SGSN.
  • Step 513 The P-GW or the GGSN forwards the control plane signaling to the MME or the SGSN, and performs step 508.
  • FIG. 6 is a schematic structural diagram of an instruction type system for implementing a message type according to the present invention.
  • the system includes: a user equipment 61, a network node 62, MTC Server 63; where
  • User equipment 61 and/or network node 62 and/or MTC Server 63 for setting a message type identifier in the transmitted control plane signaling
  • the network node 62 is further configured to: determine, according to the message type identifier, whether the control plane signaling includes user plane data, and when determining that the control plane signaling includes the user plane data, send the user plane data to the user equipment by using control plane signaling. , or other network nodes, or MTC Server 63;
  • the user equipment 61 or the MTC Server 63 is further configured to determine whether the control plane signaling includes user plane data, and when the control plane signaling includes user plane data, the user plane data is parsed therefrom.
  • the network node 62 is further configured to: when determining that the control plane signaling does not include the user plane data, forward the control plane signaling that does not include the user plane data to the corresponding user equipment 61, or other network node, or the MTC Server 63. .
  • the control plane signaling is control plane signaling including user plane data or conventional control plane signaling.
  • the user equipment is a UE, an ME, and an MS; and the network node is an eNB, an MME, an SGSN, a P-GW, a GGSN, and an MTC-IWF.
  • the control plane signaling is a non-access stratum (NAS) signaling sent by the user equipment to the MME or the SGSN, or NAS signaling sent by the MME or the SGSN to the user equipment, or a P-GW or Control plane signaling sent to the MME or SGSN by the GGSN or MTC-IWF, or control plane signaling sent by the MTC-IWF to the MME or SGSN or MTC Server, or sent by the P-GW or GGSN to the MME or SGSN or MTC Control plane signaling of the server, or control plane signaling sent by the MTC Server to the MTC-IWF or P-GW or GGSN.
  • NAS non-access stratum
  • the message type identifier is a message type indication bit.
  • the network node 62 that receives the control plane signaling determines whether the user plane data is included in the control plane signaling according to the message type identifier: when the message type indication bit is 1, it indicates that the control plane signaling includes user plane data. If 0, it means that the control plane signaling does not include user plane data; or, when the message type indication bit is 0, the control plane signaling includes user plane data, and when it is 1, it indicates that the control plane signaling does not include the user. Or the message type identifier exists in the sent control plane signaling, indicating that the control plane signaling includes user plane data, and the message type identifier does not exist in the sent control plane signaling, indicating that the control plane signaling does not exist. Contains user plane data.
  • the network node 62 sends the user plane data to the user equipment 61 or other network node or the MTC server 63 through control plane signaling: the network node parses the user plane data from the control plane signaling including the user plane data, and The user plane data and the message type identifier are encapsulated in the control plane signaling, and the control plane signaling is sent to the user equipment, or other network node, or the MTC Server.
  • the MTC server 63 determines whether the control plane signaling includes the user plane data.
  • the control plane signaling includes the user plane data
  • the user plane data is parsed out from the following: when the control plane signaling is the MO signaling, the user The device or the network node forwards the control plane signaling including the user plane data to the corresponding network node, and the corresponding network node forwards the received control plane signaling to the MTC Server, and the MTC Server determines the control plane according to the message type identifier therein. Whether the user plane data is included in the signaling, and when the control plane signaling includes the user plane data, the user plane data is parsed from the received control plane signaling.
  • the user equipment 61 determines whether the control plane signaling includes user plane data, when the control plane letter When the user plane data is included in the command, the user plane data is parsed from: when the control plane signaling is MT signaling, the MTC Server or the network node sends control plane signaling including user plane data to other network nodes, and the other The network node sends the control plane data to the user equipment, and the user equipment determines, according to the message type identifier therein, whether the control plane signaling includes the user plane data. When the control plane signaling includes the user plane data, the control plane signaling is used. Parse the user plane data.

Abstract

本发明公开一种消息类型的指示方法,包括:在发送的控制面信令中设置消息类型标识;接收到控制面信令的网络节点根据消息类型标识,判断控制面信令中是否包含用户面数据,确定控制面信令中包含用户面数据时,将用户面数据通过控制面信令发送给用户设备、或其他网络节点、或机器类型通信服务器(MTC Server);用户设备或MTC Server判断控制面信令中是否包含用户面数据,当控制面信令中包含用户面数据时,从中解析出用户面数据;本发明还提供一种消息类型的指示系统及装置。根据本发明的技术方案,能够解决控制面信令中包含用户面数据时,用户面数据丟失的问题。

Description

一种消息类型的指示方法、 系统及装置 技术领域
本发明涉及移动通信技术, 尤其涉及一种消息类型的指示方法、 系统 及装置。 背景技术
机器对机器(M2M, Machine to Machine )是指机器之间建立连接的所 有技术和手段。 M2M理念在上个世纪九十年代就出现了,但是只停留在理 论阶段, 2000年以后, 随着移动通信技术的发展, 以移动通信技术实现机 器设备的联网成为可能。 2002 年左右 M2M 业务就在市场上出现, 并在随 后的几年迅速发展, 成为了众多通信设备商和电信运营商的关注焦点。 目 前全球的机器数量比人的数量要多很多, 因此可以预见到 M2M技术的良 好的市场前景。
对 M2M通信应用场景的研究表明, 在移动网络上提供 M2M通信具有 潜在的市场前景,但 M2M通信对系统提出了很多新的要求, 为了增强移动 网络在这方面的竟争力, 有必要对现有的移动网络进行优化, 来更有效的 支持 M2M通信。
现有的移动通信网络主要针对人与人的通信进行设计, 而对机器与机 器,人与机器的通信则优化不足。此外,运营商如何能够以低成本提供 M2M 通信服务, 也是 M2M通信部署成功的关键。
基于以上情况,有必要研究移动网络支持 M2M通信的解决方案, 解决 方案要最大限度重用现有网络,降低大量 M2M通信对网络造成的影响以及 运营维护的复杂度。 目前电信市场竟争日趋激烈, 资费不断下降, 运营商 利润空间不断减小, 以人为基础的通信市场正在趋于饱和, M2M通信对运 营商来说是全新的发展机遇。
为了有效地利用移动网络资源, 第三代合作伙伴计划 (3GPP , 3rd Generation Partnership Project )提出了机器类型通信 ( MTC, Machine Type Communication ) , 即机器^机器( Machine to Machine )、机器 ^人 ( Machine to Man )进行通信的业务,其业务范围远远超出了以往人对人 ( H2H, Human to Human )之间的通信, MTC在接入控制、 计费、 安全性、 QoS、 业务模 式等方面与现在的 H2H通信模式有很大的区别。
图 1是现有技术中 3GPP演进分组系统( EPS, Evolved Packet System ) 的架构示意图, 如图 1 所示, EPS 包括无线接入网和核心网, 无线接入网 可以是陆地无线接入网 (UTRAN , Universal Terrestrial Radio Access Network ), 演进的 UTRAN ( E-UTRAN, Evolved UTRAN ), GSM或 EDGE 无线接入网络 ( GERAN, GSM或 EDGE Radio Access Network ), 在演进分 组核心网 (EPC, Evolved Packet Core ) 中, 核心网可以是移动管理实体 ( MME, Mobility Management Entity )、服务网关( S-GW, Serving Gateway )、 分组数据网管 (P-GW, Packet Data Network Gateway )等网元, 在 GPRS 核心网中核心网可以是服务 GPRS支持节点( SGSN, Serving GPRS Support Node )等网元;在 E-UTRAN中,核心网可以是演进的节点 B ( eNB, evolved Node B )。
短数据 ( Small Data )是 MTC 的特性( Feature )之一, 该 Feature所关 注的问题是: 对于部分 MTC设备而言, 其传输的数据量很小, 但是仍然需 要完整的信令流程, 传输的数据与所涉及到的信令不对称, 造成了网络资 源的浪费; 而且, 由于 MTC设备的数量往往很大, 集中的接入必然带来大 量的信令, 很容易造成网络拥塞, 所以, 需要采用更加高效的途径来进行 Small Data的传输。
Small Data包括移动主叫( MO, Mobile Originated )业务和移动被叫( MT, Mobile Terminating ) 业务, 即包括 MTC设备发送信息或接收信息。
为了实现 Small Data的有效传输, 已提出的方案包括: 通过短信发送 Small Data, 或通过控制面信令承载 Small Data。 图 2是现有技术中 3GPP 中的 MTC的架构示意图,如图 2所示,对于通过控制面信令承载 Small Data 的方式, 相关的控制面信令发送到网络节点, 网络节点将控制面信令中的 Small Data解析出来, 然后发送到相应的用户设备或其他网络节点或 MTC 服务器(MTC Server )。
在对现有技术的研究和实践过程中发现 Small Data的有效传输中存在 以下问题: 如果负责处理控制面信令的网络节点接收到的控制面信令中, 包含用户面数据, 所述网络节点可能无法区分常规的控制面信令和包含用 户面数据的控制面信令, 从而错误的处理包含用户面数据的控制面信令, 导致用户面数据的丟失。 发明内容
有鉴于此, 本发明的主要目的在于提供一种消息类型的指示方法、 系 统及装置, 用于解决控制面信令中包含用户面数据时, 用户面数据丟失的 问题。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供一种消息类型的指示方法, 在发送的控制面信令中设置消 息类型标识; 该方法还包括:
接收到控制面信令的网络节点根据消息类型标识, 判断控制面信令中 是否包含用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数 据通过控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server; 用户设备或 MTC Server判断控制面信令中是否包含用户面数据, 当控 制面信令中包含用户面数据时, 从中解析出用户面数据。
上述方法中, 该方法还包括: 确定控制面信令中不包含用户面数据时, 网络节点将不包含用户面数 据的控制面信令转发给相应的用户设备、或其他网络节点、或 MTC Server。
上述方法中, 所述在发送的控制面信令中设置消息类型标识为: 用户设备和 /或网络节点和 /或 MTC Server在发送的控制面信令中增加 消息类型标识; 其中, 所述控制面信令是包含用户面数据的控制面信令或 是常规的控制面信令。
上述方法中,
所述用户设备为 UE、 移动设备 ( ME )、 移动站( MS );
所述网络节点为 eNB、 MME、 SGSN, P-GW, 网关 GPRS 支持节点 ( GGSN )、 MTC互联功能实体(MTC-IWF )。
上述方法中, 所述控制面信令是用户设备发送到 MME或 SGSN的非 接入层(NAS )信令, 或是 MME或 SGSN发送到用户设备的 NAS信令, 或是 P-GW或 GGSN或 MTC-IWF等发送到 MME或 SGSN的控制面信令, 或是 MTC-IWF发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 P-GW或 GGSN发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 MTC Server发送到 MTC-IWF或 P-GW或 GGSN的控制面信令。
上述方法中, 所述消息类型标识为消息类型指示比特。
上述方法中, 所述接收到控制面信令的网络节点根据消息类型标识, 判断控制面信令中是否包含用户面数据为:
所述消息类型指示比特为 1 时, 表示控制面信令中包含用户面数据, 为 0时, 表示控制面信令中不包含用户面数据;
或, 消息类型指示比特为 0 时, 控制面信令中包含用户面数据, 为 1 时, 表示控制面信令中不包含用户面数据;
或, 在发送的控制面信令中消息类型标识存在, 表示控制面信令中包 含用户面数据, 在发送的控制面信令中消息类型标识不存在, 表示控制面 信令中不包含用户面数据。
上述方法中, 所述将用户面数据通过控制面信令发送给用户设备或其 他网络节点或 MTC Server为:
网络节点从包含用户面数据的控制面信令中解析出用户面数据, 并将 所述用户面数据和消息类型标识封装在控制面信令中, 将该控制面信令发 送给用户设备、 或其他网络节点、 或 MTC Server。
上述方法中,所述 MTC Server判断控制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据为:
所述控制面信令为 MO信令时, 用户设备或网络节点将包含用户面数 据的控制面信令转发给相应的网络节点, 相应的网络节点将收到的控制面 信令转发给 MTC Server, MTC Server根据其中的消息类型标识, 判断控制 面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从收 到的控制面信令中解析出用户面数据。
上述方法中, 所述用户设备判断控制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据为:
所述控制面信令是 MT信令时, MTC Server或网络节点将包含用户面 数据的控制面信令发送给其他网络节点, 其他网络节点将控制面数据发送 到用户设备, 用户设备根据其中的消息类型标识, 判断控制面信令中是否 包含用户面数据, 当控制面信令中包含用户面数据时, 从控制面信令中解 析出用户面数据。
本发明还提供一种消息类型的指示系统, 包括: 用户设备、 网络节点、 MTC Server; 其中,
用户设备和 /或网络节点和 /或 MTC Server,用于在发送的控制面信令中 设置消息类型标识;
网络节点, 还用于根据消息类型标识, 判断控制面信令中是否包含用 户面数据, 确定控制面信令中包含用户面数据时, 将用户面数据通过控制 面信令发送给用户设备、 或其他网络节点、 或 MTC Server;
用户设备或 MTC Server, 还用于判断控制面信令中是否包含用户面数 据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
上述系统中, 所述网络节点还用于, 确定控制面信令中不包含用户面 数据时, 将不包含用户面数据的控制面信令转发给相应的用户设备、 或其 他网络节点、 或 MTC Server。
本发明还提供一种用户设备, 该用户设备用于在发送的控制面信令中 设置消息类型标识, 还用于接收网络节点发送的控制面信令, 判断控制面 信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从中解 析出用户面数据。
本发明还提供一种网络节点, 该网络节点用于在发送的控制面信令中 设置消息类型标识; 还用于根据消息类型标识, 判断控制面信令中是否包 含用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数据通过 控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server。
上述网络节点还用于, 确定控制面信令中不包含用户面数据时, 将不 包含用户面数据的控制面信令转发给相应的用户设备、 或其他网络节点、 或 MTC Server。
本发明还提供一种 MTC服务器, 该 MTC服务器, 用于在发送的控制 面信令中设置消息类型标识;
还用于接收网络节点发送的控制面信令, 判断控制面信令中是否包含 用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
本发明提供的消息类型的指示方法、 系统及装置, 在发送的控制面信 令中设置消息类型标识, 判断控制面信令中是否包含用户面数据, 接收到 控制面信令的网络节点根据消息类型标识, 确定控制面信令中包含用户面 数据时, 将用户面数据通过控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server;用户设备或 MTC Server判断控制面信令中是否包含用户面 数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据, 用于 解决控制面信令中包含用户面数据时, 用户面数据丟失的问题, 实现通过 控制面信令承载的用户面数据的正确发送。 附图说明
图 1是现有技术中 3GPP EPS的架构示意图;
图 2是现有技术中 3GPP中的 MTC的架构示意图;
图 3是本发明实现消息类型的指示方法的流程示意图;
图 4是本发明实现消息类型的指示方法的实施例一的流程示意图; 图 5是本发明实现消息类型的指示方法的实施例二的流程示意图; 图 6是本发明实现消息类型的指示系统的结构示意图。 具体实施方式
本发明的基本思想是: 在发送的控制面信令中设置消息类型标识; 接 收到控制面信令的网络节点根据消息类型标识, 判断控制面信令中是否包 含用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数据通过 控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server; 用户设备 或 MTC Server判断控制面信令中是否包含用户面数据, 当控制面信令中包 含用户面数据时, 从中解析出用户面数据。
下面通过附图及具体实施例对本发明再做进一步的详细说明。
本发明提供一种消息类型的指示方法, 图 3是本发明实现消息类型的 指示方法的流程示意图, 如图 3所示, 该方法包括以下步驟:
步驟 301 , 在发送的控制面信令中设置消息类型标识;
具体的, 用户设备和 /或网络节点和 /或 MTC Server在发送的控制面信 令中增加消息类型标识;
所述控制面信令是包含用户面数据的控制面信令或是常规的控制面信 令; 所述用户面数据为 MTC特性中的 Small Data;
所述用户设备可以是 UE、 移动设备 ( ME, Mobile Equipment )、 移动 站(MS, Mobile Station ), 且用户设备配置了支持 MTC特性的功能; 所述 网络节点可以是 eNB、 MME、 SGSN, P-GW、 网关 GPRS支持节点( GGSN, Gateway GPRS Support Node )、 MTC 互联功能实体 (MTC-IWF , MTC Inter Working Function );
所述控制面信令是用户设备发送到 MME或 SGSN的非接入层(NAS, Non Access Stratum )信令, 或是 MME或 SGSN发送到用户设备的 NAS信 令, 或是 P-GW或 GGSN或 MTC-IWF等发送到 MME或 SGSN的控制面 信令,或是 MTC-IWF发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 P-GW或 GGSN发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 MTC Server发送到 MTC-IWF或 P-GW或 GGSN的控制面信令;其中, MME或 SGSN是通过 eNB发送 NAS信令给用户设备的;
本发明中, 在发送的控制面信令中增加的消息类型标识可以是消息类 型指示比特, 消息类型指示比特为 1 时, 表示控制面信令中包含用户面数 据, 消息类型指示比特为 0时, 表示控制面信令中不包含用户面数据, 或, 消息类型指示比特为 0 时, 控制面信令中包含用户面数据, 消息类型指示 比特为 1 时, 表示控制面信令中不包含用户面数据; 或, 仅在发送的包含 用户面数据的控制面信令中增加消息类型标识, 即在发送的控制面信令中 消息类型标识存在, 表示控制面信令中包含用户面数据, 在发送的控制面 信令中消息类型标识不存在, 表示控制面信令中不包含用户面数据。
步驟 302,接收到控制面信令的网络节点根据消息类型标识, 判断控制 面信令中是否包含用户面数据, 如果是, 执行步驟 303 , 否则, 执行步驟 304。
步驟 303 ,网络节点将用户面数据通过控制面信令发送给用户设备或其 他网络节点或 MTC Server,用户设备或 MTC Server判断控制面信令中是否 包含用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面 数据;
具体的, 网络节点从包含用户面数据的控制面信令中解析出用户面数 据, 并将所述用户面数据和消息类型标识封装在控制面信令中, 将该控制 面信令发送给用户设备或其他网络节点或 MTC Server;
如果网络节点是靠近用户设备或 MTC Server的网络节点, 则用户面数 据不需要再经过其他网络节点进行转发, 如果网络节点不是靠近用户设备 或 MTC Server的网络节点,用户面数据还需要经过其他网络节点进行转发, 收到控制面信令的其他网络节点的操作同步驟 302和步驟 303;
最终, 控制面信令会到达用户设备或 MTC Server, 用户设备或 MTC Server收到控制面信令后,根据其中的消息类型标识,判断控制面信令中是 否包含用户面数据, 当控制面信令中包含用户面数据时, 用户设备或 MTC Server对控制面信令进行解析, 得到用户面数据;
这里, 如果所述控制面信令是 MO信令, 用户设备或网络节点 MME 或 SGSN可以不从包含用户面数据的控制面信令中解析出用户面数据, 而 是将包含用户面数据的控制面信令转发给相应的网络节点, 如 P-GW 或 GGSN或 MTC IWF等, P-GW或 GGSN或 MTC IWF将收到的控制面信令 转发给 MTC Server, MTC Server判断控制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从收到的控制面信令中解析出用户面 数据;
如果所述控制面信令是 MT信令, MTC Server或网络节点 MTC-IWF 或 P-GW或 GGSN可以不从包含用户面数据的控制面信令中解析出用户面 数据, 而是将包含用户面数据的控制面信令发送给其他网络节点 MME或 SGSN, MME或 SGSN将控制面数据发送到用户设备, 用户设备判断控制 面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从控 制面信令中解析出用户面数据。
步驟 304,网络节点将不包含用户面数据的控制面信令转发给相应的用 户设备或其他网络节点或 MTC Server。
实施例一
图 4是本发明实现消息类型的指示方法的实施例一的流程示意图, 针 对用户设备发起 MO信令的场景, 如图 4所示, 该方法包括以下步驟: 步驟 401 , 用户设备向 MME或 SGSN发送 NAS信令, 并在 NAS信令 中设置消息类型指示比特;
具体的, 用户设备向 MME或 SGSN发送 NAS信令, 并在 NAS信令 中增加消息类型指示比特; 所述 NAS信令可以是以下任意一种信令过程中 用户设备发送的 NAS信令: 连接请求( Attach Request )、服务请求 ( Service Request )、 TAU/RAU Request等; 所述 NAS信令中包含用户面数据 Small Data;所述 Small Data的大小一般由用户签约数据或运营商操作或维护实体 ( O&M, Operation and Maintenance )或 MTC Server给出;
所述消息类型指示比特为一个比特, 该比特为 1或 0或存在表明控制 面信令中包含用户面数据, 该比特为 0或 1或不存在表明控制面信令中不 包含用户面数据, 可根据该比特的取值或是否存在判断控制面信令中是否 包含用户面数据。
步驟 402,接收到 NAS信令的 MME或 SGSN根据消息类型指示比特, 判断 NAS信令中是否包含用户面数据, 如果是, 执行步驟 403 , 否则, 执 行步驟 409;
这里, 所述 MME或 SGSN接收到 NAS信令后, 首先检查消息类型指 示比特, 判断 NAS信令中是否包含用户面数据。
步驟 403 , MME或 SGSN将 NAS信令中的用户面数据解析出来; 具体的, 所述 MME或 SGSN根据协议约定, 将 NAS信令中的用户面 数据解析出来。
步驟 404, MME或 SGSN判断是否继续通过控制面发送用户面数据, 如果是, 执行步驟 405, 否则, 执行步驟 407;
具体的,所述 MME或 SGSN自身判断或根据 0&M指示,判断是否继 续通过控制面或用户面发送所述用户面数据,如果是,执行步驟 405,否贝' J , 执行步驟 407。
步驟 405 , MME或 SGSN将用户面数据或用户面数据和消息类型指示 比特通过控制面信令发送给 MTC-IWF;
具体的, 所述 MME或 SGSN将所述用户面数据或用户面数据和消息 类型指示比特封装在控制面信令中, 将该控制面信令发送给 MTC-IWF; 所 述控制面信令为 MME或 SGSN与 MTC-IWF之间的控制面信令。
步驟 406, MTC-IWF根据消息类型指示比特确定控制面信令中包含用 户面数据, 并从中解析出用户面数据, 将用户面数据发送给 MTC Server, 流程结束;
具体的, 所述 MTC-IWF属于控制面网络节点, MTC-IWF根据消息类 型指示比特确定控制面信令中包含用户面数据, 并从中解析出用户面数据, 将用户面数据或用户面数据和消息类型指示比特重新封装在控制面信令中 发送给 MTC Server,所述控制面信令为 MTC-IWF与 MTC Server之间的控 制面信令; 所述 MTC Server从收到的控制面信令中解析出用户面数据。
步驟 407, MME或 SGSN将用户面数据转发到 P-GW或 GGSN;
具体的, MME将用户面数据转发给 P-GW, 或 SGSN将用户面数据转 发给 P-GW或 GGSN; 所述 MME或 SGSN与 P-GW之间一般没有直接的 接口, MME或 SGSN可通过 S-GW将用户面数据转发给 P-GW, 或 SGSN 将用户面数据直接转发给 GGSN。
步驟 408, P-GW或 GGSN将用户面数据转发给 MTC Server, 流程结 束。
步驟 409 , MME或 SGSN将控制面信令转发给 MTC-IWF;
具体的, 所述控制面信令中没有用户面数据, 所述 MME或 SGSN通 过所述控制面信令的指示或通过查询归属用户服务器 (HSS , Home Subscriber Server )或归属位置寄存器 ( HLR, Home Location Register ) 中 的注册信息, 查找到相应的 MTC-IWF , 将所述控制面信令转发给该 MTC-IWF。
步驟 410, MTC-IWF将控制面信令发送给 MTC Server, 流程结束。 这里,所述 MTC-IWF通过控制面信令指示或通过查询 HSS或 HLR中 的注册信息, 查找到相应 MTC Server, 并将所述控制面信令转发到 MTC
Server。
实施例二
图 5是本发明实现消息类型的指示方法的实施例二的流程示意图, 针 对网络侧发送 MT信令的场景, 图 5所示, 该方法包括以下步驟:
步驟 501 , MTC Server在控制面信令中设置消息类型指示比特; 其中, 所述控制面信令是指 MTC Server与 P-GW或 GGSN或 MTC-IWF之间的信 令。
步驟 502, MTC Server判断控制面信令是否通过 MTC-IWF发送,如果 是, 执行步驟 503 , 否则, 执行步驟 510;
具体的, MTC Server可以自身判断或根据 0&M指示选择控制面信令 是否通过 MTC-IWF发送; 如果是, 执行步驟 503 , 否则, 执行步驟 510。
步驟 503 , MTC-IWF接收控制面信令, 通过消息类型指示比特判断控 制面信令中是否包含用户面数据, 如果是, 执行步驟 504, 否则, 执行步驟 509。
步驟 504, MTC-IWF发送包含用户面数据和消息类型指示比特的控制 面信令给 MME或 SGSN;
具体的, 所述 MTC-IWF解析出用户面数据, 然后将用户面数据和消息 类型指示比特封装到新的控制面信令中; 所述控制面信令是指 MTC-IWF 与 MME或 SGSN之间的控制面信令;所述 MTC-IWF根据控制面信令指示、 或 HSS或 HLR中签约数据, 查询相应的 MME或 SGSN, 将控制面信令发 送给 MME或 SGSN。
步驟 505 , MME或 SGSN判断控制面信令中是否包含用户面数据, 如 果是, 转向步驟 506, 否则转向步驟 508。
步驟 506, MME或 SGSN从控制面信令中解析出用户面数据, 并封装 在 NAS信令中, 在 NAS信令中增加消息类型比特后, 将 NAS信令发送给 用户设备。
步驟 507,用户设备根据消息类型比特确定控制面信令中包含用户面数 据, 用户设备从控制面信令解析出用户面数据, 流程结束; 其中, 所述用 户设备根据协议规定从控制面信令中解析出用户面数据。
步驟 508, MME或 SGSN将控制面信令通过 NAS信令转发给用户设 备, 流程结束。
步驟 509, MTC-IWF转发控制面信令给 MME或 SGSN,执行步驟 508。 步驟 510, MTC Server发送控制面信令给 P-GW或 GGSN; 其中, 所 述控制面信令为增加消息类型指示比特的控制面信令。
步驟 511 , 接收控制面信令的 P-GW或 GGSN通过消息类型比特, 判 断控制面信令中是否包含用户面数据, 如果是, 执行步驟 512, 否则, 执行 步驟 513。 步驟 512, P-GW或 GGSN发送包含用户面数据和消息类型指示比特的 控制面信令给 MME或 SGSN, 执行步驟 505; 这里, 所述 P-GW与 MME 或 SGSN之间一般没有直接的接口,Ρ-GW可通过 S-GW将信令转发给 MME 或 SGSN, 或 GGSN将信令直接转发给 SGSN。
步驟 513 , P-GW或 GGSN转发控制面信令给 MME或 SGSN, 执行步 驟 508。
为实现上述方法, 本发明还提供一种消息类型的指示系统, 图 6是本 发明实现消息类型的指示系统的结构示意图, 如图 6所示, 该系统包括: 用户设备 61、 网络节点 62、 MTC Server 63; 其中,
用户设备 61和 /或网络节点 62和 /或 MTC Server 63 , 用于在发送的控 制面信令中设置消息类型标识;
网络节点 62, 还用于根据消息类型标识, 判断控制面信令中是否包含 用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数据通过控 制面信令发送给用户设备 61、 或其他网络节点、 或 MTC Server 63;
用户设备 61或 MTC Server 63 , 还用于判断控制面信令中是否包含用 户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
所述网络节点 62还用于, 确定控制面信令中不包含用户面数据时, 将 不包含用户面数据的控制面信令转发给相应的用户设备 61、 或其他网络节 点、 或 MTC Server 63。
所述控制面信令是包含用户面数据的控制面信令或是常规的控制面信 令。
所述用户设备为 UE、 ME、 MS; 所述网络节点为 eNB、 MME、 SGSN, P-GW, GGSN, MTC-IWF。
所述控制面信令是用户设备发送到 MME或 SGSN的非接入层( NAS ) 信令, 或是 MME或 SGSN发送到用户设备的 NAS信令, 或是 P-GW或 GGSN或 MTC-IWF等发送到 MME或 SGSN的控制面信令,或是 MTC-IWF 发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 P-GW或 GGSN 发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 MTC Server发 送到 MTC-IWF或 P-GW或 GGSN的控制面信令。
所述消息类型标识为消息类型指示比特。
所述接收到控制面信令的网络节点 62根据消息类型标识, 判断控制面 信令中是否包含用户面数据为: 所述消息类型指示比特为 1 时, 表示控制 面信令中包含用户面数据, 为 0时, 表示控制面信令中不包含用户面数据; 或, 消息类型指示比特为 0时, 控制面信令中包含用户面数据, 为 1 时, 表示控制面信令中不包含用户面数据; 或, 在发送的控制面信令中消息类 型标识存在, 表示控制面信令中包含用户面数据, 在发送的控制面信令中 消息类型标识不存在, 表示控制面信令中不包含用户面数据。
所述网络节点 62将用户面数据通过控制面信令发送给用户设备 61或 其他网络节点或 MTC Server 63为:网络节点从包含用户面数据的控制面信 令中解析出用户面数据, 并将所述用户面数据和消息类型标识封装在控制 面信令中, 将该控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server。
所述 MTC Server 63判断控制面信令中是否包含用户面数据,当控制面 信令中包含用户面数据时, 从中解析出用户面数据为: 所述控制面信令为 MO信令时,用户设备或网络节点将包含用户面数据的控制面信令转发给相 应的网络节点, 相应的网络节点将收到的控制面信令转发给 MTC Server, MTC Server根据其中的消息类型标识, 判断控制面信令中是否包含用户面 数据, 当控制面信令中包含用户面数据时, 从收到的控制面信令中解析出 用户面数据。
所述用户设备 61判断控制面信令中是否包含用户面数据, 当控制面信 令中包含用户面数据时,从中解析出用户面数据为: 所述控制面信令是 MT 信令时, MTC Server或网络节点将包含用户面数据的控制面信令发送给其 他网络节点, 其他网络节点将控制面数据发送到用户设备, 用户设备根据 其中的消息类型标识, 判断控制面信令中是否包含用户面数据, 当控制面 信令中包含用户面数据时, 从控制面信令中解析出用户面数据。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围, 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种消息类型的指示方法, 其特征在于, 在发送的控制面信令中设 置消息类型标识; 该方法还包括:
接收到控制面信令的网络节点根据消息类型标识, 判断控制面信令中 是否包含用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数 据通过控制面信令发送给用户设备、 或其他网络节点、 或机器类型通信服 务器(MTC Server ) ;
用户设备或 MTC Server判断控制面信令中是否包含用户面数据, 当控 制面信令中包含用户面数据时, 从中解析出用户面数据。
2、 根据权利要求 1所述的方法, 其特征在于, 该方法还包括: 确定控制面信令中不包含用户面数据时, 网络节点将不包含用户面数 据的控制面信令转发给相应的用户设备、或其他网络节点、或 MTC Server。
3、 根据权利要求 1所述的方法, 其特征在于, 所述在发送的控制面信 令中设置消息类型标识为:
用户设备和 /或网络节点和 /或 MTC Server在发送的控制面信令中增加 消息类型标识; 其中, 所述控制面信令是包含用户面数据的控制面信令、 或是常规的控制面信令。
4、 根据权利要求 1至 3任一项所述的方法, 其特征在于,
所述用户设备为 UE、 移动设备(ME ) 、 移动站(MS ) ;
所述网络节点为演进的节点 B ( eNB ) 、 移动管理实体(MME ) 、 服 务 GPRS支持节点 (SGSN ) 、 分组数据网管 (P-GW ) 、 网关 GPRS支持 节点 (GGSN ) 、 MTC互联功能实体 ( MTC-IWF ) 。
5、 根据权利要求 1至 3任一项所述的方法, 其特征在于, 所述控制面 信令是用户设备发送到 MME或 SGSN的非接入层( NAS )信令,或是 MME 或 SGSN发送到用户设备的 NAS信令, 或是 P-GW或 GGSN或 MTC-IWF 等发送到 MME或 SGSN的控制面信令, 或是 MTC-IWF发送到 MME或 SGSN或 MTC Server的控制面信令, 或是 P-GW或 GGSN发送到 MME或 SGSN或 MTC Server的控制面信令,或是 MTC Server发送到 MTC-IWF或 P-GW或 GGSN的控制面信令。
6、 根据权利要求 1至 3任一项所述的方法, 其特征在于, 所述消息类 型标识为消息类型指示比特。
7、 根据权利要求 6所述的方法, 其特征在于, 所述接收到控制面信令 的网络节点根据消息类型标识, 判断控制面信令中是否包含用户面数据为: 所述消息类型指示比特为 1 时, 表示控制面信令中包含用户面数据, 为 0时, 表示控制面信令中不包含用户面数据;
或, 消息类型指示比特为 0 时, 控制面信令中包含用户面数据, 为 1 时, 表示控制面信令中不包含用户面数据;
或, 在发送的控制面信令中消息类型标识存在, 表示控制面信令中包 含用户面数据, 在发送的控制面信令中消息类型标识不存在, 表示控制面 信令中不包含用户面数据。
8、 根据权利要求 1所述的方法, 其特征在于, 所述将用户面数据通过 控制面信令发送给用户设备或其他网络节点或 MTC Server为:
网络节点从包含用户面数据的控制面信令中解析出用户面数据, 并将 所述用户面数据和消息类型标识封装在控制面信令中, 将该控制面信令发 送给用户设备、 或其他网络节点、 或 MTC Server。
9、 根据权利要求 1所述的方法, 其特征在于, 所述 MTC Server判断 控制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据为:
所述控制面信令为 MO信令时, 用户设备或网络节点将包含用户面数 据的控制面信令转发给相应的网络节点, 相应的网络节点将收到的控制面 信令转发给 MTC Server, MTC Server根据其中的消息类型标识, 判断控制 面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从收 到的控制面信令中解析出用户面数据。
10、 根据权利要求 1 所述的方法, 其特征在于, 所述用户设备判断控 制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从 中解析出用户面数据为:
所述控制面信令是 MT信令时, MTC Server或网络节点将包含用户面 数据的控制面信令发送给其他网络节点, 其他网络节点将控制面数据发送 到用户设备, 用户设备根据其中的消息类型标识, 判断控制面信令中是否 包含用户面数据, 当控制面信令中包含用户面数据时, 从控制面信令中解 析出用户面数据。
11、 一种消息类型的指示系统, 其特征在于, 该系统包括: 用户设备、 网络节点、 MTC Server; 其中,
用户设备和 /或网络节点和 /或 MTC Server,用于在发送的控制面信令中 设置消息类型标识;
网络节点, 还用于根据消息类型标识, 判断控制面信令中是否包含用 户面数据, 确定控制面信令中包含用户面数据时, 将用户面数据通过控制 面信令发送给用户设备、 或其他网络节点、 或 MTC Server;
用户设备或 MTC Server, 还用于判断控制面信令中是否包含用户面数 据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
12、根据权利要求 11所述的系统,其特征在于, 所述网络节点还用于, 确定控制面信令中不包含用户面数据时, 将不包含用户面数据的控制面信 令转发给相应的用户设备、 或其他网络节点、 或 MTC Server。
13、 一种用户设备, 其特征在于, 该用户设备, 用于在发送的控制面 信令中设置消息类型标识, 还用于接收网络节点发送的控制面信令, 判断 控制面信令中是否包含用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
14、 一种网络节点, 其特征在于, 该网络节点, 用于在发送的控制面 信令中设置消息类型标识; 还用于根据消息类型标识, 判断控制面信令中 是否包含用户面数据, 确定控制面信令中包含用户面数据时, 将用户面数 据通过控制面信令发送给用户设备、 或其他网络节点、 或 MTC Server。
15、 根据权利要求 14所述的网络节点, 其特征在于, 该网络节点还用 于, 确定控制面信令中不包含用户面数据时, 将不包含用户面数据的控制 面信令转发给相应的用户设备、 或其他网络节点、 或 MTC Server。
16、 一种 MTC服务器, 其特征在于, 该 MTC服务器, 用于在发送的 控制面信令中设置消息类型标识;
还用于接收网络节点发送的控制面信令, 判断控制面信令中是否包含 用户面数据, 当控制面信令中包含用户面数据时, 从中解析出用户面数据。
PCT/CN2011/082474 2011-10-17 2011-11-18 一种消息类型的指示方法、系统及装置 WO2013056486A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP11861326.4A EP2608581B1 (en) 2011-10-17 2011-11-18 Method, system and apparatus for indicating type of messages
US13/636,335 US20140219183A1 (en) 2011-10-17 2011-11-18 Method, System and Apparatus for Indicating Message Type

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110314769.7 2011-10-17
CN201110314769.7A CN103052045B (zh) 2011-10-17 2011-10-17 一种消息类型的指示方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2013056486A1 true WO2013056486A1 (zh) 2013-04-25

Family

ID=48064518

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/082474 WO2013056486A1 (zh) 2011-10-17 2011-11-18 一种消息类型的指示方法、系统及装置

Country Status (4)

Country Link
US (1) US20140219183A1 (zh)
EP (1) EP2608581B1 (zh)
CN (1) CN103052045B (zh)
WO (1) WO2013056486A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104144434B (zh) * 2013-05-09 2018-10-09 华为技术有限公司 实现mtc监控的方法及装置
CN104349373B (zh) * 2013-08-07 2018-10-30 华为终端有限公司 终端监控事件配置方法、应用服务器以及归属位置设备
CN104823469B (zh) 2013-09-23 2019-01-18 华为技术有限公司 传输数据的方法和实体
CN107006070B (zh) 2015-07-06 2019-07-19 华为技术有限公司 增强多媒体广播组播业务eMBMS系统及其管理方法
US10805830B2 (en) * 2015-08-14 2020-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for regulating user data traffic in a wireless network
MX2018009875A (es) 2016-02-18 2018-09-07 Ericsson Telefon Ab L M Sistema, metodos y aparatos para la gestion de la tasa de datos para optimizacion de plano de control.
KR102168676B1 (ko) * 2016-03-23 2020-10-21 엘지전자 주식회사 무선 통신 시스템에서 트래킹 영역 업데이트 방법 및 이를 위한 장치
WO2017164696A2 (ko) * 2016-03-24 2017-09-28 엘지전자 주식회사 메시지 전송 방법 및 사용자기기
CN107579807B (zh) * 2016-06-30 2020-11-27 电信科学技术研究院 数据传输的方法及装置
CN106330398A (zh) * 2016-08-29 2017-01-11 中国联合网络通信集团有限公司 一种确定物联网业务的数据传输模式的方法及装置
CN108880738B (zh) * 2017-05-10 2020-08-21 电信科学技术研究院 一种信息处理方法及装置
CN113438695B (zh) * 2017-12-25 2022-06-21 大唐移动通信设备有限公司 一种会话建立的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1806401A (zh) * 2003-07-14 2006-07-19 三星电子株式会社 在无线分组数据通信系统中生成分组数据以支持多个服务的方法和设备
CN101112030A (zh) * 2005-07-26 2008-01-23 中兴通讯股份有限公司 基于码分多址集群系统中的集群信令封装及解封装方法
CN101115297A (zh) * 2006-09-08 2008-01-30 华为技术有限公司 一种前向信令信道消息传送方法及系统
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102195959A (zh) * 2010-03-11 2011-09-21 中兴通讯股份有限公司 Sip信令的xml数据的解析方法及装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3967115B2 (ja) * 2001-11-22 2007-08-29 株式会社エヌ・ティ・ティ・ドコモ 基地局、無線リソース制御装置、端末装置、通信システム及び通信方法
KR101364797B1 (ko) * 2007-10-02 2014-02-19 엘지전자 주식회사 상향링크 무선자원 할당 방법
EP2182328A1 (en) * 2008-10-28 2010-05-05 Koninklijke KPN N.V. Telecommunications network and method of transferring user data in signalling messages from a communication unit to a data processing centre
WO2010151186A1 (en) * 2009-06-24 2010-12-29 Telefonaktiebolaget L M Ericsson (Publ) Energy efficient base station entering sleep mode
WO2011051753A1 (en) * 2009-10-30 2011-05-05 Huawei Technologies Co. Ltd. Method and apparatus of communication of payload data
US8320292B2 (en) * 2009-11-18 2012-11-27 Motorola Mobility Llc Method to control a multimedia broadcast multicast service(MBMS) mode of a MBMS session in a communication system
EP2550817B1 (en) * 2010-03-23 2015-05-27 InterDigital Patent Holdings, Inc. Methods for communication for a machine type communication device and corresponding wireless transmit/receive unit
TWI477167B (zh) * 2010-08-05 2015-03-11 Htc Corp 處理信令擁塞之方法及其相關通訊裝置
WO2013052163A1 (en) * 2011-10-03 2013-04-11 Intel Corporation Device to device (d2d) communication mechanisms

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1806401A (zh) * 2003-07-14 2006-07-19 三星电子株式会社 在无线分组数据通信系统中生成分组数据以支持多个服务的方法和设备
CN101112030A (zh) * 2005-07-26 2008-01-23 中兴通讯股份有限公司 基于码分多址集群系统中的集群信令封装及解封装方法
CN101115297A (zh) * 2006-09-08 2008-01-30 华为技术有限公司 一种前向信令信道消息传送方法及系统
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102195959A (zh) * 2010-03-11 2011-09-21 中兴通讯股份有限公司 Sip信令的xml数据的解析方法及装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN103052045A (zh) 2013-04-17
EP2608581A1 (en) 2013-06-26
EP2608581B1 (en) 2018-07-25
CN103052045B (zh) 2019-03-12
US20140219183A1 (en) 2014-08-07
EP2608581A4 (en) 2015-03-18

Similar Documents

Publication Publication Date Title
WO2013056486A1 (zh) 一种消息类型的指示方法、系统及装置
EP3402234A1 (en) Method for updating ue configuration in wireless communication system and apparatus for same
JP5734220B2 (ja) マシン通信型デバイスのトリガーを処理するサービスネットワーク及び方法
US9215550B2 (en) Method and system for sending MTC device trigger information, and target user equipment
EP2768251B1 (en) Data transmission method, mobility management entity and mobile terminal
WO2013113186A1 (zh) 一种mtc用户设备触发信息的发送方法、系统和用户设备
US8743752B2 (en) Method and apparatus for status transition
WO2012151945A1 (zh) 一种维持大量连接的方法、用户设备及系统
US9204273B2 (en) Method and system for trigger information transmission and protocol conversion
WO2012151963A1 (zh) 一种触发信息中有效时间的处理方法和系统
WO2013131461A1 (zh) 一种用户设备接入融合控制网元的实现方法及装置
US20150215725A1 (en) Method, system, and equipment for sending trigger message
WO2014048173A1 (zh) 一种小数据发送方法、系统及用户设备
EP3059996B1 (en) Nas connection establishment method, system and radio access network node
WO2013063852A1 (zh) 设置触发信息有效时间方法、系统和用户设备
WO2015154380A1 (zh) 更新机器类型通信设备组激活信息的方法、装置及系统
WO2014071758A1 (zh) 信息的发送方法、mtc服务器、用户设备及mtc系统
WO2011032522A1 (zh) 一种实现本地接入的系统及方法
WO2014071798A1 (zh) 管理分流连接的方法、无线侧网元及移动性管理实体
CN103428732B (zh) 路由优化方法及系统、无线侧网元
WO2013102316A1 (zh) 响应触发信息的方法、系统和mtc用户设备
EP2827661B1 (en) System, apparatus, and method for triggering roaming mtc device
WO2013174201A1 (zh) 推翻低优先级和/或eab的方法、系统及相关装置
KR20220047316A (ko) 개선된 패킷 검출 규칙 프로비전에 대한 방법 및 장치

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 13636335

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2011861326

Country of ref document: EP

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

Ref document number: 11861326

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE