KR20160077516A - System, method and computer program for supporting business based on social information of users - Google Patents

System, method and computer program for supporting business based on social information of users Download PDF

Info

Publication number
KR20160077516A
KR20160077516A KR1020140187316A KR20140187316A KR20160077516A KR 20160077516 A KR20160077516 A KR 20160077516A KR 1020140187316 A KR1020140187316 A KR 1020140187316A KR 20140187316 A KR20140187316 A KR 20140187316A KR 20160077516 A KR20160077516 A KR 20160077516A
Authority
KR
South Korea
Prior art keywords
user
information
users
relationship
identifier
Prior art date
Application number
KR1020140187316A
Other languages
Korean (ko)
Inventor
윤완수
박승현
Original Assignee
마드라스체크 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 마드라스체크 주식회사 filed Critical 마드라스체크 주식회사
Priority to KR1020140187316A priority Critical patent/KR20160077516A/en
Publication of KR20160077516A publication Critical patent/KR20160077516A/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources

Abstract

A system to support a work based on social networking information according to an embodiment of the present invention comprises: a member management module configured to generate each user identifier of a plurality of users based on a plurality of pre-registered user information; and a work support module configured to generate a relation identifier between users based on the user information or the information inputted by the users and perform operation corresponding to a request received from a user. The system to support a work according to the present invention is capable of making connections and communications between users in different organizations when users perform tasks and improving work efficiency by generating relation information connecting each user to at least one other user based on affiliations or contact information, etc of the users and making the users perform work based on the networking information.

Description

TECHNICAL FIELD [0001] The present invention relates to a business support system, a method, and a computer program based on user relationship information.

Embodiments are directed to a business support system, method, and computer program based on user relationship information, and more particularly, to a business support system, method, and computer program based on user relationship information, and more particularly to a business support system based on relationship information that associates each user with another user, Systems, methods, and computer programs.

As computers are being used for information, almost all companies are currently performing business operations using a groupware application installed on an enterprise server. By utilizing functions such as e-mail, in-house bulletin board, and electronic approval executed using the groupware application, a variety of business processes required by the corporation and business connection between the employees can be accomplished through the computer.

However, the conventional groupware application is executed based on the client-server network environment in the enterprise. That is, a groupware application is installed in one or a plurality of servers in the enterprise, and it is possible for only the employees in the same company to perform business processing through the groupware application. On the other hand, personal relationships such as customer or customer contacts held by the company's employees are entirely under the individual management of the employee, and there has been no means to utilize or manage such personal relationships at the enterprise level. For example, when a particular employee moves or leaves a department, information about the employee's personal relationship is lost, which can cause inconvenience to the business.

Published Patent Publication No. 2001-0055928

According to an aspect of the present invention, there is provided a business support system and method for supporting a user's work by operating based on relationship information that associates each user with another user based on a user's contact or affiliation, and a computer program Can be provided.

The business support system according to an embodiment includes a member management module configured to generate a user identifier of each of a plurality of users based on a plurality of user information registered in advance; And a task support module configured to generate a relationship identifier between users based on the user information or information input by the user and to perform an operation corresponding to the request received from the user using the relationship identifier .

In one embodiment, the business support module includes: a relationship information generation unit configured to generate the relationship identifier by referring to the member management module; And an application execution unit configured to execute an application that performs the operation using one or more other user identifiers associated with the user by the relationship identifier. At this time, the application executing unit may be further configured to execute a plurality of applications that can share data with each other through an application programming interface (API).

In one embodiment, the user information includes a user's belonging information, and the relationship information creating unit is configured to generate the relationship identifier associating users belonging to the same corporation.

In one embodiment, the relationship information generation unit is configured to receive contact information from each user and to generate the relationship identifier associating each user with one or more other users included in the contact information of each user.

Further, in one embodiment, the user information includes user's belonging information, and the relation information generating unit associates users belonging to the related companies with each other using the predetermined association information between the companies to which each user belongs To generate the relationship identifier.

In one embodiment, the business support is further configured to present to the user a list of one or more other users associated with the user by the relationship identifier.

According to an embodiment of the present invention, there is provided a business support method comprising: generating a user identifier of each of a plurality of users based on a plurality of pieces of user information registered in advance in a business support system; Wherein the business support system comprises: generating a relationship identifier between users based on the user information or information input by the user; And performing an action corresponding to the request using the one or more other user identifiers associated with the user by the relationship identifier, in response to a request received from the user to the business support system.

In one embodiment, performing an action corresponding to the request includes executing an application that performs the action using the one or more other user identifiers associated with the user by the relationship identifier. At this time, the step of executing the application may include executing a plurality of applications that can share data with each other through an application programming interface.

In one embodiment, the user information includes a user's belonging information, and the step of generating the relationship identifier includes generating the relationship identifier associating users belonging to the same corporation.

In one embodiment, the step of generating the relationship identifier further comprises: receiving contact information from each user; And generating the relationship identifier associating each user with one or more other users included in the contact information of each user.

Further, in one embodiment, the user information includes the user's belonging information, and the step of generating the relationship identifier includes: using a predetermined association information between the users to which each user belongs, Lt; RTI ID = 0.0 > relational < / RTI >

In one embodiment, performing an action corresponding to the request includes presenting to the user a list of one or more other users associated with the user by the relationship identifier.

A computer program according to one embodiment is for execution of the business support method in combination with hardware, and may be stored in a medium.

According to an aspect of the present invention, there is provided a system and method for supporting a business, which generates relationship information associating each user with one or more other users based on a user's affiliation or a contact, and the user performs business based on the relationship information can do. Accordingly, when a plurality of users belonging to different companies perform tasks, connection and communication between users can be facilitated and work efficiency can be improved.

1 is a schematic configuration diagram of a business support system according to an embodiment.
2 is a schematic flowchart illustrating a method of supporting a business according to an exemplary embodiment.
3 is a conceptual diagram illustrating an operation of a business support system according to an embodiment.
FIG. 4 is a conceptual diagram for explaining how work performed between users belonging to different user organizations is performed using a business support system according to an embodiment.

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

1 is a schematic configuration diagram of a business support system according to an embodiment.

Referring to FIG. 1, the business support system 3 according to the present embodiment includes a member management module 10 and a business support module 20. The business support system according to the embodiments may be entirely hardware, or may be partially hardware, and partially software. For example, the business support system 3 and each unit, module, or server included therein may be collectively referred to as a device for sending and receiving data of a specific format and contents by an electronic communication method and software related thereto. The terms "part", "module", "device", "terminal", or "server" are used herein to refer to a combination of hardware and software driven by that hardware. For example, the hardware may be a data processing device comprising a CPU or other processor. Also, the software driven by the hardware may refer to a running process, an object, an executable, a thread of execution, a program, and the like.

The membership management module 10 and the business support module 20 are configured to operate in communication with one or more user terminals 1 via a wired and / or wireless network 2. [ The communication method between each module and the user terminal 1 may include all communication methods that the object and the object can network, and is not limited to wired communication, wireless communication, 3G, 4G, or other methods. For example, the business support system and the user terminal 1 may be connected to a wireless LAN (Local Area Network), a MAN (Metropolitan Area Network), a GSM (Global System for Mobile Network), EDGE (Enhanced Data GSM Environment), HSDPA Downlink Packet Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Zigbee, Wi- , Voice over Internet Protocol (VoIP), LTE Advanced, IEEE 802.16m, WirelessMAN-Advanced, HSPA +, 3GPP Long Term Evolution (LTE), Mobile WiMAX (IEEE 802.16e), UMB Communication using at least one communication method selected from the group consisting of OFDM, iBurst and MBWA (IEEE 802.20) systems, HIPERMAN, Beam-Division Multiple Access (BDMA), Wi-MAX (World Interoperability for Microwave Access) But is not limited thereto.

The user terminal 1 refers to a device used by a user to use the business support system 3. For example, the user terminal 1 may be a mobile communication terminal such as a smart phone, a personal computer, a notebook computer, a personal digital assistant (PDA), a tablet, an Internet Protocol Television (IPTV) , But is not limited to, a set-top box. It should be understood that the number of user terminals 1 shown in the figures is merely exemplary and does not limit the number of terminals or users actually operable with respect to the business support system 3.

The user can be provided with the service by the business support system 3 by accessing the business support system 3 by using the user terminal 1. [ For example, the user accesses a predetermined web page provided by the business support system 3 and executes a web application (also referred to as an app) System 3 can be used. The term web application as used herein refers to any software configured to at least partially utilize the communication with the user terminal 1 to provide services to the user of the user terminal 1. [ The web application may be implemented in a language such as Hyper Text Markup Language (HTML), Extensible Markup Language (XML), or JavaScript Object Notation (JSON), and may be executable through a web browser.

The member management module 10 is a part in which information of users using the business support system 3 is stored in a database. The business support system 3 according to the embodiments is configured not to limit the function to the inside of the enterprise like the conventional groupware but to be able to link business inside and outside the company. A plurality of users belonging to different companies can subscribe to the business support system 3, and the information of the subscribed users is stored in the member management module 10. [ In this specification, an enterprise refers to any organization that can group users into one or more groups according to their affiliation, and does not necessarily mean a commercial enterprise alone.

The business support module 20 is a part for performing an operation for business support in response to a user's request received from the user terminal 1. [ In the embodiments, the business support module 20 is configured to perform an operation based on relationship information associating each user with another user, so that various users belonging to various companies perform connection and communication with other users So that it can be easily carried out. In one embodiment, the business support module 20 may perform the operations described above in the form of a web application executed by a user's operation. In this case, the business support module 20 may be configured to allow the user terminal 1 to communicate with the application server 4 in response to the web application execution request, Lt; RTI ID = 0.0 > and / or < / RTI >

Further, the business support module 20 may be implemented in the form of a plurality of web applications. In this case, at least a part of the application programming interface (API) of each web application is known, and the application is configured to access data of the application by using the API in another application. Where access may include accessing the associated application server 4 via the application. By this data sharing, the relationship information generated in association with one application can be utilized in another application, so that connection and communication between users through the application can be facilitated.

In one embodiment, the business support module 20 includes a relationship information generation unit 210 and an application execution unit 220. The relationship information generation unit 210 generates relationship information associating each user with another user based on user information registered in the member management module 10 and / or information additionally input by the user. The application execution unit 220 executes one or more applications that operate using the relationship information generated by the relationship information generation unit 210. [ By using an application executed using the relationship information, the user can easily carry out tasks accompanied by designation, participation, or response of another user. This will be described in detail later.

The operation performed by the application executing unit 220 in the business support system 3 according to the embodiments of the present invention may be sufficient to at least partially utilize the relationship information between the users and is not limited to a specific operation Do not. For example, the operations performed by the applications of the application execution unit 220 may include browsing, sending or receiving data such as messages, e-mails, invoices or reports, managing business schedules, But may not be limited to, financials such as risk monitoring (CRMS), electronic payment, and proof of purchase / sale or slip processing.

2 is a schematic flowchart illustrating a method of supporting a business according to an exemplary embodiment. 1 and 2, a system and method for supporting a business according to embodiments will be described in detail.

First, the member management module 10 of the business support system 3 can receive and register user information of users who want to use the business support system 3 (S1). The user information may include a name, an ID, an e-mail address, a telephone number, belonging information of each user, and the authority indicated by the user. The affiliation information may include a company name to which each user belongs, a corporation or business registration number corresponding to the corporation, a department name to which the user belongs within the company, and the like. However, this is an exemplary one, and the form of the user information is not limited to that described above and can be appropriately determined according to an operation to be performed using the business support system 3.

Next, the member management module 10 can generate a user identifier (or a key) corresponding to each user who has received the information (S2). The user identifier is generated so as to be different depending on the user, as information used for specifying each user in the application provided by the future business support system 3. For example, the user identifier may be binary data of several to several tens of bytes in size, but is not limited thereto.

The relationship information generation unit 210 of the business support module 20 may generate a relation identifier (or key) between users based on the above-described user information and / or the additional information input by the user (S3) .

In one embodiment, the relationship identifier may be for identifying users belonging to the same enterprise. The user information of each user may include company information of the user, and the relationship information generation unit 210 may generate a relationship identifier that associates users belonging to the same company with each other.

In another embodiment, the relationship identifier may be for identifying other users belonging to each user's contact. The business contact information held by each employee of an enterprise is not the ownership of the individual employee but the business assets of the enterprise. In order to utilize such contact information in business and not to lose contact information even when the employee moves or retires, the relationship information generation unit 210 receives information of one or more other users to be registered in the contact of the user from the user . Next, the relationship information generation unit 210 may generate a relationship identifier such that the corresponding user is associated with another user registered in the contact by the corresponding user.

At this time, the relationship identifier that associates users by the contact may have two or more forms. For example, the type of the relationship identifier can be determined so that only one of two users associated with each other registers a different user in the contact, and when two users register each other in the contact. Alternatively, each user may categorize the contacts they register with one or more labels, and may specify other users or user rights to share the contacts with these labels. For example, each user can share his / her contact with the manager of the company or all other employees belonging to the same company by designating his / her contact as a shared contact.

In another embodiment, the relationship identifier may be for identifying users belonging to an enterprise associated with each other. To this end, association information between companies may be stored in the relationship information generation unit 210 in advance. In this case, the related information refers to the fact that one company is in a transaction relationship with another company, and may be input manually or automatically generated using companies that have purchased and sold each other based on an electronic tax bill of the National Tax Service have. At this time, the relationship information generation unit 210 may generate the relationship identifier so that the relation user associates a specific user with a user belonging to another business in a business relationship with a job to which the specific user belongs.

The embodiments described above are configured to generate a relationship identifier between users based on each company's affiliation, a contact registered by each user, and a business relationship between a company to which each user belongs and another company. This relationship identifier may be generated in advance by the business support system 3, or may be generated when the user first attempts to execute the application. In addition, the above-mentioned three kinds of relationship identifiers may be used in one application, or may be used in each separate application. Furthermore, the form of the relationship identifier described above is merely exemplary, and the relationship identifier is not limited to a specific form as long as it can associate the user with another user using the user information or the information input by the user.

Next, the business support module 20 may receive an application execution request from the user terminal 1 (S4). The application for which execution is requested may be for performing any operation related to the user's work and the user may request execution thereof by selecting any one of the applications having various functions provided by the business support module 20 . Although an execution request (S4) of an application is shown in the drawing after the relation identifier generation (S3), this is an example, and the relation identifier may be generated when the execution of the application is first requested as described above. Also, depending on the embodiment, the relationship identifier may be configured to be updated at regular intervals and / or every time the application is executed.

Next, the application executing unit 220 can perform the operation requested by the user by executing the application at least partially using the relation identifier generated in the step S3 (S5). In one embodiment, performing (S5) the operation may involve presenting to the user a list of one or more other users associated by the relationship identifier and the user requesting execution of the application. The user can designate one or more other users associated with his / her work in the presented list as a target person, a participant, an approver, a resolver, etc., and process the work.

As an example, the application provided by the business support system 3 may be an application for sending a message to another user. At this time, the user can select the recipient of the message by using the list of other users related to him by the relationship identifier. The list of other users provided in the list may vary according to the type of relationship identifier. For example, a user may select one or more recipients of other employees belonging to the same company. Alternatively, the user may select one or more recipients from contact information registered by the user or contact information registered by another employee of the same company as a shared contact. Furthermore, the user may select one or more recipients from the contact information of other companies in the business relationship with the company to which the user belongs.

As another example, an application provided by the business support system 3 may be an application for creating a schedule or a meeting and sharing information. At this time, the user can specify another attendee related to the schedule or the meeting by using the list of other users related to the user by the relationship identifier. For example, one or more of the other employees in the same company can be selected as the attendee. Alternatively, the user may select one or more attendees from contact information registered by the user or contact information registered by another employee of the same company as a shared contact. Further, the user may select one or more attendees from the contact information of another company in the business relationship with the company to which the user belongs.

3 is a conceptual diagram illustrating an operation of a business support system according to an embodiment.

Referring to FIG. 3, in the business support system according to the present embodiment, an employee application, a contact application, and a client application can be provided by the business support module 20 operating based on the member management module 10. An employee app can generate and act on a relationship identifier that associates users belonging to the same enterprise. The contact app also generates a relationship identifier that associates users based on the contact information received from each user, and can operate based on the relationship identifier. Further, the customer-facing application can generate a relationship identifier that associates users belonging to the related company with each other using the association information between the companies to which the user belongs, and can operate based on the relationship identifier.

The relationship information between the users, which is managed by the displayed employee, contact, and each app of the customer, is configured to be accessed and used by one or more other apps. Further, each of the employees, contacts, and accounts of the customer may share data with one or more other applications (i.e., App 1, App 2, App 3, and App 4) provided by a separate server (e.g., application server 4) .

As a result, between different users (i.e., user 1, user 2) belonging to different use organizations (i.e., user 1, user 2) as shown in FIG. 4, Communication and business cooperation can be achieved by using an application based on the Internet. The app at this time may be an app of each of the employees, contacts, and customers shown in Fig. 3, or may be another app operated at least partially by using these apps.

The number of each of the apps, the user, and the use agencies shown in FIG. 3 and FIG. 4 is only for explaining an application form of the business support system according to the present embodiment, It should be understood that the present invention is not limited to the number of apps to be used or the number of users or use agencies that use the business support system according to the present embodiment.

It should also be noted that the forms of use described above are exemplary only and that the type of application (or app) that can be executed using the relationship information between users is not limited to what is described herein, A variety of existing or future developments, such as viewing, transmitting or receiving the same data, managing business schedules, managing the employees' infrastructure, managing risk at all times, financial affairs such as electronic payment, The application may be configured to operate using relationship information between users, which is within the scope of the present invention.

According to the business support system and method according to the embodiments described above, it is possible to generate relationship information that associates each user with one or more other users based on a user's affiliation, a contact, and the like, Can be performed. Accordingly, when a plurality of users belonging to different companies perform tasks, connection and communication between users can be facilitated and work efficiency can be improved.

The operation according to the business support method according to the embodiments described above can be at least partially implemented in a computer program and recorded in a computer-readable recording medium. A computer-readable recording medium on which a program for implementing a business support method according to embodiments is recorded includes all kinds of recording apparatuses in which data that can be read by a computer is stored. Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and a carrier wave (for example, And the like. The computer readable recording medium may also be distributed over a networked computer system so that computer readable code is stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing the present embodiment may be easily understood by those skilled in the art to which this embodiment belongs.

While the invention has been shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. However, it should be understood that such modifications are within the technical scope of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

Claims (15)

A member management module configured to generate a user identifier of each of a plurality of users based on a plurality of user information registered in advance; And
A task support module configured to generate a relationship identifier between users based on the user information or information input by the user and to perform an operation corresponding to the request received from the user using the relationship identifier Support system.
The method according to claim 1,
The business support module,
A relationship information generation unit configured to generate the relation identifier by referring to the member management module; And
And an application executor configured to execute an application that performs the operation using one or more other user identifiers associated with the user by the relationship identifier.
3. The method of claim 2,
Wherein the application execution unit is further configured to execute a plurality of applications capable of sharing data with each other via an application programming interface.
The method according to claim 1,
The user information includes user's belonging information,
Wherein the relationship information generation unit is configured to generate the relationship identifier associating users belonging to the same corporation.
The method according to claim 1,
Wherein the relationship information generating unit is configured to receive contact information from each user and to generate the relationship identifier associating each user with one or more other users included in the contact information of each user.
The method according to claim 1,
The user information includes user's belonging information,
Wherein the relationship information generation unit is configured to generate the relationship identifier that associates users belonging to a corporation that are related to each other by using preset association information between the companies to which each user belongs.
The method according to claim 1,
Wherein the business support further comprises a list of one or more other users associated with the user by the relationship identifier.
Generating a user identifier of each of a plurality of users based on a plurality of pieces of user information registered in advance in a business support system;
Wherein the business support system comprises: generating a relationship identifier between users based on the user information or information input by the user; And
And performing, in response to a request received from the user from the service support system, an operation corresponding to the request using one or more other user identifiers associated with the user by the relationship identifier.
9. The method of claim 8,
The step of performing an operation corresponding to the request comprises:
And executing an application that performs the operation using one or more other user identifiers associated with the user by the relationship identifier.
10. The method of claim 9,
Wherein executing the application comprises executing a plurality of applications capable of sharing data with each other via an application programming interface.
9. The method of claim 8,
The user information includes user's belonging information,
Wherein generating the relationship identifier comprises generating the relationship identifier that associates users belonging to the same enterprise.
9. The method of claim 8,
Wherein the generating of the relationship identifier comprises:
Receiving contact information from each user; And
And generating the relationship identifier associating each user with one or more other users included in the contact information of each user.
9. The method of claim 8,
The user information includes user's belonging information,
Wherein the step of generating the relationship identifier comprises the step of generating the relationship identifier associating users belonging to the corporations related to each other by using preset association information between the companies to which each user belongs .
9. The method of claim 8,
Wherein performing the action corresponding to the request comprises presenting to the user a list of one or more other users associated with the user by the relationship identifier.
Combined with hardware,
Generating a user identifier for each of a plurality of users based on a plurality of pre-registered user information;
Generating a relationship identifier between users based on the user information or information input by a user; And
Executing in response to a request received from a user, an action corresponding to the request using the one or more other user identifiers associated with the user by the relationship identifier.
KR1020140187316A 2014-12-23 2014-12-23 System, method and computer program for supporting business based on social information of users KR20160077516A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020140187316A KR20160077516A (en) 2014-12-23 2014-12-23 System, method and computer program for supporting business based on social information of users

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020140187316A KR20160077516A (en) 2014-12-23 2014-12-23 System, method and computer program for supporting business based on social information of users

Publications (1)

Publication Number Publication Date
KR20160077516A true KR20160077516A (en) 2016-07-04

Family

ID=56500954

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020140187316A KR20160077516A (en) 2014-12-23 2014-12-23 System, method and computer program for supporting business based on social information of users

Country Status (1)

Country Link
KR (1) KR20160077516A (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010055928A (en) 1999-12-13 2001-07-04 이계철 Method for providing groupware application which is to support flexible bussiness management system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010055928A (en) 1999-12-13 2001-07-04 이계철 Method for providing groupware application which is to support flexible bussiness management system

Similar Documents

Publication Publication Date Title
US11223493B2 (en) Method, apparatus and computer program product for generating externally shared communication channels
US20210266278A1 (en) Method, apparatus, and computer program product for determining access control parameter discrepancies in group-based communication channels with a group-based communication system
US11050804B2 (en) Servicing group-based communication workspace add requests within a group-based communication system
CN110570166A (en) News feed technology
CN107181755B (en) Identity recognition method, device and system for office platform
US11750539B2 (en) Method, apparatus, and computer program product for generating an electronic announcement for display in a group-based communication interface
US10171408B2 (en) Following/subscribing for productivity applications
CN106470150B (en) Relation chain storage method and device
US20210149688A1 (en) Systems and methods for implementing external application functionality into a workflow facilitated by a group-based communication system
US11863640B2 (en) System, method, and apparatus for generating a third-party resource usage map in a group based communication system
KR101464448B1 (en) System and method for transmitting group message by using chatting application
US8843587B2 (en) Retrieving availability information from published calendars
CN111181833B (en) Enterprise interconnection realization method and device
KR101695325B1 (en) System, method and computer program for sharing and notifying schedule to proceed effective meeting
CN110769056A (en) Real-name system information processing method and device, electronic equipment and storage medium
US11159476B1 (en) Methods and apparatuses for managing data integration between an external email resource and a group-based communication system
KR20160077516A (en) System, method and computer program for supporting business based on social information of users
KR20160077517A (en) System, method and computer program for supporting cooperation
US20220335164A1 (en) Enhancing user identification with privacy protection across web servers
WO2020113162A1 (en) Method, apparatus and computer program product for generating externally shared communication channels
KR20170085624A (en) Server for contacts management, system comprising the same and method for recommending contacts
WO2011103665A1 (en) System, method and apparatus for managing electronic content

Legal Events

Date Code Title Description
A201 Request for examination
N231 Notification of change of applicant
E902 Notification of reason for refusal
E902 Notification of reason for refusal
E601 Decision to refuse application