Apparatus and method for generating amphibian and reptile diary based on mating and spawning records, and computer program including the same

Abstract

The present invention relates to an amphibian and reptile diary generation device based on mating and spawning records, and may include a mating record unit that generates mating data for either a male or female individual of an amphibian or reptile, a spawning record unit that generates spawning data including at least one spawning record of a female individual, a hatching record unit that generates hatching data including a profile of an individual hatched in association with at least one spawning data, and a diary generation unit that generates a rearing diary for an amphibian or reptile based on the mating data, spawning data, and hatching data.

Description

Technology Field

[0001] The present invention relates to a technology for generating amphibian and reptile diaries based on mating and spawning records. Background Technology

[0003] Recently, due to the increase in single-person households and the decline in the birth rate, the number of households raising pets is on the rise. With this increase in pet-owning households, the system for adopting and selling pets is becoming more sophisticated, and businesses necessary for raising pets are also developing.

[0004] Among companion animals, the demand for reptiles and amphibians (hereinafter referred to as amphibians and reptiles) is also steadily increasing, although the demand remains limited. However, compared to other companion animals, amphibians and reptiles are difficult to raise, and difficulties in importing and distributing them make it hard to easily acquire them or learn how to care for them.

[0005] In addition, amphibians and reptiles are characterized by active mating and spawning compared to other pets, making it essential to record and manage these activities. Furthermore, since morphs, which refer to the species of amphibians and reptiles, are inherited from the appearance or characteristics of the parents, records of the parents are also essential to accurately estimate the morph of the offspring.

[0006] Although record-keeping and management are necessary when raising amphibians and reptiles, research and development in this area are currently lacking. Prior art literature

[0008] Korean Registered Patent No. 10-2186174 (Dec. 3, 2020) Korean Published Patent No. 10-2022-0113609 (Aug. 16, 2022) The problem to be solved

[0009] One embodiment of the present invention relates to an apparatus, a method, and a computer program including the same for generating an amphibian and reptile diary based on mating and spawning records, which records mating data, spawning data, and hatching data of amphibians and reptiles so that a user can easily check the records and manage pet amphibians and reptiles.

[0010] One embodiment of the present invention relates to an apparatus, a method, and a computer program including the same for generating an amphibian and reptile diary based on mating and spawning records, capable of estimating the morph of an individual born through mating of amphibians and reptiles.

[0011] One embodiment of the present invention relates to an apparatus, method, and computer program including the same for generating an amphibian and reptile diary based on mating and spawning records, which can identify the spawning season by grouping records of mating and spawning of amphibians and reptiles through said mating. means of solving the problem

[0013] The present invention relates to an amphibian and reptile diary generation device based on mating and spawning records according to one embodiment of the present invention, comprising: a mating record unit that generates mating data for either a male or female individual of the amphibian or reptile; a spawning record unit that generates spawning data including at least one spawning record of the female individual; a hatching record unit that generates hatching data including a profile of an individual hatched in association with the at least one spawning data; and a diary generation unit that generates a rearing diary for the amphibian or reptile based on the mating data, the spawning data, and the hatching data.

[0014] The mating record unit above can generate first mating data by specifying a mating target object that has become the mating target for either the male object or the female object.

[0015] The mating record unit above can generate second mating data of the mating target object to correspond to the first mating data.

[0016] The second mating data above may include the date of mating and information about the male or female entity.

[0017] The above spawning record may include information about the female individual and the mating target individual that became the mating target for the female individual in association with the mating data when the mating data is generated.

[0018] The above spawning record unit can generate the spawning data by recording multiple spawning records of the female individual in a time series in association with the above mating data.

[0019] The above spawning record unit can generate spawning data that does not include information about the male individual.

[0020] The profile of the above-mentioned hatched individual may include information on the male individual and the female individual included in the above-mentioned spawning data as parent information.

[0021] The information of the above female individual may include a photograph and morph of the above female individual.

[0022] The above diary generation unit can display the mating data, the scattering data, and the hatching data in a pre-set diary template.

[0023] An amphibian and reptile diary generation device based on mating and spawning records according to one embodiment of the present invention may further include a morph estimation unit that estimates the morph of the hatched individual based on the male individual and the female individual.

[0024] The above morph estimation unit can estimate the morph of the hatched individual based on information about the female individual when the spawning data does not include information about the male individual.

[0025] An amphibian and reptile diary generation device based on mating and spawning records according to one embodiment of the present invention may further include a spawning season determining unit that determines the mating data and at least one spawning record of the female individual associated with the mating data as one spawning season.

[0026] The above spawning season determining unit may determine at least one spawning record included in the spawning data as one spawning season if the spawning data does not include information about the male individual.

[0027] A method for generating an amphibian and reptile diary based on mating and spawning records according to one embodiment of the present invention may include: a mating record step for generating mating data for either a male or female individual of the amphibian and reptile; a spawning record step for generating spawning data including at least one spawning record of the female individual; a hatching record step for generating hatching data including a profile of an individual hatched in association with the at least one spawning data; and a diary generation step for generating a rearing diary for the amphibian and reptile based on the mating data, the spawning data, and the hatching data.

[0028] A computer program according to another embodiment may be combined with a computing device to perform: a mating record step of generating mating data for either a male or female individual of an amphibian or reptile; a spawning record step of generating spawning data including at least one spawning record of the female individual; a hatching record step of generating hatching data including a profile of a hatched individual in association with the at least one spawning data; and a diary generation step of generating a rearing diary for the amphibian or reptile based on the mating data, the spawning data, and the hatching data. Effects of the invention

[0030] The disclosed technology may have the following effects. However, this does not mean that a specific embodiment must include all of the following effects or only the following effects; therefore, the scope of the rights of the disclosed technology should not be understood as being limited by this.

[0031] The present invention relates to an apparatus, method, and computer program including the same for generating an amphibian and reptile diary based on mating and spawning records according to one embodiment of the invention, wherein mating data, spawning data, and hatching data of amphibians and reptiles are recorded so that a user can easily check the records and manage pet amphibians and reptiles.

[0032] The present invention relates to an apparatus, method, and computer program including the same for generating an amphibian and reptile diary based on mating and spawning records according to one embodiment of the invention, and can estimate the morph of an individual born through the mating of amphibians and reptiles.

[0033] The present invention relates to an apparatus, method, and computer program including the same for generating an amphibian and reptile diary based on mating and spawning records according to one embodiment of the invention, wherein the spawning season can be identified by grouping records of mating of amphibians and reptiles and spawning through said mating. Brief explanation of the drawing

[0035] FIG. 1 is a diagram illustrating a mating and spawning record-based amphibian and reptile diary generation system according to one embodiment of the present invention. FIG. 2 is a diagram illustrating the physical configuration of an amphibian and reptile diary generation device based on mating and spawning records according to one embodiment of the present invention. FIG. 3 is a diagram illustrating the functional configuration of an amphibian and reptile diary generation device based on mating and spawning records according to one embodiment of the present invention. FIG. 4 is a diagram illustrating the sequence of a method for generating an amphibian and reptile diary based on mating and spawning records according to an embodiment of the present invention. FIG. 5 is a drawing illustrating a breeding diary according to one embodiment of the present invention. FIG. 6 is a diagram illustrating the generation of mating data according to an embodiment of the present invention. FIG. 7 is a diagram illustrating the generation of scattering data according to an embodiment of the present invention. FIG. 8 is a diagram illustrating the generation of hatching data according to an embodiment of the present invention. FIG. 9 is a diagram illustrating the generation of scattering data by one person according to an embodiment of the present invention. FIG. 10 is a drawing illustrating a spawning season record according to one embodiment of the present invention. Specific details for implementing the invention

[0036] The description of the present invention is merely an example for structural or functional explanation, and therefore the scope of the present invention should not be interpreted as being limited by the examples described in the text. That is, since the examples are subject to various modifications and may take various forms, the scope of the present invention should be understood to include equivalents capable of realizing the technical concept. Furthermore, the objectives or effects presented in the present invention do not imply that a specific example must include all of them or only such effects; therefore, the scope of the present invention should not be understood as being limited by them.

[0037] Meanwhile, the meaning of the terms described in this application should be understood as follows.

[0038] Terms such as "first," "second," etc., are intended to distinguish one component from another, and the scope of rights shall not be limited by these terms. For example, the first component may be named the second component, and similarly, the second component may be named the first component.

[0039] When it is stated that one component is "connected" to another component, it should be understood that it may be directly connected to that other component, or that there may be other components in between. Conversely, when it is stated that one component is "directly connected" to another component, it should be understood that there are no other components in between. Meanwhile, other expressions describing the relationships between components, such as "between" and "exactly between," or "adjacent to" and "directly adjacent to," should be interpreted in the same way.

[0040] A singular expression should be understood to include a plural expression unless the context clearly indicates otherwise, and terms such as "include" or "have" are intended to specify the existence of the implemented features, numbers, steps, actions, components, parts, or combinations thereof, and should be understood not to preclude the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0041] In each step, identifiers (e.g., a, b, c, etc.) are used for convenience of explanation and do not describe the order of the steps; the steps may occur differently from the specified order unless a specific order is clearly indicated in the context. That is, the steps may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

[0042] The present invention may be implemented as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc., and also include implementation in the form of a carrier wave (e.g., transmission over the Internet). Furthermore, the computer-readable recording medium may be distributed across networked computer systems, so that computer-readable code can be stored and executed in a distributed manner.

[0043] Unless otherwise defined, all terms used herein have the same meaning as generally understood by those skilled in the art to which this invention pertains. Terms defined in commonly used dictionaries should be interpreted as having meanings consistent with the context of the relevant technology and should not be interpreted as having an ideal or overly formal meaning unless explicitly defined in this application.

[0045] Referring to FIG. 1, the amphibian and reptile diary generation system (100) based on mating and spawning records may include a user terminal (130), an amphibian and reptile diary generation device (130) based on mating and spawning records, and a database (150).

[0046] The user terminal (130) can be implemented as a smartphone or wearable device capable of verifying data generated and metadata analyzed therefrom based on operations such as generating mating data through the mating and spawning record-based amphibian and reptile diary generating device (130), generating spawning data based on the mating data, generating hatching data in relation to the spawning data, and generating a rearing diary based on the mating data, spawning data, and hatching data, and is not necessarily limited thereto, but can also be implemented as various devices such as a tablet PC. The user terminal (130) can be connected to the mating and spawning record-based amphibian and reptile diary generating device (130) via a network, and multiple user terminals (130) can be simultaneously connected to the mating and spawning record-based amphibian and reptile diary generating device (130).

[0047] The amphibian and reptile diary generation device (130) based on mating and spawning records can be implemented as a server corresponding to a computer or program that sequentially performs operations such as generating mating data, generating spawning data based on mating data, generating hatching data in relation to spawning data, and generating a rearing diary based on mating data, spawning data, and hatching data. The amphibian and reptile diary generation device (130) based on mating and spawning records can be wirelessly connected to a user terminal (130) via Bluetooth, WiFi, a communication network, etc., and can exchange data with the user terminal (130) through a network.

[0048] A device for generating an amphibian and reptile diary based on mating and spawning records (130) can be provided by including it in a computer-readable recording medium by tangibly implementing a program of instructions for implementing it. In other words, the device for generating an amphibian and reptile diary based on mating and spawning records (130) can be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable recording medium. Additionally, the device for generating an amphibian and reptile diary based on mating and spawning records (130) can be composed of a computer program that sequentially performs operations such as generating mating data, generating spawning data based on mating data, generating hatching data in relation to spawning data, and generating a rearing diary based on mating data, spawning data, and hatching data, and the said computer program can be stored on a computer-readable recording medium.

[0049] The database (150) may be a storage device that stores various information generated through the process of generating mating data, generating spawning data based on mating data, generating hatching data in association with spawning data, and generating a rearing diary based on mating data, spawning data, and hatching data.

[0051] FIG. 2 is a diagram illustrating the physical configuration of an amphibian and reptile diary generating device (130) based on mating and spawning records according to one embodiment.

[0052] Referring to FIG. 2, an amphibian and reptile diary generation device (130) based on mating and spawning records may be implemented by including a processor (210), memory (230), user input / output unit (250), and network input / output unit (270).

[0053] The processor (210) can execute a procedure that performs operations such as generating mating data, generating spawning data based on mating data, generating hatching data in association with spawning data, and generating a rearing diary based on mating data, spawning data, and hatching data, and can manage memory (230) that is read or written throughout the process, and can schedule the synchronization time between volatile memory and non-volatile memory in memory (230). The processor (210) can control the overall operation of the mating and spawning record-based amphibian and reptile diary generating device (130), and can be electrically connected to the memory (230), user input / output unit (250), and network input / output unit (270) to control the data flow between them. The processor (210) can be implemented as the CPU (Central Processing Unit) of the mating and spawning record-based amphibian and reptile diary generating device (130).

[0054] The memory (230) may include an auxiliary storage device implemented as non-volatile memory such as an SSD (Solid State Drive) or HDD (Hard Disk Drive) and used to store all the data required for the amphibian and reptile diary generating device (130) based on mating and spawning records, and may include a main memory device implemented as volatile memory such as RAM (Random Access Memory).

[0055] The user input / output unit (250) may include an environment for receiving user input and an environment for outputting specific information to the user. For example, the user input / output unit (250) may include an input device including an adapter such as a touch pad, a touch screen, a virtual keyboard, or a pointing device, and an output device including an adapter such as a monitor or a touch screen. In one embodiment, the user input / output unit (250) may correspond to a computing device connected via remote access, and in such case, the amphibian and reptile diary generation device (130) based on mating and spawning records may be performed as a server.

[0056] The network input / output unit (270) includes an environment for connecting to an external device or system through a network, and may include an adapter for communication such as a LAN (Local Area Network), MAN (Metropolitan Area Network), WAN (Wide Area Network), and VAN (Value Added Network).

[0058] FIG. 3 is a diagram illustrating the functional configuration of an amphibian and reptile diary generation device (130) based on mating and spawning records according to an embodiment of the present invention. Referring to FIG. 3, the amphibian and reptile diary generation device (130) based on mating and spawning records may include a mating record unit (310), a spawning record unit (320), a hatching record unit (330), a diary generation unit (340), a morph estimation unit (350), and a spawning season determination unit (360).

[0059] Referring to FIG. 5, in one embodiment, an amphibian and reptile diary generating device (130) based on mating and spawning records can record specific amphibians and reptiles according to information input through a user terminal (130). For example, a user can record specific amphibians and reptiles by selecting a record list (5100) displayed through the user terminal (130). More specifically, the amphibian and reptile diary generating device (130) based on mating and spawning records can record specific amphibians and reptiles according to a food record (5110), weight record (5120), mating record (5130), spawning record (5140), hatching record (5150), or solitary spawning record (5160) included in the record list (5100). An amphibian and reptile diary generating device (130) based on mating and spawning records can display records for specific amphibians and reptiles as a breeding diary (5200). Here, the breeding diary (5200) can check spawning season information (5210) and specific date information (5220), and a detailed explanation thereof is provided below.

[0060] Referring to FIGS. 5 and 6, the mating record (310) can generate mating data for either a male or a female individual of amphibians or reptiles. Here, mating may refer to mating between a male individual and a female individual. The mating record (310) can generate mating data including a mating date and a mating individual. For example, the mating record (310) can generate mating data including a female individual (5131) and a male individual (5132) that have mated. More specifically, the mating record (310) can generate mating data for a specified individual. The mating record (310) can generate mating data for amphibians or reptiles for which a profile has already been created. For example, the mating record (310) can generate mating data by specifying a female individual that is the target of mating for a specific female individual that has a previously created profile. As another example, the mating record book (310) can generate mating data by specifying a female object that is the target of mating for a specific male object that has a previously generated profile.

[0061] In one embodiment, the mating record unit (310) can generate first mating data by specifying a mating target object that has become the mating target for either a male object or a female object. That is, the mating record unit (310) can generate mating data by specifying the object that has become the mating partner while recording mating for a specific object as described above.

[0062] In one embodiment, the mating record unit (310) can generate second mating data for a mating target object corresponding to the first mating data. For example, the mating record unit (310) can generate first mating data for a female object and generate second mating data for a male object that is the mating target object corresponding to the first mating data. More specifically, while generating second mating data for a male object, the mating record unit (310) can automatically register information about a female object. That is, the mating record unit (310) receives a request from the user terminal (130) to generate first mating data for a female object and creates second mating data corresponding to it, thereby providing convenience so that the user does not need to separately input mating information for a male object through the user terminal (130).

[0063] Here, the second mating data may include the date of mating and information about the male or female individual. The mating record unit (310) may generate mating data that includes the date of mating and information about the individual that mated. For example, the mating record unit (310) may generate first mating data that includes the date of mating and information about the individual that mated, and may generate second mating data that includes the same date of mating and information about the individual that mated as the first mating data. For example, the diary generation unit (340) may generate a breeding diary of the female individual that mated based on the first mating data, and generate a breeding diary of the male individual that is the mating partner of the female individual based on the second mating data. This is explained in detail below.

[0064] Referring to FIGS. 7 and 9, the spawning record unit (320) can generate spawning data including at least one spawning record of a female individual. For example, the spawning record unit (320) can generate spawning data including the spawning date after mating of a specific female individual and information of the female individual that became the target of mating included in the mating information. More specifically, the spawning record unit (320) can generate spawning data (5143) including information on the mating date, first spawning date, second spawning date, and third spawning date of a specific female individual. In one embodiment, the spawning record unit (320) can generate spawning data after a preset period has elapsed since mating. For example, the spawning record unit (320) can generate spawning data related to the mating starting 20 days after mating.

[0065] In one embodiment, when mating data is generated, the spawning record unit (320) may generate spawning data that includes information (5141) about a female individual and information (5142) about a mating target individual that became the mating target for the female individual in association with the mating data. For example, the spawning record unit (320) may generate spawning data that includes information about female individuals and male individuals included in the mating data. For example, the spawning record unit (320) may generate spawning data that includes the spawning date of the female individual and mating data associated with the spawning, and the mating data may include information about the male individual that mated with the female individual. In this way, the spawning data may include information about the parents of the individuals to be born, and the hatching record unit (330) may generate hatching data that includes information about the parents at the time of the individual's hatching, which will be described in detail below.

[0066] In one embodiment, the spawning record unit (320) may generate spawning data by recording a plurality of spawning records of a female individual in a time series in relation to mating data. More specifically, the spawning record unit (320) may generate spawning data including a plurality of spawning records associated with one mating data. For example, the spawning record unit (320) may generate spawning data in relation to the mating data generated in 23.1.1, such that the first spawning of 23.1.20, the second spawning of 23.1.30, and the third spawning of 23.2.10, which were spawned through the mating, are spawnings associated with 23.1.1.

[0067] In one embodiment, the spawning record unit (320) may generate spawning data that does not include information about male individuals. Specifically, the spawning record unit (320) may generate spawning data that includes only information about female individuals. For example, the spawning record unit (320) may generate spawning data that includes only information about female individuals when a female individual spawns alone without mating. In this way, the spawning record unit (320) may generate spawning data that does not include data about male individuals in the case of solitary spawning (5161) where a female individual spawns alone. In this way, the spawning record unit (320) may generate spawning data that includes data about male individuals or may generate spawning data that does not include data about male individuals, depending on whether mating data for female individuals exists.

[0068] Referring to FIG. 8, the hatching record unit (330) can generate hatching data including a profile of a hatched individual in association with at least one spawning data. For example, the hatching record unit (330) can generate hatching data in accordance with a pet profile registration request (5151). For example, the profile of a hatched individual may include the name, birthday, adoption date (date of birth), gender, type, weight, and morph of the hatched individual. Here, information regarding the morph may be estimated, and this is described in detail below. Additionally, the profile of a hatched individual may include parent information of the hatched individual, and the father's information (5151a) and mother's information (5151b) may each include a photograph of the parent. The hatching record unit (330) can identify the parent information included in the hatching data through the previously generated spawning data. That is, the hatching record section (330) can generate hatching data by specifying parent information through the information of the female individual included in the previously generated spawning data and the male individual mated with the female individual.

[0069] In one embodiment, the hatching record unit (330) may generate hatching data in association with spawning data only when there is a parent data linkage request upon receiving a pet profile registration request (5151). That is, the hatching record unit (330) may not register the parent information included in the spawning data as the parent of the hatched individual if there is no parent data linkage request upon receiving the pet profile registration request (5151).

[0070] Here, the profile of the hatched individual may include information on male and female individuals included in the spawning data as parent information. That is, as described above, the hatching record unit (330) automatically includes information on male and female individuals included in the spawning data as parent information, thereby providing convenience to the user by not requiring the user to perform a separate operation to input parent information.

[0071] Here, the information of the female individual may include a photograph and morph of the female individual. That is, the user can check the parent information of the born individual by checking the hatching data generated through the hatching record unit (330), and can intuitively predict the morph of the born individual through the parent's photograph and morph. Additionally, the information of the male individual may include a photograph and morph of the male individual. The hatching record unit (330) may generate information for the female and male individuals to include the photographs and morphs of the respective individuals.

[0072] The diary generation unit (340) can generate a rearing diary for amphibians and reptiles based on mating data, spawning data, and hatching data. The diary generation unit (340) can generate a rearing diary by specifying the date each individual mated, spawned, and hatched based on mating data, spawning data, and hatching data. For example, when the diary generation unit (340) receives input that the individual was fed, spawned, and hatched on 23.6.1, it can generate a rearing diary by recording this in a pre-set diary template. As another example, the diary generation unit (340) can generate and update a rearing diary by receiving information about the weight of a specific individual on 23.6.1 and receiving information about the weight of a specific individual on 23.6.20, and by entering the weight information of the specific individual on each respective date. Here, the breeding diary can be composed of a pre-set diary template, which is explained in detail below.

[0073] In one embodiment, the diary generation unit (340) can display mating data, spawning data, and hatching data on a pre-set diary template. That is, the diary generation unit (340) can generate a rearing diary for a specific individual by displaying mating data, spawning data, or hatching data on a pre-set diary template. Here, the pre-set diary template may be in the form of a calendar on which mating data, spawning data, or hatching data is not displayed.

[0074] The morph estimation unit (350) can estimate the morph of a hatched individual based on male individuals and female individuals. In one embodiment, the morph estimation unit (350) can estimate the morph of a hatched individual by using an artificial intelligence model with information about male individuals and information about female individuals as input. Additionally, the morph estimation unit (350) can estimate the morph of a hatched individual by using a photograph of a hatched individual as input to the artificial intelligence model. The artificial intelligence model of the following other embodiments, including this embodiment, can be implemented using various existing artificial neural networks such as a Convolutional Neural Network (CNN). In one embodiment, the morph estimation unit (350) can estimate the morph of a hatched individual based on a rule-based method. In another embodiment, the morph estimation unit (350) can estimate the morph of a hatched individual as at least one morph. Accordingly, the user can share the estimated morph of the hatched individual through the morph estimation unit (350) with the user community and ask other users about the type of morph of the hatched individual.

[0075] In another embodiment, the morph estimation unit (350) can estimate the morph of the hatched individual based on the degree of color change resulting from the enhancement or loss of chromatophores by comparing the hatched individual with the parent individual. That is, the morph estimation unit (350) can estimate the morph of the hatched individual by comparing a photograph of the hatched individual with a photograph of the parent individual. Additionally, the morph estimation unit (350) can estimate the morph of the hatched individual based on the pattern of the hatched individual according to body location. For example, the morph estimation unit (350) can estimate the morph of a crested gecko based on the Upper Lateral, Lower Lateral, Dorsal, and Limb of the individual.

[0076] In one embodiment, the morph estimation unit (350) can estimate the morph of the hatched individual based on information about the female individual when the spawning data does not include information about the male individual. For example, the morph estimation unit (350) can estimate the morph of the hatched individual based only on information about the female individual when the hatching of the female individual is solitary spawning (5161) that occurs without mating. More specifically, the morph estimation unit (350) can estimate that the individual hatched according to the solitary spawning of the female individual has the same morph as the female individual.

[0077] Referring to FIG. 10, the spawning season determining unit (360) can determine at least one spawning record of a female individual associated with mating data and mating data as one spawning season. For example, if there is mating on 23.01.01 and spawning associated with said mating occurs on 23.01.20, 23.02.10, and 33.03.10, the spawning season determining unit (360) can determine the mating on 23.01.01 and the 1st to 3rd spawning associated with said mating as the 1st spawning season (5211). For another example, if the spawning season determining unit (360) receives input that there is mating on June 1, 23, and that spawning related to said mating occurs first on June 20, 23, and second on July 10, 23, the spawning on June 1, 23, and the first and second spawning related to said mating can be determined as the second spawning season (5212). For another example, if the spawning season determining unit (360) receives input that there is a solo spawning on September 10, 23, the solo spawning can be determined as the third spawning season (5213).

[0078] In one embodiment, the spawning season determining unit (360) may determine at least one spawning record included in the spawning data as one spawning season if the spawning data does not include information about male individuals. As described above, the spawning season determining unit (360) may determine the solitary spawning as one spawning season if the spawning data does not include information about male individuals and includes only information about female individuals.

[0080] FIG. 4 is a diagram illustrating the sequence of a method for generating an amphibian and reptile diary based on mating and spawning records according to an embodiment of the present invention.

[0081] Referring to FIG. 4, the method for generating an amphibian and reptile diary based on mating and spawning records can generate mating data for either a male or female individual of the amphibian or reptile through the mating record section (310) (S410).

[0082] A method for generating an amphibian and reptile diary based on mating and spawning records can generate spawning data including at least one spawning record of a female individual through a spawning record section (320) (S420).

[0083] A method for generating an amphibian and reptile diary based on mating and spawning records can generate hatching data including a profile of a hatched individual associated with at least one spawning data through a hatching record section (330) (S430).

[0084] A method for generating an amphibian and reptile diary based on mating and spawning records can generate a rearing diary for the amphibian and reptile based on mating data, spawning data, and hatching data through a diary generation unit (340) (S440).

[0086] Although the present invention has been described above with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the invention without departing from the spirit and scope of the invention as described in the following claims. Explanation of the symbols

[0088] 100: Amphibian and Reptile Diary Generation System Based on Mating and Spawning Records 110: User terminal 130: Amphibian and Reptile Diary Generator Based on Mating and Spawning Records 150: Database 210: Processor 230: Memory 250: User I / O Section 270: Network I / O Section 310: Mating Record 320: Spawning Record 330: Hatching Record Book 340: Diary Creation Book 350: Morph Estimation Section 360: Spawning Season Determination Section

Claims

Claim 1 An amphibian and reptile diary generation device based on mating and spawning records, comprising: a mating record unit for generating mating data for either a male or female individual of an amphibian or reptile; a spawning record unit for generating spawning data including at least one spawning record of the female individual; a hatching record unit for generating hatching data including a profile of a hatched individual in association with the at least one spawning data; a diary generation unit for generating a rearing diary for the amphibian or reptile based on the mating data, the spawning data, and the hatching data; and a morph estimation unit for estimating the morph of the hatched individual based on the male individual and the female individual. Claim 2 A mating and spawning record-based amphibian and reptile diary generation device according to claim 1, wherein the mating record unit specifies a mating target individual that has become the mating target for either the male individual or the female individual and generates first mating data. Claim 3 A mating and spawning record-based amphibian and reptile diary generation device according to claim 2, wherein the mating record unit generates second mating data of the mating target individual corresponding to the first mating data, and the second mating data includes the date of mating and information regarding the male individual or female individual. Claim 4 A mating and spawning record-based amphibian and reptile diary generation device according to claim 1, wherein the spawning record unit generates spawning data including information about the female individual and the mating target individual that became the mating target for the female individual in association with the mating data when the mating data is generated. Claim 5 A mating and spawning record-based amphibian and reptile diary generation device according to claim 4, wherein the spawning record unit generates spawning data by chronologically recording a plurality of spawning records of the female individual in association with the mating data. Claim 6 A mating and spawning record-based amphibian and reptile diary generating device according to claim 1, wherein the spawning record unit generates spawning data that does not include information about the male individual. Claim 7 An amphibian and reptile diary generation device based on mating and spawning records, wherein, in claim 1, the profile of the hatched individual includes information of the male individual and the female individual included in the spawning data as parent information. Claim 8 An amphibian and reptile diary generation device based on mating and spawning records, characterized in that, in claim 7, the information of the female individual includes a photograph and morph of the female individual. Claim 9 A mating and spawning record-based amphibian and reptile diary generation device according to claim 1, wherein the diary generation unit displays the mating data, the spawning data, and the hatching data in a preset diary template. Claim 10 delete Claim 11 A mating and spawning record-based amphibian and reptile diary generation device, wherein, in claim 1, the morph estimation unit estimates the morph of the hatched individual based on information about the female individual when the spawning data does not include information about the male individual. Claim 12 An amphibian and reptile diary generation device based on mating and spawning records, characterized in that, in claim 1, it further comprises a spawning season determining unit that determines the mating data and at least one spawning record of the female individual associated with the mating data as one spawning season. Claim 13 A mating and spawning record-based amphibian and reptile diary generation device according to claim 12, wherein the spawning season determining unit determines at least one spawning record included in the spawning data as one spawning season when the spawning data does not include information about the male individual. Claim 14 A method for generating an amphibian diary based on mating and spawning records, comprising: a mating record step for generating mating data for either a male or female individual of an amphibian or reptile; a spawning record step for generating spawning data including at least one spawning record of the female individual; a hatching record step for generating hatching data including a profile of a hatched individual in association with the at least one spawning data; a diary generation step for generating a rearing diary for the amphibian or reptile based on the mating data, the spawning data, and the hatching data; and a morph estimation step for estimating the morph of the hatched individual based on the male individual and the female individual. Claim 15 A computer program recorded on a computer-readable recording medium that is combined with a computer, which is hardware, to enable the method of claim 14 to be performed.

Images