WO2021143834A1 - 群组更新方法、消息发送方法及装置 - Google Patents

群组更新方法、消息发送方法及装置 Download PDF

Info

Publication number
WO2021143834A1
WO2021143834A1 PCT/CN2021/072130 CN2021072130W WO2021143834A1 WO 2021143834 A1 WO2021143834 A1 WO 2021143834A1 CN 2021072130 W CN2021072130 W CN 2021072130W WO 2021143834 A1 WO2021143834 A1 WO 2021143834A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
notification
target
location
attribute
Prior art date
Application number
PCT/CN2021/072130
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 KR1020227020155A priority Critical patent/KR20220126288A/ko
Priority to US17/791,957 priority patent/US20230053967A1/en
Priority to EP21741956.3A priority patent/EP4092961A4/en
Publication of WO2021143834A1 publication Critical patent/WO2021143834A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1845—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast broadcast or multicast in a specific location, e.g. geocast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • 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/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • This application relates to the technical field of dynamic group processing, and in particular to a group update method, message sending method and device.
  • a group is a combination of a certain type of things with the same characteristics, which can exist in many ways, such as design software, chat software, social networking sites, and so on. Each group will set a certain theme and related organizational rules.
  • the established groups are usually static groups, and users are required to create groups based on the static member list.
  • users When adding group members, users need to add them manually.
  • the user When a group is created in a certain area, the user is required to update the group manually, and the group cannot be dynamically updated based on the location of the group members.
  • the manual method of the user will cause the group update delay, and also increase the workload and cost of group maintenance.
  • the present application provides a group update method, message sending method and device to at least partially solve the problems in the prior art.
  • the present application discloses a group update method, including: obtaining a location group for a target area; obtaining a dynamic update time of the location group; at each time determined according to the dynamic update time Point, obtain the target position of the target group object in the position group, and query whether there is a business object that does not belong to the position group in the target area; and update the target position according to the obtained target position and the query result Target group objects in the location group.
  • updating the target group object in the location group according to the acquired target location and the query result includes: in the case that the target location is outside the target area, from within the location group Eliminate the target group object.
  • updating the target group object in the location group according to the obtained target location and the query result including: in the case that there are business objects that do not belong to the location group in the target area, reset all the objects in the location group.
  • the business object is added to the location group.
  • obtaining a location group for the target area includes: receiving a first group resource creation request; obtaining a group attribute according to the first group resource creation request; and creating a group according to the group attribute, To obtain a location group for the target area.
  • obtaining a location group for the target area includes: receiving a second group resource creation request; creating an initial group according to the second group resource creation request; receiving a group update request; and according to the group
  • the group update request updates the attributes of the initial group to obtain a location group for the target area.
  • the group attribute includes at least one of dynamic update time, update duration, target area, location-related attributes, dynamic update attributes, and dynamic update notification attributes.
  • the method further includes: acquiring the update duration of the location group; stopping when the duration from the point in time when the location group is obtained to the current point in time is greater than or equal to the update duration An update to the target group object in the location group.
  • the method further includes: obtaining a dynamic update notification attribute of the location group; and determining that a message notification is to be sent to at least one of the target group object and the business object according to the dynamic update notification attribute In the case of sending a message notification to at least one of the target group object and the business object.
  • the present application discloses a message sending method, including: obtaining an event notification judgment standard of a subscription resource, and determining a target attribute to be monitored according to the event notification judgment standard; in the attribute value of the target attribute When a change occurs, obtain the changed attribute value of the target attribute; in the case that the notification mode is the difference notification mode, construct a difference notification message according to the changed attribute value; and send the difference notification message .
  • the method further includes: before obtaining the subscription resource event notification judgment criterion, receiving a subscription request sent by a subscriber corresponding to the subscription resource; and creating or updating the operation attribute of the subscription resource according to the subscription request.
  • the operation attributes include event notification judgment criteria, notification content type, and notification mode type, where the notification mode type includes any one of a difference notification mode and a conventional notification mode.
  • the method further includes: obtaining the notification content type and notification mode type of the subscription resource; and determining whether the notification mode is a differential notification mode according to the notification content type and the notification mode type.
  • determining whether the notification method is a differential notification method according to the notification content type and the notification method type includes: verifying the notification content type; when the notification content type is a differential notification In the case of content, it is determined that the notification method is a differential notification method; when the notification content type is non-disparity notification content, the notification method type is verified; and when the notification method type is In the case of the difference notification mode, it is determined that the notification mode is the difference notification mode.
  • determining whether the notification mode is a differential notification mode according to the notification content type and the notification mode type and further includes: in the case that the notification mode type is a regular notification mode, according to the post-change notification mode The attribute value of constructs a regular notification message.
  • constructing a difference notification message according to the changed attribute value includes: when the changed attribute value only includes an incremental attribute value, including the difference notification message that characterizes the Incremental identification parameter of the incremental attribute value; in the case that the changed attribute value only contains the decrement attribute value, the difference notification message includes the decrement identification parameter that characterizes the decrement attribute value; In the case where the changed attribute value includes both an increment attribute value and a decrement attribute value, the difference notification message includes an increment identification parameter characterizing the increment attribute value and the decrement The decrement of the attribute value identifies the parameter.
  • the difference notification message includes an increment attribute value, a decrement attribute value, an increment identification parameter characterizing the increment attribute value, and a decrement identification parameter characterizing the decrement attribute value.
  • the present application discloses a group update device, including: a location group acquisition module, used to acquire a location group for a target area; a dynamic update time acquisition module, used to acquire information about the location group Dynamic update time; the location object acquisition module is used to acquire the target location of the target group object in the location group at each time point determined according to the dynamic update time, and query whether there is in the target area Business objects that do not belong to the location group; and a group object update module configured to update the target group objects in the location group according to the acquired target location and the query result.
  • the present application discloses a message sending device, including: a target attribute determination module, configured to obtain the event notification judgment standard of the subscription resource, and determine the target attribute to be monitored according to the event notification judgment standard;
  • the value acquisition module is used to obtain the changed attribute value of the target attribute when the attribute value of the target attribute changes;
  • the difference notification message construction module is used to when the notification mode is the difference notification mode , Constructing a difference notification message according to the changed attribute value; and a difference notification message sending module, configured to send the difference notification message.
  • the present application discloses an electronic device including: a memory storing a computer program; and a processor configured to execute the computer program to implement the above group update method or the above message sending method .
  • the present application discloses a computer-readable storage medium storing computer instructions.
  • the computer instructions When the computer instructions are executed by the processor of an electronic device, the electronic device can execute the above group update method, or, the above Message sending method.
  • this application includes the following advantages:
  • the target location of the target group object in the location group is obtained based on the query, and whether there is a business object that does not belong to the location group in the target area, and the location is updated according to the obtained target location and the query result
  • the target group object in the group realizes the dynamic real-time update of the group based on the position of the object in the target area, avoids the problem of group update delay, and reduces the workload of group maintenance and reduces maintenance cost.
  • FIG. 1 shows a flowchart of the steps of a group update method provided in Embodiment 1 of the present application
  • FIG. 2 shows a schematic diagram of creating a location group according to an embodiment of the present application
  • FIG. 3 shows a schematic diagram of a group creation update notification provided by an embodiment of the present application
  • FIG. 4 shows a flowchart of the steps of a method for sending a message provided in the second embodiment of the present application
  • FIG. 5 shows a schematic diagram of a difference notification message provided by an embodiment of the present application
  • FIG. 6 shows a schematic structural diagram of a group update apparatus provided in Embodiment 3 of the present application.
  • FIG. 7 shows a schematic structural diagram of a message sending apparatus provided in Embodiment 4 of the present application.
  • the group update method may specifically include the following steps:
  • step 101 Obtain a location group for the target area.
  • the target area refers to the area where the location group within its range needs to be dynamically updated, such as "xx district in xx city", or "xx road in xx district in xx city”.
  • the target area may be determined according to business requirements, which is not limited in the embodiment of the present application.
  • the location group refers to a pre-acquired group that needs to be dynamically updated for the target area, and the location group contains objects in the target area.
  • the location group may be created according to the received group resource creation request. When creating a location group, you can obtain the object to be added from the target area, and add the object to be added to the location group to obtain the location group related to the location. According to the embodiment, the location group can also be obtained by updating according to the initial group created in advance.
  • FIG. 2 shows a schematic diagram of creating a location group according to an embodiment of the present application
  • FIG. 3 shows a schematic diagram of a group creation update notification provided by an embodiment of the present application.
  • the following is a combination of FIG. 2 and FIG. 3 and the following The specific implementation mode describes in detail the creation process of the location group.
  • the foregoing step 101 may include:
  • Sub-step A1.1 Receive a group resource creation request (first group resource creation request).
  • a group resource creation request refers to a request for creating a group. As shown in Figure 3, the group resource creation request can be sent by the application entity (AE) to the common service entity (CSE).
  • AE application entity
  • CSE common service entity
  • the group resource creation request may be a group resource creation request that does not contain the location function description information of the target area, that is, the group resource creation request can be used to create a location-independent group.
  • the group resource creation request may also create a group that is related to the location, but the location is different from the target area.
  • the group resource creation request may also be a group resource creation request containing the location function description information of the target area.
  • the AE can carry location function description information (ie target area) in the group resource creation request.
  • the group resource creation request is sent to the CSE.
  • the generated group resource creation request may also include a location-related attribute, that is, locationRelated, and this attribute value represents whether the group of resources are location-related.
  • this attribute value is TRUE, it means that the group to be created is location-related; when this attribute value is FALSE, it means that the group to be created is not location-related.
  • the group to be created is not location-related by default. If the group to be created is a location-related group, the group resource creation request should include location function description information (ie, target area), namely locationTargetArea, and this attribute value represents the geographic information of the corresponding target area. This attribute value is required when the locationRelated attribute value is TRUE.
  • location function description information ie, target area
  • locationTargetArea locationTargetArea
  • Sub-step A1.2 Obtain group attributes according to the group resource creation request.
  • the group attributes include dynamic update time (locationUpdatePeriod), update duration (dynamicUpdateDuration), target area (locationTargetArea), location-related attributes (locationRelated), dynamic update attributes (dynamicUpdate), and dynamic update notification attributes (dynamicUpdateNotification). At least one of.
  • Sub-step A1.3 Create a group according to the group attribute to obtain a location group for the target area.
  • the object to be added may be obtained, and the object to be added is an object located in the range of the target area determined by the attribute locationTargetArea.
  • the object is added to the created location group, and the value of each attribute specified in the group resource creation request is added to the location group.
  • the nodes Node1 to Node5 belong to the same target domain, such as a domain managed by the node Node0.
  • the group established in this way can adapt to the scene in the domain. Multiple group objects can be obtained from the target area. Determine the node that meets the requirements from each node as the group object. As still shown in FIG.
  • the nodes Node1, Node2, and Node3 belong to the same target area and can be added to the same location group for the target area.
  • Nodes Node4 and Node5 do not belong to the above target area and cannot be added to the group when creating a location group.
  • the foregoing step 101 may include:
  • Sub-step A2.1 Receive a group resource creation request (a second group resource creation request).
  • the second group resource creation request does not include group attributes, that is, it does not include dynamic update time (locationUpdatePeriod), update duration (dynamicUpdateDuration), target area (locationTargetArea), location-related attributes (locationRelated), and dynamic update attributes (dynamicUpdate). ), any of the dynamic update notification attributes (dynamicUpdateNotification).
  • the initial group may be created according to the second group resource creation request.
  • Sub-step A2.2 Create an initial group according to the second group resource creation request.
  • the initial group may be a normal group, that is, the initial group may be a group whose location is not related.
  • Group objects can be added to the created initial group, that is, the created initial group contains group members.
  • the group objects in the initial group may have different object attributes from the aforementioned group attributes.
  • the created initial group can also be an empty group, that is, no group object is added to the initial group.
  • the initial group may also be a pre-existing group, that is, a group created at a certain time before, which is not limited in this application.
  • Sub-step A2.3 Receive a group update request.
  • the group update request can be sent by the AE to the CSE.
  • the group update request includes the group attribute to be updated. For example, it may include at least one of dynamic update time (locationUpdatePeriod), update duration (dynamicUpdateDuration), target area (locationTargetArea), location-related attributes (locationRelated), dynamic update attributes (dynamicUpdate), and dynamic update notification attributes (dynamicUpdateNotification) .
  • Sub-step A2.4 Update the attributes of the initial group according to the group update request to obtain the location group for the target area.
  • updating the attribute value of the initial group attribute can have two meanings:
  • the original attribute value of the attribute dynamicUpdate-Notification is false, and the original attribute value of dynamicUpdate-Notification can be updated to true by updating the original attribute value.
  • the created initial group does not include the attribute dynamicUpdate.
  • the attribute value (empty) of the undefined attribute dynamicUpdate can be updated to the attribute value true.
  • the group resource creation request can be responded to.
  • the AE that sends the group resource creation request and the target node application (for example, AE1) included in the location group respectively return a response that satisfies the establishment of a dynamic group, which carries group resource information.
  • the initial group can be updated to a location-related location group for the target area.
  • the group update method may further include:
  • Step B1 Obtain the update duration corresponding to the location group.
  • the update duration refers to the duration of the dynamic update of the location group after the location group is obtained, that is, after the location group is successfully created.
  • the dynamicUpdateDuration attribute value set for the location group this attribute value represents the duration of the dynamic update of the group of resources on the target area. This attribute value is valid only when dynamicUpdate is TRUE.
  • the duration of dynamic update of the location group such as 3 days, 8 days, etc.
  • the value of the update duration may be determined according to business requirements, which is not limited in the embodiment of the present application.
  • the update duration may also be the update duration set when the initial group is updated to the location group, or may be the update duration set when the initial group is created.
  • the update duration may be determined according to business requirements, which is not limited in the embodiment of the present application.
  • the update duration corresponding to the location group can be obtained.
  • step B2 After obtaining the update duration corresponding to the location group, step B2 is executed.
  • Step B2 Stop the dynamic update operation of the target group object in the position group when the time period from the time point when the position group is obtained to the current time point is greater than or equal to the update duration time .
  • the update operation on the group objects in the location group is continued.
  • the update operation includes performing operations such as adding or subtracting group objects based on the position.
  • the update duration can be dynamicUpdateDuration
  • Hosting CSE can decide whether to update dynamic group members according to the value of the dynamicUpdateDuration attribute:
  • step 102 obtain the dynamic update time corresponding to the location group.
  • the dynamic update time refers to the time when the location group is dynamically updated.
  • one or more time points are determined according to the dynamic update time, such as 12:00, 12:30, 13:00, 13:30, and so on.
  • the dynamic update time can be started after the location group is obtained, at multiple time points at a set time interval, for example, the target group object is added to the location group from 12:00, every 20 minutes Perform a location acquisition of the target group object, that is, 12:20, 12:40, 13:00, etc.
  • the dynamic update time may be the update time set when the initial group is updated to the location group, or may be the initial dynamic update time set when the initial group is created.
  • the dynamic update time may be determined according to business requirements, which is not limited in the embodiment of the present application.
  • the group update attribute of the location group can also be set, which will be described in detail with reference to the following specific implementation manners.
  • the foregoing step 102 may include:
  • Sub-step C1 Obtain dynamic update attributes of the location group.
  • the dynamic update attribute of the group refers to, for example, dynamicUpdate.
  • the dynamic update attribute of the location group can be obtained, and then the sub-step C2 is executed.
  • Sub-step C2 when the dynamic update attribute is TRUE, obtain the dynamic update time.
  • step 103 at each time point determined according to the dynamic update time, obtain the target position of the target group object in the position group, and query whether there is an object in the target area that does not belong to The business object of the location group.
  • the target group object refers to the object that has been added to the location group related to the location.
  • the position of the target group object can be changed.
  • the target group object can be any of users, movable entities, etc., and can be determined according to business requirements.
  • the target position refers to the position of the target group object at the point in time when the position is acquired.
  • a business object refers to an object that is located in the target area, has the same type as the group object added by the location group, and is related to the location that has not been added to the location group.
  • the target location of the target group object in the location group can be acquired, and whether there is a location-related business object that does not belong to the location group in the target area.
  • the target position may be acquired by satellite positioning.
  • the GPS Global Positioning System
  • other navigation devices carried on the target group object are in the on state, and furthermore, it can realize the mobile Real-time positioning of the terminal to obtain the target position of the target group object at the position acquisition time point.
  • the target position may be the position sent by the target group object to the CSE.
  • a message may be sent to the target group object at a certain time before the position acquisition time point, so as to be the target in the group.
  • Position sharing between group objects After receiving the reminder message, the target group object can share the location with the CSE as the target location.
  • the method of obtaining the target location may be determined according to business requirements, which is not limited in the embodiment of the present application.
  • real-time monitoring of the target area can be used to monitor whether there are business objects in the target area.
  • the embodiment of the application is not limited to this.
  • other methods may be used to query whether there is a business object in the target area, which may be determined according to business requirements, which is not limited by the embodiment of the application.
  • step 104 update the target group objects in the location group according to the acquired target location and the query result. According to an embodiment, it may be determined whether the target group object needs to be deleted from the position group according to the acquired target position. According to an embodiment, it may be determined whether a new target group object needs to be added to the location group according to the query result.
  • step 104 may further include at least one of step 104.1 and step 104.2.
  • Step 104.1 When the target position is outside the target area, exclude the target group object from the position group.
  • Step 104.2 If there is a business object that does not belong to the location group in the target area, add the business object to the location group.
  • the target position of the target group object after the target position of the target group object is obtained, it can be determined whether the target position is in the target area, and when the target position is within the target area, the target group object is not processed.
  • the target group object when it is determined that the target group object is outside the target area, the target group object may be excluded from the location group. If there are business objects that do not belong to the location group in the target area, the business objects can be added to the location group. Specifically, it can be divided into the following four situations:
  • the target location is outside the target area, and there are business objects in the target area
  • the target group object can be excluded from the location group, and the business object can be added to the location group.
  • the target location is within the target area, and there are business objects in the target area
  • the target group object is not processed, and the business pair object is added to the location group.
  • the target location is outside the target area, and there is no business object in the target area
  • the target group object can be excluded from the location group without processing the business object.
  • the target location is within the target area, and there is no business object in the target area
  • the embodiments of the present application can implement dynamic updating of group members, and reduce the workload of group administrators for manually adding group members or removing group members.
  • the method may further include:
  • Step D1 Obtain the first change notification attribute corresponding to the location group preset (for example, set by AE).
  • a change notification attribute is set for the location group in advance, such as dynamicUpdateNotification, and the dynamicUpdateNotification can be used to determine whether to send a corresponding notification to the changed member.
  • the preset first change notification attribute corresponding to the location group may be obtained.
  • Step D2 When it is determined that a message notification needs to be sent based on the first change notification attribute, a first notification message of the target object is generated, and/or a second notification message of the business object is generated.
  • Step D3 Send the first notification message to the target group object; and/or send the second notification message to the business object.
  • the first notification message refers to a notification message generated to send to the target group object after the target group object is removed from the location group.
  • the first notification message can be used to notify the target group object that the target group object has been removed from the location group .
  • the second notification message refers to a notification message generated after the business object is added to the location group for sending to the business object, and the second notification message can be used to notify that the business object has been added to the location group.
  • the first notification message of the target object and/or the second notification message of the business object can be generated.
  • the method may further include:
  • Step E1 Obtain the preset second change notification attribute corresponding to the location group
  • Step E2 When it is determined that there is no need to send a message notification based on the second change notification attribute, cancel sending the notification message to the target object and/or the business object.
  • the group update method provided by the embodiment of the present application is based on obtaining the target position of the target group object in the position group, and querying whether there is a business object that does not belong to the position group in the target area, and according to the obtained target position and The query result updates the target group object in the location group, which realizes the dynamic real-time update of the group based on the position of the object in the target area, avoids the problem of group update delay, and reduces the workload of group maintenance , Reduce maintenance costs.
  • the message sending method may specifically include the following steps:
  • step 201 Obtain the event notification judgment standard of the subscription resource, and determine the target attribute to be monitored according to the event notification judgment standard.
  • the subscription resource may be a resource pre-subscribed by the subscriber.
  • the target attribute refers to the attribute that needs to be monitored by the subscriber in the subscription resource and can trigger the birth of a matching event.
  • the CSE stores attribute information about the application entities AE1 and AE2, and the application entity AE as a subscriber can subscribe to the CSE for at least a part of the attribute information about the application entities AE1 and AE2, that is, subscribe resource.
  • the AE can specify the attribute that needs to be monitored in the subscription resource and can trigger the birth of the matching event, that is, the target attribute.
  • eventNotificationCriteria In the process of creating the target attribute, you can set an event notification judgment criterion for each attribute in advance, that is, eventNotificationCriteria.
  • the event notification judgment standard indicates whether to monitor the attribute.
  • each attribute (eventNotificationCriteria/attribute) in the subscription resource can be checked to obtain the value of the event notification judgment criterion corresponding to each attribute.
  • eventNotificationCriteria is not set in an attribute, it can be regarded as processing the attribute according to the default strategy. For example, no monitoring operation is performed on the attribute, and the change of the attribute value of the attribute will not trigger the birth of the matching event. This situation is not considered.
  • the setting of the operation attribute corresponding to the target attribute can be performed after receiving the subscription request sent by the subscriber.
  • the event notification judgment criteria ie eventNotificationCriteria
  • notification content type ie notificationContentType
  • notification method type corresponding to the target attribute
  • the notification mode type may include any one of diff notification (diffNotification) and regular notification.
  • the above creation or update includes the following two situations:
  • the target attribute defines any of the three operation attributes eventNotificationCriteria, notificationContentType, and diffNotification, when at least one of them needs to be updated, the corresponding operation attribute can be updated according to the subscription request of the subscriber .
  • the target attribute defines the operation attribute notificationContentType
  • the notificationContentType after receiving the subscription request from the subscriber, it is determined that the notificationContentType needs to be updated according to the subscription request, and then the notificationContentType of the target attribute can be updated.
  • the target attribute that needs to be monitored can be determined according to the value of the event notification criterion for each attribute. For example, if eventNotificationCriteria/attribute is set, the attribute specified by the attribute will be monitored and verified according to the attribute value of the attribute specified by the attribute. If the verification succeeds, it is called the birth of a matching event; if the eventNotificationCriteria/ attribute is set, all changes in the attribute value of the target attribute will trigger the birth of a matching event.
  • step 202 when the attribute value of the target attribute is changed, the changed attribute value of the target attribute is acquired.
  • the changed attribute value of the target attribute may be only the attribute value increased by the target attribute, or only the attribute value decreased by the target attribute, or the attribute value increased and decreased at the same time for the target attribute, which can be based on actual conditions. To be sure, the embodiments of the present application do not impose restrictions on this.
  • the changed attribute value of the target attribute can be obtained. For example, if the target attribute increases attribute value A and attribute value B, then attribute value A and attribute value B are used as the changed attribute value; if the target attribute decreases attribute value A and attribute value C, then attribute value A and The attribute value C is used as the changed attribute value; if the target attribute increases the attribute value A and decreases the attribute value D, then the attribute value A and the attribute value D are taken as the changed attribute value.
  • step 203 in the case where the notification mode is the difference notification mode, a difference notification message is constructed according to the changed attribute value.
  • the notification method indicates the method used to send the notification message.
  • the notification method can be determined according to the definition of the operation attribute in the subscription request sent by the subscriber.
  • the notification method may include the difference notification method and the conventional notification method.
  • the purpose of this application is to describe the difference notification method, and the conventional notification method will not be described in detail.
  • the notification method corresponding to the target attribute can be verified and obtained. Specifically, it can be described in detail in conjunction with the following specific implementation methods.
  • the foregoing step 203 may include:
  • Sub-step F1 Obtain the notification content type and notification mode type of the subscription resource.
  • Sub-step F2 Determine whether the notification mode corresponding to the target attribute is a difference notification mode according to the notification content type and the notification mode type.
  • step F2 may further include:
  • Substep F2.1 Check the notification content type.
  • Sub-step F2.2 In a case where the notification content type is differential notification content, determine that the notification mode is a differential notification mode.
  • Sub-step F2.3 In the case that the notification content type is non-difference notification content, check the notification mode type.
  • Sub-step F2.4 In a case where the notification mode type is a differential notification mode, determine that the notification mode is a differential notification mode.
  • the notification content type refers to the content to which the notification message is generated, that is, notificationContentType.
  • notificationContentType can include five types:'Modified Attributes','All Attributes','ResourceID','Trigger Payload', and'Modified Difference'. Different types can constitute different notification content:
  • 'Modified Attributes' corresponds to only passing the changed attribute value information
  • All Attributes' corresponds to the value information of all attributes of the transfer resource
  • 'ResourceID' corresponds to only the resource ID involved
  • Trigger Payload' corresponds to the transmission of trigger payload information
  • 'Modified Difference' corresponds to only passing the change information of the changed attribute value.
  • the notification method type refers to the type of notification message sent to the subscriber when the target attribute changes its value.
  • the notification content type of the target attribute can be verified, and when the notification content type is the difference notification type, the difference notification is performed.
  • the notification method type of the target attribute is verified, and when the notification method type is the difference notification method, a difference notification is performed.
  • the difference notification method refers to a method of generating a difference notification message to send a notification to the subscriber.
  • the corresponding difference notification message can be constructed according to the changed attribute value.
  • the difference notification message may include an increment attribute value, a decrement attribute value, an increment identification parameter representing the increment attribute value, and a decrement identification parameter representing the decrement attribute value.
  • the difference notification message can be described in detail as follows in conjunction with FIG. 5.
  • a difference notification message can be constructed, that is, m2m: notification.
  • the generated notification message may contain the identification parameter of the attribute value, that is, the notification message contains "diffState". Specifically, it can be divided into an increment identification parameter, a decrement identification parameter, and the like.
  • the difference notification message can be sent to the subscriber, and then the subscriber can update the attributes of the subscription resource according to the difference notification message, that is, Update to attributes of the subscribed-to shown in Figure 5 resource.
  • the changed attribute value can include at least one of an incremental attribute value and a decrement attribute value. Then, a corresponding difference notification message can be constructed according to the specific incremental attribute value and the decrement attribute value. Specifically, it can be combined with the following The specific implementation is described in detail.
  • a difference notification message corresponding to the increase in the incremental attribute value is constructed, and the difference notification message includes There is an increment identification parameter that characterizes the increment attribute value.
  • a difference notification message corresponding to the increased incremental attribute value can be constructed, and the difference notification message contains the increase of the characteristic incremental attribute value.
  • a difference notification message corresponding to the decrement attribute value is constructed, and the difference notification message includes There is a decrement identification parameter that characterizes the decrement attribute value.
  • the difference notification message includes an increment identification parameter that characterizes the increment attribute value and a decrement identification parameter that characterizes the decrement attribute value.
  • a difference notification message that increases the increment attribute value and decreases the decrement attribute value can be constructed, and the difference notification message contains the characteristic increment attribute Value increment identification parameters and decrement identification parameters representing decrement attribute values, such as group members increase F and decrease C.
  • step 204 send the difference notification message.
  • the difference notification message may be sent to the subscriber corresponding to the target subscription resource.
  • the subscriber refers to the business party that has subscribed to the attribute value change of the target attribute to receive the notification message.
  • the subscriber can be a certain user or a certain business platform. Specifically, it can be determined according to business requirements.
  • the subscriber here is a subscriber in a broad sense, including not only the AE that subscribes to the CSE for resources and specifies the target attribute to be monitored, but also includes each group member included in the group.
  • the node AE1 in the group member can also subscribe to the CSE for the resource to receive notification messages.
  • the difference notification message After obtaining the difference notification message, the difference notification message can be sent to the subscriber, so that the difference notification of the message can be realized.
  • the embodiments of the present application can be applied to uniformly manage electronic tags in a specific area. For example, in terms of subscription notifications, you can use differential notifications to optimize the size of the data package. For example, for the merchandise push scenario in the supermarket, the supermarket has a wide variety of merchandise, and there are many types of merchandise. Subscription notifications are used to push newly-listed merchandise. In this scenario, it is very suitable to use differential notifications to notify them. By subscribing to the product catalog in the smart retail server, you can get more intuitive information about new products.
  • the message sending method provided in the embodiment of the application determines the target attribute by obtaining the subscribed resource event notification judgment criterion, and constructs the corresponding difference notification message according to the obtained changed attribute value of the target attribute, and sends the difference notification message Sent to the subscriber corresponding to the target attribute.
  • the embodiment of the present application can realize the difference notification for the target attribute change, can make the subscriber know the attribute value of the attribute change in time, and improve the subscriber's perception.
  • the group update apparatus 300 may specifically include the following modules:
  • the location group obtaining module 310 is configured to obtain a location group for the target area.
  • the dynamic update time obtaining module 320 is configured to obtain the dynamic update time of the location group.
  • the location object acquiring module 330 is configured to acquire the target location of the target group object in the location group according to each time point determined by the dynamic update time, and query whether there is any object in the target area that does not belong to the The business object of the location group.
  • the group object update module 340 is configured to update the target group object in the position group according to the obtained target position and the query result.
  • the group object update module 340 includes:
  • the object culling unit is configured to remove the target group object from the location group when the target location is outside the target area.
  • the group object update module 340 further includes:
  • the object adding unit is configured to add the business object to the location group when there is a business object that does not belong to the location group in the target area.
  • the location group obtaining module 310 includes:
  • the request receiving unit is configured to receive the first group resource creation request, or to receive the second group resource creation request and the group update request.
  • the group attribute obtaining unit is configured to obtain the group attribute according to the first group resource creation request and the group update request.
  • the location group creating unit is used to create a group according to the group attribute to obtain a location group for the target area.
  • the initial group creation unit is used for the second group resource to create an initial group.
  • the initial group update unit is configured to update the attributes of the initial group according to the group update request to obtain a location group for the target area.
  • the group update apparatus 300 further includes:
  • the update duration acquisition module is used to acquire the update duration of the location group.
  • the dynamic update timing module is used to calculate the time length from the time point when the location group is obtained to the current time point, and when the time length is greater than or equal to the update duration time, control the group object update module 340 Stop updating the target group objects in the location group.
  • the group update apparatus 300 further includes:
  • the notification attribute acquisition module is used to acquire the dynamic update notification attribute of the location group.
  • the notification message sending module is configured to send a message notification to at least one of the target group object and the business object according to the dynamically updated notification attribute, to send a message notification to the target group object and the business object. At least one of the business objects sends a message notification.
  • the notification attribute acquisition module includes:
  • the first notification attribute obtaining unit is configured to obtain the preset first change notification attribute corresponding to the location group.
  • the first notification message generating unit is configured to generate a first notification message of the target object and/or generate a second notification message of the business object when it is determined that a message notification needs to be sent based on the first change notification attribute.
  • the second notification attribute obtaining unit is configured to obtain the preset second change notification attribute corresponding to the location group.
  • the notification message sending module may be used to send the first notification message to the target group object; and/or send the second notification message to the business object. And when it is determined based on the second change notification attribute that there is no need to send a message notification, cancel sending the notification message to the target object and/or the business object.
  • the group update device provided by the embodiment of the present application realizes the dynamic real-time update of the group based on the position of the object in the target area, avoids the problem of group update delay, and reduces the workload of group maintenance and reduces Maintenance costs.
  • the message sending apparatus 400 may specifically include the following modules:
  • the target attribute determination module 410 is configured to obtain the event notification judgment standard of the subscription resource, and determine the target attribute that needs to be monitored according to the event notification judgment standard.
  • the attribute value obtaining module 420 is configured to obtain the changed attribute value of the target attribute when the attribute value of the target attribute is changed.
  • the difference notification message construction module 430 is configured to construct a difference notification message according to the changed attribute value when the notification mode is the difference notification mode.
  • the difference notification message sending module 440 is configured to send the difference notification message.
  • the message sending apparatus 400 further includes:
  • the subscription request receiving module is used to receive the subscription request sent by the subscriber corresponding to the subscription resource.
  • the operation attribute obtaining module is used to create or update the operation attribute of the subscription resource according to the subscription request.
  • the message sending apparatus 400 further includes:
  • the notification mode determination module is configured to determine whether the notification mode is a differential notification mode according to the notification content type and the notification mode type.
  • the notification method determining module includes:
  • the first verification unit is used to verify the notification content type.
  • the first difference notification method determining unit is configured to determine that the notification method is a difference notification method when the notification content type is a difference notification content.
  • the second verification unit is configured to verify the notification mode type when the notification content type is non-disparity notification content.
  • the second difference notification mode determining unit is configured to determine that the notification mode is a difference notification mode when the notification mode type is a difference notification mode.
  • the message sending apparatus 400 further includes:
  • the conventional notification message building module is used to construct a corresponding conventional notification message according to the changed attribute value when the notification mode type is a conventional notification mode.
  • the difference notification message construction module 430 includes:
  • An incremental message constructing unit configured to construct a delta notification message corresponding to an increase in the incremental attribute value when the changed attribute value only contains an incremental attribute value, and the delta notification message contains The increment identification parameter that characterizes the increment attribute value.
  • the decrement message construction unit is configured to construct a difference notification message corresponding to the decrement attribute value when the changed attribute value only contains the decrement attribute value, and the difference notification message contains The decrement identification parameter that characterizes the decrement attribute value.
  • the increase and decrease message construction unit is used to construct the difference between increasing the increase attribute value and decreasing the decrease attribute value when the changed attribute value contains both an increase attribute value and a decrease attribute value.
  • a quantity notification message, the difference notification message includes an increment identification parameter that characterizes the increment attribute value and a decrement identification parameter that characterizes the decrement attribute value.
  • the message sending device provided by the embodiment of the present application can realize the difference notification of the changed attribute value of the target attribute, can enable the subscriber to know the attribute value after the target attribute is changed in time, and improve the subscriber's perception.
  • an embodiment of the present application also provides an electronic device, including a processor and a memory, and a computer program that can run on the processor is stored in the memory, and the processor implements the above group when the program is executed.
  • Group update method or implement the above message sending method.
  • the embodiment of the present application also provides a computer-readable storage medium that stores computer instructions, and when the computer instructions are executed by a processor of an electronic device, the electronic device can enable the above-mentioned group update method or the above-mentioned message sending method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请提供了一种群组更新方法、消息发送方法及装置。群组更新方法包括：获取针对目标区域的位置群组；获取位置群组的动态更新时间；在根据动态更新时间确定的每个时间点，获取位置群组内的目标群组对象的目标位置，并查询目标区域内是否存在不属于位置群组的业务对象；以及根据获取的目标位置和查询结果更新位置群组内的目标群组对象。本申请可以实现群组对象的动态更新，且减少了群组维护的工作量及维护成本。

Description

群组更新方法、消息发送方法及装置
本申请要求于2020年1月17日提交的、申请号为202010054612.4的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及动态群组处理技术领域，特别是涉及一种群组更新方法、消息发送方法及装置。
背景技术
群组是具有相同特征的某一类事物的组合，可以有很多种存在的方式，如设计软件、聊天软件、社交网站等等。每个群组都会设定一定的主题以及相关的组织规则。
目前，建立的群组通常是静态群组，需要用户根据静态成员列表建立群组。在增加群组成员时，需要用户手动添加。在某个区域内建立群组时，需要用户对群组进行手动更新，无法根据群组成员的位置实现群组的动态更新。用户手动方式会造成群组更新延时，还会增加群组维护的工作量及成本。
发明内容
本申请提供一种群组更新方法、消息发送方法及装置，以至少部分地解决现有技术中的问题。
根据第一方面，本申请公开了一种群组更新方法，包括：获取针对目标区域的位置群组；获取所述位置群组的动态更新时间；在根据所述动态更新时间确定的每个时间点，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象；以及根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。
可选地，根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象，包括：在所述目标位置处于所述目标区域之外的情况下，从所述位置群组内剔除所述目标群组对象。
可选地，根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象， 包括：在所述目标区域内存在不属于所述位置群组的业务对象的情况下，将所述业务对象添加至所述位置群组。
可选地，获取针对目标区域的位置群组，包括：接收第一群组资源创建请求；根据所述第一群组资源创建请求获取群组属性；以及根据所述群组属性创建群组，以得到针对所述目标区域的位置群组。
可选地，获取针对目标区域的位置群组，包括：接收第二群组资源创建请求；根据所述第二群组资源创建请求创建初始群组；接收群组更新请求；以及根据所述群组更新请求更新所述初始群组的属性，以得到针对所述目标区域的位置群组。
可选地，群组属性包括动态更新时间、更新持续时长、目标区域、位置相关属性、动态更新属性、动态更新通知属性中的至少一种。
可选地，方法还包括：获取所述位置群组的更新持续时长；在从得到所述位置群组的时间点开始至当前时间点之间的时长大于或等于所述更新持续时长时，停止对所述位置群组内的目标群组对象的更新。
可选地，方法还包括：获取所述位置群组的动态更新通知属性；以及在根据所述动态更新通知属性确定要向所述目标群组对象和所述业务对象中至少之一发送消息通知的情况下，向所述目标群组对象和所述业务对象中至少之一发送消息通知。
根据第二方面，本申请公开了一种消息发送方法，包括：获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定要进行监控的目标属性；在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值；在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息；以及发送所述差量通知消息。
可选地，方法还包括：在获取订阅资源事件通知判断标准之前，接收所述订阅资源对应的订阅方发送的订阅请求；以及根据所述订阅请求，创建或更新所述订阅资源的操作属性。
可选地，操作属性包括事件通知判断标准、通知内容类型和通知方式类型，其中所述通知方式类型包括差量通知方式和常规通知方式中的任一种。
可选地，方法还包括：获取所述订阅资源的通知内容类型和通知方式类型；以及根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式。
可选地，根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式，包括：对所述通知内容类型进行校验；在所述通知内容类型为差量通知内容 的情况下，确定所述通知方式为差量通知方式；在所述通知内容类型为非差量通知内容的情况下，对所述通知方式类型进行校验；以及在所述通知方式类型为差量通知方式的情况下，确定所述通知方式为差量通知方式。
可选地，根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式，还包括：在所述通知方式类型为常规通知方式的情况下，根据所述变更后的属性值构建常规通知消息。
可选地，根据所述变更后的属性值构建差量通知消息，包括：在所述变更后的属性值仅包含增量属性值的情况下，在所述差量通知消息中包含表征所述增量属性值的增量标识参数；在所述变更后的属性值仅包含减量属性值的情况下，在所述差量通知消息中包含表征所述减量属性值的减量标识参数；在所述变更后的属性值同时包含增量属性值和减量属性值的情况下，在所述差量通知消息中包含表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
可选地，差量通知消息包括增量属性值、减量属性值、表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
根据第三方面，本申请公开了一种群组更新装置，包括：位置群组获取模块，用于获取针对目标区域的位置群组；动态更新时间获取模块，用于获取所述位置群组的动态更新时间；位置对象获取模块，用于在根据所述动态更新时间确定的每个时间点，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象；以及群组对象更新模块，用于根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。
根据第四方面，本申请公开了一种消息发送装置，包括：目标属性确定模块，用于获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定要进行监控的目标属性；属性值获取模块，用于在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值；差量通知消息构建模块，用于在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息；以及差量通知消息发送模块，用于发送所述差量通知消息。
根据第五方面，本申请公开了一种电子设备，包括：存储器，存储有计算机程序；以及处理器，被配置为执行所述计算机程序，以实现上述群组更新方法，或，上述消息发送方法。
根据第六方面，本申请公开了一种计算机可读存储介质，存储有计算机指令，当所述计算机指令由电子设备的处理器执行时，使得电子设备能够执行上述群组更新方法，或，上述消息发送方法。
与现有技术相比，本申请包括以下优点：
在本申请实施例中，通过基于获取位置群组内的目标群组对象的目标位置，并查询目标区域内是否存在不属于位置群组的业务对象，并根据获取的目标位置和查询结果更新位置群组内的目标群组对象，实现了基于目标区域内的对象的位置对群组的动态实时更新，避免了群组更新延时的问题，且减少了群组维护的工作量，降低了维护成本。
附图说明
图1示出了本申请实施例一提供的一种群组更新方法的步骤流程图；
图2示出了本申请实施例提供的一种创建位置群组的示意图；
图3示出了本申请实施例提供的一种群组创建更新通知的示意图；
图4示出了本申请实施例二提供的一种消息发送方法的步骤流程图；
图5示出了本申请实施例提供的一种差量通知消息的示意图；
图6示出了本申请实施例三提供的一种群组更新装置的结构示意图；
图7示出了本申请实施例四提供的一种消息发送装置的结构示意图。
具体实施方式
为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
参照图1，示出了本申请实施例一提供的一种群组更新方法的步骤流程图，该群组更新方法具体可以包括如下步骤：
在步骤101中：获取针对目标区域的位置群组。
在本申请实施例中，目标区域是指其范围内的位置群组需要进行动态更新的区域，如“xx市xx区”，或“xx市xx区xx路”等。具体地，目标区域可以根据业务需求而定，本申请实施例对此不加以限制。
位置群组是指预先获取的针对目标区域需要进行动态更新的群组，在位置群组中包含有处于目标区域内的对象。根据实施例，可以根据接收到的群组资源创建请求来创建位置群组。在创建位置群组时，可以从目标区域内获取待添加的对象，并将待添加的对象添加至位置群组中即可获取与位置相关的位置群组。根据实施例，也可以根据预先创建的初始群组，通过更新的方式得到位置群组。
图2示出了本申请实施例提供的一种创建位置群组的示意图，图3示出了本申请实施例提供的一种群组创建更新通知的示意图，下面结合图2和图3以及下述具体实现方式详细描述位置群组的创建过程。
在本申请的一种具体实现方式中，上述步骤101可以包括：
子步骤A1.1：接收群组资源创建请求(第一群组资源创建请求)。
群组资源创建请求是指用于创建群组的请求。如图3所示，群组资源创建请求可以由应用实体AE(Application Entity)发送给通用服务实体CSE(Common Service Entity)。
群组资源创建请求可以是不含有目标区域的位置功能描述信息的群组资源创建请求，即该群组资源创建请求可以用于创建与位置无关的群组。或者，群组资源创建请求也可以创建与位置相关，但是位置与目标区域不同的群组。
群组资源创建请求还可以是含有目标区域的位置功能描述信息的群组资源创建请求。如图3所示，AE可以在群组资源创建请求中携带有位置功能描述信息(即目标区域)，在创建针对目标区域的与位置相关的位置群组时，将携带有位置功能描述信息的群组资源创建请求发送给CSE。在生成的群组资源创建请求中还可以包含是否与位置相关的属性，即locationRelated，这个属性值代表了该组资源是否是位置相关的。这个属性值为TRUE时，表示待创建的群组是与位置相关的；这个属性值为FALSE时，表示待创建的群组不是与位置相关的。若在群组资源创建请求中没有提供该属性值，则默认待创建的群组不是与位置相关的。若待创建的群组是与位置相关的群组，则在群组资源创建请求中应当包含位置功能描述信息(即目标区域)，即locationTargetArea，该属性值代表对应目标区域的地域信息。该属性值在locationRelated属性值为TRUE时为必选属性值。
在接收到群组资源创建请求之后，执行子步骤A1.2。
子步骤A1.2：根据所述群组资源创建请求获取群组属性。
根据实施例，群组属性包括动态更新时间(locationUpdatePeriod)、更新持续时长 (dynamicUpdateDuration)、目标区域(locationTargetArea)、位置相关属性(locationRelated)、动态更新属性(dynamicUpdate)、动态更新通知属性(dynamicUpdateNotification)中的至少一种。
在获取到群组属性之后，执行子步骤A1.3。
子步骤A1.3：根据所述群组属性创建群组，以得到针对目标区域的位置群组。具体的，可以获取待添加的对象，所述待添加的对象是位于由属性locationTargetArea所确定的目标区域范围内的对象。将对象添加到创建的位置群组中，并为位置群组添加群组资源创建请求中所指定的各属性的值。例如，如图2所示，节点Node1至Node5属于同一个目标域，例如由节点Node0管理的域。这样建立的群组可以适应域内场景。可以从目标区域中获取多个群组对象。从各节点中确定满足要求的节点，以作为群组对象。仍如图2所示，节点Node1、Node2、Node3属于同一个目标区域，可以添加至针对目标区域的相同的位置群组中。节点Node4和Node5不属于上述目标区域，在创建位置群组时不能添加至群组中。
在另一种实现方式中，上述步骤101可以包括：
子步骤A2.1：接收群组资源创建请求(第二群组资源创建请求)。
在第二群组资源创建请求中不包括群组属性，即不包括动态更新时间(locationUpdatePeriod)、更新持续时长(dynamicUpdateDuration)、目标区域(locationTargetArea)、位置相关属性(locationRelated)、动态更新属性(dynamicUpdate)、动态更新通知属性(dynamicUpdateNotification)中的任何一种。可以根据第二群组资源创建请求创建初始群组。
子步骤A2.2：根据所述第二群组资源创建请求创建初始群组。
初始群组可以是普通群组，即初始群组可以是位置不相关的群组。在创建的初始群组中可以添加有群组对象，即创建的初始群组中包含了群组成员。初始群组中的群组对象可以具有与前述群组属性不同的对象属性。创建的初始群组也可以为空的群组，即初始群组中未添加群组对象。此外，初始群组也可以是预先存在的群组，即在先前的某个时间创建的群组，本申请对此不做限定。
子步骤A2.3：接收群组更新请求。
群组更新请求可以由AE发送给CSE。在群组更新请求中包括要进行更新的群组属性。例如，可以包括动态更新时间(locationUpdatePeriod)、更新持续时长 (dynamicUpdateDuration)、目标区域(locationTargetArea)、位置相关属性(locationRelated)、动态更新属性(dynamicUpdate)、动态更新通知属性(dynamicUpdateNotification)中的至少一种。
子步骤A2.4：根据群组更新请求更新所述初始群组的属性，得到针对所述目标区域的位置群组。
在本实施例中，更新初始群组属性的属性值可以包含两层含义：
1、对原有属性值的更新
例如，属性dynamicUpdate-Notification的原有属性值为false，通过对原有属性值的更新可以将dynamicUpdate-Notification的原有属性值false更新为true。
2、对未存在属性的属性值的更新
例如，创建的初始群组不包含属性dynamicUpdate，在对初始群组更新时，可以将未定义的属性dynamicUpdate的属性值(为空)更新为属性值true。
在创建或更新得到位置群组，并确定了群组对象之后，可以对群组资源创建请求进行响应。如图3所示，分别向发送群组资源创建请求的AE和包含在位置群组内的目标节点应用(例如AE1)返回满足建立动态组响应，其中携带组资源信息。
群组属性的动态更新时间(locationUpdatePeriod)、更新持续时长(dynamicUpdateDuration)、目标区域(locationTargetArea)、位置相关属性(locationRelated)、动态更新属性(dynamicUpdate)、动态更新通知属性(dynamicUpdateNotification)的具体含义如表1所示：
表1：
Figure PCTCN2021072130-appb-000001
Figure PCTCN2021072130-appb-000002
Figure PCTCN2021072130-appb-000003
本申请通过更新上述六种群组属性的至少一种，即可实现将初始群组更新为针对目标区域的与位置相关的位置群组。
根据实施例，还可以根据位置群组的更新持续时长，确定何时停止对位置群组的动态更新操作，结合下述具体实现方式进行详细描述。
在本申请的一种具体实现方式中，群组更新方法还可以包括：
步骤B1：获取所述位置群组对应的更新持续时长。
在本申请实施例中，更新持续时长是指在得到位置群组，即位置群组创建成功之后开始计时，对位置群组进行动态更新的持续时长。例如，为位置群组设置的 dynamicUpdateDuration属性值，这个属性值代表了该组资源在目标区域上进行动态更新的持续时间。该属性值只有在dynamicUpdate为TRUE的时候有效。
在位置群组的创建过程中，可以设置位置群组进行动态更新的持续时间，如3天、8天等。具体地，更新持续时长的值可以根据业务需求而定，本申请实施例对此不加以限制。
根据实施例，更新持续时长也可以是在将初始群组更新为位置群组时设定的更新持续时长，也可以为初始群组创建时设置的更新持续时长。具体地，更新持续时长可以根据业务需求而定，本申请实施例对此不加以限制。
在将初始群组更新为位置群组之后，可以获取位置群组对应的更新持续时长。
在获取位置群组对应的更新持续时长之后，执行步骤B2。
步骤B2：在从得到所述位置群组的时间点开始至当前时间点之间的时长大于或等于所述更新持续时长时，停止对所述位置群组内的目标群组对象的动态更新操作。
在位置群组的创建时间点至当前时间点之间的时长小于更新持续时长时，继续执行对位置群组内的群组对象的更新操作。根据实施例，更新操作包括基于位置，执行群组对象的增加或减少等操作。
在从得到位置群组的时间点开始至当前时间点之间的时长大于或等于更新持续时长时，停止对位置群组内的群组对象的动态更新操作，即将动态更新群组转换为普通群组，在后续需要在群组内删除群组对象或添加群组对象时，需要群组管理员手动进行。例如，更新持续时长可以为dynamicUpdateDuration，Hosting CSE可以依据dynamicUpdateDuration属性值决定是否进行更新动态群组成员的操作：
1、当前时间与群组创建时间间隔小于dynamicUpdateDuration属性值，则进行更新；
2、当前时间与群组创建时间间隔大于dynamicUpdateDuration属性值，则不再更新。
可以理解地，上述示例仅是为了更好地理解本申请实施例的技术方案而列举的示例，不作为对本申请实施例的唯一限制。
在本申请实施例中，通过设置更新持续时长，能够减少持续获取群组对象的位置和/或持续获取目标区域内的可以添加至位置群组的业务对象所耗费的资源。
接下来，在步骤102中：获取所述位置群组对应的动态更新时间。
动态更新时间是指对位置群组进行动态更新的时间。
在某些示例中，根据动态更新时间确定某个或多个时间点，如12:00、12:30、13:00、 13:30等等。
在某些示例中，动态更新时间可以为自得到位置群组后开始计时，每隔设定时间间隔的多个时间点，如目标群组对象从12:00加入至位置群组，每隔20min执行一次目标群组对象的位置获取，即12:20、12:40、13:00等。
可以理解地，上述示例仅是为了更好地理解本申请实施例的技术方案而列举的示例，不作为对本申请实施例的唯一限制。
根据实施例，动态更新时间可以是在将初始群组更新为位置群组时设定的更新时间，也可以为初始群组创建时设置的初始动态更新时间。具体地，动态更新时间可以根据业务需求而定，本申请实施例对此不加以限制。
在本申请实施例中，还可以设置位置群组的群组更新属性，结合下述具体实现方式进行详细描述。
在本申请的一种具体实现方式中，上述步骤102可以包括：
子步骤C1：获取所述位置群组的动态更新属性。
在本申请实施例中，群组的动态更新属性是指例如dynamicUpdate。
在获取动态更新时间之后，可以获取位置群组的动态更新属性，进而，执行子步骤C2。
子步骤C2：在所述动态更新属性为TRUE的情况下，获取所述动态更新时间。
在获取位置群组的动态更新属性之后，可以根据动态更新属性确定是否需要对群组资源进行动态更新。例如，在dynamicUpdate＝TRUE，则获取动态更新时间；而在dynamicUpdate＝FALSE，则没有后续操作。
接下来，在步骤103中：在根据所述动态更新时间确定的每个时间点时，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象。
目标群组对象是指已经添加至与位置相关的位置群组中的对象。目标群组对象的位置是可以发生变化的。目标群组对象可以为用户、可移动实体等对象中的任一种，可以根据业务需求而定。
目标位置是指在位置获取时间点，目标群组对象所处的位置。
业务对象是指位于目标区域内，与位置群组添加的群组对象的类型相同，且与位置相关的还未加入位置群组中的对象。
在位置获取时间点，可以获取位置群组内的目标群组对象的目标位置，并查询目标区域内是否存在不属于位置群组的与位置相关的业务对象。
在某些示例中，目标位置可以是采用卫星定位的方式获取的，例如，目标群组对象上携带的GPS(Global Positioning System，全球定位系统)等导航设备处于开启状态，进而，可以实现对移动终端的实时定位，以获取目标群组对象在位置获取时间点的目标位置。
在某些示例中，目标位置可以是目标群组对象向CSE发送的位置，例如，可以在达到位置获取时间点之前的某个时刻，向目标群组对象发送消息，以在群组内的目标群组对象之间进行位置共享。目标群组对象在接收到提醒消息之后，即可向CSE共享位置，以作为目标位置。
当然，不仅限于此，在具体实现中，本领域技术人员还可以采用其它方式获取目标群组对象在位置获取时间点所处的目标位置。具体地，获取目标位置的方式可以根据业务需求而定，本申请实施例对此不加以限制。
而对于查询业务对象的方式，可以是通过对目标区域进行实时监控，以监控在目标区域内是否存在业务对象。本申请实施例不仅限于此，在具体实现中，还可以采用其它方式查询目标区域内是否存在业务对象，可以根据业务需求而定，本申请实施例对此不加以限制。
接下来，在步骤104中：根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。根据实施例，可以根据获取的目标位置确定是否需要从位置群组中删除目标群组对象。根据实施例，可以根据查询结果确定是否需要将新的目标群组对象添加至位置群组中。
在本申请的具体的实现方式中，步骤104还可以进一步包括步骤104.1和步骤104.2中的至少一个。
步骤104.1：在所述目标位置处于所述目标区域之外的情况下，从所述位置群组内剔除所述目标群组对象。
步骤104.2：在所述目标区域内存在不属于所述位置群组的业务对象的情况下，将所述业务对象添加至所述位置群组。
根据实施例，在获取到目标群组对象的目标位置之后，可以判断目标位置是否处于目标区域，在目标位置处于目标区域之内时，则不对目标群组对象进行处理。
根据实施例，在判定目标群组对象处于目标区域之外时，可以从位置群组内剔除目标群组对象。而在目标区域内存在不属于位置群组的业务对象的情况下，可以将业务对象添加至位置群组。具体地，可以分为以下四种情况：
1、目标位置处于目标区域之外，目标区域内存在业务对象
此时，可以将目标群组对象剔除位置群组，并将业务对象添加至位置群组。
2、目标位置处于目标区域之内，目标区域内存在业务对象
此时，不对目标群组对象进行处理，而将业务对对象添加至位置群组。
3、目标位置处于目标区域之外，目标区域内不存在业务对象
此时，可以将目标群组对象剔除位置群组，而不对业务对象进行处理。
4、目标位置处于目标区域之内，目标区域内不存在业务对象
此时，不对目标群组对象进行处理，也不对业务对象进行处理。
本申请实施例可以实现群组成员的动态更新，减少了群组管理员手动添加群组成员或剔除群组成员的工作量。
在从位置群组内剔除目标群组对象，和/或将业务对象添加至位置群组之后，可以根据位置群组对应的变更通知属性确定是否向目标群组对象，和/或业务对象发送通知消息，具体地，可以结合下述具体实现方式进行详细描述。
在本申请的一种具体实现方式中，所述方法还可以包括：
步骤D1：获取预先设置(例如由AE设置)的所述位置群组对应的第一变更通知属性。
在本申请实施例中，预先为位置群组设置有变更通知属性，如dynamicUpdateNotification，可以依据dynamicUpdateNotification决定是否对变化成员发送相应的通知。
第一变更通知属性是指对变化的群组对象发送相应的通知，如，dynamicUpdateNotification＝TRUE，则发送通知。
在从位置群组内剔除目标群组对象，和/或将业务对象添加至位置群组之后，可以获取预先设置的所述位置群组对应的第一变更通知属性。
步骤D2：在基于所述第一变更通知属性确定需要发送消息通知时，生成所述目标对象的第一通知消息，和/或生成所述业务对象的第二通知消息。
步骤D3：将所述第一通知消息发送给所述目标群组对象；和/或将所述第二通知消 息发送给所述业务对象。
第一通知消息是指从位置群组中剔除目标群组对象之后，生成的用于向目标群组对象发送的通知消息，第一通知消息可以用于通知目标群组对象已经被剔除位置群组。
第二通知消息是指在将业务对象添加至位置群组之后，生成的用于向业务对象发送的通知消息，第二通知消息可以用于通知业务对象已经被添加至位置群组。
在基于第一变更通知属性确定需要发送消息通知时，可以生成目标对象的第一通知消息，和/或生成业务对象的第二通知消息，如，A进入目标区域，Hosting CSE将A纳入memberIDs属性值，dynamicUpdateNotification＝TRUE，则对A发送通知，通知内包含组信息；C离开目标区域，Hosting CSE将C从memberIDs属性值删除，dynamicUpdateNotification＝TRUE，则对C发送通知，通知内包含组信息。
在本申请的另一种具体实现方式中，所述方法还可以包括：
步骤E1：获取预先设置的所述位置群组对应的第二变更通知属性；
步骤E2：在基于所述第二变更通知属性确定不需要发送消息通知时，取消向所述目标对象和/或所述业务对象发送通知消息。
在本申请实施例中，第二变更通知属性是指不向变更的群组成员发送通知消息的属性，如dynamicUpdateNotification＝FALSE，则不发送通知。
而在根据第二变更通知属性确定不需要发送消息通知时，则取消向目标群组对象和/或业务对象发送通知消息，例如，B离开目标区域，Hosting CSE将B从memberIDs属性值删除，dynamicUpdateNotification＝FALSE，则对B不发送通知；D进入目标区域，Hosting CSE将D纳入memberIDs属性值，dynamicUpdateNotification＝FALSE，则对D不发送通知。
容易理解的是，还可以根据第一变更通知属性和第二变更通知属性来确定是否向创建群组的AE发送通知响应。如图3所示，在目标节点应用AE2进入目标区域并被加入到位置群组后，CSE向AE发送更新动态组响应，其中携带有组资源信息，用于向AE通知位置群组中目标群组对象的更新信息。
本申请实施例提供的群组更新方法，通过基于获取位置群组内的目标群组对象的目标位置，并查询目标区域内是否存在不属于位置群组的业务对象，并根据获取的目标位置和查询结果更新位置群组内的目标群组对象，实现了基于目标区域内的对象的位置对群组的动态实时更新，避免了群组更新延时的问题，且减少了群组维护的工作量，降低 了维护成本。
参照图4，示出了本申请实施例二提供的一种消息发送方法的步骤流程图，该消息发送方法具体可以包括如下步骤：
在步骤201中：获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定要进行监控的目标属性。
在本申请实施例中，订阅资源可以为订阅方预先订阅的资源。
目标属性是指订阅资源中由订阅方订阅的需要进行监控，并能够触发匹配事件诞生的属性。
例如，在图3所示的示例中，在CSE中存储有关于应用实体AE1和AE2的属性信息，应用实体AE作为订阅方可以向CSE订阅关于应用实体AE1和AE2的至少一部分属性信息，即订阅资源。进一步地，AE可以指定订阅资源中需要进行监控，并能够触发匹配事件诞生的属性，即目标属性。在CSE向AE1、AE2和AE中的至少一个发送通知消息时可以采用下述消息发送方法。
在目标属性的创建过程中，可以预先为每个属性设置一个事件通知判断标准，即eventNotificationCriteria。该事件通知判断标准指示了是否对属性进行监控的标准。
在本申请中，在判定订阅资源中的属性是否需要进行监控时，可以对订阅资源中的每个属性(eventNotificationCriteria/attribute)进行校验，以获取每个属性对应的事件通知判断标准的值。
可以理解地，在某个属性未设置eventNotificationCriteria，可以视为按照默认策略对该属性进行处理，例如不对该属性进行监控操作，并且该属性的属性值的变化不会触发匹配事件诞生，本申请对于此种情况不做考虑。
对于目标属性对应的操作属性的设置可以在接收到订阅方发送的订阅请求之后进行。具体地，在接收到订阅方发送的针对目标属性的订阅请求之后，可以根据订阅请求创建或更新目标属性对应的事件通知判断标准(即eventNotificationCriteria)、通知内容类型(即notificationContentType)、通知方式类型，其中通知方式类型可以包括差量通知(diffNotification)和常规通知中的任一种。
上述创建或更新包含以下两种情况：
1、创建，在目标属性未定义操作属性eventNotificationCriteria、notificationContentType、diffNotification三种的至少一种时，可以为目标属性创建目标属性未定义的操作属性。 例如，在目标属性未定义操作属性diffNotification时，可以在接收到订阅方的订阅请求之后，根据订阅请求确定属性定义diffNotification，则可以创建目标属性的diffNotification。
2、更新，在目标属性定义了操作属性eventNotificationCriteria、notificationContentType、diffNotification三种的任一种时，在需要对其中的至少一种更新时，则可以根据订阅方的订阅请求对相应的操作属性进行更新。例如，目标属性定义了操作属性notificationContentType时，可以在接收到订阅方的订阅请求之后，根据订阅请求确定需要更新notificationContentType，则可以对目标属性的notificationContentType进行更新。
在获取到每个属性的事件通知判断标准的值之后，可以根据每个属性的事件通知判断标准的值，确定需要进行监控的目标属性。例如，若eventNotificationCriteria/attribute进行了设置，则对由attribute指定的属性进行监控，并根据attribute指定的属性的属性值进行校验，校验成功则称之为匹配的事件诞生；若未对eventNotificationCriteria/attribute进行设置，则所有目标属性的属性值的变化都将引发匹配的事件诞生。
接下来，在步骤202中：在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值。
根据实施例，目标属性的变更后的属性值可以仅为目标属性增加的属性值，也可以仅为目标属性减少的属性值，还可以为目标属性同时增加和减少的属性值，可以根据实际情况而定，本申请实施例对此不加以限制。
在目标属性的属性值发生变更时，可以获取目标属性的变更后的属性值。例如，若目标属性增加了属性值A和属性值B，则将属性值A和属性值B作为变更后的属性值；若目标属性减少了属性值A和属性值C，则将属性值A和属性值C作为变更后的属性值；若目标属性增加了属性值A，并减少了属性值D，则将属性值A和属性值D作为变更后的属性值。
可以理解地，上述示例仅是为了更好地理解本申请实施例的技术方案而列举的示例，不作为对本申请实施例的唯一限制。
接下来，在步骤203中：在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息。
通知方式指示了采用何种方式发送通知消息。通知方式可以根据订阅方发送的订阅请求中的操作属性的定义来确定。
通知方式可以包括差量通知方式和常规通知方式，本申请旨在针对差量通知方式进 行描述，对于常规通知方式不作详细表述。
在获取目标属性之后，可以校验并获取目标属性对应的通知方式，具体地，可以结合下述具体实现方式进行详细描述。
在本申请的一种具体实现方式中，上述步骤203可以包括：
子步骤F1：获取所述订阅资源的通知内容类型和通知方式类型。
子步骤F2：根据所述通知内容类型和所述通知方式类型确定所述目标属性对应的通知方式是否为差量通知方式。
在本申请的一种具体实现方式中，上述步骤F2可以进一步包括：
子步骤F2.1：对通知内容类型进行校验。
子步骤F2.2：在所述通知内容类型为差量通知内容的情况下，确定所述通知方式为差量通知方式。
子步骤F2.3：在所述通知内容类型为非差量通知内容的情况下，对通知方式类型进行校验。
子步骤F2.4：在所述通知方式类型为差量通知方式的情况下，确定所述通知方式为差量通知方式。
在本申请实施例中，通知内容类型是指针对何种内容生成通知消息，即notificationContentType。
在本申请中，notificationContentType可以包括：'Modified Attributes'、'All Attributes'、'ResourceID'、'Trigger Payload'、'Modified Difference'五种类型，不同的类型可以构成不同的通知内容：
'Modified Attributes'对应只传递变化的属性值信息；
'All Attributes'对应传递资源所有属性值信息；
'ResourceID'对应只传递涉及资源ID；
'Trigger Payload'对应传递trigger payload信息；
'Modified Difference'对应只传递变化的属性值的变化信息。
可以理解地，本申请的核心点在于'Modified Difference'，而对于其它四种类型，本申请实施例不再加以描述。
通知方式类型是指目标属性在发生属性值变更时，向订阅方发送何种类型的通知消息的属性。
可以采用两种方式校验是否进行差量通知：
1、校验目标属性对应的通知内容类型，即校验notificationContentType的通知类型属性是否为'Modified Difference'，若是则进行差量通知。
2、校验目标属性对应的通知方式类型(包括差量通知方式和常规通知方式)，即，在通知方式类型为差量通知方式(diffNotification)时，则进行差量通知；而在通知方式类型为常规通知方式时，可以构建变更后的属性值的常规通知消息，进行常规通知。
首先，可以校验目标属性的通知内容类型，在通知内容类型为差量通知类型时，则进行差量通知。
其次，在校验目标属性的通知内容类型为非差量通知内容时，则校验目标属性的通知方式类型，在通知方式类型为差量通知方式时，则进行差量通知。
根据实施例，差量通知方式是指生成差量通知消息向订阅方发送通知的方式。
确定通知方式为差量通知方式的情况分为以下两种：
1、校验目标属性的通知内容类型(即notificationContentType)为'Modified Difference'时，进行差量通知。
2、在校验目标属性的通知内容类型(即notificationContentType)为除'Modified Difference'以外的非差量通知内容时，校验目标属性的通知方式类型Notification为TRUE，即差量通知方式时，进行差量通知。
在通知方式为差量通知方式时，可以根据变更后的属性值构建对应的差量通知消息。
在差量通知消息内可以包括增量属性值、减量属性值、表征增量属性值的增量标识参数和表征减量属性值的减量标识参数。
在本申请实施例中，可以结合图5对差量通知消息进行如下详细描述。
如图5所示，可以根据notification ContentType决定采用生成何种通知消息，notification ContentType为差量通知类型(即Modified Difference，图中未示出)时，可以构建差量通知消息，即m2m：notification。在生成的通知消息中可以包含属性值的标识参数，即通知消息中包含“diffState”，具体地，可以分为增量标识参数、减量标识参数等。在生成差量通知消息之后，可以将差量通知消息发送给订阅方，然后订阅方可以根据差量通知消息，更新订阅资源的属性，即图5中所示的Update to attributes of the subscribed-to resource。
变更后的属性值可以包含增量属性值和减量属性值的至少一种，那么，可以根据具 体的增量属性值和减量属性值构建相应的差量通知消息，具体地，可以结合下述具体实现方式进行详细描述。
在本申请的一种具体实现方式中，在所述变更后的属性值仅包含增量属性值时，构建增加所述增量属性值对应的差量通知消息，所述差量通知消息中包含有表征所述增量属性值的增量标识参数。
在本申请实施例中，在变更后的属性值仅包含增量属性值时，可以构建增加增量属性值对应的差量通知消息，在差量通知消息中包含有表征增量属性值的增量标识参数，例如，diffState＝ADDITIONS，其中需要传递变化的增量属性值信息，如属性值A增量属性值信息DE。
在本申请的一种具体实现方式中，在所述变更后的属性值仅包含减量属性值时，构建减少所述减量属性值对应的差量通知消息，所述差量通知消息中包含有表征所述减量属性值的减量标识参数。
在变更后的属性值仅包含减量属性值时，可以构建减少减量属性值对应的差量通知消息，而在差量通知消息中包含有表征减量属性值对应的减量标识参数，例如，diffState＝DECREASES，其中需要传递变化的减量属性值信息，如属性值A减量属性值信息AB。
在本申请的一种具体实现方式中，在所述变更后的属性值同时包含增量属性值和减量属性值时，构建增加所述增量属性值和减少所述减量属性值的差量通知消息，所述差量通知消息中包含有表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
在变更后的属性值同时包含增量属性值和减量属性值时，可以构建增加增量属性值和减少减量属性值的差量通知消息，在差量通知消息中包含有表征增量属性值的增量标识参数和表征减量属性值的减量标识参数，如组成员增加F并减少C等。
接下来，在步骤204中：发送所述差量通知消息。
根据实施例，可以将差量通知消息发送给所述目标订阅资源对应的订阅方。订阅方是指订阅了目标属性的属性值变更接收通知消息的业务方，订阅方可以某个用户，也可以为某个业务平台，具体地，可以根据业务需求而定。
另外，需要说明的是，这里的订阅方是广义上的订阅方，既包括向CSE订阅资源并指定要进行监控的目标属性的AE，也包括群组中所包括的各个群组成员。例如，群组成员中的节点AE1也可以向CSE订阅要接收通知消息的资源。
在获取到差量通知消息之后，可以将差量通知消息发送给订阅方，从而可以实现消息的差量通知。
本申请实施例可以应用于对特定区域的电子标签进行统一管理。例如，在订阅通知方面，可以采取差量通知的方式进行数据包裹大小的优化。例如，对于超市中的商品推送场景，超市的商品琳琅满目，商品种类众多，使用订阅通知对新上架商品进行推送，这种场景下非常适合使用差量通知对其进行通知。通过差量订阅智慧零售的服务器中的商品目录，可以更加直观获得关于新增商品的信息。
本申请实施例提供的消息发送方法，通过获取订阅资源事件通知判断标准来确定目标属性，并根据获取到的目标属性的变更后的属性值，构建对应的差量通知消息，将差量通知消息发送给目标属性对应的订阅方。本申请实施例可以实现针对目标属性变更的差量通知，能够使订阅方及时得知属性变更的属性值，提高了订阅方的感知度。
参照图6，示出了本申请实施例三提供的一种群组更新装置的结构示意图，该群组更新装置300具体可以包括如下模块：
位置群组获取模块310，用于获取针对目标区域的位置群组。
动态更新时间获取模块320，用于获取所述位置群组的动态更新时间。
位置对象获取模块330，用于根据所述动态更新时间确定的每个时间点，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象。
群组对象更新模块340，用于根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。
在具体的实现方式中，群组对象更新模块340包括：
对象剔除单元，用于在所述目标位置处于所述目标区域之外的情况下，从所述位置群组内剔除所述目标群组对象。
在具体的实现方式中，群组对象更新模块340还包括：
对象添加单元，用于在所述目标区域内存在不属于所述位置群组的业务对象的情况下，将所述业务对象添加至所述位置群组。
在具体的实现方式中，位置群组获取模块310包括：
请求接收单元，用于接收第一群组资源创建请求，或用于接收第二群组资源创建请 求和群组更新请求。
群组属性获取单元，用于根据所述第一群组资源创建请求和群组更新请求获取群组属性。
位置群组创建单元，用于根据所述群组属性创建群组，以得到针对目标区域的位置群组。
初始群组创建单元，用于所述第二群组资源创建初始群组。
初始群组更新单元，用于根据所述群组更新请求更新所述初始群组的属性，以得到针对所述目标区域的位置群组。
在具体的实现方式中，群组更新装置300还包括：
更新持续时长获取模块，用于获取所述位置群组的更新持续时长。
动态更新计时模块，用于计算在从得到所述位置群组的时间点开始至当前时间点之间的时长，并在该时长大于或等于所述更新持续时长时，控制群组对象更新模块340停止对所述位置群组内的目标群组对象的更新。
在具体的实现方式中，群组更新装置300还包括：
通知属性获取模块，用于获取所述位置群组的动态更新通知属性。
通知消息发送模块，用于在根据所述动态更新通知属性确定要向所述目标群组对象和所述业务对象中至少之一发送消息通知的情况下，向所述目标群组对象和所述业务对象中至少之一发送消息通知。
在具体的实现方式中，通知属性获取模块包括：
第一通知属性获取单元，用于获取预先设置的所述位置群组对应的第一变更通知属性。
第一通知消息生成单元，用于在基于所述第一变更通知属性确定需要发送消息通知时，生成所述目标对象的第一通知消息，和/或生成所述业务对象的第二通知消息。
第二通知属性获取单元，用于获取预先设置的所述位置群组对应的第二变更通知属性。
通知消息发送模块可以用于将所述第一通知消息发送给所述目标群组对象；和/或将所述第二通知消息发送给所述业务对象。并且在基于所述第二变更通知属性确定不需要发送消息通知时，取消向所述目标对象和/或所述业务对象发送通知消息。
本申请实施例提供的群组更新装置实现了基于目标区域内的对象的位置对群组的 动态实时更新，避免了群组更新延时的问题，且减少了群组维护的工作量，降低了维护成本。
参照图7，示出了本申请实施例四提供的一种消息发送装置的结构示意图，该消息发送装置400具体可以包括如下模块：
目标属性确定模块410，用于获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定需要进行监控的目标属性。
属性值获取模块420，用于在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值。
差量通知消息构建模块430，用于在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息。
差量通知消息发送模块440，用于发送所述差量通知消息。
在具体的实现方式中，消息发送装置400还包括：
订阅请求接收模块，用于接收所述订阅资源对应的订阅方发送的订阅请求。
操作属性获取模块，用于根据所述订阅请求，创建或更新所述订阅资源的操作属性。
在具体的实现方式中，消息发送装置400还包括：
通知方式确定模块，用于根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式。
在具体的实现方式中，通知方式确定模块包括：
第一校验单元，用于对所述通知内容类型进行校验。
第一差量通知方式确定单元，用于在所述通知内容类型为差量通知内容的情况下，确定所述通知方式为差量通知方式。
第二校验单元，用于在所述通知内容类型为非差量通知内容的情况下，对所述通知方式类型进行校验。
第二差量通知方式确定单元，用于在所述通知方式类型为差量通知方式的情况下，确定所述通知方式为差量通知方式。
在具体的实现方式中，消息发送装置400还包括：
常规通知消息构建模块，用于在通知方式类型为常规通知方式时，根据所述变更后的属性值构建对应的常规通知消息。
在具体的实现方式中，差量通知消息构建模块430包括：
增量消息构建单元，用于在所述变更后的属性值仅包含增量属性值的情况下，构建增加所述增量属性值对应的差量通知消息，所述差量通知消息中包含有表征所述增量属性值的增量标识参数。
减量消息构建单元，用于在所述变更后的属性值仅包含减量属性值的情况下，构建减少所述减量属性值对应的差量通知消息，所述差量通知消息中包含有表征所述减量属性值的减量标识参数。
增减量消息构建单元，用于在所述变更后的属性值同时包含增量属性值和减量属性值的情况下，构建增加所述增量属性值和减少所述减量属性值的差量通知消息，所述差量通知消息中包含有表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
本申请实施例提供的消息发送装置可以实现目标属性的变更属性值的差量通知，能够使订阅方及时得知目标属性变更后的属性值，提高了订阅方的感知度。
对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
另外地，本申请实施例还提供了一种电子设备，包括处理器和存储器，在存储器上存储有可在所述处理器上运行的计算机程序，所述处理器执行所述程序时实现上述群组更新方法，或者实现上述消息发送方法。
本申请实施例还提供了一种计算机可读存储介质，存储有计算机指令，当所述计算机指令由电子设备的处理器执行时，使得电子设备能够上述群组更新方法，或者上述消息发送方法。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
最后，还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将 一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上对本申请所提供的一种群组更新方法、一种消息发送方法、一种群组更新装置、一种消息发送装置、一种电子设备及一种计算机可读存储介质，进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (20)

  1. 一种群组更新方法，包括：
    获取针对目标区域的位置群组；
    获取所述位置群组的动态更新时间；
    在根据所述动态更新时间确定的每个时间点，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象；以及
    根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。
  2. 根据权利要求1所述的方法，其中，所述根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象，包括：
    在所述目标位置处于所述目标区域之外的情况下，从所述位置群组内剔除所述目标群组对象。
  3. 根据权利要求1或2所述的方法，其中，所述根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象，包括：
    在所述目标区域内存在不属于所述位置群组的业务对象的情况下，将所述业务对象添加至所述位置群组。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述获取针对目标区域的位置群组，包括：
    接收第一群组资源创建请求；
    根据所述第一群组资源创建请求获取群组属性；以及
    根据所述群组属性创建群组，以得到针对所述目标区域的位置群组。
  5. 根据权利要求1至3中任一项所述的方法，其中，所述获取针对目标区域的位置群组，包括：
    接收第二群组资源创建请求；
    根据所述第二群组资源创建请求创建初始群组；
    接收群组更新请求；以及
    根据所述群组更新请求更新所述初始群组的属性，以得到针对所述目标区域的位置群组。
  6. 根据权利要求4或5所述的方法，其中，所述群组属性包括动态更新时间、更新持续时长、目标区域、位置相关属性、动态更新属性、动态更新通知属性中的至少一种。
  7. 根据权利要求4至6中任一项所述的方法，还包括：
    获取所述位置群组的更新持续时长；
    在从得到所述位置群组的时间点开始至当前时间点之间的时长大于或等于所述更新持续时长时，停止对所述位置群组内的目标群组对象的更新。
  8. 根据权利要求4至6中任一项所述的方法，还包括：
    获取所述位置群组的动态更新通知属性；以及
    在根据所述动态更新通知属性确定要向所述目标群组对象和所述业务对象中至少之一发送消息通知的情况下，向所述目标群组对象和所述业务对象中至少之一发送消息通知。
  9. 一种消息发送方法，包括：
    获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定要进行监控的目标属性；
    在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值；
    在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息；以及
    发送所述差量通知消息。
  10. 根据权利要求9所述的方法，还包括：在获取订阅资源事件通知判断标准之前，
    接收所述订阅资源对应的订阅方发送的订阅请求；以及
    根据所述订阅请求，创建或更新所述订阅资源的操作属性。
  11. 根据权利要求10所述的方法，其中，所述操作属性包括事件通知判断标准、通知内容类型和通知方式类型，其中所述通知方式类型包括差量通知方式和常规通知方式中的任一种。
  12. 根据权利要求9至11中任一项所述的方法，还包括：
    获取所述订阅资源的通知内容类型和通知方式类型；以及
    根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方 式。
  13. 根据权利要求12所述的方法，其中，所述根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式，包括：
    对所述通知内容类型进行校验；
    在所述通知内容类型为差量通知内容的情况下，确定所述通知方式为差量通知方式；
    在所述通知内容类型为非差量通知内容的情况下，对所述通知方式类型进行校验；以及
    在所述通知方式类型为差量通知方式的情况下，确定所述通知方式为差量通知方式。
  14. 根据权利要求13所述的方法，其中，所述根据所述通知内容类型和所述通知方式类型确定所述通知方式是否为差量通知方式，还包括：
    在所述通知方式类型为常规通知方式的情况下，根据所述变更后的属性值构建常规通知消息。
  15. 根据权利要求9所述的方法，其中，所述根据所述变更后的属性值构建差量通知消息，包括：
    在所述变更后的属性值仅包含增量属性值的情况下，在所述差量通知消息中包含表征所述增量属性值的增量标识参数；
    在所述变更后的属性值仅包含减量属性值的情况下，在所述差量通知消息中包含表征所述减量属性值的减量标识参数；
    在所述变更后的属性值同时包含增量属性值和减量属性值的情况下，在所述差量通知消息中包含表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
  16. 根据权利要求9所述的方法，其中，所述差量通知消息包括增量属性值、减量属性值、表征所述增量属性值的增量标识参数和表征所述减量属性值的减量标识参数。
  17. 一种群组更新装置，包括：
    位置群组获取模块，用于获取针对目标区域的位置群组；
    动态更新时间获取模块，用于获取所述位置群组的动态更新时间；
    位置对象获取模块，用于在根据所述动态更新时间确定的每个时间点，获取所述位置群组内的目标群组对象的目标位置，并查询所述目标区域内是否存在不属于所述位置群组的业务对象；以及
    群组对象更新模块，用于根据获取的目标位置和查询结果更新所述位置群组内的目标群组对象。
  18. 一种消息发送装置，包括：
    目标属性确定模块，用于获取订阅资源的事件通知判断标准，并根据所述事件通知判断标准确定要进行监控的目标属性；
    属性值获取模块，用于在所述目标属性的属性值发生变更时，获取所述目标属性的变更后的属性值；
    差量通知消息构建模块，用于在通知方式为差量通知方式的情况下，根据所述变更后的属性值构建差量通知消息；以及
    差量通知消息发送模块，用于发送所述差量通知消息。
  19. 一种电子设备，包括：
    存储器，存储有计算机程序；以及
    处理器，被配置为执行所述计算机程序，以实现权利要求1至8任一项所述的群组更新方法，或，权利要求9至16任一项所述的消息发送方法。
  20. 一种计算机可读存储介质，存储有计算机指令，当所述计算机指令由电子设备的处理器执行时，使得电子设备能够执行权利要求1至8中任一项所述的群组更新方法，或，权利要求9至16任一项所述的消息发送方法。
PCT/CN2021/072130 2020-01-17 2021-01-15 群组更新方法、消息发送方法及装置 WO2021143834A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020227020155A KR20220126288A (ko) 2020-01-17 2021-01-15 그룹 업데이트 방법, 메시지 전송 방법 및 장치
US17/791,957 US20230053967A1 (en) 2020-01-17 2021-01-15 Group updating method, message sending method, and apparatuses
EP21741956.3A EP4092961A4 (en) 2020-01-17 2021-01-15 GROUP UPDATE METHOD, MESSAGE SENDING METHOD AND APPARATUS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010054612.4A CN113141262A (zh) 2020-01-17 2020-01-17 群组更新方法、消息发送方法及装置
CN202010054612.4 2020-01-17

Publications (1)

Publication Number Publication Date
WO2021143834A1 true WO2021143834A1 (zh) 2021-07-22

Family

ID=76808572

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/072130 WO2021143834A1 (zh) 2020-01-17 2021-01-15 群组更新方法、消息发送方法及装置

Country Status (5)

Country Link
US (1) US20230053967A1 (zh)
EP (1) EP4092961A4 (zh)
KR (1) KR20220126288A (zh)
CN (1) CN113141262A (zh)
WO (1) WO2021143834A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115334025A (zh) * 2022-10-12 2022-11-11 北京百度网讯科技有限公司 去中心化的即时通信方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005032179A2 (en) * 2003-09-26 2005-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus to reduce dispatch delays in dispatch communication networks
CN104580363A (zh) * 2014-12-02 2015-04-29 深圳市普天宜通技术有限公司 基于位置信息的自动化集群调度数据处理方法及系统
CN105357645A (zh) * 2015-12-17 2016-02-24 百度在线网络技术（北京）有限公司 基于群组的地理位置信息交互方法和装置
CN106453050A (zh) * 2016-10-10 2017-02-22 腾讯科技（深圳）有限公司 基于社交应用的信息处理方法、系统以及相关设备
CN107770754A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种通知发送方法、装置和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070072591A1 (en) * 2005-09-23 2007-03-29 Mcgary Faith Enhanced directory assistance system and method including location search functions
US8577405B2 (en) * 2009-06-12 2013-11-05 Qualcomm Incorporated Systems, methods, and machine-readable media providing location-enabled group management
CN105228111A (zh) * 2014-06-13 2016-01-06 中兴通讯股份有限公司 资源订阅处理方法及装置
CN106850794A (zh) * 2017-01-24 2017-06-13 北京百度网讯科技有限公司 用于操作群组的方法和装置、服务器以及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005032179A2 (en) * 2003-09-26 2005-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus to reduce dispatch delays in dispatch communication networks
CN104580363A (zh) * 2014-12-02 2015-04-29 深圳市普天宜通技术有限公司 基于位置信息的自动化集群调度数据处理方法及系统
CN105357645A (zh) * 2015-12-17 2016-02-24 百度在线网络技术（北京）有限公司 基于群组的地理位置信息交互方法和装置
CN106453050A (zh) * 2016-10-10 2017-02-22 腾讯科技（深圳）有限公司 基于社交应用的信息处理方法、系统以及相关设备
CN107770754A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种通知发送方法、装置和系统

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115334025A (zh) * 2022-10-12 2022-11-11 北京百度网讯科技有限公司 去中心化的即时通信方法、装置、设备及存储介质
CN115334025B (zh) * 2022-10-12 2023-02-28 北京百度网讯科技有限公司 去中心化的即时通信方法、装置、设备及存储介质

Also Published As

Publication number Publication date
KR20220126288A (ko) 2022-09-15
EP4092961A1 (en) 2022-11-23
EP4092961A4 (en) 2024-04-10
CN113141262A (zh) 2021-07-20
US20230053967A1 (en) 2023-02-23

Similar Documents

Publication Publication Date Title
EP2547040B1 (en) Group communication method and device for use in group communication
CN111200657B (zh) 一种管理资源状态信息的方法和资源下载系统
US11677850B2 (en) Method, apparatus and system for notification
CN111726303A (zh) 一种流量控制方法、装置以及计算设备
EP3358786B1 (en) Information processing method in m2m and apparatus
US20170126828A1 (en) Sending Method and Apparatus and Computer Storage Medium of Notification Message
WO2016173280A1 (zh) 监控管理方法及装置
CN105282682B (zh) 一种实现资源属性通告的方法和公共业务实体
WO2017071118A1 (zh) 监控资源管理的方法、装置和cse、存储介质
CN110505591B (zh) 订阅服务实体、订阅终端及信息订阅方法和系统
WO2021143834A1 (zh) 群组更新方法、消息发送方法及装置
JP2022191247A (ja) バルクサブスクリプションのフィルタ
WO2015117342A1 (zh) 一种通知消息的发送方法、装置和系统
WO2015117482A1 (zh) 更新资源通告的方法、本地公共业务实体及系统
CN108337280B (zh) 一种资源更新方法及装置
CN112910796A (zh) 流量管理方法、装置、设备、存储介质以及程序产品
WO2021052289A1 (zh) 事件通知方法、系统、服务器设备、计算机存储介质
CN105282728A (zh) 一种删除通告资源的方法和公共业务实体
US10659938B2 (en) Registration method and communication method for application dedicated node (ADN), and nodes
WO2016082492A1 (zh) 一种原始资源通告的方法及相应的节点
CN113079029A (zh) 配置信息订阅方法及装置
CN115152196B (zh) 用于管理订阅者的订阅的设备和方法
CN115967564B (zh) 一种数据内容防护方法和存储介质
EP3487147A1 (en) Information synchronization method and device
CN114827071B (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: 21741956

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021741956

Country of ref document: EP

Effective date: 20220817