CN114567513B - Method for a multipoint network system - Google Patents

Method for a multipoint network system Download PDF

Info

Publication number
CN114567513B
CN114567513B CN202011362736.5A CN202011362736A CN114567513B CN 114567513 B CN114567513 B CN 114567513B CN 202011362736 A CN202011362736 A CN 202011362736A CN 114567513 B CN114567513 B CN 114567513B
Authority
CN
China
Prior art keywords
endpoint
request message
sleep
wake
network system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011362736.5A
Other languages
Chinese (zh)
Other versions
CN114567513A (en
Inventor
苏敬堯
张永乐
朱元志
杜明哲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Realtek Semiconductor Corp
Original Assignee
Realtek Semiconductor Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Realtek Semiconductor Corp filed Critical Realtek Semiconductor Corp
Priority to CN202011362736.5A priority Critical patent/CN114567513B/en
Publication of CN114567513A publication Critical patent/CN114567513A/en
Application granted granted Critical
Publication of CN114567513B publication Critical patent/CN114567513B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/12Arrangements for remote connection or disconnection of substations or of equipment thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/40006Architecture of a communication node
    • H04L12/40039Details regarding the setting of the power status of a node according to activity on the bus
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40208Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215Controller Area Network CAN
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L2012/40267Bus for use in transportation systems
    • H04L2012/40273Bus for use in transportation systems the transportation system being a vehicle
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/50Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

The present disclosure relates to a method for a multipoint network system. A method for a multipoint network system, comprising: sending a sleep request message from the first endpoint to the second endpoint; and determining whether the first endpoint enters a sleep state from an awake state according to the second endpoint sending a sleep acknowledgement message in response to the sleep request message.

Description

Method for a multipoint network system
Technical Field
The present disclosure relates to methods for multi-drop (multipoint) network systems, and more particularly to methods for performing sleep and wake-up procedures in a multipoint network system.
Background
A multipoint network system is a network system in which a plurality of endpoints are connected to each other by transmission lines, and is applicable to control of vehicle equipment. However, the current multipoint network system does not provide reliable sleep and wake-up functions, and if the sleep and wake-up process is performed, the overall performance of the multipoint network system is limited only in a point-to-point manner.
Disclosure of Invention
The present disclosure is directed to a method for a multipoint network system, which can perform a one-to-many sleep process and wake-up process under the multipoint network system, and provide reliable sleep and wake-up functions to improve the overall performance of the multipoint network system, and further perform a partial endpoint wake-up function to achieve the effect of a local network (partial networking).
One aspect of the present disclosure is a method for a multi-point network system having a plurality of endpoints connected to each other, the method comprising: sending a sleep request message from a first one of the endpoints to at least a second one of the endpoints; and determining whether the first endpoint enters the sleep state from the awake state according to the situation that the at least one second endpoint transmits the sleep acknowledgement message in response to the sleep request message.
Another aspect of the present disclosure is a method for a multi-point network system having a plurality of endpoints connected to each other, the method comprising: sending a wake-up request message from a first one of the endpoints to a second one of the endpoints; and determining whether the second endpoint enters the wake-up state from the sleep state according to the content of the wake-up request message.
Yet another aspect of the present disclosure is a method for a multi-point network system having a plurality of endpoints connected to each other, the method comprising: enabling a first endpoint of the endpoints to actively enter an awake state from a sleep state, and sending an endpoint list request message from the first endpoint; and updating the stored endpoint list by the second endpoint receiving the endpoint list request message according to the endpoint index of the endpoint list request message, and correspondingly transmitting endpoint list update message containing endpoint list data to the multipoint network system.
Drawings
For a more complete understanding of the embodiments and advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a multi-drop network system according to an embodiment of the present invention;
FIG. 2 is a state diagram of any one of the endpoints of the multi-point network system of FIG. 1;
FIG. 3 is a flow chart of a method for the multi-point network system of FIG. 1 according to an embodiment of the present invention;
FIG. 4 is a flow chart of a method for the multi-point network system of FIG. 1 according to an embodiment of the present invention; and
FIG. 5 is a flow chart of a method for the multi-point network system of FIG. 1 according to an embodiment of the invention
Detailed Description
Embodiments of the present disclosure are discussed in detail below. However, it is to be understood that the embodiments provide many applicable concepts that can be embodied in a wide variety of specific contexts. The particular embodiments discussed are illustrative only and are not limiting of the scope of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. Unless otherwise limited, the singular forms "a", "an" and "the" are intended to mean the plural forms as well.
It will be understood that, although the terms "first," "second," "third," and the like may be used herein to describe various signals and/or entities, these signals and/or entities should not be limited by these terms. Such terms are merely used to distinguish one signal and/or entity from another signal and/or entity.
For simplicity and clarity of illustration, reference numerals and/or letters may be reused herein in the various embodiments, but this is not meant to indicate causal relationships between the various embodiments and/or configurations discussed.
Herein, the information related to the wake-up procedure and the sleep procedure, such as a sleep request message, a sleep acknowledgement message, a wake-up request message, a wake-up acknowledgement message, an endpoint list request message, an endpoint list update message, etc., includes fields in the format of an instruction and a node index, etc., wherein the instruction field is used to indicate the type of the information, and the node index field is used to indicate why the destination endpoint index is.
Fig. 1 is a schematic diagram of a multi-drop (multittop) network system 100 according to an embodiment of the invention. In the multipoint network system 100, the endpoint 110 1 -110 N Are in communication with each other. As shown in fig. 1, in the present embodiment, the multipoint network system 100 has a bus (bus) topology, i.e., endpoints 110 1 -110 N Commonly connected to bus 120. In other embodiments, in multipoint network system 100, endpoint 110 1 -110 N May be interconnected via bus 120. Endpoint 110 1 -110 N Each comprising a control unit 112 1 -112 N And transceiver circuit 114 1 -114 N . Control unit 112 1 -112 N For controlling the transmission and reception of messages and controlling the transceiver circuits 114 respectively 1 -114 N And transceiver circuit 114 1 -114 N Each has the functions of receiving and transmitting signals and detecting analog and digital signals. If the multipoint network system 100 is an ethernet (automotive Ethernet) system, each control unit 112 1 -112 N May be, for example, an electronic control unitA meta (electronic control unit; ECU), a hybrid control unit (hybrid control unit; HCU), a processor, a microprocessor, or a microcontroller (microcontroller), but is not limited thereto. In addition, the multipoint network system 100 may conform to specifications of 10BASE-T1, 10BASE-T1S, controller area network (Controller Area Network; CAN), and/or data line power (Power over Data Lines; poDL), and each endpoint 110 1 -110 N May be a device that complies with the Sleep/Wake-up Specification of the single pair ethernet Alliance (OPEN Alliance).
If at endpoint 110 1 -110 N Endpoint 110 in (a) n Switch, or electronic device with switch function, endpoint 110 n The interfaces used to receive and forward messages may be different ports (ports). That is, endpoint 110 n A message is received via one of the ports and forwarded from the other port to the other endpoint. In addition, the multipoint network system 100 may be connected to the endpoint 110 via a network connection 1 -110 N One or more of the nodes may be communicatively coupled to other network systems.
Fig. 2 is a state transition diagram of any node in the multipoint network system 100. The state transition diagram shown in fig. 2 includes an awake state 210 and a sleep state 220. With end point 110 i For example, if in the awake state 210, the endpoint 110 i Can have normal operation, including normal message transmission; if in sleep state 220, endpoint 110 i Is limited in operation, and only partial operation can be performed to achieve the power saving effect.
Further, sleep state 220 may be divided into a deep sleep state 222, a shallow sleep state 224, and a false alarm state 226. With end point 110 i For example, endpoint 110 may be in deep sleep state 222 i Only the analog signal detection function is turned on but other functions (e.g., the digital signal detection function is turned off) are turned off to minimize power consumption; endpoint 110 is in the shallow sleep state 224 i Starting the digital signal detection function and judging whether the detected message is a wake-up request message or not; endpoint 110 during false alarm state 226 i The digital signal detection function is turned off,and detects when the signal receiving and transmitting channel is silent.
If it is endpoint 110 i Upon detecting an incoming signal in the deep sleep state 222, the endpoint 110 i From the deep sleep state 222, a shallow sleep state 224 is entered, the digital signal detection function is turned on, and it is determined whether the detected message is an awake request message. If the received message is determined to be a wake-up request message, and the wake-up endpoint index in the wake-up request message is the same as or the global index, then endpoint 110 i The awake state 210 is entered from the light sleep state 224 for normal operation. If the received message is not determined to be a wake-up request message, or if the received message is determined to be a wake-up request message, but the wake-up endpoint index in the wake-up request message is different from the endpoint index or is not the global index, then endpoint 110 i The light sleep state 224 is entered into the false alarm state 226, the digital signal detection function is stopped, and the signal receiving and transmitting channel is detected when it is silent, and the false alarm state 226 is entered into the deep sleep state 222. In this way, the endpoint 110 may be enabled i In the lowest power consumption mode most of the time.
Fig. 3 is a flow chart of a method 300 for the multipoint network system 100 according to an embodiment of the present invention. First, step S310 is performed at the endpoints 110 1 -110 N Endpoint 110 in (a) i In the event that a sleep state is to be entered from an awake state, endpoint 110 thereby i Sending Sleep request message sleep_req to other endpoints in the multi-point network system 100 (endpoint 110 at this time i A node that actively triggers sleep flows), i.e., endpoint 110 1 -110 (i-1) 、110 (i+1) -110 N . Sleep request message sleep_req may be broadcast (broadcast) by endpoint 110 i And (5) sending out. Next, step S320 is performed to determine the endpoint 110 according to the situation that the other endpoint sends the Sleep acknowledgement message sleep_ack in response to the Sleep request message sleep_req i Whether to enter a sleep state from an awake state. Under normal conditions, each of the other endpoints that does not enter sleep state is receiving endpoint 110 i After the Sleep request message sleep_req is sent, a message for responding to the Sleep request is sentSleep acknowledgement message Sleep Ack for message sleep_req to endpoint 110 i . Thus, if it is endpoint 110 i The number of Sleep acknowledgement messages received is the same as the number of wake-up endpoint indexes in the endpoint list stored in the Sleep acknowledgement message, so that it can be determined that all endpoints not entering Sleep state in other endpoints have received endpoint 110 i The Sleep request message sleep_req is sent and is responded to the Sleep acknowledgment message sleep_ack it received, and then endpoint 110 i Update its stored endpoint list (update its own endpoint 110 i The state of (2) is updated from the awake state to the sleep state) and a flag (flag) is set. Control unit 112 i Read to endpoint 110 i After setting up the flag, the transceiver circuit 114 is controlled i And sending the updated endpoint list to all nodes in the awakening state in the multipoint network system, and then entering a sleep state from the awakening state.
Determining endpoint 110 i Whether to enter sleep state is comparison endpoint 110 i Whether the number of Sleep acknowledgement messages sleep_ack received within a predetermined time after sending the Sleep request message sleep_req is the same as that of the endpoint 110 i The number of wake-up endpoint indexes in the stored endpoint list.
Endpoint 110 i The timer may be started while the Sleep request message sleep_req is sent. If Sleep acknowledgment (sleep_ack) messages sent by all nodes in the awake state are received before the timer expires, the endpoint 110 i The timer is stopped and the sleep state is entered from the awake state. Conversely, if the Sleep Ack message sleep_ack sent by all nodes in the awake state is not completely received when the timer expires, the endpoint 110 i The Sleep request message sleep_req is retransmitted and the timer is restarted. If the number of times of retransmitting the Sleep request message sleep_req reaches the predetermined maximum number of times of retransmitting the Sleep request message and all Sleep acknowledgement messages sleep_ack sent by the nodes in the awake state are not received yet when the timer expires, the endpoint 110 i The sleep procedure is cancelled, i.e. remains in the awake state without entering the sleep state.
Fig. 4 is a flow chart of a method 400 for the multipoint network system 100 according to an embodiment of the present invention. First, step S410 is performed, and the endpoint 110 in the multipoint network system 100 i To wake up another endpoint 110 j Is performed by endpoint 110 i Sending Wakeup request message wakeup_req1 to endpoint 110 j . According to each wake scenario, the wake request message wakeup_req1 may be a global wake request message or a selective wake request message. That is, the wake-up endpoint index in the wake-up request message wakeup_req1 may be a global index or a wake-up endpoint index corresponding to a specific endpoint. For example, if all nodes in the multipoint network system 100 are to be awakened, a global wakeup request message may be sent; if a single or partial node in the multi-point network system 100 is to be awakened, a selective awakening request message including the awakening endpoint index of the node to be awakened may be sent.
Endpoint 110 i The Wakeup request message wakeup_req1 may be sent singly or in succession depending on system settings, hardware performance, and/or other conditions. In some embodiments, endpoint 110 i The Wakeup request message wakeup_req1 is sent continuously with a predetermined number of consecutive transmissions. Due to the endpoint 110 j May be in a deep sleep state, which may consume some time from the detection of the analog signal to the start of the discrimination of the message after entering the shallow sleep state, so that the signal is detected at the terminal 110 j In situations where hardware performance is limited, endpoint 110 i The Wakeup request message wakeup_req1 may be sent continuously to the endpoint 110 for a predetermined number of consecutive transmissions over a period of time j To ensure that wake-up_req 1 is received by endpoint 110 j And receiving and processing.
Next, step S420 is performed, after receiving the Wakeup request message wakeup_req1, the endpoint 110 j According to the content of wake-up_req 1, it is determined whether to enter the wake-up state from the sleep state. When it is determined that the wake-up endpoint index of the wake-up request message wakeup_req1 is the same as the endpoint index thereof, or when it is determined that the wake-up endpoint index of the wake-up request message wakeup_req1 is the global index, the endpoint 110 j I.e., enter the awake state from the sleep state, and it transmits an awake acknowledge message wakeup_ack1 to the endpoint 110 in response to the Wakeup request message wakeup_req1 i . At receiving endpoint 110 j Endpoint 110 when sending wake-up_Ack1 i Updating the stored endpoint list to correspond to endpoint 110 j Is updated by the sleeping node to the waking node. Endpoint 110 i After updating its stored endpoint list, a flag (flag) is set up, and the control unit 112 i Read to endpoint 110 i After setting up the flag, the transceiver circuit 114 is controlled i And sending the endpoint list to all nodes in the wake-up state in the multipoint network system. Due to the endpoint 110 i Nodes other than node are not actively triggering the wake-up process, so that node 110 is not actively triggering the wake-up process i All nodes in awake state except for the receiving endpoint 110 i After the endpoint list data is sent, the stored endpoint list is updated according to the endpoint list data. If except for the end point 110 i Any node other than and in the awake state is receiving endpoint 110 i The sending endpoint list is preceded by a flag that is set up before it receives endpoint 110 i After sending the endpoint list data, the previously established flag is cleared.
Endpoint 110 i The timer may be started while the Wakeup request message wakeup_req1 is sent. If wake-up_Ack1 is received before the timer expires, the endpoint 110 i The timer is stopped. Conversely, if the Wakeup acknowledgment wakeup_Ack1 is not yet received at the expiration of the timer, the endpoint 110 i Resending Wakeup request message wakeup_req1 to endpoint 110 j The timer is restarted. If the number of times of resending the Wakeup request message wakeup_req1 reaches the predetermined maximum number of times of resending the Wakeup request message and the Wakeup acknowledgement message wakeup_Ack1 is not received at the expiration of the timer, the endpoint 110 is represented j May not wake up due to some factor, or endpoint 110 j May have been disconnected from the multipoint network system 100. In this case, endpoint 110 i Does not update the corresponding endpoint 110 in its stored endpoint list j Is a state of (2).
In some embodiments, if the multipoint network system 100 is different from the endpoint 110 i 、110 j Endpoint 110 of (2) k Detecting endpoint 110 j Transmitted wake-up acknowledgementThe endpoint 110 sends a wakeup_Ack1 acknowledgement k The corresponding endpoint 110 may be updated according to the Wakeup confirm message wakeup_Ack1 to update its stored endpoint list j Is updated by the sleeping node to the waking node. Thus, the endpoint 110 k May be waiting at endpoint 110 i Aware endpoint 110 prior to sending updated endpoint list data j Has entered the awake state and may advance endpoint 110 further k Begin transmitting data to endpoint 110 j Is a time of (a) to be used.
In some embodiments, endpoint 110 i Transmitting endpoint list data to a multipoint network system 100 except for endpoint 110 j All endpoints except those in the awake state update their stored endpoint lists accordingly.
The multipoint network system 100 may generate an exception condition that the endpoint that has entered the awake state receives the awake request message, for example, the awake procedure is triggered by the endpoint, the awake acknowledgement message sent by the endpoint is missed, or other exception conditions. In some embodiments, if endpoint 110 j Upon entering the awake state from the sleep state, endpoint 110 is received k The endpoint 110 sends a wake-up request message wakeup_req2 j Judging whether the wake-up endpoint index of the wake-up request message wakeup_req2 is identical to the endpoint index thereof. If yes, then endpoint 110 j Transmitting Wakeup acknowledgement message wakeup_Ack2 to endpoint 110 in response to second Wakeup request message wakeup_Req2 k To inform endpoint 110 j Has been in an awake state.
In other embodiments, multiple endpoints in the same multipoint network system 100 may be awakened by a single endpoint. For example, if endpoint 110 i Endpoint to be awakened 110 j 、110 k It sends a Wakeup request message wakeup_req1 to each endpoint 110 j 、110 k And starts a timer. If the slave endpoint 110 is received before the timer expires j 、110 k Respectively sent Wakeup acknowledgement message wakeup_Ack1, endpoint 110 i Stop the timer and update its stored endpoint list to correspond to endpoint 110 j 、110 k Is updated by sleep node toThe node is awakened and a flag is set after updating its stored endpoint list. Conversely, if the slave endpoint 110 is not fully received at the expiration of the timer j 、110 k Respectively sent Wakeup acknowledgement message wakeup_Ack1, endpoint 110 i Retransmitting Wakeup request message wakeup_req1 to the endpoint corresponding to Wakeup confirm message wakeup_ack1 which has not been received, and restarting the timer. If the number of times of resending the Wakeup request message wakeup_req1 reaches the predetermined maximum number of times of resending the Wakeup request message and the full receipt of the slave endpoint 110 is not received yet when the timer expires j 、110 k Respectively sent Wakeup acknowledgement message wakeup_Ack1, endpoint 110 i The state of the endpoint corresponding to the Wakeup confirm message wakeup_ack1 which is not received in the stored endpoint list is not updated.
In some applications, if at endpoint 110 1 -110 N Endpoint 110 in (a) n A switch having a first port and a second port, wherein the first port is connected to other endpoints in the multipoint network system 100 and the first port is connected to other network systems (including but not limited to multipoint network systems), then when endpoint 110 n When the wake-up request message is received through the first port, the wake-up request message can be forwarded to other network systems through the second port, so as to wake up one or more endpoints in the other network systems.
Fig. 5 is a flow chart of a method 500 for the multipoint network system 100 according to an embodiment of the present invention. First, step S510 is performed by the endpoint 110 in the multipoint network system 100 i Performing local wake-up operation, actively entering wake-up state from sleep state, and after entering wake-up state, sending endpoint list request message except endpoint 110 in multipoint network system 100 i Except for all endpoints in the awake state. Next, step S520 is performed, and the endpoint in the awake state receives the endpoint 110 i After the endpoint of the endpoint list request message is sent, the stored endpoint list is updated according to the endpoint index of the endpoint list request message, and the updated endpoint list is sent to the multipoint network system 100.
For example, when a multipoint network isEndpoint 110 in a wake state in system 100 j Receiving endpoint 110 i Endpoint 110 when sending endpoint list request messages j Updating the stored endpoint list to correspond to endpoint 110 i Is updated by the sleeping node to the waking node. Endpoint 110 then j Set up flags, and control unit 112 j After detecting the flag, the transceiver circuit 114 is controlled j The updated endpoint list is sent to the multipoint network system 100 and the flag is cleared after the transmission is completed. Except for the end point 110 j All nodes in the awake state except for the node receiving the message from the endpoint 110 j After the endpoint list updating message is sent, the stored endpoint list is updated according to the endpoint list data in the endpoint list updating message. Except for the end point 110 j Any node other than and in the awake state is receiving a message from endpoint 110 j If a flag is set before the endpoint list update message is sent, whether the endpoint list update message is a node actively triggering a wake-up process or a node actively triggering a sleep process is further determined. If so, it is received by endpoint 110 j After the sent endpoint list update message, the previously established flag is maintained; otherwise, it is received by endpoint 110 j After the endpoint list update message is sent, the previously established flag is cleared. In some embodiments, endpoint 110 j Sending endpoint list update messages including endpoint list data to endpoint list stored in the multipoint network system 100 except for endpoint 110 i All other endpoints in the awake state, so that the endpoints update their stored endpoint lists accordingly, will correspond to endpoint 110 i Is updated by the sleeping node to the waking node. In this way, the endpoints may be further advanced to begin transmitting data to endpoint 110 i Is a time of (a) to be used.
In some embodiments, if endpoint 110 i Upon entering the awake state from the sleep state, endpoint 110 is received k The endpoint 110 sends a wake-up request message wakeup_req i Judging whether the wake-up endpoint index of the wake-up request message wakeup_req is identical to the endpoint index thereof. If yes, then endpoint 110 i Transmits in response to wake-up request message wakeup_reqWake-up_ack message to endpoint 110 k To inform endpoint 110 i Has been in an awake state.
In some embodiments, if the multipoint network system 100 is different from the endpoint 110 i 、110 k Endpoint 110 of (2) l Detecting endpoint 110 i Sent Wakeup confirm message wakeup_ack, endpoint 110 l The stored endpoint list can be updated according to wakeup_ack for the Wakeup confirm message to correspond to endpoint 110 i Is updated by the sleeping node to the waking node. In this way, the endpoint 110 can be further advanced l Begin transmitting data to endpoint 110 i Is a time of (a) to be used.
In addition, in the embodiment of the present invention, each wake-up node may be used as an initial sending node and send a paging request (roll call request) message at a specific time or periodically, and after other nodes in the same multipoint network system in a wake-up state receive the paging request message sent by the initial node, the paging request message is also sent to the endpoint that sent the paging request previously. In some embodiments, after receiving the paging request message sent by the originating node, other nodes in the awake state in the same multipoint network system respond only to the paging request message sent by the originating node. The paging request message includes the global index and the sender endpoint index, or only the sender endpoint index. If any endpoint in the wake-up state detects the call request message and the information of the sender corresponding to the call request message is the sleep node in the stored endpoint list, the information of the sender is updated from the sleep node to the wake-up node. In some embodiments, if any endpoint in the awake state detects the paging request message and the information corresponding to the sender of the paging request message is a sleep node in the stored endpoint list, the endpoint updates the sender information from the sleep node to the awake node and sends out the updated endpoint list. In some embodiments, the originating node sends out a new endpoint list when the endpoint list that received the response to the round robin request does not match the endpoint list stored therein for a period of time. By the way of sending the call request message at specific time or periodically, the consistency of the endpoint list content stored by all nodes in the wake-up state can be ensured.
For example, if endpoint 110 is in an awake state in multipoint network system 100 i As an initiating sending node and sending a round robin request message to endpoint 110, which is also in an awake state j 、110 k Endpoint 110 j 、110 k Receiving endpoint 110 i After sending the paging request message, sending the paging request message to the endpoint 110 respectively i . If endpoint 110 i Endpoint 110 is not received within a period of time (e.g., 100 milliseconds) after it sends the call request message k The transmitted paging request message is then resent to the endpoint 110 k The method comprises the steps of carrying out a first treatment on the surface of the If the number of retransmissions reaches the upper limit and endpoint 110 i Endpoint 110 has not yet received k The transmitted round robin request message identifies endpoint 110 k Endpoints other than those in the awake state and update the stored endpoint list will correspond to endpoint 110 i Is updated from the wake-up node to the sleep node and sent to the updated endpoint list to the multipoint network system 100. In addition, if the terminal 110 j Detecting endpoint 110 k The sent wake-up acknowledgement message corresponds to endpoint 110 in its stored endpoint list k If the information of (a) is sleep node, updating its stored endpoint list to correspond to endpoint 110 k Is updated by the sleeping node to the waking node.
In summary, the method for a multi-point network system of the present disclosure can provide reliable sleep and wake-up functions under the multi-point network system, so as to improve the overall performance of the multi-point network system, and further perform a partial endpoint wake-up function to achieve the effect of local network.
While the present disclosure has been described with reference to the above embodiments, it should be understood that the invention is not limited thereto, but may be variously modified and modified by those skilled in the art without departing from the spirit and scope of the present disclosure, and the scope of the present disclosure is accordingly defined by the appended claims.
[ symbolic description ]
100 multipoint network system
110 1 -110 N End point
112 1 -112 N Control unit
114 1 -114 N Transmit-receive circuit
120 bus
210 awake state
220 sleep state
222 deep sleep state
224 shallow sleep state
226 false alarm condition
300,400,500 methods
310,320,410,420,510,520 step

Claims (8)

1. A method for a multipoint network system having a plurality of endpoints connected to each other, the method comprising:
sending a sleep request message from a first endpoint to at least a second endpoint; and
determining whether the first endpoint enters a sleep state from an awake state according to the status of the at least one second endpoint sending a sleep acknowledgement message in response to the sleep request message,
wherein the sleep request message is sent by broadcasting, and determining whether the first endpoint enters a sleep state is comparing whether the number of sleep confirmation messages received by the first endpoint within a preset time after sending the sleep request message is equal to the number of wake-up endpoint indexes in an endpoint list stored by the first endpoint.
2. The method of claim 1, wherein the first endpoint enters a sleep state from an awake state if the first endpoint receives a sleep acknowledgement message sent by each of the at least one second endpoint within a predetermined time after sending the sleep request message; otherwise, if the first endpoint does not receive the sleep confirmation message sent by each of the at least one second endpoint within a preset time after the first endpoint sends the sleep request message, the first endpoint is kept in an awake state.
3. The method of claim 1, wherein the first endpoint only turns on analog signal detection after the first endpoint enters a sleep state.
4. A method for a multipoint network system having a plurality of endpoints connected to each other, the method comprising:
sending a first wake-up request message from a first endpoint to a second endpoint; and
determining whether the second endpoint enters the awake state from the sleep state according to the content of the first awake request message,
when the second endpoint judges that the wake-up endpoint index of the first wake-up request message is the same as the endpoint index or is a global index, the second endpoint enters a wake-up state from a sleep state, and responds to the first wake-up request message to send a first wake-up confirmation message to the first endpoint.
5. The method of claim 4 wherein the first wake-up request message is repeated and sent continuously with a predetermined number of repeated transmissions.
6. The method according to claim 4, wherein the second endpoint determines whether the awake endpoint index of the second awake request message is the same as the endpoint index of the second awake request message when the second endpoint receives a second awake request message transmitted by a third endpoint of the endpoints after the second endpoint enters the awake state from the sleep state; if yes, a second wakeup confirmation message is sent to the third endpoint in response to the second wakeup request message.
7. The method of claim 4, wherein the multipoint network system further comprises a switch having a first port and a second port, wherein the first port is connected to the endpoints of the multipoint network system and the second port is connected to another network system, and when the switch receives a third wake request message through the first port, the switch forwards the third wake request message to the another network system through the second port, thereby waking up at least one endpoint in the another network system.
8. A method for a multipoint network system having a plurality of endpoints connected to each other, the method comprising:
enabling a first endpoint to actively enter an awake state from a sleep state, and sending an endpoint list request message from the first endpoint; and
updating the stored endpoint list by a second endpoint that receives the endpoint list request message according to the endpoint index of the endpoint list request message, and correspondingly transmitting an endpoint list update message containing endpoint list data to the multipoint network system.
CN202011362736.5A 2020-11-27 2020-11-27 Method for a multipoint network system Active CN114567513B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011362736.5A CN114567513B (en) 2020-11-27 2020-11-27 Method for a multipoint network system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011362736.5A CN114567513B (en) 2020-11-27 2020-11-27 Method for a multipoint network system

Publications (2)

Publication Number Publication Date
CN114567513A CN114567513A (en) 2022-05-31
CN114567513B true CN114567513B (en) 2024-03-12

Family

ID=81712294

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011362736.5A Active CN114567513B (en) 2020-11-27 2020-11-27 Method for a multipoint network system

Country Status (1)

Country Link
CN (1) CN114567513B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804640A (en) * 2009-06-26 2012-11-28 Lg电子株式会社 Apparatus And Method For Operating Sleep Mode
CN104202800A (en) * 2014-07-09 2014-12-10 京信通信系统(中国)有限公司 Energy-saving method, device and system for femtocell
CN104753693A (en) * 2013-12-25 2015-07-01 达创科技股份有限公司 Network system and connection method thereof
CN108513345A (en) * 2018-03-28 2018-09-07 深圳市华奥通通信技术有限公司 A kind of two-way waking method and system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040203976A1 (en) * 2002-12-30 2004-10-14 Gupta Vivek G. Power management for nodes coupled to a communication link
KR101778958B1 (en) * 2010-03-09 2017-09-18 삼성전자주식회사 Communication method of a terminal and a access point for power saving of multiuser
JP5626266B2 (en) * 2012-06-05 2014-11-19 株式会社デンソー Communications system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102804640A (en) * 2009-06-26 2012-11-28 Lg电子株式会社 Apparatus And Method For Operating Sleep Mode
CN104753693A (en) * 2013-12-25 2015-07-01 达创科技股份有限公司 Network system and connection method thereof
CN104202800A (en) * 2014-07-09 2014-12-10 京信通信系统(中国)有限公司 Energy-saving method, device and system for femtocell
CN108513345A (en) * 2018-03-28 2018-09-07 深圳市华奥通通信技术有限公司 A kind of two-way waking method and system

Also Published As

Publication number Publication date
CN114567513A (en) 2022-05-31

Similar Documents

Publication Publication Date Title
WO2021082301A1 (en) Sleep and wakeup method for in-vehicle hybrid network comprising in-vehicle ethernet
US7881344B2 (en) Communication network system and wakeup method for un-wakeup node
CN108933719B (en) Vehicle-mounted CAN network management method, vehicle-mounted CAN network and vehicle
KR101580622B1 (en) Power save proxy in communication networks
US8630606B2 (en) Communications terminals for reducing power consumption and methods thereof
EP1774812A1 (en) System and method for providing upnp announcements convergence
CN109639543A (en) A kind of method and system of automobile bus load reduction
TWI763136B (en) Methods for multidrop network system
JPH0662021A (en) Communication system
JP2017092565A (en) Sleep control method
CN114567513B (en) Method for a multipoint network system
CN110509870B (en) Vehicle-mounted CAN network and vehicle-mounted CAN network management method
CN107888472B (en) Vehicle network management method, control gateway, controller and automobile
JP2015154189A (en) Communication system, gateway device, communication node and communication control method
JP6028717B2 (en) COMMUNICATION SYSTEM, GATEWAY DEVICE, AND COMMUNICATION METHOD
CN104052659B (en) Gateway used for vehicle network signal forwarding and method for vehicle network signal forwarding
CN106789510B (en) Data communication method of redundant CAN bus communication system
CN114670762A (en) Vehicle-mounted equipment wake-up control method and device and electric vehicle
CN111478838B (en) High-efficiency high-bandwidth communication method and system
CN114670764A (en) Method and device for controlling whole-vehicle dormancy of electric vehicle and electronic control unit
CN116055550A (en) Processing method, system, ECU and equipment based on vehicle-mounted OSEK network management
CN116366394A (en) Network management method and device of vehicle-mounted electronic control unit and control unit
Suermann et al. Power saving in automotive Ethernet
JP3483547B2 (en) Communication system and communication control device
CN114257962A (en) Network node, method for adjusting state of network node, and computer-readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant