CN112463204A - Pile service program gray level release method without sensing of direct connection charging pile - Google Patents
Pile service program gray level release method without sensing of direct connection charging pile Download PDFInfo
- Publication number
- CN112463204A CN112463204A CN202011256138.XA CN202011256138A CN112463204A CN 112463204 A CN112463204 A CN 112463204A CN 202011256138 A CN202011256138 A CN 202011256138A CN 112463204 A CN112463204 A CN 112463204A
- Authority
- CN
- China
- Prior art keywords
- pile
- service program
- gateway
- service
- switching
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
- G07F15/003—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity
- G07F15/005—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity dispensed for the electrical charging of vehicles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a pile service program gray level release method without perception of a direct connection charging pile, which comprises the following steps: the charging pile firstly directly connects a gateway program through TCP, and then the gateway directly connects a back-end pile service program through TCP, after the gateway receives the pile connection, a protocol frame from the charging pile is analyzed, and the corresponding relation between the pile equipment identification and the TCP connection is maintained in a memory; the operation and maintenance personnel start a new version of service program, and simultaneously keep the current connection and service unchanged; the administrator adds the new version of the service program address into the switching target option list; the operation and maintenance personnel release the rear-end pile service program in gray scale according to different space dimensions; and the gateway is disguised as a charging pile, sends a registration request to a pile service program, and reinjects the pile into the charging platform under the condition that the directly connected pile is not sensed. The method can be used for post-by-post service program gray level release, charging station-by-charging station and city-by-city, and smoothly transiting the service to the newly released service program.
Description
Technical Field
The invention relates to the technical field of internet and charging piles, in particular to a pile service program gray level release method without perception of a direct-connection charging pile.
Background
Referring to the standard of the middle power connection T/CEC 102, the charging pile of the electric automobile is connected into a charging service platform through a mobile SIM card at present. And the stub program is connected with the back-end stub service program developed by each platform in a mode of establishing TCP connection and directly connecting. The upgrade and restart of the back-end service will cause the connection between the stub and the service to be disconnected, and the charging service will be interrupted briefly.
Charging platform operators often choose to upgrade in the morning and inform customers and corporate management layers in advance. But the electricity price is relatively cheap in the morning, and many buses and operation vehicles still charge in the morning, and the sudden restart of the service can influence the charging of the buses and operation vehicles. And the operating vehicle has high requirement on the availability of the charging service platform, and once the charging service platform is not charged, the normal development of company operation business is influenced.
In order to reduce the release risk of a new version of a service program, the internet platform is mostly upgraded by adopting a gray release mode: new and old versions coexist in a period of time, more and more users are gradually guided to the new versions, and once problems are found, the flow can be quickly switched back to the stable old versions.
For a general gateway program of the internet, the life cycles of upstream and downstream TCP connections on the whole link are consistent, that is, when a TCP connection from a gateway to a back end is disconnected, the disconnection between a corresponding stub and the gateway is necessarily triggered. The communication protocol of the charging platform is a proprietary protocol developed by each operator according to the T/CEC 102 standard, and is not a universal HTTP protocol. When the universal gateway cannot analyze the private protocol content, the connection is determined according to the IP of the request end, and the IP of the SIM card on the stub is dynamically allocated by a network operator, so that the gray level issue is difficult to be carried out pile by pile, station by station and city by using the universal gateway.
Disclosure of Invention
In order to improve the usability of the charging platform and the charging user experience, the invention provides a pile service program gray scale release method without sensing of a directly-connected charging pile, the method can keep the TCP connection to the pile continuous and the charging pile and the charging user do not have the sensing function, and the method has the advantages of charging service upgrading, uninterrupted charging service during gray scale release and the like; the pile-by-pile, charging station-by-charging station and city-by-city service program gray release can be carried out, and the service is smoothly transited to the newly released service program.
In order to achieve the technical purpose, the invention provides a technical scheme that a pile service program gray level release method without perception of a direct connection charging pile comprises the following steps:
the charging pile firstly directly connects a gateway program through TCP, and then the gateway directly connects a back-end pile service program through TCP, after the gateway receives the pile connection, a protocol frame from the charging pile is analyzed, and the corresponding relation between the pile equipment identification and the TCP connection is maintained in a memory;
the operation and maintenance personnel start a new version of service program, and simultaneously keep the current connection and service unchanged;
the administrator sets the switching parameters and the HTTP switching request authentication password through a local command terminal program of the gateway, and adds the service program address of the new version into the switching target option list;
the operation and maintenance personnel release the rear-end pile service program in gray scale according to different space dimensions;
the gray level release gateway periodically trains switching requests, inquires the corresponding relation between pile equipment identification and TCP connection maintained in a memory before, finds a link to be switched, and connects the specified pile to a new version service program;
after the connection of the rear end is successfully switched, the gateway is disguised as a charging pile, a registration request is sent to a pile service program, the pile is reinjected to the charging platform under the condition that the direct-connected pile is not sensed, and the rear end service node is convenient to send a charging request to the charging pile through a new pile service.
In the scheme, during gray scale release, the switching is not simply carried out on the basis of a request path, weight or client IP as a common gateway, but on the basis of a pile equipment identification list; the reason for this is based on the stub device identity rather than the client IP, because the IP of the charging pile SIM card is dynamically assigned by the mobile network operator and reconnects may change, but the stub device identity is statically configured and fixed.
Preferably, when the operation and maintenance personnel release the gray level of the back-end pile service program, the method comprises the following steps:
determining the space dimension involved in the gray release; the spatial dimension comprises making gray levels according to piles, making gray levels according to charging stations and making gray levels according to cities;
determining a time span; the time span includes: observing how long each batch of piles is switched, and continuing to switch the next batch and estimating how long the whole upgrading is finished;
the operation and maintenance personnel send the pile equipment identification list and the switching target address to a gateway HTTP service through a remote HTTP request;
after receiving the request, the HTTP service program checks the target address and the request key MD5, and after the check is passed, records the request to the local by way of the shared memory.
In this scheme, the gateway not only supports sending the switching request and inquiring the switching result through the HTTP, but also supports switching through a command line tool. In order to protect the platform from network attack, the switching destination and the control parameter are only allowed to be set through the local command line tool, and the HTTP request password is set through the local command line tool to authenticate the remote HTTP request.
Preferably, there are four switching states for the link from each stub to the backend service program, including the following:
a first switching state: SWITCH _ NONE: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is the same as the back end address in the initial loading;
the second inversion state: SWITCH _ OK: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is different from the back end address in the initial loading;
the third switching state: SWITCH _ CANCELING: the current channel is established, the rear-end connection address is not consistent with the target address, but the specified switching target address is the same as the rear-end address during initial loading;
the fourth switching state: SWITCH _ PENDING: the current channel is established, the rear-end connection address is not consistent with the target address, but the specified switching target address is different from the rear-end address during initial loading;
if the current status is SWITCH _ PENDING or SWITCH _ CANCELING, the gateway will further determine the forward status and then choose to make a connection SWITCH.
Preferably, the following situations are included in the foregoing case that the switch request is to be carried forward:
in the first case: an attempt is being made to resolve the stub device identification in the protocol frame;
in the second situation: on the uplink or downlink of the channel, part of the cache data is still not completely sent to a receiver (a charging pile or a back-end platform service program);
in the third situation: the gateway only processes a part of certain frame data, and the switching can cause the condition of frame fragmentation;
the fourth situation is that: the idle time of the link does not reach the set threshold requirement, or the idle time of the key data frame does not reach the threshold;
in a fifth situation: the peer is not ready, common reasons include: address configuration errors, listening port errors, service not successfully initiated, or firewall restrictions.
Preferably, the connection between the stub and the gateway is always maintained, and the connection is switched only between the gateway and the backend service, so as not to affect various services on the stub and to make the stub unaware.
In the scheme, the method does not inform the stub program that the back-end service is upgraded and does not disconnect the connection between the client and the stub, but only disconnects the connection between the gateway and the back-end service while keeping the connection between the gateway and the stub, and then immediately connects a new back-end direction; in order to avoid half-frame generation during connection switching, the forwarding of the gateway in the scheme is not simply based on a TCP network packet, but is carried out by service frame after unpacking and packaging according to a charging pile communication private protocol; and after the connection of the rear end is switched to the new service direction, in order to enable the pile to be added to the charging platform of the rear end, the gateway simulates the charging pile and sends a registration message frame to the pile service program.
Preferably, in order not to affect the normal communication between the stub and the service program, after receiving the request, the gateway receives the switching request, and does not immediately perform the connection switching, but monitors the message type and the busy degree on the network link, and performs the connection switching operation when the link is selected to be idle.
Preferably, the mode of switching when the link is idle is as follows:
when a bidirectional channel between the gateway monitoring stub and a back-end service program is busy, switching is performed after a link is idle for a period of time t1, and the idle interval time t1 of the network flow can be configured;
the gateway receives the protocol frame, analyzes the command number and analyzes whether each frame is a key frame;
in order to avoid affecting normal charging service, the connection switching needs to be performed after the protocol key frame is idle for a period of time t2, and the key frame idle interval time t2 can be configured.
Preferably, in order to achieve continuous charging service, the gateway tries to connect a new back-end service address, and disconnects and replaces the old connection to the service end after the new direction is successfully connected;
and taking the new switching target direction as a main direction and the previous rear end direction as a standby direction, and connecting the pile into the charging platform through the previous direction when the main direction is not connected abnormally.
In order to avoid forwarding incomplete broken packets, according to a charging pile communication protocol, after receiving TCP original data packets, a gateway normalizes streaming data and sends the data frame by protocol frame, and the method comprises the following steps:
firstly, resolving a protocol identifier in each frame to obtain an initial position of a protocol frame, and then reading out the length of the current protocol frame according to the position of the frame length defined by the protocol;
after analyzing out individual protocol frames, the data is always transmitted downwards frame by frame as soon as possible, if the downstream sending buffer is full, the upstream data is stopped to be received;
when the protocol identification, the frame length abnormality and the CRC error are not found, the gateway still transfers the data downward, but the protocol frame statistical information is not updated any more, and the data transfer and connection switching are not affected.
The invention has the beneficial effects that: the pile service program gray level release method without sensing of the directly-connected charging pile can keep the continuous TCP connection to the pile and the non-sensing effect of the charging pile and a charging user, and has the advantages of upgrading charging service, not interrupting charging service during gray level release and the like; the pile-by-pile, charging station-by-charging station and city-by-city service program gray release can be carried out, and the service is smoothly transited to the newly released service program.
Drawings
Fig. 1 is a schematic diagram of a pile service program gray scale release method without sensing of a direct connection charging pile according to the present invention.
Detailed Description
For the purpose of better understanding the objects, technical solutions and advantages of the present invention, the following detailed description of the present invention with reference to the accompanying drawings and examples should be understood that the specific embodiment described herein is only a preferred embodiment of the present invention, and is only used for explaining the present invention, and not for limiting the scope of the present invention, and all other embodiments obtained by a person of ordinary skill in the art without making creative efforts shall fall within the scope of the present invention.
Example (b): as shown in fig. 1, in order to utilize TCP's own flow control, the gateway establishes a corresponding TCP connection to the back end for each TCP connection from the charging pile, so that the upstream and downstream connections are in one-to-one correspondence. Two fixed size buffers are opened up in the memory for two different flow directions on the channel to be used as TCP data flow transfer stations, and when the buffer is full and the downstream is not ready to consume, the data is not attempted to be received from the upstream.
As long as the connection switching is not artificially initiated when the gray scale is released, as with other internet gateways, the life cycles of the two TCP connections in each pair of channels are consistent, that is, if a certain TCP connection is disconnected, the upstream and downstream TCP connections on the channel will be released.
In order to achieve high availability and efficient forwarding, a C language multi-process mode is adopted for implementation, a Master process is only responsible for scheduling, one or more Worker processes are responsible for data forwarding services, the Worker processes are only single-thread, and all IO are asynchronous IO.
The Master process, the plurality of Worker processes, the HTTP switching request processing process and the command line processing process read and write the same data area in a memory sharing mode, and the memory sharing mode of the file mapping is persistent, so that the switching parameters and the switching request cannot be lost after the processes are restarted, and a file block lock is introduced to prevent the plurality of processes from writing the same block at the same time.
In order to avoid forwarding incomplete broken packets, the gateway normalizes the streaming data after receiving a TCP original data packet according to a charging pile communication protocol, and sends the data frame by protocol frame:
firstly, resolving a protocol identifier in each frame to obtain a protocol frame starting position, then reading out the current protocol frame length according to the position of the frame length defined by a protocol, knowing the frame starting position and the frame length, and determining a frame ending position;
after analyzing out individual protocol frames, the data is always transmitted downwards frame by frame as soon as possible, if the downstream transmission buffer is full, the upstream data is not tried to be received;
when the protocol identification, the frame length abnormality and the CRC error are not found, the gateway still transfers the data downward, but the protocol frame statistical information is not updated any more, and the data transfer and connection switching are not affected.
The pile equipment identification is distributed when the pile equipment identification is added into the charging platform, the pile equipment identification is kept unchanged after distribution, and the pile equipment identification, a charging station where the pile is located and a city where the pile is located are stored in a pile table of a charging service platform database. Therefore, before switching, operation and maintenance personnel can obtain all pile equipment identifications of the charging station and the city by inquiring the pile table, and then send pile identification lists in different spaces to the gateway, so that gray level release can be performed according to different space dimensions.
In order to perform idle time switching, a bidirectional channel between the gateway monitoring stub and the back-end service program is busy, switching is performed after the link is idle for a period of time t1 (for example, 3 seconds), and the network flow idle interval time t1 is configurable.
The gateway receives the protocol frame, analyzes the command number and analyzes whether each frame is a key frame. In order not to affect the normal charging service, the protocol key frame needs to wait for a period of time t2 (for example, 10 seconds) before performing connection switching, and the key frame idle interval time t2 is configurable.
There are four switching states for the link from each stub to the backend service program:
1) SWITCH _ NONE: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is the same as the back end address in the initial loading;
2) SWITCH _ OK: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is different from the back end address in the initial loading;
3) SWITCH _ CANCELING: the current channel is established, the rear-end connection address is not consistent with the target address, but the specified switching target address is the same as the rear-end address during initial loading;
4) SWITCH _ PENDING: the current channel is established and the back end connection address is not consistent with the target address, but the appointed switching target address is different from the back end address in the initial loading.
If the current status is SWITCH _ PENDING or SWITCH _ CANCELING, the gateway will further determine the forward status and then choose to make a connection SWITCH.
The cases where the switch request will be deferred include:
an attempt is being made to resolve the stub device identification in the protocol frame;
on the uplink or downlink of the channel, part of the cache data is still not completely sent to a receiver (a charging pile or a back-end platform service program);
the gateway only processes a part of certain frame data, and the switching can cause the condition of frame fragmentation;
the idle time of the link does not reach the set threshold requirement, or the idle time of the key data frame does not reach the threshold;
the peer is not ready, common reasons include: address configuration errors, listening port errors, service not successfully initiated, or firewall restrictions.
The switching request does not need to be delayed, and before the gateway performs switching, the gateway starts a probe program to check whether the target address is reachable. Although the stub is thousands of piles and the IP addresses are different, the addresses and ports of the back-end service programs are the same, so that a batch of stubs connected to the same destination can share one probe program and share the detection result. In order to avoid unnecessary network storms and avoid being forbidden due to network attacks by mistake, the detection period of the gateway probe program is generally 3-10 seconds, and period parameters can be set.
After the probe program passes the check, the probe program tries to establish a new connection in the process of switching, and then replaces and disconnects the old direction after connecting the new direction. And taking the new switching target direction as a main direction and the previous back end direction as a standby direction, and when the main direction is not connected in an abnormal state, still having an alternative direction to try.
In order to make the connection switching of the back end to make the pile insensitive, the gateway needs to simulate the charging pile to send a registration command to the charging platform after the back end is successfully switched, so that other service nodes in the platform can know that the path from the command to the pile is changed.
When the pile just connects, the gateway stores the registration frame in the memory for standby after receiving and identifying the registration protocol frame from the pile, and then retransmits the registration frame to a new back-end service program after receiving the switching request and switching the back-end connection to the designated target. Since the stub service does not know whether the registration request was sent by the stub or emulated by the gateway after receiving the registration frame, the backend service will send a response frame as specified by the protocol. For the gateway to make the stub imperceptible, it should intercept and discard the response messages corresponding to the registration request it simulates, and cannot let these responses reach the stub program so as not to interfere with the normal operation of the stub program.
The above-mentioned embodiments are preferred embodiments of the method for releasing pile service gray scale without sensing a direct-connection charging pile according to the present invention, and the scope of the present invention is not limited thereto, and all equivalent changes made according to the shape and structure of the present invention are within the scope of the present invention.
Claims (9)
1. Pile service program gray level release method without perception of direct connection charging pile is characterized by comprising the following steps: the method comprises the following steps:
the charging pile firstly directly connects a gateway program through TCP, and then the gateway directly connects a back-end pile service program through TCP, after the gateway receives the pile connection, a protocol frame from the charging pile is analyzed, and the corresponding relation between the pile equipment identification and the TCP connection is maintained in a memory;
the operation and maintenance personnel start a new version of service program, and simultaneously keep the current connection and service unchanged;
the administrator sets the switching parameters and the HTTP switching request authentication password through a local command terminal program of the gateway, and adds the service program address of the new version into the switching target option list;
the operation and maintenance personnel release the rear-end pile service program in gray scale according to different space dimensions;
the gray level release gateway periodically trains switching requests, inquires the corresponding relation between pile equipment identification and TCP connection maintained in a memory before, finds a link to be switched, and connects the specified pile to a new version service program;
after the connection of the rear end is successfully switched, the gateway is disguised as a charging pile, a registration request is sent to a pile service program, the pile is reinjected to the charging platform under the condition that the direct-connected pile is not sensed, and the rear end service node is convenient to send a charging request to the charging pile through a new pile service.
2. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising:
when operation and maintenance personnel release the gray level of the rear-end pile service program, the method comprises the following steps:
determining the space dimension involved in the gray release; the spatial dimension comprises making gray levels according to piles, making gray levels according to charging stations and making gray levels according to cities;
determining a time span; the time span includes: observing how long each batch of piles is switched, and continuing to switch the next batch and estimating how long the whole upgrading is finished;
the operation and maintenance personnel send the pile equipment identification list and the switching target address to a gateway HTTP service through a remote HTTP request;
after receiving the request, the HTTP service program checks the target address and the request key MD5, and after the check is passed, records the request to the local by way of the shared memory.
3. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising:
the link from each stub to the backend service program has four switching states as follows:
a first switching state: SWITCH _ NONE: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is the same as the back end address in the initial loading;
the second inversion state: SWITCH _ OK: in the current channel establishing process or after connecting with the appointed back end target, and the appointed switching target address is different from the back end address in the initial loading;
the third switching state: SWITCH _ CANCELING: the current channel is established, the rear-end connection address is not consistent with the target address, but the specified switching target address is the same as the rear-end address during initial loading;
the fourth switching state: SWITCH _ PENDING: the current channel is established, the rear-end connection address is not consistent with the target address, but the specified switching target address is different from the rear-end address during initial loading;
if the current status is SWITCH _ PENDING or SWITCH _ CANCELING, the gateway will further determine the forward status and then choose to make a connection SWITCH.
4. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 3, characterized in that: the following situations are included in which the switch request is to be deferred:
in the first case: an attempt is being made to resolve the stub device identification in the protocol frame;
in the second situation: on the uplink or downlink of the channel, part of the cache data is still not completely sent to a receiver (a charging pile or a back-end platform service program);
in the third situation: the gateway only processes a part of certain frame data, and the switching can cause the condition of frame fragmentation;
the fourth situation is that: the idle time of the link does not reach the set threshold requirement, or the idle time of the key data frame does not reach the threshold;
in a fifth situation: the peer is not ready, common reasons include: address configuration errors, listening port errors, service not successfully initiated, or firewall restrictions.
5. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising:
in order to not affect various services on the stub and make the stub unaware, the connection between the stub and the gateway is always kept continuous, and the connection switching is only carried out between the gateway and the backend service.
6. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising:
in order to avoid affecting the normal communication between the pile and the service program, after the gateway receives the request and the switching request, the gateway does not immediately perform connection switching, but monitors the message type and the busy degree on the network link and performs connection switching operation when the link is selected to be idle.
7. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 6, characterized by comprising:
the link idle handoff method is as follows:
when a bidirectional channel between the gateway monitoring stub and a back-end service program is busy, switching is performed after a link is idle for a period of time t1, and the idle interval time t1 of the network flow can be configured;
the gateway receives the protocol frame, analyzes the command number and analyzes whether each frame is a key frame;
in order to avoid affecting normal charging service, the connection switching needs to be performed after the protocol key frame is idle for a period of time t2, and the key frame idle interval time t2 can be configured.
8. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising:
in order to realize continuous charging service, the gateway tries to connect a new back-end service address, and the old connection to the service end is disconnected and replaced after the connection in the new direction is successful;
and taking the new switching target direction as a main direction and the previous rear end direction as a standby direction, and connecting the pile into the charging platform through the previous direction when the main direction is not connected abnormally.
9. The pile service program gray scale release method without sensing of the direct-connected charging pile according to claim 1, characterized by comprising: in order to avoid forwarding incomplete broken packets, according to a charging pile communication protocol, after receiving TCP original data packets, a gateway normalizes streaming data and sends the data frame by protocol frame, and the method comprises the following steps:
firstly, resolving a protocol identifier in each frame to obtain an initial position of a protocol frame, and then reading out the length of the current protocol frame according to the position of the frame length defined by the protocol;
after analyzing out individual protocol frames, the data is always transmitted downwards frame by frame as soon as possible, if the downstream sending buffer is full, the upstream data is stopped to be received;
when the protocol identification, the frame length and the CRC error are not found, the gateway still transmits the data downwards.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011256138.XA CN112463204A (en) | 2020-11-11 | 2020-11-11 | Pile service program gray level release method without sensing of direct connection charging pile |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011256138.XA CN112463204A (en) | 2020-11-11 | 2020-11-11 | Pile service program gray level release method without sensing of direct connection charging pile |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112463204A true CN112463204A (en) | 2021-03-09 |
Family
ID=74826499
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011256138.XA Pending CN112463204A (en) | 2020-11-11 | 2020-11-11 | Pile service program gray level release method without sensing of direct connection charging pile |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463204A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114629971A (en) * | 2022-02-25 | 2022-06-14 | 浙江爱充网络科技有限公司 | Pile service program thermal upgrading system and method for electric vehicle charging service platform |
-
2020
- 2020-11-11 CN CN202011256138.XA patent/CN112463204A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114629971A (en) * | 2022-02-25 | 2022-06-14 | 浙江爱充网络科技有限公司 | Pile service program thermal upgrading system and method for electric vehicle charging service platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100945972B1 (en) | Enhanced techniques for using core based nodes for state transfer | |
| JP5364671B2 (en) | Terminal connection status management in network authentication | |
| US8369346B2 (en) | Method and system for restricting a node from communicating with other nodes in a broadcast domain of an IP (internet protocol) network | |
| US20180091581A1 (en) | Method of switching download mode, control method thereof and control system thereof | |
| US20180048633A1 (en) | Perception-free authentication method and system, and control method and system based on the same | |
| AU2004209273A1 (en) | Methods and apparatus for the utilization of core based nodes for state transfer | |
| CN109413649B (en) | Access authentication method and device | |
| CN106255226B (en) | Network connection processing method and device | |
| US20220272607A1 (en) | Network Access Method and Communication Apparatus | |
| CN114629822B (en) | Link detection method, device, electronic equipment and storage medium | |
| CN111327650A (en) | Data transmission method, device, equipment and storage medium | |
| CN109936515B (en) | Access configuration method, information providing method and device | |
| CN110337137B (en) | Data packet filtering method, device and system | |
| CN113794618B (en) | Redundant network communication method and device based on virtual network card and terminal equipment | |
| CN112463204A (en) | Pile service program gray level release method without sensing of direct connection charging pile | |
| WO2017101028A1 (en) | Data transmission method, m2m server, pgw, sgw and serving network node | |
| EP1296528B1 (en) | Verification system and method for packet call processing operation of mobile telecommunication system | |
| CN112787975A (en) | Method, device and system for determining type of access device | |
| US10462848B2 (en) | Non-transitory computer readable recording medium, communication method and communication device | |
| CN111953742B (en) | Page redirection method, terminal equipment, intermediate equipment and server | |
| CN112202780B (en) | Data transmission method, device, equipment and medium based on double sockets | |
| KR102090493B1 (en) | Device and method of HTTP Proxy to reduce the HTTP protocol transmission delay and the HTTP processing load in Mobile Communication Networks | |
| JP6976199B2 (en) | Information processing server and information processing method | |
| CN114270881B (en) | Network access method and device | |
| KR100585724B1 (en) | Method for notifying network state of general packet radio service system |
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 |