CN114415987B - Multi-client coordinated connection printing system for iOS system - Google Patents
Multi-client coordinated connection printing system for iOS system Download PDFInfo
- Publication number
- CN114415987B CN114415987B CN202111456605.8A CN202111456605A CN114415987B CN 114415987 B CN114415987 B CN 114415987B CN 202111456605 A CN202111456605 A CN 202111456605A CN 114415987 B CN114415987 B CN 114415987B
- Authority
- CN
- China
- Prior art keywords
- client
- printer
- printing
- server
- information
- 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
Links
- 230000007246 mechanism Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 5
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 230000008030 elimination Effects 0.000 claims description 3
- 238000003379 elimination reaction Methods 0.000 claims description 3
- 230000009471 action Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000000034 method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
- G06F3/1203—Improving or facilitating administration, e.g. print management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
- G06F3/1237—Print job management
- G06F3/126—Job scheduling, e.g. queuing, determine appropriate device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
- G06F3/1285—Remote printer device, e.g. being remote from client or server
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1296—Printer job scheduling or printer resource handling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Abstract
The invention discloses a multi-client coordinated connection printing system aiming at an iOS system, which comprises a client, a server and a printer, wherein the client is communicated with the printer through Bluetooth, and the client is communicated with the server through Bluetooth, wireless local area network or Internet connection; the invention provides a multi-client coordinated connection printing system aiming at an iOS system, which has low requirements on printers and can rapidly perform multi-client printing tasks.
Description
Technical Field
The invention relates to the technical field of printing, in particular to a multi-client coordinated connection printing system aiming at an iOS system.
Background
The apple iOS App adopts single-to-single connection in printing and then prints. When a plurality of apps initiate printing at the same time, only one App can be connected with the bluetooth printer, and other apps are not successfully connected and the printing is failed. Therefore, for merchants of the apple iOS system, only one device can be defaulted to perform connection printing when corresponding printing is performed, and the efficiency of business activities is greatly influenced. Especially for small micro enterprises, no redundant funds are required for special people to develop and reform, and the production capacity of the small micro enterprises is greatly influenced. When a plurality of apps print, print data is sent to a print program at a printer end through a local area network when the apps print, and the print program performs queuing printing. The method is very dependent on the local area network, and once the corresponding IP changes, the printing program needs to be restarted, the corresponding printing is performed again, and the printing information is repeatedly sent by reconnection. Therefore, a system with low cost, convenient use and printing connection by multiple devices is urgently needed.
Disclosure of Invention
The invention overcomes the defects of the prior art and provides the multi-client coordinated connection printing system aiming at the iOS system, which has low requirements on printers and can rapidly carry out multi-client printing tasks.
The technical scheme of the invention is as follows:
a multi-client coordinated connection printing system for an iOS system comprises a client, a server and a printer, wherein the client is communicated with the printer through Bluetooth, and the client is communicated with the server through Bluetooth, a wireless local area network or Internet connection; the specific printing mode is as follows:
101 Initializing the configuration step: a client is connected with a printer through Bluetooth or a communication line, and printer connection information obtained by connection is transmitted to a server;
102 Primary coordination judgment step: the server coordinates the printing transaction, when the client needs to print, the server judges whether the client is a main client according to a heartbeat mechanism sent by the client, if so, the printing step of the main client is entered, and if not, the printing step of other clients is entered;
103 Main client printing step: the client connected with the printer directly sends printing information with the printer through a Bluetooth protocol, and the printer prints;
104 Other client print step: the server coordinates the printing transaction, and when the client needs to print, the server further judges whether all printers have the main client; if yes, the client side continuously waits for the corresponding printer to be emptied; if not, the server feeds back the printable information to the client initiating printing, the client is connected with the corresponding printer, and the printing information of the printing transaction is sent through the Bluetooth protocol, and the printer prints;
105 Print queue processing step): if yes, continuing to judge that if the printer is idle, transmitting the information to be printed to a main end client corresponding to the idle printer, disconnecting the printer by the main end client, connecting the printer by the client to be printed, and printing; if the printer is not idle, the information to be printed is transmitted to the main end client corresponding to the idle printer, and when the printing of the main end client is finished, the connected printer is disconnected.
Further, the printer connection information includes printer MAC information, time information, status information.
Further, at least one of the number of printers in step 101), all printers are connected to the client, and the printer connection information is transmitted to the server.
Further, if no, step 104), the client initiating printing also sends a corresponding notification to the server, that is, informs the server that the corresponding printer has the master client, and the master client is the client.
Further, the client and the server are connected and communicated through a heartbeat mechanism, and the client sends corresponding connection information with the printer to the server at regular time.
Further, the heartbeat mechanism comprises sending a heartbeat packet and responding the heartbeat packet;
the information in the transmitted heartbeat packet includes {
"id": "client unique identification",
"timestamp": time stamp ",
"printer" is a "printer unique code",
"type": category: 0 represents the secondary end, 1 represents the primary end,
"flag" state: 0 represents busy and 1 represents idle; type=0 ignoring "}
The information in the response heartbeat packet includes {
"id": "client unique identification of the original return request"
"timestamp": "returns the timestamp of the request as is",
"printer" returns the requested printer unique code as is ",
"type": "returns the category of the request as received: 0 represents the secondary end, 1 represents the primary end,
"ack": "response: 0 without a main end, and giving an auxiliary end; 1 represents normal; 2 indicates that the printer is disconnected, given to the master,
task state: 0 indicates no task, 1 indicates a task,
token, the identifier used in the subsequent pulling task, the post-use invalidation.
Further, the printing queue of the server side comprises at least two queues, wherein the first queue is a processing queue of the printing program and the second queue is a queue to be printed; when a client connected with a printer takes a print job from a server, firstly uniformly entering a queue to be printed of the server, judging whether the print job is the same print job before through an algorithm, and thus carrying out duplication elimination; after the task is re-arranged, the task enters a processing queue, the client informs the server after printing is finished, the server removes the task from the processing queue, and otherwise, the task reenters the queue to be printed after overtime.
Compared with the prior art, the invention has the advantages that:
the invention coordinates by the server side, is convenient for printing, and realizes the situations of avoiding repeated printing and missing printing by a double-list mode. The main client and the printer (namely the Bluetooth printer) maintain long connection, so that the action and time of reconnecting Bluetooth when printing each time are saved, and the reconnection operation is only carried out when the main client needs to be replaced; when printing, the corresponding printing information is submitted to a printing queue at the server side, the user operation is not blocked, and the printer takes the next printing task in the queue to be printed when idle.
Drawings
FIG. 1 is a print flow frame diagram of the present invention;
fig. 2 is a frame diagram of a heartbeat mechanism of the present invention.
Detailed Description
Embodiments of the present invention are described in detail below, wherein like or similar reference numerals refer to like or similar elements or elements of similar function throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present invention and not as a limitation of the present invention.
It will be understood by those skilled in the art that all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs unless defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Reference numerals referring to steps in the various embodiments are merely for convenience of description and do not have a substantial sequential relationship. Different steps in each specific embodiment can be combined in different sequences, so that the aim of the invention is fulfilled.
The invention is further described below with reference to the drawings and the detailed description.
Example 1:
as shown in fig. 1 and 2, a printing system with coordinated connection of multiple clients for an iOS system includes a client, a server, and a printer, where the client communicates with the printer through bluetooth connection, and the client communicates with the server through bluetooth, wireless lan, or internet connection. The clients are mobile terminals, tablet computers, PC computers and the like of mobile phones. In this embodiment, the server does not need to be connected to the printer, that is, the server manages only the client portion.
The specific printing mode is as follows:
101 Initializing the configuration step: a client is connected with a printer through Bluetooth or a communication line, and printer connection information obtained by connection is transmitted to a server. The printer connection information includes printer MAC information, time information, status information, and the like.
At least one of the printers, namely two or more printers, needs to be connected with the client, can be connected with one client, can be connected with a plurality of clients, namely all printers need to be connected once, obtains corresponding connection information of all printers, and transmits the corresponding connection information to the server through the client.
In this case, the server does not need to connect to the printer, and all information is transmitted from the client.
102 Primary coordination judgment step: the server coordinates the printing transaction, when the client needs to print, the server judges whether the client is a main client according to a heartbeat mechanism sent by the client, if so, the printing step of the main client is entered, and if not, the printing step of other clients is entered.
103 Main client printing step: the client connected with the printer directly sends printing information with the printer through a Bluetooth protocol, and the printer prints. That is, as long as the client is already connected to the printer, printing can be directly performed without disconnection.
104 Other client print step: the server coordinates the printing transaction, and when the client needs to print, the server further judges whether all printers have the main client. If yes (i.e. all printers are connected with the corresponding main end client end), the client end continuously waits for the corresponding printer to be emptied, and puts the printing transaction into a printing queue; if not (i.e. at least one printer is not connected with the corresponding client), the server feeds back the printable information to the client initiating printing, the client is connected with the corresponding printer, and the printer prints by sending the printing information of the printing transaction through the Bluetooth protocol.
If the client side initiates printing, the client side sends corresponding notification to the server side through a heartbeat mechanism, namely the server side is informed that the corresponding printer has the main client side, and the main client side is the client side.
105 Print queue processing step): if yes, continuing to judge that the printer is idle according to the step 104), transmitting the information to be printed to a main end client corresponding to the idle printer, disconnecting the printer by the main end client, connecting the printer by the client to be printed, and printing. If the printer is not idle, the information to be printed is transmitted to the main end client corresponding to the idle printer, and when the printing of the main end client is finished, the connected printer is disconnected. When the main client prints, the main client continues to operate, does not perform any independent feedback of the received server information, or gives an explicit instruction, and can disconnect and wait for the information. The whole course only needs to send corresponding information by the heartbeat mechanism.
And the client side needing printing judges whether the printing is successful or not by setting corresponding timeout waiting or not, and whether the printing request needs to be initiated again or not.
Preferably, the server may include a print queue, where the print queue includes at least two queues, one is a processing queue of the print program and the other is a queue to be printed. When a client connected with a printer takes a print job from a server, firstly uniformly entering a queue to be printed of the server, judging whether the print job is the same print job before through an algorithm, and thus carrying out duplication elimination; after the task is re-arranged, the task enters a processing queue, after the client-side prints, the server-side can know through a heartbeat mechanism, then the server-side removes the task from the processing queue, and if not, the task reenters the queue to be printed after overtime. The situation of avoiding repeated printing and missing printing is realized.
The main client and the printer (namely the Bluetooth printer) maintain long connection, so that the operation and time of the traditional Bluetooth connection during each printing are saved; when printing, the corresponding printing information is submitted to the printing queue of the server without blocking the user operation, and the printer takes the next printing task in the queue to be printed when idle, thereby greatly improving the printing speed.
The heartbeat mechanism between the client and the server is used for connection communication, and the client sends corresponding connection information between the client and the printer to the server at regular time.
The heartbeat mechanism is an interconnection communication mode of the client and the server, and information transfer interaction is regularly carried out like the heartbeat timing of a person. Specifically, the method comprises the steps of sending a heartbeat packet and responding to the heartbeat packet. The sending heartbeat package and the responding heartbeat package only list the corresponding contained information, and the specific information sending, receiving and analyzing are conventional technical means and are not described in detail.
The specific heartbeat mechanism is described in step 102), and includes first determining whether the client is a main client connected to the printer, if so, continuing to determine whether to go back to the background, if so, disconnecting the main client from bluetooth connection with the printer, and if not, disconnecting the main client from the printer, and no longer providing heartbeat information. And if the user does not need to go back to the background, the heartbeat information is periodically reported. If the client is not the main terminal connection terminal, but printing is needed at the moment, corresponding heartbeat information is directly reported. So as to facilitate the corresponding coordination of the service end. Specifically, the information in the transmitted heartbeat packet includes {
"id": "client unique identification",
"timestamp": time stamp ",
"printer" is a "printer unique code",
"type": category: 0 represents the secondary end, 1 represents the primary end,
"flag" state: 0 represents busy and 1 represents idle; type=0 ignore "}.
The information in the response heartbeat packet includes {
"id": "returns the client unique identification of the request as received",
"timestamp": "returns the timestamp of the request as is",
"printer" returns the requested printer unique code as is ",
"type": "returns the category of the request as received: 0 represents the secondary end, 1 represents the primary end,
"ack": "response: 0 without a main end, and giving an auxiliary end; 1 represents normal; 2 indicates that the printer is disconnected, given to the master,
task state: 0 indicates no task, 1 indicates a task,
token, the identifier used in the subsequent pulling task, the post-use invalidation.
For example, if the master client sends a print request, the specific heartbeat information sent is: {
"id":"4606f9172e464176af855ae5e313cb6e",
"timestamp":"1636185712096",
"printer":"SP-L36-A1B2",
"type":"1",
"flag":"1"}。
If the printer just has a task when the server responds, the returned content is as follows: {
"id":"4606f9172e464176af855ae5e313cb6e",
"timestamp":"1636185712096",
"printer":"L36-A1B2",
"type":"1",
"ack":"1",
"task":"1",
"token":"bf005607-e500-45da-a641-344a6ebf10b4"}。
If the service end responds, the printer does not have a task, and the returned content is as follows: { "id": "4606f9172e464176af855ae5e313cb6e",
"timestamp":"1636185712096",
"printer":"L36-A1B2",
"type":"1",
"ack":"1",
"task":"0"}。
in addition, in response to the disconnection of the printer, the returned contents are as follows: {
"id":"4606f9172e464176af855ae5e313cb6e",
"timestamp":"1636185712096",
"printer":"L36-A1B2",
"type":"1",
"ack":"2",
"task":"0"}。
If other clients send out print requests, the specific heartbeat information sent is: {
"id":"1bf8795db22f4d38a82b8dcaa80b9bcd",
"timestamp":"1636185712096",
"printer":"SP-L36-A1B2",
"type":"0"}。
The server responds that the printer has the client connected, and the returned content is as follows: {
"id":"1bf8795db22f4d38a82b8dcaa80b9bcd",
"timestamp":"1636185712096",
"printer":"SP-L36-A1B2",
"type":"0",
"ack":"1"}。
The server responds that the printer is not connected with the client, and the returned content is as follows: {
"id":"1bf8795db22f4d38a82b8dcaa80b9bcd",
"timestamp":"1636185712096",
"printer":"SP-L36-A1B2",
"type":"0",
"ack":"0",
"task":"1",
"token":"bf005607-e500-45da-a641-344a6ebf10b4"}。
In summary, the server coordinates the scheme, is convenient for printing, and avoids the situations of repeated printing and missing printing in a double-list mode. The main client and the printer (namely the Bluetooth printer) maintain long connection, so that the action and time of reconnecting Bluetooth when printing each time are saved, and the reconnection operation is only carried out when the main client needs to be replaced; when printing, the corresponding printing information is submitted to a printing queue at the server side, the user operation is not blocked, and the printer takes the next printing task in the queue to be printed when idle. .
The foregoing is merely a preferred embodiment of the present invention, and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the concept of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (6)
1. A multi-client coordinated connection printing system for an iOS system, characterized by: the system comprises a client, a server and a printer, wherein the client is communicated with the printer through Bluetooth, and the client is communicated with the server through Bluetooth, wireless local area network or Internet connection; the specific printing mode is as follows:
101 Initializing the configuration step: a client is connected with a printer through Bluetooth or a communication line, and printer connection information obtained by connection is transmitted to a server;
102 Primary coordination judgment step: the server coordinates the printing transaction, when the client needs to print, the server judges whether the client is a main client according to a heartbeat mechanism sent by the client, if so, the printing step of the main client is entered, and if not, the printing step of other clients is entered;
103 Main client printing step: the client connected with the printer directly sends printing information with the printer through a Bluetooth protocol, and the printer prints;
104 Other client print step: the server coordinates the printing transaction, and when the client needs to print, the server further judges whether all printers have the main client; if yes, the client side continuously waits for the corresponding printer to be emptied; if not, the server feeds back the printable information to the client initiating printing, the client is connected with the corresponding printer, and the printing information of the printing transaction is sent through the Bluetooth protocol, and the printer prints;
105 Print queue processing step): if yes, continuing to judge that if the printer is idle, transmitting the information to be printed to a main end client corresponding to the idle printer, disconnecting the printer by the main end client, connecting the printer by the client to be printed, and printing; if the printer is not idle, transmitting information to be printed to a main end client corresponding to the idle printer, and when the printing of the main end client is finished, disconnecting the connected printer;
the heartbeat mechanism comprises a heartbeat packet sending and heartbeat packet responding;
the information in the transmitted heartbeat packet includes {
"id": "client unique identification",
"timestamp": time stamp ",
"printer" is a "printer unique code",
"type": category: 0 represents the secondary end, 1 represents the primary end,
"flag" state: 0 represents busy and 1 represents idle; type=0 ignore "};
the information in the response heartbeat packet includes {
"id": "returns the client unique identification of the request as received",
"timestamp": "returns the timestamp of the request as is",
"printer" returns the requested printer unique code as is ",
"type": "returns the category of the request as received: 0 represents the secondary end, 1 represents the primary end,
"ack": "response: 0 without a main end, and giving an auxiliary end; 1 represents normal; 2 indicates that the printer is disconnected, given to the master,
task state: 0 indicates no task, 1 indicates a task,
token, the identifier used in the subsequent pulling task, the post-use invalidation.
2. The multi-client coordinated connection printing system for an iOS system of claim 1, wherein: the printer connection information includes printer MAC information, time information, status information.
3. The multi-client coordinated connection printing system for an iOS system of claim 1, wherein: at least one of the number of printers in step 101), all printers are connected with the client, and printer connection information is transmitted to the server.
4. The multi-client coordinated connection printing system for an iOS system of claim 1, wherein: if not, step 104) sends out corresponding notification to the server through a heartbeat mechanism when the client initiating printing prints, namely, informs the server that the corresponding printer has the main client, and the main client is the client.
5. The multi-client coordinated connection printing system for an iOS system of claim 1, wherein: the client side and the server side are connected and communicated through a heartbeat mechanism, and the client side sends corresponding connection information with the printer to the server side at regular time.
6. The multi-client coordinated connection printing system for an iOS system of claim 1, wherein: the printing queue of the server comprises at least two queues, wherein one is a processing queue of a printing program and the other is a queue to be printed; when a client connected with a printer takes a print job from a server, firstly uniformly entering a queue to be printed of the server, judging whether the print job is the same print job before through an algorithm, and thus carrying out duplication elimination; after the task is re-arranged, the task enters a processing queue, the client informs the server after printing is finished, the server removes the task from the processing queue, and otherwise, the task reenters the queue to be printed after overtime.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111456605.8A CN114415987B (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing system for iOS system |
| CN202311134662.3A CN117170596A (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing method for iOS system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111456605.8A CN114415987B (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing system for iOS system |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311134662.3A Division CN117170596A (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing method for iOS system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114415987A CN114415987A (en) | 2022-04-29 |
| CN114415987B true CN114415987B (en) | 2023-09-22 |
Family
ID=81265546
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111456605.8A Active CN114415987B (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing system for iOS system |
| CN202311134662.3A Pending CN117170596A (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing method for iOS system |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311134662.3A Pending CN117170596A (en) | 2021-12-02 | 2021-12-02 | Multi-client coordinated connection printing method for iOS system |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114415987B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1575458A (en) * | 2001-08-22 | 2005-02-02 | 皮尔雷斯系统公司 | Output management system and method for enabling access to private network resources |
| CN1864165A (en) * | 2003-12-11 | 2006-11-15 | 微软公司 | System for transferring documents and resources to a printer |
| CN101169708A (en) * | 2006-10-24 | 2008-04-30 | 佳能株式会社 | Information processing device, printing system and information processing method |
| CN102830946A (en) * | 2012-08-06 | 2012-12-19 | 电子科技大学 | Network printing system under private cloud environment for massive seismic data processing |
| CN203025832U (en) * | 2012-10-30 | 2013-06-26 | 浙江金大科技有限公司 | Automatic sheet filling machine system |
| CN205302255U (en) * | 2015-12-24 | 2016-06-08 | 北京三快在线科技有限公司 | Bluetooth printer and bluetooth print system |
| CN106406780A (en) * | 2016-10-15 | 2017-02-15 | 魏歌 | File print management method, equipment, server and system |
| CN108351823A (en) * | 2015-10-22 | 2018-07-31 | Netapp股份有限公司 | It realizes and automatically switches |
| CN109547291A (en) * | 2018-12-06 | 2019-03-29 | 珠海西山居移动游戏科技有限公司 | A kind of method and device of quick positioning high frequency bandwidth consumption |
| CN109565516A (en) * | 2016-04-19 | 2019-04-02 | 工业科技有限公司 | Worker safety's system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080301685A1 (en) * | 2007-05-31 | 2008-12-04 | Novell, Inc. | Identity-aware scheduler service |
| US8341214B2 (en) * | 2009-08-12 | 2012-12-25 | Xerox Corporation | System and method for communicating with a network of printers using a mobile device |
-
2021
- 2021-12-02 CN CN202111456605.8A patent/CN114415987B/en active Active
- 2021-12-02 CN CN202311134662.3A patent/CN117170596A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1575458A (en) * | 2001-08-22 | 2005-02-02 | 皮尔雷斯系统公司 | Output management system and method for enabling access to private network resources |
| CN1864165A (en) * | 2003-12-11 | 2006-11-15 | 微软公司 | System for transferring documents and resources to a printer |
| CN101169708A (en) * | 2006-10-24 | 2008-04-30 | 佳能株式会社 | Information processing device, printing system and information processing method |
| CN102830946A (en) * | 2012-08-06 | 2012-12-19 | 电子科技大学 | Network printing system under private cloud environment for massive seismic data processing |
| CN203025832U (en) * | 2012-10-30 | 2013-06-26 | 浙江金大科技有限公司 | Automatic sheet filling machine system |
| CN108351823A (en) * | 2015-10-22 | 2018-07-31 | Netapp股份有限公司 | It realizes and automatically switches |
| CN205302255U (en) * | 2015-12-24 | 2016-06-08 | 北京三快在线科技有限公司 | Bluetooth printer and bluetooth print system |
| CN109565516A (en) * | 2016-04-19 | 2019-04-02 | 工业科技有限公司 | Worker safety's system |
| CN106406780A (en) * | 2016-10-15 | 2017-02-15 | 魏歌 | File print management method, equipment, server and system |
| CN109547291A (en) * | 2018-12-06 | 2019-03-29 | 珠海西山居移动游戏科技有限公司 | A kind of method and device of quick positioning high frequency bandwidth consumption |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114415987A (en) | 2022-04-29 |
| CN117170596A (en) | 2023-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102176715B (en) | Dynamic timeout method and device in a client-server system | |
| CN101526888B (en) | Printing system, printer devices, a host device | |
| US9049070B2 (en) | Dynamic client/server session recovery in a heterogenous computer network | |
| CN103477600A (en) | Device messaging | |
| CN100521662C (en) | Method and system for realizing instant communication using browsers | |
| JP2000163360A (en) | Method for supporting at least one peripheral device on network | |
| CN106686056A (en) | Android client communication device and method allowing Android client communication device to connect and communicate with server | |
| JP2011232893A (en) | Print data creation server, printing apparatus, and printing system | |
| JP2001156828A (en) | Network peripheral device server, and method for enabling plural clients connected to server network to access plural functions of multifunctional peripheral device | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| US8086669B2 (en) | Multi-protocol print client-server communication | |
| CN103516673A (en) | Network data communication method, network data communication system, network data communication client and network data communication server | |
| US20060093119A1 (en) | Leveraging real-time communications client | |
| CN104391664A (en) | Self-service print system for realizing cross-segment communication between printer and print server | |
| US8121488B2 (en) | Infrared communication apparatus and infrared communication method | |
| CN114415987B (en) | Multi-client coordinated connection printing system for iOS system | |
| CN114415989B (en) | Multi-client connection printing system for iOS system | |
| CN103220343A (en) | Big data multi-system forwarding method | |
| CN103312753A (en) | Communication method and device of Internet of things | |
| JP4445302B2 (en) | Wireless terminal device and service search method | |
| JP2000207298A (en) | File transfer method | |
| JPH0473178B2 (en) | ||
| CN114157624B (en) | Link connection method, device and equipment for instant messaging and storage medium | |
| CN106304413B (en) | A kind of delet method of RX interface session | |
| JP2006019802A (en) | Http communication device |
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 | ||
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: Room 901, Floor 9, Building 1, No. 239, Sansheng Street, Qiaosi Street, Linping District, Hangzhou City, Zhejiang Province, 310000 Patentee after: Hangzhou Yike Information Technology Co.,Ltd. Address before: 311100 room 409, No. 108, Xincheng Road, Nanyuan street, Yuhang District, Hangzhou City, Zhejiang Province Patentee before: Hangzhou Yike Information Technology Co.,Ltd. |