WO2021146960A1

WO2021146960A1 - Message endpoint discovery method and related apparatus

Info

Publication number: WO2021146960A1
Application number: PCT/CN2020/073636
Authority: WO
Inventors: 茹昭
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-01-21
Filing date: 2020-01-21
Publication date: 2021-07-29
Also published as: CN114651423B; CN114651423A

Abstract

Disclosed are a message endpoint discovery method and a related apparatus. The method comprises: a client sending a multicast request, wherein the multicast request comprises a first uniform resource identifier (URI), and a constrained application protocol (CoAP) resource corresponding to the first URI is a /oic/res resource; and the client receiving first resource information from a first server, wherein an OCF resource reference Link parameter of the first resource information indicates, in the manner of a Links array, a resource carried by the first server, each Link parameter in the Links array corresponds to a resource, a resource attribute of the first resource information comprises a first parameter, the first parameter is used to indicate whether it is necessary to further acquire an endpoint information resource, the endpoint information resource is used to indicate endpoint information of a resource carried by the first server, and the endpoint information resource is the same as an endpoint where the /oic/res resource is located. The embodiments of the present application can realize the determination of endpoint information of any resource.

Description

Message endpoint discovery method and related device

Technical field

This application relates to the field of communication technology, and in particular to a method and related devices for discovering message endpoints.

Background technique

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. For resource-constrained application protocol (The Constrained Application Protocol, CoAP) over user datagram protocol (User Datagram Protocol, UDP), the message endpoint consists of an IPv4/IPv6 address and a UDP port number. Generally, 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, and 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. In other words, 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.

Summary of the invention

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.

In the first aspect, 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;

Wherein, 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.

In the second aspect, 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;

In a third aspect, 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;

In a fourth aspect, 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;

In a fifth aspect, 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.

In a sixth aspect, 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.

In a seventh aspect, 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. Some or all of the steps described in any method of the aspect.

In an eighth aspect, 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.

In a ninth 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.

It can be seen that, in this embodiment of the application, 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.

Description of the drawings

The following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art.

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;

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.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings.

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. Among them, the client 110 can be various electronic devices such as mobile phones, the server 120 can be an OCF device, and 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.

Among them, for each Link in the Collection resource (combined resource), Link can refer to a resource of itself (assuming it is server 1). At this time, 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. At this time, the endpoint information in the Link is an endpoint of server p.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (TDD), universal mobil et communication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, the future fifth generation (5th generation, 5G) system or new radio (NR), etc.

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.

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., is not limited in the embodiment of the present application.

In some deployments, 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. For example, 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. 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. 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. It is understandable that the server 120 may be a device including one or more of the CU node, the DU node, and the AAU node. In addition, 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 .

In the embodiment of the present 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. Moreover, 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. For example, 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.

The following first briefly introduces some basic concepts of the OCF system.

In the OCF protocol, the function of the device is defined in a resource (Resource) way. In the OCF system, 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.

(1) URI: Each resource has its own URI, and some resources have predefined URIs. This resource can be obtained by accessing the corresponding URI.

(2) Property: Each resource contains properties, which are used to describe related information of the resource.

(3) Resource reference (link): Establish a reference relationship between resources through links.

(4) Interface: The expression of the open resource and the corresponding operation method.

Among them, the OCF property (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:

①Property title: The display name of the property.

②Property name: the identifying name of the property, the key in the key-value pair <Key:Value>.

③Value type: The type of the attribute value, which can be a simple data type or a complex data type.

④Value rules: The constraint conditions of the attribute value, such as the maximum value, the minimum value, and the value range of the enumeration value.

⑤Unit: The unit of the attribute value, such as ℃.

⑥Mandatory: Indicate whether the attribute is mandatory in a certain resource type.

⑦Access mode: The access mode of the attribute value, which can be readable (R), writable (W), or readable and writable (R, W).

⑧Description: The readability description information of the attribute.

The attribute definition format is the attribute format shown in Table 1 taking the resource name "n" attribute as an example.

Table 1

Among them, 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"]

The resource type definition includes the following characteristics:

①Pre-defined URI (optional): OCF pre-defines a fixed resource URI for a specific resource, such as /oic/res

②Resource Type title (optional): the display name of the resource type

③Resource Type ID: the identifier of the resource type, that is, the value of the "rt" attribute

④Interfaces: List of interfaces supported by this type of resource

⑤Description: the readable description information of the resource type, for example, "oic.r.humidity" resource is used to describe the environmental humidity

⑥Mandatory: Indicate whether the resource type is mandatory in the OCF system

⑦Properties: Properties related to the resource type

The resource type definition format, as shown in Table 2 is the resource type format taking the switch resource "Binary Switch" as an example.

Table 2

The relevant attributes of the "Binary Switch" resource are shown in Table 3.

table 3

Among them, 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. As shown in Figure 1B, 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.

Among them, 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.

①Anchor: Context URI. When the anchor is implicit, it actually means the hosting resource that contains the Link. 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.

② href: Target URI, that is, the target resource referenced by Link, which can be a relative path or an absolute path, and href is a required attribute of Link.

③rel: The relationship between the referenced resource URI and the context URI. When rel is implicit, it means "hosts" by default, which is an optional attribute of Link. rt: The resource type identifier of the target resource, which is a required attribute of Link.

④if: The set of interfaces supported by the target resource is a mandatory attribute of Link.

⑤ p: bitmap indicates whether the target resource is discoverable and observable, which is an optional attribute of Link.

⑥eps: Endpoints (IP address + port number) of the message endpoints that can access the target resource are optional attributes of Link.

Among them, 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". "ep" represents the endpoint position of the transmission protocol, this key value is required, for example, "ep":"coap://IP:port". When there are multiple endpoints, "pri" indicates their corresponding priority. This key value is optional. The lower the value, the higher the priority.

Among them, 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.

Among them, the resource message endpoint discovery process is as follows:

1. 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

2. When the client needs to discover resources, join the "All OCF Nodes" multicast group

3. The client sends a multicast request (CoAP GET) to all servers, and the request URI corresponds to "/oic/res"

4. If you need to discover the specified resource type, you can specify "rt", and only devices that match the resource type will respond to the request. When the "rt" query parameter is omitted, all devices will respond to the discovery request

5. 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:

href (link resource URI, can be a relative path or an absolute path).

ref (relationship between link resource URI and context URI).

eps (the endpoint information bound to the link resource).

if (interface supported by link resource).

obs (whether the link resource can be observed Observability).

At present, as defined by the protocol, 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. For a simple device, generally all resources use the same IP, CoAP resources use one port (probably not the default port), and CoAPS resources use another port (probably not the default port), so implicit discovery Only the ports of CoAP resources can be discovered, but the discovery of ports of CoAPS resources is not supported, or the implicit discovery of CoAPS resources can only use fixed default ports (OCF does not currently specify this).

When the device supports explicit discovery, 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".

For example, if there is a grouping situation (that is, part of the Link uses one endpoint information, and another part or more uses another or multiple endpoint information), all links can only contain the "eps" parameter. Essentially, 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.

In response to the foregoing problems, 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.

Please refer to FIG. 2A. 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 .

Wherein, the /oic/res resource is a resource that can be accessed using the CoAP protocol, and 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.

In specific implementation, if 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. When 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.

In the specific implementation, 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.

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.

Wherein, 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.

Wherein, the first parameter may be named "ex" parameter, for example.

In a possible example, 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) .

In specific implementation, 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.

Table 4

In a possible example, the resource attribute of the endpoint information resource further includes at least one of the following:

The resource type rt of the endpoint information resource, the interface list if of the endpoint information resource, all the endpoint information lists eps, one endpoint information ep, and the URI lists hrefs of all resources on the endpoint.

In specific implementation, the format of the resource attribute of the endpoint information resource is shown in Table 5.

table 5

In a possible example, 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.

Wherein, the second parameter is an "eps" parameter (the eps key value shown in FIG. 1C).

For example, in the example of the first resource information shown in FIG. 2B, 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".

It can be seen that in this example, since 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.

In a possible example, 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.

It can be seen that, in this example, for all resources carried by the first server use the default port (CoAP resources use UDP port 5683, CoAPS resources use UDP port 5684), 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.

In this possible example, 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.

Wherein, the second parameter is an "eps" parameter, and the parameters other than the second parameter may be, for example, an "rt" parameter, an "if" parameter, and so on.

It can be seen that in this example, 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.

In this possible example, 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.

Among them, 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).

It can be seen that in this example, 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".

In a possible example, 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.

Wherein, 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.

Wherein, that the resources carried by the first server all use the same port except the default port specifically refers to:

(1) 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

(2) 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.

(3) 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.

It can be seen that in this example, for the case where all resources carried by the first server use the same port except the default port, 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.

In this possible example, 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, and the second parameter uses all Describe the endpoint information of the same port.

Wherein, as shown in FIG. 2B, 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.

It can be seen that in this example, 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 .

In a possible example, 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.

Wherein, the parameter value of the first parameter "ex" may be true.

It can be seen that in this example, for the case where the resources carried by the first server do not use the same port, that is, multiple different endpoints are used, 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.

Wherein, the parameters other than the second parameter "eps" parameter may be "rt" parameters, "if" parameters, and so on.

In this possible example, 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;

After the client receives the first resource information from the first server, 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, and 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.

Correspondingly, after the first server sends the first resource information to the client, 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.

For example, an example of the endpoint information resource is shown in Figure 2C, the resource attribute part includes the following parameters: "rt", "if", "eps", and each Link parameter includes the following parameters: "ep", "hrefs" ".

In addition, this application also proposes the following solutions:

The resource attribute of the first resource information may also include an optional first parameter "ex". When the first parameter ("ex" parameter) and the second parameter ("eps" parameter) are not included, the The resources carried by the first server all use the default port.

Further, 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.

Consistent with the embodiment shown in FIG. 2A, please refer to FIG. 3. FIG. 3 is a schematic structural diagram of a client 300 provided in an embodiment of the present application. As shown in the figure, 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.

Send a multicast request, where 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.

In a possible example, 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.

In a possible example, 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.

In a possible example, 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, and the second parameter uses the Describe the endpoint information of the same port.

In a possible example, 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.

In a possible example, 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.

Please refer to FIG. 4, which is a schematic structural diagram of a server 400 provided by an embodiment of the present application. As shown in the figure, 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.

Receiving a multicast request from a client, 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 resource type of the endpoint information resource is oic.wk.eps;

The mandatory selection of the endpoint information resource is mandatory CM.

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 foregoing mainly introduces the solution of the embodiment of the present application from the perspective of interaction between various network elements. It can be understood that, in order to implement the above-mentioned functions, the terminal includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, 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. For example, 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.

In the case of using an integrated unit, 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. For example, 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. When the processing unit 502 is a processor, the communication unit 503 is a communication interface, and 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.

In specific implementation, 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. The detailed description will be given below.

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 type of the endpoint information resource is oic.wk.eps;

The mandatory selection of the endpoint information resource is mandatory CM.

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 And receiving second resource information from the first server through the communication unit 503, where the second resource information includes endpoint information of the resource carried by the first server.

In the case of using an integrated unit, 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. For example, 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. When the processing unit 602 is a processor, the communication unit 603 is a communication interface, and 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 type of the endpoint information resource is oic.wk.eps;

The mandatory selection of the endpoint information resource is mandatory CM.

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.

It is understandable that since the method embodiment and the device embodiment are different presentation forms of the same technical concept, the content of the method embodiment part of this application should be synchronized to the device embodiment part, and will not be repeated here.

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. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in an access network device, a target network device, or a core network device. Of course, 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.

Those skilled in the art should be aware that, in one or more of the foregoing examples, 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. When implemented by 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. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. 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. For example, 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.

The specific implementations described above further describe the purpose, technical solutions, and beneficial effects of the embodiments of the present application in further detail. It should be understood that the foregoing descriptions are only specific implementations of the embodiments of the present application, and are not used for To limit the protection scope of the embodiments of the present application, any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the embodiments of the present application shall be included in the protection scope of the embodiments of the present application.

Claims

A method for discovering message endpoints, which is characterized in that it comprises:

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;

Wherein, 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 method according to claim 1, wherein 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 method according to claim 1, wherein the resource attribute of the endpoint information resource further comprises at least one of the following:

The resource type rt of the endpoint information resource, the interface list if of the endpoint information resource, all the endpoint information lists eps, one endpoint information ep, and the URI lists hrefs of all resources on the endpoint.
The method according to claim 1, wherein each Link parameter only includes OCF Link parameters other than a second parameter, and the second parameter is used to indicate where the /oic/res resource itself is located. Endpoint.
The method according to any one of claims 1 to 4, wherein 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 method according to claim 5, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate the location of the /oic/res resource itself The endpoint; 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 method according to any one of claims 1-4, wherein 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 all the resources. The endpoint information resource.
The method according to claim 7, wherein 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, and The second parameter uses the endpoint information of the same port.
The method according to any one of claims 1 to 4, wherein 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 method according to claim 9, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate the location of the /oic/res resource itself Of the endpoint.
The method according to claim 9, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;

After the client receives the first resource information from the first server, the method further includes:

The client sends a unicast request to the first port of the first server, 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;

The client receives second resource information from the first server, where the second resource information includes endpoint information of the resource carried by the first server.
A method for discovering message endpoints, which is characterized in that it comprises:

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;

Wherein, 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 method according to claim 12, wherein 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 method according to claim 12, wherein the resource attribute of the endpoint information resource further comprises at least one of the following:

The resource type rt of the endpoint information resource, the interface list if of the endpoint information resource, all the endpoint information lists eps, one endpoint information ep, and the URI lists hrefs of all resources on the endpoint.
The method according to claim 12, wherein each Link parameter only includes OCFLink parameters other than a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located. .
The method according to any one of claims 12-15, wherein the resources carried by the first server all use default ports; and the first parameter is used to indicate that there is no need to further obtain the endpoint information resource.
The method according to claim 16, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate the location of the /oic/res resource itself. The endpoint; 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 method according to any one of claims 12-15, wherein 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 all the resources. The endpoint information resource.
The method according to claim 18, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located, and The second parameter uses the endpoint information of the same port.
The method according to any one of claims 12-15, wherein 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 method according to claim 20, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate the location of the /oic/res resource itself Of the endpoint.
The method according to claim 20, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;

After the first server sends the first resource information to the client, the method further includes:

The first port of the first server receives a unicast request from the client, 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;

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.
A message endpoint discovery device is characterized in that it is applied to a client, the device includes a processing unit and a communication unit, wherein:

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;

Wherein, 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 device according to claim 23, wherein 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 device according to claim 23, wherein the resource attribute of the endpoint information resource further comprises at least one of the following:

The resource type rt of the endpoint information resource, the interface list if of the endpoint information resource, all the endpoint information lists eps, one endpoint information ep, and the URI lists hrefs of all resources on the endpoint.
The apparatus according to claim 23, wherein each Link parameter includes only OCFLink parameters except for a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located. .
The device according to any one of claims 23-26, wherein the resources carried by the first server all use default ports; and the first parameter is used to indicate that no further acquisition of the endpoint information resource is required.
The device according to claim 27, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate where the /oic/res resource itself is located. The endpoint; 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 device according to any one of claims 23-26, wherein 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 all the resources. The endpoint information resource.
The device according to claim 29, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located, and The second parameter uses the endpoint information of the same port.
The device according to any one of claims 23-26, wherein 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 device according to claim 31, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate where the /oic/res resource itself is located. Of the endpoint.
The device according to claim 31, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;

After the processing unit receives the first resource information from the first server through the communication unit, it is further configured to: send a unicast request to the first port of the first server through the communication unit, the unicast request Including 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 The communication unit receives second resource information from the first server, where the second resource information includes endpoint information of the resource carried by the first server.
A message endpoint discovery device, characterized in that it is applied to a first server, the device includes a processing unit and a communication unit, wherein:

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;

Wherein, 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 device according to claim 34, wherein 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 device according to claim 34, wherein the resource attribute of the endpoint information resource further comprises at least one of the following:

The resource type rt of the endpoint information resource, the interface list if of the endpoint information resource, all the endpoint information lists eps, one endpoint information ep, and the URI lists hrefs of all resources on the endpoint.
The device according to claim 34, wherein each Link parameter only includes OCFLink parameters except for a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located. .
The apparatus according to any one of claims 34-37, wherein the resources carried by the first server all use default ports; the first parameter is used to indicate that no further acquisition of the endpoint information resource is required.
The device according to claim 38, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate where the /oic/res resource itself is located. The endpoint; 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 device according to any one of claims 34-37, wherein 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 all the resources. The endpoint information resource.
The device according to claim 40, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located, and The second parameter uses the endpoint information of the same port.
The device according to any one of claims 34-37, wherein 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 device according to claim 42, wherein the resource attribute of the first resource information only includes parameters other than a second parameter, and the second parameter is used to indicate where the /oic/res resource itself is located. Of the endpoint.
The device according to claim 42, wherein the resource attribute of the first resource information further comprises a second parameter, and the second parameter is used to indicate the endpoint where the /oic/res resource itself is located;

After the processing unit sends the first resource information to the client through the communication unit, it is further configured to: receive a unicast request from the client through the first port of the local end through the communication unit, the unicast request Including 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 The communication unit sends second resource information to the client, where the second resource information includes endpoint information of the resource carried by the first server.
A client is characterized by comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor, The program includes instructions for performing the steps in the method according to any one of claims 1-11.
A first server, which is characterized by comprising a processor, a memory, a communication interface, and one or more programs, and the one or more programs are stored in the memory and configured by the processor Execution, the program includes instructions for executing the steps in the method according to any one of claims 12-22.
A chip, characterized by comprising: a processor, used to call and run a computer program from the memory, so that the device installed with the chip executes the method described in any one of claims 1-11 or 12-22 method.
A computer-readable storage medium, characterized in that it stores a computer program for electronic data exchange, wherein the computer program causes a computer to execute the method according to any one of claims 1-11 or 12-22 .
A computer program that causes a computer to execute the method according to any one of claims 1-11 or 12-22.