A method for grid management of bank customers based on geospatial relationships

Abstract

The present invention discloses a method for bank customer grid management based on geospatial relationships, belonging to the technical field of geographic information processing. A method for bank customer grid management based on geospatial relationships includes the following steps: S1. Create a geographic grid by selecting one or more polygons or administrative divisions on a map, and save the created geographic grid in the form of WKT text to a database; S2. Obtain the accurate longitude and latitude coordinate points of customers through on-site visits or address decoding functions, store them in the database and bind them to customer information; S3. Read the WKT text in the database and the longitude and latitude coordinate points of customers, and establish a binding relationship between customers and geographic grids by establishing a point-plane relationship between the longitude and latitude coordinate points of customers and the corresponding areas of geographic grids; S4. Set up one or more customer managers for each geographic grid to establish the association relationship of customer-grid-customer manager, and apply this relationship to various field scenarios.

Description

Technical Field

[0001] The present invention belongs to the technical field of geographic information processing, and more specifically, relates to a method for bank customer grid management based on geographical spatial relationships. Background Art

[0002] With the development of information technology, it has become increasingly important to manage and utilize the standardized address information of customers; for enterprises, government agencies, and developers, business efficiency can be improved and operating costs can be reduced through customer address information. For the financial industry, the efficiency of a series of marketing activities such as on-site visits and task distribution can be enhanced through customer address information; for the logistics industry, the distribution efficiency can be significantly improved through customer address information. In the e-commerce field, input errors by buyers during order placement can be reduced and the order placement time can be shortened through customer address information.

[0003] However, existing address standardization technologies still have problems such as inconsistent administrative division standards, low freedom of user-defined regions, and unclear allocation between users and customers, and cannot meet the needs of specific business scenarios; the low freedom of user-defined regions is due to the fact that existing regional divisions do not support custom division according to user needs; the unclear allocation between users and customers is due to problems such as time-consuming and laborious grid management relationships between customers and customer managers in existing technologies, large deviations in geographical location judgment, and unclear customer attribution relationships. Taking a method and device for insurance grid data processing based on geographical location (202410917011.X) disclosed in Chinese invention patent literature as an example, this invention uses a geographical location distribution model to obtain insurance grid geographical location data. Through grid division, grids with smaller ranges are divided in high-density areas, solving the problem of uneven customer distribution caused by geographical location. However, the administrative division of this solution is only the initialization of a five-segment address and does not take into account autonomous regions and county-level cities established according to the administrative division standards of the Civil Affairs Bureau. At the same time, the freedom of user-defined regions is also low, and it cannot be directly applied to real business scenarios and business systems.

[0004] Therefore, we need a method for bank customer grid management based on geographical spatial relationships to improve the accuracy of geographical grid division, meet the customized needs of customer managers for field customer acquisition, improve work efficiency, and reduce the burden on customer managers. Summary of the Invention

[0005] The purpose of the present invention is to provide a method for bank customer grid management based on geographical spatial relationships, which establishes a binding relationship between customers and geographical grids by creating geographical grids to match the longitude and latitude coordinate points of customers, improves the accuracy of administrative divisions, can customize the division of geographical regions according to the needs of customer managers and directly apply them to real business scenarios, improves work efficiency, and reduces the burden on customer managers.

[0006] To achieve the above object, the present invention provides the following technical solutions:

[0007] A method for managing bank customer grids based on geospatial relationships according to the present invention includes the following steps:

[0008] S1. Create a geographic grid by using a polygon formed by connecting multiple longitude and latitude coordinate points selected on a map or an administrative division where the connections between the points are closed, and save the created geographic grid in the database in the form of a WKT text;

[0009] S2. Obtain the accurate longitude and latitude coordinate points of customers through on-site visits or address decoding functions, store the longitude and latitude coordinate points in the database, and bind them to the customer information in the database;

[0010] S3. Read the WKT text in the database and the longitude and latitude coordinate points of customers, and establish the binding relationship between customers and geographic grids by judging the point-plane relationship between the longitude and latitude coordinate points of customers and the corresponding areas of the geographic grids;

[0011] S4. Set up one or more customer managers for each geographic grid to be responsible for managing and maintaining all customers in the grid.

[0012] The creation of the geographic grid is to correct the geofence and the map base map and merge them to form a geographic area grid; this creation process first involves the drawing of the first-level grid area, the responsibility assignment of the first-level grid, and the preservation of the first-level grid information; subsequently, receive the push of the first-level grid and perform the drawing of the second-level grid area, the responsibility assignment of the second-level grid, and the preservation of the second-level grid information; obtain the accurate geographic coordinates of customers through the methods of customer managers visiting and registering addresses and aggregating customer address parsing, and judge the point-plane positional relationship with the established geographic grid, so as to obtain the association relationship of customer - geographic grid - customer manager.

[0013] As a further improvement of the present invention, the polygon or administrative division described in step S1 can be composed of a single one or multiple ones.

[0014] As a further improvement of the present invention, the method for creating the geographic grid includes the following steps:

[0015] S1-1. Draw the first-level area and select the first-level grid type as an administrative area or a special area;

[0016] S1-2. Backfill and estimate the number of customers according to the area scale;

[0017] S1-3. Select whether the responsibility type is a competitive grid. If it is a competitive grid, it is necessary to set the claim limit and the claim duration, and finally select to push it to the affiliated institution;

[0018] S1-4. Save the created geographical grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the first-level grid type;

[0019] S1-5. Receive the first-level grid push and draw the second-level area, and select the second-level grid type to match the first-level grid type;

[0020] S1-6. Backfill and estimate the number of customers according to the regional scale;

[0021] S1-7. Select whether the responsibility type is a competitive grid. If it is a competitive grid, the claim limit and claim duration need to be set, and finally select to push to the affiliated institution and the affiliated customer manager;

[0022] S1-8. Save the created geographical grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the second-level grid type.

[0023] As a further improvement of the present invention, the step of backfilling and estimating the number of customers described in steps S1-2 and S1-6 is to analyze the population quantity, consumption ability or related indicators of a specific area to estimate the number of potential customers in the area, thereby improving the accuracy of the subsequent claim limit and claim duration, and making the process of allocating to the affiliated institution more reasonable.

[0024] As a further improvement of the present invention, the competitive grid described in steps S1-3 and S1-7 is a competitive relationship of resource allocation or management responsibility between different grids or regions in geographical grid management. It is necessary to set the affiliated institution to determine the claim limit and claim duration rules for management and adjustment to ensure the reasonable allocation of resources and the effective management of the grid.

[0025] As a further improvement of the present invention, the precise longitude and latitude coordinate point acquisition method described in step S2 is to perform geographical positioning through mobile devices such as mobile phones and tablets during the user's on-site visit or convert the customer's detailed address into longitude and latitude coordinate points by using the function of address decoding.

[0026] As a further improvement of the present invention, the steps of the address decoding process include:

[0027] S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address and address parsing result will appear. If the customer has no address data, the current address will be added to the manual review page, and the editable current address and address parsing result will appear;

[0028] S2-2. Add the new address data to the anchor point list and add the old address to the ignored address library;

[0029] S2-3. The anchor point list will start the engine batch process to perform real-time calculation and processing on these address data in batches. After the processing is completed, the relevant list will be updated, and a GIS map will be generated based on the processed data;

[0030] S2-4. The customer manager will verify and correct the new addresses of customers for the GIS map. If the new address is incorrect, the customer manager will be prompted with an error and the address will be added to the ignored database.

[0031] As a further improvement of the present invention, the engine batch process in step S2-3 scans the standardized addresses corresponding to the new address data by responding to the batch calculation subtasks of the new address data in the anchor point list, including province, city, district / county, town / sub-district, village / community, and house number information.

[0032] As a further improvement of the present invention, the customer manager in step S4 can obtain customers in a specified or customized manner through grid allocation; the customized manner can set the tube household attribution, address attribution, and manual allocation priority to adapt to the real business scenario.

[0033] As a further improvement of the present invention, the geographical grid can improve the grid configuration by responding to the maintenance of province / city / district / sub-district (township) / community (village). After the grid configuration is improved through grid addition / modification / deletion, the improved grid will be synchronized to the grid allocation process and further synchronized to improve the customer allocation operation; during customer allocation, customer relationship configuration and maintenance operations are performed. After completion, it is judged whether the improvement process is associated with customer transactions. If not, the maintenance can be completed. If associated, it enters the statistical stage, and public / customized indicators of the customers are displayed to reflect the satisfaction of the customers with the grid improvement.

[0034] Compared with the prior art, the beneficial effects of the present invention are as follows: a method of managing bank customer grids based on geographic spatial relationships of the present invention constructs a geographic area grid, and obtains the customer's precise geographic coordinates by means of customer manager visiting the registration address and customer address parsing, and judges the position relationship between points and surfaces with the established geographic grid, thereby obtaining the association relationship between customer-grid-account manager, and applying the relationship to offline visits, tasks and marketing scenarios; by clarifying the administrative division standards, the accuracy rate from obtaining customer addresses to administrative divisions is improved, and customers can be classified and managed in geographic space more quickly and accurately, thereby improving the efficiency of customer management; by setting up primary grids and secondary grids, as well as the concept of competitive grids, resources and management responsibilities can be allocated more reasonably to ensure the rational use of resources and effective management of grids; by supporting customer managers to freely edit geographic spatial polygons, different types of geographic areas that meet the needs of offline tasks of customer managers are established, and customized needs for field customer development in the same industry are realized; at the same time, the method of the present invention can be adjusted according to different business needs and market changes, and has good flexibility and scalability. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A schematic diagram of a flow chart of a method for customer management based on geographic spatial relationships of the present invention;

[0036] Figure 2 A schematic diagram of the process of creating a geographic grid according to the present invention;

[0037] Figure 3 This is a schematic diagram of the customer address resolution process of the present invention;

[0038] Figure 4 A flow chart is generated for the address resolution-grid allocation-grid relationship of the present invention. DETAILED DESCRIPTION

[0039] Specific embodiment 1: Please refer to Figures 1-4 A method for bank customer grid management based on geographic spatial relationship includes the following steps:

[0040] S1. Create a geographic grid by selecting multiple longitude and latitude coordinate points on the map to form a polygon or administrative division with closed lines between the points, and save the created geographic grid in the database in the form of WKT text.

[0041] Specifically, the creation of the geographic grid in step S1 involves correcting the geofence and the map base map and merging them to form a geographic area grid. This creation process first involves the drawing of the first-level grid area, the responsibility assignment of the first-level grid, and the preservation of the first-level grid information. Subsequently, it receives the push from the first-level grid and proceeds with the drawing of the second-level grid area, the responsibility assignment of the second-level grid, and the preservation of the second-level grid information. By means of the account manager's visit to register the address and the aggregation and analysis of the customer address, the accurate geographic coordinates of the customer are obtained, and the position relationship between the points and the surface of the established geographic grid is judged, thereby obtaining the association relationship among the customer - geographic grid - account manager.

[0042] Specifically, the polygon or administrative division described in step S1 can be composed of a single one or multiple ones.

[0043] Specifically, the following is the example code of the spatial relationship between the longitude and latitude coordinate points and the geographic grid described in step S1:

[0044] public AddressResultVO childrenMatching(Point point)

[0045] The current administrative division is at the fifth or fourth level and there is no lower-level administrative division, and the matching result is returned:

[0046] if (this.level == 5 || (this.level == 4 && Objects.isNull(this.children))) {

[0047] AddressResultVO addressResultVO = new AddressResultVO();

[0048] BeanUtils.copyProperties(this, addressResultVO);

[0049] addressResultVO.setStatus(0);

[0050] addressResultVO.setLng(point.getX());

[0051] addressResultVO.setLat(point.getY());

[0052] return addressResultVO;

[0053] }

[0054] Traverse and search administrative divisions:

[0055] for (GeoInfoDTO geoInfoDTO : this.children){

[0056] Process the lack of administrative division fences:

[0057] if (Objects.isNull(geoInfoDTO.getGrid())) {

[0058] continue;

[0059] }

[0060] Judge the inclusion relationship between the point object and the administrative division fence:

[0061] if (geoInfoDTO.getGrid().contains(point)){

[0062] If the inclusion relationship holds, continue to match the next-level administrative division:

[0063] return geoInfoDTO.childrenMatching(point);

[0064] }

[0065] }

[0066] If the next-level administrative division is not matched, return the current administrative division information:

[0067] AddressResultVO addressResultVO = new AddressResultVO();

[0068] BeanUtils.copyProperties(this, addressResultVO);

[0069] addressResultVO.setStatus(0);

[0070] addressResultVO.setLng(point.getX());

[0071] addressResultVO.setLat(point.getY());

[0072] return addressResultVO;

[0073] }

[0074] }。

[0075] Specifically, the geographical grid in step S1 can be improved by responding to the maintenance of provinces / cities / districts / streets (townships) / communities (villages).

[0076] Specifically, the method for creating a geographical grid includes the following steps:

[0077] S1-1. Draw the first-level area and select the first-level grid type as an administrative area or a special area;

[0078] S1-2. Backfill and estimate the number of customers according to the area scale;

[0079] S1-3. Select whether the responsibility type is a competitive grid. If it is a competitive grid, the claim limit and claim duration need to be set, and finally select to push to the affiliated institution;

[0080] S1-4. Save the created geographical grid in the form of a WKT text to the database and jump to the corresponding grid query homepage according to the first-level grid type;

[0081] S1-5. Receive the first-level grid push and draw the second-level area, and select the second-level grid type to match the first-level grid type;

[0082] S1-6. Backfill and estimate the number of customers according to the area scale;

[0083] S1-7. Select whether the responsibility type is a competitive grid. If it is a competitive grid, the claim limit and claim duration need to be set, and finally select to push to the affiliated institution and the affiliated account manager;

[0084] S1-8. Save the created geographical grid in the form of a WKT text to the database and jump to the corresponding grid query homepage according to the second-level grid type.

[0085] Specifically, the backfilling and estimating the number of customers according to the area scale described in steps S1-2 and S1-6 is to estimate the number of potential customers in the area by analyzing the population quantity, consumption ability or relevant indicators of a specific area, thereby improving the accuracy of the subsequent claim limit and claim duration, and making the process of allocating to the affiliated institution more reasonable.

[0086] Specifically, the competitive grid described in steps S1-3 and S1-7 is a competitive relationship for resource allocation or management responsibility between different grids or regions in geographical grid management. It is necessary to set the affiliated institution to determine the claim limit and claim duration rules for management and adjustment to ensure the reasonable allocation of resources and the effective management of the grid.

[0087] Specifically, the following is a code example for creating a geographical grid:

[0088] public String createTopRegionGrid(TopRegionGridDTO topRegionGridDTO){

[0089] if (regionGridUtilsService.checkGridNameExist(topRegionGridDTO.getGridName(), topRegionGridDTO.getGridLevel())) {

[0090] throw new ServiceException("Grid creation failed, grid name already exists");

[0091] }

[0092] Create a grid object and insert it into the database:

[0093] RegionGrid regionGrid = new RegionGrid();

[0094] BeanUtils.copyProperties(topRegionGridDTO, regionGrid);

[0095] regionGridMapper.insert(regionGrid);

[0096] Long gridId = regionGrid.getGridId();

[0097] Grid creation rule verification:

[0098] if (topRegionGridDTO.getGridDutyType().equals("1")&&topRegionGridDTO.getGridUserRelateDTOList().size() != 1) {

[0099] throw new ServiceException("When the assignment type is a responsibility grid, only a single organization can be selected");

[0100] }

[0101] if (topRegionGridDTO.getGridDutyType().equals("2")&&topRegionGridDTO.getGridUserRelateDTOList().size()<2) {

[0102] throw new ServiceException("Multiple organizations need to be selected when the allocation type is competitive grid");

[0103] }

[0104] Bind the organization and its account managers to the grid and insert them into the database:

[0105] topRegionGridDTO.getGridUserRelateDTOList().forEach(gridRelateDTO ->{

[0106] RegionUserRelate regionUserRelate = new RegionUserRelate();

[0107] BeanUtils.copyProperties(gridRelateDTO, regionUserRelate);

[0108] regionUserRelate.setGridId(gridId);

[0109] regionUserRelateMapper.insert(regionUserRelate);

[0110] });

[0111] Save the administrative division structure tree corresponding to the grid and insert it into the database:

[0112] topRegionGridDTO.getAdminDivisionDTOList().forEach(gridAdminDivisionDTO ->{

[0113] Integer level = codeSizeToLevel.get(gridAdminDivisionDTO.getCode().length());

[0114] if(level == 5){

[0115] Bind the five - level administrative division to the grid and insert it into the database:

[0116] RegionAdminDivisionRelate regionAdminDivisionRelate = new RegionAdminDivisionRelate();

[0117] regionAdminDivisionRelate.setCode(gridAdminDivisionDTO.getCode());

[0118] regionAdminDivisionRelate.setGridId(gridId);

[0119] regionAdminDivisionRelateMapper.insert(regionAdminDivisionRelate);

[0120] }

[0121] String parentCode = gridAdminDivisionDTO.getCode().subSequence(0, levelToParentCode.get(level)).toString();

[0122] RegionAddressTree regionAddressTree = new RegionAddressTree();

[0123] regionAddressTree.setGridId(gridId);

[0124] regionAddressTree.setCode(gridAdminDivisionDTO.getCode());

[0125] regionAddressTree.setLabel(gridAdminDivisionDTO.getLabel());

[0126] regionAddressTree.setLevel(level);

[0127] regionAddressTree.setParentCode(parentCode);

[0128] regionAddressTreeMapper.insert(regionAddressTree);

[0129] [[ID=6}};

[0130] Update the polygon of the geographical region corresponding to the grid and save the WKT text to the database:

[0131] List <string>codeLevel5 = topRegionGridDTO.getAdminDivisionDTOList().stream()

[0132] .map(RegionAdminDivisionDTO::getCode)

[0133] .filter(code ->codeSizeToLevel.get(code.length()) == 5)

[0134] .collect(Collectors.toList());

[0135] if (!gridAreaFenceService.updateGridFence("1", gridId, codeLevel5)) {

[0136] throw new ServiceException("Grid fence saving failed!");

[0137] }

[0138] gridInfoRedisService.cleanGridInfo("1");

[0139] return "First-level grid creation successful!";

[0140] }

[0141] S2. Obtain the accurate longitude and latitude coordinate points of the customer through on-site visits or the address decoding function, store the longitude and latitude coordinate points in the database, and bind them to the customer information in the database.

[0142] Specifically, the method for obtaining the accurate longitude and latitude coordinate points described in step S2 is to perform geolocation through mobile devices such as mobile phones and tablets during the on-site visit of the user or to convert the detailed address of the customer into longitude and latitude coordinate points by using the address decoding function.

[0143] Specifically, the steps of the address decoding process include:

[0144] S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address, and address parsing result will appear. If the customer has no address data, the current address will be added to the manual review page, and the editable current address and address parsing result will appear;

[0145] S2-2. Add the new address data to the anchor list and add the old address to the ignored address library;

[0146] S2-3. The anchor list will start the engine batch process to perform real-time calculation and processing on these address data in batches. After the processing is completed, the relevant lists will be updated, and a GIS map will be generated based on the processed data;

[0147] S2-4. The account manager verifies and corrects the new addresses of customers for the GIS map. If the new address is incorrect, the account manager will be prompted with an error and the address will be added to the ignored database.

[0148] Specifically, the engine batch process described in step S2-3 scans the standardized addresses corresponding to the new address data through the batch calculation subtask of the new address data in the anchor list, including province, city, district / county, town / sub-district, village / community, and house number information.

[0149] Specifically, the following is an example code for obtaining the five-level administrative division corresponding to the longitude and latitude coordinate points:

[0150] public AddressResultVO addressStandardize(String address) {

[0151] Convert the address to the longitude and latitude coordinate system through an external interface:

[0152] BaiduResponseDTO geocoding = baiduApiService.geocoding(address);

[0153] if (geocoding.getStatus()!= 0 || Objects.isNull(geocoding.getResult())) {

[0154] Return an exception message after an external interface error:

[0155] AddressResultVO addressResultVO = new AddressResultVO();

[0156] addressResultVO.setStatus(1);

[0157] addressResultVO.setMsg("Failed to convert Baidu address to longitude and latitude");

[0158] return addressResultVO;

[0159] }

[0160] Convert the longitude and latitude coordinate system to a point object:

[0161] Point point = geometryFactory.createPoint(new Coordinate(geocoding.getResult().getLocation().getLng(), geocoding.getResult().getLocation().getLat()));

[0162] Traverse and search administrative regions:

[0163] for(GeoInfoDTO geoInfoDTO : geoInfoDTOList){

[0164] Judge the inclusion relationship between the point object and the fence of the administrative region:

[0165] if(geoInfoDTO.getGrid().contains(point)){

[0166] If the inclusion relationship holds, continue to match the administrative region at the next level:

[0167] return geoInfoDTO.childrenMatching(point);

[0168] }

[0169] }

[0170] If it is not within Zhejiang Province, return the information:

[0171] AddressResultVO addressResultVO = new AddressResultVO();

[0172] addressResultVO.setStatus(999);

[0173] addressResultVO.setLng(point.getX());

[0174] addressResultVO.setLat(point.getY());

[0175] addressResultVO.setMsg("The address is not within Zhejiang Province");

[0176] return addressResultVO;

[0177] }。

[0178] S3. Read the WKT text and customer longitude and latitude coordinate points in the database, and judge the point - surface relationship through the customer's longitude and latitude coordinate points and the corresponding area of the geographic grid, so as to establish the binding relationship between the customer and the geographic grid.

[0179] S4. Set up one or more customer managers for each geographic grid to be responsible for managing and maintaining all customers in the grid.

[0180] Specifically, the customer manager described in step S4 can obtain customers through grid assignment specified or customized; the customized method can set the account management attribution, address attribution and the assignment priority of manual designation to adapt to the real business scenario.

[0181] Specifically, after improving the grid configuration through grid addition / modification / deletion, synchronize the improved grid to the grid assignment process, and further synchronize and improve the customer assignment operation; perform customer relationship configuration and maintenance operations during customer assignment. After completion, judge whether the improvement process is associated with customer transactions. If not, the maintenance can be completed. If associated, enter the statistical stage, and display public / customized indicators for customers to reflect the satisfaction of customers with grid improvement; it helps the management to make macro - decisions, such as resource allocation and regional market strategy adjustment.

[0182] Specifically, the following is an example code of the grid assignment:

[0183] public String createVirtualGrid(VirtualGridDTO virtualGridDTO) {

[0184] Create rule verification:

[0185] virtualGridDTO.checkValid();

[0186] VirtualGrid virtualGrid = new VirtualGrid();

[0187] BeanUtils.copyProperties(virtualGridDTO, virtualGrid);

[0188] After selecting the custom configuration rule, set the batch running flag and obtain the management relationship according to the rule for batch running:

[0189] if (virtualGridDTO.getGridAssignType().equals("2")) {

[0190] virtualGrid.setGridDutyType("2");

[0191] virtualGrid.setBatchFlag(Boolean.TRUE);

[0192] } else {

[0193] virtualGrid.setBatchFlag(Boolean.FALSE);

[0194] }

[0195] SysDept sysDept = sysDeptMapper.selectDeptById(SecurityUtils.getDeptId());

[0196] virtualGrid.setDeptType(sysDept.getDeptType());

[0197] virtualGridMapper.insert(virtualGrid);

[0198] Long gridId = virtualGrid.getGridId();

[0199] Insert customer:

[0200] virtualGridDTO.getCustDTOList().forEach(virtualGridCustDTO ->{

[0201] VirtualCust virtualCust = new VirtualCust();

[0202] BeanUtils.copyProperties(virtualGridCustDTO, virtualCust);

[0203] Set customer type:

[0204] CustTypeEnum custType = CustTypeEnum.getByName(virtualGridCustDTO.getCustType());

[0205] virtualCust.setCustType(custType);

[0206] Set the customer document type:

[0207] CustIdTypeEnum custIdType = CustIdTypeEnum.getByName(virtualGridCustDTO.getCustIdType());

[0208] virtualCust.setCustIdType(custIdType);

[0209] virtualCust.setGridId(gridId);

[0210] virtualCustMapper.insert(virtualCust);

[0211] };

[0212] Specify the account manager, insert the account manager and insert the customer-account manager relationship:

[0213] if (virtualGridDTO.getGridAssignType().equals("1")) {

[0214] Insert the account manager:

[0215] virtualGridDTO.getGridUserRelateDTOList().forEach(gridUserRelateDTO ->{

[0216] if (gridUserRelateDTO.getRelateType().equals("2")) {

[0217] throw new ServiceException("Failed to create virtual grid. It is not allowed to bind an organization");

[0218] }

[0219] VirtualUser virtualUser = new VirtualUser();

[0220] BeanUtils.copyProperties(gridUserRelateDTO, virtualUser);

[0221] virtualUser.setGridId(gridId);

[0222] virtualUserMapper.insert(virtualUser);

[0223] Insert customer - account manager relationship:

[0224] virtualGridDTO.getCustDTOList().forEach(virtualGridCustDTO -> {

[0225] VirtualCustUser virtualCustUser = new VirtualCustUser();

[0226] BeanUtils.copyProperties(gridUserRelateDTO, virtualCustUser);

[0227] virtualCustUser.setGridId(gridId);

[0228] virtualCustUser.setCustId(virtualGridCustDTO.getCustId());

[0229] virtualCustUserMapper.insert(virtualCustUser);

[0230] });

[0231] });

[0232] } else if (virtualGridDTO.getGridAssignType().equals("2")) {

[0233] Insert grid assignment rules:

[0234] virtualGridDTO.getVirtualGridRuleDTOList().forEach(virtualGridRuleDTO -> {

[0235] VirtualGridRule virtualGridRule = new VirtualGridRule();

[0236] BeanUtils.copyProperties(virtualGridRuleDTO, virtualGridRule);

[0237] Set the rule type:

[0238] virtualGridRule.setRelateType(CustTypeEnum.getByName(virtualGridRuleDTO.getRelateType()));

[0239] virtualGridRule.setGridId(gridId);

[0240] virtualGridRuleMapper.insert(virtualGridRule);

[0241] })

[0242] }

[0243] gridInfoRedisService.cleanGridInfo("3");

[0244] return "Virtual grid created successfully!";

[0245] }

[0246] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.< / string>

Claims

1. A method for managing bank customer grids based on geographic spatial relationships, characterized in that: The following steps are involved: S1. Create a geographic grid by selecting multiple latitude and longitude coordinate points on the map to form a single or multiple polygons or administrative divisions with closed lines between the points, and save the created geographic grid in the form of WKT text in the database; The method for creating a geographic grid comprises the following steps: S1-1. Draw a first-level area and select the first-level grid type as administrative area or characteristic area; S1-2. Backfill based on regional size: Estimate the number of potential customers in a specific area by analyzing the population, spending power or related indicators in the area; S1-3. Select whether the responsibility type is a competitive grid. A competitive grid is a competition relationship between different grids or regions in the management of geographic grids. It is necessary to set the ownership agency to determine the upper limit and duration of the claim to manage and adjust it, so as to ensure the reasonable allocation of resources and the effective management of the grid. If it is a competitive grid, the upper limit and duration of the claim need to be set, and the final choice is pushed to the ownership agency; S1-4. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the primary grid type; S1-5. Receive the primary grid push and draw the secondary area, select the secondary grid type to match the primary grid type; S1-6. Backfill based on regional size: Estimate the number of potential customers in a specific area by analyzing the population, spending power or related indicators in the area; S1-7. Select whether the responsibility type is a competitive grid. A competitive grid is a competition relationship between different grids or regions in the management of geographic grids. It is necessary to set the ownership organization to determine the upper limit and duration of the claim to manage and adjust it, so as to ensure the reasonable allocation of resources and the effective management of the grid. If it is a competitive grid, the upper limit and duration of the claim need to be set, and the final selection will be pushed to the ownership organization and the ownership account manager; S1-8. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the secondary grid type; S2. Obtain the precise longitude and latitude coordinates of the customer through on-site visits or address decoding functions, store the longitude and latitude coordinates in the database, and bind them to the customer information in the database; The steps of address decoding processing include: S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address and address resolution results will appear. If the customer does not have address data, the current address will be added to the manual review page, and the editable current address and address resolution results will appear; S2-2. Add the new address data to the anchor list and the old address to the ignored address library; S2-3. The anchor list will start the engine batch run, and through the batch calculation subtask responding to the new address data in the anchor list, scan the standardized addresses corresponding to the new address data, including province, city, district / county, town / street, village / community and house number information; perform real-time calculation and processing on these address data in batches, update the relevant list after processing, and generate GIS map based on the processed data; S2-4. The account manager verifies and corrects the customer's new address on the GIS map. If the new address is wrong, the account manager is prompted with an error and the address is added to the ignored database; S3. Read the WKT text and the customer's longitude and latitude coordinates in the database, and determine the point-to-surface relationship between the customer's longitude and latitude coordinates and the corresponding area of ​​the geographic grid to establish a binding relationship between the customer and the geographic grid; S4. Each geographic grid has one or more account managers who are responsible for managing and maintaining all customers in the grid; the account manager can obtain customers through grid allocation or customized methods; the customized method is to set the management account ownership, address ownership and manually specified allocation priority to adapt to real business scenarios; The geographic grid creation is to correct the geographic fence and the map base map and merge them into a geographic area grid; this creation process first involves the drawing of the first-level grid area, the allocation of responsibilities for the first-level grid and the preservation of the first-level grid information; then the first-level grid push is received and the second-level grid area is drawn, the second-level grid responsibilities are allocated and the second-level grid information is preserved; the customer's precise geographic coordinates are obtained through the customer manager's visit to the registration address and the customer address resolution aggregation method, and the position relationship between points and surfaces is judged with the established geographic grid, so as to obtain the relationship between customer-geographic grid-account manager.

2. A method for managing bank customer grids based on geographic spatial relationships according to claim 1, characterized in that: The method for obtaining the precise longitude and latitude coordinate points in step S2 is to perform geographic positioning through mobile phones and tablet mobile devices during the user's field visit or to convert the customer's detailed address into longitude and latitude coordinate points by using the address decoding function.

Images