A call control method, device, terminal and computer readable storage medium

Abstract

The present invention provides a call control method, device, terminal and computer-readable storage medium. The method includes a first user initiating a call to a second user, obtaining the dispatch area corresponding to the first user and the current location of the second user, and if the current location of the second user is within the dispatch area, the call is continued. The present invention also provides a call control device, a terminal and a readable storage medium. Through the implementation of the present invention, the objects controlled by the jurisdiction area can be expanded from only the dispatch station to handheld terminals other than the dispatch station; and only when the first user initiates a call to the second user, the dispatch area corresponding to the first user and the current location of the second user are obtained. The timing of the acquisition is more targeted and more accurate, and it is no longer a blind acquisition, which improves resource utilization. At the same time, the location information of the second user obtained is also more accurate, which improves the user experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the field of dedicated mobile communications for railways, and specifically, relate to, but are not limited to, a call control method, device, terminal, and computer-readable storage medium. Background Art

[0002] In railway operation, smart users register to the GSM-R network. In the call process, the access matrix is ​​mainly used to control whether calls between users are allowed. For specific wired terminals such as dispatching desks, it is generally believed that there is a need for a jurisdiction restriction function. Such terminals can only call users within their jurisdiction, and calls outside the area are not allowed to be connected.

[0003] The existing jurisdiction control function is mainly implemented by the cooperation of the dispatching station and the intelligent network. The registration and deregistration results of the function number of the handheld terminal user need to be synchronized to the dispatching station in real time, and the dispatching station interface displays all the function numbers in the current system. The dispatching station records all the location area identifiers contained in its jurisdiction, and regularly sends messages to the intelligent network to query the location information of all railway users with registered function numbers. On the dispatching station interface, the function numbers within the jurisdiction are marked as valid, and those outside the jurisdiction are marked as invalid, thereby realizing location-based call restrictions. In this way, the dispatching station and the intelligent network need to frequently synchronize user data and obtain the location information of all users at regular intervals. The time interval is difficult to define. If the time is too short, the interaction will be too frequent, and if the time is too long, the user's location information will be inaccurate.

[0004] In addition, the existing jurisdiction control is only for the function number registered by the user, but does not include the real MSISDN number. In actual operation, for different smart users, although the same function number is registered, the user attributes are different, and their jurisdictions may also be different. The existing mechanism cannot flexibly distinguish the jurisdictions. Moreover, for handheld terminals other than the dispatch desk, there may also be a demand for location-based call restriction in actual operation, and the existing system does not have such a function. Summary of the invention

[0005] A call control method, device, terminal and computer-readable storage medium provided in the embodiments of the present invention mainly solve the technical problem that in the current related technology, the object of jurisdiction area control is limited to the dispatching station, and the handheld terminal other than the dispatching station cannot be controlled; and the existing jurisdiction area control function is mainly realized by the cooperation of the dispatching station and the intelligent network. It is necessary to frequently synchronize user data between the dispatching station and the intelligent network, and obtain the location information of all users at regular intervals. Since the time interval is difficult to define, there is a problem that if the time is too short, the interaction is too frequent, and if the time is too long, the user's location information is inaccurate, resulting in low user experience and large resource usage.

[0006] In order to solve the above technical problems, an embodiment of the present invention provides a call control method, including:

[0007] There is a first user initiating a call to a second user;

[0008] Obtaining a scheduling area corresponding to the first user;

[0009] Obtaining the current location of the second user;

[0010] If the current location of the second user is within the dispatch area, the call is connected.

[0011] The embodiment of the present invention further provides a call control device, including:

[0012] A first acquisition module, a second acquisition module and a control module;

[0013] The first acquisition module is used to obtain the scheduling area corresponding to the first user when a first user initiates a call to a second user;

[0014] The second acquisition module is used to acquire the current location of the second user;

[0015] The control module is used to connect the call if the current location of the second user is within the dispatch area.

[0016] The embodiment of the present invention further provides a call control terminal, comprising: a processor, a memory and a communication bus;

[0017] The communication bus is used to realize the connection and communication between the processor and the memory;

[0018] The processor is used to execute one or more computer programs stored in the memory to implement the steps of any one of the call control methods described above.

[0019] An embodiment of the present invention further provides a readable storage medium, wherein the readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the call control method as described in any one of the above items.

[0020] The beneficial effects of the present invention are:

[0021] The present invention provides a call control method, device, terminal and computer-readable storage medium. The call control method includes a first user initiating a call to a second user, obtaining the dispatch area corresponding to the first user and the current location of the second user, and continuing the call if the current location of the second user is within the dispatch area. Through the implementation of the present invention, the objects of jurisdictional area control can be expanded from only the dispatch station to handheld terminals other than the dispatch station; and only when the first user initiates a call to the second user, the dispatch area corresponding to the first user and the current location of the second user are obtained. The timing of the acquisition is more targeted and more accurate, and it is no longer blind acquisition, which improves resource utilization. At the same time, the location information of the second user obtained is also more accurate, which improves the user experience.

[0022] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 A flowchart of a call control method provided in Embodiment 1 of the present invention;

[0024] Figure 2 A schematic diagram of scheduling area allocation provided in Embodiment 1 of the present invention;

[0025] Figure 3 A schematic diagram of a specific user registration and call control process provided in the first embodiment of the present invention;

[0026] Figure 4 A flowchart of a specific embodiment of user-level jurisdiction area control provided in Embodiment 1 of the present invention;

[0027] Figure 5 A flowchart of a specific embodiment of a system-level jurisdiction area control provided in the first embodiment of the present invention;

[0028] Figure 6 A structural diagram of a call control device provided in Embodiment 2 of the present invention;

[0029] Figure 7 This is a schematic diagram of the structure of a call control terminal provided in Embodiment 3 of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0031] Embodiment 1:

[0032] See also Figure 1 , a call control method provided in this embodiment includes:

[0033] S101: A first user initiates a call to a second user;

[0034] S102: Obtain a scheduling area corresponding to the first user;

[0035] S103: Acquire the current location of the second user;

[0036] S104: If the current location of the second user is within the dispatch area, the call is connected.

[0037] In some embodiments, the call control method in the embodiments of the present invention targets a call generated after an intelligent user registers with a GSM-R network during railway operations.

[0038] In some embodiments, the first user and the second user in the embodiments of the present invention are both users registered in the GSM-R network.

[0039] In some embodiments, if there is at least one user between the first user and the second user that is not registered in the GSM-R network, the call will be released.

[0040] In some embodiments, if the current location of the second user is not within the dispatch area of ​​the first user, that is, the second user is not under the jurisdiction of the first user, the call is released and the call process ends.

[0041] It should be noted that the first user initiating a call to the second user can be understood as the state where the first user initiates a call to the second user but the second user has not received the call instruction from the first user. It can also be understood that the first user is the calling user and the second user is the called user.

[0042] In some embodiments, the intelligent user initiates a request to register a function number through USSD operation, and the SCP performs authentication to determine whether the function number complies with the numbering plan and whether the user is qualified to register the function number. If the authentication is successful, the user and its corresponding function number data are added. After the function number is successfully registered, the user function number can be directly dialed when making a call without knowing the real MSISDN number of the called party.

[0043] In some embodiments, the first user and the second user may be both dispatch stations or handheld terminals other than dispatch stations, or one of the first user and the second user may be a dispatch station and the other a handheld terminal other than dispatch station, which is not limited here.

[0044] In some embodiments, the allocation rule of the scheduling area may be that there are multiple scheduling areas in the system, each scheduling area includes one or more location area cells. The same location area may belong to multiple different scheduling areas at the same time. For example Figure 2 As shown, the scheduling area A includes two location areas cell_1 and cell_2, and the location area cell_1 can belong to the scheduling area A and the scheduling area B at the same time.

[0045] In some embodiments, the current location of the second user can be obtained by 7. SCP sending a query location request message to HLR, which carries the called party's MSISDN number, and obtaining the current location of the called user in the response message.

[0046] In some embodiments, obtaining the scheduling area corresponding to the first user includes:

[0047] Get the role attributes of the first user;

[0048] If the role attribute is system-level jurisdiction control, the current location of the first user is obtained;

[0049] A dispatch area is determined based on the current location of the first user.

[0050] In some embodiments, a user initiates a call request and dials the function number of the second user. That is, when the first user initiates a call to the second user, the call is sent to the intelligent network platform, and the SCP queries the user data module to perform validity authentication of the calling and called function numbers and function or location addressing. If the authentication and addressing are successful, the role attributes corresponding to the function numbers of the first user and the second user and the MSISDN number of the second user are obtained.

[0051] In some embodiments, when the role attribute of the first user is system-level jurisdiction control, the dispatch area configuration is queried to obtain the current location of the first user. The dispatch area list can be obtained according to the current location of the first user, and it can be obtained which one or several dispatch areas in the dispatch area list the first user is currently in. When querying whether the current location of the second user is in any dispatch area in the above dispatch area list, if it exists, it is considered that the second user belongs to the jurisdiction of the first user, and the call is connected, that is, the call is allowed. At this time, the SCP sends a connection instruction to the MSC, which carries the called MSISDN number, instructing the MSC to page the called user. If it does not exist, it is considered that the second user does not belong to the jurisdiction of the first user, and the call is released, that is, the call is not allowed.

[0052] In some embodiments, when the role attribute corresponding to the function number of the first user is system-level jurisdiction area control, the dispatch area of ​​the first user does not need to be pre-set. As long as the current location of the first user and the current location of the second user belong to the same dispatch area, the first user is considered to have jurisdiction. In other words, when the role attribute of the first user is system-level jurisdiction area control, the dispatch area corresponding to the current location of the first user and the dispatch area corresponding to the current location of the second user can be obtained respectively. If the dispatch areas between the two are the same, the first user is considered to have jurisdiction and can initiate a call to the second user, and the call is connected.

[0053] In some embodiments, when the call is not allowed, a corresponding prompt may be given to the first user, and then a call release instruction may be sent to the MSC. It should be noted that the prompt may be voice, text message or USSD.

[0054] In some embodiments, if the role attribute is user-level jurisdiction control, obtaining a functional number and an MSISDN number of the first user;

[0055] The dispatch area is determined based on the function number and MSISDN number.

[0056] In some embodiments, if no dispatch area can be determined based on the functional number and the MSISDN number;

[0057] The dispatch area is determined according to the function number.

[0058] In some embodiments, before the first user initiates a call to the second user, the method further includes:

[0059] A corresponding function number and a role attribute corresponding to the first user are configured for the first user, where the role attributes include user-level jurisdiction control, system-level jurisdiction control, and no jurisdiction control.

[0060] In some embodiments, role attributes may also include full jurisdiction area control. It can be understood that when the user role attribute of user A is full jurisdiction area control, after the call is initiated, it will be judged as not allowed to be connected and will be released immediately. At this time, the call process will end and user A will not be able to make outgoing calls.

[0061] In some embodiments, if the role attribute of the first user is no jurisdiction area control, the SCP sends a connection instruction to the MSC, which carries the MSISDN number of the second user, instructing the MSC to page the called user. In other words, the first user can call the second user directly, and the process of calling any second user with the role attribute of no jurisdiction area control will be judged as a connection call, and the second user will be able to receive the call request of the first user.

[0062] In some embodiments, when the role attribute of the first user is configured as user-level jurisdiction control, the method further includes:

[0063] configuring a scheduling area for at least one MSISDN number corresponding to the functional number, including the MSISDN number of the first user;

[0064] and / or,

[0065] Configure the dispatch area corresponding to the function number.

[0066] It should be noted that the dispatch area configuration of the user-level jurisdiction area control has at least one of the following two situations: First, when a function number corresponds to one or more MSISDN numbers, a corresponding dispatch area is configured for each MSISDN number corresponding to the function number, and the number of dispatch areas corresponding to each MSISDN number may be the same or different, and the location of the dispatch area corresponding to each MSISDN number may be the same or different. At this time, to obtain the dispatch area of ​​the first user, it is necessary to obtain it based on the function number + MSISDN number of the first user; second, no matter how many MSISDN numbers a function number corresponds to, the corresponding dispatch area is configured only for the function number. At this time, each MSISDN number corresponding to the function number corresponds to the same dispatch area. The above two configuration methods can be selected and used according to the needs of technical personnel in this field.

[0067] The following is a specific example of the process of user A registering to the GSM-R network, and further illustrates the call control method provided by the present invention. It should be noted that the following is only a feasible example, and those skilled in the art can also use other feasible methods to register user A to the GSM-R network, see Figure 3 ,like Figure 3 As shown:

[0068] S301: registration function number;

[0069] It should be noted that the manner in which user A sends the request for registering the function number to the main processing module is not limited in the embodiment of the present invention.

[0070] S302: Registration and authentication;

[0071] In some embodiments, after receiving the registration and authentication request from the main processing module, the basic data processing module will configure its functional energy consumption and role attribute type according to the request.

[0072] It should be noted that the basic data processing module configuration consists of the function numbering plan and all role attribute types in the current GSM-R network.

[0073] S303: Authentication successful;

[0074] After the basic data processing module completes processing the registration authentication request, it will feed back a successful authentication signal to the main processing module. When the basic data processing module successfully authenticates user A, user A now has the role attribute type and function number.

[0075] S304: Add user data;

[0076] The main processing module receives the signal of successful authentication, sends the user data to the user data processing module, and sends a request to add user data to the user data processing module. Among them, the user data processing module saves all intelligent user data in the current GSM-R network, including MSISDN number, registered function number and its corresponding role attribute.

[0077] S305: Successful response;

[0078] When the user data processing module completes adding the user data of user A according to the request for adding user data, it will send a corresponding successful signal to the main processing module.

[0079] S306: Registration successful.

[0080] When the master data processing module receives the successful response signal, it will send a registration success message to the HLR. So far, user A has successfully registered in the GSM-R network. When calling, user A can directly dial the function number of user B without knowing the real MSISDN number of user B.

[0081] The following is a specific example of a call control process when user A calls user B, and further illustrates the call control method provided by the present invention. It should be noted that the following is only an example of a feasible embodiment. Figure 3 ,like Figure 3 As shown:

[0082] S307: Initiate a call;

[0083] User A initiates a call to User B through MSC, and MSC sends the call request to the main processing module.

[0084] S308: Query user data;

[0085] The main processing module sends a request to the user data processing module to query the user data. In some embodiments, the main purpose is to authenticate the validity of the function number of user A and user B.

[0086] S309: Return the result;

[0087] The user data processing module authenticates the validity of the function numbers of user A and user B, the role attribute types of user A and user B, etc. according to the user data query request. If the authentication is successful, the following steps are performed. If the authentication is unsuccessful, the call result of immediate release is directly returned to the MSC.

[0088] S310: Call control (based on the role attributes of user A and user B)

[0089] If the authentication is successful, the main processing module will also send a call control request to the call control module according to the role attributes of user A. The call control module queries the access matrix and the corresponding jurisdiction area control type of users A and B according to the role attributes of users A and B.

[0090] It should be noted that the call control module configures access matrix data, jurisdiction control types of each role attribute, etc. The jurisdiction control types include but are not limited to: user-level regional control based on function number and MSISDN number, user-level regional control based on function number, and system-level regional control.

[0091] After being processed by the call control processing module, call control is performed according to the role attributes of user A and user B obtained in the above steps. If the current call is determined to be allowed to be continued or released immediately, the result of the call being released immediately is directly returned to the MSC. If jurisdiction control is still required, the following steps are continued.

[0092] S311: Return result;

[0093] If the call control processing module considers that the call still needs to be subject to jurisdictional area control after processing, the result will be fed back to the main processing module.

[0094] S312: Query the location of user B (by MSISDN number);

[0095] After the main processing module receives the information that the current call still needs to be controlled by the jurisdiction area, it will send information to the HLR to query the current location information of the second user. In some embodiments, the location of the second user can be obtained according to the MSISDN number of the second user.

[0096] S313: Return the location information of user B;

[0097] After the HLR obtains the location information of user B, it feeds the information back to the main processing module.

[0098] S314: Jurisdiction control;

[0099] At this time, the main processing module sends the location information of user B and the relevant information of user A to the jurisdiction area control module, and the jurisdiction area control module performs jurisdiction area control.

[0100] It should be noted that the jurisdiction control module includes at least a user-level jurisdiction control module and a system-level jurisdiction control module. According to the role attribute type of user A, the jurisdiction control will be executed in the corresponding module.

[0101] S315: Return result;

[0102] After making a judgment according to its control rules, the jurisdiction area control module returns the judgment result to the main processing module.

[0103] S316: Call result.

[0104] The main processing module returns the call result to the MSC according to the above judgment result.

[0105] The above call result may be immediate release or a connected call.

[0106] The specific jurisdiction area control process of the above step S314 is further illustrated below by way of example.

[0107] When the role attribute of user A is user-level jurisdiction control, the user-level jurisdiction control module in the jurisdiction control module executes the jurisdiction control process. For details, see Figure 4 ,like Figure 4 As shown:

[0108] S401: the role attribute of user A is user-level jurisdiction control;

[0109] S402: Query the matching dispatch area based on the function number and MSISDN number of user A;

[0110] S403: Determine whether there is a record, if there is a record, execute S404, if there is no record, execute S406;

[0111] S404: Determine whether the location of user B is within the dispatching area of ​​user A, if yes, execute S405, if no, execute S408;

[0112] S405: connect the call;

[0113] S406: Query the matching dispatch area separately according to the function number of user A;

[0114] S407: Determine whether there is a record, if there is a record, execute S404, if not, execute S408;

[0115] S408: Release the call.

[0116] When it is determined to continue the call or release the call, the call control process ends.

[0117] It can be understood that when the attribute of the function number of the first user is user-level jurisdiction area control, the user-level jurisdiction area control module is entered. Priority is given to the joint query based on the first user function number and the MSISDN number to obtain the matching dispatch area of ​​the first user. If the configuration exists, it is determined whether the current location of the second user falls within the calling dispatch area; if the configuration does not exist, a separate query is made based on the function number of the first user to obtain the matching dispatch area of ​​the first user. If the configuration exists, it is determined whether the current location of the second user falls within the dispatch area of ​​the first user; if the configuration does not exist, it is considered that the dispatch area of ​​the first user is not configured and the call is not allowed. If the location of the second user falls within the dispatch area of ​​the first user, it is considered that the second user belongs to the jurisdiction of the calling user, otherwise it is considered that the called user does not belong to the jurisdiction of the calling user.

[0118] When the role attribute of user A is system-level jurisdiction control, the system-level jurisdiction control module in the jurisdiction control module executes the jurisdiction control process. For the specific process, see Figure 5 ,like Figure 5 As shown:

[0119] S501: User A's role attribute is system-level jurisdiction control;

[0120] S502: Query all dispatching areas to which user A belongs according to his current location;

[0121] S503: Determine whether the location of user B is within the dispatching area of ​​user A, if yes, execute S504, if no, execute S505;

[0122] S504: connect the call;

[0123] S505: Release the call.

[0124] When it is determined to continue the call or release the call, the call control process ends.

[0125] It can be understood that when the attribute of the function of the first user is system-level scheduling area control, the system-level scheduling control module is entered. The scheduling area configuration is queried to check which scheduling areas the current location of the first user is in, and the scheduling area list is obtained, and then the current location of the second user is queried to see whether it falls in any scheduling area in the scheduling area list. If so, it is considered that the second user belongs to the jurisdiction of the first user, otherwise it is considered that the second user does not belong to the jurisdiction of the first user.

[0126] In some embodiments, if the second user is within the jurisdiction of the first user, the call is allowed, and the SCP sends a connection instruction to the MSC, which carries the called party's msisdn number, instructing the MSC to page the called user; if the second user is not within the jurisdiction of the first user, the call is not allowed, and the first user is prompted accordingly, for example: after voice, text message or USSD, a call release is sent to the MSC.

[0127] The call control method provided in the embodiment of the present invention obtains the dispatch area corresponding to the first user and the current location of the second user when the first user initiates a call to the second user. If the current location of the second user is within the dispatch area of ​​the first user, the call is connected. If the current location of the second user is not within the dispatch area, the call is terminated. Through the implementation of the present invention, there is no need for any customized cooperation of the terminal, and the jurisdiction area can be controlled according to the real-time location information of the second user. At the same time, it can be applied to various terminals and is no longer limited to the dispatch desk. In addition, since the current location of the second user is obtained when the first user calls the second user, it is no longer necessary to frequently synchronize user data and obtain the location information of all users to achieve call control, which saves resources, improves control accuracy and control efficiency, and improves user experience.

[0128] Furthermore, the call control method provided by the present invention can be applied to first users of all role attribute types; and different jurisdiction control strategies can be adopted for different first user role attributes, which can be more flexibly applied to railway operations. Improve user experience.

[0129] Embodiment 2:

[0130] This embodiment also provides a call control device, such as Figure 6 As shown, the call control device 600 includes a first acquisition module 601, a second acquisition module 602 and a control module 603, wherein

[0131] The first acquisition module 601 is used to obtain the scheduling area corresponding to the first user when a first user initiates a call to a second user;

[0132] The second acquisition module 602 is used to acquire the current location of the second user;

[0133] The control module 603 is configured to connect the call if the current location of the second user is within the dispatch area.

[0134] In some embodiments, the call control method in the embodiments of the present invention targets a call generated after an intelligent user registers with a GSM-R network during railway operations.

[0135] In some embodiments, the first user and the second user in the embodiments of the present invention are both users registered in the GSM-R network.

[0136] In some embodiments, if there is at least one user between the first user and the second user that is not registered in the GSM-R network, the call will be released.

[0137] It should be noted that the first user initiating a call to the second user can be understood as the state where the first user initiates a call to the second user but the second user has not received the call instruction from the first user. It can also be understood that the first user is the caller and the second user is the called party.

[0138] In some embodiments, the intelligent user initiates a request to register a function number through USSD operation, and the SCP performs authentication to determine whether the function number complies with the numbering plan and whether the user is qualified to register the function number. If the authentication is successful, the user and its corresponding function number data are added. After the function number is successfully registered, the user function number can be directly dialed when making a call without knowing the real MSISDN number of the called party.

[0139] In some embodiments, the first user and the second user may be both dispatch stations or handheld terminals other than dispatch stations, or one of the first user and the second user may be a dispatch station and the other a handheld terminal other than dispatch station, which is not limited here.

[0140] In some embodiments, the allocation rule of the scheduling area may be that there are multiple scheduling areas in the system, each scheduling area includes one or more location area cells. The same location area may belong to multiple different scheduling areas at the same time. For example Figure 2 As shown, the scheduling area A includes two location areas cell_1 and cell_2, and the location area cell_1 can belong to the scheduling area A and the scheduling area B at the same time.

[0141] In some embodiments, the current location of the second user can be obtained by 7. SCP sending a query location request message to HLR, which carries the called party's MSISDN number, and obtaining the current location of the called user in the response message.

[0142] In some embodiments, the first acquisition module is further used for:

[0143] Obtaining the role attributes of the first user;

[0144] If the role attribute is system-level jurisdiction control, obtaining the current location of the first user;

[0145] The scheduling area is determined according to the current location of the first user.

[0146] In some embodiments, a user initiates a call request and dials the function number of the second user. That is, when the first user initiates a call to the second user, the call is sent to the intelligent network platform, and the SCP queries the user data module to perform validity authentication of the calling and called function numbers and function or location addressing. If the authentication and addressing are successful, the role attributes corresponding to the function numbers of the first user and the second user and the MSISDN number of the second user are obtained.

[0147] In some embodiments, when the role attribute of the first user is system-level jurisdiction control, the dispatch area configuration is queried to obtain the current location of the first user. The dispatch area list can be obtained according to the current location of the first user, and it can be obtained which one or several dispatch areas in the dispatch area list the first user is currently in. When querying whether the current location of the second user is in any dispatch area in the above dispatch area list, if it exists, it is considered that the second user belongs to the jurisdiction of the first user, and the call is connected, that is, the call is allowed. At this time, the SCP sends a connection instruction to the MSC, which carries the called MSISDN number, instructing the MSC to page the called user. If it does not exist, it is considered that the second user does not belong to the jurisdiction of the first user, and the call is released, that is, the call is not allowed.

[0148] In some embodiments, when the role attribute corresponding to the function number of the first user is system-level jurisdiction area control, the dispatch area of ​​the first user does not need to be pre-set. As long as the current location of the first user and the current location of the second user belong to the same dispatch area, the first user is considered to have jurisdiction. In other words, when the role attribute of the first user is system-level jurisdiction area control, the dispatch area corresponding to the current location of the first user and the dispatch area corresponding to the current location of the second user can be obtained respectively. If the dispatch areas between the two are the same, the first user is considered to have jurisdiction and can initiate a call to the second user, and the call is connected.

[0149] In some embodiments, when the call is not allowed, a corresponding prompt may be given to the first user, and then a call release instruction may be sent to the MSC. It should be noted that the prompt may be voice, text message or USSD.

[0150] In some embodiments, the first acquisition module is further used to:

[0151] If the role attribute is user-level jurisdiction control, obtaining the function number and MSISDN number of the first user;

[0152] The dispatch area is determined according to the functional number and the MSISDN number.

[0153] In some embodiments, the first acquisition module is further used to:

[0154] If the dispatch area cannot be determined based on the function number and MSISDN number;

[0155] The dispatch area is determined according to the function number.

[0156] In some embodiments, the call control device further includes:

[0157] The basic data module is used to configure the corresponding function number and the role attributes corresponding to the first user for the first user before the first acquisition module obtains that the first user initiates a call to the second user. The role attributes include but are not limited to user-level jurisdiction control, system-level jurisdiction control and no jurisdiction control.

[0158] In some embodiments, role attributes may also include full jurisdiction area control. It can be understood that when the user role attribute of user A is full jurisdiction area control, after the call is initiated, it will be judged as not allowed to be connected and will be released immediately. At this time, the call process will end and user A will not be able to make outgoing calls.

[0159] In some embodiments, if the role attribute of the first user is no jurisdiction area control, the SCP sends a connection instruction to the MSC, which carries the MSISDN number of the second user, instructing the MSC to page the called user. In other words, the first user can call the second user directly, and the process of calling any second user with the role attribute of no jurisdiction area control will be judged as a connection call, and the second user will be able to receive the call request of the first user.

[0160] It should be noted that those skilled in the art can also perform special configurations of role attributes as required.

[0161] In some embodiments, the call control device further includes:

[0162] A user-level jurisdiction configuration module, configured to configure a scheduling area for at least one MSISDN number corresponding to the function number, including the MSISDN number of the first user, when the basic data module configures the role attribute of the first user as user-level jurisdiction control;

[0163] and / or,

[0164] The user-level jurisdiction area configuration module is used to configure the dispatch area corresponding to the function number when the basic data module configures the role attribute of the first user as user-level jurisdiction area control.

[0165] It should be noted that the dispatch area configuration of the user-level jurisdiction area control has at least one of the following two situations: First, when a function number corresponds to one or more MSISDN numbers, a corresponding dispatch area is configured for each MSISDN number corresponding to the function number, and the number of dispatch areas corresponding to each MSISDN number may be the same or different, and the location of the dispatch area corresponding to each MSISDN number may be the same or different. At this time, to obtain the dispatch area of ​​the first user, it is necessary to obtain it based on the function number + MSISDN number of the first user; second, no matter how many MSISDN numbers a function number corresponds to, the corresponding dispatch area is configured only for the function number. At this time, each MSISDN number corresponding to the function number corresponds to the same dispatch area. The above two configuration methods can be selected and used according to the needs of technical personnel in this field.

[0166] The call control device provided by the embodiment of the present invention obtains the dispatch area corresponding to the first user by the first acquisition module and the current location of the second user by the second acquisition module when the first user initiates a call to the second user. If the current location of the second user is within the dispatch area of ​​the first user, the control module controls the call connection. If the current location of the second user is not within the dispatch area of ​​the first user, the call is terminated. Through the implementation of the present invention, there is no need for any customized cooperation of the terminal, and the jurisdiction area can be controlled according to the real-time location information of the second user. At the same time, it can be applied to various terminals and is no longer limited to the dispatch desk. In addition, since the current location of the second user is obtained only when the first user calls the second user, it is no longer necessary to frequently synchronize user data and obtain the location information of all users to achieve call control, which saves resources, improves control accuracy and control efficiency, and improves user experience.

[0167] Furthermore, the call control method provided by the present invention can be applied to first users of all role attribute types; and different jurisdiction control strategies can be adopted for different first user role attributes, which can be more flexibly applied to railway operations. Improve user experience.

[0168] Embodiment three:

[0169] This embodiment also provides a call control terminal. Figure 7 As shown, it includes a processor 701, a memory 703 and a communication bus 702, wherein:

[0170] The communication bus 702 is used to realize the connection and communication between the processor 701 and the memory 703;

[0171] The processor 701 is configured to execute one or more computer programs stored in the memory 703 to implement at least one step of the call control method in the above embodiments.

[0172] The present embodiment also provides a computer-readable storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer.

[0173] The computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the one or more computer programs stored therein can be executed by a processor to implement at least one step of the call control method in the above embodiments.

[0174] This embodiment also provides a computer program (or computer software), which can be distributed on a computer-readable medium and executed by a computing device to implement at least one step of the display data processing method and / or display method in the above embodiments; and in some cases, at least one step shown or described can be executed in an order different from that described in the above embodiments.

[0175] It should be understood that, in some cases, at least one step shown or described may be performed in an order different from that described in the above embodiments.

[0176] This embodiment further provides a computer program product, including a computer readable device, on which the computer program as shown above is stored. In this embodiment, the computer readable device may include the computer readable storage medium as shown above.

[0177] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.

[0178] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.

[0179] The above contents are further detailed descriptions of the embodiments of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A call control method, characterized in that: The call control method comprises: Configuring a corresponding function number for a first user and a role attribute corresponding to the first user, wherein the role attribute includes user-level jurisdiction control, system-level jurisdiction control, and no jurisdiction control; There is a call initiated by the first user to the second user; Obtaining a role attribute corresponding to the first user, and if the role attribute is a system-level jurisdiction area control, obtaining a current location of the first user; determining a dispatch area according to the current location of the first user; If the role attribute is user-level jurisdiction control, obtaining the function number and MSISDN number of the first user; determining the dispatch area according to the function number and the MSISDN number; Obtaining the current location of the second user; If the current location of the second user is within the dispatch area, the call is connected.

2. The call control method according to claim 1, characterized in that: If the dispatch area cannot be determined according to the function number and the MSISDN number; The scheduling area is determined according to the function number.

3. The call control method according to claim 1, characterized in that: When the role attribute of the first user is configured as the user-level jurisdiction control, the method further includes: configuring a scheduling area for at least one MSISDN number corresponding to the functional number, including the MSISDN number of the first user; and / or, Configure the dispatch area corresponding to the function number.

4. A call control device, characterized in that: The call control device comprises: a first acquisition module, a second acquisition module and a control module, wherein: a basic data module, configured to configure a corresponding function number and a role attribute corresponding to the first user for the first user before the first acquisition module acquires that the first user initiates a call to the second user, wherein the role attribute includes user-level jurisdiction control, system-level jurisdiction control, and no jurisdiction control; The first acquisition module is used to obtain the role attribute corresponding to the first user when the first user initiates a call to the second user, and if the role attribute is system-level jurisdiction control, obtain the current location of the first user; determine the dispatch area according to the current location of the first user; if the role attribute is user-level jurisdiction control, obtain the function number and MSISDN number of the first user; determine the dispatch area according to the function number and the MSISDN number; The second acquisition module is used to acquire the current location of the second user; The control module is used to connect the call if the current location of the second user is within the dispatch area. Call.

5. The call control device according to claim 4, characterized in that: The first acquisition module is also used for: If the dispatch area cannot be determined according to the function number and the MSISDN number; The scheduling area is determined according to the function number.

6. The call control device according to claim 4, characterized in that: The call control device also includes: A user-level jurisdiction configuration module, configured to configure a scheduling area for at least one MSISDN number corresponding to the function number including the MSISDN number of the first user when the basic data module configures the role attribute of the first user as the user-level jurisdiction control; and / or, The user-level jurisdiction configuration module is used to configure the dispatch area corresponding to the function number when the basic data module configures the role attribute of the first user as the user-level jurisdiction control.

7. A call control terminal, characterized in that: The call control terminal includes: a processor, a memory and a communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more computer programs stored in the memory to implement the steps of the call control method according to any one of claims 1 to 3.

8. A readable storage medium, characterized in that: The readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the call control method according to any one of claims 1 to 3.

Images