WO2015070441A1 - Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations - Google Patents

Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations Download PDF

Info

Publication number
WO2015070441A1
WO2015070441A1 PCT/CN2013/087249 CN2013087249W WO2015070441A1 WO 2015070441 A1 WO2015070441 A1 WO 2015070441A1 CN 2013087249 W CN2013087249 W CN 2013087249W WO 2015070441 A1 WO2015070441 A1 WO 2015070441A1
Authority
WO
WIPO (PCT)
Prior art keywords
local
entity
request information
information
service request
Prior art date
Application number
PCT/CN2013/087249
Other languages
English (en)
Chinese (zh)
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 PCT/CN2013/087249 priority Critical patent/WO2015070441A1/fr
Publication of WO2015070441A1 publication Critical patent/WO2015070441A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an M2M network and application, a general service entity, and an information recovery method.
  • Background art
  • Machine-to-Machine (M2M) communication is a networked application and service centered on machine intelligent interaction. By embedding wireless or wired communication modules and application processing logic inside the book machine, no manual is required. The data communication of interventions meets the information needs of users in monitoring, command and dispatch, data acquisition and measurement.
  • the overall goal of the oneM2M standards organization for machine communication is to create an open standard for the Service Capability Layer (SCL) of M2M communication to facilitate the establishment of a future network that integrates various devices and services, enabling M2M services to interoperate. Enables M2M applications to share basic services and implement them independently of the network.
  • SCL Service Capability Layer
  • the M2M network architecture defined by the oneM2M standard mainly includes an Application Entity (AE), a Common Service Entity (CSE), and an Underlying Network Service Entity (NSE).
  • AE Application Entity
  • CSE Common Service Entity
  • NSE Underlying Network Service Entity
  • the M2M AE and the M2M CSE communicate via the Mca Reference Point, and the CSE uses the Mcc reference point for communication; the CSE communicates with the NSE through the Men reference point.
  • the European Telecommunication Standardization Institute (ETSI) M2M standard uses a method of aggregating request information in a storage and forwarding mechanism, allowing a tolerable request processing delay time set according to AE or CSE (Tolerable Request Processing Delay Time). , TRPDT ) and request category (RCAT), store the request information in the local CSE until the CSE establishes a communication link that conforms to RCAT ( The storage time cannot exceed the time defined by the TRPDT), and the request information sent to the same target CSE can be aggregated and then sent.
  • AE Tolerable Request Processing Delay Time
  • CSE Tolerable Request Processing Delay Time
  • RCAT request category
  • the technical problem to be solved by the present invention is how to control the time at which the target CSE replies to the acknowledgment information.
  • the present invention provides a device-to-machine M2M network information recovery method, the M2M network includes a target general service entity and at least one application, and the method includes:
  • the target general service entity receives service request information, where the service request information includes a specific time;
  • the target general service entity sends confirmation information to the application within the specific time.
  • the target general service entity receives the service request information, including: the target general service entity receiving the first service request information from the application.
  • the M2M network further includes a local general service entity, where the target general service entity receives the service request information, including: the target general service entity receives the local a second service request information generated by the general service entity according to the first service request information received from the application;
  • the target general service entity sends confirmation information to the application within the specific time, including:
  • the target general service entity passes the local general service entity during the specific time Send confirmation information to the application.
  • the first service request information further includes a request type RCAT and a tolerable request processing delay time TRPDT, where the target general service is Receiving, by the local general service entity, the second service request information generated by the local general service entity according to the first service request information received by the application, where: if the communication link corresponding to the RCAT is established, Receiving, by the target general service entity, the second service request information that is sent by the local general service entity immediately; or
  • the target general service entity receives the delayed transmission of the local general service entity if the communication link corresponding to the RCAT is not established.
  • the second service request information where the local processing time is the time when the local general service entity establishes the communication link; if the local processing time of the local general service entity exceeds the TRPDT, the local general service entity Returning a failure message to the application.
  • the M2M network further includes a local general service entity, where the target general service entity receives the service request information, including: the target general service entity receives the local a second service request information that is aggregated by the general service entity according to the plurality of first service request information received from the application;
  • the target general service entity sends confirmation information to the application within the specific time, including:
  • the target general service entity After the target general service entity aggregates the respective acknowledgment information into the aggregation information, the aggregation information is sent to the local general service entity, and the local general service entity separates the aggregation information. Sending corresponding confirmation information to each of the applications, where the remaining time is determined by the local general service entity according to a specific time included in the plurality of the first service request information and a local processing time of the local general service entity, The aggregate information includes the respective confirmation information.
  • the first service request information further includes an RCAT and a TRPDT, where the target general service entity receives the local general service
  • the second service request information that is aggregated by the entity according to the multiple first service request information received by the application includes:
  • the local general service entity determines a delay time, and the local general service entity is in the case that the communication link corresponding to the RCAT is not established.
  • the plurality of the first service request information received from the application is aggregated in a delay time, and the target general service entity receives the aggregated second service request information from the local general service entity,
  • the local processing time is the time at which the local general service entity establishes the communication link.
  • the present invention provides an information recovery method for an M2M network, where the M2M network includes a target general service entity and at least one application, and the method includes:
  • the application sends first service request information, where the first service request information includes a specific time
  • the application receives confirmation information returned by the target general service entity according to a specific time within the specific time.
  • the application sends the first service request information, where the application sends the first service request information to the target general service entity;
  • the method includes: the application receiving the confirmation information from the target general service entity in the specific time.
  • the M2M network further includes a local general service entity, where the application sends the first service request information, including: the application to the The local general service entity sends the first service request information, so that the local general service entity sends the second service request information to the target general service entity according to the first service request information;
  • the method includes: receiving, by the application, the target general service entity from the local general service entity in the specific time The confirmation information returned.
  • the third aspect of the present invention provides a general service entity of an M2M network, including:
  • the receiving module is configured to receive service request information, where the service request information includes a specific time
  • the sending module is configured to communicate with the receiving module, and send the confirmation information to the application within the specific time.
  • the receiving module is further configured to receive the first service request information from the application.
  • the receiving module is further configured to receive second service request information generated by the local general service entity according to the first service request information received from the application;
  • the sending module is further configured to send the confirmation information to the application by the local universal service entity during the specific time.
  • the first service request information further includes a request type RCAT and a tolerable request processing delay time TRPDT, where the receiving module uses Receiving, by the local general service entity, the second service request information, if the communication link corresponding to the RCAT is established, the receiving module is further configured to receive, according to the local general service entity, Decoding, by the application, the second service request information generated by the first service request information; or
  • the sending module is further configured to: if the communication link corresponding to the RCAT is not established, if The local processing time of the local general service entity does not exceed the TRPDT, and the second service request information delayed by the local general service entity is received.
  • the receiving module is configured to receive, by the local common service entity, a second service request that is aggregated according to multiple first service request information received from the application Information
  • the receiving module is further configured to: after the aggregation information is aggregated into the aggregation information, send the aggregation information to the local general service entity, where the local general service entity performs the aggregation information After the separation, respectively sending corresponding confirmation information to each of the applications, where the remaining time is determined by the local general service entity according to a specific time included in the plurality of first service request information and local to the local general service entity The processing time is determined, and the aggregation information includes the respective confirmation information.
  • the first service request information further includes an RCAT and a TRPDT, where the communication link corresponding to the RCAT is not established. If the local processing time of the local general service entity does not exceed the TRPDT, the local general service entity determines a delay time, and the local general service entity receives the received time from the application within the delay time.
  • the first service request information is aggregated, and the receiving module is further configured to receive the aggregated second service request information from the local general service entity, where the local processing time is established by the local general service entity. The time of the communication link.
  • the present invention provides an application of an M2M network, including:
  • a sending module configured to send first service request information, where the first service request information includes a specific time
  • a receiving module configured to receive, during the specific time, the confirmation information returned by the general service entity according to a specific time.
  • the sending module is further configured to send the first service request information to the general service entity; the receiving module is further configured to use the specific time Receiving the confirmation information from the general service entity.
  • the M2M network further includes a local general service entity, where the sending module is further configured to send the first service request information to the general service entity, so that Transmitting, by the local general service entity, the second service request request information to the general service entity according to the first service request information;
  • the receiving module is further configured to receive, by the local general service entity, the confirmation information book returned by the general service entity during the specific time.
  • the present invention provides an M2M network, including: a target general service entity and at least one application;
  • the target general service entity adopts the general service entity of the M2M network described in any one of the above;
  • the application employs the application of the M2M network described in any of the above.
  • the method further includes:
  • a local general service entity configured to receive first service request information sent by the application; and send second service request information to the target general service entity.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • FIG. 1A is a flow chart showing a method for recovering information of a machine-to-machine M2M network according to Embodiment 1 of the present invention
  • FIG. 1B is a schematic diagram of an information recovery method of an M2M network applied to a oneM2M architecture according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for replying information of an M2M network according to a second embodiment of the present invention
  • FIG. 3 is a flowchart of a method for replying information of an M2M network according to Embodiment 3 of the present invention
  • FIG. 4 is a flowchart of an M2M network according to Embodiment 4 of the present invention
  • FIG. 5 is a structural block diagram of a general service entity of an M2M network according to Embodiment 5 of the present invention
  • FIG. 6 is a structural block diagram of an application of an M2M network according to Embodiment 6 of the present invention
  • FIG. 7 is a structural block diagram of an M2M network according to Embodiment 7 of the present invention.
  • FIG. 8 is a structural block diagram of a general service entity of an M2M network according to Embodiment 8 of the present invention
  • FIG. 9 is a structural block diagram of an application of an M2M network according to Embodiment 9 of the present invention.
  • the M2M network may include a general service entity and at least one application, where the general service entity may include a local general service entity and a target general service entity, and the information recovery method of the M2M network may include:
  • Step 110 The target general service entity receives service request information, where the service request information includes a specific time.
  • Step 120 The target general service entity sends the acknowledgement information to the application within the specific time. Book
  • FIG. 1B is a schematic diagram of an M2M network information recovery method applied to a oneM2M architecture according to Embodiment 1 of the present invention.
  • an M2M network architecture defined by the oneM2M standard includes an Application Dedicated Node and an application.
  • a node that can only include an Application Entity (AE) is called an application-specific node; as shown in Case 3 and Case 4 in FIG. 1B, the AE may be included and may include a general service entity (
  • the node of the Common Service Entity (CSE) is called an application service node; in addition, both the intermediate node and the infrastructure node can include AE or CSE.
  • CSE Common Service Entity
  • case 2 case 3
  • the application dedicated node 11 and the application service node 13 can communicate with the infrastructure node 17 through the intermediate node 15.
  • case 1 case 4
  • the application-specific node and the application service node can also communicate directly with the infrastructure node.
  • the application entity AE may include or provide at least one application, where the application may be an application, an application module, an application logic unit, or the like.
  • a generic business entity may be a module that has the functionality of a CSE, where the application and the generic business entity may be on the same node.
  • Another M2M network architecture can be adopted by the European Telecommunication Standardization Institute (ETSI) M2M standard. ETSI
  • the application of the M2M network may be a module with an AE function, and the local general service entity and the target general service entity may be modules with a Service Capability Layer (SCL) function, wherein the application and the general service entity may also be on the same node.
  • SCL Service Capability Layer
  • the application or SCL can set the Tolerable Request Processing Delay Time (TRPDT) and the request type (request cat says egory, RCAT).
  • the application may determine whether the general service entity receives the valid confirmation information by using the specific time included in the first service request information, for example, the application judgment starts from the issuance of the first service request information, within a specific time. Whether the confirmation message returned by the target general service entity is received, and if yes, the transmission process is successful.
  • the service request information may include other information such as the payload target general service entity address, and the payload may include specific content of the service request.
  • the load may be information such as blood pressure and heartbeat of the patient reported by the application.
  • the purpose of setting the specific time for the application is to enable the target general business entity to obtain the urgency of replying to the service request information.
  • the application is successful if it receives the confirmation information returned by the target general service entity even if the application exceeds the specified time. It is optional for the application to time the process of receiving the confirmation message. If the application is timing, it can be known which target common business entity replies can't always respond to a specific time, and the application can take some measures such as shortening the specific time.
  • step 110 is different in different scenarios: Scenario 1.
  • the M2M network includes a target general service entity and at least one application.
  • the step 110 may specifically include: the target general service entity receiving the first service request information from the application.
  • the step 120 may specifically include: sending, by the target general service entity, the acknowledgement information to the application within the specific time.
  • Scenario 2 The M2M network includes a target general service entity, a local general service entity, and at least one application.
  • Method one a single business request.
  • the step 110 may include: the target general service entity receiving the second service request information generated by the local general service entity according to the first service request information received from the application.
  • the first service request information may further include a request type RCAT and a tolerable request processing delay time TRPDT, where the target general book service entity receives, according to the local general service entity, according to the received from the application.
  • the second service request information generated by the first service request information may specifically include:
  • the target general service entity receives the second service request information that is sent by the local general service entity immediately.
  • the target general service entity receives the delayed transmission of the local general service entity.
  • the second service request information if the local processing time of the local general service entity exceeds the TRPDT, the local general service entity returns failure information to the application.
  • the step 120 may include: sending, by the local universal service entity, the acknowledgement information to the application by using the local universal service entity.
  • the step 110 may include: the target general service entity receiving the second service request information that is aggregated by the local general service entity according to the plurality of the first service request information received from the application.
  • the first service request information may further include RCAT and TRPDT, and the target general service
  • the entity may receive, by the local common service entity, the second service request information that is aggregated according to the received multiple service request information, which may include:
  • the local general service entity determines a delay time, and the local general service entity is in the case that the communication link corresponding to the RCAT is not established. Aggregating a plurality of the first service request information received from the application, and the target general service entity receives the aggregated second service request information from the local general service entity,
  • the local processing time is the time at which the local general service entity establishes the communication link.
  • the step 120 may include: in the remaining time, after the target general service entity aggregates the respective confirmation information into the aggregation information, sending the aggregation information to the local general service entity, where the local information is sent by the local And the common service entity separately sends the corresponding acknowledgment information to each of the applications, where the remaining time is determined by the local general service entity according to a specific time and time included in the plurality of the first service request information.
  • the local processing time of the local general service entity is determined, and the aggregation information includes the respective confirmation information.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • the M2M network includes a target general service entity and at least one application.
  • the information recovery method of the M2M network mainly includes:
  • Step 210 The application sends the first service request information, where the first service request information includes a specific time.
  • Step 220 The application receives the confirmation information returned by the target general service entity according to a specific time in the specific time. Specifically, step 210 is different in different scenarios:
  • the M2M network includes a target general service entity and at least one application.
  • the step 210 may specifically include: the application sending the first service request information to the target general service entity.
  • the step 220 may specifically include: the application receiving the confirmation information from the target general service entity within the specific time.
  • the M2M network includes a target general service entity, a local general service entity, and at least one application.
  • the step 210 may include: the M2M network further includes a local general service entity, where the application sends the first service request information to the local general service entity, so that the local general service entity And sending second service request information to the target general service entity according to the first service request information.
  • the step 220 may specifically include: receiving, by the application, the confirmation information returned by the target general service entity from the local universal service entity within the specific time.
  • the application can determine the specific time of the target general service entity by using the specific time included in the first service request information, so that the target general service entity can reply the confirmation information within a specific time.
  • FIG. 3 is a flowchart of a method for replying information of an M2M network according to Embodiment 3 of the present invention.
  • the M2M network may include a target general service entity, a local general service entity, an application 1 and an application 2.
  • the main processes of the information recovery method of the M2M network include:
  • Step 300 The application 1 sends a first service request information (request) to the local general service entity.
  • the first service request information may include time information such as: a specific time, and may also include information such as a payload and an address of a target general service entity.
  • Step 310 The local general service entity (Local CSE) receives the first service of the application 1
  • the second service request information may be generated according to the first service request information, and the generated second service request information is sent to the target general service entity (Target CSE). If the transmission time of the service request information or the like is not considered, the specific time included in the second service request information may be equal to a specific time in the first service request information.
  • Step 320 The application 2 sends the first service request information to the local general service entity.
  • the first service request information may include a specific time, a payload, and an address of the target general service entity.
  • the sequence of the step 300 and the step 320 may be in no particular order.
  • the application 2 sends the first service request information and the first service request information sent by the application 1 in step 300.
  • the specific content may be the same and may be different.
  • the specific time may be the same or different, and the addresses of the target general business entities are the same.
  • the load information in the first service request information of the application 2 may be the body temperature information of the patient collected by the application 2 in the M2M network.
  • Application 1 and Application 2 may be located at the same or different nodes from the local general service entity.
  • the application 11 can communicate with the target general service entity included in the infrastructure node 17 through the local general service entity on the intermediate node 14, and the application 11 can also directly interact with the infrastructure node 17 in case 1.
  • Step 330 After receiving the first service request information of the application 2, the local general service entity generates second service request information according to the first service request information, and sends the second service request information to the target general service entity.
  • the target general service entity may generate confirmation information 1 (notification1), and the notification1 may correspond to a notification ID.
  • the target general service entity may generate an identifier. For notification 2 of 2, notification can also correspond to a notification ID.
  • the target general service entity may directly send the acknowledgment information to the corresponding application through the local general service entity, or may send the acknowledgment information to be sent after a certain delay time (less than a specific time). .
  • the target general service entity determines that the address of the local general service entity that the acknowledgment information 1 and the acknowledgment information 2 need to be sent is the same, the acknowledgment information 1 and the acknowledgment information 2 can be aggregated to obtain the aggregated information, otherwise the aggregation cannot be performed.
  • the goal is that when the general service entity aggregates the confirmation information 1 and the confirmation information 2, it can judge when to reply according to the specific time of the two. For example, the specific time of the confirmation information 1 is 1 second, and the specific time of the confirmation information 2 is 0.5 seconds.
  • the target general service entity receives the first service request information of the application 1 at the time of 0.3 seconds, the application 2 is received.
  • the first service request information, the target general service entity can compare the specific time of the confirmation information 1 and the confirmation information 2, and the time of the delay, thereby determining that: the aggregate information needs to be sent before the time of 0.8 seconds, for example, the target general service entity can be at 0.7.
  • the aggregate information is sent at the second time, and the aggregated information can also be sent at the time of 0.6 seconds, as long as the time smaller than the specific time is selected.
  • the target general service entity generates an acknowledgement information subframe including the payload and the acknowledgement information identifier according to each acknowledgement information, and then splices a plurality of such acknowledgement information subframes together, and adds a local general service entity address to be sent to.
  • the frame header forms an aggregated information frame and can define the maximum allowable length of the aggregated information frame.
  • Step 350 The target general service entity sends the aggregation information to the local general service entity.
  • Step 360 The local general service entity receives the aggregation information replied by the target general service entity, and separates the aggregation information to obtain the confirmation information 1 and the confirmation information 2.
  • Step 370 The local general service entity may separately send the confirmation information to the corresponding application 1 and application 2 according to the identifier of the confirmation information.
  • the information reply method of the M2M network in this embodiment the service received by the target general service entity
  • the request information includes a specific time to enable the target general service entity to send confirmation information to the application within a specific time.
  • the general business entity can reduce or confirm the information aggregation or separation.
  • the M2M network may include a target general service entity, a local general service entity, an application 1 and an application 2.
  • the information replying party of the M2M network mainly includes:
  • Step 400 Application 1 and Application 2 respectively send the first service request information to the local general service entity.
  • the first service request information may include information such as a specific time, a payload, and an address of the target general service entity, a request type RCAT, and a tolerable request processing delay time TRPDT.
  • the local general service entity CSE or SCL
  • CSE or SCL can store the first service request information until an RCAT compliant communication link is established.
  • the value of the RCAT is used to determine whether the communication link is established.
  • the value of the TRPDT determines whether the transmission is delayed.
  • the storage time of the first service request information in the local general service entity cannot exceed the time defined by the TRPDT.
  • the local general service entity can send the information.
  • the request information to the same target general business entity is aggregated and then sent.
  • Step 410 After receiving the first service request information of the application 1, the local general service entity determines whether to save or send the first service request information according to the specific time, the TRPDT, and the RCAT value. Specifically, the following can be included:
  • Case 1 In the case that the communication link corresponding to the RCAT is established, the local general service entity generates the second service request information according to the first service request, and immediately sends the second service request information to the target general service entity.
  • Case 2 In the case that the communication link corresponding to the RCAT is not established, if the processing time of the local general service entity does not exceed the specific time and the TRPDT time, the local general service entity delays forwarding the first service request information to the The target general business entity, the local processing time includes the construction The time at which the communication link corresponding to the RCAT is established.
  • the local general service entity determines whether the time for saving the delayed transmission exceeds a specific time, any one of the parameter time values of the TRPDT.
  • the specific time length may be greater than the TRPDT time length. In this case, when the local general service entity considers whether to save the delayed transmission, only the TRPDT time may be considered, if the local general service entity saves the first service request. When the information exceeds the TRPDT time, a failed response is returned to the application 1.
  • the general service entity when the general service entity saves the first service request information and delays sending, if the first service request information from the application 2 is received within the time of saving the delayed transmission, The two first service request information are aggregated into the second service request information.
  • the local general service entity calculates the remaining time of each specific time according to the specific time, TRPDT and RCAT information of the first service request information sent by the two applications, and uses the calculated remaining time as the specific time of the target general service entity. And sending, to the target general service entity, the payload and the target general service entity address information, where the specific time may be different from the specific time of the first service request information and the second service request information.
  • the time spent in the processing of the local general service entity may be subtracted for the specific time, and the remaining is selected in practice.
  • the time is less than a specific time minus the time spent processing the local general business entity. For example, if the specific time for the application 1 to send the first service request information is 1 second, and the time for the local general service entity to process the first service request is 0.5 seconds, then the remaining time of the second service request information sent to the target general service entity is It is 0.5 seconds.
  • the specific time that the application 2 sends the first service request information is 0.8 seconds, and the time taken by the local general service entity to process the first service request is 0.5 seconds, and the remaining time of the second service request information sent to the target general service entity is 0.3 seconds.
  • the local general service entity may compare the remaining time of the first service request information included in the second service request, and may select the time with the smallest remaining time as the remaining time of the second service request. It should be noted that the specific calculation manner of the remaining time of the second service request may be determined according to actual conditions. For example, in practice, you need to consider the transmission time of the service request in the M2M network. When calculating the remaining time, you should also consider the impact of the transmission time on the remaining time.
  • the way to calculate the remaining time is: the specific time minus the local general service entity processing.
  • the time spent is subtracted from the transmission time of the service request, and the remaining time selected in the actual is less than the calculated time.
  • the smallest time among the remaining time is also selected as the remaining time included in the second service request.
  • Step 420 The local general service entity sends the second service request information to the target general service entity according to the first service request information.
  • Step 430 The target general-purpose book service entity separates the second service request information, obtains two service request information including the remaining time, and generates a confirmation according to the first service request information that is sent by the application 1 and includes the specific time.
  • Information 1 (notification1), notificationl may correspond to a notification (notification ID).
  • the confirmation information 2 (notification2) with the identifier 2 may be generated, and the notification2 may also correspond to one. Identification ID.
  • the target general service entity aggregates the confirmation information 1 and the confirmation information 2 to generate aggregate information.
  • a plurality of acknowledgment information sub-frames may be aggregated. For details, refer to the description of Embodiment 4, and details are not described herein again.
  • Step 440 The target general service entity sends the aggregation information to the local general service entity.
  • Step 450 The local general service entity separates the aggregation information, and obtains the confirmation information 1 and the confirmation information.
  • Step 460 The local general service entity sends the confirmation information 1 to the application 1, and sends the confirmation information 2 to the application 2.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time. Further, the general service entity aggregates the acknowledgement information and/or the service request information, which can reduce the signaling that needs to be transmitted in the M2M network communication.
  • FIG. 5 is a structural block diagram of a general service entity of an M2M network according to Embodiment 5 of the present invention.
  • the general service entity 500 of the M2M network mainly includes:
  • the receiving module 510 is configured to receive service request information, where the service request information includes a specific time, where the specific time is determined by a specific time in the first service request information sent by the application;
  • the sending module 520 is in communication with the receiving module block 510 for transmitting acknowledgement information to the application within the specific time.
  • the receiving module 510 is further configured to receive the first service request information from the application.
  • the receiving module 510 is further configured to receive second service request information generated by the local general service entity according to the first service request information received from the application;
  • the receiving module 520 is further configured to send the confirmation information to the application by the local general service entity during the specific time.
  • the first service request information further includes a request type RCAT and a tolerable request processing delay time TRPDT, where the receiving module 510 is configured to establish a communication link corresponding to the RCAT.
  • the receiving module 510 is further configured to receive, by the local general service entity, the first service request information received from the application. Generated second service request information; or
  • the receiving module 520 is further configured to: if the local processing time of the local general service entity does not exceed the TRPDT, if the communication link corresponding to the RCAT is not established, receive the delayed transmission of the local general service entity.
  • the second service request information is further configured to: if the local processing time of the local general service entity does not exceed the TRPDT, if the communication link corresponding to the RCAT is not established, receive the delayed transmission of the local general service entity. The second service request information.
  • the receiving module 510 is configured to receive by the local universal a second service request information that is aggregated by the service entity according to the plurality of the first service request information received from the application;
  • the sending module 520 is further configured to: after the aggregation information is aggregated into the aggregation information, the aggregation information is sent to the local general service entity, and the local general service entity separates the aggregation information. And sending, to each of the applications, corresponding confirmation information, where the remaining time is determined by the local general service entity according to a specific time included in the plurality of the first service request information and a locality of the local general service entity The processing time is determined, and the aggregation information includes the respective confirmation information.
  • the first service request information further includes an RCAT and a TRPDT, where the local processing time of the local general service entity is not established, if the communication link corresponding to the RCAT is not established. Not exceeding the TRPDT, the local general service entity determines a delay time, and the local general service entity aggregates a plurality of the first service request information received from the application during the delay time, The receiving module 510 is further configured to receive the aggregated second service request information from the local universal service entity, where the local processing time is a time when the local universal service entity establishes the communication link.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • FIG. 6 is a structural block diagram of an application of an M2M network according to Embodiment 6 of the present invention.
  • the application 600 of the M2M network mainly includes:
  • the sending module 610 is configured to send first service request information, where the first service request information includes a specific time.
  • the receiving module 620 is configured to receive, during the specific time, the confirmation information returned by the general service entity according to a specific time.
  • the sending The sending module 610 is further configured to send the first service request information to the general service entity.
  • the receiving module 620 is further configured to receive the acknowledgement information from the universal service entity within the specific time.
  • the M2M network further includes a local general service entity, where the sending module 610 is further configured to send the first service request information to the general service entity, so that the local general service is The entity sends the second service request information to the general service entity according to the first service request information;
  • the receiving module 620 is further configured to receive, by the local general service entity, the acknowledgement information returned by the universal service entity during the specific time.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • FIG. 7 is a structural block diagram of an M2M network according to Embodiment 7 of the present invention. As shown in Figure 7, the M2M network 700 mainly includes:
  • the target general service entity 710, the target general service entity 710 adopts the general service entity 600 of the M2M network in the foregoing embodiment, and the specific features thereof may be referred to in the foregoing embodiment, and are not described herein again.
  • the application 720 employs an application 700 of the M2M network as described in the above embodiments.
  • the local general service entity 730 is configured to receive the first service request information sent by the application 720, and send the second service request information to the target general service entity 710.
  • the specific time of the target general service entity can be determined by the specific time included in the first service request information, so that the target general service entity can reply the confirmation information within a specific time.
  • FIG. 8 is a structural block diagram of a general service entity of an M2M network according to Embodiment 8 of the present invention.
  • the general service entity 800 of the network may be a host server with computing power, a personal computer PC, or a portable computer or terminal that can be carried.
  • the specific embodiments of the present invention do not limit the specific implementation of the computing node.
  • the general service entity 800 includes a processor 810, a communications interface 820, a memory 830, and a bus 840. Among them, the processor 810, the communication interface 820, and the memory 830 complete communication with each other through the bus 840.
  • Communication interface 820 is for communicating with network devices, such as virtual machine management centers, shared storage, and the like.
  • the processor 810 is for executing a program.
  • the processor 81 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.
  • ASIC Application Specific Integrated Circuit
  • Memory 830 is used to store files.
  • the memory 830 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • Memory 830 can also be a memory array.
  • Memory 830 may also be partitioned, and the blocks may be combined into a virtual volume according to certain rules.
  • the M2M network includes a target general service entity and at least one application
  • the program may be program code including computer operation instructions. This program can be used specifically for:
  • the target general service entity receives service request information, where the service request information includes a specific time;
  • the target general service entity sends confirmation information to the application within the specific time.
  • the target general service entity receiving the service request information includes: the target general service entity receiving the first service request information from the application.
  • the M2M network further includes a local general service entity, and the target general service entity receives the service request information, including: the target universal service entity Receiving second service request information generated by the local general service entity according to the first service request information received from the application;
  • the target general service entity sends confirmation information to the application within the specific time, including:
  • the target general service entity sends confirmation information to the application through the local general service entity during the specified time.
  • the first service request information is further included in the request type.
  • the target general service entity receiving second service request information generated by the local general service entity according to the first service request information received from the application receiving, including :
  • the target general service entity receives the second service request information that is sent by the local general service entity immediately;
  • the target general service entity receives the delayed transmission of the local general service entity.
  • the second service request information where the local processing time is the time when the local general service entity establishes the communication link; if the local processing time of the local general service entity exceeds the TRPDT, the local general service entity The application returns a failure message.
  • the M2M network further includes a local general service entity, where the target general service entity receives the service request information, including: the target general service entity receives the local general service entity according to the Transmitting, by the application, a plurality of second service request information that is aggregated by the first service request information;
  • the target general service entity sends confirmation information to the application within the specific time, including:
  • the target general service entity aggregates each confirmation information into aggregate information for the remaining time
  • the local general service entity separates the aggregation information and sends corresponding confirmation information to each of the applications, where the remaining time is from the local
  • the general service entity determines, according to a specific time included in the plurality of the first service request information and a local processing time of the local general service entity, where the aggregation information includes the respective confirmation information.
  • the first service request information further includes an RCAT and a TRPDT
  • the target general service entity says to receive, by the local general service entity, according to the multiple received from the application.
  • the second service request information that is aggregated by the first service request information includes: if the local processing time of the local general service entity does not exceed the TRPDT, if the communication link corresponding to the RCAT does not establish a book, Determining, by the local general service entity, a delay time, the local general service entity aggregating a plurality of the first service request information received from the application, the target general service entity from the local The general service entity receives the aggregated second service request information, where the local processing time is the time at which the local general service entity establishes the communication link.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • FIG. 9 is a structural block diagram of an application of an M2M network according to Embodiment 9 of the present invention.
  • the application 900 of the M2M network may be a computing server host computer, a personal computer PC, or a portable portable computer or terminal.
  • the specific embodiment of the present invention does not limit the specific implementation of the computing node.
  • the application 900 includes a processor 910, a communications interface 920, a memory 930, and a bus 940.
  • the processor 910, the communication interface 920, and the memory 930 complete communication with each other through the bus 940.
  • the communication interface 920 is configured to communicate with a network device, where the network device includes, for example, virtual machine management Center, shared storage, etc.
  • the processor 910 is for executing a program.
  • the processor 910 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.
  • ASIC Application Specific Integrated Circuit
  • the memory 930 is used to store files.
  • the memory 930 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • Memory 930 can also be a memory array.
  • the store 930 may also be partitioned, and the blocks may be combined into a virtual volume according to certain rules.
  • the M2M book network includes a target general service entity and at least one application
  • the program may be program code including computer operation instructions. This program can be used specifically for:
  • the application sends first service request information, where the first service request information includes a specific time
  • the application receives confirmation information returned by the target general service entity according to a specific time within the specific time.
  • the sending, by the application, the first service request information includes: sending, by the application, the first service request information to the target general service entity;
  • the method includes: the application receiving the confirmation information from the target general service entity in the specific time.
  • the M2M network further includes a local general service entity, where the application sends the first service request information, where the application sends the first service request information to the local universal service entity. So that the local general service entity sends the second service request information to the target general service entity according to the first service request information;
  • the returned confirmation information includes: the application receiving the confirmation information returned by the target general service entity from the local general service entity within the specific time.
  • the service request information received by the target general service entity includes a specific time, so that the target general service entity can send the confirmation information to the application within a specific time.
  • the function is implemented in the form of computer software and sold or used as a stand-alone product, it may be considered to some extent that all or part of the technical solution of the present invention (for example, a part contributing to the prior art) is It is embodied in the form of computer software products.
  • the computer software product is typically stored in a computer readable non-volatile storage medium, including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all of the methods of various embodiments of the present invention. Or part of the steps.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Landscapes

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

Abstract

La présente invention concerne un réseau et une application M2M, une entité de services communs et un procédé de réponse d'informations. Le réseau M2M comprend une entité de services communs cible ainsi qu'une ou plusieurs applications. Le procédé comprend : la réception, par l'entité de services communs cible, d'informations de requête de service, lesdites informations de requête de service comprenant une durée spécifique ; et l'envoi, par l'entité de services communs cible, d'informations d'accusé de réception vers l'application avant la fin de ladite durée spécifique. Grâce au réseau et à l'application M2M, à l'entité de services communs et au procédé de réponse d'informations de la présente invention, les informations de requête de service reçues par l'entité de services communs cible incluent la durée spécifique, de manière à ce que l'entité de services communs cible puisse envoyer les informations d'accusé de réception vers l'application avant la fin de ladite durée spécifique.
PCT/CN2013/087249 2013-11-15 2013-11-15 Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations WO2015070441A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/087249 WO2015070441A1 (fr) 2013-11-15 2013-11-15 Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/087249 WO2015070441A1 (fr) 2013-11-15 2013-11-15 Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations

Publications (1)

Publication Number Publication Date
WO2015070441A1 true WO2015070441A1 (fr) 2015-05-21

Family

ID=53056657

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/087249 WO2015070441A1 (fr) 2013-11-15 2013-11-15 Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations

Country Status (1)

Country Link
WO (1) WO2015070441A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685204A (zh) * 2011-03-17 2012-09-19 华为技术有限公司 数据资源传输的方法和设备
CN103026778A (zh) * 2010-07-27 2013-04-03 高通股份有限公司 用于减少频繁的服务器消息的装置和方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103026778A (zh) * 2010-07-27 2013-04-03 高通股份有限公司 用于减少频繁的服务器消息的装置和方法
CN102685204A (zh) * 2011-03-17 2012-09-19 华为技术有限公司 数据资源传输的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"MACHINE-TO-MACHINE COMMUNICATION (M2M), MLA, DLA AND MLA interface", ETSI TS 102 921 V1.1.1, 29 February 2012 (2012-02-29), pages 73 - 80 *

Similar Documents

Publication Publication Date Title
US10868767B2 (en) Data transmission method and apparatus in optoelectronic hybrid network
US20180262301A1 (en) Cross-layer and cross-application acknowledgment for data transmission
US9571409B2 (en) Maximum transmission unit negotiation method and data terminal
CN104871637A (zh) 代理连接方法和装置
US9081905B2 (en) Low latency interconnect bus protocol
US9706435B2 (en) Method and system for dynamically changing upper bound on data packet size in wireless communication networks
US20100202451A1 (en) Modified internet protocol (ip) data packet for asynchronous ip communications
US20130077611A1 (en) Tunneled Direct Link Setup Systems And Methods With Consistent Link Information Maintenance
WO2023124098A1 (fr) Procédé et appareil de communication pour générer et envoyer une trame d'accusé de réception dans un réseau ieee 802.15.4
CN110996346B (zh) 一种下行报文轨迹追踪方法、装置及计算机可读存储介质
WO2019015036A1 (fr) Procédé de pontage de répéteur, et passerelle
WO2022083371A1 (fr) Procédé et dispositif de transmission de données
US11277873B2 (en) Methods and nodes for facilitating non-IP UE-to-UE communications
US20160352470A1 (en) Communication device, communication method, and communication system
US11477619B2 (en) Variable volume data transmission in a mobile communication network
JP6438110B2 (ja) 通信ネットワークでのシグナリングのための方法およびデバイス
WO2021018068A1 (fr) Procédé de surveillance de liaison radio, et dispositif de communication
US10812399B2 (en) Communication method, communication apparatus, and program for reducing delay time of transmission control protocol (TCP) transmission processing
TWI713340B (zh) 用於處理移動通信中的封包資料會聚協定複製的方法和裝置
WO2015070441A1 (fr) Réseau et application m2m (machine à machine), entité de services communs et procédé de réponse d'informations
WO2014180286A1 (fr) Procédé, cse, et système, pour la transmission d'une demande d'application m2m
US20210014006A1 (en) System and method for implementing a hybrid automatic repeat request process
US20200275374A1 (en) Service control apparatus, mobility management apparatus, service control method, and non-transitory computer readable medium
US9338016B2 (en) Method and apparatus for exchanging messages
CN114124275B (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: 13897629

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13897629

Country of ref document: EP

Kind code of ref document: A1