KR20150109790A - Sever, terminal and method for supporting ship building information sharing - Google Patents

Abstract

The present invention relates to a server, a terminal, and a method for supporting the sharing of information related to a ship building between workers in the ship building. According to one embodiment of the present invention, provided is the method for supporting the sharing of the ship building information in a terminal which includes the steps of: receiving information about at least one chatting room to be copied from a user; and transmitting a chatting room copy request message including the information about at least one chatting room to the server. Each chatting room corresponds to at least one plan. The ship building information related to at least one corresponding plan with regard to at least one chatting room is stored in a ship building information database connected to the server.

Description

TECHNICAL FIELD [0001] The present invention relates to a server, a terminal, and a method for supporting ship building information sharing,

More particularly, the present invention relates to a server, a terminal, and a method for supporting sharing of information related to ship building between operators during construction of a ship.

Generally, in order to produce a specific object such as a vehicle, a ship, or an aircraft, it is necessary to design a drawing for the specific object, to produce each part shown in the design drawing, , One completed vehicle, ship, aircraft, and so on. At this time, the design drawing is designed by the drawing designer, and the operator produces or assembles the parts based on this design drawing.

In particular, the shipbuilding industry is a typical order-taking industry, and the ship's functions and appearance change according to the demands of ship owners. Each ship owner determines the function of the ship in consideration of the position and purpose of input of the ship, so that the same ship does not exist. However, in the case of a series ship on which several identical vessels are commissioned by the shipowner, several vessels of the same type are built. Such series vessels may be dried at the same time, but may be dried at intervals in time. That is, one can dry out after months or even years.

Conventionally, various drawings of ship were written in the form of computer file such as paper or PDF and distributed to related workers. According to this conventional technique, it is difficult to grasp whether the request of the ship is properly reflected or not, and it is difficult to manage the history of the events occurring during ship construction. Moreover, it is difficult to record various phenomena that are difficult to express in text.

Especially, in case of building a series ship, it is difficult to grasp the error of the ship which was built first, requests for reflection, change of the construction method, and change of the process.

Prior Art: Korean Registered Patent No. 10-0854672 (registered on Aug. 21, 2008)

An object of the present invention is to provide a server and a terminal capable of managing a history of events occurring during shipbuilding, grasping whether requests are reflected or not, sharing ship building information capable of copying chat rooms between lines, And a method thereof.

According to an aspect of the present invention, there is provided a method of supporting ship building information sharing in a terminal, the method comprising: receiving information about at least one chat room desired to be copied from a user; Sending a chat room copy request message containing information about the at least one chat room to a server, wherein each of the at least one chat room corresponds to at least one drawing, Wherein the ship building information associated with at least one of the drawings is stored in a ship building information database connected to the server.

In particular, the information about the at least one chat room includes a source call number, a target call number, the source call number indicates a call number corresponding to at least one chat room for which the copy is desired, It may mean the line number of the target line to which the chat room containing the same information as the one chat room is to be generated.

Further, the ship building information includes the number of the at least one drawing and the line number of the line that is the subject of the at least one drawing, the drawing number includes the line number, Wherein upon receipt of the request message, for each of the at least one chat room, a call number portion of the drawing number is replaced by the target call number, the call number is replaced by the target call number, The information can create the same chat room.

The method for supporting sharing of ship building information includes receiving a search condition for searching history information of an event generated in the ship building information database from the user; Transmitting a history inquiry request message including the search condition to the server; Receiving history information corresponding to the search condition from the server; And displaying the history information.

In addition, the search condition may include at least one of a drawing number, a period of occurrence of the event, and a number of a person who generated the event.

The history information may include a drawing number, a date and time of occurrence of the event, a type of the event, and a post number of the person who generated the event.

According to another aspect of the present invention, there is provided a terminal for supporting ship building information sharing, comprising: an input unit for inputting information on at least one chat room desired to be copied from a user; Wherein the at least one chat room corresponds to at least one of the at least one chat room, and wherein the at least one chat room corresponds to at least one of the at least one chat room, And the ship building information related to at least one drawing is stored in a ship building information database connected to the server.

In particular, the information about the at least one chat room includes a source call number, a target call number, the source call number indicates a call number corresponding to at least one chat room for which the copy is desired, It may mean the line number of the target line to which the chat room containing the same information as the one chat room is to be generated.

Further, the ship building information includes the number of the at least one drawing and the line number of the line that is the subject of the at least one drawing, the drawing number includes the line number, Wherein upon receipt of the request message, for each of the at least one chat room, a call number portion of the drawing number is replaced by the target call number, the call number is replaced by the target call number, The information can create the same chat room.

In addition, the input unit receives a search condition for searching history information of an event generated in the ship building information database from the user, the transmission unit transmits a history inquiry request message including the search condition to the server, A receiving unit for receiving history information corresponding to the search condition from the server; And a display unit for displaying the history information.

In addition, the search condition may include at least one of a drawing number, a period of occurrence of the event, and a number of a person who generated the event.

The history information may include a drawing number, a date and time of occurrence of the event, a type of the event, and a post number of the person who generated the event.

According to another aspect of the present invention, there is provided a method of supporting ship building information sharing in a server, the method comprising: receiving a chat room copy request message including information on at least one chat room from which a user wants to copy Receiving; Wherein each of the at least one chat room corresponds to at least one drawing and for each of the at least one chat room the ship building information associated with the corresponding at least one drawing A method for supporting ship building information sharing, which is stored in a ship building information database connected to the server, is provided.

In particular, the information about the at least one chat room includes a source call number, a target call number, the source call number indicates a call number corresponding to at least one chat room for which the copy is desired, It may mean the line number of the target line to which the chat room containing the same information as the one chat room is to be generated.

In addition, the ship building information includes the number of the at least one drawing and the arc number of the arc that is the object of the at least one drawing, the drawing number includes the arc number, For each of the at least one chat room, the call line number portion of the drawing number is replaced with the target call number, the call line number is replaced with the target call number, and the information other than the drawing number and the call number creates the same chat room Step < / RTI >

In addition, the ship building information database may include a visit history inquiry table for storing history information on events generated in the ship build information database, and the method for supporting the ship build information sharing may include: Receiving from a terminal a history inquiry request message including a search condition for inquiring a history of an event; Inquiring history information matching the search condition in the visit history lookup table; And transmitting the history information to the terminal.

According to another aspect of the present invention, there is provided a server for supporting ship building information sharing, the server for receiving a chat room copy request message including information on at least one chat room from which a user wants to copy, A receiving unit; Wherein each of the at least one chat room corresponds to at least one figure and wherein for each of the at least one chat room the ship building information associated with the corresponding at least one drawing is associated with at least one chat room, A server for supporting ship building information sharing, which is stored in a ship construction information database connected to the server, is provided.

In particular, the information about the at least one chat room includes a source call number, a target call number, the source call number indicates a call number corresponding to at least one chat room for which the copy is desired, It may mean the line number of the target line to which the chat room containing the same information as the one chat room is to be generated.

Further, the ship building information may include a number of an arithmetic line of the at least one drawing and an arithmetic line number of the at least one drawing, wherein the drawing number includes the arithmetic number, For each of said at least one chat room, while the call line number portion of said drawing number is replaced by said target call number, said call number is replaced by said target call number, and said call number Other information can create the same chat room.

In addition, the ship building information database may include a visit history inquiry table for storing history information about events generated in the ship build information database, and the receiver may search for a history of events generated in the ship build information database Wherein the processor inquires history information matching the search condition in the visit history lookup table and the server transmits a history information request message to the terminal, .

According to the embodiment of the present invention, information on ship drying can be categorized and stored in a database, whereby a history of events occurring at the time of ship building can be managed, and information related to ship building and event occurrence history can be displayed So that the user can easily access the information on the ship that has been previously dried.

And, when building a series ship, it is easy to grasp the errors and reflection requests of the first constructed ship, change of the construction method and change of the process.

In addition, it is possible to easily confirm whether the request is reflected by supporting the comment function, and the operator can study the related information in advance when the series ship or the like ship is constructed by supporting the copying function of information related to ship building between lines.

1 is a diagram illustrating a system for supporting ship building information sharing according to an embodiment of the present invention.
FIG. 2 illustrates a terminal supporting ship building information sharing according to an embodiment of the present invention. Referring to FIG.
3 is a view showing a chat room selection screen of an application supporting sharing of ship building information according to an embodiment of the present invention.
FIG. 4 is a view showing a chat room screen of an application supporting sharing of ship building information according to an embodiment of the present invention.
5 is a view showing a chat room creation screen of an application supporting sharing of ship building information according to an embodiment of the present invention.
6 is a view showing a chatting room copying screen of an application supporting sharing of ship building information according to an embodiment of the present invention.
7 is a view showing a visit history inquiry screen of an application supporting sharing of ship building information according to an embodiment of the present invention.
8 is a diagram illustrating a middleware and an application server supporting ship building information sharing according to an embodiment of the present invention.
9 is a diagram illustrating a structure of a ship building information database according to an embodiment of the present invention.
10 is a diagram illustrating a method for a terminal to inquire and store ship building information according to an embodiment of the present invention.
11 is a diagram illustrating a method for middleware and an application server to retrieve and store ship building information according to an embodiment of the present invention.
12 is a diagram illustrating a method of copying a chat room and a method of inquiring a visit history according to an embodiment of the present invention.
13 is a diagram illustrating a method of copying a chat room and a method of inquiring a visit history according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals are used to designate the same or similar components throughout the drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

First, a system for supporting ship building information sharing according to an embodiment of the present invention will be described with reference to FIG. 1 is a diagram illustrating a system for supporting ship building information sharing according to an embodiment of the present invention.

The system for supporting ship building information sharing according to an embodiment of the present invention categorizes information related to ship building and stores the information in a database. When the user requests to view the ship building related information, the system searches for and displays the requested information in the database .

As shown in FIG. 1, a system for supporting ship building information sharing according to an embodiment of the present invention includes a middleware and application server 110, a terminal 120, and a ship building information database 130.

The terminal 120 is equipped with a ship building information sharing application, and functions as a ship building information sharing application including a ship building information reading function, a ship building information storing function, a chat room creating function, a chat room copying function, . Ship building information sharing application is an application that allows users to share information about shipbuilding. The ship building information sharing application provides a chat room, which is a virtual space in which users of the terminals 120 can share information related to ship building, and the chat room can correspond to at least one of the drawings of the ship. Users can then share ship building information associated with at least one drawing corresponding to a particular chat room in a particular chat room. The ship building information may include a request of a specific user related to at least one drawing corresponding to a specific chat room, whether or not the request information is reflected.

The terminal 120 receives a request for ship building information from a user using the ship building information sharing application and transmits the request to the middleware and the application server 110. The terminal 120 receives the ship building information from the middleware and the application server 110, (120). The terminal 120 receives the ship building information that the user desires to store in the ship building information database 130 from the user and transmits the information to the middleware and the application server 110.

The terminal 120 may be any type of data processing device capable of communicating with the middleware and application server 110, such as a mobile device such as a mobile phone, a PDA, a smart phone, etc., a notebook computer, a tablet PC, .

The middleware and application server 110 are connected to the plurality of terminals 120 and the ship building information database 130 to support a plurality of terminals 120 to share information on ship building.

The middleware and application server 110 receives the ship building information request message from the terminal 120, performs user authentication using the employee table 134 of the ship building database 130, (130), and transmits the retrieved information to the terminal (120). The middleware and application server 110 receives the ship building information that the user desires to store in the ship building information database 130 from the terminal 120 and stores the information in the ship building information database 130. Upon receiving the chat room creation request message from the terminal 120, the middleware and the application server 110 search the drawing table 135 of the ship building database 130 and transmit the list of drawings to the terminal 120.

The ship building information database 130 classifies and stores information related to ship building by chat rooms.

Next, referring to FIG. 2 to FIG. 7, a terminal supporting sharing of ship building information according to an embodiment of the present invention and an application installed in the terminal will be described.

FIG. 2 illustrates a terminal supporting ship building information sharing according to an embodiment of the present invention. Referring to FIG.

2, a terminal 120 supporting sharing of ship building information according to an embodiment of the present invention includes an input unit 121, a display unit 122, a transmitter 123, and a receiver 124 .

The input unit 121 is used to select a chat room desired to be viewed, ship building information to be added to the ship building information database 130, a chat room creation request, information on at least one chat room desired to be copied, Information, data, and the like such as a search condition for searching the history of the event that has been received. The input unit 121 may include a touch screen, a key pad, a keyboard, and a mouse.

The transmitting unit 123 transmits a message such as a ship building information request message including identification information of a chat room the user wants to view, ship building information to be added to the ship building information database 130, a chat room copy request message, a history inquiry request message, Information, data, and the like to the middleware and the application server 110. The identification information of the chat room may be a chat room ID assigned to the chat room when the chat room is opened, or a drawing number of at least one drawing corresponding to the chat room.

The reception unit 124 receives information such as ship building information, a list of drawings, visit history information, etc. related to the chat room that the user wants to view from the middleware and the application server 110.

At this time, the ship information request message may include the identification information of the user, the middleware and the application server 110 may authenticate the user using the identification information of the user, and only when the authentication is successful, ). The identification information of the user may be numbered.

The display unit 122 displays a chat room list, ship building information related to a chat room the user wants to browse, a list of drawings, and the like.

FIG. 3 is a view showing a chat room selection screen of an application supporting sharing of ship building information according to an embodiment of the present invention, FIG. 4 is a view illustrating a chat room screen of an application supporting sharing of ship building information according to an embodiment of the present invention FIG. 5 is a view illustrating a chat room creation screen of an application supporting sharing of ship building information according to an embodiment of the present invention.

When the terminal 120 receives an execution request for the ship building information sharing application from the user through the input unit 121, the terminal 120 executes the ship building information sharing application installed in the terminal 120. [

Then, the chat room selection screen shown in Fig. 3 is displayed on the display unit 122. Fig. 3, the chat room selection screen includes a chat room addition button 310, a search window 320, a search button 321, and a chat room list 330. As shown in FIG. The chat room list 330 shows a list of existing chat rooms. In FIG. 3, the chat room list 330 shows the drawing numbers of the respective rooms corresponding to the respective chat rooms for each chat room. For example, in Fig. 3, "5044DA235FA01" is a drawing numeral of a drawing corresponding to the chat room first listed in the chat room list 330. [

A drawing number is formed by coding an arc number, drawing type, block number, member type, and serial number. For example, " 5044 "indicates the line number and" DA "indicates the drawing type, that is, the drawing is a basic drawing, a detail drawing, a production drawing, "Indicates a block number. The ship divides the hull into dozens or hundreds of blocks, assembles the individual blocks on the ground, assembles them into a single hull by sequentially mounting the blocks on the ferry, where the block numbers are assigned to each block Quot; < / RTI > &Quot; FA "indicates the type of the member, that is, the member of the drawing, and" 01 "indicates a serial number, that is, the same line, the same drawing type, the same block number, In the case of a serial number to distinguish.

When the chat room selection screen is displayed on the display unit 122 of the terminal 120, the user can execute the chat room addition button 310 to create a new chat room, and to view the existing chat room, You can choose the chat room you want. At this time, the user can enter the drawing number corresponding to the chat room desired to be browsed in the search window 320 and execute the search button 321 to search for the chat room desired to be browsed.

When a chat room desired to be browsed by the user is selected, the terminal 120 displays the chat room screen related to the selected chat room shown in FIG. 4 on the display unit 122. FIG. 4, the chat room screen includes a chat window 410, an input window 420, a send button 430, and a write button 440.

In the chat window 410, ship building information related to the chat room, that is, information shared by the users in the chat room is displayed. As shown in FIG. 4, the chat window 410 displays a drawing number, a registration date, a registrant, a content, a comment date, a comment registrant, a comment target person, and a comment content of the drawing corresponding to the chat room. At this time, the drawing number may be a name of a chat room, and the contents may be at least one of text type information, image type information, and voice type information.

Therefore, according to the embodiment of the present invention, since the user can save the ship building information as a voice file and share it with other users through the chat room, information about various phenomena that are difficult to be expressed in text can be efficiently shared .

The user inputs a comment in the input window 420 and then executes the transmission button 430 in order to comment on an existing registered text. Then, the user can execute the write button 440 to register a new article. When the write button 440 is executed, a new input window is opened and the user can input text, insert an image, or attach a voice file to a new input window. The newly registered text of the user is displayed on the chat window 410.

When the user executes the chat room addition button 310 on the chat room selection screen or the chat room screen, the chat room creation screen of FIG. 5 is displayed on the terminal 120. As shown in FIG. 5, the chat room creation screen includes a chat room creation button 510, a search window 520, a search button 521, and a drawing number list 530.

The drawing number list 530 shows a list of the drawings. When the chat room addition button 310 is executed, the terminal 120 transmits a chat room creation request message to the middleware and the application server 110, and receives and displays the list of drawings from the middleware and the application server 110. At this time, upon receiving the chat room creation request message, the middleware and application server 110 access the drawing table 135 to obtain the drawing numbers stored in the drawing table 135, generate a drawing number list, Lt; / RTI >

The user selects a drawing number for which a chat room is to be created in the drawing number list 530, and then executes a chat room creation button 510. At this time, the user may enter a drawing number in the search window 520, and execute a search button 521 to search for a desired drawing.

When the chat room creation button 510 is executed, the terminal 120 displays the chat room screen of FIG. At this time, since the chat room is newly created, the chat window 410 may have no information. The user can register a new article by executing the writing button 440 on the chatting room screen.

FIG. 6 is a diagram illustrating a screen for copying a chat room between lines in an application for supporting ship building information sharing according to an embodiment of the present invention.

Line chat room copying function is also a function for creating a second chat room similar to the first chat room for the first line that has been previously constructed if the first line and the second line are series or similar to the second line. That is, the ship building information stored in the first chat room on the ship building information database 130 is also stored in the second chat room. At this time, the ship building information for the first chat room and the ship building information for the second chat room may differ only in the call number because the first and second chat rooms are different from each other. That is, only the line number part of the drawing number and the line number may be different.

6, the user inputs the line number of the source line and the line number of the target line. The source line indicates the line corresponding to the chat room the user wants to copy, and the target line indicates the target line for which the user wants to create a chat room including the same information as the chat room desired to be copied.

Then, the user selects the copy target drawing. That is, select All to copy the chat room for all drawings of the source line, and select the drawing type to copy only the chat room for a certain type of drawing, and describe the type of drawing to be copied. As described above, the types of drawings may include a basic diagram, a detailed diagram, a production diagram, a production diagram, an installation diagram, and a vendor diagram.

When the user executes the copy execution button, the terminal 120 transmits a chat room copy request message to the middleware and the application server 110. The middleware and application server 110 copies the chat room upon receiving the chat room copy request message. At this time, for each of the at least one chat room requesting copying in the chat room copy request message, the middleware and application server 110 replace the call number part of the drawing number with the target call number and the call number is replaced with the target call number, Information other than the number and the line number can create the same chat room.

7 is a view showing a visit history inquiry screen of an application supporting sharing of ship building information according to an embodiment of the present invention.

The visit history inquiry means inquiring the history of the event that occurred in the ship building information database.

In the visit history inquiry screen of Fig. 7, the user enters a search condition. The search condition includes at least one of a drawing number, a period of occurrence of the event, and a number of the person who generated the event. That is, the user inputs at least one of a drawing number, an occurrence period, and a run number, and executes a search button.

When the search button is executed, the terminal 120 transmits a history inquiry request message including a search condition to the middleware and the application server 110, and the middleware and the application server 110 download the visit history table of the ship building information database 130 And then transmits the history information corresponding to the search condition to the terminal 120.

Then, the terminal 120 displays the history information. As shown in FIG. 7, the history information may include a drawing number, a date and time of occurrence of an event, a kind of an event, and the number and name of the person who generated the event. The types of events can include chat room creation, inquiry, information storage, and comment creation.

Next, referring to FIG. 8, a middleware and an application server supporting ship building information sharing according to an embodiment of the present invention will be described. 8 is a diagram illustrating a middleware and an application server supporting ship building information sharing according to an embodiment of the present invention.

8, the middleware and application server 110 supporting the sharing of ship building information according to the embodiment of the present invention includes a processor 111, a transmitter 112, and a receiver 113. As shown in FIG.

The receiving unit 113 receives from the terminal 120 the information on the ship building information request message, the chat room creation request message, the ship building information to be added to the ship building information database 130, A chat room copy request message, a history inquiry request message including a search condition for inquiring a history of an event generated in the ship building information database, and the like. At this time, the ship building information request message may include the identification information of the chat room desired by the user and the identification information of the user.

In addition, the receiving unit 112 receives a message, such as a completion message, an error message, and inquired information, from the ship building information database 130.

The transmission unit 113 transmits information such as ship building information, a list of drawings, and the like related to the chat room desired by the user to the terminal 120.

The transmitter 113 transmits messages, information, and data such as an inquiry request message, a supplementary request message, a deletion request message, a correction request message, and ship building information to be added to the ship building information database 130. Then, the ship building information database 130 adds, modifies, deletes, or inquires the information according to the message received from the transmission unit 113. When the request of the middleware and the application server 110 is completed, a completion message is transmitted to the middleware and the application server 110, and an error message is transmitted when an error occurs. When the information is inquired, the ship building information database 130 transmits the inquired information to the middleware and the application server 110.

When the middleware and the application server 110 receive the ship building information request message from the terminal 120, the processor 111 transmits the user's identification information included in the ship building information request message and the employee table 134 to the user Authentication. At this time, the processor 111 can confirm whether or not the user is a legitimate employee by checking whether the user's identification information included in the ship building information request message exists in the employee table 134. [

If the authentication is successful, the processor 111 searches the ship building information database 130 for ship building information related to the chat room for which the user wants to browse, using the identification information of the chat room included in the ship building information request message. At this time, the transmitting unit 113 of the middleware and the application server 110 transmits the inquiry request message to the ship building database 130, the ship building information database 130 inquires the information according to the received inquiry request message, And transmits the information to the middleware and application server 110.

If the authentication fails, the processor 111 may generate a rejection message and transmit it to the terminal through the transmitter 113. [

When the middleware and application server 110 receives the ship building information to be added to the ship building information database 130 from the terminal 120, the processor 111 stores the ship building information to be added to the ship building information database. At this time, the transmitting unit 113 of the middleware and the application server 110 transmits an additional request message including ship building information to be added to the ship building database 130, and the ship building information database 130 transmits the received additional request message Information can be added.

The middleware and application server 110 stores an event generation history in the ship building information database 130 whenever an event such as inquiry of the ship building information database 130 by the user and information storage in the ship building information database 130 occurs. And store it in the visiting history table 133. [ At this time, the transmitting unit 113 of the middleware and the application server 110 transmits an additional request message including an event generation history to the ship building database 130, and the ship building information database 130 Information can be added.

When the middleware and application server 110 receives the chat room creation request message from the terminal 120, the processor 111 can obtain the drawing number from the drawing table 135 and generate the drawing number list.

When the middleware and application server 110 receives the chat room copy request message from the terminal 120, the processor 111 may copy at least one chat room desired to be copied included in the chat room copy request message. At this time, for each of the at least one chat room, the processor 111 replaces the call number portion of the drawing number with the target call number, the call number is replaced with the target call number, and the information other than the drawing number and call number creates the same chat room can do.

When the middleware and application server 110 receives the history inquiry request message from the terminal 120, the processor 111 can inquire the history information in the visiting history table 133 of the ship building information database 130. [

Next, the structure of the ship building information database according to the embodiment of the present invention will be described with reference to FIG. 9 is a diagram illustrating a structure of a ship building information database according to an embodiment of the present invention.

9, the ship building information database 130 includes a chat room information table 131, a comment information table 132, a visit history table 133, an employee table 134, and a drawing table 135 do.

The chat room information table 131 stores information on ship building information related to at least one user registered in the chat room.

9, the chat room information table 131 includes a chat room ID field, a drawing number field, a row number field, a registration serial field, a registrant number field, a registration date field, a registration type field, a text content field, Content field.

The chat room ID field stores the chat room ID assigned to the chat room when the chat room is opened, and the attribute is int.

The drawing number field stores the drawing number of at least one drawing corresponding to the chat room, and the attribute is varchar.

The line number field stores the line number of the line associated with the chat room, and the attribute is varchar.

The registration serial field stores the serial number of the article registered in the chat room, and the attribute is int.

The subscriber's number field stores the number of the user who registered the article registered in the chat room, and the attribute is varchar.

The registration date field stores the date registered in the chat room, and the attribute is date.

The registration type field stores the type of the article registered in the chat room, and the attribute is varchar. The registration type field can store whether the type of the text registered in the chat room is text, voice, image, or a combination of them.

The text content field stores the portion of text registered in the chat room whose type is text, and the attribute is varchar.

The image content field stores a portion of the article registered in the chat room whose type is an image, and the attribute is BLOB.

The voice content field stores a portion of a type registered in the chat room, the attribute of which is a blob.

The primary key of the chatting room information table 131 may be a chatting room ID field.

The comment information table 132 stores information about comments created for posts registered in the chat room.

9, the comment information table 132 includes a comment ID field, a registration serial field, a comment serial field, a comment registrant number field, a comment subject person number field, a comment registration date field, a comment type field, A comment content field, and a voice comment content field.

The chat room ID field stores the chat room ID assigned to the chat room when the chat room is opened, and the attribute is int.

The registration serial field stores the serial number of the article with the comment in the chat room, and the attribute is int.

The registration serial field stores the serial number of the comment, and the attribute is int.

The comment subscriber field stores the user ID of the user who registered the comment, and the attribute is varchar.

The subject person field stores the person's number of the subject of the comment, and the attribute is varchar.

The comment entry field stores the date the comment was registered, and the attribute is date.

The comment type field stores the type of comment, and the attribute is varchar. The comment type field may store whether the comment type is text, voice, image, or a combination of them.

The text comment field stores the part of the comment where the type is text, and the attribute is varchar.

The image comment field stores the portion of the comment whose type is the image, and the attribute is BLOB.

The voice comment content field stores the portion of the comment whose voice is the voice, and the attribute is BLOB.

The primary key of the comment information table 132 may be a chat room ID field, a registration serial field, and a comment serial field.

The visit history table 133 stores history information about events generated in the ship building information database by the user.

As shown in FIG. 9, the visit history table 133 includes a chat room ID field, a drawing number field, an event time field, an event provider number field, and an event field.

The chat room ID field stores the ID of the chat room in which the event is generated, and the attribute is int.

The drawing number field stores the drawing number of at least one drawing corresponding to the chat room in which the event occurred, and the attribute is varchar.

The event time field stores the time at which the event occurred, and the attribute is date.

The event owner field stores the user ID of the user who generated the event, and the attribute is varchar.

The event field indicates the type of the event, and the attribute is varchar. The event field may indicate whether the event is a query, information storage, reply, or chat room creation.

The primary key of the visit history table 133 may be a chat room ID field, a drawing number field, an event time field, and an event provider number field.

Employee table 134 is a table that contains information about employees.

As shown in FIG. 7, the employee table 140 includes an employee number field, a work department field employee name field.

The number field indicates the employee number of the employee, and the attribute is varchar.

The work department field indicates the work department to which the employee belongs, and the attribute is varchar.

The employee name field indicates the name of the employee, and the attribute is varchar.

The drawing table 135 is a table including information relating to the drawings.

As shown in FIG. 7, the drawing table 135 includes a drawing number field, a line number field, a drawing type field, and a contact person number field.

The drawing number field indicates the drawing number of the drawing, and the attribute is varchar.

The line number field indicates the line number of the target line in the drawing, and the attribute is varchar.

The drawing type field indicates the type of the drawing, and the attribute is varchar. That is, it can indicate whether the drawing is a basic drawing, a detailed drawing, a production drawing, a production drawing, an installation drawing, or a vender drawing.

The personnel number field indicates the personnel number of the person in charge of the drawing, and the attribute is varchar.

Next, a method of supporting ship building information sharing in a terminal according to an embodiment of the present invention will be described with reference to FIG. 10 is a view illustrating a method of supporting ship building information sharing in a terminal according to an embodiment of the present invention.

When the terminal 120 receives a request to execute the ship building information sharing application from the user, the terminal 120 executes the ship building information sharing application installed in the terminal 120, and displays the chat room selection screen shown in FIG. 3 on the terminal 120 Displays it on the display unit 122, and receives the selection of the chat room desired to be viewed by the user (S810).

Then, the terminal 120 transmits a ship building information request message including the identification information of the chat room the user wants to browse to the middleware and the application server 110 (S820). At this time, the ship building information request message may also include identification information of the user.

The terminal 120 receives the shipbuilding information related to the chat room from the middleware and the application server 110 in step S830, and displays the received shipbuilding information on the chat room screen in step S840.

Then, the terminal 120 receives the ship building information to be added to the chat room from the user (S850), and transmits it to the middleware and the application server 110 (S860). The shipbuilding information to be added may be an article or comment registered by the user in the chat room.

Next, with reference to FIG. 11, a method of supporting ship building information sharing in the middleware and the application server according to the embodiment of the present invention will be described. 11 is a diagram illustrating a method of supporting ship building information sharing in a middleware and an application server according to an embodiment of the present invention.

The middleware and application server 110 receives the ship building information request message including the identification information of the chat room and the user identification information that the user wants to view from the terminal 120 in operation S910, 134) to authenticate the user (S920).

If the authentication is successful, the middleware and application server 110 searches the ship building information database 130 for ship building information related to the chat room for which the user wants to browse (S930). At this time, the transmitting unit 113 of the middleware and the application server 110 transmits the inquiry request message to the ship building database 130, the ship building information database 130 inquires the information according to the received inquiry request message, And transmits the information to the middleware and application server 110.

Then, the middleware and application server 110 transmits the information received from the ship building information database 130 to the terminal 120 (S940).

In step S950, the middleware and application server 110 receives the ship construction information to be added to the ship construction information database from the terminal 120 (S950), and stores the received ship construction information in the ship construction information database (S950). The ship building information to be added may be a post or a comment registered by the user in the chat room. The middleware and application server 110 stores the information on the registration information in the chatting room table 131 if the ship building information to be added is registered in the chatting room and if the comment is a comment on the article registered in the chatting room, Can be stored in the comment information table 132. [ At this time, the transmitting unit 113 of the middleware and the application server 110 transmits an additional request message including ship building information to be added to the ship building database 130, and the ship building information database 130 transmits the received additional request message Information can be added.

Next, with reference to FIGS. 12 and 13, a method of copying a chat room and a method of inquiring visiting history according to an embodiment of the present invention will be described. FIG. 12 is a diagram illustrating a method of copying a chat room and a method of inquiring a visit history according to an embodiment of the present invention. FIG. 13 illustrates a method of copying a chat room according to an embodiment of the present invention, And a method of inquiring the visiting history.

12, the terminal 120 receives information about at least one chat room desired to be copied from a user (S1210), and transmits a chat room copy containing information on at least one chat room And transmits the request message to the middleware and application server 110 (S1220).

In operation S1230, the terminal 120 receives a history search request message including a search condition from the user, and transmits the history search request message including the search condition to the middleware, (S1240). The history information matching the search condition is received from the middleware and the application server 110 (S1250), and the history information is displayed (S1250).

12, when the middleware and application server 110 receives a chat room copy request message including information on at least one chat room the user wants to copy from the terminal 120 S1310), and copies at least one chat room (S1320). At this time, for the at least one chat room, the middleware and application server 110 replace the call number portion of the drawing number with the target call number, the call number is replaced with the target call number, and the information other than the drawing number and the call number is the same Create a chat room.

The middleware and the application server receive the history inquiry request message including the search condition for inquiring the history of the event generated in the ship building information database from the terminal 120 (S1330), and the visit history The history information matching the search condition is inquired in the inquiry table 133 (S1340) and transmitted to the terminal 120 (S1350).

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

110: Middleware and application server
120: terminal
130: Ship building information database
131: Room table
132: comment information table
133: Visit history table
134: Temple Table
135: drawing table
121: Input unit
122:
123:
124:
111: Processor
112:
113:

Claims (20)

A method of supporting ship building information sharing in a terminal,
Receiving information about at least one chat room desired to be copied from a user;
Sending a chat room copy request message containing information about the at least one chat room to a server,
Each of the at least one chat room corresponding to at least one figure,
Wherein for each of said at least one chat room, ship building information associated with said corresponding at least one drawing is stored in a ship building information database associated with said server. The method according to claim 1,
Wherein the information about the at least one chat room includes a source call number and a target call number,
Wherein the source call number indicates a call line number corresponding to at least one chat room for which the copy is desired,
Wherein the target call number refers to a line number of an object line for which a chat room containing the same information as the at least one chat room is to be created. The method of claim 2,
Wherein the ship building information includes a reference number of the at least one drawing and an arithmetic line number of the arc that is the subject of the at least one drawing, the drawing number includes the arc number,
Wherein the server receives, for each of the at least one chat room, a call number portion of the drawing number is replaced with the target call number, the call number is replaced with the target call number, And information other than the call number generating the same chat room. The method according to claim 1,
Receiving a search condition for a history inquiry of an event generated in the ship building information database from the user;
Transmitting a history inquiry request message including the search condition to the server;
Receiving history information corresponding to the search condition from the server; And
Further comprising the step of displaying the history information. The method of claim 4,
Wherein the search condition includes at least one of a drawing number, a period of occurrence of the event, and a number of a person who generated the event. The method of claim 4,
Wherein the history information includes a drawing number, a date and time at which the event occurred, a type of the event, and a number of the person who generated the event. A terminal for supporting ship building information sharing,
An input unit for receiving information on at least one chat room desired to be copied from a user;
And a transmitting unit for transmitting a chat room copy request message including information on the at least one chat room to a server,
Each of the at least one chat room corresponding to at least one figure,
Wherein, for each of said at least one chat room, ship building information associated with said corresponding at least one drawing is stored in a ship building information database connected to said server. The method of claim 7,
Wherein the information about the at least one chat room includes a source call number and a target call number,
Wherein the source call number indicates a call line number corresponding to at least one chat room for which the copy is desired,
Wherein the target call number refers to a line number of an object line for which a chat room including the same information as the at least one chat room is to be created. The method of claim 8,
Wherein the ship building information includes a reference number of the at least one drawing and an arithmetic line number of the arc that is the subject of the at least one drawing, the drawing number includes the arc number,
Wherein the server receives, for each of the at least one chat room, a call number portion of the drawing number is replaced with the target call number, the call number is replaced with the target call number, And information other than the number of the call generates the same chat room. The method of claim 7,
Wherein the input unit receives a search condition for searching a history of an event generated in the ship building information database from the user,
Wherein the transmitting unit transmits a history inquiry request message including the search condition to the server,
The terminal
A receiving unit for receiving history information corresponding to the search condition from the server; And
Further comprising a display unit for displaying the history information. The method of claim 10,
Wherein the search condition includes at least one of a drawing number, a generation period of the event, and a number of a person who generated the event. The method of claim 10,
Wherein the history information includes a drawing number, a date and time of occurrence of the event, a type of the event, and a number of the person who generated the event. In a method for supporting sharing of ship building information on a server,
Receiving a chat room copy request message including information about at least one chat room the user wants to copy from the terminal;
And copying each of said at least one chat room,
Each of the at least one chat room corresponding to at least one figure,
Wherein for each of said at least one chat room, ship building information associated with said corresponding at least one drawing is stored in a ship building information database associated with said server. 14. The method of claim 13,
Wherein the information about the at least one chat room includes a source call number and a target call number,
Wherein the source call number indicates a call line number corresponding to at least one chat room for which the copy is desired,
Wherein the target call number refers to a line number of an object line for which a chat room containing the same information as the at least one chat room is to be created. 15. The method of claim 14,
Wherein the ship building information includes a reference number of the at least one drawing and an arithmetic line number of the arc that is the subject of the at least one drawing, the drawing number includes the arc number,
The copying step
For each of the at least one chat room, the call number portion of the drawing number is replaced by the target call number, the call number is replaced by the target call number, and the information other than the drawing number and the call number creates the same chat room The method comprising the steps of: a. 14. The method of claim 13,
Wherein the ship building information database includes a visit history inquiry table for storing history information on events generated in the ship building information database,
Receiving, from the terminal, a history inquiry request message including a search condition for inquiring a history of an event generated in the ship building information database;
Inquiring history information matching the search condition in the visit history lookup table; And
And transmitting the history information to the terminal. ≪ Desc / Clms Page number 19 > A server for supporting ship building information sharing,
A receiving unit for receiving a chat room copy request message including information on at least one chat room the user wants to copy from the terminal;
And a processor to copy each of said at least one chat room,
Each of the at least one chat room corresponding to at least one figure,
Wherein, for each of said at least one chat room, ship building information associated with said corresponding at least one drawing is stored in a ship building information database associated with said server. 18. The method of claim 17,
Wherein the information about the at least one chat room includes a source call number and a target call number,
Wherein the source call number indicates a call line number corresponding to at least one chat room for which the copy is desired,
Wherein the target number is a line number of an object line to which a chat room containing the same information as the at least one chat room is to be created. 19. The method of claim 18,
Wherein the ship building information includes a reference number of the at least one drawing and an arithmetic line number of the arc that is the subject of the at least one drawing, the drawing number includes the arc number,
Wherein the processor is further operable, while copying each of the at least one chat room, for each of the at least one chat room, the call number portion of the drawing number is replaced by the target call number, the call number is replaced by the target call number, Wherein the information other than the drawing number and the line number is the same to create the same chat room. 18. The method of claim 17,
Wherein the ship building information database includes a visit history inquiry table for storing history information on events generated in the ship building information database,
Wherein the receiver receives from the terminal a history inquiry request message including a search condition for inquiring a history of an event generated in the ship building information database,
The processor retrieves history information corresponding to the search condition from the visit history lookup table,
Wherein the server further comprises a transmitter for transmitting the history information to the terminal.

Images