WO2024050698A1 - Procédés et appareils de demande d'abonnement, dispositif et support de stockage - Google Patents

Procédés et appareils de demande d'abonnement, dispositif et support de stockage Download PDF

Info

Publication number
WO2024050698A1
WO2024050698A1 PCT/CN2022/117344 CN2022117344W WO2024050698A1 WO 2024050698 A1 WO2024050698 A1 WO 2024050698A1 CN 2022117344 W CN2022117344 W CN 2022117344W WO 2024050698 A1 WO2024050698 A1 WO 2024050698A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
request
terminal
field
value
Prior art date
Application number
PCT/CN2022/117344
Other languages
English (en)
Chinese (zh)
Inventor
包永明
吕小强
茹昭
张军
杨宁
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/117344 priority Critical patent/WO2024050698A1/fr
Publication of WO2024050698A1 publication Critical patent/WO2024050698A1/fr

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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • This application relates to the field of communication technology, and in particular to a subscription request method, device, equipment and storage medium.
  • the first terminal can initiate a subscription request to the second terminal and wait for a response from the second terminal to activate or cancel the subscription.
  • the first terminal Take the first terminal as the subscription initiator and the second terminal as the subscription responder as an example.
  • the first terminal sends a subscription request to the second terminal, and the subscription request carries a keep subscription field (KeepSubscriptions).
  • KeepSubscriptions when the value of this field is False, all subscription relationships between the first terminal and the second terminal will be cancelled, which will cause the cancellation of the subscription relationship to have certain limitations and be inflexible.
  • Embodiments of the present application provide a subscription request method, device, equipment and storage medium.
  • the second terminal can determine the subscription relationship to be canceled based on the subscription identification field, thereby improving the efficiency of the subscription. Flexibility, the technical solutions are as follows:
  • a subscription request method is provided, the method is executed by the first terminal, and the method includes:
  • the subscription request carries a subscription identification field.
  • a subscription request method is provided.
  • the method is executed by a second terminal.
  • the method includes:
  • the subscription request carries a subscription identification field.
  • a subscription request device which device includes:
  • a sending module used to send a subscription request to the second terminal
  • the subscription request carries a subscription identification field.
  • a subscription request device which device includes:
  • a receiving module configured to receive a subscription request sent by the first terminal
  • the subscription request carries a subscription identification field.
  • a first terminal includes a memory and a processor; at least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the subscription request as described above. method.
  • a second terminal which includes a memory and a processor; at least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the subscription request as described above. method.
  • a computer-readable storage medium is provided, and a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the subscription request method as described above.
  • a chip includes programmable logic circuits and/or program instructions, and is used to implement the subscription request method as described above when the electronic device installed with the chip is running.
  • a computer program product includes computer instructions.
  • the computer instructions are stored in a computer-readable storage medium.
  • the processor reads and executes the computer instructions from the computer-readable storage medium to implement Subscription request method as described above.
  • the second terminal can determine the subscription relationship to be canceled based on the subscription identification field, thereby improving the flexibility of the subscription.
  • Figure 1 is a schematic diagram of a subscription process provided by an exemplary embodiment of the present application.
  • Figure 2 is a schematic diagram of a data model of a terminal provided by an exemplary embodiment of the present application.
  • Figure 3 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 4 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 5 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 6 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 7 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 8 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 9 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 10 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • Figure 11 is a schematic diagram of a subscription request device provided by an exemplary embodiment of the present application.
  • Figure 12 is a schematic diagram of a subscription request device provided by an exemplary embodiment of the present application.
  • Figure 13 is a block diagram of a communication device provided by an exemplary embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced long term evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi wireless fidelity
  • 5G fifth-generation communication
  • mobile communication systems will not only support traditional communications, but also support Internet of Things (IoT) communications, etc.
  • IoT Internet of Things
  • the embodiments of the present application can be applied to Internet of Things communication systems.
  • the IoT communication system includes multiple terminals, and information exchange and communication can be realized between each two terminals.
  • the terminal can also be called user equipment (User Equipment, UE).
  • the terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (Personal Digital Assistant, PDA) device, or a device with wireless communication capabilities Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future evolved Public Land Mobile Networks (PLMN) ) terminal equipment in the network, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • the terminal can be deployed on land, including indoors or outdoors, handheld, worn or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) wait).
  • the terminal may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal device.
  • wireless terminal equipment in industrial control wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid, Wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • the terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • the "instruction” mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
  • correlate can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.
  • predefinition can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminals and network devices).
  • devices for example, including terminals and network devices.
  • predefined can refer to what is defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.
  • Figure 1 is a schematic diagram of a subscription process provided by an exemplary embodiment of the present application.
  • the first terminal can initiate a subscription request to the second terminal and wait for a response from the second terminal to activate or cancel the subscription.
  • the subscription process includes the following steps:
  • Step 1 The subscription initiator initiates a subscription request to the subscription responder.
  • the subscription request is used to request the subscription responder to subscribe to a target resource.
  • the target resource may specifically include attributes and/or events, and the requested attributes and/or events may be one or more.
  • the subscription request carries at least one field, and at least one field is used to indicate the resource information of this subscription.
  • the MinIntervalFloor field is used to indicate the requested lower (lowest) minimum interval value. It can also be understood that the value of the minimum interval time field is used to indicate the boundary value of the requested minimum reporting time interval, and the boundary value is in seconds (s). According to this field, when the subscription responder needs to report multiple data, if the reporting time interval defined by the subscription responder for multiple data is less than the minimum interval, the multiple data will be cached, and after the minimum interval is reached, the multiple data will be cached. Make a report.
  • the maximum interval time (MaxIntervalCeil) field is used to indicate the requested upper limit (highest) maximum interval value. It can also be understood that the value of the maximum interval time field is used to indicate the boundary value of the maximum reporting timeout time of the request, and the boundary value is in seconds (s). According to this field, the subscription responder should report data at least once within a time period that does not exceed this boundary value.
  • the AttributeRequests field is used to indicate a list of zero or more request paths for cluster attribute data.
  • the cluster optionally includes two roles: user side (Client) and server side (Server).
  • the user side belongs to the control end, and the server side belongs to the controlled end.
  • the DataVersionFilters field is used to indicate a list of zero or more cluster instance data versions.
  • the data version filter field is optional when the attribute request list exists. Among them, if the data version (DataVersion) of the data reported twice is the same, only the DataVersion will be reported the second time, and the attribute value does not need to be reported.
  • the EventRequests field is used to indicate a list of zero or more request paths for cluster events.
  • the EventFilters field is used to indicate a list of zero or more minimum events for each specific node, and can also be understood as a filtering condition for requesting event reporting.
  • the data read in the network structure domain range list is restricted to the accessed network structure domain.
  • the subscription process is based on the Matter protocol.
  • Matter Protocol also known as the Project Connected Home over IP
  • Project Connected Home over IP is a smart home open source standard project that aims to develop and promote a new connection protocol to simplify the development costs of smart home equipment manufacturers and improve different Compatibility between manufacturers’ smart home products.
  • Matter Protocol will support communication between smart home devices, mobile applications and cloud services, defining a specific set of Internet protocol-based network technologies for devices.
  • Node represents a device node and belongs to a logical device
  • Endpoint A node contains multiple endpoints, each endpoint represents a service instance or a virtual device, and the device type corresponding to the endpoint can be indicated by device_type;
  • Cluster One endpoint contains multiple clusters. Clusters are elements that build function sets. Clusters optionally include two roles: user side and server side. The user side belongs to the control side and the server side belongs to the controlled side;
  • a cluster contains 0 or more attributes, which are used to describe the functional units in the functional set;
  • a cluster contains 0 or more commands, which are used to describe the control of functional units
  • Event A cluster contains 0 or more events. Events are used to describe records of specific behaviors that have occurred in the past of functional units;
  • the data model of the device will be explained as an example.
  • the equipment type of the root node (RootNode) of the vehicle equipment is stored under endpoint 0 (Endpoint0)
  • the air-conditioning equipment type of the vehicle equipment is stored under endpoint 5 (Endpoint5).
  • the clusters included under endpoint 5 include a temperature control cluster and a fan cluster.
  • the attributes contained in the temperature control cluster optionally include temperature attribute values
  • the commands contained in the temperature control cluster optionally include increase temperature commands and lower temperature commands
  • the events contained in the temperature control cluster optionally include temperature abnormality alarms. event.
  • the attribute request field can be expressed as follows: AttributeRequests[endpoint-id/cluster-id/attribute-id, endpoint-id/cluster-id/attribute-id,...];
  • the event request field can be expressed as follows: EventRequests [endpoint-id/cluster-id/event-id,endpoint-id/cluster-id/event-id,...].
  • Step 2 The subscription response direction sends the first data report to the subscription initiator.
  • the subscription responder After the subscription responder receives the subscription request initiated by the subscription initiator, it needs to report data once.
  • the subscription responder can report the resource information to be subscribed based on the attribute request field and event request field carried in the subscription request.
  • Step 3 The subscription initiator reports the success or failure status to the subscription responder.
  • step 3 may be implemented as: the subscription initiator sends success status information to the subscription responder.
  • Step 4 The subscription responder confirms whether to return a subscription response based on the status information returned by the subscription initiator.
  • the subscription responder can determine whether it needs to return a subscription response to the subscription initiator based on the status information received.
  • the subscription responder determines that it needs to return a subscription response to the subscription initiator and generates parameter data of the subscription response.
  • Step 5 After receiving the success status sent by the subscription initiator, the subscription responder returns a subscription response.
  • the subscription responder sends the generated parameter data to the subscription initiator through a subscription response message.
  • the parameter fields carried in the subscription response are shown in Table 2:
  • Subscription ID uint32 force Used to identify a subscription maximum interval uint16 force The final maximum reported timeout for a subscription
  • the subscription identification (SubscriptionID) field is used to identify a subscription.
  • the subscription identification field is generated based on the subscription request sent by the subscription initiator to the subscription responder.
  • the maximum interval (MaxInterval) field is used to indicate the maximum time interval finally determined after negotiation between the subscription initiator and the subscription responder. It can also be understood that the value of the maximum interval field is used to indicate the boundary value of the negotiated maximum reporting timeout, and the boundary value is in seconds (s). According to this field, the subscribing responder should report the data for the second time within a time not exceeding this boundary value.
  • Step 6 The subscription response direction sends the second data report to the subscription initiator.
  • the subscription responder after confirming that the subscription response is returned to the subscription initiator, the subscription responder sends a second data report to the subscription initiator.
  • the second data reporting should be completed within a time not exceeding the boundary value indicated by the maximum interval field.
  • Step 7 The subscription initiator sends a status response to the subscription responder.
  • the subscription initiator after receiving the second data report sent by the subscription responder, the subscription initiator will return a status response to the subscription responder to achieve the purpose of keeping the subscription connection alive.
  • the subscription request carries a keep subscription field. If the value of this field is False, all subscriptions between the subscription initiator and the subscription responder will be canceled. This will cause the cancellation of subscriptions to have certain limitations and is not enough. flexible.
  • the embodiment of the present application provides a subscription request method, which can carry a subscription identification field in the subscription request, so that the second terminal (that is, the subscription responder) determines the response, all or Partial cancellation, thereby increasing the flexibility of your subscription.
  • Figure 3 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application. The method is executed by the first terminal. The method includes the following steps:
  • Step 102 Send a subscription request to the second terminal.
  • the subscription request carries a subscription identification field.
  • the subscription identification field is used to identify one or more properties and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the value of the subscription identification field is used to indicate a request for a new subscription; in other embodiments, the value of the subscription identification field corresponds to an existing subscription, and the existing subscription may include at least one attribute. and/or events.
  • the value of the subscription identification field is 0, which is used to indicate a request for a new subscription; for another example, the value of the subscription identification field is 1, which is used to indicate an existing subscription, and the subscription identification 1 is used to indicate that a subscription has already been subscribed.
  • n attributes and m events are examples of events.
  • the mobile terminal initiates a subscription request to the smart home appliance.
  • the subscription request carries at least one subscription identification field, and each subscription identification field corresponds to different attributes and/or or event.
  • smart home appliances have 5 attributes and 5 events, and the subscription request carries two subscription identification fields.
  • the first subscription identification field is used to identify the 3 attributes and 2 events of the subscription
  • the second subscription identification field is used to identify the 3 attributes and 2 events of the subscription. 1 property and 1 event that identifies the subscription.
  • the subscription request also carries at least one of the following fields:
  • the parameter fields carried in the subscription request are as shown in Table 3:
  • the SubscriptionID field is used to identify one or more properties and/or events of the subscription.
  • the MinIntervalFloor field is used to indicate the requested lower (lowest) minimum interval value. It can also be understood that the value of the minimum interval time field is used to indicate the boundary value of the requested minimum reporting time interval, and the boundary value is in seconds (s). According to this field, when the subscription responder needs to report multiple data, if the reporting time interval defined by the subscription responder for multiple data is less than the minimum interval, the multiple data will be cached, and after the minimum interval is reached, the multiple data will be cached. Make a report.
  • the maximum interval time (MaxIntervalCeil) field is used to indicate the requested upper limit (highest) maximum interval value. It can also be understood that the value of the maximum interval time field is used to indicate the boundary value of the maximum reporting timeout time of the request, and the boundary value is in seconds (s). According to this field, the subscription responder should report data at least once within a time period that does not exceed this boundary value.
  • the AttributeRequests field is used to indicate a list of zero or more request paths for cluster attribute data.
  • the DataVersionFilters field is used to indicate a list of zero or more cluster instance data versions.
  • the data version filter field is optional when the attribute request list exists.
  • the EventRequests field is used to indicate a list of zero or more request paths for cluster events.
  • the EventFilters field is used to indicate a list of zero or more minimum events for each specific node, and can also be understood as a filtering condition for requesting event reporting.
  • the data read in the network structure domain range list is restricted to the accessed network structure domain.
  • the subscription request method provided by the embodiments of this application is based on the Matter protocol.
  • the attribute request field and/or the event request field are optional fields. Taking the attribute request field as an example, there are three situations: the subscription request does not carry the attribute request field; the subscription request carries the attribute request field and the list is all empty; the subscription request carries the attribute request field and there is data information in the list , this data information can be set according to actual needs.
  • the event request field is similar and can be used as a reference without going into details.
  • the default list corresponding to the attribute request field and/or the event request field is a wildcard.
  • the wildcard can be set according to actual needs, such as setting it as a universal value, or setting it as an asterisk, etc.
  • the subscription request carries the attribute request field and the event request field and the list is all empty, it can be considered that a status error has occurred, and the second terminal needs to report the error status to the first terminal.
  • the subscription request when the subscription request carries an attribute request field and/or an event request field and there is data information in the list, a corresponding response can be made based on the data information in the list, which will be detailed below.
  • the subscription request is used to request the establishment of a new subscription relationship; or, the subscription request is used to request the cancellation of a subscribed target resource.
  • the subscription identification field is the first value
  • the subscription request is used to request the establishment of a new subscription relationship
  • the subscription identification field is other values than the first value
  • the subscription request is used to request the cancellation of an existing subscription. target resources.
  • the subscribed target resource is used to indicate all or part of the subscription relationship between the first terminal and the second terminal.
  • the subscription request is used to request the establishment of a new subscription relationship; when the value of the subscription identification field is 0xFFFFFFFF, the subscription request is used to request the cancellation of all subscriptions of the first terminal to the second terminal. Relationship; when 0 ⁇ subscription identification field ⁇ 0xFFFFFF, that is, when the value of the subscription identification field is non-0 and non-F, the subscription request is used to request the cancellation of part of the subscription relationship between the first terminal and the second terminal, and the canceled part of the subscription relationship Determined based on subscription request.
  • the second terminal can perform status reporting and subscription response judgment with the first terminal.
  • the subscription identification field is used to trigger the second terminal to report the status of resource information to the first terminal at least based on the value of the subscription identification field; and/or the subscription identification field is used to trigger the second terminal to report the status of resource information to the first terminal based at least on the value of the subscription identification field.
  • a subscription response is sent to the first terminal.
  • the subscription response is used to indicate the cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the second terminal may make a determination based only on the value of the subscription identification field. For example, when the value of the subscription identification field is 0xFFFFFFFF, all subscription relationships between the first terminal and the second terminal are cancelled. For another example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and the subscription request does not carry the attribute request field and/or event request field (that is, the default is a wildcard), all subscription relationships corresponding to the subscription identification field are cancelled.
  • the second terminal may make a determination based on the value of the subscription identification field and other fields carried in the subscription request.
  • the subscription request carrying the attribute request field and the event request field as an example, when the attribute request field and the event request field are both empty, the second terminal sends an error status report to the first terminal, and the error status report is used to indicate the subscription.
  • the request does not indicate the target resource corresponding to the subscription ID field. It can also be understood that the error status reporting is used to indicate that the attribute request field and event request field carried in the subscription request are both empty, resulting in resource information errors.
  • 0 ⁇ subscription identification field when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and both the attribute request field and the event request field are wildcards, cancel all subscription relationships corresponding to the subscription identification field.
  • 0 ⁇ subscription identification field when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and one of the attribute request fields or event request fields is not a wildcard, cancel the subscription relationship of the data information indicated by the subscription identification field, and cancel the remaining data information not indicated by the subscription identification field. Perform data reporting.
  • the second terminal may determine the status report and/or subscription response to send to the first terminal according to the value of the subscription identification field carried in the subscription request.
  • a subscription identification field corresponds to a status report or a subscription response sent by the second terminal to the first terminal. It should be understood that the corresponding relationship between the value of the subscription identification field and the status report and/or subscription response sent by the second terminal to the first terminal can be set according to actual needs, and is not limited in this application.
  • the subscription request is used to request the establishment of a new subscription relationship.
  • the second terminal sends an error status report to the first terminal.
  • the error status report is used to indicate that the subscription request does not indicate the target resource corresponding to the subscription identification field.
  • the second terminal sends a first subscription response to the first terminal, and the first subscription response carries The subscription identification field is not the first value.
  • the subscription identification field carried in the first subscription response is generated by the second terminal based on the subscription request, and the first terminal and the second terminal can determine the existing subscription based on the subscription identification field.
  • the subscription request is used to request to cancel all subscription relationships between the first terminal and the second terminal.
  • the second terminal sends a second subscription response to the first terminal, and the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal. It should be understood that what is canceled are all existing subscriptions of the first terminal and the second terminal. When the subscription identification field is the second value, all subscription relationships between the first terminal and the second terminal are canceled regardless of whether the subscription request carries other fields.
  • the subscription request is used to request cancellation of an existing subscription.
  • the third value is generated by the second terminal based on historical subscription requests initiated by the first terminal before this subscription request. It should be understood that the third value is a numerical value that is different from the first value and the second value. Take the first value as 0, the second value as 0xFFFFFFFF as an example, and the third value as a non-0 and non-F value.
  • the second terminal sends an error status report to the first terminal.
  • the error status report is used to indicate that the subscription request does not indicate the target resource corresponding to the subscription identification field.
  • both the default attribute request field and the event request field are the fourth value (that is, a wildcard)
  • the second terminal sends a third subscription response to the first terminal, and the third subscription response is used to indicate the cancellation of the first terminal's request for the third value. All subscription relationships corresponding to the subscription identification field of the two terminals.
  • the subscription request does not carry the attribute request field and the event request field
  • the default attribute request field and the event request field are both the fourth value.
  • the fourth value can also be carried in the subscription request. That is, when both the attribute request field and the event request field carried in the subscription request have the fourth value, the second terminal sends the third subscription response to the first terminal.
  • the attribute request field and/or the event request field is a fourth value. It can be understood that the list identifier corresponding to the attribute request field and/or the event request field is a fourth value. For example, if the fourth value is a wildcard, then the list identifier corresponding to the attribute request field and/or event request field is a wildcard.
  • the second terminal When there is at least a fifth value in the list corresponding to the attribute request field and the event request field, the second terminal sends a fourth subscription response to the first terminal.
  • the fourth subscription response is used to indicate the cancellation of the first terminal's request for the second terminal. Regarding the subscription relationship indicated by the fifth value.
  • the first value, the second value, the third value, the fourth value and the fifth value can be set according to actual needs.
  • the first value is 0,
  • the second value is 0xFFFFFFFF, 0 ⁇ the third value ⁇ 0xFFFFFFFF, the fourth value is a wildcard, and the fifth value is used to indicate a specific attribute and/or event.
  • the third value can be understood as a non-0 and non-F value.
  • the first terminal is a mobile terminal
  • the second terminal is a smart home appliance
  • the cluster of smart home appliances includes 5 attributes and 5 events.
  • the mobile terminal has no subscription relationship with smart home appliances.
  • the smart home appliance when the mobile terminal sends the first subscription request to the smart home appliance, the value of the subscription identification field is 0, and the attribute request field and event request field are both empty, the smart home appliance sends an error status report to the mobile terminal, The error status reporting is used to indicate that the first subscription request does not indicate the target resource corresponding to the subscription identification field.
  • the mobile terminal sends the first subscription request to the smart home appliance.
  • the value of the subscription identification field is 0, and the attribute request field includes 3 attributes and the event request field includes 2 events.
  • the smart home appliance returns the first subscription response to the mobile terminal.
  • the subscription identification field carried in the first subscription response is not 0 or 0xFFFFFFFF, and the subscription identification field is generated according to the subscription request.
  • the value of the subscription identification field carried in the first subscription response is 3.
  • the mobile terminal sends a second subscription request to the smart home appliance.
  • the value of the subscription identification field is 0, and the attribute request field includes 2 attributes and the event request field includes 3 events.
  • the smart home appliance returns a first subscription response to the mobile terminal, and the subscription identification field carried in the first subscription response is 4.
  • the mobile terminal sends a third subscription request to the smart home appliance.
  • the value of the subscription identification field carried in the third subscription request there are the following situations:
  • the smart home appliance sends a second subscription response to the mobile terminal.
  • the second subscription response is used to indicate the cancellation of the existing subscription of the smart home appliance by the mobile terminal. All subscription relationships, that is, cancel all subscription relationships established based on the first subscription request and the second subscription request (all subscriptions with subscription identification fields 3 and 4).
  • the smart home appliance sends an error status report to the mobile terminal, and the error status report Used to indicate that the subscription request does not indicate the target resource corresponding to the subscription identification field.
  • the smart home appliance sends the third subscription response to the mobile terminal.
  • the subscription response is used to indicate the cancellation of all subscription relationships corresponding to the subscription identification field between the first terminal and the second terminal, that is, to cancel the subscription relationships of three attributes and two events established based on the first subscription request.
  • the smart home appliance sends the third Four subscription responses.
  • the fourth subscription response is used to instruct the first terminal to cancel the subscription of the second terminal to the data information indicated by the subscription identification field. For example, if there are 2 attributes in the attribute request field (that is, there is at least a fifth value in the list corresponding to the attribute request field list), and the event request field is a wildcard, then the subscription relationship of the 2 attributes and 3 events will be cancelled, and the remaining 1 property remains.
  • the subscription relationships of all events corresponding to the subscription identification field will be cancelled. If the event request field includes a specific value corresponding to at least one event, the subscription relationship for all events corresponding to the subscription identification field will not be cancelled, but only the subscription relationship for the event corresponding to the specific value will be cancelled.
  • the smart home appliance sends the fourth Subscription response, the fourth subscription response is used to indicate canceling the subscription relationship between the first terminal and the second terminal regarding the data information indicated by the subscription identification field. For example, if there is 1 attribute in the attribute request field, the subscription relationship of 1 attribute will be cancelled, and the remaining 1 attribute and 3 events will still exist.
  • the subscription identification field is carried in the subscription request, so that the second terminal can determine the subscription relationship to be canceled based on the subscription identification field, thereby improving the flexibility of the subscription. sex.
  • Figure 4 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application. The method is executed by the second terminal. The method includes the following steps:
  • Step 202 Receive the subscription request sent by the first terminal.
  • the subscription request carries a subscription identification field.
  • the subscription identification field is used to identify one or more properties and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure domain filter field .
  • the subscription request method provided by the embodiments of this application is based on the Matter protocol.
  • the subscription request is used to request the establishment of a new subscription relationship; or, the subscription request is used to request the cancellation of a subscribed target resource.
  • the subscription identification field is used by the second terminal to report the status of the resource information to the first terminal based on at least the value of the subscription identification field; and/or the subscription identification field is used by the second terminal based on at least the value of the subscription identification field.
  • the value sends a subscription response to the first terminal, and the subscription response is used to indicate the cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the second terminal may make a determination based only on the value of the subscription identification field. For example, when the value of the subscription identification field is 0xFFFFFFFF, all subscription relationships between the first terminal and the second terminal are cancelled. For another example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and the subscription request does not carry the attribute request field and/or event request field (that is, the default is a wildcard), all subscription relationships corresponding to the subscription identification field are cancelled.
  • the second terminal may make a determination based on the value of the subscription identification field and other fields carried in the subscription request. For example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and both the attribute request field and the event request field are wildcards, cancel all subscriptions corresponding to the subscription identification field. For another example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and one of the attribute request fields or event request fields is not a wildcard, cancel the subscription relationship of the data information indicated by the subscription identification field, and cancel the remaining data information not indicated by the subscription identification field. Perform data reporting.
  • the second terminal may determine the status report and/or subscription response to send to the first terminal according to the value of the subscription identification field carried in the subscription request.
  • a subscription identification field corresponds to a status report or a subscription response sent by the second terminal to the first terminal. It should be understood that the corresponding relationship between the value of the subscription identification field and the status report and/or subscription response sent by the second terminal to the first terminal can be set according to actual needs, and is not limited in this application.
  • the subscription request can be used to request the establishment of a new subscription relationship; or, the value of the subscription identification field corresponds to an existing subscription, and the existing subscription may include at least An attribute and/or event, subscription request, may be used to request cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the subscription identification field is carried in the subscription request, so that the second terminal can determine the subscription relationship to be canceled based on the subscription identification field, thereby improving the flexibility of the subscription. sex.
  • Figure 5 is a flow chart of a subscription request method provided by an exemplary embodiment of the present application. The method includes the following steps:
  • Step 302 The first terminal sends a subscription request to the second terminal.
  • the subscription request carries a subscription identification field.
  • the subscription identification field is used to identify one or more properties and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure domain filter field .
  • the subscription request method provided by the embodiments of this application is based on the Matter protocol.
  • the subscription request is used to request the establishment of a new subscription relationship; or, the subscription request is used to request the cancellation of a subscribed target resource.
  • the subscription identification field is used by the second terminal to report the status of the resource information to the first terminal based on at least the value of the subscription identification field; and/or the subscription identification field is used by the second terminal based on at least the value of the subscription identification field.
  • the value sends a subscription response to the first terminal, and the subscription response is used to indicate the cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the second terminal may make a determination based only on the value of the subscription identification field. For example, when the value of the subscription identification field is 0xFFFFFFFF, all subscription relationships between the first terminal and the second terminal are cancelled. For another example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and the subscription request does not carry the attribute request field and/or event request field (that is, the default is a wildcard), all subscription relationships corresponding to the subscription identification field are cancelled.
  • the second terminal may make a determination based on the value of the subscription identification field and other fields carried in the subscription request. For example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and both the attribute request field and the event request field are wildcards, cancel all subscriptions corresponding to the subscription identification field. For another example, when 0 ⁇ subscription identification field ⁇ 0xFFFFFFFF and one of the attribute request fields or event request fields is not a wildcard, cancel the subscription relationship of the data information indicated by the subscription identification field, and cancel the remaining data information not indicated by the subscription identification field. Perform data reporting.
  • the second terminal may determine the status report and/or subscription response to send to the first terminal according to the value of the subscription identification field carried in the subscription request.
  • a subscription identification field corresponds to a status report or a subscription response sent by the second terminal to the first terminal. It should be understood that the corresponding relationship between the value of the subscription identification field and the status report and/or subscription response sent by the second terminal to the first terminal can be set according to actual needs, and is not limited in this application.
  • the subscription identification field is carried in the subscription request, so that the second terminal can determine the subscription relationship to be canceled based on the subscription identification field, thereby improving the flexibility of the subscription. sex.
  • the attribute request field and/or the event request field are optional fields in the subscription request.
  • the subscription request carries attribute request fields and event request fields and the lists are all empty. At this time, the second terminal needs to send an error status report to the first terminal.
  • Figure 6 shows a flow chart of the subscription request method provided by an exemplary embodiment of the present application.
  • the subscription request method provided by the embodiment of the present application also includes step 303, specifically as follows:
  • the subscription request carries an attribute request field and an event request field, and both the attribute request field and the event request field are empty.
  • step 303 is performed, as follows:
  • Step 303 The second terminal sends an error status report to the first terminal.
  • the error status reporting is used to indicate that the subscription request does not indicate the target resource corresponding to the subscription identification field.
  • the attribute request field is to request a list of attributes that can be reported
  • the event request field is to request a list of reportable events.
  • the subscription request carries an attribute request field and an event request field
  • the second terminal cannot determine the attributes and events that the first terminal wants to subscribe to, and therefore will not be able to determine that it needs to send a request to the first terminal. Data information reported by the terminal.
  • the second terminal needs to send an error status report to the first terminal, so that the first terminal knows that the attribute request field and the event request field do not indicate the target resource corresponding to the subscription identification field. It can also be understood that the error status reporting is used to indicate that the attribute request field and event request field carried in the subscription request are both empty, resulting in resource information errors.
  • the second terminal sends an error when the attribute request field and the event request field are both empty. Status reporting.
  • the second terminal can send different information to the first terminal.
  • the following will be explained in detail based on the different values of the subscription identification field:
  • the subscription identification field is the first value.
  • the first subscription request is used to request the establishment of a new subscription relationship.
  • the specific value of the first value can be set according to actual needs.
  • the first value is 0.
  • both the attribute request field and the event request field carried in the first subscription request are empty.
  • the second terminal sends an error status report to the first terminal.
  • the error status report is used to indicate that the first subscription request does not indicate the target resource corresponding to the first subscription identification field.
  • the first subscription request carries an attribute request field and an event request field, and any one of them is not empty.
  • the second terminal needs to return a subscription response to the first terminal, as follows:
  • FIG. 7 shows a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • step 302 can be implemented as step 3021.
  • the subscription request method provided by the embodiment of the present application also includes step 304, specifically as follows:
  • Step 3021 The first terminal sends a first subscription request to the second terminal.
  • the first subscription request carries a first subscription identification field
  • the first subscription identification field is a first value
  • the first subscription request is used to request the establishment of a new subscription relationship.
  • the first subscription identification field is used to identify one or more attributes and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the first subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure field. Filter fields.
  • the first subscription request carries the minimum interval time field and the maximum interval time field, and step 304 is performed at this time.
  • the first subscription request carries a minimum interval time field and a maximum interval time field, which can also be understood as mandatory requirements for the minimum interval time field and the maximum interval time field.
  • step 304 is as follows:
  • Step 304 If the attribute request field and/or the event request field carried in the first subscription request are not empty, the second terminal sends a first subscription response to the first terminal.
  • the subscription identification field carried in the first subscription response is not the first value.
  • the subscription identification field carried in the first subscription response is generated by the second terminal based on the first subscription request, and the first terminal and the second terminal can determine an existing subscription relationship based on the subscription identification field.
  • the attribute request field is to request a list of attributes that can be reported
  • the event request field is to request a list of reportable events.
  • the second terminal can determine the attributes and events that the first terminal wants to subscribe to, so It can respond to the subscription relationship indicated by the first subscription identification field, and report data on attributes and events that the first terminal wants to subscribe to.
  • the second terminal After determining that a subscription response needs to be returned, the second terminal (that is, the subscription responder) needs to generate parameter data of the first subscription response corresponding to the first subscription request.
  • the first subscription response at least carries a subscription identification field. It should be understood that this field is different from the first subscription identification field. It is an identification field generated by the second terminal based on the first subscription request and is used to identify relevant information of this subscription.
  • the second terminal sends the first subscription response to the first terminal.
  • the second terminal may also report the resource information of the attribute and/or field indicated by the first subscription identification field to the first terminal.
  • the first terminal is a mobile terminal
  • the second terminal is a smart home appliance
  • the first value is 0 as an example.
  • Smart home appliances correspond to 5 attributes and 5 events.
  • the first subscription identification field carried in the first subscription request is used to identify the 3 attributes and 2 events requested to be subscribed.
  • the smart home appliance when the first subscription identification field is 0, and the attribute request field and the event request field are both empty, the smart home appliance sends an error status report to the mobile terminal, and the error status report is used to indicate that the first subscription request does not indicate the first The target resource corresponding to the subscription identification field.
  • the smart home appliance sends the first subscription response to the mobile terminal.
  • the subscription identification field carried in a subscription response is not 0 or 0xFFFFFF.
  • the smart home appliance reports data information of at least one attribute and/or event to the mobile terminal. At least one attribute and/or event is determined among 3 attributes and 2 events according to the attribute request field and the event request field.
  • the subscription identification field is the second value.
  • the second subscription request is used to request to cancel all subscription relationships between the first terminal and the second terminal.
  • the specific value of the second value can be set according to actual needs.
  • the second value is 0xFFFFFFFF.
  • FIG. 8 shows a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • step 302 can be implemented as step 3022.
  • the subscription request method provided by the embodiment of this application also includes step 305, specifically as follows:
  • Step 3022 The first terminal sends a second subscription request to the second terminal.
  • the second subscription request carries a second subscription identification field
  • the second subscription identification field is a second value
  • the second subscription request is used to request cancellation of all subscription relationships between the first terminal and the second terminal.
  • the second subscription identification field is used to identify one or more attributes and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the second subscription request also carries at least one of the following fields: minimum interval field; maximum interval field; attribute request field; data version filter field; event request field; event filter field; network structure field. Filter fields.
  • Step 305 The second terminal sends a second subscription response to the first terminal.
  • the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal. It should be understood that all canceled subscription relationships between the first terminal and the second terminal are existing subscription relationships.
  • both the attribute request field and the event request field are empty and need to be configured through a subscription request. It can be understood that the second subscription request carries the attribute request field and/or the event request field, and the attribute request field and/or the event request field are empty.
  • step 305 can be implemented as follows:
  • the second terminal sends a second subscription response to the first terminal.
  • the second subscription request is used to request to cancel all subscription relationships between the first terminal and the second terminal. Based on this, it can also be understood that no matter whether the attribute request field and the event request field carried in the second subscription request are empty or wildcard, when the second subscription identification field is the second value, the first terminal pair is cancelled. All subscription relationships of the second terminal.
  • the second terminal when the second subscription identification field is the second value, the second terminal no longer reports data information to the first terminal.
  • the first terminal is a mobile terminal
  • the second terminal is a smart home appliance
  • the second value is 0xFFFFFFFF.
  • Smart home appliances correspond to 5 attributes and 5 events, and there are 2 subscription relationships between mobile terminals and smart home appliances.
  • the smart home appliance sends a second subscription response to the mobile terminal, and the second subscription response is used to indicate the cancellation of the two subscription relationships between the mobile terminal and the smart home appliance.
  • the subscription identification field is the third value.
  • the third subscription request is used to request cancellation of an existing subscription relationship.
  • the third value is generated by the second terminal based on historical subscription requests initiated by the first terminal before this subscription request.
  • the third value is a value that is different from the first value and the second value. Taking the first value as 0 and the second value as 0xFFFFFFFF as an example, then 0 ⁇ third value ⁇ 0xFFFFFFFF can also be The third value is understood as a non-0 non-F value.
  • FIG. 9 shows a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • step 302 can be implemented as step 3023.
  • the subscription request method provided by the embodiment of this application also includes step 3061, as follows:
  • Step 3023 The first terminal sends a third subscription request to the second terminal.
  • the third subscription request carries a third subscription identification field, and the third subscription identification field takes a third value.
  • the third subscription identification field is used to identify one or more attributes and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the third subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure field. Filter fields.
  • both the attribute request field and the event request field carried in the third subscription request are empty.
  • the second terminal sends an error status report to the first terminal.
  • the error status report is used to indicate that the third subscription request does not indicate the target resource corresponding to the third subscription identification field.
  • the third subscription request carries an attribute request field and an event request field, and any one of them is not empty.
  • the second terminal can return a subscription response to the first terminal based on the attributes and/or events that are not empty, as follows:
  • Step 3061 The second terminal sends a third subscription response to the first terminal.
  • the third subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal regarding the third subscription identification field.
  • the attribute request field and/or the event request field carried in the third subscription request is the fourth value, or the third subscription request does not carry the attribute request field and/or the event request field. Used to request cancellation of all subscription relationships corresponding to the third subscription identification field.
  • the fourth value may be a wildcard character.
  • both the attribute request field and the event request field can be configured as wildcards. It can be understood that if the subscription request does not carry the attribute request field and/or event request field, the default attribute request field and/or event request field will be wildcards.
  • both the attribute request field and the event request field are wildcards and can be configured through the third subscription request. It can be understood that the third subscription request carries the attribute request field and/or the event request field, and the attribute request field and/or the event request field are defined as wildcards.
  • step 3061 can be implemented as follows:
  • the second terminal When the third subscription request does not carry the attribute request field and the event request field, the second terminal sends a third subscription response to the first terminal;
  • the second terminal sends a third subscription response to the first terminal.
  • the third subscription request is used to request cancellation of an existing subscription relationship.
  • the second terminal sends a third subscription response to the first terminal to cancel the third value corresponding to the second terminal from the first terminal. All properties and events for existing subscriptions.
  • FIG. 10 shows a flow chart of a subscription request method provided by an exemplary embodiment of the present application.
  • step 302 can be implemented as step 3023.
  • the subscription request method provided by the embodiment of this application also includes step 3062, specifically as follows:
  • Step 3023 The first terminal sends a third subscription request to the second terminal.
  • the third subscription request carries a third subscription identification field, and the third subscription identification field takes a third value.
  • the third subscription identification field is used to identify one or more attributes and/or events of the subscription.
  • a subscription identification field can be used to identify n attributes and m events of the subscription.
  • n and m are positive integers greater than 0, and n and m can be the same or different.
  • the third subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure field. Filter fields.
  • both the attribute request field and the event request field carried in the third subscription request are empty.
  • the second terminal sends an error status report to the first terminal.
  • the error status report is used to indicate that the third subscription request does not indicate the target resource corresponding to the third subscription identification field.
  • the third subscription request carries an attribute request field and an event request field, and any one of them is not empty.
  • the second terminal needs to return a subscription response to the first terminal, as follows:
  • attribute request field and/or event request field is not empty, its value may be the fourth value, or its value may be used to indicate a specific attribute and/or event.
  • the fourth value may be a wildcard character. For relevant descriptions of wildcard characters, please refer to the foregoing content.
  • the value of the attribute request field and/or the event request field carried in the third subscription request is not the fourth value, that is, the attribute request field and/or the event request field corresponds to If there is at least a fifth value in the list, and the fifth value is a value different from the fourth value, step 3062 is executed.
  • the fifth value is used to indicate the subscription relationship requested to be canceled in the subscription corresponding to the third subscription identification field. .
  • step 3062 is as follows:
  • Step 3062 The second terminal sends a fourth subscription response to the first terminal.
  • the fourth subscription response is used to indicate canceling the subscription relationship between the first terminal and the second terminal regarding the fifth value indication.
  • the third subscription request is used to request cancellation of an existing subscription relationship.
  • the second terminal can determine at least one attribute and/or event in the existing subscription relationship corresponding to the third value. Based on this, the second terminal sends a fourth subscription response to the first terminal to cancel the subscription relationship indicated by the fifth value.
  • the canceled subscription relationship is an attribute and/or event in the subscription corresponding to the third value.
  • the remaining attributes and/or events in the subscription relationship corresponding to the third value still need to be responded to.
  • the subscription relationship corresponding to the third value includes multiple attributes and/or events, and there are only some values in the list corresponding to the attribute request field and/or event request field carried in the third subscription request, and this part of the value corresponds to
  • the remaining attributes and/or events in the subscription relationship corresponding to the third value will not be determined.
  • the attributes and/or events that cannot be determined in this part still need to be responded to, or still need to be responded to. reserve.
  • Smart home appliances correspond to 5 attributes and 5 events.
  • the subscription relationship with a subscription identification field of 3 corresponds to 3 properties and 2 events.
  • the subscription relationship with a subscription identification field of 4 Corresponds to 2 attributes and 3 events.
  • the smart home appliance sends a third subscription response to the mobile terminal, and the third subscription response is used to request cancellation. All subscription relationships corresponding to the subscription identification field between the first terminal and the second terminal. If the third value is 3, unsubscribe from the 3 attributes and 2 events corresponding to identification field 3; if the third value is 4, unsubscribe from the 2 attributes and 3 events corresponding to identification field 4.
  • the mobile terminal sends a fourth subscription response.
  • the fourth subscription response is used to indicate canceling the subscription relationship between the first terminal and the second terminal regarding the fifth value indication. For example, if the third value is 3, and there are 2 attributes in the attribute request field (that is, the value of the list of attribute request fields is not a wildcard, and there are 2 specific values in the list), the list of event request fields is defined as Wildcard, then the subscription of 2 properties and 3 events will be cancelled, and the remaining 1 property will still exist.
  • the fifth value may also be a wildcard.
  • the fifth value is used to indicate that the attribute and/or event corresponding to the fifth value is adjusted to a preset configuration.
  • both the fourth value and the fifth value can be wildcard characters.
  • the third subscription request is used to request cancellation of all subscription relationships corresponding to the third subscription identification field.
  • the third subscription request carries the attribute request field and/or the event request field, and the list corresponding to the attribute request field and/or the event request field is defined as a wildcard.
  • the fifth value is a wildcard
  • the third subscription request carries the attribute request field and/or the event request field, and there is at least one wildcard character in the list corresponding to the attribute request field and/or the event request field, and the wildcard character
  • the corresponding properties and/or events will be adjusted to the preset configuration.
  • the steps on the first terminal side and the steps on the second terminal side can be independently implemented as an embodiment of the subscription request method.
  • reference can be made to the foregoing content.
  • the subscription request method provided by the embodiment of this application can be implemented as follows:
  • the first terminal sends a subscription request to the second terminal, and the subscription request at least carries the SubscriptionID field;
  • the second terminal performs one of the following steps:
  • SubscriptionID 0, the MinIntervalFloor field and the MaxIntervalCeil field are mandatory, and when one of the AttributeRequests field and the EventRequests field is not empty, the second terminal returns the subscription message.
  • the SubscriptionID contained in the subscription message cannot be 0 and xFFFFFFFF.
  • the included SubscriptionID is generated based on the subscription request;
  • Figure 11 shows a schematic diagram of a subscription request device provided by an exemplary embodiment of the present application.
  • the device includes:
  • Sending module 1120 used to send a subscription request to the second terminal
  • the subscription request carries a subscription identification field.
  • the subscription request is used to request the establishment of a new subscription relationship; or, the subscription request is used to request the cancellation of a subscribed target resource.
  • the subscription identification field is used to trigger the second terminal to report the status of resource information to the first terminal at least based on the value of the subscription identification field; and/or the subscription identification field is used to trigger the second terminal to report the status of resource information to the first terminal based at least on the value of the subscription identification field.
  • a subscription response is sent to the first terminal. The subscription response is used to indicate the cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure domain filter field .
  • both the attribute request field and the event request field carried in the subscription request are empty.
  • the sending module 1120 is used to send a first subscription request to the second terminal.
  • the first subscription identification field carried in the first subscription request is the first value.
  • the first subscription request is used to request the establishment of a new subscription relationship. .
  • the device also includes: a receiving module 1140, configured to receive a first subscription response sent by the second terminal; wherein the first subscription response is the property request field and/or the event request field carried in the first subscription request. Sent when it is empty, the subscription identification field carried in the first subscription response is not the first value.
  • a receiving module 1140 configured to receive a first subscription response sent by the second terminal; wherein the first subscription response is the property request field and/or the event request field carried in the first subscription request. Sent when it is empty, the subscription identification field carried in the first subscription response is not the first value.
  • the first subscription request also carries a minimum interval field and a maximum interval field.
  • the attribute request field and the event request field carried in the first subscription request are both empty.
  • the device also includes: a receiving module 1140, used to receive an error status report sent by the second terminal, and the error status report is used to indicate the first The subscription request does not indicate the target resource corresponding to the first subscription identification field.
  • the sending module 1120 is configured to send a second subscription request to the second terminal.
  • the second subscription identification field carried in the second subscription request is a second value.
  • the second subscription request is used to request cancellation of the first terminal pair. All subscription relationships of the second terminal.
  • the device further includes: a receiving module 1140, configured to receive a second subscription response sent by the second terminal; wherein the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal.
  • a receiving module 1140 configured to receive a second subscription response sent by the second terminal; wherein the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal.
  • the sending module 1120 is used to send a third subscription request to the second terminal.
  • the third subscription identification field carried in the third subscription request is a third value.
  • the third subscription request is used to request cancellation of an existing subscription. relation.
  • the device further includes: a receiving module 1140, configured to receive a third subscription response sent by the second terminal; wherein the third subscription response is used to indicate the cancellation of the first terminal's subscription to the second terminal corresponding to the third subscription identification field. All subscription relationships.
  • the attribute request field and/or event request field carried in the third subscription request is a fourth value; or, the third subscription request does not carry the attribute request field and/or event request field.
  • the device also includes: a receiving module 1140, configured to receive a fourth subscription response sent by the second terminal; wherein the fourth subscription response is used to indicate the cancellation of the first terminal's request to the second terminal regarding the fifth value Indicates the subscription relationship.
  • the attribute request field and the event request field carried in the third subscription request are both empty.
  • the device also includes: a receiving module 1140, used to receive an error status report sent by the second terminal, and the error status report is used to indicate the third The subscription request does not indicate the target resource corresponding to the third subscription identification field.
  • Figure 12 shows a schematic diagram of a subscription request device provided by an exemplary embodiment of the present application.
  • the device includes:
  • the receiving module 1220 is used to receive the subscription request sent by the first terminal
  • the subscription request carries a subscription identification field.
  • the subscription request is used to request the establishment of a new subscription relationship; or, the subscription request is used to request the cancellation of a subscribed target resource.
  • the subscription identification field is used by the second terminal to report the status of the resource information to the first terminal based on at least the value of the subscription identification field; and/or the subscription identification field is used by the second terminal based on at least the value of the subscription identification field.
  • the value sends a subscription response to the first terminal, and the subscription response is used to indicate the cancellation of all or part of the subscription relationship between the first terminal and the second terminal.
  • the subscription request also carries at least one of the following fields: minimum interval time field; maximum interval time field; attribute request field; data version filter field; event request field; event filter field; network structure domain filter field .
  • the receiving module 1220 is used to receive the first subscription request sent by the first terminal.
  • the first subscription identification field carried in the first subscription request is the first value.
  • the first subscription request is used to request the establishment of a new subscription. relation.
  • the device also includes: a sending module 1240, configured to send a first subscription response to the first terminal when the attribute request field and/or the event request field carried in the first subscription request are not empty; wherein, The subscription identification field carried in the first subscription response is not the first value.
  • a sending module 1240 configured to send a first subscription response to the first terminal when the attribute request field and/or the event request field carried in the first subscription request are not empty; wherein, The subscription identification field carried in the first subscription response is not the first value.
  • the first subscription request also carries a minimum interval field and a maximum interval field.
  • both the attribute request field and the event request field carried in the first subscription request are empty; the device also includes: a sending module 1240, used to send an error status report to the first terminal, and the error status report is used to indicate the first subscription.
  • the request does not indicate the target resource corresponding to the first subscription identification field.
  • the receiving module 1220 is configured to receive a second subscription request sent by the first terminal.
  • the second subscription identification field carried in the second subscription request is a second value.
  • the second subscription request is used to request cancellation of the first terminal. All subscription relationships to the second terminal.
  • the device further includes: a sending module 1240, configured to send a second subscription response to the first terminal; wherein the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal.
  • a sending module 1240 configured to send a second subscription response to the first terminal; wherein the second subscription response is used to indicate the cancellation of all subscription relationships between the first terminal and the second terminal.
  • the receiving module 1220 is configured to receive a third subscription request sent by the first terminal.
  • the third subscription identification field carried in the third subscription request is a third value.
  • the third subscription request is used to indicate the cancellation of an existing subscription. Subscription relationship.
  • the device further includes: a sending module 1240, configured to send a third subscription response to the first terminal; wherein the third subscription response is used to indicate the cancellation of all subscriptions corresponding to the third subscription identification field.
  • a sending module 1240 configured to send a third subscription response to the first terminal; wherein the third subscription response is used to indicate the cancellation of all subscriptions corresponding to the third subscription identification field.
  • not all attribute request fields and/or event request fields carried in the third subscription request are fourth values, and the fourth value is used to indicate the attributes and/or events requested in the third subscription identification field in the response.
  • the attribute request field and/or event request field carried in the third subscription request is a fourth value; or, the third subscription request does not carry the attribute request field and/or event request field.
  • the device also includes: a sending module 1240, configured to send a fourth subscription response to the first terminal; wherein the fourth subscription response is used to indicate the cancellation of the subscription relationship between the first terminal and the second terminal regarding the fifth value indication.
  • both the attribute request field and the event request field carried in the third subscription request are empty.
  • the receiving module 1220 is also used to receive an error status report sent by the second terminal.
  • the error status report is used to indicate that the third subscription request has not been completed. Indicates the target resource corresponding to the third subscription identification field.
  • Figure 13 is a block diagram of a first terminal or a second terminal of a communication device provided by an exemplary embodiment of the present application.
  • the communication device includes: a processor 1301, a receiver 1302, a transmitter 1303, a memory 1304 and a bus 1305.
  • the processor 1301 includes one or more processing cores.
  • the processor 1301 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1302 and the transmitter 1303 can be implemented as a communication component, and the communication component can be a communication chip.
  • Memory 1304 is connected to processor 1301 through bus 1305.
  • the memory 1304 may be used to store at least one instruction, and the processor 1301 is used to execute the at least one instruction to implement each step of the RAR receiving window determination method mentioned in the above method embodiment.
  • memory 1304 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory (Electrically-Erasable Programmable Read Only Memory, EEPROM), erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), static random access memory (Static Random Access Memory, SRAM), read-only memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read-Only Memory, PROM).
  • magnetic or optical disks electrically erasable programmable Read-only memory (Electrically-Erasable Programmable Read Only Memory, EEPROM), erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), static random access memory (Static Random Access Memory, SRAM), read-only memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory
  • the first terminal includes a memory and a processor; at least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the aforementioned subscription request method.
  • the second terminal includes a memory and a processor; at least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the aforementioned subscription request method.
  • This application also provides a computer-readable storage medium.
  • a computer program is stored in the storage medium.
  • the computer program is used to be executed by a processor to implement the aforementioned subscription request method.
  • the chip includes programmable logic circuits and/or program instructions, and is used to implement the aforementioned subscription request method when the electronic device installed with the chip is running.
  • the computer program product includes computer instructions.
  • the computer instructions are stored in a computer-readable storage medium.
  • the processor reads and executes the computer instructions from the computer-readable storage medium to implement the aforementioned subscription request. method.

Landscapes

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

Abstract

Sont divulgués des procédés et des appareils de demande d'abonnement, un dispositif et un support de stockage. La présente demande concerne le domaine technique des communications. Un procédé est exécuté par un premier terminal, et consiste à : envoyer à un deuxième terminal une demande d'abonnement, la demande d'abonnement comportant un champ d'identification d'abonnement.
PCT/CN2022/117344 2022-09-06 2022-09-06 Procédés et appareils de demande d'abonnement, dispositif et support de stockage WO2024050698A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/117344 WO2024050698A1 (fr) 2022-09-06 2022-09-06 Procédés et appareils de demande d'abonnement, dispositif et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/117344 WO2024050698A1 (fr) 2022-09-06 2022-09-06 Procédés et appareils de demande d'abonnement, dispositif et support de stockage

Publications (1)

Publication Number Publication Date
WO2024050698A1 true WO2024050698A1 (fr) 2024-03-14

Family

ID=90192667

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/117344 WO2024050698A1 (fr) 2022-09-06 2022-09-06 Procédés et appareils de demande d'abonnement, dispositif et support de stockage

Country Status (1)

Country Link
WO (1) WO2024050698A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104065517A (zh) * 2014-07-07 2014-09-24 用友软件股份有限公司 分布式系统软件配置管理方法和系统
US20150127122A1 (en) * 2012-05-21 2015-05-07 Lg Electronics Inc. Power device, power control device, and operating method therefor
CN108353094A (zh) * 2015-11-16 2018-07-31 康维达无线有限责任公司 用于m2m服务层的跨资源订阅
WO2021072672A1 (fr) * 2019-10-16 2021-04-22 Oppo广东移动通信有限公司 Procédé et appareil d'abonnement à une ressource
WO2021087892A1 (fr) * 2019-11-07 2021-05-14 Oppo广东移动通信有限公司 Procédé et dispositif d'abonnement à des ressources et support de stockage

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150127122A1 (en) * 2012-05-21 2015-05-07 Lg Electronics Inc. Power device, power control device, and operating method therefor
CN104065517A (zh) * 2014-07-07 2014-09-24 用友软件股份有限公司 分布式系统软件配置管理方法和系统
CN108353094A (zh) * 2015-11-16 2018-07-31 康维达无线有限责任公司 用于m2m服务层的跨资源订阅
WO2021072672A1 (fr) * 2019-10-16 2021-04-22 Oppo广东移动通信有限公司 Procédé et appareil d'abonnement à une ressource
WO2021087892A1 (fr) * 2019-11-07 2021-05-14 Oppo广东移动通信有限公司 Procédé et dispositif d'abonnement à des ressources et support de stockage

Similar Documents

Publication Publication Date Title
CN107231606B (zh) WiFi入网方法、智能硬件设备及电子终端
US20200106840A1 (en) Service Discovery Method, Registration Center, and Device
US10491686B2 (en) Intelligent negotiation service for internet of things
EP3616426B1 (fr) Configuration de la politique réseau
EP3005822B1 (fr) Transport à couche mac pour plateforme de services d'application de services directs à wi-fi sans protocole internet
CA3072674A1 (fr) Methode de parametrage d'une unite de donnees du protocole, procede d'etablissement de politiques pour le materiel employe par l'utilisateuret entite associee
WO2019205557A1 (fr) Abonnement à des ressources destinées à un dispositif de l'internet des objets
JP6629345B2 (ja) Ｍ２ｍサービスを追加するためのデバイスおよび方法
CN107409270B (zh) 用于建立设备之间的连接的方法和装置
WO2018001089A1 (fr) Procédé et appareil de traitement de données et support d'informations
US11700301B2 (en) Service registration based on service capabilities requirements and preferences
EP2564657A2 (fr) Préférences de protocole de communication
CN108322557B (zh) 一种应用设备发现方法、装置、计算机设备及存储介质
WO2024050698A1 (fr) Procédés et appareils de demande d'abonnement, dispositif et support de stockage
WO2024092379A1 (fr) Procédé et appareil de transmission de données, dispositif, et support de stockage
CN113853813A (zh) 在uwb通信和测距系统中指定接收器使能时间的装置和方法
CN106790323B (zh) 一种资源发现的方法及装置
CN111314477A (zh) P2p通信方法、系统、家庭网关、电子设备和存储介质
WO2022087796A1 (fr) Procédé et appareil d'abonnement à un attribut de dispositif zigbee, et dispositif
WO2023216960A1 (fr) Procédé et appareil de traitement de données, nœud de réseau central, dispositif électronique et support de stockage
WO2018068580A1 (fr) Procédé d'instruction et appareil de verrouillage d'écran, et procédé, appareil et système de verrouillage d'écran
US20190312929A1 (en) Information synchronization method and device
WO2023165359A1 (fr) Procédé de connexion p2p wi-fi, appareil et système
WO2023231725A1 (fr) Procédé et appareil de transmission d'informations, support de stockage et dispositif électronique
WO2023083174A1 (fr) Procédé et dispositif de mise à jour d'abonnement, élément de réseau et support

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

Country of ref document: EP

Kind code of ref document: A1