KR100575956B1 - Generation of Standardized Subscriber Information for Wireless Mobile Communication Service and Conversion into Specific Operator Information - Google Patents

Abstract

The present invention relates to a method for generating standardized subscriber information for wireless mobile communication service and converting into specific service provider information. If the XXX.subs file 30 is given as an input of the conversion tool 34 for generating a standard subscriber information data file together with the Convert.ini file 32, the conversion tool 34 for creating a standard subscriber information data file is input. The standard subscriber information data file 36 is generated using the XXX.subs file 30 and the Convert.ini file 32. The standard subscriber information data file 36 generated as described above is input to the developer information data file generation tool 40 for each developer together with the ReConvert.ini file 38, and for generating the subscriber information data file for each developer. The tool 40 receives the standard subscriber information data file 36 and the ReConvert.ini file 38, and stores XXX values converted from the standard subscriber information data file to match the subscriber schema defined for each developer. Create a .subs file 42.

Description

Generation of Standardized Subscriber Information for Wireless Mobile Communication Service and Conversion into Specific Operator Information

The present invention relates to a method for more efficiently and conveniently using subscriber-related information that a mobile mobile communication has inevitably for providing basic services and various additional services provided in a wireless mobile communication system. The present invention relates to a method of generating standardized subscriber information for a mobile communication service and converting it into specific service provider information.

Looking at the prior art as follows. Conventionally, the methods implemented for providing a mobile mobile communication service are different from each implemented carrier or wireless mobile communication system (DCS: Digital Communication System, PCS: Personal Communication System, Cellular). Although the necessary information and values to be stored are defined for the service defined in the international standard, even if there are no regulations or specific regulations for the specific information required by each country and operator using the wireless mobile communication system, Depending on the implementation method of the developer who developed the communication system, the contents and values of the information required for the implementation may be dealt with.

For the above reasons, the service operating entity provides a common wireless mobile communication service using each system developed by different developers. Although the wireless mobile communication service provided by the above system seems to provide the same service, in practice, the methods and necessary information for providing the service are different for each developer.

Due to the above constraints, the service operating entity has no way of performing a particular subscriber's information to different systems with better performance and resources in the system depending on the operation method and policy. There was no.

The purpose of the wireless mobile communication system is to provide a variety of services to the wireless mobile subscribers to create added value and profit. In order to achieve the above-described business purpose, the wireless mobile communication service providers, which are service service providers, intend to purchase a system that meets their business purpose among products of various system developers. This phenomenon occurs anywhere in the world.

However, there is a problem that occurs in accordance with the above process, which is different from the various services that must be provided in the wireless mobile communication system defined by the international standards of the wireless mobile communication system developers implement the service Because they use the information required for the information and the values defined for the information, it is possible to find the commonalities of governments used for wireless mobile communication services even for products of different system developers. However, even if there is a specification of information required for the service for a specific service required by a certain country or a specific service provider, even if the system provides the same service according to the development direction of the system developer and the implementation method used at the time of development. The information required for the implementation and the contents of the required values are different for each developer.

For the above reasons, the wireless mobile telecommunications service provider, which is the service operator, cannot actively and efficiently use all system resources in accordance with their service policy and business direction. In other words, it is not possible to extract or port subscriber information necessary to a specific system having more excellent performance and sufficient system resources than the subscriber information in a specific system.

For example, when there is a need for a service operator to port cellular subscriber information to a DCS system that can perform more service and perform more service functions, there has been no way to accomplish this conventionally.

In addition, even in the same DCS and PCS systems, the performance of the system is significantly reduced due to the number of subscribers exceeding the system capacity. We will try to port the extracted subscribers to the system with more resources in the system resources.

However, such functions are not supported conventionally. However, the same developer's system can be extracted and transplanted. However, subscriber extraction and porting between other systems is not possible.

The reason for the above is that even in a wireless mobile communication system providing a service, each developer has an information element used to develop such a service, and the information element and the information element values as described above are implemented by the developer. This is because they are different from each other, and because of this, the structure of subscriber information used by each developer is also different, and thus, subscriber information in different systems as described above cannot be shared with each other to extract or transplant subscribers.

As described above, the wireless mobile communication service providers, which are service operators, have a lot of difficulties in the management of the system and the development of the business direction according to the policy change of the service.

The present invention was devised to solve the above problems of the prior art, and can be solved by the following two methods.

First, the service operator provides the system developer with predetermined information about the subscriber information and the values necessary to provide the above services for all the wireless mobile communication supplementary services. Each developer creates the same format and database system. As described above, a database of the same format and content is generated for each developer. However, since the database systems used by the respective developers are different, this process also needs to be converted to a common data format. If the common database content and format are generated by accepting the conversion process to the common data format, the content of the subscriber information used by each developer may be the same, but the above method is not practically possible due to various constraints. And cannot be used.

In the second method, the contents of the new standard subscriber information including both the information common to the information of the different wireless mobile subscribers for each developer and the values for the specific information owned by each developer and Providing a method for creating a format for the standard information value that each information content should have, and converting the subscriber information existing for each developer to the standard information format and converting it to the standard information format. On the contrary, the above problems are solved by the service operator of the above-mentioned wireless mobile communication system by providing a tool which can convert the subscriber information content of the standard information format into the subscriber database format existing in the system of a specific system developer.

Therefore, it is an object of the present invention to convert the above-described standard format creation method and a tool and a standard information format that can convert a database format existing by each developer into a standard information format into a database format existing by each developer. It aims at providing the manufacturing method of the tool which can be provided.

In addition, in the reality that each developer provides a different database to provide the same service, the wireless mobile telecommunication operator uses the currently operating system more conveniently and efficiently according to their service policy and system resource usage direction. Its purpose is to provide a way to manage it.

Other objects and advantages of the present invention will become more apparent from the following detailed description of the invention and the accompanying drawings.

In order to achieve the above object, according to the present invention, a preferred embodiment of the standardized subscriber information generation method for a wireless mobile communication service,

Defining a standard subscriber information schema including all the information existing in common with the information existing for each developer for the subscriber information for the wireless mobile communication service existing for each developer;

Converting the subscriber information existing for each developer using the standard subscriber information schema into a standard subscriber information data file using a conversion tool for generating a standard subscriber information data file;

Defining the subscriber schema information conversion criterion information necessary for generating the standard subscriber information data file using a mapping table for generating standard subscriber information data;

Converting the subscriber information data file into subscriber information existing for each developer by using a conversion tool for generating a subscriber information data file for each developer; And

And defining the subscriber schema information conversion criterion information necessary for converting the standard subscriber information data file into subscriber information existing for each developer by using a mapping table for generating subscriber information data for each developer.

In the present embodiment, the standard subscriber information schema defines information about the identifier of the attributes, the name of the attributes, the size of the attributes, the meaning of the attributes, the range of values that the attributes can have, and the meaning and default value of the attribute values. It is desirable to have

In the mapping table for generating standard subscriber information data, when the subscriber information existing for each developer is converted into the standard subscriber information data, what size and location should be stored for each attribute and additional information for each attribute It is preferable that verification information is stored.

The mapping table structure for generating the standard subscriber information data preferably includes mapping table header information for generating the standard subscriber information data.

Preferably, the mapping table structure for generating standard subscriber information data includes information on the total number of attributes existing in the standard subscriber information schema.

Preferably, the mapping table structure for generating standard subscriber information data includes identifier information of an attribute defined in the standard subscriber information schema.

Preferably, the mapping table structure for generating standard subscriber information data includes size information of an attribute defined in the standard subscriber information schema.

Preferably, the mapping table structure for generating standard subscriber information data includes start position information of attribute information in each developer-specific subscriber table that matches an attribute defined in the standard subscriber information schema.

Preferably, the mapping table structure for generating standard subscriber information data further includes standard subscriber information schema and name information for identifying each developer's subscriber information schema.

The mapping table for generating subscriber information data for each individual company should be stored in which location and size for each attribute when converting subscriber information existing in the standard subscriber information data file into subscriber information data for each developer. It is preferable to further include additional verification information for each of the attributes,

Preferably, the mapping table structure for generating subscriber information data for each developer includes mapping table header information for generating subscriber information data for each developer.

It is preferable that the mapping table structure for generating subscriber information data for each developer includes information on the total number of attributes existing in the subscriber information schema for each developer.

It is preferable that the mapping table structure for generating subscriber information data for each developer includes identifier information of an attribute defined in the subscriber information schema for each developer.

It is preferable that the mapping table structure for generating subscriber information data for each developer includes size information of an attribute defined in the subscriber information schema for each developer.

The structure of the mapping table for generating subscriber information data for each developer may include starting position information of attribute information in a standard subscriber information data file that matches the attribute defined in the subscriber information schema for each developer.

Preferably, the mapping table structure for generating subscriber information data for each developer includes identifier information of an attribute defined in a standard subscriber information schema.

Preferably, the standard subscriber information data file has standard subscriber information data stored in a text mode.

Preferably, the standard subscriber information data information is generated by using a conversion tool for generating standard subscriber information data file for subscriber information existing for each developer.

Preferably, the standard subscriber information data information is used as an input value of a conversion tool for generating a subscriber information data file for each developer when converting the subscriber information data for each developer necessary for each developer.

The standard subscriber information data file includes information indicating which developer information of a developer is converted into a standard subscriber information data file, database version information of any developer converted into the standard subscriber information data file, and generating the standard subscriber information data file. Date and time information, the number of subscribers converted by station number, the identifier indicating the type of attribute used in the standard subscriber information data file, the attribute value of the standard subscriber information data, and the information indicating the end of the standard subscriber information data file. It is preferably configured to include.

According to the present invention for achieving the above object, a method of generating standardized subscriber information and converting into specific operator information for a wireless mobile communication service,

Entering the XXX.subs file along with the Convert.ini file into an input of a conversion tool for generating a standard subscriber information data file;

Generating a standard subscriber information data file by the conversion tool for generating the standard subscriber information data file;

Entering the standard subscriber information data file into an input value of a tool for generating a subscriber information data file for each developer together with a ReConvert.ini file; And

And generating a XXX.subs file by the tool for generating subscriber information data for each developer.

In the present embodiment, the XXX.subs file is preferably a subscriber information data file for each station number extracted in a subscriber table existing for each developer currently operating.

The information in the XXX.subs file is preferably a value generated by a subscriber information data schema defined for each developer.

Preferably, the XXX.subs file generated in the last step of the performing step is a file storing subscriber information for each station number generated by the conversion tool for generating subscriber information data file for each developer,

The content of the XXX.subs file is preferably a value obtained by converting the information of the standard subscriber information data file to fit the subscriber schema defined for each developer.

Hereinafter, a detailed operation principle of the present invention will be described with reference to the drawings. The present invention is largely composed of six regions. By using the standard subscriber information schema and the standard subscriber information schema, the subscriber information for the wireless mobile communication service existing by each developer includes all the information existing in common with the information existing by each developer. A conversion tool capable of converting the subscriber information existing for each developer into a standard subscriber information data file, a mapping table in which subscriber schema information conversion reference information necessary for generating the standard subscriber information data file is defined, and the standard subscriber information. The subscriber schema information necessary for converting the data file into the subscriber information existing for each developer is configured to include mapping table information defined.

Looking at the structure and function of each of the components of the urethra as follows. First, in the standard subscriber information schema, identifiers of attributes, names of attributes, sizes of attributes, meanings of attributes, ranges of values that attributes can have, meanings of default values, default values, and the like must be defined. The conversion tool for generating a data file is a conversion tool for converting subscriber information existing for each individual company into a standard subscriber information data file based on the standard subscriber information schema. The conversion tool as described above requires a mapping table in which subscriber conversion criteria are defined in order to convert subscriber information existing for each developer into information of standard subscriber information data. The mapping table for generating the standard subscriber information data is information used by the conversion tool for generating the standard subscriber information data. When the subscriber information existing for each developer is converted into the standard subscriber information data, the mapping table for the standard subscriber information data generation has any size at any position for each attribute. Stores additional verification information about whether each attribute should be saved and each attribute to be stored. It has the following structure.

[Conversion]

NumOfAttId =

AttId1_XXXattid =

AttId1_size =

AttId1_YYptr =

AttId2_XXXattid =

AttId2_size =

AttId2_YYptr =

AttId3_XXXattid =

AttId3_size =

AttId3_YYptr =

… … …

… … …

… … …

In the mapping table structure, "[Conversion]" represents header information of the mapping table for generating standard subscriber information data, and "NumOfAttId =" means the total number of attributes existing in the standard subscriber information schema. AttId1_XXXattid = "means an identifier of an attribute defined in the standard subscriber information schema. In addition, "AttId_1size =" indicates the size of the attribute defined in the standard subscriber information schema, and "AttId1_YYptr =" indicates the starting position of the attribute information in each developer-specific subscriber table that matches the attribute defined in the standard subscriber information schema. Indicates. In the mapping table structure, "XXX" and "YY" are name information for identifying a standard subscriber information schema and a subscriber information schema for each individual company, and an attribute for which "YYptr" information does not exist has an empty value without an assigned value. Leave blank to define default values in the standard subscriber information data file.

Next, the conversion tool for generating the subscriber information data file for each developer is a tool necessary for converting from the standard subscriber information data file to the subscriber information data file for each developer based on the information schema for each developer. The tool needs mapping table information in which subscriber information conversion criteria are defined in order to convert the standard subscriber information data file into subscriber information data for each individual company. The mapping table for generating subscriber information data for each developer is information used by the conversion tool for generating subscriber information data for each developer, and when the subscriber information existing in the standard subscriber information data file is converted into subscriber information data for each developer, For each attribute, it stores what size to be stored in which location and additional verification information for each attribute to be stored. The structure of the mapping table is as follows.

[Conversion]

NumOfAttId =?

AttId1_YYattid =?

AttId1_size =?

AttId1_XXXptr =?

AttId1_XXXattid =?

AttId2_YYattid =?

AttId2_size =?

AttId2_XXXptr =?

AttId2_XXXattid =?

AttId3_YYattid =?

AttId3_size =?

AttId3_XXXptr =?

AttId3_XXXattid =?

… … …

… … …

… … …

In the above structure, "AttId1_YYattid =" is an identifier of an attribute defined in each developer's subscriber information schema, and "AttId1_XXXptr =" is in a standard subscriber information data file that matches an attribute defined in each developer's subscriber information schema. Indicates the start position of attribute information. In addition, the attributes for which XXXptr information and XXXattid do not exist are defined for each developer in the standard subscriber information schema. There is no information on the attributes in use. The information should be left blank with no assigned value. The data must store a default value.

The standard subscriber information data file includes standard subscriber information data which is stored in a test mode and can be edited with a Vi editor. The information is generated by the subscriber information existing in each individual company. The information is generated by using a conversion tool for the first time, and the information is used as an input value of the subscriber information data conversion tool for each individual company when the information is converted into subscriber information data for each individual company.

Such a standard subscriber information data file structure is shown in FIG. The standard subscriber information data file structure includes information (10) indicating which developer information is converted into a standard subscriber information data file, and database version information (12) and standard of any developer converted into a standard subscriber information data file. Date and time information 14 for generating the subscriber information data file, number of subscribers converted by station number 16, identifiers 18 for indicating the type of attribute used in the expanded subscriber information data file, and standard subscriber information. The attribute values 20 of data and the end of the standard subscriber information data file comprise information 22 that informs. OXX, which represents the value of the standard subscriber information data attributes, is an NPA (Numbering Plan Area) which is an identifier assigned for each operator.

2 is a flowchart illustrating a method of generating standardized information for a wireless mobile communication service according to the present invention and converting the information into specific service provider information. The XXX.subs files 30 exist for each developer currently in operation. It is a subscriber information data file for each station number extracted in subscriber data. The data file is used with the mapping table for generating standard subscriber information data to enter an input value of the conversion tool 34 for generating a standard subscriber information data file and used to generate the standard subscriber information data file 36. The information of the XXX.subs files is a value generated according to the subscriber information data schema defined for each developer.

The Convert.ini file 32 converts the subscriber schema information defined for each developer as described above to generate the subscriber schema information conversion method and attribute verification required when creating the conversion tool 34 for generating the standard subscriber information data file. This is the file where the information is defined.

The conversion tool 34 for generating a standard subscriber information data file is an conversion file used to convert subscriber information existing for each developer into a standard subscriber information data file.

The standard subscriber information data file 36 is defined in the standard subscriber information data file 36 in addition to the values converted from the XXX.subs files 30 to match the values defined in the standard subscriber information schema. And include the necessary information. The configuration of the information has already been described above.

As described above, the ReConvert.ini file 38 also converts the standard subscriber information data file to generate the subscriber schema information conversion method and the information necessary for attribute verification when creating the conversion tool 40 for generating the subscriber information data file for each developer. Are defined files, and the structure of the file has been described above.

The conversion tool 40 for generating a subscriber information data file for each developer is a conversion tool used to convert the contents of the standard subscriber information data file into the subscriber information data file for each developer, and is generated by translating a function written in C language. Executable file.

The XXX.subs files 42 are files storing subscriber information for each station number generated by the conversion tool 40 for generating a subscriber information data file for each developer. The content of the file is a value obtained by converting the information of the standard subscriber information data file to match the subscriber schema defined for each developer, and stores the information for each developer-station number used in the XXX.subs files 30. Some properties may have different values than files. The reason for this is that an attribute required only for each developer may not be defined in the standard subscriber information data file. The above values are defined as default values and are stored in the XXX.subs file 42.

Accordingly, the information extracted by each developer-station number currently in operation like the XXX.subs files 30 and the information by each developer-station number converted from a standard subscriber information data file such as the XXX.subs files 42 Can be different.

While the invention is susceptible to various modifications and alternative forms, the disclosure thereof has been described with reference to specific embodiments only. It is to be understood, however, that the present invention is not limited to the specific forms referred to in the specification, but rather that the invention is intended to cover all modifications, equivalents, and substitutions within the spirit and scope of the invention as defined by the appended claims. It should be understood to include.

The present invention configured as described above has the effect of pursuing the maximization of business profits by creating high added value, which is the business goal of the wireless mobile communication service provider.

Is a structure of a standard subscriber information data file in accordance with the present invention.

2 is a flowchart illustrating a method of generating standardized information and converting into specific service provider information for a wireless mobile communication service according to the present invention.

<Explanation of symbols for the main parts of the drawings>

10: Information indicating which developer's subscriber information is converted into a standard subscriber information data file.

12: Database version information of a developer converted into a standard subscriber information data file.

14: Date and time information when the standard subscriber information data file is generated.

16: Number of subscribers converted by station number.

18: Identifier indicating the type of attribute used in a standard subscriber information data file.

20: Standard subscriber information data attribute value.

22: Information indicating the end of the standard subscriber information data file.

30: XXX.subs files.

32: Convert.ini file.

34: Conversion tool for generating standard subscriber information data file

36: Standard Subscriber Information Data File

38: ReConvert.ini file

40: Conversion tool for generating subscriber information data file for each developer

42: XXX.subs files.

Claims (20)

In the method of generating standardized information for a wireless mobile communication service, Defining a standard subscriber information schema including all the information existing in common with the information existing for each developer for the subscriber information for the wireless mobile communication service existing for each developer; Defining subscriber schema information conversion reference information necessary for generating a standard subscriber information data file using a mapping table for generating standard subscriber information data; Converting the subscriber information existing for each developer using the standard subscriber information schema into the standard subscriber information data file using a conversion tool for generating a standard subscriber information data file; Defining other subscriber schema information conversion criterion information necessary for converting the standard subscriber information data file into subscriber information existing for each developer using a mapping table for generating subscriber information data for each developer; And converting the standard subscriber information data file into subscriber information existing for each developer by using a change tool for generating a subscriber information data file for each developer. How information is generated. The method of claim 1, wherein the standard subscriber information schema includes information on identifiers of attributes, names of attributes, sizes of attributes, meanings of attributes, ranges of values that attributes can have, and meanings and default values of the attribute values. Standardized subscriber information generation method for a wireless mobile communication service. The method of claim 1, wherein the mapping table for generating standard subscriber information data has to be stored in which location and size for each attribute when converting subscriber information existing for each developer into the standard subscriber information data. A method of generating standardized subscriber information for a wireless mobile communication service, wherein additional verification information for attributes is stored. 4. The method of claim 3, wherein the mapping table structure for generating standard subscriber information data includes mapping table header information for generating standard subscriber information data. 4. The method of claim 3, wherein the mapping table structure for generating standard subscriber information data includes information on the total number of attributes present in the standard subscriber information schema. 4. The method of claim 3, wherein the mapping table structure for generating standard subscriber information data includes identifier information of an attribute defined in the standard subscriber information schema. 4. The method of claim 3, wherein the mapping table structure for generating standard subscriber information data includes size information of an attribute defined in the standard subscriber information schema. [4] The wireless mobile communication service of claim 3, wherein the mapping table structure for generating standard subscriber information data includes start position information of attribute information in each developer-specific subscriber table that matches an attribute defined in the standard subscriber information schema. Standardized subscriber information generation method for the. The standardized subscriber information for wireless mobile communication service according to claim 3, wherein the mapping table structure for generating standard subscriber information data further includes standard subscriber information schema and name information for identifying each developer's subscriber information schema. How to produce. The method of claim 1, wherein the mapping table for generating subscriber information data for each individual company has any size at any position for each attribute when converting subscriber information existing in the standard subscriber information data file into subscriber information data for each developer. And additional verification information for each of the attributes that are to be stored, and standardized subscriber information for the wireless mobile communication service. The method of claim 10, wherein the mapping table structure for generating subscriber information data for each developer comprises mapping table header information for generating subscriber information data for each developer. 12. The method of claim 10, wherein the mapping table structure for generating subscriber information data for each developer includes information on the total number of attributes existing in the subscriber information schema for each developer. . The method of claim 10, wherein the mapping table structure for generating subscriber information data for each developer includes identifier information of an attribute defined in the subscriber information schema for each developer. The method of claim 10, wherein the mapping table structure for generating subscriber information data for each developer includes size information of attributes defined in the subscriber information schema for each developer. . The structure of the mapping table for generating subscriber information data for each developer according to claim 10, wherein the structure of the mapping table for generating subscriber information data for each developer includes starting position information of attribute information in a standard subscriber information data file that matches attributes defined in the subscriber information schema for each developer. And standardized subscriber information generation method for wireless mobile communication service. The method of claim 10, wherein the mapping table structure for generating subscriber information data for each developer includes identifier information of an attribute defined in a standard subscriber information schema. 2. The method of claim 1, wherein the standard subscriber information data file stores standard subscriber information data in text mode. 18. The method of claim 17, wherein the standard subscriber information data information is generated by using a conversion tool for generating standard subscriber information data file for subscriber information existing for each developer. 18. The method of claim 17, wherein the standard subscriber information data information is used as an input value of a conversion tool for generating a subscriber information data file for each developer when converting the subscriber information data for each developer for each developer. Method of generating standardized subscriber information for communication service. 18. The method of claim 17, wherein the standard subscriber information data file includes information indicating which developer's subscriber information has been converted to a standard subscriber information data file, and database developer information of any developer's converted to the standard subscriber information data file. Date and time information when the standard subscriber information data file was created, the number of subscribers converted by station number, an identifier indicating the type of attribute used in the standard subscriber information data file, the attribute value of the standard subscriber information data, and the standard subscriber information data file A method for generating standardized subscriber information for a wireless mobile communication service, comprising information indicating the end of a service.