WO2021146960A1 - Procédé de découverte de point d'extrémité de message et appareil associé - Google Patents

Procédé de découverte de point d'extrémité de message et appareil associé Download PDF

Info

Publication number
WO2021146960A1
WO2021146960A1 PCT/CN2020/073636 CN2020073636W WO2021146960A1 WO 2021146960 A1 WO2021146960 A1 WO 2021146960A1 CN 2020073636 W CN2020073636 W CN 2020073636W WO 2021146960 A1 WO2021146960 A1 WO 2021146960A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
parameter
endpoint
information
endpoint information
Prior art date
Application number
PCT/CN2020/073636
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 CN202080077882.5A priority Critical patent/CN114651423B/zh
Priority to PCT/CN2020/073636 priority patent/WO2021146960A1/fr
Publication of WO2021146960A1 publication Critical patent/WO2021146960A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This application relates to the field of communication technology, and in particular to a method and related devices for discovering message endpoints.
  • the Open Connectivity Foundation (OCF) message endpoint is used to exchange request and response messages.
  • the specific definition of the message endpoint depends on the transmission protocol used.
  • the device's CoAP resources (resources accessible using the CoAP protocol, such as /oic/res resources, /oic/p resources) can use the default UDP port 5683
  • the device's CoAPS resources (accessible using the CoAP+DTLS protocol) Resources, such as /oic/acl resources, /oic/cred resources) can use the default UDP port 5684.
  • the discovery of the message endpoint is used by the client to obtain the endpoint information of the OCF device or resource, which is divided into implicit discovery and explicit discovery.
  • Implicit discovery means that if a device is the source of a CoAP message (for example: "/oic/res" response), then the source IP address and port number can be combined to form the message endpoint information of the device.
  • the "/oic/res" response message of CoAP can implicitly convey the endpoint information of the responding device, and convert all its carried resources into resources that can be accessed by the CoAP transmission protocol.
  • Explicit discovery means that the message endpoint information is explicitly represented by the "eps" parameter of the Links attribute in the "/oic/res" resource, and the client can access the target resource of the Link (Link is also called resource reference) through the message endpoint.
  • the embodiment of the present application provides a message endpoint discovery method and related device, in order to realize the problem of determining the endpoint information of any resource.
  • an embodiment of the present application provides a message endpoint discovery method, including:
  • the client sends a multicast request, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource;
  • the client receives the first resource information from the first server, and the OCF resource of the first resource information refers to the Link parameter indicating the resource carried by the first server in the form of Links array.
  • Each Link in the Links array The parameter corresponds to a resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • an embodiment of the present application provides a message endpoint discovery method, including:
  • the first server receives a multicast request from the client, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource;
  • the first server sends first resource information to the client, and the OCF resource of the first resource information refers to the Link parameter to indicate the resource carried by the first server in the form of an array of Links, and each link in the array of Links Each Link parameter corresponds to one resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • an embodiment of the present application provides a message endpoint discovery device, which is applied to a client, and the device includes a processing unit and a communication unit, where:
  • the processing unit is configured to send a multicast request through the communication unit, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is /oic/res Resources; and receiving first resource information from the first server through the communication unit, the OCF resource of the first resource information references the Link parameter to indicate the resources carried by the first server in the form of an array of Links, the array of Links Each Link parameter corresponds to a resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • an embodiment of the present application provides a message endpoint discovery device, which is applied to a first server, and the device includes a processing unit and a communication unit, where:
  • the processing unit is configured to receive a multicast request from a client through the communication unit, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is/ oic/res resources; and sending first resource information to the client through the communication unit, the OCF resource of the first resource information references the Link parameter to indicate the resources carried by the first server in the form of an array of Links, so Each Link parameter in the Links array corresponds to a resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • embodiments of the present application provide a client, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured by The processor executes, and the program includes instructions for executing the steps in any method in the first aspect of the embodiments of the present application.
  • embodiments of the present application provide a first server, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and are The configuration is executed by the processor, and the program includes instructions for executing steps in any method in the second aspect of the embodiments of the present application.
  • an embodiment of the present application provides a chip, including a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the first aspect or the second aspect of the embodiment of the present application.
  • an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute the For example, part or all of the steps described in any method of the first aspect or the second aspect.
  • an embodiment of the present application provides a computer program, wherein the computer program is operable to cause a computer to execute part or all of the steps described in any method of the first aspect or the second aspect of the embodiment of the present application .
  • the computer program may be a software installation package.
  • the client sends a multicast request
  • the first server receives the multicast request, and sends the first resource information to the client, where the multicast request includes the first URI, and the first URI
  • the corresponding CoAP resource is the /oic/res resource.
  • the OCF Link parameter of the first resource information indicates the resource carried by the first server in the form of Links array. Each Link parameter in the Links array corresponds to a resource.
  • the resource includes CoAP resources and/or CoAPS resources.
  • the resource attribute of the first resource information includes a first parameter.
  • the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource.
  • the endpoint information resource is used to indicate the value of the resource carried by the first server.
  • the endpoint information, the endpoint information resource is the same as the endpoint where the /oic/res resource is located, so the first parameter can clearly indicate the endpoint information of the CoAPS resource, solve the uncertainty problem of the endpoint information of the CoAPS resource, and realize the endpoint for any resource The problem of determining information.
  • FIG. 1A is a system architecture diagram of an OCF example communication system provided by an embodiment of the present application.
  • FIG. 1B is a schematic diagram of a relay in V2X provided by an embodiment of the present application.
  • FIG. 1C is a schematic diagram of a second device accessing a network device through a client according to an embodiment of the present application
  • 2A is a schematic flowchart of a method for discovering message endpoints according to an embodiment of the present application
  • 2B is an example diagram of a parameter of first resource information provided by an embodiment of the present application.
  • 2C is an example diagram of parameters of an endpoint information resource provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a client provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • FIG. 5 is a block diagram of functional units of a message endpoint discovery device provided by an embodiment of the present application.
  • Fig. 6 is a block diagram of functional units of a message endpoint discovery device provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to the exemplary communication system 100 shown in FIG. 1A.
  • the exemplary communication system 100 includes a client 110 and a server 120 (the example in the figure is server 1, server p), and the client 110 is connected to the server 120 in communication.
  • the client 110 can be various electronic devices such as mobile phones
  • the server 120 can be an OCF device
  • the server 120 is provided with OCF message endpoints and OCF resources.
  • Each OCF resource can be accessed through at least one OCF message endpoint. Multiple OCF resources can be associated with the message endpoint.
  • Link can refer to a resource of itself (assuming it is server 1).
  • the endpoint information of the Link is a certain endpoint of server 1, or it can be referenced A certain resource on another server p.
  • the endpoint information in the Link is an endpoint of server p.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE Time division duplex
  • UMTS universal mobil et communication system
  • WiMAX worldwide interoperability for microwave access
  • the client 110 in the embodiment of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent Or user device.
  • the terminal can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, relay devices, in-vehicle devices, wearable devices, terminals in the future 5G network, or public land mobile network (PLMN) that will evolve in the future This is not limited in this embodiment of the application.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile network
  • the server 120 in the embodiment of the present application may be a device for communicating with the client 110, and the network device may be a global system for mobile communications (GSM) system or code division multiple access
  • the base station (transceiver station, BTS) in CDMA) can also be the base station (NodeB, NB) in the wideband code division multiple access (WCDMA) system, or the evolved base station in the LTE system (evoled NodeB, eNB or eNodeB), can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or the server 120 can be a relay device, an access point, a vehicle device, Wearable devices and network devices in the future 5G network or network devices in the future evolved PLMN network, one or a group of (including multiple antenna panels) antenna panels of the base station in the 5G system, or can also form a gNB or
  • the network node of the transmission point such as a baseband unit (BBU), or a distributed unit (DU), etc
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU+AAU.
  • the server 120 may be a device including one or more of the CU node, the DU node, and the AAU node.
  • the CU can be divided into the server 120 in the access network (radio access network, RAN), or the CU can be divided into the server 120 in the core network (core network, CN), which is not limited in this application .
  • the client 110 or the server 120 includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided in accordance with the embodiments of the application.
  • the execution subject of the method provided in the embodiment of the present application may be the client 110, or a functional module in the client 110 that can call and execute the program.
  • resources are logical functional entities that represent information about each device, each functional service of the device, and the status of the device. These logical functional entities are exposed by the server to the client for access and operation, and the client uses the resource Operate the CRUDN and interact with the server.
  • the parameters of OCF resources mainly include URI, attributes, resource references and interfaces.
  • Each resource has its own URI, and some resources have predefined URIs. This resource can be obtained by accessing the corresponding URI.
  • Each resource contains properties, which are used to describe related information of the resource.
  • OCF property appears in the form of ⁇ Key:Value> key-value pairs, expressed in JSON as "property name”: “property value”, and the property definition includes the following characteristics:
  • 3Value type The type of the attribute value, which can be a simple data type or a complex data type.
  • 4Value rules The constraint conditions of the attribute value, such as the maximum value, the minimum value, and the value range of the enumeration value.
  • 6Mandatory Indicate whether the attribute is mandatory in a certain resource type.
  • the access mode of the attribute value which can be readable (R), writable (W), or readable and writable (R, W).
  • the attribute definition format is the attribute format shown in Table 1 taking the resource name "n" attribute as an example.
  • Resource Type is used to describe the specific application type of a type of resource.
  • a resource can have multiple resource type definitions, that is, the "rt” attribute can have multiple attribute values, such as "rt”:["oic. wk.d”,”oic.d.light”]
  • Pre-defined URI (optional): OCF pre-defines a fixed resource URI for a specific resource, such as /oic/res
  • 3Resource Type ID the identifier of the resource type, that is, the value of the "rt" attribute
  • the resource type definition format is the resource type format taking the switch resource "Binary Switch" as an example.
  • a collection resource (also called a combination resource) includes OCF Links, which represents a collection of one or more link resources, and multiple target resources or other collection resources can be referenced through the collection resource.
  • OCF Links represents a collection of one or more link resources, and multiple target resources or other collection resources can be referenced through the collection resource.
  • a Collection resource contains the switch resource of device A (light) and the switch resource of device B (fan), forming a centralized resource group.
  • the client can request multiple resources at the same time by accessing the oic.if.b interface of the Collection resource.
  • the Collection will send the request to each resource in the links, collect the response returned by each resource, and return it to the client in a unified manner.
  • OCF refers to IETF RFC5988 (web linking) to define OCF Link.
  • OCF Link is composed of key-value pairs and is used to represent the connection relationship between resources.
  • Context URI Context URI.
  • the anchor When the anchor is implicit, it actually means the hosting resource that contains the Link.
  • the anchor When the anchor is explicit, it is generally used to cover the hosting resource URI of the Link, providing non-hosting resource URI as the context URI, which is the link's available Select attributes.
  • Target URI that is, the target resource referenced by Link, which can be a relative path or an absolute path
  • href is a required attribute of Link.
  • the set of interfaces supported by the target resource is a mandatory attribute of Link.
  • bitmap indicates whether the target resource is discoverable and observable, which is an optional attribute of Link.
  • Endpoints IP address + port number
  • IP address + port number the message endpoints that can access the target resource are optional attributes of Link.
  • the OCF message endpoint is used to exchange request and response messages, and the specific definition of the message endpoint depends on the transmission protocol used.
  • Each device must be associated with at least one message endpoint. When a message is sent to the message endpoint, it will be delivered to the device associated with the message endpoint. When the message is sent to the endpoint, the target resource is addressed through the resource identifier.
  • a device can be associated with multiple message endpoints. For example, an OCF device supports CoAP and TCP at the same time and has two different endpoints.
  • the message endpoint is represented by the endpoint information "eps", and the "eps" endpoint information includes two keys "ep" and "pri”.
  • the /oic/res resource is a fixed collection resource for device resource discovery specified by the protocol. As shown in Figure 1C, it contains links to all discoverable resources on the device.
  • the resource message endpoint discovery process is as follows:
  • the server uses the multicast address of "all OCF nodes" (OCF does not use the default CoAP multicast address, uses the multicast service address registered with OCF: ff0x::158, port 5683) to perform information multicast
  • the client sends a multicast request (CoAP GET) to all servers, and the request URI corresponds to "/oic/res"
  • the server returns a list of carried resources in the form of an array of Links. Each link corresponds to a resource. Links provides the following information:
  • link resource URI can be a relative path or an absolute path.
  • the device when the device supports implicit discovery, if the device responds to a request for a certain resource (usually a CoAP resource that supports multicast, such as /oic/res resource), then the endpoint information of all its resources Same as the resource.
  • a certain resource usually a CoAP resource that supports multicast, such as /oic/res resource
  • the endpoint information of all its resources Same as the resource.
  • a certain resource usually a CoAP resource that supports multicast, such as /oic/res resource
  • CoAP resources use one port (probably not the default port)
  • CoAPS resources use another port (probably not the default port)
  • the endpoint information of its resource is included in the "eps" parameter of each link under the Links attribute in the "/oic/res" resource, and all links include the "eps” parameter to make the data redundant High, in addition, the "eps” parameter is optional. Link references that do not contain the "eps" parameter implicitly find the source port of the response message with "/oic/res".
  • all links can only contain the "eps" parameter.
  • CoAP resources and CoAPS resources are a grouping situation. If there are CoAP resources and CoAPS resources at the same time, all links must contain the "eps" parameter. If all links include the "eps" parameter, the data redundancy is relatively high.
  • an embodiment of the present application proposes a method for discovering message endpoints, which will be described in detail below with reference to the drawings.
  • FIG. 2A is a schematic flowchart of a message endpoint discovery method provided by an embodiment of the present application. As shown in the figure, the method includes:
  • Step 2a01 the client sends a multicast request (for example: CoAP GET), the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource .
  • a multicast request for example: CoAP GET
  • the multicast request includes a first uniform resource identifier URI
  • the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource .
  • the /oic/res resource is a resource that can be accessed using the CoAP protocol
  • the /oic/res resource is a fixed collection resource for device resource discovery specified by the protocol. It contains Links of all discoverable resources on the device.
  • the client needs to discover the specified resource type, it can specify the "rt" parameter, and only the server that matches the resource type will respond to the request.
  • the "rt" query parameter is omitted, the client is in the OCF multicast group All servers within will respond to the multicast request.
  • Step 2a02 The first server receives a multicast request from the client, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource.
  • the server can use the multicast address of "all OCF nodes" (OCF does not use the default CoAP multicast address, but uses the multicast service address registered with OCF: ff0x::158, port 5683) to perform more information. broadcast. When the client needs to discover resources, it joins the "All OCF Nodes" multicast group.
  • OCF OCF does not use the default CoAP multicast address, but uses the multicast service address registered with OCF: ff0x::158, port 5683
  • Step 2a03 The first server sends first resource information to the client, and the OCF resource of the first resource information refers to the Link parameter in the form of an array of Links indicating the resources carried by the first server, and the Links Each Link parameter in the array corresponds to a resource.
  • the first resource information may specifically be resource information of the /oic/res resource.
  • Step 2a04 the client receives the first resource information from the first server, the OCF resource of the first resource information references the Link parameter in the form of Links array to indicate the resources carried by the first server, and the Links array Each Link parameter corresponds to a resource.
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • the first parameter may be named "ex" parameter, for example.
  • the client sends a multicast request
  • the first server receives the multicast request, and sends the first resource information to the client, where the multicast request includes the first URI, and the first URI
  • the corresponding CoAP resource is the /oic/res resource.
  • the OCF Link parameter of the first resource information indicates the resource carried by the first server in the form of Links array. Each Link parameter in the Links array corresponds to a resource.
  • the resource includes CoAP resources and/or CoAPS resources.
  • the resource attribute of the first resource information includes a first parameter.
  • the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource.
  • the endpoint information resource is used to indicate the value of the resource carried by the first server.
  • the endpoint information, the endpoint information resource is the same as the endpoint where the /oic/res resource is located, so the first parameter can clearly indicate the endpoint information of the CoAPS resource, solve the uncertainty problem of the endpoint information of the CoAPS resource, and realize the endpoint for any resource The problem of determining information.
  • the pre-defined resource URI (Pre-defined URI) of the endpoint information resource is /oic/eps;
  • the resource type display name (Title) of the endpoint information resource is Endpoint Info
  • the resource type (rt) of the endpoint information resource is oic.wk.eps;
  • the interface list (interfaces) supported by the endpoint information resource is oic.if.baseline;
  • the mandatory selection of the endpoint information resource is mandatory CM, where the mandatory selection includes three options: M (Mandatory, mandatory), CM (Conditional Mandatory, conditionally mandatory), and O (Optional, optional) .
  • the resource type of the endpoint information resource may be named oic.wk.eps, and the attribute format of the oic.wk.eps is shown in Table 4.
  • the resource attribute of the endpoint information resource further includes at least one of the following:
  • the format of the resource attribute of the endpoint information resource is shown in Table 5.
  • each Link parameter includes only OCF Link parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the second parameter is an "eps" parameter (the eps key value shown in FIG. 1C).
  • the resource attribute part includes the following parameters: “rt”, “if”, “ex”, “eps”, and each Link parameter includes the following parameters: “Href”, “anchor”, “rel”, “rt”, “if”, "p”.
  • each Link parameter of the first resource information no longer contains the "eps" parameter, only a single "eps" parameter key value is included in the resource attribute part, so that the first resource information is in /oic/res
  • the "eps" data is reduced, effectively reducing the data redundancy of the first resource information.
  • the resources carried by the first server all use default ports; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the default port configuration is as follows: CoAP resources use UDP port 5683, and CoAPS resources use UDP port 5684.
  • the first parameter "ex" parameter value can be false, then the endpoint information of the CoAP resource and the endpoint information of the CoAPS resource can be expressed as: (“eps":[ ⁇ "ep”:"coap://IP:5683” ⁇ , ⁇ "ep":"coaps://IP:5684” ⁇ ]): That is, the port uses the default ports 5683 and 5684, and the IP is the IP address of the first server's response message.
  • the server returns "/oic/res" in "ex”
  • the parameter value is false, which clearly indicates that there is no need to obtain further endpoint information resources.
  • the terminal can accurately determine the endpoint information of the resources carried by the first server according to the port number of the default port and the IP address of the first server's response message.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the second parameter is an "eps” parameter
  • the parameters other than the second parameter may be, for example, an "rt” parameter, an "if” parameter, and so on.
  • the default port is used for all resources (CoAP resources use UDP port 5683, CoAPS resources use UDP port 5684), the value of the "ex” parameter in "/oic/res" returned by the server is false, Therefore, it is clearly indicated that there is no need to further obtain the endpoint information resource, and the terminal can accurately determine the endpoint information of the resource carried by the first server according to the port number of the default port and the IP address of the first server's response message.
  • the resource attribute of the first resource information further includes the second parameter, and the second parameter uses the endpoint information of the default port.
  • the function of the second parameter eps is: when all CoAP resources use the same port (denoted as port A) and all CoAPS resource resources use the same port (denoted as port B), the client is clearly informed of this
  • the two endpoint information is mainly applicable when A and/or B are not the default ports. Of course, it can also be used when A and/or B are the default ports (only redundant).
  • the default port is used for all resources (CoAP resources use UDP port 5683, CoAPS resources use UDP port 5684), the value of the "ex" parameter in "/oic/res" returned by the server is false, Therefore, it is clearly indicated that there is no need to further obtain the endpoint information resource, and the terminal can determine that the endpoint information of the resource carried by the first server is the endpoint information indicated by the second parameter "eps".
  • the resources carried by the first server all use the same port except the default port; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the value of the first parameter may be false, which is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resources carried by the first server include CoAP resources and CoAPS resources, and the port used by the CoAP resource is A, and the port used by the CoAPS resource is B. At least one of A and B is not the default port. In this case, the port in the endpoint information of the CoAP resource is port A, and the port in the endpoint information of the CoAPS resource is port B
  • the resources carried by the first server only include CoAP resources, and the port used by the CoAP resource is A, then the port in the endpoint information of the CoAP resource is port A.
  • the resources carried by the first server only include CoAPS resources, and the port used by the CoAPS resource is B, then the port in the endpoint information of the CoAPS resource is port B.
  • the "ex" parameter value in "/oic/res" is set to false, which clearly indicates that no further acquisition is required Endpoint information resource.
  • the terminal can determine that the endpoint information of the resource carried by the first server is the endpoint information written in the "eps" parameter.
  • the resource attribute of the first resource information further includes a second parameter
  • the second parameter is used to indicate the endpoint where the /oic/res resource itself is located
  • the second parameter uses all Describe the endpoint information of the same port.
  • the second parameter may be an "eps" parameter, and the "eps" parameter is used to indicate that CoAP resources use UDP port 44444 and that CoAPS resources use UDP port 11111.
  • the second parameter "eps" clearly indicates that the endpoint information of the current resource is the endpoint information of the endpoint where the /oic/res resource itself is located, that is, the endpoint information of the same port, to achieve clear instructions for any type of resource .
  • the resources carried by the first server do not use the same port; the first parameter is used to indicate that the endpoint information resource needs to be further obtained.
  • the parameter value of the first parameter "ex" may be true.
  • the first parameter is used to indicate that the endpoint information resource needs to be further obtained, so that each of the first resource information Link does not need to indicate the endpoint information in the current information, which can reduce the data redundancy in /oic/res.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the parameters other than the second parameter "eps" parameter may be “rt” parameters, "if” parameters, and so on.
  • the resource attribute of the first resource information further includes a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;
  • the method further includes: the client sends a unicast request to the first port of the first server, where the unicast request includes a second URI ,
  • the CoAP resource corresponding to the second URI is the endpoint information resource
  • the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located;
  • the client receives from The second resource information of the first server, where the second resource information includes endpoint information of the resource carried by the first server.
  • the method further includes: the first port of the first server receives a unicast request from the client, and the unicast The request includes a second URI, the CoAP resource corresponding to the second URI is the endpoint information resource, and the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located;
  • the first server sends second resource information to the client, where the second resource information includes endpoint information of the resource carried by the first server.
  • the second parameter "eps" is specifically used to indicate the endpoint where the /oic/res resource itself is located, thereby restricting the port where the /oic/res resource is located, that is, the port where the /oic/eps resource is located.
  • the resource attribute part includes the following parameters: "rt”, “if”, “eps”, and each Link parameter includes the following parameters: “ep”, “hrefs” ".
  • the first parameter is used to indicate that the endpoint information resource needs to be further obtained, so that each of the first resource information Link does not need to indicate the endpoint information in the current information, which can reduce the data redundancy in /oic/res.
  • the resource attribute of the first resource information may also include an optional first parameter "ex”.
  • first parameter "ex" parameter
  • second parameter eps” parameter
  • the endpoint information resource /oic/eps resource may not be added, but the default port 5684 is used for the CoAPS resource in the explicit implicit discovery. If only one Link in /oic/res contains the "eps" parameter, the other Link parameters The endpoint information may not refer to the implicit discovery and is the same as the Link parameter by default, so that the uncertainty of the CoAPS resource port can be resolved.
  • the overall idea is: if the first resource information only contains the endpoint information of one resource, the other resources carried by the first server all use the same endpoint information as the resource containing the endpoint information. If the first resource information does not contain any endpoint information, all resources carried by the first server use the default endpoint information.
  • FIG. 3 is a schematic structural diagram of a client 300 provided in an embodiment of the present application.
  • the client 300 includes a processor 310, The memory 320, the communication interface 330, and one or more programs 321, wherein the one or more programs 321 are stored in the above-mentioned memory 320 and are configured to be executed by the above-mentioned processor 310, and the one or more programs 321 Include instructions for performing the following operations.
  • the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource; and receiving the first resource from the first server Information, the OCF resource reference Link parameter of the first resource information indicates the resource carried by the first server in the form of a Links array, and each Link parameter in the Links array corresponds to a resource; wherein, the first resource information
  • the resource attribute of the includes a first parameter, the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource, the endpoint information resource is used to indicate the endpoint information of the resource carried by the first server, the endpoint information resource Same as the endpoint where the /oic/res resource is located.
  • the client sends a multicast request
  • the first server receives the multicast request, and sends the first resource information to the client, where the multicast request includes the first URI, and the first URI
  • the corresponding CoAP resource is the /oic/res resource.
  • the OCF Link parameter of the first resource information indicates the resource carried by the first server in the form of Links array. Each Link parameter in the Links array corresponds to a resource.
  • the resource includes CoAP resources and/or CoAPS resources.
  • the resource attribute of the first resource information includes a first parameter.
  • the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource.
  • the endpoint information resource is used to indicate the value of the resource carried by the first server.
  • the endpoint information, the endpoint information resource is the same as the endpoint where the /oic/res resource is located, so the first parameter can clearly indicate the endpoint information of the CoAPS resource, solve the uncertainty problem of the endpoint information of the CoAPS resource, and realize the endpoint for any resource The problem of determining information.
  • the predefined resource URI of the endpoint information resource is /oic/eps
  • the resource type display name of the endpoint information resource is Endpoint Info
  • the resource type of the endpoint information resource is oic.wk.eps;
  • the interface list supported by the endpoint information resource is oic.if.baseline;
  • the mandatory selection of the endpoint information resource is mandatory CM.
  • the resource attribute of the endpoint information resource further includes at least one of the following:
  • each Link parameter includes only OCF Link parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resources carried by the first server all use default ports; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located; or,
  • the resource attribute of the first resource information further includes the second parameter, and the second parameter uses the endpoint information of the default port.
  • the resources carried by the first server all use the same port except the default port; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information further includes a second parameter
  • the second parameter is used to indicate the endpoint where the /oic/res resource itself is located
  • the second parameter uses the Describe the endpoint information of the same port.
  • the resources carried by the first server do not use the same port; the first parameter is used to indicate that the endpoint information resource needs to be further obtained.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resource attribute of the first resource information further includes a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;
  • the program 321 also includes instructions for performing the following operations: after receiving the first resource information from the first server, sending a unicast request to the first port of the first server, the unicast request including the first port Two URI, the CoAP resource corresponding to the second URI is the endpoint information resource, the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located; The second resource information of the first server, where the second resource information includes endpoint information of the resource carried by the first server.
  • FIG. 4 is a schematic structural diagram of a server 400 provided by an embodiment of the present application.
  • the server 400 includes a processor 410, a memory 420, a communication interface 430, and one or more programs. 421, wherein the one or more programs 421 are stored in the foregoing memory 420 and configured to be executed by the foregoing processor 410, and the one or more programs 421 include instructions for performing the following operations.
  • the multicast request including a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is the /oic/res resource; and sending to the client First resource information, the OCF resource reference Link parameter of the first resource information indicates the resource carried by the first server in the form of a Links array, and each Link parameter in the Links array corresponds to one resource; and wherein, the The resource attribute of the first resource information includes a first parameter, the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource, the endpoint information resource is used to indicate the endpoint information of the resource carried by the first server, and The endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • the client sends a multicast request
  • the first server receives the multicast request, and sends the first resource information to the client, where the multicast request includes the first URI, and the first URI
  • the corresponding CoAP resource is the /oic/res resource.
  • the OCF Link parameter of the first resource information indicates the resource carried by the first server in the form of Links array. Each Link parameter in the Links array corresponds to a resource.
  • the resource includes CoAP resources and/or CoAPS resources.
  • the resource attribute of the first resource information includes a first parameter.
  • the first parameter is used to indicate whether it is necessary to further obtain the endpoint information resource.
  • the endpoint information resource is used to indicate the value of the resource carried by the first server.
  • the endpoint information, the endpoint information resource is the same as the endpoint where the /oic/res resource is located, so the first parameter can clearly indicate the endpoint information of the CoAPS resource, solve the uncertainty problem of the endpoint information of the CoAPS resource, and realize the endpoint for any resource The problem of determining information.
  • the predefined resource URI of the endpoint information resource is /oic/eps
  • the resource type display name of the endpoint information resource is Endpoint Info
  • the resource type of the endpoint information resource is oic.wk.eps;
  • the interface list supported by the endpoint information resource is oic.if.baseline;
  • the mandatory selection of the endpoint information resource is mandatory CM.
  • the resource attribute of the endpoint information resource further includes at least one of the following:
  • each Link parameter includes only OCF Link parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resources carried by the first server all use default ports; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located; or,
  • the resource attribute of the first resource information further includes the second parameter, and the second parameter uses the endpoint information of the default port.
  • the resources carried by the first server all use the same port except the default port; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information further includes a second parameter
  • the second parameter is used to indicate the endpoint where the /oic/res resource itself is located
  • the second parameter uses the Describe the endpoint information of the same port.
  • the resources carried by the first server do not use the same port; the first parameter is used to indicate that the endpoint information resource needs to be further obtained.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resource attribute of the first resource information further includes a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;
  • the program 421 also includes instructions for performing the following operations: after the first resource information is sent to the client, the first port receives a unicast request from the client, and the unicast request includes a second URI, the CoAP resource corresponding to the second URI is the endpoint information resource, the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located; and to the client The terminal sends second resource information, where the second resource information includes endpoint information of the resource carried by the first server.
  • the terminal includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the terminal into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or in the form of software program modules. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 5 shows a block diagram of a possible functional unit composition of the message endpoint discovery apparatus involved in the foregoing embodiment.
  • the message endpoint discovery device 500 is applied to a terminal and specifically includes a processing unit 502 and a communication unit 503.
  • the processing unit 502 is used to control and manage the actions of the terminal.
  • the processing unit 502 is used to support the terminal to perform the process of the technology described herein.
  • the communication unit 503 is used to support communication between the terminal and other devices.
  • the terminal may also include a storage unit 501 for storing program codes and data of the terminal.
  • the processing unit 502 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit). Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of DSP and microprocessor, and so on.
  • the communication unit 503 may be a communication interface, a transceiver, a transceiving circuit, etc., and the storage unit 501 may be a memory.
  • the processing unit 502 is a processor
  • the communication unit 503 is a communication interface
  • the storage unit 501 is a memory
  • the terminal involved in the embodiment of the present application may be the terminal shown in FIG. 3.
  • the processing unit 502 is configured to perform any step performed by the terminal in the foregoing method embodiment, and when performing data transmission such as sending, the communication unit 503 can be optionally invoked to complete the corresponding operation.
  • data transmission such as sending
  • the communication unit 503 can be optionally invoked to complete the corresponding operation.
  • the processing unit 502 is configured to send a multicast request through the communication unit 503, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is /oic /res resource; and receiving the first resource information from the first server through the communication unit 503, the OCF resource of the first resource information refers to the Link parameter and indicates the resource carried by the first server in the form of Links array, so Each Link parameter in the Links array corresponds to a resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • the predefined resource URI of the endpoint information resource is /oic/eps
  • the resource type display name of the endpoint information resource is Endpoint Info
  • the resource type of the endpoint information resource is oic.wk.eps;
  • the interface list supported by the endpoint information resource is oic.if.baseline;
  • the mandatory selection of the endpoint information resource is mandatory CM.
  • the resource attribute of the endpoint information resource further includes at least one of the following:
  • each Link parameter includes only OCF Link parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resources carried by the first server all use default ports; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located; or,
  • the resource attribute of the first resource information further includes the second parameter, and the second parameter uses the endpoint information of the default port.
  • the resources carried by the first server all use the same port except the default port; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information further includes a second parameter
  • the second parameter is used to indicate the endpoint where the /oic/res resource itself is located
  • the second parameter uses the Describe the endpoint information of the same port.
  • the resources carried by the first server do not use the same port; the first parameter is used to indicate that the endpoint information resource needs to be further obtained.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resource attribute of the first resource information further includes a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;
  • the processing unit 502 After the processing unit 502 receives the first resource information from the first server through the communication unit 503, it is further configured to: send a unicast request to the first port of the first server through the communication unit 503,
  • the unicast request includes a second URI, the CoAP resource corresponding to the second URI is the endpoint information resource, and the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located
  • FIG. 6 shows a block diagram of a possible functional unit composition of the message endpoint discovery apparatus involved in the foregoing embodiment.
  • the message endpoint discovery apparatus 600 is applied to a network device, and the network device includes a processing unit 602 and a communication unit 603.
  • the processing unit 602 is used to control and manage the actions of the network device.
  • the processing unit 502 is used to support the process of the network device to perform the technology described herein.
  • the communication unit 603 is used to support communication between the network device and other devices.
  • the network device may also include a storage unit 601 for storing program codes and data of the terminal.
  • the processing unit 602 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit). Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 603 may be a communication interface, a transceiver, a transceiver circuit, etc., and the storage unit 601 may be a memory.
  • the processing unit 602 is a processor
  • the communication unit 603 is a communication interface
  • the storage unit 601 is a memory
  • the terminal involved in the embodiment of the present application may be the network device shown in FIG. 4.
  • the processing unit 602 is configured to receive a multicast request from a client through the communication unit 603, the multicast request includes a first uniform resource identifier URI, and the resource-constrained application protocol CoAP resource corresponding to the first URI is /oic/res resources; and sending first resource information to the client through the communication unit 603, the OCF resource of the first resource information refers to the Link parameter and indicates the resources carried by the first server in the form of an array of Links , Each Link parameter in the Links array corresponds to a resource;
  • the resource attribute of the first resource information includes a first parameter, and the first parameter is used to indicate whether it is necessary to further obtain an endpoint information resource, and the endpoint information resource is used to indicate the status of the resource carried by the first server.
  • Endpoint information the endpoint information resource is the same as the endpoint where the /oic/res resource is located.
  • the predefined resource URI of the endpoint information resource is /oic/eps
  • the resource type display name of the endpoint information resource is Endpoint Info
  • the resource type of the endpoint information resource is oic.wk.eps;
  • the interface list supported by the endpoint information resource is oic.if.baseline;
  • the mandatory selection of the endpoint information resource is mandatory CM.
  • the resource attribute of the endpoint information resource further includes at least one of the following:
  • each Link parameter includes only OCF Link parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resources carried by the first server all use default ports; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located; or,
  • the resource attribute of the first resource information further includes the second parameter, and the second parameter uses the endpoint information of the default port.
  • the resources carried by the first server all use the same port except the default port; the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
  • the resource attribute of the first resource information further includes a second parameter
  • the second parameter is used to indicate the endpoint where the /oic/res resource itself is located
  • the second parameter uses the Describe the endpoint information of the same port.
  • the resources carried by the first server do not use the same port; the first parameter is used to indicate that the endpoint information resource needs to be further obtained.
  • the resource attribute of the first resource information only includes parameters other than the second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located.
  • the resource attribute of the first resource information further includes a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;
  • the processing unit 602 After the processing unit 602 sends the first resource information to the client through the communication unit 603, it is further configured to: receive a unicast request from the client through the first port of the local terminal through the communication unit 603, and The unicast request includes a second URI, the CoAP resource corresponding to the second URI is the endpoint information resource, and the first port is the port indicated by the second parameter, that is, the port where the endpoint information resource is located And sending second resource information to the client through the communication unit 603, the second resource information including the endpoint information of the resource carried by the first server.
  • the embodiment of the present application also provides a chip, wherein the chip includes a processor, which is used to call and run a computer program from the memory, so that the device installed with the chip executes the part described in the terminal in the above method embodiment Or all steps.
  • the embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute the terminal in the above method embodiment Some or all of the steps described.
  • the embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute the network in the above-mentioned method embodiment. Part or all of the steps described by the side device.
  • the embodiments of the present application also provide a computer program product, wherein the computer program product includes a computer program, and the computer program is operable to make a computer execute part or all of the steps described in the terminal in the above method embodiment.
  • the computer program product may be a software installation package.
  • the steps of the method or algorithm described in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read Only Memory, ROM), and erasable programmable read-only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in an access network device, a target network device, or a core network device.
  • the processor and the storage medium may also exist as discrete components in the access network device, the target network device, or the core network device.
  • the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a Solid State Disk (SSD)) )Wait.

Abstract

L'invention concerne un procédé de découverte de point d'extrémité de message et un appareil associé. Le procédé comprend les étapes suivantes : un client envoie une demande de multidiffusion, la demande de multidiffusion comprenant un premier identificateur de ressource uniforme (URI), et une ressource de protocole pour applications contraintes (CoAP) correspondant au premier URI est une ressource /oic/res ; et le client reçoit des premières informations de ressource en provenance d'un premier serveur, un paramètre de liaison de référence de ressource OCF des premières informations de ressource indiquant, à la manière d'un réseau de liaisons, une ressource transportée par le premier serveur. Chaque paramètre de liaison dans le réseau de liaisons correspond à une ressource, un attribut de ressource des premières informations de ressource comprend un premier paramètre, le premier paramètre est utilisé pour indiquer s'il est nécessaire d'acquérir en plus une ressource d'informations de point d'extrémité, la ressource d'informations de point d'extrémité est utilisée pour indiquer des informations de point d'extrémité d'une ressource transportée par le premier serveur, et la ressource d'informations de point d'extrémité est la même qu'un point d'extrémité où se trouve la ressource /oic/res. Les modes de réalisation de la présente invention peuvent réaliser la détermination d'informations de point d'extrémité de n'importe quelle ressource.
PCT/CN2020/073636 2020-01-21 2020-01-21 Procédé de découverte de point d'extrémité de message et appareil associé WO2021146960A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080077882.5A CN114651423B (zh) 2020-01-21 2020-01-21 消息端点发现方法及相关装置
PCT/CN2020/073636 WO2021146960A1 (fr) 2020-01-21 2020-01-21 Procédé de découverte de point d'extrémité de message et appareil associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/073636 WO2021146960A1 (fr) 2020-01-21 2020-01-21 Procédé de découverte de point d'extrémité de message et appareil associé

Publications (1)

Publication Number Publication Date
WO2021146960A1 true WO2021146960A1 (fr) 2021-07-29

Family

ID=76992740

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073636 WO2021146960A1 (fr) 2020-01-21 2020-01-21 Procédé de découverte de point d'extrémité de message et appareil associé

Country Status (2)

Country Link
CN (1) CN114651423B (fr)
WO (1) WO2021146960A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016048208A1 (fr) * 2014-09-25 2016-03-31 Telefonaktiebolaget L M Ericsson (Publ) Mobilité de dispositif avec coap
WO2017044772A1 (fr) * 2015-09-09 2017-03-16 Convida Wireless, Llc Procédés pour l'activation de messagerie coap sensible au contexte
WO2019040609A1 (fr) * 2017-08-22 2019-02-28 Convida Wireless, Llc Arborescences de ressources superposées dans un réseau de communication
WO2019192722A1 (fr) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Description d'objet pour mappage de répertoire de ressources

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20116301A (fi) * 2011-12-21 2013-06-22 Sensinode Oy Menetelmä, laite ja järjestelmä resurssien osoittamiseksi
GB2529838B (en) * 2014-09-03 2021-06-30 Advanced Risc Mach Ltd Bootstrap Mechanism For Endpoint Devices
US10708885B2 (en) * 2015-12-15 2020-07-07 Convida Wireless, Llc Methods and nodes for enabling context-awareness in CoAP
US11240093B2 (en) * 2016-10-07 2022-02-01 Convida Wireless, Llc Service layer resource management for generic interworking and extensibility
CN110035058B (zh) * 2019-02-28 2021-07-06 Oppo广东移动通信有限公司 资源请求方法、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016048208A1 (fr) * 2014-09-25 2016-03-31 Telefonaktiebolaget L M Ericsson (Publ) Mobilité de dispositif avec coap
WO2017044772A1 (fr) * 2015-09-09 2017-03-16 Convida Wireless, Llc Procédés pour l'activation de messagerie coap sensible au contexte
WO2019040609A1 (fr) * 2017-08-22 2019-02-28 Convida Wireless, Llc Arborescences de ressources superposées dans un réseau de communication
WO2019192722A1 (fr) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Description d'objet pour mappage de répertoire de ressources

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
27 June 2014 (2014-06-27), Z. SHELBY K. HARTKE C. BORMANN UNIVERSITAET BREMEN TZI: "The Constrained Application Protocol (CoAP); rfc7252.txt", XP015100722, Database accession no. 7252 *
Z. SHELBY ARM M. KOSTER SMARTTHINGS C. BORMANN UNIVERSITAET BREMEN TZI P. VAN DER STOK CONSULTANT C. AMSUESS, ED.: "CoRE Resource Directory; draft-ietf-core-resource-directory-23.txt", CORE RESOURCE DIRECTORY; DRAFT-IETF-CORE-RESOURCE-DIRECTORY-23.TXT; INTERNET-DRAFT: CORE, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, no. 23, 8 July 2019 (2019-07-08), Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland, pages 1 - 76, XP015134060 *
Z. SHELBY SENSINODE: "Constrained RESTful Environments (CoRE) Link Format; rfc6690.txt", 6690, 7 August 2012 (2012-08-07), XP015084143 *

Also Published As

Publication number Publication date
CN114651423B (zh) 2023-07-28
CN114651423A (zh) 2022-06-21

Similar Documents

Publication Publication Date Title
US20230171618A1 (en) Communication method and apparatus
CN111601353B (zh) 应用程序的路由选择方法及相关装置
WO2023011210A1 (fr) Procédé et appareil permettant d'acquérir un service périphérique
WO2021243837A1 (fr) Procédé de routage de données d'application basé sur une règle ursp, et équipement utilisateur
US11516310B2 (en) Method and apparatus for invoking application programming interface
WO2011137792A1 (fr) Procédé et appareil permettant la coopération entre des dispositifs push
WO2022032865A1 (fr) Procédé de transmission de descripteur de trafic et dispositif associé
US11317450B2 (en) Wireless communication method and network device
WO2020248582A1 (fr) Procédés et appareils pour pont tsn logique
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2023011217A1 (fr) Procédé et appareil de communication
WO2021212939A1 (fr) Procédé, appareil et système de communication
WO2023124457A1 (fr) Procédé et appareil de sélection de réseau
CN114449577A (zh) 服务质量QoS参数配置方法及相关装置
US20220006816A1 (en) Terminal management and control method, apparatus, and system
WO2022022322A1 (fr) Procédé et dispositif pour accéder à un réseau local
WO2018214762A1 (fr) Procédé et appareil d'acquisition d'un paramètre de radiomessagerie
WO2022027345A1 (fr) Procédé et dispositif de communication sans fil
WO2021163901A1 (fr) Procédé de traitement de session et appareil associé
WO2021146960A1 (fr) Procédé de découverte de point d'extrémité de message et appareil associé
WO2021088007A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif réseau
JP2023539805A (ja) 機器の検索と登録方法、ネットワーク側機器
WO2020224582A1 (fr) Procédé et dispositif de mise à jour de tranche de réseau
WO2021179169A1 (fr) Procédé et appareil de gestion de ressources, et support de stockage lisible
WO2024027299A1 (fr) Procédé et dispositif de routage de message

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20915609

Country of ref document: EP

Kind code of ref document: A1