A cell handover method and apparatus
By determining whether the target base station supports UPIP in the LTE network and selecting a base station with high signal quality and UPIP support as the handover target, the handover failure problem caused by the target base station not supporting UPIP is solved, thus improving network performance and user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI HUAWEI TECH CO LTD
- Filing Date
- 2022-12-22
- Publication Date
- 2026-04-17
AI Technical Summary
In LTE networks, handover failure occurs when the target base station does not support User Plane Integrity Protection (UPIP), impacting network performance.
When determining the target base station for handover, first determine whether it supports the UPIP function. If it does not support it, select a base station with high signal quality and that supports the UPIP function as the handover target. Use the X2 or S1 interface to interact with the core network equipment to obtain the protocol version or security result information of the base station to determine the support status and ensure the normal use of the UPIP function during the handover process.
It improved network performance, prevented handover failures, ensured the normal use of UPIP functions, and enhanced the user experience.
Smart Images

Figure CN118250761B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a cell handover method and apparatus. Background Technology
[0002] In a Long Term Evolution (LTE) network, the core network consists of core network equipment and evolved NodeBs (eNBs). The core network equipment includes a Mobility Management Entity (MME) and a Serving Gateway (SGW). The MME, belonging to the control plane, is responsible for mobility management, including user context and mobility state management, and assigning temporary user identities. The SGW, belonging to the user plane, is responsible for initiating paging for downlink data during idle states, managing and storing IP bearer parameters and network routing information. The MME and SGW are connected in a mesh network, with one MME controlling several SGWs. Core network equipment communicates with eNBs using the S1 interface, while eNBs communicate with each other using the X2 interface. The LTE Release 17 protocol introduced User Plane Integrity Protection (UPIP), which introduces three bearer-level user plane integrity protection policies (required, preferred, and not needed), including the mandatory required policy.
[0003] When a user equipment has a bearer with UPIP function enabled by the required policy, the source base station directly switches to the target base station after determining the target base station with the best signal quality.
[0004] However, when the target base station does not support UPIP, it cannot recognize protocol cells, which will lead to handover failure and affect network performance. Summary of the Invention
[0005] This application provides a cell handover method and apparatus for improving network performance.
[0006] The first aspect of this application provides a cell handover method, which includes: when a terminal device meets the cell handover conditions, a first access network device determines a second access network device, wherein the second access network device is the access network device with the highest handover priority within a preset range, the terminal device is connected to the first access network device, and the terminal device carries User Plane Integrity Protection (UPIP) functionality; the first access network device determines whether the second access network device supports UPIP functionality; when the second access network device does not support UPIP functionality, the first access network device determines a third access network device, wherein the handover priority of the third access network device is lower than that of the second access network device; the first access network device determines whether the third access network device supports UPIP functionality; when the third access network device supports UPIP functionality, the first access network device hands over the terminal device to the third access network device.
[0007] In the aforementioned aspects, when the first access network device determines that a terminal device carrying UPIP functionality needs to switch cells, and when determining the second access network device with the highest signal handover priority within a preset range, it first determines whether the second access network device supports UPIP functionality. If the second access network device does not support UPIP functionality, it reselects a third access network device with a lower priority than the second access network device among the access network devices supporting UPIP functionality within the preset range as the handover target, and then switches the terminal device to the third access network device. Since the third access network device supports UPIP functionality, it can identify protocol cells, and the signal quality of the third access network device is higher than that of the first access network device, thus improving network performance.
[0008] In one possible implementation, the step of the first access network device determining whether the second access network device supports the UPIP function includes: the first access network device obtaining the protocol version of the second access network device from local data; the first access network device determining whether the protocol version of the second access network device supports the UPIP function; when the protocol version of the second access network device supports the UPIP function, the first access network device determines that the second access network device supports the UPIP function; when the protocol version of the second access network device does not support the UPIP function, the first access network device determines that the second access network device does not support the UPIP function.
[0009] In the above possible implementations, the second access network device exchanges data with the first access network device via the X2 interface during setup. This means the protocol version of the second access network device is already stored in the local data of the first access network device. Therefore, when it's necessary to determine whether the second access network device supports UPIP, the first access network device can obtain the protocol version from its local data and then determine if the protocol version supports UPIP. If the protocol version supports UPIP, the second access network device supports UPIP; if it doesn't, it doesn't. Directly determining UPIP support from local data improves cell handover efficiency.
[0010] In one possible implementation, before the first access network device switches the terminal device to the third access network device, the method further includes: the first access network device sending a switching request to the third access network device, the switching request including context information of the bearer of the UPIP function; the first access network device receiving a switching response from the third access network device, the switching response being determined by the third access network device based on the context information; and when the switching response is an agreement to switch, triggering the first access network device to switch the terminal device to the third access network device.
[0011] In the above possible implementations, after determining to switch the terminal device to the third access network device, the first access network device also needs to confirm with the third access network device whether the switch is permissible. Specifically, it sends a switch request with context information of the bearer containing UPIP functionality to the third access network device. The third access network device can determine whether the terminal device can access the network based on this context information and then sends a switch response back to the first access network device. Only when the switch response indicates that the third access network device agrees to the switch can the first access network device switch the terminal device to the third access network device, thus improving the feasibility of the solution.
[0012] In one possible implementation, the step of the first access network device determining whether the second access network device supports the UPIP function includes: the first access network device sending a first handover request to the core network device, instructing the terminal device to hand over to the second access network device; the first access network device receiving a first handover command from the core network device; the first access network device determining whether the first handover command includes a security result information element; when the first handover command does not include a security result information element, the first access network device determines that the second access network device does not support the UPIP function; when the first handover command includes a security result information element, the first access network device determines that the second access network device supports the UPIP function.
[0013] In the above possible implementations, the first access network device cannot interact with the second access network device via the X2 interface. The core network device needs to determine whether the second access network device supports UPIP functionality. The first access network device can send a first handover request to the core network device, notifying it that the terminal device needs to be switched to the second access network device. After receiving the first handover request, the core network device can send a handover request to the second access network device and receive a handover request response from the second access network device. Then, the core network device sends a first handover command back to the first access network device. When the second access network device does not support UPIP functionality, the first handover command does not carry a security result information element; when the second access network device supports UPIP functionality, the first handover command carries the security result information element. That is, the first access network device can determine whether the second access network device supports UPIP functionality based on whether the first handover command carries a security result information element. When the X2 interface is unavailable, the S1 interface is used to determine whether the second access network device supports UPIP functionality, improving the flexibility of the solution.
[0014] In one possible implementation, after the first access network device determines whether the third access network device supports the UPIP function, the method further includes: when the third access network device does not support the UPIP function, the first access network device determines a fourth access network device, the handover priority of the fourth access network device being lower than that of the third access network device; the first access network device sends a second handover request to the core network device, instructing the terminal device to hand over to the fourth access network device; the first access network device receives a second handover command from the core network device; the first access network device determines whether the second handover command includes a security result information element; when the second handover command includes a security result information element, the first access network device determines that the fourth access network device supports the UPIP function; the first access network device hands over the terminal device to the fourth access network device.
[0015] In the above possible implementations, when the third access network device still does not support UPIP functionality, the first access network device can also send a second handover request to the core network device, notifying the core network that the terminal device is expected to switch to the fourth access network device. After receiving the first handover request, the core network device can send a handover request to the fourth access network device and receive a handover request response from the fourth access network device. Then, the core network device sends a second handover command back to the first access network device. Only when the second handover command carries the security result information element is the fourth access network device determined to be the final terminal device to be switched to, thus avoiding the impact of the access network device's lack of support for UPIP functionality on the user experience.
[0016] In one possible implementation, the method further includes: when the second handover command does not include a security result information element, the first access network device determines that the fourth access network device does not support the UPIP function; the first access network device selects a new access network device in descending order of handover priority and requests a handover from the core network device.
[0017] In the above possible implementations, if the second handover command still does not carry the security result information element, the first access network device selects a new access network device as the expected handover target for the core network device in descending order of handover priority. Multiple checks increase the probability of identifying an access network device supporting UPIP as the target, thus improving the user's call experience.
[0018] A second aspect of this application provides a communication apparatus capable of implementing the methods described in the first aspect or any of the possible embodiments of the first aspect. The apparatus includes corresponding units or modules for performing the described methods. The units or modules included in the apparatus can be implemented in software and / or hardware. The apparatus can be, for example, an access network device, a chip, chip system, or processor that supports the access network device in implementing the described methods, or a logic module or software capable of implementing all or part of the functions of the access network device.
[0019] A third aspect of this application provides a computer device, including: a processor coupled to a memory for storing instructions, which, when executed by the processor, cause the computer device to implement the methods described in the first aspect or any possible implementation thereof. The computer device may be, for example, an access network device, or a chip or chip system supporting the implementation of the methods in the access network device.
[0020] A fourth aspect of this application provides a computer-readable storage medium storing instructions that, when executed by a processor, implement the method provided in the first aspect or any possible implementation thereof.
[0021] The fifth aspect of this application provides a computer program product including computer program code, which, when executed on a computer, implements the method provided in the first aspect or any possible implementation thereof. Attached Figure Description
[0022] Figure 1 A network system architecture diagram provided for an embodiment of this application;
[0023] Figure 2 A flowchart illustrating a cell handover method provided in an embodiment of this application;
[0024] Figure 3This is a schematic diagram of an X2 switching process provided in an embodiment of this application;
[0025] Figure 4 This is a schematic diagram of an S1 switching process provided in an embodiment of this application;
[0026] Figure 5 This is a schematic diagram of the structure of a cell handover device provided in an embodiment of this application;
[0027] Figure 6 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0028] This application provides a cell handover method and apparatus for improving network performance.
[0029] The embodiments of this application are described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. As those skilled in the art will recognize, with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0030] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0031] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.
[0032] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, methods, means, components, and circuits well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.
[0033] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.
[0034] Due to the movement of terminal devices, they may move from the coverage area of one cell to the coverage area of another. Each cell can be identified by a unique number, called the cell identity (Cell ID). In this application, the Cell ID is described using the standard-defined cell global identity (CGI) as an example. The access network device sends measurement configuration information to the terminal device. This measurement configuration information may include information such as the measurement object (MO), measurement configuration, and measurement interval configuration. The measurement parameters of the measurement object may include the configuration of measurement resources on the frequency point corresponding to the measurement object, such as one or more cells on that frequency point. That is, the measurement parameters of the measurement object sent by the access network device to the terminal device may include a cell list, which includes one or more cells on that frequency point. The terminal device performs cell measurements based on the measurement configuration information and reports the measurement results to the access network device. The measurement results can include the terminal device measuring and calculating the reference signal received signal (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), and signal-to-interference-noise ratio (SINR) of the reference signals from multiple cells. Based on the measurement results from the serving cell and neighboring cells, the access network equipment determines the handover priority of each cell and can hand over the terminal device to a cell with a higher handover priority.
[0035] In this application embodiment, the access network device can be a base station, which can be used to communicate with one or more user equipments, or to communicate with one or more base stations that have partial user equipment functions (e.g., communication between macro base stations and micro base stations, such as access points); the terminal device is a user equipment, which can be used to communicate with one or more user equipments (e.g., D2D communication), or to communicate with one or more base stations. The user equipment can also be called a user terminal, and can include some or all of the functions of a system, user unit, user station, mobile station, mobile wireless terminal, mobile device, node, device, remote station, remote terminal, terminal, wireless communication device, wireless communication apparatus, or user agent. The user equipment can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, smartphone, wireless local loop (WLL) station, personal digital assistant (PDA), laptop computer, handheld communication device, handheld computing device, satellite wireless device, wireless modem card, and / or other processing devices for communication over a wireless system. A base station can also be referred to as an access point, node, Node B, evolved Node B, or some other network entity, and may include some or all of the functions of the above network entities. A base station can communicate with wireless terminals via an air interface. This communication can be carried out through one or more sectors. A base station can act as a router between wireless terminals and the rest of the access network, including IP networks, by converting received air interface frames into Internet Protocol (IP) packets. The base station can also coordinate the management of air interface attributes and can also act as a gateway between wired and wireless networks.
[0036] Reference Figure 1 The diagram shown is a network system architecture provided in an embodiment of this application. UE 1100 includes at least one processor 1101, at least one memory 1102, and at least one transceiver 1103. Optionally, UE 1100 may also include an output device 1104 and an input device 1105.
[0037] Processor 1101, memory 1102, and transceiver 1103 are connected via a bus. Processor 1101 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to this application. Processor 1101 can also be multiple processors, each of which can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).
[0038] The memory 1102 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory 1102 may exist independently and be connected to the processor 1101 via a bus. The memory 1102 may also be integrated with the processor 1101. The memory 1102 is used to store application code that executes the scheme of this application and is controlled by the processor 401 for execution. The processor 401 is used to execute computer program code stored in the memory 403, thereby implementing the method described in the embodiments of this application.
[0039] Transceiver 1103 can be used with any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. Transceiver 1103 includes a transmitter Tx and a receiver Rx.
[0040] Output device 1104 communicates with processor 401 and can display information in various ways. For example, output device 1104 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. Input device 1105 communicates with processor 1101 and can accept user input in various ways. For example, input device 1105 can be a mouse, keyboard, touch screen device, or sensor device, etc.
[0041] The eNB 1200 includes at least one processor 1201, at least one memory 1202, at least one transceiver 1203, and at least one network interface 1204. The network interface 1204 is used to connect to the network interface 1304 of the core network device 1300 via a link (e.g., an S1 interface), or to connect to the network interface 1204 of other eNBs via a wired or wireless link (e.g., an X2 interface). The functions of the components within the eNB 1200 are described in the same way as those described for the components within the UE 1100, and will not be repeated here.
[0042] Core network device 1300 can provide further network connectivity, such as telephone networks and / or data communication networks (e.g., the Internet). Core network device 1300 includes at least one processor 1301, at least one memory 1302, and at least one network interface 1304. The functions of the components within core network device 1300 are described in the functional description of the components within UE 1100, and will not be repeated here.
[0043] Core network equipment communicates with eNBs using the S1 interface, while eNBs communicate with each other using the X2 interface. The LTER17 protocol version introduced User Plane Integrity Protection (UPIP), which includes three bearer-level UPIP policies (required, preferred, and not needed), with the required policy being mandatory. When a user equipment has a bearer with UPIP enabled using the required policy, the source base station directly hands over to the target base station after determining the one with the best signal quality. However, if the target base station does not support UPIP, it cannot recognize protocol cells, leading to handover failure and impacting network performance.
[0044] To address the aforementioned issues, this application provides a cell handover method, as described below.
[0045] Please see Figure 2 ,like Figure 2 The diagram shown is a flowchart illustrating a cell handover method provided in an embodiment of this application. The method includes:
[0046] Step 201. When the terminal device meets the cell handover conditions, the first access network device determines the second access network device. The second access network device is the access network device with the highest handover priority within the preset range. The terminal device is connected to the first access network device, and the terminal device carries the user UPIP function.
[0047] In this embodiment, after receiving the measurement results sent by the terminal device, the first access network device can determine a handover priority list for neighboring cells within a preset range. This handover priority list includes cells with different handover priorities; that is, cells with higher handover priorities can provide a better user experience for the terminal device. When the terminal device connected to the first access network device meets the cell handover conditions, i.e., a handover priority list exists, in order to provide the best service to the user, the access network device with the highest handover priority (such as the second access network device) can be selected as the target access network device. The terminal device in this embodiment carries a required policy, i.e., it uses the UPIP function.
[0048] Step 202. The first access network device determines whether the second access network device supports the UPIP function.
[0049] In this embodiment, since the terminal device has a bearer using the UPIP function, the target access network device for switching also needs to support the UPIP function. That is, before the first access network device determines the switching, it also needs to determine whether the second access network device supports the UPIP function in order to ensure the normal use of the bearer using the UPIP function.
[0050] Since the first access network device and the second access network device can be connected via the X2 interface, the cell handover in this embodiment is an X2 handover. If the X2 interface of the first access network device or the second access network device is unavailable or the X2 handover fails, the S1 interface can be used for handover, that is, the cell handover in this embodiment is an S1 handover.
[0051] In the X2 handover scenario, the second access network device exchanges data with the first access network device through the X2 interface during establishment. That is, the protocol version of the second access network device is already stored in the local data of the first access network device. Therefore, when it is necessary to determine whether the second access network device supports the UPIP function, the first access network device can obtain the protocol version of the second access network device from its local data, and then determine whether the protocol version of the second access network device supports the UPIP function. That is, if the protocol version of the second access network device supports the UPIP function, the second access network device supports the UPIP function; if the protocol version of the second access network device does not support the UPIP function, the second access network device does not support the UPIP function.
[0052] Correspondingly, to determine whether a third access network device supports the UPIP function, the first access network device can also obtain the protocol version of the third access network device from local data, and then determine whether the protocol version of the third access network device supports the UPIP function.
[0053] In the S1 handover scenario, the first access network device cannot interact with the second access network device via the X2 interface. The core network device needs to determine whether the second access network device supports UPIP. The first access network device can send a first handover request to the core network device, notifying it that the terminal device needs to be handed over to the second access network device. After receiving the first handover request, the core network device can send a handover request to the second access network device and receive a handover request response from the second access network device. Then, the core network device sends a first handover command back to the first access network device. When the second access network device does not support UPIP, the first handover command does not carry a security result information element. When the second access network device supports UPIP, the first handover command carries this security result information element. In other words, the first access network device can determine whether the second access network device supports UPIP based on whether the first handover command carries a security result information element.
[0054] Correspondingly, to determine whether a third access network device supports UPIP, the first access network device can also send a request to the core network device to switch to the third access network device, and then determine whether the switching command returned by the core network carries a security result information element to determine whether the third access network device supports UPIP.
[0055] When the third access network device still does not support UPIP, the first access network device can send a second handover request to the core network device, notifying the core network that the terminal device is expected to hand over to the fourth access network device. After receiving the first handover request, the core network device can send a handover request to the fourth access network device and receive a handover request response from the fourth access network device. Then, the core network device sends a second handover command back to the first access network device. Only when the second handover command carries the security result information element is the fourth access network device determined to be the final terminal device to be handed over.
[0056] If the second handover command still does not carry the security result information element, the first access network device will select a new access network device as the expected handover target for the core network device in descending order of handover priority.
[0057] Step 203. When the second access network device does not support UPIP function, the first access network device determines the third access network device, and the handover priority of the third access network device is lower than that of the second access network device.
[0058] In this embodiment, if it is determined that the protocol version of the second access network device does not support the UPIP function, then it is necessary to reselect the access network device as the handover target. The first access network device can select the second-best access network device from the handover priority list, that is, select the third access network device with a handover priority lower than that of the second access network device as the handover target.
[0059] Step 204. The first access network device determines whether the third access network device supports the UPIP function.
[0060] In this embodiment, after selecting the third access network device, it is necessary to further determine whether the third access network device can support the UPIP bearer of the terminal device, that is, whether it supports the UPIP function.
[0061] Step 205. When the third access network device supports the UPIP function, the first access network device switches the terminal device to the third access network device.
[0062] In this embodiment, if it is determined that the third access network device supports the UPIP function, the first access network device can determine that the terminal device can be switched to the third access network device. The first access network device can send a radio resource control (RRC) connection reconfiguration message to the terminal device to notify the terminal device to switch to the third access network device.
[0063] After deciding to switch the terminal device to the third access network device, the first access network device also needs to confirm with the third access network device whether the switch is possible. That is, it sends a switch request with context information of the bearer with UPIP function to the third access network device. The third access network device can determine whether the terminal device can access the network based on the context information, and then send a switch response back to the first access network device. Only when the switch response indicates that the third access network device agrees to the switch can the first access network device switch the terminal device to the third access network device.
[0064] For X2 switching scenarios, the processing flow of this application embodiment can be as follows: Figure 3 As shown, step 301. When it is determined that the terminal device meets the cell handover conditions, the first access network device determines the second access network device; step 302. The first access network device determines whether the second access network device supports the UPIP function based on the protocol version of the second access network device in the local data; step 303. When the second access network device does not support the UPIP function, the first access network device determines the third access network device; step 304. The first access network device determines whether the third access network device supports the UPIP function; step 305. When the third access network device supports the UPIP function, the first access network device sends a handover request to the third access network device; step 306. The third access network device sends a handover request response back to the first access network device; step 307. When the handover request response is "agree to handover," the first access network device sends an RRC connection reconfiguration message for the third access network device to the terminal device. Subsequent procedures can refer to the X2 handover processing flow in 3GPP 36.423.
[0065] For the S1 switching scenario, the processing flow of this application embodiment can be as follows: Figure 4As shown, step 401. When it is determined that the terminal device meets the cell handover conditions, the first access network device determines the second access network device; step 402. The first access network device sends a first handover request to the core network device for the second access network device; step 403. The core network device sends a third handover request to the second access network device; step 404. The second access network device sends a third handover request response to the core network device; step 405. The core network device sends a first handover command to the first access network device according to the third handover request response; step 406. When the first handover command does not include a security result information element, the first access network device... Step 407. The first access network device is identified as the expected handover target. Step 408. The core network device sends a fourth handover request to the third access network device. Step 409. The third access network device sends a fifth handover request to the third access network device. Step 410. The core network sends a fifth handover request response to the core network device. Step 411. The core network sends a fourth handover command to the first access network device based on the fifth handover request response. Step 412. When the fourth handover command includes a security result information element, the first access network device sends an RRC connection reconfiguration message for the third access network device to the terminal device. Subsequent procedures can refer to the X2 handover processing flow in 3GPP 36.423.
[0066] In this embodiment, when the first access network device determines that a UE carrying UPIP functionality needs to switch cells, it first determines whether the second access network device, which has the highest signal handover priority within a preset range, supports UPIP. If the second access network device does not support UPIP, it then selects a third access network device with a lower priority than the second access network device among the access network devices supporting UPIP within the preset range as the handover target, and then switches the terminal device to the third access network device. Since the third access network device supports UPIP, it can identify protocol cells, and its signal quality is higher than that of the first access network device, thus improving network performance.
[0067] The cell handover method has been described above; the device that performs this method will be described below.
[0068] Please see Figure 5 ,like Figure 5 The diagram shows a cell handover device 50 provided in an embodiment of this application. The device 50 includes:
[0069] The processing unit 501 is configured to, when the terminal device meets the cell handover conditions, determine a second access network device, which is the access network device with the highest handover priority within a preset range, the terminal device is connected to the device, and the terminal device carries the User Plane Integrity Protection (UPIP) function, determine whether the second access network device supports the UPIP function, and if the second access network device does not support the UPIP function, determine a third access network device, the handover priority of the third access network device is lower than that of the second access network device, determine whether the third access network device supports the UPIP function, and if the third access network device supports the UPIP function, handover the terminal device to the third access network device.
[0070] The processing unit 501 is used to execute Figure 2 Steps 201 to 205 in the method embodiment.
[0071] Optionally, the processing unit 501 is specifically used for:
[0072] Obtain the protocol version of the second access network device from local data;
[0073] Determine whether the protocol version of the second access network device supports UPIP functionality;
[0074] When the protocol version of the second access network device supports the UPIP function, it is determined that the second access network device supports the UPIP function.
[0075] If the protocol version of the second access network device does not support the UPIP function, it is determined that the second access network device does not support the UPIP function.
[0076] Optionally, the device 50 further includes a transceiver unit 502, which is specifically used for:
[0077] Send a handover request to the third access network device. The handover request includes the context information of the bearer of the UPIP function.
[0078] Receive a handover response from a third access network device, the handover response being determined by the third access network device based on context information;
[0079] When the handover response is "agree to handover", the terminal device will be switched to the third access network device.
[0080] Optionally, the device 50 further includes a transceiver unit 502, which is specifically used for:
[0081] Send a first handover request to the core network equipment, instructing the terminal equipment to switch to the second access network equipment;
[0082] Receive the first handover command from the core network equipment;
[0083] Processing unit 501 is specifically used for:
[0084] Determine whether the first switching command includes a security result information element;
[0085] When the first handover command does not include a security result information element, it is determined that the second access network device does not support the UPIP function;
[0086] When the first handover command includes a security result information element, it is determined that the second access network device supports the UPIP function.
[0087] Optionally, the processing unit 501 is also used for:
[0088] When the third access network device does not support UPIP function, the fourth access network device is determined. The handover priority of the fourth access network device is lower than that of the third access network device.
[0089] Transceiver unit 502 is also used for:
[0090] Send a second handover request to the core network equipment, instructing the terminal equipment to switch to the fourth access network equipment;
[0091] Receive the second handover command from the core network equipment;
[0092] Processing unit 501 is also used for:
[0093] Determine whether the second switching command includes a security result information element;
[0094] When the second handover command includes a security result information element, it is determined that the fourth access network device supports the UPIP function;
[0095] Switch the terminal device to the fourth access network device.
[0096] Optionally, the processing unit 501 is also used for:
[0097] When the second handover command does not include a security result information element, it is determined that the fourth access network device does not support the UPIP function;
[0098] The new access network device is selected in descending order of handover priority and a handover request is sent to the core network device.
[0099] Figure 6 The diagram shown illustrates a possible logical structure of a computer device 60 provided in an embodiment of this application. The computer device 60 includes a processor 601, a communication interface 602, a storage system 603, and a bus 604. The processor 601, communication interface 602, and storage system 603 are interconnected via the bus 604. In an embodiment of this application, the processor 601 is used to control and manage the operations of the computer device 60; for example, the processor 601 is used to execute... Figure 2The steps performed by the first access network device in the method embodiment are as follows. Communication interface 602 is used to support communication by computer device 60. Storage system 603 is used to store program code and data of computer device 60.
[0100] The processor 601 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor 601 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The bus 604 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0101] The transceiver unit 502 in device 50 is equivalent to the communication interface 602 in computer device 60, and the processing unit 501 in device 50 is equivalent to the processor 601 in computer device 60.
[0102] The computer device 60 in this embodiment can correspond to the above-described... Figure 2 In the first access network device of the method embodiment, the communication interface 602 in the computer device 60 can implement the above-mentioned... Figure 2 For the sake of brevity, the functions and / or steps implemented by the first access network device in the method embodiment will not be described in detail here.
[0103] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, and others in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element mentioned here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.
[0104] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).
[0105] In another embodiment of this application, a computer-readable storage medium is also provided, which stores computer-executable instructions. When the processor of the device executes the computer-executable instructions, the device executes the method described in the above method embodiment for checking the execution of the device.
[0106] In another embodiment of this application, a computer program product is also provided, which includes computer-executable instructions stored in a computer-readable storage medium. When the processor of the device executes the computer-executable instructions, the device performs the method described in the above method embodiment for checking the execution of the device.
[0107] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0108] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.
[0109] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0110] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0111] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A cell handover method, characterized by, include: When the terminal device meets the cell handover conditions, the first access network device determines the second access network device. The second access network device is the access network device with the highest handover priority within a preset range. The terminal device is connected to the first access network device, and the terminal device carries the User Plane Integrity Protection (UPIP) function. The first access network device determines whether the second access network device supports the UPIP function. Whether the second access network device supports the UPIP function is determined based on whether the protocol version of the second access network device in the local data of the first access network device supports the UPIP function, or whether the second access network device supports the UPIP function is determined based on whether the first handover command from the core network device includes a security result information element. In the case that the first handover command includes the security result information element, the second access network device supports the UPIP function; in the case that the first handover command does not include the security result information element, the second access network device does not support the UPIP function. When the second access network device does not support the UPIP function, the first access network device determines a third access network device, and the handover priority of the third access network device is lower than that of the second access network device. The first access network device determines whether the third access network device supports the UPIP function; When the third access network device supports the UPIP function, the first access network device switches the terminal device to the third access network device.
2. The method of claim 1, wherein, When the determination of whether the second access network device supports the UPIP function is based on whether the protocol version of the second access network device supports the UPIP function in the local data of the first access network device, the first access network device determines whether the second access network device supports the UPIP function by including: The first access network device obtains the protocol version of the second access network device from local data; The first access network device determines whether the protocol version of the second access network device supports the UPIP function; When the protocol version of the second access network device supports the UPIP function, the first access network device determines that the second access network device supports the UPIP function. When the protocol version of the second access network device does not support the UPIP function, the first access network device determines that the second access network device does not support the UPIP function.
3. The method of claim 2, wherein, Before the first access network device switches the terminal device to the third access network device, the method further includes: The first access network device sends a handover request to the third access network device, the handover request including the context information of the bearer of the UPIP function; The first access network device receives a handover response from the third access network device, the handover response being determined by the third access network device based on the context information; When the handover response is "agree to handover", the first access network device is triggered to switch the terminal device to the third access network device.
4. The method of claim 1, wherein, When the determination of whether the second access network device supports the UPIP function is based on whether the first handover command from the core network device includes a security result information element, the first access network device determines whether the second access network device supports the UPIP function by including: The first access network device sends a first handover request to the core network device, instructing the terminal device to switch to the second access network device; The first access network device receives a first handover command from the core network device; The first access network device determines whether the first handover command includes a security result information element; When the first switching command does not include the security result information element, the first access network device determines that the second access network device does not support the UPIP function; When the first switching command includes the security result information element, the first access network device determines that the second access network device supports the UPIP function.
5. The method of claim 4, wherein, After the first access network device determines whether the third access network device supports the UPIP function, the method further includes: When the third access network device does not support the UPIP function, the first access network device determines a fourth access network device, and the handover priority of the fourth access network device is lower than that of the third access network device. The first access network device sends a second handover request to the core network device, instructing the terminal device to switch to the fourth access network device; The first access network device receives a second handover command from the core network device; The first access network device determines whether the second handover command includes a security result information element; When the second switching command includes the security result information element, the first access network device determines that the fourth access network device supports the UPIP function; The first access network device switches the terminal device to the fourth access network device.
6. The method of claim 5, wherein, The method further includes: When the second switching command does not include the security result information element, the first access network device determines that the fourth access network device does not support the UPIP function. The first access network device selects a new access network device in descending order of the handover priority and requests a handover from the core network device.
7. A cell handover apparatus, characterized by comprising: include: The processing unit is configured to, when a terminal device meets the cell handover conditions, determine a second access network device, wherein the second access network device is the access network device with the highest handover priority within a preset range, the terminal device is connected to the device, and the terminal device carries the User Plane Integrity Protection (UPIP) function, and determine whether the second access network device supports the UPIP function. Whether the second access network device supports the UPIP function is determined based on whether the protocol version of the second access network device supports the UPIP function in the local data of the first access network device, or based on whether the first handover command from the core network device includes a security result information element. Wherein, if the first handover command includes the security result information element, the second access network device supports the UPIP function; if the first handover command does not include the security result information element, the second access network device does not support the UPIP function. When the second access network device does not support the UPIP function, a third access network device is determined, wherein the handover priority of the third access network device is lower than that of the second access network device, and whether the third access network device supports the UPIP function is determined. If the third access network device supports the UPIP function, the terminal device is handover to the third access network device.
8. The apparatus of claim 7, wherein, When the determination of whether the second access network device supports the UPIP function is based on whether the protocol version of the second access network device supports the UPIP function in the local data of the first access network device, the processing unit is specifically used for: Obtain the protocol version of the second access network device from local data; Determine whether the protocol version of the second access network device supports the UPIP function; When the protocol version of the second access network device supports the UPIP function, it is determined that the second access network device supports the UPIP function. When the protocol version of the second access network device does not support the UPIP function, it is determined that the second access network device does not support the UPIP function.
9. The apparatus of claim 8, wherein, The device further includes a transceiver unit, which is specifically used for: A handover request is sent to the third access network device, the handover request including the context information of the bearer of the UPIP function; Receive a handover response from the third access network device, the handover response being determined by the third access network device based on the context information; When the handover response is "agree to handover", the terminal device is switched to the third access network device.
10. The apparatus of claim 7, wherein, When the determination of whether the second access network device supports the UPIP function is based on whether the first handover command from the core network device includes a security result information element, the device further includes a transceiver unit, which is specifically used for: Send a first handover request to the core network equipment, instructing the terminal equipment to switch to the second access network equipment; Receive the first handover command from the core network device; The processing unit is specifically used for: Determine whether the first switching command includes a security result information element; When the first switching command does not include the security result information element, it is determined that the second access network device does not support the UPIP function; When the first switching command includes the security result information element, it is determined that the second access network device supports the UPIP function.
11. The apparatus of claim 10, wherein, The processing unit is also used for: When the third access network device does not support the UPIP function, a fourth access network device is determined, and the handover priority of the fourth access network device is lower than that of the third access network device. The transceiver unit is also used for: Send a second handover request to the core network device, instructing the terminal device to switch to the fourth access network device; Receive a second handover command from the core network device; The processing unit is also used for: Determine whether the second switching command includes a security result information element; When the second switching command includes the security result information element, it is determined that the fourth access network device supports the UPIP function; Switch the terminal device to the fourth access network device.
12. The apparatus of claim 11, wherein, The processing unit is also used for: When the second switching command does not include the security result information element, it is determined that the fourth access network device does not support the UPIP function; A new access network device is selected in descending order of the handover priority to request a handover from the core network device.
13. A computer device, comprising: include: Processor and memory, The processor is configured to execute instructions stored in the memory, causing the computer device to perform the method of any one of claims 1 to 6.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on the computer, causes the computer to perform the method as described in any one of claims 1 to 6.
15. A computer program product, characterised in that, When the computer program product is executed on a computer, the computer performs the method as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Security activation method and communication device
CN115396884A