KR20050056824A - Sobot based on ubiquitous network, system using the sobot, operation method of the system, and transition and transferring method of the sobot - Google Patents

Abstract

The present invention relates to a ubiquitous network-based software robot, that is, a sobot technology. More particularly, the present invention relates to a new robot for moving and transferring information to various information terminals in a ubiquitous network environment including the Internet. The concept relates to software robot technology. According to the present invention, in a ubiquitous environment, information is obtained or given through wireless communication with real-world objects, and moved to various information terminals of a user through a ubiquitous network including the Internet, and transferred according to the characteristics of the information terminal, A system using a ubiquitous network-based Sobot capable of processing and transmitting the result to a user, and a method of moving and transferring such a Sobot may be provided.

Description

SOBOT BASED ON UBIQUITOUS NETWORK, SYSTEM USING THE SOBOT, OPERATION METHOD OF THE SYSTEM, AND TRANSITION AND TRANSFERRING METHOD OF THE SOBOT}

The present invention relates to a ubiquitous network-based software robot, that is, a sobot technology. More particularly, the present invention relates to a new robot for moving and transferring information to various information terminals in a ubiquitous network environment including the Internet. The concept relates to software robot technology.

SOBOT is a software robot (hereinafter referred to as SOBOT), which has a life cycle, like an object in the real world, communicates with objects in the real world, is called regardless of the user's location or type of information terminal, Identify and move and transition. The present invention relates to a ubiquitous network-based sobot, a sobot system and a service system using a sobot, a method of operating a service system using a sobot, and a method of transferring and moving a sobot.

The conventional system architecture closest to this concept may enumerate a distributed processing structure in a client-server or P2P manner. However, software running in the current distributed processing architecture mainly considered only communication with computers connected to a network, and lacked consideration of communication with objects in the real world. In addition, operating on a fixed computer, the operation in the various information terminals is very limited and there is no concept of software movement and transition between information terminals.

However, the future network development will be a ubiquitous network environment that connects the real world and the virtual space, and the software operating in such an environment improves the existing method so that users can use a consistent information service anytime, anywhere using any information terminal. New concepts are required.

The present invention is to solve the above-described technical problem, using a new concept of a software robot, namely, a sobot, a sobot system, and a sobot, which is efficiently driven in a ubiquitous network environment and is moved and transferred to various information terminals of a user. Its purpose is to provide a service system, a method of operating a service system using Sobot, and a method of transferring and moving Sobot.

A system using a SOBOT according to the present invention for achieving the above object is a SOBOT platform mounted on hardware connected to a ubiquitous network and including profile information of the hardware, a network interface for performing an interface with a ubiquitous network, and A sobot station comprising an operating system for controlling an operation of hardware equipped with a sobot platform; And a task that has a predetermined identifier and is capable of moving and transitioning to the sobot station, and performing an interface between the user, another sobot, or the sobot station, and using a plug-in profile to request the user or another sobot. It is characterized in that it comprises a sobot that controls to be performed.

A method of transitioning and moving a SOBOT according to the present invention for achieving the above object is applied to a ubiquitous network in which a different network is integrated or interworked, and a first step of determining a destination to which the SOBOT moves; A second step of preparing a movement and transition of the SoBot to a destination determined in the first step; Transitioning the plug-in specification of the SOBOT into a form suitable for hardware and software specifications of the destination device through self reconfiguration; And a fourth step of moving the sobot transferred in the third step.

In the SOBOT transfer and movement method according to the present invention configured as described above, the second step includes performing an authentication procedure on the SOBOT platform of the destination device using the SOBOT unique identifier and authentication information; When the authentication is completed, diagnosing the possibility of transition of the SoBot by referring to the SoBot platform profile of the destination device; And determining, by the destination apparatus, whether to accept the SOBOT by referring to the profile of the SOBOT that sent the movement request, and issuing a movement ticket including information on the movement permission authentication and the movement method.

In addition, in the method of transition and movement of the Sobot according to the present invention configured as described above, the third step comprises the steps of extracting a plug-in specification suitable for the destination device by comparing the Sobot platform profile and the Sobot profile of the destination device; And dynamically reconfiguring the plug-in of SOBOT according to the extracted plug-in specification.

In addition, in the method for transferring and moving a sobot according to the present invention configured as described above, the fourth step may include transmitting the unit in a sobot unit by using a movement ticket issued by a sobot platform of a device to which the sobot moves; And, it characterized in that it comprises the step of transmitting over a communication connection at a time the sobots to move in a certain period.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention will be described in detail.

1 illustrates a network environment to which a ubiquitous network-based Sobot is applied according to an embodiment of the present invention.

The ubiquitous network 100 shown in FIG. 1 comprehensively encompasses existing wired and wireless Internet environments and communication networks. The ubiquitous network 100 includes a variety of hardware such as a personal computer (PC), a game console, a portable information device such as a clock, a PDA, a telephone, a home appliance such as a digital TV, a refrigerator, a washing machine, a robot, and an RF (radio). Various real world objects are connected through a sensor network such as a frequency identifier. Particularly, an identifier assigned to the ubiquitous network 100 is called a ubiquitous object. In FIG. 1, a software set 101, a hardware set 106, and a thing set 107 are illustrated as ubiquitous objects. An identifier may also be assigned to the Sobot user 102 using the ubiquitous network 100.

The virtual space composed of ubiquitous objects is called ubiquitous space 103. Sobot 104 is a ubiquitous network-based software robot that operates on hardware connected to a ubiquitous network. The sobot 104 also has an identifier.

Sobot 104 can recognize and interact with ubiquitous objects regardless of their physical distance. Thus, the Sobot user 102 can use the ubiquitous object regardless of the physical distance.

Meanwhile, the SOBOT 104 includes a SOBOT user interface 105 for interacting with the SOBOT user 102, and interacts with the SOBOT user 102 and the SOBOT 104 and the SOBOT user 102. ) Can exchange information. Various information is embedded in objects participating in the ubiquitous space 103. The Sobot user 102 may acquire information present on the ubiquitous space 103 through the Sobot 104. The Sobot 104 intelligently assists the process of using information of the Sobot user 102. That is, the Sobot 104 serves as an information assistant on the ubiquitous network.

The SOBOT user 102 can use the SOBOT 104 to use various software sets 101, hardware sets 106, and object sets 107 that exist on the ubiquitous space 103 without spatial constraints and use the information. have.

FIG. 2 is a diagram for describing a life cycle of a ubiquitous network-based sobot according to an embodiment of the present invention.

In the embodiment of the present invention, all SOBOTs are created from the source copy (master copy) which is the source thereof, and the original SOFTWARE is original software developed from the SOBOT developer. All procedures for developing such original software, i.e., a procedure including the life cycle of general software, are called creation step 201.

After the creation step 201, a birth step 202 is performed that creates named copies of the original software, each assigned a unique identifier, for distribution to users of the Sobot. The unique identifier of the SOBOT acts as a real-world ID card in the ubiquitous environment, and is an essential element for performing the activities and service activities in all subsequent growth stages 203.

When the unique identifier assigned to the copy of the software is registered in the designated Sobot registry, the next step, the growth step 203, is performed. In the growth step 203, a Sobot learns new knowledge from an external environment or a user, fuses existing knowledge, or establishes its own knowledge base through a cooperative process with another Sobot existing in a ubiquitous environment. You will repeat the process of expanding. Sobot, with an excellent knowledge base, will have the ability to provide better service.

If a serious security problem occurs such that the Sobot's unique identifier is stolen or forged by a malicious user during the operation of the growth step 203, it is possible to cancel the registration of the identifier and take measures to prevent reuse. As such, the process of erasing registration of the unique identifier of the Sobot is referred to as revocation step 204. Once discarded, the Sobot can no longer perform the growth stage 203 and provide services.

However, if it is not a serious security problem or there is a situation where the use of the Sobot for a long time, it is possible to change to the dormant stage 205 by applying for a temporary suspension of the Sobot identifier. Like the discarding step 204, the sobot is no longer able to perform the growth step 203 or provide the service in the dormant step 205, but if the reuse is desired, the growth step 203 is applied again through an identifier recovery application. ) Can be converted to

3 is a block diagram of a service system using a ubiquitous network-based SOBOT according to an embodiment of the present invention.

As shown in FIG. 3, the service system using the SOBOT according to the embodiment of the present invention performs the SOBOT manufacturer (301) that develops the SOBOT original software, and sells the SOBOT on behalf of the SOBOT manufacturer, and identifies the SOBOT. And a SoBot service provider 302 for registering SOBOT related information, an SOBOT registry 303 for storing SOBOT identifiers, SOBOT related information, and information related to suspension / deletion, and installing the sold SOBOT therein to transfer the SOBOT. A plurality of sobot grooves 304 for controlling the control and at least one connected to each of the sobot grooves 304 to provide various services to the user through performing the growth stage of the transferred sobots as well as to perform the expansion of the knowledge base It is composed of a plurality of sobot station (305).

As described above, the Sobot has a life cycle, each stage of which is closely related to the configuration of its service system. The SOBOT manufacturer 301 is a company that develops original SOBOT software, and develops SOBOT that can provide various functions and services and consigns sales to SOBOT service provider 302. Of course, it is also possible that the Sobot maker 301 directly sells. The completion of the development of this original software corresponds to the creation phase of the Sobot life cycle.

Sobot's original software entrusted to the Sobot carrier 302 is sold according to the user's application, and the Sobot sold is copied from the original software. The sobot operator 302 receives a new identifier of a sobot to be sold from the sobot registry 303 and registers the identifier and various information related to the sale / purchase with the sobot registry 303. Various information registered in the SOBOT registry 303 can be retrieved at any time from a legitimate user or SOBOT. For example, whether or not the specific SOBOT is discarded can be confirmed. In addition, a user of a Sobot may submit a change request to the Sobot Registry 303 for changeable information about his Sobot. For example, a human application for Sobot.

The SOBOT registered in the SOBOT registry 303 is installed in a SOBOT home 304 such as a home server or a PC of the user, and is converted to a growth stage, thereby providing a service. The growth of the SoBot can transition from the SOBOT home 304 to the SOBOT station 305 in various forms and continues to grow by providing various services to the user and continuing to expand their knowledge base.

Next, a configuration and operation of a sobot station in which a sobot is installed will be described with reference to FIG. 4. 4 is a block diagram of a system using a ubiquitous network-based Sobot according to an embodiment of the present invention.

In order for the SOBOT to operate, the SOBOT platform 403 must be mounted on the hardware 402. The hardware on which the sobot platform 403 is mounted is referred to as the sobot station 400. The sobot station 400 is assumed to participate in the sobot network via the network interface 412. Hardware or things that are not equipped with the SOBOT platform 403 can participate in the ubiquitous space if they are connected to the ubiquitous network, but SOBOT cannot operate inside.

The Sobot platform 403 allows Sobot to operate on different hardware 402 and operating system 404. It is similar to the concept of the existing virtual machine. Sobot platform 403 includes and manages platform profile 405. The features and capabilities of the hardware device on which Sobot operates are specified in the platform profile 405 above. A qualified Sobot may approach the platform profile 405 to extract information from the platform profile 405.

The Sobot consists of the Sobot Core 406 and a set of Station Plug-ins 407 suitable for the Station. The sobot core 406 has an identifier of the sobot and is responsible for interfacing with the sobot station 400. The Sobot Core 406 also manages knowledge and user preferences 408 learned during service, and manages a plug-in set profile 409. The plug-in set profile 409 describes the configuration state of the plug-in.

The Sobot plug-in can be classified into an external plug-in and a functional plug-in. The appearance plug-in determines the appearance and personality of the Sobot, and the function plug-in is responsible for functions related to the information service and input / output interface functions. The appearance plug-in mainly configures the SOBOT user interface 401, through which the user 410 can experience the SOBOT. The appearance plug-in is selected in consideration of the capabilities of a hardware user interface 411 such as a display, speaker, microphone, keyboard, tactile equipment, and the like. In particular, when implemented through a graphical user interface (GUI) plug-in has an avatar form. If it is impossible to implement the GUI, it may have a text or voice form.

5 illustrates a case in which a ubiquitous network-based sobot is dispatched to another sobot home according to an embodiment of the present invention.

As shown in FIG. 5, the sobot communicates with other sobots via the sobot protocol 500. The ubiquitous network in which the Sobot protocol 500 can be used is called a Sobot network 501. Sobot communication enables cooperative work, information exchange and sharing between Sobots. The content of Sobot communication is protected by security.

The SOBOT home 502 includes a home SOBOT platform 509, a storage and management unit 506 of information and knowledge collected by individual SOBOTs, a home plug-in set 505 for providing services, a home service set 508, and an add-on processing unit. It is a special Sobot station that includes 507.

The Sobot home 502 may be operated in a personal computer, server computer, large internet data center, home server, or the like. In general, the SOBOT groove 502 can be viewed as having more computational resources than the SOBOT station.

The Sobot resides in the Sobot Home 502 and may leave the Sobot Home 502 and move to a remote Sobot Platform 510 in response to service requests from other ubiquitous objects, calls from users or other Sobots. have. In this way, the sobot that moves away from the home is called the dispatch robot 503.

Even if the dispatched sobot 503 moves, the originating sobot 504 resides in the sobot groove 502 to maintain communication with the dispatched sobot 503. The origin sobot 504 and the dispatch sobot 503 may exchange information through communication.

The dispatched sobot 503 initially moves to the core form, configures the plug-in set profile according to the platform profile of the station, and requests and sends the required plug-in to the origin sobot. The origin sobot 504 can access a relatively rich knowledge compared to the dispatch sobot 503, utilize a vast amount of computing resources, and can use a variety of plug-ins.

In the Sobot home 502, a set of home plug-ins 505 that can be sent to the dispatched Sobot core is managed. The home plug-in set 505 may also include a plug-in that can use hardware and software information services not included in the Sobot station. For example, it may include an adapter role that can use an existing web, web service, or a specific application.

Basically, even after the home plug-in set 505 is configured, additional plug-ins, information, and knowledge for performing a user's request work may be transmitted through the knowledge and information storage and management unit 506.

If the user's requested operation is not suitable for the computational resource specified in the platform profile and cannot be processed on the station, the dispatched sobot 503 may request the origin sobot 504 to perform the service remotely.

As a first example of remote performance, origin sobot 504 performs remote service using a plug-in suitable for the performance of the platform profile and request task of sobot home 502 and delivers the results to dispatch sobot 503.

A second example of remote execution is to utilize the computing power and specific applications of the home Sobot platform 509 only. This is performed by the add-on processing unit 507, and an example of the add-on may be inference about vast knowledge.

As a third example of remote performance, Sobot Home provides a set of home services 508 for frequently used or complex services. Examples of home services include knowledge searches, plug-in searches, and so on. Home services are predefined services, as opposed to dynamically combining plug-ins. Various Sobot homes 502 are possible for specialized home services. For example, a router of a rest area function, hibernation, a plug-in shop, a grave, an avatar shop, knowledge education, an evaluator, and the like.

As a fourth example of remote execution, if processing is not possible even in the belonging sobot home 502, it may request service from another sobot home of another suitable platform profile, or request transmission of a plug-in held by another sobot home. For services that require distributed processing, structurally differentiated dispatch sobots can be simultaneously transferred to multiple sobot stations.

Sobot collects and learns user preferences through interaction with the user. User preferences can be stored distributed across stations and homes. User preferences can be initially given explicitly by the user. Based on the learned preferences, it is possible to intelligently provide a personalized service to the user.

After the service, the dispatched Sobot 503 returns to the home with knowledge. After returning, preferences and service results are taken, stored with Sobot's knowledge and managed for future service. Thus, the Sobot home is the center of Sobot knowledge. The storage and management unit 506 of the knowledge and information is provided to store and manage the knowledge and information of the origin Sobot 504 after the service. The knowledge can be shared with other Sobots and can be extended in a packaged form. Knowledge in Sobot space can be managed, searched, and exchanged according to the ontology. Sobot's knowledge should be treated as an important intellectual property. Plug-ins and home services in the Sobot space can be managed and retrieved in an ontology format like special knowledge, which is handled by the registry.

6 shows a method of operating a service system using a ubiquitous network-based Sobot according to an embodiment of the present invention.

As shown in FIG. 6, the SOBOT resides in the SOBOT home and waits for a service request from another ubiquitous object (S600 and S611). Calling steps S601 and S612, meaning service request, are also possible from the user or other Sobot.

When the service request arrives at the sobot by the calling step (S601), the sobot moves from the sobot home to the remote sobot station (S605), and the sobot at this time is called a dispatch sobot. On the other hand, even when the dispatched Sobot moves in the Sobot home, the original Sobot is activated to maintain communication with the dispatched Sobot (S602). The origin sobot and the dispatch sobot may exchange information through communication.

After the dispatched Sobot moves in the step S605, the transfer of the dispatched Sobot (S606), the provision of the service, and the interaction with the originating Sobot (S607) are sequentially performed, and when the dispatched Sobot's work is completed, the dispatched Sobot is completed. Returns to the Sobot home (S608), and the service ends (S609). On the other hand, after the origin Sobot is activated by the step (S602), the origin Sobot performs the step of preparing the plug-in and knowledge (S603), performs a home service (S604), and terminates the service (S609).

If the dispatched sobot performing the operation of step S607 is unable to process the work through the belonging sobot home, another sobot home including another suitable platform profile may be called (S612). In the SOBOT home called by the step S612, the originating SOBOT of the corresponding SOBOT home is activated (S613), a home service is performed, and the result is notified to the dispatched SOBOT (S614). It ends (S615).

7 illustrates a method of transitioning and moving a sobot based on a ubiquitous network according to an embodiment of the present invention.

In FIG. 7, step S701 is a step in which the movement of the sobot is started. Initiation of the movement of the Sobot may be made at the request of a user, or may be automatically made according to a preset. Sobot automatically tracks the movement of the user, so that it can move to the user's own device or ubiquitous device close to the user's location.

The next step S702 is to determine the destination of the movement. There are two main ways to determine the destination of a move. One is to receive the destination of the movement directly from the user or a third party information provider, and the other is to determine the optimum movement destination using the movement conditions provided by the user or determined by self judgment. In order to properly determine the travel destination, intelligent information retrieval must be performed against the Sobot platform registry.

Step S703 of FIG. 7 is a step of performing the Sobot movement and transition preparation work for the first determined movement destination. Sobot moves and prepares for transfer with the help of the transfer-related services provided by the Sobot platform mounted on the move destination.

The movement and transition preparation step (S703) is largely composed of three steps (S704, S705, S706).

The step S704 is a step of performing authentication by transferring authentication information of the SOBOT to the moving destination and requesting authentication information of the moving destination. The moving destination platform receives and analyzes the authentication information of the Sobot to be moved to determine whether to accept the Sobot.

Step S705 is a step of diagnosing the possibility of transition of the SoBot, and determining the suitability of the transition by analyzing static and dynamic information such as the specification of the device, the current state of the device, and the reliability of the recent device with reference to the SOBOT platform profile of the moving destination. do. In this case, the profile of the SOBOT and the user's preference information may be additionally referred to, and accordingly, the transition may be determined.

If both agree to move and it is determined that the transfer is possible, the destination Sobot platform issues a move ticket that permits the move, and the Sobot that wants to move may receive the move ticket issued by the destination Sobot platform (S706).

If a situation in which transfer is impossible during the movement preparation step occurs, the flow returns to step S702 to select a new movement destination.

Steps S707 and S708 of FIG. 7 are steps in which actual movement and transition are performed. The step S707 is a step of transferring the plug-in specification of the SOBOT through self reconfiguration in a form suitable for the SOBOT platform of the destination device. For self reconstruction, Sobot matches the profile of the destination Sobot platform with its own profile. Based on the list of available plug-ins extracted as a result of the match, Sobot changes the configuration of the plug-in set. Plug-in modules to be removed are returned to the Sobot home, and new plug-in modules are requested to the Sobot home.

Next, step S708 is a step in which the Sobot moves to the destination platform through the ubiquitous network. The movement method of the SOBOT can be implemented in various ways. The ticket issued in step S706 may be used as a key to directly move to a Sobot individual unit or may be boarded and moved on a Sobot transport bus that moves between platforms at a predetermined time. The latter method of movement is suitable for controlling the frequency and amount of movement. The movement of the Sobot can be suitably carried out depending on the situation.

Step S709 of FIG. 7 is a flow in which the order of performing the steps S707 and S708 is reversed. The step S709 shows that, depending on the situation, the Sobot may be moved to a destination device, and then a transition operation may be performed through self reconfiguration.

As described above, the present invention can be used as a new concept of a software robot that interacts with users and real-world objects in various information terminals and services knowledge information anytime, wherever the user is, and is created with a unique identifier. It will be able to create new business models with the concept of having a lifecycle that is sold or sold to, and discarded when needed.

What has been described above is only one embodiment for implementing a system and a method of transition and movement of the Sobot using a ubiquitous network-based Sobot according to the present invention, the present invention is not limited to the above embodiment, the following patents Without departing from the gist of the invention claimed in the claims, any person of ordinary skill in the art to which the present invention extends to the technical spirit of the present invention to the extent that various modifications can be made.

1 is a view showing the overall network environment to which the ubiquitous network-based Sobot is applied according to an embodiment of the present invention.

2 is a view for explaining the life cycle of the ubiquitous network-based Sobot according to an embodiment of the present invention.

3 is a diagram illustrating a configuration of a service system to which a ubiquitous network-based Sobot is applied according to an embodiment of the present invention.

4 is a diagram showing the configuration of a system using a ubiquitous network-based Sobot according to an embodiment of the present invention.

5 is a diagram illustrating a case in which a ubiquitous network-based sobot is dispatched to another sobot home according to an embodiment of the present invention.

6 is a diagram illustrating a method of operating a system using a ubiquitous network-based Sobot according to an embodiment of the present invention.

7 is a diagram illustrating a method for transitioning and moving a bot based on a ubiquitous network according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

500: Sobot Protocol 501: Sobot Network

502: Sobot Home 503: Dispatch Sobot

504: Origins Sobot 505: Home Plug-in Set

506: knowledge and information storage and management

507: add-on processing unit 508: home service set

509 Home Sobot Platform 510 Remote Sobot Platform

Claims (8)

In a system using Sobot applied to a ubiquitous network in which different networks are integrated or interworked, Sobot station, which is installed on the hardware connected to the ubiquitous network and includes a Sobot platform including profile information of the hardware, a network interface for interfacing with the ubiquitous network, and an operating system for controlling the operation of the hardware equipped with the Sobot platform. ; And It has an identifier assigned in advance and can be moved and transitioned to the Sobot Station, and an interface between the user, another Sobot, or the Sobot Station is used to perform a task requested by the user or another Sobot using a plug-in profile. Sobot comprising a control so that System using Sobot based on ubiquitous network. The method of claim 1, wherein the Sobot is A Sobot core having an identifier assigned in advance and performing an interface with the Sobot station; A user interface for performing an interface with a Sobot user; A plug-in set including a plug-in suitable for hardware on which the Sobot platform is mounted; And And a plug-in set profile describing a configuration state of the plug-in. System using Sobot based on ubiquitous network. The robot according to claim 1 or 2, wherein the sobot is A creation step comprising a procedure for the Sobot developer to develop original software; A birth step of creating a copy of the original software given a unique identifier to distribute the Sobot to a user; A registration step of registering a unique identifier assigned to the copy of the software in the Sobot Registry and extending the knowledge base with knowledge obtained in the course of learning, fusion and cooperation with other Sobots; A discarding step of canceling registration of the identifier and making it impossible to provide a service when a security problem occurs due to theft or forgery of the unique identifier in the growth step; And Characterized by having a life cycle consisting of a dormant step of temporarily suspending the use of the identifier upon application of the user. System using Sobot based on ubiquitous network. The method according to claim 1 or 2, The SOBOT is activated by the user's request while waiting for the user's request in the SOBOT home, and when the user's request cannot be processed in the SOBOT home, the SOBOT is dispatched to another SOBOT home and distributed from the SOBOT home to the other Performing services that meet the needs of users System using Sobot based on ubiquitous network. In the method of transition and movement of Sobot applied to the ubiquitous network in which different networks are integrated or interworked, A first step of determining a destination to be moved by the Sobot; A second step of preparing a movement and transition of the SoBot to a destination determined in the first step; Transitioning the plug-in specification of the SOBOT into a form suitable for hardware and software specifications of the destination device through self reconfiguration; And And a fourth step of moving the sobot transferred in the third step. Sobot transition and movement method based on ubiquitous network. The method of claim 5, wherein the second step Performing an authentication procedure with respect to the Sobot platform of the destination device using the Sobot unique identifier and authentication information; When the authentication is completed, diagnosing the possibility of transition of the SoBot by referring to the SoBot platform profile of the destination device; And The destination apparatus may include determining whether to accept the SOBOT by referring to the profile of the SOBOT that has sent the movement request, and issuing a movement ticket including information on the movement permission authentication and the movement method. Sobot transition and movement method based on ubiquitous network. The method of claim 5, wherein the third step Comparing the Sobot platform profile and the Sobot profile of the destination device to extract a plug-in specification suitable for the destination device; And And dynamically reconfiguring the bots according to the extracted plug-in specification. Sobot transition and movement method based on ubiquitous network. The method of claim 5, wherein the fourth step Transmitting, by a SoBot unit, a SoBot unit using a travel ticket issued by a SOBOT platform of a destination device to which the SOBOT moves; And Transmitting via a single communication connection at a time the sobots to be moved at regular intervals; Sobot transition and movement method based on ubiquitous network.