WO2023130216A1

WO2023130216A1 - Communication method, apparatus and system

Info

Publication number: WO2023130216A1
Application number: PCT/CN2022/070131
Authority: WO
Inventors: 万宗顺; 刘哲; 张翔
Original assignee: 华为技术有限公司
Priority date: 2022-01-04
Filing date: 2022-01-04
Publication date: 2023-07-13
Also published as: CN116711448A

Abstract

Embodiments of the present application provide a communication method, which can be applied to the field of service-oriented architecture-based communications. The method comprises: a client entity acquires quality of service (QoS) information related to connection between a client application and a server application; the client entity sends a service request packet, the service request packet carrying QoS management and control information and a service request sequence of the client application for the server application, the QoS management and control information comprising an enabling indication of one or more of the QoS information. According to the communication method provided by the embodiments of the present application, a differentiated QoS management method can be provided for communication between vehicle-mounted applications, thereby providing guarantees of multiple dimensions such as priority and reliability.

Description

Communication method, device and system

technical field

The embodiments of the present application relate to the technical field of communication, and in particular to a communication method, device and system for a service-oriented architecture.

Background technique

With the development of automobile intelligence and networking, smart cars have higher and higher requirements for computing power and communication bandwidth, and the electronic and electrical architecture of the whole vehicle is gradually developing towards Ethernet as the backbone network. FIG. 1 is a schematic diagram of an electrical and electronic architecture of a smart car adopted in the industry. A vehicle communication network 100 includes a communication bus and multiple communication nodes. Wherein, the communication node may include a sensor 120, an actuator 130, a gateway 140, and domain controllers 110a-110c. Various applications are deployed on each node to implement corresponding functions. The communication bus may include one or more of an Ethernet (ethernet, Eth) network, a controller area network (controller area network, CAN) bus, or a local interconnect network (LIN) bus. The backbone network may be an Eth network, and the nodes on the Eth backbone network may include gateways, domain controllers, and sensors and actuators that communicate directly using the Eth network protocol. One or more domain controllers are respectively responsible for the control functions of different domains, such as the cockpit domain, intelligent driving domain controller, and vehicle domain. In the autonomous driving scenario, the sensor used for environment perception can obtain perception data, such as images, millimeter-wave radar signals, laser point clouds, etc., and send the perception data to the intelligent driving domain controller, and the fusion on the intelligent driving domain controller Applications and decision-making applications process the data, make decisions and controls based on the processed data, and send control commands to the actuators used for vehicle control to control the actuators to perform corresponding actions, such as acceleration/deceleration, variable speed, etc. road, turn, brake, or warning, etc.

With more and more functions of smart cars, more and more complex software, and more and more difficult development, the data volume and channels of communication between applications deployed on nodes will increase greatly. The industry is introducing Service Oriented Architecture (SOA) to solve the challenges of large-scale software development for smart vehicles. New technologies such as auto-driving, in-vehicle entertainment, and remote diagnostic upgrades have put forward higher requirements for in-vehicle communication. How to apply the existing Ethernet technology to the automotive field is a big challenge we face.

IP-based scalable service-oriented middleware (Scalable service-Oriented Middleware over IP, SOME/IP) is a communication protocol developed for the automotive industry, which successfully applies Ethernet communication as a middleware to vehicle communication field. Compared with other communication protocols, the current SOME/IP protocol was proposed later and is not yet mature.

Contents of the invention

The embodiment of the present application discloses a communication method, device and system, which can provide quality of service (QoS) guarantee for vehicular Ethernet communication, so as to improve its security in vehicular communication.

In the first aspect, a communication method is provided, which is used for a client entity to respond to a service request from a client application to a server application, and the client entity obtains the quality of service related to the connection between the client application and the server application QoS information, the QoS information includes at least one of the following: service-related domain information, priority information, and reliability information;

The client entity sends a service request message from the client application to the server application, and the service request message includes client connection information, QoS control information, and a service request from the client application to the server application. A request sequence, the QoS control information includes an activation indication of one or more items in the QoS information.

The above method can provide a differentiated QoS management method for communication between vehicle applications, and provide guarantees in multiple dimensions such as priority and reliability. For different types of vehicle applications, it can meet QoS requirements such as high reliability, high security, and low latency, thereby providing smart cars with better service-oriented communication capabilities.

In a possible implementation manner, the client entity sends the service request message of the client application to the server application in a broadcast manner.

In yet another possible implementation manner, the QoS control information includes a domain enabling indication, and the domain enabling indication indicates enabling domain control, and the client entity sends the client entity in a multicast manner within the service-related domain The service request message sent by the application to the server application. Thus, the data provided by the service is isolated from other data.

In yet another possible implementation manner, before sending the service request message from the client application to the server application, the client entity schedules the request message for sending according to the priority information. There are multiple manners for the client entity to schedule the request message for sending according to the priority information.

For example: the client entity determines the scheduling queue corresponding to the priority information from the scheduling queues of the system according to the priority information; the scheduling queue of the system includes at least a first scheduling queue and a second scheduling queue, the The sending priority of the first scheduling queue is higher than that of the second scheduling queue; the client entity schedules the request packet to enter the scheduling queue corresponding to the priority information. If the scheduling queue corresponding to the priority information includes a plurality of packets to be sent, the client entity sorts the plurality of packets to be sent and the request packets according to the priority information so that those with higher priority Packets are sent with priority.

For another example, the node where the client entity is located has a delay-sensitive network TSN interface device, and the client entity provides the QoS information of the service request message to the TSN interface device, so that the TSN interface device Scheduling the service request message into the sending queue corresponding to the QoS information. Therefore, the capability of the TSN interface device can be utilized to enrich the QoS control.

In yet another possible implementation manner, the QoS control information includes a reliability enabling indication, and the reliability enabling indication indicates enabling reliability control, and the service request message further includes timeout duration information.

The QoS information may be configured through a configuration tool, or the QoS information may be obtained through negotiation between the client entity and the server entity.

In the second aspect, a communication method is provided, which is used for a server entity. The server entity receives the service request message sent by the client entity to the server application, and the service request message includes the Connection information, QoS control information, and service request sequence, where the QoS control information includes an activation indication of one or more items in the QoS information;

The server entity parses the service request message to obtain QoS information corresponding to the client connection;

The server entity processes the service request message from the client application to the server application according to the QoS control information and the QoS information.

In a possible implementation manner, the QoS control information includes a domain enabling indication, the domain enabling indication indicates enabling domain control, and the server entity determines the domain information in the service request message according to the service-related domain in the QoS information Is it correct? If the domain information is incorrect, the server entity sends a reply message to the client entity, and the reply message carries an error code corresponding to the domain information error.

In a possible implementation manner, the QoS control information includes a priority enabling indication, and the priority enabling indication indicates enabling priority control, and the server entity processes the client application's request to the server according to the priority information. The service request sequence of the application; the server entity sends a reply message to the client entity, and the reply message carries processing information.

In a possible implementation manner, the QoS control information includes a reliability enabling indication, and the reliability enabling indication indicates enabling reliability control, and the server entity determines whether the processing of the service request sequence satisfies the Reliability requirements. If the processing of the service request sequence does not meet the reliability requirements, the processing information indicates that the error code corresponding to the reliability requirements is not satisfied.

In a possible implementation manner, the server entity parses and receives the service request message to obtain the client connection information and the QoS control information, and the server entity configures QoS information according to the QoS control information. The table obtains the QoS information of the client connection.

In a possible implementation manner, the QoS configuration table is configured through a configuration tool, or the QoS configuration table is obtained through negotiation between the server entity and the client entity.

In a third aspect, a communication method is provided, which is used for a client entity. The client entity sends a service discovery message, the service discovery message includes a service identifier, a client identifier, and QoS negotiation request information, and the QoS negotiation request information Including the client instance identifier (ParticipantID) and at least one of the following QoS information to be confirmed: priority information, reliability information, and domain information published by the service;

The client entity receives the service providing message and QoS negotiation confirmation information of the server entity, the service providing message includes the service instance identifier, and the QoS negotiation confirmation information includes the QoS negotiation information for each item in the QoS negotiation request information. Confirmation of information;

The client entity determines the connection and the QoS information corresponding to the connection according to the service provision message and the QoS negotiation confirmation information.

Through the above-mentioned QoS negotiation process, the client and the server can respectively obtain QoS information corresponding to each CS (client-server) connection agreed upon through negotiation.

In a possible implementation manner, the client entity sends the service discovery message in a broadcast manner;

The client entity receives the service provision message and QoS negotiation confirmation information of the server entity, including:

The client entity receives the service provision message sent by the server entity in broadcast mode;

The client entity receives the QoS response message sent by the server entity to the client entity in a unicast manner, where the QoS response message includes the QoS negotiation confirmation information.

In a possible implementation manner, the client entity sends the service discovery message in a multicast manner in a service-related domain, and the QoS negotiation information further includes the service-related domain information;

The client entity receives the service provision message sent by the server entity in a multicast manner in the service-related domain;

In a fourth aspect, a communication method is provided, including: a server entity receives a service discovery message from a client entity, the service discovery message includes a service identifier, a client identifier, and QoS negotiation request information, and the QoS negotiation request The information includes the client instance identifier (ParticipantID) and at least one of the following QoS information to be confirmed: priority information, reliability information, and domain information issued by the service;

The server entity sends a service provision message and QoS negotiation confirmation information in response to the service discovery message to the client entity, the service provision message includes a service instance identifier, and the QoS negotiation confirmation information includes A confirmation result of each item of QoS information in the QoS negotiation request information.

Through the above-mentioned QoS negotiation process, the client and the server can respectively obtain the QoS information corresponding to each CS (client-server) connection agreed upon through negotiation.

In a possible implementation manner, the server entity generates QoS configuration information according to the QoS negotiation request information.

In the fifth aspect, a communication method is provided, wherein, in response to a service request from a client application to a server application, the client entity determines the session and session state indication information corresponding to the service request, and the session includes multiple A service request from a client application to a server application;

The client entity sends a service request message, the service request message includes service connection information and session information, and the session information includes a session identifier and the session state information.

The above method can ensure the consistency and isolation requirements of the service data requested by the client application, and improve the reliability and security of communication between applications.

In a possible implementation manner, if the client application needs to lock resources for the service of the server application, the session information further includes a resource identifier.

In a possible implementation, if the session corresponding to the service request is not opened, the session state indication information indicates that the session is opened, and the service request message does not carry the service request of the client application to the server application sequence.

In a possible implementation manner, the client entity receives a reply packet sent by the server entity, where the reply packet includes confirmation information that the session is opened successfully.

In a possible implementation, if the session corresponding to the service request has been opened, the session state indication information indicates that the session is in progress, and the service request message also includes the service request of the client application to the server application sequence.

In a possible implementation, the client entity determines that service request sequences of all service requests in the session have been sent to the server entity, and the client entity sends a message indicating that the session submits .

In a possible implementation manner, the client entity receives the message indicating the session submission result sent by the server entity.

In the sixth aspect, a communication method is provided, wherein the server entity receives a service request message from the client application to the server application sent by the client entity, and the service request message includes the service request message sent by the server application to the client The application provides connection information and session information of the service, the session information includes a session identifier and the session state information, and the session includes multiple service requests from the client application to the server application;

The server entity processes the service request packet according to the session information.

In a possible implementation manner, the session state information indicates opening a session, and the server entity determines that the session state confirmation information indicates that the opening is successful; the server entity sends a reply message to the client entity, and the The reply packet includes the session state confirmation information.

In a possible implementation manner, the session state information indicates opening a session, the session information further includes a resource identifier, and the server entity processes the service request message according to the session information, including:

The server entity determines that the session state confirmation information indicates that the opening is successful;

The server entity determines whether the resource corresponding to the resource identifier is occupied by other clients, and if the resource corresponding to the resource identifier is occupied by other clients, the session state confirmation information indicates that opening fails; or, if the The resource corresponding to the resource identifier is idle, the session state confirmation information indicates that the opening is successful, and the service terminal entity locks the resource corresponding to the resource identifier;

The server entity sends a reply message to the client entity, where the reply message includes the session state confirmation information.

In a possible implementation manner, the session state indication information indicates that the session is in progress, and the service request message further includes a service request sequence of the client application to the server application, and the server entity Get the service request sequence.

In a possible implementation manner, the server entity receives a packet indicating session submission from the client entity; the server entity sends a packet indicating a session submission result to the client entity.

The server entity processes multiple service request sequences of the session after receiving the message indicating session submission;

The server entity sends a reply message to the client entity to indicate processing results of the plurality of service request sequences.

Further, the server entity unlocks the resource corresponding to the resource identifier.

In the seventh aspect, there is provided a communication device, including units for performing the steps of the methods in the above-mentioned first aspect and its various implementations, the third aspect and its various implementations, and the fifth aspect and its various implementations or modules. The modules or units may be software and/or hardware.

In a possible design, the communication device provided in the seventh aspect includes a processing unit and a transceiver unit, and the transceiver unit and the processing unit are used to realize the functions of each part in the methods of service discovery and service request by the client entity.

In an eighth aspect, there is provided a communication device, including units for performing the steps of the method in the above-mentioned second aspect and its various implementations, the fourth aspect and its various implementations, and the sixth aspect and its various implementations or modules. The modules or units may be software and/or hardware.

In a possible design, the communication device provided in the eighth aspect includes a processing unit and a transceiver unit, and the transceiver unit and the processing unit are used to realize the functions of each part in the methods of service discovery and service request by the server entity.

In one design, the communication device of the seventh aspect or the eighth aspect is a communication chip, and the communication chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In another design, the communication device of the seventh aspect or the eighth aspect is a communication device, and the communication chip may include a transmitter for sending information, and a receiver for receiving information or data.

According to a ninth aspect, a communication device is provided, including a processor, and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device executes the above-mentioned first aspect to The communication method in any aspect of the sixth aspect and various implementations thereof.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be set separately from the processor.

Optionally, the communication device further includes a transmitter (transmitter) and a receiver (receiver).

In a tenth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or an instruction), when the computer program is executed, the computer executes the above-mentioned first aspect to the first aspect Any one of the six aspects and the communication method in each implementation thereof.

In an eleventh aspect, a computer-readable medium is provided, and the computer-readable medium stores a computer program (also referred to as code, or instruction) which, when run on a computer, causes the computer to execute the above-mentioned first aspect to The data transmission method in any aspect of the sixth aspect and its various implementation manners.

In a twelfth aspect, a communication system is provided, and the system includes: at least one device according to any one of the seventh aspect and the device according to any one of the eighth aspect.

In a thirteenth aspect, a chip system is provided, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device installed with the chip system executes The communication method in any one of the above-mentioned first aspect to the sixth aspect and each implementation manner thereof.

Wherein, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In a fourteenth aspect, a vehicle including the communication system in the twelfth aspect is provided.

Description of drawings

In order to make the drawings concise, each figure schematically shows the relevant parts of the present invention, but does not represent its actual structure as a product, or additionally shows unnecessary features for the application. The figures shown in the drawings The combination of individual features is not intended to limit the application. In order to make the drawings concise and easy to understand, in some drawings, only one of the components having the same structure or function is schematically shown, or only one of them is marked. In addition, in the whole specification, the content indicated by the same reference numeral is also the same. The specific accompanying drawings are explained as follows:

FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

Fig. 2 is a schematic diagram of the SOME/IP protocol stack;

Fig. 3 is a schematic diagram of SOME/IP message format;

FIG. 4 is a schematic diagram of function deployment provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application;

6(a) to 6(c) are schematic diagrams of message formats provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of a message format provided by an embodiment of the present application;

FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of a message format provided by an embodiment of the present application;

FIG. 11 is a schematic block diagram of a communication device provided by an embodiment of the present application;

Fig. 12 is a schematic block diagram of a communication device provided by an embodiment of the present application.

Detailed ways

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above drawings are used to distinguish similar objects, and not necessarily Used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the application described herein, for example, can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion. In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b or c can represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be It can be single or multiple. It should be noted that "at least one item (item)" can also be interpreted as "one item (item) or multiple items (item)".

Herein, the same reference numerals refer to the same content. Descriptions that are known in the art or overlap each other in exemplary embodiments in the embodiment schemes of the present application will be omitted.

It should be understood that the "connection" mentioned in this embodiment of the present application may be a direct or indirect connection, wherein the indirect connection includes a "connection" via a wired or wireless communication network.

Also, when it is stated that a layer is "on" another layer or substrate, the layer can be directly on the other layer or substrate or a third layer can be therebetween.

FIG. 1 is a schematic diagram of a vehicle communication network 100 . The vehicular communication network 100 in this application may be applicable to communication between nodes in various vehicles. It can be understood that, in this application, vehicles may include one or more different types of vehicles operating on land (for example, roads, roads, railways, etc.), water (for example: waterways, rivers, oceans, etc.) or space Or moving means of transport or movable objects. For example, vehicles may include automobiles, bicycles, motorcycles, trains, subways, airplanes, boats, aircraft, robots or other types of vehicles or movable objects, and the like. The following takes the vehicle as an example to briefly introduce the functions that the vehicle can have. Taking the vehicular communication network 100 shown in FIG. 1 as an example, the backbone network may be an Eth network, and the nodes on the Eth backbone network may include a gateway 140, domain controllers 110a-110c, and sensors 120 and actuators 130 that communicate directly using the Eth network protocol. Vehicle-mounted applications on backbone network nodes use the SOME/IP protocol as a service-based communication protocol. For example, after the sensor 120 receives the data, it is sent to the gateway 140 through the CAN bus, and the gateway 140 encapsulates the data packet into a SOME/IP message and sends it to the domain controller 110 for processing through the Eth backbone network; The calculation result is encapsulated into a SOME/IP message and forwarded to the executor 130 via the gateway 140 for execution. It should be noted that the vehicular communication network shown in FIG. 1 is only an example, and the types and numbers of communication nodes may be more or less, which is not a limitation. For example, the communication node may also include one or more electronic control units (electric control unit, ECU), T-box and so on.

SOME/IP is a concept introduced by in-vehicle Ethernet communication. It is located above the layer 4 (Transmission Control Protocol TCP/User Message Protocol UDP) layer of the OSI 7-layer model, as shown in Figure 2, where the application layer and SOME are omitted. The protocol layer between the /IP layer. The application message is encapsulated into a SOME/IP message through the SOME/IP layer entity, including the SOME/IP message header and payload. The SOME/IP message is encapsulated in the payload of the TCP/UDP message and transmitted based on the TCP/IP protocol.

As shown in Figure 3, it is a schematic diagram of the SOME/IP message format. The SOME/IP message includes: a message header (Header) and a message body (Payload), and the Header mainly includes the following fields:

Message ID: used to uniquely identify a message, including a 16-bit service ID (servieid). When the message is of Method type, it consists of service ID and method ID; when the message is of Event type, it consists of service ID and event ID

Length: message length (from the request ID to the end of Payload);

The request ID, which can be used by the service provider and the caller to distinguish different calls of the same message, consists of the client ID and the Session ID, where the client ID is 16 bits.

Protocol version: currently the value must be 1;

Interface version: interface version, generally defined by the service provider;

Message Type: Used to identify the type of message.

The Payload may include a sequence of requests from the client application to the server application, event notification content of the server application, and the like.

SOME/IP provides a middleware that can control the sending and receiving of message communication, which is applicable to various platforms and supports various middleware features, such as serialization, remote procedure call, and service discovery , subscribe, and can be applied to the AUTOSAR system.

Service (service) is the core concept of SOME/IP. Compared with CAN, the service-oriented communication method can greatly reduce the load rate of the bus. In a service, two roles of a server (server) and a client (client) are defined, wherein the side where the application providing the service is located is the server, and the side where the application requesting the service is located is the client. For the same service, there can only be one server, but multiple clients can call the service at the same time. SOME/IP provides an API interface for the application layer, establishes a CS (client-server) connection, and enables it to communicate through the TCP/IP protocol. The SOME/IP access methods are divided into three types, namely event notification, remote procedure call and access process data. Compared with CAN, the service-oriented communication method can greatly reduce the load rate of the bus. Taking the in-vehicle communication network 100 shown in FIG. 1 as an example, for example, the domain controller 110a is used as an intelligent driving domain controller, on which the auxiliary driving application is deployed and needs to obtain speed limit sign information, and the domain controller 110b is used as a cockpit domain controller. The speed limit reminder application deployed on the network needs to obtain the speed limit sign information. The sensor 120 is a front camera, and the speed limit sign detection application deployed on it provides the speed limit sign information. The driving assistance application on the domain controller 110a and the domain controller 110b The speed limit reminder application on the sensor 120 is used as a client, and the speed limit sign detection application on the sensor 120 is used as a server. Service instance 1 and service instance 2 provide services for the two clients, that is, provide speed limit sign information.

Still taking the above as an example, the domain controller 110c is a vehicle domain controller, and the vehicle speed control-related applications deployed on it can request to obtain the vehicle speed control instructions provided by the assisted driving application on the domain controller 110a, then the domain controller 110a at this time The driving assistance application is a server, and the vehicle speed control-related application on the domain controller 130 is a client. It can be seen that in the vehicular network, an application can provide and/or request one or more services, and when the server application provides services for multiple clients, different service instances are used to distinguish them. The request and provision of service can be realized through the interface provided by SOME/IP protocol layer entity.

Since the SOME/IP protocol provides service-oriented communication, for each application, there is a list of services, which describes the services provided by the application and the services that the application needs to access. Since the service needs to be completed by both the server and the client, a series of preparatory work is required to confirm whether there is a network connection between the server and the client before normal data transmission. After that, the client also asks the server whether it can provide the required service, and subscribes to the event of the service. These tasks are realized through SOME/IP service discovery (service discovery). SOME/IP service discovery is used to locate service instances, check if services are available, and deploy publish and subscribe handles.

Due to the high security requirements of the vehicle network, there are many requirements for QoS, such as: for the reliability requirements of data backup and retransmission, priority guarantee can be provided at the application layer, and when the service delay cannot meet the requirements, the error Reporting and domain isolation between communication nodes or services. It can be considered to extend the SOME/IP protocol, for example, to deploy a QoS management module in the SOME/IP protocol layer entity of the in-vehicle communication node to provide QoS guarantee for the service provision and request communication process between the in-vehicle communication nodes. As shown in Figure 4, it is a possible deployment mode provided by the embodiment of the present application, wherein the SOME/IP protocol layer entity is deployed at the operating system layer of the communication node, provides a communication interface for the application, and performs serialization domain message encapsulation , packet scheduling, packet transmission, and service discovery, etc. The QoS management module can be deployed in the SOME/IP protocol layer entity of the node to provide QoS guarantee, for example, priority management, transaction management, timeout management, and regional management. It can be understood that the QoS management module can also be deployed between the SOME/IP protocol layer and the TCP/IP transport layer, which is not limited in this embodiment of the present application.

The communication method provided by the embodiment of the present application will be described below by taking the schematic flowchart shown in FIG. 5 as an example. Wherein, the client application is located on the first communication node and requests services provided by the server application on the second communication node; the server application is located on the second communication node and provides services for the client application. The first communication node and the second communication node may be the same node or different nodes. It is understandable that multiple applications can be deployed on the same node. Some applications can request services provided by applications on other nodes, and some applications can also provide services to applications on other nodes. That is to say, some applications can be clients. end, for other applications it can be the server end. Therefore, the client entity and the server entity can be deployed on the same node at the same time, and the two entities can be deployed together or independently. The client entity and the server entity can be SOME/IP protocol layer entities, respectively provide interfaces for the client application and the server application to send and receive messages, and can include a QoS management module to perform enhanced SOME/IP protocol processing.

As shown in FIG. 5 , it is a method for performing QoS negotiation between a client entity and a server entity in a service discovery phase. The method includes the following steps:

Step 510: the client entity sends a service discovery message. Correspondingly, the server entity receives the service discovery message.

The client application can send a service discovery message through the interface provided by the SOME/IP protocol layer entity to find the required service and service instance.

The client entity may send the service discovery message in broadcast mode, or send the service discovery message in multicast mode in the management domain. Wherein, the management domain may include multiple communication nodes.

Wherein, the service discovery message may include service identification, client identification and QoS negotiation request information. Wherein, the QoS negotiation request information includes the client instance identifier (ParticipantID) and at least one of the following QoS information to be confirmed: priority information, reliability information, and domain information issued by the service.

in,

Priority information (priority info): It is used to indicate the message transmission on the connection and the priority request to the server. The value range and value of the priority information can be defined according to the needs. For example, the system defines the priority as level 5, and the value range of the priority is 1 to 5. Among them, the priority of the defined value is higher, and the priority of the value is smaller. If the level is low, 5 represents the highest priority and 1 represents the lowest priority. Of course, it can also be reversed, where the priority of a small value is low, and the priority of a large value is high, and a group of discontinuous values can also be defined to represent different priorities, which is not limited in this embodiment of the present application. Usually delay-sensitive applications are prioritized over non-delay-sensitive applications

Reliability information (reliability): It is used to indicate whether retransmission is required after message transmission failure or timeout. For example, 0 can be used to indicate that retransmission is not required, 1 can be used to indicate retransmission is required, or vice versa, 0 can be used to indicate retransmission is required, 1 can be used Indicates that no retransmission is required. It can be understood that other values may also be used to indicate whether retransmission is required, and this is not a limitation.

Domain information (domian): It is used to indicate the domain that provides the corresponding service and data, which can be used for data isolation. If the domain information is not limited, it means that the domain that provides the corresponding service and data is not limited, and the corresponding service and data can be broadcast .

In a possible implementation manner, the existing SOME/IP service discovery message may be extended to carry QoS negotiation request information.

The SOME/IP service discovery message can include the SOME/IP Header shown in Figure 3, and the service discovery configuration information part, wherein the service discovery configuration information part can include service identification, service instance identification and option (Option) indication information, wherein the service The instance identifier can indicate whether to find all service instances of the service through a specific value, for example, it can be set to 0XFFFF, and the option indication information is used to indicate that the service discovery message includes one or more options. The QoS negotiation request information can be included in the service discovery message as an option. The QoS negotiation request information can reuse the existing configuration option type (type=0x01), as shown in Figure 6(a), and each QoS negotiation item is encoded according to the (key, value) method, as shown in Figure 6(b ), it means DomainID=0x0001, ParticipantID=0x0012. Carrying the QoS negotiation request information in this way can realize the compatibility between the QoS-enhanced service discovery message and the original service discovery message (endpoints that cannot recognize this configuration item can choose to discard this configuration item).

The QoS negotiation request information can also define a new option type, for example, type=0x99, as shown in FIG. 6(c). It is more concise to carry the QoS negotiation request information in this way, but special processing is required for this field.

Step 520: the server entity sends the response message of step 510. Accordingly, the client entity receives the response message

When the server application can provide the service described by the client, it will send a service provision message through the interface provided by the SOME/IP protocol layer entity.

Wherein, the service providing message may include the provided service identifier and service instance identifier.

If the server entity does not support QoS negotiation or QoS management, the field where the QoS negotiation request information is located may be discarded, and the response message may include a service provision message.

If the server entity supports QoS negotiation or QoS management, it can not only confirm the service discovery, but also confirm the QoS negotiation request information.

In a possible manner, the response message is a service provision message, and the server entity may extend the service provision message to add QoS negotiation confirmation information, wherein the QoS negotiation confirmation information may include the QoS negotiation confirmation information for each A QoS confirmation result, for example, each QoS confirmation result can be represented by a bitmap, for example, the service identifier is 0x4711 as an example, the QoS negotiation request information carries priority information and reliability information, if the server entity provides Service 0x4711, if the priority information of the service 0x4711 is considered to be consistent with the priority information in the QoS negotiation request information, but the reliability information is inconsistent, then the corresponding bit of the priority information in the confirmation result is set to "1", and the reliability information is set in the The corresponding bit in the confirmation result is set to "0". The QoS negotiation confirmation information may also include QoS information of services provided by the server entity: one or more of priority information, reliability information, and domain information.

In this implementation, the service provision message can use the same message format as the service discovery message, the difference is that the message type is different, that is, the message type field indicates the service provision message and the service discovery message respectively.

Wherein, the server entity may send the service offering message in broadcast mode, or send the service offering message (offerservice) in multicast mode in the management domain.

In yet another possible manner, the response packet includes a service provision packet and a QoS response packet. In this manner, the service provision packet is used to confirm the service discovery, and the QoS response packet is used to respond to the QoS negotiation request. information to confirm. The QoS response message includes QoS negotiation confirmation information, wherein the QoS negotiation confirmation information may include a QoS confirmation result for each item in the QoS negotiation request information. The QoS negotiation confirmation information may also include QoS information of services provided by the server entity: one or more of priority information, reliability information, and domain information.

The server entity may send the QoS response message to the client entity in a unicast manner.

After the server entity confirms the QoS, it can record the CS connection providing service for the client application and its corresponding QoS information. For example, it may be recorded through a QoS information configuration table. Table 1 is an exemplary QoS information configuration table, including CS connections and corresponding QoS information. Among them, the value of each field is explained with hexadecimal as an example. It is understandable that hexadecimal system can also be used, such as binary, decimal, etc., and the value type of each field can also be defined as required, such as text, character string etc. It is not intended to be limited. In addition, the values of the fields in Table 1 are just examples, and do not constitute a limitation on the values.

Table 1 QoS information configuration table

Among them, the first three fields of the QoS information mapping table are used to identify the connection information between a client and the server for communication, including client instance identifier (participant id), service identifier (service id) and service instance identifier (service instance id) . Taking Table 1 as an example, the client application requests service 0x4711 through instance (participantid) 0x2, and the service instance 0x1 that provides service 0x4711 for this application; service instances 0x1 and 0x2 that serve 0x4711 provide service 0x4711 for client instance 0x2 and 0x3 respectively .

If the connection has corresponding QoS information, it includes one or more of the following: domain information, priority information, and reliability information.

It should be noted that Table 1 is an example of the recording method of the QoS configuration table. It is also possible to record the connection information separately, and set the connection identifier for each connection separately, and establish the configuration table of the connection identifier and QoS information. for the limit.

Step 530: The client entity determines the QoS information corresponding to the connection providing services for the client application according to the QoS negotiation confirmation information.

After the client entity obtains the QoS negotiation confirmation information from the response message, it can determine the QoS information corresponding to the CS connection that provides services for the client application according to the QoS confirmation result and/or QoS information of each item.

The client entity can maintain a connection and QoS information mapping table for each application deployed on the node that needs to request services. Table 2 is an exemplary QoS information mapping table, including connections and corresponding QoS information.

It can be found that, compared with the server entity, the client entity also needs to record the application identifier corresponding to each client instance. Among them, the value of each field is explained with hexadecimal as an example. It is understandable that hexadecimal system can also be used, such as binary, decimal, etc., and the value type of each field can also be defined as required, such as text, character string etc. It is not intended to be limited. In addition, the values of the fields in Table 2 are just examples, and do not constitute a limitation on the values.

Table 2 QoS information mapping table

Among them, the first 4 fields of the QoS information mapping table are used to identify the connection information for a client to communicate with the server, including the application identifier (task id), client instance identifier (participant id), service identifier (service id) and service Instance ID (service instance id). Taking Table 2 as an example, the application (taskid) 0x1 requests the service 0x4711 through the instance (participantid) 0x2, and the service instance 0x4711 that provides the service 0x4711 for the application 0x1 is 0x1; the service instances 0x1 and 0x2 of the service 0x4711 are respectively the application 0x1 and 0x2 serve 0x4711.

It should be noted that Table 2 is an example of the recording method of the QoS mapping table. It is also possible to record the connection information separately, and set the connection identifier for each connection separately, and establish a mapping table between the connection identifier and the QoS information. for the limit.

Through the above QoS negotiation process, the client and the server can respectively obtain the QoS information corresponding to each CS (client-server) connection. When the client entity processes the application request service message, it can schedule and send it according to its corresponding QoS information, for example, send high-priority service requests first, send them by domain, and so on. When the server entity provides services, it can process service requests according to its corresponding QoS information, for example: prioritize high priority service requests, check whether processing times out, and so on.

The above method can provide different QoS information for different applications, so as to distinguish the application priority, reliability, service release domain, etc., and provide a basis for QoS control. For example, a delay-sensitive application may have a higher priority than a non-delay-sensitive application, and for example, applications in different domains may be isolated.

Certainly, for the scenario where service discovery is enabled, the client and the server may respectively record QoS information corresponding to each CS (client-server) connection after performing QoS negotiation through the above steps 510-530. For scenarios where service discovery is not enabled, it can also be configured or updated locally through the host computer, or remotely configured or updated through the cloud. When the car factory or supplier needs to upgrade the QoS policy, it can configure or update the QoS information in the QoS mapping table in the first management module through the host computer or the cloud. The client and the server can respectively process application packets according to the QoS information.

Fig. 7 is another communication method provided by the embodiment of the present application, which is processed according to the QoS information corresponding to the CS connection recorded by the client entity and the server entity. As shown in Figure 7, the method includes:

Step 710: In response to the client application's service request to the server application, the client entity acquires quality of service (QoS) information related to the connection between the client application and the server application.

Since each application has a list of services that it needs to access, and the connection information between the client and the server is established, each connection can include: application identification (task id), client instance identification (participant id), service identification (service id) and service instance ID (service instance id), etc. When the client application requests the server application to provide corresponding services, the client entity can obtain the QoS information corresponding to this connection. Wherein, the QoS information refers to the description in the foregoing embodiments, and may include one or more of the following:

Step 720: The client entity schedules the service request message initiated by the client application to the server application according to the QoS information obtained in step 710 for sending.

In a possible manner, the client entity may set a scheduling queue of the system, so that the scheduling queue includes at least a first scheduling queue and a second scheduling queue, where the sending priority of the first scheduling queue is higher than that of the second scheduling queue. Of course, the client entity can also set more priority scheduling queues, which is not a limitation.

The client entity determines the scheduling queue corresponding to the priority information from the scheduling queues of the system according to the priority information, and the client entity schedules the request message into the scheduling queue corresponding to the priority information.

If the scheduling queue corresponding to the priority information includes a plurality of packets to be sent, the client entity sorts the plurality of packets to be sent and the request packets according to the priority information so that those with higher priority Packets are sent with priority.

In yet another possible manner, if the node where the client entity is located has a delay-sensitive network TSN interface device, the client entity may provide the QoS information to the TSN interface device, so that the TSN interface device Scheduling the request packet into the sending queue corresponding to the QoS information. For example, the client entity may transmit to the TSN network card including the application's requirements for network bandwidth, the application's requirements for network transmission delay, and the application's requirements for network transmission reliability. The TSN network card will perform packet scheduling, traffic shaping, communication path selection, path reservation, and fault tolerance based on the information. For high-priority packets, the TSN NIC can schedule the packets into the high-priority queue and control the frame preemption policy of the TSN NIC.

Step 730: The client entity sends a service request packet initiated by the client application to the server application, wherein the service request packet includes QoS control information. Correspondingly, the server entity receives the request message.

The client entity can send the service request message by broadcasting.

If the QoS information further includes the domain information related to the service, the client entity may send the service request message in multicast mode in the domain related to the service.

Wherein, the service request message includes: client connection information and QoS control information, wherein, the client connection information includes service identification, client identification, client instance information; QoS control information includes one or more QoS information enabling instructions, each Each QoS information indication is used to indicate whether to enable the corresponding QoS information control, for example, may include a domain activation indication, a priority activation indication, a reliability activation indication, and the like. One possible way is to use a bitmap to indicate, each bit indicates whether to enable a piece of QoS information control, use "1" to indicate that the QoS information is controlled, and use "0" to indicate that the QoS information is not controlled. Taking the QoS control information (QoS control) in FIG. 8 as an example, they are reliability activation indication, priority activation indication, domain activation indication, etc. respectively. It should be noted that this is only an example and not a limitation.

If the domain enabling indication indicates enabling domain control, the service request message may further include domain information; if the reliability enabling indication indicates enabling reliability control, the service request message may further include timeout duration information.

In a possible implementation, the QoS-enhanced service request message can be obtained by extending the existing SOME/IP service request message, so that it can carry newly added QoS control information, domain information, timeout period information, etc.

The QoS enhanced service request message can include the SOME/IP Header and Payload shown in Figure 3, and the extension part can be before the Payload, as shown in Figure 8. It should be noted that FIG. 8 is only an example, and in actual use, the order and length of the fields may be different.

When the server entity receives the service request message, if it does not support the QoS enhanced service request message, it can discard the corresponding fields. If yes, step 740 may be executed for parsing.

Step 740: The server entity acquires QoS information corresponding to the connection according to the service request message sent by the client application to the server application.

The server entity parses the received service request message to obtain connection information and QoS control information, and obtains the QoS information corresponding to the connection in the QoS configuration table according to the QoS control information.

Step 750: The server entity processes the service request message from the client application to the server application according to the QoS control information and the QoS information.

If the domain activation indication indicates that domain control is enabled, the server entity determines whether the domain information in the service request message is correct according to the service-related domain in the QoS information, and if the domain information is wrong, the processing information includes the error corresponding to the domain information error code, go to step 760.

If the priority enable indication indicates that priority control is enabled, the server entity processes the service request sequence of the client application to the server application according to the priority information, and preferentially processes the service request sequence with high priority.

If the reliability enable indication indicates that reliability control is enabled, the server entity also determines whether the processing of the service request meets the reliability requirements, for example, determines whether the timeout period is exceeded, and if so, the processing information includes the processing timeout corresponding error code, go to step 760.

Step 760: The server entity sends a reply packet to the client entity, and the reply packet carries processing information. Correspondingly, the client entity receives the reply message.

As shown in Figure 9, it is another communication method between the client application and the server application, the method includes:

Step 910: In response to the service request from the client application to the server application, the client entity determines a session (transaction) corresponding to the service request and session state indication information.

A session may include service requests from multiple client applications to the server application, and these service requests have consistency requirements, that is, the server application either executes all of the multiple service requests in the session, or does not execute all of them.

The client entity can obtain the session corresponding to the service request, and determine the session status indication information.

If the session corresponding to the service request is not opened, then determine that the session status indication information indicates that the session is started (transactionstart); if the session corresponding to the service request has been opened, then the session status indication information indicates that the session is in progress (intransaction).

Step 920: The client entity sends a service request message, the service request message includes session information, and the session information includes a session identifier and the session state information. Correspondingly, the server entity receives the service request message.

The client entity can send the service request message in broadcast mode, and the client entity can also send the service request message in multicast mode in the service-related domain.

The service request message includes client-side connection information and session information, and the client-side connection information includes: service ID, client ID, and client instance ID, wherein the session information includes session ID and session state indication information.

Further, if the client application requires resource locking for the service provided by the server application, the session information may also include a resource identifier.

In a possible implementation, the existing SOME/IP service request message can be extended to obtain a service request message including session information, so that it can carry a newly added session identifier, session status indication information, and, optionally land, resource ID, etc. The service request message including session information may include the SOME/IP Header and Payload shown in Figure 3, and the extension part may be after the SOME/IP Header and before the Payload.

In yet another possible implementation manner, the embodiment shown in FIG. 7 may also be combined, that is, the extended SOME/IP service request message includes both QoS control information and session information. As shown in FIG. 10 , where the QoS control information part is indicated by a dashed box when carrying session information, the QoS control information is optional. The session state can be used for session state indication in the service request message, for example, for indicating opening of the session, session in progress, session submission, etc., and for session state confirmation in the service response message, for example, for indicating opening Session success, session opening failure, session submission success, session submission failure, etc. It should be noted that FIG. 10 is only an example. In actual use, the order and length of the fields may be different, and the session information may also be placed before the QoS control information.

If the session state indication information indicates that the session is in-transaction, the service request message may also include the service request sequence of the client.

If the session state indication information indicates opening a session, the service request may not include a service request sequence of the client. To ensure that the multiple service request sequences of the client are submitted to the server after the session is opened.

Step 930: The server entity processes the service request packet according to the session information.

After the server entity obtains the connection information and session information, it processes it according to the session state indication information.

1) If the session status indication information indicates opening a session, the server entity confirms whether the session can be opened:

If the server entity confirms that the session can be opened, it is determined that the session state confirmation information indicates that the opening is successful;

If the session information also includes a resource identifier, the server entity determines whether the resource is occupied by another client instance. If it is not occupied, the server entity locks the resource for the client instance of this session, and then confirms the session state The information indicates that the opening is successful; if the resource is occupied by other client instances, the server entity determines the session state confirmation information indicates that the opening fails.

The server entity sends a reply message, and the session state confirmation information is carried in the reply message.

The format of the reply message is the same as that of the received service request message, the difference is that the message type is different, and the session state confirmation information and the session state indication information may be the same field with different values.

2) If the session state indication information indicates that the session is in progress, the server entity obtains the service request sequence therein, and continues to step 930 to receive and process the service request message from the client entity until the session state indication information is received as a service submitted by the session request message.

Step 940: the client entity receives a reply packet from the server entity, and the reply packet includes session state confirmation information.

The client entity determines whether the session is opened successfully according to the session state confirmation information, and if the session is opened successfully, execute steps 910-920 to send a service request message carrying a service request sequence to the server entity.

Step 950: The client entity determines that the multiple service request sequences included in the session have been sent, and the client entity sends a packet indicating session submission. Correspondingly, the server entity receives a packet indicating session submission.

The message indicating session submission may still use the service request message described in step 920, wherein the session state indication information indicates session submission, and may not include the service request sequence of the client.

In yet another possible implementation, the client entity may also indicate session submission at the same time when the last service request sequence of the session is sent, that is, set the session state indication information as the session submission indication.

Step 960: The server entity sends a packet indicating the session submission result to the client entity, and the client entity receives the packet accordingly.

Wherein, the format of the message indicating that the session submission is successful may be the same as that of the service request message in step 920, except that the message type and the corresponding session state indication information are different.

Step 970: The server entity processes multiple service request sequences of the session, and sends a reply message after processing the multiple service request sequences.

After the server entity confirms that the session is submitted, it processes the received multiple service request sequences of the session, and after processing each service request sequence, sends a reply message to indicate the processing result respectively.

If the server entity locks the resource for the client instance, it unlocks the resource after executing multiple service request sequences of the session.

The method in the embodiment of the present application can ensure the consistency and isolation requirements of the service data requested by the client application, and improve the reliability and security of communication between applications.

It can be understood that the embodiments in FIG. 7 and FIG. 9 can be implemented separately or in combination, that is, the service request can include QoS-related information or session-related information, or both QoS-related information and session-related information. , when including QoS-related information and session-related information at the same time, the client entity and the server entity can refer to the processing logic for related fields in the embodiment of FIG. 7 and the embodiment of FIG. 9 .

It should be understood that the various embodiments described in this application may be independent solutions, or may be combined according to internal logic, and these solutions all fall within the protection scope of the embodiments of this application.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of methods. It can be understood that, in order to realize the above-mentioned functions, the above-mentioned client entity and server entity include corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art should easily realize that, in combination with the functions 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 drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

From the perspective of functional units, this application can divide the functional units of the client entity or server entity according to the above method embodiments, for example, each functional unit can be divided corresponding to each function, or two or more functions can be divided into integrated in one functional unit. The above-mentioned integrated functional units can be implemented in the form of hardware or in the form of software functional units.

Hereinafter, the communication device provided by the embodiment of the present application will be described with reference to FIG. 11 . It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, and correspondingly the technical effect corresponds to that of the method embodiment. Therefore, for content that is not described in detail, reference may be made to the above method embodiments, and for the sake of brevity, details are not repeated here.

Fig. 11 is a schematic block diagram of a data transmission device provided by an embodiment of the present application. The device 1100 includes a transceiver unit 1110 and a processing unit 1120 . The transceiver unit 1110 can implement a corresponding communication function, and the processing unit 1120 is used for data processing. The transceiver unit 1110 may also be called a communication interface or a communication unit.

Optionally, the device 1100 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 1120 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .

The apparatus 1100 can be used to execute the actions performed by the client entity or the server entity in the above method embodiments, specifically, the transceiver unit 1110 is used to perform the sending and receiving related actions of the client entity or the server entity in the above method embodiments The processing unit 1120 is configured to perform operations related to the processing of the client entity or the server entity in the above method embodiments.

The apparatus 1100 can implement the steps or processes corresponding to the execution of the client entity or the server entity in the method embodiment according to the embodiment of the present application. A unit of method executed by an end entity or server entity. Moreover, each unit in the apparatus 1000 and other operations and/or functions mentioned above are respectively for realizing the corresponding flow of the method embodiment in the client entity or the server entity in FIG. 5 , FIG. 7 and FIG. 9 .

Wherein, when the apparatus 1100 is used to execute the method performed by the client entity in FIG. 5 , the transceiver unit 1110 can be used to execute step 510, the client entity sends a service discovery message and step 520 receives a response message; the processing unit 1120 can be used to execute Step 530.

When the device 1100 is used to execute the method performed by the server entity in FIG. 5, the transceiver unit 1110 can be used to perform step 510 to receive the service discovery message sent by the client entity and step 520 to send a response message; the processing unit 1120 can be used to perform Step 530.

When the apparatus 1100 is used to execute the method performed by the client entity in FIG. 7 , the transceiver unit 1110 can be used to perform step 730 to send the service request message initiated by the client application to the server application and step 760 to receive the service request message from the server entity. Reply message; the processing unit 1120 can be used to execute steps 710 to 720 .

When the device 1100 is used to execute the method performed by the server entity in FIG. 7 , the transceiver unit 1110 can be used to perform step 730 to receive the service request message initiated by the client application to the server application and step 760 to send a reply message; The processing unit 1120 can be used to perform steps 740 to 750 .

When the device 1100 is used to execute the method performed by the client entity in FIG. 9 , the transceiver unit 1110 can be used to perform step 920 to send the service request message initiated by the client application to the server application, and step 940 to receive the service request message from the server entity. Reply message, step 950 sends a message indicating session submission, step 960 receives a message indicating a session submission result, and step 970 receives a reply message; the processing unit 1120 can be used to execute step 910 .

When the device 1100 is used to execute the method performed by the server entity in FIG. 9 , the transceiver unit 1110 can be used to perform step 920 to receive the service request message initiated by the client application to the server application, and step 940 to send a reply message, Step 950 receives a message indicating session submission, step 960 sends a message indicating a session submission result, and step 970 sends a reply message; the processing unit 1120 can be used to execute step 930 .

It should be understood that the specific process for each unit to perform the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, details are not repeated here.

It should be understood that the above-mentioned transceiver unit may be designed in an integrated manner, that is, include both receiving and sending functions, or may be designed separately, that is, be replaced by a receiving unit with a receiving function and a sending unit with a sending function.

The processing unit in FIG. 11 may be implemented by at least one processor or processor-related circuits. The transceiver unit may be implemented by a transceiver or transceiver-related circuits. The storage unit can be realized by at least one memory.

As shown in FIG. 12 , the embodiment of the present application further provides a communication device 1200 . The apparatus 1200 includes a transceiver 1210 , and may further include a processor 1220 coupled with a memory 1230 . The transceiver 1230 is used for signal reception and/or transmission. For example, the processor 1220 is configured to control the transceiver 1210 to receive and/or send signals. The memory 1230 is used to store computer programs or instructions and/or data, and the processor 1220 is used to execute the computer programs or instructions and/or data stored in the memory 1230, so that the methods in the above method embodiments are executed. Specifically, the processor 1220 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP. The processor 1220 may further include a hardware chip. The aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof. The aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.

Optionally, the apparatus 1200 includes one or more processors 1220 .

Optionally, as shown in FIG. 12 , the apparatus 1200 may further include a memory 1230 .

Optionally, the apparatus 1200 may include one or more memories 1230 .

Optionally, the memory 1230 may be integrated with the processor 1220, or set separately.

As a solution, the apparatus 1200 is used to implement the operations performed by the client entity or the server entity in the above method embodiments.

The embodiment of the present application also provides a communication device, which includes: a memory for storing a program; a processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is used for executing the above method embodiment A method executed by a client entity or a server entity in .

The embodiment of the present application also provides a computer-readable storage medium, including: the computer-readable medium stores a computer program; when the computer program is executed by one or more processors, the device including the processor executes the method described in the above-mentioned embodiment A method executed by a client entity or a server entity.

The embodiment of the present application also provides a chip, the chip includes a processor and a data interface, and the processor reads the instructions stored on the memory through the data interface, so as to execute the method performed by the client entity or the server entity in the above method embodiment .

The embodiment of the present application also provides a communication node, which includes any one of the above-mentioned devices in Figure 11 to Figure 12, and the communication node can be a domain controller, a gateway, an electronic control unit, a T-box, a sensor, an execution device etc.

The embodiment of the present application also provides a terminal, the terminal includes any one of the above-mentioned devices in Fig. 11 to Fig. 12, and the terminal may be a vehicle, including a vehicle with intelligent driving and assisted driving technology.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more packets of data (e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems). Communicate through local and/or remote processes.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to it or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for So that a computer device (which may be a personal computer, a server, or a network device, etc.) executes all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A communication method, characterized in that,

In response to a service request from a client application to a server application, the client entity acquires quality of service (QoS) information related to the connection between the client application and the server application, where the QoS information includes at least one of the following: service-related domain information, priority information and reliability information;

The client entity sends a service request message from the client application to the server application, and the service request message includes client connection information, QoS control information, and a service request from the client application to the server application. A request sequence, the QoS control information includes an activation indication of one or more items in the QoS information.
According to the method according to claim 1, the sending by the client entity of the service request message from the client application to the server application includes:

The client entity broadcasts the service request message of the client application to the server application.
According to the method according to claim 1, the QoS control information includes a domain activation indication, and the domain activation indication indicates enabling domain control, and the service request message sent by the client entity to the server application by the client application includes:

The client entity sends the service request message of the client application to the server application in a multicast manner in the domain related to the service.
According to the method according to any one of claims 1 to 3, before sending the service request message of the client application to the server application, further comprising:

The QoS information includes priority information, and the client entity schedules the request message for sending according to the priority information.
According to the method according to claim 4, the client entity schedules the request message for sending according to the priority information, comprising:

The client entity determines the dispatch queue corresponding to the priority information from the dispatch queues of the system according to the priority information; the dispatch queue of the system includes at least a first dispatch queue and a second dispatch queue, and the first The sending priority of the scheduling queue is higher than that of the second scheduling queue;

The client entity schedules the request packet to enter the scheduling queue corresponding to the priority information.
According to the method according to claim 5, the client entity schedules the request message to enter the scheduling queue corresponding to the priority information, comprising:

If the scheduling queue corresponding to the priority information includes a plurality of packets to be sent, the client entity sorts the plurality of packets to be sent and the request packets according to the priority information so that those with higher priority Packets are sent with priority.
The method according to any one of claims 1 to 4, further comprising:

The node where the client entity is located has a delay-sensitive network TSN interface device, and the client entity provides the QoS information of the service request message to the TSN interface device, so that the TSN interface device transmits the The service request message is scheduled to the sending queue corresponding to the QoS information.
According to the method according to any one of claims 1 to 7, the QoS control information includes a reliability activation indication, the reliability activation indication indicates activation of reliability control, and the service request message further includes timeout duration information.
According to the method according to any one of claims 1 to 8, the QoS information is configured through a configuration tool, or,

The QoS information is obtained through negotiation between the client entity and the server entity.
A communication method, characterized in that,

The server entity receives the service request message sent by the client entity to the server application by the client application, the service request message includes client connection information, QoS control information, and service request sequence, and the QoS control information Include an indication of enabling one or more items in the QoS information;

The server entity parses the service request message to obtain QoS information corresponding to the client connection;

The server entity processes the service request message from the client application to the server application according to the QoS control information and the QoS information.
The method according to claim 10, wherein the QoS control information includes a domain activation indication, the domain activation indication indicates that domain control is enabled, and the processing of the client application to the server application according to the QoS control information and the QoS information service request message, including:

Determine whether the domain information in the service request message is correct according to the service-related domain in the QoS information. If the domain information is incorrect, the server entity sends a reply message to the client entity, and the reply message carries the The error code corresponding to domain information error.
The method according to claim 10, wherein the QoS control information includes a priority activation indication, the priority activation indication indicates that priority control is enabled, and the processing of the client application pair according to the QoS control information and the QoS information The service request message of the server application, including:

The server entity processes the service request sequence of the client application to the server application according to the priority information;

The server entity sends a reply message to the client entity, and the reply message carries processing information.
The method according to claim 12, wherein the QoS control information includes a reliability activation indication, the reliability activation indication indicates activation of reliability control, and the server entity sends a reply message to the client entity, further comprising: :

determining whether the processing of the service request sequence meets the reliability requirement, and if the processing of the service request sequence does not meet the reliability requirement, the processing information indicates an error corresponding to the failure of the reliability requirement code.
According to the method according to any one of claims 10 to 13, the server entity parses the service request message to obtain the QoS information corresponding to the client connection, including:

The server entity parses and receives the service request message to obtain the client connection information and the QoS control information,

The server entity obtains the QoS information of the client connection from the QoS configuration table according to the QoS control information.
The method according to claim 14, the QoS configuration table is configured by a configuration tool, or,

The QoS configuration table is obtained through negotiation between the server entity and the client entity.
A communication method, characterized in that,

The client entity sends a service discovery message, the service discovery message includes a service identifier, a client identifier, and QoS negotiation request information, and the QoS negotiation request information includes a client instance identifier (ParticipantID) and at least one of the following QoS to be confirmed Information: priority information, reliability information, and domain information published by the service;

The client entity receives the service providing message and QoS negotiation confirmation information of the server entity, the service providing message includes the service instance identifier, and the QoS negotiation confirmation information includes the QoS negotiation information for each item in the QoS negotiation request information. Confirmation of information;

The client entity determines the connection and the QoS information corresponding to the connection according to the service provision message and the QoS negotiation confirmation information.
The method according to claim 16, wherein the client entity sends a service discovery message, comprising:

The client entity broadcasts the service discovery message;

The client entity receives the service provision message and QoS negotiation confirmation information of the server entity, including:

The client entity receives the service provision message sent by the server entity in broadcast mode;

The client entity receives the QoS response message sent by the server entity to the client entity in a unicast manner, where the QoS response message includes the QoS negotiation confirmation information.
The method according to claim 16, wherein the client entity sends a service discovery message, comprising:

The client entity sends the service discovery message in a multicast manner in the service-related domain, and the QoS negotiation information also includes the service-related domain information;

The client entity receives the service provision message and QoS negotiation confirmation information of the server entity, including:

The client entity receives the service provision message sent by the server entity in a multicast manner in the service-related domain;

The client entity receives the QoS response message sent by the server entity to the client entity in a unicast manner, where the QoS response message includes the QoS negotiation confirmation information.
A communication method, characterized in that,

The server entity receives the service discovery message of the client entity, the service discovery message includes a service identifier, a client identifier, and QoS negotiation request information, and the QoS negotiation request information includes a client instance identifier (ParticipantID) and at least one of the following QoS information to be confirmed: priority information, reliability information, and domain information published by the service;

The server entity sends a service provision message and QoS negotiation confirmation information in response to the service discovery message to the client entity, the service provision message includes a service instance identifier, and the QoS negotiation confirmation information includes A confirmation result of each item of QoS information in the QoS negotiation request information.
The method of claim 19, further comprising:

The server entity generates QoS configuration information according to the QoS negotiation request information.
A communication method, characterized in that,

In response to a service request from a client application to a server application, the client entity determines a session corresponding to the service request and session state indication information, where the session includes multiple service requests from the client application to the server application;

The client entity sends a service request message, the service request message includes service connection information and session information, and the session information includes a session identifier and the session state information.
According to the method of claim 21, if the client application needs to lock resources for the service of the server application, the session information further includes a resource identifier.
A method according to claim 21 or 22,

If the session corresponding to the service request is not opened, the session state indication information indicates to open the session, and the service request message does not carry the service request sequence of the client application to the server application.
The method of claim 23, further comprising:

The client entity receives a reply packet sent by the server entity, where the reply packet includes confirmation information that the session is opened successfully.
The method according to any one of claims 21 to 24, further comprising:

If the session corresponding to the service request has been opened, the session state indication information indicates that the session is in progress, and the service request message also includes a service request sequence of the client application to the server application.
The method according to any one of claims 21 to 25, further comprising:

the client entity determines that a service request sequence for all service requests in the session has been sent to the server entity,

The client entity sends a packet indicating the session submission.
The method of claim 26, further comprising:

The client entity receives the message indicating the session submission result sent by the server entity.
A communication method, characterized in that,

The server entity receives a service request message from the client application to the server application sent by the client entity, the service request message includes connection information and session information for the server application to provide services to the client application, and the session information includes A session identifier and the session state information, the session includes multiple service requests from the client application to the server application;

The server entity processes the service request message according to the session information.
According to the method according to claim 28, the session state information indicates opening a session, and the server entity processes the service request message according to the session information, including:

The server entity determines that the session state confirmation information indicates that the opening is successful;

The server entity sends a reply message to the client entity, where the reply message includes the session state confirmation information.
According to the method according to claim 28, the session state information indicates opening a session, the session information also includes a resource identifier, and the server entity processes the service request message according to the session information, including:

The server entity determines that the session state confirmation information indicates that the opening is successful;

The server entity determines whether the resource corresponding to the resource identifier is occupied by other clients, and if the resource corresponding to the resource identifier is occupied by other clients, the session state confirmation information indicates that opening fails; or, if the The resource corresponding to the resource identifier is idle, the session state confirmation information indicates that the opening is successful, and the service terminal entity locks the resource corresponding to the resource identifier;

The server entity sends a reply message to the client entity, where the reply message includes the session state confirmation information.
According to the method according to claims 28 to 30, the session state indication information indicates that the session is in progress, and the service request message further includes the service request sequence of the client application to the server application,

The server entity acquires the service request sequence.
The method of claims 28 to 31, further comprising:

The server entity receives the message from the client entity indicating session submission;

The server entity sends a packet indicating a session submission result to the client entity.
The method of claim 32, further comprising:

the server entity processes a plurality of service request sequences for the session;

The server entity sends a reply message to the client entity to indicate processing results of the plurality of service request sequences.
The method of claim 33, further comprising:

The server entity unlocks the resource corresponding to the resource identifier.
A communication device, configured to execute the method according to any one of claims 1-9, 16-18, 21-27.
A communication device, configured to execute the method according to any one of claims 10-15, 19-20, 28-34.
A computer-readable storage medium, comprising: the computer-readable medium stores a computer program; when the computer program is executed by one or more processors, the device including the processor executes the method described in any one of claims 1 to 34 method.
A chip, comprising a processor and a data interface, the processor reads instructions stored on the memory through the data interface, so as to execute the method as claimed in any one of claims 1 to 34.
A communication node, comprising the communication device according to claim 35 or 36.
The communication node according to claim 39, said communication node comprising: a domain controller, a gateway, an electronic control unit, a T-box, a sensor, and an actuator.
A communication system comprising the communication device according to claim 35 and the communication device according to claim 36.
A vehicle comprising the communication system as claimed in claim 41.