Handover method and apparatus

Abstract

A handover method and an apparatus. The method comprises: receiving relay information from a core network element, wherein the relay information comprises a network device handover condition and an identifier of a relay node; handing over from a first network device to a second network device on the basis of the network device handover condition; and receiving a handover response from the second network device, wherein the handover response is sent by the second network device on the basis of an authentication result after the second network device authenticates the identifier. According to the present application, by means of the authentication of the identifier of the relay node and according to the authentication result, the connection handover between the relay node and different network devices is completed, thereby avoiding additional session indication information, reducing the data transmission and the signaling overhead, and improving the network device handover efficiency of the relay node.

Description

Switching method and device

[0001] This application claims priority to Chinese Patent Application No. 202410358721.3, filed on March 25, 2024, entitled “Switching Method and Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a switching method and apparatus. Background Technology

[0003] Non-terrestrial networks (NTNs), including nodes such as satellite networks, high-altitude platforms, and drones, offer significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and freedom from geographical limitations. They have been widely applied in various fields including maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. The integration of terrestrial 5G networks and satellite networks, leveraging their respective strengths, forms a seamless global communication network encompassing land, sea, air, space, and ground, meeting the diverse and ubiquitous service needs of users.

[0004] In satellite communication systems, the movement of satellite nodes can cause group handover or group reselection issues for users within a certain area (or band). Due to the rapid movement of satellite nodes, the distances between the multiple base stations involved in group handover or reselection are often large and there are usually no interfaces. Therefore, relay nodes are needed for group handover or reselection. Furthermore, group handover is frequent in satellite communication scenarios, and existing handover or reselection procedures are suitable for static relay nodes, resulting in high data transmission latency and are not suitable for the mobility of relay nodes. Therefore, new targeted designs are needed for mobile relay scenarios to improve the effectiveness of mobility management. Summary of the Invention

[0005] This application provides a switching method and apparatus for improving switching efficiency.

[0006] In a first aspect, embodiments of this application provide a handover method that can be applied to a relay node, such as a relay node or a component (e.g., a circuit, chip, or chip system) within a relay node. Taking the application of this method to a relay node as an example, the method includes: receiving relay information from a core network element, wherein the relay information includes network device handover conditions and an identifier of the relay node; handover from a first network device to a second network device according to the network device handover conditions; and receiving a handover response from the second network device, wherein the handover response is sent by the second network device after authenticating the identifier based on the authentication result.

[0007] By using the above method, network devices can be switched based on the authentication result by authenticating the dedicated identifier of the relay node, thus avoiding the signaling overhead caused by unnecessary transmission of user data during the authentication process. In addition, the switching is performed according to the switching conditions of the network devices, which simplifies the switching process and improves the switching efficiency.

[0008] In one possible design, the network device switching conditions include at least one of the following: the clock of the relay node is at a first time node; the distance between the location of the relay node and a preset reference location satisfies a first threshold; the signal quality between the relay node and the first network device is less than a second threshold and / or the signal quality between the relay node and the second network device is greater than a third threshold.

[0009] By adopting the above method, multiple factors such as location, time, and signal quality can be considered during handover, avoiding the low efficiency of network device handover under the influence of a single factor and improving the flexibility of network control.

[0010] In one possible design, after receiving relay information from the core network element, the method further includes sending a configuration response to the first network device.

[0011] In one possible design, after receiving the handover response sent by the second network device after authenticating the identifier, the method further includes: completing data transmission between the terminal device and the second network device based on the handover response; or, rejecting data transmission between the terminal device and the second network device based on the handover response.

[0012] In one possible design, the handover response includes control signaling; the step of completing data transmission between the terminal device and the second network device based on the handover response includes: completing data transmission between the terminal device and the second network device based on the control signaling.

[0013] In one possible design, the relay node includes a first relay sub-node and a second relay sub-node.

[0014] In one possible design, the method further includes: receiving a service request from a terminal device; in response to the service request being a first type of service, performing store-and-forward service data corresponding to the service request through the first relay sub-node; and / or in response to the service request being a second type of service, performing transparent forwarding of service data corresponding to the service request through the second relay sub-node.

[0015] By using the above method, the relay nodes can be configured to adopt corresponding forwarding modes for different types of services, which can not only meet the service quality requirements of the services, but also improve the efficiency of data forwarding.

[0016] In one possible design, the relay information is generated by the core network element based on the target access request; before receiving the relay information from the core network element, the method further includes: sending the target access request to the core network element.

[0017] In one possible design, sending the target access request to the core network element includes: sending the target access request to the core network element through the first network device; receiving relay information from the core network element includes: receiving relay information sent by the core network element through the first network device.

[0018] In one possible design, the target access request includes node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with multiple network devices.

[0019] By using the above method, relay nodes can be adapted according to their capabilities, thereby reducing mobility interruption latency.

[0020] In one possible design, the method further includes: updating the configuration information of the first network device according to the type of the cell corresponding to the first network device; or updating the configuration information of the second network device according to the type of the cell corresponding to the second network device.

[0021] By using the above method, different types of cells can adopt corresponding configuration update methods, which can reduce the frequency of configuration information updates.

[0022] In one possible design, the cell type is either a non-terrestrial network cell or a terrestrial network cell; updating the configuration information of the first network device according to the cell type includes: updating the configuration information of the first network device based on an event trigger in response to the cell type being a terrestrial network cell; updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation status in response to the cell type being a non-terrestrial network cell; updating the configuration information of the second network device according to the cell type is also included: updating the configuration information of the second network device based on an event trigger in response to the cell type being a terrestrial network cell; updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation status in response to the cell type being a non-terrestrial network cell.

[0023] In one possible design, the method further includes: responding to updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation state without triggering the update of the system information block (such as SIB1); or responding to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation state without triggering the update of the system information block (such as SIB1).

[0024] In one possible design, the target access request includes session-free indication information.

[0025] Secondly, embodiments of this application provide a handover method that can be applied to a second network device, such as the second network device or a component (e.g., a circuit, chip, or chip system) within the second network device. Taking the application of this method to a second network device as an example, it includes: receiving an identifier of a relay node sent by a core network element; authenticating the identifier; and sending a handover response to the relay node based on the authentication result.

[0026] By using the above method, network devices can be switched based on the authentication result by authenticating the dedicated identifier of the relay node, thus avoiding the signaling overhead caused by unnecessary transmission of user data during the authentication process. In addition, the switching is performed according to the switching conditions of the network devices, which simplifies the switching process and improves the switching efficiency.

[0027] In one possible design, after sending a handover response to the relay node based on the authentication result, the method further includes: sending a connection establishment response to the core network element, wherein the connection establishment response includes the identifier of the relay node.

[0028] In one possible design, the relay information further includes local network device authentication information; the method further includes: in response to the second network device not existing in the local network device authentication information, sending a context update request to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node; and receiving the updated local network device authentication information and / or the identifier of the relay node sent by the core network element.

[0029] In one possible design, before sending the context update request to the core network element, the method further includes: receiving a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has authentication information in the local network device.

[0030] Thirdly, embodiments of this application provide a communication device applied to a relay node, configured to perform the following steps: receiving relay information from a core network element, wherein the relay information includes network device switching conditions and an identifier of the relay node; switching from a first network device to a second network device according to the network device switching conditions; receiving a control signaling switching response from the second network device, wherein the control signaling switching response is sent by the second network device after authenticating the identifier, based on the authentication result. The operations and beneficial effects performed by this communication device can be found in the method and beneficial effects described in the first aspect above.

[0031] In one possible design, the network device switching conditions include at least one of the following conditions: the clock of the relay node is at a first time node; the distance between the location of the relay node and a preset reference location satisfies a first threshold; the signal quality between the relay node and the first network device is less than a second threshold and / or the signal quality between the relay node and the second network device is greater than a third threshold.

[0032] In one possible design, the device is further configured to send a configuration response to the first network device.

[0033] In one possible design, the device is further configured to complete data transmission between the terminal device and the second network device based on the handover response; or to reject data transmission between the terminal device and the second network device based on the handover response.

[0034] In one possible design, the handover response includes control signaling; the step of completing data transmission between the terminal device and the second network device based on the handover response includes: completing data transmission between the terminal device and the second network device based on the control signaling.

[0035] In one possible design, the relay node includes a first relay sub-node and a second relay sub-node.

[0036] In one possible design, the device is further configured to: receive a service request from a terminal device; in response to the service request being a first type of service, store and forward the service data corresponding to the service request through the first relay sub-node; and / or in response to the service request being a second type of service, transparently forward the service data corresponding to the service request through the second relay sub-node.

[0037] In one possible design, the relay information is generated by the core network element based on the target access request; the device is further configured to send the target access request to the core network element.

[0038] In one possible design, the device is further configured to: send the target access request to the core network element through the first network device; receiving relay information from the core network element includes: receiving relay information sent by the core network element through the first network device.

[0039] In one possible design, the target access request includes node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with multiple network devices.

[0040] In one possible design, the device is further configured to: update the configuration information of the first network device according to the type of the cell corresponding to the first network device; or update the configuration information of the second network device according to the type of the cell corresponding to the second network device.

[0041] In one possible design, the cell type is either a non-terrestrial network cell or a terrestrial network cell; the device is further configured to: update the configuration information of the first network device according to an event trigger in response to the cell type being a terrestrial network cell; update the configuration information of the first network device according to a preset period and / or the neighbor cell activation status in response to the cell type being a non-terrestrial network cell; update the configuration information of the second network device according to an event trigger in response to the cell type being a terrestrial network cell; and update the configuration information of the second network device according to a preset period and / or the neighbor cell activation status in response to the cell type being a non-terrestrial network cell.

[0042] In one possible design, the device is further configured to: in response to updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation state, not trigger the update of the System Information Block (SIB); or in response to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation state, not trigger the update of the System Information Block (SIB1).

[0043] In one possible design, the target access request includes session-free indication information.

[0044] Fourthly, embodiments of this application also provide a communication device applied to a second network device side, configured to perform the following steps: receiving an identifier of a relay node sent by a core network element; authenticating the identifier; and sending a handover response to the relay node based on the authentication result. The operation and beneficial effects of this communication device can be found in the method described in the second aspect above, as well as its beneficial effects.

[0045] In one possible design, the device is further configured to send a connection establishment response to the core network element, wherein the connection establishment response includes the identifier of the relay node.

[0046] In one possible design, the relay information further includes local network device authentication information; the device is further configured to: in response to the second network device not existing in the local network device authentication information, send a context update request to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node; and receive the updated local network device authentication information and / or the identifier of the relay node sent by the core network element.

[0047] In one possible design, the device is further configured to receive a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has authentication information in the local network device.

[0048] Fifthly, this application provides a communication device capable of executing the method described in the first aspect. The communication device possesses the functions described in the first aspect; for example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The operations performed by this communication device and its beneficial effects are described in the first aspect and its beneficial effects. In one possible design, the communication device includes a processing unit.

[0049] In one possible design, the communication device further includes a transceiver unit.

[0050] In one possible design, the communication device further includes a storage unit.

[0051] In one possible design, the communication device further includes a transceiver unit and a storage unit.

[0052] Sixthly, this application provides a communication device capable of executing the method described in the second aspect. The communication device possesses the functions described in the second aspect. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware. The operations performed by this communication device and its beneficial effects are described in the second aspect and can be found in the description of the method and its beneficial effects.

[0053] In one possible design, the communication device includes a processing unit.

[0054] In one possible design, the communication device further includes a transceiver unit.

[0055] In one possible design, the communication device further includes a storage unit.

[0056] In one possible design, the communication device further includes a transceiver unit and a storage unit.

[0057] In a seventh aspect, the application provides a communication device comprising a memory and one or more processors. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the first aspect. The one or more processors are capable of executing the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first aspect.

[0058] In one possible design, the communication device may further include an interface circuit, wherein the processor is used to communicate with other devices or components through the interface circuit.

[0059] In one possible design, the communication device may also include the memory.

[0060] The aforementioned communication device may be a terminal, a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip that contains a modem module.

[0061] Eighthly, this application provides a communication device including a memory and one or more processors. The memory stores part or all of the computer program or instructions necessary for implementing the functions described in the second aspect above. The one or more processors are executable to carry out the computer program or instructions, causing the communication device to implement the methods in any possible design or implementation of the second aspect above when the computer program or instructions are executed.

[0062] Ninthly, this application provides a communication system comprising: the apparatus described in the third aspect and the apparatus described in the fourth aspect; or, the apparatus described in the fifth aspect and the apparatus described in the sixth aspect; or, the apparatus described in the seventh aspect and the apparatus described in the eighth aspect.

[0063] Tenthly, this application provides a computer-readable storage medium storing instructions or programs that, when executed on a communication device, cause the communication device to perform the methods of the first aspect, the second aspect, any possible implementation of the first aspect, or any possible implementation of the second aspect.

[0064] Eleventhly, this application provides a computer program product, the computer program product including a computer program or instructions, and instructions for the method in the first aspect, the second aspect, any possible implementation of the first aspect, or any possible implementation of the second aspect when the computer program or instructions are run on a computer. Attached Figure Description

[0065] Figure 1 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0066] Figure 2 is a schematic diagram of a network architecture based on NCR provided in an embodiment of this application;

[0067] Figure 3 is a schematic flowchart of a network device switching method provided in an embodiment of this application;

[0068] Figure 4 is a schematic diagram of an NCR node switching process provided in an embodiment of this application;

[0069] Figure 5A is a schematic diagram of data transmission during NCR soft handover as shown in an embodiment of this application;

[0070] Figure 5B is a schematic diagram of data transmission during NCR hard handover as shown in an embodiment of this application;

[0071] Figure 6A is a schematic diagram of NCR node data transmission according to an embodiment of this application;

[0072] Figure 6B is a schematic diagram of another NCR node data transmission according to an embodiment of this application;

[0073] Figure 7 is a schematic flowchart of another network device switching method provided in an embodiment of this application;

[0074] Figure 8 is a schematic diagram of a communication system structure provided in an embodiment of this application;

[0075] Figure 9 is a schematic diagram of the structure of another communication device provided in an embodiment of this application; and...

[0076] Figure 10 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. Detailed Implementation

[0077] This application provides a network device switching method, communication device, system, storage medium, and computer program product to ensure normal access for mobile relay devices. The technical solutions in this application will be described below with reference to the accompanying drawings.

[0078] The technical solution of this application can be applied to terrestrial networks (TN), non-terrestrial networks (NTN), or scenarios where NTN and TN are integrated. NTN systems can be, for example, satellite communication systems, high altitude platform station (HAPS) communication systems, global navigation satellite systems (GNSS), etc. TN systems can be, for example, fourth-generation (4G) communication systems (e.g., long term evolution (LTE) systems), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) communication systems (e.g., new radio (NR) systems), sixth-generation (6G) mobile communication systems, and future mobile communication systems, etc.

[0079] To better understand the embodiments of this application, the network architecture of the embodiments of this application will be described below. Please refer to Figure 1, which is a schematic diagram of a network architecture provided by an embodiment of this application. As shown in Figure 1, the network architecture may include terminal devices, relay devices, network devices, and core network elements. Figure 1 only illustrates the case of one terminal device, one relay device, and one network device. The link between the terminal device and the relay device is an access link, and the link between the relay device and the network device is a backhaul link. Both the access link and the backhaul link are wireless links. The relay device is used to provide wireless access services to the terminal device and connects to the network device through the wireless backhaul link to transmit user service data. The network device is used to connect to the core network elements through a wired link.

[0080] Terminal equipment, also known as user equipment (UE), mobile station, mobile station (MS), mobile terminal (MT), etc., refers to devices that provide voice and / or data connectivity to users. Terminal devices can include mobile phones, handheld terminals, customer premises equipment (CPE), laptops, subscriber units, cellular phones, smartphones, computing devices, wireless data cards, personal digital assistant (PDA) computers, tablet computers, computers with wireless transceiver capabilities, wireless modems, tactile terminal devices, handheld devices, laptop computers, session initiation protocol (SIP) phones, cordless phones, wireless local loop (WLL) stations, machine-type communication (MTC) terminals, wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), vehicle-mounted terminal devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), extended reality (XR) terminal devices, virtual reality (VR) terminal devices, and augmented reality (AR) terminal devices. Wireless terminals in real-time (AR) devices, industrial control devices, smart home devices (such as refrigerators, televisions, air conditioners, and electricity meters), smart robots, workshop equipment, self-driving devices, remote medical surgery devices, wireless data cards, smart grid devices, transportation safety devices, smart city devices, smart home devices, flying devices (such as smart robots, hot air balloons, drones, and airplanes), or other devices that can access the network.

[0081] Furthermore, terminal devices can also be terminal devices in future communication systems (such as 6th generation (6G) communication systems) or terminal devices in future evolved public land mobile networks (PLMNs). For example, 6G networks can further expand the form and function of 5G communication terminal devices; 6G terminal devices include, but are not limited to, vehicles, cellular network terminal devices (integrating satellite terminal functions), drones, and the Internet of Things (IoT).

[0082] Relay equipment provides wireless access services to terminal devices. The service data of the terminal devices is transmitted to network equipment via a wireless backhaul link from the relay equipment. Relay equipment can also be called mobile relay (MR) equipment, such as vehicle-mounted mobile relays or satellite relays. Relay equipment can be fixed or mobile. Fixed relay equipment has a fixed location, while the location of mobile relay equipment can change over time. Network equipment can include access network elements with separate centralized units (CUs) and distributed units (DUs). Network equipment can include evolved NodeBs (eNBs or eNodeBs) in Long Term Evolution (LTE). Access network equipment can also include next-generation NodeBs (gNBs) or transmitting and receiving points (TRPs) in 5G networks, or next-generation base stations in 6th generation (6G) mobile communication systems, and base stations in future mobile communication systems. Access network equipment can also include base stations evolved after the 3rd Generation Partnership Project (3GPP), or base stations in future PLMNs, broadband network gateways (BNGs), 3GPP aggregation switches or non-3GPP access equipment, access points (APs), transmitting points (TPs), mobile switching centers, etc. in wireless fidelity (WiFi) systems. It can also be equipment that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications. Network equipment can be macro base stations, micro base stations, or indoor stations.

[0083] Core network elements refer to devices in the core network (CN) that provide service support to terminal equipment. They are primarily responsible for registration, call setup, billing, mobility management, providing user connectivity, managing users, and carrying out service delivery, data processing, and routing. Core access network equipment can correspond to different devices in different communication systems. For example, in 4G communication systems, it may correspond to one or more of the following: Mobility Management Entity (MME), Serving Gateway (S-GW), etc. Similarly, in 5G communication systems, it may correspond to one or more of the following: Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), etc. In next-generation or future communication systems, these elements can provide service support to terminal equipment through one or more network elements, devices, or entities.

[0084] It should be noted that the network architecture shown in Figure 1 is not limited to the terminal devices, relay nodes, network devices and core network elements shown in the figure, but may also include other terminal devices, relay devices, network devices and core network elements not shown in the figure. These will not be listed here in this application.

[0085] For example, a network-controlled repeater (NCR) is a relay device used to amplify and forward signals when terminal devices access a base station. It consists of two parts: NCR-MT (Mobile Terminal) and NCR-FWD (Forwarding).

[0086] Figure 2 is a schematic diagram of a network architecture based on NCR provided in this application. As shown in Figure 2, the NCR-MT is connected to the base station gNB, for example, through the LTE air interface (User to Network Interface - Universal, Uu) interface, and receives control information from the base station gNB through the control link. The NCR-MT uses the control link C-link (control link) to control the NCR. For example, the NCR can receive control information (i.e., side control information) from the base station through the control link, the direction of the backhaul link, the backhaul beam, or the control link beam, and realize the switching on and off of the NCR and power control. The NCR-FWD supports transparent forwarding of data between the base station and the UE through the backhaul link and the access link.

[0087] NCRs can be deployed in non-terrestrial network systems such as satellite communication systems, high altitude platform station (HAPS) communications, and unmanned aerial vehicles (UAVs), including integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, mobile communication systems can be fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems), worldwide interoperability for microwave access (WiMAX) systems, fifth-generation (5G) systems (e.g., New Radio (NR) systems), sixth-generation (6G) systems, and future mobile communication systems.

[0088] Satellite communication systems include user equipment (UE) and network equipment. User equipment can also be referred to as user terminals, mobile stations, etc. Network equipment may include one or more satellites and ground station equipment; ground station equipment can also be referred to as core network equipment, which includes core network elements. Satellites can be low-earth orbit (LEO) satellites, non-geostationary earth orbit (NGEO) satellites, etc.

[0089] To facilitate understanding of the relevant content of the embodiments of this application, some terms and processes involved in the embodiments of this application will be explained below. This part is only for the purpose of understanding and should not be regarded as a disclosure or specific limitation of the technical solution of this application.

[0090] 1. Gaze (earth-fixed or quasi-earth fixed) and non-gaze

[0091] In satellite communication systems, based on the operating mode of the payload (such as the beam), they can be divided into staring (earth-fixed or quasi-earth-fixed) and non-staring (earth-moving) satellite communication systems. In non-staring satellite communication systems, the satellite beam coverage area moves with the satellite during a specific time period. In staring satellite communication systems, the satellite dynamically adjusts the beam direction to make the beam approximately cover the same area on the ground during a specific time period.

[0092] In non-staring LEO satellite communication systems, the movement of satellite nodes can cause group handover (connected UEs) or group reselection (idle UEs) issues for users in a certain area (which may contain one or more beams). Taking group handover as an example, a cluster of UEs in a single beam within a specific area is served by one or more beams of a first satellite in the first time frame; in the second time frame, the movement of the first satellite causes that beam to become unserviceable, and the service of that UE cluster is taken over by one or more beams of a second satellite, i.e., group handover has occurred for that UE cluster.

[0093] 2. Mobility Management

[0094] Mobility management mainly includes cell handover, cell reselection, registration update, and tracking area update. Taking cell handover as an example, the existing handover process mainly includes the following steps:

[0095] 1) Cell handover measurement: The network sends measurement configurations for multiple cells (including serving cell and neighboring cells) to the UE. The UE measures the cell signal quality (such as Reference Signal Receiving Power (RSRP) and / or Reference Signal Receiving Quality (RSRQ)) according to the measurement configuration. For example, the measurement signal can be the synchronization signal and PBCH block (SSB) signal or CSI-RS (Channel State Information Reference Signal) signal.

[0096] 2) Measurement result reporting: The UE reports the measurement results to the network. The reporting method can be periodic reporting or event-triggered reporting. In event-triggered reporting, the reporting conditions are usually configured as serving cell signal quality being less than threshold 1 and / or neighboring cell signal quality being greater than threshold 2.

[0097] 3) Handover decision: The network selects a suitable neighboring cell based on the reported results and exchanges relevant context information, access control and reserved resources with the user.

[0098] 4) Handover execution: The UE receives handover-related control information from the serving cell and completes the access process in the new cell.

[0099] 3. Proximity effect

[0100] Since the distance between users and base stations varies randomly, if each user transmits with the same power, the signal strength reaching the base station will be different. The signal is stronger when the user is closer to the base station and weaker when the user is farther away. This aggravates the nonlinearity of the communication system, and this phenomenon is usually called the near-far effect.

[0101] However, existing communication protocols only support static NCR nodes and do not support the mobility of NCR nodes. In scenarios with mobile NCR nodes, group handover based on network mobility becomes the norm. Since the existing mobility management process is complex and NCR node handover usually does not involve the data plane, it is a special type of handover. If the existing process is reused, the signaling overhead will be large and the communication mobility interruption time will be prolonged.

[0102] To improve communication efficiency based on NCR network architecture in mobile scenarios and support the continuity of NCR node services during node switching, at least one embodiment of this application provides a network device switching method.

[0103] Figure 3 shows a schematic flowchart of a network device handover method provided in at least one embodiment of this application, applied to the relay node side. As shown in Figure 3, the method includes steps S301-S303:

[0104] Step S301: Receive relay information from core network elements, wherein the relay information includes network device switching conditions and the identifier of the relay node.

[0105] For example, the relay node side may include the relay equipment as described above, or the chips, chip systems, circuits, modules, units, etc. in the relay equipment that provide wireless access services. The core network element may be an AMF, or other network elements that can realize registration management, security, access management, or service authorization related functions. The identifier of the relay node may be a Radio Network Temporary Identifier (NCR-RNTI) or the identifier of the relay node related equipment, such as a satellite identifier (satellite-ID, SAT-ID).

[0106] In one possible implementation, before receiving relay information from a core network element, the relay node may also send a target access request to the core network element. The relay information may be generated by the core network element based on the target access request. For example, the relay node may send the target access request to the core network element through a first network device. For example, the relay node may send an initial access request to the first network device, and then the first network device may send access information of the terminal device to the core network element. The access information of the terminal device includes the initial access request. The relay node may receive the relay information from the core network element through the first network device.

[0107] For example, the target access request may include no session indication information, such as no protocol data unit session indication (NO Protocol Data Unit Session Indication, NO PDUSession Indication), or other information that can be used to indicate that the relay node does not generate user data. By reducing session indications, the handover process is simplified, and data transmission latency is reduced to enhance the service continuity of the relay node.

[0108] For example, after receiving relay information from the core network element, the relay node can also send a configuration response to the first network device. For instance, after the core network element sends the relay information to the first network device, the first network device puts the relay information into Radio Resource Control (RRC) reconfiguration information and then sends the RRC reconfiguration information to the relay node. In response to receiving the RRC reconfiguration information, the relay node notifies the first network device by sending a reconfiguration response.

[0109] In one possible implementation, the network device handover conditions include at least one of the following: the relay node's clock is at a first time node; the distance between the relay node's location and a preset reference location meets a first threshold; the signal quality between the relay node and the first network device is less than a second threshold and / or the signal quality between the relay node and the second network device is greater than a third threshold. For example, the first network device is the base station corresponding to the cell where the terminal device currently resides, served by the relay node, and the second network device may be, for example, a base station corresponding to a neighboring cell of the cell where the terminal device currently resides.

[0110] Understandably, due to the lack of a significant near-far effect in NTN (i.e., the signal quality difference between the cell center and edge is not significant), cell handover or reselection based on signal quality is inefficient. Therefore, this application considers location-assisted handover and reselection enhancement technologies. These technologies can be implemented in various ways, including based on time or timers, UE location information (such as the UE's reference location distance to the cell corresponding to the first network device being greater than a first threshold, and its reference location distance to the cell corresponding to the second network device being less than a second threshold), and combinations of timers and signal quality, as well as combinations of location information and signal quality. This improves the accuracy of judging relevant criteria in the cell handover or reselection process, thereby enhancing the communication efficiency of cell handover or reselection. Furthermore, relay nodes can select thresholds and / or limits in network handover conditions based on the actual connection status between the relay node and network devices, improving the flexibility of network control.

[0111] Step S302: Switch from the first network device to the second network device according to the network device switching conditions.

[0112] For example, when a relay node meets one or more of the network device switching conditions described above, the communication efficiency between the relay node and the first network device is lower than the communication efficiency between the relay node and the second network device. Therefore, the relay node switches from being connected to the first network device to being connected to the second network device.

[0113] Step S303: Receive a handover response from the second network device, wherein the handover response is sent by the second network device after authenticating the identifier of the relay node based on the authentication result.

[0114] For example, after receiving the initial access request from the relay node, the core network element can configure the relay node's identifier, such as NCR-RNTI or SAT-ID, in the second network device before the relay node's network device handover conditions take effect, and can also establish an NG connection between the core network and the second network device in advance. After receiving the handover response sent by the second network device after authenticating the relay node's identifier, the relay node can either complete the data transmission between the terminal device and the second network device based on the handover response, or reject the data transmission between the terminal device and the second network device based on the handover response.

[0115] In one possible implementation, when a relay node switches from the first network device to the second network device, the second network device can authenticate the relay node's identifier. If authentication fails, the second network device can send a handover response indicating authentication failure (e.g., a negative acknowledgement (NACK) message) to the relay node. Upon receiving the handover response indicating authentication failure, the relay node will refuse to transmit data uploaded by the terminal device to the second network device. If authentication succeeds, the second network device can send a handover response indicating authentication success to the relay node. Upon receiving the response indicating authentication success, the relay node will allow data uploaded by the terminal device to be transmitted to the second network device.

[0116] In one possible implementation, the handover response includes control signaling. Data transmission between the terminal device and the second network device is completed based on the handover response, including: completing data transmission between the terminal device and the second network device based on the control signaling. For example, the control signaling may be border control information as described above.

[0117] The following description uses an NCR node as a relay node, a base station as the first network device and a second network device, and an AMF as a core network element to illustrate the process of an NCR node switching from the first network device to the second network device. Figure 4 is a schematic diagram of an NCR node switching process provided by at least one embodiment of this application. For ease of description, the first network device is referred to as the source base station and the second network device as the target base station. As shown in Figure 4, the switching process includes all or part of steps S401-S409:

[0118] S401: The NCR node initiates an initial access request to the source base station. The access request information may carry the capability indication of the NCR node. The capability indication information includes NO PDU Session Indication information, which is used to indicate that the NCR node itself does not generate user data.

[0119] S402: The source base station sends a UE initial access message to the core network element AMF. The UE initial access message includes an initial access request or includes the contents of the initial access request.

[0120] S403: The AMF sends the NCR authentication information, the unique identifier (NCR-RNTI or SAT-ID) within the current AMF registration area, and the handover conditions for the NCR within a subsequent period to the source base station. These handover conditions include one or more of the following: S403-1-S403-3

[0121] S403-1: When the NCR node's own clock is located at [t1,t2];

[0122] S403-2: The distance between the NCR position and the reference position is greater than the first threshold; or the distance between the NCR position and the first reference position is greater than the first threshold, and the distance between the NCR position and the second reference position is less than the second threshold;

[0123] S403-3: The signal quality between the NCR and the source base station is less than the third threshold and / or the signal quality between the NCR and the target base station is greater than the fourth threshold;

[0124] S404: Before the NCR handover conditions take effect, the AMF configures the target base station with the dedicated identifier (NCR-RNTI or SAT-ID) corresponding to the NCR in advance, and establishes an NG connection with the target base station in advance;

[0125] S405: The source base station sends an RRC reconfiguration message to the NCR node. The reconfiguration message contains the handover conditions of the NCR node.

[0126] S406: The NCR node returns an RRC reconfiguration response to the source base station;

[0127] S407: When the handover conditions are met (the NCR performs a handover evaluation (HO (Handover) Evaluation)), the NCR switches to the target base station or the cell corresponding to the target base station;

[0128] S408: The target base station authenticates the NCR-MT based on the dedicated identifier issued by the AMF (NCRAuthorization). If the authentication is successful, it returns a handover response to the NCR and sends control signaling (side control information) under the new gNB. If the authentication fails, it returns a NACK (failure response) message to the NCR.

[0129] S409: The target base station returns an NG establishment completion response to the core network. The response message contains NCR-RNTI or SAT-ID.

[0130] It should be noted that steps S401-S409 are an exemplary network device switching process, and the specific names of the devices, nodes, etc. involved are also exemplary. In the actual network device switching process, the steps performed may include all or part of the above steps S401-S409.

[0131] In this embodiment, by authenticating the relay node identifier and completing the connection switching between the relay node and different network devices based on the authentication result, data transmission and signaling overhead are reduced. In addition, by adding NO PDU Session Indication information, additional session indication information is avoided, simplifying the NCR node switching process.

[0132] In satellite communication scenarios, a relay node NCR can include two parts, NCR-MT and NCR-FWD, as mentioned above. The two parts perform different functions. For example, NCR-FWD can perform data pass-through function, while NCR-MT can control whether NCR-FWD performs data pass-through by transmitting a handover response control signal from a second network device.

[0133] In one possible implementation, the relay node includes a first relay sub-node and a second relay sub-node.

[0134] For example, the first relay sub-node could be NCR-MT, and the second relay sub-node could be NCR-FWD.

[0135] In one possible implementation, the target access request includes node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with multiple network devices.

[0136] For example, node capability information can be reported through signaling related to the initial access process, such as Message (MSG)3, MSG5, or RRC reconfiguration information.

[0137] For example, the first relay sub-node configures the second relay sub-node to either the first handover mode or the second handover mode based on the node capability information.

[0138] When the second relay sub-node is in the first handover mode, the first relay sub-node supports connecting to multiple network devices simultaneously (such as the first network device and the second network device). When the second relay sub-node is in the second handover mode, the first relay sub-node does not support connecting to multiple network devices simultaneously. At the same time, the relay sub-node can only connect to one network device (such as the first network device or the second network device).

[0139] In response to the second relay sub-node being in the first handover mode, control signaling corresponding to the second network device is activated; and / or

[0140] In response to the second relay sub-node being in the second handover mode, after communication with the first network device is interrupted, the control signaling corresponding to the second network device takes effect.

[0141] Because the NCR-MT in the relay nodes on different satellites supports different connection modes with network devices, some satellites' NCR-MTs support SoftHO (soft handover), meaning that the NCR-MT can simultaneously establish communication connections with the first network device and the second network device; while some satellites' NCR-MTs only support HardHO (hard handover), meaning that the NCR-MT does not support simultaneously establishing communication connections with the first network device and the second network device.

[0142] Before an NCR node switches from the first base station to the second base station according to the network device switching conditions, the NCR-MT configures the NCR-FWD switching mode based on whether it supports SoftHO (node ​​capability information). When the NCR-MT supports SoftHO, the NCR-FWD is configured as the first switching mode; when the NCR-MT does not support SoftHO, the NCR-FWD is configured as the second switching mode.

[0143] Figure 5A is a schematic diagram of data transmission during NCR soft handover according to at least one embodiment of this application, and Figure 5B is a schematic diagram of data transmission during NCR hard handover according to at least one embodiment of this application. As shown in Figure 5A, in the first handover mode, when the NCR switches from the first network device to the second network device, the NCR-MT can simultaneously connect to the control links of the first network device and the second network device, and can directly take effect the configuration corresponding to the control signaling sent by the second network device, thereby completing the data transmission between the terminal device (UE-1 and UE-2 in the figure) and the network device through the backhaul link and the access link. As shown in Figure 5B, in the second handover mode, when the NCR switches from the first network device to the second network device, it is necessary to first disconnect the connection with the first network device (red cross in the figure), and then activate the control link between the second network device as needed. Before activating the connection between the NCR-MT and the second network device, the data transmission of the terminal device may be interrupted. The embodiments of this application can reduce the latency of mobile interruption by adapting the capabilities of the NCR node.

[0144] Because NCR-MT has certain data processing capabilities, it can dynamically configure the working mode of NCR for different types of services. Figure 6A is a schematic diagram of NCR node data transmission shown in at least one embodiment of this application, and Figure 6B is a schematic diagram of NCR node data transmission shown in at least one embodiment of this application. The following description, in conjunction with Figures 6A and 6B, explains how the embodiments of this application can dynamically configure different types of services.

[0145] In one possible implementation, the network device switching method further includes: receiving a service request from a terminal device; in response to the service request being a first type of service, performing store-and-forward of the service data corresponding to the service request through a first relay sub-node; and / or in response to the service request being a second type of service, performing transparent forwarding of the service data corresponding to the service request through a second relay sub-node.

[0146] For example, the first type of service is a latency-insensitive service, such as a non-real-time IoT service. As shown in Figure 6A, the terminal device uploads data packets to the NCR-MT through the access link. The NCR-MT stores the data packets and then forwards them to the network device through the control link. The data packets can be generated by the terminal packaging local data. At this time, the service data is stored and forwarded (Store-and-forward, SF) through the NCR-MT.

[0147] For example, the second type of service is a latency-sensitive service with high requirements for data transmission latency, such as the eMBB (enhanced mobile broadband) service. As shown in Figure 6B, the terminal devices (UE-1 and UE-2 in the figure) upload real-time data to the NCR-MT through the access link. The NCR-FWD then transmits the data packet transparently and forwards it to the network device through the control link. At this time, the service data is amplified and forwarded (AF) through the NCR-FWD.

[0148] For example, when NCR determines whether a service type is a Type 1 or Type 2 service, it can do so by checking the type of the terminal device sending the data. For instance, data sent by a non-real-time IoT device is latency-insensitive data, which corresponds to a Type 1 service. Alternatively, it can determine the type by checking the network slice ID contained in the service data. Different slices (i.e., AF slices or SF slices) are used in different times, frequencies, spaces, and polarization domains (corresponding to at least one of linear polarization, circular polarization, elliptic polarization, etc.) to improve support for different service types through different NCR modes.

[0149] In communication systems, different network devices correspond to two types of cells: quasi-static (e.g., TN (Terrestrial Network) cell) and dynamic (e.g., NTNNCR cell). The beam change frequencies of the two types of cells are different. Using the same neighbor cell management method will lead to increased signaling overhead. The following explains how this application configures neighbor cell relationships for the two different types of cells.

[0150] In one possible implementation, the network device handover method further includes: updating the configuration information of the first network device according to the type of the cell corresponding to the first network device; or updating the configuration information of the second network device according to the type of the cell corresponding to the second network device.

[0151] For example, the cell types corresponding to the first network device and the second network device can be quasi-static (terrestrial network) or dynamic (non-terrestrial network) as mentioned above. Selecting different neighbor cell configuration update methods according to different cell types can reduce the neighbor cell update frequency and adapt to different types of neighbor cells.

[0152] In one possible implementation, the cell type is either a non-terrestrial network cell or a terrestrial network cell;

[0153] Based on the type of the cell corresponding to the first network device, update the configuration information of the first network device, including:

[0154] In response to a terrestrial network cell, the configuration information of the first network device is updated based on the event trigger.

[0155] In response to a cell type that is a non-terrestrial network cell, the configuration information of the first network device is updated according to a preset period and / or the activation status of neighboring cells;

[0156] Based on the type of the cell corresponding to the second network device, update the configuration information of the second network device, including:

[0157] In response to a terrestrial network cell, the configuration information of the second network device is updated based on the event trigger.

[0158] In response to a cell type that is a non-terrestrial network cell, the configuration information of the second network device is updated according to a preset period and / or the activation status of neighboring cells.

[0159] For example, the beams corresponding to cells in terrestrial networks are relatively stable, and the neighbor cell relationship configuration can be updated using an event-triggered method to reduce the update frequency. The beams corresponding to cells in non-terrestrial networks change frequently due to the high-speed movement of satellites, and the neighbor cell relationship configuration can be updated periodically or by designing an active state to adapt to the constantly changing beams.

[0160] The neighbor relationships of different community types can be shown in the table below:

[0161] In this context, Type1 represents cells in the terrestrial network, Type2 represents cells in the non-terrestrial network, the neighbor cell identifier is the identification information of the corresponding cell, NA in the neighbor cell status and neighbor cell validity period indicates that no configuration has been made, T1 represents the first time node, and T2 represents the second time node. For example, for non-terrestrial network cells, the neighbor cell status or validity period can be configured and activated by time or location from a given configuration set.

[0162] For example, during network device handover, the selectable network device can be chosen based on the status of neighboring cells. For instance, if Cell-N2 is active, the relay node can handover to the network device corresponding to Cell-N2; if Cell-N1 is inactive, the relay node cannot handover to the network device corresponding to Cell-N1. Furthermore, the handover time can be selected based on the neighboring cell's validity period, for example, completing the handover between time period T1 and T2. In addition to network device handover, cell reselection can also be performed based on the neighboring cell's status and validity period. Different cells can exchange information related to the neighboring cell's status and validity period.

[0163] In one possible implementation, the network device switching method further includes:

[0164] In response to updating the configuration information of the first network device according to a preset period and / or the activation status of neighboring cells, the update of the System Information Block (SIB) is not triggered; or

[0165] In response to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered.

[0166] For example, the two types of neighbor relationship configuration update information can be carried in different SIB messages, and changes in the neighbor relationship configuration of cells in non-terrestrial networks can not trigger changes in SIB1, thereby reducing the frequency of changes in SIB1 messages.

[0167] Figure 7 is a schematic flowchart of another network device switching method provided in at least one embodiment of this application, applied to the second network device side. As shown in Figure 7, the method includes steps S701-S703:

[0168] S701: Identifier of the relay node receiving data from the core network element;

[0169] S702: Authenticate the identifier of the relay node;

[0170] S703: Send a handover response to the relay node based on the authentication result.

[0171] For example, after receiving the initial access request sent by the relay node, the core network element can configure the relay node's identifier, such as NCR-RNTI or SAT-ID, in advance to the second network device before the network device switching conditions of the relay node take effect, and can also establish an NG connection between the core network and the second network device in advance.

[0172] For example, the second network device can determine whether the NCR-RNTI or SAT-ID is an authorized identifier. If so, it will pass the authentication. The second network device can also authenticate the identifier of the relay node in other ways, and this application does not restrict this.

[0173] After sending a handover response to the relay node based on the authentication result, the relay node completes the data transmission between the terminal device and the network device based on the handover response sent by the second network device.

[0174] In this embodiment, by authenticating the relay node identifier and completing the connection switching between the relay node and different network devices based on the authentication result, additional session indication information is avoided, and data transmission and signaling overhead are reduced.

[0175] In one possible implementation, after sending a handover response to the relay node based on the authentication result, the network device handover method further includes:

[0176] Send a connection establishment response to the core network element, wherein the connection establishment response includes the identifier of the relay node.

[0177] For example, after authenticating the relay node, the second network device can report to the core network and return a response indicating that the NG connection has been established.

[0178] In one possible implementation, the relay information also includes local network device authentication information;

[0179] The network device switching method also includes:

[0180] In response to the fact that the second network device does not exist in the local network device authentication information, a context update request is sent to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node;

[0181] Receive updated local network device authentication information and / or relay node identifiers sent by core network elements.

[0182] For example, the local network device authentication information may include a list of network devices, such as a network device list containing information about network device-1, network device-2, ..., network device-N. Network devices in this list have local authentication capabilities. When a relay node determines that a second network device is in the list, it can directly establish a connection with the second network device and receive a handover response from it. It should be noted that the local network device authentication information can also be in forms other than a list, such as data packets or real-time data streams; this application does not impose any restrictions on this.

[0183] In one possible implementation, before sending a context update request to the core network element, the network device handover method further includes:

[0184] Receive a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has local network device authentication information.

[0185] For example, when a relay node determines that the second network device is not in the local network device authentication information, it sends information to the second network device to notify the second network device to send a UE context update request to the core network. The core network then returns new local network device authentication information and the relay identifier to the second network device and / or the relay node. Through the local authentication function, the second base station initiates the authentication area update process to achieve mobility support for the NCR node.

[0186] It should be noted that the above embodiments can be combined to implement the combined solution. Optionally, some operations in the process of each method embodiment can be arbitrarily combined, and / or the order of some operations can be arbitrarily changed. Furthermore, the execution order between the steps of each process is merely exemplary and does not constitute a limitation on the execution order between steps; other execution orders are also possible. It is not intended to indicate that the execution order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. In addition, it should be pointed out that the process details involved in one embodiment of this document are also applicable to other embodiments in a similar manner, or different embodiments can be combined.

[0187] Figure 8 is a schematic diagram of a communication system structure provided in at least one embodiment of this application. As shown in Figure 8, the communication system 30 includes a relay node 31 and a second network device 32. The relay node 31 is configured to perform the relay node side function in any of the network device switching methods described above.

[0188] The second network device 32 is configured to perform the second network device side function in any of the network device switching methods described above.

[0189] Figure 9 is a schematic diagram of a communication device structure provided in at least one embodiment of this application. As shown in Figure 9, the communication device can be used to implement any possible function in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0190] As shown in Figure 9, the communication device 900 includes a processing unit 910.

[0191] In one possible implementation, the communication device 900 may also include a transceiver unit 920.

[0192] In one possible implementation, the communication device 900 may also include a storage unit 930.

[0193] In one possible implementation, the communication device 900 may further include a transceiver unit 920 and a storage unit 930.

[0194] In the embodiments of this application, the communication device 900 may be the relay node 31 shown in FIG8, or it may be a module (such as a chip) applied to the relay node 31. Alternatively, the communication device 900 may be the second network device 32 shown in FIG8, or it may be a module (such as a chip) applied to the second network device 32.

[0195] When the communication device 900 is used to implement the relay node side functions as described above, the transceiver unit 920 is used to receive relay information from core network elements, wherein the relay information includes network device switching conditions and the identifier of the relay node; the processing unit 910 is used to switch from the first network device to the second network device according to the network device switching conditions; the transceiver unit 920 is also used to receive control signaling switching response from the second network device, wherein the control signaling switching response is sent by the second network device after authenticating the identifier according to the authentication result.

[0196] In one possible implementation, network device switching conditions include at least one of the following conditions:

[0197] The relay node's clock is at the first time node;

[0198] The distance between the location of the relay node and the preset reference location meets the first threshold.

[0199] The signal quality between the relay node and the first network device is less than the second threshold and / or the signal quality between the relay node and the second network device is greater than the third threshold.

[0200] In one possible implementation, the transceiver unit 920 is also used for the first network device to send a configuration response.

[0201] In one possible implementation, the processing unit 910 is further configured to complete data transmission between the terminal device and the second network device based on the handover response; or,

[0202] The handover response rejects data transmission between the terminal device and the second network device.

[0203] In one possible implementation, the handover response includes control signaling;

[0204] Data transmission between the terminal device and the second network device is completed based on the handover response, including:

[0205] Data transmission between the terminal device and the second network device is completed according to control signaling.

[0206] In one possible implementation, the relay node includes a first relay sub-node and a second relay sub-node.

[0207] In one possible implementation, the transceiver unit 920 is further configured to:

[0208] Receive service requests from terminal devices;

[0209] In response to a business request being classified as a first type of business, the business data corresponding to the business request is stored and forwarded through the first relay sub-node; and / or

[0210] In response to a business request being classified as a second type of business, the business data corresponding to the business request is transparently forwarded through the second relay sub-node.

[0211] In one possible implementation, the relay information is generated by the core network element based on the target access request;

[0212] The transceiver unit 920 is also used for:

[0213] Send a target access request to the core network element.

[0214] In one possible implementation, the transceiver unit 920 is specifically used for:

[0215] The first network device sends a target access request to the core network element.

[0216] Relay information received from core network elements includes:

[0217] The first network device receives relay information from core network elements.

[0218] In one possible implementation, the target access request includes node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with both the first network device and the second network device.

[0219] In one possible implementation, the processing unit 910 is further configured to:

[0220] Update the configuration information of the first network device according to the type of the cell corresponding to the first network device; or,

[0221] The configuration information of the second network device is updated according to the type of the cell to which the second network device corresponds.

[0222] In one possible implementation, the cell type is either a non-terrestrial network cell or a terrestrial network cell;

[0223] The processing unit 910 is also used for:

[0224] In response to a terrestrial network cell, the configuration information of the first network device is updated based on the event trigger.

[0225] In response to a cell type that is a non-terrestrial network cell, the configuration information of the first network device is updated according to a preset period and / or the activation status of neighboring cells;

[0226] In response to a terrestrial network cell, the configuration information of the second network device is updated based on the event trigger.

[0227] In response to a cell type that is a non-terrestrial network cell, the configuration information of the second network device is updated according to a preset period and / or the activation status of neighboring cells.

[0228] In one possible implementation, the processing unit 910 is further configured to:

[0229] In response to updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered; or

[0230] In response to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered.

[0231] When the communication device 900 is used to implement the functions of the second network device side as described above, the transceiver unit 920 is used to receive the identifier of the relay node sent by the core network element; the processing unit 910 is used to authenticate the identifier; the transceiver unit 920 is also used to send a handover response to the relay node according to the authentication result.

[0232] In one possible implementation, the transceiver unit 920 is further configured to:

[0233] Send a connection establishment response to the core network element, wherein the connection establishment response includes the identifier of the relay node.

[0234] In one possible implementation, the relay information also includes local network device authentication information;

[0235] The transceiver unit 920 is also used for:

[0236] In response to the fact that the second network device does not exist in the local network device authentication information, a context update request is sent to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node;

[0237] Receive updated local network device authentication information and / or relay node identifiers sent by core network elements.

[0238] In one possible implementation, the transceiver unit 920 is further configured to:

[0239] Receive a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has local network device authentication information.

[0240] Storage unit 930 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application. For example, storage unit 930 is used to store data packets from a terminal device. A more detailed description of the processing unit 910 and transceiver unit 920 can be found in the relevant description in the method embodiment shown in FIG4. The processing unit 910 and transceiver unit 920 may also perform other steps, the specific implementation of which can be found in the method embodiment and will not be repeated here.

[0241] Optionally, the transceiver unit 920 can be a transceiver, which may include an antenna and radio frequency circuitry, etc.

[0242] The processing unit 910 may be a processor (or processing circuitry), such as a baseband processor, which may include one or more CPUs.

[0243] Figure 10 is a schematic diagram of a communication device provided in this application. This communication device can be used to implement any possible function in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.

[0244] As shown in Figure 10, the communication device 1000 includes at least one processor 1010. In one possible implementation, the communication device 1000 may further include an interface circuit 1020.

[0245] In one possible implementation, the communication device 1000 may also include a memory 1030.

[0246] In one possible implementation, the communication device 1000 may further include a memory 1030 and an interface circuit 1020.

[0247] In some embodiments, the processor 1010 and the memory 1030 are coupled to each other; and / or, the processor 1010 and the interface circuit 1020 are coupled to each other. It is understood that the interface circuit 1020 can be a transceiver or an input / output interface. The memory 1030 can be used to store computer instructions executed by the processor 1010, or to store input data required by the processor 1010 to execute computer instructions, or to store data generated by the processor 1010 after executing computer instructions.

[0248] When the communication device 1000 is used to implement the method shown in FIG3, the processor 1010 is used to implement the functions of the processing unit 1010, and the interface circuit is used to implement the functions of the transceiver unit 1020.

[0249] The communication device shown in Figures 9 and 10 is merely an example. In practical applications, the communication device may have more or fewer components than those shown in Figures 9 and 10, may combine two or more components, or may have different component configurations. In Figures 9 and 10, the processing unit may also be called a processing unit or processor; the transceiver unit may also be called a transceiver unit or transceiver; and the storage unit may also be called a storage module or memory. It should be understood that the division of units in the above device is merely a logical functional division. 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. In addition, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or may be electrical, mechanical, or other forms of connection. 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. The technical effects of the solutions provided in the embodiments of this application can be achieved by selecting some or all of the units according to actual needs.

[0250] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0251] The method steps in this application embodiment can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a network device or terminal. The processor and storage medium can also exist as discrete components in a network device or terminal.

[0252] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0253] In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0254] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0255] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0256] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A network device switching method, applied to the relay node side, comprising: Receive relay information from core network elements, wherein the relay information includes network device switching conditions and the identifier of the relay node; Switch from the first network device to the second network device according to the network device switching conditions; Receive a handover response from a second network device, wherein the handover response is sent by the second network device after authenticating the identifier, based on the authentication result.

2. The method according to claim 1, wherein, The network device switching conditions include at least one of the following: The clock of the relay node is at the first time node; The distance between the location of the relay node and the preset reference location satisfies a first threshold. The signal quality between the relay node and the first network device is less than a second threshold and / or the signal quality between the relay node and the second network device is greater than a third threshold.

3. The method according to claim 1, wherein, After receiving relay information from the core network element, the method further includes: Send a configuration response to the first network device.

4. The network device switching method according to claim 1, wherein, After receiving the handover response sent by the second network device after authenticating the identifier, the method further includes: Data transmission between the terminal device and the second network device is completed based on the handover response; or... The handover response rejects data transmission between the terminal device and the second network device.

5. The network device switching method according to claim 4, wherein, The handover response includes control signaling; The step of completing data transmission between the terminal device and the second network device based on the handover response includes: Data transmission between the terminal device and the second network device is completed according to the control signaling.

6. The method according to claim 1, wherein, The relay node includes a first relay sub-node and a second relay sub-node.

7. The method according to claim 6, wherein, The method further includes: Receive service requests from terminal devices; In response to the service request being a first type of service, the service data corresponding to the service request is stored and forwarded through the first relay sub-node; and / or In response to the service request being a second type of service, the service data corresponding to the service request is transparently forwarded through the second relay sub-node.

8. The method according to claim 1, wherein, The relay information is generated by the core network element based on the target access request; Before receiving relay information from core network elements, the method further includes: The target access request is sent to the core network element.

9. The method according to claim 8, wherein, Sending the target access request to the core network element includes: The first network device sends the target access request to the core network element; The receipt of relay information from core network elements includes: The first network device receives relay information sent by the core network element.

10. The method according to claim 8, wherein, The target access request includes the node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with multiple network devices.

11. The method according to claim 1, wherein, The method further includes: Based on the type of the cell corresponding to the first network device, update the configuration information of the first network device; or The configuration information of the second network device is updated according to the type of the cell corresponding to the second network device.

12. The method according to claim 11, wherein, The cell type is either a non-terrestrial network cell or a terrestrial network cell; The step of updating the configuration information of the first network device according to the type of the cell corresponding to the first network device includes: In response to the cell type being a terrestrial network cell, the configuration information of the first network device is updated based on the event trigger; In response to the cell type being a non-terrestrial network cell, the configuration information of the first network device is updated according to a preset period and / or the neighboring cell activation status; The step of updating the configuration information of the second network device according to the type of the cell corresponding to the second network device includes: In response to the cell type being a terrestrial network cell, the configuration information of the second network device is updated based on the event trigger; In response to the cell type being a non-terrestrial network cell, the configuration information of the second network device is updated according to a preset period and / or the neighboring cell activation status.

13. The method according to claim 12, wherein, The method further includes: In response to updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered; or In response to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered.

14. The method according to claim 8, wherein, The target access request includes no session indication information.

15. A network device switching method, applied to a second network device side, comprising: The identifier of the relay node received from the core network element; Authenticate the identifier; A handover response is sent to the relay node based on the authentication result.

16. The method according to claim 15, wherein, After sending a handover response to the relay node based on the authentication result, the method further includes: A connection establishment response is sent to the core network element, wherein the connection establishment response includes the identifier of the relay node.

17. The method according to claim 15, wherein, The relay information also includes local network device authentication information; The method further includes: In response to the fact that the second network device does not exist in the local network device authentication information, a context update request is sent to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node; Receive updated local network device authentication information and / or the identifier of the relay node sent by the core network element.

18. The method according to claim 17, wherein, Before sending the context update request to the core network element, the method further includes: Receive a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has authentication information in the local network device.

19. A communication device, disposed on a relay node side, configured to perform the following steps: Receive relay information from core network elements, among which, The relay information includes network device switching conditions and the identifier of the relay node; Switch from the first network device to the second network device according to the network device switching conditions; Receive a control signaling handover response from a second network device, wherein the control signaling handover response is sent by the second network device after authenticating the identifier, based on the authentication result.

20. The apparatus according to claim 19, wherein, The network device switching conditions include at least one of the following conditions: The clock of the relay node is at the first time node; The distance between the location of the relay node and the preset reference location satisfies a first threshold. The signal quality between the relay node and the first network device is less than a second threshold and / or the signal quality between the relay node and the second network device is greater than a third threshold.

21. The apparatus according to claim 19, wherein, The device is further configured to send a configuration response to the first network device.

22. The apparatus according to claim 19, wherein, The device is further configured to complete data transmission between the terminal device and the second network device based on the handover response; or... The handover response rejects data transmission between the terminal device and the second network device.

23. The apparatus according to claim 22, wherein, The handover response includes control signaling; The step of completing data transmission between the terminal device and the second network device based on the handover response includes: Data transmission between the terminal device and the second network device is completed according to the control signaling.

24. The apparatus according to claim 19, wherein, The relay node includes a first relay sub-node and a second relay sub-node.

25. The apparatus according to claim 24, wherein, The device is further configured as follows: Receive service requests from terminal devices; In response to the service request being a first type of service, the service data corresponding to the service request is stored and forwarded through the first relay sub-node; and / or In response to the service request being a second type of service, the service data corresponding to the service request is transparently forwarded through the second relay sub-node.

26. The apparatus according to claim 19, wherein, The relay information is generated by the core network element based on the target access request; The device is further configured as follows: The target access request is sent to the core network element.

27. The apparatus according to claim 26, wherein, The device is further configured as follows: The first network device sends the target access request to the core network element; The receipt of relay information from core network elements includes: The first network device receives relay information sent by the core network element.

28. The apparatus according to claim 26, wherein, The target access request includes the node capability information of the relay node, wherein the node capability information is used to indicate whether the relay node supports simultaneous connection with multiple network devices.

29. The apparatus according to claim 19, wherein, The device is further configured as follows: Based on the type of the cell corresponding to the first network device, update the configuration information of the first network device; or The configuration information of the second network device is updated according to the type of the cell corresponding to the second network device.

30. The apparatus according to claim 29, wherein, The cell type is either a non-terrestrial network cell or a terrestrial network cell; The device is further configured as follows: In response to the cell type being a terrestrial network cell, the configuration information of the first network device is updated based on the event trigger; In response to the cell type being a non-terrestrial network cell, the configuration information of the first network device is updated according to a preset period and / or the neighboring cell activation status; In response to the cell type being a terrestrial network cell, the configuration information of the second network device is updated based on the event trigger; In response to the cell type being a non-terrestrial network cell, the configuration information of the second network device is updated according to a preset period and / or the neighboring cell activation status.

31. The apparatus according to claim 30, wherein, The device is further configured as follows: In response to updating the configuration information of the first network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered; or In response to updating the configuration information of the second network device according to a preset period and / or the neighbor cell activation status, the update of the System Information Block (SIB) is not triggered.

32. The apparatus according to claim 26, wherein, The target access request includes no session indication information.

33. A communication device, disposed on a second network device side, configured to perform the following steps: The identifier of the relay node received from the core network element; Authenticate the identifier; A handover response is sent to the relay node based on the authentication result.

34. The apparatus according to claim 33, wherein, The device is further configured as follows: A connection establishment response is sent to the core network element, wherein the connection establishment response includes the identifier of the relay node.

35. The apparatus according to claim 33, wherein, The relay information also includes local network device authentication information; The device is further configured as follows: In response to the fact that the second network device does not exist in the local network device authentication information, a context update request is sent to the core network element, wherein the context update request is configured to update the local network device authentication information and / or the identifier of the relay node; Receive updated local network device authentication information and / or the identifier of the relay node sent by the core network element.

36. The apparatus according to claim 35, wherein, The device is further configured as follows: Receive a local authentication result notification from the relay node side, wherein the local authentication result notification indicates whether the second network device has authentication information in the local network device.

37. A communication system, comprising: Relay nodes and second network devices; The relay node is configured to perform the network device switching method according to any one of claims 1 to 14; The second network device is configured to perform the network device switching method according to any one of claims 15 to 18.

38. A communication device, comprising: A memory and at least one processor, wherein the memory is configured to store computer instructions, and the processor is configured to execute the computer instructions to cause the communication device to perform the network device switching method as claimed in any one of claims 1 to 14 or the network device switching method as claimed in any one of claims 15 to 18.

39. A computer-readable storage medium, wherein, The computer-readable storage medium stores instructions or programs that, when executed on a communication device, cause the communication device to perform the network device switching method as described in any one of claims 1 to 14 or any one of claims 15 to 18.

40. A computer program product, wherein, The computer program product includes a computer program or instructions that, when executed on a computer, cause the computer to perform the network device switching method as described in any one of claims 1 to 14 or any one of claims 15 to 18.

Images