Base station switching method and apparatus, computer-readable storage medium, and electronic device

Abstract

This application provides a base station handover method, apparatus, medium, and electronic device, relating to the field of communication technology. The method includes: receiving a registration request sent by a user terminal, and identifying the user terminal's identity type based on the registration request to obtain an identification result; if the identification result indicates that the user terminal corresponds to a specific identity field, then determining a handover base station timetable corresponding to the user terminal; and sending information about a pre-handover base station to the user terminal based on the handover base station timetable; wherein the user terminal uses the information about the pre-handover base station to switch its currently connected base station to the pre-handover base station. It is evident that implementing the above method allows for setting a handover base station timetable for fixed-track user terminals corresponding to specific identity fields. This enables the one-time transmission of pre-handover base station information when the user terminal is detected as a fixed-track user terminal, eliminating the need for frequent signal measurements and saving network resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a base station handover method, a base station handover device, a computer-readable storage medium, and an electronic device. Background Technology

[0002] Existing base station handover mechanisms are triggered by signal measurement events. When a user terminal's signal strength is measured to be weak at one base station and strong at another, the user terminal is switched from one base station to the other to avoid data transmission errors caused by weak signals. However, existing base station handover mechanisms require frequent signal measurements, which can consume significant network resources.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this application is to provide a base station handover method, base station handover device, computer-readable storage medium, and electronic device, which can set a base station handover timetable for fixed-track user terminals corresponding to specific identity fields. When a user terminal is detected to be a fixed-track user terminal, the pre-handover base station information can be sent out in one go using the base station handover timetable without frequent signal measurement, thereby saving network resources.

[0005] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0006] According to one aspect of this application, a base station handover method is provided, comprising:

[0007] Receive the registration request sent by the user terminal, and identify the user terminal's identity type based on the registration request to obtain the identification result;

[0008] If the identification result is used to indicate that the user terminal corresponds to a specific identity field, then the handover base station timetable corresponding to the user terminal is determined.

[0009] Information about the pre-switched base station is sent to the user terminal based on the base station handover timetable; the user terminal is used to switch the currently connected base station to the pre-switched base station based on the information about the pre-switched base station.

[0010] In one exemplary embodiment of this application, sending information about the pre-handover base station to the user terminal based on the handover base station timetable includes:

[0011] The pre-handover base station is determined based on the fixed trajectory corresponding to the user terminal;

[0012] Information about the base station to be switched is sent to the user terminal based on the base station switching timetable.

[0013] In one exemplary embodiment of this application, sending information about the pre-handover base station to the user terminal based on the handover base station timetable includes:

[0014] The system sends a handover base station timetable to the mobility management network element. The mobility management network element determines the information sending time based on the handover base station timetable and starts a timer to send the pre-handover base station information to the user terminal when the timer indicates that the sending time has arrived.

[0015] In one exemplary embodiment of this application, the method further includes:

[0016] When a change in the fixed trajectory corresponding to a user terminal is detected, the handover timetable for the user terminal is updated.

[0017] In one exemplary embodiment of this application, the user terminal is identified based on the registration request to obtain the identification result, including:

[0018] Retrieve the user identifier from the registration request;

[0019] If a specific identity field associated with a user identifier is detected, an identification result is generated to indicate that the user terminal corresponds to the specific identity field;

[0020] If no specific identity field associated with the user identifier is detected, an identification result is generated to indicate that the user terminal is a regular user.

[0021] In one exemplary embodiment of this application, the method further includes:

[0022] When a deletion request for a user identifier field is detected, the specific identity field corresponding to the user identifier is deleted.

[0023] In one exemplary embodiment of this application, before obtaining the user identifier in the registration request, the above method further includes:

[0024] When a new request for a user identifier field is detected, an association is established between the user identifier and the specific identity field.

[0025] According to one aspect of this application, a base station handover device is provided, the device comprising: a user identification module, a handover base station timetable determination module, and an information transmission module, wherein:

[0026] The user identification module is used to receive registration requests sent by user terminals, identify the identity type of user terminals based on the registration requests, and obtain the identification results.

[0027] The base station handover timetable determination module is used to determine the base station handover timetable corresponding to the user terminal when the identification result indicates that the user terminal corresponds to a specific identity field.

[0028] The information delivery module is used to send information about the pre-switched base station to the user terminal based on the base station handover timetable; the user terminal is used to switch the currently connected base station to the pre-switched base station based on the information about the pre-switched base station.

[0029] In one exemplary embodiment of this application, the information delivery module sends information about the pre-handover base station to the user terminal based on the handover base station timetable, including:

[0030] The pre-handover base station is determined based on the fixed trajectory corresponding to the user terminal;

[0031] Information about the base station to be switched is sent to the user terminal based on the base station switching timetable.

[0032] In one exemplary embodiment of this application, the information delivery module sends information about the pre-handover base station to the user terminal based on the handover base station timetable, including:

[0033] The system sends a handover base station timetable to the mobility management network element. The mobility management network element determines the information sending time based on the handover base station timetable and starts a timer to send the pre-handover base station information to the user terminal when the timer indicates that the sending time has arrived.

[0034] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0035] The base station handover timetable update module is used to update the base station handover timetable corresponding to the user terminal when a change in the fixed trajectory corresponding to the user terminal is detected.

[0036] In one exemplary embodiment of this application, the user identification module performs identity type identification on the user terminal based on the registration request, and obtains the identification result, including:

[0037] Retrieve the user identifier from the registration request;

[0038] If a specific identity field associated with a user identifier is detected, an identification result is generated to indicate that the user terminal corresponds to the specific identity field;

[0039] If no specific identity field associated with the user identifier is detected, an identification result is generated to indicate that the user terminal is a regular user.

[0040] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0041] The field processing unit is used to delete the specific identity field corresponding to the user identifier when a field deletion request for the user identifier is detected.

[0042] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0043] The field processing unit is also used to establish an association between the user identifier and a specific identity field when a new field request for the user identifier is detected before the user identification module obtains the user identifier in the registration request.

[0044] According to one aspect of this application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any of the above methods by executing the executable instructions.

[0045] According to one aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the method of any one of the above.

[0046] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations described above.

[0047] The exemplary embodiments of this application may have some or all of the following beneficial effects:

[0048] In an example embodiment of this application, a base station handover method can receive a registration request sent by a user terminal, and perform identity type identification on the user terminal according to the registration request to obtain an identification result. If the identification result indicates that the user terminal corresponds to a specific identity field, a handover base station timetable corresponding to the user terminal is determined. Information about the pre-handover base station is sent to the user terminal based on the handover base station timetable. The user terminal uses this information to switch the currently connected base station to the pre-handover base station. According to the above description, this application, on one hand, can set a handover base station timetable for fixed-track user terminals corresponding to specific identity fields, so that when a user terminal is detected as a fixed-track user terminal, the pre-handover base station information can be sent out in one go using the handover base station timetable, without frequent signal measurement, thus saving network resources. On the other hand, this application can also effectively utilize the information gain of fixed tracks to replace the existing signal strength-based handover, optimizing the measurement overhead, ping-pong effect, and unexpected call drops caused by the existing signal measurement handover mechanism, thereby improving the handover effect.

[0049] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0050] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0051] Figure 1 A schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application is shown;

[0052] Figure 2 A flowchart illustrating a base station handover method according to an embodiment of this application is shown schematically;

[0053] Figure 3 This illustration schematically depicts an application scenario according to an embodiment of the present application;

[0054] Figure 4 This illustration schematically depicts a multi-party interaction diagram according to an embodiment of the present application;

[0055] Figure 5 This illustration schematically depicts a multi-party interaction diagram according to an embodiment of the present application;

[0056] Figure 6 The diagram schematically illustrates a sequence of multi-party interactions according to one embodiment of this application;

[0057] Figure 7 A schematic block diagram of a base station handover device according to one embodiment of the present application is shown. Detailed Implementation

[0058] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of the embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this application.

[0059] Furthermore, the accompanying drawings are merely illustrative of this application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0060] Please see Figure 1 , Figure 1 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 1 The computer system 100 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0061] like Figure 1 As shown, the computer system 100 includes a central processing unit (CPU) 101, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 102 or programs loaded from storage section 108 into random access memory (RAM) 103. The RAM 103 also stores various programs and data required for system operation. The CPU 101, ROM 101, and RAM 103 are interconnected via a bus 104. An input / output (I / O) interface 105 is also connected to the bus 104.

[0062] The following components are connected to I / O interface 105: an input section 106 including a keyboard, mouse, etc.; an output section 107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 108 including a hard disk, etc.; and a communication section 109 including a network interface card such as a LAN card, modem, etc. The communication section 109 performs communication processing via a network such as the Internet. Drive 110 is also connected to I / O interface 105 as needed. Removable media 111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 110 as needed so that computer programs read from them can be installed into storage section 108 as needed.

[0063] In particular, according to embodiments of this application, the processes described below with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 109, and / or installed from removable medium 111. When the computer program is executed by central processing unit (CPU) 101, it performs the various functions defined in the methods and apparatus of this application.

[0064] Please see Figure 2 , Figure 2 A flowchart illustrating a base station handover method according to an embodiment of this application is shown schematically. Figure 2 As shown, the base station handover method may include the following steps S210 to S230.

[0065] Step S210: Receive the registration request sent by the user terminal, and identify the identity type of the user terminal according to the registration request to obtain the identification result.

[0066] Step S220: If the identification result is used to indicate that the user terminal corresponds to a specific identity field, then determine the handover base station timetable corresponding to the user terminal.

[0067] Step S230: Send information about the pre-switching base station to the user terminal based on the base station handover timetable; wherein, the user terminal is used to switch the currently connected base station to the pre-switching base station based on the information about the pre-switching base station.

[0068] It is evident that implementation Figure 2The method shown allows for the setting of a base station handover schedule for fixed-track user terminals corresponding to specific identity fields. When a user terminal is detected as a fixed-track user terminal, the pre-handover base station information is transmitted in a single step, eliminating the need for frequent signal measurements and saving network resources. Furthermore, it effectively utilizes the information gain of fixed tracks to replace existing signal strength-based handover methods, optimizing existing signal measurement handover mechanisms to address issues such as measurement overhead, ping-pong effect, and unexpected call drops.

[0069] The steps described above in this example implementation will now be explained in more detail.

[0070] In step S210, a registration request sent by a user terminal is received, and the user terminal's identity type is identified based on the registration request to obtain the identification result.

[0071] Specifically, the step of receiving the registration request sent by the user terminal can be performed by the 5G core network; the identification result can be used to indicate whether the user terminal is associated with a specific identity field, and the specific identity field can be used to indicate that the user terminal is a user terminal with a fixed trajectory. The 5G core network can include: Mobility Management Element (AMF), Session Management Element (SMF), Policy Control Element (SMF), Network Open Element (NEF), Network Repository Element (NRF), Unified Data Management Element (UDM), Authentication Server Element (AUSF), Application Element (AF), Unified Data Warehouse Element (UDR), Unstructured Data Storage Element (UDSF), Short Message Service Element (SMSF), Network Slice Selection Element (NSSF), etc.

[0072] As an optional embodiment, the user terminal is identified based on the registration request to obtain an identification result, including: obtaining the user identifier in the registration request; if a specific identity field associated with the user identifier is detected, an identification result is generated to indicate that the user terminal corresponds to the specific identity field; if no specific identity field associated with the user identifier is detected, an identification result is generated to indicate that the user terminal is an ordinary user.

[0073] Specifically, the user identifier can be represented in any form, such as numbers, strings, or text, and this application embodiment does not impose any limitation. For example, the user identifier can be the IP address of the user terminal. Furthermore, the storage method of the user identifier and the specific identity field can be in key-value format or other formats, and this application embodiment does not impose any limitation. In addition, the aforementioned ordinary user can be understood as a user not associated with a specific identity field, which belongs to the metadata type.

[0074] As can be seen, by implementing this optional embodiment, the relationship between the user terminal and a specific identity field can be determined based on the identification results, thereby providing different base station information triggering methods for different types of users, thus improving the diversity of network services. When a user terminal is detected as a fixed-track user terminal, it can be applied to the base station switching timetable to realize the one-time transmission of pre-switching base station information without the need for frequent signal measurement, thereby saving network resources.

[0075] As an optional embodiment, the above method further includes: when a field deletion request for a user identifier is detected, deleting the specific identity field corresponding to the user identifier.

[0076] Specifically, the method to delete a specific identity field corresponding to a user identifier can be: to delete the association between the user identifier and the specific identity field.

[0077] As can be seen, by implementing this optional embodiment, when the user terminal is no longer a fixed-track user terminal, the specific identity field corresponding to it can be deleted. This can provide users with a base station information triggering method based on signal strength, so that different types of users can be applied to different base station information triggering methods.

[0078] As an optional embodiment, before obtaining the user identifier in the registration request, the method further includes: when a new request for a field of user identifier is detected, establishing an association between the user identifier and a specific identity field.

[0079] Specifically, the field addition request may include at least one of the following: user identifier, motion trajectory corresponding to the user identifier, etc. Additionally, optionally, before establishing the association between the user identifier and the specific identity field, the above method may further include: determining the user's motion trajectory based on the historical connection records between the user terminal and the base station; if the motion trajectory is detected to be periodic, then the user terminal is determined to be a fixed-track user terminal, where the fixed trajectory is the motion trajectory.

[0080] As can be seen, implementing this optional embodiment can provide a base station information triggering method based on the base station handover timetable when the user terminal is a fixed trajectory user terminal, avoiding the measurement overhead, ping-pong effect, and unexpected call drops caused by the existing signal measurement handover mechanism.

[0081] In step S220, if the identification result is used to indicate that the user terminal corresponds to a specific identity field, then the handover base station timetable corresponding to the user terminal is determined.

[0082] Specifically, different user terminals can correspond to different base station handover timetables. The base station handover timetable can include at least one base station sending time (e.g., 12:30) and base station information corresponding to each base station sending time.

[0083] In step S230, information about the pre-switched base station is sent to the user terminal based on the base station handover timetable; wherein, the user terminal is used to switch the currently connected base station to the pre-switched base station based on the information about the pre-switched base station.

[0084] Specifically, the information of the pre-switching base station may include the base station's address, code, and other identifiers, which are not limited in this application embodiment.

[0085] Please see Figure 3 , Figure 3 The illustration shows a schematic diagram of an application scenario according to an embodiment of this application. Figure 3 As shown in the diagram, this application scenario includes base station A, base station B, and base station C. When the car containing the user terminal moves to position 1, it can be based on... Figure 2 The steps shown send information about base station B to the user terminal, allowing the user terminal to switch its current connection from base station A to base station B based on this information. Furthermore, when the car containing the user terminal moves to position 2, it can... Figure 2 The steps shown send information about base station C to the user terminal, which can then switch its current connection from base station B to base station C based on this information. The user terminal can be an in-vehicle device, a driver's terminal, etc., and this embodiment does not limit the application to this type of device.

[0086] As an optional embodiment, sending information about the pre-handover base station to the user terminal based on the handover base station timetable includes: determining the pre-handover base station according to the fixed trajectory corresponding to the user terminal; and sending the pre-handover base station information to the user terminal based on the handover base station timetable.

[0087] Specifically, determining the pre-handover base station based on the fixed trajectory corresponding to the user terminal includes: determining the fixed trajectory corresponding to the user terminal, and determining the pre-handover base station based on the connection records of each base station on the fixed trajectory and the terminal currently connected to the user. Optionally, the pre-handover base station information is sent to the user terminal based on a handover base station timetable, including: determining the information transmission time according to the handover base station timetable and starting a timer, so as to send the pre-handover base station information to the user terminal when the timer indicates that the transmission time has arrived.

[0088] As can be seen, implementing this optional embodiment eliminates the need for frequent signal measurements of the user terminal. Since the user terminal is a fixed-track user terminal, it is only necessary to specify the base station information transmission time to achieve a one-time transmission of pre-switching base station information, thereby saving network resources.

[0089] As an optional embodiment, sending information about the pre-switched base station to the user terminal based on the handover base station timetable includes: sending the handover base station timetable to the mobility management network element; wherein the mobility management network element is used to determine the information sending time according to the handover base station timetable and start a timer, so as to send the information about the pre-switched base station to the user terminal when the timer indicates that the sending time has arrived.

[0090] Among them, the Access and Mobility Management Function (AMF) is a major functional unit of the 5G core network, used to implement mobility management for user terminal access.

[0091] As can be seen, implementing this optional embodiment can enable the distribution of pre-handover base station information through the mobility management network element, thereby enhancing the application depth of 5G core network functions.

[0092] As an optional embodiment, the above method further includes: when a change in the fixed trajectory corresponding to the user terminal is detected, updating the handover base station timetable corresponding to the user terminal.

[0093] Specifically, the method for updating the handover base station timetable corresponding to the user terminal can be as follows: determine the changed fixed trajectory, determine the connection time between the user terminal based on the fixed trajectory and each base station, and update the handover base station timetable corresponding to the user terminal according to the connection time of each base station.

[0094] As can be seen, by implementing this optional embodiment, the base station timetable can be updated according to the changes in the fixed trajectory, and a high degree of matching between the base station timetable and the user terminal can be achieved, thereby improving the accuracy of the pre-switching base station information.

[0095] Please see Figure 4 , Figure 4 A schematic diagram illustrating multi-party interaction according to an embodiment of this application is shown. Figure 4 As shown, it includes a user terminal 410, a base station 420, a mobile management network element 430, a service contract information network storage unit 440, and a service activation system 450.

[0096] The service activation system 450 can sign service agreements with the service subscription information network storage unit 440, enabling the service subscription information network storage unit 440 to associate user terminals with specific identity fields and store the handover base station timetable corresponding to the user terminal. The service activation system 450 can also update the handover base station timetable in the service subscription information network storage unit 440. Furthermore, the service activation system 450 can delete specific identity fields corresponding to user identifiers from the service subscription information network storage unit 440.

[0097] User terminal 410 is used to send a registration request to the core network so that the core network can perform identity type identification on user terminal 410 according to the registration request and obtain the identification result. If the identification result indicates that user terminal 410 corresponds to a specific identity field, the core network determines the handover base station timetable corresponding to user terminal 410 and sends the handover base station timetable to mobility management network element 430.

[0098] The mobility management network element 430 is used to determine the information transmission time according to the handover base station timetable and start a timer so as to send the information of base station 420 to user terminal 410 when the timer indicates that the transmission time has arrived.

[0099] User terminal 410 is used to switch the currently connected base station to base station 420 based on information from base station 420.

[0100] Please see Figure 5 , Figure 5 A schematic diagram illustrating multi-party interaction according to an embodiment of this application is shown. Figure 5 As shown, it includes user terminal 510, original base station 520, mobility management network element 530, pre-switching base station 540, user plane network element 550, and data management network element 560.

[0101] Specifically, user terminal 510 can send a registration request to the core network, enabling the core network to perform identity type identification on user terminal 510 based on the registration request and obtain the identification result. If the identification result indicates that user terminal 510 corresponds to a specific identity field, the core network determines the handover base station timetable corresponding to user terminal 510 and sends the handover base station timetable to mobility management network element 530. Mobility management network element 530 determines the information transmission time based on the handover base station timetable and starts a timer to send information about the pre-handover base station 550 to user terminal 510 when the timer indicates that the transmission time has arrived. User terminal 510 is used to switch its current connected original base station 520 to the pre-handover base station 550 based on the information about the pre-handover base station 550. After user terminal 510 establishes a connection with the pre-handover base station 550, it can request user services from user plane network element 550 based on the pre-handover base station 550. User plane network element 550 can obtain data in response to user services from data management network element 560 and return it to user terminal 510.

[0102] Please see Figure 6 , Figure 6 A sequence diagram illustrating multi-party interactions according to one embodiment of this application is shown schematically. Figure 6 As shown, it includes steps S610 to S650.

[0103] Step S610: The core network receives the registration request sent by the user terminal, and performs identity type identification on the user terminal according to the registration request to obtain the identification result.

[0104] Step S620: If the identification result indicates that the user terminal corresponds to a specific identity field, the core network determines the handover base station timetable corresponding to the user terminal and sends the handover base station timetable to the mobility management network element; wherein, the mobility management network element is used to determine the information sending time and start the timer according to the handover base station timetable.

[0105] Step S630: The core network sends information about the pre-switched base station to the user terminal based on the base station handover timetable.

[0106] Step S640: The user terminal establishes a connection with the pre-switching base station based on the information of the pre-switching base station.

[0107] Step S650: The user terminal disconnects from the original base station.

[0108] It should be noted that steps S610 to S650 are the same as... Figure 2 For the specific implementation details of steps S610 to S650, please refer to the examples shown. Figure 2 The steps and their embodiments shown are not repeated here.

[0109] It is evident that implementation Figure 6 The sequence diagram shown allows for the setting of a handover base station timetable for fixed-track user terminals corresponding to specific identity fields. When a user terminal is detected as a fixed-track user terminal, the handover base station timetable is applied to achieve a one-time transmission of pre-handover base station information, eliminating the need for frequent signal measurements and saving network resources. Furthermore, it can effectively utilize the information gain of fixed tracks to replace existing signal strength-based handover, optimizing the measurement overhead, ping-pong effect, and unexpected call drops caused by existing signal measurement handover mechanisms, thereby improving handover performance.

[0110] Furthermore, this example embodiment also provides a base station handover device. (See reference...) Figure 7 The base station handover device 700 shown, the base station handover device 700 and Figure 2 Corresponding to the steps shown, the base station handover device 700 may include:

[0111] User identification module 701 is used to receive registration requests sent by user terminals, identify the identity type of user terminals according to registration requests, and obtain identification results.

[0112] The handover base station timetable determination module 702 is used to determine the handover base station timetable corresponding to the user terminal when the identification result indicates that the user terminal corresponds to a specific identity field.

[0113] The information delivery module 703 is used to send information about the pre-switched base station to the user terminal based on the base station handover timetable; wherein, the user terminal is used to switch the currently connected base station to the pre-switched base station based on the information about the pre-switched base station.

[0114] It is evident that implementation Figure 7 The device shown can set a handover base station timetable for fixed-track user terminals corresponding to specific identity fields. When a user terminal is detected as a fixed-track user terminal, the pre-handover base station information is transmitted in one go according to the timetable, eliminating the need for frequent signal measurements and saving network resources. Furthermore, it can effectively utilize the information gain of fixed tracks to replace existing signal strength-based handover, optimizing the measurement overhead, ping-pong effect, and unexpected call drops caused by existing signal measurement handover mechanisms, thereby improving handover performance.

[0115] In one exemplary embodiment of this application, the information delivery module 703 sends information about the pre-handover base station to the user terminal based on the handover base station timetable, including:

[0116] The pre-handover base station is determined based on the fixed trajectory corresponding to the user terminal;

[0117] Information about the base station to be switched is sent to the user terminal based on the base station switching timetable.

[0118] As can be seen, implementing this optional embodiment eliminates the need for frequent signal measurements of the user terminal. Since the user terminal is a fixed-track user terminal, only the base station information transmission time needs to be specified to achieve a one-time transmission of the pre-handover base station information, thereby saving network resources. In an exemplary embodiment of this application, the information transmission module 703 sends the pre-handover base station information to the user terminal based on the base station handover timetable, including:

[0119] The system sends a handover base station timetable to the mobility management network element. The mobility management network element determines the information sending time based on the handover base station timetable and starts a timer to send the pre-handover base station information to the user terminal when the timer indicates that the sending time has arrived.

[0120] As can be seen, implementing this optional embodiment can enable the distribution of pre-handover base station information through the mobility management network element, thereby enhancing the application depth of 5G core network functions.

[0121] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0122] The base station handover timetable update module (not shown) is used to update the base station handover timetable corresponding to the user terminal when a change in the fixed trajectory corresponding to the user terminal is detected.

[0123] As can be seen, by implementing this optional embodiment, the base station timetable can be updated according to the changes in the fixed trajectory, and a high degree of matching between the base station timetable and the user terminal can be achieved, thereby improving the accuracy of the pre-switching base station information.

[0124] In one exemplary embodiment of this application, the user identification module 701 performs identity type identification on the user terminal based on the registration request, and obtains the identification result, including:

[0125] Retrieve the user identifier from the registration request;

[0126] If a specific identity field associated with a user identifier is detected, an identification result is generated to indicate that the user terminal corresponds to the specific identity field;

[0127] If no specific identity field associated with the user identifier is detected, an identification result is generated to indicate that the user terminal is a regular user.

[0128] As can be seen, by implementing this optional embodiment, the relationship between the user terminal and a specific identity field can be determined based on the identification results, thereby providing different base station information triggering methods for different types of users, thus improving the diversity of network services. When a user terminal is detected as a fixed-track user terminal, it can be applied to the base station switching timetable to realize the one-time transmission of pre-switching base station information without the need for frequent signal measurement, thereby saving network resources.

[0129] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0130] The field processing unit (not shown) is used to delete the specific identity field corresponding to the user identifier when a field deletion request for the user identifier is detected.

[0131] As can be seen, by implementing this optional embodiment, when the user terminal is no longer a fixed-track user terminal, the specific identity field corresponding to it can be deleted. This can provide users with a base station information triggering method based on signal strength, so that different types of users can be applied to different base station information triggering methods.

[0132] In one exemplary embodiment of this application, the above-described apparatus further includes:

[0133] The field processing unit is also used to establish an association between the user identifier and a specific identity field when a new field request for the user identifier is detected before the user identification module 701 obtains the user identifier in the registration request.

[0134] As can be seen, implementing this optional embodiment can provide a base station information triggering method based on the base station handover timetable when the user terminal is a fixed trajectory user terminal, avoiding the measurement overhead, ping-pong effect, and unexpected call drops caused by the existing signal measurement handover mechanism.

[0135] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0136] Since the functional modules of the base station handover device in the example embodiments of this application correspond to the steps of the example embodiments of the base station handover method described above, for details not disclosed in the device embodiments of this application, please refer to the embodiments of the base station handover method described above in this application.

[0137] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0138] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0139] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0140] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0141] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0142] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A base station handover method, characterized by, include: Receive a registration request sent by a user terminal, and identify the identity type of the user terminal according to the registration request to obtain the identification result; The user terminal is identified based on the registration request to obtain an identification result, including: obtaining a user identifier from the registration request; if a specific identity field associated with the user identifier is detected, generating an identification result indicating that the user terminal corresponds to the specific identity field; if no specific identity field associated with the user identifier is detected, generating an identification result indicating that the user terminal is a regular user; the identification result is used to determine the relationship between the user terminal and the specific identity field; a regular user is a user not associated with a specific identity field, and the specific identity field is used to indicate that the user terminal is a user terminal with a fixed trajectory; If the identification result is used to indicate that the user terminal corresponds to a specific identity field, then the handover base station timetable corresponding to the user terminal is determined; the handover base station timetable includes at least one base station dispatch time and base station information corresponding to each base station dispatch time; when a change in the fixed trajectory corresponding to the user terminal is detected, the handover base station timetable corresponding to the user terminal is updated; Based on the handover base station timetable, the user terminal sends information about the pre-handover base station to the user terminal; wherein, the user terminal is used to switch the currently connected base station to the pre-handover base station based on the information about the pre-handover base station; sending information about the pre-handover base station to the user terminal based on the handover base station timetable includes: sending the handover base station timetable to the mobility management network element; the mobility management network element is used to determine the information sending time according to the handover base station timetable and start a timer, so as to send the information about the pre-handover base station to the user terminal when the timer indicates that the sending time has arrived.

2. The method of claim 1, wherein, Based on the handover base station timetable, information about the pre-handover base station is sent to the user terminal, including: The pre-switching base station is determined based on the fixed trajectory corresponding to the user terminal; The information of the pre-switched base station is sent to the user terminal based on the switching base station timetable.

3. The method of claim 1, wherein, The method further includes: When a field deletion request for the user identifier is detected, the specific identity field corresponding to the user identifier is deleted.

4. The method according to claim 1, characterized in that, Before obtaining the user identifier from the registration request, the method further includes: When a new request for a field of the user identifier is detected, an association is established between the user identifier and the specific identity field.

5. A base station handover device, characterized in that, include: The user identification module is used to receive a registration request sent by a user terminal, and to identify the identity type of the user terminal according to the registration request to obtain the identification result. The user identification module is configured to: obtain a user identifier from the registration request; if a specific identity field associated with the user identifier is detected, generate an identification result indicating that the user terminal corresponds to the specific identity field; if no specific identity field associated with the user identifier is detected, generate an identification result indicating that the user terminal is a regular user; the identification result is used to determine the relationship between the user terminal and the specific identity field. Ordinary users are those who are not associated with a specific identity field. The specific identity field is used to indicate that the user terminal is a user terminal with a fixed trajectory. The base station handover timetable determination module is used to determine the base station handover timetable corresponding to the user terminal when the identification result indicates that the user terminal corresponds to a specific identity field; the base station handover timetable includes at least one base station dispatch time and base station information corresponding to each base station dispatch time; When a change in the fixed trajectory corresponding to the user terminal is detected, the handover base station timetable corresponding to the user terminal is updated. An information delivery module is used to send information about a pre-switched base station to the user terminal based on the handover base station timetable; wherein, the user terminal is used to switch the currently connected base station to the pre-switched base station based on the pre-switched base station information; sending information about a pre-switched base station to the user terminal based on the handover base station timetable is configured to: send the handover base station timetable to the mobility management network element; the mobility management network element is used to determine the information delivery time according to the handover base station timetable and start a timer, so as to send the information about the pre-switched base station to the user terminal when the timer indicates that the delivery time has arrived.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1-4.

7. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the method of any one of claims 1-4 by executing the executable instructions.

Images