KR20070004407A - Method for community computing and community computing system - Google Patents

Abstract

A method and a system for community computing are provided to design a model collaborating in a community unit by organically combining persons, computing devices, and services, as a community model is applied to a ubiquitous computing environment. A community purpose part contains a final purpose to be attained by the community. A community skin part supports privacy protection/information hiding in the computing environment probably opening excessive information by encapsulating the community. A community policy part supports an operation of the community by being diversely combined as a policy set for functions of the community. A community member part performs mutual collaboration to attain the final purpose by binding the community. A community action part provides context-based action to be taken by the community member part to attain the final purpose.

Description

Community Computing and Community Computing System

1 is a diagram illustrating the life cycle of a community in five states for realizing a community computing method according to the present invention.

2 is a diagram illustrating a static conceptual model for a community for realizing a community computing method according to the present invention.

3 is a diagram illustrating a community divided into a service community, an infrastructure community, and a user community according to the present invention.

4 is an exemplary diagram of an autonomous media service scenario.

5 is an exemplary diagram of a healthcare scenario.

6 is a diagram illustrating the structure of a community computing system according to the present invention.

 7 is a diagram illustrating a mechanism in which a community is executed.

 8 is a diagram illustrating an order in which communities are executed.

The present invention relates to a community computing system and method. In more detail, the present invention, the community forming step of forming a community by defining the purpose of the community, policies, members, the operation of members, community operation situation, community dormancy situation and the like; Waiting for a time for the community to form and operate an actual community member after the community forming step; A community operation step in which the community monitors the status information after the community waiting step and then activates itself to start an operation when the community operation status is reached; A community dormant step in which the community temporarily stops operation on its own and waits for the next community operation step when the community meets the purpose of the community or sleeps after the community operation step; And a community termination step of terminating all operations by itself when the community no longer needs to operate.

Ubiquitous computing can be defined as' a space or environment where anyone, anytime, anywhere, can access an online network and receive services through various terminals and objects.'In order for ubiquitous computing to become visible, It is required that the network be aware of the situation of human living space.

In the field of ubiquitous computing, technologies for realizing this are continuously based on three basic concepts: invisible computing, everwhere computing, and seamless network. Developing. Examples include sensing technologies, miniaturization of devices, and radio frequency identification (RFID). These technologies and application services are developed around a single domain.

In order to grasp the user's intention and provide appropriate services in the ubiquitous computing environment where various and complex devices and services are mixed, it is required that the objects in the environment are organically combined and share their respective roles. The problem of collaboration between information, devices, and services cannot be overlooked.

Topics expected to be computing issues in the upcoming ubiquitous computing environment include heterogeneous environment control, conflict resolution among ubiquitous entities, security, The intelligence required for an individual context model. Detailed description of these is as follows.

First, in terms of controlling heterogeneous environments, not only devices with computing power and networking functions are available in ubiquitous computing environments, but also various types of software to provide services, and various protocols and networks supporting their communication. It may have heterogeneity beyond that. These heterogeneous characteristics require various integrations and collaborations among users, services, infrastructures, or networks, and it is difficult to overcome these heterogeneous characteristics with existing integration and collaboration models.

Second, in terms of solving the conflict problem between the objects that make up the ubiquitous computing environment, in the ubiquitous computing environment, the objects that make up the environment may or may not have intelligence because computing is ported to various things. have. Conflict resolution models between entities with the same level of intelligence and autonomy have been proposed, but the issue of how to detect the behavior of entities with different levels of intelligence and autonomy and resolve conflicts that may arise between them is an issue. Can be.

Third, in terms of security, a lot of information needs to be gathered and shared for personalized service and autonomous service in the mobile environment. In this process, personal information and other information related to individual privacy are different from the user's intention. May be exposed. A new security concept is needed to simultaneously pursue two different factors: privacy prevention and information sharing.

Fourth, in terms of the intelligence required for individual context models (analyzing context data to define the relationships between these data), in order to change services according to the context, only context is understood through sensing data. Rather, it should be possible to understand different contexts for different users, devices, and services. This requires understanding and sharing of contexts that are developed around domains in cross-domains.

In order to solve the above-mentioned issues and requirements, it is necessary to introduce a community concept into the ubiquitous computing environment and recreate the community as an organic and autonomous collective in the ubiquitous computing environment.

Communities are defined in a lexical sense as meetings of people living in nearby areas or meetings with common interests, which have evolved from communities in the real world to online communities that connect to the Internet.

The proposer of the present invention intends to solve the above-mentioned difficulties in the ubiquitous computing environment by designing a model in which people, computing devices, and services are organically combined and collaborated in community units by incorporating such community models into the ubiquitous computing environment.

The present invention has been proposed to solve the above problems, and an object of the present invention is to design a model in which people, computing devices, and services are organically combined to collaborate in a community unit by incorporating a community model into a ubiquitous computing environment.

The present invention has been proposed to solve the above problems, by providing a community computing system by designing a model in which people, computing devices and services are organically combined to collaborate in community units by incorporating a community model into a ubiquitous computing environment. There is.

Other objects and advantages of the present invention will be described below, which are not limited to the matters set forth in the claims and the disclosure of the embodiments thereof, but also to the broader ranges by means and combinations within the range readily recited therefrom. Add that it will be included.

In order to achieve the above object, the present invention is a community forming step of forming a community by defining the purpose of the community, policies, members, members of each other, community operation situation, community dormancy situation and the like; Waiting for a time for the community to form and operate an actual community member after the community forming step; A community operation step in which the community monitors the status information after the community waiting step and then activates itself to start an operation when the community operation status is reached; A community dormant step in which the community temporarily stops operation on its own and waits for the next community operation step when the community meets the purpose of the community or sleeps after the community operation step; And a community termination step of terminating all operations by itself when the community no longer needs to operate.

In order to achieve the above technical problem, the present invention provides a community computing system defined as an autonomous collaboration model between entities that are present in a highly distributed form in a ubiquitous computing environment. A community manager for setting goals for the service and managing service collaboration; A situation rule repository for storing rules applied for respective situations; A situation manager which obtains the situation information, which is a collection of context data from the situation rule repository, and provides the situation information to the community manager; A community repository that stores a description of the community and provides it to the community manager; A meta service repository for classifying services into types and defining and storing interfaces for each type; And a community framework that references members of the meta service repository to find and connect members to achieve service goals.

Community computing defines the autonomous collaboration model among individuals that exist in highly distributed form in ubiquitous computing environment as a community and combines it with ubiquitous computing environment to solve the complexity and computing issues brought by ubiquitous computing environment.

Collaborated entities are encapsulated into community members by community skins, and their priorities can be dynamically assigned to security, quality of service (QOS): community goals, or roles within members of the community. To ensure differentiated service quality), user preferences, and other actions between community members and community members.

Community computing, which introduces the concept of community in the ubiquitous computing environment, does not expose information that may be sensitive to users and reduces dependency on the community.

In order to implement such a community in an actual computing environment, the community is classified into three types: a user community, a service community, and an infra community.

In other words, in order to support each heterogeneous dimension in the ubiquitous computing environment, the community layer is divided as an abstract model and defined for each type of community property, and then devices, infrastructure, web services, agents, applications, etc. Various types of software and hardware are mapped to these community layers. Through this, when a service is provided to a user, the objects on the same community layer are organically combined into one community to provide a service, and the changes of the user's intention and environment can be smoothly reflected through the interworking between the community layers. Can be.

1 is a diagram illustrating the life cycle of a community in five states for realizing a community computing method according to the present invention.

In the community computing method according to the present invention, a community refers to an autonomous collaboration model between entities that exist in a highly distributed form in a ubiquitous computing environment. The attributes of the community itself are discussed in detail later.

In the community computing method according to the present invention, the community forming step refers to a step of forming a community by defining a purpose, a policy, a member, an operation between members, a community operating situation, a community dormant situation, and the like.

In the community formation stage, a goal to be completed by the community within the ubiquitous computing environment is newly set, and thus, services and devices necessary to reach the goal are selected and how they should cooperate. This information can be located in global storage or local storage, depending on the extent of the impact of the purpose of the community.

And because the purpose of the community is not just archived, there may be users or entities who want to know what the purpose of the community is, so that purpose may be announced depending on the extent of the impact of the purpose of the community. have.

In the community computing method according to the present invention, the community waiting step refers to a step in which a community waits for a time when a community should form and operate an actual community member after the community formation step.

In the community waiting phase, information about the goals the community needs to complete within the ubiquitous computing environment, the types of services and devices needed to reach those goals, and how they work together is loaded from the community storage into memory. At this moment, the community finds its members and asks them to join the community to organize the actual community to serve its purpose.

At this time, the members are entities that are tied together as a community within the community and cooperate with each other to achieve the end goal pursued by the community.

On the other hand, the community may be reconfigured through real-time discovery of new services, devices, etc., even at the moment when the community becomes active (described later) after the community waiting step.

In the community computing method according to the present invention, the community operation step refers to a step in which the community monitors the status information after the community waiting step and then activates and starts an operation when the community operation status is reached.

In the community operation phase, the requirements of the community are described, including information about the goals the community needs to accomplish within the ubiquitous computing environment, information about the types of services and devices needed to reach those goals, and how they work together. When the community members configured in the community waiting phase to perform the community activation situation (activate situation) is activated by itself and starts the operation.

The flow of information and sharing of information among members in a community is determined by the policies within the community and forced to be dormant by communities that are at a higher level than the community or require an emergency. Unless deactivated, the community operation phase continues until the state of the community members reaches the final state of the community.

In the community computing method according to the present invention, the community dormancy step refers to a step in which the community temporarily stops the operation and waits for the next community operation step when the community meets the purpose of the community or becomes dormant after the community operation step. .

In the community dormancy phase, the community recognizes that the surrounding environment has changed to a situation in which the community no longer operates, and the community enters into a deactivation state by itself.

In the community computing method according to the present invention, the community terminating step refers to a step of terminating all operations by itself when the community no longer needs to operate.

When a community no longer needs to operate, it is when the community is merged or evolved into a new community with a different goal and the original community is no longer needed.

The termination of the community can take several forms, depending on the nature of the community. That is, there may be a community that fulfills its community's fate and completely exterminates, or there may be a community that stays in a long period of deactivation. On the other hand, a community may be terminated and reorganized by an entity managing the community.

Meanwhile, in the community computing method according to the present invention, when the service type provided to the user by the community is a one-time service, the community may include the community forming step, the community waiting step, the community operation step, and the community dormancy step. After going through sequentially, the service will be provided while going directly to the community termination step.

In addition, in the community computing method according to the present invention, a service type provided to a user by the community must be repeatedly provided in a specific situation (or a request point) such as a media service, or operated in a specific situation after being serviced in the background as a security service. If the service is not a one-time service, such as a case should be, after the community has gone through the community forming step and the community waiting step, the community enters into the community operation phase when the specific situation is finished, and enters the community dormancy phase when the specific situation ends. When other specific situations occur, the service repeatedly enters the community operation stage.

A community as a subject for realizing a community computing method according to the present invention is as follows.

2 is a diagram illustrating a static conceptual model for a community for realizing a community computing method according to the present invention.

Community is an autonomous collaboration model between entities that exist in highly distributed form in ubiquitous computing environment.

The community may include a community purpose unit which contains the final purpose that the community should achieve; A community skin unit encapsulating a community to support information hiding for privacy protection and security in a computing environment in which too much information can be disclosed, and to reuse a complex service defined in a community unit; A community policy unit that is connected to the community as a set of policies for functions of the community itself and supports the operation of the community; A community member unit that is tied together as a community and cooperates with each other to achieve a final goal pursued by the community; And a community action unit providing a context-based action that the community member should take in order to achieve the purpose of the community.

Community objectives contain the final goals that the community must achieve.

The community and the goal of the community are mapped one-to-one, and this goal can be interpreted differently by information about the user's preferences and the surrounding situation. Here, the situation refers to a combination of the states of the entities constituting the ubiquitous computing environment on a time basis. Meanwhile, the objects that make up a ubiquitous computing environment include users, services, and infrastructure.

The purpose of a community is to create a temporary type that fragments according to the type and nature of the community and disappears after accomplishing the purpose, and to be a permanent type that is activated and operated in a specific situation and then deactivated in a specific situation. There is a purpose.

Since the purpose of the community is set according to the operation category of the community, it is necessary to subdivide the operation category of the community and normalize the level of the purpose to cope with it.

The community skin unit encapsulates the community, supports information hiding for privacy protection and security in a computing environment where too much information can be disclosed, and enables the reuse of complex services defined at the community level.

The community policy unit is a policy set for functions of the community itself, and is connected to various communities to support the operation of the community.

The policy of the community is the core type and option type (the core type is the basic policy type for the community to operate properly. The ones in the community concept map such as security and status belong to the core type, and the option type is added according to the characteristics of the community. For example, investment policy and risk management policy can be added in asset management community.) Core type policy is defined regardless of community type. QoS (same as page 7), security, user preferences, etc. can be defined as a policy.

Community members are entities within a community that are tied together as one community and cooperate with each other to achieve the end goal of the community.

Community members can be primitive types of users, services, or infrastructure, depending on the classification of the community, or a community, a group of each of them, can be another individual community member. .

Community member states can be divided into two states: active and active in the community, and inactive and waiting. They may be described as specific instances by community class, or by required functionality rather than instance names (eg For example, it can be described as a living room phone, a large room phone, a schedule service running on a PDA, a schedule service running on a PC, but as a required function, a phone, a schedule service, a device with a sound function, and a microphone function. Device with display, device with display function).

The community action unit serves to provide context-based actions that the community member should take in order to achieve the purpose of the community.

Action refers to the action the community should take, and the community action section describes the state-based community member state (action refers to the action the community or community member should take, and the action section describes the context-based community and community member). Describe the action). It may be defined on a rule-based basis or may be described as a planable structure by defining states (depending on the rule by defining a rule-based action on actions taken by a community or a community member in a specific situation). Actions can be made, and the states of community members and the relationships in which movements can occur are described so that community actions can be made intelligently and autonomously.).

On the other hand, in the community as a subject for realizing the community computing method according to the present invention, a web service, an application, an agent service, etc. constitute a community member, and support a complex service based on the preferences and surroundings of the community user. A service community that serves to enable cross-service collaboration; The network devices and devices constituting the infrastructure constitute a community member unit, create a device group based on location to support resource management, error recovery, quality management, etc., and propose an appropriate device to the service community. An infrastructure community that serves to construct a service-oriented community for the proper operation of the service community; And a real user, such as a family member or a coworker, constitutes a community member, and manages a profile of user group reliability, group work, and the like to derive user requirements for the service community and the infrastructure community. Characterized by the user community.

3 is a diagram illustrating a community divided into a service community, an infrastructure community, and a user community according to the present invention.

In the service community, web services, applications, and agent services constitute community members, and enable service-to-service collaboration to support complex services based on community user preferences and surroundings.

Service community is composed of web members, applications, and agent services that provide services to users, and when describing a community, the members are dynamically defined by defining members as service types or not as service instances. Allows services and communities to participate as members of a community. (Same as what was added on page 14, for example, the service type is 'Media Play', the service name is 'Windows Media Player', 'Bear Player', etc., and the service instance is 'Windows Media Player running on the living room PC', Classified as 'Windows Media Player running in a large room PDP'; In the community formation stage, the member is described only by service name or type, and in the waiting and operation stages, the appropriate service instance is found for each situation and configured as a community member. To support a mobile adhoc environment where discovered service instances can be changed at any moment; the existing service discovery and service operation techniques are made on a per service instance basis.

The infrastructure community consists of the network members and devices that make up the infrastructure, and the community members are created, and device groups are created based on location to support resource management, error recovery, and quality management, while suggesting appropriate devices to the service community. In other words, it forms a service-oriented community for the proper operation of the service community.

An infrastructure community is a physical device that allows all computers, appliances, media, and sensors with computing and networking capabilities to be members of the infrastructure community. Location-based communities may be locally defined to support resource management, self-healing, and self-healing, and service-oriented communities may be configured according to circumstances.

That is, the infrastructure community may have two types of 'location-based community' and 'service-oriented community'.

User community consists of real users such as family members and co-workers, and constitutes the members of the community, and manages profiles of user group reliability, group work, etc. to derive user requirements for service community and infrastructure community. .

A user community is a community that is connected to a real user group, and can be applied to deriving requirements of a service community and an infrastructure community by describing a family and a colleague. Meanwhile, members of the user community may be mapped to a service of a service community or a device of an infrastructure community.

The above three communities are designed to incorporate heterogeneous services, devices, etc. into an abstracted level in each class. For example, the service community is not limited to agents, but various forms such as applications and web services. The service of can be located-it is defined with scalability later.

As a subject for realizing a community computing method according to the present invention, a community can change and evolve by learning itself in the process of activating a community and achieving a goal. Aspects of changing and evolving community according to the present invention are as follows.

First, change and evolution in the community goal.

The goal of the community can be interpreted differently by user preferences and the context of the environment. The goal of the community is not only a simple change from the perspective of this interpretation, but also a change in the components of the community or a change in the physical environment. Thus, the goal itself can be more intelligent and adaptive to the situation. In this case, since it does not develop in a completely different direction from the original community goal, it does not create a new community but forms an evolved community based on the existing community.

Second, change and evolution in the role of members.

Even if the purpose of the community is not changed, the role of members participating in the community may change according to the change of the configuration of the ubiquitous computing environment. As these member roles change, the community's procedures and policies can change as well, and the community evolves itself.

Community computing is a computing methodology that can be implemented by a number of community management systems that support community computing, or can be implemented by connecting to devices in the form of middleware, supported by community description languages, community compilers, and development environments. It can also be implemented as a development methodology.

The community management system uses message-based communication for context awareness and interaction among community members. The community is created when a service developer creates a community description and loads it into the system.

The community management system has user community information in the user group profile repository and can read and use the information from the repository when needed. In addition, personal information such as individual user preferences and schedule information is also stored separately in the repository to be used when setting a community goal or determining a community action.

The community management system is divided into mobile type and domain type. Only core components such as community monitor and goal interpreter and personal information repository are uploaded to mobile type community management system, service discovery including core components, device discovery, etc. Repositories, except components and personal information, are loaded into the domain type community management system.

The following scenario describes the mechanism for driving and maintaining a community with a community management system, the first approach.

The first relates to an autonomous media service scenario, and FIG. 4 is an exemplary diagram thereof.

Hereinafter, a situation in which a user receives a phone call while watching a media service in a living room and receives a telephone call and a media service without moving while moving to a bathroom will be described with reference to FIG. 4.

[1] As the user sits on the couch, the service community management system infers the user's situation with the current time and schedule information of the user and suggests viewing the media service. When a user wants to watch a media service, the service community management system retrieves user preference information and notifies the media service to play a particular media.

[2] The infrastructure community management system recommends the TV, which is the media playback device closest to the user's location, to the service community management system, and the media service is played on the TV. The follow me media community is activated by the media service playing situation.

[3] When a call comes in, the phone closest to your location rings.

[4] The service community management system recognizes that the phone rings by the sound sensor.

[5] The service community management system needs to add the phone service, the source of the sound source service, as a community member, identify the priorities of the two services, and lower the sound to the low-priority media services to resolve sound conflicts with the media services. Inform the situation.

[6] Media services lower the volume of the TV on which media is currently playing.

[7] As the user moves into the toilet and enters the toilet while talking on the phone, the location service notifies the user of the change of location, and the media service and the telephone service currently in service receive a notification message. It is recommended that the infrastructure community management system use magic mirrors, wireless microphones, and speakers for service among the devices managed by the toilet community.

[8] The media service continues to play media that was being played on the TV through a magic mirror capable of playing media in the bathroom, and the telephone service continues to support telephone service through wireless microphones and speakers in the bathroom.

In order to provide the above scenario services without applying the community computing method according to the present invention, each service must be newly developed intelligently to grasp user preferences and surrounding conditions and provide a service accordingly, and resolve conflicts between services. To do this, new integrated systems or collaboration services must be developed for each service scenario.

However, by applying community computing as in the above scenario, we provide differentiated services to users based on contextual collaboration between existing services, and are the most optimal device when the user's location changes without fixedly binding services and devices. You can select to allow the service to be dynamically bound. This makes it easy to develop complex, context-based services, support dynamic integration and collaboration, and resolve service conflicts that can occur within them.

The second relates to a healthcare scenario, and FIG. 5 is an exemplary diagram thereof.

Hereinafter, according to FIG. 5, a situation in which an emergency occurs in a user, contacts a hospital and family, cares for him, and configures an environment and a service to cope with an emergency will be described.

[1] The user is sitting on the living room sofa watching TV.

[2,3] When an abnormal signal is detected by the heart rate monitor, the heart rate detection service informs the care service of the situation.

[4] When the profile information of the family community and the health-care community is delivered to the infrastructure community management system, the network community device closest to the user's location by using the profile information is provided by the infrastructure community management system. To form a health care network.

[5] The care service informs the attending physician of the user's heart information.

[6] In response to an emergency, your doctor will set a schedule for your appointment as well as lying down with your medication.

[7] Appointment and care services tell this care.

[8] The care service tells the monitor of the grandson of the user in another room in the room to feed the medicine and to lie down comfortably. And the service community management system compares the location information and schedule of the son and daughter of the user and asks the daughter closest to the current user's location to go to the hospital at the scheduled time.

According to the community computing method according to the present invention, when a user has an emergency, based on the information of the user community to identify the location of the members and the equipment that can be contacted to form a health care network and inform them of the emergency Responding to emergencies can be made quickly based on situational information.

6 is a diagram illustrating the structure of a community computing system according to the present invention.

In order to implement the ubiquitous intelligent space, it is important for each device, system, and service that constitutes the space to operate intelligently in response to the user's context, but each distributed entity cooperates to provide efficient services to the user. It is also important.

The collaboration service may have different targets depending on the situation and surrounding environment of the user or the context of the user's characteristics and preferences, and the goals of the service may also vary.

In order to implement dynamic collaboration services that support service goals and adaptability of collaboration targets according to the mobility and environment of users, communities are defined as communities, which are highly abstracted layers, using metaphors of collaboration units. What is needed is a system that connects with the actual service collaboration flow of the space to provide services to users.

The development of this system allows individual users to receive complex services in real time, even in their own space, even when they are not aware of their preferences.

In addition, companies or organizations that provide services reuse existing services and simply describe to the community what services are to be collated when a specific situation is recognized. Can be combined to provide new services.

To provide context-aware complex services to users in a community computing environment, managers need to be able to create and manage communities in a context-sensitive manner. The manager must support interactions for each service application to achieve common service goals, be able to coordinate conflicts that may occur during the collaboration, and provide adaptive services based on user preferences. A manager that satisfies these functions is referred to as a community manager. Hereinafter, a community computing system including a community manager will be described.

The community computing system 600 of FIG. 6 is a community computing system defined as an autonomous collaboration model between entities existing in a highly distributed form in a ubiquitous computing environment, and includes a community manager 610, a situation manager 620, and a community. It includes a repository 630, a meta service repository 640, a situation rule repository 650, and a community framework 660.

FIG. 6 discloses a lookup table 680 and a service ontology repository 670 that store information about applications and members corresponding to objects for understanding the operation of the community computing system 600.

The community manager 610 manages service collaboration for providing an appropriate service to the user based on the situation information. The community manager 610 is composed of domain-specific and user-specific instances, and the mechanisms that operate in such an environment are as follows.

The context manager receives the contextual information, which is a collection of context data from the situation manager 620, sets a goal for a user service, and recruits members to achieve the goal through the community framework 660.

These groups of members are called communities, and member actions are requested and members are called through policy modules such as policy injectors and policy repositories until community goals are achieved. dynamic collaboration solutions such as call).

If the context information determines that the community's goal has been achieved, the community is destroyed or deactivated. The community manager 610 is classified into a mobile community manager mounted on a mobile device and a domain community manager mounted on a domain server according to personal service.

The mobile community manager is installed on a device that supports mobility and assumes that it always moves with the user, and the user profile repository (user information, preference job priority, known community manager list, etc.) It has a module for user profile repository and authentication.

Every time a user moves to a place, we find the domain community manager for that place and make adjustments to the list of services that can be serviced in that domain, the actions that should be served, and perform the service directly, or It can also be done through a community manager.

Domain Community Manager is a server program that supports services in a specific domain. It monitors the status information in the domain and stores the community that can be executed in the domain and the policies to be followed by each community.

It can also send community scripts to mobile community managers, perform community tasks, and provide monitoring of communities running in the domain.

The community, which is a unit of collaboration service, should be defined as an abstraction layer and described as a meta service so that it can be interpreted at runtime and transformed into a physical service. To this end, the community computing system 600 derives a conceptual model of the community and defines a language that can describe the community based on the community schema. It also includes a meta service repository 640 that predeclares and stores meta services to be referred to when describing a community in accordance with a defined community schema specification.

Describes community specifications.

Community consists of Goal, Activate Situations, Deactivate Situations, Members, Actions, and Policies. In other words, what constitutes a community is the goal and the conditions under which the community is activated and deactivated to achieve that goal, community members, community actions and policies.

Community and community purpose are mapped one-to-one, and this purpose is described as a description that can be interpreted differently by user preference information and surrounding situation.

The goal of a community is a temporary type that is fragmented according to the type and nature of the community and disappears after the goal is achieved.It is activated and operated in a specific situation, and then deactivated in a specific situation. There is also a persistent type.

These goal settings are the same as the levels of community behavior that can operate, so they should be subdivided and normalized to levels.

Situation refers to a combination of the states of the objects that make up the environment on a time basis. Environment objects include all users, services, and devices.

The member type may be a primitive type of user, service, or device according to the classification of the community, or may be a community of each of these groups. The member state is divided into two states, active and operating in the community, and inactive and waiting. The state is described as a specific instance according to the community class, and is described as a type by the required function rather than the instance name.

Actions are actions that a community should take and describe the state of community members based on context. It can be defined on a rule-based basis or can be defined in states and described as a planable structure.

Policies are classified into core and option types, and core type policies should be defined regardless of community type. Quality of Service (QoS), Security, User Preference are defined as policies.

At the time of describing the community, it is impossible to know which service is a member and what the interface of the service is. Therefore, the services are classified into types to predefine the meta service interface for each type, and the API (Application Program Interface) is applied. Program interface).

The meta service described in this way is replaced by the community manager at the runtime with the actual service instance. Meta service can be defined in various and huge amounts according to service classification method and service domain, so it is defined as Java interface and its semantics can be understood by referencing on web with Java API.

The existing service collaboration and integration consisted of static service discovery and service execution, but the collaboration target optimized to support the diversity and mobility of the environment inherent in the ubiquitous intelligent space where the community manager system will operate. In order to target the selection and execution of services, there is a need for a technology that discovers community members that are collaborative service targets dynamically at runtime, assigns roles to them, and delivers service execution goals through an interface that they can understand.

To this end, a community manager 610 is required to interpret the described community script, to dynamically construct a community at runtime, and to request the necessary actions with each interface and protocol used by services that are community members.

The composition of the community is made through interworking with the community framework 660 and middleware based on community scripts at runtime. The community framework 660 collects services using the discovery function of the middleware and recommends them as members to the community manager 610 through inspection and negotiation as to whether these services are suitable for constraints as community members.

The community script specifies the types and constraints for the members to be configured, and the currently defined constraints are specified in the community schema.

The protocol used when requesting the recommendation of a community member to the community framework 660 uses an xml message whose key value is "service type (service_type)". The community framework 660 collects the lookup table of the middleware and has its own service table, and knows what service type (service_type) each of the services is based on the collected services.

The service lookup protocol also allows for the inclusion of "constraints". This section is a collection of community policies described in the individual community scripts, organized as "constraints," and includes the "closest to user's location" and "security level 3 or higher" policies. Etc. It contains the restrictions that a community member must have.

Therefore, when constructing a community, the members' selection criteria are "service_type" and "constraints", and the community framework 660 recommends the members to form the community, and the community script It converts the described service flow to the interface of the configured members.

Community scripts described as meta-services must be interpreted at runtime and mapped to physical services. To this end, the context of the individual, which is a key factor in determining community member composition and service goals, is built into the OWL (Ontology Web Language) repository using the protease and changed into a Resource Description Framework (RDF) file. Query by using Jena Java API. This structure ensures that all variables beginning with '$' in community scripts are replaced with specific values, and that you understand the semantics of interpreting the service's goals and the interface of the service.

As shown in FIG. 7, when the community manager 710 or 720 receives a status message from the situation manager 730, the community execution mechanism requests a configuration of a specific community in comparison with the status message of the loading community script. It will execute the member's action request.

The execution of a community may be related to community members such as requesting specific actions to members of the service or delivering information, and the community manager 730 manages the state of each community, generates its own timer, and performs specific actions. There are two types of community manager 730 directly involved.

Looking at the order in which the communities are executed, as shown in FIG. 8 below, the Community Loader loads and interprets the community scripts and passes them to the Community Organizer to configure the community with the help of the community framework 660. do.

In this process, scripts about the goals of the community and how to run the service are interpreted and changed according to the configured members, that is, the interfaces of the actual services, and each community is driven and operated by Java's thread object.

The situation message received from the situation manager 620 is heard by each community thread through the situation listener (Situation Listener), and when the message is related to the operation of the community, the message is operated according to the interpreted community action. For example, if the message received is a trigger message that requires an action of a member with a specific role in the community, the action is delivered to the member. In this process, the community framework 660 performs the transfer to the protocol that the member can understand.

The above description is merely illustrative of the technical idea of the present invention, and various modifications, changes, and substitutions may be made by those skilled in the art without departing from the essential characteristics of the present invention. will be. Accordingly, the embodiments disclosed in the present invention and the accompanying drawings are not intended to limit the technical spirit of the present invention, but to describe the present invention, and the scope of the technical idea of the present invention is limited by the embodiments and the accompanying drawings. no. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

As described above, the advantages obtained by the community computing method according to the present invention are as follows.

First, collaboration and heterogeneous dimensions are possible. The heterogeneous nature of the objects in the ubiquitous computing environment requires the integration and collaboration of various dimensions. That is, when a specific service is provided to the user, the services should be able to integrate and collaborate harmoniously based on the situation of the user, the interaction between the users, and the context information of the surrounding devices and the network. Community computing can easily derive the organic combination of heterogeneous dimensions in the ubiquitous computing environment by integrating the 'community' model in humanities sociology.

Second, encapsulation and abstraction of various information becomes possible. Community computing addresses various issues such as user privacy issues, collaborations between moving services, policies about service priorities, and conflicting user preferences that can be caused by the mobility and short-term nature of the ubiquitous computing environment. policy, and encapsulate it in a community encapsulated. In addition, in a ubiquitous computing environment, it should be possible to provide services based on situation-aware, where community summarization (encapsulation-disclosure of information between members) This can be solved with encapsulation because transparency and awareness can be harmonized because it is only disclosed within the community according to the level of authentication and trust.

Third, the problem of reuse is solved. Behind the evolution of the software development paradigm, the element of reuse is a big part. Although this unit of reuse has been gradually evolved into simple modules, objects, components, and services, these models have been insufficient to solve the new features of the ubiquitous computing environment. Community computing treats the unit of reuse as a community that incorporates collaboration and contextual awareness, which allows software developers to create new services in a ubiquitous computing environment, using community description language to describe the community to develop new composite services. It is also easy to reuse.

Fourth, real-time decision-making (dynamic reconfiguration) is possible. By describing communities in concrete logic, communities can be configured in real time and entities can be recruited to community members in a variety of ways (and can be recruited, their roles and actions are dynamically determined).

Fifth, community context sharing becomes possible. The use of the metacommunity context model when describing communities and community members enables domain consolidation at the context level, enabling the same context understanding and sharing between community members or between communities. Community computing meets the above, which is the basic condition for ubiquitous entities to have intelligence.

Other effects of the present invention, as well as those described in the above-described embodiments and claims of the present invention, as well as potential effects that may occur within the range that can be easily estimated therefrom and potential advantages that contribute to industrial development It will be added that it will be covered by a wider scope.

Claims (18)

A community forming step of defining a purpose, a policy, a member, an operation of members, a community operating situation, a community dormant situation, and the like to form a community; Waiting for a time for the community to form and operate an actual community member after the community forming step; A community operation step in which the community monitors the status information after the community waiting step and then activates itself to start an operation when the community operation status is reached; A community dormant step in which the community temporarily stops operation on its own and waits for the next community operation step when the community meets the purpose of the community or sleeps after the community operation step; And Termination phase of the community to end all actions on its own if the community no longer needs to operate Community computing method comprising a. The method of claim 1, The community is an autonomous collaboration model between entities that exist in a highly distributed form in a ubiquitous computing environment. Community Goals Department, which contains the final goals the community should achieve; A community skin unit encapsulating a community to support information hiding for privacy protection and security in a computing environment in which too much information can be disclosed, and to reuse complex services defined in community units; A community policy unit that is connected to the community as a set of policies for functions of the community itself and supports the operation of the community; A community member unit that is tied together as a community and cooperates with each other to achieve a final goal pursued by the community; And Community action unit that provides a context-based action that the community member should take in order to achieve the purpose of the community Community computing method comprising a. The method according to claim 1 or 2, The community A service community comprising a web member, an application, an agent service, and the like, wherein the web service, an application, and an agent service constitute a community member and enable collaboration between services to support a complex service based on community user preferences and surroundings; The network devices and devices constituting the infrastructure constitute a community member unit, create a device group based on location to support resource management, error recovery, quality management, etc., and propose an appropriate device to the service community. An infrastructure community that serves to construct a service-oriented community for the proper operation of the service community; And Real users such as family members, coworkers, etc. constitute community members and manage profiles of user group reliability, group work, etc. to derive user requirements for the service community and the infrastructure community. community Community computing method characterized in that divided into. The method of claim 3, wherein The infrastructure community is a community computing method characterized in that there exist two types of location-based community (service-oriented community). The method of claim 2, The purpose of the community is A method of community computing, characterized in that it has a permanent type of purpose, which is activated and operated in a specific situation and then continues to be deactivated in a specific situation. The method of claim 2, The purpose of the community is A community computing method, characterized in that it has a temporary type of purpose that is created fragmentally and then disappears after accomplishing the purpose. The method of claim 2, The community member unit, A community computing method, wherein a user, a service, an infrastructure, etc. become an entity, or a community that is a group of each of them becomes another entity. The method according to claim 1 or 2, Community computing method characterized by changing and evolving by learning in the process of the community is activated to achieve the purpose of the community. The method of claim 1, The community termination step, Community computing method, characterized in that the community is at the stage of fulfilling its own fate and completely die. The method of claim 1, The community termination step, And a community staying dormant for a long time without dying. The method of claim 1, When the service type provided to the user by the community is a one-time service, the community has sequentially gone through the community forming step, the community waiting step, the community operation step, and the community dormancy step, and then immediately goes to the community termination step. Community computing method characterized in that to provide a service on the go. The method of claim 1, When the service type provided to the user by the community must be repeatedly provided in a specific situation (or a request point) such as a media service or in the background such as a security service, but is not a one-time service such as when operating in a specific situation, After the community has passed through the community forming step and the waiting for the community, it enters the community operation phase when the specific situation ends. When the specific situation ends, the community enters the dormancy phase. When another specific situation occurs, the community operation step is repeatedly performed. Community computing method characterized in that to provide a service as it enters. In a community computing system defined as an autonomous collaboration model between entities that exist in a highly distributed form in a ubiquitous computing environment, A community manager that sets goals for services and manages service collaboration to provide appropriate services to users based on contextual information; A situation rule repository for storing rules applied for respective situations; A situation manager which obtains the situation information, which is a collection of context data from the situation rule repository, and provides the situation information to the community manager; A community repository that stores a description of the community and provides it to the community manager; A meta service repository that classifies services into types and defines and stores interfaces for each type; And And a community framework for identifying and connecting members to the community manager to refer to the meta service repository. The method of claim 13, wherein the community manager, Community computing system, characterized in that divided into a mobile community manager mounted on a mobile device and a domain community manager mounted on a domain server. The method of claim 14, wherein the mobile community manager, And a user profile repository and authentication module mounted on a device supporting mobility and having user information, preferences, priorities, and known community manager list information. The method of claim 14, wherein the domain community manager, Community computing system, characterized in that the server program that supports services in a specific domain. The method of claim 13, wherein the meta service repository, And predeclaring and storing meta services to be referred to when describing a community in accordance with a specification of a community schema, which is a language capable of describing the community. The method of claim 13, wherein the community manager, A situation observer that monitors the situation information transmitted from the situation manager and checks whether it is identical to a trigger situation of a community; A community organizer that loads community scripts at runtime to interpret communities and organize members; A runnable community that controls the execution and state management of the configured community; And And a context converter for converting a service execution message described as a meta service into a message understandable by the corresponding service and transmitting the converted message to the community framework.

Images