JP3343138B2 - User information management method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing user information in a communication service system for managing user information using a user ID in a personal computer communication service or the like. recent years,
In the information society, the use of personal computer communication services is also increasing, and users are also individual users, group users,
The tendency of users other than the original user appears, and the number of users is steadily increasing and diversifying. For this reason, there is a need for a user information management method that can appropriately cope with such an increase and diversification of users.

[0002]

2. Description of the Related Art Conventionally, in a user information management method in a personal computer communication service or the like, every user is regarded as an individual user, a fixed-length user ID and a password are given to one user, and a billing destination is charged for each user ID. In addition, a method of registering and managing user additional information such as a center output destination is adopted.

[0003]

However, in such a conventional user information management method, there are group users requesting that "there are many users but only one billing address is required" or other services. When using the service system from the system, it is necessary to assign a user ID and a password unique to the system to each user, and to register and manage user additional information.

In this case, a user ID belonging to a group user
Must be registered many times with the user additional information such as the same billing billing address, and the DA storing the user additional information must be registered.
The SD resources increase, and the work required to register and change the user information also increases. The present invention has been made in view of such a conventional problem, and can flexibly cope with any user form such as an organization, a company, and an individual, and efficiently manages the registration of user-related information while minimizing the necessary registration. It is an object of the present invention to provide a user information management method for a communication service system which is enabled.

[0005]

FIG. 1 is a diagram illustrating the principle of the present invention. First, the present invention allocates a unique user ID to each user 12 who has subscribed to the communication service system 10, and provides a service based on the user ID included in the service request when receiving a service request from the user 12. Targets service systems.

According to the present invention as such a user information management system, a plurality of user information management systems are provided, one for each user.
Of the original user IDs as a group
Give specific meaning that can be set in multiple layers according to
A unique group ID is set . When a group ID is set, one user ID is formed from the first group ID to the original user ID. When no group ID is set, the original user ID is set.
Configure the user ID only in D, a service request using the user I D, have <br/> row to provide services based on the service request, supplementary information der the group ID registered in advance
Lower-level user based on no-check information of lower-level user
Judge whether the process corresponding to the ID of
No processing is necessary for the determination result corresponding to the lower user ID.
If yes, check the validity based on the original user ID
The service is provided without performing the processing .

[0007] Here, unique user additional information can be registered in the group ID, and the user additional information registered in the specific group ID is registered in another group I belonging to a lower order.
D and the original user ID are bound by the registered additional information. As for the original user ID, unique user additional information can be registered independently, and the original user ID is restricted by the registered user additional information.

[0008] As the user additional information registered in the group ID or the original user ID, billing destination; postal code, address, telephone number, FAX number, company name, section name, name, etc. Center output destination; postal code, Address, phone number, F
AX number, company name, department name, name, etc. Information on whether it is paid or free Service authority information; information indicating the type of service provided; lower user ID no check information.

[0009] In the case where the billing destination and the paid information of the service provision are registered as the user-related information, a file of the billing input record indicating the correspondence between the user ID actually used by the user and the service fee is created in real time at the end of the service. Then, a bill file for the billing destination registered in the user ID by the badge process is created for this file and output.

[0010] As for the service authority information, each type of service to be provided or a combination of a plurality of types is registered. Further, the no-check information of the lower user ID is registered when the group ID indicates that the user 16 is the user 16 of another communication service system 14, and the processing of the lower user ID is not required.

[0011]

According to the user information management method of the communication service system of the present invention, an ID assigned to each user by the conventional user information management method is newly set as a group ID as an original user ID. A single user ID in a variable-length format is configured using only the group ID of one or more layers, the original ID of the last layer, and the original user ID.

For this reason, when a group ID is set to a specific group of a plurality of original user IDs and the group IDs are set in multiple hierarchies, specific user additional information such as a billing billing destination is registered in a higher group ID. For example, the lower group ID is restricted by the user additional information registered in the upper group ID, and the number of registered user additional information can be minimized.

As a result, the DASD storing the user information
Effective use of resources can be achieved, and the work of registering and changing user information can be reduced.

[0014]

FIG. 2 is an explanatory diagram showing the structure of a user ID used in the user information management method of the present invention. In FIG. 2, the structure of the user ID used in the present invention includes a basic type 1 shown in FIG. 2A and a basic type 2 shown in FIG. 2B. You can make molds.

First, as the user ID of the present invention, a unique ID assigned to one user in the conventional user information management system is treated as an original user ID, and a plurality of the original user IDs are defined as one group with a specific meaning. Is newly set. The basic type 1 in FIG. 2A shows the configuration of a user ID when a group ID is set for the original user ID.

In this example, a group ID is set as a group of unique original user IDs of each of A, B, and C. Therefore, the user IDs of Mr. A, Mr. B and Mr. C are composed of “Group ID + Original ID”. FIG. 2B shows a case where only the original user ID is set. For example, the original user ID of Mr. A is the one user ID of the present invention.

The group I shown in the basic type 1 of FIG.
D can be set in multiple layers as needed. For example, FIG. 2C shows the configuration of the user ID when the group IDs for A, B, and C are set in a plurality of layers. Next, as for the user ID of the present invention, as shown in the basic type 1 of FIG. 2A, it is possible to register user additional information unique to the group ID. When the user additional information is registered in the group ID as described above, the original user I of A, B, and C located below the group ID is registered.
D is bound by the contents of the incidental matter set in the group ID.

The registration of user-related items can be independently performed not only for the group ID but also for the original user ID. In addition, even when a group ID of FIG. 2C is set in a plurality of layers, a specific user incidental item can be registered for each group ID of each layer. FIG. 3 is an explanatory diagram showing the types of common incidental information registered in the user ID of the present invention.

In FIG. 3, common additional information that can be registered in the group ID or the original user ID in the user ID includes the paid / free information service / authority information of the destination output from the billing billing center and the lower user ID. There is no check information. here,
As the billing destination and the center output destination, for example, a postal code, an address, a telephone number, a FAX number, a company name, a department name, a name, and the like are used. The charge / free information is used when a bill file is created for a billing party after the system provides the service requested by the user.

The service authority information is information indicating the type of system service that can be used by the user ID. For example, the service authority information shown in FIG. 4 can be registered. In FIG. 4, ranks 1 to 5 are provided as ranks of service authority information that can be registered, and services that can be used according to this rank include DB search, games, forums, extended functions, and center output. The services indicated by ○ can be used.

Of course, the service authority information for specifying the usable services is not limited to the combination of the service types according to the ranks 1 to 5, and the service authority information which can use each service individually may be registered. FIG. 5 is an explanatory diagram showing the structure of a user ID used in the present invention and the format of an ID code used by each user corresponding to the structure of the user ID.

FIG. 5A specifically shows the structure of the user IDs of the users A, B, C and D. First, the billing destination is registered as the user-common supplementary information in the first group ID of the first hierarchy. Therefore, the original user ID of each of A to D is bound by the billing destination registered in the first group ID. That is, the billing party is the same billing party regardless of which of A to D makes a service request to the system.

The second layer is composed of two sides, A and B, and C and D.
A group ID is set for each group. The destination of the center output is individually set as the user-common supplementary information for each of the group IDs of the second hierarchy. For this reason, the center output obtained by the service request of Mr. A and B is given to the registered destination, and the center output in response to the service request from Mr. C and D is sent to another destination. In addition, service authority information is registered for each of the group IDs in the second hierarchy.

For Mr. A and Mr. B, the original user ID is further registered via the group ID of the third hierarchy. On the other hand, for C and D, the original user ID is set following the second level. Further, for A and D, service authority information unique to the original user ID itself is registered. In the configuration of the user ID shown in FIG. 5A, for example, the user ID used by Mr. A has the format configuration shown in FIG. 5B. That is, the first layer is the first group ID.
Next, the supplementary information of the billing destination shown in is provided, the group ID of the second hierarchy, the center output destination registered as supplementary information, and the paid / free information are provided, and the original user ID as the third hierarchy is provided. The service authority information is provided, and the end ID is provided at the end.

FIG. 5 shows the user ID of Mr. D.
(C) A group ID and registered user additional information are provided in each of the first, second, and third layers, and an end ID is set last. As a result, the user ID of Mr. A
The data lengths of the user IDs of Mr. and Mr. D are different, and the user IDs are configured in a variable length format according to the hierarchical structure of the user IDs.

Next, the user ID of the present invention will be specifically described separately for a group user and an individual user. FIG.
Shows the specific configuration of the user ID of the present invention applied to the group user, and the first group ID represents the name of the group user "A industry", and the group ID of the next second hierarchy is Are set with group IDs "SAPPORO", "TOKYO", and "FUKUOKA" indicating three branches of Sapporo, Tokyo and Fukuoka of the A industry. And the third
The hierarchy is the original user ID indicating the department or section belonging to each branch.

In the registration of the user-related supplementary information, the billing destination is registered for the first group ID "A industry". Therefore, the original information of each branch in Sapporo, Tokyo and Fukuoka having the lower group ID and the original user ID is registered. All charges for the service requested by the user are collectively paid to the billing destination registered in the first group ID.

For the group IDs of the second hierarchy, the common user additional information of the center output destination is registered independently. Therefore, the original user I of each branch
The center output based on the service requested in D is sent to a unique destination registered for each branch. FIG. 7 is an organization configuration diagram of the industry A in the configuration of the user ID in FIG. 6, and the user ID shown in FIG. 6 corresponding to this organization configuration diagram.
Is shown. Of course, the number of layers is not limited to the third layer, and any number of layers can be added as needed.

FIG. 8 is an explanatory diagram showing a specific example of a user ID for an individual user. In the case of an individual user, for example, as shown in FIG.
"IRA0001", and appropriate user additional information can be registered for this original user ID. In this embodiment, two user additional information, a billing address and a center output address, are registered. .

The format of the user ID used by the individual user shown in FIG. 8A is, as shown in FIG. 8D, following the original user ID "HIRA0001" and attached to the billing address and the center output destination. Information is provided, and the end ID is set at the end. Furthermore, in the user information management method of the present invention, for example, when services can be provided mutually between two communication service systems, a service request from a user belonging to another system can be handled. The user ID that can be set is set.

FIG. 9A shows that a system A and a system B exist, and the user information management method according to the present invention is applied to the system A. A user belonging to the system B can make a service request to the system A via the service center. On the system A side, the user ID making a service request from the other system B is configured as shown in FIG. 9B. That is, the first group ID indicates that the system B is used, and an appropriate original user ID set in the system B is provided following the group ID.

The no-check information of the lower-level user ID is always registered for the head group ID indicating the use from the system B. In this example, the billing destination is also registered. FIG. 9C shows FIG.
One original user I of system B shown in (b)
3 shows a format configuration of a user ID code for requesting a service of a system A used in D.

That is, a group ID “NIF” indicating a service request from the system B is set in the first hierarchy, and subsequently, no-check information of a billing address and a lower user ID is provided. Subsequently, an original user ID “GDC9999” used in the system B is provided, and an end ID is added last. When the no-check information of the lower user ID corresponding to the group ID is registered in this way, it means that the ID collation and the processing of the additional information are not performed any more, even if any ID follows.

For this reason, the other system B sends the system A
Even if you make a service request using your user ID,
System A without being aware of the unique ID of system B
Side can perform processing according to the user ID. FIG.
Reference numeral 0 denotes a group ID of one or more hierarchies, an original user ID, and a collation of the user ID on the system side when the service request is received by the user ID of the present invention, which is a registration of user additional information for each ID.
It is the flowchart which showed the acquisition processing of authority information.

In FIG. 10, upon receiving a service request from a user, the host computer of the system divides the user ID for each layer in step S1 and turns off the authority flag. Next, in step S2, the first hierarchical ID in the user ID is collated with the ID registered in advance, and if there is no matching ID in step S3, an unauthorized user ID process is performed in step S4. As shown in FIG. 11B, this illegal user ID processing outputs an error message to the terminal as a user ID error, disconnects the terminal side line, and ends the processing.

If there is a registered ID that matches the first hierarchical ID in step S3 of FIG. 10, the process proceeds to step S5,
It is checked whether service authority information is set in the first hierarchical ID of the user ID. If so, the authority flag is turned on in step S6 as service authority acquisition success. If not set, the process proceeds to step S7.

In step S7, the first level I of the user ID
It is checked whether lower-level ID no-check information is set in D. If not set, the process proceeds to step S8, and it is checked whether the end ID has been set. If not set, the process proceeds to step S9, and it is checked whether or not the next layer ID has been input. If not, an unauthorized user ID process is performed in step S23.

When the next layer ID is input, step S10 is performed.
Then, the hierarchy that has already been compared is lowered by one, and the IDs under the hierarchy and the input next hierarchy ID are compared. As a result of the collation, it is checked whether or not there is a matching ID in step S11, and if not, an unauthorized user ID process is performed in step S24. If there is a matching ID, the process proceeds to step S12 to check whether the authority flag is on or off.

If the authority flag has not been turned on, the flow advances to step S25 to check whether or not the service authority information has been set, and if so, the authority flag has been turned on in step S26 as success in obtaining the service authority. . If the authority flag has already been turned on in step S12, the flow returns to step S7 again, and after the presence / absence of the setting of the lower ID no check flag and the presence / absence of the end ID in step S8, the next hierarchy ID is input in step S9. Process.

In the process of processing each layer ID by repeating steps S7 to S12, for example, in step S7, the lower ID
When the setting of the no-check information is determined, step S13 is performed.
Proceed to. The setting of the lower ID no-check information is performed when a service request from another system is received. In step S13, the next layer I
It is checked whether or not D has been input, and if not, an unauthorized user ID process is performed in step S14. Next level ID
Is input, the flow advances to step S15 to check whether the authority flag is on or off. If the authority flag is off, ID mistake registration processing is performed in step S16. As shown in FIG. 11 (c), this ID mistake registration processing determines that there is a user ID registration error, outputs an error message to the terminal, disconnects the terminal side line, and ends the processing.

If the authority flag is ON in step S15, the flow advances to step S17 to perform a valid user ID process. This legitimate user ID process is shown in FIG.
As shown in (a), a service within the range of services registered in the user ID and determined by the service authority information is started, and the process ends when the service is completed. Further, if it is determined in step S8 that the end ID has been set, the process proceeds to step S18, where the presence or absence of the input of the next layer ID is checked. If the next layer ID is input, there is an error and the process proceeds to step S19. Perform the unauthorized user ID process. If the next layer ID is not input, the process proceeds to step S20, where the authority flag is checked on, and if it is off, the ID error registration process is performed in step S21. If the authority flag has been turned on, the process proceeds to step S22, a valid user ID process is performed, and a series of processes ends.

Next, a charging process in the user information management method using a user ID according to the present invention will be described. Each time a user makes a service request to the host computer of the communication service system and receives the service once, the host computer creates a charging input record as shown in FIG. 12 and registers it in the input file for charging processing.

The accounting input record shown in FIG. 12 is composed of a combination of a service area with a user ID actually used by the user. User I actually used by user
D is, for example, a user ID shown in the figure.
It consists of a combination of D and the original user ID, or only the original user ID. On the other hand, the service charge is calculated by multiplying the unit price per hour by the use time for a database search (DB search), and the service charge is calculated by multiplying the page unit price by the number of output pages for the center output idea. Is calculated.

The input file in which the charging input record shown in FIG. 12 is registered is created in advance in response to a service request or in real time. On the other hand, the process of acquiring the billing destination based on the input file of the billing process is performed by a badge process, for example, once a day at a predetermined time. FIG. 13 and FIG. 14 are flowcharts showing a process of acquiring a billing destination based on the input file of the billing process. The process is repeated until there is no more input file.

In FIG. 13, first, in step S1, the charge input records in the input file are sequentially read.
The user ID registered in one charging input record is divided for each layer, and the charging information flag is turned off. Next, in step S2, the first layer ID of the user ID is compared with the first layer ID registered in advance. In step S3, I
If D does not match, charging error processing is performed in step S4. In this accounting error process, the user ID and the service fee are written in an error file as shown in FIG.

If a match of the first layer ID is obtained in step S3, the flow advances to step S5 to check whether or not there is a fee. If it is not charged, the process proceeds to step S6, the billing information flag is set to ON as the successful acquisition of the billing destination, and the normal non-billing process is performed in step S7. This non-charging normal processing outputs a list of service usage status as shown in FIG.

If there is a charge in step S5, it is checked in step S8 whether a billing destination has been set. If the billing destination has been set, the process proceeds to step S9,
The charging information flag is turned on as a success in acquiring the charging billing destination, and the process proceeds to step S10. If the billing address has not been set, the process directly proceeds to step S10. In step S10, it is checked whether or not the charging information flag is on. If the flag is on, the process proceeds to step S11, where normal charging processing is performed. In this normal charging process, the user is charged for the service fee at the billing destination obtained as shown in FIG. 15A, and the service usage status is output as a list.

If the charging information flag is off at step S10, the process proceeds to step S12 in FIG.
It is checked whether D-no check information is set. If lower ID no check information is set, step S13
Then, it is checked whether or not the charging information flag is on. If it is off, a charging error process is performed in step S14. If the charging information flag is ON, the normal charging process is performed in step S15.

If the lower ID no check flag has not been set in step S12, the flow advances to step S16 to check whether the end ID has been set. If the end ID is set, on / off of the charging information flag is checked in step S17, and if it is off, step S1 is performed.
In step S8, a charging error process is performed.
In step 9, the accounting normal processing is performed.

If the end ID has not been set in step S16, the flow advances to step S20 to check whether or not the next layer ID exists in the input data. If not, the charging error process is performed in step S21. Tier ID
Is checked against Subsequently, the ID that matches in step S23
If there is no ID, a charging error process is performed in step S30. If not, the charging information flag is turned on in step S25 as the successful acquisition of the charging billing destination, and the
The normal processing of No Charge 26 is performed.

If the fee is paid in step S24, the flow advances to step S27 to check on / off of a billing information flag. If the billing information flag is off, check in step S28 whether a billing destination is set and set. If there is, step S2
At 9, it is determined that the billing destination is successfully obtained, and the billing information flag is turned on. If the charging information flag is turned off in step S27, or if the charging billing destination is not set in step S27, the process returns to step S10 in FIG.
The process proceeds to the next layer.

[0052]

As described above, according to the present invention, a new group ID is set using a conventional user ID as an original user ID, and a variable-length user ID having one or more hierarchical structures of the group ID is set. Is used to manage user information in a communication service system, so that user information can be managed flexibly in response to diversifying user forms.

Further, by registering the user additional information as the common information in the upper user ID, the lower group ID can be restricted, so that the DASD resources for storing the user information can be effectively used. Further, since the number of registered user additional information can be reduced, the amount of processing required for registration, change, and management can be reduced.

Further, the present invention can be applied to mutual entry from another communication service system, and a compatible service can be provided without losing the original user ID of each system.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is an explanatory diagram showing a basic configuration of a user ID used in the present invention.

FIG. 3 is an explanatory diagram of supplementary information registered in a group ID in a user ID according to the present invention.

FIG. 4 is an explanatory diagram of service authority information registered in a group ID according to the present invention.

FIG. 5 is an explanatory diagram showing a format configuration corresponding to a user ID according to the present invention.

FIG. 6 is an explanatory diagram showing a specific example of a user ID of the present invention for a group user

FIG. 7 is an organization configuration diagram of an organization corresponding to the user ID in FIG. 6;

FIG. 8 is an explanatory diagram showing a specific example of a user ID of the present invention for an individual user

FIG. 9 is an explanatory diagram showing a user ID of the present invention used for a request from a user belonging to another communication service system;

FIG. 10 shows a user ID in the system host of the present invention.
Flowchart showing the process of collating and acquiring the service authority information

FIG. 11 is an explanatory diagram showing details of a valid user ID, an unauthorized user ID process, and an ID mistake registration process of FIG. 10;

FIG. 12 is an explanatory diagram of a billing input record created in an input file for each user service by the system host of the present invention.

FIG. 13 is a flowchart showing a billing destination acquisition process based on the input file of FIG. 12;

FIG. 14 is a flowchart (continued) showing a billing destination acquisition process based on the input file of FIG. 12;

FIG. 15 is an explanatory diagram showing details of a normal charging process, a normal non-charging process, and a charging error process in FIGS. 13 and 14;

[Explanation of symbols]

 10: Communication service system 12: User 14: Other communication service system 16: User of another system

Continuation of the front page (56) References JP-A-63-178329 (JP, A) JP-A-64-70860 (JP, A) JP-A-64-66768 (JP, A) JP-A-63-290042 (JP) , A) Naoga Taga and four others, "ISDN Utilization Technology for Engineers", Interface June 1992, Japan, CQ Publishing Company, June 1, 1992, Vol. 18, No. 6, p. 100-200 Jun Murai, "Special Feature Network for Academic Researchers," Computer Science magazine, February February 1990, Japan, Kyoritsu, February 1, 1990, p. 4-39 (58) Fields surveyed (Int. Cl. ⁷ , DB name) G06F 15/00

Claims (11)

(57) [Claims] 1. A assigns a unique user ID for each user subscribing to the system, provides a service based on the user ID included in the service request upon receiving a service request of the user or al communication services Multiple original users, one for each user in the system
IDs are set as one group and set in multiple layers as necessary
A unique group that gives a specific meaning that can be done
Setting an ID, and, if the group ID is set, one user ID from the first group ID to the original user ID
Performing the step of configuring the steps of: configuring the user ID only in the original user ID if not set the group ID, the providing of services based on the service request and the request using the user I D And the supplementary information of the group ID registered in advance.
The lower-level user's
Determine whether the process corresponding to the ID is unnecessary
Step and the processing in which the determination result corresponds to the lower-order user ID are unnecessary.
If yes, check the validity based on the original user ID
Steps to provide services without processing
It features and be Ruyu over The information management method to become. 2. A In User chromatography The information management method according to claim 1, wherein the group ID may be registered specific supplementary information, the supplementary information registered in a specific group ID subordinate Other group ID and original user I
D is bound by the registered supplementary information.
Ruyu over The information management method. 3. In User chromatography The information management method according to claim 1, wherein the original user ID alone can create a specific supplementary information, the original user ID is constrained by supplementary information registered It features and be Ruyu over the information management method the Rukoto. 4. In User chromatography The information management method according to claim 2 or 3, wherein, as supplementary information to the group ID or the original user ID, characteristics and be Ruyu over The information that it has registered the billing billing Management method. 5. In the User over The information management method according to claim 4, wherein, zip code as the billing destination, address, telephone number, FA
X number, company name, department name, characterized in that it has registered the name, etc. and be Ruyu over The information management method. 6. In User chromatography The information management method according to claim 4, wherein, when registering the billing billing and pay information services provided as supplementary information to the group ID or the original user ID at service termination Create a file of charging input record indicating the correspondence between the user ID actually used by the user and the service fee, and create and output a billing file for the charging billing destination registered in the user ID by the badge processing for the file. It features and be Ruyu over the information management method that. 7. In User chromatography The information management method according to claim 2 or 3, wherein, as supplementary information to the group ID or the original user ID, to characterized in that registered the destination of the center output to service requests Ruyu over The information management method. 8. In the User over The information management method according to claim 7, wherein, zip code as the destination of the center output, address, telephone number, FAX number, company name, department name, that has registered the name, etc. It features and be Ruyu over the information management methods. 9. In User chromatography The information management method according to claim 2 or 3, wherein, as supplementary information to the group ID or the original user ID, to characterized in that registered a price or free services provided Ruyu over The information management method. 10. In User chromatography The information management method according to claim 2 or 3 wherein the, as supplementary information to the group ID or the original user ID, and registers the service authority information indicating the type of service provided It features and be Ruyu over the information management methods. 11. In User chromatography The information management method according to claim 10, as the service authority information, features and to Ruyu over to register the each kind or more kinds of combinations of services provided The information management method.