Channel city and transport capacity division difference compatible method

Abstract

The invention discloses a compatible method for different channel city and transport capacity division, which comprises the following steps: S1, placing an order by a channel passenger, and transmitting a channel number, a cityId get-on city id, a slng get-on longitude, a slat latitude, an elng terminal longitude and an elat latitude; s2, a transport capacity open platform order placing interface; s3, fence cache information is inquired, fence cache is inquired from redis, if cache information is not inquired, configuration information is inquired, and then the configuration information is stored in the redis caches, from the perspective of achieving transport capacity benefit maximization, a part of channels and a part of areas are divided into different places of cities, fences are delimited for the channels and the areas, and the utilization rate of the channels and the areas is improved. Caching the channel, the get-on city, the fence id and the id of the city to be converted; during channel pre-estimation or order placing, whether the coordinates are in the calibrated fence is judged according to the introduced city id, if the coordinates are in the fence, the coordinates are converted into the configured city id, and if the coordinates are not in the fence, the city id introduced by the channel is used; the problems of pre-estimation and ordering of the channel and transport capacity difference area are solved.

Description

Technical Field

[0001] The present invention belongs to the technical field of online car-hailing platforms, and specifically relates to a compatibility method with different channel cities and transport capacity divisions. Background Art

[0002] In actual online car-hailing, the city transmitted during channel estimation or order placement is based on the city boundaries defined by the channel. If the price plan is completely queried according to the city ID transmitted by the channel when calling capacity estimation or placing an order, the price plan of Langfang and Beijing may be different, which may result in a reduction in the revenue of the capacity. Since the city IDs opened by the channel and the capacity agreement must be consistent, if the capacity restriction boarding area is not within the designated city range, it may cause greater losses.

[0003] To this end, the present invention designs a compatible method with different channel city and transport capacity divisions. Summary of the invention

[0004] The purpose of the present invention is to provide a compatible method with different channel cities and transport capacity divisions to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solution: a compatible method for different channel cities and transport capacity divisions, the specific steps include: S1: a channel passenger places an order, and transmits the channel number, cityId boarding city id, slng boarding longitude and slat latitude, elng terminal longitude and elat latitude;

[0006] S2: ordering interface of the open transportation platform;

[0007] S3: Query the fence cache information. Query the fence cache from redis. If no cache information is found, query the configuration information and then store it in the redis cache. The configuration information includes:

[0008] channel channel number, cityId boarding city id, fenceId fence id where the boarding coordinates are located, toCityId city id where the fence is located and the city id to be converted;

[0009] S4: Group the fence configuration information according to the channel number and record it as: channelCityFenceGroup;

[0010] S5: If the channel number exists in the channelCityFenceGroup, obtain its configuration list;

[0011] S6: Determine whether the boarding city id cityId exists in the configuration list of the channel number. If the boarding city id cityId exists in the configuration list of the group, call the LBS fence interface to query the fence id where the boarding coordinates of fenceId are located;

[0012] S7: If the fence ID where the queried boarding coordinates of fenceId are located is in the configuration list, convert the boarding city of cityId to the city ID where the toCityId fence is located and the city ID to be converted;

[0013] S8: Determine whether the boarding city of cityId and the boarding longitude and latitude of slng are within the designated city range. If yes, perform the following steps. Otherwise, report an error to the channel and end the process.

[0014] S9: query the price plan of the billing system according to the converted city ID, so as to obtain the correct estimated price;

[0015] S10: End.

[0016] Preferably, in step S3, the configuration information is queried and the expiration time stored in the redis cache is 5 minutes.

[0017] Preferably, the same ordering interface also needs to convert the city ID of the above steps S1-S7, so that the price plan after the estimate and the order is based on the same city.

[0018] Preferably, in step S3, if there is cache information, step S4 is directly executed.

[0019] Compared with the prior art, the beneficial effects of the present invention are as follows: from the perspective of maximizing the benefits of transportation capacity, the present invention divides some channels and some areas into different parts of the city, demarcates fences for them, and caches the channels, boarding cities, fence IDs and city IDs to be converted; when estimating or placing an order for a channel, it is determined whether the coordinates are within the marked fence based on the incoming city ID. If they are within the fence, they are converted into the configured city ID. If they are not within the fence, the city ID passed in by the channel is used; the estimation and ordering problems of channels and areas with different transportation capacity are solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic diagram of the process of the present invention. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] See also Figure 1 The present invention provides a technical solution: a compatible method for different divisions of channel cities and transport capacity. From the perspective of maximizing transport capacity benefits, the present invention divides some channels and some areas into different places in the city. Generally, different places occur in some airports, so fences are drawn for them, such as the "Daxing Airport" fence, and the channel, boarding city, fence ID and city ID to be converted are cached. When estimating or placing an order for a channel, the coordinates are judged based on the incoming city ID to see if they are within the marked fence. If they are within the fence, they are converted into the configured city ID. If they are not within the fence, the city ID passed in by the channel is used.

[0023] Specific steps:

[0024] S1: The channel passenger places an order and transmits the channel number, cityId boarding city id, slng boarding longitude and slat latitude, elng destination longitude and elat latitude;

[0025] S2: ordering interface of the open transportation platform;

[0026] S3: Query the fence cache information. Query the fence cache from redis. If no cache information is found, query the configuration information and then store it in the redis cache. The configuration structure is as follows:

[0027] <dict key="channel_city_fence_list"> [{"channel":"test","cityId":"137","fenceId":138,"toCityId":44},{"channel":"test","cityId":"137","fenceId":190,"toCityId":44}]

[0028] Note: channel is the channel number, cityId is the boarding city id transmitted by the channel, fenceId is the fence id where the boarding coordinates are located, toCityId is the city id where the fence is located and the city id to be converted;

[0029] S4: Group the fence configuration information according to the channel number and record it as: channelCityFenceGroup;

[0030] Shape:

[0031] {"test":[{"channel":"test","cityId":"137","fenceId":138,

[0032] "toCityId":44}, {"channel":"test", "cityId":"137", "fenceId":190,

[0033] "toCityId":44}]};

[0034] S5: If the channel number exists in the channelCityFenceGroup, obtain its configuration list;

[0035] S6: Determine whether the boarding city id cityId exists in the configuration list of the channel number. If the boarding city id cityId exists in the configuration list of the group, call the LBS fence interface to query the fence id where the boarding coordinates of fenceId are located;

[0036] S7: If the fence ID where the queried boarding coordinates of fenceId are located is in the configuration list, convert the boarding city of cityId to the city ID where the toCityId fence is located and the city ID to be converted;

[0037] S8: Determine whether the boarding city of cityId and the boarding longitude and latitude of slng are within the designated city range. If yes, perform the following steps. Otherwise, report an error to the channel and end the process.

[0038] S9: query the price plan of the billing system according to the converted city ID, so as to obtain the correct estimated price;

[0039] S10: The same order placement interface also needs to convert the city ID of the above steps S1-S7, so that the price plan after the estimate and the order is based on the same city;

[0040] S11: End.

[0041] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A compatible method for different channel cities and transport capacity divisions, characterized by: The specific steps include: S1: The channel passenger places an order, and transmits the channel number, cityId boarding city id, slng boarding longitude and slat latitude, elng destination longitude and elat latitude; S2: ordering interface of the open transportation platform; S3: Query the fence cache information. Query the fence cache from redis. If no cache information is found, query the configuration information and then store it in the redis cache. The configuration information includes: channel channel number, cityId boarding city id, fenceId fence id where the boarding coordinates are located, toCityId city id where the fence is located and the city id to be converted; S4: Group the fence configuration information according to the channel number and record it as: channelCityFenceGroup; S5: If the channel number exists in the channelCityFenceGroup, obtain its configuration list; S6: Determine whether the boarding city id cityId exists in the configuration list of the channel number. If the boarding city id cityId exists in the configuration list of the group, call the LBS fence interface to query the fence id where the boarding coordinates of fenceId are located; S7: If the fence ID where the queried fenceId boarding coordinates are located is in the configuration list, convert the cityId boarding city to the toCityId fence's city ID and the city ID to be converted; S8: Determine whether the boarding city of cityId and the boarding longitude and latitude of slng are within the designated city range. If yes, perform the following steps. Otherwise, report an error to the channel and end the process. S9: query the price plan of the billing system according to the converted city ID, so as to obtain the correct estimated price; S10: End.

2. A method for compatibility of channel cities and transport capacity with different divisions according to claim 1, characterized in that: In step S3, the configuration information is queried and the expiration time stored in the redis cache is 5 minutes.

3. The method for compatibility of channel cities and transport capacity with different divisions according to claim 1, characterized in that: Similarly, the order placement interface also needs to convert the city ID in the above steps S1-S7, so that the price plan after the estimate and the order are based on the same city.

4. The method for compatibility of channel cities and transport capacity with different divisions according to claim 1, characterized in that: In step S3, if there is cache information, step S4 is directly executed.

Images