JP2009053869A - Device setup apparatus and control method thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device setup device for preventing a user from being thrown into confusion even when device retrieval based on a second protocol is made valid in starting setup by using a first protocol and a method for controlling the device setup device. <P>SOLUTION: Disclosed is a client setup method in a device having a network interface and a device having a plurality of setup method. Also, this device setup device is provided with a discovery function invalidating means for, when a discovery function via a network interface as a second setup method is valid, invalidating the discovery function in starting a first priority setup; and a discovery function validating means for validating the invalidated discovery function when the first priority setup is completed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

The present invention relates to a device setup apparatus that performs communication processing according to a predetermined protocol and a control method thereof.

  2. Description of the Related Art Conventionally, service providing apparatuses and service providing systems that provide services in response to service requests from client apparatuses on a network are known.

  For example, with the rapid spread of communication over the Internet, network support is being rapidly promoted for products other than conventional personal computers. In other words, network correspondence is rapidly progressing to user interactive devices such as PDAs and mobile phones, image processing devices such as scanners, printers, copying machines, and digital cameras, and home appliances such as televisions, air conditioners, and refrigerators. is there. The PDA is Personal Digital Assistance.

  Along with this, various protocols for providing automatic setup means have been proposed in order to improve convenience and simplicity in using these network-compatible devices. For example, there are network address automatic setting means, network device search and search means, application software for controlling a network-compatible device, utility software, an operating system, and the like.

  Further, Universal Plug and Play (UPnP) and Web Services for Devices (WSD) are the above-mentioned network-compatible devices. Further, BMLinkS promoted by the Japan Business Machine Manufacturers Association (JBMIA), Renedzvous supported by Apple (registered trademark) OS X, and the like are also the above-mentioned network-compatible devices. In addition, there is a unique search method suitable for the client and the device by the device and its vendor, and a unique setup procedure or setup program (see, for example, Patent Document 1).

  By proposing a plurality of such protocols, the convenience and simplicity of the product are improved, but there is a problem in that searching and communication cannot be performed between devices having different supported protocols.

  As described above, various devices are connected to the network and communicate with each other, so that a wide variety of services attractive to the user are born. However, there is a difference in the correspondence of protocols depending on devices, and there is a problem that there are many cases in which it is impossible to search for each other's existence and to communicate with each other.

As means for solving such a problem, in order to be able to communicate widely with various devices on a network, both a client device and a server device have appeared that can support a plurality of protocols.
JP 2003-006133 AA2002156947 (US correspondence)

  In the conventional example, for example, it is assumed that one predetermined server device corresponding to a plurality of protocols A and B exists in the network, and a client device corresponding to the protocols A and B searches the network. . In this case, the server device searched by the protocol A and the same server device searched by the protocol B may be recognized as different devices on the client.

  Further, the client device sets up the device searched by the protocol A, and searches for the same device by the protocol B in the background while the user is performing the setting operation via the user interface. In this case, when the setup process is started, the same device is detected a plurality of times at one time, and there is a new problem that the user may be confused by the duplicate setup process.

  In addition, there is a problem that a desired operation may not be performed unless a search and setup using an optimal protocol are performed for the combination of the corresponding device and the client device. For example, if a PC performs detection by an auto-discovery function such as UPnP of a certain device and the corresponding driver does not exist, the setup process may not be completed in a halfway state, and the operation using UPnP may not be executed. is there.

  Furthermore, when communication by a plurality of setup / detection methods occurs simultaneously, there is a problem that the communication load on the device side increases.

The present invention provides a device setup apparatus and a control method thereof that can prevent a user from being confused even when device search using the second protocol is enabled at the start of setup using the first protocol. For the purpose.

The present invention is a client setup method in a device having a network interface, and a device having a plurality of setup methods. In addition, the present invention has a discovery function invalidating means for invalidating the discovery function if the discovery function via the network interface as the second setup method is valid when starting the first priority setup. . Furthermore, the present invention is an example of a device setup apparatus having discovery function enabling means for enabling the disabled discovery function when the first priority setup is completed.

The present invention temporarily disables device search using the second protocol if device search using the second protocol is enabled at the start of setup using the first protocol. Therefore, according to the present invention, device detection by the second protocol does not occur during setup, and the user can be prevented from being confused.

  The best mode for carrying out the invention is the following embodiment.

  A server device that supports both protocols A and B is connected to the network while a client device that supports protocol A and a client device that supports both protocols A and B are operating. Yes.

  Alternatively, when the operation is started, when the device search processing by the protocol A and the protocol B is started at the same time, the device searched by the protocol A and the device searched by the protocol B are recognized separately. In other words, regarding devices that support both protocols A and B, the same device is processed as if another device is operating on the network. Therefore, a client device that supports both protocols A and B has a problem that it can be a factor causing confusion for a user who uses the protocol device.

  It should be noted that the protocol, version, address, and other numerical values described in the embodiments are not intended to limit the scope of the present invention only to those unless otherwise specified.

  FIG. 1 is a block diagram showing the configuration of a network print system PS1 that is Embodiment 1 of the present invention.

  The client 100 is installed with a general-purpose operating system such as Windows (registered trademark) of Microsoft (registered trademark) or Mac (registered trademark) OS of Apple (registered trademark) connected to the network 110. The client 100 is composed of a PC. The client 100 is installed with a general-purpose application that can be executed on the client 100.

  Windows (registered trademark) OS 1 has a function of realizing discovery, control, status acquisition, and the like of a device on a network by using a UPnP protocol processing unit 102 using XML / SOAP. The XML is an eXtensible Markup Language. The SOAP is a simple object access protocol. The UPnP is a Universal Plug and Play.

  However, Print Driver corresponding to UPnP print service is not provided as a standard. Therefore, a print job using UPnP Protocol 2 is possible only when a Print Driver corresponding to the UPnP print service is provided to a UPnP protocol compatible printer searched and discovered by UPnP Protocol 2.

  On the other hand, it is possible to realize discovery, control, status acquisition, etc. of devices on a network by using a software program provided with a server device and using a vendor-specific protocol and a driver corresponding to the protocol.

  For example, a document created by the word processor 105, which is application software, issues a print job by using the provided Print Driver for a printer compatible with the present protocol searched and found by this protocol.

  On the other hand, in the network compatible device according to the first embodiment, the network printer 200 includes a protocol stack 201 as a communication function, and includes a UPnP protocol processing unit 202 on the protocol stack. The network printer 200 is a network compatible printer. A print protocol processing unit 203 is mounted on the protocol stack, and has a print service function that analyzes a print request issued from a client and sends the print request to the printer controller 204.

  Furthermore, a predetermined vendor-specific protocol processing unit 205 is provided on the protocol stack 201, and a print protocol processing unit 203 is mounted on the protocol stack 201. It has a function of analyzing a print request issued from a client via a specific protocol and sending the print request to the printer controller 204.

  Since the printer includes a UPnP protocol processing unit, it can respond to a device search request using the UPnP protocol issued from the client 100. However, since a Print Driver corresponding to a UPnP print service operating on the OS of the client 100 is not provided, a print operation via the UPnP protocol cannot be performed. On the other hand, it also has a vendor-specific protocol processing unit, and software drivers that execute the corresponding protocol on the OS of the client 100 can realize discovery, control, and status acquisition of devices on the network. is there. For example, a document created by the word processor 105, which is application software, uses a print driver that is also provided for a printer compatible with the present protocol searched and found by this protocol. As a result, a print job can be issued.

  In another network-compatible device according to the first embodiment, the DTV 400 (DTV 400 is a digital television and a network-compatible digital television) includes a TCP / UDP protocol stack 401 as a communication function. Then, HTTP is provided on the protocol stack, and HTTP request analysis and response processing are performed.

  Similar to the network printer 200, the UPnP protocol processing unit 402 is provided on the protocol stack, and the client print protocol processing unit 403 is mounted on the TCP / UDP protocol stack 401. It has a function of sending to a printer in which a print request issued from the print application 404 of the digital television application is detected according to the UPnP protocol.

  Next, UPnP used as one of the communication protocols in the first embodiment will be described.

<< Overview of Universal Plug and Play (UPnP) >>
The UPnP network is a peer-to-peer network that does not require complicated settings such as setting an IP address and installing a device driver necessary for connecting a conventional network device. Here, an outline of the basic configuration, protocol, and execution steps of the UPnP network will be described. For details, refer to the document of each standard.

  Devices, services, and control points are defined as the basic configuration of the UPnP network. The device is a device that supports UPnP, and is a printer, a Broadband router (Internet gateway device), or the like. A service is a minimum unit that represents a function provided by a device. For example, if the device is a Printer device defined by UPnP Forum, a PrintBasic service is provided. The control point controls and uses a service that the device has, and corresponds to a PC, STB, or the like.

  The device has at least one service. The device can also have an embedded device inside. The base device is called the root device.

  FIG. U7 is a diagram illustrating a basic configuration of a UPnP network.

  A control point 710 and a root device 720 are connected to the network 700. The root device 720 has a service 721 and an embedded device 722, and the embedded device 722 has a service 723.

  The UPnP network is based on TCP / IP and distributes messages using Hypertext Transfer Protocol (HTTP) and Extensible Makeup Language (XML). The UPnP device can use TCP / IP stack protocols such as TCP, UDP, IGMP, and ARP, and can use TCP / IP services such as DHCP and DNS. By adopting TCP / IP, UPnP is independent of the physical media of the network.

  FIG. U8 shows the UPnP protocol stack.

  HTTPPU and HTTPMU are extensions of HTTP to UDP, and the basic message format used in the protocol is HTTP. HTTPPU uses unicast, and HTTPMU uses multicast communication.

  The Simple Service Discovery Protocol (SSDP) defines a method for detecting network services. The SSDP is created based on HTTPPU and HTTPMU and defines how the control point detects the service of interest and how the device announces that service.

  The Generic Event Notification Architecture (GENA) is a function that transmits and receives notifications using HTTP and HTTPMU. Define the concept of notification subscribers and publishers to enable events.

  Simple Object Access Protocol (SOAP) defines the specifications of XML and HTTP for executing Remote Procedure Call (RPC). The control point uses SOAP to control the device.

  At the top of the protocol stack is a message with vendor specific information. Next is a message supplemented with information defined in the UPnP Forum Working Committee (WC). The upper message is distributed over the IP in the HTTP message format in accordance with UPnP specific protocols such as SSDP and GENA.

  Next, UPnP execution steps will be described.

  UPnP is executed in six steps: addressing, discovery, description, control, eventing, and presentation. Hereinafter, each step will be described.

<Addressing>
In this step, an IP address is assigned so as to enable TCP / IP communication based on UPnP. A UPnP device must implement at least a Dynamic Host Configuration Protocol (DHCP) client. When the device first connects to the network, it searches for a DHCP server and obtains an address.

  If no DHCP server is found, an address must be obtained using Auto-IP. Auto-IP randomly generates an address within the range of a link-local address (169.254 / 16 in IP Version 4) defined by IANA. Then, using the Address Resolution Protocol (ARP), it is checked whether the generated address is already used, and the use of the address is announced. When the device acquires an IP address with Auto-IP, the device periodically searches for a DHCP server, and if found, acquires the address from the DHCP server.

<Discovery>
When the IP address assignment is completed, discovery is performed. When a device is added to the network, the device announces the services that the device has using the UPnP discovery protocol. Similarly, when a control point is added to the network, it searches for devices.

  FIG. U9A is a diagram illustrating a state in which a device announces using the UPnP discovery protocol.

  The device sends and announces a UDP multicast packet to the multicast address assigned by IANA for SSDP: port 239.255.255.250:1900. In FIG. U9A, the network printer 200, which is a UPnP device, notifies, and the DTV 400, STB 500, and client 100, which are control points, receive this.

  FIG. U9B is a diagram illustrating an example of an announcement packet indicating that a device has been added to the network and can be used.

  The announcement packet is transmitted via HTTPMU. A GENA NOTIFY method is used for the request, and the NTS header must be ssdp: alive. In addition, the header includes a notification valid time, a device description URL, a notification type, a service unique name, and the like, and includes only a blank line without a message body.

  FIG. U9C is a diagram showing an announcement packet indicating that a device is being deleted from the network and cannot be used.

  A GENA NOTIFY method is used for the request, and the NTS header must be ssdp: bybye.

  FIG. U10A is a diagram illustrating a state in which a control point searches using a UPnP discovery protocol and a device responds.

  The control point sends a UDP multicast packet to the multicast address assigned by SSD for the SSD: port 239.255.255.250:1900, and the device responds with UDP unicast. In FIG. U10A, the DTV 400, which is a control point, searches for a device, and the network printer 200 responds.

  FIG. U10B is a diagram illustrating an example of a search request packet.

  The search request is transmitted via HTTPMU. The request uses the M-SEARCH method, and the MAN header must be “ssdp: discover”. The ST header is a search target, has no message body, and is only a blank line.

  FIG. U10C is a diagram illustrating an example of a search response packet.

  The search response is transmitted via HTTPU. The response includes a notification valid time, a device description URL, a search target, a service unique name of the notification, and the like.

<Description>
The description is performed in the second step of the UPnP network after the control point finds the device by discovery. After this step, other steps, controls, eventing and presentation are possible.

  FIG. U11A is a diagram illustrating a description step in which the control point transmits a description request and the device responds to the description.

  The control point 710 acquires a device description URL of the root device 720 by discovery, and then transmits a description request to the device.

  FIG. U11B is a diagram illustrating an example of a description request packet.

  The description request is transmitted using the HTTP GET method.

  FIG. U11C is a diagram illustrating an example of a description response.

  The body of the HTTP message is a description described in XML. In UPnP, there are two types of descriptions: a device description and a service description.

  The device description includes a list of services that the device has, and includes a service description URL, a control URL, an eventing URL, and the like of each service. If there is a device embedded in the device, a device list is also included.

  The service description includes an action list for controlling the service and a service status table indicating the status of the service. The action list describes the name of each action, its arguments, related state variables, and input / output directions. The service state table describes the name, type, range, and event characteristics of each state variable.

  After acquiring the device description, the control point 710 acquires each service description by performing an HTTP GET to each service description URL included therein. After obtaining the service description, the control point 710 can control each service of the root device 720 and display the status.

<Control>
In the control step, the control point makes a request to the service of the device and controls the device.

  FIG. U12A is a diagram illustrating a state in which the control point controls the device.

  The control point 710 can control the root device 720 after acquiring the device description and the service description of the root device 720 in the description step. What a control point can do is to execute an action (send an action request) and acquire a result (receive an action response). In addition, what the control point can do is to execute a query of a state variable (send a query request) and acquire a value (receive a query response).

  SOAP is used for UPnP control. SOAP defines the use of XML / HTML for the implementation of remote procedure calls. The control message is formatted based on the SOAP header and the body element, and distributed via HTTP.

  The control point 710 transmits a request to the control URL acquired from the device description of the root device 720 using the HTTP POST or M-POST method.

  FIG. U12B is a diagram illustrating an example of an action request.

  In this example, the POST method is used for the request line. CONTENT-TYPE must be text / xml and charset = “utf-8”. The action name is included in SOAPACTION. The message body is described in XML and includes an Envelope element defined by SOAP, and its subelement Body includes subelements such as an action and an argument.

  FIG. U12C is a diagram illustrating an example of an action response.

  This example is an example of a success response. The response line includes an HTTP success code. The message body is described in XML and includes an Envelope element defined by SOAP, and its sub-element Body includes an action response sub-element. If the action response has an output argument, the action response includes the argument as a sub-element.

<Eventing>
In the eventing step, the control point registers a status change notification request in the device and receives a notification from the device. The service that is the source of the event is called a publisher, and the control point that is the target of the event is called a subscriber. When a subscriber requests notification of an event, it is called a subscription.

  FIG. U13A is a diagram illustrating a state of eventing.

  The control point 710 (subscriber) transmits an eventing request by an HTTP request to the eventing URL of the device description of the root device 720 acquired by the description. Also, an eventing response is received by an HTTP response. There are three types of requests: subscription for registering an event notification request, renewal for requesting renewal of registration before the registration expires, and cancellation for requesting cancellation of registration before the registration expires.

  FIG. U13B is a diagram illustrating an example of a subscription request.

  For the request line, the SUBSCRIBE method defined in GENA is used. The header includes an event message transmission destination URL, a notification type UPnP: event, and the like. There is no message body, only a blank line.

  FIG. U13C is a diagram illustrating an example of a subscription response.

  This example is an example of a success response. The response line includes an HTTP success code, and the header includes an ID for identifying a subscription, a subscription valid time, and the like. The subscription update request is made by setting the subscription ID in the header using the SUBSCRIBE method. The subscription cancellation request is made by setting the subscription ID in the header using the UNSUBSCRIPT method.

  The service 721 (publisher) of the root device 720 transmits the event message by an HTTP request to the destination URL of the event message included in the subscription request. That is, the event message is transmitted to the control point 710 and the control point 1300 which are subscribers. The subscriber who has received the message returns an HTTP response to the publisher.

  FIG. U13D is a diagram illustrating an example of an event message.

  The NOTIFY method is used for the request line. The header includes CONTENT-TYPE: text / xml, NT: upnp: event, NTS: upnp: propagation, SID: uid: <subscription ID>, and the like. The message body is described in XML and includes as many property subelements as necessary in a propertyset element having a state variable as a subelement.

<Presentation>
In the presentation step, the web service of the device is displayed on the browser. Thus, the device can be controlled from the Web page, and the service status can be displayed.

  FIG. U14 is a diagram illustrating how the browser accesses the presentation page of the device.

  Upon obtaining the presentation URL included in the device description of the root device 720, the control point 710 can display the presentation page of the root device 720 using the browser 1400. The browser 1400 obtains a presentation page by making an HTTP GET to the presentation URL of the root device 720. The root device 720 can provide service control means and status display means to the control point 710 via the presentation page.

<< Universal Plug and Play (UPnP) Outline End >>
Next, a setup method for detecting a UPnP protocol device in the client 100 and the DTV 400 will be described.

  FIG. 2 is a flowchart showing a setup method when the UPnP protocol device is detected in the client 100 and the DTV 400.

  When the client 100 and the DTV 400 that support the UPnP protocol join the network and start the service, they search for a UPnP-compatible printer that exists on the network (step 2-2).

  Next, STEP2-2 will be described in detail.

  FIG. 3 is a flowchart illustrating a UPnP-compatible printer device search process in the client according to the first exemplary embodiment.

  FIG. 4 is a diagram illustrating a format of an M-SEARCH discovery packet defined by Universal Plug and Play Device Architecture v1 in the first embodiment.

  As shown in step 3-1, for the multicast address 239.255.255.250 and the port number 1900, a packet defined in Universal Plug and Play Device Architecture 1.0 is issued. This packet is an HTTP M-SEARCH packet in the format shown in FIG.

  The UPnP protocol processing units 102 and 402 of the client 100 and the DTV 400 analyze response packets for all responses if there are responses within a predetermined time after issuing the M-SEARCH packet. Execute. In the first embodiment, the predetermined time is 30 seconds.

  FIG. 5 is a diagram illustrating a format of a response packet from a printer as an example of a network device.

  The UPnP protocol processing units 102 and 402 of the client 100 and DTV 400 record the URL of the network printer described in the packet. This process is performed on all received response packets, and the URLs of all UPnP compatible printers existing on the network are recorded (step 3-2).

  When the above process is completed, or when there is no response in the step (step 3-3), the UPnP protocol processing units 102 and 402 of the client 100 and DTV 400 end the UPnP search processing, and proceed to step 2-3. Get information. Thereafter, setup processing is executed on each client so that the device can be used via UPnP.

  On the other hand, the network printer 200 that supports the UPnP protocol joins the network and starts the service. At this time, the presence of the device is multicast to the multicast address 239.255.255.250 and the port number 1900 using SSDP and HTTMU on the same network. That is, the HTTP NOTIFY in the format shown in FIG. 4 defined in Universal Plug and Play Device Architecture 1.0 is multicast on the network. Then, it advertises that this printer is executing a service on the network.

  The advertisement message describes a URL that can be obtained by a Device Description Document that can obtain information (Device Description) about the device. Upon receiving this multicast message, the client 100 and the DTV 400 analyze the packet and record the URL of the network printer described in the packet.

  When the above process is completed, the UPnP protocol processing units 102 and 402 of the client 100 and the DTV 400 acquire printer information for the newly detected printer. Then, after it is determined that the service can be used from the client, a setup process is executed on each client so that the device can be used via UPnP.

  Next, a setup process for enabling the device to be used via UPnP on the client will be described.

  A client that detects a UPnP device, acquires information thereof, and detects that the printer is compatible with a print service performs setup on the client side in the following manner.

  Similar to the network printer 200, the DTV 400 includes a TCP / UDP protocol stack 401 and a UPnP protocol processing unit 402 on the protocol stack. In addition, a print protocol processing unit 403 compliant with the UPnP print service for clients is already installed. Therefore, when the digital television recognizes the printer, printing between the DTV 400 and the network printer 200 using the UPnP print service can be executed without performing additional setup processing by the user.

  Since the OS of the client 100 also includes a UPnP protocol processing unit, a device search using the UPnP protocol and a multicast of HTTP NOTIFY (advertisement) from the device are detected, and the UPnP device is recognized. When device information is acquired and the printer is recognized as a printer that supports the UPnP print service, a plug-and-play process for incorporating a printer driver compliant with the corresponding print service protocol into the system is executed.

  In this process, if there is no optimal device driver provided by the OS, the device driver attached to the medium such as a floppy (registered trademark) disk or CD-ROM is purchased when the device is purchased. Need to be incorporated into In order to incorporate the device driver, processing of a client system that prompts the user to set the media containing the device driver in the drive is executed.

  In the network printer 200 according to the first embodiment, the UPnP protocol is implemented mainly with the intention of performing a communication with a digital television and a printing process. Therefore, Print Driver corresponding to the UPnP print service operating on the OS of the client 100 is not provided. Print processing by communication based on a predetermined vendor-specific protocol is intended between the general-purpose OS in the client 100 and the network printer 200. A device driver for processing the protocol and a device setup method using the protocol are prepared.

  Next, a method for the client 100 to set up the network printer 200 based on this vendor-specific protocol will be described.

  The network printer 200 according to the first embodiment is a printer having both a USB and a LAN port. The network setup is continuously performed after the installation of the printer driver is completed in the execution sequence of the setup program using the USB by executing the setup program provided by the vendor.

  FIG. 6 is a diagram showing transition of a dialog indicating setup on a client computer of a network printer using USB.

  FIG. 7 is a flowchart showing the setup on the client computer of the network printer using USB.

  After the network device driver is copied to the system, when the printer and client are connected with a USB cable and the printer is turned on, the printer is recognized via USB and the printer driver is installed.

  Thereafter, in the dialog box (6-1) for performing network setup, when the user selects to perform setup (6-3), the network setup is started. After the setup process is started, a message (6-4) for prompting the user to connect the network cable to the main body and connect to the network is displayed with the USB cable connected.

  When connected to the printer network by a user operation, the setup program searches for the printer via the LAN. This detection is performed by issuing a printer search command multicast defined by a vendor-specific protocol. A device that can understand the command (in this case, a specific printer or printer adapter) returns predetermined information about the command to the host that has transmitted the command. This information includes the name, ID, address, etc. of the printer, and the printer to be connected can be specified based on the information.

  Based on all received response packets, the client recognizes that the printer is compatible with the same protocol, and selects the same printer as the printer connected via USB from the discovered printers. In this case, for a printer connected via USB, the printer name, ID, address, etc. are acquired via USB, and a matching printer is selected from the detection results.

  A communication port is created for the selected printer, a network printer icon is created according to the contents, and the setup is completed (6-8). The printer icon is used for confirming, distinguishing, or identifying a printer that can be prepared by a user, and is selected when printing from an application.

  In this system, the characteristic operation of the first embodiment will be described together with the control flow of this system.

  The UPnP protocol, the DTV 400 that supports the print service, the UPnP protocol, and the vendor-specific protocol are operating on the network. The client computer that supports the print service using the protocol is operating on the network. In order for the user to print from the client computer, the network printer 200 is newly connected to the network and set up on the client computer.

  The setup of the printer is started by executing a setup program included in the CD-ROM attached when purchasing the printer on the client computer. In the setup, first, the setup process is started without connecting the interface cable to the printer and without turning on the printer. When the user proceeds with the process according to the message displayed by the program, the copying of the printer driver software to the system ends.

  Thereafter, the printer and the client are connected with the USB cable, a message prompting the user to turn on the printer is displayed, and the USB connection and power on are performed by the user operation. As a result, the printer is recognized by the plug and play function of the OS via the USB, and the printer driver is installed.

  FIG. 8 is a transition diagram of a dialog showing the setup on the client computer using the USB of the network printer of the first embodiment.

  FIG. 9 is a flowchart illustrating the setup on the client computer using the USB of the network printer according to the first embodiment.

  When the installation of the printer driver is completed, a dialog box asking whether to perform network setup is displayed (8-1). When the user selects to perform setup (8-3), network setup is started. When the setup process is started, a message is displayed to confirm that the printer is turned on with the USB cable connected and the network cable is not connected (8-4). ).

  Hereinafter, characteristic parts will be described.

  This printer has a function for enabling or disabling the UPnP protocol function, and is controlled according to a command issued from the client. When the user confirms the message and proceeds with the setup program, the setup program uses the UPnP invalidation function and issues a command for invalidating the UPnP function via the USB.

  With this control, when the UPnP function of the printer is invalidated and connected to the network, it does not respond to device search using the UPnP protocol, nor does it issue a multicast of HTTP NOTIFY (advertisement) from the printer. That is, device recognition as a UPnP device is not performed.

  FIG. 10a is a diagram showing a command for invalidating the UPnP function issued via USB.

  Using a setting command defined for performing network settings of a predefined printer, a parameter <upnable> for specifying activation / invalidation of the UPnP function defined in advance is also set as a parameter to be set. specify.

  By setting “0” as the value of this parameter, setting is made to disable the UPnP function of the printer. If the execution of this setting command is successfully processed, the normal execution status is returned to the response command.

  After performing this process, the setup program connects the network cable to the printer body and displays a message prompting the user to connect the printer to the network (8-8). The user connects to the printer network. The setup program searches for printers via the LAN. This detection is performed by issuing a printer search command multicast defined by a vendor-specific protocol. At this time, the UPnP function of the printer is disabled. Therefore, no UPnP device is added to the network, device detection by the UPnP function of the client OS does not work, and a screen that is not related to the setup program such as the UPnP installation screen is not displayed. Also, in the DTV 400, since the UPnP printer is not detected, communication from the digital television to the printer is not performed.

  A printer search defined by a vendor-specific protocol by the setup program is performed, and a printer compatible with the protocol responds. This includes a response from the printer connected via USB. The name, ID, address, and the like of the printer are acquired via USB, and a printer that matches the information is selected as a setup target printer.

  A communication port is created for this printer and registered on the client OS as a network printer. At the same time, it is displayed as a printer icon on the user interface, and is used to confirm, distinguish or identify a printer that can be prepared by the user. When printing from the application, this icon can be selected, and the network setup is completed.

  At the end of the setup process, the program uses the UPnP activation function and issues a command to re-enable the UPnP function via USB. This control enables the UPnP function of the printer and reacts to device search using the UPnP protocol.

  FIG. 10b is a diagram showing a command for enabling the UPnP function issued via USB.

  Specifying <uppenable> as a parameter in a setting command defined to perform network setting of the printer is the same process as when the function is disabled. By setting “1” as a parameter value, a setting for enabling the UPnP function of the printer is performed. If the execution of this setting command is successfully processed, the normal execution status is returned to the response command.

  When UPnP is enabled, the printer issues a multicast of HTTP NOTIFY (advertisement) and is recognized as a UPnP device. At this point, since the network setup is completed in the client, there is no great confusion for the user.

  As described above, while the client device performs network setup using a specific protocol and the user is performing the setting operation via the user interface, the same device is searched by the UPnP protocol in the background. Is done. If the setup process is executed, such as displaying a message or dialog box associated with the setup process, the user may be confused. However, if the search using the UPnP protocol is enabled at the start of setup using the unique protocol, the detection by UPnP does not occur during setup by temporarily disabling the search, thus preventing the confusion. be able to.

  Note that the means for issuing the invalidation command for the UPnP protocol function of the printer in the first embodiment need not be limited to the described means. For example, in the network setup of this printer, when executing a setup process that does not require a USB connection, the setup program turns on the power of the target printer. Then, a command for invalidating the UPnP function may be issued via the network at an early stage after being connected to the network using a vendor-specific protocol.

In this case, since it is assumed that the corresponding printer is not specified on the network, this command is issued by broadcast communication. As a result, the UPnP function can be disabled in all printers connected to the network and capable of recognizing this command. Similarly, during the setup process in the client OS, the device search and setup process via the UPnP protocol are not performed simultaneously. The user can process the setup program without being confused.

  Next, a second embodiment of the present invention will be described.

  The UPnP protocol, the DTV 400 that supports the print service, the UPnP protocol, and the vendor-specific protocol are operating on the network. The client computer that supports the print service using the protocol is operating on the network. In order to perform printing from the client computer, the user newly connects the network printer 200 to the network and performs setup on the client computer.

  The setup of a new printer is started by executing a setup program included in a CD-ROM attached at the time of purchase of the printer on the client computer. When the user proceeds with the process according to the message displayed by the program, the copying of the printer driver software to the system ends.

  FIG. 11 is a transition diagram of a dialog indicating setup on the client computer of the network printer in the second embodiment of the present invention.

  FIG. 12 is a flowchart showing the setup on the client computer of the network printer in the second embodiment of the present invention.

  After copying is complete, a dialog box appears asking if you want to continue with network setup. When the user selects to perform setup, network setup is started. When the setup process is started, a message prompting to turn on the printer and connect to the network by connecting the network cable is displayed (11-5, S1201). In accordance with the instruction, the user turns on the printer and connects the printer to the network.

  FIG. 13 is a flowchart showing the state transition on the printer of the network printer in the second embodiment of the present invention.

  In this printer, the UPnP protocol function is disabled in a new state that has never been set up or in a state in which the settings have been initialized (S1302). As a result, when connected to the network, it does not respond to device search using the UPnP protocol, nor does it issue an HTTP NOTIFY (advertisement) multicast from the printer. That is, device recognition as a UPnP device is not performed. The UPnP function is activated (S1304) when the printer recognizes that the network setup using the vendor-specific protocol is performed and all the setups using the vendor-specific protocol are completed.

  The setup program connects a network cable to the printer body and displays a message prompting the user to connect the printer to the network. The printer is connected to the network by user operation. The setup program searches for a printer via the LAN (S1203). This detection is performed by issuing a printer search command multicast defined by a vendor-specific protocol. In this case, since the UPnP function of the printer is disabled (S1302), no UPnP device is added on the network. Further, the device detection by the UPnP function of the client OS does not work, and a screen not related to the setup program such as the UPnP installation screen is not displayed. Further, since the DTV 400 does not detect a UPnP printer, communication from the digital television to the printer is not performed.

  The setup program performs a printer search defined by a vendor-specific protocol, and a printer corresponding to the protocol responds. The search command is transmitted to all devices on the network by broadcasting. Then, a search command is received, and predetermined information for the command is returned to the host to which the device (in this case, a specific printer or printer adapter) that can understand the command has transmitted the command (1204).

  This information includes the name, ID, address, and the like of the printer, and the printer to be connected can be specified based on the information. A list of detected printers is displayed (11-9), and the printer indicated by the highlight can be selected. When the user selects a printer (1205) and proceeds with the program, a communication port is created for the printer and registered on the client OS as a network printer. At the same time, it is displayed as a printer icon on the user interface, and is used by the user to confirm, distinguish, or identify a printer that can be currently prepared. Can be selected. Then, the network setup is completed (11-14).

  At the end of the setup process, the program causes the user to select whether or not to execute the same setup program in order to set up the printer in another client OS. When it is selected not to perform network setup by the setup program, the program issues a predetermined setup completion notification command to the printer (S1207). By issuing this command, the printer determines that the setup process using the unique protocol has been completed (S1303), and the UPnP function is validated. This reacts to device search using the UPnP protocol. Further, the printer issues a multicast of HTTP NOTIFY (advertisement), and is recognized as a UPnP device. At this point, the network setup is complete on the client, so there is no significant confusion for the user.

  In this way, the client device performs network setup using a specific protocol and searches for the same device in the background by the UPnP protocol while the user is performing the setting operation via the user interface. Is done. When the setup process is executed, such as a message or dialog box associated with the setup process is displayed, the user may be confused. However, if the UPnP protocol search is enabled at the start of setup using the specific protocol, the UPnP detection will not occur during setup by temporarily disabling the search, thus preventing the above confusion. Can do.

  The above embodiment is a setup method in a client device of a server device that is connected to a network and supports a plurality of protocols, and is a client device that includes a plurality of protocols and a setup method corresponding to the protocols. In addition, when setting up a server device corresponding to the same plurality of protocols, when the setup of the server device searched via the first priority protocol is started, the search by the other protocol is effective in the server device. For example: In other words, the above embodiment is applied to a device and the device that validate the invalidated protocol when the setup process is completed after the search by other valid protocols is temporarily invalidated. Method, control program.

  The above-described embodiment is a setup method in a client device of a server device that is connected to a network and supports a plurality of protocols, and is a client device that includes a plurality of protocols and a setup method corresponding to the protocols. When setting up a server device corresponding to the same plurality of protocols, if the device has not completed the first priority setup in the initial state of the device, the protocol not used for the first priority setup is invalidated. . The embodiment described above is a device setup method for enabling the invalidated protocol when the setup process is completed.

  In other words, the above embodiment is a client setup method in a device having a network interface, and is a device having a plurality of setup methods. In the above embodiment, when the first priority setup is started, if the discovery function via the network interface as the second setup method is valid, the discovery function invalidating means for invalidating the discovery function is provided. Have. Further, the above embodiment is an example of a device setup apparatus having a discovery function enabling means for enabling the disabled discovery function when the first priority setup is completed.

  In the above-described embodiment, in the initial state, if the device has not completed the first-priority setup, the discovery function is invalidated to invalidate the discovery function via the network interface that is not used for the first-priority setup. Have means. The above-described embodiment is an example of a device setup apparatus having a discovery function enabling unit that enables the discovery function when the setup process is completed.

  Further, the above embodiment is a device having the interface 2 which is an interface other than the network interface, and is set up by the first priority device setup method. When starting this setup, at the beginning of the setup process, it communicates with the setup target device via the interface 2 and transmits a command. This is an example of a device setup device that validates the discovery function by invalidating the discovery function via the network interface and transmitting the command again when the setup process is completed.

  Moreover, the said Example can be grasped | ascertained as invention of a method. In other words, the above embodiment is a client setup method in a device having a network interface, and is a method for controlling a device having a plurality of setup methods. Further, when the first priority setup is started, if the discovery function via the network interface, which is the second setup method, is valid, the discovery function invalidation step of invalidating the discovery function and storing it in the storage device is performed. Have. Furthermore, it is an example of a device setup apparatus control method including a discovery function enabling step of enabling the disabled discovery function when the first priority setup is completed.

  In the above-described embodiment, in the initial state, if the device has not completed the first priority setup, the discovery function via the network interface that is not used for the first priority setup is invalidated and stored in the storage device. It has an invalidation process. Moreover, the said Example is an example of the control method of the device setup apparatus which has the discovery function validation process which validates the said discovery function when the said setup process is complete | finished.

Further, the above embodiment is a device having the interface 2 which is an interface other than the network interface, and starts the setup by the first priority device setup method. At this time, at the beginning of the setup process, it communicates with the device to be set up via the interface 2 and transmits a command. Thus, the discovery function via the network interface is invalidated, stored in the storage device, and the command is transmitted again when the setup process is completed, thereby validating the discovery function.

1 is a block diagram illustrating a configuration of a network print system PS1 that is Embodiment 1 of the present invention. FIG. It is a figure which shows the basic composition of UPnP. It is a figure which shows the protocol stack of UPnP. It is a figure which shows a mode that a UPnP device performs notification. It is a figure which shows the example of the notification packet which shows that a device can be utilized. It is a figure which shows the example of the notification packet which shows that a device becomes unavailable. It is a figure which shows a mode that a control point searches a device. It is a figure which shows the example of a search request packet. It is a figure which shows the example of a search response packet. It is a figure which shows the mode of a description step. It is a figure which shows the example of a description request packet. It is a figure which shows the example of a description response packet. It is a figure which shows a mode that a control point controls a device. It is a figure which shows the example of an action request. It is a figure which shows the example of an action response. It is a figure which shows the mode of eventing. It is a figure which shows the example of a subscription request. It is a figure which shows the example of a subscription response. It is a figure which shows the example of an event message. It is a figure which shows a mode that a browser accesses the presentation page of a device. 4 is a flowchart illustrating a setup method when a UPnP protocol device is detected in the client 100 and the DTV 400. 6 is a flowchart illustrating a UPnP-compatible printer device search process in a client according to the first exemplary embodiment. In Example 1, it is a figure which shows the format of the M-SEARCH discovery packet prescribed | regulated by Universal Plug and Play Device Architecture v1. It is a figure which shows the format of the response packet from the printer as an example of a network device. It is a figure which shows the transition of the dialog which shows the setup on the client computer of the network printer which uses USB. It is a flowchart which shows the setup on the client computer of the network printer which uses USB. FIG. 10 is a dialog transition diagram illustrating setup on the client computer using the USB of the network printer of the first embodiment. 3 is a flowchart illustrating a setup on a client computer using a USB of the network printer according to the first exemplary embodiment. It is a figure which shows the command which invalidates the UPnP function issued via USB. It is a figure which shows the command which validates the UPnP function issued via USB. In the second embodiment of the present invention, it is a transition diagram of a dialog showing the setup on the client computer of the network printer. 9 is a flowchart showing setup on a network printer client computer in the second embodiment of the present invention. 10 is a flowchart illustrating state transition on a printer of a network printer in the second embodiment of the present invention.

Explanation of symbols

PS1 ... Network print system,
100 ... client,
200 ... Network printer,
201 ... Protocol stack 202 ... UPnP protocol processing unit,
204: Printer controller,
205 ... Vendor specific protocol processing unit,
401 ... TCP / UDP protocol stack,
402 ... UPnP protocol processing unit,
403 ... Print protocol processing unit,
404: Print application.

Claims (6)

A client setup method in a device having a network interface, comprising a plurality of setup methods,
A discovery function invalidating means for invalidating the discovery function if the discovery function via the network interface as the second setup method is valid when starting the first priority setup;
Discovery function enabling means for enabling the disabled discovery function when the first priority setup is completed;
A device setup apparatus comprising: A discovery function invalidating means for invalidating a discovery function via a network interface that is not used for the first priority setup if the device has not completed the first priority setup in an initial state;
Discovery function enabling means for enabling the discovery function when the first priority setup process is terminated;
A device setup apparatus comprising:   A device having an interface 2 that is an interface other than the network interface, and when the setup is started by the device setting method of the first priority, at the beginning of the setup process, the device to be set up via the interface 2 The discovery function via the network interface is disabled by communicating and sending a command, and the discovery function is enabled by sending a command again when the setup process is completed. Device setup device. A client setup method in a device having a network interface, comprising a plurality of setup methods,
A discovery function disabling step of invalidating the discovery function and storing it in the storage device if the discovery function via the network interface as the second setup method is valid when starting the first priority setup;
A discovery function enabling step for enabling the disabled discovery function when the first priority setup is completed;
A method for controlling a device setup apparatus, comprising: In the initial state, if the device has not completed the first priority setup, the discovery function invalidation step of invalidating the discovery function via the network interface that is not used for the first priority setup and storing the discovery function in the storage device; ;
A discovery function enabling step for enabling the discovery function when the first priority setup process is completed;
A method for controlling a device setup apparatus, comprising:   A device having an interface 2 that is an interface other than the network interface, and when the setup is started by the device setting method of the first priority, at the beginning of the setup process, the device to be set up via the interface 2 By communicating and sending a command, the discovery function via the network interface is disabled, stored in the storage device, and when the setup process is completed, the discovery function is enabled by sending the command again. A method for controlling a device setup apparatus.

Images