WO2019218728A1 - 订阅服务器、订阅终端及信息订阅方法和系统 - Google Patents

订阅服务器、订阅终端及信息订阅方法和系统 Download PDF

Info

Publication number
WO2019218728A1
WO2019218728A1 PCT/CN2019/074122 CN2019074122W WO2019218728A1 WO 2019218728 A1 WO2019218728 A1 WO 2019218728A1 CN 2019074122 W CN2019074122 W CN 2019074122W WO 2019218728 A1 WO2019218728 A1 WO 2019218728A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
entity
information
resource
event
Prior art date
Application number
PCT/CN2019/074122
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 KR1020207035829A priority Critical patent/KR102631288B1/ko
Priority to US17/054,617 priority patent/US11470155B2/en
Priority to EP19803453.0A priority patent/EP3799458A4/en
Priority to JP2020563768A priority patent/JP7420743B2/ja
Publication of WO2019218728A1 publication Critical patent/WO2019218728A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the present disclosure relates to the field of Internet of Things technologies, and in particular, to a subscription server, a subscription terminal, and an information subscription method and system.
  • M2M Machine to Machine
  • IoT Internet of Things
  • M2M Machine to Machine
  • a machine can subscribe to events on another machine so that when another machine generates an event, it can get events from another machine.
  • an event may include multiple parts, such as a core part and an auxiliary part.
  • the core part is the core of the event.
  • the core part of the individual can not meet the needs of the application, and it is necessary to cooperate with other auxiliary parts to make comprehensive judgment.
  • a related method for obtaining event information by using a mechanism for subscribing to an event is: after obtaining the core information, sending an acquisition request for the auxiliary information to obtain auxiliary information, and constructing a complete event after receiving the auxiliary information. That is to say, after the core information of the event is obtained, the event cannot be processed in time, and other auxiliary information needs to be obtained. The problem with this approach is that it may delay the processing time of the event.
  • Another related method for obtaining event information by using a mechanism for subscribing to an event is to separately subscribe to the core information and auxiliary information of the event in order to obtain complete information of the event.
  • the transmission period of the core information and the auxiliary information is usually different, there is a possibility that the notified party continuously receives the auxiliary information from the notifying party, but still needs to wait for the core information to perform event processing.
  • the problem with this method is that the reception of the auxiliary information increases the burden of the notified party when there is no core information of the event, and also increases the network load of the notified party and the notifying party.
  • the present disclosure provides an information subscription method.
  • the method includes: after determining that the request information of the request from the first entity satisfies an event notification rule in the subscription resource related to the first entity, confirming the requested content information as the first information of the event; according to the subscription
  • the associated object of the resource acquires the second information of the event; and sends a notification message including the first and second information to the notified party of the subscription resource.
  • the subscription resource includes: the event notification rule, the associated object, and a notification address identifier of the notified party.
  • the subscription resource includes: the event notification rule and the notification address identifier of the notified party.
  • the associated object is an associated object created in a container of resources of the first entity.
  • the associated object includes an identification of an associated resource or associated resource.
  • Acquiring the second information of the event according to the associated object of the subscription resource includes: acquiring second information of the event from the associated resource, or acquiring, according to the identifier of the associated resource, from the corresponding associated resource The second information of the event.
  • the method before the determining, further includes: receiving, by the requesting party of the subscription resource, a subscription request for the first entity, where the subscription request includes: the event notification rule, the associated resource An identifier, and a notification address identifier of the notified party.
  • the subscription resource for the first entity is created according to the received subscription request.
  • the subscription resource further includes: a notification content type, and the selectable value of the notification content type includes an associated resource type value.
  • acquiring the second information of the event according to the associated object of the subscription resource comprises: acquiring the event according to the associated object of the subscription resource after determining that the notification content type is an associated resource type value The second message.
  • the first entity is an application entity, or a generic service entity.
  • the request includes creating a content instance request or updating a content instance request.
  • the method further comprises: creating a new content instance in a container for the resource of the first entity according to the create content instance request sent by the first entity, and storing the received information in the In the new content instance.
  • the associated resource includes a resource, container, or content instance of the entity.
  • the entity includes an application entity, or a generic service entity.
  • the associated resource is a resource of a second entity that is different from the first entity.
  • the method further includes: receiving a created content instance request that is sent by the second entity and carrying the second information of the event;
  • the create content instance request sent by the entity creates a new content instance in the container of the resource of the second entity, and stores the second information of the event in the new content instance.
  • the first information of the event is core information of the event
  • the second information of the event is auxiliary information of the event.
  • the core information of the event is information about the occurrence of a traffic accident
  • the auxiliary information of the event is location information of the accident vehicle.
  • the first entity is a traffic accident identification application entity and the second entity is a vehicle location sensing application entity.
  • the present disclosure also provides a subscription server.
  • the subscriber includes a confirmation module, an acquisition module, and a transmission module.
  • the confirmation module is configured to confirm the content information of the request as the first information of the event after determining that the request information of the request from the first entity satisfies the event notification rule in the subscription resource related to the first entity.
  • the obtaining module is configured to acquire second information of the event according to the associated object of the subscription resource.
  • the sending module is configured to send a notification message including the first and second information to the notified party of the subscription resource.
  • the subscription server further includes a creating module, configured to create the first entity according to the subscription request after receiving a subscription request for the first entity from the requesting party of the subscription resource Subscribe to resources.
  • the subscription request includes: the event notification rule, an identifier of an associated resource, and a notification address identifier of the notified party.
  • the identifier of the associated resource is used to create the associated object.
  • the subscription server further includes: a creating module, configured to create a first entity according to the subscription request after receiving a subscription request for the first entity from the requesting party of the subscription resource Said subscription resources.
  • the subscription request includes: the event notification rule, and a notification address identifier of the notified party.
  • the obtaining module is configured to acquire second information of the event according to the associated object of the subscription resource after determining that the notification content type is an associated resource type value.
  • the request includes creating a content instance requesting the subscription server further comprising a receiving module and a creating module.
  • the receiving module is configured to receive a create content instance request sent by the first entity.
  • the creating module is configured to create a new content instance in the container of the resource of the first entity according to the created content instance request, and store the received information in the new content instance.
  • the associated resource is a resource of a second entity that is different from the first entity.
  • the receiving module is further configured to receive a created content instance request that is sent by the second entity and carries the second information of the event.
  • the creating module is further configured to create a new content instance in a container of resources of the second entity according to the create content instance request sent by the second entity, and store the second information of the event in the new content. In the example.
  • the present disclosure also provides a subscription terminal.
  • the subscription terminal includes a subscription request module and a notification message processing module.
  • the subscription requesting module is configured to send a subscription request for the first entity to the subscription service entity to create a subscription resource related to the first entity.
  • the subscription request includes: an event notification rule, and a notification address identifier of the notified party of the subscription resource.
  • the notification message processing module is configured to receive and process the notification message sent by the subscription service entity.
  • the notification message includes first information of an event confirmed according to the requested content information sent by the first entity and second information of the event acquired according to the associated object of the subscription resource.
  • the subscription request further includes: an identifier of the associated resource, used to create an associated object in the subscription resource.
  • the subscription content further includes a notification content type.
  • the notification content type is set to the associated resource type value.
  • the present disclosure also provides an information subscription system.
  • the information subscription system includes: a first entity, a subscription service entity as described above, and a subscription terminal.
  • the first entity is used to send the request.
  • the subscribing terminal is used as the notified party of the subscription resource for receiving and processing the notification message.
  • the present disclosure also provides another information subscription system.
  • the information subscription system includes a first entity for transmitting a request, a subscription service entity as described above, and a subscription terminal as described above.
  • the subscribing terminal is used as the notified party of the subscription resource for receiving and processing the notification message.
  • the present disclosure also provides a computer readable medium having stored thereon computer readable instructions.
  • the computer readable instructions when executed by a computing device, cause the computing device to perform the method as described above.
  • the present disclosure also provides a computing device.
  • the computing device includes: one or more processors; and a memory having a plurality of instructions stored thereon.
  • the plurality of instructions cause the one or more processors to perform the method as described above in response to being executed by the one or more processors.
  • FIG. 3 is a structural diagram of an information subscription system according to an embodiment of the present disclosure.
  • FIG. 4 is a data structure of a resource created by a subscription service entity locally for a registered entity according to an embodiment of the present disclosure
  • FIG. 5 is another data structure of a resource created by a subscription service entity locally for a registered entity according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for a subscription service entity to create a subscription resource according to an embodiment of the present disclosure
  • FIG. 7 is a flowchart of an information subscription method according to an embodiment of the present disclosure.
  • FIG. 8 is a block diagram of an internal structure of a subscription service entity according to an embodiment of the present disclosure.
  • FIG. 9 is a block diagram of an internal structure of a subscribing terminal according to an embodiment of the present disclosure.
  • the functional framework of the M2M communication system defines an application entity (AE) and a generic service entity (CSE).
  • the application entity is an entity that implements M2M application service logic, such as traffic accident processing applications, vehicle networking applications, industrial control applications, and the like.
  • the generic service entity represents the service function implementation entity and is a set of "general service functions" instantiation, including data management, device management, subscription management, and security mechanisms.
  • FIG. 1 shows a flow chart of a method of information subscription in the related art.
  • the mechanism for subscribing to events is used to obtain core information and auxiliary information of the event.
  • Application Entity 1 (AE1)
  • AE2 Application Entity 2
  • AE3 Application Entity 3
  • CSE Common Service Entity
  • AE1 may be a recognition application entity that identifies a traffic accident
  • AE2 is a sensing application entity that senses traffic accident related data
  • AE3 is a management application entity that handles traffic accidents.
  • the application entity AE1 can register on the CSE by sending a registration request to the CSE.
  • the CSE can create a resource for AE1 for AE1 based on the registration request and return a registration response to it.
  • AE2 and/or AE3 can also be registered on the CSE. After successful registration, the CSE can create AE2 and/or AE3 resources locally accordingly.
  • AE3 is configured to learn information about traffic accidents for handling traffic accidents. For this reason, it is necessary to obtain the information on the occurrence of the traffic accident (the core information of the event) transmitted by the AE1 and the position information of the accident vehicle collected by the AE2 (the auxiliary information of the event) before the traffic accident can be handled.
  • AE3 may send a subscription request for AE1 to the CSE to subscribe to the event of AE1.
  • the CSE accordingly creates a subscription resource under the resources of AE1 and sends a subscription response to AE3.
  • AE1 upon detecting the occurrence of an event (eg, a traffic accident), sends a request to create a content instance to the CSE containing content information related to the event that occurred, such as the occurrence of a traffic accident.
  • the CSE After receiving the request of AE1, the CSE creates a content instance under the container ⁇ AE1>/container of the AE1 resource, records the occurrence information of the traffic accident therein, and sends a creation content instance response to AE1.
  • the CSE also generates a notification request for an event in AE1 accordingly to notify AE3.
  • AE3 sends a notification response to the CSE and obtains resource parameters related to the event.
  • AE3 finds from the acquired resource parameters that information in AE2 is also needed, for example, including the location information of the accident vehicle in the traffic accident, the next step can be processed.
  • AE3 sends a request for information to acquire information in AE2 to the CSE.
  • the CSE responds to the information request to provide information in AE2.
  • the AE3 uses the information of the AE1 and the acquired information of the AE2 to construct a complete event message package for traffic accident handling.
  • the problem with this method is that after the AE3 obtains the core information of the event, the event cannot be processed in time, and the information possessed by other entities needs to be acquired, thereby delaying the processing time of the event. For traffic accidents, this means that you may miss the best accident rescue time.
  • FIG. 2 shows a flow chart of another information subscription method of the related art. Similar to Figure 1, AE1, AE2, AE3, and CSE are referred to in Figure 2, and initially, AE1-3 has been registered on the CSE.
  • AE3 sends a subscription request to both the AE1 and AE2 to the CSE to subscribe to the events of AE1 and AE2, respectively.
  • the CSE accordingly creates a subscription resource under the AE1 resource and the AE2 resource and sends a subscription response to the AE3.
  • AE2 periodically sends location information, such as the vehicle, to the CSE by sending a create/update content instance request.
  • the CSE creates/updates a content instance to save the event each time it receives the information of AE2, and sends a create/update content instance response to AE2.
  • the CSE also sends a notification request to AE3 accordingly to communicate information from AE2 thereto.
  • AE3 sends a notification response to the CSE upon receipt of the notification request.
  • AE1 detects that an event has occurred, such as a traffic accident
  • a request to create a content is sent to the CSE.
  • the CSE After receiving the request of AE1, the CSE creates a content instance under the container ⁇ AE1>/container of the AE1 resource, records the occurrence information of the traffic accident therein, and sends a creation content instance response to AE1.
  • the CSE also generates a notification request for an event in AE1 accordingly to notify AE3.
  • AE3 sends a notification response to the CSE upon receipt of the notification request.
  • AE2 continues to transmit the location information of the vehicle after the AE1 detects a traffic accident.
  • AE2 sends location information, such as the vehicle, to the CSE by sending a create/update content instance request.
  • the CSE After receiving the information of AE2, the CSE also creates/updates the content instance to save the event, and sends a create/update content instance response to AE2.
  • the CSE also sends a notification request to AE3 accordingly to communicate information from AE2 to it.
  • AE3 sends a notification response to the CSE upon receipt of the notification request.
  • the AE3 acquires the information of the previously received AE2 after judging that the event generated by the AE1, that is, the occurrence information of the traffic accident in the AE has been received.
  • the AE3 constructs a complete event message packet for traffic accident processing, for example, using event information in AE1 and AE2 data closest to the time of occurrence of the event in the AE.
  • the problem with this method is that in a scenario such as a car network, the reporting period of the vehicle position information is shorter due to the longer reporting period of the traffic accident occurrence information.
  • the CSE will continuously send a notification message carrying the auxiliary information of the similar vehicle location to the notified party (such as AE3) of the subscription information.
  • the notified party cannot judge based on the event generated by the auxiliary information alone, and needs to wait for the core information similar to the traffic accident occurrence information. Therefore, when there is no core information of the event, the reception of the auxiliary information increases the burden of the notified party, and also increases the network load of the notified party (such as AE3) and the notifying party (such as CSE).
  • a subscription service entity a subscription terminal, an information subscription method, and a system are proposed, which can avoid increasing the network load of the notifier and the notified party, and can ensure that after receiving the notification message of the event. There is enough information to handle the event in a timely manner.
  • the subscription service entity determines that the request information satisfies the event notification rule in the subscription resource, and then the requested content information Confirming the first information of the event; and acquiring the second information of the event from the associated object of the subscription resource (such as the resource of AE2), and sending the first information to the notified party (such as AE3) of the subscription resource And a notification message of the second information.
  • the subscription service entity also acquires the second information related to the event, so that the combined event information is sent to the notified party (such as AE3) in the notification message.
  • the notified party of the subscription resource can process the event according to the complete event information in time to avoid the delay of the event processing time; on the other hand, since there is no second information directly subscribed to the event, The amount of notification messages for subscription information is reduced, and the network load of the notified party and the notifying party is alleviated.
  • FIG. 3 shows an architectural diagram of an information subscription system according to an embodiment of the present disclosure.
  • the information subscription system includes a first entity 301, a subscription server 302, and a notified party 303 that subscribes to the resource.
  • a subscription service entity can be included in the subscriber 302.
  • the Subscriber and the Subscription Service Entity are used interchangeably.
  • the first entity 301 is configured to send a request to the subscription server 302.
  • the first entity can be the entity being subscribed to.
  • the first entity 301 can be an application entity (AE) in M2M communication.
  • AE application entity
  • the first entity may also be a generic service entity.
  • the functional framework of the M2M communication system defines an Application Service Node (ASN), which may include a generic service entity and at least one application entity.
  • ASN Application Service Node
  • the application entity may first register with a generic service entity that is included in the same ASN. Thereafter, the generic service entity can send a request for creation, acquisition, update, deletion, and notification to the subscription service entity on behalf of the ASN, and receive a response from the subscription service entity.
  • the request can be a create content instance request or an update content instance request or the like.
  • the first entity sends the request upon detecting the occurrence of an event, such as a traffic accident or a change in vehicle location.
  • the first entity may also periodically send the request to periodically create or update information stored in the subscribing service entity.
  • the request can include request information.
  • the request information may be type information indicating the type of the request, such as the action involved in the request. Additionally or alternatively, the request information may also be content information for communicating information related to, for example, an event.
  • the subscriber 302 is configured to confirm the content information of the request as the first information of the event after receiving and determining that the request information of the request sent by the first entity 301 satisfies the event notification rule in the subscription resource.
  • the subscription resource may be a sub-resource created under the resource of the first entity, which may include attributes such as an event notification rule.
  • the request information satisfaction event notification rule indicates that the content information of the request is to be notified as an event to the specified notified party in the subscription resource.
  • the subscriber 302 also acquires the second information of the event according to the associated object of the subscription resource.
  • the associated object may include an identifier of the associated resource or associated resource.
  • the associated object can be a resource of the second entity 304.
  • the second entity 304 can be an entity that has registered with the subscription server 302 and created a corresponding resource thereon.
  • the subscriber 302 can thereby obtain second information about the event from the second entity 304 from the resources of the second entity 304.
  • the subscriber 302 transmits a notification message containing the first and second information of the event to the notified party 303 specified in the subscription resource.
  • the subscription service entity in the subscription server 302 can be a Common Service Entity (CSE) in M2M communication.
  • CSE Common Service Entity
  • the notified party 303 of the subscription resource is configured to receive and process the notification message sent by the subscription service entity 302.
  • the notified party 303 can process the related event based on the first and second information included in the notification message.
  • the notified party 303 of the subscription resource may be an application entity (AE), or a general service entity (CSE).
  • AE application entity
  • CSE general service entity
  • the third entity and the notified party of the subscription resource are used interchangeably.
  • the first entity may register with the subscriber prior to sending the information to the subscriber. After the registration is successful, the subscriber creates the resources of the first entity locally.
  • Sub-resources such as containers, can also be created in the resources of each entity.
  • a container in which a first entity is also created in the resources of the first entity is shown in FIG.
  • Subscription resources can be created in the container.
  • Subscription resources can include different attributes, such as event notification rules, notification address identifiers, and associated objects.
  • the notification address identifier may be, for example, a notification address of the notified party of the subscription resource, such as a URI (ie, a URI of the third entity).
  • the presence of the associated object may indicate that the event notification for the subscription resource also relates to other objects associated with the subscription resource.
  • the associated object may be an identifier of the associated resource, thereby pointing to/associating other sub-resources in the same resource, and may also point to/associate other resources or sub-resources in other resources, such as a container or a content instance. As shown in FIG. 4, the associated object of the subscription resource of the first entity may point to the container of the second entity. Additionally or alternatively, the identification of the associated resource may also include an identification of the resource type to point/associate one or more resources of the same type. This allows multiple resources to be associated at the same time in a simple manner, improving subscription efficiency.
  • the attribute of the subscription resource may further include a notification content type.
  • the notification content type is set to the associated resource type value, the indication notification message should contain related information of the associated object.
  • a content instance in the container, such as multiple content instances under the container of the second entity shown in FIG.
  • a content instance may be created when an event occurs and specific content is generated for saving event related content information.
  • the associated object of the subscription resource is set in the subscription resource.
  • the associated objects in the subscription resource can be managed by the requesting party of the subscription resource through a subscription request, such as setting, changing, or deleting.
  • Figure 5 illustrates another data structure for a resource created by a subscribing service entity locally for a registered entity.
  • the subscription service entity can create resources for each registered entity separately. It is also possible to create sub-resources such as containers in the resources of each entity. Subscription resources, content instances, and so on can be created in the container. The difference from FIG. 4 is that the associated object of the subscription resource can be created as a child resource in the container of the resource of the subscribed entity (shown as the first entity in FIG. 5) instead of being created as the attribute of the subscription resource. .
  • the associated object of the subscription resource is directly set in the container of the resource of the subscribed party (such as the first entity) of the subscription resource, the associated object may not have to be subscribed by the requester of the subscribed resource. Individually set, changed, or deleted, but can be shared by multiple subscription resources of the first entity. In some embodiments, the associated object can be set, changed, or deleted by the subscription service entity or the first entity.
  • FIG. 6 is a flowchart of a method for creating a subscription resource by a subscription service entity according to an embodiment of the present disclosure.
  • the subscription service entity sends a subscription request for the first entity.
  • the requesting party of the subscription resource may be the notified party of the subscription resource itself, that is, it may be the third entity as described above.
  • the requesting party subscribing to the resource may also send a subscription request to other entities and specify other entities as the notified party in the subscription request.
  • it can also be other entities registered on the subscription service entity.
  • the request for the subscription resource is sent by the subscription service entity, and the subscription request for the first entity includes: an event notification rule, an identifier of the associated resource, and a notification address identifier (eg, a URI of the third entity).
  • the related information of the associated object can be set or changed by the requesting party of the subscribed resource through the subscription request.
  • the identifier of the associated resource may not be included in the subscription request sent by the requesting party. In this way, related information of the associated object can be set or changed by the subscription service entity.
  • the subscription request may further include: a notification content type.
  • the notification content type can be set to the associated resource type value.
  • the subscription service entity creates a subscription resource of the first entity according to the subscription request sent by the requester of the subscription resource.
  • the subscription service entity may create a subscription resource in a container of the resource of the first entity according to the subscription request sent by the requester of the subscription resource.
  • the created subscription resource may include: an event notification rule, an association object, and a notification address identifier, such as a URI of the notified party of the subscription resource (ie, a URI of the third entity).
  • a notification address identifier such as a URI of the notified party of the subscription resource (ie, a URI of the third entity).
  • the associated object may not be included in the created subscription resource.
  • an association object created in a container of resources of the first entity may be used as an association object of the subscription resource.
  • the associated object may include an identifier of the associated resource or associated resource.
  • the associated resource may be a resource/container/latest content instance of the second entity, or the like, or a resource identifier corresponding to the resources.
  • the created subscription resource may further include a notification content type. If the notification content type in the subscription request is set to the associated resource type value, the notification content type in the created subscription resource is also set to the associated resource type value. In this way, in the case that the created subscription resource does not include the associated object, the subscription service entity can also understand that the event notification of the subscription resource also involves other associated resources.
  • the subscribing service entity returns a subscription response to the requesting party of the subscribing resource to complete the subscription.
  • the subscription service entity may create a subscription resource of the first entity locally according to the subscription resource creation instruction input by the administrator, in addition to creating the subscription resource of the first entity according to the subscription request.
  • FIG. 7 is a flowchart of a method for information subscription provided by an embodiment of the present disclosure.
  • S701 The first entity sends a request to the subscription service entity.
  • the first entity may send a request to the subscribing service entity upon detecting the occurrence of the event.
  • the request may be, for example, a create content instance request or an update content instance request.
  • the request can contain request information.
  • the first entity may be a traffic accident recognition application module, which, after detecting the occurrence of a traffic accident, carries the information about the occurrence of the traffic accident in the request for creating a content instance and sends the information to the subscription service entity for subscription to the service. The entity saves related events.
  • the subscription service entity After determining that the request information in the request satisfies the event notification rule in the subscription resource of the first entity, the subscription service entity confirms the content information of the request as the first information of the event.
  • the subscription service entity creates a new content instance in the container of the resource of the first entity according to the content creation instance request sent to the first entity, and stores the received information in the created content instance.
  • the subscription service entity compares the request information with the event notification rules of the subscription resource. If the request information satisfies the event notification rule of the subscription resource, the content information of the request is confirmed as the first information of the event.
  • the first information of the event may be core information of the event.
  • the core information of an event may be information about the occurrence of a traffic accident.
  • the request information can include the requested content information. Accordingly, the event notification rule monitors the specific content in the request. Additionally or alternatively, the request information may include type (action) information corresponding to the request. Accordingly, the event notification rule monitors the type or action involved in the request.
  • the subscription service entity acquires the second information of the event according to the association object of the subscription resource.
  • the associated object may be one of the subscribed resources and optionally created according to a subscription request.
  • the association object may also be created as a child resource in a container of resources of the first entity, and optionally may be shared by multiple subscription resources of the first entity.
  • the value of the notification content type may indicate the type of content included in the notification message.
  • the notification content type can include a plurality of selectable values.
  • the value of the notification content type may be “modify attribute type value” to indicate that the content included in the notification message is a modified attribute of the event.
  • the value of the notification content type may also be "all attribute type values" to indicate that the content included in the notification message is all attributes of the event.
  • the value of the notification content type may also be extended to “associated resource type value” to indicate that the notification message further includes related information of the associated resource.
  • the new function of the embodiment of the present disclosure can be implemented by using the data structure in the existing subscription resource, that is, the related information of the associated resource is also carried in the notification message.
  • the subscription service entity may obtain the second information of the event according to the association object in the subscription resource or the subscription resource.
  • the associated object of the subscription resource may include an identifier of the associated resource or associated resource.
  • the subscription service entity may obtain the second information of the event from the corresponding associated resource according to the identifier of the associated resource; or the subscription service entity may directly obtain the second information of the event from the associated resource.
  • An associated resource can be a resource, container, or content instance of an entity (including the first entity and other entities).
  • An entity may include an application entity, or a generic service entity.
  • the associated resource can be a resource of a second entity that is different from the first entity.
  • the identifier of the associated object may be the identifier of the resource of the second entity, and the subscription service entity may obtain the second information of the event from the resource of the second entity according to the identifier of the resource of the second entity.
  • the second entity may be an entity pre-registered to the subscribing service entity.
  • the subscribing service entity When the second entity registers with the subscribing service entity, the subscribing service entity also locally creates the resources of the second entity.
  • the second entity may send the second information of the event to the subscription service entity in the request to create the content instance.
  • the second information of the event may be auxiliary information of the event.
  • the second information may be periodically sent by the second entity to the subscription service entity in the create content instance request.
  • the second entity may be a location sensing application module in the vehicle, and the second information of the event may be location information of the vehicle.
  • the subscription service entity can be a roadside unit. The second entity may periodically transmit the second information of the event (such as the location information of the vehicle) to the subscription service entity in the request to create the content instance.
  • the subscription service entity creates a new content instance each time after receiving the request to create a content instance sent by the second entity, where the second information of the event in the content instance request is created (such as the location information of the vehicle) ).
  • the subscription service entity can obtain the event stored in the newly created content instance from the associated object, that is, the resource of the second entity.
  • the second information (such as the location information of the vehicle).
  • the subscription service entity sends a notification message to the third entity that is the notified party of the subscription resource.
  • the subscribing service entity sends a notification message including the first and second information of the event to the third entity.
  • the first and second information of the event may be the information content itself or an information identifier.
  • S705 The third entity that is the notified party of the subscription resource receives and processes the notification message.
  • the third entity may obtain the complete information of the event from the notification message, so that the event processing can be directly performed, and the delay of the event processing time is avoided.
  • the amount of notification messages of the subscription information is reduced, and the network load of the third entity and the subscription service entity is alleviated.
  • the third entity may be a traffic accident management application module, and after receiving the notification message, the traffic accident may be processed in time according to the occurrence information of the traffic accident in the notification message and the location information of the vehicle.
  • FIG. 8 is a block diagram showing an internal structure of a subscriber provided by an embodiment of the present disclosure.
  • the subscription server includes a confirmation module 801, an acquisition module 802, and a transmission module 803.
  • the confirmation module 801 is configured to confirm the content information of the request as the first information of the event after determining that the request information of the request from the first entity satisfies the event notification rule in the subscription resource of the first entity.
  • the subscription resource includes: the event notification rule, and a notification address identifier of the notified party.
  • the subscription resource also has a corresponding associated object.
  • the associated object can be included as an attribute in the subscription resource or as a child resource different from the subscription resource.
  • the association object includes: an identifier of an associated resource or an associated resource.
  • the subscription resource may further include: a notification content type.
  • the first information of the event may be core information of the event.
  • the obtaining module 802 is configured to acquire second information of the event according to the associated object of the subscription resource.
  • the obtaining module 802 after determining that the notification content type is an associated resource type value, acquires second information of the event according to the associated object of the subscription resource.
  • the associated resource may be other sub-resources of the first entity, or resources, containers or content instances of other entities. Other entities may include an application entity, or a generic service entity.
  • the second information of the event may be auxiliary information of the event.
  • the sending module 803 is configured to send, to the notified party of the subscription resource, a notification message that includes the first and second information of the event.
  • the subscription server 804 can also be included in the subscription server.
  • the creating module 804 is configured to create the subscription resource of the first entity according to the subscription request after receiving a subscription request for the first entity from the requesting party of the subscription resource.
  • the subscription request may include: the event notification rule, an identifier of an associated resource, and a notification address identifier.
  • the receiving server may further include: a receiving module 805.
  • the receiving module 805 is configured to receive a create content instance request from the first entity.
  • the creation module 804 can create a new content instance in the container of the resource of the first entity according to the request, and store the information in the received request (including the first information of the event) in the created content instance.
  • the receiving module 805 is further configured to receive a created content instance request from the second entity that carries the second information of the event.
  • the creating module 804 may create a new content instance in the second entity's container in the second entity's resource according to the request to create a content instance request sent by the second entity, and store the second information of the event in the second entity. The newly created content instance of the second entity.
  • the subscriber server can be a computing device including a processor and a memory, which can be in the form of a server, or can be a desktop computer, a notebook computer, a smart phone, a tablet computer, and other electronic devices including a processor and a memory. .
  • FIG. 9 is a block diagram showing the internal structure of a subscription terminal provided by an embodiment of the present disclosure.
  • the subscribing terminal can act as a requester of the subscription resource or as a notified party of the subscription resource.
  • the subscription terminal includes a subscription request module 901 and a notification message processing module 902.
  • the subscription request module 901 is configured to send a subscription request for the first entity to the subscription server to create a subscription resource related to the first entity.
  • the subscription request includes: an event notification rule, an associated resource identifier, and a notification address identifier of the notified party.
  • the notification content type may also be included in the subscription request to be associated with the resource type value.
  • the notification message processing module 902 is configured to receive and process the notification message sent by the subscription server.
  • the notification message includes first information of an event confirmed according to the requested content information sent by the first entity and second information of the event acquired according to the associated object of the subscription resource.
  • the second information of the event after receiving the first information of the event from the first entity, the second information of the event may be obtained from the corresponding association object according to the associated object of the subscription resource of the first entity, such that The first and second information of the event may be sent to the notified party of the subscription resource through a notification message.
  • the notified party after receiving the notification message, the notified party can process the event in time according to the complete event information, thereby avoiding the delay of the event processing time.
  • the amount of notification messages of the subscription information is reduced, and the network load of the notified party and the notifying party is alleviated.
  • the value of the notification content type is extended, so that the selectable value of the notification content type may also be an “associated resource type value”, which is used to indicate that the notification message includes related information of the associated resource.
  • the added functions of the embodiments of the present disclosure can be implemented by using the data structure in the existing subscription resources, thereby facilitating backward compatibility with the existing subscription mechanism.
  • the subscription terminal can be a television, a smart home appliance, a charging car, a desktop computer, a laptop, a smartphone, a tablet, a game controller, a music player (eg, an mp3 player, etc.), and others including a processor and a memory.
  • Terminal for example, mobile terminal, smart terminal.
  • a “module” can be a hardware unit configured as a processor, a functional block, or the like. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. Hardware units are not limited by the materials from which they are formed or the processing mechanisms employed therein.
  • a hardware unit may include components of an integrated circuit or system on chip, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), and others in silicon or other hardware devices. achieve.
  • a "module” can be a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer, but is not limited thereto.
  • an application running on a controller and a controller can be a module.
  • One or more modules can reside within a process and/or thread of execution, and a module can be limited to one computer and/or distributed between two or more computers.
  • the claimed subject matter can be implemented as a method, apparatus, or article of manufacture that uses standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof, to control a computer to implement the disclosed subject matter.
  • article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • one or more of the operations described may constitute computer readable instructions stored on one or more computer readable medium(s), where executed by a computing device The computing device will be caused to perform the described operations.
  • the order in which some or all of the operations are described should not be construed as implying that the operations are necessarily order dependent. Those skilled in the art having the benefit of this description will recognize alternative ordering. In addition, it will be understood that not all operations are necessarily present in every embodiment provided herein.
  • Computer-readable medium means a non-transitory medium and/or device that enables persistent storage of information, and/or a tangible storage device that contrasts with a simple signal transmission, carrier wave or signal itself.
  • a computer readable medium refers to a non-signal bearing medium.
  • the computer readable medium comprises hardware, such as volatile and nonvolatile, implemented in a method or technique suitable for storing information such as computer readable instructions, data structures, program modules, logic elements/circuits or other data, Removable and non-removable media and / or storage devices.
  • Examples of computer readable media can include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage device, hard disk, magnetic tape cartridge, magnetic tape, magnetic disk storage device Or other magnetic storage device, or other storage device, tangible medium or article of manufacture suitable for storing the desired information and accessible by the computer.

Abstract

本公开涉及一种订阅服务器、订阅终端及信息订阅方法和系统。所述方法包括：在判定来自第一实体的请求的请求信息满足订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息；根据所述订阅资源的关联对象获取所述事件的第二信息；向所述订阅资源的被通知方发送包含第一和第二信息的通知消息。应用本公开既能避免增加请求方和通知方的网络负荷，又可以保证在接收到事件的通知消息后能及时处理事件。

Description

订阅服务器、订阅终端及信息订阅方法和系统
相关申请
本申请要求于2018年5月18日递交的中国专利申请No.201810479229.6的优先权，在此全文引用上述中国专利申请公开的内容作为本申请的一部分。
技术领域
本公开涉及物联网技术领域，特别涉及一种订阅服务器、订阅终端及信息订阅方法和系统。
背景技术
在物联网(IoT)系统中，M2M(Machine to Machine)是重要的方面之一，其是一种以机器终端智能交互为核心的、网络化的应用与服务。一个机器可以订阅另一个机器的事件，使得当另一个机器产生事件时，它可以获取另一个机器的事件。通常，事件可能包括多个部分，比如核心部分和辅助部分。核心部分是事件的核心。但是单独的核心部分不能够满足应用的需求，需要配合其他一些辅助部分才能进行综合判定。
一种利用订阅事件的机制获取事件信息的相关方法是：在获取到核心信息后，再发送对于辅助信息的获取请求，以获取辅助信息，且当收到辅助信息后才可以构建完整的事件。也就是说，在获取到事件的核心信息后，并不能及时进行事件的处理，还需获取其它的辅助信息。这种方法的问题在于，这样可能延迟事件的处理时间。
另一种利用订阅事件的机制获取事件信息的相关方法是：为获取事件的完整信息需要分别订阅事件的核心信息和辅助信息。但是，由于通常核心信息和辅助信息的发送周期不同，所以这样可能出现被通知方不断接收到来自通知方的辅助信息，但仍需要等待核心信息以进行事件处理的情况。这种方法的问题在于，在没有事件的核心信息时，辅助信息的接收增加了被通知方处理的负担，同时也增加了被通知方和通知方的网络负荷。
发明内容
在第一方面，本公开提供了一种信息订阅方法。该方法包括：在判定来自第一实体的请求的请求信息满足该第一实体相关的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息；根据所述订阅资源的关联对象获取所述事件的第二信息；以及向所述订阅资源的被通知方发送包含第一和第二信息的通知消息。
在一些实施例中，所述订阅资源包括：所述事件通知规则、所述关联对象、以及所述被通知方的通知地址标识符。
在一些实施例中，所述订阅资源包括：所述事件通知规则和所述被通知方的通知地址标识符。所述关联对象是在所述第一实体的资源的容器中创建的关联对象。
在一些实施例中，所述关联对象包括关联资源或关联资源的标识。所述根据所述订阅资源的关联对象获取所述事件的第二信息包括：从所述关联资源中获取所述事件的第二信息，或根据所述关联资源的标识，从对应关联资源中获取所述事件的第二信息。
在一些实施例中，在所述判定之前还包括：接收来自所述订阅资源的请求方的针对第一实体的订阅请求，所述订阅请求中包括：所述事件通知规则、所述关联资源的标识，以及所述被通知方的通知地址标识符。根据接收的订阅请求创建针对第一实体的所述订阅资源。
在一些实施例中，所述订阅资源中还包括：通知内容类型，且所述通知内容类型的可选取值包括关联资源类型值。
在一些实施例中，根据所述订阅资源的关联对象获取所述事件的第二信息包括：在确定所述通知内容类型为关联资源类型值后，根据所述订阅资源的关联对象获取所述事件的第二信息。
在一些实施例中，第一实体为应用实体、或通用服务实体。
在一些实施例中，所述请求包括创建内容实例请求或更新内容实例请求。
在一些实施例中，所述方法还包括：根据第一实体发送的创建内容实例请求，在用于第一实体的资源的容器中创建一个新的内容实例，并把接收的信息存储于所述新的内容实例中。
在一些实施例中，所述关联资源包括实体的资源、容器或者内容实例。所述实体包括应用实体、或通用服务实体。
在一些实施例中，所述关联资源为不同于第一实体的第二实体的资源。在所述根据所述订阅资源的关联对象获取所述事件的第二信息之前，该方法还包括：接收第二实体发送的携带有所述事件的第二信息的创建内容实例请求；根据第二实体发送的创建内容实例请求，在第二实体的资源的容器中创建一个新的内容实例，并把所述事件的第二信息存储于所述新的内容实例中。
在一些实施例中，所述事件的第一信息为事件的核心信息，所述事件的第二信息为事件的辅助信息。
在一些实施例中，所述事件的核心信息为交通事故的发生信息，所述事件的辅助信息为事故车辆的位置信息。第一实体为交通事故识别应用实体，第二实体为车辆位置传感应用实体。
在第二方面，本公开还提供了一种订阅服务器。该订阅服务器包括确认模块、获取模块和发送模块。确认模块用于在判定来自第一实体的请求的请求信息满足第一实体相关的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息。获取模块用于根据所述订阅资源的关联对象获取所述事件的第二信息。发送模块用于向所述订阅资源的被通知方发送包含第一和第二信息的通知消息。
在一些实施例中，所述订阅服务器还包括创建模块，用于在接收到来自所述订阅资源的请求方的针对第一实体的订阅请求后，根据所述订阅请求创建第一实体的所述订阅资源。所述订阅请求包括：所述事件通知规则、关联资源的标识、以及所述被通知方的通知地址标识符。所述关联资源的标识用以创建所述关联对象。
在一些实施例中，所述订阅服务器还包括：创建模块，用于在接收到来自所述订阅资源的请求方的针对第一实体的订阅请求后，根据所述订阅请求创建第一实体的所述订阅资源。所述订阅请求包括：所述事件通知规则、以及所述被通知方的通知地址标识符。
在一些实施例中，所述获取模块用于在确定所述通知内容类型为关联资源类型值后，根据所述订阅资源的关联对象获取所述事件的第二信息。
在一些实施例中，所述请求包括创建内容实例请求所述订阅服务器还包括接收模块和创建模块。接收模块用于接收第一实体发送的创建内容实例请求。创建模块用于根据所述创建内容实例请求在第一实体 的资源的容器中创建一个新的内容实例，并把接收的信息存储于所述新的内容实例中。
在一些实施例中，所述关联资源为不同于所述第一实体的第二实体的资源。所述接收模块还用于接收第二实体发送的携带有所述事件的第二信息的创建内容实例请求。所述创建模块还用于根据第二实体发送的创建内容实例请求，在第二实体的资源的容器中创建一个新的内容实例，并把所述事件的第二信息存储于所述新的内容实例中。
在第三方面，本公开还提供了一种订阅终端。该订阅终端包括订阅请求模块和通知消息处理模块。订阅请求模块用于向订阅服务实体发送针对第一实体的订阅请求以创建第一实体相关的订阅资源。所述订阅请求中包括：事件通知规则、以及所述订阅资源的被通知方的通知地址标识符。通知消息处理模块用于接收并处理所述订阅服务实体发送的通知消息。所述通知消息中包括根据第一实体发送的请求的内容信息而确认的事件的第一信息和根据所述订阅资源的关联对象获取的所述事件的第二信息。
在一些实施例中，所述订阅请求中还包括：关联资源的标识，用于创建所述订阅资源中的关联对象。
在一些实施例中，所述订阅请求中还包括通知内容类型。该通知内容类型被设置为关联资源类型值。
在第四方面，本公开还提供了一种信息订阅系统。该信息订阅系统包括：第一实体、如上所述的订阅服务实体和订阅终端。第一实体用于发送请求。订阅终端作为所述订阅资源的被通知方，用于接收并处理所述通知消息。
在第五方面，本公开还提供了另一种信息订阅系统。该信息订阅系统包括：第一实体，用于发送请求；如上所述的订阅服务实体；和如上所述的订阅终端。订阅终端作为所述订阅资源的被通知方，用于接收并处理所述通知消息。
在第六方面，本公开还提供了一种计算机可读介质，其上存储有计算机可读指令。所述计算机可读指令在由计算设备执行时使所述计算设备执行如上所述的方法。
在第七方面，本公开还提供了一种计算设备。该计算设备包括：一个或多个处理器；以及存储器，其上存储有多个指令。所述多个指令 响应于被所述一个或多个处理器执行而使所述一个或多个处理器执行如上所述的方法。
附图说明
为使本公开的目的、技术方案和优点更加清楚明白，以下参照附图结合具体实施例，对本公开在一些实施例中详细说明。
图1为相关技术的一种信息订阅方法的流程图；
图2为相关技术的另一种信息订阅方法的流程图；
图3为本公开实施例提供的一种信息订阅系统的架构图；
图4为本公开实施例提供的订阅服务实体在本地为注册的实体创建的资源的一种数据结构；
图5为本公开实施例提供的订阅服务实体在本地为注册的实体创建的资源的另一种数据结构；
图6为本公开实施例提供的一种订阅服务实体创建订阅资源的方法流程图；
图7为本公开实施例提供的一种信息订阅方法的流程图；
图8为本公开实施例提供的一种订阅服务实体的内部结构框图；以及
图9为本公开实施例提供的一种订阅终端的内部结构框图。
具体实施方式
下面详细描述本公开的实施例。所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，仅用于说明本公开，而不能解释为对本公开的限制。
本技术领域技术人员可以理解，除非另外指定或者从上下文中清楚是指向单数形式，否则这里使用的“一”、“一个”、“所述”和“该”也可包括复数形式。这里使用的措辞“和/或”包括一个或更多个相关联的列出项的任何或所有可能的组合。
需要说明的是，本公开实施例中所有使用“第一”和“第二”等的表述均是为了区分两个相同名称非相同的实体或者非相同的参量。在本公开的上下文中，“第一”、“第二”等仅为了表述的方便，不应理解为对本 公开实施例的限定。
M2M通信系统的功能框架定义了应用实体(AE)和通用服务实体(CSE)。应用实体是实现M2M应用服务逻辑的实体，如交通事故处理应用、车联网应用、工业控制应用等。通用服务实体则代表服务功能实现实体，是一组“通用服务功能”的实例化，主要包括数据管理、设备管理、订阅管理和安全机制等。
图1示出了相关技术中的一种信息订阅方法的流程图。在该方法中，利用订阅事件的机制来获取事件的核心信息和辅助信息。在图1中示出了应用实体1(AE1)、应用实体2(AE2)、应用实体3(AE3)，以及通用服务实体(CSE)。在一个示例的交通事故的场景中，AE1可以为识别交通事故的识别应用实体，AE2为感测交通事故相关数据的传感应用实体，AE3为处理交通事故的管理应用实体。
初始地，应用实体AE1可以通过向CSE发送注册请求来在CSE上注册。CSE可以根据注册请求为AE1创建AE1的资源，并向其返回注册响应。
类似地，AE2和/或AE3也可以在CSE上进行注册。注册成功后，CSE可以相应地在本地创建AE2和/或AE3的资源。
在示例的场景中，AE3被配置为获知交通事故的信息以进行交通事故的处理。为此它需要获得AE1发送的交通事故的发生信息(事件的核心信息)以及AE2采集的事故车辆的位置信息(事件的辅助信息)，方能进行交通事故的处理。
在101，AE3可以向CSE发送针对AE1的订阅请求以便订阅AE1的事件。CSE相应地在AE1的资源下创建订阅资源，并向AE3发送订阅响应。
在102，AE1在检测到事件(例如交通事故)发生时，向CSE发送创建内容实例请求，其中包含与发生的事件相关的内容信息，例如交通事故的发生信息。CSE在接收到AE1的请求后，在AE1资源的容器<AE1>/container下创建内容实例，在其中记录交通事故的发生信息，并向AE1发送创建内容实例响应。
在103，CSE还相应地产生有关AE1中事件的通知请求以通知AE3。AE3在收到通知请求后将通知响应发送给CSE，且获取该事件相关的资源参数。
当AE3从获取的资源参数发现还需得到AE2中的信息，例如包括该交通事故中的事故车辆的位置信息，才能进行下一步处理时，在104，AE3向CSE发送获取AE2中信息的信息请求。CSE对该信息请求进行响应，以提供AE2中的信息。AE3使用AE1的信息和获取到的AE2的信息构建完整的事件消息包，以进行交通事故处理。
该方法的问题在于：在AE3获取到事件的核心信息后，不能及时进行事件的处理，还需获取其它实体所具有的信息，从而延迟了事件的处理时间。对于交通事故而言，这意味着可能因此错过最佳的事故救援时间。
图2示出了相关技术的另一种信息订阅方法的流程图。与图1中类似，图2中涉及AE1、AE2、AE3和CSE，且初始地，AE1-3均已经在CSE上注册。
在201，AE3向CSE发送针对AE1和AE2两者的订阅请求，以分别订阅AE1和AE2的事件。CSE相应地在AE1资源和AE2资源下创建订阅资源，并向AE3发送订阅响应。
在202，AE2通过发送创建/更新内容实例请求而将例如车辆的位置信息定期向CSE发送。CSE在每次接收到AE2的信息后，新建/更新内容实例以保存事件，且向AE2发送创建/更新内容实例响应。
在203，CSE还相应地向AE3发送通知请求以向其传送来自AE2的信息。AE3在收到通知请求后将通知响应发送给CSE。
在204，当AE1检测到事件发生，例如发生交通事故时，向CSE发送创建内容示例请求。CSE在接收到AE1的请求后，在AE1资源的容器<AE1>/container下创建内容实例，在其中记录交通事故的发生信息，并向AE1发送创建内容实例响应。
在205，CSE还相应地产生有关AE1中事件的通知请求以通知AE3。AE3在收到通知请求后将通知响应发送给CSE。
在一些场景下，有可能在AE1检测到交通事故后AE2继续发送车辆的位置信息。这样，在206，AE2通过发送创建/更新内容实例请求而将例如车辆的位置信息发送给CSE。CSE在接收到AE2的信息后，同样新建/更新内容实例以保存事件，且向AE2发送创建/更新内容实例响应。
在207，CSE还相应地向AE3发送通知请求以向其传送来自AE2 的信息。AE3在收到通知请求后将通知响应发送给CSE。
AE3在判断已经接收到AE1产生的事件，即AE中的交通事故的发生信息后，获取之前接收到的AE2的信息。AE3例如使用AE1中的事件信息和与AE中事件发生的时间最接近的AE2数据，构建完整的事件消息包以进行交通事故处理。
该方法的问题在于，在例如车联网的场景中，由于交通事故发生信息的上报周期更长，车辆位置信息上报的周期更短。这样，CSE会不停向订阅信息的被通知方(如AE3)发送携带类似车辆位置的辅助信息的通知消息。被通知方单独根据辅助信息产生的事件无法进行判定，需要等待类似交通事故发生信息的核心信息。因此在没有事件的核心信息时，辅助信息的接收增加了被通知方处理的负担，同时也增加了被通知方(如AE3)和通知方(如CSE)的网络负荷。
按照本公开的实施例，提出了一种订阅服务实体、订阅终端、信息订阅方法和系统，其既能避免增加通知方和被通知方的网络负荷，又能保证在接收到事件的通知消息后有足够的信息使得能及时处理事件。
在本公开的实施例中，在第一实体(比如AE1)向订阅服务实体(比如CSE)发送请求信息后，订阅服务实体判定请求信息满足订阅资源中的事件通知规则，则将请求的内容信息确认为事件的第一信息；进而从所述订阅资源的关联对象(比如AE2的资源)中获取所述事件的第二信息，向所述订阅资源的被通知方(比如AE3)发送包含第一和第二信息的通知消息。这样，在订阅事件的第一信息时，订阅服务实体对事件相关的第二信息也进行获取，从而组合为完整的事件信息在通知消息中发送给被通知方(比如AE3)。如此，一方面，订阅资源的被通知方接收到事件的通知消息后就能根据完整的事件信息及时处理事件，避免事件处理时间的延迟；另一方面，由于没有直接订阅事件的第二信息，减少了订阅信息的通知消息量，减轻了被通知方和通知方的网络负荷。
图3示出了按照本公开实施例提供的一种信息订阅系统的架构图。该信息订阅系统包括：第一实体301、订阅服务器302，以及订阅资源的被通知方303。订阅服务器302中可包含订阅服务实体。在下面的描述中，订阅服务器和订阅服务实体可互换地使用。
第一实体301用于向订阅服务器302发送请求。第一实体可以为被订阅的实体。在一些实施例中，第一实体301可以是M2M通信中的应用实体(AE)。
在另一些实施例中，第一实体还可以是通用服务实体。M2M通信系统的功能框架定义了一种应用服务节点(ASN)，其可以包括一个通用服务实体和至少一个应用实体。在这样的场景下，应用实体可以首先向被包括在相同的ASN中的通用服务实体注册。之后，通用服务实体可以代表ASN向订阅服务实体发送创建、获取、更新、删除和通知等请求，并接收订阅服务实体的响应。
在一些实施例中，请求可以是创建内容实例请求或者更新内容实例请求等。示例性地，第一实体在检测到事件发生(例如交通事故发生或者车辆位置发生变化)时发送所述请求。替换地，第一实体也可以定期发送所述请求，以便周期性地创建或者更新订阅服务实体中保存的信息。请求可以包括请求信息。请求信息可以是类型信息，用以指示请求的类型，例如请求所涉及的动作。附加地或者替换地，请求信息也可以是内容信息，用以传送与例如事件相关的信息。
订阅服务器302用于在接收并判定第一实体301发送的请求的请求信息满足订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息。该订阅资源可以是创建在该第一实体的资源下的子资源，其可以包含事件通知规则等属性。请求信息满足事件通知规则表明该请求的内容信息要作为事件被通知给订阅资源中指定的被通知方。
订阅服务器302还根据所述订阅资源的关联对象来获取所述事件的第二信息。关联对象可以包括：关联资源或关联资源的标识。在一个示例中，关联对象可以为第二实体304的资源。第二实体304可以是已向订阅服务器302注册且在其上创建相应资源的实体。订阅服务器302由此可以从第二实体304的资源获得来自第二实体304的有关所述事件的第二信息。订阅服务器302向订阅资源中指定的被通知方303发送包含所述事件的第一和第二信息的通知消息。订阅服务器302中的订阅服务实体可以是M2M通信中的通用服务实体(CSE)。
订阅资源的被通知方303用于接收并处理订阅服务实体302发送的通知消息。被通知方303可以基于通知消息中包括的第一和第二信息 来处理相关的事件。订阅资源的被通知方303可以是应用实体(AE)，或通用服务实体(CSE)。在本文中，第三实体和订阅资源的被通知方可互换地使用。
在一些实施例中，第一实体在向订阅服务器发送信息之前，可以先在订阅服务器上注册。注册成功后，订阅服务器在本地创建第一实体的资源。
图4示出了按照本公开实施例的订阅服务实体在本地为注册的实体创建的资源的一种数据结构。如图4所示，在第一实体和第二实体注册后，订阅服务实体分别为其创建第一实体的资源和第二实体的资源。在各实体的资源中还可以创建子资源，例如容器。图4上示出了在第一实体的资源中还创建有第一实体的容器。在容器中可以创建订阅资源。订阅资源中可以包括不同的属性，例如事件通知规则、通知地址标识符和关联对象等。通知地址标识符可以例如是所述订阅资源的被通知方的通知地址，比如URI(即第三实体的URI)。关联对象的存在可以表明该订阅资源的事件通知还涉及与该订阅资源关联的其他对象。关联对象可以是关联资源的标识，由此指向/关联同一资源中的其他子资源，也可以指向/关联其他资源或者其他资源中的子资源，例如容器或者内容实例等。如图4所示的，第一实体的订阅资源的关联对象可以指向第二实体的容器。附加地或者替换地，关联资源的标识还可以包括资源类型的标识，以便指向/关联同一类型的一个或多个资源。这样可以允许以简单的方式同时关联多个资源，提高了订阅效率。
可选地，订阅资源的属性还可以包括通知内容类型。当通知内容类型被设置为关联资源类型值，指示通知消息中应包含关联对象的相关信息。
在容器中还可以创建内容实例，例如图4中所示的第二实体的容器下的多个内容实例。在一些示例中，内容实例可以在事件发生且产生具体内容时创建，用于保存事件相关的内容信息。
在本公开的这一实施例中，订阅资源的关联对象被设置于订阅资源中。相应地订阅资源中的关联对象可由订阅资源的请求方通过订阅请求来进行管理，比如进行设置、更改或者删除等。
图5示出了订阅服务实体在本地为注册的实体创建的资源的另一 种数据结构。与图4中类似，订阅服务实体可以分别为各个注册的实体创建资源。在各实体的资源中还可以创建例如容器的子资源。在容器中可以创建订阅资源和内容实例等。与图4的不同之处在于，订阅资源的关联对象可以改而在被订阅实体(图5中示为第一实体)的资源的容器中作为子资源创建，而不是作为该订阅资源的属性创建。
由于在这一实施例中，订阅资源的关联对象被直接设置于订阅资源的被订阅方(比如第一实体)的资源的容器中，所以关联对象可以不必由订阅资源的请求方通过订阅请求来个别地设置、更改或删除，而是可以由第一实体的多个订阅资源共享。在一些实施例中，关联对象可以由订阅服务实体或者第一实体来设置、更改或删除。
图6示出了本公开实施例提供的由订阅服务实体创建订阅资源的方法流程图。
S601：订阅资源的请求方向订阅服务实体发送针对第一实体的订阅请求。订阅资源的请求方可以是订阅资源的被通知方本身，也即其可以是如前文所述的第三实体。替换地，订阅资源的请求方也可以为其他实体发送订阅请求且在订阅请求中指定其他实体为被通知方。由此，其也可以是在订阅服务实体上注册的其它实体。
可选地，订阅资源的请求方向订阅服务实体发送的针对第一实体的订阅请求中包括：事件通知规则、关联资源的标识，以及通知地址标识符(例如第三实体的URI)。这样，关联对象的相关信息可由订阅资源的请求方通过订阅请求来设置或更改。替换地，请求方所发送的订阅请求中可以不包括关联资源的标识。这样，关联对象的相关信息可以由订阅服务实体来设置或更改。
可选地，订阅请求中还可以包括：通知内容类型。通知内容类型可以设置为关联资源类型值。
S602：订阅服务实体根据订阅资源的请求方发送的订阅请求，创建第一实体的订阅资源。
可选地，订阅服务实体可以根据订阅资源的请求方发送的订阅请求，在第一实体的资源的容器中创建订阅资源。创建的订阅资源中可以包括：事件通知规则、关联对象以及通知地址标识符，例如所述订阅资源的被通知方的URI(即第三实体的URI)。替换地，当订阅请求中未包括关联资源的标识时，创建的订阅资源中可以不包括关联对 象。此时可以将第一实体的资源的容器中创建的关联对象用作所述订阅资源的关联对象。
关联对象可以包括：关联资源或关联资源的标识。举例而言，关联资源可以是第二实体的资源/容器/最新的内容实例等，或者是这些资源对应的资源标识。
可选地，对于订阅请求中还包括通知内容类型的情况，创建的订阅资源中还可包括通知内容类型。若订阅请求中的通知内容类型设置为关联资源类型值，则创建的订阅资源中的通知内容类型也设置为关联资源类型值。这样，在创建的订阅资源不包括关联对象的情况下，订阅服务实体也可以明了该订阅资源的事件通知还涉及其他的关联资源。
S603：订阅服务实体向订阅资源的请求方返回订阅响应，以完成订阅。
附加地或者替换地，订阅服务实体除了根据订阅请求创建第一实体的订阅资源外，也可以根据管理人员输入的订阅资源创建指令在本地创建第一实体的订阅资源。
在创建了第一实体的订阅资源后，订阅请求中指定的订阅资源的被通知方就可以从订阅服务实体收到有关第一实体的订阅信息。图7示出了本公开实施例提供的一种信息订阅的方法流程图。
S701：第一实体向订阅服务实体发送请求。
可选地，第一实体可以在检测到事件发生后向订阅服务实体发送请求。所述请求可以是例如创建内容实例请求或者更新内容实例请求。请求可以包含请求信息。例如，在车联网场景中，第一实体可以是交通事故识别应用模块，其在检测到交通事故发生后，将交通事故的发生信息携带于创建内容实例请求中发送给订阅服务实体，以便订阅服务实体保存相关的事件。
S702：订阅服务实体在判定所述请求中的请求信息满足该第一实体的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息。
可选地，订阅服务实体根据到第一实体发送的创建内容实例请求，在第一实体的资源的容器中创建一个新的内容实例，把接收的信息存储于创建的内容实例中。
订阅服务实体将请求信息与订阅资源的事件通知规则进行比较。若请求信息满足订阅资源的事件通知规则，则将所述请求的内容信息确认为事件的第一信息。可选地，所述事件的第一信息可以是事件的核心信息。例如，在车联网场景中，事件的核心信息可以是交通事故的发生信息。
在一些实施例中，请求信息可以包括请求的内容信息。相应地，事件通知规则监控的是请求中的具体内容。附加地或者替换地，请求信息可以包括请求所对应的类型(动作)信息。相应地，事件通知规则监控的是请求所涉及的类型或动作。
在示例性的车联网的场景中，第一实体的请求可以是：创建内容容器1下的内容实例1请求(内容为：isAccident＝Y(是事故吗？＝是))，相应地，类型信息为创建内容容器1下的内容实例1，内容信息为内容容器1下的内容实例1(内容为：isAccident＝Y)。
在一个示例中，事件通知规则可以监控请求中具体的内容，比如：当通知事件内容＝(isAccident＝Y)时，第一信息可以被确认为内容容器1下的内容实例1(内容为：isAccident＝Y)。在另一个示例中，事件通知规则可以监控请求的类型，比如：当通知事件类型＝创建内容容器1的内容实例时，第一信息可以被确认为内容容器1下的内容实例1(内容为：isAccident＝Y)。
S703：订阅服务实体根据所述订阅资源的关联对象获取所述事件的第二信息。关联对象可以是所述订阅资源中的一个属性，且可选地根据订阅请求来创建。或者，关联对象也可以在所述第一实体的资源的容器中作为子资源来创建，且可选地可以由第一实体的多个订阅资源共享。
在一些实施例中，对于订阅资源中包括通知内容类型的情况，通知内容类型的取值可以指示通知消息中所包含的内容的类型。通知内容类型可以包括多个可选取值。比如，通知内容类型的取值可以是“修改属性类型值”，用以指示通知消息中所包含的内容为事件的修改的属性。通知内容类型的取值还可以是“全部属性类型值”，用以指示通知消息中所包含的内容为事件的全部属性。
按照本公开的实施例，通知内容类型的取值还可以被扩展为“关联资源类型值”，用以指示通知消息中还包含关联资源的相关信息。这 样，利用现有的订阅资源中的数据结构即可实现本公开实施例新增的功能，即在通知消息中还携带关联资源的相关信息。
在一些实施例中，本步骤中订阅服务实体在确定所述通知内容类型为关联资源类型值后，可以根据所述订阅资源中或者订阅资源外的关联对象获取所述事件的第二信息。
订阅资源的关联对象可以包括：关联资源或关联资源的标识。订阅服务实体可以根据关联资源的标识，从对应关联资源中获取所述事件的第二信息；或者，订阅服务实体可以直接从关联资源中获取所述事件的第二信息。
关联资源可以是实体(包括第一实体和其他实体)的资源、容器、或者内容实例等。实体可以包括应用实体、或通用服务实体。
举例而言，关联资源可以为不同于第一实体的第二实体的资源。相应地，关联对象的标识可以为第二实体的资源的标识，且订阅服务实体可以根据第二实体的资源的标识，从第二实体的资源中获取所述事件的第二信息。
第二实体可以是预先注册到订阅服务实体的实体。在第二实体注册到订阅服务实体时，订阅服务实体也在本地创建了第二实体的资源。
第二实体在注册到订阅服务实体后，可以将事件的第二信息携带于创建内容实例请求中发送给订阅服务实体。所述事件的第二信息可以是事件的辅助信息。示例性地，该第二信息可以由第二实体定期携带于创建内容实例请求中向订阅服务实体发送。比如，在车联网场景中，第二实体可以是车辆中的位置传感应用模块，而事件的第二信息可以是车辆的位置信息。订阅服务实体可以是路侧单元。第二实体可以定期地将事件的第二信息(比如车辆的位置信息)携带于创建内容实例请求中向订阅服务实体发送。订阅服务实体则在每次接收到第二实体发送的创建内容实例请求后，创建一个新的内容实例，在该内容实例中存储创建内容实例请求中的事件的第二信息(比如车辆的位置信息)。这样，订阅服务实体在确认从第一实体接收的请求的内容信息为事件的第一信息后，便可以从关联对象，也即第二实体的资源中获取新创建的内容实例中所存储的事件的第二信息(比如车辆的位置信息)。
S704：订阅服务实体向作为所述订阅资源的被通知方的第三实体发 送通知消息。
本步骤中，订阅服务实体向第三实体发送包含事件的第一和第二信息的通知消息。事件的第一和第二信息可以是信息内容本身，也可以是信息标识。
S705：作为所述订阅资源的被通知方的第三实体接收并处理通知消息。
本步骤中，第三实体在接收到包含事件的第一和第二信息的通知消息后，可以从通知消息中获得事件的完整信息，从而可以直接进行事件处理，避免了事件处理时间的延迟。同时，也不用直接订阅第二实体的事件的第二信息，减少了订阅信息的通知消息量，减轻了第三实体和订阅服务实体的网络负荷。在车联网场景中，第三实体可以是交通事故管理应用模块，其在接收到通知消息后，即可根据通知消息中的交通事故的发生信息，以及车辆的位置信息及时进行交通事故的处理。
图8示出了本公开实施例提供的订阅服务器的一种内部结构框图。该订阅服务器包括：确认模块801、获取模块802、发送模块803。
确认模块801用于在判定来自第一实体的请求的请求信息满足第一实体的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息。所述订阅资源包括：所述事件通知规则、以及被通知方的通知地址标识符。所述订阅资源还具有对应的关联对象。关联对象可以作为属性被包括在订阅资源中，也可以作为不同于订阅资源的子资源来创建。所述关联对象包括：关联资源或关联资源的标识。在一些实施例中，订阅资源中还可包括：通知内容类型。可选地，所述事件的第一信息可以是事件的核心信息。
获取模块802用于根据所述订阅资源的关联对象获取所述事件的第二信息。可选地，获取模块802在确定所述通知内容类型为关联资源类型值后，根据所述订阅资源的关联对象获取所述事件的第二信息。所述关联资源可以是第一实体的其他子资源，或者是其他实体的资源、容器或者内容实例等。其他实体可以包括应用实体、或通用服务实体。可选地，所述事件的第二信息可以是事件的辅助信息。
发送模块803用于向所述订阅资源的被通知方发送包含所述事件的第一和第二信息的通知消息。
在一些实施例中，订阅服务器中还可包括：创建模块804。创建模块804用于在接收到来自所述订阅资源的请求方的针对第一实体的订阅请求后，根据所述订阅请求创建第一实体的所述订阅资源。所述订阅请求可以包括：所述事件通知规则、关联资源的标识、以及通知地址标识符。
在一些实施例中，订阅服务器中还可包括：接收模块805。接收模块805用于接收来自第一实体的创建内容实例请求。创建模块804可以根据该请求在第一实体的资源的容器中创建一个新的内容实例，把接收的请求中的信息(包括事件的第一信息)存储于创建的内容实例中。
当所述关联资源例如是第二实体的资源时，接收模块805还用于接收来自第二实体的携带有所述事件的第二信息的创建内容实例请求。创建模块804可以根据该请求根据第二实体发送的创建内容实例请求，在第二实体的资源中于第二实体的容器内创建一个新的内容实例，并把所述事件的第二信息存储于第二实体的新创建的内容实例中。
要指出的是，针对图6和图7讨论的所有可能性对于图8也是有效的。
示例性地，订阅服务器可以为一种包括处理器和存储器的计算设备，其可以采用服务器的形式，也可以是台式电脑、笔记本电脑、智能手机、平板电脑以及其他包括处理器和存储器的电子设备。
图9示出了本公开实施例提供的订阅终端的内部结构框图。该订阅终端可以充当订阅资源的请求方，也可以充当订阅资源的被通知方。该订阅终端包括：订阅请求模块901和通知消息处理模块902。
订阅请求模块901用于向订阅服务器发送针对第一实体的订阅请求以创建第一实体相关的订阅资源。所述订阅请求中包括：事件通知规则、关联资源标识、以及被通知方的通知地址标识符。在一些实施例中，订阅请求中还可包括设置为关联资源类型值的通知内容类型。
通知消息处理模块902用于接收并处理所述订阅服务器发送的通知消息。所述通知消息中包括根据第一实体发送的请求的内容信息确认的事件的第一信息和根据所述订阅资源的关联对象获取的所述事件的第二信息。
在本公开的实施例中，在接收到来自第一实体的事件的第一信息 后，可根据第一实体的订阅资源的关联对象，从相应关联对象中获取所述事件的第二信息，使得可以将事件的第一和第二信息一并通过通知消息发送给订阅资源的被通知方。这样，被通知方接收到通知消息后就能根据完整的事件信息及时处理事件，避免事件处理时间的延迟。另一方面，由于没有直接订阅事件的第二信息，减少了订阅信息的通知消息量，减轻了被通知方和通知方的网络负荷。
按照本公开的实施例，对通知内容类型的取值进行了扩展，使通知内容类型的可选取值还可以为“关联资源类型值”，用以指示通知消息中包含关联资源的相关信息。这样，利用现有的订阅资源中的数据结构即可实现本公开实施例所新增的功能，从而便于后向兼容于现有的订阅机制。
示例性地，订阅终端可以为电视、智能家电设备、充电汽车、台式电脑、笔记本电脑、智能手机、平板电脑、游戏控制器、音乐播放器(例如mp3播放器等)以及其他包括处理器和存储器的终端(例如，移动终端，智能终端)。
当在本文中使用时，术语“模块”、“系统”和/或“接口”等等一般性地打算指计算机相关的实体，要么硬件、硬件与软件的组合、软件，要么执行中的软件。在一些示例中，“模块”可以是被配置成处理器、功能块等的硬件单元。这可以包括以硬件实现为专用集成电路或者使用一个或多个半导体形成的其它逻辑器件。硬件单元不受形成它们的材料或者其中所采用的处理机制的限制。硬件单元可以包括以下项的组件：集成电路或片上系统、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、复杂可编程逻辑器件(CPLD)、以及在硅或其它硬件设备中的其它实现。在另一些示例中，“模块”可以是运行在处理器上的进程、处理器、对象、可执行文件、执行的线程、程序和/或计算机，但是不限于此。举例来说，运行在控制器上的应用和控制器两者都可以是模块。一个或多个模块可以驻留在执行的进程和/或线程中，并且模块可以局限于一个计算机上和/或分布在两个或更多个计算机之间。
另外，所要求保护的主题可以被实现为方法、装置或制造品，其使用标准的编程和/或工程技术来生产软件、固件、硬件或它们的任何组合以控制计算机实现所公开的主题。当在本文中使用时，术语“制造 品”打算涵盖可从任何计算机可读设备、载体或介质访问的计算机程序。
此外，本文提供了实施例的各种操作。在一个实施例中，所描述的操作中的一个或多个操作可以构成存储于一个或多个计算机可读介质上的计算机可读指令，所述计算机可读指令在由计算设备执行的情况下将使计算设备执行所描述的操作。描述某些或全部操作的次序不应被解读成暗指这些操作必然是依赖次序的。得益于本说明的本领域技术人员将会意识到可替换的排序。另外，将理解，并不是所有的操作都必然存在于本文提供的每个实施例中。
“计算机可读介质”是指使得能够进行信息的持久性存储的非瞬态介质和/或设备，和/或与单纯的信号传送、载波或信号本身形成对比的有形的存储装置。因而，计算机可读介质是指非信号承载介质。计算机可读介质包括硬件，诸如以适合于存储诸如计算机可读指令、数据结构、程序模块、逻辑元件/电路或其它数据之类的信息的方法或技术实现的易失性和非易失性、可拆卸和不可拆卸介质和/或存储设备。计算机可读介质的示例可以包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光学存储装置、硬盘、磁带盒、磁带、磁盘存储装置或其它磁性存储设备、或者适于存储期望的信息并且可以由计算机访问的其它存储设备、有形介质或制造品。
所属领域的普通技术人员应当理解：以上任何实施例的讨论仅为示例性的，并非旨在暗示本公开的范围(包括权利要求)被限于这些例子。在本公开的思路下，以上实施例或者不同实施例中的技术特征之间也可以进行组合，步骤可以以任意恰当的顺序实现。而且，存在如上所述的本公开的不同方面的许多其它变化，为了简明它们没有在细节中提供。因此，凡在本公开的精神和原则之内，所做的任何省略、修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (33)

  1. 一种用于信息订阅的方法，包括：
    在判定来自第一实体的请求的请求信息满足该第一实体相关的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息；
    根据所述订阅资源的关联对象获取所述事件的第二信息；以及
    向所述订阅资源的被通知方发送包含第一和第二信息的通知消息。
  2. 根据权利要求1所述的方法，其中所述订阅资源包括：所述事件通知规则、所述关联对象、以及所述被通知方的通知地址标识符。
  3. 根据权利要求1所述的方法，其中所述订阅资源包括：所述事件通知规则和所述被通知方的通知地址标识符，以及
    所述关联对象是在所述第一实体的资源的容器中创建的关联对象。
  4. 根据权利要求1-3之一所述的方法，其中所述关联对象包括关联资源或关联资源的标识，以及所述根据所述订阅资源的关联对象获取所述事件的第二信息包括：
    从所述关联资源中获取所述事件的第二信息，或
    根据所述关联资源的标识，从对应关联资源中获取所述事件的第二信息。
  5. 根据权利要求2所述的方法，其中在所述判定之前还包括：
    接收来自所述订阅资源的请求方的针对第一实体的订阅请求，所述订阅请求中包括：所述事件通知规则、所述关联资源的标识，以及所述被通知方的通知地址标识符；
    根据接收的订阅请求创建针对第一实体的所述订阅资源。
  6. 根据权利要求1-5之一所述的方法，其中所述订阅资源中还包括：通知内容类型，且所述通知内容类型的可选取值包括关联资源类型值。
  7. 根据权利要求6所述的方法，所述根据所述订阅资源的关联对象获取所述事件的第二信息包括：
    在确定所述通知内容类型为关联资源类型值后，根据所述订阅资源的关联对象获取所述事件的第二信息。
  8. 根据权利要求1-7之一所述的方法，其中第一实体为应用实体、或通用服务实体。
  9. 根据权利要求1-8之一所述的方法，其中所述请求包括创建内容实例请求或更新内容实例请求。
  10. 根据权利要求9所述的方法，还包括：
    根据第一实体发送的创建内容实例请求，在用于第一实体的资源的容器中创建一个新的内容实例，并把接收的信息存储于所述新的内容实例中。
  11. 根据权利要求2-3之一所述的方法，其中所述关联资源包括实体的资源、容器或者内容实例；
    其中，所述实体包括应用实体、或通用服务实体。
  12. 根据权利要求2-3之一所述的方法，其中所述关联资源为不同于第一实体的第二实体的资源；以及
    在所述根据所述订阅资源的关联对象获取所述事件的第二信息之前，还包括：
    接收第二实体发送的携带有所述事件的第二信息的创建内容实例请求；
    根据第二实体发送的创建内容实例请求，在第二实体的资源的容器中创建一个新的内容实例，并把所述事件的第二信息存储于所述新的内容实例中。
  13. 根据权利要求12所述的方法，其中所述事件的第一信息为事件的核心信息，所述事件的第二信息为事件的辅助信息。
  14. 根据权利要求13所述的方法，其中所述事件的核心信息为交通事故的发生信息，所述事件的辅助信息为事故车辆的位置信息；以及
    第一实体为交通事故识别应用实体，第二实体为车辆位置传感应用实体。
  15. 一种订阅服务器，包括：
    确认模块，用于在判定来自第一实体的请求的请求信息满足第一实体相关的订阅资源中的事件通知规则后，将所述请求的内容信息确认为事件的第一信息；
    获取模块，用于根据所述订阅资源的关联对象获取所述事件的第二信息；和
    发送模块，用于向所述订阅资源的被通知方发送包含所述第一和第二信息的通知消息。
  16. 根据权利要求15所述的订阅服务器，其中所述订阅资源包括：所述事件通知规则、所述关联对象、以及所述被通知方的通知地址标识符。
  17. 根据权利要求16所述的订阅服务器，还包括：
    创建模块，用于在接收到来自所述订阅资源的请求方的针对第一实体的订阅请求后，根据所述订阅请求创建第一实体的所述订阅资源；
    其中，所述订阅请求包括：所述事件通知规则、关联资源的标识、以及所述被通知方的通知地址标识符，所述关联资源的标识用以创建所述关联对象。
  18. 根据权利要求15所述的订阅服务器，其中所述订阅资源中包括：所述事件通知规则和所述被通知方的通知地址标识符，以及所述关联对象是被设置于所述第一实体的资源的容器中的关联对象。
  19. 根据权利要求18所述的订阅服务器，还包括：
    创建模块，用于在接收到来自所述订阅资源的请求方的针对第一实体的订阅请求后，根据所述订阅请求创建第一实体的所述订阅资源；
    其中，所述订阅请求包括：所述事件通知规则、以及所述被通知方的通知地址标识符。
  20. 根据权利要求15-19之一所述的订阅服务器，其中所述订阅资源中还包括：通知内容类型，且所述通知内容类型的可选取值包括关联资源类型值。
  21. 根据权利要求20所述的订阅服务器，其中所述获取模块用于在确定所述通知内容类型为关联资源类型值后，根据所述订阅资源的关联对象获取所述事件的第二信息。
  22. 根据权利要求15或16所述的订阅服务器，其中所述请求包括创建内容实例请求；以及所述订阅服务器还包括：
    接收模块，用于接收第一实体发送的创建内容实例请求，以及
    创建模块，用于根据所述创建内容实例请求在第一实体的资源的容器中创建一个新的内容实例，并把接收的信息存储于所述新的内容实例中。
  23. 根据权利要求15-22之一所述的订阅服务器，其中所述关联资源为实体的资源、容器或者内容实例；
    其中，所述实体包括应用实体或通用服务实体。
  24. 根据权利要求22所述的订阅服务器，其中所述关联资源为不同于所述第一实体的第二实体的资源；以及
    所述接收模块还用于接收第二实体发送的携带有所述事件的第二信息的创建内容实例请求；且所述创建模块还用于根据第二实体发送的创建内容实例请求，在第二实体的资源的容器中创建一个新的内容实例，并把所述事件的第二信息存储于所述新的内容实例中。
  25. 根据权利要求15-24之一所述的订阅服务器，其中所述事件的第一信息为事件的核心信息，所述事件的第二信息为事件的辅助信息。
  26. 一种订阅终端，包括：
    订阅请求模块，用于向订阅服务器发送针对第一实体的订阅请求以创建第一实体相关的订阅资源，所述订阅请求中包括：事件通知规则、以及所述订阅资源的被通知方的通知地址标识符；
    通知消息处理模块，用于接收并处理所述订阅服务器发送的通知消息，所述通知消息中包括根据第一实体发送的请求的内容信息而确认的事件的第一信息和根据所述订阅资源的关联对象获取的所述事件的第二信息。
  27. 根据权利要求26所述的订阅终端，其中所述订阅请求中还包括：关联资源的标识，用于创建所述订阅资源中的关联对象。
  28. 根据权利要求26或27所述的订阅终端，其中所述订阅请求中还包括通知内容类型，且该通知内容类型被设置为关联资源类型值。
  29. 一种信息订阅系统，包括：
    第一实体，用于发送请求；
    按照权利要求15-25之一所述的订阅服务器；和
    订阅终端，其作为所述订阅资源的被通知方，用于接收并处理所述通知消息。
  30. 根据权利要求29所述的系统，其中第一实体为应用实体、或通用服务实体。
  31. 一种信息订阅系统，包括：
    第一实体，用于发送请求；
    按照权利要求15-25之一所述的订阅服务器；和
    根据权利要求26-28之一所述的订阅终端，其作为所述订阅资源的被通知方，用于接收并处理所述通知消息。
  32. 一种计算机可读介质，其上存储有计算机可读指令，所述计算机可读指令在由计算设备执行时使所述计算设备执行根据权利要求1-14之一所述的方法。
  33. 一种计算设备，包括：
    一个或多个处理器；以及
    计算机可读存储介质，其上存储有多个指令，所述多个指令响应于被所述一个或多个处理器执行而使所述一个或多个处理器执行根据权利要求1-14之一所述的方法。
PCT/CN2019/074122 2018-05-18 2019-01-31 订阅服务器、订阅终端及信息订阅方法和系统 WO2019218728A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020207035829A KR102631288B1 (ko) 2018-05-18 2019-01-31 가입 서버, 가입 단말기, 정보 가입 방법, 및 시스템
US17/054,617 US11470155B2 (en) 2018-05-18 2019-01-31 Subscription server, subscription terminal, information subscription method and system
EP19803453.0A EP3799458A4 (en) 2018-05-18 2019-01-31 SUBSCRIPTION SERVER, SUBSCRIPTION TERMINAL, INFORMATION SUBSCRIPTION METHOD AND SYSTEM
JP2020563768A JP7420743B2 (ja) 2018-05-18 2019-01-31 購読サーバ、購読端末、情報購読方法及びシステム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810479229.6A CN110505591B (zh) 2018-05-18 2018-05-18 订阅服务实体、订阅终端及信息订阅方法和系统
CN201810479229.6 2018-05-18

Publications (1)

Publication Number Publication Date
WO2019218728A1 true WO2019218728A1 (zh) 2019-11-21

Family

ID=68539406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074122 WO2019218728A1 (zh) 2018-05-18 2019-01-31 订阅服务器、订阅终端及信息订阅方法和系统

Country Status (6)

Country Link
US (1) US11470155B2 (zh)
EP (1) EP3799458A4 (zh)
JP (1) JP7420743B2 (zh)
KR (1) KR102631288B1 (zh)
CN (1) CN110505591B (zh)
WO (1) WO2019218728A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113498051B (zh) * 2020-03-18 2023-01-03 维沃移动通信有限公司 一种订阅网络事件的方法和网络功能
CN113656683A (zh) * 2021-07-12 2021-11-16 北京旷视科技有限公司 订阅数据推送方法、装置、系统、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459908A (zh) * 2007-12-13 2009-06-17 华为技术有限公司 一种业务订阅方法、系统、服务器
CN101742475A (zh) * 2008-11-12 2010-06-16 华为技术有限公司 订阅和通知的方法、装置和系统
CN107566437A (zh) * 2016-07-01 2018-01-09 大唐移动通信设备有限公司 信息传输方法及装置
CN107666432A (zh) * 2016-07-29 2018-02-06 京东方科技集团股份有限公司 进行通知的方法、装置和系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7275250B1 (en) * 2001-05-01 2007-09-25 Microsoft Corporation Method and apparatus for correlating events
US20040002958A1 (en) * 2002-06-26 2004-01-01 Praveen Seshadri System and method for providing notification(s)
US7457914B2 (en) * 2005-03-25 2008-11-25 Emc Corporation Asynchronous event notification
KR100960257B1 (ko) * 2008-01-24 2010-06-01 홍유식 무선 주파수 인식 시스템과 다중 센서들을 이용한교통사고정보 통보장치 및 통보방법
US8260864B2 (en) * 2008-02-13 2012-09-04 Microsoft Corporation Push mechanism for efficiently sending aggregated data items to client
US20100100626A1 (en) * 2008-09-15 2010-04-22 Allen Stewart O Methods and apparatus related to inter-widget interactions managed by a client-side master
CN101854338B (zh) * 2009-03-31 2014-02-26 国际商业机器公司 订户设备及其订阅管理方法、实时通信方法和系统
CN104995889B (zh) * 2013-02-19 2019-01-01 Lg电子株式会社 用于修改m2m服务设置的方法及其装置
CN105580327B (zh) 2013-09-27 2018-12-18 Lg电子株式会社 用于在m2m系统中传送通知消息的方法及其装置
CN106790676B (zh) * 2013-12-05 2020-07-07 华为技术有限公司 订阅通知的实现方法和装置
JP6370547B2 (ja) * 2013-12-17 2018-08-08 株式会社日立システムズ 広域管理システム、広域管理装置、建物管理装置、広域管理方法、センサ情報送信方法、データ取得方法、およびプログラム
CN105228111A (zh) * 2014-06-13 2016-01-06 中兴通讯股份有限公司 资源订阅处理方法及装置
GB2532490B (en) * 2014-11-21 2017-02-22 Ibm Publish/subscribe messaging using message structure
JP6524264B2 (ja) * 2015-05-20 2019-06-05 コンヴィーダ ワイヤレス， エルエルシー 効率を高めるためにサービス層サブスクリプションおよび通知を分析しグループ化する方法および装置
KR102116401B1 (ko) 2015-11-16 2020-05-29 콘비다 와이어리스, 엘엘씨 M2m 서비스 계층에 대한 교차 리소스 가입
US10135940B2 (en) * 2015-12-04 2018-11-20 Oracle International Corporation Subscribing to event notifications using object instances
CN114245351A (zh) * 2016-07-14 2022-03-25 康维达无线有限责任公司 订阅和通知服务
US10666690B2 (en) * 2016-07-27 2020-05-26 Visa International Service Association Resource-related content distribution hub
WO2018182065A1 (ko) * 2017-03-30 2018-10-04 전자부품연구원 M2m 시스템에서 다중 리소스 구독 연관 방법
CN106973118B (zh) 2017-05-12 2021-04-27 京东方科技集团股份有限公司 生成和订阅通知的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459908A (zh) * 2007-12-13 2009-06-17 华为技术有限公司 一种业务订阅方法、系统、服务器
CN101742475A (zh) * 2008-11-12 2010-06-16 华为技术有限公司 订阅和通知的方法、装置和系统
CN107566437A (zh) * 2016-07-01 2018-01-09 大唐移动通信设备有限公司 信息传输方法及装置
CN107666432A (zh) * 2016-07-29 2018-02-06 京东方科技集团股份有限公司 进行通知的方法、装置和系统

Also Published As

Publication number Publication date
JP7420743B2 (ja) 2024-01-23
CN110505591B (zh) 2022-09-30
US11470155B2 (en) 2022-10-11
JP2021524089A (ja) 2021-09-09
CN110505591A (zh) 2019-11-26
EP3799458A1 (en) 2021-03-31
KR102631288B1 (ko) 2024-01-31
KR20210008525A (ko) 2021-01-22
US20210194967A1 (en) 2021-06-24
EP3799458A4 (en) 2022-03-02

Similar Documents

Publication Publication Date Title
CN108353094B (zh) 用于m2m服务层的跨资源订阅
KR102095436B1 (ko) 서비스 계층에서의 요청 처리
WO2019196813A1 (zh) 一种订阅服务的方法及装置
US11677850B2 (en) Method, apparatus and system for notification
WO2019214343A1 (zh) 订阅更新方法、设备及系统
US20170126828A1 (en) Sending Method and Apparatus and Computer Storage Medium of Notification Message
WO2019109923A1 (zh) 消息处理方法及系统、存储介质、电子设备
JP2007028117A (ja) 情報交換システム、管理サーバ、端末装置及びそれらに用いるネットワーク負荷軽減方法
WO2015123890A1 (zh) 一种m2m中信息处理的方法和装置
WO2019218728A1 (zh) 订阅服务器、订阅终端及信息订阅方法和系统
EP3174318B1 (en) Method for realizing resource attribute notification, and common service entity
WO2017181863A1 (zh) 资源访问控制方法及装置
US10219133B2 (en) Notification message transmission method and device, and computer storage medium
WO2016065842A1 (zh) M2m群组及其通告资源创建、信息交互方法和存储介质
KR20200005492A (ko) 리소스 관리 방법 및 장치
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
WO2015117446A1 (zh) 控制资源变更通知消息发送方法及装置
WO2015117342A1 (zh) 一种通知消息的发送方法、装置和系统
CN106937240B (zh) 一种获取资源的方法和装置
WO2017136979A1 (zh) 一种远程访问的实现方法、装置和系统
CN110875945B (zh) 用于在通用服务实体上进行任务处理的方法、装置和介质
WO2020029671A1 (zh) 一种直连通信的方法、amf、接入网功能实体及终端
WO2017084584A1 (zh) 一种资源发现的方法及装置
WO2018082574A1 (zh) 一种信息发送方法、单元和系统
WO2016074455A1 (zh) 组资源更新处理方法、装置、系统及cse

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020563768

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207035829

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019803453

Country of ref document: EP

Effective date: 20201218