Capability synchronization method, system and related device

Abstract

The invention discloses a capability synchronization method, a capability synchronization system and a related device. The UE comprises an NTN communication module and a mobile communication module. And after the mobile communication module is registered to the TN-CN, the NTN communication module executes the registration process of the NTN-CN through the mobile communication module, the TN-RAN and the TN-CN. And the NTN-CN obtains the NTN air interface capability information of the UE of the NTN communication module through the TN-CN, the TN-RAN and the mobile communication module. Thus, since the NTN-CN obtains the NTN air interface capability information of the UE under the TN network, the NTN-CN does not need to obtain the NTN air interface capability information of the UE again under the NTN, the signaling overhead for transmitting the NTN air interface capability information of the UE between the UE and a core network of a non-ground network is reduced, the time required by the UE for transmitting the NTN air interface capability information of the UE under the NTN is saved, and the power consumption of the UE is saved.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a capability synchronization method, system and related devices. Background Art

[0002] Nowadays, some user equipment (UE) supports non-terrestrial network (NTN) communication function. With the development of communication technology, more and more UE will support NTN communication function in the future. UE with NTN communication function can communicate through satellite in areas such as ocean, desert, grassland, high altitude, uninhabited area, etc. where mobile communication is not covered, or cannot be covered, or the communication system is damaged.

[0003] During the communication between the UE and the non-terrestrial network equipment, the non-terrestrial network equipment needs to provide the UE with corresponding communication resources according to the NTN air interface capability information of the UE. Since the UE has a lot of NTN air interface capability information, when the UE sends the UE's NTN air interface capability information to the non-terrestrial network equipment, it needs to occupy more air interface resources, the transmission time is long, and the UE consumes a lot of power. Summary of the invention

[0004] The present application provides a capability synchronization method, system and related devices, and the UE includes an NTN communication module and a mobile communication module. The mobile communication module obtains the registration information of the NTN communication module. After the mobile communication module is registered with the core network of the ground network, the NTN communication module executes the registration process of the core network of the non-ground network through the mobile communication module and the core network of the ground network. The core network of the non-ground network obtains the NTN air interface capability information of the UE from the NTN communication module of the UE through the core network of the ground network. After searching for NTN-RAN, the NTN communication module of the UE accesses the core network of the non-ground network. The core network of the non-ground network obtains the NTN air interface capability information of the UE under the ground network, saving the air interface resources of the non-ground network, and also reducing the time for the UE and the core network of the non-ground network to transmit the NTN air interface capability information of the UE under the non-ground network.

[0005] In a first aspect, the present application provides a capability synchronization method, which is applied to a communication system, wherein the communication system includes a user equipment UE, a core network NTN-CN device of a non-terrestrial network, a radio access network device NTN-RAN of a non-terrestrial network, and a terrestrial network device; the method includes: the UE receives a first non-terrestrial network air interface capability request sent by the terrestrial network device, and sends a first non-terrestrial network air interface capability message to the terrestrial network device, wherein the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE;

[0006] The terrestrial network device sends a second non-terrestrial network air interface capability message to the NTN-CN device, where the second non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE;

[0007] The UE searches for the NTN, and sends a first mobility registration request message to the NTN-CN device through the NTN-RAN device, where the first mobility registration request message is used for the UE to register with the NTN-CN device;

[0008] After receiving the first mobility registration request message, the NTN-CN device sends the UE's NTN air interface capability information to the NTN-RAN device. In this way, the UE can send the NTN air interface capability information to the ground network device under the TN, and the NTN-CN device does not need to obtain the UE's NTN air interface capability information under the NTN, saving the NTN air interface resources.

[0009] In some examples, the UE searching for the NTN means that the UE receives a signal sent by the NTN-RAN.

[0010] In a possible implementation, before the UE receives the first non-terrestrial network air interface capability request, the method further includes: after the UE successfully registers with the NTN-CN device through the terrestrial network device, the NTN-CN device sends a second non-terrestrial network air interface capability request to the terrestrial network device, and the second non-terrestrial network air interface capability request is used by the NTN-CN device to obtain the NTN air interface capability information of the UE; after receiving the second non-terrestrial network air interface capability request, the terrestrial network device sends the first non-terrestrial network air interface capability request to the UE. In this way, after the UE successfully registers with the NTN-CN device through the terrestrial network device, the NTN-CN device can obtain the NTN air interface capability information of the UE through the terrestrial network device.

[0011] In a possible implementation, the ground network equipment includes a TN-RAN device of the ground network's wireless access network and a TN-CN device of the ground network's core network; after receiving the second non-ground network air interface capability request, the ground network equipment sends a first non-ground network air interface capability request to the UE, specifically including: the TN-CN device receives the second non-ground network air interface capability request and sends the first non-ground network air interface capability request to the TN-RAN device; the TN-RAN device receives the first non-ground network air interface capability request and sends the first non-ground network air interface capability request to the UE. In this way, after receiving the second non-ground network air interface capability request sent by the NTN-CN device, the TN-CN device can respond to the second non-ground network air interface capability request and send the first non-ground network air interface capability request to the UE.

[0012] In some examples, the second non-terrestrial network air interface capability request is N1 NTN Container (UECapability Enquiry) or N1NTN Container (UE Capability Info Request), and the first non-terrestrial network air interface capability request is a non-access layer NAS message or a radio resource control layer RRC message including the second non-terrestrial network air interface capability request.

[0013] In a possible implementation, the ground network device includes a TN-CN device and a TN-RAN device; after receiving the second non-ground network air interface capability request, the ground network device sends the first non-ground network air interface capability request to the UE, specifically including: the TN-CN device receives the second non-ground network air interface capability request, and sends the second non-ground network air interface capability request to the TN-RAN device; the TN-RAN device receives the second non-ground network air interface capability request, and sends the first non-ground network air interface capability request to the UE. In this way, after receiving the second non-ground network air interface capability request sent by the NTN-CN device through the TN-CN device, the TN-RAN device can respond to the second non-ground network air interface capability request and send the first non-ground network air interface capability request to the UE.

[0014] In a possible implementation, the ground network device includes a TN-RAN device; before the UE receives the first non-ground network air interface capability request, the method further includes: after the UE successfully registers with the NTN-CN device through the TN-RAN device, the NTN-CN device sends the first non-ground network air interface capability request to the TN-RAN device; after receiving the first non-ground network air interface capability request, the TN-RAN device sends the first non-ground network air interface capability request to the UE. In this way, the UE sends signaling to the NTN-CN device through the TN-RAN device, saving air interface resources of the NTN-RAN device.

[0015] In a possible implementation, the ground network device includes a TN-RAN device; before the UE receives the first non-ground network air interface capability request, the method further includes: after the UE successfully registers with the NTN-CN device through the TN-RAN device, the NTN-CN device sends a second non-ground network air interface capability request to the TN-RAN device, and the second non-ground network air interface capability request is used by the NTN-CN device to obtain the NTN air interface capability information of the UE; after receiving the second non-ground network air interface capability request, the TN-RAN device sends the first non-ground network air interface capability request to the UE. In this way, the UE sends signaling to the NTN-CN device through the TN-RAN device, saving the air interface resources of the NTN-RAN device.

[0016] In a possible implementation, the ground network device sends the second non-ground network air interface capability message to the NTN-CN device, specifically including: the TN-RAN device sends the second non-ground network air interface capability message to the NTN-CN device. In this way, the NTN-CN device obtains the NTN air interface capability information of the UE under the TN.

[0017] In a possible implementation, the UE includes a mobile communication module and an NTN communication module; the UE receives the first non-terrestrial network air interface capability request through the mobile communication module; the mobile communication module of the UE generates a first non-terrestrial network air interface capability message based on the NTN air interface capability information provided by the NTN communication module, and sends the first non-terrestrial network air interface capability message to the terrestrial network device.

[0018] In a possible implementation, the ground network device sends the second non-ground network air interface capability message to the NTN-CN device, specifically including: the ground network device responds to the first non-ground network air interface capability message and sends the second non-ground network air interface capability message to the NTN-CN device. In this way, after receiving the NTN air interface capability information, the ground network directly forwards the information to the NTN-CN device.

[0019] In a possible implementation manner, the first non-terrestrial network air interface capability message is a user equipment capability information UECapability Information message, and the second non-terrestrial network air interface capability message is a user equipment capability information indication UECapability Infor Indication message.

[0020] In a possible implementation, the UE includes a mobile communication module and an NTN communication module; the UE receives a first non-terrestrial network air interface capability request sent by a terrestrial network device, specifically including: the mobile communication module of the UE receives the first non-terrestrial network air interface capability request, and obtains the NTN air interface capability information of the UE from the NTN communication module; the mobile communication module of the UE generates a first non-terrestrial network air interface capability message based on the NTN air interface capability information; and the first non-terrestrial network air interface capability message is sent to the terrestrial network device, specifically including: the mobile communication module of the UE sends the first non-terrestrial network air interface capability message to the terrestrial network device. In this way, the UE can send the NTN air interface capability information to the terrestrial network device through the mobile communication module.

[0021] In a possible implementation, the ground network device sends a first non-ground network air interface capability request to the UE, specifically including: after the NTN air interface capability of the UE is changed, the UE sends a first capability change message to the NTN-CN device through the ground network device, and the first capability change message is used to indicate the change of the NTN air interface capability of the UE; the NTN-CN device responds to the first capability change message and sends the first non-ground network air interface capability request to the UE through the ground network device. In this way, the UE can trigger the TN-CN device to obtain the NTN air interface capability information.

[0022] In a possible implementation, the ground network device includes a TN-CN device; before the UE receives the first non-ground network air interface capability request, the method further includes: after the UE successfully registers with the TN-CN device through the ground network device, the ground network device sends the first non-ground network air interface capability request to the UE. In this way, the TN-CN device can obtain and store the NTN air interface capability information of the UE, and when the NTN-CN device needs to obtain the NTN air interface capability information of the UE, it can directly obtain it from the TN-CN device.

[0023] In a possible implementation, the ground network device sends a first non-ground network air interface capability request to the UE, specifically including: after the UE successfully registers with the TN-CN device through the ground network device, the UE sends a first capability change message to the TN-CN device, and the first capability change message is used to indicate the change of the NTN air interface capability of the UE; the TN-CN device responds to the first capability change message and sends a second non-ground network air interface capability request to the TN-RAN device; the TN-RAN device responds to the second non-ground network air interface capability request and sends the first non-ground network air interface capability request to the UE; or, the TN-CN device responds to the first capability change message and sends the first non-ground network air interface capability request to the UE through the TN-RAN device. In this way, the UE can trigger the TN-CN device to obtain the NTN air interface capability information.

[0024] In a possible implementation manner, the first capability change message is a second mobility registration request message, and the second mobility registration request message includes a parameter for indicating a change in the NTN air interface capability of the UE; or, the first capability change message is a user equipment capability release command message.

[0025] In a possible implementation, the method further includes: after the NTN-CN device receives the first mobility registration request message, sending a first capability synchronization message to the TN-CN device, the first capability synchronization message is used to obtain the NTN air interface capability information of the UE from the TN-CN device; the ground network device sends the second non-ground network air interface capability message to the NTN-CN device, specifically including: the TN-CN device responds to the first capability synchronization message, and sends the second non-ground network air interface capability message to the NTN-CN device. In this way, the NTN-CN device sends the NTN air interface capability information to the NTN-RAN device.

[0026] In a possible implementation manner, sending the NTN air interface capability information of the UE to the NTN-RAN device specifically includes: the NTN-CN device sends an initial context setup request message to the NTN-RAN device, where the initial context setup request message includes the NTN air interface capability information of the UE.

[0027] In a possible implementation manner, the first non-terrestrial network air interface capability request is a user equipment capability query UEcapability enquiry (NTN) message, and the second non-terrestrial network air interface capability request is a non-terrestrial network air interface capability information request NTN capability info request.

[0028] In a possible implementation, the NTN air interface capability information includes the carriers supported by the UE, the antenna polarization direction of the UE, the maximum transmit power of the UE, and the duplex mode of the UE. In this way, the NTN-CN device and the NTN-RAN device can configure air interface resources and communication modes for the UE based on the NTN air interface capability information.

[0029] In a possible implementation, if the NTN-CN device does not receive the NTN air interface capability information of the UE sent by the TN-CN device, the NTN-CN device sends a third non-terrestrial network air interface capability request to the UE through the NTN-RAN device.

[0030] In the second aspect, the present application provides a capability synchronization method, which is applied to a user equipment UE, and the method includes: the UE receives a first non-terrestrial network air interface capability request sent by a terrestrial network device, and the first non-terrestrial network air interface capability request is used to obtain the NTN air interface capability information of the UE; after the UE receives the first non-terrestrial network air interface capability request, the UE sends a first non-terrestrial network air interface capability message to the terrestrial network device, and the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; after the UE searches for the non-terrestrial network NTN, it sends a mobility registration request message to the core network NTN-CN device of the non-terrestrial network, and the mobility registration request message is used to notify the NTN-CN device to send the NTN air interface capability information of the UE to the NTN-RAN device. In this way, the UE receives a request for obtaining the NTN air interface capability information under the TN, and the UE can send the NTN air interface capability information to the core network device under the TN.

[0031] In a possible implementation, before the UE receives the first non-terrestrial network air interface capability request sent by the terrestrial network device, the method further includes: the UE registers with the NTN-CN device through the terrestrial network device. In this way, the UE registers with the NTN-CN device through the TN device, and the NTN-CN device can send the first non-terrestrial network air interface capability request to the UE to obtain the NTN air interface capability information of the UE.

[0032] In a possible implementation, before the UE receives the first non-terrestrial network air interface capability request sent by the terrestrial network device, the method further includes: the UE registers with the TN-CN device. In this way, after the UE registers with the TN-CN device through the TN device, the TN-CN device can send the first non-terrestrial network air interface capability request to the UE to obtain the NTN air interface capability information of the UE.

[0033] In a possible implementation, before the UE receives a first non-terrestrial network air interface capability request sent by a terrestrial network device, the method further includes: the UE sends a first capability change message to the TN-CN device, and the first capability change message is used to indicate that the NTN air interface capability of the UE has changed.

[0034] In this way, after receiving the first capability change message, the TN-CN device can respond to the first capability change message and send a first non-terrestrial network air interface capability request to the UE to obtain the changed NTN air interface capability information of the UE. Alternatively, after receiving the first capability change message, the TN-CN device can send the first capability change message to the NTN-CN device, and the NTN-CN device can respond to the first capability change message and send a second non-terrestrial network air interface capability request to the TN-CN device, and the TN-CN device can respond to the second non-terrestrial network air interface capability request and send the first non-terrestrial network air interface capability request to the UE.

[0035] In a third aspect, the present application provides a capability synchronization method, which is applied to a non-terrestrial network device NTN-CN, and the method includes: the NTN-CN device sends a first non-terrestrial network air interface capability request to a user device UE through a terrestrial network device, and the first non-terrestrial network air interface capability request is used to obtain the NTN air interface capability information of the UE; the NTN-CN device receives a first non-terrestrial network air interface capability message sent by the UE through the terrestrial network device, and the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; after the NTN-CN device receives the mobility registration request message sent by the UE, it sends the NTN air interface capability information of the UE to the first radio access network NTN-RAN device of the non-terrestrial network, and the first mobility registration request message is used for the UE to register with the NTN-CN device. In this way, the NTN-CN device can obtain the NTN air interface capability information of the UE through the terrestrial network device, saving the air interface resources of the NTN.

[0036] In a possible implementation, before the NTN-CN device sends the first non-terrestrial network air interface capability request to the UE through the ground network device, the method further includes: the NTN-CN device accepts the initial registration request of the UE through the ground network device. In this way, the NTN-CN device accepts the initial registration request of the UE through the ground network device, and the NTN-CN device can send the first non-terrestrial network air interface capability request to the UE through the ground network device to obtain the NTN air interface capability information of the UE.

[0037] In a possible implementation, the NTN-CN device sends a first non-terrestrial network air interface capability request to the UE through the ground network device, specifically including: the NTN-CN device receives a first capability change message sent by the UE through the ground network device, the first capability change message is used to indicate that the NTN air interface capability of the UE has changed; the NTN-CN device responds to the first capability change message and sends a first non-terrestrial network air interface capability request to the UE through the ground network device. In this way, the NTN-CN device receives the first capability change message sent by the UE through the ground network device, determines that the NTN air interface capability of the UE has changed, sends the first non-terrestrial network air interface capability request to the UE through the ground network device, and obtains the changed NTN air interface capability information of the UE.

[0038] In a fourth aspect, the present application provides a capability synchronization method, which is applied to a non-terrestrial network device NTN-CN, and the method includes: after the NTN-CN device receives the first mobility registration request message sent by the UE, the NTN-CN device sends a first capability synchronization message to the core network TN-CN device of the terrestrial network, and the first capability synchronization message is used to obtain the NTN air interface capability information of the UE from the TN-CN device; the NTN-CN device receives the first non-terrestrial network air interface capability message sent by the TN-CN device, and the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; the NTN-CN device sends the NTN air interface capability information of the UE to the wireless access network NTN-RAN device of the non-terrestrial network. In this way, the NTN-CN device can obtain the NTN air interface capability information of the UE through the terrestrial network device, saving the air interface resources of the NTN.

[0039] In a fifth aspect, the present application provides a capability synchronization method, which is applied to a core network TN-CN device of a ground network, and the method includes: the TN-CN device sends a first non-ground network air interface capability request to a user equipment UE, and the first non-ground network air interface capability request is used to obtain the NTN air interface capability information of the UE; the TN-CN device receives a first non-ground network air interface capability message sent by the UE, and the first non-ground network air interface capability message includes the NTN air interface capability information of the UE; the TN-CN device sends a second non-ground network air interface capability message to the core network NTN-CN device of the non-ground network, and the second non-ground network air interface capability message includes the NTN air interface capability information of the UE. In this way, the TN-CN device can help the NTN-CN device obtain the NTN air interface capability information of the UE and save NTN air interface resources.

[0040] In a possible implementation, the TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, specifically including: the TN-CN device receives a second non-terrestrial network air interface capability request sent by the NTN-CN device; the TN-CN device responds to the second non-terrestrial network air interface capability request and sends a first non-terrestrial network air interface capability request to the UE. In this way, after receiving the second non-terrestrial network air interface capability request from the NTN-CN device to obtain the NTN air interface capability information of the UE, the TN-CN device sends the first non-terrestrial network air interface capability request to the UE to obtain the NTN air interface capability information of the UE.

[0041] In a possible implementation, the TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, specifically including: after the TN-CN device accepts the initial registration request of the UE, the TN-CN device sends the first non-terrestrial network air interface capability request to the UE. In this way, after the TN-CN device receives the initial registration request of the UE supporting the NTN communication function, it obtains the NTN air interface capability information of the UE and synchronizes the information to the NTN-CN device.

[0042] In a possible implementation, the TN-CN device sends a second non-terrestrial network air interface capability message to the core network NTN-CN device of the non-terrestrial network, specifically including: the TN-CN device receives a first capability synchronization message sent by the NTN-CN device; the TN-CN device responds to the first capability synchronization message and sends a second non-terrestrial network air interface capability message to the NTN-CN device. In this way, the TN-CN device saves the NTN air interface capability information of the UE, and when receiving the first capability synchronization message of the NTN-CN device, the NTN air interface capability information is sent to the NTN-CN device.

[0043] In a possible implementation, before the TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, the method also includes: the TN-CN device receives a first capability change message sent by the UE, and the first capability change message is used to indicate that the NTN air interface capability of the UE has changed.

[0044] In some examples, after receiving the first capability change message, the TN-CN device sends a first non-terrestrial network air interface capability request to the UE in response to the first capability change message.

[0045] In some examples, after receiving the first capability change message, the TN-CN device sends the first capability change message to the NTN-CN device; the TN-CN device receives the second non-terrestrial network air interface capability request sent by the NTN-CN device; the TN-CN device responds to the second non-terrestrial network air interface capability request and sends the first non-terrestrial network air interface capability request to the UE. In this way, the NTN-CN device can respond to the first capability change message and send the second non-terrestrial network air interface capability request to the TN-CN device, triggering the TN-CN device to obtain the NTN air interface capability information of the UE.

[0046] In a sixth aspect, the present application provides a capability synchronization method, which is applied to a wireless access network TN-RAN device of a ground network. In a possible implementation, the method includes: the TN-RAN device sends a first non-ground network air interface capability request to a user equipment UE, and the first non-ground network air interface capability request is used to obtain the NTN air interface capability information of the UE; the TN-RAN device receives a first non-ground network air interface capability message sent by the UE, and the first non-ground network air interface capability message includes the NTN air interface capability information of the UE; the TN-RAN device sends a second non-ground network air interface capability message to a core network NTN-CN device of the non-ground network or a core network TN-CN device of the ground network, and the second non-ground network air interface capability message includes the NTN air interface capability information of the UE. In this way, the TN-RAN device can help the NTN-CN device obtain the NTN air interface capability information of the UE and save NTN air interface resources.

[0047] In the seventh aspect, the present application provides an electronic device, comprising: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer executable programs. When the one or more processors execute the computer executable programs, the electronic device executes any possible implementation method as described in the second to sixth aspects.

[0048] In an eighth aspect, the present application provides a computer-readable storage medium storing a computer program. When the computer program runs on a processor of an electronic device, the electronic device executes any possible implementation method as described in the second to sixth aspects.

[0049] In a ninth aspect, the present application provides a chip, applied to a user device, comprising a plurality of modules, the plurality of modules comprising a mobile communication module and an NTN communication module, the plurality of modules being used to execute any possible implementation method as in the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 A schematic diagram of a communication system 10 provided in an embodiment of the present application;

[0051] Figure 2 A schematic diagram of a registration call flow provided in an embodiment of the present application;

[0052] Figure 3 A schematic diagram of a process of changing UE capabilities provided in an embodiment of the present application;

[0053] Figure 4 A schematic diagram of a capability synchronization method flow provided in an embodiment of the present application;

[0054] Figure 5A flowchart of another capability synchronization method provided in an embodiment of the present application;

[0055] Figure 6 A flowchart of another capability synchronization method provided in an embodiment of the present application;

[0056] Figure 7 A flowchart of another capability synchronization method provided in an embodiment of the present application;

[0057] Figure 8 A schematic diagram of the hardware structure of a UE 100 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0059] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0060] First, a communication system provided by an embodiment of the present application is introduced.

[0061] For example, Figure 1As shown, the communication system 10 may include but is not limited to core network (CN) equipment, radio access network (RAN) equipment and user equipment UE100. The core network equipment can be used to verify the user equipment and provide mobile communication services (e.g., call control, data transmission, etc.) to the UE accessing the core network equipment. The core network equipment can be divided into terrestrial network core network (TN-CN) equipment and non-terrestrial network core network (NTN-CN) equipment. NTN-CN equipment may include but is not limited to access and mobility management function (AMF) 300. AMF 300 can be used for NTN core network registration management, UE mobility management control and context security management, etc.

[0062] The wireless access network device may include one or more base stations (next generation node b, gNB). The wireless access network device may be used for UE to access core network devices. The wireless access network device may be divided into terrestrial network radio access network (TN-RAN) devices and non-terrestrial network radio access network (NTN-RAN) devices. UE100 may access TN-CN devices through TN-RAN devices, and TN-RAN devices may include Figure 1 The UE 100 can access the NTN-CN device through the NTN-RAN device, and the NTN-RAN device may include Figure 1The base station 200 shown. It should be noted that the base station 200 may include a satellite and a ground transceiver station. When UE100 sends data to the NTN-CN device, UE100 first sends the data to the satellite of the base station 200. After the satellite of the base station 200 receives the data sent by UE100, it can relay the data sent by UE100 to the ground transceiver station, and the ground transceiver station can transmit the data sent by UE100 to the NTN-CN device. Similarly, when the NTN-CN device sends data to the UE100, the NTN-CN device can first send the data to the ground transceiver station of the base station 200. The ground transceiver station can intermediately forward the data sent by the NTN-CN device to the satellite of the base station 200, and the satellite of the base station 200 can send the data of the NTN-CN device to the UE100.

[0063] Among them, TN-RAN equipment and TN-CN equipment can be collectively referred to as ground network equipment, and NTN-CN equipment and NTN-RAN equipment can be collectively referred to as non-ground network equipment.

[0064] In an embodiment of the present application, UE100 can send a wireless signal to the base station 200. After the base station 200 receives the wireless signal sent by UE100, it can forward the wireless signal sent by UE100 to the AMF300 on the ground. Similarly, AMF300 can send a wireless signal to the base station 200, and after the base station 200 receives the wireless signal sent by AMF300, it can forward the wireless signal to UE100. In this way, when UE100 is in an area such as the ocean, desert, grassland, or uninhabited area where mobile communications are not covered, or cannot be covered, or the communication system is damaged, UE100 cannot receive signals from the ground network, and can access the core network of the non-ground network through a satellite base station, and perform positioning and communication through the core network of the non-ground network.

[0065] Among them, the transmission protocol of the communication system 10 includes an access stratum (AS) protocol and a non-access stratum (NAS) protocol. In the communication system 10, UE100 and AMF300 can communicate through the NAS protocol, UE100 and base station 200 can communicate through the AS protocol, and AMF300 and base station 200 can also communicate through the AS protocol. Among them, the AS protocol layer may include a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer.

[0066] In the following description, NTN-CN equipment may be abbreviated as NTN-CN, TN-CN equipment may be abbreviated as TN-CN, NTN-RAN equipment may be abbreviated as NTN-RAN, and TN-RAN equipment may be abbreviated as TN-RAN.

[0067] In a possible implementation, after UE100 finds NTN-RAN, it performs the process of registering with NTN-CN. In the process of UE100 registering with NTN-CN, NTN-CN can obtain the NTN air interface capability information of UE through NTN-RAN. Specifically, the process of UE100 registering with NTN-CN can refer to Figure 2 The embodiment shown. Figure 2 The content of stage 7 in the description describes in detail the process of NTN-CN obtaining the NTN air interface capability information of UE100. For example, Figure 2 As shown, the call process of UE100 registering under NTN includes the following steps:

[0068] Phase 1: Downlink Synchronization (DL Sync)

[0069] S201. UE 100 receives a master information block (MIB) sent by base station 200 .

[0070] The base station 200 can broadcast and send the MIB, and all UEs within the beam range of the base station 200 can receive the MIB sent by the base station 200. The MIB includes demodulation parameters of system information block type 1 (SIB1), system bandwidth, system frame number, etc. The UE 100 can adjust the receiving frequency range of the UE 100 to the frequency range of the downlink signal received from the base station 200 based on the MIB. The UE 100 can also adjust the time point of receiving the communication frame sent by the base station 200 based on the MIB.

[0071] S202 . UE 100 receives SIB1 sent by base station 200 .

[0072] Among them, SIB1 can also be called remaining minimum system information (RMSI), and the base station 200 can broadcast and send SIB messages. UE100 can obtain the content of SIB1 broadcast and sent by the base station 200 according to the demodulation parameters indicated by MIB. Among them, SIB1 can include the reception time parameter of other SIB messages, which is used to indicate the time point when UE100 receives other SIBs.

[0073] In this way, after executing the steps of phase one, UE100 can achieve downlink synchronization between UE100 and base station 200, and UE100 can receive data sent by base station 200 within the frequency band indicated by base station 200 and at the time indicated by base station 200.

[0074] Phase 2: Uplink Synchronization (UL Sync)

[0075] S203 . UE 100 sends message 1 (message 1 , MSG1 ) to base station 200 .

[0076] Among them, message 1 is the preamble sequence of the uplink synchronization process of the 3rd generation partnership project (3GPP). UE100 can obtain the configuration information of the random access channel (RACH) based on SIB1, and select the preamble sequence (preamble) corresponding to the configuration information according to the obtained configuration information. UE100 can achieve uplink synchronization between UE100 and base station 200 based on the preamble sequence, and UE100 can send an uplink signal to base station 200. Among them, message 1 can be called a random access channel preamble sequence (RACH Preamble).

[0077] S204 . UE 100 receives message 2 (message 2, MSG2) sent by base station 200 .

[0078] After receiving MSG1 sent by UE100, base station 200 can determine the transmission delay between base station 200 and UE100 based on MSG1. Afterwards, base station 200 can determine the value of the timing advance command (TAM) field based on the transmission delay between base station 200 and UE100. The timing advance command field is a field in MSG2, which is used to indicate the time when UE100 sends uplink data. Base station 200 can send MSG2 including the TAM field to UE100. After receiving MSG2, UE100 can determine the time to send uplink data to base station 200. Message 2 can be called a random access channel response (RACH Response).

[0079] In this way, after executing the steps of phase 2, UE100 can achieve uplink synchronization between UE100 and base station 200, and UE100 can send data to base station 200 within the frequency band indicated by base station 200 and at the time indicated by base station 200.

[0080] Phase 3: Signaling radio bearers 0 (SRB0)

[0081] S205 . UE 100 sends message 3 (message 3 , MSG3 ) to base station 200 .

[0082] After receiving MSG2, UE100 can perform the steps of establishing an RRC connection with base station 200, and UE100 can transmit NAS layer data through the RRC connection. Among them, UE100 can send MSG3 to base station 200 through SRB0 on ​​the uplink common control channel (UL-CCCH) based on the time of sending uplink data indicated by MSG2, and the MSG3 is an RRC Setup Request. The SRB0 can be used to carry the RRC message MSG3.

[0083] S206 . UE 100 receives message 4 (message 4 , MSG4 ) sent by base station 200 .

[0084] The base station 200 can receive MSG3 from the UE 100 at the time indicated by MSG2. After receiving MSG3, the base station 200 can determine whether to allow the establishment of the RRC connection, and set the content of MSG4 according to the determination result. Among them, when the base station 200 does not allow the establishment of the RRC connection, the message 4 is a radio resource control reject (RRC Reject) message. When the base station 200 confirms the establishment of the RRC connection, the message 4 is a radio resource control setup (RRC Setup) message. The base station 200 can also carry the complete configuration of SRB1 in the RRC Setup message, and the base station 200 can send the MSG4 through SRB0. After receiving the RRC Setup message, the UE 100 can establish SRB1 based on the message.

[0085] In this way, UE 100 can establish an RRC connection after executing the steps of phase three.

[0086] Phase 4: Signaling radio bearers 1 (SRB1)

[0087] S207. UE 100 sends a radio resource control connection setup complete (RRC Setup Complete) message and a non-access stratum registration message (NAS Registration) to the base station 200.

[0088] After receiving MSG4, UE100 can configure SRB1 based on MSG4. After configuring SRB1, UE100 can send an RRC Setup Complete message to base station 200, which is used for UE100 to confirm that the RRC connection has been successfully established. Base station 200 can select AMF after receiving the RRC Setup Complete message. Here, the AMF selected by base station 200 is Figure 1 AMF300 shown.

[0089] The RRC Setup Complete message carries a non-access layer registration message, which can be used for UE 100 to register with AMF. The RRC Setup Complete message sent by UE 100 to base station 200 is carried on SRB1.

[0090] In this way, in the fourth stage, UE100 can send a NAS message to base station 200 through SRB1, and base station 200 can forward the NAS message of UE100 to AMF300.

[0091] Phase 5: Registration request

[0092] S208. The base station 200 sends the initial user equipment information (Initial UE Message) and registration request (registration request) message of the NG application protocol (NGAP) to the AMF300.

[0093] Among them, NGAP can provide signaling services to RAN nodes and AMF nodes, and can provide signaling and data connections for UE to access the core network. After the base station 200 selects AMF300, it can send an Initial UE Message to AMF300. The message can be used to notify AMF300 that UE100 will access the core network. The message includes the radio access network user equipment identity (RAN UE NGAP ID) assigned by the base station 200 to UE100 in the NG application protocol. AMF300 can transmit NAS messages with UE100 through the RAN UE NGAP ID. Among them, the base station 200 can send the NAS message (i.e., the registration request message) carried in the RRC Setup Complete message to AMF300 through the Initial UEMessage, and the registration request message can be used to notify AMF300 that UE100 registers the core network.

[0094] Phase 6: NAS Procedure Identity, Authentication (AUTH) and Security Mode Command (SMC)

[0095] S209.AMF300 sends a NGAP non-access layer identity request (NAS Identity Request) message to the base station 200.

[0096] Among them, the non-access layer identity request is used by the AMF300 of the core network to obtain the identity of UE100.

[0097] S210 . The base station 200 sends a non-access stratum identity request message to the UE 100 .

[0098] After receiving the NAS message sent by AMF300, base station 200 can forward the NAS message to UE100.

[0099] S211 . UE 100 sends a non-access stratum identity response (NAS Identity Response) message to base station 200 .

[0100] After receiving the NAS message from AMF300, UE100 may generate an identity response message, which carries the identity indicated by the identity request message. For example, the identity may be an international mobile subscriber identity (IMSI). UE100 may send the identity response message to base station 200.

[0101] S212. The base station 200 sends a non-access layer identity response message of NGAP to the AMF 300.

[0102] After receiving the NAS message sent by UE100, base station 200 may forward the NAS message to AMF300. After AMF300 receives the identity response message from UE100, it may perform step S213 based on the identity identifier of UE100 carried in the identity response message.

[0103] S213.AMF300 sends a NGAP non-access layer authentication request (NAS AuthenticationRequest) message to the base station 200.

[0104] After receiving the identity identification parameters, AMF300 may generate authentication parameters carried in the non-access layer authentication request message. The authentication parameters may include but are not limited to a random number (RAND) and an authentication token (AUTN) generated by AMF300 through a random number generator. AMF300 may send the non-access layer authentication request message to the base station 200.

[0105] S214 . The base station 200 sends a non-access stratum authentication request message to the UE 100 .

[0106] S215 . UE 100 sends a non-access stratum authentication response (NAS Authentication Response) message to base station 200 .

[0107] After receiving the NAS authentication request message sent by AMF300 through base station 200, UE100 can calculate the response (RES) of UE100 based on RAND and AUTN in the authentication parameters. UE100 can send a non-access layer authentication response message carrying RES to base station 200.

[0108] S216. The base station 200 sends a non-access layer authentication response message of NGAP to the AMF300.

[0109] After AMF300 receives the non-access layer authentication response message from UE100 through base station 200, it can authenticate whether UE100 is a legitimate terminal based on RES. When AMF300 confirms that UE100 is a legitimate terminal (i.e., AMF300 authentication is successful), AMF300 can provide communication services to UE100.

[0110] S217.AMF300 sends a NGAP non-access layer security mode command (NAS Security Mode Command) message to the base station 200.

[0111] The non-access layer security mode command message may be used to notify UE 100 to start integrity protection and data encryption.

[0112] S218. The base station 200 sends a non-access layer security mode command message to the UE 100.

[0113] S219 . UE 100 sends a non-access stratum security mode complete (NAS Security Mode Complete) message to base station 200 .

[0114] UE100 can determine the integrity protection and encryption algorithm based on the non-access layer security mode command message. UE100 can encrypt the NAS message based on the integrity and encryption algorithm. After receiving the non-access layer security mode command message, UE100 can also send a non-access layer security mode completion message to the base station 200 to indicate that UE100 has completed the security mode configuration.

[0115] S220. The base station 200 sends a non-access layer security mode completion message of NGAP to the AMF 300.

[0116] AMF 300 may receive a non-access stratum security mode completion message from UE 100 through base station 200, and determine that UE 100 encrypts the NAS message according to the agreed encryption algorithm.

[0117] S221.AMF300 sends an NGAP initial context setup request message and a registration accept message to the base station.

[0118] AMF 300 may send an initial context setup request message to base station 200 to start the initial context establishment process. The message includes a registration acceptance message. The registration acceptance message is a NAS message.

[0119] In this way, in the sixth stage, UE100 and UE AMF300 can transparently transmit NAS messages through base station 200 to complete identity query, authentication, setting of NAS security mode and UE100 registration process.

[0120] Phase 7: UE Capability Exchange

[0121] S222 . The base station 200 sends a user equipment capability inquiry (UE Capability Enquiry) message to the UE 100 .

[0122] After receiving the initial context setup request message sent by AMF300, base station 200 can send a user equipment capability query message to UE100 to start the capability query process of UE100. After obtaining the capability of UE100, base station 200 can provide UE100 with the resources required by UE100.

[0123] It should be noted that if the initial context setup request message includes an information element (IE) carrying the user equipment radio capability (UE Radio Capability) of UE100, it indicates that AMF300 stores the NTN air interface capability information of UE100, and the base station 200 does not execute step S222. If the initial context setup request message does not include the IE carrying the UE Radio Capability of UE100, the base station 200 can obtain the NTN air interface capability information of UE100 through stage seven, and send the NTN air interface capability information of UE100 to AMF300. It should also be noted that when UE100 performs the NTN registration process or changes capabilities, the initial context setup request message sent by AMF300 does not include the IE carrying the UERadio Capability of UE100.

[0124] S223. UE100 sends a user equipment air interface capability information (UE Capability Information) message to the base station 200.

[0125] UE100 replies to base station 200 with a UE Capability Information message, which may carry NTN air interface capability information of UE100, and is used for UE100 to report NTN air interface capability information of UE100 to base station 200. For example, NTN air interface capability information of UE100 may indicate carriers (bands) supported by UE100, user equipment categories (UE Category) of UE100, antenna polarization directions of UE100, maximum transmit power (power level) of UE100, duplex mode of UE100, and the like.

[0126] S224. The base station 200 sends a NGAP user equipment air interface capability information indication (UE Capability Info Indication) message to the AMF 300.

[0127] The base station 200 may send a UE Capability Info Indication message to the AMF 300, which may carry the NTN air interface capability information of the UE 100, and is used by the base station 200 to report the NTN air interface capability information of the UE 100 to the AMF 300. The AMF 300 may save the received NTN air interface capability information of the UE 100.

[0128] In this way, in the seventh stage, AMF300 and base station 200 both obtain the NTN air interface capability information of UE100, and AMF300 and base station 200 can configure air interface resources and communication methods for UE100 based on the NTN air interface capability information of UE100.

[0129] Phase 8: Access stratum security mode command (ASSMC)

[0130] S225. The base station 200 sends an access layer security mode command message to the UE 100.

[0131] After reporting the capabilities of UE100 to AMF300, base station 200 may send an access layer security mode command message to UE100, instructing UE100 to perform integrity protection and encryption on data, so that RRC messages can be securely transmitted between UE100 and base station 200. The access layer security mode command message may indicate the security key, integrity key, encryption algorithm, and integrity protection algorithm used when transmitting messages between UE100 and base station 200. After base station 200 sends the access layer security mode command message, when base station 200 sends data to UE100, it may encrypt the data and set integrity protection for the data, and then send the encrypted and integrity protected data to UE100.

[0132] S226. UE100 sends an access layer security mode complete (AS Security Mode Complete) message to the base station 200.

[0133] After receiving the access layer security mode command message sent by the base station 200, the UE 100 may send an access layer security mode completion message to the base station 200, and the access layer security mode completion message has been processed with integrity protection. After sending the access layer security mode completion message to the base station 200, the UE 100 may start the security mode. In the security mode, the UE 100 will use the algorithm agreed upon with the base station 200 to perform integrity protection and encryption on the data, and then send the integrity protected and encrypted data to the base station 200.

[0134] In this way, after the eighth stage, UE 100 and base station 200 can protect the transmitted data through the agreed key encryption to ensure the security of data transmission.

[0135] Phase 9: Signaling radio bearers 2 (SRB2) and data radio bearers (DRB)

[0136] S227. The base station 200 sends a radio resource control connection reconfiguration (RRC ConnectionReconfiguration) message and a registration acceptance message to the UE 100.

[0137] The base station 200 sends an RRC Connection Reconfiguration message to the UE 100. The RRC Connection Reconfiguration message includes a registration acceptance message sent by the AMF and parameters for establishing a radio bearer.

[0138] S228. UE 100 sends a radio resource control connection reconfiguration complete (RRC Connection Reconfiguration Complete) message to base station 200.

[0139] After receiving the RRC Connection Reconfiguration message, UE100 starts to establish SRB2 and DRB. After the establishment is successful, UE100 can reply RRC Connection Reconfiguration Complete message to base station 200. Among them, DRB can be used to transmit data of UE100, for example, transmission control protocol (TCP) / internet protocol (IP) data packets.

[0140] S229. The base station 200 sends an initial context setup response message of NGAP to the AMF 300.

[0141] After receiving the RRC Connection Reconfiguration Complete message, the base station 200 can send an initial context setup response message to the AMF 300.

[0142] Stage 10: Registration Completed

[0143] S230 . UE 100 sends a registration complete message to base station 200 .

[0144] S231. The base station 200 sends an NGAP registration completion message to the AMF 300.

[0145] Base station 200 sends the registration completion message of UE100 to AMF300, and UE100 successfully registers with the core network.

[0146] In this way, after the above ten steps, UE100 is successfully registered with the core network, and can send service data to AMF300 through base station 200, and can also receive service data from AMF300 through base station 200.

[0147] Phase 11: Protocol Data Unit Session (PDU Session)

[0148] S232 . UE 100 sends a protocol data unit session establishment request (PDU Session Establishment Request) message to base station 200 .

[0149] Among them, the PDU Session Establishment Request message is a NAS message.

[0150] S233. The base station 200 sends an NGAP protocol data unit session establishment request message to the AMF 300.

[0151] S234.AMF300 sends a NGAP protocol data unit session establishment accept (PDU Session Establishment Accept) message to the base station 200.

[0152] After receiving the protocol data unit session establishment request message from UE100 through base station 200, AMF300 can allocate resources for PDU session connection to UE100, and send a protocol data unit session establishment accept message to UE100 through base station 200.

[0153] S235 . The base station 200 sends a protocol data unit session establishment accept message to the UE 100 .

[0154] UE100 establishes a PDU session connection with AMF300, and PDU messages can be transmitted through this connection.

[0155] In this way, through step S222 to step S224, the base station 200 and the AMF 300 both obtain the NTN air interface capability information of the UE 100. The distance between the UE 100 and the base station 200 is far. In order to prevent the base station 200 from being unable to transmit data to the UE 100, the bandwidth used by the base station 200 for transmitting data is relatively narrow, and the data transmitted per unit time by the UE 100 and the base station 200 is relatively small. In addition, the NTN air interface capability information of the UE occupies more air interface resources, and the channel quality between the UE 100 and the base station 200 is relatively poor. It takes more time for the UE 100 and the base station 200 to transmit the NTN air interface capability information of the UE. In addition, since the power consumption of the UE 100 to send or receive satellite signals is high, the UE 100 needs to consume more power to transmit the NTN air interface capability information to the base station 200.

[0156] In a possible implementation, after the capability is changed, UE100 may send a notification message to NTN-RAN to indicate the update of the NTN air interface capability information of UE100. After receiving the notification message, NTN-RAN may notify NTN-CN to delete the saved NTN air interface capability information of UE100. NTN-RAN may also obtain updated NTN air interface capability information from UE100, and send the updated NTN air interface capability information of UE100 to NTN-CN. In this way, UE100 may notify NTN-RAN after the capability is changed. After receiving the message of the capability change of UE100, NTN-RAN may re-acquire the NTN air interface capability information of UE100, and update the NTN air interface capability information of UE100 stored in NTN-RAN and NTN-CN.

[0157] In some examples, the state of UE100 may include connected, idle, and inactive. If UE100 is in a connected state, UE100 may release the local connected state after the capability is changed, and then update the NTN air interface capability information of UE100 stored in the base station 200 and AMF300. If UE100 is not in a connected state, UE100 may directly update the NTN air interface capability information of UE100 stored in the base station 200 and AMF300, and UE100 may update the NTN air interface capability information without releasing the connected state.

[0158] In some examples, after the capability is changed, UE100 may send a registration request message of a registration type of mobility registration update to AMF300, and the registration request message includes a parameter for indicating the capability change of UE100. After receiving the registration request message, AMF300 may delete the invalid NTN air interface capability information of UE100, and trigger base station 200 to re-acquire the updated NTN air interface capability information of UE100.

[0159] For example, Figure 3 As shown, the UE100 capability change process includes the following steps:

[0160] S301. UE100 capability changes.

[0161] S302. UE100 determines whether it is in a connected state.

[0162] After the capability of UE100 is changed, UE100 may start the process of updating the NTN air interface capability information of UE100 stored on the NTN side. First, after the capability is changed, UE100 may determine whether UE100 is in a connected state. When UE100 determines that UE100 is in a connected state, step S303 may be executed. When UE100 determines that UE100 is not in a connected state, UE100 may execute step S304.

[0163] S303. UE100 releases the connection state.

[0164] After determining that the UE 100 is in the connected state, the UE 100 may release the local connected state and switch to the non-connected state (eg, idle state). After releasing the local connected state, the UE 100 may execute step S304 to notify the base station 200 to update the NTN air interface capability information of the UE 100.

[0165] S304. UE100 sends a registration request message to base station 200, including parameters for indicating that the NTN air interface capability of UE100 has changed.

[0166] After releasing the local connection state, UE100 may send a registration request message to base station 200. The registration request message may include parameters for indicating that the NTN air interface capability of UE100 has changed. Among them, the types of registration request messages sent by UE100 include initial registration, mobility registration and periodic registration. Here, in order to update the NTN air interface capability information of UE100 stored in base station 200 and AMF300, UE100 initiates a registration request message with a registration type of mobility registration.

[0167] For example, the registration request message may include a next generation radio access network radio capability update (NG-RAN RadioCapability Update) field. The NG-RAN Radio Capability Update field may be used to indicate whether the NTN air interface capability of UE100 has changed. When the value of this field is 1, it indicates that the NTN air interface capability of UE100 has changed. When the value of this field is 0, it indicates that the NTN air interface of UE100 has not changed. Here, the value of this field in the registration request message is 1.

[0168] S305. The base station 200 sends a user equipment capability release command (UE Capability Release Command) message to the AMF 300.

[0169] After receiving the parameter sent by UE100 to indicate the change of UE100 capability, base station 200 may send a user equipment capability release command message to AMF300. After receiving the user equipment capability release command message, AMF3000 may delete the stored NTN air interface capability information of UE100.

[0170] S306 . The base station 200 sends a user equipment capability query message to the UE 100 .

[0171] S307 . UE 100 sends a user equipment air interface capability information message to the base station 200 .

[0172] S308. The base station 200 sends a NGAP user equipment air interface capability information indication message to the AMF 300.

[0173] After receiving the NTN air interface capability information of the UE 100, the AMF 300 may store the NTN air interface capability information of the UE 100. Specifically, the description of steps S306 to S308 may refer to Figure 2 The description of stage seven in the illustrated embodiment will not be repeated here.

[0174] S309. UE100 switches to connected state.

[0175] UE100 can switch to the connected state after updating the NTN air interface capability information of UE100 stored on the NTN side. It should be noted that when UE100 releases the connected state, UE100 releases the RRC connection with the base station 200 and maintains the registration state in AMF300. Afterwards, after UE100 sends the updated NTN air interface capability information to the base station 200, it can switch back to the connected state and restore the RRC connection with the base station 200.

[0176] In this way, when the UE 100 capability changes, the UE 100 can Figure 3 The process shown realizes the synchronization of the NTN air interface capability information of UE 100.

[0177] An embodiment of the present application provides a capability synchronization method. UE100 includes an NTN communication module and a mobile communication module, the mobile communication module is bound to a subscriber identification module (SIM) 1, and the NTN communication module is bound to SIM2. Among them, UE100 can access the terrestrial network through the mobile communication module. UE100 can access the non-terrestrial network through the NTN communication module. After the mobile communication module is registered with the core network of the terrestrial network, the NTN communication module can execute the registration process of the core network of the non-terrestrial network through the mobile communication module, the wireless access network of the terrestrial network, and the core network of the terrestrial network. The NTN communication module can also send the UE's NTN air interface capability information to the core network of the non-terrestrial network through the mobile communication module and the core network of the terrestrial network after executing the registration process.

[0178] In this way, the NTN communication module of UE100 can access the core network of the non-terrestrial network after receiving the NTN signal. Since UE100 has sent the NTN air interface capability information of UE100 to the core network of the non-terrestrial network under the terrestrial network, and the core network of the non-terrestrial network stores the NTN air interface capability information of UE100, UE100 does not need to transmit the NTN air interface capability information to the core network of the non-terrestrial network under the non-terrestrial network, thus reducing the signaling overhead between UE100 and the core network of the non-terrestrial network, saving the time required for UE100 to transmit the NTN air interface capability information under the non-terrestrial network, and saving the power consumption of UE100.

[0179] It should be noted that the binding of the NTN communication module and the mobile communication module of UE100 with the SIM is only an example. The NTN communication module and the mobile communication module of UE100 may also be bound to an embedded subscriber identification module (embedded subscriber identification module, eSIM), which is not limited in the embodiments of the present application.

[0180] For example, Figure 4 As shown, the capability synchronization method provided in the embodiment of the present application includes the following steps:

[0181] S401 . The mobile communication module of UE100 receives a non-terrestrial network registration request message 31 from the NTN communication module of UE100 .

[0182] Among them, before initiating TN registration, the mobile communication module can receive registration request information from the NTN communication module. For example, data can be transmitted between the mobile communication module and the NTN communication module through the NAS layer protocol, and the mobile communication module can obtain the non-terrestrial network registration request message 31 of the NTN communication module through the NAS layer protocol. The non-terrestrial network registration request message 31 can be used to trigger the NTN-CN to start the registration process. Among them, the registration type of the non-terrestrial network registration request message 31 is initial registration (initial registration). The NTN communication module of UE100 is not registered with NTN-CN after power-on, and initiates an initial registration request. For example, the non-terrestrial network registration request message 31 can be expressed as NTN registrationrequest (initial registration).

[0183] The NTN communication module may send the registration request message to the mobile communication module after powering on. Alternatively, the mobile communication module may obtain the registration request message from the NTN communication module after powering on. Alternatively, the mobile communication module may obtain the registration request message from the NTN communication module before initiating TN registration. Alternatively, the mobile communication module may obtain the registration request message after successfully registering the TN-CN device.

[0184] S402. The mobile communication module registers with TN-CN through TN-RAN.

[0185] After the UE 100 is powered on, it can register with the TN-CN. The mobile communication module performs the network registration operation on the TN-CN. The specific description of the mobile communication module registering with the TN-CN through the TN-RAN can be found in Figure 2 The embodiment in which the UE 100 is registered with the NTN-CN via the NTN-RAN is not described in detail here. The mobile communication module is successfully registered with the TN-CN.

[0186] Optionally, the mobile communication module may obtain the registration request message 31 of the NTN communication module after successfully registering with the TN-CN.

[0187] S403. The mobile communication module sends a non-access layer message (NAS message) 32 to the TN-CN through the TN-RAN. The non-access layer message 32 includes an N1 non-terrestrial network container (n1 interface non-terrestrial network container, N1 NTN Container) 33. The N1 NTN Container 33 includes a non-terrestrial network registration request message 31.

[0188] The N1 interface is a communication interface between the UE 100 and the AMF 300 of the NTN, and the N1 NTN Container can be used to carry data sent by the UE 100 to the AMF 300. Exemplarily, the non-access layer message 32 can be expressed as a NAS message (N1NTN Container (NTN registration request (initial registration))).

[0189] S404. TN-CN sends N1 NTN Container 33 to NTN-CN.

[0190] TN-CN can send N1 NTN Container 33 to NTN-CN based on the information of SIM2's NTN subscription, for example, the public land mobile network (PLMN) of SIM2's NTN. Specifically, the AMF of TN-CN can send N1NTN Container 33 to the AMF 300 of NTN-CN. Among them, TN-CN includes a subscription server, which can be used to provide NTN subscription services. SIM2 can obtain the NTN subscription service through the operator of TN-CN. The AMF of TN-CN can obtain the information of SIM2's NTN subscription from the subscription server of TN-CN.

[0191] S405. NTN-CN obtains the identity of the NTN communication module.

[0192] The AMF 300 of NTN-CN can obtain the identity of the NTN communication module through TN-CN, TN-RAN and the mobile communication module. Here, the identity of the NTN communication module is the SIM2 identifier, for example, the SIM2 identifier can be a subscriber concealed identifier (SUCI). The AMF 300 can determine the identity of the NTN communication module based on the SUCI.

[0193] Exemplarily, NTN-CN may send an N1NTN Container including a non-terrestrial network identity request (NTN identity request) message to TN-CN. The non-terrestrial network identity request message is used to obtain the identity of the NTN communication module of UE100. TN-CN sends a non-access layer message including the N1 NTNContainer to the mobile communication module of UE100 through TN-RAN. The mobile communication module of UE100 sends a non-terrestrial network identity request message to the NTN communication module of UE100.

[0194] After receiving the non-terrestrial network identity request message, the NTN communication module can generate a non-terrestrial network identity response message (NTN identity response) based on the identity of the NTN communication module, and send the non-terrestrial network identity response message to the mobile communication module. The mobile communication module sends a non-access layer message to the TN-CN through the TN-RAN, and the non-access layer message includes an N1 NTN Container, and the N1 NTN Container includes the non-terrestrial network identity response message. The TN-CN sends the N1NTN Container including the non-terrestrial network identity response message to the NTN-CN. In this way, the NTN-CN obtains the identity of the NTN communication module of the UE100 through the TN-CN, the TN-RAN and the mobile communication module.

[0195] S406. NTN-CN authenticates SIM2 bound to the NTN communication module.

[0196] Authentication signaling can be transmitted between NTN-CN and NTN communication module through TN-CN, TN-RAN and mobile communication module to realize NTN-CN's AMF300 to authenticate SIM2 of UE100.

[0197] Exemplarily, after receiving the identity of the NTN communication module, the NTN-CN can authenticate the NTN communication module. The NTN-CN can send an N1 NTN Container including a non-terrestrial network authentication request message to the TN-CN. The non-terrestrial network authentication request message is used to authenticate the SIM2 bound to the NTN communication module of the UE100. The TN-CN sends a non-access layer message including the N1 NTN Container to the mobile communication module of the UE100 through the TN-RAN. The mobile communication module of the UE100 sends a non-terrestrial network authentication request message to the NTN communication module of the UE100.

[0198] After receiving the non-terrestrial network authentication request message, the NTN communication module can calculate the authentication parameters of SIM2 and the authentication parameters of the non-terrestrial network authentication request message through the authentication algorithm to obtain an authentication response, and generate a non-terrestrial network authentication response message (NTN authentication response) based on the authentication response. The NTN communication module sends the non-terrestrial network authentication response message to the mobile communication module. The mobile communication module sends a non-access layer message to the TN-CN through the TN-RAN, and the non-access layer message includes an N1 NTN Container, and the N1NTN Container includes the non-terrestrial network authentication response message. The TN-CN sends the N1 NTN Container including the non-terrestrial network authentication response message to the NTN-CN. The NTN-CN can determine whether the UE100 is authenticated based on the authentication response of the non-terrestrial network authentication response message. Here, the NTN-CN authenticates the UE100. In this way, the NTN-CN authenticates the SIM2 bound to the NTN communication module of the UE100 through the TN-CN, the TN-RAN and the mobile communication module.

[0199] S407. NTN-CN notifies the NTN communication module to configure the security mode.

[0200] NTN-CN and NTN communication module can transmit security mode command signaling through TN-CN, TN-RAN and mobile communication module to realize the security mode command operation of NTN-CN's AMF300 on UE100. UE100 and AMF300 can use the agreed encryption algorithm and integrity algorithm to ensure the security of transmitted data.

[0201] Exemplarily, after successfully authenticating SIM2 bound to the NTN communication module, NTN-CN may notify UE100 to configure the security mode. NTN-CN may send an N1 NTN Container including a non-terrestrial network security mode command message to TN-CN. The non-terrestrial network security mode command message is used to notify the NTN communication module of UE100 to configure the security mode. TN-CN sends a non-access layer message including the N1 NTN Container to the mobile communication module of UE100 through TN-RAN. The mobile communication module of UE100 sends a non-terrestrial network security mode command message to the NTN communication module of UE100.

[0202] After receiving the non-terrestrial network security mode command message, the NTN communication module can determine the encryption algorithm and the integrity algorithm, and UE100 can process the uplink data sent to NTN-CN through the obtained encryption algorithm and integrity algorithm. The NTN communication module can also generate a non-terrestrial network security mode complete message after receiving the non-terrestrial network security mode command message, and send the non-terrestrial network security mode complete message to the mobile communication module. The mobile communication module sends a non-access layer message to TN-CN through TN-RAN, and the non-access layer message includes an N1NTN Container, and the N1 NTN Container includes a non-terrestrial network security mode complete message. TN-CN sends the N1 NTN Container including the non-terrestrial network security mode complete message to NTN-CN. NTN-CN can determine that UE100 completes the security mode configuration based on the non-terrestrial network security mode complete message. In this way, NTN-CN notifies the NTN communication module of UE100 to perform security mode configuration through TN-CN, TN-RAN and the mobile communication module.

[0203] S408. NTN-CN sends an N1 NTN Container 36 including a non-terrestrial network registration accept message (NTN registrationaccept) 34 and a non-terrestrial network air interface capability request 35 to TN-CN.

[0204] After the identity authentication of UE100 is passed, the authentication is successful and the security mode configuration is successfully performed, NTN-CN can send a non-terrestrial network registration acceptance message 34 to TN-CN. The non-terrestrial network registration acceptance message 34 can indicate that the AMF 300 of NTN-CN accepts the registration request of UE100.

[0205] The NTN-CN may also send a non-terrestrial network air interface capability request 35 to the TN-CN. The non-terrestrial network air interface capability request 35 may be used to obtain NTN air interface capability information of the NTN communication module of the UE 100 when operating independently.

[0206] NTN-CN can add the non-terrestrial network registration acceptance message 34 and the non-terrestrial network air interface capability request 35 together in N1 NTN Container 36, and then send N1 NTN Container 36 to TN-CN. In some examples, NTN-CN and TN-CN can communicate through the N14 interface. Here, NTN-CN sends N1 NTNContainer 36 to TN-CN through the N14 interface.

[0207] In other examples, when UE100 registers with TN-CN, it may carry the non-terrestrial network registration request message 31 in the registration request message used to register with TN-CN. UE100 may perform steps S405 to S407 in the process of registering with TN-CN. TN-CN may carry the non-terrestrial network registration acceptance message 34 when sending a registration acceptance message to UE100 indicating that UE100 has passed the registration with TN-CN. In this way, UE100 may perform the steps of registering with NTN-CN through TN-RAN and TN-CN in the process of registering with TN-CN, thereby saving TN network air interface resources.

[0208] S409 . TN-CN sends a non-access layer message 37 to the mobile communication module of UE 100 via TN-RAN. The non-access layer message 37 includes an N1 NTN Container 38 . The N1 NTN Container 38 includes a non-terrestrial network registration acceptance message 34 .

[0209] TN-CN may parse N1 NTN Container 36 to obtain non-terrestrial network registration acceptance message 34 and non-terrestrial network air interface capability request 35. TN-CN may encapsulate non-terrestrial network registration acceptance message 34 to obtain N1 NTNContainer 38, and then encapsulate N1 NTN Container 38 to obtain non-access layer message 37. TN-CN may send non-access layer message 37 to TN-RAN. TN-RAN may send non-access layer message 37 to the mobile communication module.

[0210] S410. The mobile communication module sends the non-terrestrial network registration acceptance message 34 to the NTN communication module.

[0211] After receiving the non-access layer message 37, the mobile communication module can obtain the non-terrestrial network registration acceptance message 34 from the non-access layer message 37 and send the non-terrestrial network registration acceptance message 34 to the NTN communication module. The NTN communication module receives the non-terrestrial network registration acceptance message 34 and determines that the UE 100 is successfully registered with the NTN-CN.

[0212] In other examples, the mobile communication module can execute the process of the NTN communication module registering the non-terrestrial network during the process of registering the terrestrial network. Among them, the mobile communication module can send the registration request message of the non-terrestrial network of the NTN communication module to the TN-CN when sending the registration request message of the terrestrial network to the TN-CN, and the TN-CN can send the registration request message of the non-terrestrial network of the NTN communication module to the NTN-CN. When the TN-CN sends the registration completion message of the terrestrial network to the mobile communication module, the registration completion message of the non-terrestrial network of the NTN-CN is sent to the mobile communication module, and the mobile communication module can send the registration completion message of the non-terrestrial network to the NTN communication module. In this way, when the mobile communication module sends the signaling of the core network of the terrestrial network to the TN-CN, it can carry the signaling of the core network of the NTN communication module registering the non-terrestrial network, saving the signaling overhead. In the process of the mobile communication module registering the terrestrial network, the NTN communication module can register the non-terrestrial network through the mobile communication module and the TN-CN, and the NTN-CN can obtain the registration information of the NTN communication module. After UE100 searches for a wireless access network device of a non-terrestrial network, the NTN communication module can register to the non-terrestrial network without having to perform cumbersome identity authentication, authorization, and security mode command processes, saving time for registering the network and reducing the power consumption of UE100 in sending and receiving satellite data.

[0213] S411. TN-CN sends a radio resource control layer message 39 to the mobile communication module of UE100 through TN-RAN. The radio resource control layer message 39 includes a non-terrestrial network air interface capability request 35.

[0214] The TN-CN may encapsulate the non-terrestrial network air interface capability request 35 to obtain a radio resource control message 39, and then send the radio resource control message 39 to the TN-RAN. The TN-RAN may forward the radio resource control message 39 to the mobile communication module of the UE 100.

[0215] In other examples, the TN-CN may place the non-terrestrial network air interface capability request 35 in an N1 NTNContainer, then encapsulate the N1 NTN Container to obtain a radio resource control message 39, and send the radio resource control message 39 to the TN-RAN. The TN-RAN may forward the radio resource control message 39 to the mobile communication module of the UE 100. Alternatively, the TN-CN may encapsulate the N1 NTN Container to obtain a non-access layer message, and send the non-access layer message to the TN-RAN. The TN-RAN may forward the non-access layer message to the mobile communication module of the UE 100.

[0216] In other examples, the NTN-CN may send a non-terrestrial network air interface capability information request message (NTN capability info request) to the TN-CN. The TN-CN may forward the message to the TN-RAN. After receiving the message, the TN-RAN may send a user equipment capability query message to the NTN communication module through the mobile communication module.

[0217] Exemplarily, TN-CN may forward the non-terrestrial network air interface capability information request message to TN-RAN via NGAP. TN-RAN may generate a user equipment capability query message based on the non-terrestrial network air interface capability information request message. TN-RAN may add the user equipment capability query message to an RRC message and send the RRC message to UE100. For example, the RRC message includes an N1 NTN container, and the N1 NTN container includes a user equipment capability query message. The user equipment capability query message includes parameters for instructing UE100 to send NTN air interface capability information to TN-RAN. For example, the user equipment capability query message may be UE capability enquiry (NTN).

[0218] In other examples, the NTN-CN may send a non-terrestrial network air interface capability information request message to the TN-CN. After receiving the message, the TN-CN may send a user equipment capability query message to the TN-RAN. The TN-RAN may send the user equipment capability query message to the mobile communication module, and after receiving the message, the mobile communication module may execute step S412.

[0219] S412. The mobile communication module obtains the air interface capability information of the NTN communication module operating independently.

[0220] After receiving the non-terrestrial network air interface capability request 35, the mobile communication module can obtain the air interface capability information of the NTN communication module when it is independently running from the NTN communication module. Among them, the air interface capability information of the NTN communication module when it is independently running can be referred to as NTN air interface capability information. Among them, the NTN air interface capability information may include but is not limited to the carrier (band) supported by UE100, the user equipment category (UE Category) of UE100, the antenna polarization direction of UE100, the maximum transmit power (power level) of UE100, the duplex mode of UE100, etc.

[0221] S413 . The mobile communication module sends the radio resource control layer message 40 to the TN-CN via the TN-RAN. The radio resource control layer message 40 includes the non-terrestrial network user equipment capability message 41 .

[0222] The mobile communication module may generate a non-terrestrial network user equipment capability message 41 based on the NTN air interface capability information provided by the NTN communication module. The mobile communication module may encapsulate the non-terrestrial network user equipment capability message 41 to obtain a radio resource control layer message 40. The mobile communication module may send the radio resource control layer message 40 to the TN-RAN. The TN-RAN may send the radio resource control layer message 40 to the TN-CN.

[0223] S414. TN-CN sends N1 NTN Container 42 to NTN-CN. N1 NTN Container 42 includes non-terrestrial network user equipment capability indication message 43.

[0224] After receiving the radio resource control layer message 40, the TN-CN may parse the message to obtain a non-terrestrial network user equipment capability message 41. The TN-CN may generate a non-terrestrial network user equipment capability indication message 43 based on the non-terrestrial network user equipment capability message 41. The TN-CN may encapsulate the non-terrestrial network user equipment capability indication message 43 to obtain an N1 NTNContainer 42, and send the N1 NTN Container 42 to the NTN-CN. In some examples, the description of the non-terrestrial network user equipment capability message can be found in Figure 2 The description of the user equipment air interface capability information message shown in FIG. The description of the non-terrestrial network user equipment capability indication message can be found in Figure 2 Description of the user equipment air interface capability information indication message shown.

[0225] After receiving the N1 NTN Container 42, the NTN-CN can parse the non-terrestrial network user equipment capability indication message 43 to obtain the NTN air interface capability information of the NTN communication module of the UE 100. After the UE 100 is registered with the NTN-CN, the NTN-CN can allocate communication resources to the UE 100 based on the NTN air interface capability information of the UE 100.

[0226] In other examples, the mobile communication module may place the non-terrestrial network user equipment capability message 41 in the N1NTN Container, and then encapsulate the N1 NTN Container to obtain the wireless resource control layer message 40. The mobile communication module may send the wireless resource control layer message 40 to the TN-RAN. The TN-RAN may send the wireless resource control layer message 40 to the TN-CN. The TN-CN may obtain the non-terrestrial network user equipment capability message 41 based on the wireless resource control layer message 40, and then execute step S414 to send the NTN air interface capability information of the UE 100 to the NTN-CN. In this way, the TN-RAN may not need to parse the N1NTN Container, and may directly forward the N1 NTN Container to the TN-CN, thus saving transmission time.

[0227] In other examples, the mobile communication module can encapsulate the wireless resource control layer message 40 based on the non-terrestrial network user equipment capability message 41. The mobile communication module can send the wireless resource control layer message 40 to the TN-RAN. The TN-RAN can parse the wireless resource control layer message 40 to obtain the non-terrestrial network user equipment capability message 41. The TN-RAN can generate a non-terrestrial network user equipment capability indication message 43 based on the non-terrestrial network user equipment capability message 41. The TN-RAN can send the non-terrestrial network user equipment capability indication message 43 to the NTN-CN through the TN-CN, or the TN-RAN can send the non-terrestrial network user equipment capability indication message 43 directly to the NTN-CN. In this way, the message sent by the UE 100 to the NTN-CN can be processed by the TN-RAN, so that the TN-CN does not need to process the NTN-CN message.

[0228] In other examples, the mobile communication module may generate a non-terrestrial network user equipment capability indication message 43 based on the NTN air interface capability information. The mobile communication module may send the non-terrestrial network user equipment capability indication message 43 to the NTN-CN via the TN-RAN and the TN-CN, or the mobile communication module may send the non-terrestrial network user equipment capability indication message 43 to the NTN-CN via the TN-RAN,

[0229] It should be noted that the non-terrestrial network user equipment capability indication message 43 and the non-terrestrial network user equipment capability message 41 are only examples. The mobile communication module can use other signaling carrying the NTN air interface capability information of UE100 to send the NTN air interface capability information of UE100 to NTN-CN through TN-RAN and TN-CN. The embodiment of the present application is not limited to this.

[0230] In this way, through steps S408 to S414, NTN-CN can obtain the NTN air interface capability information of the NTN communication module of UE100 under TN. When UE100 registers with NTN-CN, UE100 does not need to transmit the NTN air interface capability information of UE100 under NTN, thereby saving air interface resources, time and power consumption for transmitting the NTN air interface capability information.

[0231] S415. UE100 searches for NTN, establishes a radio resource control connection with NTN-RAN, and sends a registration request message 44 to NTN-CN through NTN-RAN.

[0232] The UE 100 searching for NTN can be understood as receiving a signal from NTN. Exemplarily, the UE 100 can receive a signal sent by NTN-RAN (e.g., base station 200) based on the PLMN information stored in the NTN communication module. After receiving the signal sent by NTN-RAN, the UE 100 can establish an RRC connection with the NTN-RAN. For details, see Figure 2 The illustrated embodiments will not be described in detail here.

[0233] It should be noted that before UE100 searches for NTN, UE100 needs to perform a satellite alignment operation to align the antenna radiation direction of UE100 with the satellite transmission link direction of base station 200. UE100 can display a satellite alignment prompt message to prompt the user to align the antenna radiation direction of UE100 with the satellite transmission link direction of base station 200. After the satellite alignment is successful, UE100 can receive satellite signals with strong signal quality.

[0234] After UE100 establishes an RRC connection with NTN-RAN, the NTN communication module may send a registration request message 44 to NTN-CN through NTN-RAN, and the registration type of the registration request message 44 is mobility registration (mobility registration update). For example, the registration request message 44 may be expressed as registration request (mobility registration update). The registration request message 44 includes the identity of the NTN communication module.

[0235] NTN-CN can determine whether NTN-CN stores NTN air interface capability information of NTN communication module of UE100 based on the identity of NTN communication module. When NTN-CN determines that NTN air interface capability information of NTN communication module of UE100 is stored, step S416 can be executed. In this way, each device does not need to execute the steps of synchronizing NTN air interface capability information of UE100 as shown in steps S408-S414. NTN-CN can also synchronize NTN air interface capability information of UE100 to NTN-RAN.

[0236] When the NTN-CN determines that the NTN air interface capability information of the NTN communication module of the UE 100 is not stored, step S417 may be executed to obtain the NTN air interface capability information of the UE 100 through the NTN-RAN.

[0237] S416. NTN-CN sends an initial context setup request message 45 and a registration acceptance message 46 carrying the NTN air interface capability information of UE 100 to NTN-RAN.

[0238] After receiving the registration request message 44 sent by the UE 100, the NTN-CN determines the registration context and NTN air interface capability information of the NTN communication module of the UE 100 based on the identity of the NTN communication module. The NTN-CN may send a registration acceptance message 46 to the UE 100. After receiving the registration acceptance message 46, the NTN-RAN may forward the registration acceptance message 46 to the UE 100. The registration acceptance message 46 may be used to notify the UE 100 that the registration with the NTN-CN is successful.

[0239] NTN-CN may also send an initial context setup request message 45 to NTN-RAN. After receiving the initial context setup request message 45, NTN-RAN may parse the message and obtain the NTN air interface capability information of UE100. In this way, NTN-RAN obtains the NTN air interface capability information of UE100. NTN-RAN may configure relevant parameters based on the NTN air interface capability information of UE100 to provide appropriate communication resources to UE100. In some examples, NTN-CN may send the initial context setup request message 45 through the NGAP air interface. It should be noted that the initial context setup request message 45 is only an example, and NTN-CN may also send the NTN air interface capability information of UE100 to NTN-RAN through other signaling carrying the NTN air interface capability information of UE100. For example, NTN-CN may send signaling used only for transmitting the NTN air interface capability information of UE100 to send the NTN air interface capability information of UE100 to NTN-RAN, and the embodiments of the present application are not limited to this.

[0240] S417 . NTN-CN sends an initial context setup request message 47 and a registration acceptance message 48 to NTN-RAN without carrying the NTN air interface capability information of UE 100 .

[0241] After receiving the registration request message 44 sent by UE 100, NTN-CN determines the registration context of the NTN communication module of UE 100 based on the identity of the NTN communication module. NTN-CN can send a registration acceptance message 48 to NTN-RAN. NTN-RAN can send the registration acceptance message 48 to UE 100. The registration acceptance message 48 can be used to notify UE 100 that the registration with NTN-CN is successful.

[0242] After receiving the registration request message 44 sent by the UE 100, the NTN-CN determines that the NTN air interface capability information of the NTN communication module of the UE 100 is not stored based on the identity of the NTN communication module. The NTN-CN may send an initial context setup request message 47 to the NTN-RAN. After receiving the initial context setup request message 47, the NTN-RAN may parse the message, determine that the initial context setup request message 47 does not include the NTN air interface capability information of the UE 100, and may execute step S418.

[0243] S418. NTN-RAN obtains the NTN air interface capability information of UE 100, and sends the NTN air interface capability information of UE 100 to NTN-CN.

[0244] The description of NTN-RAN obtaining the NTN air interface capability information of UE100 and synchronizing the NTN air interface capability information of UE100 with NTN-CN can be found in Figure 2 The description of steps S222 to S224 is not repeated here.

[0245] In this way, the NTN-CN can obtain the NTN air interface capability information of the UE 100 under the TN.

[0246] In some examples, after NTN-CN obtains the NTN air interface capability information of UE100, the capability of UE100 changes. The NTN communication module of UE100 can send a notification message indicating the update of the NTN air interface capability information of UE100 to NTN-CN through the mobile communication module, TN-RAN and TN-CN. NTN-CN can delete the saved NTN air interface capability information of UE100. NTN-CN can also obtain the updated NTN air interface capability information from UE100 through TN-CN, TN-RAN and mobile communication module. NTN-CN can also send the NTN air interface capability information of UE100 to NTN-RAN after receiving the registration request message sent by UE100 through NTN-RAN. In this way, UE100 can notify NTN-CN after the capability changes. After receiving the message of the capability change of UE100, NTN-CN can re-acquire the updated NTN air interface capability information of UE100 to ensure the reliability of the stored NTN air interface capability information of UE100.

[0247] For example, Figure 5 As shown, the UE100 capability change process includes the following steps:

[0248] S501. NTN communication module capability changes.

[0249] After the capability is changed, the NTN communication module may notify the NTN-CN of the capability change of the UE 100 through the mobile communication module, the TN-RAN and the TN-CN.

[0250] S502. The NTN communication module sends a user equipment capability release command message 51 to the mobile communication module.

[0251] Among them, although UE100 establishes a communication connection with TN-CN and is in a connected state, UE100 does not need to change the NTN air interface capability information stored in TN-CN, so UE100 does not need to release the connected state.

[0252] The user equipment capability release command message 51 may be used to notify the NTN-CN of the capability change of the UE 100 .

[0253] S503 . The mobile communication module sends a non-access layer message 52 to the TN-CN via the TN-RAN. The non-access layer message 52 includes an N1 NTN Container 53 . The N1 NTN Container 53 includes a user equipment capability release command message 51 .

[0254] After receiving the user equipment capability release command message 51 sent by the NTN communication module, the mobile communication module may encapsulate the user equipment capability release command message 51 to obtain an N1 NTN Container 53. The mobile communication module may also encapsulate the N1 NTN Container 53 to obtain a non-access layer message 52.

[0255] S504. TN-CN sends N1 NTN Container53 to NTN-CN.

[0256] After receiving the non-access layer message 52, the TN-CN may parse the message to obtain the N1 NTN Container 53, and send the N1 NTN Container 53 to the NTN-CN.

[0257] S505 . NTN-CN sends N1 NTN Container 54 to TN-CN. N1 NTN Container 54 includes non-terrestrial network air interface capability request 55 .

[0258] After receiving N1 NTN Container 53, NTN-CN may parse N1 NTN Container 53 to obtain the user equipment capability release command message 51. NTN-CN may delete the NTN air interface capability information of UE 100, and send N1 NTN Container 54 including the non-terrestrial network air interface capability request 55 to TN-CN. The non-terrestrial network air interface capability request 55 is used to obtain the NTN air interface capability information of UE 100.

[0259] In other examples, the NTN communication module may send a registration request message with a registration type of mobility registration to the mobile communication module. The registration request message is used to indicate the change of the NTN air interface capability of UE100. The mobile communication module may send the registration request message to TN-RAN. TN-RAN may generate a user equipment capability release command message based on the registration request message. TN-RAN may send the user equipment capability release command message to TN-CN, and TN-CN may send the message to NTN-CN. Alternatively, TN-RAN may send the user equipment capability release command message to NTN-CN. In this way, TN-RAN may send a message indicating the change of the NTN air interface capability of UE100 to NTN-CN.

[0260] In other examples, the NTN communication module may send a registration request message with a registration type of mobility registration to the mobile communication module. The mobile communication module may send the registration request message to the TN-CN through the TN-RAN. The TN-CN may generate a user equipment capability release command message based on the registration request message. The TN-CN may send the message to the NTN-CN.

[0261] S506 . TN-CN sends a non-access layer message 56 to the mobile communication module via TN-RAN. The non-access layer message 56 includes an N1 NTN Container 54 .

[0262] After receiving the N1 NTN Container 54 , the TN-CN may encapsulate the N1 NTN Container 54 to obtain a non-access layer message 56 , and send the non-access layer message 56 to the mobile communication module through the TN-RAN.

[0263] In other examples, TN-CN can place the non-terrestrial network air interface capability request 55 in N1 NTNContainer, encapsulate the N1NTN Container to obtain a radio resource control message, and send the radio resource control message to TN-RAN. TN-RAN can forward the radio resource control message to the mobile communication module of UE100.

[0264] In other examples, after determining that the NTN air interface capability of UE100 has changed, NTN-CN may send a non-terrestrial network air interface capability information request message to TN-CN. TN-CN may forward the message to TN-RAN. After receiving the message, TN-RAN may send a user equipment capability query message to the mobile communication module. For details, see Figure 4 The illustrated embodiments will not be described in detail here.

[0265] In other examples, the NTN-CN may send a non-terrestrial network air interface capability information request message to the TN-CN. After receiving the message, the TN-CN may send a user equipment capability query message to the TN-RAN. The TN-RAN may send the user equipment capability query message to the mobile communication module, and after receiving the message, the mobile communication module may execute step S507.

[0266] S507. The mobile communication module obtains the NTN air interface capability information of the NTN communication module operating independently.

[0267] The description of S507 can be found in Figure 4 The description of step S412 is not repeated here.

[0268] S508 . The mobile communication module sends the non-access layer message 57 to the TN-CN via the TN-RAN. The non-access layer message 57 includes an N1 NTN Container 58 . The N1 NTN Container 58 includes a non-terrestrial network user equipment capability message 59 .

[0269] After acquiring the NTN air interface capability information of the NTN communication module operating independently, the mobile communication module can generate a non-terrestrial network user equipment capability message 59 based on the NTN air interface capability information. The mobile communication module can also encapsulate the non-terrestrial network user equipment capability message 59 to obtain an N1 NTN Container 58, and then encapsulate the N1 NTN Container 58 to obtain a non-access layer message 57. The mobile communication module can send the non-access layer message 57 to the TN-CN through the TN-RAN. The description of step 508 can also be found in Figure 4 The description of step S413 is not repeated here.

[0270] S509 . TN-CN sends N1 NTN Container 60 to NTN-CN. N1 NTN Container 60 includes non-terrestrial network user equipment capability indication message 61 .

[0271] The non-terrestrial network user equipment capability indication message 61 may include the NTN air interface capability information of the UE 100. The NTN-CN device may acquire the NTN air interface capability information of the UE 100 based on the message.

[0272] S510. UE100 searches for NTN, establishes a radio resource control connection with NTN-RAN, and sends a registration request message 62 to NTN-CN through NTN-RAN.

[0273] The NTN-CN may determine, based on the identity of the NTN communication module, whether the NTN-CN stores the NTN air interface capability information of the NTN communication module of the UE 100. When the NTN-CN determines that the NTN air interface capability information of the NTN communication module of the UE 100 is stored, step S511 may be executed. When the NTN-CN determines that the NTN air interface capability information of the NTN communication module of the UE 100 is not stored, step S512 may be executed.

[0274] S511. NTN-CN sends an initial context setup request message 63 and a registration acceptance message 64 carrying the NTN air interface capability information of UE 100 to NTN-RAN.

[0275] S512 . NTN-CN sends an initial context setup request message 65 and a registration acceptance message 66 to NTN-RAN without carrying the NTN air interface capability information of UE 100 .

[0276] S513. NTN-RAN obtains the NTN air interface capability information of UE100, and sends the NTN air interface capability information of UE100 to NTN-CN.

[0277] The description of steps S509 to S513 can be found in Figure 4 The description of steps S414 to S418 is not repeated here.

[0278] In this way, when UE100 changes the capability of UE100 when the NTN communication module is running independently under TN, it can be done by Figure 5 The steps shown synchronize the updated NTN air interface capability information of UE 100 to NTN-CN.

[0279] In one possible implementation, the NTN communication module can perform the registration process of the core network of the non-terrestrial network through the mobile communication module and the wireless access network of the terrestrial network. The NTN communication module can also send the NTN air interface capability information of the UE to the core network of the non-terrestrial network through the mobile communication module and the wireless access network of the terrestrial network. In this way, UE100 can transmit signaling to NTN-CN through TN-RAN under the terrestrial network, and receive signaling sent by NTN-CN through TN-RAN. UE100 and NTN-CN do not need to be relayed through TN-CN, and can implement the signaling interaction process through TN-RAN, saving the time required to transmit signaling.

[0280] For example, Figure 6 As shown, the capability synchronization method includes the following steps:

[0281] S601. The mobile communication module of UE100 receives the non-terrestrial network registration request message 71 from the NTN communication module.

[0282] For details, see Figure 4 The description of step S401 is not repeated here.

[0283] S602 . The mobile communication module of UE 100 sends a non-access stratum message 72 to NTN-CN via TN-RAN. The non-access stratum message 72 includes an N1 NTN Container 73 . The N1 NTN Container 73 includes a non-terrestrial network registration request message 71 .

[0284] Exemplarily, the non-access layer message 72 may be expressed as NAS message 72 (N1 NTN Container 73 (NTN registration request 71 (initial registration))). Figure 4 Compared with step S403 and step S404 shown, UE 100 may not need TN-CN for transit, but only send the non-access stratum message 72 to NTN-CN through TN-RAN.

[0285] S603. NTN-CN obtains the identity of the NTN communication module.

[0286] NTN-CN can obtain the identity of the NTN communication module through TN-RAN and the mobile communication module. Here, the identity of the NTN communication module is the SIM2 identity.

[0287] Exemplarily, NTN-CN may send a non-access layer message to the mobile communication module of UE100 through TN-RAN. The non-access layer message includes an N1 NTN Container, and the N1 NTN Container includes a non-terrestrial network identity request message. The non-terrestrial network identity request message is used to obtain the identity of the NTN communication module of UE100. The mobile communication module of UE100 sends a non-terrestrial network identity request message to the NTN communication module of UE100.

[0288] After receiving the non-terrestrial network identity request message, the NTN communication module can generate a non-terrestrial network identity response message based on the identity of the NTN communication module, and send the non-terrestrial network identity response message to the mobile communication module. The mobile communication module sends a non-access layer message to the NTN-CN through the TN-RAN. The non-access layer message includes an N1 NTNContainer, and the N1 NTN Container includes the non-terrestrial network identity response message. In this way, the NTN-CN obtains the identity of the NTN communication module of the UE100 through the TN-RAN and the mobile communication module. Figure 4 Compared with step S405 shown in the figure, the resources consumed by NTN-CN for transit are reduced.

[0289] S604. NTN-CN authenticates SIM2 bound to the NTN communication module.

[0290] Exemplarily, NTN-CN may send a non-access layer message to the mobile communication module of UE100 through TN-RAN. The non-access layer message includes N1 NTN Container, and the N1 NTN Container includes a non-terrestrial network authentication request message. The non-terrestrial network authentication request message is used to authenticate SIM2 bound to the NTN communication module of UE100. The mobile communication module of UE100 sends a non-terrestrial network authentication request message to the NTN communication module of UE100.

[0291] After receiving the non-terrestrial network authentication request message, the NTN communication module can calculate the authentication parameters of SIM2 and the authentication parameters of the non-terrestrial network authentication request message through an authentication algorithm to obtain an authentication response, and generate a non-terrestrial network authentication response message based on the authentication response. The NTN communication module sends the non-terrestrial network authentication response message to the mobile communication module. The mobile communication module sends a non-access layer message to NTN-CN through TN-RAN. The non-access layer message includes N1 NTNContainer, and the N1 NTN Container includes the non-terrestrial network authentication response message. NTN-CN can determine whether UE100 has passed the authentication based on the authentication response of the non-terrestrial network authentication response message. Here, NTN-CN authenticates UE100. In this way, NTN-CN authenticates SIM2 bound to the NTN communication module of UE100 through TN-RAN and the mobile communication module. Figure 4 Compared with step S406 shown in the figure, the resources consumed by NTN-CN for transit are reduced.

[0292] S605. NTN-CN notifies the NTN communication module to configure the security mode.

[0293] Exemplarily, NTN-CN may send a non-access layer message to the mobile communication module of UE100 through TN-RAN. The non-access layer message includes an N1 NTN Container, and the N1 NTN Container includes a non-terrestrial network security mode command message. The non-terrestrial network security mode command message is used to notify the NTN communication module of UE100 to configure the security mode. The mobile communication module of UE100 sends a non-terrestrial network security mode command message to the NTN communication module of UE100.

[0294] After receiving the non-terrestrial network security mode command message, the NTN communication module can determine the encryption algorithm and the integrity algorithm. UE100 can process the uplink data sent to NTN-CN by using the obtained encryption algorithm and integrity algorithm. The NTN communication module can also generate a non-terrestrial network security mode complete (NTN security mode complete) message after receiving the non-terrestrial network security mode command message, and send the non-terrestrial network security mode complete message to the mobile communication module. The mobile communication module sends a non-access stratum message to NTN-CN through TN-RAN. The non-access stratum message includes an N1 NTN Container, and the N1 NTN Container includes a non-terrestrial network security mode complete message. NTN-CN can determine that UE100 has completed the security mode configuration based on the non-terrestrial network security mode completion message. In this way, NTN-CN notifies the NTN communication module of UE100 through TN-RAN and the mobile communication module to perform security mode configuration. Figure 4 Compared with step S406 shown in the figure, the resources consumed by NTN-CN for transit are reduced.

[0295] S606 . NTN-CN sends a non-access stratum message 74 to TN-RAN. The non-access stratum message 74 includes an N1 NTNContainer 75 . The N1NTN Container 75 includes a non-terrestrial network registration acceptance message 76 .

[0296] S607 . TN-RAN sends a non-access layer message 74 to the mobile communication module of UE 100 .

[0297] After the identity authentication of UE100 is passed, the authentication is successful and the security mode configuration is successfully performed, NTN-CN can send a non-terrestrial network registration acceptance message 76 to the mobile communication module through TN-RAN. The non-terrestrial network registration acceptance message 76 can indicate that NTN-CN accepts the registration request of UE100.

[0298] S608. The mobile communication module sends a non-terrestrial network registration acceptance message 76 to the NTN communication module.

[0299] S609. NTN-CN sends a radio resource control layer message 77 including a non-terrestrial network air interface capability request 78 to the mobile communication module of UE100 via TN-RAN.

[0300] NTN-CN can also send a radio resource control layer message 77 including a non-terrestrial network air interface capability request 78 to the mobile communication module through TN-RAN. The non-terrestrial network air interface capability request 78 can be used to obtain the NTN air interface capability information of the NTN communication module of UE100 when it is running independently. Exemplarily, NTN-CN can place the non-terrestrial network air interface capability request 78 in an N1 NTN Container, and then encapsulate the N1 NTN Container to obtain the radio resource control message 77.

[0301] In other examples, NTN-CN may send a NAS message including the non-terrestrial network air interface capability request 78 to TN-RAN. Exemplarily, NTN-CN may place the non-terrestrial network air interface capability request 78 in an N1 NTN Container, and then encapsulate the N1 NTN Container to obtain a NAS message. TN-RAN may encapsulate the NAS message to obtain an RRC message, and then send the RRC message to the mobile communication module of UE100.

[0302] In other examples, NTN-CN may send a non-terrestrial network air interface capability information request message to TN-RAN. After receiving the message, TN-RAN may send a user equipment capability query message to the NTN communication module through the mobile communication module. The user equipment capability query message includes a parameter for instructing UE100 to send NTN air interface capability information to TN-RAN.

[0303] Exemplarily, NTN-CN may forward the non-terrestrial network air interface capability information request message to TN-RAN via NGAP. TN-RAN may generate a user equipment capability query message based on the non-terrestrial network air interface capability information request message. NTN-RAN may add the user equipment capability query message to an RRC message and send the RRC message to UE 100. For example, the RRC message includes an N1NTN container, and the N1 NTN container includes the user equipment capability query message. For example, the user equipment capability query message may be UE capability enquiry (NTN).

[0304] In some examples, the NTN-CN may place the non-terrestrial network registration acceptance message 76 and the non-terrestrial network air interface capability request 78 in the same NAS message and send the NAS message to the TN-RAN. The TN-RAN may obtain an RRC message 84 based on the non-terrestrial network registration acceptance message 76 and send the RRC message 84 to the UE 100. The TN-RAN may also obtain an RRC message 85 based on the non-terrestrial network air interface capability request 78 and send the RRC message 85 to the UE 100.

[0305] S610. The mobile communication module obtains the air interface capability information of the NTN communication module operating independently.

[0306] For details, see Figure 4 The illustrated embodiments will not be described in detail here.

[0307] S611. The mobile communication module sends the radio resource control layer message 79 to NTN-CN via TN-RAN. The radio resource control layer message 79 includes the non-terrestrial network user equipment capability message 80.

[0308] For example, the mobile communication module may generate a non-terrestrial network user equipment capability message 80 based on the NTN air interface capability information provided by the NTN communication module. The mobile communication module may encapsulate the non-terrestrial network user equipment capability message 80 to obtain a radio resource control layer message 79. The mobile communication module may send the radio resource control layer message 79 to the TN-RAN. The TN-RAN may send the radio resource control layer message 79 to the NTN-CN. Optionally, the mobile communication module may encapsulate the non-terrestrial network user equipment capability message 80 to obtain a NAS message, and then encapsulate the NAS message to obtain the radio resource control layer message 79. The TN-RAN may send the NAS message to the NTN-CN.

[0309] In some examples, the mobile communication module may send the non-terrestrial network user equipment capability message 80 to the TN-RAN. The TN-RAN may generate a non-terrestrial network user equipment capability indication message based on the non-terrestrial network user equipment capability message 80. The TN-RAN may send the non-terrestrial network user equipment capability indication message to the NTN-CN. The description of the mobile communication module sending the message to the TN-RAN can be found in Figure 4 The embodiment shown is not described in detail here. The description of TN-RAN sending a message to NTN-CN can be found in Figure 4 For a description of the message sent by TN-RAN to TN-CN, see Figure 4 The description of TN-CN sending a message to NTN-CN is not repeated here.

[0310] It should be noted that the non-terrestrial network user equipment capability indication message and the non-terrestrial network user equipment capability message 80 are only examples. The mobile communication module can use other signaling carrying the NTN air interface capability information of UE100 to send the NTN air interface capability information of UE100 to NTN-CN through TN-RAN. The embodiment of the present application is not limited to this.

[0311] S612. UE100 searches for NTN, establishes a radio resource control connection with NTN-RAN, and sends a registration request message 81 to NTN-CN through NTN-RAN.

[0312] S613. NTN-CN sends an initial context setup request message 82 and a registration acceptance message 83 carrying the NTN air interface capability information of UE 100 to NTN-RAN.

[0313] The description of step S612 and step S613 can be found in Figure 4 In this way, the UE 100 and the NTN-CN do not need to be relayed through the TN-CN, and the signaling interaction process can be implemented through the TN-RAN, saving the time required for transmitting the signaling.

[0314] In a possible implementation, UE100 includes SIM3. UE100 can use TN's communication services through SIM3 and can use NTN's roaming services. When registering the TN network, UE100 can send SIM3's NTN capability information to TN-CN, and TN-CN can send an equivalent public land mobile network (EPLMN) list of NTN PLMN to UE100. After receiving the list, UE100 can send an air interface capability change message to TN-CN. The air interface capability change message can be used to trigger TN-CN to obtain UE100's NTN air interface capability information. UE100 can search for NTN based on the EPLMN list and send a registration request message to NTN-CN. After receiving the registration request message of UE100, NTN-CN can obtain UE100's registration context and UE100's NTN air interface capability information from TN-CN. NTN-CN can send UE100's NTN air interface capability information to NTN-RAN. In this way, UE100 can send the NTN air interface capability information of UE100 to TN-CN under TN. When NTN-CN receives the registration request message of UE100, it can obtain the registration context of UE100 and the NTN air interface capability information of UE100 from TN-CN, saving the air interface resources of NTN.

[0315] In some examples, the air interface capability change message includes parameters for indicating that the NTN air interface capability of the UE 100 has changed. For example, the air interface capability change message may be a registration request message whose registration type is mobility registration, a user equipment capability release command message, and the like.

[0316] For example, Figure 7 As shown, the capability synchronization method provided in the embodiment of the present application includes the following steps:

[0317] S701. UE100 sends a registration request message 91 to TN-CN via TN-RAN. Registration request message 91 includes network capability information of SIM3 of UE100, indicating that UE100 supports NTN communication.

[0318] When UE100 sends a registration request message 91 to TN-CN, it may carry the network capability information of UE100, and the network capability information may be used to indicate that UE100 supports access to NTN-CN. UE100 may send the registration request message 91 to TN-CN through a mobile communication module. The registration request message 91 is used for UE100 to register with TN-CN.

[0319] S702. TN-CN determines an equivalent public land mobile network EPLMN list of the non-terrestrial network public land mobile network NTN PLMN of UE 100.

[0320] TN-CN and NTN-CN have reached a roaming agreement, and TN-CN stores the EPLMN list of NTN-CN. After receiving the registration request message 91 sent by UE100, TN-CN determines that UE100 has the ability to communicate with NTN, determines the EPLMN list of the NTN PLMN of SIM3 of UE100 and sends it to UE100. The EPLMN list is used to represent the EPLMN of NTN of SIM3.

[0321] S703. TN-CN sends a registration acceptance message 92 to UE 100 via TN-RAN. Registration acceptance message 92 includes an EPLMN list.

[0322] TN-CN can add the EPLMN list to the registration acceptance message 92, and send the registration acceptance message 92 to UE100 through TN-RAN. It should be noted that between step S701 and step S703, UE100 and TN-CN also perform steps such as obtaining identity identification and authentication to register with the network. For details, the specific description of UE100 registering with TN-CN can be found in Figure 2 The illustrated embodiments will not be described in detail here.

[0323] S704. UE100 sends a registration request message 93 of a registration type of mobility registration to TN-CN via TN-RAN. The registration request message 93 includes a parameter for indicating that the NTN air interface capability of UE100 has changed.

[0324] For example, the description of the registration request message 93 can be found in Figure 3 The description of step S304 is not repeated here.

[0325] S705. TN-CN sends a non-terrestrial network air interface capability request 94 to UE 100 via TN-RAN.

[0326] The non-terrestrial network air interface capability request 94 may be used by the TN-CN to obtain the NTN air interface capability information of the UE 100 .

[0327] In some examples, the TN-CN may add the non-terrestrial network air interface capability request 94 to the N1 NTNContainer, then encapsulate the N1NTN Container to obtain a non-access layer message, and finally send the non-access layer message through the TN-RAN to the UE 100. Alternatively, the TN-CN may encapsulate the N1 NTN Container to obtain a radio resource control layer message, and finally send the radio resource control layer message to the UE 100 through the TN-RAN.

[0328] In some other examples, the TN-CN may send a non-terrestrial network air interface capability information request to the TN-RAN. After receiving the message, the TN-RAN may send a user equipment capability query message to the NTN communication module via the mobile communication module.

[0329] Exemplarily, the TN-CN may send a non-terrestrial network air interface capability information request to the TN-RAN via NGAP. The TN-RAN may add a user equipment capability query message to an RRC message and send the RRC message to the UE 100. For example, the RRC message includes an N1 NTN container, and the N1 NTN container includes a user equipment capability query message. The user equipment capability query message includes a parameter for instructing the UE 100 to send NTN air interface capability information to the TN-RAN. For example, the user equipment capability query message may be a UE capability enquiry (NTN).

[0330] It should be noted that the above signaling is only an example. TN-CN, TN-RAN and UE100 can synchronize the NTN air interface capability information of UE100 through other signaling with the same function. For example, TN-CN can send a non-terrestrial network air interface capability information request to UE100 through TN-RAN to obtain the NTN air interface capability information of UE100.

[0331] S706. UE 100 sends a non-terrestrial network user equipment capability message 95 to TN-CN via TN-RAN.

[0332] After receiving the non-terrestrial network air interface capability request 94, the UE 100 may generate a non-terrestrial network user equipment capability message 95 based on the NTN air interface capability information. The UE 100 may send the non-terrestrial network user equipment capability message 95 to the TN-CN via the TN-RAN.

[0333] After receiving the non-terrestrial network user equipment capability message 95 , the TN-CN may save the identifier of the UE 100 and the NTN air interface capability information of the UE 100 .

[0334] In some examples, UE100 can add the non-terrestrial network air interface capability message 95 to the N1 NTNContainer, then encapsulate the N1NTN Container to obtain a non-access layer message, and finally send the non-access layer message to the TN-CN through the TN-RAN. Alternatively, UE100 can encapsulate the N1 NTN Container to obtain a radio resource control layer message, and finally send the radio resource control layer message to the TN-CN through the TN-RAN.

[0335] In other examples, UE100 may send a non-terrestrial network user equipment capability message 95 to TN-RAN. After receiving the non-terrestrial network user equipment capability message 95, TN-RAN may send a non-terrestrial network user equipment capability indication message to TN-CN, and the non-terrestrial network user equipment capability indication message is used for TN-RAN to synchronize the NTN air interface capability information of UE100 to TN-CN.

[0336] Exemplarily, UE100 can add the non-terrestrial network user equipment capability message 95 to the N1 NTNContainer, then encapsulate the N1NTN Container to obtain an RRC message, and finally send the RRC message to the TN-RAN. The TN-RAN can generate a non-terrestrial network user equipment capability indication message based on the non-terrestrial network user equipment capability message 95, then add the non-terrestrial network user equipment capability indication message to the N1 NTN Container, and send the N1 NTN Container to the TN-CN.

[0337] It should be noted that the non-terrestrial network user equipment capability message is only an example, and UE100 may also send the NTN air interface capability information of UE100 to TN-CN through other signaling. For example, UE100 may send a non-terrestrial network user equipment capability indication message to TN-CN through TN-RAN to synchronize the NTN air interface capability information of UE100. For another example, UE100 may send a non-terrestrial network user equipment capability message to TN-CN through TN-RAN to synchronize the NTN air interface capability information of UE100, which is not limited in the embodiments of the present application.

[0338] S707. UE 100 searches for NTN-RAN based on EPLMN.

[0339] UE100 can search NTN-RAN based on EPLMN. UE100 can also establish an RRC connection with NTN-RAN. For details, please refer to Figure 2 The illustrated embodiment will not be described in detail here. It should be noted that, in order for the UE 100 to receive high-quality NTN signals, the UE 100 may perform a satellite alignment operation before executing step S707.

[0340] S708. UE 100 sends a registration request message 96 to NTN-CN via NTN-RAN. The registration type of the registration request message 96 is mobility registration.

[0341] UE100 can send a registration request message 96 of a registration type of mobility registration to NTN-CN through NTN-RAN. The registration request message 96 includes an identifier of UE100, which is used to prompt NTN-CN to obtain the registration context of UE100 and the NTN air interface capability information of UE100 from TN-CN. Among them, the identifier of UE100 can be a SIM3 identifier, for example, the SUCI of SIM3. For example, the registration request message 96 can be a registration request (mobility registration update). Among them, the mobile communication module and the NTN communication module of UE100 are both bound to SIM3. UE100 can send a registration request message 96 to NTN-RAN through the NTN communication module, and NTN-RAN can send the registration request message 96 to NTN-CN.

[0342] S709. NTN-CN obtains the registration context of UE 100 and NTN air interface capability information from TN-CN.

[0343] After receiving the registration request message 96, NTN-CN can obtain the registration context of UE100 and NTN air interface capability information from TN-CN. The registration context of UE100 can be used to indicate whether UE100 has been authenticated, encrypted data, etc. NTN air interface capability information can be used to indicate the air interface transmission capability of UE100. For example, the registration context of UE100 may include but is not limited to the paging capability information of UE100, the aggregate maximum bit rate (AMBR) of UE100, the authentication information of UE100, the security mode configuration of UE100, etc. Among them, NTN-CN can ensure the integrity and security of data transmitted with UE100 according to the security mode configuration information of UE100. In this way, UE100 does not need to perform authentication, security mode configuration and other steps during the process of registering with NTN-CN, thereby reducing the registration time. For example, the NTN air interface capability information of UE100 may include but is not limited to the carriers supported by UE100, the user equipment level of UE100, the antenna polarization direction of UE100, the maximum transmit power (power level) of UE100, the duplex mode of UE100, etc. In this way, NTN-CN does not need to obtain the NTN air interface capability information of UE100 through NTN-RAN, saving the air interface resources of NTN and reducing the time for synchronizing the NTN air interface capability information of UE100 between UE100 and NTN-CN.

[0344] In other examples, the TN-CN may place the NTN air interface capability information in the registration context, and then send the registration context of the UE 100 to the NTN-CN. In this way, the registration context of the UE 100 may include the NTN air interface capability information of the UE 100, and the TN-CN may send the data required by the NTN-CN to the NTN-CN through only one signaling.

[0345] S710. NTN-CN sends an initial context setup request message 97 and a registration acceptance message 98 carrying NTN air interface capability information to UE 100 through NTN-RAN.

[0346] After obtaining the registration context and NTN air interface capability information of UE100, NTN-CN can send an initial context setup request message 97 and a registration acceptance message 98 carrying the NTN air interface capability information of UE100 to UE100 through NTN-RAN. The registration acceptance message 98 is used to indicate that UE100 has successfully registered with NTN-CN. NTN-RAN can send the registration acceptance message 98 to UE100.

[0347] After receiving the initial context setup request message 97, the NTN-RAN may parse the message to obtain the NTN air interface capability information of the UE 100. It should be noted that the initial context setup request message 97 is only an example, and the NTN-CN may also send the NTN air interface capability information of the UE 100 to the NTN-RAN through other signaling. For example, the UE 100 may send a signaling only for transmitting the NTN air interface capability information of the UE 100 to send the NTN air interface capability information of the UE 100 to the NTN-RAN.

[0348] It should be noted that if NTN-CN does not obtain the NTN air interface capability information of UE100 from TN-CN, NTN-CN can send an initial context setup request message of NGAP that does not carry the NTN air interface capability information of UE100 to NTN-RAN. NTN-RAN receives the message and determines that the message does not include the NTN air interface capability information of UE100, and can obtain the NTN air interface capability information of UE100 and send the NTN air interface capability information to NTN-CN. For details, please refer to Figure 4 The description of step S417 and step S419 is not repeated here.

[0349] In this way, UE 100 can access NTN-CN in a roaming manner, and does not need to perform the NTN air interface capability synchronization process under NTN, thereby saving air interface resources, device power consumption, and time spent on transmitting NTN air interface capability information.

[0350] Optionally, TN-CN may send a non-terrestrial network air interface capability request to UE 100 through NTN-RAN when sending a registration acceptance message including the EMPLN list of NTN PLMN to UE 100 through NTN-RAN. In this way, UE 100 does not need to send a registration request message with a registration type of mobility registration to trigger TN-CN to send the non-terrestrial network air interface capability request, thereby saving signaling overhead.

[0351] In a possible implementation, UE100 accesses a registration server on the Internet through WLAN. UE100 can transmit the signaling used for UE100 to register with NTN-CN and UE100's NTN air interface capability information to NTN-CN through the registration server, so as to realize UE100 registration with NTN-CN. After UE100 accesses NTN-CN, NTN-CN does not need to obtain the NTN air interface capability information of UE100, and synchronizes the NTN air interface capability information of UE100 to NTN-RAN. For details, please refer to Figure 3 or Figure 5In this way, since the NTN-CN obtains the NTN air interface capability information of the UE 100 through the WLAN, the NTN-CN does not need to obtain the NTN air interface capability information of the UE 100 through the NTN-RAN.

[0352] In a possible implementation, UE100 includes SIM6. UE100 can use the communication services of TN1 through SIM6, and can use the roaming services of TN2. When UE100 registers with the TN1 network, it can send the air interface capability information of SIM6 under TN2 to the CN of TN1, and the CN of TN1 can send the EPLMN list of TN2 to UE100. UE100 can search for TN2 based on the EPLMN list, and send a registration request message to the CN of TN2. After receiving the registration request message of UE100, the CN of TN2 can obtain the registration context of UE100 and the air interface capability information under TN2 from the CN of TN1. In this way, UE100 can roam to access TN2 without executing the air interface capability information process of TN2 under TN2, saving the time for the CN of TN2 to obtain the air interface capability information of UE100.

[0353] The electronic device provided by the embodiments of the present application is introduced below.

[0354] UE100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device and / or a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the electronic device.

[0355] Figure 8 A schematic structural diagram of UE 100 is shown.

[0356] UE 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0357] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on UE 100. In other embodiments of the present application, UE 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0358] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0359] The controller may be the nerve center and command center of the UE 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0360] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0361] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0362] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only for illustrative purposes and does not constitute a structural limitation on UE 100. In other embodiments of the present application, UE 100 may also adopt different interface connection modes in the above embodiments, or a combination of multiple interface connection modes.

[0363] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the UE 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0364] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0365] The wireless communication function of UE 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0366] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in UE100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0367] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied on UE100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0368] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0369] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), non-terrestrial network communication modules, etc., which are applied to UE100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through antenna 2.

[0370] Among them, the non-terrestrial network communication module (NTN communication module) can be used to process the signal sent by UE100 to NTN. The non-terrestrial network communication module can also be used to process the signal from NTN. In the embodiment of the present application, the non-terrestrial network communication module can send a message to NTN-RAN. The non-terrestrial network communication module can also receive a message from NTN-RAN.

[0371] In some embodiments, the antenna 1 of UE 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that UE 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0372] UE100 implements display functions through GPU, display screen 194, and application processor. GPU is a microprocessor for image processing, connected to display screen 194 and application processor. GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0373] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the UE 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0374] UE100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0375] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise and brightness of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

[0376] Camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, UE100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0377] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the UE 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0378] Video codecs are used to compress or decompress digital videos. UE100 can support one or more video codecs. In this way, UE100 can play or record videos in multiple coding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0379] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and continuously self-learn. NPU can realize applications such as intelligent cognition of UE100, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0380] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the UE 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external non-volatile memory.

[0381] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of UE100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of UE100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0382] The UE 100 can implement audio functions such as music playing and recording through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor.

[0383] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. The microphone 170C, also called a "microphone" or "microphone", is used to convert sound signals into electrical signals.

[0384] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. The gyroscope sensor 180B can be used to determine the motion posture of the UE 100. The air pressure sensor 180C is used to measure the air pressure. The magnetic sensor 180D includes a Hall sensor, and the magnetic sensor 180D can be used to detect the opening and closing of the flip leather case. The acceleration sensor 180E can detect the magnitude of the acceleration of the UE 100 in various directions (generally three axes). The distance sensor 180F is used to measure the distance. The proximity light sensor 180G can also be used for automatic unlocking and locking of the leather case mode and pocket mode. The ambient light sensor 180L is used to sense the ambient light brightness. The fingerprint sensor 180H is used to collect fingerprints. The temperature sensor 180J is used to detect the temperature. The touch sensor 180K is also called a "touch panel". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect a touch operation acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the UE100, which is different from the position of the display screen 194. The bone conduction sensor 180M can obtain a vibration signal. The button 190 includes a power button, a volume button, etc. The motor 191 can generate a vibration prompt. The indicator 192 can be an indicator light, which can be used to indicate the charging status, the change of the power, and can also be used to indicate messages, missed calls, notifications, etc.

[0385] The SIM card interface 195 is used to connect SIM cards, for example, SIM1, SIM2, and SIM3. The SIM card can be connected to and separated from the UE 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The UE 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The UE 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the UE 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the UE 100 and cannot be separated from the UE 100.

[0386] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A capability synchronization method, characterized in that: Applied to a communication system, the communication system includes a user equipment UE, a core network NTN-CN device of a non-terrestrial network, a radio access network device NTN-RAN of a non-terrestrial network, and a terrestrial network device; the method includes: The UE receives a first non-terrestrial network air interface capability request sent by the terrestrial network device, and sends a first non-terrestrial network air interface capability message to the terrestrial network device, where the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; The terrestrial network device sends a second non-terrestrial network air interface capability message to the NTN-CN device, where the second non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; The UE searches for the NTN, and sends a first mobility registration request message to the NTN-CN device through the NTN-RAN device, where the first mobility registration request message is used for the UE to register with the NTN-CN device; After receiving the first mobility registration request message, the NTN-CN device sends the NTN air interface capability information of the UE to the NTN-RAN device.

2. The method according to claim 1, characterized in that Before the UE receives the first non-terrestrial network air interface capability request, the method further includes: After the UE registers with the NTN-CN device through the ground network device, the NTN-CN device sends a second non-ground network air interface capability request to the ground network device, where the second non-ground network air interface capability request is used by the NTN-CN device to obtain NTN air interface capability information of the UE; After receiving the second non-terrestrial network air interface capability request, the terrestrial network device sends the first non-terrestrial network air interface capability request to the UE.

3. The method according to claim 2, characterized in that The terrestrial network device includes a TN-RAN device of a terrestrial network and a TN-CN device of a core network of the terrestrial network; after receiving the second non-terrestrial network air interface capability request, the terrestrial network device sends the first non-terrestrial network air interface capability request to the UE, specifically including: The TN-CN device receives the second non-terrestrial network air interface capability request, and sends the first non-terrestrial network air interface capability request to the TN-RAN device; The TN-RAN device receives the first non-terrestrial network air interface capability request, and sends the first non-terrestrial network air interface capability request to the UE.

4. The method according to claim 2, characterized in that: The terrestrial network device includes a TN-CN device and a TN-RAN device; after receiving the second non-terrestrial network air interface capability request, the terrestrial network device sends the first non-terrestrial network air interface capability request to the UE, specifically including: The TN-CN device receives the second non-terrestrial network air interface capability request, and sends the second non-terrestrial network air interface capability request to the TN-RAN device; The TN-RAN device receives the second non-terrestrial network air interface capability request, and sends the first non-terrestrial network air interface capability request to the UE.

5. The method according to claim 1, characterized in that The terrestrial network device includes a TN-RAN device; before the UE receives the first non-terrestrial network air interface capability request, the method further includes: After the UE registers with the NTN-CN device through the TN-RAN device, the NTN-CN device sends a second non-terrestrial network air interface capability request to the TN-RAN device, where the second non-terrestrial network air interface capability request is used by the NTN-CN device to obtain NTN air interface capability information of the UE; After receiving the second non-terrestrial network air interface capability request, the TN-RAN device sends the first non-terrestrial network air interface capability request to the UE.

6. The method according to any one of claims 1 to 5, characterized in that The ground network device sends the second non-ground network air interface capability message to the NTN-CN device, specifically including: The terrestrial network device sends the second non-terrestrial network air interface capability message to the NTN-CN device in response to the first non-terrestrial network air interface capability message.

7. The method according to claim 6, characterized in that The first non-terrestrial network air interface capability message is a user equipment capability information UE Capability Information message, and the second non-terrestrial network air interface capability message is a user equipment capability information indication UE Capability Infor Indication message.

8. The method according to claim 1, characterized in that The terrestrial network device includes a TN-CN device; before the UE receives the first non-terrestrial network air interface capability request, the method further includes: After the UE registers with the TN-CN device through the terrestrial network device, the terrestrial network device sends the first non-terrestrial network air interface capability request to the UE.

9. The method according to claim 8, characterized in that The sending, by the terrestrial network device, the first non-terrestrial network air interface capability request to the UE specifically includes: After the UE registers with the TN-CN device through the ground network device, the UE sends a first capability change message to the TN-CN device, where the first capability change message is used to indicate a change in the NTN air interface capability of the UE; The TN-CN device sends a second non-terrestrial network air interface capability request to the TN-RAN device in response to the first capability change message; The TN-RAN device sends the first non-terrestrial network air interface capability request to the UE in response to the second non-terrestrial network air interface capability request; or, The TN-CN device sends the first non-terrestrial network air interface capability request to the UE through the TN-RAN device in response to the first capability change message.

10. The method according to claim 9, characterized in that The first capability change message is a second mobility registration request message, and the second mobility registration request message includes a parameter for indicating a change in the NTN air interface capability of the UE; or the first capability change message is a user equipment capability release command message.

11. The method according to any one of claims 8 to 10, characterized in that: The method further comprises: After the NTN-CN device receives the first mobility registration request message, sending a first capability synchronization message to the TN-CN device, where the first capability synchronization message is used to obtain the NTN air interface capability information of the UE from the TN-CN device; The ground network device sends the second non-ground network air interface capability message to the NTN-CN device, specifically including: The TN-CN device sends the second non-terrestrial network air interface capability message to the NTN-CN device in response to the first capability synchronization message.

12. The method according to any one of claims 1 to 11, characterized in that The sending the NTN air interface capability information of the UE to the NTN-RAN device specifically includes: The NTN-CN device sends an initial context setup request message to the NTN-RAN device, where the initial context setup request message includes the NTN air interface capability information of the UE.

13. The method according to any one of claims 1 to 12, characterized in that The first non-terrestrial network air interface capability request is a user equipment capability query UE capability enquiry (NTN) message, and the second non-terrestrial network air interface capability request is a non-terrestrial network air interface capability information request NTN capability info request.

14. The method according to any one of claims 1 to 13, characterized in that The NTN air interface capability information includes carriers supported by the UE, antenna polarization directions of the UE, maximum transmit power of the UE, and duplex mode of the UE.

15. A capability synchronization method, characterized in that: Applied to user equipment UE, characterized in that the method comprises: The UE receives a first non-terrestrial network air interface capability request sent by a terrestrial network device, where the first non-terrestrial network air interface capability request is used to obtain NTN air interface capability information of the UE; After receiving the first non-terrestrial network air interface capability request, the UE sends a first non-terrestrial network air interface capability message to the terrestrial network device, where the first non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE; After searching for the non-terrestrial network NTN, the UE sends a mobility registration request message to the core network NTN-CN device of the non-terrestrial network, and the mobility registration request message is used to trigger the NTN-CN device to send the NTN air interface capability information of the UE to the NTN-RAN device.

16. The method according to claim 15, characterized in that: Before the UE receives the first non-terrestrial network air interface capability request sent by the terrestrial network device, the method further includes: The UE registers with the NTN-CN device through the ground network device.

17. The method according to claim 15, characterized in that: Before the UE receives the first non-terrestrial network air interface capability request sent by the terrestrial network device, the method further includes: The UE is registered with the TN-CN device.

18. The method according to any one of claims 15 to 17, characterized in that: Before the UE receives the first non-terrestrial network air interface capability request sent by the terrestrial network device, the method further includes: The UE sends a first capability change message to the TN-CN device, where the first capability change message is used to indicate that the NTN air interface capability of the UE has changed.

19. A capability synchronization method, characterized in that: The core network NTN-CN device applied to the non-terrestrial network is characterized in that the method comprises: The NTN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE through the terrestrial network device, where the first non-terrestrial network air interface capability request is used to obtain NTN air interface capability information of the UE; The NTN-CN device receives, through the terrestrial network device, a first non-terrestrial network air interface capability message sent by the UE, where the first non-terrestrial network air interface capability message includes NTN air interface capability information of the UE; After receiving the first mobility registration request message sent by the UE, the NTN-CN device sends the NTN air interface capability information of the UE to the radio access network NTN-RAN device of the non-terrestrial network, where the first mobility registration request message is used for the UE to register with the NTN-CN device.

20. The method according to claim 19, characterized in that Before the NTN-CN device sends the first non-terrestrial network air interface capability request to the UE through the terrestrial network device, the method further includes: The NTN-CN device accepts the initial registration request of the UE through the ground network device.

21. The method according to claim 19 or 20, characterized in that The NTN-CN device sends a first non-terrestrial network air interface capability request to the UE through the terrestrial network device, specifically including: The NTN-CN device receives, through the ground network device, a first capability change message sent by the UE, where the first capability change message is used to indicate that the NTN air interface capability of the UE has changed; In response to the first capability change message, the NTN-CN device sends the first non-terrestrial network air interface capability request to the UE through the terrestrial network device.

22. A capability synchronization method, characterized in that: Applied to non-terrestrial network equipment NTN-CN, characterized in that the method comprises: After receiving the first mobility registration request message sent by the user equipment UE, the NTN-CN device sends a first capability synchronization message to the core network TN-CN device of the ground network, where the first capability synchronization message is used to obtain the NTN air interface capability information of the UE from the TN-CN device; The NTN-CN device receives a first non-terrestrial network air interface capability message sent by the TN-CN device, where the first non-terrestrial network air interface capability message includes NTN air interface capability information of the UE; The NTN-CN device sends the NTN air interface capability information of the UE to a radio access network NTN-RAN device of a non-terrestrial network.

23. A capability synchronization method, characterized in that: A core network TN-CN device applied to a terrestrial network, characterized in that the method comprises: The TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, where the first non-terrestrial network air interface capability request is used to obtain NTN air interface capability information of the UE; The TN-CN device receives a first non-terrestrial network air interface capability message sent by the UE, where the first non-terrestrial network air interface capability message includes NTN air interface capability information of the UE; The TN-CN device sends a second non-terrestrial network air interface capability message to a core network NTN-CN device of the non-terrestrial network, where the second non-terrestrial network air interface capability message includes NTN air interface capability information of the UE.

24. The method according to claim 23, characterized in that The TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, specifically including: The TN-CN device receives a second non-terrestrial network air interface capability request sent by the NTN-CN device; The TN-CN device sends the first non-terrestrial network air interface capability request to the UE in response to the second non-terrestrial network air interface capability request.

25. The method according to claim 23, characterized in that The TN-CN device sends a first non-terrestrial network air interface capability request to the user equipment UE, specifically including: After accepting the initial registration request of the UE, the TN-CN device sends the first non-terrestrial network air interface capability request to the UE.

26. The method according to claim 25, characterized in that The TN-CN device sends a second non-terrestrial network air interface capability message to the core network NTN-CN device of the non-terrestrial network, specifically including: The TN-CN device receives a first capability synchronization message sent by the NTN-CN device; The TN-CN device sends the second non-terrestrial network air interface capability message to the NTN-CN device in response to the first capability synchronization message.

27. The method according to any one of claims 23 to 26, characterized in that Before the TN-CN device sends the first non-terrestrial network air interface capability request to the user equipment UE, the method further includes: The TN-CN device receives a first capability change message sent by the UE, where the first capability change message is used to indicate that an NTN air interface capability of the UE has changed.

28. A capability synchronization method, characterized in that: A TN-RAN device for a terrestrial network, wherein the method comprises: The TN-RAN device sends a first non-terrestrial network air interface capability request to the user equipment UE, where the first non-terrestrial network air interface capability request is used to obtain NTN air interface capability information of the UE; The TN-RAN device receives a first non-terrestrial network air interface capability message sent by the UE, where the first non-terrestrial network air interface capability message includes NTN air interface capability information of the UE; The TN-RAN device sends a second non-terrestrial network air interface capability message to a core network NTN-CN device of a non-terrestrial network or a core network TN-CN device of a terrestrial network, where the second non-terrestrial network air interface capability message includes the NTN air interface capability information of the UE.

29. An electronic device, characterized in that: include: one or more processors and one or more memories; The one or more memories are coupled to one or more processors, and the one or more memories are used to store computer executable programs. When the one or more processors execute the computer executable programs, the electronic device executes the method described in any one of claims 15-18, 19-21, 22, 23-27 or 28.

30. A computer-readable storage medium storing a computer program, characterized in that: When the computer program runs on a processor of an electronic device, the electronic device is caused to execute the method according to any one of claims 15-18, 19-21, 22, 23-27 or 28.

Images